Heya guys,
Just unboxed my N5 and went through the rigmarole of turning it on etc.
For some reason, it didn't want me to log in with my account details before showing me the home screen (not sure why).
So it didn't give me the option of downloading all my apps from my Galaxy Nexus (I know, 2 year old phone).
So, I wanted to test out the vibration on it from a phone call, and instead of mucking about, I thought I'd check out the ADM and lock/ring the device.
To my pleasure the device showed up in the ADM: https://www.google.com/android/devicemanager - but the location wasn't being found.
I have followed the troubleshooting page: https://support.google.com/accounts/answer/3265955?p=android_device_manager&rd=1#
So I've cleared out the google play services several times, restarted the phone several times - all to no avail.
My galaxy nexus is reporting correctly (when I connect it to a network - I have temporarily disconnected it thinking that it may have caused an issue).
Does anyone have any additional ideas?
Is this a common N5 issue or is everyone else working just fine?
--
P1
Hello dear forum,
something weird happened to my One S 2 days ago and I would need your help, since I am, not very smartphone-savvy. I will try to describe the problem as detailed as possible.
It is important to mention, that since a few months the phone's USB connection didn't work properly (I can charge the phone on the PC, but it won't be recognised as a device by the PC). Also the phone doesn't seem to have an SC card?? I never really noticed this, but now it puts an obstacle in my way cause there is no easy way to recover my gallery etc.
While I was manually updating my apps (at the time of the happening: WhatsApp and Skype), I suddenly got the popup message "Google Play store stopped working". I wiped recent apps and started the play store again. Suddenly, various apps (Google Drive, Gmail, Play Store, Clean Master, you name it..) all stopped working and I got a huge amount of these "stopped working"- popup messages, including "android.process.acore has stopped working".
It was impossible to get rid of the messages, because they kept appearing over and over again on the screen.
I tried to restart the phone, which didnt fix the problem. It seemed like my apps just kept crashing over and over. I rebooted again after a while and everything seemed fine. My data was also still there and wifi worked too.
But then the phone froze. I tried restarting it via the hardware button. Since then, the phone seems dead. It only starts when connected tot he charger, but always keeps freezing at the "HTC One S" startup screen.
Now I mentioned the USB connection was not working properly even before this happened. I still tried plugging the phone into the PC, and it seemed to be searching for drivers for a certain "QHSUSB_DLOAD".
I have no idea what this means and would like to ask you for suggestions on what to do (or if there is anything I could do at all). I don't have much hope, but the best case scenario for me at this moment would be to have my photos recovered.
Thank you VERY much for your suggestions, it will be hugely appreciated!
narvicloud
When I woke up today to get ready for work, my rooted Z740g was on the beginning tutorial for setting up the phone. While I was asleep the phone reset itself and erased everything I had on the phone storage. When I tried setting up the phone to see what was going on, the default keyboard app was not there! I had to use google voice to download a keyboard app from a website other than the google play store. No one had physical access to my phone and I had no other device sign ins on my google account history. I didn't grant any strange programs super user permission except for android lost. I didn't see any logs in androidlost and it uses my google account to sign in and I wasn't seeing any strange devices on that log. Do you think that this is some strange fluke or some type of malicious attack? My internal storage was almost full and occasionally my phone would reboot on its own and had various small bugs like battery monitoring being inaccurate on occasion. I'm worried about security breaches on my phone because I have seen how easy it is for someone to access the microphone, camera and any files on the device. I removed my sim and had to change all my online passwords.
Would flashing a rom completely remove any malware that might be on the device?
edit: I just noticed that there were two versions of chrome on my phone when I was trying to figure out what happened earlier today. I did notice that chrome looked different. I see a version 39 from before the wipe occurred and now I have version 28.0.1500.94 I looked up release dates and version 28 was released in 2013 and the phone wasn't even released until sometime in 2014. What gives?
foolioGrimz said:
When I woke up today to get ready for work, my rooted Z740g was on the beginning tutorial for setting up the phone. While I was asleep the phone reset itself and erased everything I had on the phone storage. When I tried setting up the phone to see what was going on, the default keyboard app was not there! I had to use google voice to download a keyboard app from a website other than the google play store. No one had physical access to my phone and I had no other device sign ins on my google account history. I didn't grant any strange programs super user permission except for android lost. I didn't see any logs in androidlost and it uses my google account to sign in and I wasn't seeing any strange devices on that log. Do you think that this is some strange fluke or some type of malicious attack? My internal storage was almost full and occasionally my phone would reboot on its own and had various small bugs like battery monitoring being inaccurate on occasion. I'm worried about security breaches on my phone because I have seen how easy it is for someone to access the microphone, camera and any files on the device. I removed my sim and had to change all my online passwords.
Would flashing a rom completely remove any malware that might be on the device?
edit: I just noticed that there were two versions of chrome on my phone when I was trying to figure out what happened earlier today. I did notice that chrome looked different. I see a version 39 from before the wipe occurred and now I have version 28.0.1500.94 I looked up release dates and version 28 was released in 2013 and the phone wasn't even released until sometime in 2014. What gives?
Click to expand...
Click to collapse
Hi, thank you for using XDA assist.
There is a general forum for android here*http://forum.xda-developers.com/android/help*where you can get better help and support if you try to ask over there.*
Good luck.
Just thought I'd throw this out there. It took me about 4 days to figure out and resolve this and couldn't figure it out. Here's what I'm running
Phone: Pixel 2
Build number: OPM1.171019.019
Magisk: v16.0
TWRP: 3.2.1-0
Android Auto: 3.0.5705
Whenever I would open AA, AA worked fine with exception to the 'Microphone' option. I validated all permissions were properly set and that I allowed AA to use voice as well as enabling 'Ok Google' but it still continued to crash with the message "Voice Commands Aren't Working Yet" . I happened to be looking for crash logs and looked at the 'tombstone' files in '/data/tombstones/' and found the following line:
Code:
/dev/ashmem/dalvik-classes.dex extracted in memory from /data/app/com.google.android.googlequicksearchbox-myLQ80LPFOqvrolYhMKlDA==/base.apk (deleted)
I wiped Dalvik/ART Cache although I didn't think this would fix it... I don't know if this had to do with that crash since there wasn't a timestamp or reference to AA but thought it was peculiar. It looks like the 'google quicksearch box' is part of the 'Google' app in Google Play. I uninstalled the 'Google' app, then re-installed (updated) it. Then opened it and went through the 3 quick steps to set it up. After doing so, I opened AA and the issue was fixed...
I hope this helps someone.
Did the issue stay fixed for you? I did the same thing (uninstalled, then reinstalled Google app updates) but the issue returned within 20 mins or so. What's extra weird is that two of my devices (Pixel XL and Nexus 6P) with the same Google account are having the same problem in the last few days, but a friend's device (Pixel XL) doesn't when used with the same radio.
Well I just checked after reading your response and something reverted/no longer working. I know it did work for a while because I played with it and used Google Assistant in AA but now it's crashing again like you've said... I guess it's not worth keeping with this process for it to only work for a few minutes... I'll have to continue looking...
I've had the versions (that I put in my first post) working together for a few weeks (with exception to AA 3.0.5705) now but I swear this issue of AA not properly working has only recently cropped up this week in the 3.0 version -- which I think has only been out for a week.
I tried rolling back to AA 2.9.XXXX and it's still not properly working so I don't have a plan at this point.
I may be speaking too early @MaSt3rGrIfF01 but it's been working 5 hours and has survived several test shutdown/reboots without AA flaking. Here's what I did on this round:
-Uninstalled Android Auto
-Removed all Magisk Modules (only left Tethering Enabler)
-Android O APT-X Libraries
-Busybox
-RAM Management
-Sysconfig Patcher
-Systemless TZData -Rebooted Phone
-Went to 'Google' app settings, performing 'Clear All Data' and 'Clear Cache'
-Uninstalled 'Google' app
-Re-installed 'Google' app
-Configured 'Google' app
-Updated 'Google' app
-Sideloaded 'Android Auto' APK version 2.9.5749
-Rebooted Phone
.... Since then, I haven't experienced a crash
...and by 7PM last night, while not touching the phone at all since my last update here, I picked it up to check and it was busted again... Back at square one.
That's been my same experience so far; Erasing all data in the Google app will immediately resolve the issue, only for it to return soon after without me changing anything. Another thing I've noticed is that once the issue rerurns, I will periodically notice alerts saying the Google app has become unresponsive or suddenly closed.
I also tried wiping my Pixel XL and used a different Google account on it. I was unable to get the issue to reproduce on the same device when using this second Google Account. At this point, it seems like there's an issue somewhere in my Google Account, rather than in the device itself. So far I'm stumped, to say the least.
That's strange that a Google account would be the result of that behavior. Nonetheless, I will give that a try. I have two Google accounts tied to my phone so I removed one and re-did my previous steps. I will give it a few hours (hopefully days) before I confirm if this might be the solve.
One thing I noticed is that immediately after wiping my phone and updating the Google app, if I look in the settings for Google Assistant I'll see that it's missing options for music (and a few other things that I don't remember right now). I cannot get the issue to reproduce in this state. If I either erase the data in the Google app or use the phone normally for a period of time (between 6 to 30 or so hours), the missing options will return. As soon as those options are back, the issue starts back up. After that, if I wipe the Google app again, it will work normally immediately but the issue will return within 20 mins or so. This issue just keeps getting stranger.
How's everything going for you so far with the other Google account?
Well I had a primary Google account that I've been using for like 8 years. Then I have another which I made this year. I had both tied to my phone. However, I removed the newer one from my phone -- all traces of it gone -- then repeated the steps from earlier.
AA worked for almost the whole day without that crashing issue. Then I started having it's normal trouble. I'm in the same place you are. We can't be the only other people experiencing this... It does make me feel slightly better that it's happening to you on a different model phone which tells me this isn't just a Pixel 2 issue.
.... but yea, still not solved on my end...
Agreed, it's really strange that I can't find anyone else online complaining about the same issues. I'll keep in touch in case I find out anything else useful.
---------- Post added at 06:11 PM ---------- Previous post was at 06:09 PM ----------
I did find this http://piunikaweb.com/2018/03/06/android-auto-voice-commands-arent-available/ and https://productforums.google.com/forum/#!msg/android-auto/GwDHrjlL3mk/Kylyw15MBgAJ
---------- Post added at 06:30 PM ---------- Previous post was at 06:11 PM ----------
After reading through that thread, it looks like the way to resolve the issue is by installing a new version of the Google App (7.22.24.21). I've never been prompted to update to it, but you can find the APK online https://www.apkmirror.com/apk/google-inc/google-search/google-search-7-22-24-release/. So far so good, I'll let you know if the issue returns.
Nice find! And agreed. I just updated Google app via the apk and the issue wasn't happening again. Didn't even have to uninstall/reinstall/clear cache
I don't know where to post this, so I'll start here.
After I took the Oreo 8.0 update on my phone (SM-955U) S8+ in layman's terms..lol, both my wife's phone and mine are not staying unlocked with Smart Lock. We use this feature when we are in our trusted place (Home).It works when it's connected to a trusted device (Car Bluetooth) I wiped my phone and did a factory reset and started from scratch to rule out software or settings. I would have to constantly (many times a day) turn off then back on my trusted place. I sometimes even delete it and re do it. I have gone into my google account and made sure my Home was in my profile. The one thing I did notice is, once in a while, I have gone into settings > apps > Google Search and cleared Cache and Delete All Data, then uninstalled Google update's and restarted my phone. Then it would work for a while, then it wouldn't again.
I'm at a loss as to what is causing this. I'm not sure if it's an OS (firmware) but or something else all together. I don't know if the Google search is a coincidence or its the actual issue.
Anyone else having this similar issue or found the fix?
It has been happening to me. It actually started right before I got the Oreo update.
Interesting, I don't remember if it started before the update or not. I was having an issue updating to begin with. So I was constantly resetting my phone.
Same here. Also started before the Oreo update...around the time of the Feb security patch. Mine works when I get home consistantly until I dont use the phone for a while. At that point I have to use the fingerprint reader or pattern to unlock every time. Very annoying.