yashsingh1/xdaforums huggingface dataset:
[G4 Android Development] lapist:
I understand what you mean. But I mean something a bit different - when I scroll the text heavily (e.g. in Kernel Adiutor), load is put to big cores (load is 50-80% on them) and they increase in frequency towards 1.6 GHz (even when I disable the input boost on them), while 4 little cores have load around 0% and they stay on input boosted freq. With older kernels it was opposite - heavy scrolling loaded little cores (much over the input boost freq), while big cores remained mainly unused. So I mean that most of the load seems to prioritize big cores now rather than little ones, at least that is what I see on my phone.
[G4 Android Development] kessaras:
Buh , I don't know I'm not tweaking and I never noticed those things. I'm only offering all possible , only the best , tweaks and I just set some default options according to my knowledge and taste.

It's user side to tune anything the way you like.

So....
[G4 Android Development] raptorddd:
go to core 5 input boost and disable it its at 480mhz. and first core keep going upwards till you feel its goos for you.
[G4 Android Development] lapist:
I see...where can I define whether Big or Little cores are prioritized for running tasks?

EDIT: I flashed again version 1.7 and I can confirm that the load is distributed differently there - just scrolling CPU section in Kernel Adiutor up and down, while watching CPU load graphs, shows that.

Version 1.7 puts load to little cores, while big cores stay at 0% CPU usage. Version 1.8 puts load to big cores and little cores remain almost unused. It is not related to input boost for core 5. I don't know what is causing that and 1.8 is significantly smoother than 1.7 due to this fact, but also battery gets exhausted significantly faster...

kessaras: BTW any chances to enable hotplug in the kernel to allow more power saving?
[G4 Android Development] raptorddd:
try interactive governor.
[G4 Android Development] kessaras:
you can confirm nothing.

before testing crap you should ask. this way you dont lose your time for nothing.

in my coding to reduce phone workload, when cpu has 0 load, monitoring stops.

this means that if the load goes to 0 for the big or small (but small always has a load), monitoring stops.

so if you were running something and suddenly load goes off from big cluster, monitoring stops and you just see a number without it being real. thats all.

no load = no monitoring cpu. Thats all. happy testing

**

An app can't tell the kernel how to work. only ME i can do that.

when load is 0 monitor freeze. it doesn't update the freq table so what you see is just a number left there.

imagine a table with frequencies.

time | hz

10.05| 1000

10.06| 1500

10.07| 1800

suddenly monitor stops , load is 0.

it wont write : 10.08| 384 (minimum speed)

thats useless..... and if load remains 0 it will keep working to write 384 ? 384 384 384 384 ? ....... useless....

in programming we do things the way we believe its better. for me its better to stop.

***

you can achieve this with 3 ways.

1) <slow>

an if to check if freq is >0 { blah blah blah }.

2) <somewhat slow>

while freq > 0 do {blah blah blah}.

3) <fast>

somewhere in the middle an if statement with a

break;

or a

continue;

(break = if the last check comes true , exit loop and go back)

(continue = if last statement true, exit loop and continue program).

So 0 load, no monitoring cpu
[G4 Android Development] lapist:
OK, I see...I can do programming too, so I know what are you talking about :) I just wanted to report that 1.8 seems to use rather big cores for processing unlike version 1.7, and it is not affected by input boost on big cores or GPU governor change and I didn't see any other change documented that would explain it, thus I was wondering whether it is wanted or unwanted behavior. I got back to 1.7 and tweaked governor/boost settings for better performance and still it seems to take less battery than 1.8 :) But maybe it is just my imagination and CPU usage shows some wrong values...

What do you think about implementing hotplug?
[G4 Android Development] kessaras:
i gave it good thought when i was still a user here and experimented a lot too before.

when we used to have AndroidGX and Slim kernels.

All those features are great but by bloating a lot the kernel we lose performance so we have to choose wisely what we add and only add the most important or best modules and features.

About hotplug.

Our big cpu anyway works only when it has a load. Thats how 808 snapd. works. So we have 4 active cores to work.

lets say we add a hotplug now which will turn off the cores when there is no load. BUT when is there actually a moment that those 4 cores dont have a load ?

Only when the phone is sleeping (deep sleep).

And instead of 384 lowest frequency we have 0.

That will benefit the overall battery drain by adding 1 more hour maximum during the time we dont use the phone and will lower the performance by adding work in kernel to check and send and receive the load , in order to turn off the cores (thing that will rarely happen with screen on). Turning on/off cpu reduces performance a lot !

It doesnt worth it.

If on the other hand it was 6 cores active then yes we would love to have the big ones turning off (by force if load is below 50% for example).

It just doesn't worth the outcome. 1 more hour sleep time versus a vast amount of performance
[G4 Android Development] lapist:
Thank you for the explanation. There are some cases where hot plug could be useful while the screen is on, for example when I am reading some long article in a browser, I read one page for maybe 20 seconds, then I scroll down, read for another 20 seconds, scroll etc. and the same can be for reading ebooks (if somebody does it still on the phone instead of Kindle). In that time when I read the text and CPU is doing nothing, some cores may be disabled. But if you say that turning on and off cores takes more power than it saves, I believe you :)
[G4 Android Development] raptorddd:
ive tried hotp[lug i dont see any improvement on battery. actually interactive gave me a more linear discharge with all cores active then using hotplug.
[G4 Android Development] Bullnados:
Pls dont let us die stupid and let us verify your imagination
[G4 Android Development] §SOLO§:
Hi, I'm using 1.8 version and I'm having very hi temperature like 60 65 Celsius while browsing and streaming music via Bluetooth... Is it ok for the phone to get this hot ?

PS I'm using data connection not wifi
[G4 Android Development] tulen_kobi:
60 on load? That is cool. My phone iddles at that temperature :D Around 90 on full load, blame LG for poor engineering.
[G4 Android Development] §SOLO§:
holy s**t that's hot :eek: !! thank for the answer :good:
[G4 Android Development] ufocus:
With v1.7(stock) temperatures are lower for me, you could try.

With 1.8(stock) I'm getting the same temperature.
[G4 Android Development] Yuri.11:
After Flash this kernel Snapchat is not work.
[G4 Android Development] Minto107:
Well. I'm getting 41 under my 'heavy' load (spotify[emoji23][emoji23][emoji23])

For me it works...
[G4 Android Development] Yuri.11:
I try Factory reset
[G4 Android Development] Minto107:
Every G4 is different, remember that. Maybe yours is older(version 1.1 or 1.0 which had higher temps) or older(mine is 1.5 years old, battery is almost dead but other than that it's in great condition)
[G4 Android Development] gioxoid:
What kind of improvements in everday life wrt to stock Freedom ROM kernel?
[G4 Android Development] madman_cro:
What governor settings are best for interface smoothness in 4 core version kernel? My big cores are gone so im hoping to smoothen it up . Thx
[G4 Android Development] kessaras:
The default setup is good for 6 cores not 4. Just use kernel adiutor to set it up the way it's best for you.
[G4 Android Development] madman_cro:
Thx. I set it up to ondemand and got touch boost to 1.4 on all cores. Increased boost time to 2000ms too . hope it works out.
[G4 Android Development] Minto107:
It will for sure... But good luck averaging any sensible SOT with that setup
[G4 Android Development] madman_cro:
Yeah. You are probably right. I switched to interactive and 864 boost on all cores. Il post screenshot when i hit 5% . but to be honest im happy to even got it working without big cores.
[G4 Android Development] Minto107:
I forgot you have big cores disabled. But 2secs of boost? I would lower it I don't think you need 2 secs ;)
[G4 Android Development] kessaras:
Updated contributors in the op.

Added [MENTION=3873953]eng.stk[/MENTION].

I honestly forgot the most important.

eng.stk work is playing an important role to this kernel stability since we use his amazing governor as default and his kernel for op3t used to guide me a lot through many customisations. (And still does if i want to check something as an advise for something i may want to do, since he is one of the top developers)
[G4 Android Development] nigxxx:
my cpu temp never went over 50c under load... aka few games, full hd youtube video... on idle around 30c.. with stock kernel
[G4 Android Development] lapist:
I also have problems with bluetooth...I have Mi Band 2 and the phone often looses connection with the band. I have to disable bluetooth and enable it again (sometimes rebooting the phone is needed) and then it works for a few hours until it stops working again. It worked without any issues with my previous phone... I am using v1.7 od titan kernel.
[G4 Android Development] kinuris:
I'm using RR with Titan, and my bip works OK along the day. FYI
[G4 Android Development] lapist:
Lucky you. I am using stock Nougat ROM with Titan and connection with Mi Band 2 breaks within a few hours. Perhaps something is different in RR, or your bluetooth device...
[G4 Android Development] Minto107:
RR isn't the best choice tbh. You should try AOSCP, it's way more compatible
[G4 Android Development] gioxoid:
This project is abandoned?
[G4 Android Development] raptorddd:
no its not.. its just that oreo aoscp takes a lot of time. [MENTION=5461026]kessaras[/MENTION]

anything new that can be added ?
[G4 Android Development] gioxoid:
So V1.8 could be considered final release for nougat?
[G4 Android Development] kessaras:
No. I updated the fs which propably will fix the encryption too. I don't have the time to build several stuff. At first of the next month I will do an update to everything.

Only stock based development has no further development, because there are no changes from LG so there is nothing to fix or add.

1.8 is last for stock.

N will get updates when I find something that need an update and security patches (only kernel level). Can't maintain whole N alone and at the same time help with O and at the same time fix several crap everyday that break after google updates , maintain the kernel and don't know what more. Lol.

So,

1) i quit N rom only security patches and whatever, kernel will go on.

2) I quit stock based as there is nothing else there to do.
[G4 Android Development] gioxoid:
Very good news. I appreciate a lot :good::fingers-crossed:
[G4 Android Development] lapist:
Any chances on fixing bluetooth issues here?
[G4 Android Development] kinuris:
Hello. I got no issues with speakers, auto audio system and calls, and smartwatch link. The only thing is the battery waste. I got a smartwatch recently and I have BT on whole day, so I don't know if it is normal or not.

Edit: I'm in RR, but I think it is using same kernel.

What is failing for you?

PD: I'm in nogapps, maybe it has something to do with BT behaviour?:confused:
[G4 Android Development] rahulsj92:
Oreo LOS 15.1

I wanted to use a kernel with Kcal support. Shall I flash this kernel on LOS unofficial 15.1 Oreo ROM? Will there be any issue? I couldn't find anything about Oreo support. Thanks in advance! :)
[G4 Android Development] kessaras:
Huh ?

Where is that , did anyone finally did the bringup ?

Where is Los 15.1 for g4?
[G4 Android Development] rahulsj92:
Sorry, wrong thread. :eek:
[G4 Android Development] SmokeTooMuch:
What does this mean? Will I not have any phone signal anymore when flashing this kernel?
[G4 Android Development] eejee:
No it means that the fm radio doesn't work. Phone works fine.
[G4 Android Development] SmokeTooMuch:
Well, after flashing it I actually don't have any wifi or LTE internet access anymore.

I'm using LineageOS 14.1 with the v29a Nougat firmware on a h815.

As soon as I flash back the LOS kernel I have internet access again.
[G4 Android Development] kessaras:
but we dont have any los maintained...............................

all roms besides mine are now outdated..............

Maybe , tulen cobi los is ok, because we have same N tree and blobs and Titan as default kernel. (i dont know if he still uses my stuff to build )

g4 doesn't have any devs any more........ (besides me and steadfasterX i mean)
[G4 Android Development] a tiny ant:
Noticing huge battery drain while charging on stock v29a. I flashed kernel version 1.8 and after that Magisk. While the performance during the day seems fine as soon as I try charging the phone it gets hot and drains the battery faster than it charges it.

Anyone else noticed that?

Edit: it looks like changing the governor and/or disabling cpu boost using kernel adiutor fixed the issue for me.
[G4 Android Development] Lurensu:
I have some missing option about debug in developer settings:

There's no "revoke adb authorization" or "allow adb over wifi" option and I can't get tcp adb to work (the port is already occupied).

Searching around I've seen that a lot of people with this issues said that it's kernel related..
[G4 Android Development] :
sorry, which version should i use for rr-7.1.2 v5.8.5 by kess? nbg, los or normal? thx!
[G4 Android Development] kessaras:
whats nbg ? thats a bank if im not wrong.

none for rr. these here are not up to date to now. i have to update them.

Plus that it wont work with official RR because we use different tree.

it will only work at my unofficial which is already using titan
[G4 Android Development] :
i mean no big cores..

however yeah, i refer to your rr unofficial, i didn't remember it uses already it, sorry -.-
[G4 Android Development] deezid:
Yh still using v. 1.8 No Big Cores on your AOSCP Nougat. Works flawlessly with a good SOT of about 4 hours (on demand govenor and some other performance tweaks).
[G4 Android Development] ItzShadowz:
What did you do to install? I'm trying to run LOS nougat but it doesn't get past boot animation
[G4 Android Development] a tiny ant:
[MENTION=5461026]kessaras[/MENTION]

I'm also having really bad Bluetooth performance. Auto connecting seems to only randomly work, as if the Bluetooth process is being hibernated.

Other than that sometimes the phone fails to notice that a Bluetooth device disconnected and sometimes it will say it's connected but actually isn't.

Pretty much the only thing I want from this kernel is being able to turn both big cores off at will using Kernel Adiutor. Is there a way to allow this with the stock kernel as well? I don't really care too much for the extra tweaks Titan offers.
[G4 Android Development] VersionTV:
Hey [MENTION=5461026]kessaras[/MENTION] ,

Sorry for the newbie question. I am using H815 (601k). I have not received any bootloop or motherboard issue for 2 years. Should i flash your kernel for better performance? :confused:
[G4 Android Development] kessaras:
what r you talking about ? My O is fine. Only bluetooth audio has a problem and its not related to bluetooth , but to the audio.

don't know. you tell me. should i go to toilet when i want to or not ?
[G4 Android Development] raptorddd:
i also have 601 if its survived that long means it good.. i think titan its better then stock. so yeah you should.
[G4 Android Development] Minto107:
Agreed. Some G4s (especially around 603)got new motherboard that is finally fixed, you had to be lucky and yours already have the new mobo. Same goes for me, even as my phone is 602(second half of the month tho) and also has fixed mobo, that I stress tested many many times and it's not gonna die
[G4 Android Development] Goatville:
G4 models affected by motherboard problems can potentially take 1-2 years to start messing up. Mine was a 510 model, and back then it was initially believed that all models 509 and later were safe batches with fixed motherboards. This was eventually proven to be false. It took mine a while to bootloop, I began using it in January 2016 and it worked fine until May 2017. Mind you, this was under quite heavy use and with a locked bootloader that I couldn't (at the time) install custom roms or kernels on. So I couldn't do as much to address thermal issues.

LG agreed to replace it, and they sent me a 701 model (meaning the motherboard was manufactured January 2017). Which I started using when it was delivered in July 2017. I've taken care to flash this kernel. And under normal daily use, opting for thermal-conscious settings.

It's still plausible that 601 or newer models could bootloop eventually. There have been a few cases of people reporting this happening to them, though it hasn't been nearly as common as the 5xx ones yet. This may just be because they haven't had long enough to cook yet. And it may not occur as easily (or as soon) if you're deliberately using kernels and other settings that are designed to keep the CPU cooler. Probably also many people who had these issues have now moved on to other phones, so we may not have many reports in the future even if the problem hasn't been fixed. Unless someone can prove otherwise, i'm not comfortable assuming 6xx or 7xx models are safe.
[G4 Android Development] Minto107:
I tested on my self, and I can guarantee that mine won't loop. I've stress tested it several times, even for hours and it wouldn't die. It shows other problems like not working SD slot or damaged eMMC memory, but all in all it still works and doesn't give a damn. Just few months left
[G4 Android Development] Goatville:
It takes a long time for the problem to actually manifest. It's supposedly related to the solder used inside the SoC being either low quality or applied in an incorrect manner by the manufacturer.

The way I recall it explained, the chip constantly heating up and cooling off over time (just normal use) causes the solder to expand and contract. With time, this eventually causes the materials to deteriorate to the point where the phone has persistently high temperatures and will fail even on basic tasks.

Even if you manage to boot it again, it will quickly fail again due to permanent thermal issues. Regardless of what you do, even disabling the two A57 cores. Nothing is a permanent fix unless you get the solder fixed.

Just stress testing the device for a few hours probably won't kill it. I put mine through some stress when I first bought it and it was fine at first. Got extremely hot and throttled, but no serious problems. It died a year and a half later during non-intensive tasks.

It seems to be the constant heating up and cooling off that deteriorates the materials and eventually leads to permanent damage and inability to maintain safe temperatures.
[G4 Android Development] kessaras:
its just the bad quality of the material they used to connect the chipsets to the board.

past few years materials changed to be more "environment friendly".

Also LG is used to make mistakes since then with their latest work on pixels xl 2 to be a big failure.

I don't trust them. They always try invent a new panel leading to crap hardware and poor battery life.

So, lately they decided to use a normal LCD for their next brand after they announced that they walk away from the smartphone fight.

Anyway. No good talking about it. Enjoy it for as long as it lives.
[G4 Android Development] owlery_hk:
I came from llama sweet kernel by genesixxbf3.

Loving your titan kernel!

Especially the picture quality.

Thank you for your great work

I have a few features requests:

Is it possible for you to include brick hotplug for the cpu and adreno idler for the gpu?

The battery life is already very good, i just wonder if some more can be squeezed out of the g4.

Thanks!
[G4 Android Development] ThePiGuy:
I just looked at the 'Added' section at the start of the thread and I noticed that it refers to WireGuard VPN. I was just wondering what this integration is - does it always route your data through a VPN (sorry if this is a silly question) or does it just use that when you use a VPN?
[G4 Android Development] --__LoRiS__--:
I have problems with BT and my Ticwatch, I don't receive notifications... I used search function but no solution found :(

Inviato dal mio LG-H815 utilizzando Tapatalk
[G4 Android Development] ThePiGuy:
Has anybody else had issues building the AOSP branch? I had an issue where it kept telling me that 'rc' in the drivers/platform/msm/qpnp-haptic.c has not been defined before usage. I (hopefully) have fixed it in my local environment by adding it to the parameters at the top of the qpnp_hap_td_enable function
[G4 Android Development] MatteoB92:
For me with the Ticwatch E all is ok, try to pair again the smartwatch

Inviato dal mio LG-H815 utilizzando Tapatalk
[G4 Android Development] Minto107:
Also it's more ROM related than kernel. Come on if you flash custom kernel you should know that
[G4 Android Development] --__LoRiS__--:
It worked before flashing the kernel on the same ROM...

Inviato dal mio LG-H815 utilizzando Tapatalk
[G4 Android Development] Minto107:
I can suggest reapplying notification access. This happens to me a lot
[G4 Android Development] ThePiGuy:
[MENTION=5461026]kessaras[/MENTION] I would just like to clarify the SELinux Enforcing/Permissive differences (I thought I should probably move here as this is more appropriate than the LOS thread). As the SE Policies are in the device tree, titan kernel should work in enforcing mode on LOS as the device trees worked in enforcing mode with the LOS kernel. Is this correct? Also, say it didn't work, what symptoms would I experience? (this is my daily driver phone so I need it to be stable)

Edit: btw, this is LOS N
[G4 Android Development] kessaras:
yes better here.

enforcing it means that when a service or an app (even stock preinstalled apps) need to access a file , a folder, or a socket, or create a socket, they can NOT do it unless you say so in the policies and allow it.

permissive it means that when a service or an app needs to perform an action such as i said above, it will do it, BUT it will just log what happened , if it was allowed or not.

so you can now imagine what happens.

e.g. to make a phone call it creates a socket, to save a file you need a permission, to edit a file you need a permission, to change from 3g to 4g it also needs to access a socket.

There is a policy for every action. So if we do not add all needed policies we cannot safely enforce.
[G4 Android Development] ThePiGuy:
Ok that makes sense. But seeing as LOS appears to have all the policies, enforcing on titan should be ok then (unless titan has additional se requirements that are not included in the default LOS sepolicies). Is that right? (Sorry, I'm being a bit slow on understanding this)
[G4 Android Development] kessaras:
kernel doesn't have policies.

and los hasn't being tested much. you see, when genesix built it, one or two people flashed it and with the first problem they saw, they moved away.

we r not magicians. we need people to use a rom for a long time and send logs and be patient enough until we release another build with fixes.

So.... i don't know if everything works. And instead of thinking about it you can just see it with your eyes and if something doesn't work, dirty build permissive and log all denials and share the log so that i help you and show you how to add the missing policies.

[MENTION=8699949]ThePiGuy[/MENTION], find me in AOSCP community in telegram. Link for the community you will find in the AOSCP thread OP.

send logs there in the future. It will help you a lot, there r also many people there like you trying to learn and build for their phone

Oh, but keep it a secret about building los.... share only with me when its about other roms.

AOSCP community is strictly for AOSCP only use :D