Related
OOk guys so I found this thread which shows MS2 got a custom kernel. The proceduce is bit difficult but can be modified for working for Defy too.
Hope has struck back again.
http://forum.xda-developers.com/showthread.php?t=1908687
Update: 2ndboot module sources are here:
https://github.com/czechop/2ndboot
Quarx puts his kernel here:
quarx2k.ru
Sdcard symlink Fix:
http://forum.xda-developers.com/showpost.php?p=32428611&postcount=392
Thanks to walter.
-------------------------------------------------------------------------------------------------------------------------------
BIGNOTE: Green lens users who flashed redlens builds please dont try using flash, you will end up burning it like me and many others.
STEPS TO FOLLOW WHEN YOU HAVE BOOTLOOPS OR BLACK SCREEN WITH RED LED ON:
-1st of all set default boot to 2nd-boot
-Go to recovery and flash the 24.9 build
-Then flash the kernel 6.10
-After that flash the latest build
-Wait and you will have your phone working proper.
For Bl7 users:
kozaks said:
If your current kernel is 2.6.32.9-ge281b6e [email protected]#1 then the custom kernel won't boot. To get it boot, you need to flash the kernel shared by our friend. Post flashing your kernel should be 2.6.32.9-ge281b6e
[email protected]#1. Once this is confirmed go ahead and flash tbw custom kernel as defined in the first page. Should be good to go.
Link to 51#1 kernel.
http://forum.xda-developers.com/showthread.php?p=32538963
Click to expand...
Click to collapse
-------------------------------------------------------------------------------------------------------------------------------
A suggestion made by a member:
rodrigojfuentes said:
Hey, I just read in this post that flashing gapps before the kernel may prevent the kernel from successfully booting. I tried it and it worked fine. I think you should advice that in the OP
Click to expand...
Click to collapse
-------------------------------------------------------------------------------------------------------------------------------
FOR SIMUNLOCK:
Redhotero said:
Dont know if it's OT or what, but helped me a lot.
This is for the people who wants "sim unlock" in quarx 10/10
1- Download this rar http://forum.motofan.ru/index.php?act=Attach&type=post&id=243798
2- Paste bp_ptc in /system/bin
3- Paste init.mapphone_umts.rc in /system/bootmenu/2nd-boot
and then:
Credits to crakeron, labsin, Dabb and all the people who helped. Im just the messenger,
PD: sorry for my english and sorry if it was posted before
Click to expand...
Click to collapse
-------------------------------------------------------------------------------------------------------------------------------
Feature request for next kernel:
-OTG cable support
- FM transmitter capability Link(requested by amirali_b)
-Sim unlock support(requested by Redhotero)
-Wifi-direct(requested by mdsaif92)
(pm me to add other features)
Waiting for someone to compile a kernel so we can test
Sent from my MB525 using xda app-developrs app
hsrars-d said:
Waiting for someone to compile a kernel so we can test
Sent from my MB525 using xda app-developrs app
Click to expand...
Click to collapse
u can try currently available kernels just to try!
To see if the scripts and modules work xD
M sure they wont work right away
+Really great news
I tried boot my kernel with it (not booted, but log is good).
Waiting for source code and changes in kernel for 2ndboot
http://pastebin.com/jKjQ2ykn
In future i think we can make one kernel for defy and defy+
so just to clear things up for noobs like me: does this mean we could have a jellybean kernel, or is this still gb? and functions like wifi direct which need to be built in the kernel are possible now?
sent from my cm7 defy...
zakoo2 said:
so just to clear things up for noobs like me: does this mean we could have a jellybean kernel, or is this still gb? and functions like wifi direct which need to be built in the kernel are possible now?
sent from my cm7 defy...
Click to expand...
Click to collapse
It means we could use custom kernels.
I think that a developer could even port 3.0.x kernel on defy, if everything 'll go fine.
We may get swap support!(many more things)
Swap is really imp for us since 512MB ram is not enough for jb
Hope Quarx gets it working
Also does kernel version really matter?
I mean if an older kernel is working perfectly and has all ROM features working,why not use that only(2.6.35)
Also I dont think Defy's hardware supports WifiDirect
Sent from my MB526 using xda premium
It seems our sweetoldlittle Defy just won't get outdated soon! Great news, great devs
Sent from my MB525 using xda app-developers app
It works for defy, but unstable for now
http://forum.xda-developers.com/showpost.php?p=32120862&postcount=21
take your time quarx.we are patient it's an amazing news
Custom kernel from sources works too
Linux (none) 2.6.32.9 #1 PREEMPT Fri Sep 28 14:11:14 MSK 2012 armv7l GNU/Linux
Quarx said:
Custom kernel from sources works too
Linux (none) 2.6.32.9 #1 PREEMPT Fri Sep 28 14:11:14 MSK 2012 armv7l GNU/Linux
Click to expand...
Click to collapse
so finally , can we think of DSSCOMP , ION and hwcomposer ?
i know it too early to ask this question
but m very eager to know the answer from quarx
So it means we will have in near future new kernels and possibilty to brick Defy completly ? Or still Defy will be unbrickable and with new kernel
wifibdirect is a sofrware thing, not hardware. the defy would be perfectly capable, but we couldnt load custom kernels (until now).
sent from my cm7 defy...
sebx_g1 said:
So it means we will have in near future new kernels and possibilty to brick Defy completly ? Or still Defy will be unbrickable and with new kernel
Click to expand...
Click to collapse
As far as I understand from this is, the bootloader is still the same, so you still always be able to resurrect your defy with the stock sbfs :cyclops:
Quarx, I can't believe you are just one person... I mean, the progress you've done on the Defy in such a short time is really amazing!!! If the custom kernel gets developed half fast the speed of your mods, our little phone will be a blast pretty soon!!!
Can't Boot
Quarx said:
Custom kernel from sources works too
Linux (none) 2.6.32.9 #1 PREEMPT Fri Sep 28 14:11:14 MSK 2012 armv7l GNU/Linux
Click to expand...
Click to collapse
Can't boot, when i try 2nd boot, defy stuck on black screen 10 to 20 seconds, and reboot :crying:
I don't know why....
I suppose you followed the milestone 2 method directly.
Quarx has not released anything (afaik), and its not intended to users at this staqe.
dumb
hsrars-d said:
I suppose you followed the milestone 2 method directly.
Quarx has not released anything (afaik), and its not intended to users at this staqe.
Click to expand...
Click to collapse
I think quarx boot the mm2 method on defy directly... im dumb
Boss442 said:
I think quarx boot the mm2 method on defy directly... im dumb
Click to expand...
Click to collapse
Yes he did that first, then he modded it and got it to boot. :victory:
This thread is for the developing of the JourneymanMod Kernel project.
For now we are in version 3. Its working great, charging while in OTG, and recoginizes if there is a charger connected or if its default OTG cable.
REMEMBER: It will only charge if you power the hub BEFORE connecting to the phone, if you connect to phone and then power the hub it wont connect.
In the attachments are 3 zip files.
We got version 4.1.1 of yakju and takju. And version 4.1.2 of yakju.
all of them are working nice.
This project will be for enabling OTG + Power, since the stock kernel dont enable charging the phone while in OTG mode.
For helping the project, or just following the news, we created an irc channel (##JourneymanMod).
The source-code of the project will be located at the github (https://github.com/caioketo/journeymanmod).
Was just googling to see if this was possible. Ordered my cable a week ago, waiting for it, & was worried that my time with usb otg would be limited by battery. Great mod! Thank you! Can't wait to try.
---------- Post added at 01:49 AM ---------- Previous post was at 01:20 AM ----------
Anyone interested in this, this is the cable I ordered. Hope it works. Clearly a normal usb otg cable would have nowhere to attach power :
URL: http://www.ebay.com/itm/Micro-USB-H...ng-phone-i9100-i9300-i9220-9250-/251127542280
THX.....................
possibl to develop same thg on n7?
Looks great! I'm about to try. Thank you!
psycho2097 said:
possibl to develop same thg on n7?
Click to expand...
Click to collapse
You should read this thread http://rootzwiki.com/topic/30615-can...imultaneously/ and I'm sure it can be done, I will try it when my N7 arrives...
Sure it is possible with others phone/tablets only need time and ppl to de xD
Almost done with the build envoriment, soon should be the firsts beta releases.
Sent from my Galaxy Nexus using xda app-developers app
caioketo said:
Sure it is possible with others phone/tablets only need time and ppl to de xD
Almost done with the build envoriment, soon should be the firsts beta releases.
Click to expand...
Click to collapse
Totally sweet! Thanks for your work on this...
friedCELLS said:
Totally sweet! Thanks for your work on this...
Click to expand...
Click to collapse
first we need this to work on gnex, then we can think about porting to others devices.
but I have faith we can make it.
The version 3 is released!
Hope you guys enjoin.
Credits to highvista.
Add to GNex CM10/CM10.1??
Would the dev be willing to submit a patch to the Galaxy Nexus CM10/CM10.1 project to enable this feature? I am not sure if this kernel could be used as a replacement for the stock CM10 kernel, but third-party kernels aren't supportable if there's a CM issue (hence my request to have it put in native CM10/10.1 kernel). Thanks!
Jim
CNLiberal said:
Would the dev be willing to submit a patch to the Galaxy Nexus CM10/CM10.1 project to enable this feature? I am not sure if this kernel could be used as a replacement for the stock CM10 kernel, but third-party kernels aren't supportable if there's a CM issue (hence my request to have it put in native CM10/10.1 kernel). Thanks!
Jim
Click to expand...
Click to collapse
Sorry for the delay on responding. This thread hasn't been as active as the original one where the JourneymanMod kernel was first introduced.
I've not submitted a patch to CM previously but, if I can set myself up to do it properly, I definitely will.
It's amazing how easy it is to compile this into custom kernels. Looking forward to the fixed patch.
Sent from my Galaxy Nexus using Tapatalk 2
how do you activate this feature in the AOSP available kernel ? I mean do you actually have to incorporate other drivers or is it maybe just an option you can select with menuconfig ? And if so do you have by any chance the specific parameters that are added to the vanilla .config file ?
tigrone said:
how do you activate this feature in the AOSP available kernel ? I mean do you actually have to incorporate other drivers or is it maybe just an option you can select with menuconfig ? And if so do you have by any chance the specific parameters that are added to the vanilla .config file ?
Click to expand...
Click to collapse
There is a modified AOSP kernel source code file that needs to be replaced. After that, it's a matter of building the kernel with this modified source code and then installing this kernel onto your phone.
This thread is pretty dead. You can find an ongoing discussion and the current kernel distributions at
http://forum.xda-developers.com/showthread.php?t=1835720
The kernels included in the ZIP archives are built as described above, from the AOSP kernel source.
I've fixed a bug in this kernel that occurs when detaching external USB power and am looking for some testing before I replace the current kernel distribution ZIP archives. If you're interested, check out the post and thread at http://forum.xda-developers.com/showpost.php?p=35910077&postcount=182. Thanks much.
caioketo said:
This thread is for the developing of the JourneymanMod Kernel project.
For now we are in version 3. Its working great, charging while in OTG, and recoginizes if there is a charger connected or if its default OTG cable.
REMEMBER: It will only charge if you power the hub BEFORE connecting to the phone, if you connect to phone and then power the hub it wont connect.
In the attachments are 3 zip files.
We got version 4.1.1 of yakju and takju. And version 4.1.2 of yakju.
all of them are working nice.
This project will be for enabling OTG + Power, since the stock kernel dont enable charging the phone while in OTG mode.
For helping the project, or just following the news, we created an irc channel (##JourneymanMod).
The source-code of the project will be located at the github (https://github.com/caioketo/journeymanmod).
Click to expand...
Click to collapse
2 Things:
1.I got CM10.1(Android 4.2.1) it will work?if not there is other solution?
2. There is something like that for Nexus7?(wifi)(CM10.1 Android 4.2.1 too)
elichai2 said:
2 Things:
1.I got CM10.1(Android 4.2.1) it will work?if not there is other solution?
2. There is something like that for Nexus7?(wifi)(CM10.1 Android 4.2.1 too)
Click to expand...
Click to collapse
1. No, it may boot but it will drain your battery and give you some issue. Other solution is try other kernel, if you want custom kernel with minimal customization try lean kernel.
2. I dont know about this
Sent from my Galaxy Nexus using Tapatalk 2
elichai2 said:
2 Things:
1.I got CM10.1(Android 4.2.1) it will work?if not there is other solution?
2. There is something like that for Nexus7?(wifi)(CM10.1 Android 4.2.1 too)
Click to expand...
Click to collapse
1. CM 10.1 doesn't include this kernel patch, as far as I know. I'd like to submit it for inclusion, but I'd need to test it, which means installing CM on my Galaxy Nexus, which I haven't wanted to do, since my GN is working very well under stock Android 4.1.2 with Journeyman Kernel V4.
2. Check out this thread on another web site
http://rootzwiki.com/topic/30615-can-you-charge-usb-host-mode-simultaneously/
I haven't followed this thread, but there was a lot of talk about a similar patch for the N7.
highvista said:
1. CM 10.1 doesn't include this kernel patch, as far as I know. I'd like to submit it for inclusion, but I'd need to test it, which means installing CM on my Galaxy Nexus, which I haven't wanted to do, since my GN is working very well under stock Android 4.1.2 with Journeyman Kernel V4.
2. Check out this thread on another web site
http://rootzwiki.com/topic/30615-can-you-charge-usb-host-mode-simultaneously/
I haven't followed this thread, but there was a lot of talk about a similar patch for the N7.
Click to expand...
Click to collapse
I actually have been testing your patch (even though in my own kernel), the results and some things I noticed I have posted on the thread you mentioned earlier when you announced you solved the bug that occurs when detaching external USB power...
Hope to see you there !
Hi,
I'm looking for a kernel (uImage) with usbhost + multitouch + norefresh for my NST firmware 1.2.1.
Thanks
me too actually. Altough i would not have to be a uImage. Zip files would also be awesome
Have you tried this one?
http://forum.xda-developers.com/showthread.php?t=1906507
I know there is a version with no-refresh and USB Host, not sure about multi-touch,
I'm also looking for one. Have USB host with keyboard working but would like kernel for 1.2.1 with drivers for audio, multitouch, etc
David0226 said:
Have you tried this one?
http://forum.xda-developers.com/showthread.php?t=1906507
I know there is a version with no-refresh and USB Host, not sure about multi-touch,
Click to expand...
Click to collapse
posts on that thread said that only version 166 works on 1.2.1
but only last version (174) of this kernel has usbhost support.
Maybe I misunderstood
jeff_kz has kernel config code here:
https://github.com/doozan/NookManager/blob/master/Buildroot/kernel-config
dnordquest said:
jeff_kz has kernel config code here:
https://github.com/doozan/NookManager/blob/master/Buildroot/kernel-config
Click to expand...
Click to collapse
Thanks for the information about the kernel but I don't have the skill to compile a kernel.
And I don't know which options to turn on in kernel-config to have usbhost, multitouch and no refresh at the same time.
The following two sources for uImage contain the identifier: Linux-2.6.29-omap1.
http://nst-recovery.googlecode.com/files/uImage_usb_audio_test.zip
http://nst-recovery.googlecode.com/files/uImage_mt_usbhost_115.zip
That is the same identifier as the uImage I am using with 1.2.1. Whether either of the above will work with 1.2.1 I do not know & I am hoping someone with experience will say. Also, I am not sure if changes to any other file will be needed to get either running. The first file is said to have been deprecated, though why I know not.
I also do not know what drivers each contains besides those indicated in the name.
dnordquest said:
The following two sources for uImage contain the identifier: Linux-2.6.29-omap1.
http://nst-recovery.googlecode.com/files/uImage_usb_audio_test.zip
http://nst-recovery.googlecode.com/files/uImage_mt_usbhost_115.zip
That is the same identifier as the uImage I am using with 1.2.1. Whether either of the above will work with 1.2.1 I do not know & I am hoping someone with experience will say. Also, I am not sure if changes to any other file will be needed to get either running. The first file is said to have been deprecated, though why I know not.
I also do not know what drivers each contains besides those indicated in the name.
Click to expand...
Click to collapse
I actualy use http://nst-recovery.googlecode.com/files/uImage_mt_usbhost_115.zip on my nook 1.2.1. Usbhost and multitouch works but I can't enable norefresh on this kernel.
I've tried both uImages above & both work on my 1.2.1 but no-refresh unsolved here, too.
This thread is for developers to discuss bringup for the 3.4 jb kernel on various devices in the Nitro HD "iproj" family. These include P930, SU640, VS920, and LU6200.
Downloaded the su640 jb sources and compiled for ijb_skt. Tried to boot on my "gimpy" p930. No boot.
Enabled console framebuffer and snapped a pic just before reboot. It's complaining about fatal regulator error (msm_rpm_err_fatal). Anyone else get this far and/or see anything similar?
If anyone wants to use a console framebuffer, here's how:
1. Enable CONFIG_FRAMEBUFFER_CONSOLE and CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY.
2. Modify console_setup() in kernel/printk.c. Delete the function body and replace it with just "return 1".
Be prepared with a camera to snap an image of the screen before it reboots.
tdmcode said:
Downloaded the su640 jb sources and compiled for ijb_skt. Tried to boot on my "gimpy" p930. No boot.
Enabled console framebuffer and snapped a pic just before reboot. It's complaining about fatal regulator error (msm_rpm_err_fatal). Anyone else get this far and/or see anything similar?
If anyone wants to use a console framebuffer, here's how:
1. Enable CONFIG_FRAMEBUFFER_CONSOLE and CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY.
2. Modify console_setup() in kernel/printk.c. Delete the function body and replace it with just "return 1".
Be prepared with a camera to snap an image of the screen before it reboots.
Click to expand...
Click to collapse
Working on bringing this up for the vs920 as that's the only one I've got.
So far I've copied the ijb_skt bits over to ijb_vzw and used a bit of grep/sed magic to replace the skt bits to vzw in the files, and add ||'s for ijb_vzw wherever ijb_skt was a condition. I'm getting successful builds But they won't boot (yet). I'll keep you updated. I'll be pushing to here as I make any changes/progress.
Got past the RPM error with a hack.
In arch/arm/mach-msm/clock.c @ clock_late_init(), remove the list_for_each_entry_safe block.
Obviously, this is just a hack. We need to figure out what's causing the issue.
Next up is the display. The kgsl driver in this kernel does not match the kgsl libs in CM10. I'm going to download the 4.1 flashable rom from this forum and see if I can update the drivers to match.
I think kgsl is happy now. Next up is the msm video driver.
tdmcode said:
I think kgsl is happy now. Next up is the msm video driver.
Click to expand...
Click to collapse
Man, You're a machine... Here I'm still trying to get something that'll boot past the LG logo lol
Got boot animation and home screen. Then it reboots after a minute or so. The shell in adb gets really laggy right before reboot. Likely causes are a kernel hardware driver failing somewhere or a massive memory leak.
I see touch events logged but by the time the home screen shows I think it's too far gone to act on them. Same with hard buttons and capacitive buttons.
Oh .. by the way I'm using CM10 not CM10.1. It matches better since it's a 4.1 kernel.
Gotta stop for the day. Here's what I've got so far...
http://androidrepo.net/roms/quattrimus/iproj/iproj-3.4-checkpoint1.diff
tdmcode said:
Oh .. by the way I'm using CM10 not CM10.1. It matches better since it's a 4.1 kernel.
Gotta stop for the day. Here's what I've got so far...
http://androidrepo.net/roms/quattrimus/iproj/iproj-3.4-checkpoint1.diff
Click to expand...
Click to collapse
Nevermind. I thought the link I just posted was for someone working on another 3.4 kernel... it wasnt.
*Edit*
I'm obviously doing something horribly wrong by trying to borrow/reuse the ijb_skt files, because I can't get a kernel that even tries to boot (gets off the first LG logo)... and don't really have the know-how to reconstruct the files.
Didn't get a chance to work on this today I was busy on another project. But I'll be back on it Monday for sure.
@Yoinx: you are going to have a harder time with the vs920 because the hardware is different and it won't boot the su640 kernel.
I do not know the approach of developing cm10 kernel from stock kernel.
According to miroslav_mm,
http://forum.xda-developers.com/showpost.php?p=42075037&postcount=40
I tried using stock 3.4 zImage + cm10 ramdisk + required libs. It boots with blackscreen
lyfkevin said:
I do not know the approach of developing cm10 kernel from stock kernel.
According to miroslav_mm,
http://forum.xda-developers.com/showpost.php?p=42075037&postcount=40
I tried using stock 3.4 zImage + cm10 ramdisk + required libs. It boots with blackscreen
Click to expand...
Click to collapse
You need to change the kgsl and msm video code to match cm10. See my patch.
tdmcode said:
You need to change the kgsl and msm video code to match cm10. See my patch.
Click to expand...
Click to collapse
The boot.img provided by @navik
Same approach, i.e. stock zImage + cm10 ramdisk
I can boot into home screen with my su640 now.
Signal, wifi work.
but laggy, blinking screen(check hw overlay setting in option can fix), no sound, no bootanimation (black screen)
----------------------------------------------------
edit:
Merged your patch
able to see boot animation
Sent from my LG-LU6200 using xda premium
LU6200 jb source is released
https://wws.lg.com/global/support/opensource/opensourceList?types=ALL&search=lu6200
lyfkevin said:
I do not know the approach of developing cm10 kernel from stock kernel.
According to miroslav_mm,
http://forum.xda-developers.com/showpost.php?p=42075037&postcount=40
I tried using stock 3.4 zImage + cm10 ramdisk + required libs. It boots with blackscreen
Click to expand...
Click to collapse
I finished my new build CM10, on 3.4 kernel, with new JB camera libs, and other new properitary stuff. Dont have any problem with 3.4 kernel on CM10 (4.1.2), I didnt patch any KGSL driver, sources from my Github working, it dont have last updates but it working. I cant upload new ROM for test now, I dont have internet at home, when I fix my provider I will upload it.
lyfkevin which display libs did you use? Did you complete build CM10 with new kernel and headers?
Take this variant:
1.) display libs: copybit.msm8660.so, gralloc.msm8660.so, hwcomposer.msm8660.so, libgenlock.so, libhwcexternal.so, libhwcservice.so, libmemalloc.so, libqdutils.so, libtilerenderer.so, and libqdMetaData.so take from official STOCK 4.1 + take Adreno libs with MetaData support from my last CM10 or from STOCK 4.1 (older version) = its working on CM10
miroslav_mm said:
I finished my new build CM10, on 3.4 kernel, with new JB camera libs, and other new properitary stuff. Dont have any problem with 3.4 kernel on CM10 (4.1.2), I didnt patch any KGSL driver, sources from my Github working, it dont have last updates but it working. I cant upload new ROM for test now, I dont have internet at home, when I fix my provider I will upload it.
lyfkevin which display libs did you use? Did you complete build CM10 with new kernel and headers?
Take this variant:
1.) display libs: copybit.msm8660.so, gralloc.msm8660.so, hwcomposer.msm8660.so, libgenlock.so, libhwcexternal.so, libhwcservice.so, libmemalloc.so, libqdutils.so, libtilerenderer.so, and libqdMetaData.so take from official STOCK 4.1 + take Adreno libs with MetaData support from my last CM10 or from STOCK 4.1 (older version) = its working on CM10
Click to expand...
Click to collapse
is your 3.4 kernel compatible with your previous cm10 builds? a lot less MBs, easier to upload.
tdmcode said:
This thread is for developers to discuss bringup for the 3.4 jb kernel on various devices in the Nitro HD "iproj" family. These include P930, SU640, VS920, and LU6200.
Click to expand...
Click to collapse
Exece me,I want to build aosp of su640 based on LG offical open sourse. I have try serverl times,but end with failure.
Should you give me some advices or guide? Thanks for your reply!
navik said:
Exece me,I want to build aosp of su640 based on LG offical open sourse. I have try serverl times,but end with failure.
Should you give me some advices or guide? Thanks for your reply!
Click to expand...
Click to collapse
You cannot do this. There are many changes to files which are not gpl .
It takes a lot of work to make an aosp ROM. You need most of the cm hardware changes and various other changes through the system. I have done it for 4.1 with only one bug: the front camera does not work. I have not tried with 4.2 yet.
tdmcode said:
You cannot do this. There are many changes to files which are not gpl .
It takes a lot of work to make an aosp ROM. You need most of the cm hardware changes and various other changes through the system. I have done it for 4.1 with only one bug: the front camera does not work. I have not tried with 4.2 yet.
Click to expand...
Click to collapse
Thanks，but I want to build aosp based on LG open sourse instead of porting.
Do you have read the guide of LG offical open sourse？It say we can build stockrom based on LG official open sourse and Google android open sourse，we just need to copy LG open sourse into android open sourse. then breakfast and lunch.but I fail，I think I didn't pick up the guide of LG open sourse 。Do you have some good advices？Thanks again！
Sent from my LG-SU640 using xda premium
Hi all !
After many years of "xda looting", i'm trying to contribute a little.
I'm a begginer, just learned 3 days ago how to use github ! So be cool guys, not a dev here.
Now i successfully compiled a Kernel, with addition of KCAL for now, but...
I got the Image.gz-dtb and i don't succeed in repacking it in a boot.img, if someone want to try, be my guest. (It's untested obviously, but compilation was without errors/warnings (we are close to stock for now.).
I tried mkboot, anykernel2, lazyflasher.... Always flash error, and i don't have time for the next few days, so if we could put a team together...
Here is the link to my compiled files (arch/arm64/boot) except dto folder. //Update to my Dev folder
Theorically you just have to rename, put it in a stock boot.img, "fastboot boot newboot.img" and test if Kcal is working with ex kernel manager, then more to come (governors, maybe OC, etc.)
Poke @d1ngh, you could help here after your work on twrp ?
Cheers guys, we could have our first custom kernel soon !
----------------------------------------
Source : [url]https://github.com/WiwiWillou/Xiaomi_Kernel_OpenSource.git[/URL]
Defconfig used = defconfig daisy-perf_defconfig (with the kcal=Y addition not commited for now) // branch daisy-o-oss
Thank you very much! That´s what I waited for. Unfortunately 7zip says error: unknown compression method... Perhaps you can repack? Thx.
That is all we need ! A custom kernel thant can handle GSI !
Voodoojonny said:
Thank you very much! That´s what I waited for. Unfortunately 7zip says error: unknown compression method... Perhaps you can repack? Thx.
Click to expand...
Click to collapse
I've updated the link, you should see the uncompressed file in folder !
Or direct link : https://drive.google.com/file/d/1TvihsIa_XbtC66yaWRZ1EPY5UR6LLD5g/view?usp=drivesdk
Thanks
WiwiPouPou said:
Hi all !
After many years of "xda looting", i'm trying to contribute a little.
I'm a begginer, just learned 3 days ago how to use github ! So be cool guys, not a dev here.
Now i successfully compiled a Kernel, with addition of KCAL for now, but...
I got the Image.gz-dtb and i don't succeed in repacking it in a boot.img, if someone want to try, be my guest. (It's untested obviously, but compilation was without errors/warnings (we are close to stock for now.).
I tried mkboot, anykernel2, lazyflasher.... Always flash error, and i don't have time for the next few days, so if we could put a team together...
Here is the link to my compiled files (arch/arm64/boot) except dto folder. //Update to my Dev folder
Theorically you just have to rename, put it in a stock boot.img, "fastboot boot newboot.img" and test if Kcal is working with ex kernel manager, then more to come (governors, maybe OC, etc.)
Poke @d1ngh, you could help here after your work on twrp ?
Cheers guys, we could have our first custom kernel soon !
----------------------------------------
Source : [url]https://github.com/WiwiWillou/Xiaomi_Kernel_OpenSource.git[/URL]
Defconfig used = defconfig daisy-perf_defconfig (with the kcal=Y addition not commited for now) // branch daisy-o-oss
Click to expand...
Click to collapse
Try it with android image kitchen (you first have to get the original bootimage from vendor/factory image, unpack it, exchange your kernel and repack it). recompiled official sources (with UBERTC) and it worked fine like that.
wertus33333 said:
Try it with android image kitchen (you first have to get the original bootimage from vendor/factory image, unpack it, exchange your kernel and repack it). recompiled official sources (with UBERTC) and it worked fine like that.
Click to expand...
Click to collapse
I've tried, maybe my image is bad, strange (I originally tried my stock source too, Google 4.9 toolchain, no luck). Can you test with the one in the link please ?
I will have access to my PC only next week...
Thanks a lot for your feedback !
wertus33333 said:
Try it with android image kitchen (you first have to get the original bootimage from vendor/factory image, unpack it, exchange your kernel and repack it). recompiled official sources (with UBERTC) and it worked fine like that.
Click to expand...
Click to collapse
Could you please share your build script ? Did you use an alternate defconfig ?
Learning here
EDIT : Which UberTC did you use ?
WiwiPouPou said:
Could you please share your build script ? Did you use an alternate defconfig ?
Learning here
EDIT : Which UberTC did you use ?
Click to expand...
Click to collapse
I used the original source code with some small changes (which are now included in official source) to make it compile.
Don't mind about the toolchain for the moment, gcc4.9 is most stable.
I don't have time trying this out atm, busy compiling los 15.1 but if you share exactly how you did it, (terminal log in pastebin and most importantly the exact errors, "doesn't work" doesn't help ) me or someone else might be able to help you (and you don't have to ask next time you get the error.
If you want you can start adjusting the lineage kernel, so i could build with los kernel which could save time towards working custom roms.
I successfully repack. But phone don't boot. (9.11 ROM)
Hello , can you help me with conpiling kernel source code? I tryed a lot of time but same issues , that could find same files.
I successfully repack image of kernel that you publish, but phone don't boot , they reboot in stock kernel(if i write fastboot boot boot.img) and I trying flashing image. They dont boot.
I vary want to create collection of custom kernel's on my device. And of course becouse i vary interested in this sphere, but new this.
Can you describe how you fix issues, or your compiling go without issues.
With best regards. Please help.
artyom5613 said:
Hello , can you help me with conpiling kernel source code? I tryed a lot of time but same issues , that could find same files.
I successfully repack image of kernel that you publish, but phone don't boot , they reboot in stock kernel(if i write fastboot boot boot.img) and I trying flashing image. They dont boot.
I vary want to create collection of custom kernel's on my device. And of course becouse i vary interested in this sphere, but new this.
Can you describe how you fix issues, or your compiling go without issues.
With best regards. Please help.
Click to expand...
Click to collapse
On which roms did you test your kernel?
Voodoojonny said:
On which roms did you test your kernel?
Click to expand...
Click to collapse
8.1 stock. 9.11
I compile stock kernel , repack him , ans this work fine. Now i need help to add kcal support. Author, can you help?
artyom5613 said:
I compile stock kernel , repack him , ans this work fine. Now i need help to add kcal support. Author, can you help?
Click to expand...
Click to collapse
I will, I'm very far from my PC for a few weeks again, I've used some commits :
https://github.com/rama982/android_kernel_xiaomi_msm8953/search?q=kcal&type=Commits
Source for pie is not pushed ?
WiwiPouPou said:
I will, I'm very far from my PC for a few weeks again, I've used some commits :
https://github.com/rama982/android_kernel_xiaomi_msm8953/search?q=kcal&type=Commits
Source for pie is not pushed ?
Click to expand...
Click to collapse
Thanks! O try to add kcal with this commits.
Yea, source for pie is not pushed. Xiaomi cant fix 8.1 kernel... Stock compiled kernel issue: wifi don't work...
WiwiPouPou said:
I will, I'm very far from my PC for a few weeks again, I've used some commits :
https://github.com/rama982/android_kernel_xiaomi_msm8953/search?q=kcal&type=Commits
Source for pie is not pushed ?
Click to expand...
Click to collapse
Can you tell me what version of kernel you use whyle compile kernel? I tryed on new 9.11, but phone dont boot.
Maybe when you compile version be 9.10 or ealier.
becouse ramdisk and kernel image can conflict
I hope this can support settings for "display temperature" so that we dont need app for calibrating warmth or coolness of display
Current state:
Kernel builded.
Kcal included.
Wifi don't work , searching fix
artyom5613 said:
Current state:
Kernel builded.
Kcal included.
Wifi don't work , searching fix
Click to expand...
Click to collapse
Kcal is working ?
Strange for WiFi, module not compiled ?