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/1...n-doesnt-show-up-in-my-app-tray-what-can-i-do
Sparatan117 said:
I tried sideloading the 4.4 Dialer into my system/priv-app/ folder and yet it only crashes every single time
Click to expand...
Click to collapse
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
.
fffft said:
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
.
Click to expand...
Click to collapse
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.
Sparatan117 said:
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...
Click to expand...
Click to collapse
Are you using a stock unmodified rom?
Like with just towel root or something similar?
Sparatan117 said:
I tried just straight up installing it without it being a system app and it works just fine. Go figure...
Click to expand...
Click to collapse
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 ----------
Sparatan117 said:
Edit 3:
Flashed via Recovery. Emptied Dalvik Cache/Cache on the way in. Still Force Closes.
Click to expand...
Click to collapse
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.
.
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.
Sparatan117 said:
but in all seriousness I don't get it either... it's weird.
Although I'm glad I'm not the only one.
Click to expand...
Click to collapse
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
.
bumpkiss
Code:
--------- beginning of /dev/log/system
E/Watchdog( 746): [email protected] 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): [email protected] 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: [email protected]
E/MtpService( 6390): Unregister mtpEmergencyReceiver
E/MtpService( 6390): Receiver not registered: [email protected]
E/MtpService( 6390): unregistering mtpMediaReceiver in UnregisterAllIntent
E/MtpService( 6390): Receiver not registered: [email protected]
E/MTPJNIInterface( 6390): noti = 3
Sparatan117 said:
--------- beginning of /dev/log/system
E/Watchdog( 746): [email protected] 1
Click to expand...
Click to collapse
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.
.
fffft said:
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.
.
Click to expand...
Click to collapse
Does it work if you click the call button?
aooga said:
Does it work if you click the call button?
Click to expand...
Click to collapse
Yes it does (just tried it)
Sorry, I did follow your procedure to the letter, and the last post I posted was the result.
I'm thinking it's just not going to happen. Maybe a full system wipe is needed... or something. Who knows. Thanks for trying though.
Related
BUG REPORTING:
This program was initially ineteded to generate a unique IMEI based on your device S/N and update Dev's install zip files... it has become so much more, and as such there are many functions involved in this process.
Due to the complexity the program has taken on... far beyond what I initially intended... to report bugs please try to use the following as a template:
Function attempting: i.e. Updating ROM... In Place Upgrade... Update framework saved on computer... etc.
Error Messages: any error message you receive... or the last message you saw prior to the issue.
End result: i.e. TelephonyManager updated, ROM not... TelephonyManager updated framework.jar not... etc....
Environment: ROM in same folder as !IMEIme.exe... ROM on same drive as IMEIme.exe... ROM on different drive... etc. (same for framework if updating framework instead)
!IMEIme.ini settings: you can put your entire ini file if you'd like.
If you could take notes of EXACTLY what buttons you click on which prompt it would be EXTREMELY helpful...
As I said, this program has taken on functions I initially had not imagined including... the more features added, the more complex testing and tracking bugs becomes... I don't want to include a bunch of messages just for the sake of letting you know where in the code you are... would not be beneficial to you... more buttons to click for no reason, etc.
The more detailed you can be, the quicker I can see what is happening... otherwise I have to try to duplicate what I think you are doing when you get the error.
Everyone should click "Thanks" on bug report posts... they have been instrumental in getting the program where it is so far.
RESERVED...
Adverse effects after running
First off, thanks for a wonderful application! Your app did in fact correctly give my Kindle a IDEI number, but it seems to have adverse effects.
Function attempting: Tried both in place Rom and update device and now attempting to use app with sound
Error Messages: Unfortunately DSP Manager has stopped (repeatably on any app)
End result: No sound and music apps crash. Some apps work but many do not. (I can provide logcat if needed)
Environment: Kindle Fire running cm9 using Hashcodes 3.0 Kernal latest (11) update.
!IMEIme.ini settings:
Use_In_Place = 0
Use_Previous_Patch = 0
Use_Serial_Number = 0
Use_MAC_Address = 0
Use_Manual_Input = 1
Encrypt_IMEI = 0
Use_IMEI(15) = 0
Use_ADB = 1
Use_ADB(usb) = 1
Use_ADB(WiFi) = 0
Clean_Up = 1
Include_Patch = 1
Device_Manufacturer = TI
Manufacturer_Device = Blaze
Device_Model = Full Android on Blaze or SDP
Build_Fingerprint = google/passion/passion:2.3.6/GRK39F/189904:user/release-keys
LCD_Density =
WiFi_IP_Address =
IMEI = 00127948612384612
Although I have tried multiple settings and configurations. I am sort of a noob so sorry if this is a silly problem.
Having looked into this... I can tell you there's nothing that the IMEI Generator does that would cause the issues you are seeing. I would recommend flashing a non-IMEI'd ROM for testing... then either do in place IMEI generation or running the IMEI Generator against the same ROM you flash.
For what you are doing... there are 2 files that are being modified, and neither should cause FC issues...
/sysem/build.prop for the manufacture, device, and build fingerprint
/system/framework/framework.jar is being extracted and edited to patch the IMEI in the GetDeviceID() function in android/telephony/TelephonyManager.smali and recompiled.
Clearing cache and dalvik cache may be something to try.
Thanks! Clearing both caches AFTER the install made it work great. I had been clearing all of the memory beforehand but it did not work. My apps now work great!
Motorola Razr GSM (SPDREM_U_01.6.7.2-180_SPU-19-TA-11.6_SIGNEuropeAustraliaEMEA_USASPDRICSRTGB_HWp2b_Service1FF) ICS.
I deodexed framework.jar because application seems to not work on odex files (as stock is), anyway new deodexed framework have not /com/android/internal/telephony/gsm/GSMPhone.smali file?! (or dir!!) infact !IMEIme 2.2.0.2 tell me about this issue (no GSMPhone.smali found). framework patched do not present diffecence between original one. exactly the same. no /android/telephony/TelephonyManager.smali mod applied.
I tryied to patch framework by "update device" + adb usb, with no device connected i choosed my framework.jar in my pc.
[Settings]
Use_In_Place = 1
Use_Previous_Patch = 0
Use_Serial_Number = 1
Use_MAC_Address = 0
Use_Manual_Input = 1
Encrypt_IMEI = 0
New_Type = 1
Use_IMEI(15) = 0
Use_ADB = 1
Use_ADB(usb) = 1
Use_ADB(WiFi) = 0
Clean_Up = 1
Include_Patch = 0
Device_Manufacturer =
Manufacturer_Device =
Device_Model =
Build_Fingerprint =
LCD_Density =
WiFi_IP_Address =
IMEI = 02546451548481584
stock framework.odex, jar and my deodexed framework attached.
Yes... due to another user trying to use the generator on a device with a framework.odex file instead of framework.jar I am looking into the most effective method of handling that situation. As of now... the generator will not work for you to patch imei functionality into the framework on these devices.
i deodexed also framework.jar but no way to patch it, GSMPhone.smali is missing totally even in backsmalied odex too!!!!
I decided to apply the patch manually, but without this file and TelephonyManager.smali not regoular i was thinking about hard mod by motorola?! do you know something about?
Pls man, give me an hand, show me the way, backsmali it you too http://forum.xda-developers.com/attachment.php?attachmentid=1634550&d=1357865096
I'm looking into the method to implement the imei into this.
do you mean into TelephonyManager.smali? I'm looking on it too. Seems so strange this framework...
Actually... looking through to find the best call to implement the patch into... TelephonyManager was the original method... but there may be better places to patch it.
Code:
invoke-direct {p0}, Landroid/telephony/TelephonyManager;->getSubscriberInfo()Lcom/android/internal/telephony/IPhoneSubInfo;
move-result-object v2
invoke-interface {v2}, Lcom/android/internal/telephony/IPhoneSubInfo;->getDeviceId()Ljava/lang/String;
All does make sense now:
http://grepcode.com/file/repository...nternal/telephony/IPhoneSubInfo.java?av=f#174
BUT, where is com.android.internal.telephony.iphonesubinfo!?!?! seems not present... all "internal" dir is missing here, backsmali fault or my fault?!
hiiii
hi,
any news of this? =)
This is the best software for this!
I'm working on the best solution... I understand the desire for this... but I want to ensure the method I choose is the best overall... and to ensure I can properly detect which method to implement during the operation.
If you could zip your entire /system/framework folder and add your /system/build.prop file it would help me test some things I've been putting together for odexed systems.
attaching files
DizzyDen said:
If you could zip your entire /system/framework folder and add your /system/build.prop file it would help me test some things I've been putting together for odexed systems.
Click to expand...
Click to collapse
Hi, Im attaching my files.
You can download here: w w w . 4 s h a r e d . c o m / z i p / j Q n n 9 8 _ B / s y s t e m . h t m l
Thanks for the help
Error ...
Hi Dizzy
I tried to use your update, but have a error ... My device is Motorola Razr XT910 with 4.0.4
after I choose the "framework.jar" he return this error:
Line 3710 (File: ".....\IMEI\!IMEIme.exe");
Error: Variable used without being declared.
After this the program close without any click to exit ..
Im, attaching a print screen
Tnx a lot man
waldirsp11 said:
Hi Dizzy
I tried to use your update, but have a error ... My device is Motorola Razr XT910 with 4.0.4
after I choose the "framework.jar" he return this error:
Line 3710 (File: ".....\IMEI\!IMEIme.exe");
Error: Variable used without being declared.
After this the program close without any click to exit ..
Im, attaching a print screen
Tnx a lot man
Click to expand...
Click to collapse
fixed... I guess nobody has been using the "Use Previous Fix" option for a while. New version uploaded... thank you for the bug report. The screen shots really helped track it down.
another error...
Hi DizzyDen,
I want to add an IMEI to my "SUPERPAD 6", but after the window: "IMEI is..." is displayed, then popup an autoit error window:
Line 3710 (File "..."): Error: Variable used without being declared.
Can you help?
Ponozka said:
Hi DizzyDen,
I want to add an IMEI to my "SUPERPAD 6", but after the window: "IMEI is..." is displayed, then popup an autoit error window:
Line 3710 (File "..."): Error: Variable used without being declared.
Can you help?
Click to expand...
Click to collapse
Before I start looking into this... note that the IMEI generator does not support de-odexing odexed systems yet... I would suggest using it on the ROM then flashing it to the device and let the device odex it again.
Hi,
Internation Pardus v15 image on rooted i9300, works very well except for this really odd USB connection error when connecting it to my Sony BT3900u car stereo, it was previously connecting without issue on the v15 Pardus build but for unknown reasons to myself now always presents an error.
Does anyone have any ideas as to what might be causing this issue? Any help would be greatly appreciated.
After getting this issue the first time, I ran through a full rebuild, wiped phone/cache/dalvick and error still persisted post rebuild.
Model:
GT-i9300
Android Version:
4.2.2
Baseband
I9300XXEMA5
Kernel version:
3.0.31-702147
Build Number:
Pardus HD Rom XV XXUDME7
Logcat:
E/MTPRx ( 8982): Read Error Came false
E/ ( 8982): read error [0] [Success]
E/MTPRx ( 8982): state from USB_STATE eventDISCONNECTED
E/MTPRx ( 8982): /data/data/com.samsung.android.MtpApplication/gadgetDisconnectAndConnect.txt: open failed: ENOENT (No such file or directory)
E/MTPRx ( 8982): stop observing and calling usbRemoved
E/MTPRx ( 8982): In usbRemoved Status bar enabled
E/MTPRx ( 8982): Sending Broadcast
E/MtpService( 8982): onDestroy.
E/MtpService( 8982): Unregister Mtp disable Receiver
E/MtpService( 8982): Receiver not registered: [email protected]
E/MtpService( 8982): unregistering mtpMediaReceiver in UnregisterAllIntent
E/MtpService( 8982): Receiver not registered: [email protected]
E/MTPJNIInterface( 8982): noti = 3
E/ ( 8982): ****** [mtp_usb_mtp_finalize] mtp_close_fd Calling
E/ ( 8982): [mtp_close_fd] fd = 50...
E/ ( 8982): [mtp_close_fd] USB endpoint [50] closed...
E/ ( 8982): ****** [mtp_usb_mtp_finalize] Updating the gInitializeFlag Flag to FALSE
E/ ( 8982): ****** [mtp_usb_mtp_finalize] Calling mtp_stop_io
E/SEC PowerHAL( 2447): sysfs_write : Error opening /sys/class/input/input1/enabled: No such file or directory
E/SEC PowerHAL( 2447): sysfs_write : Error opening /sys/class/input/input8/enabled: No such file or directory
E/videowall-TranscodeReceiver(10572): broadcastMSG : android.intent.action.ACTION_POWER_DISCONNECTED
E/MTPRx (10600): In MtpReceiverandroid.hardware.usb.action.USB_STATE
E/MTPRx (10600): check value of boot_completed is1
E/MTPRx (10600): check booting is completed_sys.boot_completed
E/MTPRx (10600): Sd-Card path/storage/extSdCard
E/MTPRx (10600): Status for mount/Unmount :mounted
E/MTPRx (10600): SDcard is available
E/MTPRx (10600): The value of first_boot is 1
E/MTPRx (10600): [ 662] The value of first_boot is 1NORMAL SEQUENCE
E/MTPRx (10600): Received USB_STATE with sdCardLaunch = 0
E/MTPRx (10600): configured is false
I'm guessing this is the correct part of the log that pretains to the MTP/USB part. If not I have attached a full log.
Try typing this in a terminal window or adb shell on your phone:
Code:
touch /data/data/com.samsung.android.MtpApplication/gadgetDisconnectAndConnect.txt
Or, make a txt file called gadgetDisconnectAndConnect and place it in /data/data/com.samsung.android.MtpApplication folder.
xpmode said:
Try typing this in a terminal window or adb shell on your phone:
Code:
touch /data/data/com.samsung.android.MtpApplication/gadgetDisconnectAndConnect.txt
Or, make a txt file called gadgetDisconnectAndConnect and place it in /data/data/com.samsung.android.MtpApplication folder.
Click to expand...
Click to collapse
Hi, thanks for the reply.
I did that as quoted, nothing seems to have changed, What should I be looking for?
Thanks!
Hello everyone
I've managed to unlock and root my SGP312 (pollux_windy). Because I always liked AOKP, I tried to install this custom ROM. Here's what I did:
1) Flashed Little Kernel into /boot while in Sony's Fastboot Mode
2) Flashed extracted boot.img of AOKP into "boot" and newest TWRP recovery (v2.6.3) into "recovery" while in LK's Fastboot Mode
3) Rebooted into TWRP recovery, wiped data, cache and dalvik cache
4) Flashed newest AOKP version (jb-mr2 milestone #1 for pollux_windy)
5) Flashed gapps (gapps-jb-20130813-signed.zip)
And tada, the custom ROM booted and everything was fine... No force closes / crashes, no problems, everything worked like a charm.. except the god damn Play Store! Whenever I open the Play Store, it only says "No connection". Pressing retry doesn't help at all. Ofcourse I always search through some forums before posting an issue, so here's what I've already tried:
- Other custom ROM (CM 10.2 stable for pollux_windy)
- Other gapps package (pa_gapps-full-4.3-20131102-signed.zip)
- Force Google Play Store and Google Play Services to stop and delete their data
- Wiped cache and dalvik cache
- Tried a connection without native IPv6 (WLAN hotspot of my HTC One, going over mobile internet which is clearly IPv4 only)
- Checked /etc/hosts (only contains 127.0.0.1 localhost)
- Executed Shark for Root -> There is clearly some data activity going on, my tablet seems to send some data to the google servers but they return an empty response as it seems (see logcat down below)? Unfortunately I am not able to analyze the packets, thanks to SSL/HTTPS...
- Changed some build.prop settings to match an original installation (model=SGP312, device=SGP312 and so on...)
And none of these methods worked. I am totally clueless what else I could try? Here's a logcat snippet:
Code:
D/Finsky ( 4435): [1] 12.onClick: b/5160617: Reinitialize account [00Z7aRpoYHPCeSI-XHfBz1uwqFI] on retry button click
D/Volley ( 4435): [221] DiskBasedCache.clear: Cache cleared.
D/Volley ( 4435): [225] DiskBasedCache.clear: Cache cleared.
I/qtaguid ( 4435): Failed write_ctrl(u 52) res=-1 errno=22
I/qtaguid ( 4435): Untagging socket 52 failed errno=-22
W/NetworkManagementSocketTagger( 4435): untagSocket(52) failed with errno -22
E/DfeApi ( 4435): [1] DfeRequest.deliverResponse: Null wrapper parsed for request=[[ ] https://android.clients.google.com/fdfe/toc 0xe8d195d1 NORMAL 21]
D/Finsky ( 4435): [1] ErrorStrings.get: No specific error message for: com.android.volley.ParseError: java.lang.RuntimeException: java.lang.NullPointerException: expected receiver of type com.google.android.finsky.protos.Response$Payload, but got null
W/NFC-LLC ( 1165): LLC length mis-match
My build.prop is now reverted to the original AOKP build.prop, which can be found here: dl.snapserv.net/build.prop.txt (Sorry, I am not allowed to post links yet...) Have you guys any idea? XDA is basically my last hope, otherwise it seems like I am doomed to use the stock ROM :/ Or did I do something wrong?
Thanks for reading and have a nice day!
Regards
NeoXiD
Code:
D/Finsky ( 4435): [1] 12.onClick: b/5160617: Reinitialize account [00Z7aRpoYHPCeSI-XHfBz1uwqFI] on retry button click
D/Volley ( 4435): [221] DiskBasedCache.clear: Cache cleared.
D/Volley ( 4435): [225] DiskBasedCache.clear: Cache cleared.
I/qtaguid ( 4435): Failed write_ctrl(u 52) res=-1 errno=22
I/qtaguid ( 4435): Untagging socket 52 failed errno=-22
W/NetworkManagementSocketTagger( 4435): untagSocket(52) failed with errno -22
E/DfeApi ( 4435): [1] DfeRequest.deliverResponse: Null wrapper parsed for request=[[ ] https://android.clients.google.com/fdfe/toc 0xe8d195d1 NORMAL 21]
D/Finsky ( 4435): [1] ErrorStrings.get: No specific error message for: com.android.volley.ParseError: java.lang.RuntimeException: java.lang.NullPointerException: expected receiver of type com.google.android.finsky.protos.Response$Payload, but got null
W/NFC-LLC ( 1165): LLC length mis-match
[/QUOTE]
Same error on my Acer A500 TegraOwners Rom 4.3 MR2 v8t6. Cant find solution.
bondcheg said:
Code:
D/Finsky ( 4435): [1] 12.onClick: b/5160617: Reinitialize account [00Z7aRpoYHPCeSI-XHfBz1uwqFI] on retry button click
D/Volley ( 4435): [221] DiskBasedCache.clear: Cache cleared.
D/Volley ( 4435): [225] DiskBasedCache.clear: Cache cleared.
I/qtaguid ( 4435): Failed write_ctrl(u 52) res=-1 errno=22
I/qtaguid ( 4435): Untagging socket 52 failed errno=-22
W/NetworkManagementSocketTagger( 4435): untagSocket(52) failed with errno -22
E/DfeApi ( 4435): [1] DfeRequest.deliverResponse: Null wrapper parsed for request=[[ ] https://android.clients.google.com/fdfe/toc 0xe8d195d1 NORMAL 21]
D/Finsky ( 4435): [1] ErrorStrings.get: No specific error message for: com.android.volley.ParseError: java.lang.RuntimeException: java.lang.NullPointerException: expected receiver of type com.google.android.finsky.protos.Response$Payload, but got null
W/NFC-LLC ( 1165): LLC length mis-match
Same error on my Acer A500 TegraOwners Rom 4.3 MR2 v8t6. Cant find solution.
Click to expand...
Click to collapse
In my case it was Little Kernel's fault. Little Kernel messed up the serial number, to the Google servers received "X-Device-ID: 0" instead of my serial number. (How I found that problem? I just went so far that I've intercepted the traffic to the google servers with a fake root certificate and Fiddler...) Such requests will just get an empty answer, which triggers these logcat errors. If you connect your device with adb, do you see the correct serial or just some messed up unicode characters like yyyyyyy...?
Regards
NeoXiD
NeoXiD said:
Same error on my Acer A500 TegraOwners Rom 4.3 MR2 v8t6. Cant find solution.
Click to expand...
Click to collapse
In my case it was Little Kernel's fault. Little Kernel messed up the serial number, to the Google servers received "X-Device-ID: 0" instead of my serial number. Such requests will just get an empty answer, which triggers these logcat errors. If you connect your device with adb, do you see the correct serial or just some messed up unicode characters like yyyyyyy...?
Regards
NeoXiD[/QUOTE]
I`m novice user and never conneced my device with adb and dont know how to do it.
bondcheg said:
In my case it was Little Kernel's fault. Little Kernel messed up the serial number, to the Google servers received "X-Device-ID: 0" instead of my serial number. Such requests will just get an empty answer, which triggers these logcat errors. If you connect your device with adb, do you see the correct serial or just some messed up unicode characters like yyyyyyy...?
Regards
NeoXiD
I`m novice user and never conneced my device with adb and dont know how to do it.
Click to expand...
Click to collapse
Okay.. Then follow this guide here: http://forum.xda-developers.com/showthread.php?t=2141817 for installing ADB and execute the command "adb devices". Although, if you do not even know what adb is, you haven't probably flashed Little Kernel, so my solution might not be the right one. Have you tested any of my tries I've listened at the thread start?
Regards
NeoXiD
NeoXiD said:
Okay.. Then follow this guide here: http://forum.xda-developers.com/showthread.php?t=2141817 for installing ADB and execute the command "adb devices". Although, if you do not even know what adb is, you haven't probably flashed Little Kernel, so my solution might not be the right one. Have you tested any of my tries I've listened at the thread start?
Regards
NeoXiD
Click to expand...
Click to collapse
A little bit hard for me. Try tomorror. But in windows the sireal number of my device looks like 000000m:.
---------- Post added at 06:51 PM ---------- Previous post was at 06:46 PM ----------
NeoXiD said:
Okay.. Then follow this guide here: http://forum.xda-developers.com/showthread.php?t=2141817 for installing ADB and execute the command "adb devices". Although, if you do not even know what adb is, you haven't probably flashed Little Kernel, so my solution might not be the right one. Have you tested any of my tries I've listened at the thread start?
Regards
NeoXiD
Click to expand...
Click to collapse
A little bit hard for me. Try tomorror. But in windows the sireal number of my device looks like 000000m:.
Emm i done mostly all you listened at the thread start but nothing helps.
Only other ROMs works fine. In any other ROMs play market have no errors. But in case i done all as guides says why other people a500 with this ROM works fine but not mine?
Sry for my english.
bondcheg said:
A little bit hard for me. Try tomorror. But in windows the sireal number of my device looks like 000000m:.
---------- Post added at 06:51 PM ---------- Previous post was at 06:46 PM ----------
A little bit hard for me. Try tomorror. But in windows the sireal number of my device looks like 000000m:.
Emm i done mostly all you listened at the thread start but nothing helps.
Only other ROMs works fine. In any other ROMs play market have no errors. But in case i done all as guides says why other people a500 with this ROM works fine but not mine?
Sry for my english.
Click to expand...
Click to collapse
That might be the fault then, because it might get interpreted as serial number '0', which might get rejected by Google. Did you flash any custom bootloader? Normally this should not occur... You can also drop me a PM so we do not spam this thread with a 4-eye-conversation.
Regards
NeoXiD
Hello there,
My Samsusng Galaxy S2 (i9100) has recently stopped working as it is supposed to. While I tried debugging the issue in any way I could, I figured out I might get some help over here.
At any time that the device itself isn't connected to a power source (USB cable [adb] or the charger), it randomly crashes (the screen turns black and I have to turn the phone on again). I also must say that this problem doesn't happen while on the recovery screen (CWM based recovery).
At first I thought this may happen because I've installed a pretty old version of Cyanogenmod (the cm11 installer version), so I installed the recent monthly build, but the issue still persists. I've tried debugging the device wirelessly (because when it was connected to a power source it never crashed), so I played a game which makes the CPU work abit, and I thought I'll get a crash log - which I didn't get. The last radio signal I got from the phone was this:
I/LibraryLoader( 2817): Expected native library version number "",actual native
library version number ""
I/chromium( 2817): [INFO:library_loader_hooks.cc(116)] Chromium logging enabled:
level = 0, default verbosity = 0
I/BrowserStartupController( 2817): Initializing chromium process, renderers=0
D/TinyALSA-Audio Hardware( 1855): audio_hw_get_mic_mute(0x4003e938, 0x4126daeb)
D/BluetoothManagerService( 2205): Message: 20
D/BluetoothManagerService( 2205): Added callback: android.bluetooth.IBluetoothMa
[email protected]:true
D/BluetoothAdapter( 2817): 1112752792: getState() : mService = null. Returning
STATE_OFF
D/libEGL ( 2817): loaded /system/lib/egl/libEGL_mali.so
D/libEGL ( 2817): loaded /system/lib/egl/libGLESv1_CM_mali.so
D/libEGL ( 2817): loaded /system/lib/egl/libGLESv2_mali.so
E/ ( 2817): Device driver API match
E/ ( 2817): Device driver API version: 23
E/ ( 2817): User space API version: 23
E/ ( 2817): mali: REVISION=Linux-r3p2-01rel3 BUILD_DATE=Wed Oct 9 21:05:
57 KST 2013
W/chromium( 2817): [WARNINGroxy_service.cc(890)] PAC support disabled because
there is no system implementation
I/chromium( 2817): [INFO:CONSOLE(0)] "Document was loaded from Application Cache
with manifest {URL}
k-core-v40.appcache", source: {URL}
d/sdk/native/sdk-core-v40.html (0)
I/chromium( 2817): [INFO:CONSOLE(0)] "Application Cache Checking event", source:
{URL}
l (0)
I/chromium( 2817): [INFO:CONSOLE(0)] "Application Cache NoUpdate event", source:
{URL}
l (0)
W/chromium( 6284): [WARNINGroxy_service.cc(890)] PAC support disabled because
there is no system implementation
I/chromium( 6284): [INFO:simple_index_file.cc(437)] Simple Cache Index is being
restored from disk.
D/Yamaha-MC1N2-Audio( 1855): yamaha_mc1n2_audio_output_stop()
D/Yamaha-MC1N2-Audio( 1855): yamaha_mc1n2_audio_route_start()
Click to expand...
Click to collapse
I've tried tracing the log files the system automatically creates in the ./system folder, but I couldn't find any useful information except from some deamon crash logs.
I tried resetting the dalvik cache, reinstalling my ROM manually (adb sideload), preforming a complete factory reset and wiping cache partition, and yet it didn't work.
I'm quite sure the issue relates to my phone's battery (which overheated a bit when I used it for a long time), but I'm still not completely sure this is the issue, so I would like to hear your suggestions.
Thanks in advance,
Eden
Eden Campo said:
Hello there,
....
I've tried tracing the log files the system automatically creates in the ./system folder, but I couldn't find any useful information except from some deamon crash logs.
I tried resetting the dalvik cache, reinstalling my ROM manually (adb sideload), preforming a complete factory reset and wiping cache partition, and yet it didn't work.
I'm quite sure the issue relates to my phone's battery (which overheated a bit when I used it for a long time), but I'm still not completely sure this is the issue, so I would like to hear your suggestions.
Thanks in advance,
Eden
Click to expand...
Click to collapse
I also read your logcat or yeah the part of it and it seems all to be fine, normal lines.
I don't own the S2 anymore and I didn't had the issue. But I suggest to try somethings first before buying a new battery.
Try another rom instead of cyanogenmod, Cyanogenmod is supporting Alot of devices and it's not really good specific for devices so I suggest to try one of the roms from the development forums.(Cyanogenmod always have bugs.)
Try to flash back to stock with odin
Try to borrow a battery from a friend and see or you still have the same problem
Remove the battery out of the phone and leave your phone without a battery for like 1-5 minutes.
It could be maybe the battery that it got issues cause the S2 is not the newest phone anymore and hardware also has a lifetime sadly. But your screen goes black and your device goes off right?
Hi,
I am having issues with the Facebook application not letting me log in..
I am having this issue on both Oneplus 3 and a Oneplus 5.
On the logcat i get the the error:
Code:
09-19 14:36:16.343 9693-13345/? W/fb4a.BlueServiceQueue: Exception during service
com.facebook.tigon.tigonutils.TigonErrorException: TigonError(2): TigonLigerErrorDomain(2) AsyncSocketException: connect failed, type = Socket not open, errno = 111 (Connection refused)
at X.1e9.onError(:416738)
at com.facebook.tigon.tigonapi.TigonCallbacksIntegerBufferJavaHelper.onError(:417283)
at com.facebook.common.jniexecutors.NativeRunnable.run(Native Method)
at com.facebook.common.jniexecutors.PooledNativeRunnable.run(:308022)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
at X.1Zd.run(:401648)
at java.lang.Thread.run(Thread.java:764)
Things I have already tried:
Delete app data and cache
Reinstall application
Factory reset device
If i use a proxy (using mitmproxy) it will go through and i get to the screen which says:
Is there anyway i can debug or fix this issue.
"We're sorry, we can't set up English (United Kingdom) at the moment"
Thanks