I have been use Nook HD hummingbird for a while. There's no official CM rom for CM11 and later, I have tried CM11 which is buggy on HW video decode and it turns out that the last official CM (CM10.1) is so stable and it has the APPOPS!
As time pass by, I feel the performance of the rom is not good enough and I'm thinking about improving it. What I'm planning to do right now is compile a kernel only with CM10.1 source with Linaro toolchain and having -O3 and some other flags. However, it seems Nook HD and Nook HD+ has the same github for the kernel: http://www.github.com/cyanogenmod/android_kernel_bn_omap
Now I'm lost. Could anyone tell me why they share the same source?
Also, I heard that I need to extract some modules from the rom in order to have a recovery flashale zip. I haven't use any programming stuff in the last 12 years and I just find some tutorial about how to compile a kernel. If anyone can provide more information about how to use that source and make a flashable zip to apply the kernel to the CM rom will be greatly appreciated.
It will also be helpful if anyone can compile the kernel and apply some patches to it.
@amaces
@pinguy1982
Related
As a bit of background, I've been a kernel developer, embedded developer, and security researcher for 10+ years. I recently bought a Nook HD+ in BN's fire sale, mostly to teach myself about Android.
Does anyone know which branches of which repos are needed for CM 10.1 for the HD+? Likewise, manifests? I found the thread in the dev forum with build instructions for CM 10.0, but that doesn't necessarily help with 10.1. I found a number of repos that seem related, but I'd rather not guess. I'm particularly interested in pushing my own kernel and device driver builds.
Also, if the build instructions vary substantially from either the instructions in the verygreen's 10.0 thread or CM's standard build instructions, let me know how it's different.
Thanks in advance!
https://github.com/verygreen/android_device_bn_ovation/tree/cm-10.1-emmc
Very green is the guy to message about building for the HD+. He figured out the proper method to install to internal memory. He's very active on the forums so message him. He's looking for another dev to take the pressure off.
That cm10 thread is more applicable to SD card builds which are far inferior (mostly slower) to the newer emmc builds. He may have newer instructions for you.
Today I was trying to get an USB gamepad working (with no luck so far) but in my search I came across this CM change: http://review.cyanogenmod.org/#/c/63293/. Which would allow me to use my beloved WiiMote again, after it stopped working in android 4.3+. However in the comments of that commit it mentions that it requires kernel support.
Since I don't have the required hardware available atm to build it myself and don't have the required number of posts yet to ask in the KMA kernel thread itself I'm asking here:
Is anyone willing and able to compile a custom KMA kernel (http://forum.xda-developers.com/xperia-z/orig-development/kma-cm-11-101-sony-kernel-blobs-t2708325) with the above needed kernel configs enabled?
(Or at least reference my request/thread in the KMA thread, so if/when Thomas has the time and willingness he might be able to do it, so it becomes available for all his kernel users)
For reference:
The XDA thread for the Carbon rom is: http://forum.xda-developers.com/xperia-z/development/rom-carbon-rom-kk-unofficial-built-t2727592
An assumption I made is that the rom syncs with the CM11 CyanogenMod/android_external_bluetooth_bluedroid repository. If there is some way I can check this, please enlighten me where to look.
The needed kernel configs are: CONFIG_HIDRAW=y and CONFIG_HID_WIIMOTE=y.
I am basing my assumption that they are not enabled on the following:
For the KMA kernel:
https://github.com/daeiron/android_...b/cm-11.0-new/arch/arm/configs/yuga_defconfig
For the default kernel of my rom:
https://github.com/Alx31/android_ke....0/arch/arm/configs/cm_fusion3_yuga_defconfig
I've done some searching and found many dated and non-specific references on building AOSP for your device. I didn't even find anything referencing lollipop. I was wondering if somebody had written up some device specific instructions for the m7. I'm looking for information like pulling in the correct binaries and kernel source.
91ludesit said:
I've done some searching and found many dated and non-specific references on building AOSP for your device. I didn't even find anything referencing lollipop. I was wondering if somebody had written up some device specific instructions for the m7. I'm looking for information like pulling in the correct binaries and kernel source.
Click to expand...
Click to collapse
Which ROM are you looking for? I found the instructions for building CyanogenMod for the Nexus 6 to be helpful when I rebuilt CM7 for the original Droid Incredible. I don't see any reason it can't be extended to the M7 and lollipop--I can indicate the appropriate changes, if that's helpful.
wiki.cyanogenmod.org/w/Build_for_shamu
I'm just wanting to build straight from aosp with maybe a custom kernel source.
91ludesit said:
I'm just wanting to build straight from aosp with maybe a custom kernel source.
Click to expand...
Click to collapse
Ah. Well, I'm not an expert by any means, but I don't think it's quite that straightforward. The Android source released by Google has no support for any devices except Nexus devices. Various ROMs, CyanogenMod being the biggest, have created open-source device trees to support additional devices. In the source tree for the device that I built for (Droid Incredible), for example, there is code for "liblights", "libsensors", a kernel module, some firmware, some configuration tweaks for various system apps like Camera and Torch--and a configuration file for the kernel. So if you want to compile AOSP for your m7, you'll have to port all that code over to the AOSP tree.
You might find it valuable to try building CM12 for your device. If you can do that successfully, then you can start tweaking with the kernel config that CM provides to suit your needs. Building CM is also very well documented, and once you've done that, it's more clear how you'd go about trying to build AOSP, and you can use the stuff that CM has done to help you port to AOSP if you want.
Here's Google's information on building straight AOSP:
https://source.android.com/source/building-devices.html
Here are CyanogenMod's guides on building for m7 and tweaking the kernel config:
http://wiki.cyanogenmod.org/w/Build_for_m7
http://wiki.cyanogenmod.org/w/Doc:_integrated_kernel_building
Here is an XDA Developer guide to porting a device from one AOSP-based ROM to another:
http://xda-university.com/as-a-developer/porting-aosp-roms-using-source-code
Thanks for the info, that's what I was afraid of. I was wanting to build something like the Google play edition, but with all the latest security updates.
Hi all,
I have a rooted sm-t810 running stock marshmallow kernel 3.10.9.8374498 and I have been trying for a long time to add support for my xbox 360 wireless dongle and controllers.
I read a lot online about it and it seems that I need to load a specific module (xpad.ko) that is not available by default in my kernel.
However I have no idea where to find one that is compiled and compatible with my kernel and I have absolutely zero experience with compiling the kernel and/or the module from source, I wouldn't know where to begin or what to do about it.
From what I understand I should download the source of my kernel in a linux desktop, compile the module in it, copy the compiled module to my decide and run insmod it, but again, I have zero experience in all this.
Could somebody help me by giving me the compiled xpad.ko for my kernel?
If not, could you tell me step by step what should I do it to do it myself assuming im a total ignorant in kernels,modules, their compilation, the specifics about android, and everything around it ?(before yesterday I didn'teven ever rooted my tablet )
Thank you in advance if anybody is willing to help!
Cheers,
Mastro
Hello all! Hope all is well by you.
Based on what I've seen on this forum, the latest available kernel for the Touchpad is version 3.4.x - an older, unmaintained LTS branch, forked from Qualcomm's repos.
It seems that the mainline kernel source has code for the MSM8660 platform (what the Touchpad is based on) which leads me to wonder if it's possible to get a mainline kernel running on the device.
If my optimism serves me right, this could open the doors to running more non-Android systems on the device!
So far my attempts at booting my compilations have yielded nothing more than a hang at the HP splash logo. I've tried different GCC versions from Linaro (targeting arm-eabi) to no avail.
I'm unsure if I'd need to tweak any DTBs, though the 3.4 kernels don't seem to make use of those.
Of course a splash logo isn't too verbose... might anyone know if there's a serial console I can access over USB or some hidden port internally? Has anyone else made a similar attempt with any progress?
Cheers!
PieGuy128 said:
Hello all! Hope all is well by you.
Based on what I've seen on this forum, the latest available kernel for the Touchpad is version 3.4.x - an older, unmaintained LTS branch, forked from Qualcomm's repos.
It seems that the mainline kernel source has code for the MSM8660 platform (what the Touchpad is based on) which leads me to wonder if it's possible to get a mainline kernel running on the device.
If my optimism serves me right, this could open the doors to running more non-Android systems on the device!
So far my attempts at booting my compilations have yielded nothing more than a hang at the HP splash logo. I've tried different GCC versions from Linaro (targeting arm-eabi) to no avail.
I'm unsure if I'd need to tweak any DTBs, though the 3.4 kernels don't seem to make use of those.
Of course a splash logo isn't too verbose... might anyone know if there's a serial console I can access over USB or some hidden port internally? Has anyone else made a similar attempt with any progress?
Cheers!
Click to expand...
Click to collapse
I am not an expert, but have learned a lot by tweaking the kernel for the Hp Touchpad. To my basic understating none of the native driver codes were release as they are not "open source". How the developers got it working is by tweaking the hardware from what is "based on". If the drivers where open source, it could possible be more helpful on getting a lot more done. All I can do is provide some links from others that had tried:
The LuneOS is using the same kernel branch as Android, but there is no development for the kernel:
https://www.webos-ports.org/wiki/Main_Page
https://www.webos-ports.org/wiki/Main_Page
It will be great to have a kernel to run Linux natively.
Here are some work around that others had used:
https://github.com/mikestaszel/ArchLinuxARM-TouchPad
https://github.com/CalcProgrammer1/kernel_tenderloin_debian
https://forum.xda-developers.com/showthread.php?t=2761381
I did the following videos running Ubuntu (arm) as Chroot and is very fast !
https://www.youtube.com/channel/UCKoir6bzzPU-Uq9UjcRR3hw
Good luck learning!
@PieGuy128
Take a look at this post from @elginsk8r about a possible 5.0 Kernel:
There is a 5.0 kernel floating around that looks promising (uses mesa rather than proprietary blobs for display) albeit missing some key hardware support in it's current state. If anyone would like to take a look at the kernel sources and see what can be done it can be found here https://github.com/flto/linux/tree/msm8660. Building and booting instructions are here https://github.com/flto/linux/wiki
original post:
https://forum.xda-developers.com/showpost.php?p=83040029&postcount=273