Hello everybody,
I was playing with SWApp Link when suddenly my watch restarted by itself and got stuck in the Omate TrueSmart logo... I can't turn it off and it's getting hot... isn't a way to restart it like a smartphone?? I don't have the screwdriver with me so I can't pull the battery off, and also I want to avoid that because of the warranty...
Any ideas?
Connect it to adb, type "adb reboot" in a command console.
I left home with the watch fully charged so I didn't bring the charger either...
I guess I'll have to wait until it dies or I arrive home and try to reboot it using adb... the thing is I already tried once to connect it to my Mac and see if adb recognized it but had no luck...
EDIT: Finally, battery's dead... I'll charge it once I arrive home... two days with my TrueSmart and already got a freeze... disappointing...
If that happens again, see if you can get a log while it hangs there with "adb logcat > ts1_freeze.txt"
I'll do that, thanks for the advise.
I now have a worse problem... My Bluetooth isn't working... I turn it on and it turns off immediately, I mean, I barely can see the switch changing from OFF to ON when it changes back to OFF.
Sent from my GT-I9300 using XDA Premium 4 mobile app
Go into settings, disable quick boot under accessibility, and reboot.
This is actually a bug introduced in 4.2.2 and usually requires you to wipe cache to clear it out.
Thanks! :cyclops:
Should I enable it again? What is it for?
BeRniTo said:
Thanks! :cyclops:
Should I enable it again? What is it for?
Click to expand...
Click to collapse
Just keeps the device in hibernate for quick startup. If drivers crash, they can't be recovered without a power cycle.
Related
So just recently I have been noticing that sometimes after my phone lock i can wake it up. Just stays on a black screen, adb works though as i can adb reboot. But the phone will not wake up until i pull the battery or adb reboot. And today at work i tried to adb reboot, it didn´t work and when i did adb devices i got this.
*****@TECH:~$ adb devices
List of devices attached
???????????? no permissions
Click to expand...
Click to collapse
The sleep issue has happened on MIUI and currently on Anroid Revolution roms. I don´t normally post, but i really can´t find anything on this issue. Help is appreciated.
Is there a certain app that you have used in all the roms. Sometimes when app is doing a lot of background work it will lock up the phone.
Sent from my PG86100 using XDA App
hmm that seems to be a possibility. but i dont think any apps i use do so much background work that it locks it up i mean. every time this happens it drives me nuts lol.
Try reflashing your kernel after a wipe of cache and davlik-cache and see if that helps at all. Also are you overclocking?? Or underclocking?? If so maybe your sleep gov min frequency is set to low. If this is the case then try rasing it a little and see if that helps as well.
Locked & Loaded
""shooter on Deck""
ok ill try raising the sleep clock a bit. also it happened again right now and when i plugged in the usb cable to my pc the amber charge light didnt come one, had to battery pull. ty
I just noticed that it happens when i hit the power button to unlock and the screen doesnt detect my finger. I lock it and tried to unlock and it happened. T.T
Sent from my PG86100 using XDA App
Hi there!
I have the following problem with my S3 (bualf1 austrian vodafone branding )
The screen stays on after the charger is plugged and the screen turns on after charging is complete!
I've done a factory reset and the problem has seemed to solved, but yesterday the problem has occured again!
I've really tried everything (every option, enabling / disabling everything, uninstalling apps, ...)
When shutting the phone down, the screen reacts as supposed (turns off while charging )
Any suggestion for me?
Sent from my GT-I9300 using xda app-developers app
No idea anyone?
Sent from my GT-I9300 using xda app-developers app
Check the developer options
Sent from my Galaxy Nexus
Already done, tested everything!
Sent from my GT-I9300 using xda app-developers app
sirtech said:
Already done, tested everything!
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
same problem as mine, occured only once. my workaround is by manually lock the phone (press power button). what kernel you use?
Are you absolutely sure this is not linked to a software you have installed?
There are certain titles that allow you to leave the screen on whilst being charged. Look carefully, it could be quite obscure.
As you said, it cleared when you did a Factory Reset but has now returned ~ thus indicating a recently installed App has resumed the screen on operation.
In reference to the phone coming on when fully charged, that is normal but the most likely reason it is not going back off again is due to whatever App setting you have that is then telling the phone once the screen is on keep it on.
bejoanakmami said:
same problem as mine, occured only once. my workaround is by manually lock the phone (press power button). what kernel you use?
Click to expand...
Click to collapse
Stock kernel, stock (austrian branded) firmware!
Manually locking works for me, but when den charging is finished the phone's display turns (and stays) on - that is my problem!
Beards said:
Are you absolutely sure this is not linked to a software you have installed?
There are certain titles that allow you to leave the screen on whilst being charged. Look carefully, it could be quite obscure.
As you said, it cleared when you did a Factory Reset but has now returned ~ thus indicating a recently installed App has resumed the screen on operation.
In reference to the phone coming on when fully charged, that is normal but the most likely reason it is not going back off again is due to whatever App setting you have that is then telling the phone once the screen is on keep it on.
Click to expand...
Click to collapse
Thats the same thinkings i have, but i didn't managed to find out, what app this could be...
the strange thing is, it works as intended when no power source is plugged (screen turns off after 30 seconds), it just doesn't turn off while charging
no idea anyone?
sirtech said:
no idea anyone?
Click to expand...
Click to collapse
I'm afraid without knowing which Apps you have installed it would be difficult to find the culprit.
If it were me I would do the following:-
1. Factory Reset again only this time do it from Recovery ~ [The recovery mode in Samsung Galaxy S III can be entered by pressing the Volume Up Key, Center button, and holding both simultaneously press the Power Button]
2. From the options provided select Wipe data/factory reset and also you need to select Wipe Cache partition and then reboot your device by selecting reboot system. You now have a completely cleared system so the next stage is important.....
3. Just install the settings, nothing more and certainly don't let Google Play reinstall your Apps.
4. Connect your power cable and see if once the S3 is charged the screen comes ON to notify you it is charged BUT THE SCREEN THEN TURNS OFF after a brief period. If it does then you at least will know under the basic setup your phone is fine. Now another slow but probably most important bit........
5. Start installing your Apps (say ten at a time) and then reboot your phone when all ten are installed and again start charging the phone.
At this stage we want to see what happens after charging is complete. If all is fine you then know what Apps are installed don't effect the screen ON problem, so continue installing another ten Apps and again reboot the phone and apply the charger to see if once charged the screen turns ON then OFF.
Continue repeating this procedure until you notice after a charge the screen this time does not turn OFF.
6. Right..... you now know the problem is being caused by one of the last ten Apps you installed. So, uninstall each App in turn (making sure you reboot each and every time you uninstall) and again recharge. This should eventually lead to one individual App that has caused the problem (the remaining Apps you uninstalled from the last ten can now be re-installed).
7. Investigate that App thoroughly to see if it alters anything on your phone that is causing the problem. Also name the App so we can look at it too.
It's a slow process granted but it's the only way you are going to find out what is causing the issue.
Basically, if it's happening from a fresh Factory Reset (via Recovery using the methods I mentioned above) then it's an issue directly with the phone.
If all is well then it's an issue with an individual App.
Good Hunting......
Same thing happened to me today and i never noticed it happen before..
Went to plug the phone in and the screen was on so i figured "Oh it will turn off after 15 seconds like usual" came back 5 minutes later still on.... uhh okay, so i hit the power button the screen went off.. I went to the restroom came back.. SCREEN BACK ON AGAIN? hmmm dubya tee eff? Turned it off again with the power button.. This time it stayed off..
Stock firmware latest upgraded 2 days after the 4th of the july.
Which firmware do you have?
Sent from my GT-I9300 using xda app-developers app
Well, that's what i've done:
1.) factory reset
2.) reinstall all settings and mailaccounts
3.) reboot and see if it still works
4.) install and configure 5 apps
5.) reboot and see if it still works
6.) repeat steps 4. und 5. as long as all apps are reinstalled and reconfigured
and so, finally the guilty app was found!
EXTENDED CONTROLS causes the problem, that the screen stays on when a charger is plugged!
Tested it on all 4 own mobiles, all of them are working as normal again!!!
THANKS BEARD!!!
Hello everyone! I scanned a few pages and search a bit but couldn't find my exact problem already listed;
When I plug in my USB cable to my laptop (Windows 7) the phone goes into 'installer mode' and sits there for about 10-15 seconds then switches to 'media device' mode. That's cool because I want it to be in media device mode normally, installer mode is useless. The problem is, if I open dev options and select USB Debugging mode, it only stays for 10-15 seconds then pops back into media device mode -- for the 10-15 seconds I can connect from my PC and start pushing my app over but then it fouls up when it comes out of dev mode.
My phone is rooted but I have very few apps on it yet, the only rooted app I have is a wifi tether app which I haven't used yet, and NoBloat which I used to disable some verizon crud. It will still flip out of usb debug mode even if I don't try to push any data to it... GRRR! I also have a problem where I can't sign into Samsung Account ("Samsung Account has stopped working")... but that's another story >=(
SonyUSA said:
Hello everyone! I scanned a few pages and search a bit but couldn't find my exact problem already listed;
When I plug in my USB cable to my laptop (Windows 7) the phone goes into 'installer mode' and sits there for about 10-15 seconds then switches to 'media device' mode. That's cool because I want it to be in media device mode normally, installer mode is useless. The problem is, if I open dev options and select USB Debugging mode, it only stays for 10-15 seconds then pops back into media device mode -- for the 10-15 seconds I can connect from my PC and start pushing my app over but then it fouls up when it comes out of dev mode.
My phone is rooted but I have very few apps on it yet, the only rooted app I have is a wifi tether app which I haven't used yet, and NoBloat which I used to disable some verizon crud. It will still flip out of usb debug mode even if I don't try to push any data to it... GRRR! I also have a problem where I can't sign into Samsung Account ("Samsung Account has stopped working")... but that's another story >=(
Click to expand...
Click to collapse
Sounds like your wonderful "Debloat" app uninstalled something you needed. That's why these apps are useless. One persons soultion isn't for everyone.
DarkMenace said:
Sounds like your wonderful "Debloat" app uninstalled something you needed. That's why these apps are useless. One persons soultion isn't for everyone.
Click to expand...
Click to collapse
As a matter of fact, I completely re enabled everything I had frozen before posting and it still doesn't work.could it be a flaw in the root process?
To be clear, I never "un-installed" anything with NoBloat, I only "Disabled" or froze some apps (mostly amazon and the verizon nfl center, nothing system-wise).
SonyUSA said:
As a matter of fact, I completely re enabled everything I had frozen before posting and it still doesn't work.could it be a flaw in the root process?
To be clear, I never "un-installed" anything with NoBloat, I only "Disabled" or froze some apps (mostly amazon and the verizon nfl center, nothing system-wise).
Click to expand...
Click to collapse
Well if you want to do a system restore send me a PM and I'll give you instructions to do so. I'll only be up for about another hour or so.
DarkMenace said:
Well if you want to do a system restore send me a PM and I'll give you instructions to do so. I'll only be up for about another hour or so.
Click to expand...
Click to collapse
For those waiting with bated breath, a full restore did not help the issue of it not staying in USB Debug mode. In fact, a total reflash of the stock ROM and kernel still had the exact same problem, which I re-created right after I performed the initial setup... so this bug exists in the normal stock ROM it seems...
SonyUSA said:
For those waiting with bated breath, a full restore did not help the issue of it not staying in USB Debug mode. In fact, a total reflash of the stock ROM and kernel still had the exact same problem, which I re-created right after I performed the initial setup... so this bug exists in the normal stock ROM it seems...
Click to expand...
Click to collapse
Your phone might be defective if it never worked from the day you got it. If that's the case you should go to Verizon.
Sent from my Rooted Verizon Samsung Galaxy S4 using xda premium
Nah, I'm almost 100% it's just a software problem because if I uncheck Debug mode then check it again, I can use the phone in dev mode for like 15-20 seconds and everything works perfectly... I can push my APK to test and it works great, but after it flips back to media mode it just kind of dies...
Edit: Can you plug your phone into your PC and tell me what mode it starts in, then wait 20 seconds and see if it changes modes? My phone immediately goes into "Installer Mode" then 20 seconds later changes to Media Mode (MTP). Maybe it's a problem with the drivers I have installed causing the phone to flip out of dev mode...
SonyUSA said:
Nah, I'm almost 100% it's just a software problem because if I uncheck Debug mode then check it again, I can use the phone in dev mode for like 15-20 seconds and everything works perfectly... I can push my APK to test and it works great, but after it flips back to media mode it just kind of dies...
Click to expand...
Click to collapse
Might try contacting Verizonnthen n havimg them connect you to Samsung if they can't fix the issue.
Sent from my Rooted Verizon Samsung Galaxy S4 using xda premium
The chumps at Verizon don't know how to do anything besides make phone calls and Samsung support is always closed by the time I get home...
Figured it out! Went into device manager and updated the "CDC Serial" with the driver from the Kies application from Samsung website, that cleared it up!
SonyUSA said:
The chumps at Verizon don't know how to do anything besides make phone calls and Samsung support is always closed by the time I get home...
Figured it out! Went into device manager and updated the "CDC Serial" with the driver from the Kies application from Samsung website, that cleared it up!
Click to expand...
Click to collapse
Good now if you ever need to restore you'll be fine with the USB debugging.
Sent from my Rooted Verizon Samsung Galaxy S4 using xda premium
Hi guys, hoping for some SuperUser help...
Using the GPS Time application to try and get my Omate TrueSmart to update the time after the battery dies (I can't believe the device can't hold enough power to maintain its internal clock, that's a terrible design flaw in a watch, but anyway)
The problem is that the GPS Time app pops up the SuperUser dialogue asking me to give it permissions--but the dialogue is too big for the screen and there's no OK button visible! How do you handle this on the TrueSmart?
metaphor_ said:
Hi guys, hoping for some SuperUser help...
Using the GPS Time application to try and get my Omate TrueSmart to update the time after the battery dies (I can't believe the device can't hold enough power to maintain its internal clock, that's a terrible design flaw in a watch, but anyway)
The problem is that the GPS Time app pops up the SuperUser dialogue asking me to give it permissions--but the dialogue is too big for the screen and there's no OK button visible! How do you handle this on the TrueSmart?
Click to expand...
Click to collapse
I use xposed for apps that spill over the edges. Start here...then move to xda
repo.xposed.info/module/de.robv.android.xposed.mods.appsettings
Sent from my HTC One using Tapatalk
Set Device Settings -> Display -> Font Size to Small and the SuperSU screen will fit on screen
fg said:
Set Device Settings -> Display -> Font Size to Small and the SuperSU screen will fit on screen
Click to expand...
Click to collapse
Thanks to both of you!
Open SuperSU and look on the first tab 'Application', Touch the #
Change 'Acces' to Allow
then save
False move on SU, now TS won't complete booting
I have a TrueSmart 1/8, US version, developers edition, with most up to date rom and with Loki's patch.
I wish I had read this thread a few minutes sooner. I was trying to install the gestures app GMD gestures I think it was and kept running into the same superuser problem. So went into settings for superuser and hit yes to have it installed I think in the system. I can't really tell you now because I can't get back into the watch at all.. I know it said to reboot immediately after and that if SU did not show up to go to the Google play store to reinstall or to open it from there or something...I'm not sure what. In any event, after SU did its thing, I powered off and on powering back on, it will not get past the Omate TrueSmart screen. Nor can I turn it off. Can anybody help me? For now I have it in the cradle so it doesn't lose power, since I cannot turn it off.
I know I can take the battery out, but I wanted to consult before I do anything more.
Tom19146 said:
... I powered off and on powering back on, it will not get past the Omate TrueSmart screen. Nor can I turn it off. Can anybody help me? For now I have it in the cradle so it doesn't lose power, since I cannot turn it off.
I know I can take the battery out, but I wanted to consult before I do anything more.
Click to expand...
Click to collapse
If you had ADB enabled, try plugging into your computer and see if you can launch an adb shell which will give you more restoration options. You may be able to undo your changes from the command line, or at the least reboot into recovery mode.
Without ADB, your options are to pull the battery or wait till it drains naturally.
fg said:
If you had ADB enabled, try plugging into your computer and see if you can launch an adb shell which will give you more restoration options. You may be able to undo your changes from the command line, or at the least reboot into recovery mode.
Without ADB, your options are to pull the battery or wait till it drains naturally.
Click to expand...
Click to collapse
What program should I have open on my PC before connecting watch (or is that a sensible question)?
New patch coming out this weekend to address that.
Tom19146 said:
What program should I have open on my PC before connecting watch (or is that a sensible question)?
Click to expand...
Click to collapse
Just a follow-up to the above, in case anyone lands in the same place, I did take the back off, remove the battery for just a moment, and then put the back back on. (I doubted, since it was frozen, that connecting to my PC would help, so i didn't try that. ) To my delight, everything was as I had left it, save that the gestures GMD app now loaded. (I made my font small, as recommended above, and was able to ok super user this time.) I had expected after removing the battery, to have to rebuild/reload everything from scratch,but that didn't happen.
Thanks to all for your help.
Ive got a note 8 that just died on me today. The screen remains blank no matter what I do. When I plug into any charger, it sends out random short vibrations usually every few seconds. Ive tried rebooting, force rebooting, recovery booting, nothing lights up the screen. No combination of volume and power keys accomplish anything. The battery had around 40% when it went out. Please help me recover this thing! Ive replaced the battery and LCD on it once. I really don't want to just throw random parts at it hoping for a fix. Yes Ive checked every connection to be secure. I am thoroughly stumped.
Skytex said:
Ive got a note 8 that just died on me today. The screen remains blank no matter what I do. When I plug into any charger, it sends out random short vibrations usually every few seconds. Ive tried rebooting, force rebooting, recovery booting, nothing lights up the screen. No combination of volume and power keys accomplish anything. The battery had around 40% when it went out. Please help me recover this thing! Ive replaced the battery and LCD on it once. I really don't want to just throw random parts at it hoping for a fix. Yes Ive checked every connection to be secure. I am thoroughly stumped.
Click to expand...
Click to collapse
Connect the phone to the PC and then open a command prompt window where you installed ADB and run adb in the command prompt window and when it opens then type adb shell reboot recovery and see if it reboots to recovery mode but it requires that you have USB debugging enabled in developer options and if it's not enabled then there's nothing else you can do.
Its totally stock. Never installed adb on this phone
Skytex said:
Its totally stock. Never installed adb on this phone
Click to expand...
Click to collapse
Adb is "installed" on your computer, not phone. Adb/fastboot commands are delivered to the device.
https://developer.android.com/studio/releases/platform-tools