Develop Bugs

[ROM] CyanogenMod 9 | MoltenMotherBoard

FEEL FREE TO DONATE US FOR ALL WE'RE DOING FOR YOU!
For general discussions, bug reports and FAQ, write HERE!​
Credits:
Jellaxy Team (in particular erikcas for CM9 / ICS sources and support)
MoltenMotherBoard team!
Downloads:
MoltenMotherBoard mirror | AndroidFileHost
Full sources:
MoltenMotherBoard sources: MoltenMotherBoard | Github
Changelog:
Nightlies
Code updates
20140927
Huge sources cleanup
Code updates from AOSP, CyanogenMod
20130722
Code updates from AOSP, CyanogenMod
20130627
New framework
Changes in Settings app
Removed MovieEditor
Various optimizations
Code updates from AOSP, CyanogenMod
20130618
Excluded Bluetooth Tether in Settings app (feature not properly working on GIO, hardware-level cause)
Excluded WiFi Direct in Settings app (feature not properly working on GIO, hardware-level cause)
Excluded CM Updates in Settings app (feature not needed and forcing closes)
USB and Wifi tethering fixed
Gapps updated to 2013.06.14
Fixed Bluetooth issues (it didn't receive files, beacuse of missing prebuilt configurations files)
Improved S2E usage
Improved Camera effects
Included MMB banner
Hacked hosts file (no more Ads)
ADB icon hided
Fixed AudioFilter.csv (it made some audio lags)
Code updates from AOSP, CyanogenMod
20130610
First release
Issues:
-----
Do you want to report an issue? Do it here!
In order to do it, create a new issue, choosing correct labels corrisponding to: Device/OS which you're using, ROM/project you're on, kind of issue.
Also, please, be sure you're running the ROM/project in the exact way we've provided it to you (do not create issues if you're using different
kernel, mod, plugins and dependencies we didn't tell to use).
General Questions: MoltenMotherBoard Projects | General Questions and Info
Official Mantainer(s): Mackief, ItachiSama, p4c0

CyanogenMod
What is CyanogenMod?
CyanogenMod is an open source replacement firmware for smart phones and tablet computers based on the Android mobile operating system. It is developed as free and open source software based on the official releases of Android by Google, with added original and third-party code.
It offers features and options not found in the official firmware distributed by mobile device vendors. Features supported by CyanogenMod include native theming support, FLAC audio codec support, a large Access Point Name list, an OpenVPN client, revoking application permissions, support for Wi-Fi, Bluetooth, and USB tethering, CPU overclocking and other performance enhancements, soft buttons and other "tablet tweaks", toggles in the notification pull-down (such as Wi-Fi, Bluetooth and GPS), app permissions management, as well as other interface enhancements. According to its developers, CyanogenMod does not contain spyware or bloatware. CyanogenMod is also stated to increase performance and reliability compared with official firmware releases.
Although only a subset of total CyanogenMod users elect to report their use of the firmware, as of 30 May 2013, CyanogenMod has recorded over 5.1 million active installs on a multitude of devices.

Looking forward to see Firefox OS on our precious Gio Good Luck!

Good luck macief

mackief said:
Hi guys! Me and my team are working hard to port B2G on our Gio. At the moment we're on holiday, so in these days we'll try to fix lot of things, but we cant upload the package. We'll do it on Saturday, when we'll in Rome again!
Team:
- mackief
- p4c0
Thanks:
- Lemmymet
- MaclawStudios
Click to expand...
Click to collapse
You mean today? Cause today is Saturday

bgm92 said:
You mean today? Cause today is Saturday
Click to expand...
Click to collapse
sunday

Nope guys.. Saturday, the next...
Sorry, you've to wait a week!

Isnt this againts the rules ? Coming soon threads
Sent from my GT-S5830 using xda premium

CoolCatGetHome said:
Isnt this againts the rules ? Coming soon threads
Sent from my GT-S5830 using xda premium
Click to expand...
Click to collapse
not if they are good enough to develop, like cm9 and jelly bean threads were, as moderator told me

not if they are good enough to develop, like cm9 and jelly bean threads were, as moderator told me
Click to expand...
Click to collapse
erm.. When are threads 'good enough to develop' and how can you know that before anything is released?

MerynGoesAndroid said:
erm.. When are threads 'good enough to develop' and how can you know that before anything is released?
Click to expand...
Click to collapse
Threads with AOSP and latest android version roms or simular like other OS ports
Example
-cm9
-cm7
-any jellybean related
- AOSP
-more
Just not the roms were somebody adds a few apks and removes some and gives it a theme but makes a thread without a download link
Sent from my GT-S5660 using xda premium

Just got a build with working RIL, things not working:
-Camera
-video playback
Maybe some more things, used parts of cm9 to get device tree and armv6 working
I'm on holidays now, can't upload it the coming 3 weeks
Sent from my B2G webbrowser

lemmymet said:
Just got a build with working RIL, things not working:
-Camera
-video playback
Maybe some more things, used parts of cm9 to get device tree and armv6 working
I'm on holidays now, can't upload it the coming 3 weeks
Sent from my B2G webbrowser
Click to expand...
Click to collapse
Great work mate!
I'll publish here my package on Saturday! Maybe we can help each other!
Let me know bro!

Hey mackief..........after you complete this for the gio...........can you try to port this on other ARMv6 phones(MINE FIRST )

csoulr666 said:
Hey mackief..........after you complete this for the gio...........can you try to port this on other ARMv6 phones(MINE FIRST )
Click to expand...
Click to collapse
If he's not having a device like yours, how is he gonna make it work for that device? :|

csoulr666 said:
Hey mackief..........after you complete this for the gio...........can you try to port this on other ARMv6 phones(MINE FIRST )
Click to expand...
Click to collapse
Maybe I can try to do it, but I cant do my best as I'll do for the Gio, because I don't have the device!

bgm92 said:
If he's not having a device like yours, how is he gonna make it work for that device? :|
Click to expand...
Click to collapse
That makes no sense.
What about cm9 builds for fit, mini by maclaw?
They didnt had it.
Phiexz releasing roms and kernels etc for devices he doesnt have
You just need to know watcha doing
Sent from my GT-S5660 using xda premium

Ya actually, you can develop for other devices. You just need the Device's sources and a friend to test that on their device

Peteragent5 said:
Ya actually, you can develop for other devices. You just need the Device's sources and a friend to test that on their device
Click to expand...
Click to collapse
Yeah someone you can PM who can test it before releasing unless you want spam
Sent from my GT-S5660 using xda premium

I can test........ That's the main reason I posted here.... I am ready to make my WFS a guinea pig for the sake of other WFS'S

[ROM] AOSP IceCreamSandwich 4.0.4 | MoltenMotherBoard

FEEL FREE TO DONATE US FOR ALL WE'RE DOING FOR YOU!
For general discussions, bug reports and FAQ, write HERE!​
Credits:
Jellaxy Team (in particular erikcas for CM9 / ICS sources and support)
marcin1147 (for support to make it booting)
OldDroid (for help with UMS / USB Mass Storage, test and support)
CyanogenMod team (for supporting ARMv6 devices)
Ganster41 (for OMX ICS hack that allowed anyone to have HW rendering)
Others for general support:
Bytecode
aspee
tioammar
MoltenMotherBoard!
Downloads:
MoltenMotherBoard mirror | AndroidFileHost
Full sources:
MoltenMotherBoard sources: MoltenMotherBoard | Github
Changelog:
Nightlies
Code updates
20141001
Huge sources cleanup
Code updates from AOSP, CyanogenMod
20130722
Code updates
RC9 | 20130616
USB and Wifi thetering fixed (broken till RC7)
Gapps updated to 2013.06.14
ADB icon hided
Hacked again AudioFilter.csv
Tethering improvements
Added new libs to manage partitions
Code updates
RC8 | 20130607
New kernel
New proprietary Bootsplash
Improved AudioFilter.csv
Code updates
RC7 | 20130511
Fixed UMS on new kernel
Added log Banner
New support for init.d scripts
Switched to Stock kernel
Added support for 4.7 GCC version and subsequent
Adjusted doubled props
Code updates
RC6 | 20130501
Settings: excluded System updates
Settings: excluded Bluetooth tethering
Launcher: 3 homescreens
MMS: Avatar showed in notification bar
Improved Camera effects
Included LiveWallpapersPicker
Code updates
RC5 | 20130403
Excluded WiFi Direct (not GIO compatible feature)
Excluded camcorder frame interval (not GIO compatible feature)
Excluded camcorder effects (not GIO compatible feature)
Increased SMS lenght from 8 to 100 (before converting to MMS)
Included 800MHz CPU speed
Re-included some UI sounds
Adjusted Camera layout
Usable without SIM card (after 1st boot - as we provide SetupWizard that needs it, not our fault)
Fixed Bluetooth issues (it broke after RC3)
Some changes for Dalvik and Battery life
Fixed Photo Editor (thank to vutaluk1995)
Fixed WiFi Tethering
Code updates
RC4 | 20130308
Switched to WEXT WiFi drivers
Fixed GPS (it broke after RC2)
Enabled Init.d support by default
Fixed GooglePlay Store - Error 491
Used Tiny_aosp.mk build config
Fixed RIL
Added AD-HOC network supports
Fixed YouTube reboots
Code updates
RC3 | 20130224
Fixed camcorder
Added GPS.conf mod
Added Ringtones loop
New updated specific Samsung libs
Added MMB-Vendor repo
Included Google vendor (Gapps on sources)
Code updates
RC2 | 20130127
Modded Hosts file (now no ads)
MMS: now with 'new-line' button
Added Superuser as default
Added apns-config.xml
Camera fixed in sources
Code updates
RC1 | 20130117
Fixed USB Mode
Cleaned init.rc
Fixed all display related lags
Added full support for QCom hardware devices
Cleaned Framework from other devices specifications
Fixed Browser
Fixed Camera (with erikcas CM9 prebuilts)
Added full support for Legacy Qualcomm OMX IL libs
Great improvements in Framework
Code updates
BETA3 | 20130103
Fixed WiFi
Fixed Display issues
Fixed GPS
Fixed compass
Force enabled Surface dithering
Code updates
BETA2 | 20121225
Added SU binaries (rooted by default)
Improvements in the framework
Improvements in display
Code updates
BETA1 | 20121215
First booting build
Issues:
-----
Do you want to report an issue? Do it here!
In order to do it, create a new issue, choosing correct labels corrisponding to: Device/OS which you're using, ROM/project you're on, kind of issue.
Also, please, be sure you're running the ROM/project in the exact way we've provided it to you (do not create issues if you're using different
kernel, mod, plugins and dependencies we didn't tell to use).
General Questions: MoltenMotherBoard Projects | General Questions and Info
Official Mantainer(s): Mackief, ItachiSama

AOSP:
XDA-Developers said:
The Android Open Source Project (AOSP), led by Google, is tasked with the maintenance and further development of Android. If you find a custom ROM that is based on AOSP, that means it will be closer to the original, vanilla Android created by Google rather than the bloated software created by Samsung, HTC, LG, and Motorola.
Click to expand...
Click to collapse
SearchConsumerization said:
The Android Open Source Project (AOSP) is an initiative created to guide development of the Android mobile platform. The Android platform consists of the operating system (OS), middleware and integral mobile applications.
The AOSP is overseen by the Open Handset Alliance (OHA), a Google-led coalition of over 30 wireless carriers, semiconductor companies, handset manufacturers and software companies. The purpose of the OHA is to further the development of open source standards for mobile devices.
The OHA member list includes Qualcomm, Broadcom, HTC, Intel, Samsung, Motorola, Sprint, Texas Instruments and Japanese wireless carriers KDDI and NTT DoCoMo. Companies that are conspicuously absent from the OHA member list include Nokia, Symbian, Apple, RIM, Microsoft, Verizon and Cingular.
Click to expand...
Click to collapse
AndroidCentral said:
AOSP is a term you'll see used a lot -- here, as well as at other Android-centric sites on the Internet. I'll admit I'm guilty of using it and just expecting everyone to know what I'm talking about, and I shouldn't. To rectify that, at least a little bit, I'll try to explain what the AOSP is now so we're all on the same page.
For some of us -- the nerdly types who build software -- the full name tells us what we need to know. AOSP stands for Android Open Source Project. The AOSP was designed and written by folks who had a vision that the world needed an open-source platform that exists for developers to easily build mobile applications. It wasn't designed to beat any other platform in market share, or to fight for user freedom from tyrannical CEOs -- it exists as a delivery mechanism for mobile apps -- like Google's mobile apps, or any of the 400,000+ in the Google Play store. Luckily, Google realized that using open-source software would ensure that this operating system/mobile application content delivery system is available for all, for free. And by choosing the licensing they did, it's also attractive to device manufacturers who can use it as a base to build their own mobile OS.
The premise plays out rather nicely. Google writes and maintains a tree of all the Android source code -- the AOSP. It's made available for everyone (you, me, manufacturers you've never heard of and not just big players like Samsung or HTC) to download, modify, and take ownership of. This means the folks at CyanogenMod can add cool stuff like audio profiles. It also means folks like HTC can change multitasking in ways that many of us don't like. You can't have one without having the other. The big players then use their modified version of this source to build their own operating system. Some, like Amazon, radically changed everything without a care to use Google's official applications and keep their device in compliance with Android guidelines. Some, like HTC radically changed everything yet followed the Android Compatibility Program (ACP) so they could include Google's core application suite -- including the Google Play store. Some, like the folks at CyanogenMod, enhance the pure AOSP code with additions but don't change the overall look and feel. Again -- that's how this open-source thing works. You can't have it without allowing folks to change it as they see fit, for better or worse.
Any of us can download and build the AOSP. We can even stay compliant with the ACP and contact Google about including their applications. Yes, any of us could build our own device using the AOSP code in our garage or basement with Google's full blessing. That's the beauty of the AOSP, and we wouldn't want it any other way.
Click to expand...
Click to collapse

So this will be AOSP based, and not CM9 based? If so, CAN'T WAIT!

it is AOSP, not AOSP based
Or CM9 or anything :laugh:
EDIT: Hope it will not end like Maclaw´s never released AOSP Project

Amazing,first AOSP for our gio.:laugh:

Not second but first. We had working closed-alpha of our AOSP ROM.

great! but why not JB?

belyava said:
great! but why not JB?
Click to expand...
Click to collapse
We prefer make a previous working version before making another.
That's like building ICS earlier than GB!? What the sense?
If we'll succeed to build AOSP ICS for GIO, then (maybe) we'll do the same with AOSP JB.

Cuz jellybean is very buggy and ics is much stable
Sent from my GT-S5660 using Tapatalk 2

marcin1147 said:
Not second but first. We had working closed-alpha of our AOSP ROM.
Click to expand...
Click to collapse
actually you are right.it is second aosp rom.

I wish you luck with this project

Still prefering AOSP gingerbread above ics. Am I the only one?
Sent from my GT-S5660 using xda app-developers app

Yeah but aosp gb on many phone is buggy We need a great developer to do it (I'm not thinking Px or SZ D)

Frankin96 said:
Yeah but aosp gb on many phone is buggy We need a great developer to do it (I'm not thinking Px or SZ D)
Click to expand...
Click to collapse
And you think ics isnt? Its the same
Sent from my GT-S5660 using xda app-developers app

Yeah I know but (Just my opinion) having an aosp gb is like having a cm without extra features, and cm7 without themes it's ugly, ics is awesome without any extra setting, because google team has done a great work , so , considering that with many build of aosp gb for msm based devices we have the bug of the first cm for gio or other (Wi-fi, gpu , radios ) , having an ics one with same bug of cm9 will be better

Too bad I dont have linux
Sent from my GT-S5660 using xda app-developers app

lol cm7 is built on aosp gb
I have also a closed-bate of aosp gb, bcoz of the cm7 device files i have a working aosp build

You no share?
Lol
Would be nice
Sent from my GT-S5660 using xda app-developers app

Now compile
Mobil cihazdan gönderildi...
aOS 2.3.6 BNC-GIO-R2

m.ali.ozkaya said:
Now compile
Mobil cihazdan gönderildi...
aOS 2.3.6 BNC-GIO-R2
Click to expand...
Click to collapse
Wow, now also we're commanded?!

[ROM] Vanilla Android [1-13-13]

I got bored and decided to build from the master branch of AOSP. This branch has the latest code changes and fixes however its not a release branch so some things may be broken too. I haven't touched any of the code the only thing I added was root. You will need to add Google Apps if you choose to use them. Also you will need to wipe if you're coming from another rom. I will keep this updated if enough people use this, if not consider this experimental.
Today's Download: http://d-h.st/4Ge

Cool, another openmaster user.
Sent from my Nexus 10 using xda app-developers app

tried out open master but there was some small things that I did not know how to fix that caused me to go back to release branches
I've learned a lot more since I posted this project which has been abandoned

Did you build user or user debug?
Sent from my Nexus 4 @1.5 GHz on Stock 4.2.1

android l compile from source?

Would someone be willing to build android l from source for the sprint gnex? I am willing to test it but I don't have the resources or the space to build it myself. Also, I would like it to be stock without root as I don't need that for the time being and don't want to risk a brick of any kind.

From what I understand, even though some sources are up for the L preview, not everything is there which limits the usefulness of source builds at the moment.
There is an ongoing discussion of L porting in the general section and even though its for the Verizon gnex, just remove the very top line in the updater script of the zip over there to make it flash on toroplus.
http://forum.xda-developers.com/showthread.php?t=2796203
Everything almost works but our open gl drivers aren't up to snuff and that pretty much can't be worked around at this point. Also it won't boot into android even though its about 90% of the way there, but full source is needed to hack around it.
Sent from my Galaxy Nexus using XDA Free mobile app

Question about honeycomb or ice?

Look, if like to start by saying I couldn't find the question section in tapatalk, and this seemed the most appropriate section to post in (move to correct one if necessary)
Anyway, my question:
I was wondering if it's possible to build either android honeycomb or tablet UI ICS (stock of course) for this kindle fire. I know that it seems weird to go back word in android versions, but honeycomb is my favorite and I wouldn't be able to build it as I don't have a Linux PC, and I'm having a surprising amount of trouble getting virtual box to work on my PC. (Yes, I'm using the correct cup architecture and have all required files) any feedback is welcome!
Edit: any way to edit the title? I didn't catch the typo... (Yet another reason to proof read)
Sent from my iPhone using Tapatalk

MeowDude said:
Look, if like to start by saying I couldn't find the question section in tapatalk, and this seemed the most appropriate section to post in (move to correct one if necessary)
Anyway, my question:
I was wondering if it's possible to build either android honeycomb or tablet UI ICS (stock of course) for this kindle fire. I know that it seems weird to go back word in android versions, but honeycomb is my favorite and I wouldn't be able to build it as I don't have a Linux PC, and I'm having a surprising amount of trouble getting virtual box to work on my PC. (Yes, I'm using the correct cup architecture and have all required files) any feedback is welcome!
Edit: any way to edit the title? I didn't catch the typo... (Yet another reason to proof read)
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
This would likely be better suited in the KFHD 8.9" Q&A forum. That being said, there will be significant work involved with porting. Honeycomb on these kindles would be like porting Windows 95 to run on a modern-day laptop. It might work, but it's unlikely. You'd have to spend a lot of time backporting Amazon's proprietary drivers (or even open source libraries, if such are still supported for older Android versions), and those are likely built with 4.0 in mind. Additionally, the underlying Android Honeycomb source code may not have critical components needed for proper operation on more recent devices like these. (It's worth noting that Amazon's stock firmware is based on ICS, so a large part of that work would likely be done already if you're porting that Android base.) Finally, I'd advise against porting older Android versions because they're not maintained or supported anymore by Google, so any compromising bugs or security holes (like the recent Stagefright issues) will not have been backported to those unsupported releases.
If you're still set on porting ICS, I haven't found any stock 4.0 build makefiles for the HD 8.9 on GitHub. You could use an unofficial prebuilt CM10.1 or CM10.2 ROM (look in the 8.9 development forum and use Xposed modules to modify the UI to tablet mode. I know of one Xposed module that backports tablet UI to JB ROMs, and it still works on KitKat/CM11. Those mods would save you a lot of time, as you wouldn't need to compile or backport older releases. If you want an up-to-date CM11 ROM to use the mods on, you'd need to compile with those sources (they're on GH here). If you're still having trouble, I'd be willing to compile CM11 for you.
Sent from my Amazon Jem using XDA Labs

monster1612 said:
This would likely be better suited in the KFHD 8.9" Q&A forum. That being said, there will be significant work involved with porting. Honeycomb on these kindles would be like porting Windows 95 to run on a modern-day laptop. It might work, but it's unlikely. You'd have to spend a lot of time backporting Amazon's proprietary drivers (or even open source libraries, if such are still supported for older Android versions), and those are likely built with 4.0 in mind. Additionally, the underlying Android Honeycomb source code may not have critical components needed for proper operation on more recent devices like these. (It's worth noting that Amazon's stock firmware is based on ICS, so a large part of that work would likely be done already if you're porting that Android base.) Finally, I'd advise against porting older Android versions because they're not maintained or supported anymore by Google, so any compromising bugs or security holes (like the recent Stagefright issues) will not have been backported to those unsupported releases.
If you're still set on porting ICS, I haven't found any stock 4.0 build makefiles for the HD 8.9 on GitHub. You could use an unofficial prebuilt CM10.1 or CM10.2 ROM (look in the 8.9 development forum and use Xposed modules to modify the UI to tablet mode. I know of one Xposed module that backports tablet UI to JB ROMs, and it still works on KitKat/CM11. Those mods would save you a lot of time, as you wouldn't need to compile or backport older releases. If you want an up-to-date CM11 ROM to use the mods on, you'd need to compile with those sources (they're on GH here). If you're still having trouble, I'd be willing to compile CM11 for you.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
Thanks for the feedback, my heart is indeed set on back porting honeycomb, I'll try later and see how it works out. I'm gonna have to research the recent stage fright bug (haven't heard of it). I figured I could just build android 3.2 from AOSP, set up the necessary drivers, and flash it. Even if that's not an option, I'll just try to build Stock ICS. I just like the older holo UI, and ICS and especially Honeycomb have it.
Sent from my iPhone using Tapatalk

MeowDude said:
Thanks for the feedback, my heart is indeed set on back porting honeycomb, I'll try later and see how it works out. I'm gonna have to research the recent stage fright bug (haven't heard of it). I figured I could just build android 3.2 from AOSP, set up the necessary drivers, and flash it. Even if that's not an option, I'll just try to build Stock ICS. I just like the older holo UI, and ICS and especially Honeycomb have it.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
If the holo UI is all you're interested in, you can use any recent ROM and this Xposed mod called Holo Themer that forces all apps that it can to fall back to the holo UI interface. Also, if you're running KitKat or below (CM11), you can use TabletKat, another Xposed mod to bring back the legacy tablet UI from Honeycomb/ICS.
Sent from my Amazon Jem using XDA Labs

monster1612 said:
If the holo UI is all you're interested in, you can use any recent ROM and this Xposed mod called Holo Themer that forces all apps that it can to fall back to the holo UI interface. Also, if you're running KitKat or below (CM11), you can use TabletKat, another Xposed mod to bring back the legacy tablet UI from Honeycomb/ICS.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
Sounds good, I'll check it out. On a side note, do you think it would be possible, after modifying the system UI, and all the system apps (framework.res,etc.,etc.) one could turn the stock Amazon OS into stock AOSP-like ICS? Just wondering, because it seems like every custom rom I find has some big I just can't stand (aside from the other ones) either it's too slow, no he youtube, the lock screen doesn't rotate, etc. while I've never had any problem with stock Amazon OS. (Other then that the may bar placement/UI/keyboard suck, but that's easily fixable).
Sent from my iPhone using Tapatalk

MeowDude said:
Sounds good, I'll check it out. On a side note, do you think it would be possible, after modifying the system UI, and all the system apps (framework.res,etc.,etc.) one could turn the stock Amazon OS into stock AOSP-like ICS? Just wondering, because it seems like every custom rom I find has some big I just can't stand (aside from the other ones) either it's too slow, no he youtube, the lock screen doesn't rotate, etc. while I've never had any problem with stock Amazon OS. (Other then that the may bar placement/UI/keyboard suck, but that's easily fixable).
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
It could be possible, but considering all the significant modifications Amazon made to the OS, it would most likely be a long, complex process. There may be xposed mods available to try to tweak the stock UI, and you could try to replace all the stock apps in the stock ROM with their AOSP counterparts, but there's always the risk of bootlooping the OS if you make modifications it doesn't agree with. I think you'd be better off using CM11 or a prebuilt custom ROM instead of trying to reverse engineer Amazon's source to reconcile it with AOSP.
Sent from my Amazon Jem using XDA Labs

I'm gonna try to work on that, there's no way I'm the only one who's thought to want the stock UI---interesting thing I found in the systemUI.apk, I found all the stock AOSP icons in SystemUI.zip/res/drawablehdpi even the tablet UI icons, which really through me off. Also, almost all the Amazon OS icons were in SystemUI.zip/res/drawable-- my idea, do some crazy xml/png editing, and get the stock UI I'm looking for. Your thoughts?
Sent from my iPhone using Tapatalk

monster1612 said:
...There may be xposed mods available to try to tweak the stock UI...
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
Do have a list of these modules? I've set up xposed framework on mine, but I'm having trouble finding modules meant for kindles, and I don't want to be constantly playing the "trial and wait 10min to restore my compressed TWRP backup" game.
Sent from my iPhone using Tapatalk

monster1612 said:
...There may be xposed mods available to try to tweak the stock UI...
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
Do have a list of these modules? I've set up xposed framework on mine, but I'm having trouble finding modules meant for kindles, and I don't want to be constantly playing the "trial and wait 10min to restore my compressed TWRP backup" game.
Sent from my iPhone using Tapatalk

I just figured out why it wasn't letting me send that last post...
Sent from my iPhone using Tapatalk

MeowDude said:
...almost all the Amazon OS icons were in SystemUI.zip/res/drawable-- my idea, do some crazy xml/png editing, and get the stock UI I'm looking for. Your thoughts?
Click to expand...
Click to collapse
You could do that, but I think it'd be easier to copy/paste icons from an AOSP/CM9 ROM. (CM9 is the corresponding version for AOSP 4.0.3, which is still ICS.)
MeowDude said:
Do have a list of these modules? I've set up xposed framework on mine, but I'm having trouble finding modules meant for kindles, and I don't want to be constantly playing the "trial and wait 10min to restore my compressed TWRP backup" game.
Click to expand...
Click to collapse
I haven't tried out the xposed framework on Amazon's stock OS, so I think you'll have to play with trial and error. However, you won't need to mess around with restoring TWRP backups - all you need to do to disable the framework is simply run touch disabled from the TWRP terminal in the /data/data/de.robv.android.xposed.installer/conf/ folder. Then reboot, uncheck the problematic mod in the Xposed Installer, delete that disabled file, and reboot to re-enable the framework.