yashsingh1/xdaforums huggingface dataset:
[Galaxy S Advance I9070 Android Development] ChronoMonochrome:
Sorry, I thought I've reverted this change. Can you confirm that setting old LCDCLK freq fixes issue? As a temporary solution you can use init.d script to set the appropriate LCDCLK freq index.

Can confirm now. I have a guess for that, for now the solution as follows:

remove /ramdisk/modules/autoload/sioplus-iosched.ko, reboot. I have to test this a bit more time to be sure 100%, but so far I couldn't reproduce an issue after removing this module (no other CPUfreq governor or I/O scheduler must be loaded as well).

It's not a bug, but rather intended behavior - due to PowerHAL changes implemented, CPUfreq can only be changed via script (see /ramdisk/perf.sh). I've previously asked if anyone would prefer to adjust CPUfreq usual way, In this case I can just remove the corresponding lines from the PowerHal script. This will make PowerHAL settings a bit more useless, but will gave easier control over CPUfreq.

The script actually works, though you're right, it works buggy and everytime shows the default profile (you can set, e.g. Powersave profile and check min/max CPU freq, to check if it actually works).

Done!
[Galaxy S Advance I9070 Android Development] isaak:
Yes, I can confirm that setting old LCDCLK freq fixed the flicker issue for my screen. I think it would be better to set it as default in the next release.

I tried your steps, unfortunately they didn't work for me.

Personally I would prefer more control over CPUfreq. Could you list the main advantages to limit CPUfreq changes only via script? Is it a sort of auto-optimization? This point is not clear to me. If you think that any change to this mechanism would affect negatively the battery life, then don't change anything.

I tried Powersave and Performance profiles, in both cases the maximum freq varies between 400 MHz and 1000 MHz, rarely reaching 800 MHz. Minimum freq is always 200 MHz and it doesn't change visually like the maximum freq. Balanced profile is always shown visually after a reboot.
[Galaxy S Advance I9070 Android Development] ChronoMonochrome:
Because of some CPUfreq scaling tunables were changed (in the case of Dynamic governor), it makes sense to implement a PowerHAL profiles, which would limit / restore the max CPUfreq. But I think I've found a solution - I will make it possible to change CPUfreq for a Balanced profile.

Ok, I found some logical errors in the script, should be fixed in upcoming release.
[Galaxy S Advance I9070 Android Development] Pdevo:
Hi Chrono,

I got some time to flash your latest build on 4.1.2 stock.

I still have issues with deepsleep and phone calls, but I guess these would just be possible to fix the day you would have some spare time to have a go on the stock jellybeans :)

I noticed that with this release bootanimation got an override, the phone boot to systen just with the initial s advance splash screen, also lighting up touch buttons backlights, but nothing wrong at all with this!

Powersave mode seems to work fine.

Had to revert back to mk kernel 6.0.1 (which I found very stable and with a really good memory management compared to cocore on stock) due to issue with calls, thinking to try android 6 soon
[Galaxy S Advance I9070 Android Development] ChronoMonochrome:
Hi,

I've recently was returning to 4.1.2 stock ROM to address these issues. I couldn't reproduce neither deepsleep nor calls issue (only outgoing calls tested, have not had a chance to test incoming calls yet). I have installed Kernel Auditor and deep sleep was working according to an app. I would still advice to install app like Wakelock detector because the issue is coming from ROM / apps part, not kernel.

I can confirm bootanimation issue on stock, but unfortunately I don't have a clue about this, since this issue only happens on stock ROM.
[Galaxy S Advance I9070 Android Development] ChronoMonochrome:
New build r5.8.1 is up!

Changelog

R5.8.1

PowerHAL fixes for 4.4.4

Experimental fix for CPU governor issue on 4.4.4

LCDCLK: revert to TeamCanjica kernel implementation
[Galaxy S Advance I9070 Android Development] Pdevo:
Ok chrono, thank you so much for observation, I flashed kernel atop mk, without changing any app or setting, before deepsleep was just working fine. I use kernel adiutor to get the stats too, so this seems strange, I guess I have then to watch out wakelocks, the only possible source for this issue.

I'll try also a reset and test again the phone calls (incoming and outcoming), report you soon!

The only relevant change to stock rom is the removal of the modem log interface binary
[Galaxy S Advance I9070 Android Development] ChronoMonochrome:
New build r5.8.2 is up!

Changelog

R5.8.2

In-kernel vibrator fix for Android 6.0+ *

* Because vibrator was disabled in a ROM level on ROMs like UltimateROM 6.0, 7.1 and LineageOS 15.1, it will be needed to re-enable it back before it will start to work. I will update the corresponding threads soon.
[Galaxy S Advance I9070 Android Development] isaak:
This was done only partially in 5.8.1-2. Please look at the screenshot (I did it after reboot).

Current LCDCLK freq is set to the default 60 Hz at the system boot (and it's okay), but it doesn't match the description (that says 60+ Hz).

I think you may need to update some description or value for a consistent result.

Nothing to complain about these fixes. I'm looking forward to the BLN support, if it's ok for you. ;)
[Galaxy S Advance I9070 Android Development] Pdevo:
So far I flashed again your kernel and did a factory reset on my phone.

Deepsleep issue is gone, and this is very good, I will then investigate on what was causing this problem.

Phone calls issue still present, I tryed to restore the modem_log_relay binary and revert csc and build prop changes I did, with no luck. I am using a personally customized UBLPL stock rom for some years now, changed every possible kernel but never faced this issue and can't really understand what's causing that. Surely trying a completely stock rom issue would fly away, but missing what's wrong.

If you have some spare time I can upload the rom and maybe have a look, but only if you'd like ;)
[Galaxy S Advance I9070 Android Development] ChronoMonochrome:
My bad, some older LCDCLK code still persist on this build. This could be causing conflicts, I will look soon into this.

UPD. No big conflicts should be here, older code won't apply changes to LCDCLK freq unless the sysfs interface (/sys/kernel/mcde/lcdclk) is touched. The correct interface (which is from TeamCanjica kernel) is /sys/kernel/s6e63m0/panel/lcd_clk . I will remove one of these interfaces as soon as I can.

I've had an opportunity to test BLN, but that was only a short test, and unfortunately, still no result, even with same code and configs enabled like on codina. But I guess I will look more deeply into this soon.

Great to know that the deepsleep issue has gone now. As for incoming / outgoing calls issue - I can take a look, but no promises though.
[Galaxy S Advance I9070 Android Development] ChronoMonochrome:
BLN

I have some news about BLN. It seems that it should be possible to fix BLN on this device - I've tested BLN again and it appears that at least blinking with the rear camera flash works.

If someone wants to test this there is how to enable BLN:

# blink mode - 2 means LEDs + rear cam flash
# but on janice, only rear cam flash works for now
echo 2 > /sys/devices/virtual/misc/backlightnotification/blink_mode
echo on > /sys/kernel/bln/bln_wakelock
echo 1 > /sys/devices/virtual/misc/backlightnotification/enabled

I've only guess about that I have so far - codina and janice apparently having different LEDs (KTD259 on codina vs KTD267 on janice).

The difference in these drivers could cause that janice LEDs aren't recognized as a BLN device. Since the rear cam driver is the same on codina and janice, BLN works with it on both devices.

I still need to investigate the BLN mechanism in order to fix blinking with the phone LEDs.
[Galaxy S Advance I9070 Android Development] redaboy:
MOD EDIT: Please don't quote the entire OP

Can i flash it with Odin
[Galaxy S Advance I9070 Android Development] ChronoMonochrome:
New build r5.9 is UP!

Hi to everyone and sorry for having to wait for a new release that long!

I was busy with some private stuff in a real life I was need to deal with. Still not having much time to work on the development due to exams (but some good news are here too).

Changelog

R5.9

Bring up all the latest CK code from Codina kernel

Fix a severe performance issue on r5.8.2 build

BLN is finally FIXED! *

* Apparently, issues with BLN were related to Janice touchkey driver that was putting the device to sleep (when the display is off) regardless of a BLN wakelock usage. Reverting this behavior seemed to enable BLN to work.

Refer to OP for details on how to enable BLN (or see my previous post).

As always, you can get this build from http://xda.mister-freeze.eu/XDA-files/ChronoMonochrome/kernel/janice/
[Galaxy S Advance I9070 Android Development] Pdevo:
Thank you chrono for this update!

I flashed kernel this morning on stock and I can say some first impressions about R5.9 and in general about 5.8 after some weeks of usage:

Not a placebo, from R5.8 I find overall performance very good, probably the best from first release of the kernel for advance, some days of usage will be needed to check how battery life performs.

The major evidence I can find is surfing the web on stock browser, this is a a good way for me to estimate especially how lmk is effective and how multitasking behave: here I can see that system can handle heavy pages further than other kernels I used, I need to stress it more before getting browser to close (some press sites in my country or also portals like Tom's Hardware etc, Tripadvisor or also my university site) and still there is less impact on other apps, resulting so far in a better multitasking I say.

Again I am facing the deepsleep issue, but this time I guess I found what can be the cause.

From WLD I find an impressive cpu wakelock caused by System(media), indicated as AudioOut_2, which basically takes place all the time.

From some searches I found this can be related to some apps like viber, skype and so on (maybe whatsapp and others, threads referring to this are not recent, some things may have changed over the years), but potentially any other app like games or music players.

Like I said some weeks ago I found my issue fixed when I did a factory reset, but then installing the really few apps I use (Whatsapp, Total Commander, XDA labs, Diskinfo and Fibrapp) this went back again, and I am not facing this with other kernels, so seems to be a little issue with this audio stuff I guess.

About calls, I really would like to find some spare time to cook from scratch the jb rom and do some further investigations to what the hell is wrong ( Here I understand you al lot, beacuse I have some tedious exams too :) ), so I will keep you updated as soon as this happens!
[Galaxy S Advance I9070 Android Development] isaak:
Thank you for fixing BLN! :)

It seems you left both LCDCLK interfaces in this release, I don't know if it's intentional:
[Galaxy S Advance I9070 Android Development] ChronoMonochrome:
Today I have faced deepsleep issue on both codina & janice phones too. I will investigate this issue as soon as I can.

No, that was not intentional, but since this bug was relatively "innocent", I've completely forgot about that.
[Galaxy S Advance I9070 Android Development] ChronoMonochrome:
New build r5.9.1 is up!

Changelog

R5.9.1

Resolved (hopefully) deepsleep issues *

Fixed touchkey not working issue **

* tested in about 24 hours so far with ~6 hours of deep sleep on UltimateROM 6.0.1 without any issues with wakelocks.

** It seems that in r5.9 was introduced a bug - touch keys weren't working (at least, on 6.0.1) after device wake up.
[Galaxy S Advance I9070 Android Development] isaak:
Interesting, but 5.9.1 is not up yet:

http://xda.mister-freeze.eu/XDA-files/ChronoMonochrome/kernel/janice/
[Galaxy S Advance I9070 Android Development] ChronoMonochrome:
There probably was some error during uploading the file - should be uoloaded now.
[Galaxy S Advance I9070 Android Development] huluhola:
1st, congrats to [MENTION=5695278]ChronoMonochrome[/MENTION] finally fix BLN on janice

so will janice go to deep sleep if BLN is enabled?
[Galaxy S Advance I9070 Android Development] ChronoMonochrome:
It will do so only if don't have any ongoing messages. Otherwise it cannot work without waking up the device.

[MENTION=5840412]ace2nutzer[/MENTION], via PM you wrote that BLN can work without wakelock when LEDs aren't blinking. Is it still the case, if so can you please share the required changes? Cause I've tried just disabling blinking and that didn't work for me.
[Galaxy S Advance I9070 Android Development] ace2nutzer:
No changes required, disable just wakelock & blink. BLN works without wakelock & blink, but not permanent, that means the 2 LEDs will only light up when the phone is randomly awake.

So it'll "blink" very irregular. Another option is to use the flash LED, that works 100% without blink and wakelock, but unfortunately the power consumption is very high, even on lowest brightness.

So the best (IMO) is to use regular wakelock (wakelock is only active during blinking) and use 100msec on_delay and 3000msec off_delay. It works even on sleep state 4 ... same like sweep2wake wakelock, but with the difference that the phone is always in wakelock.
[Galaxy S Advance I9070 Android Development] isaak:
[MENTION=5695278]ChronoMonochrome[/MENTION]

For some reason I can't play any youtube video inside a browser. I tried with Naked Browser and the native Browser of LineageOS 11 (Dynamic and ZenX governors, min 400 max 1000), but it always appears a loading circle that nevers ends. Fortunately it doesn't happen with the official youtube app.
[Galaxy S Advance I9070 Android Development] ChronoMonochrome:
Works in android 6.0.1 for me. Maybe something have changed in youtube API that caused older webview code (like 4.4.4) not to work? Can you test if this is kernel-related (you can just switch to r5.8.2 and if video playback doesn't work here too but was working earlier, then it's not kernel issue).
[Galaxy S Advance I9070 Android Development] #Henkate:
I'm on LOS11 and I'm using the "stock" kernel of LOS11, the one which comes with it (default settings). I've also tried to play YouTube videos in LOS's browser and Naked Browser, but I had the same behaviour as you. It's working fine in Chrome, but there's some lag though.

As for YouTube app, I'm using OGYoutube since I'm gapps free and the video starts playing, but then it stays black so I can't see anything. I can hear the sound though. I've used OGYoutube all the time on my Huawei Nova (which sadly broke about two months ago or so) and previous phone before Nova (Galaxy J5 2015) and there were no problems with it.
[Galaxy S Advance I9070 Android Development] isaak:
If it stopped working on [MENTION=5371721]Epirex[/MENTION] rom+kernel (as reported here), then I think it's something related to LOS11.
[Galaxy S Advance I9070 Android Development] ace2nutzer:
Chrono, did u maybe forgot to apply the live video stream patch ?

It was from epirex or meticoulos .. Check my github.

It's a very small change in the source code.. Only need to delete one or two lines.
[Galaxy S Advance I9070 Android Development] huluhola:
[MENTION=5695278]ChronoMonochrome[/MENTION]

Can u hlp to fix the compass, wifi direct on cm rom?
[Galaxy S Advance I9070 Android Development] ChronoMonochrome:
I don't maintain any 4.4.4 ROMs here... People who mentioned video playback issue on Youtube were using LOS11 by Epirex (as far as I understand). I'm afraid live streaming patch can't help here - if those videos all the time were playing normally, and now suddenly stopped to play, then it's due to Youtube changes. I've noticed some recent changes in desktop Youtube version too.

Which CM ROM? Compass was working (at least in some apps, like Compass and Sensor Box) on ROMs I've built so far. But I can assume that it won't work in some other apps due to a legacy code in the proprietary sensor lib. Wifi direct can't be fixed in any ROMs cause it's a closed technology.
[Galaxy S Advance I9070 Android Development] huluhola:
Can I ask a dumb question?

Why does ace 2 supports glonass but s advance can't support?

"Newer" novathor u8500 on ace 2??
[Galaxy S Advance I9070 Android Development] ChronoMonochrome:
Due to different Radio chips on these two phones, probably.
[Galaxy S Advance I9070 Android Development] ErackGamer:
Phone is barely entering in deep sleep in latest kernel release
[Galaxy S Advance I9070 Android Development] ChronoMonochrome:
Consider checking your apps list / wakelocks statistics etc. Deep sleep is working normally in r5.9.1.
[Galaxy S Advance I9070 Android Development] isaak:
I have a different issue.

In LOS11 I turn on the torch through quick settings button, but after 5 minutes phone is shut down.

It's always reproducible in r5.9.1.
[Galaxy S Advance I9070 Android Development] ChronoMonochrome:
New build r5.9.2 is up!

Changelog

R5.9.2

Memory management fixes*

Fixed Torch issue **

* it appeared that there still were some leftover commits that were making (reportedly) the memory management even worse than it could be.

** tested in Android 6.0.0 so far.

You can check the current consumption with the following command (type in terminal, not in adb):
[Galaxy S Advance I9070 Android Development] isaak:
In this version I found out more issues (in LOS11):

1) Rear camera recognition is broken.. if I try to open the default camera app, it will appear the alert "Unfortunately Camera Has Stopped".

I cleared data, but it didn't help. In Chrono Kernel r5.9.1, camera was fine.

2) Vibrator intensity is constant.. if I set it at 11% or 83%, the intensity is always weak, while it should change if you increase it.
[Galaxy S Advance I9070 Android Development] ChronoMonochrome:
1. I've checked the camera and apparently that the recent changes broke it. Hopefully, fixed in r5.8.3, tested Android 6.0.1 so far (try with clearing the data because this bug might persist somehow even on a normally functioning kernel).

2. Checked /sys/vibrator/pwm_value, changing a vibration intensity works here (didn't test the previous release). Do you use some app to change the vibration intensity? Maybe permissions are set wrong (in 6.0.1 they're set to 0644 / root, apps won't be able to adjust this value).
[Galaxy S Advance I9070 Android Development] isaak:
I just go in Settings -> Sound-> Vibrator Intensity. The vibration is a lot weaker than usual.

The file is already set to 0644 root like yours, tried to set it to 0777 but it didn't work, so I restored it to 0644.

[EDIT] The bug is gone away with a simple reboot!! Probably it was a weird permission issue on my side.

[EDIT 2] About Chrono Kernel R5.9.3, I installed it in LOS11, but camera still crashed (clearing data didn't help) and main storage + micro sd card were completely inaccessible (getting some 'access denied' warnings). I had to reinstall R5.9.2.
[Galaxy S Advance I9070 Android Development] ChronoMonochrome:
Update to r5.10 is up!

Changelog

R5.10

Reconsider not to include some recent patches *

Interactive: performance improvements

Camera / storage issues should be fixed now on 4.4.4

Fixed charger mode issue (thanks to [MENTION=1508790]SergeyL[/MENTION])

* I had to reconsider on regard of what patches to include in kernel builds, because some of recent changes appeared to have some negative effects, performance-wise.
[Galaxy S Advance I9070 Android Development] isaak:
In my file manager I didn't find any /proc/last_kmsg, but just /proc/kmsg. Is it the same file?

The last kernel release is great, especially the charger mode, but I had 2 forced shutdowns with the torch bundled in LineageOS 11. I didn't have the chance to take a log, but sometimes it can't handle more than 5 minutes turned on while you're actively using the phone (like navigating in the android settings or through any quick setting toggle), so I replaced the apk file with the apk file included in Vanir Rom by mkaluza (in attachment). Of course a reboot was needed to complete the replacement.

Source code of decompiled Torch:

https://github.com/mkaluza/android_packages_apps_Torch_decompiled
[Galaxy S Advance I9070 Android Development] ChronoMonochrome:
Sometimes last_kmsg log might not appear in the system (it won't be available after a cold boot, e.g. after a shutdown). I might have missed some fixes because I had to rework all the changes in a couple of the latest releases.
[Galaxy S Advance I9070 Android Development] :
No SIM card

Hi,

I installed UltimateROM-6.0-20180820-unified with chrono_kernel_r5.10-fe33fcb64789-janice on my old Samsung i9070 and I have a couple of issues:

- it dosen't see my SIM card -> No SIM card

- if I want to change the time the application crashes -> Clock has stopped

- if I want to close all the background applications -> Ssytem UI has stopped

- I do not see a reboot option if I press long on power button, only power off

The SIM card issue is the most annoying. Any idea why?

Thanks.
[Galaxy S Advance I9070 Android Development] :
Partially fixed the SIM card issue:

- if I install the janice ROM + chrono_kernel_r5.10 not the unified version it works, but is slower then before.
[General Topics] brunobski:
Hi guys, i have a kind of trouble with my i750 with WM2003SE, when people call me, it appears in the toolbar it appears the thing like in comic books, but i can't see who's calling me.

Can u help me?

Sorry my bad english.

Or a APP to see who's calling!
[General Topics] brunobski:
Anyone?

Regards.
[General Topics] brunobski:
PIC ADDED!
[General Topics] brunobski:
Helpppppppppp
[LG V20 Guides, News, & Discussion] dudeawsome:
So now we know that we are getting oreo lets talk about P.

According to the article, we should get P because currently, they don't have many devices to work on. Also states the V20 is eligible for P. That's up to LG now.

https://www.theandroidsoul.com/android-p-release-date/#jump-lg
[LG V20 Guides, News, & Discussion] popper668:
without the ability to root I will not be staying with this device or any other LG for that matter long enough to think about P
[LG V20 Guides, News, & Discussion] cnjax:
P? Pfft we haven't even seen Oreo yet
[LG V20 Guides, News, & Discussion] Snakecharmed:
I said this in one of runningnak3d's threads, but these Android releases are becoming increasingly pointless and only serve to have Google find more ways to lock us out of customizing our devices under the guise of being up-to-date with the latest software. I have no interest in Android P.

https://www.xda-developers.com/android-p-blocks-custom-overlays-substratum-themes/

Also, they seem hellbent on this rounded corner crap. Welcome to web design and desktop computing in 2005. Stupid.
[LG V20 Guides, News, & Discussion] dudeawsome:
Was just putting the info out. I don't even know if I'll have the V20 that long.
[LG V20 Guides, News, & Discussion] runningnak3d:
Thanks for bringing this to my attention.

WTF - overlays have to be signed now?!? Yes, if you are rooted, you can install your own cert, or patch the cert check out, but that is just ------ WTF?!?

I understand a lot of the security that is in place, but to add security where it isn't needed just so you can keep your LOOK -- SMFH.

All I can say is support Lineage as much as you can (I am), and don't buy phones that are locked down. Google really is trying to turn Android into Windows. Remember how easy it was to modify Windows 95, 98 -- you could replace the entire shell. XP (and even Vista, 7, and 8) you could theme very easily. Then came Win 10. Yes, you can still theme it, but since it is a rolling release, MS is making it harder and harder. Eventually Stardock will give up.

When Android was released, it was so open that you could change pretty much anything, but they are doing the same thing -- locking it down more and more.

We need a third choice. Win Phone wasn't it, and I don't know of any contenders right now that have a chance. This sucks -- it is MS and Apple all over again, only Google replaced MS.

-- Brian