Depreciated - use Alpha 0.5 instead
The following is a fix posted by Dalingrin to address a slow charge issue and SystemUI force closes when disabling notifications affecting all Touchpads.
To install -
Place the fix zip in the root of your Touchpad's memory
Reboot your HP Touchpad
Select ClockWorkMod
Select install a zip from sdcard
select the zip and install
Reboot system.
Download Links (Fixed as of 1/18/12 3:55PM EST) -
http://goo-inside.me/roms/teamdouche/tenderloin/alpha/update-charger_systemui_fix-alpha0.zip
Credit goes to Flemmard for the SystemUI fix
Having trouble accessing your Touchpad's Memory? Either reboot into ClockWorkMod and select Mounts and Storage -> Mount USB Storage
Or, from within CM9, go to settings -> Storage, and use the button at the top right to access USB Modes. Check MTP mode and connect to your computer.
If this helped you, use the thanks! button
links doesn't work.pls fix
I would remove all direct links if I were u...
Sent from my HTC Glacier using Tapatalk
truncated links
Your links are truncated. Check it. You'll see, they are not only truncated on screen in the post, the actual URL is truncated.
Thanks.
seargent007 said:
The following is a fix posted by Dalingrin to address a slow charge issue affecting all Touchpads.
To install -
Place the fix zip in the root of your Touchpad's memory
Reboot your HP Touchpad
Select ClockWorkMod
Select install a zip from sdcard
select the zip and install
Reboot system.
Download Links -
http://goo-inside.me...enderloin/alpha
http://www.techerrat...rFix-alpha0.zip
http://www.servili00...rFix-alpha0.zip
Having trouble accessing your Touchpad's Memory? Either reboot into ClockWorkMod and select Mounts and Storage -> Mount USB Storage
Or, from within CM9, go to settings -> Storage, and use the button at the top right to access USB Modes. Check MTP mode and connect to your computer.
Click to expand...
Click to collapse
Joker Fuel said:
I would remove all direct links if I were u...
Sent from my HTC Glacier using Tapatalk
Click to expand...
Click to collapse
I don't mind a direct link to the charger fix since its a one time thing. It should be noted that this fix will only be needed for this initial alpha release.
walidbang said:
links doesn't work.pls fix
Click to expand...
Click to collapse
Fixed, sorry about that, should've realized it before I copied my own post.
dalingrin said:
I don't mind a direct link to the charger fix since its a one time thing. It should be noted that this fix will only be needed for this initial alpha release.
Click to expand...
Click to collapse
Thanks, I'll make sure this isnt misinterpreted as a universal fix for all future builds.
Thanks Dalingrin for all the amazing work you put into this! I have a friend with a Galaxy Tab upset that the Touchpad has a better working version of ICS than he does!
Thanks a million dalingrin for your work on this.
Is it just me or did the notification light stay on always before this update, and hold a wake lock? But, after the tuchpad will now enter deep sleep.
Not trying to issue a bug, as I know its early. But, wondering if that was expected.
Just want ppl know that there's a new fix, Charger and SystemUI force close fix for alpha0:, scroll down and you will find it. http://rootzwiki.com/topic/15509-releasealpha0-cyanogenmod-9-touchpad/
zrzhu said:
Just want ppl know that there's a new fix, Charger and SystemUI force close fix for alpha0:, scroll down and you will find it. http://rootzwiki.com/topic/15509-releasealpha0-cyanogenmod-9-touchpad/
Click to expand...
Click to collapse
Thread updated with new fix, thanks.
Still charges rather slow...
Sent from my HP Touchpad running CM9!
itsDefying said:
Still charges rather slow...
Sent from my HP Touchpad running CM9!
Click to expand...
Click to collapse
Try charging with the screen off if you're using the Touchstone dock.
I flashed this plugged in the charger to charge came back to unlock it, the screen won't unlock. Touch screen won't respond to a touch and when I hold home + power it ask me if I want to shut down Guess I have to wait until the device dies.
newbieandroid said:
I flashed this plugged in the charger to charge came back to unlock it, the screen won't unlock. Touch screen won't respond to a touch and when I hold home + power it ask me if I want to shut down Guess I have to wait until the device dies.
Click to expand...
Click to collapse
you can hold both the power button and the menu button together for 10 seconds to force-off the device.
seargent007 said:
you can hold both the power button and the menu button together for 10 seconds to force-off the device.
Click to expand...
Click to collapse
Ha I guess it usually takes a shorter time with WebOS/CM7 I guess I'm impatience. Thank you very much for the quick response. The screen kept timing out so I assumed it wasn't responding.
rmk40 said:
Try charging with the screen off if you're using the Touchstone dock.
Click to expand...
Click to collapse
Not using touchstone.
Sent from my HP Touchpad running CM9!
I applied this fix and it seems to work just fine.
I plugged in to charge without the fix and after 15 mins, it had actually gone down from 10% to 9%.
After the fix, it bumped to 35% after about 1 hour of charge. I am happy with the fix. Thanks
Installed CM9 and the charge fix yday. Now I installed the new fix and my system is rebooting every 5 minutes...
Edit 1:
Looks like fixing the permissions and wiping the cache partition and dalvik cache fixed the rebooting stuff..
Does anyone have issues with flash player? I tried to go to the market and download the apk but it said flash player wasn't compatible with my device?
benfikaman said:
Does anyone have issues with flash player? I tried to go to the market and download the apk but it said flash player wasn't compatible with my device?
Click to expand...
Click to collapse
Works for me.
Sent from my HP Touchpad running CM9!
Related
If anyone is experiencing random restarts with darky's rom he/she should: long press power button> select recovery> wait> click delete(clear) cache >than click advanced> click clear dalvik cache >and when it's all done than restart adbd and reboot device
Sent from my GT-I9000 using XDA App
Hello,
I experienced with this ROM a strange issue: randomly with the phone in stand-by pressing the power button the phone is unable to switch on the screen and the only way to re-switch on the screen is a long press of power button in such a way that it is able to shutdown and reboot.
Has someone else experienced the same issue? Suggistions to fix it?
Thank you
better solution: don't use Darky's
best solution : read -> think -> dont hate !
decouvrir said:
better solution: don't use Darky's
Click to expand...
Click to collapse
you suck big time !
paky79 said:
Hello,
I experienced with this ROM a strange issue: randomly with the phone in stand-by pressing the power button the phone is unable to switch on the screen and the only way to re-switch on the screen is a long press of power button in such a way that it is able to shutdown and reboot.
Has someone else experienced the same issue? Suggistions to fix it?
Thank you
Click to expand...
Click to collapse
what version do you use .... try updating
I'm on the 9.1!
Sorry, but I have searched and I read a lot but no answers to this problem have been found!
themate1987 said:
If anyone is experiencing random restarts with darky's rom he/she should: long press power button> select recovery> wait> click delete(clear) cache >than click advanced> click clear dalvik cache >and when it's all done than restart adbd and reboot device
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Has this been reported to Darkyy? And if so, what is his response?
I've had a couple of random restarts on Darky's - I assumed it was due to the lagfix for some reason. But I've cleared the Dalvik Cache and will post back if that doesn't fix it!
lljkpugna said:
I've had a couple of random restarts on Darky's - I assumed it was due to the lagfix for some reason. But I've cleared the Dalvik Cache and will post back if that doesn't fix it!
Click to expand...
Click to collapse
Flash Darkyy's No-Wipe ^ flash Doc's No-Wipe. You will see the difference.
ragin said:
Has this been reported to Darkyy? And if so, what is his response?
Click to expand...
Click to collapse
Shouldn't this be
"Has this been reported to the moderator?" This is the Development forum.....
Sent from my GT-I9000 using XDA App
i experience this whenever i had my phone plug in over-night to recharge to full 100%. after i unplug and off the screen, it just wont wake up until i long press power button to restart it. then after that, everything seems fine until my next overnight recharge.
ragin said:
Flash Darkyy's No-Wipe ^ flash Doc's No-Wipe. You will see the difference.
Click to expand...
Click to collapse
So, what's the difference?
@topic
Random reboots?
There are thousands of people running my ROM everday and don't have any issue like that.
The OP is indeed right - clearing caches might work.
You guys may have to wipe - don't worry, a new ROM which will do that 110% automatically is coming soon.
Darkyy said:
Random reboots?
There are thousands of people running my ROM everday and don't have any issue like that.
Click to expand...
Click to collapse
Installed R4 yesterday (going from another custom ROM via resurrection and then the latest greatest with wiping) and already experienced some reboots. Last one was trying to copy a directory from a sdram to external SD. Next try was OK.
I am going to wipe the caches - I'll report if this does not fix it.
on 10.2, just use another Launcher. TwLauncher is the issue.
I get random reboots when using Google Maps Navigation, it just freezes for 4-5 mins then reboots... sucks when driving...
Just adding my tuppence...
I wish to mention before I start that I am more than happy with all aspects of Darky's 10.2EE - it's a really snappy and slick-looking ROM.
I have had the ROM installed for about twelve hours now. I installed the ROM only after cleaning-down my SGS, removing anything and everything that was not stock, and formatting with prejudice...
...but I'm a little concerned about something. Three times today, the system has apparently rebooted, showing the boot animation.
I do not believe it is a standard reboot, however, as it is very quick. It is rather more like a quick reboot, where the ram is cleared and the front-end re-loads.
It has happened while I was restoring apps (app only, no data), while I was downloading game data (N.O.V.A 2 first launch) and one other time (I forget what I was doing).
I am running ADW Launcher EX, so I don't believe it has anything to do with TWLauncher, though I may be ill-informed to make such an assumption.
I imagine that restoring my apps and intensively downloading data might be putting my SGS under some stress, and while it does not reboot while running anything particularly CPU-intensive, it does appear to be occurring when moving large chunks of data around.
However rare this issue, I'd welcome sensible suggestions on what to look out for. I'm going to see if I can replicate the reboot while plugged into the log viewer - if anything useful comes of it, I will post the result.
Again, let me re-iterate that I am not complaining - this is an absolutely amazing ROM, and if it happens to perform a ten second reboot every now and again as a result of heavy downloading or data movement, I think I can live with it. Everything else lives up to the 'blazing fast' claim admirably, and there seem to be massive improvements to general performance in CPU-intensive apps too (I was previously running Tayatuma's FroYo ROM, and despite some glitchy behaviour, I was too lazy to get rid of it until now).
lol darky. thats funny
10
@Whie Hawk:
1. DO NOT use 10.2, if you can use 10.2.2 (you flashed recently, didn't you?);
2. you are on custom ROM. Therefore, it is ALWAYS better to install app from Market, than to restore it, as some "minor" differences can cause "big" issues;
3. I'm (personally) glad that you're not on the "blazing fast" stadium yet
4. what I'm doing while switching ROM... is: I have all... "out of market" apk's on card, ready for install, while the Titanium is rather a list for me, not the resource. simply, when I finish flush, I check on titanium what I had, and then I reinstall it fresh from Market/SD card. BTW, Titanium is best for freeze/backup/restore while I'm on same ROM...
@Sixhouse: sorry, I couldn't understand... For a time being, looking on your posts, I presume that you are aiming to have 10.000 useless posts on XDA in different device's threads... Is it a homework in your primary school?
decouvrir said:
better solution: don't use Darky's
Click to expand...
Click to collapse
Best idea ever
Hi dude?!! I dont know if you ever experiences random reboot.
I got my phone not responding (when touch power or menu button) and i could see the Samsung logo hazy. But always resolve by reboot (hold the power button for 8 seconds)
I didnt root or apply lag fix. Is this probably cause by certain app ??? i use some of optimizer or tweaking app.
Usually this happen when i didnt touch my phone over 2 hours. This is very annoying to me. How could i resolve this problems. Does anyone know? please share!!!
Me too
Hello, I have the same issue.
My phone is rooted and i'm using the rom: I9003XXKB1 from Movistar ( spanish operator ).
Compilation number: FROYO.BGKB3
Kernel: 2.6.32.9
The phone freezes randomly and i need to force a reboot holding the power button.
Sometimes it directly reboots alone.
Greetings.
The phone freezes randomly and i need to force a reboot holding the power button.
Click to expand...
Click to collapse
Funny ****, got the same issue on my i9000 on 2.3.4 JVP with CF-Root... also had it on Froyo 2.2.1... this sucks big time, any input or hints appreciated.
Try a new fw first and post the results. Dont add anything else then observe. If all else fails, take it to where you bought it from and get a new 1.
Sent from my GT-I9003 using XDA App
konx777 said:
Hi dude?!! I dont know if you ever experiences random reboot.
I got my phone not responding (when touch power or menu button) and i could see the Samsung logo hazy. But always resolve by reboot (hold the power button for 8 seconds)
I didnt root or apply lag fix. Is this probably cause by certain app ??? i use some of optimizer or tweaking app.
Usually this happen when i didnt touch my phone over 2 hours. This is very annoying to me. How could i resolve this problems. Does anyone know? please share!!!
Click to expand...
Click to collapse
I occasionally have a random reboot as well though I haven't had any again after disabling the live wallpaper i had running from GO Weather.
Mine is a GT-9000 / 2.3.3 stock /I9000XXJVO/GINGERBREAD.XWJVH/ stock kernel at the moment
Didn't have the reboots/freezes before the last standard KIES update though.
You said "i use some of optimizer or tweaking app."
I'd say start by disabling/uninstalling all stuff that you don't really need.
Check if there are apps configured to run in the background and disable those as well
eriamel said:
I'd say start by disabling/uninstalling all stuff that you don't really need.
Check if there are apps configured to run in the background and disable those as well
Click to expand...
Click to collapse
I ever think that maybe cause by bad memory management in Froyo, thats why i use that kind of tools.
But, i'll try to get rid of it, and lets see.
*Sent from my GT-I9003 using XDA App*
Everybody seem concern to latest Gingerbread that actualy still trial ROM
Buts every feedback really needed for I9003 sake.
I have upgrade to 2.3.4 and getting worst after 10min idle. But with some trick from this forum getting better and now still evaluate.
Try this
Select all animations from display menu
go to Settings>Display>Animations>All animations
utkarshshrivastava1 said:
Select all animations from display menu
go to Settings>Display>Animations>All animations
Click to expand...
Click to collapse
Hi utkarshshrivastava, i did it. But still no hope
is it related to battery calibration or something like that ???
Now, iam back to xxkb3 an experienced with this reboot issue again
just rooted and use some apps like TitaniumBackup, Go Launcher Ex, Go Weather.
hmm...just dunno how to figure this out, not only with latona, the other device in other brand also experienced it.
I searched and found nothing like this.
When I boot my Nook Color, running Cyanogenmod 7, any recent nightly, wireless is off, even though it was on before booting.
I open Notifications, tap the wireless, it turns on and works fine. I've checked, airplane mode is not on.
Updating to newer nightlies doesn't work. I'm pretty sure this used to work. My glacier doesn't have this behavior.
Any thoughts on how to fix this so the wireless state is retained over boots?
I have the same thing but I actually prefer it this way since I use it so much for reading.
I think those lately night builds have screwed up a few things such wireless OFF on boot. Another itchy part (for me) is the Terminal Emulator somehow got blue background and when "exit" command, it doesn't exit but I must force it off under Managing Applications.
votinh said:
I think those lately night builds have screwed up a few things such wireless OFF on boot.
Click to expand...
Click to collapse
Ah, thanks. I suppose I can't file a bug since it is a nightly, I'll mention it on the appropriate thread and hope.
Another itchy part (for me) is the Terminal Emulator somehow got blue background and when "exit" command, it doesn't exit but I must force it off under Managing Applications.
Click to expand...
Click to collapse
Press the menu key, then "Reset term".
Yeap, that's another less painful way to close T.E.
Try downloading android assistant from the market and checking to see if you have airplane mode on through the app.
Sent from my LG Optimus V using Tapatalk
koopakid08 said:
Try downloading android assistant from the market and checking to see if you have airplane mode on through the app.
Click to expand...
Click to collapse
I had it, and got rid of it because it wasn't doing anything for me. I'm pretty sure I had checked this before *and* I have flashed several times, but I just got it and...the airplane is blue. I've got a thread on a dev thread, I'll ask about it getting fixed, clearly shouldn't be happening.
excarnate said:
I had it, and got rid of it because it wasn't doing anything for me. I'm pretty sure I had checked this before *and* I have flashed several times, but I just got it and...the airplane is blue. I've got a thread on a dev thread, I'll ask about it getting fixed, clearly shouldn't be happening.
Click to expand...
Click to collapse
It should not be blue. Tap on it and it should turn gray. Problem solved.
Sent from my LG Optimus V using Tapatalk
Is there an actual answer for this issuer? Is this designed by the CM7 team?
thereddog said:
Is there an actual answer for this issuer? Is this designed by the CM7 team?
Click to expand...
Click to collapse
It's an Android problem. Something to do with missing radios. Happens on the touchpad too.
---------------------------------
Sent from my LG Optimus V using Tapatalk
If this post helped you don't forget to say thanks!
Definitely not a nightly problem, it's that way in the official release too.
Sent from my NookColor using xda premium
Some smart CyanogenMod users fixed this problem. Perhaps their methods would work for you as well as they worked for me.
I guess we just have to avoid accidentally enabling airplane mode.
I actually prefer wifi off on boot as I don't need it most of the time and it just drains the battery.
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