Related
I'm not sure where to put this, but, I was on g+ yesterday and found a link that allowed me to download the ICS Android Market.
It's nice, but, I updated to the newest nightly on CM and forgot to backup my apps, and now I can't download handcent haha
If there's any interest, hit me up with a message and I'll give you the link to download it.
Under the themes or apps section probably would have been a little more fitting.
CM7 nightly
Nice!
Sent From My HTC Incredibly Dinc
FYI Googles already pushing this to all phones.
Yes, this is a discussion thread, but you are not allowed to make "meaningless" posts in here.
If you have made some discoveries post it, but no one in here is interested in "thank you" posts or similiar.
Okay, let's try to get the Android 4.2 gapps working as good as possible on our phone.
As you know Google dropped support of non-neon phones and tablets with Android 4.2.
Our Tegra2 SoC doesn't support these neon instructions, which results in a couple problems with the default gapps package.
We need to replace a couple files with older ones to get everything back working.
Update 27.04: I finally found some time to work on gapps and provide a (hopefully) fully working non-neon gapps package in the second post now!
One example: the biggest annoyance is probably the dying keyboard.
This happens because the gapps package replaces the libjni_latinime.so file included in the ROMs with a proprietary one by Google to enable Gesture input.
Unfortunately it does need neon, so you should remove the file inside the gapps package (/system/lib/) before flashing it.
In the logcat you'll usually see a SIGILL error, like this one:
Code:
A/libc(3910): Fatal signal 4 (SIGILL) at 0x4f6233a6 (code=1), thread 3910 (putmethod.latin)
I/DEBUG(92): signal 4 (SIGILL), code 1 (ILL_ILLOPC), fault addr 4f6233a6
I'm starting this thread to colloborate together on a gapps package with as much stuff working as possible, so if you do have any insights please share them
You can download the CM10 gapps package and get the nonneon files (they're in /optional/nonneon) - but not all of them are still working with Android 4.2.
P.S.: For the love of God, don't call them fapps - fapps is a foss (free and open source) package which uses OpenStreetMaps instead of GMaps and so on.
We still want gapps, just without neon libs.
Okay, here's my non-neon fixed gapps package.
Important: If you already flashed another gapps package do format /system, reflash your ROM then reflash these gapps.
If you don't do that you'll have leftovers from the former package, which results e.g. in a dying keyboard.
Changes compared to the official package:
Fixed the aosp keyboard crashes
Fixed Google Talk videochat crashing
Fixed Faceunlock
Fixed Google TTS
Fixed Google Now & Voice Search crashes on non neon devices & restored hot-word detection
Fixed Talkback
Removed unuseful stuff
Notes:
Swipe keyboard won't work - nothing I can do about that.
Complain to Google for dropping non-neon support
Same thing goes to Photoshpere - no neon: no love.
Don't try to update Google Now - the new version doesn't properly work without neon (not sure if this still applies?)
Download:
http://goo.im/devs/tonyp/non-neon-gapps
If you're interested in more details what parts I changed - here you go.
This will hopefully ensure that future gapps versions will get provided as well
to fix facelock: replace libfacelock_jni.so with non-neon lib (credits: Adam77Root)
to fix the keyboard closing: remove libjni_latinime.so
to fix google videochat: added libvideochat_stabilize.so, replaced libgtalk_jni.so with non-neon lib and removed libgtalk_stabilize.so
to fix TTS: replaced libpatts_engine_jni_api.so with a non-neon lib and GoogleTTS.apk with the apk from the teameos gapps package.
to fix Google Now and Voice Search I replaced the QuickSearchBox.apk with this one by Steady Hawkin.
Note that the newest Google Now version isn't compatible with non neon devices anymore, thus this version disables the auto-update.
replaced Talkback.apk with a working version from the eos gapps package.
Partial credits for steps 1-4 go to bubor who already started with a non-neon gapps package.
Then I reflected these changes in the 70-gapps.sh backup script.
That's important because otherwise updating the ROM will break the gapps!
Why? Updating the ROM does wipe /system - only the files which are in the script will retain.
This means that e.g. the libvideochat_stabilize.so will poof away and the libjni_latinime.so won't get updates anymore.
Additionally I removed the g.prop file in /system/etc to prevent the GooManager from trying to update the gapps package if new (neon) updates come.
To reduce the package size I completely removed the photosphere stuff.
Just a thought here: since our cpu does not support neon instruction set, wouldn't it be an option to patch the P990's kernel with an neon-emulator? This way, the neon instructions will be translated into something the cpu can process. Corrrect me if I'm wrong.
I'm saying this because I've seen something similar happen on Mac OS X, where version 10.8.x requires a cpu capable of SSSE3 (not SSE3) instructions. They have patched the kernel with an SSSE3 emulator so that it works on older hardware and AMD cpus.
Sent from my LG-P990 using xda premium
Robin2 said:
Just a thought here: since our cpu does not support neon instruction set, wouldn't it be an option to patch the P990's kernel with an neon-emulator? This way, the neon instructions will be translated into something the cpu can process. Corrrect me if I'm wrong.
I'm saying this because I've seen something similar happen on Mac OS X, where version 10.8.x requires a cpu capable of SSSE3 (not SSE3) instructions. They have patched the kernel with an SSSE3 emulator so that it works on older hardware and AMD cpus.
Sent from my LG-P990 using xda premium
Click to expand...
Click to collapse
I'm thinking about the exact opposite - try to disassemble the libs, replace the neon instructions and reassemble. Not sure yet how much work it would take though...
bugadani said:
I'm thinking about the exact opposite - try to disassemble the libs, replace the neon instructions and reassemble. Not sure yet how much work it would take though...
Click to expand...
Click to collapse
this will be an horrendous work. I've seen some projects trying to hack armv6 instructions into the newer armv7 packages - it's really hard as you have to do it in smali as Google won't release it's sources.
I'm extremely full with loads of projects currently - I'm still hoping some people will take this over and try to build a nicely working non neon gapps version. this only requires trial and error, no real technical knowledge. but the interest seems low
Sent from my LG-P990 using xda app-developers app
Developer or not... But since you said yourself that "this will be an horrendous work", allow me include a little something here.
Changelog:
* All apps updated to 4.2.2 versions
* Google Play Store updated to 3.10.14
* Google Play Services updated to 3.0.25
* Gmail2.apk (Gmail) and GoogleEars.apk (Sound Search for Google Play) removed since they are available in the Google Play Store
** May require uninstalling and reinstalling Gmail and Sound Search after flashing.
* Keeps previous version's Photosphere/Picasa sync install on Mako, Manta, and Tuna.
Click to expand...
Click to collapse
From the way I see it, this horrendos work wouldn't really pay off since the earlier version of Gapps has... well... more or less everything the so-called new version has. So why bother if I may ask?
Back to you sir
Soooo, I have been looking into this for the past few days. I think I have got an understand of this that is good enough to make this work.
Since you are working so hard on CM10.1, I'll be willing to put great effort into this. Already started out with some basics, but I am pretty confident that I can make it work by the end of this week.
Will do some proper testing when it has been finished, once everything has been worked out, I'll push it public so you all can have the joy of using it in whatever way you may please
natalya said:
Soooo, I have been looking into this for the past few days. I think I have got an understand of this that is good enough to make this work.
Since you are working so hard on CM10.1, I'll be willing to put great effort into this. Already started out with some basics, but I am pretty confident that I can make it work by the end of this week.
Will do some proper testing when it has been finished, once everything has been worked out, I'll push it public so you all can have the joy of using it in whatever way you may please
Click to expand...
Click to collapse
Any news on your project?
Well, I'm a little disappointed that no one else worked on this - it's basically using Google and trial and error.
Thanks goes to massimo who has offered me some help and did some tests
Anyways, I decided to take matters into my own hands now, as I want to release CM10.1 over the weekend and don't want people to complain because they flashed the wrong gapps packages.
@natalya: If there's anything else you discovered which isn't working please provide it, but as you didn't post what you did in almost 2 weeks now I didn't want to wait anymore.
Changes compared to the official package:
Fixed the aosp keyboard crashes
(note: swipe won't work on non neon devices, nothing I can do about that)
Fixed Google Talk videochat crashing
Fixed Faceunlock
Fixed Google Now & Voice Search crashes on non neon devices & restored hot-word detection
Fixed Talkback
Removed unuseful stuff
Let me explain the steps taken so others can learn what has been done and can update gapps theirselves.
to fix facelock: I replace libfacelock_jni.so with non-neon lib (credits: Adam77Root)
to fix the keyboard closing: I removed libjni_latinime.so
(note: this diables the keyboard swiping - it will never fully work on non-neon devices!)
to fix google videochat: added libvideochat_stabilize.so, replaced libgtalk_jni.so with non-neon lib and removed libgtalk_stabilize.so
to (partially) fix TTS: replaced libpatts_engine_jni_api.so with a non-neon lib
to fix Google Now and Voice Search I replaced the QuickSearchBox.apk and added the libgoogle_recognizer_jni_l.so lib from this one by Steady Hawkin.
Note that the newest Google Now version isn't compatible with non neon devices anymore, so this one disables the auto-update
replaced Talkback.apk with a working version from the above gapps package[/url].
Note the English TTS not working, see below.
Partial credits for steps 1-4 go to bubor who already started with a non-neon gapps package.
Then I reflected these changes in the 70-gapps.sh backup script.
That's important because otherwise updating the ROM will break the gapps!
Why? Updating the ROM does wipe /system - only the files which are in the script will retain.
This means that e.g. the libvideochat_stabilize.so will poof away and the libjni_latinime.so won't get updates anymore.
Additionally I removed the g.prop file in /system/etc to prevent the GooManager from trying to update the gapps package if new (neon) updates come.
To reduce the package size I completely removed the photosphere stuff.
As for the swipe keyboard this feature requires neon-support and will not work properly on our phone, no matter what.
Known bugs:
Google text to speech doesn't seem to work in English. fixed
Download:
http://goo.im/devs/tonyp/non-neon-gapps
If you already flashed another gapps package do format /system, reflash your ROM then reflash these gapps.
This is needed to ensure nothing remains broken from former flashes.
Please give some feedback for this gapps package.
If something doesn't work don't forget to attach a logcat
Okay, I managed to fix the Google-text-to-speech engine as well by replacing the GoogleTTS.apk with the one from the teameos gapps package.
I pushed the new version online and removed the old one.
All bugs I am aware of are now fixed, if you notice anything else that isn't working please give feedback
Time to clean up the OP.
tonyp said:
[*]Don't try to update Google Now - the new version doesn't properly work without neon.
Click to expand...
Click to collapse
Play store is offering me to update Google Search after installing your CM10.1 ROM and this gapps package. Is Google Now part of Google Search so I should avoid this update too?
ciarpame said:
Play store is offering me to update Google Search after installing your CM10.1 ROM and this gapps package. Is Google Now part of Google Search so I should avoid this update too?
Click to expand...
Click to collapse
You can update it and you can use it.
Sadly it has huge lags (as in it freezes from time to time and the waiting times can be taking forever sometimes)
Sent from my LG-P990 using xda app-developers app
For those who want to use the aosp-keyboard, Google recently released Google-keyboard (witch is similar to the aosp, but fully non-neon compatible)
In the US it should be available through the play store, for the others http://dl.androidnext.de/com.google.android.inputmethod.latin.apk
our 2x learns gesture typing
Thread cleaned up.
This is the dev discussion subforum so it's not the right place to ask about specific ROMs.
If you'll find out something new for the non-neon gapps package then you can post in here, everything else goes into the other sections.
Thank you!
P.S.: I've tried extracted the new lib (libjni_unbundled_latinimegoogle.so) from the Google keyboard - it's not compatible to the AOSP one included in ROMs.
If you want to include it into the gapps package you need to rename the apk to LatinIME.apk and add the lib, then it'll overwrite the AOSP keyboard.
(I'm too lazy to update the gapps package in here for a keyboard you can simply install).
I created a non-neon gapps package with the keyboard included.
It will replace the AOSP keyboard by the very similar google keyboard (that fixes gesture typing). Everything else is like tonyps-non-neon-gapps.
Download gapps-jb-20130427-nonneon-tonyp-keyboard.zip
All credits to Google, tonyp and the others mentiont in the first post.
Have fun!
P.S. @tonyp if you want you can put it on the gooserver to the other gapps.
Latest Google Now (26/06/2013) seems to work just fine. I'm not getting those crazy UI lags I got before, if I updated Google Now from the play store
Since the files from tonyp on goo.im are down, here is the working downloadlink for non-neon Gapps:
http://tonyp.basketbuild.com/downlo...on-gapps-/gapps-jb-20130427-nonneon-tonyp.zip
New google keyboard is available: link
DJNoXD said:
New google keyboard is available: link
Click to expand...
Click to collapse
Ah good that you're reviving this thread, I've been meaning to update it with some information.
I never intended to maintain a gapps package and won't do so.
So if someone wants to follow my instructions and offer updated neon-compatible packages for 4.3 and 4.4 go ahead.
The instructions should still apply, but things may have changed a little in the newer versions so they might needs some adaption (e.g. the Talk to Hangouts transition).
Personally I include a mini/tiny gapps neon compatible package in all my ROMs which only contains the most important apps.
I've created the package quite some time ago, it is fully open sourced and can (and already is) used by everyone.
https://github.com/tonyp/android_vendor_google
I update the repo on my own accord, if someone needs a faster update pull requests are always welcome.
But gapps are capable of updating theirselves via the play store, so this usually isn't needed anyways.
I would prefer if others are using my repo and sent pull requests instead of forking and forgetting about the origin, but that's of course your choice.
To include the gapps into your own build you have to add the repo to your manifest and add the following lines to a makefile.
(it doesn't matter which one as long as it's called - an obvious choice would be somewhere in the device tree):
Code:
MINI_GAPPS := true
$(call inherit-product, vendor/google/tiny_gapps_nonneon_tonyp.mk)
P.S.: @DJNoXD This isn't directed at you, I know you're already using my gapps repo in your roms, just a headsup for other potential devs.
tonyp said:
Ah good that you're reviving this thread, I've been meaning to update it with some information.
I never intended to maintain a gapps package and won't do so.
So if someone wants to follow my instructions and offer updated neon-compatible packages for 4.3 and 4.4 go ahead.
The instructions should still apply, but things may have changed a little in the newer versions so they might needs some adaption (e.g. the Talk to Hangouts transition).
Click to expand...
Click to collapse
Hi @tonyp, I hope it's ok to revive this thread again resp. to hijack it a bit from your original intention!? Even if the origin of my following NEON related questions is founded in my lag problems with CM11 2014/11/13 build by @gucky01
gucky01 said:
http://sourceforge.net/projects/lgo...m-11-20141113-UNOFFICIAL-p990.m1.zip/download
Here we go, guys! As promised, here the first build. It`s 100% Tonys work. So we have to thank him for his great work!
All the best to you!
Click to expand...
Click to collapse
I find they fit this thread much better than any other CM10.x/CM11/CM12 ROM XDA thread. Not just one but all of those ROMs are affected by the missing NEON instruction set of the Tegra 2 SOC.
How can one prove wether a current ROM does not call any NEON instructions? Is it sufficient to see that there are no SIGILL entries in the logs?
Let's assume a dev releases a ROM that initially does not call any NEON instructions. Is it possible that updates of Google apps introduce calls of NEON instructions making the ROM misfunctional/unusable?
AFAI understood your trick to assemble non-NEON gapps is to replace shared opjects ( .so files) that call NEON instructions by their (more or less) equivalent non-NEON shared objects. Could there be Google apps or third party apps that call NEON instructions in their core binary?
If so, our P990 will not able to run them, right? I'd like to assemble a list of apps that won't run without NEON support (is there still any list?).
Do calls of NEON instructions on systems that don't support NEON always result in FCs, hot re-boots, or BSODs? Other way round: can calls of NEON instructions on systems that don't support NEON also result in lag or even heavy lag? (gmail 5.0.1 uses to take 10 seconds to start in my recently installed CM11 after the cleanest install possible; I just left the BB and system data/cal un-touched).
I am looking forward for your reply, well-knowing that you don't use the P990 as your daily driver any more for a long time now.
I wish you all a good 2015!
Can anyone update xposed to work with the new security fixes applied to newer android 4.4.4 builds ?
New fix: Install the apk file found here:
Http://forum.xda-developers.com/showpost.php?p=64063168&postcount=62
edit: old fix:
read the attachment txt file and copy two files from an older build for your device to those folders (/system/lib & (/system/bin)
http://forum.xda-developers.com/showpost.php?p=63864337&postcount=35
@rovo89 : can you update it please?
robuser007 said:
Can anyone update xposed for the new security fixes found in newer android 4.4.4 builds ?
Click to expand...
Click to collapse
Black_Focus_X said:
@rovo89 : can you update it please?
Click to expand...
Click to collapse
What devices and ROMs are you using that have these problems, and what is in the error logs and logcat?
Without this information, no one can help you, not even rovo89 himself.
Also, have you searched the forum to see if others have this issue and what's been learned about it?
It's Samsung Galaxy S3 with Cyanogenmod 11 official! I searched the forum but couldn't find an answer. Maybe my english isn't good enough
My device is Motorola RAZR XT910, with a TI OMAP4 ARMv7-A SoC.
Right now, I am on an Unofficial CyanogenMod 11 (Android 4.4.4) ROM which contains the latest security fixes for the Stagefright vulnerability and was built on November 15. When I try to install Xposed framework, using the latest official stable installer from Xposed Repo, I get an the following error: "Xposed is not (yet) compatible with Android SDK version 19 or your processor architecture (armeabi-v7a)".
When I was on the latest Official CyanogenMod 11 ROM for my device, that was built back on September 1st, Xposed would install and work properly on it, withour any troubles / warnings / errors. Now, I just want to use the latest build that has me protected against Stagefright but I can not install Xposed framework on it at all.
@rovo89 Is there / will there be any fix for this issue?
Having the same problem with the latest build of CM11 (2015.11.15).
unknownsoldierx said:
Having the same problem with the latest build of CM11 (2015.11.15).
Click to expand...
Click to collapse
Same on XT910 on 15.11 CM11 build!
from XT910 or XT925 using Tapatalk
me 2
samsung n5120, just update the new cm11 then show the error message
Yes, i got the same error message when I updated my Redmi 1S to the newest CM11.
I tried to search in MIUI forum but the answer only for MIUI OS.
I tried the patch for my Redmi 1S, it gave me bootloop.
Are there any explanation for this?
Thanks
Same issue here...Redmi 1s..CM 11 4.4.4 ...xposed not working...any solution ??
FYI, I believe this commit is causing the problems:
http://review.cyanogenmod.org/#/c/118800/
Replacing /system/bin/app_process and /system/lib/libandroid_runtime.so from previous CM builds will allow the framework to be installed without problems.
Ok, i'll try
But it can't be a right solution
Well, of course it's meant to be a temporary workaround, until (hopefully) rovo89 will have the time to fix this, if possible. If you heavily rely on Xposed it's better than nothing.
With the link to the commit, I just wanted to help to point out where the problem comes from in order to maybe get a permanent solution.
derf elot said:
Well, of course it's meant to be a temporary workaround, until (hopefully) rovo89 will have the time to fix this, if possible. If you heavily rely on Xposed it's better than nothing.
With the link to the commit, I just wanted to help to point out where the problem comes from in order to maybe get a permanent solution.
Click to expand...
Click to collapse
rovo it's not going to fix anything on kk, it's been done, too old. He's working on M and somewhat supporting L, so no luck with older builds.
Thank you. I tried it and. Yes it works. Xposed working
---------- Post added at 16:36 ---------- Previous post was at 16:34 ----------
ldeveraux said:
rovo it's not going to fix anything on kk, it's been done, too old. He's working on M and somewhat supporting L, so no luck with older builds.
Click to expand...
Click to collapse
Can you look into his head or what?
LG Optimus 4X HD Nightly 15112015 Xposed not working.
View attachment 3544451
Sorry about the pic being in spanish but is my girlfriend phone and i was giving her instructions via skype. It says "Xposed is not (yet) compatible with Android SDK version 19 or your processor architecture (armeabi-v7a)".
derf elot said:
FYI, I believe this commit is causing the problems:
http://review.cyanogenmod.org/#/c/118800/
Replacing /system/bin/app_process and /system/lib/libandroid_runtime.so from previous CM builds will allow the framework to be installed without problems.
Click to expand...
Click to collapse
Can someone make an update.zip for recovery ?
Feel free to try the zip I posted here. Make a backup first. Normally re-flashing your ROM should solve any issues, but you never know.
Xposed dead in latest CM11 *Unofficial* rom
Same thing with cm11 latest release with security patches for stage fright. Although the rom is listed as "Unofficial", it comes from THE Official cm11 OMAP 4 developer. Only listed unofficial because CM has not caught up with the developer. Xposed Framework does not work anymore on Android 4.4.4 See attached screenshots.
Ohmster said:
Same thing with cm11 latest release with security patches for stage fright. Although the rom is listed as "Unofficial", it comes from THE Official cm11 OMAP 4 developer. Only listed unofficial because CM has not caught up with the developer. Xposed Framework does not work anymore on Android 4.4.4 See attached screenshots.
Click to expand...
Click to collapse
You just posted what some other guys posted before you...
And if you would read the thread then you would know there is an update.zip for this problem! With this, Xposed is working without problems!
Google Dialer v37 & Contacts v3.7.7 on Stock ROMs (any ROM really) August 1st, 2019
I maintained a simple little project on the V20 forum that added Google's Pixel Dialer app and Google Contacts to (any device, really) my V20, and I thought it might be a good idea to post in here about it too, since I am now on a LS998 V30+
Link to the thread in V20's apps section HERE
These zips should work on any android running nougat and above, but I will only support the V30 for sure, since thats what I have.
Installing this will not remove anything you already have on your phone, it will only add google's dialer app and framework as a second phone app.
as always, my latest updates and newest files can be found in this shared Google Drive folder
This link has been changed, the correct one is above. I had (wanted) to move this project to a separate dedicated account that was not so personal. Reshare the folder to yourself using Google Drive and/or update your bookmark.
August 1st, 2019
- updated both apps to latest version of each as supplied by Google, app versions are below...
arm64 zips
Phone-com.google.android.dialer-(arm64)-33.0.247985459-publicbeta-3998624.apk
Contacts-com.google.android.contacts-3.5.51.247103087-2209215.apk
OLD Changelog:
August 1st, 2019
- updated both apps to latest version of each as supplied by Google, app versions are below...
- updated all the framework files to match the ones in the latest release from opengapps
- removed LGInCallUI app as it is not completely necessary in this particular project
arm64 zips
Phone-com.google.android.dialer-37.0.260231449-publicbeta-4339080.apk
Contacts-com.google.android.contacts-3.7.7.260733580-2243311.apk
April 25th, 2019
- updated both apps to latest version of each as supplied by Google, app versions are below...
arm64 zips
Phone-com.google.android.dialer-31.0.241960258-publicbeta-3785841.apk
Contacts-com.google.android.contacts-3.5.7.243634183-2209036.apk
arm(32) zips
Phone-com.google.android.dialer-31.0.241960258-publicbeta-3785840.apk
Contacts-com.google.android.contacts-3.5.7.243634183-2209035.apk
All files can be found and downloaded from my shared Google folder (above) or attached to this post (below).
March 27th, 2019
- updated both apps to latest version of each as supplied by Google, app versions are below...
arm64 zips
Phone-com.google.android.dialer-31.0.240233734-publicbeta.apk
Contacts-com.google.android.contacts-3.4.6.234021015-2191599.apk
arm(32) zips
Phone-com.google.android.dialer-31.0.240233734-publicbeta-3785464.apk
Contacts-com.google.android.contacts-3.4.6.234021015-2191598.apk
February 22nd, 2019
- updated both apps to latest version of each as supplied by Google. App versions are below...
arm64 zips
Phone-com.google.android.dialer-29.0.234661434-publicbeta-3570857.apk
Contacts-com.google.android.contacts-3.4.6.234021015-2191599.apk
arm(32) zips
Phone-com.google.android.dialer-29.0.234661434-publicbeta-3570850.apk
Contacts-com.google.android.contacts-3.4.6.234021015-2191598.apk
questions or comments? leave a reply here and I will see it. I don't visit here often but I should get back to you either immediately or within 2-3 weeks.
~syndre
- I don't think it's necessary, but by request (and to avoid confusion) I have made a Android 9.0+ PIE compatible flashable zip to install just the dialer's framework.
January 22nd, 2019
- Updated apks to latest versions from Google
Phone-com.google.android.dialer-28.0.229824408-publicbeta-3464836.apk
Contacts-com.google.android.contacts-3.3.3.226019458-2171201.apk
-I uninstalled any updates to the phone and contacts app I had installed, and flashed the non-magisk version on to my V30+, both apps are working fine.
-I copied those files into the magisk template I've been using and zipped that to create a magisk installable version. I have not tested this one but I assume it will work for those who use it.
- expect arm versions within the next week.
downloads are attached below, to this post.
December 20th, 2018
I am still not sure why it was happening, but the Phone app started randomly force closing on me a few days ago. I do a lot of playing around with mods and stuff so it could just be me. I have updated and tested both of the zips being released today, and the app is working again for me. I use a stock Oreo LG ROM. Everyone who hasn't had this issue or if you're on another device or on AOSP, ignore this paragraph. Theres a few files different in here from the previous version, so please flash this update so I know we're all on the same page. ty
- Updated dialer to latest apk from Google: v27.0.225573798-publicbeta-3347328.apk
- Updated/changed a couple framework related files to get the app to stop force closing on my device.
- arm (32) versions made and posted, too. Make sure you use the correct zip for your device!
New files can be found attached onto this post below and/or in the drive folder linked to above.
November 26th, 2018
updated phone to today's release from google
These are a little different from the previous (Nov 26) version, if you experience any issues at all please let me know!
attached below, and also available HERE
November 26th, 2018
updated arm64 apk's
arm update soon
flashable zips are attached below
November 15th, 2018
seems like they always put one out after I post... v26 is supposed to officially have dark mode in the dialer app (now both phone and contacts).
attached below
November 13th, 2018
my last post in this thread
Updated APK's to versions:
Phone-com.google.android.dialer-25.0.220310144-3118535.apk
Contacts-com.google.android.contacts-3.2.4.220343473-2161331.apk
both regular and magisk flashable zips are attached to this OP.
You can also find everything related to this project here in this shared drive folder.
New Favorites Section and Dark Mode on display in this Screenshot Album...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Above is still not Google official, but easy to manipulate. See thread started by @JonnyTrulove HERE!
October 27th, 2018
Updated arm64 APKs to Google's newest version of each, both released today:
Phone-com.google.android.dialer-25.0.218361296-3118167.apk
Contacts-com.google.android.contacts-3.1.6.218196352-2149637.apk
I'll upload zips with version 25 for arm devices soon. I'm literally on my phone, typing this from a pitch dark cabin in the woods in the Midwest U.S. with someone sleeping a foot away from me.
Download arm64 zip to flash directly to system, also attached below OP
Download arm64 zip packaged as a magisk module, instead, also attached below OP
LINK CHANGED/UPDATED
Link to my NEW shared drive folder.
October 8th, 2018
arm64 versions with new contacts v3.1.3 update
arm64 version with new contacts v3.1.3 update -Magisk Module
I built these and edited this top post totally on mobile, I hope it works..
I'll fix[/IMG] the rest later
it has just come to my attention that some people (on other devices) are having problems because I never switched over to the 2018 dialer framework in these zips. Both versions have always been there, I just had it named in such a way that the 7.0 version wax being used.
I have changed it over to the newer Oreo 8.0 framework, and will use that from today onwards.
Any issues because of this on LG phones? Please leave a response about it.
download 8.0 framework below, or here
October 3rd, 2018
Updated all apk's involved, and put together an arm version so I could use it on my older arm devices.
arm64 version for V30 and newer phones, magisk'd
arm64 version that writes directly to /system partition
arm version for your older phones , magisk'd
arm version that writes directly to /system partition
I have also attached the same 4 zips to this top post. They must have raised the file size limit recently or something ¯\_(ツ)_/¯
September 28th, 2018
Updated APK's to Phone v24 and Contacts v3.0.7
regular /system flashable zip HERE
NEW
Magisk Module I put together HERE
After flashing onto your device, you will have to manually enable all the permissions for each app.
Also you'll need to change the default phone app in your settings.
As far as I can tell, everything in the phone app works (caller ID, spam filter, nearby places)
Unless you use google voice, you will still need to have your carrier's voicemail app installed to use Visual Voicemail.
using either of these methods will allow you to download updates from the play store, so you will not need to wait for me post an update to have the latest versions of both phone and contacts.
I don't expect any problems on your device, as this zip is fairly simple and straightforward. If any bugs do show up, though, I will work with V30 users. I make these zip files for my own personal use. I am sharing them because you might want them too!
Lastly, I often will upload newer versions to a folder on google drive without updating this top post every single time.
You can access that HERE, and share it to yourself or whatever. I'm just trying to make it easiest on myself and anyone interested in following the project.
unattached file DL count -
arm64:3640 | arm64-magisk: 1332 | arm:398 | arm-magisk: 436
syndre said:
I maintained a simple little project on the V20 forum that added Google's Pixel Dialer app and Google Contacts to (any device, really) my V20, and I thought it might be a good idea to post in here about it too, since I am now on a LS998 V30+
These zips should work on any android running nougat and above, but I will only support the V30 for sure, since thats what I have.
Link to the thread in V20's apps section HERE
September 28th, 2018
Updated APK's to Phone v24 and Contacts v3.0.7
regular /system flashable zip HERE
NEW
Magisk Module I put together HERE
After flashing onto your device, you will have to manually enable all the permissions for each app.
Also you'll need to change the default phone app in your settings.
As far as I can tell, everything in the phone app works (caller ID, spam filter, nearby places)
Unless you use google voice, you will still need to have your carrier's voicemail app installed to use Visual Voicemail.
using either of these methods will allow you to download updates from the play store, so you will not need to wait for me post an update to have the latest versions of both phone and contacts.
I don't expect any problems on your device, as this zip is fairly simple and straightforward. If any bugs do show up, though, I will work with V30 users. I make these zip files for my own personal use. I am sharing them because you might want them too!
Lastly, I often will upload newer versions to a folder on google drive without updating this top post every single time.
You can access that HERE, and share it to yourself or whatever. I'm just trying to make it easiest on myself and anyone interested in following the project.
Thanks
Click to expand...
Click to collapse
You don't need to move contacts to the system. Just the phone app.
TotallyAnxious said:
You don't need to move contacts to the system. Just the phone app.
Click to expand...
Click to collapse
Ok, and?
I like it in /system, where it won't get accidentally removed.
I assume since you took the time to comment that you think its better installed as a user app for some reason.. I'm curious now, what is/are those reasons?
Putting apps like that on the system partition makes no difference in functionality, and saves space it would otherwise be taking up on /data...
Your stock contacts app comes out of the box on /system, most if not all gapps packages put contacts onto /system.
There are many, many apps that will work on either system or installed as a user app.
I put it there because I like it there. phone and contacts in my installer come together as one package. There's no reason to not keep it simple and put both apps in the same destination.
Thanks for commenting, I guess... but I don't know why you are telling me something I'm well aware of.
Once you have the framework and permission files on the system partition for the phone app, you can sideload that APK too onto /data, if that's what you prefer.
I don't plan on changing anything, and look forward to later in the day when I'll hopefully forget about being confused about why you needed to mention this, especially with zero context.
Sent from my LGE V30+ using XDA Labs
I used this on my phone - I previously had Contacts from the Play Store and a modified copy of Phone from Martin.077 (I was using version 20). Anyway I wanted to mention with this version, the visual voicemail feature built into the Phone app is working for me with a retail US998+ on Verizon, and this is mostly stock firmware. I say mostly stock because I have the Verizon modem flashed - signal strength at my home doesn't seem as good with the V30 as it was with my Droid Turbo, so I've been experimenting.
If I install and use Magisk module, does disabling the module let me use original dialer?
nvm, installed Magisk module. Working great. Thanks!
tagor said:
If I install and use Magisk module, does disabling the module let me use original dialer?
nvm, installed Magisk module. Working great. Thanks!
Click to expand...
Click to collapse
Installing any of my zips from this thread will not do anything to your stock dialer app (as far as I know).
You will have to go into the phone settings and switch which one you want set as the default.
To use stuff in the google one, you must set google phone as default.
If you ever need to update your PRL or anything like that, you will have to switch it back to the LG contacts app, or else the dialer "secret codes" wont do anything.
I should have mentioned that in the OP..
Installing this will not remove anything you already have on your phone, it will only add google's dialer app and framework as a second phone app.
hitokage004 said:
Anyway I wanted to mention with this version, the visual voicemail feature built into the Phone app is working for me
Click to expand...
Click to collapse
Replying to myself to indicate this apparently isn't correct (based on info from another thread). I didn't know when people referred to visual voicemail, they were referring to the text transcription stuff. I have a Google voice number that isn't really used, but I've seen the transcriptions on the website from people who misdialed and left a message - I wasn't particularly impressed and had to listen anyway.
It was mentioned that there is configuration files that will make it work though, so what I said is partly correct - as the voicemail tab shows in the Google dialer when using this version. The modified version I used before didn't have that tab.
EDIT - See below.
ChazzMatt said:
Visual Voicemail is not transcription. Visual Voicemail is merely a list of voice messages so you can pick and choose the order you wish to listen or even delete without listening. It MAY also include voicemail-to-text transcription, but that is not the purpose of the visual voicemail definition. Early visual voicemail applications (from when the name came) did not have voicemail-to-text transcription and was called that because you could SEE the list of messages on a video interface.
https://www.lifewire.com/what-is-visual-voicemail-3426762
https://en.wikipedia.org/wiki/Visual_voicemail
__________
If they were referring only to voicemail-to-text transcription, they are wrong. That can be INCLUDED in a "Visual Voicemail" service, but is not what visual voicemail means.
Google Voice does have "visual voicemail" (list of messages on the website) as well as having voicemail-to-text transcription (website, text, and email). Both my wife and I have Google Voice numbers and I appreciate both the text and email transcriptions I receive.
Click to expand...
Click to collapse
:good:
Working on one plus 6 with magisik module. Posting your work in one plus forum.
saxena1 said:
Working on one plus 6 with magisik module. Posting your work in one plus forum.
Click to expand...
Click to collapse
thats fine just please don't forget to mention where you got it from
syndre said:
thats fine just please don't forget to mention where you got it from
Click to expand...
Click to collapse
Already mentioned you name
please update your post regularly ?
saxena1 said:
Already mentioned you name
please update your post regularly
Click to expand...
Click to collapse
I just finished one
there's new framework file being used now. I never had problems with the nougat version, but some on the V20 board have been having issues, so I switched the file in the zip to the newer one.
I suspect these LG phones work fine on stock ROMs (my original intention) with the nougat framework ive been using all along, and that other devices are the ones not working properly without the updated Oreo framework.
I don't really have any way to test on phones I don't own, so I'll have to rely on you guys for help. I've included both Nougat and Oreo frameworks now attached to the top post. All the zips dated October 8th have the newer 8.0 framework
syndre said:
I just finished one
there's new framework file being used now. I never had problems with the nougat version, but some on the V20 board have been having issues, so I switched the file in the zip to the newer one.
I suspect these LG phones work fine on stock ROMs (my original intention) with the nougat framework ive been using all along, and that other devices are the ones not working properly without the updated Oreo framework.
I don't really have any way to test on phones I don't own, so I'll have to rely on you guys for help. I've included both Nougat and Oreo frameworks now attached to the top post. All the zips dated October 8th have the newer 8.0 framework
Click to expand...
Click to collapse
How do I get VM to show up in the Google dialer?
I have my stock T-Mobile VM app installed.
Sent from my LG-H932 using XDA Labs
Contacts installed fine, but not the dialer. I get "App not installed". Anyone know how to fix this?
This may be a silly question, but is there an APK version of this that I can install without TWRP. My v30 isn't rooted and I've done that in the past with my Google phones but I'd be a little nervous to do it with this one in case I bricked it.
nobdow said:
This may be a silly question, but is there an APK version of this that I can install without TWRP. My v30 isn't rooted and I've done that in the past with my Google phones but I'd be a little nervous to do it with this one in case I bricked it.
Click to expand...
Click to collapse
This doesnt need root or TWRP. Just download and run the apk.
You don't need root? I've got no where to put the zips (but I don't have root)
The APK for contacts installs but phone does not install on my v30 h933 - the package installer sometimes doesn't even give an error and other times it just says "not installed".
I can't get the apk to install either.
Sent from my LG-H931 using Tapatalk
Yeah, can't get it to stick on a stock 932.
You can use this without root, but the bootloader must be unlocked and TWRP installed. Unlocking the bootloader and installing TWRP doesn't require you to install a root app like Magisk.
For those who want to use the Google Dialer (aka Phone) without unlocking the bootloader - I used Martin.077's patched copy previously. With that version though, you'll have to wait for them to update it - it can't use the updates from Google in the Play Store. Google Contacts will install and update from the Google Play Store without any modifications.
If you have Beta 1.5 and/or 1, and can upload it and provide me with a link, I would much appreciate it.
Rooted Beta 2 is problematic--Play Store won't update apps, some apps not starting properly, permission issues, etc. I am hoping I can dirty flash to 1.5.
Thanks.