Database Info

[ROM][JB]CM10 with Linaro toolchain based on Quarx repo

I've created a fork of Quarx's Defy CM10 repository, to build the latest version from Quarx but using the Linaro 4.7 toolchain. I encourage anyone who might stumble upon this thread to go to linaro.org and read about this non-profit organization and what they are trying to do. Note that TI is a supporting member of this non-profit org, as well as Samsung, LG, ARM, etc. All of these companies have interests in optimizing code performance on ARM architectures.
Now, Quarx has already created a couple of builds using the Linaro 12.10 toolchain. These builds are available as his November 17th and 18th builds, but there was much debate in the original CM10 thread (here) as to whether or not there was (1) any benefit from using the Linaro toolchain and (2) if the Linaro toolchain was adding instability. I think after these discussions Quarx decided to revert back to the original prebuilt Android toolchain.
I've created this build as an experiment, using the latest available (12.11) version of the Linaro toolchain.
Builds are located here:
http://goo.gl/vbAKN
Changelog:
cm-10-20121215-UNOFFICIAL-mb526.zip: First build, based roughly on Quarx 05-Dec or perhaps later; I just forked his most recent repo, then added Linaro 12.11 and made a few small changes to get it to build. (Thank you Quarx)
cm-10-20121218-UNOFFICIAL-mb526.zip: Cherry picked "Volume adjust sound preference 1" and Volume adjust sound preference 2 from ICS. (StevenHarperUK)
cm-10-20121219-UNOFFICIAL-mb526.zip: wpa_supplicant_6 switched to CyanogenMod official jellybean-stable branch. This means maniac's and Quarx's commits and changes involving AdHoc are not in this version. Trying to see if this helps wifi connectivity at my gym where the phone seems to get very confused and drops/connects to wifi many times. Wifi at my home is no issue. This version also reverts a change from Quarx that may or may not have an effect on reading NTFS cards... No idea, for testing.
cm-10-20121222-UNOFFICIAL-mb526.zip: using Linaro 2012.12. Screenshot option in long press power much enabled by default, cherry pick for screen off animation (not sure what benefit this was), more debugging statements in MediaProvider to debug NTFS issue.
cm-10-20121224-UNOFFICIAL-mb526.zip: same as above, but used Linaro optimizing compiler flags from Kayant, removed the screen off animation cherry pick.
cm
cm-10-20130104-UNOFFICIAL-mb526.zip: Switch to JellyX kernel repo from Blechd0se (thanks!), kernel built with standard gcc 4.4.3 while everything else is built with Linaro gcc 4.7. Seems to be stable overnight, I had to wipe cache/dalvik/data to get it to boot. I've rebooted it several times on purpose to check stability and it is, so far, stable.
The forked repo is located here:
https://github.com/skelliam/android
If you want to try to build this yourself, you *will* encounter build errors. One in particular with Linaro is regarding strict-aliasing. There is some discussion of this on the Linaro blog here. There are several other errors that you'll enounter, but fortuantely, Quarx has already created a script that checks out fixes for most of these.
So in general, the process will be something like this:
Move to a directory that will hold the sources. I just created a directory 'cm'.
Code:
$ mkdir cm
$ cd cm
$ repo init -u git://github.com/skelliam/android.git -b jellybean
Now you need to run Quarx's script to make the fixes required for Linaro. From the ROOT of your repository (in my case the cm subdirectory):
Code:
$ ./device/moto/jordan-common/apply_linaro.sh
Now, what the heck, try to build it. You will encounter more compile errors but it is worth it to see what I'm talking about. To build:
Code:
$ source build/envsetup.sh
$ brunch mb526
You should get a bunch of errors related to strict aliasing. To fix these, right now I've applied local changes on my repo, in the remaining makefiles responsible for the errors. Here are the changes I've made locally to get around these issues. I will try to make an update to the apply_linaro.sh script as Quarx did, it was 2 am when I did this and I just wanted to get it built.
Update 5-Jan-2013 I've checked in everything now, so if you use my base manifest file (from github.com/skelliam/android) you should not need to make any changes OTHER than to run the apply_linaro.sh script.

Someone mentioned that the BBC I player app doesn't work.
First of all, are we talking about this app?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So I tried this out here. On first install, when I tried to open a program, the phone became almost unresponsive, something was hogging the CPU. I had to pull the battery.
After rebooting, this app seems to work fine:
That's my experience anyway. As far as Netflix, I've just recently cancelled my subscription, so I can't do much with that one.
Sent from my MB526 using Tapatalk 2

Nice ROM seams to be verry smooth. battery life is as far as I can say quite good.
I think I found a bug - Bluetooth is not working I think. Same behavior as on quarx' 2012-11-18 - build.
At least for me. Maybe quarx' bluetooth-fix for this build can solve the problem? Couldn't test yet.

Thread moved as your OP has no format whatsoever and the Development section isn't for discussions. If you want this in Development please make it clearer that this is an actual ROM and not just a discussion and also add all credits with links to the original work. Just look at some of the other ROM threads for an example of what should be included e.g changelog/features, what changes have been made, what you're asking people to test for you to discuss, just anything really to give more info then you have given already.
Thanks
AvRS

AvRS said:
Thread moved as your OP has no format whatsoever and the Development section isn't for discussions. If you want this in Development please make it clearer that this is an actual ROM and not just a discussion and also add all credits with links to the original work. Just look at some of the other ROM threads for an example of what should be included e.g changelog/features, what changes have been made, what you're asking people to test for you to discuss, just anything really to give more info then you have given already.
Thanks
AvRS
Click to expand...
Click to collapse
Really a PM would have been fine.
This thread was created to avoid clutter in another thread.
At the bottom of the post I'm pretty sure it says that it was posted with Tapatalk from my phone? As soon as I'm on my PC I'll add as much rich content as you desire... There is only so much I can do from my phone.
Lastly, each thread IS a discussion, I have no idea what a "forum" is for other than discussing things.
Sent from my MB526 using Tapatalk 2

I'll confirm that Netflix does not work. Stuck on splash screen with loading wheel spinning. Never tried it on quarx 0512, though.
Great build, IMO. No problems on any of my heavy use apps. No reboots or freezes yet. 20 hrs uptime.
Using my standard setup; no ksm, no zRam, no overclocking, 16 bit transparency. Interactive and noop.
Sent from my Red Lens MB525 using xda app-developers app

EldonTyrell said:
I'll confirm that Netflix does not work. Stuck on splash screen with loading wheel spinning. Never tried it on quarx 0512, though.
Great build, IMO. No problems on any of my heavy use apps. No reboots or freezes yet. 20 hrs uptime.
Using my standard setup; no ksm, no zRam, no overclocking, 16 bit transparency. Interactive and noop.
Sent from my Red Lens MB525 using xda app-developers app
Click to expand...
Click to collapse
Awesome, thanks for testing it. I've been having some instability regarding wifi and Tasker, but I experienced this also with the Nov-18 from Quarx. I will keep investigating it.

On last builds by quarx I had problems with touch screen input getting delayed/unresponsive some times. Until now I don't experience that in this build, but I should use it longer to be sure.

Oh I see now it's the same as what I did before the difference was I was trying to compile CNA with it but it broke in so many places I just gave up loool I will try again I guess and see if there is indeed some improverments in CNA because I remember full linaro CM & kernel that I tried before was a bit smoother that just having linaro compiled kernel.
Anyways thanks for clearing that up for me

wskelly said:
Someone mentioned that the BBC I player app doesn't work.
First of all, are we talking about this app?
View attachment 1568120
So I tried this out here. On first install, when I tried to open a program, the phone became almost unresponsive, something was hogging the CPU. I had to pull the battery.
After rebooting, this app seems to work fine:
View attachment 1568122
That's my experience anyway. As far as Netflix, I've just recently cancelled my subscription, so I can't do much with that one.
Sent from my MB526 using Tapatalk 2
Click to expand...
Click to collapse
It was I. I was looking at the official BBC iplayer app which is here and requires the BBC Media Player to do the heavy lifting here
It's not as severe a crash as on the 05/12, where I had to yank out the battery, it crashes when it should hand off to the stream, the rest of app works, you can navigate the programme listings etc but just at the point when the stream starts on CM7.20 it hangs. I have access to 3 defys so I can confirm that is the point when the app crashes. I can also confirm the Netflix issue. Are these two related?
As I said in the other thread it is significantly snappier, I'll keep one defy on Quarx, one on this linaro build and one on CM7.20 for feedback (well at least until xmas when they're all being given as presents) :laugh:

The problem I get with all newer builds by Quarx , from 11/18 onwards, is this logcat entry: "E/MediaProvider( 9674): Can't obtain external volume ID even though it's mounted.", which causes process media to be killed all the time, making the user experience a true hell: camera, music player, Play Store, etc, etc, etc, i,e. practically nothing which requires access to my NTFS formatted 64GB card works! So, I'm always back to his 11/17 build (for a month now). I already posted thiis many times on his CM10 dev thread, but, as usual, I get ignored. You, most probably, have already read my posts about this issue there. Anyway, any thoughts if I would face this issue if I flashed your ROM?

Awesome job ...works fine on MB525 green :thumbup:...
Sent from my MB525 using xda app-developers app

casouzaj said:
The problem I get with all newer builds by Quarx , from 11/18 onwards, is this logcat entry: "E/MediaProvider( 9674): Can't obtain external volume ID even though it's mounted.", which causes process media to be killed all the time, making the user experience a true hell: camera, music player, Play Store, etc, etc, etc, i,e. practically nothing which requires access to my NTFS formatted 64GB card works! So, I'm always back to his 11/17 build (for a month now). I already posted thiis many times on his CM10 dev thread, but, as usual, I get ignored. You, most probably, have already read my posts about this issue there. Anyway, any thoughts if I would face this issue if I flashed your ROM?
Click to expand...
Click to collapse
Hi casouzaj... This is interesting that it started happening between 11/17 and 11/18, so it should be easy to find and fix.
Yes you should probably face this issue with this build because I'm using the repo from Quarx, all of the files are the same except for some changes to get it to build with Linaro.

wskelly said:
Hi casouzaj... This is interesting that it started happening between 11/17 and 11/18, so it should be easy to find and fix.
Yes you should probably face this issue with this build because I'm using the repo from Quarx, all of the files are the same except for some changes to get it to build with Linaro.
Click to expand...
Click to collapse
Thanks a lot, wskelly! Would you be meaning that you1ll get this issue fixed anytime soon?

wskelly said:
Hi casouzaj... This is interesting that it started happening between 11/17 and 11/18, so it should be easy to find and fix.
Yes you should probably face this issue with this build because I'm using the repo from Quarx, all of the files are the same except for some changes to get it to build with Linaro.
Click to expand...
Click to collapse
So, your rom will be 'fork with linaro' only, or you have plans to change something?
I ask, because after 18.11 Quarx builds start drain battery (Android OS takes half of usage), wipes, reinstalls, clean rom, nothing can help.

Great ROM!
Using bf5x batt have jumps
Bluetoot fix from quarx work!
Any idea for batt jumps? Installed on top from 18/11 quarx with full wipe>rom > gapps>reboot

After 24h use:
Verry smooth and in my opinion best responding CM10 I used until now. Usally I stick with quarx' build.
Battery drain about 2% per hour at light/normal use (just a little surfing, reading news, checking mails, etc)
Bugs so far:
Bluetooth disabling crashes phone app.
Bluetooth fix of quarx helps to at least solve the crash. Got bluetooth mouse correctly working. File transfer to a compueter doesn't work.
Reboot into bootmenu/recovery fails - just a reboot happens

wskelly said:
The completed build is located here:
http://goo.gl/vbAKN
Click to expand...
Click to collapse
Is there any mirror? I can not download from this link - download resetting every time when reaching ~25%.

casouzaj said:
The problem I get with all newer builds by Quarx , from 11/18 onwards, is this logcat entry: "E/MediaProvider( 9674): Can't obtain external volume ID even though it's mounted.", which causes process media to be killed all the time, making the user experience a true hell: camera, music player, Play Store, etc, etc, etc, i,e. practically nothing which requires access to my NTFS formatted 64GB card works! So, I'm always back to his 11/17 build (for a month now). I already posted thiis many times on his CM10 dev thread, but, as usual, I get ignored. You, most probably, have already read my posts about this issue there. Anyway, any thoughts if I would face this issue if I flashed your ROM?
Click to expand...
Click to collapse
Could this be the reason, that i am not able to listen properly to music anymore?
Every 5-10 minutes my mobile forgets almost every song on my sd-card, there are some left, but most have gone.

trurl3 said:
Is there any mirror? I can not download from this link - download resetting every time when reaching ~25%.
Click to expand...
Click to collapse
http://www.multiupload.nl/M1QNFOA0JS

[Security] fb0 world read- and writeable on Samsung Galaxy S2 with CM9.1.0 galaxys2

Hello,
the device /dev/graphics/fb0 is word read- and writeable on my device (Samsung Galaxy S2 with CM 9.1.0). I suspect it is the same way on many other devices.
Every app can read the whole framebuffer and make screenshots. If the app would do that it could also monitor the softkeyboard. The results wouldn't need to be saved because it could extract the pressed key on the fly.
I have tested a short loop in the Terminal and it worked. I was able to get screenshots from an app with the FLAG_SECURE set. Which should disallow the ability to make a shot. ( I wasn't root. ) I was able to get the fb dumps with the keyboard and the keys pressed.
You can manualy set the Permissions to 660, then only root and graphics users can use it.
Can someone please confirm this configuration on other devices?
I don't think it is intendet that every app can play keylogger.
And before you ask I havn't posted/informed anyone. Because if you look at the /dev/exynos-mem hole you want to check every other file in /dev for similar errors. So that is what I did and i can't be the only one. So I figure the blackhats are two steps ahead.

blulantern said:
Hello,
the device /dev/graphics/fb0 is word read- and writeable on my device (Samsung Galaxy S2 with CM 9.1.0). I suspect it is the same way on many other devices.
Every app can read the whole framebuffer and make screenshots. If the app would do that it could also monitor the softkeyboard. The results wouldn't need to be saved because it could extract the pressed key on the fly.
I have tested a short loop in the Terminal and it worked. I was able to get screenshots from an app with the FLAG_SECURE set. Which should disallow the ability to make a shot. ( I wasn't root. ) I was able to get the fb dumps with the keyboard and the keys pressed.
You can manualy set the Permissions to 660, then only root and graphics users can use it.
Can someone please confirm this configuration on other devices?
I don't think it is intendet that every app can play keylogger.
And before you ask I havn't posted/informed anyone. Because if you look at the /dev/exynos-mem hole you want to check every other file in /dev for similar errors. So that is what I did and i can't be the only one. So I figure the blackhats are two steps ahead.
Click to expand...
Click to collapse
I'm 90% certain this file was copypastaed from a Samsung initramfs - so some Samsung releases most likely have this setup too. I'll ask codeworkx which one.
I'm in the process of cleaning up ueventd, unfortunately this mess happened just as I was getting ready to leave for the holidays.

Entropy512 said:
I'm 90% certain this file was copypastaed from a Samsung initramfs - so some Samsung releases most likely have this setup too. I'll ask codeworkx which one.
I'm in the process of cleaning up ueventd, unfortunately this mess happened just as I was getting ready to leave for the holidays.
Click to expand...
Click to collapse
I was unable to locate the same issue in stock devices, maybe CM is using copypasta from old firmware ramdisks.

jcase said:
I was unable to locate the same issue in stock devices, maybe CM is using copypasta from old firmware ramdisks.
Click to expand...
Click to collapse
Yeah, there's a good chance it predates XWLPM. We swapped kernel sources but not ramdisks with Update7.
What builds have you looked at? I'm going to try and see if codeworkx remembers which build he pulled those from.
I'm going to attempt to do a ueventd cleanup before I leave for the holidays. It may be an "axe everything and let the rest of the team figure out what broke and needs repair" approach...

I think this may have been in a samsung leak that never got removed, it dates back to the very first commit of this file in ICS, but isn't in one of my initramfs dumps from one of the first ICS official releases.
http://review.cyanogenmod.org/#/c/28759/
If no observed regressions it will be backported to CM10/CM9 time permitting, but could take some time as I'm unavailable from tomorrow onwards until the new year.

Hi,
I did a little code search on github, this issue seems more widespread than I thought.
I can't post external links here, because I'm new
If you search on Github in Code for:
/dev/graphics/fb repo:CyanogenMod/*
You will find
CyanogenMod/android_device_htc_click » init.bahamas.rc (Rust)
CyanogenMod/android_device_geeksphone_zero » init.zero.rc (Rust)
If you don't restrict the search on a repo you will get many results for different devices, the once i checked had the permission set to 666 or 777 (in the latest revision). But I didn't find the result with the galaxys2 so i figure my results are far from complete.
Is there a mechanism to let the owners know without searching through every projekt and opening an issue there?
Thanks.

Entropy512 said:
Yeah, there's a good chance it predates XWLPM. We swapped kernel sources but not ramdisks with Update7.
What builds have you looked at? I'm going to try and see if codeworkx remembers which build he pulled those from.
I'm going to attempt to do a ueventd cleanup before I leave for the holidays. It may be an "axe everything and let the rest of the team figure out what broke and needs repair" approach...
Click to expand...
Click to collapse
Recent builds (im lazy and in bed so ill look later)
Sent from my SGH-I317M using xda premium

Entropy512 said:
I think this may have been in a samsung leak that never got removed, it dates back to the very first commit of this file in ICS, but isn't in one of my initramfs dumps from one of the first ICS official releases.
http://review.cyanogenmod.org/#/c/28759/
If no observed regressions it will be backported to CM10/CM9 time permitting, but could take some time as I'm unavailable from tomorrow onwards until the new year.
Click to expand...
Click to collapse
Makes sense since leaks often have more relaxed permissions due to debugging.
Sent from my SGH-I317M using xda premium

[ROM][AOSP] [Nightly/Release] CarbonRom JB [xt897/xt897c]

About Carbon
CarbonRom is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look at, build, and use our code on CarbonDev GitHub.
We would like to thank CyanogenMod for their device trees, framework/settings mods and their code that was incorporated into this project. We also extend our gratitude to the devs whose code that we have incorporated. Proper authorship has been maintained and can be viewed on our repository.
Special thanks also go to Slim Rom for some of their features, PA, AOKP, and anyone else we may have borrowed commits from that hasn't been mentioned here. If you feel you have been unfairly left out, please - let us know.
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash! If you have questions, ask your fellow users or ask us in #teamcarbon on freenode IRC.
Screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Carbon Updates
Join us on these Social Media Channels to keep yourself up-to-date on all the latest Carbon news, updates, contests, and more! Join our completely open Google+ community for insider conversation with devs and other users.
Download Carbon
All Carbon downloads and further information such as features, changelog, and FAQ can be found on our goo.im page.
http://goo.im/devs/carbon
Changelog
For a detailed changelog, check out the changes made each night here:
Change Log
Support
We spend an astonishing amount of time developing this software. We can't spend much time on XDA as a result, so if you need support, please try the following:
1) Search. Search, search, search. Yes, you. I don't care how unique or important your question is, it's very likely someone has adressed it already. Especially if you're even close to new at this.
2) Read our FAQ, which can be found on our goo.im page linked above. It's new, but expanding fast. Just like us!
3) Ask a question in your device forum. Someone will no doubt try to help you. Warning: this help may come in the form of telling you it's a dumb question that has been asked before. See step 1 - such are the perils of asking questions when you haven't done the research yourself. Android is about helping yourself.
4) Ask a question on our IRC channel. Connect to #teamcarbon on irc.freenode.net or click here. You'll find several other Carbon fans and usually one or more devs as well. Please be polite.
Who is Team Carbon?
Andros11
BigShotRob
Bionic Beast
dg4prez
Kejar31
mattmanwrx
morfic
nocoast
pixeldotz
slick_rick
winner00
Remember, every penny you send to us goes right back into the rom. It's used for hardware, server costs, etc - all the things that help us make Carbon better with every release. Your support means the world to us! If you've enjoyed Carbon, please consider a donation toward this goal. Thank you, and we hope you continue to enjoy Carbon!
​

BUGS​
Some (not all) seem to experience issues with GPS. If you have issues with GPS, please RSD the JB image and then flash Carbon. GPS should work now. (I've also heard you can just restore a stock backup, get a lock, then flash Carbon again...)
Haptic feedback on soft keyboard is not provided when enabled (which it is by default)
While capturing a picture to send via MMS, ensure HDR is deselected - Gallery will cause a force close if HDR is enabled!! (Note - HDR works for normal still photos, just not MMS.)
Update Google Search (manual update), or else any voice searches will fail with FC. Update the app, and it is resolved.
Caps lock LED doesn't seem to work properly...
Camera button doesn't work? Cam/camcorder works fine, but the physical camera button does not seem to function (in Carbon).

Reserved

Also reserved

1st to try it out. Slide out keyboard light does not work.

Great! Now we as CDMA user have much ROM options to choose. Carbon seems a big hit nowadays along with Paranoid with its Halo features. Thanks a lot for the port.

gtownswagga said:
1st to try it out. Slide out keyboard light does not work.
Click to expand...
Click to collapse
Ah, I did not notice that. Should be easy to fix, it's probably a liblights issue... as I cannot adjust the brightness either
Edit - fixed the brightness issues, and added back the multipress options... but I am still missing the keyboard backlight! I will keep working at it, and keep this thread updated.
Edit 2 - welp, looks like there are some frameworks/base hacks required. I will upload the build I am running now, everything with liblights is fixed (brightness of the display, notification LED) are fixed but keyboard backlight is not. Working on fixing that now.

Figured I would post again - as liblights should be completely fixed now folks .
I probably need to test MMS again, I'm trying to think of what else I could have missed... let me know what you find broken guys! I'm also curious if this works on the GSM hacked variants, or if I have to run another build for that group.
Edit - just tested outbound MMS (which is all I can test), it seemed fine.

First off great job. I love this rom. One question. Will your kernel work with this rom? I tried flashing and it greyed out my WiFi. I had to wipe and reflash the rom.
Sent from my Motorola Photon Q LTE using Tapatalk 2

dwaynet89 said:
First off great job. I love this rom. One question. Will your kernel work with this rom? I tried flashing and it greyed out my WiFi. I had to wipe and reflash the rom.
Sent from my Motorola Photon Q LTE using Tapatalk 2
Click to expand...
Click to collapse
Now don't quote me on this, but isn't that kernel for 4.0.4?

dwaynet89 said:
First off great job. I love this rom. One question. Will your kernel work with this rom? I tried flashing and it greyed out my WiFi. I had to wipe and reflash the rom.
Sent from my Motorola Photon Q LTE using Tapatalk 2
Click to expand...
Click to collapse
dpwhitty11 said:
Now don't quote me on this, but isn't that kernel for 4.0.4?
Click to expand...
Click to collapse
Well, I have a few kernels. There's one I released for CM, and my kernels that have their own thread (which are for stock).
Unfortunately I will probably have to release a separate kernel for this, as any time the kernel modules change, wifi will be broken if you don't keep up with it (this is why your wifi is broken dwaynet89.)
I assume you were using the CM kernel? That would be the only one having a chance at working. I can whip up another one for this build too if needed

arrrghhh said:
Well, I have a few kernels. There's one I released for CM, and my kernels that have their own thread (which are for stock).
Unfortunately I will probably have to release a separate kernel for this, as any time the kernel modules change, wifi will be broken if you don't keep up with it (this is why your wifi is broken dwaynet89.)
I assume you were using the CM kernel? That would be the only one having a chance at working. I can whip up another one for this build too if needed
Click to expand...
Click to collapse
I'm sorry for not making that clear but yeah I was talking about the cm kernel. If you don't mind I would love one of your kernels for this rom.
Sent from my Motorola Photon Q LTE using Tapatalk 2

Installed and running nicely. Can confirm also that face unlock through the normal system settings does not work and force closes. Might it be related to the camcorder video issues? Doesn't impact me a whole lot as one of my wifi network requires secure credentials and won't allow any security less than a pin. Will look for other bugs but looks really solid to begin with. Thanks for all your work!
Sent from my XT897

This ROM seems really cool and i like most of it so far. FYI starting from stock and letting GPS lock before installing the ROM works here too. No problems with GPS for me. One thing i am missing and maybe its just me but is there a menu for changing launcher settings in this one like there is in CM? I always remove the google search bar and increase the grid size. Short term fix for me was i backed up trebuchet with all of the settings like i like it in CM 10.1 and restored it in carbon. Thanks for the work on this and if you need help with testing stuff i'll be glad to help.

Mordannon said:
This ROM seems really cool and i like most of it so far. FYI starting from stock and letting GPS lock before installing the ROM works here too. No problems with GPS for me. One thing i am missing and maybe its just me but is there a menu for changing launcher settings in this one like there is in CM? I always remove the google search bar and increase the grid size. Short term fix for me was i backed up trebuchet with all of the settings like i like it in CM 10.1 and restored it in carbon. Thanks for the work on this and if you need help with testing stuff i'll be glad to help.
Click to expand...
Click to collapse
There's a TON of settings. Check the 'Carbon Rom' menu.

disconnecting wifi
Hi first off amazing job on this rom arrrghh. The only issue I'm having with this rom is when connected to my WiFi it will just randomly disconnect and go back to my lte service. And to re-enable it I have to go to settings>WiFi>and connect to my WiFi again. Not a big deal for me, just wanted to let u know this issue occurs. Also the issue I had with the supersu on the cm10.1 rom isn't happening on this rom. And I did clean fresh install no dirty flashing. But other than that problem everything works amazing. Keep up the good work ur the best.

sk8rguy05 said:
Hi first off amazing job on this rom arrrghh. The only issue I'm having with this rom is when connected to my WiFi it will just randomly disconnect and go back to my lte service. And to re-enable it I have to go to settings>WiFi>and connect to my WiFi again. Not a big deal for me, just wanted to let u know this issue occurs. Also the issue I had with the supersu on the cm10.1 rom isn't happening on this rom. And I did clean fresh install no dirty flashing. But other than that problem everything works amazing. Keep up the good work ur the best.
Click to expand...
Click to collapse
Hm, now I've heard on stock people having issues with wifi turning on & off.... but I don't think they had to actually re-enable it in settings.
So you say the wifi is not only disconnecting, but it is being disabled as well? IE when you go into settings, wifi is set to 'off' and you have to flip it back 'on'? Or are you just cycling it off/on in order to get it working again...

One bug that I am noticing with the latest build is in portrait mode the bottom corners of the screen do not respond to touches. In the screenshots below it shows me touching the search option in the phone app, the #'s button on the keyboard to change to using #'s and the save in the lockscreen shortcut options. I had to hit these repeatedly to get the screenshots and they still were not responding to touches.
I never dirty flash and I tried rebooting and also wiping and reflashing but dosen't resolve the inssue.
Sent from my Motorola Photon Q LTE using Tapatalk 2

dwaynet89 said:
One bug that I am noticing with the latest build is in portrait mode the bottom corners of the screen do not respond to touches. In the screenshots below it shows me touching the search option in the phone app, the #'s button on the keyboard to change to using #'s and the save in the lockscreen shortcut options. I had to hit these repeatedly to get the screenshots and they still were not responding to touches.
Click to expand...
Click to collapse
Hm, I don't think I noticed this. I'll check it out, thanks.

arrrghhh said:
Hm, I don't think I noticed this. I'll check it out, thanks.
Click to expand...
Click to collapse
It may be a hardware issue (hopefully not) I just flashed previous build before the bug and now I'm having the same issue. I'm going to restore a backup of cm 10.1 and see if its there also.
Sent from my Motorola Photon Q LTE using Tapatalk 2

[ROM][Unofficial]Firefox OS 2.0 Pre-Release for Kindle FIre HD 7[5/22 Alpha]

*** USE AT YOUR OWN RISK! I AM NOT RESPONSIBLE IF THIS SOFTWARE OR SOMETHING ELSE SUDDENLY FRIES YOUR DEVICE. ***
Firefox OS
Download Info:
Latest Build: [2014-05-22] Alpha 2.0 Pre-Release
Links:
Dev-Host: Download
Md5sum: 1b9e59c7af3ef6f481f736c207dce1df
Older Builds:
[2014-05-20]
Links:
Dev-Host: Download
Md5sum: cf1cabaa21cd4b3767449bc7300666b0
[2014-03-12]
Links:
Dev-Host: http://d-h.st/1qH
Md5sum: 8799eafb470354ad0ecc717f0fb3ad88
[2014-02-36]
Links:
Dev-Host: http://d-h.st/gkB
Md5sum: 8c1635cf11375db632b0f5f3f4897737
Ok i have been working on this for a few months and finally got around to uploading my latest build and decided to make this public. This is Firefox OS ported to Kindle Fire HD 7". It is still quite buggy but I believe alpha status sounds about right at this point. Here's some info about this OS in case people want to know the technicalities. This OS is based on AOSP 4.3 using hashcodes cm 10.2 device tree with some modifications. While it is based on AOSP Android, this OS is only based on it in the sense its core is based on android, it has no dalvik virtual machine so don't even bother flashing a gapps package with it, it wouldn't even recognize it inside the OS.
I have to give a big thanks out to Hashcode, for putting up with all my questions in the irc about building rom's considering i'm totally new to compiling an android os, much less troubleshooting the technical things. Also have to give a big thanks to the Mozilla dev's in their irc because they helped me quite a bit in figuring out how to get past the main bug i was having(especially gerard-majax). For those of you who weren't in the testing you would'nt know but the original builds of this would boot up to the firefox boot animation, flash a white screen and then blank. Managed to work around this rather than fix it for now thanks to them, along with answering alot of my questions that are more inside Firefox OS's realm rather than android's. Now that i mentioned that i have to thank all my tester that helped me get this project off the ground by testing the rom out and reporting any bugs, along with just reporting if the latest build worked. These people include but not be limited to: Jserrano56, LinearEquation, Ph0enix_216, r3pwn, viktormax3, trinaldi, south956, and Latonya1. If i left anyone out i'm sorry, i grabbed everyone's names from my sent items rather than browsing the entire thread where everyone volunteered. I will add screenshots as soon as i can.Screenshots added! Sorry for there not being any lockscreen pics, i can't take them because the shortcut for screenshot in Firefox OS is power + home button, and there are no softkeys in the lockscreen for homebutton...
Screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now let me list some bugs it has that are currently being worked on to the best of my limited capabilities:
[Pre-2/26]
Battery Gauge doesn't work - Fixed sorta (see new bug below that was caused by fixing this)
[2/26]
Gralloc is disabled because of bug with sgx gpu's so theres some laggyish graphics < Fixed [2014-03-12] (thank you mozilla devs for patching this!)
"Insert SIM Card" message is displayed on drop down menu and lockscreen < I'm looking into this, all i know is i need to figure out how to disable RIL
Camera is broken - now compiles sucessfully but still doesn't work (mediaserv crashes and burns)
Video Playback wont even initiate < still not sure about this problem, trying to look into it- Fixed [2014-05-20]
Issue where device tends to not want to come out of sleep mode unless plugged into charger < Looking into - Fixed [2014-05-20]
Bluetooth isn't working yet - Fixed [2014-05-22]
Miscellaneous GUI glitches < These are more than likely mainstream since version 1.3 was being stabilized until recently.
Charging Loop on lockscreen when charged by usb low power < still looking into this
sdcard is a bit glitchy
mtp isn't working (adb works fine though)
usb connection restarts every so often < probably related to why mtp isn't working
small boot animation < not sure if i should stretch this or fill in the background with blue or see if mozilla devs have a higher res version somewhere
Note that like i mentioned in the bugs, this is based on a 1.4 Pre-Release, which isn't exactly the most stable branch. If you are wondering why i used an unstable branch the answer is simple, 1.3 is based on ICS sources, and i didn't have an ICS device tree to work with. At this point i guess you could say this OS is comparable in a sense to Ubuntu Mobile OS, simply because android is more popular, but as i like odd things i decided to go for it with this ROM, so I will say this, if all you use your Kindle for is email, browsing the web and listening to music, then this ROM would be good for that, it was designed to be Completely html driven. It should run smoother than it does now in the coming updates.
So without further ado let me post some instructions for flashing this ROM:
***Notice*** Please make sure you have at least twrp 2.6.3.1 installed or you may encounter problems.
Download the ROM above and place on sdcard
Boot into twrp
Do a factory reset
Hit Install
Choose the ROM
Reboot
Profit!
Notice: I am looking for developers that would like to help me with this project as i don't know any C++ or C coding, so the bugs i can fix are limited to what i can find that is simple or simple enough in C++ that i can change a string here or there. So please if you aren't busy or are interested i would love some help fixing things.
Now for any developers that are interested here is a small tutorial on how to download and compile this because the process is slightly different than the android setup by a little:
First off i suggest reading the setting up the build environment herethat Mozilla made, but keep in mind some things when following their instructions, their build instructions were designed around the stable 1.3 branch which I'm not using, so certain things like the compiler versions they list are incorrect so for what they call for using as gcc and g++, install the 4.7 version. Another thing they don't mention because i stray from their path is you will in fact need Java, so make sure that's installed. i included a preset .userconfig to specify the correct version of gcc and g++ to be used, if its in a unusual path or something look in the .userconfig file to change it(its in the root folder of the build environment). I also advise setting the ccache higher than they put it at, it usually works at what they set it to but recently i couldn't get it to build until i set it to 5GB. One last thing i haven't automated yet is because this was a non Java using OS the signapk.jar file doesn't get auto-copied to the folder it needs to be in when the otapackage is made so if you ever make clobber or its your initial build remember to
Code:
cp tool/update-tools/bin/signapk.jar out/host/linux-x86/framework/signapk.jar
Ok that paragraph appears to be a bit of a mess but i think i put the core info for setting up a build environment in there. Next how to download and set everything up. First off goto the folder you want to set this up in(for me it was my home folder) and run
Code:
git clone https://github.com/stunts513/B2G.git
once that is done run this:
Code:
./config.sh tate
Now go do something for a few hours because its going to download a lot of data.
Now that it is done downloading there is something important you need to do or it will complain about missing dependencies, go into the frameworks/base/graphics/jni folder and rename Android.mk to Android.mk.disabled or just delete it. I suggest if you want to put this in another name other than your login name on Linux to "export USER=blah". Ok now things get different but simple, run this
Code:
./build.sh -jX
where X is the number of physical + logical cores your pc has. Once the build process finishes run
Code:
./build.sh otapackage
Once that is done you would think "yay my build is complete", but no it never could be that simple, lemme explain the next steps to do until someone helps me recode some python scripts.
Now that we have a signed apk we need to add some things to it to get it finished because the python scripts need some editing i don't know how to do. Go into the out/target/product/tate folder and open the zip file it created up, add the data folder into it. Now open the META-INF/com/google/android/updater-script and find this line
Code:
mount("ext4", "EMMC", "/dev/block/platform/omap/omap_hsmmc.1/by-name/system", "/system");
package_extract_dir("system", "/system");
right after it add these lines:
Code:
mount("ext4", "EMMC", "/dev/block/platform/omap/omap_hsmmc.1/by-name/userdata", "/data");
package_extract_dir("data", "/data");
and don't forget at the end to add the
Code:
unmount("/data");
before the
Code:
unmount("/system");
Now that that is over with grab the last command you see outputted in the terminal about running java -jar signapk.jar and modify it so it doesn't have the /tmp directory as the input file, and make the output filename whatever you wish. Tada theres a successful build for ya. if you want to look at it i have this info on my github wiki for b2g in case i either left something out or had extra info on there.
XDA:DevDB Information
Firefox OS, ROM for the Amazon 7" Kindle Fire HD
Contributors
stunts513
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.0.x
ROM Firmware Required: 2nd bootloader and twrp 2.6.3.1 or higher
Based On: AOSP and a CM device tree
Version Information
Status: Alpha
Created 2014-02-27
Last Updated 2014-05-27

Nice work stunts!!
Sent from my Nexus 4 using Tapatalk

Thanks! Hopefully this will attract some dev's and some people might get interested in this os. I find this is very interesting in the sense that all the apps are literally coded in JavaScript and html5, so practically anyone could learn simple languages and make apps, I already have been learning a bit of JavaScript myself so I can understand what's going on in Gaia a bit better (Gaia is what the ui is called for those not informed). Learning JavaScript is kinda interesting because its the first object oriented language I've learned I believe. Anyways things I'm going to need a dev's help with more than likely are the camera, the Bluetooth, and the video playback issue. I have some leads with video playback but haven't had very much luck with figuring it out. Anyways I hope to see more people posting in and their thoughts plus any bugs they found/I forgot to mention. By the way I recommend trying the games out, they run quite smoothly considering I have gralloc disabled, I was surprised that games like solitaire actually had dragging and such, I'm kinda new to html5 so it actually surprised me.
Sent from my Amazon Kindle Fire HD using Tapatalk

Great job, stunts. I'm definitely gonna give this one another go.
Sent from my iPod touch using Tapatalk

upload pics please ! great work !

Thanks, BTW I did upload pics, because this is a devdb thread it has a screenshots button up at the top so I didn't think I really needed to put pics in the main post but I guess I can because they aren't exactly in your race the way it is. I'll link them into the post when I get on my PC.
Sent from my Amazon Kindle Fire HD using Tapatalk
Edit: ok i put linked the screenshots that were there already so they show up on the main post, if you think i put too many or they are too big or somethign please feel free to tell me so.

This is just AWESOME!! Thank you for this
Sent from my LG-E430 using XDA Premium 4 mobile app

stunts513 said:
Thanks, BTW I did upload pics, because this is a devdb thread it has a screenshots button up at the top so I didn't think I really needed to put pics in the main post but I guess I can because they aren't exactly in your race the way it is. I'll link them into the post when I get on my PC.
Sent from my Amazon Kindle Fire HD using Tapatalk
Edit: ok i put linked the screenshots that were there already so they show up on the main post, if you think i put too many or they are too big or somethign please feel free to tell me so.
Click to expand...
Click to collapse
exellent work. keep like this !

Thanks for the support! I have been looking into disabling ril so that annoying insert sim message will go away, I kinda made some progress on it but its kinda half and half progress, I'm twiddling around with gaia's innards, and someone mentioned there's a way to build Gaia that's meant for a tablet so I tried it, here's the upside so far about it, it took the annoying sim message away, and has a slightly different layout with only 2 pages on home screen and I think the search box was disabled. This is the downside, it took away the games collections and such, the icon for insert sim is still on the status bar and the lock screen still says no sim. Even worse than that was the fact I believe the only way I can put it into practical flashing use is to make a production build rather than a user debug build, in order for me to even test it I had to wipe data, and then run a make file that pushed the needed files via adb. Even weirder to me is I found out as it is right now I was thinking I need to edit hashcode's python scripts for building the otapackage to include /data to be auto included in the packaging process, and after seeing how a production build is made I see why it's unnecessary, a production build actually puts them on the system partition. Might still add a command line option to the scripts for if its a user debug build to do so. Sorry if this seems like confusing ramblings, I find it fun talking about technical things.
Sent from my Amazon Kindle Fire HD using Tapatalk

Haha stunts, the beauty of having your own rom thread is you can ramble all you want! Thanks for your efforts, I'll be checking it out!
Sent from my MB865 using xda app-developers app

Looks promising. Be keeping an eye one this. Once it turns beta I'll give it a try. Keep up the good work.
I checked this out I really like it. Hope you keep up with this.
Sent from my Kindle Fire HD 7 using XDA Premium 4 mobile app

Update!
Ok, here's an update, have a major bugged fixed in this release as well as minor graphical bugs.
Update: [2014-03-12] Alpha 1.4 Pre-Release
Links:
Dev-Host: Download
Md5sum: 8799eafb470354ad0ecc717f0fb3ad88
Whats fixed in this update:
-gralloc works now (thank you mozilla devs for fixing this)
-misc gaia(the homescreen/gui) fixes.
What these fixes mean:
With gralloc functioning now, the graphics are much much less laggy, and i can also start troubleshooting the video playback issues a bit more than previously. You will now notice a nice artifacting loading logo on videos in youtube, and on games like safecracker it will be a nice big fullscreen artifact on the screen while sound is playing.
Gaia misc fixes from upstream, they are nice little things that needed fixing that now work correctly, like that little bar of bleed through from the homescreen on certain apps and games is gone, things like that. I will update my screenshot now so that actually looks nicer.
Thanks to this update some things were brought out that i now can start throwing some guesses around as to whats up with video playback and the games and such that are artifacting. It probably has to do something with a buffer, but i have said this before i need a dev that will help patch this kinda stuff, i have no clue how to myself. All i know is most of the problems i'm having with video playback issues and artifacting and such are probably caused by the fact Mozilla has their own custom framework/av folder, which in turn i believe has its own custom libstagefright, this also i think had something to do with why i couldn't get the camera's hal module to compile. So if any dev is willing to take a look at this please help me.

Finally had a good time to test this out (if you call Argumentative Writing class a good time). Flashed well, booted without a hitch, and the setup wizard or whatever it's called went smooth. I've gotta say, nice job Other than the bugs you've already addressed, my only complaint was that the music app went into a scrolling loop when in the album art view, then crashed.
@stunts513, be proud of yourself - this is quite the accomplishment I only wish I could do something as awesome as this.

Thanks, I'm thinking about trying to build it for the other devices as well sometime this week to test it out and commit any tweaks I may need to make to compile for those devices. I've been doing other things lately so I haven't been booted into Linux much this week and my debugging hit a bit of a standstill, I'll try debugging it again soon and see if I can fix anything else.
Sent from my Amazon Kindle Fire HD using Tapatalk

Bump?
For your own custom Sig : http://forum.xda-developers.com/showthread.php?t=1922304

Can't wait till this reaches its beta stages. Would definitely use it!
Sent from my Amazon Tate running CyanogenMod 11

Same here, I enjoyed watching it but the YouTube no video was the killer for me, does hulu work on it by any chance even thru chrome cast
For your own custom Sig : http://forum.xda-developers.com/showthread.php?t=1922304

Funny it would get bumped today. I've been upgrading to a cm 11 device tree kitkat based build for about 4 or 5 days. Been having to debug a error for the past few days that was driving me nuts and I finally got passed it. Even more surprising is the fact I didn't have to disable the camera and I think it compiled its module successfully. I just finished a build a while ago and plan on testing it tomorrow once I make a nandroid backup. My main issue is as it turns out from multiple devs telling me(hashcode and gerard-majax) I added some unneeded stuff to the manifest back in the jb builds. Apparently just because the compilation process requests it and errors out without it doesn't mean its required(this really surprised me). Long story short some llvm and clang related stuff was being compiled thanks to some librs related stuff and erroring out for some reason and it turns out I had to kill it at the source. Let's hope my build works, I'll try to post the results depending on if I go shopping for parts for my microwave or not.
Edit: oh and as to the video, I have not heard of b2g having chromecast. I don't know if they would support it or not considering its based on googles work but forked in a different direction. And no as of that last build no video was working. I think it was something with ducatti not working right so none of the video would even decode and there was some kinda buffer error with I think open on related animations so even of the decoder worked I think it would a been artifacting like the YouTube play button and such. Hopefully the cm 11 builds will work better. I still don't have a dev to help me with this so progress is kinda slow seeing as I don't know c++ I can't do too much. I'm just glad all the devs have put up with my questions up until now as I know how annoying I can get. It's not often I find tech savy people that know more than me about PC's as i come from a small town so I tend to have a million questions when I find someone smarter than me.
Sent from my Amazon Tate using Tapatalk

UPDATE!
Download Info:
Latest Build: [2014-05-20] Alpha 1.4 Pre-Release
Links:
Dev-Host: Download
Md5sum: cf1cabaa21cd4b3767449bc7300666b0
Update info:
-updated to a kitkat build with the cm 11 device tree
Fixes:
-Fixed video playback - (actually hashcode did, i just pulled in changes from his repo and it worked)
-Camera doesn't work but the module is compiling now so camera *may* work soon, don't hold me to it.
On another note, i noticed while atleast video playback is working not all video files are openable, but i haven't tried much outside of a random file left over from a android game that it found so i don't know the extent of what can and can't be played. The file i played had audio and no video.
Oh and something important you need to do when you first boot into it, enable soft home from settings>developer options, for some reason the previous method i used involving a build.prop property didn't work this time around. Kinda annoying...
Todo:
- In the next few days i'm going to sync up my sources with hashcodes again becasue he said he's got some camera fixes he's working on that might help.
- See if the hwc will build and load on cm11 builds as it may fix the artifacting on certain games

Nice will try asap, today's too late and I just saw......imma download though
For your own custom Sig : http://forum.xda-developers.com/showthread.php?t=1922304

[ROM][4.4.X][HISTORY][HUMMINGBIRD|OVATION] MoKee OpenSource Project

Disclaimer:
Code:
All the firmwares, custom ROMs, official firmware updates, mods and tools mentioned here belong to their respective developers/owners.
You will be doing everything at your own risk.
We nor the developers cannot be held responsible if you end up damaging or bricking your device.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Introduction:
MoKee OpenSource is based on the Google AOSP. We update our source code frequently to keep up with the latest development, and not forgetting to merge in special features of our own at the same time.
A small group of people from around the world who are interested in Android launched this project on the 12th of December 2012, and is committed to make this ROM better and better. Like most contributors of open source projects (Omni, CyanogenMod, Slim AOSPA etc), we are doing all these in our free time as our passion...
Since this project is open source, anyone interested can participate in the development (maintain new devices, contribute code etc). Newcomers are always welcomed!
Read here for developer application; with this, you can host your unofficial MoKee builds on our server!
Features:
Odexed for faster performance (only in official releases, nightlies are deodexed)
Incremental updates
OTA updates - update on the fly!
Native exFAT support (Samsung devices only)
ListView animations
Multi window
Calendar - with lunar and solar calenders
Lunar calendar in lock screen
Task switching sidebar in recent apps (the list will increase if you install supported apps)
Bulk SMS recipients
Adjustable SMS font size
SMS sending delay
Smart dialing
Speed dialing
IP dialing
Custom carrier name
Network speed in status bar (upload and download!)
Built in timer in Apollo - determine when to stop playing music
MoKee Setup Wizard
Active Display
Adjustable navigation bar height
Unique Power Saver functions!
Custom screen off animations
** Not yet merged
PIE control
Auto hide status bar
Smart capture
Many more! Since we are constantly adding new features, see changelogs to keep updated!
Screenshots
The screenshots below gets outdated very fast!
Multi-window:
Screen Off Animations:
Scale down:
Fade out:
Unique features:
Feature-rich settings:
Links:
Official Site:
http://www.mokeedev.com/en
Google Plus Community (join us for faster response!):
https://plus.google.com/communities/112433388317801966872
Statistics:
http://stats.mokeedev.com
Nightly Build Status:
http://build.mokeedev.com
Bug Tracker:
http://issues.mokeedev.com
Changelog:
http://changelog.mokeedev.com
GitHub:
http://github.com/MoKee
Kernel Sources:
https://github.com/MoKee/android_kernel_bn_omap
Code Review:
http://review.mfunz.com
Final Release:
http://rom.mk/?device=hummingbird&type=history
http://rom.mk/?device=ovation&type=history
MoKee Gapps (full list):
http://www.androidfilehost.com/?w=files&flid=11492​
Installation Instructions:
1. Wipe data/factory reset
2. Format /system
3. Flash ROM
4. Flash MoKee Gapps
5. Reboot​
Donations:
All donations will be used for bandwidth, you can see the current bandwidth usage here:
http://traffic.mokeedev.com
Current rate is 6TB per/month, extra at USD0.02/GB
So yea, show some "MoKee lurve" here:
http://www.mokeedev.com/en/donations
Credits:
- MoKee Developers: https://github.com/orgs/MoKee/members
- CyanogenMod
- AOSP
- Koush for open-sourced SuperUser
- Slim Roms
- OmniROM
- @omkarsathe92 for the videos! ​
XDA:DevDB Information
MoKee OpenSource Project, ROM for the Barnes & Noble Nook HD, HD
Contributors
martincz, Ryuinferno
Source Code: https://github.com/MoKee
ROM OS Version: 4.4.x KitKat
Version Information
Status: Stable
Created 2014-05-24
Last Updated 2015-07-29

set_metadata_recursive: some changes failed
status 7 error
looks like I can't install it, 140531 Release.

What recovery should be used?
Thanks

antebr said:
What recovery should be used?
Thanks
Click to expand...
Click to collapse
Use the one from CM11 thread.
Thanks for the wonderful ROM
Cool boot animation :good:
Flashed the latest nightly. Booted up fine. But for some reason the keyboard wouldnt show up while registering the tablet. Probably fault with Gapps package? I dont know. So I skipped tablet registeration. Navigation bar was disabled, so I enabled it through settings (Buttons>enable on-screen nav bar). Pretty much like CM but has special features like Active Display, Short Cut bar ( which shows up in recent apps), list view animation, Split view. We can also "lock apps" in the recents menu which prevents it from being cleared away.
But got " Unfortunately, Google Keyboard has stopped" error all the time and I couldnt type anything.
IMO this would get more users if this was posted in the "Android Development" forum.
EDIT: Hmm it seema the problem is gapps package in GENERAL. Weird. Tried both PA gapps and the one from cyanogenmod site. Both cases force closes and keyboard unable to open. Went on and did a fresh install without any gapps package and had no crashes and the keyboard worked as well. But for me its pretty useless without Play Store.

adwait.bhandari said:
Use the one from CM11 thread.
Thanks for the wonderful ROM
Cool boot animation :good:
Flashed the latest nightly. Booted up fine. But for some reason the keyboard wouldnt show up while registering the tablet. Probably fault with Gapps package? I dont know. So I skipped tablet registeration. Navigation bar was disabled, so I enabled it through settings (Buttons>enable on-screen nav bar). Pretty much like CM but has special features like Active Display, Short Cut bar ( which shows up in recent apps), list view animation, Split view. We can also "lock apps" in the recents menu which prevents it from being cleared away.
But got " Unfortunately, Google Keyboard has stopped" error all the time and I couldnt type anything.
IMO this would get more users if this was posted in the "Android Development" forum.
Click to expand...
Click to collapse
Just a heads up; you can change your boot logo using the rom toolbox app.

@martincz
Thanks for building Mokee for the Nook HD/HD+!
I haven't had the chance to check everything but so far it looks pretty nice. However, I have Ovation and the build has an incorrect storage_list.xml in framework-res.apk. It appears to be a generic storage_list and not for our devices.
I flashed the latest nightly but upon checking the release build, it also has the same incorrect storage list. Of course with this incorrect file, storage in settings does not read sdcard1 and a file manager is unable to find it as well. Additionally, when connected to a PC the device just comes up blank. I just took a look at the Hummingbird build and it also has the incorrect storage_list.xml.
I've attached a file below containing the correct storage_list.xml for our devices.
https://www.dropbox.com/s/dq0ayclmfvndbk0/storage.zip
Btw, I flashed the latest Mokee gapps listed in the OP and had no problem with the keyboard came right up and away I went.
Thanks again and I'm hoping you can get this squared away. Also, as mentioned in an above post, I think this would get more exposure in the "regular" Android development. This "original" forum has always been kind of a dead area in the Nook forum.
Mike T

webdroidmt said:
@martincz
Thanks for building Mokee for the Nook HD/HD+!
I haven't had the chance to check everything but so far it looks pretty nice. However, I have Ovation and the build has an incorrect storage_list.xml in framework-res.apk. It appears to be a generic storage_list and not for our devices.
I flashed the latest nightly but upon checking the release build, it also has the same incorrect storage list. Of course with this incorrect file, storage in settings does not read sdcard1 and a file manager is unable to find it as well. Additionally, when connected to a PC the device just comes up blank. I just took a look at the Hummingbird build and it also has the incorrect storage_list.xml.
I've attached a file below containing the correct storage_list.xml for our devices.
https://www.dropbox.com/s/dq0ayclmfvndbk0/storage.zip
Btw, I flashed the latest Mokee gapps listed in the OP and had no problem with the keyboard came right up and away I went.
Thanks again and I'm hoping you can get this squared away. Also, as mentioned in an above post, I think this would get more exposure in the "regular" Android development. This "original" forum has always been kind of a dead area in the Nook forum.
Mike T
Click to expand...
Click to collapse
Ow snap! That's what the problem was . I should have read the OP more carefully regarding the GAPPS. I had totally freaked out when I saw that the storage was not accessible. I thought it was only with mine.

Excited to see this. Once pie control is ready I'm all over this.
Sent from my Nexus 5

adwait.bhandari said:
Ow snap! That's what the problem was . I should have read the OP more carefully regarding the GAPPS. I had totally freaked out when I saw that the storage was not accessible. I thought it was only with mine.
Click to expand...
Click to collapse
Same thing happened to me yesterday lol. Flashed this rom and then wondered why I couldn't download anything. I freaked out and flashed back to CM.
Sent from my SPH-L710 using Tapatalk

Where does one put the new strafed file?
Sent from my PC36100 using xda app-developers app

jpisini said:
Where does one put the new strafed file?
Sent from my PC36100 using xda app-developers app
Click to expand...
Click to collapse
Don't know if "strafed" is just a typo, or you are talking about the correct storage_list.xml file I referenced above??? If you are talking about the storage_list file, it pretty much has to be compiled in the build. I just attached that file so that the dev could see the difference between his framework compiled in the build and the correct one.
It is contained in the framework-res.apk in /system/framework of the rom. If someone has experience with apktool, (requires java) it can also most likely be edited. Unfortunately, with my limited experience I tried and could not get it to work.
Btw, downloaded the latest nightly and it still has not been corrected. From the looks of it, the dev hasn't been active on XDA since he posted this here. He may end up being another in a long string of disappearing devs in the Nook HD forum.
Mike T

OK thanks my phone changed storage to strafed and I didn't notice.
Sent from my PC36100 using xda app-developers app

I tried the latest stable build this morning it still can't see the sdcard.
-------------
Tried inserting the file in before flashing no luck same errors.Unfortunately not my area. I have tried building from source and just can't seem to get it straight.

It's already fixed, try the next RELEASE version, or go for the nightlies

Will do so sometime this week thanks. It does look pretty cool the little bit I did play with it.
Sent from my SPH-L900 using XDA Free mobile app

New version is much nicer and it does see the sdcards. No FCs yet either. So far I am enjoying it.

Never mind had to format my nook as it overheated just playing with settings. Shame I really like the look and feel.
Sent from my SPH-L900 using XDA Free mobile app

Running the latest mokee on my HD+. Very nice experience. Android version is 4.4.4. It does overheat a bit.

I'd just like to say thank you to the Mokee team.
I've been on Cyanogenmod nightly's for ages but switching to this (01\09\14 nightly) has invigorated my tablet.....So much quicker and fluid than before....
Might even give it a spin on my Oneplus One ?
Thanks again.
Sent from my BN NookHD+ using XDA Free mobile app

Is overheating still an issue? I'd love to give this a try but as everything "works" on my current ROM (albeit slowly) I'm a bit hesitant to try this, overheating is important to me since I read a lot on my tablet.