Does anyone else have issues with the WiFi connection while the screen is turned off? I noticed that not a single one of my music streaming / radio apps work when the screen isn't on. It works for maybe a minute before all sound just stops. Starts just fine again once I power up the screen.
Has there been any changes done to the handling of these matters in ICS perhaps?
Pretty annoying not being able to stream music over WiFi as I think I'll hit my 5GB limit on data pretty fast if I can't use the WiFi at work for this.
So has anyone else noticed these issues?
SBS_ said:
Does anyone else have issues with the WiFi connection while the screen is turned off? I noticed that not a single one of my music streaming / radio apps work when the screen isn't on. It works for maybe a minute before all sound just stops. Starts just fine again once I power up the screen.
Has there been any changes done to the handling of these matters in ICS perhaps?
Pretty annoying not being able to stream music over WiFi as I think I'll hit my 5GB limit on data pretty fast if I can't use the WiFi at work for this.
So has anyone else noticed these issues?
Click to expand...
Click to collapse
Yeah same here. I remember this being an issue with Android 2.1 for my Desire but was fixed in custom roms. Might be the same situation here again.
I remember this being an issue with my Nexus One, don't remember if it was fixed in 2.2 or 2.3. I remember testing file transfer using SwiFTP, with the bug the file transfer would go down to double digits (kB/sec), with the bug fix it would be a few hundred kB/sec, with the screen on it would hit mB/sec or so (in any Android version).
I believe this is the official issue:
http://code.google.com/p/android/issues/detail?id=9781
With my Nexus S I'm not experiencing this bug. Sscreen on still gives me a major wifi speed boost, but screen off I get a few hundred kB/sec, which should be more than enough for any streaming app. KiloBYTES btw, not bits. I'm surprised ICS and/or Galaxy Nexus brought this problem back. Or it could be something else entirely.
Are you connected via 2.4GHz or 5GHz wifi? I would think the new 5GHz radio in the GN probably has more aggressive power saving features. Try switching to 802.11b/g (instead of 802.11n, in any frequency), see if it helps.
Have you changed your WIFI sleep policy?
On my Froyo phone, if you hit menu while in the WIFI settings (I know there is no menu in ICS) you get an option to go into advanced settings where you have the option to choose your WiFi sleep policy (When screen turns off, never when plugged in, never).
There should be a way to access that advanced settings area somewhere.. My phone is a couple hundred miles away right now and I won't see it for another week so I can't be of much further help right now. However, there "was" a setting in previous versions.
best info at the time last year was here for the N1
http://www.google.com/support/forum/p/android/thread?tid=01a47ff5b0a92d52&hl=en
7xx replies there to read, but really good info. somewhere in there, maybe around#600 the info gets good, can't remember. But shortly around this time the problem was gone/fixed.
there was a guy with an app i think it was wifi fixer, i could be wrong. that worked sometimes, but battery drain was bad. Whatever google, or CM did fixed the low power save mode issue. I'm thinking it was something at the kernel level?
edit, on second thought, there's no good reason to read all that. You won't get a fix out of it anyway. It was updated away in the end, something related to MAC addresses and build numbers and frf50 or some such.
BUT this seems like the same kind of thing going on in the power save mode.
Have you checked your advanced settings?
Wi-Fi>>(settings [bottom right])>>Advanced>>Keep Wi-Fi on during sleep...
Mine was set to always by default, so I suspect that the issue lies else where...
Neville.Holland said:
Have you checked your advanced settings?
Wi-Fi>>(settings [bottom right])>>Advanced>>Keep Wi-Fi on during sleep...
Mine was set to always by default, so I suspect that the issue lies else where...
Click to expand...
Click to collapse
Same here. Mine was set to always by default but still getting this issue.
Sent from my Galaxy Nexus using XDA App
I would suggest that this issue is related to the individual applications you are using, rather than anything to do with Android.
I am able to stream music from Google Music via WiFi just fine when the screen is off, and I am also able to talk to someone on Skype via WiFi just fine when the screen is off.
oscillik said:
I would suggest that this issue is related to the individual applications you are using, rather than anything to do with Android.
I am able to stream music from Google Music via WiFi just fine when the screen is off, and I am also able to talk to someone on Skype via WiFi just fine when the screen is off.
Click to expand...
Click to collapse
Thanks for posting that; I was getting pretty worried and disappointed after reading this thread. I had to deal with this when I first got my Nexus One, until Google released the 2.2.1 update with a new Broadcom driver which finally fixed the issue. No streaming, no pushes, just nothing at all from wifi when the phone went to sleep. All traffic to/from the phone would just stop. It was maddening.
The Galaxy Nexus comes to Canada a week from today, and this would've been a show-stopper for me. At least it's working for you, so my day isn't ruined quite yet
Has this issue ever been nailed down? I've seen considerable discussion on it going back years. I've seen considerable speculation regarding WIFI mode and Governor. I've seem many of the bug reports marked closed.
Yet I have a GN on v4.0.4 and the moment the screen goes off - either because you turn it off or it just times out - the WIFI goes to h*ll. I've run ping and network trace from both sides and there is no doubt the WIFI stays connected, however latency goes way up and packets are lost... and with TCP connections it gets congested with retransmits. I've run with the governor set to "Performance" and there is no difference.
So, is there any consensus on what is causing this problem with current stock hardware/software?
I read that it's something that's been coded in for a while. Try using this:
https://play.google.com/store/apps/details?id=com.ratcash.wifiperf
-Sent via XDA Premium-
Ok, to answer my own question, this is still related to the PSP issue from years ago:
code.google.com/p/android/issues/detail?id=9781
code.google.com/p/android/issues/detail?id=15549
Bottom line is that some hardware - like GN - has an additional level of PSP on WIFI. The issue was resolved by inclusion of an additional lock mode - WIFI_MODE_FULL_HIGH_PERF - some time ago. However, its up to an application to request the new lock state if it thinks it needs it. Many don't.
So, its probably not a bad idea to contact developers of the various applications and recommend they look into the new lock level in the later APIs.
Also, the "WIFI High Performance Widget" can be used to manually hold a WIFI_MODE_FULL_HIGH_PERF lock on the WIFI if you're dealing with an application that isn't doing it its self. Beware of the other "WIFI fixes" out there, none of the ones I tested were acquiring the correct lock.
Also, from an adb shell you can use "dumpsys wifi" to see who is holding what lock, for example:
Code:
Locks acquired: 5 full, 5 full high perf, 5 scan
Locks released: 4 full, 4 full high perf, 5 scan
Locks held:
WifiLock{PANDORA type=1 [email protected]}
WifiLock{HighPerformance type=3 [email protected]}
Here you can see Pandora is only holding type=1 (WIFI_MODE_FULL) and HighPerformance is holding type=3 (WIFI_MODE_FULL_HIGH_PERF). Dumping the WIFI state takes the guess work out of it.
Tried that widget, having absolutely no luck with 'in tune' and 'winamp' for radio with the galaxy nexus verizon...
as soon as the device sleeps, wifi goes to hell and buffer drops in and out every 2 seconds. Completely unusable, any recent fixes? this is totally making me think I just bought a $400 brick since this feature was very important for me.
What may be confusing about that widget is that it is a "widget". You have to locate it under "widgets" and then put it on the surface and then click it to enable it... it should be blue when on, and black when its not.
tlum said:
What may be confusing about that widget is that it is a "widget". You have to locate it under "widgets" and then put it on the surface and then click it to enable it... it should be blue when on, and black when its not.
Click to expand...
Click to collapse
I have been trying to put the 'widget' itself (2x2 square) on the home screen but even if i hold and drag it to where I want it, it never actually appears on the screen. And of course i'm still getting crazy ping times...Does anyone else have this working on a GN (verizon - not that it should make a difference)?
I have found a few workarounds to this issue, none are great and frustrate me greatly.
1. Root and use the franco kernel. Seems people with that have no issues - since you can set? the wifi to full performance.
2. Use this wifi performance widget
3. Use an app that has properly set its own wifi settings. - Going through all the radio apps on the google market, i am finding only one app that seems to be doing this right: DI Radio - some kind of dance/techno/etc - confirmed it with ping times, they remain low on sleep.
Not one other radio app seems to have set 'proper' settings - which shows that something needs to be addressed in the os...I was having good luck with the yahoo music app, but depended on the stream (maybe some buffer more :dunno - the ping results are garbage.
EDIT: I tried installing high performance wifi again, and finally got the widget to one of the homescreens! Let me break it down for anyone else who comes across this. After install, the small 1x1 blue app box is put on your desktop and the black screen comes up with the wireless networks and a checkbox. I then went to apps->widgets and tried putting the 2x2 widget on the home screen again, and like always it clicks on like its there (and when you click home and its never there). However, this time I hit BACK instead of home after dropping the widget and it took me back to the black screen with the checkbox, then i hit home and voila its sitting there. You can click on it like you mentioned! Confirmed with ping for tune in...pings remain low.
If this continues to work, it may be a godsend. It is annoying having to have this, but far far better than not.
I had that problem also especially when i tried to download big files when the screen turn off the download speed became extremely slow, this widget solve this, i think to that moment its the easiest solution tap it when you need it tap it again when you done.
By the way i had this problems with franko kernel also and again to my opinion it is the good solution for now, until the apps developers update their apps.
Sent from my Galaxy Nexus using XDA
If you download the SDK - you only need Android SDK Platform-tools - to a PC and use the adb shell it is easy to dump the WiFi lock state with dumpsys wifi and see exactly which app(s) are holding what locks. Completely takes all of the guessing out of who is doing what when. Judging the behavior can be subjective because there are other reasons that the WiFi can break up which can be very frustrating.
developer.android.com/guide/developing/tools/adb.html
Erlang2012 said:
I had that problem also especially when i tried to download big files when the screen turn off the download speed became extremely slow, this widget solve this, i think to that moment its the easiest solution tap it when you need it tap it again when you done.
By the way i had this problems with franko kernel also and again to my opinion it is the good solution for now, until the apps developers update their apps.
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
The app does work well, however I have been running into some issues as I continue to use it. It randomly decides to turn off the forced max wifi (even though its still blue and looks like its operating) or perhaps the phone is forcing the wifi issue again. It seems to happen when you are downloading, playing with some other apps? You only notice it when you sleep it and the streaming radio immediately starts having issues.
Solution is to flip back to the widget turn it off and turn it on again. It works, but is another annoyance.
I haven't yet ascertained exactly what causes it to switch off yet.
tlum said:
If you download the SDK - you only need Android SDK Platform-tools - to a PC and use the adb shell it is easy to dump the WiFi lock state with dumpsys wifi and see exactly which app(s) are holding what locks. Completely takes all of the guessing out of who is doing what when. Judging the behavior can be subjective because there are other reasons that the WiFi can break up which can be very frustrating.
developer.android.com/guide/developing/tools/adb.html
Click to expand...
Click to collapse
I will look into this, thank you.
---------- Post added at 06:16 PM ---------- Previous post was at 05:28 PM ----------
I used the adb shell (learned how to install all these dev tools and how to use it first ) and here is some updated info:
Tunein = type=1
Pandora = type=1
Audioaddict service (Digitally imported app I posted above previously) = type=3
google music = type=3
High performance app = type=3 (havent figured out why this likes to stop randomly)
I will update with more app info, hopefully others can also email the developers and see that it gets fixed, so we no longer have to use damn workarounds...
jeep364 said:
... It randomly decides to turn off the forced max wifi (even though its still blue and looks like its operating)...
Click to expand...
Click to collapse
Yes, it definitely has an issue holding its lock, and it definitely seems related to another application taking over and also when it switches to cell and back, I can confirm that. It may be related to the OS since the widget thinks it still on when clearly the lock as been released, so it may be that the OS released the lock and the widget has no idea. I haven't taken the time to look into the details yet, and this is something we should make the developer aware of.
tlum said:
Yes, it definitely has an issue holding its lock, and it definitely seems related to another application taking over and also when it switches to cell and back, I can confirm that. It may be related to the OS since the widget thinks it still on when clearly the lock as been released, so it may be that the OS released the lock and the widget has no idea. I haven't taken the time to look into the details yet, and this is something we should make the developer aware of.
Click to expand...
Click to collapse
Yup, from what I can see it loses lock:
1. when cell switching
2. manually killing/starting wifi
3. when ANY application is downloaded/removed (ie. changes in permissions)
4. when playing with dolphin, other apps for more than a few minutes, it will kill it even though the blue stays lit. I think its as you mentioned, during general use of the phone, at some point some permissions are changed and hifi performance is tossed off its lock.
If you only are streaming music and re enter the phone to check a gmail alert or two...it seems to be fine. otherwise you need to hit the lock widget one more time before sending it to sleep with pandora/tune in playing.
Related
I'm seeing many users notice different little bugs with the phone (me included) and instead of having multiple threads about it, maybe we can all post it in one place where later the devs can see it and work on them once the phone is rooted etc.. Good idea/bad idea? I come from an Evo 4g with Sense rom so I wonder how many of these might not really be "bugs" but just a different user experience.
I'll start..
Accu weather app not updating location automatically
apk files downloaded from the computer and then transferred to phone are not showing up (unknown sources, usb debugging checked)
No function when touching the clock widget. It does not launch me to alarm, world clock, time etc menu. Maybe this is just a touchwiz thing as I mentioned above, I come from a sense rom.
So far those are the ones on top of my head. As I use the phone more, I'm sure I'll spot more (hope not!).
Anyone else?
Phone dialer issues
I have to reboot my phone from time to time to make a call.
It just says call ended when i try to call out.
When i reboot it works fine for a few hours.
Mentioned above plus the following so far (except reboot for calling issue):
No landscape mode using TW (auto-rotate enabled)
Red LED only available notification color (REALLY?!)
Skype video calling is upside down when using in portrait mode.
Also, phone call is automatically in Speaker mode when calling after making a Skype video call.
*Occasional phone FREEZES. As in, one minute it is okay, and the next minute, you have to do a battery pull. Happened twice since I got it on launch day.
*Browser closing for no reason. Happened 4 times since launch day.
*When plugged in with Samsung charger, phone's screen will act real glitchy
*SWYPE does not work properly, no matter the settings. Have to type normally.
That's all the software bugs I've experienced. Hardware-wise, there are reports of problems with data, 3G, 4G, and WIFI....I haven't seen any word on Bluetooth yet.
Journeyjeans said:
*Occasional phone FREEZES. As in, one minute it is okay, and the next minute, you have to do a battery pull. Happened twice since I got it on launch day.
*Browser closing for no reason. Happened 4 times since launch day.
*When plugged in with Samsung charger, phone's screen will act real glitchy
*SWYPE does not work properly, no matter the settings. Have to type normally.
That's all the software bugs I've experienced. Hardware-wise, there are reports of problems with data, 3G, 4G, and WIFI....I haven't seen any word on Bluetooth yet.
Click to expand...
Click to collapse
Go exchange your phone -- sounds like a lemon. No other real complaints about freezing or auto-closing apps.
Erislover said:
Go exchange your phone -- sounds like a lemon. No other real complaints about freezing or auto-closing apps.
Click to expand...
Click to collapse
Actually, other's have experienced auto-closing apps and freezing. It's in a thread around here or at sprintusers.com, I forget which.
For the first three days I couldn't get data while roaming though the proper settings were checked. Sprint customer care reset my phone and after an hour of waiting it works.
All else its great (except for the above oddities with Touch Wiz) though I haven't checked GPS after encrypting the device.
Sent from my SPH-D710 using XDA App
humdrum2009 said:
I have to reboot my phone from time to time to make a call.
It just says call ended when i try to call out.
When i reboot it works fine for a few hours.
Click to expand...
Click to collapse
Can you elaborate on this issue?
Also, anyone else having similar issues, please chime in.
Are you seeing a circle with a slash through it (no service) when this happens?
Can you receive calls when this happens?
Do you lose 4G or WiFi? Or is it just Voice/3G?
Does it seem to happen sometime after making a call/text (~30min), or any other pattern you've noticed?
Are you rooted?
If yes, what kernel (zedomax or tanimn/shabbypenguin - trying to narrow down an issue with one of the current root kernels)?
Exchange Appt. Notification Bug
I have had multiple reminders pop up for from my Exchange calendar and i can't seem to dismiss or snooze them from the notification bar. The snooze and dismiss buttons are available but are non responsive. The only way I can get rid of the notification is with the "Clear" button which is for all notifications. Has anyone else noticed this?
Journeyjeans said:
*SWYPE does not work properly, no matter the settings. Have to type normally.
Click to expand...
Click to collapse
I know this may sound silly, and you may have already checked this, but check your language settings. I've read about some owners that were having problems with Swype discovered that their language was set to Spanish.
Also, on the LED notifications only being Red, I've been playing with an App called Light Flow. I've at least been able to change the notification colors to Blue using this App. Also, the App lets you use "White" as a color, which still shows a Red light, but blinks very fast if some of you prefer a faster blinking light.
I have had the roaming data issue as well. It does eventually work for me though, but on once occasion it took 10 minutes before data turned on after the roaming started. I will try calling Sprint as well.
Wifi signal is bad.. but speedtest says otherwise. I think the issue is with the amount of bars displayed and not the actual signal. I was standing 5 fee fromt he router and still didn't have full bars.
Ive been having problems today with dropping data connection. Toggling 4G off and on seems to restore it even in no 4G areas. I guess it resets the radio or something?
MadFlava said:
Ive been having problems today with dropping data connection. Toggling 4G off and on seems to restore it even in no 4G areas. I guess it resets the radio or something?
Click to expand...
Click to collapse
Try profile and prl update...
My data did cut in and out till i did the normal sprint updates
Sent from my SPH-D710 using XDA App
Just got this phone friday. So far the only bugs I am experiencing are roaming in places my evo got coverage and the security draw pattern having a mind of its own making it very hard to unlock the screen. Also the wifi reception is noticeably weaker than my evo
nate420 said:
Try profile and prl update...
My data did cut in and out till i did the normal sprint updates
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
Ive done that already and it didnt help. Thanks, tho.
Luckily, no freezes or crashes here (knock on wood).
what i HAVE noticed is the rotate bug, for instance
when rotating the phone for texting or browsing, you have to kind of
bring it up to your chest @ about a 90 degree angle in order for it to rotate.
calibrated it all correctly & i still have to do that.
this is my first phone from the Epic/Galaxy company so im not sure if that was a problem in the original Epic 4g (non-touch) but it sure is kind of annoying :/
hopefully the dev's can tweak the gyro or SOMETHING.
Poor Wifi/3g Signal
Noticed lower bars on both wifi and 3g...when in same spot on my Evo 4g I had more...might be just how many bars its displaying and not the actual signal...but not for sure...actually went into roaming a few times when with my Evo 4g I never did (even with roaming was set to automatic...now I have it set to sprint only)
Hello. Has anyone tried updating through Kies? I tried and it says that this version of software cannot be updated. I just got my phone today. I did have problems installing the drivers. After I let it install say one or two drivers, one would error out. Once I unplugged it a few times and then plugged it back it, all of the drivers installed.
I hope this doesn't mean that Samsung is not going to upgrade to ICS or else I am taking this back. I have a Samsung Galaxy Tab 7" and it won't allow updating with rooting. Thanks for any input and have a great day/night!
analyst28 said:
I have had multiple reminders pop up for from my Exchange calendar and i can't seem to dismiss or snooze them from the notification bar. The snooze and dismiss buttons are available but are non responsive. The only way I can get rid of the notification is with the "Clear" button which is for all notifications. Has anyone else noticed this?
Click to expand...
Click to collapse
I noticed this too.
you have to check the check boxes next to the calender item. This is deceptive because the boxes have checks in them. But they should be green and not grey.
hope that helps
Problem summary
Known cause (might be others): selecting an app from the Recents list (Task Switcher)
Temporary fix: turn the screen off, then back on
Workaround: avoid using Recents list (you can use a 3rd party task switcher instead)
How to test: open Messaging, hit Home, hit Recents, select Messaging from the list. Your screen will be less sensitive until you turn the screen off and back on. You can view the pressure by going to Settings -> Developer Options -> turn on Pointer Location. This will allow you to see the Prs of each tap in your status bar. Normally your lightest taps that register will show anywhere from 0.28 to 0.32. However, after this bug is activated, you will mostly get values over 0.40 for your light taps. This is actually a very noticeable increase, especially when trying to type quickly.
Please report any other known methods to "activate" this bug. After re-assigning my Recents button to a 3rd party app (I'm using Simple Task Switcher), I haven't seen this bug at all. It seems that a couple of people have seen it produced by something other than Recents, but they haven't narrowed it down (or reliably reproduced it on purpose).
Please star this issue officially so Google can fix:
Link is http://code.google.com/p/android/issues/detail?id=29734
Note: Downloading & using Screen filter application from play store, with brightness set to
Your hands are really dirty or really dry. Try moisturizer or something.
Been using my screen for almost hour straight now. No issues.
--------+++--------
iphone. helping computer illiteracy become popular since 2007.
Hehe yes this s gonna be a difficult one to confirm. But it is definitely not dirty hands. To clarify, a quick press of the power button to lock then unlock completely fixes the issue. Same fingers suddenly register perfectly. This is driving me nuts as the phone is not even usable right now. Literally.
@rbiter said:
Been using my screen for almost hour straight now. No issues.
--------+++--------
iphone. helping computer illiteracy become popular since 2007.
Click to expand...
Click to collapse
ios 6.2 doesnt get issues.
I don't know about your other experiences, but as far as the browser goes I have the same scrolling effects as you do. I think this is how it is meant to be. They tightened the scrolling a lot and I kinda like it. Before one small flick would send me across the whole page, which was kinda annoying. Just my preference.
I'm not having this problem. It would drive me crazy too. Been using my phone alot over the past two days and I didn't run into this problem even after almost 1h of continuous surfing. Also a few checkpoints of Shadowgun didn't trigger it.
But you can confirm your problem if you enable "cursor position" in the dev options (hope that's what it 's called in english). "Prs" and "Size" should need a lot more than around 0.30-0.40 to register your touch if you have the problem you describe.
I am sorry that you're experiencing this, but 4.0.4 has nothing to do with this. 4.0.4 is just software, Galaxy Nexus is not a pressure-sensitive device, it is merely touch-sensitive. Which means that software gets an analogue signal from the touchscreen, either 1 or 0. It has no 'range' of sensitivity, so it cannot decrease in sensitivity in software (if it did, then it would not work at all).
This is entirely hardware issue and I suggest either making sure your screen is clean, your screen protection thing (if you use one) isn't acting up or if your hardware has become faulty (have you dropped it recently?).
If problem persists then return under warranty.
My wife had this issue once.
It was the third party launcher she was using.
I don't think its a matter of touch sensitivity dropping, its a matter of the system just being too slow to really work right.
It was ADW EX, fwiw.
kristovaher said:
I am sorry that you're experiencing this, but 4.0.4 has nothing to do with this. 4.0.4 is just software, Galaxy Nexus is not a pressure-sensitive device, it is merely touch-sensitive. Which means that software gets an analogue signal from the touchscreen, either 1 or 0. It has no 'range' of sensitivity, so it cannot decrease in sensitivity in software (if it did, then it would not work at all).
This is entirely hardware issue and I suggest either making sure your screen is clean, your screen protection thing (if you use one) isn't acting up or if your hardware has become faulty (have you dropped it recently?).
If problem persists then return under warranty.
Click to expand...
Click to collapse
Lol that is hilarious. You forgot the step where its the OS that actually processes the input data, so in that process, a ton of problems can arise.
And personally, since 4.0.4 I have also been experiencing a "similar" issue. When scrolling down (and only down), I experience a kind of "lag" like if it only registers the swipe movement half an inch lower. Its not a big deal, but still an issue.
Edit : What he explains as "pressing very hard" is most likely the fact that when you press harder you actually cover more surface, so the amount of extra input data can definitely impact the behavior.
I had issues for a few hours after the 4.0.4 update, where my softkey buttons weren't responding. Thankfully, it seems to be fine now, but it was a cause for concern.
Sent from my Galaxy Nexus
gokpog said:
I'm not having this problem. It would drive me crazy too. Been using my phone alot over the past two days and I didn't run into this problem even after almost 1h of continuous surfing. Also a few checkpoints of Shadowgun didn't trigger it.
But you can confirm your problem if you enable "cursor position" in the dev options (hope that's what it 's called in english). "Prs" and "Size" should need a lot more than around 0.30-0.40 to register your touch if you have the problem you describe.
Click to expand...
Click to collapse
Thank you my friend, I should have thought of this; now I have numbers to confirm this. So with cursor option enabled I can get down to 0.30, managed 0.28 once. However when the bug starts, I can confirm that I cannot get below 0.60. It just refuses to register that input for some reason.
I lock the screen, 1 second is all it takes, and now it registers down to 0.30 again and all touch works properly. Its almost like some type of memory leak issue is the way it feels to me. It only starts happening after a few min of use.
Its definitely an issue now that I can see the pressure numbers. The question is what the hell can I do about it. I flashed aokp29 with the latest 4.0.4 ota merged in, problem still occurs. I'm gonna try stock 4.0.2 or 4.0.1 just to see. Thanks.
I have never had much luck upgrading Linux versions. That's why I start fresh every time with Android. Lol
Sent from my Galaxy Nexus using Tapatalk
Before I start digging, anyone know specifically which driver controls the touch input? I'll try looking thru github.
Also I was on stock 4.0.1 prior to this. So this could be normal behavior for everyone but everybody is used to it since nobody stayed on 4.0.1 like me. Cause I can easily say this is difficult to notice if you aren't paying attention. The question is, why does locking the screen temporarily change it back...
I can confirm some of what you are saying..sometimes when I'm browsing the scrolling tightens up..I lock the phone then unlock it and it is smooth again..doesn't happen all the time tho..doesn't bother me but I've noticed it
Sent from my Galaxy Nexus using XDA
I can also confirm. This morning I found the Swiftkey was lagging on Facebook. Something like the phone did not receive the touch. Then I rebooted and now it is ok.
I did not get this issue on 4.0.2 and I don't install anything new on 4.0.4.
The way I installed 4.0.4 was from the official factory image, so my phone is fresh! I reinstalled all apps manually as well. Nothing fancy apps.
I know this is my first post, but I can definitely confirm this issue.
I use my Galaxy Nexus for development, so the screen is always on. The sensitivity goes down very quickly.
My phone was an International GNEX that I loaded the US firmware on and then I flashed the OTA 4.0.4 update.
kristovaher said:
I am sorry that you're experiencing this, but 4.0.4 has nothing to do with this. 4.0.4 is just software, Galaxy Nexus is not a pressure-sensitive device, it is merely touch-sensitive. Which means that software gets an analogue signal from the touchscreen, either 1 or 0. It has no 'range' of sensitivity, so it cannot decrease in sensitivity in software (if it did, then it would not work at all).
This is entirely hardware issue and I suggest either making sure your screen is clean, your screen protection thing (if you use one) isn't acting up or if your hardware has become faulty (have you dropped it recently?).
If problem persists then return under warranty.
Click to expand...
Click to collapse
Just to point out, the phone is all digital. It does not get an analog signal from touching the screen. Also to that point you said analog but then described digital with the 1 and 0
Has anyone affected tried going between 4.0.2 and 4.0.4? To check the possibility of a driver or some related value changing.
Also, if not fixed by going back to 4.0.2, this could be due to current leakage from somewhere causing the touch to not work properly. I've seen it on other capacitive touch devices, though mainly when a non-compatible charger is connected. When you shut the screen off, the charge causing the problem/interference with the touch is temporarily dissapated, but then comes back after you use it again. Probably very unlikely in this case, unless Google changed something in the touch driver that makes it more sensitive to interference, which in turn messes with actual input from fingers.
TechNoir said:
Has anyone affected tried going between 4.0.2 and 4.0.4? To check the possibility of a driver or some related value changing.
Also, if not fixed by going back to 4.0.2, this could be due to current leakage from somewhere causing the touch to not work properly. I've seen it on other capacitive touch devices, though mainly when a non-compatible charger is connected. When you shut the screen off, the charge causing the problem/interference with the touch is temporarily dissapated, but then comes back after you use it again. Probably very unlikely in this case, unless Google changed something in the touch driver that makes it more sensitive to interference, which in turn messes with actual input from fingers.
Click to expand...
Click to collapse
Its possible. I was on 4.0.1 so perhaps this issue originated in 4.0.2 but I never noticed since I didn't update then. I can add that I did multiple wipes and clean flashes, and also tried both aokp 28 and 29 (new 4.0.4 ota merged), and happened on both.
I'll post what I just sent to arbiter which gives more insight.
From my extra testing under normal use my light touches register 0.28-0.33. Especially on swipes, the end of the swipe registers 0.28 as the finger travel breaks contact with the screen giving that swipe extra input which pushes the swipe motion further extra boost. When the bug starts the touch swipe won't even break 0.38-0.40, and that extra swipe data is lost resulting in the end of the swipe data points being excluded and swipes travel half the distance.
This gets exacerbated on the keyboard when fast typing light pressed. Its so bad it frustrates my face off cause typing just ceases to be possible. Such a difficult issue to diagnose.
Click to expand...
Click to collapse
Yes my face literally flew off!
Just wanted to start a thread to discuss this device. For those not familiar with it, it's a very inexpensive 11.6" laptop that runs RemixOS 2.0 from the factory. It does NOT have a touchscreen and the display is a low resolution (1366x768) TN panel display. The CPU is an Allwinner A64 Cortex A53 quad-core 64-bit processor.
The device I purchased (via their Kickstarter campaign) has 2gb RAM and 32gb storage - and it costs me $89.
Some interesting things I've found so far...
1. To disable the damn "click" sound every time you select something (via the touchpad or a mouse), download the QuickShortcutMaker application from the play store. Then expand the Settings items under the Activities section and find the "Other Sounds" activity. Once you click on the Other Sounds activity, click on "Try" on the right-hand side - this will open the "Other Sounds" dialog where you disable "Touch Sounds"! You can also disable some other sounds here. No idea why Remix doesn't allow access to these sound options. Explore the other Settings activities - there are some other cool things you can do. I also used this app to create "Shortcuts" to specific forums in Tapatalk (something that you do via widgets in standard Android). This QuickShortcutMaker app is pretty damn useful on this device!
2. I've found that I was able to connect my Apple USB->Ethernet adapter to this device and it works! However, it doesn't seem to work with ALL apps. For example, Tapatalk doesn't work with it for some reason - but so far, every other app has worked. You can also access ethernet settings via the QuickShortcutMaker app mentioned above.
3. Enable "Experimental Features" by clicking on the "Kernel Version" section of Settings->About. Once you do this, enable the "Use mouse wheel to simulate swipe gesture". This allows you to zoom in and out of things like web pages, images, etc. To do this, hold down CTRL+ALT while moving the mouse wheel. Apparently, the touchpad on this device does NOT provide pinch-to-zoom functionality, so without this setting, there is no way to zoom in and out in most apps! Kind of a big issue! Unless there is another way that I just don't know about. I know you can CTRL- and CTRL+ to zoom in and out in web pages, but that really just increases the size of the text - not really a true zoom in/out.
4. Gmail app. If you open the Gmail app as a window, you don't get the "split-screen" that you get if you open the app in full screen. But if you open in as a full-screen window and then "restore" it to a smaller window, the split-sceen function still works. I usually just leave Gmail minimized in order to keep the split-screen function active for Gmail.
5. Sometimes, the screen comes back on if you put the device into standby with the power button and then close the lid. I haven't been able to find the exact circumstances where the screen comes back on when closed, but it seems that when it does come on when it's closed, it stays on! Need to figure out why this occurs..
6. Bottom of device gets REALLY hot after any extended use. May be a long-term issue...
7. By default, wifi is set to turn off when in standby (unlike tablets) - unless the device is plugged in - then wifi will stay on. This can all be changed under Settings->Wifi->Advanced. I actually set mine to always turn wifi off when in standby since it seems that the device doesn't actually work while in standby anyway (again, unlike tablets). May help avoid wifi failure over the long-term.
8. I have run into websites (such as microcenter.com) where when you open a drop-down list, there is no way to "scroll" the list if it goes off the screen. To see what I mean, go to microcenter.com and try to set the store location - it opens a drop-down list that goes off the screen and there is no way to scroll down in the list! The "work-around" is to use the down arrow key, but it doesn't work very well (web page wants to update every time you press the down arrow)....
That's about it off the top of my head... It's a shame that this device cannot upgrade to RemixOS 3.0, like was stated in the kickstarted campaign (and later "retracted").
Anyone know how to root this thing?
It's an interesting device for the cost, but what I *really* want is a similar, large'ish device with a higher-quality, higher-resolution touchscreen that is removable from the keyboard - with at least 2gb of RAM (10" and 1gb of RAM isn't enough for RemixOS!) and runs RemixOS 3.0 - so far, I can't seem to find such a device...
Sent from my A1160 using Tapatalk
I got the same model 2GB w/32GB storage. Do you or anyone know how to get it to charge and or power on. Mine only worked for 2 days, now nothing. I contacted Azpen over a week ago about it and still haven't heard from them. Please help.
Cerealius said:
I got the same model 2GB w/32GB storage. Do you or anyone know how to get it to charge and or power on. Mine only worked for 2 days, now nothing. I contacted Azpen over a week ago about it and still haven't heard from them. Please help.
Click to expand...
Click to collapse
I just plugged mine in and it charged fine (blue LED next to charging port turns on when charging and turns off when fully charged).
To turn mine on, I just held down the power button on the keyboard for a while... You can also fully power it off that way as well (if it gets hung or something, which I have managed to do a few times now).
I've *really* put this thing through it's paces over the last few days. Overall, it's a decent device for the price. Personally, I'd rather spend a little more for one with a better, higher-res, removable touchscreen though.
I also have a HP Slatebook 10 x2 - and it's a great device, but stuck on Android 4. Otherwise, it has a MUCH nicer, removable touchscreen and even an extra battery in the keyboard (that charges the tablet when attached). Just wish it was a little bigger (13" or so) and was running Remix OS.
But, for $89, I can't complain, my A1160 actually runs pretty well for what it is...Luckily, I haven't had any issues with mine.
Sent from my HP SlateBook 10 x2 PC using Tapatalk
Hello...
@jtrosky, thanks for starting this thread, i've already gotten something out of it... getting rid of that damn clicking every keypress.
It was also nice to find that quickshortcutmaker, thats really a cool app that seems to allow more access than I could find...
Everyone else, hello!
I am an PC user since 84' and an Apple iPad user since, well the day the ipad 2 came out and now I'm on the iPad now. The only reason I say any of this is because the reason I got this Azpen A1160 was to help learn a bit about android and linux. I would also like to figure out how to get to the root...
Knock on wood but I got this three days ago and have literally beaten the software out of it loading, looking, deleting, and I thought I had screwed it up several times but it just keeps on ticking. The back does get a little warm, I haven't actually measured it yet but I'm going to, but I dont think it's too bad. I've run six full charges on battery and worked on it plugged in. (which it doesn't seem to like)
I'm happy with it right now and I think its going be a fun ride. I bet this is going to be a fun place to be in the next couple of months...
Buddy
Oh - one more thing I found out - and this may be well known already for those more familiar with RemixOS. If you click and hold on the little icons on the bottom-right of the taskbar, you can move them around. So, for example, you can make it so the brightness, volume, bluetooth and wifi icons are always visible, even when that section is "collapsed"...
Also - I *love* having the key to disable the touchpad (the key next to the arrow keys). Since I usually use a bluetooth mouse, it's so nice being able to disable the trackpad so quickly and easily!
Oh - and the Prtscr button on the keyboard brings up the very cool screen capture tool, which let's you select what area of the screen to capture. Very handy tool!
Still not sure what the "Pausc" button does - I'm assuming it's actually a misprint and it's supposed to say "Pause". Gotta love cheap electronics that are made in China!
So far, this device is definitely working well for me. Although, I'm not so sure the screen is big enough to truly take advantage of the RemixOS windowing capabilities... But, it's still better than not having any windowing capabilities.
Sent from my A1160 using Tapatalk
One more quick tip - there are apps out there that will let you boost the volume of the device. Right now, I'm using Music Volume EQ to boost the volume, but there are probably better apps out there for this purpose... Will explore more later and post an update if I find a better app.
Sent from my A1160 using Tapatalk
Hello guys, thank you for creating this thread.
Did anyone have any issue by setting up a password for the lock screen?
I did, and it worked for a couple of times, then it started not to recognize the password (password was correct, no caps lock...). Of course it didn't work after reboot as well.
The only option was to remotely reset the device using the google's tool from another pc. Very annoying. Since then never tried to set another security system for the screen lock.
I'm also getting an a problem after turning off the screen: when I try to turn it on again, most of the time I get a blank screen. I have to try several times to get back to remix os.
Did anyone faced this issue as well?
Regards
sephitoor said:
Hello guys, thank you for creating this thread.
Did anyone have any issue by setting up a password for the lock screen?
I did, and it worked for a couple of times, then it started not to recognize the password (password was correct, no caps lock...). Of course it didn't work after reboot as well.
The only option was to remotely reset the device using the google's tool from another pc. Very annoying. Since then never tried to set another security system for the screen lock.
I'm also getting an a problem after turning off the screen: when I try to turn it on again, most of the time I get a blank screen. I have to try several times to get back to remix os.
Did anyone faced this issue as well?
Regards
Click to expand...
Click to collapse
I have not tried setting up the lock screen (I just leave mine unlocked). And no, I have not had any issues with a blank screen when turning the device back up. What's strange is that the device does not automatically turn on when opening the screen - at least not on my device - I have to press the power button.
Your issues are probably because of the poor quality control with these device. Somehow, I lucked out and got a "good one", but many people seem to be having build-quality issues with them...
Sent from my A1160 using Tapatalk
Great posts and many thanks to the OP.
I got a US 2 pin power plug instead of a UK plug. Does anyone know of a similar products power lead that will fit our A1160?
Need help...
Hi,
First, thanks for creating this thread and posting your tips. Obviously there are not a lot of people using this device yet so it is great to find useful info on it.
Since there is no known root solution yet, I tried installing NetGuard as an adbllocking solution that does not require root. I have used it before without any issues. Unfortunately, on the Azpen, every time that I enable it, it blocks all internet access (it is obviously not supposed to do that). I even tried alternative apps like AdClear and got the exact same result. There is something strange going on with the Azpen. I would really appreciate it if anyone had any pointers as to how I could resolve this.
Thanks...
Welp! I had much higher hopes for this device and I haven't even received mine yet! Will this be rootable?
Thanks for creating this, used both your sound clicking tip and the pinch to zoom in. A bit annoying having your fingers in multiple place to zoom in, but what can you do? I'm a college student and have found that I can't access the net with this device due to it's mac address changing each time. I'm not sure if anyone else has noticed this or if mine is the only one. Just thought I would share that.
HyugaSho said:
Thanks for creating this, used both your sound clicking tip and the pinch to zoom in. A bit annoying having your fingers in multiple place to zoom in, but what can you do? I'm a college student and have found that I can't access the net with this device due to it's mac address changing each time. I'm not sure if anyone else has noticed this or if mine is the only one. Just thought I would share that.
Click to expand...
Click to collapse
That is *really* interesting! Sure enough, if I disable and re-enable the wifi, the MAC address does change!! That makes absolutely no sense - I've never seen such a thing!
I'll look into that a little more - but without root, I doubt there is anything that can be done about it. So strange!
One possible option - set wifi to stay enabled all of the time - maybe that way the MAC will stay the same. You can set that in the wifi settings advanced options. I've found that you have to reboot after setting it to always stay active....
Sent from my A1160 using Tapatalk
So far I have been impressed for the cost of this unit. I have a few concerns and wanted to see if anyone had input:
1. Since the length of the power chord is so short. Is it possible to use a USB to Barrel jack type of adapter to power this? That way you can attach to a portable power bank?
2. battery power, I find it to not last that long and I find it takes forever to charge. I thought that this would last 5-7 hours unplugged, nope. It was supposed to charge within in a hour, nope. Any ideas on this?
I use an external mouse and click on the trackpad disable button. I find it much easier to use the computer when typing.
I'm looking at Pinebook, a notebook having the same AllWinner processor (CortexA53).
It seems this notebook can run all OSs suppoted by Pine64, such as Android, some linux distro, Windows IOT and they are working on a Chroimum porting (try to have a look at the pin64 forum).
Do you think it would be possible to do the same with A1160 ?
Another solution could be PhoenixOs (as pointed out in some comment on Kickstarter).
There are already some devices with CortexA53 processor running PhoenixOS out of the box.
I honestly don't know what OS's can be ported over to this device yet. I have a feeling that it's never going to have a huge user base though, so I wouldn't expect much from the developers out there.
Now that Chromebooks can run Android apps, this device just isn't quite as interesting as it once was. Basically, you can now get an inexpensive, *high quality* Chromebook and still have most of the advantages of this device, plus the high quality and frequent updates part.
To be completely honest, I have very low expectations for this device in the long-term. With how hot it gets after any real usage, I expect the mainboard to fail in short order. We'll see. Although, so far, I've really been using it pretty heavily and it does seem to be holding up, but it's only been about a week....
Sent from my A1160 using Tapatalk
Something else I recently noticed - and this may already be a well-known thing with RemixOS... If you close an app by clicking the back arrow on the top-left of the window, you continue to get notifications for that app. But if you close it by clicking the "X" in the top-right of the window, it seems to completely the kill the process and you no longer receive notifications (or if it's an app that stays around and puts a "permanent" notification in the notification tray, the "x" seems to completely stop the app as well and removes its notification item).
At least that's what seems to happen...
Also noticed that even if you setup wifi to stay active even with power off, the unit eventually goes into a "deep sleep" where you will no longer get new email notifications, etc. It even seems to turn wifi off after a while (even though it's set to stay on all of the time).
Lastly, if you have an external mouse connected, close the laptop lid and then move the mouse, it turns the screen back on - even while closed!
Sent from my A1160 using Tapatalk
Hi All,
Saw this in the comments and thought I would chip in with my experience so far.
I got the 64GB version and so far it is the computer I have paid for.
The track pad as everyone said is very crappy, but I just use an external mouse instead so its not a big problem.
I seem to have a good unit and don't have any problems with the unit.
My only gripe is that the battery kinda sucks and after using it intensive for like 3-4 hrs, it will have almost no battery. I wish it came with my UK adapter instead of the US one, but its okay.
Furthermore, is there anyway to put widgets on it? or Use another launcher?
Has anyone tried to root it or tried to install another OS on top of it? I heard that PhoenixOs is possible?
MindlessManiacs said:
Hi All,
The track pad as everyone said is very crappy, but I just use an external mouse instead so its not a big problem.
Furthermore, is there anyway to put widgets on it? or Use another launcher?
Has anyone tried to root it or tried to install another OS on top of it? I heard that PhoenixOs is possible?
Click to expand...
Click to collapse
For what it's worth, my trackpad actually works really well. I was surprised to read all of the complaints about it. I'm guessing that a lot of them are defective?
Regarding the widgets, no - there is no way to use Widgets in Remix OS 2.0 (not sure about 3.0), which is a huge limitation. Widgets are one of the things that make Android so powerful - and I miss them big time in Remix OS...
I too would like to know if there is a way to load PhoenixOS on this device. I thought I saw it mentioned somewhere that it would be possible (maybe one of the updates on Kickstarter?). I will see if I can email Azpen about this. RemixOS 2.0 is really good, but not quite "finished" in my opinion...
Sent from my A1160 using Tapatalk
Hi! Does somebody receive a blank white screen when laptop booting or waking up?
Every time when I push power button I get a blank white screen... How I can fix it?
Hi everyone,
I have 2 Galaxy S8+ from Verizon and here are my issues:
Past issues:
One of them did not come with the Galaxy Apps store (Not the plays store), and that phone also experienced the DQA issue
Current issues:
If I turn on Fingerprint gestures, the fingerprint sensor will stop working, this was an issue I had from the day I got the phone and has continued even through the updates. Here's a thread I made about it a while ago : https://forum.xda-developers.com/galaxy-s8+/help/fingerprint-sensor-t3595614
My internal speaker has detached, or at least I think that is the issue, as sometimes when I am in a phone call and shake the phone just a little bit, it will either start making a weird buzz sound or completely cut off the sound. Shaking it again will fix it, that's why I think it's a physical issue. I haven't dropped my phone and just in case I ever do, I have a case and a screen protector on it, and neither of them (phone, case, screen protector) have any damage marks on them.
The Biggest Issue: Currently this is the most annoying bug I am experiencing is that whenever I go to lock screen and security in the setting app, it crashes the settings app. I also can't use the search function in the settings app, as it crashes the app withing a few seconds. The lock screen and security is the only menu in which I experience this, I am 99% sure this is due to me turning on Secure startup. I had it turned on a few days after I got the phone and it worked great, I had to turn it off once, about a month ago in order to get a quicker boot. After that I was experiencing issues turning it back on (meaning I turned it on, rebooted the phone and it would not work) , after some persistence, I was able to get it to work and it has worked and still works.
One thing to mention is that I had done the most recent system update, I am not sure this issue was caused by at, since the inability so search in the setting menu has happened prior to the latest update.
I have tried everything other than a full factory reset (wiping all cache, wiping apps cache, reset setting, reset network settings), which I refuse to do, It is absolutely unacceptable for me to pay this much for this phone and have so many issues with it, I have factory resetted my phone (Samsung's recommendation) in order to fix the first issue listed above, multiple times and it did not work.
At this point I really don't know what to do, Samsung support has been useless in this, I don't wish to replace my phone right now as I need it to much to even give up for one day, If anyone has any advice/fix other than factory resetting, I'll happily try it.
Thank you,
GGgamer16
Sounds like a factory reset is needed. I just tried all you mentioned with zero problems on the newest update w/ navbar options and experienced none of that. Speaker problem is most likely hardware related.
Anyone had any luck getting rid of the wifi disconnect? The issue where wifi disconnects showing a ! next to the wifi symbol on the status bar?
*Hooligan* said:
Anyone had any luck getting rid of the wifi disconnect? The issue where wifi disconnects showing a ! next to the wifi symbol on the status bar?
Click to expand...
Click to collapse
You try changing your WiFi channel? Using 5ghz or 2.5ghz? I use Wifi 100% of the time I'm home and never have any issues with disconnects.
brandonc0526 said:
You try changing your WiFi channel? Using 5ghz or 2.5ghz? I use Wifi 100% of the time I'm home and never have any issues with disconnects.
Click to expand...
Click to collapse
Yeah I have tried changing channels. It didn't matter. I'm on 2.4 GHz.
I found a possible fix from another forum. I changed my wifi encryption from wpa2 AES/tkip to wpa2 tkip only last night and was rock solid after that point. I didn't have any more wifi issues... Just wanted to mention this change for other people. I usually got 5+disconnects every night. I'm gonna try just the AES option tonight and see how it acts.
Really strange issue just started occurring today as far as I can tell. I am on a Google Pixel XL, unlocked, rooted (with Magisk), running latest 8.1 with Feb security patch. This morning I have started experiencing a very strange issue with making phone calls with my phone. Regardless if I use a home screen direct dial shortcut, attempt to dial from within contacts, from call log, etc...I experience a VERY long delay between attempting to place the call and the call actually being made. Upwards of 30 sec or even much longer. I just used the stopwatch app to time a 3 min 10 sec. delay between the time I attempted to make a call by pressing the phone icon next to a recent call in the call log and when the phone actually "dialed" the call. Between the pressing of the button and the actual making of the call - there was no indication the phone had even accepted the input. I have never seen this behavior and it just started today. I have frozen my Call Control app (spam call filtering), Cleared cache and data for the "Phone" app. Disabled Advanced LTE Calling. I'm at a loss...the last app update on the "Phone" app was Feb 7, 2018
Anyone else experienced this or any suggestions? I have searched the forums and reddit and there appear to be some similar issues being reported - but nothing widespread. Any suggestions welcomed.
EDIT: The issue does not occur when booted into safe mode. So now I am hunting for which most recent app update is causing the issue. Good times.
Thanks!
S
sb1893 said:
Really strange issue just started occurring today as far as I can tell. I am on a Google Pixel XL, unlocked, rooted (with Magisk), running latest 8.1 with Feb security patch. This morning I have started experiencing a very strange issue with making phone calls with my phone. Regardless if I use a home screen direct dial shortcut, attempt to dial from within contacts, from call log, etc...I experience a VERY long delay between attempting to place the call and the call actually being made. Upwards of 30 sec or even much longer. I just used the stopwatch app to time a 3 min 10 sec. delay between the time I attempted to make a call by pressing the phone icon next to a recent call in the call log and when the phone actually "dialed" the call. Between the pressing of the button and the actual making of the call - there was no indication the phone had even accepted the input. I have never seen this behavior and it just started today. I have frozen my Call Control app (spam call filtering), Cleared cache and data for the "Phone" app. Disabled Advanced LTE Calling. I'm at a loss...the last app update on the "Phone" app was Feb 7, 2018
Anyone else experienced this or any suggestions? I have searched the forums and reddit and there appear to be some similar issues being reported - but nothing widespread. Any suggestions welcomed.
EDIT: The issue does not occur when booted into safe mode. So now I am hunting for which most recent app update is causing the issue. Good times.
Thanks!
S
Click to expand...
Click to collapse
Update: No idea what is going on - but I think I resolved the issue accidentally. I connected my Pixel XL to my computer to try to capture a logcat while the issue was occurring to see if I could find a clue as to the offending app. However, I was unable to reproduce the issue while running the logcat. I disconnected from my computer and now the issue is resolved. Phone calls can be made and respond immediately. This is after multiple reboots, clearing cache, data on phone app, etc did not resolve the issue and it could be readily reproduced.....not sure why the simple act of connecting to computer and running a logcat could have resolved. But oh well.
sb1893 said:
Update: No idea what is going on - but I think I resolved the issue accidentally. I connected my Pixel XL to my computer to try to capture a logcat while the issue was occurring to see if I could find a clue as to the offending app. However, I was unable to reproduce the issue while running the logcat. I disconnected from my computer and now the issue is resolved. Phone calls can be made and respond immediately. This is after multiple reboots, clearing cache, data on phone app, etc did not resolve the issue and it could be readily reproduced.....not sure why the simple act of connecting to computer and running a logcat could have resolved. But oh well.
Click to expand...
Click to collapse
And....issue has recurred. This time after making successfully making call over lunch while connected to Bluetooth system in my car. After that first call...all other calls were impacted by the 30 sec to 2 min delay before going thru. I've tried installing older version of Google Connectivity Services and that did not resolve the issue as well as using the Pixel Launcher (I normally use Nova). Once again, I was able to clear up the issue by simply connecting my phone to my computer via USB. (Didn't even run any commands within ADB this time - just connected phone and was able to make immediate calls again.) So now I think something related to connecting to my car bluetooth system is the culprit. But that car bluetooth version hasn't changed in a long time. And this has never happened before this morning. (I did use bluetooth in the car to make a call this morning when I first noticed the issue.) I'm at a loss. I'll keep playing with it I guess. Hopefully whatever got messed up gets corrected with another update soon.
sb1893 said:
And....issue has recurred. This time after making successfully making call over lunch while connected to Bluetooth system in my car. After that first call...all other calls were impacted by the 30 sec to 2 min delay before going thru. I've tried installing older version of Google Connectivity Services and that did not resolve the issue as well as using the Pixel Launcher (I normally use Nova). Once again, I was able to clear up the issue by simply connecting my phone to my computer via USB. (Didn't even run any commands within ADB this time - just connected phone and was able to make immediate calls again.) So now I think something related to connecting to my car bluetooth system is the culprit. But that car bluetooth version hasn't changed in a long time. And this has never happened before this morning. (I did use bluetooth in the car to make a call this morning when I first noticed the issue.) I'm at a loss. I'll keep playing with it I guess. Hopefully whatever got messed up gets corrected with another update soon.
Click to expand...
Click to collapse
The saga continues. The issue occurs immediately after the first call I attempt when connected to my BMW bluetooth system. From that point on, I experience a 30 sec to 3 min delay between attempting to make a call and the Pixel XL actually initiating the call. The quickest way I have found to resolve the issue is to plug the phone into a charger for a few seconds and I am then again able to place calls. I have verified that the BMW bluetooth software is up to date and has not been updated in over a year. (Again - this issue just started happening yesterday...and I've been on Feb security patch for several weeks). I just cleared cache from within Titanium Backup. Will see if that improves the situation. Very weird. I also was just able to recreate the issue using just a simple Plantronics headset. So I continue to think it is something related to the Bluetooth stack on the phone. But I am not sure how to check to see if any of that has been updated via app update since I upgraded to Feb security patches. (I reproduced the issue at my desk using the headset after clearing cache.)
S
Any news on this? This is absolutely killing me. Sometimes a hard reset stops fixes it, sometimes now. I bought this phone for almost $1,000 in April last year and it can't make phone calls. Pretty bad bug to say the least.
Racermanz said:
Any news on this? This is absolutely killing me. Sometimes a hard reset stops fixes it, sometimes now. I bought this phone for almost $1,000 in April last year and it can't make phone calls. Pretty bad bug to say the least.
Click to expand...
Click to collapse
No - but I'm at least somewhat encouraged to know I am not the only one dealing with the issue. Today I flashed factory images (but preserved my data by removing the -w from the flash-all.bat)...that did not resolve. I've tried the reset app preferences, reboot suggestion I found elsewhere - no dice. Google pushed a new Phone app yesterday - that also did not resolve. I've even tried uninstalling Magisk completely and dropping back to 15.4 - also no help. I'm running out of ideas. I've taken to carrying a charging cable in my car...so if I absolutely need to make a call when the phone isn't behaving, I can just quickly plug it in...which does clear up the issue temporarily. Also keep a charging cable at my desk now...so I'm limping along..but for an issue that just appeared out of nowhere this week...it's been pretty frustating to deal with. Also - I no longer believe being currently connected to Bluetooth is related to the issue. I've been able to get the issue to occur today while not connected to any bluetooth devices.
Try
settings>system>developer options>media>disable USB audio routing
DR3W5K1 said:
Try
settings>system>developer options>media>disable USB audio routing
Click to expand...
Click to collapse
Thanks bros. This is such a strange bug. Right now it works before I have turned off USB audio routing. I have turned off USB audio routing. I will report back if this DOESNT work. If I don't post again we can assume this works.
Thanks DR3W5K1, great name bro.
DR3W5K1 said:
Try
settings>system>developer options>media>disable USB audio routing
Click to expand...
Click to collapse
Just tried to toggle on, which looks to mean Disable. Then rebooted. No luck. Issue still occurs. Thanks for the suggestion. Willing to try anything even to just eliminate as possibility at this point.
Well - I have found a better workaround. When you attempt a call, if you get no response, you can toggle Airplane mode "ON"....You will then see the call you attempted fail. When you turn Airplane mode back "Off" you can can successfully make calls again. Better than having to plug into a charger cable to get the attempted call "unstuck"....still no idea what is going on....but this workaround at least is more palatable, portable, and take a few seconds...hope someone can figure out root cause soon and a proper fix becomes available.
EDIT: Even better workaround. Toggling Mobile Data OFF and ON has the same effect of clearing the issue. And works better when connected to Bluetooth in car as those connections will be maintained vs. using Airplane mode toggle. So - issue seems to be related to Mobile Data somehow - but I have already had Advanced Calling / LTE, etc...turned off as one of my first steps in troubleshooting this issue.
Has OP been down the road of looking at any and all apps installed that are interacting with the Phone permission? I remember snapchat was causing weird beeps for people when making calls until the permission was manually revoked.
Maybe some app is having a bad interaction?
Try changing the network mode in the secret menu dial *#*#4636#*#* to get there
The.Yield said:
Has OP been down the road of looking at any and all apps installed that are interacting with the Phone permission? I remember snapchat was causing weird beeps for people when making calls until the permission was manually revoked.
Maybe some app is having a bad interaction?
Click to expand...
Click to collapse
I have tried that. Sorry for not mentioning it in this thread. At one point I revoked "Phone" permission from all apps other than Phone, Carrier Services, and Contacts. Rebooted. Issue still occurred.
DR3W5K1 said:
Try changing the network mode in the secret menu dial *#*#4636#*#* to get there
Click to expand...
Click to collapse
Ahhh...I had forgotten about this secret menu. Looks like I could permanently toggle off VoLTE, WifiCalling, etc...here. But - not sure I want to go that route...I'm OK at present with Toggling Mobile Data via Quick Settings tile. And hopefully this issue eventually gets solved as mysteriously as it was introduced via some update.
Having the same problems on OG Pixel XL 8.1 with February security patches. All apps latest up to date.
Have tried uninstalling latest Phone app update. Clearing Phone app cache, etc nothing works. Network mode change, SIM reinstall, Network type change.
Only airplane mode toggle will fix it.
FYI mobile data toggle does NOT fix it for me, only airplane toggle. I wonder if network data toggle will only fix it if you are on a network provider currently doing calling over mobile data. Im on TMobile with great LTE coverage, but the mobile data toggle doesn't work for me.
tesla45 said:
Having the same problems on OG Pixel XL 8.1 with February security patches. All apps latest up to date.
Have tried uninstalling latest Phone app update. Clearing Phone app cache, etc nothing works. Network mode change, SIM reinstall, Network type change.
Only airplane mode toggle will fix it.
FYI mobile data toggle does NOT fix it for me, only airplane toggle. I wonder if network data toggle will only fix it if you are on a network provider currently doing calling over mobile data. Im on TMobile with great LTE coverage, but the mobile data toggle doesn't work for me.
Click to expand...
Click to collapse
Interesting....I'm on Verizon and I do believe that they route calls over Mobile data at times. I'm going to stay tuned, but likely done with much more deep investigation at the moment. I've spent enough time down this particular rabbit hole and the Mobile Data toggle is workable for me (not ideal, obviously)...hopefully a permanent fix materializes soon. Thanks to all for their suggestions and moral support. Much appreciated.
OK WORKAROUND FOR ANSWERING CALLS UPDATE:
Found this floating on some other forum, not sure where after this mad dash of a search I did this morning, but original credit to them...
When you receive a call and the phone is active and unlocked, press the power button to lock the phone and bring up the blue call management screen. Now you can swipe to answer.
This seems to work for more than one test call as I've tried this multiple times in a row.
NO REAL WORKAROUND FOR MAKING CALLS YET (outside of airplane mode toggle, or using Google voice/hangouts to place calls).
GOOGLE SUPPORT - THIS IS CLEARLY A SOFTWARE ISSUE, not a 3rd party app issue either since the problem goes away for answering calls when you press the lock screen or toggle airplane mode for placing calls. Please STOP ASKING CUSTOMERS TO invest hours of time (or money) FACTORY RESETTING PHONES, or REPLACING/BUYING NEW PHONES.
MY HUNCH is there is some core google service that isn't being used in SAFE MODE, but starts being used on NORMAL BOOT that is causing all these issues. I really DOUBT its a 3rd party app.
Install the stock again clearing all the data. Don't restore anything with titanium or install any extra apps. Then make a call.
tesla45 said:
OK WORKAROUND FOR ANSWERING CALLS UPDATE:
Found this floating on some other forum, not sure where after this mad dash of a search I did this morning, but original credit to them...
When you receive a call and the phone is active and unlocked, press the power button to lock the phone and bring up the blue call management screen. Now you can swipe to answer.
This seems to work for more than one test call as I've tried this multiple times in a row.
NO REAL WORKAROUND FOR MAKING CALLS YET (outside of airplane mode toggle, or using Google voice/hangouts to place calls).
GOOGLE SUPPORT - THIS IS CLEARLY A SOFTWARE ISSUE, not a 3rd party app issue either since the problem goes away for answering calls when you press the lock screen or toggle airplane mode for placing calls. Please STOP ASKING CUSTOMERS TO invest hours of time (or money) FACTORY RESETTING PHONES, or REPLACING/BUYING NEW PHONES.
MY HUNCH is there is some core google service that isn't being used in SAFE MODE, but starts being used on NORMAL BOOT that is causing all these issues. I really DOUBT its a 3rd party app.
Click to expand...
Click to collapse
And all this time, I thought my problem was only on the delay in placing calls. I just tested and confirmed that I am also having the same issue of being unable to answer calls. I also verified that the workaround you describe above works perfectly for me for answering calls. Also - I appreciate the suggestion to restore to fully factory reset, wiping data, and test prior to installing any apps....BUT I am not willing to invest that amount of time when I have viable workarounds. I agree that this is almost certainly a Google software issue in some core app or service and I'm hoping that we will see a resolution shortly...(maybe in March Security patches? - but I'm not holding out hope as I haven't seen that much widespread concern about this issue elsewhere.)
sb1893 said:
And all this time, I thought my problem was only on the delay in placing calls. I just tested and confirmed that I am also having the same issue of being unable to answer calls. I also verified that the workaround you describe above works perfectly for me for answering calls. Also - I appreciate the suggestion to restore to fully factory reset, wiping data, and test prior to installing any apps....BUT I am not willing to invest that amount of time when I have viable workarounds. I agree that this is almost certainly a Google software issue in some core app or service and I'm hoping that we will see a resolution shortly...(maybe in March Security patches? - but I'm not holding out hope as I haven't seen that much widespread concern about this issue elsewhere.)
Click to expand...
Click to collapse
Glad the workaround helps you too. My emphasis CAPS in my last post was clearly misleading, I was actually suggesting NOT to reinstall/factory reset because I don't believe that solves the problem long term and its a huge ask for a customer (when really Google should be solving this problem for us).
Based on this little workaround its clearly a software problem that Google needs to address, I've raised the issues on many threads in their product forums ... hope it gets to the right people ASAP because I believe lots of Pixel users are running into the problem (both Pixel 2 and 1st gen, another indication its NOT a HW problem).
Keep the workarounds coming folks!