Database Users

Pros and Cons of CM7 on KF?

Hi, the reasons I've bought the Kindle Fire was that I wanted a cheap tablet on one hand (whilst it's quite capable HW-wise) and it's ability to be customized (it's capacity to have 3rd party roms on it, etc) on the other. On that second point I'm sure that the community will work its magic in the coming months: my dilemma however is with what I should do with the Fire I *currently* have...
I've received it a couple of days ago and I found out that the vanilla ROM seems quite alright on in itself. It seems limited, but as long as one roots and installs the Market (almost) the whole of Android force is unleashed. The UI is not always functional but it does feel as a breath of fresh air in a landscape which is tatterered with clones of the same thing (Google's UI)...
Anyhow the purpose of this thread -as the topic title states- is to weigh whether the installation of CM7 on KF is a justifiable move (given what we have at hand) for everyday use. I do own other android devices as well and installing CM flavours there was -often- an easy move given the benefits (more hardware capabilities, cleaner/faster UI, etc).
But on KF things seem to be less clear cut. For one CM7 doesn't seem to do more than what the stock rom already achieves in either the hardware side of things (no new "function" is enabled) *or* the software side (the lag is still there, and Amazon has/had already done an admirable job to keep her device working without the need of any physical buttons).
So my question is to those who already made the move to CM7 for daily usage. Was it worth it for any non experimental purposes? Were there any discernable benefits compared to stock? (I mean considering how the situation is right *now*, not how things *can* be).
Thanks for your attention and sorry for the length of this post, it's only that this is the first time that I find myself in front of such a dilemma. Before KF I would often install CM on my device no questions asked, but now things seem less clear cut. Your opinions will be valued - again, thank you.

For everyday use i find CM7 more useful simply because the Fire launcher is convoluted. Nothing you cant achieve with a launcher, however launchers tend make pior use of the sceeen real estate. Also no need to worry aboit the root removing OTA updates.
The only downside i have with CM7 right now is the lacl of volume softkeys

The Anthem said:
For everyday use i find CM7 more useful simply because the Fire launcher is convoluted. Nothing you cant achieve with a launcher, however launchers tend make pior use of the sceeen real estate. Also no need to worry aboit the root removing OTA updates.
The only downside i have with CM7 right now is the lacl of volume softkeys
Click to expand...
Click to collapse
Hmm, but how can a mere launcher be the whole reason to change a Rom? Why can't -one- siimply install one from the market?

The Anthem said:
Also no need to worry aboit the root removing OTA updates.
Click to expand...
Click to collapse
IMHO, this is the main reason to install CM7.
The Anthem said:
The only downside i have with CM7 right now is the lacl of volume softkeys
Click to expand...
Click to collapse
There is workaround for this, I do not remember, but somewhere in the forum

gett said:
IMHO, this is the main reason to install CM7.
Click to expand...
Click to collapse
The only reason I haven't tried CM7 is that I have had Amazon Prime for a long time and like to use Amazon's services.
Originally Posted by The Anthem
The only downside i have with CM7 right now is the lacl of volume softkeys
Click to expand...
Click to collapse
There is workaround for this, I do not remember, but somewhere in the forum
Click to expand...
Click to collapse
"Volume Control" from the Android Market is great - it puts a volume slider that auto-hides on the edge of the screen.

Pros: It does everything the kindle does at stock and then more (If you want to use emulators and games, I would recommend it).
Cons: It is hard to set up the stock amazon apps on CM7, although possible. There is also a small chance of bricking your device if you do everything totally wrong and for some reason (like not following directions) cannot unbrick using the known methods.
The main difference for me has been that I can use different PDF software to read PDFs more clearly and that I can play emulators on it.

A con for cm7 right now is the CPU constantly being at 1008mhz when wifi is on...at least for me. I tried the mac address fix but it didn't work.
Sent from my MB860 using XDA App

For me I feel CM7 gives you that tablet feel more so than the Amazon UI. Having customization is always one of the main things I look for. I do have Amazon Prime however I hardly use any of their services besides the shipping. (Netflix > Amazon Instant Video)
Also if you do everything right and make a back up of your stock, you can always revert back to it if you don't like what you see.

The browser is smother on cm7 silk loads a bit faster, but the scrolling feels smoother on cm7, also in stock firmware when you go full screen you cant get rid of the gray bar, on cm you can hide it and show it as much as you want.
How ever... i feel that battery life is a bit shorter, but not much, I don't know if anyone else has that feeling.

there are no cons to CM7. ITS THE GREATEST software. I just got finished with ice cream sammich and that is boring as heck. Flashing back to CM7 and leaving my Vision in the ice cream.
Sent from my HTC Vision using xda premium

there are no cons to CM7. ITS THE GREATEST software. I just got finished with ice cream sammich and that is boring as heck. Flashing back to CM7 and leaving my Vision in the ice cream.
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
You've got to be kidding me...

Winglerw28 said:
Pros: It does everything the kindle does at stock and then more (If you want to use emulators and games, I would recommend it).
Cons: It is hard to set up the stock amazon apps on CM7, although possible. There is also a small chance of bricking your device if you do everything totally wrong and for some reason (like not following directions) cannot unbrick using the known methods.
The main difference for me has been that I can use different PDF software to read PDFs more clearly and that I can play emulators on it.
Click to expand...
Click to collapse
Yea I got chrono cross working so its been great. I agree with the pdfs as well studying for some it certs so its been really helpful.

androidcues said:
there are no cons to CM7. ITS THE GREATEST software. I just got finished with ice cream sammich and that is boring as heck. Flashing back to CM7 and leaving my Vision in the ice cream.
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
... this is your brain on drugs.

GBH2 said:
"Volume Control" from the Android Market is great - it puts a volume slider that auto-hides on the edge of the screen.
Click to expand...
Click to collapse
Which volume control, there are seven of them?
THX

cuban11182 said:
Which volume control, there are seven of them?
THX
Click to expand...
Click to collapse
https://market.android.com/details?id=rubberbigpepper.VolumeControl
imo this should be included with the rom

I am running CM7 as a daily ROM at the moment, and I can say that it is much better than the Amazon stock ROM. When running stock you have to worry about OTA updates that can potentially remove root access and prevent it from being acquired again (until a workaround is found). Also, for me at least, CM7 seems to run much better than the stock ROM did, with little to no lag.

GBH2 said:
The only reason I haven't tried CM7 is that I have had Amazon Prime for a long time and like to use Amazon's services.
"Volume Control" from the Android Market is great - it puts a volume slider that auto-hides on the edge of the screen.
Click to expand...
Click to collapse
Even if you have Amazon Prime you can use Amazon services still. You just have to download the apps onto CM7. I have done this, but I forgot where I got the apk files.

A couple more notes on CM7 v Stock
I no longer have the issue where the Fire wont wake and I have to hold power for a reboot.
Inputs seem more responsive, I no longer have to press things multiple times or them to work, mainly back button was problematic.
Much greater app compatibility in the Marketplace.
Also, thanks for he volume control, just what I needed.

ragul40 said:
Even if you have Amazon Prime you can use Amazon services still. You just have to download the apps onto CM7. I have done this, but I forgot where I got the apk files.
Click to expand...
Click to collapse
Interesting. I may have been misinformed. I have Amazon Prime, have for years. I realize that I can still install the Kindle app and other Amazon apps, but can I still receive Amazon Prime free Streaming videos and free Kindle owners lending library, etc. if I switch over to CM7?

I rooted just the other day, I run cm7 on all my other devices, I do not have interest in it beyond the app swap option and swipe lock screen. The stock build + market is all I need at this point. When cm7 develops into a fully stable option I will certainly switch but for now I don't reccomend it.

[INFO] no more official TWRP

I don't know if everyone already knows this, but for those who don't. As of right now TeamWin is dropping the TWRP project . The reasons are on their website. But they said they will (hopefully) help out with CWM
Shifted from Outer Space

Man that really blows I enjoyed twrp
Sent from my PG06100 using Tapatalk

That does suck. I liked it a lot better than cwm
Sent from my PG06100 using Xparent Blue Tapatalk

Touch CWM did make it kinda redundant, but I suppose the purpose of TWRP being part of CWM with it's large following was bound to do something like this.

gigermunit said:
Touch CWM did make it kinda redundant, but I suppose the purpose of TWRP being part of CWM with it's large following was bound to do something like this.
Click to expand...
Click to collapse
Expect touch cwm is ugly. Hopfully with Team Win helping out, i can stand using it

I hope teamwin can make cwm touch better too lol. It needs some bling bling.

I'd rather recovery devs spent time improving functionality/stability, not looks. Why does it matter if recovery looks good if it works well? It's not like it's a main part of user experience, even flashaholics spend a very small amount of time (proportionally) in recovery. I guess I'm just curious, why the focus on looks?

HTCotta said:
I'd rather recovery devs spent time improving functionality/stability, not looks. Why does it matter if recovery looks good if it works well? It's not like it's a main part of user experience, even flashaholics spend a very small amount of time (proportionally) in recovery. I guess I'm just curious, why the focus on looks?
Click to expand...
Click to collapse
Have you seen touch cwm? You only get to use half the screen and the other half in blank when it could be used to continue the list of options. Everything is bigger so you are scrolling a hell of a lot more since instead of full screen usage like before it's half screen like I mentioned. Its a headache to use. I switched back to twrp 2.0 cause they got it right and for me everything works.
Sent from my PG06100 using Xparent Blue Tapatalk

Good riddance. CWM works perfectly.

Kinda liking Touch CWM. But it was nice to have options.

prboy1969 said:
Kinda liking Touch CWM. But it was nice to have options.
Click to expand...
Click to collapse
It's nice to have 3 batteries that work too. It's nice to pop in another battery when yours is dead and have it charged at 98%. I totally am getting one of those wall chargers dude.

Glad it helped man. I'm totally loving the extra up time on the Batt.

Noob advice: The current state of Kindle fire custom ROMs

Hi,
(I already have experience with rooting and installing custom roms on my HTC desire.)
A colleague of mine will travel to the US in a few days, and we where thinking of having him buy and bring back two Kindle Fires from there.
I have a few questions about the feasibility of this, and would be very grateful for some info, to avoid spending .
The infos in this forum are very extensive, and it is very difficult to keep the overview (especially since things change so rapidly).
1. How well are the custom roms working at the moment? Are they ready to be used in actual work environments, or are they still too experimental for this?
2. I want a very minimalist rom, the vanilla Google experience (my favourite on the HTC was Oxygen ROM). Any recommendations? ICS would be great, but Gingerbread would be okay, too. Most important is stability.
3. When I will try rooting and flashing the devices that will take place in Europe. Could this cause problems? E.g., the Amazon Marketplace is inaccessible from here (blocks non-US IPs). I assume that wont matter, just wanted to make sure.
Thanks for your help in advance!
rhhd

1:
http://forum.xda-developers.com/showthread.php?t=1533001
http://forum.xda-developers.com/showthread.php?t=1556910
2:
http://forum.xda-developers.com/showthread.php?t=1475054
3:
http://forum.xda-developers.com/showthread.php?t=1519456
http://forum.xda-developers.com/showthread.php?t=1547252
http://forum.xda-developers.com/showthread.php?t=1393862
http://forum.xda-developers.com/showthread.php?t=1288862
maybe this one is also interesting for you:
http://forum.xda-developers.com/showthread.php?t=1382360

CM7 is nice. Completely stable. You'd probably like Barebones CM7. I was using Standing on the Shoulders of Giants CM7 ROM and loved it.
But...I really wanted ICS, so I flashed CM9. It's beautiful, and very stable, however due to no hardware acceleration (yet) you won't have flash and some games seem to not work.
With all that said, stick to flashing a CM7 Rom and you'll be happy, IMO.

Thanks for the responses.
ChicagoGOBLUE said:
due to no hardware acceleration (yet) you won't have flash and some games seem to not work.
Click to expand...
Click to collapse
And this also means no hi-res video support, right?
Or do is just need to have the right app for that?

right - allthrough you can do hi res video with software like mx player does
but this will result in low framerates (stuttering depending on the source) and high battery usage

Thanks again!
One more question: I just noticed the Kindle Fire has only one physical button (power). The Nook Color has at least a few more (Power, Home, Vol+, Vol-).
Is that an annoyance in everyday life on the Kindle? On my HTC I am kind of glad about the Home, Back, Menu and Volume buttons...
(We haven't yet made a final decision between Kindle and Nook.)

there are softbuttons for all this functions and i learned to live with it
in the meantime it is a bit strange for me when i take the gtab from my wife with the hardbuttons
no problem at all ...

rhhd said:
Thanks again!
One more question: I just noticed the Kindle Fire has only one physical button (power). The Nook Color has at least a few more (Power, Home, Vol+, Vol-).
Is that an annoyance in everyday life on the Kindle? On my HTC I am kind of glad about the Home, Back, Menu and Volume buttons...
(We haven't yet made a final decision between Kindle and Nook.)
Click to expand...
Click to collapse
Not gonna lie, the lack of physical volume buttons drives me crazy. Livable now that I have CM9, but if using CM7 the 'volume control' app/widget/whatever, is a good option.

The lack of physical buttons on the kindle fire is a lucky break for developers as ICS is built with soft buttons in mind for the major functions of the OS so the one button isn't really a big problem. If google decides to go back to relying on physical buttons in jelly bean then the kindles custom rom future will be up in the air. For now if I were you i'd stick with CM7 until the developers have a chance to perfect the new kernel they're working on that will allow for better graphics among many other improvements.

I bought and registered my Kindle while I was in the states and I haven't had any problems with it here in Europe. I used the stock ROM for a few months and was only able to access the US Amazon, though I'm American so I don't know how that will effect you.
As for the soft buttons, I didn't have any problems with it. I thought the KF's stock ROM organized it pretty well; it was really easy to access the volume and brightness controls. The only thing I didn't like was that the bottom task bar was really big and, although it shrinks when you have full screen on, I was still annoyed by it. CM7 doesn't have that problem, though as someone else mentioned, apps are necessary to comfortably access volume control.
To sumarize, I think it was worth getting. I'm happy with it.

Touch Sensitivity

Just got my Nexus 4, no doubt its a great phone but the touch sensitivity is awful, like my htc explorer's (a low end phone) touch is even better than Nexus 4, theres nothing wrong with the touch screen but it just doesnt recognize light touches. Is it the same case with everyone?
Sent from my Nexus⁴

There's a mod to improve the touch screen sensitivity. Requires root.
http://forum.xda-developers.com/showthread.php?t=2163924
The touchscreen used to be sensitive but Google changed something in an update and this mod just reverts back to the old sensitivity. Using it now it's brilliant!

Try turning on the dev option to show pointer location, which also shows the pressure registered for a touch. I can get 0.2-something for a swipe (higher for a straight touch).
My screen is fine. Franco's kernel also has some sensitivity improvements (and still uses the latest driver, avoiding other issues), which you might like to try.
Sent from my Nexus 4

jiayit said:
There's a mod to improve the touch screen sensitivity. Requires root.
http://forum.xda-developers.com/showthread.php?t=2163924
The touchscreen used to be sensitive but Google changed something in an update and this mod just reverts back to the old sensitivity. Using it now it's brilliant!
Click to expand...
Click to collapse
Already know about that mod but don't wanna root my Nexus⁴ just for now.
Sent from my Nexus⁴

hsn97 said:
Already know about that mod but don't wanna root my Nexus⁴ just for now.
Sent from my Nexus⁴
Click to expand...
Click to collapse
Then I'm afraid you don't have many options available :/
If you are willing to root, however, I would recommend one of the newer revisions of Franco kernel (i.e. r134) which includes touch sensitivity improvements, without breaking touch-based recoveries.
Sent by carrier pigeon

klvnhng said:
Then I'm afraid you don't have many options available :/
If you are willing to root, however, I would recommend one of the newer revisions of Franco kernel (i.e. r134) which includes touch sensitivity improvements, without breaking touch-based recoveries.
Sent by carrier pigeon
Click to expand...
Click to collapse
Ill surely root but just wanna experience stock for some time. And the touch isn't that bad now actually
An off-topic question, can you guys tell me how to mount N4 as usb storage in windows? When i connect it with cable to my Win Xp laptop it shows device connected ad N4 and shows internal memory but when i try to move any files in it, it just gets stuck so whats the deal?
Sent from my Nexus⁴

If you're not willing to root and install CWM, then get used to the, "poor" sensitivity. Sorry, pal.

hsn97 said:
Ill surely root but just wanna experience stock for some time. And the touch isn't that bad now actually
An off-topic question, can you guys tell me how to mount N4 as usb storage in windows? When i connect it with cable to my Win Xp laptop it shows device connected ad N4 and shows internal memory but when i try to move any files in it, it just gets stuck so whats the deal?
Sent from my Nexus⁴
Click to expand...
Click to collapse
You can root and unlock bootloader and still stay stock, just so you know.

Project OtterX: New Direction

** WARNING. WORK-IN-PROCESS DISCUSSION. NO ETAS. NO DONATIONS. NO PROMISES. **
PROJECT OTTER X DISCUSSION
It's a major change to the device. If you choose to update, it won't be easy to flash back the stock files and use your device as a Kindle again. The device name will actually change to "otterx", so that the 2 sets of files can be kept clearly distinct as well as provide a safety net for those who accidentally download the wrong thing and try to flash it.
GOALS OF THIS PROJECT: Make everyone happy of course.
[DONE] Update the bootloader (u-boot). And I don't mean "tweaks" to the bootloader, I mean: the current code was based on a 2011 release. The newer bootloader will be based on a 2014 release. Changes to be included in the update:
[DONE] A much better text driven menu system laid on-top of the initial boot graphic (as opposed to the image-only menus currently)
[DONE] Cleaned up device initialization / charging loop for extreme low battery situations
[DONE] Support devtree binary loading (native support for newer kernels)
[DONE] Support for decompessing kernels in new formats
[DONE] Native "reboot recovery" support no more hacky idme/sticky values
[DONE] Device "handling" changes like a longer button press to fully power on the device. Avoids "accidental" power ons while traveling.
[DONE--NEED NEW OTTERX ROM] Built in support for "charger" mode. IE: plug the device in while it's off and it boots into the native Android charger screen, vs a full boot of Android.
[DONE] I'm guessing a new initial power-on logo as well (it says "KINDLE" -- I lied.. but you can change it!)
[DONE] Partition layout change to support 5 to 6gb of combined app / sdcard storage.
[DONE] Rebuild a new TWRP to support combined data/storage
[DONE] The process for changing the partition layout is be handled in the bootloader menu. Users will need to pull everything off the internal storage prior to performing the change as it will wipe system, cache and userdata partitions out during the process.
[DONE] Kernel and userspace now support F2FS format for userdata. This is a new filesystem specifically designed for devices which use EMMC style storage.
Kernel update. A lot has happened to the OMAP kernel world over the last year. Much of the code needed to run newer kernels has been merged into the mainline. However, much has not. So I'm riding the line between: 1) finishing the 3.4 kernel using the new bootloader and partition layout, with an option for upgrading later to an even newer one. Drawback: I don't have a 512MB based ducati binary to process HD codecs for the 3.4 kernel. Or, 2) starting a newer kernel to go hand in hand with the other portions of this update (it would be 3.8 or newer). Why upgrade the kernel? Besides the typical "bigger better faster" mentality, I want some specific solutions to current problems: our graphics layer has been outdated for 1-2 versions of Android, and we still use a TI supplied ducati binary for HD codecs. If we update to a 3.8+ kernel, I can then attempt to build a custom ducati binary which would work better with our 512MB memory requirements and leave more free space to the OS.
Of course, the REAL end goal: to keep this device current and usable using today and future OS updates. And yes, maybe even get OTG and the MIC functions working.

reserved

yes i would update immediately
edit
Multi boot isn't a priority for me and as you say space is key with the kindle.
the new partitions sounds great.
Sent from my Nexus 5 using Tapatalk

My kindle is my toy. I burn any rom I can on it, and make backups to store off kindle. I have other equipment, would probably try to make an image before changing. But I would play with it!
I do not want to dual boot. I use virtual environments on my desktop for other os.
Sent from my Nexus 7 using xda app-developers app

1) I would absolutely perform this update. No - I never had an intention to use this device as a stock Kindle Fire Reader.
2) I really can't say if it would appeal to others. But the rationale makes sense to me.
3) I agree - better to have one VERY usable ROM.

This project is exactly what this device needs.
Sent from my Nexus 7 using XDA Premium 4 mobile app

Thanks for your ideas. These ideas will make KF an interesting device to develop and test apps.
Sent from my Amazon Kindle Fire using Tapatalk

1 - I would definitely repartition etc.
2 - I think most current users would also
3 - I wouldn't personally dualboot
I would also love Ubuntu with a similar partition layout,
Thanks for the continuous support, it has provided a great user experience

I wouldn't mind not going back to kindle software.

1. Would you perform such an update knowing that you would have a hard time going back to the Amazon software.
Yes, definitely
2. If I were to drop the partition layout change from this project do you think more users would like it? Or less?
Less
3. I had considered a dual boot option to be built into the new menu system.
Drop the dual-boot idea
Kevin

Yes for all 3, it will make the kindle much more better and faster
Sent from my Moto G using xda app-developers app

just ordered a replacement screen for my emmc damaged kindle, so i will also be trying your unbrick procedure soon. thanks so much for all your work Hash. its greatly appreciated. cheers Steve
Sent from my Nexus 5 using Tapatalk

Hashcode, it would be great to see you take Kindle Fire development in this direction. The plans are grand and it's obviously going to take a lot of work, but it would certainly breathe new life into the device. If you're going to do it, I say you swing for the fences. My guess is most people around this forum are here for the full android experience and not so worried about leaving the amazon ecosystem behind. Plus, the storage capacity on the KF has been a sore point from the beginning, so combining the userdata and sdcard partitions is really the best way to optimize usage for all users. With those two things in mind, I think it's a relatively easy decision to repartition as you've planned and forgo dualboot (which will also complicate the emulated sdcard usage anyway). Eagerly looking forward to the great things to come! :good::good:

Hashcode said:
DISCUSSION POINTS:
1. Would you perform such an update knowing that you would have a hard time going back to the Amazon software. Who really uses their original Kindle Fire as a reader anymore anyway?
2. If I were to drop the partition layout change from this project do you think more users would like it? Or less?
3. I had considered a dual boot option to be built into the new menu system. But I think we just don't have the internal space for it. I'd rather have 1 VERY usable tablet, than a dual boot system which isn't as usable in either ROM. Thoughts?
Click to expand...
Click to collapse
I really love your idea for otterx.
On your discussion points:
1. Yes, I would update for sure
2. The partition layout change seems like it is key to otterx. If the partitioning is manual it will cause problems for some. If it is automatic then everyone will love it. Neither of these options will scare me away BTW.
3. I prefer a single ROM that is stable/usable versus two unstable dual boot ROMs.
Even if otterx doesn't get off the ground, thanks again for helping keep this HW relevant.

1. I would update for sure.
2. The partition idea seems brilliant since space is a key constraint. It would also be great to have OTG working.
3. No need for dual boot.

My vote
I just want to cast my vote for Project OtterX along with everyone else. I'd update (I haven't run Amazon software in my KF for more than two years). The partitioning is key and necessary to keep the KF usable with future OS updates. As with others, dual boot isn't important to me.

1) I would totally update, been years since my last boot of the Amazon OS. I can get any Amazon App from Google Play, Non-Amazon Prime Users should NOT have a problem, unless they are and usae Instant Video.
2) In theory this should way better, but there might be a problem: Harder Developing. If it is in fact harder to develop a ROM for this specific type of system, we may look into very few ROMs available, which I am pretty sure I community does NOT want. Even though, I am doubtful it will get any harder.
3) Dual Booting might be awesome, but on this device, the Hardware will be much slower and otherwise defeat the purpose of building this new "OtterX".
In other words, I FULLY AGREE, that we should continue or start the OtterX project. We might wanna do a poll to assure that our community in fact will want this. Hope you have success in this Hashcode!!!
Sent from my Amazon Kindle Fire using xda app-developers app

Dual booting can be really useful for me specially if we can boot tar images easily with chroot with also a specific kernel instead of repartitioning every time

Small update as I work on the new bootloader.
Some of the new screens.
Image #1: I really like the new ultra simple bootscreen of the HDX's so I thought I'd start there... tho I may still change "kindle fire" to something else.
Image #2: Is the low battery charging screen
Image #3: Is a new screen similar to what the KFireHD 8.9" has for anytime you enter fastboot mode.
(Text responses from fastboot are shown on the fastboot screen)
Once I get the menu system up and running, I'll try and put some shots of that up as well.

Hashcode, you are constantly amazing with what you have managed to make work on this device. I love all the ideas of this project, I'm definitely a #2 user from your first question. I primarily use my Kfire as a reader(Amazon Kindle app) and internet browser, with some gaming/email here and there.
Discussion Points:
1) I definitely would, I tried going back to the Amazon software about a year ago and couldn't stand it then, let alone since all the work you've done in the last year to get the newer 4.3 and 4.4 revs available.
2) I feel this is a less likely to use situation. the Kfire has a horrendous partition layout for a normal tablet use, I know why it was, but compared to how fluid it feels on my Gnex(similar in that it has no SDcard slot either) the kfire could definitely see better usage in your proposed setup.
3) I have no large interest in dual boot myself, as you mentioned it had a limited amount of storage on the device, something I've found running into limits quickly just using Multiple profiles in CM let alone adding a whole extra system of data to the tablet. Personally I'd prefer the tablet made as functional/quick as possible without worrying about a second OS. I'll be perfectly content with one Os that runs great rather than 2 that could both stand to run better.