Related
Hello,
thank you in advance for your help.
Facts: rooted ICS 4.0.3 IMLK74K.DE_epad-9.4.2.15-20120221
Problem: Everytime when i like to open Accounts & Syncronisation (don't know the exact translation in german it's called "Kontakte & Synchronisation") the dialog suddenly quits.
I installed log viewer to check what's going on, you can see the error message in the Screenshot.
So i think the problem is, that i deleted Pcsynclauncher.apk from ASUS, my question is, can anyone tell me how to extract that file from the Stock ROM i downloaded from here or can anyone post the file on the board?
THX
DidierSchnee said:
Hello,
thank you in advance for your help.
Facts: rooted ICS 4.0.3 IMLK74K.DE_epad-9.4.2.15-20120221
Problem: Everytime when i like to open Accounts & Syncronisation (don't know the exact translation in german it's called "Kontakte & Synchronisation") the dialog suddenly quits.
I installed log viewer to check what's going on, you can see the error message in the Screenshot.
So i think the problem is, that i deleted Pcsynclauncher.apk from ASUS, my question is, can anyone tell me how to extract that file from the Stock ROM i downloaded from here or can anyone post the file on the board?
THX
Click to expand...
Click to collapse
I'm guessing you did not unlock the bootloader yet Try extracting the zip I have attached to your "C:\" , install adb on your pc then run the following command
Code:
adb push C:\PCSyncLauncher.apk /system/app
Code:
adb push C:\PCSyncLauncher.odex /system/app
Follow this guide if you need help installing ADB (http://www.theandroidsoul.com/how-to-install-adb-on-windows-full-guide/)
Thank your for your help.
Had some problems with adb push (permission denied, adb remount gave me operation failed), so i copied the files on the prime and "installed" them with the terminal!
problem solved.
DidierSchnee said:
Thank your for your help.
Had some problems with adb push (permission denied, adb remount gave me operation failed), so i copied the files on the prime and "installed" them with the terminal!
problem solved.
Click to expand...
Click to collapse
Great job thinking out-side of the box. This is how a Dev is born, hope you will join us soon
thx, but there is only one problem called time
Sent from my Transformer Prime TF201 using Tapatalk 2
And I still have that problem, even after installing files
Code:
[email protected]:/data/system/dropbox # cat *
Process: com.android.settings
Flags: 0x8be45
Package: com.android.settings v15 (4.0.3-WW_epad-9.2.2.6-20120525)
Build: asus/WW_epad/TF101G:4.0.3/IML74K/WW_epad-9.2.2.6-20120525:user/release-keys
java.lang.IllegalArgumentException: Unknown package: com.asus.pcsynclauncher
at android.os.Parcel.readException(Parcel.java:1331)
at android.os.Parcel.readException(Parcel.java:1281)
at android.content.pm.IPackageManager$Stub$Proxy.getApplicationEnabledSetting(IPackageManager.java:2423)
at android.app.ApplicationPackageManager.getApplicationEnabledSetting(ApplicationPackageManager.java:1153)
at com.android.settings.accounts.ManageAccountsSettings.updateUi(ManageAccountsSettings.java:198)
at com.android.settings.accounts.ManageAccountsSettings.onStart(ManageAccountsSettings.java:105)
at android.app.Fragment.performStart(Fragment.java:1532)
at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:862)
at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:1032)
at android.app.BackStackRecord.run(BackStackRecord.java:622)
at android.app.FragmentManagerImpl.execPendingActions(FragmentManager.java:1382)
at android.app.FragmentManagerImpl$1.run(FragmentManager.java:426)
at android.os.Handler.handleCallback(Handler.java:605)
at android.os.Handler.dispatchMessage(Handler.java:92)
at android.os.Looper.loop(Looper.java:137)
at android.app.ActivityThread.main(ActivityThread.java:4424)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:511)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:784)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:551)
at dalvik.system.NativeStart.main(Native Method)
1|[email protected]:/data/system/dropbox # ls -la /system/app/PCSyncLauncher.*
-rw-r--r-- root root 44092 2013-05-26 18:01 PCSyncLauncher.apk
-rw-r--r-- root root 18968 2013-05-26 18:01 PCSyncLauncher.odex
adb push didn't work for me either, so copied files randomly. I tried to find the cause but failed. My guess is that somewhere in the system must be written information about this package, but it isn't and I don't know where it should be.
Ok, now I even tried something else but still have negative result:
Code:
pm install /sdcard/Download/PCSyncLauncher.apk
pkg: /sdcard/Download/PCSyncLauncher.apk
Failure [INSTALL_FAILED_DEXOPT]
need a different version
Hi, I just took the poor decision of uninstalling the com.asus.pcsynclauncher package from my TF201 , so I am getting the same exception when trying to access accounts & sync.
I just tried the APK supplied by MasterZen88, however I get error log entries "Package com.asus.pcsynclauncher has mismatched uid: 10003 on disk, 10053 in settings" and a "dexopt failed on .... [email protected]' res = 65280" when installing, which ends up failing.
I assume it is because my ICS version is different: IML74.WW_epad-9.4.2.28-20120525
What do you think? If my assumption is correct, is there anyone that can supply me with the right APK and ODEX?
Thank you for your help.
I have spent many hours traulling the net, scanning through forums across multiple websites and found no information on how to make my device which in its current software incarnation currently seems to only allow MTP as the option for transferring data via the USB cable to and from my Mac running OSX 1.7.3.
Please note, that that google app for file transfers DOES NOT WORK (for me). I cannot get it to work no matter which god I've prayed to or what kinda dance I did. So I looked for alternatives.
ADB worked, but I got tired of ADB to push files across (which is effective, but not what I would call fun). I came across MacPort, giving us ports of Linux/Unix stuff in the world of OSX. YAY!
Found that the various libraries for MTP and MTP-FS was ported! YAY!
After installing the hell out of macport (found: www macports org) and runing the updates.
Drop to the command line and then run these commands once:
Code:
sudo port install libmtp
sudo port install mtpfs
Every time you load your device:
Code:
sudo mtpfs
Awesome! Progress, plug in the device and run mtpfs. But then I get this:
Code:
bergenmacbook:Applications bergenlarsen$ sudo mtpfs
Listing raw device(s)
Device 0 (VID=04e8 and PID=6860) is a Samsung GT-P7510/Galaxy Tab 10.1/S2/GT-N7000/Galaxy Nexus.
Found 1 device(s):
Samsung: GT-P7510/Galaxy Tab 10.1/S2/GT-N7000/Galaxy Nexus (04e8:6860) @ bus 250, dev 6
Attempting to connect device
PTP_ERROR_IO: failed to open session, trying again after resetting USB interface
LIBMTP libusb: Attempt to reset device
inep: usb_get_endpoint_status(): Operation timed out
outep: usb_get_endpoint_status(): Operation timed out
LIBMTP PANIC: failed to open session on second attempt
Unable to open raw device -208647360
I'm running MIUI v4 (2.4.13) with Siyah Kernel (currently 3.1RC5).
Help?
BergenLarsen said:
I have spent many hours traulling the net, scanning through forums across multiple websites and found no information on how to make my device which in its current software incarnation currently seems to only allow MTP as the option for transferring data via the USB cable to and from my Mac running OSX 1.7.3.
Please note, that that google app for file transfers DOES NOT WORK (for me). I cannot get it to work no matter which god I've prayed to or what kinda dance I did. So I looked for alternatives.
ADB worked, but I got tired of ADB to push files across (which is effective, but not what I would call fun). I came across MacPort, giving us ports of Linux/Unix stuff in the world of OSX. YAY!
Found that the various libraries for MTP and MTP-FS was ported! YAY!
After installing the hell out of macport (found: www macports org) and runing the updates.
Drop to the command line and then run these commands once:
Code:
sudo port install libmtp
sudo port install mtpfs
Every time you load your device:
Code:
sudo mtpfs
Awesome! Progress, plug in the device and run mtpfs. But then I get this:
Code:
bergenmacbook:Applications bergenlarsen$ sudo mtpfs
Listing raw device(s)
Device 0 (VID=04e8 and PID=6860) is a Samsung GT-P7510/Galaxy Tab 10.1/S2/GT-N7000/Galaxy Nexus.
Found 1 device(s):
Samsung: GT-P7510/Galaxy Tab 10.1/S2/GT-N7000/Galaxy Nexus (04e8:6860) @ bus 250, dev 6
Attempting to connect device
PTP_ERROR_IO: failed to open session, trying again after resetting USB interface
LIBMTP libusb: Attempt to reset device
inep: usb_get_endpoint_status(): Operation timed out
outep: usb_get_endpoint_status(): Operation timed out
LIBMTP PANIC: failed to open session on second attempt
Unable to open raw device -208647360
I'm running MIUI v4 (2.4.13) with Siyah Kernel (currently 3.1RC5).
Help?
Click to expand...
Click to collapse
Tried installing gvfs-gphoto2 and nautilus?
Read more here:
How To: Fix Samsung Galaxy Nexus MTP File Transfer for Ubuntu GNU/Linux 11.10
Is there a way to root the new 45.4.13 OTA that rolled out? I have tried all the root methods listed on: http://forum.xda-developers.com/showpost.php?p=20331601&postcount=5
Without any luck!
I want to add that I was rooted before applying the OTA.
stevetrooper said:
Is there a way to root the new 45.4.13 OTA that rolled out? I have tried all the root methods listed on: http://forum.xda-developers.com/showpost.php?p=20331601&postcount=5
Without any luck!
Click to expand...
Click to collapse
Wait, what? Even photon-torpedo didn't work?
any updated status with this yet?
I'm curious too...
Please keep us apprised and a system dump would be helpful from someone who has the update.
Sent from my MB855 using xda app-developers app
Shad0wguy said:
Wait, what? Even photon-torpedo didn't work?
Click to expand...
Click to collapse
Nope, tried it multiple times.
Torpedo worked for me this evening.
Sent from my MB855 using Tapatalk 2
Torpedo worked for me, AIO did not.
I still laugh when ppl are still using the AIO root when its been so unreliable in the past. The photon-torpedo method has ALWAYS worked and I don't know why people aren't using the torpedo method to root by default.
OP you must be doing something wrong because the torpedo method still works any many folks have confirmed that.
Glad to hear its still working, here is the error I get:
$ ./photon-torpedo.sh
ERROR: ld.so: object 'libpcprofile.so' cannot be loaded as audit interface: undefined symbol: la_version; ignored.
_XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed
_XSERVTransMakeAllCOTSServerListeners: server already running
Fatal server error:
Cannot establish any listening sockets - Make sure an X server isn't already running
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional information.
ddxSigGiveUp: Closing log
./photon-torpedo.sh: line 5: /lib/libphoton-torpedo.so: Permission denied
ERROR: ld.so: object 'libphoton-torpedo.so' cannot be loaded as audit interface: invalid ELF header; ignored.
_XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed
_XSERVTransMakeAllCOTSServerListeners: server already running
Fatal server error:
Cannot establish any listening sockets - Make sure an X server isn't already running
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional information.
ddxSigGiveUp: Closing log
Then looking at the log:
$ cat /var/log/Xorg.0.log
_XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed
_XSERVTransMakeAllCOTSServerListeners: server already running
Fatal server error:
Cannot establish any listening sockets - Make sure an X server isn't already running
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional information.
(WW) xf86CloseConsole: KDSETMODE failed: Bad file descriptor
(WW) xf86CloseConsole: VT_GETMODE failed: Bad file descriptor
(WW) xf86OpenConsole: VT_GETSTATE failed: Bad file descriptor
ddxSigGiveUp: Closing log
following for further developments..
Reboot has changed the message slightly...
$ /data/tmp/photon-torpedo.sh
/data/tmp/photon-torpedo.sh
ERROR: ld.so: object 'libpcprofile.so' cannot be loaded as audit interface: undefined symbol: la_version; ignored.
Fatal server error:
Server is already active for display 0
If this server is no longer running, remove /tmp/.X0-lock
and start again.
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
ddxSigGiveUp: Closing log
/data/tmp/photon-torpedo.sh: line 5: /lib/libphoton-torpedo.so: Permission denied
ERROR: ld.so: object 'libphoton-torpedo.so' cannot be loaded as audit interface:
invalid ELF header; ignored.
Fatal server error:
Server is already active for display 0
If this server is no longer running, remove /tmp/.X0-lock
and start again.
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
ddxSigGiveUp: Closing log
stevetrooper said:
Reboot has changed the message slightly...
$ /data/tmp/photon-torpedo.sh
/data/tmp/photon-torpedo.sh
ERROR: ld.so: object 'libpcprofile.so' cannot be loaded as audit interface: undefined symbol: la_version; ignored.
Fatal server error:
Server is already active for display 0
If this server is no longer running, remove /tmp/.X0-lock
and start again.
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
ddxSigGiveUp: Closing log
/data/tmp/photon-torpedo.sh: line 5: /lib/libphoton-torpedo.so: Permission denied
ERROR: ld.so: object 'libphoton-torpedo.so' cannot be loaded as audit interface:
invalid ELF header; ignored.
Fatal server error:
Server is already active for display 0
If this server is no longer running, remove /tmp/.X0-lock
and start again.
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
ddxSigGiveUp: Closing log
Click to expand...
Click to collapse
You obviously have not done the root torpedo method before or else you would know that the big ole message you just copied is anticipated and you don't need to worry. You have root successfully.
Just follow this video
http://www.youtube.com/watch?v=zb3Yh_NmSBk
ericdabbs said:
You obviously have not done the root torpedo method before or else you would know that the big ole message you just copied is anticipated and you don't need to worry. You have root successfully.
Just follow this video
http://www.youtube.com/watch?v=zb3Yh_NmSBk
Click to expand...
Click to collapse
Unfortunately the script does not give me the # prompt. So when you run the install-su script it fails. I found others that had the same problem and they never figured out how to get it to work.
ERROR: ld.so: object 'libphoton-torpedo.so' cannot be loaded as audit interface: invalid ELF header; ignored.
Fatal server error: Server is already active for display 0 If this server is no longer running, remove /tmp/.X0-lock and start again.
Please consult the The X.Org Foundation support at http://wiki.x.org for help.
ddxSigGiveUp: Closing log
$ ./install-su.sh Usage: mount [-r] [-w] [-o options] [-t type] device directory cp: /system/bin/su: Read-only file system Unable to chmod /system/bin/su: Read-only file system Usage: mount [-r] [-w] [-o options] [-t type] device directory rm failed for /lib/libphoton-torpedo.so, Permission denied.
just a shot in the dark from a total NOOB are you using an terminal emulator on the phone or via computer??? I needed to do it via computer torpedo worked for me.... just trying to help...... sometimes the most obvious things are overlooked
tiny2nz said:
just a shot in the dark from a total NOOB are you using an terminal emulator on the phone or via computer??? I needed to do it via computer torpedo worked for me.... just trying to help...... sometimes the most obvious things are overlooked
Click to expand...
Click to collapse
Thanks, I have tried with Android Terminal Emulator and adb shell from my PC, neither worked.
tiny2nz said:
just a shot in the dark from a total NOOB are you using an terminal emulator on the phone or via computer??? I needed to do it via computer torpedo worked for me.... just trying to help...... sometimes the most obvious things are overlooked
Click to expand...
Click to collapse
That's a very valid point. After the first soak, many people they needed to use computer, not emulator, for it to work. Wonder is s/he has the right computer drivers?
---------- Post added at 12:59 PM ---------- Previous post was at 12:57 PM ----------
stevetrooper said:
Thanks, I have tried with Android Terminal Emulator and adb shell from my PC, neither worked.
Click to expand...
Click to collapse
Do you have the right drivers? i.e. - do other adb commands work?
willysp said:
That's a very valid point. After the first soak, many people they needed to use computer, not emulator, for it to work. Wonder is s/he has the right computer drivers?
---------- Post added at 12:59 PM ---------- Previous post was at 12:57 PM ----------
Do you have the right drivers? i.e. - do other adb commands work?
Click to expand...
Click to collapse
I downloaded the drivers from the photon torpedo thread. adb works just fine, can push the file to the photon, without any errors. I even tried adb on 2 different computers, Windows XP and the other Windows 7.
The photon-torpedo.sh is very simple:
#!/bin/bash
umask 0
LD_AUDIT="libpcprofile.so" PCPROFILE_OUTPUT="/lib/libphoton-torpedo.so" /usr/bin/X
cat /data/tmp/libphoton-torpedo.so > /lib/libphoton-torpedo.so
LD_AUDIT="libphoton-torpedo.so" /usr/bin/X
When I look in /lib the file libphoton-torpedo.so exists and has a timestamp from when I ran, so its catting the file correctly.
I don't get the # prompt, so running install-su.sh does not work.
Found this in the photon-torpedo thread in Development:
Sparky_McBurning said:
I figured out the problem and a fix.
Problem:
If /lib/libphoton-torpedo.so was not removed from /lib before the OTA update, the permissions are updated to no longer be over-writable, so the /data/tmp/photon-torpedo.sh step that 'cat's libphoton-torpedo cannot re-write the file with new permissions.
Fix:
Update photon-torpedo.sh to use a different filename for libphoton-torpedo.so. I used libphoton-torpedo2.so. No problems. Just make sure you remove any versions of libphoton-torpedo.so from /lib/ after rooting, and you won't have this problem in the future.
Click to expand...
Click to collapse
Hi
I tried to install AMP(apache, mysql, php5) since I was interested on using Atrix as a web server.
Apache was success, but MySQL was failure. No MySQL, No PHP5(of course)
I tried force installing Busybox using dpkg expecting to be updated(version stayed same), removing and making directories that makes the problem, No luck.
I think it's related to my outdated Busybox(readlink?) There's too many problems here.
Lot of people just say "it's impossible" but why not? At least I want to know why it fails.
I have terminal log below. Sorry for bad, bad english.
Thanks
[email protected]:/$ sudo apt-get -f install
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
obconf leafpad lxde-common linux-libc-dev lxrandr pcmanfm lxde-core lxappearance gpicview libc6-dev lxpanel
lxde-settings-daemon xarchiver
Use 'apt-get autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 120 not upgraded.
3 not fully installed or removed.
After this operation, 0B of additional disk space will be used.
Setting up mysql-server-5.0 (5.1.30really5.0.75-0ubuntu10.5) ...
* Stopping MySQL database server mysqld [ OK ]
mkdir: cannot create directory `/var/log/mysql': No such file or directory
dpkg: error processing mysql-server-5.0 (--configure):
subprocess post-installation script returned error exit status 1
Setting up libapache2-mod-php5 (5.2.6.dfsg.1-3ubuntu4.6) ...
readlink: invalid option -- 'q'
BusyBox v1.10.2 (Ubuntu 1:1.10.2-2ubuntu7) multi-call binary
Usage: readlink [-f] FILE
Display the value of a symlink
Options:
-f Canonicalize by following all symlinks
ucf: Unable to determine The new file
dpkg: error processing libapache2-mod-php5 (--configure):
subprocess post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of php5-mysql:
php5-mysql depends on phpapi-20060613+lfs; however:
Package phpapi-20060613+lfs is not installed.
Package libapache2-mod-php5 which provides phpapi-20060613+lfs is not configured yet.
dpkg: error processing php5-mysql (--configure):
dependency problems - leaving unconfigured
No apport report written because the error message indicates its a followup error from a previous failure.
Errors were encountered while processing:
mysql-server-5.0
libapache2-mod-php5
php5-mysql
E: Sub-process /usr/bin/dpkg returned an error code (1)
Click to expand...
Click to collapse
vctshim said:
Hi
I tried to install AMP(apache, mysql, php5) since I was interested on using Atrix as a web server.
Apache was success, but MySQL was failure. No MySQL, No PHP5(of course)
I tried force installing Busybox using dpkg expecting to be updated(version stayed same), removing and making directories that makes the problem, No luck.
I think it's related to my outdated Busybox(readlink?) There's too many problems here.
Lot of people just say "it's impossible" but why not? At least I want to know why it fails.
I have terminal log below. Sorry for bad, bad english.
Thanks
Click to expand...
Click to collapse
Hi, could you solve the issue? I wan to install it too, for my work.
Thanks!
douglasroos said:
Hi, could you solve the issue? I wan to install it too, for my work.
Thanks!
Click to expand...
Click to collapse
I found out it is impossible. Many repos are dead and crucially Ubuntu in this is outdated (without LTS)
I sold the Atrix and bought ARM-based Open PCs (e.g. Raspberry Pi, Cubieboard, Beaglebone Black, Udoo, etc..)
If you want low-power web server, this might be the way to go
(Ubuntu Phone might work but I'm not sure YET)
Hello, I was given a Gtablet by a friend. Everything is in proper working order except for the wifi. The wifi will endlessly scan, never pulling up any SSIDs. Here's what I've done to troubleshoot:
Ascertained flight mode was off (it was)
Enabled wifi through the developer options (Did nothing)
Manually enter SSID/Security information (Claims that SSID is not in range)
Reloaded the OS (He had VEGAn Tab on there. I reloaded the 5.1 Beta. I don't know what version he had on there, oops.)
After a clean install I have the exact same issue, which leads me to believe it is a hardware issue rather than a software issue. Is this common? Am I forgetting something? Would loading an entirely different ROM be of any use or do they also use the same driver?
My apologies if this has been answered previously, but in all my searching I can only find people who have this problem temporarily; a reboot fixes it for them. I haven't been able to find someone who has had this as a persistent issue.
JungleWallace said:
Hello, I was given a Gtablet by a friend. Everything is in proper working order except for the wifi. The wifi will endlessly scan, never pulling up any SSIDs.
Click to expand...
Click to collapse
I'll have to look at some logs to ascertain what your WiFi problem is.
Run the commands in this post (after rebooting the tablet) and then post the text files that're created.
rajeevvp said:
I'll have to look at some logs to ascertain what your WiFi problem is.
Click to expand...
Click to collapse
Thanks, see attached are the logs as per request. As a side note, now that I have the terminal emulator on there I tried a few commands I dug up on the internet after I looked over the logs.
Code:
$ su
# ifconfig tiwlan0 up
# ifconfig eth0 up
Both gave an error message
Code:
error: SIOCGIFFLAGS (No such device)
Also
Code:
# svc wifi enable
did not solve my issues. Oh well.
FYI:
JungleWallace said:
...I tried a few commands I dug up on the internet after I looked over the logs.
Code:
$ su
# ifconfig tiwlan0 up
# ifconfig eth0 up
Both gave an error message
Code:
error: SIOCGIFFLAGS (No such device)
Click to expand...
Click to collapse
The wireless LAN interface name on the gTab is wlan0. Hence your error messages: "No such device" for the ifnames tiwlan0 and eth0. (The latter would work for the ethernet I/F on the dock--if you had one connected.)
Also
Code:
# svc wifi enable
did not solve my issues. Oh well.
Click to expand...
Click to collapse
1. You have to look at the Android system logs (using logcat) to see the result of that svc command.
2. Your Android logs indicate that your WiFi interface is a) disabled at startup and b) then not enabled thereafter:
Code:
01-07 23:21:10.429 V/ConnectivityService( 990): Starting Wifi Service.
01-07 23:21:10.429 I/WifiService( 990): WifiService starting up with Wi-Fi [B]disabled[/B]
Suggestions:
Since this now looks like a ROM problem (ie. not HW):
1. See this thread. Run the script to disable Airplane Mode which might be causing your problem. If that doesn't work, try step 2:
2. Boot into CWM and then a) Format /cache and b) Repartition the Internal SD card (take the external one out first).
You'll lose all your current apps and data with this step, essentially reverting to a "fresh" install of your ROM.
Re-setup WiFi, time & date and other things again.
If step 2. doesn't work, report back next year, and I'll give you more commands to run then.
rajeevvp said:
If step 2. doesn't work, report back next year, and I'll give you more commands to run then.
Click to expand...
Click to collapse
Negative. Ran the airplane fix script, nothing. Reset cache/re-partitioned, still nothing. It's still endlessly scanning/shutting off/scanning.
JungleWallace said:
Negative. Ran the airplane fix script, nothing. Reset cache/re-partitioned, still nothing.
Click to expand...
Click to collapse
OK. Not one of the common simple problems, then.
It's still endlessly scanning/shutting off/scanning.
Click to expand...
Click to collapse
This is puzzling because from your last logs, it doesn't look like the wlan kernel driver was even loaded, so no AP scanning should be possible. A little background will clarify what I mean.
On all the 2.6.32.x kernels for the gTablet, the wlan driver is not compiled into the kernel. Instead, it is built as a separate kernel module which is loaded and unloaded as needed by Android (from the files in /system/lib/hw/wlan/). When the wlan driver is loaded both the kernel (dmesg) and Android (logcat) will show some characteristic messages and until the driver is inserted into the kernel no AP scanning, or other wireless functions, should be possible. And, no wlan driver-related messages in your logs tells me that the driver was likely not loaded. (Also, only after the wlan driver is loaded does it check and initialize the wireless HW. So, only after its been loaded, strictly speaking, can we rule out a HW problem.)
Sometimes the Android logs are not complete, so I want to you setup ADB on your PC, enable USB debugging on the gTablet (Setting > Applications > Development) and collect the Android logs like this from now on:
1. Power off gTab; attach the USB cable to it.
2. Open a CMD.exe window on the PC, then run this command (and keep the window minimized):
Code:
C:\> [B]adb logcat -v time > logcat.txt[/B]
After all the tests/commands have been done, restore this window and press Ctrl-C to kill ADB and terminate Android log collection.
3. Power on the gTablet. The ADB command will wait for the gTablet and keep collecting logs on the PC.
Post also the output of these commands:
Code:
C:\> [B]adb shell dmesg > dmesg.txt[/B]
C:\> [B]adb shell lsmod > lsmod.txt[/B]
C:\> [B]adb shell "cd /; find system -type f -print0 | xargs -0 sha1sum" > sha1sum.txt[/B]
Is this the ROM you currently have?
Have you applied the VEGAn 1.00 beta 5.1.1 supplement also?
rajeevvp said:
OK. Not one of the common simple problems, then.
.........
Is this the ROM you currently have?
Have you applied the VEGAn 1.00 beta 5.1.1 supplement also?
Click to expand...
Click to collapse
That was the current ROM I was using. I had not applied the supplement yet, but now I have. Still the same issue. Here are the logs.
JungleWallace said:
That was the current ROM I was using. I had not applied the supplement yet, but now I have. Still the same issue. Here are the logs.
Click to expand...
Click to collapse
In this one I can see the kernel WiFi driver being loaded, and the driver is not reporting any HW chip, SDIO bus, or other errors:
Code:
<4>[ 23.485281] sdio_reset_comm():
<4>[ 23.503617] DHD: dongle ram size is set to 294912(orig 294912)
<4>[ 23.676913] Firmware version = wl0: May 17 2010 22:38:50 version 4.218.223.1
<4>[ 23.887647] wlan0: Broadcom Dongle Host Driver mac=e0:2a:82:08:3e:81
<4>[ 23.894047] Enter wl_control_wl_start
<4>[ 23.897864] Exited wl_control_wl_start
<4>[ 23.907103]
<4>[ 23.907109] Dongle Host Driver, version 4.218.223.1
As far as the kernel driver is concrned, everything looks OK, but the Android logs still don't show any SSID associations.
What're the exact outputs of these commands? (You can post a screenshot. Mask the psk= value from the 1st output, if present)
Code:
C:\> [B]adb shell "fgrep -v '#' /data/misc/wifi/wpa_supplicant.conf | tr -s '\n'"[/B]
ctrl_interface=wlan0
update_config=1
...
C:\> [B]adb shell wpa_cli -i wlan0 driver rssi[/B]
...
C:\> [B]adb shell wpa_cli -i wlan0 driver linkspeed[/B]
LinkSpeed [I]nn[/I]
C:\> [B]adb shell wpa_cli -i wlan0 scan[/B]
OK
C:\> [B]adb shell wpa_cli -i wlan0 scan_results[/B]
bssid / frequency / signal level / flags / ssid
aa:bb:cc:dd:ee:ff 2452 185 [WPA2-PSK-CCMP] [I]YourSSID[/I]
Collect also the dmesg and logcat outputs as before.
[/FONT]
rajeevvp said:
What're the exact outputs of these commands? (You can post a screenshot. Mask the psk= value from the 1st output, if present) [...] Collect also the dmesg and logcat outputs as before.
Click to expand...
Click to collapse
See attached. Ignore my syntax errors that I underlined. I was typing wlan instead of wlan0.
JungleWallace said:
Ignore my syntax errors that I underlined. I was typing wlan instead of wlan0.
Click to expand...
Click to collapse
Those are OK since you've corrected them. But, these commands you'll have to redo:
1. In the first command (fgrep ... | tr), you've typed a '/' (forward slash) instead of what I've given in the example, which is a '\' (back-slash) character.
The correct character will remove all those blank lines. But, this is a minor typo compared to:
2. The last 2 commands (wpa_cli scan* ...), which you'll have to redo. This time without the extraneous driver argument (again, see the example)--which turns it into a completely different (and non-existent) command. This is why the output doesn't look like what I've shown.
Instead of typing the commands in manually, select and copy the command lines from the browser and paste them into the shell window.
You might also want to increase the no. of columns that CMD.exe displays: Right-click on the title-bar; choose Properties; select Layout; increase the no. of Columns to, let's say, 150.
3. That dmesg.txt file is not very useful because you've not rebooted the tablet before issuing that command.
The kernel has a fixed-size message buffer, so all the HW initialization messages printed only at system boot will be overwritten by later, and irrelevent, messages as time passes. From the timestamps, it looks like your tablet's been on for a couple of weeks, at least--I can't see any of the earlier boot-up messages.