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
Related
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
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?
Hello,
I recently bought on Internet a cheap tablet (REF : LAZER MD1005). Since, it was used, I did a factory reset in order to clean all the data of the previous owner. However, when it rebooted, the screen stopped working. I don't think it's an hardware problem, since it worked fine before. I'm not very aware of how android works, but I thought some drivers could have been deleted, is that possible ?
Here you'll find all the info I grabbed :
Brand : Lazer
Model : MD1005
Android Version : 4.1.1
Kernel Version : 3.0.8
Build number : JRO03C.20130412.v008
Touch Screen Controller : CHIPONE ICN8305M
> When I type 'logcat | grep EventHub' it tells me that there is on event6 a device named 'chipone-ts', but that it has no configuration file.
> Here is what I get with getevent -p
Code:
add device 2: /dev/input/event6
name: "chipone-ts"
events:
KEY (0001): 0066 008b 009e 00d9
ABS (0003): 002f : value 0, min 0, max 254, fuzz 0, flat 0, resolution 0
0030 : value 0, min 0, max 255, fuzz 0, flat 0, resolution 0
0032 : value 0, min 0, max 255, fuzz 0, flat 0, resolution 0
0035 : value 0, min 0, max 1024, fuzz 0, flat 0, resolution 0
0036 : value 0, min 0, max 600, fuzz 0, flat 0, resolution 0
0039 : value 0, min 0, max 255, fuzz 0, flat 0, resolution 0
input props:
INPUT_PROP_DIRECT
Do you think there is any way to fix this ? Thanks for your help !
You can try to flash your original rom !!!
Sent from my XT1022 using Tapatalk
androidrocks23 said:
You can try to flash your original rom !!!
Sent from my XT1022 using Tapatalk
Click to expand...
Click to collapse
Thank you for your reply.
Indeed, that would be a good idea.
However this tablet is so rare that I did not manager to find any original rom.
Hi.
I am using xt912 gsm prepaid sim India.
I am facing problem with ussd code for checking my balance and other think.
Like *111# not working.
I tried CM12.1 and AOKP
But same problem.
Can any one fix this ?
Or give me any other rom 4.4 or 4.1
Thanks .
Use ES File Manager or any other file manager that supports root and navigate to /system and open your build.prop, scroll to the last line and leave about two spaces(that is hit enter twice) and paste this..
Code:
# General GSM Settings
telephony.lteOnGsmDevice = 1
telephony.lteOnCdmaDevice = 0
telephony.rilV7NeedCDMALTEPhone = false
persist.ril.mux.noofchannels = 10
persist.ril.modem.mode = 2
persist.ril.features = 0x102
persist.radio.vzw.cdma.mdn = deleted
persist.radio.ap.phonetype = 1
persist.radio.lte.mm.disable = 1
ro.telephony.default_network = 3
ro.telephony.gsm-routes-us-smsc = 0
ro.telephony.ril.v3 = writeaidonly, signalstrength
ro.cdma.data_retry_config = default_randomization=2000, 0, 0, 120000, 180000, 540000, 960000
ro.gsm.data_retry_config = max_retries=infinite, default_randomization=2000, 0, 0, 80000, 125000, 485000, 905000
ro.cdma.subscribe_on_ruim_ready = false
# Motorola GSM Settings
ro.mot.eri = 0
ro.mot.phonemode.vzwglobalphone = 0
ro.mot.phonemode.vzw4gphone = 0
ro.mot.lte_on_cdma = 0
ro.mot.ds.fastdormancy.disable = true
Now save it, close the build.prop and reboot your device.
Thanks, it's work for me. I'm using Droid Razr in Bangladesh. I'd also tried lots of Customs Rom including CM 12.1 but none works about ussd problem.
Sr My English is very bad
I've been running Nexus v4.0.5 on my Apollo device. The issue is my kindle start to rebooting or turning off after entering sleep mode I wanted to try another rom, but I'm not sure it could help
What is the problem ?Please help.
Sigosuuu said:
Sr My English is very bad
I've been running Nexus v4.0.5 on my Apollo device. The issue is my kindle start to rebooting or turning off after entering sleep mode I wanted to try another rom, but I'm not sure it could help
What is the problem ?Please help.
Click to expand...
Click to collapse
Nexus v4.0.5 is very old and is no longer supported. Suggest installing the immediate successor (Fire Nexus) which you can do without loss of data.
Is the device running Safestrap?
Davey126 said:
Nexus v4.0.5 is very old and is no longer supported. Suggest installing the immediate successor (Fire Nexus) which you can do without loss of data.
Is the device running Safestrap?
Click to expand...
Click to collapse
I installed (Fire Nexus) but the issue not fix :crying::crying::crying::crying::crying::crying::crying:
Sigosuuu said:
I installed (Fire Nexus) but the issue not fix :crying::crying::crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
Likely an app. You will need to use a tool like GSAM or BBS to identify the culprit.
My Apollo HDX behaves similarly, and has since I got it (refurbished) six months ago: very shortly after going into screen-off mode, a reboot occurs.
This happened under the stock 4.5.5.2 OS, but seemed to be mitigated if I set it to keep wifi on during sleep.
Under LineageOS 14.1, however, it reboots whether that option is enabled or disabled.
I've tried several times to see if anything interesting appears via wireless logcat, but nothing is terribly obvious. Here's the last attempt:
Code:
07-03 01:59:19.246 1157 1234 E WifiHAL : wifi_error acquire_supported_features(wifi_interface_handle, feature_set *): requestResponse Error:-95
07-03 01:59:19.247 1157 1540 E BatteryStatsService: no controller energy info supplied
07-03 01:59:19.247 1157 1540 E BatteryStatsService: no controller energy info supplied
07-03 01:59:19.248 1567 1567 E PhoneInterfaceManager: [PhoneIntfMgr] queryModemActivityInfo: Empty response
07-03 01:59:19.257 1157 1540 E BatteryStatsService: modem info is invalid: ModemActivityInfo{ mTimestamp=0 mSleepTimeMs=0 mIdleTimeMs=0 mTxTimeMs[]=[0, 0, 0, 0, 0] mRxTimeMs=0 mEnergyUsed=0}
07-03 01:59:20.383 544 884 D audio_hw_primary: out_standby: enter: stream (0xb624ab00) usecase(1: low-latency-playback)
07-03 01:59:20.489 544 884 D hardware_info: hw_info_append_hw_type : device_name = speaker
After that, the device no longer pings as it has begun restarting.
Using Wake Lock (https://play.google.com/store/apps/details?id=eu.thedarken.wl), I found certain combinations that would prevent reboots when the screen goes off:
wifi on, wakelock WIFI_MODE_FULL_HIGH_PERF => ok
wifi on, wakelock WIFI_MODE_FULL (or less) => *restart on sleep*
wifi off, wakelock PARTIAL_WAKELOCK => ok
wifi off, wakelock WIFI_MODE_FULL_HIGH_PERF (or less) => *restart on sleep*
airplane mode, no wakelock => ok
Seems almost like some sort of hardware/driver issue.