[Q] Does Cyanogenmod run well on Moto G? - Moto G Q&A, Help & Troubleshooting

Hi, I need a phone that's capable of running Cyanogenmod, and I'm considering buying the Moto G because it is relatively cheap and powerful. I just need the opinion of someone who already has this phone, would you recommend the Moto G to someone who wants to run CM and why/why not?
Is the last M snapshot usable (not having any serious bugs that are dealbreakers), in other words, is this phone a viable option for someone who want a cheap phone with CM, or should I stay away from it?

DigitalBroccoli said:
Hi, I need a phone that's capable of running Cyanogenmod, and I'm considering buying the Moto G because it is relatively cheap and powerful. I just need the opinion of someone who already has this phone, would you recommend the Moto G to someone who wants to run CM and why/why not?
Is the last M snapshot usable (not having any serious bugs that are dealbreakers), in other words, is this phone a viable option for someone who want a cheap phone with CM, or should I stay away from it?
Click to expand...
Click to collapse
Well, the latest unofficial CM11 M9 on the thread in the general section works pretty amazing for me. The support is also improving. So I would go for it.
Sent from my Moto G using XDA Premium 4 mobile app

DigitalBroccoli said:
Hi, I need a phone that's capable of running Cyanogenmod, and I'm considering buying the Moto G because it is relatively cheap and powerful. I just need the opinion of someone who already has this phone, would you recommend the Moto G to someone who wants to run CM and why/why not?
Is the last M snapshot usable (not having any serious bugs that are dealbreakers), in other words, is this phone a viable option for someone who want a cheap phone with CM, or should I stay away from it?
Click to expand...
Click to collapse
What I have to talk about the "CyanogenMod 11" in "Moto G" (Dual SIM) is that it is running well. Use the "The Green Machine" kernel 1.2.5 because the latest (2.0.1) is closing the camera app.
Has some bugs .. at first were not important but are currently driving me mad ..
BUG: In WhatsApp when I get a great audio, it crashes while running the audio and closes the app.
BUG: In Multi-SIM settings, selecting data for the second chip it shows an error signature.
BUG: Audio delay in music player. It has been corrected with a fix audio.
For now these are what I found. I'm still constantly using and testing various functions and applications.
It is good for design and options it contains. However, sometimes, the little bugs make me mad.
I had no crashes system for now.
I did not test good games yet.
Sorry for the english .. Translated by GoogleTradutor.

avrtlg said:
BUG: Audio delay in music player. It has been corrected with a fix audio.
Click to expand...
Click to collapse
Can I ask what this bug was doing? I'm wondering if it's the same problem I'm having. I'd try to change the volume and the app would freeze up and eventually stop responding. Can't figure out for the life of me how to fix it.

Enabling Bass boost in DSP manager fixes it. You can also flash the old audio libs. The flashable zip is available in one of the threads.
Sent from my Moto G using XDA Premium 4 mobile app

Related

[Q] CM10 as a daily driver for S4 model

I am thinking of buying a used HTC One S in Canada for $200-$250, and I believe all Canadian models are the S4 type.
I have never used nightlies before, so I am wondering how stable the current CM10 nightlies are on this model. I do not expect nightlies to be perfect, but I use my phone very frequently so I don't want to risk dealing with oddities like lost network, broken tethering, broken camera, etc. Even worse are things like the phone shutting itself down at night and causing the alarm to not ring.
What I need to be working in order to use a ROM as a daily driver:
- The phone part, meaning calls, SMS, and data
- Alarm clock
- Camera for photos (can live without the video for the most part)
- Headphone (for music)
- Bluetooth (for hands free calling in my car)
- Tethering and portable hotspot
- Youtube playback
- GPS
Performance is not too big of a deal as long as scrolling is smooth and core apps like the browser don't chug. I don't play games on my phone so graphics lag is not important. Basically, I would like to have an experience that at least is on the level of CM7 on my Desire Z and LG O2X.
So for those who own the S4 variant of the One S, how is your overall experience with CyanogenMod 10? Is it safe to use as a daily driver? If anything is currently broken, what is it?
Look in the cm10 thread and read people's reactions...
Sent from my HTC VLE_U using xda app-developers app
Works 100% for me...I don't use tethering or car bluetooth though.
Nightlies can run fine one night and have issues the next as commits change. So, maybe not the stability you are looking for. I have had good luck with them same as el_smurfo. I have had data connection issues when screen off/wifi on with aosp. Wasn't a big deal to me, maybe will be to you. Not sure if either of them have been fully resolved yet. The next nightly will have many commits, check out the CM thread and see what folks say about it when available. But, as machoman1337 said read the OP page and last 20 pages or so of the threads. Maybe klin's aokp rom would be better to try first. Also, get familiar with how to flash on the 1s. Depending on hboot you may be fastbooting the boot.img separate from the rom. And some roms now are including the radio. TWRP seems to be the preferred recovery for most of us. Also, most of us find the flash goes better if you wipe System as part of your full wipe.
Ken

Audio playback causes device to reboot

At first I thought it was a rom issue, but it happens to be on every 4.2.2 rom I've tried. Then I thought it was a kernel issue - until I tried nitros rom which is blur based 4.1.2.
The problem? I drive a lot, the ability to use apps such as beyond pod, mlb at bat (to listen to my tigers!), tune in radio etc. Is very important to me. If I download a podcast and begin to play it, it's only a matter of time before my phone freezes up and reboots. Same for the other apps I mentioned. Usually it takes less than 5 minutes for my phone to freeze / reboot.
This has happened to me for a while now, and it does seem to get worse on certain roms / nightlies, but virtually across the board, the result is the same. I have tried carbon, liquid smooth, xenon hd, as well as nitros roms.
I am very frustrated at the moment, as I have no real options other than going back to stock, which sucks because I am in love with so many of the features available with the aforementioned custom roms. Any help or feedback would be appreciated!
Edit: meant to post this in help section, I apologize
Sent from my DROID RAZR HD using Tapatalk 2
I've got the same issue, there's some discussion about this at the end of the CM 10.1 thread in the ROMs section. I personally haven't tried the suggested fix, so YMMV.
DonKilluminati23 said:
At first I thought it was a rom issue, but it happens to be on every 4.2.2 rom I've tried. Then I thought it was a kernel issue - until I tried nitros rom which is blur based 4.1.2.
The problem? I drive a lot, the ability to use apps such as beyond pod, mlb at bat (to listen to my tigers!), tune in radio etc. Is very important to me. If I download a podcast and begin to play it, it's only a matter of time before my phone freezes up and reboots. Same for the other apps I mentioned. Usually it takes less than 5 minutes for my phone to freeze / reboot.
This has happened to me for a while now, and it does seem to get worse on certain roms / nightlies, but virtually across the board, the result is the same. I have tried carbon, liquid smooth, xenon hd, as well as nitros roms.
I am very frustrated at the moment, as I have no real options other than going back to stock, which sucks because I am in love with so many of the features available with the aforementioned custom roms. Any help or feedback would be appreciated!
Edit: meant to post this in help section, I apologize
Sent from my DROID RAZR HD using Tapatalk 2
Click to expand...
Click to collapse
Have you tried skiralaxs cm10.1 build? I'm currently on the 7/1 build with none of those problems.newest builds for all have a Bluetooth bug. Make sure you wipe everything including data.
sent from my xt926 RAZR maxx hd
I am on his newest nightly as we speak, it seems to be better, I have only had 1 occurrence of the phone locking up while listening to a podcast. Unfortunately, I don't think carbon or liquid smooth are based off that version. Thanks for the suggestion, skrilaxs version does seem better in that regard!
Sent from my XT926 using Tapatalk 2
Also, when watching videos (YouTube, hbo go) I am having similar problems on skrilax 7/12.
Sent from my XT926 using Tapatalk 2
Moto does know about this, I am having the same issue, and the latest update (the OTA leaking around here) has that listed as one of the fixes. Does not say specific scenarios, but just "reboot issues mitigated". This will be my first full day running it, and I have alot of driving to do, so i'll know in the next couple hours if Moto happened to fix it.
hollovoid said:
Moto does know about this, I am having the same issue, and the latest update (the OTA leaking around here) has that listed as one of the fixes. Does not say specific scenarios, but just "reboot issues mitigated". This will be my first full day running it, and I have alot of driving to do, so i'll know in the next couple hours if Moto happened to fix it.
Click to expand...
Click to collapse
Please let me know, I haven't run the leak yet but I'm hoping for the best
Sent from my Razr HD using Tapatalk 2
DonKilluminati23 said:
Please let me know, I haven't run the leak yet but I'm hoping for the best
Sent from my Razr HD using Tapatalk 2
Click to expand...
Click to collapse
Will do, have had reboots at least once a day since the JB upgrade, so far since yesterday none.. will update later tonight on how it went, should have at least one by then if its not fixed.
Im just hoping whatever moto did can be used to stabilize the AOSP roms too, because audio playback reboots me on those even more than stock did.
Update: I think Moto did it, I drove 70 miles with music playing the whole time and not one reboot. Very impressed, have never gone that long, cept when the phone was on ics..
hollovoid said:
Will do, have had reboots at least once a day since the JB upgrade, so far since yesterday none.. will update later tonight on how it went, should have at least one by then if its not fixed.
Im just hoping whatever moto did can be used to stabilize the AOSP roms too, because audio playback reboots me on those even more than stock did.
Update: I think Moto did it, I drove 70 miles with music playing the whole time and not one reboot. Very impressed, have never gone that long, cept when the phone was on ics..
Click to expand...
Click to collapse
Awesome! Hopefully the 4.2.2 roms will benefit soon. The two main culprits for me have been listening to to podcasts (beyondpod) and mlb at bat, but I have also noticed watching videos on YouTube can cause the reboots as well, though it takes a video of a decent length to recreate the problem.
Also, there are times I go an hour without a lockup, but once I get one, they begin to occur more frequently. Just my observations. Maybe I'll try the update, what's the easiest way to flash? I'm assuming I need stock recovery etc?
Sent from my Razr HD using Tapatalk 2
DonKilluminati23 said:
Awesome! Hopefully the 4.2.2 roms will benefit soon. The two main culprits for me have been listening to to podcasts (beyondpod) and mlb at bat, but I have also noticed watching videos on YouTube can cause the reboots as well, though it takes a video of a decent length to recreate the problem.
Also, there are times I go an hour without a lockup, but once I get one, they begin to occur more frequently. Just my observations. Maybe I'll try the update, what's the easiest way to flash? I'm assuming I need stock recovery etc?
Sent from my Razr HD using Tapatalk 2
Click to expand...
Click to collapse
Yeah need stock recovery, and need a sdcard because stock recovery wont read internal memory
After that, if you need to re install recovery and re root gotta do it with adb and fastboot, because the auto utils dont work right anymore, was going nuts thinking things got patched up until I tried it manually and it worked, lol.
The newest nightly build from Skrilax (http://skrilax.droid-developers.org...om/cm-10.1-20130714-NIGHTLY-xt926-skrilax.zip) upgrades to the .86 kernel and fixes the issue. Before this I downgraded to .84 kernel and that didn't have the bluetooth bug based on this post http://forum.xda-developers.com/showpost.php?p=43429334&postcount=1627 by steveo17.
bananapeapod said:
The newest nightly build from Skrilax (http://skrilax.droid-developers.org...om/cm-10.1-20130714-NIGHTLY-xt926-skrilax.zip) upgrades to the .86 kernel and fixes the issue. Before this I downgraded to .84 kernel and that didn't have the bluetooth bug based on this post http://forum.xda-developers.com/showpost.php?p=43429334&postcount=1627 by steveo17.
Click to expand...
Click to collapse
Downloading now, I'll try that one out when I get out of work!
Sent from my Razr HD using Tapatalk 2
bananapeapod said:
The newest nightly build from Skrilax (http://skrilax.droid-developers.org...om/cm-10.1-20130714-NIGHTLY-xt926-skrilax.zip) upgrades to the .86 kernel and fixes the issue. Before this I downgraded to .84 kernel and that didn't have the bluetooth bug based on this post http://forum.xda-developers.com/showpost.php?p=43429334&postcount=1627 by steveo17.
Click to expand...
Click to collapse
Still getting reboots on that build
Sent from my Razr HD using Tapatalk 2
DonKilluminati23 said:
Still getting reboots on that build
Sent from my Razr HD using Tapatalk 2
Click to expand...
Click to collapse
Did you try the .84 kernel?
bananapeapod said:
Did you try the .84 kernel?
Click to expand...
Click to collapse
Yes I tried with and without, still got reboots when listening to podcasts.
Sent from my Razr HD using Tapatalk 2
DonKilluminati23 said:
Yes I tried with and without, still got reboots when listening to podcasts.
Sent from my Razr HD using Tapatalk 2
Click to expand...
Click to collapse
That's too bad... not sure what's going on. I'm having a new problem where the bluetooth will automatically connect to my car hands free profile but not my logitech cigarette lighter bluetooth to aux device. If I go into bluetooth settings and tap to connect, then it works just fine.
bananapeapod said:
That's too bad... not sure what's going on. I'm having a new problem where the bluetooth will automatically connect to my car hands free profile but not my logitech cigarette lighter bluetooth to aux device. If I go into bluetooth settings and tap to connect, then it works just fine.
Click to expand...
Click to collapse
It seems to me that there are several issues right now, some may be related but I feel that once one is fixed another pops up. I guess all we can do is test and report what we find.
Sent from my Razr HD using Tapatalk 2
bananapeapod said:
The newest nightly build from Skrilax (http://skrilax.droid-developers.org...om/cm-10.1-20130714-NIGHTLY-xt926-skrilax.zip) upgrades to the .86 kernel and fixes the issue. Before this I downgraded to .84 kernel and that didn't have the bluetooth bug based on this post http://forum.xda-developers.com/showpost.php?p=43429334&postcount=1627 by steveo17.
Click to expand...
Click to collapse
Bluetooth A2DP seems to have improved with the 7/15 skrilax build (.86 kernel) but I still have cases where it reboots. Appears to be related to the phone trying to mux a second stream. For instance, streaming music to my car's headunit, then start Waze app and when it goes to announce something, phone reboots.
And for me, using N38 (.84 kernel) with the latest nightlies seemed to make the phone laggy.

Any Kit-Kat Roms coming our way?

Sounds like they did a good job with optimizing broadcast batches so as to cut down on battery life and also cut down on memory requirements for the system and phones like ours with low RAM.
It sounds like a great fit for this phone. Does anyone know if CM or other solo developers plan to bring KitKat to the MPQ?
Thanks
Yes, in due time.
Patience. Don't ask for ETA's.
Looks like Motorola has updated their software upgrade page for the Moto X to say that it is receiving Kit-Kat, but Photon Q's page has an ambiguous "Future plan coming soon". I doubt we'll get an official update, but personally I care more about the Play Services updates. Most of the Kit-Kat features (besides some IR stuff) seem like they are already in CM.
Solust said:
Looks like Motorola has updated their software upgrade page for the Moto X to say that it is receiving Kit-Kat, but Photon Q's page has an ambiguous "Future plan coming soon". I doubt we'll get an official update, but personally I care more about the Play Services updates. Most of the Kit-Kat features (besides some IR stuff) seem like they are already in CM.
Click to expand...
Click to collapse
i dont think that Motorola will make another update for our photon q and even if so, why should they update it to android 4.4 instead of 4.2 or 4.3 ?
pujdo1 said:
i dont think that Motorola will make another update for our photon q and even if so, why should they update it to android 4.4 instead of 4.2 or 4.3 ?
Click to expand...
Click to collapse
Google has been releasing updates fairly fast, so some device manufactureres deciced to skip some of them and move to the latest version available to keep up with development.
Though I am not avare of any Motorola produced device that was receveing long term updates, they abandon it soon (more-less) after release.
Even nexus devices fall under 18-month update policy: http://www.phonearena.com/news/Goog...Galaxy-Nexus-will-not-get-Android-4.4_id48950
However, there are other factors regarding samsung galaxy nexus: "While Google clearly states the 18-month rule for dropping Galaxy Nexus support, it is also likely that the company was forced to take this step because Texas Instrument, which manufactured the processor for the device, has shut down its mobile phone business."
Agreed. Better battery life and less RAM usage on 4.4 would make it a welcome improvement for the Photon Q LTE. I would also like to see Miracast (Widi) working properly. At 1.9 Ghz on the Wheatley gov with it's dual Core, thanks to Dev's like Argggh, if we had 4.4....it would be another year before I even thought about getting a new phone. May be an GS5 by that time, or the Nexus 6.
If not by moto is it possible to compile it from source? Like cm, or would it be dependent on moto proprietary 4.3 stuff?
Sent from my XT897 using XDA Premium 4 mobile app
T-Mobile Moto X has got KitKat leaked update yesterday. It's too fast and will be the first non nexus to receive KitKat.
Sent from my XT897 using XDA Premium 4 mobile app
CM-11.0 is in development, but I'd not expect that to be stably useable in a month.
It can boot and the graphics seems to be fine, but no audio, camera and wifi yet, at this moment...
kabaldan said:
It can boot and the graphics seems to be fine, but no audio, camera and wifi yet, at this moment...
Click to expand...
Click to collapse
Hah, I saw the branches... good work!
I was going to try compiling it but ran into build errors, haven't put much effort into it lately. Good to know it can be built and boots! :good:
pujdo1 said:
i dont think that Motorola will make another update for our photon q and even if so, why should they update it to android 4.4 instead of 4.2 or 4.3 ?
Click to expand...
Click to collapse
Because there is probably no upgrade path in the coming year for the Photon Q. Slates don't count. So it should get the latest and greatest until a successor is planned.
Do somebody hear something about CM11 on our phone ? recently do a terrible silence in this matter
niko99 said:
Do somebody hear something about CM11 on our phone ? recently do a terrible silence in this matter
Click to expand...
Click to collapse
...you must be patient
aosp from arrrghhh works good...but without sd card and keyboard backlight
CornholioGSM said:
...you must be patient
aosp from arrrghhh works good...but without sd card and keyboard backlight
Click to expand...
Click to collapse
The SD card is kind of a critical one... And I'm not sure what is missing :/
As for keyboard backlight, I've ported this to other ROM's like AOKP - and it is NOT going to be a straightforward task on AOSP - probably not worth the effort.
Hoping to get the SD card fixed, that is annoying!!
arrrghhh said:
The SD card is kind of a critical one... And I'm not sure what is missing :/
As for keyboard backlight, I've ported this to other ROM's like AOKP - and it is NOT going to be a straightforward task on AOSP - probably not worth the effort.
Hoping to get the SD card fixed, that is annoying!!
Click to expand...
Click to collapse
Yeah, it was fun booting your build up just to see^^
Only problem I had was finding a working GApps....could load your build fine but if i tried to load any of PA's GApps or some others(like the one you have listed in your thread) I would just get constant bootloop. Anyway, looking forward to CM 11! Thanks for the update Skrillax :good:
slimbrady said:
Yeah, it was fun booting your build up just to see^^
Only problem I had was finding a working GApps....could load your build fine but if i tried to load any of PA's GApps or some others(like the one you have listed in your thread) I would just get constant bootloop. Anyway, looking forward to CM 11! Thanks for the update Skrillax :good:
Click to expand...
Click to collapse
there is already working CM11
http://forum.xda-developers.com/showpost.php?p=47954424&postcount=348
- GSM SIGNAL / CALLS / CALL BACK working
- KEYBOARD BACK LIGHT working
- SD CARD Working
- CAMERA with recording wideo working
- GSM DATA working
- GAAPS / STORE etc working
- WIFI working
- SMS / MMS ( for GSM users look bottom)
- ROOT etc working
- HDMI out working
- MEDIA DOCK working
What dont work
- camera button (but work if you start manual camera apk )
For GSM user there is needed to change in bulid.prop like below
ro.telephony.gsm-routes-us-smsc=0
telephony.lteOnCdmaDevice=0
ro.telephony.default_network=3
telephony.rilV7NeedCDMALTEPhone=false
regards
niko99 said:
there is already working CM11
http://forum.xda-developers.com/showpost.php?p=47954424&postcount=348
- GSM SIGNAL / CALLS / CALL BACK working
- KEYBOARD BACK LIGHT working
- SD CARD Working
- CAMERA with recording wideo working
- GSM DATA working
- GAAPS / STORE etc working
- WIFI working
- SMS / MMS ( for GSM users look bottom)
- ROOT etc working
- HDMI out working
- MEDIA DOCK working
What dont work
- camera button (but work if you start manual camera apk )
For GSM user there is needed to change in bulid.prop like below
ro.telephony.gsm-routes-us-smsc=0
telephony.lteOnCdmaDevice=0
ro.telephony.default_network=3
telephony.rilV7NeedCDMALTEPhone=false
regards
Click to expand...
Click to collapse
Hrmm nice, i'll give it a whirl. This site turned me into a real rom junkie lol
Is SMS working now?
ZenInsight said:
Is SMS working now?
Click to expand...
Click to collapse
Yes, but if you are gsm user you need to edit build.prop like i wroted

CyanogenMod 11.0 for Photon Q

Download: http://download.cyanogenmod.org/?device=moto_msm8960_jbbl
After the sweet time while Photon Q (xt897) has been a happy part of the unified moto_msm8960 builds, with the KitKat update released (so far) for Verizon Droid Razr HD (xt926) and Droid Razr M (xt907) by Motorola, things have changed.
The changes made by Moto in the KK update are very deep and break a lots of things for non KitKat updated devices.
Since the 1st July 2014 nightly build (besides the M8 release, the last JB based, xt897 compatible build), only KK updated devices have been supported by new CM moto_msm8960 builds.
A KitKat update for xt897 has been confirmed to be cancelled by Motorola.
As the new 3.4 kernel turned out to be not so easy to be made flawlessly working with the JB based baseband firmware as initially expected, I've decided (with the punch and help by @stargo ) to uphold an alternative moto_msm8990_jbbl builds, so that CM could support also the moto_msm8960 devices not updated to KK firmware so far (or ever), again. The jbbl builds are still based on the old 3.0 kernel.
So, after a one month pause, xt897 is again officially supported by CM (together with xt925, xt905, xt902 and mbm886), via new moto_msm8960_jbbl builds.
moto_msm8960_jbbl device specific source repos:
https://github.com/CyanogenMod/android_device_motorola_moto_msm8960_jbbl
https://github.com/CyanogenMod/android_device_motorola_qcom-common
https://github.com/CyanogenMod/android_kernel_motorola_msm8960-common/tree/cm-11.0
finally a version without xposed/theme engine conflict.
thx a lot for that and the time you guys put into this kernel issue!
As this thread only has provided a link for the download, I have moved the thread to the general section.
Once you have provided the needed information about the ROM then I will move it back.
Please PM me when the OP if complete or with any questions.
Thanks,
Toledo_JAB
Speaker issue
I'm running 0803 and when I'm talking through a headset and unplug the headset during a call, the phone goes to speaker mode.
Haven't installed 0805 yet. Just thought I'd share...
And to be honest. I don't get called that often
someone tried bt audio?
I think it might be broken.
connecting with my logitech bt adapter it still plays music through the phone's speaker and the phone is forced to reboot.....
nightly from 08.03.
Working for me with headphones on RAZR m.
Sent from my DROID RAZR M using XDA Free mobile app
Thank you for this! I haven't tested bluetooth yet but I noticed when I call people or when people call me the screen goes black as if it's permanently asleep. I can't see the screen come back on no matter what I do until I hang up. Anyone else have this problem?
No perm sleep for me... Just NXP hal NFC issues as always, and auto brightness... Great battery life!
Sent from my DROID RAZR M using XDA Free mobile app
Network issues?
Has anyone been able to connect to LTE data yet?
I was able to "force" LTE by selecting the network type.
This causes "Service State" to read "Voice: Out of Service, data: In service" which is not that surprising as I don't think I have ever had voice over LTE on sprint yet.
The "Mobile network state" stays a "Connecting" or "Disconnected"
Also of some concern is the "Signal strength" alternates between ~-108dBm 32asu and 0dBm 99asu. I traditionally haven't had that bad of a signal where I am.
Stock rom reports consistent -80dBm and 4asu on CDMA -eHRPD:14 and -108dBm 32asu on LTE:13, so seems similar, but no fluctuations to 0dBm
3G seems to work alright, but I do experience the occasional disconnect which refuses to reconnect. I sometimes can remedy with a reboot.
Running 8/11 nightly plain with fresh data/cache partitions
Any word on the auto brightness fix?
Sent from my DROID RAZR M using XDA Free mobile app
How about HDMI and Lapdock support in current builds? I just tried to attach the Photon Q to my Atrix-Lapdock again. Touchpad and keyboard are working, but no video
jrk190 said:
Any word on the auto brightness fix?
Click to expand...
Click to collapse
After I return from vacation (in 10+ days), I'll prepare a debug build for Razr M with some additional backlight info output. The issue is Razr M specific, so I will need to see the dmesg from that debug build running on Razr M to be able to figure out what's going wrong on that particular device (the backlight paths in kernel are different between Razr M and other moto_msm8960 devices).
tobby88 said:
How about HDMI and Lapdock support in current builds? I just tried to attach the Photon Q to my Atrix-Lapdock again. Touchpad and keyboard are working, but no video
Click to expand...
Click to collapse
This should be fixed automagically with the switch to 3.4 kernel, which is unfortunatelly not ready yet for the prime time on Photon Q (still a work in progress).
Sweet, might want to post on the M thread.
Sent from my DROID RAZR M using XDA Free mobile app
Does CM11 allow the Wi-Fi calls from the stock ROM (Scratch Wireless)? Or how could I still use though?
Hdmi worked for me with a regular pc monitor, but it seems to fail with the motorola lapdock.
Unfortunately the phone became more sluggish with hdmi output enabled, playing n64 emulator was no problem though.
I went from 0819 to 0821. 0819 had some trouble waking up twice. So I decided to update. Haven't had any issues so far. At least not as a daily. But then again, I haven't used BT or Youtube. Just been gaming, browsing, email and Hangouts.
Yes...
The Changelog tells us that there's a fix for reboot when holding power button down for 7 seconds. To me, the mooooost annoying feature!
I will be downloading shortly and start testing.
Been testing for about 3 weeks. Battery life is unbelievably excellent. Stable, fast, smooth, well done. The bugs I have found are with Google Sound Search which force closes on me when I use it. Bluetooth works but when I try to pair it to my car it crashes on me.
Alphadestrious said:
Been testing for about 3 weeks. Battery life is unbelievably excellent. Stable, fast, smooth, well done. The bugs I have found are with Google Sound Search which force closes on me when I use it. Bluetooth works but when I try to pair it to my car it crashes on me.
Click to expand...
Click to collapse
Google Sound Search issue is a GApps issue, not CM11 ROM issue. The 20140606 gapps contain GoogleEars.apk but miss libvorbisencoder lib for it. Remove GoogleEars.apk from /system/app and install Sound Search directly from Play market to fix it.
For the debugging of BT crash when pairing with your car BT, logcat/bugreport is needed.

Choosing a rom - personal taste and opinions

The amount of roms has started to rise. Personally I think it's time to create a thread that can guide users that find it hard to know what would suit them the best.
I'm pretty much a Cyanogenmod/Lineage OS freak. Nothing else ever made me want to use anything else as the daily driver. Other than having 2 identical phones available nothing can probably change that ?
Please help filling this thread with your points of view of why you use a certain rom. If possible point out both reasons of why someone should use it and why not.
So here is my thoughts about using Lineage OS. (consider this to be a work in progress at the time being, and please correct me if any claims are incorrect)
1. One thing with Lineage is that it is apparently trying to avoid is compability issues. One main thing is root capabilities. It's not built-in but made as an add-on. Might sound bad but making root a choice can be a good thing. More and more things detect root and might not work if detected.
The downside of this compability would be that mod support needs to be an add-on too.
The other problem is SafetyNet. A cat and mouse race of no end it seems. Lineage will never try to fool SafetyNet checks to make it pass. If other roms comes with built-in methods to fool SafetyNet I don't know.
2. It feels pretty basic and minimal. It has a smaller amount of customization than some other custom roms but probably enough for most. Other than Privacy Guard no major functions are added.
Many roms is based on Lineage OS. So if you like Lineage but can feel like something is missing you might want some other rom.
3. Some tools used for Cyanogenmod now exists for Lineage. For example Lineage Downloader. A downloader with build changes (and upcoming build changes) easily readable in the app. It can also save you some mobile data by only downloading delta updates (no need to download full zip every update).
LineageOS Changelog is a other nice app.
As far as I know not many tools exists for other roms.
4. Lineage is mostly nightly builds. Builds considered stable might not happen anytime soon. That might scare some users from flashing it.
Some other roms that has builds named 2.5 and similar, while still based on Lineage and other roms, they normally have been tested with several daily builds up to a certain point that it would deserve a bump in the version number. Probably less issues if you only flash 2.5 and wait for 2.6 and so on.
5. Lineage currently lacks OMS/Substratum support. That might be a deal breaker for some. But for me I rather stay ugly than add possible issues and additional battery drain.
6. If you want more options and fancy stuff in the kernel, like tweaking with Kernel Adiutor, some other roms might be less restricted and allowing more stuff in original kernel.
7. JIRA - https://jira.lineageos.org - site for rapporting new bugs and regressions for Lineage. Bug rapporting is only open on weekends though. The site adds a nice level of professional feeling but a active forum is always nice too.
8. Something something... ?
Sent from my XT1650-03 using Tapatalk
swejuggalo said:
The downside of this compability would be that mod support needs to be an add-on too.
Click to expand...
Click to collapse
So, is there any mod support that can be installed on Lineage after flashing the ROM?
Shani Ace said:
So, is there any mod support that can be installed on Lineage after flashing the ROM?
Click to expand...
Click to collapse
We had one working for unofficial builds. But none for official builds yet. This is the biggest downside of Lineage at the moment. Not sure how big the problem is to create a flashable zip that solves this.
Sent from my XT1650-03 using Tapatalk
How about the sound quality?this one thing I know, Kindle Fire Hdx of Lineage is very bad.
a442509097 said:
How about the sound quality?this one thing I know, Kindle Fire Hdx of Lineage is very bad.
Click to expand...
Click to collapse
Some report some issues on low volume. Nothing I noticed. Not sure if the complaints is about phone calls or music though, or if it happens with headset... Personally I would not specify any sound coming from a phone as high quality, but I am very picky about sound, on the border to crazy picky [emoji6]
Sent from my XT1650-03 using Tapatalk
a442509097 said:
How about the sound quality?this one thing I know, Kindle Fire Hdx of Lineage is very bad.
Click to expand...
Click to collapse
Replicated the sound issue when using low volume on loudspeaker. This bug is reported at JIRA and marked as in progress. Probably exist in several custom roms.
Still haven't seen anyone complaining on sound quality in any other regards (if I don't count reviews, but that is about the speaker quality).
Sent from my XT1650-03 using Tapatalk
swejuggalo said:
Replicated the sound issue when using low volume on loudspeaker. This bug is reported at JIRA and marked as in progress. Probably exist in several custom roms.
Still haven't seen anyone complaining on sound quality in any other regards (if I don't count reviews, but that is about the speaker quality).
Sent from my XT1650-03 using Tapatalk
Click to expand...
Click to collapse
Would you mind linking me to the bug? I also have it since some time
https://jira.lineageos.org/browse/BUGBASH-676
Sent from my XT1650-03 using Tapatalk

Categories

Resources