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.
Related
My N1 is very difficult to fix GPS.
When indoor, I lost all stas, and when outdoor, with out cloud, it take about 3-4 min for fix GPS with 6-8 stas.
I try some solutions in here, but no lucky.
my N1 rom: cyanogen nightly build (last)
radio: 5.08....
Plz help me
Indoor fix will always be difficult to impossible. Nothing out of ordinary.
For quick outdoor fix - do you have data connectivity? Or you're not using 3G data? If not - that's the reason for a long fix time.
If you do have cellular data, try going into your APN settings and changing your primary one so that the APN type says:
default,supl
This greatly improved my lock time.
Sent from my Nexus One using XDA App
Cyanogen 6 definitely has a GPS issue: http://code.google.com/p/cyanogenmod/issues/detail?id=2090
While AGPS settings improve the performance, something is still wrong. I remember stock Froyo to be a 5-20x times faster at getting a GPS lock (I've had cases with a clear blue sky where it's taken 120 seconds to get a GPS fix, before it was a max of maybe 10 seconds).
Also I notice that with GPS Status, I see 1, 2, then 3, 4 satellites show up, then they all disappear... and it starts again, until it gets around 7-8 satellites and gets a lock with 32m accuracy and then the precision slowly increases...
I wish someone could tell me 1) what change Cyanogen has implemented that causes this behavior 2) how to revert back to the old GPS code.
Strange. Your experience doesn't match mine. CM6 here on an AWS Nexus One, with the newer radio. I can get a lock in seconds on GPS Status.
Sent from my Nexus One using XDA App
ever since my switch to cyanogen i have had same problem
Cmstlist, turn off your data (3G and wifi) and try getting a lock with GPS Status so you can see the progress. I'm running the Rogers/AT&T version, and this bug drives me crazy. I'm running the 9/20/2010 nightly, but even RC3 had this bug.
Well if you remove access to aGPS, of course you'll take longer to get a lock.
My guess: stock N1 gets a faster lock because it has a supplementary cache of offline GPS info supplied by gpsonextra. The urls for gpsonextra appear in /etc/gps.conf in CM6 but I'm betting it doesn't function properly on an AOSP firmware. Can anyone prove my instinct right or wrong?
Sent from my Nexus One using XDA App
I've checked on Enomther's build I'm running, which is also AOSP ROM. The most significant correlation of GPS lock time I've noticed was only with data connectivity rates. I've used GPS Status, and it took ~5-10 seconds to lock both in the open near my house and on the moving train at 150km/h in a significantly changed location, with the only thing being common - there was good 3G reception in both areas. Both times it locked in 2 "batches", 3 satellites being locked in the 1st one, and another 5-6 in the 2nd one. The first "batch" is probably strong satellite signals that were locked after Almanach download almost immediately, and the other "batch" might have been post- Ephemeris download. Either that or it has gpsonextra functional - but in any case, the lock is super-fast when the data rates are good.
On the other hand, the data registered on Traffic Info is only 40k download and 20k upload - even on GPRS it won't take long. But the base station needs to support aGPS - that's also something to consider.
Gingerbread 2.3.3 from March 11th running on my (old and outdated) HTC Touch Diamond 2 (Topaz). Was surprised how fast it is running - no crashes so far.
To get it running on your device please follow following basic instructions:
Extract XDA's FRX05 to the ANDBOOT folder of your SD card (yes it is Froyo 2.2.2 but we will update/replace it in step 2)
Replace the existing system.ext2 with the one you should download from southcape.org. first post, you can't miss is, version from march 11th. In this step we replace Froyo 2.2.2 with Gingerbread 2.3.3
Install newest Glemsom kernel (my choice: htc-msm-linux 20110228_202832)
Replace the existing rootfs.img with the newest one (my choice: rootfs-20110224-3dd92b8.zip), otherwise your device will not boot
Change startup.txt to your needs. I added pm.sleep_mode=1, otherwise my device would have wakeup problems
Tested & working:
Incoming/Outgoing Calls (in active & sleep mode),
WLAN/3G/2G,
Exchange (Email, Calender & Contacts) with push,
Gmail (Email via k-9, Calender & Contacts) with imap idle /push,
No wakeup problems after sleep
Hope I was able to help somebody
bean
------------------------------
Gingerbread 2.3.3 (South Cape/xda, March 11th)
Touch Diamond 2 (Topaz)
Kernel: Glemsom's 1276 & modules-2.6.27.46-01276-g6a6a1c1.tar.gz
Sleep mode 1 - no wakeup problems for a long long time
Did you something special to run 3G data?
I took a complete build which was posted in the froyo thread. everything else is fine, especially the performance up to now
Good write up for people new to XDAndroid. But for people who do not want to take the time, here is the link to my bundles, where all of this is done in a bundle or you can use my system.ext2 files that are more recent builds from xdandroid git. These also have camera working
http://forum.xda-developers.com/showpost.php?p=12205814&postcount=6063
freakatzz said:
Did you something special to run 3G data?
I took a complete build which was posted in the froyo thread. everything else is fine, especially the performance up to now
Click to expand...
Click to collapse
Do you have a cdma or gsm phone? if you have a cdma phone you need to add force_cdma=1 to your startup.txt
I did the exact same things as mentioned in post 1. The build is somehow unstable for my Topaz (Topa100). I have problems with sudden sleep freezes, no real Data Transfer trough the Cell Network. I cannot use 2G somehow, but really i have no idea what i am using. I have the feeling some of the upper bar icons are not even present with my device. I have only 3 icons active. Not a single one showing the Network type.
(i am not sure if standard android multitasking works with XDAndroid, if yes, i cannot access it)
The battery drains itself very fast. The phone enters sleep mode, but after some time the Led indicator goes orange. The phone gets hot, evidence that something is running on the device.
I don't have any ideas, what, where .... i really want to see a video of a stable working Topaz with latest build , so i know what is missing on my device.
Running 2.3.3 on Topaz
Hey, I've been running the 2.3.3 latest build (thanks The Jokah for the post).
Unfortunately there are a few kernel related issues and hardware sometimes won't turn off or be 'off' at all. Plus porting the OS will usually require more resources and processor power which means less battery life. (I hope I am at least remotely correct in saying that)
I've had a few crashes when receiving calls at first but as you can see below I have the settings tweaked to fix that, and i make sure to place an outgoing call first thing after booting. The only thing I haven't got to work is GPS which may or may not ever be fixed (thanks for those of you working on it) My camera and everything else runs smooth even though I'm underclocking it for protection.
I've run most common apps and some others like FB, Skype, Weather Bug (w/o auto location enabled)...I even ran Angry Birds and Fruit Slice.
so all in all its a really excellent build but still has the obvious issues when trying to run an OS package on hardware that wasn't originally developed for it.
I get on average with internet use 5 to 10 hours of battery life so good luck on that end.
Justin:
HTC Topa160 with qualcom 528MHz
Carrier: AT&T
Crappy ram and such
Crappy internal Storage and such
4GB SD external
WinMo 6.5 Rom 2.31.502.4
Radio 4.48.25.20
Protocol 61.39tc.25.30H
Rooted
XDAndroid Gingerbread 2.3.3 Latest Build (and shtuff)
Startup
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2293
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 msmvkeyb_toggle=off hw3d.force=1 force_cdma=0 acpuclock.oc_freq_khz=500000 sensor=topaz pm.sleep_mode=2 rel_path=andboot"
boot
your bundle packages doesnt work for me. After run haret and it freezed before get into linux.
bkcheah75 said:
your bundle packages doesnt work for me. After run haret and it freezed before get into linux.
Click to expand...
Click to collapse
Sorry I mean bundles provided by "TheJokah" doesnt work for me. I follow 'Bean+' guideline and gingerbread working well now.
Just battery running fast.
bkcheah75 said:
Sorry I mean bundles provided by "TheJokah" doesnt work for me. I follow 'Bean+' guideline and gingerbread working well now.
Just battery running fast.
Click to expand...
Click to collapse
my bundles are the same as his writeup, but with all the latest files from source. they should work the same
wow - this version is very nice.
---------------------------------------------------------------------------
- when i press the original power button it is not the "home" button
it does the same function like the "end call" button.
answer:
Q. Why does the end call button has the same function as the power button and how do i fix this?
A. The key mapping was changed in a recent rootfs release, to sort that out go into the Main Menu -> SpareParts and select the "End button behaviour" to be "Go Home".
Click to expand...
Click to collapse
---------------------------------------------------------------------------
Q: how can i root this version? (z4root?, SuperOneClick?)
---------------------------------------------------------------------------
Q: As i toggle WLAN, it doest' work - sometimes yes, sometimes no
E-P-S said:
Q: how can i root this version? (z4root?, SuperOneClick?)
Click to expand...
Click to collapse
All the Android ports around here are already rooted.
E-P-S said:
Q: As i toggle WLAN, it doest' work - sometimes yes, sometimes no
Click to expand...
Click to collapse
It always toggles on/off properly for me when I have it turned on from WinMo before using haret.
However, sometimes it turns on, connects to my home network but doesn't really work (no data transfer), disconnecting from and reconnecting to the network seems to fix that.
Rooted
Yes You Right. Big Thanks.
I've installed now:
-Root Checker
-Droidwall
-Superuser
and Titanium Backup
Slow
After the boot, very slow in my case
Cannot do anything
I am very excited! The system is very fast. and battery life is very good!
Good work!
But I have one problem after booting, most applications do not see the sd card as Android Music and Gallery
If you know how to fix this problem, I will be very happy.
Thank you very much, this solved my problem, too. But how can ich activate the task manager, when the home button isn't working like it should?!?
krigav said:
Thank you very much, this solved my problem, too. But how can ich activate the task manager, when the home button isn't working like it should?!?
Click to expand...
Click to collapse
yes, this is mine problem, too
still gps and data problem
i have still this two problems:
data works only after reboot, after switch off/on data no connection!
gps dont work
my impression :
since the camera is working for topaz etc. the development
get very sluggish....
There's already a new version out (March, 25) which is working very well with your decription. But i have still 2 problems:
1. when answering a call, nobody can hear the other person... when finishing this "ghost-call" android freezes...
2. when using facebook-app and trying to post my actual place the phone freezes after some seconds...
any ideas how to fix this?
thx in advance
Maddin91 said:
There's already a new version out (March, 25) which is working very well with your decription. But i have still 2 problems:
1. when answering a call, nobody can hear the other person... when finishing this "ghost-call" android freezes...
2. when using facebook-app and trying to post my actual place the phone freezes after some seconds...
any ideas how to fix this?
thx in advance
Click to expand...
Click to collapse
Did you read about "first-call" need?
Is a well discussed issue on Froyo. I think this issue is still on Gingerbread. After each reboot you need to place 1 single first outcome call. You can make it dialing your own phone number till you listen the unavailable tone. Then drop the call.
After that you can receive calls very well.
been usin this build for 2 weeks now.. no real problems.... ocasional force closes... only when i try to run apps i knew better to not even try!!!
otherwise.. dont have the incoming call problem...
very fast... very what i would call stable.... definetly my favorite ANdroid build for our devices
[Info] "fd_not_activated" and "apntype: default" logging flood both fixed for v20o
This is just for your interest and only concerns u if your network provider does not have fast dormancy enabled and you are receiving a logging flood (fd_not_activated and "apntype: default") due to this which seems to decrease battery life sometimes rapidly.
I managed to increase the fast-dormancy-timer from 1000 milliseconds (= 1 second) to 31337 milliseconds (about 31 seconds).
So your logs won't be flooded anymore if your network does not support fast dormancy.
They also won't be flooded by the apntype: default message any more -- this message will only appear from time to time (and then 4 or 5 in a row).
This fix will be incorporated and first available to public along with my new v20o custom ROM I am working on, and hopefully it will increase battery life for non-fd-user noticeably.
I still have to check if there are any side effects but it doesn't seem so.
Good night and merry x-mas all
Update: found the method with the command accessing the RIL and telling it to activate fast dormancy. set it to false all the time and removed flooding logs. looks good for me
that would be great! hope it will work!
Gesendet von meinem LG-P990 mit Tapatalk
Update: next step for me will be to completely disable Fast Dormancy. It is definitely possible. Just need some more time.
Edit: ok think i fixed it. found the method with the command accessing the RIL and telling it to activate fast dormancy. set it to false all the time and removed flooding logs. looks good for me
Hi, thank you for your efforts. I'm using your current SR1 kernel release ROM. Can you please explain when this is important? Is it applicable to GSM/EDGE or just UMTS?
edit:
Nevermind, I just read in the v20o thread that it seems to be a 3G issue.
But most European GSM providers support fastdormancy and the reason we use it is because it saves battery when you want speed (hsdpa) and battery (jump back to umts). We need to fix fastdormancy, not disable it
A better solution would be to find a way to force the phone to only UMTS to not jump to hsdpa. If you could dig through the RIL and find it that would be awesome.
For v20o we just need the right baseband
as per some posts in SGS2 forum http://forum.xda-developers.com/showthread.php?t=1111581&page=13
better data connexion with FD off, but we must try to see the battery life.. in my case my provider doesn't support FD
my provider supports fd, but still have the fd bug. think its better to turn it off...
wapz said:
But most European GSM providers support fastdormancy and the reason we use it is because it saves battery when you want speed (hsdpa) and battery (jump back to umts). We need to fix fastdormancy, not disable it
A better solution would be to find a way to force the phone to only UMTS to not jump to hsdpa. If you could dig through the RIL and find it that would be awesome.
For v20o we just need the right baseband
Click to expand...
Click to collapse
Reverse engineering the dalvik bytecode / smali is a pain in the ass. it would really be too difficult to try to fix fast dormancy instead of turning it off. fixing is the job of LG`s DEVs which have access to all the source code and not only bytecode and reverse engineered parts. my provider does not support fast dormancy and there are others too and for those turning off fd is nothing bad at all. just writing from a fixed rom, battery life seems improved for me
thanks!! i have the "apntype: default" flood with every rom and every baseband: hope you can release the fix soon!
stegg said:
thanks!! i have the "apntype: default" flood with every rom and every baseband: hope you can release the fix soon!
Click to expand...
Click to collapse
My new rom will be finished soon, just implementing some last features and testing. fd is disabled. once released you can take the corresponding files from my rom and use it with any other v20o rom. maybe i will also make a fd-disable mod for v20l/m ..
Jellybean 4.2.2 for the Droid 3
[ CURRENTLY THIS ROM REQUIRES A ROM-SLOT1 INSTALL IN SAFESTRAP ]
[ ALL Jellybean 4.2.x ROMs should be using 20130301 GApps: http://goo.im/gapps ]
OFFICIAL CyanogenMod 10.1 (Android 4.2.2): [NIGHTLIES]
http://www.get.cm/?device=solana&type=nightly
[03/06] - BT/Speakerphone Fix in next nightly(thanks DHacker)
[02/26] - HWcomposer API 1.0 (JB-MR1 compliant)
[02/26] - HD codec fixes
[02/26] - Kernel updates / bugfixes for clock management, battery drain and stability
[02/26] - Android 4.2.2 merged into CM10.1
[01/23] - MMS fix (sending from native Messaging app)
[01/20] - Keyboard Backlight fixes (tied to the front button backlight for now)
[01/18] - Fixed incoming call bug
[01/16] - Fixed bluetooth for device starting. Audio is still bad.
OLDER CyanogenMod 10.1:
http://goo.im/devs/Hashcode/solana/cm10.1/
AOKP (Android 4.2.2): [B5]
http://aokp.co/supported-devices/?id=58&device=solana
Official release: [GETTING REBUILT FOR BOOT ISSUE]
[03/06] - BT/Speakerphone Fix -- need to get a new build up(thanks DHacker)
[03/05] - Official Release Build #5
[02/26] - Official Release Build #4
[02/26] - HWcomposer API 1.0 (JB-MR1 compliant)
[02/26] - HD codec fixes
[02/26] - Kernel updates / bugfixes for clock management, battery drain and stability
OLDER AOKP:
http://goo.im/devs/hashcode/solana/aokp/
CyanogenMod 10:
http://goo.im/devs/hashcode/solana/cm10/
USING WITH GSM INFORMATION FOUND HERE (by Skreelink):
http://forum.xda-developers.com/showpost.php?p=34057016&postcount=1
ICS BUILDS:
CyanogenMod 9:
http://goo.im/devs/hashcode/solana/cm9/
** NOTE: I Kept the HD Codecs alive in this build. I realize they are laggy and need work to reduce the memory impact.
KERNEL NOTES:
This is the same kexec kernel used in the CM9 builds, so expect all of the same issues (see below):
- No Camera
UPDATED: 2013-02-26
CURRENT DROID 3 DEVELOPMENT:
CAMERA NOTES:
** I would never expect the camera to be fully functioning. I am working several avenues to get a functional camera on the Droid 3, but they're all sketchy at best. Just know that if you choose to flash custom ROMs w/ newer OS versions: You won't have a camera.
** Did I say don't expect the camera to be fixed? If it was to be fixed, trust me, you'll see me all over the boards, twitter and the social universe telling people about it.
** There are other devs now working on the kexec kernel and it's possible that they can get some basic camera functionality through kernel drivers. It's quite complicated and there are no public data sheets which describe the sensor functions in great detail for our devices.
** Don't expect the camera to be fixed.
CHANGES OVER THE LAST MONTH:
BATTERY LIFE / KERNEL BUGFIXES:
https://github.com/STS-Dev-Team/kernel_mapphone_kexec/commits/3.0.31
- Several internal clocks which were left active are now turned off as they should be. (since they're un-used)
- IPI/LOCAL timers were re-enabled in the kernel. These are interrupt driven timers which help trigger various drivers for updates.
- Bugfixes to allow other lower level functions to run in the kernel as well like gpmc
- I've fixed the kernel bootlog recovery driver (/proc/last_kmsg) so that this now works in our kexec kernel. This is a copy of the last kernel bootlog from a prior boot. So if you crash, please reboot and pull /proc/last_kmsg with adb and send me a log via email: hashcode0f at gmail.com
- Removed a hack to initiate the sound driver, causing it to stay active all of the time in the background. It now starts normally and suspends normally. (Thanks to kfazz for the fix).
JB-MR1 DEVICE UPDATES WITH OMAPZOOM:
https://github.com/STS-Dev-Team/android_device_motorola_solana/commits/jb-mr1
- hwcomposer now updated to API1.0
- domx (HD codec) code updated to the latest sources
CHANGES OVER THE NEXT MONTH:
- I'm taking the kexec kernel back to the beginning and re-merging Motorola's changes with the Texas Instrument changes that are needed to run the kernel on the Droid 3: memory allocations, HD codec binary changes, etc.
- This process is already 3-4 weeks in the running, and will be another 2-3 weeks before it's done.
- Once that kernel source is ready for prime-time, I'm going to swap the Droid 3 over to the new kernel source.
WHY DO THIS?
- By taking the time to create a full kernel history (from omapzoom) and integrate the Motorola changes into it, I can then migrate the kernel sources forward in a nice orderly manner cherry-picking new kernel commits directly from Omapzoom.
- This should make for a much cleaner / more stable kexec kernel in the future. And allows other devs to see where I'm going w/ kernel development so that they can add to it. Each file shows how it was edited and by who so it's more transparent where Motorola made their changes to the original TI kernel.
BATTERY DRAIN AND WHEN WILL IT BE "FIXED":
- The current kernel cannot put the UART ports to sleep like a normally booted kernel can. There is an issue that happens during kexec where the clocks associated w/ the UART ports become stuck in a full enabled mode. Any attempts to place them in suspend or disable hangs the kernel. It's being looked at. Right now the device never really 100% suspends. Hence higher than normal battery usage.
"OFFICIAL" ____ (AOKP/CM) MEANS WORKING CAMERA/BLUETOOTH AUDIO RIGHT?
- No. Actually "official" just means you can repo init the source straight from either AOKP/CM and build the device w/o worrying too much about extra sources or patches, etc.
- "Official" also means automated builds for the device (in some fashion). Currently for AOKP it's every 2-3 weeks and for CM it's nightly. These have the benefit of including any changes to the ROM automatically.
- The device doesn't get any more devs
- The device isn't magically fixed or more stable
Just thought I'd toss that in
How do I get from safstrap 1.0.8 using mavrom 4.5 to test this baby. Fairly detailed please. I have eta 906 btw.
Sent from my DROID3 using Tapatalk 2
Wohhhhaaaa thank you !!!!!
downloading ......
i will see how its work in Europe
Dude awesome. Thanks so much! Does the camera work?
Sent from my xt862 using xda app-developers app
duncan254 said:
How do I get from safstrap 1.0.8 using mavrom 4.5 to test this baby. Fairly detailed please. I have eta 906 btw.
Sent from my DROID3 using Tapatalk 2
Click to expand...
Click to collapse
From the experience of various users, all one needs is an update of safestrap to 2.0 and the flash of the kexec ROM. I did this over stock, CM7 and CM9. Many other users have gone from other ROMs - including some version of mavrom.
---------- Post added at 04:36 PM ---------- Previous post was at 04:30 PM ----------
MrObvious said:
Dude awesome. Thanks so much! Does the camera work?
Sent from my xt862 using xda app-developers app
Click to expand...
Click to collapse
Nope. Or should I say not yet...
Do I need to uninstall safestrap 1? What happens to my current nonsafe stock rom?
Sent from my DROID3 using Tapatalk 2
duncan254 said:
Do I need to uninstall safestrap 1? What happens to my current nonsafe stock rom?
Sent from my DROID3 using Tapatalk 2
Click to expand...
Click to collapse
I think that the steps to follow would be something like
1) Go back to non-safe/stock
2) Uninstall safestrap 1.08 from there
3) Install the new one
4) Go to safe mode and finally
5) Flash the build and admire that precious CM9 bootanimation
That's what I would do anyway, I didn't have to since the first safestrap I've ever installed was the 2.0/kexec version
Enviado desde mi GT-I5510 usando Tapatalk 2
I just deleted old safestrap and installed new one on safe system. Everything appears fine. However, the dl is not working.
Sent from my DROID3 using Tapatalk 2
GSM on Movistar Argentina network is working fine (850 mhz/1900mhz UMTS). SMS is ok too.
The GSM level indicator is stuck in the middle. *#*#INFO#*#* Phone information says Signal Strength 0dBm 97 asu. Seen this before in previous ICS builds. Signal indicator works fine in non-safe 906.
Wifi seems solid. Netflix and mp4 video is working
Guess we "just" need audio and camera now.
Thanks Hash and kexec team
EDIT: Oh, and I forgot to say F*CK YOU MOTO!
Amazing! :good:
THANK YOU CM9 TEAM!
and hash and jonpry
I'm a bit confused as to why the phone doesn't work in my tests - I get a force close whenever I try to make a call and attempting to call the phone results in "number unavailable".
rojocapo reports it as working on GSM in argentina, so I wonder what the difference might be.
I've tried *#*#info#*#*, which shows the phone on GSM auto, switching to GSM only doesn't seem to help - and of course I cleared cache+data before flashing.
rojocapo said:
GSM on Movistar Argentina network is working fine (850 mhz/1900mhz UMTS). SMS is ok too.
The GSM level indicator is stuck in the middle. *#*#INFO#*#* Phone information says Signal Strength 0dBm 97 asu. Seen this before in previous ICS builds. Signal indicator works fine in non-safe 906.
Wifi seems solid. Netflix and mp4 video is working
Guess we "just" need audio and camera now.
Thanks Hash and kexec team
EDIT: Oh, and I forgot to say F*CK YOU MOTO!
Click to expand...
Click to collapse
By GSM you are referring to voice calls, or to voice calls plus data connection? And if data connection is alive in this build, did you need to configure the APNs?
Enviado desde mi XT860 usando Tapatalk 2
thingonaspring said:
I'm a bit confused as to why the phone doesn't work in my tests - I get a force close whenever I try to make a call and attempting to call the phone results in "number unavailable".
...
I've tried *#*#info#*#*, which shows the phone on GSM auto, switching to GSM only doesn't seem to help - and of course I cleared cache+data before flashing.
Click to expand...
Click to collapse
Is doing the '#info' stuff the same as going to the Network Settings and clicking on the right radio button? For me, the default is CDMA/WCDMA and selecting GSM Auto does the trick, but not without a reboot.
My phone now seems to be bricked. Believe it or not, I was inside the XDA app and suddenly the phone locked up. No response to the touchscreen or hard keys. I did a battery pull and the I don't even get the Motorola dual-core logo any more.
The phone was on USB charge all the time during the KEXEC tests.
I'll try with another battery and a wall charger.
EDIT: NEVERMIND, battery was at 0%. Plugged it to the wall charger for a while an now it booted up. Maybe USB charging is not working ok? Strange...
rojocapo said:
My phone now seems to be bricked. Believe it or not, I was inside the XDA app and suddenly the phone locked up. No response to the touchscreen or hard keys. I did a battery pull and the I don't even get the Motorola dual-core logo any more.
The phone was on USB charge all the time during the KEXEC tests.
I'll try with another battery and a wall charger.
EDIT: NEVERMIND, battery was at 0%. Plugged it to the wall charger for a while an now it booted up. Maybe USB charging is not working ok? Strange...
Click to expand...
Click to collapse
I have problems with usb charging on all roms. Only works in usb mass storage mode.
Sent from my XT860 using xda premium
the_linkin3000 said:
By GSM you are referring to voice calls, or to voice calls plus data connection? And if data connection is alive in this build, did you need to configure the APNs?
Enviado desde mi XT860 usando Tapatalk 2
Click to expand...
Click to collapse
thingonaspring said:
I'm a bit confused as to why the phone doesn't work in my tests - I get a force close whenever I try to make a call and attempting to call the phone results in "number unavailable".
rojocapo reports it as working on GSM in argentina, so I wonder what the difference might be.
I've tried *#*#info#*#*, which shows the phone on GSM auto, switching to GSM only doesn't seem to help - and of course I cleared cache+data before flashing.
Click to expand...
Click to collapse
By GSM I am referring to voice plus data connection. I always use an app called HiAPN to automatically detect my APN settings by reading the network id from the SIM card. The app was complaining about "no SIM card inserted", so did INFO and set the network to GSM auto. After a reboot HiAPN set the APN correctly and data was working.
I was also getting the "number unavailable" message before setting the network to GSM auto and rebooting.
rojocapo said:
My phone now seems to be bricked. Believe it or not, I was inside the XDA app and suddenly the phone locked up. No response to the touchscreen or hard keys. I did a battery pull and the I don't even get the Motorola dual-core logo any more.
The phone was on USB charge all the time during the KEXEC tests.
I'll try with another battery and a wall charger.
EDIT: NEVERMIND, battery was at 0%. Plugged it to the wall charger for a while an now it booted up. Maybe USB charging is not working ok? Strange...
Click to expand...
Click to collapse
LOL! Yeah, and the battery indicator is broken.
Bobbar said:
LOL! Yeah, and the battery indicator is broken.
Click to expand...
Click to collapse
Yup, it's broken.
BTW, I tried the Razr Beats patch and I still have no sound.
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)