CM bug not allowing me to view notifications or tiles?? - ONE Q&A, Help & Troubleshooting

Hi I was running jgcaaps cm ROM from December and it was amazing. So It being a few months I decided to update.
However when updating I (I always do full wipes) noticed that after android booted up I couldn't swipe down from the notification shade? It just gets stuck and doesn't open down to the quick tiles.
Also when downloading or doing anything that normally shows up in the notification shade, it simply doesnt.
I tried an AOSP ROM and its no longer an issue. Im pretty sure it is something with CM as I tried 2 other cm based ROMs and sure enough it was still happening.
Just curious if anyone has experienced this and knows if there is a fix? i do like the endless customization options that CM offers but this is a huge issue that just started happening to me.
Thanks!

Related

[Q] Similar problems with all JB ROMS. is it a hardware issue?

Pretty much every time I flash a JB ROM my infuse is fine for a few days. Sometimes even a week. Perhaps a bit laggy, but I guess that's expected given the outdated hardware.
Then eventually I start getting having these two issues
1) random shut offs - in this case the phone sometimes will not boot unless I pull the battery and put it back in.
2) or an error that reads something like "unfortunately System UI has stopped"
I can press "okay" and then get the error again over and over. I can only get out of it by pulling the battery, or holding the power button down.
I did go back to GB for a while and did not have any of these problems.
All my apps are installed from the play store, not restored from a backup. I do not overclock or undervolt.
I'd simply blame hardware, except I don't seem to have problems with GB.
This has always happened to me as well. I would say that its due to incompatibility with JB. Wasn't so bad on ICS but I found that on JB I would be reflashing after only about 2 weeks because it got so bad.
-Sent from that.... you know.... thing that sends these things-
DarK_DemoN said:
This has always happened to me as well. I would say that its due to incompatibility with JB. Wasn't so bad on ICS but I found that on JB I would be reflashing after only about 2 weeks because it got so bad.
-Sent from that.... you know.... thing that sends these things-
Click to expand...
Click to collapse
Try Paranoid Android 4.1.2 pa_infuse4g-2.53-04NOV2012-152548 . I have been using that with no issues except the Video camera being crap (photos just fine though), and you have to toggle wifi on and off to get it working. 4.2.2 roms don't work that well on really any phone I have tried even the Gnex I own had issues. I upgraded from AEON straight to Paranoid Android using their upgrade steps listed on their page. No problems no errors didn't even loose my IMEI.
I have tried the newest 4.2.2 roms from liquid, Cyan, and paranoid android. 4.2.2 roms acted badly for me in general I can't remember if I ever got that exact error. I Keep on wiping and going back to my 4.1.2 PA nandroid backup. I kinda think it might be a general 4.2.2 issue dunno.
Also saw this on the latest Beanstalk out 4-10 (so I think you should stick to 4.1.2 roms which of course don't get updated anymore)
Trouble Alerts/Workarounds:
Status bar/Notification Drawer - There seems to be a bug with the 4.2.2 status bar/notification drawer freezing. It is happening on numerous phones at random and there is not a fix available yet. Workaround - Numerous ways to workaround this issue, but easiest in my opinion is to go to settings - system settings - PIE - Enable/Disable PIE. This restarts systemUI and unfreezes the status bar.
Does anyone know what sh means? Android os is destroying my battery life.
Sent from my SGH-I997 using xda app-developers app
Use cpuspy
Sent from my SGH-I997 using Tapatalk 2
I hope you have now the latest JB ROMS update, and every thing is working fine.
I hope you have now the latest JB ROMS update, and every thing is working fine.
for me, Beanstalk latest build 1.205 is working awesome, battery life is like i do not need to charge for two days.
Yianaki said:
Try Paranoid Android 4.1.2 pa_infuse4g-2.53-04NOV2012-152548 . I have been using that with no issues except the Video camera being crap (photos just fine though), and you have to toggle wifi on and off to get it working. 4.2.2 roms don't work that well on really any phone I have tried even the Gnex I own had issues. I upgraded from AEON straight to Paranoid Android using their upgrade steps listed on their page. No problems no errors didn't even loose my IMEI.
I have tried the newest 4.2.2 roms from liquid, Cyan, and paranoid android. 4.2.2 roms acted badly for me in general I can't remember if I ever got that exact error. I Keep on wiping and going back to my 4.1.2 PA nandroid backup. I kinda think it might be a general 4.2.2 issue dunno.
Also saw this on the latest Beanstalk out 4-10 (so I think you should stick to 4.1.2 roms which of course don't get updated anymore)
Trouble Alerts/Workarounds:
Status bar/Notification Drawer - There seems to be a bug with the 4.2.2 status bar/notification drawer freezing. It is happening on numerous phones at random and there is not a fix available yet. Workaround - Numerous ways to workaround this issue, but easiest in my opinion is to go to settings - system settings - PIE - Enable/Disable PIE. This restarts systemUI and unfreezes the status bar.
Click to expand...
Click to collapse

Heads up floating window bug

I have enabled "Launch in floating window" for Heads up notifications. However, none of my Heads up notifications are launching in floating mode. They are still launching in normal full screen mode. Anyone else experience this issue? If so, is there a solution?
I am using Mahdi 2.9 Final 11/03
Update: I have tried almost all of the kitkat roms in the forums to see if it was just a problem in Mahdi. The ROMs that have the floating window option in Heads up are hit and miss. It works in some ROMs but not all. I also tried using a previous version of Mahdi and still couldn't get it working.
I would ask in the thread that's specific to the ROM so in the Mahdi thread for example. Better chance of getting an answer I think.
Myself I have no clue never used that, but I'm on stock ROM lol

Display stops working, mostly, on second boot after installing non-stock.

I've got an odd problem with my p900. If I install any lollipop ASOP ROMs, the first time I reboot after initial install, the display mostly stops working. The first boot works fine, I go through the setup wizard, set everything up, and the tablet works and displays fine as long as I don't reboot.
Specifically, what will happen if I reboot is that the tablet will go through the normal boot, and get to the point when the wallpaper and status bar will come up, but no homescreen icons or anything. Then after a while, about 2-5 minutes, the display will go black except for the status bar. I can pull down the notifications drawer from the status bar, and it will display, as will the quick settings, but anything I tap to try to interact with will seemingly just do nothing. If I have 'show touches' on, then touches will display properly, anywhere on the screen, but they seem to do nothing. I've tried trebuchet, google now, and adwex, the home app doesn't seem to make a difference.
The problem first began in I want to say october, when I flashed a CM12 nightly update. I unfortunately no longer remember which nightly I was on nor which I flashed to. I of course immedately tried to flash back to the previous nightly when I discovered the problem, but it did no good. It took me a while to figure out the pattern to the problem after it first occurred, as I often don't reboot the device for a long while after a first install. I don't have a lot of spare time to devote to sitting down and just focusing on trying different things, so it wasn't until president's day weekend that I tried what I *thought* would fix it, ODINing back to stock and installing the latest CM12.1. Clearly that didn't work, or I wouldn't be posting.
I've tried the 20151104, 1029, 1006, and 0910 CM12.1s from http://forum.xda-developers.com/gal...nt/rom-cyanogenmod-12-lollipop-5-0-1-t2971945. I've also tried Civz lollipop, pacman, and resurection remix. Anything not stock based has the problem. I tried running stock, but I've been running CM since G1 days, and I just can't stand stock, even the stripped down and modded versions. It just doesn't work right, and I can't get used to it, even after forcing myself to use it for several days.
I've never encountered such a weird problem, and I can't seem to find anyone else having a similar problem. I have no idea how to troubleshoot this beyond what I've done already. I'm currently running thompatry's Cm12.1 20160212, having not rebooted after the initial install, and it's running mostly ok, but I live in dread of my battery dying, and of course I can't install any xposed modules like xprivacy or multiwindow, which is bothersome. I have the wifi only US model, v1awifi, and I'm currently running TWRP 3, tho I was on TWRP 2.8.something when the issues first started happening.
what's the last 3 characters of your bootloader version?
heldc said:
I've got an odd problem with my p900. If I install any lollipop ASOP ROMs, the first time I reboot after initial install, the display mostly stops working. The first boot works fine, I go through the setup wizard, set everything up, and the tablet works and displays fine as long as I don't reboot.
Specifically, what will happen if I reboot is that the tablet will go through the normal boot, and get to the point when the wallpaper and status bar will come up, but no homescreen icons or anything. Then after a while, about 2-5 minutes, the display will go black except for the status bar. I can pull down the notifications drawer from the status bar, and it will display, as will the quick settings, but anything I tap to try to interact with will seemingly just do nothing. If I have 'show touches' on, then touches will display properly, anywhere on the screen, but they seem to do nothing. I've tried trebuchet, google now, and adwex, the home app doesn't seem to make a difference.
The problem first began in I want to say october, when I flashed a CM12 nightly update. I unfortunately no longer remember which nightly I was on nor which I flashed to. I of course immedately tried to flash back to the previous nightly when I discovered the problem, but it did no good. It took me a while to figure out the pattern to the problem after it first occurred, as I often don't reboot the device for a long while after a first install. I don't have a lot of spare time to devote to sitting down and just focusing on trying different things, so it wasn't until president's day weekend that I tried what I *thought* would fix it, ODINing back to stock and installing the latest CM12.1. Clearly that didn't work, or I wouldn't be posting.
I've tried the 20151104, 1029, 1006, and 0910 CM12.1s from http://forum.xda-developers.com/gal...nt/rom-cyanogenmod-12-lollipop-5-0-1-t2971945. I've also tried Civz lollipop, pacman, and resurection remix. Anything not stock based has the problem. I tried running stock, but I've been running CM since G1 days, and I just can't stand stock, even the stripped down and modded versions. It just doesn't work right, and I can't get used to it, even after forcing myself to use it for several days.
I've never encountered such a weird problem, and I can't seem to find anyone else having a similar problem. I have no idea how to troubleshoot this beyond what I've done already. I'm currently running thompatry's Cm12.1 20160212, having not rebooted after the initial install, and it's running mostly ok, but I live in dread of my battery dying, and of course I can't install any xposed modules like xprivacy or multiwindow, which is bothersome. I have the wifi only US model, v1awifi, and I'm currently running TWRP 3, tho I was on TWRP 2.8.something when the issues first started happening.
Click to expand...
Click to collapse
Have you tried changing kernel? I mean in the case of civz lollipop rom you do get an option of 2 different kernels try choosing the opposite to the one you had chosen before. Thank you, hope it helps.
I won a year ago 2 Note Pro, one works flawlessly while the other is slow af and it has the same issue that you speak about. If I stay on stock everything is good more or less (sometime little slow), but if I install Lineage or any other Custom Rom is too slow and has the same issue you speak.
I changed both batteries, but nothing to do. If anyone knows, text please.
Thank you!

Lineage 14.1

I've finally decided to flip the switch, so the 14.1 nightly builds are running (though they are built only once a week, due to the current infrastructure limitations).
The official builds are signed with private keys (for good security reasons), so there's no plan to provide any unofficial builds by me, to avoid the hassle of switching between different keys.
I'd like to thank @Loader009 for the donation of his retired xt897 devices to me, it greatly helped to make the transition from 13.0 to 14.1 much less painful.
Please let me know about the issues you encounter when running 14.1. In the case of the device crashes, I need to see the output of "cat /proc/last_kmsg" from adb shell, captured after the device rebooted after the crash. Thanks in advance.
I've got it flashed on my RAZR HD XT925 JBBL with the DPI changed to 320. I bought it secondhand and it came with KKBL so I downgraded to JBBL. Most things run fine but some apps that render off the GPU like Temple Run 2 and Subway Surfs show artifacts (random black squares and multicoloured artifacts). This occurs both in Lineage OS 13.0 and 14.1, what's the cause of this to occur?
I've noticed only two problems:
1 - NFC doesn't work properly. I can't read any tag. Android Pay also says, that device is not supported to use NFC.
2 - I use 2 custom layouts for physical keyboard and hot-keys like CTRL+Space don't work. I tried to modify the layout to make it work, but it doesn't work while typing (since space key in use, maybe)
I just installed it yesterday after a complete wipe (and format data/cache f2fs), and think I've got it all set up the way I like except launcher, and didn't run into any real problems yet.
I can't figure out how to get the expected shift/capslock behaviour from hardware keyboard. Still playing with settings.
It didn't come with an APN for freedompop but I found that info on another thread here, before applying that I didn't get LTE, only 3G or no data at all (at the places I've been in last day or so).
I dunno anything about NFC, but Android Pay installed for me with Aroma Gapps, haven't tried using it, doubt it'll work for tap-to-pay tho, as it didn't work for the last few versions of CM either, something to do with PN544 driver or something.
Did LineageOS come with trebuchet? I ended up with only the google now launcher, but maybe my gapps install erased trebuchet, I used aroma for the first time and may have selected things wrong... this one seems I can't customize much, can't get rid of google search bar, can't set background as solid color, can't set background color of app drawer at all which is back to a grid like kitkat.
Play store says firefox not compatible... dunno why. Maybe something I didn't select right with Aroma gapps, although every other app installed fine. Totally unrelated to LineageOS or our phone, but I wish I could find an idiots guide for aroma app selection, explaining what each app is for, particularly system apps I'm not familiar with.
edit: had one reboot, also had errors about MTP host stopping pop up...
enigma9o7 said:
I just installed it yesterday after a complete wipe (and format data/cache f2fs), and think I've got it all set up the way I like except launcher, and didn't run into any real problems yet.
...
Did LineageOS come with trebuchet? I ended up with only the google now launcher, but maybe my gapps install erased trebuchet, I used aroma for the first time and may have selected things wrong... this one seems I can't customize much, can't get rid of google search bar, can't set background as solid color, can't set background color of app drawer at all which is back to a grid like kitkat.
Click to expand...
Click to collapse
Trebuchet is the default launcher for LineageOS. Your Gapps deleted it. Also, if you use a smaller GApps, there is no google search bar ie its not installed. I personally use OpenGapps Pico.
Nightly build from 2017-07-28. Wi-Fi not working. Is it just me?
//EDIT: Tried older builds, too. Wi-Fi did not work with any of them. Flashed back to CM 11.0 and it worked again. Tried LineageOS 13.0 and Wi-Fi worked, too.
//EDIT2: Okay, I think I've figured it out. When I flashed the LineageOS 14.1 after I flashed the phone with previous versions, the Wi-Fi worked alright. It stopped working after changing File system to f2fs.
//EDIT3: Fine, I actually don't know, what happened, but I just changed the File system to f2fs again, flashed the phone with LineageOS 14.1 one more time and the Wi-Fi surprisingly works. I have absolutely no clue, why it did not work after the first flashing.
Shift key not working as expected
I already posted this in a seperate thread a few days ago, but I've got no response and it's driving me crazy, and I assume anyone who is still using this device is because of the physical keyboard, so probably relevant to all.
How do restore traditional "shift" behavior? I want to be able to press then release shift, and the next key I press is shifted. Right now I have to hold shift and another key simultaneously if I want capital letters or symbols from the numbers. I think there even used to be an LED that light up when shift was pressed/released until the next keypress, although I'm more concerned about how it actually works than the led...
I've played with most of the settings on the attached screenshot, other settings only seem to make things worse, sometimes making nothing happen at all for shift, sometimes putting out garbage, sometimes messing with capslock behavior (which is working normally with these settings, although no LED either)... but I certainly haven't tried everything.
If this is standard behavior for everyone using L14.1 and not a setting, is there a file I can modify or a 3rd party app, or anything, to get behavior I want?
rootdefyxt320 said:
I've got it flashed on my RAZR HD XT925 JBBL with the DPI changed to 320. I bought it secondhand and it came with KKBL so I downgraded to JBBL. Most things run fine but some apps that render off the GPU like Temple Run 2 and Subway Surfs show artifacts (random black squares and multicoloured artifacts). This occurs both in Lineage OS 13.0 and 14.1, what's the cause of this to occur?
Click to expand...
Click to collapse
hi
the version that you flashed in your xt925 was the oficial one released by LOS?
did u do any kind of port or mod?
enigma9o7: I've had the same problem sometimes back with the older builds of LineageOS 14.1. Try to clean flash it with the newest build from yesterday. I just tried to type something with the physical keyboard and the Shift button just worked "correctly".
EDIT: Okay, I think I've figured out your problem. You probably use the Asanti v2 keyboard setting. Switch it to Asanti v1 and the Shift key should work as expected.
Krlos Eduardo said:
hi
the version that you flashed in your xt925 was the oficial one released by LOS?
did u do any kind of port or mod?
Click to expand...
Click to collapse
It's the official 14.1 one for XT897.
rootdefyxt320 said:
It's the official 14.1 one for XT897.
Click to expand...
Click to collapse
without doing any port?
Should updates work thru the updater?
I just tried doing it, it downloaded succesfully, then rebooted into TWRP, but didn't do anything. So I tried installing myself (took me a while to find the file btw) and it failed zip signature verification. So I downloaded it on my PC, copied it over via USB, then tried again, and still fails.
kabaldan said:
I've finally decided to flip the switch, so the 14.1
Click to expand...
Click to collapse
@kabaldan, I noticed that a number of device trees in LineageOS now have a new branch of "lineage-15.0", but the xt897 does not. Is this an ominous sign that the xt897 will not be built for Oreo?:crying: or is just a timing thing at this early stage:fingers-crossed:
any hope for running it on mb886?
mb886 - atrix HD - ...you can test it if is your bl unlocked and twrp installed.
Mainboard have same base - msm8960. But i am now 100% sure if your phone is bl free unlockable. if not, then you can test to unlock it via sunshine.
I have installed this and for a while all was fine. But I was browsing in chrome when all of a sudden it froze and the phone restarted and went into a boot loop just showing the bootloader unlocked screen. I cleared the cache and dalvik cache from TWRP, which makes it boot, but any attempt to uninstall or launch chrome makes it happen again. Now it just seems to be happening at random without even opening chrome.
How can I wipe my device completely and start again? I know I can do a factory reset, but is there a lower level way to wipe it? I also saw something about changing the filesystem, is that worth doing (can it make it a bit faster)?
I have ordered a gemini PDA that I hope will arrive by late january or sometime in february, but I need this phone to get me through a couple more months!
Installed this a couple weeks ago, upgrading from a 4.4.4 CM after a number of apps I run on this finally dropped support. I did a complete wipe including the f2fs formats as suggested and it installed without incident.
I cannot believe how well it runs: keyboard works and lights up on pull out, turns off on close, hdmi port works, gps, camera+flash works. It really didn't lose any speed from my older install. Really well done, I was afraid there would be bigger problems but only a couple small ones so far.
The couple things I noticed: slow to get carrier signal and voice is garbled when using freedompop's dialer or google hangouts on the bottom mic. Slow signal seems normal, even 4.4.4 had this issue, though it can sometimes take a few minutes. Using a sound recorder shows the bottom mic working, but using fpop/hangouts dialer makes it garbled. Top mic, speaker phone, always works though. I don't have regular service to see is default dialer has same issue though, just freedompop free service which is just voip.
Still, this is a pretty awesome breath of life on this old thing. Ram holds it back somewhat but it's still pretty useful.
So I just wiped everything, repaired filesystems, and reinstalled. Data and cache were already f2fs so nothing to do there. But I noticed that during install it says:
twrp patching system unconditionally
unknown command [log]
unknown command [log]
Do I need a newer version of TWRP? I have 2.8.6. I noticed that at least 3.0 is available: https://forum.xda-developers.com/showthread.php?t=1887070
Here is 3.1.1-0 for you
https://drive.google.com/file/d/1vO4_nq3FNquuO3neHrOzuIb5gnmN11AZ/view?usp=sharing
CornholioGSM said:
Here is 3.1.1-0 for you
https://drive.google.com/file/d/1vO4_nq3FNquuO3neHrOzuIb5gnmN11AZ/view?usp=sharing
Click to expand...
Click to collapse
Thanks!
I've now installed the latest TWRP and reinstalled Lineage, gapps and su, and I didn't get any errors this time
But I have a really odd problem which I was hoping this would fix and it hasn't - I can't download certain applications from the play store, they say "Downloading" but they never actually start to download. Eventually either it mysteriously stops trying to download or I get an error message with code 492. It seems to be applications that are over a certain size. I've been googling but can't find any solutions that work. I have a lot of free space in all partitions. Did something with the directory structure get screwed up maybe? Seems like some problem with the dalvik cache I think, but wiping doesn't seem to help. I have no idea at this point

UI Inconsistencies on 10.3 for different devices.

Hello everybody, Happy New Year to all! First post on here after a few years but I never left XDA without an answer till now. My question is about the color of the notifications and the Quick Toggles drop-down menu. I was on beta 3 (The *new* Beta 3, on Android 10) and my notifications and Quick Toggles finally became true black like I always wanted them to be. I didn't think much of it, just welcomed the change. Problem is, I then decided to backup my phone and install 10.3 stable, 2 days after it came out, via local upgrade. I backed up my phone and installed, rebooted and was greeted with a phone with all its data but reporting 10.6 (and having grey notifications and Quick Toggles). I knew that *shouldn't* happen and since I'd already backed up everything, I decided to wipe everything and reinstall. Problem was, the only rollback package I managed to find was 9.0.2 and that was after hours upon hours of searching. I installed the package via Local Upgrade and wiped everything from the stock recovery, booted into it fine and set up my phone. I then installed all OTAs back up to 10.3. Phone booted up fine and everything seemed normal. EXCEPT, for the fact my UI is pretty much how it was on Pie. I watched videos of OP6s with 10.3 having all black notifications and Quick Toggles and read posts from other users in Reddit and OnePlus forums where they either had the same UI as me or the all black one. I've read multiple, very differing accounts from users of the same phone on the same software and also noticed this inconsistency myself but I couldn't find a clear answer anywhere, no one seems to know how the UI is supposed to be and I don't know enough about how Android works to know what actually controls this part of the OS's looks. I'm starting to believe I did something wrong but although I've been through many roms, mods and magisk modules, I don't actually know what to do this time. Any insight, advice, help or guidance, would be really appreciated. Thanks a lot.

Categories

Resources