Ok, in this thread I will describe one problem that I have faced with my Iconia and that was also reported by one other user on a forum.
Basically, Iconia uses Atmel mxt1386 touchscreen controller. The same controller is used in Asus EEE Transformer and Motorola Xoom and even Samsung Galaxy Tab 10.1. So far, there are a lot of reports of EEE Transformer's and Xoom's touchscreens suddenly stopping working and starting working after a full battery discharge.
One day after a reboot my Iconia stopped booting - it keeped hanging on the Acer logo and when I tried entering recovery it was hanging at "booting recovery kernel image". However, that only happened with Acer kernels. With my own kernel, ported from EEE Transformer, the tablet could boot. I have recompiled the acer kernel with framebuffer console and found out it got stuck at the touchscreen interrupt handler while EEE's driver just printed an error and stopped working.. Basically, the response I got from from the touchscreen was [1, 0x80, 0, 0, 0, 0, 0, 0]. And it was not detected with i2cdetect
At first, I thought my touchscreen cable was damaged. I have disassembled the tablet and tried twisting the cable to see if it gives any result. My result was that if I disconnect and reconnect the cable, an interrupt comes. Btw, the cable has sharp 'teeth' and you can crimp it pretty much like ethernet.
Ok, so then I added some printks to the driver. Turns out, when some data coming from the touchscreen was incorrect, the driver hanged (deadlocked) because the semaphore was pushed down two times and never upped. So, I have commented out semaphores and bingo - it continued booting. Although there were a lot of warn_slowpath errors and CRC error, it reported correct coordinates. I flashed Acer's kernel after it and it booted fine. Looks like a proper init by Acer driver reset the controller.
The archive in the link contains tegra i2c driver from the chromium tree (in case it finds i2c errors like nak, it retries the transmission several times) and the touchscreen driver. You need to comment out "#define USE_SEMA" to disable semaphores and build the kernel with it in case you encounter the problem..
http://www.mediafire.com/?jt6b19nr7rsy70s
I do not have another 'brick' to test if my solution works in all cases but I'm just leaving the stuff here in case anyone faces the trouble. To flash when your tablet is not booting you'll probably some help from sc2k..
What's the moral of the story? The moral is that as touchscreen is not used in recovery, it may be a good idea to add the 'hacked and buggy' driver to the recovery kernel to allow to recover the device by just booting recovery in case anyone faces the problem.. Of course it's better to fix the driver properly or even use the driver from mainline linux and patch it.
EDIT 29-oct-2011:
here is a link to the cwm recovery image with the 'hacked' driver. Boots just fine.
http://www.mediafire.com/?39jk1j15wkpr57o
So just to clarify this is a software/recovery problem not a hardware problem?
This is a combined problem. It is a hardware problem as the touchscreen stops getting recognized by i2cdetect, probably due to firmware bugs.. It is a software problem because the driver behaves incorrectly when the hardware fails.
Ok, I will post the reply from sc2k who investigated the issue a bit. Let's keep it here for reference. I think it will be nice to patch the mainline driver (from chromium or mainline linux) and use it instead of acer's driver but I won't probably do it unless I hit the issue again or make some progress with my chromium kernel
sc2k said:
Ok.. I finally understand the issue:
Your tochscreen always responded with [1, 0x80, 0, 0, 0, 0, 0, 0]
buffer[1].bit7 seems to be some kind of "message incomplete" bit. As this is always transmitted, the worker thread never releases the semaphore which causes the ATMEL_Initial to stop at ATMEL_SyncWithThreadToReadMsg.
After you disabled the semaphore, ATMEL_Initial continues. ConfigError is probably 0, so next function to be called will be ATMEL_CheckConfig.
This function first calls ATMEL_SendCMDgetCRC. As semaphores are disabled, this will probably not be able to receive the checksum (due to timing) so that ConfigChecksumError=1.
If ConfigChecksumError==1, ATMEL_CheckConfig will call ATMEL_WriteConfig and ATMEL_Backup that will probably be successful and thus fixes the configuration issue. Even if it does not complete succesfully, the whole recovery process is repeated until all conditions are satisfied.
Conclusion:
- Somehow the configuration in your touchscreen controller got messed up.
- Removing the semaphores triggered ATMEL_WriteConfig + ATMEL_Backup which probably fixed the issue.
I believe, a good fix would be to add a check "if (counts > 20) { up(&mxt->sema); goto fail; }" or similar to mxt_worker for irq_type == ATMEL_ReadResponseMsg_Noaddress. This would prevent these endless interrupt loop and allow the driver to fix the configuration.
Really nice bug that you have found in this driver
Click to expand...
Click to collapse
Link to cwm recovery image invalid
Hi sp3dev,
sorry to ask but could you pls reupload your cwm recovery image? Mediafire says the file is not available any more.
I am not an expert in ROMs and I know nothing about cooking them or kernels. But I think I am having a problem similar to that described in your thread: after a sw update the touchscreen became unsensitive. Shutdown, reset, factory reset do not solve the problem. When I flash a new ROM to try and "reset" the screen controller, I get stuck at the "ACER" logo after flashing with CWM and rebooting the system. If I shut down and restart again, the machine starts but the touchscreen is still unresponsive. Luckily enough, I can use a USB mouse to interact with the device.
I am currently running HC 3.1 (stock), rooted. I took a full nandroid backup with CWM. Do you think it is safe to flash your recovery with the modified touchscreen driver (that is, if you are kind enough to re-upload it for me...)?
Thanks a lot for any advice you can provide.
Best, Andrea
I see that thor2002ro has seen this thread, but will we see the driver implemented in the next CWM release?
If it can help people recover from a known brick and if the stack does not introduce problems then I hope that we see something, at least a recovery instruction for the touchscreen added to CWM or the whole stack. aferall this could be something that ends up happening to alot of us :S
I had this problem with my Galaxy Tab and tried the fixes mentioned but it just didn't work for me. I have, however, figured out what's really going wrong.
I always had this failure showing up in dmesg:
[ 1.707677] tegra-i2c tegra-i2c.1: I2c error status 0x00000008
[ 1.707913] tegra-i2c tegra-i2c.1: no acknowledge from address 0x4c
[ 1.708080] tegra-i2c tegra-i2c.1: Packet status 0x00010009
[ 1.709363] Warning: To wake up touch-ic in deep sleep, retry i2c communication!
[ 1.748037] tegra-i2c tegra-i2c.1: I2c error status 0x00000008
[ 1.748355] tegra-i2c tegra-i2c.1: no acknowledge from address 0x4c
[ 1.748523] tegra-i2c tegra-i2c.1: Packet status 0x00010009
[ 1.749788] sec_touch 1-004c: Failure accessing maXTouch device
So, it can't read from the touchscreen controller at address 0x4c. The fix mentioned in this thread was to re-write the configuration, with the assumption that the device was somehow wedged. That doesn't work either, since you can't write to 0x4c - same lack of acknowledgement.
I tried adding a reset. No change. Disconnected the battery overnight. Also no change.
Then, I realized what's going on. The MXT1386 has a "Firmware Update" mode. When you put it into update mode, the device address changes from 0x4c to 0x26! Once it gets into that mode, it doesn't respond to the original address. Since I don't have the docs for the device, I just called the driver function that updates the firmware. Once that process is complete and the chip reset, it reverts to its original address. At that point (after a final reboot), all is well.
I have a replacement kernel that you can install and boot which re-enables the touchpad. I'd suggest making a nandroid backup first, installing my kernel, then restoring the nandroid once it's fixed.
http://www.rickmurphy.net/mxt1386_fixer.zip. While this is a p4wifi (Gtab 10.1 Wifi-only) it'll probably fix the problem on a 3G tablet as well as long as you restore the correct kernel once it's done..
Whew. It's good to have the toy back working.
k1mu said:
I had this problem with my Galaxy Tab and tried the fixes mentioned but it just didn't work for me. I have, however, figured out what's really going wrong.
I always had this failure showing up in dmesg:
[ 1.707677] tegra-i2c tegra-i2c.1: I2c error status 0x00000008
[ 1.707913] tegra-i2c tegra-i2c.1: no acknowledge from address 0x4c
[ 1.708080] tegra-i2c tegra-i2c.1: Packet status 0x00010009
[ 1.709363] Warning: To wake up touch-ic in deep sleep, retry i2c communication!
[ 1.748037] tegra-i2c tegra-i2c.1: I2c error status 0x00000008
[ 1.748355] tegra-i2c tegra-i2c.1: no acknowledge from address 0x4c
[ 1.748523] tegra-i2c tegra-i2c.1: Packet status 0x00010009
[ 1.749788] sec_touch 1-004c: Failure accessing maXTouch device
So, it can't read from the touchscreen controller at address 0x4c. The fix mentioned in this thread was to re-write the configuration, with the assumption that the device was somehow wedged. That doesn't work either, since you can't write to 0x4c - same lack of acknowledgement.
I tried adding a reset. No change. Disconnected the battery overnight. Also no change.
Then, I realized what's going on. The MXT1386 has a "Firmware Update" mode. When you put it into update mode, the device address changes from 0x4c to 0x26! Once it gets into that mode, it doesn't respond to the original address. Since I don't have the docs for the device, I just called the driver function that updates the firmware. Once that process is complete and the chip reset, it reverts to its original address. At that point (after a final reboot), all is well.
I have a replacement kernel that you can install and boot which re-enables the touchpad. I'd suggest making a nandroid backup first, installing my kernel, then restoring the nandroid once it's fixed.
http://www.rickmurphy.net/mxt1386_fixer.zip. While this is a p4wifi (Gtab 10.1 Wifi-only) it'll probably fix the problem on a 3G tablet as well as long as you restore the correct kernel once it's done..
Whew. It's good to have the toy back working.
Click to expand...
Click to collapse
Though I don't have this problem, and hope never to, it is a scary scenario. Thanks for investing your time to come up with a fix for ppl who have this problem.
Sent from my GT-P7510 using xda app-developers app
OTAw said:
Though I don't have this problem, and hope never to, it is a scary scenario. Thanks for investing your time to come up with a fix for ppl who have this problem.
Click to expand...
Click to collapse
Thanks. I've also sent a patch to the person who I thing maintains the driver. If they'll accept the fix, it'll automatically correct this problem regardless of the type of device being used. That'd be a good thing.
I have the common problem with my Acer Iconia A500.
The tablet's touchscreen suddenly stopping working. And didn't start working after reset, shutdown, deattaching the battery, or any firmware upgrades/downgrades.
Custom bootloaders and restores also didn't help.
It is starting working only when I shutdown the tablet and don't use it for a while.
When I turn on the tablet after 2-3 hours, the touchscreen works. But after 10-15 minutes of usage(or even idle), touchscreen stop working again.
I tried many ways to solve this problem, but nothing works for me.
When I tryed to figure out this issue, I found only a few topics in the internet, but all of them was leading to this thread.
So, tell me please, is there any workaround to this touchscreen problem?
I suggest, this is the hardware problem. But if there is any software fix, it would be good.
DIZAZTER said:
I have the common problem with my Acer Iconia A500.
The tablet's touchscreen suddenly stopping working. And didn't start working after reset, shutdown, deattaching the battery, or any firmware upgrades/downgrades.
Custom bootloaders and restores also didn't help.
It is starting working only when I shutdown the tablet and don't use it for a while.
When I turn on the tablet after 2-3 hours, the touchscreen works. But after 10-15 minutes of usage(or even idle), touchscreen stop working again.
I tried many ways to solve this problem, but nothing works for me.
When I tryed to figure out this issue, I found only a few topics in the internet, but all of them was leading to this thread.
So, tell me please, is there any workaround to this touchscreen problem?
I suggest, this is the hardware problem. But if there is any software fix, it would be good.
Click to expand...
Click to collapse
Well, if you have done a rollback using TD's V4 rollback tool, and the problem still persists, then it's likely a hardware issue.
If it were software, the TS would either work, or it wouldn't. The fact there's a time limit involved, indicates some component heating up and causing the issue.
I would suggest, if you are no longer under warranty, to pop off the cover, and start checking connections. More than likely a connection is failing. (cold expands, heat contracts). Might explain why it works when it's cool. (this is why we put old HDD's in the freezer, sounds strange, but can't deny physics)
You can google for 500 breakdown videos. Plenty of them out there.
As a test in the temp theory, just play with the tab till it fails. Toss it in the fridge for 15 minutes or so. If it works, then it's mechanical.
I'd bet on the connectors. Then check the board with a magnifying glass.
MD
Moscow Desire said:
Well, if you have done a rollback using TD's V4 rollback tool, and the problem still persists, then it's likely a hardware issue.
If it were software, the TS would either work, or it wouldn't. The fact there's a time limit involved, indicates some component heating up and causing the issue.
I would suggest, if you are no longer under warranty, to pop off the cover, and start checking connections. More than likely a connection is failing. (cold expands, heat contracts). Might explain why it works when it's cool. (this is why we put old HDD's in the freezer, sounds strange, but can't deny physics)
You can google for 500 breakdown videos. Plenty of them out there.
As a test in the temp theory, just play with the tab till it fails. Toss it in the fridge for 15 minutes or so. If it works, then it's mechanical.
I'd bet on the connectors. Then check the board with a magnifying glass.
MD
Click to expand...
Click to collapse
You're right about the temp.
Actually, I put the tablet in the fridge even before I saw you reply.
After that procedure, touchscreen works fine for a while. And after freezing it works much longer period. I guess, it works just before getting warm.
I wanted to mention about the temperature dependence, but you did it first.
My warranty is expired. So I'm already has disassembled and taken the tablet apart. But I saw nothing noticeably wrong there.
I guess, there is some kind of connection failure, but it's microscopically small. Or it's situated inside of a board or a chip.
Anyway, thanks a lot.
At least I figured out that this is only hardware issue and there is no way to fix it with software patch.
Moscow Desire said:
If it were software, the TS would either work, or it wouldn't. The fact there's a time limit involved, indicates some component heating up and causing the issue.
..
I'd bet on the connectors. Then check the board with a magnifying glass.
Click to expand...
Click to collapse
I agree. Your problem has nothing in common with the issue that was causing my touchscreen to not work. That was a software problem with a reliable software fix.
I have seen a Galaxy Tab with a flaky touchscreen, but when I took it apart to look at what was wrong I found that the connector for the touchscreen had been ripped completely off the motherboard. The induhvidual responsible tried to fix it by taping the touchscreen connector to the motherboard! Needless to say, that wasn't a very reliable fix. :laugh:
I've pulled the kernel that had my patch off of my web site because it's only usable on the P7510 (WiFi) device and caused a 3G tablet to hang.
Could someone please explain what went wrong?
I use a acer a700 and get everytime i make display on such errors:
mXT1386E: mxt_late_resume
<4>[ 1641.027524] tegra-i2c tegra-i2c.1: I2c error status 0x00000008
<4>[ 1641.027938] tegra-i2c tegra-i2c.1: no acknowledge from address 0x4c
<4>[ 1641.028178] tegra-i2c tegra-i2c.1: Packet status 0x00010009
<4>[ 1641.045244] tegra-i2c tegra-i2c.1: I2c error status 0x00000008
<4>[ 1641.045398] tegra-i2c tegra-i2c.1: no acknowledge from address 0x4c
<4>[ 1641.045670] tegra-i2c tegra-i2c.1: Packet status 0x00010009
<4>[ 1641.069140] mXT1386E i2c write 3 time
<4>[ 1641.069539] mXT1386E: ATMEL_Resume OK!
Any idea?
Why?
On boot, dmesg write this:
mXT1386E: reenter_count: 0
mXT1386E: Config has errors
mXT1386E: The status is 0x90
mXT1386E: reenter_count: 1
mXT1386E: Config status is ready
How can we fix it?
Please devs!Help us!!!
djsven said:
Could someone please explain what went wrong?
I use a acer a700 and get everytime i make display on such errors:
mXT1386E: mxt_late_resume
<4>[ 1641.027524] tegra-i2c tegra-i2c.1: I2c error status 0x00000008
<4>[ 1641.027938] tegra-i2c tegra-i2c.1: no acknowledge from address 0x4c
<4>[ 1641.028178] tegra-i2c tegra-i2c.1: Packet status 0x00010009
<4>[ 1641.045244] tegra-i2c tegra-i2c.1: I2c error status 0x00000008
<4>[ 1641.045398] tegra-i2c tegra-i2c.1: no acknowledge from address 0x4c
<4>[ 1641.045670] tegra-i2c tegra-i2c.1: Packet status 0x00010009
<4>[ 1641.069140] mXT1386E i2c write 3 time
<4>[ 1641.069539] mXT1386E: ATMEL_Resume OK!
Any idea?
Why?
On boot, dmesg write this:
mXT1386E: reenter_count: 0
mXT1386E: Config has errors
mXT1386E: The status is 0x90
mXT1386E: reenter_count: 1
mXT1386E: Config status is ready
How can we fix it?
Please devs!Help us!!!
Click to expand...
Click to collapse
That "no acknowledge from address 0x4c" means that your touchscreen chip is not responding. It's possible that it's just dead, or possible that it's stuck in firmware update mode (in update mode, the address changes to 0x26). If you can point me to kernel source for your A700, I can modify it try to recover the touchscreen. (Of course, I'm assuming that it's just dead and that the touchscreen never works. If it works some of the time but fails later, it's probably just a hardware problem.)
k1mu said:
That "no acknowledge from address 0x4c" means that your touchscreen chip is not responding. It's possible that it's just dead, or possible that it's stuck in firmware update mode (in update mode, the address changes to 0x26). If you can point me to kernel source for your A700, I can modify it try to recover the touchscreen. (Of course, I'm assuming that it's just dead and that the touchscreen never works. If it works some of the time but fails later, it's probably just a hardware problem.)
Click to expand...
Click to collapse
Hi @k1mu got a question regarding this discussion. Would there also be benefits from this fix if it's only a unresponsiveness in runtime? I assume also djsven has it within runtime and the ts recovers itself... what I get from this thread is that it's regarded to the tab being unrecoverably stuck on firmware update mode? If not and it could fix hangs for some seconds in runtime it would be awesome if you could make a patch for this driver or just point me to a diff...
Thanks in advance
Elibl said:
Hi @k1mu got a question regarding this discussion. Would there also be benefits from this fix if it's only a unresponsiveness in runtime? I assume also djsven has it within runtime and the ts recovers itself... what I get from this thread is that it's regarded to the tab being unrecoverably stuck on firmware update mode? If not and it could fix hangs for some seconds in runtime it would be awesome if you could make a patch for this driver or just point me to a diff...
Thanks in advance
Click to expand...
Click to collapse
If it's just slow to respond, then the touchscreen is basically working and isn't going to be helped by this fix.
That (slow, jerky response to screen input) is caused by CPU hogging processes keeping the tablet too busy, or too many applications running at once, keeping the OS busy shuffling memory around (that's called thrashing).
k1mu said:
If it's just slow to respond, then the touchscreen is basically working and isn't going to be helped by this fix.
That (slow, jerky response to screen input) is caused by CPU hogging processes keeping the tablet too busy, or too many applications running at once, keeping the OS busy shuffling memory around (that's called thrashing).
Click to expand...
Click to collapse
Sure that's only system hangs... I ment does your fix help for input lags/death regarding 0x4c address/firmware update mode... If you show me the diff I could just test it... Would be highly appreciated
Elibl said:
Sure that's only system hangs... I ment does your fix help for input lags/death regarding 0x4c address/firmware update mode... If you show me the diff I could just test it... Would be highly appreciated
Click to expand...
Click to collapse
No, the system doesn't hang, it works just fine if you plug in a keyboard.
Here's the diff:
Code:
diff -c drivers/input/touchscreen/orig/atmel_mxt1386.c drivers/input/touchscreen/atmel_mxt1386.c
*** drivers/input/touchscreen/orig/atmel_mxt1386.c 2012-10-10 08:11:10.543325982 -0400
--- drivers/input/touchscreen/atmel_mxt1386.c 2012-10-10 08:35:30.545044039 -0400
***************
*** 22,27 ****
--- 22,29 ----
* Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
*/
+ #define FIX_CHIP_HANG
+
#define DEBUG_INFO 1
#define DEBUG_VERBOSE 2
#define DEBUG_MESSAGES 5
***************
*** 2539,2544 ****
--- 2541,2550 ----
/* Initialization of driver */
/******************************************************************************/
+ #ifdef FIX_CHIP_HANG
+ extern int mxt_do_firmware_load(struct mxt_data *mxt, const char *fn);
+ #endif
+
static int __devinit mxt_identify(struct i2c_client *client,
struct mxt_data *mxt)
{
***************
*** 2559,2564 ****
--- 2565,2585 ----
msleep(30);
goto retry_i2c;
}
+ #ifdef FIX_CHIP_HANG
+ /* If we tried twice and no response, maybe it's in firmware
+ * load mode. Try to upload firmware.
+ */
+ if (mxt->read_fail_counter == 2) {
+ printk(KERN_DEBUG "Trying firmware reload.");
+ mxt->last_read_addr = -1;
+
+ mxt_do_firmware_load(mxt, MXT1386_FIRMWARE);
+
+ reset_chip(mxt, RESET_TO_NORMAL);
+ msleep(300);
+ goto retry_i2c;
+ }
+ #endif
dev_err(&client->dev, "Failure accessing maXTouch device\n");
return -EIO;
}
diff -c drivers/input/touchscreen/orig/atmel_mxt1386_cfg.c drivers/input/touchscreen/atmel_mxt1386_cfg.c
*** drivers/input/touchscreen/orig/atmel_mxt1386_cfg.c 2012-10-10 08:12:43.773952501 -0400
--- drivers/input/touchscreen/atmel_mxt1386_cfg.c 2012-10-10 08:36:55.704576439 -0400
***************
*** 408,417 ****
return 0;
}
- int mxt_load_firmware(struct device *dev, const char *fn)
- {
- struct mxt_data *mxt = dev_get_drvdata(dev);
unsigned int frame_size;
unsigned int pos = 0;
unsigned int retry;
--- 408,416 ----
return 0;
}
+ int mxt_do_firmware_load(struct mxt_data *mxt, const char *fn)
+ {
unsigned int frame_size;
unsigned int pos = 0;
unsigned int retry;
***************
*** 518,520 ****
--- 517,526 ----
return ret;
}
+ int mxt_load_firmware(struct device *dev, const char *fn)
+ {
+ struct mxt_data *mxt = dev_get_drvdata(dev);
+
+ return mxt_do_firmware_load(mxt, fn);
+ }
+
Hello all Forum Users.
Unfortunately I'm not yet allowed to post on Android Development, so I have to write here.
I would be gratuful if someone could post a link there or permit me to write there:
http://forum.xda-developers.com/showthread.php?t=2180085
I'm quite experienced FreeBSD kernel developer and I would like to get involved into pinkflozd CM kernel development.
I'm almost newbe to Linux kernel but I think there are some problems with WiFi on e610 devices.
I have the latest CM 10 with pinkflozd CM kernel v0.70.
Everything seems to work OK except from the Wifi.
When the WiFi is off, "lsmod" shows only "frandom" module - it's OK.
When I turn the WiFi on, "lsmod" shows also "librasdioif" and "wlan" modules loaded
but the WiFi is unable to turn on and the modules are unloaded soon.
"dmesg" show some info (not including everything):
- wlan0: link is not ready (many times)
- init: untracked pid xxxx exited
- wlan: unloading driver v0.2.2.542
- <many other errors>
- libra sdio remove : Module removed.
I also tried "l5_wifi_fix" - it didn't help.
I can send more debug info if required. I am not familiar with the Android "log" subsystem.
I have a problem with the 3G Data Connection. The WiFi is working fine, sorry I can't help about it. I just didn't know where to ask my question. How can i fix data connectivity? before flashing CM10, on original ICS it was working just fine. I also tried flashing only the ROM without the pinkflozd kernel, still no connectivity. In settings its set on "allowed" or whatever it says. Please help. :/
l5_wifi_fix must be started from PC, there is fix.cmd, of course phone must be connected by USB
Andro995 said:
I have a problem with the 3G Data Connection. The WiFi is working fine, sorry I can't help about it. I just didn't know where to ask my question. How can i fix data connectivity? before flashing CM10, on original ICS it was working just fine. I also tried flashing only the ROM without the pinkflozd kernel, still no connectivity. In settings its set on "allowed" or whatever it says. Please help. :/
Click to expand...
Click to collapse
I'm afraid I can't help. Everyone says that 3G Data Connection starts working after the second reboot.
Try reboot and then run "dmesg" from the terminal. Scroll it and try to find something which might be useful to solve the problem.
twisted_tits said:
l5_wifi_fix must be started from PC, there is fix.cmd, of course phone must be connected by USB
Click to expand...
Click to collapse
Thanks, I know it. I've rewritten the script so it could be executed from Linux.
Some dmesg output
I have something like that when booting PinkFlozd kernel:
<4>[ 23.496161] ------------[ cut here ]------------
<4>[ 23.496248] WARNING: at arch/arm/mach-msm/clock.c:196 clk_disable+0x138/0x148()
<4>[ 23.496274] ebi_grp_3d_clk is unbalanced
<4>[ 23.496288] Modules linked in: wlan(P) librasdioif frandom
<4>[ 23.496351] [<c00467c4>] (unwind_backtrace+0x0/0x138) from [<c00d5e00>] (warn_slowpath_common.constprop.7+0x4c/0xd0)
<4>[ 23.496391] [<c00d5e00>] (warn_slowpath_common.constprop.7+0x4c/0xd0) from [<c00d5ea8>] (warn_slowpath_fmt+0x24/0x34)
<4>[ 23.496428] [<c00d5ea8>] (warn_slowpath_fmt+0x24/0x34) from [<c00569c4>] (clk_disable+0x138/0x148)
<4>[ 23.496466] [<c00569c4>] (clk_disable+0x138/0x148) from [<c046dd9c>] (_sleep+0x108/0x3ec)
<4>[ 23.496499] [<c046dd9c>] (_sleep+0x108/0x3ec) from [<c046eadc>] (kgsl_idle_check+0x154/0x1c8)
<4>[ 23.496538] [<c046eadc>] (kgsl_idle_check+0x154/0x1c8) from [<c00f0d44>] (process_one_work+0x1ec/0x354)
<4>[ 23.496573] [<c00f0d44>] (process_one_work+0x1ec/0x354) from [<c00f10a0>] (worker_thread+0x1c8/0x308)
<4>[ 23.496608] [<c00f10a0>] (worker_thread+0x1c8/0x308) from [<c00f6b0c>] (kthread+0x84/0x8c)
<4>[ 23.496646] [<c00f6b0c>] (kthread+0x84/0x8c) from [<c0040e9c>] (kernel_thread_exit+0x0/0x8)
<4>[ 23.496673] ---[ end trace a139245ee3e508ee ]---
It might be the reason why WiFi doesn't work.
kkarpowi said:
Thanks, I know it. I've rewritten the script so it could be executed from Linux.
Click to expand...
Click to collapse
BTW - Running l5_wifi_fix results are:
modprobe: 'librasdioif.ko': invalid module format
modprobe: 'wlan.ko': invalid module format
WiFi working
WiFi is working after a total wipe and CM10-20130414 installed.
I don't know what was wrong or if anything was fixed. Really don't know.
PinkFlozd kernel and gapps also installed and still OK.
I hope that everything else is working fine - checking...
I recommend to update your stock firmware to V20A_Rooted.kdz. Its very smooth and runs my Temple run 2 whith no lags on 800mhz.
Link for the kdz update:
http://forum.xda-developers.com/showthread.php?t=2230679
Link for the 4.1.2 Clean rom v2:
http://forum.xda-developers.com/showthread.php?t=2232123
jannick63 said:
I recommend to update your stock firmware to V20A_Rooted.kdz. Its very smooth and runs my Temple run 2 whith no lags on 800mhz.
Link for the kdz update:
http://forum.xda-developers.com/showthread.php?t=2230679
Link for the 4.1.2 Clean rom v2:
http://forum.xda-developers.com/showthread.php?t=2232123
Click to expand...
Click to collapse
That's what I did yesterday. And AFTER that (and of course after reinstalling the latest CM10 from scratch) WiFi started working. Strange, isn't it?
my sim card is not working
Andro995 said:
I have a problem with the 3G Data Connection. The WiFi is working fine, sorry I can't help about it. I just didn't know where to ask my question. How can i fix data connectivity? before flashing CM10, on original ICS it was working just fine. I also tried flashing only the ROM without the pinkflozd kernel, still no connectivity. In settings its set on "allowed" or whatever it says. Please help. :/
Click to expand...
Click to collapse
my sim card is not working
you should try flashing baseband,specify which base band you are in now
Sent from my LG-P700 using xda app-developers app
OP, if you want to help pm pinkflozd. And I think you need to post at least 10 times to be able to post on development forum.
So just keep posting on this thread
on my p705g - vanir rom
Hi Guys.
Im not expecting CyanogenMod nightlies to be bug-free, but it seems everyone else using them is reporting working WIFI.
I have tried all of them, and always get the same error... perhaps (likely) im doing somthing stupid.
The Symptom:
Enable wifi the usual way, tragging the wifi toggle switch to "on",
the text "Turning on wi-fi" appears, tobble switch jumps back to off.
The following appears in logcat.
Code:
01-05 19:09:48.273: E/WifiStateMachine(673): Failed to load driver!
01-05 19:09:48.293: E/WifiStateMachine(673): DriverFailedState
The following appears in dmesg.
Code:
<4>[ 741.598999] DHD: dongle ram size is set to 786432(orig 786432) at 0x180000
<4>[ 741.599121] CHIP VER = [0x1]
<4>[ 741.599121] ----- CHIP bcm4335_B0 -----
<6>[ 741.600463] CFG80211-INFO2) wl_event_handler : tsk Enter, tsk = 0xdacc4da0
<4>[ 741.600494] wl_create_event_handler thr:1386 created
<4>[ 741.606719] p2p0: P2P Interface Registered
<4>[ 741.606811] dhd_attach thr:1387 created
<4>[ 741.606903] dhd_attach thr:1388 created
<4>[ 741.606994] dhd_attach thr:1389 created
<4>[ 741.607086] dhd_attach thr:138a created
<4>[ 741.607269] dhd_bus_start: nvram_type = [txt_murata]
<4>[ 741.680633] _dhdsdio_download_firmware: dongle nvram file download failed
<4>[ 741.680664] dhd_bus_start: dhdsdio_probe_download failed. firmware or nvram wrong
<4>[ 741.680694] dhdsdio_probe: dhd_bus_start failed
Everything else is working perfectly.
Model - Samsung Galaxy S4 - JFLTECAN United Kingdom - '3' Network.
It looks like I am missing the firmware?
The current plan of action is to download and flash the stock ROM, find the firlware, re-flash a nightly, and ADB push it into the correct place.
Am I barking up the correct tree ?
This prblem appeared exactly when i flashed the first nightly, so im hoping i havent fried the wifi chip during a flash.
Thanks.
Chris.
UPDATE:
The BCM4335 runs the radio, bluetooth and WIFI... the radio and bluetooth are fine.. im comleely lost
Looks like its not missing firlware files?
Yup.. im lost.
I am having the same issue on my D4, just flashed the latest nightly this morning.
DROID4 using xda app-developers app
Theis81 said:
I am having the same issue on my D4, just flashed the latest nightly this morning.
DROID4 using xda app-developers app
Click to expand...
Click to collapse
With the same dmesg output?
ceedeeess84 said:
With the same dmesg output?
Click to expand...
Click to collapse
Let me check, I went back to stock when I realized I had no wifi. I will likely flash last night's build today as well, will report back on functionality.
i'm having the same issue, however i'm back on stock android now, so i don't have access to the terminal fix.
so how would i go to fixing this please?
Edit:
ADB method :
disable wifi
adb root
adb shell rm /data/.cid.info
enable wifi
No-adb method :
Download a root-enabled file explorer from Play Store (such as ES File Explorer)
Disable wifi
Remove /data/.cid.info
Enable wifi
ceedeeess84 said:
With the same dmesg output?
Click to expand...
Click to collapse
Oddly enough I rebooted into CM just now and both bluetooth and wifi are working, not sure what was up. Sorry I couldn't help here.
Pixelhouse said:
i'm having the same issue, however i'm back on stock android now, so i don't have access to the terminal fix.
so how would i go to fixing this please?
Edit:
ADB method :
disable wifi
adb root
adb shell rm /data/.cid.info
enable wifi
No-adb method :
Download a root-enabled file explorer from Play Store (such as ES File Explorer)
Disable wifi
Remove /data/.cid.info
Enable wifi
Click to expand...
Click to collapse
Wow... That has fixed it !?
The kernel logs about failing to upload firmware seem to have been a massive red-herring.
THANKS!!!
Very Very Odd!
Oh well.. Thanks again!
Hi there everyone.
I appologize for this repetitive post, but I have some questions that I can't find an answer.
I have 4.3 up to the latest. I received my nexus yesterday and it updated automatically to the latest version. After that the device started to randomly reboot.
I tried:
- Factory reset (from menu)
- Factory reset from recovery + wipe cache.
Still does not work. Now I heve 2 more questions :
- Can I flash the factory image without root/coustom recovery ? Is there any probability it will solve my problem ? Will I lose OTA ?
- This is a 16 gb model. I also have a black 8 Gb model that does not have this problem. Can I backup my 8gb nexus and install my recovery on the other 16 gb nexus, with the hope It will fix the problem ?
Thank you very much. It's kind of urgent. I can't return it to google because I bought it on a internet store (white edition no more). :crying:
It is a 4.3 thing. Try flashing 4.2.2 factory image and report back.
Sent from my Nexus 4 using xda app-developers app
What I can't get Is why only some devices are affected ... My 8GB nexus 4 runs pretty smooth.
Later on ... It does the same on 4.2.2. So I think this is a more serious problem.
My brand new black nexus 4 is also rebooting, I was wondering couldn't you just reflash android 4.3 and wipe your existing android 4.3 and see if that helps?
Sent from my Nexus 7 using Tapatalk 4
Ulyan said:
What I can't get Is why only some devices are affected ... My 8GB nexus 4 runs pretty smooth.
Later on ... It does the same on 4.2.2. So I think this is a more serious problem.
Click to expand...
Click to collapse
I tried to set it back to android 4.2.2 and it does the same so I'm going to send mine back to O2 and ask for a replacement.
Sent from my Nexus 7 using Tapatalk 4
Since a week or so, my Nexus 4 reboots randomly every hour as well. I'm on stock 4.3 (JWR66Y) which ran perfectly before. I did try to find the cause/trigger of the problem but had no luck so far.
cat /proc/last_kmsg shows that there was a kernel panic at the end of the output, but I can't find any backtrace. Also my /data/dontpanic folder is empty so I don't know where to look any further.
Code:
[ 1026.690462] PM: suspend exit 2013-09-12 13:27:04.015709352 UTC
[ 1026.690553] suspend: exit suspend, ret = 0 (2013-09-12 13:27:04.015831337 UTC)
[ 1026.690645] suspend: enter suspend
[ 1026.690645] PM: Syncing filesystems...
[ 1026.690920] PM: suspend entry 2013-09-12 13:27:04.016197294 UTC
[ 1026.803997] Freezing user space processes ... (elapsed 0.02 seconds) done.
[ 1026.839310] sync done.
[ 1026.839371] PM: Syncing filesystems...
[ 1026.874835] sync done.
[ 1027.079230] Freezing remaining freezable tasks ... (elapsed 0.02 seconds) done.
[ 1027.101449] Suspending console(s) (use no_console_suspend to debug)
No errors detected
Boot info:
Last boot reason: kernel_panic
Is there another method to get a backtrace of what triggered the kernel panic?
I found a thread on the google product forums where a lot of people are experiencing a similar issue, but no solutions so far.
Any hints on how I can debug this problem any further would be greatly appreciated!
I have the same problem with this, doesn't matter what version of android I install, custom or not.
THe phone is basically unusable now
Hi Folks,
Another "no wifi" s4 here. This is a work colleagues phone that was totally stock. After upgrading to 4.4.2, wifi won't turn on. I've tried pretty much everything I've found on this site with regards to fixing it. The last thing that I hadn't looked at was the /persist folder (MMCBLK0P17). The one on this phone is empty and from what I've read, it should be populated. Could someone with a rooted i9505 post a list of the contents or better still, upload a copy of their /persist folder please?
TIA!
Mark
mjh74 said:
Hi Folks,
Another "no wifi" s4 here. This is a work colleagues phone that was totally stock. After upgrading to 4.4.2, wifi won't turn on. I've tried pretty much everything I've found on this site with regards to fixing it. The last thing that I hadn't looked at was the /persist folder (MMCBLK0P17). The one on this phone is empty and from what I've read, it should be populated. Could someone with a rooted i9505 post a list of the contents or better still, upload a copy of their /persist folder please?
TIA!
Mark
Click to expand...
Click to collapse
So what is everything found on this site with regards to fix it?
/persist folder is also empty on my phone.
mjh74 said:
Hi Folks,
Another "no wifi" s4 here. This is a work colleagues phone that was totally stock. After upgrading to 4.4.2, wifi won't turn on. I've tried pretty much everything I've found on this site with regards to fixing it. The last thing that I hadn't looked at was the /persist folder (MMCBLK0P17). The one on this phone is empty and from what I've read, it should be populated. Could someone with a rooted i9505 post a list of the contents or better still, upload a copy of their /persist folder please?
TIA!
Mark
Click to expand...
Click to collapse
Dial *#1234# and paste here what appears.
AP: I9505XXUGNG8
CP: I9505XXUGNG8
CSC: I9505BTUGNG2
So far I've tried the following:
Flashing the wifi-fix
Re-partitioning before flashing a stock rom
Rooting, Phillz recovery, clear dalvik, factory reset and format for new rom option before flashing various different 4.4.2 UK stock roms.
Editing build.prop and changing "ro.securestorage.support=true" to false.
Removing the back, removing and replacing the antenna wire.
Flashing a CM11 nightly.
Deleting wpa_supplicant.conf
Dmesg shows some interesting stuff.
"<4>[ 1277.591125] ## wifi_remove
<4>[ 1277.591125] wifi_set_power = 0
<4>[ 1277.591156] ####btlock released, cookie: WiFi
<6>[ 1277.591156] ------------------------------------------------
<6>[ 1277.591156] ------------------------------------------------
<6>[ 1277.591156] brcm_wlan_power Enter: power off
<6>[ 1277.591186] barcode_emul_ice4: ice_gpiox_set : num = 3 , val = 0
<7>[ 1277.592590] usb 1-1: usb wakeup-resume
<7>[ 1277.592651] usb 1-1: finish resume
<7>[ 1277.599456] hub 1-0:1.0: resume on port 1, status 0
<7>[ 1277.599487] hub 1-0:1.0: port 1, status 0503, change 0004, 480 Mb/s
<6>[ 1277.727569] [email protected] 42
<6>[ 1277.732635] set_freq_limit: 0x1 -1, min 384000, max 1350000
<4>[ 1277.822662] wifi_set_carddetect = 0
<4>[ 1277.822692] brcm_wifi_status:298 status 0
<6>[ 1277.822692] mmc1: Slot status change detected (1 -> 0)
<4>[ 1277.823638]
<4>[ 1277.823638] failed to power up wifi chip, max retry reached, exits **"
As I'm typing this, the phone has a stock rom and isn't rooted. I've just rooted again with CF-ROOT and Odin, rebooted the phone and wifi enabled instantly, something I've not seen before! It was the first boot and SuperSU wanted to update and reboot. After the reboot, wifi will no longer come on again.
I See you have the same error as I'm having:
Code:
<6>[ 1277.822692] mmc1: Slot status change detected (1 -> 0)
Can you check dmesg for mmc1 CRC errors and post output here?
ajax505 said:
I See you have the same error as I'm having:
Code:
<6>[ 1277.822692] mmc1: Slot status change detected (1 -> 0)
Can you check dmesg for mmc1 CRC errors and post output here?
Click to expand...
Click to collapse
Here you go.
mjh74 said:
Here you go.
Click to expand...
Click to collapse
So after pretty much giving up and weeks of flashing and faffing around. I managed to get wifi enabled. I've no idea how but I went from stock rom XXUGNG2, rooted with CF-AUTO-ROOT, Phillz recovery installed and a Cyanogen nightly and no wifi. Flashed XXUGNG2 back to the phone and wifi sprung into life! I then flashed XXUGNG8 and wifi still worked! I then performed a factory reset from Backup & Reset and wifi hasn't worked again since!?!?
So I'm not so convinced now that it's a hardware issue as I first thought.....
Lucky you I tried every possible solution. The interesting thing is that if I flash stock I can see Wifi mac, toggle button is "alive" but wifi won't turn on. If I flash cyanogen, wifi mac is not available and the wifi button is gray saying "turning wifi on" like forever.
ajax505 said:
Lucky you I tried every possible solution. The interesting thing is that if I flash stock I can see Wifi mac, toggle button is "alive" but wifi won't turn on. If I flash cyanogen, wifi mac is not available and the wifi button is gray saying "turning wifi on" like forever.
Click to expand...
Click to collapse
Like you, I'm back at exactly the same place. Cyanogen won't even let me turn wifi on now, the button is grayed out and says "turning wifi on". Stock roms show a pale green wifi signal icon until it turns gray again and fails. Arghhh how did I get it working briefly?!
mjh74 said:
So after pretty much giving up and weeks of flashing and faffing around. I managed to get wifi enabled. I've no idea how but I went from stock rom XXUGNG2, rooted with CF-AUTO-ROOT, Phillz recovery installed and a Cyanogen nightly and no wifi. Flashed XXUGNG2 back to the phone and wifi sprung into life! I then flashed XXUGNG8 and wifi still worked! I then performed a factory reset from Backup & Reset and wifi hasn't worked again since!?!?
So I'm not so convinced now that it's a hardware issue as I first thought.....
Click to expand...
Click to collapse
mjh74 said:
Like you, I'm back at exactly the same place. Cyanogen won't even let me turn wifi on now, the button is grayed out and says "turning wifi on". Stock roms show a pale green wifi signal icon until it turns gray again and fails. Arghhh how did I get it working briefly?!
Click to expand...
Click to collapse
When people learn that means "nightly" with CM?