Some people (like me) loosing the signal to the provider. WiFi is ok, but to get back the mobile connection I had to reboot the phone (1-2 times a working day. I never had this problem over the weekend).
I could pin down this behavior to a fast switching between mobile connection and no mobile connection. If the connection is just reestablished and in the next moment it is lost again the phone hangs. I take the underground to reach the office. That is the reason why I only have this issue on working days
So the solution is clear: Stop working. Enjoy the free time
I used "How to get useful logs" from tonyp with the App: SysLog and found in the modem.log the following error: (full log attached)
( 98): dlc[12] atchannel: at_send_command_full() at handshake fails, err - 12. Restarting rild
( 98): lge-ril: handle Cp Reset (CP Reset Cause - 1, RIL recovery activated flag - 0, dlc - 12)
( 98): [0485]< DEACTIVATE_DATA_CALL fails by E_RAIDO_NOT_AVAILABLE
( 98): dlc[12]: lge-ril - requestInterface: Exiting DLC handler, thread - 22231000. s_dlc_handler_create_tracker - 0x6013f
( 759): Exception processing unsol response: 1054Exception:java.lang.RuntimeException: Unrecognized unsol response: 1054
( 759): Unrecognized RIL errno 16
Click to expand...
Click to collapse
I tried a lot of different basebands but could not fix the problem. The only difference was the RIL errno changed from 16 to 14 ???
The basebands I tried are: V30b, V30a, V30c (SU660 - because the sticker under the battery says: Made in Korea), V20m, V20s. In the end I tried different RILs but that only made the problem worse. Now I am back on the original cm10.1 RIL.
Losing the IMEI in the phone is not the problem. I already checked this.
I am pretty sure it is not ROM related because I experienced the same thing on cm7.2 and now on cm10.1 from tonyp on the old and new Boot loader
Regards
Fidi
Possible solution
Hi,
it looks like I found a solution for the loosing signal problem.
After trying all kinds of differnt basebands I switched to an old not recommended baseband. No signal lost for 4 working days in a row :fingers-crossed:
I am now on Baseband 0823-V21b and using ROM tonyp cm10.1 (04)
For the baseband have a look at the P990 Complete Baseband Overview Thread from tonyp: http://forum.xda-developers.com/showthread.php?t=1658047
Cheers
Fidi
Thanks for your informations, i think i have the same problem. Please respond if you have further informations!
I keep you updated:
Over the weekend: Everything worked fine and stable. I used the phone "normal" over the last three days. Including running with Endomondo Sports Tracker and some other parts. The phone is still stable. No reboot since the downgrade to Baseband 0823-V21b.
If I don't get any issues over the week I think that's the solution.
trampi did you downgrade your baseband too? I hope it's a working solution for you too.
Cheers
Fidi
Thank you Fidi!
I have the same logs when my data connection drops, currently with tonyp's T-Build 4 and Kowalski 125 and baseband 0725-V10d.
I will try this out, and report back.
Well I had this data drop issue but when using tonyp's T-Build I started having drops in the whole mobile connection (no voice as well). So I followed his recommendation and flashed BB V30a but that did nothing. Then I tried his Paranoid Android and it's working great!
Bad news here:
7 hours after flashing the baseband 0823-V21b (tonyp T-Build 4, kowalski kernel 125 exp), I got the same error again, and no data, no voice. And only reboot will fix it.
As soon as I see
## AT COMMAND TIMEOUT ##
in the radio log, I'm in the same situation again.
then at the moment of the connection blackout, always followed by:
E/RILJ ( 584): Exception processing unsol response: 1054Exception:java.lang.RuntimeException: Unrecognized unsol response: 1054
and
D/RIL ( 98): dlc[5]: lge-ril - requestInterface: Exiting DLC handler, thread - 7126560. s_dlc_handler_create_tracker - 0x611df
Only with this baseband I don't see this anymore:
E/GSM ( 593): Unrecognized RIL errno 16
I've found a workaround to restore the connection without rebooting:
first kill the /system/bin/rild process
then kill the com.android.phone process
They will both restart automatically.
So this looks like a problem with the ril. Is the ril not compatible with the baseband?
This is also suggested by the "Exception processing unsol response" messages: ril is not able to handle certain baseband commands, although this could also be a corruption on the baseband side...
Now creating a script to automate this workaround will at least give back the connection immediately.
Hi gios_
I am running on the same configuration: 0823-V21b (tonyp T-Build 4, kowalski kernel 125 exp)
If you could provide the script that will check for the error and kill the two services that would be gorgeous. That will solve the problem even if we don't find a "real" solution :fingers-crossed:
Here's the script to fix the connection:
Code:
#!/system/xbin/sh
ps|grep phone|cut -c10-14|xargs kill
ps|grep rild|cut -c10-14|xargs kill
To quickly execute it, you can use gscript (then leave out that first line).
do you guys already check with this solution?
Code:
http://forum.xda-developers.com/showthread.php?t=2075564
antec123 said:
do you guys already check with this solution?
Code:
http://forum.xda-developers.com/showthread.php?t=2075564
Click to expand...
Click to collapse
I did not try that solution because their problem seems to be something else: transition from wifi to data not working; whereas our problem is connection dropping (not only data) at a random moment.
Also my IMEI number is transmitted correctly, so I doubt changing it will do any good.
gios_ said:
I did not try that solution because their problem seems to be something else: transition from wifi to data not working; whereas our problem is connection dropping (not only data) at a random moment.
Also my IMEI number is transmitted correctly, so I doubt changing it will do any good.
Click to expand...
Click to collapse
i used that solution, and with kowalski kernel exp 125 i haven't gotten any data loss. up time already 4 days. using kowalski kernel exp 124, i always get data loss and need reboot.
i use bb v30b ics, and ril (default). rom is using tony bulid 4 cm10.1 newBL. and using 2G always.
Yes, I tried this. But I never lost my IMEI and the solution did not help me
At the moment I am happy with my old baseband (no drops over two weeks). But It looks like that's only a solution for my phone. Maybe we should create a script, that scans the logs for the error and if the connection drops we could restart it with the solution from gios_
FidiS said:
Yes, I tried this. But I never lost my IMEI and the solution did not help me
At the moment I am happy with my old baseband (no drops over two weeks). But It looks like that's only a solution for my phone. Maybe we should create a script, that scans the logs for the error and if the connection drops we could restart it with the solution from gios_
Click to expand...
Click to collapse
yeah i think that true. I'm also confused why some people still have data loss with kowalski exp 125 and some people don't, so wierd
I will stick with baseband 0823-V21b. Still there is no real issue.
There is only remaining thing. In the situations when I formerly lost my connection now the phone rarely heats up for a short time with can drain the battery about 3%. After that the connection is reestablished and everything works as it should
Cheers Fidi
Related
I seem to be having an odd problem with my new G1.
In any Cupcake build (JF 1.51, TheDude's 1.2, Official ADP) I flash, neither the compass nor the accelerometer sensors work at all. I have flashed between them several times, with an Alt+W each time, so I know it's not a bad flash.
The strange thing is, when I jump back to an official RC29 build, both sensors work fine. I haven't tried RC30 or anything else, but I know the sensors are physically functional.
I have re-flashed the latest radio as well, as it is currently using 2.22.19.26I.
If anyone can help me with this problem, I would greatly appreciate it.
gigawatts said:
I seem to be having an odd problem with my new G1.
In any Cupcake build (JF 1.51, TheDude's 1.2, Official ADP) I flash, neither the compass nor the accelerometer sensors work at all. I have flashed between them several times, with an Alt+W each time, so I know it's not a bad flash.
The strange thing is, when I jump back to an official RC29 build, both sensors work fine. I haven't tried RC30 or anything else, but I know the sensors are physically functional.
I have re-flashed the latest radio as well, as it is currently using 2.22.19.26I.
If anyone can help me with this problem, I would greatly appreciate it.
Click to expand...
Click to collapse
I think your using the pre-cupcake apps. Did u download the apps after you updated or did you install them from a back up?
Best way to check, You should got to settings and then sounds&display and check off orientation. You phone should switch from portrait to landscape when you rotate any program (except homescreen). If that works then nothing is wrong with your phone. If it doesn't then something happened somewhere weird
any apps i have installed have been after i flashed a rom (after a wipe) and not from a backup. Plus, something as simple as Google Maps or the Browser App should just rotate without opening the keyboard.
Best way to check, You should got to settings and then sounds&display and check off orientation.
Click to expand...
Click to collapse
By that I assume you place the check mark (lit green) next to the option, not "check it off" (not lit green). I have tried both checked and unchecked in pre-installed apps like maps and browser, and still nothing.
Small update. I just flashed JF's v1.43_RC33 with root, keeping the same more recent radio, and both sensors work there, as they do in RC29. It seems to be ONLY cupcake based roms where they don't work.
Any other suggestions anyone has for me? I might try a hero build next, to see if they work there, but I'm not sure how stable they are yet.
Any help/suggestions would be greatly appreciated!
Accelerometer fix
http://forum.xda-developers.com/showpost.php?p=4081673&postcount=4885
I tried your suggestion, and it did not work. Unlike the other user reporting that the sensors would work for a short time after reflashing, mine has never worked after a cupcake flash. Only after a pre-cupcake flash.
Although ideas like that are what I am looking for, possible corrupt config files that need to be cleared or maybe a mod probe command of some sort to activate or wake up the sensors.
Upon some more inspection, I get the feeling something is wrong with my akmd process, or whatever executable generates the akmd_set.txt compass and accelerometer calibration data. I tried to follow some instuctions to purge the akmd_set.txt file to clear any bad config, but the file is no where to be found. My phone doesnt seem to generate one at all when it's booting.
The akmd process does remain running in the background, as here is its ps output:
Code:
# ps | grep akmd
compass 77 1 1320 328 c020d268 afe0c45c S /system/bin/akmd
This is the output I get from logcat when I try to manually run the /system/bin/akmd process or when it restarts automatically after being killed:
Code:
D/AKMD ( 362): akmd 1.6.4 START
D/AKMD ( 362): library version: 1.2.1.1129
D/AKMD ( 362): Compass OPEN
D/AKMD ( 362): No calibration data
D/AKMD ( 362): Can not initial compass parameters error: -5
and this is the output I get when I run a program like Orienteer:
Code:
I/ActivityManager( 90): Starting activity: Intent { action=android.intent.action.MAIN categories={android.intent.category.LAUNCHER} flags=0x10200000 comp={com.deafcode.android.Orienteer/com.deafcode.android.Orienteer.Orienteer} }
I/ActivityManager( 90): Start proc com.deafcode.android.Orienteer for activity com.deafcode.android.Orienteer/.Orienteer: pid=363 uid=10041 gids={}
D/SensorManager( 363): found sensor: AK8976A 3-axis Accelerometer, handle=0
D/SensorManager( 363): found sensor: AK8976A 3-axis Magnetic field sensor, handle=1
D/SensorManager( 363): found sensor: AK8976A Orientation sensor, handle=2
D/SensorManager( 363): found sensor: AK8976A Temperature sensor, handle=3
D/dalvikvm( 363): GC freed 920 objects / 64320 bytes in 92ms
D/LocationManager( 363): Constructor: service = [email protected]
D/Sensors ( 90): sensors=00000005, real=00000005
D/GpsLocationProvider( 90): setMinTime 2000
W/IInputConnectionWrapper( 145): showStatusIcon on inactive InputConnection
I/ActivityManager( 90): Displayed activity com.deafcode.android.Orienteer/.Orienteer: 1313 ms
D/dalvikvm( 145): GC freed 795 objects / 45896 bytes in 165ms
D/GpsLocationProvider( 90): TTFF: 7203
Maybe this will give someone some more insight as to the problem I am having.
hello,
i me french and i have the same problem.
No akmd_set.txt on my phone.
If you are a solution could you partage it ?
I think it's a driver problem but i'm not sure.
JEEP
Unfortuantly I have still not found a solution, but continue to look for one. I will let you know here if I do manage to solve it.
I am also having the same problem. Wiping does not fix it and the method stated by Cyanogen didn't work either. I don't know if this will be any help, but I do know the accelerometer issue started about 3 or 4 days ago for me. Maybe if I list things I've done to my phone in the last few days, it might help narrow down the cause if others with the same issue compare their experiences to each other.
I have a US T-Mobile G1 and I have been rooted since February. Since that time I have upgraded to (and currently use) the latest radio from HTC, Haykuro's SPL, and a class 6 4gb card. I've also been through more roms than I can count in that time, all without an accelerometer issue till now.
Now that I've got all that out of the way here's the more relevant stuff:
Within the last week I have upgraded to Cyanogen's 1.3.1 recovery boot and installed the latest JAC Hero build. I repartitioned my card into 3 partitions with the directions given in JustAnotherCrowd's thread using parted in the recovery's console.
Code:
#parted /dev/block/mmcblk0
rm 1
rm 2
mkpartfs primary fat32 0 3420
mkpartfs primary ext2 3420 3932
mkpartfs primary linux-swap 3932-3964
This is the first time I've ever used apps to sd. After using that rom for about a day, I switched to Cyanogen's build and wiped my user data without wiping the ext partition of my sd card and I continued to use the swap partition on my Cyanogen build. I'm fairly sure but not 100% certain that the accelerometer was still working at this point. Soon after installing this rom, Cyanogen released an update including the compcache modules to replace the linux-swap setup. I installed the custom userinit.sh script to system/sd to activate compcache. Then Cyanogen released another update (immediate bug fixes) almost as soon as I got this rom working. I flashed the update.zip, but then it started to boot loop. I wiped the phone (not the ext partition), still boot looped. I took out the sd, still boot looped. I put the sd card back in wiped again, reflashed, and then clicked "repair ext file system". STILL BOOT LOOPED! (Don't say I just wasn't giving it enough time to boot because I acctually watched the boot animation flicker in and out for a second and start over.) Next, I used fastboot to restore only the user data from a nandroid backup of an older Cyanogen rom. This time it worked. Next, I installed the audio resources to system/sd/media and linked them using the userinit.sh file. The next day, I realized that the accelerometer was no longer functioning.
I hope this description helps to figure this out.
I'm having the exact same issue.
testing567, can you post the userinit.sh file you are currently using, and possibly you or someone else post their userinit.sh of a phone with a working accelerometer and compass here?
I am thinking that one of my init scripts may not be calling the akmd service properly, as in not with the correct permissions or something, and thus not calibrating itself on boot. I was planning on upgrading to the latest cyanogen update today, as i am running 3.6.5 right now. I was also considering upgrading my SPL to a dev SPL so i can use nandroid to backup (getting a little tired of loosing everything when attempting different roms to fix this issue).
I got my userinit.sh from this post.
http://forum.xda-developers.com/showpost.php?p=4140826&postcount=74
I also decided to take advantage of the media symlinking already in this script and pushed the audio resources to system/sd/media/.
I've always had the same issue when upgrading to a cupcake based rom. Nobody else until recently seemed to share my misfortune (sorry for everyone else). There is an exception though, JF 1.5 (T-Mobile) build the sensors work (although miscalibrated). I haven't found any other solutions or any other way to generate the settings file. My process output appears to be the exact same as you've posted.
I'll keep trying some things but I just want to keep this alive incase anyone else needs a fix and one of us comes up with a solution.
RemoteDJ, I may actually have a solution to your miscalibrated problem. In the process of going through and trying to get my sensors working, I created an empty akmd_set.txt file with chmod 777 permissions (just so it wouldnt ***** about some user permissions when trying to edit it), and then rebooted the phone. Upon looking at the file after reboot, it was filled with calibration data.
Although this has not fixed my problem, it may help you. Also, the application "Bubble" has a calibrate sensors menu option, which may help you too. I may have to try reverting back to JF 1.5 to see if I have better luck there. Was that JF 1.51 you were using? If not, please advise.
Yes it was JF 1.51, it's funny because I just got done making a blank chmod 777 akmd_set.txt lol. Of course i'm on the latest stable cm-3.6.8.1 currently and the sensor doesn't work at all.
Just so we stay up to date with each others findings, I also pulled the akmd app from Haykuro's ION, JF 1.43, JF 1.51, Official RC33 and the current CM build. I have only tried replacing the current one with the ION app (in recovery), so far no change, but I think the only file difference I noticed out of the files I pulled was that the JF 1.43 and Official RC33 seemd to be the same (haven't hashed them to verify) and different then the others which seem to be the same but since I haven't hashed any of them to verify yet I can't say for sure.
I am calling it a night right now but will let you know if I find anything tomorrow.
Just a followup with the hash info.. looks like I was correct:
517a87a4e6caa5e66f0520c68dcb7c0e - Official RC33
517a87a4e6caa5e66f0520c68dcb7c0e - JF 1.43
c3a80124ab072f9bf12cc9e4155a0f9f - JF 1.51
c3a80124ab072f9bf12cc9e4155a0f9f - ION
c3a80124ab072f9bf12cc9e4155a0f9f - CM 3.6.8.1
Another Edit: I am apparently not good at going to sleep.. Good News! (semi).
I left the akmd_set.txt in place (it got filled with data just like yours)
replaced ion/cm akmd with jf 1.43 and now the sensor appears to be working (although still miscalibrated for me, this might be a hardware issue.. lots of drops).
step by step.
copy jf1.43 akmd to sdcard (i just pulled it out of the update zip).
reboot recovery
mount /system
rm /system/bin/akmd
mount /sdcard
cp /sdcard/jf1.43_akmd /system/bin/akmd
then umount (probably not required)
reboot.
It still didn't work, but I deleted the akmd_set.txt via adb and then rebooted and voila!
Let me know if any of that works for you
Edit: I was able to fix my calibration by reverting to the rc30 akmd, I have absolutely no idea why my device is so picky, but it only has ever had correct calibration with accelerometer on the rc29/30 builds (this includes all official t-mobile ota releases). Anyway just wanted to through that out there incase anyone else uses the jf1.43 and is miscalibrated.
RemoteDJ,
Thank you so much for that suggestion! That totally worked for me! I flashed cm-3.6.8.1 tonight and replaced its /system/bin/akmd binary with the one from jf 1.42. After messing around with some permissions (I failed to realize the akmd binary was not set as executable when i moved it over ) i was able to create a blank akmd_set.txt, chmod 777 it, and then restart the akmd service (stop akmd, followed by start akmd).
I can not thank you enough for this suggestion! Guess it just took another similar brain bashing away at the same problem to solve it. I just wonder why this is not a problem for a lot of other people out there. It's the same hardware, so you would think everyone upgrading to cupcake would have an incompatible akmd binary. Strange...
Sweet, I'm really glad it worked for you!
I can't imagine for the life of me why other people don't have similar problems, but then again I've had a few problems that seemed indivualized to my device lol. Its only recently that I discovered a few other people were having problems with the accelerometor.
Oh well, all in all just glad this worked.
Maybe we can get Cyanogen to include this in his FAQ as an alternative for sensor repair for the people like us. I might reply on the latest build thread later, anyway have a good one.
So far I haven't had any luck with this. I'm actually tempted to send my unit back to HTC with the ota 1.5 cupcake on it and see what happens. I'm not sure if it was working when they sent it to me or not. It doeswork with the rc29 though.
I'm having the same issue, no compass apps seem to work, google sky maps doesn't work , the level app doesn't work, all are froze.
How can I fix it?
Hi all,
I hope I can get some help here.
Yesterday I rebooted my S4 Active after I installed some app updates, and suddenly WIFI can't be enabled anymore.
First I thought the phone might be broken, but I tested a factory reset and WIFI works again.
But I don't want to reinstall all apps and lose app settings and so on. I also want to know what is causing this issue, it might happen again.
I am on official Stock Rom (Android 4.4.2) I9295XXUCNE5 I9295PHNCNE1. I am using this rom without any problems since a half year.
So I did some testing with adb and usb debugging, and for some reason the wifi kernel driver cannot be loaded. I tried loading it manually with:
Code:
insmod /system/lib/modules/dhd.ko
But this fails with:
Code:
insmod /system/lib/modules/dhd.ko
insmod: init_module '/system/lib/modules/dhd.ko' failed (Exec format error)
I looked into output of kmesg, and it shows this when trying to load the wifi module:
Code:
<3>[ 614.365997] QSEECOM: qsee_disable_clock_vote: Client error.Extra call to disable SFPB clk
<3>[ 614.362304] QSEECOM: qseecom_ioctl: Failed to vote for SFPB clock-6
<3>[ 614.362060] QSEECOM: qsee_vote_for_clock: SFPB Bandwidth req failed (-6)
<3>[ 614.361816] AXI: msm_bus_scale_client_update_request(): Client 3720895680 passed invalid index: 3
Again when I do a factory reset, WIFI works fine again, so it has to be a software bug somewhere.
After factory reset and working WiFi disable Play Store auto update.
Do one app update, test wifi, next app update, test WiFi,...
Easier to identify if an app is source of issue than do all in one update.
Not sure if insmod or other module related commands might need su credentials provided by rooting.
O-T said:
After factory reset and working WiFi disable Play Store auto update.
Do one app update, test wifi, next app update, test WiFi,...
Easier to identify if an app is source of issue than do all in one update.
Not sure if insmod or other module related commands might need su credentials provided by rooting.
Click to expand...
Click to collapse
That's kind of pain in the ass when you have like 100 apps installed
Well I know the last apps that got updated. But how can this damage wifi system driver? And yes insmod needs root , and my phone was NOT rooted prior this issue. I rooted it know in order to properly debug the problem.
best regards,
Andre
delta_ray said:
That's kind of pain in the ass when you have like 100 apps installed
Well I know the last apps that got updated. But how can this damage wifi system driver? And yes insmod needs root , and my phone was NOT rooted prior this issue. I rooted it know in order to properly debug the problem.
best regards,
Andre
Click to expand...
Click to collapse
Try flashing the NE5_PHN_wifi_150107.zip in CWM from the NE5 folder on my GDrive.
JASONRR said:
Try flashing the NE5_PHN_wifi_150107.zip in CWM from the NE5 folder on my GDrive.
Click to expand...
Click to collapse
Thanks I tried this. Unfortunately, the problem persists.
Do you know which files are used by the WIFI kernel module?
My guess is that some config file causes this problem.
delta_ray said:
Thanks I tried this. Unfortunately, the problem persists.
Do you know which files are used by the WIFI kernel module?
My guess is that some config file causes this problem.
Click to expand...
Click to collapse
Those are the files in the zip file. You can also try deleting data/misc/wifi/wpa_supplicant.conf and rebooting or even try deleting the entire folder.
You can also try my ROM, super WizCyan that is based on the PHN firmware with mostly S5 apps.
Can your rom installed without factory reset over stock rom?
A side note, Play Store also does not work anymore. I am online over LTE and can use Internet, but Play Store gets timeout while loading.
Some more debugoutput from logcat, but not helping much:
Code:
E/WifiHW ( 848): ##################### set firmware type 0 #####################
I/WifiHW ( 848): module is semco
E/WifiHW ( 848): ==========[WIFI] Station firmware load ===========
E/WifiHW ( 848): ==========[WIFI] SEMCO MODULE ===========
E/WifiHW ( 848): return of insmod : ret = -1, Exec format error
If I just knew what is causing the driver fail.
delta_ray said:
Can your rom installed without factory reset over stock rom?
A side note, Play Store also does not work anymore. I am online over LTE and can use Internet, but Play Store gets timeout while loading.
Some more debugoutput from logcat, but not helping much:
Code:
E/WifiHW ( 848): ##################### set firmware type 0 #####################
I/WifiHW ( 848): module is semco
E/WifiHW ( 848): ==========[WIFI] Station firmware load ===========
E/WifiHW ( 848): ==========[WIFI] SEMCO MODULE ===========
E/WifiHW ( 848): return of insmod : ret = -1, Exec format error
If I just knew what is causing the driver fail.
Click to expand...
Click to collapse
Unfortunately not, as most of the stock apps have been replaced by S5 apps. You can try but will get a lot of fc's. If you want to try without factory reset use super backup to backup calls, call logs, contacts and calendar and clear cache and data for these before flashing ROM as well as clear cache and dalvic and restore these after flashing the ROM.
Any specific reason why you do not want to wipe data. I always do it once in a couple of months and reconfigure all apps except for a couple of banking apps that I redtore with titanium backup to save the hassle of contacting the banks again. This helps to clear the clogginf od data and keep the phone smooth.
For playstore you can wipe cache and data for google play & play services and stop them from running.
---------- Post added at 01:20 PM ---------- Previous post was at 01:08 PM ----------
Did you try deleting data/misc/wifi/wpa_supplicant.conf and rebooting and/or deleting the entire data/misc/wifi folder
JASONRR said:
Any specific reason why you do not want to wipe data. I always do it once in a couple of months and reconfigure all apps except for a couple of banking apps that I redtore with titanium backup to save the hassle of contacting the banks again. This helps to clear the clogginf od data and keep the phone smooth.
For playstore you can wipe cache and data for google play & play services and stop them from running.
Click to expand...
Click to collapse
Just pure lazyness . But it seems like that I have to go for the factory reset and backup/restore all apps after.
However I hope to find the source of this issue, who knows when it will happen again.
delta_ray said:
Just pure lazyness . But it seems like that I have to go for the factory reset and backup/restore all apps after.
However I hope to find the source of this issue, who knows when it will happen again.
Click to expand...
Click to collapse
If it works after factory reset, then I would say there is corruption in data. Try deleting 'data/misc/wifi' folder flash the wifi zip and restart
I restored the /data/misc/wifi folder from an older working backup.
Still the same error, there must be something else causing the problem.
delta_ray said:
I restored the /data/misc/wifi folder from an older working backup.
Still the same error, there must be something else causing the problem.
Click to expand...
Click to collapse
I would suggest that you delete thd folder itself. Also you could try with the Ktoonez kernel from here
http://forum.xda-developers.com/showthread.php?p=51925641
delta_ray said:
I restored the /data/misc/wifi folder from an older working backup.
Still the same error, there must be something else causing the problem.
Click to expand...
Click to collapse
Have you changed LTE-modem (NON-HLOS.BIN) from what's in stock *NE5 ROM you informed in OP?
http://forum.xda-developers.com/showthread.php?p=56955843
O-T said:
Have you changed LTE-modem (NON-HLOS.BIN) from what's in stock *NE5 ROM you informed in OP?
http://forum.xda-developers.com/showthread.php?p=56955843
Click to expand...
Click to collapse
No haven't change LTE-Modem Software, still have the stock NE5 installed.
JASONRR said:
I would suggest that you delete thd folder itself. Also you could try with the Ktoonez kernel from here
http://forum.xda-developers.com/showthread.php?p=51925641
Click to expand...
Click to collapse
I guess I should get KT-SGS4-KK4.4-AOSP-jactive_eur-04.19.2014.zip?
This kernel works with my Stock 4.4.2 rom?
delta_ray said:
I guess I should get KT-SGS4-KK4.4-AOSP-jactive_eur-04.19.2014.zip?
This kernel works with my Stock 4.4.2 rom?
Click to expand...
Click to collapse
Not that one, get KT-SGS4-KK4.4-TW-eur-01.03.2015.zip, there is an issue with touchscreen which is being looked into, I am currently using KT-SGS4-KK4.4-TW-eur-01.09.2015_debug2.zip from the debug folder.
JASONRR said:
Not that one, get KT-SGS4-KK4.4-TW-eur-01.03.2015.zip, there is an issue with touchscreen which is being looked into, I am currently using KT-SGS4-KK4.4-TW-eur-01.09.2015_debug2.zip from the debug folder.
Click to expand...
Click to collapse
The kernel did not work on stock rom. Anyway I did another factory reset and restored most apps and settings using TitanBackup Root.
And guess what happened after restore of all the apps & settings?
WIFI is broken again.
Does somebody know all data files are used by WIFI?
delta_ray said:
The kernel did not work on stock rom. Anyway I did another factory reset and restored most apps and settings using TitanBackup Root.
And guess what happened after restore of all the apps & settings?
WIFI is broken again.
Does somebody know all data files are used by WIFI?
Click to expand...
Click to collapse
It seems that something in the settings is breaking the wifi. You can wipe the data of settings and wifi individually and check if it fixes the issue.
If you are doing factory reset, I always recommend to redo the settings again rather than restoring through TB.
Can you take a logcat and send the entire one to check if there is anything there.
Not sure if I mentioned it but I removed "wpa_supplicant.conf" multiple times, it doesn't solve the problem.
JASONRR said:
It seems that something in the settings is breaking the wifi. You can wipe the data of settings and wifi individually and check if it fixes the issue.
If you are doing factory reset, I always recommend to redo the settings again rather than restoring through TB.
Can you take a logcat and send the entire one to check if there is anything there.
Click to expand...
Click to collapse
How can I just reset WIFI settings?
Hello,
today I was working with my Xperia Z (C6603) and flashed a CM12 build. After having some problems with TWRP, I solved it in the end an TWRP and CM12 were working fine. But WiFi and Bluetooth won't turn on anymore. When I press "turn on" it takes some time and then the switch turns off again. A MAC address is not shown anymore. I tried to flash stock firmware with Flashtool, but didn't change anything.
Can someone help me to solve this? Is my phone partially bricked?
Thanks a lot!
Some update as I try to find the problem. I looked into logcat and only find this info when I try to turn on WiFi:
Code:
D/WifiService( 814): setWifiEnabled: true pid=1072, uid=10008
E/WifiStateMachine( 814): Failed to load driver
And when I try to execute wpa_suuplicant manually with "/system/bin/wpa_supplicant -Dnl80211 -iwlan0 -c/system/etc/wifi/wpa_supplicant.conf"
Code:
I/wpa_supplicant( 9440): rfkill: Cannot open RFKILL control device
E/wpa_supplicant( 9440): Could not read interface wlan0 flags: No such device
E/wpa_supplicant( 9440): Could not read interface wlan0 flags: No such device
E/wpa_supplicant( 9440): wlan0: Failed to initialize driver interface
Anyone? Just a hint to narrow down the problem?
Hi,
I have similar problem. My WiFi stopped working out of the blue.
I am quite sure I didn't changed anything. System crash occured when I was switching from Airplane mode to Normal mode (this usually turns WiFi on, if it was activated (and then deactivated) in Airplane mode). Then I got stucked in bootloop. Wiping dalvik-cache helped, but it was not the cause. At first, bluetooth was crashing too, but now it seems it works.
In *#*#INFO#*#* I can see
Code:
Supplicant state: UNINITALIZED
. LogCat issues are almost the same.
I've tried factory reset, but it didn't solved the problem. I've checked permissions, reflashed wifi-modules, tried WiFi Fixer app, reinstalled kernel, flashed another kernel, checked the wpa_supplicant.conf…but it still doesn't work.
EDIT: Oh, I forgot to mention my device: Xperi Mini St15i (Smultron), rooted, unlocked bootloader, Stock ICS ROM (only de-bloated, it worked until now) 4.0.4, build number 4.1.B.0.587. I've used kernel Kappa v1.6, but after the error occured, I tried switch to Rage kernel v2.32.
EDIT2: I've tried to restore original hosts, wpa_supplicant.conf, modules, wifi/*, etc....almost everything and nothing helped. I've flashed original stock ROM (you can find flashable stock ICS ROM for st15i here). I still don't know what happend and I'd like to know it. Hope I'll never see this problem again…
I have same problem than other User with all ROMa. Lossing data connection and I have to restart phone. Some days, two or three times in a day.
User @EnzaX describes it here:
https://forum.xda-developers.com/me...t/rom-resurrection-remix-5-8-5-build-t3739715
Anybody have solved it?
Best Regards.
Check network first. If it is not problem use airplane mode to refresh network.I am also using this rom past it released here. No network related issues yet.
Only works again restarting phone. Exist any mode to log what's happen?
Alkro said:
Only works again restarting phone. Exist any mode to log what's happen?
Click to expand...
Click to collapse
Enable root in settings. Install xposed framework or any logcat apps(from playstore).Check log then.
I have installed Catlog. Error occurs again this morning. I have activate log, i have putted airplane mode and the problem persist. There is a lot of logs but i don't know how to export all log or search what line is interesting for this problem.
There is log labels like:
Activity-Manager, mali_winsys, PhoneStatusBar, NativeCrypto, ProviderInstaller,etc...
Is there any logcat in Xposed Framework or Play store to filter log for only catch errors with data connection. With my actual ROM, is possible that error don't sucedde every day
Hi all:
Here is a LineageOS 17.1 ROM for Z5 compact (suzuran).
Download 2022-09-11
This is a 7z archive with the zip'ed rom and the md5 file in it. Please unpack this archive, copy the included two files somewhere to your device, reboot into TWRP and flash this zip file. Enable md5sum checking. The zip file itself is not signed, so you have to disable zip verification.
Kernel sources
Tree sources
Features:
OS Version: 10.0 (Q)
Kernel: Linux 3.10
Kernel 3.10.108
New: Android security patch level: 5 September 2022
Using sony blob's from stock version 32.4.A.1.54
Memory issues finally fixed!
Battery consumption significantly reduced! For further reduction, please follow these instructions.
Google Pay does not give an error when starting the app. This does not mean, that payment is working. I can't test it, because I don't use this feature at all. Please report if it's working or not.
Updated aptX encoder blobs.
P2P-Crashes fixed.
Important informations:
You should be familiar with general installation of custom ROMs.
Required for installation: TWRP 3.2.1 (pick the version from 2018-02-23!!!) There is a version 3.2.3 out there, but with that version I had problems to restore my backups. 3.2.1 is just working perfect for me!
OR use my self built TWRP-version 3.6.2!
This ROM needs a clean install, old /data may cause problems!
This ROM is NOT pre-rooted.
It is highly recommended that your device is running (or HAS RUN in the past!) the latest stock ROM from Sony (32.4.A.1.54) before flashing this ROM.
Otherwise the baseband files may not match.
Working:
Bluetooth
Camera; both built-in camera (Snap) and 3-rd party camera apps.
Snap may be a little bit laggy, please use 3-rd party camera app instead; for example OpenCamera. If you're running into errors, please report.
Enforced SELinux support (see attached screenshot)
Fingerprint
FM-Radio
GApps (pick this version: ARM64, 10.0, pico [tested])
German app AusweisApp2 working (see this post)
GPS
Headset
LiveDisplay (see attached screenshots)
Location services
Notification LED
Offline charging
Phone calls (see attached screenshot)
SafetyNet test passed successfully
Signed build
SMS
Torch
WiFi
These things are NOT (or badly) working:
Camera focus at low distances.
Encryption
Payment
Streaming (mirroring)
VoLTE
Maybe some more things are not working.
If you have problems with GApps:
Sometimes the SetupWizard of GApps crashes on and on. Then you have to boot into TWRP, mount system, and go into terminal, where you have to delete SetupWizard (see screenshots):
Code:
cd /system/system/priv-app
rm -rf SetupWizard
Reboot.
Use this rom at your own risk! It comes without any warranty! I'm not responsible for any damage! If you don't agree with that, don't try to flash this rom in any way.
Benefits:
Added F-Droid and UnifiedNLP! If you don't want this, simply de-install it.
I've set maximum speaker volume to a higher value.
I've increased microphone gain.
I've changed the microfone gain to avoid echo in phone calls.
Changelog
Troubleshooting:
If you're running into an error, please search in this thread if this error is already posted, before you post it again!
If not, I need a LOG to see what went wrong. Without a LOG I can't help you!
A LOG can be fetched by connecting the device with an USB cable to your PC and then by typing these commands line by line:
Code:
adb root
adb shell logcat -b all -d > logcat
Send my this LOG file via PM.
If you think this could be a SELinux related issue, please try to set the device to permissive mode first.
If the issue is gone, I need the policy file too (plus LOG). Fetch it by typing this line in a terminal:
Code:
adb pull /sys/fs/selinux/policy
If you stuck in a bootloop you can fetch a LOG with this trick:
Press the power button and the volume up button together until the device shuts down.
HOLD the power button.
Release the volume up button and press the volume down button immediately after releasing the volmue up button.
The device should start into TWRP recovery.
Tap on "Advanced", then on "Terminal" and enter these commands line by line:
Code:
cd sys/fs/pstore
cp * /sdcard
Send me the copied file(s), if any, via PM.
Hi Bernie,
First things first : Thank you so much for your amazing work on this device.:highfive:
So hard to find a good, compact and up to date smartphone.
So i tried your Los17.1 and i just noticed another issue : ram usage.
Without nor the gapps neither other apps installed, the system is using 1.6go ram (even the keyboard can take time to appear once you launch an app)
On your Los14.1 (i tried with the last one you created, a few days ago) : it would be something like 0.8go ram (so everything run smoother) still without gapps and other apps / settings.
Maybe, now our days, 3go ram is mandatory for android + gapps + 3rd party ...
Ryu--X said:
So i tried your Los17.1 and i just noticed another issue : ram usage.
Without nor the gapps neither other apps installed, the system is using 1.6go ram (even the keyboard can take time to appear once you launch an app)
Click to expand...
Click to collapse
I know about that. I've tried with gapps and I can confirm that ram is running out of free space. Sometimes the system is not responding any more (screen is flickering and it seems that nothing happens) and I have to restart it (press power button quite a long time until power menu appears).
It is indeed far away from being a daily driver... :angel:
Another issue: It seems that location services (gps) are not working.
Does anybody confirm that?
Although Bernard warmed us that this ROM is not precisely ready yet, I tried to give it a go, Twice, already. At each time, some variations: with and without gapps (Pico and Nano), via the recommended TWRP and the 3.3.1 one. The result is always the same: after the language selection, my phone reboots on the 'Just a sec', endlessly. I have to restore a nandroid backup, on order to have a working phone again.
Sent from my Xperia Z5 Compact using XDA Labs
Berni-0815 said:
It is indeed far away from being a daily driver... :angel:
Another issue: It seems that location services (gps) are not working.
Does anybody confirm that?
Click to expand...
Click to collapse
I can confirm that unfortunately GPS isn't working.
By the way, i saw many other good roms on many devices ... that had an alpha rom far worse than this one
casouzaj said:
Although Bernard warmed us that this ROM is not precisely ready yet, I tried to give it a go, Twice, already. At each time, some variations: with and without gapps (Pico and Nano), via the recommended TWRP and the 3.3.1 one. The result is always the same: after the language selection, my phone reboots on the 'Just a sec', endlessly. I have to restore a nandroid backup, on order to have a working phone again.
Sent from my Xperia Z5 Compact using XDA Labs
Click to expand...
Click to collapse
i didn't have this behavior on my tests, but i usually let the system start and wait for few minutes before using it (especially on 1st boot).
Also, i always reboot once after the 1st boot.
Hope it will help
casouzaj said:
after the language selection, my phone reboots on the 'Just a sec', endlessly.
Click to expand...
Click to collapse
Clean install?
That should not happen...
Ryu--X said:
I can confirm that unfortunately GPS isn't working.
Click to expand...
Click to collapse
You have to enable google's location service in location settings. With that, maps is working with correct location; but I don't know if the location comes from gps, wlan or network. It's raining since many days and I don't want to stand outside in the rain and wait for gps connection... :angel:
I've tried to install f-droid and their location services; no better results...
By the way, i saw many other good roms on many devices ... that had an alpha rom far worse than this one
Click to expand...
Click to collapse
Yes, I know. The problems are always the closed-source binaries from qualcom and sony that are not properly working on LineageOS versions > 14.1
We're working on it but I'm not able to say if we can fix these issues.
BTW: Is anyone able to make an outgoing call successfully?
Berni-0815 said:
Clean install?
That should not happen...
Click to expand...
Click to collapse
Yup,, every single time!
Sent from my Xperia Z5 Compact using XDA Labs
As I said, that should not happen...
Berni-0815 said:
BTW: Is anyone able to make an outgoing call successfully?
Click to expand...
Click to collapse
i tried both calling and receiving a call without issue.
Just a pop up saying mobile network is unavailable ,at the end ,when i hang up (but it's wrong, network is still available)
Ryu--X said:
i tried both calling and receiving a call without issue.
Just a pop up saying mobile network is unavailable ,at the end ,when i hang up (but it's wrong, network is still available)
Click to expand...
Click to collapse
Weird! At my device this popup comes in the moment when trying to make an outgoing call. And this call is not started! The other end does not ring!
Could you please tell us, which preferred network type is set in *#*#info#*#* "Phone info" and in "Mobile network settings" (see screenshots)?
I'm not on any aspect a Dev but I give you all my energy on continuing the developpment of this ROM.
Any other support available ?
Berni-0815 said:
Weird! At my device this popup comes in the moment when trying to make an outgoing call. And this call is not started! The other end does not ring!
Could you please tell us, which preferred network type is set in *#*#info#*#* "Phone info" and in "Mobile network settings" (see screenshots)?
Click to expand...
Click to collapse
Here it is !
And you can make an outgoing call sucessfully? The other end rings and you can make a call?
Berni-0815 said:
And you can make an outgoing call sucessfully? The other end rings and you can make a call?
Click to expand...
Click to collapse
Yes exactly , both ways are ok (incoming and outgoing).
Ryu--X said:
Yes exactly , both ways are ok (incoming and outgoing).
Click to expand...
Click to collapse
Hmmm. Then is must be a problem with my german providers (with their apn I think); I've tested two: T-Mobile and O2. With both I can't make outgoing calls...
New version out; see 1st post
Berni-0815 said:
Hmmm. Then is must be a problem with my german providers (with their apn I think); I've tested two: T-Mobile and O2. With both I can't make outgoing calls...
Click to expand...
Click to collapse
Pretty strange, indeed.
The phone i tested with is on another provider than my z5c.
I got to say that i checked the apn before making my tests, and they were good.
I will retry with the new version tonight .
Thanks
The APN shouldn't matter for regular calls unless you're using Wifi calling or VoLTE, maybe disable both and see if it works.