Related
Okay, my phone is Samsung Galaxy GT-I9000 (firmware 2.3.3). For a sometime now there has been various problems with the GPS. At first the phone couldn’t get any GPS fix at all. (I’ve done the testing using GPS Test Plus software). Then I found this http://forum.xda-developers.com/showthread.php?t=878970 . After this hardware fix the phone finally began to find satellites. (Thank you kindly!). As a matter of fact the phone finds quite quickly 6-10 satellites in downtown Helsinki (Finland). The probles is, however, that it can’t get a proper fix. Every once in a while you get a fix for a few seconds, but basically there is no fix at all.
I’m a bit dumbfounded by this. I can’t figure out what still could be wrong with the unit. All I can think of are the GPS settings. Mine are as follows:
GENERAL SETTINGS
Test Mode: S/W Test
Operation Mode: STANDALONE
Start Mode: Hot start
GPS Plus: ON
GPS Logging: OFF
Time out: 100
Accuracy: 30
SUPL Settings
Server FQDN Type: Custom Config
Server: supl.google.com
Server Port: 7276
Server Type: UMTS SLP
SUPL Secure Socket: OFF
AGPS Mode: SUPL
SSL Type: VerSign
Do you think there still is something I should try before I purchase a new phone?
PS. Very informative noob video! In addition to solving this GPS problem I was also looking for the movie "Snow white and the seven perverts". Luckily I learned from the noob video that there is no porn available on this site.
Also experienced poor GPS quality. Specially on ICS it is almost impossible to get a proper fix and a constant signal. But it does not only seem to be a HW issue, also the driver has a major effect. Froyo 2.2 had good implementations for example. With Darky 9.5 I get very fast fixes in 5-10 seconds and a constant signal.
If you want a recent OS then I would get a new phone, one from Sony Ericsson, they have cheap models from 2011 that get ICS update, like the Xperia Arc series.
But before selling your SGS try stock Gingerbread with JW4 or JVU, they seem also soffisticated.
Hi everybody,
I start this new thread about tethering (wifi , usb or bluetooth) not working for our N7000 with custom rom based on aosp 4.2.2.
What known:
- only some users has this
- it is not due by contract or by provider limitations
- it is not due by radio/modem driver used
- it is there after a fresh total wipe flash
- in the same N7000 with same sim card with a custom rom based on 4.1.2 stock all works perfectly
- internet connection and wifi work well
This following is my logcat with jellybeer 4.2:
build.board: smdk4210
build.bootloader: unknown
build.brand: Samsung
build.cpu_abi: armeabi-v7a
build.cpu_abi2: armeabi
build.device: GT-N7000
build.display: JellyBeer-v4.20-15MAY2013-070019-20130515
build.fingerprint: samsung/GT-N7000/GT-N7000:4.0.3/IML74K/ZCLP6:user/release-keys
build.hardware: smdk4210
build.host: build2
build.id: JDQ39E
build.manufacturer: samsung
build.model: GT-N7000
build.product: GT-N7000
build.radio: unknown
build.serial: 0019d06f23711f
build.tags: test-keys
build.time: 1368594044000
build.type: userdebug
build.user: beerbong
version.codename: REL
version.incremental: eng.beerbong.20130515.070019
version.release: 4.2.2
version.sdk_int: 17
05-18 18:03:47.733 D/Tethering(2233): sendTetherStateChangedBroadcast 1, 0, 0
05-18 18:03:47.748 D/Tethering(2233): InitialState.processMessage what=4
05-18 18:03:47.748 D/Tethering(2233): sendTetherStateChangedBroadcast 0, 0, 0
05-18 18:03:47.783 D/SoftapController(1898): Softap fwReload - Ok
05-18 18:03:47.908 D/SoftapController(1898): Softap startap - Ok
05-18 18:03:47.948 E/hostapd (14811): Configuration file: /data/misc/wifi/hostapd.conf
05-18 18:03:47.948 I/hostapd (14811): rfkill: Cannot open RFKILL control device
05-18 18:03:48.038 D/Tethering(2233): sendTetherStateChangedBroadcast 1, 0, 0
05-18 18:03:48.078 W/hostapd (14811): wlan0: Could not connect to kernel driver
05-18 18:03:48.293 W/InputMethodManagerService(2233): Window already focused, ignoring focus gain of: [email protected] attribute=null, token = [email protected]
05-18 18:03:48.388 V/PhoneStatusBar(2351): setLightsOn(true)
05-18 18:03:48.483 E/hostapd (14811): Using interface wlan0 with hwaddr 50:cc:f8:8e:30:9a and ssid 'AndroidAP'
05-18 18:03:48.493 D/CommandListener(1898): Setting iface cfg
05-18 18:03:48.493 D/CommandListener(1898): Trying to bring up wlan0
05-18 18:03:48.508 D/Tethering(2233): Tethering wlan0
05-18 18:03:48.508 D/Tethering(2233): InitialState.processMessage what=2
05-18 18:03:48.528 D/Tethering(2233): sendTetherStateChangedBroadcast 0, 0, 0
05-18 18:03:48.533 D/Tethering(2233): Tethered wlan0
05-18 18:03:48.538 D/Tethering(2233): sendTetherStateChangedBroadcast 0, 1, 0
05-18 18:03:48.618 D/Tethering(2233): MasterInitialState.processMessage what=1
05-18 18:03:48.618 D/TetherController(1898): Setting IP forward enable = 1
05-18 18:03:48.623 D/TetherController(1898): Starting tethering services
05-18 18:03:48.623 D/TetherController(1898): Tethering services running
05-18 18:03:48.628 D/TetherController(1898): setDnsForwarders(0 = '8.8.8.8')
05-18 18:03:48.628 D/TetherController(1898): setDnsForwarders(1 = '8.8.4.4')
05-18 18:03:48.628 D/TetherController(1898): Sending update msg to dnsmasq [update_dns:8.8.8.8:8.8.4.4]
05-18 18:03:48.638 D/Tethering(2233): chooseUpstreamType(true), preferredApn =4, got type=-1
05-18 18:03:48.648 D/ConnectivityService(2233): startUsingNetworkFeature reconnecting to 0: enableDUNAlways
05-18 18:03:48.668 D/Tethering(2233): notifying tethered with iface =null
05-18 18:03:48.668 D/Tethering(2233): TetheredState.processMessage what=12
05-18 18:03:48.678 I/dnsmasq (14816): started, version 2.51 cachesize 150
05-18 18:03:48.678 I/dnsmasq (14816): compile time options: no-IPv6 GNU-getopt no-DBus no-I18N DHCP no-scripts no-TFTP
05-18 18:03:48.678 W/dnsmasq (14816): warning: no upstream servers configured
05-18 18:03:48.678 I/dnsmasq (14816): DHCP, IP range 192.168.48.2 -- 192.168.48.254, lease time 1h
05-18 18:03:48.678 I/dnsmasq (14816): DHCP, IP range 192.168.47.2 -- 192.168.47.254, lease time 1h
05-18 18:03:48.678 I/dnsmasq (14816): DHCP, IP range 192.168.46.2 -- 192.168.46.254, lease time 1h
05-18 18:03:48.678 I/dnsmasq (14816): DHCP, IP range 192.168.45.2 -- 192.168.45.254, lease time 1h
05-18 18:03:48.678 I/dnsmasq (14816): DHCP, IP range 192.168.44.2 -- 192.168.44.254, lease time 1h
05-18 18:03:48.678 I/dnsmasq (14816): DHCP, IP range 192.168.43.2 -- 192.168.43.254, lease time 1h
05-18 18:03:48.678 I/dnsmasq (14816): DHCP, IP range 192.168.42.2 -- 192.168.42.254, lease time 1h
05-18 18:03:48.678 I/dnsmasq (14816): read /etc/hosts - 1 addresses
05-18 18:03:48.698 I/dnsmasq (14816): using nameserver 8.8.4.4#53
05-18 18:03:48.698 I/dnsmasq (14816): using nameserver 8.8.8.8#53
05-18 18:03:48.753 D/dalvikvm(2351): GC_CONCURRENT freed 3124K, 55% free 9479K/20672K, paused 2ms+3ms, total 25ms
05-18 18:03:48.753 D/dalvikvm(2351): WAIT_FOR_CONCURRENT_GC blocked 22ms
05-18 18:03:49.918 D/ConnectivityService(2233): ConnectivityChange for mobile_dun: CONNECTED/CONNECTED
05-18 18:03:49.978 E/SecondaryTablController(1898): ip route add failed: /system/bin/ip route add 0.0.0.0/0 via 109.52.99.1 dev rmnet1 table 60
05-18 18:03:49.978 W/FrameworkListener(1898): Handler 'interface' error (No such device)
05-18 18:03:49.978 E/ConnectivityService(2233): Exception trying to add a route: java.lang.IllegalStateException: command '282 interface route add rmnet1 secondary 0.0.0.0 0 109.52.99.1' failed with '400 282 ip route modification failed (No such device)'
05-18 18:03:49.983 E/ConnectivityService(2233): Exception trying to remove a route: java.lang.IllegalStateException: command '283 interface route remove rmnet1 default 0.0.0.0 0 109.52.99.1' failed with '400 283 Failed to remove route from default table (No such process)'
05-18 18:03:50.018 W/NetworkPolicy(2233): shared quota unsupported; generating rule for each iface
05-18 18:03:52.548 D/lights (2233): set_light_buttons off
05-18 18:03:53.008 D/Tethering(2233): TetherModeAliveState.processMessage what=3
05-18 18:03:53.008 D/Tethering(2233): chooseUpstreamType(true), preferredApn =4, got type=4
05-18 18:03:53.058 D/TetherController(1898): setDnsForwarders(0 = '213.230.129.10')
05-18 18:03:53.058 D/TetherController(1898): setDnsForwarders(1 = '213.230.155.10')
05-18 18:03:53.058 D/TetherController(1898): Sending update msg to dnsmasq [update_dns:213.230.129.10:213.230.155.10]
05-18 18:03:53.058 I/dnsmasq (14816): using nameserver 213.230.155.10#53
05-18 18:03:53.058 I/dnsmasq (14816): using nameserver 213.230.129.10#53
05-18 18:03:53.063 D/Tethering(2233): notifying tethered with iface =rmnet1
05-18 18:03:53.063 D/Tethering(2233): TetheredState.processMessage what=12
05-18 18:03:53.158 W/libc (14874): protoent* getprotobyname(char const*)(3) is not implemented on Android
05-18 18:03:53.158 W/NatController(1898): Unable to set TCPMSS rule (may not be supported by kernel).
05-18 18:03:53.243 D/WeatherUpdateService(14679): Service started, but shouldn't update ... stopping
05-18 18:03:53.453 D/GCM (2610): GcmService start Intent { act=android.net.conn.CONNECTIVITY_CHANGE flg=0x8000010 cmp=com.google.android.gms/.gcm.GcmService (has extras) } android.net.conn.CONNECTIVITY_CHANGE
05-18 18:03:53.573 D/libgps (2233): proxy_agps_ril_update_network_state: called
05-18 18:03:53.573 D/dalvikvm(2610): GC_CONCURRENT freed 664K, 42% free 4510K/7708K, paused 13ms+38ms, total 159ms
05-18 18:03:53.673 D/ConnectivityService(2233): handleInetConditionHoldEnd: net=0, condition=100, published condition=100
05-18 18:04:00.733 D/lights (2233): set_light_buttons on=1
any idea? any more data or test?
Sent from my GT-N7000 using xda app-developers app
wrong forum, try Q and A, this forum is for ROM Development.
I have had this from time to time, usual due to bugs and under developed ROM. Maybe kernel issue?
my god, this guy has flood jellybeer's thread and now he open a thread in bad section...
this guy is trying to find answares from who he thinks is more competent.
Did I write in a wrong section? I'm sorry but I think this is a issue of developers' competence, it is not a simple q&a.
I notice that all here are so gentle with who need help, tell me what is the trouble about asking and going on in discussion.
When I was a HD2 owner, I found that audio quality during calls was bugged... a part of the thread was like some here, saying I "flood" the thread, I was wrong, I must stop asking and writing... then it was known as a issue of HD2 and developers solve it...
why this time it cannot be the same?
Sent from my GT-N7000 using xda app-developers app
you are right, it is a development issue but this section is for ROM development, not issue solving for bugs. You may notice that some developers will actually place a support thread in a Q & A section for questions such as yours, you should do the same, its appropriate. This section is for developers thread creation..
The CM/AOKP ROM I am on tethers fine, HyperDroid, you should post in your ROMs respective thread.
Agreed with all - this isn't the correct forum.
However - This must be a known issue with all AOSP/CM9-10 Roms.
This is one of 2 reasons I stopped using AOSP/CM9-10 roms. (The other was multiview).
Seriously there is No point using AOSP/CM9-10 if you wan't tethering to work as it simply won't in my experience.
I have horrible memories of trying to do dial-ins for work via tethering and it just randomly dropping the connection for no reason on multiple CM9-10/AOSP roms - Seriously if tethering is crucial - don't waste your time.
qazzi76, correct.
If it does not work properly and is so important to one then change to a ROM that works properly..
I have had the same issue as OP in past and it kept me away from CM etc for a while, along with other issues with CM etc.
If everything needs to be right use a TouchWiz ROM. It is a known issue the CM does not have source files for the Note, so there will be issues (so I believe)
Accept and learnt to live with what you choose to use, its everyone's choice in a custom ROM world.
I'll flash a stock based custom rom to have all function working, but I think that if some doesn't work in a rom it must be written on rom description and not saying "full working".
I don't understand why for a lot of people tethering works and for some not with aosp 4.2.2.
This is a limitation due to the not known samsung code? ok but so I must think that we have different N7000 with different hardware, in same case they work with base aosp code...
I still don't understand...
Sent from my GT-N7000 using xda app-developers app
Or maybe it's operator restrictions... With jellybeer tethering work good.
Have you test tethering with a other SIM card of different operator?
M3GATROLL said:
Or maybe it's operator restrictions... With jellybeer tethering work good.
Have you test tethering with a other SIM card of different operator?
Click to expand...
Click to collapse
I know, for some users all works perfectly, for some, like me, not.
it seems ti be a known 4.2.2 aosp issue, but not for all and I don't understand why.
As I wrote in the first post, it's not due to a provider o contract limitation, I make this test:
- my wife has a Desire HD with a 4.2.2 custom rom (codefire) and with her sim tethering works well;
- I put in my wife's Desire HD my sim card and wifi tethering works perfectly, so the problem is not my provider, my sim or my contract;
- I put my wife's sim in my note and wifi tethering doesn't work.
APN are exactly the same, we have same provider.
farinacci_79 said:
I know, for some users all works perfectly, for some, like me, not.
it seems ti be a known 4.2.2 aosp issue, but not for all and I don't understand why.
As I wrote in the first post, it's not due to a provider o contract limitation, I make this test:
- my wife has a Desire HD with a 4.2.2 custom rom (codefire) and with her sim tethering works well;
- I put in my wife's Desire HD my sim card and wifi tethering works perfectly, so the problem is not my provider, my sim or my contract;
- I put my wife's sim in my note and wifi tethering doesn't work.
APN are exactly the same, we have same provider.
Click to expand...
Click to collapse
So your isolation test has identified your note running CM/aosp to be the issue, either hardware or the OS. Your next test is to use a different ROM.
By the way, I to have a DHD and I have had tethering issues on that from time to time, and guess what, it was with CM or aosp based ROMs..
I think you are going to find it is with ROMs not specifically made for the device that has issues like this..
twerg said:
So your isolation test has identified your note running CM/aosp to be the issue, either hardware or the OS. Your next test is to use a different ROM.
By the way, I to have a DHD and I have had tethering issues on that from time to time, and guess what, it was with CM or aosp based ROMs..
Click to expand...
Click to collapse
I tested my N7000 with JellyBeer 4.18, JellyBeer 4.20 and ReVolt 4.3 and tethering never works.
With different 4.1.2 roms based on stock firmware tethering works every time.
In my DHD tethering works always, I've never had any issue, now I'm using CodefireX 4.2.2 based rom and the same sim card I use on N7000.
twerg said:
I think you are going to find it is with ROMs not specifically made for the device that has issues like this..
Click to expand...
Click to collapse
I think that the problem is that some N7000 are different from others, or some provider's SIM works different on N7000 then in others PDA.
Due to this, roms based on AOSP/CM give this issue on some N7000, not on all.
The best test, but I cannot do, can be use my N7000 as it is now, with the sim card of who says that all works perfectly.
In this case I can understand if tethering issue is due by provider/sim card or by the hardware of my N7000.
my experience with these types of roms and tethering is that i can connect and use it for a bit of time before i get no data transfer at all.
The only way for me to fix it is to either turn data off on the phone or place in to flight mode and then re-enable the radio and tethering. It will then work for a bit before failing again, again with no data transfer. The connection never drops, just stops sending and receiving.
This is enough for me to change roms, if I want or need a feature to work properly I change to a rom that will work for me.
I am not going to sook about it when it is not going to be fixed. This is a long running issue, I an sure there is a fault that may have been raised with CM or respective Rom devs, just get over it. It may get fixed, it may not.. Move on, or fix it yourself if you can..
farinacci_79 said:
I know, for some users all works perfectly, for some, like me, not.
it seems ti be a known 4.2.2 aosp issue, but not for all and I don't understand why.
As I wrote in the first post, it's not due to a provider o contract limitation, I make this test:
- my wife has a Desire HD with a 4.2.2 custom rom (codefire) and with her sim tethering works well;
- I put in my wife's Desire HD my sim card and wifi tethering works perfectly, so the problem is not my provider, my sim or my contract;
- I put my wife's sim in my note and wifi tethering doesn't work.
APN are exactly the same, we have same provider.
Click to expand...
Click to collapse
ok... and have you test application like this or other in playstore ?
twerg said:
my experience with these types of roms and tethering is that i can connect and use it for a bit of time before i get no data transfer at all.
The only way for me to fix it is to either turn data off on the phone or place in to flight mode and then re-enable the radio and tethering. It will then work for a bit before failing again, again with no data transfer. The connection never drops, just stops sending and receiving.
This is enough for me to change roms, if I want or need a feature to work properly I change to a rom that will work for me.
I am not going to sook about it when it is not going to be fixed. This is a long running issue, I an sure there is a fault that may have been raised with CM or respective Rom devs, just get over it. It may get fixed, it may not.. Move on, or fix it yourself if you can..
Click to expand...
Click to collapse
Using stock rom or custom rom based on stock I've never had any issue, so your data connection is something different.
I know that the best for now is to change rom to one with all features I need working, but who surf XDA is looking for the best and/or the last before stock relase...
It is a concept.
I'll test last pristine slim rom, based on lxt5 and if all works that can be my rom for the moment...
Samsung is relasing 4.2.2 update for S3, we have S4 firmware... maybe developers will relase something new soon.
Sent from my GT-N7000 using xda app-developers app
M3GATROLL said:
ok... and have you test application like this or other in playstore ?
Click to expand...
Click to collapse
Yes I tested a few tethering app from store, that you linked too, but nothing, no data shared.
Sent from my GT-N7000 using xda app-developers app
This one is the only one that has worked for me on aosp based rom. Currently with pac man rom it works but after using the app I have to reboot to make wifi working again.
Can't the problem be related to ad booking apps or some lines in the host file. I never succeed having tethering working in my note before this app.!!
Envoyé depuis mon GT-N7000 avec Tapatalk
rom08 said:
This one is the only one that has worked for me on aosp based rom. Currently with pac man rom it works but after using the app I have to reboot to make wifi working again.
Can't the problem be related to ad booking apps or some lines in the host file. I never succeed having tethering working in my note before this app.!!
Envoyé depuis mon GT-N7000 avec Tapatalk
Click to expand...
Click to collapse
Using a stock based custom rom none?
For me, with a based stock rom, no problem with tethering.
Yes I have the same problem as yours. I can use tethering with samsung base rom but not with aosp ones. This app work but break wifi until reboot when you stop it. Try it you have 20 minutes for the refund if it don't work.
Envoyé depuis mon GT-N7000 avec Tapatalk
today I tested asylum... same result, tethering not working :banghead:
Sent from my GT-N7000 using xda app-developers app
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.
wifi.supplicant_scan_interval not found in build.prop ....what could i do?
is it ok to manually add it at the end of the file? i could add wifi.supplicant_scan_interval=xxx ( where ix can be 300... 600...)
but i don't know if this "forced" string can bring me some problems. i firstly have to understand WHY in official lenovo rom is is not present. or is it a MISSING option in every mediatek?
info: i am on stock lenovo andoid 5.0 rom by cuoco92 1.13
phone: lenovo k3 note
update:
i added (because it's not present in my stock build.prop file) the string :
wifi.supplicant_scan_interval ......... and setted value at 600 ( 10 minutes), but does now work at all
i tested in this way, i turned off wifi on router and waited android disconnected wifi....waited just 10 seconds and then REactivated on router wifi on.
if all work good, wifi should be fixed by android only 10 minutes AFTER...........instead it does reconnect just after about 15 seconds.....from the time i re activate on router.
THIS IS NOT OK.............
i tried to do this build.prob hack ecause i have an HUGE alarm from android system: com.android.server.wifimanager.action.start scan at about 3 times per minute!!! THIS IS KILLING MY BATTERY
how can i calm down this alarm???? it's something related the "wifi scan"..... but i can't understand what wakelock/alarm is the bad boy...... and how to reduce that alarm
no one?
I just finished a clean flash of Lineage OS kitkat from milaq and the wifi settings is stuck on "Turning WiFi on". The MAC address in listed at "Unavailable" under Status.
Diving deeper, I got terminal working and see the following from netcfg:
Code:
lo UP 127.0.0.1/8 0x00000049 00:00:00:00:00:00
dummy0 DOWN 0.0.0.0/0 0x00000082 42:6e:b7:fa:06:25
sit0 DOWN 0.0.0.0/0 0x00000080 00:00:00:00:00:00
ip6tnl0 DOWN 0.0.0.0/0 0x00000080 00:00:00:00:00:00
wlan0 UP 0.0.0.0/0 0x00001003 00:1d:fe:eb:a1:c9
A kernel module is present at /system/lib/modules/ath6kl.ko while dmesg logs the driver as working (I think) and one suspicious message:
Code:
ath6kl: temporary war to avoid sdio crc error
ath6kl: ar6003 hw 2.1.1 sdio fw 3.2.0.144 api 3
ath6kl: firmware supports: sched-scan,sta-p2pdev-duplex,rsn-cap-override
Code:
wlan0: link is not ready
I originally suspected a driver issue, but now I wonder if Android is not using the right interface. What can I do to check if Android is using wlan0?
I have read about reloading the kernel module which I haven't tried yet. ifconfig doesn't return any messages and ifconfig wlan0 reports:
Code:
wlan0: Cannot assign requested address
Appreciate any pointers as to which area to focus my debugging.
Did you resolve your issue? I am having similar issue and would like to elaborate and hopefully get some help here:
I have been using the HP TouchPad since fall of 2011, loaded CM9 in 2012 and worked perfectly since until about a month ago, wireless stopped working (will not even bring up any wireless network), just stuck on "turning wifi on".
Browse forum, tried many solutions like removing /data/misc/wifi & DHCP etc, nothing works.
Loaded a few different ROM, a couple of them after initial reboot was able to access wifi, then after a day or so, it will stop working, yesterday, decided to try loading 7.1.x using instructions here, after loading kitkat 4.4, again, wifi worked for a while, then this morning it stopped and stuck on "turning wifi on" again, continue upgrade to Evervolv 7.1.x successfully, unfortunately, again, wifi is stuck on "turning wifi on".
Reason why I kept trying and not chalk it up as HW issue is that wifi connected perfectly in WebOS, it stays on for days and never lose connection after Android OS started to have issue, nothing on Router (Netgear R7000 on DD-WRT) setup has been changed in last year, all other 11+ wireless devices work fine.
Can one of the expert kind soul here shed some light and help me with this? Really puzzle me..., this will be my last hope before finally giving up on it.
Thanks
My hp touchpad started one week ago to fail to detect any wifi. It is supposed to be searching, but don't find any wifi.
I have checked the wifi with webOs and it works.
I am running Lineage too.
I have installed CM12 and now wifi works again properly.
I'm afraid I will have to come back to this old version
I'm having the same issue with wifi never turning on. WEbOS has no problem connecting but I've tried many different versions and combinations of Android but none of them work. Some above seem to have had a connection and then lost it but my TouchPad would never turn on wifi after I installed android. I've also tried several different suggestions I've found on the internet but none of them have worked. About a year ago, I tried different versions of KitKat and now I tried another version of KitKat that is supposed to be the most stable but still no luck. Can anyone help? Is there a solution to this problem?
Thanks,
S