Database Develop

Prevent Kaiser/Tilt/8925 from Vibrate on Boot?

Hi,
Own a 8125/Wizard, and it never vibrated on startup/reboot.
So, my 8925 is annoying the heck out of me when it vibrates on boot!
Any way to disable it? Doesn't seem that a registry hack would process the desired change so early in the HTC startup sequence. (Sorry if this has been asked before -- I couldn't find it in a google/wiki search.)
Thx.

Yes, it has been asked for hundreds times before; and still has no solution. You can always put it (Kaiser) in your shock if you find boot up vibration is annoyed; or you may want to take out the vibrator, too.

I don't find it annoying at all. I find it really informative so in case I turn it off and I accidentally turn it on, if I feel that vibration, I can quickly take out the battery before any sound can come out of the phone.

phi11yphan said:
Hi,
Own a 8125/Wizard, and it never vibrated on startup/reboot.
So, my 8925 is annoying the heck out of me when it vibrates on boot!
Any way to disable it? Doesn't seem that a registry hack would process the desired change so early in the HTC startup sequence. (Sorry if this has been asked before -- I couldn't find it in a google/wiki search.)
Thx.
Click to expand...
Click to collapse
How often do you need to reboot? Other than software installs I rarely need to reboot, is it really that much of an inconvenience?

Nghiem said:
Yes, it has been asked for hundreds times before; and still has no solution. You can always put it (Kaiser) in your shock if you find boot up vibration is annoyed; or you may want to take out the vibrator, too.
Click to expand...
Click to collapse
Put it in my shock?

It was asked before? Sorry -- didn't see anything related, using searches on "disable" and "vibrate" and ("*boot*" or "*start*").
wizzzard said:
How often do you need to reboot? Other than software installs I rarely need to reboot, is it really that much of an inconvenience?
Click to expand...
Click to collapse
In this case, it's an inconvenience. (But if it were preference, would that change the question at all? )
I've been needing to reboot my Kaiser frequently because of a battery drain problem. Reboot triggers the vibrate, which is not helping my low battery situation.
I don't turn off my phone -- I always keep it on (unless it dies as described above), and charge every night. So, I don't need to know when it turns on. The vibrate notification on boot is only wasting battery for me -- even without a drain problem. (But I wouldn't want to permanently disable the vibrate, in case I need vibrate mode once every ~2 months or so, like in a noisy environment.)
Put it like this guys -- was there ever any good purpose for when your computer beeps on boot? Just because it can, does that mean it should? Default should be 'disabled'. Otherwise, HTC should at least provide us with an OPTION to disable! Just like the bios option to disable a computer speaker's beep on boot.
As to battery drain, that's another issue. (If anyone is curious, it's the original 1350 mAh, and it's heating to 108 F using up to 650 Ah. Haven't isolated which app might be doing it. Tried WM5 and WM6 roms. Hard resets. Reflash. Disabled BT, GPS, HSPD, and took all apps off auto-download data. Ordered new 2400 and 1600 mAh batteres, in case my battery is fried.... but I think that's just me being optimistic.)

Computer beeps on Startup
phi11yphan said:
Put it like this guys -- was there ever any good purpose for when your computer beeps on boot? Just because it can, does that mean it should? Default should be 'disabled'. Otherwise, HTC should at least provide us with an OPTION to disable! Just like the bios option to disable a computer speaker's beep on boot.
Click to expand...
Click to collapse
I don't know about the whole vibrate on startup thing as it does not bother me since I rarely re-boot the phone, but the beep on start up on a computer did originally (and possibly still does) serve a good purpose. The beeps were used to convey error codes. For example, on one of my old pc's, 1 beep meant things were ok. two beeps indicated an error in the processor, etc.
I know this was off post... sorry

Can someone with 2.2 froyo update perform this check for me..."stay awake" gone?

Can someone with 2.2 froyo update perform this check for me..."stay awake" gone?
So I installed the new froyo update last night and I see one thing missing I liked which was on the 2.1. It had a feature called "stay awake" under the application settings I believe. Well I go to charge my phone for the first time since installing 2.2 and the screen stays on and never sleeps unless I press the lock button. This is only with the usb/charger plugged in.
Can someone verify theres is the same way please? I am thinking they either designed it this way or there is was a problem with my install? Not a big issue, just something I wanted to get clarification on. Thanks!

They did remove Stay Awake from every froyo I've looked at.
It's very easy to add it back. You have to decompile the Settings.apk and remove one line from the .smali files.
Sent from my Captivate using XDA Premium.

I had the same exact problem when I did my upgrade. I was worried about burning the screen and went looking for some fixes for it. You can edit the Settings APK like the above reply mentions Here.
You can also download some widgets to toggle it.
However in playing with the phone I did a couple of reboots, once witht he USB plugged in, (not sure that makes a difference) and noticed that the phone timed out like normal while it was plugged in so I left it alone after that.

Thanks for the replies guys. New twist to the story today. I left my "samsung" OEM charger(one that came with my Cappy) at work Friday so I went to AT&T to buy one. They didn't have an OEM samsung charger but only the AT&T branded micro usb ones so I picked one of those up.
Went home to plug it in, and the screen sleeps/turns off like normal. So now I'm thinking it has something to do with the charger being used? Interesting...

Also still reading up on all the stickies here on XDA on how to modify this phone from rooting/etc so can't quite get into that yet! =/

OK, Similar problem, hopefully someone can help. My phone used to stay on when plugged in (even with 2.2). Convenient since I frequently use it for GPS (Google maps and Google navigator). I tried to use it for GPS the other day, and it kept turning off. Looked for the setting to stay on when plugged in, and noticed it was gone.
Apparently some software I was using changed a setting somewhere. Any EASY way to switch the feature on and off? Can someone recommend a widget or utility to do it?

S4A Occasionally Won't Wake from Sleep

I can't figure out what's causing it. I don't have very many apps installed that didn't come with the phone, and any I did install were from the Play Store. I haven't done any modifications such as root to the device.
In order to bring it back to life, I have to either hold the power button down for 30 seconds to shut it down (or take out the battery) and power it back on.
Interestingly, if I have notifications waiting and the LED is flashing, that continues to flash even if the phone won't wake up.
I did 'disable' several of the bloatware apps in the app management area in Settings. I'm starting to think that must be what's causing it. Is there a particular bloatware app that should never be disabled? One that would cause this issue?
Other apps I've installed are things like Netflix, eBay, the app for my bank, and a TV-listings app. Pretty basic stuff. I don't think any of those would be the problem, would they?
Remaining battery doesn't appear to have an effect. It's happened with full battery and somewhat low battery.
'Services' that I use are Exchange push email and Gmail. I also have it Bluetooth synched to my car's hands-free thing.
Any help would be appreciated. Taking my phone out of my pocket to use it just to find that it's not responsive is very troublesome.
Thanks.
EDIT: For clarification, this is an AT&T version of the S4A.

EvilTelephone said:
I can't figure out what's causing it. I don't have very many apps installed that didn't come with the phone, and any I did install were from the Play Store. I haven't done any modifications such as root to the device.
In order to bring it back to life, I have to either hold the power button down for 30 seconds to shut it down (or take out the battery) and power it back on.
Interestingly, if I have notifications waiting and the LED is flashing, that continues to flash even if the phone won't wake up.
I did 'disable' several of the bloatware apps in the app management area in Settings. I'm starting to think that must be what's causing it. Is there a particular bloatware app that should never be disabled? One that would cause this issue?
Other apps I've installed are things like Netflix, eBay, the app for my bank, and a TV-listings app. Pretty basic stuff. I don't think any of those would be the problem, would they?
Remaining battery doesn't appear to have an effect. It's happened with full battery and somewhat low battery.
'Services' that I use are Exchange push email and Gmail. I also have it Bluetooth synched to my car's hands-free thing.
Any help would be appreciated. Taking my phone out of my pocket to use it just to find that it's not responsive is very troublesome.
Thanks.
EDIT: For clarification, this is an AT&T version of the S4A.
Click to expand...
Click to collapse
maybe u can enable back all the apps that u have disabled and see if it happens anymore.
u mentioned "the phone won't wake up" and "not responsive". do u mean that the screen stayed off and u are unable to get the screen to be on?

cfchong said:
u mentioned "the phone won't wake up" and "not responsive". do u mean that the screen stayed off and u are unable to get the screen to be on?
Click to expand...
Click to collapse
That's right. None of the buttons wake the phone up or turn on the screen. I can tell the phone is still 'on' though. It's not like it got powered off in my pocket.

The advice you've got is sound - if you think it might be because of disabled apps, re-enable them all and see if it keeps happening. If it doesn't... well then you disable them one at a time until it starts happening again.
Then you come back to the forum again and let everyone know which app never to disable.
If it doesn't stop happening after re-enabling all the apps... well then my guess would be a faulty device. Can't think of any other logical reason for it to behave like that. So try the apps first, if that doesn't help, "return to sender".

EvilTelephone said:
That's right. None of the buttons wake the phone up or turn on the screen. I can tell the phone is still 'on' though. It's not like it got powered off in my pocket.
Click to expand...
Click to collapse
if enabling back all system apps do not resolve the problem, try disabling all user apps to test. one of your downloaded app may be the cause.

Alright, over the past month I've done a bunch of testing. Here are my results.
1. Re-enabling all the system apps didn't help.
2. I uninstalled all my user apps. Didn't help.
3. I completely reset the phone to stock settings and formatted all storage. That didn't help.
4. I figured maybe it was something with bluetooth since it seemed to happen after I used bluetooth devices. I disabled bluetooth completely. It didn't help.
I'm out of ideas for the moment. Could the phone just be bad? I would wonder why the issue only happens occasionally.
Thanks.

Start a chat with Samsung. They have always been good to me.
GT-i9295(i537) running SafeStrap

I have the same problem, is there any solution, thanks

ogbeate said:
I have the same problem, is there any solution, thanks
Click to expand...
Click to collapse
Solved, rom change and ready, do not turn off more

I have the same problem in i9500. I now live in China and have purchased an s2, s3 and now the s4 from China Unicom. I have successfully rooted and flashed new ROMS (latest HK stock firmware) on the S2 and S3. When I bought the s4, it worked fine. I immediately flashed the latest stock HK ROM using Odin 3.07, After flashing, the phone is unresponsive after going into deep sleep meaning that nothing happens when I press the power button. After a long press of the power button, the phone will re-boot. Sometimes I have to pull the battery. Again, this phone is totally stock. I haven't added any applications. I re-flashed the stock China Unicom formware and I took the phone to the Samsung Service facility and they did a new flash. Phone worked great. I take it home, flash the HK ROM with Odin...same results; phone is unresponsive after going into deep sleep. I return to the Samsung service store and they again flash the phone. Phone works fine. What are they doing that I'm not doing? Could the partition table get corrupted during my flash processes. Should I try another version of Odin? Should I try a PIT file and try that? I'm downloading the ROM's from SamMobile. Thanks in advance for any suggestions.
Edit: I fixed this problem by upgrading to 4.3 which brought it's own set of problems.

[Q] Moto X randomly dies

Ok, so I bought a brand new in box Moto X from an acquaintance. After a month or two it started randomly rebooting, and after a couple of weeks of rebooting once or more per day, it died. Wouldn't power on (not even recovery). I sent it in for repair>got it back>3 days and it died again>sent it in again>got it back>1 day and it died again>sent it in again>got replacement>2-3 months later the new phone is starting the cycle again. Every time I pull it out of my pocket, the lock button doesn't work, and it's locked up on Active Display. I hold the power button and reboot it, only to have it happen again in an hour. I am doing a factory reset now--does anyone have any idea what the problem may be? what i should avoid when setting it up again?
This phone is 100% untampered with. No root, no nothing.
Please help me out. Thanks!

quaxer said:
Ok, so I bought a brand new in box Moto X from an acquaintance. After a month or two it started randomly rebooting, and after a couple of weeks of rebooting once or more per day, it died. Wouldn't power on (not even recovery). I sent it in for repair>got it back>3 days and it died again>sent it in again>got it back>1 day and it died again>sent it in again>got replacement>2-3 months later the new phone is starting the cycle again. Every time I pull it out of my pocket, the lock button doesn't work, and it's locked up on Active Display. I hold the power button and reboot it, only to have it happen again in an hour. I am doing a factory reset now--does anyone have any idea what the problem may be? what i should avoid when setting it up again?
This phone is 100% untampered with. No root, no nothing.
Please help me out. Thanks!
Click to expand...
Click to collapse
That sounds like a headache.
When were both phones manufactured? What version of KK were you running? Did you upgrade software OTA, if so what did it upgrade to?
Are you saying you never downloaded any apps? never installed anything on the phone? What services did you use? (apps.. anything, what were they?) Were there any other things you noticed out of the ordinary? What were Motorola's responses the first time they replaced the phone? What are their responses now that you are having the same issues with this replacement device?
Otherwise I'd advise you let us know what modifications (apps installed, anything) you had done and continue to do, that will give a variable context to the issue, at least. Other wise we a have an issue with no variables on the actual phone. The more information you give the higher quality the responses you can receive

bothgoodandbad said:
That sounds like a headache.
When were both phones manufactured? What version of KK were you running? Did you upgrade software OTA, if so what did it upgrade to?
Are you saying you never downloaded any apps? never installed anything on the phone? What services did you use? (apps.. anything, what were they?) Were there any other things you noticed out of the ordinary? What were Motorola's responses the first time they replaced the phone? What are their responses now that you are having the same issues with this replacement device?
Otherwise I'd advise you let us know what modifications (apps installed, anything) you had done and continue to do, that will give a variable context to the issue, at least. Other wise we a have an issue with no variables on the actual phone. The more information you give the higher quality the responses you can receive
Click to expand...
Click to collapse
1) I don't know when the phones were manufactured. Can you advise me how to tell?
2) I had a number of apps on it including WhatsApp, BBM, Toggl, SwiftKey, The Weather Network, ES File Explorer, BBC, The Economist, Espresso, Google Now Launcher, Dictionary.com, TimmyMe, MyBackup Pro, eBay, Amazon, Kayak and a few others. It's still doing the same thing after a data wipe.
3) The first three times I had trouble they had me send in the phone with no quibbles. The first two times they tried to repair it (the documentation just said "replaced component, and reflashed software"), and after two failed attempts, they simply replaced it. Now they want to start the cycle over again... asking me to send it in for repair.
When they sent me the replacement it arrived with 4.4.4. The previous phone had issues with 4.4.2 and 4.4.3 both. I am still running stock 4.4.4.
Thanks for your help

quaxer said:
1) I don't know when the phones were manufactured. Can you advise me how to tell?
2) I had a number of apps on it including WhatsApp, BBM, Toggl, SwiftKey, The Weather Network, ES File Explorer, BBC, The Economist, Espresso, Google Now Launcher, Dictionary.com, TimmyMe, MyBackup Pro, eBay, Amazon, Kayak and a few others. It's still doing the same thing after a data wipe.
3) The first three times I had trouble they had me send in the phone with no quibbles. The first two times they tried to repair it (the documentation just said "replaced component, and reflashed software"), and after two failed attempts, they simply replaced it. Now they want to start the cycle over again... asking me to send it in for repair.
When they sent me the replacement it arrived with 4.4.4. The previous phone had issues with 4.4.2 and 4.4.3 both. I am still running stock 4.4.4.
Thanks for your help
Click to expand...
Click to collapse
Thanks, hopefully your info helps someone help you better or hopefully it can help/spark someone truly seasoned in android/moto x etc to chime in
To check your manufacture date boot into your fastboot menu, check image to verify you're there.
Then choose BP Tools and then once that menu loads choose the option for UPC/Manufacture date read out, check for the date when it appears on the screen, maybe you are on a batch that has specific issues.
I've never heard of this issue, yuk sounds terrible. Goodluck! If you do end up finding answers somewhere else can you please come back here and post the resolution?

When I hit BP Tools it just reboots the phone... I don't know what's wrong???

maybe static electricity?
or do you use any cases?
maybe wrong charger?

Multiple devices, different Android versions, Sounds like an app issue to me.
If it happens frequently, then that is good in a way... You could factory reset and don't install a single app. If it doesn't act up for a couple days ..... Install about 5 apps. Go a couple days.... Install 5 more, etc... Etc. When it starts to act up, you know it's an app you recently installed, so it'll be easier to narrow down.
A logcat could help too. Search on that for how. It would likely show what happened at the time of the reboot /shutdown.

quaxer said:
1) I don't know when the phones were manufactured. Can you advise me how to tell?
2) I had a number of apps on it including WhatsApp, BBM, Toggl, SwiftKey, The Weather Network, ES File Explorer, BBC, The Economist, Espresso, Google Now Launcher, Dictionary.com, TimmyMe, MyBackup Pro, eBay, Amazon, Kayak and a few others. It's still doing the same thing after a data wipe.
3) The first three times I had trouble they had me send in the phone with no quibbles. The first two times they tried to repair it (the documentation just said "replaced component, and reflashed software"), and after two failed attempts, they simply replaced it. Now they want to start the cycle over again... asking me to send it in for repair.
When they sent me the replacement it arrived with 4.4.4. The previous phone had issues with 4.4.2 and 4.4.3 both. I am still running stock 4.4.4.
Thanks for your help
Click to expand...
Click to collapse
quaxer said:
When I hit BP Tools it just reboots the phone... I don't know what's wrong???
Click to expand...
Click to collapse
use the volume +up button (once BP Tools is highlighted) and not the power button to select BP Tools I'm assuming that's what's happening, hmm

I would send it back to Motorola again. If the issues continue, tell them you want it replaced with something else like the 2014 Moto X.

Ok -- so the issues stopped completely over Christmas vacation, but I went back to work this morning (I work in a dusty woodworking plant) with my phone in my pocket, and bang, they were back. Every time I pulled my phone out of my pocket it had powered off, and finally it didn't want to power back on. I called Moto, and this time actually got a competent rep on the line. He blamed the issues on static electricity, and I second his opinion, because the machinery I work with tends to create some static, and the dust in my pocket may exacerbate the problem (?)
Anyway, he recommended that I plug the phone in and hold the power button for 2 minutes to drain the static. Voila! It seems to have worked.
Solved for the time being. Thanks everyone for your input.

quaxer said:
Ok -- so the issues stopped completely over Christmas vacation, but I went back to work this morning (I work in a dusty woodworking plant) with my phone in my pocket, and bang, they were back. Every time I pulled my phone out of my pocket it had powered off, and finally it didn't want to power back on. I called Moto, and this time actually got a competent rep on the line. He blamed the issues on static electricity, and I second his opinion, because the machinery I work with tends to create some static, and the dust in my pocket may exacerbate the problem (?)
Anyway, he recommended that I plug the phone in and hold the power button for 2 minutes to drain the static. Voila! It seems to have worked.
Solved for the time being. Thanks everyone for your input.
Click to expand...
Click to collapse
This thread is awesome.
Also, I recommend leaving your phone on your desk/home/car when you work
Or maybe a full-body armor case or something.
Statics & electronics = bad idea. Even if you can drain it and it works, it's still hurting the components inside.

So, it's been a bit, but I just came back to this phone. I never did send it in to Moto, though it seemed to have died completely. It sat in the drawer for a couple of weeks, and now on a whim I plugged it into my computer, and it started up! I had never tried plugging it into a computer, just chargers...
BUT,
In the last 10 minutes it's been sitting here rebooting itself every 2 minutes... I guess I'll try wiping it again (It didn't do the trick last time), but this phone has serious problems.

Droid Turbo responding slow, locks up regularly. Any ideas?

I've got a co-worker with a Droid Turbo that has been working fine for him for a long time. However, within the last week or so it's been acting up. As the resident computer geek he's asking me for any help, and as most geeks do... I'm asking you other geeks for help!
I've not used this model before so I'm pretty ignorant to this mode specifically though I've been and Android user for many years now.
Here's the info I have: The phone will sometimes simply lock up and fail to respond at all. Occasionally it will fix itself and start to respond, but usually it requires a reboot of the phone. There doesn't appear to be any one specific thing thing/action/app that causes the lockup.
He is not a "power user" or one who would go into settings and mess with stuff or install questionable side loaded apps. He did not install a new app recently.
The phone charges without a problem and when it locks up it can be rebooted by holding the power button. I rebooted his phone and it everything came back, but it was operating slowly...
He's running 5.1, and I checked for updates and it reports being on the latest version.
So questions:
1. Is this a known issue with Droid Turbo's at all? If so, is there a fix for it?
2. What's the best diagnostic apps for Android? I've never really had to use one myself recently so I'm not up on this.
Thanks for any help.

I'd probably recommend doing a factory reset. The firmware on the 5.1 turbo seems to be kind of unstable with age so resetting all of that will probably fix it.

RedRamage said:
I've got a co-worker with a Droid Turbo that has been working fine for him for a long time. However, within the last week or so it's been acting up. As the resident computer geek he's asking me for any help, and as most geeks do... I'm asking you other geeks for help!
I've not used this model before so I'm pretty ignorant to this mode specifically though I've been and Android user for many years now.
Here's the info I have: The phone will sometimes simply lock up and fail to respond at all. Occasionally it will fix itself and start to respond, but usually it requires a reboot of the phone. There doesn't appear to be any one specific thing thing/action/app that causes the lockup.
He is not a "power user" or one who would go into settings and mess with stuff or install questionable side loaded apps. He did not install a new app recently.
The phone charges without a problem and when it locks up it can be rebooted by holding the power button. I rebooted his phone and it everything came back, but it was operating slowly...
He's running 5.1, and I checked for updates and it reports being on the latest version.
So questions:
1. Is this a known issue with Droid Turbo's at all? If so, is there a fix for it?
2. What's the best diagnostic apps for Android? I've never really had to use one myself recently so I'm not up on this.
Thanks for any help.
Click to expand...
Click to collapse
i know this is 2-weeks old, but I would try to clear out the cache in the "storage". secondly, wiping cache from the recovery menu always helps as well.
finally, check to see if any apps are running in the background, as some of those contain ads that tend to hog RAM.