[OnePlus 5T  ROMs, Kernels, Recoveries, & Other Dev] mad-murdock:
Top!

Naja, auf jeden Fall was unter 10 sekunden. Und ob 60 sinnvoll ist - bei wem klingelt das schon 60 sekunden?

5/10/15/20 oder vielleicht sogar 3/5/10/15/20. Müsste hören wie 3 klingt in Anwendung. Außerdem wette ich wir treiben hier grade Leute in den Wahnsinn weil wir deutsch quatschen! Lol!

---------- Post added at 06:31 PM ---------- Previous post was at 06:29 PM ----------

If you really want to save battery over night, go to airplane mode. Airplane mode used to save even more battery than switching a phone off and later on again when I tested it a few years back. Up to a day.

---------- Post added at 06:37 PM ---------- Previous post was at 06:31 PM ----------

If your phone drains 11% over night (assuming 8 hours) with wifi+LTE turned off then something is VERY wrong and I would suggest a clean install with carefully restoring apps. Assuming AOD is off, you should look at 0.5%/h to a maximum of 1%/hour. But 1%/hour is already a pretty high value. And those values are WITH wifi and the usual background checks for notifications.

---------- Post added at 06:46 PM ---------- Previous post was at 06:37 PM ----------

Wow! Something kept your phone awake 50% of its sleep time. If you click on summary, you can choose kernel wakelocks and partial wakelocks - that should give you an idea which of your apps is missbehaving.

Also, since Nougat an app missbehaving like this should be forced to doze by the system. There are currently only 2 ways around being forced to doze: Being a system app - aka did you flash additional zips over the omni zip which contains system apps. Or having a special place in the settings -> apps&notifications -> special app access -> battery optimizations. That list should be VERY short and only contain stuff like cellbraodcasts, some com.qualcomm.* stuff, download manager, google play services, shell. Thats it. If you got other entries there, its highly likely that app is responsible.

If both things are normal, there is a possiblitly you stumbled upon a bug. But from experience, its 99% user apps. A phone being awake 50% while its screen turned off is for sure NOT normal.

---------- Post added at 06:48 PM ---------- Previous post was at 06:46 PM ----------

Maxwen wrote a few pages back whats the reason for the re-build. It was something with settings crashing when you access mobile networks under a certain condition.

---------- Post added at 06:53 PM ---------- Previous post was at 06:48 PM ----------

There are 2 searches on XDA. On the very top to the right is the global XDA search. It is not very useful if you just want to know anything about your rom. Above the first post, there is a smaller, visually more hidden search field. It only searches this thread. If you had searched for TWRP or password or decrypt, the answer to your question would have probably been in one of the first 3 results.

---------- Post added at 07:03 PM ---------- Previous post was at 06:53 PM ----------

Honestly, transfering files via MTP (the name of the "new" protocol) is a mess. In the old days, when you just had your devices attached as USB storage, there was nearly never any issue with it. But google had to change it because people did crash their filesystems all over the place due to disconnecting the cable without first unmounting the device. (The "remove storage" icon in windows). So MTP was born - or better said put to use.

And... its... terrible. On windows it works most of the time, on linux it can be somewhat complicated to get running, even though it got better. But even IF it is working - try to copy some files and while copying try to browse your device. It will hang, since only one operation at a time. It can even crash the running copy process. Sometimes the only way to get it working again is to disconnect your device and reconnect it again. In short: MTP is a mess. It's not unusual if it does not work.

Also, you dont get a drive letter. So if you use a fancy nice file explorer (big fan of total commander here), it wont even show up. The device only shows up - and is browsable - in the windows explorer under "This PC".

I am sure I did not fix your problem, but I had to rant against MTP. Was there really no better protocol back at the day?

Edit: There are 2 options to using MTP. One would be accessing your files via adb. Adb is pretty stable - and with tools like ADB Fileexplorer it becomes an UI instead of just being a command line tool. And if you got a decently working wifi, you can access your phone via tools like airdroid or wifiexplorer. Granted its not that comfortable compared to raw explorer access, it at least works.