Related
I just successfully rooted my (non-Fender) MyTouch using the howto at the unlockr website. The whole point of it was so I could use a tethering app like Barnacle, but I am finding that my laptop cannot seem to use the connection it provides, even though it sees it and appears to connect.
Further, my phone is now extremely flaky and is unable to fully sync my Google account (contacts are blank and won't sync at all). It often reboots itself for no apparent reason. I am regretting screwing around with it at this point.
Can anyone recommend a ROM to install that is stable and will give me all the functionality I had before I rooted, plus will work well for Barnacle or another good wifi tethering app? And I still don't see exactly where on this site I go to actually download ROMs.
Thanks in advance for any assistance.
Do you have a 32a or 32b board? do you have your sd card with 3 partitions Fat/ext2-3-4/swap?
What recovery did you flash? newest Amen ra 1.70?
What radio and SPL do you have.
We have to know these in order to choose a rom. But there are many good ones, just sounds liek you found a crappy one or one not made for your phone
Improved things with latest cyanogen ROM
Ok, so after my first post I managed to flash my phone with the latest cyanogen ROM. Now the flakiness has gone away and I have back all the stability of my former phone, plus actually a couple things I like better than before.
Alas, Barnacle still does not work properly. It starts and runs fine right up until my laptop or iPad actually tries to connect with it, then I get the message that "process stopped unexpectedly".
Thanks for your response. I will try to find the right place to post my tethering problem to see if someone can help me with it.
Mod. edit: not dev related, moved to general
There is a thread over in the N1 Q&A about this (although i can't post links), but I wanted to post something in here to see if others have seen this issue.
I didn't see much else about this when searching, basically my issues are as such:
My N1 will go to known good wifi networks, at work, at home and at other locations where my other devices work flawlessly. I have a coworker with the exact same firmware (we updated using the same file) on a nexus one that has never seen this problem, which I find odd, but I'm fairly new to Android. It looks like a software or driver issue to me, but as I said, I'm new to Android.
My device shows the known networks as "Disabled", but I can connect manually.
Mine shows the same issue running FRF83. Device is unlocked and the FRF50 was a stock rooted build, the FRF83 is FRF83 stock rooted + insecure + ChainsDD's Superuser app + deodexed update.
there are some screenshots tha tI took if anyone cares to take a look. I'm happy to do any debugging to help resolve this issue. I'm relatively new to android but I'm pretty technical and am not afraid to poke around, etc. I have the SDK installed. Attached are the details of my environment.
Thanks in advance,
nb
i recently read through practically ever HD2 android thread i could find on this site and after a bit of researching installing trial and error i managed to install a working android build on my phone (only functions not working as far as ive seen is wifi tethering)... After i realized it was working i called t mobile and had them switch me to an android plan however i cannot get data service anywhere when i do an H comes up and still cannot connect to facebook apps and things that require internet connection however on wifi everything works and even without wifi i can send calls and get texts sometimes... any help anyone could give me would be great and if you need to know the build or radio info ill google how to find it i guess
What version are you running?
I am running with Wi-fi tethering working and 3G/HSPA working fine. My version of Android does 95% of what I want in an Android phone. The only major features missing in the version I am running are:
Proximity detection(if you put your face to the phone it doesn't disable the touchscreen)
Compass - Don't use it
FM Radio - Don use it
Auto screen brightness control
It would be helpful to post details about your phone s/w (see my signature below for an example).
Like i said im noob a bit lol
My build the facial proximity works, and auto screen brightness as well compass.. i never tried though my GPS im not sure cuz like i said im having issues with the data service so i havent gotten a chance to check... and i would love to post my phone info but as good as i THOUGHT i was with electronics im very new to the phone end of it if you could tell me how id relle appreciate it
At least tell us what Android build you are using.
You know what build you downloaded, unzipped and put on SD card right?
Affter the update to 3.2 on the Wifi model, some people have reported issues with Bluetooth tethering and some have not. It seems that both people are right. It works once, but then after you disconnect, then it will not work again until you restart your Xoom.
There might be other ways around restarting, but so far that has worked every time that I have tried it. Which is annoying since it does take a while to restart. I just go ahead and restart when I have time, and then it is ready to go when I need to enable the connection.
Hopefully this is a minor issue that Google will resolve in 3.2.1
I am currently running stock 3.2 on a wi-fi only Xoom.
-Matt
i have the same issue and its pretty annoying ......hopefully someone can help with an easy work around
I have never been able to bluetooth tether to my Samsung Vibrant. I can connect but tapping on the wrench icon doesn't bring up anything but UnPair.
1+
Sent from my Xoom using XDA Premium App
bt tether does not work from nexus s 4g either...
Matt112211 said:
Affter the update to 3.2 on the Wifi model, ... Bluetooth tethering ... works once, but then after you disconnect, then it will not work again until you restart your Xoom.
Click to expand...
Click to collapse
Same problem with my Defy running CM7. Sucks!
At least we know a reboot will allow us to get back online
+1 tethering to n900
MY Turtle Beach PX5s work just fine on my Xoom via Bluetooth. I can hear music and listen to Netflix just fine.
+1 htc hero, worked before 3.2 now only works on first boot of xoom
Matt112211 said:
It works once, but then after you disconnect, then it will not work again until you restart your Xoom.
Click to expand...
Click to collapse
This is definitely an issue with 3.2.
I started working on it yesterday with Solarnz and BRD. More info to come soon.
Nice one was talking to brd about it earlier but good to know its already being looked at
Sent from my Xoom using Tapatalk
Still no BT working for me.
C_K
OK, since nothing is happening anymore here, I'll get that thread up again.
This issue really sucks, so I tried different things to get it fixed...
What I know: It seems to be a dhcp-problem. If you are rooted and type "netcfg" in a terminal, you'll see that the interface "bnep0" (that's the one for bluetooth-tethering) will only get an IP-address and a subnet-mask on the first connect.
After reconnecting the IP keeps stuck at 0.0.0.0/0. Anyway, it seems that it gets an IPV6-address!?
By typing "su dhcpcd" you sometimes can get a valid IP for bnep0 and a working tethering, but that's not sure... Sometimes you'll get an IP, but the subnet is stuck at 0.
At first I thought it was a bug with the dhcp-deamon, so I pulled /system/bin/dhcpcd out of a 3.1 ROM and pushed it to my 3.2 ROM. Unfortunately there was no difference...
My new ideas are:
1) Maybe it could be possible to define a static configuration for bnep0. My problem is that I don't find the proper config-files. Surely someone can tell me. This way we could maybe work around a dhcp-issue (if it is).
2) Maybe it could(!) also be something with IPV6... It could help to deactivate IPV6, but here it's the same, I don't know how.
Maybe you guys have more ideas! This issue really, really sucks and I am sure we can at least find a workaround! Rebooting can't be the solution.
McDV said:
Maybe you guys have more ideas! This issue really, really sucks and I am sure we can at least find a workaround! Rebooting can't be the solution.
Click to expand...
Click to collapse
Where I last left off, I found that dhcpcd was still running after terminating the initial successful Bluetooth tether. Pre-3.2, both kbnepd and dhcpcd would be stopped.
Killing dhcpcd before attempting a re-tether may be an interim solution. On my device (MZ604 Wi-Fi, 3.2 stock, rooted), if I killed the orphaned dhcpcd process, I could re-tether successfully without a reboot. Savvy users with root, please try this on your device and let me know your feedback:
From a fresh boot, initiate a successful Bluetooth tether
Before terminating the tether, bring up a terminal/adb shell
Run ps, note the kbnepd and dhcpcd processes and their pid's
Terminate the tether
In the terminal/adb shell, run ps again
Note the absence of kbnepd, but dhcpcd still running (same pid as before)
kill dhcpcd
Try re-tethering via Bluetooth
I compared getprop during a successful tether with that after terminating the tether to see if there was a property change which we could use as an init trigger for a hack (kill dhcpcd when x = y), but there was no change. kbnepd doesn't even show on getprop, unfortunately, at least on my device.
Note also that the 3.2 update patches dhcpcd (brd also pointed out changes to ramdisk [init.stingray.rc] regarding dhcpcd) and libnetutils. Comparing logcats between 3.1 and 3.2 and digging through pre-Honeycomb source code gives some indicators that the bug might be in libnetutils. Time wasn't very permitting for me to continue following up on it this week, however.
Until we find a better solution, I was considering putting together a quick and dirty 1x1 widget which rooted users could tap to manually kill dhcpcd before re-tethering. I'll await feedback first on whether manually killing dhcpcd (steps above) works for others. So lemme know.
I've tried it, with no result.
For me there isn't the problem that dhcpcd isn't terminated. Anyway, I've tried to "su kill dhcpcd", but it doesn't help at all...
The idea with libnetutils.so sound good. So I've tried to replace it with the one from 3.1. Unfortunately it ended up in bootloops. Maybe someone could try to fix libnetutils.so
Does s.o. know, if it would be possible, to port the DHCP-client from 3.1 to 3.2? Maybe it would be sufficient to just copy mor than only /system/bin/dhcpcd or libnetutils.so. But I don't know which files need to be copied to not end up into bootloops.
For the moment I downgraded to 3.1, but that's not really satisfying...
No fixes, workarounds or other solutions by now? OK, looks like I'll have to stay at 3.1 'till Ice Cream Sandwich. ;-)
Same issue here, very irritating!
Anyway, it seems that we, who want to use bluetooth-tethering, are a minority, so no one really cares. Neither Google, nore the devs here. ;-) Not even the Tiamat-Team seems to care.
Maybe we'll have to wait until Ice Cream Sandwich is released or maybe there is a 3.2.1 or 3.3 update...
I think it would be possible to port the DHCP-client from 3.1 to 3.2 to solve the problem, but I don't know how.
So the only workaround is using 3.1 - optionally with Tiamat 1.4.4 kernel, because Tiamat 2.1 doesn't work with 3.1 anymore.
Maybe add a comment and star here:
http://code.google.com/p/android/issues/detail?id=18835
I don't care whether you delete this topic or not. It is, somewhat, development related. I'm just doing a new topic for this thing because, if I were to post this on a ROM thread, it would have become covered with 100 other posts within the hour, decreasing the chances of the developer reading it! My hope, with this thread, is that someone interested or someone who knows about this, sees it and does something about it! Please read first, and if you, the one who has the power to delete threads for whatever reason, consider it utterly useless and retarded, delete it.
I'm a new DHD user (switched over from the Desire). This issue was in Sense ROMs for the Desire, as well. The Desire S had this problem with stock GB, too.
In CM-based ROMs such as MIUI (which is what I'm currently using), you get an "Advanced" section under Wireless Networks. From there, you can choose the wi-fi channels (11, 13, 14). On a freshly flashed MIUI, no channel is selected. I have two wi-fi networks in my appartment (one is mine, one is from a neighbour). That second wi-fi network, from my neighbour... my phone does not see it (unless I choose 13 or 14 wi-fi channels).
Funny thing. That neighbour's wi-fi... it's set on channel #3. It's a MSI RG54SE II router, if that matters.
Now, on Sense ROMs, such as Android Revolution HD and RunnyDrOiD (the ones I have tried so far), you don't get the option to choose the channels. So... that RG54SE II is unseen by my phone.
Back when I was having the Desire... Only LeeDrOiD ROM had that "Advanced" section under Wireless Networks. Not sure if that's the case with his ROM for the DHD, as well...
So, this thing is not only for the DHD. It's also for the Desire, and the Desire S. My gilfriend has a DS, and until I convinced her to let me unleash her phone's lockers and flash something on it, she could only see 3 Wi-Fi`s (stock 2.3.3, that is), while I could connect to all 20 that were available in the zone.
--
Hope you get my point. Hope you know what I'm talking about. Hope I'm not the only one that noticed this!!!
If anyone has any idea on how to solve this... please tell me. I have tried LeeDrOiD's "Adhoc networking" (that was the only network-related addon I could find, so...) patch, but that didn't do the work. I don't know what will, since there isn't any addon for this... or I'm blind? Open my eyes, then - KINDLY, not with a banhammer.
Formhault said:
I don't care whether you delete this topic or not. It is, somewhat, development related. I'm just doing a new topic for this thing because, if I were to post this on a ROM thread, it would have become covered with 100 other posts within the hour, decreasing the chances of the developer reading it! My hope, with this thread, is that someone interested or someone who knows about this, sees it and does something about it! Please read first, and if you, the one who has the power to delete threads for whatever reason, consider it utterly useless and retarded, delete it.
I'm a new DHD user (switched over from the Desire). This issue was in Sense ROMs for the Desire, as well. The Desire S had this problem with stock GB, too.
In CM-based ROMs such as MIUI (which is what I'm currently using), you get an "Advanced" section under Wireless Networks. From there, you can choose the wi-fi channels (11, 13, 14). On a freshly flashed MIUI, no channel is selected. I have two wi-fi networks in my appartment (one is mine, one is from a neighbour). That second wi-fi network, from my neighbour... my phone does not see it (unless I choose 13 or 14 wi-fi channels).
Funny thing. That neighbour's wi-fi... it's set on channel #3. It's a MSI RG54SE II router, if that matters.
Now, on Sense ROMs, such as Android Revolution HD and RunnyDrOiD (the ones I have tried so far), you don't get the option to choose the channels. So... that RG54SE II is unseen by my phone.
Back when I was having the Desire... Only LeeDrOiD ROM had that "Advanced" section under Wireless Networks. Not sure if that's the case with his ROM for the DHD, as well...
So, this thing is not only for the DHD. It's also for the Desire, and the Desire S. My gilfriend has a DS, and until I convinced her to let me unleash her phone's lockers and flash something on it, she could only see 3 Wi-Fi`s (stock 2.3.3, that is), while I could connect to all 20 that were available in the zone.
--
Hope you get my point. Hope you know what I'm talking about. Hope I'm not the only one that noticed this!!!
If anyone has any idea on how to solve this... please tell me. I have tried LeeDrOiD's "Adhoc networking" (that was the only network-related addon I could find, so...) patch, but that didn't do the work. I don't know what will, since there isn't any addon for this... or I'm blind? Open my eyes, then - KINDLY, not with a banhammer.
Click to expand...
Click to collapse
This is not the answer you're looking for, but it's worth a mention. You should just ask your neighbor to use a recommended channel. I notice that you're outside of the U.S., where you are supposed to use channels 1, 5, 9 or 13 to prevent wi-fi networks from interfering with each other (within the U.S. you are supposed to use channels 1, 6 or 11). You can make up a story and tell your neighbor that his oddball channel 3 configuration (that he probably decided to use for no good reason) is causing interference with your own network, and you have the technical proof to back it up. From Wikipedia:
"There are 14 channels designated in the 2.4 GHz range spaced 5 MHz apart (with the exception of a 12 MHz spacing before Channel 14). As the protocol requires 25 MHz of channel separation, adjacent channels overlap and will interfere with each other. Consequently, using only channels 1, 6, 11 is recommended in the US to avoid interference. In the rest of the world, the four channels 1, 5, 9, 13 are recommended."
Maybe you can just get your neighbor to follow the rules and switch his network to channel 1, 5 or 9. Then every ROM that you use will have no problem connecting to his network and the problem is solved. I'm assuming you have his permission to use his network resources.
Both my Huawei and his MSI router are configured to channel 3. I put it to that, because there are other 10 networks within this area, and I thought... meh... perhaps they're not using the same channel, lol. Anyway, with the phone, on 14 channels, I only see 5 networks, including mine. With the laptop, I see about 11, so I believe this applies to whatever networks there may be outside, too...
The neighbour I'm talking about... I don't have his permission. I think it's one of those 50 year old couples who don't give a **** about what hardware the ISP installs in their home. Most older-than-45 people here, in my country, know nothing about Wi-Fi, and, since they don't even use it... I wouldn't be surprised if the people who own that MSI router don't even know it's there.
Anyway... the gateway, interface, whatever (192.168.1.1) is accessible, and the user/pass are not changed ("admin', that is). It ain't got a password, neither, obviously. So I could get in and change everything I wished regarding WLAN. Too bad it ain't got /n, but still... I'll try to change the channel even further, and try again with a Sense ROM.
Still, that doesn't fix the issue. Downtown, the most crowded place in the entire city... there are about 25 Wi-Fi networks around (at least that's what I can detect with my phone). My phone (CM-based ROM) can see them all. My girlfriend, with her stock ROM`ed Desire S, could only see 5 or 6. That is no longer the case now, since she's got MIUI, too. And I believe this is the issue with all Sense ROMs : you see 30% of the WLANs you'd see with a CM-based ROM...
I can't ask public stores : hey, your wi-fi... it's set to a channel that my phone just can't see, change it!
Off topic
@Formhault - You risk Jail if you violate the neighbors privacy. It's like you found on the street a wallet full of money and you don't gave back to the injured person.
I posted a thread just like this before and it passed rather unseen. And un touched. Also I asked for a similar situation and had negative answer. But my issue is that I have a VIZIO router.
This is a rather new router and it gives me another option VIZIO HD. Which is more advance and speedier. I have a 12mb connection but I dont have full speed as I cant connect with this.
And a samsung galaxy can also a motorola atrix so I would like to know if someone knows if this can be modified.
Rc mix beast. Inspire 4g nrgz
Firstly, using a persons WiFi without permission is theft, regardless of whether it is locked or not. Does an open window in someone's house mean you can legally steal there belongings?
Secondly, this is not Development related in the slightest.
Thirdly, you want the XDA community to help you find a solution to break the law? You should search for an answer elsewhere. i.e. not XDA.
Thread Closed