yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] Ruggerxpunk:
I'm sorry to say that I don't believe you at all unless you're using your device at 1% brightness while watching a 5 hour movie.

There's a big difference between 5 hour SoT, and having your device actually on for the entire day (from when you wake up until you go to sleep).

The screenshot is likely not from the OnePlus One device.

Or it was the same scenario I described above, 1% brightness, everything else off (Wi-Fi, Location, Bluetooth) while letting the screen sit on the desktop for 5 hours, or watch a movie for 5 hours.

You can't claim an arbitrary amount ("maybe 3-4 hours") and then immediately declare that you don't monitor it.

It makes your claim null and void.

I'd like to see some community screenshots of real-world usage (using Hangouts, using Maps, using Chrome, using Facebook, etc.) and I guarantee by the end of the day, the average will be 1.5 hours SoT with the highest drain being Mobile Network Standby.

It isn't just our device on Oreo with this issue. It affects both OEM ROMs and Custom ROMs alike:

https://talk.sonymobile.com/t5/Xper...twork-standby-battery-drain/td-p/1287134#gref

https://forums.lenovo.com/t5/Moto-Z/Mobile-Network-Standby/td-p/4049381

https://xdaforums.com/mi-5s/help/mobile-network-standby-draining-battey-t3762776

https://xdaforums.com/htc-10/help/mobile-network-standby-t3742458
[ONE Original Android Development] adibeckett:
I'm usually on 75% WiFi and 25% Lte throughout the day. Medium brightness. Again I basically just watch YouTube, browse internet and forums. No gaming.
[ONE Original Android Development] rob.d.s i9505:
Strange to read in them articles that super su is better for battery
[ONE Original Android Development] uudruid74:
If you are only getting 1.5 hours of SOT, your phone is ****ed. If you have a mobile standby drain of 50%, something is very wrong

---------- Post added at 05:10 PM ---------- Previous post was at 05:08 PM ----------

Wouldn't make any difference. Neither supersu nor magisk stays running. It spends all its time asleep and makes zero impact on battery.

---------- Post added at 05:13 PM ---------- Previous post was at 05:10 PM ----------

I don't do any of that. Maybe you guys need to replace your old worn out batteries!
[ONE Original Android Development] Syaani:
I just bought new one. Still running Nougat though.
[ONE Original Android Development] Ruggerxpunk:
Please provide screenshots of both your Battery Stats and your About Phone in order to corroborate your claim that you're achieving 5 hours SoT on the Oneplus One.

Otherwise I'm sorry, but, it's impossible to believe your claim.

First of all, you're not even using a OnePlus One, you use a OnePlus 3T as indicated by your signature.

So your comments on this forum relating to this battery conversation are irrelevant.

Secondly, you're parroting my point which is: having a Mobile Standby Drain of 50% means something is very wrong, and it is very wrong on each and every Oreo and Pie ROM for the OnePlus One, as well as several other devices as I've pointed out in my links above.

The main point I'm attempting to convey is such that:

Discussing Battery Life discrepancies between Oreo or Pie ROMs is useless because they all suffer the same Mobile Network Standby battery drain issues on the Oneplus One.

That's a fact.
[ONE Original Android Development] 19Gonzo82:
I've had SOTs of 4-5 hrs on TugaLos Oreo as well. Using the phone mainly on WiFi, browsing 9gag, Xda and YouTube. Achieved that with some kernel tweaks though that aren't possible on this rom I think.
[ONE Original Android Development] uudruid74:
I have both numb-nuts. My Oneplus One, using the tricks you accuse people of, gets 9+ hours of SOT and thats well documented. My One gets the same battery life as my 3T, if not better. Its currently running this ROM.

I monitor battery carefully and never seen a 50% drain from anything
[ONE Original Android Development] bageraz:
My current battery stat (dont know good SoT or not).

Greenify most less to none use apps with root & xposed, brightness control with lux lite, wifi always off (wifi speed suck in my current location), location always on, did not use Bluetooth, printer service off, gboard, gmaps installed, rotation always on with 3rd party apps (broken screen need to rotate), no gaming, mostly for news & whatsapp. And btw still on POSP v1.
[ONE Original Android Development] adibeckett:
Mostly on WiFi. On the latest Post V2.0 beta and kernel. No kernel mods. Only Magisk modules I use are Nav bar Disabler and viper.

Chroma keyboard, Facebook, Facebook messenger are installed. Auto rotate is enabled.

I guess not bad for a 4+ year old one plus one battery?
[ONE Original Android Development] Ruggerxpunk:
Please provide proof to your claim via a screenshot showing the percentage that your Mobile Network Standby uses from your OnePlus One (and please try to do so without becoming emotional or name-calling).

Thanks for showing the proof of your Mobile Network Standby battery drain.

The scenario you're showing via your screenshots is a little different than the issue we're discussing here.

In your case, your phone only lasted 7 hours throughout the day, but it's because you drained it with 5 hours of almost successive usage.

The issue with these Oreo and Pie ROMs is that the Mobile Network Standby will drain the battery constantly throughout the day no matter what, even when the device is idle, and even without a SIM card.

So whereas the OnePlus One (back on Marshmallow, etc.) used to never drain battery at all when idle, these new ROMs/architecture have introduced this Mobile Network Standby bug which will drain the battery indefinitely.

So again, my point is that it's pointless to discuss battery life comparisons between different Oreo/Pie ROMs for the OnePlus One.
[ONE Original Android Development] novecentoundici:
There's a

massive

difference in standby drain turning the mobile network to 2G when not using it (Wi-fi or screen off). Since neither the ROM include the automatic option, nor I can use Xposed's Gravity Box or similar (which I've been using for years), I installed Toggle Network Type and I manually disable 4G. This way I can get 3 days standby (with battery charged up to 80% and down to 20% or so) with moderate use.

Accubattery reads a 0,6% drain with screen off.
[ONE Original Android Development] rob.d.s i9505:
So switching to 3G made a massive difference then?

I am wondering what the battery drain is if we turn our devices off at night?
[ONE Original Android Development] bageraz:
Should be no battery drain at all if turn of device all night imo.
[ONE Original Android Development] Timmmmaaahh!:
Well that could technically be achieved but your device wouldn't wake up anymore (or at least take a long time to do so). A motion sensor needs to be fed some juice for when you pick up your device so it can wake up some services to make sure that when you double tap that screen, it immediately wishes you a good morning. 1-2% should be acceptable.

Hi Rugger! Please allow me to pinch in here. IMHO you're making a very empty point there. You could state that based on the things you've seen but you may have been deceived. First off, it may not even be drain at all. There's a pretty good chance that mobile use has always been this high but since the overhaul of battery stats in Oreo, Android may be reporting it more clearly. I do recall some 'Android' and 'System' services pre-Oreo that many people used to report drain about but no one really knew what they were exactly. It's just another theory; we really don't have any solid facts to prove anything.

Let's also keep in mind that hardware support dropped years ago. I'm sure [MENTION=4800121]Sultanxda[/MENTION] can testify an incredible amount of shims are holding this device together. I'd be quite surprised if this didn't have any impact on battery life. Then again, what do I know? :D

Oh man, the 5+h of SoT screenshots go beyond me as well. Believe me when I say I've tried every single trick in the book but except for a handful of accidental successes, I've failed to achieve this number in regular day-to-day use. Even since I've replaced my battery a few months back, not much has changed.

Given the erratic way OnePlus entered the market back then, I'd guess there's a bunch of devices that got lucky and a bunch of them didn't (read: we got duped). There could of course be a different usage pattern in play here. Specific apps we're overlooking, the way we carry and care for the device or yes, even manipulated test results. Everybody lies, right? I have attempted manipulation myself and it's really easy: just enabling caffeine (keep the screen awake) and leaving the device for a few hours will gain spectacular results.

Here's a useful pointer to all though (so this off topic mumbo jumbo at least has some meaning): I've completely stepped away from the classic overnight charging. I've spent many hours of research on this (great source) and it's generally just not a good idea to keep your device plugged in at night. So I've adopted the 20/80 rule, keeping my battery charged between 20% and 80%. Therefore I have no reliable battery stats to share but I can proudly say that AccuBattery is showing that my battery health is 93% - Based on 126 sessions with 5,456% charged for 156,861 mAh total. All it takes is a different charging habit.

Anyway, your conclusion is most correct:

So perhaps it is best to leave it at that.
[ONE Original Android Development] Agent_fabulous:
Cool, I'll try adding it.

I'm sorry for the slow updates, I got caught up with college projects and events here. I'll try to push updates as soon as I can. Thanks for cooperating :)
[ONE Original Android Development] 19Gonzo82:
Dude, take all the time you need. Glad some fabulous dev keeps that trusty bacon alive and brings it into pie age ;)
[ONE Original Android Development] Tagkaman:
Hey, great rom. Just wondering if it would be possible to have the option to change the corners back to the default level of rounded-ness. Just looking for that full vanilla pie experience :)
[ONE Original Android Development] uudruid74:
First, a 5 hour movie is an awefully long movie, and I don't know why you think decoding h.264 video is child's play, but it ain't. You must be too young to realize how hard it really is if you are comparing it with an idle device.

Second, I just brought my OnePlus One with me all day long. I've been using it without a SIM, but your report states that the drain bug you speak of should still bite. I even had Waze going for about 2 hours, screen at about 75% so I could read it in the car, and didn't plug it in. I charged the phone 16 hours ago and I still have nearly 20% battery left. No Greenify or other tweaks. My usage graph and screen on time isn't showing on the stock battery graph (says 0 mins SOT - anyone else getting this?) but Accubattery says with today's usage I'll have 4.5 hours SOT and it measured 3 hours so far. Based on idle drain, it an stay on and sleeping for over 63 hours.

I actually expected a lot better. I'm used to 6+ hrs SOT and over 100 idle, but maybe it will pick up. I may put my old Lollipop ROM on it to compare.

but 1.5? You've got issues. You aren't chicken little so stop acting like it

---------- Post added at 04:03 AM ---------- Previous post was at 03:59 AM ----------

Little note. It takes about 2 years for your battery to degrade to where a full charge is only 80% of the life of a new battery ... So if you charge to 80% ... Then you are getting 80% battery life NOW rather than 2 years later. And the degradation curve isn't linear ... The decay actually slows. Seems pointless to me.
[ONE Original Android Development] uudruid74:
you really need to post the bottom of the discharge screen ...
[ONE Original Android Development] bipinbaglung:
Is the issue with Google Pixel Setup Sync related to this ROM or it is related to the GAPPS given here?
[ONE Original Android Development] subdancer:
It was a gapps problem and it was not the only one =)

The problem is fixed with the latest gapps version from 5th september.

see here: https://xdaforums.com/showpost.php?p=77540507&postcount=211

download here:

https://builds.nezorfla.me/?dir=opengapps/pie/arm/20180905

I've tested pico and nano. both work without problems.

you can flash rom and gapps directly together as usual without booting up in between.

[MENTION=5834335]Agent_fabulous[/MENTION]

I've found this bug while doing some logcat stuff.

it's happening whenever you activate the phone from standby and sometimes also in between. my log is full of it.

09-07 03:53:53.881 671 3016 D WificondControl: Scan result ready event
09-07 03:53:53.892 671 694 I EthernetTracker: interfaceLinkStateChanged, iface: wlan0, up: true
09-07 03:53:54.538 316 316 E WifiHAL : wifi_get_link_stats: requestResponse Error:-5
09-07 03:53:54.542 671 2079 E WifiVendorHal: getWifiLinkLayerStats(l.937) failed {.code = ERROR_INVALID_ARGS, .description = }
09-07 03:53:57.559 316 316 E WifiHAL : wifi_get_link_stats: requestResponse Error:-5
09-07 03:53:57.567 671 2079 E WifiVendorHal: getWifiLinkLayerStats(l.937) failed {.code = ERROR_INVALID_ARGS, .description = }
09-07 03:54:00.615 316 316 E WifiHAL : wifi_get_link_stats: requestResponse Error:-5
09-07 03:54:00.620 671 2079 E WifiVendorHal: getWifiLinkLayerStats(l.937) failed {.code = ERROR_INVALID_ARGS, .description = }

another one:

09-07 04:49:51.617 349 349 W wificond: Copy constructor is only used for unit tests
09-07 04:49:51.618 349 349 W wificond: Failed to get NL80211_ATTR_EXT_FEATURES
09-07 04:49:51.618 349 349 W wificond: Copy constructor is only used for unit tests
09-07 04:49:51.618 349 349 W wificond: Failed to get NL80211_ATTR_EXT_FEATURES
09-07 04:49:51.619 349 349 W wificond: Copy constructor is only used for unit tests
09-07 04:49:51.619 349 349 W wificond: Failed to get NL80211_ATTR_EXT_FEATURES

Those might be related to the wifi issues some people posted.

Google also released security patches for september.

Can you pls give us a bump to android-9.0.0_r8 with the next update? =)

I also can't wait for the dark theme. It would be great if the notifications would have a dark background as well if one activates Device Theme: Dark in display settings.

It would be also nice to change the color of the black bar on top where the clock and battery is ( i guess that's the notch bar =) ) so it fits to the dark grey. see picture.
[ONE Original Android Development] bipinbaglung:
:good:

Now official OpenGapps has also been released. I will try that.

Thanks.
[ONE Original Android Development] Agent_fabulous:
Afaik, this shouldn't make much of a difference.

Also, I'm not gonna lie, the WiFi fix was purely experimental. I was trying to move things around in /data and it happened to fix WiFi. I could find no reason why it wants to load the wcnss config from /data/vendor/wifi. Looking through relevant sources, it should be loading it from /data/misc/wifi, but whatever. It works with a simple symlink xD

Corresponding change: f399ed57

Also, revision bumps are easy. I'm trying to get some basic functionality restored first :)
[ONE Original Android Development] atulpchaudhari:
Where can i see changelog of new update?

Thanks in advance.

---------- Post added at 03:37 PM ---------- Previous post was at 03:32 PM ----------

As latest android pie GApps available here which package to flash micro or nano?

---------- Post added at 03:37 PM ---------- Previous post was at 03:37 PM ----------

https://opengapps.org
[ONE Original Android Development] bageraz:
The glory of the dark theme is upon us and shall we wait for thee glorious day:cool:
[ONE Original Android Development] Ramana_369:
1. Screen cast is not working properly.

It is able to connect but after connecting showing ablank screen and then disconnecting.

Tried with sony bravia led tv. Can you please check and solve the issue.

2. How to disable onscreen buttons?

3. Trusted Facial recognition is not working
[ONE Original Android Development] bageraz:
Just want to inform that opengapps is working as intended
[ONE Original Android Development] bageraz:
Btw why the notification panel does not go full drop?
[ONE Original Android Development] 19Gonzo82:
If only people would search threads before reporting the same bugs or asking the very same (already solved) questions over and over again...
[ONE Original Android Development] lepidas:
USB debugging disabled, connecting to my pc, >Tap for more options, all options are greyed out.

USB debugging enabled, the same as above

USB debugging enabled and Default USB configuration file transfer, then my pc gets disabled(frozen)for 5-6 seconds, in the Android still all options by the taskbar are greyed out.
[ONE Original Android Development] subdancer:
Ok, i see! Thx for clarifying and no worries, your hack works great. Wifi is working fine and i also didn't have a problem with it so far.

It's just

logcat | grep Error

shows the error popping up like every 3 seconds. I guess after a day it might have caused a tiny bit of drain. I'll investigate further. If someone else here can help us fix it pls join us.

In the meantime i'm trying to wrap my head around the posp2 code. I have some more questions if you wouldn't mind:

I was searching for the source code reference for: Settings->Display-.> Device Theme "Dark" . Is this the right spot ? -> https://github.com/PotatoProject/vendor_potato/tree/baked-release/packages/overlays/DarkCommon

To change the background color of the top black status bar (picture from last post) we would have to change

<item name="android:colorPrimaryDark">@*android:color/primary_dark_device_default_settings</item>

in https://github.com/PotatoProject/ve...Common/SysuiQsDarkTheme/res/values/styles.xml ?

I guess you are doing it in the right order :good:. Would it be possible to automate the pull of the revision bumps and trigger a jenkins to build the source every time google pushes out a security update? That way we would have the benefit of early security updates. No clue how much manual changes are needed for every security bump. Just thinking out loud.

Thank you very much for all the work you've put into all of this so far!! Countless commits! Bacon is getting legendary because of you and we all wouldn't be here without you =)

I can't wait for the next stato of potato :cyclops:
[ONE Original Android Development] se7enlyn:
just transferred some files from my desktop to OPO yesterday and i didn't encounter such issues.
[ONE Original Android Development] se7enlyn:
Here:
[ONE Original Android Development] se7enlyn:
Additional screenshot
[ONE Original Android Development] rob.d.s i9505:
Ok can you give me a run down what you have on?

That's amazing life
[ONE Original Android Development] Ruggerxpunk:
nothing wrong with my phone, in fact it's not half bad all things considered. Proof attached.

Now let's see yours.
[ONE Original Android Development] se7enlyn:
Please go to page 33 , post #325

Nothing special running, all stock, no changes made in kernel settings.

Flashed the rom with pico gapps.
[ONE Original Android Development] jerryhou85:
Dear all,

Thread has been cleaned up to remove off-topic posts. Please post on the thread subject and respect each other.

Thank you.

In case you forgot our rules:

2. Member conduct. 2.1 Language: XDA is a worldwide community. As a result, what may be OK to say in your part of the world, may not be OK elsewhere. Please don't direct profanity, sexually explicit language or other offensive content toward Members or their work. Conversely, while reading posts from other members, remember that the word you find offensive may not be offensive to the writer. Tolerance is a two-way street.

2.3 Flaming / Lack of respect: XDA is about sharing and this does not involve virtual yelling (flaming) or rudeness. Flaming or posting with a lack of respect is unacceptable. Treat new members in the manner in which you would like to have been treated when you were a new member. When dealing with any member, provide them with guidance, advice and instructions when you can, showing them respect and courtesy. Never post in a demanding, argumentative, disrespectful or self-righteous manner.

2.4 Personal attacks, racial, political and / or religious discussions: XDA is a discussion forum about certain mobile phones. Mobile phones are not racial, political, religious or personally offensive and therefore, none of these types of discussions are permitted on XDA.

10. Help others if you can.

If you see posts from others where you can help out, please do so. This place exists because people are helping each other, and even if you are relatively new to the matter, there's probably quite a few people with less experience than you, who could benefit from what you've learned. Don't be shy.

15. Keep threads / posts on-topic

Whilst a minor amount of off-topic posting may be overlooked, the general rule is that your posts / threads must be relevant to the Forum / thread in which you are posting.

General Forums - For news and announcements relating to your device.

Q&A Help & Troubleshooting Forums - For all question / request threads and posts. If there is no Q&A Help & Troubleshooting forum, use the General Forum of the relevant device

Accessories Forum - For posts related to accessories relevant to the device

Development Forums (ones with the word development in the title) - For Developers to post release threads e.g. ROMs and Kernels including modifications to kernels, bootloaders, ROMs, etc., as well as R&D development discussion threads designed with an end goal

Themes and Apps Forums - For the posting of Themes and / or Apps as well as announcements & discussions including modifications made to Themes and Apps.

Regards

Jerry

Forum Moderator
[ONE Original Android Development] alma23:
No need to be sorry, nevermind the updates, take all the time you need! It's your free time and your abilities, so we just humbly ask but we don't want you to waste your time with our requests and we couldn't be more grateful than we are now anyway (man, your work with Oreo has been Fabulous too, we haven't forgotten it)!

Good luck (even if I don't think you need that LOL) with the college and thank you again for all your work! :)
[ONE Original Android Development] jaspreettttt:
Anyone else having GPS disconnect for a couple of seconds then reconnection?

Happens several times. Especially when driving with Waze or Google maps.
[ONE Original Android Development] bageraz:
Known issues. Try install gps locker to minimize the issue
[ONE Original Android Development] KuldeepShivankar:
Hi, i'm currently on RR- Oreo. I want to try this android P ROM. Can anyone tell me if the hardware touch buttons are working or not?

And any major bugs?
[ONE Original Android Development] grinimark:
I did the same change some days ago. Backup in twrp...don't forget.

hardware buttons are working as usual, but they don't have backlight.

I flashed the ROM together with the pico GAPPS.

All running buttersmooth...is really a fine ROM...I'm just missing the endless possibilities of customization in RR.

Mark
[ONE Original Android Development] KuldeepShivankar:
Thank you. Actually i've given my opo to my dad. So he want simple UI so customisation is not My priority for now. :)

-Can i use nano gapps? Or only pico is required?

-Flashing thunder kernel breaks camera?

-Did you encountered random reboot?

Thanks again. :)
[ONE Original Android Development] jaspreettttt:
Will try

Will try a gps locker.

Thx
[ONE Original Android Development] bageraz:
Flash thunder dont break camera. None random boot for now.
[ONE Original Android Development] KuldeepShivankar:
And what about nano Or pico gapps?

substratum works?
[ONE Original Android Development] bageraz:
Both are good. Imo better get nano for extra stuff. Substratum i dont know, never tried on pie.
[ONE Original Android Development] beatbrot:
Is there any way to disable software nav-bar and remap hw-buttons already?
[ONE Original Android Development] kunalshgkr:
while setting up the the device i'm getting this pop up "pixel setup keeps stopping"