Related
So basically, my hd2 is not running smooth at all. Every time i do a rom update and then restore my contacts/messages/settings it keeps getting frozen and unresponsive. So I have to restart the device, but I don't know why it should be restarted anyway, isn't is kind of super fast?!?! So, now, when I recently updated my ROM, the device is so damn slow, that even after typing my PIN it takes a minute to launch htc sense and everything. When I'm moving through the tabs it's so damn laggy i can't stand it. . Is anyone else experiencing this????
To be honest, and I'm no expert, it sounds like you have some serious phone problems, probably out of your control. Not to sound like a pessimist but given how everyone else seems to be ok with the HD2, could be either a major rom/radio problem or hardware failure??
I've updated my hd2 using the official rom from HTC and, apart from the occasional lag i get from WinMo, my device runs sweet as a a proverbial nut. Especially as I have run the tweaks suggested by the forums here.
Given that you have said that you've upgraded the ROM and it's made no difference, the only thing i could suggest is possibly send it back under warranty?
Obviously, I'd wait and see if someone with more know-how has a better explanation, i'm merely giving you my POV.
Hope you get this sorted ASAP. A properly working HD2 is a marvellous thing.
All the best
To the OP,
There could be so many causes for your problems. I would start as follows:
- Take your SD card out and see if the phone boots and is not laggy with the card out
- If this does not work take a look at the SMS threads on here and see if the solutions there help you
- If no joy then read the Hints @ Tips thread on here, if you have not already done so, and pickup on the cache move tips, using the task manager to close open files, etc
- I that fails look for the thread "HD2 Died - or did it" and implement the solutions in there
- If that does not help and you have been flashing a fair few roms then hop over to the MTTY thread in rom development and see if that helps.
Plenty to be getting on with.
Hope you get it sorted.
WB
My power up to sense loaded time = 55 secs.
Any different?
thanks for this quick reply. I am using Energy Leo ROM, but I don't think this could be the problem, or is it? Because I have performed a hard-reset now and it's running quite smooth again.. But the question is for how long.
Two questions I have now:
-does it happen to anyone, when you try to wake up the phone, screen doesn't wake up, only the keys in the bottom start to glow? It happened to me from time to time
-does anyone else experience missed key taps? When I tap something from time to time it just doesn't get recognized so I have to "retap" it...
[^IcEmAn^] said:
thanks for this quick reply. I am using Energy Leo ROM, but I don't think this could be the problem, or is it? Because I have performed a hard-reset now and it's running quite smooth again.. But the question is for how long.
Two questions I have now:
-does it happen to anyone, when you try to wake up the phone, screen doesn't wake up, only the keys in the bottom start to glow? It happened to me from time to time
-does anyone else experience missed key taps? When I tap something from time to time it just doesn't get recognized so I have to "retap" it...
Click to expand...
Click to collapse
I have experienced question 1 and 2.. however not alot or not frequent.. I tend to think that this is just a computer and computers do crash depending on whats going on.. The missed screen taps only happens once or twice when its playing up. I do have a screen protector on though so whether the dust, oil or screen protector is causing that is a different story, but isnt a big problem for me to remove the screen protector to find out.
so, the latest problem.. my hd2 had been running for ~16 hours without any problem now, but in last 10 minutes i had to restart it twice, because the screen stopped responding after i wanted to type new sms in a conversation (first time) and after i had a pop-up message about new sms (second time). As said before, I'm using energy rom, latest issue (17.2.). Could the problem be, in fact connected with this rom or specifically with sms software?
using cooked roms you can generally expect a few lockups and restarts.
Also, the screen not powering up, just the hard keys backlight is an issue across the board, from custom roms to official roms. Some roms seem to do it, some don't, but one that doesn't do it to me might well do it to you.
[^IcEmAn^] said:
so, the latest problem.. my hd2 had been running for ~16 hours without any problem now, but in last 10 minutes i had to restart it twice, because the screen stopped responding after i wanted to type new sms in a conversation (first time) and after i had a pop-up message about new sms (second time).
Click to expand...
Click to collapse
It has been mentioned before that if you have a large number of texts stored, it will take a while for it to allow you to reply to a text. (It has to go through the database, check for the texts sent by the user, then arrange them alongside the ones sent to them by you, then put them in chronological order, then display them, this takes time)
but i would presume the device should be working anyway (but slower, of course) and not flashing the display and being "frozen" ?
The frozen issue with texts is all in the SMS thread I pointed you to earlier. Solutions to the phone freezing are in the HD2 Died thread, again as I pointed out earlier.
How many of these potential solutions have you tried? Tryy these things first then come back if they don't work rather than make assumptions about your ROM.
WB
after 3 months i still have the issue with missed strokes.. even after the latest energy rom update :\
anyone?
So Im VERY new to this, first Windows Mobile phone. And this is my first post.
Right after receiving my HD2, I was disappointed with my purchase. I loved my Android powered G1, and fell in love with HTC. But when I got my HD2, the texting was terrible, and my phone kept freezing. After talking with a few friends about this, I was referred to this site.
From there, I did some research, and have learned a little bit. I decided to upgrade the ROM to the stock T-Mobile 2.13, through a link I found on this site. At the same time, I loved the interface of the CHT and CHTE, so I loaded those. Also, at the recommendation of Cookie's thread, I loaded Chainfire HD2 3D Driver Patch V2.0.
Well everything feels better, Ive started using Swype, and I havent had any freezing issues. I couldnt be happier...
But I recently notice (I dont do many phone calls, or talking. Im more web, email, and text) my incoming call screen isnt popping up. My phone will ring, I pull the phone out, and I see my home screen, and it is unlocked, like it should be when an incoming call comes through. I start tapping on the screen, and where I tap, icons/buttons start popping up. The "Mute" button, the "Answer/Ignore" bar, and SOMETIMES the caller's ID pic (if Im lucky enough for it to be someone who has a pic).
Now, this doesnt happen ALWAYS, but it does happen here and there. Ive also noticed, that the function that blacks/locks the screen when in call, against your face is running funny.
Does anyone know if this is related to my ROM? The 3D Driver Patch? CHT? Has anyone had anything similar???
I DID do a search, but only in this TMOus HD2 General sub forum. Should I be looking else where? Sorry for such a novel. I just felt that I should provide any possibly necessary info, since Im kind of clueless to this phone modifying world.
TIA.
Hmm...if it were me I'd definitely start with uninstalling that video driver and see if that changes the behavior.
Also, are you using the stock lockscreen or do you have CHT lockscreen enabled via CHTE? If you do have CHT's enabled, then next you might want to switch it off and see if it helps.
I don't know for sure that either of those will resolve that, but that's where I'd start troubleshooting.
After your new rom finished flashing, did you perform a manual hard reset (as recommended by most chefs)?
I've found that there is more chance of the rom being unstable if you dont.
(flashes dont always take first time, no clue why, but i'd estimate about 1 in 10 flashes just isn't stable, yet the next flash with the same rom is stable, , , I've also noted similar results when installing an OS on my PC, , , sometimes it just doesnt wanna take properly.)
theidealone said:
So Im VERY new to this, first Windows Mobile phone. And this is my first post.
Right after receiving my HD2, I was disappointed with my purchase. I loved my Android powered G1, and fell in love with HTC. But when I got my HD2, the texting was terrible, and my phone kept freezing. After talking with a few friends about this, I was referred to this site.
From there, I did some research, and have learned a little bit. I decided to upgrade the ROM to the stock T-Mobile 2.13, through a link I found on this site. At the same time, I loved the interface of the CHT and CHTE, so I loaded those. Also, at the recommendation of Cookie's thread, I loaded Chainfire HD2 3D Driver Patch V2.0.
Well everything feels better, Ive started using Swype, and I havent had any freezing issues. I couldnt be happier...
But I recently notice (I dont do many phone calls, or talking. Im more web, email, and text) my incoming call screen isnt popping up. My phone will ring, I pull the phone out, and I see my home screen, and it is unlocked, like it should be when an incoming call comes through. I start tapping on the screen, and where I tap, icons/buttons start popping up. The "Mute" button, the "Answer/Ignore" bar, and SOMETIMES the caller's ID pic (if Im lucky enough for it to be someone who has a pic).
Now, this doesnt happen ALWAYS, but it does happen here and there. Ive also noticed, that the function that blacks/locks the screen when in call, against your face is running funny.
Does anyone know if this is related to my ROM? The 3D Driver Patch? CHT? Has anyone had anything similar???
I DID do a search, but only in this TMOus HD2 General sub forum. Should I be looking else where? Sorry for such a novel. I just felt that I should provide any possibly necessary info, since Im kind of clueless to this phone modifying world.
TIA.
Click to expand...
Click to collapse
I read somewhere that the "unleaked official ROM" caused more problems than it was worth. I got the 2.13 ROM on the leaked version before it was made official and it has been working great since. I read that they made more changes and then made it official and that it was causing phones to be bricked and most phones ended up worse than they where before the the upgrade. The only "negative" thing i experienced was the screen sensitivity but it appears that the cab featured in the sticky at the top of the post fixed that!? Kinda strange If all else fails Factory Reset and try again. I always like to take a baseline reading. When my phone began acting screwy I would restore and run it stock for a few days to see if problems persisted...then after about three or four days slowly begin installing things...
Thanks for the responses! I will start with sirphunkee's suggestions. As I was typing, I started thinking the Driver Patch was a good possibility. Also, I have noticed that the phone doesnt just "sleep" the screen when I put the phone to my face, it locks. Im assuming this is something to do with CHTE's lock, because as sirphunkee mentioned, I am using the CHTE lock, instead of the stock.
Im going to start there, and see what happens.
Also, I did NOT do a manual hard reset. How would I go about doing so (yes, Im a HUGE noob. More of a car guy)? Im hoping I wont need to do this, as Im assuming I will need to restore all of my contacts, reorganize them, and reset everything else, as if the phone were new out of the box... Correct? But in case that is necessary, how do I do so?
As far as the leaked or official version... I couldnt find it on T-Mobile's site. I read a thread here, where it had been there then removed, due to people having issues with the download. I then was searching Swype or something, same forum, and found another thread, where someone had a link to the download through T-Mobile. Kinda hard to explain, but I will see if I can find the link, and the thread.
Thanks again guys! I really appreciate it. And thanks for taking it easy on me.
I just tried to post the links. I found them in my browser History. But because I have such a new account, I cant post.
theidealone said:
I just tried to post the links. I found them in my browser History. But because I have such a new account, I cant post.
Click to expand...
Click to collapse
Thanks for the effort though, you'll be able to put up links after just a few more posts (it's listed in the forum rules...hint, hint). Also, toreone already threw up a new thread in this section with that link for everybody, so don't sweat that
EDIT: oops, missed the rest of your questions there. The hard-reset is exactly what you said...resets the phone to factory-fresh condition. Yes, contacts will have to be reapplied, but sorting really shouldn't be an issue depending on your method of backing up and restoring them. I highly recommend using the built-in Microsoft Myphone utility for that (and it's wise to let it back them up regularly too, just in case, I just have mine set to do it each night while it's charging).
You can perform a hard-reset a couple of ways:
1. on your settings tab, hit "menu", then "all settings", then "system". You'll find an icon in there titled "clear storage". Run that, use 1234 as the code, and it will do its deed.
2. with the phone powered off, hold both the vol up and down buttons at the same time, and then press the end/power button to turn it back on, then it will take you into the same hard-reset process as the first method.
Hi all,
I'm running OzDROID 2.0 for my rom, 2.10.50.26 for my radio, and Hyperdroid1.6 for Android. Also TMOUS. I just recently updated my rom from an energy build to this one (wanted a lighter, faster loading WinMo). I've been having a nasty problem with the screen not coming back on when it goes to sleep. The buttons light up when i press them, but the screen stays black. Just today alone, i've had to pull the battery FOUR times. Some days it's ok, some days it's a nightmare. I checked the hyperdroid post for a radio recomendation but couldn't see any. I've tried using SetCPU to adjust clock speeds using profiles for sleeping, etc in hopes that some obscure thing will work. no good. I mean, what if i see bigfoot and want to snap a pic but the screen doesn't turn on?
My only ideas left include:
-Formatting my 16gb SD card. (would like to avoid, but will do if people think it would help. I hate setting stuff back up)
-Getting Hyperdroid1.7. (Havent yet cause 1.6 w/ Cyanogen is pretty F'n awesome, and minus this problem, i LOVE it)
-Updating my radio. (Going to do this anyways as i randomly get the "robot voice" problem. I plan on upgrading to 2.12.50.02_2 unless anyone has better suggestions)
I just wanted to check here to see if anyone has one of those "Ohh, enable <enableable option>, dumbass!" fixes. I'm not that experienced with this phone stuff. If anyone could help I would greatly appreciate it.
Thanks!
Searching is your friend. App tray->Settings->Display->Auto-Rotate to OFF/Auto brightness to OFF. This has been covered bajillions of times, the HD2 builds of Android have problems with rotation and the light sensor causeing the kernel to wig out and BSOD.
Sorry for inconveniencing you. If you had any idea how much time i've spent on here trying to figure it out, you'd understand why I decided to just ask this myself. I've had this problem for a month and am finally just now posting. If I found that anywhere I would have gladly done it. The funny thing is - those two ARE disabled, and have been. I dont like auto-rotate and auto-adjust brightness has always been off.
I even took the time to read the "similar posts" that are recommended after typing in the subject.
Since those two are off and my problem persists, I suppose I should format my SD card and try other stuff. So while that problem may have been covered "a bajillion times" it appears your solution is not the miracle cure and is probably a good reason as to why it's been asked "a bajillion times."
Why is it then when I tell people to search, they instantly peg me as some jackass just trying to pawn them off. This issue, the "black screen of death" or, "my phone wont wake from sleep under android" HAS INDEED been covered many, many times. It's cause by either what I just told you, or the particular kernel that you are running is one that tends to get stuck in the sleep mode and won't let the screen come back on. Seriously 9 times out of 10 the problem is caused by auto rotate or auto brightness.
Ashasaur is right but also none of the android versions are very stable anyway and eventually you will face this problem on all of them some sooner than others but they will eventually crash in one way or another
Sent from my PC36100 using XDA App
ashasaur said:
Why is it then when I tell people to search, they instantly peg me as some jackass just trying to pawn them off. This issue, the "black screen of death" or, "my phone wont wake from sleep under android" HAS INDEED been covered many, many times. It's cause by either what I just told you, or the particular kernel that you are running is one that tends to get stuck in the sleep mode and won't let the screen come back on. Seriously 9 times out of 10 the problem is caused by auto rotate or auto brightness.
Click to expand...
Click to collapse
I don't doubt that, but when you reply to someone asking for help with a tone as if they are retarded, don't expect them to buy you flowers. Sorry this has been asked so many times but I feel i put good time into researching this problem and didn't see a problem asking a Question on a QUESTION and answer forum. Like i said, sorry i inconvenienced you and I do appreciate your response, however you did come across as a jackass. I understand you probably deal with a lot of crap as a forum mod, but I didn't post this intending to ruin your day. You can see my post count and gather from it that I don't spend days posting pointless questions. If I came across a solution that worked, this post wouldn't exist.
Try a different radio(2.11.50.20) seems to be doing good for me, also try copying your files to a better SD card. And there is a tab under Setting>Home>>Items that says Home Timeout: 4 Hrs... try unchecking that box. I am new to the HD2 also and trying to tweak it just right so it stops turning off in the middle of the night and making me late for work cause no alarm lol
Anyone experiencing any? Sometimes if i dont restart my phone for 2days my phone gets weird.
1. when someone calls screen stays black till i slide it when i think the sliders at.
2. same with messaging black screen till i just randomly press on the screen and it opens.
Also same when i do my slidepattern lock i have to guess where the dots are.
Then phone gets sluggish to go back home screen
Anyone else experiencing this?
I am not rooted. Also i installed the update manually.
very weird, does this mean you have the call wonk bug on stock GB rom? maybe some others can reply and confirm. but cm7 users have a similar call bug that isnt known to be present on the stock ROM.
by call wonk bug do you mean where someone calls and the screen is just black, and if you slightly move the slider to answer the phone the screen comes off of black?
yes, very random things happen after a few days on stock gb - i have to reboot and/or kill the launcher every so often. find gb battery life sucks too.
Damnit i might have to reset and stick to 2.2 till this fixes its annoying. You say this is also present in cayenmod(sp?) 7.0?
sotorious said:
by call wonk bug do you mean where someone calls and the screen is just black, and if you slightly move the slider to answer the phone the screen comes off of black?
Click to expand...
Click to collapse
well not exactly, but similar. the "call wonk" bug has been plaguing AOSP versions of gingerbread for months now, and nobody can fix it. until this thread, the "wonk" problem is only present on AOSP version, NOT the OTA version of gingerbread from google. some people dont experience it, like me, and some do. it varies as to what exactly happens with the wonk, so i cant give a good description. but i'm not sure your problem is necessarily the same issue. seems similar, but possibly something different.
I've been having the same issues lately. It's very similar to the Gingerbread keyboard bug where the popups stop showing when you press the keys or hold a key to get the menu of other characters. It's actually still there, and you can try to guess where the character you want is and hope to get it... but it doesn't display. This can be fixed by killing the Android Keyboard process.
I'm seeing similar things in other places on my phone. Today, after not having rebooting for quite a while, the unlock slider wouldn't slide. Swiping my finger across where it should slide still unlocked the phone, but nothing animated to show this.
I went to change my News & Weather widget refresh interval the other day and the screen went dim (like it does in behind a select list popup), but nothing showed... however, the popup was there... and by guessing the location on the screen I was able to hit the refresh interval I wanted (after several attempts).
I've noticed the same in a few other locations that I can't remember right off. Basically, something is supposed to show on the screen, but doesn't... yet the phone still reacts properly as if it were there. Just like the keyboard bug.
It could be some kind of screen refresh bug... in my case (completely stock... updated manually to 2.3) it's definitely not any kind of call wonk as experienced in AOSP builds (unless this is the root cause of those wonks, but I somehow doubt that).
Thankfully, I haven't had any battery life issues with Gingerbread. Maybe even a little better battery life (or maybe just placebo effect).
^^^ ditto that entire post.
At first noticed it with the incoming call screen, and then the keyboard.
Easy to fix, but is a huge annoyance. Often can't see who is calling and end up answering blindly which is BS.
I'm now starting to see it in apps all over the place. Tower Raiders 2, Market, Messenger, and probably more I'm forgetting. Having to reset every couple days is becoming almost a necessary inconvenience.
Battery has been perfect, contrary to many. I did see a noticeable drop in Quadrant score switching to GB, but overall feel of performance has probably been better. Swype for some reason stopped working, similar to what happens after you update, but nothing has updated since? Regardless I'm sure an reinstall will fix.
Nothing but stock for me btw.
RogerPodacter said:
very weird, does this mean you have the call wonk bug on stock GB rom? maybe some others can reply and confirm. but cm7 users have a similar call bug that isnt known to be present on the stock ROM.
Click to expand...
Click to collapse
I'm afraid the call "wonk" bug is also on the stock Google ROM for "some" Nexus One users. See here:-
http:***//code.google.com/p/android/issues/detail?id=15297
(remove "***" as I cannot post links yet)
Personally I've never experienced it. There are lots of theories about this "wonk" and its cause.
Cyanogen has been battling to find an answer, even though he cannot replicate it himself.
One theory is that it comes about by not fully wiping the handset and SDcard before installing 2.3 for the first time and then not re-installing anything from a previous backup but rather doing a piecemeal restore on both phone and SDcard as if the handset were new.
I have to admit that, being an ex Nokia symbian user, this was the approach I adopted as not doing so on the symbian platform caused no end of problems.
[email protected] said:
I'm afraid the call "wonk" bug is also on the stock Google ROM for "some" Nexus One users. See here:-
http:***//code.google.com/p/android/issues/detail?id=15297
(remove "***" as I cannot post links yet)
Personally I've never experienced it. There are lots of theories about this "wonk" and its cause.
Cyanogen has been battling to find an answer, even though he cannot replicate it himself.
One theory is that it comes about by not fully wiping the handset and SDcard before installing 2.3 for the first time and then not re-installing anything from a previous backup but rather doing a piecemeal restore on both phone and SDcard as if the handset were new.
I have to admit that, being an ex Nokia symbian user, this was the approach I adopted as not doing so on the symbian platform caused no end of problems.
Click to expand...
Click to collapse
Probably the reason that thread hasn't been acknowledged is its a cluster of people with this 'issue', but claiming to be on OTA 2.3.3 and AOSP-based CM7..
My understanding of what is defined as the 'wonk' (which I experienced when my N1 was on CM7) is
15-20 seconds where the caller can't hear me, usually resulting in a hang up after about 10 seconds
call comes in but no slider to answer
That thread is describing a 2 second delay after the call connects, which I have NOT experienced on OTA GRI40 but would be manageable if I did. The 'wonk' as described above makes a cell phone unusable and I personally haven't seen a report of the 'wonk' on OTA GRI40. More importantly for myself, I have not experienced it in over a month of use..
Yea well the g2x is coming out next week or so and i mean it is on 2.2 which i guess i am fine with and if or when gingerbread comes to that hopefully all the wonks turn into woos!
I've had the keyboard issues randomly, and this week I had the issue where the screen is black when a call comes in. As someone before me mentioned, this is not the CM7 "wonk" and an issue with 2.3.3.
[email protected] said:
I'm afraid the call "wonk" bug is also on the stock Google ROM for "some" Nexus One users. See here:-
http:***//code.google.com/p/android/issues/detail?id=15297
(remove "***" as I cannot post links yet)
Personally I've never experienced it. There are lots of theories about this "wonk" and its cause.
Cyanogen has been battling to find an answer, even though he cannot replicate it himself.
One theory is that it comes about by not fully wiping the handset and SDcard before installing 2.3 for the first time and then not re-installing anything from a previous backup but rather doing a piecemeal restore on both phone and SDcard as if the handset were new.
I have to admit that, being an ex Nokia symbian user, this was the approach I adopted as not doing so on the symbian platform caused no end of problems.
Click to expand...
Click to collapse
the 2 second delay is not the "call wonk" people are experiencing on AOSP versions. the wonk is where the whole phone screen goes black for 30 seconds, and anything that uses the mic crashes or doesnt work. this 2 second delay when answering is an issue, but a different one, and commong to all 2.3.
If you're having the call delay problem, especially on a device that is not the Nexus One, please star the issue here:
http://code.google.com/p/android/issues/detail?id=16230
This is a known bug with Gingerbread, that Google recently declined, saying it was "device specific" (to the Nexus One).
However this problem is also being reportedly widely on the HTC Desire, as well as Samsung Galaxy devices. I have posted a new issue above and not attributed it to a specific device.
Please comment and star this issue. And please specificy especially if your device is not the Nexus One, so that Google gets this message that this is a widespread Gingerbread bug, which has nothing to do with the device.
Thanks.
The Google employee following up on the call delay issue, in the Google support forums, is asking people to fill out the following form, to gather information about how people are affected and on what devices.
http://goo.gl/10HJ1
I updated to GB right away, and I am just now annoyed enough to come post in the N1 threads.
Issue 1:When a call comes through the screen goes black. I will press the power button and the screen pops back up, displaying the caller info.
Issue 2: Sometimes (not all the time) when I close an app, any app, the home screen is blank with just the wallpaper picture showing. Again I press the power button to "sleep" the phone, press the power button again, slide to open and all of my short cuts and widgets are back to normal.
Issue 3: I also have the delay when answering. I have learned to play this off by bringing the phone up to my ear a little slower.
Issue 4: The trackball is extremely slow (unusable pretty much) in certain apps like Dolphin Browser HD, Yahoo! Mail, among others. This is mainly when I want to select text and use the Froyo trackball, click, drag, click method as opposed to the GB dragging of the little orange boxes...which I find the GB method more difficult anyway.
I will edit my post as more things come to mind.
My N1 is not rooted, btw.
I don't have enough posts to post in the thread... but I wanted to say its awesome, but the back light setting for the capacitive buttons is not working. Also camera still crashes if you refocus too quickly. Reboot is required to get it back.
truckfreak69 said:
I don't have enough posts to post in the thread... but I wanted to say its awesome, but the back light setting for the capacitive buttons is not working. Also camera still crashes if you refocus too quickly. Reboot is required to get it back.
Click to expand...
Click to collapse
And that's why you're not allowed to post yet. Both are known, it's being worked on (the camera is a CM9 issue, but Task may fix it first, and if you don't touch to focus while it's focusing, it won't freeze). The backlight problem has been reported so many times it's not funny, so before you get 10 posts I STRONGLY recommend you spend some time reading the forums, and learning how to search effectively (hint: use google search and use XDA as one of the search terms).
Then your first experience won't be the flame-tastic one it would be otherwise.
I'm in kinda the same boat as you although I've done quite a bit of snooping on the forums and in the thread and have not found any answers to my issues. Just to get the formalities out of the way, yes I did a full wipe, and I've wiped each time I've flashed an update to the ROM. These issues have been present on each iteration of the ROM thus far, and was not present on stock.
Issue #1 - Notification LED stops working correctly if device is sleeping, the color works fine and will blink on the correct times to start but after a few blinks it either will go solid or stop blinking period.
Issue #2 - While listening to Google Music or local music with the screen off notifications cause the volume of the music to drop but then not return to the level it was at previous to the notification until you hit the volume rocker.
I don't have time to read through the entire 150 pages of threads. I was aware that it had been a problem, but the latest build was just released right before I posted that. I did not see anyone discuss them since the new post. But thank you.
truckfreak69 said:
I don't have time to read through the entire 150 pages of threads. I was aware that it had been a problem, but the latest build was just released right before I posted that. I did not see anyone discuss them since the new post. But thank you.
Click to expand...
Click to collapse
Search Thread > Reading 150 pages of posts. It is a forum tool for a reason