[Q] All ROMS FC - Nexus One Q&A, Help & Troubleshooting

Hey all,
So this started one morning when I was using MUIU 9.30. Looked at phone and it would freeze on me. Anything I did, turned screen on and started navigating around for maybe 2 minutes and phone started FCing on Activity, or whatever the app happen to be up at the time. I thought maybe the ROM was all screwey, so I moved back to my cyanogen backup from a couple of days before. Same thing started happening, whether I was using LauncherPro or ADW. I had thought it might have been the MUIU launcher since before I was seeing it a lot while fooling around with icon placements. tried a wipe and reinstall of muiu, kept happening. Thought I'd start again with Cyanogen 6 but it happens on it too. Decided to go to Paul's release of FRG83 full stock with root, happened, same thing when trying FRG83 rooted with busybox. II have no idea where the problem is, I"m just afraid it's the N1 hardware. Captured logcat and this is what it shows.
Code:
10-07 14:56:09.078: WARN/SharedBufferStack(263): waitForCondition(LockCondition) timed out (identity=4, status=0). CPU may be pegged. trying again.
10-07 14:56:10.078: WARN/SharedBufferStack(263): waitForCondition(LockCondition) timed out (identity=4, status=0). CPU may be pegged. trying again.
10-07 14:56:10.448: INFO/Process(95): Sending signal. PID: 95 SIG: 3
10-07 14:56:10.459: INFO/dalvikvm(95): threadid=3: reacting to signal 3
10-07 14:56:10.479: INFO/dalvikvm(95): Wrote stack traces to '/data/anr/traces.txt'
10-07 14:56:11.078: WARN/SharedBufferStack(263): waitForCondition(LockCondition) timed out (identity=4, status=0). CPU may be pegged. trying again.
10-07 14:56:12.078: WARN/SharedBufferStack(263): waitForCondition(LockCondition) timed out (identity=4, status=0). CPU may be pegged. trying again.
10-07 14:56:13.078: WARN/SharedBufferStack(263): waitForCondition(LockCondition) timed out (identity=4, status=0). CPU may be pegged. trying again.
Code:
10-07 14:56:39.078: WARN/SharedBufferStack(263): waitForCondition(LockCondition) timed out (identity=4, status=0). CPU may be pegged. trying again.
10-07 14:56:40.078: WARN/SharedBufferStack(263): waitForCondition(LockCondition) timed out (identity=4, status=0). CPU may be pegged. trying again.
10-07 14:56:40.478: INFO/Process(95): Sending signal. PID: 95 SIG: 3
10-07 14:56:40.478: INFO/dalvikvm(95): threadid=3: reacting to signal 3
10-07 14:56:40.498: INFO/dalvikvm(95): Wrote stack traces to '/data/anr/traces.txt'
10-07 14:56:40.508: INFO/Process(95): Sending signal. PID: 272 SIG: 3
10-07 14:56:40.508: INFO/dalvikvm(272): threadid=3: reacting to signal 3
10-07 14:56:40.508: INFO/dalvikvm(272): Wrote stack traces to '/data/anr/traces.txt'
10-07 14:56:41.078: WARN/SharedBufferStack(263): waitForCondition(LockCondition) timed out (identity=4, status=0). CPU may be pegged. trying again.
10-07 14:56:42.078: WARN/SharedBufferStack(263): waitForCondition(LockCondition) timed out (identity=4, status=0). CPU may be pegged. trying again.
10-07 14:56:42.508: INFO/Watchdog_N(95): dumpKernelStacks
10-07 14:56:43.078: WARN/SharedBufferStack(263): waitForCondition(LockCondition) timed out (identity=4, status=0). CPU may be pegged. trying again.
10-07 14:56:44.088: WARN/SharedBufferStack(263): waitForCondition(LockCondition) timed out (identity=4, status=0). CPU may be pegged. trying again.
Code:
10-07 14:57:40.088: WARN/SharedBufferStack(263): waitForCondition(LockCondition) timed out (identity=4, status=0). CPU may be pegged. trying again.
10-07 14:57:40.268: WARN/ActivityManager(95): Activity idle timeout for HistoryRecord{44f93990 com.android.launcher/com.android.launcher2.Launcher}
10-07 14:57:40.268: WARN/ActivityManager(95): Timeout of broadcast BroadcastRecord{4512e048 android.intent.action.SCREEN_ON} - [email protected]
10-07 14:57:40.268: WARN/ActivityManager(95): Receiver during timeout: BroadcastFilter{44f3ba20 ReceiverList{44f3de78 272 com.android.phone/1001 remote:44f37ff0}}
10-07 14:57:40.278: DEBUG/WindowManager(95): I'm tired mEndcallBehavior=0x2
10-07 14:57:40.378: DEBUG/dalvikvm(95): GC_FOR_MALLOC freed 9697 objects / 410944 bytes in 93ms
10-07 14:57:40.378: INFO/dalvikvm-heap(95): Grow heap (frag case) to 5.278MB for 74655-byte allocation
10-07 14:57:40.458: DEBUG/dalvikvm(95): GC_FOR_MALLOC freed 279 objects / 13520 bytes in 81ms
10-07 14:57:40.458: INFO/Process(95): Sending signal. PID: 272 SIG: 3
10-07 14:57:40.468: INFO/dalvikvm(272): threadid=3: reacting to signal 3
10-07 14:57:40.488: INFO/dalvikvm(272): Wrote stack traces to '/data/anr/traces.txt'
10-07 14:57:40.558: INFO/Process(95): Sending signal. PID: 95 SIG: 3
10-07 14:57:40.558: INFO/dalvikvm(95): threadid=3: reacting to signal 3
10-07 14:57:40.558: DEBUG/dalvikvm(95): GC_FOR_MALLOC freed 183 objects / 6928 bytes in 90ms
10-07 14:57:40.558: INFO/dalvikvm-heap(95): Grow heap (frag case) to 5.403MB for 99532-byte allocation
10-07 14:57:40.658: DEBUG/dalvikvm(95): GC_FOR_MALLOC freed 3 objects / 112 bytes in 76ms
10-07 14:57:40.668: WARN/ActivityManager(95): finishReceiver called but none active
10-07 14:57:40.758: INFO/Process(95): Sending signal. PID: 264 SIG: 3
10-07 14:57:40.758: INFO/dalvikvm(264): threadid=3: reacting to signal 3
10-07 14:57:40.768: DEBUG/dalvikvm(95): GC_FOR_MALLOC freed 157 objects / 105400 bytes in 96ms
10-07 14:57:40.768: INFO/dalvikvm-heap(95): Grow heap (frag case) to 5.545MB for 199048-byte allocation
10-07 14:57:40.788: INFO/dalvikvm(95): Wrote stack traces to '/data/anr/traces.txt'
10-07 14:57:40.818: INFO/dalvikvm(264): Wrote stack traces to '/data/anr/traces.txt'
10-07 14:57:40.858: INFO/Process(95): Sending signal. PID: 263 SIG: 3
10-07 14:57:40.858: INFO/dalvikvm(263): threadid=3: reacting to signal 3
10-07 14:57:40.868: DEBUG/dalvikvm(95): GC_FOR_MALLOC freed 693 objects / 22280 bytes in 95ms
10-07 14:57:40.908: INFO/dalvikvm(263): Wrote stack traces to '/data/anr/traces.txt'
10-07 14:57:40.968: INFO/Process(95): Sending signal. PID: 484 SIG: 3
10-07 14:57:40.978: INFO/dalvikvm(484): threadid=3: reacting to signal 3
10-07 14:57:40.978: DEBUG/dalvikvm(95): GC_FOR_MALLOC freed 74 objects / 276432 bytes in 77ms
10-07 14:57:41.038: DEBUG/dalvikvm(95): GC_FOR_MALLOC freed 32 objects / 202528 bytes in 56ms
10-07 14:57:41.058: INFO/dalvikvm(484): Wrote stack traces to '/data/anr/traces.txt'
10-07 14:57:41.058: INFO/Process(95): Sending signal. PID: 294 SIG: 3
10-07 14:57:41.068: INFO/dalvikvm(294): threadid=3: reacting to signal 3
10-07 14:57:41.098: INFO/Process(95): Sending signal. PID: 95 SIG: 9
10-07 14:57:41.098: WARN/Watchdog(95): *** WATCHDOG KILLING SYSTEM PROCESS: com.android.server.am.ActivityManagerService
10-07 14:57:41.258: INFO/dalvikvm(294): Wrote stack traces to '/data/anr/traces.txt'
10-07 14:57:41.938: WARN/SharedBufferStack(263): waitForCondition(LockCondition) timed out (identity=4, status=0). CPU may be pegged. trying again.
Code:
10-07 15:01:43.998: WARN/SharedBufferStack(263): waitForCondition(LockCondition) timed out (identity=4, status=0). CPU may be pegged. trying again.
10-07 15:01:44.998: WARN/SharedBufferStack(263): waitForCondition(LockCondition) timed out (identity=4, status=0). CPU may be pegged. trying again.
10-07 15:01:45.698: INFO/ServiceManager(53): service 'SurfaceFlinger' died
10-07 15:01:45.698: INFO/ServiceManager(53): service 'permission' died
I broke up the Log as I didnt think it was necessary that I post the same SharedBufferStack warning over and over, just image it continuous between the breaks. If you notice the times most of those have at least a full minute of the SharedBufferStack warning, and between the last 2 sections over 3 minutes of nothing but the warning go by and then the phone just gives up and reboots.
Seeing all those SharedBufferStack warning makes me afraid my CPU is failing.
Does anyone have any idea what may be happening to my phone?

Did you try turning off backup & restore settings in menu before wipe, and/or wiping everything and starting with clean ROM?

I didnt turn backup and restore settings before wiping, but on the last few tries I did skip sign in so it wouldnt try to pull down all my apps or contacts or anything. Yet it still happened. As of right now, I have only seen it freeze once after posting my comment and am dreading a reboot thinking it may happen again.
And yes, i have tried a full wipe and coming back to a clean stock rom. I'll post again later if it happens again, but I'm still wondering why this would happen across ROMs even though I have done full wipes, SDEXT, cache, dalvik cache, system.

Huascar82 said:
I didnt turn backup and restore settings before wiping, but on the last few tries I did skip sign in so it wouldnt try to pull down all my apps or contacts or anything. Yet it still happened. As of right now, I have only seen it freeze once after posting my comment and am dreading a reboot thinking it may happen again.
And yes, i have tried a full wipe and coming back to a clean stock rom. I'll post again later if it happens again, but I'm still wondering why this would happen across ROMs even though I have done full wipes, SDEXT, cache, dalvik cache, system.
Click to expand...
Click to collapse
I had a similar problem like this when 2.2 was released. Try installing a rom with a sdcard that only has the rom on it.
My problem originated from a folder of pictures that apparently were so corrupt it would freeze my phone. So just slowly copy over your phones files and see if you can pinpoint the file that might be causing it.

Related

[Q] Course network location issue. Rooted, unlocked flashed (froyo) G1

Guys,
I know you lot are a bunch of geniuses, and I really need your help.
I've searched these forums for the last 2 1/2 hours and come away with nothing more than a headache.
I have recently flashed my G1 with the latest release of Cyanogenmod 6.1.0.
Before this, I always!! got coarse network location from the phone, whenever I posted a Buzz or used Google maps, even the weather widget worked perfectly.
Now I've flashed, it's not working.
I've tried a "permanent" fix I was hoping would work here:
http://forum.xda-developers.com/showpost.php?p=9576852&postcount=108
But it didn't. No change.
However, if I follow the instructions in post 1:
http://forum.xda-developers.com/showthread.php?t=845152
Force closing and clearing the user data, followed by a reboot, it works!
But it stops again after a reboot.
All I can figure is that something is blocking the network location stuff stored in Google Services Framework which is deleted when I clear, and rewritten on a reboot.. Is there an APK or .ZIP floating around which addresses this?
To add to this, I was getting this network issue on Biff's Froyo Rom.
I've tried flashing different radios (I usually use the one ending in I, but have tried the newer one ending in 02) with no change.
I want to use Froyo so very badly, but I rely heavily on this coarse network location detection, and without it the phone just doesn't respond fast enough for me on location requests. (Relying on GPS alone)
I'm unlocked, flashed with Danger SPL, running stock radio (ending in I).
I'm sure I'm not the only G1 user with this problem, it seems to be common, so I really hope I just didn't search for the correct keywords and someone will be here to point me to the answer!
If anyone needs more info, please let me know.
Hope someone can help!
Jason
Edit: Logcat of error...
D/LocationMasfClient( 159): getNetworkLocation(): Location not found in cache,
making network request
D/LocationMasfClient( 159): getNetworkLocation(): Number of prefetched entries
0
D/dalvikvm( 159): GC_FOR_MALLOC freed 19253 objects / 1006720 bytes in 243ms
E/LocationMasfClient( 159): getNetworkLocation(): GLS does not have location
Bump!
To add to this, I noticed today I had location in the centre of town, but when I came home it wouldn't update. It kept telling me I was still in town.
Thanks.

USB Mount Broken After Upgarding to Latest CM7 Nightly

I've just upgraded my Nook Color to the latest nightly build, encore_70.
Everything worked fine, except that when I connected my Nook to computer, and clicked on the "Select to copy files from/to your computer" from the notification area, nothing happened. No dialogs, no errors.
I wonder what's wrong? I don't see other people complaining about this, but both my nook color and my computer used to work just fine.
I tried to start it from adb am and run adb logcat for it, here's the dump:
...
I/ActivityManager( 1016): Starting: Intent { flg=0x10000000 cmp=com.android.syst
emui/.usb.UsbStorageActivity } from pid 3593
D/AndroidRuntime( 3593): Shutting down VM
D/dalvikvm( 3593): GC_CONCURRENT freed 101K, 69% free 321K/1024K, external 0K/0K
, paused 0ms+0ms
D/jdwp ( 3593): adbd disconnected
D/VoldCmdListener( 913): volume shared /mnt/sdcard ums
D/VoldCmdListener( 913): volume shared /mnt/emmc ums
W/InputManagerService( 1016): Window already focused, ignoring focus gain of: co
[email protected]
I/ActivityManager( 1016): Displayed com.android.systemui/.usb.UsbStorageActivity
: +586ms (total +5m38s822ms)
Doesn't seem to have any problems. I can see the SD card and internal storage icons on my desktop now, but none of them actually mounted.
Same here (nightly 69). I used to get two icons in the notification area on the NC, when USB was plugged in - a USB symbol and a little bug icon. Now I just get the USB symbol and tapping on it does nothing.
Ditto here...I noticed it last night, not sure what # nightly I had....figured it was a bug and updated to the latest. Same problem....when I click on the notification, for a brief second see the screen when you mount the SD card (the little Android with a USB arm)....but then it just goes back to my homescreen.
I am having the same problem here.
EdInBTR said:
I am having the same problem here.
Click to expand...
Click to collapse
Me too. Was at latest "stable" now tried #73 & #74 Nightlies. Both don't work.
k
Edit: Went back to last "Stable" (Think it is 5/8) & the function is back.
Guys, this is a known issue with the latest builds of CM7..... It was discovered and noted late last week. If you need USB connectivity, you need to go back to a stable CM7 or download an app from the market (sorry can't remember what it's called).
I installed WiFi Explorer Pro when this issue cropped up. I can think of few reasons to go back to USB connecting to my desktop.
Sent from my NookColor using XDA Premium App
Chasmodai said:
I installed WiFi Explorer Pro when this issue cropped up. I can think of few reasons to go back to USB connecting to my desktop.
Sent from my NookColor using XDA Premium App
Click to expand...
Click to collapse
Yup....That was the app.
i use this app http://forum.xda-developers.com/showthread.php?t=952456 works extremely well
EverythingNook said:
i use this app http://forum.xda-developers.com/showthread.php?t=952456 works extremely well
Click to expand...
Click to collapse
I use the same since I bought my NOOK and it was always the best solution for USB connection.

PuTTY Fatal Error

Does anyone know why Android Studio periodically attempts to open a connection (status bar says Checking Incoming and Outgoing Changes), and then fails with a popup(Title = "PuTTY Fatal Error", Content="Network error: Connection timed out")?
I took a screenshot and have attached it.
This began earlier today and has become really annoying.
PEBKAC
Loool
It was a work project, and Android Studio was trying to connect to the office Mercurial repository, which it couldn't do since I was at home.
*facepalm*
Nothing to see here... Move along.

[Bluetooth]Turn off and on without reason or pattern

Hello everyone,
A big thanks in advance (and after, no worries) if you can help.
I have a nexus 6, CM13 and all it's fine but few weeks ago my bluetooth started to act a little strange by itself : it's turn off, disconnect the headset and turn on and reconnect the headset.
I have made test this weekend and I don't see any pattern.
I desactivate all the authorization for all the apps and no succes. I deinstall lot of apps but nothing.
I have the habit of listenning audio book when running or fitness so to have to relaunch the play during activity is quite boring.
If you have any idea or if you need some log, please ask!
You're not alone. I and many others are having the same problem with no resolution yet. I even bought a new headset a couple months ago, thinking my headset was going bad, but that didn't help.
I saw that. I find a lot of thread on the net about this problem. Various rom, various phone and no solution.
Sometimes they tried to do factory reset but with no success.
And I have two headset (one for the sport and one for the rest) so I already exclude the headset.
BT issues are really nothing new with CM roms. They have had them for years and never fixed them. This is why more and more are no longer using their code. Many are completely dropping all their code with the 7.0 update.
Your best bet is to troubleshoot it yourself. The first thing you should have done is pull a logcat.
JimSmith94 said:
You're not alone. I and many others are having the same problem with no resolution yet. I even bought a new headset a couple months ago, thinking my headset was going bad, but that didn't help.
Click to expand...
Click to collapse
I should have mentioned that I'm not on CM, but am having the same problems on stock rooted 6.0.1 with the August security update.
JimSmith94 said:
I should have mentioned that I'm not on CM, but am having the same problems on stock rooted 6.0.1 with the August security update.
Click to expand...
Click to collapse
This normally turns out to be a kernel issue somewhere. As you are on stock then I would get a logcat. At worst case it maybe a hardware issue. A log will help you determine where the issue is.
Same problem here. For months having this annoying issue.
I'm also on stock rom, and this is getting worse everyday. I am now on Nougat beta participating in the preview with the stock rom and the problem is still there.
I tried several fixes and resets, wipes, etc. with no success. I am very close to throw it against the wall, believe me. It is specially annoying with my VW bluetooth and with a Jabra 510 speaker. With my other bluetooth headphones (Genius) it works very well and no cuts... I don't understand the pattern...
So, I read to do a logcat... how do I do it? And how do I deduct from the log what is happening and when?
Thanks in advance.
agustinsj said:
Same problem here. For months having this annoying issue.
I'm also on stock rom, and this is getting worse everyday. I am now on Nougat beta participating in the preview with the stock rom and the problem is still there.
I tried several fixes and resets, wipes, etc. with no success. I am very close to throw it against the wall, believe me. It is specially annoying with my VW bluetooth and with a Jabra 510 speaker. With my other bluetooth headphones (Genius) it works very well and no cuts... I don't understand the pattern...
So, I read to do a logcat... how do I do it? And how do I deduct from the log what is happening and when?
Thanks in advance.
Click to expand...
Click to collapse
XDA Developers, being a forum for developers, has many tutorials and help threads about logcat, since a logcat is the single best, and often the ONLY way to find OS level issues.
http://forum.xda-developers.com/showthread.php?t=2141817
http://forum.xda-developers.com/showthread.php?t=1726238
http://forum.xda-developers.com/showthread.php?t=1378491
Pkt_Lnt said:
XDA Developers, being a forum for developers, has many tutorials and help threads about logcat, since a logcat is the single best, and often the ONLY way to find OS level issues.
http://forum.xda-developers.com/showthread.php?t=2141817
http://forum.xda-developers.com/showthread.php?t=1726238
http://forum.xda-developers.com/showthread.php?t=1378491
Click to expand...
Click to collapse
I have a BT headset and an Android Wear watch connected.Here are (I think) the relevant parts of one of my logcats where it dies and restarts four minutes apart:
Code:
08-10 12:53:17.182 975 1681 I ActivityManager: Process com.android.bluetooth (pid 21994) has died
08-10 12:53:17.183 975 1681 W ActivityManager: Scheduling restart of crashed service
...
08-10 12:53:17.401 975 1073 I ActivityManager: Start proc 31623:com.android.bluetooth/1002 for service com.android.bluetooth/.btservice.AdapterService
...
08-10 12:53:20.312 975 3086 I ActivityManager: Process com.android.bluetooth (pid 31623) has died
08-10 12:53:20.313 975 3086 W ActivityManager: Scheduling restart of crashed service
...
08-10 12:53:21.362 975 2813 I ActivityManager: Start proc 31765:com.android.bluetooth/1002 for broadcast com.android.bluetooth/.pbap.BluetoothPbapReceiver
...
08-10 12:57:43.497 975 3092 I ActivityManager: Process com.android.bluetooth (pid 31765) has died
08-10 12:57:43.499 975 3092 W ActivityManager: Scheduling restart of crashed service
...
08-10 12:57:43.695 975 1073 I ActivityManager: Start proc 932:com.android.bluetooth/1002 for service com.android.bluetooth/.btservice.AdapterService
...
08-10 12:57:46.510 975 3098 I ActivityManager: Process com.android.bluetooth (pid 932) has died
08-10 12:57:46.511 975 3098 W ActivityManager: Scheduling restart of crashed service
...
08-10 12:57:49.453 975 1073 I ActivityManager: Start proc 1403:com.android.bluetooth/1002 for service com.android.bluetooth/.btservice.AdapterService
I see nothing before it dies, and it seems really weird that BT dies with only an informational message, but the restarts are warnings.
JimSmith94 said:
I have a BT headset and an Android Wear watch connected.Here are (I think) the relevant parts of one of my logcats where it dies and restarts four minutes apart:
Code:
08-10 12:53:17.182 975 1681 I ActivityManager: Process com.android.bluetooth (pid 21994) has died
08-10 12:53:17.183 975 1681 W ActivityManager: Scheduling restart of crashed service
...
08-10 12:53:17.401 975 1073 I ActivityManager: Start proc 31623:com.android.bluetooth/1002 for service com.android.bluetooth/.btservice.AdapterService
...
08-10 12:53:20.312 975 3086 I ActivityManager: Process com.android.bluetooth (pid 31623) has died
08-10 12:53:20.313 975 3086 W ActivityManager: Scheduling restart of crashed service
...
08-10 12:53:21.362 975 2813 I ActivityManager: Start proc 31765:com.android.bluetooth/1002 for broadcast com.android.bluetooth/.pbap.BluetoothPbapReceiver
...
08-10 12:57:43.497 975 3092 I ActivityManager: Process com.android.bluetooth (pid 31765) has died
08-10 12:57:43.499 975 3092 W ActivityManager: Scheduling restart of crashed service
...
08-10 12:57:43.695 975 1073 I ActivityManager: Start proc 932:com.android.bluetooth/1002 for service com.android.bluetooth/.btservice.AdapterService
...
08-10 12:57:46.510 975 3098 I ActivityManager: Process com.android.bluetooth (pid 932) has died
08-10 12:57:46.511 975 3098 W ActivityManager: Scheduling restart of crashed service
...
08-10 12:57:49.453 975 1073 I ActivityManager: Start proc 1403:com.android.bluetooth/1002 for service com.android.bluetooth/.btservice.AdapterService
I see nothing before it dies, and it seems really weird that BT dies with only an informational message, but the restarts are warnings.
Click to expand...
Click to collapse
Is this logcat from the watch or phone and is the headset connected to the watch or phone and is this BT crash from the watch or headset?
I'm trying to understand if this is a phone issue or watch issue and who to get this information to for some help?
As we've exchanged posts before, both my headset and watch drop connections from the phone, though I've minimized this with some hacks. This only happens when I am out and about, and can not duplicate it when I am near a computer to get a logcat. When I'm walking or on my bike I get it from the headset, even when the phone is on my belt only two feet away. When I look at the watch, it has dropped too.
Pkt_Lnt said:
Is this logcat from the watch or phone and is the headset connected to the watch or phone and is this BT crash from the watch or headset?
I'm trying to understand if this is a phone issue or watch issue and who to get this information to for some help?
As we've exchanged posts before, both my headset and watch drop connections from the phone, though I've minimized this with some hacks. This only happens when I am out and about, and can not duplicate it when I am near a computer to get a logcat. When I'm walking or on my bike I get it from the headset, even when the phone is on my belt only two feet away. When I look at the watch, it has dropped too.
Click to expand...
Click to collapse
Hi Pkt_Lnt! This is from my phone and I have saved the rest of the logcat if it will help you. My BT headset is only connected to my phone. This was at home while I was on a phone call and the BT connections to both the headset and watch were lost twice. The phone icon went from connected to just on both times. I don't recall this happening before I got an Android Wear watch, but I've had several over the past few years.
BTW, I'm only on the phone two or three times a day, but this happens almost every time I receive a call, but very rarely when I initiate a call.
I'd be interested in what hacks you have done to see if they might help me.
Thanks Pkt_Lnt! for your useful information.
As Jim I also have a watch connected (Huawei) and I see also continuous but random disc&connections.
Will try to get that catlog for the thread as soon as I can.
One thing that maybe a chance or not is that always always when I'm ridding and go through a bridge the BT disconnects from my car headset. Always. That is the only pattern I can verify. Can a LTE cell update break a BT connection? Maybe the radio chip is fooled by this change?
I remember in previous versions to marshmallow that this happened once in a blue moon... now dozens an hour.
Thanks.
JimSmith94 said:
Hi Pkt_Lnt! This is from my phone and I have saved the rest of the logcat if it will help you. My BT headset is only connected to my phone. This was at home while I was on a phone call and the BT connections to both the headset and watch were lost twice. The phone icon went from connected to just on both times. I don't recall this happening before I got an Android Wear watch, but I've had several over the past few years.
BTW, I'm only on the phone two or three times a day, but this happens almost every time I receive a call, but very rarely when I initiate a call.
I'd be interested in what hacks you have done to see if they might help me.
Click to expand...
Click to collapse
I've frozen Google Connectivity Services, switched to Legacy DHCP in developer settings, turned off wifi on the watch, and disabled cloud sync in the Android Wear app on the phone.
agustinsj said:
Thanks Pkt_Lnt! for your useful information.
As Jim I also have a watch connected (Huawei) and I see also continuous but random disc&connections.
Will try to get that catlog for the thread as soon as I can.
One thing that maybe a chance or not is that always always when I'm ridding and go through a bridge the BT disconnects from my car headset. Always. That is the only pattern I can verify. Can a LTE cell update break a BT connection? Maybe the radio chip is fooled by this change?
I remember in previous versions to marshmallow that this happened once in a blue moon... now dozens an hour.
Thanks.
Click to expand...
Click to collapse
Well, the bridge would block the cell signal, but I don't think it should drop the BT since they are handled by different software, but I'm not sure what hardware (antenna) handle cellular / wifi / bluetooth. This is hard to sort out. What I know is that cellular, voice and data, is controlled by the phone radio. Both wifi and bluetooth are controlled by the kernel. On bluetooth and wifi drops, they will occur simultaneously for me. When I see a bluetooth drop on mobile, there is not effect on my cellular data.
So, what would help is noting phone type, ROM used, kernel used, and I know we all have Huawei watches. I have a Nexus 6, Pure nexus ROM, ElementalX kernel. I've tested three kernels besides stock to see what is happening. It just occurred to me that I have not disconnected my watch when out using my headset to see if those headset dropouts happen.
edit - Even though I've tried differnet kernels to solve the BT / WiFi drops, I suspect they have the same stock kernel modules that control those functions since I've seen no difference in them. No kernel control apps have anything related to those two functions either. (le sigh)
There is no solution, but hope for the future.
Check posts 8 and 11 here. I have the HBS-730 and it works except for the "out of range" dropouts.
http://forum.xda-developers.com/nexus-6/help/nexus-6-marshmallow-bluetooth-operating-t3253708
Ideas from Reddit, none have worked for me.
https://www.reddit.com/r/nexus6/comments/4pk876/nexus_6_keeps_disconnecting_bluetooth_audio_at/
Google Product forums have many posts, but no solutions and it is a user to user forum like XDA.
I've found so many entries in Google Code, but none that seem to be this issue. I have not been able to search all that come up to narrow it down and report with a good logcat.
https://code.google.com/p/android/i...D+Type+Status+Owner+Summary+Stars&cells=tiles
Now my head hurts from all the searching, I need a time out.
Pkt_Lnt said:
I've frozen Google Connectivity Services, switched to Legacy DHCP in developer settings, turned off wifi on the watch, and disabled cloud sync in the Android Wear app on the phone.
Well, the bridge would block the cell signal, but I don't think it should drop the BT since they are handled by different software, but I'm not sure what hardware (antenna) handle cellular / wifi / bluetooth. This is hard to sort out. What I know is that cellular, voice and data, is controlled by the phone radio. Both wifi and bluetooth are controlled by the kernel. On bluetooth and wifi drops, they will occur simultaneously for me. When I see a bluetooth drop on mobile, there is not effect on my cellular data.
So, what would help is noting phone type, ROM used, kernel used, and I know we all have Huawei watches. I have a Nexus 6, Pure nexus ROM, ElementalX kernel. I've tested three kernels besides stock to see what is happening. It just occurred to me that I have not disconnected my watch when out using my headset to see if those headset dropouts happen.
edit - Even though I've tried differnet kernels to solve the BT / WiFi drops, I suspect they have the same stock kernel modules that control those functions since I've seen no difference in them. No kernel control apps have anything related to those two functions either. (le sigh)
Click to expand...
Click to collapse
I am on a stock rooted Nexus 6 running the latest MOB30W, my watch is the Huawei Watch running the latest M6E69B, and I'm on the latest Android Wear 1.5.0.3124679.gms.
I have tried your hacks as well, but they made no difference. However, I just tried your suggestion and disconnected my watch in the Android Wear app. I just made it through a 25 minute incoming call with no disconnect at all, so I think you're on to something! Maybe for now, somebody can come up with something in Tasker to disconnect the watch when the phone is answered and reconnect on hangup.
JimSmith94 said:
I am on a stock rooted Nexus 6 running the latest MOB30W, my watch is the Huawei Watch running the latest M6E69B, and I'm on the latest Android Wear 1.5.0.3124679.gms.
I have tried your hacks as well, but they made no difference. However, I just tried your suggestion and disconnected my watch in the Android Wear app. I just made it through a 25 minute incoming call with no disconnect at all, so I think you're on to something! Maybe for now, somebody can come up with something in Tasker to disconnect the watch when the phone is answered and reconnect on hangup.
Click to expand...
Click to collapse
Ah, I love Tasker ideas!
http://www.pocketables.com/2015/01/disconnecting-one-bluetooth-device-using-tasker.html
Try the attached, customize them for your device and contacts and let me know. I don't have a second phone here to test them at the moment.
You will need Secure Settings if you don't already have it. It has its own idiosyncrasies with systemless root if you have it.
Attachments removed because of errors in my logic.
Pkt_Lnt said:
Ah, I love Tasker ideas!
http://www.pocketables.com/2015/01/disconnecting-one-bluetooth-device-using-tasker.html
Try the attached, customize them for your device and contacts and let me know. I don't have a second phone here to test them at the moment.
You will need Secure Settings if you don't already have it. It has its own idiosyncrasies with systemless root if you have it.
Click to expand...
Click to collapse
Haha, I had created my own before I saw that you had attached yours! The watch ID is different of course, but yours disconnects when the phone is ringing and reconnects when it's off hook.
As I understand it, off hook means that the phone state is either dialing, active, or on hold, so I set mine to disconnect the watch when the phone is off hook and reconnect when it's idle. I'm a Tasker rookie, and I don't have a second phone to test with either, so I could be wrong.
JimSmith94 said:
Haha, I had created my own before I saw that you had attached yours! The watch ID is different of course, but yours disconnects when the phone is ringing and reconnects when it's off hook.
As I understand it, off hook means that the phone state is either dialing, active, or on hold, so I set mine to disconnect the watch when the phone is off hook and reconnect when it's idle. I'm a Tasker rookie, and I don't have a second phone to test with either, so I could be wrong.
Click to expand...
Click to collapse
Oh good. Yes I can see now I had phone off hook wrong. I have plenty of Tasker profiles, but none on phone calls. Let me know if this works when you test it.
Pkt_Lnt said:
Oh good. Yes I can see now I had phone off hook wrong. I have plenty of Tasker profiles, but none on phone calls. Let me know if this works when you test it.
Click to expand...
Click to collapse
I added flash messages to my connect and disconnect tasks, dialed my Google Voice number, and the messages popped up on the screen properly. I'll have to wait for an actual call to be sure it really works.
Dear all,
I just install catlog, launch it, bluetooth, the music app and after a few moment : disconneting like always.

Logcat shows "EVENT_COUNTRY_NOT_WHITELISTED"

I turned on "Force debug logging" in Android Auto's Developer Settings, then plugged the phone to crankshaft (an Android Auto head unit emulator that runs on a Raspberry Pi).
While on a trip to Japan earlier, I could use Android Auto with the rental car's head unit. So when it didn't work with crankshaft back home, I decided to check log, and these lines caught my attention:
Code:
04-15 18:30:12.842 27404 27404 I FsmController.LITE: fireEvent(EVENT_COUNTRY_NOT_WHITELISTED)
04-15 18:30:12.842 27404 27404 I CAR.SETUP.LITE: setup failed
04-15 18:30:12.842 27404 27404 I CAR.SETUP.LITE: Setup finished: supported=false
04-15 18:30:12.851 27404 30767 V ClearcutMetricXmitter: Transmission is done.
04-15 18:30:12.852 27404 30767 V ClearcutMetricXmitter: Transmission is done.
04-15 18:30:12.852 27404 30767 V ClearcutMetricXmitter: Transmission is done.
04-15 18:30:12.856 27359 4073 D GH.ConnBroadcast: com.google.android.gms.car.FRX: state=FAILED, at 1299780
04-15 18:30:12.856 27404 27404 I CAR.SETUP.SERVICE.LITE: Tearing down car connection for reason 1
04-15 18:30:12.856 27359 27500 I GH.ConnLoggerV2: Session 77c4cc77-0aaa-4dd4-911c-028e73d40e0a, event 35, detail OptionalInt.empty, FRX_FAILED, at 1299780
04-15 18:30:12.856 27404 27404 I CAR.STARTUP.LITE: Tearing down car connection with reason 1
04-15 18:30:12.856 27404 27404 I CAR.SETUP.SERVICE.LITE: tearDown
So it seems pretty obvious that Android Auto actively terminated connection because of "EVENT_COUNTRY_NOT_WHITELISTED". This gets me thinking - to still try and use AA, would it be possible to use a GPS spoofer? Has anyone had success using AA in countries where AA is banned?
Already tried VPN'ing to another country, doesn't work...
Also just tried "GPS Setter". Spoofed location for Google Maps (as a test) and Android Auto. Maps shows spoofed location, but AA still fails to connect for the same reason (i.e. EVENT_COUNTRY_NOT_WHITELISTED)
Any help appreciated !!
Found a solution after search through local discussion forums.
The problem actually lies with "Google Play Services" which is the one responsible for detecting where your location is, not "Android Auto". The key to working around this issue of using Android Auto in an unapproved country is to download the Google Play Services with a particular build variant. If you retrieve the version number of the currently installed Google Play Services on your phone, you will see something like "Version: xx.xx.xx (190400-xxxxxxxxx)" where the number in brackets is the "build variant". For A12, you will probably have 190400-xxxxxxxxx as your build variant, and A11 will likely have 150400-xxxxxxxxx.
The only build variants known so far that bypass country checks are 200400 for A12, and 170400 for A11. APKMirror has these build variants that you can download. Once you have replaced "google play services" with the one you have downloaded from APKMirror, you are good to go. The only question left now is - how do you prevent Google Play from auto-updating Google Play Services back to the newest and problematic version?

Categories

Resources