Any of us still on stock FRF91 with mac addresses not starting with 00:* are dealing with the bug where wi-fi disconnects when the phone goes to sleep:
(sorry, my account is too new to properly link the bug thread)
google.com/support/forum/p/android/thread?tid=01a47ff5b0a92d52&hl=en&start=120
This is fixed in the latest CM6 nightly builds, but I don't think it's possible to get the .ko from that build to work on stock FRF91.
I backported the fix from git (android.git.kernel.org/?p=platform/system/wlan/broadcom.git;a=commitdiff;h=5a838529e6197475cbe8f5a4557fbd31f90586a6) to the earlier version of the driver.
I've been testing this for the last 30 minutes and haven't been kicked off wi-fi once after the screen went to sleep.
How to install:
Make sure you're on FRF91 and have rooted yourself
adb shell and get root via 'su'
Copy your old driver to /data/local: cat /system/lib/modules/bcm4329.ko > /data/local/bcm4329.ko.old
Check that the MD5 of the unzipped .ko is 959dda656228b4191f8e97b920482ae2
From your system, adb push the attached bcm4329.ko (unzip it first) to /data/local/bcm4329.ko.new
adb shell and get root via 'su' again
Copy the driver over top of the old one: cat /data/local/bcm4329.ko.new > /system/lib/modules/bcm4329.ko
Reboot
You'll probably screw up future OTA updates if you manually patch this, but it's easy enough to undo (just flash the stock FRF91 or replace the old driver). Also, it worked fine for me, but you'll be doing this at your own risk, etc, etc etc.
---
mmastrac, unrevoked
Does this work?
I'm at work without access to a usb cable and wonder if this is worth looking at later today.
I like this alot too bad am too bad at the shell stuff, can't this packed and flash it from recovery ?
nevermind that, I thought it's something different than normal push pull stuff.
Can do this through Root Explorer very easy and less hectic.
This doesn't work on CM 6RC1. get a wireless error can't start wireless.
I don't have the problems that my nexus logged of the wifi network while screen is off.
But when I make a ping to nexus one everything is fine when screen is on, but it become very unresponsable with screen off and has connection time out.
Is this the patch for that problem?
Can more people test this out? Some people report that the latest CM doesn't fix this issue.
kindiboy said:
This doesn't work on CM 6RC1. get a wireless error can't start wireless.
Click to expand...
Click to collapse
CM6 ships with a different kernel, so this .ko won't work for those builds. This is only for those on the stock FRF91 build who can't use the updated driver from the latest tree.
For CM6 users, it should be fixed in the latest nightlies here:
hxxp://mirror.kanged.net/cm/nightly/passion/
Formel-LMS said:
I don't have the problems that my nexus logged of the wifi network while screen is off.
But when I make a ping to nexus one everything is fine when screen is on, but it become very unresponsable with screen off and has connection time out.
Is this the patch for that problem?
Click to expand...
Click to collapse
This patch should fix this issue. The broadcom driver in stock FRF91 filters out traffic to the device when the screen is off due to a bug in the implementation that was supposed to filter out traffic to other devices instead.
I can ping my device even while the screen is off with this patch in place. You may also have to change your wi-fi sleep policy to get the best results.
mmastrac said:
This patch should fix this issue. The broadcom driver in stock FRF91 filters out traffic to the device when the screen is off due to a bug in the implementation that was supposed to filter out traffic to other devices instead.
I can ping my device even while the screen is off with this patch in place. You may also have to change your wi-fi sleep policy to get the best results.
Click to expand...
Click to collapse
Hi man, maybe you can check out the my thread about this issue here:
http://forum.xda-developers.com/showthread.php?t=731395
I hear there are people with the latest nightly build still finding the problem exists. And their MAC address starts with actually 00?
How about your case? Did your phone have this problem before and its MAC address, I suppose, begins with 38?
hbkmog said:
Hi man, maybe you can check out the my thread about this issue here:
I hear there are people with the latest nightly build still finding the problem exists. And their MAC address starts with actually 00?
How about your case? Did your phone have this problem before and its MAC address, I suppose, begins with 38?
Click to expand...
Click to collapse
My n1 has a 38:* MAC address, so I was seeing wifi disconnect almost as soon as the screen went off (and getting disabled in some cases).
There are other wifi issues on the n1 phones. This patch just fixes the worst one.
Yes, and my NexusOne has a MAC starting with 00.
WiFi doesn't disconnect, but I can't hear stream audio....
I try this fix here now.
But, what I wanna know:
Kernel updates includes this bcm***.ko, too.
Can you share your fixes, that the kernel devs can use them, too?
I tested this and seems to be working fine, thanks a lot.
Just wanted to add another thank you. I tried this and it's worked great.
Hm, it doesn't work on enoms rom.
Now I'm sad.
Formel-LMS said:
Hm, it doesn't work on enoms rom.
Now I'm sad.
Click to expand...
Click to collapse
Possibly because enoms rom is using a different kernel. I suggest you request enom to update the driver source in his rom.
Hi guys
someone can upload a modified stock (FRF91 or FRG33) with the fix?
i don't know how to fix it and i will be very grateful
thank you!!
@mmastrac
thank you
it works only on original FRF91 ROM
can you make ist for FRG33 ?
I just tested the new FRF83 (2.2.1) and it includes this fix. Pings now go through when the wifi sleep policy is set to never, as they should.
I'm not really sure about this part, but looking at the new bcm4329.ko binary it appears this patch was included:
http://android.git.kernel.org/?p=ke...ff;h=8097ca0f92819b977472381f46315de15633361c
nachod0g said:
I just tested the new FRF83 (2.2.1) and it includes this fix. Pings now go through when the wifi sleep policy is set to never, as they should.
Click to expand...
Click to collapse
Thanks heaps for confirming. I guess there isn't much stopping me from going to the new firmware other than another 1-click root method.
Related
Need some help on this.
Here are the steps that I have taken so far:
git clone git://android.git.kernel.org/kernel/experimental.git
cd experimental
git branch -r
git checkout --track -b 2.6.32 origin/android-msm-2.6.32-test1
I then have the correct 2.6.32 kernel checked out from git.
I then adb pull /proc/config.gz .
zcat config.gz > .config
export ARCH=arm
export CROSS_COMPILE=arm-eabi-
export KERNEL_DIR=/full/path/to/kernel
then:
make oldconfig
(hit enter to accept all defaults)
make
Problem is I then encounter an error on USB ether.c. I am able to comment out enough of the code to get it to compile the zImage, but after repacking using a stock boot.img ramdisk, does not boot.
Any tips on either solving the USB issue or getting the kernel to boot would be appreciated!
You can make mahimahi_defconfig to get the default android kernel config and add stuff on from there with make menuconfig. Not sure about the usb issue. Swetland said there could be issues with the .32 kernel since they just started working on it.
I used the .32 kernel over the weekend. Overall I found I got worse battery life, The auto brightness adjust doesn't work since the sensors don't work with it yet, and the button backlights were very flaky. I went back to .29 and decided to hold off on .32 till the android devs tuned it up for the N1.
Not trying to persuade you not to use it. Just wanted to let you know what my experience was.
I can confirm the issue. I just tried compiling and I get the same issue.
Code:
CC drivers/usb/function/ether.o
drivers/usb/function/ether.c: In function 'usb_ether_setup':
drivers/usb/function/ether.c:295: error: 'struct net_device' has no member named 'open'
drivers/usb/function/ether.c:296: error: 'struct net_device' has no member named 'stop'
drivers/usb/function/ether.c:297: error: 'struct net_device' has no member named 'hard_start_xmit'
drivers/usb/function/ether.c:298: error: 'struct net_device' has no member named 'get_stats'
make[2]: *** [drivers/usb/function/ether.o] Error 1
make[1]: *** [drivers/usb/function] Error 2
make: *** [drivers] Error 2
Edit:
After looking through the .config I yanked off the phone with cyanogen's addon, I found CONFIG_USB_FUNCTION_ETHER=y. I switched it to no and it has compiled fine. No clue on if it boots yet, still trying.
Sorry if this is a dumb question. But will this kernel implement more or all of the n1's available ram?
A really nice way you can test if your kernel boots without having to overwrite your old kernel is this command
fastboot boot /path/to/zImage
If it doesn't boot, you can power cycle your phone and you're back to the kernel that you had before. Once you've tested the kernel and want to flash it
fastboot flash zimage /path/to/zImage
staulkor said:
Edit:
After looking through the .config I yanked off the phone with cyanogen's addon, I found CONFIG_USB_FUNCTION_ETHER=y. I switched it to no and it has compiled fine. No clue on if it boots yet, still trying.
Click to expand...
Click to collapse
Aha. Doing that, compiling, then fastboot boot zImage worked!
Thanks all
EDIT: Wow, this thing is really really fast. Animations and overall performance while running the Nexus livewallpaper are equivalent to the 2.6.29 kernel on non-live wallpapers. Don't have working backlights on the 4 touch buttons, assume this is a lib/hw/sensors.so issue. Also can't compile the Wifi module without it erroring out as well. Looking forward to seeing rom's based on this!
jairuncaloth said:
A really nice way you can test if your kernel boots without having to overwrite your old kernel is this command
fastboot boot /path/to/zImage
If it doesn't boot, you can power cycle your phone and you're back to the kernel that you had before. Once you've tested the kernel and want to flash it
fastboot flash zimage /path/to/zImage
Click to expand...
Click to collapse
WOW that saves a lot of time! Thanks for the tip
I was using the packaging method at the bottom of this wiki page http://wiki.cyanogenmod.com/index.php/How_to_build_a_kernel_port
It that the correct method on making the correct boot.img? Whenever I tried it I couldnt get it to boot. I just did the direct zImage boot and it worked fine, nothing changed.
Edit: Got my zImage booting with the fastboot method. Haven't tried the "traditional" way. And Wow! It is so much faster with the live wallpapers. I can confirm the 4 touch button backlights dont work along with auto dim and proximity sensor. It is also still only seeing 217352 kB of ram. I saw the "High Memory" option in the .config. I will play with that and see if I can enable all 512mb on this sucker
staulkor said:
WOW that saves a lot of time! Thanks for the tip
I was using the packaging method at the bottom of this wiki page http://wiki.cyanogenmod.com/index.php/How_to_build_a_kernel_port
It that the correct method on making the correct boot.img? Whenever I tried it I couldnt get it to boot. I just did the direct zImage boot and it worked fine, nothing changed.
Edit: Got my zImage booting with the fastboot method. Haven't tried the "traditional" way. And Wow! It is so much faster with the live wallpapers. I can confirm the 4 touch button backlights dont work along with auto dim and proximity sensor. It is also still only seeing 217352 kB of ram. I saw the "High Memory" option in the .config. I will play with that and see if I can enable all 512mb on this sucker
Click to expand...
Click to collapse
Were you able to compile the wireless driver?
Yes, wireless is working fine. The module is put in drivers/net/wireless/bcm4329/bcm4329.ko. Just push it to /system/lib/modules/bcm4329.ko and reboot and your wireless should work.
staulkor said:
Yes, wireless is working fine. The module is put in drivers/net/wireless/bcm4329/bcm4329.ko. Just push it to /system/lib/modules/bcm4329.ko and reboot and your wireless should work.
Click to expand...
Click to collapse
I don't reboot after pushing the wifi driver and haven't had any trouble out of it.
jairuncaloth said:
I don't reboot after pushing the wifi driver and haven't had any trouble out of it.
Click to expand...
Click to collapse
The module is loaded when wifi is turned on, so yeah, no reboot needed. I sometimes try to turn on wifi after updating the kernel, see it fail, push the driver module, try again and off it goes.
So it does. Just tried it and what do you know
Any luck with you guys getting the sensors working?
staulkor said:
So it does. Just tried it and what do you know
Any luck with you guys getting the sensors working?
Click to expand...
Click to collapse
Unfortunately no. No light sensor also means no proximity sensor which is awful when making phonecalls.
swetland said:
The module is loaded when wifi is turned on, so yeah, no reboot needed. I sometimes try to turn on wifi after updating the kernel, see it fail, push the driver module, try again and off it goes.
Click to expand...
Click to collapse
Done that a few times as well
humancyborg said:
Unfortunately no. No light sensor also means no proximity sensor which is awful when making phonecalls.
Click to expand...
Click to collapse
I can't live without the proximity sensor
That thing has spoiled me from the cliq and now n1
TheDudeOfLife said:
I can't live without the proximity sensor
That thing has spoiled me from the cliq and now n1
Click to expand...
Click to collapse
Woah man. Been wondering what happened to you. lol You gonna be devvin' up the N1?
good work everyone now I need to remember my programming from college and such to help work out some bugs can't wait to get mine tomorrow!
Anyone know how or where the /lib/hw/ sensor files get built? Is there source available?
humancyborg said:
Anyone know how or where the /lib/hw/ sensor files get built? Is there source available?
Click to expand...
Click to collapse
Not yet. Last I checked it was a bunch of empty projects. I'm hoping they'll have it soon.
I see two new commits in the experimental tree today regarding the CM3602 (light and proximity sensor for Nexus).
Going to do a git pull and see if it works.
Also noticed that the accelerometer is not working either using 2.6.32.
EDIT: SUCCESS! Light, proximity and accelerometer sensors are now working with this new build!!
Hi all,
Inspired by the post made by crnkoj, Fix for nonworking WiFi on Simunlocked ATT Atrix 4G I decided to exploit this method and avoid the backdraws it has.
It worked very well for me on my 1.5.2, i don't see any problems with other versions as well.
Instead of restricting access to the settings.db file I decided to use db triggers to restrict changes for wifi_country_code.
The script (I modified the script from GladRoot4.2) can be found here
Many thanks to crnkoj, who came up with this solution and GladRoot team for the script.
DISCLAIMER
THIS IS ALL ON A BASIS OF INFORMING PEOPLE
I AM NOT RESPONSIBLE FOR ANY DAMAGE, LOSS OF DATA, OR BRICKED DEVICES IN CONJUNCTION OF TRYING OUT THESE STEPS
DO IT ON YOUR OWN RISK.
Instructions for the fix:
1.Do the factory reset with non-working sim in the phone.
2.Boot and register MotoBlur with wifi.
3.Switch wifi off!!!
4.Switch the device off and insert your sim card. Power the device back on.
5.Without switching on the wifi enter your MotoBlur details again (no need for internet connection).
6.Root the device.
7.Apply fix.
8.Reboot.
You should be fine. Switch on wifi and enjoy. I had to switch wifi on and back off twice to make it work.
Best regards,
Kiza
Great job Alexander!
I'm assuming this doesn't work on the Bell Atrix.
Great job Akizakian! I was looking into that way 2 weeks ago or so but i have almost no sql programming skills, so it was out of my league to do it. I think this fixes it all
I devised a better solution to this one. The problem lies in the WLAN drivers in the /system/etc/firmware/wifi/ the three binary files. I exchanged those with the driver files from the optimus lg 2x/speed and now everything works without any restrictions on the settings.db, i must test the situation if all wifi routers work with it, but i think there shouldnt be a problem, eventually someone can try to only change 1 by 1 the driver and see which one is the problem, so in the end effect the true solution would be just to exchange one driver binary. if there is interest post here so ill upload the 3 drivers i used, otherwise i wont bother, its a pretty straight forward procedure tho. oh racecar this solution should almost 100% work for the bell atrix aswell. And once the international atrix comes out and we get our hands on an international system dump/drivers we can just use that driver.
crnkoj said:
I devised a better solution to this one. The problem lies in the WLAN drivers in the /system/etc/firmware/wifi/ the three binary files. I exchanged those with the driver files from the optimus lg 2x/speed and now everything works without any restrictions on the settings.db, i must test the situation if all wifi routers work with it, but i think there shouldnt be a problem, eventually someone can try to only change 1 by 1 the driver and see which one is the problem, so in the end effect the true solution would be just to exchange one driver binary. if there is interest post here so ill upload the 3 drivers i used, otherwise i wont bother, its a pretty straight forward procedure tho. oh racecar this solution should almost 100% work for the bell atrix aswell. And once the international atrix comes out and we get our hands on an international system dump/drivers we can just use that driver.
Click to expand...
Click to collapse
There is intrest. I tried your solution using the files in my galaxy, that didnt work. wifi wouldnt even turn on. I would like to try yours.
pm me your email, ill send you the files attached. the thing is lg optimus 2x has basically the same board as moto atrix and luckyly the same broadcomm wlan/bluetooth chip with even fm radio on it....
wargame1 said:
There is intrest. I tried your solution using the files in my galaxy, that didnt work. wifi wouldnt even turn on. I would like to try yours.
Click to expand...
Click to collapse
crnkoj, this is really a great job! It's the best solution we could find! PM-ing you my email, please send me the files too.
crnkoj said:
I devised a better solution to this one. The problem lies in the WLAN drivers in the /system/etc/firmware/wifi/ the three binary files. I exchanged those with the driver files from the optimus lg 2x/speed and now everything works without any restrictions on the settings.db, i must test the situation if all wifi routers work with it, but i think there shouldnt be a problem, eventually someone can try to only change 1 by 1 the driver and see which one is the problem, so in the end effect the true solution would be just to exchange one driver binary. if there is interest post here so ill upload the 3 drivers i used, otherwise i wont bother, its a pretty straight forward procedure tho. oh racecar this solution should almost 100% work for the bell atrix aswell. And once the international atrix comes out and we get our hands on an international system dump/drivers we can just use that driver.
Click to expand...
Click to collapse
can you please send me the files, the motorola atrix wifi is not working, and non of the solution they have mentioned worked so far. email: [email protected] i hope your method can solve the problems
hello,
the method did not work, tested couple of times, however wifi refused to work period, please try to check if there is something can be done to with your patch
Have you done the factory reset before trying this method? It will not work if reset is not done.
i replaced the original wifi files with the lg optimus ones and now i cant unlock my phone(unlock swipe doesnt work) no matter how many times i pull out battery and put back... any help will be really appreciated.. thank u
i replaced the original wifi files with the lg optimus ones and now i cant unlock my phone(unlock swipe doesnt work) no matter how many times i pull out battery and put back... any help will be really appreciated.. thank u
i replaced the original wifi files with the lg optimus ones and now i cant unlock my phone(unlock swipe doesnt work) no matter how many times i pull out battery and put back... any help will be really appreciated.. thank u
Thx
great job
its working good
here is the link to a tutorial how to fix it with drivers:
http://forum.xda-developers.com/showthread.php?p=13754274#post13754274
can someone please post the wifi drivers for one of the newer htc phones (like evo 4g).. the lg optimus drivers dont seem to work here neither doe the wifi fix patch
Well obviously this is an atrix fix not an htc evo4g... it could very much me something totally else
yes
yes i have an atrix and ok i didnt know u needed drivers from a tegra 2. n im in Ghana. i keep getting a message on command prompt saying "bad mode" after i chmod to 755 or 0755..
thanks
well do such:
adb shell
su
mount -o rw,remount -t ext3 /dev/block/mmcblk0p12 /system
cd /system/etc/firmware/wifi/
chmod 755 *.bin
that must work, if you copied them over properly ...
Can anyone download for me the latest firmware with WiFi security fix from here? I need RUU_HTC Gratia_Froyo_S_HTC_WWE_2.37.405.11_Radio_47.54.35.20_7.13.35.13_release_223105_signed.exe file, but download seems locked for me, don't know why.
I just tried to download the RUU but it seems that the file is missing. Either they have removed it or it is temporarily unavailable.
Maybe somebody downloaded it and has it saved and can could upload it
What are the 6th and 7th characters in your device serial number? Those two characters are what identify which device you have. It says there is no update necessary for my serial number (which is an AT&T Aria, device code R0).
I have a Gratia, I think that's why it gives us different results. 6th and 7th places are "RJ". This is what I get when I enter my SN. When I click the download button I get a 404
Download WiFi security fix
Please click the download button below to get the WiFi security fix for your product.
Please note: This update will remove the personal data stored on your phone. Please backup all your personal data before installing this update. You can use HTC Sync to backup your phone.
RUU_HTC Gratia_Froyo_S_HTC_WWE_2.37.405.11_Radio_47.54.35.20_7.13.35.13_release_223105_signed.exe
To install the update, click download and save the file to your computer. Once the file is saved, follow these steps.
Make sure you have backed up all personal data. This update will remove all personal data from your phone.
On your phone, enable USB debugging. (From the Home screen, MENU > Settings > Applications > Development > Check USB debugging)
Connect your phone to the computer using the USB cable that came with your phone. Wait a moment for your computer to identify your phone, this may take a few minutes.
If your computer cannot find your phone, you may need to install HTC Sync. You can download HTC Sync here.
After your computer has found your phone, double click on the Update file you saved to start the process.
Follow the on screen instructions to finish updating your phone. Note! * If you encounter an error while updating your phone, it's possible that the connection to your phone was interrupted. Simply exit the program, disconnect your phone and start over.
Note! * If you encounter an error while updating your phone, it’s possible that the connection to your phone was interrupted. Simply exit the program, disconnect your phone and start over.
Fully exit the update to ensure there is no conflict of multiple instances of the program running.
Disconnect the USB cable from both the phone and the computer.
After a few moments, reconnect the USB to the computer and phone. See above if your phone or computer cannot find each other.
Run the update.
Please contact us for any additional questions.
Click to expand...
Click to collapse
drumist said:
What are the 6th and 7th characters in your device serial number? Those two characters are what identify which device you have. It says there is no update necessary for my serial number (which is an AT&T Aria, device code R0).
Click to expand...
Click to collapse
"RJ" is that characters. (for example, H T 1 2 8 R J 0 0 5 1 8, it's not my serial, but leads to the same update)
And yes, branded devices wouldn't get that update, they'll get it later.
Seems that file is absent on HTC's servers for some reasons. Well, I had reported to HTC support, and they could not say anything certain about it, just "contact to service center".
Yes, they don't like to make it easy to get certain RUUs sometimes.
If you load the frame in a new tab and click the download button it gives me this URL but still a 404.
http://dl4.htc.com/RomCode/\WiFi se...54.35.20_7.13.35.13_release_223105_signed.exe
Yep, i've found it already. Thanks nevertheless.
For now i'll wait for HTC support's answer.
Any news on this one?
gooooooooooood
Cosmo123 said:
Any news on this one?
Click to expand...
Click to collapse
I've continued conversation with support. Firstly they've sayed that that update is unapplicable to my russian Gratia, and i should go to the service center if i have any wifi issue. After some explanations (about unavailable update to non-russian but still european phones) they've promised to report to their engineers, and still recommended to contact service center. I don't know what to think about it. The situation looks pretty stupid for now. They have that update and i even know it filename (whoa!) but they don't want me to get that file for some reason.
I can only try to install stock rom to my Gratia and try to get FOTA update, if it's present as FOTA. But i don't think that it'll be successfull. BTW i can loose S-OFF in that case.
Kot_Ik said:
I've continued conversation with support. Firstly they've sayed that that update is unapplicable to my russian Gratia, and i should go to the service center if i have any wifi issue. After some explanations (about unavailable update to non-russian but still european phones) they've promised to report to their engineers, and still recommended to contact service center. I don't know what to think about it. The situation looks pretty stupid for now. They have that update and i even know it filename (whoa!) but they don't want me to get that file for some reason.
I can only try to install stock rom to my Gratia and try to get FOTA update, if it's present as FOTA. But i don't think that it'll be successfull. BTW i can loose S-OFF in that case.
Click to expand...
Click to collapse
I hope you realize that the "wifi security fix" just fixes a software bug in Sense UI. If you are running a custom ROM that is not based on HTC's Sense UI, there is no reason to apply the update.
I know, dude. I'm even use modified CM on Gratia instead of stock rom. But some times ago for some people i've made custom rom (that was based on sense) and i want to keep it updated.
Hi, anyone have this rom -> Gratia_Froyo_S_HTC_WWE_2.37.405.11_Radio_47.54.35.20_7.13.35.13_release_223105_signed.exe if yes plese upload it! I have RUU_Liberty_Froyo_S_HTC_WWE_2.32.405.1_Radio_47.52.35.18_7.13.35.05_release_154177_signed.exe
Nobody have this ROM yet. Download link is still broken.
.
Thread moved to Q&A due to it being a question. Would advise you to read forum rules and post in correct section.
Failure to comply with forum rules will result in an infraction and/or ban depending on severity of rule break.
Hi,
Has anyone got this file from the HTC website
its for HTC Gratia,
RUU_HTC Gratia_Froyo_S_HTC_WWE_2.37.405.11_Radio_47.54.35.20_7.13.35.13_release_223105_signed.exe
Update is available through link in first post. HTC fixed it.
Hello,
having the follwing problem: On my Xperia Mini Pro (sk17i) the wifi is not working anymore.
How does it show up: When enabling wifi (e.g. via gui applet) it disables immediately.
When does it happen first time: I played around with phone connected via USB to computer. At the same Time I played around with Wifi Hotspot und USB Tethering (which seemed to work). After this, wifi connected no more and I never got it working again. I know, this could be just coincidence. This happens with build 4.0.2.A.0.69.
I waited, since new ICS update has been shipped and installed it. But it had no effect. Wifi haven't worked.
Since I thought it would help to have writing access to the configuration files, I rooted the Phone and made a downgrade to buld 4.0.2.A.0.42. I installed also Android development kit on my computer. The wifi problem persists. Now there is a possibility to change files in system partition, but I have no idea, where to start with.
Attached to the post there are three log files:
dmesg.txt - Logging while running up the phone
logcat_Extraction.txt : Logging while starting wifi via applet. It shows how wifi tries to get up, runs into an exception and disables.
tiwlan.ini.txt : configuration file for wifi. (windows converted)
I'm not really deep in android/linux, but have several years programming experience with windows.
It would be kind, if anybody could give me a hint of what went wrong (configuratoin, driver, hardware fault?).
ADDED: Perhaps anybody could post a tiwlan.ini(.txt) from his/her phone (SK17i), so that I can compare it with my one?
Best regards
Horst
horst.beta said:
Hello,
having the follwing problem: On my Xperia Mini Pro (sk17i) the wifi is not working anymore.
How does it show up: When enabling wifi (e.g. via gui applet) it disables immediately.
When does it happen first time: I played around with phone connected via USB to computer. At the same Time I played around with Wifi Hotspot und USB Tethering (which seemed to work). After this, wifi connected no more and I never got it working again. I know, this could be just coincidence. This happens with build 4.0.2.A.0.69.
I waited, since new ICS update has been shipped and installed it. But it had no effect. Wifi haven't worked.
Since I thought it would help to have writing access to the configuration files, I rooted the Phone and made a downgrade to buld 4.0.2.A.0.42. I installed also Android development kit on my computer. The wifi problem persists. Now there is a possibility to change files in system partition, but I have no idea, where to start with.
Attached to the post there are three log files:
dmesg.txt - Logging while running up the phone
logcat_Extraction.txt : Logging while starting wifi via applet. It shows how wifi tries to get up, runs into an exception and disables.
tiwlan.ini.txt : configuration file for wifi. (windows converted)
I'm not really deep in android/linux, but have several years programming experience with windows.
It would be kind, if anybody could give me a hint of what went wrong (configuratoin, driver, hardware fault?).
Best regards
Horst
Click to expand...
Click to collapse
Have you wipe cache/factory reset after upgrading/downgrading your firmware?
Sent from my SK17i using xda app-developers app
Izzy Stinson said:
Have you wipe cache/factory reset after upgrading/downgrading your firmware?
Sent from my SK17i using xda app-developers app
Click to expand...
Click to collapse
Thanks for your answer.
As I used Flashtool. I selected option "Wipe Cache". Is it that, what you mean with "factory reset"? - My first hope was to solve my wifi-problem with updating or downgrading to another build version, but it had no effect on it. I thought, that the partitions with eventually damaged configuration files or invalid drivers will be overwritten by the new one. Possibly I was wrong.
Regards
Horst
horst.beta said:
Thanks for your answer.
As I used Flashtool. I selected option "Wipe Cache". Is it that, what you mean with "factory reset"? - My first hope was to solve my wifi-problem with updating or downgrading to another build version, but it had no effect on it. I thought, that the partitions with eventually damaged configuration files or invalid drivers will be overwritten by the new one. Possibly I was wrong.
Regards
Horst
Click to expand...
Click to collapse
Try to wipe data as well, and always make a backup first before messing around with CWM.
claudiod94 said:
Try to wipe data as well, and always make a backup first before messing around with CWM.
Click to expand...
Click to collapse
Yes, in Flashtool I choosed the other possible options "Wipe data", "Wipe apps log" too. After the phone has been rooted, I installed CWM for having an image from the partitions, but I saw no other way to save them completely but pull and push single files with adb.
Regards
Horst
Something strange happened after I reset my SM-R750P. Everything is working fine via Gear Manager, however the UI isn't available and as a result, I can't select or navigate to anything on the device. I am able to answer calls and receive notifications, but nothing else. I've already tried several resets, but the problem persists. I even tried flashing the rootfs.img from a stock SM-R750W since Sprint doesn't have their firmware available and no difference.
ChardC said:
Something strange happened after I reset my SM-R750P. Everything is working fine via Gear Manager, however the UI isn't available and as a result, I can't select or navigate to anything on the device. I am able to answer calls and receive notifications, but nothing else. I've already tried several resets, but the problem persists. I even tried flashing the rootfs.img from a stock SM-R750W since Sprint doesn't have their firmware available and no difference.
Click to expand...
Click to collapse
you ruined any chance of recovery when you flashed the other firmware....
Sadly...
Okay, so the device isn't dead. I need the original firmware from sprint in order to restore functionality. After doing some thorough investigations, I came across some service codes for the device and one in particular, was beneficial *#0808# I was able to put the device in debugging mode and I am able to see the logs via sdb . It seems like a lot of services/applications are not starting up correctly. The snapshot for the sdb log doesn't contain the errors. I'll attach it from my computer.
ChardC said:
Okay, so the device isn't dead. I need the original firmware from sprint in order to restore functionality. After doing some thorough investigations, I came across some service codes for the device and one in particular, was beneficial *#0808# I was able to put the device in debugging mode and I am able to see the logs via sdb . It seems like a lot of services/applications are not starting up correctly. The snapshot for the sdb log doesn't contain the errors. I'll attach it from my computer.
Click to expand...
Click to collapse
The original sprint firmware is not available.
cipherswitch said:
The original sprint firmware is not available.
Click to expand...
Click to collapse
Hey,
The watch is back in service, it seems your information regarding the SM-750J is sound. Due to the fact that this variant does not contain a SIM slot for GSM variants or the support for CDMA technology on the SM-R750P and SM-R750V, its rootfs.img did the recovery on my SM-R750P. I suspect this may work for persons that have a similar issue.
Regards,
ChardC said:
Hey,
The watch is back in service, it seems your information regarding the SM-750J is sound. Due to the fact that this variant does not contain a SIM slot for GSM variants or the support for CDMA technology on the SM-R750P and SM-R750V, its rootfs.img did the recovery on my SM-R750P. I suspect this may work for persons that have a similar issue.
Regards,
Click to expand...
Click to collapse
Wait a minute, ur saying that u successfully flashed the r750j firmware and have a fully working sprint watch???
cipherswitch said:
Wait a minute, ur saying that u successfully flashed the r750j firmware and have a fully working sprint watch???
Click to expand...
Click to collapse
Successfully flashed using the rootfs.img file, no standalone phone support (no call forwarding/data), everything else is working smoothly.
If you can make root available, I am willing to try that too. In essence, the phone is working like the Wi-Fi only model seen in the SM-R750J
..
---------- Post added at 05:36 AM ---------- Previous post was at 05:34 AM ----------
ChardC said:
Successfully flashed using the rootfs.img file, no standalone phone support (no call forwarding/data), everything else is working smoothly.
If you can make root available, I am willing to try that too. In essence, the phone is working like the Wi-Fi only model seen in the SM-R750J
Click to expand...
Click to collapse
were you ever able to get this watch back up and running. I'm currently stuck in the download mode with a message saying it couldnt do a normal boot.
Hi, yes I was able to. Which model do you have? What exactly was done to cause the issue? You may require a different solution.