Develop Bugs

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.

Black Screen of Death: ROM or Kernel Issue?

I just had my first Black Screen of Death requiring a battery pull. I don't know if it's a ROM or Kernel problem. I just flashed Liquid Smooth 1.5RC1 and the latest trinity. Not undervolted. I did a search, didn't find anything. Any ideas?

Amphibliam said:
I just had my first Black Screen of Death requiring a battery pull. I don't know if it's a ROM or Kernel problem. I just flashed Liquid Smooth 1.5RC1 and the latest trinity. Not undervolted. I did a search, didn't find anything. Any ideas?
Click to expand...
Click to collapse
Does this rom come stock with trinity kernel? If it does not and you flash it.. then it is normal, you are supposed to let the kernel sit and reboot after the phone is settled. Im not entirely sure what it is but i have to do it everytime otherwise i get what we called it back in my epic fourms "the dead hooker syndrome" where the lights would come on but the phone would be unresponsive.

No I flashed Trinity separately and ran it after several reboots and s**t for like 3 hours then this happened. I ran trinity before and never had this issue. My guess is that it's Liquid. For now, I shall observe and see if it happens again.

The ROM doesnt control the CPU .. the kernel does.. my guess is its a bad download or something is keeping it from coming out of deep sleep..

What is your minimum speed of the CPU? Anything below stock can cause issues.
Sent from my Galaxy Nexus using XDA

I'm running 307. I run 180 on IMO and Franco with zero issues, which is what I had used for a month.

Amphibliam said:
I'm running 307. I run 180 on IMO and Franco with zero issues, which is what I had used for a month.
Click to expand...
Click to collapse
It could be the fact that your phone just doesnt like Trinity... although we all have the same chipset... they arent all built to withstand the same conditions. Some handle more than others.

ÜBER™ said:
It could be the fact that your phone just doesnt like Trinity... although we all have the same chipset... they arent all built to withstand the same conditions. Some handle more than others.
Click to expand...
Click to collapse
What he said. Having your lowest frequency set at ~100, 300 regardless if it works on one particular kernel. Your phone might not like that kernel and cause it to not wake back up.
Best way to workaround it is just to simply boost your lowest frequency.... or just flash another kernel.

I would except Franco (m4/nightlies), IMO overheats my phone, PBJT fails at performance and battery, Popcorn is good, but I haven't tried the latest.

Amphibliam said:
I would except Franco (m4/nightlies), IMO overheats my phone, PBJT fails at performance and battery, Popcorn is good, but I haven't tried the latest.
Click to expand...
Click to collapse
I think kernels for sprint work for Verizon try samurai kernel in our forums. Its what I use or you could just flash faux kernel his is based on that.
Sent from my Galaxy Nexus using xda premium

[FIX] Pops and crackles in headphone output.

Hey everyone, just thought I would let it be known that (at least on my phone) overclocking past 1.8GHz causes horrible clicks and pops when listening through the headphone jack. I am using the Rogers Stock ROM with the latest KT747 kernel, and the issue appears when clocked to 1.89GHz, even though the rest of the phone runs stable. Took me a while to track down the problem!
I was hoping people with other kernels/roms/configurations could weigh in to see if this is an isolated or a widespread issue. For the time being I have just decided to overclock manually when it is needed.
EDIT: It appears after more testing that it was the kernel itself. Switching to stock kernel fixed the problem.

MatinatorX said:
Hey everyone, just thought I would let it be known that (at least on my phone) overclocking past 1.8GHz causes horrible clicks and pops when listening through the headphone jack. I am using the Rogers Stock ROM with the latest KT747 kernel, and the issue appears when clocked to 1.89GHz, even though the rest of the phone runs stable. Took me a while to track down the problem!
I was hoping people with other kernels/roms/configurations could weigh in to see if this is an isolated or a widespread issue. For the time being I have just decided to overclock manually when it is needed.
Click to expand...
Click to collapse
isn't your phone blazing hot to the hand?

Death&co said:
isn't your phone blazing hot to the hand?
Click to expand...
Click to collapse
Suprisingly the temperature increase is hardly noticeable. I tested while playing N. O. V. A. 3 and a few other games. My One XL got burning hot while overclocked to 1.7GHz, even though it's the same chip, which I find strange.

I had this probelm as well on my SGS3, ended up exchanging my phone for another reason and the new phone doesnt do it anymore.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

The galaxy s3 explodes with stock temps, I would be afraid to oc to 1.9GHz Oh, and I would edit the title from [FIX] it's kind of misleading since there isn't a fix here.

MatinatorX said:
For the time being I have just decided to overclock manually when it is needed.
Click to expand...
Click to collapse
I'm still trying to figure out when you would "need" to overclock.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

americasteam said:
I'm still trying to figure out when you would "need" to overclock.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
I'm a power user. I do just about everything with my phone, including lots of gaming with emulators. Perhaps I got a higher than normal quality chunk of silicon, but the phone didn't overheat at all, even when overclocked. The only time it got noticeably warm was while overclocked, gaming and charging all at once.
To those having this problem, it appears it wasn't related to overclocking after all, as the issue appeared a day later on stock frequencies. Changing back to a stock kernel fixed the problem.
In the end I sold it and bought an international SGS3 from eBay. I don't care for LTE, but the Wolfson DAC and Mali-400 GPU appeal to my usage case nicely.

MatinatorX said:
Perhaps I got a higher than normal quality chunk of silicon, but the phone didn't overheat at all, even when overclocked. The only time it got noticeably warm was while overclocked, gaming and charging all at once./QUOTE]
Seeing posts like this just make me cry inside...from the day I first got my phone and activated it, I have been having overheating problems. No one would take my device back so after my 30 day "return" period or whatever, I decided to root my phone to underclock/undervolt to solve my problem....but even know, my phone gets warm by just using stock Browser after a fresh install (not Chrome or anything else) WITH underclocking.
Click to expand...
Click to collapse

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