Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,733,098 Members 46,839 Now Online
XDA Developers Android and Mobile Development Forum
Announcement from Hashcode: If a Kindle was a Nexus..

Project OtterX: New Direction

Tip us?
 
Hashcode
Old
(Last edited by Hashcode; 29th May 2014 at 07:08 AM.)
#1  
Hashcode's Avatar
Recognized Developer - OP
Thanks Meter 21980
Posts: 3,208
Join Date: Sep 2011

 
DONATE TO ME
Default 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.
The Following 51 Users Say Thank You to Hashcode For This Useful Post: [ Click to Expand ]
 
Hashcode
Old
#2  
Hashcode's Avatar
Recognized Developer - OP
Thanks Meter 21980
Posts: 3,208
Join Date: Sep 2011

 
DONATE TO ME
reserved
The Following 4 Users Say Thank You to Hashcode For This Useful Post: [ Click to Expand ]
 
lovejoy777
Old
(Last edited by lovejoy777; 24th January 2014 at 11:40 PM.)
#3  
lovejoy777's Avatar
Senior Member
Thanks Meter 1625
Posts: 2,390
Join Date: Dec 2011
Location: Nottingham

 
DONATE TO ME
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
Gnex: Dreams 4.4 KitKat
Kindle Fire: OtterX SlimKat & 777Kernel
http://forum.xda-developers.com/show....php?t=2747564
Nexus 5: SlimKat

If you like my work or think I have helped please hit the thanks/donate buttons
 
Ixthusdan
Old
#4  
Senior Member
Thanks Meter 110
Posts: 384
Join Date: May 2012
Location: Mishawaka, IN
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
 
bhuffman
Old
#5  
Junior Member
Thanks Meter 0
Posts: 14
Join Date: Jul 2008
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.
 
burgon
Old
#6  
Member
Thanks Meter 3
Posts: 59
Join Date: Mar 2009
This project is exactly what this device needs.

Sent from my Nexus 7 using XDA Premium 4 mobile app
 
ammubarak
Old
#7  
Senior Member
Thanks Meter 32
Posts: 155
Join Date: Dec 2011
Location: Safwa, Saudi Arabia
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
 
werwortmann
Old
#8  
Junior Member
Thanks Meter 1
Posts: 6
Join Date: May 2012
Location: Pretoria
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
 
firered365
Old
#9  
firered365's Avatar
Senior Member
Thanks Meter 159
Posts: 727
Join Date: Mar 2012
Location: Houston
I wouldn't mind not going back to kindle software.
//Phone: Mako
//ROM: Stock
//Tablet: Otter
//ROM: CM11
The Following User Says Thank You to firered365 For This Useful Post: [ Click to Expand ]
 
kev716
Old
#10  
Junior Member
Thanks Meter 2
Posts: 19
Join Date: Aug 2013
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

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes