I've been running CM9 for several months now and I definitely love it and up until last week, I was running CM9 Beta 1. So I decided to upgrade this week to CM9 RC1 and everything went fine. Now the problem is that one of my applications is not working correctly. It is a custom application that listens for a side button press (using WAKE) then loads up the application before the lockscreen, and this is where my problem comes in.
For whatever reason, after upgrading to the latest CM9, my phone does not come out of sleep with WAKE when the lockscreen is enabled. I found that if I disable the lockscreen altogether, then the WAKE key works perfectly fine. But as long as the keyguard is up, it does not WAKE at all. Of course the obvious solution is to disable the lockscreen, but I don't want to do this at all. So I was hoping that someone out there knows how to fix this (perhaps by editing a file that involves the keyguard).
Note: The application worked fine in CM9 Beta 1, but anything onwards it doesn't work. I think this has to do with the lockscreen widgets added in the newer releases of CM9.
Also, can anyone point me to the download link for CM9 Beta 1. I can't find it anywhere, but I'm pretty sure it still exists on their servers, but the links are simply gone. I was stupid and deleted the CM9 Beta 1 zip right before I upgraded to RC1. So at the very least I could flash Beta 1 to get everything working again.
So can anyone shed any light on how to fix my problem (besides disabling lockscreen)?
*bump
steven.smith said:
I've been running CM9 for several months now and I definitely love it and up until last week, I was running CM9 Beta 1. So I decided to upgrade this week to CM9 RC1 and everything went fine. Now the problem is that one of my applications is not working correctly. It is a custom application that listens for a side button press (using WAKE) then loads up the application before the lockscreen, and this is where my problem comes in.
For whatever reason, after upgrading to the latest CM9, my phone does not come out of sleep with WAKE when the lockscreen is enabled. I found that if I disable the lockscreen altogether, then the WAKE key works perfectly fine. But as long as the keyguard is up, it does not WAKE at all. Of course the obvious solution is to disable the lockscreen, but I don't want to do this at all. So I was hoping that someone out there knows how to fix this (perhaps by editing a file that involves the keyguard).
Note: The application worked fine in CM9 Beta 1, but anything onwards it doesn't work. I think this has to do with the lockscreen widgets added in the newer releases of CM9.
Also, can anyone point me to the download link for CM9 Beta 1. I can't find it anywhere, but I'm pretty sure it still exists on their servers, but the links are simply gone. I was stupid and deleted the CM9 Beta 1 zip right before I upgraded to RC1. So at the very least I could flash Beta 1 to get everything working again.
So can anyone shed any light on how to fix my problem (besides disabling lockscreen)?
Click to expand...
Click to collapse
I had all the beta's till it went RC so I deleted them sorry. Have you tried RC2 maybe it will work.
I had all the beta's till it went RC so I deleted them sorry. Have you tried RC2 maybe it will work.
Click to expand...
Click to collapse
I didn't even know RC2 was out. I just checked their download page and it still shows only RC1.
On another note I found that it is without a doubt a keyguard problem. The inbuilt keyguard on CM9 is blocking pretty much everything except for the power and volume keys. Trying to find out how to get around this without installing other software. Anyone have any idea how to do this by editting a file related to the keyguard?
Also, a link to CM9 Beta 1 would be tremendously helpful.
steven.smith said:
I didn't even know RC2 was out. I just checked their download page and it still shows only RC1.
On another note I found that it is without a doubt a keyguard problem. The inbuilt keyguard on CM9 is blocking pretty much everything except for the power and volume keys. Trying to find out how to get around this without installing other software. Anyone have any idea how to do this by editting a file related to the keyguard?
Also, a link to CM9 Beta 1 would be tremendously helpful.
Click to expand...
Click to collapse
http://download.cyanogenmod.com/?type=RC&device=epicmtd
Before I contact the developer of this app, I thought I'd check with the community first to see if this problem is widespread or not.
Basically, the problem is that the Restore Settings function doesn't restore the Notification Sounds for me. It does restore other settings, such as LED Colour, Vibration Pattern, without problems.
I'm using the latest version of Light Flow, 3.1.1 and currently running JBSourcery V2.1 ROM.
Other relevant details are:
1.) I use custom sounds that I store on the SD card under /sdcard/Notifications.
2.) I backup the current settings via the Backup function within the app and via TiBackup as well.
3.) After burning a new ROM, restoring data from either the TiBackup or Restore function within the app does not restore the notification sounds.
4.) I haven't fully tested this theory yet, but I believe if I choose a default sound that's included with Jelly Bean ROM (stored in /system/media/audio/notifications), then it works fine.
Anyone else having this problem?
tomtecs said:
Before I contact the developer of this app, I thought I'd check with the community first to see if this problem is widespread or not.
Basically, the problem is that the Restore Settings function doesn't restore the Notification Sounds for me. It does restore other settings, such as LED Colour, Vibration Pattern, without problems.
I'm using the latest version of Light Flow, 3.1.1 and currently running JBSourcery V2.1 ROM.
Other relevant details are:
1.) I use custom sounds that I store on the SD card under /sdcard/Notifications.
2.) I backup the current settings via the Backup function within the app and via TiBackup as well.
3.) After burning a new ROM, restoring data from either the TiBackup or Restore function within the app does not restore the notification sounds.
4.) I haven't fully tested this theory yet, but I believe if I choose a default sound that's included with Jelly Bean ROM (stored in /system/media/audio/notifications), then it works fine.
Anyone else having this problem?
Click to expand...
Click to collapse
This is a very late response but I am having the exact same issue pretty much...same thing with both Light Flow and Alarm Clock Plus...I received a response from the Light Flow dev that I'll share here in case someone like me finds this in a Google Search as well:
"Hi
I'm aware of this when doing a full wipe.
The ringtone picker is a standard element in android that'll be being used by both apps. It stores automatically a link to where the file is held in the media database.
When you wipe your phone it'll give new ids and this then causes the issue. I've looked into this before, but not yet found an elegant solution around the issue.
Cheers, Andrew"
Hi there,
First off I would like to thank AngSanley for his work on the 4.4.4 CM 11 ROM, absolutely excellent development and keep up the good work. Hopefully I thought I would make a bug report here since i still can't post in the X development section:
1. Phone.apk problems:
a. Operator and Caller names coincide with each other (Issue was mentioned before in the thread however still looking forward to hearing from @AngSanley for a reply)
b. Repeated Missing Calls crash the com.android.phone process and the only solution is to call the missing call to get the phone app running again. To emulate that leave the call until it ends twice and see what happens
2. System Processes
In Jelly Bean and Ice Cream Sandwich you were able to disable system stock apps such as Browser, email, messages and it was possible to install the playstore apps as a replacement. I was wondering if it's still possible to enable that in the current ROM or it's not a bug as of the new releases.
Note: This also includes Trebuchet since I'm not currently using it.
3. Reboots in some cases disables the home button action in UDNB and prevents the lockscreen process from running properly which requires me to reinstall the ROM and Gapps while clearing cache and Delvik or by force stop and enabling lockscreen (which gets me to problem 2 sometimes).
Thank you again for the ROM and looking forward to hearing about upcoming updates with the ROM.
For the first issue, the problem is known. I mentioned it but it's difficult to fix.
For the third issue though, I found a solution. I disabled UDNB and installed Soft Buttons app. If the buttons crash, I disable them from the app and immediately enable them again. I reboot and... that's all!
(as for the second, I use some stock apps, so I can't tell you for sure)
Sent from Tapatalk via Nokia X
For the first issue, the problem is known. I mentioned it but it's difficult to fix.
Click to expand...
Click to collapse
Hopefully it gets addressed because it makes the phone literally unusable. The current list by AngSanley doesn't show it so I hope it's addressed to him.
For the third issue though, I found a solution. I disabled UDNB and installed Soft Buttons app. If the buttons crash, I disable them from the app and immediately enable them again. I reboot and... that's all!
Click to expand...
Click to collapse
Any specific app on the playstore because there are many apps for it
(as for the second, I use some stock apps, so I can't tell you for sure)
Click to expand...
Click to collapse
No problem it's fine. The imitation of it can be made if you even disable messages for example. It shows immediately that the phone loses functionality especially in the lockscreen process.
I'm really looking forward to hearing from @AngSanley on these. Especially on the phone process issue .
ElementalXY said:
Any specific app on the playstore because there are many apps for it
Click to expand...
Click to collapse
Couldn't attach it from Tapatalk. Here you are!
(Note that you MUST disable UDNB from Settings > Apps first, because the phone will show you 2 navbars!)
plankton69 said:
Couldn't attach it from Tapatalk. Here you are!
(Note that you MUST disable UDNB from Settings > Apps first, because the phone will show you 2 navbars!)
Click to expand...
Click to collapse
Thank you very much . It's working well and even better than UNDB!
PS: I can now post in the development section so is it possible to repost it over there instead or wait for AngSanley?
Yea bro....ur all mentioned bugs are also happend with the me... and there is also a big problem.... this bug happed with me two times and i need to wipe dalvik cacke two times....
so that problem is when i install xpossed app n when i restart than the statusbar gone.. it says com.androd.systemui.apk stopped... plz find way to fix it without wipe dalcik cacke
n second problem is whn i install any new theme n appy n restart my phone than same happens.... please do something brohers... love this rom ... really awsm..
Yea bro....ur all mentioned bugs are also happend with the me...
Click to expand...
Click to collapse
Does the phone crash happen with you too in missed calls? If not then I honestly think I should wipe the phone haha.
yes... i also get that error phone procced stopped.... but i pressed ok button 4 5 times and its stopped... but if i donwload any cm theme and after appy it when i restart mob the process of sytemui stopped than i need to to wipe data that time tht ok button not working.. please find any trick repair it without formating data..
ElementalXY said:
Does the phone crash happen with you too in missed calls? If not then I honestly think I should wipe the phone haha.
Click to expand...
Click to collapse
You should. Do a full wipe before flashing CM11.
Dom3616 said:
You should. Do a full wipe before flashing CM11.
Click to expand...
Click to collapse
Unfortunately I won't be able to do that since I just bricked my phone while formatting to the original stock version lol. I'm currently stuck on Nokia Emergency Connectivity and will be sending it to the Nokia care center next month haha. I'll be doing a fresh install when I get it back.
PS: I'm guessing no solutions for this problem outside the warranty am I right?
ElementalXY said:
Unfortunately I won't be able to do that since I just bricked my phone while formatting to the original stock version lol. I'm currently stuck on Nokia Emergency Connectivity and will be sending it to the Nokia care center next month haha. I'll be doing a fresh install when I get it back.
PS: I'm guessing no solutions for this problem outside the warranty am I right?
Click to expand...
Click to collapse
Yes you are right.
Installation Instructions:
https://wiki.cyanogenmod.org/w/Install_CM_for_ls970
Click to expand...
Click to collapse
Changelog:
20160814:
Updated using branch cm-12.120160127:
Updated to CM-12.1 using codebase cm-12.1-YOG7D
Updated libs from mako, which fixes GPS, Encryption, & some dirty log messages.
Click to expand...
Click to collapse
Special Thanks:
Looking at the commit log, I've got to say thank you to Shelnutt2 and Ricardo Cerqueira. Seth, for his work on porting this device & permission to post this build, and Richardo for maintaining the gproj kernel.
Click to expand...
Click to collapse
I've been using this with Ting. Seems more stable than the CM-11 build that I was using. Mms & cell data are the two things that do not work out of the gate for me. Wondering how this shapes up with Sprint. I vaguely remember cell data working, but I don't think the default mms app did. However, I was able to use a third party mms app for pictures.
If this works well for people I'll see what I can do about getting my changes pulled upstream.
XDA:DevDB Information
UNOFFICIAL CM12.1 for LS970, ROM for the Sprint LG Optimus G
Contributors
fuzzy7k, Shelnutt2, Ricardo Cerqueira
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Testing
Created 2016-01-28
Last Updated 2016-08-17
What gapps version to use?
Thanks for providing this! I've installed it, to replace my cm-12-20151108-NIGHTLY-ls970.zip ROM. But I haven't been able to find a gapps download that will work with this (all Google services keep crashing) or fail to installed (Status 6). Any help will be appreciated.
Thanks!
gapps version
I was able to get this working. After battling through a barrage of pop-up messages telling me that various google apps had crashed (repeatedly for each one), I got into Play Store and did an update all. I had to uninstall/reinstall Keep and Messenger, and now all seems well.
The only thing I'm currently having a problem with is Titanium Backup, which keeps crashing no matter what I've tried.
Otherwise, all seems to be working well. I'm hoping that a the flaky problems I was having with the previous CM-12 ROM will be fixed with this version.
For whatever reason, no matter what version of CM12 I install, wifi does not work. I'll put in the password and then it times out "failing to authenticate." Have you run into this issue? Any known fixes?
For whatever reason, no matter what version of CM12 I install, wifi does not work. I'll put in the password and then it times out "failing to authenticate."
Click to expand...
Click to collapse
My wifi is working. With the previous CM12 install I did have a problem where wifi would stop working after it was connected ("!" next to the wifi indicator), and I'd have to turn the wifi off and on again to fix it. I haven't experienced that problem yet with this build, though it's too soon to know if that problem has gone away.
geodosch said:
My wifi is working. With the previous CM12 install I did have a problem where wifi would stop working after it was connected ("!" next to the wifi indicator), and I'd have to turn the wifi off and on again to fix it. I haven't experienced that problem yet with this build, though it's too soon to know if that problem has gone away.
Click to expand...
Click to collapse
Yeah I just went through unrooting and going to stock (where it worked fine) and now tried again to install without luck. I don't understand this problem or what could possibly be the issue at this point.
Edit: I have noticed that I'm not seeing my 5 GHz network although it was available in stock.
Profile switcher
It seems the option to switch profiles from the power button is gone. In the settings for buttons, there's an option to show "Airplane Mode", but not the profile selector. I do have multiple profiles created, so it's not because of that.
geodosch said:
I was able to get this working. After battling through a barrage of pop-up messages telling me that various google apps had crashed (repeatedly for each one), I got into Play Store and did an update all. I had to uninstall/reinstall Keep and Messenger, and now all seems well.
The only thing I'm currently having a problem with is Titanium Backup, which keeps crashing no matter what I've tried.
Otherwise, all seems to be working well. I'm hoping that a the flaky problems I was having with the previous CM-12 ROM will be fixed with this version.
Click to expand...
Click to collapse
Hey geodosch, same experience here with pop up errors with one difference, I was not able to get into Play Store... I only have four com.google.* green droid icons, and after clicking them I get 'App isn't installed'. Which gapps did you install, any other tips?
Many thanks!
I tried quite a few, but the one I eventually used was downloaded from opengapps.org. Select ARM; 5.1; Micro. You may want to use a different variant based on your needs. The details of what's in each is here.
The filename for the one I used is 'open_gapps-arm-5.1-micro-20160304.zip'
I don't recall anything else special I needed to do. I hope this helps!
A couple of issues
I've found was appears to be a bug in the call log. Whenever I make an outgoing call, the call log shows an incoming call at the same time, with the ID of "unknown".
The other is an intermittent problem, which I haven't been able to determine how to reproduce. Sometimes the screen will go black, with the exception of the top status bar. I've had it happen when unlocking the phone, and also when opening a new app. Once this occurs, I've only been able to recover by rebooting. Holding the power button does bring-up the reboot screen, and as mentioned the status bar is fine, so it doesn't appear to be related to the display driver. I also took a screenshot when it was in this state, and the image is what the screen looks like: black with a status bar.
Sorry for the seemingly silly question, but where is the download? Following the link leads me to a wiki which leads me to a nightly build from mid 2015.
curiousGeorge said:
Sorry for the seemingly silly question, but where is the download? Following the link leads me to a wiki which leads me to a nightly build from mid 2015.
Click to expand...
Click to collapse
Did you click the "Downloads" tab near the top of this topic? (Between "Discussion" and "Reviews") There should be a link there to "cm-12.1-20160127-UNOFFICIAL-ls970.zip", dated 2016-01-28.
Thanks for the tip on where to find the download. This is actually a really clever thing to do; integrating the download into the forum navigation itself.
geodosch said:
I tried quite a few, but the one I eventually used was downloaded from opengapps.org. Select ARM; 5.1; Micro. You may want to use a different variant based on your needs. The details of what's in each is here.
The filename for the one I used is 'open_gapps-arm-5.1-micro-20160304.zip'
I don't recall anything else special I needed to do. I hope this helps!
Click to expand...
Click to collapse
I'm having a lot of trouble getting Google Apps installed. I get the messages about the failures, but no Google Play store appears. I've tried on the latest "nano" release -- I'll try the exact file you mentioned.
One difference may be that I'm on TWRP 2.8.3.0 -- what's your recovery? Mine cries foul about no SELinux context support in the kernel, and I also noticed the Gapps blob said something about fixing SELinux permissions (it doesn't report success or failure). After installation there are 4 or 5 "google logo" icons that don't do anything, labeled com.android.google.whatever that don't open, instead claiming "XXX isn't installed" where XXX is the name of the app. Another poster here said the same. Anyway, I'll try that particular file and cross my fingers!
Edit: nope. Transferred the Gapps zip to the storage, booted into recovery, wiped everything except internal storage, flashed the ROM, flashed the GApps, reboot. Still get a bunch of green lifeless icons that won't load any app. What to do?
Ah, looks like I was right. It's the silly SELinux thing. The trick is to go here http://forum.xda-developers.com/showthread.php?t=2524485 and set the phone to permissive. Which you can totally do because you can go into the build info and click build number until you get "developer mode" enabled and enable root access in apps. Then everything works perfectly, even from a seemingly glitched install, regardless of GApps version. Pretty nice eh?
I'm gonna let everything update and then try reenabling SELinux, for kicks.
[edit]Ah, rebooting screws everything up again until the SELinux changer finally loads and changes things to permissive. So it doesn't exactly stick at boot. Still looking for a permanent fix...
curiousGeorge said:
Thanks for the tip on where to find the download. This is actually a really clever thing to do; integrating the download into the forum navigation itself.
I'm having a lot of trouble getting Google Apps installed. I get the messages about the failures, but no Google Play store appears. I've tried on the latest "nano" release -- I'll try the exact file you mentioned.
One difference may be that I'm on TWRP 2.8.3.0 -- what's your recovery? Mine cries foul about no SELinux context support in the kernel, and I also noticed the Gapps blob said something about fixing SELinux permissions (it doesn't report success or failure). After installation there are 4 or 5 "google logo" icons that don't do anything, labeled com.android.google.whatever that don't open, instead claiming "XXX isn't installed" where XXX is the name of the app. Another poster here said the same. Anyway, I'll try that particular file and cross my fingers!
Edit: nope. Transferred the Gapps zip to the storage, booted into recovery, wiped everything except internal storage, flashed the ROM, flashed the GApps, reboot. Still get a bunch of green lifeless icons that won't load any app. What to do?
Click to expand...
Click to collapse
I'm running ClockworkMod 6.0.4.7. It's been a while since I originally installed the CM ROM, but I know I didn't have any luck with TWRP, though I can't say for certain that it was at fault... it may have been due to some other issue which I later fixed, and switching to CWM may have been incidental.
I've found that using the official CM recovery fixed my gapps woes.
On another note, GPS isn't working for me.
So, I totally didn't see any notifications that this thread was active. I've been working on trying to get Marshmallow up and ran into a dead end. So, I came here.
geodosch said:
I've found was appears to be a bug in the call log. Whenever I make an outgoing call, the call log shows an incoming call at the same time, with the ID of "unknown".
Click to expand...
Click to collapse
Same here, although it doesn't do it for all callers, I'll rebase on the newest code and see that does the trick.
geodosch said:
The other is an intermittent problem, which I haven't been able to determine how to reproduce. Sometimes the screen will go black, with the exception of the top status bar. I've had it happen when unlocking the phone, and also when opening a new app. Once this occurs, I've only been able to recover by rebooting. Holding the power button does bring-up the reboot screen, and as mentioned the status bar is fine, so it doesn't appear to be related to the display driver. I also took a screenshot when it was in this state, and the image is what the screen looks like: black with a status bar.
Click to expand...
Click to collapse
I experienced the same. Although, I haven't in some time, since I stopped trying to use multiple profiles, that must contribute. adb still works as well, and I tracked the error in the code and it was right next to a TODO item. Go figure. If you see it again and are next to a computer, see if you can't get a logcat so I can check on that code again.
geodosch said:
It seems the option to switch profiles from the power button is gone. In the settings for buttons, there's an option to show "Airplane Mode", but not the profile selector. I do have multiple profiles created, so it's not because of that.
Click to expand...
Click to collapse
It's there, under "Power menu". Just search for power.
Nicene Nerd said:
On another note, GPS isn't working for me.
Click to expand...
Click to collapse
I read somewhere that you may need to get a lock in a ZVC build before flashing. Try that. It sounded like hog wash to me, and didn't work when I tried it. But, after updating the libs, all was fine. So, maybe both conditions must be met. On a positive note, I rarely have GPS enabled, but when I flip the switch, it comes on. So, it's not like you need to leave it on across reboots.
fuzzy7k said:
So, I totally didn't see any notifications that this thread was active. I've been working on trying to get Marshmallow up and ran into a dead end. So, I came here.
Click to expand...
Click to collapse
fuzzy7k said:
Same here, although it doesn't do it for all callers, I'll rebase on the newest code and see that does the trick.
Click to expand...
Click to collapse
Glad to see you taking I look here. I really don't want to replace my Optimus G, since all phones now seem to be either low-end performance or over-sized. So I'm glad I can still keep mine going with these builds.
fuzzy7k said:
I experienced the same. Although, I haven't in some time, since I stopped trying to use multiple profiles, that must contribute. adb still works as well, and I tracked the error in the code and it was right next to a TODO item. Go figure. If you see it again and are next to a computer, see if you can't get a logcat so I can check on that code again.
Click to expand...
Click to collapse
I hadn't tried adb before rebooting (Murphy's Law: whenever it happened I was often doing some time-constrained task, so I just rebooted as quickly as I could.) But the next time it happens I'll connect and check the logs. It's interesting that you mention multiple profiles, because it seems to have happened several times in my car, and I have profiles set-up to switch when the car bluetooth connects/disconnects.
If you're going to be poking around in the code, another issue that I've been having is the default app for the browser no longer seems to work consistently. I know this worked on an older CM12 build, and think it used to work on this one. But when something launches a browser I'm very often prompted for which one (Chrome or Browser.)
---------- Post added at 08:13 PM ---------- Previous post was at 08:11 PM ----------
fuzzy7k said:
It's there, under "Power menu". Just search for power.
Click to expand...
Click to collapse
In the power menu, I see an option to switch users (which is disabled, since I don't have multiple users set-up), but I don't see an option for Profiles.