nothingblooms
Well-known member
...what is this magic?
Sent from my SPH-D710 using Tapatalk 2
::shrug:: lol
...what is this magic?
Sent from my SPH-D710 using Tapatalk 2
No worries, it still puzzles me that everyone seems to be having wakelock/or LOS .I have no issues ( except for the one mms issue I fixed do to my error). I can switch between wifi and 3g and be perfectly fine, in fact the bars and everything seem to be working flawlessly. Deep sleep as soon as i hit the power button and absolutely no waking up unless I want it to. No LOS when charging, and no random reboots. Torch, camera, gps, wifi, 3g, mms, sms, calls, no los, deep sleeps, google now, bluetooth(except for media), marketplace, battery life, etc etc all normal. ::shrug::
No worries, it still puzzles me that everyone seems to be having wakelock/or LOS .I have no issues ( except for the one mms issue I fixed do to my error). I can switch between wifi and 3g and be perfectly fine, in fact the bars and everything seem to be working flawlessly. Deep sleep as soon as i hit the power button and absolutely no waking up unless I want it to. No LOS when charging, and no random reboots. Torch, camera, gps, wifi, 3g, mms, sms, calls, no los, deep sleeps, google now, bluetooth(except for media), marketplace, battery life, etc etc all normal. ::shrug::
Well there is one major difference between you and us Mr. US Cellular is it? Are others on your network reporting the same flawlessness?
Sent from my SPH-D710 using Android Central Forums
Well there is one major difference between you and us Mr. US Cellular is it? Are others on your network reporting the same flawlessness?
Sent from my SPH-D710 using Android Central Forums
hey can anybody tell me my device id is changed on every install is this something to worry about
Ok I can tell you by formatting system in recovery prior to flashing will cause a status 7 cause it looks at your current build.prop and by formatting system you delete the build.prop. Follow my directions in the op. format system nor use calks wipe all script is in my op.
Woo! Now I am no expert at all so bare with me. Maybe there is a RIL/Modem conflict causing the ghost LoS. I logcat on my phone so I cant really show besides a screenshot. So I have my wifi turned off at the moment. BUT, there is an error on WifiStateMachine stating that it fails to disable IPv6 which leads to error on ConnectivityService which leads to error on MobileStateTracker because it cant connect to the phoneservice
Someone please look into this. Again I am no expert, just trying to help, so if I am wrong, dont chastise me about how I am a noob and have no idea what I am doing
Do we have another mirror for jb? Dropbox is flooded..
DK Pm if you are interested in having me host a mirror... I have a 100/100 fiber connection to my house and im running a safe http file sharing server.. I should be able to help quite a bit.
This seems legit.
Sent from my SPH-D710 using Android Central Forums
Well I know of two issues ive come across in all the logcats.
1. lib.omx.sec.decoder.so is erroring out (Fixing now)
2. WiFi Supplicant is also erroring out (Fixing now)
Now the decoder could in theory create some if not all these issues.
Go for it.