yashsingh1/xdaforums huggingface dataset:
[G2 Android Development] blastagator:
I have had this problem before and it drove me insane. What I ended up doing (because I couldn't figure out WTF the problem was, was to create a second folder with the kernel code and updated my scripts to basically copy <GITHUB_SOURCE_DIR> to <TEMP_WORKING_DIR> and then compile in the temp folder. When next build runs, delete <TEMP_WORKING_DIR>, copy the original source, and start again. This obviously seems like overkill, but I was so sick of the problem, I was satisfied just having SOMETHING that worked every time.

This is the rough code from a different kernel I was building:

#!/bin/bash

Root_dir=/home/greg/android/gits
kernel_src=$Root_dir/LGG2_TWRP_Kernel
build_src=$Root_dir/LGG2_Kernel-build
toolchain_dir=$Root_dir/toolchains/arm-eabi-4.9
dtbtool_dir=$Root_dir/toolchains

# Copy kernel to a build folder
cd $Root_dir
rm -rf $build_src
rsync -a --exclude='.git' $kernel_src/ $build_src
cd $build_src

make clean
cp arch/arm/configs/cyanogenmod_vs980_defconfig .config

make ARCH=arm CROSS_COMPILE=$toolchain_dir/bin/arm-eabi- zImage -j4

Upon looking in my scripts for last time I was building your kernel, I think I accomplished the same sort of "reset" using the following code:

#!/bin/bash

homedir=/home/greg/android/galatic

# Resync kernel to lambda source
cd $homedir/kernel
git clean -fxd
git reset --hard HEAD
git fetch origin lambda -f
git checkout origin/lambda
git branch -D lambda
git checkout -b lambda

# Resync anykernel to lambda source
cd $homedir/anykernel
git clean -fxd
git reset --hard HEAD
git fetch origin lambda -f
git checkout origin/lambda
git branch -D lambda
git checkout -b lambda

# Remove wallpaper change
rm -rf $homedir/anykernel/wallpaper

Of course, substituting whatever branch name you're doing. I'm honestly not sure if this was working or not, try my first suggestion if this doesn't do it.
[G2 Android Development] GalaticStryder:
Much thanks, there must be another alternative as it didn't happen on my previous releases.

When did you first encounter this issue? What distro was hosting the build?

I wanna collect all resources to complement my findings.
[G2 Android Development] blastagator:
I have always used BBQ Linux (a flavor of Arch). I don't recall when it started happening or if I ever had a time without it (I mostly build TWRP which builds the kernel as part of the larger compilation, and there was never an issue there). I just remember thinking there was some kind of cache that I couldn't find somewhere, and that compiled code must be getting included and not actually recompiled (reinforcing this, it seemed that all builds after the first build were significantly faster).

Really don't know where the problem is/was, but rsync didn't take too long on my SSD, so once that worked I never bothered to go back and investigate further.
[G2 Android Development] bamonkey:
I'm actually glad i have slept since trying to compile. I noticed that when i opened the zip file I had made it was missing the zimage and dtb files. Looking at how how the anykernel script was supposed to work i was kind of confused why this was happening. jump to me just now waking up and seeing the latest posts here. I can resync sometime later at work and try on d800 again....but maybe between the both of you a build on my device will have already been done. Just dont want to waste time if you get what im saying :silly:

sorry if what i say is confusing Im obviously very new to compiling kernels, using toolchains, etc. I do understand the basic structure of what 'should' be in a kernel and a general degree of why *been messing with this stuff since the original galaxy S1*

nevermind: missing liblz4-tool...more stuff im finding as I go along. nothing to see here people move along
[G2 Android Development] bamonkey:
Alrighty! Zimage successful but now it looks like dtb is being a pain. looking through the log I see:

Found file: msm8974-v2-g2-att.dtb ...
Version: 1
...skip, incorrect 'qcom,msm-id = <' format
skip, failed to scan for 'qcom,msm-id = <' tag

after this it begins to search the subdir in arch/arm/boot/dts/ till it basically gives up

began the search and even found something interesting here:

http://xdaforums.com/showpost.php?p=49218060&postcount=894

not sure if on my side but just a heads up where im at with this right now.

edit: SUCCESS! did a couple things but now have latest booting on D800.
[G2 Android Development] chenweifei:
d802？？？
[G2 Android Development] bamonkey:
since your D802 i would say use the one posted just the other day since its more "official"

http://xdaforums.com/showpost.php?p=68730528&postcount=1604

i wouldnt have many changes to what was built by the man himself:highfive:
[G2 Android Development] GalaticStryder:
Since you're here, could you complement the Ubuntu/Debian instructions with the resources you needed in the readme.md, the Fedora ones seem alright the libs were already pulled out-of-the-box mostly.
[G2 Android Development] bamonkey:
sure can. I've got about 30 minutes left before i leave the office so let me wrap it up here and ill do it on my machine at home. ill just edit/add under the ubuntu part and 'hopefully' i remember all the differences it took. it may take another person to run through it again just to make sure OR ill make a duplicate VM and see if i can from a fresh image. just PM the new readme.md to you or paste it here?

edit: just the changes here is what i meant NOT the whole thing

edit edit: pull request was added because why not? https://github.com/GalaticStryder/kernel_lge_msm8974/pull/3
[G2 Android Development] GalaticStryder:
Thanks, but I'll cherry pick that due to force pushing some git --amend on the ccache guide that I've got right now. I don't if it fixes the issue but forces the compilation of all nodes if you clean it (in script) if the variant is not the same.

There's also the dtc package part that you need with the new dt.img from CM13, I'll add that: https://www.archlinux.org/packages/community/x86_64/dtc/

That's how we roll:

http://i.imgur.com/dswZxDH.png
[G2 Android Development] GalaticStryder:
Time's over, let's test BETA 3

It's celebration time, the Infinito release is shaping the stable conditions on its own, finally. After a lot of hard work, I'm getting something to be considered and tested today: BETA 3.

I've spent a great time trying to figure out the new fantasy behind a couple bad builds, it was all about ccache fuc**** me up, now it's partially solved after today's tests.

See here: https://github.com/GalaticStryder/kernel_lge_msm8974/issues/2

Now, let's put the name in the woods.

1. The kernel finally has a release schedule and automation, it's a two-week schedule for BETAs regardless the name of the release.

2. The kernel has hybrid support for marshmallow and nougat, so I added the Android version to .zip name.

3. Incremental builds are now experimental to cause less confusion.

4. I'm using the Github interface to track issues, releases, and tags on the fly per code base.

Download/Information: https://github.com/GalaticStryder/kernel_lge_msm8974/releases/tag/IB3

The release page is populating during runtime and uploaded manually, so it will populate with all variants during the day.

Warning:

There's gonna be an issue or missing thing here and there but the essentials are put to test with this BETA. Remember, dirty flash your ROM to ensure the init scripts and fstab are untouched, then flash the kernel and wipe caches to debuild dex2oat inodes. This will ensure maximum stability out-of-the-box due to non-conflicting kernel inits.
[G2 Android Development] TSLNL:
You made a spelling mistake (marshmallow) in the file names, though..

Anyways, awesome work once again!
[G2 Android Development] GalaticStryder:
Thanks, I was rushin' and forgot that. Fixed: https://github.com/GalaticStryder/kernel_lge_msm8974/commit/df6f4e55bd7ae6e9625cdc347e2011bf231acae2
[G2 Android Development] errikosd:
First of all thanks for the great work!

With BETA 3, I have really low volume on the speaker and I can't seem to be able to control the volumes at all (tried with Synapse, FauxSound). They keep sticking to their default values. I am on AOSPA.
[G2 Android Development] GalaticStryder:
Synapse implementation is quite old and I was going to remove it in order to use STweaks for a couple drivers like this one and fast charge.

If you go to /sys/kernel/sound_control_3/

You can change the lge_stweks_control parameter to 0 manually and set Quality preset in the app. I didn't test it on AOSPA though but it has worked quite good before (H).
[G2 Android Development] rigok9:
BETA 3 on Ls980, no touch and boot problems with this release. Everything else seems to be working fine. Thanks for your time and efforts.
[G2 Android Development] GalaticStryder:
Thanks for the information, if you find anything strange, report. For now, I've only found one issue after all this week which is the CPU getting stuck on 1.2GHz after some rebooting, though it can be fixed just by settings the values again.

This seems to be the only problem/issue as in this release and some missing UKM stuff that are for H release yet.

EDIT: Updated post one to include that bug + how to workaround it for now. I'll fix it in the next release... Also thread updated to Infinito BETA 3 (partially) there's a lot to write...
[G2 Android Development] Dimberr:
Hi, thank you for your work!

Should I put suspend max or min frequency to the desired frequency like 2.2GHz?

And am I get I right, that 2.2Ghz is actually 300ghz? You mentioned that it is opposite
[G2 Android Development] guilledoc1:
Why when installing it change the wallpaper? Sorry if silly question but sometimes it can be a little annoying

Thanks for your hard work
[G2 Android Development] GalaticStryder:
Change this line to zero in the zip file.

Yes, the driver had this bug before and I forgot to patch it :crank: Just put the suspend as the normal frequency for now.
[G2 Android Development] ig_df:
Settings with synapse does not stuck on boot. Why is it so?

We haven't busybox out from the box with this kernel? I'm using last Infinito Beta 3 with RR rom on LS980.
[G2 Android Development] GalaticStryder:
We actually have three busybox binaries, two in the device and another one for the installer. After you flash it, the Synapse cache will be constructed and odexed in memory. That was fine in LP/KK but it is abnormal and not supported on marshmallow SDK leading to exec issues during app runtime on dex2oat process.

So, resuming the answer, you'll need to recreate the cache manually inside the app by tapping the Clear Synapse Data button and then restart the app with/without the boot error message to adjust your settings. After that, if you reboot the next time it will timeout the ART runtime verification (takes 2min to do so) and apply the settings just fine.

Sounds a little bit weird but it works that way and logcat confirms this. It's always good to create profiles to recover your settings as well.

You just need to that once after all (most likely) after reflashing a kernel update that causes the Synapse cache to freak out. Just do the process of clearing it again and put your settings on top.
[G2 Android Development] ceikokitkat:
Sorry, but I can't find this button in Synapse. Where it is?
[G2 Android Development] GalaticStryder:
Under tools, Clear Synapse Data. Press it, the app will open again, just go to tools and Restart Synapse. Press ok on the message dialog if it appears, and tweak what you want. Export the config at the last page with some name to apply it the next time you need it.

If you reboot the device, it will do what I said earlier about the timeout time to apply the settings and will restore those settings.

OBS: BETA 4 is online at: https://github.com/GalaticStryder/kernel_lge_msm8974/releases/tag/IB4
[G2 Android Development] ig_df:
New beta 4 version now without bugs with cpu stuck freq.? If you've solved previous problems, i'll wait a lot for ls980 version.
[G2 Android Development] JuubiV1:
Don't know what happened but after flashing BETA 4 my data partition was wiped. It's not a big deal for me cuz I got backup but it shouldn't happend I think.

I'm using AICP and I dirty flashed it cuz of update. Cleaned dalvik and cash than flash kernel and it booted fine but I found out that my data partition was wiped.

And for sure I didn't wipe it in TWRP.
[G2 Android Development] GalaticStryder:
Infinito BETA 4

Hi, guys.

Just a quick release here, face it as a bugfix update mainly. Though there were actually more changes that dorimanx is reserving for his next release and that I've put on this BETA for testing as well.

The primary objective was to fix the MSM limiter callback and it's done, I've split the suspend and resume registers as I did previously: https://github.com/GalaticStryder/kernel_lge_msm8974/commit/bf6a9804267090d3eb744bf4179fadf8bb98f860

It makes more sense that way and thus removes some redundant is this really suspended? questions from the driver, making it a little very little, nano little, pico little faster.

The second one was to update the driver to show the governor load in the limiter interface, this can help to see if the governor is being efficient or not by comparing real CPU load against the governor load.

The third one didn't exist, but as I've seen some new changes from dorimanx I decided to bundle them to help with testing... In the middle of those changes I had to recap the RMNET structure and I did so. It's now using extended IOCTL with register/deregister support to be tested.

More changes in the changelog.txt archive that you can open on a terminal emulator with cat command or by navigating with any file explorer to /sbin/changelog.txt.

This and all new releases will now use the Github framework because I can tag and release on the fly as I code and build.

There's always an introduction to which variants the release covers, a quick introduction to the changes and the downloads [A-Z] in the bottom. Plus the ability to download the source code in a tarball or zip file, don't download those files, it's just a bunch of code! If you wanna get into kernel and development in general, read the readme.md file.

BETA 4 release: https://github.com/GalaticStryder/kernel_lge_msm8974/releases/tag/IB4

All releases: https://github.com/GalaticStryder/kernel_lge_msm8974/releases

Before you ask, Pre-release stands for the BETA stage, this was added by Github.

Tell me what you think about this new "download center". It's better for me...

#!/bin/dev

The lambda-devel branch is already compatible and running GGC 6.1 compiled by master dorimanx. See attachment.
[G2 Android Development] Indiant:
Great kernel, I like it very much.

I use Beta-N4-d802-06242016, because all of the newest have a bug.

When I push ADB over network tile the phone restarts.

0624 was the last working version without this bug.
[G2 Android Development] aleasto:
Is UV working correctly? I don't remember ever having a stable -50 UV but seems stable here, latest beta
[G2 Android Development] boyheadkick:
1. Do we have a QnA thread for this kernel?

2. Is it fine if I use Kernel Adiutor instead of Synapse? I'm running RR on my device and it has Kernel Adiutor built in to settings and I'd like to take advantage of that. I don't do anything crazy with my config anyway.
[G2 Android Development] alexx_kidd:
Yes ,of course
[G2 Android Development] aleasto:
I don't really see drawbacks of UV as long as it's stable. Was just asking if it is correctly implemented, since in previous attempts -50v looked to make my phone reboot more often(i still was using steps of 25, if I recall correctly quite some time ago anything but that wouldn't apply), but maybe it just wasn't related at all.
[G2 Android Development] Floodland:
Congratulations on beta 4! State of the art kernel. It is working awesome with Orion 2.6.1. I had to tweak bricked hotplug a little, for it to avoid switching core 1 on and off without reason, but so far it is working marvelous
[G2 Android Development] blastagator:
Successful install on d800. Yay! Excellent work.

Have you considered getting rid of modules? Newer android versions did away with them. I only think of this since I saw the complainy install script message:

Base ROM doesn't support modules, unfortunately...

I also ran lsmod to confirm nothing is loaded after boot.

Maybe just change all of the config lines with =m to =y and disable:

CONFIG_MODULES=y

Although, frankly some of them could probably just be disabled instead of converted from =m to =y
[G2 Android Development] GalaticStryder:
Don't be afraid of the message, I've added this just to tell the user not to run insmod on CyanogenMod as an example, because it doesn't have modules compiled in kernel and not bundled in the ROM.

I've made this possible on AOSPA kernel to use exfat-nofuse and insmod it on boot.

It's just a warning as I said.

https://github.com/GalaticStryder/a...mmit/5686ebc559c90c1ff74d4232e15ac44b7a8764fa

I need some modules because of my work, mainly garmin module and its deps. Same goes for CIFS/NFS filesystem that may be useful for someone doing IT job...

The modules are very lightweight and won't affect anything if you don't load them. I just don't wanna create yet another config file for AOSPA and CM...

This was introduced for AOSPA mainly:

https://github.com/GalaticStryder/kernel_lge_msm8974/commit/92845e644fb41624bf2111041650fa3b9fefea75

This one converts some =y driver to =m like the Xbox controller, making the basic kernel yet lighter and faster to boot ;)

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

The problem as of now is that CM and ROMs that don't enable modules will fall apart to have this very cool kind of support that I haven't seen anywhere and that some people will eventually need.

Linux mainline is 60% composed of modules on x86_64 machines, if Linux supports them then it's a question of honor to keep them... Also, I know they keep them because the x86_64 kernel is more generic but it doesn't mean they should be disabled on a target based kernel like ours.
[G2 Android Development] blastagator:
I was browsing the commits earlier and saw that. Makes sense now that I know your work situation. So far so smooth in my testing :) Had to flash phh superuser (magisk version) twice to get it to work (no clue why) but other than that, nothing odd so far!
[G2 Android Development] Hiyaslalabs:
Working very smooth with XOSP! Fast charging and battery is fairly good it does still overheat when gaming. Does synapse work? Otherwise what alternative can I use? Thanks.
[G2 Android Development] matteo0026:
It's normal that phone goes overheating a little bit... To 65-70° of CPU and 40 of battery is all ok... If goes up, there are some problems i think...

[MENTION=5422660]Galactics[/MENTION]tryder i'm trying infinito beta 4 with aicp and it's good, but not perfect, expecially side battery juice... Yesterday i got 2:50 hrs of sot from 96% to 21%... 60% in 3g/4g
[G2 Android Development] GalaticStryder:
That's normal, I need to convert some values to more conservative ones in bricked hotplug. I'm working on the blu_plug right now, though. Let's see if I can make it default on BETA 5 for testing purposes. Otherwise, I'll need to take a closer look at bricked code to see why it's spiking so much.

CPU wise, I'll tune interactive to be more conservative and make it default once impulse now has a GPU boost framework to put the values at 320MHz as the stock kernel does instead of my 200MHz decision - it saves a good battery, though.
[G2 Android Development] SREEPRAJAY:
Yet another great release...

Exodus plus the Latest beta

[MENTION=6175749]GalaticStryder[/MENTION] bravo sir...great work

There is still some battery left...first charge...so I think it can be better next time

Edit- six hours and twenty six mins....and nineteen left...need to charge now
[G2 Android Development] Floodland:
Sounds great. The way I minimized the spikes was setting the idle frequency to 1728mhz (default was 422mhz, way to low). Cpu 1 is still plugged without significant load, but IMHO, much better...
[G2 Android Development] szabyka95:
How old is your battery? Which CFW are you using?
[G2 Android Development] SREEPRAJAY:
Battery is around one year and two months...I use kernel adiuter to manage multi cores.. [MENTION=6175749]GalaticStryder[/MENTION] recommended settings actually...
[G2 Android Development] rabies876:
Voltage table I'm using lord Boeffla
[G2 Android Development] boyheadkick:
I remember lord boeffla from my galaxy s3 days

Is this table stable for our device?
[G2 Android Development] rabies876:
Using it for the pass two days without any issue with Exodus ROM and it like motion of water SMOOTH
[G2 Android Development] GalaticStryder:
Just something to consider, the OnePlus One (bacon) uses the MSM8974AC (aka Pro version of our SoC) with 300MHz-2.5GHz frequency range. This SoC has its own voltages for its hardware, it's close to what we have but it's not what we have, take in consideration that LG internal components are usually better and thus will consume more of the regulator supplier, when you need burst it will panic the driver if it's too low. The N5 can go almost 600mV for its first frequency that can be tailored down to 266MHz without any reboot... this won't happen here.

For the better scaling and hardware life, keep them as is with barely minimal changes.
[G2 Android Development] Master Tenzing:
Where can the recommended settings be found?
[G2 Android Development] metteduch:
[MENTION=6175749]GalaticStryder[/MENTION] do you never use LG stock based ROMs? Just curious as I can imagine stability, performance and battery would be insane with such kernel on a clean LG ROM :)
[G2 Android Development] SREEPRAJAY:
Found by using a little bit of search from this FORUM....

If I remember right...it used to be around the 145-150 pages in this thread... [emoji12] [emoji6] [emoji4]

Please use the Q&A for such type of posts...Please
[G2 Android Development] zizuka:
damn what do you even do with your phone when you use it? you got 46 mins extra screen on time in just 6%? crazy
[G2 Android Development] :
Phone rebooted twice on latest infinito release on f320 variant using bliss 6.4, i forgot to pull logs. I'll pull logs if it will happen again.
[G2 Android Development] GalaticStryder:
I've never had a random reboot on D802 for the past months... actually, the only freeze/reboot that I can see is triggered from adb upon USB mode switching but it's not a deemed issue for me and it's prone to be fixed sooner or later.
[G2 Android Development] Romagnolo1973:
In stock there is the best kernel ever released, by master Dorimanx. GalacticStryder work is inspired by Dori kernel and when compatible it use some Dorimanx blobs, so we can call Infinito as the dorimanx kernel for non stock roms.
[G2 Android Development] android extreme:
[MENTION=6175749]GalaticStryder[/MENTION] random reboot opening chrome on resurrection remix rom(on a clean flash obviously)
[G2 Android Development] GalaticStryder:
Well, Chrome opened a cache instance and F2FS freaked out on get_dirty_pages. I was aware this BUG has got back after the latest F2FS updates on 3.4.y but it's now more "rare" than before.

I'll see if I can workaround this issue for now until Jaegeuk Kim patches this issue.

Look at here: https://git.kernel.org/cgit/linux/kernel/git/jaegeuk/f2fs-stable.git/log/?h=linux-3.4.y

Compare with here: https://github.com/GalaticStryder/kernel_lge_msm8974/commits/lambda/fs/f2fs

All caught up, all I can do is wait for now and recommend people to use EXT4 until he sorts that out or until I patch it on my on.

Actually, he fixed this with this change: https://github.com/GalaticStryder/kernel_lge_msm8974/commit/76c11dbe49c18b92c854afb90915625f1c4b38f1

And introduced the error back again in: https://github.com/GalaticStryder/kernel_lge_msm8974/commit/917060b6e08dc3ccfc4231023611a2d4f23150b0
[G2 Android Development] armivzla:
I use f2fs in Data and Cache, and it works perfect.

Not if internally is doing or creating some kind of cycle error. But Until Now, it has worked fluid.

The only thing I changed is the governor to Interactive. I feel better than "Impulse"