Related
Hi there guys well i just installed the new Android build.. and when i have 2 sign up to google or gmail because i got gmail it wont search a internet spot...
and i got gps so i always use the WIFI.
tnx
u have to be more specific. It may be why no one has responded other than me yet.
i think he is referring to one of these:
http://glemsom.anapnea.net/android/htc-msm-android/
http://glemsom.anapnea.net/android2/htc-msm-linux/
I've been having the same problem since the beginning but nobody has really been able to figure out what's wrong. I turn on WiFi and then after a couple seconds I see an error that says "Unable to scan for networks.", and then WiFi shuts down.
^Same problem here. Wifi not working.
If you guys won't tell us what version you are using and if you got the batterie fix installed etc, then we won't be able to help you. So be more specific so we can help.
Build: [email protected]_150404
kernel:6e8abc4740a90c0a592ce9add49d8eab9f35633d Wi-Fi:12e1f9b75b92213a6b028b3ab35a6e22f7217f80
Date: Sun Jun 06 15:04:04 2010 +0200
that build doesnt have working wifi on tilt 2s...
but the droid 2.1 with launcher pro has working wifi...
you need to intall the modules that fix the wifi if you have the battery fix. its on the home site here
moto2000 said:
but the droid 2.1 with launcher pro has working wifi...
Click to expand...
Click to collapse
I installed this version of android, but also get the message:
Unable to search for networks
If you use the batterie fix you need to install the zimage AND the module. Some people (including me ) seem to forget that.
Tried it already, but still doesn't work.
"Unable to scan for networks."
well..
well what i ment was that my WIFI wont work... i got the latest version of this tread http://forum.xda-developers.com/showthread.php?t=627997 build on 1 July-2010..with launcher pro.
This is my error that says "Unable to scan for networks.", and then WiFi shuts down...
peruwan said:
well what i ment was that my WIFI wont work... i got the latest version of this tread http://forum.xda-developers.com/showthread.php?t=627997 build on 1 July-2010..with launcher pro.
This is my error that says "Unable to scan for networks.", and then WiFi shuts down...
Click to expand...
Click to collapse
Same here been have this problem from ever since i've try android, rhod 210 cant get wifi to work for the life of me.
Someone please halp.
I dont think there is a way to get wifi and battery working at the same time in GSM phones...but I could be wrong, can someone confirm?
For what its worth, I had the same problem with wifi not working. But I didn't have my sim card in yet. not having the sim card was my problem. if that's your problem you might get connected to wifi after trying my option which made everything work smoothly.
Anyone having any luck yet with this?
ijwhelan said:
Anyone having any luck yet with this?
Click to expand...
Click to collapse
the newest rootfs fixes this.
i got the new build 16/6
well i got the new build 16/6 and still no WIFI working... do i have to update before i run the xandroid?
New user here, I'm also having the exact same issue.
Phone: HTC TIlt 2 (gsm)
windows Mobile 6.5 Professional
CE OS 5.2.21849(Build: 21849.5.0.63)
CPU: Qualcomm 7201A
Rom Version: 1.59.502.3(67150)WWE
Radio Version: 4.48.25.20
-every time wifi is enabled it displays the scanning icon for a few seconds and than pops up a message saying unable to scan for networks. The message will repeat two or three more times and than wifi shuts off.
I've tried the all of the 6/16 builds (2.0.1 Eclair, 2.1 AOSP, Sense etc.) as well as the 6/06 and several of the older builds Even the 3/01 builds when wifi was first working. In fact I also tried adding the device's MAC to the startup.txt with those builds, and the current ones. I've tried battery fix free builds, so I dont think that is the issue.
I ran both a .cab install with the Project Android launcher, and the manual install booting with haret.exe.
I updated to the latest rootfs, zimage, and initrd. And I deleted my data.img after every update
I'm still using the stock rom and radio. Although I have seen other users with the same specs who have working wifi. I'd like to avoid flashing a new rom and radio to the phone if possible, but I suppose it will be my next step if i can't find any other fix.
Any thoughts on what I'm doing wrong? Did i miss something stupid?
hey everyone,
i have a strange issue and hope that someone can help me.
I use the neopeek Roms a lot and i have tried every single kernel.
But whenever the phone is in sleep mode io dont get any phone calls. the phone wakes up (red led) but thats it.
after i called my phone while it was in sleep mode it wouldnt go back into sleep mode.
i dont have this issue with the system.ext file androids.
over at neopeek.com we couldnt find a solution thats why im posting it over here.
thank you for ure help!
nick
the-nj said:
hey everyone,
i have a strange issue and hope that someone can help me.
I use the neopeek Roms a lot and i have tried every single kernel.
But whenever the phone is in sleep mode io dont get any phone calls. the phone wakes up (red led) but thats it.
after i called my phone while it was in sleep mode it wouldnt go back into sleep mode.
i dont have this issue with the system.ext file androids.
over at neopeek.com we couldnt find a solution thats why im posting it over here.
thank you for ure help!
nick
Click to expand...
Click to collapse
try pm.sleepmode=2 in your startup.txt
Eodun said:
try pm.sleepmode=2 in your startup.txt
Click to expand...
Click to collapse
We should not be using this in the newer kernels. BZO made a commit to the PLL2 code, and you should now either be using =1 or =0. I'd recommend =1 if you're OC'd, =0 if not. But not =2, assuming you're on a newer kernel (within the last 2 months I'd say...)
Also, to the OP - does this happen on FRX04 builds...? You also said you tried "every kernel" - there's some newer ones than autobuild, like 1253 - have you tried that?
hey,
thanks for your fast replies.
i already tried pm.sleep_mode 1 and 2 i have tried with and without oc.
currently im testing the FROYO B. but i have this issue with every build. ive tested every build so far. and i tried every other kernel i could find besides the autobuild. tested the 1253, the other one here at xda and the neopeek kernels.
had no luck with any kernel.
i had the same problem with the screen call ... it did not wake on any call but after i changed sleep mode to 2 it worked perfect
excuse my language
thank's man
hey,
thanks...i dunno why cuz normally pm.sleep_mode=2 shouldnt work but for some reason it does...seems to work...thanks
the-nj said:
hey,
thanks...i dunno why cuz normally pm.sleep_mode=2 shouldnt work but for some reason it does...seems to work...thanks
Click to expand...
Click to collapse
I tried sleep mode 1 and 2, still won't wake up. I also keep trying every new update between the kernel testing and the rootfs.
radcpuman said:
I tried sleep mode 1 and 2, still won't wake up. I also keep trying every new update between the kernel testing and the rootfs.
Click to expand...
Click to collapse
Are you overclocking? Assuming you're using a fairly new kernel, you should either be using 1 or 0 for the sleep_mode setting.
arrrghhh said:
Are you overclocking? Assuming you're using a fairly new kernel, you should either be using 1 or 0 for the sleep_mode setting.
Click to expand...
Click to collapse
No overclock. I have the latest test kernel and even today's rootfs update.
Here is my startup.txt.
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 msmts_calib=0x9f.0x39a.0x35c.0x78 msmvkeyb_toggle=off pmem.extra=1 gsensor_axis=2,1,3 rel_path=andboot north_am_dialing=0 force_cdma=0 hw3d.force=0 physkeyboard=tilt2 pm.sleep_mode=0"
boot
I tried sleep_mode=1 earlier. If the LED is flash green, it doesn't wake up. I only started using the test kernels because non test stuff was doing the same thing. Everything else is working great since I turned off the GPS settings.
Would the incoming call issue be something that could be seen in log files by chance?
radcpuman said:
No overclock. I have the latest test kernel and even today's rootfs update.
Here is my startup.txt.
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 msmts_calib=0x9f.0x39a.0x35c.0x78 msmvkeyb_toggle=off pmem.extra=1 gsensor_axis=2,1,3 rel_path=andboot north_am_dialing=0 force_cdma=0 hw3d.force=0 physkeyboard=tilt2 pm.sleep_mode=0"
boot
I tried sleep_mode=1 earlier. If the LED is flash green, it doesn't wake up. I only started using the test kernels because non test stuff was doing the same thing. Everything else is working great since I turned off the GPS settings.
Click to expand...
Click to collapse
There's some old deprecated commands in there. I highlighted them in red.
Also, why are you disabling hw3d? In addition, why do you have the north_am_dialing statement in there if it's set to 0? Also, I would definitely switch the sleep mode to 1.
What system image are you using? FRX04? I don't have this issue whatsoever, assuming the phone is doing OK (no SoD condition, no pegging proc, etc) the phone always wakes up for calls...
Have you tried deleting your data.img?
arrrghhh said:
There's some old deprecated commands in there. I highlighted them in red.
Also, why are you disabling hw3d? In addition, why do you have the north_am_dialing statement in there if it's set to 0? Also, I would definitely switch the sleep mode to 1.
What system image are you using? FRX04? I don't have this issue whatsoever, assuming the phone is doing OK (no SoD condition, no pegging proc, etc) the phone always wakes up for calls...
Have you tried deleting your data.img?
Click to expand...
Click to collapse
I'm using FRX04. Most of the setting except for pm.sleep_mode came from the startup utility. I have deleted the data.img once. I've even re-sized it to 769mb.
With the latest kernel image and rootfs I haven't had any issues except the dpad backlight stays on for a long time and incoming call issues. Then after a while will return to normal.
Should I take the hw3d out or set it to 1?
radcpuman said:
I'm using FRX04. Most of the setting except for pm.sleep_mode came from the startup utility. I have deleted the data.img once. I've even re-sized it to 769mb.
With the latest kernel image and rootfs I haven't had any issues except the dpad backlight stays on for a long time and incoming call issues. Then after a while will return to normal.
Should I take the hw3d out or set it to 1?
Click to expand...
Click to collapse
You can either take the hw3d statement out, or set it to one - they both should have the same effect.
There is no 'dpad' on the TP2. Do you mean the 4-button row at the bottom...? If those lights are on at boot, they will stay on in Android, so make sure they do not turn on at boot. Basically get the phone in portrait mode and wait until the button lights go dark.
Please try your data.img again. You can simply rename it, this is just a test - that file gets messed up and causes odd effects, this might be one of those instances.
arrrghhh;11295243
Please try your data.img again. You can simply rename it said:
Thanks for you help arrrghhh!
I renamed the data.img. Started it up, signed in to my google account to sync contacts. Waited for it to go to sleep, then called the phone. The LED went to amber, but didn't wake up and ring. I have the sleep_mode set to 1. I set the 3d setting to 1.
Click to expand...
Click to collapse
** Notice **
There are 2 new kernels out K011 & K012 that are supposed to fix the deep sleep issue. If you are using a ROM that does not include one of these new Kernels please do not continue reporting deep sleep issues on them. Contact your ROM developer and get them to update the ROM with the new kernel. You could try another ROM with the new kernel's included or try the fixes mentioned further down in this post.
Mainly interested in now is reports of deep sleep issue with K011 and K012. Thanks out to everyone for their help with this bug hunt.
**********
Time to find out what those of us who have no deep sleep when running the custom kernels have in common. Even if you don't have any problems with Deep Sleep, your input would be appreciated as it could help eliminate items. If you can think of anything else we can add let me know and I'll update this Post. If possible please attach the same information as I have below as it would help greatly in determining what phones that absolutely can not get deep sleep with the FreeXperia Custom Kernel have in common. When posting possible solutions please indicate if you have had problems getting deep sleep before or not.
Update - I've added a count at the front of each line to count the number of submittal's for that line. As Items are eliminated from confirmed working deep sleep users I'll change the font color to red.
Update 2 - Thread has grown beyond my ability to keep up so I'm Just going to but a synopys at the bottom. If you believe that any of my assumptions there are incorrect, please PM me with the details so I can keep this information as accurate as possible
When reporting deep sleep problem or working include the following information
-------------------------------------------------------------
Phone Information from under battery
Sony Ericsson 10a
Type: AAD-3880074-AV AAAB
FCC ID PY7A388074 CB5
IC: 4170B-A3880074 10W20
Carrier Information
1 Rogers Wireless
GSM/GPRS/EDGE on the 850 and 1900 MHz bands
UMTS/HSPA on the 850 and 1900 MHz bands
ROMS tried using custom kernel with deep sleep issues
All FreeXperia ROMs from V014 to V021
[ROM][MAY24]BlackEditionHD_1.4_SE[Gingerbread 2.3.4]
Base ROM's tried
Rogers 2.1 stock ROM
Generic X10a build 2.0.A.0.504
Generic X10i build 2.0.A.0.504
Baseband's tried
Base .52
J's custom .52
Base .49
Base .46
Mini-Boot versions tried
V1
V2
V3
Factory Unlocked No
-----------------------------------------------------------------------
Here is what I've been able to determine so far
Majority of X10a have Deep Sleep problems
Majority of X10i are able to obtain Deep Sleep in some way.
So far everyone reporting unlocked phones have deep sleep (Incorrect, some don't have deep sleep)
Possible solutions if you are having deep sleep issues
1. Install V2 or V3 of the mini-loader from the custom kernel thread (DoomLoRD) Link
2. Try the Screen Off Fix (9Lukas5) Link
3. Manually select your network operator. (The Gingerbread Man) Link
4. After fully charging the phone to 100%, reboot after disconnecting (DoomLoRD) Link
5. Un-check automatic updating in date & time settings. (Temoi19) Link
6. (My_Immortal) has a solution If it's the dialer keeping your phone awake. Link
#5 is what finally worked for me. If any of these fixes have worked for you make sure to thank whomever came up with it by following the link to their original post.
** BREAKING NEWS **
J has just posted in his CM7 thread.
small progress
weems that we have found the deep sleep issue
not shure for now but we will provide an baseband togherther with J003
this combination seems to fix deepsleep for all testers
ETA 24h to be shure
Click to expand...
Click to collapse
The new Rom release is now available in the second post here. The Kernel included does not include overclock so if you want overclock you'll have to download K012 from the first post.
Here are the known issues posted by J in his thread. Please note the items for Deep Sleep and make sure to apply them before reporting any deep sleep issues.
KNOWN BUGS
-after reboot USB mass storage is not working if USB in plugged (unplug/replug USB to fix)
-if you still have deepsleep bug disable autotime update and automatic network
-deepsleep appers only when device is not connected to USB and corect baseband is used
Click to expand...
Click to collapse
Nice one buddy, great idea, i do not suffer from deep sleep so will edit my post later with my results, do you want the date the phone was manufactured.
I ALWAYS HAVE HAD DEEP SLEEP.
*Sony x10i
*Type AAd-3880056-bv aaac
*FCC ID PY7A3880056 CB5
*IC 41708_A3880056 10w13
*manufacture date year 2010 week 13
Using 3UK, HSPA, i have tried only Jerpelea's roms and had deep sleep on every one, my generic rom used is Sony Ericsson X10i_2.1.A.0.435_X10i and i use J's bb52 but it works also for me on bb49/sony bb52.
My only other point is that my phone was factory unlocked which may be another good point.
For those that don't know how to tell the manufacture date its under the battery and is shown like mine as 10W12, 10 being the year 2010 and W12 is week 12 of that year so April.
Apps that are very active in background prevent my device from going to deepsleep. Like MSN Talk Pro, PowerAMP and idk what more. I dont think its hardware related.
Sent from my X10i using Tapatalk
smartgardens said:
Nice one buddy, great idea, i do not suffer from deep sleep so will edit my post later with my results, do you want the date the phone was manufactured.
Click to expand...
Click to collapse
Great idea!! Now just where would I find that info?
PlayGunsta said:
Apps that are very active in background prevent my device from going to deepsleep. Like MSN Talk Pro, PowerAMP and idk what more. I dont think its hardware related.
Sent from my X10i using Tapatalk
Click to expand...
Click to collapse
I've actually tried this from a fresh install, with only CPU Spy installed and still I didn't have deep sleep. I'm saying it's hardware related as it could just as well be provider related.
GreatBigDog said:
Great idea!! Now just where would I find that info?
Click to expand...
Click to collapse
No idea sorry, Doomlord should know, it is under the battery somewhere, iv'e looked but can not make it out.
Hi guys, no deep sleep, no matter what
Edit: i received from Tim-br...
X10a Sensuous Black
Mobile Phone GSM/GPRS/EDGE 850/1800/1900
UMTS/HSPA band 1/2/5/6
Type: AAD-3880074-AV AAAB
FCC ID PY7A388074 BY9
IC: 4170B-A3880074 10W21
This is my post in J's thread...
I'm trying to fix deep sleep issue since J release v21 final, but no success.
My steps:
* usual (wipe everything, install update.zip, BB from package.)
* v2 e v3 miniloader (one in each clean install)
* repair with seus (after that clean install of bb from package and rom)
*flash many se 2.1 firmware (after that clean install of bb and rom)
* clean install and bb .49.
*battery calibration (full charge "off line", wipe battery stats)
*applied patch "when screen off "
*no apps installed (in each installation, JUST CPU spy from market, without gapps.
*another formatted sdcard
*wifi set to "when screen off " or wifi disabled.
*GPS and bt disabled.
*tried adw or arc launcher
No DEEP SLEEP. (Just work with airplane mode active)
Sent from my X10 using XDA App
michaeljordam said:
Hi guys, no deep sleep, no matter what
This is my post in J's thread...
I'm trying to fix deep sleep issue since J release v21 final, but no success.
My steps:
* usual (wipe everything, install update.zip, BB from package.)
* v2 e v3 miniloader (one in each clean install)
* repair with seus (after that clean install of bb from package and rom)
*flash many se 2.1 firmware (after that clean install of bb and rom)
* clean install and bb .49.
*battery calibration (full charge "off line", wipe battery stats)
*applied patch "when screen off "
*no apps installed (in each installation, JUST CPU spy from market, without gapps.
*another formatted sdcard
*wifi set to "when screen off " or wifi disabled.
*GPS and bt disabled.
*tried adw or arc launcher
No DEEP SLEEP. (Just work with airplane mode active)
Sent from my X10 using XDA App
Click to expand...
Click to collapse
Can you edit your post please to add the information asked for in the first post. We are trying to find something in common between all of our phones.
GreatBigDog said:
I've actually tried this from a fresh install, with only CPU Spy installed and still I didn't have deep sleep. I'm saying it's hardware related as it could just as well be provider related.
Click to expand...
Click to collapse
Yes I tried the same earlier, its just a matter of finding something we have in common, what it is I don't know.
Ok guys just done some testing cm7.03 and disappointing results, atleast for me.
Flashed bb.49, wiped everything in recovery. Fresh install of v21 and flashed v2 miniloader (no reboot in between) and signed into Google, allowed it to sync contacts no Google restore, no gmail, skipped install of Google apps. I have only installed CPU spy through market. Nothing restored through titanium.
My SD card is being a SOB and for some reason thinks I have no pics on my card, so possible issue there so it wont allow me to upload the screenies I just took but I managed 9 seconds of deep sleep after leaving the phone alone after my install as described for maybe about 2 - 2.5 hours. Baseband.49 with v2 miniloader isn't the answer I'm affraid atleast for me. Tomorrow will try same kind of install but using v3 mini loader.
Edit; no luck sorry
Sent from my X10 using XDA Premium App
GreatBigDog said:
Can you edit your post please to add the information asked for in the first post. We are trying to find something in common between all of our phones.
Click to expand...
Click to collapse
Edited, my last post. I see small diferences between you and me.
i don´t remember what bb came with phone, but i gues was .46.
I´ll try that now....
.49 don´t fix deep sleep.
How come we havn't asked those with deep sleep working to make a nandroid backup from xrecovery and upload it so we all can try it out?
SkyStars said:
How come we havn't asked those with deep sleep working to make a nandroid backup from xrecovery and upload it so we all can try it out?
Click to expand...
Click to collapse
Good idea, worth a try, i will do one tomorrow if nobody has done it before, think i will just check with Jerpelea first if that's ok by him.
Edit .... I will just pm a few with it rather upload it.
Sent from my X10 using XDA Premium App
Great! let us know how that goes.
I guess I'm a bit behind on what this even is.. What is the deep sleep? I know sleep mode and hibernation on a PC, but how do I know if my phone has it or does it?
CPU spy from market
highaltitude said:
I guess I'm a bit behind on what this even is.. What is the deep sleep? I know sleep mode and hibernation on a PC, but how do I know if my phone has it or does it?
Click to expand...
Click to collapse
Sent from my X10i using XDA App
Deep Sleep is sort of like Stand-by mode on your PC, it will wake up by its own to sync mail and do whatever and then go back to sleep. Without deepsleep you will lose 5-10% battery an hour just idling instead of just 1% for every 5-10 hours.
GreatBigDog said:
I've actually tried this from a fresh install, with only CPU Spy installed and still I didn't have deep sleep. I'm saying it's hardware related as it could just as well be provider related.
Click to expand...
Click to collapse
Ok just tired another fresh install on bb.49 this time using miniloader v3. Same testing.g environment as mentioned in cm7 thread. It seems impossible for me.
Ok guys just done some testing cm7.03 and disappointing results, atleast for me.
Flashed bb.49, wiped everything in recovery. Fresh install of v21 and flashed v2 miniloader (no reboot in between) and signed into Google, allowed it to sync contacts no Google restore, no gmail, skipped install of Google apps. I have only installed CPU spy through market. Nothing restored through titanium.
My SD card is being a SOB and for some reason thinks I have no pics on my card, so possible issue there so it wont allow me to upload the screenies I just took but I managed 9 seconds of deep sleep after leaving the phone alone after my install as described for maybe about 2 - 2.5 hours. Baseband.49 with v2 or v3 miniloader isn't the answer.
Sent from my X10 using XDA Premium App
Does anybody have an unlocked phone that they could try a sim card from another provider with? I've tried a 2nd one from the same provider but my phone is locked so I can't try a different one.
cm 7.0.3 - bypass v3
I tried a different simcard today and got deepsleep on it but I also had deepsleep with my usual simcard until it hit 15 % battery. Maybe losing deepsleep had to do with coming out of airplane mode on my device. I couldn't restore it and tried everything written in the other thread.
I gave the hardware - software cause some thoughts. I don't think it is hardware related. Sony would never upgrade to GB if it would be hardware related but I remember they said that they had some trouble with GB and the kernel.
Anyways I use the same apps on J's GB that I used on freex10 and i have absolutely no problems with deepsleep. The problem must reside within the Kernel, bypass or GB since lots of people even get the no deepsleep on a fresh install or lose it after some time.
Also drivers are not complete like camera and proximity. I would guess that there are still lots of incompatibilities that could also be the cause for something like that. Maybe some piece of hardware doesn't get addressed right or something. Figuring out what would be the cause exactly is way out of my league.
Just some 5 cents from me.
Regards
No deepsleep here for the past 3 or 4 versions of J's kernel (didn't try any before that).
Phone info:
Code:
Sony Ericsson X10a
Type: AAD-3880074-AV ACAM
FCC ID: PY7A3880074 CB5
IC: 4170B-A3880074
MoP 1233-8309.10 SI 1237-4604
Manufacture Date: 10W33 (August 2010)
Made in China
Network info:
AT&T
HSPA
WCDMA preferred
(Sorry, don't know where to find the same network info you posted).
ROMs:
Only use Z's FreeX10 B4 - Hotfix 1 (with CM settings)
Basebands:
.49
.52
J's .52
Bootloader bypass versions:
V1
V2
V3
Running services:
Code:
XPERIA Flashlight; Process: jp.co.telemarks.ledlightx10
LedLightWidgetService
Digital clock; Process: com.sonyericsson.digitalclockwidget
DigitalClockService
Market; Process: com.android.vending
AlarmService
HTC_IME mod; Process: jonasl.ime
HTC_IME mod
Misc:
FreeXperia Recovery
I keep Wifi/3G turned off unless I am using them, so they shouldn't be causing an issues.
Not using any SetCPU profiles/task killers/OC APPS/UV APPS/UV modules
I do get deep sleep in airplane mode (only tested for 2 minutes, but that was 2 minutes more than I've gotten any other time).
Perhaps a radio is keeping the CPU running?
Not sure if anyone else has seen this issue. I have been having Wifi issues with almost all GB ROMs. Wifi will be working fine then just drop off and reconnect randomly. This happens while I am using it and not while sleeping. I have confirmed this with Vegan 7.1, GHarmony, and the Flash* version from Slatedroid. I do not remember having this issue with CM7, but didn't like the ROM so I changed. I really want to switch to GB but this is a show stopper. Anyone thoughts?
Update to the latest Pershoot kernel. That has some fixes for this.
If the problem still persists, try downgrading your WiFi firmware blobs.
Note, however, that the causes of WiFi drops are many. Some troubleshooting will be needed to find out the exact cause of your problem.
Thanks for the recommendations. I tried newer kernel and downgrading the Wifi blobs. Still no go. The odd thing is this only happens with GB ROMs, all Froyo ROMs are fine, and it seems to be limited to my home Wifi, which is WPA/WPA2, at work with LEAP it doesn't happen. Going to try changing some settings on my WIFI this weekend. To compare Flashpoint from Slatedroid works fine, but the GB version Flashlight has the problem. Also going to try the older Vegan 7 on 1.2 bootloader, i don't remember this happening on that or CM7 build 86.
See if this helps: It doesn't.
Code:
$ [B]su[/B]
# [B]wpa_cli -i wlan0 driver setsuspendopt 1[/B]
[I]Wait 15 secs[/I]
# [B]wpa_cli -i wlan0 driver setsuspendopt 0[/B]
Sorry most of this is greek to me as I am a NOOB. Have Gtab 3588 1.1 vegan 7.?
all of a sudden I can't connect to wifi, all my other devices at home work fine. Getting a disabled connection from home, have tried re-adding, rebooting, reseting rom, reinstalling Vegan.
I sorry I need step by step help
thx Jaye
markmac said:
Not sure if anyone else has seen this issue. I have been having Wifi issues with almost all GB ROMs. Wifi will be working fine then just drop off and reconnect randomly. This happens while I am using it and not while sleeping. I have confirmed this with Vegan 7.1, GHarmony, and the Flash* version from Slatedroid. I do not remember having this issue with CM7, but didn't like the ROM so I changed. I really want to switch to GB but this is a show stopper. Anyone thoughts?
Click to expand...
Click to collapse
I think it has to do with the AES encryption key updates and the gingerbread wifi libs. Take a look at this post to see how you can change your router settings to prevent or minimize this.
http://forum.xda-developers.com/showpost.php?p=18035185&postcount=144
gtabowner said:
Sorry mosy of this is greek to me as I am a NOOB. Have Gtab 3588 1.1 vegan 7.?
Click to expand...
Click to collapse
Exact version?
all of a sudden I can't connect to wifi, all my other devices at home work fine. Getting a disabled connection from home, have tried readding, rebooting, reseting rom, reinstalling Vegan.
Click to expand...
Click to collapse
As I said in post #2, above:
Note, however, that the causes of WiFi drops are many. Some troubleshooting will be needed to find out the exact cause of your problem.
Click to expand...
Click to collapse
However, you can:
1. Try upgrading to the latest pershoot kernel. Since you're on Vegan 7 (a Gingerbread ROM) and the 1.1 bootloader, go to http://droidbasement.com/db-blog/ and download this file boot-cm_2632.46_gb-oc-uv-xtra-vfp_fp-083111.zip from there. Copy the zip file onto your gtab, then install it using CWM.
2. If the upgraded kernel doesn't help try downgrading the firmware blobs using the link in post #2. Use the Cyanogenmod zip file.
3. If neither of the 2 steps above work, then follow this post and get me some logs.
As i thought,i have tried Vegan 7.0 and the problem is not occuring. I did have an issue with the new market but i just rolled back to original and removed the market updater. Seems like the issue is related to the 2.3.5 versions of ROMs.
rajeevvp said:
Exact version?
As I said in post #2, above:
However, you can:
1. Try upgrading to the latest pershoot kernel. Since you're on Vegan 7 (a Gingerbread ROM) and the 1.1 bootloader, go to http://droidbasement.com/db-blog/ and download this file boot-cm_2632.46_gb-oc-uv-xtra-vfp_fp-083111.zip from there. Copy the zip file onto your gtab, then install it using CWM.
2. If the upgraded kernel doesn't help try downgrading the firmware blobs using the link in post #2. Use the Cyanogenmod zip file.
3. If neither of the 2 steps above work, then follow this post and get me some logs.
Click to expand...
Click to collapse
will try this today
Thank you again. when I can get in I will find out what exact Vegan and such i am using. What info do you need? and exactly where do I find it. It says 7.0.0 when booting up
Thank you all again.
gtabowner said:
What info do you need? and exactly where do I find it. It says 7.0.0 when booting up
Click to expand...
Click to collapse
Fine, then you have a Gingerbread ROM. Just follow the instructions in post #7, above, and see if each step helps.
If steps 1. and 2. don't help you, use the instructions in the link in step 3. to get me logs which will help me troubleshoot your problem.
rajeevvp said:
If steps 1. and 2. don't help you, use the instructions in the link in step 3. to get me logs which will help me troubleshoot your problem.
Click to expand...
Click to collapse
HI,
I hope this thread is still active as I'm having very similar issue. It has started 2-3 weeks after I got my gTablet and flashed it. The usual scenario is this:
1. Reboot
2. Immediate connection to wifi
3. Starting using internet - immediate disconnect
4. After several minutes of constant connect/disconnect finally connected
5. From now it works for a few minutes, then disconnect, then reconnects, works again, disconnects again etc.
What I have already tried:
1. Changing wifi channel - no difference
2. Changing security (wpa, wep, none) - no difference
2. Downgrading blobs - no difference
3. Installing new kernel - that seem to stabilize reconnection (it reconnects more often and more reliable)
At home I'm runnig netgear WNDR3300 router with ddwrt installed. I've also tried public RoadRunner access point in the gym but the result is the same.
I'm starting to think it is a hardware problem but would like somebody to verify that. Any help greatly appreciated. Log files are attached.
Thanks,
Janusz
1. As per the logs your access point seems to be returning an invalid lease time (-1 seconds). Change the DHCP lease time to 3600 seconds (1 hour) and get me another set of logs.
2. Why does your Netgear wireless router broadcast 2 SSIDs, "PL" and "PLN" ?
My DHCP lease time was set to set to 1440 minutes (minutes is the only available unit here). I don't remember changing that so it must be a default one. I can change it to 60 minutes and rerun logs.
My router has 2 radios. I need to keep WEP encryption for my linksys internet radios that don't support WPA. Originally I only had one radio turned on with WEP but once I started getting problems with gtablet I played with different settings. Now I'm running both radios. PLN is WPA encrypted with G only connection on channel 11 and PL is WPA b/g on channel 4. They don't interfere with each other and turning one of them off or on didn't make a difference for gTablet.
Janusz
New set of logs after chaning DHCP lease time to 60 minutes. Disconnects seem to be less frequent and they reconnect almost immediately. My previous post should say that PL radio is set to WEP, not WPA.
Thanks a lot,
Janusz
januszk said:
New set of logs after chaning DHCP lease time to 60 minutes. Disconnects seem to be less frequent and they reconnect almost immediately.
Click to expand...
Click to collapse
Change the WPA Group Rekey Interval to a different value (I have it set to 1800 seconds) then reboot both the router and the gTablet. The new set of logs show that the gTab is having trouble connecting to the Netgear.
See also this post for another setting which you can try tweaking.
Done. Was set to max 99999. Still disconnects, hard to say if less or more often then before (although works way better then yesterday). New logs attached.
Thanks,
Janusz
januszk said:
Done. Was set to max 99999. Still disconnects...
Click to expand...
Click to collapse
The latest set of logs show that the gTablet is still having problems connecting to the Netgear router:
Code:
gTablet$ [B]su[/B]
gTablet# [B]logcat -d -v time | egrep -i 'connectivity|dhcp|wpa|wifi|wlan'[/B]
...
10-21 12:51:13.406 E/ConnectivityService( 1048): Attempt to connect to WIFI failed.
...
I also see that the tablet is trying to connect to SSID 'PLN'. The first set of logs had it connecting to SSID 'PL'.
Suggestions:
1. Go back to the default values for Wireless LAN Settings on the wireless router--except for the ones we changed in this thread.
2. Delete the WiFi connection from the gTablet, reboot, then set up a new connection (only for SSID 'PLN').
3. For this new connection, set the no. of channels to 11 channels--ie US channel settings. (Advanced WiFi settings)
4. Turn off any "Network Notification" in WiFi settings.
5. Go back to the stock firmware on the wireless router instead of dd-wrt.
...hard to say if less or more often then before (although works way better then yesterday). New logs attached.
Click to expand...
Click to collapse
It's still disconnecting pretty regularly. Subjective judgements can be erroneous, so use the script (attached) that I use to check these things. After making the script (which needs busybox) executable and moving it into /data/local/bin, run it like this inside a Terminal Emulator window:
Code:
gTablet$ [B]dmesg | d.awk[/B]
[63636.011275] STA connect received 1
[66204.696828] STA connect received 1: 42m 48s
You can also pass one of the previously collected dmesg*.txt files through the script:
Code:
gTablet$ [B]d.awk /mnt/sdcard/dmesg2.txt[/B]
<4>[ 33.513973] STA connect received 1
<4>[ 215.890648] STA connect received 1: 3m 2s
<4>[ 396.218500] STA connect received 1: 3m 0s
<4>[ 576.546805] STA connect received 1: 3m 0s
<4>[ 757.899052] STA connect received 1: 3m 1s
<4>[ 938.227396] STA connect received 1: 3m 0s
Thanks a lot. I'll try some of those. I'll get my tablet to one of my friends to see if this will work better with other routers. I've already tried leaving only PLN connection but it didn't make any difference. The reason why latest logs were primarily PLN were because if "forgot" settings for PL. You have suggested to change WPA key renewal and this setting is only for PLN, thats why I removed PL, which is WEP. I may try resetting to defaults but I don't really want to go back to stock firmware as it has been reported by many as buggy and unstable. Its dd-wrt that puts new lifie into it. I have the whole bunch of other wifi devices at home and everything works perfectly.
I'll also give your script a try to see where I stand at.
BTW: Do you think it may be hardware problem? I don't think the BT/WIFI module is easily replacable without replacing the whole motherboard.
In the meantime I really appreciate your help so how can I buy you a beer?
Janusz
januszk said:
BTW: Do you think it may be hardware problem?
Click to expand...
Click to collapse
Nothing in the logs indicate that this is hardware-caused. Other people, including me, have faced this before without hardware issues, so it is very likely a software problem. Our gTablet does not work well with some kinds of wireless routers. I have a software fix working on my gTab which I am in the process of testing. I'll send it upstream after I'm satisfied that it doesn't inadvertently break other things.
In the meantime I really appreciate your help so how can I buy you a beer?
Click to expand...
Click to collapse
Make a donation to your favourite charity instead--or buy a beer for a friend.
OK, will do
I've installed your custom awk script. Disconnects are every few minutes or so, well I'll live with it for now and try another router. When you have your fix ready sign me up for a beta testing.
Thanks again,
Janusz
I have been using epinter's CM10.1 for Atrix 4g and following the Atrix 4g CM10.1 developer discussions. I am trying to get the camera flash to work. krystianp posted that one should extract from CM9, the files tcmd and tcmdhelp and put in /system/bin. But I cannot find a CM9 for the Atrix 4g (olympus) that has these files. Does anyone know where to find them? (Would have posted to the CM10.1 thread but don't have permission to do so.)
Search fo his cm9. It should have the libs you are looking for. Also, z's one shot cm10.1 might have them as well
Hit the damn thanks button instead!
Enviado desde mi MB860
Thanks
andresrivas said:
Search fo his cm9. It should have the libs you are looking for. Also, z's one shot cm10.1 might have them as well
Hit the damn thanks button instead!
Enviado desde mi MB860
Click to expand...
Click to collapse
Thanks... Downloading a CM9 from krystianp now. I was thinking of trying to get from z's one shot if that didn't work. (And yes I did hit the thanks button ). Now on to see if putting these files in /system/bin will actually get the flash to work. The only post I could find from someone who tried it suggests "no".
The problem I've been having is the flash not flashing at all when the "shutter" button is pressed. Instead the phone light comes on when I press the "focus" button and goes off when released (unless I've selected "no flash"). Seems like for other people the flash works but timing is off.
rhcohen said:
Thanks... Downloading a CM9 from krystianp now. I was thinking of trying to get from z's one shot if that didn't work. (And yes I did hit the thanks button ). Now on to see if putting these files in /system/bin will actually get the flash to work. The only post I could find from someone who tried it suggests "no".
The problem I've been having is the flash not flashing at all when the "shutter" button is pressed. Instead the phone light comes on when I press the "focus" button and goes off when released (unless I've selected "no flash"). Seems like for other people the flash works but timing is off.
Click to expand...
Click to collapse
I placed those files but flash is still not working, maybe you have better luck :fingers-crossed:
reply
Feche said:
I placed those files but flash is still not working, maybe you have better luck :fingers-crossed:
Click to expand...
Click to collapse
No, no better luck here. Copied files to /system/bin, changed permissions to 755, verified owned by root like other files in the directory, rebooted. Same behavior as before.
Did you try Krystianp's 12/31 kernel, which apparently has flash working for some? I downloaded it but haven't flashed it yet out of concern for the bad battery drain noted by someone.
rhcohen said:
No, no better luck here. Copied files to /system/bin, changed permissions to 755, verified owned by root like other files in the directory, rebooted. Same behavior as before.
Did you try Krystianp's 12/31 kernel, which apparently has flash working for some? I downloaded it but haven't flashed it yet out of concern for the bad battery drain noted by someone.
Click to expand...
Click to collapse
I currently have it installed, the flash with stock camera app doesn't work, but with CameraMX flash works fine. :good:
reply
Feche said:
I currently have it installed, the flash with stock camera app doesn't work, but with CameraMX flash works fine. :good:
Click to expand...
Click to collapse
For what it is worth, I just installed the 12/31 kernel and the flash with stock camera app now DOES work for me*, and the timing even seems to be OK. So someone ought to be interested in understanding the difference between your configuration and mine. (If anyone is actually following this, my sequence, executed over the past week or so, was a wipe/clean install of epinter's 12/11 CM10.1 rom, followed by his latest gapps, followed by a second flash of the 12/11 rom. Then this morning putting the tcmd and tcmdhelp files in /system/bin, with appropriate permisssions; and then finally flashing krystianp's 12/31 kernel.) Too soon to comment on battery life.
I think this kernel is supposed to be logging network disconnects (which I also seem to experience, about one a day, requires reboot to reconnect). Do you know where we find the resultant logs, and how (lacking permissions to post at the developers' site) we are supposed to deliver them to krystianp? I notice that, in response to a submitted log file, krystianp made a post about restarting the radio from a terminal, which didn't actually achieve a re-connection for the one person who tried it.
* small update: the flash works with stock app, but only if I do a spot ("touch") focus first. Small price to pay!
Great to know its working! As fir that "thanks" thing, it's my signature from tapatalk, nothing personal
As for the logs, on either cm9 or cm10 forum krystianp gave instructions on how to get those logs. One is dmesg and the other logcat, but can't remember exact commands
Hit the damn thanks button instead!
Enviado desde mi MB860
reply
andresrivas said:
Great to know its working! As fir that "thanks" thing, it's my signature from tapatalk, nothing personal
As for the logs, on either cm9 or cm10 forum krystianp gave instructions on how to get those logs. One is dmesg and the other logcat, but can't remember exact commands
Hit the damn thanks button instead!
Enviado desde mi MB860
Click to expand...
Click to collapse
Thanks --- so I found the relevant krystianp post on the logs:
http://forum.xda-developers.com/showthread.php?p=48954198&highlight=dmesg#post48954198
Specifically,
"To get kernel log just do (as root):
dmesg>/sdcard/kernel.log
And for radio log do:
logcat -b radio >/sdcard/radio.log
(Logcat works continuously so you might have to use ctrl+c to cancel it) "
Question is, what do I do with these logs? I could attach them to a reply at the developer forum if I had permission to reply....
Presumably I don't want to keep running this kernel with debugging turned on forever.
You can attach they here and nention krystianp so he get notified
Hit the damn thanks button instead!
Enviado desde mi MB860
reply
andresrivas said:
You can attach they here and nention krystianp so he get notified
Hit the damn thanks button instead!
Enviado desde mi MB860
Click to expand...
Click to collapse
Thanks, I will wait a couple of days so there is some accumulated info in the logs and do that. So far, no drops and one spontaneous reboot.
reply, to forward to krystianp
andresrivas said:
You can attach they here and nention krystianp so he get notified
Hit the damn thanks button instead!
Enviado desde mi MB860
Click to expand...
Click to collapse
OK, attached are kernel.log and radio.log (combined into the file atrixlogs.tar). Hopefully someone notifies krystianp.
Here is what they represent: I installed krystianp's kernel two days ago. Since then I have had two spontaneous reboots, and two more reboots that I initiated because in the first case the radio died; in the second case the radio didn't die (still had bars) but there was no data connection. In both cases rebooting restored full functionality.
Note in the case where the radio died, I went to no bars and stayed there; then when I tried turning airplane mode on and off, the network status symbol in the status bar disappeared (no triangle at all, rather than having an empty triangle).
Krystianp had suggested trying to stop/restart the radio from a terminal when the network drops; I did not try this as I was away from my computer and so did not have access to the instructions for the terminal command.
I hope these logs are of help.
rhcohen said:
OK, attached are kernel.log and radio.log (combined into the file atrixlogs.tar). Hopefully someone notifies krystianp.
Here is what they represent: I installed krystianp's kernel two days ago. Since then I have had two spontaneous reboots, and two more reboots that I initiated because in the first case the radio died; in the second case the radio didn't die (still had bars) but there was no data connection. In both cases rebooting restored full functionality.
Note in the case where the radio died, I went to no bars and stayed there; then when I tried turning airplane mode on and off, the network status symbol in the status bar disappeared (no triangle at all, rather than having an empty triangle).
Krystianp had suggested trying to stop/restart the radio from a terminal when the network drops; I did not try this as I was away from my computer and so did not have access to the instructions for the terminal command.
I hope these logs are of help.
Click to expand...
Click to collapse
have you tried turning radio on and off from testing tab from dialer *#*#4636#*#* then select phone info scroll down and there is a tab to turn radio off and on. saves time from a reboot.
You should have mention him by @krystianp . Not sure it will work from the phone
Hit the damn thanks button instead!
Enviado desde mi MB860
RE turning radio off and on
overboard1978 said:
have you tried turning radio on and off from testing tab from dialer *#*#4636#*#* then select phone info scroll down and there is a tab to turn radio off and on. saves time from a reboot.
Click to expand...
Click to collapse
No I haven't tried this. Does this do something different from krystianp's suggestion from Jan 2 at the 10.1 developer thread :
echo "shutdown" > /sys/class/radio/mdm6600/command
echo "powerup" > /sys/class/radio/mdm6600/command
which, per reply post from Feche (also Jan 2), succeeds in starting up the radio but not making a connection?
further update
rhcohen said:
No I haven't tried this. Does this do something different from krystianp's suggestion from Jan 2 at the 10.1 developer thread :
echo "shutdown" > /sys/class/radio/mdm6600/command
echo "powerup" > /sys/class/radio/mdm6600/command
which, per reply post from Feche (also Jan 2), succeeds in starting up the radio but not making a connection?
Click to expand...
Click to collapse
----------
OK I have a further update. Using the testing tab from the dialer gives me the option of turning the radio off; when I click it nothing changes -- in particular no option to turn the radio on.
When I try krystianp's echo "shutdown" and echo "powerup" commands, I get a system prompt back but no indication that anything has changed with the radio (though maybe it would be reflected in the radio logs). In any event, certainly no connection to the network.
With regard to including @krystianp in the mssage -- where am I supposed to include this (to get the log files to him)?
rhcohen said:
----------
With regard to including @krystianp in the mssage -- where am I supposed to include this (to get the log files to him)?
Click to expand...
Click to collapse
Doesn' t it appear as a link to his user profile? go there and select
Code:
send message -> send a private message to krystianp
.
I don't see a place to attach a file to the message, but you can link to this thread.
reply; and what is "uv"?
PolesApart said:
Doesn' t it appear as a link to his user profile? go there and select
Code:
send message -> send a private message to krystianp
.
I don't see a place to attach a file to the message, but you can link to this thread.
Click to expand...
Click to collapse
-------------
Thanks. Sending the logs may no longer be relevant; @krystianp posted a new kernel a day and a half ago. I flashed it yesterday, and so far, no radio drops. If I get any I will post another message with logs and also send a message to krystianp.
I notice in describing the new kernel he says he made changes to radio and UV. Can someone tell me what is UV? I tried a search in the 10.1 developer forum and a more general google search but find nothing useful (I suspect this use of "UV" does not mean "ultra-violet".)
As of today, he said the last kernel just adds more debug information. for me it didn't work for much time, with random reboots, probably caused by UV changes. UV is shorthand for "undervolting", an attempt to lower voltage to cpu (and perhaps some other devices) in order to preserve battery and generate less heat.
reply
PolesApart said:
As of today, he said the last kernel just adds more debug information. for me it didn't work for much time, with random reboots, probably caused by UV changes. UV is shorthand for "undervolting", an attempt to lower voltage to cpu (and perhaps some other devices) in order to preserve battery and generate less heat.
Click to expand...
Click to collapse
I saw today's post but didn't interpret it the same way. He had already said that this kernel, along with the one from 12/31, were for people with the disconnect errors (which I was getting), but when he posted the Jan 5 kernel he indicated there were changes to radio and UV; I thought today's notice was just reaffirming the purpose of both the 12/31 and 1/5 kernels.
The 12/31 kernel clearly did more than just turn on logging however, as it seems to have fixed the camera flash for many (including me).
And the 1/5 kernel seems to be working more stably for me -- 1 1/2 days now without a radio drop. Maybe just luck.