[ROM] Jellytime Sosei 4.3

Search This thread

billypoke

Senior Member
May 4, 2011
198
60
Durham, NC
If someone screws this up...
 

Attachments

  • christian_bale_american_psycho_patrick_bateman_axe_10989289_RE_PwnzElite_has_declared_war_on_Gra.jpg
    christian_bale_american_psycho_patrick_bateman_axe_10989289_RE_PwnzElite_has_declared_war_on_Gra.jpg
    35.7 KB · Views: 281

hardslog

Inactive Recognized Contributor
Nov 17, 2009
1,724
2,103
So far so good. Loaded all my apps and this seems more stable than the 0904 WDS built. Pio, you are a rock star!

Sent from my A100 using xda app-developers app
 

nickownzya

Senior Member
Aug 20, 2010
236
59
Really nice work, Pio!
So far no issues found, beside the lockscreen's not rotating.

Thanks a lot:)
 

das_webos_transformer

Senior Member
Feb 3, 2012
1,150
317
So, when can I expect to be able to shoot a lazzzer from my power button? Lol

This has just fifteen priority over the new halo.

Results.
(Insert results here)

Sent from my A100 using xda premium
 

tony_2018

Senior Member
Aug 17, 2009
59
3
Can we run flash video from web browser with this ROM. I'm not seeing if this build supports flash or not.
 

justjackyl

Senior Member
Jul 28, 2012
1,539
565
Can we run flash video from web browser with this ROM. I'm not seeing if this build supports flash or not.

I restored Flash from a previous backup.
I am able to watch Youtube and Netflix, as well as watch Youtube from the browser. (Not just the YT app.)
I dunno if that info helps or not.
 

pio_masaki

Senior Member
May 7, 2012
4,577
3,651
Surprise, Az
Can we run flash video from web browser with this ROM. I'm not seeing if this build supports flash or not.

Sigh...jellybean does NOT support flash. This is googles choice not mine. That said, flash does generally work just don't expect it to be 100% bug free, considering it never was on any android version even when it was supported.

Tapatalked from my Nexus 7 - Kuroikaze AOSP
 
  • Like
Reactions: StonedYoda

justjackyl

Senior Member
Jul 28, 2012
1,539
565
Sigh...jellybean does NOT support flash. This is googles choice not mine. That said, flash does generally work just don't expect it to be 100% bug free, considering it never was on any android version even when it was supported.

Tapatalked from my Nexus 7 - Kuroikaze AOSP

Well if I didn't just fail pio.
I mean I knew that, but I was thinking on the lines of sideloading flash via titanium backup.
That's how I do it anyways.
Isn't everything going to HTML5 anyways?

G2x-temasek CM7 build135.4 w/faux 054 kernel
 

pio_masaki

Senior Member
May 7, 2012
4,577
3,651
Surprise, Az
Well if I didn't just fail pio.
I mean I knew that, but I was thinking on the lines of sideloading flash via titanium backup.
That's how I do it anyways.
Isn't everything going to HTML5 anyways?

G2x-temasek CM7 build135.4 w/faux 054 kernel

Html5 is supposedly the future yeah.

Didn't fail me, just want it clear its unsupported to use flash on jellybean.

Sent from my Galaxy Nexus using Tapatalk 2
 

hardslog

Inactive Recognized Contributor
Nov 17, 2009
1,724
2,103
If you don't have it backed up you can still also get the latest version of android flash from the adobe website. You have to search pretty hard but it is there.

Flash works for me but you cant use dolphin browser for it either even if you do have flash installed.

Sent from my A100 using xda app-developers app
 

littleemp

Senior Member
May 18, 2011
271
50
Does the kernel have the fix to avoid eMMC bricking like the godmachine/linuxsociety does? Just curious.
 

littleemp

Senior Member
May 18, 2011
271
50
You mean the fix for Samsung devices that has nothing to do with us? No. Its a stock cm9 kernel, figure if you want to use another kernel you'll flash it lol

Sent from my Galaxy Nexus using Tapatalk 2

Well this build is as smooth as a greased stripper pole, so I'm not messing with it just yet. I am trying to find the line to switch back to 7" UI n the build.prop and I'm coming up empty handed, is it safe to assume I can overwrite one of the old build.props with the current one to trigger it?
 

justjackyl

Senior Member
Jul 28, 2012
1,539
565
Well this build is as smooth as a greased stripper pole, so I'm not messing with it just yet. I am trying to find the line to switch back to 7" UI n the build.prop and I'm coming up empty handed, is it safe to assume I can overwrite one of the old build.props with the current one to trigger it?

If you flashed this rom than you cannot drop into phab mode.
If pio kept it the same as the test build, it only had tabui or phabui overlays, but not both.
The switchable overlay was a waydownsouth's addition and is available in the 9-2-12 cm 4.1.1 build.

G2x-temasek CM7 build135.4 w/faux 054 kernel
 

pio_masaki

Senior Member
May 7, 2012
4,577
3,651
Surprise, Az
No its one or the other with mine, wds never shared that one. Its literally forced in the source to always be tablet ui. I can build a normal phablet ui as well but that's 6 hours per release in build time.

Sent from my Galaxy Nexus using Tapatalk 2
 

littleemp

Senior Member
May 18, 2011
271
50
No its one or the other with mine, wds never shared that one. Its literally forced in the source to always be tablet ui. I can build a normal phablet ui as well but that's 6 hours per release in build time.

Sent from my Galaxy Nexus using Tapatalk 2

Roger that.

I've gotten used to the customizable toggles in phones and seeing that Google apparently dropped the old Tablet UI completely in 4.2, I figured I might get reacquainted with it in my tablet before the source is released.
 

das_webos_transformer

Senior Member
Feb 3, 2012
1,150
317
I'd be down for a phablet build. I think it feels natural.

Also this build is awesome, better keyboard, smoother and minimal bugs. I think then lock screen is off. Has anyone tried the 4.2 apps yet?

Sent from my A100 using xda premium
 

Top Liked Posts

  • There are no posts matching your filters.
  • 85
    After the rather...disappointing way I departed and the resulting issues, I'm setting some things straight here and now.

    1. No ETAs. Period. I don't want to see when will I fix or add anything.

    2. No complaining. There's a line between reporting an issue and complaining. This line is crossed when it's reported more then once.

    3. Requesting additions is fine, within reason. Keep it within reason, I'm not a real dev.

    4. Using this ROM...this is where a lot of issues have come up, generally speaking, you can use this ROM as a base if you choose, however ASK ME FIRST. That's it! Everything could have been avoided if people had simply asked me before using my ROM and slapping their names on it then putting it out there. Please include some credit to waydownsouth, gh123man, randomblame and myself. For 4.3 Jellytime, randomblame in particular.

    5. Hosting/mirroring. Please don't host or mirror this elsewhere, I will supply hosts for this ROM, I don't need more, and I prefer to keep track of how many users of a given build I have. Hosting elsewhere interferes with this. The only exception I can see is for our Russian/Ukrainian user community, my hosts may be slow there, or in other parts of the world. If you wish to host for another country, please let me know.

    6. READ. For the love of all that is holy and great, READ the OPs, read at least the page before where your post will be. I will not answer questions already answered. If I respond, it may not be the nicest way I could do so. Please, save me, yourself, and everyone else the time and /facepalming and at least attempt to find the answer on your own. This is not limited to only this ROM, but anything you may wish to post about in this thread. Questions about CWM or TWRP don't belong here, but if they are valid questions that have something to do with this ROM, go ahead, after reading up on it.

    7. Remaining on topic....well this one is loose. I prefer it to stay related only to this ROM, however I know things stray, and generally I'm OK with this, just try to keep it at least related to android. Or at least something related to something to do with on this planet.

    Features:
    Halo
    PIE
    Listview Animations (settings>display)
    System Settings (CM)

    Screenies:
    40
    Builds
    Jellybean 4.1
    Build 1 | Mirror
    Kuroikaze-Sosei RC1
    Kuroikaze-Sosei II B3 Final

    Jellybean 4.3
    Jellytime 4.3 - AFH | Jellytime 4.3 - DH

    Gapps 4.1
    http://goo.im/gapps/gapps-jb-20121011-signed.zip

    Gapps 4.3
    gapps-jb-20130813-signed.zip



    Change log 4.1
    Build 1: Updated to 4.1.2 sources. Generally stock CM10. Everything works. I think.

    RC1: Based on Black Bean AOSP sources now.

    Sosei II B3 Final:

    Seeder
    AC!D audio
    XLoud
    Supercharged
    Die Hard launcher
    init.d memory tweaks
    time killer killer mod
    maximum overdrive mod
    service preserver
    transition animations

    Final release.

    Change log 4.3
    Ported from Randomblame's Jellytime Build 7
    Build 1: Unreleased, initial trials to get it running. Bootloops.
    Build 2: Unreleased, boots, but runs badly, storage is broken, audio stutters
    Build 3: Almost everything works now, fixed storage via init/ramdisk entries


    FULL WIPE NO MATTER WHAT
    Broken in 4.1
    RC1 -
    Auto Brightness
    Hardware Rotation Lock Switch (use software settings, it's more flexible anyways)
    GPS

    Fixed -
    HDMI audio should now work (again)
    Switchable UI (tab or phab UIs now)

    Bugs-
    In tab ui the clock is messing it's rear texture on the homescreen, ie its not black there, its wallpaper instead. Doesn't interfere with anything, just a glitch.

    Huge thanks to justjackyl for testing this out for me and reporting back on issues.

    FULL WIPE NO MATTER WHAT
    Broken in 4.3
    Mic
    ?

    Untested:
    GPS
    HDMI
    Bluetooth
    Dock

    Bugs:
    WiFi will not reconnect if it turns off, a reboot is needed. Turning off the always scanning option seems to help this.
    Forcing GPU acceleration can help even out the framerate in some cases.

    4.1 Instructions:
    Root and unlock your device, if you haven't, visit the All things Iconia A100 link in my sig, and read up. Then read again. Then proceed with rooting, unlocking, and installing a custom recovery.

    I'm not going to note each recovery's method of installation, hopefully by now you guys know what to do in your recovery of choice.

    Download the ROM to external SD
    Download a current GApps package to your external SD card. Get one for JB, you can try a 4.2 package, but is as yet unsupported.
    Reboot into recovery using whatever method you like:
    -Power off then power on holding volume -
    -Power menu>reboot>recovery if your ROM supports this
    -App from the Play store reboot recovery
    Full nandroid backup
    FULL WIPE
    -Factory reset
    -Wipe System
    -Wipe Dalvik
    -Wipe Cache
    Flash ROM (install from zip)
    Flash appropriate GApps zip
    Reboot system
    Let system boot, allow up to 10 minutes for the GUI to come up from the boot animation
    After the welcome setup wizard appears, let the tab sit for 10 minutes. Longer is fine.
    Reboot tablet
    Let sit 5 more minutes
    Complete the setup wizard
    Restore apps and whatever. Do not restore system apps and/or data
    Restore user app data if you wish, but it may cause issues. If problems come up, factory reset and try again without restoring data.

    Feel free to flash any kernel you want, but don't post about problems here until you use the kernel it came with first.

    4.3 Instructions:
    Root and unlock your device, if you haven't, visit the All things Iconia A100 link in my sig, and read up. Then read again. Then proceed with rooting, unlocking, and installing a custom recovery.

    I'm not going to note each recovery's method of installation, hopefully by now you guys know what to do in your recovery of choice.

    Download the ROM to external SD
    Download a current GApps package to your external SD card. 4.3 ONLY! Don't report anything if you use anything but the gapps I linked from my site.
    Reboot into recovery using whatever method you like:
    -Power off then power on holding volume -
    -Power menu>reboot>recovery if your ROM supports this
    -App from the Play store reboot recovery
    Full nandroid backup
    FULL WIPE Don't report ANYTHING if you did not flash 100% clean!
    -Factory reset
    -Wipe System
    -Wipe Dalvik
    -Wipe Cache
    Flash ROM (install from zip)
    Flash appropriate GApps zip
    Reboot system
    Let system boot, allow up to 10 minutes for the GUI to come up from the boot animation. It may blank out for awhile on the first boot, just leave it be.
    After the welcome setup wizard appears, let the tab sit for 10 minutes. Longer is fine.
    Reboot tablet
    Let sit 5 more minutes
    Complete the setup wizard

    I strongly recommend you download and install apps FRESH from the Play Store, and do NOT restore apps if possible. If you want, then go ahead...
    Restore apps and whatever. Do not restore system apps and/or data
    Restore user app data if you wish, but it may cause issues. If problems come up, factory reset and try again without restoring data.

    Do not report any issues if you:
    Dirty flashed.
    Restored anything with any app.
    Don't use the supplied kernel.
    Modified the ROM in any way prior to the issue coming up.
    Did not read the entire post and noted what bugs are already known to exist.
    Did not use the 4.3 GApps on my site which I linked right below the ROM download.
    Can not report a bug issue without quoting Hawkeye because you skipped all of this.


    Thanks:
    waydownsouth
    randomblame
    gh123man
    godmachine / linux society
    justjackyl
    das_webos_transformer / xbooow
    Cyanogenmod
    AOKP
    Team Baked
    The Team behind the AC!D audio engine
    Plus more, I'm sure.
    12
    RC1 is up

    Ok guys go grab Kuroikaze-Sosei RC1

    Notes:
    Based in Black Bean AOSP Source now, Jellytime was always an AOSP rom except for the last one, that was CM10 and was more of a holder until I worked this one out.

    This is still of course built from source for our devices (I don't port stuff :victory:) and should offer enough options and customizations to keep you guys happy for awhile.

    Highlights:

    Uses Black Bean sources now, which itself has AOKP and CM10 and I'm sure other sources, its a little bit of everything.

    CM9 kernel as usual for its proven reliability and stability. Works with GM's kernels as usual.

    HDMI Audio should now be working

    Switchable UIs

    Fast as hell and slicker then...yeah. Should work with any JB Gapps.

    Check the second post for more info on the changes.
    8
    Not secretly, no, I had setup the laptop to work on cm10 a bit and just built a couple new cm10s for you guys. Updating black bean too so this one may also get updated soon.

    Sent from my HTC DNA
    8
    Updated OP.

    Tapatalked from my Nexus 7 - Kuroikaze AOSP