Develop Bugs

problem charging and typing on cyanogen, anyone else

i really must ask, i have had this problem forever and need to know if anyone else has it. When my phone is plugged in charging the keyboard always messes up and hits random keys. anyone know how to fix it or what is causing it. had this phone for a year now, and seen cyanogen 7.0.3 i am about to kill it.

I personally have not seen this problem. I am running the CM 7 nightlies, and i am having a good experience. The keys are fine for me, but i will be sure to keep on the lookout for that bug...
I'm guessing you have already tried to re-flash.
Also, do you have a wifi problem on CM7? I've had the worst luck because in my old Synergy Rom, i could get wifi in my room perfectly, but now with CM7, I barely get any reception if not any at all.

I've had this issue, but pretty much on any ROM. Whenever my phone is charging, it isn't very responsive to any touch input. Once unplugged, works fine.

Its a hardware issue, not software

I've seen some Incs that will have unresponsive / unpredictable touch-screens when plugged in to cheap chargers. In the cases that I've seen, they never misbehave on an OEM charger: only on third-party budget ones. As noted by br125, it has always been a hardware issue in my experience.
You can try different chargers to see if it makes a difference.

I did on the older versions of CM but not sense CM7

We had this same problem on the old D1's, the solution was to use the OEM charger it originally came with.
Hope this helps

I'm using the OEM charger and have this issue on MIUI/incredikernel. Laggy and unresponsive touch input while charging.

I noticed this issue too, really odd and annoying. I've been running MIUI for a little over a week and have noticed the problem is completely gone and normal typing is actually more responsive. Always been a CM7 fanboy but I'm quite impressed with miui....

byrong said:
I've seen some Incs that will have unresponsive / unpredictable touch-screens when plugged in to cheap chargers. In the cases that I've seen, they never misbehave on an OEM charger: only on third-party budget ones. As noted by br125, it has always been a hardware issue in my experience.
You can try different chargers to see if it makes a difference.
Click to expand...
Click to collapse
I have an OEM charger and a third-party charger as well and i have experienced the problem randomly on both. I seem to notice the problem more when i charge it while connected to my laptop

I have the same problem. I've noticed that the trackball work perfectly and in fact have temporarily got around this problem ( as long as I do not have to type in something) in this manner.

The problem has something to do with being grounded.

Ouya Issues

GF got me an ouya as a stocking stuffer and even though I really wanted one and think its a great little toy, I cant get over a few issues.
I am hoping some of you guys can tell me you've experienced the same and maybe even have a fix.
My console is rooted but stock rom.
1) controller lag is awful. Even playing an old SNES game mario world was so unresponsive I couldn't even finish the first stage. I downloaded "The Ball" which actually is a very interesting little game I might buy for 9$ but seriously the Lag would get so bad My guy would end up spinning in cricles and killing himself.
I recently decided to hard wire the system since I have read online thats a possible fix but really didnt get time to test. Also read placing the system on its side helps but REALLY?
2) Sound dissapears. EVERY time I reboot or come up from sleep mode (50/50 on that one) I have to repeatedly unplug and re plug in the HDMI plug until sound returns. WTF is up with that? Also read this could be a universal problem after the latest update.
3) Wireless N will not work. Again I have hardwired it for now but the thing WILL NOT see my wireless N on my duel band. It will see the G fine and have "excellent" connection but it will not see the N. I even tried manually entering the SSID but no luck. My buddy who also bought one when I did seems to have ZERO the issues Im having.
I have been dealing with tech support and wondering If I shoudl just return the thing to Target as a faulty model and try again.

tevil said:
GF got me an ouya as a stocking stuffer and even though I really wanted one and think its a great little toy, I cant get over a few issues.
I am hoping some of you guys can tell me you've experienced the same and maybe even have a fix.
My console is rooted but stock rom.
1) controller lag is awful. Even playing an old SNES game mario world was so unresponsive I couldn't even finish the first stage. I downloaded "The Ball" which actually is a very interesting little game I might buy for 9$ but seriously the Lag would get so bad My guy would end up spinning in cricles and killing himself.
I recently decided to hard wire the system since I have read online thats a possible fix but really didnt get time to test. Also read placing the system on its side helps but REALLY?
2) Sound dissapears. EVERY time I reboot or come up from sleep mode (50/50 on that one) I have to repeatedly unplug and re plug in the HDMI plug until sound returns. WTF is up with that? Also read this could be a universal problem after the latest update.
3) Wireless N will not work. Again I have hardwired it for now but the thing WILL NOT see my wireless N on my duel band. It will see the G fine and have "excellent" connection but it will not see the N. I even tried manually entering the SSID but no luck. My buddy who also bought one when I did seems to have ZERO the issues Im having.
I have been dealing with tech support and wondering If I shoudl just return the thing to Target as a faulty model and try again.
Click to expand...
Click to collapse
1) I don't have any lags with controllet. I have used Wifi, but now I'm using ethernet and work fine. Try the controller settings with wifi and bluetooth settings.
2) I have sound bug only in emulator. Solution is go to the audio settings and than back. Once do this in GTA but I only press 2x menu button a than quit and it worked.
3) I have only 802.11 N and no problem. If you mean 5GHz N this is not support.

Mattthev said:
1) no problem. If you mean 5GHz N this is not support.
Click to expand...
Click to collapse
okay then thats it cause mine is dual channel
Still the controller lag is a huge issue.
Also the sound settings are not it cause literally I will just replug in the HDMI and it comes back.
thanks
Ive googled and seen others who say their sound went after the latest update and since mine updated as soon as it turned on then thats probably it

tevil said:
okay then thats it cause mine is dual channel
Still the controller lag is a huge issue.
Also the sound settings are not it cause literally I will just replug in the HDMI and it comes back.
thanks
Ive googled and seen others who say their sound went after the latest update and since mine updated as soon as it turned on then thats probably it
Click to expand...
Click to collapse
Try another HDMI cable and use ethernet.

Mattthev said:
Try another HDMI cable and use ethernet.
Click to expand...
Click to collapse
yeah been through about 4 cables until I finally just went back to stock because it was the shortest.
All of them did it.
Im on ethernet now. Will have to run some plays tonight.

Location. Is your Ouya in clear sight and close to the controller? For some ungodly reason the Ouya has a metal case, a metal case surrounding all the wireless antennas.
I recently placed my Ouya 6" from where it previously resided, but behind my TV. Now my streaming shows buffer every 2-3 minutes.
I have heard the aftermarket cases offer significant improvements in wireless performance. Since the WiFi and Bluetooth use the same chip and antenna both are affected, and both improve with increased signal that is the result of removing the Faraday cage from around the motherboard. This improves the responsiveness of the controller since it isn't fighting for signal as much, and Bluetooth is a low power short range protocol as it is.
Also try calibrating the controller. Pull the batteries, put them back in, and fire up the controller. Don't touch it while its starting. It helped improve my controller some, didn't notice if it improved lag at all though.

ill try the recalibration.
I have turned it on its side and its about 8' to the right of where I sit in plain line of sight. Also its using a hard cable now. improved but NOT great. Will work fine for like 15 minutes then just start buggin out.
My controller firmware is 0x0103 which seems to be older since there is 0104 out now.
My buddy who has ZERO issues with his controller running wifi with his OUYA behind his TV is going to tell me his firmware tonight. He lives in anotehr state tho so we cant trade controlelrs.
Been going back and forth with OUYA cust serv on this.
Also the sound thing seems to be a big issue on the OUYA forums

No issues with sound for me, so it is not universal. It's probably a bug that affects some TV's and receivers but not others. Stuff like that was super common when HDMI was new. Doing support for HD cable boxes sucked, let me tell you.
Sent from my ADR6350 using Tapatalk

[Q] Help me get through a day!

My Tmo S3 is getting old and cranky apparently. Not sure what else to try, perhaps someone can weigh in?
1. I'm running CM11. I have tried other ROMs, all had the same issues.
2. It charges best with my Qi charger, as my daughter tripped on my charging cable once and it pulled out. It will still charge via USB, but slowly.
3. I have tried ART and Dalvik. No difference in battery life.
4. I've tried another battery. Also no difference.
5. I've tried Trebuchet, GNL and Nova.
6. I've tried installing Xposed with a couple of modules (not at the same time) one to help with wakelocks and one to help minimize Google's location checks.
7. I've tried taking out my Sandisk micro card. No difference.
It slows way down sometimes, generally when there are a couple of things going on but not always. For example, I got to work a few days ago, at an unfamiliar location. My phone was in the car cradle, plugged in to the car charger (bought from Tmo for the phone). Google Maps was running to nav me. I unplugged it, stopped Maps and tried to text my husband that I'd arrived. It would load Hangouts but never the conversation. Just the spinning circle. I needed to get in to the classroom. Rebooted, it booted then booted itself again, I could finally text him, but it was still hanging. When I would type, all the letters (google keyboard) would stay "lit up" so I couldn't see the keyboard.
Sometimes I get audio notifications, sometimes not. Sometimes it rings, sometimes not. Sometimes while I'm looking at the hangouts conversation it'll ding that I have a new message but the message won't show up for another minute or two.
Any other ideas? I'd really like to not have to buy another phone, but I'm beginning to wonder if this one is just done.
Frustrating because I used to run GNL, have "Ok, Google" enabled from any screen, have my Twitter update once an hour, have weather update once an hour, and now I've uninstalled Twitter, my weather updates manually (so no severe weather warnings...), I've ditched GNL and turned off "Ok, google." It isn't like my phone wasn't running these things.
Example: Today I had to go shopping for household and grocery items. Each time I was in the vehicle the phone was plugged in. The drive into town, between stores, while I ate lunch in the van. It was full 99% when I left home. 4 hours later it was at 29%...plugged in. I tried both the car charger and a brand new USB cable plugged into my FM transmitter.

I kinda have a feeling its got to do with how you're charging it. USB and car chargers generally don't push more than 500ma, where a good wall charger will be rated between 1-2A. No idea about wireless charging but I'd suspect they charge with a lower current. I could be wrong though.
Anyway, it also matters what cables you use. Many replacement charging cables won't handle the higher current. So even if you are using a good charger, a cheap cable can reduce any benefit expected. Over time, this all may have a negative effect on how much voltage the battery can push out to the device, impacting performance. Plus as the battery gets old this naturally happens anyway so the effect could be combined.
It also might help to start over fresh with your system and apps. Flash firmware via Odin first. (This would be a good time to test things while fully stock). Then reflash your ROM and only restore essential data. Reinstall everything else and start clean.
If you have the same problems, especially while stock, and a new battery doesn't help, it is possible some hardware has started to degrade due to age.
Whatever the problem may be though, backup your important data off-device soon, just in case.
Sent from my SAMSUNG-SGH-T999 using Tapatalk

Thank you for your input, DocHoliday. I appreciate your wisdom. Up until about a month ago, I'd used the OEM wall charger and cable. We wondered about the cable so my husband bought me a good replacement. We definitely try to stuck with good quality, our phones are investments we can't afford to replace if we can help it.
I do believe we're going to ODIN to stock tomorrow. I need my husband's help on that one. I've never dealt with ODIN, only installing zip or the CM installer. If we can save it and make it stable we'll pass it to our daughter. I gave up and bought a Moto G.
I'm really interested though in what the outcome will be with stock. I have, indeed, tried what you suggested as far as starting fresh with system and apps. Yesterday I did a full wipe, wiped /system, cache, Dalvik. Signed in to Google and put only what I needed back on.
Thanks again for the advice. I'll report back after running stock a few days.

For people who have never used it, Odin can sound a lot more intimidating than it really is. It's really quite simple though, so if you find you have to do it on your own at some point, I'm sure you'll be just fine.
Sent from my SAMSUNG-SGH-T999 using Tapatalk

Thank you for that vote of confidence. I can always cover up Touchwiz with Nova, right? ?

Yup!
Sent from my SAMSUNG-SGH-T999 using Tapatalk

[Q] Touchscreen behaves erratically when charging

Hey All
Today I picked up an HTC One M8.
Have set it up and only had it up and running for a few hours.
I plugged it in to charge using the charger that came with it and noticed that the screen would become erratic. Phantom touches would register making it very hard to use. Have tried it in different sockets but the issue remains.
I have tried a spare charger that I have in the house and the issue is not present.I know the HTC charger is a little different in that it supports some kind of quick charger, so its not really a like for like swap I guess.
Is there a chance that the included charger is faulty? Or could the phone be at fault?
I really don't want to have to return it but will it it looks like its the phone that has an issue.
Thanks

Well, at this point its hard to guess from here. Can you upload some snaps/videos ? It would be helpful for anyone who visits the thread. It doesn't take much time either. :good:

Is it a brand new phone? if not I think the digitizer is going bad.

scorror said:
Is it a brand new phone? if not I think the digitizer is going bad.
Click to expand...
Click to collapse
Yeah it's brand new. Phone is fine off charge and when using other charges. It's just the stock charger tat seems to cause issues.

warpkid said:
Hey All
Today I picked up an HTC One M8.
Have set it up and only had it up and running for a few hours.
I plugged it in to charge using the charger that came with it and noticed that the screen would become erratic. Phantom touches would register making it very hard to use. Have tried it in different sockets but the issue remains.
I have tried a spare charger that I have in the house and the issue is not present.I know the HTC charger is a little different in that it supports some kind of quick charger, so its not really a like for like swap I guess.
Is there a chance that the included charger is faulty? Or could the phone be at fault?
I really don't want to have to return it but will it it looks like its the phone that has an issue.
Thanks
Click to expand...
Click to collapse
Do you have a case on your phone? I have a UAG case and the charger sometimes doesn't fully click leading to that behaviour. Without the case there is no problem using the phone while charging.

Maybe the stock charger is faulty. Probably the wires has lost continuity.

I have the same issue with a unofficial charger (2.0A).
No issue with original charger (1.5A)

You are not alone
I also have a HTC One M8 with the same problem!
I have to disconnect the USB cable so that I can use the phone correctly without 'phantom touches' activating things I didn't want.
A classic example is pressing the back button will more often than not take me to google now. It's not supposed to do that. It only ever does this when charging.
Also when using any app the phantom touches will activate things I didn't want it to. Some apps will indicate which button you clicked and this is the perfect way to see this problem in action, because buttons will be clicking that you didn't even touch.
It's almost like the touch screen becomes ridiculously sensitive and even just a touch of breeze from a fan can activate a phantom touch.
My phone has done this since brand new. I've had the phone for around 3 months now. There was a software update since I had the phone and it didn't fix the problem.
It does this for me with the stock USB cable, samsung USB cable, generic USB cable, charging from AC/PC/Car it doesn't matter.
It even has the problem when the battery is at 100% with the cable connected.
The only way to accurately use the phone is to unplug the cable!
I'm in Australia on the Telstra network
Android: 4.4.3
HTC Sense: 6.0
Software: 2.23.841.1
HTC SDK API 6.25

Erratic Touch on Verizon HTC One M8
This has been driving me mad.
Got Verizon Variant Red HTC One M8 near the beginning of August.
I bought a spigen clear case, a longer usb cable, and a 2AMP charger to use at work. I was chewing through the battery while playing Clash of Clans on it at work.
I pretty much always turn on visual feedback for touch on my smartphone now and noticed sometimes while playing Clash I would see multiple touches go in a horizontal line across my screen (if you do not know you play clash of clans in a horizontal position so technically the lines would run vertically down the phone)
I also have a tempered glass screen on my phone so I figured it was some kind of freak nuance with the case pushing the glass or something.
Bought a UAG Case for my phone, few days later I notice the same behavior, bought cases have a small "lip" to protect the screen if you drop the phone face down, I again figured this must be the culprit and bought a new case.
Barely there Clear case by casemate, I have had the case for 3 days and today is my first day at work since, immediately upon connecting my charger I noticed the erratic touch behavior.
At this point I realized it was never the case, it has to be something with charging in general or the specific charger I am using.
Anyone got any clue what is actually causing this issue?
Links to all of the hardware I mentioned in this post for clarification:
iXCC-SMART-Capacity-Travel-Charger/dp/B00HPTU0OU/ref=sr_1_16?ie=UTF8&qid=1410767078&sr=8-16&keywords=2+amp+charger
Hi-Speed-Braided-Tangle-Free-Charging-Motorola/dp/B00HZXYYQ6/ref=pd_cp_cps_2
Case-Mate-Barely-There-Case-HTC/dp/B00IZFYI28/ref=sr_1_1?s=wireless&ie=UTF8&qid=undefined&sr=1-1&keywords=barely+there+htc+one+m8
Spigen%C2%AE-STRONG-FLEX-Release-Capsule-Premium/dp/B00IF5B218/ref=sr_1_6?s=wireless&ie=UTF8&qid=1410767095&sr=1-6&keywords=htc+one+m8+case
URBAN-ARMOR-GEAR-Case-HTC/dp/B00IEFUB3E/ref=sr_1_1?s=wireless&ie=UTF8&qid=1410767120&sr=1-1&keywords=uag+htc+one+m8
EDIT: not enough posts to post links, but if you just insert the standard amazon address in front of all of those you'll get to the items in question.

Hi guys, any news?
I'm experiencing the same issue and this is driving me mad.
Experiencing this with different chargers. My cover is a Spigen Ultra Hybrid Metal Slate...if I put it off, theres no problem while charging
Greetings from Switzerland

Hi guys,
I have faced the issue as well. In my case, if I charge the phone using the dot view case then the touchscreen behaves wrongly. However, if I charge the phone with no case at all it works fine.
Anyway after I flashed the latest firmware (.401.6) the problem is gone. What firmware do you have?
Cheers.

Hi Guys,
For anyone interested, I have just noticed that it happened depending on the charger also.
Cheers.

I have the same problem
Using htc one m8 developer edition 4.4.2. This issue comes with every charger. With or without case or screen protection.

Yep, I've noticed this issue as well. Any solution?

warpkid said:
Yeah it's brand new. Phone is fine off charge and when using other charges. It's just the stock charger tat seems to cause issues.
Click to expand...
Click to collapse
If it's brand new, take it back for a replacement. The sooner the better because the longer you wait, the more they may think it is user caused.

I just got my phone replaced due to bad mic. I had a brand new one on release day and now I got a refurb both suffered the same issues. It's not always that it does it but it certainly pisses you off. Same symptoms as the op describes, I have yet to find a permanent solution.

This is so super irritating. I feel you. I just found out though that it occurs when I have my case on.. So whenever i use the phone when I'm charging I have to pull the case off. It really doesn't make any sense lol but this is my workaround for this bug.

I also have the same problem
It seems to occur when the phone is close to full charge. Every app goes crazy. When I unplug the charger it returns to normal.

jaycaplan said:
It seems to occur when the phone is close to full charge. Every app goes crazy. When I unplug the charger it returns to normal.
Click to expand...
Click to collapse
I have the same issue with mine; I found a website which said to do the following:
Using two fingers swipe down on the status bar then touch the gear icon > Display & Gestures > G-Sensor calibration
Place your phone on a flat surface then touch Calibrate.
After the calibration process has finished tap Ok.
You should also calibrate the finger touch on your screen to deal with the keyboard issue.
Open “Settings” and go to “Language and Keyboard”
Tap “HTC Sense Input”
Tap “Advanced”
Tap “Calibration tool” (Calibrate your screen for a better touch experience)
Now you are asked to type the given sentence
One done, Calibration Complete message appears
Hit “Reset Calibration” to reset screen to factory default
Click to expand...
Click to collapse
It's still present, but it hasn't been as bad - I turned on the visual feedback in the developers settings, and you can watch the cursor fly all about the screen like it's possessed!

Same issue here, on the latest software. This is my second m8 with the same issues.

Android Auto Charging Slowly

This one's huge for me and might warrant a return. My 3 XL when I plug into my Fiesta and Android Auto comes on switches from Charging to Charging Slowly, and I maintain or lose charge over the course of my trip. My 2 XL and first-gen could gain charge no problem. Wasn't Rapid, but was plenty fast.
Anyone else seeing this? This is a huge problem for me. I rely on my car to top off my phone during drives and if this can't happen anymore it kills AA for me.
Edit: There's a thread on Google's own Android Auto forums regarding this issue (apparently for people who actually have USB-C in their vehicles, the problem is ironically worse), and best yet, it has an actual Google engineer interacting and collecting data. Please report your experience here with full details, make/model of car, phone, OS and Play Services versions, etc: https://productforums.google.com/forum/#!topic/android-auto/1NmG3ojHX_k;context-place=mydiscussions
Also, user bigdave79 helpfully reported here that if you plug in your phone, let Android Auto open, and without unplugging go into USB Preferences and toggle from USB Controlled by "This Device" to "Connected Device" it will switch itself right back, but charging speed will return to expectations. While still not a fix, this helps further suggest this is truly a software bug and not a hardware or software feature/decision.

TurboFool said:
This one's huge for me and might warrant a return. My 3 XL when I plug into my Fiesta and Android Auto comes on switches from Charging to Charging Slowly, and I maintain or lose charge over the course of my trip. My 2 XL and first-gen could gain charge no problem. Wasn't Rapid, but was plenty fast.
Anyone else seeing this? This is a huge problem for me. I rely on my car to top off my phone during drives and if this can't happen anymore it kills AA for me.
Click to expand...
Click to collapse
If I'm not mistaken it probably depends on your car. My 2018 Civic can't fast charge because Android Auto run through one specific USB spot. If I used a fast charge car adapter it would but then lose AA

I'm well aware. To reiterate, BOTH previous Pixels had NO trouble with my car. This is specific to the 3 XL.

I'm not having this issue in my car. Using the same USB C car charger I used on my 2XL.

TurboFool said:
I'm well aware. To reiterate, BOTH previous Pixels had NO trouble with my car. This is specific to the 3 XL.
Click to expand...
Click to collapse
I recently purchased a quick charge charger for my car. It worked great with a Note 9, S8+, and a Razer phone. My Pixel 3 XL however, charges slowly. It is kind of annoying.

I think you're all missing the Android Auto part of this. Not a car charger. The USB port built into the car to allow it to connect to Android Auto.

glad i am not the only one who is having this issue.... it charged my s8+ fast but it shows slow charging with pixel 3 xl =\

Well, this is annoying. Same thing on my 3 XL, "Slowing Charging".
Plugged the 2 XL back in- charging normally. Ford Explorer.
Let's hope it is some stupid $hit related to this-
https://www.xda-developers.com/google-pixel-fast-charging-android-pie-fix/
The time frame and Oct release seem to match the build date in the 3 XL I have, so maybe the build of PIE is not synced to the OTA release and the next OTA will fix it? Wishful thinking I suppose..

Google support was worse than useless on this, asking questions in circles and misunderstanding me. That said, thanks to someone on Reddit and my own thinking, I tried enabling USB Debugging. After a reboot of the phone it resolved the issue. AA starts up faster, as well.

TurboFool said:
Google support was worse than useless on this, asking questions in circles and misunderstanding me. That said, thanks to someone on Reddit and my own thinking, I tried enabling USB Debugging. After a reboot of the phone it resolved the issue. AA starts up faster, as well.
Click to expand...
Click to collapse
Thank you for posting, never would have thought about that.

So the problem actually returned, but was resolved again with another reboot. This is very odd. Combined with the severe memory leaks, I have to reboot this phone more than I'm used to.

TurboFool said:
So the problem actually returned, but was resolved again with another reboot. This is very odd. Combined with the severe memory leaks, I have to reboot this phone more than I'm used to.
Click to expand...
Click to collapse
How do you tell what it is charging at now? I can see it on the main screen if the screen is powered off (ambient) and Android Auto isn't running.
The battery dialog screen used to say, maybe I'm in the wrong spot?

d j a said:
How do you tell what it is charging at now? I can see it on the main screen if the screen is powered off (ambient) and Android Auto isn't running.
The battery dialog screen used to say, maybe I'm in the wrong spot?
Click to expand...
Click to collapse
Turn the screen off and back on to look at the ambient screen text at the bottom.

TurboFool said:
Turn the screen off and back on to look at the ambient screen text at the bottom.
Click to expand...
Click to collapse
So all you did was enable USB Debugging through the developer options and your pixel 3 now charges at a similar speed as the Pixel 2 when connected in the car using Android Auto?
I was so hopeful and tried it out this morning but no luck at all. I even rebooted the phone 3 times and still receiving the "Slowly charging" dialog and the phone gained 2% in an hour.

Mastaking said:
So all you did was enable USB Debugging through the developer options and your pixel 3 now charges at a similar speed as the Pixel 2 when connected in the car using Android Auto?
I was so hopeful and tried it out this morning but no luck at all. I even rebooted the phone 3 times and still receiving the "Slowly charging" dialog and the phone gained 2% in an hour.
Click to expand...
Click to collapse
Correct. Could be a 3 versus 3 XL thing, I don't know. But yes, enabled that function, restarted, and it immediately stayed on Charging. It later returns to the bad behavior, so I basically have to restart my phone every time I enter the car.

I'm seeing the same thing. I have had developer options enabled since first day and have never seen it show rapid charging. Even with the original charger I am seeing charging slow. Since the Pixel 3 is on Sept build it is most likely the same issue as the pixel. Hopefully this will be fixed in the next update.

I too am experiencing issues with AA and a Pixel 3 XL.
1) 2014 Cadillac CTS V-Sport Premium with Cue. The phone connects and AA works just fine; however the phone shows "charging slowly".
2) 2000 Dodge Dakota R/T with a Pioneer AVH-2300NEX; latest firmware version 8.35. The phone will not establish a connection to the head unit via USB, and battery indicator flashes between charging and not charging.
I still have my Pixel 2 XL, which performs flawlessly in the CTS. Same cable, same port. The P2 XL reports "charging", and gains a charge when AA is in use.
In the Dakota, the P2 XL also performs flawlessly since the 8.35 firmware update. Again, same cable, same port. Just like the in the CTS, the P2 XL reports "charging" and gains a charge while AA is in use.
It is to be noted that developer mode is enabled on both phones, and USB debugging is "on" (both phones). I have tried the whole restart thing; to no avail.

I've initiated a return process. Since Google's unable to offer any indication of this problem being known to them or a solution being planned, I can't go forward like this. I like this phone quite a bit, but its experience isn't so dramatically better from my 2 XL as to justify putting up with a problem with no expected solution. I'll keep my eye on updates and see if any indicate this issue has been seen and fixed and maybe consider a repurchase then. Otherwise I'll hold out for the 4.

TurboFool said:
I've initiated a return process. Since Google's unable to offer any indication of this problem being known to them or a solution being planned, I can't go forward like this. I like this phone quite a bit, but its experience isn't so dramatically better from my 2 XL as to justify putting up with a problem with no expected solution. I'll keep my eye on updates and see if any indicate this issue has been seen and fixed and maybe consider a repurchase then. Otherwise I'll hold out for the 4.
Click to expand...
Click to collapse
Mine went to FedEx today. Sadly, I love the phone but already got an RA for it prior to the return window expiring. I am not confident that Google will fix the issue in a timely manner; or even acknowledge there is one. For $1000, I am not willing to go backwards in functionality. If I see proof the issue is resolved, then like you; I may decide to repurchase. If not, the P2 XL still has another year of warranty and 2 years of support.

SmoovC said:
For $1000, I am not willing to go backwards in functionality. If I see proof the issue is resolved, then like you; I may decide to repurchase. If not, the P2 XL still has another year of warrany and 2 years of support.
Click to expand...
Click to collapse
Exactly that. I spent a lot of money on a phone to replace a very good phone. There should be no regressions for that price.
Oh well, my 2 XL was fantastic, truly. I'll probably need a few days to readjust to the screen and a month or two to wait for most of the new features to filter back to it, and I'll be fine until next year.