[ROM/KERNEL] OFFICIAL CM10.1 + 3.0.50 Kernel for Kindle Fire 2 [CM NIGHTLIES] - Kindle Fire 2 Android Development

*** USE AT YOUR OWN RISK! WHILE I TRY MY BEST TO PROVIDE WORKING KERNELS/ROMS, I AM NOT RESPONSIBLE IF THIS SOFTWARE OR ANYTHING I'VE WORKED ON SUDDENLY FRIES YOUR DEVICE. ***
THIS ROM REQUIRES A 2ND-BOOTLOADER / RECOVERY BE INSTALLED ON YOUR KINDLE FIRE 2. FOLLOW INSTRUCTIONS HERE:
http://forum.xda-developers.com/showthread.php?t=2100963
*** READ CAREFULLY BEFORE DOING ANYTHING ***
*** Kindle Fire 1st-gen ROMs/KERNELS are *NOT* compatible with the Kindle Fire 2.
ONLY FLASH ROMs/KERNELS that are made for the Kindle Fire 2. ***
Month "stable" Snapshot CM builds:
Monthly "Stable" Builds
Nightly CM Builds:
Nightly Builds
Latest GAPPS:
http://goo.im/gapps/gapps-jb-20130301-signed.zip
Older builds are found here:
http://goo.im/devs/Hashcode/otter2/
CHANGES:
[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.
Virtual keyboard input on Jellybean is terrible. Needs a protocol update or something. Fixing. For now use an alternate keyboard like Swype
KERNEL FEATURES:
[01/06] Mainline version updates to 3.0.50 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 18 hours ago)
[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
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.1)
repo init -u https://github.com/CyanogenMod/android -b cm-10.1
repo sync
vendor/cm/get-prebuilts
. build/envsetup.sh && brunch otter2
RESERVED FOR NOTES

RESERVED

So does the mic input not work At all or is it off and on?
Sent from my SAMSUNG-SGH-I717 using xda premium

The MIC needs some kernel changes in the sound driver.

The gapps link doesn't work
Sent from my SAMSUNG-SGH-I717 using xda premium

rkingsparx81 said:
The gapps link doesn't work
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
http://goo.im/gapps/gapps-jb-20130301-signed.zip

Thanks
Sent from my SAMSUNG-SGH-I717 using xda premium

It was taking me to the gapps page on goo.im (which was intended), but I went ahead and edited it to be the latest file.

Been running since the first un-offical builds, been running the offical for a few weeks now, been running like a charm.
Just an FYI, On my device when I try to reboot to recovery, the device just reboots in to android.
Edit; Brief video for you, as you can see it reboots like normal (Sorry for the background noise!)
http://www.youtube.com/watch?v=9vyr_zya5dQ

Flashed 04.04.13 and all is good the weather on the lock screen is now displayed it didn't work for me on the 03.04.13
Sent from my Amazon Kindle Fire2 using xda premium

Yeah, one of the funny bits with installing Nightlies is that randomly stuff will break. I try and keep track of which has the most working as I'm moving along so that I can revert to a more "stable" version if needed.

Hashcode, will we get the m3 build?
Gesendet von meinem Amazon Kindle Fire2 mit Tapatalk 2

Thank you so mutch .just downloaded the m3 build. So nice to have you.
Gesendet von meinem Amazon Kindle Fire2 mit Tapatalk 2

Yeah we weren't on the original M3 list so I had to get added and for a re-run that the CM team did a day later.
From now on, we should be on the right list to get the monthly stable builds.

Hashcode, there is a little problem with the naming of our otter2 device. It shows me on the get.cm site that this is a kindle fire hd.

Yep, i reported it yesterday.
Sent from my DROID RAZR HD using Tapatalk 2

Building CM10.1 from source
Hashcode, I have successfully built CM10.1 from source for the otter2 by following the instructions in this thread and the CyanogenMod wiki. Thanks for the great work.
However, I did have a couple of issues that I had to work around. I'm not sure if it's because I did something wrong or because there is a problem. When I got to the "Extract Proprietary Blobs" section and ran the device/amazon/otter2/extract-files.sh script, I received an error message saying that the lib/hw/sensors.otter.so file couldn't be found. I poked around the filesystem on my KF2 (running CM10.1 nightly cm-10.1-20130411-EXPERIMENTAL-otter2-M3), and found that there was a lib/hw/sensors/otter2.so file.
Similarly, the file vendor/amazon/otter2/otter2-vendor-blobs.mk also contained the reference to otter rather than otter2, and caused a problem later in the build cycle.
By changing the otter to otter2 in both device/amazon/otter2/proprietary-files.txt and vendor/amazon/otter2/otter2-vendor-blobs.mk, I was able to get the build to complete successfully. Is this a known issue or did I do something wrong?
Thanks.

I noticed i only have 673 total ram with this rom...my ram has been stolen lol...I flashed from this cm10.1 to stock rom, and on stock ram shows right.. around 924 total.. but with this rom im missing ram, i only have 673 total.. Possible bug? What is the cause an how can i fix this?

Newest nightlies will include an all new audio driver in the Android OS. It works, but it's not finished (no MIC support yet).
I'll try and keep this updated as testing continues.

Did anyone else have issues with the last nightly not booting? I tried flashing 17 twice but kept letting stuck at the boot logo. Flashed 15 back again and up and running again.
Sent from my Amazon Kindle Fire2 using Tapatalk HD

Related

[ROM] Ubuntu Touch Preview [02/27: Alpha Update #1]

** Work-In-Progress: Ubuntu Touch Preview is just that.. a PREVIEW. Do not complain about missing features, etc. The OS isn't nearly ready for primetime. **
THIS REQUIRES THE 2ND-BOOTLOADER/RECOVERY ALREADY BE INSTALLED ON YOUR DEVICE. IF YOU DON'T HAVE THAT, THEN START HERE:
http://forum.xda-developers.com/showthread.php?t=2128175
Curious as to how the Ubuntu Touch Preview looks? Why not load it on your Kindle Fire HD and see for yourself.
CHANGES:
[02/27] Fixed the UI DPI settings. Needs to re-flash following the instructions below.
Instructions [CHANGED 02/27]:
1. Make a Titanium Backup and/or backup in recovery of your current Android. This preview is fun to play with but not a replacement for something as developed as CM 10.1
2. Download the Kindle Fire HD 8.9 Mini-Android base for Ubuntu Touch and place it on your device:
[02/27] http://goo.im/devs/Hashcode/jem/ubuntu-phablet/phablet-20130227-jem.zip
md5sum: dedfd4cfb56f234112140272c4b67ae5
3. Download the latest Ubuntu Touch Preview Filesystem .zip from Ubuntu:
http://cdimage.ubuntu.com/ubuntu-touch-preview/daily-preinstalled/current/quantal-preinstalled-phablet-armhf.zip
If the above link is broken, use this link for a full listing of the current build files (download the quantal-preinstalled-phablet-armhf.zip .. soon to be raring-preinstalled-phablet-armhf.zip):
http://cdimage.ubuntu.com/ubuntu-touch-preview/daily-preinstalled/current/
4. Reboot into recovery. Wipe system and Factory Reset (wipes data/cache).
4a. Wipe system and Factory Reset (wipes data/cache).
IMPORTANT:
4b. Install the quantal-preinstalled-phablet-armhf.zip FIRST, and then the phablet-2013xxxx.zip SECOND.
5. Reboot and Enjoy
NOTE: The preview comes pre-loaded with several users in the login screen and they have data to browse around with. Move to the "Guest" account and tap on area where it tells you to login.
WHAT WORKS:
Display
Touch screen
Wifi
WHAT DOESN'T WORK:
There's so much that is still being implemented into the Touch version of Ubuntu, that this list could get pretty long.
No sound obviously (WIP for all ROMs)
[*] [FIXED 02/27] Need to adjust the GRID_UNIT_PX in /home/phablet/.bashrc to be slightly smaller so that the on-screen keyboard fits correctly (I'd guess 16-18).
Barely any sensors other than touchscreen work. IE: no rotation, etc. Ubuntu WIP issue.
No HD codecs (still being worked on) Ubuntu WIP issue.
Battery doesn't get a reading currently due to the custom sysfs path. (Can fix in kernel updates later)
No screen timeout / auto blank -- becareful when walking away from the device. Need to press the power button to turn the screen off. Ubuntu WIP issue.
RELATED UBUNTU TOUCH LINKS:
(Some of these describe how to install it on devices -- you can ignore those instructions and follow the above for the Kindle Fire HD 8.9)
Ubuntu Touch Wiki: https://wiki.ubuntu.com/Touch/
Release Notes: https://wiki.ubuntu.com/Touch/ReleaseNotes
IRC Channel on freenode.net: #ubuntu-touch
RESERVED
Great man!!!
Thanks!
Great work Hashcode! Downloading NOW!
Re: [ROM] Ubuntu Touch Preview [02/26: Alpha]
I thought about asking you for a port of this some days ago, but i figured you'd be too busy. Thanks Hash!
Sent from my Nexus 4
Re: [ROM] Ubuntu Touch Preview [02/26: Alpha]
Hash code does it again!
Sent from my Amazon Kindle Fire HD
Awesome.! I just read about this in Engadget and hash already has it up. .
Hashcode said:
** Work-In-Progress: Ubuntu Touch Preview is just that.. a PREVIEW. Do not complain about missing features, etc. The OS isn't nearly ready for primetime. **
THIS REQUIRES THE 2ND-BOOTLOADER/RECOVERY ALREADY BE INSTALLED ON YOUR DEVICE. IF YOU DON'T HAVE THAT, THEN START HERE:
http://forum.xda-developers.com/showthread.php?t=2128175
Curious as to how the Ubuntu Touch Preview looks? Why not load it on your Kindle Fire HD and see for yourself.
CHANGES:
[02/27] Fixed the UI DPI settings. Needs to re-flash following the instructions below.
Instructions [CHANGED 02/27]:
1. Make a Titanium Backup and/or backup in recovery of your current Android. This preview is fun to play with but not a replacement for something as developed as CM 10.1
2. Download the Kindle Fire HD 8.9 Mini-Android base for Ubuntu Touch and place it on your device:
[02/27] http://goo.im/devs/Hashcode/jem/ubuntu-phablet/phablet-20130227-jem.zip
md5sum: dedfd4cfb56f234112140272c4b67ae5
3. Download the latest Ubuntu Touch Preview Filesystem .zip from Ubuntu:
http://cdimage.ubuntu.com/ubuntu-touch-preview/daily-preinstalled/current/quantal-preinstalled-phablet-armhf.zip
If the above link is broken, use this link for a full listing of the current build files (download the quantal-preinstalled-phablet-armhf.zip .. soon to be raring-preinstalled-phablet-armhf.zip):
http://cdimage.ubuntu.com/ubuntu-touch-preview/daily-preinstalled/current/
4. Reboot into recovery. Wipe system and Factory Reset (wipes data/cache).
4a. Wipe system and Factory Reset (wipes data/cache).
IMPORTANT:
4b. Install the quantal-preinstalled-phablet-armhf.zip FIRST, and then the phablet-2013xxxx.zip SECOND.
5. Reboot and Enjoy
NOTE: The preview comes pre-loaded with several users in the login screen and they have data to browse around with. Move to the "Guest" account and tap on area where it tells you to login.
WHAT WORKS:
Display
Touch screen
Wifi
WHAT DOESN'T WORK:
There's so much that is still being implemented into the Touch version of Ubuntu, that this list could get pretty long.
No sound obviously (WIP for all ROMs)
[*] [FIXED 02/27] Need to adjust the GRID_UNIT_PX in /home/phablet/.bashrc to be slightly smaller so that the on-screen keyboard fits correctly (I'd guess 16-18).
Barely any sensors other than touchscreen work. IE: no rotation, etc. Ubuntu WIP issue.
No HD codecs (still being worked on) Ubuntu WIP issue.
Battery doesn't get a reading currently due to the custom sysfs path. (Can fix in kernel updates later)
No screen timeout / auto blank -- becareful when walking away from the device. Need to press the power button to turn the screen off. Ubuntu WIP issue.
RELATED UBUNTU TOUCH LINKS:
(Some of these describe how to install it on devices -- you can ignore those instructions and follow the above for the Kindle Fire HD 8.9)
Ubuntu Touch Wiki: https://wiki.ubuntu.com/Touch/
Release Notes: https://wiki.ubuntu.com/Touch/ReleaseNotes
IRC Channel on freenode.net: #ubuntu-touch
Click to expand...
Click to collapse
Hi, hashcode.
yesterday, the procedure is different, which is correct?
"4b. Install the quantal-preinstalled-phablet-armhf.zip FIRST, and then the phablet-2013xxxx.zip SECOND."
And, can i only flash the phablet-2013****.zip for update?
I would download the filesystem again and reflash. Its on nightly updates now.
Sent from my DROID RAZR HD using Tapatalk 2
Likelyhood of KFHD7 Port?
Is there any chance that you'll make a Kindle Fire HD 7 port? It seems a little odd that it's the only fire with no support...
kindle fire hd
any updates on wip? still have no sound?
tufeijoe said:
any updates on wip? still have no sound?
Click to expand...
Click to collapse
Last update from hash code mentioned being "80% with audio"
Sent from my SGH-I897 using xda app-developers app
How to create this from source code? Not found the repository.
Download the Kindle Fire HD 8.9 Mini-Android base for Ubuntu Touch and place it on your device:
Add ubuntu phablet build repo and guide
tufeijoe said:
any updates on wip? still have no sound?
Click to expand...
Click to collapse
https://github.com/JoeyJiao/android_local_manifest/blob/phablet/README.mkdn
Hey should this work with the newer "raring" version? I'm having some trouble. I got a blank screen with backlight after installing both zips. I did a wipe too. I'll try one more time and see.
thanks
Yep, I need to debug the raring boot. None of my devices work atm.
Sent from my XT894 using Tapatalk 2
Hashcode said:
Yep, I need to debug the raring boot. None of my devices work atm.
Sent from my XT894 using Tapatalk 2
Click to expand...
Click to collapse
Bump to say thanks for all the work on this and express continued interest (my device is the kf2).
Also isnt the current release ver. Saucy?
Can't wait for this one... Thanks Hash:thumbup:
Sent from my Amazon Kindle Fire HD using xda app-developers app
any updates?
Would love to know if we are close to a working rom based on the latest release. I have tried Quantal, Raring, and Saucy on my KF HD 8.9 with no luck so far. @Hashcode I am sure that you have a million things going on, and you efforts are greatly appreciated, and highly respected! Thanks!
No luck
I tried the quantal and saucy version, but after rebooting I see the orange and blue Kindle logo followed by a black screen. I've waited for at least 15 minutes. Any ideas?

[ROM][DEV] Ubuntu Touch For B&N Nook Tablet

DISCLAIMER: You should know by now that anything you do can and probably does void warranties, can and may brick your devices, etc etc yada yada.... This is my first ever attempt at a port, second ROM to ever build. The base for this is CM10.1 maintained by the official devs for the B&N Nook Tablet (acclaim), so complete props to everyone who has gone looney to get us here. This port isn't very usable and as such is no daily driver by any means.
I will try to explain the details of building as best as I can remember to anyone who wants to know. I had to comment out certain lines here and there and add my changes below them. Being new to this all, I have yet to set up a git for the sources. I just wanted to get this up as I haven't seen anyone else post this for Nook Tablet. From what I know, this should work for the 8g and 16g as this is based off the Official CM10.1 for us. Again, your risk, there are plenty of ways to unbrick this device and plenty of guides.
Discussion thread:
[ROM][DISCUSSION] Ubuntu Touch B&N Nook Tablet
For those of you just wanting to take it for a spin:
(name change as I am building using two different sets of repos, one with only a local branch based off the cm repos, and my own that I will push updates to)
Download Device Specific Build:
Build 5: ut-cm-20130610-acclaim.zip - 35.72 MB
Older Builds:
(The following builds screen displays stop working for newer Ubuntu fs builds)
Build 4: ubuntu_touch-20130529-acclaim.zip - 35.54 MB
Build 3: ubuntu_touch-20130524-acclaim.zip - 34.94 MB
Build 2: ubuntu_touch-20130513-acclaim.zip - 34.90 MB
Build 1: ubuntu_touch-20130511-acclaim.zip - 34.90 MB
Download Ubuntu FS File:
Saucy is the new Raring
http://cdimage.ubuntu.com/ubuntu-touch-preview/
Installation:
1) put both files on your sdcard by your method of choice
2) go into recovery
3) format data/factory reset <-- NOTE: If you want to save data, new builds should backup stuff, not sure what all though.
4) format system to ensure clean install
5) flash Custom build and flash Ubuntu fs file
6) reboot and pray it works.
After boot up notes:
- May have to push power button to get initial display.
-To get a chroot shell from your computer's terminal:
Code:
$ adb root
$ adb shell
$ ubuntu_chroot shell
- Keyboard does not currently work on Home screens. In Raring I would restart ubuntu-session. I do not see it in Saucy. 2013-06-15: playing around and starting the 'killprocs' service, keyboard worked afterwards.
Code:
[email protected]:/# service killprocs start
- Wifi seems to need a reboot to work correctly currently
- Added a script to change the display size.. If you do not like it or want to mess around with it, you can adjust the display through the chroot by editing the acclaim.conf file. After editing, reboot.
Code:
/etc/ubuntu-session.d/acclaim.conf
Build notes!
Build 5:
- Updated ubuntu sources, resulting display seems fixed for newer builds! (circa June 1st or maybe a little sooner)
- Honestly not sure atm if build 4 has it, but added a script to auto fix the display size (adds acclaim.conf for you), Saucy images seem to not require a reboot, Raring images do (or an ubuntu-session restart).
Build 4:
- Using wpa_supplicant 8 instead of 8_TI
Build 3:
- Wifi works with some terminal junk!
Build 2:
- Videos stopped working for some reason, need to debug.
- Apps no longer force close
- Wifi still down
Build 1:
- It boots
- Display works
- Sound Works
- Videos Work
- No wifi
- All apps force close after a couple of seconds
- No rotation
I'm new to all this git stuff, but figured I'd try it out:
https://github.com/dejello/android_device_bn_acclaim
https://github.com/dejello/android_kernel_bn_acclaim
I will be adding a wiki or readme on the device repo that shows dependencies and other edits needed to build your very own.
-dejello
Build 2! and some pics...
THIS POST IS NO LONGER REQUIRED, but kept for informational purposes
Updated - Build 3 now up!
Wifi seems to be working with some terminal junk. I followed this page as a reference after figuring out the wlan module wasn't being loaded: http://www.omappedia.com/wiki/Mac80211_based_open_source_architecture#Procedure_to_build_WLAN_and_test_on_Ubuntu_FS
NOTE: The module is apparently being unloaded after a while, possibly to do with going to sleep, not sure atm. If you have installed the terminal core app you can get back online without plugging back in..
I did the following commands and checked the browser and I was online!
Code:
[email protected]:/ # adb shell
[email protected]:/ # ubuntu_chroot shell
[email protected]:/# sudo mount -t proc proc /proc
[email protected]:/# lsmod
[I]Module Size Used by
wl12xx 189125 0
mac80211 384303 1 wl12xx
pvrsrvkm_sgx540_120 336017 34
cfg80211 181275 2 mac80211,wl12xx
compat 2718 0 [/I]
Notice: It did not show wl12xx_sdio - which has wlan0.
Code:
[email protected]:/# insmod /system/lib/modules/wl12xx_sdio.ko
[email protected]let:/# tail -3 /var/log/kern.log
[I]May 25 23:23:09 ubuntu-phablet kernel: [ 377.563903] wl12xx_set_power: 1
May 25 23:23:10 ubuntu-phablet kernel: [ 377.900939] wl12xx_set_power: 0
May 25 23:23:10 ubuntu-phablet kernel: [ 377.911682] wl12xx: loaded[/I]
[email protected]:/# ifconfig wlan0 up
[email protected]:/# tail -3 /var/log/kern.log
[I]May 25 23:25:04 ubuntu-phablet kernel: [ 492.360870] wl12xx_set_power: 1
May 25 23:25:05 ubuntu-phablet kernel: [ 492.839141] wl12xx: firmware booted (Rev 6.3.10.0.133)
May 25 23:25:05 ubuntu-phablet kernel: [ 492.864288] ADDRCONF(NETDEV_UP): wlan0: link is not ready[/I]
[email protected]:/# iwconfig wlan0 essid "tinyguest"
[email protected]:/# dhclient wlan0
[email protected]:/# ip addr
[I]......
7: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
link/ether 58:67:1a:53:b1:bd brd ff:ff:ff:ff:ff:ff
inet 192.168.2.13/24 brd 192.168.2.255 scope global wlan0
inet6 fe80::5a67:1aff:fe53:b1bd/64 scope link
valid_lft forever preferred_lft forever[/I]
Note: "tinyguest" is my test guest network with no security atm, insert the SSID of your network. I have not tested yet to see if this will work with security on.
Not sure how stable everything is, but hey, it's a dev preview so
UPDATE: I just had a realization.... After insmoding wl12xx_sdio.ko and bring the wlan0 up, I simply restarted the network manager service and now the gui shows up! I do need to check my wpa_supplicant file as I had been playing with it. <-- Fine unedited. I am also running a new minidroid build compiled using wpa_supplicant 8 vs wpa_supplicant 8_TI that I have yet to upload. I will need to see if this has any effect. I was having an issue compiling the TI version and was getting annoyed trying to figure it out New commands are as follows:
Code:
[email protected]:/ # adb shell
[email protected]:/ # ubuntu_chroot shell
[email protected]:/# insmod /system/lib/modules/wl12xx_sdio.ko
[STRIKE][email protected]:/# ifconfig wlan0 up[/STRIKE] <-- DIdn't even up it this past time, seems that restarting the network-manager service up's it.
[email protected]:/# service network-manager restart
Will be updating this post and adding a pic..
Doing great . Keep up. And why not tranfering it to nt dev thread?
Στάλθηκε από το Barnes & Noble Nook Tablet μου χρησιμοποιώντας Tapatalk 2
demetris_I said:
Doing great . Keep up. And why not tranfering it to nt dev thread?
Στάλθηκε από το Barnes & Noble Nook Tablet μου χρησιμοποιώντας Tapatalk 2
Click to expand...
Click to collapse
Thanks nothing in comparison to what you've been up to lately though. I probably should see about getting this thread moved over shouldn't I....
I'm really excited, I hope your project takes off in a big way
I admit to confusion, though - you say the base of this is the great work done on cm10.1 nightlies by the devs here, so is this actually ubuntu touch, or a skin over android? I'm not being critical, just looking to understand.
Thanks!
tmoulder said:
I'm really excited, I hope your project takes off in a big way
I admit to confusion, though - you say the base of this is the great work done on cm10.1 nightlies by the devs here, so is this actually ubuntu touch, or a skin over android? I'm not being critical, just looking to understand.
Thanks!
Click to expand...
Click to collapse
Sorry for the late reply, yes, currently Ubuntu Touch is running in a chroot on a mini build of android.
Other notes, today I started trying to figure out what exactly breaks the display on the newer ubuntu fs images.
dmesg shows ubuntu-session terminating with: "terminated with status 139". I still have an image from May 24th that works, and upon updating libplatform-api1-hybris or ubuntu-platform-implmentation-android (both of which will install the other) the display breaks with ubuntu-session terminating with: "terminated with status 127" or depending on what I've done ocassionally some other error.
More searching to follow....
UPDATE: see Build 5 notes, I hadn't fully updated my ubuntu sources apparently Display seems to work now!
PS - the git stuff isn't current atm, but the edits should still work. the wiki dealio needs work.
dejello said:
Sorry for the late reply, yes, currently Ubuntu Touch is running in a chroot on a mini build of android.
Other notes, today I started trying to figure out what exactly breaks the display on the newer ubuntu fs images.
dmesg shows ubuntu-session terminating with: "terminated with status 139". I still have an image from May 24th that works, and upon updating libplatform-api1-hybris or ubuntu-platform-implmentation-android (both of which will install the other) the display breaks with ubuntu-session terminating with: "terminated with status 127" or depending on what I've done ocassionally some other error.
More searching to follow....
UPDATE: see Build 5 notes, I hadn't fully updated my ubuntu sources apparently Display seems to work now!
PS - the git stuff isn't current atm, but the edits should still work. the wiki dealio needs work.
Click to expand...
Click to collapse
You say build 5 should fix the display not showing? I tried it and the "Current" Saucy phablet image and got nothing.
I'm about to try the Raring image and see if it works...
ajbiz11 said:
You say build 5 should fix the display not showing? I tried it and the "Current" Saucy phablet image and got nothing.
I'm about to try the Raring image and see if it works...
Click to expand...
Click to collapse
Nope...Saucy bootloops...I don't know how to get a logcat through fastboot, will look it up...
there was a period recently where they were breaking things alot with changes... I have a working version I can upload, but if they update hybris and/or the platform-api again it'll break until i update the build.
Sent from my SCH-I510 using xda app-developers app
Nook HD?
Great work! Any idea if you might get around to making a similar build for the Nook HD/HD+?
iCello said:
Great work! Any idea if you might get around to making a similar build for the Nook HD/HD+?
Click to expand...
Click to collapse
That is in my plans as I just got the HD+, not sure just yet as to when.. I need to pm verygreen or someone else and see what all I need to build cm10.1 first as I am missing something. Once I get a working build I will work on Ubuntu.
Sent from my SCH-I510 using xda app-developers app
dejello said:
That is in my plans as I just got the HD+, not sure just yet as to when.. I need to pm verygreen or someone else and see what all I need to build cm10.1 first as I am missing something. Once I get a working build I will work on Ubuntu.
Sent from my SCH-I510 using xda app-developers app
Click to expand...
Click to collapse
Alright, sounds good!
iCello said:
Alright, sounds good!
Click to expand...
Click to collapse
Ok, seems I just wasn't paying attention.. Replaced the boot image in the zip with the apparent non-sdcard version >.> CM10.1 booted so I will work on a build in a bit. For the moment though the tv is calling me
Are you planning non starting a new thread for ubuntu on the HD+?
Sent from my Nook HD+ using Tapatalk 2
Not sure atm.. If not I will update the title of this one
Sent from my SCH-I510 using xda app-developers app
So... if the Ubuntu will be available for HD+, changing a pair of things would make it for HD, is it correct?
Thank you!
dejello said:
That is in my plans as I just got the HD+, not sure just yet as to when.. I need to pm verygreen or someone else and see what all I need to build cm10.1 first as I am missing something. Once I get a working build I will work on Ubuntu.
Sent from my SCH-I510 using xda app-developers app
Click to expand...
Click to collapse
I would love this on my Nook HD (not HD+), I have ubuntu installed on all of my systems and love it over windows.
Sent from my Nook HD using XDA Premium HD app
Once I get working builds again (with the new stuff they've added for booting) I will build one for the HD for which I will need testers as I do not have an HD. Honestly did not really work on it today as I am really tired. Looks like I managed to get that one build in before they added this stuff.
dejello said:
Once I get working builds again (with the new stuff they've added for booting) I will build one for the HD for which I will need testers as I do not have an HD. Honestly did not really work on it today as I am really tired. Looks like I managed to get that one build in before they added this stuff.
Click to expand...
Click to collapse
I'll gladly test a build for Nook HD
Sent from my Nook HD using XDA Premium HD app

[ROM][Linaro 4.7][P31xx][JB][4.3] CM 10.2 w/Espresso10++ 3.0.96 + Code Review

Hi all,
I will be building cm-10.2 from source nightly and posting it here. These builds are straight from the CyanogenMod Github repo.
These are Unofficial Builds, built by me, from the nightly sync with the source repo. I am not part of the core CM dev team, but I do contribute to the Code Review: http://review.cyanogenmod.org/#/, I'm just a man with a compiler.
After you flash the rom please open up settings / developer settings and then set root access to ADB and Apps. You can access developer settings by tapping the build number 7 times on the about screen.
Thanks Codeworkx!
---------------------------------------------------
P3110/P3113=====>: http://d-h.st/DTz - 20130919 Posted!
TabletUI Patch===>: http://d-h.st/Z1E
ChangeLog====>: http://changelog.bbqdroid.org/
P3100========>: http://d-h.st/eP4 - 20130919 Posted!
TabletUI Patch=>: http://d-h.st/32y
Espresso10++ Kernel: http://d-h.st/UPc - 3.0.96 - p31xx
- Compiled with Linaro 4.7 toolchain. (13.08)
- Overclock and Variable Voltage control - credit to: @ketut.kumajaya & cmenard.
- Xbox 360 wired / wireless controller + LED support.
https://github.com/codyf86/android_kernel_samsung_espresso10/tree/cm-10.2
https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/log/?h=linux-3.0.y
http://releases.linaro.org/latest/components/android/toolchain/4.7
Gapps 4.3: http://d-h.st/NhB
Explore my Dev-Host: http://d-h.st/users/codyf86
ClockWorkMod Recovery P3110/P3113: http://d-h.st/vZi - 6.0.3.7 - Tar!
ClockWorkMod Recovery P3110/P3113: https://www.file1.info/gmsY2BC - Zip!
ClockWorkMod Recovery P3100:====> http://d-h.st/eKO - 6.0.3.7 - Tar!
ClockWorkMod Recovery P3100:====> https://www.file1.info/PACugfc - Zip!
---------------------------------------------------
IR has been merged into official nightlies!!!
Special thanks @ketut.kumajaya!
https://github.com/kumajaya/android_kernel_samsung_espresso10/tree/cm-10.2
---------------------------------------------------
Shinobisofts' Universal Tar to Flashable Zip Program. (Python)
http://forum.xda-developers.com/showthread.php?t=2419920
Android-Andis' recovery.img to Flashable Zip Script:
http://forum.xda-developers.com/showpost.php?p=44725849&postcount=390.
xNiiCADEMUS' ROM Installation video.
http://youtu.be/uooLuG0Ydr8
---------------------------------------------------
Thanks to Caldair for ApG!
Thanks to Jiangyi for IR insight and general awesomeness!
Thanks to Kenundrem for pulling blobs and other files for me!
---------------------------------------------------
CMAcount:
http://www.cyanogenmod.org/blog/cyanogenmod-account
https://account.cyanogenmod.org/login
I have also compiled in the following from the CyanogenMod Code Review:
If you saw something listed below, that is no longer listed, it has been merged.
SystemUI: Add ADB over WiFi QuickSettings Tile
http://review.cyanogenmod.org/#/c/50211/
http://review.cyanogenmod.org/#/c/50210/4
USB audio support [1/2]&[2/2]
http://review.cyanogenmod.org/#/c/49295/
http://review.cyanogenmod.org/#/c/49296/
usbaudio: Fix output device routing
http://review.cyanogenmod.org/#/c/49292/
Allow showing statusbar on top of fullscreen window.
http://review.cyanogenmod.org/#/c/48352/
Add configuraion for showing statusbar on top of fullscreen window.
http://review.cyanogenmod.org/#/c/48359/
Add the possiblity of using secondary storage for user 0.
http://review.cyanogenmod.org/#/c/47918/
To use the above patch, if you choose to:
Go into Settings / Storage and cycle the check box once.
After you cycle the setting once, choose on or off and reboot.
Recovery: support format external storage to custom fstype using vold.
http://review.cyanogenmod.org/#/c/49899/
Recovery/Vold: Use quick format for NTFS volumes.
http://review.cyanogenmod.org/#/c/49920/
Hit thanks if I helped!
------------------------------------------------------------------------
My Fast and Helpful Socket API for Python 3.2.2+Android:
https://github.com/codyf86/fahsocket-py3-android
You build fast.
But you also build only for one device (or 2 really).
Sent from my LG-P690b using Tapatalk 2
I can build for anything if you ask nice enough. I'd like to stick to samsung devices though.
Luigi asked if I can add the IR blaster changes for the p3113 that had been patched into cm 10.1 on a few unofficial builds. Let me get the 0804 build out of the way; as I will start building it in about 6 hours or so. Then I'll look into adding support for it.
CodyF86 said:
I can build for anything if you ask nice enough. I'd like to stick to samsung devices though.
Click to expand...
Click to collapse
Wow! thanks.
Anyway whats the different from this to codeworks build?
I mean i can build for the supported devices. I'm not trying atm to add support to unsupported devices.
These are from the same source I'm just building them nightly and posting them. The last p3110 build was from 0730, so I built / will build the latest ones everyday.
CodyF86 said:
Luigi asked if I can add the IR blaster changes for the p3113 that had been patched into cm 10.1 on a few unofficial builds. Let me get the 0804 build out of the way; as I will start building it in about 6 hours or so. Then I'll look into adding support for it.
Click to expand...
Click to collapse
can't wait!
Sent from my TouchPad using xda app-developers app
I flashed the 3110/3113 on 3113 works well thank you sir
If I could add a +1 to the IR addition
If you need a tester for a 3113 cm ROM let me know
Sent from my GT-P3110 using xda premium
CodyF86 said:
I can build for anything if you ask nice enough. I'd like to stick to samsung devices though.
Click to expand...
Click to collapse
Thanks..!!
thanks +1
Sent from my GT-P3100 using XDA Premium HD app
Not waiting for a new constructor of cm, but ok, let's see What do you have to offer us ...
Lol I think you may have misunderstood. This isn't a spin off of cm-10.2 or another version of it. This is literally cm-10.2 compiled from the repo sources and I usually sync after midnight then build. The last cm-10.2 build for both p3110 and p3100 was 20130730.
I compiled the latest from the repo and posted it and I'm just going to keep on rebuilding everynight and post it until cm-10.2 starts building automatically at night for all devices with a build server; Like they do with 10.1 atm,
CodyF86 said:
Lol I think you may have misunderstood. This isn't a spin off of cm-10.2 or another version of it. This is literally cm-10.2 compiled from the repo sources and I usually sync after midnight then build. The last cm-10.2 build for both p3110 and p3100 was 20130730.
I compiled the latest from the repo and posted it and I'm just going to keep on rebuilding everynight and post it until cm-10.2 starts building automatically at night for all devices with a build server; Like they do with 10.1 atm,
Click to expand...
Click to collapse
then my confusion be gone
so this is excatcly like what codeworkx create.
glad to have two mainteners for this device:good:
antutu said:
then my confusion be gone
so this is excatcly like what codeworkx create.
glad to have two mainteners for this device:good:
Click to expand...
Click to collapse
He builds more often. Not only that but he will try to implement IR Blaster funtionality for P3113.
P3100 boots up without problems
You can't control the wind, but you can adjust your sails
Sent Form My Galaxy Tab 2 GT-P3100 ,Dual booted using Black Hawk Kernel
Luigi2012SM64DS said:
You build fast.
Click to expand...
Click to collapse
damn fast!! TabletUI patch run perfect :angel:
http://forum.xda-developers.com/sh....1/CM10.2/SlimBean] Tablet UI - Auto-Patcher
On p3100
Here is 20130804 for p3110. p3100 is building right now. I fell asleep last night or I would have already posted both lol. I'll update the first post also.
P3110: http://d-h.st/TAe
P3100: Building Now!
Ok so p3100 is building now and will be done in an hour or two, but I have to run some errands and won't be back for 3 or 4 hours. I'll post p3100 when I get back, sorry for the delay.
I'm using next kernel 1.7 + CyanogenMod 4.3. Runs great i can't detect any trouble. Just edited build.prop file to fix bootanimation
Sent from my GT-P3100 using xda app-developers app
Why no credit´s to @codeworkx or CM-Team in OP? Nobody really thought codeworkx would work for us on CM10.2 ... but he did!!! And thats why i think credits should be added....!
Thank´s for the daily nightlys.

Android 4.4 Kit Kat Discussion Thread

This thread is for the developers to discuss the bugs and problems of the kitkat development for the p990.
Nice that you created a thread for kitkat! Really thanks
So for the progress on cm 11:
It is really difficult to find the cause of the dark screen, because we can't get an adb connection to working. The devices don't show up with adb devices
Maybe it is disabled at the moment
We can't take all changes from your slimroms repo, because cyanogenmod toke another way in handling backward compatibility. So for now we have a dark screen with cm 11 and no adb
Here are some of the threads from other tegra2 devices which I'm following:
Galaxy R: link
Galaxy Tab 10.1: link
Captivate Glide: link
Xoom: link
P990: link
Additional T2 devices where I didn't see any Kitkat related threads, yet:
Eee Pad TF101: link
Atrix 4G: link
All still suffer from the same problems, we need some proper workarounds (in frameworks/native most likely) to fix the hot reboots before we can move on to fix the smaller problems.
I've posted in some of them in order to help with other problems (like the set_metadata one where I send the fix to @DJNoXD as well), but I have no idea how to fix the hot reboots currently.
Personally I don't see a use in fixing various stuff as long as the device is too unstable thanks to the reboots (that's why you won't find any 4.4 thread from my so far).
I'm just collecting some information in this thread to have everything together.
Therefore some more stuff regarding the device stuck at boot which we faced earlier as well:
tonyp said:
The only way to fix the blobs would be an update by nvidia / the vendors - which isn't happening obviously.
So you need to workaround the limitations of the old EGL in the sources to re-add compatibility (which btw had to be done for Android 4.3 and partly Android 4.2 as well).
The reason that CM11 doesn't boot up for you is that CM hasn't merged the required patches.
The commits do exist on CMs gerrit though:
http://review.cyanogenmod.org/#/q/s.../android_frameworks_native+branch:cm-11.0,n,z
They're new implementations of the CM10.2 patches by arcee.
Note that in some first tests the new ones didn't work for me on my tegra2 phone anymore - somethings seems to be broken in them for the tegra2 architechture.
The OmniROM has (had? I think they partly reverted it here) used forwardports of the old CM10.2 patches - which the SlimROM has merged as well in a similiar manner.
But this only fixes booting, I still do have way to many hot reboots so some more stuff has changed in 4.4 - which I didn't manage to fix or workaround so far.
What we need is someone with that kind of deep hardware knowledge.
All in all: Blindly changing blobs or other libs won't help here at all. Just building against different framework/native trees won't either.
The surfaceflinger and probably some more stuff in frameworks/native needs to get worked on in code.
Currently there doesn't exist a tegra2 device which fully works to my knowledge - and I'm following a couple ones like the Galaxy R, the Xoom, the Transformer TF 101, the Atrix and the Galaxy Tab 10.1.
I'm working on the 2x, but have way too less time at the moment to dig any deeper into the code - while the current ROM boots (using my frameworks/native repo here) and has a working ril, wifi & storage it's nowhere near a daily driver thanks to frequent hot reboots.
Click to expand...
Click to collapse
Edit: Reminder: Do not spam in this forum section!
I will delete all "thanks" posts or similiar non-development related ones without a comment.
When i use the sources for frameworks native from @DJNoXD, i have less then 2 hot reboots a day. I even use it as daily driver with a work around for wifi.
I think if we could find the commits that broke the stability we could search for a work around or fix. I already tried it only for the sufaceflinger but i had no success, because it still worked properly, so it maybe is related to libgui or i think libui?
Took me hours for the surfaceflinger, so it will take even more time for all other in framework native. When i found some time during the week, i will try.
But KitKat is awesome related to RAM, Multitasking and performance.
Gesendet von meinem LG-P990 mit Tapatalk
Evervolv frameworks/native etc were no help getting the tf101 to boot omni. So far we're at Boot Animation
thx to
kishoreinme said:
Having the 3 perfhud .so files in /lib/egl/ causes this. Delete them and it boots
Click to expand...
Click to collapse
from this thread: http://forum.xda-developers.com/showthread.php?t=2517719&page=9
http://forum.xda-developers.com/showthread.php?t=2489841&page=7
Firtecy said:
When i use the sources for frameworks native from @DJNoXD, i have less then 2 hot reboots a day. I even use it as daily driver with a work around for wifi.
Gesendet von meinem LG-P990 mit Tapatalk
Click to expand...
Click to collapse
Is that the frameworks from slimrom or from https://github.com/DJNoXD/frameworks_av1 ?
dlumberg said:
Is that the frameworks from slimrom or from https://github.com/DJNoXD/frameworks_av1 ?
Click to expand...
Click to collapse
These are the repos that I use for slimrom:
https://github.com/p990-slimrom/
Here is the GalaxyR Omni 4.4.2 development link
http://forum.xda-developers.com/showthread.php?t=2576793
Eeeeh, have I been gifted with a special P990?
I've flashed Tonyp's 4.4 build named cm-11-20131213-UNOFFICIAL-p990 and I am pretty much facing no bugs. Only bug I could find on this fine evening was that USB doesn't get mounted, it charges when connected though.
Sound works, camera works, external SD card works, WiFi works, I bet GPS works but testing that will have to wait till the morning. All of this is on a clean CM11 build without doing any modifications at all. I too am still shocked over this and since I couldn't believe it myself, so I figured I'd post a video bringing this to light.
Short YouTube footage of my P990 running KitKat: YouTube
Could someone do a full wipe and see what they come up with by flashing that same build? It seems rather surreal if 4.4 only works this well on just my phone.
Please note, I have not been under the developmental processes of this project. This is simply testing - all credits to the developers!
USB tether will not work under windows because there are no drivers found. And it works fine under linux. How to fix the hardware id (vid,pid)?
Sent from my XT875 using XDA Premium 4 mobile app

[Q] How to enable SElinux in CM11 nightlies?

How to enable SElinux and set it to enforcing mode in NOOK HD+ cm11 nightlies?
pastee said:
How to enable SElinux and set it to enforcing mode in NOOK HD+ cm11 nightlies?
Click to expand...
Click to collapse
There are no SELINUX lines in the cm11 kernel defconfig and there should be if selinux were not disabled as it is on cm11 for the nook. Don't know why its disabled as the ones doing unofficial cm11 for my phone have enabled it.
So unless your building it, might as well forget about it and wait for someone to release a build with it enabled.
pastee said:
How to enable SElinux and set it to enforcing mode in NOOK HD+ cm11 nightlies?
Click to expand...
Click to collapse
Update: 3/21/14 This nightly breaks my selinux patch and cm isn't usable with a looped error box. I rebuilt cm with the latest code and tested again but no go so its a deeper issue with how I have it set up. Since I don't have the time and they are slowly enabling selinux (as it appears and as I assume) then the last patch posted is the last selinux patch from me. That patch no longer works for any nightlies past 3/20/14 or so. Sorry, hopefully they will enable it soon.
[4/2/14 - removed ubuntu one download links... ubuntu one will cease to exist soon.]
You can now enable selinux...
Requirements:
nook hd+ ovation
cm11 emmc
Notes:
Tested on recent nightlies so don't know how far back or foward this will work.
(Re-)flash after new installs or after every update.
To remove just flash a newer cm11 build or reflash the same build. Files will be overwritten and selinux will be disabled.
Will try to post updated zips if needed though no guarantee.
I am using my selinux patch and it works.
Thanks to succulent, verygreen, and whoever else made code available that I used.
Instructions:
Reboot into recovery
flash zip file
reboot into cm11
settings -> about tablet -> scroll to bottom and it should say enforcing for selinux.
Free apps in play store to change between enforcing and permissive modes. Don't know how safe they are though I tested selinux mode changer app and it worked.
If your tablet goes down if flames don't blame me. Use at your own risk...
Please backup fully in the recovery before installing. Safety first...
Changes
feb 9th
Fixed no wifi after immediate flash of cm without reboot. You may now flash anytime you want.
(Added wl1271-nvs.bin file and set_metadata lines for it in script to make sure it gets installed.)
feb 5th
Settings -> about tablet now shows information from cm official instead of from my builds. This cleans up the find updates section too.
Should also offer best compatibility with future cm builds.
(Removed build.prop and metadata lines from scripts. Found they weren't needed afterall.)
****** Important note: Does not work with cm11 builds after ~3/20/14. +BREAKS cm11 ********
Download
Attached to this post:
****** Important note: Does not work with cm11 builds after ~3/20/14. +BREAKS cm11 ********
I would really like this for hummingbird builds.
Sent from my BN Nook HD using xda app-developers app
Blue49974 said:
I would really like this for hummingbird builds.
Sent from my BN Nook HD using xda app-developers app
Click to expand...
Click to collapse
Would try, but I'm probably not good enough to do it without that device in my hands. Maybe someone will.

Categories

Resources