Related
The only thing I have done to this phone is root.
My phone several times today has had it's screen blacked out and cannot be awoken or used because all buttons on the phone become unresponsive. However, I know the phone is still working because it still receives notifications and I can hear it.
I have to take out the battery to fix this. Has happened about 5 times today.
Anyone else with this issue?
That certainly isn't normal. I would return it.
Also noticed that when using adb that it kicks my phone out after a certain time... something like 1 minute. Does this happen to anyone else?
I often have to do adb kill-server in order to see my device again.
I too have the same problem (though less frequently).
I have a rooted Epic using Joey Krim's method (raidagainstthecage-arm5.bin). I attributed it to the Overclock Widget which I have uninstalled to see if it gets any better. I like that widget for throttling down the CPU while the screen is off.
I guess it is best to start collecting data on this.
Phone was purchased at BestBuy.
Hardware version: D700.0.5
Anyone else seeing similar behavior? How about on a non-rooted Epic?
I was running SetCPU but uninstall the application and it was still happening to me. I have a feeling it has to do with the root method. My girlfriend's phone doesn't have root and it hasn't happened to her at all.
@jspielberg did you root via the one click method or manually with adb?
I rooted via adb.
Other root required apps installed:
Titanium Backup
Wireless-Tether Experimental (adhoc mode only working currently on the Epic it looks like)
Overclock Widget (now removed)
I think that is it for SU needed apps.
jspielburg did you use OS X by any chance to do your root? Couldn't get this thing to connect on windows so used my mac to root.
This happened to me not 30 minutes ago. And I'm 100% sure its root.
Sent from my SPH-D700 using XDA App
volcomjerk said:
jspielburg did you use OS X by any chance to do your root? Couldn't get this thing to connect on windows so used my mac to root.
Click to expand...
Click to collapse
I did indeed use my mac also for root via ADB...
I can't see how that would matter, but it is good data nonetheless.
Very odd. I have not had a single issue with a blackout, or unresponsive buttons after I rooted 11am yesturday. Then again, I removed most of the sprint bloatware, and removed more useless crap from startup. All the rooted app's are working as expected.
antidelldude said:
Very odd. I have not had a single issue with a blackout, or unresponsive buttons after I rooted 11am yesturday. Then again, I removed most of the sprint bloatware, and removed more useless crap from startup. All the rooted app's are working as expected.
Click to expand...
Click to collapse
Yeah everything is working fine. But I went to pick up the phone to make a call and it was dead. Complete blackout screen, not lights. Nothing.
@Fixter that happened to me too.
Everyone having this problem please state how you rooted. I have a feeling the EPIC doesn't like being on ADB through OS X or 64-bit OS's apparently.
I rooted Tuesday morning using Windows 7 32 bit mode, ran cmd as Administrator and followed Joeykrim's manual instructions.
I have had no problems with the screen being able to be turned back on and I have been on my phone performing various tasks for hours at a time.
volcomjerk said:
@Fixter that happened to me too.
Everyone having this problem please state how you rooted. I have a feeling the EPIC doesn't like being on ADB through OS X or 64-bit OS's apparently.
Click to expand...
Click to collapse
I rooted via ADB on 64-bit Ubuntu using joeykrim's method, not a single issue.
Sent from my SPH-D700 using XDA App
ImSoHungry said:
I rooted via ADB on 64-bit Ubuntu using joeykrim's method, not a single issue.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I rooted with One Click Root. Windows 7 32bit.
I rooted using quick root on Windows 7 then did a full reset after I started having problems and still am having problems with the screen not turning on unless I pull out the battery
Is there a way to undo the "one click root" I did from the instructions here on XDA yesterday?
I rooted last night via OSX 64bit and have not experienced this issue. But now i am very afraid...
killahkosha said:
I rooted using quick root on Windows 7 then did a full reset after I started having problems and still am having problems with the screen not turning on unless I pull out the battery
Click to expand...
Click to collapse
Wow, after doing a full reset without root I am not seeing problems yet but this post makes me worried that it's not just related to root or unrelated to root at all.
I did a full reset through the menu on the phone, I haven't tried doing one through the holding volume down while booting method but I will after work
I'm new to android wear but not to android.
Just received the wear24 (love it so far)
I am on metro with an lg g5 7.1 nougat and watch is 7.1.1 android 2.0 android wear app 2.8
I can't figure out how to make and receive calls. How to answer texts and the messenger app keeps telling me to install messenger on my phone and sending me to the play store messenger download which says open because it is already installed.
Any insight or help would be great this watch is now cheap and flying off of the shelves so I figured this could be a good thread.
Basically what to do when you first get the wear24 and how to use it without Verizon.
Thanks
adambomb_13 said:
I'm new to android wear but not to android.
Just received the wear24 (love it so far)
I am on metro with an lg g5 7.1 nougat and watch is 7.1.1 android 2.0 android wear app 2.8
I can't figure out how to make and receive calls. How to answer texts and the messenger app keeps telling me to install messenger on my phone and sending me to the play store messenger download which says open because it is already installed.
Any insight or help would be great this watch is now cheap and flying off of the shelves so I figured this could be a good thread.
Basically what to do when you first get the wear24 and how to use it without Verizon.
Thanks
Click to expand...
Click to collapse
There was a thread on Reddit regarding FB messenger. As of a couple days ago, the current beta version of FB messenger for the phone fixed the 'need to install' issue.
So... I'm in a pickle.
My Wear 24 lost connection with my phone, and wouldn't reconnect. I disconnected and reset the watch, and when I went back to reconnect to my phone, the check mark and x won't appear when the pin pops up.
I've tried clear my Wear os app data and restarting my phone, and shutting down and resetting my watch multiple times, no dice.
I attached a pic for reference.
https://imgur.com/a/DUGugRR
rdeets said:
So... I'm in a pickle.
My Wear 24 lost connection with my phone, and wouldn't reconnect. I disconnected and reset the watch, and when I went back to reconnect to my phone, the check mark and x won't appear when the pin pops up.
I've tried clear my Wear os app data and restarting my phone, and shutting down and resetting my watch multiple times, no dice.
I attached a pic for reference.
https://imgur.com/a/DUGugRR
Click to expand...
Click to collapse
You have to go to the wear app and disconnect the watch from there. When try to repair via the wear app again. You only need to click yes to the PIN prompt on the phone. Not the watch
c_86 said:
You have to go to the wear app and disconnect the watch from there. When try to repair via the wear app again. You only need to click yes to the PIN prompt on the phone. Not the watch
Click to expand...
Click to collapse
I have disconnected the watch from the app. It shows me the new watch setup screen. That's what brings me to the watch pin.
Disregard. LG Package Disabler Pro was the culprit.
rdeets said:
Disregard. LG Package Disabler Pro was the culprit.
Click to expand...
Click to collapse
Glad you got it
c_86 said:
Glad you got it
Click to expand...
Click to collapse
Thanks. I was a little pissed when I realized what happened. Getting tired of using an unrooted device.
rdeets said:
Thanks. I was a little pissed when I realized what happened. Getting tired of using an unrooted device.
Click to expand...
Click to collapse
Agreed. I just wish there was a way to root my lg watch sport.
c_86 said:
Agreed. I just wish there was a way to root my lg watch sport.
Click to expand...
Click to collapse
Try flashing it with a Huawei unlock file? Half joking, but it actually worked for a V30.
I'm able to initiate calls from the watch, can hear them through the watch speakers, but the person I'm calling cannot hear me. Other voice commands to the watch work, so I know the mic works.
I've removed the VZ settings from the watch, and am using Bluetooth calling options via my Sprint phone.
Any ideas to fix the lack of sound from me during calls would be appreciated.
I wasn't sure where to put this but this seems appropriate - I've had a lot of issue with logging my google account. i tried wiping/deleting the account off my phone and everything. the only thing that worked was turning off my mobile data and trying with just a wifi connection through bluetooth.
My watch is now on 2.12 after doing system upgrade...I keep reading about people being on 2.7 or 2.8....Why does my watch say it is up to date?
Note that the Wear OS version and the Wear OS APP versions are completely separate. 2.7 and 2.8 refer to the app version. Still on your watch, but different from the OS itself.
I just got Wear24 several days ago from eBay for $50 and it already has problem. Since the very first moment of the first booting, it's lower half of the screen flashing/flickering white like crazy. It doesn't happen when it enters ambient mode. At first I thought it is the software issue, but after resetting and updating the watch to Wear OS 2.13, it still presents. I'm thinking of return it despite loving it.
Anyone having the same issue?
Hello,
I use to "OK Google" on my Nexus 5X and it worked even the screen's device was off. Assistant works fine but it seems it can't turn on me Redmi Note 7. Is it a "Nexus only" functionality ?
Thanks.
maybe, in the N7 the application itself tells you that it does not work with the phone locked with screen off
works for me in pixel experience rom for redmi note 7, i did have to set it back up for this lavendar device
Mine works perfectly though
It seems I had to activate "Voice Match" which I did. Actually this doesn't solve the problem.
I also use "Pixel Experience". Weird.
I haven't seen any phone waking up with screen off with Ok google except Nexus phone. Strange !
Could you please tell us @XeoNoX and @ahadrox what's your secret ?? rom & kernel you're using ? special setup ? additionnal mods ?
21vm said:
I haven't seen any phone waking up with screen off with Ok google except Nexus phone. Strange !
Could you please tell us @XeoNoX and @ahadrox what's your secret ?? rom & kernel you're using ? special setup ? additionnal mods ?
Click to expand...
Click to collapse
Mine is working fine, and I'm completely using my phone normally, no root, no twrp, bootloader locked. MIUI 10.3.9.0.PFGMIXM
there are 4 settings (maybe 5) you have to active, one somewhere in google now settings / assistant and another somewhere in system settings in the rom. and then u have to do the voice matching, and then the "always on display" or whatever they call it. Also make sure u have allowed all the correct permissions in the system settings such as microphone access, phone access, etc..
i assume u need the stock google apps or better installed as well unless you plan to manually install the packages. My phone unfortunately broke 2 weeks ago and i am awaiting a replacement part. Says it wont be here till November (international snail mail, im hoping it arrives faster), im currently using a really old phone in the meanwhile so i cant check.
I encounter a trouble on my HP laptop which is it always freezes after sleep mode. Even though the mouse and keyboard is working but still nothing response on laptop screen after sleep mode. What happening on this? Anyone got same problem with me?
Yes, i know this bug, but decided to ignore sleep mode for years on win 10.
Maybe you could tell, whats your exact model, and we find a way to fix it.
dumboyan said:
I encounter a trouble on my HP laptop which is it always freezes after sleep mode. Even though the mouse and keyboard is working but still nothing response on laptop screen after sleep mode. What happening on this? Anyone got same problem with me?
Click to expand...
Click to collapse
I had the same problem, the only thing that fixed it was a complete reinstall of windows. However, i found that it wont work if you do a fresh install from your own pc, download the latest version and install. I looked everywhere for a solution and this was the best bet, all other options gave me a blue screen of death.
Definitive solution:
1- open device manager
2- search for Intel Management Engine
3- Right click and choose Disable.
Congratulation! You can now SLEEP comfortably.
dkionline said:
Yes, i know this bug, but decided to ignore sleep mode for years on win 10.
Maybe you could tell, whats your exact model, and we find a way to fix it.
Click to expand...
Click to collapse
i too
it's really dizzy
dumboyan said:
I encounter a trouble on my HP laptop which is it always freezes after sleep mode. Even though the mouse and keyboard is working but still nothing response on laptop screen after sleep mode. What happening on this? Anyone got same problem with me?
Click to expand...
Click to collapse
thats why i dont use hp laptops anymore becuase i used to have a hp laptop for schooling and when ever i close the lid to put it to sleep it freezes so i got a acer laptop instead
Hi guys, I have replaced it with a new hard drive these days, and the freeze problem is already fixed. I recommend anyone to install SSD.
You can change your setting and Follow these steps to resolve this issue.
1- open device manager.
2- search for Intel Management Engine.
3- Right-click and choose Disable.
My Android Auto is stopped working when i manually update to 1.1.3
Anyone seeing the same issue? Is there a way to downgrade to 1.1.2?
Also, i had performed factory reset on 1.1.3 and it didn't helped, AA is still not working.
you shouldn't have done that
UserNamist said:
you shouldn't have done that
Click to expand...
Click to collapse
yes lesson learned in a hard way. so i need to downgrade to previous version or use my other phone since i rely heavily on AA...
ok problem solved. i need to manually go to phone usb setting and select file transfer. what a rookie mistake.
I still not updatedbecause it didn't appeared and I'm in 1.1.2 and Android auto doesn't work it shows black screen in my car and the phone says it's connected.
Gerard03 said:
I still not updatedbecause it didn't appeared and I'm in 1.1.2 and Android auto doesn't work it shows black screen in my car and the phone says it's connected.
Click to expand...
Click to collapse
It doesn't work on 1.1.2 for you?
panni said:
It doesn't work on 1.1.2 for you?
Click to expand...
Click to collapse
No it doesn't just black screen in the car and the phone says it's connected, also the first time I done it it showed the Android auto introduction screen on the phone, but the screen remains in black.
Gerard03 said:
No it doesn't just black screen in the car and the phone says it's connected, also the first time I done it it showed the Android auto introduction screen on the phone, but the screen remains in black.
Click to expand...
Click to collapse
have you checked your usb connection option when connected to AA? there should be an option for selecting either file transfer/AA, USB tethering, MIDI, PTP, and no data transfer (default selection).
advanxer said:
have you checked your usb connection option when connected to AA? there should be an option for selecting either file transfer/AA, USB tethering, MIDI, PTP, and no data transfer (default selection).
Click to expand...
Click to collapse
No but I will check. I didn't know you need to do that to use AA.
So this is not related to 1.1.3. Please stop picking this thread up in other threads and stop posts like "there are issues with 1.1.3 and Android auto". Thanks!
advanxer said:
My Android Auto is stopped working when i manually update to 1.1.3
Anyone seeing the same issue? Is there a way to downgrade to 1.1.2?
Also, i had performed factory reset on 1.1.3 and it didn't helped, AA is still not working.
Click to expand...
Click to collapse
Gerard03 said:
I still not updatedbecause it didn't appeared and I'm in 1.1.2 and Android auto doesn't work it shows black screen in my car and the phone says it's connected.
Click to expand...
Click to collapse
panni said:
It doesn't work on 1.1.2 for you?
Click to expand...
Click to collapse
This is not from the Nothing OS 1.1.3 update, but from the Android Auro update
The most common message users report seeing is "phone not compatible" when pairing their device via the Android Auto app. What happens on the car screen depends on the specific make and model, but it's usually an error message of some sort, with some user submissions shown below.
The issue appears to be Android version independent and related solely to the Android Auto 7.8.6 update.
Google representatives responded to the thread, asking for more details about the user reports, including Android Auto version number, smartphone model, car make/model and other relevant data. But for the past three days, Google has remained silent on the issue besides mentioning that the information has been passed on to the Android Auto team.
If you're having problems, downloading an earlier version of Android Auto may solve the problem, and you can also try signing up for the beta programme while you wait for a fix for the app.
Ok thanks I will try.
Gerard03 said:
Ok thanks I will try.
Click to expand...
Click to collapse
If you want, go to see this news from AndroidSage : https://www.androidsage.com/2022/08...8-0-6-beta-apk-with-new-features-coolwalk-ui/
I am not sure whether my previous issue was related to specific Nothing OS or AA version. But here's what i had observed:
In 1.1.2, i can simply plug in the AA usb cable to the Nothing phone (with locked screen) and AA will load automatically on the car HU.
In 1.1.3, that did not happened. After connecting the USB cable, AA will not load automatically. Instead, i will need to unlock my phone, go to USB Accessory setting and change either from "File transfer" to "No data transfer" or from "No data transfer" to "File transfer", then only AA will load on my HU. Since this setting is not permanent, i need to repeat this steps every single time i want to use AA.
Works perfectly fine here
Funny, i changed from S22 Ultra and now all troubles with Android Auto is gone, louder navigation and the 1-3 sec of silence every 5 mins when playing music is gone, OnePlus 8t Samsung s20 fe 5g and s22 Ultra all had the same issues, now i can finally enjoy music while driving!
Android-Desire said:
Funny, i changed from S22 Ultra and now all troubles with Android Auto is gone, louder navigation and the 1-3 sec of silence every 5 mins when playing music is gone, OnePlus 8t Samsung s20 fe 5g and s22 Ultra all had the same issues, now i can finally enjoy music while driving!
Click to expand...
Click to collapse
Doubt that's an hardware or phone issue.
It's an AA issue mostly. I haven't had any problems with my OP8T for example. On some phones i had issues but after clearing cache, force close and reinstalling AA it worked flawless.
P6P said:
Doubt that's an hardware or phone issue.
It's an AA issue mostly. I haven't had any problems with my OP8T for example. On some phones i had issues but after clearing cache, force close and reinstalling AA it worked flawless.
Click to expand...
Click to collapse
Wierd how there is no issue on this phone out of any phone i have used before.
Can we mark this thread as fixed?