Open assusdan opened 8 years ago
Yes, Is booteable in my device. At the moment I just made selinux as permissive.... I will add more tweaks in the future. PS: Maybe if I finish this project I will try to modify my kernel for cm13 using your zera kernel as base for seeing the changes that I must do... Don't know if it will be difficult or easy.. If you can help me it will be amazing!
My CM kernel is for Zormax device tree (based on sprout4 with some changes to common 6582). Device tree download link: https://mega.nz/#!zd0EnLxB!jEXgpICb0MX_pwNkWzL8tD2oJUeMwTFZBNci2ztT_Mw What device tree are you using with Zeus kernel? How much bugs are there? Is it more powerful than stock kernel?
Precompiled ROM CM13 Zormax tree: https://yadi.sk/d/_vZv31iyv8RjM
This kernel is not for compile any rom at the moment... I didn't add any patches for now.. The kernel is more powerful than stock kernel. And I will try to adapt your kernel to my device for boot zormax rom with sprout patches but... Can you say to me the guide that I must follow to atleast boot it? Thanks in advance
I can help you with booting my kernel. 1) Fix MBR at https://github.com/Pablito2020/android_kernel_hs_zerasrs/blob/cm-13.0/arch/arm/mach-mt6582/alps/partition/cust_part_mbr.c#L4 2) Add your lcm .c file and change Makefile and mt65xx_lcm_list.c here https://github.com/Pablito2020/android_kernel_hs_zerasrs/tree/cm-13.0/arch/arm/mach-mt6582/alps/lcm 3) Open your codegen.dws in DrvGen.exe (via Wine); then GenCode and put generated files here: https://github.com/Pablito2020/android_kernel_hs_zerasrs/tree/cm-13.0/arch/arm/mach-mt6582/alps/dct/dct 4) Add your touchpanel here: https://github.com/Pablito2020/android_kernel_hs_zerasrs/tree/cm-13.0/drivers/input/touchscreen/mediatek 5) Change your LCM and touchpanel and screen resolution at https://github.com/Pablito2020/android_kernel_hs_zerasrs/blob/cm-13.0/arch/arm/configs/alps_defconfig 6) Compile it as usually. If you get any errors, ask me here and I'll help you. 7) Repack CM13 Zormax rom's boot.img (I'm using AndImgTool.exe. Carliv Image Kitchen not tested). Change only kernel. 8) Change your modem in /system/etc/firmware 9) Don't change any libs at the moment. Just flash rom with ALL wipes ( System + Data + Cache + others)
At what rom are you testing Zeus kernel?
I'm testing it in my stock rom 5.0, is working well in cm12.1 for stock kernel (sources by @dee3000)
PS: I use your kernel as "stock" and I add the files that you say before from my kernel source to your kernel sources for boot it?
I can't get what you said about stock. Yes, pick this files from stock, but you must change some of them. There will be (99%) errors in LCM drivers.
Okay @assusdan fix error during compiling...
Text: To see full details build your kernel with:
'make CONFIG_DEBUG_SECTION_MISMATCH=y'
GEN .version
CHK include/generated/compile.h
UPD include/generated/compile.h
CC init/version.o
LD init/built-in.o
arch/arm/mach-mt6582/built-in.o: In function .LANCHOR0': :(.data+0x8b24): undefined reference to
hx8389b_qhd_dsi_vdo_tianma_lcm_drv'
:(.data+0x8b28): undefined reference to `hx8389_qhd_dsi_vdo_truly_lcm_drv'
make[1]: * [vmlinux] Error 1
make: * [sub-make] Error 2
Image: http://imgur.com/a/2xQ65
Hope you can know how to fix it...
Yes I know. One of these: 1) LCM driver .c file don't compile 2) You changed lcm_list file wrong Please add test branch and commit your changes. It really will help fix errors :)
Okay, I will make a branch called cm13 in this repository.. I will upload the changes now..
Here you go: https://github.com/Pablito2020/kernel_cyanogenmod_13_krillin/commit/c2910f0865ba7517d189af7f232c88d8e35607fe @assusdan this are the changes that I made to the kernel
https://github.com/Pablito2020/kernel_cyanogenmod_13_krillin/tree/cm-13.0/arch/arm/mach-mt6582/alps/lcm Add here your lcm .c files (e.g. otm9605a_dsi_vdo_cs.c)
So on other questions I will answer tomorrow. Good luck!
@assusdan Ok, first of all. Finally I compiled the kernel, but it didn't boot, it stucks at logo. There are my last commit: https://github.com/Pablito2020/kernel_cyanogenmod_13_krillin/commit/1f6edfce498eb796d931d41cf00b2f8bb9d70293
And there is the last_kmsg:
show last_kmsg2 sig 1128743492, size 6272, hw_status 1128743492, reboot_mode 0!
(0)[1:init]******** MTK WDT driver shutdown done ********
[ 132.673196] (0)[1:init][vibrator]vib_shutdown: enter!
[ 132.673212] (0)[1:init][Power/PMIC] [dct_pmic_VIBR_enable] 1
[ 132.737607]-(3)[4841:BootAnimation][SMI] [pid=4787]Init OSTD for larb_base: 0xf4010000
[ 132.737635]-(3)[4841:BootAnimation][SMI] [pid=4787]SMI init
[ 132.737668]-(0)[1:init][DEVAPC] Vio Addr:0x16010200 , Master ID:0xe , Dom ID:0x0, W
[ 132.805203]-(3)[4841:BootAnimation][SMI] [pid=4787]Init OSTD for larb_base: 0xf4010000
[ 132.805231]-(3)[4841:BootAnimation][SMI] [pid=4787]SMI init
[ 132.805263]-(0)[2542:CatalogerThread][DEVAPC] Vio Addr:0x16010200 , Master ID:0xe , Dom ID:0x0, W
[ 132.871518]-(2)[4841:BootAnimation][SMI] [pid=4787]Init OSTD for larb_base: 0xf4010000
[ 132.871545]-(2)[4841:BootAnimation][SMI] [pid=4787]SMI init
[ 132.871576]-(0)[0:swapper/0][DEVAPC] Vio Addr:0x16010200 , Master ID:0xc , Dom ID:0x0, W
[ 132.879383] (0)[4647:Binder_3]EXT4-fs (mmcblk0p7): ext4_da_writepages: jbd2_start: 2147483603 pages, ino 36969; err -30
[ 132.938523]-(1)[4841:BootAnimation][SMI] [pid=4787]Init OSTD for larb_base: 0xf4010000
[ 132.938543]-(1)[4841:BootAnimation][SMI] [pid=4787]SMI init
[ 132.938570]-(0)[2461:FlusherThread]
I've only replaced kernel in boot.img, and firmware folder from system folder (not from system.new.dat )
Well, try to test your kernel in recovery (replace kernel in your recovery with compiled). Maybe it will boot.
Okay, will try to boot it in recovery. I won't try more things with these kernel until the next Wednesday (12/10/16) because of exams... Will compile TWRP recovery with the compiled kernel Wednesday as well. PS: Does the last.kmsg say the error? Maybe is that line: 132.879383[4647:Binder_3]EXT4-fs (mmcblk0p7): ext4_da_writepages: jbd2_start: 2147483603 pages, ino 36969; err -30 Don't know so much about learning logs.... Thanks in advance @assusdan
Was this kernel booting for 132 seconds? Seems that it is log from another kernel.
@assusdan I can't remember what seconds was the kernel booting... I copy the last_kmsg-2 file from /proc. Maybe I must copy the last_kmsg file for see the log of this kernel? So I will reinstall the rom and I'll copy the last_kmsg and I'll show it to you.
Try this.
Okay, you were right it wasn't the correct last_kmsg....
Now I paste the last_kmsg and the last_kmsg2:
LAST_KMSG-2:
show last_kmsg2 sig 1128743492, size 6936, hw_status 0, reboot_mode 0!
2: stopping and cpu_relax,state:3
[ 930.550844]-(3)[0:swapper/3]Backtrace: B<4>[ 930.550852]-(3)[0:swapper/3]
[ 930.550859]-(2)[0:swapper/2][
LAST_KMSG:
ram console header, hw_status: 2, fiq step 0.
bin log 0.
y][vibrator]vibrator_enable: vibrator first in value = 80
211.306790[91:recovery][vibrator]vibrator_enable: vibrator cust timer: 50
211.306805[91:recovery][vibrator]vibrator_enable: vibrator start: 80
211.306852[5:kworker/u:0][Power/PMIC] [dct_pmic_VIBR_enable] 1
211.386898[5:kworker/u:0][Power/PMIC] [dct_pmic_VIBR_enable] 0
211.779459[91:recovery][vibrator]vibrator_enable: vibrator first in value = 80
211.779481[91:recovery][vibrator]vibrator_enable: vibrator cust timer: 50
211.779497[91:recovery][vibrator]vibrator_enable: vibrator start: 80
211.779544[5:kworker/u:0][Power/PMIC] [dct_pmic_VIBR_enable] 1
211.859585[5:kworker/u:0][Power/PMIC] [dct_pmic_VIBR_enable] 0
212.343455[91:recovery][vibrator]vibrator_enable: vibrator cust timer: 50
212.343495[91:recovery][vibrator]vibrator_enable: vibrator start: 80
212.343575[5:kworker/u:0][Power/PMIC] [dct_pmic_VIBR_enable] 1
212.423578[5:kworker/u:0][Power/PMIC] [dct_pmic_VIBR_enable] 0
214.506140[91:recovery][vibrator]vibrator_enable: vibrator first in value = 80
214.506163[91:recovery][vibrator]vibrator_enable: vibrator cust timer: 50
214.506178[91:recovery][vibrator]vibrator_enable: vibrator start: 80
214.506222[5:kworker/u:0][Power/PMIC] [dct_pmic_VIBR_enable] 1
214.586253[5:kworker/u:0][Power/PMIC] [dct_pmic_VIBR_enable] 0
214.629565[91:recovery]type=1400 audit(1476024878.920:59): avc: denied { remove_name } for pid=91 comm="recovery" name="recovery-from-boot.p" dev="mmcblk0p5" ino=1704 scontext=u:r:init:s0 tcontext=u:object_r:system_file:s0 tclass=dir
214.629691[91:recovery]type=1400 audit(1476024878.920:60): avc: denied { rename } for pid=91 comm="recovery" name="recovery-from-boot.p" dev="mmcblk0p5" ino=1704 scontext=u:r:init:s0 tcontext=u:object_r:system_file:s0 tclass=file
214.822116[0:swapper/1][Power/Battery] \ battery : bat_thread_wakeup **
214.822170[56:bat_thread_kthr][Power/Battery] [BAT_thread]Cable out
214.822183[56:bat_thread_kthr][MUSB] USB is ready for disconnect
214.947688[1:init][GPS: ] mt3326_gps_power: null pointer!!
214.948161[1:init]mt_usb_disable, 0, 0
214.948260[1:init]\ MT auxadc driver shutdown!! **
214.948278[1:init][LED]mt65xx_leds_shutdown
214.948287[1:init][LED]mt65xx_leds_shutdown: turn off backlight
214.948299[1:init][LED]PMIC#2:0
214.948382[1:init][LED]PMIC#1:0
214.948444[1:init][LED]PMIC#3:0
214.948505[1:init][LED]PMIC#4:0
214.948565[1:init][LED]backlight control through BLS!!1
214.948576[1:init][BLS]disp_bls_set_backlight: 0
214.980595[1:init][DDP] MT_CG_DISP0_SMI_LARB0 is forced on
215.390571[1:init][GPIO] 26: Pin 112 decrypt warning!
215.550629[1:init][Power/PMIC] [dct_pmic_VGP2_enable] 0
215.557704[1:init][DDP]disp_path_power_off, caller:mtkfb
215.557733[1:init][DDP]disp_reg_backup() start, _pRegBackup=0xdeadbeef, reg_offset=0
215.557807[1:init][DDP]disp_reg_backup() end, *pRegBackup=0x2, reg_offset=213
215.557840[1:init][DDP] OVLReset called 0
215.557997[1:init][SMI] [pid=1]on_larb_power_off(), larb_idx=0
215.558161[1:init]-AudDrvshutdown
215.558312[1:init]*** MTK WDT driver shutdown done ****
215.558335[1:init]mtkfb_vsync device shutdown
215.558356[1:init]JPEG Codec shutdown
215.558379[1:init][MATV] shutdown
215.558403[1:init]mt_pwm_shutdown
215.558422[1:init][vibrator]vib_shutdown: enter!
215.558450[1:init]ALMK driver shutdown
215.558482[1:init][Power/Battery] \ battery driver shutdown!! **
215.558512[1:init][Power/BatMeter] [battery_meter_shutdown]
215.558614[1:init][Power/PMIC] \ MT6323 pmic driver shutdown!! **
215.558664[1:init]Restarting system with command ''.
215.558688[1:init]machine_shutdown: start, Proess(init:1)
215.558708[1:init]Backtrace:
215.558777[1:init]
In my opinion, I think that is the last_kmsg the file who say what driver is failing... Hope you can know what driver is failing @assusdan
@Pablito2020 you forgot change your LCM here: https://github.com/Pablito2020/kernel_cyanogenmod_13_krillin/blob/1f6edfce498eb796d931d41cf00b2f8bb9d70293/arch/arm/configs/alps_defconfig#L1168
@assusdan IF I change the LCM driver I have compilation error.... How to know what LCM driver I must put there? Thanks in advance
Just send me an error and I will help you
How to know what LCM driver I must put there?
As in this kernel, if it is bootable.
Here you go he compilation error: Image: http://imgur.com/a/rua3c
This happens if I cahnge the line that you sayed before to my stock one that is that: CONFIG_CUSTOM_KERNEL_LCM="hx8389_qhd_dsi_vdo_truly hx8389b_qhd_dsi_vdo_tianma"
I think that I msut modify something in /drivers/misc/mediatek/lcm... ANd add this files on it? Ok, edit, there is no lcm folder in drivers/misc/mediatek...
@assusdan
As far as i know, there is no support of two screens in Makefile. So change here https://github.com/Pablito2020/kernel_cyanogenmod_13_krillin/blob/cm-13.0/arch/arm/mach-mt6582/alps/lcm/Makefile Add in the end of file obj-y += hx8389_qhd_dsi_vdo_truly.o obj-y += hx8389b_qhd_dsi_vdo_tianma.o
And set your lcm in defconfig CONFIG_CUSTOM_KERNEL_LCM="hx8389_qhd_dsi_vdo_truly hx8389b_qhd_dsi_vdo_tianma"
Thanks @assusdan finally the kernel boot it! Now I must fix touchpanel driver... Because touch is not working... But boot it was more than enough :) Thanks @assusdan if you can help me with the touch driver will be awesome.
Send me dmesg
adb shell dmesg > file.txt
Do it in a first seconds of booting (as fast as adb finds your device)
Here you go @assusdan
Link to download it on google drive: https://drive.google.com/open?id=0Bz2oqTTLsabkNENLVTlSUFBGZ2c
Hope you can find the bug problem! Thanks in advance
@Pablito2020 1) change here https://github.com/Pablito2020/cyanogenmod_kernel_bq_krillin/blob/cm-13.0/arch/arm/configs/alps_defconfig#L1724 to this https://github.com/Pablito2020/Zeus_Kernel_Krillin/blob/Zeus-beta/arch/arm/configs/krillin_defconfig#L1762 2) add here https://github.com/Pablito2020/cyanogenmod_kernel_bq_krillin/blob/cm-13.0/drivers/input/touchscreen/Kconfig these 3 strings: https://github.com/Pablito2020/Zeus_Kernel_Krillin/blob/Zeus-beta/drivers/input/touchscreen/Kconfig#L484 3) add here https://github.com/Pablito2020/cyanogenmod_kernel_bq_krillin/tree/cm-13.0/drivers/input/touchscreen/mediatek/ft5336 these files: https://github.com/Pablito2020/Zeus_Kernel_Krillin/tree/Zeus-beta/arch/arm/mach-mt6582/krillin/touchpanel/ft5336
Thanks @assusdan will try at the afternoon, I will say to you if it worked :) Thanks in advance :)
@assusdan I'm having a lot of errors with the ft5336 drivers because my device have the feature of doubletap to wake incorporated in this driver and it gives me a lot of compilation errors..... Don't know how to delete the f***ing double tap and compile the kernel. The driver is this: https://github.com/Pablito2020/Zeus_Kernel_Krillin/blob/Zeus-beta/drivers/input/touchscreen/mediatek/ft5336/ft5336_driver.c
This is the error compilation:
drivers/built-in.o: In function check_gesture': /home/pablito2020/Cyanogenmod-Kernal/kernel/drivers/input/touchscreen/mediatek/ft5336/ft5336_driver.c:1734: undefined reference to
TMD2772_enable_ps_tp'
/home/pablito2020/Cyanogenmod-Kernal/kernel/drivers/input/touchscreen/mediatek/ft5336/ft5336_driver.c:1736: undefined reference to TMD2772_read_ps_tp' /home/pablito2020/Cyanogenmod-Kernal/kernel/drivers/input/touchscreen/mediatek/ft5336/ft5336_driver.c:1745: undefined reference to
custom_vibration_enable'
/home/pablito2020/Cyanogenmod-Kernal/kernel/drivers/input/touchscreen/mediatek/ft5336/ft5336_driver.c:1749: undefined reference to TMD2772_enable_ps_tp' drivers/built-in.o: In function
tpd_resume':
/home/pablito2020/Cyanogenmod-Kernal/kernel/drivers/input/touchscreen/mediatek/ft5336/ft5336_driver.c:2257: undefined reference to `check_charger_exist'
Help would be really apreciated. Thanks in advance
Okay @assusdan Finally compiled the kernel with my touch drivers but... When I flash it on my device it passes from the bootlogo but after a few seconds in the bootanimation my phone reboot to the logo and then to the bootanimation again and again.... I can't take logcat in the bootanimation part But I can take the last_kmsg. So here you go!: http://hastebin.com/iwiqupatav.md
Thanks in advance
@Pablito2020 first of all, are you sure that kernel is booting for 42 seconds? If its a true, repack it in recovery (e.g. TWRP) and take dmesg log continuously while kernel is booting. Secondly, if you're disabling your touch, kernel is bootable?
@assusdan yes, if I disable my touch drivers kernel is booting... Anyway. I will download the omnirom sources and compile twrp with the new kernel with the touch driver... Maybe it will boot. And I will try to get a logcat. Bcause last_kmsg hace no sense with this issue
There is no need to recompile twrp. Just repack it in Carliv Image Kitchen / AndImgTool with replacing kernel by compiled. How did you fix errors? Say me step by step. Maybe I'll find error.
@Pablito2020 add. Logcat has no info about kernel. Useadb shell dmesg
@assusdan sorry for being late, I'm working on my exams and I don't have to much time. NOw I will git push my changes to my kernel and you can see how I fixed the compilation error. Cheers
Well. I'm waiting
Даня привет. Че происходит, почему я уведомления получаю из этой вашей беседы?
@dee3000 это потому что мы твой ник упомянули. Заигнорь. @dee3000 that's because we said your nickname. Forgot it.
@Pablito2020 any news?
@assusdan Finally I fixed touch. Now the big problems are that SDCard storage is not mounting and the rear camera is not working and the frontal camera is inverted....
Thanks in advance
What about sdcard, here is a fix: https://github.com/Pablito2020/cyanogenmod_kernel_bq_krillin/blob/cm-13.0/arch/arm/mach-mt6582/alps/core/board.c#L576 , https://github.com/Pablito2020/cyanogenmod_kernel_bq_krillin/blob/cm-13.0/arch/arm/mach-mt6582/alps/core/board.c#L620 - change to MSDC_CD_HIGH
about rear camera: build libs and add support in kernel, as always. I'll say you neccessary patchs to ALPS's source code to build camera libs. about frontal: I'll give you fix later, when I could code.
Okay, Thanks! I will try it @assusdan .
PS: How to boot cm14? TRy to boot it with this kernel and reboot to recovery...
Hope you can respond all my questions ;)
Thanks in advance
Flashlight depends on rear camera; I'll help you with inverted frontal later; I'll give you Cm14 patch later
Thanks for all @assusdan waiting for the cm14 patch and for the fix for rear camera and frontal inverted camera.
Hello! Is this kernel bootable on your device?