Related
Homtom HT10
a new official firmware has been released:
HOMTOM-HT10-Android6.0-V01-20170226.zip
http://www.homtom.cc/
https://drive.google.com/file/d/0By2t6rTTiNQNcEJ1QkpKQnhzck0/view?usp=sharing
no change log unfortunately
could you please report if those major bugs listed bellow are finally fixed?
is it rootable? if yes, how?
- no OTA update
- losing user language preference (simcard default language is used instead)
- losing connectivity (cannot make/receive calls)
- iris / pattern unlock crash/reboot
- random reboot
- screen calibration issue (not responding sometimes and it cannot be fixed with calibration apps from Google store)
- blurry pictures (slow focus and shutter speed)
- bad audio quality (over saturated)
- clean of malwares and chinese apps
Hardware features that were announced but never won't be available (fake advertising / SCAM):
- 5Ghz Wi-Fi compatibily
- NFC
- OTG
*** UPDATE ***
Ok folks... I removed the simcard and also the battery few seconds and flashed latest firmware with sp_flash_tool (firmware mode not download mode) and lost everything (all apps / data) but there is a good news... smartphone doesn't lose language preference anymore!
unfortunately smartphone is still losing connectivity and network (cannot make/receive calls even if there is network signal !)
(I thought it was solved too because it has worked almost half a day but actually i've still got this issue!)
so HomTom HT10 is still a useless 'smart' brick...
And HomTom is doing the same than UMI: banning from their Facebook page users reporting bugs or false avertising (OTG/NFC/Wi-Fi 5Ghz/full bands support/...).
Got mine 2 weeks ago and have not experinced any of the problem above. I think you have got a bad phone only(fake copy?).
I had a update as soon as I started the phone and it is now HOMTOM-HT10-Android6.0-V01-20170225, hmm yours is 0226.
I am no super user of phones but this one is working very good only the sound when doing the iris thing is annoying.
Tradexer said:
Got mine 2 weeks ago and have not experinced any of the problem above. I think you have got a bad phone only(fake copy?).
I had a update as soon as I started the phone and it is now HOMTOM-HT10-Android6.0-V01-20170225, hmm yours is 0226.
I am no super user of phones but this one is working very good only the sound when doing the iris thing is annoying.
Click to expand...
Click to collapse
Mine is the same it's just their typo error. When extracted it's 20170225
Anyway there is a new official firmware... Anyone tried it already?
@ homtom.cc
HOMTOM-HT10-Android6.0-V01-20170510.zip
I'm looking for an English (or global) custom ROM for this device running Android 6.x or 7.x
MoKee, GizROM, LineageOS 13/14/15. Any ROM 100% working.
I bought one of these a while back and using it on the T-Mobile network for over 8 months. I also have not had any trouble that you stated above such as loosing connectivity or the iris scan crashing. I do agree that it would be nice if you could turn off the iris scan noise though. Love this phone and glad I took a chance when ordering it.
I may have found this thread a little late, but here I am. I have the Homtom HT10 running the firmware Android-6.0-V01-20161202 and I was able to root the device using Kingo Root. It's been a while, but I think there were some additional steps to go through before this root worked. My question is if anyone here has had success in rooting one of the newer firmwares, since I'm not sure if this root would survive the firmware update and I wouldn't want to lose root access.
Also, does anyone know how to replace the Kingo Superuser app with Chainfire's version?
mine was working good, i rooted , and install magisk and after a while i loose connectivity when make calls..i flash full firmware..format and all the stuff and still cannot make callss
leo_hacker82 said:
mine was working good, i rooted , and install magisk and after a while i loose connectivity when make calls..i flash full firmware..format and all the stuff and still cannot make callss
Click to expand...
Click to collapse
I've flashed HOMTOM-HT10-Android6.0-V01-20170622 and so far all works pretty good (it keeps the language)...
Only audio EQ quality is poor (distorsion) and volume / quality issue in phone calls.
Not sure yet if OS is able to switch properly from a deficient 4G network to 3G/2G (because i'm currently using forced 3G mode in settings) but it seems to work better than previously.
flashing the Rom
Hi guys. I'm having trouble loading the latest firmware thru sp flash tool.
I'm running Windows 10 and I've installed the extra drivers.
Would love some help.
Thanks
Did you have to push any button combinations to get SPflashtool to start?
chevycowboyusa said:
Did you have to push any button combinations to get SPflashtool to start?
Click to expand...
Click to collapse
maybe u need to press volume up or down..or both i dont remember dont have any more...but that should work...or maybe press power and both volume buttons...
leo_hacker82 said:
maybe u need to press volume up or down..or both i dont remember dont have any more...but that should work...or maybe press power and both volume buttons...
Click to expand...
Click to collapse
I used a different version of flash tool and it started when I put the battery in. There's so many versions of flash tool I guess. But I got it working.
Thanks for the response!
Chevy
My HT10 (got it a month ago) GPS not working
Hi guys
My HT10 GPS in to working. The phone is new, I just got it, and it literally only has viber and Here maps on.
The GPS tested today, not working.
Under a sky with no clouds in the middle of a field with no obstructing buildings and no signal whatsoever.
custom build version: alps-mp-m0.mp9-v1.33_aeon6797.6c.m_p11
Hello
I am french and I live in Ireland.
I have same problem with my Homtom HT10. My smartphone is still losing connectivity and network (cannot make/receive calls even if there is network signal !). I indicated the problem to Homtom who asked me to update Firmware but it did not improve the problem. Homtom suggests me sending back the smartphone for repair but postal charges are very expensive for China.
No solution... I have to restart my Homtom all days if I want to send a SMS or make a phone call.
Perhaps a problem with the SIM Card ?
I got mine since 4 months ago.
Probably the worst android I ever got.
It is fast ok and charge is really quick but its always losing connection. Its more like a photo camera and mp3 than phone.
The other stupid thing is that can connect Wifi 5Ghz and the 2.4 is really slow.
I have already stock firmarware 20170622
Serious Homtom ??
Hi
My question to Homtom :
When Androïd 7.0 Nougat is going to arrive for my Homtom HT10 ?
Homtom's answer :
Dear customer,
Hello.
Unfortunately, we don't have any available news about update to Android 7.0 on HT10 at present. Please note that the original Android platform could not be upgraded in normal situation.
Best regards!
Email: [email protected]
It's not a joke... An incompetent technical department
If my phone is on for more than 10 minutes, I lose calling functionality. When I try to call someone, it freezes and the Pixel becomes unresponsive, forcing me to hold down power for 10 seconds for a reboot. After this, it works just fine for another 10 or so minutes.
I have no idea when calling functionality begins to be lost because I can still send and receive texts, but I can't make or receive calls. I don't even get a wave of missed calls or anything when it works after a reboot.
Google Assistant has it's own issues when this happens too. It won't come up with "Hey, Google" at all. When I long press the home button, Google Assistant comes up, but I just get the floating dots. Fortunately, it doesn't freeze when I try this. Restart the phone and I'm good for about 10 minutes or so. I tried installing 3rd party calling apps, but the problem persists.
Hoping this is a Pie issue and waiting for the next security patch, will likely do a sideload flash-all. Any suggestions as to what the problem is from? Could my SIM card be the problem? Any apps I could try to help narrow down the issue? I had no issues with Oreo.
Thanks in advance.
Tried rebooting in safe mode. Slightly similar results: works fine for about 10 minutes but then it's just the mic not working. I can make and receive calls with out the phone freezing, but no mic.
mbstone said:
If my phone is on for more than 10 minutes, I lose calling functionality. When I try to call someone, it freezes and the Pixel becomes unresponsive, forcing me to hold down power for 10 seconds for a reboot. After this, it works just fine for another 10 or so minutes.
Click to expand...
Click to collapse
I have a similar issue with a used Pixel I purchased. I couldn't place or receive calls, with everything else working fine. Did the prerequisite online searches with results finding most everyone experiencing this issue chalking it up to hardware but I'm still thinking software. I tried a different phone app (drupe-enabled as default) with some success, then the problem returned (a few days later, rarely get/make calls). The default google phone app (version 23.0) fails every time. Currently looking into TWRP/Root and hoping to eliminate certain default apps to experiment further. Will be keeping an eye on this post! :cyclops:
--- Three weeks later ---
Could there be an issue within google play services with phone dialer app (any/or stock app)?
After continued issues I parked phone in drawer a bit then pulled out and tinkered with a few weeks later. Tried to isolate problem using logcat and on a hunch I flashed TWRP and a custom ROM but NOT any gapps package. Sticking sim in and using the built in phone app (Resurrection Remix -com.android.dialer) it works without issue. What? I flashed gapps (correct version/etc) and sure enough the problem returned. Went back to rom minus gapps, works fine. So, with straight up stock rom - stock phone dialer fails, custom rom - it works without a gapps package but not with.
Aimless Rambler said:
I have a similar issue with a used Pixel I purchased. I couldn't place or receive calls, everything else working fine. Did the prerequisite online searches with results finding most everyone experiencing this issue chalking it up to hardware but I'm still thinking software. I tried a different phone app (drupe-enabled as default) with some success, then the problem returned (about 5 days later). The default google phone app (version 23.0) fails every time. Currently looking into TWRP/Root and hoping to eliminate certain default apps to experiment further. Will be keeping an eye on this post! :cyclops:
Click to expand...
Click to collapse
Went back to Oreo before I had the problems and... problems persist. I'm sad. I had the privilege of speaking to someone from Google Support who was very knowledgeable. Unfortunately, my best option from the rep was to take it in to one of their authorized repair places.
Are you guys on Verizon? I'm having this problem with my dad's pixel on vzw.
brkshr said:
Are you guys on Verizon? I'm having this problem with my dad's pixel on vzw.
Click to expand...
Click to collapse
AT&T
---------- Post added at 07:47 AM ---------- Previous post was at 07:45 AM ----------
mbstone said:
Went back to Oreo before I had the problems and... problems persist. I'm sad. I had the privilege of speaking to someone from Google Support who was very knowledgeable. Unfortunately, my best option from the rep was to take it in to one of their authorized repair places.
Click to expand...
Click to collapse
--- Three weeks later ---
Could there be an issue within google play services with phone dialer app (any/or stock app)?
See my updated post (# 3) for what I've tried since..
Vzw ended up replacing my dad's phone through extended warranty. I talked to Google for awhile. Multiple factory resets, factory image installs, tried older phone apks. Nothing worked.
brkshr said:
Vzw ended up replacing my dad's phone through extended warranty. I talked to Google for awhile. Multiple factory resets, factory image installs, tried older phone apks. Nothing worked.
Click to expand...
Click to collapse
Older/newer phone dialer apps didn't work for me either ... custom rom and eliminating google play services did (no gapps). I'm still tinkering with the device ... installing frequently used apps using F-droid and Yalp, will test it. Not quite sure why but it works.
I ended up flashing Lineageos for Microg, presents it's own problems in the learning experience but it works.
Nothing ever worked in the end. No, not with Verizon. Bought through Canadian carrier called Fido.
Called Google tech and they weren't overly helpful. I started a chat with a Google Tech and they suggested I take it to UBreakIFix. They did a free diagnostic test and I referenced https://support.google.com/pixelphone/forum/AAAAb4-OgUsIW_gxTpXX3s/?hl=by that thread. Said they'd fix it for free even thought I was out of warranty. Got a new motherboard and my phone works like a charm.
I want to know how do I flash any if the files found on Google's developer site. (https://developers.google.com/android/drivers#sailfish)
It gives *.tgz files.
The reason for this is that my pixel has been cursed with the dreaded mic issue. I hope that flashing a driver image could help restore some functionality. It has now even spread to my speakers, the phone can't produce audio and videos and audio don't play unless through a Bluetooth device. AUX is not functional.
First it was just the mic giving issues and I good just reboot the phone and it would work again for some time. But now rebooting does nothing and now I can't even hear sound to play a video or game. Please help.
Just to give more description I want a way either via fastboot or adb or through the Recovery to install these files, if possible. Would it solve the issue?
Other issues include not being able to swipe to answer calls and the phone freezes if I do. Apps crash sometimes if they require audio output.
Same issue here (Searching for a used dead phone - 2017 manufactured, maybe screen cracked, body damage etc. So that I can replace the mobo as most of them say this is the way to fix it).
I saw some comments in Google forums that ''Android P beta builds'' fixed the issue for some. Wanted to try that, but I am not able to find beta links (As beta is over)
Installing drivers is worth a try.....Even I would like to know
So anybody has any ideas yet? Anything software wise at all?
Try flashing some custom roms and kernels
**FIX** unlock BL, twrp3231, pixeldust 9.0 ROM, magisk 18.1
Hey friends I was having same issue after stock to 9.0 update (with all patches up to today 3-9-19) on my pixel, first it wouldn't read a Sim and I unlocked the bootloader and used adb to fix that by resetting the modems, then less than 24 hours later it dropped the mic and then sound all together (probably with one of the first updates).
So I updated the phone completely and still no mic no audio. Checked xda and only found this thread. Tried 4 times to download the Google fix and every time it failed so I can't say if the adb sideload fix works but I had already prepped the twrp room and magisk files so I proceeded with that after 24 hours and no solution I could find.
Much to my satisfaction as soon as the rom was loaded (pre magisk) i heard audio. Continued to root and came out with sound and mic and mobile data finally! Pixeldust is very nice so far, snappy and lots of options though maybe a more mellow graphic designer for the stock wallpaper is called for!
Donz7733 said:
Same issue here (Searching for a used dead phone - 2017 manufactured, maybe screen cracked, body damage etc. So that I can replace the mobo as most of them say this is the way to fix it).
I saw some comments in Google forums that ''Android P beta builds'' fixed the issue for some. Wanted to try that, but I am not able to find beta links (As beta is over)
Installing drivers is worth a try.....Even I would like to know
Click to expand...
Click to collapse
Looks like you could try Android q beta now if you want
Sent from my Pixel using Tapatalk
thewraith420 said:
Looks like you could try Android q beta now if you want
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Yeah planning to try it out
melchpro said:
**FIX** unlock BL, twrp3231, pixeldust 9.0 ROM, magisk 18.1
Hey friends I was having same issue after stock to 9.0 update (with all patches up to today 3-9-19) on my pixel, first it wouldn't read a Sim and I unlocked the bootloader and used adb to fix that by resetting the modems, then less than 24 hours later it dropped the mic and then sound all together (probably with one of the first updates).
So I updated the phone completely and still no mic no audio. Checked xda and only found this thread. Tried 4 times to download the Google fix and every time it failed so I can't say if the adb sideload fix works but I had already prepped the twrp room and magisk files so I proceeded with that after 24 hours and no solution I could find.
Much to my satisfaction as soon as the rom was loaded (pre magisk) i heard audio. Continued to root and came out with sound and mic and mobile data finally! Pixeldust is very nice so far, snappy and lots of options though maybe a more mellow graphic designer for the stock wallpaper is called for!
Click to expand...
Click to collapse
how do you reset modems ? my pixel dont read a sim
My Google Pixels microphone randomly died after some point in its lifespan, but happened recently. First i updated version to Android Q Beta 1 (and it was working all right on that version) but when i updated it to Android Q Beta 2 (microphone stopped working and whole UI experience was buggy, some apps not working, random restarts, etc...) but then i got it back on Android Pie, and it worked for few minutes into boot and died yet again... Then i installed custom ROM (Pixel Dust) with TWRP recovery and Root, but nothing of those helped, then i got it back on Android Pie via adb sideload OTA. That didn't help either... So i don't know is it the software problem (because it seems to work first few minutes after i boot it) or is it the hardware problem. I use my phone mostly for phone calls and now because microphone is dead, it lost its functionality... But speaker was working,earpiece and 3.5mm jack.. Any suggestions??
i'm having a similar problem at the moment. Since the April OTA update, phone calls stopped working. Even when using a BT headset. I tried reverting to Full Recovery Image from february, but that only helped a bit. Also, any other audio app was not able to use the speaker. With the Feb version, youtube and google music were back working, but phone calls are still not possible, causing the telephone app to freeze. I was thinking about installing some custom rom too, but that doesn't seem to do the trick. Did you try to wipe the cache in recovery?
Update
found three possible workarounds for people having the same issue, perhaps one of those helps. I'll go through them today evening.
You could try enabling the "Disable USB audio routing" in developer options and see if that works for you. It did work for me
Click to expand...
Click to collapse
A couple of days ago one of the CEs here pointed out to me that I needed to enable the setting for wired headphones in Google Settings > Search, Assistant & Voice > Voice > Hands Free and toggle on the ‘wired headset’ setting,
Click to expand...
Click to collapse
Change your launcher, for example, on nova launcher, disallow permission to microphone for google app and never let him this permission, do not use google assistant.
Click to expand...
Click to collapse
LaTerminator said:
My Google Pixels microphone randomly died after some point in its lifespan, but happened recently. First i updated version to Android Q Beta 1 (and it was working all right on that version) but when i updated it to Android Q Beta 2 (microphone stopped working and whole UI experience was buggy, some apps not working, random restarts, etc...) but then i got it back on Android Pie, and it worked for few minutes into boot and died yet again... Then i installed custom ROM (Pixel Dust) with TWRP recovery and Root, but nothing of those helped, then i got it back on Android Pie via adb sideload OTA. That didn't help either... So i don't know is it the software problem (because it seems to work first few minutes after i boot it) or is it the hardware problem. I use my phone mostly for phone calls and now because microphone is dead, it lost its functionality... But speaker was working,earpiece and 3.5mm jack.. Any suggestions??
Click to expand...
Click to collapse
Maybe is a kernel error..but definitely is not a hardware problem. maybe try changing kernels. o downgrading to 7.
since none of the above tricks worked in my case, i booted TWRP to clean the caches. Didn't bring any good result. So i flashed ElementalX Kernel and now i got some kind of a better result, even if it's still weird. Everything works now except incoming calls. I can actively call other persons, use whatsapp or facebook audio calls and all is good. Only if i receive calls, still mic is muted.
I will try everything from above, and hopefully something will actually work and get my Pixel back in life. I will get you updated guys.
Thanks for the support.
toxic_garden said:
i'm having a similar problem at the moment. Since the April OTA update, phone calls stopped working. Even when using a BT headset. I tried reverting to Full Recovery Image from february, but that only helped a bit. Also, any other audio app was not able to use the speaker. With the Feb version, youtube and google music were back working, but phone calls are still not possible, causing the telephone app to freeze. I was thinking about installing some custom rom too, but that doesn't seem to do the trick. Did you try to wipe the cache in recovery?
Update
found three possible workarounds for people having the same issue, perhaps one of those helps. I'll go through them today evening.
Click to expand...
Click to collapse
None of those helped so far, i'll try flashing some kernel then...
I discovered that when i try to record with my camera video, it says "Can't record audio. Another app is using the mic." Also when i try to record audio message on Messenger app, as soon as i click on microphone icon it says some error.
Update, my sound and video won't record, both on Youtube or Instagram or any kind of video audio playback.
Update
I flashed ElementalX kernel and same stuff happened, phone calls and microphone was working for first 30 minutes then it got back to old days, not working as usual. Now i think this is hardware problem
LaTerminator said:
Update
I flashed ElementalX kernel and same stuff happened, phone calls and microphone was working for first 30 minutes then it got back to old days, not working as usual. Now i think this is hardware problem
Click to expand...
Click to collapse
have you tried chaging vendor image, or getting a vendor image from a working pixel?
I installed lineageos 16 without gapps and is working good for hours until installed gapps.
ericksidaroth said:
have you tried chaging vendor image, or getting a vendor image from a working pixel?
Click to expand...
Click to collapse
how do i change vendor image actually??
I hope this goes to the right place, if not can someone direct me to where it goes.
I'm having an issue with what appears to be the phone app. i can call out but when the recipiant picks up all they here is a beep like a old school fax whine. I've searched this issue and I'm at a loss. Phone is Oneplus 7t with 18.1 hotdogb with no Google.
Thanks for any help,
Lowdownin
It is not just the phone app from my digging. I am also having the same issue with Signal, as well as another dialler I have installed to test. It also happens when using a SIP client both in the Phone app and separately (Mizudroid).
Regardless of how the call is made (inbound to me or outbound to another), all they hear is a high pitch tone. I can hear them fine. Hitting mute stops the noise for them, however unmuting restores it.
I have checked and the phone records sound via the microphone and when in speaker mode and the playback is perfect.
As per @Lowdownin928, I am at a loose end. I am in the process of downgrading and will report if that has an effect.
New ROM released today, tried that first - https://download.lineageos.org/hotdogb. No change.
Downgraded to the last before the one I was having trouble with - lineage-18.1-20210926-nightly-hotdogb-signed.zip - however this has the same issue.
At this stage I cannot work out why the ROM could cause this but then using other ROM's does not fix, even when doing a full wipe. Something else is going on.
Am looking at reverting to a t-mobile or international ROM to go way back and see what happens. If that does not fix it then I am stumped, as it seem to not be hardware. Very, very strange.
OK, so have installed an original t-mobile version of Android 10.0.3 for the 7T and low and behold, it works perfectly. No issue with outbound calls from SIM or SIP, did not bother testing further.
For reference, factory default t-mobile rom I used was at https://onepluscommunityserver.com/list/Unbrick_Tools/OnePlus_7T/T-Mobile_HD63CB/Q/, put phone in EDL mode and run the MDM. Came up fine.
Proceeded to System Update to v. 11.0.1.4.HD63CB. Reboot then tested for outbound noise on calls - no problems at all.
So at this stage the only way to fix this is to revert to the stock ROM, even with 11 it works fine. I have no idea what has happened with the LineageOS ROM but there is a fault somewhere. I am heading off to ask the question (and hope you will as well) but hope all this detail gives you an idea of where to go.
Just had a thought - there may be other ROM's that work fine, it could only be LineageOS that has this issue. If you don't need the feature set then look around in here.
Super surprised no-one else has had this issue, but there you go.
Success. Thanks to LuK1337, Lineage Team Member on the Reddit Support area this seems to have cleared the issue.
---
T-Mobile firmware isn't supported, you can flash retail one by following https://wiki.lineageos.org/devices/hotdogb/fw_update
---
So bootloader, flash lineage recovery, enter fastboot mode inside lineage recovery, flash all the .img's as laid out and then follow the rest of the install. Took a long time and careful reading but this was the key for the phone noise.
Thanks LuK1337.
Just wanted to let you guys know that I was also having the same issue and this solved it for me. Thanks so much dmc.kiint and LuK1337