Hi everyone-
Unfortunately I'm new to these forums so I can't post to the developer forums myself (even though I'm an android developer in my 9-5), I just wanted to let people know my experience with the lastest FXP 216 ROM.
Firstly; 4.2.2 is a lot better at 4.1.2, especially when it comes to UI interactions - Project butter really works very well in this release of android, a lot of the garbage collector/kernel have been optimised, and you do get a better battery life as a result - I'm able to get a full day out of my Xperia Z without having to turn STAMINA mode on (of course... Stamina mode doesn't exist in FXP/AOKP).
In FXP 216, almost everything works as you expect it - Wifi, camera, auto screen brightness, FM Radio, most things are just flawless. I've only found three problems - One major (depending on your use).
1) GPS just doesn't work for all apps. Google Maps works fine but Runkeeper, and GPS Test fail to get a lock. I've tried Faster Fix to no avail. Definitely seems like a problem with the type of hardware - i.e. Google Maps works because it doesn't require such a perfect lock as Runkeeper. I suspect this is a problem with GLONASS support but it would merely be speculation.
2) And this is minor one for me - Headset buttons don't work - i.e. you can't play/pause/skip music with them.
3) FXP 216 has an "interesting" issue where it won't pick up UK phone networks without having to play with some of the settings. Play with the settings a couple of times, reboot a couple of times, and all comes good. Strangely the Xperia AOKP nightly doesn't have this problem.
But the GPS is a killer problem for me as I use Runkeeper every couple of days, so back to a rooted stock for me. I'll definitely keep my eye on FXP, and I might (if I find myself suddenly un-lazy on a Sunday) file a bug with them or Cyanogen alerting them to the GPS issues.
Anyway, I just wanted to put that out there seeing as I can't reply on the ROM boards as I'm a n00b and all.
-Soen
Related
I see in the Dev forum that the first RC1 of Cyanogenmod 7 for Milestone is available, but when I go to download it here, it doesn't seem to be available. I guess it would be called update-cm-7.0.0-RC1-0.07-11.02.18-Milestone-signed.zip but that last one available was the 11.02.15 release. Does anyone know whether the RC1-7.0.0-11.02.18 has been withdrawn for some reason?
I've been testing each and every build with good success, so I'm really keen to try the new one. I would ask in the dev forum, but I'm relatively new at the XDA forum and am therefore not eligible to post in it.
SF
Well, I eventually found the correct download link at https://github.com/downloads/nadlabak/android/update-cm-7.0.0-RC1-0.07-11.02.18-Milestone-signed.zip
Thanks,
SF
How is it working out so far? I've recently just started using cm6 but I don't want to install too much / get invested in it if CM7 is solid enough to use day 2 day.
FANdroid said:
How is it working out so far? I've recently just started using cm6 but I don't want to install too much / get invested in it if CM7 is solid enough to use day 2 day.
Click to expand...
Click to collapse
I would stick with cm6 for now. CM7 could use many improvements and as of now is very memory hungry (I was on the feb.10 release). CM7, however, has many bug fixes that are not implemented in cm6, for example, the wifi fix (wasn't working with some n routers before I think [depending on the security type or something] ) and it seems as though there is also the random freeze + random reboot fix (using another, older kernel) I would not switch to CM7, until many bugs are fixed. Also some games don't work.
FANdroid said:
How is it working out so far? I've recently just started using cm6 but I don't want to install too much / get invested in it if CM7 is solid enough to use day 2 day.
Click to expand...
Click to collapse
It's great. But video playing not working for me.
So I installed CM7 to try it out, and on RC1 my videos play fine (widescreen) using the included "Video" app. Well most of them do, one of them is displayed 4:3 for some reason?
I'm finding that it works quite well. Battery life is good, but there are a few bugs that need working out. CM6 is probably better if you need your phone to be 100% reliable, but I like to push the boundaries and play around.
Bugs or missing features so far:
- Button lights and keyboard backlight not working properly for me (and at least one other user here)
- Auto backlight brightness not working for me at all
- Volume button swapping/remapping not yet implemented, so that in lanscape mode left means louder (which is the wrong way round for me)
- Memory usage is a problem, so that Launcher pro keeps having to re-initialise
- Camera is VERY unreliable
- Getting random reboots and lockups, especially in Google Maps
Still, things are getting better with every release and I can always go back to CM6 if I want, since I made a Nandroid backup in OpenRecovery before I installed the CM7 update. I've just installed the RC2 update, so lets see how that goes...
SF
Normally I don't have a problem locating this kind of info, but for TP CM9 it eludes me. I found the link with the tech speak generated list. But I need the info to be a bit more plain english. And couldn't find a known issues list. I would like to check this info to see if I would like to try it out on my TP.
Thanks much.
StoneRyno said:
Normally I don't have a problem locating this kind of info, but for TP CM9 it eludes me. I found the link with the tech speak generated list. But I need the info to be a bit more plain english. And couldn't find a known issues list. I would like to check this info to see if I would like to try it out on my TP.
Thanks much.
Click to expand...
Click to collapse
Known issues are basically the camera and mic don't work, some folks have wifi issues and some don't... and some have issues with the audio acting up when waking from sleep... I myself am happy to say I don't have wifi or audio issues... but camera and mic are driver issues that may never get to work. All in all very stable though
Sent from my cm_tenderloin using Tapatalk 2
If camera and mic are the only problems then I see no reason not to give it a shot. I don't know if I would ever use them.I was concerned that it was missing core functionality making it something one wouldn't use as a daily OS and only switch over to it for test scenarios and then switch back. I have cm9 on my Samsung epic (the one with hw kb). Would the current latest nightly be the one to go with?
Just curious, why are the camera and mic drivers so difficult? I would have thought having them running on WebOS was at least some of the work. I guess porting said work to Android is a completely different ballgame.
I wonder if the wifi/audio issues are still being worked on tho? Or are those of us with those stuck with em forever?
The big thing for me was hardware video decoding. Alpha 1 fixed that for YouTube, and alpha 2 finished the fix for Netflix and others.
If you haven't already, check out the thread at rootzwiki.
I was using webOS by choice until CM9 came out. I switched to CM9, and have been using it as my daily driver since the very first Alpha. I never video chat, but if I wanted to I know I can just boot webOS.
Don't let people here tell you CM9 (or the Kangs thereof) are unstable. Some people continue to spew that we don't have a stable version of android purely because its called an alpha. I don't think it will graduate past alpha without camera/mic support, and that may never happen. Right now, without trying, I am sitting at 587 hours of up time on my TouchPad. I can't think of a better word to use than "stable."
Sent from my Galaxy S II (i777)
Known Issues that I can think of. I know some were mentioned above, but all in one place is good.
Broken, NO FIX:
1) No Microphone
2) No Camera
Partial Workarounds:
1) Audio gets noisy with screen off. Kinda workaround: Turn volume down, only happens at higher volume levels. Or set screen timeout longer/always on while playing audio. No complete fix.
2) Wi-Fi dies or doesn't reconnect. Some people never have a problem, others do. Workarounds: First, set WiFi to always on so it doesn't turn off with the screen. Second, try changing the channel on your router, or if you have 2.4ghz/5ghz switchable, try using the other. If Wi-Fi still dies, toggle it off and back on.
3) Some people report that if the TouchPad fully discharges to 0% they have trouble getting Android to charge properly. Others report that if you reboot the device with it plugged in, sometimes it won't charge. I've experienced neither problem, but the best advice is, charge before the device shuts off fully, and unplug the charger/usb while booting.
Broken, but Completely Fixable:
1) Random crashes. Install CPU Master and raise minimum CPU speed to 384 or 416 depending on which works for you, and crashes go away. Also, don't overclock too much.
Setup Issues:
1) DPI is at 160dpi stock. This works for most things, except a few tablet apps and games will not work properly. Setting DPI to 120dpi fixes everything, but the display quality is not ideal. 132dpi is ideal, but breaks the market after a day or two. Most people use 160dpi or 120dpi.
2) The default launcher, Trebuchet, is NOT compatible with the 4:3 aspect ratio of the TouchPad's screen if you use any DPI other than 160. Why something so easily fixable has not been fixed escapes me, but you will quickly find you need a new launcher. Go Launcher HD is one of a few that are very friendly to the TouchPad.
App Issues (not really issues but you probably want to know)
1) A few apps really, really, really are picky about the screen size and just won't scale right. (see Trebuchet notes above). One example is Politico HD - it forces 16:9 aspect ratio and thus gets cut off. Some apps simply refuse to run. Contacting the developers rarely works. This is probably less than 1% of the apps on the market, however.
2) Some developers simply are too strict on app compatibility on the market, and whitelist only select devices. Getting compatibility from these guys is a longshot. Best option is to install on another device, grab the APK or use Titanium Backup to move the app to the TouchPad.
3) Some games (notably Gameloft is the worst) enforce device compatibility checks within the program itself and it will refuse to run unless you masquerade as an approved device by hacking your build.prop... which is not normally recommended.
Did I miss anything anyone?
Hi all,
I've searched on this forum and in Cyanogenmod's forum about the stable release of Cyanogenmod version 10.1.2 (latest stable I think), but couldn't find an answer about this. Are there any known issues or shortcomings of this ROM? Is everything working fine? (internal/external storage, NFC, WiFi, etc.)? I live in Chile, are there any concerns about baseband, ie. will telephony/3G work just fine?
I want to try CM asap, but I'd like to find some reassuring info that everything will work fine afterwards
Thanks in advance for any help on this,
UPDATE: I'll list here a summary of known issues I'm aware of; thanks a lot to all who have replied! Please correct me if I got anything wrong, I want to document known issues for the LATEST STABLE CM version only! Nightlies don't count!
- Issues with MHL (Not working? working poorly?)
- No screen wake with volume key (my stock v20A doesn't do that, either, for the record
- No FM Radio
- WiFi during sleep drains battery quickly
- Having NFC on drains battery quickly
- Camera app sometimes corrupts pictures on best quality settings
- Can't connect to WEP-protected WiFi networks (found this elsewhere on the forums)
Everything works perfectly fine from my experience. Apart from the MHL issue, which I recently discovered, everything is perfectly done
there is no volume wake... in stock when lock screen offs.. volume key wakes the screen. its not bug just a tip!
there is no lg hidden menu too and lg fm radio
but there is a lot of other things in cm
wifi during sleep no very good (drains battery, but stays better with iodak kernel)
some also say nfc drains battery, havent tested myself.
camera app little bug when putting pictures to excelent quality (becomes corrupt if to many details on picture)
Thanks a lot for all your replies. I've added an update to the original post with all known issues I've been able to gather, from replies to this thread and looking on the forums.
I had issues
e_jim said:
Hi all,
I've searched on this forum and in Cyanogenmod's forum about the stable release of Cyanogenmod version 10.1.2 (latest stable I think), but couldn't find an answer about this. Are there any known issues or shortcomings of this ROM? Is everything working fine? (internal/external storage, NFC, WiFi, etc.)? I live in Chile, are there any concerns about baseband, ie. will telephony/3G work just fine?
I want to try CM asap, but I'd like to find some reassuring info that everything will work fine afterwards
Thanks in advance for any help on this,
UPDATE: I'll list here a summary of known issues I'm aware of; thanks a lot to all who have replied! Please correct me if I got anything wrong, I want to document known issues for the LATEST STABLE CM version only! Nightlies don't count!
- Issues with MHL (Not working? working poorly?)
- No screen wake with volume key (my stock v20A doesn't do that, either, for the record
- No FM Radio
- WiFi during sleep drains battery quickly
- Having NFC on drains battery quickly
- Camera app sometimes corrupts pictures on best quality settings
- Can't connect to WEP-protected WiFi networks (found this elsewhere on the forums)
Click to expand...
Click to collapse
I don't know, but I had to go back to the LG ROM, after install the CM 10.1.2 on my LG 4X the battery life was the worst I've ever seen, I had to recharge it at least 3 times per day. When I let the phone completely charged at night, in 6 hours the phone drained up to 20% of the battery, I mean, the phone just standing by drained 20%!!! I think that's crazy!!... I let it with 100% and when I woke up the phone had only between 85% and 80%... when with the LG ROM it just drained at most 4% (96% for use). And when I was using the phone, the screen process used up to 50% of the battery. I had to go back to the original rom.
I have to say that the phone ran so much better in every aspect than with the LG ROM, but I prefere battery life. Has anyone had the same problem that me? I would like to go back to the CM but for me is very important the battery life.
Thank you so much!
I was about to change to it but then I wad told that there's battery problems so I thought it is not worth it.
Sent from my Lg p-880 using xda premium
In all cm based roms i had lockscreen notification bar drop issue i think it's the only annoying bug.
Not sure if it's in 10.1.2.
Dear all,
it is my first try to run cyanogenmod (10.1 Rel 7) on my SGS+. But when using it, I immediately found plenty of issues:
- Navigation is only partially working. After a while the maps starts jumping around and dark semi transparent overlay sections appear so that one cannot see the full map. In the forum I found the hint to deactivate Dithering. Done. Only little improvement.
- Alarm clock is not working when the phone is turned off.
- Screen goes off after dialing a number (workaround: lift phone to the ear and lower it back down -> screen is on again).
- No FM radio app (in comparison to the stock rom).
- Skype video is still upside down (as with stock rom).
My colleagues were very enthusiastic about cyanogen mod. In contrast, I haven't really detected the advantages. Are the developpers still working on the issues? Is there anything I can do to support you guys?
To answer your queries:
-Navigation- use the bug reporting method on the CM10.1 forums and submit it as a bug report either in the S CM10.1 thread or on JIRA. More details are given in the CM10.1 thread OP.
-This feature doesn't work even on stock. Its not a bug, and its not just CM10.1. MIUI allows this apparently however.
-This is normal, not a bug either. When you call someone the screen goes off because you're going to lift it to your ear anyway. The 'workaround' is actually the proximity sensor, and a similar thing happens on stock roms. The only solution to this is to press a button when the screen initially turns off.
-FM Radio isn't included in CM builds by default, as the API needed for it needs some intense changes made to it. There's Spirit FM if you want to run the risk. Check out the thread for more information.
-Skype on CM10.x is a known issue
Try CM10.2 and see if that helps the first issue, if not, report it using the methods in the CM threads. Otherwise everything else is as normal/known.
Sent from my GT-P7510 using Tapatalk HD
Irrespective of a few bugs there are definitely a number of advantages to using CM.
Have you noticed how smooth CM10.1 is? For me it's smoother than stock. Definitely a plus.
The pre-installed applications are more polished/work better and you actually have control over them. Don't like one? You can remove it. Unlike stock where you are stuck with a lot of junk (unless you have rooted your phone).
Bugfixes! We're no longer stuck with a 2 year old version of an OS for which we don't receive any bugfixes.
Customizability. CM gives you a lot more features to have your phone just the way you want it.
Overclocking and undervolting.
Not everyone had this problem, but my phone took > 5 minutes to get a GPS fix on stock. It takes < 10 seconds on CM.
And that's just what I came up with in a few minutes. Yes, there will be a few bugs and features which you think are weird (like the screen turning off when you make a call) but you'll find that on any piece of software. If you personally feel CM is a downgrade then it's your right to think so and go back to stock ROM. That doesn't mean the average xda-user is going to agree with you though.
(I think there are also a few ROMs based on the stock 2.3.6 versions, but since I've never used them I wouldn't know which ones are worth trying.)
Hi all,
Can anyone help with this issue. I can see no long discussion about it which seems to suggest it's either rare (not great) or something I am doing (probably).
My WiFi status appears to be fine throughout the day, when in regular use. I have no speed issues (connection speeds as expected for my home internet), no random drops or on/off switches and no seeming battery drain. I have all additional services on (Bluetooth, location and NFC as I want the phone to be fully functional at all times and not just 'look nice') and despite this I get what I would expect in battery life (c. 6 hrs screen on time). YET, amongst a few other problems (what is the slider customisation about - awful!) the one I can't fathom is this:
My WiFi switches off over night presumably when the phone goes into deep sleep. I have gone into the advanced settings and set it to 'Always on' but this doesn't seem to keep it 'always on'. I wake up in the morning and it is off. I was running some Tasker profiles (which seem to make little difference given the slider issue noted above) but actually my WiFi isn't one off the Tasks effected by a night time profile.
Any help would be appreciated.
AS a secondary question, I switched my VPN over to Canada as suggested and was provided with the Nougat update. I haven't yet tried it but was wondering if there are any bugs that I should consider before switching over given I am 4 days into owning this phone and still haven't ironed out certain things in Marshmallow.
Just as a follow up question, would the 'turn Doze off' option help with this? Surely I shouldn't have to do this though?
Am I the only one having this issue? That would suck. Even so, would anybody more adept at these things than me like to have a guess at solving the issue.
IV had agresive dose mode on and haven't had any wifi problems but I am on 4.0.1 so might want to just update it as it's really stable and I haven't had any issue except having to reconfigure the APN settings. PS if you do update reset you phone after as some people have said it helps with the new file system.
Greedyfly said:
Hi all,
Can anyone help with this issue. I can see no long discussion about it which seems to suggest it's either rare (not great) or something I am doing (probably).
My WiFi status appears to be fine throughout the day, when in regular use. I have no speed issues (connection speeds as expected for my home internet), no random drops or on/off switches and no seeming battery drain. I have all additional services on (Bluetooth, location and NFC as I want the phone to be fully functional at all times and not just 'look nice') and despite this I get what I would expect in battery life (c. 6 hrs screen on time). YET, amongst a few other problems (what is the slider customisation about - awful!) the one I can't fathom is this:
My WiFi switches off over night presumably when the phone goes into deep sleep. I have gone into the advanced settings and set it to 'Always on' but this doesn't seem to keep it 'always on'. I wake up in the morning and it is off. I was running some Tasker profiles (which seem to make little difference given the slider issue noted above) but actually my WiFi isn't one off the Tasks effected by a night time profile.
Any help would be appreciated.
AS a secondary question, I switched my VPN over to Canada as suggested and was provided with the Nougat update. I haven't yet tried it but was wondering if there are any bugs that I should consider before switching over given I am 4 days into owning this phone and still haven't ironed out certain things in Marshmallow.
Click to expand...
Click to collapse
This happens when people is crying about updates every day. Then, when the updates are available, they update it in the first minute and again, they start crying, that they encounter bugs and stuff that doesnt work as it should, even if they dont have any idea how to revert their OS to the previous working one. People should learn how to be patient and enjoy their phones without being so greedy about updates.
Just sit tight, enjoy your phone, READ forums about latest updates and the problems encountered on that specific update ( since its still a beta update, and an early one , called Beta 1 ). If they seem to be fine with those issue, ONLY then should update to the latest one.
smilirulz said:
This happens when people is crying about updates every day. Then, when the updates are available, they update it in the first minute and again, they start crying, that they encounter bugs and stuff that doesnt work as it should, even if they dont have any idea how to revert their OS to the previous working one. People should learn how to be patient and enjoy their phones without being so greedy about updates.
Just sit tight, enjoy your phone, READ forums about latest updates and the problems encountered on that specific update ( since its still a beta update, and an early one , called Beta 1 ). If they seem to be fine with those issue, ONLY then should update to the latest one.
Click to expand...
Click to collapse
I haven't 'cried' about anything, pal, so keep your unhelpful comments to yourself or help. Don't middle ground-it by offering your own personal, and incorrect, opinions.
I hadn't upgraded anything, I was running stock OS and stock marshmallow, so I had literally done nothing to my device other than switch it on and download the same apps I've been using for years.
I've also rooted several devices in the past with no issues and chime in when I can to help, but I'm not a dev and there are far more technologically gifted individuals operating in this forum which is why I sought help here... Not that I got much from you. But I'm more than capable of reading release notes and making sure I can revert backwards before installing anything.
Now to anyone still here, and with the same issue, it appears that carrying out the update to Nougat, re-adding my WiFi networks and clearing system cache solved the problem or at least for the first night. Should this change I'll update here.
ISO_Metric said:
IV had agresive dose mode on and haven't had any wifi problems but I am on 4.0.1 so might want to just update it as it's really stable and I haven't had any issue except having to reconfigure the APN settings. PS if you do update reset you phone after as some people have said it helps with the new file system.
Click to expand...
Click to collapse
Hi Iso, thank you for your response, I hadn't seen this until now.
The upgrade to 4.0.1 does appear to have done the trick somewhat as it stayed on overnight without issue. I did notice it wasn't on a little later this morning but I am giving the device the benefit of the doubt on that one as I have been messing about with certain things and it's possible I or a profile in tasker switched it off.
As an aside do you recommend any other potential fixes, just to be on the safe side.
Did you factory reset after upgrading? Other than that it's probably a app you have I hear Facebook is really bad at battery
ISO_Metric said:
Did you factory reset after upgrading? Other than that it's probably a app you have I hear Facebook is really bad at battery
Click to expand...
Click to collapse
I didn't factory reset, only Cache wipe after the upgrade, and as it seems ok so far, I am reluctant to factory reset the device as it took so long to set up in the first instance.
Should it start becoming an issue again I'll try it but for now...
Also I know there are backup options though I haven't found one that works flawlessly which gives me the confidence to explore this avenue just yet.
You might have to because in nuogat they optimized the file system and in order to get the new one you have to factory reset not 100% sure it affects battery life but it really affects performance, PS also try turning off gestures, ambient display and pocket mode
ISO_Metric said:
You might have to because in nuogat they optimized the file system and in order to get the new one you have to factory reset not 100% sure it affects battery life but it really affects performance, PS also try turning off gestures, ambient display and pocket mode
Click to expand...
Click to collapse
Are you sure ISO? The UI has been updated and the already snappy OS feels snappier. Is there a way to tell for sure if it's required?
If so, any good recommendations for backup capability. I have used Helium to mixed results and I can't use Titanium as I have no root (and don't wish to).
Maybe not but it all elts fails