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 All,
I've just purchased another Nexus S (I had two already) but this time second hand. This one however is doing some odd things. I've used Nexus S's since it was released so have a feeling for them. It does thing like:
- Rings with incoming calls but stays on lock screen.
- Has incoming calls but doesn't ring
- Freezing on the home screen & not getting touch input
- General oddities
First thing I'd guess would be to think it was dropped or damaged in some way but it's spotless, just the usual scratches or scuffs you'd expect on a 2nd hand phone. Box & everything look genuine, compared it with the other phones and it look all fine. I've done a reset of the software back to default (using in Phone reset) but still doing odd things.
Does anyone have any idea what I can do to find out what is going on here, is there some sort of system self check I can run to check for internal damage? Fuller system reset I can do? Etc.
Any advice?
Phone details:
Android Version: 4.1.1
Baseband Ver: I9020XXKI1
Build num: JRO03E
Kernel Version: 3.0.31-g3b0c5d2
Cheers,
Mark
Was meant to post this in the Q&A thread I think, sorry about this. Could one of the moderators please move it for me.
Thanks,
Mark
GPS
Root (I prefer to root myself)
WiFi
Clean ESN
Sent from my Nexus S 4G using xda app-developers app
I would suggest a full reset using the stock images from Google. Or root and flash a custom ROM.
Sent from my Nexus S
[email protected] said:
GPS
Root (I prefer to root myself)
WiFi
Clean ESN
Click to expand...
Click to collapse
GPS? Not sure what you mean, it's active some times, but don't use geo-location features on the phone often.
Root: No, stock updated OTA
Wifi: connected all the time to the same router as my other S's
Clean ESN: I assume so, didn't check, but I'm able to make and receive calls 85% of the time without any issues and very infrequent drops. It doesn't seem to be a network problem more the phone acting up in funny ways.
Cheers,
Mark.
7TimesCursed said:
I would suggest a full reset using the stock images from Google. Or root and flash a custom ROM.
Click to expand...
Click to collapse
I'd actually prefer to keep this one stock as its being used for work. I've rooted one of my S's, but this new one is being used as a main phone so have not rooted.
I've never flashed back a stock image, can this be done without root? If so, would you be kind enough to point me in the right direction of a walk-through so I can give it a go?
Cheers,
Mark.
Does anyone experience wifi disconnect and reconnecting while browsing?
Sent from my GT-S5360 using xda app-developers app
Noo..
yes i do
I do too. So that makes two of us? What can be the problem?
Sent from my GT-S5360 using xda app-developers app
Oh c'mon guyz..
Why u never read.
Its in the same post of hyperion..
U got to go to..
Settings>wifi>option button>deep sleep policy nd change it to dont disconnect
** rooting is new for me,
nd i am a noob to root....**
menewtoroot said:
Oh c'mon guyz..
Why u never read.
Its in the same post of hyperion..
U got to go to..
Settings>wifi>option button>deep sleep policy nd change it to dont disconnect
** rooting is new for me,
nd i am a noob to root....**
Click to expand...
Click to collapse
Yes, this worked for me too. :good:
booterbotter said:
Yes, this worked for me too. :good:
Click to expand...
Click to collapse
i knw it worked ..
next time plz read full article..
carl didnt wrote all that just to pass time..
** rooting is new for me,
nd i am a noob to root....**
menewtoroot said:
Oh c'mon guyz..
Why u never read.
Its in the same post of hyperion..
U got to go to..
Settings>wifi>option button>deep sleep policy nd change it to dont disconnect
** rooting is new for me,
nd i am a noob to root....**
Click to expand...
Click to collapse
agree
Random reboots in Hyperion 8
Overall the Hyperion 8 ROM is a nice-good-looking one. However, I've found 2 major bugs(?):
It reboots randomly at least once a day.
The "Restart" option doesn't work. The phone shuts down but never comes on.
In both cases, when booting, it gets stuck in the Samsung logo. To boot up, I have to remove the battery.
Also, it takes ages to reboot, about 6 min.
Does anyone is experiencing the same issues? Any possible solutions?
Cheers.
Blue.Ghost said:
Overall the Hyperion 8 ROM is a nice-good-looking one. However, I've found 2 major bugs(?):
It reboots randomly at least once a day.
The "Restart" option doesn't work. The phone shuts down but never comes on.
In both cases, when booting it gets stuck in the Samsung logo. To boot up, I have to remove the battery.
Also, it takes ages to reboot, about 6 min.
Does anyone is experiencing the same issues? Any possible soluctions?
Cheers.
Click to expand...
Click to collapse
I would say try re-flashing it following the install instructions from the Hyperion 7 thread exactly.
I have had the same thing as you when I first installed hype 8 but no random reboots and restart works fine on my current install
One problem I have with Hype 8 is that the stock browser included with the ROM will not connect via wi-fi, at all - although all other apps like Play store do, the browser only works on 3G. I usually use One Browser but that doesn't work either. I am currently using Opera Mini as that will work but I have no idea why this is...and yes I have pruned the hosts file and checked the Droidwall is not on (even if it was I have configured all apps to have access). Annoying, like the way the data toggle sometimes doesn't turn off - but hardly a game-breaker when Hype is so excellent on battery life and memory usage :good:
Cheers,
Stokey
Blue.Ghost said:
Overall the Hyperion 8 ROM is a nice-good-looking one. However, I've found 2 major bugs(?):
It reboots randomly at least once a day.
The "Restart" option doesn't work. The phone shuts down but never comes on.
In both cases, when booting, it gets stuck in the Samsung logo. To boot up, I have to remove the battery.
Also, it takes ages to reboot, about 6 min.
Does anyone is experiencing the same issues? Any possible solutions?
Cheers.
Click to expand...
Click to collapse
I been using it since it came out & its never restarted on me or failed to boot
I suggest you reinstall it and use hells fusion #50 kernel
hey i m using jellyblast..how do i get hyperion 8 widout bricking my sgy...ive got d zip files
Sent from my GT-S5360 using xda app-developers app
Dhaval Bhatt said:
hey i m using jellyblast..how do i get hyperion 8 widout bricking my sgy...ive got d zip files
Sent from my GT-S5360 using xda app-developers app
Click to expand...
Click to collapse
Do a data wipe/reset ie wipe data system & cache
Mount everything ie system & data
Install zip from sd card
Select zip file
Done
a simple method
change your ROM
Hyperion bugs
stokeyblokey said:
I would say try re-flashing it following the install instructions from the Hyperion 7 thread exactly.
I have had the same thing as you when I first installed hype 8 but no random reboots and restart works fine on my current install
One problem I have with Hype 8 is that the stock browser included with the ROM will not connect via wi-fi, at all - although all other apps like Play store do, the browser only works on 3G. I usually use One Browser but that doesn't work either. I am currently using Opera Mini as that will work but I have no idea why this is...and yes I have pruned the hosts file and checked the Droidwall is not on (even if it was I have configured all apps to have access). Annoying, like the way the data toggle sometimes doesn't turn off - but hardly a game-breaker when Hype is so excellent on battery life and memory usage :good:
Cheers,
Stokey
Click to expand...
Click to collapse
Thanks for your reply Stokey. In my case, I've got no problems at all with the stock browser; it is able to connect via either wifi or 3G. I wonder if such differences may be due to the build we're using. I downloaded Hyperion 8 build 2 with the default Savie kernel. Are you using the same build?
Theroretically build 2 would be more stable, isn't it? Should I revert back to build 1?
Cheers,
Blue Ghost
Blue.Ghost said:
Thanks for your reply Stokey. In my case, I've got no problems at all with the stock browser; it is able to connect via either wifi or 3G. I wonder if such differences may be due to the build we're using. I downloaded Hyperion 8 build 2 with the default Savie kernel. Are you using the same build?
Theroretically build 2 would be more stable, isn't it? Should I revert back to build 1?
Cheers,
Blue Ghost
Click to expand...
Click to collapse
I'm using build 2 with hells fusion #50 - no problems at all
Make sure you have disabled wifi deep sleep in wifi settings
Blue.Ghost said:
Thanks for your reply Stokey. In my case, I've got no problems at all with the stock browser; it is able to connect via either wifi or 3G. I wonder if such differences may be due to the build we're using. I downloaded Hyperion 8 build 2 with the default Savie kernel. Are you using the same build?
Click to expand...
Click to collapse
No, I only had build 1 because every download of build 2 was interrupted I am trying again now as I really would prefer not to use Build 1 for obvious reasons! I only installed it because of a weird wifi issue I was having on Hype 7 - I did all the tweaks to fix wifi but even though it was on all the time, if I didn't use it for a short while sometimes the signal icon would go grey and stay grey - forever! Although connected and showing an IP address in the advanced wifi settings, nothing at all could connect through wifi and I only had 3G - this has happened 3 times with Hype 7 and necessitated a reinstall via stock each time, hence me wanting to try 8 as I needed the wifi connection and a battery that lasted a full work day for the last 2 days.
Theroretically build 2 would be more stable, isn't it? Should I revert back to build 1?
Click to expand...
Click to collapse
I would say stick with Build 2 for a couple of reasons: the launcher is not a paid-app; I think build 2 uses his Hype 7 launcher which I actually prefer (sometimes less functionality suits better); if there were any fixes from Build 1 they will be included although I don't think there were any that were mentioned...
Same kernel on both builds (thank you Savie! :good but as others are saying, you can use at least one other kernel - I have never changed just the kernel but maybe that would help fix my Hype 7 issues...anyhow, I am off to try Build 2 - good luck with yours - let us know how you get on.
Cheers,
Stokey
EDIT: Can anyone help me to get the AudioFX widget to actually do something other than be almost invisible whatever settings I use? Or suggest an alternative that works with Hype 8?
stokeyblokey said:
EDIT: Can anyone help me to get the AudioFX widget to actually do something other than be almost invisible whatever settings I use? Or suggest an alternative that works with Hype 8?
Click to expand...
Click to collapse
Open AudioFX in drawer app then adjust the transparency settings. Make it 20% then 40% then 60% then back to opaque. It will show up.
Sent from my GT-S5360 using xda premium
stokeyblokey said:
No, I only had build 1 because every download of build 2 was interrupted I am trying again now as I really would prefer not to use Build 1 for obvious reasons! I only installed it because of a weird wifi issue I was having on Hype 7 - I did all the tweaks to fix wifi but even though it was on all the time, if I didn't use it for a short while sometimes the signal icon would go grey and stay grey - forever! Although connected and showing an IP address in the advanced wifi settings, nothing at all could connect through wifi and I only had 3G - this has happened 3 times with Hype 7 and necessitated a reinstall via stock each time, hence me wanting to try 8 as I needed the wifi connection and a battery that lasted a full work day for the last 2 days.
I would say stick with Build 2 for a couple of reasons: the launcher is not a paid-app; I think build 2 uses his Hype 7 launcher which I actually prefer (sometimes less functionality suits better); if there were any fixes from Build 1 they will be included although I don't think there were any that were mentioned...
Same kernel on both builds (thank you Savie! :good but as others are saying, you can use at least one other kernel - I have never changed just the kernel but maybe that would help fix my Hype 7 issues...anyhow, I am off to try Build 2 - good luck with yours - let us know how you get on.
Cheers,
Stokey
EDIT: Can anyone help me to get the AudioFX widget to actually do something other than be almost invisible whatever settings I use? Or suggest an alternative that works with Hype 8?
Click to expand...
Click to collapse
Agreed! Or use BeatsWidget included in other roms like USSrv9 and ota of JellyBlast. Its beats themed and looks cooler than the default one.
Thank you to makeouttactics and GaEuL (pressed!).
This was driving me mad!
Oh, and today whilst using Opera Mini to post on Facebook I had a spontaneous reboot - first one on Hype 8...will keep you posted.
Cheers,
Stokey
This topic has been discussed a lot of times on internet but I am really concerned about fixing my phone as no matter what, if i am on 2G, 3G or WIFI I stop having notification after 15-20 minutes. In fact I tried PINGING my device and PING stops really after 15 minutes. Anyways, currently I am desperately waiting for 4.3 and there is just no NEWS of the RELEASE DATE whatsoever. But also I am not much into CUSTOM ROM or KERNELS but was wondering if I can only update the KERNEL version (i.e., FRANCO if any one suggest) and solve this issue. I want to be remain on STOCK ANDROID but is it possible to only upgrade the kernel ?
Also I would need tutorial for the quickest root and the safest kernel to follow and keep upgrading it all the time. Thank you.
ibrahim52 said:
This topic has been discussed a lot of times on internet but I am really concerned about fixing my phone as no matter what, if i am on 2G, 3G or WIFI I stop having notification after 15-20 minutes. In fact I tried PINGING my device and PING stops really after 15 minutes. Anyways, currently I am desperately waiting for 4.3 and there is just no NEWS of the RELEASE DATE whatsoever. But also I am not much into CUSTOM ROM or KERNELS but was wondering if I can only update the KERNEL version (i.e., FRANCO if any one suggest) and solve this issue. I want to be remain on STOCK ANDROID but is it possible to only upgrade the kernel ?
Also I would need tutorial for the quickest root and the safest kernel to follow and keep upgrading it all the time. Thank you.
Click to expand...
Click to collapse
The choices and threads are out there for you if this is truly bothering you. You can stay stock and flash a couple of files to test out if your issue is fixed. Rooting is not the end of the world and you can always go back. As for tools there are multiple stickied root methods just choose one. Also no guarantee 4.3 fixes the issue. I flashed a couple files from Development in the Wifi/Fix thread and my problems went away. May for you it may be the prima drivers but you wont know until you do it
playya said:
The choices and threads are out there for you if this is truly bothering you. You can stay stock and flash a couple of files to test out if your issue is fixed. Rooting is not the end of the world and you can always go back. As for tools there are multiple stickied root methods just choose one. Also no guarantee 4.3 fixes the issue. I flashed a couple files from Development in the Wifi/Fix thread and my problems went away. May for you it may be the prima drivers but you wont know until you do it
Click to expand...
Click to collapse
I will be still waiting till 4.3 is released but just one thing I wanted to confirm when you said your problem was FIXED. Was it on both 3G / WiFi because this issue occurs on both interface.
Are there any other particular apps that still gets notification after everyone don't?
Sent from my Nexus 4 using xda app-developers app
QuackDuck said:
Are there any other particular apps that still gets notification after everyone don't?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
any APP has the same issue. I use the following and in everything it is the same frustrating issue.
whatsapp
Talk.to
Email (Even if the settings are on 1 hour INBOX CHECK, it never works until i manually do the sync)
These are the only apps I always expect to notify me INSTANTLY. Also it was the same in Google talk and any other IM apps.
ibrahim52 said:
I will be still waiting till 4.3 is released but just one thing I wanted to confirm when you said your problem was FIXED. Was it on both 3G / WiFi because this issue occurs on both interface.
Click to expand...
Click to collapse
for me I had mostly issues on wifi and now I can ping my phone after 30 minutes and it still going. I never honestly noticed it on 3g but either way you have options try them first
playya said:
for me I had mostly issues on wifi and now I can ping my phone after 30 minutes and it still going. I never honestly noticed it on 3g but either way you have options try them first
Click to expand...
Click to collapse
Thanks but it also happens in 2G because 3G I can't use due to my work environment where I can't keep charging my phone and in 3G this phone battery drains quickly. Well, two more weeks ill wait for 4.3 and if Google is still fooling then I will go ahead with ROOT and some KERNEL experiments. Thanks a load.
***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