I am using a G-Tablet TNT Lite 4.2.2, other than that, nothing special.
I noticed that when I leave the tablet alone for about 10 minutes I am forced to turn OFF the wireless then turn it back ON again for it to work.
It still shows as connected but nothing works until I restart the connection.
If I am actively browsing or using RDP it does not disconnect me.
The WiFi sleep policy is set to 'never'
There is no difference if the device is plugged in or not.
Two different G-Tablets on two different wireless networks; same problem.
The problem existed with previous versions of TNT Lite (I think I started with 4.0)
I've scoured the forums and have not found any answers.
Has anyone else heard of this problem?
I have this too when I put mine to sleep or leave it sitting for a while.
Same on mine, running Vegan. It's quite the pain in thine arse. I haven't found a fix either. I'll watch this thread though. Maybe someone has an answer.
OK. Many months later... still no solution. I now run an ACER Iconia as my primary tablet but still use my Viewsonic gTablet on a regular basis.
I have tried many different ROMs and have experienced the same problem. Do I really have a defective device?
-me- said:
OK. Many months later... still no solution. I now run an ACER Iconia as my primary tablet but still use my Viewsonic gTablet on a regular basis.
I have tried many different ROMs and have experienced the same problem. Do I really have a defective device?
Click to expand...
Click to collapse
Have you tried one of the newer kernels? The ones that come with ROMs are, sometimes, quite old.
My wireless usually drops off when I use the dock to recharge without using wifi at the same time, and usually does not drop wifi if it's not on the dock. Vegan 5.1.1.
Yes. I am currently running:
Flashback 7.2
Android 3.01
WiFi Version : unknown
Kernel Version : 2.6.32.43-cyanogenmod
[email protected] #1
Build Number: Gtablet
-me- said:
Yes. I am currently running:
Flashback 7.2
Android 3.01
WiFi Version : unknown
Kernel Version : 2.6.32.43-cyanogenmod
[email protected] #1
Build Number: Gtablet
Click to expand...
Click to collapse
Try Flashback 8.0 or Pershoot .46 kernel
Dave,
I used nVflash, took it back to stock 1.2 4349 ROM,
Then proceeded to install Flashback 8. During the process I wiped all data, formatted to 4090:0 then back to 2048:0. Flashback 8 is working great.
The wireless seems a bit better... I can leave it 15 minutes and it was still working. But, if I bring the gTablet out of a screen sleep, the wifi shows as still connected, but the bars are grey instead of blue. I cannot browse the internet until I shut off the wireless, then turn it back on.
I will try some experiments today and tomorrow to see if I can narrow down the possibilities.
Please know that I am very grateful for your input!
Get me a dmesg output please.
1. Reboot the gtab
2. Run a Terminal Emulator app (get one from Market if needed), then type:
Code:
$ [B]dmesg > /mnt/sdcard/dmesg.txt[/B]
3. Attach that dmesg.txt file here.
Hi.
I took two snapshots.
One with the wireless working... and the second when it was 'grey' or stuck needing a reset.
(I had to wrap them into a single rar file because I was not able to attach more than one file to this message)
-me- said:
I took two snapshots.
One with the wireless working... and the second when it was 'grey' or stuck needing a reset.
Click to expand...
Click to collapse
I can see plenty of NAND flash-related errors in those kernel messages, but, the WiFi looks clean.
As a first test, re-install Pershoot's latest kernel for 1.2 bootloaders, then run these commands, then reboot and see if there is a difference:
Code:
[I]Become superuser.[/I]
$ [B]su[/B]
[I]Mount /system read-write.[/I]
# [B]mount -w -o remount /system[/B]
[I]Get rid of redundant files.[/I]
# [B]rm -f /system/etc/nvram.txt /system/lib/modules/nvram.txt[/B]
[I]Copy pershoot's WiFi kernel module into the correct dir. for HC.[/I]
# [B]mv /system/lib/hw/wlan/bcm4329.ko /system/lib/modules/.[/B]
[I]Backup the Flashback-supplied WiFi firmware blobs.[/I]
# [B]mv /system/vendor/firmware/fw_bcm4329.bin /system/vendor/firmware/fw_bcm4329.bin.orig[/B]
# [B]mv /system/vendor/firmware/fw_bcm4329_apsta.bin /system/vendor/firmware/fw_bcm4329_apsta.bin.orig[/B]
[I]Move pershoot's firmware blobs into the correct dir. for HC.[/I]
# [B]mv /system/lib/hw/wlan/fw_bcm4329* /system/vendor/firmware/.
[/B] [I]Remount /system read-only again[/I]
# [B]mount -r -o remount /system[/B]
If your WiFi is not better, get me another dmesg output and also a logcat output:
Code:
$ [B]su[/B]
# [B]logcat -d -v time > /mnt/sdcard/logcat.txt[/B]
For the su command to work, you will need the Superuser app from Market (if it's not already installed).
Hi rajeevvp,
I reloaded everything... I am running the latest 2.6.32.46 kernel.
After entering the commands you listed then a reboot, the wireless is still dropping off. I captured the logcat.txt (which I've attached)
I had the device 'forget' my wireless credentials, then re-added them, I get my wifi back, it has the same effect as turning off then on the wifi.
One more thing I am going to try is to use another wireless router. Who knows, maybe it will help.
Re: "I can see plenty of NAND flash-related errors in those kernel messages, but, the WiFi looks clean."
» I saw those as well. I am a little concerned. I wonder if it is just a glitch or is the flash memory failing?
Thank-you!
P.S. The logcat.txt was greater than 87.9 KB so I had to rar it.
-me- said:
One more thing I am going to try is to use another wireless router. Who knows, maybe it will help.
Click to expand...
Click to collapse
This is a good idea. Also a good idea--while we're testing this--to set both the WAP and the tablet to use DHCP-assigned IP addresses and enable wireless authentication (if they're not already so)--to WPA2-PSK w/AES.
Re: "I can see plenty of NAND flash-related errors in those kernel messages, but, the WiFi looks clean."
» I saw those as well. I am a little concerned. I wonder if it is just a glitch or is the flash memory failing?
Click to expand...
Click to collapse
We'll come back to this later.
P.S. The logcat.txt was greater than 87.9 KB so I had to rar it.
Click to expand...
Click to collapse
The rar file was missing the dmesg output. Get me new logs with both the dmesg and logcat outputs like this:
1. Reboot tablet.
2. When the tablet has stabilized at the desktop, open a Terminal Emulator window and type:
Code:
gTablet$ [B]log -t _me_ "Tablet booted"[/B]
If the WiFi is working, type:
Code:
gTablet$ [B]log -t _me_ "WiFi working"[/B]
When the WiFi stops working, type:
Code:
gTablet$ [B]log -t _me_ "WiFi stopped working"[/B]
The commands above insert your own log messages into the Android logging subsystem. You can add any additional commentary you feel is important. This way, I can see what happened when. The last logcat output didn't seem complete for some reason--certain log messages were not present.
3. Once the WiFi's stopped working, run both the dmesg and the logcat commands already given.
4. After this, try configuring the WiFi interface manually--ie. independently of Android--and get me the output from each command:
Code:
Become superuser
gTablet$ [B]su[/B]
Check state of the WiFi interface
gTablet# [B]busybox ifconfig wlan0[/B]
Check default routes
gTablet# [B]busybox route -n[/B]
Manually configure static IP address
gTablet# [B]busybox ifconfig wlan0 192.168.111.151 netmask 255.255.255.0[/B]
Manually add a default route to the Internet
gTablet# [B]busybox route add default gw 192.168.111.1[/B]
Check if the WiFi i/f has been configured
gTablet# [B]busybox ifconfig wlan0[/B]
Check if the default route was set up
gTablet# [B]busybox route -n[/B]
Then ping both your gateway (192.168.111.1) and Google's DNS server (8.8.8.8). Both should work. We're trying to determine if yours is an Android problem or a general system (kernel/drivers/HW) problem.
I followed your instructions exactly. I have included the two files. They should be complete.
I pinged both google and my router when the wireless dropped off and both of them returned:
....
From 192.168.111.151 icmp_seq=x Destination Host Unreachable
etc...
-me- said:
I followed your instructions exactly. I have included the two files. They should be complete.
Click to expand...
Click to collapse
Nope. Still not useful. From the log messages, it looks like about 30 mins had passed (and the tablet had gone to sleep at least once in that interval) before the problem occured. Is this correct?
Does the problem only occur when the tablet comes out of sleep? Can you try reproducing the problem while keeping the tablet awake? If you can't, then in settings > WiFi Settings, set your WiFi to off (go to mobile data) when the display does. This way, when the tablet goes into its deep sleep mode, the WiFi is turned off, and forceed to re-initializ when you press the power button to wake it up.
I pinged both google and my router when the wireless dropped off and both of them returned:
....
From 192.168.111.151 icmp_seq=x Destination Host Unreachable
etc...
Click to expand...
Click to collapse
Was this after configuring the IP address manually using the commands I have or before? If it is before then the error message shown is to be expected.
What did those commands output when you ran them?
Hi rajeevvp.
Thank-you for taking the time to help me.
I don't think the tablet went to sleep... and it had been running about 30 minutes. I had the screen set to never go to sleep and wireless set to 'never' as well.
I did try the WiFi off (more mobile data) method with the same result.
The tablet was actively being used, but not for anything that required the internet.
The ping results were after I had used the commands. I had not restarted the gTablet after entering the commands.
Thanks to your input, I started thinking that the gTablet might not be to blame.
This morning, I rebooted the device... and I hooked up a WAP54g. I have been using a Linksys WRVS4400Nv2 router for a long time and expected that if the router had no problems with any of my other devices that it could not be to blame.
It has been about three hours and it has not yet disconnected from the WAP54g. If it is still working tonight, I'll connect back to the Linksys N and see if it stops again. I'll report back what I find.
-I've always used WPA2 w/AES
-me- said:
I don't think the tablet went to sleep... and it had been running about 30 minutes.
Click to expand...
Click to collapse
That's odd. I can see the kernel repeatedly trying to suspend and someone then waking it up by pressing the power button. This switches the screen on and then 60 seconds later it switches off again (timed out at the lockscreen?). A few minutes later, the power button is again pressed, and this time, the tablet wakes up fully, then the system starts killing processes because its getting low on memory.
It has been about three hours and it has not yet disconnected from the WAP54g. If it is still working tonight, I'll connect back to the Linksys N and see if it stops again. I'll report back what I find.
-I've always used WPA2 w/AES
Click to expand...
Click to collapse
Keep me informed. Thanks.
Thank-you for all your help.
Wireless worked all day long without a disconnect. After dinner I connected back to the Linksys WRVS4400Nv2 and within 5 minutes... wifi disconnect. Connected back to the WAP54G and the problem goes away. I am embarrassed that I did not try this sooner. If someone had suggested it, I would have tried it. The problem is solved.
Now... nVflash errors. Should I start a new thread?
mydave1 said:
Try Flashback 8.0 or Pershoot .46 kernel
Dave,
Click to expand...
Click to collapse
Hey OP!
I would highly agree with this suggestion... just sayin'.
The stock ROM is remarkably underwhelming. I think you will be happy with this. Just known in advance the camera does not work.
Related
Ok all here is my problem and I know there many more suffering from this:
Connecting to the internet from my Hero works fine on 2G (GPRS) and Wi-Fi, but is very unstable on 3G (UMTS) and H (HSDPA).
By starting a thread, I want to get to an answer as to WHY this is happening and hopefully find a solution
My problem started around the time I started using custom 2.1 (or radio) ROMs, but I am not sure whether flashing those is actually the cause. I have a SIM unlocked Hero and an unlimited data plan with T-Mobile Netherlands (called Web 'n' Walk Plus @ 1 Mbit/s down, 384 Kbit/s up). I had no problem on the stock 1.5 ROM/radio.
Symptoms:
Whenever an app is making a server request, the 3G icon starts blinking the up arrow, shortly followed by the H icon blinking the up arrow, indicating the request is made.
When all is well, the response is received and communication is quick and smooth. Most of the time though, the phone continues making requests but no response is received and the application reports a network error/timeout. This happens while signal strength is max (4 bars).
Ping test:
Enter *#*#INFO#*#* in the phone dialpad and select Phone Information, press the "Run ping test" button.
- The line "Ping IpAddr" reports: "Fail: IP addr not reachable";
- The line "Ping Hostname(www.google.com)" reports: "Fail: Host unreachable";
- The line "HTTP Client test" reports: "Fail: IOException".
The preferred network type is "WCDMA preferred", as set in the lower part of the same screen.
Note: WCDMA is an air interface standard used for UMTS and the like and is not related to CDMA, which is the mobile access technology used in the USA as opposed to GSM, which is used everywhere else in the world.
The thing is though, that the connection does not seem to fall back to 2G but rather experiences a timeout.
FWIW: the Phone Information screen reports a signal strength of -dBm, 25 asu.
Tried:
- Flashing various ROMs to spot any difference, none found.
- Flashing newer radio ROM (JU instead of EU), no luck.
It is here when I first start posting about it:
http://forum.xda-developers.com/showthread.php?p=6099325#post6099325
Other cases that seem to point at the same problem:
http://android.modaco.com/content/h...93937/hero-strange-3g-data-connection-problem
http://forum.xda-developers.com/showthread.php?t=547563
http://forum.xda-developers.com/showthread.php?t=616475
http://support.t-mobile.co.uk/discussions/index?page=forums&topic=8010384abbabde01276d5f3caa005e2d
I hope that anyone experiencing the same post his or her findings, so that we can try to detect a pattern and maybe the solution to this.
UPDATE: Apparent solution for T-Mobile 3G problems:
http://forum.xda-developers.com/showthread.php?t=595108
Fix includes settings as proposed by adwinp below.
Explanation of some settings: http://forum.xda-developers.com/showpost.php?p=5123531&postcount=46
UPDATE 2:
Well, my problems have vanished "as snow in the sun" (old Dutch proverb)!
Applying the latest radio (JU) and the settings as mentioned by adwinp below made my 3G connection fly again, steady and smooth. Thanks adwinp!
How to modify your build.prop file:
1) Connect your handset via USB, make sure USB debugging is enabled
2) From the Android SDK > tools directory, type the following:
Code:
# adb pull /system/build.prop ~/build.prop
3) Open the file with your favorite editor and append the following lines:
Code:
ro.ril.enable.dtm=1
ro.ril.hep=1
ro.ril.hsxpa=2 #for USA, use 1
ro.ril.gprsclass=12 #for USA, use 10
ro.ril.enable.a52=1
ro.ril.enable.a53=1
ro.ril.hsdpa.category = 28
ro.ril.hsupa.category = 7
Save the file. Next:
Code:
# adb remount
# adb push ~/build.prop /system/build.prop
# adb reboot
Some sources claim that a second reboot is necessary, check this for yourself.
Good luck!
UPDATE 3:
Seems my joy was short lived; could be that just rebooting was a temporary fix and a good old placebo effect, since I already experienced connection loss again. Sigh. Anyone else with a good idea?
UPDATE 4:
Could this be an MTU issue, like stated here or here? I'd like to know the methods of changing the MTU for 3G, investigating now.
UPDATE 5:
None of the theories above seem to be plausible. Looks like T-Mobile/Orange is the culprit here. Further reading here: https://t-mobile-forum.pocketinfo.nl/showthread.php?p=725207#last (in dutch)
You have either a
1: physical problem with the handset
2: network problem (check if other ppl within the same network have the same problem)
Try playing with these values in /system/build.prop
ro.ril.enable.dtm = 1 # you might want to disable this one, although it doesn't hurt
ro.ril.hep = 1
ro.ril.hsxpa=2
ro.ril.gprsclass=12
ro.ril.enable.a52=1
ro.ril.enable.a53=1
ro.ril.hsdpa.category = 28
ro.ril.hsupa.category = 7
# Default network type 0 => WCDMA Preferred.
ro.telephony.default_network = 0
These settings come from my ROM, which has been tested on various networks in Poland, Germany and Mauritius.
3G performance is flawless.
I have been having this very same problem, and I know others have too. it is strange but has only happened since the newer 2.1 builds have been out.
After lengthy conversations with the high technical team at Orange UK they diagnosed my problem as for some reason the phone is trying to connect to two 3g radio towers at the same time (usually should connect to only one) basically this is confusing the phone.
What the fix seems to be is:
- *#*#4636#*#*
- phone options
- ping test (will probably fail)
- change to "GSM ONLY" - for 30 seconds or more NOT LESS!!
- ping test (should succeed)
- then change back to "WCDMA Only" or "preferred"
- ping again (should now work)
If this does not fix it then you have two more options
- take the sim out the phone for 30 seconds (this is the minimum required time to disconnect your phone from the towers your on)
- OR airplane mode for 30 seconds.
Then try the above again and all should be working.
adwinp said:
Try playing with these values in /system/build.prop
Click to expand...
Click to collapse
As a professional software developer, I always get an itch when I am advised to 'try playing', I need to know if something is working or not
ro.ril.enable.dtm = 1 # you might want to disable this one, although it doesn't hurt
ro.ril.hep = 1
ro.ril.hsxpa=2
ro.ril.gprsclass=12
ro.ril.enable.a52=1
ro.ril.enable.a53=1
ro.ril.hsdpa.category = 28
ro.ril.hsupa.category = 7
# Default network type 0 => WCDMA Preferred.
ro.telephony.default_network = 0
Click to expand...
Click to collapse
Do you have any reference information for these settings? I'll try to look it up myself but I can't fiddle with them unless I know what the possible values are and at least know what each setting is used for
Lennyuk said:
After lengthy conversations with the high technical team at Orange UK they diagnosed my problem as for some reason the phone is trying to connect to two 3g radio towers at the same time (usually should connect to only one) basically this is confusing the phone.
Click to expand...
Click to collapse
Interesting reason; you think this could be related to the fact that the latest VillainROMs stem from CDMA ROMs? What I still don't get is that speech and GPRS traffic are unaffected, these just work.
I already tried your fixes several times but for me they don't work everytime. Ah well, hopefully the official 2.1 update does some good here
j0bro said:
Interesting reason; you think this could be related to the fact that the latest VillainROMs stem from CDMA ROMs? What I still don't get is that speech and GPRS traffic are unaffected, these just work.
I already tried your fixes several times but for me they don't work everytime. Ah well, hopefully the official 2.1 update does some good here
Click to expand...
Click to collapse
Possibly however my problems first seemed to start after the Legend based roms.
j0bro said:
Interesting reason; you think this could be related to the fact that the latest VillainROMs stem from CDMA ROMs? What I still don't get is that speech and GPRS traffic are unaffected, these just work.
I already tried your fixes several times but for me they don't work everytime. Ah well, hopefully the official 2.1 update does some good here
Click to expand...
Click to collapse
I don't think a CDMA source is the issue here.
I've ported a CDMA to GSM with no problem whatsoever.
You could always try replacing libreference-cdma-sms.so, libreference-ril.so, libril.so and libhtc_ril.so from a GSM ROM.
Im also on T-mobile NL with unlimited web n walk
i dont have that issue, and i am currently on aHero 0.7 with latest radio,
also havent encountered the problem on other 2.1 roms
i hope this is some additional information
I always run into this problem as well on all of the 2.1 ROMS pretty much. I'm on the 3 network in the UK. Basically I never had this problem with any of the modaco 1.5 ROMS.
Awesome. Thankyou!
This has fixed my annoying 3G issues, Exactly as you describe.
What exactly is the solution?
Update 2 - First post.
Previously browsing maps would stall and the "up" arrow be stuck on, with the "down" one empty. I say maps, but anything really that uses the data connection. Most often going into Airplane mode and back again fixed it. Now it just works, and quickly too.
BTW - I'm on orange UK.
ChrisCoooo said:
Update 2 - First post.
Previously browsing maps would stall and the "up" arrow be stuck on, with the "down" one empty. I say maps, but anything really that uses the data connection. Most often going into Airplane mode and back again fixed it. Now it just works, and quickly too.
BTW - I'm on orange UK.
Click to expand...
Click to collapse
So just adb those values into the build.prop file and now everything is fine?
Yep. Thats basically all I did, I did a remount, pulled the build prob to my local, edited it, then pushed it back.
First reboot then I had connectivity, but the status bar showed it not being registered on the network. Second reboot and it was all good. A consitent 3G/H signal and no stalling of data transfers.
ChrisCoooo said:
Yep. Thats basically all I did, I did a remount, pulled the build prob to my local, edited it, then pushed it back.
First reboot then I had connectivity, but the status bar showed it not being registered on the network. Second reboot and it was all good. A consitent 3G/H signal and no stalling of data transfers.
Click to expand...
Click to collapse
I edited my OP, since I experienced connection loss again. How is it holding up for you?
Great topic J0bro.
I am having exactly the same problems as you describe. I was just searching the web since at first i couldn't find anything usefull here. I just went back to see if there were some new rom updates and i saw this topic.
I am now running villain 5.2 and latest radio. I was already experiencing the same probs a while back but not as much as i am now. It seems that when I try to open an app on the market i get a lot of connection errors. The switching between the 3g and H takes too long and times out.
I now have a stream running on stream live radio and that uses my H connection. Once it is continuously using H it seems just fine......
Strike that italic part.... When i was typing that it disconnected went back to 3G and lost connection. Now its switching back and forth between 3G and H
Damn this sucks man. I will try the part of of the build.prop....
Pff and i just got my debricked hero back
FYI I am on t-mobile NL with web n walk plus
Did you try replacing the ril libs I mentioned in /system/lib ?
Did you test this in another city?
adwinp said:
Did you try replacing the ril libs I mentioned in /system/lib ?
Did you test this in another city?
Click to expand...
Click to collapse
Just put it underneath the rest in the build.prop and rebooted twice.
Did I do that right?
Hi there which 2.1 Rom did u try?
On tmobile UK and had same 3g problem with stock rom but its fixed now. Only been testing with villainroms. Version 3.4 and 5 beta2 works perfect, the legend based one doesn't work and has same 3g problems. So its probrqbly not universal across 2.1 roms
Re: [2.1 ROMs] Unstable 3G/H connection but 2G and Wi-Fi are fine
i'm on villain 5.2
Sent from my Hero using the XDA mobile application powered by Tapatalk
Hi! I'm having serious problems with the wifi on my phone in stock global 2.1. Two weeks or so ago it started to not connect (or better say not initialize) to wifi, giving "Unable to start wifi..." message. Sometimes it connected and a while after it wouldn't let me continue browsing, connecting to Market or refreshing Facebook widget, although it still being as connected.
I decided first to restore my phone to defaults, but that did not work. Then I reflashed using X10 Flash Tool, but again with the same problems. So after that I decided to flash using PC Companion (thinking that this may miraculously resolve all). Now I'm here suffering from an "unable to connect" phone.
I've taken a log using dmesg just after this problems have come up. maybe there could be an answer to this. I'f there's a better way to log this, please tell me.
Any advice?
"2.815328] Using very old AMSS modem firmware."
Is the issue just at home or out and about?
Sorry but I don´t understand what you mean. Looking at that log it seems that something goes wrong and it shuts down just after trying to init:
"<4>[ 51.871484] ar6000_readwrite_file: file /sys/devices/platform/msm_sdcc.2/detect_change filp_open error -2"
Also, you can see this more clearly from:
"<4>[ 6163.536082] Normal WIFI mode." (line 2361)
_SpAiK_ said:
Sorry but I don´t understand what you mean.
Click to expand...
Click to collapse
I don't understand what it means either, which is why I asked if it's just at home or out and about.
Doh! Sorry, it happens everywhere. I've tried in open and secured wifis.
Hi, this looks like the issue I have, did you had any luck fixing it?
http://forum.xda-developers.com/showthread.php?p=12882017
Hi, yesterday I managed to have wifi working for at least an hour, when it normally lasts few minutes before it freezes. It was set to "never" in the "disable wifi policy", so I went to dinner and when I was back it was disconnected. Then it was not capable of getting connection again.
I have Blade Wifi Fix installed and it seems to do something. Anyway you could try to set wifi to static ip, let it connect and wait until freezes, then set it to automatic ip and reconnect. It worked for me, at least for a while. I may try again and post a logcat.
Anyway there's another threat here (see second page) where I have some more info about the problem.
Hey any luck figuring out the problem? Im still without Wi-Fi
Hope I'm not duplicating anything, but there seems to be a lot of BT related questions and none answered in one unified place. Also I think the BT Dev thread should be left to the devs (to keep it easier for them to work on things, rather than help us mere mortals ).
This applies to CM7 (latest nightlies, Tablet Tweak RCs) ONLY (as far as I know).
So, if bluetooth does not turn on, there a few things that you can try.
Do a HARD reset (that is, hold down the power button until the NookColor turns off, then start it back up.
Fix Permissions in ClockworkRecovery:
Boot into CWR (w/SD, load it in. With CWR installed on eMMC, go to ROM Manager > Reboot into Recovery. Alternatively, hold down the power plus "N" button for ~8 seconds (from a shutdown NookColor).
Try both!
An interesting thing to note is some users (myself included) can only start up bluetooth within a pretty short window of time after the NC has booted up. Not sure why timing is important, but could be a factor for those who cannot start up BT after some given time of operation.
I found this tip that may work after a fresh (read: wipe system/data) install, but may also work after flashing a nightly over a nightly.
If you're ready to turn on Bluetooth, there's a trick. If you don't do this, Bluetooth will just refuse to turn on / be enabled.
Turn off wifi (Settings > Wireless & Networks > Wi-Fi)
Reboot
Turn on Bluetooth (Settings > Wireless & Networks > Bluetooth)
Turn on wifi
It seems a bit odd, but that's what you have to do. From then on out it'll work fine.
Click to expand...
Click to collapse
Credit here (step 2)
For a list and description of devices that work with the NC, check this out:
Known functional Bluetooth devices
For tethering data via BT, try android-wifi-tether. While it can be used to create an access point on your phone via wifi, you can also opt to use BT to create the tether. This works well in conjunction with TetherGPS which I use to provide GPS info to the NC from my G1 while using CoPilot Live to show navigation (I don't have data on the G1).
If you have the BT enable problem try this kernel and let me know if it changes anything:
http://forum.xda-developers.com/showpost.php?p=12683824&postcount=1754
dalingrin said:
If you have the BT enable problem try this kernel and let me know if it changes anything:
http://forum.xda-developers.com/showpost.php?p=12683824&postcount=1754
Click to expand...
Click to collapse
Tried that previously and it did not work for me.
In other words, it works as with all the kernels I've tried (your OC'd and stock kernel): it will start up if I start is quickly, but otherwise not.
ace7196 said:
Tried that previously and it did not work for me.
In other words, it works as with all the kernels I've tried (your OC'd and stock kernel): it will start up if I start is quickly, but otherwise not.
Click to expand...
Click to collapse
me too. I went back to 4/4 since them. If I leave BT on all the time, it is on when I boot, but if I turn off BT and reboot, it won't come on without a hardboot (holding down power.)
Fix permissions is NOT needed, just a hard boot.
dalingrin said:
If you have the BT enable problem try this kernel and let me know if it changes anything:
http://forum.xda-developers.com/showpost.php?p=12683824&postcount=1754
Click to expand...
Click to collapse
For the last few days Ive been trying to get BT working w/ my car stereo, using phiremod 5.3
I have no problems enabling Bluetooth (first time I had to reboot a few times and fix permissions)
With it flat against the stereo, I'm 'paired but not connected' and getting it to actually connect usually takes 4 - 5 tries.
After its connected- when I try to play any kind of music, it gets stuck every few seconds- and stays stuck for more than a few seconds (like 10) and plays again.
I just downloaded this kernel, (wiped caches, fixed permissions again) and it connected on the second time, and only got 'stuck' once for maybe 2 seconds, and played the rest of the song with no problems.
Seems like it changed something on my end...
Just figured I'd mentioned it.
(I can go back to the other kernel, or a different version of cm7, and see if I get the same connecting/ stuttering problem, if you thing it would help)
Btw- thanks so much for sharing all of your hard work!
breebauer said:
After its connected- when I try to play any kind of music, it gets stuck every few seconds- and stays stuck for more than a few seconds (like 10) and plays again.
I just downloaded this kernel, (wiped caches, fixed permissions again) and it connected on the second time, and only got 'stuck' once for maybe 2 seconds, and played the rest of the song with no problems.!
Click to expand...
Click to collapse
I dont' know if anyone who's building from source wants to take a look at this patch committed 3 days ago on the omapzoom tree to frameworks/base, but it seems to address a bluetooth corruption problem.
Can anyone who's using the copilot app tell me exactly how to get it set up? I can get the GPS signal to the nook but then I get an error about an invalid imei number.
Sent from my NookColor using Tapatalk
Calla969 said:
Can anyone who's using the copilot app tell me exactly how to get it set up? I can get the GPS signal to the nook but then I get an error about an invalid imei number.
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
Check out this posting:
http://forum.xda-developers.com/showthread.php?t=1024963
I believe you also need the Bluetooth GPS Provider app from the market.
Calla969 said:
Can anyone who's using the copilot app tell me exactly how to get it set up? I can get the GPS signal to the nook but then I get an error about an invalid imei number.
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
Never had an issue with the IMEI number, but here's how I got it setup.
Start with the TetherGPS app running server on the phone and client on the NC, as well as tether-wifi from google running on the phone, then connect to the AP on the NC
Next, open/install the app. It should read the GPS data from the phone
Now, switch back to a wireless connection with internet access, download the voice, then enter the serial/etc...
Finally, load the app back up after all the registration stuff 'n things, and use the "internet" connection from the phone to grab the GPS info.
Copied and edited from cm7 user thread.
I have xoom bluetooth keyboard with disconnect issues. Would the special kernel help with this?
From the accessories thread. "I found a work-around. Download the app Bluetooth Keyboard JP, change the settings in settings > Language and Keyboard to that app, then connect the keyboard." Anybody else try this or others? Blue Input is another one. I know of one more but can remember its name.
I'm running Phiremod v5.3 cm7 from emmc and cm7 nightlies from sd card. I usually have a data sd card but can switch it out. I have updated the cm7 sd card before. Not sure which nightly and OC I used last. Could use ClockWorksMod to flash this kernel to Phiremod v5.3. Could replace the kernel, uImage, on the SD card. Usually there are different kernels for emmc and sd card.
Another issue: When I have the keyboard active and playing flash files from the internet, it seems to buffer more. If I move the keyboard out of range or use settings to disconnect the keyboard, the buffering is less and the flash files play better. I have cyfi bluetooth external speakers. When I use them I get the same buffering issue, so I just use an external player through the headphone jack instead.
ace7196 said:
Never had an issue with the IMEI number, but here's how I got it setup.
Start with the TetherGPS app running server on the phone and client on the NC, as well as tether-wifi from google running on the phone, then connect to the AP on the NC
Next, open/install the app. It should read the GPS data from the phone
Now, switch back to a wireless connection with internet access, download the voice, then enter the serial/etc...
Finally, load the app back up after all the registration stuff 'n things, and use the "internet" connection from the phone to grab the GPS info.
Click to expand...
Click to collapse
Question: will 'Wireless Tethering' work in place of 'tether-wifi'? Or does it -have- to be 'tether-wifi'? Thanks!
any software will work that tethers.:-D
ace7196 said:
Never had an issue with the IMEI number, but here's how I got it setup.
Start with the TetherGPS app running server on the phone and client on the NC, as well as tether-wifi from google running on the phone, then connect to the AP on the NC
Next, open/install the app. It should read the GPS data from the phone
Now, switch back to a wireless connection with internet access, download the voice, then enter the serial/etc...
Finally, load the app back up after all the registration stuff 'n things, and use the "internet" connection from the phone to grab the GPS info.
Click to expand...
Click to collapse
Apparently the latest version of Copilot has introduced this error. I have spoken with tech support regarding the issue and they told me that they are aware of the problem and will release an update early next week that will fix the problem. Apparently if you have version 8.2.504 it works, but the new version breaks it. The dev won't send me a copy of the old version, so I guess I'll just have to wait and hope.
lschroeder said:
Copied and edited from cm7 user thread.
I have xoom bluetooth keyboard with disconnect issues. Would the special kernel help with this?
From the accessories thread. "I found a work-around. Download the app Bluetooth Keyboard JP, change the settings in settings > Language and Keyboard to that app, then connect the keyboard." Anybody else try this or others? Blue Input is another one. I know of one more but can remember its name.
Another issue: When I have the keyboard active and playing flash files from the internet, it seems to buffer more. If I move the keyboard out of range or use settings to disconnect the keyboard, the buffering is less and the flash files play better. I have cyfi bluetooth external speakers. When I use them I get the same buffering issue, so I just use an external player through the headphone jack instead.
Click to expand...
Click to collapse
I don't know if that is a solution, but the problem appears to be a conflict between wifi and bluetooth. Turn off wifi and most of your keyboard problems will go away.
Also there is an app on the market called "Null Keyboard" Which simply turns on a keyboard device that disables everything keyboard related. It doesn't disable bluetooth input, but it gets rid of the long-press pop ups and is suppose to solve other issues as well (including the software keyboard popping up every time you want to type.)
I haven't had time to install it, but it's purchased.
Does anyone know where (on the Nook) the BT chip/antenna is located?
It might help to know, since the range is so limited...
breebauer said:
Does anyone know where (on the Nook) the BT chip/antenna is located?
It might help to know, since the range is so limited...
Click to expand...
Click to collapse
http://www.zdnet.com/photos/nookcolor-teardown/487636?seq=62&tag=content;photo-frame#photo-frame
So across the bottom and up the right side as you hold it portrait.
khaytsus said:
http://www.zdnet.com/photos/nookcolor-teardown/487636?seq=62&tag=content;photo-frame#photo-frame
So across the bottom and up the right side as you hold it portrait.
Click to expand...
Click to collapse
Thanks! That makes a big difference...
(For some reason, I was thinking it was on the upper left corner- not sure why)
chisleu said:
I don't know if that is a solution, but the problem appears to be a conflict between wifi and bluetooth. Turn off wifi and most of your keyboard problems will go away.
Also there is an app on the market called "Null Keyboard" Which simply turns on a keyboard device that disables everything keyboard related. It doesn't disable bluetooth input, but it gets rid of the long-press pop ups and is suppose to solve other issues as well (including the software keyboard popping up every time you want to type.)
I haven't had time to install it, but it's purchased.
Click to expand...
Click to collapse
I was just using google voice to text from several feet back. In fact it was hard to read the small print from that distance. I did not realized that keyboards have a larger range then headsets.
Testing Bluetooth Keyboard JP now. Force closes, so just switched to swift keyboard I downloaded from amazon app store for free. To get out swift keyboard and get a null keyboard, I hit the back key on the xoom keyboard, then the virtual swift keyboard no longer shows up.
@chisleu do you have a link or instruction to modify bluetooth keyboards so that keys can have their mappings corrected. Xoom has some correct and some wrong or disabled under CM7.
Couldn't get BT to work at all however powering down while the wifi is off, and turning the bluetooth on before the wifi made it works on the first try. Was streaming Slacker to my stereo in a matter of minutes. Wifi doesn't seem to interfere with the BT audio stream at all, audio sounded crisp and perfect. Range however was still limited to a foot or so.
Hoping there is a possible hardware mod that can hook up an antenna to the BT chip. I'd be in heaven if I had full BT functionality on this beast.
FYI, Although I don't have any RF experience I'm still an electrical engineer so if anyone can toss me a bone on the PCB layout or pinouts of the nook I might be able to try stuff to boost the range.
What is the feasibility of adding dial-up networking client support to CM7? Some folks are able to tether their NC to their phone using an ad hoc wifi network, and others have had success via a Bluetooth personal area network (PAN) using the "pand" utility. Unfortunately, I have a Blackberry phone, and it does not support the PAN profile. It does, however, support dial-up networking (DUN) over Bluetooth (confirmed with a Windows laptop).
According to https://sites.google.com/a/android.com/opensource/projects/bluetooth-faq, "dund" is the client utility that is needed to establish a dial-up connection from Android to another device. When I run this command on the NC, it says "dund: not found". I'm not a developer and don't know how much effort would be involved in adding this functionality to the build. Is it just a matter of including the binaries, or is there additional development work involved?
Thanks in advance..
I have a G Tablet that I've been messing around with for the last 3 months or so. It had been fairly solid and reliable with Calkulin's ROM installed on it for awhile. Then the wifi started becoming unreliable when connecting to the ad-hoc wifi generated by my droid. This was aggravating, but the infrastructure wifi was still fine. Then that changed for me too. I get these periods where is just says error for he wifi status. I find that rebooting solves the problem for a while, but only for 10 minutes, if I'm lucky. I tried using different ROMs and finally settled on GTabComb BETA 2.0. I like this, but I still have the same wifi issues. To try to fix it, I used NVFlash to go back to the stock rom, still had the problem. Used the format utility, that scared the crap out of me, then NVFlash to go to Stock ROM. Then reinstall GTabComb, still with the flaky wifi. Has anyone else encountered this issue or have any idea how to fix it? I can't say I find my tablet terribly useful with no wifi.
are you sure it's an issue with the tab and not the Droid? has either device had an update to their tethering software?
Currently only using home wifi from my FIOS router. I was just poking around in there and noticed the Xbox stuff is being forwarded to the same IP as the Tablet. To avoid an IP Address conflict, I've given it a static IP in the DHCP settings that's well away from where the other IPs are being assigned out of. Hopefully I'll see some improvement.
Edit: Well, so much for it being an IP address conflict, it's out again with error.
Edit2: I've run the Fix Permissions from ROM Manager, that didn't help either. I can not figure this one out. Under the About Tablet, it says the wifi is an unknown version, is there a way to update the wifi itself?
Ya i have only had mine a few days and the wifi seems to drop in and out. If i disconnect and then reconnect it seems to help but i worry it will end up like yours eventually
Can you guys tell us what roms youre using when this happen? I'm trying to figure out if this is a software or hardware issue.
Between myself and family, we have 3 gtabs. And none have the problems that you guys describe.
I'm currently using GTabComb, but it started happening while I was running Calkulin. I didn't stay on stock long enough in between the two to really ascertain if that was a problem there as well.
In another post I mentioned having the same exact issue. My wifi out of the blue just became unreliable while tethered. Going on a week & a half now. I've been on the same rom on my phone for months, so I know it's not my phone. On my tab I've been using CM7 for months as well.
If I'm connected to my wifi router at home I have no problems. I have no idea what gives. I've tried just about everything I could (different roms, fix permissions, wiped all data, nvflash). The only thing I have not done is a complete G-Tab format utilizing the G-Tab format utility tool.
goodintentions said:
Can you guys tell us what roms youre using when this happen? I'm trying to figure out if this is a software or hardware issue.
Between myself and family, we have 3 gtabs. And none have the problems that you guys describe.
Click to expand...
Click to collapse
using VeganTab gingeredition
Are you using Barnacle, Wireless Tether for Root Users, or some other adhoc wifi app?
Sent from my Droid using XDA App
EL TEJANO said:
In another post I mentioned having the same exact issue. My wifi out of the blue just became unreliable while tethered. Going on a week & a half now. I've been on the same rom on my phone for months, so I know it's not my phone. On my tab I've been using CM7 for months as well.
If I'm connected to my wifi router at home I have no problems. I have no idea what gives. I've tried just about everything I could (different roms, fix permissions, wiped all data, nvflash). The only thing I have not done is a complete G-Tab format utilizing the G-Tab format utility tool.
Click to expand...
Click to collapse
Don't bother with the G-Tab format utility, it doesn't help this issue. And besides, it has to be the scariest thing i've done to my tablet, I thought I was going to have to crack it open to make it work again after I did that.
I was using Wireless Tether for Root Users on my original Droid. Haven't tried it lately since the infrastructure issue popped up as well.
Fox_spy: If you gTab keeps dropping connections like clockwork, try flashing the zip file posted in this thread.
The wlan binary blobs in that zip file should work with all kernels, but, if you still have problems, the script saves your original wlan binary blobs as filename.bin.orig in /system/lib/hw/wlan, so you can easily restore them.
I'd like to know if downgrading-the-firmware-blobs solution works for you.
Just thought I'd post my experiences...
I've been using CM7 versions on mine, recently upgraded to 7.0.3 and my wifi connection now frequently drops. Haven't done much troubleshooting. I just disable and re-enable it to get the connection back.
rajeevvp said:
Fox_spy: If you gTab keeps dropping connections like clockwork, try flashing the zip file posted in this thread.
The wlan binary blobs in that zip file should work with all kernels, but, if you still have problems, the script saves your original wlan binary blobs as filename.bin.orig in /system/lib/hw/wlan, so you can easily restore them.
I'd like to know if downgrading-the-firmware-blobs solution works for you.
Click to expand...
Click to collapse
This didn't work for me. It definitely changed the version though since I could see a difference in file size between the 2 files. I couldn't figure out how to change it back either since I kept getting permission denied. I've found that visiting the Android Market is a guaranteed drop and error for my wifi.
Have gone back to totally stock 3588 and that's working fine right now. Wifi is staying online and working as far as I can tell. I wish stock had the google Market so I could test that. I may have to go to another mod, but I don't want to have my wifi go flaky.
I believe I've fixed the wifi issue. As a crap shoot I typed the word "repair" into the Android Market & saw several apps for wifi repair. Though the apk description read that the fix was for other specific models I decided to give it a go. I figured well if it borks my rom I'll just restore my current backup.
I came across an app called "FXR WiFi fix and rescue". So far I've been using it for the past 2 hours via Wireless Tether & it hasn't dropped once. Previously before the fix, I was lucky if I got 5-10 min. before it dropped connection.
Just to make sure it wasn't a fluke I left my phone & tab untouched & connected for 30 min with an open web-page. When I came back to test it out, it was still connected.
If you want to try it then I suggest you back up your rom first. Let us know how it goes.
I'm running the latest CM7 nightly build btw.
Fox_Spy said:
Have gone back to totally stock 3588 and that's working fine right now. Wifi is staying online and working as far as I can tell. I wish stock had the google Market so I could test that. I may have to go to another mod, but I don't want to have my wifi go flaky.
Click to expand...
Click to collapse
You can put market on stock, I ran that way until recently.
EL TEJANO said:
I believe I've fixed the wifi issue. As a crap shoot I typed the word "repair" into the Android Market & saw several apps for wifi repair. Though the apk description read that the fix was for other specific models I decided to give it a go. I figured well if it borks my rom I'll just restore my current backup.
I came across an app called "FXR WiFi fix and rescue". So far I've been using it for the past 2 hours via Wireless Tether & it hasn't dropped once. Previously before the fix, I was lucky if I got 5-10 min. before it dropped connection.
Just to make sure it wasn't a fluke I left my phone & tab untouched & connected for 30 min with an open web-page. When I came back to test it out, it was still connected.
If you want to try it then I suggest you back up your rom first. Let us know how it goes.
I'm running the latest CM7 nightly build btw.
Click to expand...
Click to collapse
Unfortunately this didn't fix my problem in GTabComb, but you mentioned CM7 which I actually don't seem to have any problems with from a wifi perspective. I put CM 7.1 RC 1 BL1.1 onto my tablet and the wifi is great, but I can't use it long term because it doesn't see the internal SDCard, which is annoying to say the least. No idea what's up on that one. Trying to find the mod I originally had on here for long term use to try that for a fresh install again, if only I could remember what it was.
Edit: Random question for those with wireless problems. Do you have a case on your tablet? I've got one of those full body skins. I really hope that's not the cause.
I put GtabComb Alpha 1.6.2 onto my tablet and it can scan networks and isn't immediately erroring out, which puts it ahead of some other ROMs I've tried. But it doesn't see ad-hoc networks so I won't know if it's stable until later when I get home.
Edit: $*^%, wifi fail at home using my FIOS router. However it occurs to me that I've got a repeating wireless bridge in my house, so I'm unplugging that and trying this again. I did manage to do more this time around before it dropped. So, I'm sort of making progress.
Edit2: I can't decide if I'm pissed or not that turning off the bridge seems to have fixed it. I may have to experiment more before I'm satisfied though.
Edit3: It's still going in and out. Damn.
Fox_Spy said:
This didn't work for me.
Click to expand...
Click to collapse
That's a pity. My Wi-Fi drops were fixed after the firmware blob downgrade.
Send me the dmesg.txt that results from this command, after you've got a few Wi-Fi drops. Inside a Terminal program, type:
Code:
$ dmesg > /mnt/sdcard/dmesg.txt
I couldn't figure out how to change it back either since I kept getting permission denied.
Click to expand...
Click to collapse
The files are inside the /system partition which is normally read-only. You also need superuser privileges to make changes to that partition. Next time, use Root Explorer.
Fox_Spy said:
Here is the result of the dmesg command.
Click to expand...
Click to collapse
There definitely are errors in there:
Code:
<3>[ 9.178150] init: Cannot mount the device /dev/block/mmcblk3p2 at /data as ext3 file system...retrying
<6>[ 9.208172] mmc2: new high speed MMC card at address 0001
<6>[ 9.213853] mmcblk3: mmc2:0001 MAG4EM 14.9 GiB
<6>[ 9.218526] mmcblk3: p1 p2
<3>[ 10.187720] init: Cannot mount the device /dev/block/mmcblk3p2 at /data as ext3 file system...retrying
and
Code:
<4>[ 38.377123] wlan0: set mcast_list failed, cnt 1
<4>[ 38.382574] wlan0: set allmulti 1 failed
<4>[ 38.387120] wlan0: set promisc 0 failed
<4>[ 38.777511] dhdcdc_query_ioctl: dhdcdc_msg failed w/status -5
<4>[ 38.783858] dhdcdc_query_ioctl: dhdcdc_msg failed w/status -5
<4>[ 38.819789] dhdcdc_query_ioctl: dhdcdc_msg failed w/status -5
<4>[ 38.827627] dhdsdio_htclk: Failed access turning clock off: -35
<4>[ 38.874905] dhdsdio_htclk: HT Avail request error: -35
<4>[ 40.883829] Return_dpc value is : 0
Plenty more errors towards the end of the file, and all of them are SDIO-related errors.
On the gTablet, both the wlan hardware and the SD card use the SDIO interface, which accounts for your SD card and wlan problems.
I see that you're running a custom Clemsyn kernel, so, I can't decide if this is a kernel problem or a hardware malfunction. Here's what I suggest you do.
1. Install ClockworkMod v0.8--the safe and stable version for gTablets.
2. Shut down the gTablet for ~5 mins.
3. Boot into clockworkmod and run that dmesg command again. I want to see the messages from a safe, standard kernel.
There doesn't seem to be an attach file option, or I'm missing it
Click to expand...
Click to collapse
After you press either "Post reply" or "Quote" scroll down. There is an "Additional Options" section where you can "Manage Attachments".
Hello everyone
I have Cyanogenmod 7.0.3 running on my HTC Legend but am having trouble with the GPS.
I have used GPS test on both radio firmware 7.13.35.05 and 7.08.35.21 and get 6-10 satellites on both and about 5-8 in use. However I never get a position or accuracy reading and in apps such as Google Maps it just says "waiting for location".
What can be the problem ?
I actually have the same problem, but the only time it locks (RARELY) when I use Maps. RARELY!
I flashed to CM 7.1 RC and don't think I experienced this problem in 7.0.3. I'm also curious as to what the problem is, I've updated the radio to 7.13.35.13 long ago and recently I've applied the GPS "Faster Fix" Mod buried somewhere in the Dev forum.
I have tried the faster fix without luck.
When the gps eventually gets a fix (after 10-20 minutes sometimes never) it works flawlessly.. . But then when i turn it of and on - the same story.. waiting for ages
Is this a rom problem or a general Legend issue ?
My 5 year old Garmin Nuvi gps for the car gets a lock within 8 seconds... So er new smartphone should be able to do this also.
I thought I share my GPS experience.
Ever since I updated gps.conf to point to a local ntp server,
I now always get a GPS fix in seconds.
I'm currently loving CM71 RC1 but have also had GPS success with B 0.84.
I hope this helps.
Ithought that was what fasterfix was supposed to to ? To modify the gps config file..
How do you do it manually ?
Use Root Explorer.
Take a gander through here:
http://forum.xda-developers.com/showthread.php?t=1066284
CM7 defaults to NTP_SERVER=europe.pool.ntp.org
HTC defaults to NTP_SERVER=north-america.pool.ntp.org
So replace that line with a server closer to your part of the world from pool.ntp.org.
The safest way to replace gps.conf is via recovery, for example:
adb reboot recovery
+/+/ then +/+/
adb shell mount /system
adb push gps.conf /system/etc/gps.conf
adb shell chmod 644 /system/etc/gps.conf
adb reboot
Do you see the GPS icon blinking? If so then you can try flashing the various GPS fix files, modifying configurations, or waving your phone in the air to recalibrate the sensors. However, after none of those solutions worked for me, I realized the issue was hardware related. The GPS sensor is directly underneath the loudspeaker on the back, behind the plastic cover. Similar to the way the battery cover is the antenna for WiFi/mobile network etc, the upper cover is the antenna for GPS. I found that fiddling around with it, or applying pressure where the speaker is can help achieve a better GPS signal, but if you stop applying pressure, it tends to stop working again.
Download the "GPS Test" app from the market, run it, look at the strength of the GPS and then check again after applying pressure. If you notice the bars go up, then you've found your issue. If you are adventurous enough, you can use a pin to pry open the cover (be careful not to scratch) and you'll see two small metallic connectors below the speaker. You could try to adjust them to provide better contact with the antenna in the plastic cover. That's how I fixed my GPS issues.
My config is now set to europe (where i live) and i get 9-11 satellites with 20-45 in signal strengthwith "gps test" but it still takes up to 20 minutes sometimes to get a fix. The icon is blinking but it still takes far more time than suppose to.
My garmin gps running watch lock on to a satellite in under 10 second..
This is crazy..
I have now tried to set to denmark (my home country) at that seems to do the trick.. But come on.. everytime i travle to germany and france i have to reset the servers ?
Can it really be true that gps in smartphones are so bad when older gps devices for cars and waches are better ?
You may also set up to 4 servers and they dont need to be from the same pool.
0.europe.pool.ntp.org 1.europe.pool.ntp.org 2.europe.pool.ntp.org 3.europe.pool.ntp.org
Yeah, I would expect the europe pool should be enough but see how you go.
i have cm7.1 rc1. i'm trying to change gps.conf with the one i made, but i can't:
if i paste it with root explorer (r/w) it tells me that it's been pasted, but after reboot there is always the same old file
with adb shell i have this error
Code:
- exec '/system/bin/sh' failed: No such file or directory (2) -
someone can help me?
use the recovery procedure listed before
doubleup said:
use the recovery procedure listed before
Click to expand...
Click to collapse
i did, but when i type adb shell mount /system it gives me the error i wrote in the previous post
loscassapalle said:
i did, but when i type adb shell mount /system it gives me the error i wrote in the previous post
Click to expand...
Click to collapse
You need to start clockworkmod via update.zip
follow the launching recovery steps shown here
http://forum.xda-developers.com/showthread.php?t=698404
thanks, you were right. i've updated it, but still not work:
with gps status i cleared previous data and download new ones, but after 10 min nothing happened.
i've radio 7.05.35.26, should i try to update?
loscassapalle said:
thanks, you were right. i've updated it, but still not work:
with gps status i cleared previous data and download new ones, but after 10 min nothing happened.
i've radio 7.05.35.26, should i try to update?
Click to expand...
Click to collapse
I assume you have data turned on? Also what does your conf file look like?
dancemonkey said:
I assume you have data turned on? Also what does your conf file look like?
Click to expand...
Click to collapse
yes, data on.
i copied it from that post , only changing the ntp server
interesting to know what happens after you update your radio
the post you got gps.conf from says is all good with radio 7.13.35.05
i went from b084 to cm71 so everything was wiped out and got that radio
keep us posted