Related
Anyone else notice that they're not getting notifications for some received texts on the Inspire? It seems to be random, and I don't notice the new text until I open up the messaging app and see it there, I don't get sound/vibrate or anything in the notification bar. I'm using the Inspired ROM and rooted but I don't think that's the cause of the problem.
I noticed the same thing this morning. I'm completely stock for the moment.
Sent from my HTC Inspire 4G using XDA App.
Well, I guess I'm glad it's not just me. I hope somebody has a fix for it.
I only sent a test message last night after I got the Inspire and it was received and I was notified without issue. Then I installed Handcent and turned off stock messaging app Notifications and Handcent has been working fine.
Rooted with a dhd rom here. I didn't think I was having this problem but checked my messages and sure enough I had one from a hour ago I never got a notification about..... the gf soooo isn't going to believe me its my phone again.
Sent from my Desire HD using Tapatalk
yg17 said:
Anyone else notice that they're not getting notifications for some received texts on the Inspire? It seems to be random, and I don't notice the new text until I open up the messaging app and see it there, I don't get sound/vibrate or anything in the notification bar. I'm using the Inspired ROM and rooted but I don't think that's the cause of the problem.
Click to expand...
Click to collapse
I had a similar issue where my 2 Gmail accounts weren't giving notifications when I received new email. Also my Sense clock/weather wasn't always updating the weather when I unlocked the phone.
I ended up doing a factory reset and reinstalled all my apps manually and everything appears to be fine at the moment.
Yep, same problem. Seems to only happen later in the day?
ditto
**********
Anything guys?? This is really frustrating
Really need help with this. Bump.
Sent from outside your window with my Inspire 4G
I've had the same thing happen. I was in the middle of a conversation and it seemed like the other person just disappeared. Was going to send them another text when I noticed they had actually responded.
The issue clearly hasn't been resolved... It's happening to me as well. No notification. Or I get it, hear it and feel it, and then unlock my phone and no notification in the top bar or on the msg icon on my homescreen. But its def there when I open msgs....this is very frustrating as I've been patiently waiting by my phone for an answer about a new job. Has anyone had a fix for this? I'm completely stock no root. I'm about to go on to ATT and have words with them if it can't be resolved I'm geting a new phone...this is stupid we can't get basic functionality to work....out of the box.
You could try using a different SMS app like Handscent that does notifications itself. I think Go SMS does notifications too.
Or they could admit there is an issue and fix it. I shouldn't have to get a third party app to do basic phone functions like sms and phone. Wtf!
Or you could root your phone instead of expecting AT&T to fix something when it takes them months just to release updates for things that should have been included in the first place.
Well its not really on ATT its on HTC. And besides rooting would void my warranty. And if I get this job ill be leaving the country, in which case id like to return the phone as I doubt it will do me much good in the Netherlands. Either way. Shoulda worked correctly out of the box. It's an HTC sense/Rom issue not an ATT service issue.
So I got my nexus s and like it a lot but I have a question I only have this device for over 24 hours but today in the morning I went to the market to download power amp, anyways while I was in the market the background was black instead of white, I thought it was weird but then again maybe utterly was a feature, now I went to the market to get the pizza hut app(man I been waiting for this since I had it in my iPhone) and the background is white like the evo, what gives? I haven't mess with the setting so I got no idea what could it be?
Thanks for the help
Sent from my Nexus S 4G using Tapatalk
Hope I’m posting this in the right place. Ok here we go:
Bought a Nexus S (i9020T) a couple of weeks ago. It was shipped with 2.3.2. I got the 2.3.4 upgrade OTA and installed it. After the installation the screen has a red tint. And I’m not talking about the color variations between different Android versions, this is really bad! I can’t look at pictures and some text is unreadable. The screen is not broken since the bootloader looks normal, so my guess is that it is software related.
I have downgraded the phone back to 2.3.2 and everything is normal. I have tried to reinstall 2.3.4 as well as going from 2.3.2 to 2.3.3 and then 2.3.4, both by downloading the files from Google and manually install and by doing it OTA. I have unlocked the bootloader and tried to load a whole bunch of different ROMs and Kernels. Nothing works. The Voodoo Color Control is not even close to fixing it. The only version that works is stock 2.3.2. I have googled it and it doesn’t seem to be a common problem.
So I’m reaching out to you guys to see if anyone has heard about this behavior and know what to do?? I can live with 2.3.2 but the reason I bought the phone was to get instant updates. I’ll attach a picture of the home screen which should be black. I don’t have international warranty so turning it in to Samsung is not an option.
Any ideas??
wow. that mr is a defective unit imho. i think that you should try to get a replacement. i do not think that you need international warranty or something. just a receipt might do it. (it worked with htc for many nexus one's purchased on ebay for ex) . just give it a try.
sorry for the news. i hope u get it solved or i hope i am wrong.
keep us updated.
Hmm, yeah I was afraid of that.
Just thinking though, what could be defective? It works just fine on 2.3.2. If i run 2.3.4 (or 2.3.3) and start the phone, the Google-logo shows up in white for about 5 seconds, then it turns red and everything is red after that.
Eldrin said:
Hmm, yeah I was afraid of that.
Just thinking though, what could be defective? It works just fine on 2.3.2. If i run 2.3.4 (or 2.3.3) and start the phone, the Google-logo shows up in white for about 5 seconds, then it turns red and everything is red after that.
Click to expand...
Click to collapse
That's really strange. It seems that the update only is screwing things for you. Try sending supercurio a PM. He knows these stuff. He is the dev of the voodoo tweaks and application. He'll surely be able to answer you and give you an advise.
Sent from my Nexus S using Tapatalk
Eldrin, Have you finally found a way to fix it ?
Or are you stick in 2.3.2 ?
Red complexion on ICS
Did you find a solution to this problem?
When I turned on my Nexus S i9020 this morning all greyish colors where red. Directly after turning it on, the lock and the google writing where white as usual, but after about 2 second it got a red complexion. I tried to make a screenshot of my homescreen, but in the jpg the red complexion has vanished and it looks as usual.
I'm running ICS 4.0.3 stock and did the update back in december. Removing the battery for a minute didn't help.
Has anyone an idea?
EDIT: After about 5 restarts it was back to normal! Anyhow, I made a short clip of the startup sequence before www . youtube . com/watch?v=vy5NkFrQDuA
So I just got a Nexus S 4g on Monday and my dad and I already rooted the phone and have been trying different roms. He actually rooted it and swapped out the stock rom before I even knew I was getting it.
So with both of the roms I have tried, whenever i recieve an incoming call the speakerphone automatically activates and I have to manually turn it off.
We already tried reflashing the rom and we have also tried replacing a lib***.so file (forget which one) and neither fixed the problem. I cant find any sort of setting for this.
Anyone else having this problem? Is there a fix available that someone can guide me? Very new to Android so I'm still learning the tricks of flashing etc.
Just curious...did you test the phone before it was rooted.
Sent from my PC36100 using XDA Premium App
I received the phone on monday evening and my dad had the phone all day and routed it etc.
I never handled the phone with the stock rom. Its not too big a deal since I don't use it for much calling but a fix would be greatly appreciated.
Sent from my Nexus S 4G using XDA App
webhead1994 said:
I received the phone on monday evening and my dad had the phone all day and routed it etc.
I never handled the phone with the stock rom. Its not too big a deal since I don't use it for much calling but a fix would be greatly appreciated.
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
Well it seems like you don't know if this problem has always existed or if it is a result of flashing a custom rom. Best bet would be go back to completely stock and see if you still have the problem.
Sent from my PC36100 using XDA Premium App
Just flashed the new miui rom and it fixed the problem. Now I just have to redo my launcher lol.
Sent from my Nexus S 4G using XDA App
I'm having the same problem running a stock version of Android.
I started to have the same problem few days ago and my phone is all original stock, ,,
my wife just started experiencing this today. completely stock nexus s. we may try uninstalling the last few apps that had updates and see if we can trace it to one of those.
edit: are any of u using go sms (specifically version 3.66)? other users are complaining that recent update is causing this issue. im sending my wife a backed up version i have of 3.65 to see if its resolved
edit 2: rolling back to 3.65 did not resolve the issue, but rolling back to 3.64 did. good thing i have appmonster pro.....
I just started to have this problem today too. I did try to activate GoogleVoice yesterday but the calling issue did not begin until today. Running MATR1X v.6 and CM7 nightly #83. Didn't have this problem during stock.
Go sms's latest update is the culprit. The August 29 th update is responsible. Just uninstall that and put some other sms app.
Should solve it, It fixed my phone.
it happened to me twice yesterday, I answer the phone the screen went black and the sound routed to the speaker..can't go back to turn it off during the call as the screen has nothing. (stock rooted)...will uninstall GoSMSPro and see how it goes
If anyone needs/wants the 3.64 version of GO SMS, dm me you're email addy. (i'm assuming this would be ok on XDA since the app is FREE in the market?)
They (GoSMS) just released an update 3.66 to fix the problem
vennstrom said:
They (GoSMS) just released an update 3.66 to fix the problem
Click to expand...
Click to collapse
Its still exists on 3.66. My wife was using this version and it had the problem. We had to roll back to 3.64 before it went away.
u were right, Go SMS was the issue, they released an update today and solved the problem!
cheers everyone!
Glad I saw this thread... my G2 started doing this after not changing the ROM in months, at least now I know what caused it. I got my Nexus S yesterday and haven't answered any calls without the headset yet, lol, so I thought it was just my G2.
Anyone else having this? The time on my phone is reading incorrect by about 10 mins. I am using the stock clock widget and under settings it is set to use network determined time or somethingike that.
Any ideas?
Sent from my HTC One S using xda premium
Try selecting your city and country, i it desnt work you should probably just do a factory reset.
or just set the time manually...why HR just for that ffs?
I'm using ClockSync from the Play Store.
Sent from my HTC One S using XDA
I have got the same problem. Over the day the time gets an offset of around 3 seconds. After I had it on the charger over night (and ONLY if it was on the charger) the time of the phone is over 10 minutes behind the real time. I already disabled using the network time etc. but nothing helped. I don't think that this is a hardware failure.
I've got the same problem. Last night even my manually set time changed. Really strange.
Sent from my HTC One S using XDA
same problem here - seems to be related to charging over night, going to test.
any apps that have recently been updated that have permission to change time?
have tried rolling back google movies, will see if that helps.
also i would be interested to know if everyone is o2 (i am) - might be a problem with one of the o2 bloatware apps?
what seems to have sorted mine (for the time being) is just restarting the phone, very odd but seems ok at the moment
hpsauce37 said:
Anyone else having this? The time on my phone is reading incorrect by about 10 mins. I am using the stock clock widget and under settings it is set to use network determined time or somethingike that.
Any ideas?
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Network time also gives me an instant offset of ~10 min
I will try the manual setting, and see how that goes.
Might give a try at ClockSync, mentioned above.
Same problem here. I can adjust the clock, but whether I use the network time or not, after a few hours to a few days it's lagging behind by about 10 minutes. It's quite annoying.
customromfan said:
I'm using ClockSync from the Play Store.
Sent from my HTC One S using XDA
Click to expand...
Click to collapse
Thanks, I'll try that.
Automatic sync with that app needs root, I don't plan on rooting just yet - will probably make use of the warranty replacement because of the arc oxidation issue. Maybe the clock will work in the replacement.
no progress for me here, what an annoying bug.
reboot sets the time correct again but that's no fix!
following these steps it looks to me like a network time issue:
1. wake up with the clock 12mins slow
2. go into time settings and untick network time
3. set the correct time
4. retick network time and the clock jumps back to being wrong again
would really appreciate if anyone's got a clue on a fix
I've contacted HTC, they escalated it, I'll will forward their answer once I get it.
Sent from my HTC One S using XDA
Solution, probably)
Hi all! Also had this bug, until checked all boxes in Date&Time settings. Try to make all automatic. For me it solved problem.
Srem said:
no progress for me here, what an annoying bug.
reboot sets the time correct again but that's no fix!
following these steps it looks to me like a network time issue:
1. wake up with the clock 12mins slow
2. go into time settings and untick network time
3. set the correct time
4. retick network time and the clock jumps back to being wrong again
would really appreciate if anyone's got a clue on a fix
Click to expand...
Click to collapse
this is really strange - been staying at my girlfriends for a couple of weeks and not had this problem. so unless it a location problem (10mins walk), the only difference is ive been using a different charger overnight (htc vs kindle)
determined to figure this out
HTC told me that the update should help. For my part, it works now, although already before the update.
Sent from my HTC One S using XDA
doing the ota update now, was holding off but might as well try it.
hope it fixes
hi guys, any luck on the time issue? by girlfriend's phone is experiencing the same issue of being 10 minutes off
mine seems ok after the ota update
ota update?
I know this is an old thread but my wife is getting the error on a new HTC 1 s from bell. What is the its update and where do I get it?
Srem said:
mine seems ok after the ota update
Click to expand...
Click to collapse
Your too close too a black whole
Sent from my HTC One S using xda premium