yashsingh1/xdaforums huggingface dataset:
[G2 Android Development] pipyakas:
My f320 also have PVS bin 2 yet I undervolted it to 720mv for 300, 422 and 499mhz w/o any problem, using beta n7

But it will never handle any freq higher than 2.65ghz, which cause logo hang and reboot for many version for me in the past
[G2 Android Development] murok9042:
After rebooting phone I always get a toast message: synapse boot cancelled. Even your workaround above does not work. Using Beta 6 btw.

Gesendet von meinem LG-D802 mit Tapatalk
[G2 Android Development] GalaticStryder:
Synapse is a bit "tenebrous" in marshmallow, in order to get all settings restored properly you'll need to set all settings manually after the "trick" if you didn't save the profile before. I always get "Synapse boot complete" using this:

1. Install it from PlayStore and open it.

2. You'll get no UCI support after accepting root privileges.

3. Close it and re-open.

4. Last applied settings weren't deemed stable message will appear.

5. Go to tools, clear synapse cache and restart the app.

6. Restart the app once or twice again.

7. Confirm the message if it still appears and make your tweaks and save a profile for them.

8. Restart Synapse, it shouldn't pop up with any message this time.

After those steps it will stick properly your settings after booting as it's supposed too. Don't open the app right after boot, wait for the boot complete message. If open it all settings will be there.

I know it's hacky but it's what we have besides terminal. I'm planning to get around with Synapse code updates to attempt a fix, which is probably not the case as the developer doesn't even care about it anymore and won't accept my pull request if I manage to do so.

Another possibility that I was thinking off was a ZSH oriented app with manual/automatic toybox controls for all sysfs changes.

E.g.: Type gpu_clk 450 && gpu_gov msm-adreno-tz. Type cpuclk 2500 && cpu_gov darkness. All this on a simple material applet interface and a simple manual for the commands.
[G2 Android Development] Floodland:
Sounds good, but what about a simpler/less effort option: You could make your own kernel adiutor mod, adding the parameters your kernel support.

Other developers already did that (Zg85), and is a simple/elegant solution, for a well known software which is faster and do not have the issues Synapse does. It is Open Source, Apache license, and +-95% of the required code is already written.
[G2 Android Development] thtkidsvm:
Probably just have to adjust the voltages at the higher frequency. Maybe that's what I have to do instead of globally lowering the frequency. Undervolting thoroughly could be quite a tedious task and I feel like Im not going to see a huge difference so I just leave it alone for now.
[G2 Android Development] murok9042:
Thanks for the steps but I am having issues at step 7.

I cannot save/backup a profile - it always shows an error: tar: can't execute 'compress'. "no such file". after trying to backup the profile. I did give a profile name and apply it either. I gave permissions for storage in the applications settings, too. But the error still appears.
[G2 Android Development] GalaticStryder:
I misspelled, the right name is 'config'. Profile used is for the Synapse UI setting I think. Tap 'export config' then restart and apply config. Your done after that.
[G2 Android Development] peestandingup:
Hi. Are there no betas for the D801? Only ones I'm seeing are the stable version from last year & the Pure one.
[G2 Android Development] DvineLord:
can the N4 beta for d800 be used as daily driver kernel?
[G2 Android Development] murok9042:
Thanks again but I still get "Synapse boot cancelled" after doing your steps and rebooting phone. Do I have to deactivate the stabilty check in the app settings? I am giving the app root permissions and the permission for the storage. Could it be due to the current CustomROM which I am using right now.

I just want to change the charging speed - it only charges 1000 mA with original charger + cable. Is there any other app you would recommend to change the value for the charging speed e.g. with a command in terminal emulator?
[G2 Android Development] GalaticStryder:
These are the commands that I've written based on Dori's implementation: https://github.com/GalaticStryder/a...mmit/4332411fd5462b08623c748cf80c75d9cab54945

echo 2 > generic /sys/kernel/fast_charge/force_fast_charge
echo 1800 > /sys/kernel/fast_charge/fast_charge_level
echo 1800 > /sys/module/smb349_charger/parameters/smb349_thermal_mitigation

You don't need to be deemed stable to fast charge, just open the app and select fast charger mode custom and 1800 or more mV, as you wish.
[G2 Android Development] murok9042:
Ok this is working fine! But is there any command to save it? After rebooting phone the values are back to stock again :(
[G2 Android Development] GalaticStryder:
This is not a static sysfs node, it will switch back to disabled eventually. You should try adding the commands I told you to /sbin/lambda_post-boot.sh.
[G2 Android Development] murok9042:
After rebooting phone lambda_post-boot.sh is also getting back to stock after adding the three commands into this file [emoji26]

EDIT

Synapse boot complete!! I just did wipe dalvik/cache with recovery before doing your suggested steps. Now synapse is working fine after reboot ?

Gesendet von meinem LG-D802 mit Tapatalk
[G2 Android Development] GalaticStryder:
BETA 8 schedule/info

I'm programming a BETA 8 for tomorrow targeting all variants, I merged a potential fix for the non-booting case with some bootloaders. The DTS (board) code that should have fixed the issue was merged a lot of time ago but the actual C# code for it was bypassed.

I could only discover this when searching the sound changes to see if I haven't missed anything, then I revisited the DTS change history and found a change that should have fixed the bootloader voltage setting issues. Calling the 'qcom,proxy-consumer-voltage' returned me nothing, looking a little bit more I found out the I missed the #C part for the 'qcom,proxy-consumer-voltage' DTS call.

Which is: https://github.com/GalaticStryder/kernel_lge_msm8974/commit/340fefff18bbafbc2cf740b3b9304e085904c589

To complement:

https://github.com/GalaticStryder/kernel_lge_msm8974/commit/add71c280baa82e89872eb0380d7b15479c75245

And enabled for all devices, including the ones that boot properly:

https://github.com/GalaticStryder/kernel_lge_msm8974/commit/a6a07f71101bf448dfeccb3510cd3d24b810b281

BETA 8 includes the rest of the sound changes from 3.10 like mfd and slimbus needed counterparts, which are vital to get a better sound out of the hardware abstraction. As only D802 had 3.10 sound on incremental, this is new to everyone.

UKM code was polished and converted to newest changes including limiter API. It still has got one little issue in the RAM status page cause I need to backport LMK from dorimanx and neobuddy.

There is some more multitasking spice on BETA 8 which makes swapping and reclaim smarter and efficient. LMK was reduced to what corresponds to 'medium' profile in dorimanx kernel, which is lower (less killer of tasks) than default profile due to LG stock RAM management being poorer - of course - than 6.0 CAF firmwares like PA 6.0 and CM 13.0. Swap usage is now using 40% of all RAM iteration (dorimanx uses 50% but as I said he needs to deal with LG stock memory management).

The full change is here: https://github.com/GalaticStryder/a...mmit/dc77e27d10743fe28f8051301aae1091b7f4957a

D800 - [MENTION=5031300]blastagator[/MENTION] - and D801 (both already available at AFH) are key devices that I need reports since I don't build them for ages, also because D800 was a known hang on LG logo on the new base tests. Let's see if the consumer change has shown some effect. Please post the firmware (ROM, baseband...) when reporting.

D802 is also in AFH for the testers, it has consumer support enabled just like all variants and it's running solid all day.

Other devices will build tomorrow...
[G2 Android Development] bamonkey:
Beta 8 - D800

ROM - Latest AICP nightly

Hybrid Bootstacks/Baseband Bumped

Latest Blastigator Recovery

Still stuck on LG Boot logo I'm afraid to report - Ive been trying to find any kind of logs to help you out each time. No last_kmsg is ever generated and im not sure if a dmesg pulled from the terminal in recovery would help you. If there is anything you want me to try I'm up all night. Thanks for the continued effort on this device, i know its been a real PITA.
[G2 Android Development] ytgbg:
[MENTION=6175749]GalaticStryder[/MENTION]

D802 on latest Exodus. Beta 8 works great. No issues to report.

Great work, as always!
[G2 Android Development] Kuyakj84:
D801 on latest CM 13 nightly. Hangs on LG logo. No logs unfortunately.
[G2 Android Development] fuibauer:
D802 also on latest CM13 nightly - it normaly boots to the cm bootanimation but after that the screen is black an remains black. I will add a recovery text hope its the right one that you need. :)
[G2 Android Development] GalaticStryder:
There can be a wide range of issues on nightlies, they change many things needed for the kernel like vold and fs management. I'd avoid those nightlies, not blaming the maintainers but the general CM context as a bleeding-edge product. This issue should be in your dmesg, you can pull it from ADB shell.
[G2 Android Development] Mrondo:
D801 on 08/02 CM13 nightly hangs on LG logo for me as well, Beta N8. I was unable to grab logs
[G2 Android Development] thtkidsvm:
Beta 8 on my d801 and it didn't get past LG logo. Im using XOSP 7-14 unofficial build 6.3, hybrid bootstack. beta 6 and beta 4 worked on XOSP.
[G2 Android Development] eggeioss:
D802 on latest PA with stock ROM bootloader. Beta 8 boots fine and runs great!

Inviato dal mio LG-D802 utilizzando Tapatalk
[G2 Android Development] GalaticStryder:
Getting logs on this stage may be impossible due to ADB load up happening later in the boot sequence. I've tried to use the consumer driver to hold the voltage to 1160mv when booting and restricted the max frequency to 2.57GHz after seeing a performance gain over 2.8GHz after all this time.

Dorimanx has a code to lock up at 2.2GHz before his limiter driver initializes, it means during boot it will stick at 2.2GHz. I could do the same here but after some reading I think 2.5GHz will lead to faster boot times if it's ok for all variants.

I'll see if I can push something called BETA 9 to test this, on my D802 seems all good after the change.
[G2 Android Development] dan3840:
The kernel is great but lacks an option to force the processor to keep the frequency when the temperature is high. In previous versions gave to modify the options in thermal but no longer has the option to do so
[G2 Android Development] GalaticStryder:
It's not finished... didn't play with thermal yet. I'll mod it from showp's work.
[G2 Android Development] paryav:
D802 last RR B8.

Boot ok.

App compiled at boot ok.

Overclocking with high voltage ok.

Trottling ok.
[G2 Android Development] kwstas93:
i am with Incremental-N260-SOUNDFX all working fine but when i change speaker gain after restart the kernel audikator it is zero again.i cant change speaker gain.it reset itself.....RESURRECTION REMIX M
[G2 Android Development] banjaminicc:
try beta 8
[G2 Android Development] paryav:
Oops.

Not all ok. D802 RR last.

After some time i need reboot.

Reboot.

Bootloop on RR logo.

Reboot in recovery. Wiped cache and Dalvik cache. Reboot.

Bootloop. Cant get compile app.

Reboot in recovery. Re flash B8. Reboot.

Bootloop

Reboot in recovery. Flash B2. Reboot.

All OK. App compiled. Phone run.

Reboot in recovery. Flash B8. Not wiped cache and Dalvik cache. Reboot.

All OK. Phone run.

B2 have some Overclocking But always boot.
[G2 Android Development] kwstas93:
the same problem with beta 8 .i try it and with synapse too
[G2 Android Development] blakeatl:
Beta 8 stuck on the LG screen for me on d801. Ressurection Remix latest version.
[G2 Android Development] pipyakas:
Im experiencing a weird issue on DU 10.4 with beta n7, f320 variant

Only one cpu core is used, always for all kind of task, and it would ramp up to 2.2ghz because cpu usage is very high

In order to get other cores running I need to manually set min core awake to something higher than 1

And also this problem doesnt exist with DU default kernel
[G2 Android Development] GalaticStryder:
As far as I've taken a look at their repos, they change many stuff on the init files, inclusive CPU settings. When you flash my kernel, if those init changes are applied it may conflict with MSM limiter after it's up. Not a Kernel problem, but a compatibility issue...

Thanks for the report.
[G2 Android Development] android extreme:
To fix this issue disable and re enable the hotplug that you use
[G2 Android Development] GalaticStryder:
BETA 9 is alive for all

Get ya packages...

Changelog: (Compared to BETA 6)

Al Viro - get rid of kern_path_parent()
Ícaro Hoff - dts: consolidate voltage and frequency values for the MSM8974 SoC
Ícaro Hoff - defconfig: CONFIG_MISC_FILESYSTEMS is gone for so long
Eric Dumazet - ipv6: add complete rcu protection around np->opt
WANG Cong - UPSTREAM: ppp: defer netns reference release for ppp channel
Hong-Mei Li - drivers: lmk: Fix null pointer issue
Hong-Mei Li - drivers: lmk: Fix double delete issue
Yi-wei Zhao - staging: android: lmk: read rb tree root with spinlock
Ícaro Hoff - lmk, reclaim: enhanced pressure and logic code
Hong-Mei Li - staging: android: lowmemorykiller: implement task's adj rbtree
Pranav Vashi - mm: process_reclaim: Expose current pressure to sysfs
Ícaro Hoff - sound: remove file_inode helper from es325 and friends
Ícaro Hoff - documentation: update after all sound related updates
Sagar Dharia - slimbus: Use physical address type where physical address is used
Dorimanx - SLIMBUS: sync with 3.10.y to fix call start errors.
Dorimanx - SLIMBUS: add missing include.
Sagar Dharia - slimbus: Remove unnecessary pointer type-cast
Sagar Dharia - slim_ngd: Handle invalid/timeout TX errors gracefully
Kiran Gunda - slim_msm: effective management of data ports
Sagar Dharia - slim_msm: Handle ADSP SSR gracefully for apps-owned data channels
Mitchel Humpherys - slim_msm: fix LPAE builds (64-bit division)
Ícaro Hoff - mfd: GENERIC_HARDIRQS still needed for my kernel
Mark Brown - mfd: core: Push irqdomain mapping out into devices
Dorimanx - dts: fix missing define for cdc-mad-dmic-rate
Ícaro Hoff - mfd: convert to 3.10 sound as well
Gopikrishnaiah Anandan - ARM: dts: msm: Update the vifeed back routing
Ícaro Hoff - defconfig: update all configs to latest changes
David Collins - regulator: Add proxy consumer driver
Devin Kim - dts: MBHC skipped when using external headset detection

Downloads

AFH is now organized per folder/variant: https://www.androidfilehost.com/?w=files&flid=53519

There's a special change on voltages/frequency table to attempt booting all hardware.
[G2 Android Development] DvineLord:
d800 still didn't boot on N9 runnung latest RR.

try making new pure builds and see if they boot.
[G2 Android Development] Floodland:
Beta N9 boots fine with Exodus latest nightly on D806 (but Beta 8 and several incrementals also did so).

Great job
[G2 Android Development] fuibauer:
the phone boots now fine on cm13 latest nightly (D802). keep up the good work.

and i could offset -55.
[G2 Android Development] GalaticStryder:
In such cases, I'll just be adding the "usual" things on top of my AOSPA Kernel branched out from the old pure builds. I just want people to report whether N9 is working for them or not to see what targets I can keep the current development (D802 as my variant) and which ones will need to rebase.

Report

Device: D802

Bootstack: Hybrid

Firmware: Paranoid Android

State: Functional

Simple and easy until both branches: lambda-devel and lambda cross together after rebase. I don't know what can cause this behaviour but I have an idea where it started happening: swap/zram.

Anyway it's too late for bringing something up 2000+ changes on top of the other one. So I'll just filter the essentials (hotplug, thermal, uv/ov...) and build.
[G2 Android Development] pipyakas:
Beta N9 does not boot and hang on LG logo on DU 10.4, f320
[G2 Android Development] thtkidsvm:
Device: d801

Bootstack: Hybrid

Firmware: XOSP 6.3

State: doesn't go past LG Boot Logo
[G2 Android Development] axlrvx:
I don't know what you did with the Beta N4 for d802 GalacticStryder but is perfect for me. I don't need to touch anything.

CM13 20160804 Nightly + Lambda kernel BETA N4.

Thanks!

Enviado desde mi LG-D802 mediante Tapatalk
[G2 Android Development] DvineLord:
does anyone have a working N4 d800 beta they could share?
[G2 Android Development] eggeioss:
Beta N9 Report

Device: D802

Bootstack: Stock LG

Firmware: Paranoid Android

State: Functional!
[G2 Android Development] PhilRoll:
do lambda kernel support f2fs format?
[G2 Android Development] xxoscarxx28:
N9 for F320 can't get pass LG boot logo.
[G2 Android Development] chrislam1220:
So DU is not suggested to flash this kernel?
[G2 Android Development] paul89rulez:
Beta n9 report:

Device:d802

Bootstack:hybrid

Firmware:Turbo ROM (zg85)

State: functional
[G2 Android Development] Punraz_:
Beta N9 works on RR D802
[G2 Android Development] blakeatl:
Same here. D801

Now on Exodus 8/04

Stuck on LG Logo

Able to use Pure Stable 4/21 and it's still smooth as butter.
[G2 Android Development] damianmu:
BETA N9

Device: D802

Bootstack: Hybrid

Firmware: RR

State: Works without any problems
[G2 Android Development] SREEPRAJAY:
Orion 2.4

D802

So far so good...smooth and silky

Maybe someone benefits....today or someday

Thanks [MENTION=6175749]GalaticStryder[/MENTION]
[G2 Android Development] _Legend0:
Beta N9

Dirty Unicorns 10.4

D802

Working without issues :D
[G2 Android Development] Mrondo:
Device: D801

Bootstack: Hybrid

Firmware: CyanogenMod 13

Status: Doesn't boot
[G2 Android Development] GalaticStryder:
Thanks for the reply, I'm yet going to try some voltage changes to test those variants before rebasing them, I might get back to 1200mV but lock it to default 1100mV during boot since 2.5GHz won't have problems with the stock voltage. The D800 variant will need more effort to see why it doesn't settle with the new base.
[G2 Android Development] Mrondo:
Sure thing. I'm willing to be a tester for my variant when the need arises
[G2 Android Development] niklas389:
I could test these also, if you need someone! :)

I've got an D802 (:
[G2 Android Development] Shaaryn:
Can someone share his kernel settings please?

I want my battery lasts more.
[G2 Android Development] Floodland:
Default settings are pretty good IMHO. I just limit high frequency (to 1.9, 1.7ghz also provide enough performance) and tweak a little bricked hotplug increasing plug percentages (specifically core 1, which is usually is turned on and off for no good reason, even with minimal load).

I suggest to pay more attention to other aspects not kernel related (screen brightness, perverse Google services, location off unless required, etc).
[G2 Android Development] bestgames:
BETA N9

Device: LS980

Bootstack: Hybrid

Firmware: RR 5.7.2

State: Stuck at logo
[G2 Android Development] pipyakas:
Is thermal throttling a part of the rom? While using DU I noticed that it doesnt thermal throttle at all, I can play modern combat 5 for around 15min and the cpu would get to 90 degree running 2.27ghz

While RR would throttle it all the way down to 1.5ghz, all on beta n7
[G2 Android Development] GalaticStryder:
Of course, thermal-manager binary is the responsible for msm-thermal zone management for most devices, there's a file in device trees that points out the zones for a given device: cpu0, display, battery and other thermal sensors to retrieve the thermal information.

The binary lives in /system/bin/thermal-engine (https://github.com/AOSPA/android_de...26be790f0b7af1d31b/sepolicy/file_contexts#L38)

And it needs policy allows to run on enforcing: https://github.com/AOSPA/android_de...00122a5d3d988438021c/common/thermal-engine.te

As well as a service instance:

https://github.com/AOSPA/android_de...e790f0b7af1d31b/rootdir/etc/init.qcom.rc#L394

And this is the binary: https://github.com/ThankYouMario/pr...-caf/g2-common/proprietary/bin/thermal-engine

As a binary we don't know how it manages that, but I assume it's a barely runtime event written in C++ that adresses the msm-thermal driver to the DT nodes after parsing the config file I mentioned above.

The config file is extracted from LG G2 stock ROM to reproduce the same behavior as the stock firmware: https://github.com/GalaticStryder/d...shmallow-caf/configs/thermal-engine-8974.conf

If any of those values point wrong sensors your thermal driver will fry your device in hot oil. I'd say that one of those dependencies for thermal to work is wrong in the "ROM" you mentioned or another thermal solution was adopted without cleaning up the binaries/configs and etc.

Other drivers like Intelli Thermal used on Dori's kernel are based on the lines for MSM thermal to avoid ROM conflicts like that. Long life MSM thermal!
[G2 Android Development] n@vier:
[MENTION=6175749]GalaticStryder[/MENTION]

Device: D802

ROM: AICP 11 6.0.1 (latest build 07/27)

Kernel: Lambda Hipnose Beta N9

Status: it works great!

Great job! Thanks ;)
[G2 Android Development] GalaticStryder:
Thanks for the input on D802, it works good for sure, AICP has a great maintainer behind so it's a pretty decent combo. Synapse has got an update today, it makes my UKM mode much more stable, finally! If you're coming from dorimanx kernel you'll miss some options like built-in control of Faux S.C. driver (not yet ported from his configs) and thermal tunables which are using msm-thermal.

If you see anything strange, please report so I can catch up before stable/rebase release.
[G2 Android Development] NightBladeDK:
Same for me.

Ls989 using a hybrid bootstack.

Beta N9 failing to boot, stays at LG logo.
[G2 Android Development] n@vier:
Yes I will test deeply and I will report if I find something... :good:

I had noticed that faux s.c. driver didn't work but with V4A Atmos 4.8 Sony Beats Edition is not a problem ;)

Also single thermal control works well (I always monitor in real time all parameters with devchek info floating monitor on status bar ;) ) temps are good and fast charge works too only synapse is not perfect... I think that if you will find a simple way to switch all controls to a more clean app it would be great but I know it could not be so simple....

PS: I come from dorimanx's kernel after 15 months of exclusive use and test of his MASTERPIECE...we know he is a live legend...but only see a solid kernel for AOSP Rom MM (that are now a big step up compared to LP stock and stock based Rom) with the philosophy based on dorimanx kernel under the hood (I checked all parameters of synapse...) it is a great work... so thanks for your development ;)
[G2 Android Development] d_Schizzo:
Hey n@vier,

nice to see you here too buddy! ;):good:

I just switched to Dirty Unicorns on saturday. Its a very nice combo with this kernel!

You are right, dorimanx is very good and i was on stock because of dori since i own my g2. But the bugs with stock-lollipop ROM was killing me lately.

This kernel works very well, but synapse is kinda ****ty. I use kernel adiutor now. Much much better and stabler, with build-in tasker support:good:.

Regards,

Schizzo
[G2 Android Development] eggeioss:
Hi guys, stability and speed are very great but I have the impression that Beta N9 consumes more battery than Beta N8.

Inviato dal mio LG-D802 utilizzando Tapatalk