• Login:

Welcome to the Toshiba Thrive Forum.

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed.

+ Reply to Thread
Page 1 of 6 1 2 3 ... LastLast
Results 1 to 10 of 52
Like Tree82Likes

Thread: [Guide] Your walkthrough of Jelly Bean ROMs for the Thrive 10"

  1. #1
    Developer

    Member #
    18359
    Join Date
    Sep 2012
    Location
    Surprise, Az (that's a real place)
    Posts
    3,752
    Liked
    1894 times
    Twitter
    piomasaki

    [Guide] Your walkthrough of Jelly Bean ROMs for the Thrive 10"

    This is going to be a long, tedious, boring, hugely rambling bunch of text that most will have already stopped reading.

    If you kept going, congratulations, you're on your way to reading the most in depth guide I have ever attempted:

    A picture book of Jelly Bean ROMs currently available for the 10" Thrive.

    First up, we have...drumroll.....CM10!

    Chapter 1: The Background (yes, chapters!)

    Android Source, AOSP (Android Open Source Project) is the base that we use the build the ROM. Google creates this source and releases it, and its patches, to the public who can then use the code how they wish. This is a giant leap for mobile OS as previously it was all closed source, meaning only the company had it's source, or manufacturers of devices using this OS, such as Windows, Blackberry, iOS, etc. Android being completely open allows us to use Android on a variety of devices not originally supported, case in point being our Thrives running Jelly Bean. If Android left it to the manufacturers to release the source, we'd never have Jelly Bean. However, we still need more. The source is just the source, it builds the ROM, but it doesn't build it for any given device, for this we need....

    Trees! Those wonderful leafy things....wait...wrong one. In this case trees are broken up into 2 different parts, the device tree, and the vendor tree (though some don't consider the vendor tree to be a tree). The device tree tells the source how to interact with the device you're building for, it also tells it to build extra parts, libraries and some drivers to enable the device to use its various hardware, such as GPS, WiFi, BT, the screen, the digitizer, you get the point. If this is incorrect, it will not work properly, if at all, on a device. These trees is what the Unified project was about, building working fully functional CM10 ROMs by building the trees correctly. Lots of trial and error. The Vendor tree contains the proprietary files needed, these are files that source is not released for, and we must use pre existing, pre built files, these include anything nVidia, such as CPU and GPU libraries and drivers. One thing, the ROM may build perfectly fine, but if it's missing one more part, it'll never leave the Toshiba bootloader screen which is...

    The Kernel. This mystery is a collection of its own source files, controlled via defconfig. This file tells what to build for the hardware to work. If the kernel doesn't work, nothing else will, period. If the ROM is the brain, the kernel is the nervous system. It directly converts any commands given to work with and interact with the hardware, and the hardware to interact with the user. Anything you do on the screen, touching the WiFi toggle, for example, will then interact with the driver, which then interacts with the kernel, which then interacts with the hardware. Once the hardware listens, for example WiFi turns on, it reports it to the kernel, which reports to the driver, which reports to the screen to show the toggle as ON. As you can probably tell, a faster kernel = a faster system. A faulty kernel = a faulty system.

    CM10 refers to CyanogenMod 10, in this case 10 covers android version 4.1. CM10.1 covers the 4.2 release of android (its confusing but both have Jelly Bean as their name even with some major changes). CyanogenMod is a collection of useful modifications to the Google AOSP Source (you read that section above, right?) and offer things such as:

    Status bar icon changes
    Toggles to the status bar for quick changes to your system hardware
    A theme engine so you don't get bored with the same old icons and colors
    Various tweaks and enhancements to various parts of the ROM for stability, fixes, patches and speed

    CyanogenMod is of course, not the only modification available for the AOSP source, though many do still base on CM's existing modifications and build upon them with their own. Examples of this are Team Baked's Black Bean, available here, and also Paranoid Android (at the time of the writing they are moving to AOSP instead), also available here.

    Chapter 2: The ROMs

    This is going to be a multi part after school special of rundowns of each ROM, and its distinct and common features. I'll begin with CM10 as that is most commonly used here, and is the basis for all existing Jelly Bean ROM work anyways.

    Part One: CyanogenMod 10

    As covered before, CyanogenMod10 (CM10) is a modification of Google's AOSP Android source, and features plenty of additional fun stuff.

    The most common version of this build you will see for this device is the Unified Builds, created by a team of 3 +1 wiki operator, Tybar began the project, JBettcher and myself (pio_masaki if you didn't notice) took up arms and began working on getting CM10 built and running on this device. Indest runs our Wiki and created not only a custom gapps package for our device, but a side pack filled with useful apps, voted on by this very community. The team currently has just myself and Indest still active, but development does continue on a much slower basis.

    Features you can look forward to, and may already know about, that do not exist in normal AOSP "Vanilla" builds are:

    Power menu = the normal power menu is simply a way to turn off the device. This is found by holding power for a second or two (much longer and you may power off the device). CM10 instead adds a few features to this menu, including:

    Reset
    Reset also includes the ability to choose Normal system reboot and Recovery reboot. The normal reboot option will reboot into Android, recovery will reboot into your currently installed recovery, be it TWRP or CWM (or stock, which is extremely unlikely).

    Screenshot
    Yup, just like it sounds, it takes a screen shot. Hitting this option will take a capture of the screen in about half a second.

    It also includes toggles for Airplane Mode, Silent Mode, and Profiles. Configuring what shows up in the Power Menu can be configured at:

    Settings>System>Power Menu

    Options include:

    Reboot Menu
    Screenshot
    Profile Switcher
    Airplane Mode
    Sound Panel

    Status Bar Toggles = These can be seen by swiping your clock in the Navigation Bar, then tapping it again. It will rise up and show your currently enabled toggles.

    These can be configured at:

    Settings>System>Notification Drawer

    Options include:

    Airplane Mode
    Orientation
    Bluetooth (on/off)
    GPS (on/off)
    Wi-Fi (on/off)
    LED Flashlight (we don't have a flash, non functional)
    Mobile Data (we don't have a cell modem, non functional)
    2G/3G (we don't have a cell modem, non functional, however is to conserve battery)
    Sound
    Widget Button Order

    Widget Button Order is the sub menu to further configure the toggles, to the left is an arrow type icon, pulling this up or down will move this up or down in the toggle list as you see it. It will only allow you to manage currently enabled toggles from the previous menu.

    Status Bar = Tweaks and mods to what you see on your navigation bar at all times, like your clock, battery icon, etc.

    These options can be configured at:

    Settings>System>Status Bar

    Show Clock (on/off) disables if unchecked, or enables if checked, the clock)
    AM/PM Style (sub menu allows Normal, Small, None, which is default)
    Auto Hide (allows the navigation bar to "hide" on full screen applications such as Movies or Games, currently non functional)
    Battery Status Style (sub menu, allows various types of icon to be used)
    Show Notification Count (allows a number to show how many of a given notification you have, IE 3 unread Gmail notifications will display a small 3 on it)

    Wallpaper = Same as choosing wallpaper in your launcher, allows setting of a wallpaper on your desktop.

    Font Size = Handy for those with less then perfect vision, or those who have overly perfect vision, you can attempt to adjust font sizes here, range from Small to Huge. Normal is default here.

    Hardware Keys = This is I think meant for hardware keys such as phones usually have. Its limited use on tablets as most don't have a home key let alone anything else. It does, however, allow you to force the 3 dot menu key in your navigation bar. If functional, these options allow you to set sub actions for long pressing a given button, such as holding Home could open menu, or launch voice search, etc. Must be checked before any options can be set.

    Software:

    CM File Manager
    Now includes the rather nicely working CM File Manager (called File Manager in your app drawer) and starts in a basic "safe" mode, which only browses your internal SD card. It does allow up to a full Root level, which allows Read/Write of all areas of the device including /system. Be careful here. Also includes a text editor, which is quite decent. Allows for more control over permissions then ES File Manger as it can also change Ownership. This is installed in /system/app and requires a root explorer or other root application to remove (uninstall).

    DSP Manager
    Included in CM ROMs for as long as I can recall (CM7 actually) this app allows you to tweak a few things for audio. It allows you to change on a per output level, meaning settings are separate for Speakers, Headphones and Bluetooth. Jacking up the bass in Headphone will not affect the bass in Speakers, etc. Includes presets, EQ for fine tuning, all around decent EQ style application. This is installed in /system/app and requires a root explorer or other root application to remove (uninstall).

    CM Updater
    Useless for us as we are unofficial, what this should be doing is notifying us of updates for our device. As I build them, this is non functional and can safely be removed. This is installed in /system/app and requires a root explorer or other root application to remove (uninstall).

    This concludes (for now) the CM10 ROM coverage.
    Last edited by pio_masaki; 01-03-2013 at 10:42 PM.
    JB/ICS OC Kernels | My ROMs section | TWRP Recovery for Thrive
    CM10 General Thread | Jelly Bean Guide
    Donations, always appreciated!
    Need a rollback or reflash? Just send a PM!

  2. Ads


  3. #2
    Developer

    Member #
    18359
    Join Date
    Sep 2012
    Location
    Surprise, Az (that's a real place)
    Posts
    3,752
    Liked
    1894 times
    Twitter
    piomasaki
    Part Two: Black Bean

    Based on CM10 sources, this also brings in modifications from other places, such as AOKP, as well as some of their own. Most notably, the ROM is themed in Black. If you don't like a back ROM, stay away. If you don't mind black and want a bit more features then CM10 offers, give this one a try.

    Theme

    Right off you'll notice a few changes to the visuals of the ROM vs any other ROM you've run on the Thrive. The Navigation buttons (home, back, recents) are changed to a two part blue/white icon set, and the backgrounds of all UI elements is black. It does contain the Theme engine, so this can be changed if you wish.

    Settings
    This is where we begin to differ in the amount of things you can change in this ROM vs CM10.

    Where in CM10 you would see Settings>System, you'll see that is removed and instead you'll see BAKED Rom Control.

    Rom Control
    Grab a coffee, we have a lot to cover here.

    About Team BAKED (shows you information about the team behind Black Bean, such as website, source, IRC and the developers themselves)

    Control CPU
    (this will trigger a SU prompt)

    CPU Settings = Works like an OC app, allows you to change to frequencies the kernel can use, Governor and Scheduler used. Use caution here, and only toggle Set On Boot after testing the settings.

    Voltage Settings = Not available on our device kernel.

    Other Settings = Allows control over various other aspects of your device hardware, not for fiddling without a backup handy

    Free Memory = Sets when to start purging memory, default is 80. Raising this up to higher numbers will begin to result in slowdowns in multi tasking as the apps need to reload more often. Find the balance that works for you. Set at Boot to set this number for every boot.

    Fast Charge = Unsupported on our device kernel.

    Propmodder/Init.D = Allows changes to various startup variables in build.prop and init.d scripts, use caution here.

    Show Build.prop = as it says, displays your build.prop

    WiFi scan interval = setting this to a higher number will save battery, but may slow down WiFi catching signals. 150 is usually an acceptable middle.

    Window Manager max events per second = How much can you do at once? This will allow more of it to happen. 240 is about as high as you want to go.

    Telephone ringer delay = Not used on our device

    Dalvik Heap size = default is 256, while you can change this to a higher number, it won't do much on our 1GB of RAM and may cause OOM issues.

    HSUPA upload speed hack = Not used on our device

    Proximity sensor delay = Not used on our device

    Change your Build Number = If you don't want the build number you have, you can change it here, no real reason to, though.

    PM Sleep Mode = I'm not sure what this is for, however I think its how it sleeps during the night, IE it can possibly cause wake locks.

    Optimize TCP Stack = Supposedly offers better performance for internet usage, Check to enable, uncheck to disable (default is unchecked/off)

    Check in service = Disables Android's calling home to Google. Check disables this, unchecked leaves it alone. Default is unchecked/calls home.

    3G Speed hack = Not used on our device

    GPU Acceleration = Enables the GPU to render the UI, known as Project Butter. Check to enable, uncheck to disable. Default is checked/enabled.

    SDcard speed hack = Allows you to set the read ahead cache, much higher then 4096 is wasted, experiment with this number, 2048 works well and is default.

    Enable Start up Tweaks = As it sounds, checking this enabled the following tweaks to be active. Useful if you enable one but don't know which is causing problems. Default is checked/enabled

    Disable Logcat = like it sounds, this disables the logcat from running. This saves resources, but makes debugging impossible. If you don't logcat, disable it. Checked is disabled, unchecked is enabled. Default is unchecked/enabled.

    Zipalign APKs = optimizes the apk files (your apps which are basically zip files) for faster loading. Checked is enabled, unchecked is disabled. Default is checked/enabled.

    Fix Permissions = As it sounds, it runs a permissions repair each boot. This is normally not needed and slows down booting. Checked for enabled, unchecked for disabled. Default is unchecked/disabled.

    Clear Cache = As it sounds, this will clear the cache each boot. This is drastically increase boot time as it will reload the cache every boot. Checked for enabled, unchecked for disabled. Default is unchecked/disabled.

    Enable sysctl = Allows sysctl scripts/functions to be run. These mostly reside in scripts in init.d. Checked is enabled, unchecked is disabled. Default is checked/enabled.

    Enable Scheduled tasks = Sounds like it is, this allows cron jobs to run, meaning scripts that fire at certain times. Checked is enabled, unchecked is disabled. Default is checked/enabled.

    Sound = Some extra sound settings.

    Headphones plugged in action = sets a function when you plug in a set of headphones as far as notifications go. It can be set for None, silent or vibrate. None is default.

    Bluetooth A2DP connected action = same as heaphones, allows you to set what happens when these connect. None is default.

    Face down audio mode = same as the previous two settings, what to do with notifications if the device detects it's laying face down.

    Power Menu = As in CM10 there are power menu changes, however couple more are added, which I will cover only the additional options.

    Show Expanded desktop Toggle = unlike the hide bar option in CM10, this is a manual hiding of the navigation bar. Excellent for watching movies or playing games so you don't hit the buttons while playing. Holding power will allow you to toggle it back to visable.

    Show Navivation bar toggle = offers the ability to use navigation bar buttons from the power menu. Useful if you have desktop expanded but only need to hit back and choose another movie to watch, for example.

    Show vibrate/sound chooser = a toggle to switch between sound modes, vibration and normal sound settings. Useless as we have no vibration at this time.

    Nav Bar = Various changes to the navigation bar such as colors, animation and long press functions.

    (not even a third of the way through ROM control and my face is hurting, I'll continue this later)
    Last edited by pio_masaki; 01-03-2013 at 11:32 PM.
    JB/ICS OC Kernels | My ROMs section | TWRP Recovery for Thrive
    CM10 General Thread | Jelly Bean Guide
    Donations, always appreciated!
    Need a rollback or reflash? Just send a PM!

  4. #3
    Developer

    Member #
    18359
    Join Date
    Sep 2012
    Location
    Surprise, Az (that's a real place)
    Posts
    3,752
    Liked
    1894 times
    Twitter
    piomasaki
    Part Three: Paranoid Android

    This ROM is currently also based on CM10, however there has been talk of it being moved over to AOSP instead. The build currently available is based on CM10 source.

    (gonna flash this to give a walkthrough, will not be completed tonight)
    Last edited by pio_masaki; 01-03-2013 at 10:46 PM.
    JB/ICS OC Kernels | My ROMs section | TWRP Recovery for Thrive
    CM10 General Thread | Jelly Bean Guide
    Donations, always appreciated!
    Need a rollback or reflash? Just send a PM!

  5. #4
    Developer

    Member #
    18359
    Join Date
    Sep 2012
    Location
    Surprise, Az (that's a real place)
    Posts
    3,752
    Liked
    1894 times
    Twitter
    piomasaki
    Part Four: Kuroikaze Shinka

    A continuation of my CM10 work on the Iconia A100, this started as a type of preview build for the community to play with early in the project's life, and is what lead to the Unified Project as users became confused by multiple releases of the ROM with various fixes/breakages. It then became a test bed for my various Jelly Bean builds, like Black Bean and Paranoid Android. Shinka marked the new coming of the ROM, based soley on CM10, as originally intended, it's the pinacle of my modding abilities. Built using the Linaro 4.7 toolchain and containing various other tweaks for improved performance and audio, it pushes the thrive about as far as I can currently achieve with my skills.

    Most of the changes are under the hood, though some are apparent otherwise.

    What makes this different from a normal CM10 build = Aside from under the hood changes like linaro and flags for it, you may notice a few changes.

    Software
    CM Updater is removed
    Acid Audio is added
    Dolby is added
    Awesome Beats is added
    Various files included for sony, xplod, beats to function
    Various lines added to build.prop to utilize these files and options
    Seeder Entropy is added, binary install with init.d script used to call it.

    Under the hood
    Linaro Toolchain 4.7 is used to build both the kernel and the ROM
    Kernel and ROM both use -O3 flags
    Kernel and ROM both use strict-aliasing
    Various other tweaks and flags used for optimizing the builds
    Slight changes to dalvik memory
    Changes to OOM and memory handling
    Decreased (eliminated?) EGL OOM errors

    Other options are still present in the CM10 outline in Part One.
    Last edited by pio_masaki; 01-03-2013 at 10:57 PM.
    JB/ICS OC Kernels | My ROMs section | TWRP Recovery for Thrive
    CM10 General Thread | Jelly Bean Guide
    Donations, always appreciated!
    Need a rollback or reflash? Just send a PM!

  6. #5
    Developer

    Member #
    18359
    Join Date
    Sep 2012
    Location
    Surprise, Az (that's a real place)
    Posts
    3,752
    Liked
    1894 times
    Twitter
    piomasaki
    beyond all comprehension now
    bluezr1, mrbcx and JiveTurkee like this.
    JB/ICS OC Kernels | My ROMs section | TWRP Recovery for Thrive
    CM10 General Thread | Jelly Bean Guide
    Donations, always appreciated!
    Need a rollback or reflash? Just send a PM!

  7. #6
    Thrive Conveyor
    Member #
    3387
    Join Date
    Sep 2011
    Location
    Surprise, AZ
    Posts
    383
    Liked
    35 times
    U da man pio
    THRiVE 16gb
    CM10 Jellybean 4.1.2 (built from source with pio_masaki's trees and kernel)
    TWRP Recovery (built by pio_masaki)
    GL2SD
    128gb Lexar 400x UHS-i Class 10 SDXC Card

  8. #7
    Thrive Operative
    Member #
    10088
    Join Date
    Jan 2012
    Posts
    152
    Liked
    15 times
    Quote Originally Posted by dandroid7 View Post
    U da man pio

    You are a legend Pio, nice and easy to understand. Well done. Now to read it again!!.

    Cheers


    I suppose the question will be asked, which is the fastest.
    Last edited by ajsbonneville; 01-04-2013 at 12:14 AM.

  9. #8
    Thrive Lurker
    Member #
    20319
    Join Date
    Dec 2012
    Posts
    22
    Liked
    0 times
    thank you pio great guide

  10. #9
    Thrive Operative
    Member #
    5021
    Join Date
    Nov 2011
    Location
    Sacramento, CA
    Posts
    131
    Liked
    31 times
    Thanks Pio, I know how much effort you must put into that. I had to write guides for end users in a previous life!

  11. #10
    Thrive Informant
    Member #
    15329
    Join Date
    Jun 2012
    Posts
    70
    Liked
    9 times

    Re: [Guide] Your walkthrough of Jelly Bean ROMs for the Thrive 10"

    Well pio I didn't quite understand..........lol. Thank you, it begins to be remarkable and gigantic the effort and time that you have gave to this forum that really we must consider giving a name after you. I really look up to you, bless you and your family.

    Sent from my AT100 using Tapatalk 2


 
+ Reply to Thread
Page 1 of 6 1 2 3 ... LastLast


Ads

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts

Search tags for this page

how to install jelly bean on toshiba thrive
,
how to update toshiba thrive to jelly bean
,
how to upgrade toshiba thrive to jelly bean
,

jelly bean for toshiba thrive

,
jelly bean toshiba thrive
,
jellybean for thrive
,
toshiba thrive cyanogenmod
,
toshiba thrive jb rom
,

toshiba thrive jelly bean

,
toshiba thrive jelly bean download
,

toshiba thrive jelly bean rom

,

toshiba thrive jelly bean update

,
toshiba thrive jelly bean upgrade
,
toshiba thrive roms
,
toshiba thrive upgrade to jelly bean
Click on a term to search our site for related topics.