Related
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);
+ }
+
You read the title correctly.
HDMwIn now supports HDMI out on gingersense. Congrats to TeamWin for this fine release. I have been waiting for HDMI out support for a while.
agrabren said:
The Alpha kernel is now available from Kernel Manager! Give it a test drive!
(Sense only)
We'll be porting the whole re-architecture over to CM7. Not gonna leave AOSP out to dry!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=17068475&postcount=1850
This new kernel is a complete rewrite of the app. The functionality is now fully automatic and no longer requires a separate app. The team has said they do plan on releasing an App to allow those who wish to tinker with settings to do so, but otherwise, a seperate app is unneeded. Gone are the daemon downloader loops.
More indepth information is available here:
http://www.androidcentral.com/android-central-exclusive-hdmwin-gingerbread-first-look
How long did it take you to perfect HDMwIn for Gingerbread?
I've spent over 100 hours getting all the little details right and all the algorithms working smoothly. I anticipate another 10-20 hours until all the wrinkles are fixed.
So HDMI just outputs on its own? The user doesn't need to do anything?
Exactly. The user plugs in the HDMI cable, and it just works. The user is welcome to make adjustments via the UI, but there's generally no need. But there will always be someone who is fussy and wants it to lock rotation, change scaling or modify the overscan defaults.
Did there not used to be auto-rotation? And does auto-rotation work for everything? I noticed it worked in both Nova and the YouTube app.
There was a rudimentary version of auto-rotation in old builds, but that required the UI to read the sensors. This consumed massive amounts of battery, and performed poorly. This new method requires no extra power, and offers a smoother experience to the user. Any application which natively handles rotation (either fixed, like Nova, or dynamic, like Messages) will work out-of-the-box. As for YouTube, YouTube isn't mirroring. It uses native HDMI support for Gallery videos and YouTube videos. That was one of the great new features. You no longer need to disable mirroring to use YouTube. It switches automatically.
You mentioned there's now YouTube app support. Is there also support for videos played in the browser app?
Only the YouTube app and Gallery app support HDMI out-of-the-box from HTC. So when those apps run, you'll have different output on your TV from your device. If you're playing video (or anything else) on the device in a player which doesn't natively handle the EVO's HDMI port, you'll get full mirroring. If the app is HDMI-aware, you'll get the app's intended behavior.
Are there any performance enhancements in the new HDMwIn? How are the scrolling speeds compared to the previous version?
We're using the same "Silky Johnson" technology which drove our previous accelerated kernels, so we're seeing the same smooth responsiveness and performance. Because we now do aspect scaling a little more accurately, it's possible the GPU isn't quite as taxed as before, but we haven't felt a noticeable difference. The device no longer has a polling loop running in the background, so that helps battery life and performance as well.
You mentioned there's a custom kernel involved. What kind of features does this kernal support? Are other kernals supported?
I always build our new features directly on top of the HTC kernels. Once we release the kernel and source code, we work with other kernel developers to get our code integrated into their kernels. This kernel has all the latest EDID fixes (for people who would plug in a TV and have the phone immediately crash) as well as the HDMI mirroring.
Click to expand...
Click to collapse
Video Preview available here:
http://www.youtube.com/watch?v=gu7OVC31Nc4&feature=player_embedded
Warning!!
The kernel has been released on Kernel Manager. This is a free app available on Android Market. Before installing this kernel, please nandroid your phone. This is an alpha kernel. There may be instabilities and other issues. Be aware that installing this kernel will override any other custom/stock kernel you may have installed. You will lose the abilities of those kernels (such as overclocking, HAVs, etc.). This requires root. Do NOT use this kernel with an ASOP rom (MIUI, CM7, etc.). An ASOP version is coming according to the devs.
How to install:
Apparently, kernel manager has issues with the HDMwIn kernel, so please flash from recovery manually instead.
- Run Kernel Manager and approve the superuser request.
- Press menu and select 'Advanced Options'. Ensure 'Flash automatically' isn't checked.
- Select Load Kernel List.
- Scroll to the bottom of the list.
- Select PoonSense 2.3.3.
- Press Download + Flash Kernel.
- Using a file manager, navigate to root of SD card. sdcard/kernel-manager/agrabren contains a .zip file callled "2.3.3-1-793-HDMwIn-Sense233-Alpha-signed.zip". That file is also attached to this thread.
- Move that .zip file to the root of your SD
- Reboot into recovery
- Wipe cache and dalvik cache.
- Flash the .zip file.
- Reboot
- Enjoy HDMwIn.
Also, agrabren has updated his kernel due users having issues with blank screens. If you guys are having issues, please use his newest kernel: build 793. That version is now available on Kernel Manager and attached to this thread.
http://forum.xda-developers.com/showpost.php?p=17074174&postcount=1864
Old method of install. Causes Wifi errors and other bugs, use alternative method above.
Code:
[B]How to install:[/B]
- Install Kernel Manager from Market
- Run Kernel Manager and approve the superuser request.
- Press menu and select 'Advanced Options'. Ensure 'Clear Cache' and 'Clear Dalvik Cache' are checked.
- Select Load Kernel List.
- Scroll to the bottom of the list.
- Select PoonSense 2.3.3.
- Press Download+ Flash Kernel.
- After the reboot, enjoy HDMI mirroring. There is no app to start or configure. It just works now. Plug in an HDMI cable and you are good to go.
Excellent! Can't wait to try... of course I just lost my HDMI cable
deleted post I was in the wrong forum.
Is this kernel godmode compliant?
Sent from my PC36100 using Tapatalk
Hi Guys,
I have a simple question, Is this kernel compatible with the Stock Ver on Gingerbread ?
Also is this kernel support Wireless N ?
Thanks
Khilbron said:
Is this kernel godmode compliant?
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Since I didn't hear an answer on this, I downloaded the kernel from Kernel Manager (poonsense 2.3.3) made a backup of Synergy RC2+Godmode. Flash was sucessful, ROM booted with no problems. When I get home in 4 hours I will hook up my HDMI cable and test functionality.
Is anybody having WIFI problems after flashing? I flashed last night, this morning I get "Error" under Settings -> Wireless & Networks -> WiFi (the word Error is right below the word Wi-Fi; attempting to click the checkbox does nothing. It stays unchecked).
Might be a coincidence, as I was also updating my GPS driver last night as well.
mpsantiago said:
Is anybody having WIFI problems after flashing? I flashed last night, this morning I get "Error" under Settings -> Wireless & Networks -> WiFi (the word Error is right below the word Wi-Fi; attempting to click the checkbox does nothing. It stays unchecked).
Might be a coincidence, as I was also updating my GPS driver last night as well.
Click to expand...
Click to collapse
I can confirm this I didn't think to test my WiFi after flashing. I receive the error message as well.
Sent from my PC36100 using Tapatalk
mpsantiago said:
Is anybody having WIFI problems after flashing? I flashed last night, this morning I get "Error" under Settings -> Wireless & Networks -> WiFi (the word Error is right below the word Wi-Fi; attempting to click the checkbox does nothing. It stays unchecked).
Might be a coincidence, as I was also updating my GPS driver last night as well.
Click to expand...
Click to collapse
This will happen if you flash the new kernel through kernel manager. All you have to do is flash the kernel manually and everything *should* work fine.
Go into recovery, clear cache and delvik. Then go to flash file from sd, scroll to the folder called kernel manager, then open the agrabren folder and there will be the flashable zip. Note, this only works if you have already downloaded the file through kernel manager. Otherwise you will have to find the zip file in the dev area. I will include a link soon to the zip.
Find the link here... Second post down (I think)...
http://forum.xda-developers.com/showthread.php?t=987592&page=188
P.S. Always Nandroid Backup prior to any flashing... I am no pro, this is simply the method that worked for me.
I hope this helps, it worked for me the exact same way on all 3 of my EVO's.
Thanks to agrabren and all who contributed, this is one amazing piece of work!! Everything works flawless!
Sent from my S-OFF OG EVO using XDA Premium App
ABBUB said:
This will happen if you flash the new kernel through kernel manager. All you have to do is flash the kernel manually and everything *should* work fine.
Go into recovery, clear cache and delvik. Then go to flash file from sd, scroll to the folder called kernel manager, then open the agrabren folder and there will be the flashable zip. Note, this only works if you have already downloaded the file through kernel manager. Otherwise you will have to find the zip file in the dev area. I will include a link soon to the zip.
Find the link here... Second post down (I think)...
http://forum.xda-developers.com/showthread.php?t=987592&page=188
P.S. Always Nandroid Backup prior to any flashing... I am no pro, this is simply the method that worked for me.
I hope this helps, it worked for me the exact same way on all 3 of my EVO's.
Thanks to agrabren and all who contributed, this is one amazing piece of work!! Everything works flawless!
Sent from my S-OFF OG EVO using XDA Premium App
Click to expand...
Click to collapse
I didnt use Kernel Manager to flash it, I downloaded the kernel, booted to Ra Recovery, backed up my current ROM, then wiped Cache 3x, and Dalvik 3x, then i manually flashed the zip via install zip from SD Card, and my WiFi still errors out. So what you said is irrelevant to the issue. I appreciate your attempt to try and fix it, but the fix is not a fix.
Khilbron said:
I didnt use Kernel Manager to flash it, I downloaded the kernel, booted to Ra Recovery, backed up my current ROM, then wiped Cache 3x, and Dalvik 3x, then i manually flashed the zip via install zip from SD Card, and my WiFi still errors out. So what you said is irrelevant to the issue. I appreciate your attempt to try and fix it, but the fix is not a fix.
Click to expand...
Click to collapse
Try using the newest kernel version attached to this thread. Agrabren fixed some issues and updated the kernel to a new version. Make sure to flash manually and wipe cache and dalvik cache.
I've updated the instructions and attached the newest kernel version to this thread.
MultiDev said:
Try using the newest kernel version attached to this thread. Agrabren fixed some issues and updated the kernel to a new version. Make sure to flash manually and wipe cache and dalvik cache.
I've updated the instructions and attached the newest kernel version to this thread.
Click to expand...
Click to collapse
I downloaded and flashed the kernel at 2:05pm today, the Kernel I flashed was
2.3.3-1-793-HDMwIn-Sense233-Alpha-signed.zip
Which after looking is the kernel you have attached to the OP. So that won't do it. I do believe this kernel is incompatible with Synergy+Godmode. But for the Dev's sake here is my logcat.
08-29 19:35:05.314 D/WifiStatusBarPreference(484): set wifi enable: true
08-29 19:35:05.314 D/WifiService(192): setWifiEnabled =truemAirplaneModeOverwridden =false
08-29 19:35:05.334 D/WifiService(192): setWifiEnabledBlocking:Enable Wifi
08-29 19:35:05.354 D/NetSharing_NSReceiver(1689): onReceive : android.net.wifi.WIFI_STATE_CHANGED
08-29 19:35:05.354 D/NetSharing(1689): wifi enabled change, state = false
08-29 19:35:05.354 I/WifiHW (192): wifi_load_driver enter
08-29 19:35:05.354 I/WifiHW (192): check_driver_loaded
08-29 19:35:05.354 I/WifiHW (192): insmod
08-29 19:35:05.394 D/StatusBarPolicy(484): onReceive , action=android.net.wifi.WIFI_STATE_CHANGED
08-29 19:35:05.434 I/WifiHW (192): wifi_load_driver end error 2
08-29 19:35:05.434 E/WifiService(192): Failed to load Wi-Fi driver.
08-29 19:35:05.454 D/NetSharing_NSReceiver(1689): onReceive : android.net.wifi.WIFI_STATE_CHANGED
08-29 19:35:05.454 D/NetSharing(1689): wifi enabled change, state = false
08-29 19:35:05.474 D/StatusBarPolicy(484): onReceive , action=android.net.wifi.WIFI_STATE_CHANGED
08-29 19:35:53.491 D/WifiStatusBarPreference(484): set wifi enable: true
08-29 19:35:53.491 D/WifiService(192): setWifiEnabled =truemAirplaneModeOverwridden =false
08-29 19:35:53.501 D/WifiService(192): setWifiEnabledBlocking:Enable Wifi
08-29 19:35:53.501 I/WifiHW (192): wifi_load_driver enter
08-29 19:35:53.501 I/WifiHW (192): check_driver_loaded
08-29 19:35:53.501 I/WifiHW (192): insmod
08-29 19:35:53.501 I/WifiHW (192): wifi_load_driver end error 2
08-29 19:35:53.501 E/WifiService(192): Failed to load Wi-Fi driver.
08-29 19:35:53.511 D/NetSharing_NSReceiver(1689): onReceive : android.net.wifi.WIFI_STATE_CHANGED
08-29 19:35:53.511 D/NetSharing(1689): wifi enabled change, state = false
08-29 19:35:53.531 D/StatusBarPolicy(484): onReceive , action=android.net.wifi.WIFI_STATE_CHANGED
08-29 19:35:53.531 D/StatusBarPolicy(484): onReceive , action=android.net.wifi.WIFI_STATE_CHANGED
08-29 19:35:53.541 D/NetSharing_NSReceiver(1689): onReceive : android.net.wifi.WIFI_STATE_CHANGED
08-29 19:35:53.541 D/NetSharing(1689): wifi enabled change, state = false
Ok, reflashing with 2.3.3-1-793-HDMwIn-Sense233-Alpha-signed.zip seems to have solved my issues.
Khilbron said:
I didnt use Kernel Manager to flash it, I downloaded the kernel, booted to Ra Recovery, backed up my current ROM, then wiped Cache 3x, and Dalvik 3x, then i manually flashed the zip via install zip from SD Card, and my WiFi still errors out. So what you said is irrelevant to the issue. I appreciate your attempt to try and fix it, but the fix is not a fix.
Click to expand...
Click to collapse
Not saying who is right or wrong for sure, but my wifi also did not work after flashing this from kernel manager. I wiped from recovery (dalvik and cache), and then flashed the zip from within TWRP, rebooted and everything was fixed. So for me the fix was a fix.
@ABBUB, I thanked you for your fix
madiom said:
Not saying who is right or wrong for sure, but my wifi also did not work after flashing this from kernel manager. I wiped from recovery (dalvik and cache), and then flashed the zip from within TWRP, rebooted and everything was fixed. So for me the fix was a fix.
@ABBUB, I thanked you for your fix
Click to expand...
Click to collapse
Yes but are you using synergy godmode, because that is what I am using if so, then I will temporarily flash twrp and flash the radio for a third time.
Sent from my PC36100 using Tapatalk
Khilbron said:
Yes but are you using synergy godmode, because that is what I am using if so, then I will temporarily flash twrp and flash the radio for a third time.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
I'm assuming you mean kernel when you say radio cause otherwise, you are flashing the wrong thing.
If you are still having wifi issues after flashing the latest kernel, try using the fix from here:
http://forum.xda-developers.com/showthread.php?t=1158629
That will rewrite your broken wifi driver and hopefully fix that issue.
MultiDev said:
I'm assuming you mean kernel when you say radio cause otherwise, you are flashing the wrong thing.
If you are still having wifi issues after flashing the latest kernel, try using the fix from here:
http://forum.xda-developers.com/showthread.php?t=1158629
That will rewrite your broken wifi driver and hopefully fix that issue.
Click to expand...
Click to collapse
I'll give that a shot, I also noticed that it broke 4G as well so I'm going to download it again later could be a bad download and yes I meant kernel.
Sent from my PC36100 using Tapatalk
Khilbron said:
Yes but are you using synergy godmode, because that is what I am using if so, then I will temporarily flash twrp and flash the radio for a third time.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Nope, not using Synergy, I am using MikeG. I thought I read somewhere in the Synergy forum about special flashing instructions for those using "godmode"
Awesome can't wait for this to be merged into a Tiamat kernel!
My replacement HDMI cable arrived just now so I tested it- mirroring works great on MikG 2.45
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!
Hello, on my Nexus 4 on any custom ROMs I am unable to turn on Wifi or Bluetooth. When I move slider, it going to be gray and waiting for few seconds, later going back to 'OFF' position. I tried on Paranoid Android and Cyanogen Mod, on their stock kernels and on Franco kernel as well. I don't have idea, what can be a reason, specially, when on Stock 4.2, 4.3 and 4.4 all is working fine, even on port from N5.
Do you have any ideas what to change to use wifi on my Nexus?
Dmesg shows only this in loop:
<3>[ 543.922386] mdp4_overlay_set: mdp4_overlay_req2pipe, ret=-34
<3>[ 543.922508] msmfb_overlay_set: ioctl failed, rc=-34
<6>[ 543.923821] MDP: unknown ioctl (cmd=40146da2) received!
<3>[ 543.938989] mdp4_overlay_req2pipe: mdp4_overlay_format2type!
Click to expand...
Click to collapse
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?