Database Users

How is JL2 treating everyone?

Should I bite the bullet and try an upgrade? I'm still marinating on 2.1.

if you feel safe, and don't mind taking the phone back to the store for repair at any random day
then go ahead by all means.
PROS: you'll find out sooner, and get your phone warrantied before it expires, or your device might work perfectly and never dies.
CONS: you'll most likely be stuck without a phone for a few weeks

I've had JL2 for a couple of weeks and it's working well. I did have Darky's ROM on it for a couple of days but it was acting up so I put JL2 back on.
No lag, Great GPS, no issues at all.
Ian

I love JL2... But I have not had a single issue since the phone came out. I was the first person to buy the phone at the north Bell store in the Eaton Centre the day it came out on Aug 6th.
I flashed jk4 on dec 8th or so and had no issues and then moved to JL2 a few days ago. On 2.1 I always got a quick lock with GPS but did suffer from minor drifting. That drifting is now gone on 2.2 (both jk4 & jl2)
Sent from my GT-I9000M

And after reading the sd issue thread I would reccomend upgrading even more. If it bricks with sd failure it really sounds like Bell had stepped up with getting new phones and a credit out to people.
Sent from my GT-I9000M

been on jl2 since dec 24th, everything works fine for the most part. One issue though - i can't close the contacts, i have to press the home button and then when i check the task manager, it's still running in the background. This get's pretty annoying. Anyone else experiencing this?
EDIT:: also do you guys see 304 MB of ram that's accessible (through task manager->ram manager)? That's what i see (wasn't 2.1 also like this?)

asicman said:
Should I bite the bullet and try an upgrade? I'm still marinating on 2.1.
Click to expand...
Click to collapse
Do it now so that if you have any problems, it'll happen sooner than later, and you'll still be covered by your warranty, which you are almost 5 months through.

If I were you, I'd install it as soon as possible. Worst case scenario is they ship you a new phone within 7 days if your phone breaks. My phone had a failed internal sd when I did a factory reset before I went to try the jl2 upgrade since I was told by bell it would fix the problem, but unforunately my phone broke before I even got the chance to do it so bell did a work order and sent me a new phone which I should receive within 7 days, all I have to do is ship them back my broken phone when I receive the new one.

asicman said:
Should I bite the bullet and try an upgrade? I'm still marinating on 2.1.
Click to expand...
Click to collapse
My buddy's phone died after going to JL2. The good thing was that Bell is giving him a new phone within the next 5 business days AND he got $100 credit for all the trouble.

I flashed the jl2 modem today on a jpu based rom. A couple hours later and I'm now stuck in a boot loop. coincidence? Who knows.

I've been on JL2 since it came out on Kies. The day before while I was on JK4 my phone was starting to get some FCs and at one point I got the "Internal SD Unexpectedly Removed" error so I'm pretty sure my internal SD was on the brink of failing. I'm glad a new firmware came out. I immediately upgraded and did a factory reset and formatted the internal SD. It's been smooth sailing ever since and I do take a lot of pictures, video, etc. on my phone with no issues since JL2.
I love JL2 so far. It's fast (just as fast as JK4 was) and after some tweaking via instructions I found here GPS is good. I have had ONE force close since upgrading and I think that was just the Winamp app being stupid.
I haven't really seen anyone posting here about actually being bricked after JL2. Has anyone actually upgraded to JL2 and got the internal SD error?

Thanks for the input everyone. I'm a little more confident now with upgrading. And it of course makes sense to do it now to find out problems whilst there is still warranty.
I'll give it a wack tonight. Btw, with an upgrade, do things like music and contacts get wiped out? Its my first android upgrade and I plan on using kies. Any caveats with kies?
Sent from my GT-I9000M using XDA App

asicman said:
Thanks for the input everyone. I'm a little more confident now with upgrading. And it of course makes sense to do it now to find out problems whilst there is still warranty.
I'll give it a wack tonight. Btw, with an upgrade, do things like music and contacts get wiped out? Its my first android upgrade and I plan on using kies. Any caveats with kies?
Sent from my GT-I9000M using XDA App
Click to expand...
Click to collapse
You should be ok with a straight upgrade, but I'll always recommend doing a factory reset - it clears out the crap that could cause problems.
As for your music and stuff, that depends where you store it. If you have it on your internal sd, and you do a factory reset, then yes. If its on your external sd, then no. Contacts are fine if you store them on your SIM or sync with Google.

andd64 said:
been on jl2 since dec 24th, everything works fine for the most part. One issue though - i can't close the contacts, i have to press the home button and then when i check the task manager, it's still running in the background. This get's pretty annoying. Anyone else experiencing this?
Click to expand...
Click to collapse
I am and it's very irritating indeed. It's the same with the internet browser (always has been)
andd64 said:
EDIT:: also do you guys see 304 MB of ram that's accessible (through task manager->ram manager)? That's what i see (wasn't 2.1 also like this?)
Click to expand...
Click to collapse
Yes

gtg2 said:
I flashed the jl2 modem today on a jpu based rom. A couple hours later and I'm now stuck in a boot loop. coincidence? Who knows.
Click to expand...
Click to collapse
Is it really safe to combine different files from different ROMs? I would think mixing and matching can cause some problems.
Ian

I do have one complaint after going to JL2 -
In my Picasa albums in Gallery, the photos are no longer sorted by date as they were in 2.1. Also, sometimes the Gallery fails to load/display the full resolution image instead just displaying the pixelated preview while flipping through images.
Never had this problem in 2.1 (JH2) - I wonder if it's possible to revert the Gallery app to the previous version?

I got my phone in september and never had any trouble with it. I have rooted it, applied different lag fix and enen managed to stupidly brick it but it always survived.
I like JL2, but I had no problem with JK4 either. However, I don't find TouchWiz as smooth as it was with JH2. It lags a little when switching across apps or homescreens, so I use LauncherPro which is perfect.
BUT, my GPS doesn't work at all
It worked ok before installing JL2, but now its totally useless. I can see satellites but can't get a fix....any advice?

Smooth ride so far. Went from stock 2.1 (end-of-August purchase) to JL2. I did not do the JK4.

So far ok.............. I seem to get FC on the Samsung hub everytime I pull the battery out and I have to re-install the app. GPS locks but it takes awhile.

Just do it! My phone was bricked on Dec 25 for no reason. I updated to froyo 2.2 via Kies about a month ago. I called Bell and told them my issue, internal fried sd card! They gave me Bell's Data Support line. I'm getting a brand new Samsung Galaxy with the latest Dec 24. froyo 2.2.1 update installed. I'll be without a phone for about a week or so but there customer service is awsome. I also go a $100 credit to my account for the inconvience.
If you update and phone is bricked call this number 1.877.328.2123 and they will send you a new phone in 3-5 days.

Help with Nebula ROM ISSUES

After a few issues I was able to get Nebula ROM 1.0.7 up and running on my EPIC. I really like it so far. It is much faster then the other ROM I tried out, plus it doesn't have any of the cheesey sound efffects.
I have used it for a day with no problems. My battery was getting a bit low so I shut the phone down to change batteries. I put the new battery in and when I booted it up it just went into a loop with the Nebula animation, then the 1.0.7 screen would come up and then it would just loop.
I took the battery back out, reinstalled it, and this time it boots into the phone but everything FC's. Took the battery out again and booted it back up and now this time it loads up, some things run, but others FC...
I did the clearing of all caches and user data three times along with a dalevic wipe three times... What gives??
I consider myself a computer geek, but am definately new to the rooting/custom rom thing, so I am a Noob, be gentle!!

socos25 said:
After a few issues I was able to get Nebula ROM 1.0.7 up and running on my EPIC. I really like it so far. It is much faster then the other ROM I tried out, plus it doesn't have any of the cheesey sound efffects.
I have used it for a day with no problems. My battery was getting a bit low so I shut the phone down to change batteries. I put the new battery in and when I booted it up it just went into a loop with the Nebula animation, then the 1.0.7 screen would come up and then it would just loop.
I took the battery back out, reinstalled it, and this time it boots into the phone but everything FC's. Took the battery out again and booted it back up and now this time it loads up, some things run, but others FC...
I did the clearing of all caches and user data three times along with a dalevic wipe three times... What gives??
I consider myself a computer geek, but am definately new to the rooting/custom rom thing, so I am a Noob, be gentle!!
Click to expand...
Click to collapse
Firstly, I'm sorry for your troubles and welcome you to the ROM scene. But I would say posting this (or looking through) the Nebula ROM thread or posting this in the Q&A section would likely end up with better results.
Secondly, I also had experienced issues with Nebula ROM 1.0.7. My recommendation is to Odin all the way back to DK28, then work your way back up to Nebula. Also, try flashing Nebula twice onto the device to try to remedy any problems.
Another tip, it seems that if you are using things like Titanium Backup that there are instances of people running into problems of backed up apps causing problems. Starting new is probably the best bet.
Hope this was of some use!

Thank you for the help.. I posted this in General because every other day I see people getting ripped into for not posting in General, so to be honest I have been scared to post anywhere else... But I have read the Nebula thread, not all 110+ pages, but quite a few of them. I am going to Odin back to DK28, format my SD card, and start from scratch, then try reinstalling all of my Apps.
I just think it is wierd that it worked flawlessly for a whole day without one FC and then when I changed my battery it went to hell.
The even stranger thing is some apps work fine, and then others FC everytime. Seems to be no rhyme or reason..
Only other thing I am thinking is I installed a bunch of new apps today and wondered if that could be part of the problem...
Oh well, it has made me more aware of what is going on behind the scenes with my phone.

I could be totally wrong, but I think that's due to it being an ext4 with no journaling rom. Without that safety net its possble for data to be corrupted. sinse I switched to ext4 with no journaling I started letting the phone turn off instead of just pulling out the battery.
Like I said tho I could be wrong on this. Back when I was on the moment I had ext2 which doesn't have journaling either and if the data became currupted somehow, it would cause the symptoms you are explaining.
Sent from my SPH-D700 using Tapatalk

socos25 said:
Thank you for the help.. I posted this in General because every other day I see people getting ripped into for not posting in General, so to be honest I have been scared to post anywhere else... But I have read the Nebula thread, not all 110+ pages, but quite a few of them. I am going to Odin back to DK28, format my SD card, and start from scratch, then try reinstalling all of my Apps.
I just think it is wierd that it worked flawlessly for a whole day without one FC and then when I changed my battery it went to hell.
The even stranger thing is some apps work fine, and then others FC everytime. Seems to be no rhyme or reason..
Only other thing I am thinking is I installed a bunch of new apps today and wondered if that could be part of the problem...
Oh well, it has made me more aware of what is going on behind the scenes with my phone.
Click to expand...
Click to collapse
Ah, alright. I'm not too certain as I'm unaware of a good deal of the inner workings of Android, but I do hope things get straightened out for you. My phone still has some apps that act up sometimes, mostly JuicePlotter it seems.

Hanging arround... I forgot my last un and passwd(I had an htc tilt a while ago... now I can't post on dev forum...) to use 1.0.7 I think you need ext4 (at least I'm using it) some apps are giving troubles with ext4. So try one by one, and use the cwm3 backup system. At least for me is easier and safer than tit or backup pro.
Sent from my SPH-D700 using Tapatalk

I am so glad I didn't update to 1.0.7!

socos25 said:
After a few issues I was able to get Nebula ROM 1.0.7 up and running on my EPIC. I really like it so far. It is much faster then the other ROM I tried out, plus it doesn't have any of the cheesey sound efffects.
I have used it for a day with no problems. My battery was getting a bit low so I shut the phone down to change batteries. I put the new battery in and when I booted it up it just went into a loop with the Nebula animation, then the 1.0.7 screen would come up and then it would just loop.
I took the battery back out, reinstalled it, and this time it boots into the phone but everything FC's. Took the battery out again and booted it back up and now this time it loads up, some things run, but others FC...
I did the clearing of all caches and user data three times along with a dalevic wipe three times... What gives??
I consider myself a computer geek, but am definately new to the rooting/custom rom thing, so I am a Noob, be gentle!!
Click to expand...
Click to collapse
Sorry I missed this yesterday, but I wanted to say that I had the same problem updating to 1.07 and I had already gone back to DK28 stock w/ CWM3 before the upgrade. I also restored some apps and settings selectively using titanium. One thing that we may have in common is that I ran my battery ALL the way down accidentally after this upgrade, tried turning it on a couple times (and it would shut down right away) and when I plugged the phone back in I got the repetitive force closes when I tried to turn it on.
Anyhow, I recharged completely, started from stock DK28 again (and wiped the battery stats) and even with restoring the same settings from Titanium I have been running it for about a week now and it is rock solid. So, give it another shot and see how it goes...

The short version is I got everything working!! And Nebula 1.0.7 is the fastest rom I have used yet... But don't get too excited because this is only the third I've tried, and one of the other two is stock DK28.
What I ended up doing was Odin'ing back to DK28, installing CW3, and then doing the 3x3 clears. Then I also formated everything I could find in CW. Installed the Nebula Rom and still had an issue. Rebooted back into CW3 and then reinstalled the ROM again, and whalla.. It works.
I think for some reason you have to install it twice.. Strange I know..

I had force close issues as well, and all I did to fix it was go into CWM, and format/clear cache partition, and format/clear the dalvik-cache. Did this cache clear and dalvik clear 3 times.

coryshad said:
I could be totally wrong, but I think that's due to it being an ext4 with no journaling rom. Without that safety net its possble for data to be corrupted. sinse I switched to ext4 with no journaling I started letting the phone turn off instead of just pulling out the battery.
Like I said tho I could be wrong on this. Back when I was on the moment I had ext2 which doesn't have journaling either and if the data became currupted somehow, it would cause the symptoms you are explaining.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
I second this as a possible problem. Shut the phone off 100% before removing the battery. On the moment that I also had if you removed the battery or used quick boot with ext2 you faced possible data corruption, but there were kernels that would check and fix data. You'd end up in a boot loop though if it didn't repair.
Sent from my SPH-D700 using XDA App

I've been making sure to shut it off before removing the battery, so far so good. I'm really liking this much better than stock.
Want to try a speedtest with the wifi tethering while going down th road.
I did a speedtest yesterday in my house and got 1.5mb DL, .5mb up. That was on my airrave though.
Sent from my SPH-D700 using XDA App

Strange "black" Reboots

Hi!
I'm suffering from reboots on my Note (also on my S2...). I call them "black" reboots because the screen becomes black, there's no start-up animation , I only hear the sound, and the home screen don't comes up, or it do it after a long delay. So, the screen is mostly black. Until 2-3 minutes pass, and reboot again.
-Sometimes occurs simply starting up the phone in the morning. I'm advised of a slow launcher load (Go Launcher, but it can occurs on TW).
If I go to System Monitor (System Panel app), I see the 2 cores working hard, toghether or alternating. The "System" app goes mad. The battery drain becomes quick, and the phone back around the camera begins to warming...
After 2-3 minutes with this behaviour, the "black" reboot comes up. Often, after rebooting, the message "Unable to run System process"- Force Close-Wait (or so) appears in the black...etc
If I force shut-off, then I wait and then shut-on again, all things seem normal, until...reboot
-Factory reset (through Recovery, of course) seems arrange all things, until I load again the apps. I've unistalled all "tweaking" apps for overclocking, Ram managing, etc. I only have Root explorer and Speed Boost as Root operating things...
- My Rom is an odex Pre-rooted XXLC1, Modem XXLB2, but the multiCSC is not from it.
How the phone can become so unstable with only the half memory app capacity occuped? (800 Mb or so of 2GB)?
And how can it often occurs on updating apps from damned Google Play Store?
Is worth to flash another Rom (not ICS...), or re-flash same with its CSC included?
Sorry if I've been too long. In my searchs I only see things about bricks or another type of reboots.
Thanks for read me!

i get these once every two weeks or so.

I also get these type of reboots, I get them on RocketROM and on previous roms I've had installed the only way I've found to get out of them is to boot into recovery and wipe the caches. Before I was rooted I removed some of the apps I'd moved to the SD Card and that sometimes stopped the boot loop. I now only update apps one by one someone suggested it was to do with the amount of apps moved to the sd card and the multiple updating of them. I'm still not sure of the cause I know its the only flaw on my Note that I'm fed up with.

Im running stock ics rom straight from samsung only with root and getting the same behaviour as yourself. About 2 to 3 times a week...
Sent from my GT-N7000

Ive posted a poll as i also experience this issue. Can you vote on the poll here please with how many reboots you are getting etc - http://forum.xda-developers.com/showthread.php?t=1706343

tallen3 said:
I also get these type of reboots, I get them on RocketROM and on previous roms I've had installed the only way I've found to get out of them is to boot into recovery and wipe the caches. Before I was rooted I removed some of the apps I'd moved to the SD Card and that sometimes stopped the boot loop. I now only update apps one by one someone suggested it was to do with the amount of apps moved to the sd card and the multiple updating of them. I'm still not sure of the cause I know its the only flaw on my Note that I'm fed up with.
Click to expand...
Click to collapse
gnikolakis said:
Im running stock ics rom straight from samsung only with root and getting the same behaviour as yourself. About 2 to 3 times a week...
Sent from my GT-N7000
Click to expand...
Click to collapse
Guys, i don't know if I'm going to cry of pain or to laugh of huge joy, after seeing this is almost ..."normal"
We have a beautiful 500€ plastic and metal block which is unable to perform the half of things it's supposed to do! And we don't know exactly why...
Sure I do wipes, but most of times this fixes nothing, and the reboot returns.
If I re-install with Titanium, I am very careful unsellecting into the batch which things can cause problems, installing only a few apps.
After some days, I go on installing manually some others.
The Play updates are critical, as I see... Why? How it's possible that this "beasts" with so much RAM and so much App Memory (2 GB on S2 and Note!) fail down handling its management, with their super 2 core CPU's?
It's too serious. How we can live with a 500€ phone rebooting bad 2 times a week?
Can you imagine that on your computer, forcing you to re-install OS and apps once or twice a week? It's crazy. Is Android going crazy?
Maybe Samsung don't like Root users? Have HTC same problem?
There's someone with a non rooted phone with same problem?

Are you guys running stock? Had custom rom installed or still have?
Sent from my GT-N7000 using Tapatalk 2

baz77 said:
Are you guys running stock? Had custom rom installed or still have?
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
I have this Rom, based on strict stock, but rooted: http://forum.xda-developers.com/showpost.php?p=24690725&postcount=154
Mine is the XXLC1
No tweaks, no overclocking, no CWM...

I had the same problem when my GN was on rooted LC1. I disappeared after I made a factory reset and let my apps reinstall by Play Store.

Yes me too got out of this strange reboot by a factory reset today morning.
Something is messed up .....
Very difficult to find that something ...
better idea would be a factory reset .....

I think the problem is with the Stock Samsung Rom, it doesnt happen in CM9 Roms. I had this problems wen on ROcket rom, but vanished when on Asylum Rom.

go wild...
"I had the same problem when my GN was on rooted LC1. It disappeared after I made a factory reset and let my apps reinstall by Play Store"
Thanks, milesabords, I'll try that the...(glappps) next time.
.
prabhu1980 said:
Yes me too got out of this strange reboot by a factory reset today morning.
Something is messed up .....
Very difficult to find that something ...
better idea would be a factory reset .....
Click to expand...
Click to collapse
Yesss, very difficult. I'm not on advanced technical stuff, but my intuition says that is something deep inside the Rom, something that is related to CPU-Memory management.
By the way, do you have/had many apps (250+)? Have you made recently massive update and/or installing apps, or massive "App to SD" moves?
bhasg1007 said:
I think the problem is with the Stock Samsung Rom, it doesnt happen in CM9 Roms. I had this problems wen on ROcket rom, but vanished when on Asylum Rom.
Click to expand...
Click to collapse
You are pushing me a little step more to the wild side of Android.... Here I'll go!
It seems to me that the Note is a strangely different phone of, say, S2. Some apparently "simple" apps that I carry on from 2 years ago don't run right.
And the little lags that sometimes appear on touching icons, never, never appear on the fast S2.

Lol be carefully factory on ICS resetting...
Try and official rom, haven't seen it myself
Sent from my GT-N7000 using Tapatalk 2

baz77 said:
Lol be carefully factory on ICS resetting...
Try and official rom, haven't seen it myself
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Don't worry, baz77, I don't touch ICS by now even with gloves & calipers...

[Q] Play store breaks Cyanogenmod?

Hi everyone,
This morning when wake up I noticed a lot of applications were stopping ("XYZ has stopped") - including Google Keep. Also, many app/system settings were suddenly missing from the phone. I had to go through the whole process of reinstalling CM10, realizing that my Nandroid backup (made with OBackup) was in CWM format, rendering it unusable with TWRP (or this is what I, being pretty much a newb in the ROM world, understand from the situation).
A couple weeks ago something similar happened : my defy would bootloop at the CM logo.
This is starting to be exasperating a bit. But the only thing I can think of is that now I noticed I have Play Store 4.4.21 on the Defy - whereas on my Nexus 7 I have 4.3.11. Hence the version on my Defy seems to be the one that just came out. Could Play Store updating itself be causing the problems I'm having on my Defy? Why do I now have the new version if I just flashed CM10 a couple minutes ago, and why would it be working correctly now?
I already googled everything I could think of relating to this and couldn't come up with an answer. That is to say, I'm pretty much clueless about all this!
Thanks..

tb877 said:
Hi everyone,
This morning when wake up I noticed a lot of applications were stopping ("XYZ has stopped") - including Google Keep. Also, many app/system settings were suddenly missing from the phone. I had to go through the whole process of reinstalling CM10, realizing that my Nandroid backup (made with OBackup) was in CWM format, rendering it unusable with TWRP (or this is what I, being pretty much a newb in the ROM world, understand from the situation).
A couple weeks ago something similar happened : my defy would bootloop at the CM logo.
Thanks..
Click to expand...
Click to collapse
There are 2 possible things going on here:
problems with android's data sync with google's services. (this morning there was a diffused malfunction, at least here in Italy)
the infamous CM10's data corruption bug (see details in the bug list). it especially happens if you let completely discharge your phone. Symptoms match with yours
Since the data corruption bug is still under investigation, the best workaround is to keep a (weekly?) data backup.
After a data corruption, reformat in ext4 through the recovery's data tool and then:
reflash rom and gapps
restore your data

Well both times CM broke my phone's battery wasn't empty at all (the last time it was charging...)
When you refer to the sync problem I experienced it on my N7 yesterday, but it seems nowhere as dangerous as to be able to completely break the OS.
Oh well anyway, seems like CM10 isn't quite ready for being a daily driver.. I'll simply learn how to flash/restore backups correctly and as fast as possible it seems!
Sent from my Nexus 7 using Tapatalk 4

The only thing that really bothers me is that I never thought I'd lose so much time in rooting/modding my old defy.. I've spent countless hours on XDA/other forums, and yesterday I even had to restore the (almost bricked) defy with rsdlite after (incorrectly) trying to put CWM to restore my otherwise unusable backup. Then, when I had succeeded in putting CWM, it would totally refuse to restore, complaining about unmountable /system!
I do understand that its totally my choice to root/mod my devices, but with cell phones becoming more and more essential nowadays in everyday life, it seems to me that everyone almost has to become an android developer to survive!
/whine
Sent from my Nexus 7 using Tapatalk 4

New Nexus 6P User, problems out of the gate

So like the title says, I'm a new Nexus 6P user, and I had problems out of the gate.
I bought the device 2nd hand from a guy off craigslist, after my S6 edge started over heating after I had the screen replaced (don't buy Samsung "edge" phones, I know your careful, but on the off chance you drop it, your in a world of trouble).
I tested the phone, before I bought it, it appeared pretty much brand new, everything worked. When I got home, and hard reset it again for good measure all hell broke lose.
After a hard reset the phone wanted to update to build 19 something. After the update and a reboot, the phone app kept crashing before I could finish the setup process. The only thing I could do is factory reset it again. This appeared to clear up that problem. I did the near by device thing, and restored it from what Google could find out about my S6 edge. I wish it was more of a restore like what you can do in the iOS world, but it's better then what we had before so it's cool. I noticed that Chrome would crash everytime you tried to use it only in less I uninstalled the update. After I got the phone to the point where I wanted it, I thought I was free in the clear. When I started trying to use music apps, they all crash. Apple Music, Spotify, Soundcloud. Then I noticed YouTube also crashed the same way. When I tried to make a phone call, the phone app would crash too... So the phone was useless. I downloaded the SDK and the most current build which I think was 20 something. I followed a guide on here and formatted the phone reinstalling everything around build 20. The only thing this fixed was the phone issue.
I could now make phone calls without it crashing, but I was in the same boat with some applications working, and the same ones that didn't work not working. I flashed this phone 5, or 6 times, with the last time me formatting the userdata. I read that it wasn't a good idea because it could lock me to only 32GB ( I had a 64GB version), but after I did the flashing along with the usedata format, I still had 64GB of useable space, however I still had the same issue with the same types of applications crashing. I tried older builds, same issue (also the older builds all had the problem with the phone app crashing to the point that the phone wasn't usable).
I ended up sending the phone to the manufacturer, which appears to be in the same metroplex I live in. Hopefully they can find a hardware problem under warenty and fix it. I'm making this post to see if anyone else ran into similar issues, and if anyone knows if this is a hardware build issue, that was hopefully resolved.
I'm sorry to be so long winded...

Is the phone rooted and running a custom ROM?

Pappy35 said:
Is the phone rooted and running a custom ROM?
Click to expand...
Click to collapse
Everything appeared to be stock, I don't know if it was rooted before, but when I was finished with it it was stock, I even locked the boot loader again (it was locked before I started flashing it)

vmiyoshi said:
Everything appeared to be stock, I don't know if it was rooted before, but when I was finished with it it was stock, I even locked the boot loader again (it was locked before I started flashing it)
Click to expand...
Click to collapse
How much did you pay for it?
Sent from my LG-H830 using Tapatalk

RidinNerdy said:
How much did you pay for it?
Sent from my LG-H830 using Tapatalk
Click to expand...
Click to collapse
I paid 4 for it...