RAZR XT710 EU
I've had spotty GPS functionality ever since I've switched to the CM10.1 roms which means I had to sometimes restart the phone to get the blinking status icon. But once it was blinking I knew it took a few seconds to lock and I would get some satellites even indoors.
Two weeks ago the GPS stopped working completely, ever since I removed the SIM card. I've tried reinstalling the same ROM, installing other ROMs, doing a clean install on another slot (4.1.2. SPREM) but it just does not want to find any satellites.
I've used GPS Toolbox, Faster GPS and NMEA Decoder to see what it's outputting. On one ROM I was getting some strings with $PMOTO but no NMEA position strings.
The libgps shows an error code which could be either 9 on one ROM or 12 on another:
Code:
D/libgps_GpsMgr( 444): schedGps() mode: 3, tbf: 0, accuracy: 0, perf: 0, pAgps: null
D/libgps ( 444): GpsInterface_stop()
E/libgps ( 444): recv_command_status() : fix returned error code 9
D/libgps_GpsMgr( 444): sched() set mode: 3, tbf: 0
D/libgps ( 444): status_cb: GPS_STATUS_SESSION_END (2)
D/libgps_GpsMgr( 444): schedGps() mode: 0, tbf: 1, accuracy: 0, perf: 0, pAgps: null
D/libgps ( 444): GpsInterface_set_position_mode( 0, 1, 100, 0 )
D/libgps ( 444): GpsInterface_start()
D/libgps_GpsMgr( 444): sched() set mode: 0, tbf: 1
D/GpsLocationProvider( 444): NTP server returned: 1382386872254 (Mon Oct 21 22:21:12 CEST 2013) reference: 36370 certainty: 18 sy
stem time offset: -326353
D/libgps ( 444): GpsInterface_inject_time( 1382386872254, 36370, 18 )
D/libgps ( 444): status_cb: GPS_STATUS_SESSION_BEGIN (1)
V/PhoneStatusBar( 576): setLightsOn(true)
D/libgps ( 444): GpsXtraInterface_inject_xtra_data( 0x41FC6370, 60862 )
......
E/libgps ( 444): recv_command_status() : fix returned error code 12
AFAIK the GPS functionality is on the same chip with WiFi and Bluetooth, both of which work perfectly. Is there any antenna connector that might have come loose? I didn't see any in the ifixit teardown.
Can Matt's utility be used to reset a phone that's non-Verizon? Or should I use RSD?
Fixed by flashing the factory firmware with RSD Lite.
Hi,
I also had a problem with GPS in Russia,
Here is a solution what helped me.
http://forum.xda-developers.com/showthread.php?p=43910953
If you don'thave the gps.omap4.so file, just placed the attached file on system/lib/hw, fix permissions (RWX / R-- / R--) via any root file explorer and reboot.
Click to expand...
Click to collapse
Related
Wifi Calling now working! This is a T-Mobile US only feature as your phone carrier must have the architecture on their end for this to work.
Wifi Calling still uses your minutes as if you were connected to a tower.
Wifi Calling turns off your cellular radio when it's connected. This saves power and will also show -113dB signal.
Wifi Calling also sends SMS and MMS over wifi.
[11/10/10 v1.0]
-fixed kineto_ko kernel module. its now included and loads on bootup, compiled from cyanogenmod-exp kernel
-should make it easier for everyone past and present to get wifi calling up and running.
-temporarily disabled bundled kineto app, it was causing problems so until I figure it out I'm not including it with the update.zip
Thanks to Rsotbiemrptson for getting the Libraries and everything into an update.zip.
Thanks to intersectRaven for the kernel mod's regarding kineto and applying the WiFi PM FAST patch.
Thanks to Myshkinbob for the research and creating PM FAST patch.
To Install
1)If you don't have the 5.08 or 5.12 radio installed you MUST install that first!
2)Download and flash the Wildmonks or intersectraven kernel(before flashing kineto!)from the links below
3)Download and flash kineto-n1-bundle attached below.
4)Download and install MS-HTCVISION-KNT20-02.apk
5)If you install any kernel, 720p hacks or mods it can break wifi calling.. any time you flash an update.zip re-flash the kineto bundle. There are important libraries linked in build.prop that must be in or there will be problems. You can attempt to make a custom build.prop or post in the forum for help.
5)Enjoy!
Known Issues
-Bluetooth - Calls are not being connected to a bluetooth at this time.
-Bootloops on enabling wifi - Update your radio! 5.12 or 5.08 is required.
-After flashing if you still experience call problems it will be necessary to change your setcpu screen off profile to 245min 384max.
-Volume is low
-Sporadic MMS sending problems(APN related)
intersectRaven Kernels
CM Based Kernel 20101108_1328 - http://www.mediafire.com/download.php?4obtdv52efkvece
NON-CM Based Kernel 20101108_1328 - http://www.mediafire.com/download.php?urv9wl2ek0fae9c
wildmonks Kernels
http://forum.xda-developers.com/showthread.php?t=693375
dekips said:
Credit to the G2 OTA Update thread and Stryf3 for the APK extraction. I've installed this but I keep getting "Please wait while connecting to T-Mobile". I figured I'd upload it here for fellow N1's while I played with it.
*Update with logcat:
I/Kineto::main( 312): Kineto: SendAlarmEvent Enter
E/KINETO ( 312): KLOG0A2- ERROR: IBS Msg Q Post: size is too large
E/KINETO ( 312): KLOG0A2- ERROR: Failed to post to Queue
I/Kineto::Receiver( 312): onReceive Exit
D/KIPCapp ( 312): KIPC_SendMessage: len = 1, socket = 0
D/KIPCapp ( 312): Connecting... socket = 53, state = 0
D/KIPCapp ( 312): Address is 127.0.0.1, Port is 45211
E/KIPCapp ( 312): Connect failed 111
E/KINETO ( 312): KLOG103- ganswitch_init - error sending message!
D/KIPCapp ( 312): KIPC_SendMessage: len = 1, socket = 0
D/KIPCapp ( 312): Connecting... socket = 53, state = 0
D/KIPCapp ( 312): Address is 127.0.0.1, Port is 45211
E/KIPCapp ( 312): Connect failed 111
E/KINETO ( 312): KLOG103- ganswitch_init - error sending message!
D/KIPCapp ( 312): KIPC_SendMessage: len = 1, socket = 0
D/KIPCapp ( 312): Connecting... socket = 53, state = 0
D/KIPCapp ( 312): Address is 127.0.0.1, Port is 45211
E/KIPCapp ( 312): Connect failed 111
E/KINETO ( 312): KLOG103- ganswitch_init - error sending message!
D/KIPCapp ( 312): KIPC_SendMessage: len = 1, socket = 0
D/KIPCapp ( 312): Connecting... socket = 53, state = 0
D/KIPCapp ( 312): Address is 127.0.0.1, Port is 45211
E/KIPCapp ( 312): Connect failed 111
E/KINETO ( 312): KLOG103- ganswitch_init - error sending message!
D/KIPCapp ( 312): KIPC_SendMessage: len = 1, socket = 0
D/KIPCapp ( 312): Connecting... socket = 53, state = 0
D/KIPCapp ( 312): Address is 127.0.0.1, Port is 45211
E/KIPCapp ( 312): Connect failed 111
E/KINETO ( 312): KLOG103- ganswitch_init - error sending message!
I/Kineto::Receiver( 312): onReceive Enter
I/Kineto::main( 312): Kineto: SendAlarmEvent Enter
E/KINETO ( 312): KLOG0A2- ERROR: IBS Msg Q Post: size is too large
E/KINETO ( 312): KLOG0A2- ERROR: Failed to post to Queue
I/Kineto::Receiver( 312): onReceive Exit
D/KIPCapp ( 312): KIPC_SendMessage: len = 1, socket = 0
D/KIPCapp ( 312): Connecting... socket = 53, state = 0
D/KIPCapp ( 312): Address is 127.0.0.1, Port is 45211
E/KIPCapp ( 312): Connect failed 111
E/KINETO ( 312): KLOG103- ganswitch_init - error sending message!
D/KIPCapp ( 312): KIPC_SendMessage: len = 1, socket = 0
D/KIPCapp ( 312): Connecting... socket = 53, state = 0
D/KIPCapp ( 312): Address is 127.0.0.1, Port is 45211
E/KIPCapp ( 312): Connect failed 111
E/KINETO ( 312): KLOG103- ganswitch_init - error sending message!
D/KIPCapp ( 312): KIPC_SendMessage: len = 1, socket = 0
D/KIPCapp ( 312): Connecting... socket = 53, state = 0
D/KIPCapp ( 312): Address is 127.0.0.1, Port is 45211
D/KIPCapp ( 312): Connect failed 111
E/KINETO ( 312): KLOG103- ganswitch_init - error sending message!
D/KIPCapp ( 312): KIPC_SendMessage: len = 1, socket = 0
D/KIPCapp ( 312): Connecting... socket = 53, state = 0
D/KIPCapp ( 312): Address is 127.0.0.1, Port is 45211
E/KIPCapp ( 312): Connect failed 111
E/KINETO ( 312): KLOG103- ganswitch_init - error sending message!
E/KINETO ( 312): KLOG0C3- xmk_QueryOSQueue SDL Queue empty : WAIT_FOREVER
E/KINETO ( 312): KLOG0A3- ibs_os_GetMsg: Timeout forever for UKCC qHnd 0x814310a4
D/KIPCapp ( 312): KIPC_SendMessage: len = 1, socket = 0
D/KIPCapp ( 312): Connecting... socket = 53, state = 0
D/KIPCapp ( 312): Address is 127.0.0.1, Port is 45211
E/KIPCapp ( 312): Connect failed 111
E/KINETO ( 312): KLOG103- ganswitch_init - error sending message!
I/Kineto::Receiver( 312): onReceive Enter
I/Kineto::main( 312): Kineto: SendAlarmEvent Enter
Click to expand...
Click to collapse
same here stuck on enabling.....please someone fix...keep us posted please
From the looks of things, there is an underlying app that the Wifi Calling app connects to. Any thoughts?
dekips said:
From the looks of things, there is an underlying app that the Wifi Calling app connects to. Any thoughts?
Click to expand...
Click to collapse
Kineto apk has a oss.html which calls out files used for IPSec VPN connections. I suspect some VPN magic at work.
daijizai said:
Kineto apk has a oss.html which calls out files used for IPSec VPN connections. I suspect some VPN magic at work.
Click to expand...
Click to collapse
It's possible there is a tunnel which it is trying to establish, I'd like to think that it would only do that when the wifi calling is enabled. I'm getting a crazy flow from logcat of it trying to connect even when wifi calling is off and wifi is off.
There is a local daemon or missing piece of software it can't connect to. Is this application in the radio or is it another apk?
Ive stripped it down and am in the process of reading, but it needs to be set to try to connect to something or somewhere, without the datafile that tells it where to connect to it just cycles a connect to localhost
the package just loops trying to connect to 127.0.0.1
Viralblack said:
Ive stripped it down and am in the process of reading, but it needs to be set to try to connect to something or somewhere, without the datafile that tells it where to connect to it just cycles a connect to localhost
the package just loops trying to connect to 127.0.0.1
Click to expand...
Click to collapse
I'm in the process of getting a full update.zip.. no luck tonight so I'm calling it and goin to bed
I want to guess that it *could* possibly be in a host file.... It seems like it is doing a port loopback, to the radio... I assume...
do we have an IRC to talk to the guy that pulled this out of his phone?
It could be in the hosts file. I hope we get this soon, because I have like zero service in my apartment and this will be amazing
iria said:
It could be in the hosts file. I hope we get this soon, because I have like zero service in my apartment and this will be amazing
Click to expand...
Click to collapse
can someone get a line in to the guy(s) that has the file?
same problem
im getting same as everyone else
Here's a quote that might clarify some things:
So here’s the update on yesterday’s reported OTA update to the G2, which brought Wi-Fi calling and mobile hotspot creation to a very small set of users. T-Mobile released this official statement to clarify its position:
“Wi-Fi Calling and tethering Wi-Fi sharing are not currently supported on the T-Mobile G2. T-Mobile knows these features are important to consumers and we’re working to deliver them to G2 users in the future. We have nothing further to announce at this time.”
It’s pretty much what they’ve said before on the subject, and it doesn’t tell us much. It could mean that the update we saw yesterday was just a test and won’t be rolled out to the rest of G2 owners. Or it might be a test sample to see how these features affect data traffic, in order to help T-Mo with pricing. Or maybe they really are rolling it out to everyone and just haven’t put the support feautres, etc. in place yet.
via PhoneScoop by way of TmoNews
Click to expand...
Click to collapse
Just installing the apk won't be enough. There are a few libraries that will be needed as well. The kineto libraries and module(s) will be needed as well. The path to the RIL will have to be redirected also. This is likely changed via the build prop. A full system dump from a WiFi calling equipped G2 would be needed.
I still have not been able to source the original G2 OTA update.zip nor have I any luck finding someone with an updated G2 to pull specifics on the Kineto app configuration. If anyone has any luck with any of the above please post.
dekips said:
I still have not been able to source the original G2 OTA update.zip nor have I any luck finding someone with an updated G2 to pull specifics on the Kineto app configuration. If anyone has any luck with any of the above please post.
Click to expand...
Click to collapse
A co-worker recently obtained a G2. I will see if he has gotten the update, and if so, if he will help us
bennettm89 said:
A co-worker recently obtained a G2. I will see if he has gotten the update, and if so, if he will help us
Click to expand...
Click to collapse
yeah he should have the same problem and once they go online meaning tmobile it will and should automatically configure itself like ota
Weird thing is that I installed this and it actually worked, or at least looked like it worked for a minute. I got a new icon on the taskbar when calling with it enabled, and the call went through fine.
I turned the wifi calling off and then back on and now it is acting like everyone else's now... stuck on enabling.
Not sure if it actually was working for that one call, but it sure seemed like it. Wish I would have thought to grab a screenshot.
I'm stoked. I really need this at home.
Same here. When I originally installed the app, I had WiFi turned on and was at home near my UMA router. Worked fine until I disabled the application and attempted to re-enable it. Now stuck on enabling like everyone else.
Hi all,
I have a t-mobile phone and tried to install android 2.2. there. I used mdeejay's and darkStone's builds, but wifi didn't work at any of them. I've found a person who uses T-mobile hd2 too and installed the same versions of rom and radio. It didn't helped. In windows mobile wifi works well.
Could you please advice how to hande it? Did anyone face the same problem?
Thank you in advance.
#did some debug via adb:
I suppose that the red line below tells about reason.. But I haven't dealt with WPA on android before.. Any help is appreciated.
D/WifiService( 1916): setWifiEnabled( mAirplaneModeOverwridden=)false
I/WifiHW ( 1916): wifi_load_driver enter
D/NetSharing_NSReceiver( 2298): onReceive : android.net.wifi.WIFI_STATE_CHANGED
D/NetSharing( 2298): wifi enabled change, state = false
I/WifiHW ( 1916): wifi_load_driver end right 3
I/WifiHW ( 1916): wifi_start_supplicant enter
I/WifiHW ( 1916): wifi_start_supplicant end right 2
D/WifiService( 1916): ACTION_BATTERY_CHANGED pluggedType: 2
I/wpa_supplicant( 2771): CTRL-EVENT-STATE-CHANGE id=-1 state=0 BSSID=00:00:00:00
:00:00
E/wpa_supplicant( 2771): Failed to disable WPA in the driver.
D/NetSharing_NSReceiver( 2298): onReceive : android.net.wifi.WIFI_STATE_CHANGED
D/NetSharing( 2298): wifi enabled change, state = true
D/PowerManagerService( 1916): New lightsensor value:40, lcdValue:90
D/lights ( 1916): set_light_buttons
D/lights ( 1916): set_light_keyboard
E/SettingsWifiLayer( 2298): Unable to scan for networks
D/SurfaceFlinger( 1916): Layer::setBuffers(this=0x6257a8), pid=2298, w=1, h=1
D/SurfaceFlinger( 1916): Layer::setBuffers(this=0x6257a8), pid=2298, w=1, h=1
D/SurfaceFlinger( 1916): Layer::requestBuffer(this=0x6257a8), index=0, pid=2298,
w=350, h=85 success
E/WifiHW ( 1916): Supplicant not running, cannot connect
E/SettingsWifiLayer( 2298): Unable to scan for networks
D/SurfaceFlinger( 1916): Layer::setBuffers(this=0x4ca268), pid=2298, w=1, h=1
D/SurfaceFlinger( 1916): Layer::setBuffers(this=0x4ca268), pid=2298, w=1, h=1
D/SurfaceFlinger( 1916): Layer::requestBuffer(this=0x4ca268), index=0, pid=2298
w=350, h=85 success
E/WifiHW ( 1916): Supplicant not running, cannot connect
V/WifiStateTracker( 1916): Supplicant died unexpectedly
D/WifiStateTracker( 1916): Reset connections and stopping DHCP
D/NetUtils( 1916): ifc_get_info addr=0 !
D/WifiStateTracker( 1916): Disabling interface
D/WifiService( 1916): setWifiEnabled( mAirplaneModeOverwridden=)false
D/WifiStateTracker( 1916): Reset connections and stopping DHCP
D/NetUtils( 1916): ifc_get_info addr=0 !
D/NetSharing_NSReceiver( 2298): onReceive : android.net.wifi.WIFI_STATE_CHANGED
D/NetSharing( 2298): wifi enabled change, state = true
D/WifiStateTracker( 1916): Disabling interface
I/WifiHW ( 1916): wifi_stop_supplicant enter
I/WifiHW ( 1916): wifi_stop_supplicant end right 1
I/WifiHW ( 1916): wifi_unload_driver enter
I/WifiHW ( 1916): wifi_unload_driver end right 2
D/NetSharing_NSReceiver( 2298): onReceive : android.net.wifi.WIFI_STATE_CHANGED
D/NetSharing( 2298): wifi enabled change, state = false
how to set up MAC address for android builds (except startup.txt)?
Hi again,
I did some search and found that the core of the problem is in getting MAC address for wifi. (as dmsg says). Exactly the same problem was for Touch2, Tilt and other devices (http://forum.xda-developers.com/showthread.php?p=9211659) and it was resolved after they corrected wifi-nvram.txt. This file is responsible for setting up MAC address there, but I couldn't find it at builds for hd2.
if anybody knows what file is used to set up MAC address for wifi, I would be very appreciated.
Thanks!
I believe they just checked for their WiFi mac address from one of the following locations:
Settings->About phone->Status
Wireless & Networks -> WiFi Settings -> Menu Button -> Advanced
Then they edited the nvram.txt file @ /system/lib/hw/wifi/nvram.txt to include the proper MAC address.
Thanks for the answer!
Unfortunatelly wireless settings are not available until wifi is turned on.
I investigated the problem deeper and found that the reason could be in wifi hardware initialization. I did dmesg and saw the following:
wlan: wifi_set_power = 1
htcleo_wifi_power: 1
wlan: wifi_set_carddetect = 1
htcleo_wifi_set_carddetect: 1
mmc0: card_present 1
mmc0: Slot status change detected (0 -> 1)
wlan: Dongle Host Driver, version 4.218.204.2
mmc0: queuing CIS tuple 0x91 length 3
mmc0: new high speed SDIO card at address 0001
wlan: DHD: dongle ram size is set to 294912(orig 294912)
wlan: dhd_bus_rxctl: resumed on timeout
wlan: firmware version: ver
wlan: Return_dpc value is : 0
wlan: stop poll
wlan: dhd_bus_rxctl: resumed on timeout
wlan: dhd_preinit_ioctls: can't get MAC address , error=-110
wlan: dhdsdio_probe: failed
Since in windows mobile wifi does work I used the firmware files from WM: nvram.txt and rtecdc1.bin. As it turned out nvram in android is located in /proc/calibraion. But unfortunatelly it didn't help. So, I think that the problem is in bcm4329.ko driver. I'm not sure why other people with the same hd2 (t-mobile US) and the same ROM/RADIO/Android have no such issue. Perhaps my broadcomm hardware has a problem which is bypassed in windows, but not in Android.
I wonder if there is a way to get more detailed info than dmesg and logcat give (except building andoid sources of course ).
I don't know if it can help, but still, I'll say it anyway.
I think i had the same problem some times ago.
Wifi in android wouln't work, but was perfectly working in winmo.
it seems that if wifi is on in winmo when you boot on android, the wifi device seems to be blocked in some way.
Do you have wifi enabled in winmo? if yes, try to disable it, and boot on android to see if it works.
Hi kushulain,
Thanks for the advice! (I've almost started to build andriod by myself to find out the reason..) Unfortunatelly wifi was turned off when android was booting.
But this is another point to play around. I haven't tried to boot andriod with wifi turned on.
Thanks!
Just tried to boot andriod with wifi turned on. The device hangs at the beginning of the booting (even before screen with 'htc' appears). I think it is connected to my problem.
Did someone have similar problems?
Hey, I have the same problem, did you find any solution ?
Guys have you tried to change the radio part of the phone with a suitable one?
canavaro said:
Hey, I have the same problem, did you find any solution ?
Click to expand...
Click to collapse
hi, I didn't fix it actually due to lack of time. I tried to use wm hw init files in Android, but it didn't help. There is a score of my posts on this forum regarding this topic so you can find exactly what I tried. The funny thing is that WiFi works in wp7.
To stealth21
yes, that was the first thing I tried.
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!
Hi, ive recently bought a phone I9301 (the one with 1.5gb RAM and 4.4.2 kitkat from 12th August)
but the main problem is that the phone happens to restart itself
it does it very often when (i think) something wakes it up from the Deep Sleep (after about 10minutes of doing nothing) like:
- unlocking the phone
- setting the alarm
- receiving a call
sometimes it restarts automatically when i'm not using it
ive checked the android there are no Kernel panic logs left, no crash logs at all
tried to crash the phone while having it connected to the Catlog via USB, but it doesnt go Deep Sleep while charging (so the alarm and calls worked) but managed to crash it once
thats what the CatLog left me with
Code:
10-04 13:31:30.145: E/SMD(225): DCD ON
10-04 13:31:30.345: E/adsprpc(254): vendor/qcom/proprietary/adsprpc/src/listener_android.c:124:listener protocol failure -1
10-04 13:31:30.355: E/adsprpc(254): vendor/qcom/proprietary/adsprpc/src/listener_android.c:128::error: -1: 0 == (nErr = __QAIC_HEADER(adsp_listener_next_invoke)( ctx, nErr, 0, 0, &ctx, &handle, &sc, bufs->inbufs, inBufsAllocated, bufs->inbufLenReqs, MAX_BUFS, bufs->outbufLenReqs, MAX_BUFS))
10-04 13:31:30.365: E/adsprpc(254): vendor/qcom/proprietary/adsprpc/src/listener_android.c:187:listener thread exiting with code -1
10-04 13:31:30.365: E/adsprpc(254): vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:215::error: -1: 0 == (nErr = remotectl_open(name, (int*)ph, dlerrstr, sizeof(dlerrstr), &dlerr))
10-04 13:31:30.375: E/adsprpc(254): vendor/qcom/proprietary/adsprpc/src/listener_android.c:189:listener thread failed to cleanly shutdown. This is ok durring process exit.
10-04 13:31:30.375: E/adsprpc(254): vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:215::error: -1: 0 == (nErr = remotectl_open(name, (int*)ph, dlerrstr, sizeof(dlerrstr), &dlerr))
10-04 13:31:30.375: E/adsprpc(254): vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:215::error: -1: 0 == (nErr = remotectl_open(name, (int*)ph, dlerrstr, sizeof(dlerrstr), &dlerr))
10-04 13:31:30.375: E/adsprpc(254): vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:215::error: -1: 0 == (nErr = remotectl_open(name, (int*)ph, dlerrstr, sizeof(dlerrstr), &dlerr))
10-04 13:31:30.385: E/adsprpc(254): vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:215::error: -1: 0 == (nErr = remotectl_open(name, (int*)ph, dlerrstr, sizeof(dlerrstr), &dlerr))
: E/(): Device disconnected
(look at the bottom), i guess nothing special, however didnt find time to check what the remotectl_open function does in detail
its been to the Warranty 2 times, first time they 're' flashed the firmware, but the problem remained, tried disabling tons of built-in apps, hard reset, nothing works
second time they said theres nothing to do and all i have to do is just wait for the release of firmware update,
any ideas whats wrong with the phone?
I have been having Wifi problems with my Z2 for a while and decided to try and flash this.
I'm not 100% sure if this is the culprit or not but I have been having worse issues since.
Wifi seems to be stable but;
Bluetooth disconnects and reconnects intermittently, noticeable as Sleep for Android loses sync with my Garmin midway through the night
If Wifi has been connected for a while and I head out and lose Wifi connection, my mobile data stays off and won't come back on until I hard reset my phone.
I'm currently running Resurrection Remix N for Xperia Z2.
I'm guessing I'll need to do a logcat for both instances?
logcat
I believe it's around line 133;
Code:
09-02 12:29:41.496 D/ConnectivityService(1305): handleLingerComplete for NetworkAgentInfo [MOBILE (LTE) - 104]
09-02 12:29:41.500 D/DcNetworkAgent(2931): NetworkAgent: NetworkAgent channel lost
09-02 12:29:41.500 D/DcNetworkAgent(2931): NetworkAgent: DcNetworkAgent: [unwanted]: disconnect apnContext={mApnType=default mState=CONNECTED mWaitingApns={[[ApnSettingV3] Telstra Internet, 2937, 50501, telstra.wap, , , , , , -1, default | supl, IP, IP, true, 0, 0, 0, false, 0, 0, 0, 0, , , false]} mApnSetting={[ApnSettingV3] Telstra Internet, 2937, 50501, telstra.wap, , , , , , -1, default | supl, IP, IP, true, 0, 0, 0, false, 0, 0, 0, 0, , , false} mReason=dataDisabled mDataEnabled=false mDependencyMet=true}
09-02 12:29:41.511 D/ConnectivityService(1305): NetworkAgentInfo [MOBILE (LTE) - 104] got DISCONNECTED, was satisfying 9
09-02 12:29:41.554 I/libmdmdetect(334): ESOC framework not supported
09-02 12:29:41.555 E/libmdmdetect(334): Found internal modem: modem
09-02 12:29:41.556 I/libmdmdetect(334): ESOC framework not supported
09-02 12:29:41.556 E/libmdmdetect(334): Found internal modem: modem
09-02 12:29:41.591 I/libmdmdetect(334): ESOC framework not supported
09-02 12:29:41.592 E/libmdmdetect(334): Found internal modem: modem
09-02 12:29:41.613 W/ConnectivityExtension(1305): ConnectivityExt jar file not present