Develop Bugs

big mistake updating to 2.2

ever since I updated to 2.2, no matter what rom I'm using..performance has been so poor compared to 2.1. I wish I never updated. My battery runs out quick, temperature goes up to 100F even when idle and my phone hangs every time I turn on wifi. Hopefully I find out a solution soon, i've been flashing and uninstalling roms all day these past two days. I love the phone though don't get me wrong =\

That sounds quite odd.
Are you using an unmodified SBF, or are you using a release where the author/publisher has made a lot of changes? When having problems, it may be best to stick to one release and try to narrow down your problems, instead of trying many different releases and introducing new variables into the mix.
Are you overclocking your phone - perhaps it's causing the rise in temperature? Or are you running a lot of widgets? There may be some widgets that use the system too aggressively, causing too much strain/heat.

Hi! Did you do "wipe" before and after flashing?

That is very odd. I am on Froyo and performance has been phenomenal ever since the flash.
I agree with naenee, check the ROM you're flashing...

i flashed the UK 3.4.2-117 and right now using Pay's 2.1 rom. I remember that I did wipe data/cache before flashing and after flashing. IDK, im just not having problem's with this particular rom..it seems like it happens on all the other ones im trying. I get random freezes and especially when I toggle on wifi. I recently installed setVEL and will see if battery improves, this means i don't need milestone right? I'm also using setCPU.
I might try to flash 3.4.2_131-003 PL version. Will it cause any trouble and can I go back down to UK 3.4.2-117?

Seeing as it uses the same kernel, you should be able to do so...
bkuu said:
I might try to flash 3.4.2_131-003 PL version. Will it cause any trouble and can I go back down to UK 3.4.2-117?
Click to expand...
Click to collapse

I have been using the orange 2.2 for several days and no specific problem is noted.

well I reinstalled pays rom first and everything is working good. No more hang ups or freezes but I still can't get the battery to last as long.My phone is mostly idled, running on 2G, just one widget, and everything in settings turned down to the least minimal settings..im talking about battery saver, screen brightness all the way down..everything off! 6 hours in and im already on 70%. I can live with that but I'm using setVsel and I know it could do better. Anyone know another way I can make my battery last longer?

I'm running Pays latest rom based on the UK 3.4.2 and it runs great. I'm also using setvsel (as every defy user should) and optimized all my vsels ([email protected], [email protected], [email protected]) using stability test. I haven't had a 'normal' day of use yet, but with heavy use (installing apps, web browsing, flashing rom) I've gotten at least a full day (~15 hrs) out of a charge.
I recommend minimizing your vsels using setvsel, then judging your battery life. Check out the setvsel thread for more help.
Sent from my MB525 using XDA App

And remember this is a smart phone, some people report getting 2 to 3 days of use out of it. That's basically idle time tho. These new smart phones are just that, and use much more battery than the Dumbphone.

Dewman4life said:
And remember this is a smart phone, some people report getting 2 to 3 days of use out of it. That's basically idle time tho. These new smart phones are just that, and use much more battery than the Dumbphone.
Click to expand...
Click to collapse
Even if that's the case (and I dispute it, I use my phone a fair amount in the ~3 days the battery averages), it still doesn't explain why the OP's phone is dropping 30% in 6 hours while idling.

When I updated to froyo, my battery life went from about 15 hours of use to 21 hours between charges. So I'm thinking the op has an app doing the draining.
Sent from my MB525 using XDA App

Unfortunately, this is a characteristic of Android.... Ridiculously inconsistent in the battery department.

Wife's phone is on official froyo, has been amazing since updated (a few weeks ago) but since yesterday some weird reason it's been super glitchy and freezing up. Not sure why...haven't changed anything to it and she's only downloaded an app or two (such as pandora) in the last couple days...I was playing around with it trying to figure out what was up...can't figure it out. I went into titanium backup to freeze some apps thinking maybe some blur crap was freezing it up but TB froze up so I can't even get in there. Also, same as OP, the battery has been heating up really quick lately, especially when on wifi.
Not sure what's up here...but I'm hoping nothing serious! Will keep you all updated on this...we'll see if there is a trend going on here.

bkuu said:
ever since I updated to 2.2, no matter what rom I'm using..performance has been so poor compared to 2.1. I wish I never updated. My battery runs out quick, temperature goes up to 100F even when idle and my phone hangs every time I turn on wifi. Hopefully I find out a solution soon, i've been flashing and uninstalling roms all day these past two days. I love the phone though don't get me wrong =\
Click to expand...
Click to collapse
check your cpu usage... if it's constantly arround 99%, you may experience the "usb-plug/unplug"-bug.
try enabling usb debug and restart your phone.

hah2110 said:
Unfortunately, this is a characteristic of Android.... Ridiculously inconsistent in the battery department.
Click to expand...
Click to collapse
I would rather say it is a characteristic of people using android, to have widely different usage patterns, causing differences in how long a charge lasts for each.

Hi there. Have you tried to recalibrate the battery? There is an app on the marke called Battery Calibrator. From what I understand if you play with roms the battery can give you problems so it need to be calibrated again. I hope this can help.

For those interested... I'm having a problem, I don't know yet if it's a bug or a hardware defect.
My phones wastes A LOT of battery while it should be suspended.
I've tracked the problem to, apparently, Motorola's SIM driver. From what I've discovered so far, the SIM isn't accepting the suspend state and therefore the "suspend" process uses too much CPU time... all of this when the phone is, supposedly, saving battery.
As I can't get a motorola engineer involved, I can't say for sure if this is the true cause... but it's the closer I've got to a diagnostic, so far.
Your problem might or not be related to this, but if you're interested about what I've found or what my kernel log looks like so you can compare with your own problem... this is the thread at motorola's owner forum:
https://supportforums.motorola.com/thread/47721

So is it just my epic?

So no matter what rom i load on my phone i get the same thing.... it will not wake up and i have to remove the battery. Now on stock its fine! but any rom.. and yes i have tried them.. numerous times.. Right now i have AOSP genocide 2 and its working the best. I can go 4 or 5 hours before i need to do a battery pull (sometimes). This morning i have had to do i battery pull twice but now it seems to be fine.
Now its not over clocking that is doing it. I have been all through that. My phone blazes when at 1.3ghz but will not turn back on ever with out a battery pull. right now there is no overclocking and voltage control is denied root. This seems to be working the best.
I really want something besides the stock rom. mainly because my phone is snappier and the battery life is wayyyyyyy better. So is it just my phone? Should i bring it into sprint and get a new epic?

NissanNick said:
So no matter what rom i load on my phone i get the same thing.... it will not wake up and i have to remove the battery. Now on stock its fine! but any rom.. and yes i have tried them.. numerous times.. Right now i have AOSP genocide 2 and its working the best. I can go 4 or 5 hours before i need to do a battery pull (sometimes). This morning i have had to do i battery pull twice but now it seems to be fine.
Now its not over clocking that is doing it. I have been all through that. My phone blazes when at 1.3ghz but will not turn back on ever with out a battery pull. right now there is no overclocking and voltage control is denied root. This seems to be working the best.
I really want something besides the stock rom. mainly because my phone is snappier and the battery life is wayyyyyyy better. So is it just my phone? Should i bring it into sprint and get a new epic?
Click to expand...
Click to collapse
Are these freezes ONLY happening when running o/c? If so, then your hardware might not like o/c speeds. Please clarify that it is not an o/c issue due to the information you provided above.
If you're stable and having no locking issues on stock, then flash ROMS/kernels and of the bat start boosting to o/c speeds then seeing instability, how/why are you ruling out it's not a o/c or hardware limitation?
NissanNick said:
I really want something besides the stock rom. mainly because my phone is snappier and the battery life is wayyyyyyy better. So is it just my phone? Should i bring it into sprint and get a new epic?
Click to expand...
Click to collapse
I don't think sprint will swap your phone out just because you can't manage stable o/c speeds on your phone. LOL

Sounds like you need to do the classic Wipe 3X before flashing.

Sorry guys i should have been more clear. I am not a noob i always wipe 3x. It is not a O/C issue. I have gone through all the clocking and my phone just does not like it.. I can live with that. What i am saying is even when not O/C and denying all access from anything that could effect my processor the ROM's Still don't work right. They freeze even with NO O/C at all! Every one of them. So i am thinking i just got the bad end of the silicon?
Also i relies Sprint will not just exchange my phone.. But im sure i could come up with something lol.
Well i really like my epic but i am thinking of switching to the photon if i cant get the ROMS to work right. I really wanted to wait until next year to upgrade.

NissanNick said:
Sorry guys i should have been more clear. I am not a noob i always wipe 3x. It is not a O/C issue. I have gone through all the clocking and my phone just does not like it.. I can live with that. What i am saying is even when not O/C and denying all access from anything that could effect my processor the ROM's Still don't work right. They freeze even with NO O/C at all! Every one of them. So i am thinking i just got the bad end of the silicon?
Also i relies Sprint will not just exchange my phone.. But im sure i could come up with something lol.
Well i really like my epic but i am thinking of switching to the photon if i cant get the ROMS to work right. I really wanted to wait until next year to upgrade.
Click to expand...
Click to collapse
It's not the overclocking that causes your phone to go into sleep of death, it is the low end. 100 Mhz causes sleep of death on a lot of phones on a custom ROM. Set your minimum frequency to 200 Mhz and you will be fine. Don't change any of the stoick voltages.

Try using stock speeds (400-1000). Then work your way incrementally in both directions to see which frequency(ies) cause your issues. Each phone is unique, so find the sweet spot.
I get the black screen of death about twice a month running twilight 1.1.1. My phone runs 200-1000 with no undervolting and set on conservative. I'm just too lazy to bother playing with settings since I'm holding out for SRF 1.3 to release.

Puzzling Random Reboot Issue

I've been trying to figure this out for months and have had no luck so I wanted to see if any of you had any recommendations.
I used to run Sense roms like the stock one and the sense 2.1 mctwist rom and they had no issues.
When CM9 came out, I decided to switch over to that. It functioned fine except I would get random reboots about 1-2 times each day. Tried clean installs, etc but nothing work.
Then CM10 came out and I upgraded. Once again, it works excellent except I still get random reboots once or twice a day.
And just recently I tried the AOKP Jelly Bean ROM, hoping it was a CM issue, but I also got the random reboots on AOKP.
What could be causing this? Occasionally I can go through the day without a reboot, but 9 out of 10 times, I get at least one reboot each day. Sometimes it happens while it's in my pocket and I don't even notice for a few hours.
These reboots are basically the phone starts showing the boot animation, but with a very dim screen and it just stays stuck with the spinning boot animation. It won't reboot until I pull the battery or do the 3 button reset.
Any advice? Should I try a different radio or...? I don't even know. I love JB so much so I'd hate to have to go back to a sense rom, but I can't take these reboots anymore.
Thanks

jpzsports said:
I've been trying to figure this out for months and have had no luck so I wanted to see if any of you had any recommendations.
I used to run Sense roms like the stock one and the sense 2.1 mctwist rom and they had no issues.
When CM9 came out, I decided to switch over to that. It functioned fine except I would get random reboots about 1-2 times each day. Tried clean installs, etc but nothing work.
Then CM10 came out and I upgraded. Once again, it works excellent except I still get random reboots once or twice a day.
And just recently I tried the AOKP Jelly Bean ROM, hoping it was a CM issue, but I also got the random reboots on AOKP.
What could be causing this? Occasionally I can go through the day without a reboot, but 9 out of 10 times, I get at least one reboot each day. Sometimes it happens while it's in my pocket and I don't even notice for a few hours.
These reboots are basically the phone starts showing the boot animation, but with a very dim screen and it just stays stuck with the spinning boot animation. It won't reboot until I pull the battery or do the 3 button reset.
Any advice? Should I try a different radio or...? I don't even know. I love JB so much so I'd hate to have to go back to a sense rom, but I can't take these reboots anymore.
Thanks
Click to expand...
Click to collapse
It could be an app causing it, or overheating. Do you over/under clock/volt? You may want to try underclocking a little, or raising the voltage a little. You may also want to check the system and kernel logs to see if they reveal the issue.

cmlusco said:
It could be an app causing it, or overheating. Do you over/under clock/volt? You may want to try underclocking a little, or raising the voltage a little. You may also want to check the system and kernel logs to see if they reveal the issue.
Click to expand...
Click to collapse
I used to overclock on my sense roms with no issue. But on CM10 I just have it set to stock speeds with no overclocking or adjusting the voltage. Could my phone be getting old and so even stock speed is causing overheating? My phone doesn't feel noticeably hot, unless it gets stuck in one of these reboots. Then it feels rather warm. What would you recommend I change my voltage to?
And I tried doing logs but they get wiped when I restart
EDIT: Odd thing I just discovered. I borrowed my friend's seido extended battery for the dinc and popped it in my phone. After charging it up for a bit, I used the phone and within 10 minutes it started acting weird and rebooted. And after restarting, it rebooted again a few minutes later. So basically it was even worse. Any correlation here? Does the extended battery = more heat = that's why my phone is rebooting?

It's hard to even guess unless you can get a log. If you give one of the stock based ROMs another trial for a few days, and the phone does not reboot, then it is safe to say it is not hardware. I'd start by at least ruling out the hardware possibility.
Do not use Titanium or some other app to restore any sort of data from one ROM to another. That often seems to cause a lot of people problems.
If your phone isn't that hot, I agree that heat isn't likely the problem. Mine absolutely roasts while navigating (while charging, screen on, gps and 3g antennas on, music playing, overclocked, weak original stock battery, otterbox case so it can't breathe, etc.) and it doesn't ever reboot from heat.
Everyone uses their phones differently. So what may be stable for one person might not be for others. I've come to the conclusion that there is only one person who can determine if a ROM is stable... that is the one person who uses it everyday. Just because some other people are using a ROM and getting good results, it doesn't mean that you ever will (even with you wiping/flashing/installing apps by the book).
CM9, CM10, or any and all ICS and JB roms are going to have things that aren't working right for some time still. It's just the nature of the beast. App compatibility, especially, is just one of those things. It's a testament to how good those awesome devs are that anything works on our Dinc running JB and ICS.
I never ran the ICS and JB ports for long (in fact only very short periods of time) because my problems far outweighed the benefits. There is no shame in GB working better for you. I run a variant of CM7 (which is gingerbread)... it is definitely different than stock-sense. Then I use alternate launchers (Go launcher is my favorite) to change it up even more. You can do so much customization that isn't dependent on the ROM. Then I can use something like ROM TOOLBOX PRO for even more customization.
Software is not fashion. What actually works never goes out of style (despite what the hipster kids on xda might be saying ...get off my lawn... grumble...)

jpzsports said:
I used to overclock on my sense roms with no issue. But on CM10 I just have it set to stock speeds with no overclocking or adjusting the voltage. Could my phone be getting old and so even stock speed is causing overheating? My phone doesn't feel noticeably hot, unless it gets stuck in one of these reboots. Then it feels rather warm. What would you recommend I change my voltage to?
And I tried doing logs but they get wiped when I restart
Click to expand...
Click to collapse
I would use incredicontrol and raise all max voltages by 25 or one push of the plus button. Sometimes as phones get older the processors get worn , and have issues with not enough power or even with the stock max frequencie of 998mhz. If raising the max voltage dosent help, i would underclock down from max 998.

Thank you both for the replies. I really appreciate it. I'll try overvolting and see how it goes tomorrow. If I still get reboots, I'll try running a stock rom for a few days and see how it performs.

jpzsports said:
Thank you both for the replies. I really appreciate it. I'll try overvolting and see how it goes tomorrow. If I still get reboots, I'll try running a stock rom for a few days and see how it performs.
Click to expand...
Click to collapse
Pardon me harping on my pet issue, but my phone does that if I underclock the CPU minimum to 128MHz. If I leave it at 245 I can go for days on end (I've seen uptimes of over 200 hours). For whatever that's worth...

musical_chairs said:
Pardon me harping on my pet issue, but my phone does that if I underclock the CPU minimum to 128MHz. If I leave it at 245 I can go for days on end (I've seen uptimes of over 200 hours). For whatever that's worth...
Click to expand...
Click to collapse
That is true, if i go down to 128 i have screen on freezing issues, and random reboots.

EDIT: Odd thing I just discovered. I borrowed my friend's seido extended battery for the dinc and popped it in my phone. After charging it up for a bit, I used the phone and within 10 minutes it started acting weird and rebooted. And after restarting, it rebooted again a few minutes later. So basically it was even worse. Any correlation here? Does the extended battery = more heat = that's why my phone is rebooting?
Click to expand...
Click to collapse
This is certainly a clue... but I don't know what it means...
I would not think the the extended battery would produce more heat. Since both batteries should be discharging at the same rates the heat output should be the same (just that the bigger one would take longer since it has more reserve). I've ran across stories of people who had phones that went completely wonky when they tried swapping batteries or getting a new one. I really don't know anything about it, I'm still on my stock battery.
It certainly couldn't hurt to try wiping your battery stats in clockwork. There is apparently some magic methodology to do it "correctly". I don't know about that either... here is a thread.
http://forum.xda-developers.com/showthread.php?t=1359395

Well just as an update, I tried the overvolting and clearing the battery stats but still got the reboots. I installed one of the Stock Sense ROMs and it's been running great with no reboots. Apparently my phone just doesn't like non-Sense ROMs for some reason. Oh well. At least I have a working phone. Pretty amazing how fast the stock rom runs!

Well, I guess it's good to hear the hardware is ok.
You still could try out the CM10s (or other JB roms) by starting off without installing your apps (if you can live without them). App compatibility might be your problem. Let it run for a while with no additional apps added. Then, add them back slowly (one or two a day or every couple of days) from the market only. If the reboots start up later on... you will probably recognize the one that is the source of trouble.
Of course you still have plenty of options in the gingerbread family to choose from. If you've never tried out some GB AOSP/CM roms, that would be worth a try. You've got stock roms, stock roms with sense removed, and the whole variety of AOSP/CM7 (official and unofficial) to choose from. Launchers...themes... mods... etc... all kinds of ways to change from whatever you start with. The only GB roms that I ever had problems with were the official "stable" CM7.0 and CM7.1 ROMs. I've been running one unofficial CM7 build (about 99.99% of the time...except to test drive newer stuff) for almost a year. Its been the best thing that's ever happened to my phone.

[Q] random reboots in every ROM lg nitro hd i

Hi Guys
Well i have install several ROMS wich as HO!NO! full throtlle, Cyanogenmod 9 an 10 stables and Nigthly edition, JellyBam and others that i not even remember and all of them always in some point they just reboots and im really hate it. I use wakelocks app and it works for a few days but eventually it reboot and he battery drain really fast, 8hours in EDGE and just a little chatting on whatsapp and a few calls.
i always wipe system, datvilks etc, im kind of new on this stuuuf but i think im doing it correctly.
Im starting to think that maybe its a hadware problem. Onces i ask some crappy tech gay in a store and he told me that i should buy another battery i dont know why, i thought that he just want to sell me the battery but i dont know.
Can anyone help me or recomend a ROM or something?
I just want a ROM that doesnt reboot and good battery life and i can do normal stuff. i dont care about overclocking or anything like that,
Thanks in advance

I would install a stock rom, either stock AT&T gingerbread or ICS for the Nitro and see if it still reboots. If it does, I think you have a hardware problem.

itiskonrad said:
I would install a stock rom, either stock AT&T gingerbread or ICS for the Nitro and see if it still reboots. If it does, I think you have a hardware problem.
Click to expand...
Click to collapse
I would go here first: http://www.att.com/esupport/article.jsp?sid=KB413885&cv=820
This will make sure you are 100% stock. Then if you are still having issues you know that it is a hardware problem. Just make sure you do a full wipe after install.
Sent from my LG-P930 using xda app-developers app

Sparcots miui ics port is the only rom that has zero bugs, black screens, or reboots for me. I've tried everything else.
Sent from my LG-P930 using xda app-developers app

Another potential issue is your SD Card.
I've also noticed lately that my Nitro sometimes randomly reboots. I run with the CM10 Nightlies. The other day, after installing a new nightly, it was really bad, almost constantly rebooting. I took out the battery, removed the SD card and let it sit for awhile (like 1/2 hour or so). Then I put everything back together, reinstalled the nightly and it's MUCH MORE stable now (still randomly reboots, but the instances are much less).
Give that a try and see if it helps at all.
Good luck!

Hi All!
I have LG P936 Optimus true hd with vodafone v20c firmware.
It`s regularly several spontaneous reboots per day. I saved logs with one reboot
03-13 17:03:41.993 F/libc ( 417): Fatal signal 11 (SIGSEGV) at 0x00000001 (code=1)
03-13 17:03:42.404 I/DEBUG (10445):
Click to expand...
Click to collapse
how it can be solved? Help please!

My solution has been to just stick with Gingerbread.. No rebooting, good battery life even with the stock battery, runs all the apps I need.
I do miss ics/jellybean, but I rather have a stable phone with great battery life than a pretty, unstable bleeding edge phone.
If anyone wants to build an awesome gingerbread/ics hybrid.. Then I am down. Lol.
Sent from my LG-P930 using xda app-developers app

Can you tell what happened based on the logs?

two P930s (NItro HD), one with hardware issues
I have two P930s. One of them is much more sensitive to ROM settings and I find I need to limit the CPU to 1200 Mhz or so to prevent random reboots.
The other one works well at full 1500 Mhz speed. This particular model seems to have inconsistent hardware build quality. It makes me reluctant to try any other LG devices (a relative has an LG dishwasher that has also been troublesome, with random shutdowns and error codes).

possible causes
1 - bad sd card
2 - bad flash
3 - unstable recovery .
for me , i have noticed the same , and found it fixed once i upgraded my recovery

1 - bad sd card
its rebooting without sd card
2 - bad flash
its rebooting on two v20c firmware what I used
3 - unstable recovery .
I use official kdz firmware only, not cwm

I' ve got the same problem. I've changed the sd card but it didn't work.

Similar issues here with a Nitro that a friend let me borrow while I'm waiting for parts for my other phone. Random reboots on several different ROM's including stock.
I'm going to try Kernel Tuner and up the voltage a little and see if the phone is more stable. wistlo mentioned limiting the CPU to 1200 Mhz and I think he may be on the right track. If the processor cannot handle being clocked to 1500, which is stock, then a common method (at least with PC's) is to either lower the Mhz or increase the voltage. Or both.
I just tried this a few minutes ago and I'll report back later.

budroid said:
Similar issues here with a Nitro that a friend let me borrow while I'm waiting for parts for my other phone. Random reboots on several different ROM's including stock.
I'm going to try Kernel Tuner and up the voltage a little and see if the phone is more stable. wistlo mentioned limiting the CPU to 1200 Mhz and I think he may be on the right track. If the processor cannot handle being clocked to 1500, which is stock, then a common method (at least with PC's) is to either lower the Mhz or increase the voltage. Or both.
I just tried this a few minutes ago and I'll report back later.
Click to expand...
Click to collapse
My phone was still unstable. I decided to try a stock Gingerbread ROM and it seems to run very, very well.

budroid said:
My phone was still unstable. I decided to try a stock Gingerbread ROM and it seems to run very, very well.
Click to expand...
Click to collapse
Yeah, i remember downgrading to GB to root, didn't use it muchzbut it never once rebooted.
Bought mine last week on ebay brand new (packages sealed and everything), i let it fully charged and started using it.
Came with stock ICS and has been constantly rebooting for the past week.
If i didn't live overseas and didn't have to pay so much money to clear through customs here i would have returned it, but i'm stuck with it and searching for help.
Funny thing is i've gamed on it for hours straight and stability tests for more than 2 hrs and it never rebooted. Then i'll whip out the keyboard to type a message or install an app on play store...or simple web browsing and BAM!....reboots
I've changed to 3 SD Cards even tried without it, still reboots.
All wireless signals off, reboot.
Different ROMS/Kernels, factory reset/wipe, Battery cover off, diff. governors I/Os, Underclocks & Overvolts, tried it all....except going back to GB.
It kind of irks me to know that i came from a GB phone to upgrade to a "new" phone that can only run on GB stable.
It always crashes during some really "stressLESS" stuff, lol. CPU scaling problem maybe?
Also, with no SD Card installed and on boot i get a "SD Card damaged. Try Reformatting" error. Is it normal to get this error with no SD installed?

squatch04 said:
...
Funny thing is i've gamed on it for hours straight and stability tests for more than 2 hrs and it never rebooted. Then i'll whip out the keyboard to type a message or install an app on play store...or simple web browsing and BAM!....reboots
...
Click to expand...
Click to collapse
This definitely makes me think you've got a CPU scaling problem. If you're doing something consistent, like playing a game or stress testing...The CPU will likely stay at a single frequency...But in your case, once you start doing some other activity (which very likely caused a CPU frequency change), the reboot occurs.
Definitely try installing SetCPU and set both the minimum and maximum frequency to something midrange, like 1.2GHz. This way you're locking the phone to a single value (no scaling) and not the max frequency so you won't overload it. Then do what you usually do when it reboots and If the phone stays stable, you'll know the problem is likely an issue with CPU frequency scaling. If it still reboots, at least you've removed one possible reason from the list.

Namuna said:
This definitely makes me think you've got a CPU scaling problem. If you're doing something consistent, like playing a game or stress testing...The CPU will likely stay at a single frequency...But in your case, once you start doing some other activity (which very likely caused a CPU frequency change), the reboot occurs.
Definitely try installing SetCPU and set both the minimum and maximum frequency to something midrange, like 1.2GHz. This way you're locking the phone to a single value (no scaling) and not the max frequency so you won't overload it. Then do what you usually do when it reboots and If the phone stays stable, you'll know the problem is likely an issue with CPU frequency scaling. If it still reboots, at least you've removed one possible reason from the list.
Click to expand...
Click to collapse
It was suggested in another thread that setting the governor to conservative 486 min 1404 max fixed the BSOD, so I tried it and haven't had a single reboot since I posted the last time. I was lucky if I got 30 min before trying it out.
I agree with you, definitely seems to be CPU scaling issue.
Conservative gradually increases the speed compared to the massive min to max spikes you'd get with ondemand.

I will try that with CM10.1 Rc2 with Wind Kernel. I got a few reboot when using my Calendar app for example, while low on battery.
Sent from my LG-P930 using xda app-developers app

radhames562 said:
Can anyone help me or recomend a ROM or something?
Click to expand...
Click to collapse
Try one thing: buy you a new microsd card and see if it helps

salimbaba said:
for me , i have noticed the same , and found it fixed once i upgraded my recovery
Click to expand...
Click to collapse
Tell me, plz, how can I do that? Now I have old 5.8.0.2 recovery. But since I dumped old 8Gb Sandisk and inserted 16Gb Sandisk I now had no reboots. But I want new recovery nonetheless

Battery overheating / draining

There is something going on with my phone, Samsung Galaxy S3, V4.3 where occasionally, lately it has been once a day the power draw from the battery will spike as high as 2,000ma (2 amps). This last long enough to drop the charge 10 - 20% and creates excessive battery heat. It happens on charge or off charge. I have tried viewing the running processes with System Tuner and nothing shows up in the list using an excessive amount of CPU. Better Battery Staus also doesn't pinpoint the problem. I have most everything Greenified accept Google stuff of course and useful stuff like email, etc. I now believe it could be connected with GPS since I turned off the GPS I have not had another event other than a 800ma spikes that quickly go away. Need more time to confirm it is GPS related. Are there any programs that will log which applications are using GPS? Any other ideas what could be the problem? I don't understand why System Tuner doesn't show me which process is eating the battery? Can anyone point me in the right direction.

I thonk it may be the radio itself. I have recently noticed similar issues on mine but its usually when streaming videos. I rarely use gps so i cant speak on that right now.
If i have it plugged in while doing this, it gets hot enough to trigger a shutdown due to thermal event....it crashes!

DocHoliday77 said:
I thonk it may be the radio itself. I have recently noticed similar issues on mine but its usually when streaming videos. I rarely use gps so i cant speak on that right now.
If i have it plugged in while doing this, it gets hot enough to trigger a shutdown due to thermal event....it crashes!
Click to expand...
Click to collapse
Same here, I also noticed with System Tuner that several applications that normally use 1% or less of CPU seem to spike to 8 - 30%. This all seem very odd. Now I am wondering if the background radio steals CPU cycles and leaves no time for normal applications. Anyway, the issues are reduced with GPS off although the battery does get warm sometimes without any reason I can fine. I'll try streaming audio and see if it triggers.
I would be willing to try a different radio. My current software is Model Number SGH-T999, Android version 4.3, BaseBand version T999UVUENC2, Kernel 3.0.31-1962493, Build number JSS15J.T999UVUENC2.

Unfortunately, no other radio will work. You can try one just to be sure about it. It wont brick, but just wont function. Youll have unknown imei and baseband until you flash the NC2 modem back.
Im currently running my port of S3Rx 4.0, but ill flash back to NC2 in a couple if days to test more on mine. Im also using a case/housing not meant for the T999 so theres a good chance that is contributing to my problems though.

DocHoliday77 said:
Unfortunately, no other radio will work. You can try one just to be sure about it. It wont brick, but just wont function. Youll have unknown imei and baseband until you flash the NC2 modem back.
Im currently running my port of S3Rx 4.0, but ill flash back to NC2 in a couple if days to test more on mine. Im also using a case/housing not meant for the T999 so theres a good chance that is contributing to my problems though.
Click to expand...
Click to collapse
Okay, thank you for the replies. Please stop by if you learn anything new. Velis Auto Brightness is up to 64% CPU usage, grrr. I posted on developers forum maybe troubleshooting that will lead to a fix. The 2 amp spikes haven't occurred since I disabled GPS, so I am guess you are correct about the radio.

The problem returned so turning off GPS isn't a complete fix, seems to reduce the frequency is all. It looks like Android System is the problem. If I shut down pull the battery reboot the bad behaviour continues, only fix seems to wait it out. My next phone most likely will not be a sammy.

Im not really sure what to suggest at this point. I can say that what we are experiencing isnt typical though.
Out of curiosity, have you given any of the ported kk roms a try? I think my Sprint port is probably the most stable/bug free, but they are all good and ive had pretty good battery on each one compared stock. (Ive always had good battery life even on stock though, aside from a few recent issues that I believe are more my own fault). TMS3KK is a solid rom with very few issues. S3Rx 4.0 is as well, but ill be posting an update to it hopefully later today, so I cant say its really been thoroughly vetted yet. Still worth a look though, imo.

DocHoliday77 said:
Im not really sure what to suggest at this point. I can say that what we are experiencing isnt typical though.
Out of curiosity, have you given any of the ported kk roms a try? I think my Sprint port is probably the most stable/bug free, but they are all good and ive had pretty good battery on each one compared stock. (Ive always had good battery life even on stock though, aside from a few recent issues that I believe are more my own fault). TMS3KK is a solid rom with very few issues. S3Rx 4.0 is as well, but ill be posting an update to it hopefully later today, so I cant say its really been thoroughly vetted yet. Still worth a look though, imo.
Click to expand...
Click to collapse
No time to try a different ROM yet. I should have time the weekend after next. Thank you for all your suggestions.

I tried replacing the battery. After the first charge the phone lasted for 2 days before the battery dropped to 5%. It took 6 hours to charge back to 100%. No problems until later, it seems to dislike being unplugged moved to a new location and plugged in again. This appears to be when the problem occurs. I usually just leave the phone plugged in all the time. I'll test further with the power before I make up my mind. I think this will be the last Sammy phone for me?

Is it a non stock battery? I've always had issues with those reporting correctly.
Sent from my SAMSUNG-SGH-T999 using Tapatalk

DocHoliday77 said:
Is it a non stock battery? I've always had issues with those reporting correctly.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Usually I would buy a non stock battery however since this phone lays next to me in bed to wake me in the mornings I am a little concerned with a fire so it is a Samsung battery from Samsung. Leaving it unplugged for a bit and plugging it back in didn't work stop the battery drain. There are no processes eating the battery according to System Tuner so got to change the ROM.
Should I try a ROM first or kernel or both? Could it be an Xposed module, thinking about turning all of those hacks off?
I just remembered, this only happens if the screen is on and the phone is plugged into the charger. And rebooting doesn't clear the problem.

I would start with a stock based ROM. If it were me I'd go full stock rooted. But yeah I'd ditch xposed for now. You might even try reflashing your current ROM, factory resetting and this time don't use any exposed mods. If it still has problems, then try a different ROM.
It wouldn't surprise me at all to find xposed was the culprit. Its really cool, and the dev is amazing, but I prefer not to use it at all. IMO, it's much better to have the mods coded into the ROM itself.
Sent from my SAMSUNG-SGH-T999 using Tapatalk

DocHoliday77 said:
I would start with a stock based ROM. If it were me I'd go full stock rooted. But yeah I'd ditch xposed for now. You might even try reflashing your current ROM, factory resetting and this time don't use any exposed mods. If it still has problems, then try a different ROM.
It wouldn't surprise me at all to find xposed was the culprit. Its really cool, and the dev is amazing, but I prefer not to use it at all. IMO, it's much better to have the mods coded into the ROM itself.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Thank you Doc, will do so and report back here the results.

My phone does the same thing now. My phone never did this when I first got it a couple years ago. I use GPS a lot because son plays on a travel hockey team. I could drive 3 - 4 hours away with the phone on and plugged in using the GPS without any issues. Now, my phone gets so hot in about an hour of the same type of use and it shuts down.
I thought that maybe there was something wrong with the phone because of age but now I see it could be something different.

It very well could be age related, or it could be partially due to that too. But I'd do as I suggested above and run stock for a bit to test. If on a custom rom, and especially kernel, you could run into issues like that too.
If you have the same problem on stock, (and you're sure its not an app acting up), there's a very good possibility that its more of a hardware related issue.
Sent from my SAMSUNG-SGH-T999 using Tapatalk

And it is not the battery. I can't load stock until next weekend, need my phone for work.

You can always use better battery stats to investigate while you use it normally. Let it log all wakelocks, including kernel wakelocks for a full cycle.
Sent from my SAMSUNG-SGH-T999 using Tapatalk

DocHoliday77 said:
You can always use better battery stats to investigate while you use it normally. Let it log all wakelocks, including kernel wakelocks for a full cycle.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Tried that, been there, odd thing is nothing shows there. I'm gonna reload with stock per your suggestion next weekend and if that doesn't work I'll try a custom kernel.

Try remove greenify app and see what happens. Cuz with my case the latest version (2.4.x.x) of greenify driving my phone nuts. That app used to be great.

I'm back. Loaded stock 4.3 ROM / kernel, radio is at newest versions, I am going to say the problem is gone. The battery heats up to about 32-33 degrees Celsius however the phone isn't hot like it is burning up so I believe the problem is like Doc suggested earlier with the radio. Which would explain why the process monitors never see any rouge application using to much CPU. So after some pondering, this doesn't stop a rouge application from using to much bandwidth and cooking the radio so to type. If I had to pin it down I am going to suggest it maybe one of these two applications: FCC speedtest and or Opensignal or some other application. Both of the listed applications periodically test the network bandwidth and report back to a central server. I suspect that this maybe trigger the heat problem from the extend radio usage. No proof at this time just conjecture.
I am considering jumping to an AOSP ROM to be free of the Samsung bloat, NOT CM, don't care for CM, does anyone have any good suggestions to try?