Related
I was looking to buy this phone but I note its having some major issues: http://www.androidheadlines.com/201...ers-reporting-premature-battery-shutdown.html
Anyone know just how widespread the issues are? Is it too risky to buy?
I have had the VZW Pixel 128GB from the day of release, installed all the updates as they were released. I have experienced no issues whatsoever in all the time I have had it. I have unlocked, rooted, unrooted, installed 2 different custom kernels and stock. Through all this I have had 0 issues with the phone. I love it.
Sent from my Pixel using XDA-Developers mobile app
Protibus said:
I have had the VZW Pixel 128GB from the day of release, installed all the updates as they were released. I have experienced no issues whatsoever in all the time I have had it. I have unlocked, rooted, unrooted, installed 2 different custom kernels and stock. Through all this I have had 0 issues with the phone. I love it.
Sent from my Pixel using XDA-Developers mobile app
Click to expand...
Click to collapse
Same here. No issues.
dccxviii said:
I was looking to buy this phone but I note its having some major issues: http://www.androidheadlines.com/201...ers-reporting-premature-battery-shutdown.html
Anyone know just how widespread the issues are? Is it too risky to buy?
Click to expand...
Click to collapse
It is not a major Pixel issue. It is a minor Android 7 issue. It is happening at low levels to a few phones. I don't even recall seeing anyone in these pixel forums about it.
I have this issue, on the regular (non-XL) Pixel. I first noticed it between Christmas and NYE, the device shut down at around 20% battery. It's now happening almost every time the battery drops below 25%, albeit at slightly different capacities each time (between 18-25%). This morning I used the "chat" option to discuss with Support, without noticing the new security patch released this morning. So now I'm running my battery down and waiting to recreate the issue. Support played dumb and said they hadn't heard of the issue.
cliche guevara said:
I have this issue, on the regular (non-XL) Pixel. I first noticed it between Christmas and NYE, the device shut down at around 20% battery. It's now happening almost every time the battery drops below 25%, albeit at slightly different capacities each time (between 18-25%). This morning I used the "chat" option to discuss with Support, without noticing the new security patch released this morning. So now I'm running my battery down and waiting to recreate the issue. Support played dumb and said they hadn't heard of the issue.
Click to expand...
Click to collapse
Did the security patch help? I had the same issue on my 5" Pixel (around 10% though) and did a factory reset (with only the most necessary apps installed), since then the problem is gone. BUT i also received the January security patch on the same day, so i don't really know what fixed it.
What i also recognized on my screenshots and my others that were posted on this matter, is the wrong Awake/"Aktiv" indicator before the shutdown happened (see the attached screenshot). IMO, this may point to a software issue, not an actual faulty battery or cool temperatures.
Hello
I have the same issue
I am use XL device . this issue happen to me 3 times . first time was before a month when the battery come to 50% the phone shut down
second time was before tow days and the same issue happened before 3 hours :crying::crying:
I dont know if the hardware problem or software problem
Please help :crying::crying::crying:
ph0b0z said:
Did the security patch help? I had the same issue on my 5" Pixel (around 10% though) and did a factory reset (with only the most necessary apps installed), since then the problem is gone. BUT i also received the January security patch on the same day, so i don't really know what fixed it. [emoji14]
What i also recognized on my screenshots and my others that were posted on this matter, is the wrong Awake/"Aktiv" indicator before the shutdown happened (see the attached screenshot). IMO, this may point to a software issue, not an actual faulty battery or cool temperatures.
Click to expand...
Click to collapse
Any resolution for this problem now? Have the same problem on my xl.
Gesendet von meinem Pixel XL mit Tapatalk
[email protected] said:
Any resolution for this problem now? Have the same problem on my xl.
Gesendet von meinem Pixel XL mit Tapatalk
Click to expand...
Click to collapse
Nothing new that i know of, i didn't run into this problem since the factory reset. Maybe, in some cases, it's a hardware issue after all? Does your awake-log look faulty as well?
ph0b0z said:
Nothing new that i know of, i didn't run into this problem since the factory reset. Maybe, in some cases, it's a hardware issue after all? Does your awake-log look faulty as well?
Click to expand...
Click to collapse
Yes, exactly the same as you described, even with the false activity line as shown on your picture. Does this work now too after your factory reset?
Gesendet von meinem Pixel XL mit Tapatalk
[email protected] said:
Yes, exactly the same as you described, even with the false activity line as shown on your picture. Does this work now too after your factory reset?
Gesendet von meinem Pixel XL mit Tapatalk
Click to expand...
Click to collapse
Yes, it happened after new years, when the device was just about a week old and did not occur since then. This is from yesterday (regular Pixel), while i never crack the 5h mark with mixed usage: https://goo.gl/photos/Yui6D3sdSK8gyFax9
These are from when the first or second early shutdown occured: http://imgur.com/a/4g0V5
I find it a bit weird that this is not a bigger topic on XDA, there are a "lot" of posts in the issue tracker, the pixel user community and even a some on reddit from time to time.
ph0b0z said:
Yes, it happened after new years, when the device was just about a week old and did not occur since then. This is from yesterday (regular Pixel), while i never crack the 5h mark with mixed usage: https://goo.gl/photos/Yui6D3sdSK8gyFax9
These are from when the first or second early shutdown occured: http://imgur.com/a/4g0V5
Click to expand...
Click to collapse
Okay, I'm not 100 % sure but I think this happened first time after the February update. Looks like I should do a factory reset. Let's see if this works for me as well.
Will report, thanks.
Gesendet von meinem Pixel XL mit Tapatalk
Anyone have a change to beta test 7.1.2? there is a supposed fix in that code
@invisiblek - as you are currently the only developer out there
Factory images:
https://essential-live.herokuapp.com/developer/current-builds
Oreo beta:
https://essential-live.herokuapp.com/developer/beta-builds
Just wanted to add that in order to completely flash the factory image you will need to unlock the critical partition in fastboot before flashing:
fastboot flashing unlock_critical
wow, very cool, will give the oreo a try.
cheers
???
Can someone Post His experiences please? Is it good as a Daily Driver?
wegwolv said:
Can someone Post His experiences please? Is it good as a Daily Driver?
Click to expand...
Click to collapse
from the source
Known issues list (updated 11/14)
Intermittent Bluetooth connectivity issues with certain auto brands
Battery performance degradations until optimized Oreo framework complete
Occasional ANRs with certain apps
Click to expand...
Click to collapse
haven't tested this myself yet.
derausgewanderte said:
from the source
haven't tested this myself yet.
Click to expand...
Click to collapse
Thanks for the Infos! I'm getting Mine tomorrow.
Can I flash NMJ32F on the Sprint version?
unfortunately, the stutter has not improved on Oreo. In fact, it feels worse.
Oreo is working fine for me this whole 25 minutes. I haven't tested Bluetooth yet though
lkhafra said:
Oreo is working fine for me this whole 25 minutes. I haven't tested Bluetooth yet though
Click to expand...
Click to collapse
Has the camera app improved in Oreo?
Has anyone successfully tried flashing NMI81C to an unlocked device? I can't imagine there'd be a problem, but if no one has done it or seen any problems with it then I know what I'm doing when I get home tomorrow. That was the last build my bluetooth music controls worked with, so I'm pretty excited to be able to flash back to it.
quazimodem said:
Has the camera app improved in Oreo?
Click to expand...
Click to collapse
I do not think any app was updated. Unless there is some API in Oreo that would inherently improve the cam.
Does anyone know if you can flash the unlocked firmware onto the Sprint's variant of the Essential after it is carrier unlocked?
xterminater07 said:
Does anyone know if you can flash the unlocked firmware onto the Sprint's variant of the Essential after it is carrier unlocked?
Click to expand...
Click to collapse
Yes it works
Sent from my PH-1 using Tapatalk
Oreo running great...only found one bug dealing with wifi hotspot and not being able to select 5ghz as the band to use.
Since flashing Oreo last night I am getting excellent battery life and it appears that I may do better than I was on Android nougat. Personally I really like this phone and no the camera is not the best but for $450 this is probably the nicest phone anyone can hold in their hand at any price point. Once the dads get interested because of price and we can get a port for the Huawei camera I'm sure this camera would do very well
jasonevil said:
Yes it works
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
Nice, I will try to flash the Oreo beta of the Unlocked version to my Sprint variants. BTW, do you happen to know how to trigger the UICC unlock menu without having to have the Sprint sim in there and activate the phone? Sprint reps told me the phone is unlocked on their end, but my phone still say invalid sim because the UICC unlock menu has not been activated on the phone itself. Would flashing the unlocked firmware solves this?
Only downside for me so far on the beta is battery life.
On nougat I would go to bed with 100% battery and wake up with 100%.
On Oreo I woke up with like 97%. Keeps dying quicker during the day as well, but this is expected as they mentioned the Oreo framework wasn't optimized for battery life yet.
jasonevil said:
Yes it works
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
xterminater07 said:
Does anyone know if you can flash the unlocked firmware onto the Sprint's variant of the Essential after it is carrier unlocked?
Click to expand...
Click to collapse
Not only does it work but definitely recommended as you will get the latest fingerprint sensor fix as well as better screen touches.
I am coming up on 24 hours into this Oreo beta, and it's my daily driver. So far, so good. Battery life seems a bit better for me, although it was great before - hard to do an apples to apples comparison though. No bluetooth issues, in fact, this seems a bit better with Plantronics Voyager/Legend than before - haven't tried in the car yet. I had one spontaneous reboot (I wasn't using it, just sitting on the desk and I noticed it rebooting) but so far, I can't see any reason not to charge ahead. The install did turn off wifi calling, I had to re-enable that. No service/signal issues (on T-Mobile in central Texas).
Since swapping a few ROMs, android 11, now 10, screen has ghost touches when navigating.
Flipping annoying as!
Any fix?
badaas said:
Since swapping a few ROMs, android 11, now 10, screen has ghost touches when navigating.
Flipping annoying as!
Any fix?
Click to expand...
Click to collapse
I have same problem, I flashed custom rom for first time in over a year and then went back to stock and now I have same problem, I flashed factory image and wiped data and problem still there, post fix here if you find it please
I installed February stock Android 11.
Fixed it.
I'm now on latest superior and is ok thank fook.
Any one notice multi touch stops working on stock and custom roms?
miko12312 said:
Any one notice multi touch stops working on stock and custom roms?
Click to expand...
Click to collapse
Multitouch is not working at all with my wife's phone. Literally took out of its box three days ago. Google sucks.
joaquincgarcia said:
Multitouch is not working at all with my wife's phone. Literally took out of its box three days ago. Google sucks.
Click to expand...
Click to collapse
How are you guys testing if multi-touch is working or not?
If multi-touch wasn't working, wouldn't that mean that pinch/zoom would not work because it requires two (multi) touch points?
JohnC said:
How are you guys testing if multi-touch is working or not?
If multi-touch wasn't working, wouldn't that mean that pinch/zoom would not work because it requires two (multi) touch points?
Click to expand...
Click to collapse
Yes as I am having issues when trying to zoom or use to touches at once it will only read one, sometimes going into landscape mode and back gets it back working but will do it again at random , I do have a screen protector and a google case ,but only till recently after the march update it
JohnC said:
How are you guys testing if multi-touch is working or not?
If multi-touch wasn't working, wouldn't that mean that pinch/zoom would not work because it requires two (multi) touch points?
Click to expand...
Click to collapse
I have also tried enabling point location in dev options still only reads 1 touch , also going to android 10 does fix all touch issues, but I'd rather have android 11
miko12312 said:
Yes as I am having issues when trying to zoom or use to touches at once it will only read one, sometimes going into landscape mode and back gets it back working but will do it again at random , I do have a screen protector and a google case ,but only till recently after the march update it
Click to expand...
Click to collapse
I am having this issues on my mother's phone, practically since I got it for her (about 1.5 months). Its barely usable for her. Has anything worked for you guys?
Thanks!
Android 11
Having wierd issues with my pixel 2 xl.
Running last Android 11 update.
Currently on custom ROM.
Tried Lineageos 18, pixel experience 11 but same problem.
Sometimes its impossible to text also.
Been happily using my phone from almost 2 years.
Having this issue recently.
Tested without Mobile cover and screen guard.
While typing this, everything seems normal but issue do arises from time to time.
Plz help me out here.
I have uploaded a video name "Pixel 2 XL touch issue" on youtube by username Mohammed Shaikh
msshaikh1717 said:
Having wierd issues with my pixel 2 xl.
Click to expand...
Click to collapse
That is unfortunate, but you are in the wrong subforum since this is for the Pixel 4a.
Your issue belongs to one of the Pixel 2 XL subforums.
Widespread Pixel 4a issue. Uding official Android 10 is the only known workaround that works for multiple users.
Alright, so currently im dealing with some Multitouch issues on my Pixel 4a. The repair place i went to UBREAKIFIX said they'll have to do the whole repair they did preciously again and charge me (because of 2 small dents at the side of the screen). Would not recommend. I wanted to get a poll of everyone with this exact issue Here is some steps to test:
1. Enable Developer Options (Go into build number click however many times and get developers options
2. Go to Developer Options in System settings,
3. Scroll down to Input and enable "Show taps" and "Pointer Location.
4. Put two fingers down and see if multiple pointers are shown (If not, Multi-touch does not work)
Also some other Notes:
Downgrading to Android 10, Makes multitouch work for some reason :/
Also would like to know if you've gotten your phone repaired before.
Any help figuring this whole thing out is appreciated
Can I ask what was the repair they did the first time to fix your touch problem?
hammered58 said:
Can I ask what was the repair they did the first time to fix your touch problem?
Click to expand...
Click to collapse
The first time, it was just a broken screen, had to replace it
fbievan said:
The first time, it was just a broken screen, had to replace it
Click to expand...
Click to collapse
Dont know if started happening before or after, but i noticed it recently, and started digging, brought it to the place and they said they wouldnt cover it under warranty because of 2 small dents at the side of screen which have zero relation to the problem at hand
fbievan said:
Dont know if started happening before or after, but i noticed it recently, and started digging, brought it to the place and they said they wouldnt cover it under warranty because of 2 small dents at the side of screen which have zero relation to the problem at hand
Click to expand...
Click to collapse
That's sucks, hard to prove if there right or wrong without putting a known good screen on
hammered58 said:
That's sucks, hard to prove if there right or wrong without putting a known good screen on
Click to expand...
Click to collapse
Also as i noted, for some reason downgrading to andorid 10 has multitouch working. (From flash.android.com)
fbievan said:
Also as i noted, for some reason downgrading to andorid 10 has multitouch working. (From flash.android.com)
Click to expand...
Click to collapse
I honestly cant say if its the hardware or software, maybe it might be a combination of both? I'm not entirely sure, however downgrading to android 10 from googles flash tool does seem to have it work. I had what i would guess is a full screen replacement from UBREAKIFIX, due to shattering the entire screen. Honestly, spending 140 dollars just to see if it might work is not worth it to me, so I'm really not sure what to do.
Even doing it yourself the cheapest I've seen a screen is 110 from AliExpress, which I don't get because I just replaced one on a g7 moto play for 20 bucks off ebay
hammered58 said:
Even doing it yourself the cheapest I've seen a screen is 110 from AliExpress, which I don't get because I just replaced one on a g7 moto play for 20 bucks off ebay
Click to expand...
Click to collapse
Is there any reason why this multitouch would work on android 10? I dont see exactly what is happening here
fbievan said:
Is there any reason why this multitouch would work on android 10? I dont see exactly what is happening here
Click to expand...
Click to collapse
idk,, maybe the sensitivity is setup diff
hammered58 said:
idk,, maybe the sensitivity is setup diff
Click to expand...
Click to collapse
After looking for a while seems the entire drivers are different in the kernel. But that is my brief look at. If anyone who knows kernel drivers would like to take a look at it. Would be helpful
LineageOS 19.1 - multitouch just stopped working today after several weeks without problems. No repairs or damage.
I'm on stock but rooted. I've been slack so still on October patch. Multi touch working fine. Never had a problem with it.
(Finally updated to December patch and it's still working.)
LionDGem said:
LineageOS 19.1 - multitouch just stopped working today after several weeks without problems. No repairs or damage.
Click to expand...
Click to collapse
What fixed it for me was downgrading to android 10 then updating all the way up...
From right here: https://forum.xda-developers.com/t/...ter-apr-security-update.4428089/post-87356703
fbievan said:
What fixed it for me was downgrading to android 10 then updating all the way up...
From right here: https://forum.xda-developers.com/t/...ter-apr-security-update.4428089/post-87356703
Click to expand...
Click to collapse
Wonder how this actually fixes the issue. Sounds strange.
LionDGem said:
Wonder how this actually fixes the issue. Sounds strange.
Click to expand...
Click to collapse
I don't know... As far as I know downgrading has the kernel touchscreen driver seemingly working... from there I know little
fbievan said:
I don't know... As far as I know downgrading has the kernel touchscreen driver seemingly working... from there I know little
Click to expand...
Click to collapse
Multitouch stopped working on my Pixel 4A 5G after updating to android 13.
Maybe a bug caused by an OTA update?
qqBenji said:
Multitouch stopped working on my Pixel 4A 5G after updating to android 13.
Maybe a bug caused by an OTA update?
Click to expand...
Click to collapse
I have LineageOS 19.1 here. So android 12. i'll try that android 10 approach
I can confirm now that downgrading to Official Google Pixel 4a Stock Rom Android 10 fixed the issue. I try to go back to LOS 20 now and see what happens.
PS: Using internal updater to update to Android 13 broke it again. Taking the long route now.
PPS: That chromium based flash tool is really handy. Would be awesome to have something like that for LineageOS.
PPS: As soon as I install anything above Android 10, multitouch stops working. I'll sell this stupid thing as is (will let te buyer know of course). Its a shame.
How are you finding it?
KraftwerkElectro said:
How are you finding it?
Click to expand...
Click to collapse
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Scroll till u hit sunfish pixel 4a,
KraftwerkElectro said:
How are you finding it?
Click to expand...
Click to collapse
hammered58 said:
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Scroll till u hit sunfish pixel 4a,
Click to expand...
Click to collapse
I'm pretty sure he didn't ask "how" to find the download of the firmware, but for people who flashed the ROM, what is their evaluation/experience of this new firmware.
Easy change. Big up to to the Magisk team, root worked right away.
I haven't seen any big change yet -still checking...
DiamondJohn said:
I'm pretty sure he didn't ask "how" to find the download of the firmware, but for people who flashed the ROM, what is their evaluation/experience of this new firmware.
Click to expand...
Click to collapse
You are correct
I don't actually notice any difference, on this 3rd day, although responses may be a bit "perkier"
DiamondJohn said:
I'm pretty sure he didn't ask "how" to find the download of the firmware, but for people who flashed the ROM, what is their evaluation/experience of this new firmware.
Click to expand...
Click to collapse
If that's the case then "I haven't found it"
day 3 in and all i noticed is the new setting for the lock screen clock and the battery life is noticeably worse. hopefully the battery gets back to normal after a few days.
badtlc said:
day 3 in and all i noticed is the new setting for the lock screen clock and the battery life is noticeably worse. hopefully the battery gets back to normal after a few days.
Click to expand...
Click to collapse
Some battery loss can be exoected as the new AI "learns". Haven't noticed that here, tho
amphi66 said:
Some battery loss can be exoected as the new AI "learns". Haven't noticed that here, tho
Click to expand...
Click to collapse
It is pretty bad for me still. Overnight battery drain used to be about 5%. Lately it has been 8-9%. Even tried a factory reset to make sure no bugs from the OTA update.
I put it on my 4a. It seems mostly the same.
Lock screen clock is bigger.
Media controls are heaps different.
I gotta update my apps now because new rules.
I haven't noticed battery issues but I'm not a heavy user and it's only been a day or two.
So far , I have only one issue: when I make a call, I hear also the ambient noise in my headphones.
Before upgrading to Android 13 I didn't have this issue and I was only hearing the other person speaking.