Develop Bugs

[ROM/KERNEL] OFFICIAL CM11.0 + 3.0.72 Kernel for Kindle Fire [NIGHTLIES]

STEP 1: DOWNLOAD TWRP 2.7.x.x and UPDATE (REQUIRED FOR 4.4):
EDIT: @Dees_Troy has an official 2.7.x.x w/ SElinux support here:
http://techerrata.com/file/twrp2/blaze/openrecovery-twrp-2.7.0.1-otter.img
Flash with the following adb commands:
Code:
adb shell
su
idme bootmode 4002
reboot
# back in your PC shell
fastboot -i 0x1949 flash recovery openrecovery-twrp-2.7.0.1-otter.img
If you have problems with that file and/or don't want to use adb/fastboot flash method, you can download a flashable .zip from the following locations. Use your existing recovery to flash the update:
Mirror 1: Download (Goo.im)
BEFORE FLASHING ANDROID 4.4: PERFORM A WIPE + ADVANCED->FORMAT SYSTEM TWRP.
STEP 2: DOWNLOAD A BUILD OF CM11.0:
DO NOT USE ART YET. BUGGY AND WILL PROBABLY NEED A DATA WIPE TO RECOVER FROM
NIGHTLIES:
http://download.cyanogenmod.org/?device=otter
GAPPS (Use Version "CM 11" row):
http://wiki.cyanogenmod.org/w/Gapps
Older builds are found here:
http://goo.im/devs/Hashcode/otter/cm10/
http://goo.im/devs/Hashcode/otter/cm10.1/
http://goo.im/devs/Hashcode/otter/cm10.2/
GAPPS (For Android 4.3/CM10.2 builds):
http://goo.im/gapps/gapps-jb-20130813-signed.zip
CHANGES:
[05/15] More audio updates to fix low-power states (screen off / background music)
[11/25] Released updated build for cm11.0
[08/12] Kernel updated to 3.0.72 (on par w/ Google/common kernel)
[07/30] Updated to CM10.2 build
[05/26] Backlight driver update to help w/ SODs
[05/24] Sensor updates (includes light sensor now usable in Android OS
[05/24] Reverted 2 sound driver commits in the kernel to help w/ headset function -- testing needed.
[05/14] New audio driver (WIP)
[03/27] Reboot Recovery mode is now fixed
[01/17] Updated SGX/PowerVR driver to latest binaries from omapzoom (still showing [email protected])
[01/15] CM10.1 updates + reverted some USB changes in the kernel for sleep testing
[01/07] Battery life / sleep improvements
[01/06] Update to 3.0.50 kernel
[01/06] Update wifi firmware to R5.SP3.06
[12/16] Fixed Deep Sleep
[12/15] Added multi-profile fix
CURRENT KNOWN ISSUES:
The headphone MIC input is not functioning correctly yet. Work in progress.
KERNEL FEATURES:
[08/12] Mainline version updates to 3.0.72 updated to current with Google's kernel/common
[01/06] WLAN Firmware R5.SP3.06
[11/07] Updated to SGX/IMG DDK [email protected] for Android (via omapzoom)
[11/07] WLAN Firmware R5.SP3.03
[09/05] Updated to SGX/IMG DDK [email protected] for Android
Based on TI kernel 4AI.1.7 (3.0.31 mainline) which supports 512M memory mapping needed by the Kindle Fire
Uses ducati binary from TI based on rpmsg 1.20.5.11 (replaced Archos ducati binary from ICS 4.0.3)
Kernel audio: Added a switch device "h2w" which allows the OS to recognize headset plug events and adjust audio capture routes accordingly. Translation: OS can recognize we have a MIC input via headset now. (NOTE: that audio recording is still not working at this time. Tho it is very close).
MUCH better standby / sleep function. The device will go inactive for much longer periods of time (80-100 seconds) while still waking up appropriately for wifi events, power button triggers, etc. And this is still going to get even better when I re-implement DPLL cascading and the charger fixes coming later.
Many bugfixes pulled down from TI's omapzoom sources.
RESERVED FOR NOTES
XDA:DevDB Information
Official CyanogenMod 11.0 for Kindle Fire 1st Edition, ROM for the Amazon Kindle Fire
Contributors
Hashcode
ROM OS Version: 4.4.x KitKat
Version Information
Status: Stable
Created 2014-05-01
Last Updated 2014-05-21

UPDATED 2013-11-25 for CM11.0/CM10.2/CM10.1
DEVELOPER BUILDING:
Several patches are outstanding in CM's review so building this from source is currently not an option w/o some Cherry Picks:
Patch 1: http://review.cyanogenmod.org/#/c/53917/
Patch 2: http://review.cyanogenmod.org/#/c/54562/
And I'll be updating more of the cm11.0 gits tonight w/ changes to the build / extract files processes.
Won't get a decent build till that's all done.
KNOWN BUGS:
1. EHCI USB 2.0 isn't able to be add to the kernel w/o it crashing. Need to fix for higher speed USB transfers.
6. Headset recording via the MIC input jack doesn't work
DEVS
BUILDING THIS ROM:
First, read through Google's Android website about "how to setup a build environment":
http://source.android.com/source/initializing.html
Then you can setup the Kindle Fire by doing the following:
mkdir android
cd android
(Use main repo for CyanogenMod 10.2)
repo init -u https://github.com/CyanogenMod/android -b cm-10.2
repo sync
vendor/cm/get-prebuilts
. build/envsetup.sh && brunch otter

FINALLY!
I'll see if I can help with power button LEDs.
*out-of-topic note: 3rd post!

1. The backlight doesn't sync up well with the screen. Meaning that sometimes when you bootup you won't see anything but a black screen. Once the boot is done, you can hit the power button a few times and eventually the screen and backlight will sync up and you'll get a picture.
Click to expand...
Click to collapse
I can't even get a picture.

animefun135 said:
I can't even get a picture.
Click to expand...
Click to collapse
Power button four or five times, and it'll pop up.
Edit: not having the sync issue in HC, hash, do you have the log posted on your site regarding the back light issue? I know its kernel related but 3.2 is a lil more cumbersome, so it could just be OS lag. Are we using 4.0.3 or 4.0.4?
Sent from my MB860 using XDA

Power button four or five times, and it'll pop up.
Click to expand...
Click to collapse
I tried 30+ times.

Nice job Hashcode.
Sent from my PG86100 using Tapatalk

I don't have time at the moment to pull down the sources and poke around for myself, but it sounds like #4 is a script issue of some sort.
Either one of the scripts that needs to fire for shutdown is hanging up, or the output isn't returning properly so that the master script can continue and finish pulling it all down.
If I get a chance tonight, I'll grab the sources and poke around a bit.
I deal with hanging/incorrectly-terminating script **** at work all the time, so now I might even be able to contribute, yay!

Reserving this for a complete description of the backlight driver/issue and related sources for research.
Sent from my DROID4 using XDA

Hey Hash I wanted to let you know that the charger does work for me. I don't have to boot back into twrp. Don't know if its just me or what but it works.
Edit: Didn't see that you had put its not working well instead off not at all, I'll do some more testing to see if it will give me problems. So far plugged it in about 20 times and its registering the charge.
Sent from my Amazon Kindle Fire using XDA

Let me be the first to say "Does Netflix work with this?"
Just kidding, things are coming along it appears, wish I knew more about hacking kernels, last time I did anything with a kernel I ran "make xconfig"

i just get a lit up black screen 0.0??

symbiiote said:
i just get a lit up black screen 0.0??
Click to expand...
Click to collapse
This issue is popping up with random people (myself included) and Hashcode has been made aware of it on the other thread, http://forum.xda-developers.com/showthread.php?t=1591869&page=5
The user who posted about it as well as another person as far as I know posted logs from their Kindle Fire's that depict the issue at hand. On a side note, and I know i'll get flamed for this, lets cut the arguing and just keep this thread as Hashcode requested it be, a development thread. If someone bashes you just ignore it and move on, the less clutter here the better Hashcode will be able to scan through it and pick out problems we're having and fix them.
To throw my two cents in on the issue itself:
I've noticed that when attempting to apply the suggested fix and sync up the graphics driver and the backlight I sometimes see quick glimpses of what I think are items on the screen, i'm wondering if this suggests an intermittent issue caused by the initial flash of the rom (could this explain why some are able to use the rom and some aren't). If this isn't possible please excuse my ignorance, it just made sense to me based on the limited amount of knowledge I have on this situation.

isaiahhhhh said:
I've noticed that when attempting to apply the suggested fix and sync up the graphics driver and the backlight I sometimes see quick glimpses of what I think are items on the screen, i'm wondering if this suggests an intermittent issue caused by the initial flash of the rom (could this explain why some are able to use the rom and some aren't). If this isn't possible please excuse my ignorance, it just made sense to me based on the limited amount of knowledge I have on this situation.
Click to expand...
Click to collapse
Wait, are you talking about things like large grey rows of pixels appearing on the screen? Sometimes I see gradients of monochromatic tones in addition to this. They only appear as the backlight is shutting off.

isaiahhhhh said:
This issue is popping up with random people (myself included) and Hashcode has been made aware of it on the other thread, http://forum.xda-developers.com/showthread.php?t=1591869&page=5
The user who posted about it as well as another person as far as I know posted logs from their Kindle Fire's that depict the issue at hand. On a side note, and I know i'll get flamed for this, lets cut the arguing and just keep this thread as Hashcode requested it be, a development thread. If someone bashes you just ignore it and move on, the less clutter here the better Hashcode will be able to scan through it and pick out problems we're having and fix them.
To throw my two cents in on the issue itself:
I've noticed that when attempting to apply the suggested fix and sync up the graphics driver and the backlight I sometimes see quick glimpses of what I think are items on the screen, i'm wondering if this suggests an intermittent issue caused by the initial flash of the rom (could this explain why some are able to use the rom and some aren't). If this isn't possible please excuse my ignorance, it just made sense to me based on the limited amount of knowledge I have on this situation.
Click to expand...
Click to collapse
your right, sorry, as for the rom, i noticed when i flashed hashcode's rom then reloaded rom over it youtube worked in HD, and that got me thinking, you think we can get a Flashable ZIP of the kernel?

is this the kernel that everyone was waiting for? 3.0?

@shahabk818
YES!
But it's still in development, so not for daily use!

TuikS2 said:
@shahabk818
YES!
But it's still in development, so not for daily use!
Click to expand...
Click to collapse
so this will fix the hardware acceleration problem, right?

shahabk818 said:
so this will fix the hardware acceleration problem, right?
Click to expand...
Click to collapse
So you can't read the title, right? [WIP][KERNEL][DEV-ONLY] 3.0 Kernel Development for Kindle Fire [04-10]
DEV ONLY!

OK, so compiled an aosp last night from the CM9 tree... I'm still not having a back light issue? Can't adjust brightness, but no sync issues. Could it be the ROM?
Sent from my MB860 using XDA

[ROM][WIP][kexec] Ubuntu with Freedreno!

I've been working on getting Ubuntu running on my Sprint Galaxy S3 using the same method I used on my Epic 4G - kexec from recovery loading the root filesystem off a partition on an SD card.
What I've done so far:
* Found a kexec loader to boot into a custom kernel, which is required for booting off an SD card, among other things;
* Compiled a custom kernel with KGSL DRM support enabled for Freedreno;
* Built a minimal Ubuntu 13.10 armhf rootfs and compiled the Freedreno DRM/DDX/Mesa Gallium driver with changes to support the Adreno 225 and stub occlusion query (possibility of full dekstop OpenGL 2.1 support!);
* Got X11 working with USB keyboard, touchscreen, and fbdev. Still working on getting the Freedreno DDX to load.
I still get a kernel oops with the camera driver (http://pastebin.com/egZbxsED), but it apparently doesn't affect stability or cause reboots anymore.
Working so far:
* USB Host - only tested with a keyboard, but other input/storage/audio/video devices should also work.
* Framebuffer console - thanks castrwilliam!
* Touchscreen works with X.org fbdev driver and the following added to /usr/share/X11/xorg.conf.d/11-evdev-quirks.conf:
Code:
Section InputClass
Identifier "Touchscreen"
Driver "evdev"
MatchProduct "sec_touchscreen"
EndSection
* Power and volume buttons
Untested:
* Bluetooth - might need firmware
* Sensors - should work just fine
* Home, menu and back buttons should work but probably need mapping
Unlikely to work due to proprietary Android-only blobs:
* Camera
Kernel config changes:
# IMPORTANT: remove the line that says "depends on !MSM_KGSL_DRM" from drivers/gpu/msm/Kconfig:70
CONFIG_DEVTMPFS=y
CONFIG_DEVTMPFS_MOUNT=y
CONFIG_VT_CONSOLE=y
CONFIG_DRM=y
CONFIG_MSM_KGSL_DRM=y
I may eventually post a pre-built kernel, but if you don't know how to compile a kernel from source, this guide is not for you.
Likewise, if you don't know how to prepare an armhf Ubuntu root filesystem, this guide won't help much.
After building the kernel, copy arch/arm/boot/zImage to your SD card along with the attached zImage.zip (CWM-flashable kexec loader).
It might need modifications (META-INF/com/google/android/updater-script) depending on how you have your card set up.
UPDATE: Unfortunately, this phone hasn't been a good fit for me. I never got very far booting Ubuntu or Freedreno, so I decided to sell it.
For anyone still interested in this project, I believe castrwilliam has the required patches.
When I get my next Snapdragon device (either the new Nexus 7, a Nexus 4, a Galaxy S4, or another phone with Adreno 320 graphics), I will post the Mesa patches for occlusion query support. Sorry I wasn't more helpful with this device.

Added to favourites, I'll see what I can do with it over the weekend
Sent from my SPH-L710 using Tapatalk 4 Beta

Great work. Good luck debugging.
Sent from my SPH-L710 using xda app-developers app

Maybe taking a look at how Motorola worked Ubuntu, in a way, with Webtop that came on the Photon. The Photon has the integrated Ubuntu-based 'Webtop' application from Motorola. The Webtop application is launched when the phone is connnected to the external display through Laptop dock or HD multimedia dock. In Webtop mode, offering similar user interface of typical Ubuntu desktop, the phone can run several applications on external display such as Firefox web browser, SNS clients and 'mobile view' application enabling total access of the Photon and its screen. In September 2011, Motorola released the source code of Webtop application at SourceForge.
I know it's not an app you're trying to use but it may help in finding how to work some of the kinks you have. I hope that helps

Hi, I'm the person maintaining Ubuntu currently for HP Touchpad (http://forum.xda-developers.com/showthread.php?t=2225462) (which also uses an MSM SOC.) It's starting to show its age... I'm trying to get this to where you have it currently on a Verizon S3 / d2vzw (obviously, kexec'ing into a Verizon kernel instead.) Maybe we could collaborate?
Currently I have the KT747 kernel (kexec host support as well as guest) (compiled as a zImage. If you can provide me with access to the patches you have for freedreno and hopefully also an initramfs image (I'm going to mod the HPTP rootfs, so no need there)... I'd love it.

My only modifications to the kernel so far are the ones I mentioned in the OP and three of Rob Clark's Freedreno commits from the mako-kernel branch of kernel-msm on his GitHub - namely, "kgsl: drm: remove checking on 'active'", "video/msm: add true ARGB", and "kgsl: fix null ptr on cache flush".
At one point I had X11 working with freedreno displaying the GNOME background, but the screen blanked after 10 seconds and I couldn't recover from that. Unfortunately, after experimenting with different kernel config options, I lost that semi-working configuration and the GPU started to page fault, sometimes displaying a corrupted screen and sometimes rebooting before displaying anything.
Believe me, I've been working on this for weeks, and it's very frustrating that it doesn't even sort of work. My minimal modifications to Mesa to get it to recognize the Adreno 225 are highly unlikely to be the cause of the problems, and I highly doubt the differences between the 220 and 225 are to blame since it was working at one point. It's a one liner, figured out from from freedreno/mesa issue #2.
Castrwilliam, the initramfs is the least of your worries. I don't use one, since its only function is to display the Plymouth splash, which doesn't work anyway.

gTan64 said:
...
Castrwilliam, the initramfs is the least of your worries. I don't use one, since its only function is to display the Plymouth splash, which doesn't work anyway.
Click to expand...
Click to collapse
Yeah, I realized how you were doing this after looking at the kexec script. I was trying to boot from Android, not recovery, and was under the impression you had put a disk image on external SD, and then made the initramfs loop-mount that and boot from it... but now I see you partitioned it.
It's a shame you don't have your original config, I'll try to get it booting again on my end. I remember doing something like this a while back, where I made like 10 differently configured kernels at once, and tested them each in turn. I imagine the ramconsole would help a good bit so that I could look a how far we're getting. (The touchpad has its own version of that, which you can read directly from the bootloader (bootie.) Then again, it also has LVM volumes for storage instead of actual partitions (except for boot) - which makes it uber easy to boot lots of OSes.)
Currently I'm not doing too well. I remember that kexec did work at one point on d2vzw hardware but I'm assuming that it still does now (new bootloaders, 3.4 kernels, ...) I do kexec -e, the reboot happens, I see the Samsung bootloader screen, then the screen blanks for like 5 seconds and it reboots again - back into android.

castrwilliam said:
I imagine the ramconsole would help a good bit so that I could look a how far we're getting...
the screen blanks for like 5 seconds and it reboots again - back into android.
Click to expand...
Click to collapse
The RAM console should be enabled by default, so check /proc/last_kmsg once Android boots back up.
It could be something simple like the root filesystem not mounting, either due to how you partitioned the card or not having time to settle, hence rootwait. Or it could be something else. I haven't gotten any useful output in /proc/last_kmsg with the framebuffer console enabled, so make sure that's disabled unless you want a headache and a psychiatrist visit.
Unfortunately, I've spent way too much energy trying to debug the GPU page fault, and I probably won't have much time to work on it after next month. I want this bug dead and forgotten, so more eyes would be great!

X11 works (shows something on screen) with the X.org "fbdev" driver. I can't reproduce anything with "freedreno" (or "modesetting", which I accidentally loaded at one point...)
The touch screen doesn't respond, but the power key works and brings up a shutdown dialog.
Screenshot attached. I used the 13.04 Touchpad rootfs with some modifications...

Okay, you can get the fbcon working by either loading it as a module during boot OR changing its "module_init" macro in drivers/video/console/fbcon.c to "late_initcall".
Picture attached. Sorry for blurriness, I don't have an actual digital camera, only what's on my sig. This should make debugging a bit easier.

Nice to see some more freedreno development on android phones
I'm using freedreno with a slightly different approach, starting it directly from android on a chrooted shell, which is a lot more easier to debug.
The kernel needs some fixes from the mako branch and the following configs:
Code:
CONFIG_DEVTMPFS=y
CONFIG_VT=y
CONFIG_DRM=y
CONFIG_MSM_KGSL_2D=y
CONFIG_MSM_KGSL_DRM=y
Rob Clark (the maintainer of freedreno) has been working on his own kernel driver for adreno gpu:
https://github.com/freedreno/kernel-msm/commits/ifc6410-drm
This would be a nice addition/replacement for the current qualcomm gpu driver.

Wootever said:
Nice to see some more freedreno development on android phones
I'm using freedreno with a slightly different approach, starting it directly from android on a chrooted shell, which is a lot more easier to debug.
The kernel needs some fixes from the mako branch and the following configs:
Code:
CONFIG_DEVTMPFS=y
CONFIG_VT=y
CONFIG_DRM=y
CONFIG_MSM_KGSL_2D=y
CONFIG_MSM_KGSL_DRM=y
Rob Clark (the maintainer of freedreno) has been working on his own kernel driver for adreno gpu:
https://github.com/freedreno/kernel-msm/commits/ifc6410-drm
This would be a nice addition/replacement for the current qualcomm gpu driver.
Click to expand...
Click to collapse
How do you stop the SurfaceFlinger (I think that's proper terminology) from hogging the framebuffer?

Semi Working Freedreno/X11
castrwilliam said:
How do you stop the SurfaceFlinger (I think that's proper terminology) from hogging the framebuffer?
Click to expand...
Click to collapse
HEY, look what I did?!
(There are a lot of patches req'd to get this far. Even at this point, there's a weird bug where the cursor loops across the edge of the screen and windows overlap themselves. If you want to know, I'll elaborate in a further post, otherwise, let's get that touchscreen working for release!)
Thanks to Rob Clark (again, the author of freedreno) who helped me get this far on his IRC channel at Freenode.

castrwilliam said:
HEY, look what I did?!
(There are a lot of patches req'd to get this far. Even at this point, there's a weird bug where the cursor loops across the edge of the screen and windows overlap themselves. If you want to know, I'll elaborate in a further post, otherwise, let's get that touchscreen working for release!)
Thanks to Rob Clark (again, the author of freedreno) who helped me get this far on his IRC channel at Freenode.
Click to expand...
Click to collapse
Are we keeping track of all the necessary patches? I'm on https://github.com/CyanogenMod/android_kernel_samsung_d2, branch cm-10.2_kgsl, with the per-process pagetable hack, the "active" kgsl_drm fix, Adreno 225 case in Mesa (freedreno_screen.c), and my stub occlusion query hack. I wasn't on #freedreno when Rob Clark pointed out the libdrm bug I heard about from the Wiki - did you fix that? I'm still getting the assert crashes.
I'll be on #freedreno at some point tomorrow.

gTan64 said:
Are we keeping track of all the necessary patches? I'm on https://github.com/CyanogenMod/android_kernel_samsung_d2, branch cm-10.2_kgsl, with the per-process pagetable hack, the "active" kgsl_drm fix, Adreno 225 case in Mesa (freedreno_screen.c), and my stub occlusion query hack. I wasn't on #freedreno when Rob Clark pointed out the libdrm bug I heard about from the Wiki - did you fix that? I'm still getting the assert crashes.
I'll be on #freedreno at some point tomorrow.
Click to expand...
Click to collapse
I got this to work by using a fairly old libdrm, but a new DDX (xf86-video-freedreno). I haven't fixed the assert bug on the newer ones.
You need to patch the DDX's msm-device.c to set the width to 736 (has to be a multiple of 32), and then disable/comment out/delete where it calls the mode-set function (there's a comment about making xrandr happy in the right place.) I can make a patch soon, but I have a feeling that this is what made the other bug happen with the looping cursor.
edit -- I fixed the looping cursor. A patch is attached...
Youtube video of it working: http://www.youtube.com/watch?v=rh9wmmYuKxY
Tips:
Set the firnware path for the dhd (wi-fi) driver to /system/etc/wifi/bcmdhd_sta.bin (WITHOUT the _b2 buffix, it will be added by the module). Set the nvram file to /system/etc/wifi/nvram_net.txt. Then, add the Android partitions to the /etc/fstab (mmcblk0p14 is system.)
apt-get install xserver-xorg-input-multitouch and then add a config file under /usr/share/X11/xorg.conf.d/ to get the touchscreen working. It will act like a laptop trackpad. You MUST use the multitouch driver. "evdev" will segfault the server on any touch. Note that you can match the TS in an InputClass with its udev name, "sec_touchscreen".
The date that I compiled the working Freedreno libdrm was the date that Ubuntu 13.04 was released. I'm working on narrowing it down to a Git SHA1 revision. I used Rob Clark's repository, not the freedesktop one.
Use the master branch of the DDX, sorry for the earlier confusion.
For battery savings, you might want to cherry pick the DPMS commit from the a3xx branch of the DDX.

castrwilliam said:
How do you stop the SurfaceFlinger (I think that's proper terminology) from hogging the framebuffer?
Click to expand...
Click to collapse
There are two binaries you can execute with adb shell stop/start that kills and restart the android proccesses, allowing access to the framebuffer.

Okay, so 2-D does work with my mods, but I just tried 3-D last night (ran es2gears with the Adreno 225 mod in place on mesa) and the pagefaults returned.
I did notice something about your pagefault reboots, though: they shouldn't necessarily be happening, it's a NULL pointer dereference that can be fixed in the handler by doing this in drivers/gpu/msm/kgsl_iommu.c (function is kgsl_iommu_fault_handler):
Change
Code:
curr_context->pagefault = 1;
curr_context->pagefault_ts = curr_global_ts;
To:
Code:
if (curr_context) {
curr_context->pagefault = 1;
curr_context->pagefault_ts = curr_global_ts;
}

So anyone got any updates for this if not i will start building upon what is there if it is ok
Sent from my SCH-S960L using xda premium

allenjthomsen said:
So anyone got any updates for this if not i will start building upon what is there if it is ok
Sent from my SCH-S960L using xda premium
Click to expand...
Click to collapse
I guess it is OK. Hopefully you can make a dent in this development. Keeping my eye on this thread.

No longer developing for this phone
Unfortunately, this phone hasn't been a good fit for me. I never got very far booting Ubuntu or Freedreno, so I decided to sell it.
For anyone still interested in this project, I believe castrwilliam has the required patches.
When I get my next Snapdragon device (either the new Nexus 7, a Nexus 4, a Galaxy S4, or another phone with Adreno 320 graphics), I will post the Mesa patches for occlusion query support.

fhd kernel ( ZE551 ) & POSSIBLY hd (ZE550) with KVM & Bridge compiled. *need help*

fhd kernel ( ZE551 ) & POSSIBLY hd (ZE550) with KVM & Bridge compiled. *need help*
MODERATOR NOTICE:
All thread posted in the Development section must have a link to kernel sources to meet GPLv2 requirements. Because this thread does not have proper sources linked and because development has stopped, the thread has been closed.
This is my first time working with Android kernels, but I compiled the 2.12.40 kernel source adding in support for KVM ( Kernel supported Virtual Machines, ie running Windows almost full speed ) and Bridge ( to allow qemu-kvm to set up network adapters bridged with the current wifi adapter ).
I tar'd the bzImage & modules, but don't know what to do to make something installable/flashable so will need help on that end of things.
Edit:
I uploaded a new flashable kernel img based off 2.19. This one should support: kvm, bridge and NTFS read/ *LIMITED* write, swap and ignore kernel module signatures. XDA only allows 8mb for .img files, so I tar'd it.
Edit2:
I compiled a ZE550 kernel ( called hd ) and if some brave souls want to try it, I also put together a boot.img.
Edit3:
New fhd kernel has been compiled with additional usb modules. Kernel should now load kvm related modules automatically, so you shouldn't need to use the script anymore.
Anyone brave/crazy enough to try it out? I'm guessing you need an unlocked bootloader & root.
Edit 4:
New fhd & hd kernels for 2.20
Edit 5:
New exfat.ko module

ycavan said:
This is my first time working with Android kernels, but I compiled the 2.12.40 kernel source adding in support for KVM ( Kernel supported Virtual Machines, ie running Windows almost full speed ) and Bridge ( to allow qemu-kvm to set up network adapters bridged with the current wifi adapter ).
I tar'd the bzImage & modules, but don't know what to do to make something installable/flashable so will need help on that end of things.
Anyone brave/crazy enough to try it out? I'm guessing you need an unlocked bootloader & root.
Click to expand...
Click to collapse
Why 2.12? 2.18 kernel source is available...

That just happened to be the kernel source linked in Android development. If this test works out, I can probably do the same thing with whichever kernel source is available.
Our phones are pretty amazing to be able to compile their own kernels natively on the device.
Sent from my ASUS_Z00AD using XDA Free mobile app

Finally able to compile the 2.18 kernel.. it's a bit weird since it acted like it was missing some files. Untar'd the 2.18 kernel source over 2.12's kernel source and that allowed it compile.
Anyway, it's in the OP called fhd_kernel_20150629.tar and should have KVM ( kernel supported virtualization ), Bridge ( for Qemu-KVM to create bridging ethernet adapters ) & NTFS Read/ *LIMITED* Write.
Once again, it's in the form of bzImage and the modules since I don't know how to replace the kernel on Android devices. ( normally, I'd just make a test linux line in the boot menu for Linux )

One suggestion would be to flash the zImage using
Code:
fastboot flash zImage nameofzImage
or test it using
Code:
fastboot boot nameofzImage
but I dont know if the phone supports the "boot" command.
I´m not sure about the modules either and I can´t test it, as my phone didn´t arrive yet.
Other solution, try this:
http://forum.xda-developers.com/showthread.php?t=2670512

ycavan said:
Finally able to compile the 2.18 kernel.. it's a bit weird since it acted like it was missing some files. Untar'd the 2.18 kernel source over 2.12's kernel source and that allowed it compile.
Anyway, it's in the OP called fhd_kernel_20150629.tar and should have KVM ( kernel supported virtualization ), Bridge ( for Qemu-KVM to create bridging ethernet adapters ) & NTFS Read/Write.
Once again, it's in the form of bzImage and the modules since I don't know how to replace the kernel on Android devices. ( normally, I'd just make a test linux line in the boot menu for Linux )
Click to expand...
Click to collapse
Can I ask how you included NTFS r/w support into your kernel? Did you just set the CONFIG_NTFS_FS flag?

TheSSJ said:
Can I ask how you included NTFS r/w support into your kernel? Did you just set the CONFIG_NTFS_FS flag?
Click to expand...
Click to collapse
I added CONFIG_NTFS_FS=m ( you could set to that y ) and CONFIG_NTFS_RW=y in /{working directory}/device/asus/moorefield/fhd/mofd_fhd_diffconfig
when you make the kernel, it's going to ***** about the config files not matching; follow the directions and manually update all of the other config files and it will finally compile.
Building for Android is a pita. )

Well, then here come the disappointing news (I discovered that when I wanted to include NTFS USB-OTG support directly by the kernel for my TWRP and it didn't mount it as R/W):
CONFIG_NTFS_RW is just a partial write support. It won't create files or folders, it can only overwrite existing files and only by the size they currently have
config NTFS_RW
bool "NTFS write support"
This enables the partial, but safe, write support in the NTFS driver. The only supported operation is overwriting existing files, without changing the file length. No file or directory creation, deletion or renaming is possible. Note only non-resident files can be written to so you may find that some very small files (<500 bytes or so) cannot be written to.
Click to expand...
Click to collapse
Only possibility available is to include ntfs-3g driver using fuse

Yeah, that is a bit of a downer. Now to figure out why nobody finished the NTFS kernel module.

ycavan said:
Yeah, that is a bit of a downer. Now to figure out why nobody finished the NTFS kernel module.
Click to expand...
Click to collapse
Please keep me posted, I'd like to remove the dependency of ntfs-3g in recovery. I fear there actually is no native support of NTFS (googling was not helpful unfortunately)

1) modify module loading function to ignore module version/magic strings.
2) compile the kernel with toolchain used by ASUS (or close to it)
3) use pre-compiled tntfs.ko from original boot.img
I don't have right now the patch for module loading procedure. Need to check old Galaxy S3/S4 custom kernels source (but it's should be easy to patch by finding error string). In time when exFat module source wasn't available, this trick was very common in samsung custom kernels for exFat support.

Thanks

Wait wait wait. Did I read that correctly? Full speed windows? On the zenfone? I think I just died. Does this mean windows 8/10 or windows xp and below?

I know a bit about android kernel, and i'm thinking about buying this device. Well, i'm going to try to build a kernel for this device as soon as i got this device. One thing you should know is, android is an open-source, so before you uploading your compiled kernel, make sure you have already uploaded the sources

LUCKYSHOT52 said:
Wait wait wait. Did I read that correctly? Full speed windows? On the zenfone? I think I just died. Does this mean windows 8/10 or windows xp and below?
Click to expand...
Click to collapse
It's only in theory.
In reality, there is no Z35xx support in windows, and i doubt anyone will write drivers by himself (windows isn't opensource). Officially Z35xx is Android-only SoC.

FajarMF28 said:
I know a bit about android kernel, and i'm thinking about buying this device. Well, i'm going to try to build a kernel for this device as soon as i got this device. One thing you should know is, android is an open-source, so before you uploading your compiled kernel, make sure you have already uploaded the sources
Click to expand...
Click to collapse
The source is already available, so no worries there, since this is source that Asus released.

For all of the brave folks out there, I was finally able to create a bootable image of the latest 2.19.20 kernel. Anyone brave enough can find it in the OP.
I flashed it and my phone booted up, so that's a bonus.

ycavan said:
For all of the brave folks out there, I was finally able to create a bootable image of the latest 2.19.20 kernel. Anyone brave enough can find it in the OP.
I flashed it and my phone booted up, so that's a bonus.
Click to expand...
Click to collapse
is there extra features such as other governor or i/o scheduler?

cangcan said:
is there extra features such as other governor or i/o scheduler?
Click to expand...
Click to collapse
To be honest? I can't remember since my main focus was getting kvm compiled in.
I've attached my .config for the 20150707 build ( in the boot image ).
I've also attached a screenshot of Windoze 7 being installed.
Commandline for Arch Linux x86_64 to start qemu-kvm to install windoze:
qemu-system-x86_64 -display none -vnc :1,password -monitor stdio -m 1G -smp 4 -enable-kvm -drive file=/mnt/0/machine1.img,format=raw -cpu host -cdrom /mnt/MicroSD/Vcd/en_windows_7.iso -boot menu=on --usbdevice tablet
breakdown of the command line:
-display none = no display, I did this to test the virtual machine. normally, you would probably use -display sdl w/ XServer-XSDL running
-vnc :1,password, This says to set up a vnc server with normal port + 1 ( 5901 ) and you expect a password to be set later
-m 1G, 1 gig of ram
-smp 4, our VM will use 4 cores
-enable-kvm, enable Kernel support Virtual Machines
-drive file=/mnt/0/machine1.img,format=raw, my "disk" file
-cpu host, use the same cpu information
-cdrom /mnt/MicroSD/Vcd/en_windows_7.iso, my Windows 7 install cd turned into an iso
-boot menu=on, enable the boot menu ( hit F12, etc.. )
--usbdevice tablet, Qemu's Vnc server sucks at tracking mouse positions so using tablet mode keeps the mouse pointer .. well on-point

Tks for share
Kernel great work
But how to install window 7 ? ?
Gửi từ ASUS_Z00AD của tôi bằng cách sử dụng Tapatalk

OmniROM Android R (11) for Pi 4

OmniROM
Download
Images taged with MICROG contain a pre-installed ready to use
microG setup https://microg.org/
Images tagged with WEEKLY can be used to setup
official Google gapps
64bit build
Tablet mode configuration (not Android TV)
At least 4GB model recommened
No HW accelerated video playback
Mesa support for V3D is WIP so expect some graphic issues (especially on higher resolutions - HD 1920x1080 in general should be fine)
Support of booting from SD or USB by just changing config.txt (check README below)
GPIO support - monitor and set README.gpio
chrome (ium) is broken use alternative browser (firefox, edge)
for screen issues check https://www.raspberrypi.org/documentation/configuration/cmdline-txt.md
if you experience black bars connect to HDM1 or add disable_fw_kms_setup=1 to config.txt files
how to do updates? - check README.update
Adjust screen resolution:
To force a different screen resolution edit in /system/build.prop the line
#debug.drm.mode.force=1280x800
Remove the leading # comment and adjust to the screen resolution you want e.g.
debug.drm.mode.force=1280x720
Make sure to also check the README.txt in there
For questions please also use our official Telegram channel
https://t.me/OmniROM_Community
For current progress and how to build yourself check
README.build
XDA:DevDB Information
OmniROM, ROM for the Raspberry Pi 4
Contributors
maxwen, maxwen
Source Code: https://github.com/omnirom/android_kernel_brcm_arpi/
ROM OS Version: Android 11
ROM Firmware Required: 64bit
Based On: AOSP
Version Information
Status: Stable
Created 2020-10-28
Last Updated 2020-10-28

Builds
https://dl.omnirom.org/tmp/rpi4/
The plan is to have about weekly builds - at some point it will be part of all the other OmniROM devices with regular weekly builds
once the Android 11 cycle starts
20201016
Just a snapshot of the current state
Non microG builds will come later
20201028
WEEKLY and MICROG build
20201105
TWRP included
IMPORTANT
Check new recovery section in README for all the details
EVEN MORE IMPORTANT as posted before to get a working TWRP I had to disable userdata encryption for the moment
that means IF you try to boot this with your old userdata you will get an unpleasent surprise. You must start with
a fresh userdata partition (mkfs + tune2fs). You CAN (if you know what you do) create an backup BEFORE
updating by using adb shell and e.g. create a copy of userdata on an external USB device and copy that back afterwards.
But after all of that hassle from now on updating will be much easier since with TWRP you can create
userdata backups on an external USB device very easy
So going from this release an update could work like this.
1) boot your current install into TWRP
2) create an userdata backup on an external USB device
3) flash the new build - you dont need to care about userdata
just do whatever you always do with it e.g. resize
4) boot new build
5) go into Advanced settings and switch boot mode to recovery and restart
6) in TWRP restore the backup you created before from external USB device
7) flash switch_boot_rom.zip and reboot system
8) enjoy
add boot mode switch in Advanced settings
add audio output switch in Advanced settings
whatever has been done since the last build
20201115
fixed 5GHz WiFi AP
fixed Fondar USB touch screen
actual development
20201122
switch to new kernel base - big thanks to Konsta - with update to 5.4.77
update mesa to v20.2
initial work to support pi camera - not yet working but close
initial work to support gpio - IF you want to use gpio please contact me on tg cause I was too lazy to create a README for this yet
all core system updates and fixes
20201128
performance tuning
November security update
gpio support update
all core system updates and fixes
20201206
added gpioi-fan
cpufreq config in advancded settings
all core system updates and fixes
20201214
property persist.debug.drm.mode.force to adjust screen resolution
all core system updates and fixes
20201224
added disable_fw_kms_setup=1 to config.txt files. This should remove unneeded black bars for some screen when connected on HDM1. I did not see any problems on screens that have no issue with that anyway so I enabled by default. If you face issues remove line and report back please
enabled showing BT device battery level if applicable
all core system updates and fixes
Best Xmas wishes for those who care about it and looking forward to 2021
20201231
add WiFi firmware for p400
kernel update 5.4.85
add userdata resize and project quota enable script in TWRP
reduce dB of max media volume
all core system updates and fixes

Does this build support the original RPI 7" touch screen?

elhennig said:
Does this build support the original RPI 7" touch screen?
Click to expand...
Click to collapse
Not out of the box since I dont have one of those to test myself
BUT it should contain the needed overlays so if you know your way around
give it a try and report back if there is something missing.

Regarding "No HW accelerated video playback", is there a chance this is coming anytime soon?
Thinking about using this for MS xCloud gaming.

maxwen said:
Not out of the box since I dont have one of those to test myself
BUT it should contain the needed overlays so if you know your way around
give it a try and report back if there is something missing.
Click to expand...
Click to collapse
I am afraid I have no idea how to build my own ROM or configure overlays respectively. I guess you just notice from my answer that this is the sad truth

ich_mind said:
Regarding "No HW accelerated video playback", is there a chance this is coming anytime soon?
Thinking about using this for MS xCloud gaming.
Click to expand...
Click to collapse
Depends mostly on mesa development - but nothing I would hold my breath for

elhennig said:
I am afraid I have no idea how to build my own ROM or configure overlays respectively. I guess you just notice from my answer that this is the sad truth
Click to expand...
Click to collapse
well - the thing is that this does not have anything to do with building ROMs
should all be possible by modifying config.txt
Looking at the LOST OS builds might give some hints since I think he supports it

Just one word of wisdom here from me since I saw in some reports as something negative
"It’s stuck in “tablet mode” instead of Android TV mode"
I really dont think a raspi is a well equipped device to be used for ATV when you get
a ATV USB stick from e.g. Xiaomi for about 40E that simply works without issues and
has official google support.
So while everyone feel free to use our repostories to create an ATV build dont ask me for it cause I wont do it.

please help after propper flash to my sd card all i get is the no input screen as if nothing is connected to my tvs hdmi port

Thanks a lot for the work you put into this.
I'm really looking forward to how this project will develop.
If I may I have a stupid question - is there a way foreseen to safely shutdown the pi? I mean I know how to setup a safe shutdown in e.g. raspbian but I doubt it's the same in android.

Growking99 said:
please help after propper flash to my sd card all i get is the no input screen as if nothing is connected to my tvs hdmi port
Click to expand...
Click to collapse
I think you hit me already in TG - but just to reiterate here again - as it is in also the README
Using latest firmware is MANDATORY - 64bit support has been added a few months ago
without you will get the described no boot
Best is to flash latest firmware (which also includes USB boot even if you dont need it)
There are a long list of pages describing how to update. Just linking one here for reference
https://www.tomshardware.com/how-to/boot-raspberry-pi-4-usb
You MUST do that in e.g. Raspberry OS so best do it before even starting with Android

lernfaehig said:
Thanks a lot for the work you put into this.
I'm really looking forward to how this project will develop.
If I may I have a stupid question - is there a way foreseen to safely shutdown the pi? I mean I know how to setup a safe shutdown in e.g. raspbian but I doubt it's the same in android.
Click to expand...
Click to collapse
Long press the power button in the navigation bar -> shut down

That's pretty cool, thanks for hard work.
But it's still not usable for daily use as a media center since there is no HW accelerated video playback.
All Android builds on raspberry pi have the same issue .. :/
I think that these builds are just proof that you can have Android on raspberry pi than anything else.

flyl0 said:
That's pretty cool, thanks for hard work.
But it's still not usable for daily use as a media center since there is no HW accelerated video playback.
All Android builds on raspberry pi have the same issue .. :/
I think that these builds are just proof that you can have Android on raspberry pi than anything else.
Click to expand...
Click to collapse
Welcome captain obvious - tell us something new...

maxwen said:
Welcome captain obvious - tell us something new...
Click to expand...
Click to collapse
It's just an observation lol what I don't understand is that there are almost no differences between Android 9, 10 or 11 for pi, they are all the same.
I wonder what's the real point to make all these builds which all lack the same features.. No disrespect, I'm just wondering.
Captain obvious

flyl0 said:
It's just an observation lol what I don't understand is that there are almost no differences between Android 9, 10 or 11 for pi, they are all the same.
I wonder what's the real point to make all these builds which all lack the same features.. No disrespect, I'm just wondering.
Captain obvious
Click to expand...
Click to collapse
You are just too focused on what you want to do with the device

does it have google apps out of the box

vedforeal said:
does it have google apps out of the box
Click to expand...
Click to collapse
of course not - this would be illegal
We are not in China here ...
PS: I did not find any android-11 gapps out there that would work currently
So the only way is anyway microG for now - which is enough for most people

i tried to boot off 32gb usb and it wont work
and first thing before you say anything about my bootloader being out of date its not here is the bootloader output BCM2711 detected
Dedicated VL805 EEPROM detected
BOOTFS /boot
BOOTLOADER: up-to-date
CURRENT: chu 03 set 2020 12:11:43 UTC (1599135103)
LATEST: chu 16 abr 2020 17:11:26 UTC (1587057086)
FW DIR: /lib/firmware/raspberrypi/bootloader/critical
VL805: up-to-date
CURRENT: 000138a1
LATEST: 000137ad
when i try to boot the build (from the website i didnt compile it) with either the microg or the weekly build after flashing the pi just simply wont start and the green and red light just keeps flashing and nothing happens i was able boot twisterOS just fine off this same usb so its this build i dont know if i did something wrong but the file system was present in gparted and i tried booting it without expanding the partition and with doing so. also i tried to "fix" all the partitions using gparted and that did nothing also i noticed that the /boot directory in this build seems a bit empty compared to my manjaro build i know your working hard on this but this might be a bug in your build and id be willing to help you fix it

Shieldroot Tools Have Leveled Up!

Hi friends~!
Shieldroot has Leveled Up and No longer Requires an External Hard Drive!
Please remember to change the IP address in ADBCONNECT
DOWNLOAD: https://mega.nz/file/QQpUUSba#Q17teRIq2IUJNk-qTe-3qfgYwXlz4VcX9KtPjHERSWI 1.6 GB ZIPPED
GOOGLE DRIVE: https://drive.google.com/file/d/1FusTaAJ5oCNXbYQ_58xgXPMYfRg0Qy0m/view?usp=sharing
I have cleaned up the clutter in our previous edition of Shieldroot, as well as updated the adb tools for us. I have also included new code for easily wiping all your partitions, to ensure you have the smoothest Sailing.
I will post the link when its finished updating, i just needed a placeholder for all this crap~!
VIDEO GUIDE:
This is a never ending WIP (work in process) so Enjoy The Ride XD
FOR THOSE THAT NEED IT:
~! whyyyy IT's MaGiC
My stumblez along the Way
You Must be Familiar with this Method Please Before Using the new Tools
Root Nvidia Shield TV Pro 2019 Version
THIS IS OUTDATED https://forum.xda-developers.com/t/bootmod-root-your-shield-in-1-minute-2015-2017-2019.4524873/ REPLACES THIS IF YOU WANT ANDROID OR USE THIS GUIDE...
forum.xda-developers.com
I want to thank my New friend, Dawn!!! They showed me the way~!
nooted1
forum.xda-developers.com
With majisk Modules, by sharing some awesome github repos. I will link those soon
This one IDK What it is But I will find out~!
magisk_files/app-release.apk at alpha · vvb2060/magisk_files
Contribute to vvb2060/magisk_files development by creating an account on GitHub.
github.com
Adguard
https://download.adguard.com/d/18673/adguard.apk
A Magisk Repository For Enabling User Added Certs
GitHub - Magisk-Modules-Repo/movecert: movecert
movecert. Contribute to Magisk-Modules-Repo/movecert development by creating an account on GitHub.
github.com
GET TO KNOW ME IF YOU DARE~!
Hello New Friends!
My name is Jen. Long time lurker, recent poster here the last few months. I recently had a stay at the hospital due to a fever I had for four days, In those four days I had entered a stage of psychosis, Long story short, I Recovered, shed...
forum.xda-developers.com

Friends~! I don't have the Time to port these over to the 2015, 2017 versions. I ask someone who follows those forums please take the shieldroot tools and make them your own, it's all open source <3

And that's a wrap, we all updated here B0IS part 2 figuring out what the effs to do with the modules... coming sooon tee hee~!

jenneh said:
This one IDK What it is But I will find out~!
magisk_files/app-release.apk at alpha · vvb2060/magisk_files
Contribute to vvb2060/magisk_files development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
This is a modified Magisk branch which re-adds MagiskHide functionality

nooted1 said:
This is a modified Magisk branch which re-adds MagiskHide functionality
Click to expand...
Click to collapse
Le HAWT ~!! I am taking a break from the shield today, to play with and fix NOX, but I'll look at this again tom after work~! Thank you, Dawn!

I was successful with what I wanted to do today in Nox: https://forum.xda-developers.com/t/fully-cracked-nox-android-emulator.4381833/
Future endeavors will involve learning the poison they put in virtualbox, to ammend that, then cannibalize the executable, as well as attempting to inject a bootloader somehow~! Practice for our Shield, Tee-hee~!

jenneh said:
I was successful with what I wanted to do today in Nox: https://forum.xda-developers.com/t/fully-cracked-nox-android-emulator.4381833/
Future endeavors will involve learning the poison they put in virtualbox, to ammend that, then cannibalize the executable, as well as attempting to inject a bootloader somehow~! Practice for our Shield, Tee-hee~!
Click to expand...
Click to collapse
hey, can you please make a howto explaining how to go back to nvidias shield tv pro own build? right now I’m on your build but I want to install latest nvidia shield tv pro android update

KinkyGolab said:
hey, can you please make a howto explaining how to go back to nvidias shield tv pro own build? right now I’m on your build but I want to install latest nvidia shield tv pro android update
Click to expand...
Click to collapse
Yes I promise to do so with the release of my roms. I'm trying as hard as I can to fix my driver issue I just got the certificate signing software's programmed and built the driver I just need to sign it today and if it doesn't work I will revert back to Windows 10 so that I can make that rom for you guys

@KinkyGolab here's a recovery kit, just run erase all partitions, then recovery, and you're set~! if you want the boot locker code turned off, reboot into fastboot after running recovery then run the lock bootloader command
RECOVERY.zip
drive.google.com