Database Users

ADB is having serious issues...

I'm new, moving on.
I've been working on a game through Unity for the past couple of days, but the issue I keep running into is that any time I have to turn off/restart my computer or unplug my phone, I begin a small battle with ADB. At this point, ADB loses sight of the phone, even after I reconnect it. Only solution I've been able to find is to uninstall the Google USB driver, reinstall, kill ADB server, START ADB server, rinse and repeat a few times, and MAYBE it'll see it.
There really has to be an easier way to do this. I shouldn't have to battle a driver issue every time I sit down to work. If I do, I don't understand how some of you aren't completely suicidal from spending more time fighting a driver than actually developing whatever it is you develop..
Phone: Google/LG Nexus 5
OS: Windows 8.1

gradylorenzo said:
I'm new, moving on.
I've been working on a game through Unity for the past couple of days, but the issue I keep running into is that any time I have to turn off/restart my computer or unplug my phone, I begin a small battle with ADB. At this point, ADB loses sight of the phone, even after I reconnect it. Only solution I've been able to find is to uninstall the Google USB driver, reinstall, kill ADB server, START ADB server, rinse and repeat a few times, and MAYBE it'll see it.
There really has to be an easier way to do this. I shouldn't have to battle a driver issue every time I sit down to work. If I do, I don't understand how some of you aren't completely suicidal from spending more time fighting a driver than actually developing whatever it is you develop..
Phone: Google/LG Nexus 5
OS: Windows 8.1
Click to expand...
Click to collapse
windows 8.1 has problem many times, so I also have windows 7
adb is flawless in win7
saying from personal experience.

gradylorenzo said:
I don't understand how some of you aren't completely suicidal from spending more time fighting a driver than actually developing whatever it is you develop.
Click to expand...
Click to collapse
Use the emulator or just transfer the apk package to your phone. It takes 15 seconds.

I faced the same issues when connecting using a USB cable. ADB over network option in Developer tools is actually much more reliable provided that you have a Wifi connection on both your workstation and your device. You need to run a command to connect, but that's easily solved by writing a batch file. Try it out.

Multiple Wear watches with one phone problems!

Hello everyone.
Is there anyone here with multiple Wear watches (preferably with different Wear versions) paired to a single phone?
I am wondering it it is just me, or anyone else too, that have such problems with watches.
I suspect that since the Wear app v. 2.0 started rolling out, having multiple watches (with different OSs) paired to my phone just started an armageddon.
Before official 2.0, I had devprev on huawei and 1.5 on zw3 and Gwatch. I had ZERO issues, ever. Then, Wear app v. 2.0 update came and it slowly began:
Wear app is going haywire almost every week. I shot few videos, hopefully I will be able to throw them on youtube tonight to showcase what is happening. But basically: I choose a watch and connect it in wear app. App shows connected. I leave for work. At work I notice I dont get notifications. I check the app, and it shows one of few possible screens: trying to connect.. or "Have a watch? set it up" (that is the most hilarious for me ) Or shows a page that would normally show your chosen watch, but it is blank. Everytime I close and open Wear app, it can show something different. It can also be showing "Connected" for a long time, but nothing works. You cant see battery stats, change watchface, nothing...
The last time, I even lost all my paired watches in BT settings. Wear app says "reconnect", ok, it reconnects, but actually isnt connected. Well, I am not sure about that to be honest.. Smart lock works Sometimes, watch says connected too (in Settings-About) The most faulty watches are those with 2.0. But it happened to 1.4 and 1.5 too.
As of right now, only zenwatch3 on 1.5 is working, but, I did a FR yesterday because it wasnt working
I am really f**king fed up with resetting every god damn watch every god damn week so that it can work for a week and then god damn break again!
I am so glad I still keep my Sony SW2 as a backup, this watch works just AWESOME! Wear watches are still nowhere near the ease of usability and reliability of SW2.
EDIT: I uploaded videos of said behaving:

NOone with issues with multiple watches??

Yes, only 1.5 watches still, but I get best results with only one watch powered on at a time, and only one manually chosen to be connected via BT in the phone app. Otherwise, there are frequent connect/disconnect notifications, mysterious quick battery drain, and often conflict between what the phone app says is connected, and what the icons on the watch say about the connection. I occasionally get the "set up your watch" on the phone app as well. I just back out of it, and it's ok.

sirrelevant said:
Yes, only 1.5 watches still, but I get best results with only one watch powered on at a time, and only one manually chosen to be connected via BT in the phone app. Otherwise, there are frequent connect/disconnect notifications, mysterious quick battery drain, and often conflict between what the phone app says is connected, and what the icons on the watch say about the connection. I occasionally get the "set up your watch" on the phone app as well. I just back out of it, and it's ok.
Click to expand...
Click to collapse
Thanks, the symptoms are the same. But it is happening to me even when I have only one watch powered on and only one watch connected to phone. But, 7 watches total are paired. I am starting to think if it is something with BT 4.0 hardware limitations.

Google Play Store crashing on Wear24 - Possible Solution

I've seen this reported a few places (here and on Reddit) - I was experiencing the same issue, but somehow kind of backed into a solution... Hopefully the following can work for others.
As I said, I backed into this, so not sure which of the steps ultimately did it, but it appears to have boiled down to Google Play Services needing the update.
1) I first forced my watch to use its own wifi.
- Selected to "stop using carrier profile" (not delete) (in sim info)
- turned off Cellular and bluetooth in Connectivity (leaving only wifi), as well as turned off bluetooth on my phone (i think this helped with faster downloads on my watch)
- I also had the watch on the charger during this time, not sure if that matters.
2) Then I Updated Android Wear App on watch
- This had to happen pretty fast but i eventually got it
- Open play store, quickly swipe from top, select my apps, select "update"
- I had to do this a few times (because play store was of course crashing). But eventually Android Wear updated to 2.8
3) Then I updated Google Play Services
- Once Wear updated to 2.8, I was prompted with a notification of "Must update Google Play Services to use Android Wear". I clicked this a few times, but nothing seemed to be happening. Not sure if this would have eventually gone through on wifi or not... So I:
- Turned off Wifi on the watch
- Turned on bluetooth on both watch and phone (to pair them again)
- The next time i clicked the Google Play Services notification it started to download, then updated!
After Play services update was complete, i could then access Play Store with no issues!

I just had the same issue on my Huawei Watch 2, here is the post I made about how to resolve the issue:
https://forum.xda-developers.com/android-wear/help/how-to-fix-google-play-crashing-t3746732

Big Boy Laroux said:
I've seen this reported a few places (here and on Reddit) - I was experiencing the same issue, but somehow kind of backed into a solution... Hopefully the following can work for others.
As I said, I backed into this, so not sure which of the steps ultimately did it, but it appears to have boiled down to Google Play Services needing the update.
1) I first forced my watch to use its own wifi.
- Selected to "stop using carrier profile" (not delete) (in sim info)
- turned off Cellular and bluetooth in Connectivity (leaving only wifi), as well as turned off bluetooth on my phone (i think this helped with faster downloads on my watch)
- I also had the watch on the charger during this time, not sure if that matters.
2) Then I Updated Android Wear App on watch
- This had to happen pretty fast but i eventually got it
- Open play store, quickly swipe from top, select my apps, select "update"
- I had to do this a few times (because play store was of course crashing). But eventually Android Wear updated to 2.8
3) Then I updated Google Play Services
- Once Wear updated to 2.8, I was prompted with a notification of "Must update Google Play Services to use Android Wear". I clicked this a few times, but nothing seemed to be happening. Not sure if this would have eventually gone through on wifi or not... So I:
- Turned off Wifi on the watch
- Turned on bluetooth on both watch and phone (to pair them again)
- The next time i clicked the Google Play Services notification it started to download, then updated!
After Play services update was complete, i could then access Play Store with no issues!
Click to expand...
Click to collapse
I had followed these instructions when you posted it in another thread. I was able to update to android wear 2.8 and update google play services, yet, my play store was still crashing. Similar to steejo's above linked solution, I side loaded the newest version of the android wear play store. Going on 2 days now and haven't seen the issue come back.

Thank you very much steejo for describing how to solve this. Had this same issue as well with the Wear24 and using ADB over WiFi to install the Android Wear and the Google Play Services software got the crashes to finally stop.

This is absolutely ridiculous on Android's part. Pathetic actually. Why even continue releasing watches if you don't want fix bugs or even continue the development of Wear. Including pushing hardware manufacturing (2 year old snapdragon chip). Before finding these posts my experience with Android Wear the past 2 weeks was horrible.

v2.2v said:
This is absolutely ridiculous on Android's part. Pathetic actually. Why even continue releasing watches if you don't want fix bugs or even continue the development of Wear. Including pushing hardware manufacturing (2 year old snapdragon chip). Before finding these posts my experience with Android Wear the past 2 weeks was horrible.
Click to expand...
Click to collapse
Want to know something else ridiculous? I had to downgrade the native Phone application on my Pixel 2 back to stock because I noticed that when I received calls, the screen on my phone would go completely black and only my watch would buzz. I'm not sure that Google really gives a s*** about Android Wear users, wouldn't be surprised if they release a Pixel Watch and end support for all other Android Wear devices.

steejo said:
Want to know something else ridiculous? I had to downgrade the native Phone application on my Pixel 2 back to stock because I noticed that when I received calls, the screen on my phone would go completely black and only my watch would buzz. I'm not sure that Google really gives a s*** about Android Wear users, wouldn't be surprised if they release a Pixel Watch and end support for all other Android Wear devices.
Click to expand...
Click to collapse
Well I'm 100% a Pixel XL guy so I would love that lol

v2.2v said:
Well I'm 100% a Pixel XL guy so I would love that lol
Click to expand...
Click to collapse
Oh don't get me wrong, I'd love one too lol but I just got this watch and want it to last a bit, or at least obtain updates on it.

Ticwatch E - Unable to use Google voice search

I just got a Ticwatch E. It's fresh out of the box today using Android Wear 2 and all that (I gather it originally didn't support Android Wear, but it does now with the latest firmwares I guess.) One of the biggest reasons I finally updated to a modern smartwatch (my Pebble Time has served me very well and done just about everything I ever wanted except just a few things) was to be able to use the Google Assistant for (mostly) hands-free operations like getting directions while driving and etc without having to pull out the phone, unlock it, etc etc. (Especially since I prefer that my phone stays in my pocket when I don't need to do anything complex and at all times while driving.) I setup a bunch of stuff but just found out I have a huge problem in that this is the one thing I needed that absolutely does not seem to work.
Whenever I attempt to actually use the assistant by either holding the power button a moment or "ok google" (which I want to keep off to save battery life, but I turned on to test this) it just pops up a blank screen with a picture of a circle with an arrow (basically a refresh symbol which seems to be used to say "loading" a lot on Android Wear.) I've tapped around, tried sliding from each direction (of course left to right just backs out, but I tried the other three too,) waited a long time, and tried unlocking the phone after a quick google search. I have no clue what if any apps other than Android Wear need to be installed, but I did install the Google Assistant and already had the actual Google app itself installed. (I'd rather have only whatever is necessary, but for now I'm kind of trying to throw everything at it.) I also have the Ticwatch app itself installed even though I don't need or want the fitness tracking stuff.

[RESOLVED] Help track down new USB Host (Audio) issue

I'm stuck with a recent development on my NST and am not sure what to look at next.
I've been using USB Host Audio for a long time. For the most part I use it regularly once each week to stream NPR on Sunday mornings via the TuneIn radio app. It's been working really well for a long time via the typical external USB audio attachment.
Recently the NST spontaneously (soft) reboots during the program, returning to the marching dots and then the home screen. This generally happens about 30-45 minutes into play. After the reboot Wi-Fi is still connected and USB Host mode (incl. audio) is still active. All I have to do is restart the TuneIn app and off I go again.
I always fully charge the NST the night before so it's not a power issue. I have made other changes to the system since enabling USB Host but I do have a few old backups and went back to one a few weeks ago to see if something I did messed up somehow, but even with a configuration that pre-dates the start of the issue, I still get the reboot.
This morning I tried a hardware swap, using a different USB Audio attachment. Same behavior.
I finally took a look at the logcat from this morning but it appears to have wiped out everything from before the reboot. I only see my restart of the TuneIn app, etc.
I have not tried:
1. a new OTG cable (I have one)
2. a different audio app for an extended play time
Those are on my to-do list. I suppose it's possible that there is a hardware issue with my NST, but there is no way for me to determine that.
Does anyone have any suggestions for running down this problem?

If it fails that reliably, pipe adb logcat into a file and see what happens.
Code:
C:\>adb logcat>log.txt

Renate NST said:
If it fails that reliably, pipe adb logcat into a file and see what happens.
Code:
C:\>adb logcat>log.txt
Click to expand...
Click to collapse
Before or after the event?

Start the logging first, it will genereate a ton of text.
Then start your app.
When it blows up, stop the log and look for interesting stuff at the end of the really big log.

remove all traces of an app?
Renate NST said:
Start the logging first, it will genereate a ton of text.
Then start your app.
When it blows up, stop the log and look for interesting stuff at the end of the really big log.
Click to expand...
Click to collapse
Maybe not necessary, but there is an oddity I have found. I tried running Pandora for several hours and had no trouble with that app.
Today I tried TuneIn Radio again but this time I searched for the station I generally listen to when I get a spontaneous reboot and then let that play, rather than selecting the favorite. That also worked fine for several hours. It's a longish story, but I decided I would delete the old favorite and save a "new" one. I could not do it. I also could not delete another favorite, nor could I add a new one.
That led me to look at the app data. To my surprise I could not find any kind of file where the "favorite" data was saved (it's not online, as there is no login for the free version of TuneIn Radio). I don't know how I ever managed to get the two original favorites saved! This is the same app version I run on all my devices and it works fine on them.
So....I uninstalled the app, checked to make sure the data/data/... folder was gone, deleted the dalvik-cache entry for the app, restarted the NST, and installed a fresh copy of the app.
My old favorites were still there (again, it can't be from and online database somewhere--can it, without a login?). Where could this information be hiding? I checked the Android folder on the SD card and there is no entry there.
Clearly, for now, I will try searching for the station on Sunday morning, rather than playing from the "favorite" bookmark and
see if I get a good result as I did today.

Renate NST said:
Start the logging first, it will genereate a ton of text.
Then start your app.
When it blows up, stop the log and look for interesting stuff at the end of the really big log.
Click to expand...
Click to collapse
Indeed. I ran various audio apps for hours on end and never saw the issue so then I started down the road to thinking there was something up with the TuneIn app. Finally eliminated that and then got to wondering about this 1.2.2 update a few people have mentioned.
So...I ran the TuneIn app each morning for a few hours as I would normally do only on Sunday morning. Never had a problem until Saturday morning (last week) when the device rebooted. The next day (Sunday) it was fine. Ha! I thought I had fooled it into rescheduling on Saturdays.
Then I spent this past week repeating the experiment with my laptop running ADB wirelessly and capturing the logcat. No problems until this morning (Saturday). Then a spontaneous reboot. The log is quite long (attached below) but the meaty part seems to have a lot to do with getting ready to download and then install an update. There are many checks which seem to drive the device crazy because it discovers all these unexpected apps (!) as well as some missing ones. Seems especially distressed to find that the bndemomode.apk is missing. Go figure.
Anyway, at one point it decides it has a good copy of the update (in /cache/recovery---alas it disappears in the crash) and then all hell breaks loose, eventually resulting in a reboot (and a failed update, of course). My expectation is that this has nothing at all to do with USB audio but simply is a timing thing. The device happens to have an active WiFi connection when the B&N servers are looking for action. I could test this next Saturday morning, I guess.
The problem now is what to disable to prevent this in the future. I want the Library and Reader to be functional, but I don't purchase any B&N books or use any of the other B&N features.
I just got a second NST from a generous XDA member and I will probably experiment with that. First I want to see what's the deal with the 1.2.2 update. It's probably just security updates so the device can still interface with B&N servers. It would be nice if they updated the cacerts.bks file, but I doubt they did. Then I want to try eliminating as much B&N stuff as possible while still maintaining Library/Reader/Dictionary function--and not destabilizing the device.

it's the update attempt
So having established that the issue had shifted to early Saturday mornings I fired up WiFi this morning and just let the NST sit on the home screen, "no" apps running. Within an hour I actually saw the screen go black (from screensaver state) and then the device rebooted.
I've located a db in data/data/com.bn.devicemanager/databases which, among other things, holds a record of software updates (sample attached below). Before this morning there were 4 listed with (unfortunately) incomprehensible dates like "1524315275901" (last Saturday, 4-21-18). Today (4-28-18) there was a fifth entry dated "1524926768756". Each of the entries has a field for "date received" (with data like I've shown) and a field for "date last comp" (among other fields). The value for "date last comp" is "0" for each entry.
I'm thinking edit the "date last comp" field of today's record to show today's date string?
I'd just like this behavior to stop. Clearly the date and time for the update attempt do shift, following some arcane rules (a second NST running FW 1.2.1 and just registered but not rooted did not update this morning) so while early Saturday morning is better for me than early Sunday morning when I am listening to NPR, I don't imagine things will stay this way.
Any thoughts?
Edit: Oh @jeff_kz, I love you! Here is the answer: https://forum.xda-developers.com/showpost.php?p=34433959&postcount=3