yashsingh1/xdaforums huggingface dataset:
[Android General] Soumy1234:
What I'm trying to build: Resurrection Remix Pie for gprimelte

Turns out I just forgot a dependency folder (/device/samsung/qcom-common). I also deleted lineage.mk and pa.mk, since there was a rr.mk and edited the lineage.dependencies file to rr.dependencies and add rr_gprimelte to the lunch menu. But now when I run ". build/envsetup.sh", "lunch", "(lunch number for rr_gprimelte-userdebug)" and then "brunch gprimelte", this is what I get near the end (sorry if it's not very clear, I used the "command > Output.txt" feature to get all of the output as it gets cut off and there are way too many characters....)

Warning (reg_format): "reg" property in /soc/i2c@21/qcom,actuator@18 has invalid length (8 bytes) (#address-cells == 2, #size-cells == 1)
Warning (reg_format): "reg" property in /soc/i2c@22/qcom,eeprom@50 has invalid length (8 bytes) (#address-cells == 2, #size-cells == 1)
Warning (reg_format): "reg" property in /soc/i2c@21/qcom,actuator@18 has invalid length (8 bytes) (#address-cells == 2, #size-cells == 1)
Warning (reg_format): "reg" property in /soc/i2c@22/qcom,eeprom@50 has invalid length (8 bytes) (#address-cells == 2, #size-cells == 1)
Warning (avoid_default_addr_size): Relying on default #address-cells value for /soc/i2c@21/qcom,actuator@18
Warning (avoid_default_addr_size): Relying on default #size-cells value for /soc/i2c@21/qcom,actuator@18
Warning (avoid_default_addr_size): Relying on default #address-cells value for /soc/i2c@22/qcom,eeprom@50
Warning (avoid_default_addr_size): Relying on default #size-cells value for /soc/i2c@22/qcom,eeprom@50
Warning (avoid_default_addr_size): Relying on default #address-cells value for /soc/i2c@21/qcom,actuator@18
Warning (avoid_default_addr_size): Relying on default #size-cells value for /soc/i2c@21/qcom,actuator@18
Warning (avoid_default_addr_size): Relying on default #address-cells value for /soc/i2c@22/qcom,eeprom@50
Warning (avoid_default_addr_size): Relying on default #size-cells value for /soc/i2c@22/qcom,eeprom@50
make: Leaving directory '/home/android/RR/kernel/samsung/msm8916'
ninja: build stopped: subcommand failed.

[0;31m#### failed to build some targets (11:07 (mm:ss)) ####[00m
[Android General] DJABHipHop:
[MENTION=7026648]AlaskaLinuxUser[/MENTION] I like your Just Notes applications but I think applications could use new look that more more polish & professional, applications settings need a more polish & professional look plus email syncing capability allow user to access notes across multiple device using there existing email account like Yahoo, Gmail, Hotmail & iCloud would be perfect along with rom support so user can add to there rom as system app, better theme selection and dark mode as well along with pixel app icon.

JustNotes

New Just Notes UI
[Android General] AlaskaLinuxUser:
Well, the great thing about open source apps, is that you are allowed to take it and change it. :good:
[Android General] DJABHipHop:
Any lightweight android ide for mac
[Android General] AlaskaLinuxUser:
Hanging Up The Gloves

Hey everyone, well, the video says it best, so here it is:

https://www.youtube.com/watch?v=fKSiVL7nIqM

Essentially, due to changes in my schedule and work, I'll be hanging up the gloves on the video tutorial series.

Feel free to watch through any of these videos though, as there is still a lot of material. This thread will also stay open for people to ask questions and discuss the videos, however, my involvement in answering those questions is going to come to an end.

I really hope that you have enjoyed the series, and that it was helpful to you in your Android career!
[Android General] _JaSoN_:
[MENTION=7026648]AlaskaLinuxUser[/MENTION] thanks for all your videos and for all the help learned a lot from you thanks for all that

wish you all the best :)
[Android General] Nathan Miguel:
A6020 kernel update help

I've been researching on the kernel of my "A6020" device and saw that many github branches merged with the branch "caf / LA.BR" in version 3.10. But as my device was made in 2016 I wanted to do an update of version 3.10 (reported in the branches) to 3.18, so that I add the latest security path, firmware update, and processing optimization, just as it is done in the latest Linux kernel, such as 4.20.

I'll be putting the kernel link from factory in my github, just select my first commit, and just below the branches that I would be interested in merge with it.

But The questions is, which one would be the most recommended merge to my device? Keeping in mind that I want to by less the 3.18 already that 3.10 lost the LTS

A6020 original kernel: https://github.com/nathanmiguel123/android_kernel_lenovo_msm8916

Branch for merge:

https://kernel.googlesource.com/pub/scm/linux/kernel/git/stable/linux.git/+/refs/tags/v3.18.136

https://source.codeaurora.org/quic/la/kernel/msm-3.18/tree/?h=LE.BR.1.3.1_rb1.75 - Branch LE.BR.1.3.1_rb1.75

https://source.codeaurora.org/quic/la/kernel/msm-3.18/tree/?h=LA.BR.5.6

https://android.googlesource.com/kernel/common/+/refs/tags/ASB-2019-03-05_3.18 - security update

https://android.googlesource.com/kernel/msm/+/refs/tags/android-9.0.0_r0.66

https://source.codeaurora.org/quic/la/kernel/msm-3.10/?h=LA.BR.1.3.7_rb1.9
[Android General] prabhjot368:
hi sir thanks for all of your efforts .. but can you guide me through making device tree for exynos processor .. someone said that ther are no hals available for exynos,, so i want to ask how to get hals for exynos is it possible? or not? or the process is same as snapdragon to create dt?
[Android General] DJABHipHop:
I'm trying to make a notes app that sync with my email similar to apples nots apps on iOS & MacOS does anyone have a template in can use to get me going in the right directions?
[Android General] krishV:
Sir, need help with notification text is in black when i turn on bark theme how to fix it
[Android General] nalas:
Hi guys.

I have Samsung galaxy s7 with Oreo, on Ga laxy Note Fe is out Pie ...this phones has the same firmware and Im trying to port kernel from Note FE to S7...

I used kernel source from S7 and Ramdisk modded from Note Fe but after install Ive got bootloop on Samsung logo..all is on TouchWiz, no aosp.

What you suggest for to do? I have to edit source linux too?

Big thx for answers.

Cheers.

Wysłane z mojego SM-G930F przy użyciu Tapatalka
[Android General] Abhishek17599:
Log : https://del.dog/owovumetej.pl

Can anyone help?... I am building lineage os 16 unofficially
[Android General] lucki1000:
Hello,

I want to know in which file i can change this path:

kernel/motorola/msm8937/arch/configs/cedric_defconfig to kernel/motorola/msm8937/arch/arm64/configs/cedric_defconfig

The error line:

ninja: error: 'kernel/motorola/msm8937/arch/configs/cedric_defconfig', needed by '/home/..../AndroidSource/lineage16/out/target/product/cedric/obj/KERNEL_OBJ/.config', missing and no known rule to make it

Thanks for any help.

---------- Post added at 15:13 ---------- Previous post was at 15:06 ----------

What happend if you use the normally boot.img of S7 Note and change the kernel in the boot.img with your S7's ?
[Android General] nalas:
Now is oki...

I had to copy some drivers from Oreo to PIE kernel source from S7....WiFI, BT, NFC and now is good.

Thx for interesting :)
[Android General] DJABHipHop:
How do I rebrand the LineageOS setup wizard when there no image for the logo
[Android General] Pavel Alm:
Anyone here can tell me how to build a 64 bit kernel for my A6+
[Android General] herontrott:
Thanks
[Android General] reachomk:
Thank you so much AKLU!

Your videos on device trees have helped so much and I look forward to learning from the Kernel Mod videos!

Hope you get back to android soon!

Thanks again!
[Android General] AlaskaLinuxUser:
Just a quick update: I'm working on some HD videos for Android Pie! Stay tuned!
[Android General] SnowFuhrer:
Awesome, I want to build an android pie rom for my phone!
[Android General] AlaskaLinuxUser:
That's great! Do keep in mind though, this video series covers basic building, such as building a ROM for a phone that already exists. Building from scratch, or upgrading from one android version to another ( if it has not been done before ) is a more advanced topic, which will be covered in the intermediate to advanced video series. Be sure to check the link in the op for the more advanced topics series. :good:
[Android General] nickrule1896:
Hey, I'm currently trying to build a custom kernel for my S7, but right now it seems like i can't even make clean the kernel source? I downloaded the kernel source off samsung's page and pointed it to a toolchain correctly. I don't know what I'm doing wrong? I am suspecting that the kernel source is missing some files. And when i try to download some other version of the kernel source, it compiles properly, but I only get an Image.gz and no dtb files as mentioned in many guides?

scripts/Makefile.clean:17: drivers/input/touchscreen/melfas/mms100s/Makefile: No such file or directory
make[4]: *** No rule to make target 'drivers/input/touchscreen/melfas/mms100s/Makefile'. Stop.
scripts/Makefile.clean:92: recipe for target 'drivers/input/touchscreen/melfas/mms100s' failed
make[3]: *** [drivers/input/touchscreen/melfas/mms100s] Error 2
scripts/Makefile.clean:92: recipe for target 'drivers/input/touchscreen' failed
make[2]: *** [drivers/input/touchscreen] Error 2
scripts/Makefile.clean:92: recipe for target 'drivers/input' failed
make[1]: *** [drivers/input] Error 2
Makefile:1251: recipe for target '_clean_drivers' failed
make: *** [_clean_drivers] Error 2
[Android General] AlaskaLinuxUser:
Hi nickrule1896, welcome to the thread.

I need a little more information to help you.

First, have you watched my video series, particularly the part about kernel work?

Second, what guide are you following? (links help a lot)

Third, why are you running make clean before you build? Or does it not build and then you are trying to make clean? Is that part of the guide?

Fourth, what source are you using, and what other source have you tried? (links help a lot)

Fifth, and final question, I'm guessing you are building as a stand alone kernel, or are you building in a ROM source code tree, such as Lineage or AOSP?

Hopefully those answers will shed some light on how to help you further.
[Android General] nickrule1896:
Hi, thanks for the prompt reply! I really do need the help :(

1. I intend to do so later on today, as it seems more in depth as compared to the other guides I am following!

2. https://xdaforums.com/chef-central/android/guide-how-to-build-android-kernel-t3654336

https://xdaforums.com/android/software/guide-noob-guide-building-custom-kernel-t3775494

https://xdaforums.com/android/software-hacking/reference-how-to-compile-android-kernel-t3627297

and some others which roughly say the same things. What I gathered from all these is that I will need to get the kernel source from Samsung's open source website, a toolchain (I downloaded different ones), point the Makefile to the toolchain, perform "make ARCH=arm64" and hope that I get an Image file in the boot folder.

3. I believe these guides I'm following actually recommend me to do so before building.

4.. The official one that I used is "G930FXXU2DRAG" from the Samsung OpenSource site. I have also used some others cloned from GitHub like https://xdaforums.com/s7-edge/development/reference-els-exynos-linux-stable-3-18-t3771958, and some of the following that I have forked https://github.com/nickmx1896?tab=repositories.

5. Correct me if I'm wrong but i think I am building a standalone kernel, or at least that's what I want to do and have been doing (I hope) :fingers-crossed:

In fact, I have managed to build Image.gz files for some of the kernel sources, but the only ones that I have managed to boot successfully is the SuperStock kernel source (which is already a custom kernel itself), but reboots every 10 minutes or so. The rest either hangs with "Seandroid Enforcing" error or just hangs at the first boot splash screen. I am not sure which part of the process is screwing me over. Perhaps it is the part where I'm using Android Image Kitchen?
[Android General] AlaskaLinuxUser:
Android Pie video tutorial is out! The OP has been updated with links, and here they are as well.

Remember, this is a basics tutorial, so this only shows building for a device that actually already exists in the AOSP rom source, the marlin. I do have an emulator video at the end where we check out Pie briefly, so keep an eye out for that.

I am uploading all the videos for that now, it might take a little while to finish on my slow internet.

Downloads!

New HD Pie videos:

MP4 Video GitLab:

https://gitlab.com/alaskalinuxuser/HD_compile_android_pie_videos

Clicking on a video in GitLab will allow you to watch it online.

MP4 Video Downloads:

https://gitlab.com/alaskalinuxuser/...ster/HD_compile_android_pie_videos-master.zip

This download is rather large due to the multiple videos.

Youtube links:

New HD series (including Android Pie) :

https://www.youtube.com/playlist?list=PLRJ9-cX1yE1m8k9gztsQnnXDg1G4X1f6z
[Android General] nickrule1896:
Hey, thanks for the suggestions! I have watched the video on the standalone kernel building, which I believe is what I'm currently doing. Am I right to say that non-standalone kernel building means building together with the rest of the android system/firmware?

As for the toolchains, I have tried both 4.8 and 4.9 versions from Google. Both gave me the same make clean problems as shown below. With regard to the flags, I believe I have set them properly by editing the Makefile directly. (I also tried the export method which I believe is the same thing).

scripts/Makefile.clean:17: drivers/input/touchscreen/melfas/mms100s/Makefile: No such file or directory
make[4]: *** No rule to make target 'drivers/input/touchscreen/melfas/mms100s/Makefile'. Stop.
scripts/Makefile.clean:92: recipe for target 'drivers/input/touchscreen/melfas/mms100s' failed
make[3]: *** [drivers/input/touchscreen/melfas/mms100s] Error 2
scripts/Makefile.clean:92: recipe for target 'drivers/input/touchscreen' failed
make[2]: *** [drivers/input/touchscreen] Error 2
scripts/Makefile.clean:92: recipe for target 'drivers/input' failed
make[1]: *** [drivers/input] Error 2
Makefile:1249: recipe for target '_clean_drivers' failed
make: *** [_clean_drivers] Error 2

My latest attempt was to try and build a kernel for Galaxy S7 Android 7.0. I downloaded the kernel source (G930FXXU2DRAG) off the official site. Right now the built image is unable to boot on my phone (stuck on the splash screen). I'm wondering if it is because I am not using a correct kernel base? My phone's build number indicates G930FXXS2DRAB, baseband G930FXXU2DRA9 (sorry I'm not sure which to look at).

Oh that's nice! Food here is awesome :D
[Android General] AlaskaLinuxUser:
Great!

Question, if you skip the make clean step, what happens?

Make clean is used to clean the directory of build files created while building. But you have not built anything yet, so you don't need to run make clean. I only make clean after building something and making changes, before running build again.
[Android General] nickrule1896:
I tried that too, build succeeds, but still unable to boot. I'm not sure which part am I doing wrong :confused:
[Android General] AlaskaLinuxUser:
Okay, good. One thing I'm positive about is that make clean is not causing your issues.

After you flash your new kernel, your phone reboots. You should try to grab the last_kmesg file to see what happened. So do this:

Flash new kernel, then let it reboot.

When it reboots, go to recovery.

Look for these two files:

If you have either, use

# cat (file path file name) > /sdcard/kmesg.text

So you can see what went wrong.
[Android General] nickrule1896:
You mean I can do this even though the phone does not get pass the boot splash screen, because it doesn't even enter the boot animation. So I should just flash the kernel, reboot system, and when it hangs I can reboot into recovery to grab the required files?
[Android General] AlaskaLinuxUser:
That's the idea. :good:
[Android General] nickrule1896:
I got these two files, one is for the kernel that is bootable but reboots randomly, and the other that is stuck on splash screen. I'm not sure which part of the file I should start looking from?

Unbootable: https://pastebin.com/N9A3G04A

Bootable: https://pastebin.com/ipP2kjmu

I took roughly the last 400-500 lines of code. Anything in the files I should take note of? Anyways I think I'm quite confident in the building process of the kernel, just that i can't get it to boot currently. I'm pretty sure I used AIK correctly as I did the same repack method for the bootable kernel. But then again, this bootable kernel reboots randomly :confused:
[Android General] AlaskaLinuxUser:
Great! I'm glad you were able to pull the files.

Now you have something tangible to work with.

Generally, you need to look for these key words: err, error, fail, failed, reboot, shutdown, bug, kernel bug, can't, not found, panic, and recovery.

The reason that it is difficult to give you something specific to look for is that there is no standard. The debug messages you see are written by programmers and can be found throughout the kernel source code that you built with.

In the unbootable logs:

By line 340, it is too late, the issue is already out of control, everything is shutdown, and it is sending the command to reboot now. This is a good place to work backwards from.

As you scroll up, notice that everything is shutting down. This is everyone getting ready to abandon ship. (lines 264,267,268, etc.)

Notice line 244-248, the system remounts UserData file system in an "emergency" to r/o or read only.

The only odd errors are the mmcqd ( responsible for reading the SDCARD ) having issues with reading, and there was this fail:

<3>[ 289.827385] [3: init: 1] exynos_smc_read: ERR! read Fail: 11

But that happens rather late in the game, so I'm not sure. Perhaps there is something earlier in the logs that needs review?

I agree that you have the building down, as you can build one kernel that does boot. I think it may be wise for you to do one of three things:

1. Download LineageOS of the appropriate branch (you are doing Oreo right? so LineageOS 15) and build for your device. Now work with that kernel. This will give you the right flags, the right source, and the right setup to build your kernel properly (for sure). Does the rom flash and work? Then you can then use the zImage and put into your extracted boot image and try that.

2. Download the LineageOS kernel for your phone, and the LineageOS device tree for your device so you know which defconf file to use. Build that kernel stand alone and see if it works any better.

3. Post under the Q/A section of the S7, or in one of the kernel guides you are following with your specific questions and issues for more specific help from the S7 community, or more specific help for kernel development from the guides you are reading. You could possibly post on the thread for the kernel that you can build, and *politely* ask that developer to assist you with how you build his/her kernel.

Unfortunately, I cant readily see the problem, so I think you need specific help. My opinion is that your source code or flags are not right, but I don't have an answer as to what is the problem. If it was me, I'd go with option #1 first.
[Android General] Rawwrius01:
Hey, It's me again :D the one with the not working wifi. My device got a new kernel source and I put my compiled image in the stock boot.img ( unpacking replace the boot.img-zimage with my image and repack) now the WiFi is working. I am very happy about that :D. So I started to mod the kernel. My goal was to OC the weak cpu and happily I found a custom kernel for a device with nearly the same hardware (except the display und small things). I searched for OC commit in the source and found one. I apply all changes toy kernel and it compiled. I thought nice ! So I decided to add some other commits like disable CRC fir more performance ect. All went well and the kernel boot up, also wifi works :D but I can't OC the kernel and the max cpu clock is still the same. Also I've got the same benchmark ( tried this because of the CRC changes). For the OC I had to change some lines in /arch/arm64/boot/dts/exynos7870.dtsi. do I have to change something that this will be added to the compiled kernel? I also saw that the update zip from the kernel I cherry picked got a zImage and a dts file but I only got a image file when I compiled? Can I change this or have I to change this? I can make some changes in the menuconfig to get a image.gz-dbt file but what do I have to do with this? Also it's way smaller as the image.

So the main question is do you know what i am doing wrong ?

And another small question is. How to I get the lz4 compression working? When I enable it in my config and flash it my kernel won't boot.

PS: I watched your kernel videos but I wasn't able to solve my problem with this guide. Also I wanna build for the stock Samsung rom because of the Handy Features the stock room got like multi/ resizeable picture mode and perfect SPEN support. I use this tablet for University and I really like it. I only wanna ad some tweaks for more battery and performance.

I have to thank you very much for your guide. It's way more Handy to SEE some guides it makes the whole tutorial more interesting and way easier to follow :) really great work. Maybe I will try to build a whole rom for my old Nexus 5 sometimes and I will definitely use your videos to learn or solve problems.

And a pic to show that the kernel is booting :D

Gesendet von meinem ONEPLUS A3003 mit Tapatalk
[Android General] AlaskaLinuxUser:
Welcome back! And congratulations! I'm glad you found some good source code to work with and have your WiFi working! Well done on getting started, and I'm glad you like the videos. I'm trying to make more in HD.

So, back to your question(s). The guide is, well, a guide for a particular phone, so it can't show every possible outcome, but hopefully it has done it's job, which was to give you a basic idea of how changes work. Sounds like you took it to heart, because you are on the right track!

Do you have a github/gitlab where you uploaded your work? Without seeing what you changed, I can't see what went wrong. You should make a repository, or fork one for the unchanged working kernel, then commit your changes to it, so I can see what you did. Then link it here and I'll try taking a look if I have time.

Typically, you have to adjust the tables, and change the max frequency in the arch folder, and them edit some form of file in the device drivers for the cpufreq scaling so it can use it. But each chip is different.

Also, it is wise to make clean then build again when doing this kind of kernel work. I've had that hang me up a time or two before.

I also would suggest that you only make one change at a time when doing kernel work. But good work so far, you are making great progress!
[Android General] nickrule1896:
I see that this line "Setting of SDR104 timing in not been!!" appears much more often in the unbootable kernel? I compared it to a stock nandroid img, and it seemed like it was looping around that line.

Unbootable: https://pastebin.com/TvDWvQSD

nandroid: https://pastebin.com/912WEaWz

If I'm building stand alone kernel from LineageOS, my rom base needs to be on LineageOS itself right? For the kernel source code, do I extract it from the full Rom source code?

P.S. inside the official source zip Samsung provided a kernel zip and platforms zip, maybe I'm supposed to include certain parts of platforms for building?

Thank you so much thus far! :)