Related
Hi Guys,
I have a question about the update to version 4.1.2.
When I go to Settings > About > System update, I see that the update to 4.1.2 is found but it says that it is waiting to download but it stays like that forever and nothing happens.
Has anyone else seen such behavior? Do you know why it is happening and if it is normal?
Thanks!
Maybe a stupid question but... are you connected to WiFi when you see the message?
b00mb00mchuck said:
Maybe a stupid question but... are you connected to WiFi when you see the message?
Click to expand...
Click to collapse
Yes, of course I am
I also forgot to mention that I am fully stock, unrooted and locked.
wyvorn said:
Hi Guys,
I have a question about the update to version 4.1.2.
When I go to Settings > About > System update, I see that the update to 4.1.2 is found but it says that it is waiting to download but it stays like that forever and nothing happens.
Has anyone else seen such behavior? Do you know why it is happening and if it is normal?
Thanks!
Click to expand...
Click to collapse
Make sure you have a good WiFi connection. The WiFi in my dorm shows a good connection (String signal) but the internet can sometimes timeout easily. Make sure your connection to the internet is superb.
wyvorn said:
Yes, of course I am
I also forgot to mention that I am fully stock, unrooted and locked.
Click to expand...
Click to collapse
Taking a quick look at your wifi icon its not transferring or receiving data. No black arows inside..
Sent from my Nexus 7 using Tapatalk 2
mattrmay said:
Make sure you have a good WiFi connection. The WiFi in my dorm shows a good connection (String signal) but the internet can sometimes timeout easily. Make sure your connection to the internet is superb.
Click to expand...
Click to collapse
My connection is very good. For just in case, I put the Nexus besides the wifi router and still nothing happens.
Omar04 said:
Taking a quick look at your wifi icon its not transferring or receiving data. No black arows inside..
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Yes, I know what the arrows mean but my question is why this is happening? Is there a way for me to force the download? Or maybe I just have to wait more (it's been like this since yesterday)?
Try powering off the Nexus and then starting it up again. If that doesn't work, try using the technique to trick it into updating mentioned in this thread (yes, it's for a different situation but still worth a shot)
http://forum.xda-developers.com/showthread.php?t=1930603
Sent from my MB860 using xda app-developers app
wyvorn said:
My connection is very good. For just in case, I put the Nexus besides the wifi router and still nothing happens.
Yes, I know what the arrows mean but my question is why this is happening? Is there a way for me to force the download? Or maybe I just have to wait more (it's been like this since yesterday)?
Click to expand...
Click to collapse
Take a look at this thread:
http://forum.xda-developers.com/showthread.php?t=1934670
AnotherBill said:
Try powering off the Nexus and then starting it up again. If that doesn't work, try using the technique to trick it into updating mentioned in this thread (yes, it's for a different situation but still worth a shot)
http://forum.xda-developers.com/showthread.php?t=1930603
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
Hey, thanks for the suggestions. I tried powering off and on and it didn't work.
Then I tried the method to force stop the Google Services Framework and when I went to the System updates screen, I had the option to check for updates. I checked and I am back to where I was before - the update shows but is only "waiting to download"
wyvorn said:
I also forgot to mention that I am fully stock, unrooted and locked.
Click to expand...
Click to collapse
Not really a solution but why are your locked?
Sent from my Nexus 7
krelvinaz said:
Not really a solution but why are your locked?
Sent from my Nexus 7
Click to expand...
Click to collapse
probably because he isnt in to rooting?? and just wants his update. not everyone on XDA unlocks and flashes im sure.
krelvinaz said:
Not really a solution but why are your locked?
Sent from my Nexus 7
Click to expand...
Click to collapse
Well, I bought the N7 recently and I want to see how it feels without rooting and custom roms. But later on, I will most probably unlock it.
Hi everyone. I have the same problem with the download. Mine N7 is also stock. Tried the method with the framework multiple times, tried to restart, tried another internet, still no luck in downloading. Any further suggestions?
svetlio89 said:
Hi everyone. I have the same problem with the download. Mine N7 is also stock. Tried the method with the framework multiple times, tried to restart, tried another internet, still no luck in downloading. Any further suggestions?
Click to expand...
Click to collapse
Same issue here! I see the update, but it's waiting to download forever. Could this be connected to the location? Same as the the other guy I'm located in Sofia, Bulgaria.
spooooky said:
Same issue here! I see the update, but it's waiting to download forever. Could this be connected to the location? Same as the the other guy I'm located in Sofia, Bulgaria.
Click to expand...
Click to collapse
Yeah, I'm starting to think the same, as I am in Sofia too.
Anyway, I could not find a solution, so I rooted and installed CM10, so no issue for me anymore.
Another one from Sofia. Waiting to download and after some time... unable to download.....
Sent from my Nexus 7 using Tapatalk 2
Hi
I have a Galaxy Tab 2 which I had originally put omni-4.4.2-20140509 on.
After the installation (as soon as the device is turned on) it kept telling me the Bluetooth Share had stopped.
This error keeps coming up for a 1 minute or so no matter how much I click OK.
If after the error has gone I try to turn bluetooth on, the error comes back up again.
The error was getting so annoying that I disabled bluetooth share in the app manager.
I installed omni 4.4.4-20140708 hoping this would fix the issue but it hasn't and now I'm at a loss as to how to fix this after spending hours searching the web.
Please can someone help with this.
Many Thanks
Still an issue
This issue is still causing a problem even with the latest nightly release.
Please can some one help with this
Thanks
ashsense said:
This issue is still causing a problem even with the latest nightly release.
Please can some one help with this
Thanks
Click to expand...
Click to collapse
As of this date I haven't seen a solution.
ranges said:
As of this date I haven't seen a solution.
Click to expand...
Click to collapse
I had another issue crop up which meant I had to factory reset and reinstall the rom .
Bizarrely after doing this the issue didn't return even though I did this when the issue first appeared.
Glad I now have my Bluetooth back
Hi,
I'm sorry if it's a trivial question that has been asked million times before -- referring as an exact duplicate is also appreciated.
I have a Galaxy S5 device and I'm experiencing troubles with it with the following symptoms/scenario:
* The device works fine in general.
* The device screen gets totally black if the device turns the screen off after a certain period of time that's configured in Settings.
** The device seems to work though, and to react on awaking with the Power button. A: I assume it works behind the black screen because I can see the bottom buttons highlighted for a while. B: However, I'm not sure what happens if making screenshots the device using adb -- I haven't checked it yet.
** The device cannot reboot within a certain amount of time: up to 30 minutes (boot loop). When the period ends up, the device can boot again.
* If the device gets asleep after pressing the Power button, I can awake it and it works fine.
So, the general rule is to make sure that the device does not gets asleep itself and does not get into "coma".
The workarounds I could find so far:
* Install an app that merely does not let the device sleep so the screen is constantly turned on.
* Increase the sleep timeout up a reasonable amount of time (say, 10 minutes) and not forget to press the Power button within this period.
The question is: why does it happen and how do I resolve this issue? I mean: why does screen not get turned on when I try to awake it after it gets asleep itself?
Android 6, the stock firmware, no root.
Thank you in advance!
Are you using a 3rd app in order to gain in battery or performances?
fgth90 said:
Are you using a 3rd app in order to gain in battery or performances?
Click to expand...
Click to collapse
Thank you for the feedback. No, never: the scenario I described in the question can happen even after re-flashing a stock firmware (Android 5 or 6 --- the version does not really matter).
hurricane flow said:
Thank you for the feedback. No, never: the scenario I described in the question can happen even after re-flashing a stock firmware (Android 5 or 6 --- the version does not really matter).
Click to expand...
Click to collapse
Did you wipe everything before flashing your new firmware?
fgth90 said:
Did you wipe everything before flashing your new firmware?
Click to expand...
Click to collapse
Yes, absolutely.
hurricane flow said:
Yes, absolutely.
Click to expand...
Click to collapse
Hum...
When you screen off with power button, then screen on with power button after short time, it works, right?
---------- Post added at 09:20 AM ---------- Previous post was at 09:16 AM ----------
hurricane flow said:
Yes, absolutely.
Click to expand...
Click to collapse
What's your phone model and what's your firmware?
fgth90 said:
Hum...
When you screen off with power button, then screen on with power button after short time, it works, right?
Click to expand...
Click to collapse
Yes, it works when I turn off the screen with power button myself. I can turn on it later even after a long period of time.
But when the screen is off by Android itself (I mean after an inactivity period), then, when I try to turn it on, the device seems to work and even react the screen taps (I guess since I haven't check it with `adb shell screencap` yet). The only difference is that the screen is off in such case, so I can't see anything.
hurricane flow said:
Yes, it works when I turn off the screen with power button myself. I can turn on it later even after a long period of time.
But when the screen is off by Android itself (I mean after an inactivity period), then, when I try to turn it on, the device seems to work and even react the screen taps (I guess since I haven't check it with `adb shell screencap` yet). The only difference is that the screen is off in such case, so I can't see anything.
Click to expand...
Click to collapse
What's your phone model and what's your firmware?
Maybe you should try to flash a different firmware from sammobile.
Don't forget to wipe everything, including system of course.
Maybe cleaning your sdcard as well (but I don't know why it should interfere).
Is your problem recent, I mean only existing after your last firmware flash?
fgth90 said:
What's your phone model and what's your firmware?
Click to expand...
Click to collapse
Not sure if I'm giving all necessary info, but I hope it's what necessary:
Software version: G900PVPS3CQA2
Hardware version: G900P.04
Device name: Galaxy S5
Model number: SM-G900P
Android version: 6.0.1
Baseabnd version: G900PVPS3CQA2
Kernel version: 3.4.0-10090296 [email protected] #1 Tue Jan 10 14:50:06 KST 2017
Build number: MMB29M.G900PVPS3CQA2
fgth90 said:
Maybe you should try to flash a different firmware from sammobile.
Don't forget to wipe everything, including system of course.
Click to expand...
Click to collapse
I tried to flash another firmwares a few times, but if the device was fine with them, then the describe issue persisted, so it made me think that I was using wrong firmwares. It's hard to say if I have a wrong one now, but it works except of that issue...
fgth90 said:
Is your problem recent, I mean only existing after your last firmware flash?
Click to expand...
Click to collapse
No, it's not recent per se: I had a well-working device with stock firmware for very long period, and suddenly got a reboot and forever bootloop. Flashing a new firmware was the only way I could resurrect it more or less. But now the only issue I see is that the device falls into "coma" if I don't press the Power button. Well, it makes me think that something prevents the screen from turning on, and I believe it must be a software issue. ... Or not -- I can't tell, this is where my knowledge is running out.
hurricane flow said:
Not sure if I'm giving all necessary info, but I hope it's what necessary:
Software version: G900PVPS3CQA2
Hardware version: G900P.04
Device name: Galaxy S5
Model number: SM-G900P
Android version: 6.0.1
Baseabnd version: G900PVPS3CQA2
Kernel version: 3.4.0-10090296 [email protected] #1 Tue Jan 10 14:50:06 KST 2017
Build number: MMB29M.G900PVPS3CQA2
Click to expand...
Click to collapse
Had you got this update http://www.galaxys5update.com/sprint-galaxy-s5-update-g900pvps3cqa2-january-security-patch/
they talk about stability improvments?
fgth90 said:
Had you got this update http://www.galaxys5update.com/sprint-galaxy-s5-update-g900pvps3cqa2-january-security-patch/
they talk about stability improvments?
Click to expand...
Click to collapse
If I understood you correctly, then it's installed on the device according to the information is posted above. The same happened before I applied the update too, so probably this update doesn't change anything for that.
hurricane flow said:
If I understood you correctly, then it's installed on the device according to the information is posted above. The same happened before I applied the update too, so probably this update doesn't change anything for that.
Click to expand...
Click to collapse
What you can try is a 3rd app to screen off your screen when you put your phone at horizontaly position and screen on with gestures.
I pm you a link for it.
It won't resolve your problem but can screen your phone off before the delay on settings.
Wait a little then try, then report.
Good luck
fgth90 said:
What you can try is a 3rd app to screen off your screen when you put your phone at horizontaly position and screen on with gestures.
I pm you a link for it.
It won't resolve your problem but can screen your phone off before the delay on settings.
Wait a little then try, then report.
Click to expand...
Click to collapse
Great! Thank you very much! I never had an idea of another way of making the screen off except of "let Android do it" or "let me do it myself" -- a 3rd-party app is to the rescue! That's a brilliant suggestion to work around the issue since it made my eyes got open for totally another solutions. And let Android to be the last one in that screen off queue! Thank you!!
hurricane flow said:
Great! Thank you very much! I never had an idea of another way of making the screen off except of "let Android do it" or "let me do it myself" -- a 3rd-party app is to the rescue! That's a brilliant suggestion to work around the issue since it made my eyes got open for totally another solutions. And let Android to be the last one in that screen off queue! Thank you!!
Click to expand...
Click to collapse
Nice to notice it worked.
But remember it's half done.
Your problem is still present.
Good luck matey
Franck
fgth90 said:
Nice to notice it worked.
But remember it's half done.
Your problem is still present.
Click to expand...
Click to collapse
Absolutely, but I'm still impressed by the alternative you suggested. Thanks again.
It can be a Hardware problem, If updated to Latest firmware in correct region, And not worked, Is The Hardware causing this.
fgth90 said:
What you can try is a 3rd app to screen off your screen when you put your phone at horizontaly position and screen on with gestures.
I pm you a link for it.
It won't resolve your problem but can screen your phone off before the delay on settings.
Wait a little then try, then report.
Good luck
Click to expand...
Click to collapse
can i have that pm too? i have the same problem: https://forum.xda-developers.com/galaxy-s5/help/galaxy-s5-doesnt-wake-home-key-weird-t3556724
I'm looking for suggestions for figuring out the cause.
I'm not rooted.
I tried clearing cache in recovery.
The wakelock exists even in airplane mode.
The wakelock goes away after a reboot, but reemerges at some point.
Any ideas on what to try or where to go from here?
Thanks.
stokholm said:
I'm looking for suggestions for figuring out the cause.
I'm not rooted.
I tried clearing cache in recovery.
The wakelock exists even in airplane mode.
The wakelock goes away after a reboot, but reemerges at some point.
Any ideas on what to try or where to go from here?
Thanks.
Click to expand...
Click to collapse
Install betterbatterystats with the steps without root and find the culprit : https://www.google.nl/amp/s/www.xda-developers.com/stop-wakelocks-android-without-root/amp/
I have this too, found anything yet?
asc366 said:
I have this too, found anything yet?
Click to expand...
Click to collapse
Just installed GSam Battery Monitor Pro and currently waiting for it to happen again.
stokholm said:
Just installed GSam Battery Monitor Pro and currently waiting for it to happen again.
Click to expand...
Click to collapse
Let me know, i was unable to drill down using bbs
asc366 said:
Let me know, i was unable to drill down using bbs
Click to expand...
Click to collapse
I had to use a Magisk module to make BBS a system app to get it to work in Oreo. Even with root priveledges it wasn't collecting any data.
jhs39 said:
I had to use a Magisk module to make BBS a system app to get it to work in Oreo. Even with root priveledges it wasn't collecting any data.
Click to expand...
Click to collapse
Found out what the wakelock was? Im not rooted.
asc366 said:
Found out what the wakelock was? Im not rooted.
Click to expand...
Click to collapse
I'm not either, but with an ADB command you can grant permission for battery stats anyway.
It's a kernel wakelock. I'm not sure where to go from here. What's the best place to reach out to OnePlus, to have this fixed?
I suddenly face the same issue..
By the way, did you guys wipe data before/after installing beta oreo ota? I did not
swa100 said:
By the way, did you guys wipe data before/after installing beta oreo ota? I did not
Click to expand...
Click to collapse
I have
swa100 said:
By the way, did you guys wipe data before/after installing beta oreo ota? I did not
Click to expand...
Click to collapse
Me neither.
Some people in the Oreo Beta thread seem to think that its a Bluetooth wake lock and that if you turn off Bluetooth and then reboot your phone it goes away.
I had a wake lock problem before I figured out how to get BBS to work but it went away after a couple days. I'm not using the stock kernel though--I'm using Lightning Kernel which blocks some wakelocks automatically and allows you to block others using the ElementalEx kernel control app.
jhs39 said:
Some people in the Oreo Beta thread seem to think that its a Bluetooth wake lock and that if you turn off Bluetooth and then reboot your phone it goes away.
I had a wake lock problem before I figured out how to get BBS to work but it went away after a couple days. I'm not using the stock kernel though--I'm using Lightning Kernel which blocks some wakelocks automatically and allows you to block others using the ElementalEx kernel control app.
Click to expand...
Click to collapse
This could be a valid point. I use Bluetooth quite often. Do you use Bluetooth a lot?
swa100 said:
This could be a valid point. I use Bluetooth quite often. Do you use Bluetooth a lot?
Click to expand...
Click to collapse
OP here. I have Bluetooth on all the time. But as I said, even in airplane mode the wakelock won't stop.
stokholm said:
OP here. I have Bluetooth on all the time. But as I said, even in airplane mode the wakelock won't stop.
Click to expand...
Click to collapse
Theres ppl claiming you need to actually boot with bluetooth disabled. Not just switching to airplane.mode but actually starting your phone without bluetooth. Have you tried this?
swa100 said:
This could be a valid point. I use Bluetooth quite often. Do you use Bluetooth a lot?
Click to expand...
Click to collapse
I use Bluetooth a lot and I'm not having that wakelock problem but the kernel I'm using might be blocking it. Several people have said if you turn of Bluetooth and then reboot your phone the wakelock goes away. It's definitely worth trying.
I ended up going back to nougat. This wakelock was killing my battery life. Going to report the bug now.
edit: reported. See: https://forums.oneplus.net/threads/wakelock-after-using-bluetooth-devices.704688/ follow/reply would be great!
More and more people seem to have these problems:
https://forums.oneplus.net/threads/wakelock-after-using-bluetooth-devices.704688/
And in general: https://forums.oneplus.net/feedback/?node_id=243
Can anyone confirm if this bug still occurs on the stable version or on open beta 3?
March security update is out which also includes "digital wellbeing support"
Downloading now, 93Mb.
Update went fine.
New wellness feature looks good, could be useful for some, though it does list all apps even ones you are not "really" using like Nova launcher .... but this will probably reduce in stats prominence as I use phone properly during day.
More importantly. Does it fix the Bluetooth issues that exists in the Jan and Feb updates
mobileman88 said:
More importantly. Does it fix the Bluetooth issues that exists in the Jan and Feb updates
Click to expand...
Click to collapse
I presume it doesn't.
Titokhan said:
I presume it doesn't.
Click to expand...
Click to collapse
Though I wonder if our bug is related to the Pixel "Bluetooth reliability" update (I don't have this issue so not checked)
Listed in update bulletin
https://source.android.com/security/bulletin/pixel/2019-03-01
And here is the security update bulletin, if anyone is interested
https://source.android.com/security/bulletin/2019-03-01.html
Titokhan said:
I presume it doesn't.
Click to expand...
Click to collapse
Not much point in this update then. I had to roll back to December for my Bluetooth even be remotely usable for my car and speakers
The thing that's strange is all these Bluetooth issues ...I don't have any of em. My PH1 works normally with my car, portable Bluetooth speaker and 2 different sets of Bluetooth headphones. Many of the issues others complain of I can't replicate or simply don't have.
autosurgeon said:
The thing that's strange is all these Bluetooth issues ...I don't have any of em. My PH1 works normally with my car, portable Bluetooth speaker and 2 different sets of Bluetooth headphones. Many of the issues others complain of I can't replicate or simply don't have.
Click to expand...
Click to collapse
I think most of the people who are having issues have a wearable device, like a smart watch, that is giving the most issues.
OTA and Fastboot zip images from Essential
goofball2k said:
OTA and Fastboot zip images from Essential
Click to expand...
Click to collapse
How about LED notification light? look like still not working or not fixed yet
chanh2018 said:
How about LED notification light? look like still not working or not fixed yet
Click to expand...
Click to collapse
Works for me. Do you have it enabled?
autosurgeon said:
The thing that's strange is all these Bluetooth issues ...I don't have any of em.
Click to expand...
Click to collapse
Same here. Stock, rooted with Magisk, no TWRP. The phone was on Jan update when I bought it, went through both Feb and March updates, no issues. As pointed out, the problem might be more related to wearables, and I don't use them (just a headset and a car speakerphone)...
chanh2018 said:
How about LED notification light? look like still not working or not fixed yet
Click to expand...
Click to collapse
This one seems to be hit and miss for me... For example, it works for SMS, but not for missed calls.
Does this update have any sim relocking tricks? Thanks.
kt-Froggy said:
Same here. Stock, rooted with Magisk, no TWRP. The phone was on Jan update when I bought it, went through both Feb and March updates, no issues. As pointed out, the problem might be more related to wearables, and I don't use them (just a headset and a car speakerphone)...
This one seems to be hit and miss for me... For example, it works for SMS, but not for missed calls.
Click to expand...
Click to collapse
I'm also in Stock w Magisk 18.1 anderen w/o twrp since february. How exactly did you update? AS described here?
https://topjohnwu.github.io/Magisk/tutorials.html
no SIM relocking issue for me. mine stills says Sprint on bootscreen but i'm able to get T-Mobile signal
chanh2018 said:
How about LED notification light? look like still not working or not fixed yet
Click to expand...
Click to collapse
Mine has worked fine all along. In fact I don't have and never had either the Bluetooth issues or the wifi issues. So either the hardware is that different from device to device or something else is going on.
autosurgeon said:
Mine has worked fine all along. In fact I don't have and never had either the Bluetooth issues or the wifi issues. So either the hardware is that different from device to device or something else is going on.
Click to expand...
Click to collapse
Just to double check, you're on Pie, not Oreo right?
If so, that's weird, 'cause on mine, it's ok on Oreo but latest Pie
tqwzUX6fn39GZMEzSnDF said:
I'm also in Stock w Magisk 18.1 anderen w/o twrp since february. How exactly did you update? AS described here?
https://topjohnwu.github.io/Magisk/tutorials.html
Click to expand...
Click to collapse
No, my update process is based on the steps from this thread: https://forum.xda-developers.com/es...de-step-step-instructions-to-install-t3877259
In short: adb sideload OTA zip, extract new boot.img from the update, patch with Magisk, fastboot flash patched boot. I haven't tried the method you linked. Maybe another time...
chanh2018 said:
Just to double check, you're on Pie, not Oreo right?
If so, that's weird, 'cause on mine, it's ok on Oreo but latest Pie
Click to expand...
Click to collapse
I have been on 9.0 since the first Beta. I am currently on the latest March security update of 9.0.0
autosurgeon said:
I have been on 9.0 since the first Beta. I am currently on the latest March security update of 9.0.0
Click to expand...
Click to collapse
Hummm.....that's really bug me. I just re-flashed the stock ROM and still no LED notification. Have no clue how to fix it.
but thanks for the response.