It doesn't. Looking on the history of P2 forum, you're only trying to assume that this is the problem. One guy posted that his SoT increased by 1 hour, another dude said something about permissions and hurr durr, it's FM fault for sure!Yes, if you dislike idle drain, dont know why a phone needs to drain battery this much when its not being used? And why does the FM radio need to drain battery when its not even being used?
It doesn't. Looking on the history of P2 forum, you're only trying to assume that this is the problem. One guy posted that his SoT increased by 1 hour, another dude said something about permissions and hurr durr, it's FM fault for sure!
Give me the hard facts. If you're basing your theory on post of random person then we don't have anything to talk about. Lots of people on xda post such stupid things about battery life after installing weekly update. You need to make longer tests in similiar conditions to prove anything, not 1 charge like this dude mentioned. Boring.
Im on mokee 9 and battery drain is 2% over night so FM Radio is not a problem for me.
Having a different OS can make THE difference!
There were battery drain and no problems with FM Radio in Lineage OS 16.0 (Android 9)
In this screenshot are the FMRadio app permissions in LineageOS 17.1 from P2a42 January 2021 build.
View attachment 5240045
Can you post a screenshoot from your phone and give some details about mokee 9 OS ?
What? Cool, but stop philosophizing. I don't care about what you do, so that essay is completely unnecessary as in the end it is completely unrelated and has nothing to do with the case. You're assuming something on your theoretical knowledge, not testing.I’m a long time (20+ years) CB & ham radio user. A radio device, regardless of frequency, with a poor or no antenna uses more power and drains the battery quickly. On same principle in the remote areas the phone “chase” the cell towers signal, does a lot of tower chasing / switching and uses more battery. In such remote areas is recommended to switch the phone OFF or use air-plane mode to save battery!
Remember that P2 oem software phone has a function for the button on left side to switch to power save mode when all background apps are OFF to save battery!
The P2 phone uses the headset as antenna for FM Radio app and most of the time the headset (antenna) is not plugged in. The FM Radio app might scan, when the phone is idle, in the background 24/7 for FM radio stations.
Again, you're making assumptions that FM Radio does something (which it doesn't btw.) with no hard evidence. You didn't do any tests to confirm that it's AOSP radio fault, and I'm sure of that, because otherwise you would've share your results already. Instead, you're trying to defend your point with this unrelated wall of text and prove something... yeah, what?On the same analogy what are the details and the hard facts why a simple FM Radio receiver app needs to be ON all time on the background 24/7 use CPU time/power and have such system level permissions for location (GPS receiver) microphone and telephone?
Sure. I don't know if you already realised this (apparently not), but this change is project-wise, it was commited on 16.0 branch, and most importantly - it applies to ALL of the devices. Even better, this change is applied to other ROMs aswell. It's completely unrelated to what you reported about permissions aswell. That doesn't matter though as content of this commit is thing from the past anyway.The FM Radio app permissions were changed to system app level on 6 May 2020, that is 2 weeks from the Lineage OS 17.1 release. The last lineage OS 16.0 release (19 April 2020) the FM Radio app did not require any special permissions.
Coincidences? Maybe? Maybe not!?!?
Cool story. Maybe strip your OS to the bare minimum in such case, like some people do, build it and enjoy your "lightweight and power efficient" broken OS. Don't forget to add battery booster scripts and other crap. Not like the official builds are bloat-free already and completely fine on that matter.I’m sure that everyone agree that a clean and lean operating system with no bloatware is more power efficient and uses less battery!
There was huge jump in required specs to build a ROM starting from A10, then next one in A11. Maybe there was a jump for end-users devices too.I am assuming 10 simply requires more juice. One could of course try and tweak CPU settings, but this seems like a common issue among all Android users, not only this ROM.
There was huge jump in required specs to build a ROM starting from A10, then next one in A11. Maybe there was a jump for end-users devices too.
I can't tell for sure. It might be just a nasty bug too. 18.1 is too broken in current state for P2 to even consider testing if something has changed for better.
Mokee 9 is on Android 9
No problem. I'm not an insider though. I just built 18.1 on my own from sources that were available at the time of building to see where we are.Thanks for details and to take your time to share your hands-on expertise, in-depth knowledge and insider Lineage OS 18 development status/issues.
No problem. I'm not an insider though. I just built 18.1 on my own from sources that were available at the time of building to see where we are.
Can't say that I'm some kind of pro either. I just analyzed the topic a bit and checked out on these rumors if this makes any sense. It didn't, but I disabled FM radio feature completely anyway and checked this out, just to be sure. Android ports are hacky due to some parts of them being closed-source (thanks to OEMs), so it was worth giving it a shot, because some bugs are just weird and shouldn't be happening when you first look at it. That didn't make any difference though.
About these permissions... The commit you shared was kinda related to the thing, but you thought it added these "new" permissions for FM app. Commit itself didn't mention location permission for example. It's because it overriden FM app permissions actually and revoked it and rest of them. Since it was introduced on 16.0 tree, FM app in 16.0 builds, before it was merged, most likely had all of these permissions too. That's why they're unrelated to the battery drain at all. The latter commit I mentioned in my earlier post was introduced on 17.1 branch and it kinda reversed this behavior, so that's why you're seeing them again.
I can't tell why they can't be disabled and where this behavior is defined tho but it doesn't matter much as I said earlier.
You can also take a look at how priv-app allowlisting works in android documentation.
Major problems yet to be fixed for our P2. In case you haven't noticed, there is no 11 ROM for P2 working 100% yet, even though plenty of 11 ROMs have been released to the public. Wifi display is still not working and probably also some other things I don't know about.LineageOS 18.1 is Released officially. But is not avalible for Lenovo P2
#include <std_disclaimer.h> /* * Your warranty is now void. * * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features included in this ROM * before flashing it! YOU are choosing to make these modifications, and if * you point the finger at me for messing up your device, I will laugh at you. */