I have put this all together on the uk release and put it out as a rom here:
http://forum.xda-developers.com/showthread.php?p=34971303#post34971303
So here is a thread to talk about getting the German release of Jelly Bean on the 8013 and the 8010
I cross referenced the way that pimpmaneaton did his redemption rom, being able to work on the 8013 and 8000 with the aroma installer, checked what was different between the two for ICS.
With the build.prop, it was mostly just some changes to from 8000 to 8013 in the naming of things, but there were also a couple things coded out to get it better on the 8013
We have been looking into the dialer commands to see if any will disable the radio, more on post 11 for that testing.
I have had success with no reboots as well as removing the pesky no signal icon. I have included a flashable zip file that will take care of the build.prop, delete the files we know are not needed, disable the telephone by replacing the framework-res, adding in darkman-rs circle 1% battery mod, removing the null signal and airplane mode icons by replacing the systemui.apk
Step one: Download a jelly bean rom
I have been using darkman_rs version of the JB since it is stock and works nicely, also he has a lot of other nice stuff for it like a circle battery mod I like, and the telephony disabler.
Here is a link to his rom http://forum.xda-developers.com/showthread.php?t=1909950
***
Flash rom, clear cache/dalvik
Reboot, login/setup/etc until you reach a fully installed state.
Then reboot to recovery and install the fix zip.
Set cpu to ondemand
***
fix zip for 8013:
https://www.dropbox.com/s/xkb3spitb5vhlas/Complete_jb80xx_v2.zip
fix zip for 8010:
http://db.tt/tNMC0ZAv
The only difference between the two is the device name in the build.prop
-------------------------------------------------
Other fun stuff:
Adding in the 4 way reboot
I got this from Team Unions ROM here http://forum.xda-developers.com/showthread.php?t=1995700
It is a great rom and all the stuff here should work for that rom as well
https://www.dropbox.com/s/v97fqjyuvjkx7f2/reboot2.zip
there are a lot of nice tweaks from pimp my rom
here http://www.xda-developers.com/android/pimp-my-rom-install-tweaks-on-any-android-device/
Set your governor to ondemand has gotten a lot of good reports for stopping the reboots. This can be done with several tools from the market, I use rom toolbox pro, others use setcpu.
This was posted by darksabre_x
Here's SetCPU. It's been released free for XDA members. Donate when you are able.
http://forum.xda-developers.com/showthread.php?t=505419
Also check out this thread for more multiwindow apps and how to add more!!
http://forum.xda-developers.com/showthread.php?t=1985240
Super cool!!
I found this, some more information on the Pegasusq Governor
http://forum.xda-developers.com/showpost.php?p=24233103&postcount=3
I removed the non flashable zips because a lot of people were getting confused, all the same stuff is in the fix zips above and will be easier to update if need be.
If there are any more things, add them, lets see if we can get this up and running perfectly before samsung does!
Thanks to everyone here for working together to get this running on the 8013!
what do you think is causes the reboots?
TramainM said:
what do you think is causes the reboots?
Click to expand...
Click to collapse
In my experiences as well as what others have had, it only reboots when it is idle, so it would be an issue with the sleep mode of something, maybe when it tries to go to sleep, something tries to tell the radios to do something different and it doesn't like it to it reboots.
I am going to try getting my csc changed to germanys to see what that does.
smaw51 said:
In my experiences as well as what others have had, it only reboots when it is idle, so it would be an issue with the sleep mode of something, maybe when it tries to go to sleep, something tries to tell the radios to do something different and it doesn't like it to it reboots.
I am going to try getting my csc changed to germanys to see what that does.
Click to expand...
Click to collapse
Sounds like a Dormancy thing, how could one get rid of that?
EDIT: How come airplane mode doesn't help, and the shutdown while charging? I mean I can keep my screen on all day and while its charging but won't that damage it
TramainM said:
Sounds like a Dormancy thing, how could one get rid of that?
EDIT: How come airplane mode doesn't help, and the shutdown while charging? I mean I can keep my screen on all day and while its charging but won't that damage it
Click to expand...
Click to collapse
Yes, I would imagine that would cause damage to a few things. There is a screen dimmer that keeps the screen *on* but has it dimmed to it appears to be off. I don't know what kind of long term effects it would have on the screen would be, because it is still on and has a slight glow to it.
http://www.xda-developers.com/andro...-screen-with-screen-standby-xda-developer-tv/
It is used for things like hooking up to your tv or computer to run things without having the screen on as well. I don't know if that will work or not.
I didn't have any luck changing my csc stuff, but I did have luck with ROM tool box finally freezing apps I wanted to, so well see how that plays out.
Cheers Smaw51 used your buldprop and systemUI giving it another go hopefully the reboot will stop anyway thanks
Try this in the Dialer ##4636*##
TramainM said:
Try this in the Dialer ##4636*##
Click to expand...
Click to collapse
where did you find this? Hopefully it works, my note is on the charger right now, I'll go check on it in a few minuets to see if it is still on.
smaw51 said:
where did you find this? Hopefully it works, my note is on the charger right now, I'll go check on it in a few minuets to see if it is still on.
Click to expand...
Click to collapse
Friend who dev'd for HTC amaze gave it to me completely turns off the radio
TramainM said:
Friend who dev'd for HTC amaze gave it to me completely turns off the radio
Click to expand...
Click to collapse
How do you know if it works or not? I am still getting power off during charge. After code was put in, it just wiped clean the dialer. Other codes I found I tested on my phone and tablet for various things all brought up a different screen thing.
Here are some codes I found here http://forum.xda-developers.com/showthread.php?t=1894102
*#197328640# Service Mode
*#7353# Self Test (Menu of 12 tests to use)
*#12580*369# --- Main Version (AP, CP, CSC, RF cal, HW Rev)
*#0*# another test
*#0011# service mode
*#0283# --- Loopback Test
*#232338# --- WlanMacAddress (Enable/Disable WiFi Powersave Mode)
*#197328640# --- Service Mode (Debugging, Testing. Use menu > back to go back in menus)
These look more promising:
*#7284# --- Phone Utility (USB Settings) I set both to PDA, didnt really seem to fix anything
*#9900# sysdump, has a few different things you can get for diagnosis stuff
Ill contact him to see if I can get the right one
It should be *#*#4636#*#* I have some ideas I am going to start working on. Think kernel work is needed.
Sent from my SCH-I535 using Tapatalk 2
pimpmaneaton said:
It should be *#*#4636#*#* I have some ideas I am going to start working on. Think kernel work is needed.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Yes, I believe it is kernel related, but the problem is we did not have the 4.1 kernel source code
pimpmaneaton said:
It should be *#*#4636#*#* I have some ideas I am going to start working on. Think kernel work is needed.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I was thinking it was Kernel Panics when it tried to sleep.
What's odd (in my experience with both JellyNote and the German JB) is that it doesn't happen at a specific period after the device goes idle. Once it happened 2-3 minutes later, other times my Note sat there running fine for an hour or more before suddenly rebooting. I tried both using the ROM as normal, as well as once doing a complete wipe and re-install (of JellyNote) and not installing any additional software or tweaking settings beyond the startup wizard. Didn't seem to matter, I still got reboots at random intervals while idle.
It'd be nice if Samsung rolls out an N801X rom next.
TramainM said:
I was thinking it was Kernel Panics when it tried to sleep.
Click to expand...
Click to collapse
In the v6 supercharger script there is an option to stop kernel panics and keep it from rebooting. Maybe this is the solution.
Sent from my GT-N8013 using Tapatalk 2
Have you tried it?
Sent from my Galaxy Nexus using xda app-developers app
I have put this version of Jelly Bean on my N8010.
To start with I had a couple of reboots when the tab was idle. What I have subsequently done is:
Frozen com.sec.phone 1.0
Frozen Phone 4.1.1 - N8000XXBLJ9
In settings turned Blocking Mode on
I used Titanium Backup to freeze the programs. So far after a reboot I have not had any further reboots on idle - touch wood
Ok, I am not totally sure which of my changes or combination thereof has done the trick. Am afraid I am too impatient to use the new Jelly Bean to determine absolutely.
What I will say from my experience so far is the the tab is much faster than on ICS and stable for me to use all the time. So this seems a very good temporary solution until the offical N8010/N8013 roms come along.
Using Ondemand governor in a N8010 an the moment no reboots...it seems that the problem is the pegasusq governor
Related
Does anyone have a logcat from their dead transformer, during/around the time when it died?
Has anyone noticed any trends in when it happens? I saw something about 82% battery but I think that's just a coincidence.
Please post here so we can get to the bottom of this.
Jcarrz1
I think this is dev, unless it's a hardware issue. But hopefully we'll be able to discern that.
I have had multiple sleep of death issues after rooting. When I flashed back to the stock Blob, they stopped. Every time I root to Blob V5 (I am on the most recent firmware), they come back. I tried MoDaCo's Rom - they still occurred. Trying Prime's Rom now - so far it's working without any sleep of deaths.
I was on MoDaCo's Hr4 for a few days and never had a sleep of death. Since installing Prime 1.2 I've had 3 or 4.
Since we've had completely opposite experiences I think we can safely rule out that this issue is ROM related.
I've used both those roms and never had a sleep of death. But I also used the root method without the v5 blob, just the standard GingerbreakBB.
I've had one sleep of death incident, using unrooted stock Transformer configuration.
mine case: downgrade back to 8.2.2.6 using SD method (EP101_SDUPDATE.zip) then Gigerbreakbb then the BLOBV5 => lots of SOD issue.
May be we must update to the latest 8.2.3.9 before break using gingerbreakbb and install BLOBV5?
BR
Blob 5 is made to work with 8.2.3.9... It will most definitely have issues with the old firmware.
I am beginning to think the issue is with one of my apps and its settings. When I am rooted, I use Titanium Backup to restore my data and maybe the reason for the SOD is because something in an application isn't playing nice with Honeycomb... Obviously when I am not rooted, I cannot restore the settings and thus no SOD.
I just flashed back to root with Blob V5. Going to see if there are any SOD issues before installing apps... Will probably install one by one to try to see if I can find the problem - A PITA, but I really want the SOD to stop.
Had it with latest asus Update, no root and 40% brightness + wifi sleeps while screen is off. Lockscreen was enabled.
Sent from my Nexus One using Tapatalk
Edit:
Had another one after changing wifi sleep policy. I think it is wifi related.
The-Nazgul said:
Had it with latest asus Update, no root and 40% brightness + wifi sleeps while screen is off. Lockscreen was enabled.
Sent from my Nexus One using Tapatalk
Edit:
Had another one after changing wifi sleep policy. I think it is wifi related.
Click to expand...
Click to collapse
Other threads are pointing to the WiFi scanning be enabled. I have flashed back to MoDaCo Hr4 (because it was more stable for me than Prime 1.2) and also disabled WiFi notifications and will report back if/when I get a SOD.
Unrooted, getting about one or two of these a day depending...... seems to happen more if I've left it sleeping for an hour or more.
Putzy said:
Unrooted, getting about one or two of these a day depending...... seems to happen more if I've left it sleeping for an hour or more.
Click to expand...
Click to collapse
this could relate to wifi scanning as well. were you connected, and what are your current settings?
Thanks for participating everyone, so far there isn't a conclusive answer.
However, could someone install log collector from the market, and leave it there until the BlackSOD happens, and then upload the file? that would be super awesome. preferably someone who gets them all the time. if the last thing in the logcat is consistently wifi-related, then we're on to something.
is there any firmware version on which NOBODY has EVER had a BlackSOD? This could be worth looking in to as well.
Well, I rerooted and have installed about 80% of my apps. So far no SOD. I have a few more apps to install and I usually freeze some of the unwanted apps. Will post an update later. Also, I read on other forums that fancy widget caused issues like this on other tablets. I had been using beautiful widgets I wonder if the way that tries to access wifi causes issues.
The apps I have yet to install are:
Watchdog lite, beautiful widgets, adfree android
Sent from my Transformer TF101 using Tapatalk
Just had one while wifi was disabled! I guess that makes it less likely that wifi causes the problem.
Next time I will upload a logfile!
Sent from my Nexus One using Tapatalk
I've had 2 so far, both with Hr4 and blob v5. Battery has been at different levels, so I think thats a coincidence.
Has anyone tested on a 100% Factory reset device (either with a custom or stock ROM?) That should help rule out any apps which may cause the problem.
FWIW, never had this issue (have run Stock, HR1 -> HR4 & Prime V1.2)
so far no SOD after a clean tstart
Had a SOD this morning on Hr4 so I will run Log Collector today and hope to catch another. I'm assuming that Log Collector is continually writing to my Gmail draft so it should be there after the full reboot? Doesn't seem like it will let me mirror logcat to a file on sdcard...
sent from a device using an app
I realize this isn't the least bit helpful, but after having several SoD issues, and trying all the fixes (and then undoing them), I haven't had the issue for a week now. Mine would do it sporadically -- it would happen once in a day, and then 3 times in a day -- and the only thing I've left changed is disabling the lock screen, but I think that's just coincidence. This will be a hard one for Asus to nail down.
Hopefully someone produces a helpful log for Asus, I'm sure some non-XDA people may think they have a dead tablet rather than one they have to force power down and reboot.
had my firs SOD today.
running prime 1.2 US. battery at 96%. wifi on.
spuniun said:
Had a SOD this morning on Hr4 so I will run Log Collector today and hope to catch another. I'm assuming that Log Collector is continually writing to my Gmail draft so it should be there after the full reboot? Doesn't seem like it will let me mirror logcat to a file on sdcard
Click to expand...
Click to collapse
So it does not seem that this app will work because it only collects logs in real-time, does not store them for later analyzing. What else can I use other than leaving adb logcat running?
sent from a device using an app
I recently wiped all of my phone (factory+cache) and installed the latest 4.0.3 official update from SAMSUNG.
I also enabled the FULL DISK ENCRYPTION while doing this.
I am now waiting to decrypt it to see if this problem persits if I turn the encryption off.
The problem is that if I leave my phone locked for a few hours/minutes it randomly won't turn on the screen again, when I press the power button.
A hard reboot (holding) fixes this everytime. But this is not a fix, we all know.
It never happened on Gingerbread 2.3.5.
I am beginning to suspect there's a bug in the ICS firmware, although it's 4.0.3, it could slip through.
It's hard to say what's causing the trouble. I have connected the phone to USB now. Waiting for the symptom to show again. I assume I can get a good logcat.
adb shell logcat > logcat.txt
So I'm waiting for an error / event of POWER button at this moment, and will keep logging till it produces the same error again.
Regards,
That's called the black screen of death. It's an ICS bug. For now, rebooting seems to be the only solution ice seen on xda.
Sent from my GT-I9100 using xda premium
a67543210 said:
That's called the black screen of death. It's an ICS bug. For now, rebooting seems to be the only solution ice seen on xda.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
I can't believe this ! Is this a SAMSUNG or an Android/ICS problem ?
My version is:
4.0.3
IM74K.XXLPQ
Any custom ROMs addressed this issue or how can you avoid this on ICS? Is the only solution to go back to Gingerbread ?
Hi guys, hope your well.
I am having a similar issue too. I am on Hydrogen AOKP Rom, and I get exactly the same. However, apart from just the blank screen, my phone gets extremely hot too.The only way to get it back on is to remove the battery. Very annoying!!
I cant seem to figure what it is. I have tried to search here on XDA for the resolution but to no avail. Could it be the Kernal? The Modem? Tweaking via SetCPU? or a combination of all? Atleast if I could get pointed to the right direction that'll be a start! lol
Are you guys getting the overheating problem too?
Its a bit like continual posting in the wrong forum nobody knows why ??
jje
rumz82 said:
Hi guys, hope your well.
I am having a similar issue too. I am on Hydrogen AOKP Rom, and I get exactly the same. However, apart from just the blank screen, my phone gets extremely hot too.The only way to get it back on is to remove the battery. Very annoying!!
I cant seem to figure what it is. I have tried to search here on XDA for the resolution but to no avail. Could it be the Kernal? The Modem? Tweaking via SetCPU? or a combination of all? Atleast if I could get pointed to the right direction that'll be a start! lol
Are you guys getting the overheating problem too?
Click to expand...
Click to collapse
No overheating (yet) you can help if you can keep logcatting through usb cable till it lock/standby freezes and your screen won't come on when pressing power ..
Install SDK + Drivers, write in commandprompt:
adb shell logcat > save.txt
Wait for the error / freeze where screen won't come on.
Then paste here or upload somewhere might contain a lead to a solution!
Double - sry - galaxy forgot login
It's a kernel issue. I had exactly the same problem. Flash the latest siyah kernel that should sort it out. I went through 10 different Roms till I worked it out
Sent from my GT-I9100 using XDA
thedadio said:
It's a kernel issue. I had exactly the same problem. Flash the latest siyah kernel that should sort it out. I went through 10 different Roms till I worked it out
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
Nah!
It's there on all the kernels. I myself am a Siyah user.
I moved back to GB for this weird and terribly serious issue, but that time i didn't know it was a common problem.
This is ICS' best feature for sure.
I really CAN NOT believe how this issue is NOT yet known well and haven't brought in to front line. Google knows about it and yet I haven't seen any official statements about it. How ****in unbelievable or not perhaps? Google way?? Well **** it.
Utter Nonsense. What i wonder is, really, does any Android user actually use the phone but show off only??
I can almost reliably reproduce this problem.
I'm on ICS LP7 stock XEU version. When I have downloads running with Ttorrent, there's an almost 50% chance that the screen will not turn on once it goes to sleep. The phone is not frozen as my downloads continue to run; just that nothing is being shown on the display. If you hold the volume down button you will feel the phone vibrate to tell you it went into silent mode, which means the phone didn't freeze. After about a minute or so if I try again everything will work as normal, until I put the screen to sleep again.
gtcardwhere said:
I can almost reliably reproduce this problem.
I'm on ICS LP7 stock XEU version. When I have downloads running with Ttorrent, there's an almost 50% chance that the screen will not turn on once it goes to sleep. The phone is not frozen as my downloads continue to run; just that nothing is being shown on the display. If you hold the volume down button you will feel the phone vibrate to tell you it went into silent mode, which means the phone didn't freeze. After about a minute or so if I try again everything will work as normal, until I put the screen to sleep again.
Click to expand...
Click to collapse
Do the logcat as I provided the correct command to extract it to a file.
Then do your torrent thing, and make it crash- so we can debug !
Used to happen, since I installed latest hydrog3n-ICS rom (13-05) never had those again!
have you uv your phone so much?
i tried to uv my phone so much, and it can't turn on screen when i lockscreen about 1min
sunshean said:
have you uv your phone so much?
i tried to uv my phone so much, and it can't turn on screen when i lockscreen about 1min
Click to expand...
Click to collapse
uv?
ultra-violet ? is my phone in danger of skincancer ?
dezzadk said:
I recently wiped all of my phone (factory+cache) and installed the latest 4.0.3 official update from SAMSUNG.
I also enabled the FULL DISK ENCRYPTION while doing this.
I am now waiting to decrypt it to see if this problem persits if I turn the encryption off.
The problem is that if I leave my phone locked for a few hours/minutes it randomly won't turn on the screen again, when I press the power button.
A hard reboot (holding) fixes this everytime. But this is not a fix, we all know.
It never happened on Gingerbread 2.3.5.
I am beginning to suspect there's a bug in the ICS firmware, although it's 4.0.3, it could slip through.
It's hard to say what's causing the trouble. I have connected the phone to USB now. Waiting for the symptom to show again. I assume I can get a good logcat.
adb shell logcat > logcat.txt
So I'm waiting for an error / event of POWER button at this moment, and will keep logging till it produces the same error again.
Regards,
Click to expand...
Click to collapse
Hi,
It happened to me as well after the ICS update and I tried to plug the AC charger to see what happens, and surprise...the screen turned on .
It's not a fix (especially when away with no accessories) but it's better than nothing, hope this helps; also you should try plugging the USB cable. Tell me if it helps.
Thanks,
dezzadk said:
uv?
ultra-violet ? is my phone in danger of skincancer ?
Click to expand...
Click to collapse
Haaaaahahah! He means under volting. I don't know if you was serious lol but just saying. I'm on cm9 but don't have this problem :-/.
Sent from my GT-I9100 using xda premium
Yep,I mean under volting, you need to look your kernel, and I think it doesn't work fine because your kernel has under volting so much.
Sent from my GT-I9100 using Tapatalk
Reading around and installing load monitor from play store should fix this until a better solution is found
Sent from my GT-I9100 using Tapatalk 2
Best solution is to stay on GB because is more stable, until ICS gets better cooked!
***TL;DR***I know now that 4.3 has this bug and it is something we will deal with. I understand the causes, but the problem is buried in the kernel vs the ROM, you can still read my semi adventure but I wanted to make this edit to save you time if you think I found an answer. Overall WIFI is a huge trigger for screen wakes along with shotty or chattery reception.***
First off SlimBean is pretty much the best ROM I've dealt with, so many options, faster then I've ever experienced, and sharp looking. I've been sharking around these forums for 2 years afraid to ever make a name and post due to my lack of knowledge. I love the search options for finding answers that this forum offers to visitors and I've surely used it to root an old AT&T Atrix 4G and now my current DD the Glacier. Now I feel as though I have a little bit of sense of what the heck I am doing and would like to share my path to figuring out how to make SlimBean 4.3 work for me. Who knows maybe this may help some people that have similar problems.
The problem::: On a SEMI clean install of [UNOFFICIAL]SlimBean 4.3 \\ Nightly \\ 22.08.2013 I noticed the Glacier in standby would suddenly illuminated with light although the screen was black. It was enough to light to catch my eyes as I was starting to fall asleep. I ignored it until morning then paid attention to it happening all day at work on and off constantly with the WIFI off and just mobile network, then mobile network off, reboot, nothing seemed to help and I couldn't bare the thought of the phone's screen just on all the time.
After reading threads about HTC's possibly having bad screen made from Taiwan I was in disbelief that it was the Hardware as coming from a year old version of MIUI, I never had a problem with the screen. Leading to the idea it must be a software issue / user issue in which I must of rushed the install of the ROM or it's a quirk in 4.3.
Prior to reinstalling the same ROM, I went with trying other similar ROM's finding [UNOFFICIAL] Carbon 4.3 \\ Nightly \\ 26.08.2013 literally was just released, also a super customizable fast ROM. Everything went smooth until I played music through headphones and the illuminated black screen was back. Now I'm definitely convinced it's the software so I move on to the source code of these ROM's ev_glacier-nightly-2013.08.27.
Ev_glacier-nightly-2013.08.27 Had no screen wakes after 2 hours idle on mobile network only. I wasn't in a location with WIFI as I believe a network with a lot of information chatter may be causing these standby black illumination wakes. Back to SLIM.
SUPER clean install. 1) Format SD card completely 2) fresh download w/ checked md5 of Slimbean 3) Full Wipe "wipe data factory reset" "wipe cache" 4) format/system & format/cache manually just in case 5) Clear Dalvik 6) And fix permissions since although I believe it has no point but it's just so easy to click just in case. Probably doing things double.
Here I am now.. Slimbean is back and nothing but the .zip has been installed along with updating Nova Launcher. I am waiting to reinstall GAPPS so I can first isolate this problem within the ROM itself. What I am noticing is on just mobile network 2g/3g/2g+3g I do not get the phantom wakes, but with WIFI on it so far is only happening about 20-30 seconds after the phone drops into Standby and at least now it's not long lasting, just a few screen black flashes and it's gone. The entire 20 minutes or so I've been typing this, keeping an eye on the screen it's been quiet. Progress is being made.
Now I have thoroughly read up on and used Better Battery Stats, Wakelock detector, and Greenify to help isolate problems prior to the clean install and am waiting to install any Google apps (play store) up until tomorrow so I can pay more attention to my phone and make sure it's just a WIFI wake lock causing the screen to illuminate black. Also was toying with the idea of installing 3.0.64 kernel. I'm curious as to see if it's not just the WIFI wake lock, but all wake locks that actually wake the screen. Once I'm ready to install the play store I'm going to start combing through the device using these fantastic guides and the aforementioned apps...
[GUIDE] The Total Newb's Guide to Wakelocks ::: [HOW TO] Fix Your Skyrocket's Battery Life ::: [GUIDE] Insanely Better Battery Life When Idle
My goal with this long post is to share my experience and also commended these developers on these awesome ROM's. I will post much shorter updates on how I fixed or found the exact problem. Mainly after searching I saw similar issues but not this direct "random black illuminated screen" problem. Thanks, and be sure to call me out on anything contained in this post.
the waiting game
At 9 hours from 100% charge, I'm at 40% battery with on 1.5 hours of screen time. I went through all my settings and disabled all sounds and haptic feed back. I have yet to install any apps and am running off the bare bones of just the ROM. WiFi & 4g mobile data were on all night with the screen flashing only if I used it then locked it with the power button.
Thinking I can live with these timeout 2-5 flashes, I start browsing the forum from my phone, put it down to get ready for work, look back at the phone as it is flashing black screen rampantly on it's own. Then it holds the black screen for a solid minute or two.
WiFi chatter wake lock must be doing this... Reboot to recovery - wipe dalvik - wipe cache - reboot phone. Now to test just 4g network, flash happens on first screen lock, but not as rampant. Hmmm. My next step will be to wait for full battery drain / charge then I want to try the kernal I mentioned above. 3.0.64 kernel.
Funny stuff
Realizing the Kernel I wanted to flash doesn't work with 4.3, I hope at least some of the 86 people that viewed my post got a laugh. Even the older version of SlimBean causes the random screen flashes and the screen on while charging even with the ROM settings for such off. WiFi seems to be the greatest cause. It's as if wakelocks are actually being represented as screen flashes since the kernel is so powerful.
I just don't want to use the CM ROM...
I'm going to dig around the forums further and type in different key words of my problem just to make sure I didn't miss someone already answering this question. Slim has all the functions I always wanted out of my droid and I'm dead set to make it work...or just live with screen flashes I guess.
Hope this is a comedy for someone.
only other link
I've found on the issue I have.
http://forum.xda-developers.com/showthread.php?t=1148057
Non-Stop ROMS
1) SlimBean 4.2 & 4.3 Both have this black screen flicker / black screen wake / black screen on while charging.
2) Carbon 4.3 Had it black screen on while listening to music / black screen constant while charging
3) Evolve 3.3 based of 4.3 seemed to work fine, but I wasn't a fan of the larger Icons and screen, similair to CM 4.3 so I didn't leave it long enough to test...
4.3 CM 4.3 black screen wake almost constant / black screen on while charging... also didn't last long to really test everything.
I am down the river if I want this to just go away. I have installed all these ROM on a completey clean formated SD card each time
I'm sticking with SlimBean as it has the looks and reacts like I expect my phone to. After doing some more searching and after a little time has passed for more 4.3 development there may be a kernel that will work better for me.
Oh here is another dead end I've found... http://forum.xda-developers.com/showthread.php?t=2185747&page=3 [KERNEL] Fixed the flickering screen problem,CM10,CM10.1,SENSE3.6 4.0 4.1 That goes no where...
wifi
WiFi is the biggest culprit for the random screen wakes. I've just been living with it since I dig the slimbean 4.3 ROM so much. Thought I might pop back on here to make some closure. I worked on removing some apk's from the already minimal gapps I installed and will soon start a separate thread on just that. As long as after searching I don't find the same info I figured out.
I think you've got the screen flicker bug.
Try flashing the .69 kernel, it claims to stop the flicker.
Also I know it's got something to do with the WiFi. I know a little about it though.
Sent from my myTouch 4g using xda app-developers app
thanks for the response
N_otori0us_ said:
I think you've got the screen flicker bug.
Try flashing the .69 kernel, it claims to stop the flicker.
Also I know it's got something to do with the WiFi. I know a little about it though.
Sent from my myTouch 4g using xda app-developers app
Click to expand...
Click to collapse
I see you all over the place when it comes to Glacier threads. Today at work I was searching around for a download link. I read through a ton of other ROMS threads hoping it was buried in the comments somewhere. So far I only turned up and old thread with a dead link and a couple of other threads you mentioning to other people to download the .69 KERNEL which I am guessing the full version number is 3.0.69, if it's not then there may be my first problem in finding the link...
*edit
this is the main thread I keep finding, you have so many other kernels on there
http://forum.xda-developers.com/showthread.php?p=43983635&highlight=+69#post43983635
I have a little idea about the screen flicker.
A member called zyGh0st told me. I've pmed Elgin but no response.
I'll pm coderzs too Lil.
Sent from my myTouch 4g using xda app-developers app
reading about kernals
N_otori0us_ said:
I have a little idea about the screen flicker.
A member called zyGh0st told me. I've pmed Elgin but no response.
I'll pm coderzs too Lil.
Sent from my myTouch 4g using xda app-developers app
Click to expand...
Click to collapse
All the Kernels in the Glacier Bible page you have been keeping up seem old. I'm nervous to try one since they obviously seem like they won't work. I'm game to try what ever and post on here my progress so if anyone else stumbles upon the issue they can guide their way through it.
I've been searching "kernel 3.0.69", "kernels 4.3 roms", "jb rom kernel", "4.3 jb kernel", sometimes including the term "glacier" or "MT4G" with little to no luck between XDA and just google itself. I always just find ROMS that just mention the kernel but have no downloads.
Reading your older posts I see that youve already tried the kernel.
Sent from my myTouch 4g using xda app-developers app
K is for kernel
N_otori0us_ said:
Reading your older posts I see that youve already tried the kernel.
Sent from my myTouch 4g using xda app-developers app
Click to expand...
Click to collapse
I tried 3.0.64 kernel, not this mysterious .69 kernel you have mentioned. If you have a link or mirror of it I'll be glad to give it a go.
___________________________________________________________________________________________________
Found how you added the 2 kernels to the Bible page, I just flashed .64 again and I'm nothing but bootloops. I'll give .62 a chance since now I'll have to re-flash Slim.
___________________________________________________________________________________________________
make the double bootloops with either of those 2 kernels. I waited like 5 minutes, restarted the phone to see if it would boot and it just stayed on the slim splash screen. Of course I wiped dalvik and cache before installing either.
Bottom of your 5th post
Sent from my myTouch 4g using xda app-developers app
addiction
N_otori0us_ said:
Bottom of your 5th post
Sent from my myTouch 4g using xda app-developers app
Click to expand...
Click to collapse
Oh yes, I head that already downloaded on the SD but the name CM_SENSE made me think it was a ROM not a kernel. The .66 kernel link is dead, but the .58 flashed & works but there is still the flicker on 4.22 SlimBean. 4.22 is so lame compared to 4.3. Even if there wasn't a flicker on 4.22 I don't think I'd keep it. Those big ICONS are just too much. I think that's why I like Carbon also. Anywho...
My addiction to messing with my phone is always in conflict with work. As if I don't have enough problem solving to deal with outside of cell phones.
I am going to try out the recovery I see in your signature, Recovery : 4EXT 1.0.0.5 RC8, just to see if it makes a difference. If you have the same phone without the same problem I must then eliminate the different variables to find the true problem. I found a "how to" and am either going to put in the time in a couple of hours or tonight. Then I'm going to start the rounds of testing ROMS / KERNELS all over again and I'll post my findings here.
I appreciate the back and forth, I actually got a can't thank anymore message because I used up my 8 yesterday~
Living with it
I've been just living with the screen flash. The ROM is just to sweet to give up. At some point if there it a completely stable 4.3 I may upgrade.
On a regular work day I don't have any available WIFI, so I toggle it off then reboot the phone every morning. I usually get a random screen flash everytime I manually lock / turn the screen off and that's it. With WIFI on I get random flashes at random rates and for random lengths.
Playing music invokes these random black screen wakes also, I've stuck to my old blackberry as my MP3 player...I know that statement seems extemely wrong and against all sciences, but the 9780 bold works perfect as a music player. They had the long-press song skip in the volume button well before anyone added it to Android.
If ever I find the correct ROM / KERNEL combination, or someone else figures out the problem and I find it, I will post it here. This winter I am going to get more into understanding & compiling roms + digging through code so maybe I'll find it myself...ha!
tonyMEGAphone said:
I've been just living with the screen flash. The ROM is just to sweet to give up. At some point if there it a completely stable 4.3 I may upgrade.
On a regular work day I don't have any available WIFI, so I toggle it off then reboot the phone every morning. I usually get a random screen flash everytime I manually lock / turn the screen off and that's it. With WIFI on I get random flashes at random rates and for random lengths.
Playing music invokes these random black screen wakes also, I've stuck to my old blackberry as my MP3 player...I know that statement seems extemely wrong and against all sciences, but the 9780 bold works perfect as a music player. They had the long-press song skip in the volume button well before anyone added it to Android.
If ever I find the correct ROM / KERNEL combination, or someone else figures out the problem and I find it, I will post it here. This winter I am going to get more into understanding & compiling roms + digging through code so maybe I'll find it myself...ha!
Click to expand...
Click to collapse
Have fun man, and If you ever need help or guidance just tell us, we'll be here
I bought S4 2 months ago. Recently, it keep restarting and restarting. The battery go down from 50% to 0% when it restart. Anyone know how to fix this issue ?
Same thing over here
My S4 acted that way also.
It happened when I took burst pictures and then touch the little photo icon in the corner to see the captured images.
The phone restarted at 0% battery and got into restart loop.
Only removing the battery for a few seconds could stop this loop.
Now, I reinstalled a new ROM.
Hope it works.
Try install new recovery+ROM
There are many ways to try to fix this issue start from the least expensive :
- disconnect wireless
- remove sd card
- remove the battery and the sim card and reinsert them
- check if your battery is swollen and replace it if so
- try a factory reset
- if you have a custom rom try stock rom
good luck
..
difyel said:
There are many ways to try to fix this issue start from the least expensive :
- disconnect wireless
- remove sd card
- remove the battery and the sim card and reinsert them
- check if your battery is swollen and replace it if so
- try a factory reset
- if you have a custom rom try stock rom
good luck
Click to expand...
Click to collapse
- i already removed sd card, but it keep restarting.
- Just did, didnt work.
- My battery is fine, lots of people are suffering this problem so i think this is software, firmware, etc. problem.
- already did, twice.
- I havent touched anything about ROM.
Logcat or kernel dbug messages may be useful in this cases
Sent from my GT-I9505 using XDA Premium 4 mobile app
smep said:
Logcat or kernel dbug messages may be useful in this cases
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
can u give me more detail about those 2?
thinhtyt said:
can u give me more detail about those 2?
Click to expand...
Click to collapse
Those are diagnostic tools, they log every thing including fatal errors that cause the system to restart.
Install from play store
Sent from my GT-I9505 using XDA Premium 4 mobile app
Getting the same-ish problems. Phone is rebooting like mad, doesn't matter what ROM I have installed at all. Not sure if it's an issue with my battery but it seems that it could be a voltage/current issue that causes the phone to die for just long enough. As everyone knows if you pull the battery out whilst the phone is on, then put it back in after a second or two, the phone tries to reboot without you ever having pressed the power button
I just got 2 new batteries. Gotta wait about a week for them to come. Gonna do some testing, see if it stops the issues. If not, then it's a hardware issue and I'm gonna see if I can get it replaced under warranty.
How to use logcat
My problem seems to be different compared to the others in this thread, but don't want to start a new thread. Currently my S4 is lying in the office all week, because I use another phone, when I am outside of the office. It's equiped with pre-rooted MGA, but I also tried various other ROM's, with different ways of flashing e.g. CWM, Odin etc. also no wipe/full wipe. The problem is that as soon, as I take the phone away from the office, I have several restarts a day, which is never happen in the office. This is strange!
My thoughts are, that some app is responsible.
questions:
- can I find out in using logcat? / How to use logcat?
- There is a description to boot the phone into safe mode http://skp.samsungcsportal.com/integrated/popup/FaqDetailPopup3.jsp?cdsite=my&seq=871239. It's not working for me. Has anybody tried that?
- Any other ideas?
schlork said:
My problem seems to be different compared to the others in this thread, but don't want to start a new thread. Currently my S4 is lying in the office all week, because I use another phone, when I am outside of the office. It's equiped with pre-rooted MGA, but I also tried various other ROM's, with different ways of flashing e.g. CWM, Odin etc. also no wipe/full wipe. The problem is that as soon, as I take the phone away from the office, I have several restarts a day, which is never happen in the office. This is strange!
My thoughts are, that some app is responsible.
questions:
- can I find out in using logcat? / How to use logcat?
- There is a description to boot the phone into safe mode http://skp.samsungcsportal.com/integrated/popup/FaqDetailPopup3.jsp?cdsite=my&seq=871239. It's not working for me. Has anybody tried that?
- Any other ideas?
Click to expand...
Click to collapse
You may have an application that response to locations through gps which give you another set of profile depend on your location, try turn gps off and see...
Sent from my GT-I9505 using XDA Premium 4 mobile app
Try to swap batteries. When phone keep restarting all the time battery is faulty. Hope it helps.
Hi guys, I tested a few days before coming back. So what I can say now
Try to swap batteries. When phone keep restarting all the time battery is faulty. Hope it helps.
Click to expand...
Click to collapse
==> It is not battery
You may have an application that response to locations through gps which give you another set of profile depend on your location, try turn gps off and see...
Click to expand...
Click to collapse
I believe that goes in the right direction, but turning off GPS did not help. But I think it must have to do with location, sometimes it is stable the whole day (same as in the office) sometimes 2-3 reboots, one after the other.
Must be an app, but how to find?
I've been noticing this problem increase over the past few months. It started when I used navigation over longer trips like an hour. The phone would all of a sudden stop responding and then just restart. I noticed its really hot when this happens so I figure it's overheating. Recently it even happens on short trips.
I'm using triforce rom 3.1 which uses agat's kernel. I have not noticed any other restart or crashing issues aside from when I use navigation. I find it important to mention that this all occurs even if the phone is not plugged in or charging.
Has anyone else noticed something like this?
I thought about taking it to sprint since i have tep, but I figure they will either just tell me it's my fault since it's a custom rom or just offer to format the phone like they do with every other problem.
Any ideas are appreciated.
Not an expert, but sounds KERNAL related....try a differant kernal...
Sent from my SPH-L720 using XDA Free mobile app
chris-allen said:
Not an expert, but sounds KERNAL related....try a differant kernal...
Sent from my SPH-L720 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the tip. I'll have to find one that still works with my older version of the rom. If nothing else, I may just wait until I have a little more time and use a new or different rom all together and see if that makes a difference.
iivisionii said:
Thanks for the tip. I'll have to find one that still works with my older version of the rom. If nothing else, I may just wait until I have a little more time and use a new or different rom all together and see if that makes a difference.
Click to expand...
Click to collapse
I just wanted to follow up and see if anyone had more suggestions or a specific kernel to try. I tried 3 different ones with the following results:
KT-SGS4-JB4.2-TW-SPR-02.20.2014 - No navigation reboots, started rebooting randomly otherwise
AGAT_GS4_v0.5.1 - Still reboots/overheats during navigation
AGAT_GS4_v0.5.2 - Still reboots/overheats during navigation
Stock. I've never had good luck on custom kernels going back to the S2 (the same devs as currently).
Really, my devices have always ran worse and with significant issues, including the one you are describing.
If that's not an option, play with the governor settings, remove any overclock, and try other ROMs.