Related
please help me everybody~~~my phone still can not work g-sensor,light sensor and automatic shut-screen when i calling. i have try all new versions or wm rom,radio.but still can not work too. but they can use well in wm. so i don't what de matter,please~~thank you~~sorry for my poor english~~~
Please post your build and rom information, preferably compactly in your sig.
Did you try to calibrate your g-sensor? This can hose some builds.
dbh369 said:
Please post your build and rom information, preferably compactly in your sig.
Did you try to calibrate your g-sensor? This can hose some builds.
Click to expand...
Click to collapse
i did try calibrate my g-sensor,but it can not work too.
my ROM is ChuckyDroidROM,
Radio: 2.12.50.02_2,
build: NexusHD2-FRG83 V1.5 PPP + RMNET (Android/Froyo 2.2.1).
i did try too many build,such as FroyoStone_Sense_V3.2,d4_Sense_Classic,Mdeejay eVo Sense v. 1.1 Warm,Mdeejay eVo Sense v. 1.8 Revolution.but none of them can fix my problem.......wm rom driver i have try 3.14,2.14.2.10,1.80。radio i have try 2.08,2.10,2.12,2.14,2.15 too.....so i relly don't know what the problem i have.
Many people said never calibrate the g-sensor inside Android....
So if you already do so, you can try to follow the instruction on a thread here focus to fix the g-sensor
Sent from my HTC HD2 T8585 using XDA App
ctrlaltdel said:
Many people said never calibrate the g-sensor inside Android....
So if you already do so, you can try to follow the instruction on a thread here focus to fix the g-sensor
Sent from my HTC HD2 T8585 using XDA App
Click to expand...
Click to collapse
i have try many method...Even the first time just entering the android is still not available g-sensor,lisht sensor too....
i also have this problem, g-sensor seems to work fine but light sensor never worked in android for me.it doesn`t matter what android build,wm rom or radio i`m using it doesn`t work. Now I have mdeeja 1.8 revolution on VBN ROM reloaded*2 with 2.15 radio and it`s doesn`t work
Yes, if you run the calibration sequence in android, you lock it gain numbers taht are too high and the g-sensor goes unusable. I don't know why you are getting that specific error, but two possibilities:
1) you are not getting a good initiation from WM before booting Android
If so, you need to wait a bit before running clrcad and haret
2) the calibration messed you up.
If so, there's a thread on how to undo that, but I don't remember where (search android general I think). Or you will need to rebuild android since this data is stored in your dataimg.
Otherwise, it sounds like it might be hardware related, and you need a new phone.
editted: I've never used a Nexus build, so I would try an EVO. I would also reformat the sd card and go with a clean install just to see. You can tell real quick if it is working be opening email and turning sideway. If the screen autorotates, you have g-sensor. It is possible you have a disabled g-sensor too as that was a common way to address the bad g-sensor response in the early builds. Again a complete clean re-build might find this issue.
If I remember correctly, Chucky boots you straight into Android, you might try a different ROM and see if that helps...
My $0.02...
I have the same problem，too！I try all kinds of wm rom and Android rom！It always didn't worked on the Android，but work perfect on the WM！
dbh369 said:
Yes, if you run the calibration sequence in android, you lock it gain numbers taht are too high and the g-sensor goes unusable. I don't know why you are getting that specific error, but two possibilities:
1) you are not getting a good initiation from WM before booting Android
If so, you need to wait a bit before running clrcad and haret
2) the calibration messed you up.
If so, there's a thread on how to undo that, but I don't remember where (search android general I think). Or you will need to rebuild android since this data is stored in your dataimg.
Otherwise, it sounds like it might be hardware related, and you need a new phone.
editted: I've never used a Nexus build, so I would try an EVO. I would also reformat the sd card and go with a clean install just to see. You can tell real quick if it is working be opening email and turning sideway. If the screen autorotates, you have g-sensor. It is possible you have a disabled g-sensor too as that was a common way to address the bad g-sensor response in the early builds. Again a complete clean re-build might find this issue.
If I remember correctly, Chucky boots you straight into Android, you might try a different ROM and see if that helps...
My $0.02...
Click to expand...
Click to collapse
I do not think a hardware problem, because they can work well on wm,just can not work on android...all of your method i have try again...but still can not work...I'm going crazy...but the Compass can not work, in wm always point on 6076 or 101,in android can not move....
no sensors
same problem. i tried ozy,vbn with 2.10, 2.12, 2.14 and 2,15 radios (with >12 i got ~57mA batt drain) with many sense (mdeejay clean 1.1, evo 2.0, desirehd) / cm6 (jdms, subcraft, hyperdroid) based builds without any success. I always calibrated gsensor and waited for a fixed gps before booting into android.
I'm keen to help to fix but someone should tell how to debug
R, Janos
my tablet specs.:
noname, 7", RK2918 Cortex A8, 512 MB DRR3, 4 GB, mini HDMI, mini USB, SD Card (external), camera 1 (front), wireless and audio from realtek, no bluetooth.
buttons: volume up and down, on/off, reset
original OS: Android Gingerbread 2.3.1
mainboard: M732HR_V1.2 20110921 (from PCB)
(updates made from external sd-card with "update.img", also supports flashing with RKFlash tools via usb)
----------------------------------------------------------------------------------
mtd table from original update.img:
initrd=0x62000000,0x500000
mtdparts rk29xxnand:
[email protected](misc),
[email protected](kernel),
[email protected](boot),
[email protected](recovery),
[email protected](system),
[email protected](backup),
[email protected](cache),
[email protected](userdata),
[email protected](kpanic),
[email protected](user)
----------------------------------------------------------------------------------
needed a firmware (stock or custom) to be able to use some apps etc, so i flashed the one given here:
RK2918 Tab Odys-Loox rocks with CyanogenMod 10 / 10.1!
(http://forum.xda-developers.com/showthread.php?t=2012654, beta build - v1.2)
after flashing completed, tablet hard bricked. no screen, nothing (even backlight of screen not working, so it is not a "black screen of death" but instead "death" only i guess :laugh: , though it reacts on charging with led)
anyone have any idea about what happened or how to recover it?
ps. atm i work on "29-30 pin shorted" thing (http://www.slatedroid.com/topic/41388-unbrick-instructions/) but not sure if it will work for me yet.
update
I was able to de-brick it (couldnt use "short 29-30 pins" thing, chips had a metal cover over them soldered to mainboard, I used reset button with volume buttons, I pushed them like crazy alot of times and somehow got rockchip usb flash state for once then re-flashed stock rom (I had rom-dump files and original "update.img"), it is working now with stock rom.
continued as follows:
1) Tried alot of other roms from similar tablets, some just stays at android screen, some works with corrupt graphics, etc
2) Oma_Odys_Loox_JB_CM10_4.1.2_v1.2 = killed the tab, debricked by luck
3) Oma_Odys_Loox_JB_4.1.1_v1.2.1a (with Oma_extSD_to_NAND_OTG_fix) = works till welcome screen, but touchpad not working so i couldnt check the system further more
4) Oma - Odys Loox GB 2.3.1 v1.3a = touchpad not working, and graphics weird (low color depth+some minor glitches on image), just waiting at main screen cause of touchpad, adb shell works (with root)
5) flashed original kernel over Oma - Odys Loox GB 2.3.1 v1.3a, screen resolution, color depth fine now, touchpad working too, but have problem with sensor, left-right or up-down shifted up to tablet position, trying to fix it
6) activated "ro.sf.hwrotation=270" in build.prop, sensor fine now. Only problem left is touch screen Y axis inverted
7) still working on Y axis issue, but weird thing is calibration works correctly, no inverted axis! and succesfull. but then I have to click upside for something downside or downside for something upside.
8) darn. it is not up or down. it becomes left or right if flip tablet to 1 side.
9) i decided that problem is about touch-driver and i dont have enough knowledge to fix it. left over tablet with factory rom, working but ehhh.
note:
thx to Oma7144, i learned few things from his/her posts, i try to find thx button now xD
I tried to change the internal partitions because by default only 1GB is available for apps, this failed horrible with the provided app (HK Rom Editor) and caused a bootloop.
Afterwards I re-flashed the phone with firmwares which I found on Needrom, that worked fine but the touchscreen is totally misaligned doesn't matter which one I use. If I press for example the top part the phone thinks that I'm touching the middle, it does work fine its just totally wrong calibrated. I can't check if anything else isn't working.
Model: THL 4440, 4GB
Android: 4.2.2
Has someone any idea how I can fix this issue? Do I need a different stock firmware?
Someone told me that I deleted/overwrote my touchscreen calibration files, is there any way how I can identify the chip or get proper files for the THL 4400?
Hi guys,
I am using the S6 Edge 925F with stock Rom. 2 days ago i change my charging port. after that all of my sensor (proximity, accelerator, light, gyroscope heart rate,...) doesnt work. i should to say that before changing the charging port phone accidently went to downloading mode and then powered off
i'm try:
1-wipe cach partition the factory reset
2-install stock rom 6.0.1 with 5 file and re-partiotion
Result: sensors not working.
i'm test with *#0*# and i see all sensor doest work
and then test sensor hub. result:
MCU firmware version: BR010
Bin firmware version: BR0116010800
MCU name :NG
FAIL
i found a working phone has the same version in both places, but my phone has not same firmware version
I don't know how to fix this. Can you guys please help me?
I'm having the same problem, have you been able to fix this problem?
I keep searching for a way to correct, in case I find something I will return to inform.
After updating to firmware 1.31 with teclast OTA updater the touchscreen of the tablet has ghost touches.. I have testet it with a screen touch test app and there are ghost touches on the upper screen boarder without touching the tablet by fingers...
Before the firmware update to 1.31 everything was fine...
Does anyone else got this problem?
I had downloaded the previous older firmware (1.28, no touchscreen problems before with that firmware, zip file) from the teclast website and wantet to downgrade it by flashing the 1.28 firmware with the teclast update tool (local update, choosing the zip file) , but it stops after rebooting with the message "error" and boots up the 1.31 firmware system... What im doing wrong?
I really like the tablet, but these ghost touches since the update to firmware 1.31 are a real problem....
mitsch266 said:
After updating to firmware 1.31 with teclast OTA updater the touchscreen of the tablet has ghost touches.. I have testet it with a screen touch test app and there are ghost touches on the upper screen boarder without touching the tablet by fingers...
Before the firmware update to 1.31 everything was fine...
Does anyone else got this problem?
I had downloaded the previous older firmware (1.28, no touchscreen problems before with that firmware, zip file) from the teclast website and wantet to downgrade it by flashing the 1.28 firmware with the teclast update tool (local update, choosing the zip file) , but it stops after rebooting with the message "error" and boots up the 1.31 firmware system... What im doing wrong?
I really like the tablet, but these ghost touches since the update to firmware 1.31 are a real problem....
Click to expand...
Click to collapse
I have the same problem. We are waiting the new firmware 1.31+
udolini said:
I have the same problem. We are waiting the new firmware 1.31+
Click to expand...
Click to collapse
OK... So it seems to be a software problem... Good to know... Hopefully the issue get solved very soon with a new firmware update....
We're discussing the matter HERE, Teclast seems to be aware of the problem. Let's hope they solve it, and soon enough
I bought the tablet on 26/12/2017 and I had problems with touchscreen but I reflashed 1.32 firmware and I solved the problem. I installed TRWP and rooted with Magisk working well the last 3 weeks. But I started again to have problemas with touchscreen, It doesn`t response any touch. I am trying to flash other firmwares and try to solve the problem, but now I have a tablet with no touchscreen. I am thinking to flash T10 (E3C6)-TOS-V2.00-CDF8 firmware, I know that I have EC35 model but I desesperate. The next step is to give back the tablet to gearbest.
txesterfield said:
I bought the tablet on 26/12/2017 and I had problems with touchscreen but I reflashed 1.32 firmware and I solved the problem. I installed TRWP and rooted with Magisk working well the last 3 weeks. But I started again to have problemas with touchscreen, It doesn`t response any touch. I am trying to flash other firmwares and try to solve the problem, but now I have a tablet with no touchscreen. I am thinking to flash T10 (E3C6)-TOS-V2.00-CDF8 firmware, I know that I have EC35 model but I desesperate. The next step is to give back the tablet to gearbest.
Click to expand...
Click to collapse
I have the same problem.
Maybe completely loosing touch is more of a hardware problem.
It is possible that something break, or whatever went wrong, and no firmware can fix hardware issues. I suggest you try to return your devices. Hopefully, this is just rare hardware problem.
Alan_SP said:
Maybe completely loosing touch is more of a hardware problem.
It is possible that something break, or whatever went wrong, and no firmware can fix hardware issues. I suggest you try to return your devices. Hopefully, this is just rare hardware problem.
Click to expand...
Click to collapse
I don`t think so. I am testing to install another versions and when I installed T10 (E3C6)-TOS-V2.00-CDF8 (I know, the model is not the same), the touchscreen works but with ghost touches. The panel is ok, they have to fix the digitilazer driver.
txesterfield said:
I don`t think so. I am testing to install another versions and when I installed T10 (E3C6)-TOS-V2.00-CDF8 (I know, the model is not the same), the touchscreen works but with ghost touches. The panel is ok, they have to fix the digitilazer driver.
Click to expand...
Click to collapse
Alan_SP said:
Maybe completely loosing touch is more of a hardware problem.
It is possible that something break, or whatever went wrong, and no firmware can fix hardware issues. I suggest you try to return your devices. Hopefully, this is just rare hardware problem.
Click to expand...
Click to collapse
I have found a strange solution. I have inserted a Samsung MicroSD and I have removed it, yesterday it didn't works but this morning (power off the tablet all the night) the touchscreen is working again!! I have to test if the hard case it could be the problem, but I don't think so.
This is really strange behavior. Who knows why it stopped working and then started.
FW 2.01
I have the same issue with ghost touchscreen after installing the firmware 2.01. My previous version was 1.32. I downloaded the FW and then installed it through OTA from local place.
Dead spots in T10 Touch screen
Radek72 said:
I have the same issue with ghost touchscreen after installing the firmware 2.01. My previous version was 1.32. I downloaded the FW and then installed it through OTA from local place.
Click to expand...
Click to collapse
Recently updated from build V1.32 to V1.35.
Have notice that there is (quick often) a "dead" area about 1/2 way up the landscape screen and for most of the width. It's about 10 - 15 mm wide. Detected it with "Touch Screen Test" from the play store. If I move rapidly it seems to minimize it. In some games I have to rotate the screen 180 deg sometimes in order to get a response.
Also the screen is sometimes unresponsive and I have to close with power button a open screen again to get touch response.
Have had some problems with Hall sensor not allowing complete boot and screen response, but I seem to cure that with taking T10 out of the folder / case before booting.
Any Comments or similar experiences by anyone. Think I may go back to V1.32 if I can.
geo_57_3103 said:
Think I may go back to V1.32 if I can.
Click to expand...
Click to collapse
You can, you need to flash full version of 1.32 ROM.
geo_57_3103 said:
Recently updated from build V1.32 to V1.35.
Have notice that there is (quick often) a "dead" area about 1/2 way up the landscape screen and for most of the width. It's about 10 - 15 mm wide. Detected it with "Touch Screen Test" from the play store. If I move rapidly it seems to minimize it. In some games I have to rotate the screen 180 deg sometimes in order to get a response.
Also the screen is sometimes unresponsive and I have to close with power button a open screen again to get touch response.
Have had some problems with Hall sensor not allowing complete boot and screen response, but I seem to cure that with taking T10 out of the folder / case before booting.
Any Comments or similar experiences by anyone. Think I may go back to V1.32 if I can.
Click to expand...
Click to collapse
It is a hardware problem. When my touchscreen wasn't working (power on) I unmounted it and with the tablet unmounted its begin to work. I pressed all the electronics components and nowadays it is working perfectly.
txesterfield said:
It is a hardware problem. When my touchscreen wasn't working (power on) I unmounted it and with the tablet unmounted its begin to work. I pressed all the electronics components and nowadays it is working perfectly.
Click to expand...
Click to collapse
Explain please? What do you mean by unmount?
Do I have to disassemble the tablet? Is it a setting?
geo_57_3103 said:
Explain please? What do you mean by unmount?
Do I have to disassemble the tablet? Is it a setting?
Click to expand...
Click to collapse
Yes. Sorry about my english... I disassembled it and it works prefectly
Ghost touch problem is fixed?
Hi, Teclast replied to my message stating the ghost problem is fixed.. Can someone Please confirm it? Whats the latest firmware you've installed?
txesterfield said:
Yes. Sorry about my english... I disassembled it and it works prefectly
Click to expand...
Click to collapse
Would you be able to post step by step instructions on how you disassembled and reassembled to fix this problem?
Andreserralheiro said:
Hi, Teclast replied to my message stating the ghost problem is fixed.. Can someone Please confirm it? Whats the latest firmware you've installed?
Click to expand...
Click to collapse
Also very interested if anyone has had any progress??
Andreserralheiro said:
Hi, Teclast replied to my message stating the ghost problem is fixed.. Can someone Please confirm it? Whats the latest firmware you've installed?
Click to expand...
Click to collapse
I'm on v1.35, I'm not sure if ghost touches are completely solved, but at the moment I don't see them that much (i.e. lately I didn't noticed any). But, it actually also depends which game you play, as they were problem only in games and only in certain games.
Also, I heard that they are less problem for TOS version, but TOS has other problems, mainly with Google software not working, but I see it is supposedly solved with latest TOS, which is still not available for my device (only for G6 devices).
Anyway, at least there's effort from Teclast to solve this problem and other issues also.
For me, generally speaking, for some time ghost touches aren't problem, but your usage may differ from mine and you can have problems (or not, of course).
geo_57_3103 said:
Recently updated from build V1.32 to V1.35.
Have notice that there is (quick often) a "dead" area about 1/2 way up the landscape screen and for most of the width. It's about 10 - 15 mm wide. Detected it with "Touch Screen Test" from the play store. If I move rapidly it seems to minimize it. In some games I have to rotate the screen 180 deg sometimes in order to get a response.
Click to expand...
Click to collapse
I have a touchscreen problem after updating to version 1.35.
In the lower area is a dead area. It's about 10 - 15 mm wide. Detected it with "Touch Screen Test" from the play store.
Here is my Problem-Video: youtu.be/wPt5pG_fvvU
I hope Teclast solves the problem quickly!!
Baraccuda