Three years of happines on a finely tuned Defy (T-Mo US standard firmware) that now has started giving me a lot of grief; something trigers a 2nd boot phase (that's how I call it... it's the phase with the MotoBlur/Android animation) while the phone is already running (seemingly OK,).
It's weired; out of the blue, I can see the MotoBlur animation start, and when it completes, the phone will lose wi-fi, cell network goes down (there's a red '+' icon displayed), and soon the phone freezes and only a battery pull will get it going again. This happens at random, sometimes when the phone is not used. If I were to speculate on the likely cause, I'd point out wi-fi, but... what do I know?
So far, I've done a factory reset, reflashed the firmware, and I've even tried two other SBFs (the GB Blur U3_3.4.2_179-6.1, and the CEE U3_3.4.2_179-002 Deblured), all for naught.
I think I've done all that's available to mere mortals, and now it's time to seek help of the experts here.
Please
MarSOnEarth said:
Three years of happines on a finely tuned Defy (T-Mo US standard firmware) that now has started giving me a lot of grief; something trigers a 2nd boot phase (that's how I call it... it's the phase with the MotoBlur/Android animation) while the phone is already running (seemingly OK,).
It's weired; out of the blue, I can see the MotoBlur animation start, and when it completes, the phone will lose wi-fi, cell network goes down (there's a red '+' icon displayed), and soon the phone freezes and only a battery pull will get it going again. This happens at random, sometimes when the phone is not used. If I were to speculate on the likely cause, I'd point out wi-fi, but... what do I know?
So far, I've done a factory reset, reflashed the firmware, and I've even tried two other SBFs (the GB Blur U3_3.4.2_179-6.1, and the CEE U3_3.4.2_179-002 Deblured), all for naught.
I think I've done all that's available to mere mortals, and now it's time to seek help of the experts here.
Please
Click to expand...
Click to collapse
I think you suffered from the RIL bug.
tl:dr
hotdog125 said:
I think you suffered from the RIL bug.
Click to expand...
Click to collapse
Thanks, it seems likely. I do fit in the general profile of users reporting the problem... it all started after a trip to Europe last summer, where I did use the phone on local networks with their pay-as-you-go SIMs. So, tl:dr (actually I just started reading) on the ins and outs of the issues involved, but (to cut to the chase) has the fix/workaround for this problem been found?
Thanks.
There is a patch in custom ROMs.
Sent from my MB526 using xda app-developers app
hotdog125 said:
There is a patch in custom ROMs.
Click to expand...
Click to collapse
Hey, thanks for the heads up. Do you know which one(s)?
Most ROMs have the patch.
Sent from my MB526 using xda app-developers app
Semi solution
Installed BasebandSwitcher which minimized (not eliminated) the frequency of reboots. Also, the trick that helps is to make sure the phone is set to be on either cell network, or on Wi-Fi, at any one time. It's a pain, but at least I can use the phone until I get a new one. Thanks to hotdog125 for pointing me in the right direction.
Related
Anyone here seeing some data issues on the D2 running Fission? I am in a major city, and it seem like I am kind of having some data issues since I starting running Fusion, specially when browsing the web. The internet seems to lag a bit, and connection seems a bit slow(good bit slower than normal). I got a message few times relating to the data connection. I want to say this could be a network issue, but my sister with a Droid Inc, says here data is fine? Any ideas?
Called VZW today up asking if there was an issue on their end, and they said no. Tech then told me to take out the battery for 10-15 seconds and they try the internet when back on. Tech said it could be due to the phone not properly switching from one tower to another. It did work, but about 2 hours latter I was having the same connection issue where pages would no open up, and data was a bit on the slow side. Did the same method again, and that worked. I didn't have this issue on the stock D2 rom, or with my Eris(well that always dropped 3G reception, this is full bars with connection problem). Could this be due to me being on Fission 2.2.2, or is it whole different matter not due to being in Fission? Thanks
tbaker077 said:
Called VZW today up asking if there was an issue on their end, and they said no. Tech then told me to take out the battery for 10-15 seconds and they try the internet when back on. Tech said it could be due to the phone not properly switching from one tower to another. It did work, but about 2 hours latter I was having the same connection issue where pages would no open up, and data was a bit on the slow side. Did the same method again, and that worked. I didn't have this issue on the stock D2 rom, or with my Eris(well that always dropped 3G reception, this is full bars with connection problem). Could this be due to me being on Fission 2.2.2, or is it whole different matter not due to being in Fission? Thanks
Click to expand...
Click to collapse
Im running 2.2.2 and im not having that issue. My girl has a D1 and she gets the same crappy service i get i really dont think its the rom. And i dont think there is enough of a difference between 2.2.1 and 2.2.2 to have one get different reception than the other
Shot from my level 60 crossbow of awesomness!
Maybe it just my phone then? I guess will see what I can do.
Have your tried a root reset with a reinstall?
I have been having this problem, Data will just stop working all together. Text messages won't get sent or delivered. The 3G icon just shows uploading and not downloading or stops showing anything at all. I can't fix it unless I turn on Airplane Mode then back off or reboot the phone. Right now I'm running Fission 2.1 but I ran into Data issues with the default R2D2 rom.
volcanomike said:
I have been having this problem, Data will just stop working all together. Text messages won't get sent or delivered. The 3G icon just shows uploading and not downloading or stops showing anything at all. I can't fix it unless I turn on Airplane Mode then back off or reboot the phone. Right now I'm running Fission 2.1 but I ran into Data issues with the default R2D2 rom.
Click to expand...
Click to collapse
So the issue your having is not related to a fission rom...
So, I may have solved the issue. I started clean again; cleared all data and status and stuff, then reinstalled 2.2.2, and then hard rested. Only thing I did different was not install the black status bar and all seems fine, and data seems normal.
tbaker077 said:
So, I may have solved the issue. I started clean again; cleared all data and status and stuff, then reinstalled 2.2.2, and then hard rested. Only thing I did different was not install the black status bar and all seems fine, and data seems normal.
Click to expand...
Click to collapse
I hate to say this man, but from my experience, the more "stuff" you throw on top of a rom, the more bugs your gonna encounter. And youll never have the same bug twice...
Why is that?
Mackattack said:
Why is that?
Click to expand...
Click to collapse
Why is what?
The issue may have arisen again, but I was on the market, so it not clear if that was the market issue many people are facing or it was a data issue.
mikeyinid said:
Why is what?
Click to expand...
Click to collapse
More stuff you put in the more bugs you encounter.
Mackattack said:
More stuff you put in the more bugs you encounter.
Click to expand...
Click to collapse
Im not a dev or anything, but here is an example. I was having problems with a rom i was running last night, reboots and such. The very first thing the dev who made the rom asked me was if i was running a theme. Now, im not saying you shouldnt use custom themes or addons with these roms, but every device is different and will react different. And when your flashing 3-4 different themes over a rom trying to find one you like, or flashing addons then trying to undo them your gonna create some issues. Of course, and i remind you again that im not a dev, this is completely based on my experience, and opinion
I guess with themes that can make sense. I wonder what team defused has to say about this?
Hey folks,
My wife's MyTouch 4G has suddenly started locking once it goes to sleep. I cannot wake it up at all without popping the battery
here's what I've tried
- Removing potential problem apps
- Hard Reset
- Clearing all items in recovery (cache, delvik(sp?), battery stats, etc..)
- SIM swap with my phone (also a MyTouch 4g)
The only thing I didn't do was try a different ROM, only because her and I are using the same phone, and my install is working perfectly fine (Awesome ICS 3.6). Any other suggestions before I look at getting a new phone?
Thanks!
RickoT said:
Hey folks,
My wife's MyTouch 4G has suddenly started locking once it goes to sleep. I cannot wake it up at all without popping the battery
here's what I've tried
- Removing potential problem apps
- Hard Reset
- Clearing all items in recovery (cache, delvik(sp?), battery stats, etc..)
- SIM swap with my phone (also a MyTouch 4g)
The only thing I didn't do was try a different ROM, only because her and I are using the same phone, and my install is working perfectly fine (Awesome ICS 3.6). Any other suggestions before I look at getting a new phone?
Thanks!
Click to expand...
Click to collapse
(1)
Try flashing a new kernel
(2)
Try a new rom Awesome ICS is very Outdated. (Yes in working on an update but its outdated)
Sent from my Dark Unicorn Resurrected v.2.5 using Tapatalk 2
I will try this, I have never flashed a kernel before,I usually use whatever comes with the rom, any suggestions on a particular kernel?
...Awesome... said:
(1)
Try flashing a new kernel
(2)
Try a new rom Awesome ICS is very Outdated. (Yes in working on an update but its outdated)
Sent from my Dark Unicorn Resurrected v.2.5 using Tapatalk 2
Click to expand...
Click to collapse
RickoT said:
I will try this, I have never flashed a kernel before,I usually use whatever comes with the rom, any suggestions on a particular kernel?
Click to expand...
Click to collapse
Personally I like Frosted Cherry There are a few more here in Awesomes OP HERE though. If one doesnt seem to work give the others a shot.
Well, sadly I did a restore on her phone, and now it just locks up on boot and never gets to the setup process for your account. Then I tried another rom and it complained about an unexpected offset (different numbers each time). Then I found this post.. http://forum.xda-developers.com/showthread.php?t=1394238
Followed the instructions to restore to the factory OS... now it doesnt get past the boot animation, or goes to sleep during it which requires a battery pop. What the guy explained in the post about the eMMC chip going bad exactly describes the behavior of her phone, so I am thinking it is that. We ordered her a Samsung Galaxy S III ($600) last night after spending about 4 hrs trying to get the phone to even boot to the OS.
Sadly I think its toasted
thanks for all the help/suggestions though, I may use them on my phone since mine is still alive and kicking with no issues (*knock on wood*)
~Rick
RickoT said:
Well, sadly I did a restore on her phone, and now it just locks up on boot and never gets to the setup process for your account. Then I tried another rom and it complained about an unexpected offset (different numbers each time). Then I found this post.. http://forum.xda-developers.com/showthread.php?t=1394238
Followed the instructions to restore to the factory OS... now it doesnt get past the boot animation, or goes to sleep during it which requires a battery pop. What the guy explained in the post about the eMMC chip going bad exactly describes the behavior of her phone, so I am thinking it is that. We ordered her a Samsung Galaxy S III ($600) last night after spending about 4 hrs trying to get the phone to even boot to the OS.
Sadly I think its toasted
thanks for all the help/suggestions though, I may use them on my phone since mine is still alive and kicking with no issues (*knock on wood*)
~Rick
Click to expand...
Click to collapse
Hopefully the samsung works well for you. Personally i've never heard of a "Bad Chip" phone acting that way in particular. When you boot into HBoot (Power and Vol Up at the same time) do you still have S=Off?????
Never posted in these forums before, since I've never suffered any problems with my HD2 until now. So I will post it my way.
Background info:
I have been using tytung's Android ROMS since he was developing Froyo, starting with MAGLDR. Since then I've been constantly upgrading to his next releases. When cLK eventually got stable (around the latest stable GB releases I think), I switched over to that bootloader. Not having any problems. When ICS finally got it's HWA fully working I switched over to this. I had never encountered any problems with my phone ever, which I am greatly thankful for... That was until now.
My problem:
Approx a week after installing tytung's NexusHD2 ICS v2.7, I started having problems with the phone's data connection in general. When I turn on the phone, it MAY get signal to my data carrier. Sometimes I do, other times I don't. I can try to put the phone in "Plane mode", and back to normal. But that has the same effect as when i turn off/on the phone. Other times when the signal bar shows that I either have full or 50% signal (two dots), I am not able to call, send sms nor browse the internet at all. WTF!? I have tried disabling the WiFi but this has no effect. When I search for data providers(carriers?), I may find all of them after two minutes of searching, I'll find none OR it will search for ever and never come to any conclusion.
Searching:
I have searched through nearly the whole developement thread, and also searched through this Q&A thread, but I can't find anyone who suffers the exact same problems as me. There are some threads and problems similar to mine, but none of their "fixes" has killed the problem for me.
What I have tried:
- Tried the WiFixerFree-solution
- Tried different (older) kernels
- Tried flashing older tytung releases (2.3, 2.4, 2.5, 2.6)
- Did a fresh install
- Extending the system partition (in case of bad blocks)
no success
I don't think this has anything to do with tytung's newest release. It's just weird that this recently started happening, especially after working so good for so long. Does anyone have any clue on what I can do now?
Disassemble your phone and make sure the antenna tabs are touching the contacts,I did this and sure enough one was not touching. After reassembling, full signal was restored.
Sent from my HTC HD2 using xda premium
Omg found the stupidest solution to this irritating one week-long problem.
I tried to extend the system partition even further. Weird that this solution rarely have come up as an option in the forums.
Hope this is helpful to anyone else who may suffer the data drop-problem.
EDIT: Nope... Just a temporarily solution. I can't understand why this should have something to do with the hardware, when I haven't done anything that could harm the phone in any way. But I'll do it asap, and report back. Thank you for the tip.
The 3g connection not working and I can't even use the gprs and I can't enter APNs to let the phone access the internet please please please help me
Now I can use the internet only through the Wi-Fi connection!!!!
Which apps2sd scripts are you using?.I used to have this problem with Link2sd...but yesterday,I did a clean installation and flashed INT2EXT script,and I must say,no network issues anymore...
Sent from my NexusHD2 using xda app-developers app
Hagdi2 said:
Which apps2sd scripts are you using?.I used to have this problem with Link2sd...but yesterday,I did a clean installation and flashed INT2EXT script,and I must say,no network issues anymore...
Sent from my NexusHD2 using xda app-developers app
Click to expand...
Click to collapse
Aaaahh! Thank you! I am currently using Link2sd, will try to flash the INT2EXT script, and report back!
Zmip said:
Aaaahh! Thank you! I am currently using Link2sd, will try to flash the INT2EXT script, and report back!
Click to expand...
Click to collapse
Any good news? I have this problem also, after flashing 2.7. I have restored my HD2 back to my previous backup, but still suffering this problem.
The 3G/H signal jumps between 0 ~ 4 bars, but most of the cases it has 0 bar, then switches to edge. If the internet get disconnected, it cannot reconnect automatically. have to turn off data and back on to connect to the internet.
I flash the latest radio, no help. reflash the sd card, no help. reformat the phone, no help.
The last thing i want to try is to part my phone and reconnect the data antenna
link:
http://forum.xda-developers.com/showthread.php?t=1190180
if nothing helps/i break my HD2, then it is time to buy a new phone.
Reporting back. Just installed int2ext+, and can report back that after only 3 minutes of use that my data dropped... again. I were not able to call, and neither send sms or anything.
I will get the needed tools to disassemble my phone and TRY to fix the connections. When this is done I will report back again.
Thanks for all tips I have gotten so far! I love this community!
Fffffffffffffffff
NAH! Just disassembled my phone and straightened up the pin that was the problem for this guy
After 2 minutes of uptime, the signal dropped to two bars, then after ten more seconds it dropped to zero... Now it is back to "normal", doing random bumps from 0, to two to four bars. Soooo... f*uck
The pins were my problem, I only have data dropout when going into the market or sending/receiving MMS's now.
i have similar problem too.after using wifi tethering. 3g IS not working anymore till reboot. sometimes 3g automatically change to 2g and vice versa
Any solution?
***TL;DR***I know now that 4.3 has this bug and it is something we will deal with. I understand the causes, but the problem is buried in the kernel vs the ROM, you can still read my semi adventure but I wanted to make this edit to save you time if you think I found an answer. Overall WIFI is a huge trigger for screen wakes along with shotty or chattery reception.***
First off SlimBean is pretty much the best ROM I've dealt with, so many options, faster then I've ever experienced, and sharp looking. I've been sharking around these forums for 2 years afraid to ever make a name and post due to my lack of knowledge. I love the search options for finding answers that this forum offers to visitors and I've surely used it to root an old AT&T Atrix 4G and now my current DD the Glacier. Now I feel as though I have a little bit of sense of what the heck I am doing and would like to share my path to figuring out how to make SlimBean 4.3 work for me. Who knows maybe this may help some people that have similar problems.
The problem::: On a SEMI clean install of [UNOFFICIAL]SlimBean 4.3 \\ Nightly \\ 22.08.2013 I noticed the Glacier in standby would suddenly illuminated with light although the screen was black. It was enough to light to catch my eyes as I was starting to fall asleep. I ignored it until morning then paid attention to it happening all day at work on and off constantly with the WIFI off and just mobile network, then mobile network off, reboot, nothing seemed to help and I couldn't bare the thought of the phone's screen just on all the time.
After reading threads about HTC's possibly having bad screen made from Taiwan I was in disbelief that it was the Hardware as coming from a year old version of MIUI, I never had a problem with the screen. Leading to the idea it must be a software issue / user issue in which I must of rushed the install of the ROM or it's a quirk in 4.3.
Prior to reinstalling the same ROM, I went with trying other similar ROM's finding [UNOFFICIAL] Carbon 4.3 \\ Nightly \\ 26.08.2013 literally was just released, also a super customizable fast ROM. Everything went smooth until I played music through headphones and the illuminated black screen was back. Now I'm definitely convinced it's the software so I move on to the source code of these ROM's ev_glacier-nightly-2013.08.27.
Ev_glacier-nightly-2013.08.27 Had no screen wakes after 2 hours idle on mobile network only. I wasn't in a location with WIFI as I believe a network with a lot of information chatter may be causing these standby black illumination wakes. Back to SLIM.
SUPER clean install. 1) Format SD card completely 2) fresh download w/ checked md5 of Slimbean 3) Full Wipe "wipe data factory reset" "wipe cache" 4) format/system & format/cache manually just in case 5) Clear Dalvik 6) And fix permissions since although I believe it has no point but it's just so easy to click just in case. Probably doing things double.
Here I am now.. Slimbean is back and nothing but the .zip has been installed along with updating Nova Launcher. I am waiting to reinstall GAPPS so I can first isolate this problem within the ROM itself. What I am noticing is on just mobile network 2g/3g/2g+3g I do not get the phantom wakes, but with WIFI on it so far is only happening about 20-30 seconds after the phone drops into Standby and at least now it's not long lasting, just a few screen black flashes and it's gone. The entire 20 minutes or so I've been typing this, keeping an eye on the screen it's been quiet. Progress is being made.
Now I have thoroughly read up on and used Better Battery Stats, Wakelock detector, and Greenify to help isolate problems prior to the clean install and am waiting to install any Google apps (play store) up until tomorrow so I can pay more attention to my phone and make sure it's just a WIFI wake lock causing the screen to illuminate black. Also was toying with the idea of installing 3.0.64 kernel. I'm curious as to see if it's not just the WIFI wake lock, but all wake locks that actually wake the screen. Once I'm ready to install the play store I'm going to start combing through the device using these fantastic guides and the aforementioned apps...
[GUIDE] The Total Newb's Guide to Wakelocks ::: [HOW TO] Fix Your Skyrocket's Battery Life ::: [GUIDE] Insanely Better Battery Life When Idle
My goal with this long post is to share my experience and also commended these developers on these awesome ROM's. I will post much shorter updates on how I fixed or found the exact problem. Mainly after searching I saw similar issues but not this direct "random black illuminated screen" problem. Thanks, and be sure to call me out on anything contained in this post.
the waiting game
At 9 hours from 100% charge, I'm at 40% battery with on 1.5 hours of screen time. I went through all my settings and disabled all sounds and haptic feed back. I have yet to install any apps and am running off the bare bones of just the ROM. WiFi & 4g mobile data were on all night with the screen flashing only if I used it then locked it with the power button.
Thinking I can live with these timeout 2-5 flashes, I start browsing the forum from my phone, put it down to get ready for work, look back at the phone as it is flashing black screen rampantly on it's own. Then it holds the black screen for a solid minute or two.
WiFi chatter wake lock must be doing this... Reboot to recovery - wipe dalvik - wipe cache - reboot phone. Now to test just 4g network, flash happens on first screen lock, but not as rampant. Hmmm. My next step will be to wait for full battery drain / charge then I want to try the kernal I mentioned above. 3.0.64 kernel.
Funny stuff
Realizing the Kernel I wanted to flash doesn't work with 4.3, I hope at least some of the 86 people that viewed my post got a laugh. Even the older version of SlimBean causes the random screen flashes and the screen on while charging even with the ROM settings for such off. WiFi seems to be the greatest cause. It's as if wakelocks are actually being represented as screen flashes since the kernel is so powerful.
I just don't want to use the CM ROM...
I'm going to dig around the forums further and type in different key words of my problem just to make sure I didn't miss someone already answering this question. Slim has all the functions I always wanted out of my droid and I'm dead set to make it work...or just live with screen flashes I guess.
Hope this is a comedy for someone.
only other link
I've found on the issue I have.
http://forum.xda-developers.com/showthread.php?t=1148057
Non-Stop ROMS
1) SlimBean 4.2 & 4.3 Both have this black screen flicker / black screen wake / black screen on while charging.
2) Carbon 4.3 Had it black screen on while listening to music / black screen constant while charging
3) Evolve 3.3 based of 4.3 seemed to work fine, but I wasn't a fan of the larger Icons and screen, similair to CM 4.3 so I didn't leave it long enough to test...
4.3 CM 4.3 black screen wake almost constant / black screen on while charging... also didn't last long to really test everything.
I am down the river if I want this to just go away. I have installed all these ROM on a completey clean formated SD card each time
I'm sticking with SlimBean as it has the looks and reacts like I expect my phone to. After doing some more searching and after a little time has passed for more 4.3 development there may be a kernel that will work better for me.
Oh here is another dead end I've found... http://forum.xda-developers.com/showthread.php?t=2185747&page=3 [KERNEL] Fixed the flickering screen problem,CM10,CM10.1,SENSE3.6 4.0 4.1 That goes no where...
wifi
WiFi is the biggest culprit for the random screen wakes. I've just been living with it since I dig the slimbean 4.3 ROM so much. Thought I might pop back on here to make some closure. I worked on removing some apk's from the already minimal gapps I installed and will soon start a separate thread on just that. As long as after searching I don't find the same info I figured out.
I think you've got the screen flicker bug.
Try flashing the .69 kernel, it claims to stop the flicker.
Also I know it's got something to do with the WiFi. I know a little about it though.
Sent from my myTouch 4g using xda app-developers app
thanks for the response
N_otori0us_ said:
I think you've got the screen flicker bug.
Try flashing the .69 kernel, it claims to stop the flicker.
Also I know it's got something to do with the WiFi. I know a little about it though.
Sent from my myTouch 4g using xda app-developers app
Click to expand...
Click to collapse
I see you all over the place when it comes to Glacier threads. Today at work I was searching around for a download link. I read through a ton of other ROMS threads hoping it was buried in the comments somewhere. So far I only turned up and old thread with a dead link and a couple of other threads you mentioning to other people to download the .69 KERNEL which I am guessing the full version number is 3.0.69, if it's not then there may be my first problem in finding the link...
*edit
this is the main thread I keep finding, you have so many other kernels on there
http://forum.xda-developers.com/showthread.php?p=43983635&highlight=+69#post43983635
I have a little idea about the screen flicker.
A member called zyGh0st told me. I've pmed Elgin but no response.
I'll pm coderzs too Lil.
Sent from my myTouch 4g using xda app-developers app
reading about kernals
N_otori0us_ said:
I have a little idea about the screen flicker.
A member called zyGh0st told me. I've pmed Elgin but no response.
I'll pm coderzs too Lil.
Sent from my myTouch 4g using xda app-developers app
Click to expand...
Click to collapse
All the Kernels in the Glacier Bible page you have been keeping up seem old. I'm nervous to try one since they obviously seem like they won't work. I'm game to try what ever and post on here my progress so if anyone else stumbles upon the issue they can guide their way through it.
I've been searching "kernel 3.0.69", "kernels 4.3 roms", "jb rom kernel", "4.3 jb kernel", sometimes including the term "glacier" or "MT4G" with little to no luck between XDA and just google itself. I always just find ROMS that just mention the kernel but have no downloads.
Reading your older posts I see that youve already tried the kernel.
Sent from my myTouch 4g using xda app-developers app
K is for kernel
N_otori0us_ said:
Reading your older posts I see that youve already tried the kernel.
Sent from my myTouch 4g using xda app-developers app
Click to expand...
Click to collapse
I tried 3.0.64 kernel, not this mysterious .69 kernel you have mentioned. If you have a link or mirror of it I'll be glad to give it a go.
___________________________________________________________________________________________________
Found how you added the 2 kernels to the Bible page, I just flashed .64 again and I'm nothing but bootloops. I'll give .62 a chance since now I'll have to re-flash Slim.
___________________________________________________________________________________________________
make the double bootloops with either of those 2 kernels. I waited like 5 minutes, restarted the phone to see if it would boot and it just stayed on the slim splash screen. Of course I wiped dalvik and cache before installing either.
Bottom of your 5th post
Sent from my myTouch 4g using xda app-developers app
addiction
N_otori0us_ said:
Bottom of your 5th post
Sent from my myTouch 4g using xda app-developers app
Click to expand...
Click to collapse
Oh yes, I head that already downloaded on the SD but the name CM_SENSE made me think it was a ROM not a kernel. The .66 kernel link is dead, but the .58 flashed & works but there is still the flicker on 4.22 SlimBean. 4.22 is so lame compared to 4.3. Even if there wasn't a flicker on 4.22 I don't think I'd keep it. Those big ICONS are just too much. I think that's why I like Carbon also. Anywho...
My addiction to messing with my phone is always in conflict with work. As if I don't have enough problem solving to deal with outside of cell phones.
I am going to try out the recovery I see in your signature, Recovery : 4EXT 1.0.0.5 RC8, just to see if it makes a difference. If you have the same phone without the same problem I must then eliminate the different variables to find the true problem. I found a "how to" and am either going to put in the time in a couple of hours or tonight. Then I'm going to start the rounds of testing ROMS / KERNELS all over again and I'll post my findings here.
I appreciate the back and forth, I actually got a can't thank anymore message because I used up my 8 yesterday~
Living with it
I've been just living with the screen flash. The ROM is just to sweet to give up. At some point if there it a completely stable 4.3 I may upgrade.
On a regular work day I don't have any available WIFI, so I toggle it off then reboot the phone every morning. I usually get a random screen flash everytime I manually lock / turn the screen off and that's it. With WIFI on I get random flashes at random rates and for random lengths.
Playing music invokes these random black screen wakes also, I've stuck to my old blackberry as my MP3 player...I know that statement seems extemely wrong and against all sciences, but the 9780 bold works perfect as a music player. They had the long-press song skip in the volume button well before anyone added it to Android.
If ever I find the correct ROM / KERNEL combination, or someone else figures out the problem and I find it, I will post it here. This winter I am going to get more into understanding & compiling roms + digging through code so maybe I'll find it myself...ha!
tonyMEGAphone said:
I've been just living with the screen flash. The ROM is just to sweet to give up. At some point if there it a completely stable 4.3 I may upgrade.
On a regular work day I don't have any available WIFI, so I toggle it off then reboot the phone every morning. I usually get a random screen flash everytime I manually lock / turn the screen off and that's it. With WIFI on I get random flashes at random rates and for random lengths.
Playing music invokes these random black screen wakes also, I've stuck to my old blackberry as my MP3 player...I know that statement seems extemely wrong and against all sciences, but the 9780 bold works perfect as a music player. They had the long-press song skip in the volume button well before anyone added it to Android.
If ever I find the correct ROM / KERNEL combination, or someone else figures out the problem and I find it, I will post it here. This winter I am going to get more into understanding & compiling roms + digging through code so maybe I'll find it myself...ha!
Click to expand...
Click to collapse
Have fun man, and If you ever need help or guidance just tell us, we'll be here
I have a Moto G4 Play, I believe it is XT1607, purchased straight from Motorola. I'm running Squid's CM with the stock kernel. Overall it works great, but I have a minor annoyance: when I first turn the phone on from being completely off, the time and date is always completely wrong. I mean off by MANY hours and minutes (like I don't even know where it gets this time from), as well as like 20-30 days. Obviously this isn't much of a problem since time syncs with my cellular network after the boot is complete, but this still bothers me slightly. Every other phone I've had kept the time accurate even when it was off. Is this a ROM issue or a G4 Play issue? Anyone else experiencing this?
*Note that I don't remove the battery when the phone gets turned off.
It's nothing tho. Connect to WiFi or use the latest ROM
I have the same problem in my Moto g4 play. Any suggestion?
It's tied to your Recovery. TWRP goes off whatever the hardware time is. My phone was initially in Mountain or Central time, but even with it set to Pacific Time it's off by several hours and minutes. The only way to fix it would be to modify whatever the heck smartphones use as BIOS/CMOS.
mkollersms said:
It's tied to your Recovery. TWRP goes off whatever the hardware time is. My phone was initially in Mountain or Central time, but even with it set to Pacific Time it's off by several hours and minutes. The only way to fix it would be to modify whatever the heck smartphones use as BIOS/CMOS.
Click to expand...
Click to collapse
Maybe this is something Moto removes as a result of unlocking bootloader. There's no possible way this glitch exists on stock firmware.
jasonmerc said:
Maybe this is something Moto removes as a result of unlocking bootloader. There's no possible way this glitch exists on stock firmware.
Click to expand...
Click to collapse
Well, I would gather that the clock applications (CM has two) would be storing that information either in the memory space directly or not at all. That's the only way I could see that file being recreated on boot. As far as I can tell, phones don't have button cell batteries in them, so don't ask me how the Recovery manages to keep time.
jasonmerc said:
I have a Moto G4 Play, I believe it is XT1607, purchased straight from Motorola. I'm running Squid's CM with the stock kernel. Overall it works great, but I have a minor annoyance: when I first turn the phone on from being completely off, the time and date is always completely wrong. I mean off by MANY hours and minutes (like I don't even know where it gets this time from), as well as like 20-30 days. Obviously this isn't much of a problem since time syncs with my cellular network after the boot is complete, but this still bothers me slightly. Every other phone I've had kept the time accurate even when it was off. Is this a ROM issue or a G4 Play issue? Anyone else experiencing this?
*Note that I don't remove the battery when the phone gets turned off.
Click to expand...
Click to collapse
Hey bro! I have this phone too!
triggerlord said:
Hey bro! I have this phone too!
Click to expand...
Click to collapse
Good to hear from you again. Is your internal clock being stupid as well (assuming you flashed TWRP/ROMs and such to it)? If so what exact model do you have?
jasonmerc said:
Good to hear from you again. Is your internal clock being stupid as well (assuming you flashed TWRP/ROMs and such to it)? If so what exact model do you have?
Click to expand...
Click to collapse
I have the XT1607. I bought it off Amazon. I flashed AOKP + Gapps and the clock seems to work fine on mine.