Hey guys, I'm having a SMS timestamp issue since rooting and installing SenseUI rom and CM rom.
Note, this did -not- happen on the stock n1 rom. I'm currently in China using China Mobile so I haven't been able to test this back in the states (TMobile) yet.
Basically, when I send a message to anyone (android, iphones, etc), their received timestamp of my message is 7-8 minutes in the past. Obviously this is quite the annoyance for threaded messages on smartphones. I can replicate this by sms'ing my own phone and the timestamp of the received message is 8 minutes before I sent it.
I've tried everything I can think of. I've even nandroid restored my original backup and the issue is still happening. I've turned on/off the "get time from network" settings, updated radio and redowngraded, tried 3-4 different roms, but nothing is working.
Anyone seen this before or have any ideas? Frustrating the hell out of me!
anyone have any ideas?
1) There is known bug/problem in Galaxy S with eclair 2.1 that USSD code stops working after some time in . I faced this problem for many days and was unable to use some GSM services like balance checking etc. I did not find any solution for it on internet.
Luckily, I was able to pin point the cause which was creating the USSD problem and just want it to share so that your time can be saved.
I observed the mobile tracker is causing the problem. As soon as I turn it off USSD works fine. When the mobile tracker is On then USSD is screwed up again. I am sure there may be other apps which can cause similar problems ... please share if u find any...And of course all galaxy S users..please confirm if the mobile tracker is casing issue in your phones as well??
2) Edit Update - For those who find "Mobile Tracker" is not the root cause --
Backup your important data.
You have to do a clean install / Factory RESET once again... try to isolate the problem causing app by installing the apps one by one and checking the USSD code functioning...for me it was mobile tracker on galaxy s Android 2.1 .....
I know this is quite tiresome work when you want lots many apps on your device...
But then you have to make a choice.
3) USSD code error when i do a speed dial..
Please hold speed dial digit for few seconds instead of using # then number OR number then call...
I have the same issue and I really don't know what's causing it. However when I put the SIM from an older contract (same carrier) USSD codes work.
However with the sim/contract I got the phone with, I get the following error "You don't have access to this service".
Might be related to the fact that the contract isn't fully activated or something like this
USSD Balance Check Problem Solved / Solution.
Samsung Galaxy S I9000 USSD command output problem solved, thanks to Ravi4Chahal.
Problem:
when i run my balance checking command *124# the USSD command executes but no output displayed,
Solution:
I disabled the mobile tracker in Settings -> Location and Security -> Mobile Tacker -> Disable
I too had a similar problem that I was only able to solve disabling Mobile tracker.
Does anybody know of a way that we can keep the mobile tracker on?
Its really a great tool in case your phone gets stolen
Thanks a lot,
I have samsung i5801 i just switched off the mobile tracker, now i can check the balance and also it shows the balance after the call is ended.
But the mobile tracker is a good utility wat should i do make both work properly.
thanks ravi4chahal, i'm able to run ussd codes now.
but still, i'm not getting "last call charge" message
Vodafone India
I recently upgraded to leaked Froyo 2.2 XXJPH, it seems USSD problem is resolved in this version. USSD code running fine along with mobile tracker at the same time.
Cheers!
Thanks Ravi! I was also facing the same problem but wasnt able to figure as to what was causing the problem. Now I can atleast check my balance by disabling the Tracker temperorily.
Samsung Galaxy S: Mobile Tracker is the problem indeed! I was wondering why I couldn't check my balance any longer... Thx!
Since Froyo seems to fix the issue, all we have to do is wait
USSD Code in Galaxy S
Indeed Tracker is the key problem to run USSD code in Galaxy S. Hope Froyo will solve the problem soon.
Thanx Guys. Problem Solved. Been wondering about it since i bought my phone 3 months back.
ravi4chahal said:
There is known bug/problem in Galaxy S that USSD code stops working after some time. I faced this problem for many days and was unable to use some GSM services like balance checking etc. I did not find any solution for it on internet.
Luckily, I was able to pin point the cause which was creating the USSD problem and just want it to share so that your time can be saved.
I observed the mobile tracker is causing the problem. As soon as I turn it off USSD works fine. When the mobile tracker is On then USSD is screwed up again. I am sure there may be other apps which can cause similar problems ... please share if u find any...And of course all galaxy S users..please confirm if the mobile tracker is casing issue in your phones as well??
Click to expand...
Click to collapse
Hello,
Can you help me to solve the same problem in Samsung GT-i5503, because there is no option of Mobile tracker to disable.
Thank you in advance.
Nodirbek
yes , so is m110s, no mobile tracker
You have to do a clean install / Factory RESET once again... try to isolate the problem causing app by installing the apps one by one and checking the USSD code functioning...for me it was mobile tracker on galaxy s Android 2.1 .....
I know this is quite tiresome work when you want lots many apps on your device...
But then you have to make a choice
I do not have mobile tracker
in my samsung galaxy fit i have same problem, but my setting does not have tracker.
Any suggestion?
hello all
i am facing the USSD code error when i do a speed dial.
after reading here i see my mobile tracker isant marked even wich means it is not working and disabled but i still have the error.
if i try to mark under mobile tracker wich is Set mobile tracker it asks me for a password.
the mobile tracker it self is grayed out and it says i need to log into my samsung account in order to use it.
so mobile tracker is not working and still have the error what could this be ?
would love to fix this using speed dial allot
If it isn't "Mobile Tracker" then it must be some other app causing the issue. Backup your important data and do factory reset. Most probably it would solve the problem.
ravi4chahal said:
1) There is known bug/problem in Galaxy S with eclair 2.1 that USSD code stops working after some time in . I faced this problem for many days and was unable to use some GSM services like balance checking etc. I did not find any solution for it on internet.
Luckily, I was able to pin point the cause which was creating the USSD problem and just want it to share so that your time can be saved.
I observed the mobile tracker is causing the problem. As soon as I turn it off USSD works fine. When the mobile tracker is On then USSD is screwed up again. I am sure there may be other apps which can cause similar problems ... please share if u find any...And of course all galaxy S users..please confirm if the mobile tracker is casing issue in your phones as well??
2) Edit Update - For those who find "Mobile Tracker" is not the root cause --
Backup your important data.
You have to do a clean install / Factory RESET once again... try to isolate the problem causing app by installing the apps one by one and checking the USSD code functioning...for me it was mobile tracker on galaxy s Android 2.1 .....
I know this is quite tiresome work when you want lots many apps on your device...
But then you have to make a choice.
3) USSD code error when i do a speed dial..
Please hold speed dial digit for few seconds instead of using # then number OR number then call...
Click to expand...
Click to collapse
ravi4chahal said:
If it isn't "Mobile Tracker" then it must be some other app causing the issue. Backup your important data and do factory reset. Most probably it would solve the problem.
Click to expand...
Click to collapse
I have a similar problem with my GT I9008L. I tried all solutions but no change. I think it's probably due to the fact that the phone is from china and its firmware csc is solely china while i am outside china. Can anybody help me there? Many thanks.
Hey, I got my Xiaomi Mi5 a little over a week ago and recently noticed that a few times a friend has sent an SMS and I have not received it. Unfortunately I am unable to replicate the problem.
I'm wondering if anyone else has had this problem and managed to fix it?
I am currently on MIUI version 7.2.4.0.0 (MAACNDB) <-- Installed by vendor but I'm not sure if that could be causing the problem. I have not switched yet as it would ruin any chance at returning the phone.
I have made a switch back to the default SMS app (I was using Google Messenger) but am not sure if this has fixed the problem yet.
Any help regarding the issue or speculation if this is a hardware or software problem would be appreciated.
Thanks
Hi, I am having the same issue.
Did you find a solution?
Thanks
Hello Mandy,
I'm emailing back because of the issue with the bluetooth.apk. I notice on the new firmware (May 25) they completely took away the actual bluetooth selection in settings and made it completely dependent on the bluetooth.apk your company created. This would be ok, however the application doesnt allow you to connect OBD2. Especially since the device (OBD2) doesnt allow you to change the password/pin. It keeps saying that the device has disconnected.
Also, it would seem as though that the bluetooth.apk doesnt send ANY information back to the phone to tell it to start a call. This is suppose to happen. I should be able to dial a number through the bluetooth.apk or even through "Ok Google" command and it send the information to the phone but it doesn't. Also, there should be a text messaging app that is similar in the process except it should depend solely on our voices to type the message and send via bluetooth to our phone and then send to the contact. This would be a true hands free app that everyone is looking for.
The Bluetooth app should be getting contact updates from google sync contact but some how this has been a problem since day one, but never addressed. I'm going to go ahead and post this in the forum.carjoying.com forums, but also post it to xda-developers.com forums to see who else is having these issues. I was actually not happy when I found out the new rom update (25may2017) had more issues that the last firmware update.
-----------------------------------------------------------------------
Ok guys, I know that there is a modded bluetooth apk someone is passing around, however that app keeps causing me to have feedback problems. When making a call, the receiver gets loud feedback on their end.
If would be awesome if I could get a lot of you to email in if you havent already about the bluetooth.apk. It sucks and needs to be fix. Let me know if I should have done something different. Thanks.
Hello,
I just installed LOS 15.1 on a friend's Nexus 6, using the latest official build and the pico-OpenGAPPS to get the play store working. Now My friend is experiencing delays in receiving messages in Threema: some time messages arrive hours after they were written, some times they won't be received until the app is opened manually. Some times, though, messages do arrive right after they have been sent.
No settings have been altered after the installation and no options have been fiddled with, and this behaviour is quite annoying. A messenger service that takes hours to receive messages is not quite what it is supposed to be.
There's an option in Threema's menu to renew the push token, thus re-registering with GCM. But doing so does not solve this problem. We already checked the other options that Threema mention in their FAQ.
Is there any thing that can be done to get rid of this delays? Did I use the wrong GAPPS? Do I need to install the nano version instead of pico? Does any one else have the same problem?
Thanks in advance for any help and clue.
Try disabling battery optimization for the app.
That option was already set to no optimising.
Problem solved by completely reinstalling LOS from scratch.