I have a problem when I update to 4.3 rom. I turn on auto-rotate. When I rotate the screen horizontally. I get bootloop. It automatically restart. I tried in 4.1.2 and 4.2 versions. It doesn't have this problem. It only occur in 4.3 rom. Can you help me to solve this problem ?
Hi,
I have a Qware TB-9718D tablet (rebrand of ployer-momo11-speed) with RK3066 CPU and Android 4.04.
I've installed the CWM-ROM-Ployer_Momo11_3-0-8_M1_software_chinese-version_4-2-2_20130425-4-2& CWM ROM (Android 4.2.2) on the tablet and it boots just fine.
However, the touch screen does not seem to work anymore with this ROM.
I have tried two touch screen fixes (which were suggested on another site): one of which was the 907c_compatibility_1.2.0.zip
Both files did not solve the problem.
Does someone else have any suggestions on how to fix the touch screen with this ROM?
Could I for example extract the touch screen driver from the original ROM's lib folder and use it in this new ROM?
Thanks in advance.
Does anyone have any suggestions?
Hi friends my Turbox Tablet Model No. G78 is keep restarting.
when i wipe it in recovery mode then it works fine but after 2, 3 hours or after 1 day when i connect to internet and start to install some apps after this tab start restarting.
and some apps auto install like, Privacy Guard, Easy Touch, Omni Swipe etc.
and also have some suspicious services like. Timeservice, MonkeyTest etc.
please help about this problem and also provide any custom ROM for my TAB.
what custom recovery did you use for this? I have a G78 Chinese tablet too running on Andorid 4.1.1 and I'm looking to update the OS in here to a custom rom.
I was in China recently and bought a Koobee Halo H1 but even when the language is changed to English, it still gives system updates in Chinese and won't let me install Google Play or anything related.
I tried flashing it with the official ROM from NeedRom and it seemed to work but now the screen is completely unresponsive (the screen turns on but the touch screen won't respond when it's pressed). I've tried reflashing it, updating it and so on but the same problem always arises.
Would anyone have any suggestions on how I can get it to use an English operating system that can use Google Play?
Any help greatly appreciated.
Hello,
I have a Samsung Galaxy S4 (i9505) with a strange behavior (ghost touch, mainly). Anyway, I have installed a dozen of custom ROMs (even reinstalling the stock ones) with no success.
I've noticed that no matter what ROM was currently installed, I've got the same TSP values (when running *#2663# code):
Phone's TSP FW version: SYB0085C
Part's TSP FW version: SYB0085C
Config TSP FW Version: SGH-I337_SY_0608
TSP checksum data: NA
(btw, I actually have an i-9505 model but it prints SGH-I337 , as above)
Looks like the phone software was messed up by the former owner (or by a regular update).
I've tried to wipe/format all the partitions (I'm using TWRP recovery) but the TSP firmware is still there (as the TWRP itself uses the touch screen input only).
How to actually get rid of the current TSP firmware (complete wipe/remove) so I could install another version from scratch (along with a custom ROM or such)?
Does the recovery software (TWRP) use a custom (embedded) TSP firmware? (though I got the same ghost touches in TWRP, too).
Thank you in advance for any help.
I've just installed (downgrading) another TWRP version (hoping for a non-touch driven interface - with no luck).
Anyway, while testing the new recovery interface I've noticed that the ghost touches almost disappeared (and they were present in the recovery mode, too).
After restarting the phone, I've noticed the same reduction in ghost touches (though they're still "alive") but I wonder what could have been the influence of the new (actually, older) version of TWRP on touch screen firmware (or touch screen behavior, for that matter)?
Does the recovery software (TWRP) use it's own touch screen firmware and did it actually rewrite the former TSP firmware version?
Any ideas, please?
I've made some progress on chasing the TSP firmware.
I found that the "apnhlos" (by-name) partition is mounted as /firmware during regular operation (but was not mounted during recovery). Hence I have mounted it then I found out its content:
Code:
keymaste.b00 q6.b00 skmm_ta.b03 tima_key.b03 tima_pkm.b03 vidc.b03
keymaste.b01 q6.b01 skmm_ta.mdt tima_key.mdt tima_pkm.mdt vidc.mdt
keymaste.b02 q6.b03 tima_atn.b00 tima_lkm.b00 tzapps.b00 wcnss.b00
keymaste.b03 q6.b04 tima_atn.b01 tima_lkm.b01 tzapps.b01 wcnss.b01
keymaste.mdt q6.b05 tima_atn.b02 tima_lkm.b02 tzapps.b02 wcnss.b02
mc_v2.b00 q6.b06 tima_atn.b03 tima_lkm.b03 tzapps.b03 wcnss.b04
mc_v2.b01 q6.mdt tima_atn.mdt tima_lkm.mdt tzapps.mdt wcnss.b05
mc_v2.b02 skmm_ta.b00 tima_key.b00 tima_pkm.b00 vidc.b00 wcnss.mdt
mc_v2.b03 skmm_ta.b01 tima_key.b01 tima_pkm.b01 vidc.b01
mc_v2.mdt skmm_ta.b02 tima_key.b02 tima_pkm.b02 vidc.b02
Now that's the true challenge: which one is the TSP firmware (if any)?!
Any help, please?
I'm in the twilight zone, really.. I've tried to delete the whole content of "apnhlos" aka "/firmware" aka "/dev/block/mmcblk0p1" while in recovery mode, it shows an empty partition but after reboote the whole content is back!
I've even tried to format it (mkfs.vfat /dev/block/mmcblk0p1), it looks empty afterwards but then again, the data is back after reboot.
Now I really need some help.. how to actually get rid of that partition content?
Any help, please? I'm running out of ideas..
Meanwhile, my sensor hub (software) has broken, too (no sensor is working nor detected) hence I need to reflash that sensorhub firmware too.
I've tried the "*#2663#" method but it fails when I'm trying to update SENSORHUB.
I've flashed a lot of stock ROMs (using Heimdall tool) but no one seems to change the TSP or SENSORHUB firmware.
Are they stored on kenrnel or something?
Hi guys,
Still no luck on my quest of replacing my phone's touch screen driver.
I found the location of the driver (/sys/bus/i2c/drivers/synaptics_rmi4_i2c) but I don't know how to disable it (for testing purpose only) or how to actually replace it.
For instance, does anyone know how to disable (or unbind de touch screen device from the aforementioned driver) using an adb (shell) command?