I'm having trouble finding consistent detailed information on GPS tethering with the Nook, and what I can find is pretty old. If I want to use my phone's GPS on my Nook, what apps are needed and what steps should I take? I've downloaded both GPS Tether and TetherGPS Lite, but I'm not sure I've figured out all the right setup on phone and Nook to get either one working.
Thanks in advance.
Related
So I was playing around with this GPS tether app. But I didn't manage to get it to work..
I was able to start the app and the GPS started working and got coordinates and everything seamd fine on the phone. I could not however not get access to it from my computer. I Guess GPS Tether is actually just an gpsd. so I used telnet to port 2947. I Got connected but I did not get any data, all i got was an "GPSD" showing now and then..
I'm running MCR r6.
Anyone got this working?
My reasons for wanting this is the ability to use any GPS app on my computer and the phone acting as an GPS device(using TCP-COM). and not having to buy an GPS device. And it would be very cool!
I have now managed to get data with telnet.. but when using an NMEA gps program, it doesnt seam to work, like GPSCommunicator :/ (using TCP-COM)
http://www.panazzolo.com/
Some time ago I rooted my Eris and flashed KaosFroyo v37. Very pleased with this rom and liked the ability of having root privileges. I naturally installed Wireless Tether for root users and was able to share my 3g with my laptop, although this does not help me with my desktop as I don't have wireless on my desktop. I do however have bluetooth on my desktop. I was pleased to see that I could also bluetooth tether to my desktop using the same program. I paired the two together and enable the bluetooth option of Wireless Tether, got my desktop to connect to it and was all set to go. Opened my web browser, tried to go to google, no luck. Checked the phone and it was rebooting. What??? So I tried it again, same result. Tried it a few more time and kept an eye on my phone to find out at what point it was rebooting. I could have my computer connected to it through the bluetooth tether until I tried to surf the web from my desktop.
At first I thought that maybe the wireless program was just not completely compatible with the Eris. I tried different roms (KaosFroye v38, v39, Tenzo 2.2.1, Nonsensikal v13.2, 15.2,16.1) all with the same results. Just yesterday I was messing around with this little problem again. Did some digging around the internet and found alot of information about bluetooth networking with android and Linux. Was able to run pand command from android shell and found that it has Bluetooth PAN daemon version 4.47. I believe that all the correct bleutooth tools are installed, so than I ran "pand -l -r NAP" and was able to get my phone to be a bluetooth network access point. Connected my computer to it, tried to access it throught the bluetooth network, and guess what, the phone rebooted. Now I do not think that it has anything to do with Wireless Tether for root.
I did some more digging on the internet and found that the bluetooth network interface is supposed to be bnep0. I can not find and interface on my phone for bnep0. Ok. More digging, bnep0 interface is part of the kernel built from the module bnep.ko. I can no find that module on my phone. Do I not need that module? Is that module not built at compile time of the rom? Does the Eris hardware not evan capable of Bluetooth PAN?
Could some one shed some light on this subject. Would really like to tether my desktop to me phone as that is the only way I can get internet at home. Thanks
P.S. My desktop and laptop are both dual boot into Windows Vista or Ubuntu 10.10 and they both use identical bluetooth usb cards.
I don't have an answer for you, but just wanted to add that I'm curious if anyone is knowlegeable about this, too.
You can use wired tethering. If you need help doing so, I've done it a lot as it's my and my girlfriend's only internet and has been for the past five months, too. I use wired because the wireless seems to use battery power faster than it can be charged on the phone, plus it gets even hotter for me. As it is, even with wired tethering, I take the back off and let it sit in front of a fan face-down to keep it cooler.
You're mileage may vary, of course. In my experience both wired and wireless is fairly unreliable and easy to overburden so much that the phone loses it's internet until I do an APN Restore and reboot the phone. Sometimes a reboot of my PC is necessary, too. I don't know if you've had this experience with the standard wireless tethering. I also download a LOT, so this could be a factor.
Thank you for the reply. Yes i can use wired tether to do internet as well, and yes the phone does heat up. It has never gotten so hot that I had to do a restore on it yet though. If that happens I think I would have a stroke and probably keep the phone in the freezer while tethering.
I have been trying to find some type of answer to this problem. I have been searching around and trying to figure out how to compile this module but since I am not versed enough in the whole compile process I am kind of lost. I have downloaded and installed EasyDev v6 on my laptop running Ubuntu 10.10, nut that won't even compile the complete rom. I believe it downloaded all the source code it needs(took about 8 hours), when it was finished it told me where to find my new rom, but when I go there it's only a little over 4 megs in size. I will keep plugging away and if I come across some kind of info I will pose it here.
Well I think I figured out how to compile the bnep.ko module. Using my laptop, I found my kernel source and typed
'export CCOMPILER="$PATH_TO_SOURCES"/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi-' and then
'make ARCH=arm CROSS_COMPILE=$CCOMPILER menuconfig'
I was able to select the options for compiling a new kernel. Under networking → bluetooth → bnep
I noticed that it was already enabled. Must be included in the defualt build of the kernel. I told it to build a new bnep module. Saved my config file, and then ran the make -
'make ARCH=arm CROSS_COMPILE=$CCOMPILER modules'
To my surprise it actually build me a bnep.ko module. I copied module to phone into /system/lib/modules/ and tried to install the module.
'insmod /system/lib/modules/bnep.ko' and it told me “insmod: init_module '/system/lib/modules/bnep.ko' failed (Exec format error)”
Great now what. Well I tried the whole bluetooth tether again and guess what, now the bluetooth won't even turn on. I removed the bnep.ko file and was able to enable bluetooth again. Well I guess I am no further along now then when I started, except I have a little more understanding of how to build a kernel.
I have installed PDANet on my Eris and the Toshiba Bluetooth Stack on my Laptop. I am able to use Bluetooth DUN without a problem. The wireless tether for root app would always crash my phone. I am going to try a android tablet in a few minutes. I am running TazzFroyo.
Hi,
I'm not sure whether it's good thing to open one thread related to two problems but I haven't got better idea how to put it.
Main problem:
Since I have acquired my GT540 I'm still searching for the solution for reverse tethering. My operator doesn't have decent data plan, quite often I'm out of any wifi range and currently I'm completely out of wireless.
So I'm left with workable USB connection and Bluetooth. Which leads us to...
Secondary problem:
I found this thread http://forum.xda-developers.com/showthread.php?t=835912 and solution proposed there is quite feasible to me as usbnet still seems to be song of the future and I'm using Linux on the host PC anyway. But when I tried to implement it, I learned that PPP is not enabled in my kernel, which understandably derailed my plan. I use CM7 by Mur4ik.
The question then is, can I somehow painlessly enable this PPP support?
Or could someone politely nudge Mur4ik to enable it in the next release of SwiftDroid? (I don't have sufficient rights to post in devel forum myself)
Or, is there another, working way of getting net access for my phone?
Cheers.
So, you don't have Wireless Adapter or WiFi to put on your desktop and share the internet?
I have tested to share the PC internet connection via USB to GT540 and i never did it...
I bought a WiFi AP and now I use the GT540 with Wireless on my entire house, i think its better than USB.
As I mentioned, sometimes I have wireless access but recently I'm stuck without. Besides, in this most recent cm7-m6 adhoc networking doesn't work either.
Yes, I think too that having wifi coverage in home is nice but the problem I stated is what to do WHEN you don't have it.
So with no bluetooth, anyone have any ideas on how to get GPS on our N2E's (rooted with touchnooter)?
Would a USB GPS receivers work such as a GlobalSat BU-353
Appreciate any feedback, I'm on a mission
We don't think there's bluetooth so it's got to be wifi tethering
I have been trying to use gpstethering app but it doesn't get an ip address. The one time it did, the NT said it was receiving but the data was not updating. The app developer (compton software) doesn't respond.
For gpstethering app, you need to see the address when you pull down the notification window.
I installed a toggle gps app for the NT, then one to allow mock locations.
I am also trying to see if I can feed it serial data as it has serial pins behind the sd card.
Is there such a thing as gps tethering? I mean, GPS has tethering and you just connect to it ad-hoc? What brand of GPS is that?
apeine said:
Is there such a thing as gps tethering? I mean, GPS has tethering and you just connect to it ad-hoc? What brand of GPS is that?
Click to expand...
Click to collapse
Any Android device with a built in GPS can do this.
TetherGPS
Don't use the old ad-hoc patch. As described below it did not even work for me (I saw the network, but could not connect).
Instead it produced just new problems: The wifi reconnect after wake-up stopped working properly, I often had to manually disable and reenable the wifi to get a connection back. And even then it was always very shaky.
I restored the original files and everything seems to be back to normal.
So I would advise against using the very old adhoc patch.
Can someone tell me what the current status on ad-hoc wifi for the NST is?
There is some very old thread about this, that says that you can use the patch for the Nook Color. But it is not clear whether that can be done with the current versions of the Nook, the Nooter, etc., so I am a bit worried about bricking.
Can anyone help? Thanks!
rhhd,
I have a STR with 1.1.1 firmware, rooted, running multitouch, and I've done all the process for running ad-hoc, which runs quite well. Do it! There is a later post on the same thread about changing an entry in a file which allows adhoc run well.
Thanks for the info and for pointing me to the ini post. I did all of this.now I can see the adhoc network, but I cannot connect to it. My Android phone also can't connect to it, so maybe its a general Android problem.or maybe Windows is to blame.
Anyway I now installed Connectify. This works well, so I don't care about adhoc anymore.
Sent from my NOOK using XDA
rhhd,
That problem with disconnecting when sleeping already existed before, so it is not new. I guess it has to be checked with care before announcing it does not work at all.
I am not sure if we talk about the same thing:
Of course the Nook disconnects on sleeping, that is probably intentional to save battery (my HTC Desire does the same).
I am talking about quick and reliable reconnecting after wake-up.
I have tested it pretty extensively on my device, both before the restore and after. Probably took me two hours. So I am pretty sure about this. Of course, it may only apply to my device, but I doubt it.
Connectify allows testing this pretty well, because it allows you to see when the sleeping device disconnects.