I recently flashed my first rom, going from stock 2.3.3 to Fallout 4.4.0. I always had the sms delay issues on 2.3.3, since flashing Fallout 4.4.0 I've still got the issue, but I also have text messages going missing as well.
Do any of the ICS custom roms have the SMS delay fix built in? Or is there a way to apply the fix to any rom I use?
Thanks
I've never had any issue with text messages going missing or any delay issues, either on stock or (currently) on CM9.
Are you sure it isn't a hardware issue with your particular phone instead of software?
It is a noted issue with some Desire S handsets. Why it's only some I don't know. There are a lot of users with this issue - link. It's also been discussed here on XDA.
FlexiPack said:
It is a noted issue with some Desire S handsets. Why it's only some I don't know. There are a lot of users with this issue - link. It's also been discussed here on XDA.
Click to expand...
Click to collapse
I do vaguely remember something to do with this issue, but I think it was solved by an HTC update a long time ago. I can't imagine that any current ROM has this issue - it was a base software fix, not an add-on fix AFAIK.
If you are getting this now then I suspect it is something other than the ROM causing the problem.
FlexiPack said:
It is a noted issue with some Desire S handsets. Why it's only some I don't know. There are a lot of users with this issue - link. It's also been discussed here on XDA.
Click to expand...
Click to collapse
That link also points to the software update that brought the Android version up to 2.3.5 as fixing the issue, why didn't you upgrade to 2.3.5? I still think it has something to do with your hardware and the fact it is only some would make me think that even more.
I presumed that any rom after 2.3.5 would have the fix but it was still happening on the ICS rom I tried. Today I have flashed 2.3.5 (version 2.10.401.9). I've still got sms delay
It's looking like it's not a software issue but I don't understand how it could be a hardware issue. Surely a hardware fault would mean they either do come through or don't, not the occasional delay or one going missing. So far my phone doesn't seem to have dropped signal when idle, so it 'may' have fixed something at least!
If my memory serves me correctly then the issue was related to the radio that came with the 1.47 update many moons ago
Sywepd form my DsereiS
That's interesting. Perhaps I could update to a custom rom and change the radio. So far the delays have been very short and none have gone missing so it's definitely better than before. I'd hate to be stuck on gingerbread though.
Related
Ok I've been meaning to make this thread for a while now but held off on it assuming it was just my phone, or maybe even just a small batch of phones. But now that I have noticed a lot of people having the same problem as mine the I feel that it should definitely be addressed and hopefully more people will be more aware of it.
Basically the problem is with the touchscreen while I am typing. Certain keys will just "lock" up and become unresponsive. The most noticeable key would be the "Delete" key. It won't work and would be completely unresponsive, only way it will come back in working form is if I just simply wait, or close/re-open the keyboard. Other keys get affected as well, such as other vowels and the letter "O" is prominent as well. But pretty much almost every key gets affected here and there, the "delete" key is just the most prominent and happens more than the others.
Now the obvious first act would be to pin-point the problem. Various possibilities would be:
- Keyboards fault
- Kernel/ROM's fault
- Or if it's just a manufacture defect
First I thought it was just the stock Android KB's problem, so I'e literally tried almost every mainstream KB out there in the market such as:
- SmartKeyboard Pro
- SwiftKey X
- Flex T9
- Swype
- HTC's Touch Input
- Go Keyboard
And with all of those I still experience the problem. So I counted out the possibility of the KB being the cause of the problem. So then i figured it was the ROM itself, but I've tried numerous ROM's such as Virtual Fusion, Virtual Unity, speedDEMON MIUI, CM7 and it's numerous RC's/Nightly's. And the problem still persisted with all of those ROM's.
The only ROM's I know it doesn't happen on is Royal Ginger 2.1 and the stock T-Mobile mySense build. Also I've had other MT4G's in the past that did not have this problem on any ROM.
That confused me as now I can't tell if the problem is software or hardware related.
Thus, I called TMO for a warranty exchange. The phone I had where the problem happened was good screen with BAD eMMC chip. The new one I just received is good screen with GOOD eMMC. With my new phone the problem still persists.
So basically I would just like to get to the bottom of this problem and see if anyone else is having this problem, and if so please post your issue here as well. I would really like to know if this is just maybe a kernel issue with the latest MT4G kernels that are out, or if it's just another one of the plethora of hardware problems that haunts the MT4G.
====UPDATE====
Okay, so there seems so have been a fix floating around for this and it was DEFINITELY not what I had expected. Credit goes to the dude that found it and for jberg22 for bringing it to the attention in this thread. Here is the thread that you can read up on. I'm not sure if it's a 100% fix but it has been a fix for some. Try it and let us know what your results are! It would be nice to know if this has worked for people with this problem. Here's a picture of what it looks like on our MT4G thanks to Mathato!
Glad you decided to post about this. Since more and more people are having touchscreen issues, it's definitely becoming a problem. The mystery is why the problem occurs on all ROMs except for RG. Hopefully more people will post here with their issues and we can get this thing nailed down!
TeeJay3800 said:
Glad you decided to post about this. Since more and more people are having touchscreen issues, it's definitely becoming a problem. The mystery is why the problem occurs on all ROMs except for RG. Hopefully more people will post here with their issues and we can get this thing nailed down!
Click to expand...
Click to collapse
I had that problem with my first mytouch 4g and then ended up bricking it trying to unroot it...but i've never had a problem with this one.
never had any problems like this before... did it happen over time? or immediately after you flashed the ROM?
saranhai said:
never had any problems like this before... did it happen over time? or immediately after you flashed the ROM?
Click to expand...
Click to collapse
Pretty much after a day I started to notice it with VU. But it's usually instant.
I've been complaining about this for a while. Since it doesn't happen on stock rom I don't know wtf to think.
Sent from my HTC Glacier using XDA Premium App
I've definitely seen this,
Some keys lock,
The answer button when receiving a call,
The pull down bar not sticking, for example able to grab it but once sliding it down an inch it goes right back up.
All this on ONLY VU.
No other ROM does this to me, but I stick with it because I love unity!
Sent from my HTC Glacier using XDA App
I wonder if this is happening on 2.3.4 builds only?
my2sense said:
I wonder if this is happening on 2.3.4 builds only?
Click to expand...
Click to collapse
I'm assuming the ota 2.3.4 doesn't have this issue?
Sent from my HTC Glacier using XDA Premium App
Phateless said:
I'm assuming the ota 2.3.4 doesn't have this issue?
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
Good question. I have yet to try the official TMO OTA ROM. But I would assume the problem would disappear in that build. I'll probably flash it to check one day.
Sent from my HTC Glacier using XDA Premium App
If there's at least one build that doesn't have this bug (and which happens to be the original build) - it means that it's SW issue.
Jack_R1 said:
If there's at least one build that doesn't have this bug (and which happens to be the original build) - it means that it's SW issue.
Click to expand...
Click to collapse
I agree. I went back to stock, almost hoping to see the issue appear again, but it didn't.
Jack_R1 said:
If there's at least one build that doesn't have this bug (and which happens to be the original build) - it means that it's SW issue.
Click to expand...
Click to collapse
I would tend to think so too, but I've run VU since the day it was released with no issues, yet Mackster can't run that ROM because he's unable to type. I think it's possible that within the MT4G production run, there are slight H/W differences somewhere within the phone's internals. I mean, the problem occurs on almost every ROM for him (everything except RG). The problem seems a little more complex than a simple ROM bug.
This happens on my phone as well. Thought it was just me... it didn't happen on stock mySense, or RoyalGinger 2.1. I'm currently running RoyalGinger 3.0 & it hasn't happened yet. It DOES/DID occur on CM7 (nightly & stables), MIUI, Virtuous unity & virtuous fusion ...
I currently have a mt4g with the good screen & bad eMMC chip...
Sent from my HTC Glacier using XDA App
cbutt said:
This happens on my phone as well. Thought it was just me... it didn't happen on stock mySense, or RoyalGinger 2.1. I'm currently running RoyalGinger 3.0 & it hasn't happened yet. It DOES/DID occur on CM7 (nightly & stables), MIUI, Virtuous unity & virtuous fusion ...
I currently have a mt4g with the good screen & bad eMMC chip...
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
God damn dude, same exact situation as me. What are the odds?? Lol. Weird ain't it?
I have a new phone now with good eMMC and it doesn't happen nearly as much, but still happens a little.
mackster248 said:
God damn dude, same exact situation as me. What are the odds?? Lol. Weird ain't it?
Click to expand...
Click to collapse
I don't think it's chance. I think we're onto something here. On phones that have the touchscreen typing problem, it occurs on every ROM except for stock and RoyalGinger. So the question is, what's different about RG? What does it have in common with the stock OTA ROM?
I believe RoyalGinger should be considered stock for this discussion - because it's based on stock.
The pattern you're pointing to might mean that there are indeed some HW differences within MT4G production run, that are accounted for by the stock drivers, but aren't accounted for by other drivers.
Jack_R1 said:
I believe RoyalGinger should be considered stock for this discussion - because it's based on stock.
The pattern you're pointing to might mean that there are indeed some HW differences within MT4G production run, that are accounted for by the stock drivers, but aren't accounted for by other drivers.
Click to expand...
Click to collapse
How is it based on stock btw? Because isn't RG pretty much like 99% CM7? And I think he said his kernel is based off of Zinx's?
Jack_R1 said:
I believe RoyalGinger should be considered stock for this discussion - because it's based on stock.
The pattern you're pointing to might mean that there are indeed some HW differences within MT4G production run, that are accounted for by the stock drivers, but aren't accounted for by other drivers.
Click to expand...
Click to collapse
I think you're thinking of RoyalGlacier, which is based on mySense. RoyalGinger is an AOSP-type CM7-based ROM. I think you're right that this issue may be driver related. It'd be nice to figure out what's different about the stock and RG drivers, compared to all other ROM's hardware drivers.
TeeJay3800 said:
I think you're thinking of RoyalGlacier, which is based on mySense. RoyalGinger is an AOSP-type CM7-based ROM. I think you're right that this issue may be driver related. It'd be nice to figure out what's different about the stock and RG drivers, compared to all other ROM's hardware drivers.
Click to expand...
Click to collapse
I think for the purpose of testing we should roll back to a 2.3.3 build of cm7, because I never noticed this until a couple months ago.
Sent from my HTC Glacier using XDA Premium App
Hi my Friends, Please Report any Problem with Primo-S Rom.
Not leaked In Orginal Post.
at first By My Phone :
1. No sound & Mic not Work In Ver.3.0;
2.Downanimation not fixed in display ...
If you read the thread, you will see that there appear to be quite a few reports of sound not working during calls (including by myself). This seems to be a common problems which is sometimes cured by rebooting with a cache-wipe.
Unfortunately this is sdtill very much a beta version and I have no hopes of it becoming stable until HTC release the full version of ICS for the Desire S so we have the correct kernel and hardwae drivers.
Simon.TS.HTC said:
If you read the thread, you will see that there appear to be quite a few reports of sound not working during calls (including by myself). This seems to be a common problems which is sometimes cured by rebooting with a cache-wipe.
Unfortunately this is sdtill very much a beta version and I have no hopes of it becoming stable until HTC release the full version of ICS for the Desire S so we have the correct kernel and hardwae drivers.
Click to expand...
Click to collapse
Thanks for your feedback, but in <3.0 We didn;t Have this Problem.
And prox not answer ....
jack15381 said:
Thanks for your feedback, but in <3.0 We didn;t Have this Problem.
And prox not answer ....
Click to expand...
Click to collapse
I'm afraid that I disagree the reporting of sound issues during calls has been reported in the ROM across all versions. Even though I've never experienced it myself, but I only really try the ROM rather than seriously test it as I appreciate that its still early days.....
ben_pyett said:
I'm afraid that I disagree the reporting of sound issues during calls has been reported in the ROM across all versions. Even though I've never experienced it myself, but I only really try the ROM rather than seriously test it as I appreciate that its still early days.....
Click to expand...
Click to collapse
Any Solution ?
For Example, change build.prop.
jack15381 said:
Any Solution ?
For Example, change build.prop.
Click to expand...
Click to collapse
None found so far....seems to be intermittent, if you read the ROM thread you see that I've already attempted to find if there is a common factor, but haven't found one so far, it can often be resolved by rebooting, which isn't good, a phone which doesn't function for calls is pretty useless to me! Although this is cutting edge ROM port still awaiting the correct kernel version so needs to be given time.
Hi,
I rooted my phone a couple of days back & upgraded to ICS using Hellfire v1.8 rom.
Since I was getting lags, I also got the flak0's lag fix.
I have started facing an issue the phone would freeze post a long call on the phone screen, I can't even get it to reboot by pressing 'lock+vol up' button. The only way is to remove the battery & put it back.
I saw a similar issue seen in this thread from partzman2:
http://forum.xda-developers.com/showthread.php?p=28342782#post28342782
But unfortunately, I am unable to comment on the thread as I don't have enough posts in my name. I searched the forums for this issue, but couldn't find a solution.
Any help is appreciated.
My sincere thanks to dev folks
Just wanted to take a moment to thank the dev folks who put in a lot of work in creating these roms/mods - experience is so much better, I can't even begin to explain.
I have had g2x for more than 14 months now & I had been running stock froyo 1st & then GB (2.3.3) - the experience was so bad, that I used it only for making phone calls or occasional emails, as i couldn't even browse or do anything w/o hitting some problem or the other. Even phone calls used to crash at times.
After updating to ICS, I haven't stopped using the phone be it browsing, watching you tube videos, trying new apps, emails etc, with occasional phone calls .
Again, thanks a lot for so much hard work, its really appreciated.
gg84 said:
Just wanted to take a moment to thank the dev folks who put in a lot of work in creating these roms/mods - experience is so much better, I can't even begin to explain.
I have had g2x for more than 14 months now & I had been running stock froyo 1st & then GB (2.3.3) - the experience was so bad, that I used it only for making phone calls or occasional emails, as i couldn't even browse or do anything w/o hitting some problem or the other. Even phone calls used to crash at times.
After updating to ICS, I haven't stopped using the phone be it browsing, watching you tube videos, trying new apps, emails etc, with occasional phone calls .
Again, thanks a lot for so much hard work, its really appreciated.
Click to expand...
Click to collapse
Hi, welcome to XDA :fingers-crossed:
I have some sort of sad news for you. In general-- ICS on the G2X isn't really stable right now. A lot of rom's have problems with lag after a few weeks, graphical errors, rebooting, and phone calles (as you mentioned). I'm not sure exactly how to fix your problem, but I had it too. I couldn't find a suitable fix, so i went back to Cyangogenmod 7 (gingerbread)
The latest nightly (newest build uploaded on their server) is available here: http://download.cyanogenmod.com/?type=nightly&device=tenderloin
If you are NOT using the march 2012 baseband, flash "old_baseband.zip". I am looking for the file (not sure what thread it is in).
What baseband are you one?
Also, If you must try ics, i suggest Owain's build 77. It's one of the most stable I've found so far.
I'll update post soon.
Blazing angel said:
Hi, welcome to XDA :fingers-crossed:
I have some sort of sad news for you. In general-- ICS on the G2X isn't really stable right now. A lot of rom's have problems with lag after a few weeks, graphical errors, rebooting, and phone calles (as you mentioned). I'm not sure exactly how to fix your problem, but I had it too. I couldn't find a suitable fix, so i went back to Cyangogenmod 7 (gingerbread)
The latest nightly (newest build uploaded on their server) is available here:
[//gg84 - I had to snip out the link as I am not even allowed to post a link which actually someone else had put & I am just quoting //]
If you are NOT using the march 2012 baseband, flash "old_baseband.zip". I am looking for the file (not sure what thread it is in).
What baseband are you one?
Also, If you must try ics, i suggest Owain's build 77. It's one of the most stable I've found so far.
I'll update post soon.
Click to expand...
Click to collapse
Thanks for the info. Actually, I went through quite a bit of dev threads before deciding to go with ICS - I was quite curios about its features & was ready to take the risk.
Only thing is that owain's recent 79 build seemed to have quite a bit of issues from the posts, & hellfire seemed a bit old/stable, so went with that. I didn't consider using old owain's builds (which might be an overlook from my part).
Is there a way I can find what I might lose (& possibly gain), if I switch to owain's 77 build?
I am using Jul15, 2011 baseband & kernel is 2.6.32.59-CM9-faux123-050.
Is there a better baseband/kernel that I should try?
I switched the kernel to harsh kernel & I feel that the speed has improved, but "freezing on a call randomly" issue still exists. Also, it crashes & reboots once in a while but I still feel that its worth all the pain as now I am actually able to make use of the phone.
Blazing Angel, did you find the latest baseband which I can try using?
Another bug I found is that I cannot really configure the lock screen buttons/shortcuts - as in adding a an app to be able to accessed from the lock screen like we do for camera. I see the option of changing this in setting but it doesn't persist when I try to change it.
Anyone seeing this?
gg84 said:
I switched the kernel to harsh kernel & I feel that the speed has improved, but "freezing on a call randomly" issue still exists. Also, it crashes & reboots once in a while but I still feel that its worth all the pain as now I am actually able to make use of the phone.
Blazing Angel, did you find the latest baseband which I can try using?
Another bug I found is that I cannot really configure the lock screen buttons/shortcuts - as in adding a an app to be able to accessed from the lock screen like we do for camera. I see the option of changing this in setting but it doesn't persist when I try to change it.
Anyone seeing this?
Click to expand...
Click to collapse
The latest baseband is march 2012. To update, you need to install Tmobile's V21Y update.
Follow this guide
http://forum.xda-developers.com/showthread.php?t=1674901
Note: If you install this, and try to use a rom other than CM7 7.2.0, you need to flash owains New_baseband fix after flashing a rom from here
http://owain.hopto.org/T-Mobile LG...w_baseband.zip
Hi just want to add info with new baseband the bluetooth doesn't work.
Blazing angel said:
Hi, welcome to XDA :fingers-crossed:
I have some sort of sad news for you. In general-- ICS on the G2X isn't really stable right now. A lot of rom's have problems with lag after a few weeks, graphical errors, rebooting, and phone calles (as you mentioned). I'm not sure exactly how to fix your problem, but I had it too. I couldn't find a suitable fix, so i went back to Cyangogenmod 7 (gingerbread)
The latest nightly (newest build uploaded on their server) is available here: http://download.cyanogenmod.com/?type=nightly&device=tenderloin
If you are NOT using the march 2012 baseband, flash "old_baseband.zip". I am looking for the file (not sure what thread it is in).
What baseband are you one?
Also, If you must try ics, i suggest Owain's build 77. It's one of the most stable I've found so far.
I'll update post soon.
Click to expand...
Click to collapse
some of that i experienced my self , most of the times the camera and hdmi port is sacrificed in the g2x
Thanks for the info guys. Say my gps works/locks already (takes a bit of time though) with the hellfire ICS, is there anything I get by flashing this new baseband?
Does it or would it fix the random freezing on calls by any chance?
Basically, I read the instructions & it seems that I'd have to go back to stock, unroot & then re-root + reflash + restore my apps etc - seems like too much if I am not getting something out of it.
If it doesn't add much value, then I will consider doing it once another stable version of hellfire or owain's rom is released..
BTW, did anyone experience the lock screen config issue I posted in my earlier post - basically I can't add custom short cuts to the lock screen, there is an option to do this in the settings but they dont stick (I am on hellfire v1.8 right now)
Hello,
I have the following problem:
I experience visual artifacts when using two-finger rotate in Google Maps, also Photoshpere is really acting up... the images flicker...
Not all devices have it, as a matter of fact there are few of them (reported). Let's try to collect as much data as we can in order to find the cause of this and maybe a fix. I'll start.
HTC One S
Color: Gradient Blue
HBOOT:1.14.0002
Radio:1.06es.50.02.31
Jun 11 2012, 14:36:28
It's recommended to attach a logcat with the problem.
The problem allways happen when try to rotate Gmaps with two fingers, and photoshpere gets crazy especially after taking 1st photo.
It seems like an accelerometer problem, but accelerometer utilities seems to report the sensors working fine, so maybe a GPU driver problem.
C'mon guys, let's get this fixed
For the flicker have you tried changing debug.composition.type=dyn to debug.composition.type=gpu? I also had the same issue with that camera but only tried it when it come out, have you tried other packs that have it?
Darknites said:
For the flicker have you tried changing debug.composition.type=dyn to debug.composition.type=gpu? I also had the same issue with that camera but only tried it when it come out, have you tried other packs that have it?
Click to expand...
Click to collapse
I've tried many packs... i will try those and report back. The thing that scares me is that this happens on Virtuous Rom also (which is almost stock build with HTC jb libs), and this may mean that i will never have fully working jb not either from HTC.
adi4motion said:
I've tried many packs... i will try those and report bach. The thing that scares me is that this happens on Virtuous Rom also (which is almost stock build with HTC jb libs), and this may mean that i will never have fully working jb not either from HTC.
Click to expand...
Click to collapse
What you get both issues on Virtuous? that can't be good.
Darknites said:
What you get both issues on Virtuous? that can't be good.
Click to expand...
Click to collapse
yes... that's also what i'm afraid of...
Keep in mind the camera is for 4.2, not 4.1, and I doubt we'd ever get stock camera on official Sense.
PcFish said:
Keep in mind the camera is for 4.2, not 4.1, and I doubt we'd ever get stock camera on official Sense.
Click to expand...
Click to collapse
ok, that's not a problem, i can live without photoshpere, but the fact is Google Maps also have this problem and I need GMaps...
I know that at least 3 others reported this problem (and i'm sure that are many others who didn't test for it) I wonder where are they now...
I started this thread hoping that if other users reported it, the devs would try to solve this, but i think i'll just have to wait for HTC to give us JB and see if i still have the problem (but I am really concerned that I might have it). What's wrong with this One series? so many bugs (and not minor): cases chipping, helicoptering bug, sound issues, performance issues (one x), this problem....
I reported in another thread that I have this problem and I do, when using photosphere, I've seen it, although if I keep my movements nice and slow and steady, it seems to hold together.
I haven't seen any problem in Google Maps though, what happens to you in there?
Cheers
wheeliemonster said:
I reported in another thread that I have this problem and I do, when using photosphere, I've seen it, although if I keep my movements nice and slow and steady, it seems to hold together.
I haven't seen any problem in Google Maps though, what happens to you in there?
Cheers
Click to expand...
Click to collapse
when i rotate the map with two fingers i get visual artifacts
I have the same problem on photospere, on maps I have no graphical problems, but the magnet sensor seams to change it's direction sometimes. Had this on CM10, and now on 4.1 Sense+.
Edit: I mean I have the orientation problem on photosphere. My screen does not flicker.
I have this same exact problem with an HTC One XL. I have not found a fix for it.
I've tried flashing every flavor of jellybean there is. It oddly seems to not happen if I use a sense version of jellybean. But I hate sense and want vanilla android.
AOKP, AOSP, modded, unmodded, doesn't matter. I get this annoying graphics glitch when I try to scroll around using maps or photosphere.
I hope it's not purely hardware related, and that there's an easy software fix for it.
Ive had an issue now for days now, where texts like to be pushed to my phone very late, though with correct timestamps. I though it was an issue that could be solved by complete fresh install, going from latest viper, to latest clean rom, both running latest bulletproof kernel. perhaps its worthy to note im one twrp 2.3.1, hboot 1.14, baseband 0.19as.32.09.11_2_10.105.32.25L (that's my radio ver right?)
@dethpikil sorry, it wasn't very clear... Was the problem solved with a clean ROM flash or no?
RollTribe said:
@dethpikil sorry, it wasn't very clear... Was the problem solved with a clean ROM flash or no?
Click to expand...
Click to collapse
Nah he said he "thought" it could be solved so I assume it didn't work. Maybe try flashing a different radio?
-Sugardaddy
Also what carrier are you on?
Are these texts coming from people with iDevices? This is a known issue, and it's a problem with iMessage, not your phone. Happens to me sometimes as well.
Lets see. My problem has reduced since new flash of clean Rom and cleaning of excess sms messages. Though lessened I've still experience latency, from other android users. I'm on att. One friend in particular this seems to happen often with is on tmobile android. And I did want to give a new radio a shot, however the ruu processes I have found are unclear and scary, and most ppl only express frustration towards my ignorance, so the new radio will probably wait until I feel more comfortable with whatever it is the ruu process entails.
Sent from my HTC One X using xda app-developers app
@dethpikil you don't have to ruu to change radios
@RollTribe (<< hopefully i did that right lol) im aware, but from what ive come to understand, ruuing is necessary for enjoying the 3.4 kernal. so i just seems that updating would kill a couple birds in the process
I don't think this is solely an issue with iPhones. I get multiple duplicate messages from people with Android phones too, although it happens less frequently compared to people with iCrap.