Ok, so here's the story:
I was running oxygen+franco.kernel, and was suffering from loads of random reboots, as well as the oxygen signal dropping bug.
While I was looking for the source of the problem, I wiped the phone back to B138, and re-installed oxygen without the franco.kernel. Still had the signal loss, but the reboots stopped.
dzo fixed the network bug (thanks dude if you see this) and I thought it was safe to re-install the franco.kernel. But after I did the reboots returned!
So my question is, is anyone else suffering from this reboot problem with [04 OCT] franco.kernel? Or has anyone suffered from, then fixed it?
Thanks for any advice in advance!
P.S. Yes I could just not install the kernel, but I had some good performance and battery boosts from it, so would love to have it on and stable again!
I haven't oxygen anymore, but I've using it until latest cm7 update and always with frankco' s kernel(this include the 4 october version which I'm still using until now) and I never had reboot problems. Maybe your governor/io settings caused this.
I have
CPU: 400min 1000max, governor: SMARTASSV2, i/o scheduler: vr
vethan said:
Ok, so here's the story:
I was running oxygen+franco.kernel, and was suffering from loads of random reboots, as well as the oxygen signal dropping bug.
While I was looking for the source of the problem, I wiped the phone back to B138, and re-installed oxygen without the franco.kernel. Still had the signal loss, but the reboots stopped.
dzo fixed the network bug (thanks dude if you see this) and I thought it was safe to re-install the franco.kernel. But after I did the reboots returned!
So my question is, is anyone else suffering from this reboot problem with [04 OCT] franco.kernel? Or has anyone suffered from, then fixed it?
Thanks for any advice in advance!
P.S. Yes I could just not install the kernel, but I had some good performance and battery boosts from it, so would love to have it on and stable again!
Click to expand...
Click to collapse
i had the exact same problem with oxygen and 4oct franco. i traced the problem back to the kernel, uninstalled franco and no more reboots. now i'm using stock oxygen kernel. i was using franco with smartass2 governor 400 min 1200 max, now i'm using ondemand governor (i think) and same freqs. didn't notice any difference in battery life or performance to be honest, so i'm fine.
I had same rebooting issue with Franco´s kernel and Oxygen.
But if I had wlan on, no reboots. Didn't even have to be connected.
I only keeped wlan on and reboots were gone.
Bit strange... but now using Oxygen without Franco´s kernel.
Timbermax said:
I had same rebooting issue with Franco´s kernel and Oxygen.
But if I had wlan on, no reboots. Didn't even have to be connected.
I only keeped wlan on and reboots were gone.
Bit strange... but now using Oxygen without Franco´s kernel.
Click to expand...
Click to collapse
That's interesting. I'm trying to use CM7 and Franco's kernel now, and just had a reboot, but I'll switch wifi on an see how it goes
Related
Hey guys,
I have the Lightspeed 1.0.7 ROM w/ Thor's 3.9R3 kernel installed. I have my tab overclocked to 1.5 Ghz and I'm noticing random reboots the 3rd day which is weird because i never had reboots the first 2 days.
I noticed it after I open the system tuner app. does this have anything to do with the kernel? Or app?
Thanks
I have the same issue with system tuner on Thor's 14.1 using the 3.9R3 kernel. Also
using SetCPU to undervolt so I thought they may be conflicting or its just a glitch in the app. It usually crashes even if I don't change anythind just leave it on the CPU tweaks tab. I think I remember it happening on Taboonay 2.2 but I forget which kernel I was using at the time.
hello people i have opened this thread because the official thread stands a high risk of shutting down
on this thread you can talk about
kernels
best configuration kernel+rom
modds
bugs
fixes
and helping other people
all credit goes to sixstringsg and rom devs!
i got a realy good performence from both samephore and devil kernel but in both i got the android os drain whan phone is not used (5-6%) for 1 hour in wifi...:\
so for me i'm still looking for the right option to choose.
the os bug is fixed in b27.2 i think correct me if im wrong
Great Idea !
Best battery life - Semaphore latest kernel with battery saver mode, didle works perfect, wifi on and network on, and have 4 -8 % drain by whole night ( no drain with wifi only ) It seams that my phone also charges quicker, but that could only be impression by using car charger in most cases to charge it.
When it comes to installation issues. I never had any problems ( full wipe ). To make it complete trouble less get some other ISC flashed before hand, update kernel to semaphore and then flash build27.
When coming from GB use this guide, and files to flash. I did that way when changing from GB to ICS and never had any FC. The only thing you could do is to update kernel after flashing as the one below has a CWM 3 not 5.
And don't flash from your external SD card ( its obvious right ? )
theandroidsoul.dot/drz-miuiv4-beta-6-based-on-ice-cream-sandwich-for-galaxy-s-i9000
MinedSafe said:
Great Idea !
Best battery life - Semaphore latest kernel with battery saver mode, didle works perfect, wifi on and network on, and have 4 -8 % drain by whole night ( no drain with wifi only ) It seams that my phone also charges quicker, but that could only be impression by using car charger in most cases to charge it.
When it comes to installation issues. I never had any problems ( full wipe ). To make it complete trouble less get some other ISC flashed before hand, update kernel to semaphore and then flash build27.
When coming from GB use this guide, and files to flash. I did that way when changing from GB to ICS and never had any FC. The only thing you could do is to update kernel after flashing as the one below has a CWM 3 not 5.
And don't flash from your external SD card ( its obvious right ? )
theandroidsoul.dot/drz-miuiv4-beta-6-based-on-ice-cream-sandwich-for-galaxy-s-i9000
Click to expand...
Click to collapse
yes you get getprop. issues with b27 when flashing so
download b23 and b27 and put them onto the root of your sd card
also download gapps and semaphore
flash b23
bootloop
pull battery
go into cwm flash b27
also flash gapps and semaphore b4 reboot
paintball23456 said:
the os bug is fixed in b27.2 i think correct me if im wrong
Click to expand...
Click to collapse
not for me. thats the one thing missing in this rom... in all other ics with the same kernel setting i dont have this problem.... beside that i love this rom! so fast + stable!! and maybe someone without battery drain can share he's full settings and kernel?? thx..
rotemkk said:
not for me. thats the one thing missing in this rom... in all other ics with the same kernel setting i dont have this problem.... beside that i love this rom! so fast + stable!! and maybe someone without battery drain can share he's full settings and kernel?? thx..
Click to expand...
Click to collapse
you on b27.2 not b27
paintball23456 said:
you on b27.2 not b27
Click to expand...
Click to collapse
yup. had b27 and installed 27-2 over it without wipe.. maybe wipe will help..
rotemkk said:
yup. had b27 and installed 27-2 over it without wipe.. maybe wipe will help..
Click to expand...
Click to collapse
yes a wipe is the way dont even a update lol without a wipe you have rom leftovers and you dont want that
Media Storage bug fixed in 27.2
Hi, just wondering if the duplicate photos/music in media storage is fixed in 27.2?
rotemkk said:
yup. had b27 and installed 27-2 over it without wipe.. maybe wipe will help..
Click to expand...
Click to collapse
paintball23456 said:
yes a wipe is the way dont even a update lol without a wipe you have rom leftovers and you dont want that
Click to expand...
Click to collapse
I came from be18's B26 to B27 with full wipe and then to B27-2 with only Cache/Dalvik wipe. All good, no loops or FCs.
However, I did have rather high Android OS % and battery drain on both B27 and B27-2. Battery life was great on B26 with Devil 14.2. Tried stock, Devil 14.2 and Devil 1.1.5 kernels on B27 with no improvement.
Now using Semaphore 0.9.1 and that seems to have solved it. Fast, stable and only lost a few percent last night with WiFi on. I recommend B27-2 + Semaphore 0.9.1.
(My settings are 1200Mhz OC, SIO, SmartassV2)
cenonmin said:
Hi, just wondering if the duplicate photos/music in media storage is fixed in 27.2?
Click to expand...
Click to collapse
Don't think so mate
Sent from my SGH-I9000 using xda premium
OS Bug
It's still there, I come from full Wipe but it does not matter it's not kernel related it's Rom related. The only ICS out there to my knowledge without the OS bug is Dark Knight ICS 4.0.4 (very fast but not as smoothe and feature rich as this one)
thaidroid said:
It's still there, I come from full Wipe but it does not matter it's not kernel related it's Rom related. The only ICS out there to my knowledge without the OS bug is Dark Knight ICS 4.0.4 (very fast but not as smoothe and feature rich as this one)
Click to expand...
Click to collapse
i think the latest update is fixed b27.2 check the bug list here http://code.google.com/p/aokp/issues/list
JimmyNZ said:
I came from be18's B26 to B27 with full wipe and then to B27-2 with only Cache/Dalvik wipe. All good, no loops or FCs.
However, I did have rather high Android OS % and battery drain on both B27 and B27-2. Battery life was great on B26 with Devil 14.2. Tried stock, Devil 14.2 and Devil 1.1.5 kernels on B27 with no improvement.
Now using Semaphore 0.9.1 and that seems to have solved it. Fast, stable and only lost a few percent last night with WiFi on. I recommend B27-2 + Semaphore 0.9.1.
(My settings are 1200Mhz OC, SIO, SmartassV2)
Click to expand...
Click to collapse
smartassv2 has crap battery life i only flick to it for gaming use ondemand with vr if your on devils and for semaphore i say stick to stock settings
paintball23456 said:
smartassv2 has crap battery life i only flick to it for gaming use ondemand with vr if your on devils and for semaphore i say stick to stock settings
Click to expand...
Click to collapse
i also recommend in semaphore settings put touch sensitivity on chaiefire
Guys,I flashed rom yesterday Night, but I have 27% of android System,no os, only Android System ...
Sent from my SGH-I9000 using XDA
From what I've read in the forums, Android 4.0.3 has "Android OS" bug.. It's only fixed in Android 4.0.4 .. so, need to wait for it..
DaRkSuMTiN said:
From what I've read in the forums, Android 4.0.3 has "Android OS" bug.. It's only fixed in Android 4.0.4 .. so, need to wait for it..
Click to expand...
Click to collapse
never happen ANDROID SYSTEM at 27%.....android OS yes,but android system si another thing..and phone in battery statistics is always active.....it seems not go sleeping..
Hello,
can someone help me? Im trying to install AOKP ICS, but when choosing the update.zip it gives the following messages "assert failed: getprop("ro.product.device") == "Galaxys" || getprogp("ro.build.product") == "galaxysmtd" || ... and so on.
I can't install AOKP. I've downloaded and copied the file two times and the checksums match.
Any Idea what might help?
Kind regards
I am currently at Neutrino rom V2.5p2 GT
my phone have some problem that it cannot wake up after a long period of idle, such as EVERYDAY I wake up in the morning but I cannot wake my phone up. I have to pull my battery off and back in to reboot the device. This problem made me fail to receive morning calls for a whole week.
I am using Juicedefender, but not sure if it is the cause of problem.
Since this is the first custom rom I flash and I love Neutrino, but I think stability is a must to me. Are the V2.5p2 EE or V2.2 having a better stability? should I try them? or any patch can fix this problem?
Thank you so much!
same as u with 2.5p2 ee
wait for the next build
Sleep of death as its known, not always rom specific many of us experience it on different roms under different loads under different situations.
There's a few of us trying to track down the underlying problem, but at the moment we are all trying out different things which some work for people and not others
so agreed with the above just wait for the next build maybe that will work for you.
Harrison85 said:
Sleep of death as its known, not always rom specific many of us experience it on different roms under different loads under different situations.
There's a few of us trying to track down the underlying problem, but at the moment we are all trying out different things which some work for people and not others
so agreed with the above just wait for the next build maybe that will work for you.
Click to expand...
Click to collapse
Like i've said in the Neutrino thread - it's a CM7 bug that was present in the original weekly.
Flash the 023 kernel, wipe dalvik, reboot.
023 seems to have fixed the problem for me. Going through a second day without random reboots, sleep of death.
Link to the kernel can be found in the faux dev thread, but it's also in my sig.
I think my phone must be hate custom ROMs because it have SOD for Jokersax and Turl CM9 as well as Neutrino ROM. Did flash some faux kernel but solve nothing. Still running Jokersax CM9 although SOD simply because of ICS. My own opinion, don't try CM9 unless you are ready to stay with it until official release.
Sent from my MB860 using XDA
ko_wei13 said:
I think my phone must be hate custom ROMs because it have SOD for Jokersax and Turl CM9 as well as Neutrino ROM. Did flash some faux kernel but solve nothing. Still running Jokersax CM9 although SOD simply because of ICS. My own opinion, don't try CM9 unless you are ready to stay with it until official release.
Sent from my MB860 using XDA
Click to expand...
Click to collapse
What's your WIFI sleep policy set to?
And just to be 100% sure - do you wipe properly during rom flashing?
xploited said:
What's your WIFI sleep policy set to?
And just to be 100% sure - do you wipe properly during rom flashing?
Click to expand...
Click to collapse
I didn't enable wifi. Just using data plan. The setting for 'Keep Wi-Fi on during sleep' is Always as default.
I'm using N_01.100.00R baseband, could it be the issue? Any baseband recommend to use in Asia?
I follow what Jokersax said, format /system, wipe user data, wipe cache and dalvik cache in CWM. I manage to flash every single ROM and boot normally. Weird.
Sent from my MB860 using XDA
xploited said:
Like i've said in the Neutrino thread - it's a CM7 bug that was present in the original weekly.
Flash the 023 kernel, wipe dalvik, reboot.
023 seems to have fixed the problem for me. Going through a second day without random reboots, sleep of death.
Link to the kernel can be found in the faux dev thread, but it's also in my sig.
Click to expand...
Click to collapse
I am going to flash the 023 for a try. I just flash it in cwm recovery and that will be ok?
OK I have just flashed the 023 kernal, let me test my device for a few days to see whether SOD still exist, thanks!
ko_wei13 said:
I didn't enable wifi. Just using data plan. The setting for 'Keep Wi-Fi on during sleep' is Always as default.
Click to expand...
Click to collapse
I am using the default ATT baseband N_01.77.30P.
But from my experience, the reboot / sleep of death issue is most definitely related to WiFi.
Try setting Wifi sleep to "off when the screen is off" and switching to 023 kernel.
Haven't had any issues with this set up in the last 2 days.
xploited said:
I am using the default ATT baseband N_01.77.30P.
But from my experience, the reboot / sleep of death issue is most definitely related to WiFi.
Try setting Wifi sleep to "off when the screen is off" and switching to 023 kernel.
Haven't had any issues with this set up in the last 2 days.
Click to expand...
Click to collapse
Read from other thread with the workaround solution by installing Load Monitor or Wake Lock to prevent phone to go into deep sleep and fail to wake up. Now my phone run at 216Mhz instead of deep sleep when screen off. So far no SOD experience yet. But don't know how my battery life ink this case. Will update again after more observation.
[edit] no luck for load monitor. Get a SOD after 2 hours. Trying wake lock now. So far 6 hours no SOD. Will keep update.
Sent from my MB860 using XDA
Jokersax CM9 v0.4.1
I flashed the 023 1.3GHz kernal and the SOD disappeared last night!
I think the 023 1.0GHz kernal also work
I will observe for a few more days and report it here
Neutrino V2.6 GT and GT+ comes with 023 Kernel. It might solve the SOD as well. Downloaded. Will try it now..
Sent from my MB860 using XDA
ko_wei13 said:
Neutrino V2.6 GT and GT+ comes with 023 Kernel. It might solve the SOD as well. Downloaded. Will try it now..
Sent from my MB860 using XDA
Click to expand...
Click to collapse
I think the problem is solved with the 023 kernal! 2 days after flashing with no problem even set the wifi to be always on.
I think V2.6 EE version is worth trying since it include the CM7 kernal and claimed to have amazing battery efficient! But the V2.6 version introduced Launcherpro and many changes so I am not going to change it at this point, maybe a few days later.
Can I just flash the V2.6 stock CM7 kernal on my V2.5p2?
where can I find that CM7 kernal???
stainlesteel said:
Can I just flash the V2.6 stock CM7 kernal on my V2.5p2?
where can I find that CM7 kernal???
Click to expand...
Click to collapse
Why would you want the 2.6 kernel on 2.5p2?
For me 023 fixed the SOD issues.
Anyway, if you want to try the 2.6 kernel, download the rom, extract boot.img from the archive and flash it via fastboot, wipe dalvik, reboot.
If i were you, I would switch to 2.6 entirely. Haven't had any SODs in the past 24 hours since flashing.
stainlesteel said:
I think the problem is solved with the 023 kernal! 2 days after flashing with no problem even set the wifi to be always on.
I think V2.6 EE version is worth trying since it include the CM7 kernal and claimed to have amazing battery efficient! But the V2.6 version introduced Launcherpro and many changes so I am not going to change it at this point, maybe a few days later.
Click to expand...
Click to collapse
Flashed V2.6 GT and no SOD so far, but Play Store keep FC. Now revert back to CM9 Jokersax v0.4.1 with wake lock to keep my CPU on when screen off. No SOD for 2 days, but battery only can stay around 10hrs.
Sent from my MB860 using XDA
Oh I found the kernal swaping thread and the problem is solved!
I got is every once in a while with neutrino 2.2
My neutrino 2.6 have a priblem in search and home buttons.
TF101 running Revolver4 and Guevor's kernel has me whistling ;')
I had SOD's and other problems multiple times a day with all the ICS ROM's until I added Guevor's kernel (test11 was the first really stable on for me). I skipped running test 12(a,b, etc.) and went to test13 from test11 and it just seems very solid. OC'ed to 1504 and no heat issues, so SOD's, fewer FC's with apps, too.
If you're as tired as I was of the bleeding-edge, check out Guevor's kernel, I hear it's bringing stability to several other ROM's too.
Thread here.
yup, same here. I'm running revolver beta 1.3.1, with test13 kernel, and it's been very stable since i changed to guevor's kernel.
i don't oc my tf though... it just doesn't need to be oc'd
Well I got ~240h uptime stable with EOS build 19 before I got my first SOD (on that build).
I dont think Ive ever had an app FC on me.
The only time I am getting SOD is when I get multiple notifications at one time, like texting through Google Voice app or multiple emails coming in from different accounts. I am using ARHD 3.1.0 with Guevor (test 13). Anyone experiencing this?
Fast:
Check this out!
Fast, Stable, and Consistent:
ROM: ARHD 3.2.0.
Kernel: TestyMeh ICS 1.0 - OC+SIO+Initd ICS, New Suspend Method, Added Veno
Well , I made a full wipe for my transformer then installed ARHD 3.2 with guevor kernel test13 and it's very very stable. From the last charge and up to now, I've got 2 days and 8 hours with no single reebot and the wifi being connected all the time. I've left the kernel with it's default configuration at 1.2 GHz maximum.
I had some problems with Megatron and Guevor, but now i tried TestMeh and it is stable for 3 days, so i am happy
Revolver + test13 - stable as a rock at 1400Mhz.
Hey guys
I'm sorry for the question but i couldn't find a straight forward answer.
Do i flash a kernel the same way i flash a rom, through CWM?
My Kernel Flash Procedure:
I wipe Cache first. Then flash the kernel, in the same CWM session. I always a have a nandroid backup just in case something goes wrong and it has happened. Example: like not moving passed the boot logo for more than 15 mins. If this happens go back into CWM restore nandroid and reboot. Then do a MD5 check on zip file if possible or re-download kernel. Most of the time I check the zip file before flashing with the MD5 checker app.
Haven't tried the new kernels, all 3 of my tfs have been running rock solid since day one of ics... All on revolver 1.3.1 each one easily hit 300+ hours uptime. I am a little hesitant to change anything as they are all as perfect as I could imagine. But I might update oneto see what performance gains I achieve.
Sent from my SAMSUNG-SGH-I997 using XDA
Revolver RC1 and Guevor test 13/14
On my TF101, coming from 1.3.1 with wiping cache and Dalvik cache, I had good speed, wifi, Bluetooth etc. I did have lots of hanging in Gmail. I also did not ever get deep sleep.
After flashing Guevor test 14, all systems have been "go".
Thanks, developers.
Edit: No! reboot or any other system issues for an up time of 49+ hours. Gmail has started freezing again. Sometimes FC works for a while, but nothing fixes Gmail for me right now.
Gmail was fixed for the moment by reboot, no wipes. test 15 has been completely solid also (16 hours).
I did try the Guevor test 14 kernel, which is a very good kernel. However, on my thermal heat gun at the higher frequencies 1704 the tf101 is running 1c to 5c hotter then TestyMeh on my tf101. This might explain why some tf101s are more unstable at higher frequencies and volts due to heat. However, each tf101 is different. My was a pre-order from last year and seemed to have better components.
---------- Post added at 05:54 PM ---------- Previous post was at 05:31 PM ----------
Can't speak for every tf101, but if I set Min freq at 312MHz and not use the default 216MHz, I have not had any re-boots or SODs for every day use in almost a month now.
Hi, I didn't try Revolver4 but i did it with guevor's kernel test15.
Tryed Guevor's last test15 kernel with eos and got wifi-off allways... so I tryed TestyMeh 1.0 with eos and everything works cool. (OC-1600)
Revolver 4 is stable with test15? I'm thinking about swith to...
Sorry to be a little offtopic but I really need to comment something about!
I'm using test15 now. With test14 I had an SOD.
Grateful to Guevor for his stick-to-it-ivness with this kernel!
Hello guys. Can someone help me explain this picture (see attached)
Brand new D802, rooted, flashed TWRP and the CM12, latest nightly, and I'm having this weird activity when screen is off, draining a lot of battery. Any clues?
Thanks
Try a custom kernel like Render's kernel and see if the problem is fixed. If it's still not fixed then maybe it's a bug in the latest nightly, right now I'm using the 20150128 nightly and Render's kernel R9 and I don't have any issue with battery consumption.
raulx222 said:
Try a custom kernel like Render's kernel and see if the problem is fixed. If it's still not fixed then maybe it's a bug in the latest nightly, right now I'm using the 20150128 nightly and Render's kernel R9 and I don't have any issue with battery consumption.
Click to expand...
Click to collapse
Thanks for the tip. Haven't tried it yet, I looked up and I saw that there was a drain from the phone sensors and LED notifications, and so I uninstalled Google Fit and also uninstalled Lightflow for the LED. Now it seems to be fixed, too bad because I used those.