Please help to get JB kernel sources, we need this for CM10.1. OP is here: http://forum.xda-developers.com/showthread.php?t=2288883
Click to expand...
Click to collapse
Please post all non-dev questions and discussions here:
http://forum.xda-developers.com/showthread.php?t=2194497
Click to expand...
Click to collapse
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Download:
alpha 2.0
Click to expand...
Click to collapse
Requirements:
Unlocked bootloader
CWM recovery installed
Install:
Download the rom
Extract the boot.img
Copy the rom to your sdcard
Go to recovery and flash the rom
Wipe data
Reboot to bootloader/fastboot
Install boot.img with fastboot ---> fastboot flash boot boot.img
Reboot and enjoy!
Sources:
All sources avaliable here: https://github.com/ProtouProject
Use this for init the repo: "repo init -u git://github.com/ProtouProject/android.git -b ics"
If you have any fix/patch, just make a pull request or send me a PM!
Credits:
neXus PRIME
sakindia123
Working:
Touchscreen
Lights
GSM & data
Camera
Audio
Headset detect
Sensors
External SD
Menu button
Not working:
Wifi
Bluetooth
Video recording
Audio recording
Internal memory
Changelog:
alpha 2.0:
GSM & data fixed
Camera fixed
Audio fixed
External sdcard fixed
Releasetools fixed
Sensors fixed
HTC log fixed
Menu button fixed
alpha 1.0:
First release
Support
Support:
If you would like to support me and the development, you can donate to me here:
Donators: (Thank you guys )
@vogonpoetlaureate
[*]@simaka
atis112 said:
Working:
Touchscreen
Lights
Not working:
Everything else...
Click to expand...
Click to collapse
Great Job bro! Too bad the camera's dead
@Atis112, is it possible the WiFi has something to do with the radio? Or is it kernel related?
MaartenXDA said:
@Atis112, is it possible the WiFi has something to do with the radio? Or is it kernel related?
Click to expand...
Click to collapse
Mostly its kernel related. Just maybe.
On the rom radio you had the driver of bluethooth wifi 3g gprs gms/cdma all hardware used for communicate.
So basicaly change or update the radio may improve the compatibility and working with a rom.
Generaly on a kernel you can include drivers hardware code. for a best compatility we can imagine extrac drivers from ruu and script those driver on a kernel.
Guys calm down. All the fixes will come soon enough.
Atis kept the device.mk/boardconfig.mk as small as possible just to make it boot. He'll add the required libs one by one as they work.
Read the device/board mk files and you'll pretty much figure out why wifi or other stuff is not working.
Dont make wild guesses, (almost) all things are under his control
Regards
Subscribing, gonna flash it tomorrow for sh*ts and giggles
AW: [ROM][ICS]Unofficial CyanogenMod9 alpha1.0[17/03/2013]
Finally a CM Rom cant wait for the full-working version :thumbup:
Sent from my HTC Desire X using xda app-developers app
I am having a tingling sensation that something big is coming...
myusernamewastoken said:
I am having a tingling sensation that something big is coming...
Click to expand...
Click to collapse
github is quiet but I don't know maybe he will release and update sources simultaneously.:fingers-crossed:
EDIT: read around a bit wont be surprised with some massive development cause most of the stuff(practically everything) is disabled.
also I hav a question and its a genuiene query no malice of any kind but why is the board defined as msm7x27a rather than 8225 right ?
and the gpu is adreno 200 rather than 203 ?
and do we have a brodcom wifi chip(cause I saw yasir say about the pico sources and they have this chip) might b some things you possibly overlooked or maybe I really didnt understand their purpose(so please explain...?)
Re: [ROM][ICS]Unofficial CyanogenMod9 alpha1.0[17/03/2013]
Google msm8225 and you'll get that it is built in a way as to make it fully backward compatible with msm7x27a.... That's why if we define board as 7x27a, it still works.
Same goes for pico, lge p700, desire sv. And other phones.
Sent from my HTC Desire X
neXus PRIME said:
Google msm8225 and you'll get that it is built in a way as to make it fully backward compatible with msm7x27a.... That's why if we define board as 7x27a, it still works.
Same goes for pico, lge p700, desire sv. And other phones.
Sent from my HTC Desire X
Click to expand...
Click to collapse
yes I read that somewhere a long time ago(and promptly forgot) guess that would help when submiting upstream to make the Desire X officially supported(but I'm getting ahead of myself here)
anyway this is revolutionary for our device and am glad that we got to cm so early on.:good:
happy for the community
Well, seems like yasir and me weren't reading too much into the whole issue of cm booting (as loirr) said
Happy to see it worked, just got a new comp, now we're getting CM - can't wait ! - tried the alpha CM and I love the look ...
cheers and thanks to yasir for his awesome work onthe kernel and TWRP, cpkv5 for the best custom ROM for DX out there and everyone else for appreciating the DX - it's a very good phone, and only gonna get better :good:
Re: [ROM][ICS]Unofficial CyanogenMod9 alpha1.0[17/03/2013]
For WiFi and so on, you need to use your modules from your kernel.
Lloir said:
For WiFi and so on, you need to use your modules from your kernel.
Click to expand...
Click to collapse
We don't need modules. everything included in the kernel. (But i will add them as modules again later)
atis112 said:
We don't need modules. everything included in the kernel. (But i will add them as modules again later)
Click to expand...
Click to collapse
You kernel defconfig files are pointing to wrong files in case you use separate modules
https://github.com/ProtouProject/an...u/blob/ics/arch/arm/configs/atis112_defconfig
CONFIG_BCMDHD_FW_PATH="/system/etc/firmware/fw_bcm4330.bin"
Should be
CONFIG_BCMDHD_FW_PATH="/system/etc/firmware/fw_bcm4330_b2.bin"
Atleast its my guess.
Also, similar file name errors in Boardconfig.mk
BOARD_WPA_SUPPLICANT_DRIVER := WEXT
WPA_SUPPLICANT_VERSION := VER_0_8_X
BOARD_WPA_SUPPLICANT_PRIVATE_LIB := lib_driver_cmd_wext
BOARD_WLAN_DEVICE := bcm4330
WIFI_DRIVER_MODULE_PATH := "/system/lib/modules/bcm4330.ko" (Should be bcmdhd.ko)
WIFI_DRIVER_FW_PATH_STA := "/system/etc/firmware/fw_bcm4330b2.bin" (Should be fw_bcm4330_b2.bin)
WIFI_DRIVER_FW_PATH_AP := "/system/etc/firmware/fw_bcm4330b2_apsta.bin" (Should be fw_bcm4330_b2_apsta.bin)
WIFI_DRIVER_MODULE_NAME := "bcm4330"
WIFI_DRIVER_MODULE_ARG := "firmware_path=/system/etc/firmware/fw_bcm4330b2.bin (fw_bcm4330_b2.bin) nvram_path=/proc/calibration iface_name=eth0 (wlan))"
I might be TOTALLY wrong about everything, so dont mind it.
Regards
Yasir
neXus PRIME said:
You kernel defconfig files are pointing to wrong files in case you use separate modules
https://github.com/ProtouProject/an...u/blob/ics/arch/arm/configs/atis112_defconfig
CONFIG_BCMDHD_FW_PATH="/system/etc/firmware/fw_bcm4330.bin"
Should be
CONFIG_BCMDHD_FW_PATH="/system/etc/firmware/fw_bcm4330_b2.bin"
Atleast its my guess.
Also, similar file name errors in Boardconfig.mk
BOARD_WPA_SUPPLICANT_DRIVER := WEXT
WPA_SUPPLICANT_VERSION := VER_0_8_X
BOARD_WPA_SUPPLICANT_PRIVATE_LIB := lib_driver_cmd_wext
BOARD_WLAN_DEVICE := bcm4330
WIFI_DRIVER_MODULE_PATH := "/system/lib/modules/bcm4330.ko" (Should be bcmdhd.ko)
WIFI_DRIVER_FW_PATH_STA := "/system/etc/firmware/fw_bcm4330b2.bin" (Should be fw_bcm4330_b2.bin)
WIFI_DRIVER_FW_PATH_AP := "/system/etc/firmware/fw_bcm4330b2_apsta.bin" (Should be fw_bcm4330_b2_apsta.bin)
WIFI_DRIVER_MODULE_NAME := "bcm4330"
WIFI_DRIVER_MODULE_ARG := "firmware_path=/system/etc/firmware/fw_bcm4330b2.bin (fw_bcm4330_b2.bin) nvram_path=/proc/calibration iface_name=eth0 (wlan))"
I might be TOTALLY wrong about everything, so dont mind it.
Regards
Yasir
Click to expand...
Click to collapse
I will check it later.
But i already fixed some things:
Sensor
Audio
External SD
HTC log, You will need this too if you want to build AOKP or PA because some prop lib wont working without this.
Related
Hey guys. I have a HTC Desire which is unsupported by Paranoid Android on it's list of supported devices.
Seeing as I've only got my feet wet in the world of android development by building CM from source.
I now want to build Paranoid Android from source on my HTC Desire. Seeing as it is unsupported from PA I have downloaded the PA source and I now need to merge it with the Evervolv source as the Evervolv source is the one built for Jellybean to work on the Desire!
Thanks for your help guys!
topgeardave said:
Hey guys. I have a HTC Desire which is unsupported by Paranoid Android on it's list of supported devices.
Seeing as I've only got my feet wet in the world of android development by building CM from source.
I now want to build Paranoid Android from source on my HTC Desire. Seeing as it is unsupported from PA I have downloaded the PA source and I now need to merge it with the Evervolv source as the Evervolv source is the one built for Jellybean to work on the Desire!
Thanks for your help guys!
Click to expand...
Click to collapse
There's instructions on paranooid androids website or github...I don't remember which one....
Basically you sync paranoid android source then you add your device tree/proprietary/kernel
Then you build
It's the same process as cyanogenmod except you use PA source instead of CM source
Sent from my HTC PH39100 using Tapatalk 2
mg2195 said:
There's instructions on paranooid androids website or github...I don't remember which one....
Basically you sync paranoid android source then you add your device tree/proprietary/kernel
Then you build
It's the same process as cyanogenmod except you use PA source instead of CM source
Sent from my HTC PH39100 using Tapatalk 2
Click to expand...
Click to collapse
This. Assuming they are setup like most other Android distros, you just pull their source, grab a device/proprietary folder for you device and you are good to go. You will of course need to fix any issues that arise while compiling but that is where you should start.
Thanks guys! You're the best! I'll try it and if I have any problems compiling I'll let you know
What would I do once I've cloned all necessary device files?
Hey guys, I've merged the cm10 files needed to get it compiling. When I tried compiling I've got this error whilst building. Any help would be much appreciated
find: ‘src’: No such file or directory
*** Overlay change detected, clean shared intermediate files...
*** rm -rf out/target/common/obj/APPS/Settings_intermediates out/target/common/obj/APPS/framework-res_intermediates out/target/common/obj/APPS/Mms_intermediates out/target/common/obj/APPS/Phone_intermediates out/target/common/obj/APPS/Gallery2_intermediates out/target/common/obj/APPS/LatinIME_intermediates out/target/common/obj/APPS/SettingsProvider_intermediates out/target/common/obj/APPS/SystemUI_intermediates
PRODUCT_COPY_FILES vendor/pa/prebuilt/common/bin/backuptool.sh:system/bin/backuptool.sh ignored.
PRODUCT_COPY_FILES vendor/pa/prebuilt/common/apk/GooManager.apk:system/app/GooManager.apk ignored.
PRODUCT_COPY_FILES vendor/pa/prebuilt/common/bootanimation/HDPI.zip:system/media/bootanimation.zip ignored.
PRODUCT_COPY_FILES vendor/pa/prebuilt/pa_bravo.conf:system/etc/paranoid/properties.conf ignored.
PRODUCT_COPY_FILES vendor/pa/prebuilt/pa_bravo.conf:system/etc/paranoid/backup.conf ignored.
No private recovery resources for TARGET_DEVICE bravo
build/core/tasks/kernel.mk:44: ***************************************************************
build/core/tasks/kernel.mk:45: * Using prebuilt kernel binary instead of source *
build/core/tasks/kernel.mk:46: * THIS IS DEPRECATED, AND WILL BE DISCONTINUED *
build/core/tasks/kernel.mk:47: * Please configure your device to download the kernel *
build/core/tasks/kernel.mk:48: * source repository to kernel/htc/qsd8k
build/core/tasks/kernel.mk:49: * See http://wiki.cyanogenmod.com/wiki/Integrated_kernel_building
build/core/tasks/kernel.mk:50: * for more information *
build/core/tasks/kernel.mk:51: ***************************************************************
make: *** No rule to make target `out/target/product/bravo/kernel', needed by `out/target/product/bravo/boot.img'. Stop.
Total time elapsed: 0 minutes (52.929561210 seconds)
Click to expand...
Click to collapse
topgeardave said:
Hey guys, I've merged the cm10 files needed to get it compiling. When I tried compiling I've got this error whilst building. Any help would be much appreciated
Click to expand...
Click to collapse
Is your device support by CM9/in development for CM10? Can you add the inline kernel building feature? Also double check all the paths/filenames involved here to make sure they are valid.
thewadegeek said:
Is your device support by CM9/in development for CM10? Can you add the inline kernel building feature? Also double check all the paths/filenames involved here to make sure they are valid.
Click to expand...
Click to collapse
It's not supported by CM themselves but another Dev has compiled it from source and I have cloned his repositories. Where can I place a kernel source inside my PA source? In the htc/bravo folder? And how can I add the inline kernel building feature?
Look at a currently supported device for details I'm how to do it, or maybe lithid can help you here. I currently don't have access to all my crap though, so I can't get the information. Have you checked to make sure your kernel is named appropriately and in the correct location? Even though it's deprecated that method should work.
Sent from my SCH-R760 using Tapatalk 2
thewadegeek said:
Look at a currently supported device for details I'm how to do it, or maybe lithid can help you here. I currently don't have access to all my crap though, so I can't get the information. Have you checked to make sure your kernel is named appropriately and in the correct location? Even though it's deprecated that method should work.
Sent from my SCH-R760 using Tapatalk 2
Click to expand...
Click to collapse
Oh right ok, I'll try and ask a few HD2 devs on how they managed to build it from source. And how should I name the kernel source?
topgeardave said:
Oh right ok, I'll try and ask a few HD2 devs on how they managed to build it from source. And how should I name the kernel source?
Click to expand...
Click to collapse
You can name the folder whatever you want, it just needs to match whatever you put into your BoardConfig.Mk.
You'll need to add the following lines to is:
# Kernel Config
TARGET_KERNEL_SOURCE := path/to/your/kernel
TARGET_KERNEL_CONFIG := your_config_defconfig
thewadegeek said:
You can name the folder whatever you want, it just needs to match whatever you put into your BoardConfig.Mk.
You'll need to add the following lines to is:
# Kernel Config
TARGET_KERNEL_SOURCE := path/to/your/kernel
TARGET_KERNEL_CONFIG := your_config_defconfig
Click to expand...
Click to collapse
Thanks mate, I'll try that as soon as I get home as I'm at work at the moment. If I face any other problems, I'll let you guys know
I ran into that problem as well trying to compile PA for the Rezound, and it was just I had the kernel folder named wrong. I had to change /pa/kernel/htc/vigor to /pa/kernel/htc/vigor-3.0 but now Im running into more problems.
Optimized CyanogenMod 12 Android 5.0.2 Lollipop for the Redmi Note 4G(QCOM) brought to you by haoyangw
NOTE: This is for the QCOM variant of the Redmi Note, otherwise known as Redmi Note 4G, and NOT the MTK variant of the Redmi Note. In short, this ROM will NOT work on the MTK variant of Redmi Note 4G
NOTE: GApps is NOT provided, use any GApps package you can find. I would recommend Open GApps for Lollipop(link below).
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We're not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Version Number explanation is in the #2 post, changelog and device tree branches for my github repositories explanation is listed in the #3 post
Comment your reviews below or even better, PM me as I won't be regularly monitoring this thread. Thanks again! You will be listed in the credits too
Downloads
ROMs
All ScarletRice builds and addons(AndroidFileHost)
All ScarletRice builds and addons(BasketBuild)
ScarletRice selected builds and addons(XDA)
I don't have the time to link specific builds everytime there is a new one anymore, so unfortunately you all have to go into XDA downloads or AndroidFileHost folder and download the latest one. So sorry!
Recoveries(compiled by me )
CWM, Philz touch and twrp recoveries(AndroidFIleHost)
Addons(includes my custom kernels So keep an eye on it)
Addons(AndroidFileHost)
Addons(BasketBuild)
XDA Downloads(Addons and ROMs)
Older downloads:
ScarletRice Beta 0.1
ScarletRice Alpha 0.02: https://mega.co.nz/#!40cXxKQL!Dd-pk41oJOPJbhLILLGnS9yAE09ly6nKIIfgRzLCpak
ScarletRice Beta 0.1 AndroidFileHost mirror
ScarletRice Alpha 0.01: https://mega.co.nz/#!EgN1lIxY!n7f-o9bujoh6eAu0H8iuaiiGrQ1fG3OCxYoodAyuLSA
The battery life so far on this ROM is amazing! It doesn't face any kind of drain issues so far, except maybe for the infamous Google Play Services wakelocks. To quote:
Swordsman0815 said:
Battery life seems to be amazing... I am off the charger for over 12hrs and still have around 46% of charge left
Click to expand...
Click to collapse
Well good/bad battery life is actually really subjective, some people might have higher standards due to their past experience etc so it all depends! Try it out yourself and see
Not working:
Cast screen/Screen mirroring
FM Radio
Compass
Back Camera and front camera video Fixed now
Buggy power detection Fixed
Flashing red borders(chrome only) Fixed
Working:
Back and Front camera(video + photo)(wipe dalvik if doesn't work)
Wifi
Headphones
Touch
Auto brightness
Gyroscope
Alarms
Location
Double tap 2 wake(built into ROM zip's kernel and my custom kernels) Removed due to bugs
Anything else
Installation
Download the ROM from the link above
Download GApps package for Lollipop(Recommended: OpenGapps, for 4.4+ and all architectures)
Download any addons/custom kernels from links above or anywhere else
Put the zip files on your SDCard
Reboot in Recovery(choose one of the 3 above if you wish )
Wipe Data / Factory Reset(ONLY IF you are coming from another ROM/upgrading to beta 0.2.x to get working camera)
Recommended: Wipe dalvik-cache
Select "Install zip from SDCard"
Choose CM12 zip file
Select "Install zip from SDCard"
Choose GApps zip file
Optional: Select "Install zip from SDCard"
Optional: Choose addon/kernel zip
Reboot system
Reporting bugs
If you have found a bug, make sure you fill up a form here: Google Form: Bug reporting This allows me to easily track all bugs reported without scanning the whole thread. Do make SURE that you fill in a VERY detailed description! And don't forget logs! For a tutorial on how to get logs, here you go! Log tutorial Of course, feel free to still report bugs here as I will be monitoring this thread But you MUST fill up a form, reporting on XDA is optional
Sources
Manifest
For those who would like a shortcut to sync all the neccessary repos to build stable cm12, just download/copy the contents of this file into .repo/local_manifest: Local manifest xml and the next time you repo sync everything will be there Then just 'lunch cm_dior-userdebug' and 'make -j4 otapackage'
Manually
I've finally given up making my own trees and fixing the annoying bugs in Xiaomi's kernel sources, so here are all the working tree/sources brought to you by our awesome devs! I take no credit for this! GO AND THANK THEM!
Edit: I've made some minor updates and fixes to the trees, but still credit goes to them!
Updated trees(updated by me but originally created by the following devs)
Device tree
Kernel source
Vendor tree(a.k.a. prebuilt/proprietary blobs tree)
Original trees:
@Silesh.Nair's device tree
@Silesh.Nair's vendor tree
@audahadi's kernel source
@stane1983's kernel source
I've uploaded the device tree I used to compile twrp to my device tree above, the branch name is 'twrp'. It's based on syhost's outdated twrp device tree, with problematic flags removed to fix bugs and also translated back into english, so there you go!
NOTE: Currently this device tree is ONLY for compiling CM12, you can face all kinds of build errors if you compile CM11 with it. For example, you will not be able to compile sepolicy in the device tree. You have been warned. Have fun building
Credits
CyanogenMod
XDA
syhost(for his twrp device tree)
Stane1983(for his first working trees)
Silesh.Nair(for his updated trees)
sm_94(for his suggestions on fixes)
And everyone else who contributed logcats and findings and worked hard for the better of all Note 4G users. Thanks!
XDA:DevDB Information
ScarletRice, ROM for the Xiaomi Redmi Note
Contributors
haoyangw
Silesh.Nair
sm_94
stane1983
sadlmadl(Contributed best and most logs and reports)
Swordsman0815(Contribute working/not working reports and logs )
@suhasgta(contributed logs, suggestions and reports )
And all others who contributed logs and reports! Thanks A LOT!
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Stable
Created 2015-03-17
Last Updated 2015-11-29
Version numbers
Version Number explanation
There will be 4 naming conventions for builds, namely Alpha, Beta, Release Candidate and Stable.
Alpha - Build is NOT tested and may not boot
Beta - Build has been tested and boots up, but there are many device-related issues and bugs
Release Candidate, or RC - Build has been tested and device-related issues and most bugs are fixed
Stable - No more than 3 minor bugs and no performance or battery drain issues(caused by ROM on my side)
Changelog + Github Repos' Branches
Changelog:
1.0
Device:
Fixed front and back camera(photo+video) as well as video playback
ROM:
Optimized with O3 and graphite
Enabled optimizing compiler for ART
Kernel:
Added more cpu governors(total 23)
Added gamma control
Added faux sound control
Added alucard and intelli hotplug
Compiled with O2
Maybe more(can't remember)
0.2.4
Device:
Merged changes from sileshn
Fixed some more webview problems(that were not caused by the previous absence of webview completely)
Added FM blobs, FM radio should work properly now (also means you'll need my new local manifest to sync qcom's fm stuff)
Tweaked media configs, hopefully improves some stuff(but playing youtube videos and the like still not working )
0.2.3.1
ROM:
Fixed superuser
Device:
Fixed google play store crashes
Tweaked button brightness, hopefully it isn't too bright nor dim
Old builds' changelogs:
0.2.3
ROM:
Compiled with user instead of eng, should result in increased performance!
Fixed performance issues! Now it's faster than syhost's cm12.1! You know what that means? if we build for cm12.1, then bam, performance will be faster than a rocket! And did I mention Justarchi optimizations and graphite flags?
Many vulnerability fixes like the new Serialization vulnerability
Device:
Bright button lights should now be fixed No light at all Sorry!
Location should be working properly now, without relying on Xiaomi's partners like Qualcomm
Fixed annoying flashing red borders ONCE AND FOR ALL!
0.2.2
Clean install(i.e. with factory reset required for working front camera)
ROM:
Fix Gapps problems(e.g. Play store and google keyboard crashes) by removing system jar compression tweak
Improved performance a little
0.2.1
ROM:
Fix prebuilt WebView that caused browser crashes
Add some missing blobs to increase performance
0.2.0
ROM:
Integrate home button fix
Upstream fixes(most notably stagefright vulnerability fix)
Use prebuilt WebView
System jars 0 compression(store only), but causes problems
Add Open Camera as system app
0.1
ROM:
Finally boots
Fix front camera
Device:
Use Silesh.Nair's device tree to fix problems and make ROM boot
Custom kernel:
V1.2.4:
Updated intelliactive and intellidemand to faux's latest sources, no longer using some outdated files that I got because of laziness So intelliactive is finally working properly(no reboot), and also better performance/battery etc
Added intelli hotplug driver, do check it out!
Updated simple and simpleondemand gpu governors, but they still don't work So do AVOID them!
V1:
Add intelliactive and smartmax governors
Add SIO and ZEN I/O schedulers
Experimental fix for back camera
Github Repository Branch Explanations:
Kernel source repo
cm-12.0: stock cm12 kernel without extra governors and I/O schedulers
cm-12.0-custom: CM12 custom kernel with extra governors and I/O schedulers
stock: Original kernel source from Xiaomi with only fixes for compilation errors
cm-12.0-wip: latest fixes/additions for cm12 that may not work/compile successfully
Upcoming(when it appears on the kernel source repo, cm12.1 is coming ):
cm-12.1: CM12.1 custom kernel with extra governors and I/O schedulers
cm-12.1-custom: stock cm12.1 kernel without extra governors and I/O schedulers
wip-cm12.1: latest fixes/additions for cm12.1 that may not work/compile successfully
Hi, I tried your rom just now on my Redmi Note 4G but it doesn't boot at all.
I wouldn't mind being a tester! I'm installing now and I'll see how it works.
fix
what about camera. fixed or not yet
It's stuck on the MI boot screen.
Finaly
thanks haoyangw for this thread. I would to participate but I just a noob and don't have skill about devs . I just follow and subscribe this thread, hope you can fix any problem about this devices. :good:
i can also help testing,i have min knowledge about what a rom is and logcat.
robreyes07 said:
Hi, I tried your rom just now on my Redmi Note 4G but it doesn't boot at all.
Click to expand...
Click to collapse
Hi, can you send me a logcat please? Or install LiveBoot by ChainFire through recovery and post all the errors you see printed. Thanks a lot! Sorry if the ROM doesn't boot
Good to see someone is working on CM12 for our phone. I tried CM12 syhost version and it's awesome but camera doesn't work and I need it. If you manage to get camera to work that would be awesome.
Thanks for your work. You may want to check the source code for the official cm12 version of the htc desire 816. It has the same gpu/cpu combination so there must be some similarities.
What is the point of this thread when the rom doesn't even boot
i think,
shyampareek said:
What is the point of this thread when the rom doesn't even boot
Click to expand...
Click to collapse
I didn't know but i hv subscribe
shyampareek said:
What is the point of this thread when the rom doesn't even boot
Click to expand...
Click to collapse
The point is to encourage someone to work on device. Right now it gathers little to no interest at all.
shyampareek said:
What is the point of this thread when the ROM doesn't even boot
Click to expand...
Click to collapse
Point is to give support to developer, or this thread will die. I think u shouldn't be on this forum, so ungrateful
haoyangw said:
Hi, can you send me a logcat please? Or install LiveBoot by ChainFire through recovery and post all the errors you see printed. Thanks a lot! Sorry if the ROM doesn't boot
Click to expand...
Click to collapse
Sure, maybe this weekend kind of busy this workdays.
robreyes07 said:
Hi, I tried your rom just now on my Redmi Note 4G but it doesn't boot at all.
Click to expand...
Click to collapse
Nemado said:
Thanks for your work. You may want to check the source code for the official cm12 version of the htc desire 816. It has the same gpu/cpu combination so there must be some similarities.
Click to expand...
Click to collapse
Yeah I thought of that, I copied some bits from the desire 816 device tree for Redmi Note 4G. I've tried building recovery with my sources and device tree and the recovery works perfectly, so I think it must be something in the ROM that is the problem. I'll need a logcat for tracking the malfunctioning part.
robreyes07 said:
Sure, maybe this weekend kind of busy this workdays.
Click to expand...
Click to collapse
Thanks a lot! Hope I can get this ROM working soon, then our beloved device will get Lollipop sweetness.
Have you tried to compile kernel that xiaomi relased for our device?
What's up guys, even though this Nexus 4 is 4 years old, (pun not intended XD) it's still holding up strong and in time for some Nougat treatment. [emoji14]
Note: Most of the components are working and I believe that it is enough for daily tasks. However, YOU see whether it fits your needs or not.
Working:
- Audio
- Wi-Fi
- Bluetooth
- RIL
- H/W Acceleration
- USB
- GPS
- NFC
- Sensors
Semi-Working:
- Camera (Video recording stutters sometimes with some apps)
Not Working:
How to Flash:
1. Download Zip
2. Flash zip
3. Flash GApps
4. Wipe Data (If coming from anything other than 7.0)
4. Flash SuperSU (Optionnal, Uses systemless as a root method)
5. Profit
Note: You will see Fc's all along the setup, just skip them if shown. Also if Google Play Services is crashing, grant it the location permission in the settings.
Download:
AOSP 7.0 download folder
Mirror
Quanta:
Quanta V19 Test
GApps:
OpenGApps
Banks GApps
SuperSU: SuperSU Stable
Sources:
Device Tree
Kernel Source
Changelog, other stuff
Code:
V10 (18/12/16):
- Updated to Android 7.1.1
- Patched kernel with the latest security fixes.
V9: (14/10/16)
- Video recording on Camera2 partially fixed (Video shakes sometimes)
- Fixed stack trace for native processes
- Updated to October's Security patches
- Misc fixes
V8: (18/09/16)
- Kernel patched accordingly to September security fixes (Patches all Quadrooter exploits up to now)
- Fixed Torch
V7: (11/09/16)
- Updated to September security fixes (For real this time)
- Enabled H/W encoding for video recording
- Re-enabled navigation bar tweaks and night mode in SystemUI
- Fixed Google Play Services FC's using OpenGApps (For real also)
- Add possibility to change WebView provider
V6: (09/09/16)
- Updated to September security patches
- Fixed freezing while watching YouTube
- Attempt to enable LTE
- Hidden misc battery drain as it causes some misinterpretations
V5: (05/09/16)
- Enabled Doze for real this time
- Reverted a change that may have broke Camera
V4: (02/09/16)
- Fixed H/W video decoding for the most part
- Kernel: SDCard FS enabled
- Attempt to fix permissions for GApps
- Enabled Navigation Bar tweaks and Night mode in SystemUI Tuner.
V3: (30/08/16)
- Fixed Sensors
- Semi-Fixed camera
- Fixed MPDecision
- Enabled Doze
- Used Flo's developper preview N GPU drivers
V2: (28/08/16)
- Fixed audio
- Fixed GPS
- Fixed data connectivity
- Disabled the power toggle widget which caused Settings to crash on every boot
V1 (26/08/16):
- Initial release
Here's a video showing how to install the ROM. (Thanks @Swapnil Soni)
Here's another one with a little overview of it. (Thanks @DaKoin)
Build instructions:
Since some of you guys asked me how to build from scratch, I will give a walkthrough of what I mostly did.
Note that this is in no way a walkthrough in how to compile (there are several guides for that on XDA) but more a guide
on how I did my setup so you can replicate the AOSP builds on your device.
Here's what I did:
1. Download the latest AOSP revision for android-7.1 which is r6 at the time of this writing (replace with whatever required branch necessary)
Code:
repo init -u https://android.googlesource.com/platform/manifest -b refs/tags/android-7.1.1_r6
repo sync
2. Download the kernel source used for the build:
Code:
git clone https://github.com/zaclimon/android_kernel_google_msm -b mako_nougat
3. Once both sources has been downloaded, compile the kernel. Note that AOSP do have a kernel toolchain that you can use to compile
Code:
export CROSS_COMPILE "/path/to/aosp/prebuilts/gcc/linux-x86/arm/arm-eabi-4.8/bin/arm-eabi-"
make mako_defconfig
make -j$(grep -c processor /proc/cpuinfo)
4. Copy the arch/arm/boot/zImage file to the Android source into device/lge/mako-kernel
Note: You must create the said directories if they don't exist. You also must rename the file to kernel after copy.
5. Go back to the AOSP source, and download/update/replace the following repositories for each component (relative path):
Code:
device/lge:
git clone https://github.com/zaclimon/android_device_lge_mako mako
hardware/qcom:
git clone https://github.com/zaclimon/android_hardware_qcom_audio audio
git clone https://github.com/zaclimon/android_hardware_qcom_display display
git clone https://github.com/zaclimon/android_hardware_qcom_gps gps
git clone https://github.com/zaclimon/android_hardware_qcom_media media
vendor:
git clone https://github.com/zaclimon/android_vendor_lge lge
6. Apply the following patches to each of their respective repositories:
Code:
bionic:
https://github.com/LineageOS/android_bionic/commit/81af26a3a033723fb34ddf280e33a9d4a6ce82c4.patch
frameworks/base:
https://gist.github.com/zaclimon/bb39d7f5059b63e3add3b5cad15e87db
https://android-review.googlesource.com/#/c/147266/
system/sepolicy:
https://github.com/LineageOS/android_system_sepolicy/commit/10dd0402ab62aa1a6416d7ea549a6a3eea1c6ae4.patch
7. Increase RAM usage for Jack (Only if you have 6/8GB of RAM in your system)
Code:
export ANDROID_JACK_VM_ARGS="-Xmx4g -Dfile.encoding=UTF-8 -XX:+TieredCompilation"
8. Once all the patches have been applied, we can now proceed to compile the system.
Code:
. build/envsetup.sh && lunch aosp_mako-userdebug
make -j$(grep -c processor /proc/cpuinfo) otapackage
9. The build should be in out/target/product/mako
10. Flash and enjoy!!
You're the king, buddy! ?
P.
[sntfrmnxs⁴]
first
oops, second
Thanks @zaclimon and BTW wiping data is needed?
Nitin
nitin.chobhe said:
first
Nitin
Click to expand...
Click to collapse
Ha ha ! Almost.
Sent from my Nexus 4 using Tapatalk
You're great!!
nitin.chobhe said:
first
oops, second
Thanks @zaclimon and BTW wiping data is needed?
Nitin
Click to expand...
Click to collapse
It's not necessary per se because it should boot fine. That said, as always, it's recommended to wipe so random issues are less prone to happen.
Merci infiniement !!!
Just downloaded, and works, I think we need to changes the permission so that google play service not crashing
Its people like you who make this world a better place, thank you very much!
zaclimon said:
It's not necessary per se because it should boot fine. That said, as always, it's recommended to wipe so random issues are less prone to happen.
Click to expand...
Click to collapse
Thanks man! One last question - I need N gapps for this, right?
Open gapps should be fine?
@cqloveqc what gapps did you use? And what permissions need to be modified?
Nitin
funthomasz said:
Its people like you who make this world a better place, thank you very much!
Click to expand...
Click to collapse
nitin.chobhe said:
Thanks man! One last question - I need N gapps for this, right?
Open gapps should be fine?
@cqloveqc what gapps did you use? And what permissions need to be modified?
Nitin
Click to expand...
Click to collapse
Please everybody read the note (I should make it bold so people can see it)
"Note:You will see Fc's all along the setup, just skip them if shown. Also if Google Play Services is crashing, grant it the location permission in the settings. I'm also surprised to say that even with your data not wiped, it's working."
I am coming from the fake Nexus Rom aka I do not have a custom bootloader yet. What bootloader is the best to go with?
Could someone write me a quick instruction how to get started with my situation. I bet there are a lot coming from fake nexus.
Thanks for the great work!!
wow! cool zaclimon, so quanta is now N compatible i guess? haha, gj, if i'll find any kind of fix for something, i'll pull request, and thanks alot!
aabuk said:
wow! cool zaclimon, so quanta is now N compatible i guess? haha, gj, if i'll find any kind of fix for something, i'll pull request, and thanks alot!
Click to expand...
Click to collapse
I compiled a stock kernel as I wanted to start off a fresh base if ever others wanted to use a custom kernel. (Including myself with Quanta) It is patched with Google's latest updates.
I could compile a build of Quanta and incorporate the patches required to boot Nougat but it wouldn't be fair lool.
zaclimon said:
Please everybody read the note (I should make it bold so people can see it)
"Note:You will see Fc's all along the setup, just skip them if shown. Also if Google Play Services is crashing, grant it the location permission in the settings. I'm also surprised to say that even with your data not wiped, it's working."
Click to expand...
Click to collapse
I'm using the open gapps 7.0 arm version, and after change the app permission, all is good so far
And another sergestion, can we change the original LCD density to 240 instead of the default 320 ?
This change make the desktop more attractive.
zaclimon said:
I compiled a stock kernel as I wanted to start off a fresh base if ever others wanted to use a custom kernel. (Including myself with Quanta) It is patched with Google's latest updates.
I could compile a build of Quanta and incorporate the patches required to boot Nougat but it wouldn't be fair lool.
Click to expand...
Click to collapse
hahaha, okie, atleast i got some space to look at dem kernelzz, thanks for echo
cqloveqc said:
I'm using the open gapps 7.0 arm version, and after change the app permission, all is good so far
And another sergestion, can we change the original LCD density to 240 instead of the default 320 ?
This change make the desktop more attractive.
Click to expand...
Click to collapse
This has been allowed always from build.prop, did you try that?
P.
[sntfrmnxs⁴]
Gu$houn* said:
This has been allowed always from build.prop, did you try that?
P.
[sntfrmnxs⁴]
Click to expand...
Click to collapse
Yes, I've tried that by using a es file manager, but if we can make the 240 default, we don't need to make change anymore
Damn I'm late to the party, downloading now !
And thanks a ton @zaclimon for keeping mako alive, you're the man !
@zaclimon nice work.. keep it clean please
Hello,
I've started to bring the ROM forward to LineageOS X.x for the G850F. If anybody knows how to port a ROM or knows C/C++ and want to work together, feel free to contact me! Reading and understanding strace output is essential.
SOURCES
I will post my progress in this thread.
I already booted it but it has many bugs : Ril, Camera, Etc...
나의 IM-100S 의 Tapatalk에서 보냄
good job bros keep going
SerenityS said:
I already booted it but it has many bugs : Ril, Camera, Etc...
나의 IM-100S 의 Tapatalk에서 보냄
Click to expand...
Click to collapse
So you already fixed ril.h, kernel build issues, SlteRIL.h, gralloc.h ... ???
modpunk said:
So you already fixed ril.h, kernel build issues, SlteRIL.h, gralloc.h ... ???
Click to expand...
Click to collapse
Check this - https://github.com/SerenityS/android_device_samsung_slte
Im using CM13 kernel source with SELinux permissive , CM13 vendors.
It has little bit dirty commit status & sources because i try many things to fix errors.
SerenityS said:
Check this - https://github.com/SerenityS/android_device_samsung_slte
Im using CM13 kernel source with SELinux permissive , CM13 vendors.
It has little bit dirty commit status & sources because i try many things to fix errors.
Click to expand...
Click to collapse
I've started too, the main repo is now here:
https://git.cryptomilk.org/projects/android/android_device_samsung_sltexx.git/
The kernel already has all the fixes and compiles.
I would be great if you could start again based on my android_device_samsung_sltexx.git branch and we work together to get things done. There is #cyanogenmod-exynos5 on irc.freenode.net for developers.
A lot of stuff will not work, because the features have not been ported to cm-14.1 yet. For example the Samsung camera code is not in framworks_av, color support is missing etc.
So the first steps are just to get it compiling.
Next:
Update ril.h (this is a manual task which needs to be done carefully)
Update sepolicy
modpunk said:
A lot of stuff will not work, because the features have not been ported to cm-14.1 yet. For example the Samsung camera code is not in framworks_av, color support is missing etc.
So the first steps are just to get it compiling.
Next:
Update ril.h (this is a manual task which needs to be done carefully)
Update sepolicy
Click to expand...
Click to collapse
https://github.com/SerenityS/android_device_samsung_slte
In branch cm-14.1, I updated ril.h & some other fixs, so we need to verify it.
+ source are based on your cm-14.1
SerenityS said:
https://github.com/SerenityS/android_device_samsung_slte
In branch cm-14.1, I updated ril.h & some other fixs, so we need to verify it.
+ source are based on your cm-14.1
Click to expand...
Click to collapse
Yes, I've looked into your changes already but a lot of some are not really correct.
SLTE doesn't need a modemloader, this is only required for treltexx and gts2 devices. We also do not have to set the hwrevison for cbd.
I like your ril.h changes, they are small and easy to review! Great work!
I review and cherry-pick them tomorrow. I don't have time today.
Thanks for your help!
That will be great!
modpunk said:
Yes, I've looked into your changes already but a lot of some are not really correct.
SLTE doesn't need a modemloader, this is only required for treltexx and gts2 devices. We also do not have to set the hwrevison for cbd.
I like your ril.h changes, they are small and easy to review! Great work!
I review and cherry-pick them tomorrow. I don't have time today.
Thanks for your help!
Click to expand...
Click to collapse
Okay I revert commits what we doesnt need.
I've just tried to test about seclabels and domain_deprecated just now, but I think it doesn't need now.
I don't know why it work soon without that patches, maybe there is something about the work at Cyanogen Team.
Now I'm in clean build, I'll let you know that we need patches surely when the build is done.
+ Please check my hardware_5430 repo and vendor repo.
Mobicore works without any error (according to logs).
@SerenityS can you tell me what works and what doesn't so far:
RIL (radio)
phone calls
Wifi
Camera
Audio
...
modpunk said:
@SerenityS can you tell me what works and what doesn't so far:
RIL (radio)
phone calls
Wifi
Camera
Audio
...
Click to expand...
Click to collapse
No problem.
I will rebuild with your source and notice which function working or not working.
modpunk said:
@SerenityS can you tell me what works and what doesn't so far:
RIL (radio)
phone calls
Wifi
Camera
Audio
...
Click to expand...
Click to collapse
Work
WIFI
Bluetooth
Audio
NFC
etc,,
Not work
RIL (slte.java?)
Camera (SHIM not working properly now + maybe more framework's problem)
GPS (Need hexedit : https://github.com/TheMuppets/propr...mmit/976064c4c69acbb91c8355b09c0c7645ba6cd76d)
In cm-14.1_dev branch
Fix more sepolicy denied (Fix for CBD - now can working cpboot service normally)
Fix settings FC
Update README
Fix module name for stlport (I don't know why you using stlport instead of libstlport)
logcat : https://gist.github.com/SerenityS/d437342e6516461b402cde28aead6b1f
SerenityS said:
Work
WIFI
Bluetooth
Audio
NFC
etc,,
Not work
RIL (slte.java?)
Camera (SHIM not working properly now + maybe more framework's problem)
GPS (Need hexedit : https://github.com/TheMuppets/propr...mmit/976064c4c69acbb91c8355b09c0c7645ba6cd76d)
In cm-14.1_dev branch
Fix more sepolicy denied (Fix for CBD - now can working cpboot service normally)
Fix settings FC
Update README
Fix module name for stlport (I don't know why you using stlport instead of libstlport)
logcat : https://gist.github.com/SerenityS/d437342e6516461b402cde28aead6b1f
Click to expand...
Click to collapse
I will try to look into RIL tonight.
The Samsung Camera support in frameworks/av is missing.
Can you give more details on the GPS hexedit ...
modpunk said:
I will try to look into RIL tonight.
The Samsung Camera support in frameworks/av is missing.
Can you give more details on the GPS hexedit ...
Click to expand...
Click to collapse
Check commit message in themuppets'.
Now camera is working
+ If sepolicy permissive, video recording and shim working too.
So we need to fix sepolicy..
나의 IM-100S 의 Tapatalk에서 보냄
Is it usable now ? And where can i download the file if yes ?
What works:
RADIO
Camera taking normal picture
Audio
Wifi
What doesn't work:
GPS
Video decoding
Haven't tested more yet ... time to go to bed ...
@SerenityS Do you have gpsd working. Did you use a newer gpsd binary?
Hello!
This is a development thread for the project of upgrading of the Linux kernel for the U8500 platform.
Builds provided here (at the moment of writing this message) are not considered to be used as a daily driver, by any means, - these are rather a dev preview versions.
For now, there are a several LK builds (the highest currently supported kernel version is 3.10).
Because builds here are really not stable, I'll just leave a disclaimer here.
Code:
#include <std/disclaimer.h>
/*
* I am not responsible for bricked devices, dead SD cards, thermonuclear
* war, or the current economic crisis caused by you following these
* directions. YOU are choosing to make these modificiations, and
* if you point your finger at me for messing up your device, I will
* laugh at you.
*/
Working features
RIL
Camera (front & rear) - only works in <3.8
Video (playback & recording)
Audio (playback & recording)
Wifi
Bluetooth (broken in >=3.8, needs a workaround to manually startup)
USB, ADB
Tethering (not tested)
GPS (not tested)
Sensors
Known bugs
IRQs are mishandled by some device drivers (abb_btemp, abb_fg)
proximity sensor might not work (not tested, cause it's broken on my device)
deep sleep might not work at a times
MMC driver works unreliably in >=3.8 (contiguous usage might lead in a data corruption)
networking is not fully-functional (no mobile data)*
camera is broken in 3.8
*some other features of the android kernel might not present - it's because these kernels lacks android-specific patches.
Sources
LK 3.5
LK 3.6
LK 3.7
LK 3.8
LK 3.9
LK 3.10
Downloads
http://xda.mister-freeze.eu/XDA-files/ChronoMonochrome/misc/upgrading
Installation
install chrono kernel r5.2 or higher (this is needed to pick up the necessary scripts, incl. bootscripts, etc)
reboot to recovery
install build linked in "Downloads" section
Credits
Linux kernel development community
Google
ST-Ericcson
Samsung
Team Canjica
XDA:DevDB Information
U8500 Linux kernel upgrading project, Kernel for the Samsung Galaxy Ace II
Contributors
ChronoMonochrome
Kernel Special Features:
Version Information
Status: Alpha
Created 2017-05-09
Last Updated 2017-05-10
Reserved
Porting
The porting a higher kernel version tehnique I'll describe here is not intended to be a guide for dummies. I'll assume you've already built a kernel for your device, familiar with git versioning control usage and with some porting / coding tehniques.
Firstly, you need a cleaned source for your device. By "cleaned" I mean, there are no Linux incremental patches, android changes applied, manufacture-specific patches are avoided when possible and so on - you need sources as closest to a "pure" Linux kernel as possible. Otherwise you'll have later need to deal with conflicts resolution, you'll most likely be unable to resolve and the kernel won't boot.
So, without a further forewords, the tehnique is below:
1) As was previously mentioned, a clean kernel source is required, I'll assume we are starting from LK-3.4 ( https://github.com/ChronoMonochrome/Chrono_Kernel-1/commits/ea228ee0f5e9935841aff25c62fa163cd78dc01d ) and porting a higher kernel versions. A kernel base needs to be tested for any bugs just to distinguish, which bugs were intruduced during porting from those ones that already present in a kernel base.
2) The following steps will mostly use git bisect and git merge commands in order to merge all the changes from a higher kernel versions and help to find / resolve the bugs that were introduced. I suggest copying a git kernel repo that you use for building to a somewhere else, so you can use it , e.g. for grepping a different versions source, bisecting the revisions and so on, so don't need to bother messing up in your main repo that you use for build.
3) Firstly, lets just try to merge a higher kernel version, e.g. LK 3.5 by issuing a command git merge lk-3.5. You'll likely have a lot of merge conflicts, most of which you can resolve with resetting the paths to a some revision (either a kernel base - lk 3.4, or the version you do port, or just another suitable conflict resolution). So I suggest to write those paths to a text file, like so:
Code:
arch/arm/boot
arch/arm/mach-ux500
arch/arm/plat-nomadik
drivers/mmc
include/linux/mmc
drivers/usb
include/linux/usb
drivers/mfd
include/linux/mfd
...
Write all the paths you intend to reset to the kernel base, you most likely need to re-use them later. To actually perform a resetting source, you can issue
Code:
for path in $(cat file_with_a_paths.txt | xargs)
do
git checkout COMMIT $path
done
Be sure not to put to this file anything not the device-specific! Resetting to the kernel base should be avoided when possible (never ever try resetting archictecture-specific paths, e.g. arch/arm/kernel, arch/arm/mm and so on - unless you really know that kernel will boot thereafter, instead, you have to manually resolve such conflicts). Resolve any other conflicts by resetting paths to the porting source (e.g. LK 3.5).
Note. While resetting with a paths is probably not the most accurate tehnique, but people don't live that long to use more accurate approach, e.g. performing git cherry-pick for every upstream commit and then manually resolving all the conflicts, you'll just sooner or later get bothered and will abandon it.
4) When you're done with the previous steps you can try building kernel. You'll likely have a build errors - because some part of a source got not updated (e.g. the device-specific drivers), you need manually implement the necessary by a higher kernel version changes. Firstly check if an upstream kernel contains the necessary fixes (example: https://github.com/ChronoMonochrome/Chrono_Kernel-1/commit/9fae8c449b710f502662da1cbcf26ece5a098af9 , https://github.com/ChronoMonochrome/Chrono_Kernel-1/commit/fe027c25d6db0d100937deb5248e249ec5b24ee7 ). If the driver you are porting doesn't exist in the upstream, you can also try to find a similar change and mimic it: https://github.com/ChronoMonochrome/Chrono_Kernel-1/commit/5f2e7afbf2ac3284dc62b3d96a0627c7f99ed4e9 ( ported similarly to https://github.com/ChronoMonochrome/Chrono_Kernel-1/commit/526c597 ). In the worst case scenario you will need to examine the upstream changes and apply the changes so that the drivers complies to the upstream changes: https://github.com/ChronoMonochrome/Chrono_Kernel-1/commit/ea6432d167 .
5) If everything is done properly and you're lucky enough, the compiled kernel might already bootup. If not, you'll need to find a culprint that doesn't let the device to boot up. Switch to a copy of your kernel sources, reset the source to the base kernel version (e.g. LK 3.4), issue git bisect good, then issue git bisect bad lk-3.5, git will reset to a somewhere in a middle between of LK 3.4 and LK 3.5.
6) Save your changes in the kernel repo, by assigning a some branch to it, switch to the source base, merge all the fixes you've already introduced, then merge the revision you have got in the previous step by bisecting the tree. Repeat these steps until you'll find a first bad commit.
7) If you are already on this step, the most trickiest part starts here - testing (hopefully) working kernel for bugs (if any). While logs can be useful sometimes (so you can google the failing messages and find something useful), there are also many bugs you can find only performing git bisect tehnique decribed above.
The decribed algorithm only possible thanks to having a clean kernel source. The usage of this guide is not limited only to the kernel porting, it can be used on other projects as well, this is just what I've come across to, when I've ever started porting Linux kernel versions higher than LK3.4.
Reserved
I wonder if any of this expertise couldn't look pretty cool here too.
Wooooowwwewe
Oooh
Look whose good boys have been trying to win the STE mastermind prize as of lately
https://github.com/novathor-mainline/linux
https://git.kernel.org/pub/scm/linu...inux-nomadik.git/log/?h=ux500-skomer-v5.5-rc1
mirhl said:
Oooh
Look whose good boys have been trying to win the STE mastermind prize as of lately
https://github.com/novathor-mainline/linux
https://git.kernel.org/pub/scm/linu...inux-nomadik.git/log/?h=ux500-skomer-v5.5-rc1
Click to expand...
Click to collapse
Seriously!
mirhl said:
Oooh
Look whose good boys have been trying to win the STE mastermind prize as of lately
https://github.com/novathor-mainline/linux
https://git.kernel.org/pub/scm/linu...inux-nomadik.git/log/?h=ux500-skomer-v5.5-rc1
Click to expand...
Click to collapse
Wow, that's incredible
Exynos4412 already got some mainline support, it would be very nice to have this one supported too.
Aaaaand it's done, kinda.
ST-Ericsson NovaThor U8500 - postmarketOS
wiki.postmarketos.org
device/testing/linux-postmarketos-stericsson · master · postmarketOS / pmaports · GitLab
postmarketOS package build recipes
gitlab.com