[ROM 4.2.2] JELLYBAM - v6.4.0 [27/02/2013] [i717] [AOKP | CM10.1 | ParanoidAndroid
- Thread starter OPGT
- Start date
-
- Tags
- development
- Status
Do you have the link to the actual Baked Thread.. I wanna read thru it before flashing, Thank you..If you like inverted gapps, may I suggest BAKED
http://goo.im/devs/BAKED/gapps/gappsinverted-jb-20130118-signed.zip
I always stack 'em up in TWRP -- one quick install:
then wipe cache & dalvik after install
- jellybam-v6.4.0_quincyatt-STABLE.zip
- h0tcakez-JB-4.2.2-Kernel-v3.1.0.zip
- gappsinverted-jb-20130118-signed.zip
I have had zero issues with this method.
---------- Post added at 02:22 PM ---------- Previous post was at 02:17 PM ----------
By USB storage I mean sometimes when my phone boots up I can't access my internal memory, gallery, camera, or files stored there.. It's not mounted.. A couple reboots always fixes it tho..
This is an amazing Rom! I loaded it last night and was immediately blown away by the boot animation to start although I get a white flashing screen toward the end of the Boot animation (anyone Else?) I've been using this fairly heavy today and the battery life is great. a link the the Baked Gapps would be a good read but I'm still trying to get used to all the options available with this Bad Ass Rom.. Great work
There is no Baked thread for our device, you'll just have to search around...
(TeamBaked makes fantastic ROMs for other devices)
The very best inverted stuff comes from travp624 and b-boy over at RootzWiki (in my opinion)
I know how to stop that flickering when browsing the homescreens without Disabling HW overlay. For me it had something to do with the Nav bar. When I set the nav bar to "0" In Paranoid preferences, thats when the flicker would occur, and when I set the nav bar back to "100" it would go away. So if you've taken off the navbar that may be the problem. If you enable PIE, the flicker should stop. (you dont necessarily have to use PIE, just enable it in the settings.)
Has anyone been looking at the new ROM Controls igio has been showing on F/B? Going to be very nice and so much cleaner. He's hinting that it may be ready Sunday!
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
I'm not getting any flicker at all with this build...I didnt get it on stock kernel, I didnt get it on 4Aces, and I dont get it on Flapps 3.10 not sure why some people are. I also did a clean install of 6.4.0 instead of dirty flashing.
I understand that. But I always clean wipe, and have used all the kernels listed and it still happens to me WHEN I take off the nav bar. and the flicker only happens when I scroll through homescreens. Like I said I isolated it to the nav bar, because it only happens when I turn it off. It may just not play well with some peoples phones, but I've since fixed the problem. So no biggie. Just posted my solution for people who experienced it as well, and I'm guessing I helped at least one person.
The answer to this is in the OP. It's in the FAQ section. To save you some trouble it says "How can I solve the android.process.acore error?" : Go into Settings/Applications/Contacts - Delete data , but next time do a little digging man:good:
Thanks. I Google it after i posted the question.
Sent from my SAMSUNG-SGH-I717 using XDA Premium HD app
Google Play Music stopped working
So all was well with 6.4.0 with the stock kernel for a whole day. I was able to play local music on google play music without editing the build.prop. I was pretty excited. But that went kapoooey today (wouldn't play any songs). So I edited my build.prop and that didn't fix it (like it did in 4.1.0). So I may try to flash an alternate kernel to see if it fixes this. For now I am back to the AT&T ICS release. Isn't TWRP great (its just like changing clothes)?
So all was well with 6.4.0 with the stock kernel for a whole day. I was able to play local music on google play music without editing the build.prop. I was pretty excited. But that went kapoooey today (wouldn't play any songs). So I edited my build.prop and that didn't fix it (like it did in 4.1.0). So I may try to flash an alternate kernel to see if it fixes this. For now I am back to the AT&T ICS release. Isn't TWRP great (its just like changing clothes)?
- Status
Similar threads
- Locked
- Locked
Top Liked Posts
-
There are no posts matching your filters.
-
31ISources: https://github.com/jellybam & https://github.com/igio90 & github.com/cyanogenmod :Sources
First Off, Credit goes to iGio90. This is no means my rom and i'm aloud to post this ROM according to this
and give credit where due. On the OFFICAL FaceBook page.
Want to Donate?
FEATURES
BUGS
Downloads & Installation
download JellyBam Mod Edit
Wipe data
wipe cache & dalvik cache
Flash ROM
Reboot
Enjoy
FAQ
***ChangeLog 27/02/2013
**again all credit goes to iGio90 who developed the ROM**
Credits
Chris41g
AOKP team
Cyanogenmod Team
Paranoid Android Team
Carbon Team
PAC-Man Team
Paintball2345 For helping out on this thread10Just a quick off topic FYI. For any new members that may not know. If you see members that continually are making non-helpful or sarcastic comments and you don't wish to see them anymore.
Go to the forum on your PC...click on the offending members screen name...you will get a dropdown menu. One option will be to add to your ignore list. Click on that and you will never see another post from that person.:laugh:10Re: [ROM 4.2.2] JELLYBAM - v6.3.0 [24/02/2013] [i717] [AOKP | CM10.1 | ParanoidAndroi
Everyone in this thread is reporting a legitimate issur with this rom. They are rightfully upset tbat a reportedly stable rom was released which is obviously not stable. That being said: igio stated he would not be creating an official Jellybam thread on xda and had no issues of another member creating one given proper credit was posted. This thread is being used to improve developement of this rom and inform others of the issues present with the current release. There is no reason to be defensive nor to report this thread.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 27
We can't action what we don't know is going on. Contrary to popular opinion, we don't read every post on every thread. If you see something, Report it. That is why that button is there.
Someone did hit the Report button, hence why I am here now.
Cleaned.
******************
Obviously there is a problem with screen flickering.(?) Maybe some logcats or someone tearing the ROM down would help resolve the situation. If you can't do that, then just have to be patient until someone else can/does. This is why we have "Flash at your own risk" and "Make a Nandroid" in almost every Dev thread.
We know the inherent risks, but we still push that install button don't we. Plesae be mindful that there are issues with this ROM and it is a flash-at-your-own-risk type thing.
