Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,733,034 Members 47,374 Now Online
XDA Developers Android and Mobile Development Forum

[Q] [APK Request] 4.4 Dialer

Tip us?
 
Sparatan117
Old
#1  
Sparatan117's Avatar
Senior Member - OP
Thanks Meter 58
Posts: 151
Join Date: Oct 2009
Location: South Carolina
Default [Q] [APK Request] 4.4 Dialer

Hey guys,

I tried sideloading the 4.4 Dialer into my system/priv-app/ folder and yet it only crashes every single time. (yes I set the permissions to 0644)
Does anyone ... has anyone tried moving / porting this?

Pulled the Dialer from here
http://www.androidpolice.com/2013/12...-what-can-i-do
 
fffft
Old
#2  
fffft's Avatar
Senior Member
Thanks Meter 199
Posts: 645
Join Date: Jul 2013
Quote:
Originally Posted by Sparatan117 View Post
I tried sideloading the 4.4 Dialer into my system/priv-app/ folder and yet it only crashes every single time

Well I tried it and it works fine. You didn't describe how you tried to install it though, making it rather hard to spot where you went astray.

I'd bet though that you didn't wipe the cache and data in the Application manager plus wipe Dalvik from recovery.

What do I win for being right.. ?






ps: the md5 should be 65:1e:d1:f2:61:07:f9:6e:62:2c:81:08:83:c4:53:a3

.
Attached Thumbnails
Click image for larger version

Name:	Screenshot_2014-07-03-13-48-23.png
Views:	43
Size:	120.5 KB
ID:	2831301  
 
Sparatan117
Old
(Last edited by Sparatan117; 4th July 2014 at 01:34 AM.)
#3  
Sparatan117's Avatar
Senior Member - OP
Thanks Meter 58
Posts: 151
Join Date: Oct 2009
Location: South Carolina
Quote:
Originally Posted by fffft View Post
Well I tried it and it works fine. You didn't describe how you tried to install it though, making it rather hard to spot where you went astray.

I'd bet though that you didn't wipe the cache and data in the Application manager plus wipe Dalvik from recovery.

What do I win for being right.. ?






ps: the md5 should be 65:1e:d1:f2:61:07:f9:6e:62:2c:81:08:83:c4:53:a3

.
You know, I would have loved if it had worked, but it didn't ...

I put the APK directly into priv-apps
set the privilages to 0644
cleared the data from the app
cleared the Dalvik Cache

... still force close... thoughts?

EDIT:

I tried just straight up installing it without it being a system app and it works just fine. Go figure...

Edit 2: Nevermind haha
Resorting to flashing via Recovery. See if this works

Edit 3:
Flashed via Recovery. Emptied Dalvik Cache/Cache on the way in. Still Force Closes.
 
TheArtiszan
Old
#4  
Senior Member
Thanks Meter 77
Posts: 786
Join Date: Jun 2009
Quote:
Originally Posted by Sparatan117 View Post
You know, I would have loved if it had worked, but it didn't ...

I put the APK directly into priv-apps
set the privilages to 0644
cleared the data from the app
cleared the Dalvik Cache

... still force close... thoughts?

EDIT:

I tried just straight up installing it without it being a system app and it works just fine. Go figure...
Are you using a stock unmodified rom?
Like with just towel root or something similar?
 
fffft
Old
#5  
fffft's Avatar
Senior Member
Thanks Meter 199
Posts: 645
Join Date: Jul 2013
Quote:
Originally Posted by Sparatan117 View Post
I tried just straight up installing it without it being a system app and it works just fine. Go figure...
Okay, I get it.. you don't want to pay off the bet.

=8-0



Sure, whatever. Glad it's working for you though. And it works for the rest of us too.

Good enough.

.

---------- Post added at 07:39 PM ---------- Previous post was at 07:35 PM ----------

Quote:
Originally Posted by Sparatan117 View Post
Edit 3:
Flashed via Recovery. Emptied Dalvik Cache/Cache on the way in. Still Force Closes.

Seriously? That doesn't make any sense.

I installed it on two systems and it was super easy and has been super stable. And there are 100+ comments on the original article without anyone there having issues either. Write out a detailed description of all the steps you took to install it so we can see where you went wrong.


.
 
Sparatan117
Old
#6  
Sparatan117's Avatar
Senior Member - OP
Thanks Meter 58
Posts: 151
Join Date: Oct 2009
Location: South Carolina
Yeah well I guess pretty close to stock

I have Beans NF6 Factory build (upgrade without wiping data)
I have Chainfire's autoroot

Flashed TWRP recovery
Flashed the file via this ( http://www.androidfilehost.com/?fid=23269279319196848 ) file.
Wiped Dalvik/Cache via TWRP
Rebooted
Wiped data in App Manager
Started.
[insert picture of dog poop]


but in all seriousness I don't get it either... it's weird.

Although I'm glad I'm not the only one.
 
fffft
Old
#7  
fffft's Avatar
Senior Member
Thanks Meter 199
Posts: 645
Join Date: Jul 2013
Quote:
Originally Posted by Sparatan117 View Post
but in all seriousness I don't get it either... it's weird.

Although I'm glad I'm not the only one.

Okay, two of you ran into problems trying to install it. Still just a minor glitch.

To troubleshoot this though, we need you to be a lot more detailed. You didn't mention a lot of things.. e.g. you didn't say anything about checking permissions in your description.. so did you? And what was the result? Did you check the md5? Did you wipe the cache from the Application manager.. you only mention wiping the data. I know, picky, picky. But troubleshooting is all about the details. And we need to those things if we are to pin down the cause.

I'm also wondering about the order you wiped the data /cache. It's normally done in the reverse and that may be causing you problems. Wiping Dalvik should be the last step.

This procedure works. I've tried it three times now:
Check md5 of download
Move dialer to /system/priv-app
Confirm that permissions are 0644
[you can try running it at this point if you want to. it will force close at this point]
Open the Application manager i.e. Settings > Applications > Application Manager > All > Google Dialer
Force Stop > Clear cache > Clear data > OK
Reboot to recovery mode > wipe cache + Dalvik
Reboot to system
Open app drawer, click on Google Dialer & observe that it works properly


.
 
Sparatan117
Old
#8  
Sparatan117's Avatar
Senior Member - OP
Thanks Meter 58
Posts: 151
Join Date: Oct 2009
Location: South Carolina


bumpkiss

Code:
--------- beginning of /dev/log/system

E/Watchdog(  746): !@Sync 1

E/PersonaManagerService(  746): Unable to read user list

E/PersonaManagerService(  746): Unable to read user list

E/PersonaManagerService(  746): Unable to read user list

E/PersonaManagerService(  746): returning null in  getPersonasForUser

E/MotionRecognitionService(  746):   mReceiver.onReceive : ACTION_USER_PRESENT  :: UNLOCK SCREEN

E/SmartFaceService - 3rd party pause(  746): onReceive, ACTION_STATUS_BAR_ANIMATING: true

E/SmartFaceService - 3rd party pause(  746): onReceive, ACTION_STATUS_BAR_EXPANDED: true

E/ActivityThread( 4896): Failed to find provider info for com.dropbox.carousel.CuOwnerCheckProvider

E/SmartFaceService - 3rd party pause(  746): onReceive, ACTION_STATUS_BAR_COLLAPSED: false

E/PersonaManagerService(  746): Unable to read user list

E/ActivityThread( 5740): Failed to find provider info for com.amazon.dcp.settings

E/Watchdog(  746): !@Sync 2

E/ConnectivityService(  746): Attempt to connect to mobile_mms failed (dataEnabled).

E/PersonaManagerService(  746): Unable to read user list

--------- beginning of /dev/log/main

E/MTPJNIInterface( 6390): Status for mount/Unmount :mounted

E/MTPJNIInterface( 6390): SDcard is  available

E/SQLiteLog( 6390): (21) API call with NULL database connection pointer

E/SQLiteLog( 6390): (21) misuse at line 96852 of [00bb9c9ce4]

E/SQLiteLog( 6390): (21) API call with NULL database connection pointer

E/SQLiteLog( 6390): (21) misuse at line 93317 of [00bb9c9ce4]

E/SQLiteLog( 6390): (21) API call with NULL database connection pointer

E/SQLiteLog( 6390): (21) misuse at line 93317 of [00bb9c9ce4]

E/SQLiteLog( 6390): (21) API call with NULL database connection pointer

E/SQLiteLog( 6390): (21) misuse at line 96852 of [00bb9c9ce4]

E/        ( 6390): [mtp_init_device]  After open the MTP fd = 59 and line = 678...

E/MTPJNIInterface( 6390): Getting gadget reset status0

E/LightSensor(  746): RED : 1, GREEN : 1, BLUE : 1, CLEAR : 1, CALCULATED LUX : 0.000000, CCT : 1596.000000, REAL LUX : 0.000000 a_time = 238, gain = 64, ir=1, rp1=1, gp1=0, bp1=0, cp1=0, cpl=3202560

E/SPPClientService( 6195): [[SystemStateMonitorService]] SystemStateMonitorService : noConnect? : false

E/SMD     (  257): DCD ON

E/LightSensor(  746): RED : 1, GREEN : 1, BLUE : 1, CLEAR : 1, CALCULATED LUX : 0.000000, CCT : 1596.000000, REAL LUX : 0.000000 a_time = 238, gain = 64, ir=1, rp1=1, gp1=0, bp1=0, cp1=0, cpl=3202560

E/MTPRx   ( 6390): state from USB_STATE event DISCONNECTED

E/MTPRx   ( 6390): ignore this event

E/DataRouter(  267): USB Interface is open with 0x9

E/SMD     (  257): ***Received data notification[DR->SMD]***

E/SMD     (  257): Path set is DATA_PATH_DR_SMD_MANAGER

E/SMD     (  257): Message:

E/SMD     (  257): Sending data to SMD: Len = [3]

E/SMD     (  257):  buffer = []

E/SMD     (  257): Wrote 3 chars to SMD PORT fd=7 ch = 81

E/LightSensor(  746): RED : 1, GREEN : 1, BLUE : 1, CLEAR : 1, CALCULATED LUX : 0.000000, CCT : 1596.000000, REAL LUX : 0.000000 a_time = 238, gain = 64, ir=1, rp1=1, gp1=0, bp1=0, cp1=0, cpl=3202560

E/MTPRx   ( 6390): state from USB_STATE event CONNECTED

E/MTPRx   ( 6390): state from USB_STATE event DISCONNECTED

E/MTPRx   ( 6390): stop observing and calling usbRemoved 

E/MTPRx   ( 6390):  sendbooster is false!

E/MTPRx   ( 6390): In usbRemoved Status bar enabled

E/MTPRx   ( 6390): Sending Broadcast

E/SPPClientService( 6195): [[SystemStateMonitorService]] SystemStateMonitorService : noConnect? : false

E/MtpService( 6390): onDestroy.

E/MtpService( 6390): Unregister Mtp disable Receiver

E/MtpService( 6390): Receiver not registered: com.samsung.android.MtpApplication.MtpService$1@42a5d088

E/MtpService( 6390): Unregister mtpEmergencyReceiver

E/MtpService( 6390): Receiver not registered: com.samsung.android.MtpApplication.MtpService$2@42a5d368

E/MtpService( 6390): unregistering mtpMediaReceiver in UnregisterAllIntent

E/MtpService( 6390): Receiver not registered: com.samsung.android.MtpApplication.MtpService$3@42a5d648

E/MTPJNIInterface( 6390): noti = 3
 
fffft
Old
#9  
fffft's Avatar
Senior Member
Thanks Meter 199
Posts: 645
Join Date: Jul 2013
Quote:
Originally Posted by Sparatan117 View Post
--------- beginning of /dev/log/system

E/Watchdog( 746): !@Sync 1
Thanks for that but that log isn't deep enough to answer most of our questions. But if you could tackle the ones I posed in my last post? And can you try the install procedure that I suggested? It should work or at least give us some insight into what is failing.

Meanwhile, the dialer works here.

.
Attached Thumbnails
Click image for larger version

Name:	Screenshot_2014-07-03-19-09-09.png
Views:	18
Size:	99.6 KB
ID:	2831736   Click image for larger version

Name:	Screenshot_2014-07-03-19-09-32.png
Views:	21
Size:	99.5 KB
ID:	2831737   Click image for larger version

Name:	Screenshot_2014-07-03-19-09-43.png
Views:	17
Size:	71.7 KB
ID:	2831738   Click image for larger version

Name:	Screenshot_2014-07-03-19-09-50.png
Views:	15
Size:	122.4 KB
ID:	2831739   Click image for larger version

Name:	Screenshot_2014-07-03-19-08-47.png
Views:	14
Size:	49.7 KB
ID:	2831740  

Click image for larger version

Name:	Screenshot_2014-07-03-19-08-53.png
Views:	16
Size:	62.6 KB
ID:	2831741  
 
aooga
Old
#10  
aooga's Avatar
Senior Member
Thanks Meter 824
Posts: 2,839
Join Date: Feb 2011
Location: California
Quote:
Originally Posted by fffft View Post
Thanks for that but that log isn't deep enough to answer most of our questions. But if you could tackle the ones I posed in my last post? And can you try the install procedure that I suggested? It should work or at least give us some insight into what is failing.

Meanwhile, the dialer works here.

.
Does it work if you click the call button?

Tags
app, dialer, request
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes