This is the Q&A topic for [thread="20962941"]GTabCombOver[/thread].
Does flash player work on this rom?
I think only opera browser
Best HC Yet
I really like this ROM. Couple of items of note that i have seen. My Wifi started to error out. I have tried fixing it, but it still just reports error. I am going to try pershoots kernel. I had issues before with Clems HC kernel. Second I tried inserting a USB disk, and the status bar says USBDisk2 inserted, but it does not appear to be mounted.
Flash
AeroToxin said:
Does flash player work on this rom?
Click to expand...
Click to collapse
Flash works for me in Opera, but it can be a bit touchy.
What version of opera and flash are you using? I downloaded opera mobile 11.1 because 11.5.3 gives me problems, I'll put in a url, push enter, and whatever I type goes away it tries to load the page and just stops (like I pushed cancel on loading the page). Then I was gonna download flash 10.3 and opera started acting up made the tablet slow and had to reboot.
USB and Wifi
markmac said:
I really like this ROM. Couple of items of note that i have seen. My Wifi started to error out. I have tried fixing it, but it still just reports error. I am going to try pershoots kernel. I had issues before with Clems HC kernel. Second I tried inserting a USB disk, and the status bar says USBDisk2 inserted, but it does not appear to be mounted.
Click to expand...
Click to collapse
Does turning it off and on fix the wifi?
I'll look into using a usb disk soon.
No just keeps going into an error state. It seems to be after modifying the WPA_Supplicant with Root Explorer, is when it errors. For work, my company uses LEAP and this is the only way i know of to get it to work. I have done it a hundred times with different ROMs. For some reason unless i leave the wpa_supplicant unmodified, it goes into error. I have double checked and re-checked to see i haven't made any mistakes.
markmac said:
No just keeps going into an error state. It seems to be after modifying the WPA_Supplicant with Root Explorer, is when it errors. For work, my company uses LEAP and this is the only way i know of to get it to work. I have done it a hundred times with different ROMs. For some reason unless i leave the wpa_supplicant unmodified, it goes into error. I have double checked and re-checked to see i haven't made any mistakes.
Click to expand...
Click to collapse
That would probably be the reason. GTabComb has a different wpa_supplicant from most ROMs, so it might not be compatible with the modification you are using. Can you give me more details on what you are doing to modify it?
Sure. Basically I was adding the network, from the Settings applet to use 802.x. I would then modify the supplication to look like the following with Root Explorer:
Network={
ssid=”<networkname>”
scan_ssid=1
key_mgmt=IEEE8021X
auth_alg=LEAP
eap=PEAP
identity=”<domain>\<username>”
password=”<password>”
phase2=”auth=MSCHAPV2”
}
Only after i modified it did it error. Before i modified, the entry was still there, but in the default form which didn't work.
Let me know if there is anything i could test for you. This is the only thing holding me back from finally being happy with an HC ROM.
markmac said:
Sure. Basically I was adding the network, from the Settings applet to use 802.x. I would then modify the supplication to look like the following with Root Explorer:
Network={
ssid=”<networkname>”
scan_ssid=1
key_mgmt=IEEE8021X
auth_alg=LEAP
eap=PEAP
identity=”<domain>\<username>”
password=”<password>”
phase2=”auth=MSCHAPV2”
}
Only after i modified it did it error. Before i modified, the entry was still there, but in the default form which didn't work.
Click to expand...
Click to collapse
Is that the entirety of your wpa_supplicant.conf file or only a fragment? Because, there are other parameters missing, and it says "Network=..." instead of "network=...". Not sure if case matters in the wpa_supplicant.conf file, but, it is something to check.
A detailed debug output would help in troubleshooting your problem. Get it by doing this in CWM:
Code:
$ [B]adb remount[/B]
$ [B]adb shell mv /system/bin/wpa_supplicant /system/bin/wpa_supplicant.bin[/B]
$ [B]adb push wpa_supplicant /system/bin/wpa_supplicant[/B]
$ [B]adb shell chown root.system /system/bin/wpa_supplicant[/B]
$ [B]adb shell chmod 755 /system/bin/wpa_supplicant[/B]
Use this shell script as the wpa_supplicant to push:
Code:
#!/system/bin/sh
exec /system/bin/wpa_supplicant.bin -ddd "[email protected]"
Collect the logs like this:
1. Power off gTab.
2. Connect USB cable.
3. Run "adb logcat -v time > logcat.txt" in a CMD.exe window.
4. Power on gTab.
5. Kill the adb logcat or shutdown tablet after WiFi has errored out.
This will collect all the logs right from the beginning.
That was just the section I edited. I don't have my cable with me so i can't run ADB right now. I did just do the same thing on Flashback and it worked, but I prefer to run GtabCombOver.
heapsize
What app can I use to change the heapsize? Also, dumb question.... What app should I use to adjust the overclocking?
markmac said:
I did just do the same thing on Flashback and it worked, but I prefer to run GtabCombOver.
Click to expand...
Click to collapse
Try using the wpa_supplicant binary from Flashback, then...
---------- Post added at 11:02 PM ---------- Previous post was at 10:59 PM ----------
cgingermany said:
What app can I use to change the heapsize?
Click to expand...
Click to collapse
Just edit /system/build.prop and change dalvik.vm.heapsize.
awesome, thank you! I'll give that a shot. On the dev page someone there said switching those up a little was helping with overall performance so I'll give it a shot and let you guys know. Thanks again.
gtabcombover said:
That would probably be the reason. GTabComb has a different wpa_supplicant from most ROMs, so it might not be compatible with the modification you are using. Can you give me more details on what you are doing to modify it?
Click to expand...
Click to collapse
Actually, I'm having the same problem, and I haven't made any changes to wpa_supplicant.
The only way to get WiFi functioning again is to reboot the device. I can't turn off WiFi, because it just keeps saying "Error." I even tried going into airplane mode, but it made no difference.
In my case, the problem seems to be related to the fact that I've changed the setting for the wifi disconnect policy to "Never when plugged in." I don't remember having this problem prior to making that change.
I've changed it back to "Never" and will report on whether the problem persists.
dagwud said:
Actually, I'm having the same problem, and I haven't made any changes to wpa_supplicant.
The only way to get WiFi functioning again is to reboot the device. I can't turn off WiFi, because it just keeps saying "Error." I even tried going into airplane mode, but it made no difference.
In my case, the problem seems to be related to the fact that I've changed the setting for the wifi disconnect policy to "Never when plugged in." I don't remember having this problem prior to making that change.
I've changed it back to "Never" and will report on whether the problem persists.
Click to expand...
Click to collapse
Mine wont connect at all....... What am I doing wrong?
dagwud said:
In my case, the problem seems to be related to the fact that I've changed the setting for the wifi disconnect policy to "Never when plugged in."
Click to expand...
Click to collapse
Very unlikely.
Will need to look at logs to determine the actual cause of your problem. See post #12. Also get the kernel messages using:
Code:
C:\> [B]adb shell dmesg > dmesg.txt[/B]
---------- Post added at 09:30 PM ---------- Previous post was at 09:23 PM ----------
cgingermany said:
Mine wont connect at all....... What am I doing wrong?
Click to expand...
Click to collapse
Do a basic check. Look at the wpa_supplicant.conf file and see if it looks OK. As a minimum, for home networks, check that the ssid= and psk= values are correct:
Code:
C:\> [B]adb shell cat /data/misc/wifi/wpa_supplicant.conf[/B]
Again, will need to look at logs to find out what's wrong.
rajeevvp said:
Very likely.
Will need to look at logs to determine the actual cause of your problem. See post #12. Also get the kernel messages using:
Click to expand...
Click to collapse
I haven't had time to do as you've requested. However, restoring the setting to the "default" has alleviated the problem. The device appears to be turning off WiFi after a period of time, since it's often had to reconnect after I turn the screen back on.
I'll get to the logs when I'm at my computer and have the time to wait for the wifi error.
Related
The light just stays red forever and never turn green.
pm.sleep is 1
gps is off
any ideas?
Post a dmesg or try the WisTilt2 kernel - but only use the latter if you're able to grab dmesgs and logcats.
bijan588 said:
The light just stays red forever and never turn green.
pm.sleep is 1
gps is off
any ideas?
Click to expand...
Click to collapse
Rogue apps? There's some apps that can kill sleep... I've had a few that I had to outright remove because it kept causing issues with sleep (WeatherBug... freakin' malware.)
Whats a dmsg?
bijan588 said:
Whats a dmsg?
Click to expand...
Click to collapse
It's dmesg, and it's a type of log. Read the FAQ please, it's related to ADB.
As aaarghhh pointed out, dmesg is a kind of kernel log file, that you can get either on the phone itself through a terminal application, or via your PC when it's connected to your android phone (requiring Android Debug Bridge and the apropriate drivers to be installed first).
The FAQ's section on ADB/Logs is good, and I've tried to further clarify getting logs here (in the second step)
and installing ADB here.
Getting your logs by running the commands on your phone is easier, in some ways, although going through the effort to set up ADB and the USB drivers will give you much more flexibility, as well as the ease of dumping the logs straight onto your PC. If you run the command from your phone, you will have to either upload them to xda-dev directly, or dump the file to your SD card and read it from your PC.
I know how annoying it is trying to set up ADB, open a terminal, export logs to local files, copy, paste, etc just to submit a bug report or help a developer diagnose an issue.
That is why I put together this little app to do all of that for you!
This app runs the following commands:
dmesg
logcat -v time -d
logcat -v time -b radio -d
getprop
uname -a
ps
It puts these together into a single document and uploads it to Pastebin, so you can just put a link in a forum thread or IRC or in the bug tracker.
To run these, sadly it needs root. It also requires permissions to read phone identity so that it can automatically mask your ESN/MDN/etc in the logs before it uploads them. It also requires permissions to read account information so that it can mask all of your accounts in the logcat.
EVEN WITH ALL OF THOSE THINGS BLOCKED AUTOMATICALLY PLEASE LOOK OVER YOUR LOG BEFORE GIVING OUT THE URL. IT IS A PRIVATE PASTEBIN AND IF YOU FIND SOMETHING PRIVATE YOU CAN REMOVE IT.
Usage:
Install the app on your phone.
Run the app.
Add any information that should be masked (keep in mind private phone ids and accounts will be masked automatically).
Hit PasteBin! and wait for the upload to finish.
Note the url at the bottom of the screen and give it to whoever requested your logs.
This is just a simple app to help get logs, but if you have any suggestion of how it might be better, do let me know by posting in this thread.
Known Issues:
If you add too many mask strings the app doesn't scroll so you lose the PasteBin! button and/or the resulting URL.
Google Code Project: http://code.google.com/p/getlogs/
Version History:
Version 1.2
Added filtering to "just a file" output
Limited dmesg and both logcats to only 1000 lines each to prevent OutOfMemory Exceptions.
Version 1.1
Added ability to just save the file, no upload. (/sdcard/Android/apps/com.GetLogs/data/)
App now remembers the last message, in case you forget to write down your pastebin address.
Added ps to the list of processes run.
Version 1.0
Initial Version
Upgrade Instructions:
Uninstall current version if installed.
Install new version.
good work, thanks button pushed
Ok so, update - application not installed error, yes I have unknown sources selected, just doesn't install. Any ideas?
Sent from my MSM using XDA App
VistroDistro said:
Ok so, update - application not installed error, yes I have unknown sources selected, just doesn't install. Any ideas?
Sent from my MSM using XDA App
Click to expand...
Click to collapse
Hm, I get the same thing, I've never published an android app before and I chose not to sign it, maybe I need to do that...
EDIT: Ok I signed it and it installs now, sorry about that.
worked like a charm : )
again, good work
Hi,
Is there any way for the file to be dumped on the phone instead of uploading it to pastebin. The user can then pick his way of displaying the file to the world.
This is awesome, gonna install it when I get home so I can get highlandsun some logs of radio failures that occur when I'm at my desk at work. (I never have time to get the logs from the terminal when working, and I can't ADB at work.)
New version in first post, see the Version History for the updates.
Awesome work!
Nice work rpierce99. This should help get us a flood of logs .
Awesome! Will have a try.
I'm running this but it's not giving me a url and I can't see to find the file that it's supposed to create.
Demonic240 said:
I'm running this but it's not giving me a url and I can't see to find the file that it's supposed to create.
Click to expand...
Click to collapse
If you hit the pastebin button the url gets spit out just below the button. If you want the file it is in /sdcard/Android/apps/com.GetLogs/data/
Deleted...
Demonic240 said:
I posted the data file in another thread but I don't think anyone was able to look at it. Here is the logs for my tilt2. The issue I'm running into is that wifi loses the data connection immediately when the phone goes to sleep. The wifi signal does not drop, and in fact still says I'm connected, so the only way to regain data is to turn off the wifi then back on. Would someone be able to look at these logs and help me out here?
Click to expand...
Click to collapse
Hrm...
No offense, but this really doesn't belong here. IIRC, you posted the logs in the FRX06 thread - which is good, but don't you remember me mentioning opening a bug on the tracker? Obviously if there's already a bug open, just add your comments/logs to it... if there isn't already a bug on it, open a new bug with your comments/logs .
Seriously, this has absolutely nothing to do with this thread.
arrrghhh said:
Hrm...
No offense, but this really doesn't belong here. IIRC, you posted the logs in the FRX06 thread - which is good, but don't you remember me mentioning opening a bug on the tracker? Obviously if there's already a bug open, just add your comments/logs to it... if there isn't already a bug on it, open a new bug with your comments/logs .
Seriously, this has absolutely nothing to do with this thread.
Click to expand...
Click to collapse
Ah, I'll remove it then. Sorry about that.
Better dmesg binary
In the interest of having more readable kernel logs...
Delete your current /bin/dmesg and put this one in there instead. Make sure you chmod it 755.
highlandsun said:
In the interest of having more readable kernel logs...
Delete your current /bin/dmesg and put this one in there instead. Make sure you chmod it 755.
Click to expand...
Click to collapse
At work without adb. Using terminal on Rhod.
What am I missing?
Code:
$ $ su
# mount -o remount,rw /
# rm /bin/dmesg
# cp /sdcard/dropbox/dmesg /bin
cp: write error: No space left on device
# ls -l /bin/dm*
-rwxrwxrwx 1 0 0 0 Jun 29 10:10 /bin/dmesg
It does remove dmesg, it does copy the new, but filesize=0
Your rootfs is full. You can install it in /system/bin or /system/xbin instead. There's already one in there too, which is a symlink to toolbox. You should delete the symlink first, of course.
@HYC: Oh yes, sweet. Thanks.
@rpierce99: "Just a file" gives me..... just a file ... and crashes. However, the file is good. Thanks.
Hi i was just looking for some quick clarification if anyone is willing.
Boot into Clockwork Recovery. -DONE
Navigate to "mounts and storage". -DONE
Select "mount USB storage". -DONE
Copy /usr/src/tegratab/boot-custom-kernel.zip to the mounted filesystem. -HOW?
I tried adb push /usr/src/tegratab/boot-custom-kernel.zip /sdcard I dont believe it worked since nothing actually happened. I didnt even get my command line back. Im just waiting though, its been about 10 minutes though, I really dont think anything is happening. Actually it just finished, and now my tab is locked up. After I fix this I hope someone will be able to tell me how to properly install this. Also when I go into the android system then turn on usb storage device and try and drag and drop it says its going to take 3 hours?
I cant seem to figure out how to copy my file to "the mounted filesystem" I dont get a filesystem that I can drag and drop my zip into, I dont see or know of a command to do it through the terminal. So how can I accomplish this?
Thanks!
DKS1282 said:
Hi i was just looking for some quick clarification if anyone is willing.
Boot into Clockwork Recovery. -DONE
Navigate to "mounts and storage". -DONE
Select "mount USB storage". -DONE
Copy /usr/src/tegratab/boot-custom-kernel.zip to the mounted filesystem. -HOW?
Click to expand...
Click to collapse
Need details--
Whose kernel is this? Is it for the gTab? Where was it compiled from (source)? Is it stable? Has it been tested? Why is the guy telling you to copy the zip file onto the internal SD via ClockworkMod when you can do it more easily by other means? Can I have a look at the contents of the zip file?
really? in order to install it you have to know all that? The zip file is over 1.5 gigs.. How do you propose I get it to you?
DKS1282 said:
really? in order to install it you have to know all that? The zip file is over 1.5 gigs.. How do you propose I get it to you?
Click to expand...
Click to collapse
This kernel better be able to sing and dance for you if it's that big. What the hell is in there? I want to see what's in there now.
DKS1282 said:
really? in order to install it you have to know all that? The zip file is over 1.5 gigs.. How do you propose I get it to you?
Click to expand...
Click to collapse
This is why I asked you for the details. A compiled kernel for the gTab, along with the most useful modules, plus the installer program, is about 3MB, max.
The complete Linux kernel source, uncompressed, is around 450MB. Compressed, it is ~100MB. A compressed 1.5GB file would therefore contain a heck of a lot more than just the kernel sources. What were you expecting to happen here? Ram a boat-load of source into the tablet and it should automatically compile and install everything for you?
Actually no... I followed a link and followed directions and I actually thought I was doing well till I saw the size of the file... Im actually going to work on recompiling the kernel again. It was a version of pershoots but I think the tutorial I was working off of is incorrect as are most of them on the net. Im learning but sadly not at the pace I would like, Im new to linux and android. Thank you all for the help so far. I'll post what ive done here in a lil bit and I was wondering if I would be able to get advice on how to install it... Ill even link the tutorial I follow. Here it is http://forum.xda-developers.com/showthread.php?t=916198
Now that Ive gone over it again its an issue in the zipping... For some reason my 28.7M file zips to 1.6gb WTF? Here is the command I used
From inside the file where the contents is to be zipped zip -r /usr/src/tegratab/boot-custom-kernel *
Yes evey time I zip it it comes out to 1.6 gigs. The system file is is pretty small but after its been ziped it actually takes most of the 1.6gb... Could I possible send the meta file, kernel file, and system file? Or maybe someone could tell me how to correctly do this? Ive followed the directions in that link and thought I was getting a legit output but I guess that im not even close.
GOOD NEWS EVERYBODY! I can save you 15% on car insurance...
Actually I was able to figure out what has happened... There were some symlinks that didnt get removed so it grabbed everything in that link and zipped it as well... after I fixed the issue it zipped correctly and I was even able to get it to install... Sadly the prolific driver for the 2303 is still not included even though it shows on the kernel menuconfig as being included, I guess Im going to try again and make it modular and see if I can get the driver file to install that way.. Ill let you know how it goes and also upload and link it if I can get it to work in case someone else wants to grab it and build off it. Im also planning on helping out the forums a little bit...
Thank you again.
DKS1282 said:
Sadly the prolific driver for the 2303 is still not included even though it shows on the kernel menuconfig as being included...
Click to expand...
Click to collapse
Attach the .config (kernel configuration file) so I can look at it.
Does running dmesg on the new kernel show the driver loading/initializing?
Are the /dev/ttyUSB* device files present? Are the permissions for those serial devices correct? I'm not sure what they ought to be, but try making them read+write for all--at least while you are testing things: chmod 666 /dev/ttyUSB* as root.
Here is actually the zipped kernel file. When it compiles it does show the drivers being installed, I just cant get the device to recognize the Prolific cable. Ive tried including them, Ive tried modular, im not sure how to make it work, or if there is something im missing entirely. Thanks again.
http://www.mediafire.com/?nil9bh3spu6sp78
DKS1282 said:
Here is actually the zipped kernel file.
Click to expand...
Click to collapse
The binary is no use to me--I don't have your hardware. The .config file is what I need.
When it compiles it does show the drivers being installed, I just cant get the device to recognize the Prolific cable.
Click to expand...
Click to collapse
The real test is the dmesg output, not whether the driver is being compiled in.
However, I think your problem is that you've compiled the wrong driver. What you need is the driver for "Prolific PL-2301/2302 based cables" which is included by enabling:
config USB_NET_PLUSB
which depends on
config USB_USBNET and
config EXPERIMENTAL
The module will be called plusb.ko, I think.
Sorry for being really uneducated on this. But I can not find any of thoes that you listed in the kernel. Also I cant even find the config file. I know where im targeting it from command line but if I try to move it it says file not found, and if I try and go there visually the file isnt there.
Id love to be able to upload what you want to see, and Id love to be able to add in the items you just suggested. But alas. neither seems possible.
Its honestly odd to me.. Ive been reading a couple different posts on the net that say you install this driver for the Prolific 2303. But not the PL2303.... So why is it included when it doesn't do what its supposed to do? Ive tried a lot of different methods and none of them work. It sucks cause I see people using it. Maybe Its not the kernel and its the android OS? I really have 0 clue at this point and about to just give my resignation at my employment.
The .config file will be present in the kernel's main directory (/usr/src/tegratab/gtab-2632/.config) if you have already built a kernel.
It looks like there are 2 drivers for Prolific hardware in the source tree. One is for host-to-host cables with Prolific chips (which is not enabled by default, and which, I think, is what you want), and the other for a Prolific USB serial port adapter (which is already enabled by default).
To build the module for the first, do a make menuconfig, then select:
Device Drivers > Network device support > USB Network Adapters > Prolific PL-2301/2302 based cables
However, you should verify what you have before you build the module. Do a "lsusb" then check the USB device IDs against the USB ID database in /var/lib/usbutils/usb.ids on a regular Linux machine.
Hints:
0. See pershoot's hints to another user here and further along in the same thread.
1. Make sure that you have downloaded the correct pershoot kernel: froyo or gingerbread.
2. You don't need to include all the modules in your kernel zip file. Just overwrite the kernel proper (zImage), the wireless driver (bcm4329.ko) and then add only the prolific driver module. Otherwise you're just wasting space on the /system partition.
3. Sign the zip file after creating it.
Thank you so much for the attempt.
But my .config file is not located where you have directed me. I checked there before, I could send you a screen shot showing you this.
Thank you for showing me where the driver for the cables where, I would not have checked network adapters looking for USB.... Alas, this has not solved my problem. The cable is still undetected by the OS. Although almost EVERY other usb is detected.
Im really not sure why this wont work. It installs 100% fine I have 0 issues on this, but the Prolific 2303 usb to serial cable will not show up in log cat or anything.. Although when i adb shell and do lsusb I see it and it has a device ID and everything.
Thank you again for the help..
DKS1282 said:
But my .config file is not located where you have directed me.
Click to expand...
Click to collapse
It is created in the kernel's top-level directory (ie. the same directory as the file REPORTING-BUGS) after you do "make menuconfig".
If you still can't find it, do,
find /some/path/ -name .config
after you've finished "make menuconfig". Replace /some/path/ with your kernel source dir (or / to search everything that is mounted).
Alas, this has not solved my problem. The cable is still undetected by the OS. Although almost EVERY other usb is detected.
Click to expand...
Click to collapse
If the driver is built as a module then the kernel will recognize it only after you have loaded the module. Load the correct module first, either plusb.ko or pl2303.ko, depending on your hardware, then check for detection/initialization messages from the module by issuing a "dmesg" command immediately after the "insmod /some/path/driver.ko" command.
Im really not sure why this wont work. It installs 100% fine I have 0 issues on this, but the Prolific 2303 usb to serial cable will not show up in log cat or anything.. Although when i adb shell and do lsusb I see it and it has a device ID and everything.
Click to expand...
Click to collapse
Still lacking details:
1. Did you download the correct kernel--Froyo/GB?
2. Are you sure you're running the new kernel after flashing the zip file?
3. Did you insmod the correct module?
4. What is the USB device ID shown?
5. Did you run dmesg--not logcat--after you insmod'ed the correct module? Can I see that dmesg output?
I can not find a .config file anywhere on this computer. it just does not exist.
Yes I am using a gingerbread version.
Insmod does not install anything for me. Although I installed the modules before even packaging the kernel. Ive verified this by checking in the the correct driver files once installed.
I dont remember the device Id exactly but its something similar to 067b:2303
I didnt run dmesg, honestly, this is way beyond me. I have absolutely no clue what im doing at all... I wasnt even hired for this job.. I was supposed to create an app that will use this specific cable on this specific device, although they did not give me the device able to use the cable... So now I have to figure out how to do this, and im just going to resign and tell them im not a hacker im a developer. Thank you very much for your effort but I am turning in my resignation here now at the end of the day. Thank you again and I'll give you thanks.
You had asked a while back if dev/ttyUSBx has shown, and I did get that to show last night. its dev/ttyUSB0 Ive tried to use a usb to serial api but the app couldn't open the serial port... Im guessing because android does not support that (since they dont really support anything) I personally dont even understand why these things sell... Its a giant useless phone that can not make phone calls. Im in the wrong business I need to sell useless products to consumers.
DKS1282 said:
I can not find a .config file anywhere on this computer. it just does not exist.
Click to expand...
Click to collapse
You a) didn't search correctly, b) haven't built the kernel yet, or, c) done a "make mrproper" and cleaned up.
Yes I am using a gingerbread version.
Click to expand...
Click to collapse
Which ROM?
I dont remember the device Id exactly but its something similar to 067b:2303
Click to expand...
Click to collapse
You cannot be vague about this. Run a Terminal emulator on the gTablet (download one from Market if needed), then type in the command in bold:
Code:
$ [B]lsusb[/B]
Send me the output of lsusb.
I didnt run dmesg,...Thank you very much for your effort but I am turning in my resignation here now at the end of the day.
Click to expand...
Click to collapse
Steady on, mate--we'll get you sorted: Just send me the lsusb output and I'll build a kernel for you--if the current kernel sources include the driver code.
You had asked a while back if dev/ttyUSBx has shown, and I did get that to show last night. its dev/ttyUSB0 Ive tried to use a usb to serial api but the app couldn't open the serial port...
Click to expand...
Click to collapse
Does the app have permissions to read/write the device? Use the chmod command I gave in an earlier post to give permissions.
Next: once the actual hardware is connected to the Prolific cable, is data appearing on /dev/ttyUSB0? Run,
Code:
$ [B]hexdump -C /dev/ttyUSB0[/B]
to see if any data appears.
But, this depends on the device. Some devices need to be triggered, either electrically or by sending commands to the port, before they will send anything back. Other devices will spit data out as soon as power is applied to them.
Which kind is yours?
lsusb returns 067b:2303
My device needs to have data sent to it in order for it to start spitting out data. Otherwise there is nothing happening. It requires a 16bit hex "Start Command". So of course $ hexdump -C /dev/ttyUSB0 returns nothing.
I have the kernel I built here, as well as the gingerbread 2.3.4 rom i am using, and Ive also included the Gaps I needed to install into 2.3.4 to activate the USB feature. (why isnt that feature standard since its really the only difference for 2.3.3 and 2.3.4?
http://www.mediafire.com/?1phzkmvhtr0li
Thank you again.
Honestly you know what would fix all of this... Being able to install windows 7 on this tablet. I know the viewsonic view pad has a dual boot android / windows 7 how cool is that?
DKS1282 said:
lsusb returns 067b:2303
My device needs to have data sent to it in order for it to start spitting out data. Otherwise there is nothing happening. It requires a 16bit hex "Start Command". So of course $ hexdump -C /dev/ttyUSB0 returns nothing.
Click to expand...
Click to collapse
That's assuming that /dev/ttyUSB0 is the correct port, which may not be the case.
Right after the tablet has booted, load both the Prolific kernel modules (or only plusb.ko, if the other is built into the kernel--you still haven't sent me your .config file), attach the Prolific cable to the tablet, then attach the actual device to the cable, then run a
Code:
$ [B]dmesg > /mnt/sdcard/dmesg.txt[/B]
command. Attach the dmesg.txt so I can look at it.
Couldnt do it. Lost the job. Thanks anyway.
Hiya people..
So I was on the first Beta by Team DRH ICS but decided to go back to Beastys.
I went to CWM, wiped everything, installed the beastys.zip and rebooted the G-Tab.
But now when I turn the G-Tab on the screen is just black after the "Notion Ink" bootanimation..
I've tried NVFlashing 4349 Rev4 with the CWM Touch 5504 B14.
Tried with Calkulin+ClemsysFroyo and Beastys+ClemsysFroyo, also tried with and without the SOD Fix for Froyo ROMs.
If I just let the G-Tab boot after the NVFlash it works, it boots up to the TnT ROM.
I've also tried unplugging the battery for 15 sec or so, and pressing the internal reset button.. Still no luck =/
Anyone at all got any clue on how to fix this? =/
ZoZo- said:
Anyone at all got any clue on how to fix this? =/
Click to expand...
Click to collapse
Do these two things:
1. Boot into CWM, run this ADB command and post the output.
Code:
C:\SOME\PATH> [B]adb shell fdisk -l /dev/block/mmcblk3[/B]
2. After installing the ROM of choice in CWM, and before rebooting into the ROM for the very first time:
- power off the gTab
- connect the USB cable to PC.
- run this ADB command on the PC (and keep it running until you encounter the black screen):
Code:
C:\SOME\PATH> [B]adb logcat -v time > logcat.txt[/B]
- now power on the gTab.
This sequence will ensure that all the logs are collected, and right from the start. Kill the log collection after some time and post that output here too.
Ehum... Could the adb shell fdisk -l command have done anything?
Because after another NVFlash 4349 > NVFlash CWM Touch > Flash Beastys... It magically works!
I couldn't initiate any logcat, only get "waiting for device"
ZoZo- said:
Ehum... Could the adb shell fdisk -l command have done anything?
Click to expand...
Click to collapse
If you ran the fdisk while in CWM, then no--the fdisk was just a diagnostic command.
I couldn't initiate any logcat, only get "waiting for device"
Click to expand...
Click to collapse
That is how it should be. ADB will wait until the device is booted up and the ADB server on the device runs.
Different tablet, same problem
This is same topic, but a different tablet.
A friend on mine purchased Xtex MyTablet 7" (ICS); after about a week, the tablet boots into a "blank" screen, after running two bootanimations.
I ran "adb logcat" and can see the system processes running, but screen stays blank, making the tablet unusable.
I ran "adb logcat -v time > logcat.txt" and here is the file:
https://dl.dropbox.com/u/18476770/Android/logcat.txt
This tablet being fairly new, I could not find any support forums for it; I opened a ticket with the supplier, but they are very slow responding.
I turn to XDA, knowing the knowledgeable and helpful people here will shine some light my way.
Thank you in advance
./B
kozmo2k4 said:
This is same topic, but a different tablet.
A friend on mine purchased Xtex MyTablet 7" (ICS); after about a week, the tablet boots into a "blank" screen, after running two bootanimations.
Click to expand...
Click to collapse
Since I don't have that tablet, it's difficult to do comparisons to determine deviant behavior. So, what follows are just guesses:
1. There is this error message in that log which might be relevant (or it might not--I've no idea):
Code:
06-12 21:12:30.659 E/SurfaceFlinger( 85): couldn't find an EGLConfig matching the screen format
06-12 21:12:30.729 E/DisplayDispatcher( 85): Open Display Device Failed!
06-12 21:12:56.849 E/DisplayManagerService( 149): Open Display Device Failed!
2. I noticed that some 3rd party live wallpapers were being loaded. Did the problem start after the live wallpapers were installed? Maybe that's causing problems.
Given that you are able to see 2 (?!!!) boot animations before the display goes blank, I would have to guess that its no. 2 (heh!) that's causing problems. Uninstall all the live screensaver packages using ADB. Use this as a guide.
As a last resort, you could try going into CWM (if it's installed) and do a "wipe data/factory reset", then re-install the ROM. You will lose all data with this.
Thank you for the fast reply, rajeevvp.
I'm sorry I said it wrong earlier, there is only one boot animation, the "old school" letters: ANDROID, with a light beam running across them. There are two "boot logos" that flash on the screen prior to that. My PC, right now logged in on Win7x64, recognizes the tablet connected (USB device connected jingle) at the Android bootani.
I'm going to try to adb uninstall some of the apps and we'll see what happens.
Thanks for the insight.
./B
[EDIT]: Unfortunately, no CWM installed. I can't even figure out any kind of recovery on this. Only physical buttons are: Power, Menu and Escape. I tried all combinations, but it just boots up.
---------- Post added at 05:23 PM ---------- Previous post was at 04:50 PM ----------
Follow up:
ADB has root access, I can browse all directories (i.e. /data/data)
adb uninstall, all I get is "Failure"
In adb shell, after remount rw, command: rm -f /data/app/.apk
says "No such file or directory"
I know I typed the package name (com.cellfish.livewallpaper.marvel_avengers-1.apk) correctly. Hmmm
./B
kozmo2k4 said:
Follow up:
ADB has root access, I can browse all directories (i.e. /data/data)
adb uninstall, all I get is "Failure"
Click to expand...
Click to collapse
What is the exact command you used? As the document says, if you are using ADB, you should do:
Code:
C:\SOME\PATH> [B]adb uninstall [I]packagename[/I][/B]
Unfortunately, no CWM installed. I can't even figure out any kind of recovery on this.
Click to expand...
Click to collapse
If you can figure out how to get into stock recovery (it would be very unusual to not have one--its needed for ROM upgrades for instance), then you could try this:
Clear Cache and Data from Stock Recovery
Thank you for the reply.
Here is what I've tried:
Code:
adb uninstall com.cellfish.livewallpaper.marvel_avengers-1.apk
then the app full name I found in Play Store
Code:
adb uninstall The Avengers Live Wallpaper
Al I get is "Failure"
Next I tried
Code:
adb shell
[email protected] # mount -o rw,remount /data
[email protected] # rm -f /data/app/com.cellfish.livewallpaper.marvel_avengers-1.apk
The I get:
rm failed for -f, No such file or directory
I was not able to figure out how to get to recovery of any sorts; like I mentioned, only 3 physical buttons, Power, Menu and Esc. Tablet has microSD slot, Mini HDMI, 3.5mm headphone, Mini-B USB and full USB ports. That's all. I'm getting close to opening the case to see if there is a reset button, but waiting for my colleague's pernission (she'll most likely just send it back).
Update:
I was able to remove the live wallpaper in adb (just omitted the -f after rm), but no cookie....black screen after boot.
Is there a way to wipe-factory reset with adb? Just delete the contents of /data/app directory? .... Only one way to find out...
---------- Post added at 06:22 PM ---------- Previous post was at 05:59 PM ----------
Update II:
Code:
adb shell wipe data
did the trick, tablet booted up just fine (except for the Chinese language...lol).
Thank you again for all your help!
Linux ROCKS
./B
Follow up post
Just a follow up:
A couple of days later, my colleague had brought the tablet back with black screen again.
After a little "interrogation", I found out that she actually hit the brightness button on the Power Widget a couple of times and that had dimmed the background light to ZERO.
Having more information than before, I've came across two possible solutions:
1. Use LED flashlight and shine it on the screen at a certain angle and try to make out the icons on the (LCD) screen and re-adjust the brightness...
2. Use Droid Explorer with the "Screen Cast" java applet to mirror the screen on a PC and try to adjust the brightness that way.
3. Try to reset the brightness sqlite database (way out of my league; I'm a "hardware guy", not a programmer...)
Well, number 2 was the winner!
So, for future reference, if anyone get "black screen only" and have ADB set up on your PC, use the Droid Explorer (http://de.codeplex.com/) with Screen Cast plugin to access you Android device.
I hope this will help someone....
kozmo2k4 said:
Code:
adb uninstall com.cellfish.livewallpaper.marvel_avengers-1.apk
Click to expand...
Click to collapse
You have to use the package name and not the apk name to adb uninstall. Look inside the /data/system/packages.list file to determine this.
Update II:
Code:
adb shell wipe data
did the trick, tablet booted up just fine (except for the Chinese language...lol).
Click to expand...
Click to collapse
A bit drastic, but, that works . But, I wouldn't have recommended wiping the /data partition like that while inside the ROM. This is why a recovery mode exists.
I wouldn't be surprised if after a wipe like that and a subsequent filesystem check, the /data/lost+found directory contained more than a few files/dirs.
---------- Post added at 11:16 PM ---------- Previous post was at 11:13 PM ----------
kozmo2k4 said:
Just a follow up:
A couple of days later, my colleague had brought the tablet back with black screen again.
After a little "interrogation", I found out that she actually hit the brightness button on the Power Widget a couple of times and that had dimmed the background light to ZERO.
Having more information than before, I've came across two possible solutions:
1. Use LED flashlight and shine it on the screen at a certain angle and try to make out the icons on the (LCD) screen and re-adjust the brightness...
2. Use Droid Explorer with the "Screen Cast" java applet to mirror the screen on a PC and try to adjust the brightness that way.
3. Try to reset the brightness sqlite database (way out of my league; I'm a "hardware guy", not a programmer...)
Well, number 2 was the winner!
So, for future reference, if anyone get "black screen only" and have ADB set up on your PC, use the Droid Explorer (http://de.codeplex.com/) with Screen Cast plugin to access you Android device.
I hope this will help someone....
Click to expand...
Click to collapse
+1 kozmo2k4. We need more smart users like you on the board.
Thank you for the kind words, rejeevvp. I love to "tinker" with things and do not give up that easily.
I know the "adb shell wipe data" was an overkill, like chasing a fly with a .50cal, but at that point in time it was the most feasible.
I've tried all possible button combinations to get into recovery, but everything led to regular boot.
After the successful booting into the ROM, I did notice an option under settings>development to boot Recovery. Which I did, and was presented with a basic "blue" Android System Recovery .
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I did another Wipe Data and wipe Cache and rebooted.
Everything seemed to be working fine afterwards, and my colleague texted me that the tablet is running faster and smoother than when she first got it, so everything is all good.
[Edit] Funny thing I just noticed, in the picture it says to use (Q7, volume up/volume down, Home, Enter), however, there were no "hard" buttons labeled that, only: Power, Menu and Escape!
Here is the front:
Sent from my NookColor CM9 using Tapatalk 2
kozmo2k4 said:
After the successful booting into the ROM, I did notice an option under settings>development to boot Recovery. Which I did, and was presented with a basic "blue" Android System Recovery .I did another Wipe Data and wipe Cache and rebooted.
Click to expand...
Click to collapse
+1 again. That is the right thing to do.
[Edit] Funny thing I just noticed, in the picture it says to use (Q7, volume up/volume down, Home, Enter), however, there were no "hard" buttons labeled that, only: Power, Menu and Escape!
Click to expand...
Click to collapse
Tried the soft buttons? ...but, yeah, that's Android for you--basically not a lot of QA going on anywhere. Even the top guns like Asus seem to be asleep at the switch.
BTW, I think I've found where the screen brightness level is stored--at least for Gingerbread. Care to run a few test commands with that tablet?
Reset Brightness
rajeevvp said:
+1 again. That is the right thing to do.
Tried the soft buttons? ...but, yeah, that's Android for you--basically not a lot of QA going on anywhere. Even the top guns like Asus seem to be asleep at the switch.
BTW, I think I've found where the screen brightness level is stored--at least for Gingerbread. Care to run a few test commands with that tablet?
Click to expand...
Click to collapse
Soft buttons work while in ICS; when tablet was off, only "hard buttons" were available.
I would be more than happy to run few tests, but I returned that table on Sunday (have the feeling that wasn't the last time I saw it, though).
During my "research", I came across these possible locations of brightness setting on ICS:
/sys/class/backlight/rk28_bl/brightness
or
/sys/class/leds/lcd_backlight/als
(however, I don't see "rk28_bl" or "lcd_backlight" on my gTablet ICS 4.0.4, or my SPH-D710 2.3.6 under /sys/class; I have "/sys/class/pwm-backlight/" tree on both devices:
There was also a script to reset brightness to 100% in sqlite database
Code:
#sqlite3 /data/data/com.android.providers.settings/databases/settings.db
sqlite> update system set value=255 where name='screen_brightness';
sqlite> .exit
#reboot
But I did not get to try any of that, since I got lucky with Android Commander and ScreenCast.
kozmo2k4 said:
During my "research", I came across these possible locations of brightness setting on ICS:
/sys/class/backlight/rk28_bl/brightness
or
/sys/class/leds/lcd_backlight/als
(however, I don't see "rk28_bl" or "lcd_backlight" on my gTablet ICS 4.0.4, or my SPH-D710 2.3.6 under /sys/class;
Click to expand...
Click to collapse
Everything under /sys/ depends on the kernel. Some files and directories are standard, some, like the above, are not.
I have "/sys/class/pwm-backlight/" tree on both devices:
Click to expand...
Click to collapse
Interesting...don't have that on the pershoot kernel. Try fiddling with the values in "brightness" as root.
There was also a script to reset brightness to 100% in sqlite database
Code:
#sqlite3 /data/data.com.android.providers.settings/databases/settings.db
sqlite> update system set value=255 where name='screen_brightness';
sqlite> .exit
#reboot
Click to expand...
Click to collapse
+1 again. The path is different (/data/data/...) but that's what I meant. There is also the 'screen_brightness_mode' setting. 1 => Auto brightness, 0 => manual brightness, I think. You may need to change both.
rajeevvp said:
Everything under /sys/ depends on the kernel. Some files and directories are standard, some, like the above, are not.
Interesting...don't have that on the pershoot kernel. Try fiddling with the values in "brightness" as root.
+1 again. The path is different (/data/data/...) but that's what I meant. There is also the 'screen_brightness_mode' setting. 1 => Auto brightness, 0 => manual brightness, I think. You may need to change both.
Click to expand...
Click to collapse
That was a TYPO on my part (fixed on original post for future reference).
My gTablet is on ICS (actually I just flashed AOKP, running pretty good so far) with TeamDRH kernel. My phone is on stock EL29-repack (Calkulin's v3.0) kernel.
Hope all this info will come in handy for someone in the future!
I am glad you were able to solve this issue for your friend because I did exactly the same thing as she did and now I have black screen.
I could not follow all the discussion so, is it possible to dumb it down so I can repeat what you did to fix that XTEX tablet?
Thank you
fazluke said:
I am glad you were able to solve this issue for your friend because I did exactly the same thing as she did and now I have black screen.
I could not follow all the discussion so, is it possible to dumb it down so I can repeat what you did to fix that XTEX tablet?
Thank you
Click to expand...
Click to collapse
Do you have ADB.set up on your PC?
If so, go ahead download and install Droid Explorer (there is a link few posts back).
Once installed, run it, ensuring you "powered on" tablet is recognised. Along the top row of icons, there is one called Screen Cast (hovering over the icons will show the name). Select it, let the Java applet install, then click Screen Cast and that should open a new window, mirroring the tablets screen. Then you can navigate on the tablet to settings.... and get it set.
I think there may be a video on YouTube showing this.
Hope this will help.
[Edit] Here is a link to Youtube:
http://www.youtube.com/watch?v=eEeHaszOMi0&feature=youtube_gdata_player
Sent from NOOK Color CM7.2 using Tapatalk 2
Thanks for the quick response, will download and follow your directions, then report back tonight.
fazluke said:
Thanks for the quick response, will download and follow your directions, then report back tonight.
Click to expand...
Click to collapse
Worked exactly as described with minor issue. Screen cast does not work on locked device. I see the locked screen but can't unlock it and the Youtube link confirmed that too.
I tried to turn it off and on, to see if I can get hold of it before it goes into locked mode and after few tries I got it to work.
Another issue was that my mouse will not control it. SO looking at the computer screen and moving my finger on the tablet surface, I managed to get to setting/display and adjust brightness.
Thank you again for your help.
I'm having an issue with the wireless on the g tablet. It's stuck on "Turning Wif-Fi on... and never turns on. I've tried flashing back to stock tnt, clearing any possible cache/system files I can think of. I'm currently running on the newest version of smoother bean that I just installed for the 3rd time just to make sure I didn't have an issue when flashing the rom. I've had no issues with it up until a few days ago. My friend borrowed it, tried to connect to a different wireless network. They input the password wrong once, and then it went to turning on and has been stuck there ever since. Help, i'm at my wits end! Thanks in advance
gargator said:
I'm having an issue with the wireless on the g tablet. It's stuck on "Turning Wif-Fi on... and never turns on.
Click to expand...
Click to collapse
Get hold a dmesg output like this: Reboot the tablet. Then, after the WiFi fails, open a Terminal Emulator window and type in the command line in bold.
Code:
$ [B]dmesg > /mnt/sdcard/dmesg.txt[/B]
Post the .txt file here.
rajeevvp said:
Get hold a dmesg output like this: Reboot the tablet. Then, after the WiFi fails, open a Terminal Emulator window and type in the command line in bold.
Code:
$ [B]dmesg > /mnt/sdcard/dmesg.txt[/B]
Post the .txt file here.
Click to expand...
Click to collapse
I'm a bit of a noob using the terminal emulator. When i type that command in, it says "operation not permitted".
You are going to have to give the terminal SuperSU. Permission first. Type in "su" first and grant it the permission the enter in the command.
gargator said:
When i type that command in, it says "operation not permitted".
Click to expand...
Click to collapse
That's a strange error to get. Post a screenshot, or, exactly what you typed in and the response you got back.
Since I'd rather not troubleshoot some obscure "ROM-not-setup-correctly" bug on top of a "WiFi-not-working" bug, see if you can run the dmesg via adb (set it up first if you have to). Connect the USB cable to the gTab, then in a CMD.exe window on the PC type:
Code:
C:\> [B]adb shell dmesg > dmesg.txt[/B]
---------- Post added at 12:59 AM ---------- Previous post was at 12:56 AM ----------
nobe1976 said:
You are going to have to give the terminal SuperSU. Permission first. Type in "su" first and grant it the permission the enter in the command.
Click to expand...
Click to collapse
Why do you now need Superuser permissions to run dmesg or write to /mnt/sdcard? Are you doing something non-standard on Smoother Bean, Nobe?
Not that I am aware of. I just saw that he got the permission issue and tried it myself. Got same message and went ahead and su the terminal and was able to get the text file onto internal storage. Will look into this, but it is not a major.
Sent from my DROID BIONIC using xda app-developers app
nobe1976 said:
Will look into this, but it is not a major.
Click to expand...
Click to collapse
Well, it might be.
What it says is that an app which normally has permission to write to the SD card is unable to do so for some reason. Which implies that other apps also having the same permissions (sdcard_rw) might also have problems and so act screwy.
rajeevvp said:
Well, it might be.
What it says is that an app which normally has permission to write to the SD card is unable to do so for some reason. Which implies that other apps also having the same permissions (sdcard_rw) might also have problems and so act screwy.
Click to expand...
Click to collapse
Attached to post is .txt file.
If you have an external SD card in the slot, remove it, then boot the tablet up. See if the WiFi starts working.
Also, get me another dmesg output.
rajeevvp said:
If you have an external SD card in the slot, remove it, then boot the tablet up. See if the WiFi starts working.
Also, get me another dmesg output.
Click to expand...
Click to collapse
Wow...that fixed it. You managed to determine from that .txt file that the sdcard was preventing the wifi from turning on? You are a true genius. Thanks so much for the help.
gargator said:
Wow...that fixed it. You managed to determine from that .txt file that the sdcard was preventing the wifi from turning on? You are a true genius. Thanks so much for the help.
Click to expand...
Click to collapse
So glad that you guys figured it out. The nexted step is to find out how it happened. If you can for me connect your micro sdcard to your PC and open up to view hidden files. Certain ROMs place hidden files on storage to run and if the card was running on a different device that could of been what caused the issue. Delete any hidden files and folders once they display and empty the trash can. If using Linux once you delete those files and folders another one will pop up named trash, delete that also.
Sent from my SmoOth A$$ Gtablet
nobe1976 said:
The nexted step is to find out how it happened. If you can for me connect your micro sdcard to your PC and open up to view hidden files. Certain ROMs place hidden files on storage to run and if the card was running on a different device that could of been what caused the issue.
Click to expand...
Click to collapse
Nope. This isn't a software problem at all. It's a HW fault--most likely with his microSD card: You can clearly see the kernel repeatedly trying, and failing, to read that card. And that, for some reason, causes the WiFi to go wonky because it is connected to the main system bus via a SDIO (an SDcard-like) interface.
gargator said:
You managed to determine from that .txt file that the sdcard was preventing the wifi from turning on?
Click to expand...
Click to collapse
It was actually quite simple to figure what the problem was from the error messages.
As I said above, you'll most probably have to replace your microSD card. But, to rule out bad electrical connections being the problem, it wouldn't hurt to clean the contacts on both the microSD card and inside the microSD card slot on the gTablet with some rubbing alcohol. See if you can get your data from the card after that.
rajeevvp said:
Nope. This isn't a software problem at all. It's a HW fault--most likely with his microSD card: You can clearly see the kernel repeatedly trying, and failing, to read that card. And that, for some reason, causes the WiFi to go wonky because it is connected to the main system bus via a SDIO (an SDcard-like) interface.
It was actually quite simple to figure what the problem was from the error messages.
As I said above, you'll most probably have to replace your microSD card. But, to rule out bad electrical connections being the problem, it wouldn't hurt to clean the contacts on both the microSD card and inside the microSD card slot on the gTablet with some rubbing alcohol. See if you can get your data from the card after that.
Click to expand...
Click to collapse
I will definitely give both a good cleaning just to make sure. There was no info on that sd card, and it had been working fine with it in there up until we had mistyped the wifi password. That's when the problem started. But still working fine after 24 hours. Thanks again for the help.
gargator said:
There was no info on that sd card, and it had been working fine with it in there up until we had mistyped the wifi password. That's when the problem started.
Click to expand...
Click to collapse
A wrong WiFi password didn't cause your current WiFi/SD card problem. There are 2 reasons for saying this:
1. Doing any one of Format /data, wipe data/factory reset, or Partition internal SD card in CWM would've erased your WiFi password. And, you've stated that you have done more than one of those operations in attempting to fix your problem. So, unless you typed in the wrong password each time, a wrong password is not the cause.
2. In any case, the kernel messages clearly show that it's failed to initialize the WiFi hardware, so a right or wrong password doesn't matter.
BTW, you haven't got me that follow-up dmesg output I wanted.