Database Develop

my wifi disconnect and reconnect itself ?

this is the log :
false
E/ConnectivityService( 1488): not failing over to mobile type 0 because Mobile Data Disabled
D/ConnectivityService( 1488): Dropping ConnectivityChange for WIFI: DISCONNECTED/SCANNING
help plz

Did you root your phone, flash ROM/kernel or change any system settings before this happened?
Sent from my CM7 GT-S5570I

[Q] Radio (gsm) turned off when 3g is enabled

Hi,
I've been using cyanogenmod in my p880 for a while now and it worked pretty well until last weekend when it started loosing radio (gsm) signal.
After a while I noticed that when I was home, connected to wifi, it didn't occur.
Testing a little bit I found out that the problem was in the 3g. If I set the phone to use only 2g it works, but when I switch to 3g it looses the radio signal after a minute and does not work again until reboot.
The phone gets hot and the battery consumption increases a lot. In the battery status it shows that the "Phone" app's cpu time in "real time", like 100% usage, even with no calls at all..
I'm currently using nightly builds of CM 11, but I flashed the stable CM10 (with factory reset, data wipe) and the problem persisted. Then I flashed the latest nightly again, after another reset/wipe.
To use logcat I turned on the phone using only 2g, started logcat and when switched to 3g. The complete log can be found here:
https://drive.google.com/file/d/0B29xKdkT5wYzZmhleFZlcUhYc28/edit?usp=sharing
It was the first time I saw a logcat file, so I'm not sure, but I found some relevant things:
05-19 17:34:28.263 D/MobileDataStateTracker( 531): default: Broadcast received: android.intent.action.ANY_DATA_STATE apnType=default
05-19 17:34:28.263 D/MobileDataStateTracker( 531): default: Received state=CONNECTED, old=CONNECTED, reason=(unspecified)
05-19 17:34:28.273 E/MobileDataStateTracker( 531): default: unknown network type: 0
05-19 17:34:28.313 E/ConnectivityService( 531): net.tcp.usercfg.default not found in system properties. Using defaults
05-19 17:34:28.313 E/ConnectivityService( 531): net.tcp.delack.default not found in system properties. Using defaults
05-19 17:34:28.323 D/MobileDataStateTracker( 531): supl: Broadcast received: android.intent.action.ANY_DATA_STATE apnType=supl
05-19 17:34:28.323 D/MobileDataStateTracker( 531): supl: Received state=DISCONNECTED, old=DISCONNECTED, reason=radioTurnedOff
I hope someone can help me so I can use 3g again...
Thanks

check the settings for your apn
try with another kernel
Does this happen with absolutely no apps installed? (i.e fresh install?)

So I am not alone
hsafenix said:
Hi,
I've been using cyanogenmod in my p880 for a while now and it worked pretty well until last weekend when it started loosing radio (gsm) signal.
After a while I noticed that when I was home, connected to wifi, it didn't occur.
Testing a little bit I found out that the problem was in the 3g. If I set the phone to use only 2g it works, but when I switch to 3g it looses the radio signal after a minute and does not work again until reboot.
The phone gets hot and the battery consumption increases a lot. In the battery status it shows that the "Phone" app's cpu time in "real time", like 100% usage, even with no calls at all..
I'm currently using nightly builds of CM 11, but I flashed the stable CM10 (with factory reset, data wipe) and the problem persisted. Then I flashed the latest nightly again, after another reset/wipe.
To use logcat I turned on the phone using only 2g, started logcat and when switched to 3g. The complete log can be found here:
https://drive.google.com/file/d/0B29xKdkT5wYzZmhleFZlcUhYc28/edit?usp=sharing
It was the first time I saw a logcat file, so I'm not sure, but I found some relevant things:
05-19 17:34:28.263 D/MobileDataStateTracker( 531): default: Broadcast received: android.intent.action.ANY_DATA_STATE apnType=default
05-19 17:34:28.263 D/MobileDataStateTracker( 531): default: Received state=CONNECTED, old=CONNECTED, reason=(unspecified)
05-19 17:34:28.273 E/MobileDataStateTracker( 531): default: unknown network type: 0
05-19 17:34:28.313 E/ConnectivityService( 531): net.tcp.usercfg.default not found in system properties. Using defaults
05-19 17:34:28.313 E/ConnectivityService( 531): net.tcp.delack.default not found in system properties. Using defaults
05-19 17:34:28.323 D/MobileDataStateTracker( 531): supl: Broadcast received: android.intent.action.ANY_DATA_STATE apnType=supl
05-19 17:34:28.323 D/MobileDataStateTracker( 531): supl: Received state=DISCONNECTED, old=DISCONNECTED, reason=radioTurnedOff
I hope someone can help me so I can use 3g again...
Thanks
Click to expand...
Click to collapse
+1 here
I believe that it all started around 0427 Nightly, not sure, though.
I thought of switching to 2g network only yesterday after reading an old post in CM forums.
Did not have time to pull a logcat, yet, thanks for sharing! Hope somebody will figure out what the problem can be...

Rudjgaard said:
check the settings for your apn
try with another kernel
Does this happen with absolutely no apps installed? (i.e fresh install?)
Click to expand...
Click to collapse
My settings are as per wind IT specifications, but I noticed that in CM settings there is much more than specified by Wind, such as apn protocol, apn roaming protocol and bearer, which values are unknown to me. Will investigate on those values.
Tried also with official CM11 stock kernel, with no success.
No, I did not try with no apps installed, I will keep this test as the very last resort. I did not install new apps since when the problem started.
Inviato dal mio GT-P3110 utilizzando Tapatalk

Rudjgaard said:
check the settings for your apn
try with another kernel
Does this happen with absolutely no apps installed? (i.e fresh install?)
Click to expand...
Click to collapse
I checked the apn settings and they are ok..
It happened with a fresh install as well, when I fleshed CM10.
I didn't try another kernel yet, but Ottonet did and it did not solve the problem

SignalStrength: Hotfix TD-SCDMA
There could be some interesting news for those like me who are affected by network losses when in 3G.
One of the commits that will be compiled in tomorrow nightly amends misbehaviours in Android/telephony/SignalStrength.java
This is "Take 2".
https://github.com/CyanogenMod/andr...mmit/94186f84815c8f179ebee6b1d07b086fd06af489
The first attempt was made (so far as I was able to reconstruct) on April 28th, see here
https://gitorious.org/cyandreamproj...mmit/cbd9cf1fa383ea588a5a445306534c01f8aa1ca8
I believe I've had 3g issues since the end of april.
Now, I'm not android developer at all, and I would not like to arise too much xpectations or to get overexcited about something that has nothing to do with network losses when in 3g, so I would really appreciate if somebody more skilled than me would provide some comment/explanations.
[EDIT] it turned out that it was *today's nightly*, so, if there is some improvement, it can be enjoyed right away.
Downloading...
[EDIT 05232014] No joy. Whataver it did that fix, it did not solve the network loss issue.

Ottonet said:
There could be some interesting news for those like me who are affected by network losses when in 3G.
One of the commits that will be compiled in tomorrow nightly amends misbehaviours in Android/telephony/SignalStrength.java
This is "Take 2".
https://github.com/CyanogenMod/andr...mmit/94186f84815c8f179ebee6b1d07b086fd06af489
The first attempt was made (so far as I was able to reconstruct) on April 28th, see here
https://gitorious.org/cyandreamproj...mmit/cbd9cf1fa383ea588a5a445306534c01f8aa1ca8
I believe I've had 3g issues since the end of april.
Now, I'm not android developer at all, and I would not like to arise too much xpectations or to get overexcited about something that has nothing to do with network losses when in 3g, so I would really appreciate if somebody more skilled than me would provide some comment/explanations.
[EDIT] it turned out that it was *today's nightly*, so, if there is some improvement, it can be enjoyed right away.
Downloading...
[EDIT 05232014] No joy. Whataver it did that fix, it did not solve the network loss issue.
Click to expand...
Click to collapse
Just confirming, I also installed the last nightly (05-24) and the problem persists.

Does anyone think it could be a hardware problem?

hsafenix said:
Does anyone think it could be a hardware problem?
Click to expand...
Click to collapse
Hi..the problem still persists (I'm on Wind). I've always used Vanir, now I switched to official Cyanogen Nightly...still nothing happens

Hi. I had cellular network problems (no signal) in omni ROM and cm official too. Anyone tryed changing base band? I have v20a EUR ... Anyone tryed different?
Inviato dal mio LG-P880 utilizzando Tapatalk

I'm posting some modem.log , hoping it's not against forum rules (can remove if it is)
06-12 15:28:24.105 D/GsmDCT ( 896): overall state is CONNECTED
06-12 15:28:24.105 D/GsmDCT ( 896): startDataStallAlarm: tag=61578 delay=60s
06-12 15:30:00.745 D/use-Rlog/RLOG-RILC( 151): rild: grabPartialWakeLock, s_wakeup_lock_flag - 0
06-12 15:30:00.745 D/use-Rlog/RLOG-RILC( 151): rild: wakelock acquired
06-12 15:30:00.745 D/use-Rlog/RLOG-RILC( 151): [UNSL]< _LGE_RESTART_RILD {AT Command Timeout}
06-12 15:30:00.745 D/use-Rlog/RLOG-AT( 151): dlc[12] atchannel: at_send_command_full() end; err:-4
06-12 15:30:00.745 D/use-Rlog/RLOG-RILC( 151): [1666]< DATA_CALL_LIST fails by E_REQ_TIMEOUT
06-12 15:30:00.745 D/use-Rlog/RLOG-RIL( 151): dlc[12] lge-ril: requestInterface(DATA_CALL_LIST) invoking *requestFunction(req:57, data: 0x00000000, len:0)...DONE
06-12 15:30:00.745 D/use-Rlog/RLOG-RIL( 151): dlc[12]: lge-ril - requestInterface: Exiting DLC handler, thread - 1074013352. s_dlc_handler_create_tracker - 0x301ff
06-12 15:30:00.755 D/RILJ ( 896): *********RILJ: LgeRestartRild Start
06-12 15:30:00.755 D/RILJ ( 896): ### Show RIL Recovery popup ###
06-12 15:30:00.825 E/RILJ ( 896): Uncaught exception read length=52Exception:java.lang.NullPointerException
06-12 15:30:00.825 I/RILJ ( 896): Disconnected from 'rild' socket
06-12 15:30:00.825 D/PHONE ( 896): [ServiceState] setNullState=1
06-12 15:30:00.825 D/GsmSST ( 896): [GsmSST] Poll ServiceState done: oldSS=[0 0 home I WIND I WIND 22288 UMTS UMTS CSS not supported -1 -1 RoamInd=-1 DefRoamInd=-1 EmergOnly=false] newSS=[1 1 home null null null Unknown Unknown CSS not supported -1 -1 RoamInd=-1 DefRoamInd=-1 EmergOnly=false] oldMaxDataCalls=1 mNewMaxDataCalls=1 oldReasonDataDenied=-1 mNewReasonDataDenied=-1
06-12 15:30:00.825 D/GsmSST ( 896): [GsmSST] RAT switched UMTS -> Unknown at cell -1
06-12 15:30:00.825 D/PHONE ( 896): [ServiceState] setNullState=1
06-12 15:30:00.825 D/PhoneProxy( 896): [PhoneProxy] updatePhoneObject: radioTechnology=0
06-12 15:30:00.825 E/use-Rlog/RLOG-RILC( 151): error on reading command socket errno:104
06-12 15:30:00.825 D/GsmSST ( 896): [GsmSST] Iwlan feature available = false
06-12 15:30:00.825 D/RilRequest( 896): [5314]< DATA_CALL_LIST error: com.android.internal.telephony.CommandException: RADIO_NOT_AVAILABLE ret=null
06-12 15:30:00.835 I/use-Rlog/RLOG-RILC( 151): libril: new connection
06-12 15:30:00.835 D/use-Rlog/RLOG-RILC( 151): rild: grabPartialWakeLock, s_wakeup_lock_flag - 1
06-12 15:30:00.835 D/use-Rlog/RLOG-RILC( 151): [UNSL]< UNSOL_RIL_CONNECTED {7}
06-12 15:30:00.835 D/use-Rlog/RLOG-RILC( 151): rild: grabPartialWakeLock, s_wakeup_lock_flag - 1
06-12 15:30:00.835 D/use-Rlog/RLOG-RILC( 151): [UNSL]< UNSOL_RESPONSE_RADIO_STATE_CHANGED {RADIO_SIM_READY}
06-12 15:30:00.835 I/use-Rlog/RLOG-RILC( 151): RIL Daemon version: android lge-ril 1.0
06-12 15:30:00.835 I/RILJ ( 896): Connected to 'rild' socket
06-12 15:30:00.865 D/GsmSST ( 896): [GsmSST] updateSpnDisplay: radio is on but out of service, set plmn='Nessun servizio.'
06-12 15:30:00.865 D/RILJ ( 896): [UNSL]< UNSOL_RIL_CONNECTED {7}
06-12 15:30:00.865 D/RILJ ( 896): [0213]> RADIO_POWER off
06-12 15:30:00.865 D/GsmSST ( 896): [GsmSST] updateSpnDisplay: changed sending intent rule=2 showPlmn='true' plmn='Nessun servizio.' showSpn='false' spn=''
06-12 15:30:00.885 D/RILJ ( 896): [0214]> REQUEST_SET_PREFERRED_NETWORK_TYPE : 0
06-12 15:30:00.885 D/use-Rlog/RLOG-RILC( 151): [1363036565]> RADIO_POWER (0)
06-12 15:30:00.885 D/use-Rlog/RLOG-RILC( 151): [1363036565]< RADIO_POWER fails by E_RAIDO_NOT_AVAILABLE
Inviato dal mio LG-P880 utilizzando Tapatalk

I have additionally extreme battery consumption.

I have this problem too.
With Resurrection Remix (CM 11 based) and Wind IT....

complete logs
Happened today, gathered all the logs i could. Kernel dmesg, modem log And main log.
All with official CM11 from 17/06. But it's the same on other cm11 based.
Time is:
<4>[14:06:18 18:49:45.571] ##@acm_read_bulk !ACM_READY
<4>[14:06:18 18:49:45.581] **************************
<4>[14:06:18 18:49:45.581] !!!!! ts_ldisc_close !!!!!
<4>[14:06:18 18:49:45.581] **************************
<4>[14:06:18 18:49:45.581] ### CP Crash : 1, USB DISCONNECT : 0 ###

I have the same problem as well, it started around 2 - 3 weeks ago, I was on beanstalk 4.4.2, a build from march, if I remember correctly. I had no issues before, but suddenly I lost signal every time on 3G. I tried several Roms with and without the RIL-Patch by Flying_Bear, but nothing helped so far. The only "workaround" is to stay on 2G. I'm starting to get tired of constantly reflashing my phone to try other Roms.
Its strange, that the same error occurred around the same time for so many people. I would like to know if it also happens on stock, or if its a special hardware-revision that fails. My phone version is SWS-Black (Swiss market, but bought in Germany).

It looks like something in the connection behavior got changed. When using earlier nightlies you could observe the phone connecting via HSPA+ (H+) everytime it was possible. But in later builds the phone only connects via HSPA+ if you actively use mobile data and changes back the connection to HSDPA (H) afterwards, thus resulting in constant changes between those network types. I believe this change was included to save battery but it really doesn't if your phone constantly loses connection and you have to reboot. Maybe this change was a global one but as you can see our phone can't handle it. Hopefully demetris can either identify that change and revert it or fix it.

@rob3110 , i understand your frustration, i'm changing ROM too. I also did try EPRJ RIL without success. Now I'm experimenting a RIL from CM 10.2. It seems no Dev is looking into it, it's a pity. I'm trying to analyze error logs but I'm no real Dev... You can post your logs if you like
Inviato dal mio LG-P880 utilizzando Tapatalk

Right now I'm trying the strange bug-fix JustChris20 posted in the EPJR-RIL-fix thread:
http://forum.xda-developers.com/showpost.php?p=53015495&postcount=105
1. install your rom of your choice.
don't modify anything, no ril, nothing...
2. shutdown your system and remove your battery. Now press the power button for 30 seconds. Wait further one minute. Now insert your battery back and start handy. enjoy your network... ?
Click to expand...
Click to collapse
(But without flashing a new Rom) So far I haven't lost connection for the last hours, but it is to early to be certain. I'll have to test it for at least some days or weeks to know, if it helped permanently. Maybe it helps others as well.
Just for interest, what carriers are those on with this error, or what countries are they from? Does it only happen in Europe (I'm from Germany)? If so, what happened, did something change with the hsdpa or hsdpa+ networks? Or does this error occur all over the world?

rob3110 said:
Right now I'm trying the strange bug-fix JustChris20 posted in the EPJR-RIL-fix thread:
http://forum.xda-developers.com/showpost.php?p=53015495&postcount=105
(But without flashing a new Rom) So far I haven't lost connection for the last hours, but it is to early to be certain. I'll have to test it for at least some days or weeks to know, if it helped permanently. Maybe it helps others as well.
Just for interest, what carriers are those on with this error, or what countries are they from? Does it only happen in Europe (I'm from Germany)? If so, what happened, did something change with the hsdpa or hsdpa+ networks? Or does this error occur all over the world?
Click to expand...
Click to collapse
I am having the same troubles and I am also from Germany (carrier: simyo).
I did follow your instructions and will report if it worked or not.
Edit: today I did have another disconnect, so unfortunately this rather easy "fix" didn't work out (at least for me).
Hopefully someone finds another sollution.

rootarded said:
I am having the same troubles and I am also from Germany (carrier: simyo).
I did follow your instructions and will report if it worked or not.
Edit: today I did have another disconnect, so unfortunately this rather easy "fix" didn't work out (at least for me).
Hopefully someone finds another sollution.
Click to expand...
Click to collapse
Yeah, didn't work for me either. I still get those disconnects on 3G. I will ask my carrier (E-Plus) if there was a recent change to the 3G-network that might have brought us this error, but I don't think they will give me a useful answer...

[Q] Firmware update - "Something went wrong"

Hi there. Just got my Gear Live today from Google Play(ordered on 14 July), firmware build is KKV81. When I try to update the firmware from the settings it just says "Something went wrong". Has anyone encountered the same problem? Any ideas how to fix this? I suppose my other option is to update the firmware via adb as described here: http://forum.xda-developers.com/showthread.php?t=2797501, but some steps are not detailed enough so I would like to try something less dangerous first.
Thanks in advance.

apan1982 said:
Hi there. Just got my Gear Live today from Google Play(ordered on 14 July), firmware build is KKV81. When I try to update the firmware from the settings it just says "Something went wrong". Has anyone encountered the same problem? Any ideas how to fix this? I suppose my other option is to update the firmware via adb as described here: http://forum.xda-developers.com/showthread.php?t=2797501, but some steps are not detailed enough so I would like to try something less dangerous first.
Thanks in advance.
Click to expand...
Click to collapse
The same situation!
My firmware build is KKV81, same as yours, and also can't update with OTA to the latest version
And this is in logcat output, while trying to update:
Code:
08-07 20:06:40.620 606-606/? I/SystemUpdateService﹕ onCreate
08-07 20:06:41.660 454-569/? I/ActivityManager﹕ START u0 {act=android.settings.SYSTEM_UPDATE_SETTINGS cmp=com.google.android.gms/.update.SystemUpdateWearableActivity} from pid 619 on display 0
08-07 20:06:41.720 606-606/? D/SystemUpdateActivity﹕ status=6 mobile=false batteryState=0 roaming=false lastCheckinTime=1407349343493 mSetupWizard=false
08-07 20:06:41.780 454-474/? I/ActivityManager﹕ Displayed com.google.android.gms/.update.SystemUpdateWearableActivity: +105ms
08-07 20:06:42.000 662-682/? W/bt-btif﹕ dm_pm_timer expires
08-07 20:06:42.000 662-682/? W/bt-btif﹕ dm_pm_timer expires 0
08-07 20:06:42.000 662-682/? W/bt-btif﹕ proc dm_pm_timer expires
08-07 20:06:43.620 606-606/? I/SystemUpdateService﹕ onCreate
08-07 20:06:43.650 606-1692/? I/SystemUpdateService﹕ network: NetworkInfo: type: PROXY[], state: CONNECTED/CONNECTED, reason: enabled, extra: (none), roaming: false, failover: false, isAvailable: true, isConnectedToProvisioningNetwork: false; metered: false; mobile allowed: true
08-07 20:06:43.650 606-1692/? I/DownloadAttempt﹕ current file is null
08-07 20:06:43.650 606-1692/? I/DownloadAttempt﹕ mSize -1 mDownloaded -1
08-07 20:06:43.650 606-1692/? I/SystemUpdateService﹕ status is 1 (ready)
08-07 20:06:43.650 606-1692/? I/SystemUpdateService﹕ starting download of http://android.clients.google.com/packages/ota/global_samsung_sprat/9463bb9866a01116311155b89e4aae4c436db98c.signed-sprat-KMV78Y-from-KKV81.9463bb98.zip
08-07 20:06:43.660 606-606/? D/SystemUpdateActivity﹕ status=2 mobile=false batteryState=0 roaming=false lastCheckinTime=1407349343493 mSetupWizard=false
08-07 20:06:43.660 606-1692/? I/SystemUpdateService﹕ now status is 2 (in_progress)
08-07 20:06:43.670 606-1693/? I/DownloadAttempt﹕ querying downloadmanager
08-07 20:06:43.690 606-1693/? I/DownloadAttempt﹕ mUrl is http://android.clients.google.com/packages/ota/global_samsung_sprat/9463bb9866a01116311155b89e4aae4c436db98c.signed-sprat-KMV78Y-from-KKV81.9463bb98.zip
08-07 20:06:43.700 606-1693/? I/DownloadAttempt﹕ including auth header <AUTH_HEADER_HEAR>...
08-07 20:06:43.710 606-1694/? I/SystemUpdateService﹕ network: NetworkInfo: type: PROXY[], state: CONNECTED/CONNECTED, reason: enabled, extra: (none), roaming: false, failover: false, isAvailable: true, isConnectedToProvisioningNetwork: false; metered: false; mobile allowed: true
08-07 20:06:43.710 606-1694/? I/SystemUpdateService﹕ now status is 2 (in_progress)
08-07 20:06:44.690 168-169/? E/clockwork_proxy_native﹕ Cannot find uid for tcp connection from 192.168.167.239:44849 to 212.0.195.142:80
08-07 20:06:44.690 1378-1453/? D/ClockworkProxy﹕ TCP connection requested by uid=-1
08-07 20:06:44.690 1378-1453/? D/ClockworkProxy﹕ TCP connection is not from a google app, closing it...
08-07 20:06:44.700 606-1693/? I/DownloadAttempt﹕ caught ioexception
java.io.EOFException
at com.android.okhttp.internal.Util.readAsciiLine(Util.java:342)
at com.android.okhttp.internal.http.RawHeaders.fromBytes(RawHeaders.java:311)
at com.android.okhttp.internal.http.HttpTransport.readResponseHeaders(HttpTransport.java:135)
at com.android.okhttp.internal.http.HttpEngine.readResponse(HttpEngine.java:644)
at com.android.okhttp.internal.http.HttpURLConnectionImpl.execute(HttpURLConnectionImpl.java:353)
at com.android.okhttp.internal.http.HttpURLConnectionImpl.getResponse(HttpURLConnectionImpl.java:297)
at com.android.okhttp.internal.http.HttpURLConnectionImpl.getResponseCode(HttpURLConnectionImpl.java:509)
at apc.b(SourceFile:328)
at apc.doInBackground(SourceFile:44)
at android.os.AsyncTask$2.call(AsyncTask.java:288)
at java.util.concurrent.FutureTask.run(FutureTask.java:237)
at java.lang.Thread.run(Thread.java:841)
08-07 20:06:44.710 606-1697/? I/SystemUpdateService﹕ network: NetworkInfo: type: PROXY[], state: CONNECTED/CONNECTED, reason: enabled, extra: (none), roaming: false, failover: false, isAvailable: true, isConnectedToProvisioningNetwork: false; metered: false; mobile allowed: true
08-07 20:06:44.710 606-1697/? I/SystemUpdateService﹕ now status is 5 (failed)
08-07 20:06:44.730 606-606/? D/SystemUpdateActivity﹕ status=6 mobile=false batteryState=0 roaming=false lastCheckinTime=1407349343493 mSetupWizard=false
08-07 20:06:44.730 606-1697/? I/SystemUpdateService﹕ download failed; clearing attempt
08-07 20:06:44.750 606-610/? D/dalvikvm﹕ GC_CONCURRENT freed 298K, 9% free 6140K/6724K, paused 3ms+11ms, total 41ms
08-07 20:06:44.760 606-1697/? V/SystemUpdateService﹕ retry (wakeup: true) in 19969 ms
08-07 20:06:49.230 454-483/? I/PowerManagerService﹕ Going to sleep by user request...
And the most interested part of this log is that:
Code:
08-07 20:06:44.690 168-169/? E/clockwork_proxy_native﹕ Cannot find uid for tcp connection from 192.168.167.239:44849 to 212.0.195.142:80
08-07 20:06:44.690 1378-1453/? D/ClockworkProxy﹕ TCP connection requested by uid=-1
08-07 20:06:44.690 1378-1453/? D/ClockworkProxy﹕ TCP connection is not from a google app, closing it...
I can say only that I do not like this very much... not sure if it can be fixed... Anyone has ideas how to proceed with OTA?

I wonder if this is the same issue people are having over on the G watch forums..theres something wrong with the size of the OTA and the watch not having enough storage

Finally, I was able to update the watch. This error persisted while I was staying in 3g-zone of local operator - Unite (Moldova). (I tried both - sharing 3g connection from the Android phone and sharing 3g connection from router, in both cases update was failed with stacktrace above). As soon as I moved home to the fixed ethernet network I was able to proceed with update. In the same time, it was quite hard to proceed with installing update after it was actually downloaded. The "yes" button in the prompt "Do I want to install update" was clickable, but there happened nothing on click. Finally, after restarting and unknown action from me I was able to make update. I am happy now.
So, try to move to other provider and try to update there.

Also got the update by resetting my gear live...
Sent from my SM-G900W8 using Tapatalk

[Q] Unable to unbrick my bricked phone

Dear People,
I have a problem with my LG P990. It keep hanging on the LG logo with a blue bar under it. I searched the symptons and I found out it is bricked.
This happend after i hard resetted my rooted phone. I tried the following things:
1. I have tried to use Smartflash but my PC wasn't able to recognize my phone when I plugged it in while holding the Volume Down button. I installed different drivers. The ones that were provided by a website and the drivers from the LG Support website.
2. I tried to use AIO toolkit but I get the following error I couldn't find any solutions for on the internet:
======================================
The phone will display a S/W download.. screen,
while the command-window will inform you of the progress.
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 4
chip sku: 0xf
chip uid: 0x0a7c818341ff2117
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 17
sdram config strap: 0
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: fastboot.bin
/ 1027184/1027184 bytes sent
fastboot.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
Succesfully updated partition table information to C:\Users\R...
\Temp\partitions.txt
Checking partition layout...Current Partition Layout could not be detected
Operation aborted
Press any key to return to main menu
I have Windows 8.1 but also tested these 2 methods on a Windows 7 PC.
I read about another method from one of the XDA members called ProgMaq but every download gives a 404 Not Found message or my browers warns me to not go to the website because it is not safe.
What can I do to unbrick my phone?

You should try to change bootloader and follow the instructions in aio

Change SD Card file system?

Wi-fi and BT Failing to Start after Rooting Issues - No solutions worked till date!

Hi All,
Need some help in getting my wifi and bluetooth back to normal. It's over a month now and all my attempts have failed! I would really appreciate some ideas here. Thank you, and sorry for long thread.
Phone info:
Samsung galaxy S6 SM-G920T (T-Mobile), firmware version: NRD90M.G920TUVS6FRC1, stock OS with root and TWRP recovery
Situation:
Bluetooth does not turn ON at all
Wifi takes a long time to turn ON, and only way to turn it ON is from settings (quick access tile does not work)
Wifi does not remember any password
All other functions work correctly, and the phone is now lightning fast after factory reset
Details and Steps Taken:
Rooted my phone a month ago, and started changing config. Took OS and app backup only, but no EFS/other partition backup.
Turned OFF "Allow OEM Unlock" - don't ask why
This (I believe) resulted in WIFI not remembering passwords, so after reviewing potential solutions, I changed "Secure.Storage" value in build.prop to "0"
Took backup of WPA_supplicant.conf and deleted the file
Problem was not resolved, and I had to restart the phone
Restart resulted in FRP lock - to resolve this I re-installed the OS from stock firmware from Sammobile; Yet - no luck on wifi and bluetooth, error still persisted
I reviewed the system log and found tons of errors (listed below). Based on errors, I tried:
Copying libbluetooth_jni.so library file to '/system/lib' and '/system/vendor/lib' folders
Changing 'semGetAllowBluetoothMode' value to "True" - this reduced some errors (refer below)
Validating file / folder permissions for the /efs partition - they seem to be appropriate, but I cannot confirm since there is no reference
I have also tried using SmartSwitch - but it doesn't recognize phone in download mode. It backups the apps, etc. though
Also wiped the system partition once using TWRP, and re-imaged. Yet no luck.
My hunch currently for these errors is:
The /efs permissions became incorrect or partition became corrupt due to some configuration I performed
The system lost its encryption key when the "OEM unlock" was disabled, and thus cannot read any files from the /system and /efs partition (the device was NOT encrypted, but I am thinking /efs is always encrypted by system - correct me if I am wrong)
System log snippets:
Bluetooth Related Log:
Bluetooth GATT service:
Code:
BtGatt.GattService: [GSIM LOG]: gsimLogHandler: null, msg: MESSAGE_LOAD_PREF
Bluetooth Adapter Service:
Code:
BluetoothAdapterService: onProfileServiceStateChanged() serviceName=com.android.bluetooth.gatt.GattService, state=12, Message sending
semGetAllowBluetoothMode:
Resolved this error by updating the value to "True" in build.prop. Was this the right fix, or is it supposed to get value = 2.
Code:
DevicePolicyManagerService: semGetAllowBluetoothMode - value retunrs : 2
Wifi error log:
Code:
WifiHW : ##################### set firmware type 0 #####################
WifiHW : ==========[WIFI] SEMCO MODULE ===========
WifiHW : TEMP_FAILURE_RETRY complete
NetworkManagement: wifiFirmwareReload Error reloading wlan0 fw in STA mode: event = 200 208 Softap operation succeeded
WifiMonitor: killSupplicant p2ptrue init.svc.wpa_supplicant=unknown init.svc.p2p_supplicant=unknown
WifiHW : supplicant_name : p2p_supplicant
WifiHW : Unable to open connection to supplicant on "@android:wpa_wlan0": No such file or directory
WifiWatchdogStateMachine: Unhandled message { when=0 what=135173 arg1=2 target=com.android.internal.util.StateMachine$SmHandler } in state NotConnectedState
WifiMonitor: startMonitoring(wlan0) failed!
WifiStateMachine: Failed to setup control channel, restart supplicant
WifiHAL : wifi_event_loop: Read after POLL returned 4, error no = 0
WifiHAL : wifi_cleanup: Read after POLL returned 4, error no = 2
WifiHAL : Event processing terminated
NetworkManagement: wifiFirmwareReload Error reloading wlan0 fw in STA mode: event = 200 219 Softap operation succeeded
NetworkManagement: wifiFirmwareReload Error reloading wlan0 fw in STA mode: event = 200 229 Softap operation succeeded
NetworkManagement: wifiFirmwareReload Error reloading wlan0 fw in STA mode: event = 200 240 Softap operation succeeded
NetworkManagement: wifiFirmwareReload Error reloading wlan0 fw in STA mode: event = 200 248 Softap operation succeeded
WifiHAL : wifi_event_loop: Read after POLL returned 4, error no = 11
NetworkManagement: wifiFirmwareReload Error reloading wlan0 fw in STA mode: event = 200 256 Softap operation succeeded
WifiStateMachine: Failed 6 times to start supplicant, unload driver
WifiStateMachine: sendErrorBroadcast code:10
WifiController: WifiControllerWifi turn on failed