A popup just showed on my screen telling me that the phone just created a bug report. It sent the report to my mail. Since I am experiencing a lagging issue and have seen that numerous others are experiencing it too, I though this might be helpful if any dev can help out by this bug report.
The subject says:
p1_tmo_us-user 6.0 MRA58K 1603210524c8d release-keys
I think I can not attach files here (I tried). If anyone is interested I can send it to them in person.
Related
Hi all. So I have an unlocked Tattoo which I created a goldcard and successfully flashed thanks to the excellent advice from people on this forum.
However, there is one thing that frustrates me about it. And that is the timestamp on SMS messages. There is an update for the HTC Magic which solves this problem but I have been unable to find one for the Tattoo. Does anyone have a solution to this?
Thanks!!
Whats wrong with your timestamp?
motherconfessor said:
Hi all. So I have an unlocked Tattoo which I created a goldcard and successfully flashed thanks to the excellent advice from people on this forum.
However, there is one thing that frustrates me about it. And that is the timestamp on SMS messages. There is an update for the HTC Magic which solves this problem but I have been unable to find one for the Tattoo. Does anyone have a solution to this?
Thanks!!
Click to expand...
Click to collapse
without further info, we can't confirm this issue, it could just be your software revision loaded on the device...
Whenever I get an incoming text the timestamp says it is 4 hours earlier than the time I received it. Yet my sent texts have the right timestamp, so my thread is all messed up. All my received texts are at the top and all my sent texts are at the bottom.
I am not sure what details you want but my software version is 1.67.4 on the Rogers network.
What I have been experiencing is that it seems like the incoming timestamp is set somehow by the sender's carrier. Im saying that because I usually receive texts from people on 3 different carriers and only one of them has this problem. So I do not really bother about it.
yash08 said:
What I have been experiencing is that it seems like the incoming timestamp is set somehow by the sender's carrier. Im saying that because I usually receive texts from people on 3 different carriers and only one of them has this problem. So I do not really bother about it.
Click to expand...
Click to collapse
True true. I've noticed the same. It seems like a problem with the senders operator not setting the correct time.
This could actually be an Android-wide thread but since I'm experiencing it on the Galaxy S I figured I'd post it here.
I'm currently experiencing the trouble with the Galaxy S on KPN that, even though it asks for a delivery report I never receive one.
I've done some Google'ing around and it turns out that KPN, much like O2 in the UK (apparently) use a different kind of SMS gateway that has an alternative method of delivery reports implemented the Messaging application just doesn't seem to support.
There are a few tricks around like starting your SMS with a special code that will actually give you a delivery report but having to type *0# in every message you send is just a workaround that really shouldn't be needed in the first place.
I was wondering if anyone has an SMS app around that support an 'alternative' delivery report method or allows for a few chars to be inserted automatically, anything to just get those reports working?
Also, does anyone know how to tell the Galaxy not to cut off a longer SMS with the (More...) thing but just display the whole thing? It's god damn irritating.
Apparently Android has a known bug on how it deals with delivery reports. More information can be found here:
http://code.google.com/p/android/issues/detail?id=2305
(Not sure if the problem you describe is the same as in this bug.)
Thanks, that is indeed the bug I was having.
Strangely enough, delivery notifications did work on my HTC Hero with a Froyo AOSP ROM on it....
It seems it has actually been fixed in a froyo build so it might just make it to the official Samsung 2.2 update if they pull in the sources. Who knows, would be awesome if this worked/
I'm having the opposite problem (Froyo 2.2 JPO on Galaxy S i9000 16GB).
When I send an sms (delivery notification is on) in most cases, I'll get two notifications... (maybe I'm getting yours as well )
I've had this problem on 2.1 as well but not so often. Seems like it's worse on 2.2...
When I receive a text. It doesn't show up but there is a new blank message from 5556. What's that about? Anyone else having this issue? I have not begun troubleshooting.
kelbizzle said:
When I receive a text. It doesn't show up but there is a new blank message from 5556. What's that about? Anyone else having this issue? I have not begun troubleshooting.
Click to expand...
Click to collapse
Itz the mac user trying to hack youu
solution: turn off bluetooth
It can be also that when you first time boot to cm it activated your 3g, maybe it is sign of it.
I am experiencing this now too. But I'm on a Samsung Captivate. Rooted, but no custom ROM or anything.
I've also come across one other person experiencing it on an HTC Desire:
http://androidforums.com/desire-support-troubleshooting/192806-sms-mms-issue.html
Hopefully someone has an idea.
"Blackbook" app was causing this issue.. Uninstall it!
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.