Related
on every single cm7, or cm7 based rom, i get the same problem, when i dim the screen, then turn it back on nad black screen. backlight is on, but screen is not. to run any new bb rom i have to use a special kernel so kernels cannot be used. The thing is, after 2 or 3 times, the screen comes on, or if i tap the screen it comes on.
but i tried fundoozzz's miui pureveiw which i now assume is based of cm7, and guess what, the screen does not come on-at all.
any suggestions
russian392 said:
on every single cm7, or cm7 based rom, i get the same problem, when i dim the screen, then turn it back on nad black screen. backlight is on, but screen is not. to run any new bb rom i have to use a special kernel so kernels cannot be used. The thing is, after 2 or 3 times, the screen comes on, or if i tap the screen it comes on.
but i tried fundoozzz's miui pureveiw which i now assume is based of cm7, and guess what, the screen does not come on-at all.
any suggestions
Click to expand...
Click to collapse
Same problem here. My phone does not like cm7 roms. :-\ it simply falls dead
I use cm9, aosp gb and ics without any of problems.
I'm trying the new MIUI pure view and the problem is horrible. Working g on a solution.
Sent from my LG-P506 using xda premium
sarus_b said:
Same problem here. My phone does not like cm7 roms. :-\ it simply falls dead
I use cm9, aosp gb and ics without any of problems.
Click to expand...
Click to collapse
anyway i think i found a fix if anyone has a black screen bug like that, or lets just say you cant run aokp.
http://forum.xda-developers.com/showthread.php?t=1227682
i would switch to rashed97's cm10 rom, its way more stable than all the other stuff, and it has a version for each optimus phone
Exactly,, what is the fix you found...
Do you tested on your lg thrive?
gabo_lope said:
Exactly,, what is the fix you found...
Do you tested on your lg thrive?
Click to expand...
Click to collapse
The kernels included multiple black screen bug fixes, I assumed the could work, but my thrive did not like them, my color was way off and stuff like that. Black screen persists but depends on ROM I think. Give it a go and don't forget, backup everything.
Sent from my LG-P506 using xda premium
i only had that problem on. cm9, try gingersnap 2.3, it doesnt has that problem
i would really like to use fundoozz's miui pureview rom, it has the issue, i doubt it is based of cm7 but it is GB, i have no freaking idea what the problem could be, but still looking, also plz help me, get a cm7 rom that has the issue and try finding a fix for it by testing.
Thanks,
Hey guys so I've got a huge issue. I'm on now my 3rd SGSIII and I'm getting very annoyed. My screen goes nuts randomly. I think I've found a fix, but I'm not sure what's causing it, as most people don't show the symptoms. My screen starts flashing and flickering, whether it's the lockscreen, the homescreens, within an app or in the app menu it does the same thing. I haven't taken a video of it yet, but will if someone wants to see what's happening. I've had it happen only on JB, both roms and stock doesn't seem to matter. The 'fix' is the same one as AOSP rom users use, which is to disable hardware overlay, however I don't know why a non-AOSP rom would need to deal with this. The roms I've used are: Vengeance, CleanRom, Synergy and The Executioner. I've gotten so annoyed that I've gotten Verizon to allow me to switch to the DNA if I want. I've taken a few Logcat's, if someone who can decipher them more than I can to figure out what's actually wrong would be great! I've taken a bunch of logcats, but only have one posted to pastebin. It was taken whilst I was having the issues. Thanks for the help guys!
http://pastebin.com/2SZkQGZJ
LlirasChosen said:
Hey guys so I've got a huge issue. I'm on now my 3rd SGSIII and I'm getting very annoyed. My screen goes nuts randomly. I think I've found a fix, but I'm not sure what's causing it, as most people don't show the symptoms. My screen starts flashing and flickering, whether it's the lockscreen, the homescreens, within an app or in the app menu it does the same thing. I haven't taken a video of it yet, but will if someone wants to see what's happening. I've had it happen only on JB, both roms and stock doesn't seem to matter. The 'fix' is the same one as AOSP rom users use, which is to disable hardware overlay, however I don't know why a non-AOSP rom would need to deal with this. The roms I've used are: Vengeance, CleanRom, Synergy and The Executioner. I've gotten so annoyed that I've gotten Verizon to allow me to switch to the DNA if I want. I've taken a few Logcat's, if someone who can decipher them more than I can to figure out what's actually wrong would be great! I've taken a bunch of logcats, but only have one posted to pastebin. It was taken whilst I was having the issues. Thanks for the help guys!
http://pastebin.com/2SZkQGZJ
Click to expand...
Click to collapse
is the show screen updates or something similar on in developer settings?
dragon1357 said:
is the show screen updates or something similar on in developer settings?
Click to expand...
Click to collapse
Nope, I don't run that stuff because all of the rendering updates and stuff can get annoying to look at while working. I'm able to get the same issues on a fully stock rom, and a pure flashed rom, with a few programs installed. But the fact that the hardware render seems to be the issue to me is just very odd on a non-AOSP rom.
I have been having screen flickering issues ever since I flashed the latest AOKP build (AOSP) I originally thought that it was because of the kernal and the under voting that I applied but even with a different governor and normal volt settings the screen still flickeres. After some poking around I figured you that it is only happening while I am trying to type and by uninstalling the Swype beta keyboard the screen flicker had been reduced to almost nothing. I do not know why the keyboard would amplify the effect but if I use the system keyboard the flickering becomes almost non existent.
Also, the screen flickers anytime a pop up menu is on screen, such as in the tapatalk app, the menu that pops up to allow you to quote someone..
Sent from my SCH-I535 using Tapatalk 2
Had been having the same issue on Baked Bean 6, flashed BB7 last night and it seems the problem is gone. BB7 being 4.2.1 I'm guessing whether intentional or not somewhere along the process of updating the "bug" if it indeed was as it appeared was squashed.
I'd be curious to know what was causing this, if by chance you find a definitive answer please post it.
Thanks
Lk
I had a very similar issue for a while, i flashed LEAN KERNEL
Rebooted twice, and problem went away.
For an update, I flashed kt's latest kernal and the flashing has ceased.
Sent from my SCH-I535 using Tapatalk 2
Has anyone else noticed that the flash is really slow on 4.4.2? I used flash alerts pro since 4.4 and on 4.4 I could set the flash to blink 6 times or more in under a second. Now on 4.4.2 its more like 2-3 times. I am currently running Liquid Smooth and its the same. I tested with the torch app and no change. Anyone know why?
Sent from my Nexus 5 using Tapatalk
Jacob030 said:
Has anyone else noticed that the flash is really slow on 4.4.2? I used flash alerts pro since 4.4 and on 4.4 I could set the flash to blink 6 times or more in under a second. Now on 4.4.2 its more like 2-3 times. I am currently running Liquid Smooth and its the same. I tested with the torch app and no change. Anyone know why?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Could be where the torch app was merged from. The torch app on Carbon ROM is very fast, no lag/stutter what so ever. On other ROMs however, I have noticed the latent period from the click activity and the actual flash coming on. If you check the repo where the torch was merged from, that's probably why. Many use CM yet lately, is had issues. See if any differences between the ROMs and that'll probably answer why so lagged flash.
RevelationOmega said:
Could be where the torch app was merged from. The torch app on Carbon ROM is very fast, no lag/stutter what so ever. On other ROMs however, I have noticed the latent period from the click activity and the actual flash coming on. If you check the repo where the torch was merged from, that's probably why. Many use CM yet lately, is had issues. See if any differences between the ROMs and that'll probably answer why so lagged flash.
Click to expand...
Click to collapse
See that's the thing. Its not just the torch app. Its every app that has a strobe setting. Its like the flash can't flash fast enough. Maybe something is different in the kernel that changed the flash rate. It worked fine on stock 4.4, but not on stock 4.4.2. Weird........
Sent from my Nexus 5 using Tapatalk
Jacob030 said:
See that's the thing. Its not just the torch app. Its every app that has a strobe setting. Its like the flash can't flash fast enough. Maybe something is different in the kernel that changed the flash rate. It worked fine on stock 4.4, but not on stock 4.4.2. Weird........
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
The torch app is the cause, it's been reported a lot. With a faulty torch app, as I've read across many boards, the flash "happens to early in camera" or "not working" or "laggy". The flash rate, in your case, is probably due to this as well. With new merged torch from either CM or other sources lately, there has been A LOT of reports against it working/misfunction. What I can say is, try flash another ROM that works (could try Carbon ROM) and test the flash/strobing effects. If it works on that ROM, then it's the liquid smooth ROM/torch. If not, then it's the phone. But I looked into liquid smooth before but lately, they've had problems, one being the torch app.
RevelationOmega said:
The torch app is the cause, it's been reported a lot. With a faulty torch app, as I've read across many boards, the flash "happens to early in camera" or "not working" or "laggy". The flash rate, in your case, is probably due to this as well. With new merged torch from either CM or other sources lately, there has been A LOT of reports against it working/misfunction. What I can say is, try flash another ROM that works (could try Carbon ROM) and test the flash/strobing effects. If it works on that ROM, then it's the liquid smooth ROM/torch. If not, then it's the phone. But I looked into liquid smooth before but lately, they've had problems, one being the torch app.
Click to expand...
Click to collapse
Here's vids of what I mean.
Stock 4.4
http://youtu.be/IzVoLCKMInM
Stock 4.4.2
http://youtu.be/QvkN6x0Dto0
Jacob030 said:
Here's vids of what I mean.
Stock 4.4
http://youtu.be/IzVoLCKMInM
Stock 4.4.2
http://youtu.be/QvkN6x0Dto0
Click to expand...
Click to collapse
I see what you're saying, flash is slower. The reason, being on custom ROM and that the updates to Kitkat have been battery drain and camera issues are probably causing you the issue. The update to 4.4.2 probably caused the problem because of upgrades to camera/torch files. As before, if test another ROM quick and see if issue persist. If so, then it's 4.4.2 and, if not, then it was ROM related. Only reasons and change.
I know this question is really subjective. I'm coming from the Note II and have not been in this forum more than a couple of days so I'm not famililar with the developers and their work.
I'm just not sure what Rom to start with.
Speed/stability. Feature Customizations, You know, General grovieness
Stock.
Sent from my HTC6525LVW
ufkal said:
I know this question is really subjective. I'm coming from the Note II and have not been in this forum more than a couple of days so I'm not famililar with the developers and their work.
I'm just not sure what Rom to start with.
Speed/stability. Feature Customizations, You know, General grovieness
Click to expand...
Click to collapse
You literally described viper rom
Sent from my HTC6525LVW using Tapatalk
If you want customization, ViperROM is the way to go. It is fast and has so many options and settings it can almost be overwhelming if there were anymore things to explore in their tweaks app. Has some nice themes (although many are not fully compatible yet) as well. For a stock ROM with speed and removed bloatware, I recommend Skyfall. It has been the fastest for me as far as stock roms go. Bonestock is great as well, I just had awful battery life on it (which was my fault but was too lazy to diagnose so i crack flashed something else. Just try them all and see what you like best.
Stock. Everything works and you never have to wipe for an update.
Sent from my HTC6525LVW using xda app-developers app
Viper.
Stock with xposed seems to do the trick for me
Sent from my HTC6525LVW using Tapatalk
I've flashed BoneStock and have been really happy with it honestly. I really only wanted the bloatware removed and it did a good job of that.
I haven't tried any others yet though. Stock is actually really, really nice. HTC did a fantastic job with Sense 6.0.
A second vote for Viper! This ROM has been fantastic. Performance is much improved over stock, battery consumption has been lower, and there are so much customization that can be done through Viper One's tweak configuration (including enabling Power Saver mode which Verizon took away, performing an "auto hide" of the navigation bar, adding custom themes and colors, etc.). The devs of this ROM are also VERY responsive. Be sure to make a nandroid back up using CWM or TWRP before flashing any custom ROM, so you have something to go back to if you are not happy.
Was thinking about grabbing this phone, but what about those of us coming from stock Nexus Android? I see people recommending stock, but then dont you have to deal with Sense and stuff? Or am I just missing something?
twan69666 said:
Was thinking about grabbing this phone, but what about those of us coming from stock Nexus Android? I see people recommending stock, but then dont you have to deal with Sense and stuff? Or am I just missing something?
Click to expand...
Click to collapse
You can flash the Google play edition rom
Sent from my HTC6525LVW using Tapatalk
twan69666 said:
Was thinking about grabbing this phone, but what about those of us coming from stock Nexus Android? I see people recommending stock, but then dont you have to deal with Sense and stuff? Or am I just missing something?
Click to expand...
Click to collapse
I've run the Stock Nexus, and LOVED IT. I also got used to Samsung's TouchWhiz, I personally like HTC's Sense. Much like ROMS, this is a personal choice. I'm sure, once I see a CM or something like that I will give it a try to check it out. Sense is not like it was a couple of years ago. It Flies. Check it out, see for your self.
NoFanboy said:
You can flash the Google play edition rom
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Yeah, Ive been looking that thread over and it looks like there's a couple of issues still. After looking that over I started browsing around here and thats how I found this thread. Funny nobody has recommended it yet though?
ufkal said:
I've run the Stock Nexus, and LOVED IT. I also got used to Samsung's TouchWhiz, I personally like HTC's Sense. Much like ROMS, this is a personal choice. I'm sure, once I see a CM or something like that I will give it a try to check it out. Sense is not like it was a couple of years ago. It Flies. Check it out, see for your self.
Click to expand...
Click to collapse
Thanks
ufkal said:
I know this question is really subjective. I'm coming from the Note II and have not been in this forum more than a couple of days so I'm not famililar with the developers and their work.
I'm just not sure what Rom to start with.
Speed/stability. Feature Customizations, You know, General grovieness
Click to expand...
Click to collapse
See if the stock will work fine for you. From there,you would know if you will still look for something better or new.
Hey guys,
I have a VZW HTC One M8 with the following version details:
Cyanogenmod 11-20141112-snapshot-m12-m8
Unlocked bootloader
M8_WLV PVT SHIP S-OFF
CID-VZW__001
HBOOT-3.16.0.0000
RADIO-0.89.20.0222
OPENDSP-V26.2.2-00538-M8974.0106
OS-
eMMC-boot
This phone came to me with a clean Cyanogenmod install on it. I wiped it anyway to be sure. I have an S3 that I've been running CM11 on up until I got this phone so I'm no stranger to Cyanogenmod.
My issues appear to be randomly occurring and I cannot seem to pin down what is causing it or when it actually happens. Here are the various issues I'm seeing:
1. Screen fails to reorient when being turn - this happens system wide, even the home screen fails to reorient. Perhaps a problem reading the gyro sensor?
2. Lux values get stuck, usually at 45. Ambient light sensor?
3. Double tap to wake stops working - need to use the sleep/wake button to turn the screen on. Can still double tap the status bar to turn the screen off
4. Incorrect battery reporting - The battery appears to drain normally and at a consistent pace, however if the phone is shutoff or rebooted I will sometime see a huge drop when the phone boots back up.
I have a screenshot from the phone this afternoon but cannot post it (attachments fail to upload on this forum). I can probably PM it to you though.
I noticed if the phone gets to 5%, sometimes ~15% it will just turn off because the battery has actually died but the OS thinks differently.
The first 3 issues fix themselves after reboot.
Oh and I've noticed that the profiles feature doesn't work properly. If the ring mode is set to vibrate on the work profile, it will stay in vibrate even when it switches back to the default profile which is set to ring mode. The phone will not let me set custom notification sounds with Profiles enabled either. Example: Hangouts uses the notification sound as set by the default in Settings. I cannot change this. I can turn off Profiles and I can change the notification tone on Hangouts all day long.
Not quite sure what I should be looking at here so any guidance or suggestions would be much appreciated. Let me know if you need any more details.
You answered the question yourself in the second sentence of your post.
beaups said:
You answered the question yourself in the second sentence of your post.
Click to expand...
Click to collapse
beaups,
Was really hoping for a more descript answer. Can you please elaborate?
cstokes86 said:
beaups,
Was really hoping for a more descript answer. Can you please elaborate?
Click to expand...
Click to collapse
You are running cm. Probably known cm bugs or possibly you need different firmware. Either way, there's no such thing as a hardware problem until it exists on stock software.
beaups said:
You are running cm. Probably known cm bugs or possibly you need different firmware. Either way, there's no such thing as a hardware problem until it exists on stock software.
Click to expand...
Click to collapse
I forgot to mention in my original post:
I already searched around for the various issues I'm having but was not able to find any mentioning of them in any known issues lists. Was hoping to see if any devs on here had suggestions on things to try.
cstokes86 said:
I forgot to mention in my original post:
I already searched around for the various issues I'm having but was not able to find any mentioning of them in any known issues lists. Was hoping to see if any devs on here had suggestions on things to try.
Click to expand...
Click to collapse
Search better. This took me less than 5 minutes:
http://forum.xda-developers.com/showpost.php?p=56813202&postcount=3167
http://forum.xda-developers.com/showpost.php?p=56733227&postcount=3140
http://forum.xda-developers.com/showpost.php?p=56719654&postcount=3130
and many, many more all in that thread, which happens to be the CM thread for your phone.
Oh, and welcome to XDA
beaups said:
Search better. This took me less than 5 minutes:
http://forum.xda-developers.com/showpost.php?p=56813202&postcount=3167
http://forum.xda-developers.com/showpost.php?p=56733227&postcount=3140
http://forum.xda-developers.com/showpost.php?p=56719654&postcount=3130
and many, many more all in that thread, which happens to be the CM thread for your phone.
Oh, and welcome to XDA
Click to expand...
Click to collapse
Thanks for those links. I was looking in the official known problem lists for Cynogenmod for these issues to see if they actually confirmed anything. I will look at possibly installing a nightly and testing with that, but I'm a bit reluctant to go that route since this is my daily driver.
cstokes86 said:
Thanks for those links. I was looking in the official known problem lists for Cynogenmod for these issues to see if they actually confirmed anything. I will look at possibly installing a nightly and testing with that, but I'm a bit reluctant to go that route since this is my daily driver.
Click to expand...
Click to collapse
If you are looking for stability, flash a sense based ROM. Its just the way it is.
beaups said:
If you are looking for stability, flash a sense based ROM. Its just the way it is.
Click to expand...
Click to collapse
^ Can't disagree with that, but I loathe the bloatware and manufacturer UI and skins they put on their devices, not to mention the freedom and functionality I lose out on by going back to a more or less stock experience. If I want stock non-CM, I'll just flash 5.0 GPE and see how that goes, but I've already tested with that as well and missed the functionality that CM brings. :/
Win/Lose.
Do you think the firmware (not the ROM/OS) is highly out of date and should be updated by now?
cstokes86 said:
^ Can't disagree with that, but I loathe the bloatware and manufacturer UI and skins they put on their devices, not to mention the freedom and functionality I lose out on by going back to a more or less stock experience. If I want stock non-CM, I'll just flash 5.0 GPE and see how that goes, but I've already tested with that as well and missed the functionality that CM brings. :/
Win/Lose.
Do you think the firmware (not the ROM/OS) is highly out of date and should be updated by now?
Click to expand...
Click to collapse
Yes you should update that firmware. There's an emmc controller firmware update amongst other things included you should have. Have you tried gpe or stock with some of the xposed modules now available?