Develop Bugs

[Q] random vibration pulses after DK28 update

I just updated to DK28 using the update.zip over stock software (no root) and on top of various new features and new bugs, I've noticed a strange new behavior.
At least several times per hour, my phone will give a quick vibration pulse, then maybe a second or two later will give two (or sometimes three) real quick pulses. I have no idea why it's doing this and whether it means something or not. Anyone know?
I can't seem to correlate the behavior to anything in particular the phone is doing at the time. It happens with the phone sleeping, and it does it while I'm using it. It happens when I'm on the home screen, when I'm reading web articles, when I'm playing with other apps, when it's on the charger, when it's off...

pilby said:
I just updated to DK28 using the update.zip over stock software (no root) and on top of various new features and new bugs, I've noticed a strange new behavior.
At least several times per hour, my phone will give a quick vibration pulse, then maybe a second or two later will give two (or sometimes three) real quick pulses. I have no idea why it's doing this and whether it means something or not. Anyone know?
I can't seem to correlate the behavior to anything in particular the phone is doing at the time. It happens with the phone sleeping, and it does it while I'm using it. It happens when I'm on the home screen, when I'm reading web articles, when I'm playing with other apps, when it's on the charger, when it's off...
Click to expand...
Click to collapse
I got that too, plus lag and other bugs when first went to 2.2 (rooted 2.1 and used update.zip). Did you wipe when you updated? I didn't so it was acting weird... Plus the GPS didn't work so I did the Odin thing and now it works fantastic.

Did you wipe when you updated?
Click to expand...
Click to collapse
No. I probably should.
I just wondered whether these little vibration pulses were meant to indicate something, or whether they're just a bug.

happens when an app crashes

My vibration was related to turning on the WIFI became very unstable. The DK28 I had came with clockwork mod so I did a recovery to Epic Experence 2.0.7 chosing the recover form a specific zip file I had copied to my SDcard. Fixed the vibration problem and my USB connection then agin worked on my Windows 7 laptop

[Q] Sense 2.1/3.0 Rom common issues

So I've tried out MikG 2.2, Synergy nightlies and 6/27 RC1, Kingdom Revolution and Synergy-Kingdom and I seem to have the same two prevalent issues I could use some help with.
1.) I use the desk clock feature of my EVO in night mode. Problem is all these roms share a common problem, that being that for some reason the World Clock service will crash and take it out of night mode. Also not sure why but with standard EVO sense roms it immediately goes to the clock whereas with the sense 2.1/3.0 roms the screen dims but doesn't go to the night clock for somewhere around 10 minutes like on an aosp rom.
2.) I use google nav heavily. I make about 10-15 stops a day for work and need it always running. Problem is with sense 2.1/3.0 roms that for some reason I haven't been able to identify, the screen will dim randomly and ultimately shut off during navigation sessions. I have tried setting the screen to always on while charging, messed around with spare parts and set the brightness to manual and auto, disabled power saving features on the phone, all to no avail. The phone is constantly plugged in and mounted on my dash, so its always charging.
I keep no personal info on my phone, so when I wipe it for a rom, EVERYTHING is wiped. SDCard, Rotation and battery stats, data, cache, system, boot, everything. I do that once over, then mount it, format the sdcard with my computer, then copy vr_superwipe and flash that to wipe it all again, then remount, format again on computer, unmount and go through the wipe list again, then remount and copy over whatever rom I am installing and start the flashing process. I use AmonRa 2.3 as I have had issues in the past with clockwork not wiping properly. I never punch in my google account until I can disable restore features. I have tried the desktop clock and google nav on a freshly installed version of each of those roms with touching nothing else and also with full profile and all that, they still do what they do.
So my question is to the community, am I overlooking something or does anyone have any ideas for me? I wanted to hit up this forum first before going to the respective dev forums. Thanks.

I use the desktop clock every night too, on my night stand.
You know, the button next to the "night" button takes it right to the clock screen.
As for Nav, I rarely use it, living in a small town, so I haven't had that problem

Watcher07 said:
So I've tried out MikG 2.2, Synergy nightlies and 6/27 RC1, Kingdom Revolution and Synergy-Kingdom and I seem to have the same two prevalent issues I could use some help with.
1.) I use the desk clock feature of my EVO in night mode. Problem is all these roms share a common problem, that being that for some reason the World Clock service will crash and take it out of night mode. Also not sure why but with standard EVO sense roms it immediately goes to the clock whereas with the sense 2.1/3.0 roms the screen dims but doesn't go to the night clock for somewhere around 10 minutes like on an aosp rom.
2.) I use google nav heavily. I make about 10-15 stops a day for work and need it always running. Problem is with sense 2.1/3.0 roms that for some reason I haven't been able to identify, the screen will dim randomly and ultimately shut off during navigation sessions. I have tried setting the screen to always on while charging, messed around with spare parts and set the brightness to manual and auto, disabled power saving features on the phone, all to no avail. The phone is constantly plugged in and mounted on my dash, so its always charging.
I keep no personal info on my phone, so when I wipe it for a rom, EVERYTHING is wiped. SDCard, Rotation and battery stats, data, cache, system, boot, everything. I do that once over, then mount it, format the sdcard with my computer, then copy vr_superwipe and flash that to wipe it all again, then remount, format again on computer, unmount and go through the wipe list again, then remount and copy over whatever rom I am installing and start the flashing process. I use AmonRa 2.3 as I have had issues in the past with clockwork not wiping properly. I never punch in my google account until I can disable restore features. I have tried the desktop clock and google nav on a freshly installed version of each of those roms with touching nothing else and also with full profile and all that, they still do what they do.
So my question is to the community, am I overlooking something or does anyone have any ideas for me? I wanted to hit up this forum first before going to the respective dev forums. Thanks.
Click to expand...
Click to collapse
I haven't noticed any of those problems in regard to the navigation app and I use both Google & the Sprint TelNav app often. My device's display stays lit when I'm using the apps. I haven't noticed the thing in regard to the clock either, but I'll experiment with it later and sew what I CA cone up with. Finally, your method of wiping is suffice. You really don't need a superwipe or format-all zip when yo have RA v2.3 and you wipe EVERYTHING in the wipe menu except the card. If you have the time, flash Warm 2.2 RLS-5 and see if you still experience the things you referenced above.
posting & replying from my EVO 4G

HipKat said:
I use the desktop clock every night too, on my night stand.
You know, the button next to the "night" button takes it right to the clock screen.
As for Nav, I rarely use it, living in a small town, so I haven't had that problem
Click to expand...
Click to collapse
Not so much worried about the screen not dimming, more dealing with the entire app crashing. Might be worth mentioning I'm on a hw0004 evo as well. I've also used Calkulins latest radios combo pack to make sure I'm at the latest of all radios.

Something new about the nav issue, the screen doesn't shut off fully, I let it go today to see what would happen and the screen stayed dim until the voice needed to prompt me for a turn in which the screen returned to normal brightness. So it would appear that for some reason the screen will dim after a couple minutes if you're on a straight leg of a trip but will bring the screen back up to normal brightness when it needs to communicate to turn or whatnot. Not sure what to make of that but I was able to confirm it multiple times.
**UPDATE**
Well, apprently a few other people have been seeing this issue from the google maps 5.7 update, so it looks like it might not be ROM related.

EVERY app, stock or not, continiously resets(closes and reopens).

Ive sort of tried to search this one (How do I search JUST the Epic 4g section of XDA??) and found no one describing this problem the way I do...
This is my second time having this issue, and the fix for it last time was a pain in the ass, so id like a new fix-
Every app, every aspect of my phone, continuously resets/reloads. This is most noticeable with Hancent SMS, as it saves a message as a draft when you close out of the app... Well, right now, ill be typing and "message saved as draft" will constantly pop up at the bottom of the screen (about once every 2 seconds), and the phone will lag and it will erase 1 or two characters(making me look like I cant type :silly: ).
If this was the only problem, maybe I could live with it, but it affects everything. Launcher Pro randomly/continuously resets. The notification bar often resets while trying to pull it down. The phone app will close or freeze as soon as I start receiving a call. Sometimes it'll play my ringtone without a way for me to answer, other times I never knew I missed a call unless they leave a voice mail... And sometimes its worse than others, sometimes its fine for an hour, then something goes stupid and even a reboot doesn't help. For instance, right now, it was happy. I launched aLogcat to check it out and now the screen orientation REFUSES to stay one way. Even setting the phone down, it switches directions every few seconds, which makes aLogcat reload and therefor its unusable.
I haven't mentioned what im running because Ive had this exact same issue on a totally different rom, almost a year ago, but im running-
build - SleeperROM_3.0.0_FC09
kernal - 2.6.35.7-Shadow-FC09_v1.0
baseband - S700.0.5s.FC09
firmware - 2.3.6
Ive had this happen on EB13 on the EpicExperience ROM too.
SOO, if anyone has advice on how to fix this, id be extremely interested.
On the other hand, last time I had this issue I was convinced it was a corrupt piece of memory somewhere early in the OS, something I corrupt during install, and I went ahead and reflashed and wiped and reflashed and wiped and returned to stock and etc. etc. etc... and that seemed to work... actually, I dont know exactly what part of the process fixed it, thats why I do not want to repeat it unless I have to... BUT, if someone would like to explain/point me in the right direction. I'd like to know how to DELETE AS MUCH AS POSSIBLE and FLASH as CLEAN as possible. (that is, if no one else knows of a fix for my problem)
thanks all!

Err, well only thing I can think of is a truly clean install using Odin. This means do not restore any data from backups. Then slowly begin installing applications 1-by-1 through the play store website (for speed sake) to see if your issue creeps up again.
It also couldn't hurt to format your SD card too. Corrupt data on the SD card can cause some wonky things at times.

get another device...i hope u have the equipment protection plan

Thanks for the advice guys OFF TO THE ODIN MACHINE! haha.

[Q] Updated to stock JB - Now phone freezes/crashes

Hi all -
I'm on AT&T, 100% stock, non-rooted, etc. I upgraded to JB last night via Kies without issue.
However, ever since the upgrade, my phone won't go more than 5 minutes without freezing and then crashing.
It's a very odd behavior... the screen will still animate. So, if I'm playing a game with a timer, the timer will still count down. But all touch input (including menu/home/back) does nothing. Home/back don't illuminate or do anything, but they do provide haptic feedback. Power button does turn the screen on/off.
Eventually after a few minutes, the lock screen comes up with the "tip" even though I've clicked to never show it again. However, it barely registers a swipe to unlock when it freezes again. At that point, it will usually self-reboot.
I've tried to enable some of the developer options to see if maybe there was a rogue program that was incompatible with JB, and maybe causing the issue, but I couldn't see any correlations.
I really want to avoid doing a factory reset if at all possible, as I have a game that I worked really hard on to beat a few levels, and I'd hate to lose my progress.
Anyone have any ideas on what I can try?
I should note that uninstalling programs is iffy... sometimes it works, other times it just uninstalls indefinitely.
Thanks!

Castaway78 said:
Hi all -
I'm on AT&T, 100% stock, non-rooted, etc. I upgraded to JB last night via Kies without issue.
However, ever since the upgrade, my phone won't go more than 5 minutes without freezing and then crashing.
It's a very odd behavior... the screen will still animate. So, if I'm playing a game with a timer, the timer will still count down. But all touch input (including menu/home/back) does nothing. Home/back don't illuminate or do anything, but they do provide haptic feedback. Power button does turn the screen on/off.
Eventually after a few minutes, the lock screen comes up with the "tip" even though I've clicked to never show it again. However, it barely registers a swipe to unlock when it freezes again. At that point, it will usually self-reboot.
I've tried to enable some of the developer options to see if maybe there was a rogue program that was incompatible with JB, and maybe causing the issue, but I couldn't see any correlations.
I really want to avoid doing a factory reset if at all possible, as I have a game that I worked really hard on to beat a few levels, and I'd hate to lose my progress.
Anyone have any ideas on what I can try?
I should note that uninstalling programs is iffy... sometimes it works, other times it just uninstalls indefinitely.
Thanks!
Click to expand...
Click to collapse
This sounds somewhat familiar to my experiences with JB. I rooted right away with the stock JB and had freezing / crash issues. So I then went pure stock and had issues (un-rooted). I then tried a custom TW-based ROM called BlackJelly and had issues. Now I am on CM10.1 which is AOSP JB4.2.1 based and things are even worse.
There seems to be no JB ROM that is stable for my phone. Getting very tired of this.
See my thread for details:
http://forum.xda-developers.com/showthread.php?t=2044769
- Ed

Strangely enough, my issue ended up going away. I think it was a rogue program that needed it's dalvik cache rebuilt. Once uninstalled, the phone worked great. Not sure what app it was.

[Q] No Notification Light

I've noticed over the past couple of days with my M8 that the notification light doesn't activate for anything but charging. I see that many people with Verizon versions are complaining of the same issue. Is anyone else experiencing this on their's? I already know that the only thing Tmo will tell me to try is a factory reset, or have the phone replaced (both a hassle this far into ownership).

Shift4g said:
I've noticed over the past couple of days with my M8 that the notification light doesn't activate for anything but charging. I see that many people with Verizon versions are complaining of the same issue. Is anyone else experiencing this on their's? I already know that the only thing Tmo will tell me to try is a factory reset, or have the phone replaced (both a hassle this far into ownership).
Click to expand...
Click to collapse
You may just want to RMA it so you have a new phone instead of finding something later down the line thats major. T-Mo will usually send you your replacement first and you mail your messed up one back. You could also just take it back to the store and do an exchange (I think) since it's within the 14 day period.

I've noticed it too. I get the amber light when charging and green when done, but thats it. I feel its more of a software bug than anything to do with the hardware.

Have you checked the "Notification Lights" setting under Display? It lets you choose which actions will activate the light.
That said, I have noticed the light is pretty minimal when compared to the SGS series notification lights. Additionally, I do not see a stock option to change the color of the light but no doubt that will come in time with Cyanogen Mod.

Booted into safe mode, tested the LEDs, they work fine. IMO, its definitely a software issue. Also, not sure if this is for everyone but booting into safemode also hoses your home screens. Now I have to redo all my folders.

SeanFloyd said:
Have you checked the "Notification Lights" setting under Display? It lets you choose which actions will activate the light.
Click to expand...
Click to collapse
I did check and play with that, yes. I even downloaded Lightflow with no success. I'm going to lean toward it being a software issue. Hopefully a patch gets compiled at some point.

small update. I was really wanted the stupid notification led to work. I didn't realize how much I looked at it when I'm at work. So I decided to wipe and start over. I made a nandroid backup just in case nothing worked and wiped. I read around the internet that if you don't log into your google account after the wipe, let it do its stuff that it would work so I did. Before I logged into my google account my wife texted me and bam, it worked. Ok, so far so good. I logged in and it still worked. Well, I don't want to go and redownload all my apps so I went into the custom recovery (Yes, I'm rooted and am using the rom in the development section that is rooted, deodexed and a few more things, but the rest is stock) and restored just the data partition. All my apps came back and the LED stopped. WTF is up with that!? I looked at all my apps and nothing was there that would affect the LED. I decided to use Titanium Backup and got all my apps backed up, wiped again, didn't log in to my google account until after the phone fully booted. Logged in, restored my apps via titanium backup and boom, the led was working and is still working. I also use an app called Helium to keep a few apps backed up to my Google Drive and happened to have my homescreen settings backed up (folders, background, etc) and restored that. All my folders came back and the LED still worked. I now have a working notification LED!
Another small thing too. I noticed that when I let my phone boot up before logging into my account, the experience was a little different. Certain things loaded on the phone that didn't load before. My only thought on that is that I had two Samsung phones before this one that maybe something downloaded from my google account, some setting it kept backed up for me, that broke the LED. If you don't log into the account until after you let it fully boot, there is no option to restore your settings from google. It all starts new.
the backup utility I use is called Helium. You CAN use it without root. YOu have to plug into your computer after each reboot but then it will work without being connected. It'll backup the apps data and restore it after you redownload it from the appstore and can also backup both the app and data. It'll backup the homescreens settings like folders. No, I'm not plugging it but its a huge time saver.
Anywho, I now have a working LED for notifications and that is the process i used. Its annoying but I'm glad it works now. Being able to backup and restore my apps is the only reason I did it. That process can be very long and annoying so being able to restore them all in 3 minutes is the only reason why I did the process.
Hope this helps someone and helps to realize its a software bug and not a physical bug.

My LED is working for notifications I just can't alter the color which is a bummer.

johnomaz said:
small update. I was really wanted the stupid notification led to work. I didn't realize how much I looked at it when I'm at work. So I decided to wipe and start over. I made a nandroid backup just in case nothing worked and wiped. I read around the internet that if you don't log into your google account after the wipe, let it do its stuff that it would work so I did. Before I logged into my google account my wife texted me and bam, it worked. Ok, so far so good. I logged in and it still worked. Well, I don't want to go and redownload all my apps so I went into the custom recovery (Yes, I'm rooted and am using the rom in the development section that is rooted, deodexed and a few more things, but the rest is stock) and restored just the data partition. All my apps came back and the LED stopped. WTF is up with that!? I looked at all my apps and nothing was there that would affect the LED. I decided to use Titanium Backup and got all my apps backed up, wiped again, didn't log in to my google account until after the phone fully booted. Logged in, restored my apps via titanium backup and boom, the led was working and is still working. I also use an app called Helium to keep a few apps backed up to my Google Drive and happened to have my homescreen settings backed up (folders, background, etc) and restored that. All my folders came back and the LED still worked. I now have a working notification LED!
Another small thing too. I noticed that when I let my phone boot up before logging into my account, the experience was a little different. Certain things loaded on the phone that didn't load before. My only thought on that is that I had two Samsung phones before this one that maybe something downloaded from my google account, some setting it kept backed up for me, that broke the LED. If you don't log into the account until after you let it fully boot, there is no option to restore your settings from google. It all starts new.
the backup utility I use is called Helium. You CAN use it without root. YOu have to plug into your computer after each reboot but then it will work without being connected. It'll backup the apps data and restore it after you redownload it from the appstore and can also backup both the app and data. It'll backup the homescreens settings like folders. No, I'm not plugging it but its a huge time saver.
Anywho, I now have a working LED for notifications and that is the process i used. Its annoying but I'm glad it works now. Being able to backup and restore my apps is the only reason I did it. That process can be very long and annoying so being able to restore them all in 3 minutes is the only reason why I did the process.
Hope this helps someone and helps to realize its a software bug and not a physical bug.
Click to expand...
Click to collapse
There was an issue like this with the m7, or at least the sprint version. It was after the first update they pushed, 4.3 maybe, though I'm not sure. If you installed the update you were fine, but if you installed it and then had to do a factory reset, if you signed in on the first boot up, the light wouldn't work. You had to let it boot to the sign in screen, restart, then sign in in order to get it to work right. It was really odd.

So I just got my phone. Do I have to wipe it and start over to get the damn notification light to work?? Kinda irritated...

E30Nova said:
So I just got my phone. Do I have to wipe it and start over to get the damn notification light to work?? Kinda irritated...
Click to expand...
Click to collapse
If its not working, yes. Annoying as hell but I am glad I took the time to do what my above post says. I guess I never realized how much I looked at the light.

Man, it was working for a bit, but only for gmail apparently.
I wonder, do the people that convert to the GPE RUU or flash a GPE rom have the same problem?

Yeah, the LED is definitely won't, but I also think it's a software thing. As long as it lights up when charging, the hardware is working, so... Sense bug. They also don't give you many options in the Settings as someone pointed out. I notice the issue more when using 3rd party apps, the stock Sense apps seem to be mostly working fine.

Remember - if you in any way shape or form are using any part of "do not disturb" - while it's enabled, there are no LED's as well and sounds and vibrations.

Yeah mine only works for charging. I tried restoring fresh (not rooted so didn't do titanium with old settings), however I did restore from HTC Backup. Mostly did it for my text messages. I may decide to restore one more time just to see if it works, but really this is software related. HTC should patch it up.

If anyone is still having this problem, theres an app in the play store that fixes this. Install it, run it once and uninstall. My notification light works perfectly now.
https://play.google.com/store/apps/details?id=de.jannux.switchledon