yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] ele95:
yes for me too after flashing aroma gapps
[OnePlus 3 & 3T Cross Device Development] morphvale:
Getting the same. Tried removing SIM, switching between EXT4/F2FS, Flashing with/without Magisk, manually changing the Installer.sh of the official 8.0 nano GAPPS or using the unofficial one from SF. No matter what, can't get past the language selection screen.
[OnePlus 3 & 3T Cross Device Development] Dirk:
Which Firmware works with the Experimental build? I'm getting Error 7 using TWRP 3.2.1-0 with latest Stable firmware.

I'm currently using 14.1 with OB15 firmware.
[OnePlus 3 & 3T Cross Device Development] manishvermaa:
https://androidfilehost.com/?w=files&flid=170282 This gapps is suggested by lineage os. Maybe this wont give setupwizard fc.
[OnePlus 3 & 3T Cross Device Development] Dirk:
Can Chrome users just check something for me? Go to Youtube and go full screen on any video. Is your Status Bar still visible or is it hidden?

Edit: 'Display Size' setting breaks things:

https://xdaforums.com/pixel-2-xl/help/chrome-playing-video-fullscreen-t3754909#post77253269

I need to know now whether this happens in LOS currently.
[OnePlus 3 & 3T Cross Device Development] Uumas:
Visible
[OnePlus 3 & 3T Cross Device Development] Dirk:
Check my edit above. Setting Display size to 'Default' should fix it so Status Bar is hidden. Could you check for me?

Thanks.
[OnePlus 3 & 3T Cross Device Development] iron@ss:
Not visible for me in expanded mode on Google Chrome. Display size = Default. Hope that helps. :)

EDIT: Not visible in Smallest display setting, either.
[OnePlus 3 & 3T Cross Device Development] Uumas:
Not visible on default, smaller or smallest, but visible on small.
[OnePlus 3 & 3T Cross Device Development] Dirk:
Let me write up my findings in a clear manner:

The Bug:

In Chrome and Chrome Beta, Status Bar is visible when going Fullscreen on video playback. (Bug not present when using Firefox or Samsung Browser).

The Cause:

Issue is caused by certain Display Size settings.

Experiments:

'Default' preset works properly. Status Bar is hidden.

'Small' preset doesn't work. Status Bar is visible.

My preference for UI is 'Custom', 400 dpi. Status Bar is visible.

Closest 'Custom' value to preference is 399 dpi. Status Bar is hidden but Gboard broken.

Closest working 'Custom' value to preference that is over 400 dpi, is 403 dpi. Status Bar hidden, Gboard works.

Solution:

Find a Custom Display Size that's closest to your preference that doesn't break Fullscreen. In LOS the setting can be found in 'Developer Options'.

---------- Post added at 16:36 ---------- Previous post was at 16:29 ----------

Thanks chaps.

So certain Browsers seem able to adapt to DPI changes better than others. It's a problem on Chrome. I can't use my preferred DPI because it breaks that Browser.

I can't see that there's much that can be done at the ROM level to fix this. Maybe just changing the value of the 'Small' Preset to something that works? If anything it's something Google need to fix in Chrome, right?

[MENTION=4405529]nvertigo67[/MENTION]

Perhaps you have some idea... why is it when you set a custom value 411 the result is reported as 420, but when you set 420, it's reported as 411? And how could there be an odd number for dots-per-square-inch?
[OnePlus 3 & 3T Cross Device Development] Playa82:
Ok guys. I think my problem is the idle drain. I try to drain the battery to 5% and then i charge it full. Maybe my mistake is i charge it even if i got 60 or 70 % left. I hope it solves my problem. But as i said. I never had this problems before the last update. Very strange.
[OnePlus 3 & 3T Cross Device Development] :
Strange, in deed. Get betterbatterystats (there's a free version for xda users) and after a night of idleing get the stats for summary, kernel wl, partial wl, processes and time in state since screen off.

This is one of the best issue descriptions I've read so far, dude!

I disagree on the aapt config los is using. This doesn't mean los is using an wrong aapt config, it's just I like this one:

https://github.com/nvertigo/android...mmit/0faffa00305ec66dc87eb9f58c0b287d87241913

I didn't test with custom sizes, but for all preconfigured display sizes I have NO status bar on chrome->youtube->fullscreen.

You are comparing real apples to virtual, standarized apples: dpi is the physical resolution (if you take a ruler and a looking glass you can count the dots per inch) - which is independent from the screen size (4", 5", 5.5" or whatever). dp is a kind of "virtual unit" telling the app how much space is taken in account to display an item - this is size AND dpi dependent. Smallest width refers to dp, the value shown in display size, if a custom one is used is dpi.

The actual mathematic relation is computed by the aapt build time config.

Sounds complicated? This nearly condensed my brain, when dealing with the first time... ;)

There is a writeup on this topic on https://source.android.com/ - I'm low on time this afternoon and can't find it instantly.

BTW: I guess it's a chrome bug - and if my aapt config is working around this, this doesn't mean my config is "more right", nor it's not a chrome bug.
[OnePlus 3 & 3T Cross Device Development] mk_1996:
I can confirm its a chrome bug. I have tested this with many roms and this issue is present everywhere.
[OnePlus 3 & 3T Cross Device Development] Dirk:
First time for me and still trying to wrap my head around it! :laugh:

Thsnks for the input. Valuable as always. :good:

There didn't seem to be many mentions of it from my Googling efforts. A few posts on the Product Forums. It was an xda search which revealed the cause and solution.

Google need to step up their game!
[OnePlus 3 & 3T Cross Device Development] Playa82:
Ok guys. Here are my stats. Only 4 % overnight. As i said. Strange...
[OnePlus 3 & 3T Cross Device Development] Naudiz:
My BBS looks quite similar to yours, but I have a high idle drain since last build. No particular wakelocks, 95% deep sleep, but still a lot of drain out of nothing. It's very weird.
[OnePlus 3 & 3T Cross Device Development] user7743:
I have had that with some builds where no one else seemed to suffer the same issue. The only solution i could find was a clean install.
[OnePlus 3 & 3T Cross Device Development] paper13579:
I've run into the same bug. And it's really annoying. Please share how you changed the clock position. I can't seem to find it in the settings
[OnePlus 3 & 3T Cross Device Development] Playa82:
or could be the heat here why my battery drain fast. i'ts around 35 C° (95 F) the last days here
[OnePlus 3 & 3T Cross Device Development] ps_minky16:
Definitely not heating at that temp. Where i live(delhi) usually its 39-40°c and base temp of my phone is usually over 35°c and still my battery lasts for 4hrs on los.
[OnePlus 3 & 3T Cross Device Development] suolrihm:
Go to settings: System>Statusbar>Clock. The thing should be called Clock Position
[OnePlus 3 & 3T Cross Device Development] nasbdh9:
Does today's build include 2018-08-05 security patch?
[OnePlus 3 & 3T Cross Device Development] ele95:
i dont think so :confused:
[OnePlus 3 & 3T Cross Device Development] Naudiz:
I'm a little bit confused by the discussion in Commit 222347 - op3: Update from OOS 5.0.4.

Will the next build be running on 5.0.4 Firmware or not? In the discussion some Devs said that PlayStore-Certification got broken and OP28/37 should be used instead, but then the change got merged anyways...

So what FW to use on next build?
[OnePlus 3 & 3T Cross Device Development] Dirk:
For LED Notifications, how many of you find that apps ignore the 'Default' setting, if you set one? I have to manually add every single app and set up the controls individually.
[OnePlus 3 & 3T Cross Device Development] Playa82:
me, but i set up my led for every app seperately. its no big deal, but it should not to be done.
[OnePlus 3 & 3T Cross Device Development] :
Blobs for the next build are taken from 5.0.4. See TheMuppets (blob commits doesn't show up in gerrit or git).

For ob30/39 and 5.0.4 the fingerprint/description duple is messed up. Safetynet api will be broken and playstore will be uncertified with these duples (no matter of Magisk and/or patched kernel), so we use a proofed to work duple. This doesn't mean the blobs from 5.0.4 aren't used. See the commits on TheMuppets, 5.0.4 update is already pushed.

Though los will flash on all fws equal or later https://github.com/LineageOS/android_device_oneplus_oneplus3/blob/lineage-15.1/board-info.txt, I would use the same fw version as the oos rom the blobs are taken from: 5.0.4.
[OnePlus 3 & 3T Cross Device Development] Dirk:
Problem is it's been broken for the whole Oreo cycle so far and hasn't been addressed. Good chance it will continue to be broken through the Pie Cycle.

*I knew i would find a Pie Cycle on Google the second i typed it!

---------- Post added at 16:39 ---------- Previous post was at 16:10 ----------

Flashaholics ahoy. New Build up!

Edit: There might be something wrong with the build. There's a message on the linked page about the build no longer being available, and on the official page the file size is half what it should be.

Edit 2: Linked page has the correct download, official page has a bad one.

https://www.lineageoslog.com/15.1/oneplus3
[OnePlus 3 & 3T Cross Device Development] :
Telling from the picture I guess P doesn't support ota updates, but otbb(*) updates, does it? Then the phrase "rollout" starts making sense!!! *lol*

(*) Out of The Bicycle Box
[OnePlus 3 & 3T Cross Device Development] Dirk:
Rofl :laugh:

Updates will be hand delivered said a Google 'Spokes' man! :p
[OnePlus 3 & 3T Cross Device Development] S4turno:
download.lineageos.org links to mirrorbits.lineageos.org and mirrorbits redirects users to a mirror close to them. Apparently it doesn't check if the file exists on that server before redirecting users, that's why sometimes we get an error. The link itself is correct, but it takes a few minutes for new builds to propagate to all mirrors.

Umeå University's mirror is first to get new builds (probably because they also host build servers): https://ftp.acc.umu.se/mirror/lineageos/full/oneplus3/
[OnePlus 3 & 3T Cross Device Development] Playa82:
i think there is something wrong in todays build. it's only 224 MB

Edit:

Now it works.
[OnePlus 3 & 3T Cross Device Development] Dirk:
At least read the previous page before posting. Then use the links provided.

[MENTION=4405529]nvertigo67[/MENTION]

Any idea why the 'Default' setting for LED Notification would be broken? Is it something you've had to fix in your own build?
[OnePlus 3 & 3T Cross Device Development] :
No, it's one of those...

In deed I havn't managed to get apps (not supporting notification led itself) to show up a light at all (i.e. google keep). k9 has support on it's own, but is only working if I enable vibration in addition to the notfication lights. Whatsapp on the other hand is working without wistles (9 out of 10)... I havn't found something in the logs, so it's one of those... :(
[OnePlus 3 & 3T Cross Device Development] alochmst98:
I have a 3T. I recently updated TWRP to 3.2.2-0 and now when I try to update to the latest LineageOS nightly from the OTA, TWRP no longer does the usual apply update and reboot. Instead, it asks me whether I want to keep the system read-only, and then (whichever way I answer) it takes me to the main TWRP recovery screen ( Install, Wipe, Backup, etc.). I don't know how to make it apply the update, so I tell it to reboot to System and then once I'm booted back up I have a notification saying the LineageOS update failed.

The LineageOS version that I'm currently on: 15.1-20180731-NIGHTLY-oneplus3

The OTA update I'm trying to install: 15.1-20180807-NIGHTLY-oneplus3

TWRP: 3.2.2-0

Edit: Never mind, I now see that TWRP has already released 3.2.3-0, even though 3.2.2-0 came out just a few days ago. Maybe it's to fix this bug. I'd delete this post, but I don't see a delete button anywhere.

Edit #2: After updating TWRP to 3.2.3-0, the OTA update worked as normal again. Not a LineageOS issue, but a TWRP issue with encrypted phones.
[OnePlus 3 & 3T Cross Device Development] Playa82:
dumb question. do you guys use the latest 5.0.4 firmware now ? im on 5.0.3. and i got no issues at the moment. or should i update ?
[OnePlus 3 & 3T Cross Device Development] xhenon:
Could your tell me from where you download this firmwares?

And also, is it for op3 or op3t?

Thanks
[OnePlus 3 & 3T Cross Device Development] BillGoss:
OnePlus 3T

https://xdaforums.com/oneplus-3t/how-to/firmware-beta-10-t3631166/post72892105

OnePlus 3

https://xdaforums.com/oneplus-3/how-to/op3-flashable-firmware-modem-zips-t3816066/post77064598
[OnePlus 3 & 3T Cross Device Development] xhenon:
Thanks a lot
[OnePlus 3 & 3T Cross Device Development] lammpat:
404 not found

tried other available pages, all throwing 404. Whats wrong?
[OnePlus 3 & 3T Cross Device Development] user7743:
Is it just me, or did Privacy Guard disappear from the setting menus? I don't seem to see it anymore... Or am I being a bit blind?
[OnePlus 3 & 3T Cross Device Development] vivian&ondine:
Settings/security/trust should be there somewhere.
[OnePlus 3 & 3T Cross Device Development] :
It's there ...

settings > security & privacy > trust > Privacy Guard ... Here we are ?
[OnePlus 3 & 3T Cross Device Development] Dirk:
No 404 here. Did you try:

https://ftp.acc.umu.se/mirror/lineageos/full/oneplus3/

https://mirrorbits.lineageos.org/fu...age-15.1-20180807-nightly-oneplus3-signed.zip
[OnePlus 3 & 3T Cross Device Development] user7743:
Cheers guys. Guess I was being blind.
[OnePlus 3 & 3T Cross Device Development] :
I doubt your eyes are the problem...

If you are missing a setting, why not search settings? (If your settings search only finds apks, search this very thread.)

If you're thankfull for received help, why not use the thanx button?
[OnePlus 3 & 3T Cross Device Development] FrailtyXYZ:
very well said.
[OnePlus 3 & 3T Cross Device Development] SawFEAR:
Anyone else got the issue that after applying newest nightly update the gcam pixelmod from any modder immediately crashs when opened? Is this something with the camera2api? It worked fine before all time.
[OnePlus 3 & 3T Cross Device Development] pedritopl:
No such problem here. Using Arnova V8 without any problems on latest build.
[OnePlus 3 & 3T Cross Device Development] suolrihm:
I use the latest GCam Mod by Skulshady - No issues, no crashes
[OnePlus 3 & 3T Cross Device Development] SawFEAR:
Amy Idea of how to change this behaviour again? It started Just after The Update finished, so I am quite eure that the issue ist related to ist. I updated fromm July 10th to August 8th. The camera in WhatsApp is still working without issues. The normal unmodded Google Camera also Crashes at start.

I got Magisk, but I haven`t changed a thing. I also started reinstalling, clearing Cache and restarting the phone. But without luck.

Glas for your Help,

Cheers
[OnePlus 3 & 3T Cross Device Development] Dirk:
When did you last update your Firmware, and what version are you on?
[OnePlus 3 & 3T Cross Device Development] Playa82:
hey guys, im on 5.0.3 firmware at the moment. what would be better when i update to 5.0.4 firmware ? or is it not needed at the moment ?
[OnePlus 3 & 3T Cross Device Development] :
I recommend using the firmware from that oos version the blobs for the build you want to run are taken from.

Current build ships with blobs from 5.0.4. Previous build was ob30/39. There's no lineage build based on 5.0.3.

Generally all firmwares equal or newer then ob16 should work - at least that's what the flashing script is checking for:

https://github.com/LineageOS/android_device_oneplus_oneplus3/blob/lineage-15.1/board-info.txt This includes 5.0.3, of course.
[OnePlus 3 & 3T Cross Device Development] Dirk:
ROM is based on 5.0.4. atm. Go for it. I've had no issues.
[OnePlus 3 & 3T Cross Device Development] multiwirth:
Is aptx enabled in this rom and can someone confirm it is working correctly?

I want to find out if my headphones support aptx since there is no further info about it and a serious looking website said it does.

In the dev options, i switched to aptx codec but it reset it back to sbc after connecting to my headphones.
[OnePlus 3 & 3T Cross Device Development] mk_1996:
Well if you select aptx and if it resets to sbc,then your headphones doesn't support aptx. Both devices(the phone and the headphones) must support aptx. I can confirm this. I have a samsung u flex which has aptx support and it works perfectly fine on los 15.1
[OnePlus 3 & 3T Cross Device Development] multiwirth:
Well thank you for your confirmation.

So in this case my headphones don´t support aptx.
[OnePlus 3 & 3T Cross Device Development] :
aptx and aptx hd are working flawlessly with this rom - aptx low latency isn't supported. I've tested aptx myself (Teufel Move BT).

For the bt audio codec selection: for most usecases the system is selecting the "best" codec. If you connect a aptx supporting device, the system will select aptx. For the rare usecases you don't want aptx but sbc (I have no clue, why you shouod want this), you can use the dev opts settings to switch to sbc.

As soon as a bt device is connected, the dev opts will show which codec is used - no matter what's set in the switch. The switch will NOT be reset! I.e. if I set aptx hd and connect my Move BT, tge dev opts page shows aptx, the switch stays on aptx hd; if I disconnect the Move BT and connect my soundlink, the dev opts page shows sbc, though the switch is still on aptx hd.

For general day to day usage I'd recommend using the default system selection setting!

aptx is a qcom proprietary codec. qcom takes a licence fee. Vendors implementing aptx/hd/low latency are forced by the licence contract to show the aptx logo at least on the box and in the specs. aptx.com has a database on aptx enabled devices - which is far from complete... But if you google the specs for your device, it shouldn't be too hard to confirm if your device supports aptx or not.
[OnePlus 3 & 3T Cross Device Development] isitmeor:
very strange

i cant find the on-screen navigation bar

i am on oneplus 3t lineageos 15.1
[OnePlus 3 & 3T Cross Device Development] Explorer23:
Settings > system > buttons

First switch on the page is what you're looking for.
[OnePlus 3 & 3T Cross Device Development] isitmeor:
I wish, but as you can see they are not
[OnePlus 3 & 3T Cross Device Development] Perry3D:
Did you manage to solve this? I have the same issue.

No partial wakelocks and still 4% idle drain.
[OnePlus 3 & 3T Cross Device Development] :
Since it seems impossible to me to get information and logs on this (tried many times - the only one willing to give some info was [MENTION=2754073]Playa82[/MENTION]: https://xdaforums.com/showpost.php?p=77257347&postcount=3394 - sadly this shots wer taken after the issue vanished "automagically") I doubt anybody is able to fix this.

Perhaps opening a ticket on jira (https://wiki.lineageos.org/bugreport-howto.html ) will help you to supply the mandatory information.

BTW: 4% idle drain may be good depending on the time: 4% over night (like in the posting from [MENTION=2754073]Playa82[/MENTION]) is perfectly ok. 4 %/h is much too much.

BTW2: How do you know from the given information it is "the same issue"? All users complaining on idle drain lately havn't given enough information to be sure it is the same...
[OnePlus 3 & 3T Cross Device Development] Playa82:
today i had 24 % overnight. the night before only 6 %. its very strange. but because of dash charge it's not a big deal. i hope the problems will be fixed soon.
[OnePlus 3 & 3T Cross Device Development] Explorer23:
Well, this is how it looks on my side:
[OnePlus 3 & 3T Cross Device Development] isitmeor:
very strange did install it 3 times already
[OnePlus 3 & 3T Cross Device Development] :
Can we asume you clean flashed three times? If not: clean flash.
[OnePlus 3 & 3T Cross Device Development] Dirk:
And without Xposed. ;)
[OnePlus 3 & 3T Cross Device Development] :
If this is true, I'm speechless.

[Break - for overcoming the speechlessness]

For completeness: clean flash with only gapps (if you use them) - don't install/restore any apps, nor any mods, before you've checked the button settings.

OT:

I remember you've felt a bit annoyed, that some devs have stoped participating in their own threads. I can't do anything about the annoyance, but if I consider the last two pages, it's not surprising, at least...
[OnePlus 3 & 3T Cross Device Development] Dirk:
I'm only guessing, but the last time i saw someone here with a setting missing it was because of Xposed.

[MENTION=2589364]isitmeor[/MENTION] What Firmware version are you using and what Mods, if any?
[OnePlus 3 & 3T Cross Device Development] isitmeor:
yep a clean flash
[OnePlus 3 & 3T Cross Device Development] isitmeor:
I am using lineage OS 15-20180731 and their SU ad gapps 14 August 2018 ARM 8.1 mini

also used the latest lineage OS
[OnePlus 3 & 3T Cross Device Development] Dirk:
The fact that you don't understand what i mean by 'Firmware' raises a Red flag for me. The Firmware in this case is a seperate .zip file that you should have flashed with the ROM. For example, if your phone is a OP3T, you might have flashed 5.0.4 Firmware from here:

https://xdaforums.com/oneplus-3t/how-to/firmware-beta-10-t3631166

If your phone is a OP3, you might have flashed a Firmware from here:

https://xdaforums.com/oneplus-3/how-to/op3-flashable-firmware-modem-zips-t3816066

If you didn't flash Firmware, the version you currently have will be whatever version of OOS was last on your phone. So if you came from OOS Open Beta 24. for example, your Firmware would be out of date.
[OnePlus 3 & 3T Cross Device Development] :
Two points left to check:

change the fw to ob30/39 or 5.0.4, and/or

clean flash without gapps at all (skip all skipable parts of the first time setup) and check if the settings are back again. If the settings show up again without gapps, use nano or pico of opengapps or the MindTheGapps package.
[OnePlus 3 & 3T Cross Device Development] Paardenpijper:
I noticed that the lockscreen statusbar icons are not alligned correctly with the homescreen statusbar icons.

The lockscreen icons have more space between them and the top of the screen.

Anyone else experiencing this?
[OnePlus 3 & 3T Cross Device Development] Dirk:
New Build Up!!

https://www.lineageoslog.com/15.1/oneplus3
[OnePlus 3 & 3T Cross Device Development] isitmeor:
I used to have OnePlus 3T OxygenOS 5.0.4 Ver 5.0.4 (2018-07-29) on it

that version does show the on screen buttons
[OnePlus 3 & 3T Cross Device Development] Dirk:
Well, unless you're married to the idea of running stock LOS i'd recommend trying Nvertigo's custom build or Resurrection Remix. The latter is LOS based, passes Safetynet out of the box (which LOS doesn't), is stable, feature rich and has great Battery life.

https://sourceforge.net/projects/resurrectionremix-oreo/files/oneplus3/
[OnePlus 3 & 3T Cross Device Development] iron@ss:
Cheers Dirk! :)

Thank goodness my local pub has superfast broadband and free Wi-Fi. Probably best if I stay here until it is downloaded and installed and then thoroughly checked out... Should take at least another 3 or 4 pints. :good:
[OnePlus 3 & 3T Cross Device Development] Dirk:
:highfive:

I reckon if i join you, together we could slow that 'Superfast' Broadband down to a slow crawl. Probably take until last orders to get anything done! :good:
[OnePlus 3 & 3T Cross Device Development] Dirk:
Here's a Screenshot of Navbar Options on Ressurection Remix. There's plenty to play with:
[OnePlus 3 & 3T Cross Device Development] iron@ss:
Can't see the problem Dirk.

Lovely, old, stone, rural, Cotswold pub with a wide range of real ales and lagers... a bright, sunny, afternoon, pretty barmaids and a landlord that does lock-ins. It's got to be the only way to install new ROMs. ;)
[OnePlus 3 & 3T Cross Device Development] Dirk:
Sounds like you died and wound up in Heaven good buddy! Against all odds i might add. :p

And there's me now wondering where i might pitch up tonight to get a good Ruby Murray and a Pint of Tiger!