Related
CM6 is definitely great, I think without question it is a vast improvement.
The only issue I have is my battery life is ABSOLUTELY HORRIBLE. Could be the worst battery life I've had with any phone. But maybe that's just the EVO, with it's big screen and speedy processor. I underclock to 384 mhz sometimes but then the thing slows down and even freezes. I have 3 different batteries and they all perform about the same (not good.) Before I had a partial wake issue but that's gone, and battery life still stinks. I've also tried calibrating but nothing really seems to make it better.
I hear the snap thing is good for battery life but I everytime I open that thread I get a headache. I love this phone and am obsessed wtih it but that thread is a bit much even for me!
Can anyone give me a quick and dirty explaination of what snap is / how to use snap? Which kernel to flash? Some day I hope to digest that mammoth of a thread, but right now I'm too busy reading texts for college and Just want better battery life.
Thanks!
Download app System Panel. Will help show you what is eating up your battery/resources.
Then, download app Juice Defender. Worth it to get the paid version. Its like 3 bucks IIRC. This will help you get more battery life out of your phone.
-Sent from my Evo.
nyc_zx10 said:
Download app System Panel. Will help show you what is eating up your battery/resources.
Then, download app Juice Defender. Worth it to get the paid version. Its like 3 bucks IIRC. This will help you get more battery life out of your phone.
-Sent from my Evo.
Click to expand...
Click to collapse
Yeah, I tried System Panel but the things eating my battery were mostly system things, like Browser. I guess I could give it another go.
Why are Juice Defender reviews so bad? I've considered it before also, maybe will try playing with it again
snap 8.2 is the current release. you can try any of the kernels, but i would avoid the 7.0/7.1 SD Card implementations since that technology has been put on the back burner for a bit.
Snap allows you to you Overclock and Undervolt (aka: UV).
Overclocking of course is for speed and Undervolting may save battery.
all EVOs are not created equal. some like undervolting some do not. so snap is available in multiple flavors. each with a different UV floor. the lower the floor the more potential battery saving..but also the more chance for a random reboot or wifi/gps acting funny. remember UV retards the amount of power so things can act goofy. the different UV floors are 800mv - 925mv. for example...i use the 8.2_900 because it works well with my EVO. the 8.2_800 booted great but after a while started rebooting itself. 8.2_850 just hung at bootup. the 8.1 kernels didn't work for me at all. 7.3b1 was great.
HAVs is adaptive..so don't get stressed if your device fails to boot properly the first time. wipe the cache/dalvik and try again.
so download a few of the 8.2 kernels.
make your nandroid
begin trial and error (I'd suggest starting at 800, 850 then 900 to get a feel)
don't be afraid to wipe the Cache and Dalvik multiple times.
don't worry about the whole thread. just grab the last few pages and read the OP. then feel free to ask.
i also recommend setCPU. you can find some threads for SetCPU configurations to help. BUT....make sure SetCPU is disabled when flashing the new kernel. once you get a working kernel you can enable SetCPU...but during testing phase it will give you gray hair.
jmxp69 said:
Just a few quick thoughts on voltages/freqs after seeing a handful of discussion in the thread:
1) Every 8.2 kernel has voltages lower than stock. The default stock voltage @ 245 is something around 1050.
2) No real effort is made to UV at the top end. It's a little lower, but the objective at the highest CPU frequency is not to UV. Most of the benefit of UV comes at the low end of the scale when your phone is idle (most of the time). Less voltage = less draw.
3) nHAVS scales voltage at each step. There is a min.max voltage at every cpu frequency. This range is fairly small--50-75mv, but it enables HAVS to decide based on feedback from the CPU which one to apply. And the max at each step is lower than stock. So no matter how you slice it, even if you're running 925, you are undervolted. This becomes a question of how undervolted.
4) OC is not about undervolting, it's about overclocking. The differences is voltage vs. frequency. OC means we're increasing the CPU frequency beyond stock which is 998mhz in the case of Evo. If you move your SetCPU slider beyond 998mhz, you're overclocking.
The objective of overclocking is speed. The objective of undervolting is battery savings. Snap gives you both. We overclock when we increase the fequency with SetCPU. We undervolt automatically via nHAVS. As of this writing, UV is handled in the kernel, it happens most at the bottom end of the frequency scale.
I hope this helps clear up some of the questions. Great conversation by the way.
Click to expand...
Click to collapse
GREAT EXPLANATION Dragin!!!
and also, to the OP.... dont forget, if you do go with setcpu, do NOT 'set on boot' mmmmkay??? lol
Thank you Dragin!!!
That helps a lot! So once you have Snap setup at what you feel is "good" does your phone seem to perform as well as before you had it undervolted? Man, sounds like a pretty involved process - maybe I better wait until I can really sit down and play with it.
goodelyfe said:
GREAT EXPLANATION Dragin!!!
and also, to the OP.... dont forget, if you do go with setcpu, do NOT 'set on boot' mmmmkay??? lol
Click to expand...
Click to collapse
Do you mean for the first flash? Or every time you boot your phone?
If not set on boot, it means you have to start SetCPU manually after each boot. Doesn't seem right
Sent from my PC36100 using XDA App
foueddyf said:
Do you mean for the first flash? Or every time you boot your phone?
If not set on boot, it means you have to start SetCPU manually after each boot. Doesn't seem right
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I think he's talking about when ur figuring out the best setup
Regarding Juice:
I didn't really read too much into the reviews for this particular app. It works. I was having battery issues. Downloaded Juice, got the settings somewhat right to my liking and so far no complaints. Unplugged my phone from charger this morning at roughly 9am, been using it moderately all day, and as of right now at 12:50am, I am at 29%.
Bad reviews or not, I can attest to it working and making a difference in battery life.
Sent from my PC36100 using XDA App
I had the same issue, left to stock with kingx.
Sent from my PC36100 using XDA App
nyc_zx10 said:
Regarding Juice:
I didn't really read too much into the reviews for this particular app. It works. I was having battery issues. Downloaded Juice, got the settings somewhat right to my liking and so far no complaints. Unplugged my phone from charger this morning at roughly 9am, been using it moderately all day, and as of right now at 12:50am, I am at 29%.
Bad reviews or not, I can attest to it working and making a difference in battery life.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Do you know what in particular Juice is doing to give you better battery life? like what does Turn off certain things based on conditions or?
That is some good battery life.
Correct.
You can set conditions to do certain things. Such as disable data/3g/wifi while screen is off. Also if you need data synced you can set a condition to enable data wifi or 3g for X minutes every X minutes/hours.
I am not affiliated with the dev in anyway but it def made a difference and was worth the price for it.
Sent from my PC36100 using XDA App
nyc_zx10 said:
Correct.
You can set conditions to do certain things. Such as disable data/3g/wifi while screen is off. Also if you need data synced you can set a condition to enable data wifi or 3g for X minutes every X minutes/hours.
I am not affiliated with the dev in anyway but it def made a difference and was worth the price for it.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Meh... see I really don't want to do those things. I can turn off data sync myself and just have gmail forward me a text message when I have an email. I just was hoping there was a way to get decent battery life without going back to the days of Winmo
I absolutely adore CM6, but I'm really starting to think that it is not battery friendly. Last night my battery went from full to 25% in 8 hours. I had nothing running, my partial wake was fine, and Android system took up 60%+. I really don't feel like doing another wipe, but it looks like I may have to. Just want it to work right at this point.
Again, I truly love CM6, the open source concept, the transparency, the whole clean idea of it, but there is something seriously wrong with the battery life (at least in every install I have tried)
berardi said:
I absolutely adore CM6, but I'm really starting to think that it is not battery friendly. Last night my battery went from full to 25% in 8 hours. I had nothing running, my partial wake was fine, and Android system took up 60%+. I really don't feel like doing another wipe, but it looks like I may have to. Just want it to work right at this point.
Again, I truly love CM6, the open source concept, the transparency, the whole clean idea of it, but there is something seriously wrong with the battery life (at least in every install I have tried)
Click to expand...
Click to collapse
i agree with you. but i also feel that CM6 is on par with the Official HTC/Sprint ROM when it comes to battery life expectancy. however, after i put on the snap kernel and copied someones setcpu config....i got 26+hrs of 'use it as i wish' time + still had about an hour of in-pocket time left. i was hooked. i bet you an imaginary dollar the same will happen for you.
as for finding your EVOs kernel made in heaven...
it's not too bad so long as you have some time. but if you are time strapped, need your phone in 20min and don't read the OP... you will curse and swear. expect to get hung up at the HTC splashscreen a few times and it will bootloop on you before your done. <I'd suggest just leaving your battery cover off until you are done muckn about for that session>
klick may be easier for the some end users because of fewer selections. I've never used his kernels. if i try them, i'll prolly wait till he's put out a few AOSP versions...to work out any bugs.
oh yeah...one odd thing, it seems that sometimes folks flash a incompatible kernel it gets 'stuck'. after that 'bad flash' they are unable to flash any kernel until after they have nandroided back and rebooted...then they can flash again. i had this happen twice....i was unable to get a known good kernel to load until after i restored from backup. /shrug
oh....try this. download the snap7.5_925 kernel. if it runs smooth. call it a day and you should be pretty happy with that until the new versions come out. yeah, if you got one of the _800 kernels running you may pull an extra 30-45min of time...but that requires a level of geekdom that not everyone has.
DraginMagik said:
i agree with you. but i also feel that CM6 is on par with the Official HTC/Sprint ROM when it comes to battery life expectancy. however, after i put on the snap kernel and copied someones setcpu config....i got 26+hrs of 'use it as i wish' time + still had about an hour of in-pocket time left. i was hooked. i bet you an imaginary dollar the same will happen for you.
as for finding your EVOs kernel made in heaven...
it's not too bad so long as you have some time. but if you are time strapped, need your phone in 20min and don't read the OP... you will curse and swear. expect to get hung up at the HTC splashscreen a few times and it will bootloop on you before your done. <I'd suggest just leaving your battery cover off until you are done muckn about for that session>
klick may be easier for the some end users because of fewer selections. I've never used his kernels. if i try them, i'll prolly wait till he's put out a few AOSP versions...to work out any bugs.
oh yeah...one odd thing, it seems that sometimes folks flash a incompatible kernel it gets 'stuck'. after that 'bad flash' they are unable to flash any kernel until after they have nandroided back and rebooted...then they can flash again. i had this happen twice....i was unable to get a known good kernel to load until after i restored from backup. /shrug
oh....try this. download the snap7.5_925 kernel. if it runs smooth. call it a day and you should be pretty happy with that until the new versions come out. yeah, if you got one of the _800 kernels running you may pull an extra 30-45min of time...but that requires a level of geekdom that not everyone has.
Click to expand...
Click to collapse
Thanks man, appreciate the breakdown.
You have inspired me, I'm going to bite the bullet and try this snap7.5_925 kernel. I'll report back my luck
I do enjoy this stuff, really - just right now it would be irresponsible for me to spend too much time on it. School comes first right now.
DraginMagik said:
... after i put on the snap kernel and copied someones setcpu config....i got 26+hrs of 'use it as i wish' time + still had about an hour of in-pocket time left. i was hooked. i bet you an imaginary dollar the same will happen for you.
Click to expand...
Click to collapse
Wow, I'd love to have that kind of time with CM6, right now I drain at about 10% an hour with no usage at all; where can I find that setcpu config? I really like CM6 but battery life is killing me right now.
loupy said:
Wow, I'd love to have that kind of time with CM6, right now I drain at about 10% an hour with no usage at all; where can I find that setcpu config? I really like CM6 but battery life is killing me right now.
Click to expand...
Click to collapse
Yeah dragin, don't hog those sweet settings! I'm enjoying Snap 7.6 and it seems to be helping out my battery life a bit, but I'd love to see your SetCPU details.
I've found that the issue for me is bluetooth. If I have it on constantly my battery will drain 10-15% per hour. With bluetooth off it's only draining 1%-2% per hour.
Seems like the bluetooth needs work on CM6 in order to have the efficiency that the other ROMs i've tried (Fresh and EViO) have. Nonetheless, I'm sticking with CM6 and just use the bluetooth when necessary.
I have the same issue with bluetooth on CM 6.0.0. I am running the stock kernel that comes with cyanogenmod, so this is definitely not a snap issue. There was a bug submitted about a month ago:
code.google.com/p/cyanogenmod/issues/detail?id=2136
I *really* hope this can get fixed for the 6.1 release, but it is currently listed with a low priority. I really love CM6, but basically making bluetooth unusable for more than a few hours really makes me struggle with the using this rom.
Why not the 7.6 with turbo...just wonderin
How fast can I overclock my chip to in my Rhod100 safely?
I'm using OCT I.5
CPUs are all different from on another. A "safe" speed for one person may not be for another. Best bet is to experiment by trying the next increment up, and test to see if there is any instability, SOD, etc. If everything looks okay, try the next increment up.
Some people on the overclocking thread seem to be having good luck at the lower-700s, with dynamic OC'ing turned off. I have mine set for the default 652 MHz setting (but with dynamic OC'ing off) just to be on the safe side.
You do not increase voltage, so overclocking to any value should be safe. In the worst case you just hang the device, but a softreset fixes this. I found the 710Mhz frequency to be 100% reliable.
Thanks Guys. Been a big help
i dunno, depends on software and rom. i personally do 768 no dynamic, all settings 0 at 1000ms on energy cookie 23138 sep 14. no reset needed for a month or so. and when it did it was user error lol.
but u just gotta play with it. expect to reset a few times. and id keep all settings on 0 at 1000 ms. just me.
Jackos said:
You do not increase voltage, so overclocking to any value should be safe. In the worst case you just hang the device, but a softreset fixes this. I found the 710Mhz frequency to be 100% reliable.
Click to expand...
Click to collapse
710 is the most reliable ive seen from public opinion
I did a bit of research and found out the chip is capable of 850mhz.
I've got mine running at 806.4 and seems to be runnning fine. I switched the stepping off. Feels awesome.
uncleswoop said:
i dunno, depends on software and rom. i personally do 768 no dynamic, all settings 0 at 1000ms on energy cookie 23138 sep 14. no reset needed for a month or so. and when it did it was user error lol.
but u just gotta play with it. expect to reset a few times. and id keep all settings on 0 at 1000 ms. just me.
Click to expand...
Click to collapse
How can no reset be needed for a month if your rom version is only 3 days old?
enahs_ said:
How can no reset be needed for a month if your rom version is only 3 days old?
Click to expand...
Click to collapse
i lol'd
enahs_ said:
How can no reset be needed for a month if your rom version is only 3 days old?
Click to expand...
Click to collapse
i meant from reset needed from sod's or other issues.
energy has been my rom of choice for quite some time. every version has been fully compatible for me with oct. thats what i meant to say
Can someone link to the overclocking software? I'd like to give it a try.
How about battery life and temperature? Does overclocking to 710 reduce battery life and increase the phone's operating temperature? If so, by how much?
gromky said:
Can someone link to the overclocking software? I'd like to give it a try.
How about battery life and temperature? Does overclocking to 710 reduce battery life and increase the phone's operating temperature? If so, by how much?
Click to expand...
Click to collapse
There Are 2 Overclocking Apps You Can Find Them
Here http://forum.xda-developers.com/showthread.php?t=725290
&
Here http://forum.xda-developers.com/showthread.php?t=698374
Does overclocking the phone kill your battery? I already only get two days of battery life.
Yes, I noticed decreased battery life with 710Mhz OC.
gromky said:
Does overclocking the phone kill your battery? I already only get two days of battery life.
Click to expand...
Click to collapse
I get three days with NRG ROM, but I have pretty light use. However with OC it is no worse than before.
Also using Energy ROM, have experimented overclocking at 650 MHz, and now 710 MHz for the past few days (based on suggestions in this tread, actually!). Haven't noticed a significant reduction in battery life. I get around 2 days also. 2 days has been pretty typical on the Rhodium for me, with the stock ROM and Energy, and moderate usage. Most comments on the main overclocking thread seem to indicate that battery life is not greatly reduced. Just anecdotal comments, of course. Don't think anyone has done any halfway scientific testing.
~8mA more during sleep
~40mA more during stress
That's why you don't notice a big difference during "normal usage". Try not to use the device for some days (I know it's hard ;D) with overclocking and without so you will notice the difference. Like I said in another thread: We do not measure the battery life while using the device - because this isn't measurable and doesn't give any reliable results.
It's like the percent battery driver - any clever person should notice that this cannot be described as precise.
Im using 787MHz dynamic oc with no problem at all. It doesnt seem to affect battery life either, but then again Im not using Sense.
Jackos said:
~8mA more during sleep
~40mA more during stress
That's why you don't notice a big difference during "normal usage". Try not to use the device for some days (I know it's hard ;D) with overclocking and without so you will notice the difference. Like I said in another thread: We do not measure the battery life while using the device - because this isn't measurable and doesn't give any reliable results.
It's like the percent battery driver - any clever person should notice that this cannot be described as precise.
Click to expand...
Click to collapse
I'm not exactly sure what point you are making. My observation is that with or without OC, the length of time my phone can be used before recharging is approximately the same, i.e., I don't detect any decrease in battery discharge.
Since my usage patterns are the same for both cases, this variable drops from the equation.
So, you need to run the program every time the phone boots? Or does the program remember its settings?
Yesterday I put the netarchy havs less kernel on my phone and with some stress testing and general testing found that it worked well at 1.15 mhz. I carried it around all day messing with it no problem. Today, the real test came when I ran GPS on my phone in my car. The phone lasted about 3 minutes of GPS before it started rebooting. Then my 4g was broke from it somehow. Anyhow, I restored my phone and all seems well now.
I still want to mod the voltage and clock speed. Any advice on this? The phone always gets hot when I use GPS because it uses a lot of processor, frequently its on the charger and possibly in sunlight. When it was not overclocked or undervolted my phone NEVER reboots not once since I've had it.
Is the problem the undervolting, overclocking or both? Should i give up on this due to the way I use my phone?
Thanks in advance.
Try different kernels. I use netarchy sbc 4.2.2 more havs, works great. I also use his 4.3.4 more havs sbc. They both work for me. Battery life is awesome and gps works good. No prob here. Try those out and see what happens. Hope this helps.
Sent from my HTC EVO Phone, should'nt we all have one?
Okay so is there any danger to this? It seems like every time my phone starts rebooting from overclocking or undervolting apps start disappearing from my phone and stuff stops working.
I use amon RA 2.3 and every time I recover it works again but I was just wondering how dangerous it is for me to experiment they way I have been. I have already recovered my phone 3 times from issues like this that broke it.
Every phone reacts differently to kernels, undervolting, and overclocking so you will have to experiment to find out what works for you and what doesn't. Just make sure that you dont check the "set on boot" box until you know your setup is stable. A reboot shouldn't hurt anything though.
I am running Netarchy 4.3.4 more havs, overclocked to 1190 and it's as stable as can be on my phone. However, if I go over 1190 it immediately locks up and reboots.
Sent from my HTC EVO 4G with Tapatalk
kd0axs said:
Every phone reacts differently to kernels, undervolting, and overclocking so you will have to experiment to find out what works for you and what doesn't. Just make sure that you dont check the "set on boot" box until you know your setup is stable. A reboot shouldn't hurt anything though.
I am running Netarchy 4.3.2 more havs, overclocked to 1190 and it's as stable as can be on my phone.
Sent from my HTC EVO 4G with Tapatalk
Click to expand...
Click to collapse
Yeah but the reboots are hurting my phone! I have to restore it due to the problems the reboots and freezing causes (sometimes I have to battery pull due to full lockup). 2 times when I pulled battery due to full lockup apps went missing from phone memory but the available space on the phone was as if the apps were still there. Another time my 4g wouldn't turn on.
Is that abnormal? Can it mess up my phone in a way that recovering wont be able to fix or is recovering generally a sure shot?
The reboots should not be hurting the hardware, unless you overclock excessively. What the reboots are doing is corrupting your file system because open files do not get closed properly.
Are you after speed or battery life? I think the two are mutually exclusive. If you have great speed (be it governor or because of overclock), you will pay the price in battery life. I think the trick is to find the balance between the two that suits *you*.
gpz1100 said:
The reboots should not be hurting the hardware, unless you overclock excessively. What the reboots are doing is corrupting your file system because open files do not get closed properly.
Are you after speed or battery life? I think the two are mutually exclusive. If you have great speed (be it governor or because of overclock), you will pay the price in battery life. I think the trick is to find the balance between the two that suits *you*.
Click to expand...
Click to collapse
Because I use the 1-1-1 power management system (see sig) my main concern is performance. I love my phone and when I use it I want it to be fast and smooth. I would *prefer* if the extra speed didn't dramatically change my battery life but I'm okay with a small decrease in battery life if the speed gain is reasonable for the tradeoff. Anyhow I thought a lot of people ran HAVS along with overclocking to have both to a degree.
Only time I charge my battery is when I am using it in the car with my car charger. At home I charge all my batteries on an external charger - my phone is a mobile device I prefer to never be bound to a cord. I sleep with my phone next to me off the charger lol.
Okay so my phone is running more HAVS now and it seems the same as before so I guess my friend is HAVS friendly. I will run this for a day to check if any reboots happen and aim for tomorrow to overclock again. It may have been the 1.19 mhz that caused the issue. I will drop it down to 1.15 or 1.1 and see if its stable.
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
Can someone run a long CPU throttling test on this phone to see how heavily it scales as heat builds? The only test I've found online is https://3dnews.ru/assets/external/illustrations/2019/05/27/988154/sm.throttle_1.400.jpg, and it's pretty bad. I've seem comments about how this is one of the hottest 855 devices, and I dunno if you can use some software workarond like on some Xiaomi phones.
The test above was done using https://play.google.com/store/apps/details?id=skynet.cputhrottlingtest.
I've been looking for a strong phone to run emulators and my picks where either this or the Xiaomi 9T/K20 series. Screen, camera and development edged me towards this phone, but if it can barely sustain a gaming session then it's no good.
When I got mine I used it as a hotspot for 4 days while waiting for the flipcase I had ordered.
I was running both the 2.4G and 5G wifi hotspots at the same time, with a laptop and several other devices using it, and I also used it normally at the same time and even ran some benchmarks like Antutu, and it only got lukewarm at most.
Of course I have the E30 model with 12GB ram, which probably helps keep it cooler.
I'm still on Android 9 if that matters.
cobben said:
When I got mine I used it as a hotspot for 4 days while waiting for the flipcase I had ordered.
I was running both the 2.4G and 5G wifi hotspots at the same time, with a laptop and several other devices using it, and I also used it normally at the same time and even ran some benchmarks like Antutu, and it only got lukewarm at most.
Of course I have the E30 model with 12GB ram, which probably helps keep it cooler.
I'm still on Android 9 if that matters.
Click to expand...
Click to collapse
I found various results on Antutu and similar apps, but that only says about burst usage. If that image I linked is correct, after a few minutes the processor clock falls drastically.
If you don't mind please run the app I linked and print the result here. The default time is 15 minutes, but if you can manage a longer test I would appreciate. Of course you'll need to leave the phone resting during that time, so keep that in mind.
An example of a good result, ran on a Mi 9: https://i.redd.it/sh23onvimmq31.png. The phone can be used at full power without downclocking for a long time.
Here are the result. It depends on the temp on the sensor. It hit 90c when ran at full clock speed and it dropped to dynamic clock speed when it was hot on prime core. When it was cold enough it can boost to full speed again.
The environment temp was around 25c. Probably worse if the env temp was high
mickey36736 said:
Here are the result. It depends on the temp on the sensor. It hit 90c when ran at full clock speed and it dropped to dynamic clock speed when it was hot on prime core. When it was cold enough it can boost to full speed again.
The environment temp was around 25c. Probably worse if the env temp was high
Click to expand...
Click to collapse
Thanks a lot! Finally more data on this.
The clean step is similar to the first slowdown on the test I linked, maybe from some governor setting on the kernel. There should be a way to either remove or relax the thermal profile if needed, but while a tiered throttle might be too overzealous at least it makes for less performance flutuation.
Anyway, overall it's far from what I've seem before, and pretty good on my book. Good to know. Are you on Android 10 already?
XDFefo said:
Thanks a lot! Finally more data on this.
The clean step is similar to the first slowdown on the test I linked, maybe from some governor setting on the kernel. There should be a way to either remove or relax the thermal profile if needed, but while a tiered throttle might be too overzealous at least it makes for less performance flutuation.
Anyway, overall it's far from what I've seem before, and pretty good on my book. Good to know. Are you on Android 10 already?
Click to expand...
Click to collapse
Yes, I'm on Android 10 right now. Every day use is fine but actually warmer than I expected. Especially when I do a lot of opening apps, switch between apps that ramp up the prime core.
XDFefo said:
Thanks a lot! Finally more data on this.
The clean step is similar to the first slowdown on the test I linked, maybe from some governor setting on the kernel. There should be a way to either remove or relax the thermal profile if needed, but while a tiered throttle might be too overzealous at least it makes for less performance flutuation.
Anyway, overall it's far from what I've seem before, and pretty good on my book. Good to know. Are you on Android 10 already?
Click to expand...
Click to collapse
I found thermal config file in /vendor/etc
It use virtual-threm to set cpu clock speed in this snapdragon 855 platform based on current temperature.
This is the stock setting that I got from here
https://github.com/AndroidDumps/asu...0-release-keys/vendor/etc/thermal-engine.conf