Related
I'm working on adding support for a WiFi only build of CM-11 for the SM-T325.
I am making no attempt at this time to add cellular support because I don't own the device and it would be very painful to try to do that without the device. However, a WiFi only version seems possible and I want to use this thread to validate that.
As a first step, I'm looking for people to test that this recovery works for them on a SM-T325: cwmr-20140528-mondrianlte.
You'll need to unzip the file and then flash it in Odin. If you don't know how to do that, then a test build is probably not for you!
Yes..it works!!!
crpalmer said:
I'm working on adding support for a WiFi only build of CM-11 for the SM-T325.
I am making no attempt at this time to add cellular support because I don't own the device and it would be very painful to try to do that without the device. However, a WiFi only version seems possible and I want to use this thread to validate that.
As a first step, I'm looking for people to test that this recovery works for them on a SM-T325: cwmr-20140528-mondrianlte.
You'll need to unzip the file and then flash it in Odin. If you don't know how to do that, then a test build is probably not for you!
Click to expand...
Click to collapse
i can confirm that this recovery does indeed function as expected...i installed my rom (ran into a weird "android is upgrading" bootloop but it eventually loaded...that may be my experimental multiwindow mod i'm using or the fact that i have completely deleted the touchwiz launcher) as well as created a backup (didnt restore) & all seems to be in order. I may be overreaching a bit about my abilities but im sure if u get a working wifi version going for us then the least i can do is get the cellular working...on a sort of related note would u happen to know if its possible to output through hdmi while in recovery mode? As far as this build is conncerned...anything else u may need tested just give me a shout
edit: looked for the backup which is usually on the internal sd (read:accessible from pc) and although the folder is there its empty...finally found it in "data-media-clockworkmod" & just wanted to know is this normal?
THEDEVIOUS1 said:
i can confirm that this recovery does indeed function as expected...i installed my rom (ran into a weird "android is upgrading" bootloop but it eventually loaded...that may be my experimental multiwindow mod i'm using or the fact that i have completely deleted the touchwiz launcher) as well as created a backup (didnt restore) & all seems to be in order. I may be overreaching a bit about my abilities but im sure if u get a working wifi version going for us then the least i can do is get the cellular working...on a sort of related note would u happen to know if its possible to output through hdmi while in recovery mode? As far as this build is conncerned...anything else u may need tested just give me a shout
edit: looked for the backup which is usually on the internal sd (read:accessible from pc) and although the folder is there its empty...finally found it in "data-media-clockworkmod" & just wanted to know is this normal?
Click to expand...
Click to collapse
That is normal (it is independent of users and /sdcard is specific to user 0 of the tablet).
If you want to work on the radio, you'll need to be able to build sm-t320. If you get that to build, I'll push up my current repos for the sm-t325.
Would you mind booting into recovery and grabbing a dmesg (/proc/kmsg) for me?
Hopefully I can post a cm 11 build in a couple of hours and we can see how that works.
crpalmer said:
That is normal (it is independent of users and /sdcard is specific to user 0 of the tablet).
If you want to work on the radio, you'll need to be able to build sm-t320. If you get that to build, I'll push up my current repos for the sm-t325.
Would you mind booting into recovery and grabbing a dmesg (/proc/kmsg) for me?
Hopefully I can post a cm 11 build in a couple of hours and we can see how that works.
Click to expand...
Click to collapse
either i dont know what i'm doing or adb isnt working properly in cwm...when i connect i get a weird "usb recognized but there's a problem" sound instead of the usual "affirmative" noise if that makes sense (windows)
Here's a build to try: cm-11-20140528-UNOFFICIAL for the sm-t325.
crpalmer said:
Here's a build to try: cm-11-20140528-UNOFFICIAL for the sm-t325.
Click to expand...
Click to collapse
I will give it a try. No mobile Internet with this rom, right? Which gapps I should use? Or is gapps for every rom the same?
works perfectly...thx
crpalmer said:
Here's a build to try: cm-11-20140528-UNOFFICIAL for the sm-t325.
Click to expand...
Click to collapse
everything seems to be ok on my end although i cant test as thoroughly as i'd like to because my screen is screwed (broken lcd)...gps took a long time to track & still never redrew the map after it did but that was without high accuracy mode enabled & no data of course. Mic, camera, mhl/hdmi, sound, video playback, wifi, bluetooth (wait let me check...yep!), auto brightness, lid sensor are all working properly...so now i need your permission. Besides getting data working...i just want to know am i free to use this in a dual boot configuration with my rom & post it in my thread? Also...this is not important but do u know if screen mirroring works with the wifi version?
THEDEVIOUS1 said:
everything seems to be ok on my end although i cant test as thoroughly as i'd like to because my screen is screwed (broken lcd)...gps took a long time to track & still never redrew the map after it did but that was without high accuracy mode enabled & no data of course. Mic, camera, mhl/hdmi, sound, video playback, wifi, bluetooth (wait let me check...yep!), auto brightness, lid sensor are all working properly...so now i need your permission. Besides getting data working...i just want to know am i free to use this in a dual boot configuration with my rom & post it in my thread? Also...this is not important but do u know if screen mirroring works with the wifi version?
Click to expand...
Click to collapse
I don't know whether or not screen mirroring works. No one has complained but I don't have any way to test it.
You can (obviously) post a link to the thread. I would prefer that you didn't link to a specific version as I hope to post more test builds here (although so far only 3 people have downloaded it which shows either a lack of interest or a lack of early adopters).
crpalmer said:
I don't know whether or not screen mirroring works. No one has complained but I don't have any way to test it.
You can (obviously) post a link to the thread. I would prefer that you didn't link to a specific version as I hope to post more test builds here (although so far only 3 people have downloaded it which shows either a lack of interest or a lack of early adopters).
Click to expand...
Click to collapse
Hello, I will root my device and download the test build as well ! Will post back soon.
Thanks for trying to bring support for this device !
Bautinho88 said:
I will give it a try. No mobile Internet with this rom, right? Which gapps I should use? Or is gapps for every rom the same?
Click to expand...
Click to collapse
Sorry, I missed this post... Use the gapps from the sm-t320 thread.
crpalmer said:
Sorry, I missed this post... Use the gapps from the sm-t320 thread.
Click to expand...
Click to collapse
woohoo...well i got data working but calls are a no go as of right now. i can assure u the lack of activity in this thread is definitely not due to lack of intereset....more than likely its because its barely been a full day not to mention that there are not that many of us lte users but best believe once word gets round they'll come running. As far as my permission request...what i was thinking is that i'll just wait until the monthly releases start coming, make the proper changes for data (unless u actually make ours official also which would be awesome) & include it in a dualboot (hopefully multirom) setup. From what i've read ...alterations will need to be made to both kernels/roms which is why i was asking could i use it. I would definitely put a "use at your risk" disclaimer up as to not have the official thread flooded with issues not actually related to cm itself...let me know if u need anthing else on my end
edit: i do have one weird issue though...i copied the dialer app from another device with cm11 but it doesnt show up in the app drawer but is in fact found within the app manager in settings (i know i can just download another dialer but thought i would ask)
edit 2: calls not working yet & but i did get the phone app to appear & sms are also good to go (no mms at the moment)...got rid of the error message on outgoing calls (incoming wont even ring at all) but now it just force closes before it dials out (even with a different dialer)
THEDEVIOUS1 said:
woohoo...well i got data working but calls are a no go as of right now. i can assure u the lack of activity in this thread is definitely not due to lack of intereset....more than likely its because its barely been a full day not to mention that there are not that many of us lte users but best believe once word gets round they'll come running. As far as my permission request...what i was thinking is that i'll just wait until the monthly releases start coming, make the proper changes for data (unless u actually make ours official also which would be awesome) & include it in a dualboot (hopefully multirom) setup. From what i've read ...alterations will need to be made to both kernels/roms which is why i was asking could i use it. I would definitely put a "use at your risk" disclaimer up as to not have the official thread flooded with issues not actually related to cm itself...let me know if u need anthing else on my end
edit: i do have one weird issue though...i copied the dialer app from another device with cm11 but it doesnt show up in the app drawer but is in fact found within the app manager in settings (i know i can just download another dialer but thought i would ask)
edit 2: calls not working yet & but i did get the phone app to appear & sms are also good to go (no mms at the moment)...got rid of the error message on outgoing calls (incoming wont even ring at all) but now it just force closes before it dials out (even with a different dialer)
Click to expand...
Click to collapse
Here's a new build that has all of the telephony bits enabled. I haven't tried booting it (I'm at work, the tablet is at home) but it should have the dialer and all the other framework that is needed for telephony. Let me know if you get calls working with it:
cm-11-20140529-beta
crpalmer said:
Here's a new build that has all of the telephony bits enabled. I haven't tried booting it (I'm at work, the tablet is at home) but it should have the dialer and all the other framework that is needed for telephony. Let me know if you get calls working with it:
cm-11-20140529-beta
Click to expand...
Click to collapse
Can I use TWRP or must be done under recovery (cwmr-20140528-mondrianlte) from the first post?
megatooth said:
Can I use TWRP or must be done under recovery (cwmr-20140528-mondrianlte) from the first post?
Click to expand...
Click to collapse
twrp is fine. The recovery was just because the first step is to make sure that boots before bothering to get the whole system to boot..
I will install your latest build and return with impressions.
Edit: @crpalmer: Phone.apk/dialer is missing and I have no service.
megatooth said:
I will install your latest build and return with impressions.
Edit: @crpalmer: Phone.apk/dialer is missing and I have no service.
Click to expand...
Click to collapse
Yeah, I made no attempt to get the radio working, hence the title...
@THEDEVIOUS1, did you make any progress on modifying the build I posted to get voice working? If so, let me know what changes you've made and I'll see if I can incorporate them.
crpalmer said:
Yeah, I made no attempt to get the radio working, hence the title...
@THEDEVIOUS1, did you make any progress on modifying the build I posted to get voice working? If so, let me know what changes you've made and I'll see if I can incorporate them.
Click to expand...
Click to collapse
Long story short...still no voice. Now for the rest of it...i've gotten it to the point where i can dial out but neither the mic nor speaker works when the call is answered by the other party (i think this is due to the fact that it reports that the call ends as soon as it begins on my device). As far as receiving calls is concerned...NOTHING. I have even gone as far as flashing a note 3 modem (yeah i know...stupid :silly in an attempt to fix it & still no go...i just recently found the build prop edit to allow outgoing calls so hopefully the rest is as simple as editing the build prop. Speaking of which...getting data/phone working is NOT quite so simple but i've gotten it down to the bare minimum number of changes that need to be made. So far we need to add the "lib-qcril-hook-oem.so" from the n9005 cm11 rom & the "libsec-ril.so" as well "libril.so" from the stock T325 rom (which is enough by itself to get data working) as well as decompile the framework-res.apk & and change both the sms & voice config bools enable to true (which i'm sure there is a flag for in source)...this makes the phone app appear as well as allows u to send texts then we need to add the line "ro.telephony.ril.v3=newDialCode" to the prop which allows us to dial out. Well...thats where i'm at as of right now so its back to google for me to put together the rest of the pieces unless u have some insight from working on devices with radios that can be of some assistance
THEDEVIOUS1 said:
Long story short...still no voice. Now for the rest of it...i've gotten it to the point where i can dial out but neither the mic nor speaker works when the call is answered by the other party (i think this is due to the fact that it reports that the call ends as soon as it begins on my device). As far as receiving calls is concerned...NOTHING. I have even gone as far as flashing a note 3 modem (yeah i know...stupid :silly in an attempt to fix it & still no go...i just recently found the build prop edit to allow outgoing calls so hopefully the rest is as simple as editing the build prop. Speaking of which...getting data/phone working is NOT quite so simple but i've gotten it down to the bare minimum number of changes that need to be made. So far we need to add the "lib-qcril-hook-oem.so" from the n9005 cm11 rom & the "libsec-ril.so" as well "libril.so" from the stock T325 rom (which is enough by itself to get data working) as well as decompile the framework-res.apk & and change both the sms & voice config bools enable to true (which i'm sure there is a flag for in source)...this makes the phone app appear as well as allows u to send texts then we need to add the line "ro.telephony.ril.v3=newDialCode" to the prop which allows us to dial out. Well...thats where i'm at as of right now so its back to google for me to put together the rest of the pieces unless u have some insight from working on devices with radios that can be of some assistance
Click to expand...
Click to collapse
Can you send me a logcat of making a call?
crpalmer said:
Can you send me a logcat of making a call?
Click to expand...
Click to collapse
Keep an eye on this post...i just jumped off the deep in end & tried to install the hlte version as is (with kernel swap of course ) so it may take me a minute to get back (i have a nandroid but like to make the cjanges manually so i know the exact process & origin of files). Well i'll be damned...incoming calls work (complete with mic & speaker) with note 3 version of cm11! Outoing still seem to be an issue but this clears up a few gray areas i had concerning whether the ril files matched the modem & so on...i had the bright idea of swapping a few of the framework files then just thought they were so similar that the whole thing should boot. Anyway....shouldnt be long to figure out what the hold up is now bu tgive me a few & i'll post the log after i test a ouple of things then flash back to the other setup
edit: Aaaaaaannnnddd....done! added the line i spoke about in my previous post to the build.prop & now both incoming & outgoing calls are working with the N9005 version...just out of curiosity i'm about to go through & see whats broken the first of which i notice is rotation (i personally hate portrait) but seems like everything else is as well including wifi, camera, lid, bluetooth, & ironically speaker audio (video playback & apollo play no audio through loudspeaker...both work through wired headset). I will still get that logcat a lil later...at this point i dont think it has anything else to do with the build prop because i had already added most of the stuff i found missing in ours from the hlte & it didnt work. I'm thinking maybe another lib file that needs to be swapped...perhaps maybe something in framework
THEDEVIOUS1 said:
Keep an eye on this post...i just jumped off the deep in end & tried to install the hlte version as is (with kernel swap of course ) so it may take me a minute to get back (i have a nandroid but like to make the cjanges manually so i know the exact process & origin of files). Well i'll be damned...incoming calls work (complete with mic & speaker) with note 3 version of cm11! Outoing still seem to be an issue but this clears up a few gray areas i had concerning whether the ril files matched the modem & so on...i had the bright idea of swapping a few of the framework files then just thought they were so similar that the whole thing should boot. Anyway....shouldnt be long to figure out what the hold up is now bu tgive me a few & i'll post the log after i test a ouple of things then flash back to the other setup
edit: Aaaaaaannnnddd....done! added the line i spoke about in my previous post to the build.prop & now both incoming & outgoing calls are working with the N9005 version...just out of curiosity i'm about to go through & see whats broken the first of which i notice is rotation (i personally hate portrait) but seems like everything else is as well including wifi, camera, lid, bluetooth, & ironically speaker audio (video playback & apollo play no audio through loudspeaker...both work through wired headset). I will still get that logcat a lil later...at this point i dont think it has anything else to do with the build prop because i had already added most of the stuff i found missing in ours from the hlte & it didnt work. I'm thinking maybe another lib file that needs to be swapped...perhaps maybe something in framework
Click to expand...
Click to collapse
The outgoing call issue is likely just that the audio configuration is missing the use cases for voice calls. That's why I wanted the logcat because that should be easy to add.
When you're done with the hlte version (which is actually not a great idea for a daily driver as there are other things that are different that you may not notice (two biggest I can think of is that the hardware is different and several of the HAL libraries need to enable/disable different files in /sys/ and the networking configuration is different which may break some kernel/user-space interactions).
But if you can send me the logcat, the build.prop that you are happiest with and detailed information about anything else that you chnaged (e.g. exactly what you changed in frameworks so I'm not guessing) then I'll take a look at another test build.
So here's my issue, my Galaxy S Blaze has been switched from ROM to ROM constantly, I have seen ROMS with modified build.props, other added features, and a bunch of other tweaks, you name it! I don't know what all those tweaks mean, I have no idea if it could affect the way my phone receives the signal but it got me so frustrated that I kept switching roms until finally then I went back to stock and am no longer am switching to another ROM.
Here's a history of the ROM switching I've made in the past couple of months:
1st - MIUI
2nd- Cyanogenmod
3rd- Gummy ROM
4th- Liquidsmooth ROM
5th- Cyanogenmod
6th- Dirty Unicorns (problems with signal started occurring right about here, and onwards)
7th- Stock ROM (hmm... nope nothing fixed.)
8th- Validus (still no, I didn't like the constant force-closing of many apps)
9th- Gummy ROM (nope, what's worse is my screen kept freezing if I had atleast 2 apps open and I slid down the notification drawer)
10th- Cyanogenmod (well, maybe switching to cyanogenmod will fix it)
11th- Gummy ROM (*sigh* switching back? Nope, still didn't help my signal)
12th- Stock ROM (you would expect it to be fixed right about here, but nope)
So what's up what is the exact problem with my signal? Here's the thing: My signal works! That's a start atleast. However, if I turn on my Wi-Fi while I'm home, I can still call/text people, all of that works. But after maybe 2 hours or so, the signal bar is still there, it's telling me it has signal and it's connected, SOMETIMES it will be empty meaning I have no signal(when I really do). But in reality, I can't receive texts, nor calls, none of that. So how do I fix it? By restarting my phone sadly, that has been the only solution for me for these past 2 months. People have complained to me because I don't answer my phone anymore, well I'm sorry my phone can't receive those calls due to this messed up signal. There are 3 other T-Mobile phones in the house that have no problem! The problem here is with my Blaze phone.
So what if I turn the Wi-Fi off for the whole day and see if it's the main thing causing the issue? Well, I did this. Turns out that the signal stays on longer than when I'm on Wi-Fi but it still goes out. I have switched SIM Cards, I have tried switching my APN: from "epc.tmobile.com" to "fast.t-mobile.com" but the problem appears to happen more quickly on the "epc" one than the "fast" one. Please help me with this, this has been frustrating me a lot lately. I'm not sure if anyone has even had the same exact problem that I'm having, I've searched online but haven't seen a similar problem.
Some of you might say, wow that is a lot of ROMS you've switched to, I'm sure there were more that I missed but that's as of recent. I can install ROMS correctly, I know how to use CWM when installing a .zip and using Odin when it's a .tar(or other supported file extensions). I've factory reset, wiped the cache, the dalvik cache, all before installing a new rom. After installing each rom, I've also factory reset and wiped the cache to make sure no other problems could affect the way the rom would work. Hopefully I did the procedure right, thanks for anyone who's willing to help me!
Right now I am running:
Baseband Version:
T769UVLH5
Kernel Version:
3.0.8-perf-T769UVLH5-CL990184
[email protected] #1
SMP PREEMPT Fri Aug 17 15:12:14 KST 2012
Android Version:
4.0.4
Another Issue is that I can't even transfer files to and from my phone when connected to my computer! This is another big issue, here are some images:
http :// i.imgur.com/xx699ss.png
http :// i.imgur.com/1wRzJpX.png
Here's what happens when I turn Wi-Fi Calling on but maybe it's just a built-in function that I forgot it had and it's probably normal:
http :// i.imgur.com/cTSqRci.png
By the way, sorry for the links just copy and paste them in a browser to and remove the spaces between the http :// and i.imgur, thanks! Unfortunately, I can't post links until I reach 10 posts. If the links don't work for you, I've also provided attachments.
Many thanks!!!
That last picture does show the proper function of Wi-Fi calling however I don't know what to say about the rest of your problems.
Sent from my SAMSUNG-SGH-T769 using XDA Free mobile app
There are two things I would recommend trying...
1. Use Blackhole System Wipe
I know you've been following all the proper steps in CWM (and I would say to keep doing so), but I've added using Blackhole, in addition to the first steps, and I always get great system performance on my phone, and my parent's phones (I put them on ProvisionMod after stock was being stupid). It works well for pre installation for ANY ROM and helps prevent pesky issues. However, chances are, your issue is baseband related and this probably won't solve it... But still! You never know! It's worth a shot!
2. Reroot your phone
I know this will be annoying and pesky... but sometimes the process goes wrong from the beginning and starts giving issues later on... When I first rooted my mom's blaze, something went wrong, despite my following all the directions, and one of her partitions was completely disabled, no matter the ROM. I redid the process of rooting her phone (not from GB though... From the ICS stock) and fixed the issue instantly! I would try these two steps first and see if they do anything! Good luck!
Sent from The Doctor's Blaze
Q&A for Lollipop 5.0 runs on our msm8960s on kkbl
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Lollipop 5.0 runs on our msm8960s on kkbl. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Battery Life
derpyherp said:
I think its odd how there is no deep sleep state i put a screen shot of the cpu times at each cpu speed... Its odd but somehow battery life is amazing
Click to expand...
Click to collapse
I switch back to cm11 because i have 6%/hr of battery drain, (7hr/41min Screen on time, 65% left), that is for me horrible battery life.
I did not look the cpu states, but, if there is no deep sleep, it sould explain mi experience about battery.
I have the same mensage when I was in f2fs. I have to go back to ext4 to work.
Does anyone know if the AOSP Camera will be made available? I don't like the Google one since it doesn't allow me to choose the external SD card as a storage option.
The system itself boots, and runs quite smoothly from what I've tried so far. Very exciting!
But I've found that Lastpass crashes immediately when I try to launch it. I did a clean install with CM12 11/17. Has anyone else seen this behaviour with this app? I'm assuming for the moment it just hasn't yet caught up to Android 5, and I'll have to sit patiently on 4.4 until then.
Cubkyle said:
The system itself boots, and runs quite smoothly from what I've tried so far. Very exciting!
But I've found that Lastpass crashes immediately when I try to launch it. I did a clean install with CM12 11/17. Has anyone else seen this behaviour with this app? I'm assuming for the moment it just hasn't yet caught up to Android 5, and I'll have to sit patiently on 4.4 until then.
Click to expand...
Click to collapse
I don't use that app, but it's probably either one of two things (or both):
This ROM was just release back on 11/14, so it's fairly new (the 11/14 was the first release), so there could be some issues that are causing the app to fail.
The app needs to be updated to run correctly under LP. There were some major changes to the API for LP that could cause other apps to fail that are now using these deprecated API calls. The developer needs to take there app and compile it under the latest LP compiler and libs to see if it compiles.
So, you'll probably have to wait and see. So far, I've been lucky. The apps that I need to work (CoPilot USA, etc) all work. Just waiting for dhacker to figure out the correct set of libs for DRM so that Google Play Movies and Netflix start working again. They work fine under my Nexus 7 running LP, but that was an official release by Google.
iBolski said:
I don't use that app, but it's probably either one of two things (or both):
This ROM was just release back on 11/14, so it's fairly new (the 11/14 was the first release), so there could be some issues that are causing the app to fail.
The app needs to be updated to run correctly under LP. There were some major changes to the API for LP that could cause other apps to fail that are now using these deprecated API calls. The developer needs to take there app and compile it under the latest LP compiler and libs to see if it compiles.
So, you'll probably have to wait and see. So far, I've been lucky. The apps that I need to work (CoPilot USA, etc) all work. Just waiting for dhacker to figure out the correct set of libs for DRM so that Google Play Movies and Netflix start working again. They work fine under my Nexus 7 running LP, but that was an official release by Google.
Click to expand...
Click to collapse
It turns out it was simply a matter of PEBCAK. I uninstalled Android System Webview, because it has the same icon as the stock Browser, while I was removing unwanted processes.
The first time , I flashed 11/15 version, everything seems to work fine ,then I flashed gapps, then I got no signal anymore,but everything else seems to work, so I did a factory reset, the gsm signal came back again, today when I trying to flash 11/18 version, the signal gone again, this time I don't want loose my data , what should I do to get a gsm signal? *#*#4636#*#* seems not working on 11/18, sorry for my poor english
Cubkyle said:
It turns out it was simply a matter of PEBCAK. I uninstalled Android System Webview, because it has the same icon as the stock Browser, while I was removing unwanted processes.
Click to expand...
Click to collapse
Ah, I'm familiar with those errors as well as the ID10T error as well.
Works just fine, very smooth. Had no troubles with the signal at all.
However, I can't receive a call, the dialer just stops. It is possible though to make a call. Anyone had this problem?
yes had that error many times "dialer has stopped", this is work in progress man. I hope that dhacker checks this and the other thread and try to remedy some of the prob.
For that dialer has stopped error, a reboot can cure it. But again i cant rely on a phone that is going to quit when you need to make or receive a call.
So the fix for no service is still reboot and hope?
I'm on Verizon CDMA, XT926, 11/23 build, 11/22 gapps, SuperSU 2.27
Thanks.
Doug B.
I had an odd issue on 11/22 build:
When I connect my car via bluetooth, when a call comes in, pressing the answer button does nothing and the call keeps ringing forever.
Also,
Is Anyone having issues with restoring on TWRP 2.8.1.0? I tried restoring a backup I made and my phone won't boot. It just gets stuck at the cyanogen mod screen.
Edit: I restored a previous backup, installed TWRP 2.8.2.0 and then restored the backup I was trying to. It worked.
dvgb173 said:
So the fix for no service is still reboot and hope?
I'm on Verizon CDMA, XT926, 11/23 build, 11/22 gapps, SuperSU 2.27
Thanks.
Doug B.
Click to expand...
Click to collapse
On my 11/25 build data wasn't working at first, I just turned it on and off from settings and it started working.
11/25 build is working for me as far as being able to receive phone calls. I was previously getting FCs on it when an incoming call was coming, but I was also running f2fs. I've gone back to ext4 and things seem to have stabilized at this point.
This build is the dhacker? I found nothing in his link. Many changes over the previous build?
When open 3g ,call comein can not.
How to fix it?
Thank.
soowijux said:
When open 3g ,call comein can not.
How to fix it?
Thank.
Click to expand...
Click to collapse
Now, I install 30/11 it OK.
Thanks.
SMS issue
Is the sms issue (can't receive sms, although the phone I'm sending from receives the delivery report) still present in this new build (12-02)? I've tried the 11-25 build and BlissPop and none of them allowed me to receive sms... It's the one real issue that's keeping me from jumping into Lollipop
Razr HD (XT925, KK bootloader)
My device does not come out of the boot with this version.
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
Xperia XZ3 (H9493) - 52.1.A.0.672 - RU version
Notification seek bar bug - STILL!!! – If I’m playing media through chrome, soundcloud or another app, the notification seek bar does not work in most situations. This has been a bug since the initial Android 10 roll out and I’m still shocked that we’re still going through this.
Swipe up from the lock screen – I’ve noticed this since the update from Android 9 to 10. It used to be a quick flick of the thumb where I could go from the notifications on the lock screen to the security pattern. Now since the A10 update, I can’t do that anymore. It is a longer swipe, more exaggerated swipe to get to the security options. It was easier with 1 hand before and it needs to go back to whatever it was in Android 9
Camera – Still gives error unknown error. It’s MUCH EASIER to fix than the first and second android 10 releases but it still shouldn’t be like this. It’s at the point where I don’t know if it’s an actual software or hardware problem. And with everything that’s going on, I probably won’t be able to confirm for the next 6 months. I'll probably end up wasting$200 fixing the hardware, that was really a software issue all along.
Fingerprint – Good, I believe either at or close to Android 9 speed
Battery – Good
Networking issues – I believe better than the last update. It seems good so far so
No idea why the software version has to be in the notification quick settings. That doesn’t need to be there. It’s out of place/doesn't add value by being there
I am so frustrated by Sony. They’re taking steps to fix this but damn you should have been on the ball. I do a clean install each update because I don't trust Sony to do this correctly.
This phone is like the Renault Formula 1 team. It's a great product and each update is a step further but holy **** you all should have been a lot farther along by now. Now Mclaren (One Plus) is starting to pass you.
Edit: I forgot to add this earlier. I found a bug by random. In dark mode, About phone -> Emergency Information, the notification bar text is black. So you've got a dark screen with black text.
I still have not received an air update on my H9493. my software version is still 532.
Wa1ker_ru said:
I still have not received an air update on my H9493. my software version is still 532.
Click to expand...
Click to collapse
I too haven't received an update since December on my xz3 h9493 my version is 532
kaderzaim said:
I too haven't received an update since December on my xz3 h9493 my version is 532
Click to expand...
Click to collapse
In the morning I received an update with the numbers 618
Wa1ker_ru said:
In the morning I received an update with the numbers 618
Click to expand...
Click to collapse
I too received it this morning and I'm still waiting for the 672
supervf1s said:
Xperia XZ3 (H9493) - 52.1.A.0.672 - RU version
Notification seek bar bug - STILL!!! – If I’m playing media through chrome, soundcloud or another app, the notification seek bar does not work in most situations. This has been a bug since the initial Android 10 roll out and I’m still shocked that we’re still going through this.
Swipe up from the lock screen – I’ve noticed this since the update from Android 9 to 10. It used to be a quick flick of the thumb where I could go from the notifications on the lock screen to the security pattern. Now since the A10 update, I can’t do that anymore. It is a longer swipe, more exaggerated swipe to get to the security options. It was easier with 1 hand before and it needs to go back to whatever it was in Android 9
Camera – Still gives error unknown error. It’s MUCH EASIER to fix than the first and second android 10 releases but it still shouldn’t be like this. It’s at the point where I don’t know if it’s an actual software or hardware problem. And with everything that’s going on, I probably won’t be able to confirm for the next 6 months. I'll probably end up wasting$200 fixing the hardware, that was really a software issue all along.
Fingerprint – Good, I believe either at or close to Android 9 speed
Battery – Good
Networking issues – I believe better than the last update. It seems good so far so
No idea why the software version has to be in the notification quick settings. That doesn’t need to be there. It’s out of place/doesn't add value by being there
I am so frustrated by Sony. They’re taking steps to fix this but damn you should have been on the ball. I do a clean install each update because I don't trust Sony to do this correctly.
This phone is like the Renault Formula 1 team. It's a great product and each update is a step further but holy **** you all should have been a lot farther along by now. Now Mclaren (One Plus) is starting to pass you.
Edit: I forgot to add this earlier. I found a bug by random. In dark mode, About phone -> Emergency Information, the notification bar text is black. So you've got a dark screen with black text.
Click to expand...
Click to collapse
Same here like a attached photo
Camera unknown error most of the time
Very sometime good again .but I can't
find anyway to slove that problem.I tried to clear cached clear data forced stop disabled
and restart still have that unknown error
After that I flashed stock ftf 10.0
again with full wiped and then repair software with PC suited also wasting time
Please give me any ideas guys thz
PS Xz3 H9493 .618
kokokmt said:
Same here like a attached photo
Camera unknown error most of the time
Very sometime good again .but I can't
find anyway to slove that problem.I tried to clear cached clear data forced stop disabled
and restart still have that unknown error
After that I flashed stock ftf 10.0
again with full wiped and then repair software with PC suited also wasting time
Please give me any ideas guys thz
PS Xz3 H9493 .618
Click to expand...
Click to collapse
It's possible it's a hardware problem. It happens to me too but it was worse with the initial A10 update. My understanding is if you squeeze beside the camera when turning the phone, it can solve the issue. This is because it's a possible loose ribbon.
The initial A10 release was terrible so flash up to .672 and it may fix the problem (if it's a software issue)
supervf1s said:
It's possible it's a hardware problem. It happens to me too but it was worse with the initial A10 update. My understanding is if you squeeze beside the camera when turning the phone, it can solve the issue. This is because it's a possible loose ribbon.
The initial A10 release was terrible so flash up to .672 and it may fix the problem (if it's a software issue)
Click to expand...
Click to collapse
I really appreciated your reply I'm so confused that problem is hardware or not.Coz I got back my camera very sometime but after few days
It happened again ??? and also I found
another user reported that bugs at Sony'
Discussion and any other places when they upgraded to A10.Another problem is
My device is H9394 Dual So latest ver
Of A10 is .618 . Ver 672 is not yet for my
Region thz
PS Now I tried to downgraded android 9
If Downgrade is fix this problem I will
let you know
kokokmt said:
I really appreciated your reply I'm so confused that problem is hardware or not.Coz I got back my camera very sometime but after few days
It happened again and also I found
another user reported that bugs at Sony'
Discussion and any other places when they upgraded to A10.Another problem is
My device is H9394 Dual So latest ver
Of A10 is .618 . Ver 672 is not yet for my
Region thz
PS Now I tried to downgraded android 9
If Downgrade is fix this problem I will
let you know
Click to expand...
Click to collapse
Hey I am also facing this problem on my xz3 dual. Failed to restart the camera is consistently occuring in the past few weeks but restarting the phone worked then. But now its been almost 2 days, camera app says unknown error, I tried everything mentioned above but still unable to resolve the issue. Kindly let me know if downgrading the firmware resolves the issue.
Thank you
Camera unknown error issue
Splinter07 said:
Hey I am also facing this problem on my xz3 dual. Failed to restart the camera is consistently occuring in the past few weeks but restarting the phone worked then. But now its been almost 2 days, camera app says unknown error, I tried everything mentioned above but still unable to resolve the issue. Kindly let me know if downgrading the firmware resolves the issue.
Thank you
Click to expand...
Click to collapse
Of course
I am waiting to downgrade 9
But it was delay coz of covid 19
I can not go to any service center.
Because I can't downgrade it myself .
I hope that problem is software issue .
After downgrade to android 9
That problem can fix or not I will
let you know
Thank you
It is not a software problem for my device
Splinter07 said:
Hey I am also facing this problem on my xz3 dual. Failed to restart the camera is consistently occuring in the past few weeks but restarting the phone worked then. But now its been almost 2 days, camera app says unknown error, I tried everything mentioned above but still unable to resolve the issue. Kindly let me know if downgrading the firmware resolves the issue.
Thank you
Click to expand...
Click to collapse
Today I downgrade my Xz3 H9493 to android
9 but my camera didn't get back.So I decided
to check hardware.that is really sad.
Coz I have to take out all water proof
Seal from my back cover .After that I found
my Camera connector is loose.That's why
occurring unknowm error and after
2 or 3 days is good again.At last that is
not a software error at all.
I got error while enabling tethering
Anyone else?
I'm having signal issues. Dropping connection all the time. Latest firmware hurt this badly.
Same SIM on a Samsung A30S on android 9 works fine.
Hello guys. I need your help finding 52.1.A.0.618 for H9436