[ROM][7.1.2][i9305]Unofficial LineageOS 14.1 with modifications

[nTxw]

Battery drain with active SIM card

Hello, i did a clean install and everything seems to work (Bluetooth not tested).

But I expericence strong battery drain since CM14.0 / CM14.1 also under LineageOS, but only when SIM card is "active". In flight mode with WiFi enabled, the battery last much longer. Any suggestions what could be the cause? "Ruhezustand" (hibernation) seems to consume a lot of energy.

PS: I flashed stock kitkat Modem since CM13 (i think) or CM14, not sure since when. I9305XXUFOA1
https://xdaforums.com/galaxy-s3/development-i9305/modemi9305-n-tkk-4-4-x-flashable-modems-t3296456


Thank you!

 

[FloBaoti]

I have huge battery drain for a few days with this rom.
Anyone see something strange ?

 

[dawidd6]

I have huge battery drain for a few days with this rom.
Anyone see something strange ?

Well, your cpu runs at max frequency for most of the time. This is strange for me.

 

[FloBaoti]

Yes that's what I saw. But no wakelock, no frozen app... No kernel tuning app neither.
The only thing I changed is radio (modem binary) few days ago. I switched back to previous one and I will see if that was the cause.
But if radio was the problem, shouldn't have some kernel wakelock or rild daemon locks... ?

 

[nTxw]

Hi dawidd6, Hi FloBaoti, a few days ago i flashed latest 4.4.4 Stock KitKat Modem I9305XXUFQG1 as suggested in the rgib thread. Thanks to you dawidd6 for the hint!
https://xdaforums.com/showpost.php?p=74494153&postcount=542
https://samsunggalaxyrom.com/firmware/update-galaxy-s-3-lte-gt-i9305-i9305xxufqg1-android-4-4-4

First impression was it is better, but i had no time for testing so far. I use my i9305 only as second device. Most of the time in flight mode with Wi-Fi switched on, because of battery drain with "active" SIM since CM14/LineageOS.

I am not familiar with RIL topic, but I have the impression there must be some dependency to modem regarding battery drain. Because battery life is much better in flight mode with Wi-Fi on. I will charge the battery and see battery life within the next days. I also will try to install BetterBatteryStats app for monitoring.

 

[p.a.n]

Hi everyone,
I found a new board for my phone for something like 25USD and I couldn`t resist So here is my new build:

lineage-14.1-20171128_075344-UNOFFICIAL-i9305-ci.zip

A new feature is call recording. The other side is recorded directly from GSM, not over microphone, like some apps do. It works in the built-in dailer, but only after the call is connected - click on the the 3 dots and Record Call (see the screenshot). One more little problem is with the permissions for writing to the external card - after granting this permission, the dialer app has to be restarted (the simplest way is to restart the whole system). So it won`t work for the first time. Alternatively you can grant this permission through settings before dailer starts. I also tried Call Recorder app from F-Droid, which works completly automaticaly and out of the box (or at least the version I tested does).

Please, be careful with this, call recording may be illegal in your country.

All my changes and list of commits used for this build are in the zip file as described in OP.

 

[rocon]

Hey, p.a.n. I'd like to move to your ROM for the F2FS support, and since official lineage seems dead. Mostly because I read an article which basically dissed the FUSE implementation and it's double caching behaviour. But I'd really can't abandon zram which means I'd need to flash the boeffla kernel for it. Correct me if I'm wrong but I think that'd would negate the point of using your ROM as it'd overwrite your kernel settings including F2FS support, right?

If so, is it possible for you to create a build with zram added to the lineageos_i9305_defconfig?
Should be around line 1186, add the lines with the pluses next to it.

# CONFIG_PARPORT is not set
CONFIG_BLK_DEV=y
+CONFIG_ZRAM=y
+CONFIG_ZRAM_LZ4_COMPRESS=y
# CONFIG_ZRAM_DEBUG is not set
# CONFIG_BLK_DEV_COW_COMMON is not set

And remove this line around #2816

#CONFIG_ZRAM is not set

I believe zram won't init on boot by default, which means users of your ROM shouldn't take a hit, and I'd be able to verify if it works by bringing it up manually with my own init scripts. I tend to favor zram greatly because I load all my apps into RAM and prevent them from leaving with an xposed module. Keeps things snappy and saves on I/O reads/writes which I think the s3 lacks specwise.

 

[Tremolo4]

I'm having a battery drain as well, CPU is on maximum frequency 99% of the time my screen is on.
BetterBatteryStats with root permission shows the process "qmiproxy" is responsible.

I used a self-built lineage rom a few days ago to encrypt my phone, since encryption was fixed in upstream. Repo. These are @p.a.n's patches as compiled by @mtr_
I encrypted my phone immediately after I got it working. Then I noticed the battery drain / CPU usage. Maybe encryption is related?
Although the problem does not occur when switching back to @mtr_ 's ROM from here. But my phone is still encrypted (and everything works).

So, to summarize: The battery drain / qmiproxy problem happens with both my rom and @p.a.n's new rom, but not @mtr_ 's rom. So the culprit SHOULD me somewhere in the upstream changes of the last two months? Well maybe one of you has an idea

I found this in p.a.n's patches, maybe related?

#For EncryptionMode - remove disabled, Modify class main
service qmiproxy /system/bin/qmiproxy
    seclabel u:r:qmiproxy:s0
    class main
    user radio
    group radio gps

Edit: Ah I just noticed, maybe SELinux permissive in @mtr_'s ROM prevents the problem.

Edit 2:: Yes, setting SELinux permissive "fixes" the problem, using my rom based on @mtr_'s version of @p.a.n's patches.

 

[mtr_]

Correct me if I'm wrong but I think that'd would negate the point of using your ROM as it'd overwrite your kernel settings including F2FS support, right?

I'll shorten your wait time for response until @p.a.n can answer you.
@p.a.n's kernel has only 4 features changed: F2FS, SDcardFS, increased log sizes and LZMA compression for initial ramdisk(useful to fit new TWRP). Besides these 4, the ROM will work the same.

I'm having a battery drain as well, CPU is on maximum frequency 99% of the time my screen is on.
BetterBatteryStats with root permission shows the process "qmiproxy" is responsible.

I used a self-built lineage rom a few days ago to encrypt my phone, since encryption was fixed in upstream. Repo. These are @p.a.n's patches as compiled by @mtr_
I encrypted my phone immediately after I got it working. Then I noticed the battery drain / CPU usage. Maybe encryption is related?
Although the problem does not occur when switching back to @mtr_ 's ROM from here. But my phone is still encrypted (and everything works).

So, to summarize: The battery drain / qmiproxy problem happens with both my rom and @p.a.n's new rom, but not @mtr_ 's rom. So the culprit SHOULD me somewhere in the upstream changes of the last two months? Well maybe one of you has an idea

Edit: Ah I just noticed, maybe SELinux permissive in @mtr_'s ROM prevents the problem.

Edit 2:: Yes, setting SELinux permissive "fixes" the problem, using my rom based on @mtr_'s version of @p.a.n's patches.

Be carefull, avoid enabling SELinux on builds based on files from my repository. I never had the time to finish getting correct permissions for all things, it won't work correctly with enforced setting (for example calls notification may not display). The first time I ran @p.a.n 's rom I noticed that mDNie doesn't have correct SELinux permissions. That meant that there could be more unnoticed permissions of less used features that needed fixing.

 

[rocon]

I'll shorten your wait time for response until @p.a.n can answer you.
@p.a.n's kernel has only 4 features changed: F2FS, SDcardFS, increased log sizes and LZMA compression for initial ramdisk(useful to fit new TWRP). Besides these 4, the ROM will work the same..

I see, it's as I feared. I guess I'll have a go at building a version with those two features sometime in the future then.

Thanks for the clarification.

 

[Tremolo4]

Be carefull, avoid enabling SELinux on builds based on files from my repository. I never had the time to finish getting correct permissions for all things, it won't work correctly with enforced setting (for example calls notification may not display). The first time I ran @p.a.n 's rom I noticed that mDNie doesn't have correct SELinux permissions. That meant that there could be more unnoticed permissions of less used features that needed fixing.

Yes, now that you mention it, I've had that problem of not getting calls before setting SELinux to permissive
Running very fine these last weeks. No crashes or modem not working problems like I've had with the "official" LineageOS.
Thanks again @p.a.n and @mtr_ and everyone else involved!

 

[YogiCK]

Any plans for next releases?

 

[parkkis]

Hi guys, thanks for all the effort! - Do you like to use

lineage-14.1-20170917-UNOFFICIAL-i9305.zip (mtr_) or
lineage-14.1-20171006-UNOFFICIAL-i9305.zip (mtr_) or
lineage-14.1-20171128_075344-UNOFFICIAL-i9305-ci.zip (p.a.n)

or some other?

 

[mtr_]

Any plans for next releases?

If someone is interested in my builds, he can check my AFH profile (https://androidfilehost.com/?w=files&flid=216607&sort_by=date&sort_dir=DESC). I'll be uploading new ones sporadically, but won't be notifying here about them.

 

[parkkis]

If someone is interested in my builds, he can check my AFH profile ... I'll be uploading new ones sporadically, but won't be notifying here about them.

Thank you - I try that. Had stock 4.4.4 Kitkat and flashed lineage-14.1-20171128_075344-UNOFFICIAL-i9305-ci.zip which has started rebooting on its own...stays on showing lineage logo. Have to remove battery several times a day.

Is there version history file telling about the changes/improvements you're making?

 

[mtr_]

Thank you - I try that. Had stock 4.4.4 Kitkat and flashed lineage-14.1-20171128_075344-UNOFFICIAL-i9305-ci.zip which has started rebooting on its own...stays on showing lineage logo. Have to remove battery several times a day.

Is there version history file telling about the changes/improvements you're making?

There aren't many changes other than the ones that come from updated LineageOS. Like I posted before https://xdaforums.com/showpost.php?p=73828872&postcount=26 . If there will be any non LineageOS based changes, they'll be in https://github.com/m-tr/android_device_samsung_i9305 or https://github.com/m-tr/android_kernel_samsung_smdk4412 . The point of my builds is to keep the old stablest RIL synced with the most up to date LineageOS 14.1. I think the most informative place to look for LineageOS changes is https://review.lineageos.org/#/q/status:merged+branch:cm-14.1 .

 

[Massedil]

The point of my builds is to keep the old stablest RIL synced with the most up to date LineageOS 14.1.

Do you think that your ROM will solve this RIL problem ?

Do you have a migration build ?

 

[mtr_]

Do you think that your ROM will solve this RIL problem ?

Do you have a migration build ?

It is worth giving a try.
For most roms you'll find only full rom builds. As this rom is very similar to the official one, you could try doing a backup and directly flashing it over the official one.

 

[Oswald Boelcke]

Do you think that your ROM will solve this RIL problem ?

Do you have a migration build ?

I'm using RR-N-v5.8.5-final on three i9305's without any issues at all i.e. also no RIL issue.