Hello all
Since I'm unable to find a decent thread on the random freezing of the information on the status bar, here it is.
this is to keep the development threads clean of troubleshooting, and leave it with just development questions, and if we do find a direct link to any particular issue, we can collect this info and pass it on to the correct developer, instead of having issues spread all over the place.
This topic has been opened in direct relation to the Battery symbol in the status bar freezing after the over night use of Airplane mode currently taking up space in the Kernel thread.
But other freezing status bar issues are welcome. we can try and track down a common reason for it happening.
Thank you.
**********************
In reporting your bug, please follow these points so we can try to help you better.
What are your details in regards to these fields
Boot Loader.
Rom.
Kernel.
Any add on flash options (Int / Ext card change / swap partition, 3rd party gapps etc.)
performance settings.
Kernel management settings (if applicable)
Developer Options.
Sound and display options
running background apps.
What 3rd party hardware is being used. (this includes charging from USB port on computer)
And a short description of your problem. how it happens.
Thank you.
Now for Example. this is the layout of a user thats having the battery symbol in the status bar freeze after using airplane mode.
BL: New Bootloader
Rom: CM10 - Look ma, No Hands - By Pengus77
Kernel: [email protected] Kernel exp125
Addons: Konstankang Lite Gapps
Performance settings: Min216 - Max 1500 - Screen Off 608 (CPU Adjuster Active default profile)
Kernel Manager:
PSP - off
hotspot managment - off
screen on managment - On
Wifi TX Level - 11dBm
LEDs - 11
Internal / External read ahead: 1024
USB fast Charge - Off
Single core - Off
2nd core hotplug - off
Dyna Fsync - On
Max Load balance PM
Developer Options - Default / off
Sound options. Mute all
Custom ringtone
custom notification tone
Haptic feedback on all option off.
volume rocker option - on
Display options.
Auto brightness - on
Auto rotate - off
sleep after 15 seconds
pulse lights - on
System options.
Center Clock.
Circle battery with percentage.
Running background apps.
Whats app, Facebook, DSP manager, G+, Google services, Android Keyboard, Nova launcher, CPU adjuster, Pdroid
Charge using only LG charger and cable purchased with my phone.
Randomly, some mornings i find my battery symbol is left on in the mornings.
I do not charge my phone over night, and I use Airplane mode to save power during the night.
sometimes I find that the battery percentage is still the same as it was when i put it down for the night. Better battery stats state
that I have a drain of 0% in over the 8-10 hours I sleep, when i wake i only activate wifi, and for some time before leaving my home i use my phone, with the apps provided above,
but the battery symbol does not drain, it stays at the % as it was still the night before.
oddly, when i turn on full radio use, my battery drain is very fast, to level out after a few minutes. so my battery symbol is only stuck after i had airplane mode on, but then starts to work after i turn off airplane mode.
Any help would be welcome.
*********************************************
I know its alot to digest, but the more information that you can give the better for finding the issue quicker. as most of these issues do not show up in regular Logs, we can only test and search for these issues and report what may be causing it. when we find a sure pattern of what may be causing it, be that, Rom, Kernel, or app, we can then pass that information to the correct Developer.
Data Loss Possible solutions
This is a TUT, by User x_justin,
http://forum.xda-developers.com/showthread.php?p=42044655
It details how to erase your CALibration data, for your phone and how to restore your IMEI.
I Found that after your IMEI is correctly restored, the correct calibration data must also be restored. (this is normally done during a baseband flash)
I've found that flashing a full stock firmware (Using the LG tool) will do this without hassle.
I recommend using the version made for your phone and region. by the use of this link
http://csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn="IMEI"
Replace "IMEI" with your own number, (without the dashes) and it will direct to an LG server with the latest stock Full rom, and drivers for your phone.
After these two things are done, using the AIO tool by Spyrosk to set your preferred bootloader, and recovery, you can flash your rom of choice.
****Please note, all of these processes will fully wipe your phone to factory setting. so please make a backup of your data partition*****
Mr. Tag alot, has a mission.
Hello.
Since this thread is being ignored i went through a HUGE amount of pages from the Kernel thread ,and a couple of Rom threads to Tag everyone having Data loss, status bar freezing issues.
If any of you do still have issues, continue your feedback here. for Two reasons.
1. Posting non-development questions in the Dev thread is NOT allowed on XDA. TonyP and Pengus are being nice allowing you to do it, but in the end it is against XDA rules without solid proof. ( logcats etc.) and since the logs do not show the error correctly we cannot say its kernel or Rom related yet.
2. When you have a troubleshooting question, XDA has a Q/A trouble shooting section. were you can Tag people that you may think can help. this thread is here to collect information about these bugs. and if the dev threads continue to get tied up, a Mod will come in a delete all the important information we need. - to keep the thread on track with Development.
so please. all those that are tagged. if you are still having problems with your phone, link your data here, or simply give a feedback report here so the data does not get deleted,
This is the troubleshooting thread for Data loss, and freezing status bar symbols. you have all been noted to post in the Dev threads about these issues. please continue your posting here so we can correctly track down the bugs. and help eachother, instead of spreading our hopes over the Dev section.
@dimedevil @Peppe91 @tavoc @andreilica @BS86 @x_justin @Luk_Optimus @imayoda81 @genemini @matrixstr @zchuxz3x @frc147 @vs0587 @saaavikk @brugobo @rktdi @extreme79 @jcdid @dr.lube @DcR-Nl @my_dnl @sudden36 @sushantp666 @oneearleft
Those of you above have experienced a freeze in there system in some regard to the Thread title. (i've found you all by going through all the current popular threads in Development, to ask you all to put your experiences here.
those of you that have resolved your problems, please give a short description of how you did this. and add your rom / kernel bootloader and baseband info here if you don't mind.
Those of you that have not resolved your freeze or network problems please continue to report here instead of the Development threads as to keep them clean for development reasons. i've sent a PM to the thread owners asking to pass anyone posting questions related to these issues here. and to ignore any and all other posts relating to it form this point.
When we do find out what is causing the problem, and it cannot be fixed with a simple process like changing your baseband or whatnot, i'll collect this information and PM the correct developer involved to sort it out.
So Please. this is meant to be a Community of Techie minds helping each other out. This Troubleshooting thread has been opened to stop filling dev sections with crap. and to allow all of us to add our experiences together to find a solution.
My 3rd post will hold Information proven to have helped others. and i'll keep checking this thread often to help anyone I can. and relay any decent process to check for different bugs mentioned by those above.
Thank you for reading such a long post.
Necro
cool idea, this thread necro!
Still testing, but since complete wipe, without restore no probs(no posts) with me... :fingers-crossed:
Here I am with 2 different cases of data connection freeze and also gsm signal lost.
Phone set up
BL: New Bootloader
BB: v30a
Rom: CM10 - Look ma, No Hands - By Pengus77
Kernel: [email protected] Kernel exp125
Addons: Standard Gapps
Performance settings: no kernel overclock/undervoltage
Kowalsky Manager:
PSP - on
hotspot managment - on
screen on managment - On
Wifi TX Level - 12dBm
LEDs - 3
Internal / External read ahead: 512/256
USB fast Charge - Off
Single core - Off
2nd core hotplug - On
Dyna Fsync - On
Max Load balance PM
The log No_GSM has some more strange errors in the modem log. The other one has just the above libe.
In the Senza_rete log I tried to make a call with no result. The call was closed immediatly by the phone with no sound.
In another case ( but there is no log, sorry ) I kille the phone process, and then the connection worked once more, I'll test and log also that whenever it happens again.
I received my pm but I never suffered Amy time from data loss....But thanks to the OP who has taken the initiative....kudos my friend
I will come up with all the info when I get to the laptop
Thanks again
Sent from my LG-P990 using xda premium
Hi there,
currently testing KK125. Seems good so far.
My config is:
Boot Loader: old
Rom: TonyP v4
Kernel: KK125
Gapps by tonyp. SD Card mounting normal
performance settings in K-Manager:
activated PSP, HPM, APM
TX Power 11
Read ahead 1024
Max load Balance PM
everything other off
Cpu adjust with UV
min 216, max 1,2 Ghz
dyninteractive
I/O: row
1.2 [email protected] mV
1,1 @ 970 mV
1 @950 mV
[email protected] mV
[email protected] mV
[email protected] mV
[email protected] mV
[email protected] mV
[email protected] mV
[email protected] mV
With 122 everything was ok, with 123 and 124 I had problems with the the above config. 125 seems good again.
I have had 3g mobile signal + data drops. Usually it's just data, but I've sometimes also been unable to make calls, i.e. mobile signal is completely gone. I also had drops with the older 124pre kernel which came with the look ma no hands rom. I'm going to downgrade to exp122 next.
Drops definitely only occur with poor 3g signal conditions, when phone switches to 2g.
BL: New Bootloader
Rom: CM10 - Look ma, No Hands - By Pengus77
Baseband V30a
Operator: Saunalahti/Elisa, Finland
Kernel: [email protected] Kernel exp125
Addons: standard gapps
Performance settings: Min216 - Max 1200 - Screen Off 608 (CPU Adjuster Active default profile). CPU governor interactive. I/O scheduler row. Slight undervolting.
PSP - on (but I always have wifi turned off when I'm not using it)
hotspot managment - on
screen on managment - On
Wifi TX Level 10
LEDs - 20
Internal / External read ahead: 512/512
USB fast Charge - Off
Single core - Off
2nd core hotplug - on
Dyna Fsync - off
Max Load balance PM
Developer Options - Default (android debugging + usb debugging notify are on, but I don't remember turning them on myself)
Sound options.
Custom ringtone
other options I don't remember touching.
Display options.
Auto brightness - on
Auto rotate - on
sleep after 1 minute
pulse lights - on
System options.
Circle battery with percentage.
Running background apps.
Whatsapp, G+, Google services, Android Keyboard, Nova launcher, CPU adjuster
I charge with whatever chargers I have, never the original 'cos it's powering my raspberry pi Mostly I use these 3: Nokia lumia 800 usb charger, old round plug nokia charger with nokia usb adapter (CA-146C), or Nexus 7 usb charger (2 amp).
Hi, first of all thanks for the attention for who still has the data loss problem.. Since flashed kk125 it was all ok but unfortunately yesterday had all day long the data loss signal with the status bar seems connected... Today I'll try to format data and all wipe..
I just want to know if I should try the cal erase..? Anyone can advice me? Thanks again..
Sent from my LG-P990 using xda app-developers app
Here my situation...
I could be wrong, but I think there is something related to wifi / mobile network switch.
I always read that problems are due to mobile network but problem could be related to turn wifi on/off.
At the moment I'm trying whit PSP off (even if I never had problem with it when in coverage).
P990 #1 - my phone
----------------------
BL: new bootloader
ROM: T-build 5 gcc4.8 (clean install)
Kernel: kk125 (installed over kk124)
Addons: feav camera
Performance settings: default value
Kernel management settings (if applicable): PSP on, Hotspon ON, Screen ON, others default value
Developer Options: default
Sound options: sound on
Display option: manual brightness, 10mins sleep
running background app: FB, G+, Gmail, Whatsapp, NewsRepublic
What I've noticed is that data loss occour randomly after losing wifi signal (not always, not often). Attached logs are related to this case:
phone attached to the AP
moved at the border of the AP range
continuous automatic wifi connection/disconnection
after some time no data and unable to join to wifi and mobile network
Other situation is when I leave my office:
turn wifi off
wait for 3g network and blue bars
lock my phone
lift to the underground park (no signal)
on the road usually I have to reboot the phone to get data
One time I got mobile freeze & battery freeze (sorry, no log):
turn wifi off and leave home
going somewhere with weak mobile signal (and stay there for a while)
after a couple of hours (with phone always on a chair) noticed battery indicator freezeed and no mobile data
reboot
P990 #2 - my wife's phone
------------------------------
BL: new bootloader
ROM: T-build 5 gcc4.8 (clean install)
Kernel: kk125
Addons: feav camera
Performance settings: default value
Kernel management settings (if applicable): PSP on, Hotspon ON, Screen ON, others default value
Developer Options: default
Sound options: sound on
Display option: manual brightness, 10mins sleep
running background app: FB, G+, Gmail, Whatsapp, NewsRepublic, ebay, amazon, twitter, instagram
Yes, kk125 it's a great improvement: with PA13 & kk124 got a lot of data lost, now is better, but data loss persists.
At work, P990 #2 is without wifi and very weak mobile network: with kk125 no data loss.
When moving at home, attacking the wifi, it could happen that it lost the data connection (both wifi and mobile data) and the phone did not want to wake up (only led button switch on): after a couple of minutes she was able to turn on the display.
Sorry, no logs cose she reboot the phone.
t-build 4, kk125, newbl, bb 30A
all kernel settings default.
(same problems with other basebands)
One thing that might be different from others:
my provider is an MVNO, so I have to enable "national roaming".
Connection loss about 3 times a day. Sometimes only data, but mostly data+voice+sms.
It seems to happen mostly when I wake up the phone from standby.
I can restore the connection often by killing the android.phone and rild processes.
(for a script see: http://forum.xda-developers.com/showthread.php?t=2336597)
The log line that I always see at the moment the data/connection loss occurs is:
Code:
## AT COMMAND TIMEOUT ##
or more complete, the lines that return in every loss-log:
radio:
Code:
07-08 15:56:00.630 D/AT (11113): atchannel: at_send_command_full_nolock: err == ETIMEDOUT, DLC = 5
07-08 15:56:00.630 D/AT (11113): dlc[5] atchannel: at_send_command_full_nolock() end, err:-4
07-08 15:56:00.630 D/AT (11113): dlc[5] atchannel: at_handshake() end; err:-4
07-08 15:56:00.630 D/AT (11113): dlc[5] atchannel: at_send_command_full() at handshake fails, err - 5. Restarting rild
07-08 15:56:00.630 D/RIL (11113): lge-ril: handle Cp Reset (CP Reset Cause - 1, RIL recovery activated flag - 0, dlc - 5)
07-08 15:56:00.630 D/RIL (11113): ## AT COMMAND TIMEOUT ##
07-08 15:56:00.630 D/RIL (11113): lge-ril: RestartModem - Closing /dev/ttyspi0 device to restart the modem. s_modem_control_fd - 12
(...)
07-08 15:56:04.540 E/RILJ (11099): Exception processing unsol response: 1054Exception:java.lang.RuntimeException: Unrecognized unsol response: 1054
(...)
07-08 15:56:09.549 D/RIL (11113): dlc[5]: lge-ril - requestInterface: Exiting DLC handler, thread - 33756936. s_dlc_handler_create_tracker - 0x6111f
07-08 15:56:09.549 E/GSM (11099): Unrecognized RIL errno 16
dmesg:
Code:
<4>[13:07:08 15:56:02.050] ifx_spi_write -- fail():count:67 [.W.{[email protected] [user=1941659]@....[/user]'..]
<4>[13:07:08 15:56:02.060] [SPI] : ifx_spi_write (459 line): SPI Retry Count is .. 3
<4>[13:07:08 15:56:02.060]
<4>[13:07:08 15:56:02.070] [MUX] : ts_ldisc_tx_looper (2377 line): retry dlci : 23 retry result : -2 retry_cnt : 2
<3>[13:07:08 15:56:02.080] *******************************
<3>[13:07:08 15:56:02.080] *Start RIL Recorvery Mode *
<3>[13:07:08 15:56:02.090]
<3>[13:07:08 15:56:02.090] * Restart IFX Modem *
<3>[13:07:08 15:56:02.099] *******************************
<4>[13:07:08 15:56:02.099] [MUX] : ts_ldisc_close (2525 line): modem reset start !!
That last line in the radio log is from:
frameworks/opt/telephony/src/java/com/android/internal/telephony/CommandException.java
There are only 14 error codes defined, so why does the baseband return error 16?
Seems like baseband and RIL are not compatible.
Same for "Exception processing unsol response"
in telephony/java/com/android/internal/telephony/LGEStarRIL.java
And once every 2 days, I get a system crash that requires a battery pull. Sometimes the screen remains on and frozen.
This might be related because often right before the crash a "Start RIL Recorvery Mode" message appears.
Code:
[13:07:07 19:40:45.790] kernel BUG at /Volumes/CM/src/kernel/lge/star/kernel/workqueue.c:1037!
[13:07:07 19:40:45.790] Unable to handle kernel NULL pointer dereference at virtual address 00000000
[13:07:07 19:40:45.790] pgd = c0004000
[13:07:07 19:40:45.790] [00000000] *pgd=00000000
[13:07:07 19:40:45.790] Internal error: Oops: 805 [#1] PREEMPT SMP
[13:07:07 19:40:45.790] last sysfs file: /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state
[13:07:07 19:40:45.790] Modules linked in: zram(C)
[13:07:07 19:40:45.790] CPU: 0 Tainted: G WC (2.6.39.4-Kowalski-Exp #125)
[13:07:07 19:40:45.790] PC is at __bug+0x1c/0x28
(...)
[13:07:07 19:40:45.790] [<c0049874>] (__bug+0x1c/0x28) from [<c0095a80>] (__queue_work+0x2bc/0x41c)
[13:07:07 19:40:45.790] [<c0095a80>] (__queue_work+0x2bc/0x41c) from [<c0095c44>] (queue_work_on+0x34/0x44)
[13:07:07 19:40:45.790] [<c0095c44>] (queue_work_on+0x34/0x44) from [<c0095c98>] (queue_work+0x30/0x58)
[13:07:07 19:40:45.790] [<c0095c98>] (queue_work+0x30/0x58) from [<c032ad68>] (ifx_spi_send_and_receive_data+0x1e0/0x210)
[13:07:07 19:40:45.790] [<c032ad68>] (ifx_spi_send_and_receive_data+0x1e0/0x210) from [<c032ae9c>] (ifx_spi_handle_work+0x104/0x15c)
[13:07:07 19:40:45.790] [<c032ae9c>] (ifx_spi_handle_work+0x104/0x15c) from [<c009627c>] (process_one_work+0x278/0x45c)
[13:07:07 19:40:45.790] [<c009627c>] (process_one_work+0x278/0x45c) from [<c00967c4>] (worker_thread+0x1a8/0x2a4)
[13:07:07 19:40:45.790] [<c00967c4>] (worker_thread+0x1a8/0x2a4) from [<c009a778>] (kthread+0x7c/0x84)
[13:07:07 19:40:45.790] [<c009a778>] (kthread+0x7c/0x84) from [<c0047158>] (kernel_thread_exit+0x0/0x8)
is it true so far, all those that have posted about data loss is using v30 basebands. is there any on v20-v28 basebands experiencing these?
some communication issues with Ril on the v30 basebands maybe? from the logs it seems Ril tries to reset but fails to do so.
interesting stuff so far guys. please keep posting any new info and logs if you do experience the data loss.
Thank you.
necrowakker said:
is it true so far, all those that have posted about data loss is using v30 basebands. is there any on v20-v28 basebands experiencing these?
some communication issues with Ril on the v30 basebands maybe? from the logs it seems Ril tries to reset but fails to do so.
Click to expand...
Click to collapse
Unfortunately I got the exact same behaviour and logs with v10, v20 and v30 basebands on t-build 4 with kk125 (did not try v28).
Contrary to my experience, FidiS has better luck with a v21 baseband (http://forum.xda-developers.com/showthread.php?t=2336597)
gios_ said:
Unfortunately I got the exact same behaviour and logs with v10, v20 and v30 basebands on t-build 4 with kk125 (did not try v28).
Contrary to my experience, FidiS has better luck with a v21 baseband (http://forum.xda-developers.com/showthread.php?t=2336597)
Click to expand...
Click to collapse
v21, thats a SU660 baseband thought right? got to consider that different hardware builds could be better at using radio software than others.
but thank you for your feedback. all the radio logs gave the same error? oe was there any difference to these logs? also was your rom a restored backup, or a fresh install on each of these baseband flashes?
necrowakker said:
v21, thats a SU660 baseband thought right? got to consider that different hardware builds could be better at using radio software than others.
but thank you for your feedback. all the radio logs gave the same error? oe was there any difference to these logs? also was your rom a restored backup, or a fresh install on each of these baseband flashes?
Click to expand...
Click to collapse
According to the baseband thread 0823-V21b-Baseband is regular p990, not su660.
The lines that I posted above were always exactly the same apart from pid numbers and timestamps. In some cases there were additional errors, but I don't think those are baseband-specific eg "ERROR: requestScreenState failed"
I did restore from a backup after flashing the basebands... There's something I could try indeed, thanks!
gios_ said:
According to the baseband thread 0823-V21b-Baseband is regular p990, not su660.
The lines that I posted above were always exactly the same apart from pid numbers and timestamps. In some cases there were additional errors, but I don't think those are baseband-specific eg "ERROR: requestScreenState failed"
I did restore from a backup after flashing the basebands... There's something I could try indeed, thanks!
Click to expand...
Click to collapse
ah sorry, didnt notice the v21 baseband being p990, ah, sometime its granted to be blind =P
yep, restoring backups (if the problem is persistent in the partitions) could keep the error on each reflash. testing clean at every stage is best for working out bugs.
necrowakker said:
is it true so far, all those that have posted about data loss is using v30 basebands. is there any on v20-v28 basebands experiencing these?
some communication issues with Ril on the v30 basebands maybe? from the logs it seems Ril tries to reset but fails to do so.
interesting stuff so far guys. please keep posting any new info and logs if you do experience the data loss.
Thank you.
Click to expand...
Click to collapse
as I am on the old bootloader I havethe old v20q Baseband and had data loss problems with KK123/124.
viljoviitanen said:
I have had 3g mobile signal + data drops. Usually it's just data, but I've sometimes also been unable to make calls, i.e. mobile signal is completely gone. I also had drops with the older 124pre kernel which came with the look ma no hands rom. I'm going to downgrade to exp122 next.
Click to expand...
Click to collapse
Just a quick followup. It's now been 3 days since I downgraded to exp122, and I've had no drops or any other problems at all...
Awesome thank you. Hopefully this will help track down what's happening.
Hello,
I upgraded my phone to the unbranded/Nordic version (9.2.A.1.210) from the original 9.1.A.1.140.
While this brought many positives (support of BLE for my forerunner & good battery life), it also brought some negatives:
- A terrible clicking noise when the camera is auto-focusing (clearly a known bug in all JB version ...)
- A very unstable wifi
On this second issue, I have not seen any other report of the issue.
The symptoms are quite basic, after some time (around couple of hours), the phone will no longer associate with any wifi.
The only method I found was to enable/disable the airplane mode to restore normal wifi operation ...
I have installed wifi-fixer for having more details, since the wifi is looping on the association mode (could be authentication errors on these known network). Of course, all authentication info are correct as the phone will connect properly once going through the airplane mode ...
I also re-flash that firmware, from the .ftf but also forcing it from Sony SUS ...
At this point I reverted back to 4.1.2 as I'd rather have less features but reliable one (wifi is flawless now - well just as it should be ...)
Anyone else with the problem ? Any solution identified ?
Same problem Here
Would you please point me to the tutorials to get back my phone to 4.1.2, thank you?
guiguyz said:
Hello,
I upgraded my phone to the unbranded/Nordic version (9.2.A.1.210) from the original 9.1.A.1.140.
While this brought many positives (support of BLE for my forerunner & good battery life), it also brought some negatives:
- A terrible clicking noise when the camera is auto-focusing (clearly a known bug in all JB version ...)
- A very unstable wifi
On this second issue, I have not seen any other report of the issue.
The symptoms are quite basic, after some time (around couple of hours), the phone will no longer associate with any wifi.
The only method I found was to enable/disable the airplane mode to restore normal wifi operation ...
I have installed wifi-fixer for having more details, since the wifi is looping on the association mode (could be authentication errors on these known network). Of course, all authentication info are correct as the phone will connect properly once going through the airplane mode ...
I also re-flash that firmware, from the .ftf but also forcing it from Sony SUS ...
At this point I reverted back to 4.1.2 as I'd rather have less features but reliable one (wifi is flawless now - well just as it should be ...)
Anyone else with the problem ? Any solution identified ?
Click to expand...
Click to collapse
Just follow the guide in the general section (i.e. retrieve the right .FTF file and use flashtool), this is very straightforward.
Tried with the ROM from Singapore, same issue ...
=> Association rejected on all known wifi
(using the power button to cycle the airplane mode restore the wifi for 10-15 mn)
Any advice on how to troubleshoot ?
guiguyz said:
Tried with the ROM from Singapore, same issue ...
=> Association rejected on all known wifi
(using the power button to cycle the airplane mode restore the wifi for 10-15 mn)
Any advice on how to troubleshoot ?
Click to expand...
Click to collapse
Maybe it's your wifi that gives problem of compatibility when you're on 4.3
Try with another wifi if you can..
And try to change some settings of your current wifi like number of channel, kind of encryption, and so on..
In fact the problem is more complex as sometime my wifi appears to be ok but I do not have any connectivity ...
Now, I believe I found some interesting infos:
=> prb is directly tied with usage of Bluetooth (especially 4.0 BLE)
When the wifi is 'broken', disabling BT will indeed restore normal wifi operation ...
I could not notice the issue before since Android 4.1.2 do not support BLE ...
I've notice others thread reporting WIFI/BT issue (notably around support of smartwatch)
In my case, I'm trying to have my garmin GPS Watch to pair with the phone, this is were the prb can be easily reproduced
I have the same issue! That damned Association Reject!
I can confirm this is due to Sony 4.3 as Wi-Fi still work normally on my other 4.3+ devices (Nexus 7 2012, Galaxy Nexus)
Sent from my LT25i using Tapatalk
Same here
i have tried numerous methods to fix this so far no luck..im on ub flashed 2 3 roms even stock rom with sus
One observation ...
This time, running stock .210 but not installing my BT4.0 Application (Garmin Connect), I only had the Wifi/BT issue once ...
I will install the application but not connect to my watch (Forerunner 620), to see where exactly is the breaking point.
After all these, I will certainly consider unlocking my bootloader and try the Omni ROM (as I see Walter79 is extremely active)
I have the European version, And it is slow to connect to the GPS, in addition to the "Search for GPS" notification in any application that uses GPS. When it is already connected, the "Location established" notification comes out.
Some help?
Same problem here!
I had the same device with same problem!
Any workaround/fix?
iff you guys are rooted you can try the gps fix module from downloads section. I am on custom rom Asoip and no such problem with gps it is very fast. Also there is an app called Agps on playstore which can re calibrate the Gps and it makes it function faster and it doesnt need root.
A-GPS is only assisted GPS. It's "fake GPS" so to say. Most GPS Status/toolbox apps can "Fix" AGPS by clearing the cache and it will be re-downloaded. However, if you just enable location services for a longer period of time, it should fix itself so to say.
THAT SAID, A-GPS is not precise and is not your location.
Install "GPS Status" from Play Store (either or both) and check the signal strength there.
From what I found... in terms of GPS accuracy...
#1 Samsung Exynos / Huawei HiSilicon (high-end chips, I have not tested lower end Exynos / Kirin)
#2 Snapdragon 600 series (like 670, 675)
#3 Snapdragon 800 series (845, 855 - their signal is trash)
I don't know where MediaTek/Helio stands. But yea, from the devices I tested, this is what I saw. There is the Snapdragon 700 series, not sure how that performs either.
mi 8
Hello everyone,
I recently bought a galaxy s10, and decided to root it to get all the magisk goodness. But it turned out my NFC payment app cannot be downloaded from the app store (and of course unavailable to download elsewhere), so I decided to switch back to stock ROM, until some improvements and better roms show up here in the next months.
But I encountered a problem regarding S Health. I downloaded the patched apk by xpirt on xda, the app works, but the heart rate monitor, spo2, glucose and blood pressure sensors doesn't show up anywhere.
I tested my sensors with the *#0*#, and the HRM sensor work flawlessly. But there's no option to use it in S Health.
I also downloaded the "My BP Lab" app to test the blood pressure sensor, and the app says that "sensor does not exist on this device".
I also switched back to the rooted rom with magisk, edited the build.prop, same results.
I read here that :
Stress, SpO2, blood glucose and blood pressure measurements are disabled in the following countries: AO, ZA, GB, FR, AT, HU, CZ, GR, SI, DZ, TH, CA, CY, JP.
Click to expand...
Click to collapse
Which of course, I live in France, and therefore I have a French CSC (XEF to be more precise, maybe it is available in another CSC ?). But, this info may be outdated since there seems to be support for those sensors on the french version of Samsung's website.
Does anyone here managed to use the sensors in the S health app with the magisk root ?
What solution can you suggest me ? I thought about flashing a different CSC in order to trick my phone to think it is not region locked, but i'm unsure of its positive or negative consequences.
KuraKira37 said:
Hello everyone,
I recently bought a galaxy s10, and decided to root it to get all the magisk goodness. But it turned out my NFC payment app cannot be downloaded from the app store (and of course unavailable to download elsewhere), so I decided to switch back to stock ROM, until some improvements and better roms show up here in the next months.
But I encountered a problem regarding S Health. I downloaded the patched apk by xpirt on xda, the app works, but the heart rate monitor, spo2, glucose and blood pressure sensors doesn't show up anywhere.
I tested my sensors with the *#0*#, and the HRM sensor work flawlessly. But there's no option to use it in S Health.
I also downloaded the "My BP Lab" app to test the blood pressure sensor, and the app says that "sensor does not exist on this device".
I also switched back to the rooted rom with magisk, edited the build.prop, same results.
I read here that :
Which of course, I live in France, and therefore I have a French CSC (XEF to be more precise, maybe it is available in another CSC ?). But, this info may be outdated since there seems to be support for those sensors on the french version of Samsung's website.
Does anyone here managed to use the sensors in the S health app with the magisk root ?
What solution can you suggest me ? I thought about flashing a different CSC in order to trick my phone to think it is not region locked, but i'm unsure of its positive or negative consequences.
Click to expand...
Click to collapse
You have tripped Knox
RoyalPriis said:
You have tripped Knox
Click to expand...
Click to collapse
Yes definitely, but it seems like it is possible to get those sensors working, based on the comments in the patched S health apk post. Does your sensors works in S health ?
Hi all! I was wondering if any of you guys have seen this issue before. I have an old Galaxy S10 that I wanted to resurrect for emulation and forgot the reason why I stopped using it was because the Bluetooth functionality, once toggled on, would look like it's trying to turn itself on but never enables.
I've tried:
Installing all updates
Resetting network settings
Clearing Bluetooth app cache / pairings
Wiping the system cache partition
Factory resetting
Re-flashing current and past firmwares
I was able to get Bluetooth to enable and function normally by random after re-flashing the firmware but would quit after 5-10 minutes.
On the S10 and my current phone Pixel 4a (with functional Bluetooth) I went into Developer options to check currently running services to compare. On the 4a the Bluetooth process is listed as having 1 process and 7 services, whereas on the S10 there were only 2 services and were missing services such as SapService, HidDeviceService, BluetoothPbapService, GattService. (I can post in an edit which services are failing to run on the S10 if need be). The Bluetooth process on the S10 will only show up once Bluetooth is toggled even though it doesn't enable, but will stop running, then start running again, rinse and repeat.
So that being said, is this a hardware issue that I'm SOL with? Are there any other remedies that I could try?
Any input would be appreciated. Thanks!
First off, which S10 do you have... Exynos/Snapdragon makes a big difference, but knowing the model number helps a lot in general as well.
What firmware are you on now?
On my 973U (ie, Snapdragon) I have 1 process and 7 services right now (with BT turned on)... on Oreo with January security (I have stayed off A12 because of many reports of issues on it). I can provide more detail later if needed, as well.
.
schwinn8 said:
First off, which S10 do you have... Exynos/Snapdragon makes a big difference, but knowing the model number helps a lot in general as well.
What firmware are you on now?
On my 973U (ie, Snapdragon) I have 1 process and 7 services right now (with BT turned on)... on Oreo with January security (I have stayed off A12 because of many reports of issues on it). I can provide more detail later if needed, as well.
Click to expand...
Click to collapse
I have an SM-G973U (CCT) running G973USQU6GUJ3, which I believe is the last version of Android 11. I've tried Android 10 and 9 firmwares (can't recall which ones) and I've been having the same issue regardless, which makes me think it could be hardware-based.
In a couple of hours I can edit this post with the two processes that do run, if need be.
Made a mistake - my phone is 975U but that shouldn't matter.
I'm on G975U1UES6GUL1 which I believe is a later version than what you have... but I don't think that will fix anything for your issue. I was on GUL before, and everything worked fine then.
I'd say start off bone-stock after an ODIN and see if it works there (ie, don't download anything, if you can avoid it). Maybe some app you have is killing the BT? But if it doesn't work there, then yes it could just be a hardware thing... disappointing for sure.