Related
First off here is my info:
Phone: AT&T Samsung Galaxy Note i717
ROM: Cyanogenmod 10 quincyatt nightly build 12/23 (in attempt to remedy my problem)
Using this guide http://forum.xda-developers.com/showthread.php?t=1958944&highlight=install+cyanogenmod in installed the 11//14 stable build initially without too much trouble.
I did find right away that I was unable to locate any camera application or any way to access it other than the lockscreen shortcut.
When I attempted to use the shortcut from the lockscreen it simply does nothing. It doesn't crash my phone, but it also does not open my camera.
I also tried installing a couple of camera applications from the play store and they start up, but the camera never activates.
This problem persisted even when I upgraded to todays nightly build 12/23, also so far I have noticed no new problems with this build as opposed to the 11/14 stable build.
I have searched for a solution for this problem in the forums, and perhaps I missed something, if that is the case then please direct me to the proper thread.
I tried posting this in the development section only to find out that I am unable to (I've been using this site for a while but never needed to register to ask a question).
If anyone has had this problem and/or knows how to fix it I would greatly appreciate your input.
I apologize if I have left anything out, if I have then let me know and I will get back to you as soon as I can.
Edit: I updated to the 12/24 nightly build today and it appears to have resolved the camera issue right away. If anyone else is having this problem then I hope this helps.
ill give $5 to the person that fixes this.
tatzelworm said:
First off here is my info:
Phone: AT&T Samsung Galaxy Note i717
ROM: Cyanogenmod 10 quincyatt nightly build 12/23 (in attempt to remedy my problem)
Using this guide http://forum.xda-developers.com/showthread.php?t=1958944&highlight=install+cyanogenmod in installed the 11//14 stable build initially without too much trouble.
I did find right away that I was unable to locate any camera application or any way to access it other than the lockscreen shortcut.
When I attempted to use the shortcut from the lockscreen it simply does nothing. It doesn't crash my phone, but it also does not open my camera.
I also tried installing a couple of camera applications from the play store and they start up, but the camera never activates.
This problem persisted even when I upgraded to todays nightly build 12/23, also so far I have noticed no new problems with this build as opposed to the 11/14 stable build.
I have searched for a solution for this problem in the forums, and perhaps I missed something, if that is the case then please direct me to the proper thread.
I tried posting this in the development section only to find out that I am unable to (I've been using this site for a while but never needed to register to ask a question).
If anyone has had this problem and/or knows how to fix it I would greatly appreciate your input.
I apologize if I have left anything out, if I have then let me know and I will get back to you as soon as I can.
Edit: I updated to the 12/24 nightly build today and it appears to have resolved the camera issue right away. If anyone else is having this problem then I hope this helps.
Click to expand...
Click to collapse
I have the same problem.
Fixed?
James Musacchio said:
I have the same problem.
Click to expand...
Click to collapse
Well as I stated in my edit, the 12/24 nightly appears to have fixed this issue so far as i can tell. Also updated to the 12/25 nightly and the camera still works. One bad thing about this is that I have experienced more than a few reboots, but my phone starts up so fast afterwards that its a small price to pay for having my camera back.
As always, make a backup before you flash the newest nightly but I haven't seen too many problems other than the occasional crash of a couple apps and the unfortunate reoccurring crash of Apollo which is annoying.
Let me know if this fixes your issue, if it does then I'm glad I could help.
Tried CM10 nightly myself tonight, and was quite happy with it, until ....
Random reboots ....5 in 3 hours.
Camera is good, but the menu button was iffy ....
It's getting better, but I'm gonna stay with my backup for a bit longer I think ....g
12/25 is a bit sketchy
gregsarg said:
Tried CM10 nightly myself tonight, and was quite happy with it, until ....
Random reboots ....5 in 3 hours.
Camera is good, but the menu button was iffy ....
It's getting better, but I'm gonna stay with my backup for a bit longer I think ....g
Click to expand...
Click to collapse
Yeah I decided to try the 12/25 build and didn't notice any improvements from the 12/24. Ironically about an hour after my last post my phone then went into a reboot loop that I couldn't stop until I removed my battery. I had to boot into cwm recovery and then reflash the 12/24 build. So far this is the most stable nightly that allows for the camera to work without causing too many issues besides one incident I had the first day I flashed it.
I recommend people stay away from 12/25 as it was extremely unstable in my experience. I may try the 12/26 build simply because I can, but I'll definitely keep the 12/24 on hand if that fails as well.
Hello everyone,
I have tried looking around the XDA forums regarding my issue but my case seems a bit unique and so I haven't really seen any threads that solved my problem.
I have always stuck with AOSP and AOKP roms solely for their customisation capabilities and quick updates. Only gripe I have with these is just the poor battery life, which is why I went back to using a sammy rom.
Specifically, when I use a 4.3 stock sammy rom (i.e. I was using Indie's Omega Rom when this first happened), after I record a video in instagram and try to upload it, the app crashes. I can get to the page just before the caption page and the app crashes. This isn't just specific to the Omega Rom but all 4.3 stock roms I have tried, so I'm thinking that this isn't a rom-specific issue maybe..? But it might be something to do with the camera itself?
I have tried wiping the dalvik cache, fixing permissions, and even formatting my whole phone - both internal and external storages, so I'm not sure what might be the problem. Which is why I hope someone can help me out
I have seen some threads which have said it might be an issue with changing some camera settings but I haven't touched these so that shouldn't be an issue.
On a side note, another issue I've noticed with the 4.3 stock roms is that apps such as LMT don't work even though they are running in the background and I receive toast notifications about them having root access and all. Not sure if this is related, or something else completely.
I thank you for taking the time to read this, and really hope I can get some help regarding this isue.
Regards.
having the same issue here on s3...... on mk6 4.3 rom. has also happened to me across CM11 and cm10.2 and s4 revolution rom.
anyone know what i can try?
Sorry if this thread already exists.
You have no idea how happy I am this ROM exists!! But I cannot get SMS working. I get FC's on every SMS app I try including Hangouts. Anybody else getting this and/or have a remedy? Thanks
I was about to post the same error here, I have an Amaze with Videotron, S-Off, Super CID, HBOOT-1.93.2222 (JuopunutBear), TWRP as a recovery.
I tried everything, I tried different Gapps, I also tried without installing Gapps, I tried sms apps from the Play Store and Hangouts too. The only thing I haven't tried is formatting my internal SD card. (it was a clean install, all formatted and cache cleared). I also tried switching to ART but I had the same problems.
Everytime I try to just open the sms apps, the app crashes. I managed to see the error once and it was something about SQL but it might be a misinterpretation from my part.
Calls, 4G and WiFi were all working perfectly too.
After some research on Google, I tried installing busybox, xposed framework and uninstalling Voice+, but nothing works. The basic messaging app just closes without any kind of message and other apps show that it stopped working.
(I tried the Evervolv rom 4.4 and SMS were working on that one, maybe it's a setting with my network type as I am on Videotron in Canada and it is using AWS, maybe a setting under *#*#4636*#*# ??)
I want to contribute and sen some log of that error, how can I do that? I am familiar with roms, kernels, etc but not that much with logs... I tried many roms before and never got that specific problem...
Thanks to anyone who can help with this issue!
It's not just you SMS simply doesn't work on this rom and I was surprised to see that no one else pointed this out in the original thread. The default Messaging app closes immediately when you try and open it. Other SMS apps also crash either immediately upon opening them, or when you try to send a message (hangouts & SMS Pro for example). This is the only thing keeping me from using this amazing rom as my DD.
I have the same exact problem with SMS- will try the evervolv 4.4 though was really looking forward to CM11
Edit: also didnt have any other problems with the rom except for the black boxes and the camera
Let's hope there is a way to fix it!
I would post the question in the official thread but I do not have enough posts to do so unfortunately
Heck I couldn't even try SMS due to the black box issue, that's why I didn't mention it in the original thread.
For those with the black box issue--are you using the correct gapps?
In olden days there were some issues with some google things not working, and people uninstalling the ones that came in gapps and downloading them fresh from the play store.
Have you gone into recovery and fixed permissions?
Again, in days of yore, this might straighten some things out.
Is it possible that black-boxing has something to do with CPU frequency, and is it possible to tweak up the speed through developer options and lose the boxes?
I haven't tried this rom yet, as I'm currently sticking with the stable(r) cm10.
Good luck.
anybody get the SMS working on this ROM so far?
pbergonzi said:
For those with the black box issue--are you using the correct gapps?
In olden days there were some issues with some google things not working, and people uninstalling the ones that came in gapps and downloading them fresh from the play store.
Have you gone into recovery and fixed permissions?
Again, in days of yore, this might straighten some things out.
Is it possible that black-boxing has something to do with CPU frequency, and is it possible to tweak up the speed through developer options and lose the boxes?
I haven't tried this rom yet, as I'm currently sticking with the stable(r) cm10.
Good luck.
Click to expand...
Click to collapse
The black box issue has nothing to do with GPU or CPU speeds. There are discussions on the dev threads. The issue affects other legacy devices on various KK based source builds, not just Amaze and CM. The consensus is this seems to be related to the default browser which has changed in KK. This would also explain why it effects other gapps too.
MS92 said:
anybody get the SMS working on this ROM so far?
Click to expand...
Click to collapse
Not that I'm aware of.
Media Issues
The ROM is pretty good for the most part.
I just have this problem where Play Music gives this error, "Cannot play the music track you requested"
I clear my media storage and try to rescan my SD card but none of the apps work. They all crash.
Is there anyway to fix this?
ranwal said:
The ROM is pretty good for the most part.
I just have this problem where Play Music gives this error, "Cannot play the music track you requested"
I clear my media storage and try to rescan my SD card but none of the apps work. They all crash.
Is there anyway to fix this?
Click to expand...
Click to collapse
Maybe app settings for the app and Erase App Data?
can i get a link for the updated adreno drivers? thanks!
865DETH said:
can i get a link for the updated adreno drivers? thanks!
Click to expand...
Click to collapse
Yes you can its on last three pages of orignal thread you also have to sign up for that
Sent from my HTC_Amaze_4G using Tapatalk
as the OP says and i quote that only non working things are
1. camera exposure
2. tethering
but as the thread goes ahead we read more prolems/bugs
May i ask what is the current status for bugs/not working and other issues and what has been fixed and any other stuff we should flash over the ROM like driver, may it be upoaded to the OP for ease as its reall hard to search for those things on mobile app. thank you and good luck.
Anyone else have issue disabling their microphone while in a call? I tried with both the speaker phone and regular handset mode, the "no mic" icon enables but my caller can still hear me. The Hold button seems to work fine though.
FYI, it took a while for the battery to figure itself out. I wiped the battery stats before flashing everything and the first few days I got a lot of jumping battery levels. I let it charge all the way down as much as I could then rebooted and did a full charge and rebooted again and then full charge again. That seemed to reset the battery level to the correct state.
I also , enabled Device/GPS only for the location detection other wise the google services at 50% or more battery.
I'm running the 2014-02-16 build, with the updated video drivers.
Camera is not working
I have also installed this pacman rom 4.4.2. all is well instead of camera.
Any updates for the camera isssue??
Shahxz said:
I have also installed this pacman rom 4.4.2. all is well instead of camera.
Click to expand...
Click to collapse
Since PAC uses the CM device tree for its source any issues with CM will also be evident in PAC. Until the CM devs are able to resolve the camera exposure issue it will exist in both ROMs.
Librastar said:
Any updates for the camera isssue??
Click to expand...
Click to collapse
Think about your question for a minute. Have you seen any recent posts in the CM dev thread indicating an update which solves this issue? If you had just taken a moment to look at the dev thread instead of posting this you would have answered your own question. It's not like the CM-11 thread is incredibly long, it's only 28 pages total. This post is just laziness on your part and an unnecessary waste of bandwidth.
is there any alternate app in the market, i tried couple of apps but nothing useful
@Odysseus1962
If I were to compile AOSP, which variant would you suggest for me to build?
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Q&A for [ROM][LP][5.0.2][UNOFFICIAL]BlissPop v1.8 - Updated 01/23/2015
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][LP][5.0.2][UNOFFICIAL]BlissPop v1.8 - Updated 01/23/2015. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Torch and camera
torch don't work, camera take a shoot will crash
zeronatdo said:
torch don't work, camera take a shoot will crash
Click to expand...
Click to collapse
Torch working for me. Google camera from play store works as a replacement for the broken stock camera.
dandrumheller said:
Torch working for me. Google camera from play store works as a replacement for the broken stock camera.
Click to expand...
Click to collapse
Thanks, i will try :good:
GPS still isn't working
I dirty flashed from 1.8 to 2.0 but the gps still doesn't work.
edit: i used the gps tool box app and actually it works now, but it still takes a long time to lock onto GPS, anyway thanks for this rom!
omgitslink said:
I dirty flashed from 1.8 to 2.0 but the gps still doesn't work.
edit: i used the gps tool box app and actually it works now, but it still takes a long time to lock onto GPS, anyway thanks for this rom!
Click to expand...
Click to collapse
Agreed, GPS locks seem slow. Might be what we are stuck with given the cm12 fix.
Havent been on any other gproj ROMs to compare.
Google camera
Does all functions work in the google camera (panorama, photo sphere and lens blur)? Right now I'm using CM12 official with Solid Kernel and only regular photo and video is working.
ryupunk said:
Does all functions work in the google camera (panorama, photo sphere and lens blur)? Right now I'm using CM12 official with Solid Kernel and only regular photo and video is working.
Click to expand...
Click to collapse
Sure, go and find something not working why don't you.
I hadn't tried any of them. Sphere and pano only show black screens, apparently not working. Lens blur is functional
dandrumheller said:
Sure, go and find something not working why don't you.
I hadn't tried any of them. Sphere and pano only show black screens, apparently not working. Lens blur is functional
Click to expand...
Click to collapse
Actually, that's a problem with all the lollipop roms that I have tried for the e970 (and most of the KK, except for some the MAKO based). Seems that our camera is quite difficult to please....
BTW dandrumheller, it seems that you have tried most of the roms out there for our device, which one did you find more stable? At the time I'm using the official CM12 with Solid Kernel and in my opinion is really good (except for the camera and the bluetooth address, which aren't dealer breakers for me). Thanks.
ryupunk said:
Actually, that's a problem with all the lollipop roms that I have tried for the e970 (and most of the KK, except for some the MAKO based). Seems that our camera is quite difficult to please....
BTW dandrumheller, it seems that you have tried most of the roms out there for our device, which one did you find more stable? At the time I'm using the official CM12 with Solid Kernel and in my opinion is really good (except for the camera and the bluetooth address, which aren't dealer breakers for me). Thanks.
Click to expand...
Click to collapse
I actually haven't tried many of the Lp roms. Candy5 has been the most stable and battery efficient for me. Had some issues with bsod on beanstalk 5.0, though 4.4 versions were excellent. Blisspop has been quite stable, but uninspiring in terms of battery life. My phone hates solid kernel - tons of freeze and crash issues. In general I seem to have better luck with mako based roms. Have not tried CM12 yet.
dandrumheller said:
I actually haven't tried many of the Lp roms. Candy5 has been the most stable and battery efficient for me. Had some issues with bsod on beanstalk 5.0, though 4.4 versions were excellent. Blisspop has been quite stable, but uninspiring in terms of battery life. My phone hates solid kernel - tons of freeze and crash issues. In general I seem to have better luck with mako based roms. Have not tried CM12 yet.
Click to expand...
Click to collapse
Cool. I might try Candy5 and see how it goes. Thanks for you answers!
I'm having an issue where the contact names aren't showing up in the stock messenger, or gosms (haven't tried at other). The full number shows, but never the names. I've tried clearing caches and data on contacts and messengers. Tried resyncing the contacts from Google. I've double checked the privacy guard settings. Basically, I've searched around and tried everything I can think of, but still no luck! So I figured I'd ask the experts! Any ideas???
Ive noticed a few other minor issues. ...
I've had the problem with not being able to move the download, as someone mentioned above. Ive had to connect to PC, transfer from phones internal storage to the PC, then back to EXT SD card in the phone.
The 2/13 build does seem to be a little harder on the battery, and runs a lil warm (also mentioned above). I haven't had any crashing issues, but can feel the temp difference over the average.
Possibley related to the heat and battery issues; I noticed that there are two interfaces for the CPU/GPU clocking and scheduling, under the Performance section of System Settings. Maybe there's a conflict happening there? From memory, I don't remember the "Device Control" section being there in the previous build. It seems redundant to have both. Although Device Settings is much more robust, and I would prefer it be integrated instead of keeping the old, minimal interface. Some adjustments to Device Settings, while disabling the other minimal settings on boot, seems to have helped with heat and battery drain a little bit.
No problems with GPS, that I've noticed
Titanium Backup v6 has problem gaining root access in all cm12 ROMs I've tried. To fix, go to Titanium BU Preferences, scroll to bottom, select Troubleshoot Options (or something like that), and highlight/select the option to force the app to use the SYSTEM busybox, not the one baked into Titanium BU. Restart the app, and root works. Also worth mentioning is that you may have to enable root access under Developer Options in System Settings before any app can gain root. Otherwise, no issues with root, or Super SU.
Hi,
After using Beanstalk 4.4 for several months, finally I tried first LP based ROM BlissPop...so far it seem good, only couple of crashes in last week, few issues are present that are highlighted already (like camera panorama not working...battery life affected).
Since last couple days, the strange issue is being encountered, when i get a call, phone rings but there is no interface to receive the call, i then have to go to call screen and there it says "return to the active call" when i click, i get to the screen where i can receive the call. This started happening without any updates so not sure what caused it? I even tried latest version of ROM but same issue present.
Any ideas?
P.S: thanks to everybody who contributes to this excellent site, i have been a regular reader of the site but got to post something today for the first time.
dandrumheller said:
I actually haven't tried many of the Lp roms. Candy5 has been the most stable and battery efficient for me. Had some issues with bsod on beanstalk 5.0, though 4.4 versions were excellent. Blisspop has been quite stable, but uninspiring in terms of battery life. My phone hates solid kernel - tons of freeze and crash issues. In general I seem to have better luck with mako based roms. Have not tried CM12 yet.
Click to expand...
Click to collapse
---------- Post added at 07:35 AM ---------- Previous post was at 06:49 AM ----------
Okay, it turned out to be a feature that some one must have activated on my cell (my little kiddo likes to tinker with my cell)
In App Notification section, Dialer was blocked and that was causing it to not show up whenever i got a call.
Its working great now
idreamido said:
Hi,
After using Beanstalk 4.4 for several months, finally I tried first LP based ROM BlissPop...so far it seem good, only couple of crashes in last week, few issues are present that are highlighted already (like camera panorama not working...battery life affected).
Since last couple days, the strange issue is being encountered, when i get a call, phone rings but there is no interface to receive the call, i then have to go to call screen and there it says "return to the active call" when i click, i get to the screen where i can receive the call. This started happening without any updates so not sure what caused it? I even tried latest version of ROM but same issue present.
Any ideas?
P.S: thanks to everybody who contributes to this excellent site, i have been a regular reader of the site but got to post something today for the first time.
Click to expand...
Click to collapse
system control issue
I went through all 9 pages of the thread and didnt notice anyone else having this issue. In 2.2 under performance and then system control app when one goes to features and then vibration intensity it just force closes on me...is anyone else having this issue? Any suggestions on what I can do to fix?
So I'd like to see what was being discussed in the normal thread for this great rom but the following link isn't working and since I'm a forum baby I'm not allowed to post in the grownup thread... Can anyone help me out with this? Does anyone check this side of the thread?
http://click.xda-developers.com/api...ww.reddit.com/r/oneplus/comm...updateservice/
---------- Post added at 10:43 PM ---------- Previous post was at 10:39 PM ----------
Also, the last build(the one before latest) ... The vibration control in performance>device control was fixed and working.... In the latest build it's broken once again and force closing every time I select it. Just wanted to mention in case no one is aware of it.
So if 4.8.15 is the latest build why does the ota update app found in the app drawer ask me to update to the latest version so my configuration will be appropriate for ota updates? Is there something specific I have to do in order for that feature to work properly?
Lol is this thing on?
In the latest build, was the performance tab in settings cut out of the build?
---------- Post added at 02:40 PM ---------- Previous post was at 02:33 PM ----------
MitchRapp01 said:
In the latest build, was the performance tab in settings cut out of the build?
Click to expand...
Click to collapse
It contained the free app that allowed you to do all kinds of different things with the phone...I forget what it was called....I know part of the file name was x.nameless rom.com
You can try kenvinjoa kernel or nitro kernel
Does this build allow encryption?
I did the whole manual update to Lollipop, unfortunately, my phone keeps searching for GPS when I use apps that need it.
The problem is I like to use a boating app, and I go far enough offshore that I do not get data. Btw, I get this issue with any app that needs GPS, including Pokemon Go!
After searching online, it appears to be a bug in Lollipop itself.
Either downgrade, of go to Marshmallow if I can find a decent daily driver.
Anyone else have similar issue?
leroadrunner said:
I did the whole manual update to Lollipop, unfortunately, my phone keeps searching for GPS when I use apps that need it.
The problem is I like to use a boating app, and I go far enough offshore that I do not get data. Btw, I get this issue with any app that needs GPS, including Pokemon Go!
After searching online, it appears to be a bug in Lollipop itself.
Either downgrade, of go to Marshmallow if I can find a decent daily driver.
Anyone else have similar issue?
Click to expand...
Click to collapse
My Mate2 did the same thing...mostly after google updated a bunch of stuff. Just started doing it about a month or so ago.
Haven't touched it (all stock) in about a week. Got my new Mate8 about 4 days ago
"Searching for GPS" bug, might need to downgrade to KitKat
Try this:
http://forum.xda-developers.com/showthread.php?p=68572626
See post 35!
More details of my experience in that thread. Wife just pre-ordered an iPhone 7, probably out of pity, for me. One day I showed her my Google Maps and set it to drive home. No sound, no directions, but it quickly discerned origin and route home, when we got home it said "you have arrived," but the map, even though the pointer updated position throughout the drive, still showed the route line from the origin!
Sent from my iPad using Tapatalk
I've never had this issue on any ROM
Found a workaround
I was experiencing exactly the same issue! Not only that but it seems like this issue has popped up on reddit and latest amazon reviews too. Seems to have started occurring after July of this year for many people. I haven't determined the root cause, but it seems like it's affecting too many people to be a hardware issue. Some things I tried that DIDN'T work:
* Flashed latest Cyanogen snapshot, although I like it a lot more than stock
* Tweaked the /system/etc/gps.conf file for my region
Finally I found that my phone time significantly drifted off atomic time, noticed it could be a whole second off. After reading online about GPS technology, it seems having an accurate client atomic time should improve GPS performance. I used an app called ClockSync (with root is easier) to make sure my time was accurate and turned off syncing time with cell tower. It worked!! Using a GPS testing app (GPS Status & Toolbox) I can lock on to my position reliably in < 10 seconds. This is still running on Cyanogen.
I'm in love with this phone, so happy I don't have to buy a new one.
fenwaysnow said:
I was experiencing exactly the same issue! Not only that but it seems like this issue has popped up on reddit and latest amazon reviews too. Seems to have started occurring after July of this year for many people. I haven't determined the root cause, but it seems like it's affecting too many people to be a hardware issue. Some things I tried that DIDN'T work:
* Flashed latest Cyanogen snapshot, although I like it a lot more than stock
* Tweaked the /system/etc/gps.conf file for my region
Finally I found that my phone time significantly drifted off atomic time, noticed it could be a whole second off. After reading online about GPS technology, it seems having an accurate client atomic time should improve GPS performance. I used an app called ClockSync (with root is easier) to make sure my time was accurate and turned off syncing time with cell tower. It worked!! Using a GPS testing app (GPS Status & Toolbox) I can lock on to my position reliably in < 10 seconds. This is still running on Cyanogen.
I'm in love with this phone, so happy I don't have to buy a new one.
Click to expand...
Click to collapse
I tried to install CM13. I failed miserably. Then I started by playing the Pokémon Go game and observing the erratic character movement. Then played with the GPS settings. Turning off High Accuracy and leaving on Device Only still is working, except inside structures that block GPS signal. Tried High Accuracy while visiting San Francisco this last weekend and started having issues there, so back to Device Only for me.
Thank you for sharing what has worked for you!!!!
Sent from my MT2L03 using Tapatalk
I found the latest Cyanogen snapshot I tried (cm-13.0-20160823-SNAPSHOT-ZNH5YAO0M5-mt2) too unstable. I started to experience random reboots every day, even while using Google maps turn-by-turn navigation. Restored back to official lollipop build (MT2-L03C00B322) from my backup (that was factory restored before backing up). Now it's suddenly working without any workarounds! I have no idea why it's working now. If you are considering dumping your phone for a new one, you could try a factory reset first to make sure it's not a hardware issue. :/
---------- Post added at 05:26 AM ---------- Previous post was at 05:19 AM ----------
jzchen said:
I tried to install CM13. I failed miserably.
Click to expand...
Click to collapse
It was definitely not straightforward, I ran into several issues. First, TWRP recovery was complaining about invalid file system format so I switched to Cyanogen recovery to flash system. Second, I was getting constant Google services has crashed messages. Found out I needed to install it right after, before rebooting first. Third, I was stuck in boot-loop during Cyanogen startup. A hard reset finally fixed it.
fenwaysnow said:
I found the latest Cyanogen snapshot I tried (cm-13.0-20160823-SNAPSHOT-ZNH5YAO0M5-mt2) too unstable. I started to experience random reboots every day, even while using Google maps turn-by-turn navigation. Restored back to official lollipop build (MT2-L03C00B322) from my backup (that was factory restored before backing up). Now it's suddenly working without any workarounds! I have no idea why it's working now. If you are considering dumping your phone for a new one, you could try a factory reset first to make sure it's not a hardware issue. :/
---------- Post added at 05:26 AM ---------- Previous post was at 05:19 AM ----------
It was definitely not straightforward, I ran into several issues. First, TWRP recovery was complaining about invalid file system format so I switched to Cyanogen recovery to flash system. Second, I was getting constant Google services has crashed messages. Found out I needed to install it right after, before rebooting first. Third, I was stuck in boot-loop during Cyanogen startup. A hard reset finally fixed it.
Click to expand...
Click to collapse
That's a lot to deal with!!!
As of yesterday I am back to High Accuracy, and just as you note everything seems fine, particularly with regards to GPS.
I guess if I want to have Android 7, I'll save up for a phone that comes with it, unless I learn how to manually do it myself. (I was once a CECS major, about 16 years ago...)
Thank you again for sharing your experience! I hope we can all go back to enjoying our exceptionally large screens....
Sent from my MT2L03 using Tapatalk