Hello, I have a launch Evo Shift (almost a year old now), and am running Cyanogenmod Nightly 255 with a2ext and a ton of apps installed (above 200 apps running from a class 10 32gb card, dalvik cache on the card), and ScaryKernel with the smartass governor (max 1497 MHz). However, I sporadically get random reboots, gps not working (requiring a reset), camera reboots, and the rare "turn off" bug where it turns off while sleeping. In addition most recently I have a bug where every time that I reboot into clockworkmod recovery to back up , it resets almost all of my phone preferences.
I absolutely love cyanogenmod and appreciate the hell out of it and the work that has been done, but I'm wondering if these bugs are either due to running cyanogenmod nightlies or if I have a defective phone. I also have tried Sense-based roms such as Mikshifted, but the Sense memory overhead is just too large for me. I have no worries if the phone is defective, since I have sprint insurance and can wipe back to stock to exchange it. However, going through all the exchange, re-root and restore procedure would be a pain if its not necessary. Does anyone have any thoughts or advice?
Thanks in advance.
I don't think this is s shift problem. I experienced this myself and even had my phone replaced by sprint because i thought it was. Try not overclocking and see if that helps. Another way to test if its the phone is to see if you have these same problems on a sense rom
Sent from my PC36100 using xda premium
draven760 said:
Hello, I have a launch Evo Shift (almost a year old now), and am running Cyanogenmod Nightly 255 with a2ext and a ton of apps installed (above 200 apps running from a class 10 32gb card, dalvik cache on the card), and ScaryKernel with the smartass governor (max 1497 MHz). However, I sporadically get random reboots, gps not working (requiring a reset), camera reboots, and the rare "turn off" bug where it turns off while sleeping. In addition most recently I have a bug where every time that I reboot into clockworkmod recovery to back up , it resets almost all of my phone preferences.
I absolutely love cyanogenmod and appreciate the hell out of it and the work that has been done, but I'm wondering if these bugs are either due to running cyanogenmod nightlies or if I have a defective phone. I also have tried Sense-based roms such as Mikshifted, but the Sense memory overhead is just too large for me. I have no worries if the phone is defective, since I have sprint insurance and can wipe back to stock to exchange it. However, going through all the exchange, re-root and restore procedure would be a pain if its not necessary. Does anyone have any thoughts or advice?
Thanks in advance.
Click to expand...
Click to collapse
I would say try using shift deck, U.K.E, or any cm based aosp roms and see if the problem persist. If it does then its your phone, if not then its a bug in the nightly which is the reason its a nightly because bugs could be there
From what you've stated above I don't think it's a phone, or Rom issue. Seems like you have way too many apps. You have to keep in mind a lot of those apps run in the background. Which uses up Memory, which slows the phone. It will also in xtreme cases cause Random Reboots, Lag, even Random app shut down. I'd remove at the very least half of those and see how it performs. Even 100 apps is still a bit much.
Great, thank you for the advice. Even though I have been monitoring my free memory and running programs, I'm kind of a pack rat so I think it's just time to streamline my programs.
Yes definately loose a lot of thoose apps. Might even want to try a fresh reflash, no apps. Then just add what you know you'll definately need. Willing to bet it's not even half.
TEAM MiK
Mik Roms Since 3/13/11
Which governor are you using with Scary kernel? You should be using Scary gov not any of the others.
Min mhz 300+
Check this first.
If that wasn't your problem run fix permissions from ROM manager and reboot.
If that wasn't your problem boot into clockwork recovery, format /system, wipe dalvik cache, wipe cache, reflash cm255, flash crashv2010's gapps, reflash scary kernel, reboot, wait 10 minutes, problems solved.
---------- Post added at 02:10 PM ---------- Previous post was at 02:08 PM ----------
draven760 said:
and ScaryKernel with the smartass governor
Click to expand...
Click to collapse
This is your problem! ONLY USE Scary, Toasty or Batterysave!
Scary = smartass
Toasty = performance
Batterysave! = conservative
ALL OTHER GOVS WILL NOT BE STABLE!!!
Smartass has always been stable for me
Sent from my PG06100 using Xparent Pink Tapatalk
YoungCorruptionV2.0 said:
Smartass has always been stable for me
Sent from my PG06100 using Xparent Pink Tapatalk
Click to expand...
Click to collapse
Depends how large the gap between your min/max cpu is.
What's your min max?
Try widening it with smartass and see how stable it is.
Well I guess I'm the exception . Dodge Kernel v1.6 Ext.4 , smartass setting , 1.92gHz Max , 245gHz Min. Can run that all day, but usually don't. I use the default settings 1.2gHz Max , 245gHz min. The battery life is better at the default settings.
VICODAN said:
Depends how large the gap between your min/max cpu is.
What's your min max?
Try widening it with smartass and see how stable it is.
Click to expand...
Click to collapse
I usually have the min at the lowest and the max at around 1.2 - 1.6 ghz
prboy1969 said:
Well I guess I'm the exception . Dodge Kernel v1.6 Ext.4 , smartass setting , 1.92gHz Max , 245gHz Min. Can run that all day, but usually don't. I use the default settings 1.2gHz Max , 245gHz min. The battery life is better at the default settings.
Click to expand...
Click to collapse
Some shifts can run 1.9ghz some cant. I have 2 shifts here, both hardware rev 004, one can't go past 1.6ghz.
---------- Post added at 01:38 AM ---------- Previous post was at 01:36 AM ----------
YoungCorruptionV2.0 said:
I usually have the min at the lowest and the max at around 1.2 - 1.6 ghz
Click to expand...
Click to collapse
smartass on pershoot is ok
smartass on scarykernel is not ok.
Yes definately know what you mean. Out of six mine is the only one that will do 1.9gHz . All hardware 004. Out of the others two will do 18gHz, but only one is stable. The rest max out at 1.5gHz, after that they're not stable.
TEAM MiK
Mik Roms Since 3/13/11
VICODAN said:
Some shifts can run 1.9ghz some cant. I have 2 shifts here, both hardware rev 004, one can't go past 1.6ghz.
---------- Post added at 01:38 AM ---------- Previous post was at 01:36 AM ----------
smartass on pershoot is ok
smartass on scarykernel is not ok.
Click to expand...
Click to collapse
Probably true, i'm on tiamat v1.1.4 with smartassV2 so that could make a difference but i always use smartass cause i love the battery life i get with it
prboy1969 said:
Yes definately know what you mean. Out of six mine is the only one that will do 1.9gHz . All hardware 004. Out of the others two will do 18gHz, but only one is stable. The rest max out at 1.5gHz, after that they're not stable.
TEAM MiK
Mik Roms Since 3/13/11
Click to expand...
Click to collapse
YoungCorruptionV2.0 said:
Probably true, i'm on tiamat v1.1.4 with smartassV2 so that could make a difference but i always use smartass cause i love the battery life i get with it
Click to expand...
Click to collapse
Thank you for confirming my opinion as fact. I will reference this thread again later if I need to.
i would get new rom manager that fixed some of my problems also try reloading cm7 and put back on you phone with titanium backup
VICODAN said:
Some shifts can run 1.9ghz some cant. I have 2 shifts here, both hardware rev 004, one can't go past 1.6ghz.
---------- Post added at 01:38 AM ---------- Previous post was at 01:36 AM ----------
smartass on pershoot is ok
smartass on scarykernel is not ok.
Click to expand...
Click to collapse
I have rev 0004 and mine clocks to 2ghz just fine...Some kernels just can't handle 2ghz, and most only clock to 1.8 or 1.9
Related
http://forum.xda-developers.com/showthread.php?t=1020637
DON'T USE THE ROM, IT IS OUTDATED AND HAS BEEN DISCONTINUED!
DO NOT USE THE "PUV" (Pinky UnderVolt) VERSION, IT WILL CAUSE YOUR DEVICE TO GET STUCK AT THE SPLASHSCREEN! (POSSIBLY)
I DID NOT MAKE THIS KERNEL, I'M JUST POSTING IT HERE FOR YOU ALL.
THIS IS NOT FOR ANY OTHER ROMS BESIDES CM7 (AND CM7-BASED ROMS) AND MIUI, SO DON'T ASK!
I'm using the UUV CFS version. It is very fast and smooth, I urge you not to have an OC past 1.3GHz as a daily driver, unless you want horrible battery life.
Any option below PUV is safe (UUV, -50mV, and -25mV all work, but every device varies).
i didnt think my phone could ever sh*t itself until i flashed this kernal.
dethpikil said:
i didnt think my phone could ever sh*t itself until i flashed this kernal.
Click to expand...
Click to collapse
i logged in just to ask you to decrypt that message. what does that mean? bad kernal?
vln004 said:
i logged in just to ask you to decrypt that message. what does that mean? bad kernal?
Click to expand...
Click to collapse
lol, iffy kernal. especially with two versions available, its kinda strange testing them and seeing whats best for your phone. flashed the cfs version, and as expected, things seemed evenly smother throughout the phone, yet even at 1.99, there was nothing special or over the top about performance. also, i had a very strange, completely indescribable hiccup after booting.
EDIT
tried the bfs version, and still nothing special. maybe its just me and my miui rom. the 1.99 is cool, but i think im just gunna stay away from this.
Been running his kernels for a couple of weeks, no issues. It is nice to be able to choose from different undervolt versions. Helps battery life a little, around 5%-10% in my experience.
NikolaiT, just FYI this kernel works with Ultimate Droid, which is based on CM7. In case you want to update the OP.
henrybravo said:
NikolaiT, just FYI this kernel works with Ultimate Droid, which is based on CM7. In case you want to update the OP.
Click to expand...
Click to collapse
+1. Running 4.2 cfs -25 version on UD now. 4.0 was the best battery life ever on any cm7 based roms. Haven't tried the puv version yet, but rest assured I will try and report results..
Sent from my Desire HD using Tapatalk
dethpikil said:
lol, iffy kernal. especially with two versions available, its kinda strange testing them and seeing whats best for your phone. flashed the cfs version, and as expected, things seemed evenly smother throughout the phone, yet even at 1.99, there was nothing special or over the top about performance. also, i had a very strange, completely indescribable hiccup after booting.
EDIT
tried the bfs version, and still nothing special. maybe its just me and my miui rom. the 1.99 is cool, but i think im just gunna stay away from this.
Click to expand...
Click to collapse
Hardly "iffy", the differences are stated in the thread or here.
I've been using this kernel with CM7 Final for quite some time now and it's been quite solid.
rasroygbiv said:
+1. Running 4.2 cfs -25 version on UD now. 4.0 was the best battery life ever on any cm7 based roms. Haven't tried the puv version yet, but rest assured I will try and report results..
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
Careful, the PUV version softbricked my device. Easily fixable through reflashing your ROM or just a new kernel.
It may not brick yours because some devices can handle it, some can't.
helushune said:
Hardly "iffy", the differences are stated in the thread or here.
I've been using this kernel with CM7 Final for quite some time now and it's been quite solid.
Click to expand...
Click to collapse
+1. Not "iffy" at all.
I've been using it for a while now. At the moment I'm using the latest CFS -25 UV version @ 1305 with the scaling set to Intelligent Donkey (lol) and I actually made it an entire day without charging. That's saying a lot for someone that gets about 12 hours max on a charge.
Sent from my GT-I9000 using XDA App
TheBassman369 said:
I've been using it for a while now. At the moment I'm using the latest CFS -25 UV version @ 1305 with the scaling set to Intelligent Donkey (lol) and I actually made it an entire day without charging. That's saying a lot for someone that gets about 12 hours max on a charge.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
I'm currently pulling two days at 64% with the same kernel but my CPU settings are 122 min - 1075 max.
So what's everyone recommendations for the best version of this Kernel in terms of both optimum battery and performance?
Additionally... what kinds of CPU governors and max-min frequencies are you using? I've seen a few post what their using in this thread, but I'd like to get some more opinions.
I've been using this Kernel for a few weeks now with no issues. The UUV had some slight hesitation when scrolling so now I'm running 4.3 CFS with the -50 UV and it's absolutely perfect. Fantastic battery life running at 122/1305 MHz with the -50 UV.
i'm using 4.2 and I didn't flash any scripts... is the default -25UV? I'm gonna try 4.3 and -50 script later tonight.
quick question to the group: what is eating up your battery? mine, oddly enough is cell standby and phone idle. i'm using stock radio. in the past (on froyo builds), it's always been screen time.
substance12 said:
i'm using 4.2 and I didn't flash any scripts... is the default -25UV? I'm gonna try 4.3 and -50 script later tonight.
quick question to the group: what is eating up your battery? mine, oddly enough is cell standby and phone idle. i'm using stock radio. in the past (on froyo builds), it's always been screen time.
Click to expand...
Click to collapse
Default is no undervoltage.
Cell Standby and Phone Idle are my two biggest "battery killers" but that's normal operation.
henrybravo said:
+1. Not "iffy" at all.
Click to expand...
Click to collapse
maybe all of you missed the whole miui thing. it says it works great with miui, but my phone seemed very buggy after switching from cattleprods kernel, but you tested it on very different roms than me. it addition, my quadrant score were crap on both types, cfs and bfs, which is completely contrary to the description of one over the other. so yes iffy.
Can anyone explain the difference between the scheduler flavors? I use cfs, but bfq or io?
dethpikil said:
maybe all of you missed the whole miui thing. it says it works great with miui, but my phone seemed very buggy after switching from cattleprods kernel, but you tested it on very different roms than me. it addition, my quadrant score were crap on both types, cfs and bfs, which is completely contrary to the description of one over the other. so yes iffy.
Click to expand...
Click to collapse
I sure did. Pardon.
sugardaddy1979 said:
Can anyone explain the difference between the scheduler flavors? I use cfs, but bfq or io?
Click to expand...
Click to collapse
Check these two posts: Post 1, Post 2. Looks like BFQ is the standard scheduler and VIO is quicker on paper (kind of like BFS vs CFS).
Thanks for the explanation. The bfqhs seems much smoother than the io. I am running it with the uuv.
hello, I just wanted to make this thread for everyone to share their lowest AND stable voltage values for each frequency. Here goes mine:
(anything above 1000mhz was not tested)
1000mhz <-- 950mV
800mhz <-- 825mV
500mhz <-- 550mV
300mhz <-- 500mV
The following was done with eb1.0.4 + trinity kernel.
please share yours.
Copied from the kernel thread...
Bionix 2 at 1.2Ghz using deadline scheduler.
I attached my PMCpu settings in case anyone needs a reference.
Stressed tested for 15 mins stable.
Quadrant at 3337, Linpack around 45.
Click to expand...
Click to collapse
I started by doing -50 on all from 1200 oc...ill test for a whole day and drop it down -25 tomorrow and test for a whole day. And please post scheduler also.
So far @-50 on deadline scheduler all is working well, no freezes.
G2X
And how is battery life for everyone?
I can't belive how efin good mine has been, bt on, wifi on for 2 hrs, on xda forums every 30 minutes unplugged at 4:30a at 1:00p still had 55% left, whereas stock kernel would be at 15-10%...
G2X
GideonX said:
Copied from the kernel thread...
Click to expand...
Click to collapse
Using your settings running very smoothh!
Sent from my LG-P999 using XDA Premium App
fcisco13 said:
I started by doing -50 on all from 1200 oc...ill test for a whole day and drop it down -25 tomorrow and test for a whole day. And please post scheduler also.
So far @-50 on deadline scheduler all is working well, no freezes.
G2X
Click to expand...
Click to collapse
I have no idea what schedulers are
Also, a question to everyone, what are some of your unstable symptoms from UV? Since I've never had any rebooting issues with my g2x, I am not sure if some of the symptoms I was experiencing is from UV'ing or from the kernel. If you gone under the UV limit, does your phone just freeze or would it autoreboot?
c19932 said:
I have no idea what schedulers are
Also, a question to everyone, what are some of your unstable symptoms from UV? Since I've never had any rebooting issues with my g2x, I am not sure if some of the symptoms I was experiencing is from UV'ing or from the kernel. If you gone under the UV limit, does your phone just freeze or would it autoreboot?
Click to expand...
Click to collapse
UV will more than likely freeze or you will reboot... UV typically just makes everything really unstable, you might get stuck in a bootloop and have to reflash
JHaste said:
UV will more than likely freeze or you will reboot... UV typically just makes everything really unstable, you might get stuck in a bootloop and have to reflash
Click to expand...
Click to collapse
oh and a precaution to those using eb1.0.4 + trinity kernel. I set my max voltage for 1000mhz (my max. frequency as well) too low, and the phone autoreboot on startup twice and then did a factory reset itself This happened twice so be aware
GideonX said:
Copied from the kernel thread...
Click to expand...
Click to collapse
I'm running this settings and so far really good.
Thanks man!
Sent from my Bionix 2 - A TeamWhiskey Production using XDA App
fcisco13 said:
I can't belive how efin good mine has been, bt on, wifi on for 2 hrs, on xda forums every 30 minutes unplugged at 4:30a at 1:00p still had 55% left, whereas stock kernel would be at 15-10%...
G2X
Click to expand...
Click to collapse
What ROM and Kernel are you using? Also, which EB can be used with the Trinity kernel? GB or FroYo?
Anyone find that their battery has actually gone down while UV'ing? I'm finding after a full charge, the first 30% has been quicker by almost an hour. Not a really scientific method of testing, but I do just about the same thing every morning (email, txt, etc.) left over from the night before. That first 30% has a lot of screen off time, which will lower the speed to 300Mhz using PMCpu.
I'm going to up the voltage to at least 700 for 300Mhz and see how that fairs.
hah2110 said:
What ROM and Kernel are you using? Also, which EB can be used with the Trinity kernel? GB or FroYo?
Click to expand...
Click to collapse
--EB 1.0.4 FROYO (gutted removed live wallpapers, wifi calling, tmo stuff)
--Trinity 15 EB1.04 FROYO
[email protected] pimp my cpu (free on xda)
--Went down -50volts on all speeds
Battery is unbelievable..
G2X
I just restored my EB 1.02. I'm going to flash trinity kernel and report back after one day of use.
Sent from my LG-P999 using XDA App
I've heard several people had lockups and phone factory reset when uv too low, i think going more than -50 is really risking it...
G2X
fcisco13 said:
--EB 1.0.4 FROYO (gutted removed live wallpapers, wifi calling, tmo stuff)
--Trinity 15 EB1.04 FROYO
[email protected] pimp my cpu (free on xda)
--Went down -50volts on all speeds
Battery is unbelievable..
G2X
Click to expand...
Click to collapse
Can Trinity be used with EB Gingerbread?
hah2110 said:
Can Trinity be used with EB Gingerbread?
Click to expand...
Click to collapse
There are specific kernel for gb, look for one that is for EB1.04GB
G2X
Ok, I'm running infusion A2, not OC'd, UV'd 100 across the board just fine.
My problem starts fast when I OC to 1600, it rans ok there, for the few minutes I tested it at stock voltages. The problem is when I change ANY CPU step to UV it just crashes and reboots my phone instantly. Tried it 3 times. It comes back on fine, even if I left set as boot checked (accidentally), but the settings were not saved. Haven't tried B2 yet to see it is repeatable on 1400, and don't really want to repeat it at all.
Any ideas why this is happening? On Doctorz ROM using SetCPU to OC/UV.
Thanks y'all
Try voltage control instead (free in the market) but honestly, not all Infuses can handle 1.6 ghz. In your case, you are most likely right on the line of crashing at 1.6, when you change the voltages, you cross that line.
Its well know messing with the native clock speed can AT some phones and some times cause low stability and reboots also force closes etc. I suggest you to try lower OC speeds like 1.4 Ghz ive been running my Infuse on 1.4 forever without one single problem.
Yeah, was gonna go to B2 and try 1.4, but figured I would get some suggestions first.
Had VC at first, but didn't try OC, just UV, gonna try that tomorrow.
jonrobertd - did you flash a certain kernal to OC your Infuse? Everything I've read says either the Infuse can't be OCed. I even tried using SetCPU but it kept giving me errors when I'd run it, telling me something like "no profiles loaded" or something like that.
---------- Post added at 07:31 AM ---------- Previous post was at 07:25 AM ----------
koriotto said:
...ive been running my Infuse on 1.4 forever without one single problem.
Click to expand...
Click to collapse
koriotto - how are you overclocking your Infuse? What OS are you using (Froyo, GB, etc.)?
You have to have a kernel that supports overclocking....and yes the infuse can be overclocked...I'm running it at 1.6 myself on my rom....the infusion gb kernel can be overclocked....entropy's daily driver can't...the community kernel is Froyo....if your running gingerbread rom and flash the community kernel your phone will bootloop.....read...
Sent from my SAMSUNG-SGH-I997 using xda premium
Overclock to high frequencies and lower the voltage too much and the CPU becomes unstable. Some can handle it, some can't, all cpus are different.
Sent from my SAMSUNG-SGH-I997 using XDA App
Will these ever go away on my nexus s? I have gotten them in everything from stock 2.3, cyanogenmod 7, stock ICS, oxygen, and every single ICS rom I have used. I understand some software bugs take a while to find but I have had this bug for over a year, will it every get a fixed? (Or is this not a software bug but an actual issue with my phone?)
Could be cause from UV settings if you touched them
Sent from my Nexus S using XDA
ThisNight said:
Could be cause from UV settings if you touched them
Sent from my Nexus S using XDA
Click to expand...
Click to collapse
Nope. I usually run 200 mhz minimum and 1200 max for my cpu. On stock I also ran stock volts.
tominater12 said:
Nope. I usually run 200 mhz minimum and 1200 max for my cpu. On stock I also ran stock volts.
Click to expand...
Click to collapse
Well, you're running an overclock... Try running without.
CM7 has a sleep of death/reboot bug, so try another ROM not based on CM7 too.
Highly recommend Oxygen 2.3.2 coupled with Franco 08.12.2011 GB kernel.
If you're interested in ICS ROM, give AOKP ROM and Matr1x kernel a try. It's rock stable for me. I just rebooted to flash the new build, but before that it lasted for couple weeks for me without rebooting. Link to AOKP ROM is in my sig.
tominater12 said:
Nope. I usually run 200 mhz minimum and 1200 max for my cpu. On stock I also ran stock volts.
Click to expand...
Click to collapse
There's your problem. Perhaps increase the voltage? Your phone may not be able to handle the frequency without extra voltage.
There should be no random reboots if you never touched anything kernel related. If so, then bear the consequences.
I've been using CM9 v2.2 for about 3 months now haven't overclocked or undervolted and haven't had any "random" reboots ever.
I'd highly recommend the Androxide ROM along with Air Kernel. I've been running this combo overclocked to 1200 without any voltage setting changes for a decent amount of time.
random reboot frequency - about once a week ..
AeroEchelon said:
There's your problem. Perhaps increase the voltage? Your phone may not be able to handle the frequency without extra voltage.
There should be no random reboots if you never touched anything kernel related. If so, then bear the consequences.
I've been using CM9 v2.2 for about 3 months now haven't overclocked or undervolted and haven't had any "random" reboots ever.
Click to expand...
Click to collapse
I second that. Usually OCing requires raising voltages across the board. I use +25mV (arm and int). If you're suing a matr1x kernel that's even more reason to raise voltages, because afaik that kernel is undervolted by default.
Best of luck.
zgomot said:
I second that. Usually OCing requires raising voltages across the board. I use +25mV (arm and int). If you're suing a matr1x kernel that's even more reason to raise voltages, because afaik that kernel is undervolted by default.
Best of luck.
Click to expand...
Click to collapse
Thirding it.
If you are having problems then roll everything back to stock... its not good enough to say you have run every rom , yet fail to mention you OC. What other tweaks do you run? Deep Idle?
I'd bet if you flash CM9 with no tweaking it, it will be fine.
bringonblink said:
I'd bet if you flash CM9 with no tweaking it, it will be fine.
Click to expand...
Click to collapse
Or just about *ANY* rom for that matter. First ensure you can run it stable without OC, UV, didle, mods, themes etc then, by all means, go ahead and tweak to your hearts's content.
Overclocking to 1200mhz CPU only does NOT require extra voltage across the board, but possibly a boost at the 1200mhz voltage. Each frequency runs at a different, changeable voltage which has nothing to do with all the others. LiveOC, however, raises the frequency of each step and as such generally requires a boost in voltage across the board or thereabouts.
As for the problem the OP is having, who knows. Could you describe any specific things you've done, though? Full wipes (detail what you wipe), titanium backup restores, etc.
First thing i would be trying now is to do a full wipe (factory/data reset, format /boot, format /system), flashing either stock 2.3.6 or 4.0.3 and installing only necesseties and try for a week or so. If there are still reboot problems, describe them and hopefully i can give you some useful things to try. If you had this problem before the 1 year mark you could have probably gotten the phone fixed/replaced under warranty, though. If it is now over a year i'm afraid that's too late though.
Just for info:
ALWAYS on stock, unrooted, right now 4.0.3 OTA. Since 4.0.3 random reboots, w/o any culprit cause I can find..
So, I guess, has nothing to do with ROM, voltage, solar storms, etc..
Well this is all bullcrap. . . i installed CM7.0.1 and CM7 RC1 and the latest ICS from CM team and her phone either randomly reboots or switches off totally while charging in the night.
Its got bugger all to do with the kernel because i used the standard kernel with all the CM7 & CM9 roms and the same things happen over and over.
Also the OC'ing idea is BS, i don't OC my nexus S or hers and even mine suffers random reboots.
there has to be some code somewhere thats not behaving a sit should and google never sorted it and CM team never found it, or the hardware is just ****ty in this hand set.
Have you tried other ROM besides CM7? I remember when I flashed CM7 for the first time. My phone never liked it, it was all bugs for me. I even noticed that OC'ing would generate problems on any ROM.
I just ran away from CM7 and OC'ing.
Try Oxygen ROM (or stock as they stated before) with all set up to defaults and test for a while.
hutzdani said:
Well this is all bullcrap. . . i installed CM7.0.1 and CM7 RC1 and the latest ICS from CM team and her phone either randomly reboots or switches off totally while charging in the night.
Its got bugger all to do with the kernel because i used the standard kernel with all the CM7 & CM9 roms and the same things happen over and over.
Also the OC'ing idea is BS, i don't OC my nexus S or hers and even mine suffers random reboots.
there has to be some code somewhere thats not behaving a sit should and google never sorted it and CM team never found it, or the hardware is just ****ty in this hand set.
Click to expand...
Click to collapse
I admit I had reboots with cm7' but with latest cm9 nightly I have none. Stock kernel stock oc and stock voltage with deep idle off
Sent from my Nexus S using Tapatalk 2 Beta-2
bmszabo said:
Just for info:
ALWAYS on stock, unrooted, right now 4.0.3 OTA. Since 4.0.3 random reboots, w/o any culprit cause I can find..
So, I guess, has nothing to do with ROM, voltage, solar storms, etc..
Click to expand...
Click to collapse
The update was pulled for many reasons. Try stock GB or Oxygen ROM and enjoy life without freeze, sleep of death or reboot...
As some of you may know, I've been working on a custom kernel for ICS/JB and its about done (for a first release). Current kernel features include: (If feature begins with a * then check below for more information)
Compatible with all AOSP ICS & JB roms
rebased to CAF Linux 3.0.40 kernel
Built in Low-memory killer w/ Fugeswap (as seen in the v6 Supercharger)
Optimized ram usage/handling (Swap & Zram)
Increased Wi-fi connectivity range
*Low & High power Wi-fi scaling steps
*Badass Governor (Default)
Lazy Governor
Imported Snapdragon optimizations used by the Sensation (Thanks Romanbb)
Lagfree Governor
Fast charging for unknowns
HIGHLY Tweaked for the perfect battery life and performance
Updated Bluetooth code from CAF
V(R), simple, deadline, noop, and CFQ I/O schedulers
*Ondemand & Intelli(gent)demand Governor
Stable Undervolting of the CPU
increased SDcard readahead speed
Tweaked Flashlight
Added more clock steps to the GPU for compatibility with low power browsing and GPU OC @ 320 mhz
I think 6 testers should be enough for now, thanks for participating
If you wish to join in this this beta testing please feel free to shoot me a PM or hit me up on GTalk @ [email protected]
You may find my source hosted @ Github
Current testers (in order of request sent):
AgentCherryCola
sino8r
onebornoflight
phone77
jjbz
WeekendsR2Short
CoNsPiRiSiZe
More information:
Badass Governor: This governor has built in profiling (like used in SetCPU but not as battery & Ram consuming). This is also the default and highly recommended governor. This governor features a 3 phase system CPU profiling system. This will change your CPU speed based on usage. This saves a lot of power as your speed doesn't just keep at one clock no matter how much your using you phone. A similiar profiling system is also used for the GPU and such.
Ondemand and Intellidemand Governor: Intellidemand is based off the Ondemand governor but features a 2 phase CPU profiling system with some added tweaks.
Wi-fi Low and High power scaling steps: This is a feature that will determine whether to use High or low power voltages on the Wi-fi chip to save battery. eg: Wi-fi will be turned to low power when idle or screen off. Wifi will be turned to high power when actively in use or in progress of a download. Take note that high power wi-fi voltage isn't necessarily "High" power but more of just "Stock HTC" power.
Thanks:
TeamDS
Strapped365
faux123
showp1984
RomanBB
and any others I may have missed
I'll test out this Kernel. I'll test CM9, AOKP, and MIUI.
Sent from my HTC MyTouch 4G Slide using Tapatalk 2
I'm ready!
ditto dude... thanks!
Il do it!
::Respect::
So how's the kernel testing going out guys! This looks really promising
Sent from my myTouch_4G_Slide using Tapatalk 2
Ok I think thats enough testers for now, Testing will begin soon just making some final adjustments
Quite psyched to check this out!
Sent from my HTC MyTouch 4G Slide using xda app-developers app
sorry for the delay, Ive been troubleshooting battery issues which started after upgrading past 3.0.30, im thinking about downgrading back to that version to see if the problem persists
xmc wildchild22 said:
sorry for the delay, Ive been troubleshooting battery issues which started after upgrading past 3.0.30, im thinking about downgrading back to that version to see if the problem persists
Click to expand...
Click to collapse
Battery issues are nothing new with the latest kernel commits. Just take a stroll through the CM9 thread
Honestly, I've seen better battery life on the old 2.6 kernel
gtmaster303 said:
Battery issues are nothing new with the latest kernel commits. Just take a stroll through the CM9 thread
Honestly, I've seen better battery life on the old 2.6 kernel
Click to expand...
Click to collapse
I'm not saying everyone else is lying I'm just saying that personally I find better screen on time with the latest kernel, except I must be one of the few.
Xmc whatever you got we'll test if ya want
::Respect::
CoNsPiRiSiZe said:
I'm not saying everyone else is lying I'm just saying that personally I find better screen on time with the latest kernel, except I must be one of the few.
Xmc whatever you got we'll test if ya want
::Respect::
Click to expand...
Click to collapse
Yea, I don't know how you do it... Possibly a fluke, or just your setup
CoNsPiRiSiZe said:
I'm not saying everyone else is lying I'm just saying that personally I find better screen on time with the latest kernel, except I must be one of the few.
Xmc whatever you got we'll test if ya want
::Respect::
Click to expand...
Click to collapse
Then I'll make sure to include the "Conspirisize ultra performance" version
Soooooo how about that kernel release for all of us (;
Sent from my HTC MyTouch 4G Slide using Tapatalk 2
I think his Kernel was lost in Goo.Im crash.
::Sense 4.0::
I believe he had most of it on Github?
WeekendsR2Short said:
I believe he had most of it on Github?
Click to expand...
Click to collapse
Most is correct, but all the new commits wasn't so the source is most likely complete and would compile, but it sounded like the new additions that needed tested were not pushed into git so are now lost
Sent from my HTC MyTouch 4G Slide running MikXE
strapped365 said:
Most is correct, but all the new commits wasn't so the source is most likely complete and would compile, but it sounded like the new additions that needed tested were not pushed into git so are now lost
Sent from my HTC MyTouch 4G Slide running MikXE
Click to expand...
Click to collapse
I had 30+ commits that I were going to push to git fixing a lot of problems but my hard drive fried at the same time goo went down. (I have a live network backup of my hard drive hosted on goo) So I lost those commits.
strapped365 said:
Most is correct, but all the new commits wasn't so the source is most likely complete and would compile, but it sounded like the new additions that needed tested were not pushed into git so are now lost
Sent from my HTC MyTouch 4G Slide running MikXE
Click to expand...
Click to collapse
Well CRAP! :crying:
---------- Post added at 08:21 PM ---------- Previous post was at 08:20 PM ----------
..
---------- Post added at 08:22 PM ---------- Previous post was at 08:21 PM ----------
xmc wildchild22 said:
I had 30+ commits that I were going to push to git fixing a lot of problems but my hard drive fried at the same time goo went down. (I have a live network backup of my hard drive hosted on goo) So I lost those commits.
Click to expand...
Click to collapse
..