GPS works poorly in non-official roms? - P3600 ROM Development

Hi,
It seems to me that GPS takes a long time to fix for non-official roms, as compared to using official roms? It is just a coincidence?

willowxda said:
Hi,
It seems to me that GPS takes a long time to fix for non-official roms, as compared to using official roms? It is just a coincidence?
Click to expand...
Click to collapse
Yes.
I have very good cold and hot TTFs.
It might depend on location, software, device movement.

don't quite think so. At least I don't think the GPS chips are smart enough to distinguish if your flash is official or not.
gps are driven by drivers - unless a rom chef knows how to write one, any unofficially cooked rom contains official drivers.
one thing though is the radio rom that might have been included in some unofficial flash packages. that's the hardware firmware that actually has impact on the TTFF.

willowxda said:
Hi,
It seems to me that GPS takes a long time to fix for non-official roms, as compared to using official roms? It is just a coincidence?
Click to expand...
Click to collapse
Did you consider that the first fix after any flash will take a very long time?
After that, things improve dramatically. It's always best to reopen the GPS application where you closed it, so the GPS-receiver will not waste any time with the determination of time and ephemerides, and to remain immobile until the fix has been achieved. This way I get fixes below 30s, while a fix in the driving car might take 2-3 minutes.
Since the position and number of visible stars changes, GPS conditions vary over the day, even if you remain at the same position. This causes time differences for the fix as well.
TG.

Related

AOKP issues

First of all, I want to say that I absofreakinglutely love this ROM. I have FINALLY convinced my friends with Evos to root and give this thing a shot because of what this ROM is capable of.
I have two issues that maybe I can get some assistance with. I am running Milestone 4.
First, the GPS just doesn't work. I lose GPS signal instantly and it does not guide me. I have flashed GAPPS, this did not actually put Maps on my phone so I installed it from the market. Any assistance with this would make me pretty much shutup.
Second, there is a lag when I turn on the screen to when the screen actually turns on. I haven't officially timed it, but I would say it is a second, maybe slightly longer. I have turned off all animation. This problem isn't going on 100% of the time, but at least 50%.
Thank you for reading!
Welcome to the world of running Alpha ROMs.
So there isn't anything we can do about these things?
lehalter said:
So there isn't anything we can do about these things?
Click to expand...
Click to collapse
Look into an updated GPS radio. AOKP Build28 ran GPS fine on my handset, apart from GoogleMaps liking to drain battery in the background....I had flashed an updated GPS radio when on CM7.1 last year

Why is GPS better on GB?

...than it is on ICS. Just wondering if anyone can enlighten me on this issue. Also, is it possible GPS performance on ICS will be similar to that of GB in the future? I'm not a dev, so I don't know nearly as much about this stuff as I'd like to.
I'm on Darkside v7 rom with UVLE1 radio.
My GPS always locks within 5-10 seconds. Pretty much the same with when I was still on GB. I tried the UVLC8 radio also, and it had similar performance.
What kind of GPS issue do you have? Is it not locking?
belly1026 said:
I'm on Darkside v7 rom with UVLE1 radio.
My GPS always locks within 5-10 seconds. Pretty much the same with when I was still on GB. I tried the UVLC8 radio also, and it had similar performance.
What kind of GPS issue do you have? Is it not locking?
Click to expand...
Click to collapse
Takes 15-20 seconds while outside. Inside, you can pretty much forget it. And this is on every ROM I've tried. I've also tried the GPS fix in the development section. Same result.
Tried a GB ROM and it locked in 5-10 seconds while inside. Huge difference. And I've seen lots of posts with people saying it's better on GB.
Pandemic187 said:
Takes 15-20 seconds while outside. Inside, you can pretty much forget it. And this is on every ROM I've tried. I've also tried the GPS fix in the development section. Same result.
Tried a GB ROM and it locked in 5-10 seconds while inside. Huge difference. And I've seen lots of posts with people saying it's better on GB.
Click to expand...
Click to collapse
Well, I guess I just never understood why people actually need to use GPS while inside.
I only use GPS when I'm outside for Yelp, Waze, Cardio Trainer, etc and my ICS GPS works just fine.
belly1026 said:
Well, I guess I just never understood why people actually need to use GPS while inside.
I only use GPS when I'm outside for Yelp, Waze, Cardio Trainer, etc and my ICS GPS works just fine.
Click to expand...
Click to collapse
Point being, 5-10 seconds inside translates to instantaneous while outside. Not so with ICS. At least not for me.
Pandemic187 said:
Point being, 5-10 seconds inside translates to instantaneous while outside. Not so with ICS. At least not for me.
Click to expand...
Click to collapse
only thing I can recommend is for you to try flashing a different radio.
I tried turning on my GPS inside (with Maps app) just now and I got a lock within 7 seconds (yes, I timed it).
belly1026 said:
only thing I can recommend is for you to try flashing a different radio.
I tried turning on my GPS inside (with Maps app) just now and I got a lock within 7 seconds (yes, I timed it).
Click to expand...
Click to collapse
Believe me...I've tried just about every combination under the sun with the same result. Like I said, I'm not the only one who has said it's better on GB.

Battery and stability issues with new ICS

I've updated from a rooted stock GB ROM to the ICS update. I'm surprised this is the update Sprint/Samsung released for the phone. The GB ROM was stable and clean, this one seems to have some issues... primarily:
1) Battery life is 6-7 hours LESS - at least.
One thing I've noticed here is that "Android OS" is using about half of the battery. Previously (and confirmed with my buddy with his GSIII), this only used about 4% or 5% . I suspect this is a culprit.
I've attached some screenshots showing this.
Almost no use of the phone all day, I was at work - some light texting later in the day. So little that SMS or GoSMS don't even appear on the chart.
2) Swype keyboard issues.
Yes, you can clear your app cache for swype and get it to work. However, you apparently can't get copy/paste/select word/select all to work.
When you click on text and click the little handle that appears, only a small box appears above, which is where the menu should be for copy/paste/select word/select all should be. At least I think that's the options - from memory, since I don't have them any more. :crying:
I've attached a screenshot showing this.
[EDIT: This is a usage issue - I consider this more difficult than before, and quirky in that it doesn't always work, but generally if you press and hold text, it'll open an edit panel where the notification bar is. Sometimes double-clicking works.]
3) Signal issues.
Again using the Battery screen - I'm seeing some very odd patterns both with carrier data signal and wifi. Previously, carrier signal was an uninterrupted line, of varying shades of green that corresopnded to signal strength. Now, when I look at this line, there's some very good sized breaks in it. That's a sharp contrast to how it used to be.
I know that searching for signal can use battery - maybe an issue with the radio? modem?
Same for wifi - I used to have a setting for "wifi off when screen off". Now it's gone, or changed - I see a "wifi on while sleep" that is checked. Despite this setting remaining constant, I see periods where that seems to be happening (later), but also a long period where wifi is active despite the screen off.
I've attached a screenshot showing this. See the "mobile network signal" line in the plot.
4) General, observed quirkiness.
Screen not being as responsive. When I press the power button on my phone now, it takes 2 or 4 seconds for the screen to activate. Touching the screen sometimes results in a very laggy response... enough time to poke the screen a second time. Skippy/unsmooth screen transitions in some cases. I've had GoSMS vanish on me a couple times and I had to relaunch it. Other apps become unresponsive and I've had to hit the home button repeatedly - sometimes 10-15 seconds before the phone comes back to the home screen and out of that app.
The screen captures were taken throughout the day - the times appear on them.
I've also attached two BetterBatteryStats dump files - one of them I had all options checked, the other just the defaults. They were taken about the same time, and about the same time I took the 8 hour screen cap.
If it matters, I'm using Go Launcher EX, it's still my stock launcher. I'm noticing not many people on ICS using it - are there known problems?
This is frustrating to me - I use this phone for work, I came off an AOKP ROM to get back on a stock ROM, for two things:
1) stock stability and battery life.
2) the Exchange account options for sync scheduling (on peak/off peak schedules for sync) that only seem to be in the stock ROM.
[EDIT: I performed a full factory wipe several days ago, and reinstalled all apps via market, and still are experiencing these exact symptoms. No improvement. May restore my nandroid from before the wipe just to gain back a few things I inadvertently lost as this didn't resolve anything.]
Accordingly, I'd like to see this ROM working. Any thoughts on these?
Anyone else observing these symptoms, relative to the stock GB rom?
5) GPS changes/bugs
I've also noticed some GPS changes / bugs that I'm not liking.
The GB GPS sucked, now this one seems worse:
Driving tonight, I had to reboot my phone to stop my eternal wait for "searching for GPS" in the car. No different than I've occasionally had to do with the GB rom.
However, then when I made a couple wrong turns or deviations from the route, it got stuck on "recalculating". Eternally.
I know I was in an area with good data, because I exited the Navigation app, relaunched it and picked the last destination and it calculated the new route instantly. It didn't successfully recalculate once... three times I had to restart the navigation app.
Also - the old navigation app used to tell you "...in a quarter mile, exit on..." and "...in 100 feet, turn onto..."
This new navigation app does no such thing. It just says "turn right on _____ street". Which is useless if there's no street sign (hence several of my "recalculating" incidents).
Bump - anyone experiencing these bugs? I haven't seen them reported - any of them.
Looking for something to try to resolve one, or all of them.
Any suggestions are appreciated, thanks.
geolemon said:
Bump - anyone experiencing these bugs? I haven't seen them reported - any of them.
Looking for something to try to resolve one, or all of them.
Any suggestions are appreciated, thanks.
Click to expand...
Click to collapse
I have had HORRIBLE battery life since the upgrade. It is worse than half of what I was getting prior to ICS
My GPS is working like a bauce though, finds my locations within seconds.
My boss got the upgrade last night and has Go Launcher and their suite of products on his device and he can't send texts now
I feel accomplished if I've stumped all of XDA... :silly:
I did discover a workaround for the copy/paste/select issue - long pressing in ICS opens a menu at the top of the screen for that.
However, still stumped on
1) 6-7 hour battery life reduction
3) signal issues
4) Quirkiness/freezing/sputtering responses
5) GPS issues - both signal and new app
Anyone else but me experiencing any others besides #1?
geoleomon - I would suggest grabbing XDA's version of Better Battery Stats, and monitoring your battery life that way rather then using the Android version.
But yes, I have experienced some of the battery issues, just no where near to that extent (maybe 4 -6 hours less).
GH0 said:
geoleomon - I would suggest grabbing XDA's version of Better Battery Stats, and monitoring your battery life that way rather then using the Android version.
But yes, I have experienced some of the battery issues, just no where near to that extent (maybe 4 -6 hours less).
Click to expand...
Click to collapse
Where do I get that one? (I paid for the full version of the Android market version)
What's different about it?
geolemon said:
Where do I get that one? (I paid for the full version of the Android market version)
What's different about it?
Click to expand...
Click to collapse
Nothing, except this one is free.
http://forum.xda-developers.com/showthread.php?t=1179809
Hmm.. Weird I've had the ota installed for a day now and my Android os is averaging 10-15% at the most
Sent from my SPH-D710 using Tapatalk 2
GH0 said:
Nothing, except this one is free.
http://forum.xda-developers.com/showthread.php?t=1179809
Click to expand...
Click to collapse
I've previously posted my results from the paid full version of the app... see the original post, two text files attached.
(one complete, one over-complete)
Anything out of the ordinary in there? What should I look for?
thanks-
Another piece of the puzzle:
I was using the camera, and it crashed - an error I didn't capture but something like "media server crashed - camera must restart". Happened twice before the camera actually started OK. Perhaps significantly, I had the phone docked when I fired up the camera - desk dock.
Also, noticing that listening to music in my desk dock at work, several times now the song has just stopped playing a few seconds in, and the media player closes. I restart the music player, and everything is OK. Sometimes that happens 2 or 3 times before the player works again, and then sometimes it'll happen an hour or so later even after it does start working again.
Could this be related?
try this then report back I have none of these issues you speak of but I am generally in a good signal area. Your signal looks awful, defiantly will cause battery drain.
http://forum.xda-developers.com/showthread.php?t=1721229
riggs170 said:
try this then report back I have none of these issues you speak of but I am generally in a good signal area. Your signal looks awful, defiantly will cause battery drain.
http://forum.xda-developers.com/showthread.php?t=1721229
Click to expand...
Click to collapse
I used the "nodata" version of that kernel to install CWM after rooting.
This will wipe my phone, which I'm looking to avoid doing if possible, if that's not the "nodata" version I already have.
Can you clarify on what you are advising?
Interesting though - a coworker suggested possibly if I wipe my phone it might clean things up.
I have just cleared my Dalvik cache, however I believe I did this before. I'm doing this now noting that as per my prior post, I'm seeing a few things force close, or else stop suddenly (like music player) without closing.
Also using CWM to "fix permissions" (not quite sure what this means).
We'll see what my results are after this.
I'd like to get this stock ROM working well if at all possible - if for no other reason than the Exchange peak/off peak email sync settings that don't seem to exist in other ICS ROMs.
I wish a mod would sticky a battery life complaint thread and close all others. Every other thread is an ics battery life complaint.
Sent from my SPH-D710 using Tapatalk 2
geolemon said:
I used the "nodata" version of that kernel to install CWM after rooting.
This will wipe my phone, which I'm looking to avoid doing if possible, if that's not the "nodata" version I already have.
Can you clarify on what you are advising?
Interesting though - a coworker suggested possibly if I wipe my phone it might clean things up.
I have just cleared my Dalvik cache, however I believe I did this before. I'm doing this now noting that as per my prior post, I'm seeing a few things force close, or else stop suddenly (like music player) without closing.
Also using CWM to "fix permissions" (not quite sure what this means).
We'll see what my results are after this.
I'd like to get this stock ROM working well if at all possible - if for no other reason than the Exchange peak/off peak email sync settings that don't seem to exist in other ICS ROMs.
Click to expand...
Click to collapse
using nodata is you're problem, all of the issues you've described could be caused by using nodata, this is why it is advised in almost every roms dev thread to do a full wipe, not no data... you may be able to get away with it without any serious bugs upgrading the same rom one revision but not going from gb to ics. you need to do a full wipe and fresh flash, legacy gb app framework is causing these issues, not ics
kingsway8605 said:
I wish a mod would sticky a battery life complaint thread and close all others. Every other thread is an ics battery life complaint.
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
SERIOUSLY! i dont get why people come to xda to whine about the OTA, XDA is the place you come not to run stock... And half the threads that arnt about battery life/"bugs" where the poster provides only basic anecdotal "evidence" and no technical data whatsoever on FF18 are gripes about sprint and sprint related issues... have people never heard of the sprintusers forum, THATS where those complaints belong, not here
cp320703 said:
using nodata is you're problem, all of the issues you've described could be caused by using nodata, this is why it is advised in almost every roms dev thread to do a full wipe, not no data... you may be able to get away with it without any serious bugs upgrading the same rom one revision but not going from gb to ics. you need to do a full wipe and fresh flash, legacy gb app framework is causing these issues, not ics
Click to expand...
Click to collapse
Thanks for this part - however...
The very advantage of going the OTA (or at least stock - I didn't OTA it) stock route is to not clear the phone.
Samsung/Sprint spent how many months developing this, to provide an update that's supposed to be clean for existing, non-technical, non-rooted, mom & pop users. I wanted to go this route simply as the "cleanest" option. And I've got lots set up on my phone and very little time around now - I'd prefer not to lose it if I can avoid it. As much as you try to back up, and remember, and all that, every time you wipe you forget something...
It's a little bit like being a Jeep owner, and saying "you know, everyone could get away with driving a Jeep".
Sure... they could... but they wouldn't all enjoy it, and it really wouldn't fit everyone's use case.
Usually, advise like this really just reflects a lack of vision: "I can't imagine anyone who uses their phone different than ME".
cp320703 said:
SERIOUSLY! i dont get why people come to xda to whine about the OTA, XDA is the place you come not to run stock... And half the threads that arnt about battery life/"bugs" where the poster provides only basic anecdotal "evidence" and no technical data whatsoever on FF18 are gripes about sprint and sprint related issues... have people never heard of the sprintusers forum, THATS where those complaints belong, not here
Click to expand...
Click to collapse
Does this look like whining, or seeking a solution? Hey, look - the original post!
geolemon said:
...This is frustrating to me - I use this phone for work, I came off an AOKP ROM to get back on a stock ROM, for two things:
1) stock stability and battery life.
2) the Exchange account options for sync scheduling (on peak/off peak schedules for sync) that only seem to be in the stock ROM.
Accordingly, I'd like to see this ROM working. Any thoughts on these?
Anyone else observing these symptoms, relative to the stock GB rom?
Click to expand...
Click to collapse
Again - seems more and more like you are a child, not only lacking maturity, but injecting your own prejudices rather than reading.
I'm seeking solutions.
And XDA is the place for options. Solutions are a subset of options.
Grow up.
I wasn't referencing you as whining at all, however this thread belongs in the Official OTA thread, not on its own, that's what the commenter prior to me and I were both refrencing- the constant new threads about the same 3 or 4 issues with the OTA when there is already a thread for it... that said you said you're seeking solutions, I offered you one that will work, I'm sorry that it displeases you, but doing a full wipe and a clean install will solve pretty much every issue you have, so backup your apps, and text messages if you want those as well, it takes less than 5 minutes in titanium backup and SMS backup, and do a clean flash or Odin (if flashing make sure you are on a safe kernel). That will fix your problems, its silly to keep asking for solutions when the best and most likely to be successful one has already been proffered.... or should you still for some reason not want to do this just unroot and take it to a sprint store, they'll do a factory reset, that'll fix all of the issues you're having. Save the time and effort and just do it yourself, no one is going to post any magic advice that'll make it all OK with nothing unchanged
Sent from my SPH-D710 using xda app-developers app
cp320703 said:
I wasn't referencing you as whining at all, however this thread belongs in the Official OTA thread, not on its own, that's what the commenter prior to me and I were both refrencing- the constant new threads about the same 3 or 4 issues with the OTA when there is already a thread for it... that said you said you're seeking solutions, I offered you one that will work, I'm sorry that it displeases you, but doing a full wipe and a clean install will solve pretty much every issue you have, so backup your apps, and text messages if you want those as well, it takes less than 5 minutes in titanium backup and SMS backup, and do a clean flash or Odin (if flashing make sure you are on a safe kernel). That will fix your problems, its silly to keep asking for solutions when the best and most likely to be successful one has already been proffered.... or should you still for some reason not want to do this just unroot and take it to a sprint store, they'll do a factory reset, that'll fix all of the issues you're having. Save the time and effort and just do it yourself, no one is going to post any magic advice that'll make it all OK with nothing unchanged
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
I'll try it... just want to make that the last resort.
Wouldn't you consider it to be equivalent to just wiping/factory reset via CWM?
geolemon said:
I'll try it... just want to make that the last resort.
Wouldn't you consider it to be equivalent to just wiping/factory reset via CWM?
Click to expand...
Click to collapse
yup wiping in cwm will do it, again be sure you're on a safe recovery eg. agats or chris41's... things like the force closes of music player and the malfunctioning of swipe, camera, etc, are due to coming from gb without a full wipe... i do realize its a PITA if you wanted to keep it simple, but it is what it is you know... insofar as battery I've never had a problem running ff18 based roms such as blu kuban or goodness, I've never run bone stock myself but if you continue to have issues there are tweaks, such as kobridges and phakers scrips that'll help out a lot, in addition to disabling unnecessary syncs, etc... however after giving it a few days to settle I've not had any problem getting a full day of moderate use out of ff18 based roms...
just to add a little more, fixing permissions will help a little with force closes... if you are unfamiliar with the UNIX permission system you can find some good info here ( http://www.perlfect.com/articles/chmod.shtml ), however it would still probably be best to to a wipe as it most likely won't fix all the bugaboo's you have from keeping your gb /data partition... despite what the horrid touchwiz interface would have you believe ICS is a huge step forward from GB, and that old app data can and will cause problems... lastly sorry if i came off a bit gruff, as I'm sure you've picked up I'm somewhat tired of seeing threads about the OTA, however to your credit you did post tons of concise, detailed info and were open to suggestions, I've seen similar thread where the OP just posts something akin to "ICS data sux, wtfff????" and when recognized devs tell them what they need to do they start to argue, which makes no sense to me... I was most likely taking my frustration at those threads and their apposition to the purpose of XDA out on you, for that I apologize, good luck with it and should you need further help let me know, I'd be glad to assist or at least point you in the direction of information that may help
This thread seems to have gone off the rails a bit... All the answers you seek are in development op. It requires reading though... There are roms and explanations for every problem you listed. If you say no they're not... Then you have not taken the time to read... Simple as that... I am a developer here and no one taught me anything. I READ AND LEARNED IT. i have a family and a life and the whole bag... So there are no exscuses. I challenge you to take the time to read and learn and give back. Maybe YOU can find the answera to your questions and post the answers here so you can help someone else who will post this and that doesnt work (but does, they just didnt read and learn how to fix it). Because as soon as you post it someone else will have the same complaints and questions and will be to lazy to search...

[Q] Random reboots and lock ups (memory leak?)

Hey all,
I've had this issue with everything but the stock rom. After a certain amount of time the phone either locks up to where I have to pop the battery, or will graphic glitch on the screen for a second and then auto reboot. Happens maybe 2-4 times a day depending on the day.
I've done a full wipe and full factory reset. I've been modding phones for ages and this is the first time I've encountered this issue. Everything else seems to run completely fine.
I'm running resurrection rom, but it's done this on several other roms I've tried. However all roms are AOKP/AOSP based if that's relevant.
If there is anymore information I can offer please don't hesitate to ask. I searched the forums and couldn't seem to find anyone else really talking about this. It can be a giant headache so hopefully I can get it sorted.
heartspains88 said:
Hey all,
I've had this issue with everything but the stock rom. After a certain amount of time the phone either locks up to where I have to pop the battery, or will graphic glitch on the screen for a second and then auto reboot. Happens maybe 2-4 times a day depending on the day.
I've done a full wipe and full factory reset. I've been modding phones for ages and this is the first time I've encountered this issue. Everything else seems to run completely fine.
I'm running resurrection rom, but it's done this on several other roms I've tried. However all roms are AOKP/AOSP based if that's relevant.
If there is anymore information I can offer please don't hesitate to ask. I searched the forums and couldn't seem to find anyone else really talking about this. It can be a giant headache so hopefully I can get it sorted.
Click to expand...
Click to collapse
If this has just started recently in would say it is indeed apart of the cm base, and related to kernel issue. Since the kernel devs are using cm and their kernel base most ROMs kernels have the same base, which means in a round about way they may react the same way on your device. To me, you said graphic glitch, then reboot. I would bump up your voltage little by little and see if it stops, I also would change govs in the kernel.. I'm assuming it happens on any cm kernels you've tried? Yank555 has an awesome cm kernel I would highly recommend, or even imoseyon always has a solid stable cm kernel as well.
How are you transferring the firmware? The heavy cable with the heavy plug? If so, it might have damaged your device's USB port and is causing intermittent disconnections which are corrupting the data as it is transferred. Try a lightweight cable and make sure it is firmly seated, then don't let it move during the transfer.
If this solves it then maybe look into replacement due to faulty design.
Frank
It is happening on all roms, however the only custom roms I've tried are CM based. I'll take a look at these other kernels and see if that resolves. Thanks for the help and idea's so far guys.
I've been having the same issues. Hellish reboots though. 10+ a day... Keep me posted. Thanks
Sent from my SM-N900T using XDA Premium 4 mobile app

[ROM] CM11 for Find7a: Nightly discussion

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!

Categories

Resources