yashsingh1/xdaforums huggingface dataset:
[G2 Android Development] ytgbg:
No mobile data connectivity issue

[MENTION=6175749]GalaticStryder[/MENTION]

Hi mate,

No-mobile-data-issue appeared again on latest Incremental 234. I managed to take last kmsg and dmseg. Reboot is resolving temporary the issue.

Hope this helps.

Also, probably not kernel related, but rom- I am using your latest PA rom but getting problems with bluetooth transfers of files from pc. The phone connects successfully, but in the middle of transfer is always failing. I got last kmsg and dmesg right after this is happening.

Once again - probably not kernel related, but rom - I can't get the pc connection via usb to work for file transfers. After attaching the usb cable to the pc and phone, and choosing file transfer option instead of charging, there is a message on the pc that the usb transfers could be faster and the phone is not detected and nothing is happening. All other MM roms I got did connect immediately and without problems.

I also got last kmsg and dmesg after this happening.

I am new to this help-dev-properly and please excuse me if I did something wrong with attached logs or did not attaced what is suppose to be attached. I just want to help. Logcats that I did are always comming back at 0 bytes.

All kmsg's and dmesg's were taken with Kernel Adiutor Mod.

If you need anything esle, just tell me what is needed and I will reproduce the problems and do what you need/say to detect the problem.
[G2 Android Development] idkwhoiam322:
Where can I get the PA builds mentioned in recent posts? Thanks in advance!

Edit: I got it from his profile, thanks anyways!
[G2 Android Development] ytgbg:
XDA G2 Android Development Section. The same section as this thread.
[G2 Android Development] Floodland:
Incremental 234 boots good again. I did not experience signal issues at this point, but was on WiFi coverage almost all the time. Will test a little more today (Metro connectivity is a tough condition for any cell phone around here) and report if I find issues. Thank you, keep rocking
[G2 Android Development] GalaticStryder:
UL seems to be delaying connection then tunneling, tracing the issue I found out that the base kernel has dmux fast shutdown and it causes race when SPS requests other devices like Bluetooth and NFC at the same time, so it just hangs cause the code is not complete. I pushed some fixes from dorimanx kernel for SPS and BAM DMUX and will be testing it to the bottom up. It's early to say but my BT was going down pretty fast when I got high music playback goin' on YouTube. Now, it's holding steady, let's see.
[G2 Android Development] xGOGI:
When you add fast charging?
[G2 Android Development] GalaticStryder:
BETA 6 rolling out

Finally found a decent usage for G+ collections.

https://plus.google.com/collection/kRtzWB

As I posted it will be available for all variants to test tomorrow. D802 might get uploaded today.

I'll try to use the collections to post news about Lambda development, so if you wanna know about it just follow the collection.

Finally stability proof and feature rich!

--- EDIT ---

Ok, pushing BETA 6 for certain variants to test.

Changelog in comparison to BETA 4:

USB keyboard support (use your phone as a keyboard and mouse) - no drivers needed for your PC.
USB backports from 3.10
BAM/SSR updated to 3.10
Fast charge 3.1 support
SPS and Wi-Fi patched
KGSL fixes from 3.10
Removed 3.18 changes for GPU (battery wasn't happy)
Display and MDP patches
Crypto performance fixes
MMC patches and optimization using IRQ
SMPboot patches
+ Everything from latest BETA 5 and 4 but Crypto LZ4 removed (was encrypting the device on reboots - I'll probably need to backport FS to apply it)

Most patches, fixes, and features are from dorimanx with a few minor changes to my tree and for the AOSP environment itself.

Full changelog in comparison to April 4th (3.4.111 vanilla kernel): http://pastebin.com/7fTzZDCr
[G2 Android Development] jeongin8885:
Problem at My f320 with mokee rom

I flashed Beta N6 kernel for f320 after installing Mokee Rom(nightly), but it can't pass lg logo so I boot it recovery mode and install Beta N1 for f320, it successfully boot. I notice the newest lambda kernel to my korean community(Naver Cafe). Other people said that after flashing the newest kernel, it can't pass bootlogo too. Lastly I finally check other people who can successfully boot, but nobody can't successfully boot.

Thanks for reading my feedback and if my post is rude, please understand my fool English ability.
[G2 Android Development] quangtuyen88:
Dirty flash Beta N6 from CM13 nightly N4 and boot working... Now i'm using and will report if have issue.. Seem everything is good until now.
[G2 Android Development] jeongin8885:
Would you send me kernel N4 for f320, I want to flash N4 from N1 first, and flash N6 after flashing kernel

My Email: jil8885@gmail.com
[G2 Android Development] ytgbg:
Beta 6 boots just fine on my D802 with latest PA. All seems fine for the last 20 minutes of my regular use pattern. Will monitor mobile data to see if any drop downs are happening.
[G2 Android Development] quangtuyen88:
Sr i don't have beta N4 for F320..

https://www.androidfilehost.com/?w=files&flid=82254

Seem N4 only for D802.
[G2 Android Development] lunafag:
The mobile data issue seems to be finally solved and I finally got my hands on tweaking. Some controls turned out to be very finicky, especially in Synapse: max frequency always dropping back to 2.2, zram turning back on its own. Adiutor did a better job. Also it has additional options(fb notifier/state notifier switch and msm limiter disable switch). I ended up disabling msm limiter as I suspect it was the reason for erratic max freq behavior and hurting multithreaded performance, but it's not 100%, maybe it's just overheating(it would be cool to have thermal control btw). Here's what I got so far, I suspect PA users can do a little better as it's better optimized. Can't check fast charge at the moment. Thanks [MENTION=6175749]GalaticStryder[/MENTION] for his hard work.
[G2 Android Development] quangtuyen88:
good benkmark point.. can you share your tweak ??
[G2 Android Development] ipatel:
when will the N6 or Hipnose version be uploaded for D800?
[G2 Android Development] GalaticStryder:
UKM code isn't finished yet, don't blame on it. The kernel uses MSM limiter 5 API so UKM can't control it at this time (working on it...), ZRAM can't be changed just like that, yet! Also, there's no special reason changing its size or compression tool for now.

Adiutor Mod is good but not as easy to add my custom stuff and scripts like Synapse/UKM. The FB/state notifier switcher is bull**** you can't/shouldn't disable them. MSM limiter is not meant to be disabled if you like your battery, use the Terminal app or ADB shell to change the frequencies there.

Sysfs path: /sys/kernel/msm_limiter

I've explained all about it and how to use it some time ago.

Don't ask for ETAs, I'll push all variants one by one for people to test. Last time this variant was misbehaving, let's see this time.
[G2 Android Development] lunafag:
[MENTION=6175749]GalaticStryder[/MENTION], cooling down the phone proved that the source of the problems was simple overheating, everything sticks fine now. I personally prefer Synapse myself, that good ol' UI. There's an option called arch power, is it worth enabling? Couldn't find any info about it. Zram off toggle would be useful(Adiutor just executes swapoff when you set size to zero). Fast charge option got disabled during charging with an AC charger - I've encountered that on other ROMs/kernels that provided that option, no surprises here. Strangely, multiple GPU benchmarks didn't show any improvement. Is there a way to check whether it's not simply a visual change?

[MENTION=3666271]quangtuyen88[/MENTION], you should get something close to that without changing anything, just let your phone cool down. It was just a little misunderstanding.
[G2 Android Development] GalaticStryder:
I explained about how I dealt with ZRAM in previous posts. Thus it will only be used when you reduce your LMK values to barely minimal ones and get more than 12 apps in the background (RAM), if you need more RAM it will allocate some of them to the compressed memory block at the cost of CPU usage but will keep multitasking like a brand new phone. You don't need to disable it if the LMK is set to high profiles and there aren't many process in RAM.

Don't give much importance on Synapse UI for indication if some feature is working. Just use the sysfs path to it and see for yourself if it is working. Just unplug set them on Synapse and close it, plug your charger and measure. Arch power is for savings, it will kill performance and doesn't save much battery.
[G2 Android Development] idkwhoiam322:
Just a suggestion, could you add the links to changelogs of the builds you post in androidfilehost in the description?

That would make it easier to access if it gets lost in the thread!

Thanks!
[G2 Android Development] zauzaupt:
boots fine on latest stable 20/07/2016 mokee rom on d802 32gb device.
[G2 Android Development] jeongin8885:
I think that kernel for f320 is wrong file. I share this new version release to Korean Community named develoid and some people downloaded new version and flashed,nobody cansuccess boot and stuck into lg bootlogo. So I roll back my kernel to Beta N1. I don't know why it can't boot.

Thanks for reading my quote. I have only poor English writing ability so please understand my article if it sounds rude.
[G2 Android Development] fuibauer:
wont boot

the kernel wont boot on the latest nightly of cm13. (clean and dirty install)

Lg g2 d802 16gb
[G2 Android Development] thtkidsvm:
Hmm I thought I was the only one getting stuck at lg logo. The first lambda beta 5 that I compiled allowed me to boot in to my d801 fine but when I turned off USB tethering the device just reboots. So I saw some new commits and changes to beta 5 and decided to compile beta 5 again hoping that it would fix the USB tethering issue but instead device doesn't even boot at all it just stays at the lg logo. Had to go back to beta 4 as I deleted the first beta 5 build that I compiled?. BTW I tried it on cm13 nightly 07-08 and on cm13 nightly 07-19.
[G2 Android Development] matteo0026:
Why i have bootloops on d802 when i try to flash hipnose beta N6 on XOSP 6.3?

here the logcat: https://drive.google.com/file/d/0B2CDSAt5MIakbWJRSlg2YXh1NDQ/view?usp=sharing
[G2 Android Development] murok9042:
[MENTION=6798358]matteo0026[/MENTION]

Did you try an older version of this kernel? It should work on XOSP Rom cause it's based on CM13.

Gesendet von meinem LG-D802 mit Tapatalk
[G2 Android Development] matteo0026:
Where is beta N5? I found only beta N4...
[G2 Android Development] Floodland:
Beta 5 was removed because it had issues. Beta 4 is super stable, well performing with no outstanding issues.

With beta 6 I just had the network disconnecting issue reported with previous incrementals. I did not see this issue with incremental 234. The only way to connect to cellular data network was to flash back Beta 4 (reboots and network resets did not work for me). I could try to replicate the issue again to get logs if needed, though I am not sure which was the trigger.
[G2 Android Development] matteo0026:
Ok, good, i flashed beta 4 and it's all ok. But it's strange that bootloop...
[G2 Android Development] GalaticStryder:
Cleaned up the branches, if you want to compile you have lots of options.

Branches:

Lambda for non-OC kernel and without NET/BAM/SPS changes -> Stable

USB for the latest changes in NET/BAM/OC/SPS/USB changes -> Beta 6 compilation

Crypto same as USB but for encryption tests -> Incremental only

I'll push a build for F320/D800 called BETA 7 as a flashback on the stable point of BETA 4 with only governors and CPU changes without OC.

Hope someone will come back with good news for these devices. D802 will keep on crypto changes + attempt to fix cellular dropping, it will receive only incremental builds.
[G2 Android Development] paryav:
Flash Beta6 after Beta2 - Hang on LG logo

Flash Beta4 and after Beta6 All OK.

But i need set High voltage than stock on freq high 2500.

I think by default on some cheaps need more voltage on boot

—------

D802. Resurrectionremix last.
[G2 Android Development] astherion:
GalaticStryder

Thanks for the latest N6 beta for LS980 (it was a birthday present - it was my birthday on 20/07, he-he). For now it seems stable and fast as hell! Thanks, your work is awesome!!!

P.S. I've make "dirty flash" on ls980 pure stable, didn't clean nothing, just flash and reboot. No issues!!!
[G2 Android Development] android extreme:
There is a way to tweak the thermal engine? I've noticed that is too aggressive when it cut cpu and gpu frequency

EDIT:the problem was related to exodus rom, now on cyanide the device is perfectly cool
[G2 Android Development] Wesley32:
Newest beta for D800 doesn't boot. Hangs at LG logo.

Using exodus ROM with LP bootstack. I think? Lol
[G2 Android Development] GalaticStryder:
This device doesn't seem to boot my kernels since the beginning, don't know why and reflecting the configs just shows the device differences, not missing anything on them. As I can't test a D802 as I don't have one I'll cease the support until someone finds out what is going on. BETA 7 had no OC so it's not the cause either.

If someone that has a D800 rollback my kernel until like 47 pages back and get the newest (zram, then OC, then...) changes on top and test, that would get us closer to what the problem could be.

If anyone is interested in doing that I can help though.
[G2 Android Development] thtkidsvm:
Try flashing an older beta right before flashing latest beta. In my case I flashed beta4 -->beta 6--> then reboot.
[G2 Android Development] paryav:
I am wiped Dalvik cache.

Then reboot.

Kernel boot and Hang or reboot after optimizing 10 or less app. Ok. I am flash B4 kernel without overckloking. Kernel load success and compile all app. Than flash B6 without wiped Dalvik cache. Kernel boot without strange warning about system But applied voltage from kernel adiutor app and all run as is. I am shue in my situation default voltage from Speed overckloking need more voltage.

I think kernel Mast boot without overckloking.!

Who need overckloking can applied values from special app aka kernel adiutor

Thanks for Hard work

Solution:

----------

Change /ramdisk/sbin/lambda-post_boot.sh in zip added

echo "2265600" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

or other max_freq.

Reflash kernel
[G2 Android Development] MB525:
Kernel beta 6 booted and worked fine for the last two days on ResurrectionRemix 5.7.1.

A bit hot sometimes but I changed governor and hotplug settings. Thanks for your efforts.
[G2 Android Development] Wesley32:
Do you have a direct link for d800 beta N4? I'm having trouble finding it. I only have beta N2.
[G2 Android Development] thtkidsvm:
Unfortunately no. I dont even have a d800 and I can't compile it for you, but you could try beta n2 then beta 6
[G2 Android Development] blakeatl:
Not seeing any love for the d801 since beta N1.
[G2 Android Development] GalaticStryder:
Will put +20V out-of-the-box and set 2.2GHz in next BETA. You don't need to wipe caches if it gets you in trouble.

Will push the BETA 8 for it (tomorrow?). There aren't many people reporting about some devices like VS980, F320... I'll compile all variants and boots what boots next time.

You can change the kernel back and forth, doesn't matter as long you're running bumped.
[G2 Android Development] paryav:
Thanks for answer.

I have strange phone.

Added this power to lambda-post_boot.sh remove any problem with high freq. Apps compiled.

# set higher voltage

echo "790 790 790 800 810 830 840 850 875 885 920 935 965 1010 1065 1135 1175 1200 1200" > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table
[G2 Android Development] GalaticStryder:
3.10 sound code

Merged 3.10 sound and Faux Sound control drivers from dorimanx and converted to my tree yesterday. Today, I did the Synapse part to select which app should control it. The actual Synapse controls will take some more time (they are old and don't fit).

See the collection post about it.

The build for D802 was dropped today in my Drive. Get while it's hot.

Use FauxSound app for now (it's selected by default). Synapse to STweaks code needs fundamental changes and I'll touch 'em without getting rid of the profiles support: LG stock, quality, loud...

All credits to [MENTION=2376110]dorimanx[/MENTION] for backporting it from neobuddy and recreating the Faux GPL controller for the LG G2. I just imported the code and the essential helpers (otherwise they wouldn't work properly on 3.4.y without FS code from 3.10).

Branch: sound

I've previously updated F2FS from latest upstream 3.4.y stable branch so it's more than just sound on latest incremental.

Time for testing...
[G2 Android Development] paul89rulez:
Grabbed! Testing now
[G2 Android Development] lunafag:
[MENTION=6175749]GalaticStryder[/MENTION], sound code works even better than what's built in crdroid(there's also a "headset high-performance mode" setting in Adiutor, that apparently even works), but speaker gain doesn't stick in fauxsound.
[G2 Android Development] xxoscarxx28:
F320 boots with Beta 7 stock voltage tables

Edit: Fast charge not available, too aggresive thermal throttling but in overall it is better
[G2 Android Development] GalaticStryder:
Thanks for the reply, it's a 2.2GHz table on BETA 7. It's a tailored version just for booting purposes. The thermal code is yet to be changed.

The GPL sound controller isn't the same as Faux for Nexus, dorimanx needed many patches for it to work. His firmware is stock LP and ours is CAF MM which may lead to some more possibilities on ROM side (PA) to extend the usage of it. The speaker sticks if you let the app running, doesn't stick on boot cause the driver resets the values to lge_stweaks controller (reg in/out) instead.
[G2 Android Development] xxoscarxx28:
Just another heads up, mpdecision hotplug still works, performs smoother and more battery-friendly than bricked hotplug... mpdecision's hard-boost to 1574 is non-existent (which is better)

I also noticed a drop in BogoMIPS, from 38.40 to 38.00 (38.40 with stock kernel), does this mean lower ips (instructions per sec.) for our cpu?
[G2 Android Development] Floodland:
Initial impressions with latest incremental for d802 are pretty good. Sound is a bit quieter, but it is way better than mm stock in terms of quality/response.

V4a is a good way to overcome sound amplification settings not sticking.

All the rest seems to be working really good. Keep up the great work!
[G2 Android Development] android extreme:
The latest incremental on resurrection remix is nearly perfect finally we can have a decent sound also on aosp rom :), the only bugs that i've found seems not(all) related directly to the kernel:

-if you set 1 to MMC clock scaling control(for a faster read/write operation) you will have an opposite effect(seems noticeabily slower also when you try to open the dialer).I think that only the description of the parameter should be changed here

-in synapse when you choose 4 compression streams on zram setting and exit from the application you can easily check that, when you reopen the app, the same setting was resetted to 1(if you need a log about that i will provide to you but in my opinion the issue seems easy to be fixed)

Furthermore i would ask to you if would be possible add Laziness and Ramp Thredsholt control on gpu side because i noticed that on aosp kernel the gpu frequency was more aggressively lowered that on dorimanx kernel.
[G2 Android Development] pipyakas:
Beta n7 running great on f320 RR 5.7.1, even with -50mv uv and I havent bumped into any reboot yet
[G2 Android Development] fuibauer:
Tried your latest Incremental on my D802 and it wont boot. It stucks at LG logo and reboot and stuck again. I forced some restarts but i wont work - tried nearly all 6.0.1 roms... Seems like i got a **** pro that cant handle the overclock :(
[G2 Android Development] GalaticStryder:
Can you plug your USB cable into your PC and see if it shows up when booting. Have you tried it on PA? Thermal manager on boot should be 2.5GHz~2.8GHz as per logcat. MSM limiter only changes to 2.2GHz on system boot completed. I'm working on this, might switch to a built-in protection in the CPU code itself.

Thanks for the info, did you try BETA 6? Trying to collect more studies on the 'hang on boot' errors for some users.
[G2 Android Development] pipyakas:
Beta n6 hang on lg logo for me, I dont know how to get more info about it :rolleyes:
[G2 Android Development] xxoscarxx28:
Seems like the problem is due to a fail-safe mechanism of the cpu that is being triggered due to the overclock. You can reproduce the "hanging" by setting your governor to performance then undervolting the cpu by -75 or more (must use the OC version)... After some time everything will lock up (hang)

What makes no sense is that the previous builds are working just fine despite being an OC kernel with 2.8 Ghz set on boot
[G2 Android Development] murok9042:
What exactly did you changed in governor and hotplug settings?

PS: Nevermind ?

Gesendet von meinem LG-D802 mit Tapatalk
[G2 Android Development] DvineLord:
going to try new d800 build without wiping dalvik/cache to see if it boots.

edit: didnt boot. wiped cache/dalvik and fixed permissions for the heck of it for a second boot still nogo.
[G2 Android Development] pipyakas:
How about using a aroma menu in the kernel installation that let user choose different OC levels, like in elementalx? :rolleyes: would that take a lot of time or it doesnt compatible with anykernel? :rolleyes:
[G2 Android Development] DvineLord:
please dont, half my screen doesnt work and aroma doesnt have usb-otg mouse support, therefore i cant flash anything aroma.
[G2 Android Development] Floodland:
Having the user to confirm voltage table while installing is not a bad idea, but Aroma is. Twrp for our devices does not get along with it.

But maybe, a simpler option: stick with LG defined voltages/frequencies for G2 (conservative values won't hurt) until boot finishes.
[G2 Android Development] blastagator:
AROMA works fine if the right version is used. However, I don't think AROMA should be used due to the fact it isn't really maintained anymore.
[G2 Android Development] thtkidsvm:
My d801 has PVS bin 2 and speed 1and it doesn't go under 730mv without rebooting and having issues. I see that under arch/arm/boot/DTS/msm8974 regulator the min mv is 500mv. Is this the reason my device doesn't boot when I compile the kernel under sound branch? Can I change that to the min mv my device can handle?
[G2 Android Development] GalaticStryder:
MSM8974 board DT config isn't just for the LG G2, 500mV is just a reference for this SoC. Even hammerhead (N5) can't handle -600mV without issues. The G2 has a much "better" panel, camera and other internals than the N5 has, so it demands more power. I gotta push some config changes to match the source code changes in audio, don't build sound branch yet. Though I'm also getting tough time fixing everything I can in PA device trees.
[G2 Android Development] thtkidsvm:
Oh OK, maybe that's why it doesn't boot. I'll wait for the next update though im eager to try it out. Beta n6 works great I don't think I have that issue with USB tethering anymore, I don't encounter any major issues from day to day usage. I'm thinking about changing my partitions to f2fs. Does beta n4 or n6 support f2fs or should I compile a kernel from the f2fs branch?
[G2 Android Development] GalaticStryder:
Totally supported on all versions, you'll get a performance jump when compiling f2fs branch plus more stability due to June/July patches "Kim" has made in the 3.4.y-stable tree. I don't backport 3.10 F2FS nor 3.18 as Dorimanx does, needs many other dependencies in MM and FS that I don't wanna get into - at least for Hipnose - since it's performing stable enough for all the effort I tried to put on it.
[G2 Android Development] YuvalHas:
I have the cm13 rom

Is that kernel supports a f2fs file system?

(TWRP F2FS)

What kind of Lamda version I have to installed? Beta or stable?
[G2 Android Development] khanjui:
Supports F2FS and i think latest beta will be good to go.