Database Develop

Cyanogenmod 5.0.5.3 - Wireless_tether 2.0_pre8 (and older)

I just loaded my AT&T version with cyanogen 5.0.5.3, and the wireless tether app does not work.
No matter the security settings I use, it always shows unsecure network on my laptop (OSX, Ubuntu and Vista).. If I set it to unsecure in the app, it still does not connect.
I have never used it before, but I am assuming the cyanogenmod kernel has the required bits for the app to work properly.
Am I missing something stupid?
Thanks
-G

ghost_o said:
I just loaded my AT&T version with cyanogen 5.0.5.3, and the wireless tether app does not work.
No matter the security settings I use, it always shows unsecure network on my laptop (OSX, Ubuntu and Vista).. If I set it to unsecure in the app, it still does not connect.
I have never used it before, but I am assuming the cyanogenmod kernel has the required bits for the app to work properly.
Am I missing something stupid?
Thanks
-G
Click to expand...
Click to collapse
Did you turn off USB tethering?

hotweiss said:
Did you turn off USB tethering?
Click to expand...
Click to collapse
Never turned it on, and verified it is off...

how did you load the apk?

lpasq said:
how did you load the apk?
Click to expand...
Click to collapse
Downloaded to SD, and installed from browser download screen...

ghost_o said:
Downloaded to SD, and installed from browser download screen...
Click to expand...
Click to collapse
you may want to adb push method or adb install -r method instead. reboot after install. or try my rom linked in signature.
if you don't know how to use sdk's adb, do a search here on xda for one of the many basic tutorials or ask for details.

lpasq said:
you may want to adb push method or adb install -r method instead. reboot after install. or try my rom linked in signature.
if you don't know how to use sdk's adb, do a search here on xda for one of the many basic tutorials or ask for details.
Click to expand...
Click to collapse
Will do adb.. I have the linux sdk..
Thanks, will post back with results..

OK, installing with adb has the same effect.
There are posts from the google code pages where this has happened in the past (last year though), so I doubt related..
Out of ideas...!

eth0 IEEE 802.11-DS ESSID:"AndroidTether" Nickname:""
Mode:Ad-Hoc Frequency:2.437 GHz Cell: 3A:4E:3D:88:EC:41
Bit Rate=72 Mb/s Tx-Power:32 dBm
Retry min limit:7 RTS thrff Fragment thrff
Encryption keyff
Power Managementmode:All packets received
Link Quality=5/5 Signal level=-57 dBm Noise level=-57 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
This is with WEP set.. It must have something to do with wpa_supplicant somewhere.. I'll keep digging...

maybe it might have something to do with atnt not able to do it throught there network. like us tmobile users can use data while on the phone? dont know alot but that could be a possibility

Nah, wpa_supplicant is not negotiating wep for some reason. I just replace the wpa_supplicant.conf file with a very generic open key WEP config and it still does not work..
I need to dig through my broadcom nda's and find this chip, and see if I can use the firmware.. I'll just load it up in AP mode and run hostapd and be done with it....
Ad-Hoc just plain sucks, almost as much as wep...

Cant find find wireless apk anywhere can someone please give me link

ttieder said:
Cant find find wireless apk anywhere can someone please give me link
Click to expand...
Click to collapse
http://lmgtfy.com/?q=android-wifi-tether&l=1

deprecate said:
http://lmgtfy.com/?q=android-wifi-tether&l=1
Click to expand...
Click to collapse
lmgtfy.com - that was awesome - my family members are gonna feel like idiots asking me questions now!
I had not heard of that site before.

Regarding wep-encryption & CM 5.0.5.x:
http://code.google.com/p/android-wifi-tether/issues/detail?id=292
So, wep-encryption is broken (no idea why) on the latest cyanogenmod-build. Please use CM 5.0.4.1 - it works flawlessly there.
I will take a closer look the next days ... but it's hard to tell what is causing this - I don't know which changes were made on CM.
By the way ... why was this topic moved to Q&A
This is definitely an issue which needs to be solved and should stay in development!

Thanks - I googled for quite a while, and never came across that info. Tethering is not that critical (unless I am travelling), so I will just wait for a fix sometime.
I would have figured other in this forum would have hit it though?!?!?
-G

I've installed 5.0.5.3 and downgraded the kernel which came with 5.0.4.1 - and it start working again! So, I would say that this issue is related to the latest kernel (2.6.33.1)!
I've created an issue on cyanogemod:
http://code.google.com/p/cyanogenmod/issues/detail?id=1217

i have wifi tether pre 8 on latest CM mod and its working great, wep works, and no errors in log.

I am having the same problem. I have both a nexus one and motor milestone. Tethering on milestone doesn't have problems but my nexus can't seem to connect as well no Sep security. I can see the my SSID, anyone can help?

There are obviously factors that differ between devices somehow. I too can change kernels and the issue goes away. Something is "missing" somewhere. A git pulled vanilla 2.6.33 kernel works just fine when booting the zimage from fastboot..
I have not looked at the cyanogen .config or wireless module source yet to see any modifications that would effect it...
I'm more interested in the module working in AP mode now that the driver supports it, and have been working on that...
-G

[HELP]cmd adb error msg...

I already have my pc setup with adb. It appears to be working just fine. I'm trying to setup adb on my laptop and is running into all types of problems. I've downloaded the sdk and ran the sdk setup.exe and downloaded all the latest files, and of course the usb driver. I was able to successfully install the driver and was able to connect my G1 for file transfer. I've followed the guide info to the letter but for some strange reason I get the following:
Code:
* daemon not running. starting it now *
* daemon started successfully *
error: device not found
I've already tried uninstalling the newest driver and installing the working one from my pc, then I tried downloading a driver that was listed by a user in this thread. Still no luck. Any advice would be greatly appreciated!

SG_Shadow said:
I already have my pc setup with adb. It appears to be working just fine. I'm trying to setup adb on my laptop and is running into all types of problems. I've downloaded the sdk and ran the sdk setup.exe and downloaded all the latest files, and of course the usb driver. I was able to successfully install the driver and was able to connect my G1 for file transfer. I've followed the guide info to the letter but for some strange reason I get the following:
Code:
* daemon not running. starting it now *
* daemon started successfully *
error: device not found
I've already tried uninstalling the newest driver and installing the working one from my pc, then I tried downloading a driver that was listed by a user in this thread. Still no luck. Any advice would be greatly appreciated!
Click to expand...
Click to collapse
plug your phone in
get working drivers
install linux, it works better

I already have my pc setup with adb. It appears to be working just fine. I'm trying to setup adb on my laptop and is running into all types of problem
Click to expand...
Click to collapse
[*]plug your phone in
[*]get working drivers
[*]install linux, it works better
Click to expand...
Click to collapse
u forgot a step.
[*]post in the correct forum

Firerat said:
plug your phone in
get working drivers
install linux, it works better
Click to expand...
Click to collapse
1) Done [Don't insult me!]
2) Tried 3 different drivers. All allowed me to connect my G1 to transfer files, but not ADB.
3) ...shouldn't have to install linux. My pc (running windows abviously) works just fine. My laptop, running windows, should work the same.
Thanks for the assistance though...
Daneshm90 said:
u forgot a step.
[*]post in the correct forum
Click to expand...
Click to collapse
Fail!

SG_Shadow said:
1) Done [Don't insult me!]
2) Tried 3 different drivers. All allowed me to connect my G1 to transfer files, but not ADB.
3) ...shouldn't have to install linux. My pc (running windows abviously) works just fine. My laptop, running windows, should work the same.
Thanks for the assistance though...
Fail!
Click to expand...
Click to collapse
read the adb for dummies thread, post in that thread...........................
and
your welcome.
would you like me to wipe your nose as well?

This IS in the wrong forum.
Moved.

Firerat said:
read the adb for dummies thread, post in that thread...........................
and
your welcome.
would you like me to wipe your nose as well?
Click to expand...
Click to collapse
I really wouldn't except this behavior from you, but I see we all fall from grace every now and again. I've posted in that thread already, no one can seem to come up with an intelligent response. I followed all the instructions in both adb help threads for proper installation on my laptop. If you don't know the answer to what I'm seeking, I would honestly prefer you not to reply at all. Don't assume I'm the typical xda idiot, assume I'm the most intelligent person you've ever spoke to, then go from there with your next reply.

SG_Shadow said:
I really wouldn't except this behavior from you, but I see we all fall from grace every now and again. I've posted in that thread already, no one can seem to come up with an intelligent response. I followed all the instructions in both adb help threads for proper installation on my laptop. If you don't know the answer to what I'm seeking, I would honestly prefer you not to reply at all. Don't assume I'm the typical xda idiot, assume I'm the most intelligent person you've ever spoke to, then go from there with your next reply.
Click to expand...
Click to collapse
you posted a couple of hours ago, duplicating posts might be considered spam
you didn't really give any useful information in your post(s)
and if I were to assume your were, then this is just some boring role play thing at a job interview or something, as you wouldn't really need anyones help on this.

Everyone, Chill it.
We don't need a flame war.
Check your firewall. Make sure it's not blocking the connection. Also, are you using the same USB cord on both machines?

ivanmmj said:
Everyone, Chill it.
We don't need a flame war.
Check your firewall. Make sure it's not blocking the connection. Also, are you using the same USB cord on both machines?
Click to expand...
Click to collapse
Thank you for trying to "actually" assist me. I am using the exact same usb cable on purpose to rule that out as a reason. I've also recently update both computers to the latest norton antivirus. Like I stated the drivers install on the laptop and I'm able to connect the G1 for file transfers, so I assume the driver is working but when I type in adb device or adb shell in cmd, I get the no device msg. I'm really stumped with this one...
*Update* My norton did remove adb.exe from windows\system32 on both computers, but I was able to restore that file on both. Like I said, my pc works just fine, laptop no good...

And point 3
Install linux ( ubuntu 10.4 )
Just give it 10gb
It will eliminate hardware faults as being the problem
The android developer has a tutorial for 10.4, so it should be easy
( no need for drivers, aparently 10.4 ships with the android udev rule )

the driver for file transfer isnt the same as the driver for adb....so your logic is flawed
seriously tho, use linux...wubi is pretty good now and u only need 4-10gb if u are only using it for android stuff
in my experience, windows, especially where norton is used, randomly breaks adb

The file transfer is done using the standard windows mass storage driver, not an android specific driver. Even if it's the same norton, try disabling it and see what happens. Also, trying removing the driver completely and reinstalling it again. I've had the issue happen also only when in windows and it's always something random.

virtualbox _should_ ( I think ) let you 'see' the Android Phone regardless of the drivers being installed on the Windows host
But, I have not tested that

Did you ever get this to work, I have the same issue?
I'm having the same issue, I'm trying to use ADB with my TF300T from a Windows 7 64 bit system. Always get the error adb error.
I have a couple of questions will this work correctly with a 64bit O.S?
Also the part of the instructions that reference SDCARD are they talking about the directory on my ASUS /sdcard/ or are they talking about the physical card?
Just need to know does it require you to have a sdcard in the ASUS to use adb?
May sound like fundamental questions to a lot of you, however I have combed through these forums as well as others all over the web, and the majority of instructions seem to be lacking the basics.
Thank you,

I have Ubuntu at work should I run ADB through this?
I have Ubuntu at work
It's a bit of a process according to the instructions that I have on the
screen right now to setup ADB through this, is there any gotchas that I should
know about before attempting this?
This is running on a VM on one of my servers. What I'm looking for is any known compatibility issues with versions of ADB and the Asus TF300T running .26
Thanks in advance.
Nordis

Ethernet MCS7830

I have USB Ethernet on MCS7830
asix.com.tw
FrootAttach/driver/MCS783x_FreeBSD_driver_v1.0.0.1.zip
Can somebody build module?

post in android development and hacking thread.

Ta-da!
I made it. But i have no root.

I have this USB network card and drivers for it (in the end of page). Please help me to add it to my Note.

It's impossible without root.
If you root your phone just load module with insmod.

FedX IV said:
It's impossible without root.
If you root your phone just load module with insmod.
Click to expand...
Click to collapse
I have root. Can you please explain it in detail?

People should learn to click thanks than just keeping to ask questions
Sent from my GT-N7000 using Tapatalk

Hi guys
This is just great news. I was thinking about buying Galaxy Note, but could not decide because it was not clear if there will ever be usb 2 lan drivers.
And now you're writing about it in this thread!!!
Please, Guys, if anyhow possible make it work! Please!
If we get a working version, I will donate for sure. And I'm also sure I'm not the only one interested!!!
Many thanks for your efforts and togetherness!
Sindu

Download and unzip module, then in terminal type
insmod PATH/mcs7830.ko
If it load successful, type something like
ifconfig eth0 inet 192.168.10.15 netmask 255.255.255.0
ifconfig eth0 up

I'm interested in whether this actually works in practice?

Can anyone rebuild this USB ethernet driver pack for Note?
http://forum.xda-developers.com/showthread.php?t=1274656
cuz now i've get:
# ismod: init_module '/system/lib/modules/usb_ethernet/pegasus.ko' failed (Exec format error)
when try to load those built for Tegra drivers

I have a startech.com usb2106s (MOSCHIP usb-ethernet driver 1-3.1.1:1.0: eth0: register 'MOSCHIP usb-ethernet driver' at usb-0000:00:0b.1-3.1.1, MOSCHIP 7830/7832/7730 usb-NET adapter)
And I get the same error trying to load the driver in CM9 ICS.

what exactly it does?

[GUIDE] USB Modem ZTE MF626

Hi everyone,
I wanted to share my struggle of getting my USB Dongle to work. Others will probably work in a similar way and hopefully this helps someone.
What I did:
Disable CD mode on ZTE MF626 via PC
This needs to be done via AT commands on either a Windows or Linux machine. A usefull guide can be found here:
=> wiki.archlinux.org/index.php/ZTE_MF626_/_MF636
If the Modem doesn't show up as serialdevice (check dmesg for /dev/ttyUSB*) entries, ejecting the storage-device (/dev/sr0 for me) could make it to
Check if it registers as Modem on Android
I opened a terminal on my Nexus and checked dmesg if it created those /dev/ttyUSB* devices, which it should after disabling CD mode. I guess your Nexus needs a kernel with OTG enabled. I'm using the default one of codenameandroid.
Connect via PPP app while Wireless is off
I thought this will be the most difficult part, but I found a really usefull widget for that:
=> play.google.com/store/apps/details?id=de.draisberghof.pppwidget
All I needed to do was specifying the serialdevice manually (/dev/ttyUSB2 for me) and entering my connection details (access point name, username, password) and I also changed the dialing target to *99#.
That's all. To connect, you need to turn off WIFI, tapp on the widget and click connect. The screenshot shows the widget
Widget screenshot: imageshack.us/a/img854/9738/screenshot2012092110320.png
(I'm sorry, can't post real links yet..)
Hopefully you can share similar experiences in this thread to make multiple devices work with our (yet) 3g less Nexus 7

http://forum.xda-developers.com/showthread.php?t=1882832
if i am not mistaken the mf100 and the mf626 are the same.

Not similar
kendong2 said:
http://forum.xda-developers.com/showthread.php?t=1882832
if i am not mistaken the mf100 and the mf626 are the same.
Click to expand...
Click to collapse
The tips is Thrue, I use Putty as Hyperterminal. Working good!:good:

Thanks for the share, this is helpful specially the AT command guide. Im using ZTE MF190B and PPP widget does everything for me, but sometimes it does not work always. I'll try the AT command guide.

Putty
ryanrudolf said:
Thanks for the share, this is helpful specially the AT command guide. Im using ZTE MF190B and PPP widget does everything for me, but sometimes it does not work always. I'll try the AT command guide.
Click to expand...
Click to collapse
Read this: it may help you http://www.gprsplans.com/2011/03/how-to-executing-at-commands-under_01.html

Just rooted my remix mini

Yeah!!!!

pcGoose said:
Yeah!!!!
Click to expand...
Click to collapse
How'd you go about it?
Sent from my SM-N920T using Tapatalk

I connected Remix mini to pc with UART cable, and installed update-su.xxx. zip from there.

You GOTTA post some How-To's here!
MANY Remix Mini owners on the planet are trying to accomplish just this!
Great Job, though.

For those who would like to root Remix Mini:
Jide will not offer root access and do not encourage our users to root their devices as it voids the warranty of Remix Mini.

The gain of root access outshadows the lost warranty of any device imo. We are not even talking about a 700$ device here.
Done a quick search here before work. Correct there are 3v and 5v uart? At what voltage level do we need to be to interface with the mini?

RemixOS_Cameron said:
For those who would like to root Remix Mini:
Jide will not offer root access and do not encourage our users to root their devices as it voids the warranty of Remix Mini.
Click to expand...
Click to collapse
i was 1 of the original backers of this kickstarter project and was looking forward with excitement to receiving my mini told some of my friends and relatives who were also enthusiastic, so i received my mini played with it and patiently waited for a method to become available to root it people asked me about my mini but in all honesty could not recommend it because of the lack of root access.
i believe most of the people who backed the project are like myself enthusiasts and have at least 1 or more rooted devices have become dismayed by JIDE`S intransigence by refusing to offer any form of root access they are now playing catchup as remix os gets ported to other devices with better specs . i know were ill be looking for my next version of remix os and it sadly wont be with JIDE.

There's a header for UART on the corner of the PCB. Hook up RX, TX, and GND through a serial port. RX -> TX, TX -> RX and GND -> GND. Serial-to-USB/FTDI works, it's what I'm using right now.
Use minicom (or something like CoolTerm if you're on Windows) to connect: 8N1 (8 data bits, no parity bits, 1 stop bit) with a baudrate of 115200.
Bam. Root terminal.
Code:
[email protected]:/ # ls
acct
cache
charger
config
d
data
default.prop
dev
etc
file_contexts
fstab.sun50iw1p1
init
init.common.rc
init.environ.rc
init.rc
init.recovery.sun50iw1p1.rc
init.sun50iw1p1.rc
init.sun50iw1p1.usb.rc
init.trace.rc
init.usb.rc
init.zygote32.rc
init.zygote64_32.rc
logger
mnt
nand.ko
proc
property_contexts
root
sbin
sdcard
seapp_contexts
selinux_version
sepolicy
service_contexts
storage
sunxi-ir-rx.ko
sunxi_tr.ko
sys
system
ueventd.rc
ueventd.sun50iw1p1.rc
vendor
verity_key
[email protected]:/ #

johnmurrayvi said:
There's a header for UART on the corner of the PCB. Hook up RX, TX, and GND through a serial port. RX -> TX, TX -> RX and GND -> GND. Serial-to-USB/FTDI works, it's what I'm using right now.
Use minicom (or something like CoolTerm if you're on Windows) to connect: 8N1 (8 data bits, no parity bits, 1 stop bit) with a baudrate of 115200.
Bam. Root terminal.
Click to expand...
Click to collapse
http://www.ftdichip.com/Products/Cables/USBTTLSerial.htm
Just for verification. any cable goes since we are not connecting vcc?

It is the cable I am using
"Eruner PL2303HX USB To TTL To UART RS232 COM Cable Module Converter" : Amazon ($6.99)
White -> TX
Green -> RX
Black -> GND
1. Download UPDATE-SuperSU.zip
2. Unzip the UPDATE-SuperSU.zip
3. Copy superSU and META-INF/com/google/android/update-binary(from #2) onto USB drive
on putty
mount -o rw,remount /
mount -o rw,remount /system
cd /system/bin
ln -s busybox-smp unzip
cd /data/local/tmp
cp /mnt/usbhost/Storage01/UPDATE-SuperSU-xxx.zip /data/local/tmp
cp /mnt/usbhost/Storage01/update-binary /data/local/tmp
sh update-binary 0 1 /data/local/tmp/UPDATE-SuperSU-xxx.zip
reboot

Nidor said:
http://www.ftdichip.com/Products/Cables/USBTTLSerial.htm
Just for verification. any cable goes since we are not connecting vcc?
Click to expand...
Click to collapse
Yeah any should work.
I just grabbed the one I had in front of me already, from Sparkfun, which happened to be 3.3V since I'm using it for XBees. Worked fine for me.
pcGoose said:
It is the cable I am using
"Eruner PL2303HX USB To TTL To UART RS232 COM Cable Module Converter" : Amazon ($6.99)
Click to expand...
Click to collapse
If you don't have one already, I'd say go with pcGoose's choice. FTDI ones are pretty pricey these days.

No, we are not connecting vcc。
johnmurrayvi said:
Yeah any should work.
I just grabbed the one I had in front of me already, from Sparkfun, which happened to be 3.3V since I'm using it for XBees. Worked fine for me.
If you don't have one already, I'd say go with pcGoose's choice. FTDI ones are pretty pricey these days.
Click to expand...
Click to collapse

pcGoose said:
No, we are not connecting vcc。
Click to expand...
Click to collapse
Just RX, TX, and GND.
Whoops, didn't mean to imply 3.3V was actually related to the Mini's UART.
Thanks for catching that, didn't intend for that ambiguity.

@johnmurrayvi @pcGoose
Thanks for the info. Finally I can get started on actually using my mini.

SuperSU install doesn't work.
I tried to install SuperSU v265, but it wouldn't install. Then I tried to install SuperSU v246 and it did something, but now Remix isn't booting any more! :crying: I can still communicate with Remix Mini via CoolTerm, but my thumb drive isn't available any more. (I guess you call it not mounted??)
As a Windows User, I guess can use some help here!
Can you post a link to a working UPDATE-SuperSU-xxx.zip ? (I mean one that would work here on Remix Mini)

Guerol said:
I tried to install SuperSU v265, but it wouldn't install. Then I tried to install SuperSU v246 and it did something, but now Remix isn't booting any more! :crying: I can still communicate with Remix Mini via CoolTerm, but my thumb drive isn't available any more. (I guess you call it not mounted??)
As a Windows User, I guess can use some help here!
Can you post a link to a working UPDATE-SuperSU-xxx.zip ? (I mean one that would work here on Remix Mini)
Click to expand...
Click to collapse
https://download.chainfire.eu/696/SuperSU/

I'm about to buy an USBUART PL2302 Cable, hoping it works.

pcGoose said:
https://download.chainfire.eu/696/SuperSU/
Click to expand...
Click to collapse
This is the same SuperSU v2.46, what broke my Remix Mini in the first place...
Could the Remix Mini Version be relevant?
I have another Rexmix Mini unopened in original packaging. Would it help to use this one without updating first?

Guerol said:
This is the same SuperSU v2.46, what broke my Remix Mini in the first place...
Could the Remix Mini Version be relevant?
I have another Rexmix Mini unopened in original packaging. Would it help to use this one without updating first?
Click to expand...
Click to collapse
experiencing the same thing as you. Thought I missed something but haven't had time to play around with it.
I updated to latest os version before trying to root. Everything seemed ok during the steps but after reboot it never gets past second bootlogo and can't seem to mount usb even through terminal cmd...
maybe they implemented something in newer os version that on startup looks for changes/modifications?
If you got the stomach for it I'll say try and root your second one without updating it first.

did you install busybox ?
Nidor said:
experiencing the same thing as you. Thought I missed something but haven't had time to play around with it.
I updated to latest os version before trying to root. Everything seemed ok during the steps but after reboot it never gets past second bootlogo and can't seem to mount usb even through terminal cmd...
maybe they implemented something in newer os version that on startup looks for changes/modifications?
If you got the stomach for it I'll say try and root your second one without updating it first.
Click to expand...
Click to collapse
here is a link to a chinese site the guy said he installed busybox first
h**p://23pin.logdown.com/posts/435610-root-remix-mini