Related
Hey guys, instead of trying to describe my problem I'll just post this brief report.
Product:
Archos 101 - 16gb
OS:
Urukdroid
Build:
1.0
Firmware:
2.1.8
pre-conditions:
Before installing urukdroid I completely formated the hdd; Urukdroid is installed in the internal storage.
Expected result:
After the power button is pressed the tablet should wake up properly.
Actual Result:
I need to press the power button several times making the screen blink a couple of times. Every now and then I cant wake it up at all. However, after holding the power button for a few seconds the screen blinks for a brief moment before turning itself off.
- This error is not reproducible when Im using the stock ROM or Chulri's method.
One more question: If im using Urukdroid 1.0 am I stuck with firmware 2.1.8? Is it possible to update to the latest firmware?
Thanks guys!
Same problem..but
ActuallyDan said:
Hey guys, instead of trying to describe my problem I'll just post this brief report.
Product:
Archos 101 - 16gb
OS:
Urukdroid
Build:
1.0
Firmware:
2.1.8
pre-conditions:
Before installing urukdroid I completely formated the hdd; Urukdroid is installed in the internal storage.
Expected result:
After the power button is pressed the tablet should wake up properly.
Actual Result:
I need to press the power button several times making the screen blink a couple of times. Every now and then I cant wake it up at all. However, after holding the power button for a few seconds the screen blinks for a brief moment before turning itself off.
- This error is not reproducible when Im using the stock ROM or Chulri's method.
One more question: If im using Urukdroid 1.0 am I stuck with firmware 2.1.8? Is it possible to update to the latest firmware?
Thanks guys!
Click to expand...
Click to collapse
I have the same problem but i noticed that the problem occurs with certain apss. for example with paypal. After installing it i have the same problem. By the way its not only with Uruk because i formatted and reinstalled with latest firmware and the same thing happens. I do not have a solution yet but uninstall the apps which cause the problem...
ActuallyDan said:
Hey guys, instead of trying to describe my problem I'll just post this brief report.
Product:
Archos 101 - 16gb
OS:
Urukdroid
Build:
1.0
Firmware:
2.1.8
pre-conditions:
Before installing urukdroid I completely formated the hdd; Urukdroid is installed in the internal storage.
Expected result:
After the power button is pressed the tablet should wake up properly.
Actual Result:
I need to press the power button several times making the screen blink a couple of times. Every now and then I cant wake it up at all. However, after holding the power button for a few seconds the screen blinks for a brief moment before turning itself off.
- This error is not reproducible when Im using the stock ROM or Chulri's method.
One more question: If im using Urukdroid 1.0 am I stuck with firmware 2.1.8? Is it possible to update to the latest firmware?
Thanks guys!
Click to expand...
Click to collapse
not sure it is the problem, but try to set the brightness level >30%..
fly_us said:
not sure it is the problem, but try to set the brightness level >30%..
Click to expand...
Click to collapse
Sadly, that's not the problem. I always keep the brightness around 11% to save the battery.
ActuallyDan said:
Sadly, that's not the problem. I always keep the brightness around 11% to save the battery.
Click to expand...
Click to collapse
Try to increase it to >30% and restart again. It is an very old bug of gen 8 Archos since first froyo rom. Any brightness <30% make the wake up process become very unstable.
fly_us said:
Try to increase it to >30% and restart again. It is an very old bug of gen 8 Archos since first froyo rom. Any brightness <30% make the wake up process become very unstable.
Click to expand...
Click to collapse
Oh sorry, there was a small misunderstanding on my end. I actually read <30% last night . Anyway, I have set it to 50% now and so far everything has been working just fine. Thank you!
I have a problem with Huawei Mediapad s7-301u after update to ICS. Everything works fine but when I finish for example with game and put tablet in standby my tablet turn off completely and I must turn on tablet again. Factory reset doesn't help. Flashing rom again doesn't help also. Any solution?
"I have a problem with Huawei Mediapad s7-301u after update to ICS".
Just a couple (or more) of questions , which ROM ICS are you using exactly on your MediaPad, i.e. stock ICS, AOK? (presumably not CWM 10.1 ,CWM 10.2 nor Evervolv as they are Jellied Beans and later) maybe Hwmod Under/Overclock - B0005 to B010.
"Standby" means just tap the power switch, or did you power off'? If not what is standby? TWRP?
If power off did you rename/delete the dload folder on your exSdcard, and last but not least why factory reset? Flashing ROM again, why ,which and how - step by step please let me know.
(I presume you deleted the old rom from the exSdcard) and or recovery.img
If you have powered down the tab, on power on, it should after ten seconds , turn on.
As there are so many "STOCK" roms available, try Settings, About Tablet to clarify, ), scroll down, "Build Number" is S7-301........................"
I am getting confused with some 10 threads as to which ROM is the best for my old Mediapad, but I see no reason why a stock rom would behave as such.
If I can help, reply
Rgds
Hillbillie
a.k.a. Still looking for Olive Oil
Official ROMs C232B005 and C232B002 General Version.
Just tap the power switch.
I remove microsd from tablet. I don't use it. Factory reset because I have problem and I tried to fix on this way. Flashing ROM with instructions from huawei official page.
Honeycomb works without any problem.
hillbillie said:
"I have a problem with Huawei Mediapad s7-301u after update to ICS".
Just a couple (or more) of questions , which ROM ICS are you using exactly on your MediaPad, i.e. stock ICS, AOK? (presumably not CWM 10.1 ,CWM 10.2 nor Evervolv as they are Jellied Beans and later) maybe Hwmod Under/Overclock - B0005 to B010.
"Standby" means just tap the power switch, or did you power off'? If not what is standby? TWRP?
If power off did you rename/delete the dload folder on your exSdcard, and last but not least why factory reset? Flashing ROM again, why ,which and how - step by step please let me know.
(I presume you deleted the old rom from the exSdcard) and or recovery.img
If you have powered down the tab, on power on, it should after ten seconds , turn on.
As there are so many "STOCK" roms available, try Settings, About Tablet to clarify, ), scroll down, "Build Number" is S7-301........................"
I am getting confused with some 10 threads as to which ROM is the best for my old Mediapad, but I see no reason why a stock rom would behave as such.
If I can help, reply
Rgds
Hillbillie
a.k.a. Still looking for Olive Oil
Click to expand...
Click to collapse
matke84 said:
Official ROMs C232B005 and C232B002 General Version.
Just tap the power switch.
I remove microsd from tablet. I don't use it. Factory reset because I have problem and I tried to fix on this way. Flashing ROM with instructions from huawei official page.
Honeycomb works without any problem.
Click to expand...
Click to collapse
I have no problem with B005 nor B010 (Both HwMod´s original root and the overclocked kernel version)
Have you tried these?
Tthe simple download , unzip , copy dload to card , reboot, take out card and power off
for ten seconds after the droid blacks out?
It took me a while to to get it right - as in I loaded o.k. then powered off too soon, then tried again - but it´s working fine for 4 months now.
(not forgetting to rename dload, of course!!)
Hope this helps, also checkout androidiani.com for hwmod´s old threads if the downloads aren´t here
hillbillie
Hello,
I have been looking for the answer all over but can´t find it.
I have 3 nooks, they all worked fine for 6 month, but this year in January they all automatic self restored them selves, and downgraded to the old version 2.0.2
I don´t know what happened or what could cause this problem, i did not press any restore buttons or install any software that would cause that, no addition SD cards or cables connected. Just woke up next day they all show me Set up Screen where i have to choose language , and connect to the internet, then they install them self, and i check the version and it´s old one..
After that i have to install about 2-3 updates, till i get to the 2.2 version
The only thing that i suspect is that they were all put together in to the same box, and could be that they press on each other THE N button , but would that trigger them to self restore ??
Thank you, i would really appreciate your help. Because i have more nooks and i am afraid if this could happen to them also one day.
The last version of firmware for the Nook Tablet (the Nook model discussed in these forums) are 1.4.3. Your Nooks most likely are HD or HD+, as the latest firmware for them are 2.2.x. You should post on your question on the forums dedicated to the HD/HD+: http://forum.xda-developers.com/nook-hd.
FWIW, a commonly known trigger for a Nook to get into a state leading to factory-reset is when it fails to boot/reboot 8 consecutive times.
Thank you for your answer, i am so sorry , didn´t realise that this is not NOOK HD forum (
digixmax said:
The last version of firmware for the Nook Tablet (the Nook model discussed in these forums) are 1.4.3. Your Nooks most likely are HD or HD+, as the latest firmware for them are 2.2.x. You should post on your question on the forums dedicated to the HD/HD+: http://forum.xda-developers.com/nook-hd.
FWIW, a commonly known trigger for a Nook to get into a state leading to factory-reset when it fails to boot/reboot 8 consecutive times.
Click to expand...
Click to collapse
I found amazing problem that works almost like magic.
So what happens is that i have 3 nooks , and to save some space i put all of the together in to the same box.
Now i have been doing some test and found out that When you put nooks on top of each other they will turn of the screens and can if you move them a little, they will turn on as well. So that could cause the problem that they would turn on / off so many times that that would lead to the boot / reboot / factory-reset.
It´s unbelievable that 1 nook is turned off can have EFFECT on the other one that is ON, it will wireless tell him to turn of the screen .
Here is the video :
I will post this in to the Nook HD forum
digixmax said:
The last version of firmware for the Nook Tablet (the Nook model discussed in these forums) are 1.4.3. Your Nooks most likely are HD or HD+, as the latest firmware for them are 2.2.x. You should post on your question on the forums dedicated to the HD/HD+: http://forum.xda-developers.com/nook-hd.
FWIW, a commonly known trigger for a Nook to get into a state leading to factory-reset when it fails to boot/reboot 8 consecutive times.
Click to expand...
Click to collapse
The Mini M8S TV Box is a new budget box running Android 5.1 with the Amlogic S905 and 2GB of Ram.
Review:
Mod Edit: Link leading to affiliate sales links removed
Hello,
it coming with root or how it can be rooted?
Thank you.
The Mini M8S is very intriguing. SD card, Bluetooth, and 2 GB RAM. Just need to find it from a reputable retailer online, since I'm probably going to stay away from Gearbest. Would like to know if this box can be wiped and installed with a vanilla Android OS. Would like to start from scratch and not be running any of their pre-installed junk.
Also kind of a bummer this doesn't do 5G wifi. I would think that all the newer boxes would include it. It's got everything else I'm looking for in a budget Kodi box.
fireman_vt said:
Hello,
it coming with root or how it can be rooted?
Thank you.
Click to expand...
Click to collapse
According to the review, it's already rooted. I think the question is whether or not it can be flashed with a different ROM. Hopefully there's a guide out soon. Would love to get vanilla Android on it. (just ordered one off Gearbest)
hello, the seller said that it is ...
Quote:
By Brown Apr-04/2016 12:04:38
Question:
Is this unlocked i.e rooted? I came across many apps that say not supported by this device in the play store. Is this where I should or could side load them by merely downloading the .apk myself ?
Reply::
Hello Brown,
Thank you for your inquiry,it is unlocked but not rooted.You can download the app in the media center like kodi.Have a nice day.
Got mine yesterday from gearbest. It was rooted and I must say I'm very impressed. Very fast and played everything I've tried with no buffering and perfect picture. Very happy
Sent from my SM-N920C using XDA-Developers mobile app
KevandLynds said:
Got mine yesterday from gearbest. It was rooted and I must say I'm very impressed. Very fast and played everything I've tried with no buffering and perfect picture. Very happy
Sent from my SM-N920C using XDA-Developers mobile app
Click to expand...
Click to collapse
Hi, can you tell me if this boots when powered or do you have to turn it on with the remote? Thanks.
Gunde said:
Hi, can you tell me if this boots when powered or do you have to turn it on with the remote? Thanks.
Click to expand...
Click to collapse
It's powered up as soon as I plugged in the cable
Hello, I also I got one. Well done, compact, without lags. The device is root. Only small usb ports and little available RAM. I personally use a Nova launcher and combined small keyboard with touch.
Best Regards.
(Google translate)
Hi to all. Does anyone know how to reflash the rom in case we need to do so? The device is rooted. A bad apk may cause harm. Where can we find the rom to reflash if this happens?
I've also got e of these but is giving me problems with failed updates and random reboots. Could do with reflashing to see if this solves the problem but I have no idea as to where to get the files from for this device. Anyone know?
Or is there a different firmware I can try?
Cheers
From http://www.gearbest.com/:
By Bryan Apr-12/2016 05:04:55
Question:
Where can I download firmware updates?
Reply::
Hello Bryan,
Please kindly send us e-mail to http://www.gearbest.com/about/contact-us.html. Then we will contact our supplier to ask for the update firmware.
This box is very nice, here are some details:
There is a small hole underneath for the reset button; you can use a toothpick to hold the button while you insert the power. This will give you access to recovery.
Looking at traffic flow I can see it connects to fota4.adups.cn to determine if there is a new update and downloads the updates from: hwfotadown.mayitek.com
Here is the latest patch as of this writing:
http://hwfotadown.mayitek.com/ota/r...04011829-LMY47V-2016041117331460428050687.zip
At this time I am unable to find a full firmware IMG file that I could use with the "USB Burning Tool" (The ultimate recovery, if things go bad)
For me there is no OTA update (says i have the latest), device comes with firmware from 28 of March, It is working fine though.
I installed Selinux mode changer to make Selinux permissive and after reboot the device was unresponsive. I tried the reset procedure as described by tpcip6 above and after a factory restore the device restored the rom perfectly. All apps were there despite the fact that i had uninstalled a couple of them. I was surprised. How could this happen? Is there a hidden recovery partition or something? Anyway i was happy that the box was fully functional again.
r0c0 said:
For me there is no OTA update (says i have the latest), device comes with firmware from 28 of March, It is working fine though.
Click to expand...
Click to collapse
I'm getting the same problem. Other people have mentioned that there's an update by my OTA is saying it's up to date even though i have the March version. Even the screenshots from @fireman_vt show an April update.
Thanks to @tcpip6 i've downloaded the new update.
Also, i'm having an issue with Kodi and SPMC where any 5.1 file i play with passthrough enabled causes audio drops every few seconds (i'm using HDMI). Hopefully the updated can help with this issue.
pratikp16 said:
I'm getting the same problem. Other people have mentioned that there's an update by my OTA is saying it's up to date even though i have the March version. Even the screenshots from @fireman_vt show an April update.
Thanks to @tcpip6 i've downloaded the new update.
Also, i'm having an issue with Kodi and SPMC where any 5.1 file i play with passthrough enabled causes audio drops every few seconds (i'm using HDMI). Hopefully the updated can help with this issue.
Click to expand...
Click to collapse
Did you manually applied the update and did it work?
r0c0 said:
Did you manually applied the update and did it work?
Click to expand...
Click to collapse
I am still at work so haven't had a chance. I hope it's as simple as booting into recovery and flashing? Will try an OTA just before in case.
pratikp16 said:
I am still at work so haven't had a chance. I hope it's as simple as booting into recovery and flashing? Will try an OTA just before in case.
Click to expand...
Click to collapse
Dont think you need recovery, just copy the file to root of sdcard and then in the update app choose offline.
Maybe they removed the update because of issues like the disappearing of google play store?
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