yashsingh1/xdaforums huggingface dataset:
[G4 Android Development] Bleuzen:
Yes, I can confirm this. After 3 days of using, I never had battery problems with my build, (which is also 5.2).

I made a new one today and will test it a bit. If it works, maybe I will create a second thread where I post this as 'temporary builds'.

Btw. this is NOT my Rom. I just built it, but it is still (mainly) kessaras rom.

Until now I did not change any code or files. Because I'm NOT an Android Rom developer!

(But maybe I will make a change soon, because if kessaras keeps the 'faster charge' change, I will try to revert it for my builds!)

I mean: this makes no sense to me. The problem is not charging, the problem is battery drain! Why should changing something with charging help?

(Anyhow, this is not to bash kessaras. I still like the work he does. But I also just want to help (at least as much as I can with my knowledge). So I also say a bit bad things sometimes, but I don't mean it that bad!)
[G4 Android Development] tambukey:
TL;DR 99% of user complaints are USER ERROR and are not [MENTION=5461026]kessaras[/MENTION] 's fault.

The battery problem isn't even a problem either and Kessaras knows this. It is RILD running heavy that is the issue. It is a random on boot problem. The issue is people can't recognize that or do not know how to check if that is what is killing their battery. I have had Zero and I mean Zero battery/ charging problems since sometime in January. I say zero once I actually understood what the problem was. Charging was due to the wall adapters I was using, as well as not recognizing that my phone was too hot to charge faster. At 30C(this is my best guess) or less, you should be able to achieve max charge. I have seen all the way up to 1780mA. Right this minute i'm at 36C and getting 600mA(which is still higher than some are reporting). All excessive battery drains came from either a runaway RILD or app issues that all could be fixed via a few terminal commands. Download RIL control from app store(if you are rooted). Use that app to fix any RILD runaway or no SIM detected issues. Just tap the stop button once, then start once and it will work every single time, and be patient it takes a second for the script to run. And honestly there is no reason to no root any more and the root allows us free users to do our own troubleshooting and correcting.

Any one complaining about battery or charging isn't doing their own part. Try launching phone in safe mode to be sure that there aren't underlying issues that have nothing to do with the rom. Most of the complaints on here are single user issues. Unless everyone that got onto these forums had the same issue, then it isn't up to [MENTION=5461026]kessaras[/MENTION] to fix it.

Learn to work for yourself and be thankful to kessaras for getting us to Oreo. Do research and learn the Android operating system.

To understand the RILD runaway better: this occurs on a boot. that is the reason you can go days(indefinitely) without any battery drain fault. If the runaway doesn't occur at boot, it wont the rest of the time on that boot. Any phone reboot/ (restart of RILD) has the possibility to runaway. Easiest way to check if it is the culprit is using the Terminal. (go to developer options and turn on this option) in the Terminal enter:

su
top

and watch it for a bit. You should rild on the right hand side. if it isn't runaway it sits about 0.3- 0.6% CPU. When it does runaway it'll be one of the top 3 processes. If it is runaway, open the app RIL Control, hit the stop button, wait, hit the start button, and there you have now fixed your massive battery drain issue.
[G4 Android Development] Bleuzen:
It is not a random on boot problem. This always happens to me with kessaras builds. I already restarted often, but everytime the battery drains very fast (what also ends up in slower charging). So this is not random, it's always.

Now I only know the fact, that with a build I did on 20180211, I never had problems with the battery. Even not after some reboot.

Now compare to the problem:

kessaras build: always fast battery drain

my build: never fast battery drain

Got it? Right, it's a new bug, not that random rild thing anymore! (Ok, I'm not 100% sure right now, but I guess.)

And I don't hate kessaras. I still like him! Because he has done a lot and made O working on our device. This is great!

What I do is just trying to help how I can. Even if it is currently only this bug report and the fact, that it works on my build.

And no, I'm not alone with this problem. This is not a single user thing. And my build fixed it (even if I not changed code) not only for me.

I know, I didn't write a fix. Until now I just wanted to share my experiences / what happend to me.
[G4 Android Development] tambukey:
Trust me the RILD is a completely random(in terms that I don't understand yet what causes it) thing and it does not occur everytime. I have gone over 20 boots without it ever happening. I have also gone boot after boot with it happening. If you did not change anything on your build then how did it magically get fixed?

RILD issue has been around for a bit, I don't remember which build the runaways started, but I know when I was on 0204 it happened a couple times. On 0212 again it can occur. Currently on 0215 and it still runs away.
[G4 Android Development] ntnlzr:
man just use your build, or open a new thread with your build but stop to compare your rom with this one pls
[G4 Android Development] Bleuzen:
Ok, I will test and compare builds some more days and see. Thanks for your information, I will keep an eye on rild.

Maybe it's really just luck (cause you said 20 boots.. don't know, if the luck lost me and SeewolfPK for kessaras builds).

So I will test things a bit more...

Well, the reason why I think I could be fixed in my build, is because it's one day older than kessaras first 5.2 build. Don't know, if there were bad changes on that day. So even if I didn't change anything, there could be a difference.

I will shut up about this for now. (I think it's better to not spam this thread.)

And maybe, only maybe, I will open a new thread someday for this. Will see..

---------- Post added at 05:20 PM ---------- Previous post was at 05:17 PM ----------

Again, this is NOT my Rom. This is still the one of kessaras. I think I just did a 'somehow lucky' build.

And I know, I could 'just use it'. But I wanted to help, even if it is just by the fact that the bad change (if there is one) happend between 20180211 and 20180212. (But this little message I wanted to share gone a way to far I think.)

So as I said, I will stop writing about it here now. And yes, I think your right. I should open a new thread (if I could get 100% sure that it is fixed).
[G4 Android Development] kessaras:
Guys you totally ignored my post where I announced the today's build. I said rild bug which drains battery it's fixed.

Charging fast is fixed.

Battery drain is less. Still not as good as before but it's better and I will improve it.

I never said I can't.

I only said I need time. I can't go faster. Whoever wants to go faster , he may sync and help.

And your build [MENTION=8773692]Bleuzen[/MENTION] , I will say it again.

It wasn't 5.2. You only synced to what others pushed not g4 updates because I hadn't push yet my work.

If I stop developing and you build one month later , it doesn't mean it's up to date. Look lineage. Is lineage up to date if you build now ?

No it's not. Because our device needs a Los maintainer.

Same is here. Without me updating you only sync to old stuff and build.

So do not compare what you built to what you will build.

And now for example if you sync and build , you will have big battery drain , because I haven't merged the changes I did today and fixed what I fixed.
[G4 Android Development] Bleuzen:
Nice, that it's fixed now, thank you!

(Yes, the only reason for my build some days ago was aoscp 5.2, so with security patches and so, not the G4 updates itself. I know that and I already understood it. So now we can stop talking about it, this is history, since you said it's fixed anyway ;))

One question left: You said that it is not a good idea to let it charge over night with this build. Is this still the case or did you revert this or change something again?
[G4 Android Development] kessaras:
its safe. i let it 3 hours + on charger to make sure it will be ok.

saying its "not safe" its from technical side. as a pc mechanic i know that when we send more mA at a battery , if the battery is full, it will go ka-boom.

but the flow here when its closing to 100% take it slow and doesn't send so many mA. so it's good.
[G4 Android Development] tambukey:
Hard to comprehend exactly what you're saying. For February 15 build, RILD is fixed? Or are you saying you fixed it on your end, but it wasn't merged into the February 15 build?
[G4 Android Development] ThePiGuy:
That's great - well done :)

Just out of interest (it's not a big issue, but I was just wondering), has the issue of the SIM sometimes not being detected on boot also been fixed

Also, thanks for all your hard work - it's great that Oreo is working on our G4's
[G4 Android Development] SmokeTooMuch:
Where to find the option for the advanced restart menu on AOSCP 5.2? I can't seem to find it.

I'm running the aoscp_h815-5.2-20180215-unofficial build and I can tell you it's not fixed yet.

Also, the torch tile doesn't work.
[G4 Android Development] Minto107:
Yep, rild doesn't seem to drain my battery any longer on today's build

Use search on xda, it doesn't hurt, I've already said how to do it
[G4 Android Development] deltadiesel:
Sure you could

Because your the one that added it. It worked on previous build of Oreo

How do I remove device check?
[G4 Android Development] ThePiGuy:
I think the point might be that disabling the device check might cause more harm than good, as it protects people from accidently flashing the wrong software
[G4 Android Development] deltadiesel:
No way? It works on my device and he ADDED 810TO AOSCP NOUGAT before so what's the problem now
[G4 Android Development] bedencic:
long press restart to get advanced menu.

for torch tile use flashlight tile fix kenzo (search in google play)
[G4 Android Development] Minto107:
If you would have opened updater-script you would already know... That's just being lazy

[MENTION=5461026]kessaras[/MENTION], could you check kernel in latest version? Mine starts default with performance governor
[G4 Android Development] tambukey:
download the h811 zip, then edit /META-INF/com/google/android/updater-script. You'll see all the 811s, change them to 810? I'm no expert, may have to change where p1 is too, not sure if that is device specific.

edit: Actually I changed my mind, changing the h811s to match your h810 should would, so long as the rom actually supports it. For that updater_script the assert checks for any of those within ro.build.product/product.device through a bunch of OR statements; therefore any true return should allow the installer to run. But again I am only looking at the updater script, im not looking at any other files., but Kessaras even said you could just edit that file a little while ago.
[G4 Android Development] deltadiesel:
Right because I know what an open updater script is....

---------- Post added at 09:11 PM ---------- Previous post was at 09:10 PM ----------

Anyone know specifically? Thanks
[G4 Android Development] Minto107:
You got an answer in 2nd quoted post... Have you at least opened that file? You're the type of guy that I said that never should unlock his phone as he doesn't know what he's doing
[G4 Android Development] obvious:
http://bfy.tw/GcuU
[G4 Android Development] #ApolloLiteProblems:
If you don't know what it is, search it! It's really simple and clears space in the thread for those that have genuine new bugs to report, which at this stage will be very few because the ROM is very stable considering the state of G4 development and that Kessaras is one person developing the ROM.
[G4 Android Development] vellanifederico:
v29A stock to AOSCP

Hi,

In the end I tried to install AOSCP but I found some problems.

Sometime ago I've installed LineageOS, Rezurrection Remix and AOSCP 3.8 on my h815 and now I have Nougat Stock Rom v29A.

I tried to check now, after flashing the stock ROM again, if bootloader is locked again but in dev option I can't enable OEM, so I think that I have again the bootloader unlocked.

So I tried to install agin TWRP via adb using "fastboot boot twrp.img" but the terminal says:

downloading 'boot.img'...

OKAY [ 0.397s]

booting...

FAILED (remote: unknown command)

I don't know why it's failed because I always used this command without problems. So in the end I used "fastboot flash recovery recovery.img" and the terminal said SUCCESS, but I'm not sure it's right and I won't try to launch in recovery mode my LG G4 or if I didn't installed successfully the twrp recovery I will going to lose all my datas.

Someone could help me? I would like to install AOSCP 5.1
[G4 Android Development] ThePiGuy:
Fastboot boot is no longer a command in v29a. That's why it isn't working. As long as it flashed correctly, and you are sure the file isn't corrupted at all, then immediately after you have flashed twrp (if you boot into your OS, it will wipe TWRP and you will need to start again), perform fastboot reboot, and then use the key combo to boot into recovery. Then ensure system is patched and you are good to go
[G4 Android Development] kessaras:
and you just discovered why we have a battery drain.

i moved init scripts to bin and one of them , does not execute. i will fix it in the morning.

Nice one ! You should have checked it sooner. Me i never rooted to see adiutor.

EDIT:

Look at the pic.

in the init.qcom.rc i forgot to move the boot script to bin.

the script IS in /system/bin but the service that start it is looking for it in /system/etc in the old dir.

Weldone ! You fixed our battery drain.
[G4 Android Development] vellanifederico:
I have to check if TWRP isn't corrupted?

So when phone is in fastboot mode I have to do "fastboot flash recovery recovery.img" and after "fastboot reboot" and in the end power off phone and launch recovery using power and volume buttons? I don't understand in which case my OS will wipe TWRP.

Thank you very much
[G4 Android Development] ThePiGuy:
I assume you are talking about the LG reset phone screens. They can't be removed, and you need to press yes twice to procede to TWRP. Assuming everything has gone to plan, no data will be wiped, but make sure you have a backup because if, for some reason, TWRP has been overwritten (e.g. because you rebooted your phone after flashing TWRP) then it really will reset your phone

Edit: assuming your TWRP is the latest beta from SteadfasterX, then you can use the md5 file from his site to check that your TWRP image was downloaded correctly
[G4 Android Development] Minto107:
Glad I could help ;) if we talk about kernel related stuff, could you check core control as well? Or explain how it works? It disables big cores to reduce overheating, but in my case it doesn't turn big cores back again when phone is cool. Msm_thermal seems to work fine on the other hand, maybe it core control also needs some love in next builds? ;)

Sent from Galaxy Tab A10 with 7300 battery ;)))
[G4 Android Development] raptorddd:
[MENTION=5461026]kessaras[/MENTION] is the N aocp and R.R also updated? i see N for h818 feb8 date and feb 01 for h811.:)
[G4 Android Development] kessaras:
yes. i will have to root and check. But you do one more check after todays' build. i will fix that script to execute.

yes. aoscp N manually from me when i have time to and RR just syncs to the official so it gets updated. But i wont do RR O yet because i still have the bl audio bug.
[G4 Android Development] Minto107:
Sure thing ;) just mention me or quote my post so I'll know when it's ready ;)
[G4 Android Development] Termehansen:
Maybe do a 'grep -rnw -e "/system/etc/"' in the source folder to see if there are more left overs...
[G4 Android Development] stratonz:
Hi, just a question. With latest 15/02 build I've noticed that when I long press an icon app the three choices uninstall, information and modify don't appear... Has someone the same problem or is just the configuration on my G4?

Thanks in advance.

Inviato dal mio LG-H815 utilizzando Tapatalk
[G4 Android Development] vellanifederico:
I checked the TWRP version, it's the last and the md5 confirm that's not corrupted.

One last thing: you said that I don't have to reboot OS because TWRP will be overwritten again, so after I've done "fastboot flash recovery recovery.img" and so "fastboot reboot" I have to use immediately the key combo to boot into recovery or only after power off use the combination key to boot into recovery?
[G4 Android Development] troullis2004:
[MENTION=5461026]kessaras[/MENTION] I just tested 16.2 version and it boots with conservative and blueactive governors. Stable is that ril didn't start at boot so no pin screen came up but I manually started it with ril app. I also enabled the workqueue for waken cpus to reduce battery consumption.
[G4 Android Development] Monkeypox95:
[MENTION=5461026]kessaras[/MENTION], is it possible to add on the first page (or elsewhere) a status for the two known bugs that remains : BT Calls and Wifi tethering ?

Indeed, it is not easy to follow when we left the topic a while.
[G4 Android Development] kessaras:
But it's not like it's gonna change any time soon. Instead of adding that , why not add the fact that I fixed it when it's fixed ?

15/01 in change log it's there. And since it's not announced fixed...
[G4 Android Development] Frazzy:
The Bluetooth calling thing keeps me busy at night...

It is distorting in a way that seems like the input volume is to high. You say you are using a open source Hal. Is it possible to look at the source for that Hal?

If it isn't possible to alter the Hal, is it possible to overwrite settings that are set in the Hal like a volume?

I am trying to understand the way Android works with things like this.

Thanks again for the ROM. It gets better with every update!
[G4 Android Development] ojcu:
Due to ILAPO I need to modify the boot image. Do what would be the procedure then step by step? First TWRP, disable big cores, then Magisk and then AOSCP followed by disabling the cores? Does Magisk need disabling the cores at all? Sorry if it's a noob question but I'm new to Magisk and ILAPO.
[G4 Android Development] MatteoB92:
Do you still have the bl audio bug into O AOSCP, also? Or are you been able to fix it?

Inviato dal mio LG-H815 utilizzando Tapatalk
[G4 Android Development] burish:
It's still there. kessaras will tell us when and how he fixed it.
[G4 Android Development] ThePiGuy:
On device boot, use the recovery key combo. An easy way to do it is to enter fastboot reboot into your terminal, and then hold volume down and power before pressing enter on the command in the terminal. This ensures the keys are pressed on boot, and from there you can use the combination (power briefly released and then pressed when LG logo appears), and then the two yes's to get into twrp
[G4 Android Development] vellanifederico:
It' really urgent! Now I'm in TWRP but the when I choose zip to sdcard (aoscp 5.2) the console said:

Error: this package is for device g4, p1, h815, your device is .

My device is h815 with nougat stock v29a. Now I don't have any system on it. Help me urgently please
[G4 Android Development] ThePiGuy:
I'm assuming you made a backup first (this really is a must before modifying your phone in any way, as it allows you to recover from issues such as this quickly and easily).

In terms of the error, this is much better off in the TWRP thread, as [MENTION=5545101]steadfasterX[/MENTION] (the developer) knows much more about this than me
[G4 Android Development] kessaras:
How many devs do you count in g4 community ?

2 ?

And I'm one of them ?

I'm not answering anything related to twrp. You all go post your questions in twrp thread. I'm already too busy with other things.

(And don't say that it would be faster to just answer , because if I do , more people will pop up asking unrelated stuff)

We have a thread for twrp and of course a Dev too. He is 100% capable to solve any problem and answer any question as well.
[G4 Android Development] Wallandroid:
After dirty flash rom, do we still need to dirty flash gapps as well? Thanks for an amazing job kessaras!
[G4 Android Development] kessaras:
I believe it's written there for a reason . (Only for unofficial. Official OTA is ok)
[G4 Android Development] ThePiGuy:
[MENTION=5461026]kessaras[/MENTION]

I have just noticed that the AOSCP website now has another build for the H815 (version 5.2, date 2018-02-15). Does this build contain the latest fixes that you have implemented, such as the battery charging etc, or do we need to stay unofficial for now?
[G4 Android Development] SeewolfPK:
[MENTION=5461026]kessaras[/MENTION]: *ThumpsUp* - 20180216 runs now 2 hours on my device and need only 4% from the battery.
[G4 Android Development] MUSTANG0012:
So i saw this new module in magisk manager. [MENTION=5461026]kessaras[/MENTION] do you think it could help regarding the bluetooth calling bug. I have no carkit to test it so ill just mention it here for someone to test. Hope it helps
[G4 Android Development] kessaras:
No. Fixed it just now.

I don't know. The libs we have them , I think I added them when I made O. If not I can add them for a test.
[G4 Android Development] tambukey:
Looking up more info on apt-X, to me it looks like that won't fix it. For apt-x to work the devices on both ends needs to support it. So if a car doesn't support it, the Bluetooth transmission will default back to SBC. It may help, it may not. I think if anything it possibly could be a fix for some people, but definitely not a complete fix. If i wasn't at work I would go and try it right now, but if no one tests it throughout the day I will check this afternoon and report back.
[G4 Android Development] ntnlzr:
could you share the log here i want looking in too
[G4 Android Development] Frazzy:
What kind of log do you want me to run?

Just a normal logcat? Or do you want me to add some options?
[G4 Android Development] ThePiGuy:
I am trying to build my own unofficial version of AOSCP from source (it's as much for the satisfaction of building it as anything else -I haven't done it very many times yet), and unfortunately about halfway, I encountered a Ninja build error. I have been unable to find a log that I can attach, but the build fails with ninja exit status 1. Above that, it says "subcommand failed"

I did notice, a few lines above it says "neverallow on line 503 of system/sepolicy/public/domain.te"

Then it says "1 never allow failures occured

Error while expanding policy"

From this point I get a whole load of warnings before it ends.

Have I set up my build environment wrong?
[G4 Android Development] kessaras:
Which never allow rule ?

Aoscp doesn't have any , I fixed them.
[G4 Android Development] vellanifederico:
[URGENT] h815 without OS

I'm in TWRP recovery on my LG G4 H815, I've clean all datas (dalvik, cache, data, system, internal storage) and after I tried to install AOSCP 5.2 but console said "the package is for g4, p1, h815 and you are in a .", type error: 7.

How can I solve this problem? Now my phone hasn't got any OS, I just have TWRP recovery and in adb shell I type "su" the terminal said "not found".

Please help me urgently. I think that I don't have any build.prop
[G4 Android Development] ThePiGuy:
I'm starting to wonder if I accidently downloaded the wrong device files so I will start again see if I get the same errors (I also tried it as root which messed up file permissions)

---------- Post added at 02:59 PM ---------- Previous post was at 02:52 PM ----------

Type error 7 for this ROM generally means you aren't running the latest TWRP beta from steadfasterX. Go to the TWRP thread and download the latest TWRP beta (steadfasterX manages both the official and the unofficial). Try again afterwards

By the way, if you don't have a backup, I would seriously recommend making one on stock so you can easily revert to it if you have any issues
[G4 Android Development] vellanifederico:
I use the lastes, 3.1.1, the AOSCP's script doesn't recognize my device id