I read all the posts about the random reboots, and seemed to me it happens when the TF goes on deep-sleep mode. So I added these 2 lines to my build.prop and have not gotten anymore reboots:
ro.ril.disable.power.collapse=1
pm.sleep_mode=2
If someone can try it, and post your results to verify, it could help others that are having this issue.
lunadomain said:
I read all the posts about the random reboots, and seemed to me it happens when the TF goes on deep-sleep mode. So I added these 2 lines to my build.prop and have not gotten anymore reboots:
Click to expand...
Click to collapse
Thanks for the suggestion. It has been how long since you add the 2 lines? My first reboot and the second one has a gap of more than 48 hours.
lunadomain said:
I read all the posts about the random reboots, and seemed to me it happens when the TF goes on deep-sleep mode. So I added these 2 lines to my build.prop and have not gotten anymore reboots:
ro.ril.disable.power.collapse=0
pm.sleep_mode=2
If someone can try it, and post your results to verify, it could help others that are having this issue.
Click to expand...
Click to collapse
What is the effect of that mod on battery life?
Sent from my Nexus S using Tapatalk
Thanks Luna d did you see where someone said gnufabio had tweeted it was a problem with the old nvidia drivers? Wondering if you came up with this independent of gnufabio's discovery..
48 hours and no reboot
luna_c666 said:
Thanks Luna d did you see where someone said gnufabio had tweeted it was a problem with the old nvidia drivers? Wondering if you came up with this independent of gnufabio's discovery..
Click to expand...
Click to collapse
No, I just thought that since some of the reports were mentioning the Deep-Sleep state, then disabling this could solve the problem. So I decided to root and modify the build.prop by adding those two lines. I haven't had a single reboot in more than 48 hours now. Before the modification I would get a reboot every 8-12 hours.
Battery Life Effect: Negible
steve.garon said:
What is the effect of that mod on battery life?
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
I didn't see much of a change in battery life. Try the mod and see how it goes for you.
Added end rebooted. Experienced only a few reboots in the past 5 days. Wiped data from HC Revolver 3.11.1 and flashed ICS last week.
Will report. The first command line sounds promising already. I don't know zilch about coding so excuse me from being nub, but shouldn't that 0 be changed in 1 because the disable function should be 'enabled' (assuming 0= enable and 1= enabled)? Sounds more logical to me.
Good catch; I edited the first post.
Martijn1971 said:
Added end rebooted. Experienced only a few reboots in the past 5 days. Wiped data from stock HC Revolver and flashed ICS last week.
Will report. The first command line sounds promising already. I don't know zilch about coding so excuse me from being nub, but shouldn't that 0 be changed in 1 because the disable function should be 'enabled' (assuming 0= enable and 1= enabled)? Sounds more logical to me.
Click to expand...
Click to collapse
Good catch, guess I made a mistake when I typed the post. Yes, it should be 1 to disable the Power Collapse.
Random reboots
I have random reboots after I close my transformer with the dock attached, i open it and both batteries are dead and it is stuck at the asus boot screen, I edited my build prop and will post my results...
lunadomain said:
Good catch, guess I made a mistake when I typed the post. Yes, it should be 1 to disable the Power Collapse.
Click to expand...
Click to collapse
Ok changed 0 to 1. Did not have a reboot in the past twelve hours, but I had them seldomly anyway. Will report again.
-edit: just had a 1st reboot within an hour of changing from 0 to 1. Happened when I left my appartment (and my wifi connection) and opened my tablet in the train. I have wifi turned of during sleep. I also upgraded YouTube app for testing purposes during that period (although I never use it) to test 720p. Not sure if it's related.
No luck for me, about an hour after editing build.prop my tablet had shutdown again.
Wished asus hurried up with an update.
rtwo said:
No luck for me, about an hour after editing build.prop my tablet had shutdown again.
Wished asus hurried up with an update.
Click to expand...
Click to collapse
I believe that sleep has nothing to do with reboots. I think gnufabio was right about the video drivers being the cause. I had a major video driver glitch that made my tablet crashed and running the glbenchmark app show loads of artifacts. Nvidia need to update their drivers...
Sent from my Nexus S using Tapatalk
72 hours and no reboot
rtwo said:
No luck for me, about an hour after editing build.prop my tablet had shutdown again.
Wished asus hurried up with an update.
Click to expand...
Click to collapse
I guess it depends on the device and apps installed. I have more than 3 days without a reboot. Before the fix I could not go more than a day without a reboot. Lets's hear from others that have tried the build.prop fix.
lunadomain said:
ro.ril.disable.power.collapse=1
pm.sleep_mode=2
Click to expand...
Click to collapse
Have docked the TF, fully charged both. Added the above two lines. Then rebooted.
I will report back the result.
wow...all night long without reboot.
I wait one day more to say it SOLVED
Sent from TF101G - Revolver 3.11
kokopopz said:
Have docked the TF, fully charged both. Added the above two lines. Then rebooted.
I will report back the result.
Click to expand...
Click to collapse
A random reboot happened after 5 hours. The two lines do not resolve the issue.
Took the tablet out of the case and it just showed a frozen boot screen and was very warm.
Hope asus fixes this soon
5 days without a reboot
sciacca75 said:
wow...all night long without reboot.
I wait one day more to say it SOLVED
Sent from TF101G - Revolver 3.11
Click to expand...
Click to collapse
I have more than 5 days without a single reboot. The build.prop trick fixed my reboot issues so far. Anyone else have good results with this?
steve.garon said:
I believe that sleep has nothing to do with reboots. I think gnufabio was right about the video drivers being the cause. I had a major video driver glitch that made my tablet crashed and running the glbenchmark app show loads of artifacts. Nvidia need to update their drivers...
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
This might be the issue for some. I can see a little graphical glitch sometimes when opening the Youtube application, but then it goes away after a split-second. Maybe there's different hardware revisions of the Transformer, and some have a version that's being affected more than others?
I got even a worse problem! It kept rebooting itself continuously on the "Eee Pad" logo! I had to press the Power+Volume Down to shut it down then power it on again normally!!
I don't know exactly how long it was rebooting... I came back from work and saw it like that!
Related
I found this while searching on google. I take no credit for this, but am posting it here so that you can use it too.
Basically it enables airplane mode and disables it at boot. It doesn't add any time to boot, because it coincides with the Media Scanning.
All you do is install it and forget about it.
Anyway, heres the link:
http://forum.xda-developers.com/showthread.php?t=938677
Ignore that it says 2.1 only... Works just fine on my ROM.
Sent from my Captivate
Thanks.
Sent from my GT-I9000
I actually had this installed for a couple weeks now. Phone boots and then goes into airplane mode. I did love the one time where my phone booted up, I got a phone call right and forgot about the airplane mode and it kicked me off the call!
It won't download to my phone and I'm stuck at work. Can anybody upload it here or post a drop box link for me? Thanks!
Edit: Forgot I can use Astro for the download.
Mike, what do you think of this explanation and fix? It is interesting to read there why this happens, if nothing else. I look forward to your ROM fix tonight!
I actually have 2 tasker events setup that takes care of this nearly transparently. On device shutdown tasker sets airplane mode and clears it on boot.
I just have to do it manually if I get some kind of random reboot or sleep/charge death.
reinbeau said:
Mike, what do you think of this explanation and fix?
Click to expand...
Click to collapse
It might be a problem if you turn off GSM on an at&t phone.
Sent from my Captivate
MikeyMike01 said:
It might be a problem if you turn off GSM on an at&t phone.
Sent from my Captivate
Click to expand...
Click to collapse
Yeah. That could be problematic. I just did it... Next time I read the WHOLE thread first.
thx for sharing , I am curious tho , how many ppl have this issue can anyone give there s ?
I am 13% but I spend lots of tiem in the basement so thats about normal ...
DAGr8 said:
thx for sharing , I am curious tho , how many ppl have this issue can anyone give there s ?
I am 13% but I spend lots of tiem in the basement so thats about normal ...
Click to expand...
Click to collapse
I get it every once in a while. I usually check after every reboot.
MikeyMike01 said:
It might be a problem if you turn off GSM on an at&t phone.
Sent from my Captivate
Click to expand...
Click to collapse
kAh, see, I know so little about cell signals and how they worked that went right over my head (whoosh!)
harpo1 said:
I get it every once in a while. I usually check after every reboot.
Click to expand...
Click to collapse
ok and what is your percentage ?
I only realized this was an issue sometime last week and when I checked it was 50%.
Toggle airplane mode and within 10 mins it dropped to 38% and then went down to 17% a few hours later. But since then everytime I unplug or reboot I toggle airplane mode and most days it's at 0% ~ 5%
DAGr8 said:
ok and what is your percentage ?
Click to expand...
Click to collapse
If I catch it right away it will go down to 0 by days end. If not and I catch it later it varies.
thanks for the link! i'm just curious though, is there any reason why this signal bug hasn't been addressed at the ROM level? from my brief searching it seems like it occurs on most devices.
aadvanced1 said:
thanks for the link! i'm just curious though, is there any reason why this signal bug hasn't been addressed at the ROM level? from my brief searching it seems like it occurs on most devices.
Click to expand...
Click to collapse
I think including the apk in future ROMs seems a definite possibility as this fix released very recently.
After recent update, within 24hrs, my transformer has frozen completely three times. This is where I have to hold down the power 10+ sec and turn the unit back on. One time, about 40min watching a video via hbogo website. One playing a game (walkabout) and another time, just playing mp3 from the main screen via a widget.
Has anyone else experience this? Never happened on prior firmware versions.
Keyboard flash problem
I don't know if this can help: after firmware upgrade my browser crash if i try to tipe something in a flash animation, keyboard isn't show and then crash.
Exactly the same experience here: with 3.01 I had no problems at all; since OTA update 3.1 two days ago 'sleep of death' (shutdown in sleep mode) all the time!
Very annoying, according to other threads/ forums SOD was SOLVED for couple of guys with 3.1 update - I just received my SOD with 3.1!
Thanks Asus; I do hope someone/ somewhere is working on a fix!
In the meanwhile: any help/ solution for SOD (except downgrading/ rooting) would be very wellcome!
TF101, US, stock 3.1 unrooted
Same here with some Apps. MyLibrary was working fine on a pdf, now it freezes and crash all the time. Impossible to read anything anymore.
Battery seems to be drained faster too.
Since I have gotten the update the tablet is very sluggish. It was perfect before. I had no light bleed and it was very smooth. Now I have a ton of light bleed and it is so sluggish it almost takes 4 mins to connect to the internet. Anyone know the customer support number?
lukesjr said:
Since I have gotten the update the tablet is very sluggish. It was perfect before. I had no light bleed and it was very smooth. Now I have a ton of light bleed and it is so sluggish it almost takes 4 mins to connect to the internet. Anyone know the customer support number?
Click to expand...
Click to collapse
software has nothing to do with your hardware screen showing more lightbleed, other than if the brightnessis higher which may show it better.
superevilllama said:
software has nothing to do with your hardware screen showing more lightbleed, other than if the brightnessis higher which may show it better.
Click to expand...
Click to collapse
I don't disagree, but the fact is that I didn't see it before now it is terrible. I thought I had a "good one". Oh well.
In general last update has improved performance, allows more variety ( file types) in video streaming from my server, slightly better browser performance and slightly better wifi reception, however I have noticed a few lock ups that were not there before last update. Long Power button hold required to recover.
I'm having the freeze problem in Firefox after the update. it will work for a bit, but some sites will cause the tablet to lock up and I have to do the power off reboot. The stock browser is working fine.
On another forum they were saying it's pure superstition, but..: turning OFF the auto brightness has prevented sleep of death on my Transformer (SODs since update 3.1) allready about a day!
I know people say it's nonsense, but for anyone else struggling with auto shutdown in sleep mode problem; give it a try!
mllk said:
After recent update, within 24hrs, my transformer has frozen completely three times. This is where I have to hold down the power 10+ sec and turn the unit back on. One time, about 40min watching a video via hbogo website. One playing a game (walkabout) and another time, just playing mp3 from the main screen via a widget.
Has anyone else experience this? Never happened on prior firmware versions.
Click to expand...
Click to collapse
I've had four freezes, all in Press Reader tablet edition, and was thinking they were related to that app specifically, but maybe not. Reason being, my wife got her first freeze last night playing angry birds.
My freezes in Press Reader are not caused by the update, though, as two of them happened before the update was released. Also, I've discovered though that it is only the UI that is freezing, because on one freeze I had internet radio playing, and it kept playing for multiple minutes after the UI for froze.
More on my Press Reader freezes here:
http://forum.xda-developers.com/showpost.php?p=15741085&postcount=7
Do freeze issues go away if you clear all caches / factory reset?
Reason I ask, is this has helped me in the past, so I always do one, including right after this recent OTA update...
Sent from my Transformer TF101 using XDA Premium App
Huh, I've not had any problems. My 32gb TF is a B50, and dock is a B60. I usually have it connected to the dock.
I've had my ASUS Transformer for about 4 days now, never had any freezes yet, not with nor without the update (updated yesterday).
mike5065 said:
Do freeze issues go away if you clear all caches / factory reset?
Reason I ask, is this has helped me in the past, so I always do one, including right after this recent OTA update...
Sent from my Transformer TF101 using XDA Premium App
Click to expand...
Click to collapse
Can't speak to the other people, but I'm not trying because it's such a [email protected]*dy hassle to do a factory reset, when there's no way to back everything up in one go without root access.
Backup is definitely a major shortcoming of Android.
+1 to the sleep of death issue aft the 7/16 update. Screen will go off and tablet will either reboot or need a reboot.
I have had my auto brightness off since day 1, kept default brightness, and have been lucky with no issues. Still on 3.1.
Sent from my Transformer TF101 using Tapatalk
monkespit said:
I have had my auto brightness off since day 1, kept default brightness, and have been lucky with no issues. Still on 3.1.
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
3.1 is the latest.. of course you're still on 3.1
Try changing the rom and kernel. The Netformer kernel seems the fastest and smoothest. I had the screen freezes also. Running Clem's v3rom for 8.4.4.11 then flashed the Netformer over instead of using Clem's kernel.
avlon said:
+1 to the sleep of death issue aft the 7/16 update. Screen will go off and tablet will either reboot or need a reboot.
Click to expand...
Click to collapse
We're not talking sleep of death here, we're talking lockups while the tablet is active. Totally different issue, or at least totally different symptom.
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!
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
Since 20140415 nightly update (installed via CMupdater) I'm experiencing the Phone Problem. The translated German text would be
"there was a problem with your phone's modem, the device needs to be rebooted..."
I've had those before, but to a small extend. Now it's more like: it takes around 30 Minutes from reboot until the "Problem" reappears.
I'm sorry, I cannot post to the dev-thread, yet. If any logs are needed, I'd update back to 20140415 or 20140416 (where this also happened) and try to grab'em.
EDIT: it might be important information: I've come from the "full" nightly "11-20140407-NIGHTLY_mb526", then used cmUpdater on the 14th, the 15th and the 16th April (so: the last three days), at least that are the files present in my /sdcard/cmupdater folder. The problem has appeared yesterday.
Question: if I do incrementals, will I have to update every day?
oops - it seems not to be the ROM I guess
As I didn't have those problems with 20140407, I downgraded to that version. Seems it didn't have an effect - just about half an hour after downgrade, I had the "Problem", again.
I'll reboot once and if the "Problem" reappears at the same rate, I'll do a full-wipe reinstall.
St0fF said:
As I didn't have those problems with 20140407, I downgraded to that version. Seems it didn't have an effect - just about half an hour after downgrade, I had the "Problem", again.
I'll reboot once and if the "Problem" reappears at the same rate, I'll do a full-wipe reinstall.
Click to expand...
Click to collapse
It is a hardware problem of the Defy, it will go away with time.
hotdog125 said:
It is a hardware problem of the Defy, it will go away with time.
Click to expand...
Click to collapse
I'm having this since 3 days and I'm barely reachable because of that - what are the experiences, how long may it take until this goes away?
St0fF said:
I'm having this since 3 days and I'm barely reachable because of that - what are the experiences, how long may it take until this goes away?
Click to expand...
Click to collapse
For me, the system stabilises after 36 hrs of uptime.
Defy / temporary failure
hotdog125 said:
For me, the system stabilises after 36 hrs of uptime.
Click to expand...
Click to collapse
That sounds really weird! After it stabilizes - when does the problem return? Any idea what caused this effect?
mklmkl said:
That sounds really weird! After it stabilizes - when does the problem return? Any idea what caused this effect?
Click to expand...
Click to collapse
It doesn't return. Hence I said the system stabilizes.
Sent from my Nexus 7 using Tapatalk
Try to flash new modem.Latest or just different.Try BasesbandSwitcher .I Had simillar problems with CM10 and I dont know how exactly i solved it - flashing,switching,trying...Some says that CM ROMs dont change the modem because it have no modem in CM ROMs.
That's the infamous RIL bug. Try disabling and re-enabling location. Doesn't make much sense, but fixed it for me.
propov said:
Try to flash new modem.Latest or just different.Try BasesbandSwitcher .I Had simillar problems with CM10 and I dont know how exactly i solved it - flashing,switching,trying...Some says that CM ROMs dont change the modem because it have no modem in CM ROMs.
Click to expand...
Click to collapse
That's what fixed it for me: I reflashed to factory, then installed cm10/cm11 freshly.
dau_ said:
That's the infamous RIL bug. Try disabling and re-enabling location. Doesn't make much sense, but fixed it for me.
Click to expand...
Click to collapse
Thanks for that information - I'll try to remember next time I get banged by this.
Another search result
[email protected],
i just thought about perhaps creating another thread that may be made sticky, collecting all possible reasons, explanations and most likely workarounds for the RIL Bug - and I found this answer:
http://forum.xda-developers.com/showpost.php?p=50830467&postcount=5
It says undervolting might be a factor. My Defy is undervolted. So I'll try to figure out some less extreme settings, as RIL just reappeared on my phone.
P.S.: I couldn't find that post originally, as at that time I wasn't aware of the bug's name - searching for "RIL bug" in fact returns a lot of results.
St0fF said:
That's what fixed it for me: I reflashed to factory, then installed cm10/cm11 freshly.
Click to expand...
Click to collapse
that's the only thing which helped me too. many rom's worked okay for me and had no RIL reboots ever, but when i've tried to use them again instead of newer ones i tried - i got constant reboots. reflashed to factory and no more ril's again.