[Q] Any drawbacks of using PA's dialer? - Paranoid Android Q&A

Today I noticed that I wasn't actually using Google's stock phone dialer, but rather one built by PA. To be honest, I only noticed this by checking its package name after I noticed something new (the ability to change phone number lookup providers). I was wondering if I lose any sort of functionality or features by not using the stock dialer. In particular, I wondered if the stock dialer provided any information to Google Now cards.

Related

Different dialer

Hi all,
Is there an alternative to the stock dialer for the SIII? Couple of things I don't like about the stock one if anyone knows any fixes for it that I'm not aware of.
When using the keypad to enter the name or number of the person you want to call, my old phone's dialer would suggest people or numbers based on recent or frequent calls so I can punch in a few letters or numbers and who I want to call would normally be at the top of the list and i can just click the name and it would call. The SIII doesn't seem to do that.
Also, this dialer seems pretty sluggish sometimes when working with dialer screens (dialing the chosen number, opening pull down menu, going between tabs, etc.).
Thanks,
Ho'okani
Hookani said:
Hi all,
Is there an alternative to the stock dialer for the SIII? Couple of things I don't like about the stock one if anyone knows any fixes for it that I'm not aware of.
When using the keypad to enter the name or number of the person you want to call, my old phone's dialer would suggest people or numbers based on recent or frequent calls so I can punch in a few letters or numbers and who I want to call would normally be at the top of the list and i can just click the name and it would call. The SIII doesn't seem to do that.
Also, this dialer seems pretty sluggish sometimes when working with dialer screens (dialing the chosen number, opening pull down menu, going between tabs, etc.).
Thanks,
Ho'okani
Click to expand...
Click to collapse
Yea man you type the first number(letter) it pulls a name and next to that name it shows an arrow pointing down with the list of names for that letter. Works great
Sent from my SGH-T999 using xda app-developers app
Thanks. Knew about the arrow thing but just looking for something more intuitive. When you open up the list of names there doesn't seem to be any logical order to it and the ones at the top are usually names I rarely call. You would think the most used or recently called names would be at the top. Plus my phone seems sluggish when trying to open that list of names.
Thanks,
Ho'okani
App store search for dialer will answer your questions.
Sent from my SAMSUNG-SGH-I747 using xda premium
My favorite is exDialer paired with exDialer ICS Theme. Both free ON Google Play.
Thanks. Trying out exDialer and seems to be pretty good so far.
Ho'okani
Try out task650 aokp rom its got that and way way more
Sent from my SGH-I747M using xda premium
thatsupnow said:
Try out task650 aokp rom its got that and way way more
Sent from my SGH-I747M using xda premium
Click to expand...
Click to collapse
Any AOSP rom for that matter, the dialer on AOSP roms are really good. But if you want to stay on the default rom, I'd +1 exdialer for its customization options and speed. I think there are modified stock roms with the AOSP dialer, but I'm not too sure/can't find them at the moment.

[Q] Question pertaining to caller ID

I'm on Rogers. Running stock. I noticed something about caller ID on my previous Note with different ROMs: Some ROMs, like CM, will show the caller's name and number, but other ROMs, such as the stock one I'm running now, only show the number (it will show the name if the person is in my contacts).
I'd like to have PROPER caller ID (i.e. name + number) with this here stock ROM. Can anyone tell me why it's a go on some ROMs and not on others?
So I guess the only difference is that CM will display the number under the contact name, while TW ROMs only display the name (or just the number if no name is stored for that specific number) of the person calling.
Personally I don't care who so and so's number is, because their number is already stored on my phone.
I can't see this ever being changed, seeing as this wouldn't be a simple "add on".
Sent from my SGH-I317 using xda app-developers app
No, it's more like a CM knows the name of a non-contact, whereas TW doesn't. For example, let's say Sears calls me about my underpants catelogue order. Sears isn't in my contacts. TW caller ID will show "800-669-6969", and CM will show "Sears 800-669-6969".
Ah yes I know what you mean now. For my carrier thats a feature called caller id lookup. I think the carrier searches the 411 and sends the info to the phone.
Very good question now that I understand. I'm not sure if that has anything to do with APN settings or possibly TW ROMs don't have that feature available. I don't have that on my note 2 either, yet had that with my old iPhone.
Sent from my SGH-I317 using xda app-developers app
Yes, I thought perhaps it was a carrier feature, but it's puzzling why it works with some ROMs and not others,.
velveteen71 said:
Yes, I thought perhaps it was a carrier feature, but it's puzzling why it works with some ROMs and not others,.
Click to expand...
Click to collapse
Unless the specific rom looks for the 411 using data while the call is coming through. Wish TW ROMs had it, cause I'm not going to switch and lose out on all the features.
Sent from my SGH-I317 using xda app-developers app

Custom ROM with whitelist feature.....

Is there a custom rom out that allows a "Call Blocking" mode, with a whitelist feature?
The stock Galaxy S3 from AT&T has a call blocking option, which is toggle on or off, and within that, you can choose to whitelist certain contacts, so for example, my phone has call blocking turned in at night, but yet certain work people can ring my phone no matter what, my family, etc.
That's the basic piece that would be awesome. To make it beyond perfect, having the option to let text sounds, email sounds, and phone sounds come through for a designated contact would be the icing on the cake.
It's the one feature I've missed from my old Blackberry, the sound profiles and the "exception" list was above and beyond great.
Thanks,
10k
AW: Custom ROM with whitelist feature.....
Not a custom ROM but an App (needs root though). Give LBE Security Manager a shot. http://forum.xda-developers.com/showthread.php?t=1422479
Sent from my GT-I9100G using xda app-developers app
This is also the reason why I've stuck with AT&T's stock firmware for so long. I wanted to try out Rogers' stock firmware on my i747, but I wanted to know know if there is a way to tell what bloatware comes in each carrier released version. I'm just being told that Rogers has less bloatware than AT&T, but I have no way of telling how much less bloatware as I want to get good battery life without the device being unstable. Custom ROMs no longer interest me unless its something that adds features from the Note2.
I'm trying to look for the APK file that you wanted that you can play with it from the stock ROM I had extracted earlier.
That's what I've been doing too. I've tried quite a few ROM's over the time I've had Android devices, but that one feature is something I actually really appreciate having.
I am currently using the stock AT&T ROM on my device, rooted it, and went nuts with root uninstaller (a few times a little too nuts, but CWM saved the day). It's running well, but I do miss how great some of those custom rom's do with battery life and speed.
Instead of looking for a ROM, why not simply install an app like touch pal contacts that had option for both white listing and black listing.
Sent from my SAMSUNG-SGH-I747 using xda premium
I actually haven't found one that does what I want, cleanly anyway. I'll try your suggestion out.
If you are looking at AOSP roms you will need to look at the Play Store or some mods. A couple mentioned here are not bad but like you said, they may not be as "easy" as what you want. You can always try some customized ROMS based off the SGS3 stock ROM. I have tried one or two with the Blocking Feature (maybe more but since I have only recently started using it I didn't really look for it).

Lost Functionality with Custom Roms?

So Im going to pick up a note 3 next week, sick of verizons 120 dollar phone bills, so gonna move to T-mobile. mainly for the Wi-Fi calling since i work in a metal dungeon with no cell coverage.
I will probably go ahead and get SU, but wait until cyanogenmod kit kat comes out to do a custom rom.. Does anyone have any idea how many (if any at all) of the note 3 software packages we will lose? i mean will the s pen and wi-fi calling and all the other options still work like it does out of the box?
Nope, with cm you will lose everything. Wifi calling, s pen features, all the motion features, camera, etc... That's why I stick to touchwiz.
Sent from my SM-N900T using xda app-developers app
flipq88 said:
Nope, with cm you will lose everything. Wifi calling, s pen features, all the motion features, camera, etc... That's why I stick to touchwiz.
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
Oh? So someone has already made a CM rom for the note3? Please direct me to it, otherwise all you're spouting out is hearsay.
Rickdaddy said:
Oh? So someone has already made a CM rom for the note3? Please direct me to it, otherwise all you're spouting out is hearsay.
Click to expand...
Click to collapse
No it's a fact. I don't need there to be a cm rom to know those features will be lost. You know why? Cuz its AOSP, and all the features are part of TOUCHWIZ. So don't try to be a smartass.
Sent from my SM-N900T using xda app-developers app
flipq88 said:
Nope, with cm you will lose everything. Wifi calling, s pen features, all the motion features, camera, etc... That's why I stick to touchwiz.
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
You're not wrong, but you're not really right either. You won't lose EVERYTHING, you'll lose the TouchWiz-specific stuff and gain the AOSP-specific stuff.
WiFi calling will be gone, that's a T-Mobile specific thing really but it's baked into the stock ROM and not open source, thus GONE.
S-Pen hardware itself likely will work, as its driver is baked into the kernel which is open source. It will show up as a pointing device like a mouse, but third party S-Pen supporting apps will still be able to read pressure sensitivity and S-Pen button states. The TouchWiz-specific S-Pen functionality will be gone such as pen popup menu, pen windows, pen screenshot, and other pen actions built into the TouchWiz software. You'll still be able to take notes and draw with third party apps (of which many exist).
Motion features will be gone, those are TouchWiz specific software things. The motion sensors themselves will still be usable by apps that use motion features themselves, but the TouchWiz software motion features are GONE.
Camera will still exist, but instead of the TouchWiz camera app it will be the AOSP (or modified version thereof) camera app. You'll still have all the camera hardware features (flash, touch focus, video, etc) but the software image enhancements TW provides will be gone (replaced by whatever software image enhancements the ROM's app has though). CM's version of the AOSP camera app is quite good though, on my Note 1 it had plenty of features and took great pics. There's also Focal. The front camera is also still usable both by the camera app and by video chat programs. Camera features like 4K and slow motion video may not be supported right out of the box, but CM's been pretty good at updating the AOSP camera app as new hardware comes out. Remember that both of those camera features aren't Samsung's doing but rather features of the Snapdragon 800 SoC and many non-Samsung phones (including AOSP's flagship Nexus 5) are using that processor. You can be pretty much guaranteed those will be supported.
So, tl;dr: quit spreading the FUD that AOSP removes critical functionality. It does remove a lot of software functionality, but the hardware will still be supported and what you lose in TouchWiz features you make up for in custom ROM features. If you like the TW features stick with TW, but if you like the custom ROM features you're probably better off with a custom AOSP-based ROM. There are already attempts to bring things like multi-window and such to AOSP in projects like Halo for Paranoid Android and OmniROM which has splitscreen working. More options are a good thing, not a bad one.
As soon as Google Voice is integrated with Hangouts (of which it already is on iOS, grrr), WiFi calling will be available on AOSP. You will just have to set up a free Google Voice number, then have incoming calls be forwarded to Google Talk (Hangouts) and your regular number. So if you have a cell connection, answer it with the stock dialer; if you don't have a cell connection, answer it with Hangouts. You will have to give out your Google Voice number (or port your number to Google Voice), but after that, just direct all cellular calls to go through Google Voice, then you will only have one number.
A great thing about giving out your Google Voice number instead of your regular number, is that if you get a call from an advertiser (spam), you can set Google Voice to play a "this number has been disconnected" recording to that number if they call again (call blocking/filtering). That way, you will never get a call from them again, even if they keep calling. Again, all this is free except to port your number.
Of course, we have yet to see Google Voice integration with Hangouts on Android, and it is looking like May 14th, 2014 will likely be when we may see it.
thanks for the replies. i think ill stick with touchwiz for a while, i liked it in my 14 minutes playing with it, so im sure ill like it more once i actually own the phone.
I was hoping we could pry the software from t mobiles rom and apply it to a custom rom, but i guess the simplest thing for me will be to just root and get rid of the bloat + autostarts.

[Q] Google Wallet Tap and Pay on AOSP

For a long time I used a stock TW rom with my Note 2. I recently switch to AOSP roms (currently Carbon ROM) and one of the only things I'm disappointed with is that when I install Google Wallet it no longer has the option for Tap and Pay. First off, does anyone know why it would not have this option (I'm using AT&T I317 build prop settings) and secondly, is there something I can do to fix this?
Its not just you. Tap and pay unavailability is an ongoing problem with aosp roms... even kitkat ones, Which is weird because afaict Google nexus phones (which are pure android) have gw tap and pay that works. Even weirder still is how little the xda folks know (or care) about it.
I kinda want to know if gw tap and pay works on the cyanogenmod one plus one?
After nearly two years running aosp roms on my note 2 (which I am using for this post), I unrooted and went back to stock mostly for tap and pay.
I also just preordered a nexus 6. Even though it's pure Google I expect tap and pay to work. If it doesn't, it's going back.
-Peter
I have found posts on xda and other places (albeit older posts for older versions of GW) that made it seem like it was possible. I have seen molded versions of GW apks and build.prop hacks to make the phone appear to be a different phone.
I agree with you though that I'm surprised this hadn't been discussed more here on xda. I have searched every combination of keywords I could think of to figure this out.

Categories

Resources