Related
Hi guys,
I've recently installed cyanogen on my IncS and thought that the Talk application has the new video option...ive flashed the latest gapps and the video option isnt there.
i thought this was odd as when i had HD Revolution Rom installed i could see the camera icons.
anyone come across this and fixed it?
Cyanogen 7.0 is based on 2.3.3.
Gtalk video is in 2.3.4, but I don't know if it's in the 7.1RC1 (think it needs a newer Gapps package than is listed on that thread).
The new Cyanogen RC1 for IncS is 2.3.4
I have a screenshot but i cant post outside links yet
From http://goo-inside.me/gapps
20110613: This package is designed for Android 2.3.4, and will not work on 2.3.3. It contains all of the applications updated for 2.3.4, but does not include the new Google Talk with video chat due to there being no compatible library available for non-ARM7 and non-neon board devices, from Google or another OEM.
Click to expand...
Click to collapse
So I guess we have to wait until there is an updated version that does work.
I noticed the same thing with rc1 of cm7. The camera option is not visible. I was surprised to find that it was on 2.3.4. It appears that miui latest is also running 2.3.4.
Sent from my HTC Incredible S using Tapatalk
On the hd revolution tom I can the camera icon...never tested whether it worked though
Sent from my Incredible S using Tapatalk
I tested video in Revolution HD but it didn't work properly, I saw the one behind computer, but he didn't see me...
If you are on CM7 RC or Nighties, Use this gtalk patch from Modaco.
Install the apk
run the app, patch the gtalk
uninstall the apk.
DONE!
didn't worked for me on wildfire....
i'ws looking for some good voice chat option for htc wildfire, found this but it just crashes if click on video option, and there's no voice option for me....
So, i tried that patch - it appears to have deleted my google account and now have no contacts - and now network data access
well its working beautifully on my inc s w/ cm7 nightly 15-50.
i actually factory reset my phone and reinstall the patch for couple of times, it never goes wrong. me and my girl use gtlk video often.
i dont know why funny problems happened on your guys phone.
The gtalk patch is working fine now, i just re-synced, re-setup my apn's and all is good.
Patch is working great
I flashed the nightly version of the Pac Man ROM to my HTC ONE earlier. Everything works great but I can't get the GPS to work. I thought it may have been google maps so I downloaded strava as well and GPS definitely does not work. It just continues to look for signal. I tried searching for a fix and wanted to post in the actual development thread, but I don't have enough posts so it directed me here to the general section. Any help would be appreciated. I know they release new updates each day so I will continue backing up and flashing to see if the new releases work was just curious if I was missing something. Thanks.
junglegreencleeds said:
I flashed the nightly version of the Pac Man ROM to my HTC ONE earlier. Everything works great but I can't get the GPS to work. I thought it may have been google maps so I downloaded strava as well and GPS definitely does not work. It just continues to look for signal. I tried searching for a fix and wanted to post in the actual development thread, but I don't have enough posts so it directed me here to the general section. Any help would be appreciated. I know they release new updates each day so I will continue backing up and flashing to see if the new releases work was just curious if I was missing something. Thanks.
Click to expand...
Click to collapse
You have to get on a stock sense build to get a GPS lock before you flash any aosp Rom to have a working GPS, backup your aosp flash sense get the lock on sense then restore aosp
Sent from my HTCONE using Tapatalk
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
I try ROMs and ROMs and ROMs and all are unusable, because the
phone freezes with nameless-5.1.1-20151107-p880-nightly or
reboots when starting apps with euphoria-os-1.1-p880-unofficial-20160208-user or
is extremely slow and is stottering with aosplp-20151122-p880
a..s.o
The apps which lead to a reboot with euphoria work fine with aosp and nameless. Euphoria is fast, faster than nameless, which would be fast enough for me. There are no problems which exist with every ROM.
Does anyone have a recommendation for a ROM for the P880 which works without big problems. At the moment I think about to go back to 4.4 and try beanstalk-4.4.4010-20140904-p880cm
Of course I would be happy to find a ROM with fixed stagefright-bugs, but it looks like to be impossible
lg-optimus said:
Of course I would be happy to find a ROM with fixed stagefright-bugs, but it looks like to be impossible
Click to expand...
Click to collapse
Check out http://forum.xda-developers.com/showpost.php?p=66049970&postcount=1195
This is the latest 5.1.1 ROM with security patch level at 2016-04-01. It has all known stagefright bugs fixed so far.
If you wish to report issues on the ROM I shared, then use the thread over there, not here.
MoltenMotherBoard is the last custom ROM that I miss to test. I'm going to try it in the next days.
According to my test, my answer to the thread question is: NO, there's no custom rom working fine for my daily use.
Actually fastest rom was liquid smooth 4.4.4. Our phone hardware outdated. Like the others said this phone is crap
I'm running Euphoria version 1.0-p880-20150130 (Android 5.0.2), it's the best Lollipop based custom ROM for our device in my opinion. Unlike AOSP it has more settings (& features), and it's more stable than later versions of Euphoria. If you want to stick to KitKat, check out the latest CM nightlies.
To be honest, after 2 years of testing custom ROM... today i finally found the best one to keep... STOCK!!!
I've re-discovered the pleasure of see who is calling me at once, not after 20 seconds. I can finally take photos, hear who is calling, open apps without having to wait like 20-30 seconds.
I appreciate the effort of every developer... but at the end, the result is that out of 20-30 custom ROMs for our phone... no one can be used for daily use and being happy with it
bs360 said:
To be honest, after 2 years of testing custom ROM... today i finally found the best one to keep... STOCK!!!
I've re-discovered the pleasure of see who is calling me at once, not after 20 seconds. I can finally take photos, hear who is calling, open apps without having to wait like 20-30 seconds.
I appreciate the effort of every developer... but at the end, the result is that out of 20-30 custom ROMs for our phone... no one can be used for daily use and being happy with it
Click to expand...
Click to collapse
having JellyBean running on your device in 2016 is a very very very bad idea.
Here's the issues I found with LG stock JB-4.1.2 ROM v20 euro-open. If you can live with them, then good for you.
- Bluetooth button action broken. Cannot invoke Google Search or Voice Dialer from bluetooth headsets. Fixed in custom ROM such as CM/AOSP KK and LP.
- No update for Google Maps. Version 7 is the final version for v20c. Fixed in CM/AOSP KK/LP.
- No notification from Lock Screen. Fixed in CM/AOSP LP.
- No smart lock to avoid the hassle of entering PINs for known location and known BT device. Fixed in CM/AOSP LP.
- No screen cast. Fixed in AOSP LP.
- No bluetooth tethering. Fixed in AOSP LP.
Actually I'm on stock now (euro 20c), and my version of Maps is 9.25.1.
But yes, you're right...I'm ok because for instance I don't use bluetooth at all.
I still miss to test "AOSP Lollipop 5.1.1 | MoltenMotherBoard"...but my question is: is smooth as the stock? Are these working ? camera, flash, barcode, dialer reader, calls in general..
thanks in advance
bs360 said:
Actually I'm on stock now (euro 20c), and my version of Maps is 9.25.1.
"AOSP Lollipop 5.1.1 | MoltenMotherBoard"...but my question is: is smooth as the stock?
Click to expand...
Click to collapse
When I was still on LG stock JB, Maps somehow got updated. But then the device slowed to crawl and I factory reset it and I didn't get Google Play store to update it again. Glad you have it and it works for you.
Barcode and FM radio are not working. If these 2 are important to you, then you should stick with LG stock.
For UI smoothness, I think Lollipop itself has made tons of improvement that it is at least the same or better than JB. Don't take my words for it, you should try it out yourself and pass on the judgement.
I reinstall again LS KK 4.4.4 and updated to latest Mourta's kernel from modaco forum. Phone back to alive.
asgz said:
I reinstall again LS KK 4.4.4 and updated to latest Mourta's kernel from modaco forum. Phone back to alive.
Click to expand...
Click to collapse
please link?
LS 3,2 4.4.4 and mourta's kernel inside of the file. I installed rom and open gapps after a few days wiped cache and updated kernel.
here is the link : http://s4.dosya.tc/server/uqoebl/LS_KK_4.4.4.rar.html
asgz said:
LS 3,2 4.4.4 and mourta's kernel inside of the file. I installed rom and open gapps after a few days wiped cache and updated kernel.
here is the link : http://s4.dosya.tc/server/uqoebl/LS_KK_4.4.4.rar.html
Click to expand...
Click to collapse
i just get an loop bot, i can't install a kernel..
Does anyone know how to fix the Ok Google voice function in android 7? It only works in the Google app and not everywhere.
tApPeD fROM mY nExUs 6
This works, if not try to do it with an older version of google app, and then update to latest beta
http://forum.xda-developers.com/showpost.php?p=69190540&postcount=82
Try the above, but for me that didn't work. The only alternative I found was to switch to a stock-based ROM. No one has been able to pin down the reason why as of yet, but OK Google detection simply isn't working correctly on Nexus 6 AOSP ROMs. Yet it works like a champ on my Galaxy S4 running Android 7.0 AOSP.
Strephon Alkhalikoi said:
Try the above, but for me that didn't work. The only alternative I found was to switch to a stock-based ROM. No one has been able to pin down the reason why as of yet, but OK Google detection simply isn't working correctly on Nexus 6 AOSP ROMs. Yet it works like a champ on my Galaxy S4 running Android 7.0 AOSP.
Click to expand...
Click to collapse
Just installed cyanide and it works very well
Is that a Cyanogenmod ROM? If so, that's not AOSP as I define it.
Strephon Alkhalikoi said:
Is that a Cyanogenmod ROM? If so, that's not AOSP as I define it.
Click to expand...
Click to collapse
No, i don't think so, it runs on aosp too, nitrogen
for example
I was running Pure Nexus the entire time, until this issue occurred. Obviously, Pure Nexus is an AOSP ROM, and nothing I tried worked. In fact, the last thing I tried, which was to install Open GApps instead of Pure Nexus GApps, completely crashed the Google app so it was impossible to complete setup.
For alternatives, I've tried running Nitrogen and one other ROM, though I forgot which one. All of them built with an AOSP core, and all of them failed. The only ROMs that actually worked were danvdh's stock lite ROM and tupac4u's debloated stock. Factory resets do not help. I tried that as well and the problem still presents itself when an AOSP ROM is installed. Since only the stock ROMs have worked for me, there has to be an issue somewhere in the AOSP ROMs that is causing this.
Oh, and before I forget, Cyanogenmod is not an option. I refuse to run it on this device, and in fact none of the devices suitable for use as a daily driver in house use it.
Strephon Alkhalikoi said:
I was running Pure Nexus the entire time, until this issue occurred. Obviously, Pure Nexus is an AOSP ROM, and nothing I tried worked. In fact, the last thing I tried, which was to install Open GApps instead of Pure Nexus GApps, completely crashed the Google app so it was impossible to complete setup.
For alternatives, I've tried running Nitrogen and one other ROM, though I forgot which one. All of them built with an AOSP core, and all of them failed. The only ROMs that actually worked were danvdh's stock lite ROM and tupac4u's debloated stock. Factory resets do not help. I tried that as well and the problem still presents itself when an AOSP ROM is installed. Since only the stock ROMs have worked for me, there has to be an issue somewhere in the AOSP ROMs that is causing this.
Oh, and before I forget, Cyanogenmod is not an option. I refuse to run it on this device, and in fact none of the devices suitable for use as a daily driver in house use it.
Click to expand...
Click to collapse
i actually think its a google now issue. both my lg k7 and lg blahblahblah both had it working on any screen, then it stopped working, and options disappeared. a few days later, the options reappeared, i enabled them, and now works again on any screen.
I guess I didn't word things quite right, as I meant to say the interaction between the Google app and ROM was causing the issue. Hopefully you're right about it being app related so I can move back to Pure Nexus.
I'll give it a shot... I'm running Chroma MM and it works but not in Nitrogen OS. I think it was working on the sky dragon ROM but I was having corruption issues on boot with it while using multirom.
tApPeD fROM mY nExUs 6
Coming to find out, in my case it apparently wasn't app or ROM related. As of right now I have OK Google anywhere working properly with Pure Nexus, and sticking through reboots as well. My solution?
Follow the ROM instructions.
Pure Nexus requires updating both bootloader and modem and strongly recommends using fastboot to do it. I had done the update about two weeks prior to Pure Nexus being released, but using flashable zips that are available on the forums. Obviously, those zips did not flash a complete package.
EDIT: OK Google detection is once again broken. Hopefully Google solves this problem, because this is annoying.
Anybody figure this out? It only seems to work on factory images, not AOSP ROMs.
Strephon Alkhalikoi said:
Coming to find out, in my case it apparently wasn't app or ROM related. As of right now I have OK Google anywhere working properly with Pure Nexus, and sticking through reboots as well. My solution?
Follow the ROM instructions.
Pure Nexus requires updating both bootloader and modem and strongly recommends using fastboot to do it. I had done the update about two weeks prior to Pure Nexus being released, but using flashable zips that are available on the forums. Obviously, those zips did not flash a complete package.
EDIT: OK Google detection is once again broken. Hopefully Google solves this problem, because this is annoying.
Click to expand...
Click to collapse
Sorry to rehash this but it's a bit of a bump. It's actually not Google's fault. OoenGapps made a change back in September, changing HotwordEnrollment.apk. okGoogle anywhere has been broken ever since. It's only happening to AOSP Roms like the person above stated. The maintainers of CM for the 6P are trying to get to the bottom of it to see if they can do anything to fix the issue.
MrBrady said:
Anybody figure this out? It only seems to work on factory images, not AOSP ROMs.
Click to expand...
Click to collapse
Try to freeze the hotword enrollment apk.....I use ROM Toolbox Pro for this. It is a system app.....froze it and then followed the directions around the forums and google assistant worked for me on nitrogen on screen off, it seemed to me to be a little more "finicky" at starting from screen off then on stock, but that could just be me and how my voice training was saved or whatever....good luck