BACKUP YOUR EFS THROUGH FREEGEE AND/OR TWRP
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is a preview of CM-12.0 built entirely from CM sources. There are few modifications (listed below in features).
Features
- Settings->About Phone->CyanogenMod updates uses wfhome.net servers (my builds)
Latest Build
I have started Nightly's
Downloads
Latest Builds
http://goo.gl/kQP3f8 - Private Hosting (no ads, no waiting, enjoy)
Old Builds
http://goo.gl/Sz2K7a - Android File Host
Google Apps
http://forum.xda-developers.com/android/software/gapps-google-apps-flashable-package-t2930266
TWRP - 2.8.3.0
http://teamw.in/project/twrp2/155
Known Issues
- "No SIM Card" message on lock screen (CM12 issue)
- Built in Messenger App doesn't work right (CM12 issue)
- Nothing else that I have noticed
All changes can be viewed on the CyanogenMod gerrit.
Thanks to all who have developed CyanogenMod and the device and kernel trees for the Optimus G.
I'm using a modified version of @JulianXhokaxhiu CyanogenModOTA tools on my web server.
https://github.com/julianxhokaxhiu/CyanogenModOTA
Source
http://github.com/CyanogenMod
http://github.com/rjwil1086
The E970 and LS970 are slightly different, have you used the LS970 sources to build? The LS970 has minor differences in the camera as well as it being CDMA and not requiring a SIM card. Are these taken into affect? I am going to test because this is actually based on US hardware so I am hoping for most things to work that do not because other builds are based from international versions.
dopy25 said:
The E970 and LS970 are slightly different, have you used the LS970 sources to build? The LS970 has minor differences in the camera as well as it being CDMA and not requiring a SIM card. Are these taken into affect? I am going to test because this is actually based on US hardware so I am hoping for most things to work that do not because other builds are based from international versions.
Click to expand...
Click to collapse
I did use the LS970 sources. I have AT&T and Sprint phones (just not an LS970) so I am aware of the network differences. I am also aware of the 13MP camera the LS970 has. This is built entirely with CM sources (I'm using a fork of http://github.com/TheMuppets for vendor blobs; I added some gps blobs to get gps working). The device tree for these two phones share a lot of stuff as they are broken into 3 repositories (gproj-common, ls970-common, and ls970). The e970 also uses gproj-common and ls970-common which are about 95% of the device tree code for both phones. There is already a CM-12.0 branch on github for the ls970 so I'm assuming it was updated just like the e970. Just need someone with hardware to check it out.
rjwil1086 said:
I did use the LS970 sources. I have AT&T and Sprint phones (just not an LS970) so I am aware of the network differences. I am also aware of the 13MP camera the LS970 has. This is built entirely with CM sources (I'm using a fork of http://github.com/TheMuppets for vendor blobs; I added some gps blobs to get gps working). The device tree for these two phones share a lot of stuff as they are broken into 3 repositories (gproj-common, ls970-common, and ls970). The e970 also uses gproj-common and ls970-common which are about 95% of the device tree code for both phones. There is already a CM-12.0 branch on github for the ls970 so I'm assuming it was updated just like the e970. Just need someone with hardware to check it out.
Click to expand...
Click to collapse
Great! Sounds like you know what you are doing. I am downloading it right now and am at 20%. I will flash when done and absolutely report back.
EDIT FOR FINDINGS
@rjwil1086 GREAT JOB! The ROM is working great on my device (LS970) so I will send some feedback
PROS
1) Everything seems to work for the most part except items listed under CONS.
2) Calls and data are working from flashing, no extra steps needed to achieve calls or data. 4G coverage included.
3) Superuser is integrated (THANK YOU)
4) Camera works superb, even quality is amazing. (see cons)
5) Voicemail by long pressing one works and on other CM12 does not.
6) You can turn on "flash" while video recording so you have overhead light. Maybe I've missed that in every other ROM but that's great! (Does not cause phone to power down, see #6 cons)
CONS
1) Messaging app does not send a text from within the built in app (Quick reply works fine) I think this is CM issue and not device because it is in all CM based roms currently.
2) Swipe texting does not work with built in keyboard.
3) No SIM card appears in notification bar on lock screen (once again in other CM12 ROMS).
4) Data usage is not tracked at all, it says no apps used data right after I used the browser and the Play Store to download something.
5) NEW FINDINGS:: Phone calls will not end, pressing the end icon only makes the end option go away but the phone call is still in progress. I tried using a bluetooth headset and only the device. My work around is to enable Airplane Mode then disable it, that shuts the phone call off.
6) using flash in any camera app causes device to power off, overhead light during video recording is fine though.
7) Volume control on screen lock is not possible. You must unlock the screen to alter the volume (notable in music playing)
8) Very important!! While making a call, the phone immediately disconnects. When I call back, the other caller is still connected so it goes to voicemail. I have to ask them to ignore the first call so I can make it again. This happens every time and is very difficult to manage since I have to enable airplane mode to end the call.
On another note, I am using the Multiboot method and have this installed as primary, I haven't tested any secondary ROMs but I do not expect them to boot and that is due to a specific patch being required for the kernel that is not compatible with gproj. Also, it will not install as secondary, it fails upon flashing. The only thing I noticed is that it takes awhile longer at the boot screen to get past it than other roms. No issues though since it works to my expectations.
I will continue to use this to see if anything else comes up, but over all this is awesome. I look forward to CM fixing things upstream. Please keep those builds coming, they work.
Looks good. Once those CM bugs get worked out, this ROM will be fantastic! Thank you for this ROM! Willing to test any new updates. Seems like dopy did a pretty solid review so far.
This ROM running Android Lollipop 5.0?
RegKilla said:
This ROM running Android Lollipop 5.0?
Click to expand...
Click to collapse
Yes, CM12 is 5.0 (in this case 5.0.1)
EDIT: @rjwil1086 ...
GREAT JOB ON THAT UPDATE. I'm not sure if it was you that fixed it or CM fixes, but some of the previous issues are gone. Now this is extremely stable. I definitely recommend it to anyone with an LS970.
Fixed issues: (calls are main thing fixed)
1) Calls end perfectly fine
2) Phone no longer shuts off at flash of the camera.
3) no issues with music. (I didn't mention it before but when I would try to play music from any app, it would say it was playing but the song would not progress and there was no sound. I also attributed it to my bluetooth headset, but now the issue is gone)
4) Adaptive brightness and notification bar brightness adjustment has always worked with this ROM. (basically all aspects of brightness work)
still existing issues
1) Volume control on inactive lock screen. (still have to turn on screen)
2) Data usage still not tracked by settings/data usage.
3) messaging app will not show active send, pressable icon (cannot send text from within the app but quick reply still works) (I'm certain CM issue)
4) Swipe texting with built in keyboard (most likely CM issue)
5) Not really an issue but lock screen still says "No SIM card" (CM issue?)
Great update, more than half of the major issues have been fixed, now it seems like mostly CM issues , and not even major problems.
dopy25 said:
Yes, CM12 is 5.0 (in this case 5.0.1)
EDIT: @rjwil1086 ...
GREAT JOB ON THAT UPDATE. I'm not sure if it was you that fixed it or CM fixes, but some of the previous issues are gone. Now this is extremely stable. I definitely recommend it to anyone with an LS970.
Fixed issues: (calls are main thing fixed)
1) Calls end perfectly fine
2) Phone no longer shuts off at flash of the camera.
3) no issues with music. (I didn't mention it before but when I would try to play music from any app, it would say it was playing but the song would not progress and there was no sound. I also attributed it to my bluetooth headset, but now the issue is gone)
4) Adaptive brightness and notification bar brightness adjustment has always worked with this ROM. (basically all aspects of brightness work)
still existing issues
1) Volume control on inactive lock screen. (still have to turn on screen)
2) Data usage still not tracked by settings/data usage.
3) messaging app will not show active send, pressable icon (cannot send text from within the app but quick reply still works) (I'm certain CM issue)
4) Swipe texting with built in keyboard (most likely CM issue)
5) Not really an issue but lock screen still says "No SIM card" (CM issue?)
Great update, more than half of the major issues have been fixed, no it seems like mostly CM issues , and not even major problems.
Click to expand...
Click to collapse
Yup all those were fixed by CM developers. I saw several CDMA fixes in the ril code. I'm sure there were more elsewhere in the code. Swipe on the keyboard is disabled in CM because it doesn't work on any of my devices.
rjwil1086 said:
Yup all those were fixed by CM developers. I saw several CDMA fixes in the ril code. I'm sure there were more elsewhere in the code. Swipe on the keyboard is disabled in CM because it doesn't work on any of my devices.
Click to expand...
Click to collapse
So the 12/20/14 build fixes those bugs?
Downloading now. Thank you for this again! Breathes some life into this old phone lol.
Edit; I would just like to add; you sir, have made me love cyanogenmod once again.
I use to use CM 10.2 all the time, but honestly, when the official CM11 came out with LS970 sources, it always felt, not laggy, but not responsive. As in just sluggish. Gee Roms always ran fast on my optimus, but always over heated easily too.
I absolutely love this ROM. It is extremely fast and uses LS970 sources. I can finally leave stock confidently. Is there anyway I can repay you? I am on mobile, so I can't see much, but do you have a donation link? I'd pay to keep this going.
Fantastic job. It works great!
Never had this much responsiveness on a LS970 cm ROM before.
Edit 2: Does anyone know how to disable mobile data? I like to turn it off so it doesn't suck battery in low service areas. Thanks again.
Whiplashh said:
Edit; I would just like to add; you sir, have made me love cyanogenmod once again.
I use to use CM 10.2 all the time, but honestly, when the official CM11 came out with LS970 sources, it always felt, not laggy, but not responsive. As in just sluggish. Gee Roms always ran fast on my optimus, but always over heated easily too.
I absolutely love this ROM. It is extremely fast and uses LS970 sources. I can finally leave stock confidently. Is there anyway I can repay you? I am on mobile, so I can't see much, but do you have a donation link? I'd pay to keep this going.
Fantastic job. It works great!
Never had this much responsiveness on a LS970 cm ROM before.
Edit 2: Does anyone know how to disable mobile data? I like to turn it off so it doesn't suck battery in low service areas. Thanks again.
Click to expand...
Click to collapse
I agree, it is definitely snappier than any ROM I've ever used on this phone.
As far as data, I don't know. I tried a few widgets and shortcuts to no avail. I'm sure it's a matter of time before it's enabled in settings from CM.
I did have some partial success with quick shortcut maker. Run a search for "data" and try to use the shortcut to data roaming under "phone." What it did was say settings has force closed, but it shut off my mobile data. It caught me off guard but a reboot turned it back on.
On the plus side, battery life is pretty wicked already.
dopy25 said:
I agree, it is definitely snappier than any ROM I've ever used on this phone.
As far as data, I don't know. I tried a few widgets and shortcuts to no avail. I'm sure it's a matter of time before it's enabled in settings from CM.
I did have some partial success with quick shortcut maker. Run a search for "data" and try to use the shortcut to data roaming under "phone." What it did was say settings has force closed, but it shut off my mobile data. It caught me off guard but a reboot turned it back on.
On the plus side, battery life is pretty wicked already.
Click to expand...
Click to collapse
Even with data on the battery is good? That's awesome!
Just a heads up, the build does still have some phone issues. Can't call on first try and hangup without hitting airplane mode. Calls coming in work perfectly, but out can be a hassle.
Whiplashh said:
Even with data on the battery is good? That's awesome!
Just a heads up, the build does still have some phone issues. Can't call on first try and hangup without hitting airplane mode. Calls coming in work perfectly, but out can be a hassle.
Click to expand...
Click to collapse
From what I've noticed, it is absolutely great on battery. I'll post some screen shots. I was in and out of 3/4G. Downloaded a few files, probably 500mb worth. Played tapped out, which is a freaking battery hog. And still lasted a whole day. I did just notice that the total hours don't seem to be tracked, that's odd.
On the phone thing, I am so sorry you're still having that issue, it is gone for me. Are you sure you're on the 12/20 build? Maybe we did something different.
I flashed the 12/18 and GApps since I tried it first (then restored the backup of it because I had since flashed another ROM and neither would work as secondary on my multi boot setup) then I flashed the 12/20 build to update (dirty flash over 12/18) cleared cache's twice because I like to. And it seemed to work. That's a real bummer that it doesn't work for you. Incoming or outgoing work fine for me, for now anyway.
screen shots I'll have to post later, I always have issues doing that on my phone
dopy25 said:
From what I've noticed, it is absolutely great on battery. I'll post some screen shots. I was in and out of 3/4G. Downloaded a few files, probably 500mb worth. Played tapped out, which is a freaking battery hog. And still lasted a whole day. I did just notice that the total hours don't seem to be tracked, that's odd.
On the phone thing, I am so sorry you're still having that issue, it is gone for me. Are you sure you're on the 12/20 build? Maybe we did something different.
I flashed the 12/18 and GApps since I tried it first (then restored the backup of it because I had since flashed another ROM and neither would work as secondary on my multi boot setup) then I flashed the 12/20 build to update (dirty flash over 12/18) cleared cache's twice because I like to. And it seemed to work. That's a real bummer that it doesn't work for you. Incoming or outgoing work fine for me, for now anyway.
screen shots I'll have to post later, I always have issues doing that on my phone
Click to expand...
Click to collapse
I clean flashed the 12/20 build. Wiped everything twice because thats how I do. Had to go back to stock so I could make calls and organize a friends bday party. Hopefully this flash will be better.
Whiplashh said:
I clean flashed the 12/20 build. Wiped everything twice because thats how I do. Had to go back to stock so I could make calls and organize a friends bday party. Hopefully this flash will be better.
Click to expand...
Click to collapse
The weird thing is, it's happening intermittently for me as well. But it seems more like making calls from the first call screen. Selecting recents seems to not do it. Also seems like it happens more when LTE is on. I haven't tried switching to 3G only but it dedi definitely didn't do it when I only have 3G.
dopy25 said:
The weird thing is, it's happening intermittently for me as well. But it seems more like making calls from the first call screen. Selecting recents seems to not do it. Also seems like it happens more when LTE is on. I haven't tried switching to 3G only but it dedi definitely didn't do it when I only have 3G.
Click to expand...
Click to collapse
It just happens all the time. I'm using CWM recovery so I don't know if that effects it. Hopefully it will work out soon. That and the messaging bug. Loving the ROM so far. Once those 3 things are fixed, this phone won't see stock again lol.
(Data toggle, messaging send which IS a cm thing, and the phone issue).
Whiplashh said:
It just happens all the time. I'm using CWM recovery so I don't know if that effects it. Hopefully it will work out soon. That and the messaging bug. Loving the ROM so far. Once those 3 things are fixed, this phone won't see stock again lol.
(Data toggle, messaging send which IS a cm thing, and the phone issue).
Click to expand...
Click to collapse
I can only assume that recovery shouldn't be an issue as long as it's semi up to date. But some people are having sensor issues on all other builds and it very well could be related, I don't know enough on the subject. I will keep up on this because this ROM really is slick. I use textra for messaging but I really like the built in messenger. Google messenger is almost identical but has MMS issues. Nothing on textra, it works perfectly. So I'm still using this daily. I'm sure data toggle will go in soon. I see an APN update in the change log so I'm sure it's coming soon. I'll keep you updated.
dopy25 said:
I can only assume that recovery shouldn't be an issue as long as it's semi up to date. But some people are having sensor issues on all other builds and it very well could be related, I don't know enough on the subject. I will keep up on this because this ROM really is slick. I use textra for messaging but I really like the built in messenger. Google messenger is almost identical but has MMS issues. Nothing on textra, it works perfectly. So I'm still using this daily. I'm sure data toggle will go in soon. I see an APN update in the change log so I'm sure it's coming soon. I'll keep you updated.
Click to expand...
Click to collapse
Thank you!
Whiplashh said:
Thank you!
Click to expand...
Click to collapse
Give today's build a shot. I just made about 10 phone calls to various numbers from various locations within the dialer and all connected the first time, and disconnected fine.
There is still no data toggle, but data is now being tracked (or at least showing that it was previously tracked) I also do not see any apn settings but that might not have been an update for our device that I saw.
Messaging still does not send from within the app but quick reply is fine (I use Textra SMS and everything works in it)
If there's anything else you want me to check just say the word. I wonder if it's a cache issue with the dialer or something causing the phone to misbehave, but it seems to be working fine now.
dopy25 said:
Give today's build a shot. I just made about 10 phone calls to various numbers from various locations within the dialer and all connected the first time, and disconnected fine.
There is still no data toggle, but data is now being tracked (or at least showing that it was previously tracked) I also do not see any apn settings but that might not have been an update for our device that I saw.
Messaging still does not send from within the app but quick reply is fine (I use Textra SMS and everything works in it)
If there's anything else you want me to check just say the word. I wonder if it's a cache issue with the dialer or something causing the phone to misbehave, but it seems to be working fine now.
Click to expand...
Click to collapse
That's one down. Like I said, I love this ROM. The camera is AMAZING. I'll test it and see what happens.
Related
my wife has the att nitro hd, when the screen goes off during a call sometimes nothing including power button will turn it back on. Anyone know of a fix? did the ATT small update fix this?
Actually it comes back on after a long minute or two. Not very helpful if you need the dialpad or keys, etc.
I have just rooted it for her and installed CWM.
I have added a few proximity tweaks to build.prop
gsm.proximity.enable=false (rebooted twice but screen still goes off)
also used the ro.lg.proximity and the mot.lge.proximity (dont recall exact wording) both were set to a value of 5.
I'll have to take alook into the lg hidden dialer menu to see if I can disable this.
I dont like this sensor on my device either, but I have an option in settings to disable it, which makes it bearable.
thanks for the help guys.
I have noticied LG throws together some junky builds, typos, bad english/grammar. Wonky sensors etc. Incorrect kernel build ReadMe's
I thought I recall someone with another device just placing a peice of tape over the sensor. hmmm..worth a try.
cheers.
chrisrotolo said:
gsm.proximity.enable=false (rebooted twice but screen still goes off)
also used the ro.lg.proximity and the mot.lge.proximity (dont recall exact wording) both were set to a value of 5.
Click to expand...
Click to collapse
Congrats. Today, you learned that most of the "tweaks" found at XDA are utter bull****
aremcee said:
Congrats. Today, you learned that most of the "tweaks" found at XDA are utter bull****
Click to expand...
Click to collapse
What about the tweaks that aren't BS? Are they already included in your CM9 builds?
From what I can tell, pretty much the main thing that build.prop is good for is providing information about the system and software (i.e. info about the build). It's not really used much for useful configurations as far as I know.
networks tweaks actually have doubled me download speed.
I still have faith.
but can anyone answer my questions I posted in ICS SLim thread and PM'ed Andasa , no responses yet.
does ICS slim or CM9 have option to keep lcd no during call? and does it work??
what's working not working? I found changelogs but not a working/not working list for CM9.
and has anyone successfully restored a nandroid from ICS to GB without real issues?
thanks guys.
i doubt the ota fixed your issue as the issue is not one that occurs for every nitro.
I can tell you that when I make a phone call they screen stays no.
what's working not working, well, many of us are running it daily with no probs.
as you prolly know, it is a nightly build so a public list of what's working or not isn't rly part of the deal.
i've succesfully restore a nandroid from both slim and cm9 back to the stock att rom and others many many times. dozens.
thanks good enough.
I will have to give it a go.
would you recommend one or the other?
CM9 or slim?
thank you.
well, I like them both a lot. slim is just a trimmed down version of cm9 and i _think_ it does run just a bit snappier........maybe..but it's not wildly different from cm9. I usually switch back&forth throughout the day.
There's no setting in CM9 to disable the proximity sensor, although there may be a way to do it.
We just got a Nitro HD for my wife and her phone also has this issue. I have not gotten to know the phone well enough to try rooting or anything else of that nature, it's pure stock.
When she makes a call the screen turns off immediately after hitting the call button and will not wake up. When she receives a call we get a glimpse of the in-call screen with the various buttons etc but then the screen turns off. If the other party hangs up her screen turns back on, but if she calls something automated, like voicemail, she can't do anything except pull the battery to disconnect.
I've tried putting my thumb over the proximity sensor, hitting all buttons including power, and nothing makes the screen wake up or turns the phone off other than a battery pull.
The phone was running a build from last November when we first got it (V10i?) and today prompted us to update, so I did that hoping it would solve the problem. The phone is currently on V10j, but the problem persists.
Any help?
no driver said:
We just got a Nitro HD for my wife and her phone also has this issue. I have not gotten to know the phone well enough to try rooting or anything else of that nature, it's pure stock.
When she makes a call the screen turns off immediately after hitting the call button and will not wake up. When she receives a call we get a glimpse of the in-call screen with the various buttons etc but then the screen turns off. If the other party hangs up her screen turns back on, but if she calls something automated, like voicemail, she can't do anything except pull the battery to disconnect.
I've tried putting my thumb over the proximity sensor, hitting all buttons including power, and nothing makes the screen wake up or turns the phone off other than a battery pull.
The phone was running a build from last November when we first got it (V10i?) and today prompted us to update, so I did that hoping it would solve the problem. The phone is currently on V10j, but the problem persists.
Any help?
Click to expand...
Click to collapse
If you bought it from a store, get it exchanged for a new one.
actually works much faster on cm9, but therr still should be an optin to keep lcd on during call. i found some free apps that will disable hardware drivers but cant find the name of the proximity sensor driver, only that is named LGE.
Unfortunately it was given to us by a friend after my wife lost her Captivate, so taking it to a store to exchange is probably not going to work too well. As far as I can tell it was never used before we got it--the battery was still in it's own sealed pouch, the texting and driving warning was on the phone, and the phone went through the whole initial setup routine--but they didn't send us the box, I guess to cut down on mailing costs. I was hoping there was a known solution.
Ok, I downloaded two proximity sensor test apps today, but neither showed any activity. On my Captivate I get different readings with Proximity Sensor Finder (market link), but on the Nitro it is stuck at 3cm and it doesn't register anything no matter where I put my hand over the phone.
Can someone whose phone works right try installing this app and make sure that it picks up different readings on this device? OP, if you are still having issues, can you also try this app and see if it is static for you?
Thanks.
Took off the screen protector that they installed at the AT&T store and now the proximity sensor works just fine. OP, do you have a screen protector on your device?
we had an awfully thick one from att. we have since changed it to a super thin one. screen off is not a real problem on cm9, however i feel all devices should have the option to disable proximity sensor/keep lcd on during calls.
It's worth trying to use the warranty on the phone. Even though you dont have the original sales reciept, the phone has been released for less than a year, so no matter when you bought it, it is still within it's year long guaranteed warranty window.
Finished reading the thread, I suppose this post is now irrelevent
Thread Closed !!
New Google's Android 4.2.1 Features
-> Photo Sphere
-> Gesture Typing
-> Multi-User Support (Tablets Only)
-> Miracast Wireless Display Support
-> Daydream
-> Notification Power Controls
-> Google Now Improvements
For More Information on Which of the above features available in CyanogenMod, Come to My New Thread T989 Official CM10.1 4.2.1 Discussion (Coming Soon)
Enjoy !!! :good:
This is very useful! I am currently running AOKP JB and I will pay attention to this thread as it geets updated so I can see which ROM has less bugs, AOKP JB by TLS, or CM10.
theandroidrooter88 said:
This is very useful! I am currently running AOKP JB and I will pay attention to this thread as it geets updated so I can see which ROM has less bugs, AOKP JB by TLS, or CM10.
Click to expand...
Click to collapse
This is why i started this Thread, So we can discuss Bugs in the latest versions. :highfive:
I heard AOKP JB is stll having SODs and RRs. Do u find anything like these?
Why do we say there are no more SOD or RR? are we just taking guesses? Haven't seen any changes that would be anywhere near relevant for fixing those.
Sent from my SGH-T989 using Tapatalk 2
algorhythm said:
Why do we say there are no more SOD or RR? are we just taking guesses? Haven't seen any changes that would be anywhere near relevant for fixing those.
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
First we have to fix our flashing methods and recoveries used. I for one haven't experienced one single RR or SoD since I started flashing official nightlies. People are probably causing these issues themselves to begin with. Expecting a fix for an issue that has no identifiable cause.. I wonder if any other phones outside the t989 forums are experiencing RR and SoDs with Jelly Bean..
Sent from my SAMSUNG-SGH-T989 using xda premium
algorhythm said:
Why do we say there are no more SOD or RR? are we just taking guesses? Haven't seen any changes that would be anywhere near relevant for fixing those.
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
running 10-10. I experienced one soft reboot after restoring apps and then running all of them (I don't blame my phone). no sod yet. i don't know if they fixed rr or sod completely but i believe they made an impact. I think people are making assumptions since the 4.1.2 update claimed "better performance and stability fixes" and the bbq log shows a lot of framework and system updates
algorhythm said:
Why do we say there are no more SOD or RR? are we just taking guesses? Haven't seen any changes that would be anywhere near relevant for fixing those.
Sent from my SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
We are not guessing. I said there are no SODs or RRs because I installed each update and i am pushing hard my device to get a RR. Also as i observed that there are no SODs. CM10 09-Oct Nightly is more stable than previous Nightlies. I know there are still some issues like as i stated above. We can find solutions for common problems but not major problems.
garth719 said:
running 10-10. I experienced one soft reboot after restoring apps and then running all of them (I don't blame my phone). no sod yet. i don't know if they fixed rr or sod completely but i believe they made an impact. I think people are making assumptions since the 4.1.2 update claimed "better performance and stability fixes" and the bbq log shows a lot of framework and system updates
Click to expand...
Click to collapse
Great to hear that your running latest 10-Oct Nightly. A Simple advice to you & all other users, is to restore app without data if your are using any backup tools such as TitaniumBackup etc., Restore Apps with data cause Problems.
srikanth.t989 said:
We are not guessing. I said there are no SODs or RRs because I installed each update and i am pushing hard my device to get a RR. Also as i observed that there are no SODs. CM10 09-Oct Nightly is more stable than previous Nightlies. I know there are still some issues like as i stated above. We can find solutions for common problems but not major problems.
Click to expand...
Click to collapse
Sorry, I don't mean to crap on the thread but unless you can confidently say that SODs and RRs have been fixed (changelogs, yourself writing the code, etc.), going by your own experience shouldn't be the end-all-be-all to say whether something is fixed or not. Just like with call echo, some devices are worse than others.
I see that supposedly the issue with audio and docking has been addressed. However, the docking option is still grayed out for me when docked. Just looking for audio pass-through while docked...
Been running CM10 for the past few days and updating nightlies. My issues so far:
1. No sound with Alarms, just vibrating
2. I have been told by caller that I sounded weird using phone mic, but fine with headset
3. Had phone freeze once this morning on 10/9 with touch keys lit, but screen black, had to pull battery
I am now on 10/10 and plan on doing a clean install of it this afternoon, so I'm not sure how many of these issues with persist yet
SOD RR is not fixed for me, ran latest cm10 as well as aokp nightlies
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
eight_heads said:
Been running CM10 for the past few days and updating nightlies. My issues so far:
1. No sound with Alarms, just vibrating
2. I have been told by caller that I sounded weird using phone mic, but fine with headset
3. Had phone freeze once this morning on 10/9 with touch keys lit, but screen black, had to pull battery
I am now on 10/10 and plan on doing a clean install of it this afternoon, so I'm not sure how many of these issues with persist yet
Click to expand...
Click to collapse
1. There are issues with all of the volume settings. To fix your alarm volume open the clock settings, go to volumes and chnge the volume level. It should work. You can fix all volume settings with a simple toggle. 2. Make sure you have noise suppression enabled in call settings. 3. To avoid pulling the battery hold down the power for 10-15 seconds and it will reboot.
running 10-10 with TWRP and clean install (no tdj scripts). No rr/sod for 6 hrs so far. just a soft reboot after loading a ton of apps and running them all to push my phone to the max. No issues except the ones above and a tiny camera app issue thats already been reproduced (switching from camera mode--> video mode-->panorama-->camera will cause fc). I'm starting to think this is dd material. will let you know of any rr/sods.
I'm on recent CM10 Oct10 nightly and the BLN lights stay on, even with the Oct 7 nightly.
Update: fixed my own problems. This post helped: go to menu - systems - advanced settings - sensor and uncheck and check enable keys notifications and then send yourself a text or email. It actually should work out the box mine always has. Make sure you have notifications checked off in the apps like sms and gmail.
Also check display - notification light to make sure it enabled and you can add the apps you want to have the light enabled to work
Sent from my SAMSUNG-SGH-T989 using XDA Premium HD app
on CM10: 10-10. Google Now still no voice. ( prompt voice ). also, Google Now Initializing takes forever after press on mic. I am using GAPP 0726.
garth719 said:
1. There are issues with all of the volume settings. To fix your alarm volume open the clock settings, go to volumes and chnge the volume level. It should work. You can fix all volume settings with a simple toggle. 2. Make sure you have noise suppression enabled in call settings. 3. To avoid pulling the battery hold down the power for 10-15 seconds and it will reboot.
running 10-10 with TWRP and clean install (no tdj scripts). No rr/sod for 6 hrs so far. just a soft reboot after loading a ton of apps and running them all to push my phone to the max. No issues except the ones above and a tiny camera app issue thats already been reproduced (switching from camera mode--> video mode-->panorama-->camera will cause fc). I'm starting to think this is dd material. will let you know of any rr/sods.
EDIT:
Just ran the music player for 45min on a run. no skips, nothing.. ran a 90 mb mp3 file too which usually gives my ipod trouble.. good sign
Click to expand...
Click to collapse
So is that how we're saying we don't get random reboots anymore? We just call them something else??
algorhythm said:
So is that how we're saying we don't get random reboots anymore? We just call them something else??
Click to expand...
Click to collapse
well there was a difference in this reboot because my phone didnt actually fully shut off. the "cyanogenmod" boot animation came up and the phone was ready to go in about 20 seconds. there was no usual vibration indicating that the phone has shut off and no "samsung" boot image as a regular reboot would do. call it what you will
Quote:
[email protected]: on CM10: 10-10. Google Now still no voice. ( prompt voice ). also, Google Now Initializing takes forever after press on mic. I am using GAPP 0726.
Try updating it on the market
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Laazyboy said:
SOD RR is not fixed for me, ran latest cm10 as well as aokp nightlies
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Run only One ROM. Do a clean reflash. We are not experiencing any SODs or RRs. Use only one ROM because Flashing different ROMs one after the Other will Make your device weak. The data left by the AOKP causes some errors to CM10. Thats why i said that don't restore the apps with data.
So there's been a lot buzz lately about the bugs that are present in the latest build. Therefore, I'm going to maintain the thread to keep track of it all.
RULES:
-This is not a thread for feature requests. It's a thread for bugs, issues, and problems only!
-Before posting, you must swear under oath and punishable by law, that you are referring to a fresh installation and not a dirty flash (a fresh flash can alleviate a lot of the intermittent problems you may be having)
-In order to be a bug, it has to be confirmed by other users under same conditions
Please make sure to actually test bugs instead of saying yes yes yes. I will try to test each bug, but I'm relying on people's integrity as well. We don't want devs wasting time trying to fix something that isn't properly broken. So ensure that your bugs are legit and reproducible. Also, logcats where possible would be an amazing help too. I'm only adding bugs OP that are confirmed by at least a couple users. If it's not in the OP, it's not official.
Current bug list in no particular order:
Lock screen takes a while to draw
GPS works but reports 0-2 satellites only, NMEA data stream seems to be incorrect, so parsing this data may be touchy in some apps
Face unlock doesn't work
Autobrightness is choppy and slow
Pictures from camera show up in the wrong orientation from how they were taken
Bluetooth for headsets does not work, but may work connecting to GPS, etc.
Audio in skype is messed up
Gallery picture editing
Sound delay in calls
Work in progress...
FIXED (latest build)
Music skip/stutter when screen is off
Tethering is broken - M3 Build - thanks budor
No audio in video recording
Data usage/tracking does not work in the settings menu
Keyboard crashes
Current news...
Bluetooth is still broken
New build has an updated kernel with ota support
They are closing in on the audio issues
Stay tuned for a fresh build when the new monthly is released
For the record: this is on CM10.1, on the Samsung Captivate Glide, using the recent 4.2.2 update dated 2/17/2013
- Bluetooth Headset profile doent work
- Audio in video recording not working
- Photosphere unavailable
- audio stutters if screen is turned off (seems to be a CPU sleeping issue)
- Something (i am suspecting Google+, even though i am not actively using it) is filling up my SD card with gigabytes of thumbnails, which i have to delete manually
- lockscreen takes too long to appear
- from 4.2.1 to 4.2.2 the mount point of the external SD card changed again (so 'acast' cant find my downloaded podcasts). Not a bug per se, but a symlink would've been nice?
- auto-brightness is choppy and slow
- GPS usually get a lock in an okay-ish timeframe, but always reports that it's only locked to "0 / 2 satellites"
- face unlock doesnt work (hangs when opening the camera)
- orientation issues when taking photos: if i take a photo in landscape mode, it ends up in portrait mode in the gallery, and vice versa
Since i guess and hope many people will report bugs, and some of them will be not reproducable by others, we should have some mechanism to 'vote' or 'confirm' bugs, i guess?
All of the above...
Connecting to PC with USB, MTP mode does NOT work (it did work in Adam77root's last CM10.1 build ...)
Email - Any mail delivered into sub folders (Using Push MS Exchange) doesn't create a notification.... I miss a lot of email when sorting via rules on delivery. This is new in JB.
Some apps are deleted after reboot. (temporary fix is manually move to sdcard)
The phone connection will drop randomly and not come back until I reboot the phone. Note that I am using a Rogers (Canadian) model, if it has any relevance. Let me know how I can help you diagnose this bug.
mschweini said:
For the record: this is on CM10.1, on the Samsung Captivate Glide, using the recent 4.2.2 update dated 2/17/2013
- Audio in video recording not working
Click to expand...
Click to collapse
+1
- lockscreen takes too long to appear
Click to expand...
Click to collapse
+1
- from 4.2.1 to 4.2.2 the mount point of the external SD card changed again (so 'acast' cant find my downloaded podcasts). Not a bug per se, but a symlink would've been nice?
Click to expand...
Click to collapse
+1, using Directory Bind as a replacement
- auto-brightness is choppy and slow
Click to expand...
Click to collapse
+1
- GPS usually get a lock in an okay-ish timeframe, but always reports that it's only locked to "0 / 2 satellites"
Click to expand...
Click to collapse
GPS lock timeframe +1, not sure about the report
- face unlock doesnt work (hangs when opening the camera)
Click to expand...
Click to collapse
+1
- orientation issues when taking photos: if i take a photo in landscape mode, it ends up in portrait mode in the gallery, and vice versa
Click to expand...
Click to collapse
+1
yohan4ws said:
Some apps are deleted after reboot. (temporary fix is manually move to sdcard)
Click to expand...
Click to collapse
For me, some apps are weird and are missing icons: http://i.imgur.com/CNZ5Nwq.png
face unlock does not work, but it's not that important, just to mention it.
OP updated. Please make sure to actually test bugs instead of saying yes yes yes. I will try to test each bug, but I'm relying on people's integrity as well. We don't want devs wasting time trying to fix something that isn't properly broken. So ensure that your bugs are legit and reproducible. Also, logcats where possible would be an amazing help too. I'm only adding bugs OP that are confirmed by at least a couple users. If it's not in the OP, it's not official.
Sent from my SGH-I927 using Tapatalk 2
Just thought that I would mention that I've noticed that the audio stutter is even more noticeable when the phone is plugged into something using a line in instead of headphones. I'm not sure if this is a issue specific to my device, but if I use a patch cord (audio cable, but w/o the extra contact for a remote) the music sometimes stops altogether, and rarely resumes. This happens whether the screen is on or off. Bluetooth audio stream however is completely fine. No stutter even if screen is off.
Devian50 said:
Just thought that I would mention that I've noticed that the audio stutter is even more noticeable when the phone is plugged into something using a line in instead of headphones. I'm not sure if this is a issue specific to my device, but if I use a patch cord (audio cable, but w/o the extra contact for a remote) the music sometimes stops altogether, and rarely resumes. This happens whether the screen is on or off. Bluetooth audio stream however is completely fine. No stutter even if screen is off.
Click to expand...
Click to collapse
I've never had it stop on me all together.
I feel like this thread should be in the dev section, no? Flag this thread to move it if you think so
Sent from my SGH-I927 using Tapatalk 2
Please don´t throw stones, but bluetooth is or isn´t working? I´d like to try CM 10.1 but I need bluetooth working to use the phone while driving.
brunobbarcelos said:
Please don´t throw stones, but bluetooth is or isn´t working? I´d like to try CM 10.1 but I need bluetooth working to use the phone while driving.
Click to expand...
Click to collapse
2nd post ... says Bluetooth headset profile doesn't work .. this means you can stream Audio to your car's stereo, but you can NOT use your headset... I'm going to assume it's the same accross all ROMs that you can HEAR the other person talk, but the microphone via bluetooth isn't enabled.... my other assumption is that it has to do with the sound driver issues of using skype etc. where when the microphone is activated, all other sound output becomes sloooow motion. -
These are assumptions based on an under educated hypothesis .. a guess.. a shot in the dark ... based on no fact .. and hence, could be completely entirely wrong
Here's a thought, though, why don't you do a nandroid backup in CWM one evening, download the CM10.1 and install it and play with it test bluetooth and some other things, report your findings and if bluetooth deosn't work, revert back to your backup... nothing lost and everything to gain PLUS you'll be helping out the community.
gtmaster303 said:
I've never had it stop on me all together.
I feel like this thread should be in the dev section, no? Flag this thread to move it if you think so
Sent from my SGH-I927 using Tapatalk 2
Click to expand...
Click to collapse
The reason it isn't in the dev section is because it isn't actually a dev thread. The dev section is more for an actual product, whereas this is more documentation for a product, meant to answer questions people might otherwise ask in the general section.
Any of you guys use Whatsapp? It will tell you that tablets are not supported.. :/
And the main Google search app (where you can't type more than one letter from the homescreen) always closes.
Great work BTW. I just got this this afternoon. I'm loving how smooth it is
Sent from my SGH-I927 using xda app-developers app
chrisyjwai said:
Any of you guys use Whatsapp? It will tell you that tablets are not supported.. :/
And the main Google search app (where you can't type more than one letter from the homescreen) always closes.
Great work BTW. I just got this this afternoon. I'm loving how smooth it is
Sent from my SGH-I927 using xda app-developers app
Click to expand...
Click to collapse
Whatsapp works for me.
You can fix the google search app by disabling the hotword feature.
Snuuuuupy said:
Whatsapp works for me.
You can fix the google search app by disabling the hotword feature.
Click to expand...
Click to collapse
Yea. Sorry my bad. I had no service at that point. The app could not verify a network and assumed it was a tablet.
Thanks.
Okay. So basically I flash this firmware and before I proceed to use any of the apps I decide to update them. So while the outdated search app still had the hotwords feature on, I updated it. Thereafter, the app will close even before I could get to the setting menu. So the only way is to either use the older version or use the older version to turn off the hotwords feature and update. I know this is minor. Just thought I'd add this to a bugs thread.
And there are some speaker/microphone issues with google hangouts.
Anyone second this?
Sent from my SGH-I927 using xda app-developers app
chrisyjwai said:
Okay. So basically I flash this firmware and before I proceed to use any of the apps I decide to update them. So while the outdated search app still had the hotwords feature on, I updated it. Thereafter, the app will close even before I could get to the setting menu. So the only way is to either use the older version or use the older version to turn off the hotwords feature and update. I know this is minor. Just thought I'd add this to a bugs thread.
And there are some speaker/microphone issues with google hangouts.
Anyone second this?
Sent from my SGH-I927 using xda app-developers app
Click to expand...
Click to collapse
Open up the older one. Don't update, disable hotwords and that new google feature (cards?). Update, should work fine.
Tethering
Tethering is broken, I didn't see it in the list. Even FoxFi doesn't work.
I'm looking for Android 4.2.2. I use group MMS a lot at work and hate GoSMSPro. I am not the most advanced user, I have flashed ROMs before. Any recommendations? I would prefer something functional vs. something with more bells and whistles.
Android 4.2.2 AOSP roms have group message/MMS which works great. Unfortunately, there are few issues with AOSP roms, such as camera focus (there is a script by Sputnikk23 to get focus to work every time) and call log (only when dialing out, it looks as if call ends and then dials the number). These are being worked on.
If you do decide to flash one of these AOSP roms, I would recommend you turn GPS on and get a lock on whatever stock rom you are on and then going into recovery to flash the AOSP rom and GAPPS. Otherwise, GPS may not lock. Make sure to make a nandroid of whatever rom you are on as well.
I would recommend CM10.1.
Before you flash an AOSP Rom make sure you flash the teenybin through lgnpst first, it's located in the dev section. I'm running aokp and it's running flawlessly
Sent from my Optimus G using xda app-developers app
Am I reading it right that CM10.1 is basically issue free?
morganstein said:
Am I reading it right that CM10.1 is basically issue free?
Click to expand...
Click to collapse
That depends on your definition of "basically."
Camera Focus only works on first launch. There is a script to use for launching the camera to fix this.
Camera is limited to 8MP resolution in GAPPs.
Photosphere is troublesome to get working.
Placed calls appear to end as soon as they start, but the call goes through.
Using Android Beam to transfer files via bluetooth complains that a valid SIM card is not inserted, which required me to reboot each time it was used in order to once again access network or wifi data.
Bluetooth multimedia audio is lower latency than stock, but impacts wifi bandwidth.
CPU Frequency appears to stick at 1GHz unless a third party tool is used.
Some complain that the colors in the screen appear washed out or dim.
No built-in method for configuring the behavior of the capacitive key backlight.
All this being said, the experience of using the phone with CM10.1 is superior to stock. It's just that everything that makes this phone different from the Nexus 4 doesn't work properly.
About CyanogenMod
CyanogenMod is a free, community built, aftermarket firmware distribution of Android which is designed to increase security, performance, reliability and customization over stock Android.
About nightly builds
Nightly builds are automatically compiled builds of the latest CyanogenMod source from github. These builds are not officially supported. If you find bugs or issues please discuss here. Do not submit bug reports for nightly builds on the CyanogenMod issue tracker.
How to install
Preparation
Ensure you have a working copy of ADB for your PC. A simple search should find versions for all major operating systems.
If you are running "stock" (ColorOS), the first thing you will need is a recovery. There are many recoveries available. The most popular ones are CWM and TWRP. Please consult other threads to find and install a suitable recovery.
Once you have a suitable recovery, download from download.cyanogenmod.org to your PC.
If you wish to have Google applications available such as the Play Store, download a current copy of gapps. CM recommended gapps are shown at wiki.cyanogenmod.org.
Reboot your phone into recovery.
Installation
If you wish to save any of your current data, back it up. Details vary by recovery. The app "Titanium Backup" is also popular to backup and restore your installed apps.
Wipe your internal data. Again, details vary by recovery. The option is usually called "wipe data / factory reset" or something similar. This is absolutely critical and required if you are coming from a stock ROM or a different third party ROM. Note! If you are coming from a previous nightly build of CM11, you can often get away with keeping your data. But if you encounter any issues, please wipe data and retry.
Find an option in your recovery that looks like "Install from sideload" or Install from ADB" and select it. On your PC, run "adb sideload cm-11-yyyymmdd-NIGHTLY-find7.zip". ADB should show a progress indicator. When the file has completed uploading, it should install. Repeat with your gapps package if desired.
Reboot your phone. The first boot after install can take a few minutes (usually no more than 5 minutes) so be patient.
Enjoy!
tdm
Systems Engineer
Cyanogen, Inc.
Known Issues
* Find7s: Screen may not wake when phone is hot.
This is apparently an interaction between the thermal throttling code and the video/gpu driver. It has been reproduced and we are working on a fix.
* Find7s: Notification light sometimes misbehaves.
We are working on a fix.
* Find7a: Battery sometimes drains too quickly.
This issue is under investigation. We do not have a repro or a fix at this point.
* Find7a: Mic doesn't work while on speakerphone.
This issue is under investigation. We do not have a repro or a fix at this point.
@tdm,
thanks for this, could you please let me know what the bugs for this are?
About time we hade a thread for CM in here!
Thanx and good work @tdm.
Would like to know what Recovery we must use. CWM or can we also use TWRP? What GAPPS - BANKS or PA GAPPS. Also when u use the package with google camera it breaks the camera functionality!
Answered my own question:
TWRP and CWM both work good.
Use PA GAPPS with NO! Google Camera
Cm works pretty well for me. When the Android OS is not draining my battery I can easily hold it out for over 24h, hope it gets fixed soon.
Is there something I can do to help in helping fixing this problem?
Besides I've had it a few times now that when I unlock my screen that my flashlight turns on, very weird, but only had it since today/latest nightly.
Willthor said:
I've had it a few times now that when I unlock my screen that my flashlight turns on, very weird, but only had it since today/latest nightly.
Click to expand...
Click to collapse
That has happened to me many times. The screen gestures are very sensitive. This is a firmware/hardware issue. I believe we plan to use the proximity sensor to mitigate the issue, not sure if that has been committed already or not.
Will CM include this following?
*50 MP Camera Snapper like on ColorOS
*Breathing Notifications (not Blinking Notifications like implemented now on CM).
Also there is a problem when you charge via VOOC Rapid Charger when the device is turned off, the output process on the screen will be an endless loop of Oppo logo->then Charging Indicator->Oppo Logo-> Charging Indicator again and just repeatedly same process.
hulicow said:
Will CM include this following?
*50 MP Camera Snapper like on ColorOS
*Breathing Notifications (not Blinking Notifications like implemented now on CM).
Also there is a problem when you charge via VOOC Rapid Charger when the device is turned off, the output process on the screen will be an endless loop of Oppo logo->then Charging Indicator->Oppo Logo-> Charging Indicator again and just repeatedly same process.
Click to expand...
Click to collapse
I believe Oppo is reserving 50mp for their own ROM.
Don't know about breathing notifications.
I'll try to look into off mode charging.
I'm on 07/15 nightly and the only bug I have is mic on speaker calls.
This is my daily driver now.
Anyone knows of a camera app that can take slow shutter photos like on colorOS camera?(about the only feature I miss from colorOS)
I don't need the 50mp camera thing. But proper hdr and more reliable auto focus would be nice. Up get a lot of out of focus pics on CM compared to ColorOS.
And a fix for the busted HLS streaming in kitKat would be sweet.
One more thing...a solid newb proof fix for the stupid partition layout would be awesome.
Finally...Auto brightness is borked. It's an issue on every ROM I've tried. Really frustrating.
Sent from my X9006 using XDA Premium 4 mobile app
tdm said:
Known Issues
* Find7s: Screen may not wake when phone is hot.
This is apparently an interaction between the thermal throttling code and the video/gpu driver. It has been reproduced and we are working on a fix.
* Find7s: Notification light sometimes misbehaves.
We are working on a fix.
* Find7a: Battery sometimes drains too quickly.
This issue is under investigation. We do not have a repro or a fix at this point.
* Find7a: Mic doesn't work while on speakerphone.
This issue is under investigation. We do not have a repro or a fix at this point.
Click to expand...
Click to collapse
Is the battery draining issue still there?
Juiceboy125 said:
Is the battery draining issue still there?
Click to expand...
Click to collapse
No battery drain for me at least.
But I can't seem to take a proper panorama photo, not even with OnePlus camera.
Other than those few annoying bugs it's the smoothest experience I 've ever had.
gamotom said:
No battery drain for me at least.
But I can't seem to take a proper panorama photo, not even with OnePlus camera.
Other than those few annoying bugs it's the smoothest experience I 've ever had.
Click to expand...
Click to collapse
Well, that's good to hear. I've had this rom for awhile and I just wanted to make sure. But, if you mind me asking, how much screen time do you usually get? I get about 5 and a half average.
Juiceboy125 said:
Well, that's good to hear. I've had this rom for awhile and I just wanted to make sure. But, if you mind me asking, how much screen time do you usually get? I get about 5 and a half average.
Click to expand...
Click to collapse
I get about 1,5 days of use with 4 and a half SOT. But keep in mind that I like my display bright so I've tweaked up autobrightness values.
Has anyone here experienced screen going unresponsive after a bit of browsing on chrome. No issues using Mozilla Firefox though!
Re battery drain: the battery drain happens in standby. Then the battery looses ~1.5-2% per hour, meaning almost 15-20% overnight. It should be only a few instead.
To investigate this, can you guys with no battery drain let us know which modem/firmware you guys are using?
Thanks!
Using the last few nightlies, I've noticed that the gestures no longer work with the screen off. Specifically, double tap to wake and drawing a circle to start the camera.
Not sure if it's something I did on my end or a more common issue
nihir said:
Using the last few nightlies, I've noticed that the gestures no longer work with the screen off. Specifically, double tap to wake and drawing a circle to start the camera.
Not sure if it's something I did on my end or a more common issue
Click to expand...
Click to collapse
double tap 2 wake works with flashing last 3 nightlys!
silasje1 said:
double tap 2 wake works with flashing last 3 nightlys!
Click to expand...
Click to collapse
Hmm. Must be something I've done. Thanks!