yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] Sytis:
A small question which I am not really sure is 100% on topic: Am currently on release 20180731 and saw some F2FS updates in the patchnotes and kernel I'm using updated it as well. So now I'm willing to update to latest Los with F2FS and wipe everything clean beforehand. I noticed some files where added in the / partition so even lower then /system and /vendor. So is there a way to go back to complete stock like out the box stock? Maybe use stock recovery and then install TWRP again?
[OnePlus 3 & 3T Cross Device Development] isitmeor:
Hi i did install Ressurection Remixand yes it does have the onscreen navigation
[OnePlus 3 & 3T Cross Device Development] pitrus-:
Use the modified unbrick tool, then you will go back to stock OxygenOS and still keep the internal storage files.

Skickat från min ONEPLUS A3003 via Tapatalk
[OnePlus 3 & 3T Cross Device Development] Perry3D:
Sorry for the late answer. Took me two nights to evaluate the issue. I meant 4%/h.

It's definitly related to my wifi. On the second screenshot i turned of wifi over night and it went down from 4.2%/h to 0.6%/h.

And i am not sure if its related to Lineage because the only partial wakelock that looks heavy is CastDeviceController from the Google Play Services.

https://image.ibb.co/d9QmT9/Screenshot_BBS_20180814_072926.png

https://image.ibb.co/dRc0o9/Screenshot_BBS_20180815_075546.png

This is the 20180807 build with 5.0.4 firmware.
[OnePlus 3 & 3T Cross Device Development] :
Thanx for answering at all.

What about the kernel wakelocks? Is [timerfd] always the top most if this drain occurs - no matter if the kernel wakelocks doesn't sum up to the awake while screen off time?

For debugging (not for guessing) these pages are important: Summary, kernel wakelocks, partitial wakelocks, processes and cpu states. These pages are only usefull after some idle time with the issue present (this should be obvious, but somebody posted all those screenshots I requested with 0.5%/h drain - which is normal and needs no debugging, of course).

BTW:

I'm pretty sure that we have two different drain issues here on the last 40 pages: one is solvable by using a custom kernel with [MENTION=947981]Lord Boeffla[/MENTION]'s kernel wakelock blocker - the other isn't addressed or debugged or even looked closly at, because nobody is insterested in providing information. That some people without looking at information always state "I have the same" doesn't help to tell these - at least - two different issues.
[OnePlus 3 & 3T Cross Device Development] Perry3D:
These are all after nearly 7 hours of idle. Sadly the cpu states are missing. I can provide them later

https://ibb.co/eZhv5p

https://ibb.co/hvzmBU

https://ibb.co/gb14Fp

https://ibb.co/jm5RBU

https://ibb.co/ncODrU

Would a recording of a matlog help? I looked into it but i didn't find anything interesting. Maybe due to lack of experience :p
[OnePlus 3 & 3T Cross Device Development] counterfeit187:
Is something broken with addon.d support? every update I have to reinstall magisk.
[OnePlus 3 & 3T Cross Device Development] :
Dirty flashes work like supposed to. I'm on the beta update channel. Since 16.6 the execution of the addon.d script is shown after the output of rom flashing.

What do you do exactly when updating? Do you have a twrp log from an update session at hand?

Try a cusom kernel with boeffla's kernel wakelock blocker. (i.e.: Boeffla's, franco's, caesium - from memory, far from complete)

A general trick to reduce play services activity: use a minimal gapps package and install only additional gapps from play store you are actually using. Also check in google account settings if you really need all active syncs - don't sync what you don't need.

In addition [MENTION=4487956]S4turno[/MENTION] has some really valuable tricks: https://xdaforums.com/oneplus-3/one...eplus-3-3t-t3739169/post76827895#post76827895 (this includes, but is not limited to gapps - other apps suck bat, too)
[OnePlus 3 & 3T Cross Device Development] S4turno:
Apparently this bug was fixed: VPN connections treated as metered connections

Downloads/updates from the Play Store now work as expected when using a VPN (or anything that emulates a VPN) over WiFi.

https://review.lineageos.org/#/c/LineageOS/android_frameworks_opt_telephony/+/222660/

https://review.lineageos.org/#/c/LineageOS/android_frameworks_base/+/222655/

https://review.lineageos.org/#/c/LineageOS/android_frameworks_base/+/222657/
[OnePlus 3 & 3T Cross Device Development] Dirk:
I was running into this bug all the time trying to download new Podcast episodes, before finding out it was a bug.

Can confirm that everything works with both VPN and WiFi on now.
[OnePlus 3 & 3T Cross Device Development] tyler19820201:
My OP3T is very slow on this ROM. Sometimes it takes 15-20seconds to open an app

Does it normal? Or what should i setting?
[OnePlus 3 & 3T Cross Device Development] Dirk:
Clean Install with latest Firmware, if not already using it. What Firmware are you running?
[OnePlus 3 & 3T Cross Device Development] tyler19820201:
8.1.0

20180807 nightly
[OnePlus 3 & 3T Cross Device Development] Dirk:
Flash 5.0.4 from here:

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

Then Clean install ROM.
[OnePlus 3 & 3T Cross Device Development] tyler19820201:
Ok

Thanks

I am using 4.0.3 fw but i remember when i was flashing it i have needed to set up DM verity verification manually on CMD

Do i have to do the same with this? I am using multirom

Anyway does not flash the file. ERROR7 :(
[OnePlus 3 & 3T Cross Device Development] Dirk:
Try updating to latest TWRP if you haven't already. If that doesn't help you might have to try flashing full OxygenOS 5.0.4 and then clean install LOS.

https://xdaforums.com/oneplus-3t/how-to/official-oxygenos-5-0-1-android-8-0-t3728119
[OnePlus 3 & 3T Cross Device Development] :
Depends on the app. Some large (mainly heavy graphics intense apps) can take that long - on boot loaded, day to day apps like Settings or Clock should start nearly immediatly.
[OnePlus 3 & 3T Cross Device Development] tyler19820201:
I was trying to speed up the phone to increase dirty ratio and cpu clock etc. but still the same.. Basically i have problem only with one app: Bluemail emailmanager. The rest of the apps are slow as well, i mean slower then on LOS 14 but i can "tolerate" them.:rolleyes:

I am talking about only the launch of app. Once the app has launched then will be operate on "normal" speed.
[OnePlus 3 & 3T Cross Device Development] :
Before ****ing around with details one should really,really knows what he's doing, you should use an oreo fw for an oreo rom.

EDIT:

Just checked the source and updater-script: it's not possible to flash LineageOS-15.1 on a device with firmware build earlier then 2017-11-16 04:58:57. If you successfully flashed the signed Lineage-15.1 build, you can't have been on 4.0.3 firmware!!!

Since you are unsure which fw you are using, I would strongly recommed flashing 5.0.4 firmware and then clean flash the rom. If it's still slow, reformat data (ext4 is recommended by OP).
[OnePlus 3 & 3T Cross Device Development] Explorer23:
Minor (negligible really) issue I found: updater doesn't seem to detect charging correctly.

- plugged in at low charge, downloaded update, tried to install at 18% and it said that it needs at least 30% of charge or 20% if plugged in

- tried a few minutes later at 27% and still got the same message (even though the conditions are met now)

- a few more minutes later it started the update process normally at 30%+
[OnePlus 3 & 3T Cross Device Development] tyler19820201:
Yes, it is good to know.

So it means i have higher then 4.0.3

I have just wiped the app chache and had become a little faster...

Anyway i was trying to flash the 5.0.4 but it gives ERROR7 code and there is no assert line in the script to delete...

Where can i check what is my current FW exactly?

I have TWRP TWRP_3.1.1-1_multirom_oneplus3_20171120-02 and the LOS15 mentioned before
[OnePlus 3 & 3T Cross Device Development] :
For the official twrp you need at least the unified twrp-3.2.1-0 to have oreo support. As [MENTION=1763460]Dirk[/MENTION] already said: use the current (3.2.3-0). I don't know for unofficial multirom twrp, but I guess 3.1.x-x doesn't support oreo, since 3.1 is over 18 months old.

The easiest way is flashing the fw you want (you want 5.0.4). To get the build time of the fw get an image of "/dev/block/bootdevice/by-name/modem", use strings(1) on the img and grep for "Time_Stamp".

I.e.:

ingo@adler /usr/local/src $ adb shell su -c "dd if=/dev/block/bootdevice/by-name/modem " 2>/dev/null|strings|grep "Time_Stamp"
"Time_Stamp": "2018-07-19 22:54:22"
ingo@adler /usr/local/src $

Compare the date to the release dates on this page: https://downloads.oneplus.com/devices/oneplus-3t/ or https://downloads.oneplus.com/devices/oneplus-3/ .

The build time (the one you greped) should be older then the release, but not as old as the previous release. For the above example (3t) it's older then the release date of 5.0.4, but newer then ob30, so the fw used is 5.0.4.
[OnePlus 3 & 3T Cross Device Development] tyler19820201:
Thanks

I want use MultiROM in the future so i can not flash the latest "normal" TWRP however that would be the easiest way. That is why i use this old one. However TWRP_3.2.1-1_multirom_oneplus3_20180125-01 this is what i have found as the latest multirom support TWRP, hopefully can do 5.0.4...

But if you know any newer TWRP multirom support for OP3T let me know
[OnePlus 3 & 3T Cross Device Development] :
Sorry, but I have no knowledge of multirom installations. Also: I think to ask multirom specific questions in the multirom thread will be more succesfull.
[OnePlus 3 & 3T Cross Device Development] tyler19820201:
Agree

Thanks for help
[OnePlus 3 & 3T Cross Device Development] Playa82:
Since last update i noticed the fingerprint dont work poperly anymore and i can unlock my device even when i cover the pocket sensor. Anybody else with this problem ?
[OnePlus 3 & 3T Cross Device Development] xhenon:
In my case is working fine, as always
[OnePlus 3 & 3T Cross Device Development] :
hey dianlujitao is there any or slight chance you will be working on one3/t after or duing

Huawei Honor 4/4X on the los16 which is slowly being developed? the work you did on 15.1 was amazing and rock solid stable

thanks in advance for your work
[OnePlus 3 & 3T Cross Device Development] dmrx921:
gapps error

Hello, after flashing the rom and gapps, google play and google services does not work.

What version have you put?
[OnePlus 3 & 3T Cross Device Development] :
Have you flashed rom and opengapps in one flashing session without making a reboot in between?
[OnePlus 3 & 3T Cross Device Development] dmrx921:
yes, it always did like that, you finish flashing both beams erase data and erase cache and restart.

Is it wrong?
[OnePlus 3 & 3T Cross Device Development] :
http://downloads.codefi.re/jdcteam/javelinanddart/gapps/MindTheGapps-8.1.0-arm64-20180808_153856.zip

If your question is: "What's wrong with my installation?" You need to provide the mandatory information - all answers regarding what have gone wrong with your installation based on the information you've supplied so far is just uninformed guessing.
[OnePlus 3 & 3T Cross Device Development] :
Again: information is missing!

Let's assume you want to clean flash coming from some other rom with a gapps package installed. You can wipe data and caches after the flash, but you must wipe system BEFORE!!! flashing the rom. Otherwise the gapps addon.d script can interfere with flashing gapps.

I recommend this order:

flash latest official twrp (currently: 3.2.3-0) and reboot to recovery

flash oxygenos 5.0.4 firmware and reboot to recovery

wipe system (at the very, very least delete /system/addon.d - I highly recommend wiping system!), data, dalvik and cache

flash rom and gapps package without rebooting to system in between

reboot to system

optional:

run through initial device setup and reboot to recovery

flash Magisk
[OnePlus 3 & 3T Cross Device Development] nasbdh9:
Waiting for oneplus to release the 9.x kernel source code
[OnePlus 3 & 3T Cross Device Development] :
ahh okay thank you for respons :)
[OnePlus 3 & 3T Cross Device Development] CodesCodger:
Why? 8.0 source is able to run 9.0 with. Many other roms are running just fine with 8.0 based kernels
[OnePlus 3 & 3T Cross Device Development] Perry3D:
After a some new clean installs with different gapps packages and no good results i finally installed caesium kernel and the problem seems to be gone. Even without any tuning of the wakelocks.

This night my phone only drained about 0.6%/h which is totally fine. There seems to be something wrong with the los stock kernel.
[OnePlus 3 & 3T Cross Device Development] :
you make it for me then? you are smart to know this above skilled devs :)
[OnePlus 3 & 3T Cross Device Development] :
I'm running los stock rom and stock kernel, drain is about 0.7%/h over night measured with bbs (with stripped opengapps super package). All sync services (gmail, WhatsApp, ...) enabled. So, no problem on my side with Los stock (kernel)
[OnePlus 3 & 3T Cross Device Development] Perry3D:
You can read my history about this topic. It only appears if i am logged into my wifi at home. As soon as i disable wifi the drain stops.

Maybe, but this i just a guess, my chromecast and/or google home is responsible for this. Used the wifi at a friends house at the weekend and there was no drain.
[OnePlus 3 & 3T Cross Device Development] dianlujitao:
op3 is the least priority device on my Pie bringup list, because it's for my daily use.
[OnePlus 3 & 3T Cross Device Development] :
It's not only your history. This randomly occurs on any builds for some users. It's related to wifi (I've never expirienced this myself, nor read a bugreport with wifi disabled). A kernel like caesium with [MENTION=947981]Lord Boeffla[/MENTION]'s kernel wakelock blocker is helping on this. I'm hunting this one for over 7 months, but still have no clue, what's the cause - the wl blocker is no cure, but hides the sympthoms successfully.

If you read the complete history of idle drain issues carefully, you'll find an other one, which occurs also with kernel wl blocker implemented. On that one I'm even more clueless, since I havn't been able to reproduce it, nor enough information to examine it.

You made my day! This implies a well maintained 15.1 and 16.x when it makes sense to switch the daily driver. :good::good::good:

I belive that in regards to a stable, feature rich and worth switching 16.x it's a good idea to wait for oss p sources as well as OxygenOS P blobs.

BTW: thanx for your efforts, contributions and solutions for Lineage and op3!
[OnePlus 3 & 3T Cross Device Development] DougRoberts:
Nice work on this release, thanks!

lineage-15.1-20180814-nightly-oneplus3

One problem I've discovered, however, is that Google Assistant doesn't work very well. About half the time the mic doesn't pick up my voice interaction. Instead it just hangs, and once hung a restart is required to get it working again.
[OnePlus 3 & 3T Cross Device Development] Viktorrr:
Does anyone have any issues with the USB Configuration on the latest LOS 15.1-20180814?

I can't switch the USB mode from Charging to File transfer (MTP) mode when my op3t is connected to PC. Switch of the modes just doesn't appear in the notification bar when I plug in cable connected to PC. My phone just starts charging. I tried to switch the usb mode in the Developers options as well but without success. Nothing changes when I select any others modes.

I thought there is maybe a problem with my cable - but it works fine with another device. Does anyone observe the same issue?
[OnePlus 3 & 3T Cross Device Development] DougRoberts:
Is it a USB 2.0 port, or a 3.0 port? They sometimes behave differently.

I don't have the problems you describe; switching the USB transfer mode works for me using USB 3.0.
[OnePlus 3 & 3T Cross Device Development] Spanking Time:
I had some awful battery drain on this ROM. Had to go back to OOS stock. Seems it only affects some users then.
[OnePlus 3 & 3T Cross Device Development] pitrus-:
It depends on the apps you use. OxygenOS has more aggresive app killer so if you use poor written apps or just apps that use up more CPU power or communicate a lot you get less drain by killing these in the background.

Skickat från min ONEPLUS A3003 via Tapatalk
[OnePlus 3 & 3T Cross Device Development] Spanking Time:
Nah. I'm talking complete idle with screen off. Battery drain for no reason and it's not apps.
[OnePlus 3 & 3T Cross Device Development] pitrus-:
That sounds more like with the default kernel without wakelock killer. I'm using Caesium kernel and get great idle/screen off power usage.

Skickat från min ONEPLUS A3003 via Tapatalk
[OnePlus 3 & 3T Cross Device Development] :
This posting is pointless: mandatory information is missing, and since you have switched to an othermrom it would be pointless to ask for more information. It also shows a lack of respect to the people trying to solve/work around this issue. Otherwise you would have tested a kernel with [MENTION=947981]Lord Boeffla[/MENTION]'s kernel wakelock blocker implemented (I really lost count on how often this is mentioned in this thread!).

I always wonder why people write things like foobar is so bad on the barfoo rom that I had switch to blafasel rom, without providing a proper bug report or trying the advices others posting on the same topic. This doesn't help the user posting this, nor other users suffering from foobar, nor the devs to fix it. On the other hand postings of this kind doesn't make the thread easier to follow for other users willing to help to sort out the issue... :(

There are very good reasons for the xda rule: search before posting.

[MENTION=4244522]pitrus-[/MENTION]'s explenation seems plausible as a trigger for the issue. I wonder what secret knowledge/information you have, denying it could be triggered by an app. If you read the postings on idle drain in this thread closely, you will find that the kernel wakelock blocker cures the sympthom of idle drain, though the wl statistics doesn't show wakelocks that sum up to awake while screen off time... So just because the misbehaving app isn't shown in the stats api, it doesn't mean it's not a misbehaving app. If it's an missbehaving app, which is killed early on oos, but is constantly unning on los, that would perfectly explain the idle drain difference between los and oos. Though I think it's related to wifi - it could be trigered by an app.

Again: your statement lacks all mandatory information, shows that you don't honor the postings allready written on this topic and therefor is pointless.

I guess you are right. I also guess this advice is routed to the void. At least the last 5 times this advice has been ignored by [MENTION=8988355]Spanking Time[/MENTION]... :(
[OnePlus 3 & 3T Cross Device Development] xuser_:
Sorry to eatup a post here but I had to admit that after your post I feeling improved a bit :)

Thanks!
[OnePlus 3 & 3T Cross Device Development] dmrx921:
In the end I solved the problem by flashing the rom the gapps (open mini gapps, the ones that gave error were mindthegapps) and I had the wipes (cache and dalvik cache) restart and everything was fine until now.
[OnePlus 3 & 3T Cross Device Development] Spanking Time:
You realize the dev doesn't support custom kernels and specifically asks not to report bugs if a custom kernel is used. He may be referring mainly to logcats, but the principle is the same and very simple: I shouldn't have to go find a custom kernel for this ROM to avoid my battery being eaten like a fat kid with cake on his birthday. Seems you're the one who needs to do some searching before posting.

A massive idle battery drain is not acceptable for a daily driver, especially for a ROM of Lineage's reputation. I did read the prior posts, and I know I'm not the only one who experienced this problem. Don't let your feelings get hurt so easily. I'm not busting anyone's balls here. It's a fine ROM other than the battery issue, but that's a BIG issue. It's nice to let other potential new users know of the problem because it's certainly not in the original post or the FAQ.
[OnePlus 3 & 3T Cross Device Development] :
You are completely right here, but on one point: the bug doesn't occur with a custom kernel, but the main sympthom is avoided with it. You are right again: it shouldn't be neccessary to use a custom kernel! Sadly that's the way it is.

You are right her, too. The drains described in this thread are not accaptable. They are around (randomly) since alpha state and since then I ry to hunt them down to no success. I know that the wl blocker is NOT solving the cause, but just the sympthom. Since not only me, but also the device maintainer doesn't know how to fix it, it's just fair enough to communicate the work araound.

Putting this issue in the faqs is surely a good idea. Fixing this (without any doubt: serious or BIG) issue is an even better idea - but I have to admit after 7 months of trying, I'm currently run out of ideas. I'm the first one appriciating if you can add additional information, ideas or solutions.

BTW: I don't feel hurt. I just tried to point out, that your original posting and the following conversation (including my own for that matter) does not offer any new information, ideas or solutions. I havn't meant to offend you - I'm just frustrated on this issue to answer the same over and over again.
[OnePlus 3 & 3T Cross Device Development] Spanking Time:
Fair enough. I have no evidence to support this, but I suspect some hardware aspect of the OP3T just doesn't play nicely with this ROM/kernel. E.g., the device has the off-screen gestures, which I assume are hardware based. We may never know for sure the cause of this battery issue though.
[OnePlus 3 & 3T Cross Device Development] :
It's not the off screen gestures - disabling gestueres in settings and kernel doesn't help, once the drain occurs.

I guess it's wifi related (not necessarily the kernel driver), because disabling wifi immediatly stops the drain. It returns asmsoon as wifi is enabled again (drain shows up -> disable wifi -> drain gone -> enable wifi again -> drain is present again), but I'm not sure if it's the kernel driver, something in the frameworks or an misbehaving app...

I really hope we can get down to this, because otherwise we can't get it fixed. I prefer getting a real fix rather then the brute force work around.
[OnePlus 3 & 3T Cross Device Development] iron@ss:
lineage-15.1-20180821-nightly-oneplus3 is up! :D
[OnePlus 3 & 3T Cross Device Development] adityaduggal:
Sorry guys for posting a newbie question, I have just tried to installed LOS but I am getting `assert failed: op3.verify_modem("2017-11-16 04:58:57") == 1`, now basically I am coming from stock unbrick and would like to know that if I flash the mentioned modem then assert should pass or do I need to flash some specific rom to update my modem and firmware.

I was getting the same error when I tried to flash this over OMNI ROM 8.1 so then I kind of unbricked my device came to the stock rom and again I am getting this error 7 assert failed.

[MENTION=5091734]dianlujitao[/MENTION] I can confirm that there seems to be an issue, I tried to install the 20180717 build of LOS15.1 gave me the same error but when I tried to install the Nitrogen-OS-O-oneplus3-20180808.zip it was installed properly so I am assuming that there is an issue with the build or is there something that I am missing still to install LOS
[OnePlus 3 & 3T Cross Device Development] Dirk:
Latest OOS ROM or just the Firmware .zip from that ROM.