After lots of frustration and hours to make this work, It's done.
This Google Dialer works just like the one in the Nexus 5 stock.
What's the difference between this dialer and the CM11 dialer?
1.) On the dial screen, it allows you to type a name of a business or "place" and the dialer will show you the closest numbers to you for fast dialing
2.) Incoming Caller ID Lookup, This compares your incoming call to the same database for any name lookup and/or picture lookup, in January or soon after, it will show contacts for Google+ on the caller ID screen. As far as I know, you do not have to have this person in your circles to have the caller id show.
How do you install it?
1.) First and very formost. This is for Cyanogenmod 11 with 4.4.1+. If you try to do it on any earlier Android version, you'll most likely get lots of force closes and your phone will stop functioning altogether... You've been warned...
2.) Boot into recovery
3.) Backup
4.) Flash this file: http://www.tinozplace.com/moto-kitkat/12-10_GoogleDialer_4.4.1_signed.zip or for 4.4.2,
http://www.tinozplace.com/moto-kitkat/12-12_GoogleDialer_4.4.2_signed.zip
5.) Reboot
6.) Profit???
I edited the installer file to delete dialer.apk, so you no longer have to do that.
Enjoy!
If you'd like, I have built the dialer into my gapps. This way you don't need to flash several zips each time you upgrade to a new nightly.
http://www.tinozplace.com/moto-kitkat/12-17-gapps-wDialer.zip
NOTE:
You can link to this post, however mirroring and posting the link to my site on any other forums is strictly prohibited. I worked for weeks doing research and was finally completed yesterday.
Tested to be working on:
HTC One
Motorola xt926
Motorola xt925
Motorola mb886
Sprint Galaxy S4 (Verizon)
If you have confirmed this zip is working on any other roms or phones, please post here
EDIT: Gapps fixed to allow use on other phones. Someone was complaining that Wifi was being interfered with, along my travels, I found that certain versions of CloudPrint was getting in the way. Updated to 4.4.1 CloudPrint2.apk.
EDIT: Works with 4.4.2
EDIT: Reports of the LTE toggle (in the quick settings panel) being broken have come to my attention. There isn't much I can do about this. It's google's code, not "backwards-compatible" with AOSP. You'll have to choose the dialer or the LTE toggle, sorry.
EDIT: If you downloaded 12/10gappswDialer, redownload the latest. Somehow, I forgot to put the APK's in the zip. Very sorry about this.
Did you test this on aosp roms base on android 4.4.1?
Just CM..
Wow fantastic work. I'm assume this would work on SlimKat. I just have to find the balls.
Reach down in your pocket, you'll find them
Let me know if it does work, my guess is it will as long as you are on 4.4.1
Reach down in your pocket, you'll find them
Heck, if you do a backup, there should be nothing to worry about.
Let me know if it does work, my guess is it will as long as you are on 4.4.1
Congrats man. I've been watching your progress on this and can't wait to give it a try next time I flash a kitkat rom
Heck yeah man!!! Nice work. I know you had your doubt's about this one so its nice to see that you figured it out.
Sent from my Nexus 7 using Tapatalk
Great job. I think I'll finally jump to CM11 tonight and give this a spin. :good:
If you are on a different device, use the dialer without the gapps. I'll fix the gapps tomorrow
Sent from my XT926 using Tapatalk
Works on ose rom xt925
Envoyé depuis mon XT925 avec Tapatalk
spart'84120 said:
Works on ose rom xt925
Envoyé depuis mon XT925 avec Tapatalk
Click to expand...
Click to collapse
Gapps Fixed for other devices (See OP)
Working on mb886!!!
Sent from my MB886 using Tapatalk
Thanks. OP updated
Sent from my Nexus 7 using Tapatalk
This dialer works, but after i flash it, i got FC in settings/interface/quick settings panel, allso /quick settings panel/tiles and layout.
I use CM11 today build, also on yesterday build was the same.
If i flash a clean build those settings works fine, after i flash this google dialer i got the problems.
XT925
darktyroll said:
This dialer works, but after i flash it, i got FC in settings/interface/quick settings panel, allso /quick settings panel/tiles and layout.
I use CM11 today build, also on yesterday build was the same.
If i flash a clean build those settings works fine, after i flash this google dialer i got the problems.
XT925
Click to expand...
Click to collapse
Are you flashing the Gapps with the dialer or just the dialer?
I do not have that problem, my guess is that you have the LTE toggle? That probably won't work because this dialer is Google source and CM is AOSP.
Did you have this problem in previous nightlies? or did you just start using this dialer?
Would this gapps are propper for ART?
Sent from my XT925 using Tapatalk
motopuk said:
Would this gapps are propper for ART?
Sent from my XT925 using Tapatalk
Click to expand...
Click to collapse
Yes. It's all I will ever release
abuttino said:
Are you flashing the Gapps with the dialer or just the dialer?
I do not have that problem, my guess is that you have the LTE toggle? That probably won't work because this dialer is Google source and CM is AOSP.
Did you have this problem in previous nightlies? or did you just start using this dialer?
Click to expand...
Click to collapse
Well i flash both. Simple dialer and gapps with dialer. Same problem. It makes FC when i press on those settings but after that i can use the settings.
Sent from my Motorola Razr HD XT925 using Tapatalk 2
I updated the OP to explain this.
Related
Hey all,
The GTalk video call fc bug on CM10 has been discussed sparsely in various threads and in order not to spam/pollute them even more with posts regarding the issue i decided to make a new one, just to figure out if it really works ok for some and why's that. Recently it was mentioned that if one flashes the Xoom modded gapps (by EOS team - found here http://forum.xda-developers.com/showthread.php?t=1777987) he'll get video call running since the EOS team has modded the package in order to work with non-NEON devices (or something like that - haven't been able to find clear documentation in their thread). I flashed said gaps package and, even though the phone is able to initiate the video call in the background, i get a foreground 'unfortunately gtalk has closed' or so message. Thats definitely better than before when the program was simply crashing, but doesn't solve the issue. Audio calls run fine though. Pengus mentioned that he wiped dalvik/cache, flashed EOS gapps, rebooted and rebooted again and it worked. Didnt happen for me, still same issue on video calls. I must also note that even b4 flashing EOS gapps, i was able to do video calls and even videoconference (3 way video call) using G+ hangouts, so it must be a program specific issue more than a general android libs situation (excuse my ignorance - doing my best to understand how things work in this OS ). So how do this run for you people? Is there anyone who managed to get it running fine on CM10, and if yes, can you give some details on your current setup? Also, if you did manage to get it running, did you follow a different flashing procedure than the one mentioned here? Thanx for your replies/participation
My current setup: CM10 3/1 nightly, old BL, v28e BB, EOS gapps
Peace
Ximo F. Verde said:
Hey all,
The GTalk video call fc bug on CM10 has been discussed sparsely in various threads and in order not to spam/pollute them even more with posts regarding the issue i decided to make a new one, just to figure out if it really works ok for some and why's that. Recently it was mentioned that if one flashes the Xoom modded gapps (by EOS team - found here http://forum.xda-developers.com/showthread.php?t=1777987) he'll get video call running since the EOS team has modded the package in order to work with non-NEON devices (or something like that - haven't been able to find clear documentation in their thread). I flashed said gaps package and, even though the phone is able to initiate the video call in the background, i get a foreground 'unfortunately gtalk has closed' or so message. Thats definitely better than before when the program was simply crashing, but doesn't solve the issue. Audio calls run fine though. Pengus mentioned that he wiped dalvik/cache, flashed EOS gapps, rebooted and rebooted again and it worked. Didnt happen for me, still same issue on video calls. I must also note that even b4 flashing EOS gapps, i was able to do video calls and even videoconference (3 way video call) using G+ hangouts, so it must be a program specific issue more than a general android libs situation (excuse my ignorance - doing my best to understand how things work in this OS ). So how do this run for you people? Is there anyone who managed to get it running fine on CM10, and if yes, can you give some details on your current setup? Also, if you did manage to get it running, did you follow a different flashing procedure than the one mentioned here? Thanx for your replies/participation
My current setup: CM10 3/1 nightly, old BL, v28e BB, EOS gapps
Peace
Click to expand...
Click to collapse
Hi,
here is what I did to solve this: I just took the libvideochat_jni.so from the eos-package and pushed it to /system/lib. Afterwards I cleared gtalk data and cache, restarted the device. Finally I could do video-calls
I've also attached the libvideochat_jni.so I used, maybe someone can make a flashable zip from it. I'm on pengus latest rom+kernel by the way.
Regards,
orgler
orgler said:
Hi,
here is what I did to solve this: I just took the libvideochat_jni.so from the eos-package and pushed it to /system/lib. Afterwards I cleared gtalk data and cache, restarted the device. Finally I could do video-calls
I've also attached the libvideochat_jni.so I used, maybe someone can make a flashable zip from it. I'm on pengus latest rom+kernel by the way.
Regards,
orgler
Click to expand...
Click to collapse
thanx for the tip mate. pushed the file w quick adb pusher, wiped app's data/cache but still get fc when trying to video call.. all this after i moved to official cm10.1, but i doubt that thats the problem. what a terrible bug #@$%&$#@&!!!!
Sent from my LG-P990 using xda app-developers app
reverted to cm10, gonna try it out again.
Sent from my LG-P990 using xda app-developers app
I didn't even wipe dalvik cache. Just the gtalk data. And then I did a reboot. Does voice chat work? Does the app just close or do you get a fc?
Gesendet von meinem LG-P990 mit Tapatalk 2
ok, went back to cm10 3/1 nightly (old BL), flashed pengus' new kowalski kernel, pushed the .so file, deleted talk's data, rebooted. getting instant fc on both video and audio calls. :banghead:
Sent from my LG-P990 using xda app-developers app
Could you create a logcat?
Gesendet von meinem LG-P990 mit Tapatalk 2
ok, doin it now
Sent from my LG-P990 using xda app-developers app
There you go. Logcat of fc first on video call n then on audio call. View attachment gtalk-video-audio-fc-logcat.txt
I installed the gapps and gtalk video work after my first reboot.
gTalk video doesn't work for me either... Hangouts work, even though they had a hard time starting to work, but eventually I was able to do a video conference, after some hangs and reboots...
The simplest of features don't work on android 4.x... I like the fluidity but this is starting to get irritating...
wucinac said:
I installed the gapps and gtalk video work after my first reboot.
Click to expand...
Click to collapse
what rom? BL? gapps?
Sent from my LG-P990 using xda app-developers app
LarsPT said:
gTalk video doesn't work for me either... Hangouts work, even though they had a hard time starting to work, but eventually I was able to do a video conference, after some hangs and reboots...
The simplest of features don't work on android 4.x... I like the fluidity but this is starting to get irritating...
Click to expand...
Click to collapse
hangouts worked with no issues for me.. but the gtalk fc's really start to irritate me as well, especially because it seems that for some it runs well, but dont know why. another BL issue then?
Sent from my LG-P990 using xda app-developers app
Ximo F. Verde said:
what rom? BL? gapps?
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
new bootloader, P.A. by tonyp, [email protected] kernel, gapps with gtalk video chat and JT Inverted Productions JusTunBean Inverted JB.
I flash this order and everything works ok.
it seems that it works on some new bl roms. anyone that got it workinh on the old bl? (or anyone that can figure out what went wrong on the logcat i posted a few posts above? had flashed the eos gapps .so file mentioned on p.1)
Sent from my LG-P990 using xda app-developers app
Here is my logcat of GTalk FC with suggested library http://pastebin.com/pX3hTBjB
UPD: seems i have fixed GTalk video...
You need to take from eos Talk.apk, libvideochat_jni.so, libvideochat_stabilize.so and check, if you have original /system/lib/hw/camera.tegra.so. If you experimented with ICS cam, camera.tegra.so possibly changed.
wfd said:
Here is my logcat of GTalk FC with suggested library http://pastebin.com/pX3hTBjB
UPD: seems i have fixed GTalk video...
You need to take from eos Talk.apk, libvideochat_jni.so, libvideochat_stabilize.so and check, if you have original /system/lib/hw/camera.tegra.so. If you experimented with ICS cam, camera.tegra.so possibly changed.
Click to expand...
Click to collapse
wow great news. Where did u push Talk.apk and libvideochat_stabilize.so? I havent flashed ICS cam, so i guess camera.tegra.so shouldn't need any changes.
EDIT: Nevermind, found them.
/system/app/Talk.apk
/system/lib/libvideochat_stabilize.so
Oh, and you should take libs from optional/noneon/lib folder in eos archive
Don't forget about permissions and owner (644 root:root)
wfd said:
/system/app/Talk.apk
/system/lib/libvideochat_stabilize.so
Oh, and you should take libs from optional/noneon/lib folder in eos archive
Don't forget about permissions and owner (644 root:root)
Click to expand...
Click to collapse
Sorry you've confused me a bit now. Take which libs from optional/noneon/lib folder? libvideochat_stabilize.so and libvideochat_jni.so only, isnt it? Because these files also exist in the EOS package in system/lib. And permissions/owner for which files?
Ximo F. Verde said:
Sorry you've confused me a bit now. Take which libs from optional/noneon/lib folder? libvideochat_stabilize.so and libvideochat_jni.so only, isnt it? Because these files also exist in the EOS package in system/lib. And permissions/owner for which files?
Click to expand...
Click to collapse
Cant seem to be able to change permissions/owner.. Can you tell me in detail how's you do that?
Unlocked Bootloader required. Must flash via CWM or TWRP. Do not use Safestrap.
These ROMs are mostly stable. Expect bugs and occasional instability/crashes. Flash at your own risk.
Instructions
Make a backup beforehand
Wipe Data, Cache, and Format System
Install ROM & GApps
CM10 by Hashcode -- enable USB debugging for MTP
Bugs: lockscreen display artifacting, camera only works in 3MP or 8MP, no BT music
GPS: Settings -> Location Access -> GPS Source -> click Use Internal GPS
ROM: http://d-h.st/RQm
GApps: http://goo.im/gapps/gapps-jb-20121011-signed.zip
OpenPDroid for CM10 -- allows total privacy control over your apps
Patch ZIP: http://forum.xda-developers.com/attachment.php?attachmentid=1891228
PDroid Manager (required): http://forum.xda-developers.com/showthread.php?t=1994860
Undo/Removal ZIP: http://forum.xda-developers.com/attachment.php?attachmentid=1891232
=================================================
Extra: CM10.1 by Hashcode -- no camera; if you want camera, install Epinter's 10.1 for XT926
ROM: http://goo.im/devs/Hashcode/vanquish/cm10.1
GApps: http://goo.im/gapps/gapps-jb-20130301-signed.zip
==================================================
All credit goes to Epinter, Hashcode, dhacker, and especially Dan Rosenberg for the bootloader. Donate to them if you use this!
Dan: http://vulnfactory.org/blog/2013/04/08/motorola-bootloader-unlocking/
Epinter: http://forum.xda-developers.com/donatetome.php?u=3721576
Hashcode, dhacker: http://blog.hash-of-codes.com/
Click "Thanks" for the CM10 upload. You won't find it anywhere else. Enjoy!
Nice, finally development is coming along. Dl now thanks
Sent from my XT926 using Tapatalk 2
do we need to mount system before flashing? also, do we need to wipe system?
forgot to ask in my original post, but do you have the link for gapps?
I flashed the most recent gapps from vitreous. Works fine. The camera is not present for me however :S
Sent from my XT926 using xda app-developers app
sunkim50 said:
forgot to ask in my original post, but do you have the link for gapps?
Click to expand...
Click to collapse
http://goo.im/gapps/
I flashed the cm10 and camera works. The only thing I've found is that when I turn my screen off or lock it, it doesn't really go off. Lines start appearing lightly then they get brighter and brighter... Not sure what's going on. I see cm10.1 was added as a bonus to this post. Does that mean the camera is fixed on cm10.1 also?
Sent from my XT926 using Tapatalk 2
an21281 said:
I flashed the cm10 and camera works. The only thing I've found is that when I turn my screen off or lock it, it doesn't really go off. Lines start appearing lightly then they get brighter and brighter... Not sure what's going on. I see cm10.1 was added as a bonus to this post. Does that mean the camera is fixed on cm10.1 also?
Sent from my XT926 using Tapatalk 2
Click to expand...
Click to collapse
I'll let you know when I flash this...like...NOW
an21281 said:
I flashed the cm10 and camera works. The only thing I've found is that when I turn my screen off or lock it, it doesn't really go off. Lines start appearing lightly then they get brighter and brighter... Not sure what's going on. I see cm10.1 was added as a bonus to this post. Does that mean the camera is fixed on cm10.1 also?
Click to expand...
Click to collapse
That is an odd issue. I'm not experiencing that. Did you install any apps or modifications?
As for 10.1, I just found the file from Hashcode and linked it, so I don't know about the camera. I'm only interested in 10 for now as it's more stable. Give it a shot and let us know.
Camera does not work in 10.1, I flashed it earlier. Everything else seems pretty smooth though.
Yea, I am experiencing the same problem as the guy above. Those lines act as its like a screensaver lol idk. when it disappear, it takes awhile me to unlock the phone. Dbl press power to make sure its off then press power multiple times to turn screen back on. Other then this problem its running like a champ!
Cm 10.1- I had problems with WiFi not turning on, it did work then it just stopped
Can't make work cm10 with gsm. It's only lte/cmda. cm10.1 works fine, but constantly process com.android.phone stops...
I'm installing them over modded deodexed 4.0.4.
Should I install those ROMs over stock 4.1.1?
Sent from my DROID RAZR HD using xda app-developers app
anddep said:
Yea, I am experiencing the same problem as the guy above. Those lines act as its like a screensaver lol idk. when it disappear, it takes awhile me to unlock the phone. Dbl press power to make sure its off then press power multiple times to turn screen back on. Other then this problem its running like a champ!
Cm 10.1- I had problems with WiFi not turning on, it did work then it just stopped
Click to expand...
Click to collapse
Same problem with the lock screen here. works great besides that.
Just changed lock screen clock to center and problem disappeared
Nm still there
Sent from my XT926 using Tapatalk 2
progrockguy said:
Unlocked Bootloader required. Must flash via CWM or TWRP. Do not use Safestrap if you want a working camera.
Install ROM and GApps. Wipe Cache & Factory Reset. Then reboot.
All credit goes to Epinter, Hashcode, and especially Dan Rosenberg for the bootloader. Donate to them if you use this!
Dan: http://vulnfactory.org/blog/2013/04/08/motorola-bootloader-unlocking/
Epinter: http://forum.xda-developers.com/donatetome.php?u=3721576
Hashcode: http://blog.hash-of-codes.com/
Click "Thanks" for this upload. Enjoy!
CM10: http://d-h.st/RQm
GApps: http://goo.im/gapps/gapps-jb-20121011-signed.zip
=================================================
BONUS: CM10.1 by Hashcode:
http://goo.im/devs/Hashcode/vanquish/cm10.1/cm-10.1-20130124-UNOFFICIAL-xt926.zip
Click to expand...
Click to collapse
What's the difference between cm10 and the bonus cm10.1? Sorry if that's a bad question..
Sent from my DROID RAZR HD using Tapatalk 2
I think one is ICS & the other is JB if I remember correctly.
Sent from my DROID RAZR HD using Tapatalk 2
Hashcodes' CM 10.1 is running like a champ other than the camera and video not worker. I believe soon that won't be an issue. I'm using it as a daily and loving it. Can't wait top see more Roms like AOKP and PA
---------- Post added at 10:55 AM ---------- Previous post was at 10:54 AM ----------
rebretz000 said:
I think one is ICS & the other is JB if I remember correctly.
Sent from my DROID RAZR HD using Tapatalk 2
Click to expand...
Click to collapse
They both are JB. 10 is 4.1 while 10.1 is 4.2
I can't get Media audio to play via speaker or Bluetooth. anyone else?
Sent from my XT926 using Tapatalk 2
itsdubai said:
What's the difference between cm10 and the bonus cm10.1? Sorry if that's a bad question..
Sent from my DROID RAZR HD using Tapatalk 2
Click to expand...
Click to collapse
CM10 is JB 4.1.2 and CM10.1 is JB 4.2.2
koftheworld said:
Same problem with the lock screen here. works great besides that.
Just changed lock screen clock to center and problem disappeared
Nm still there
Sent from my XT926 using Tapatalk 2
Click to expand...
Click to collapse
I just changed the clock and my phone still does the same. The lines start to appear slowly in red and get brighter. It's hard to see it immediately daytime but at night you can see it easily. After a minute it's very bright though. I thought it had to do with the notification light since when you set that and try to test it the same thing happened s with screen off but much faster.
I shut off notification light since then and still there also. Never seen this issue before. Either way getting the camera working is a big step! Thanks again
Sent from my XT926 using Tapatalk 2
Looks like the CM10 download site is blocked at work for me, is there a mirror anywhere? Thanks.
Got it downloaded, working real nice so far, very smooth. I do have the lockscreen issue too. This is amazing, so glad to have CM on this phone. Thanks to all.
I could need some help.
I just finished installing [ROM-AOSP] Official CM10.1 (JB 4.2.2) [NIGHTLIES] from the dev forums. Everything seems to be working just fine, except sending SMS's.
I can receive them but every SMS I try sending, fails.
I tried updating the SMSC number from the *#*#6496#*#* menu and toggle on/off some of the settings there, but nothing changed.
radio On
IMS registration required OFF
SMS over IMS ON
lte ram dump OFF
Edit: installed Nightly 5/30 gapps 4.2.2 GSM network RO
Thanks
Are you using gsm network did your internet connection work
Sent from my XT894 using xda app-developers app
silviu6482 said:
I could need some help.
I just finished installing [ROM-AOSP] Official CM10.1 (JB 4.2.2) [NIGHTLIES] from the dev forums. Everything seems to be working just fine, except sending SMS's.
I can receive them but every SMS I try sending, fails.
I tried updating the SMSC number from the *#*#6496#*#* menu and toggle on/off some of the settings there, but nothing changed.
radio On
IMS registration required OFF
SMS over IMS ON
lte ram dump OFF
Thanks
Click to expand...
Click to collapse
I am working on a solution with a friend of mine now....
there is a workaround as we speak....
use VZW Messenger... everything works there.
Keep your eyes opened and I will try to keep you updated as progression is made.
je2854 said:
I am working on a solution with a friend of mine now....
there is a workaround as we speak....
use VZW Messenger... everything works there.
Keep your eyes opened and I will try to keep you updated as progression is made.
Click to expand...
Click to collapse
Thank you, just saw the reply, will try and install the app and confirm if it works.
Now to find the apk... seems like i have to manually install if i find it since i'm not on VZN or in the US for that matter.
Edit: installed VZmessages and HC SMS together with the latest Nightly 05/30 .. sms still not working. (Works fine stock 4.1.2 though).
NighPlayer32 said:
Are you using gsm network did your internet connection work
Sent from my XT894 using xda app-developers app
Click to expand...
Click to collapse
Yes, I'm on a gsm network, orange ro.
I don't have a data plan so i didn't bother trying.
silviu6482 said:
Yes, I'm on a gsm network, orange ro.
I don't have a data plan so i didn't bother trying.
Click to expand...
Click to collapse
ok I have a same issue but with TobbysMod script it is all fixed it
this ist from a german siete but it only patch the build.prob for GSM an some other fixes an keyped changes for ö ä ü (Caps+A/O/U)
hier a link
https://mega.co.nz/#!9kRTCICB!D228WW7MtPUZPWjHRKGcMQVGOixqjQs3a-_77QerNNg
NighPlayer32 said:
ok I have a same issue but with TobbysMod script it is all fixed it
this ist from a german siete but it only patch the build.prob for GSM an some other fixes an keyped changes for ö ä ü (Caps+A/O/U)
hier a link
Click to expand...
Click to collapse
Seems i'll have to download it from home as i can't download directly on my phone. Thanks will let you know if it works.
Sent from my DROID4 using xda app-developers app
Same problem
Hey guys I am having this same problem, but I'm using the phone on Verizon. The problem just began with the June 2nd Nightly. I tried entering the Dialer menu but, when I finish entering the number *#*#6496#*#* it just dissapears. Any help?
Edit: Reverted back to the June 1st nightly and texting is working again.
IndiaBhai said:
Hey guys I am having this same problem, but I'm using the phone on Verizon. The problem just began with the June 2nd Nightly. I tried entering the Dialer menu but, when I finish entering the number *#*#6496#*#* it just dissapears. Any help?
Edit: Reverted back to the June 1st nightly and texting is working again.
Click to expand...
Click to collapse
It should dissapear and bring up a menu. If it doesn't yours is weirder than mine.
The below information is obsolete. Please use the official obake version of CM12 for support on 2013 Droid devices.
A small patch I put together to make the new CM11 Ghost builds work (kinda) on the 2013 Droid Ultra series phones (Mini, Ultra, Maxx). It may also work for other Ghost based ROMs, but I haven't tested this.
So far, it's been lightly tested on the Droid Ultra M (Mini), and Droid Ultra Maxx. No guarantees, but it's been working okay so far for me.
Thanks to @an21281 for testing, and @mainbord for the original Droid Mini bins. Thanks also to the CM team for supporting us without even knowing it. =)
YOU ACCEPT RESPONSIBILITY FOR ALL RISKS BY CHOOSING TO USE THIS PATCH
- If it breaks your phone, you get to keep both halves. If it eats your data, not my problem. Etc, etc.
- If you are lazy or like to take shortcuts, definitely don't use this.
Requirements:
- Unlocked bootloader. Phone should be on newest stock bootloader, radio, etc. (4.4.4 currently)
- Philz recovery for ghost: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/ghost/
- CM11 Ghost: CM11 Ghost
- GApps. I use the PA Nano package: PA Gapps
Instructions:
- Boot to recovery, and wipe data and cache.
- Install CM11 Ghost, then GApps, then the patch
Notes:
- This is done in my free time, and isn't something I plan on supporting. If I have time, I may make updates.
- I'm not actually using CM11 on my phone at the moment, so can't test things currently.
- TWRP for ghost doesn't set the right properties. Go bug them.
- The huge "full" GApps packages can fill up /system and break ****.
Changelog:
0.6 - 4.4 bins
0.8 - 4.4.4 bins
** Please search the forum or Google your question before posting. Thanks! **
Thank you so much!!
Man, i kept trying to figure out how to rewrite the build.prop and change the binaries to be able to flash the ones that switched to the ghost source. I really, really, appreciate this patch. Maybe with the present state of BL unlock and the super cheap price on the maxx we will actually (for once) see a large amount of development for the msm8960dt branch and not just be limited to the ghost builds. thank you for this, again.
Thanks for taking the time to make this patch, everything has been working perfectly so far!
kitcostantino said:
Man, i kept trying to figure out how to rewrite the build.prop and change the binaries to be able to flash the ones that switched to the ghost source. I really, really, appreciate this patch. Maybe with the present state of BL unlock and the super cheap price on the maxx we will actually (for once) see a large amount of development for the msm8960dt branch and not just be limited to the ghost builds. thank you for this, again.
Click to expand...
Click to collapse
Glad to hear it's working for you.
At least as far as the Maxx goes, all the heavy lifting was done by the CM11 folks.
The patch for the maxx is one binary file for the button lights, two simple configs, and a few lines in build.prop.
I'll be curious if the patch works for the plain Ultra.
Rottgrub said:
Glad to hear it's working for you.
At least as far as the Maxx goes, all the heavy lifting was done by the CM11 folks.
The patch for the maxx is one binary file for the button lights, two simple configs, and a few lines in build.prop.
I'll be curious if the patch works for the plain Ultra.
Click to expand...
Click to collapse
Droid mini CM, keys and sound works!
This patch is going to be very useful if Lollipop is going to integrate the best of Motorola. This means I'll be able to flash CM ghost and still have native active display or whatever it is called in the Nexus 6. At that point, the customs ROMs will actually be relevant to the Moto X and Droid Maxx.
Sent from my iPad using Tapatalk
mainbord said:
Droid mini CM, keys and sound works!
Click to expand...
Click to collapse
Great! Thanks for getting the ball rolling! Guessing you figured out the camera problem you were having? (I was guessing maybe a gapps issue with the Google Camera?).
Problem with camera was in 19oct nightly, i installed 21 oct build and it works. Sorry for my english.
mainbord said:
Problem with camera was in 19oct nightly, i installed 21 oct build and it works. Sorry for my english.
Click to expand...
Click to collapse
Your English is fine. Thanks for the warning about that build date.
So when CM has a lollipop build (CM12?), we might be able to use this patch and have the Google version of Active (Ambient) Display? The only thing that keeps me from running CM is lack of a smooth working Active Display. This would be great news!
What happened to half of the pages in this thread
Sent from my XT1080 using Tapatalk
nubia11 said:
What happened to half of the pages in this thread
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
I asked the mods to clean up the off topic posts. The posts removed were requests for information either already contained in the first post, or easily found with a quick Google search. Unfortunately, these sorts of posts contribute nothing to the discussion, and make it hard for readers to find actual data when/if they have problems.
That said, I'm glad people were able to help you out. Have you had any luck getting it working?
No. I'm not sure if I can use twrp ghost on my XT1080.... If so I will try it and let you / others
Sent from my XT1080 using Tapatalk
---------- Post added at 10:45 AM ---------- Previous post was at 10:44 AM ----------
nubia11 said:
No. I'm not sure if I can use twrp ghost on my XT1080.... If so I will try it and let you / others know
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
Sent from my XT1080 using Tapatalk
It isn't working... Here is what I get... "This package is for device xt1056" also... Error executing updater binary in zip/sdcard/cmghost/cm-11 11 20141023-nightly..........and so on. Any ideas?
Sent from my XT1080 using Tapatalk
I'm just wondering if maybe I didn't flash something right. You would think that the patch would go first but I did exactly what was in the op
Sent from my XT1080 using Tapatalk
nubia11 said:
I'm just wondering if maybe I didn't flash something right. You would think that the patch would go first but I did exactly what was in the op
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
Install Philz CWM recovery. Boot to recovery, and wipe data and cache.
Install CM11 Ghost, then GApps, and only then the patch.
Thank you
Sent from my XT1080 using Tapatalk
I'm getting flashing error
aneeshmbabu said:
I'm getting flashing error
Click to expand...
Click to collapse
Make sure you're using Philz recovery.
Sent from my XT1060 using Tapatalk
jakereeves31 said:
Make sure you're using Philz recovery.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
I'm using twrp , how to flash philz recovery.. I already installed twrp.. Thanks for ur help , step wise help needed for flashing philz recovery.. My model xt1080,droid maxx
Hello,
I searched the internet for a capps.zip file from COS13 to flash on my One running CM13 as the truecaller integration is absent from the dialler in the unofficial capps v2[probably modded from the COS12.1 to work with CM13] , which is the feature i liked the most,not to mention,of course, also the call receiving and in-call UI of the COS dialler... and I do not know jack about developing myself so if someone could extract the files from COS13 and make them into a flashable zip..
Thank you.
http://forum.xda-developers.com/showpost.php?p=66281005&postcount=12336
qaliza said:
http://forum.xda-developers.com/showpost.php?p=66281005&postcount=12336
Click to expand...
Click to collapse
I've flashed your zip and I get a reboot every time I make a call. I'm using the latest sultan CM13.
Skeer_boy said:
I've flashed your zip and I get a reboot every time I make a call. I'm using the latest sultan CM13.
Click to expand...
Click to collapse
I'm still one the 18/4 build and its working great. Make sure u enabled all permissions for the dialer app.
qaliza said:
I'm still one the 18/4 build and its working great. Make sure u enabled all permissions for the dialer app.
Click to expand...
Click to collapse
They're all enabled, that was the first thing I checked. It's strange because it doesn't give an FC or anything, it just reboots.
Let me know if it happens to you when/if you flash the latest version.
Enviado do meu A0001 através de Tapatalk
Skeer_boy said:
They're all enabled, that was the first thing I checked. It's strange because it doesn't give an FC or anything, it just reboots.
Let me know if it happens to you when/if you flash the latest version.
Enviado do meu A0001 através de Tapatalk
Click to expand...
Click to collapse
Sure i will..
Skeer_boy said:
I've flashed your zip and I get a reboot every time I make a call. I'm using the latest sultan CM13.
Click to expand...
Click to collapse
I've had @qaliza's ZIP installed on the previous Sultan build and it worked great. As soon as I've flashed the 30/4 build it started rebooting, just as you've described. Had to remove the dialer and Truecaller service and flash the latest build again for the original dialer to work again.
Skeer_boy said:
I've flashed your zip and I get a reboot every time I make a call. I'm using the latest sultan CM13.
Click to expand...
Click to collapse
i had tried thay zip earlier,its basically just the capps from 12.1 for cm13 so fc on dialler,I had the same problem,other apps worked fine though
Skeer_boy said:
They're all enabled, that was the first thing I checked. It's strange because it doesn't give an FC or anything, it just reboots.
Let me know if it happens to you when/if you flash the latest version.
Enviado do meu A0001 através de Tapatalk
Click to expand...
Click to collapse
Skeer_boy said:
I've flashed your zip and I get a reboot every time I make a call. I'm using the latest sultan CM13.
Click to expand...
Click to collapse
alonroz said:
I've had @qaliza's ZIP installed on the previous Sultan build and it worked great. As soon as I've flashed the 30/4 build it started rebooting, just as you've described. Had to remove the dialer and Truecaller service and flash the latest build again for the original dialer to work again.
Click to expand...
Click to collapse
karantGoldstein said:
i had tried thay zip earlier,its basically just the capps from 12.1 for cm13 so fc on dialler,I had the same problem,other apps worked fine though
Click to expand...
Click to collapse
For Those who are facing Soft reboot while Making/Receiving calls using Truecaller(from the C-App zip mentioned above), make sure after giving permissions to "Phone" app you must select the default Telephone app from Settings > Apps > Cogwheel(Setting icon at the top right) > Default Apps > Phone app.
If Default Phone app is not selected the soft reboot will occur.