Database Develop

Forced Power off?

So as i continue using my Captivate there are little glitchy things i have been noticing. For example several times now in the past week or two i will have picked up my phone and hit the unlock button but nothing happens. Fair enough maybe its doing something else and has lagged for a second on the lock screen. Well i try hitting the unlock button again and it start its boot up process. I don't know if its a particular program or if its the o/s that is turning it off as a battery saving state. Maybe an app that is causing a forced Power off? Anyone have an idea to fix or locate the problem?
Android > Ios
Android > Ios

Do you have a stock ROM on it or a 3rd Party "Cooked" one?
My phone has started doing this - known issue. Only thing to really do is to exchange it with AT&T.
Just haven't had times - so I deal with the random Reboot 3-4 times a day

"3rd party cooked" - being the file i saved to the internal sd card and ran the update from system recovery? Sorry not good with android lingo lol
If you can't tell i am migrating from Ios
Android > Ios

[Q] Note 3 screen wont turn off

As stated, screen will not go off via timeout or power button tap. Power button is recognized and will bring up shut down menu like normal.
Device is rooted (thanks DG) and had been running well for over a week. Defrosted all apps from tibu in case I got over zealous but no better. A factory reset has not cleared it up either. Hoping the oneclick from the root package will correct the issue, but thats not until I get home later this evening.
Has anyone experienced / recovered from this issue?
Smart stay is turned off

I've had noticeable lag like a few seconds and sometimes I wonder if it's going to shut off but it always does. Better set a dark lock screen wallpaper to conserve your battery
Sent from my SAMSUNG-SM-N900A using xda app-developers app

I know this is kind of basic, but what is your setting here:
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app

Thanks for the thoughts.
I had already gone through the standard - double check the settings, remove recent apps. When all that failed and a factory reset still didn't clear it up I was beginning to worry about some kind of hardware damage (don't see how since I treat it better than my child ).
Fortunately the one click from the root seems to have restored proper operation. Back to rooting and rebuilding!

3496255310
papashex said:
Thanks for the thoughts.
I had already gone through the standard - double check the settings, remove recent apps. When all that failed and a factory reset still didn't clear it up I was beginning to worry about some kind of hardware damage (don't see how since I treat it better than my child ).
Fortunately the one click from the root seems to have restored proper operation. Back to rooting and rebuilding!
Click to expand...
Click to collapse
I'm having the same problem, I rooted through vroot.... what do you mean one click fixed it little my incite would be helpful....
thank you

Mine just did this, scared the hell out of me It also didn't go into deep sleep before it started. (Not rooted).
Pulled the battery, waited 30 seconds, plugged it back in.... same thing. Waited a few minutes, seems to have sorted itself out.
Scary....

This is definitely a software bug and it is related to the Headphone detection bug that people are having too (it's actually the same bug causing both issues). This happens to me quite often after I restart my phone. It's kind of like the phone hangs during the startup process. I've also noticed that the wifi/bluetooth status that was present before restarting the phone (i.e. whether they on/off) doesn't get applied until the bug sorts itself out.
For me sometimes this works: open an app like Chrome and then hit the home button to get back to your launcher. This works 95% of the time for me. I'm wondering if it has something to do with not having Touchwiz set as the default launcher.

I'm experiencing this same problem. If I don't manually turn the screen off by tapping the power button, the screen will not timeout.

Phone volume level resets

The volume level for the HTC phone app resets to maximum volume (and blasts the speaker's voice) after a certain period of time. I normally like to keep it at two volume levels from the bottom. The problem existed on ViperOne versions 5.0 and subsequent versions (all flashed after a complete wipe and run on either of the latest 401.8 or .9 firmware). Because of this issue, I have switched to another ROM, where the problem doesn't exist. I haven't tried version 5.7 because nothing in the changelog suggests this problem was addressed. I want to go back to ViperOne because the customizations offered are astounding.
I have tried the following to fix the problem, but none have worked:
1. killing the phone app
2. disabling Beats
3. upgrading to .9 firmware
I didn't mess with any phone or sound customizations in Venom Tweaks.
It appears another user posted about this problem in the ViperOne thread but nobody answered it.

@Turge, @j to the 4n, @hansbert: I have done a complete wipe and flashed the latest version, 5.8, but the problem still exists. I've also disabled Sound Enhancer and Beats and changed media permission with the phone app, to no avail. Any suggestions?

mpmtx said:
@Turge, @j to the 4n, @hansbert: I have done a complete wipe and flashed the latest version, 5.8, but the problem still exists. I've also disabled Sound Enhancer and Beats and changed media permission with the phone app, to no avail. Any suggestions?
Click to expand...
Click to collapse
I call or getting called daily...and never experienced that issue. I think if if would be a general issue, we would have more reports.
When you did the clean install, I hope you didnt restore any 3rd party apps before testing it?

j to the 4n said:
I call or getting called daily...and never experienced that issue. I think if if would be a general issue, we would have more reports.
When you did the clean install, I hope you didnt restore any 3rd party apps before testing it?
Click to expand...
Click to collapse
I did not install any third party apps. I don't think third party apps are the problem because I have used the same apps on other ROMs w/o the same issue. After searching, I found other people have experienced the same problem on different phones. A few reported the problem was a third party app, but I don't have the apps they deemed the culprit on my phone.
I'm running the same firmware as the ROM base. I did a complete wipe, chose stock config, ATT tweaks, and I did choose the option in AROMA to remove some apps and selected some HTC apps (although I can't think of a reason why this would affect the volume). If nobody else is reporting the same issue, it may be due to the extent my phone configuration differs from others'. It may be the combination of options I chose in the installer. I will to do an install with only default options selected and report back.

I think the source of the reset is remapping, in Venom Tweaks, any of the buttons (except of course the power button) to the action of turning off the screen. I installed the Volume Locker app, which locks the call volume and sets off the LED when there is an attempt to change the call volume. By accident, I noticed when I turned off the screen, many times the Volume Locker program would set off the LED and notify me that there was an attempt to change the call volume (what it called the "voice volume"). After some experimenting, I found I could replicate the problem every time I turned off the screen by a long press of the home button (I had always mapped this particular input to turn the screen off in Venom Tweaks).
Also, if any other button (e.g., double tap of home, volume down) except the power button is mapped to turn off the screen, there is an attempt to change the call volume by increasing it one level. If the button is used repeatedly to turn off the screen and the volume level is not readjusted, the volume level reaches maximum. On the other hand, if I use only the power button to turn off the screen and disable Volume Locker, no change in call volume occurs. So I think there may be an issue in the way the buttons are mapped to turn off the screen.
Can somebody else try to replicate this issue to verify I'm not mistaken?
@j to the 4n: If you think this problem merits attention, I can send you a bug report log. Just let me know.

[Q] Is anyone getting awful bluetooth reception?

I have a pair of bluetooth earbuds that I use when I'm on the go, and ever since I got my new turbo, they have been constantly skipping and stuttering when I try to listen to music. It's totally ridiculous, the devices are only two feet away from each other, at most! Is anyone else having similar issues?

Rixanu said:
I have a pair of bluetooth earbuds that I use when I'm on the go, and ever since I got my new turbo, they have been constantly skipping and stuttering when I try to listen to music. It's totally ridiculous, the devices are only two feet away from each other, at most! Is anyone else having similar issues?
Click to expand...
Click to collapse
Nope. Mine is mint in the car with calls and music. Streams to a kitchen speaker perfect too.

civiksi said:
Nope. Mine is mint in the car with calls and music. Streams to a kitchen speaker perfect too.
Click to expand...
Click to collapse
Hmmm, I wonder if it's motion based. I'm sitting in my room listening to it now and it's a lot better. Unfortunately that doesn't really solve my problem, though.

Rixanu said:
Hmmm, I wonder if it's motion based. I'm sitting in my room listening to it now and it's a lot better. Unfortunately that doesn't really solve my problem, though.
Click to expand...
Click to collapse
Rixanu - I think you're on to something... I'll give my "story" and hopefully someone a little more savvy than us can help figure it out.
I switched over from the good ole Galaxy Nexus about a month ago. No major complaints on the Turbo yet as we await Lollipop, with the exception of this Bluetooth issue. I have the Bluetooth paired in the car, and a set of headphones - music and everything worked perfectly on the GNex through the Bluetooth. Now, primarily, it's often choppy (mustic anyway) - for reference, when listening to music I listen via Google Play (all access or whatever they call it now). I figured the choppiness was related to the fact that the music was being streamed since most wasn't downloaded yet, but after very limited experimenting, I believe it must have to do with the physical Bluetooth radio. I had noticed in the past that when the music streams perfectly, a lot of times if I pick it up to check an email, text, etc., it becomes choppy, but thought that was strange since the RAM should be more than sufficient to multitask without choppiness. On my way home from a friend's, I played around and stuck my hand over various parts of the back of the phone, and would press the phone against my pant, etc., and could effectively interfere completely with the connection such that it would be only silent, and not even choppy. Yet, while the music wasn't playing, the track continued to playback on the device and when the music would pick up after I moved the phone, it would be 10 seconds or whatever later as if it had been playing straight through the whole time.
I haven't tested this theory too much yet, but I think combined with your issue, there's certainly something there. Unfortunately, I frequent these parts in order to find answers to these types of issues and don't have the solutions myself.
Do we have lemons, or is this issue prevalent?
I'm happy to provide more info to anyone that can help.
Thanks in advance!

I was having the same problem. It was so bad Bluetooth was completely unusable. I contacted Motorola and they sent me the following steps to try. I worked perfectly. Good luck.
Dear Michael
Thank you for contact Motorola tech support, i send to you the steps you have to follow up to clear the cache for you Driod turbo
Before you do the Wipe cache, please un pair the Blue tooth devices and forget it for the phone, after you do that follow the steps and do the wipe cache.
This will remove any temporary files that may be causing the problem, but will not delete your files or settings.
1. With the phone powered off, press the VOL DOWN KEY for 2-3 seconds then POWER key then release.
2. The device will display different BOOT OPTIONS
3. Use the VOL DOWN Key to SCROLL to Recovery and VOL UP Key to select (I think he meant POWER to select)
Tip: If the device reboots, you may have waited to long to make a selection, you will need to begin the process again.
4. The device will display the Motorola logo and then the Android in distress ( logo with Exclamation mark)
5. Press and hold the VOL UP key for 10-15 seconds. While still holding the VOL UP key tap and release the POWER key
Tip: You can try this step, holding the phone in landscape. If you are stuck on step 6, try a force reboot by pressing the Power key and Vol Down key, and start the process again.
6. The device will display additional menu options (Text will appear in BLUE)
7. Use the VOL DOWN Key to scroll to wipe cache partition and the POWER Key to select this option
8. The device will then perform the partition wipe
9. The device will reboot and start the normal power up sequence
Answer Title: Clear Cache Partition
Answer Link: https://motorola-global-en-usa.custhelp.com/app/answers/detail/a_id/102367
Thank you for choosing Motorola products
Regards.
Richard.

I think Bluetooth stinks. Poorly implemented, stupid pairing issues, and poor quality. I have had very little success with Bluetooth on any device I have had.
Sent from my XT1254 using XDA Free mobile app

Found a Fix for the Stuttering BT issue. It's the dumb kernel on 5.02 that stutters the playback as soon as screen is off. I used a partial wakelock so the cpu stays active after screen off with this app. It works. No more stuttering. As for speakers that require high sample rate I just switched the cpu governor to performance. It's a workaround but the partial wakelock should work especially on bluetooth headphones. Here's the app's link https://play.google.com/store/apps/details?id=eu.thedarken.wl&hl=en

Every time I drive away from my house and the phone loses wifi signal, the bluetooth skips really bad during the transition. Once I get far enough away, it usually clears up again. For my situation, it seems the wifi radio is somehow interfering with the bluetooth signal.

Strange behavior from Nexus 6 Display

My N6 is running Android 7.0, have not had problems until a couple of days ago.
The right half of my display started scrolling while, the left side of the display was normal. I powered it off and back on a couple of times and, the issue was still there; I panicked and did a factory reset from the "Settings" menu hoping that would solve the problem, it did not; I still had a jacked up display.
Is this a failure mode that anyone else has seen?
I powered the phone off and, turned it back on with the volume control button pressed and, it booted into safe mode(?) then, I toggled the mode to "Restart" and, upon restart, my display was normal. This was not the end as, it will occasionally be split screen when I unlock it. I have discovered that sometimes if I receive or make a call the display will return to normal, if not, I just power cycle it into the safe-recovery mode (but not do anything else) then toggle to restart and, it's all good until next time.
Is it possible that another device (blue-tooth) in close proximity could cause my phone display to act up?

queensgate555 said:
My N6 is running Android 7.0, have not had problems until a couple of days ago.
The right half of my display started scrolling while, the left side of the display was normal. I powered it off and back on a couple of times and, the issue was still there; I panicked and did a factory reset from the "Settings" menu hoping that would solve the problem, it did not; I still had a jacked up display.
Is this a failure mode that anyone else has seen?
I powered the phone off and, turned it back on with the volume control button pressed and, it booted into safe mode(?) then, I toggled the mode to "Restart" and, upon restart, my display was normal. This was not the end as, it will occasionally be split screen when I unlock it. I have discovered that sometimes if I receive or make a call the display will return to normal, if not, I just power cycle it into the safe-recovery mode (but not do anything else) then toggle to restart and, it's all good until next time.
Is it possible that another device (blue-tooth) in close proximity could cause my phone display to act up?
Click to expand...
Click to collapse
So weird, but same thing has been happening to me the past few days. But I have a justified cause. It started immediately after installing Franco Kernel.
Sent from my Nexus 6 using Tapatalk

queensgate555 said:
My N6 is running Android 7.0, have not had problems until a couple of days ago.
The right half of my display started scrolling while, the left side of the display was normal. I powered it off and back on a couple of times and, the issue was still there; I panicked and did a factory reset from the "Settings" menu hoping that would solve the problem, it did not; I still had a jacked up display.
Is this a failure mode that anyone else has seen?
I powered the phone off and, turned it back on with the volume control button pressed and, it booted into safe mode(?) then, I toggled the mode to "Restart" and, upon restart, my display was normal. This was not the end as, it will occasionally be split screen when I unlock it. I have discovered that sometimes if I receive or make a call the display will return to normal, if not, I just power cycle it into the safe-recovery mode (but not do anything else) then toggle to restart and, it's all good until next time.
Is it possible that another device (blue-tooth) in close proximity could cause my phone display to act up?
Click to expand...
Click to collapse
It is a known hardware issue in some N6 phones, some have it and it only shows up on certain rom / kernel combos, even stock. One thing that helps is to use the interactive kernel governor and/or the down sampling factor. Of course you will need a kernel manager app for that.
https://forum.xda-developers.com/showpost.php?p=63249802&postcount=4602

Pkt_Lnt said:
It is a known hardware issue in some N6 phones, some have it and it only shows up on certain rom / kernel combos, even stock. One thing that helps is to use the interactive kernel governor and/or the down sampling factor. Of course you will need a kernel manager app for that.
https://forum.xda-developers.com/showpost.php?p=63249802&postcount=4602
Click to expand...
Click to collapse
That's good to know.
I inserted the Bluetooth question because, coincidentally or not this issue presented when I acquired a wristwatch ($19.00 from China) that connected to my phone via Bluetooth, It had it's own fitness app which I installed (which did not work). To me, there seems to be more "connection" than expected as, the fault thing only seems to happen when the watch was powered on (but not even connected via Bluetooth). If there was a bug caused by the companion app, that should have been taken care of by the factory reset.
I'm going to do some "scientific testing" by, not powering on the watch for a week and see if the issue reoccurs. Meanwhile, I will read up on kernel manager apps.

I've since flashed stock pn, and now elementalx. It's not acted up yet. Seemes to be a better performance kernel. We'll see how battery is. Sorry to hijack your thread!
Sent from my Nexus 6 using Tapatalk

queensgate555 said:
That's good to know.
I inserted the Bluetooth question because, coincidentally or not this issue presented when I acquired a wristwatch ($19.00 from China) that connected to my phone via Bluetooth, It had it's own fitness app which I installed (which did not work). To me, there seems to be more "connection" than expected as, the fault thing only seems to happen when the watch was powered on (but not even connected via Bluetooth). If there was a bug caused by the companion app, that should have been taken care of by the factory reset.
I'm going to do some "scientific testing" by, not powering on the watch for a week and see if the issue reoccurs. Meanwhile, I will read up on kernel manager apps.
Click to expand...
Click to collapse
Well, so much for "scientific testing" and wishful thinking.....didn't take long to eliminate the wristwatch, now to fix the problem.
.