Since I applied the froyo update from Paul's site wifi was working fine for 36 hours.
After a crash caused by copying files on my sdcard I rebooted the phone several times to recover it (another story).
Then wifi stopped working, by "stopped working" I mean the driver won't even load, giving me a warning in logcat, some timeouts in dhd_module_init and "Error" in the control panel.
It has nothing to do with my router configuration because I cannot even enable the wifi to scan for some ssid so it's not a "false alarm" issue...
I tried to flash Stock rom and radio, flash superboot FRF50, the last cyanogen, wipe a few thousand times between all of this but nothing seems to give life back to my wifi chip... I tried flashing InsectRaven and cyanogen .34 kernels with no results...
I can't stop thinking it is hardware related but why ??!! There was no shock, no fall, no EMP from a nuke in the vicinity, everything was smooth when I got back from work and bam !
Is there some options to pass to the driver when I insmod to "reset" the chip in a healthy state ?
Can I somehow compile a debug build giving more informations on my hardware when it is crashing like **** ?
I don't know where to look anymore ... and I'd like some proof thats it is indeed fried...
Here are logs from various sources when I enable wifi in the settings (or insmod /system/lib/modules/bcm4239.ko)
From dmesg : http://pastebin.com/uaRM4EyK
From logcat :
Code:
E/WifiService( 83): Failed to load Wi-Fi driver.
From insmod /system/lib/modules/bcm4239.ko :
Code:
# insmod bcm4329.ko
insmod: init_module 'bcm4329.ko' failed (Invalid argument)
I2C errors in dmesg : http://pastebin.com/ehB7RtN7
Another question , has someone successfully compiled "strace" and "modinfo" to run on android ?
I guess it will be helpful to debug my issue.
Hi,
I'm having a similar issue, thought on another device. Did you find a fix for this?
Thx
Raph
Related
Hi guys. I rooted my legend succesfull and when I go to terminal emulator and type su i gives me the # as it should. But I still can't get Wifi Tethering to work it gives me errors when I push start.
Loading tiwlan_drv.ko module failed
Activating wifi interface failed
setting ad-hoc mode failed
setting essid failed
setting channel failed
Any advice?
Best Regards Liquid211
This might be a little late, but did you or anyone try using this - forum.xda-developers.com/showthread.php?t=754961 - on the Legend?
Have this working well and thought this info may help others...
First, your phone needs to be rooted and busybox properly installed. If you've rooted in the past few days, you're fine as the current payload-update.zip does install busybox with all of the links, but if you rooted early please confirm this before continuing.
Next, grab the tun.ko module from the OpenVPN thread.
Then follow the instructions for the Motorola Droid at the VPN Connections site, using the tun.ko you downloaded previously. The one caveat here is that you have to copy the module in recovery on the Incredible as we don't yet have rw access to the /system partition when booted normally.
Once you've restarted your phone after installing tun.ko, just install the latest VPN Connections apk and you're ready to go!
One point that confused me (for longer than I care to admit) is that once you create a VPN profile, you have to long-press on it to bring up the menu for connect/disconnect.
Enjoy!
Dave
which vpn connections. I downloaded latest from the store it opened but did not work.
then tried the latest from the site and it forces close. I'll start over tonight and try again.
-------------------------------------
Sent via the XDA Tapatalk App
I was working on this the other day, but I cannot get the phone to connect to my company's VPN - I setup the IPSEC ID/PW correctly as well as my user IP/PW, but I get an ISAKMP_N_AUTHENTICATION_FAILED. The one thing I didn't do was copy tun.ko in recovery mode - I just did a modprove /sdcard/tun.ko...it didn't complain and it seems like VPN Connections can find the device node without a problem.
On my linux box, I can run the same config options in vpnc and connect no problem...
I got it working after a couple days playing with it. My problem was that I had not installed busybox to xbin like their instructions outlined since it was already installed to sbin. once installed to xbin and proper permissions were granted, it worked like a charm.
Please someone post a complete how to. I cannot get this working. Busybox will not "--install" to xbin
Is there a secrete to getting busybox installed? I know this is weak sauce, but I need help.
Did you try installing busybox while in recovery mode?
where do I install busybox? /system/xbin or sbin?
Kulaa said:
where do I install busybox? /system/xbin or sbin?
Click to expand...
Click to collapse
I've got it in both places. It needs to be in xbin for the vpnc-script. I tried modifying the vpnc-script but running in to too many problems.
Those to configured their ASA
I am trying to setup the ASA for this VPN. Numerous vague (to me) unresolved errors. Phase 1 completes (easy).
Phase 2 Failure: Mismatched attribute types for class Encapsulation Mode: Rcv'd: Tunnel Cfg'd" Transport
Group = <group>, Username = <username>, IP = <IP Address>, All IPSec SA proposals found unacceptable!
" " Duplicate Phase 2 packet detected. No last packet to retransmit.
I am not finding the answers to these issues. I have not been working on VPNs for long but have setup A LOT of client (Any Connect & SSL) VPNs. I tried to "match" those configurations and have failed.
Anyone know of a tut they used to set the VPN up on the Firewall side? Im sure one of these guys I work w/ can set it up in mins but learning the hard way is what "they" prefer. < a week later is enough, I concede!
Bump ~ 10 ~
Bump ~ 10 ~
Console output?
It think I followed all the necessary steps but wanted to confirm somehow. Is there any ways to see the log on what VPN Connect is trying to do and why login fails?
supagene said:
It think I followed all the necessary steps but wanted to confirm somehow. Is there any ways to see the log on what VPN Connect is trying to do and why login fails?
Click to expand...
Click to collapse
./vpnc --debug 3 --script <path to script> --gateway <gatewayip> --id <VPN Group ID> --username <username>
johnnybags said:
./vpnc --debug 3 --script <path to script> --gateway <gatewayip> --id <VPN Group ID> --username <username>
Click to expand...
Click to collapse
./vpnc --script ./vpnc-script --gateway gateway.domain.com --id "Default Initial G
roup" --username supagene
Enter IPSec secret for Default Initial [email protected]: *******
Enter password for [email protected]: *******
uname: not found
basename: not found
grep: not found
which: not found
grep: not found
which: not found
grep: not found
which: not found
[: not found
readlink: not found
[: not found
[: not found
hash comparison failed: (ISAKMP_N_AUTHENTICATION_FAILED)(24)
check group password!
I know about the comment to check the group password, but I copy and pasted it so I know it is correct. Any suggestions? Do I copy the busy box from sbin to xbin or do I need to look for another busybox, where do you recommend me getting it form? Sorry for the noob questions.
Ok So I looked and found that the Procudures I followed for Rooting didn't actually copy busybox to xbin so maybe the first post should be updated to mention to check that xbin actually has busybox. I used the same busybox that was included in the rooting guide.
Now I'm at a different error.
Error binding to source port. Try '--local-port 0'
Failed to bind to 0.0.0.0:500: Address already in use
that's fine, it means you probably have another process of vpnc running that didn't terminate. just ad --local-port 0 to the end of your command line.
So how is your ASA configured? Is it the latest software or 8.2? ???
Kulaa said:
So how is your ASA configured? Is it the latest software or 8.2? ???
Click to expand...
Click to collapse
Not sure. I just know that the Admin can connect with his Cyanogen Modded G1 and it works great for him. He has his NAND fully unlocked of coarse.
Thanks for all the help I'll post my next issue tomorrow.
Following this thread that was linked for helping to get this working on the Incredible.
I'm getting a constant "unable to connect" error... Where do I need to enable logging to find out more about where the error is happening at? On my ASA or on the Incredible?
Thanks.
I've never got it working but if you look above you'll see how I ran this thin in adb shell. That will output everything to console and tell you what is wrong.
What about subj on FROYO-based FW's?
I tried to enable it on JM5 firmware (Eclair), but no success
We need to compile bnep.ko module for kernel version 2.6.32 and a bluetooth pan daemon - pand.
So, in case of Eclair, i tried to use bnep.ko, compiled for kernel 2.6.29 and pand version 4.47 (see attachments for both).
And what i've done (step-by-step):
1) Inserting our bnep.ko:
Code:
insmod /lib/modules/bnep.ko
2) Copying pand to /system/bin/
3) Trying to start listening for a incoming bluetooth PAN connection by typing:
Code:
pand -n --listen --role NAP
4) .. and seems we have a problem
Code:
pand[7013]: Bluetooth PAN daemon version 4.47
pand[7013]: Failed to connect to the local SDP server. Connection refused(111)
pand[7013]: Bind failed. Address already in use(98)
... and i have no idea whats going wrong.
So, it will be great if someone could compile bnep.ko for FROYO-based firmwares, may be it will be more lucky
Could someone please compile and post the bnep.ko module and pand for the Galaxy Tab wifi P1010. It seems they left it out of a device that desparately needs it, considering it has no 3g.
I actually have no way of tethering this tab with my phone. It does not pick up adhoc wifi (wpa supplicant hack from p1000 does not work on this device), and itbdoes not support bluetooth pan, which is ultimately my preferred tethering solution because of better battery performance.
I tried the above files but they dont work on the p1010. I even tried copying pand from other devices, but so far none of them execute on this device.
Would really appreciate it if someone could compile the above for the p1010. The kernel version is 2.6.32.9 [email protected] #1. Thanks.
A bit late but someone may need it http://www.patthoyts.tk/blog/android-bluetooth-tethering.html
@sinancetinkaya: Thanks, d00d, came in *very* handy!
Hello xda-kaiser-android community
My configuration is :
SDCARD with 4 partitions :
FAT16 with Haret, zimage, inird, default.txt
SYSTEM (ext2)
DATA (ext2)
swap
I've managed to launch Android, and the phones does work.
Unfortunately, at the moment, some other things does not work :
WIFI : fails when getting the IP (so I scan WIFI networks well, but there is a problemn when creating the network interface...)
Modem : does not work..
Camera : not very important for the moment, but can become more...
So, I wanted to dump log files and try, with the terminal, to guess what is happening, but I COULD NOT MANAGED to SU ROOT (as a Linux user, I don't feel comfortable when I cannont be root on my personnal machine)...
When launching the "SuperUser" program the Applist is empty ?
When I set suid and root:root ownership of /bin/su on the SYSTEM partition, when SD mounted on my computer, It is not preserved when used inside Android...
After some inspection of the init scripts (see here under), my question is :
WHY SYSTEM PARTITION IS NOT MOUNTED with ROOT privileges ??
WHY is it chowned to the user 1000:1000 ?
Code:
# mount and set perms
$BB mount -o noatime,nodiratime -t auto $PARTITION $SD_EXT_DIRECTORY;
if [ "$?" = 0 ];
then
$BB chown 1000:1000 $SD_EXT_DIRECTORY;
$BB chmod 771 $SD_EXT_DIRECTORY;
log -p i -t mountsd "$SD_EXT_DIRECTORY successfully mounted";
Thank you for your comments, any help will be appreciated
Regards
Bernie
I overpost myself : My problem probably comes from the way I extracted the Froyo tarball to the SYSTEM partition...
I'll try again and inform you of my mistake.
Regards
why don't you try FAT32 instead of FAT16
bernie.discale said:
I overpost myself : My problem probably comes from the way I extracted the Froyo tarball to the SYSTEM partition...
I'll try again and inform you of my mistake.
Regards
Click to expand...
Click to collapse
Don't extract the froyo tarball. Just place androidinstall.tgz and androidupdate.tgz into the SDCARD andboot folder. Then, after you boot linux, touch and hold the center of the screen, and an install menu will appear. Then select your partitions, install system (and format data partition), install updates, and fix permissions, then exit. Android should start. Be sure your kernel (zImage) and drivers (androidupdate.tgz) match, and it also helps for the initrd.lzma to match. When wifi doesn't work, that usually means the driver is mismatched.
Hi Guys
Thnk you for your answers.
I got a more urgent issue than porting my kaiser to android : I've been forced to move my laptop back to windows again ...
So I must know workaround to dual boot linux (and, believe me, this install of windows is not the standard one)..
But A soon as I can, I will try the install stuff.
thank you again
Heydiho !
Things get better...
I caught eu-froyo-odex and installed it as is after entering the installation menu (launched by init ?)... The su command is now working. I have to tackle a few things now :
Wifi works even worse (now I clealry see an error, where, with the other distro, it was probably a permission issue)
Screen has still odd behaviors
Keymap issue with Keyboard arrows does not work in terminal
And camera to be confirmed
I'll dig the forum for topics on these subjects and get back if I'm really stuck
Best regards
Bernie
Hello
Things goes in the good direction :
Wifi is now ok (was not working with panel 1.. can this be correlated ?)
Screen works better with panel 2, but I'am still not sure if mine is 2 or 3)
Keymap Fixed : was only a matter of using bash insted of default busybox's shell
camera is not working
GPRS modem not working
Battery consumption is high with system on sdcard
Stay tuned !
I am working on a couple of things, specifically a "build.prop" mod and adding a "gps.conf" file to /system/etc, which is just a list of AGPS servers and to fix some GPS issues.
The modded build.prop that I have reworked adds some dalvik cache lines and "sleep mode" lines, as our Kaisers don't have a sleep mode implemented.
Camera and GPRS can be associated with the radio rom installed. I found that on my specific device, radio 1.70.19.09 allowed GPS and data to work smoothly, but I would lose the phone after the first call and camera had just a dark green screen. 1.65.16.25 dropped GPRS but improved data speeds and allowed the phone to work as well as the camera.
YMMV but I would say wipe any trace of WM from that phone (support is ending this May) and go directly with Android via NAND install.
Hello guys
@PoXFreak
I still have some habbits on my WM (freeOTFE encryption, contacts and some other stuffs) that are still working well on WM, and I don't feel very comfortable in switching on full Android (I mean on NAND) while I'am not very used to use Android... I would have definitely preferred to have a working platform booting from sdcard before flashing the NAND, but you confirmed that some issues may be linked to the SDCARD install...
I'm stuck since the beginning of march with the GPRS modem, and I don't clearly understand what are you talking about (have to check what you mean by radio).
My problem is, at the moment, that I don't have any mean to debug : is there a way to activate logs for users spaces programs ? Where to find em ?
If there is a better way to debug, what is it ?
As always, thank you, in advance, for any answer.
I'll try by myself a soon as I can (and, during the last weeks, it was not the case).
Best regards
I will add, moreover, that I'am still not sure of my panel (2 or 3 !!!)
Regards
Hey,
ive some issuse with the vpn connection (cooper gt-s5830).
about the issues with openvpn:
iv'e tried different versions of cm.
The problem is that if i press on a configuerd profile, it says "connect...." for a few sekonds and than abort with a message like "no network connection".
the openvpnserver log looks like no one've tried to connect
I used kali linux to sniff the data while the cooper trys to connect to the vpn server, but there was no output.
so the phone ( the openvpn implementation ) can't send data by wlan.
aktually ive no app to sniff the 3g data, but the issue is the same.
so i think its must be a mistake between the systemapp openvpn and the cm7issues with IPSec Xauth PSK:
if i run the cooper with =>cm9 it will come with android =>4.x.
with android 4.0 the "IPSec Xauth PSK" connection is implementated.
if i try to connect it works. but if im not in the same wlan and trying to use the 3g connection the cooper does a force quit an boot again if i try to acces anything over network......
ive tryed different roms different kernels... i dont know why the issue is every time the same..
vpn is a software solution so it shouldn be addictet to any harware resources... why this works for other phones and not for mine?
is any cooper out there with working vpn?
pelase help me
ps:
i wondert bout this htt p: // w ww . modaco.com/topic/353469-fixed-problem-using-openvpn-on-galaxy-ace-gt-s5830/
i tried many cm7 versions, no one worked...
Open vpn on cm10+
Now im trying to use "OpenVpn for Android" on the cooper with cm10.? Android 4.3
The log says:
Code:
OpenVPN ROUTE: failed to parse/resolve route for host/network: ::/0
Das Öffnen des tun Interfaces ist katastrophal gescheitert.
Fehler: Cannot create interface
ERROR: Cannot open TUN
Process eited with exit value 1
hey, ill be very glad if you reply to my issue...
just test vpn if it works please report to me...
it would be verry nice if i can get a cm backup with working vpn.
i still dont saw a cooper with working openvpn.
in one forum someone wrote he got openvpn working with just installing cm7.
akutally i use the last nightly version downloaded at cyanogenmods website...
but this vopenvpn implementation wont work for me....
in the next week i*l try to debug the coopers system and try to find the destination of the error..
maybe we kan fix it by editing the code before building cm7.
same issue with IPSec Xauth PSK
Hi,
I have the same problem using IPSec Xauth PSK with CM10.1: Connection works, but as soon as data is sent the phone reboots. I have already tried several versions of CM to no avail. Could it be a problem with a hardware driver that is still the original version from Samsung?
A few other people out there report this issue for other phones, as well, but I have seen nobody with a solution.
Thanks,
Theisu