yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] drezz2:
No one uses BBS? When you create an access point or put the GPS, BBS marks "awake screen off" even if you remove the access point / GPS.

The processor spends all the time in 300mhz instead of staying in sleep (this has always happened to me),
[ONE Original Android Development] woshee:
OK After a couple of days of testing, I still have the network problem, and maybe also the 4g/wifi issue....

I'll try he firmware switch....
[ONE Original Android Development] eiwarmer:
Could also be a hardware issue. Maybe your sim or simcard tray is failing on you. Tried the sim in a different phone?
[ONE Original Android Development] woshee:
I seriously doubt it, it's not that old... I haven't tried the firmware flashing though, don't know which one to choose from....
[ONE Original Android Development] :
The latest fw/baseband version cm were bundled with (before switching to LineageOS, which has no fw/baseband on board), was DI.3.0c6-00241. This combo (LineageOS combined with this baseband) is running fine for me for ages now. Give it a try.

Place to download from:

https://xdaforums.com/showpost.php?p=64975341&postcount=1
[ONE Original Android Development] Zflash:
I had a lot of issues with the One not getting in deep sleep and found out that the culprits are telegram and WhatsApp. After killing them the phone really goes for hours nicely in deep sleep. Does anyone have the same issue? Fairly stock LineageOS install with no custom kernel at the moment.
[ONE Original Android Development] eiwarmer:
24 hours uptime and 3,0-3,5 hours sot max is what I'm getting on almost every pie ROM with the first original battery. Sot sucks on Pie and so does the deep sleep (3% at 7 hours sleep) but I don't care. I feel blessed to have to LOS team backing me up with fast security patches and an almost bug free experience :) And I can't live without the pie notification throughout the OS (go back to any marshmallow ROM and you get my drift).
[ONE Original Android Development] Zflash:
Same here, but when I kill the 2 messaging apps, the standby time increases immensely so I was wondering what the root cause of this was .
[ONE Original Android Development] drezz2:
I have the nightly of 27.07.2019 and so far it had not happened to me but in the last week it has happened to me sometime, the mobile was running out of signal, or data, and the only way to re-enable it was restarting, I don't know the reason of this, because they are the first times that has happened to me .. maybe for some update of the services of google play?

Has anyone had problems with this? It is quite frustrating to see the battery drain, when not entering deep sleep, after using the GPS or the access point (even deactivating them, once they have been activated)
[ONE Original Android Development] drezz2:
I have establiced I am notified with 15 gigabytes of data use, can someone explain to me the reason why I put 15 and in the second capture I put 16.11? No matter how much you put, on one screen one comes out and on the other, a larger amount, is there anything I don't understand?
[ONE Original Android Development] woshee:
I flashed another firmware and the problem didn't happen since.

It was this one :bacon_firmware_oxygen_update_2016_01_22_.4.0.1.c7-00013 that I found in this thread:

https://xdaforums.com/oneplus-one/general/firmware-modem-oneplus-one-t3462214

Hope it will stay this way
[ONE Original Android Development] SethGeckoXDA:
15 GiB = 16.1 GB
[ONE Original Android Development] drezz2:
:eek:

true, but since in both places it puts GB and not GiB in one and GB in another, I also don't understand that it uses two different units, it gives rise to confusion, or so I think

---------- Post added at 10:09 AM ---------- Previous post was at 10:06 AM ----------

did it always happen to you?

It has only happened to me a couple of times that I remember
[ONE Original Android Development] woshee:
Nope it was only this summer, but updating the nightlies didn't fix it.
[ONE Original Android Development] drezz2:
can any update of google play services cause this? otherwise I do not understand
[ONE Original Android Development] woshee:
google services has nothing to do with network connectivity.... It was most certainly a nightly that didn't go well.
[ONE Original Android Development] drezz2:
I have a nightly at the end of July and so far I had not presented that problem on those two or three occasions (from what I understand that it is not caused by a recent change and I am surprised that the problem saw him 1 month after the update)
[ONE Original Android Development] eiwarmer:
Hey [MENTION=2836769]jrior001[/MENTION] did you notice if you record a video and tap the display to take a picture the camera app freezes?

I've got a log if you'd like to take a look at this please.
[ONE Original Android Development] LTMendarynas7:
Can confirm. Just tried and it froze
[ONE Original Android Development] SethGeckoXDA:
This issue is already being tracked here.
[ONE Original Android Development] rubenium:
Same problem here since several weeks. Currently also with build of Sept 7th 2019. No solution found for this weird charging behavior?
[ONE Original Android Development] Zflash:
Ok, so I thought my cable or connector was going bad but more people are having issues with this. I have exactly the same problem with charging although a short quality cable makes this syndrome appear less.
[ONE Original Android Development] hgmichna:
Weird charging problem

I have had this or a very similar charging problem about a year ago. I reported it, and it got fixed in one of the next builds.

The charging current to the battery went to very low, sometimes negative values. But sometimes it charged normally.

Perhaps this is the same defect that was restored by mistake.
[ONE Original Android Development] :
I have had this slow charging issue with 15.1 - but with day one from 16 this issue wasn't any longer an issue. Charging was/ is fine for me with 16.
[ONE Original Android Development] merikgvr4:
Do we have split screen functionality on this rom?
[ONE Original Android Development] eiwarmer:
Yes!
[ONE Original Android Development] trancinguy:
Get a charger that outputs 2.4 A and a high quality cable you will charge fully in an hour. The only time I get problems charging is when I plug into a low output.
[ONE Original Android Development] rubenium:
no, it is not about the cable. Tried with several cables, including the original one and the original charger.

It charges correctly with the phone switched off. The connection and disconnection problems occurs when charging from low battery (let's say between 1 and 25%) and with the phone switched on, so it is clearly a rom issue.
[ONE Original Android Development] trancinguy:
Try 2.4a output then see if it makes a difference or not. The original is probably 1a to 1.5a.
[ONE Original Android Development] hgmichna:
Weird charging problem

The phone charges with any current, 500 mA, 1 A, 1.5 A, and max, unless it is defective. Normally you can charge it, slowly, on a computer USB port. I don't understand what you mean.

I'll say it again. If it charges with 2.4 A, but not with any lower current, then it is defective.
[ONE Original Android Development] crixxelven:
Hello! I recently installed this on my 4 year old bacon and I'm loving it. One thing tho, I doesn't seem dark mode is working?
[ONE Original Android Development] eiwarmer:
Which build you on here it's working fine.
[ONE Original Android Development] eiwarmer:
See the screenie
[ONE Original Android Development] merikgvr4:
How to enable?
[ONE Original Android Development] trancinguy:
Display - Style: Dark -Dark Mode: Black.
[ONE Original Android Development] crixxelven:
I used 16.0-20190903 paired with Pico. I went to display and tried to select dark mode but to no avail. I tried restarting, still didn't work.
[ONE Original Android Development] godblessing:
Hello.

I've been using LOS 16.0-20190808-NIGHTLY for about 2 weeks.

Everytime I play music, whether it plays in default Music app or Phonograph, the next track will sounds horrible.

As horrible as you can't hear any song. It just pure a noise and the volume will going up on its own.

Did somebody experience the same issue as me?

I haven't trying update because I'm on my busy weeks. I'm here seeking for answer or maybe report an issue.
[ONE Original Android Development] eiwarmer:
It's display > advanced > style > style > dark

You can chance the dark style at the dark mode to black if you want

---------- Post added at 08:36 AM ---------- Previous post was at 08:25 AM ----------

Not here. I've been listening to music on Bluetooth headphones and never had this issue. I've been upgrading on almost a daily cycle too.
[ONE Original Android Development] merikgvr4:
Can you help me enabling split screen? Thanks

Disregard. Figured it out. Had to use home button. Thanks
[ONE Original Android Development] eiwarmer:
You could also long press the app icon on the recents screen like in the screenie
[ONE Original Android Development] merikgvr4:
Pretty cool. Thanks for sharing.
[ONE Original Android Development] Lanchon:
hey [MENTION=2836769]jrior001[/MENTION],

VERY STRANGE OCCURRENCE AFTER UPGRADE.

a friend has an OPO running Sultan's CyanogenMod (Android 6) from 2017, no encryption, 401 modem. i set out to upgrade it without factory reset. this is what i did:

1) install latest official twrp.

2) twrp backup.

3) flash signing key migration: a) format system. b) flash very old official LOS migration build (from first month of LineageOS operations) which is android 7.1. c) flash su addon. d) flash nano gapps.

4) boot and reboot android 7.1 to migrate keys. no issues.

5) flash current LOS 16: a) format system. b) flash current official LOS. c) flash su addon. d) flash nano gapps.

6) boot and reboot. everything works completely fine now.

except... after a few hours this happens: suddenly when i input the correct unlock pattern, the screen goes dark, then the lockscreen comes up again. the cycle repeats forever. adbd is not open (but was before) so i can't logcat. stuff like web-whatsapp works though i cant unlock. notifications update correctly from the network. i can receive whatsapp calls.

so i decide its probably a flash corruption and do this:

7) format system, clear caches, reinstall all, reboot.

same exact problem: i cant unlock.

8) restore android 6 (CM) backup. reboot, the phone works fine.

9) reinstall everything: key migration build, then LOS 16. everything works again fine.

except...

after a few hours...

THE EXACT SAME PROBLEM HAPPENS AGAIN!!!

again, i cant unlock the phone!!!

wtf is happening? anybody heard of something like this?

i'm afraid LOS might be file-encrypting on the background, then loosing the key and thus can't unlock. is this (silent encryption) possible at all? how can i stop it? why is it failing?

thanks so much for your help!!!
[ONE Original Android Development] fmc000:
Started happening to me too with the latest build. I blamed magisk but I see that it happens with standard su too...
[ONE Original Android Development] Lanchon:
what started happening? you can't unlock your lockscreen? what did you do about it?
[ONE Original Android Development] eiwarmer:
Well normally I'd say when migrating too a whole new Android version a clean flash is mandatory meaning wipe your data too. But since another user has the same issue it might be a build error, yikes :silly:

You could try a previous build to see if the problem persists? Because I haven't encountered this issue and I'm definitely not going to flash the latest build lol
[ONE Original Android Development] fmc000:
Just to be clear: the "cannot unlock" problem is not related at all to a OS version change. I've been running LOS 16 for months and this problem was first seen with the last two releases.

[MENTION=4141005]Lanchon[/MENTION] What did I do: as this is just a "test phone" for me I simply wiped /data the first time. When it happened again I tried to restore a nandroid without /boot because I thought that the problem was caused by Magisk. It worked but you say that it happened with the standard SU too so...
[ONE Original Android Development] eiwarmer:
Well I'm running lineage-16.0-20190910-nightly-bacon-signed.zip with no lock screen issue here so idk. Are you running any mods? Xposed?
[ONE Original Android Development] fmc000:
No mods apart from Magisk. The problem does not happen always. For example, I turned off the phone in early August and left in a drawer for about one month. It was working fine. Then I turned it on and I couldn't unlock it (with PIN, I never use pattern and, believe me, the code was correct because it's impossible to forget, remember that we're talking about a test phone).

Edit: I haven't been able to replicate the problem with POSP.
[ONE Original Android Development] Timmmmaaahh!:
Via TWRP's file manager, navigate to /data/system, then delete anything with a '.key' extension and anything with 'locksettings' in its name. Then reboot and pin should be gone.
[ONE Original Android Development] trynex:
Unfortunately, the later effort is also in abandoned state : https://review.lineageos.org/c/LineageOS/android_device_samsung_hlte-common/+/254223

Don't know if there will be any more efforts in this direction : :(
[ONE Original Android Development] ze7zez:
There is nothing to worry about.

p.s.

Select "Miracast" and "Android 9" on this phonedb.net site.

Currently 156 smartphones with Android 9 support Miracast in stock rom. :good:
[ONE Original Android Development] godblessing:
Ah.. I guess I'll try update my phone first. Since it hasn't been done for weeks.

I'm just curious that my phone could play any other audio source (e.g. YouTube, Chrome), but music(audio file) player. I've tried audio stream apps (e.g. JOOX, Spotify) and they work fine.

Will update on this post after apply update on my phone.

Thanks!
[ONE Original Android Development] Lanchon:
has anybody done this? NOTE THAT IF YOUR PHONE/USER IS ENCRYPTED YOU MIGHT LOOSE ALL DATA!!!

---------- Post added at 08:12 AM ---------- Previous post was at 07:58 AM ----------

UPDATE ON THE CANNOT UNLOCK ISSUE

i was able to find this mirror of old LOS builds for bacon:

https://www.celsoazevedo.com/files/android/oneplusone-lineageos/

(build are archived by archive.org)

i had reverted to CM6 before.

so i backed up CM6 again, flashed LOS14 migration build, migrated, flashed most recent archived LOS 14.1, and everything worked fine, even after 24hs.

then i backed up LOS14.1, flashed most recent archived LOS 15.1, and everything worked fine, even after 48hs.

so the can't unlock issue seems to be related to LOS 16. i wont be seeing my friend for a long time now, so i can't risk flashing LOS 16 again. this is the best i could do for him.

if anybody finds out more about this issue, please reply to this message as i won't be checking this thread often (i don't own an OPO).

thanks again!
[ONE Original Android Development] jrior001:
I updated my bacon a few days ago to try to replicate this unlock issue and so far have not run into to any issues. Reading back through your upgrade procedure it looks like you may have skipped over a version? If so your lucky it booted at all.
[ONE Original Android Development] :
Nope this procedure is fine too delete lockscreen issue after nandroid backup. I've done this several times, included encrypted data ...
[ONE Original Android Development] Lanchon:
yes, i did. i went from 7.1 migration build straight to 9.0. but other people saw the same issue without upgrades-- or so i think.

i wasn't aware you shouldn't skip android versions on upgrade. this restriction is surely bad design if true, and restricts upgrade efforts of OEMs that lagged behind. if theres any link with info about this, please share.
[ONE Original Android Development] jrior001:
We work real hard to test and verify version bumps per device. In theory, a 2 version jump should work if we did everything properly, but its not a vetted situation. There's just to many builds and potential changes over the months to test every possible scenario.
[ONE Original Android Development] rubenium:
unfortunately, GPS fixing issues after latest updates. It takes ages to fix gps position, when it was a matter of seconds with previous builds :(
[ONE Original Android Development] vicky2131:
+1 for GPS not getting locked
[MENTION=2836769]jrior001[/MENTION]
[ONE Original Android Development] trancinguy:
anyone sometimes losses mobile signal, only emergency calls?

GPS problem here as well.
[ONE Original Android Development] ImmortAlex:
+1

Never has problems with GPS until now. Probably, some servers are down?
[ONE Original Android Development] rubenium:
I have to keep checking but location is behaving better since today. Maybe you are right and the location servers of the A-GPS were behaving weird?

As I said, I keep on checking
[ONE Original Android Development] ze7zez:
"Miracast support was backported to Android Pie"

Maybe we'll get Miracast working in LineageOS 16.

Work in progress.
[ONE Original Android Development] lom4x:
Screenshot from 20 September build with the phone in the corner of the window at 13 floor. Also I always edit /system/etc/gps.conf to change NTP_SERVER to more appropriate in my opinion pool.ntp.org instead of north-america.pool.ntp.org and A_GLONASS... to 7 which seems doesn't work anyway. As you can see phone see GLONASS and beidou sattelites but locks only on GPS sats.

Отправлено с моего A0001 через Tapatalk
[ONE Original Android Development] trynex:
Oh, you got me excited. But, I am not sure, if this would apply to our device?

AFAIK, another one could have worked, but it was thought a better solution is possible, but in the end both are in abandoned state... :(
[ONE Original Android Development] livingbeings:
I have a wifi 2.4Ghz slow connection problem. I searched in some other forum and found this problem discussion but did not find the solution, any help?

My version is lineageos 16 aug 13 2019 build
[ONE Original Android Development] SethGeckoXDA:
Slow download speed on the 2.4 GHz band is most likely related to older protocols (802.11b or 802.11g) and Google's NearbyMessagingService. You can read up on different strategies to circumvent this issue here.
[ONE Original Android Development] drezz2:
Are the GPS problems indicated above solved? or was it not something general?

when you start the gps even if it is not in use with bbs I see that the processor does not return to iddle
[ONE Original Android Development] SethGeckoXDA:
Can you share a screenshot of BBS when GPS is on and one where your GPS is off? I want to see if it is the same for me.
[ONE Original Android Development] drezz2:
the only thing that is going to be seen is that instead of appearing in "deep sleep" it appears as "awake screen off" and that time appears in cpu states at 300mhz, it happens to me so much if I put the gps (and do not use any gps application ) as if I activate the Wi-Fi zone to share Wi-Fi, but once deactivated it continues to happen, if I restart the mobile it stops happening.

Curiously when I put the GPS and do not use any GPS application, the GPS icon appears at the top for a few seconds and then disappears
[ONE Original Android Development] hgmichna:
Location services

When Google's location services are activated, the GPS is switched on from time to time, roughly once every 10 to 15 min, to record and forward your position.

Depending on circumstances, the time can differ. My guess is that, if you have location sharing on and somebody you share your location with asks for your location, it is taken more rapidly. If you are sleeping or the phone is resting, it is taken less often. Does anybody know more?
[ONE Original Android Development] drezz2:
I thought that even if the GPS is switched on, if there was no application using it, it would never be activated (I must be wrong then)

then it would be "the problem" for which it seems to keep the processor continuously at 300mhz and in wakelock instead of going to iddle
[ONE Original Android Development] hgmichna:
Location services

To be precise, an app uses it, a Google services app.

I don't see though why temporary use of the GPS should keep a wakelock in place afterwards. Normally obtaining the position takes only a few seconds.
[ONE Original Android Development] aci89:
Hi everyone,

I had the same camera issue with my OnePlus One as well (camera crashes on open, unable to open the settings of the app to clear the user data, etc...).

My OPO was upgraded from 14.1 to 15.1, then 15.1 to 16 without wiping data every major upgrade, but only by wiping system and cache partitions.

If it can help I managed to make the camera app work again by removing the following line

<renamed-package new="org.lineageos.snap" old="com.cyanogenmod.snap" />

from /data/system/packages.xml in recovery mode (I noticed that trying to remove the org.lineageos.snap package using pm from adb shell caused the system to complain about com.cyanogenmod.snap missing, so I tried removing that reference in the packages.xml file).

I don't know if this workaround has some side effects so I don't recommend doing that, but I hope it could be useful to address the issue
[ONE Original Android Development] lom4x:
Yes, i've previously upgraded from 14.1.

BTW, I haven't checked NFC, but payment with NFC were broken in first 15.1 builds and were patched.
[ONE Original Android Development] denloi:
Hi! Any reason why the full facebook messenger shows as lite version when in use?
[ONE Original Android Development] pippoaacc:
Looking to clean install but short on time. I have been away from flashing for a while: is Titanium still the one-stop best for app with data porting?
[ONE Original Android Development] Struppi0815:
I flashed the new Nightly. The LED still doesn't work.

Gesendet von meinem SM-G900F mit Tapatalk
[ONE Original Android Development] the sparrow:
one plus one

official lineage os 16.0 ,upgraded from 15.1("dirty" /no wipe)

first of all,thank you for an amazing job an and contribution.

los 16 so far works as promised

only one issue (maybe it is only for me,maybe not)

****notification led

on charging notification led not working for some reason.....

?

thank you for any replay on that subject.
[ONE Original Android Development] hgmichna:
Upgrading without wiping data

Sorry, but this is nonsense. Android is designed to be upgraded without losing app data, and it works just fine. If something doesn't, then that is a defect and should be repaired.

But you are welcome to visit me for the next major update, wipe data and then reinstall and reconfigure my 200 apps. Plan for a couple of days.
[ONE Original Android Development] Mandrake2010:
Impossible change sound. Soundpicker (system app) Google crash.

Last build ( 03/03) led not work.
[ONE Original Android Development] jmax91:
Due to the lack of kernels avalaible now, it would be possible add kcal support? It's the only thing I miss since it was removed at the end of 2014 on stock COS.
[ONE Original Android Development] Thanhbat:
If you want your screen is more vibrant like amoled display, so Enhance color in live display setting is enough to me.

---------- Post added at 18:46 ---------- Previous post was at 18:45 ----------

Clear default set in Soundpicker app info setting, then choose Media Storage as default and you are fine
[ONE Original Android Development] krzysn:
I have noticed the next error in LOS16 - sometimes screen freezes for a teens of seconds when is unlocked. App added to quick-access (below the screeen) as well as status bar are responsible but app drawer is not working. Looks like trebutchet freezes. Hope it can be corrected in a next update.

Clean los16 instalation.
[ONE Original Android Development] o-l-a-v:
Just testet 3. mars build on my old OnePlus One. So cool that this old winner has Pie now.

One thing I noticed: The back light on the hardware keys are very dim. Does this just happen for me? It's almost impossible to see what key is what.
[ONE Original Android Development] arcadius77:
Is camera working fine?
[ONE Original Android Development] sn809:
As usual superb work