Just checking if anyone else has the same issue since installing ICS. I know that the B & N Nook app has never been the most stable app and has always been a little glitchy, but now when I open up one of my e-magazines, if I try to zoom into an article or a picture the whole screen goes black. It doesn't happen all the time but it is quite frequent. I have tried a few different mags and have encountered the same problem. Not sure if there is something in the settings I can alter to alleviate this glitch? Never had this particular problem before the update! Any suggestions?
P.S. I have a non rooted US WiFi stock ICS version.
Hi all,
I've recently installed the ICS ColdFusionX ROM tillals 15/05 build, on my Orange Sanfrancisco (ZTE Blade) (gen1 - TPT'd to gen2).
After some initial problems I now only have one problem blocking me from using this ROM as my daily...
When I go to make a call (and possibly also when someone calls me) the call is established but the phones screen goes black. The UI and buttons then effectively become disabled meaning I can't hangup the call, or exit without removing the battery :-(
This is a real shame as it otherwise seems to be an excellent ROM... I really can't believe how fast and smooth it is!
I've looked around, and can't see anyone else mention this issue (when establishing calls from the device itself). The few posts I've seen suggest recalibrating the proximity sensor and rebooting, but I've tried that and no luck :-( any ideas???
Thanks greatly.
Update
After re-installing and experiencing the same problem, I managed to resolve it simply by recalibrating the proximity sensor (and not reseting/rebooting).
this problem has been fixed try fixed try flashing the rom again
I have tried several rom/kernel combinations on two Nexus 7's and noticed that while doing normal internet surfing or using basic applications that the screen will black out for second then come back on and resume where it was. I noticed some posts on this in the android development sections, yet no one seems to have a fix. Is this a software thing or a hardware thing?
I noticed this when I installed CM10 based PA, so I guess it's a ROM issue.
Its the surfaceflinger issue. They did something recently to it and im guessing dont realize its a bug.. but let me link you the fix it will work on any ROM.
surfaceflinger-fix.zip Flash in recovery and enjoy.
I have a Canadian Note 3 (SM-N900W8), it's KNOX 0x0 rooted and I have CM11 M12 installed. I have been using only the M builds since I got this phone, I didn't even set up Touchwiz when I got it, I rooted and installed Cyanogenmod out of the box.
Now, with the new CM12 builds coming out, what happened to CM11, are they going to fix the remaining issues? Or did they just bail on legacy KitKat users because I'm having TONS of problems and I don't want lollipop, it runs like absolute crap for the nightlies right now and CM11 M12 isn't much better. Bluetooth takes a couple of attempts to connect, when it does my phone runs super slow to the point it force restarts. For instance, if I'm driving around, listening to music on the car stereo, pull over some where, find a new album on Google Music, start playing that, it's all good, do this a few times, every time I use my phone it gets slower and slower until it force restarts and then bluetooth has trouble connecting again. I've tried this on a few other vehicles of different brands and aftermarket stereos and it's the same result.
Audio is all funky when bluetooth is on too, it sounds like robots for the system sounds and if bluetooth drops while it's connected the music starts playing from the phone and sounds all roboty. I always do clean flashes too and the latest Paranoid Android GAPPS every time I reflash, the ROM is fine out of the box, works flawless for the first few days but after awhile, it becomes so bad I have to backup, wipe, reflash, and start over for another few weeks.
Another issue is somewhere between M8 and M12 one of the builds corrupted my SD card, I tossed in a second new card, it was corrupted again, FutureShop won't give me another one and said my phone is breaking them so I'm SD-less right now.
There are also quite a few apps that force close, but always at random, it's never when doing the same thing over and over, for instance, I can be scrolling through G+ and it tells me settings has stopped working, wasn't even using settings, didn't even have it open, haven't clicked it since booting my phone, just randomly stops working for no reason, this also happens all the time with the Camera, it says it just stops working when I haven't even used it and then if I try to use it, it says the camera is disconnected and won't work until I reboot.
I turn my phone off every night while it's charging and turn it back on every morning so every morning it gets a fresh restart, and I have to restart my phone probably 5ish times a day, if I'm using bluetooth more then normal then there's quite a few more unintentional reboots in there as well.
The last issue, which is a known issue is NFC not working, is there a fix for this yet? I kinda miss this feature and with how flawed CM11 is getting I don't know where to turn since they always seemed to be the most stable out of everything I've tried.
Any before anyone says Temasek's CM builds, I tried it, the final for CM11, it was worse then M12, it's exactly the same as M12, but every issue happens more frequently. Also, the pull down menu (when pulling down from the top right to show toggles), the bottoms of the last row was cut off so it didn't look very appealing either, it also used WAY more battery life, I usually get a full day out of one charge, so around 18 to 20ish hours on one charge, with temaseks cm11 I had to charge my phone half way through the day, sometimes my phone would just die on me without me knowing, the battery usage was always Android System.
A new problem that just happened lastnight was Google Keyboard was deleted and only the voice search would work, but "voice search can't be reached" so I couldn't search for another keyboard app from the playstore. I also used the stock GAPPS so AOSP keyboard is replaced with Google Keyboard, I had to reflash again this morning because I couldn't figure out the keyboard thing, there wasn't even a keyboard under languages in settings so I had no options to pick which keyboard to use. When I reflashes this morning I used the Modular GAPPS to it keeps the AOSP Keyboard just in case this happens again but I'm getting really tired of only having a reliable phone for a few weeks.
So, are there any fixes for these issues?
Bluetooth taking multiple attempts to connect
Bluetooth forcing random reboots
Bluetooth making audio from device all funky and sounds like a robot
Corrupting SD cards
Random system apps stopping without me even using or opening them
Google Keyboard vanishing
Are there any stable ROMs I could try for the HLTE? Maybe one that has working NFC? I'm almost thinking of going back to stock *throws up in mouth* but I don't know what else to do with how many bugs there are and Lollipop is only getting worse with the issues.
I'm also trying to avoid Lollipop because everything is white, Note 3 is an AMOLED display, each pixel illuminates on it's own so white screens use WAY more battery life then black ones which was a feature of Temasek's CM11 that I liked, had the option in settings to make everything black like the good old days.
So guys? Really out on my luck here, not sure what the next step is, any fixes for these problems? Any other ROM's I could try? Would flashing a new recovery and reflashing CM11 M12 fix some of these issues? I'm using Xiaoli CWM v6.0.4.7(20140125). Would the fact that KNOX isn't tripped have something to do with this? I really don't understand why there aren't more posts for these issues which leads me to believe I'm one of the only ones experiencing them.
Any help or suggestions would be greatly appreciated
EDIT:
I forgot to mention that when recording audio or video, it's as if the mic gain is set on full so even the slightest sound is pure distortion, normal talking volume and it clips, I found an app that lets me choose between the mics and when I pic the external mic, it's all muffles as if something is covering it but my phone wasn't in a case while I was testing so I'm not sure what the deal is there but I can't record any decent audio with this and when I record in 4K using Cinema FV-5, all the videos turn out looking like Anaglyph 3D but all pink and green, it's really weird and I don't understand why, but 1080p at 60fps works fine.
I am on CM12 and luckily have had no issues at all. I came from KK 4.4.4 and still have the NB7 BL and modem. I tried one of the guys slim ROMs alpha builds but had issues (probably operator error) but I've tried Bluetooth, GPS, WiFi , LTE etc and everything is good. Not sure what to tell you. I do however always wipe internally and d/l all my apps again through WiFi. A bit cumbersome I know but it won't give me any residual data.
Sent from my SM-N900W8 using XDA Free mobile app
that static screen(snow) you get when your tv isnt on a channel, i get that flashed right before the ambient display shows. anyone one else have this issue ?
Probably have screen on/off setting on CRT in settings. Are you on a custom rom? I don't see the setting in OOS anywhere.
got same issue here
I've noticed the same thing randomly happening. Doesn't happen all the time so can't see what might be causing it. I'm using full stock and there is no setting I can see.
vuway said:
that static screen(snow) you get when your tv isnt on a channel, i get that flashed right before the ambient display shows. anyone one else have this issue ?
Click to expand...
Click to collapse
I get that since when I got the device last year but after update it show very less like maybe once a month. No way to fix it tho
Yup, Same here! Happens randomly on different custom kernels.
It's a feature, not a bug
I've noticed that it seems to happen when the screen lights up for a notification too.
I would only get this when on Smurf Kernel. When I switch to EX or RZ, the issue goes away.
thank you everyone for your input, its nice to know its a common issue. maybe ill try ex kernal. im currently on smurf. or i might just leave ambient turned off. doesn't seem to have much advantage over the regular lock screen anyway
I got this problem too a few weeks ago after trying out some kernels. I fixed it by dirty flashing OOS into both slots. It's a small but very annoying issue.
All kernels that use Dynamic FSync have this issue. You must turn OFF Dynamic FSYNC in EX Kernel Manager