Wifi Channel 13 @ GB Roms (DSC especially) - Streak 5 Q&A, Help & Troubleshooting

Hi there,
i'm really enjoying the DSC rom v0.7 i'm using and also all the other communitybased GB roms i've tryed so far. Really damn good work the devs are doing! But there is one problem i'm running into with all of them. I cannot use the wifi channels 12 and 13. Even having changed the regulatory domain in the build.prob (de, eu) did not help this. Is there a thing i can do to make this work?
TIA
Gostl

We could start with determining on which level this channels are blocked.
via adb shell or terminal emulator do:
wpa_cli
scan_results
Do you see
12 2467 Europe/France
13 2472 Europe/France
frequencies in results?

Thx for quick reply. Hmm what am I supposed to see? When I run wpa_cli it says it's unable to connect to wpa supplicant... I then get a prompt (not terminal, inside the application) that does not respond to anything.
I don't know if I'm doing this right.
Sent from my Dell Streak using XDA App

I forgot to mention, you need to issue su command in terminal first.

Hmm, i only see the networks available. I think i can only see whether or not i will see channel 12 and 13 when there is an AP using them. Currently i don't have one available so i will wait untill i come across the problem again.
Thanks so far!
Gostl

Related

[FIX] AdHoc Wifi support on the NC!

Great news everyone! </farnsworth>
ADHOC Wifi Support for Nook Color (stock)!
[EDIT] There appears to be an issue reconnecting when wifi sleeps and comes back on. Researching a permanent fix, in the meantime go to settings -> Wireless and toggle wifi off/on to correct it
This fix will allow you to connect to ADHOC wireless networks ( such as to a laptop or with wifi-tether on an android phone )
Like most other fixes, this requires your nook to be rooted and usb adb working, please follow the guides here and/or at the nook dev wiki first!:
Rooting: http://nookdevs.com/NookColor_Rooting
USB-ADB: http://nookdevs.com/NookColor_USB_ADB
HOWTO enable ADHOC tethering:
1. Download and unzip the attached zip file below, this should give you a wpa_supplicant-adhocfix file
2. *DISABLE WIFI ON YOUR NC*
3. Make a backup of your current wpa_supplicant:
Code:
adb pull /system/bin/wpa_supplicant wpa_supplicant.backup
4. Remount the /system partition RW:
Code:
adb shell mount -o remount,rw /dev/block/mmcblk0p5 /system
5. Push the new wpa_supplicant:
Code:
adb push wpa_supplicant.adhocfix /system/bin/wpa_supplicant
6. Fix permissions:
Code:
adb shell chmod 755 /system/bin/wpa_supplicant
7. Remount the /system partition RO:
Code:
adb shell mount -o remount,ro /dev/block/mmcblk0p5 /system
8. Enable WIFI on your NC, you should now be able to see ADHOC networks in the list! ( they'll be displayed with a (*) prefix )
[edit] Credit where credit's due, this was taken from a wpa_supplicant IBSS patch I found via a Google search, if anyone knows the party responsible, let me know so I can credit them properly!
http://szym.net/android/
This is compiled against TI's Omapedia Eclair sources ( http://omappedia.org ) - since this is a different framework than the B&N stock build, I can't guarantee this will work, won't brick your device, etc. Use at your own risk!
If you encounter any problems, please use this thread to let us all know.
That's all there is to it, enjoy!
I can confirm that this will allow you to connect you Nook Color to an adhoc network created by a Jailbroken iPhone 4 and MyWi.
Works great! Thanks!
WHOEVER made this fix....THANK YOU! This was the biggest thing I was missing on my NC! Works great!
Cool you figured this out! For some reason, I've been able to use the adhoc network on my Androidized HTC Leo (HD2) since the first time I tried, even before rooting.
Sent from my Rooted Nook Color using XDA App and iPhone MyWi adhoc connection.
You guys ROCK!!!!!!!!!!
Works great with my Droid now. Thanks!
Confirmed working with Mobile Wi-Fi Router on my VZW Touch Pro2.
Many thanks! Another big step!
Work perfectly on my motorola droid 1 using Wireless tether or Barnacle. Thanks for sharing this with us
Works great with AT&T Samsung Captivate and android-wifi-tether ver. 2.0.5-pre15.
Thank you very much!
My NC is stuck at trying to obtain an IP address from my Droid 1. I'm using Barnacle.
Any ideas?
*edit*
It took several attempts but it finally connected. Being able to get connected anywhere is awesome. Thanks for posting this!
Working great from my epic 4g.
Pro Tip: If you want a quick way to toggle wifi (and a few other settings) tap the clock in the nook's notification bar for a quick settings dialog.
Thanks for this. I can now use my nook at work tethered to my phone. You may want to edit the typo in step 7 as we all caught it but someone may not.
Philosophy757 said:
Thanks for this. I can now use my nook at work tethered to my phone. You may want to edit the typo in step 7 as we all caught it but someone may not.
Click to expand...
Click to collapse
Thanks for noticing, corrected the extra 'o'
As noted in the OP, this is based on TI's omap eclair reference sources, and there *is* a pretty glaring bug.
Basically, if your screen goes to sleep, waking it back up triggers a wifi-reconnect which fails to reinitialize the network properly. Your wifi settings will show 'Connected, no internet' when this happens.
Toggle Wifi off/on to fix this, I'm working on a permanent fix right now and will update when it's working.
Thanks everyone for testing and boosting the ol' ego a little
Some random tips so folks don't repeat the same mistakes I made while doing installing the ad hoc feature.
Don't choose to "forget" a wireless access point because then it doesn't appear again even if the device sees it. You'll have to manually enter the SSID, encryption type, and password to get it to work properly.
While mounting and remounting using adb, if you get a device busy error, disconnect the nook from the computer and come back to it later. Then reconnect and try again. For good measure I also powered down the nook. Not sure what happens if you leave the system folder mounted as RW, but I suspect bad things could happen.
Oh and the fix works like a charm. This is one really nice device.
Works perfect on my NC tethered to my MyTouch 3G ( rooted with CyanogenMod-6.1 )
Many many thanks to the dev. !!
Nice work, and thank you. Working fine with another rooted droid (running CM6.1).
I had the "device busy" error and went ahead and unplugged, then reset to ro with Root Explorer- no problems.
This reminds me of when the Droid first got rooted- took a little while to make progress but every few days that would be another BIG, popular advance.
Thanks so much!!!! Droid1 still has life! Yeah.
Thanks. This works great. One question. Does anyone know where I can get the original wpa_supplicant file? I misspelled it so I don't have a good backup. Thanks.
Original nook wpa_supplicant
Here ya go...
OK. Maybe I can't upload files.

[HOW-TO] Wifi Fix for CM6 [1/2/2011]

DISCLAIMER: Nobody -- and I do mean nobody -- is responsible for a bricked device except for the person attempting this modification. Do not contact me to complain that you borked your Slide by not following instructions.​
All credit for this discovery goes to knowmercymod​
Certain Espresso owners running CM6 (or CM6 derivatives) may have discovered that their wifi functionality doesn't work as expected. The issue is well-documented on the CM6 issue tracker [issue 2153] and the cause of the problem is known, but there is no source-based solution at the moment. As such, there's no easy way to distribute a fix for working wifi within a packaged CM6 zip.
The issue relates to missing GPL'd drivers for the MSM7227 chipset from Qualcomm that is used in several devices, most notably the HTC Espresso, Legend and Aria. But due to small versioning differences in certain aspects of this chipset, some devices have functioning wifi using the generic open-source SDIO modules and others do not. The permanent solution for this issue is cajoling HTC into releasing this code -- this process is already underway -- but, in the meantime, this thread will serve to provide a temporary solution that is 100% effective.
So let's get started...
Step 1: Downloading the necessary files​
Attached to this post are the two files necessary to fix this issue:
sdio.ko
tiwlan_drv.ko
They both come from *stock* Espresso -- the code currently in use in the CM6 repository does not generate fully-functional versions of these modules.
Download the "modules.zip" file to your PC and extract the two files to an easily accessible location.
Step 2: Backing up the corresponding files on your device [optional]​
This optional step will walk you through backing up the existing files on your device. This is completely unnecessary as those files can simply be restored by re-flashing a CM6 zip, but I figured that people should get in the habit of backing up stock files before modifying their device.
To do so, execute the following two commands -- both can be done while the phone is booted up or in recovery (if you're in ClockworkMod recovery, just make sure your system partition is mounted -- partitions->mount /system):
Code:
ADB PULL /system/lib/modules/tiwlan_drv.ko [DESTINATION]
ADB PULL /system/lib/modules/sdio.ko [DESTINATION]
To use my PC as an example, I would connect my Slide via USB and enter the following commands on the command line:
Code:
ADB PULL /system/lib/modules/tiwlan_drv.ko ~/Documents/Android/Backup
ADB PULL /system/lib/modules/sdio.ko ~/Documents/Android/Backup
Step 3: Replacing the files on your device​
So now we're ready to make the actual modification. First step: boot into recovery. My preferred method is to use the ADB REBOOT RECOVERY command.
Once you're in ClockworkMod Recovery, please make sure system is mounted -- partitions->mount /system
Then you would simply execute these two commands:
Code:
ADB PUSH [SOURCE]/tiwlan_drv.ko /system/lib/modules/tiwlan_drv.ko
ADB PUSH [SOURCE]/sdio.ko /system/lib/modules/sdio.ko
To use my PC as an example, I would enter the following commands on the command line:
Code:
ADB PUSH ~/Downloads/modules/tiwlan_drv.ko /system/lib/modules/tiwlan_drv.ko
ADB PUSH ~/Downloads/modules/sdio.ko /system/lib/modules/sdio.ko
Once you've pushed these files, simply reboot your device and you're done! You should no longer have any issues with your wifi connectivity, including (but not limited to) full wifi tether functionality when using the Wireless Tether 2.0.5 application.
And, again, all credit for this temporary fix goes to knowmercymod (who is far too humble to post this himself).
Saving this space for future updates...
I hope this fixes my frequent disconnects, but on the legend section they fixed the problem by changing the channels to 14 instead of 11, not sure if that will work for espresso.
UPDATE: Works great! Thanks for posting this.
Very exciting news! I'll fully charge and try this fix. Looking forward to using CM instead of stock.
Just pushed the files to cyanoginger 1.1.. wifi and wifi tether both appear to work perfectly now
Cool, thanks for posting!
I did it, not sure if it did anything. Weird thing is, after pushing the 2 files I noticed I forgot to mount the system folder but it said it transfered successfully.. *shrugs*
I think tethering was working before, either way though, it works now
Awesome! Thanks so much for the hard work. I know you guys will manage a perm fix via a regular rom soon. HTC will cough up that source code for ya
Just chiming in to say this works for me. Takes a little longer now to connect to an access point than it used to, but rock solid after that. With s-off, didn't even have to be in recovery, just mounted system rw, pushed files, and rebooted.
Sent from my MyTouch 3G Slide running CM6.1.1
Did it right off my phone with sufbs file manager. Great job hopefully its integrated in next cm build.
I keep getting a "out of space" error when I go to copy the files.
Please help.
poormanq45 said:
I keep getting a "out of space" error when I go to copy the files.
Please help.
Click to expand...
Click to collapse
If you have not applied s-off patch by alpharev, then you have to push the files while in clockwork recovery, after going to the partitions menu and selecting mount /system. If you are in fact s-off, you have to use a terminal emulator and type [code}mount -o rw,remount /system[/code] and then push the files
Sent from my T-Mobile myTouch 3G Slide
CM6 wifi works fine for me, but would these drivers work better with my phone anyways since they're specifically made for this phone?
Applied this on Arayaray revamped which seemed to have spotty wifi for me especially when accessing the market. After applying this the wifi is perfect not a single problem at all now, thanks so much!!
I refuse to connect my phone to my pc. Is there any way to get these files pushed onto my phone? Terminal Emulator work? If not, it's cool. Wifi seems to be working for the most part under CM6.
xaodxkevin said:
CM6 wifi works fine for me, but would these drivers work better with my phone anyways since they're specifically made for this phone?
Click to expand...
Click to collapse
It depends. These files are taken *directly* from the stock espresso rom and are known-good. If you're not having any issues with wifi running CM6 I don't feel comfortable telling you this will "improve" anything -- but I don't think it would hurt. In any case, if you follow my instructions you will have backed up the original files and can restore them at any time.
Hayzie said:
I refuse to connect my phone to my pc. Is there any way to get these files pushed onto my phone? Terminal Emulator work? If not, it's cool. Wifi seems to be working for the most part under CM6.
Click to expand...
Click to collapse
Uhhhh -- why? That seems incredibly myopic and weird. You know what -- never mind -- I don't want to know. You can use a terminal emulator on the device to move the two files from your sdcard to their rightful place on /system. I'll leave it as an exercise to the user to figure out the correct commands to do so.
Well I'll tell you anyways... MyTouch Slide always acts funny when plugged via USB to my pc, more-or-less so Windows 7. I could say this is an uncommon issue, but it's not. So it's not weird.
Mine works just fine, whats funny about it when u plug it in? Sorry to bring this up here herbrewtoyou but im curious lol
Sent from my T-Mobile myTouch 3G Slide using XDA App
Hey guys I just pushed the 2 files to my phone, I'm running CM 6.1.1-Slide - since I flashed to 6.1 and then reflashed to 6.1.1 I have had 0 Wifi capability. So I push these files and followed the instructions, and well I still have no wifi. I will enable it and it will scan, try to authenticate and then disconnect and repeat.......any ideas???
ApeMan911 said:
Hey guys I just pushed the 2 files to my phone, I'm running CM 6.1.1-Slide - since I flashed to 6.1 and then reflashed to 6.1.1 I have had 0 Wifi capability. So I push these files and followed the instructions, and well I still have no wifi. I will enable it and it will scan, try to authenticate and then disconnect and repeat.......any ideas???
Click to expand...
Click to collapse
Sounds like an issue with your router...
No its def not the router, phone would connect all day long before switching to CM.

[Q] VPN on G-tablet

I have been having trouble connecting to my work VPN with the G-Tablet. I have since tried going to ZPad 3.0 in hopes this would fix the issue. However, no luck. The VPN server is reporting an event error of 20209.
After a few hours of looking on other forums it turns out this have been an issue since Android 2.1. They have either intentionally left out the encryption module from PPPD or it was forgotten in the build. The 'fix' is to copy the PPPD file from a version prior to 2.1 (Android 1.5?) and save it to the System/xbin directory. However there is an argument over if should go into system/bin for 2.2.
Does anyone have more information on this - or better yet a fix/update? Any help on this would be appreciated.
which ROm are you using
stock ROM doesn't have VPN at all.
justauser said:
stock ROM doesn't have VPN at all.
Click to expand...
Click to collapse
I'm using ZPAD 3.0 ROM at the moment.
I have narrowed it down to a problem with the MPPE 128 encryption. I have found a PPPD that is supposed to fix the problem (see link below), but I don't now how to get it to the system directory. How do you mount system as R/W?
Alternate PPPD:
H***://melko.hiljanen.com/~qvr/android/ppp/
Root explorer will allow you to mount it that way
Sent from my DROIDX using Tapatalk
Let me know how it goes... I have been trying to connect my gtab but I thought I was the only person interested!
Sent from my DROIDX using XDA App
vectorcharlie said:
Let me know how it goes... I have been trying to connect my gtab but I thought I was the only person interested!
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Ditto!!!!!!!!
Tried your link, getting the same error I've seen in the past:
Code:
pppd: This system lacks kernel support for PPP. This could be because
the PPP kernel module could not be loaded, or because PPP was not
included in the kernel configuration. If PPP was included as a
module, try `/sbin/modprobe -v ppp'. If that fails, check that
ppp.o exists in /lib/modules/`uname -r`/net.
See README.linux file in the ppp distribution for more details.
I think(?) we need a customized kernel with ppp. So far, we have NTFS and CIFS support that's been added by some of the devs, here.
vectorcharlie said:
Let me know how it goes... I have been trying to connect my gtab but I thought I was the only person interested!
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
No luck. The PPPD file didn't make a difference. I guess I should not have been surprised. The L2TP connections are supposed to work so I may try that tomorrow - if I can convince the network admin to make the changes on the vpn server.
The lastest info I have been able to collect on this issue is that it has been known at google since 2.0 was released. They were having a problem keeping a connection using MPPE 128 over PPTP so instead of releasing something that did not work right, they removed support for it until a later date. Said date has not been determined.
I will keep you posted as I find out more.
roebeet said:
Tried your link, getting the same error I've seen in the past:
Code:
pppd: This system lacks kernel support for PPP. This could be because
the PPP kernel module could not be loaded, or because PPP was not
included in the kernel configuration. If PPP was included as a
module, try `/sbin/modprobe -v ppp'. If that fails, check that
ppp.o exists in /lib/modules/`uname -r`/net.
See README.linux file in the ppp distribution for more details.
I think(?) we need a customized kernel with ppp. So far, we have NTFS and CIFS support that's been added by some of the devs, here.
Click to expand...
Click to collapse
I came across this too. Since the ppp directory exists under system/etc I have made the assumption that there is support for it (at least under ztab 3.0). In order to check using the method above we would need a terminal app or some other way to run the commands. If there is a way to do it natively I am too new to know.
Any devs willing to tackle this issue?
Newanzer said:
No luck. The PPPD file didn't make a difference. I guess I should not have been surprised. The L2TP connections are supposed to work so I may try that tomorrow - if I can convince the network admin to make the changes on the vpn server.
...
I will keep you posted as I find out more.
Click to expand...
Click to collapse
No luck. The Net Admin decided it would be too much work just for a tablet test (and his iPAD VPN work just fine thank you). Anyone willing to try a L2TP test?
I have tried L2TP in Vegan with no success. used my android phone to verify settings and it works fine from there.
nephelim said:
I have tried L2TP in Vegan with no success. used my android phone to verify settings and it works fine from there.
Click to expand...
Click to collapse
Ok so that is 2 ROMs down:
TNT Stock - No option
Vegan - Not functional
Just need TNT light and Zpad Clean v3.0 tested. I'm suspecting that it will be no for both. This is starting to creep higher on my list of needs. Does anyone know of a ROM VPN works in?
I confirm that the advent vega rom has the same problem.
Unable to use vpn.
Newanzer said:
Ok so that is 2 ROMs down:
TNT Stock - No option
Vegan - Not functional
Just need TNT light and Zpad Clean v3.0 tested. I'm suspecting that it will be no for both. This is starting to creep higher on my list of needs. Does anyone know of a ROM VPN works in?
Click to expand...
Click to collapse
Do you need tun.ko/kernel support for this stuff? Clemsyn compiled that into one of his kernels - check his thread in the Development forum out, and give that kernel a try with the Vegan ROM, that might get you closer.
rcgabriel said:
Do you need tun.ko/kernel support for this stuff? Clemsyn compiled that into one of his kernels - check his thread in the Development forum out, and give that kernel a try with the Vegan ROM, that might get you closer.
Click to expand...
Click to collapse
That could be worth the check. I would like to see a list of exactly what his kernel supports before I try though.
[EDIT]: Checked change log. VPN module in kernel not mentioned.
Looking over the list of known issues at Google, this problem has been known for a while. The fact that Google hasn't addressed it worries me a bit. It is possible that since phones are the largest part of their OS client, VPN isn't a high priority. They may be waiting for the open source community to solve their problem for them.
Was able to get VPN working
YOU WILL NEED TO HAVE ROOT AND BUSYBOX INSTALLED. PLEASE MAKE A BACKUP IN CASE SOMETHING GOES WRONG.
1st you will need the new kernel found at the below address.
http://forum.xda-developers.com/showthread.php?t=903505
2nd you will need to insert the tun.ko included in with the kernel into /system/lib/modules/2.6.32.27-cyanogenmod folder on the tablet using root explorer.
3rd you will need to install the latest version of vpn from
http://code.google.com/p/get-a-robot-vpnc/downloads/list
4th install a terminal emulator and then you will need type the following commands
su (press enter)
cd /system/lib/modules/2.6.32.27-cyanogenmod (press enter)
insmod tun.ko (press enter)
You should now be able to connect on VPN.
there is very easy installation get and run vpn frome purevpn........
brainyjd said:
YOU WILL NEED TO HAVE ROOT AND BUSYBOX INSTALLED. PLEASE MAKE A BACKUP IN CASE SOMETHING GOES WRONG.
1st you will need the new kernel found at the below address.
http://forum.xda-developers.com/showthread.php?t=903505
2nd you will need to insert the tun.ko included in with the kernel into /system/lib/modules/2.6.32.27-cyanogenmod folder on the tablet using root explorer.
3rd you will need to install the latest version of vpn from
http://code.google.com/p/get-a-robot-vpnc/downloads/list
4th install a terminal emulator and then you will need type the following commands
su (press enter)
cd /system/lib/modules/2.6.32.27-cyanogenmod (press enter)
insmod tun.ko (press enter)
You should now be able to connect on VPN.
Click to expand...
Click to collapse
Sorry for asking this noob question, but is this VPN fix only for Cyanogenmod, or will work with others, such as TnT Lite?
I'm running TnT lite and there no's VPN setup option.
tnt is missing the vpn shortcut
use VPN Show
Kazuyuki Eguchi/Tools
found in android market to access the vpn menu
i have used with sucess on most roms open vpn and open vpn settings
with out problems just by install them and setting it to auto run at start
with install to xbin and create a folder on internal sd "openvpn"
then place a vpn.conf file there
then connect this cause an error but causes super user to give it root rights
after that all my vpn,s work with out going near openvpn
purevpn said:
there is very easy installation get and run vpn frome purevpn........
Click to expand...
Click to collapse
Please elaborate...
Thanks!

[Q][SGP311]GPS issues with CM10.1

I did install Cyanogen Mod 10.1 from the link in the "Free Xperia" thread (stable pollux_windy) today. It actually was an update from a nightly version from some days ago. It works pretty well except the gps, which doesn't work at all. I've done some googeling, but I didn't find anyone with similar problems. GPS worked fine for me with the stock rom, so i guess the chip is working. If i use a GPS tester, it shows that 0 satellites are available. I've not switched back to stock to try if it still works, because I had hoped that i could save all the time.
The positioning system works from time to time, but I guess it is only Wifi positioning. If i deactivate the Wifi positioning, it can't get any gps fix.
What i tried so far:
Stop/Reboot/Restart GPS
Wipe Cache and Dalvik Cache
Reboot again and again and again
Comparing the GPS.conf to the one from the stock rom (they are identical)
This is the first time I tried installing a custom rom, so there is a high chance, I did something wrong, but i would really appreciate if someone told me what it was. And please remember, that i'm quite new to the whole custom rom scene.
Not getting any answers at least tells me the problem is not that simple and I am not too stupid.
I thought till now at least anyone would have asked for details or anything.
Please anyone help! I desperately need the GPS!
Woozar said:
Not getting any answers at least tells me the problem is not that simple and I am not too stupid.
I thought till now at least anyone would have asked for details or anything.
Please anyone help! I desperately need the GPS!
Click to expand...
Click to collapse
Woozar,
working now to understand the problem. You know adb connection (debug mode)??. You know how to create logcat.txt??.
Asap I will tell you if I find the solution....
Regards
I just googled it. I need to use usb debug mode and then attach it to a pc with the android ask installed and run the command
Code:
adb logcat -d > logcat.txt
Do I need adb root access for this?
Shall I upload the file to the thread or send it to you personally?
Woozar said:
I just googled it. I need to use usb debug mode and then attach it to a pc with the android ask installed and run the command
Code:
adb logcat -d > logcat.txt
Do I need adb root access for this?
Shall I upload the file to the thread or send it to you personally?
Click to expand...
Click to collapse
make cold reset on GPS status app Pro
download AGPS
Swicth off the tablet
start adb logcat just after power on the tablet.
open GPS status again, download again AGPS.....
wait for searching in open sky area
only stop it after few min gps status is running...lets say 10 minutes.
press Ctrl+C on terminal mac to stop logcat.txt
send logcat.txt link download to me private.
I will use my and yours to search what is failing...
which CM10.1 running now...me experimental 25/06/13.
Sorry no time now...
I am not allowed to post links, so I need to post it like this.
https ://dl.dropboxusercontent.com/u/11941413/1
I hope I did everything as you wanted me to.
Please let me know if you need anything else.
Woozar said:
I am not allowed to post links, so I need to post it like this.
https ://dl.dropboxusercontent.com/u/11941413/1
I hope I did everything as you wanted me to.
Please let me know if you need anything else.
Click to expand...
Click to collapse
logcat.txt was good, but not usefull info errors.
I sent you private message here.
Regards.
Does this affect all sgp311 or does it work for anyone?
Is sgp 312 or 321 affected, too?
I'm in the same boat and after researching the XDA forums for a while it seems to me that GPS is not working in any of the current custom ROM's for our device. If GPS is important for you you would have to stick to the Stock ROM and wait a little bit more until the developers fix it.
For reference:
---------------------------------
SGP311 - Wifi-only Version (16GB) => CyanogenMod 10.1 (pollux_windy) = No GPS
SGP312 - Wifi-only Version (32GB) => CyanogenMod 10.1 (pollux_windy) = No GPS
SGP321 - LTE Version => CyanogenMod 10.1 (pollux) = GPS is working
---------------------------------
Tip: Some very resourceful user suggested a neat workaround where you could use the GPS from a mobile phone in the tablet. I didn't try it yet but it seems to be a good idea:
http://forum.xda-developers.com/showpost.php?p=43159748&postcount=10
I hope this helps!

Preview upgrading working?

I am considering flashing my main phone, and I cannot find an answer to this question:
Is the OS update functionality now working? i.e. if I install "current" now and run the updater next week, will I get the newer version? I don't want to switch until I no longer have to flash to get the newest version.
Thank you!
I installed Ubuntu touch on my nexus 4 last week , but I did the full install, not the way you flash a ROM normally , via Ubuntu on my computer.
If you ask me, is it functional, well yes you can make phone calls and send text message but it's very buggy, sometimes it freeze and you need to power off the phone manually and restart it.
It's totally better than the version I flashed 5 months ago but it's not something I would use as daily driver, except if your a die hard Ubuntu fan.
In back on android for your information.
My advice is wait for the 1.0 public version to become available.
Sent from my Nexus 7 using xda app-developers app
jonathan,
I think you misread the question...
I'm on an ubuntu-system build dated Sept. 20 2013 (near as I can determine).
I can see that there are OTA Updates available (the size of available update keeps increasing when checked), but have not yet had success getting the phone to update either via WiFi or 3G, automatically or manually, with the update manager app or via system settings (2 areas there purport to allow updating).
Soon (hopefully over the weekend) I will manually install a newer version of ubuntu-system via my Ubuntu Box.
I'll check back in and let you know...
For the record: I flashed the newest version. I quickly learned that you needed to do some cl work to get the clock set correctly. Unfortunately, given the recent switch to a read-only file system by default, I couldn't get the fixes to work. I reverted back to the legacy non-r/o version but found it way too buggy to use as a daily driver.
Some other things I noticed: gps doesn't really work (or I couldn't get it to) with google maps and you can't send multi-recipient sms. I could put up with living in UTC time for a few weeks, but those two things are deal breakers for me. Going to keep my eyes on the status of the project.
Thanks to a terminal command tip from eagleofdeath13 I found the workaround for correcting the timezone under the read only file system.
RumoredNow said:
That's the most helpful thing I've seen since ubuntu-system emerged... Thanks, I was ready to revert to cdimage-touch, but now I won't have to. :highfive:
So following the example, I opened terminal on my GNex (latest ubuntu-system --channel saucy --no-backup) and typed in
Code:
sudo mount /dev/loop0/ -o remount, rw
after entering the password for sudo, I next typed
Code:
sudo dpkg-reconfigure tzdata
and it brought up the timezone applet.
I was allowed to write my current time to the system!!!!!
Click to expand...
Click to collapse
The Read/Write command lasts only the one terminal session, but is very useful.
GPS and maps I have no cures for.

Categories

Resources