yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy Note I717] Adizzzle:
Re: [ROM 4.2.2] JELLYBAM - v6.3.0 [24/02/2013] [i717] [AOKP | CM10.1 | ParanoidAndroi

Well in my opinion, it would be in all our best interest to put our brains together (if you guys want to find a fix) and try and figure out this silly flickering issue on our own. :)

iGio90 asked me to test a different kernel, but as I had mentioned before, the ones I tested didn't work for me at all.

Does anyone have any other suggestions as to how we can get the silly flickering gone for good?

:beer:"We can't stop here! This is Bat Country":beer:
[AT&T Samsung Galaxy Note I717] dparrothead1:
Wish I had and idea. I tried everything to get a clean flash. I wiped everything 3 times and hit fix permissions before rebooting. Reflashed the rom twice. Mine is more than just simple screen flicker. Mine flashed screen to black continuously. Flashing just llke the boot screen except back instead of white. Unable to even set it up properly or get to settings.

Just for FYI. Igio has a F/B page for JellyBAM Official Rom and there is one post to list your problems. You should show your device/problem. If he is as responsive as he was with 6.1, maybe we will see a fix tomorrow or the next day. Fingers crossed.
[AT&T Samsung Galaxy Note I717] ZacksBuilds:
Re: [ROM 4.2.2] JELLYBAM - v6.3.0 [24/02/2013] [i717] [AOKP | CM10.1 | ParanoidAndroi

Would it have something to do with force closing pur the screen locking and unlocking and skipping the lockscreen really fast I don't know just throwing things out there. :o
[AT&T Samsung Galaxy Note I717] chappatti:
Here is a more detailed method for fixing screen flicker by editing build prop. I am on another ROM, but if anyone volunteers it looks straightforward. My Goo.im download is running EXTREMELY slowly, so I have to wait to flash.

http://xdaforums.com/showthread.php?t=1904827
[AT&T Samsung Galaxy Note I717] rquiett:
I am on a different cm 10.1 based rom and can tell you I had the screen flicker issue. It was to the point it bothered me and the fix I was given by another member here was to change the debug.mdpcomp max layer that was at 3 to 2 in the build.prop since doing this I have not had a flicker yet. Of course reboot after making the change.
[AT&T Samsung Galaxy Note I717] unibomber:
That's to perm disable hw overlay since after reboot some dev options don't stick. I was searching and found the same fix. Thanks for the effort.
[AT&T Samsung Galaxy Note I717] kimtyson:
I set mine to 720x480 so as to take less screen realestate.

Agreed! however, if you do the Secondary Display "fix" you can at least get it to work enough to make it usable. This will allow for looking around the ROM.

God this thing is full of configs and tweaks. It's a flashaholics wet dream. Can't wait for it to actually work 100%... err 98%.

---------- Post added at 02:09 PM ---------- Previous post was at 01:57 PM ----------

Does anyone understand what the Secondary Display fix is doing under the hood? Since it seems to resolve the issue, we just need further understanding of what it does. Then maybe get rid of the dang second window on top of everything else.
[AT&T Samsung Galaxy Note I717] dparrothead1:
Just 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:
[AT&T Samsung Galaxy Note I717] kimtyson:
An odd thing. They have only posted the ROM on Goo. The other two links (Direct and Upload) do not have our ROM uploaded yet. Do you think maybe they were just looking for a couple of guinea pigs to test this thing?
[AT&T Samsung Galaxy Note I717] chappatti:
The Goo.im app on phone cannot find the Jellybam files, and just returns to menu. The website for Jellybam changed, and I think the gooim APP has the old website?
[AT&T Samsung Galaxy Note I717] pockets916:
Re: [ROM 4.2.2] JELLYBAM - v6.3.0 [24/02/2013] [i717] [AOKP | CM10.1 | ParanoidAndroi

There are so many options on this ROM its gonna be awesome once all the bugs get worked out
[AT&T Samsung Galaxy Note I717] roloracer:
Re: [ROM 4.2.2] JELLYBAM - v6.3.0 [24/02/2013] [i717] [AOKP | CM10.1 | ParanoidAndroi

Nice to see a thread in the Dev section is up, looking forward to try it.

RoloRacer on AOSPA Nexus 10
[AT&T Samsung Galaxy Note I717] kimtyson:
I just received a reply on the other (official Jellybam) site. This was an official release. They had trouble with the other two upload sites so that is why it is only on Goo. They will be providing support. Of course, they kind of have their hands full with so many devices, a new website, and a popular ROM. Patience will be a virtue here. I can't deal with it until it gets the screen flicker fixed so I am back to Flapps 4.2.2, which is pretty damn good.
[AT&T Samsung Galaxy Note I717] shayneflashindaily:
Re: [ROM 4.2.2] JELLYBAM - v6.3.0 [24/02/2013] [i717] [AOKP | CM10.1 | ParanoidAndroi

Alright not bothering with this if screen flicker is present. ... Jellybeer is da best.
[AT&T Samsung Galaxy Note I717] OPGT:
screen flickering isnt that bad for me?.. guess i got lucky...
[AT&T Samsung Galaxy Note I717] Teufel Hunden:
Re: [ROM 4.2.2] JELLYBAM - v6.3.0 [24/02/2013] [i717] [AOKP | CM10.1 | ParanoidAndroi

I was looking into this till I read that Only the OP has it running "ok"

1 out of....... Everyone.... Not the best of odds

Biggest dog on the block, NOTE!! 4.2.2 JB!
[AT&T Samsung Galaxy Note I717] ZacksBuilds:
Re: [ROM 4.2.2] JELLYBAM - v6.3.0 [24/02/2013] [i717] [AOKP | CM10.1 | ParanoidAndroi

Might flash this just to see the frequency of the screen flickers.. I'll report back.
[AT&T Samsung Galaxy Note I717] OPGT:
Re: [ROM 4.2.2] JELLYBAM - v6.3.0 [24/02/2013] [i717] [AOKP | CM10.1 | ParanoidAndroi

Yea idk... Wiped delvic/cache X2 wiped system and factory X2 then wiped caches again and booted up fine. I'll look into more...
[AT&T Samsung Galaxy Note I717] kimtyson:
All due respect to the OP but which is it, "Isn't that bad" or "booted up fine"?

Mine booted pretty well but I got the flicker. I assume you got flicker, too. Right?
[AT&T Samsung Galaxy Note I717] OPGT:
Its fine. I should have been more clear. I got it booted up and it does flicker, but not as bad as everyone else is saying. People are also getting just plain black screens.. I get an occasional flicker here and there, but thats just me.
[AT&T Samsung Galaxy Note I717] shayneflashindaily:
Re: [ROM 4.2.2] JELLYBAM - v6.3.0 [24/02/2013] [i717] [AOKP | CM10.1 | ParanoidAndroi

Yeeeeeah i had major flicker. .........i didnt even bother. Ill check back when this rom has its flicker fixed
[AT&T Samsung Galaxy Note I717] CB620:
Complete waste of time.

Every time i attempt to do something my screen blacks out.

You ask for testers for other builds but when it comes to the i717 users you turn down a helping hand.

This rom is useless.

Don't flash it.

Period.
[AT&T Samsung Galaxy Note I717] pTeronaut:
Agreed. Flicker so bad, that I couldn't get to settings to turn MTP on so that my PC could get at the build.prop, disabling HW overlays made the flickering worse.

I also have noticed, that they have made no attempt to correct the flicker in the boot animation either.
[AT&T Samsung Galaxy Note I717] dparrothead1:
Re: [ROM 4.2.2] JELLYBAM - v6.3.0 [24/02/2013] [i717] [AOKP | CM10.1 | ParanoidAndroi

Everyone needs to lighten up on the OP.....he didn't build this ROM.

OK, I finally used the fix and got the black flashing off.....except for that little overlay screen. But then I discovered all of my APN options were gone....so, no phone.

Right now, I'm back to Flapps latest build. Like I said before, igio responded quickly to the 6.1 bugs so hopefully he will do the same here.
[AT&T Samsung Galaxy Note I717] crutzulee:
I for one would like to thank the makers of jellybam for at least continuing to try and keep our phones current. Their 4.1.2 ROM has been my daily driver since it came out and it has been a very stable performer for me. It has put me in a position where I am in no great rush to upgrade.

I would also really like to thank the OP of this thread for providing a place for the brave early adopters of this new ROM to share their experiences so that guys like me can read about and decide whether or not to take the next leap. Thanks to all of you for sharing your experiences!!!!

But, I would like to reserve my biggest thanks for the Jimmy Buffet fan who finally showed me a way to eliminate the useless chatter of a couple of guys who seem to think they are self appointed mods. Jesus, the number of times I have wished for an unthanks button due to unhelpful finger wagging posts of these two magpies....PROBLEM SOLVED!!!!
[AT&T Samsung Galaxy Note I717] kimtyson:
Good post Crutzulee.

I am conflicted about this update. I'm really happy that they continue to work and share. At the same time I am a little sad\angry that they released something that is unusable due to the flicker. (And I don't even know what other issues there may be, if any, because it is next to impossible to use or test.) I do agree with the majority who believe we need to be patient and keep the faith.
[AT&T Samsung Galaxy Note I717] jshinn1:
Tried it loved all of the options so cant wait till the flicker issues are fixed seems like it wasnt to bad but as soon as you touch the screen....BOOOM flicker crazy lol great work though implementing all this stuff together I think its still amazing how they are supporting all these devices at once.
[AT&T Samsung Galaxy Note I717] unibomber:
The fact that from what I can see is 2 devs working on jellybam for like 15 phones is a feat in it self. I don't see why there is complaining. You try the ROM, it doesn't work, put the old one back on. That's what backup and restore is for.
[AT&T Samsung Galaxy Note I717] JEZZEJAMEZ:
Re: [ROM 4.2.2] JELLYBAM - v6.3.0 [24/02/2013] [i717] [AOKP | CM10.1 | ParanoidAndroi

X2, im late to party. Agree.. This is fixable. I was the second post and very first download, my download worked but flicker haha this was like blinking every second. ( not stable) but after combination of the few suggestions it's tolerable. I'm combing through trying things I will post back if some combination works.

Thanks op .

BlA¢K ★ X

$†@¢KH○u$€ ®€D
[AT&T Samsung Galaxy Note I717] OPGT:
Added Screenshots!!
[AT&T Samsung Galaxy Note I717] Teufel Hunden:
Re: [ROM 4.2.2] JELLYBAM - v6.3.0 [24/02/2013] [i717] [AOKP | CM10.1 | ParanoidAndroi

Looks great, now to get it running correctly

Biggest dog on the block, NOTE!! 4.2.2 JB!
[AT&T Samsung Galaxy Note I717] Bradl79:
They just used the wrong nightly they used 02/24 they should have just used the 02/21
[AT&T Samsung Galaxy Note I717] ZacksBuilds:
Re: [ROM 4.2.2] JELLYBAM - v6.3.0 [24/02/2013] [i717] [AOKP | CM10.1 | ParanoidAndroi

So the screen flicker should be fixed by tomorrow? Thank the lord! My jellybam Is back! :D
[AT&T Samsung Galaxy Note I717] chappatti:
Yup, I agree and noted that. I tried both on my CM ROM and clearly 2/24 and the experimental are bad news ...... 2/21 is highly recommended, indeed, also for people that have screen flicker on earlier versions. Other things like bluetooth, gps, audio are all excellent.!!:good:
[AT&T Samsung Galaxy Note I717] captemo:
my 2 cents

i have to agree with a select few....dparrothead and roloracer

just like the GB update for the infuse. people pushed and pushed until developers got tired of hearing all the crying and pushed it out ready or not. of course it was NOT. then everybody started *****ing because it sucked.

i have not flashed this yet because i consider myself possibly the wiser one here. all you that are gung ho, ready or not are going to provide me with all the information i need. what i have learned, without any frustrastions is that it is not quite ready. so i will wait.

every single rom on XDA and every single OP states "FLASH AT YOUR OWN RISK".

and you do. so dont immaturely whine and cry. these people are sacrificing their time and efforts to please all. which you can never please everybody. pleasing all for basically nothing. FOR FREE!

there may be a few, but honestly, how many of you actually donate to these people who sacrifice their efforts. more often than not, they are getting dumped on.

no wonder these folks leave.

again just my 2 cents. hope this get better because i have heard some great things about the 4.1.2 version which i WILL be flashing tomarrow.

FOKKER OUT!!!
[AT&T Samsung Galaxy Note I717] Adizzzle:
Re: [ROM 4.2.2] JELLYBAM - v6.3.0 [24/02/2013] [i717] [AOKP | CM10.1 | ParanoidAndroi

What a rant!

On a lighter note iGio will most definitely address this "flickering" issue its just a matter of when. To be honest, aside from the flickering this is a very stable ROM, and the amount of settings available is almost overwhelming! I'm still searching for a quick fix. Nothing yet. :P

:beer:"We can't stop here! This is Bat Country":beer:
[AT&T Samsung Galaxy Note I717] jshinn1:
Yea I noticed all of those settings were overwhelming
[AT&T Samsung Galaxy Note I717] ZacksBuilds:
Re: [ROM 4.2.2] JELLYBAM - v6.3.0 [24/02/2013] [i717] [AOKP | CM10.1 | ParanoidAndroi

Could the fix be just rolling back the Cm nightly to the 2/21 I think it is. Because from what I've heard that is the correct nightly they made a mistake and used the experimental nightly. Possible fix? :)
[AT&T Samsung Galaxy Note I717] chappatti:
@captemo : Okay. This is getting too much !!

1. Flashing this ROM does not kill your phone or anything like that. Don't make it out like flashing this is the most stupid thing you can do. Screen flickers, you cannot use it.... go back to your backup or previous ROM. Unlike others, I ACTUALLY FLASHED the ROM several times, fooled with it for several hours to try and make it usable for myself.

2. I tried it because I realise the dev has put in a lot of effort into it. AND, I got to see what this ROM can do, and I am impressed. Never would have known if I had not flashed.

3. EVERYBODY pushes for EVERY ROM..... This is not the first or last..... We are all just total nuts like that.

4. When there is such an obvious problem - the screen flickers like a strobe in a disco - for EVERYONE who flashes, one wonders that's all.

Yes, there are some folk who have a harsh way of saying things. Most of the folk are giving feedback, that the dev needs to now to fix this.
[AT&T Samsung Galaxy Note I717] Adizzzle:
Re: [ROM 4.2.2] JELLYBAM - v6.3.0 [24/02/2013] [i717] [AOKP | CM10.1 | ParanoidAndroi

This is what i will bring to iGio's attention on GTalk in the wee hours of the morning, considering there is a 9 hour difference in time between him and I. I'm sure it wont be that crazy hard of a fix so we may even see it as early as tomorrow. I definitely have my doubts though.

:beer:"We can't stop here! This is Bat Country":beer:
[AT&T Samsung Galaxy Note I717] dparrothead1:
Re: [ROM 4.2.2] JELLYBAM - v6.3.0 [24/02/2013] [i717] [AOKP | CM10.1 | ParanoidAndroi

Canada isn't near Italy???:rolleyes:
[AT&T Samsung Galaxy Note I717] cpgeek:
you mean Carbon Blue ;)

---------- Post added at 11:49 PM ---------- Previous post was at 11:45 PM ----------

I know I should be testing my own stuff and this request is probably found upon - but if there's any way I could convince one of you upstanding testers to do me a favor and pair a bluetooth keyboard or mouse and tell me if it works, it would be greatly appreciated. (i've been having all kinds of bluetooth hid related issues with 4.2.2 roms recently. I've yet to get my bluetooth keyboard or mouse working in a 4.2.2 rom, usually i can pair ok but then it simply doesn't work.

Thank you very much!
[AT&T Samsung Galaxy Note I717] dumbquestion:
tone. lots of promise in this ROM- look @ its pedigree... but the tone of our comments and sometimes the haste with which we offer them needs to be matured. We are (mostly) recipients of other's hard work and efforts. Our awareness of that should be evident in our correspondence.

This isn't directed @ you, dparrothead, but is meant as a reminder to any who feel frustrated with this release.

More on topic, I installed this ROM early today & have been messing with it all day long. I have read and posted over here and over there. I have tried all of the suggestions that have been proffered, but have not been able to overcome the screen flicker in an acceptable for daily-driver way. I am very encouraged and offer anything I can do to help. I will wait patiently for the opportunity to do so, or for an improved iteration. Thanx.
[AT&T Samsung Galaxy Note I717] cpgeek:
you know, when watching old episodes of star trek TNG, DS9, and VOY I noticed that any time something went seriously wrong (ship gets hit by weapons, power runs low, something randomly explodes) all the touch panels flicker. as much as I LOVE that android and other touch os's do a great job at emulating the amazing touch i/o interfaces seen on sci-fi that's supposed to exist in the 24th century, I wish they wouldn't have emulated it *that* closely that when something minor goes wrong we get this awful screen flicker. - my sociology commentary, I mean no disrespect or disapproval - i know these dev processes take time and thank you to those who have contributed to the wonderful work that has gone on thusfar.

---------- Post added at 02:11 AM ---------- Previous post was at 01:44 AM ----------

I didn't hear any reply to my post earlier and i found some time to do a backup to sd, full wipe, and a flash of jellybam 6.3.0. despite the flicker, I decided to go on and test the bluetooth keyboard and unfortunately it seems that just like in the recent CM builds and the most recently jellybeer builds, bluetooth keyboard support is just plain broken. It allows you to successfully pair a device, but once it's paired, it will never connect no matter if you initiate the connection from the keyboard or from the phone, or both at the same time, it just times out. I'm guessing that this is an upstream CM bug, but i'm not sure where to post about this bug.
[AT&T Samsung Galaxy Note I717] JEZZEJAMEZ:
Re: [ROM 4.2.2] JELLYBAM - v6.3.0 [24/02/2013] [i717] [AOKP | CM10.1 | ParanoidAndroi

Omg, its that time of the month. Wheres the MOD ?i never seen so many adults act an treat each other like kidz. No wonder developers move on from here. They work for free and users still treat them like shXX,!

BlA¢K ★ X

$†@¢KH○u$€ ®€D
[AT&T Samsung Galaxy Note I717] shayneflashindaily:
Re: [ROM 4.2.2] JELLYBAM - v6.3.0 [24/02/2013] [i717] [AOKP | CM10.1 | ParanoidAndroi

I hope this thread is either cleaned up or closed due to the simple fact no one can respond properly... I wont be back in this thread for this reason. Goodluck
[AT&T Samsung Galaxy Note I717] dparrothead1:
Re: [ROM 4.2.2] JELLYBAM - v6.3.0 [24/02/2013] [i717] [AOKP | CM10.1 | ParanoidAndroi

From the forum.
[AT&T Samsung Galaxy Note I717] Woody:
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.
[AT&T Samsung Galaxy Note I717] OPGT:
To get everyone to chill out a little I've figured out what is wrong... The kernel itself is the problem, not the rom.. The stock CM kernel Igio90 put on this rom had Fu***** up commits (causing the horrible screen flickers). So everyone needs to chill out and be patient until Igio90 can build off a different CM source. Thanks for being patient guys.. ill keep in contact with Igio90. You guys will have a flickerless rom soon.

P.S- MAYBE one of you guys could try compiling your own kernel?? :0
[AT&T Samsung Galaxy Note I717] kimtyson:
The Dev has acknowledged the issue, which is really good for everyone involved. Now we just need to wait and hope things get sorted out. In the mean time I sure hope it doesn't mean more judgmental posts about other peoples posts in here. It seems only certain people are permitted an opinion.

By the way, the Bug Report placed by dparrothead1 in that other forum is the most constructive action I have seen to resolve the flicker issue in this new and exciting ROM. Thank you sir.

Edit: Sorry OPGT, and anyone else working behind the scenes. I guess maybe there is other less public, constructive actions taking place, too. Let me amend my comment to state that dparrothead1's is the most constructive PUBLIC action.

---------- Post added at 09:37 AM ---------- Previous post was at 09:30 AM ----------

Thank you for your assistance to the Devs. If I could I would work on a kernel. I have not learned that skill as of yet.

I honestly think we are more chill than the reactions may indicate in this thread. For me, I am very chill. I only reported my observations of the flicker. I'm not stressed about it at all. I understand that this stuff is not guaranteed to work, we flash at our own risk, yada yada yada. There just seems to be a group of folks that have made a mountain out of a molehill in the thread about people "complaining" and being ungrateful. I don't think that is a true picture of things.
[AT&T Samsung Galaxy Note I717] BigBison420:
I personally can't wait to flash this ROM ... it's got a laundry list of features unlike any other.
[AT&T Samsung Galaxy Note I717] Teufel Hunden:
Re: [ROM 4.2.2] JELLYBAM - v6.3.0 [24/02/2013] [i717] [AOKP | CM10.1 | ParanoidAndroi

Has anyone tried 4aces or flapps kernels?

Biggest dog on the block, NOTE!! 4.2.2 JB!
[AT&T Samsung Galaxy Note I717] OPGT:
Yes. Neither work.
[AT&T Samsung Galaxy Note I717] Adizzzle:
Re: [ROM 4.2.2] JELLYBAM - v6.3.0 [24/02/2013] [i717] [AOKP | CM10.1 | ParanoidAndroi

Uh yes, as i stated before, i tried 4aces 14 and 19 kernel, as well as various versions of flapps kernel's. All in all the screen goes black and then i need to restore. It doesn't help.

:beer:"We can't stop here! This is Bat Country":beer:
[AT&T Samsung Galaxy Note I717] rbaladiang:
Re: [ROM 4.2.2] JELLYBAM - v6.3.0 [24/02/2013] [i717] [AOKP | CM10.1 | ParanoidAndroi

If this ROM was built based on 2/22 or 2/24 CM nightlies, then flickers exists. The 2/21 CM nightly should be flicker-free.
[AT&T Samsung Galaxy Note I717] Adizzzle:
Re: [ROM 4.2.2] JELLYBAM - v6.3.0 [24/02/2013] [i717] [AOKP | CM10.1 | ParanoidAndroi

So am i able to just pull a kernel from a stable version of CM10.1 and flash that along with the Rom, or am i just overlooking something?

:beer:"We can't stop here! This is Bat Country":beer:
[AT&T Samsung Galaxy Note I717] dparrothead1:
Re: [ROM 4.2.2] JELLYBAM - v6.3.0 [24/02/2013] [i717] [AOKP | CM10.1 | ParanoidAndroi

If that were the case, wouldn't one of flapps older kernels work?

I experience some flicker on flapps newest build, but I can fix that. What I am getting with 6.3, I wouldn't describe as flicker....mine is flashing screen to black continuously.
[AT&T Samsung Galaxy Note I717] Adizzzle:
Re: [ROM 4.2.2] JELLYBAM - v6.3.0 [24/02/2013] [i717] [AOKP | CM10.1 | ParanoidAndroi

Very true, i was thinking too simplistic.

:beer:"We can't stop here! This is Bat Country":beer:
[AT&T Samsung Galaxy Note I717] OPGT:
you were thinking in the right direction, but it seems Stock CM is the only kernel that likes JellyBam. So if someone were to create a stock CM kernel based on the 2/21 release of commits then we would have a flickerless screen.
[AT&T Samsung Galaxy Note I717] chris41g:
that kernel has different headers, thus wont boot with newer roms. you can try the kernel 4Aces-29 which i just uploaded.