Related
Hi,
I installed today a CM11 from this thread http://forum.xda-developers.com/optimus-4x-hd/general , and I have an issue concerning Wi-fi connection. Basically I can put password in, but wi-fi shows it is saved and secured with wep and there is no connection at all. It is strange for me because on Paranoid Android for P880 wifi works just fine. Anyone has any tips?
Welcome to the forum and thanks for your report.
First of all, could you please let us know if you're using the Official (maintained by Demetris) or the Unofficial(maintained by laufersteppenwolf) CM11? The link that you provide does not lead to a thread.
Also reporting such problems would be best to be posted on the specific threads of the ROM, accompanied by some kind of log.
I had a similar problem earlier this year when I was switching between a lot of ROMs.
Do you have your WiFi set up to block any device with an unregistered MAC-address?
If so, check if the MAC-address on your phone changed after flashing the new ROM.
For some reason official and unofficial sources can have different addresses.
Q&A for [Rom] [4.4.4] Cyanogenmod 11 for Moto X
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Why do not you gets the wifi error, error in the security settings, screen lock / slide
Roaming Indicator Flashing
My Moto X (XT1056) works perfectly on stock ROM but when I installed CM11 on it, its roaming indicator started flashing. I have tried changing its network modes but still it keeps on flashing. I can receive messages and calls but can't make any call or send messages. What to do?
Sorry, I 'm new to this , which version I should download for my moto x 1058, thanks
i don´t speak english correctly
In June, I made a mistake that wiped my phone all the way down to boot img. Using adb and my extremely limited knowledge of how to use it, I was able to get this puppy up and running again. Due to money issues, it's just a small entertainment center for me now, (music, movies while I ride the bus, news & books, etc,) so I depend on WiFi heavily. When I (luckily!) Reformatted the phone from scratch, (misplaced my backup, when internal memory was wiped when the oops happened,) cm11 was having problems with WiFi. I believe that, from what I'm reading in the cm11 post, that the WiFi issue is cleared up and I'd like to get up to date, setting as how I'm using an April release. I'm using a sprint moto x, (1056, I THINK!?)
Am I gonna have to find this modem people are talking about, or can I just clean flash up to the latest nightly?
Can anyone throw me a little bone here?
Thanks, all...
Any and all info is greatly appreciated!!!
Hammerdroid said:
In June, I made a mistake that wiped my phone all the way down to boot img. Using adb and my extremely limited knowledge of how to use it, I was able to get this puppy up and running again. Due to money issues, it's just a small entertainment center for me now, (music, movies while I ride the bus, news & books, etc,) so I depend on WiFi heavily. When I (luckily!) Reformatted the phone from scratch, (misplaced my backup, when internal memory was wiped when the oops happened,) cm11 was having problems with WiFi. I believe that, from what I'm reading in the cm11 post, that the WiFi issue is cleared up and I'd like to get up to date, setting as how I'm using an April release. I'm using a sprint moto x, (1056, I THINK!?)
Am I gonna have to find this modem people are talking about, or can I just clean flash up to the latest nightly?
Can anyone throw me a little bone here?
Thanks, all...
Any and all info is greatly appreciated!!!
Click to expand...
Click to collapse
Before anything, reinstall the stock ROM. After that you can use some custom rom if you want.
Don't forget to back up your data.
does anyone have a backup of a build where the WiFi works after a wipe? (WiFi is broken on the newest builds, unless you update from an older one without wiping)
>1 week builds aren't available at download.cyanogenmod.org anymore :/
tomatoketchup said:
does anyone have a backup of a build where the WiFi works after a wipe? (WiFi is broken on the newest builds, unless you update from an older one without wiping)
>1 week builds aren't available at download.cyanogenmod.org anymore :/
Click to expand...
Click to collapse
I have downloaded the 21/10 build, u want it? To uploaded to mega :9
I have downloaded the 21/10 build, u want it? To uploaded to mega :9
Click to expand...
Click to collapse
yes please!!
GPS doesn't fix CM11 GHOST
Hi. I use cm 11 during 2 weeks and i have a problem wih the gps. Indeed, on the lastest nightly, the gps can't fix. How can we make the gps fixing ? Thank you
Sorry for my bad english.
Following this thread since a couple of month I see there won't be a snapshot coming.
So: is there a nice daily you recommend for my moto x (xt1052)?
Since its a long way from stock 4.4.4 I don't intend to wipe.... more than -hopefully- once.
Achilles Etimone said:
Following this thread since a couple of month I see there won't be a snapshot coming.
So: is there a nice daily you recommend for my moto x (xt1052)?
Since its a long way from stock 4.4.4 I don't intend to wipe.... more than -hopefully- once.
Click to expand...
Click to collapse
Well today build its a snapshot the first!!
Yes!
Marco Lomas said:
Well today build its a snapshot the first!!
Click to expand...
Click to collapse
Looking FORWARD to it.
GPS on Moto X
Can't seem to reply to tekanina in the main thread here:
http://forum.xda-developers.com/showpost.php?p=56970715&postcount=673
-------
Quote:
Originally Posted by sayhellotwoheaven
hi! i have a issue with the last SNAPSHOT M12.
Mi GPS doesn't works normally. In gmaps get stuck in my location and don't move when I walk or drive. Additionally, I play a gem called INGRESS, an aumented-reallity-game that uses the GPS, and same problem, when i walk or drive, gps stuck in the position, or random jumps.
help pls ):
-------
Tekanina replied:
Flash stock ROM get GPS lock, boot into recovery flash CM. GPS should work. I have to do this every once in while when GPS starts acting up usually good until you clean flash or switch Roms.
------
I was having this problem until moments ago. GPS Status and Toolbox would never find a single satellite, though I found it worked fine in stock.
Strangely, Tekanina's advice worked for me on my Xt1053 DE. I restored a TWRP backup of stock (not for the first time), got GPS lock, then flashed the latest CM nightly, got an binary error on flashing, did a wipe, binary error went away, flash succeeded, booted up, got GPS satellites right away! Not sure if it was getting a GPS lock in stock, or the full wipe that fixed this. I though for sure GPS was borked in recent versions of CM on ghost. Seems it isn't!
---------- Post added at 04:02 PM ---------- Previous post was at 03:56 PM ----------
Tony77FR said:
Hi. I use cm 11 during 2 weeks and i have a problem wih the gps. Indeed, on the lastest nightly, the gps can't fix. How can we make the gps fixing ? Thank you
Sorry for my bad english.
Click to expand...
Click to collapse
Tony, try Tekanina's advice here in the main thread. Worked for me:
http://forum.xda-developers.com/showpost.php?p=56970715&postcount=673
Slightly simpler question here: Does CM11 for MotoX still let me use Active Notifications, the twist-to-launch-camera, and the always-listening for OK Google Now functions?
Notifications
shadowfist23 said:
Slightly simpler question here: Does CM11 for MotoX still let me use Active Notifications, the twist-to-launch-camera, and the always-listening for OK Google Now functions?
Click to expand...
Click to collapse
Unfortunately, no, it doesn't. Due to the lack of a normal notifications LED, this means you get no indication at all of notifications. There is a bright green LED in the earpiece that a couple of people have figured out how to turn control, but apparently it can't be used as a notification LED because (at least for now) it requires a USB connection to turn on:
http://forum.xda-developers.com/moto-x/themes-apps/app-moto-x-charging-led-control-tasker-t2602689
https://github.com/StephenMilone/MotoX_LED
http://forum.xda-developers.com/moto-x/general/enable-moto-x-charging-led-tasker-t2603085
http://review.cyanogenmod.org/#/c/57550/
I'm currently using cm11 M12 snapshot on Verizon moto x but if I flash any of the newer nightlys,I get an error system. Ui is not responding. This error pops up or out from nowhere . The snapshot works fine . anyone else experiencing this?
Nightlies crashing, looking for stable version
Seeing following builds crash (com.android.phone) crash constantly when enabling Wi-Fi on the below images:
cm-11-20141224-NIGHTLY-ghost.zip
cm-11-20141219-NIGHTLY-ghost.zip
Anyone know of a recent, stable version that I can fall back to?
Thanks!
I have bootloader unlock from motorola official website, with twrp installed & rooted. also my cell is SIM UNLOCKED.
Everything was perfectly working on stock.
But After flashing latest Build today on my XT 1056 sprint, Signal bar showing 'R' with no signal. But I can make call & msg.
How can I resolve the said problem?
BTW, I am using my cell in Pakistan, not on sprint network.
Sent From My Moto X
Hi all,
anyone have a valid link for cm-11-20150105-NIGHTLY-ghost.zip
Thanks in advance
Zanglus
please help! iam facing problem in many root apps after flashing android m stock rom. zanti shows no network even when i am connected to super fast wifi. droidsheep not showing anything, wifianalyzer also having problem.and one more question, do we have any xposed for android 6 yet?
any one has answer?
Hello,
Like many others, my phone was solid on 6.0.1. My phone was on shamu-mmb31c image that comes with radio radio-shamu-d4.01-9625-05.32+fsg-9625-02.109.
After upgrading to 7.1.1, I started to have wifi/connectivity issues. No workaround was helping.
I started flashing older radios in hope that it will fix the issue. Even radio of 6.0.1 (above) did not resolve the issue. To just prove to myself that issue is not hardware related I flashed back factory image of 6.0.1 shamu-mmb31c and all the connectivity issues were resolved.
After above experiment, I came to the conclusion that the issue with 7.1.1 is not just the radio, reason being that flashing radio of 6.0.1 did not fix it.
For next step I want to flash 7.1.1 , then flash radio AND kernel of 6.0.1 over it. to see if it will give me a good result or not,===== having 7.1.1 and solid connectivity.
Now my question is,:
Will having an older kernel flashed on 7.1.1 cause any failure? Will it be a good test? Does it even make sense? What would be the caveat of having old kernel on 7.1.1 ? Will features of 7.1.1 stop working?
Thanks,
You can't use an M kernel on N or vice versa. Won't work.
joseph230 said:
Hello,
Like many others, my phone was solid on 6.0.1. My phone was on shamu-mmb31c image that comes with radio radio-shamu-d4.01-9625-05.32+fsg-9625-02.109.
After upgrading to 7.1.1, I started to have wifi/connectivity issues. No workaround was helping.
I started flashing older radios in hope that it will fix the issue. Even radio of 6.0.1 (above) did not resolve the issue. To just prove to myself that issue is not hardware related I flashed back factory image of 6.0.1 shamu-mmb31c and all the connectivity issues were resolved.
After above experiment, I came to the conclusion that the issue with 7.1.1 is not just the radio, reason being that flashing radio of 6.0.1 did not fix it.
For next step I want to flash 7.1.1 , then flash radio AND kernel of 6.0.1 over it. to see if it will give me a good result or not,===== having 7.1.1 and solid connectivity.
Now my question is,:
Will having an older kernel flashed on 7.1.1 cause any failure? Will it be a good test? Does it even make sense? What would be the caveat of having old kernel on 7.1.1 ? Will features of 7.1.1 stop working?
Thanks,
Click to expand...
Click to collapse
Your issue is 7.1.1. Android N is full of issues that are causing many people to go back to android 6.0. Every Odd numbered release from google seems to be buggy ones.
zelendel said:
Your issue is 7.1.1. Android N is full of issues that are causing many people to go back to android 6.0. Every Odd numbered release from google seems to be buggy ones.
Click to expand...
Click to collapse
LOL, Seems Microsoft Windows curse is universal (95,98,2000,xp,vista,7,8,...10).
zelendel said:
Your issue is 7.1.1. Android N is full of issues that are causing many people to go back to android 6.0. Every Odd numbered release from google seems to be buggy ones.
Click to expand...
Click to collapse
I flashed radio of 7.1.1 over 6.0.1 and it did not cause any issues. This is a proof to what you just said. Kernel is full of bugs and that is hard to fix
Sticking with 6.0.1 for now! Maybe I should get back into using custom roms again!
Thanks.
joseph230 said:
LOL, Seems Microsoft Windows curse is universal (95,98,2000,xp,vista,7,8,...10).
Click to expand...
Click to collapse
Heck 98, XP and 7 were the only good ones. Dont even get me started on 10. I had to go back and revert over 300 PC to windows 7 when the 10 upgrade happed. That was just a nightmare.
What sort of issues are you talking about? Besides the speakerphone echo.
zelendel said:
Your issue is 7.1.1. Android N is full of issues...
Click to expand...
Click to collapse
I can confirm that.
Changed some things
Using lite stockROM of danvdh and Franco's kernel incl. speaker echo fix.
After debloat, decrypt and previous G-app(black) of TBO-team and removing Gmail and G-messenger it seems to work well.
Fingers crossed..., will report here.
Lawstorant said:
What sort of issues are you talking about? Besides the speakerphone echo.
Click to expand...
Click to collapse
Wifi and Radio connection drops all the time. Many people seem to experience it!
NLBeev said:
I can confirm that.
Changed some things
Using lite stockROM of danvdh and Franco's kernel incl. speaker echo fix.
After debloat, decrypt and previous G-app(black) of TBO-team and removing Gmail and G-messenger it seems to work well.
Fingers crossed..., will report here.
Click to expand...
Click to collapse
basically you are changing all the parts. I am hoping Google do that in future updates!!! Of course I doubt that since they do not care about old devices!
joseph230 said:
basically you are changing all the parts. I am hoping Google do that in future updates!!! Of course I doubt that since they do not care about old devices!
Click to expand...
Click to collapse
It seems to me that Google changed policy.
Till now the changes made the N6 great again.
No encryption, dark interface when possible.
Aquamail is better than Gmail, Signal is better than G-messenger. Nova launcher is better than G-now launcher.
I replace/disable G-apps and G-services when possible.
No Google Assistant, no Fit, no Pay, no Game, no Hangouts, no Wearable, no G-drive, no G-now.
Runs smoothly, no issues. Excellent battery life. Good to have XDA.
The touch delay is present since the release of Marshmallow, Nougat and Oreo ROMs in Titan (not sure about Falcon). There is no escape. It's good to see our 2014 devices with the latest version of the Android, but this error is very annoying and is being ignored. Doesn't matter how good the ROM is. If you using any custom ROM with Android 6.0 and up on titan, i'm sure you have this issue.
So i want to open a discussion about this issue here
If you don't know what i talking about, let's simulate the issue:
Try to write something in stock keyboard of your MM,Nougat or Oreo ROM. Now try pressing a second finger in the screen out of the keyboard and write anything else... You noticed? No?
Try to play a very intensive tap game, like Geometry Dash. Play a bit. Now play with a second finger on screen... You noticed?
Only KitKat and Lollipop Roms are free from this bug.
So, the only workaround for this touch delay is pressing a second finger on screen. Shame.
The questions left: Anyone knows a solution? The cause of this issue? There is no way to fix this?
I tried some custom kernels, no success.
I don't think anyone will ever fix this issue unfortunately,it was supposed to be fixed with the last official update(MM 6.0,bootloader 0x4887),but the problem is still there.
Metalhead666 said:
I don't think anyone will ever fix this issue unfortunately,it was supposed to be fixed with the last official update(MM 6.0,bootloader 0x4887),but the problem is still there.
Click to expand...
Click to collapse
Some people say the same on Lenovo Foruns...
Pixx 1001 said:
Some people say the same on Lenovo Foruns...
Click to expand...
Click to collapse
I think it is a kernel related issue rather than the bootloader,like some people said on lenovo foruns.I don't have proper knowledge to fix it,you could try to contact some of our developers,maybe there's still someone interested.
I don't notice this on the dirty unicorn 11.7 i am using this rom for daily driver , but can you tell if this problem happen in one rom or on all the roms ? and can you tell wat rom are you using? and dit you try a custom kernel with the rom wen the delay hapen ?
HiR3x said:
I don't notice this on the dirty unicorn 11.7 i am using this rom for daily driver , but can you tell if this problem happen in one rom or on all the roms ? and can you tell wat rom are you using? and dit you try a custom kernel with the rom wen the delay hapen ?
Click to expand...
Click to collapse
Every single ROM above 6.0 that I tested have this problem (Cm,AOKP,AOSP,Lineage,Slim,DU,CypherOS,AEX,CrDroid,RR and many more),with and without custom kernels.
I don't use my Moto G to play games , but some random games from PlayStore (Minigore 2, Bejeweled 2, Samurai II) the touch doesn't work well (or simply doesn't work! You can test all of them if you want). Using a 5.1 ROM, they work normally. It would be nice if the people post more problems about this touch issue happening on apps/games on Moto G Titan. I want to know if the same happens on Moto G Falcon, 4G variants.
Just stick to stock Lollipop rom guys. Newer versions of Android are just not meant to be on this phone, either on a custom or a stock ROM.
Jimisballjohn said:
Just stick to stock Lollipop rom guys. Newer versions of Android are just not meant to be on this phone, either on a custom or a stock ROM.
Click to expand...
Click to collapse
Well, I used ViperOs (7.1) as my daily driver at work, school for a good time (6 months I guess)... I liked Nougat Features and I guess I will keep using it, or another Nougat ROM, as they work perfectly for it on Titan.
Looks like titan Pie ROMs have the issue too (Used LineageOS 16 for testing).
It sucks that this still has not been resolved. Happened to me as well on LineageOS 16.
I do not feel this in the ROM of the Pixel Experience in the version of android 9, here the touch is normal.
LightWard said:
I do not feel this in the ROM of the Pixel Experience in the version of android 9, here the touch is normal.
Click to expand...
Click to collapse
I would like to test it myself and give a feedback, but sadly, my old Moto G2 had the input of the charger/usb connector broken. If anyone have tested the ROM too, would be good if they give a feedback here.