Related
My wife gave me a Fitbit for Christmas (Apparently, she wants me to get off my butt more and move around!)
The Fitbit is a small wearable device that measures your activity level, etc. The Fitbit app uses Bluetooth 4.0 to sync with the device. The sync function is working with my Samsung Galaxy S3 phone, which is setup with a custom ROM. The app does not sync on the G Pad using stock firmware.
According to the specs I see, the G Pad is supposed to have support for BT 4.0. I don't have any other devices that use it.
Does anybody here have a Fitbit device? I'm curious to know if anybody has tried to sync one on a G Pad with different firmware. Or on a GPE device. It might be that it would work on a 4.3 or 4.4 ROM.
I have a GPE and the app syncs fine with my Flex. I did, however, participate in the Fitbit beta program when they were testing for devices other than the Galaxy series (namely Nexus and Motorola devices with BT 4.0). My Fitbit app is version 1.8.4 if that helps. Here's the link to the beta program: https://docs.google.com/forms/d/1ZVjMd9JsDyo45g7uUV60clx7D780ouDka-wgNwvqxmA/viewform
Yes, I was playing with my new fitbit all day yesterday and unless you have one of their devices that is currently known to be compatible you have to be signed up for the Beta program. I am currently running android 4.4 with the cyanogenmod.
I signed up for the Beta by joining the google group here: https://groups.google.com/forum/#!forum/fitbit-android-sync-beta
Which allows you to go to: https://play.google.com/apps/testing/com.fitbit.FitbitMobile
Where you click become a tester. You then need to uninstall the fitbit app, clear the cache for the google play store (I used Clean Master to do this), and reinstall the fitbit app. You will now have the beta version of the app and when you login it will automatically find and start syncing to your fitbit. Note that by default the background syncing is turned off. If you want to be able to do this you have to enable it under devices.
Indeed LG gpad Hardware supports bt4. You need 4.3+ Android for bt4. I tried it with cm and it works.
If you want stock experience, then you have to wait for the Kitkat release.
Forgot to add : I tried it with a polar h7 bt4 heart rate monitor. Works great.
Not necessarily true regarding needing 4.3. They do support the LG G2 which is still on 4.2 stock. Im using it with mine and it syncs fine to the G2. I've never tried syncing to my G Pad tho
chadderbox said:
Not necessarily true regarding needing 4.3. They do support the LG G2 which is still on 4.2 stock. Im using it with mine and it syncs fine to the G2. I've never tried syncing to my G Pad tho
Click to expand...
Click to collapse
Good to know. I might check the fitbit after all.
Unfortunately the polar h7 doesn't want to pair with my Stock LG g2. It is after 4.3 that Android provides platform support to bt4. The solution that LG and Samsung used in the lower api levels apparently doesn't pay nice with all hardware.
http://developer.android.com/guide/topics/connectivity/bluetooth-le.html
Sent from my LG-V500 using Tapatalk 4
chadderbox said:
Not necessarily true regarding needing 4.3. They do support the LG G2 which is still on 4.2 stock. Im using it with mine and it syncs fine to the G2. I've never tried syncing to my G Pad tho
Click to expand...
Click to collapse
Correct. The Fitbit app syncs on my Galaxy S3, which is using a custom rom running Android 4.1.2. That version doesn't support Bluetooth 4.0., so I think they must have it working with Bluetooth 3 on some devices.
woody1 said:
Correct. The Fitbit app syncs on my Galaxy S3, which is using a custom rom ruining Android 4.1.2. That version doesn't support Bluetooth 4.0., so I think they must have it working with Bluetooth 3 on some devices.
Click to expand...
Click to collapse
I have an LG Lucid 2 running 4.1.2 on a custom rom and while the tech specs say it has bluetooth 4.0 I can't get it to sync. It doesn't even look like the beta version is installing at all but I don't know how to tell for sure.
colwellkr said:
I have an LG Lucid 2 running 4.1.2 on a custom rom and while the tech specs say it has bluetooth 4.0 I can't get it to sync. It doesn't even look like the beta version is installing at all but I don't know how to tell for sure.
Click to expand...
Click to collapse
Looks to me like the app checks to see what device it's installed on and the sync features are only enabled for certain devices. On the G Pad, I can check my my dashboard, etc., but I can't sync or interact with the tracker. On the S3, the app lets me sync and do other things.
I've no way of trying this myself but to you guys who say that you should have support for BT4.0, you could try and trick the device that will not sync. Go into the build.prop and take the ro buildnumber and name and so on and change them to the same of a device that you are certain it works with. If the the Fitbit is checking up against a buildnumber or model number, chances are it's from the build.prop. And could be funny if you could actually trick it just by making your phone into something else. ^^ (That is if BT4 is supported as said.)
CuraeL said:
I've no way of trying this myself but to you guys who say that you should have support for BT4.0, you could try and trick the device that will not sync. Go into the build.prop and take the ro buildnumber and name and so on and change them to the same of a device that you are certain it works with. If the the Fitbit is checking up against a buildnumber or model number, chances are it's from the build.prop. And could be funny if you could actually trick it just by making your phone into something else. ^^ (That is if BT4 is supported as said.)
Click to expand...
Click to collapse
That's a really good idea. I have double and triple checked the specs for my phone and it does say Bluetooth 4.0. I think I'll try this since it worked for me tricking QPair into thinking my gpad was a v510. Thanks!
colwellkr said:
That's a really good idea. I have double and triple checked the specs for my phone and it does say Bluetooth 4.0. I think I'll try this since it worked for me tricking QPair into thinking my gpad was a v510. Thanks!
Click to expand...
Click to collapse
Don't thank me yet. ^^ Fingers crossed.
CuraeL said:
Don't thank me yet. ^^ Fingers crossed.
Click to expand...
Click to collapse
Hmm, trying to edit build.prop on my phone does not seem to be working. Neither ES File Explorer, nor 920 Text Editor, are able to edit/rename/save anything to build.prop or in /system. It says is a read only file system.
colwellkr said:
Hmm, trying to edit build.prop on my phone does not seem to be working. Neither ES File Explorer, nor 920 Text Editor, are able to edit/rename/save anything to build.prop or in /system. It says is a read only file system.
Click to expand...
Click to collapse
Ah, rule number one of flashing KitKat: When done go to play store and get supersu, run it and let it update the binary. Choose normal, not CWM\TWPR. Let it finish the install, takes10 secs or so. Restart and tadaa root. It has to be done on all devices for now. Go into supersu after reboot and find Settings and then untick "Respect CM superuser bleh bleh."
Good luck.
CuraeL said:
Ah, rule number one of flashing KitKat: When done go to play store and get supersu, run it and let it update the binary. Choose normal, not CWM\TWPR. Let it finish the install, takes10 secs or so. Restart and tadaa root. It has to be done on all devices for now. Go into supersu after reboot and find Settings and then untick "Respect CM superuser bleh bleh."
Good luck.
Click to expand...
Click to collapse
My phone is running a custom 4.1.2 Rom called Lucidian. Would this still apply to that? I have superuser already working on it. And on my gpad running 4.4.2 cm11 I didn't have to do that to get root.
colwellkr said:
My phone is running a custom 4.1.2 Rom called Lucidian. Would this still apply to that? I have superuser already working on it. And on my gpad running 4.4.2 cm11 I didn't have to do that to get root.
Click to expand...
Click to collapse
And you have tried build.prop and it worked on your G Pad with CM 11? Funny, I had to do it on two different devices and just assumed I would have to on the G Pad as well. Now 4.1 i don't recall had any root issues, beats me why you can't edit the system on that one. Anyways, sounds like an incomplete root, like what happened in ICS 4.0 on the first Galaxy Note. Gave root but didn't do it for the full system..
Now with Nougat Support!
Shout to Rovo89 for the Xposed Framework, and the various people who inspired this.
Sensor Disabler (previously known as Disable Proximity) is an Xposed application that allows you to disable or modify most of the sensors on your device, including the proximity sensor. It supports Tasker for changing the sensor status (via In-App Purchase), a blacklist/whitelist for choosing how certain apps will respond to Sensor Disabler, and a reliable and efficient way of modifying and disabling sensors without causing unnecessary slowdown on the device.
I can't offer support for phones that I don't own, but if your phone runs a close to AOSP ROM (for instance Nexus devices) or a CM-based/Lineage ROM (which I can easily see the sources for), this should work. If you're having issues, try to gather the logs from the Xposed app that relate directly to this app and post them here as well as your issue. I recommend reading over the logs yourself to see if the issue might be with your Xposed installation and not the app itself.
Links:
Source Code
Module
Google Play Link
This has been tested on:
Nexus 5 running 4.4.2.
Nexus 5 running 5.0.1.
Nexus 5 running 5.1.
LG G2 running 4.2.2.
OnePlus One running CM11S.
OnePlus One running COS12.
Nexus 6P running 6.0
OnePlus One running LineageOS 14 (Nougat)
Currently, this mod works on 4.2 - 7.1.
Post any questions/requests/etc in this thread, and I'll attempt to get to them in a timely manner.
- Wardell Bagby.
here's link : http://repo.xposed.info/module/com.mrchandler.disableprox
and there is any ways to disable it totally??
WardellChandler said:
I saw a fairly important need for this app, so I decided to make it.
Click to expand...
Click to collapse
Why could I need this app and want to disable proximity?
defim said:
Why could I need this app and want to disable proximity?
Click to expand...
Click to collapse
Someone like me who does not find much of a use of the proximity sensor which has been eating up battery while im on call, would be interested in this feature
Don't work with Themasek KK 4.4.4 v105. Galaxy S3
HGT - Galaxy S3 S5 blue - any KK ROM
defim said:
Why could I need this app and want to disable proximity?
Click to expand...
Click to collapse
If, like me, your Nexus 4's proximity sensor is dead and you're unable to wake up your phone during calls!
HorstiG said:
Don't work with Themasek KK 4.4.4 v105. Galaxy S3
HGT - Galaxy S3 S5 blue - any KK ROM
Click to expand...
Click to collapse
Alrighty, thanks for that!
ravijani said:
and there is any ways to disable it totally??
Click to expand...
Click to collapse
Thanks. Possibly, using the Hardware Disabler app on the Play Store. I've never gotten that to work for me, though.
There might also be a way to truly truly disable it using Xposed, but I'd need to delve extremely deep into the Android sources. I'll look more into it, but definitely no promises.
Could you make an app that has an interface and that can disable touch?
Basically when I put YouTube on my device and give it to my daughter to watch her cartoons she presses the screen and videos go back and forth and even exit, I've tried searching everywhere for a touch disable option, there's 2 apps on the play store but don't work, are very old and outdated...
If anybody knows where I can find one please let me know....
Sent from my GT-I9195 CarbonKat 4.4.4
kamikaze702k said:
Could you make an app that has an interface and that can disable touch?
Click to expand...
Click to collapse
To get OT for a minute, while this might be possible, there are some inherent difficulties associated with this. You should look into an app like Live Lock: YouTube & Kids Lock for Android. Best of luck!
Update 1.01 don't work. S3 Temasek KK 4.4.4 v1.05, Boeffla Omni Kernel.
HGT - Galaxy S3 S5 blue - any KK ROM
HorstiG said:
Update 1.01 don't work. S3 Temasek KK 4.4.4 v1.05, Boeffla Omni Kernel.
Click to expand...
Click to collapse
Hmm. I'll have to wait until I get get the 4.4.4 source straight. Expect an update in a day or so for that.
EDIT: So I've gotten the 4.4.4 source, and I can't see why it wouldn't work. Did you reboot after installing?
A problem that plagued me for a year, gone in 2 minutes. Thank you very much.
rohail6 said:
A problem that plagued me for a year, gone in 2 minutes. Thank you very much.
Click to expand...
Click to collapse
That's what I made it for! I'm very happy to help!
Instead of disabling the sensor, you could try recalibrating, as described in this post. it worked for my Sprint GN2.
http://forum.xda-developers.com/showthread.php?t=2569141
Since the N4 suffers an annoying bug which causes a crackling noise to the headset signal whenever the proyimity sensor is active, I'd like to request an option to disable the sensor only when headset is plugged.
It would be even better if you would consider to integrate your app with Tasker so we could disable the sensor on different contexts too.
cramu said:
Since the N4 suffers an annoying bug which causes a crackling noise to the headset signal whenever the proyimity sensor is active, I'd like to request an option to disable the sensor only when headset is plugged.
It would be even better if you would consider to integrate your app with Tasker so we could disable the sensor on different contexts too.
Click to expand...
Click to collapse
I actually have been wanting to try out Tasker support, so I'll look into that. I think I can push an update that'll disable during headphone disconnected only in the next few days, then I'll work on Tasker support.
Thanks for responding so quickly and for considering my suggestions.
Working on HTC Sensation XE running Vipers ROM 5.1.2 (Android 4.1.2)
Thank you very much!!! :good: I finally solved a problem due to the proximity sensor (probably broken) whose wakelock plagued my battery after a call or automatic brightness; thank you!
Noob question: can RILJ wakelock also be related to the proximity sensor?
Bino92 said:
Working on HTC Sensation XE running Vipers ROM 5.1.2 (Android 4.1.2)
Thank you very much!!! :good: I finally solved a problem due to the proximity sensor (probably broken) whose wakelock plagued my battery after a call or automatic brightness; thank you!
Noob question: can RILJ wakelock also be related to the proximity sensor?
Click to expand...
Click to collapse
To be honest, I don't know. I've never come across the RILJ wakelock issue (literally had to Google it to figure out what you meant) but it could be a possibility?
Although, according to this article here, it has something to do with accessing your location.
My two cents is, go ahead and give my app a try and if it works, great! But I don't know anything about the RILJ wakelock issue to provide any concrete data on whether this will fix it or not. Doesn't hurt to try!
Has anyone installed and tried Google Dialer on this phone yet? If so which apk did you use? Any problems?
What google dialer are you talking about? It already has the stock dialer from aosp on the phone.
termleech said:
What google dialer are you talking about? It already has the stock dialer from aosp on the phone.
Click to expand...
Click to collapse
Has built in caller id and you can type in names of nearby places to call stores and such.
I have and works perfectly.
http://www.apkmirror.com/apk/google-inc/google-dialer/google-dialer-1-1-apk/
Junior Passos said:
I have and works perfectly.
http://www.apkmirror.com/apk/google-inc/google-dialer/google-dialer-1-1-apk/
Click to expand...
Click to collapse
Is there anything special needed? Root? Disabling the stock dialer?
No, I have it installed but I have 2 phone apps in app drawer, you can't disable the phone app that comes with the phone.
Just tried it. Moto assist does not work using the Google dialer. So when I'm home, the phone no longer let's me answer the phone with voice activation. I use that more than I'd use the Google dialer features, thanks for posting the apk though.
Junior Passos said:
I have and works perfectly.
http://www.apkmirror.com/apk/google-inc/google-dialer/google-dialer-1-1-apk/
Click to expand...
Click to collapse
Thanks for the link and info!
Any time I do the location search at the top of the dialer in the APK I get a force close of the dialer. For instance I can type "Home Depot", as soon as I press on the result to select it I get a FC.
RyanTX said:
Any time I do the location search at the top of the dialer in the APK I get a force close of the dialer. For instance I can type "Home Depot", as soon as I press on the result to select it I get a FC.
Click to expand...
Click to collapse
I'm pretty sure you need more than just the dialer apk to get that functionality.
I was looking for a way to have that functionality as well, and after a little research I found out that the location search on the dialer is an exclusive feature for Nexus and Google Play devices :crying: . I had that on my Galaxy S4 GPE and I liked that feature too. Found a post on Android Police explaining on how to make it work on other devices, but a lot of bugs can happen.
seco2004 said:
I was looking for a way to have that functionality as well, and after a little research I found out that the location search on the dialer is an exclusive feature for Nexus and Google Play devices :crying: . I had that on my Galaxy S4 GPE and I liked that feature too. Found a post on Android Police explaining on how to make it work on other devices, but a lot of bugs can happen.
Click to expand...
Click to collapse
I've updated to Android 5.0 out of the box when I got my phone few days ago. - This morning I've installed the 1.1 Dialer APK linked in this thread, however, something did not work, when I pull up the app info on the only icon in the drawer it tells me version 5.0-10.
However, if I go into Settings > Apps > (Downloaded Tab) I see Dialer 1.1 is installed, under (All) I still see Dialer, and version lists 5.0-10 - The 5.0-10 is the stock moto one for Android 5.0, and this one does not have the caller ID, reverse look-up.
I might try disabling the 5.0-10, but from what I understand, that messes with the phone in a big way?
Shemploo said:
I've updated to Android 5.0 out of the box when I got my phone few days ago. - This morning I've installed the 1.1 Dialer APK linked in this thread, however, something did not work, when I pull up the app info on the only icon in the drawer it tells me version 5.0-10.
However, if I go into Settings > Apps > (Downloaded Tab) I see Dialer 1.1 is installed, under (All) I still see Dialer, and version lists 5.0-10 - The 5.0-10 is the stock moto one for Android 5.0, and this one does not have the caller ID, reverse look-up.
I might try disabling the 5.0-10, but from what I understand, that messes with the phone in a big way?
Click to expand...
Click to collapse
I'm not sure what can happen if you disable the stock dialer app, maybe prevent you from making/receiving phone calls if you don't have another dialer app installed? That's just my guess though, never actually did it to check. Were you able to make the location feature work?
Sent from my XT1097 using Tapatalk
seco2004 said:
I'm not sure what can happen if you disable the stock dialer app, maybe prevent you from making/receiving phone calls if you don't have another dialer app installed? That's just my guess though, never actually did it to check. Were you able to make the location feature work?
Sent from my XT1097 using Tapatalk
Click to expand...
Click to collapse
I was unable to get the Caller ID to work, the phone shows me that they are both installed ( Settings > Apps ) - however, the one that came with the stock/factory ROM is preventing the 1.1 version for loading/showing at all in the apps list, so short of disabling the stock one (which I understand is not something one should be doing), I can't even open/access the offloaded one (Dialer 1.1)
I might get brave and disable the stock dialer, see if the Dialer 1.1 surfaces in the apps list.
Shemploo said:
I was unable to get the Caller ID to work, the phone shows me that they are both installed ( Settings > Apps ) - however, the one that came with the stock/factory ROM is preventing the 1.1 version for loading/showing at all in the apps list, so short of disabling the stock one (which I understand is not something one should be doing), I can't even open/access the offloaded one (Dialer 1.1)
I might get brave and disable the stock dialer, see if the Dialer 1.1 surfaces in the apps list.
Click to expand...
Click to collapse
I think that no major issues should arise as long as you just freeze the app and not uninstall it with titanium backup, but again, that's just my wild guess haha. Anyway, leave us posted about your findings.
Sent from my XT1097 using Tapatalk
OK - Got it Working!!! - Not Really, it crashes.
Step #1 - Download/Install the APK from this post
(will need a file manager to browse the phone to where the APK was downloaded to)
Step #2 - Create shortcut for Google Dialer 1.1 that you just installed using QuickShortcutMaker
Detailed instructions are HERE - Start at Step #3 on that page.
(Stock Dialer should be the only one showing in app drawer, you need to make a shortcut for the Google Dialer 1.1)
Step #3 - Win!!!
Some Pictures as Proof in Puddin
Stock Moto X Lollipop 5.0 Dialer / Settings
Nexus Android 5.x Dialer (Dialer 1.1) / Settings / Results
Google Dialer 1.1 shortcut above Stock Dialer shortcut.
Since trying this app initially, I've rooted my phone, and I've tried to follow steps outlined in (http://htc-one.wonderhowto.com/how-to/install-new-kitkat-4-4-3-dialer-your-htc-one-0155515/), specifically Step 2 - Where the app is installed in /system/priv-app/ folders - I am sad to report this does not work still on MotoX
As previous users suggested, there are probably those other services the Dialer depends on that need to be installed.
I'll update if I find a solution.
I don't know if it matters but I had a Nexus 6 before getting my Moto X. The Google Dialer was version 2.0. I didn't grab the APK before returning it but I'm sure it could be pulled from the factory image.
I was unable to make this work, root/non-root.
Got it working, here -http://forum.xda-developers.com/moto-x-2014/themes-apps/mod-google-dialer-messenger-pure-edition-t2982408
Hi all,
I've received the OTA update to 7.1.1 (kudos to Wileyfox for delivering!).
However, I'm not too keen on the Truecaller dialer they bundled...
Any suggestions on an unobtrusive T9 dialer? I'd be happy to have Google Phone back (the Marshmallow dialer) but it seems to be unavaible from Google Play...
Thanks
I got pointed to this one here: http://www.apkmirror.com/apk/google...gle-phone-8-0-148481159-android-apk-download/ and will give it a try.
Try ExDialer from Modoohut from the playstore. Supports a number of themes and so on.
Google dialer 8 from apk mirror can't be installed on the device.
This version is ok: http://www.apkmirror.com/apk/google...-7-0-140861421-nonnexus-android-apk-download/
This looks also promising, but I haven't try it: https://forum.xda-developers.com/android/apps-games/app-google-dialer-t3557412
Thanks, i see that I linked to the wrong version. I installed the non-nexus version you linked to and it's fine.
Everybody keeps banging on about true caller like it's new for nougat but I've always had it as default dialer on marshmallow......
ratbags said:
Everybody keeps banging on about true caller like it's new for nougat but I've always had it as default dialer on marshmallow......
Click to expand...
Click to collapse
That's not the same... There was a Truecaller mod on the standard C.os dialer. You could disable it and never see it again . That was not the case in this update.
The stink is being raised because the two questionable pack-ins - Zen and Truecaller - can't be simply disabled. Otherwise most users who didn't want the stuff would just disable it and move on.
dryhte said:
That's not the same... There was a Truecaller mod on the standard C.os dialer. You could disable it and never see it again . That was not the case in this update.
The stink is being raised because the two questionable pack-ins - Zen and Truecaller - can't be simply disabled. Otherwise most users who didn't want the stuff would just disable it and move on.
Click to expand...
Click to collapse
Well my true caller couldn't be disabled even in marshmallow...
ratbags said:
Well my true caller couldn't be disabled even in marshmallow...
Click to expand...
Click to collapse
That's... weird I can't remember how I did it because it literally took seconds... But hey, even here a fix is just a download away. I'm quite happy with the Nougat ROM, just with a different dialer and launcher (in fact I had already replaced Trebuchet by Nova before)
Google Play store says it's not compatible; I've tried various APKs and when I go to install they also say incompatible.
That sucks. What might be the cause? I know the S8 can install it.
I'm also having the same issue... The LG phone app is horrendous
pacmantravis said:
Google Play store says it's not compatible; I've tried various APKs and when I go to install they also say incompatible.
Click to expand...
Click to collapse
This is the dialer I'm using...https://www.apkmirror.com/apk/googl...-7-0-140861421-nonnexus-android-apk-download/
When you go to the link, scroll down to "Download APK". Don't install a newer version, because it probably won't work. Or if you do and it does work, let me know.
It's the stock Google dialer, and everything works. I've used it on several phones lately. When you install it, make sure and go to your settings menu, then apps, then Configure apps, and then set the new dialer to be your default phone app. Easy as pie
Google dialer on V30
lyall29 said:
This is the dialer I'm using...
Click to expand...
Click to collapse
Thanks for this. Planning on picking up my V30 today and want to eliminate that ugly ass LG dialer immediately.
This is the newest update for the Google dialer for non pixel phones. Works great. https://www.google.com/amp/s/forum....id/apps-games/app-google-dialer-t3557412/amp/
justibasa said:
This is the newest update for the Google dialer for non pixel phones. Works great. https://www.google.com/amp/s/forum....id/apps-games/app-google-dialer-t3557412/amp/
Click to expand...
Click to collapse
The "Nearby places" doesn't work in that version.
can someone link a version of google dialer that works fine on V30? do one of these work? https://www.apkmirror.com/apk/google-inc/google-phone/google-phone-13-0-171616398-release/
i hate the lg dialer so much
mrkoven said:
can someone link a version of google dialer that works fine on V30? do one of these work? https://www.apkmirror.com/apk/google-inc/google-phone/google-phone-13-0-171616398-release/
i hate the lg dialer so much
Click to expand...
Click to collapse
This is what I'm looking for too. The Duo integration is what I'm really after.
lyall29 said:
This is the dialer I'm using...https://www.apkmirror.com/apk/googl...-7-0-140861421-nonnexus-android-apk-download/
When you go to the link, scroll down to "Download APK". Don't install a newer version, because it probably won't work. Or if you do and it does work, let me know.
Click to expand...
Click to collapse
As per the notes on the thread, this older version is the only one that fully works on Non-Nexus devices. The newer patched versions may install but are often buggy and lack the necessary framework for spam call rejection and other features.
oh wow...i didn't realize the dialer required framework and such to use those features. kind of second guessing my ordering of the V30 now...
Perhaps this
https://android.gadgethacks.com/how-to/turn-your-lg-v30-into-google-pixel-2-0180558/
Guyinlaca said:
As per the notes on the thread, this older version is the only one that fully works on Non-Nexus devices. The newer patched versions may install but are often buggy and lack the necessary framework for spam call rejection and other features.
Click to expand...
Click to collapse
This old version works for me, but no with Bluetooth, so I cannot use the phone on my car. Stock ugly dialer work well with Bluetooth
[email protected] said:
This old version works for me, but no with Bluetooth, so I cannot use the phone on my car. Stock ugly dialer work well with Bluetooth
Click to expand...
Click to collapse
Bluetooth works in my car with the dialer version 7 point something, same one highlighted in this thread. Permissions maybe?
lyall29 said:
This is the dialer I'm using...https://www.apkmirror.com/apk/googl...-7-0-140861421-nonnexus-android-apk-download/
When you go to the link, scroll down to "Download APK". Don't install a newer version, because it probably won't work. Or if you do and it does work, let me know.
It's the stock Google dialer, and everything works. I've used it on several phones lately. When you install it, make sure and go to your settings menu, then apps, then Configure apps, and then set the new dialer to be your default phone app. Easy as pie
Click to expand...
Click to collapse
Does your dialer have the voicemail tab? I'm on T-Mobile and have to use T-Mobile's Visual Voicemail app on my unlocked phone. I couldn't get the voicemail tab to show up and there was nothing in the settings that could activate it. I tried a SIM card pulling trick I saw on Reddit but that didn't do it either. Thanks!
feelfreetoblameme said:
Does your dialer have the voicemail tab? I'm on T-Mobile and have to use T-Mobile's Visual Voicemail app on my unlocked phone. I couldn't get the voicemail tab to show up and there was nothing in the settings that could activate it. I tried a SIM card pulling trick I saw on Reddit but that didn't do it either. Thanks!
Click to expand...
Click to collapse
I can check when I get home tonight. I’m using my iPhone right now. I’ll let you know later.
Edit...I'm home now and looking at my V30 with the Google dialer, and I don't see a voicemail tab anywhere.
How did you enable call screen or dialing screen to stock one? On my v30 only the dialer screen showsup and the calling screen is LG one.
girish1in said:
How did you enable call screen or dialing screen to stock one? On my v30 only the dialer screen showsup and the calling screen is LG one.
Click to expand...
Click to collapse
You have to ensure that the Google Phone app is actually properly set as your default Dialer/Phone app. I had a similar problem until I did that. Under settings, go to apps and then click on "Configure apps" under the three dot overflow menu on the top right. Make sure the correct app is listed under "Phone app".
lyall29 said:
This is the dialer I'm using...https://www.apkmirror.com/apk/googl...-7-0-140861421-nonnexus-android-apk-download/
Click to expand...
Click to collapse
Thank you thank you THANK YOU! :good:
Been searching for days to find an apk that works on my LG V20, and this works perfectly - even location search.