Develop Bugs

Bluetooth pairing request every time you connect ?

well, i was told this problem did not exist in the note 2 but apparently it seems that it does stateside. i use my phone daily in my car to connect to the appradio 2 via bluetooth. with the note 2 every time you connect you must confirm the pairing request number by hitting OK. is there any possible way around this? this pairing request was a common complaing amongs gs3 users as well. however, i always used CM10 and the problem didn't exist on aosp roms.
am i missing something is there anyway around this? it definitely isn't a setting on my radio as i changed nothing and the previous phone connected automatically every time.

knives of ice said:
with the note 2 every time you connect you must confirm the pairing request number by hitting OK.
Click to expand...
Click to collapse
I don't have to confirm anything when I connect to Bluetooth in my car. I get in, put it in its holder, plug power in, Tasker turns on BT, and it connects, no confirmation.

somnifac said:
I don't have to confirm anything when I connect to Bluetooth in my car. I get in, put it in its holder, plug power in, Tasker turns on BT, and it connects, no confirmation.
Click to expand...
Click to collapse
Holder? Can I see a picture? :good:

somnifac said:
I don't have to confirm anything when I connect to Bluetooth in my car. I get in, put it in its holder, plug power in, Tasker turns on BT, and it connects, no confirmation.
Click to expand...
Click to collapse
damn, i have no idea why i get the pairing request every single time on the pioneer appradio. there are a ton of people that get the same thing with samsung phones but its fixed with aosp roms.

knives of ice said:
damn, i have no idea why i get the pairing request every single time on the pioneer appradio. there are a ton of people that get the same thing with samsung phones but its fixed with aosp roms.
Click to expand...
Click to collapse
I have the avh-4300 and for some reason auto connect was set to off. I hadn't changed it myself but that was the reason I wasn't connecting automatically.

Kelvala said:
Holder? Can I see a picture? :good:
Click to expand...
Click to collapse
It's nothing special. It's the universal windshield mount from Sprint. I've been using it for long enough that the padding in the clamp is kind of worn wide enough that the N2 *just* fits, if I slide it in from the top, with the clamp wide open. No need to put the phone in, and snug up the sides. Just slide it down into the foam.

knives of ice said:
with the note 2 every time you connect you must confirm the pairing request number by hitting OK. is there any possible way around this?
Click to expand...
Click to collapse
This happens on mine as well. No need to do anything but no need for an extra screen prompt

I have also had this problem, any fix yet?

I had the same problem, fixed after factory reseting my car DVD

question about smart covers

I just got my MoKo case for this. The smart cover is great and turns the screen off and on without having to mess with the power button all the time. But when the cover is closed for any long period of time, the screen does not turn on when the cover is opened. Why is that?

This has come up in a few threads. For me, it seems to be correlated with having no wifi connection. I've never seen the delay when wifi is operational, only when I've either turned off wifi or am no longer in range of the wifi I was connected to. At home, where I always leave wifi on, I can have it off overnight and it still comes on instantly when I open the case the next day.

If you set WiFi to turn off when the tablet is a sleep it will not turn back on after 15-30 minutes. I have mine set to WiFi always on and it works fine. If you want to save a little battery you can turn wifi off manually at night. Shame it doesn't work like the original Nexus 7.
Sent from my Nexus 7 using xda premium

ncguy68 said:
If you set WiFi to turn off when the tablet is a sleep it will not turn back on after 15-30 minutes. I have mine set to WiFi always on and it works fine. If you want to save a little battery you can turn wifi off manually at night. Shame it doesn't work like the original Nexus 7.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Although I don't have any of my wifi settings set to limit anything and are all set as suggested above, this was still occurring. I just tested this out with WiFi off and wifi settings don't appear to be the factor at all. With the tablet plugged in, I closed the smart cover and opened it about 45 minutes later and the screen came on fine. I unplugged it from the charger and closed the cover again for 45 more minutes and this time the screen did not turn on. Any ideas?
There is one setting that I do not have turned on and it's new to 4.3:
"Scanning always available
Let Google's location services and other apps scan for networks, even when WiFi is off"

When my Nexus is plugged in it never enters deep sleep and the auto on/off works fine.
When I changed the WiFi advanced setting to Keep WiFi awake during sleep to Always auto on/off works fine. If I turn WiFi off or set it to turn off during sleep the auto on/off will not work after 15-20 minutes.
I figure it has something to do with WiFi and/or deep sleep mode.
Sent from my Nexus 7 using xda premium

I had this issue when I was on stock. I believe the device has crashed. At this point, only option I had was to hold the power button until a full reboot.
Ever since switching to the CM10.2 nightlies, have never seen this issue again.
So my recommendation, get off of stock ASAP. :laugh:

That has nothing to do with it here, nothing is crashing. I think it's the smart cover not having the capability to waken the screen when the tablet is in deep sleep. It sounds to me like you traded crashes for something preventing deep sleep.

N7 had been closed for an hour.. I have Wifi off when screen is off... so *IF* that is the cause
- picked up the tablet, opened the cover.. did not turn on
- closed the cover
- opened again, N7 came on
so.. I ask, exactly how did the 1st failed opening wake up the Wifi (but not the tablet) if that is the culprit?
ie. if the determining failure condition is Wifi off rendering the cover unable to wake the tablet, I should be able to open/close/open the cover 100 times in a row without having it come on.

I don't know what the mechanism is, I just know it has never failed to come on instantly when it had a valid wifi connection.
It sometimes (but by no means always) has a big delay when wifi is off.
Those are the only two data points that seem consistent to me. Perhaps it does have to be off a long time and also have no wifi for the cover to not wake it immediately, but I haven't actually noticed if that is the case.

zim2dive said:
N7 had been closed for an hour.. I have Wifi off when screen is off... so *IF* that is the cause
- picked up the tablet, opened the cover.. did not turn on
- closed the cover
- opened again, N7 came on
so.. I ask, exactly how did the 1st failed opening wake up the Wifi (but not the tablet) if that is the culprit?
ie. if the determining failure condition is Wifi off rendering the cover unable to wake the tablet, I should be able to open/close/open the cover 100 times in a row without having it come on.
Click to expand...
Click to collapse
How long did you wait after the failed attempt to try the second attempt? Perhaps its just very very delayed the first time, and by the time you try the second time its "woken up" and ready to respond correctly?

muyoso said:
How long did you wait after the failed attempt to try the second attempt? Perhaps its just very very delayed the first time, and by the time you try the second time its "woken up" and ready to respond correctly?
Click to expand...
Click to collapse
I actually just got this case too well this one (http://amzn.com/B00CKA1IYU). Not sure if its the one you purchased. Mine was sitting in my office closed for about 45 minutes with WiFi off. I went over to open it and the screen turned on. I put it in my backpack later in the day and it sat there for about 30 minutes and I drove home. I got home and took it out of my backpack and set it on my desk unopened and with WiFi still off. I let it sit there for about another 30 minutes. I read this post and thought "I haven't opened the cover since before leaving work". So out of curiosity I opened it and the screen turned on.
So either my Nexus 7 isn't going into sleep with WiFi off or it actually works?
BTW: I like the case for the price! Bought 2 days ago so I paid 12.99 w/ free shipping.

Not the same but it's the same manufacturer so probably the same magnet

muyoso said:
How long did you wait after the failed attempt to try the second attempt? Perhaps its just very very delayed the first time, and by the time you try the second time its "woken up" and ready to respond correctly?
Click to expand...
Click to collapse
You have asked the magic question.
Left the N7 overnight.. got up, opened the case.. and watched... it took 10-15 seconds and then the screen came on, certainly very delayed, but as a consequence of opening the 1st time, as it should.
Just repeated the experiment after an hour.. ~9 seconds from flap open to display on.

cowabunga said:
I had this issue when I was on stock. I believe the device has crashed. At this point, only option I had was to hold the power button until a full reboot.
Ever since switching to the CM10.2 nightlies, have never seen this issue again.
So my recommendation, get off of stock ASAP. :laugh:
Click to expand...
Click to collapse
which CM10.2 nightlies are you using?
because i found there are few CM ROM in here.
thank you

prowede said:
which CM10.2 nightlies are you using?
because i found there are few CM ROM in here.
thank you
Click to expand...
Click to collapse
I run the official one from http://get.cm/?device=flo
Just get the most recent one (ie. dated 8/21 as of right now)

cowabunga said:
I run the official one from http://get.cm/?device=flo
Just get the most recent one (ie. dated 8/21 as of right now)
Click to expand...
Click to collapse
I just tried the official CM Rom today, however, the problem still exists.
I have tried different version (21, 23,24/8), still the same....
Very strange...

Problem still exists with Spet 11 build.
A pretty long lagtime for the wifi to reconnect before turning on the screen.
Turning on bluetooth is a workaround.
So smart wake waits for a wireless connection?
Wasn't the case in the old Nexus 7.

bland.life said:
Problem still exists with Spet 11 build.
A pretty long lagtime for the wifi to reconnect before turning on the screen.
Turning on bluetooth is a workaround.
So smart wake waits for a wireless connection?
Wasn't the case in the old Nexus 7.
Click to expand...
Click to collapse
For now (until there is a fix), turn on bluetooth and leave that enabled.. very little power drain, and prevents the delay turning back on.

zim2dive said:
For now (until there is a fix), turn on bluetooth and leave that enabled.. very little power drain, and prevents the delay turning back on.
Click to expand...
Click to collapse
If I have Bluetooth on and leave the cover closed for a long time and when I open the cover again the WiFi will not turn on.
In one instance I can flip the WiFi switch in Settings to on but it will revert to off, in another instance the switch simply refuse to barge.
Rebooting the device fixes it and brings WiFi back (until the next long cover closure).

bland.life said:
If I have Bluetooth on and leave the cover closed for a long time and when I open the cover again the WiFi will not turn on.
In one instance I can flip the WiFi switch in Settings to on but it will revert to off, in another instance the switch simply refuse to barge.
Rebooting the device fixes it and brings WiFi back (until the next long cover closure).
Click to expand...
Click to collapse
then you have a different/worse issue from everyone else (ie. the delay turning on after cover is opened).
I'd do a restore from a factory image, and try that for 2 days.. if it still won't turn on, you need to RMA yours.

trusted devices range is too great. need to decrease blue tooth power?

Hi all.. I find when i have my 360 as a trusted device on my phone, the blue tooth range is too powerful. example - it works over 10-15meters away.
i dont want my watch to unlock the phone unless im only 3-5m away..
help.....

I don't know a direct solution to your problem but a good work around is that if you click the unlock button on the lock screen before walking away, the device will stay locked and require a PIN before it can be opened again, even though its still paired with the trusted device. Very handy if you just wanna leave your phone for a few minutes but not going to be far enough away for it to disconnect from the watch or don't want to turn off the trusted devices feature.

Pixel not waking up from sleep

Anyone else having issues with the Pixel not waking up from sleep. This happens to me seemingly randomly, at least I have not been able to pinpoint what is causing it. I have to use the power button and volume rocker to hard reboot it. This is my second unit that has done this, and Google just wants to replace it again.
I made a quick video of it:
https://www.youtube.com/watch?v=97iho4sHAlc

I have exactly the same problem ...
to boot, I press 10 seconds repeatedly on the power button.
I already had the problem of keyboard update ...

I thought this was solved but sadly it's still around. Suffered from it a few days ago after doing a factory reset about a week ago.

Ves said:
I thought this was solved but sadly it's still around. Suffered from it a few days ago after doing a factory reset about a week ago.
Click to expand...
Click to collapse
Same here, I finally received the Feb update on my replacement Pixel and thought it was solved... nope.
I bought the Pixel for quick work trips so I did not have to bring my laptop. I take allot of flights in the morning and return that afternoon/evening. The Pixel was going to be used for Presentations, and notes. It is super frustrating when I have the tablet all setup to present and I have to mess with it to get it to turn back on. This thing has way to many problems for a premium tab, and seems like Google has not dedicated the appropriate resources to supporting it (support/dev).

Ah the old "Sleep of Death" it seems to have plagued (mostly) tablets for years. I've had it happen on my Asus Transformer T101 years ago and it also happened on my Samsung Galaxy Tab S 10.5". I haven't had it happen yet in the months I've owned the Pixel, but I have had some odd issues where I press the power button to turn it on and it shows the unlocked boot warning for literally a second and then turns off/reboots, when it does that I have to hold the power button for like 10 seconds to force a reboot and then it boots up fine.
Sent from my Pixel C using Tapatalk

I use the pattern to unlock my device. For years on my Asus TF201 (which had occasional severe performance problems), I would occasionally turn it on, get nothing for several seconds, and then get the pattern unlock screen for a fraction of a second, and then it would sleep. Sometimes if I drew the pattern really fast it would unlock it. Othertimes, I think I just rebooted it.
With the Google Pixel C, I (perhaps foolishly) continued the pattern unlock approach. It usually works fine. But occasionally, I will get the pattern unlock screen soon enough, enter the pattern, and it will do nothing for several seconds (just frozen on the pattern screen with my drawn pattern) and then go to sleep. If I try this repeatedly, sometimes once it will actually let me in. Otherwise I reboot and try again.

buurmas said:
I use the pattern to unlock my device. For years on my Asus TF201 (which had occasional severe performance problems), I would occasionally turn it on, get nothing for several seconds, and then get the pattern unlock screen for a fraction of a second, and then it would sleep. Sometimes if I drew the pattern really fast it would unlock it. Othertimes, I think I just rebooted it.
With the Google Pixel C, I (perhaps foolishly) continued the pattern unlock approach. It usually works fine. But occasionally, I will get the pattern unlock screen soon enough, enter the pattern, and it will do nothing for several seconds (just frozen on the pattern screen with my drawn pattern) and then go to sleep. If I try this repeatedly, sometimes once it will actually let me in. Otherwise I reboot and try again.
Click to expand...
Click to collapse
I do not use the pattern lock, I do secure it with a passcode though. My issue does not seem to be related to the security though as it does it at random times and never display the login prompt.

still having both random reboots and screen blackouts. This is a shame google will not acknowledge the problem and say they're fixing it. It only makes me believe that they know about it yet CANT fix it. Like its a hardware issue more than a software one. At least if they would say "we are aware of the issue and working on a fix" or "we were working on a fix but now working just a big OS update instead" Id feel like I wasnt ripped off by them. I mean I have EVERY nexus device box still displayed in my hobby room at my house. Im a huge fan but this is really bad.

Joined beta N program, hopefully this issue is resolved on the Pixel C.

Phone is starting....

I have my phone connected to my watch and utilizing smart lock so I dont need to do pattern or fingerprint unlock. However every morning I need to do pattern unlock and phone will say "Phone is initializing" as if I restarted the phone. Is this normal now on these phones?
Sent from my SM-N975U1 using Tapatalk

Have you set up scheduled reboots in device care by chance? Mine did that this morning but I have it set to restart overnight on Friday mornings.

VeriSkye said:
Have you set up scheduled reboots in device care by chance? Mine did that this morning but I have it set to restart overnight on Friday mornings.
Click to expand...
Click to collapse
Thanks. Weird it was set to reboot on Fridays. I never set that. Wonder if that's a default. And I swear yesterday morning I also had do pattern unlock. Maybe I'm trippin. Anyways, I will keep an eye out tomorrow. And I have changed it to reboot on Sundays.

I know I use to use this with devices and if you didn't use the phone for X amount of hours the phone would lock and require a pin/fingerprint, but that was back when I had the pixel, I stopped using it seemed to make me have to put my pin every time I wanted to use google pay instead of just unlocking my phone and paying.

I get that message when rebooting too. I came from a Pixel 3 and it didn't have that when restarting. Not sure if this is a Samsung thing but it makes startup a bit slow comparatively

bupac said:
I get that message when rebooting too. I came from a Pixel 3 and it didn't have that when restarting. Not sure if this is a Samsung thing but it makes startup a bit slow comparatively
Click to expand...
Click to collapse
it's seemingly to do with Knox and the encryption, seems it is to stop people connecting to the locked phone and extracting data in start up.

If you're referring to the message that says phone is starting after you unlock it you can get rid of that by turning this off.