Related
Hi there,
(Im opening a new thread as the old one was completely off the topic of the original post)
So on CM11S, my phone screen was working fine. After the CM12S update, my phones screen sometimes doesn't respond correctly when I go to unlock my phone with the unlock pattern. (The timing of the update and the problem occurring may just be coincidence) Its as if holding your finger on the screen isn't registered as staying on the screen, its like the phone thinks I am lifting my finger off and reapplying it very quickly, I cant draw my unlock pattern and unlock my phone. It also affects the 'swipe down' I must do to get the unlock pattern prompt.
If I restart my phone, it usually fixes the problem. Although in the past few days, it has started happening more frequently and sometimes restarting the phone doesn't solve the issue. It is becoming more of a frustration now because of how frequently I have to restart my phone just to unlock it.
I first believed that using a glass screen protector was the problem, I thought the glass was causing ghost touches, so I removed my glass protector and replaced it with a film protector, at first it seemed that this was the problem, but I have just encountered the problem again. I'm not sure if its a hardware or a software issue, because restarting the device is fixing the problem most of the time, but its also switching off all power to the digitizer during a reboot so I cant tell what is the culprit.
I've opened a support ticket with OnePlus but it says it can be up to 10 days before I get a reply, I figured I'd post here too to see if anyone else has had similar issues or even found a fix.
Thanks in advance!
I had the same problem
I was having the same issue, although I never updated to CM12S. Instead, this happened to me when running Exodus Lollipop ROM and the SlimLP ROM. Since then, I have switched to Paranoid Android Alpha2 and have not had the issue recur in the last few days running PA. So to me it seems like a software glitch in many of the Lollipop ROMs. Try PA if you like and see if it's fixed.
welcome to ghost touch
google "oneplus one ghost touch" and join the hundreds of other known cases
I had a feeling this was the ghost touch issue, but my phone hasn't really had actual ghost touches, its just that most of screen stops working. I've got a few videos of it happening. First the screen goes a bit unresponsive, then after a short while, about 1/3 of the screen is completely unresponsive, I switched on show touches in development options and you can see that from the middle to the bottom of the screen there is no response unless I use the very edge on the right side, then it works, its like it has a dead spot. If I reboot my phone, that usually fixes the problem for a while, sometimes up to a whole day, but the problem comes back with time.
I was given a patch by the OnePlus automated support message, and it says my case has been forwarded to a specialist. I have just applied the patch which has rolled me back to CM11, I'm guessing it did more than just that, but the patch and notes don't really explain what it does. Either way, I'm in the process of receiving OTA updates so I can get back on CO12 so I can hopefully restore my data with my ADB backup (never done this before, not rooted my One yet)
Has anyone had any success with this patch?
Thanks
EDIT: So my ADB Backup isn't restoring on my phone. I am using Holo Backup (formerly Simple ADB Backup) and when I chose restore and select the backup, it just show the output for the help command from ADB and then doesnt appear to do anything else. Are there any manual commands to restore my backup or have I done something wrong?
Try going back to cm11s and then check...
Sent from Android (a google product)
Hi there,
So heres an update, I applied the first patch and it rolled me back to CM11S and the issue was still present on CM11S, I then got OTA's back up to CO12 and the issue still happens. I have turned off the off screen gestures and the ambient wakeup thing. It doesn't happen as often but when it happens, 2 restarts are needed to get it running smooth again.
My support ticket with OnePlus has gone quiet and I don't really know what my next step is? I have heard there is a second patch but I couldn't backup properly last time with ADB so I don't know if I want to go through all of the wiping and reupdating again when people report the 2nd patch is also ineffective.
Does anyone have any suggestions? I feel a bit cheated now knowing that my phone has what I can tell to be a manufacturing defect / hardware issue.
Another update here.
So after a week of silence from the OnePlus tech support, I have a new person handling my ticket and he has told me that I need to apply another display patch. I'm guessing this is the 2nd patch and not this final patch which was mentioned by Carl on Facebook.
Either way, I ran into a problem applying the 1st patch, I couldn't make a proper backup of my phone before I did the patch. I used SimpleADBBackup which I thought would work well but it took a very long time to create the backup and then when I applied the backup back onto my newly flashed phone, It missed many apps, only did app data for a few apps and didn't take any of my pictures or SD storage, so all my SMS and Call log backups were also lost. I would like to take a proper backup this time but I don't know how to do it? I don't trust this ADB backup method, even on the Simple ADB Backup program, it admits that ADB backups are hacky and untested.
I have been trying to use Helium but for some reason, my phone wont get past connecting it to the computer companion app, I have all phone drivers and ADB drivers installed correctly, but helium on the android side cant seem to see the computer app, the computer side of the app says that helium is enabled, but on my phone it is stuck on "waiting for the helium desktop app".
I feel like I'm having the worst luck with this phone, and its frustrating because I really like this phone and this flaw is really getting in the way of using this phone, I counted 8 restarts in one day due to the screen not working.
I hope someone can help me out, I don't want to fully wipe my phone again and I cant seem to back anything up correctly!
One more here... when everyone had the probelms, my screen works almost good... now trying the nightli from Cm... the problems become mroe and more big... ( than soon it is oneplus two? xD Its not in my mind waste more money on OPO company... jajajaja Any solution? we waiting for the miracle update they promised?
naghtan said:
One more here... when everyone had the probelms, my screen works almost good... now trying the nightli from Cm... the problems become mroe and more big... ( than soon it is oneplus two? xD Its not in my mind waste more money on OPO company... jajajaja Any solution? we waiting for the miracle update they promised?
Click to expand...
Click to collapse
I'm not sure if a full solution has been found yet. I read on Facebook that they are working with Synaptics to make a final patch which should solve the issue.
I've given up on trying to backup my phone without root, it just seems impossible to do right. I've just applied the 2nd display patch and got my phone running again, I think I may stay on CM11 and just forget lollipop until this issue gets resolved. I'm pretty sure last time I was on KitKat, the issues were there still but it may be less frequent, who knows?!
Do I have a better chance of seeing this screen issue less on KitKat or should I just update to CO12 for the 3rd time?
Another update here,
I have been instructed and have booked a remote session with OnePlus. I'm guessing they are going to be flashing CO12 or OxygenOS and hopefully some kind of display patch or calibration fix. I really hope this solves my problem, the issue has become a daily occurrence and I have also finally seen a ghost touch, it looked like it was trembling . I really love this phone apart from this issue but it happens way too often to ignore it. Ill post what happens after the session.
donk165 said:
Another update here,
I have been instructed and have booked a remote session with OnePlus. I'm guessing they are going to be flashing CO12 or OxygenOS and hopefully some kind of display patch or calibration fix. I really hope this solves my problem, the issue has become a daily occurrence and I have also finally seen a ghost touch, it looked like it was trembling . I really love this phone apart from this issue but it happens way too often to ignore it. Ill post what happens after the session.
Click to expand...
Click to collapse
You may can check this while you wait for support..
https://www.reddit.com/r/oneplus/comments/361dr7/how_to_fix_your_touchscreen_issues_if_you_are_on/
vickykolari said:
You may can check this while you wait for support..
https://www.reddit.com/r/oneplus/comments/361dr7/how_to_fix_your_touchscreen_issues_if_you_are_on/
Click to expand...
Click to collapse
Thanks for this, I'm not going to root yet though because I think I'm finally at the stage where I can start the RMA process, I have a new video of the touch screen being unable to maintain a touch and drag gesture, and then another video doing the same action but just after restarting my phone - it works fine after the restart.
During this support session, I was flashed onto Oxygen OS and I really miss CO12 now, so many features that I grew accustomed to are not present in Oxygen. Oxygen does seem quite solid, but I've gotten way too used to all the features of Cyanogen.
Oh well, ill live with it until I get another reply from the support team.
I write with the assistance for 10 posts at today and I declare them to STOP sending me those bug non fixing ROMS/ZIPS...
I will replace by myself the screen (they don't change it in warranty because I've on the frame some dents... )
It's a clear HW issue, on any software, if the display degrade to a "fail stage" you wan't come back never to a total solve situation.
I loved my Oneplus, but they buy some batches of too cheap display, and after some month, I see clearly the results.
donk165 said:
Thanks for this, I'm not going to root yet though because I think I'm finally at the stage where I can start the RMA process, I have a new video of the touch screen being unable to maintain a touch and drag gesture, and then another video doing the same action but just after restarting my phone - it works fine after the restart.
During this support session, I was flashed onto Oxygen OS and I really miss CO12 now, so many features that I grew accustomed to are not present in Oxygen. Oxygen does seem quite solid, but I've gotten way too used to all the features of Cyanogen.
Oh well, ill live with it until I get another reply from the support team.
Click to expand...
Click to collapse
I wish you all the luck mate..
vickykolari said:
I wish you all the luck mate..
Click to expand...
Click to collapse
Thanks man,
It went well, I have been issued an RMA and will be sending it back soon. Just waiting on the postage label.
Ive just received my new OnePlus One today, very chuffed as it hasn't cost me anything. RMA and Support with OnePlus may be a bit slow but at least they do the right things!
To anyone facing screen issues, create a support ticket and persist with it, it should pay off!
Flash the latest CM 12 nightlies and you're good to go
Sent from my A0001 using Tapatalk
anugrah n3xu5 said:
Flash the latest CM 12 nightlies and you're good to go
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Your a bit late here man, that phone has been sent back and I'm on my 2nd OPO now, using the latest official CO12 build with these touchscreen fixes. No touchscreen problems on this phone.
donk165 said:
Your a bit late here man, that phone has been sent back and I'm on my 2nd OPO now, using the latest official CO12 build with these touchscreen fixes. No touchscreen problems on this phone.
Click to expand...
Click to collapse
Congrats! Enjoy the beast
Sent from my A0001 using Tapatalk
Hey guys!
I have posted before but since then the issue has exacerbated to the point where I'm at my wit's end.
I have the SM-P907A AT&T version of this tablet. I bought it second hand and started experiencing issues almost immediately, although nothing as bad as what I'm going through now.
It began with the odd blue-screen and very rare restart. It quickly escalated when I created multiple profiles (user ids). The restarts would happen entirely randomly but without fail within 10 minutes of operation no matter what I did. Oddly enough, it would NEVER restart when connected to a power supply, though I have drawn very little from that.
Thusly, I factory reset my tablet and hoped that would fix the issue; to no avail. Then I decided to Odin flash the stock ROM. Again no joy. Restarts were persistent and regular when the tablet wasn't connected to a power supply. I then rooted the tablet, installed Titanium Backup Pro and proceeded to freeze all apps/odex-es related to Samsung Knox. As some have posted, doing this helped them out. Not lucky enough, I guess.
My questions:
Did my setting up multiple users somehow mess with the tablet in such a deep and integrated way that even factory resetting, re-flashing stock would not help? Is that even possible? My firmware version is P907AUCU1AND7. I'm going to manually update to Lollipop but if my meddling with the multiple users "broke" something essential, will that help?
No, proppably not
kalaris said:
Hey guys!
My questions:
Did my setting up multiple users somehow mess with the tablet in such a deep and integrated way that even factory resetting, re-flashing stock would not help? Is that even possible? My firmware version is P907AUCU1AND7. I'm going to manually update to Lollipop but if my meddling with the multiple users "broke" something essential, will that help?
Click to expand...
Click to collapse
I don't think that using the multi user functionality has anything to do with the issues you are experiencing. I have 3 user on my tablet and using it for a year now. Both on KitKat and Lollipop that I am using now. Both rooted, KitKat with Xposed also. Never had issues with blue screens and reboots.
Issues with US devices have been posted regularly and explanations have been posted. Don't focus on multiuser for the issues you experience.
I' am using the SM-P905 International version (EUR)
PDA: P905XXUABOG1
CSC: P905EURABOG1
Ridiculous
Okay guys. Seriously ridiculous. I downloaded the lollipop ROM but got an error when adb sideloading it because it requires the previous firmware P907AUCU1ANK2 for it to update properly whereas I have the one older than that: P907AUCU1AND7.
Can someone help a brotha out? Post a link from where I can download it?! Maybe share their stock rom file?! Pretty please? I've managed to find only TWO results on google. One is a mobilefileserver result requiring that I Pay $60. The other is a Chinese site requiring that I pay significantly less but in a way which is baffling me at the moment.
Any good guy out there who can help??????
A member posted links to it in 5.1.1 upgrade posts...
Sent from my SPH-L300 using XDA Free mobile app
zomg! thank you! how'd i miss this?!
kalaris said:
The restarts would happen entirely randomly but without fail within 10 minutes of operation no matter what I did. Oddly enough, it would NEVER restart when connected to a power supply, though I have drawn very little from that.
Click to expand...
Click to collapse
Random restart is the problem of cracked battery connector. Re solder the battery connector will fix it permanently.
Read the thread " Flickering Screen " in Galaxy Note or Tab Pro, you will see they all have similar problem like yours and the fix is simple.
No software or upgrade will fix the hardware problem, regardless Kitkat or Lollipop.
Hi guys, I am currently experiencing a very annoying problem on my OnePlus One. If I go to a place with bad reception or no mobile data available, my phone won't automatically get connection on good reception area before I reboot it.
Let's say I have good signal strength and working mobile data on my room, but my kitchen has bad signal strength and no mobile data. If I went to the kitchen and let the phone loses reception and mobile data, then go back to my room, my phone will have no reception and no mobile data unless I reboot it. Usually I can just turn on Airplane mode and turn it off so my phone can reinitialize the reception but not anymore.
I noticed this problem since I flashed Cyanogenmod Snapshot 13.0-20160819 (ZNH5YAO0IN). This problem is very annoying especially when I am outside because I often found myself missing lots of Whatsapp texts since I don't realize my phone doesn't have any mobile data.
What do you suggest to fix this problem? Any help is appreciated.
Try changing rom?... We have lots of good Nougat ROMs.
You can flash a new modem, go through the one plus one sections.Only if you're rooted.
Else you try formatting the phone, obviously with data backup.
Hope it'll help. Thanks
nokkenas said:
Hi guys, I am currently experiencing a very annoying problem on my OnePlus One. If I go to a place with bad reception or no mobile data available, my phone won't automatically get connection on good reception area before I reboot it.
Let's say I have good signal strength and working mobile data on my room, but my kitchen has bad signal strength and no mobile data. If I went to the kitchen and let the phone loses reception and mobile data, then go back to my room, my phone will have no reception and no mobile data unless I reboot it. Usually I can just turn on Airplane mode and turn it off so my phone can reinitialize the reception but not anymore.
I noticed this problem since I flashed Cyanogenmod Snapshot 13.0-20160819 (ZNH5YAO0IN). This problem is very annoying especially when I am outside because I often found myself missing lots of Whatsapp texts since I don't realize my phone doesn't have any mobile data.
What do you suggest to fix this problem? Any help is appreciated.
Click to expand...
Click to collapse
This is a fairly common problem with the OnePlus One. It's caused by the modem version you're on. For some (including myself), the problem can be fixed by flashing the c7 modem vs the older c6 ones. But, do be warned, for some this wipes out all radios on your device (Bluetooth, wifi, LTE, etc. all break). So before you try flashing new modems, make sure you have a copy of the one your phone currently has so you can flash it in the event that your radios stop working. (I want to say a nandroid backup doesn't actually save/restore the modem firmware). Do some googling in that direction. Might just lead to a fix.
Sent from my A0001 using Tapatalk
Elius2676 said:
This is a fairly common problem with the OnePlus One. It's caused by the modem version you're on. For some (including myself), the problem can be fixed by flashing the c7 modem vs the older c6 ones. But, do be warned, for some this wipes out all radios on your device (Bluetooth, wifi, LTE, etc. all break). So before you try flashing new modems, make sure you have a copy of the one your phone currently has so you can flash it in the event that your radios stop working. (I want to say a nandroid backup doesn't actually save/restore the modem firmware). Do some googling in that direction. Might just lead to a fix.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Pardon my lack of knowledge with modems, but which one from this thread can I flash? I see some marked as H20 or Oxygen update, are they tied to that specific ROM or will they work on any ROM?
They're not ROM specific. They're device specific. You'll just want to try the c7-13 one, I'm guessing. Just keep in mind the cautions I said previously.
Sent from my A0001 using Tapatalk
Elius2676 said:
They're not ROM specific. They're device specific. You'll just want to try the c7-13 one, I'm guessing. Just keep in mind the cautions I said previously.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
I saw a fellow member on the same country as me flashing the C7-11 (latest available on Modem Collection thread) and it worked for him so I figured I might give it a try. So far so good, not a single problem. But hey, thanks very much for pointing me to the right direction! I was close to change my ROM and wipe everything.
Edit: 5 days passed, not a single problem encountered. Suggested fix is proven.
Hello XDA!
I'm having some issues with the wi-fi, and bluetooth, connectivity on my GM-930F S7 (Non-edge) phone.
The wi-fi issue is that it occasionally disconnects, and when I try to re-connect, it either doesn't work (quickly goes through the motions, but doesn't connect), or lists the hotspot as "disabled". I had no issues with this on my backup Note, nor on my older S5.
The bluetooth issue is that if the phone doesn't seem to have a direct line-of-sight to the earphones then the audio almost immediately drops out and begins to stutter/drop seconds of audio, like somebody is bashing the mute-button.
I think both of these issues are related, potentially they share the same radio. I do have a HDSPA+ connection when I'm out and about, so that works, but I do think perhaps I've got a mismatched radio/setting somewhere which is screwing with those two.
I've already tried to return to stock, twice, using two separate ROMs flashed through Odin (BTU-G930FXXU1DPLT-20170117160813, & G930FXXU1DQE7_G930FEVR1DQD1_EVR) (I'm with EE), and I've also tried a myriad of other roms, (AOKP, AOSPExtended, ResurrectionRemix, SlimRom, Linage 14.1), however none of them seem to solve the issue.
My question is has anybody experienced an issue like this before? Are there any specific radios or things you'd recommend I flash, either via TWRP or Odin? Any more details I can provide?
Just so I'm clear, the wi-fi and bluetooth worked beautifully on my S5, so I have no reason to believe that hardware is at fault, it's very likely the phone.
I've also just tried it with a MM rom (G930FXXU1APAW_G930FOXA1APBA_BTU) and the same issue occurs.
Seems like faulty hardware. I am using superman ROM and no problems so far. I mean, i doubt you will fix it by changing ROM. You should bring it to the service.
Sent from my SM-G930F using Tapatalk
pakidermo5000 said:
Seems like faulty hardware. I am using superman ROM and no problems so far. I mean, i doubt you will fix it by changing ROM. You should bring it to the service.
Sent from my SM-G930F using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply! I don't think it's hardware, if it was then the wi-fi/bluetooth would either work, or not work. I mean if I keep the phone close to the earphones the bluetooth is fine, but if it's arms length away, or there isn't a line-of-sight, it drops, the wi-fi is similarly spotty, but not working/broken. I had a similar issue on my old S5, I ended up solving it but I can't remember how, it was years ago. However it certainly was a software issue. Either ROM, or Kernel, or Modem/CP, etc.
I see lots of comments from people about the issue occurring once they upgrade to Nougat, so I'm very sure it's software. Possibly an issue with the Kernel or Modem, or a combination of both.
Would it be possible (minus the EFS of course) to get an upload of your setup so I can try with your exact settings? I've tried the SuperMan ROM before, but I'll give it another go now.
Also (Although it isn't 100% solved), I've found trying out the ROM "[ROM] S8 FULL PORT FOR S7 & S7 EDGE by ambasadii [AQEB] [v3.1]" noticeably increases the range that the bluetooth works over. It still isn't a large range, but it more than doubles it. I've gone back to previous ROMs I've tried, speaker and phone in the same place, and it doesn't transmit that far, back to the S8 Port, and it does. I've no idea what could be causing this and it's really bothering me. I know the S8 has upgraded bluetooth software, but this speaker worked fine with my S5.
BarrettBear said:
Would it be possible (minus the EFS of course) to get an upload of your setup so I can try with your exact settings? I've tried the SuperMan ROM before, but I'll give it another go now.
Click to expand...
Click to collapse
What do you need exactly? I have the exynos version.
Sent from my SM-G930F using Tapatalk
pakidermo5000 said:
What do you need exactly? I have the exynos version.
Sent from my SM-G930F using Tapatalk
Click to expand...
Click to collapse
As do I
Ideally just a snapshot of your system, minus all the personal information and such - if your bluetooth works fine with your modem/rom/bootloader/etc and it doesn't on mine, then at least I can be reasonably sure it is a hardware issue, in which case I'll have to try to get it mended.
The reason I'm not 100% sure is the S8 ROM extended the BT range to what other S7 ROMs haven't, so I'm still not 100% sure.
I have been fighting problems with my widgets freezing, as well as updates from the Play Store freezing, for a long time, on my Note 9, which on on V9 of Android.
Doing a complete factory refresh fixes the problem, temporarily. All searchs turn up instructions to clear cache, etc, to no avail.
I finally did a global search on XdA and found this thread based on a Xiaomi Mi 8 with Miui 9.6.3 having the problem with the Play Store. The 'fix' was to turn off blue tooth, and reboot.
I have tried that, and what do you know...that fixes the problem...until I need blue tooth turned on.
So, I"m thinking this is a general Android problem, given it is on two different brands of phones, with two different mfgr updates, and different versions of Android.
Anyone else know of this issue, and of any fix? I'm thinking maybe Google needs to address it, and likely is not aware of the problem. I have no idea how to communicate it to Google, and no expectation that they'd pay attention to me.
ewingr said:
I have been fighting problems with my widgets freezing, as well as updates from the Play Store freezing, for a long time, on my Note 9, which on on V9 of Android.
Doing a complete factory refresh fixes the problem, temporarily. All searchs turn up instructions to clear cache, etc, to no avail.
I finally did a global search on XdA and found this thread based on a Xiaomi Mi 8 with Miui 9.6.3 having the problem with the Play Store. The 'fix' was to turn off blue tooth, and reboot.
I have tried that, and what do you know...that fixes the problem...until I need blue tooth turned on.
So, I"m thinking this is a general Android problem, given it is on two different brands of phones, with two different mfgr updates, and different versions of Android.
Anyone else know of this issue, and of any fix? I'm thinking maybe Google needs to address it, and likely is not aware of the problem. I have no idea how to communicate it to Google, and no expectation that they'd pay attention to me.
Click to expand...
Click to collapse
If you are using a custom ROM, it is probably something in the ROM that the ROM developer needs to fix, in this case, you will have to get the developer to fix this issue in the ROM itself. Post details of the issue in the thread where you got your ROM.
If you're using stock, it probably isn't something that involves Google's part of your stock firmware, it is probably something caused by your manufacturer's part of your stock firmware.
What I mean is, android devices have Google's base android OS on them, but they also have things on top of the base OS that is put there by the manufacturers and/or carriers, such as the UI that your device uses, some manufacturers use their own UI instead of the stock Google UI.(i.e. TouchWiz UI for Samsung devices, Sense UI for HTC devices, etc).
If this is the case, you need file a bug report to your specific device's manufacturer or to your specific carrier.
Sent from my SM-S767VL using Tapatalk
Yes, I am using a stock ROM. I will try notifying my carrier, although I find it interesting that the Chinese brand Xiaomi has the same problem. I don't think that would be sourced by my carrier, AT& T.
ewingr said:
Yes, I am using a stock ROM. I will try notifying my carrier, although I find it interesting that the Chinese brand Xiaomi has the same problem. I don't think that would be sourced by my carrier, AT& T.
Click to expand...
Click to collapse
That may or may not be for the same reason, maybe the two devices have the same bluetooth components and use the same drivers in the kernel, the kernels also could or could not be the same.
Sent from my SM-S767VL using Tapatalk
Well, at any rate, I guess I may dump this Note 9. I do find consistently that turning BT off it works fine, but I need BT on a lot, and it's wearing out fast to be thinking of turning it on and off.
BTW...I don't recall if I mentioned it, but my wife has a Note 9 too. I had it first, and experienced this problem. WE swapped to see what happened. Still have the problem, so both phones have it.
IN her case, she doesn't use many apps, doesn't care about updating apps, but turning BT off to do so is no problem. Only time she used BT is in the car.
Just an update...
I ended up going back to the N.ote 9. It's been working flawless for quite a while. I had decided whatever was causing the issue got fixed... But it's back tonight. And, turning off Bluetooth does NOT fix it this time.
Really frustrating.
Interesting thing...so I reloaded the Note 3-4 times trying different things. Couple interesting things I noted:
One test was to factory reset, load zero other apps, and check Play Store. It had severa apps to upead. I selected update all, and the freeze happened on the very first app. So this confirms it is not any of the third party apps that I use that is causing this.
By late evening, I had restored my phone to the way I use it. There were 20 apps that needed updating. It was stuck on the first one at 99% for 2 hourse when I went to bed.
When I got up this morning, all had updated...6 hours earlier. So at around 2:30 all apps updated one right after the other.
This feels like the PS is holding back the updates until some unknown parameter is met.
I have searched and spent a few hours reading posts about this problem. It apparently is prevalent, for years. Most of the posts talk about erasing cache and data for PS and/or Download Manager. Those and nothing else suggested is working. It's interesting that it seemed that turning off blue tooth would allow PS to work fine...a few months ago, but not now.