Hi!
So, I just moved to that new shiny awesome ROM and that looks just amazing.
One extremly annoying issue tho. When screen is locked and I push power button there is a huge lag between three buttons on the bottom side of the screen lights up and actual screen lighting up. Its about 1 second lag after me pressing the power button and screen being able to be unlocked.
I tried to search for similar issues, but doesnt seems like anyone have it on my sort of phone model.
AT&T HTC One X evita here with 28th June 2013 uxylon build date. RUU version is 3.18
It's a pretty common issue for ROMs on the 3.4 kernel.
Sent from my Evita
I don't get it on PacMan rom. Used to on all other 3.4 kernel roms.
Sent from my One X using xda app-developers app
DroidRunner said:
I don't get it on PacMan rom. Used to on all other 3.4 kernel roms.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
changed to pacman rom problem still persists. sad day i guess
Okay, it may sound like a retarded noob question, but i swear 2 days ago i knew nothing about android.
Can you possibly change kernel version somehow or? I so much love this unxylon/cyanogen mod design and animation.
but i want to be everything close to perfect so..
SoulSurvivors said:
Okay, it may sound like a retarded noob question, but i swear 2 days ago i knew nothing about android.
Can you possibly change kernel version somehow or? I so much love this unxylon/cyanogen mod design and animation.
but i want to be everything close to perfect so..
Click to expand...
Click to collapse
Why is my kernel 3.4.50 while cm is 3.4.49? Did I cheat? No, I just patched it from kernel.org myself
OH, to actually answer your question, there's probably something wrong with the lockscreen. For now, I just disable the security feature.
aznrice2k4 said:
Why is my kernel 3.4.50 while cm is 3.4.49? Did I cheat? No, I just patched it from kernel.org myself
OH, to actually answer your question, there's probably something wrong with the lockscreen. For now, I just disable the security feature.
Click to expand...
Click to collapse
Tried pretty much everything. Ends up it laggs on any ROM with design like xylon/cyanogen mod has. Dont really know whatsup
Related
I have Nexus S i9020 and I have this bad problem..
It's started when I flashed AOSP ICS Brainmaster's Mix.. When I locked the phone, I had a strange yellow-green flash on the screen.. I tried flashing different kernels - no effect.. When I tried playing with Voodoo colors - no effect.. The only "semi-cure" was: if you return to "Stock gingerbread colors" that damn screenflash was seen only on the contour of clock and "that slide thing to unlock the screen" (don't know how to name it in english=))..
I thought that it was just the bug of the ROM then.. But when I flashed CM9 latest alpha everything remained the same.. I also thought that it was just a bug of the ROM..
But now I flashed ICS OTA after the downgrade to stock 2.3.6.. And the result is the same to switching to gingerbread colors in Voodoo app on AOSP old ICS ROMs.. I still have the screenflash on the contour on the lock and that "slidething"..
It's really annoying now as I'm starting to think that it is a hardware issue.. But all other functions work just perfect, not any single issue with the screen.. I haven't dropped my phone, haven't kicked it or something (bought it in June)
Can anybody help with this please?
P.S.: there were some similar threads here, but I haven't found the cure..
I tried playing with "Transition animation scale" and "Window animation scale" in Developer Options.. Setting window animation scale to 0.5x solves the problem.. But it turns off CRTscreen fadeout.. So there is something wrong with it on my phone.. I don't want to loose it, it's beautiful..
Any advice please?
I understand that I can only annoy with this question.. But still I don't know what to do! Please suggest any possible ideas, every piece of wisdom could help!
Now I've rooted official ICS, installed Nexus Beam 4.1.0 and flashed Glados 2.1 kernel.. And the green & yellow screenflash once again all over the screen when I lock the phone..
In every other possible way the screen behaves itself perfectly.. But when it turns off I see that damn flash..
Mine does it too
Sent from my Nexus S using XDA App
Mine does it only when i wake the phone and put it back to sleep without unlocking it
Mine has the exact same problem. It doesn't happen in gingerbread but on ics roms, even stock, it does a flash. On stock its lighter and harder to see, but if I change voodoo settings it turns green. I doubt its hardware considering it works fine on gingerbread.
Sent from my Nexus S using xda premium
So we have not only one complaint.. Something must be done to cure it.. It's really annoying as it is the only thing that works not fine on this phone!
Can somebody of the developers please comment on this problem?
Has someone found an answer to this?
Max2mus said:
I have Nexus S i9020 and I have this bad problem..
It's started when I flashed AOSP ICS Brainmaster's Mix.. When I locked the phone, I had a strange yellow-green flash on the screen.. I tried flashing different kernels - no effect.. When I tried playing with Voodoo colors - no effect.. The only "semi-cure" was: if you return to "Stock gingerbread colors" that damn screenflash was seen only on the contour of clock and "that slide thing to unlock the screen" (don't know how to name it in english=))..
I thought that it was just the bug of the ROM then.. But when I flashed CM9 latest alpha everything remained the same.. I also thought that it was just a bug of the ROM..
But now I flashed ICS OTA after the downgrade to stock 2.3.6.. And the result is the same to switching to gingerbread colors in Voodoo app on AOSP old ICS ROMs.. I still have the screenflash on the contour on the lock and that "slidething"..
It's really annoying now as I'm starting to think that it is a hardware issue.. But all other functions work just perfect, not any single issue with the screen.. I haven't dropped my phone, haven't kicked it or something (bought it in June)
Can anybody help with this please?
P.S.: there were some similar threads here, but I haven't found the cure..
Click to expand...
Click to collapse
Max2mus said:
I tried playing with "Transition animation scale" and "Window animation scale" in Developer Options.. Setting window animation scale to 0.5x solves the problem.. But it turns off CRTscreen fadeout.. So there is something wrong with it on my phone.. I don't want to loose it, it's beautiful..
Any advice please?
Click to expand...
Click to collapse
Max2mus said:
I understand that I can only annoy with this question.. But still I don't know what to do! Please suggest any possible ideas, every piece of wisdom could help!
Now I've rooted official ICS, installed Nexus Beam 4.1.0 and flashed Glados 2.1 kernel.. And the green & yellow screenflash once again all over the screen when I lock the phone..
In every other possible way the screen behaves itself perfectly.. But when it turns off I see that damn flash..
Click to expand...
Click to collapse
Raver27 said:
Mine does it too
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
tdtylert said:
Mine does it only when i wake the phone and put it back to sleep without unlocking it
Click to expand...
Click to collapse
apreichner said:
Mine has the exact same problem. It doesn't happen in gingerbread but on ics roms, even stock, it does a flash. On stock its lighter and harder to see, but if I change voodoo settings it turns green. I doubt its hardware considering it works fine on gingerbread.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
Max2mus said:
So we have not only one complaint.. Something must be done to cure it.. It's really annoying as it is the only thing that works not fine on this phone!
Can somebody of the developers please comment on this problem?
Click to expand...
Click to collapse
matmat07 said:
Has someone found an answer to this?
Click to expand...
Click to collapse
I've seen this discussed somewhere already, but can't recall where!? But to my knowledge, if I can remember correctly it can be corrected by resetting voodoo control settings back to 2.3.3 defaults! Something to do with gamma settings I think! But obviously you have to be rooted to have & use voodoo control!!
I've tried a couple of those settings, but it never totaly get rid of the problem, it's just less visible. But since I know it's there, i'll always be seeing it XD
You know when your in an app then go back home and the widgets need to reload them selves its like that but with all my icons they keep disappearing and reappearing until I open an app or lock my phone then unlock again. I noticed it twice so far and the last time I was downloading a bunch of music to my phone so might have something to do with lag even though there shouldn't be any problems with 2 gigs of ram.
Sent from my Samsung Galaxy S III
Ive noticed this too but on mine they just flicker real quick. I'm sure it has something to do with TW. It is rather annoying, i'd like to know more about this.
Mark930 said:
You know when your in an app then go back home and the widgets need to reload them selves its like that but with all my icons they keep disappearing and reappearing until I open an app or lock my phone then unlock again. I noticed it twice so far and the last time I was downloading a bunch of music to my phone so might have something to do with lag even though there shouldn't be any problems with 2 gigs of ram.
Sent from my Samsung Galaxy S III
Click to expand...
Click to collapse
That only happened to me when I had the clock +weather widget on my home screen. When I replaced it with just the clock (digital)widget, everything was running smooth.
Sent from my SCH-I535 using xda premium
Hmm i got that clock widget on maybe ill remove it. Did it flicker on every home screen and every icon or just the widget?
Sent from my Samsung Galaxy S III
mine does this all the time...no matter what app i am in prior to going home....it is realllllllyyyy annoying....hopefully a sw update will fix
viskey said:
mine does this all the time...no matter what app i am in prior to going home....it is realllllllyyyy annoying....hopefully a sw update will fix
Click to expand...
Click to collapse
Im hoping its software issue this is only my 3rd day with the phone and want to figure out if i should return it or wait for an update. Also my keyboard did the same kind of thing but it was just one flash not sure if there related. Little bugs remind me why my last phone was an iphone.. Thats the only thing i miss about ios is there are really aren't any bugs.
Sent from my Samsung Galaxy S III
Mark930 said:
Im hoping its software issue this is only my 3rd day with the phone and want to figure out if i should return it or wait for an update. Also my keyboard did the same kind of thing but it was just one flash not sure if there related. Little bugs remind me why my last phone was an iphone.. Thats the only thing i miss about ios is there are really aren't any bugs.
Sent from my Samsung Galaxy S III
Click to expand...
Click to collapse
I think it is a software issue. My screen flickers when I flashed CNA and BlackBean but does not flicker with AOKP. My guess is that AOKP is more stable and less buggy?
I would suggest going into your developer options and disable HW overlays. This works on AOSP ROMs and it should work on TW ROMs also.
Sent from my Slim Beaned i535
DX.Deception said:
I would suggest going into your developer options and disable HW overlays. This works on AOSP ROMs and it should work on TW ROMs also.
Sent from my Slim Beaned i535
Click to expand...
Click to collapse
+1
DX.Deception said:
I would suggest going into your developer options and disable HW overlays. This works on AOSP ROMs and it should work on TW ROMs also.
Sent from my Slim Beaned i535
Click to expand...
Click to collapse
Will do. But quick question, wouldn't the developers of CNA and Black Bean have figured this out prior to the release of their custom rom?
sghrush said:
Will do. But quick question, wouldn't the developers of CNA and Black Bean have figured this out prior to the release of their custom rom?
Click to expand...
Click to collapse
I would have thought so. But then again there roms are probably built from a modified source and compiled. Once compiled they probably flash it to make sure it boots. If confirmed to boot they probably upload the original. In that case it would not have the option enabled. That is my educated guess on the subject. lol
Screen flickering on AOSP based roms is nothing new, been a known issue for a long time. Some things get fixed then break cause of something else was changed.
Flickering
My phone is original. No Root. Screen just started flickering the other day. I have had it since August. I did nothing different to the phone. Verizon claims I damaged the phone in some way. I have not done anything to damage it. If I open the Gallery on the phone, it starts going crazy. Does not always do it. If I use something like Google Earth or Maps and then open the Gallery, I get horizontal lines across the screen flickering up and down randomly. Swiping gets sluggish when all this happens. Almost like the memory fills up. I look in the memory and it is not even using 1GB, but is close to it when all this happens. Not sure what the heck happened to cause this issue to all of sudden start occurring.
I've been preoccupied recently, and haven't been paying much attention to XDA. I've been running JellyBAM 4.0.0 for about 3 months without an issue. But the other day I noticed that the AOKP Lock Screen / Notification Weather was off. My guess would be that the provide is no longer available.
Once I found an issue, I started wondering if there was a worth successor to JellyBAM?
JellyBam has been banned from xda.
GoPadge said:
I've been preoccupied recently, and haven't been paying much attention to XDA. I've been running JellyBAM 4.0.0 for about 3 months without an issue. But the other day I noticed that the AOKP Lock Screen / Notification Weather was off. My guess would be that the provide is no longer available.
Once I found an issue, I started wondering if there was a worth successor to JellyBAM?
Click to expand...
Click to collapse
What do you like specifically about JellyBAM? Jellykang as well as the new Cyanogenmods and AOKP are likely all at least as good.
It's been banned? Oh do tell the tale...
rorytmeadows said:
It's been banned? Oh do tell the tale...
Click to expand...
Click to collapse
JellyBAM was a full blown kang of if I'm not mistaken PACman. The only thing changed at source level was credits.
Sent from my Nexus 4 using Tapatalk 2
Ziida said:
What do you like specifically about JellyBAM? Jellykang as well as the new Cyanogenmods and AOKP are likely all at least as good.
Click to expand...
Click to collapse
First and foremost, the camera app works. (A big plus over JellyBAM 3.3 and PACMan v17 - 19 and I'll ignore the lack of 1080 video.)
It's fairly stable. Easily usable as a daily driver.
Paranoid is included - Allowing the ASUS SuperNote app to be re-scaled to a runnable size.
AOKP lockscreen customization is nice. I like the extra targets, calendar and weather. (But then the Weather source appears broken, so it's disabled.)
My current issues are as follows:
Broken Weather in AOKP
Sluggish performance when the phone has been idle
Phone app / LCD doesn't turn back on after talking. (Works ok when the other party hangs up, but it sucks when you're leaving a VM.)
GoPadge said:
First and foremost, the camera app works. (A big plus over JellyBAM 3.3 and PACMan v17 - 19 and I'll ignore the lack of 1080 video.)
It's fairly stable. Easily usable as a daily driver.
Paranoid is included - Allowing the ASUS SuperNote app to be re-scaled to a runnable size.
AOKP lockscreen customization is nice. I like the extra targets, calendar and weather. (But then the Weather source appears broken, so it's disabled.)
My current issues are as follows:
Broken Weather in AOKP
Sluggish performance when the phone has been idle
Phone app / LCD doesn't turn back on after talking. (Works ok when the other party hangs up, but it sucks when you're leaving a VM.)
Click to expand...
Click to collapse
Yeah the camera could have been just me switching out the wrong libs...who knows with that. Next up...try a source port....
Sent from my Nexus 4 using Tapatalk 2
strapped365 said:
Yeah the camera could have been just me switching out the wrong libs...who knows with that. Next up...try a source port....
Click to expand...
Click to collapse
Do you have a recommendation?
GoPadge said:
Do you have a recommendation?
Click to expand...
Click to collapse
Maybe snatch the PACman source and throw the cm10.1 source tree in it and compile it?
Not to sure on how all that works but I'm supposed to be getting a ROM built for the EVO Shift guys, so maybe I'll settle on PAC and try to build for both devices...if I can keep my laptop cool enough
Sent from my Nexus 4 using Tapatalk 4 Beta
I just bought a Nexus 5 and I was wondering which is better: CM11 nightlies or just having rooted stock FW ..
Which one is faster? (bootup time, app launch times, smoothness)
And am I really missing any features when staying stock?
This http://forum.xda-developers.com/showthread.php?p=46344624
It's really up to you to decide which is better. Cm will probably have more bugs than stock but maybe they're ok for you
gFrenken97 said:
I just bought a Nexus 5 and I was wondering which is better: CM11 nightlies or just having rooted stock FW ..
Which one is faster? (bootup time, app launch times, smoothness)
And am I really missing any features when staying stock?
Click to expand...
Click to collapse
I prefer stock because of the difficulty of porting the Google Dialer with Caller ID by Google
gFrenken97 said:
I just bought a Nexus 5 and I was wondering which is better: CM11 nightlies or just having rooted stock FW ..
Which one is faster? (bootup time, app launch times, smoothness)
And am I really missing any features when staying stock?
Click to expand...
Click to collapse
I flashed just about everything and settled on stock. cm11, purity ROM, sanity, slim, you name it. Stock with xposed is great. On any custom ROM, I lost LTE and still don't know why. Gravitybox is just about the same as running a custom ROM, too.
Sent from a stock/rooted n5 running franco.kernel
I dont see much of a point in owning a nexus if you are just gonna throw Cyanogenmod on it.
Sent from my Nexus 5 using xda app-developers app
I would probably stick with stock if I didn't require voice+ app by cyanogenmod. Until hangouts come with full Google voice number support sticking with CM11.
CM11 really isn't that buggy with current nightly, it's incredibly stable. Also the fact that it's a continuous work in progress is plus. You never know when stock gets updates.
Other than that I would use paranoid android when that comes out or pacman.
Sent from my Nexus 5 using xda app-developers app
muyoso said:
I dont see much of a point in owning a nexus if you are just gonna throw Cyanogenmod on it.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Yeah just buy the cyanogenmod phone that they released. http://www.engadget.com/2013/12/20/oppo-n1-cyanogenmod-certified-by-google/
mistahseller said:
Yeah just buy the cyanogenmod phone that they released. http://www.engadget.com/2013/12/20/oppo-n1-cyanogenmod-certified-by-google/
Click to expand...
Click to collapse
Or like any other Android phone. Almost every major Android phone has Cyanogenmod ported to it. I don't personally understand the appeal of buying a Nexus phone to then throw on the same custom rom that you could run on literally any other Android phone. I guess if you are off contract and absolutely love Cyanogenmod for some insane reason. . . . .
As said on a non nexus the cyanogen team really shine, to be honest I'm loving cataclysm ROM at the minute. Close to stock but has just enough customisations for me
Sent from my Nexus 5 using XDA Premium 4 mobile app
muyoso said:
Or like any other Android phone. Almost every major Android phone has Cyanogenmod ported to it. I don't personally understand the appeal of buying a Nexus phone to then throw on the same custom rom that you could run on literally any other Android phone. I guess if you are off contract and absolutely love Cyanogenmod for some insane reason. . . . .
Click to expand...
Click to collapse
Yeah... not a big cyanogen mod fan, although a big fan of Carbon ROM so I guess I am?
hey guys, i am a bit late but finally i upgrade from sgs2 to n5. and stock-google-android seems to be slick and fast. but what i miss is customizable quick settings and detailed volume control, which i had with my beloved cm. would that be things that xposed can do for me? what are you guys using with your n5?
tyvm!
kws
kweso said:
hey guys, i am a bit late but finally i upgrade from sgs2 to n5. and stock-google-android seems to be slick and fast. but what i miss is customizable quick settings and detailed volume control, which i had with my beloved cm. would that be things that xposed can do for me? what are you guys using with your n5?
tyvm!
kws
Click to expand...
Click to collapse
Gravity box does the job fine but i feel that it does slow my phone down a bit. I prefer CM over stock
alb3rtt said:
Gravity box does the job fine but i feel that it does slow my phone down a bit. I prefer CM over stock
Click to expand...
Click to collapse
thx for your reply! i like cm very much. but i figured there would be the disadvantage that cm updates will take a little longer than google (which was the other way round with samsung). maybe this will change since google is sending out dev-previews of new major releases now.
have a nice day,
kws
kweso said:
thx for your reply! i like cm very much. but i figured there would be the disadvantage that cm updates will take a little longer than google (which was the other way round with samsung). maybe this will change since google is sending out dev-previews of new major releases now.
have a nice day,
kws
Click to expand...
Click to collapse
I will never use CM again, and will stay away from CM variants if at all possible.
You're talking about 2-3 days here. If that worried about it, go back to stock until CM updates. That's what I did for 4.4.3. I was already in bootloader flashing the new modem, so figured I'd just flash the rest.
Aerowinder said:
You're talking about 2-3 days here.
Click to expand...
Click to collapse
rly? youre saying cm releases new major versions 2-3 days after google releases it?
kweso said:
rly? youre saying cm releases new major versions 2-3 days after google releases it?
Click to expand...
Click to collapse
Slim does.
Are there any roms being worked on? The XL has two so far. Hoping we get some.
They have two now? Wow I only saw the Lineage one, good to hear.
I'm wondering this as well, I imagine it shouldn't be that hard to port them over to our Walleye should anyone want to. After all, aren't they basically the same phone besides the bigger battery and different screen?
Anyway it's still early days yet, we just have to be patient.
Sent from my Samsung Galaxy S7 using XDA Labs
kalinda99 said:
They have two now? Wow I only saw the Lineage one, good to hear.
I'm wondering this as well, I imagine it shouldn't be that hard to port them over to our Walleye should anyone want to. After all, aren't they basically the same phone besides the bigger battery and different screen?
Anyway it's still early days yet, we just have to be patient.
Sent from my Samsung Galaxy S7 using XDA Labs
Click to expand...
Click to collapse
Yup theres LOS and AOSP so far. Carbon and ABC are being worked on, also think DU, OMNI, AICP and SLIM but not 100% sure. After spending so much on a phone seeing development is a relief. The phone is amazing stock, but coming from N6 I do miss flashing a bit. Havent used the N6 since dec 5 but I still download all latest rom updates + TWRP etc. for the N6 to keep backed up for the future.
I'm impatiently waiting for the Carbon Ron. I had it on my HTC m8 and genuinely miss it.
Sent from my Pixel 2 using Tapatalk
Diesel_Jeremiah said:
I'm impatiently waiting for the Carbon Ron. I had it on my HTC m8 and genuinely miss it.
Click to expand...
Click to collapse
I would be happy with anything at this point. I'm just shocked there isn't something at this point.
I haven't heard anything about any roms.
Looks like the XL now has 3 roms.
I know thats awesome just hope there will be a maintainer for them for the regular Pixel 2
jfdebo779 said:
Looks like the XL now has 3 roms.
Click to expand...
Click to collapse
Archangel said:
I know thats awesome just hope there will be a maintainer for them for the regular Pixel 2
Click to expand...
Click to collapse
Me too.
According to the maintainer of taimen for LineageOs there will be a mantainer. That's what he said in the post. But it's up to the maintainer to provide unofficial/test builds for us. .
does flashing a custom rom on a Pixel effect the camera picture quality like it does on Oneplus Phones?
vuP22 said:
does flashing a custom rom on a Pixel effect the camera picture quality like it does on Oneplus Phones?
Click to expand...
Click to collapse
I never had that issue with the Nexus phones. I would assume the same for this. It was one reason I purchased this phone over the 5T.
I'm glad that there are some ROMS being worked on. I really REALLY miss hold-back-to-kill and music controls with the volume rocker. Would be EXTREMELY helpful to have status bar brightness control as well. Pulling down the shade every time I want to change the brightness is pretty tedious.
GohanBurner said:
I'm glad that there are some ROMS being worked on. I really REALLY miss hold-back-to-kill and music controls with the volume rocker. Would be EXTREMELY helpful to have status bar brightness control as well. Pulling down the shade every time I want to change the brightness is pretty tedious.
Click to expand...
Click to collapse
If passing safety net is not an issue for you, the Xposed module GravityBox for Oreo is now ready. I believe this has all of the features that you are looking for.
Thanks
Thanks, this will work for now. Status bar brightness is a little glitchy in landscape, but other than that this it's perfect shin while I wait for an actual ROM.