Related
Scroll to the very bottom of this page and click "Vote for this issue and get email change notifications." RIGHT NOW to help get this issue fixed! http://code.google.com/p/android/issues/detail?id=9392
I have personally experienced this bug once that I can remember, and luckily for me it wasn't TOO big of a deal. I thought maybe it was a random, one time deal until I saw this post on Engadget. However, this bug is a lot more widespread than I thought.
The bug itself can be read about here: http://www.engadget.com/2010/12/31/android-still-has-horrible-text-messaging-bugs-thatll-get-you-f/
tl;dr:
1.Randomly, your phone may send a text message that you send to a contact to a random person on your contacts list with no warning.
2.Or, possibly less important, open the wrong text conversation when you try to open a text thread or open a text through via the notification bar.
Me personally, I've only experience the first issue that I listed one time. However, the second one happens often enough to annoy me, and enough that I double check every time I open a thread to make sure I'm talking to the right person.
My question is, is it possible for a dev (or multiple devs) to look in to this issue and fix it? Apparently it's only of "medium" importance as far as Google is concerned, but that's a bit ridiculous to me. People could literally lose their job or their marriages over something like this.
Also, IMO, this should be on the front page of xda..
EDIT: I'll also be posting this in the general Android forum since I think it needs more press.
hasnt affected myself.
using an htc sense ui, htc messaging app.
I have that issue with it openings the wrong thread. Didn't realize it was an OS glitch.
oohaylima said:
I have that issue with it openings the wrong thread. Didn't realize it was an OS glitch.
Click to expand...
Click to collapse
me neither
Bumping this, as it needs more attention.
Sent from my HERO200 using XDA App
Interesting. I did have an issue similar to this. It was in stock sense 2.1. I wanted to send a text to one contact, but it sent it to the last contact I had texted. Didn't know out was a universal bug.
Sent from my HERO200 using XDA App
I've noticed this since this first day I got my hero. I figured it was a glitch in the system or whatever. I just got used to it like you said, I check to make sure I'm talking to the right person.
Would be nice to have it gone tho if its an easy fix.
i cant say i have seen this issue, except the opening the wrong thread thing too
This doesn't happen on sense roms only stock mms.apk on aosp roms. I always double check cause it puts me in wrong threads all the time lol I failed once with a weiner pic to the wrong girl. It was very weird man very weird since then.
"I shave my armpits cause it makes me aerodynamic when i fight"
It appears the issue is now "critical" priority on Google's code page. Good! That's at least some progress..
I think Brett Favre is going to use this bug as his defense.
Step 1: Use Handcent
Step 2: ?????????????
Step 3: PROFIT!!!!!!!!
Okay, they could have handled this better, but the easiest way to fix it is to use some other app for a while. If Runkeeper doesn't work, I'll use Cardiotrainer for a while. Same concept.
Happened to me once.... I sent a nude picture to my GF and later that day it somehow got sent to another girl. Made an interesting conversation.
Anyways.... a flashable patch would be nice, if that is realistic.
An update! It appears an Android developer of some sort has posted saying the issue has been reproduced and fixed. You can read the comment here:
http://code.google.com/p/android/issues/detail?id=9392#c1460
"Thanks to everyone for your patience while we've been investigating these reports. As it turns out, we believe there are two distinct situations being discussed on this issue chain. Fortunately, we have fixes for both of them.
When some users tap to open a message in the Messaging application, they're seeing a different message appear instead. We don't believe this issue is affecting many users, but we've developed a fix that we're preparing to deploy. Of course, double-checking the displayed message before hitting "Send" will prevent any messages from being sent to the wrong recipients. We've found in testing this issue, it is more likely to occur if you tap on a message before the Messaging app is fully loaded, so we recommend waiting for all the elements to load before clicking on the message you want to display.
Separately, some users have reported that their SMS messages are being delivered to the wrong people. It took us some time to reproduce this issue, as it appears that it's only occurring very rarely. Even so, we've now managed to both reproduce it and develop a fix that we will deploy.
While we don't anticipate any persistent problems, we'll continue to investigate in case we come up with additional ways to trigger these bugs. Thanks again for helping us improve Android."
Hurray!
http://www.emccann.net/dho/3-Vanir-mirror/4-nighties/08-21-2013/
Here is a link to a great piece of work in progress.
This thread is DHO approved, I personally asked if I could post a thread sharing his work for the D4 and he gave me the go.
I went ahead and asked DHO if he could tackle development for this device as I feel the Droid 4 lacks in the development scene in comparison to most phones. Being that he's an awesome guy. without hesitation he took the challenge and within a day he has a working build.
It's the very very first build and his first time working on a device like this one so expect some minor and i mean MINOR bugs.
As each build is released you'll see improvements with each one, this guy does great work. In my opinion he has the best AOSP rom for the i605 which is the device I have. I had asked him to make this for my girlfriend as she owns the D4.
If you download, find DHO and thank him. If you like the work, donate. If you do not enjoy the work, move on silently but still hit that "thanks" button cause he still took time to make it or y'all.
If you guy's are thankful, hit "thanks"...after all I payed and am going to continue to pay him for building for this device. (He absolutely did not ask for money, I just felt it was right to do so considering he is investing his time into another device when he already builds for like 15 others)
Changelog(s) - http://d-h-o.us/home/?p=363
Link to DHO's profile - http://forum.xda-developers.com/member.php?u=2633294
Donate to DHO! - https://www.paypal.com/us/cgi-bin/w...63663d3faee8d48a116ba977951b3435308b8c4dd4ef1
Just to note, the very first build, it didn't have working hard keys but he may have fixed and reuploaded...if he hasn't he will...also if you guys install this please try your hardest to get him some logs
LOGS LOGS LOGS!
I assure you, if you get this man a log, the bug will be SQUASHED ASAP!
Could we possibly do a pure base PA3?
I've been trying to build out ParanoidAndroid3 and it doesn't work for me... Willing to my phone on the line as well...
Sent from my Maserati using XDA Premium
Is it possible to get some info on the ROM and maybe screenshots? I have never heard of Vanir and tried googling and for some reason got nothing?
Sent from my DROID4 using xda app-developers app
azrael293 said:
Is it possible to get some info on the ROM and maybe screenshots? I have never heard of Vanir and tried googling and for some reason got nothing?
Sent from my DROID4 using xda app-developers app
Click to expand...
Click to collapse
from what I found, it's a Gnex ROM ported over....
guess since I'm I flashaholic I'll nandroid my 4.3 nightly and try it...
will report back shortly.
UPDATE:
What doesn't work
Wi-Fi
Hardware Keys
Soft Home Key
Dialer (Phone)
after phone dialer didn't work I stopped testing....
Hope this helps everybody who was curious about this 'mystery' ROM
If you want to play with it make sure you flash in Slot-1.. it is Kexec
je2854 said:
from what I found, it's a Gnex ROM ported over....
guess since I'm I flashaholic I'll nandroid my 4.3 nightly and try it...
will report back shortly.
UPDATE:
What doesn't work
Wi-Fi
Hardware Keys
Soft Home Key
Dialer (Phone)
after phone dialer didn't work I stopped testing....
Hope this helps everybody who was curious about this 'mystery' ROM
If you want to play with it make sure you flash in Slot-1.. it is Kexec
Click to expand...
Click to collapse
Vanir/Commotio is a team that started building for Gnex initially, it's not a port.
Wifi does work, try a reboot or go into terminal , type su, then wifical.sh
the rest you are correct about.
I will try to get screen shots and maybe more info when I have more time
Sent from my SCH-I605 using Tapatalk 2
Another maserati build is up for 8/22
For you people who are running or even just trying, if you experience any bugs please do your best to get a log. LOGS LOGS LOGS!
I assure you that DHO will work on fixes and squash them bugs if you get him a log...it is hard for me to get logs for this device as I don't own it my girlfriend does and she isnt always able to let me tinker with it so please get logs for us to get a better well rounded rom.
I am pretty sure this will be the fastest and most buttery rom for this phone if we all work together and get DHO logs of bugs we occur
http://www.emccann.net/dho/3-Vanir-mirror/4-nighties/08-22-2013/
download that baby!
Has anyone else tried this. Curious as how its working. Screenshots maybe?
Sent from my XT894 using xda app-developers app
Just tried out the 08/22 build.
My observations:
Like the look and feel. Pretty quick in the limited amount of time I tested. Lots of mods/customization options. Keyboard works just fine. Hard keys are not working but can work around using pie control. More interesting is auto-rotate IS working. Last I checked this was still not working on CM10.2. Did not get a chance to test wifi and, like je2854 said, the dialer is not working. Doesn't force close, just brings up blank screen.
So, still some bugs to be worked out but a pretty solid start. Looking forward to seeing how this progresses. Thanks DHO and ahjee.
P.S. I tried to take a screen shot but the power button + volume down did not work. Is there a different way of taking screen shots in 4.3 or is this just a bug?
kwyrt said:
Just tried out the 08/22 build.
My observations:
Like the look and feel. Pretty quick in the limited amount of time I tested. Lots of mods/customization options. Keyboard works just fine. Hard keys are not working but can work around using pie control. More interesting is auto-rotate IS working. Last I checked this was still not working on CM10.2. Did not get a chance to test wifi and, like je2854 said, the dialer is not working. Doesn't force close, just brings up blank screen.
So, still some bugs to be worked out but a pretty solid start. Looking forward to seeing how this progresses. Thanks DHO and ahjee.
P.S. I tried to take a screen shot but the power button + volume down did not work. Is there a different way of taking screen shots in 4.3 or is this just a bug?
Click to expand...
Click to collapse
have you used the Xposed Modules for 4.3? it works without fail.
another nightly was released for you guys yesterday...check it out and get some logcats please, DHO can't fix the bugs for this device if the users don't report bugs to him and log cats help so much as it basically points out in the log what is going wrong so he can go through and fix...i know i sound like a broken record but I'd like for him to get as much info as he can cause the end result will be a buttery smooth, fluent, stable and well performing rom!
je2854 said:
have you used the Xposed Modules for 4.3? it works without fail.
Click to expand...
Click to collapse
can you link me to a working xposed module for framework for 4.3? the one i used for my Note 2 does not seem to work for my girlfriends D4...
Would it be possible that HDMI will work for us?
HDMI is the only reason why I have a stock based rom.
Nightlight 27/08, dialler and soft key not work
ahjee said:
can you link me to a working xposed module for framework for 4.3? the one i used for my Note 2 does not seem to work for my girlfriends D4...
Click to expand...
Click to collapse
umm, If I cannot find the link I will post as an attachment (sorry for the original poster if they see this)
Thanks for reporting the bugs you guys experience, I have relayed the bug list over to DHO for him to work on...He will get the hard keys working, this whole time he thought i meant the keyboard so he kept trying to get that to work when they already had haha, now the he knows we mean the hard keys such as Menu, Home, Back and Search i bet the next nightly or two will have them working without doubt...the others may or may not be done next build but soon enough
I appreciate the feed back but guys please try to get log cats via an app in the market or using ADB please, it allows him to see whats going on within the build and why things arent working...
expect new builds with bug fixes real soon.
Problems still found in the night 09.05.2013:
- Buttons (Menu, Home, Back and Search) do not work
- Dialer does not work (hangs when pressing any number)
- Virtual keyboard appears even using the physical keyboard.
does 3g work on this rom im trying to find a 4.3 rom that 3g actually works I cant get it at all on the 10.2 nightly
ahjee said:
Thanks for reporting the bugs you guys experience, I have relayed the bug list over to DHO for him to work on...He will get the hard keys working, this whole time he thought i meant the keyboard so he kept trying to get that to work when they already had haha, now the he knows we mean the hard keys such as Menu, Home, Back and Search i bet the next nightly or two will have them working without doubt...the others may or may not be done next build but soon enough
I appreciate the feed back but guys please try to get log cats via an app in the market or using ADB please, it allows him to see whats going on within the build and why things arent working...
expect new builds with bug fixes real soon.
Click to expand...
Click to collapse
No more updates?
I've been running into Daydream problems in conjuction with Xposed Installer. Specifically with Clock plus DayDream by @martinpelant.
You can find all the information I was able to gather here: http://forum.xda-developers.com/showpost.php?p=54258696&postcount=31
As I think this is more a problem of that app I posted the information there. However, when I uninstalled Xposed Framework (that is to say the patches to the system, not the Installer nor the applications that use Xposed) the problem was also gone. Before that step I also tried unselecting ALL Xposed modules and rebooting, deactivating them, uninstalling, etc, etc. As I said the app began working correctly after uninstalling Xposed Framework and problem arose again upon installing the Framework. I must also mention that this problem only happen when using Clock plus Daydream as I tested with other "daydream" apps and they work properly.
In the aforementioned post you will find catlogs, a video and some other information that might be useful.
PS: I repurposed this post as I first posted the problem here before realizing the culpruit was Clock plus
J_M_V_S said:
I've been trying to solve this for the last couple of days. I'm not certain that this is an Xposed bug/problem but seems to be the most likely and that's why I post this here.
Click to expand...
Click to collapse
This looks like a short wakelock to me. As Xposed doesn't use any wakelocks, it seems unlikely that it's the culprit. I obviously can't speak for all the modules, so you should try if it still occurs if you disable them. Or even easier: Just press the uninstall button in Xposed Installer and reboot. If it still occurs, you can be sure that it's neither Xposed nor any module.
rovo89 said:
This looks like a short wakelock to me. As Xposed doesn't use any wakelocks, it seems unlikely that it's the culprit. I obviously can't speak for all the modules, so you should try if it still occurs if you disable them. Or even easier: Just press the uninstall button in Xposed Installer and reboot. If it still occurs, you can be sure that it's neither Xposed nor any module.
Click to expand...
Click to collapse
I'm really sorry @rovo89. I was in the middle of this post when I was able to find the problem. Somehow it seems I pressed the Post button on the unfinished post. Really sorry about that. The problem was (is) on Clock Plus Daydream. I will repurpose the OP as Xposed might still be somewhat responsible.
For some odd reason, App Locale is not working on Nougat. I think it is based of @rovo89 module of App Settings so can you please @rovo89 update you App Setting module so we can change the language of specific apps? I really need it for my day to day. Thank you.
riahc3 said:
For some odd reason, App Locale is not working on Nougat. I think it is based of @rovo89 module of App Settings so can you please @rovo89 update you App Setting module so we can change the language of specific apps? I really need it for my day to day. Thank you.
Click to expand...
Click to collapse
Yep, I'm looking for this on Oreo, as well. Doing an initial search, it looks as though Google changed the way locales work in Nougat/Oreo APIs, but I don't know enough about Xposed development to be any use in trying to fix it...
bobertfishbone said:
Yep, I'm looking for this on Oreo, as well. Doing an initial search, it looks as though Google changed the way locales work in Nougat/Oreo APIs, but I don't know enough about Xposed development to be any use in trying to fix it...
Click to expand...
Click to collapse
I dont blame @rovo89 per say for it because like you said, it is documented that locale settings changed in Nougat but App Settings has a great proof of concept for other devs to learn a bit about Xposed so it would be nice if he updated it.
Hi,
As @bobertfishbone said, Google changed the way locales work. So I forked the repository and added Nougat & Oreo compatibility.
Here is the link to the git: https://github.com/Flo354/XposedAppLocale
I also made a PR but I don't have much hope for it being reviewed, the project has no activity: https://github.com/jiefoxi/XposedAppLocale/pull/14
Man, I'd LOVE to have a working App Settings on Oreo and Nougat.
App Settings:
https://forum.xda-developers.com/xposed/modules/mod-app-settings-v1-9-2014-05-14-t2437377
The app development stopped years ago.
And if app specific notification capabilities could be added to it, that would be icing. Total control of app notifications, size, etc. etc. etc.
Take my donations now!!! $$
Flo354 said:
Hi,
As @bobertfishbone said, Google changed the way locales work. So I forked the repository and added Nougat & Oreo compatibility.
Here is the link to the git: https://github.com/Flo354/XposedAppLocale
I also made a PR but I don't have much hope for it being reviewed, the project has no activity: https://github.com/jiefoxi/XposedAppLocale/pull/14
Click to expand...
Click to collapse
Just got back into the country and got the chance to try this out--it works perfectly! Thanks so much for sharing.
I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community
Requirements:
- twrp 3.2.0+
- backup everything before install
- wipe data before upgrading from LineageOS 14.1 or stock rom
Install:
- Flash zip in TWRP
- Don't forget about gapps (arm 8.1)
Google apps should be installed via recovery immediately after installing ROM.
If you reboot into ROM before installing Google apps, you must factory reset and then install them, otherwise expect crashes.
Known issues:
unstable fingerprint
stuff, I haven't checked
Download:
T810: https://drive.google.com/open?id=1LlC7jBfq3H9FuPKZeKdQ3KyuiglgJTYv
T815: https://drive.google.com/open?id=1ZXg6Oy_aSfYL4XoXovfPzQ9pZqD1XVmw
Device sources:
https://github.com/bonuzzz
Yeah! Thanks for all the work.
I flashed the rom (t810) but the orientation is upside-down: not easy to press the right buttons :laugh:
So I couldn't really test it further.
halloarno said:
Yeah! Thanks for all the work.
I flashed the rom (t810) but the orientation is upside-down: not easy to press the right buttons :laugh:
So I couldn't really test it further.
Click to expand...
Click to collapse
do you mean the orientation of touch sensor?
bonuzzz said:
do you mean the orientation of touch sensor?
Click to expand...
Click to collapse
Screen is upside-down (orientation sensors are OK). And screen touch sensitivity is normal. So I see a button in left up corner and have to touch in right down corner where it actually has to be.
halloarno said:
Screen is upside-down (orientation sensors are OK). And screen touch sensitivity is normal. So I see a button in left up corner and have to touch in right down corner where it actually has to be.
Click to expand...
Click to collapse
I will upload proper build tomorrow. Thanks for bug report!
Boom. Been waiting for 8.1 for 815 for ages. Thanks for your work can't wait to see how this progresses!! ?
bonuzzz said:
I will upload proper build tomorrow. Thanks for bug report!
Click to expand...
Click to collapse
Congratulations bonuzz very happy to hear your success thanks a lot for your work
Ok one more thing can I use your work to build a different os please man?
( seem to be blind (or stupid) - Can someone please point me to a working TWRP 3.2 for the T810 so I am ready when the new build drops? Thanks a bunch!)
Edit: Sorry, found it. Stupid indeed.
I fixed drm stuff, so netflix is working now. I want to fix some small things before uploading new build, but I'm not sure I finish and make new builds today. @Androbots feel free to use all code from github
I suspect that the display is rotated 180 degrees because there are one too many hwrotation=270 entries between the gts2-common and gts210 device trees. I'm running my own build right now with all those extra ones removed, including having taken out the system_prop.mk file from the gts210wifi repo, since it's identical to the system.prop file already there. Out of respect for bonuzzz, I won't post my own build in this thread.
For those wondering, the official 3.2.1 TWRP works perfectly fine.
bonuzzz, I haven't tested your build yet, but if you managed to fix wifi and bluetooth, I take my hat off to you sir
ripee said:
I suspect that the display is rotated 180 degrees because there are one too many hwrotation=270 entries between the gts2-common and gts210 device trees. I'm running my own build right now with all those extra ones removed, including having taken out the system_prop.mk file from the gts210wifi repo, since it's identical to the system.prop file already there. Out of respect for bonuzzz, I won't post my own build in this thread.
For those wondering, the official 3.2.1 TWRP works perfectly fine.
bonuzzz, I haven't tested your build yet, but if you managed to fix wifi and bluetooth, I take my hat off to you sir
Click to expand...
Click to collapse
Only t810 and t815 require rotation, so this parameter is in device specific config only. And if you have several strings it doesn't mean the image on display will rotate each time. It is just duplicate string.
Why not you finally create your own thread for your builds? I think it will be good idea:good: You have link to your builds in your signature, but you don't have any place where your users can ask you for help...
Nice to see U back @bonuzzz, especially with such amazing things ?
As always, I keep my fingers crossed for U and Ur great things for Android community. Keep on and NEVER give up! Thx for all ur efforts ?
bonuzzz said:
Only t810 and t815 require rotation, so this parameter is in device specific config only. And if you have several strings it doesn't mean the image on display will rotate each time. It is just duplicate string.
Why not you finally create your own thread for your builds? I think it will be good idea:good: You have link to your builds in your signature, but you don't have any place where your users can ask you for help...
Click to expand...
Click to collapse
Because right now my builds are in worse shape than yours, assuming you fixed wifi, bluetooth, the 180 degree display rotation, and everything else in your OP.
Edit: If the gts210vewifi is anything to go by, Oreo requires an hwrotation of 90, not 270 as in Nougat, for the proper orientation, courtesy of luk1337.
Voytec83 said:
Nice to see U back @bonuzzz, especially with such amazing things
As always, I keep my fingers crossed for U and Ur great things for Android community. Keep on and NEVER give up! Thx for all ur efforts ?
Click to expand...
Click to collapse
Go away, spammer
ripee said:
Because right now my builds are in worse shape than yours, assuming you fixed wifi, bluetooth, the 180 degree display rotation, and everything else in your OP.
Edit: If the gts210vewifi is anything to go by, Oreo requires an hwrotation of 90, not 270 as in Nougat, for the proper orientation, courtesy of luk1337.
Click to expand...
Click to collapse
I have the same behaviour in tab s3, but I thought it is because of libs from another device. But it's very funny, in oreo rotation is in another side)
PS: I mean not only oreo builds...
Yup, setting hwrotation to 90 instead of 270 fixes the display being flipped. As for wifi and bluetooth, I will patiently wait for your expertise, bonuzzz
ripee said:
Yup, setting hwrotation to 90 instead of 270 fixes the display being flipped. As for wifi and bluetooth, I will patiently wait for your expertise, bonuzzz
Click to expand...
Click to collapse
bt issue is just permission issue net_bt_stack --> bluetooth in init scripts
for wifi fix you will wait very very long time...
To be honest, I don't want to collect again the guys, who just "patiently waiting" for new commits from my side and fully depended from my work. Users will have cloned roms with same issues.
bonuzzz said:
bt issue is just permission issue net_bt_stack --> bluetooth in init scripts
for wifi fix you will wait very very long time...
To be honest, I don't want to collect again the guys, who just "patiently waiting" for new commits from my side and fully depended from my work. Users will have cloned roms with same issues.
Click to expand...
Click to collapse
So why make the effort to build again? This is the same old story with you. One day, you are helpful and generous with your builds; the next day, you complain about not wanting to make any more effort than you had already made.
Please make a decision and stick with it: either do your best to fix the most basic functions and let someone like me help you the best way I can by building from your code often, and giving you full credit, so that we can all give you frequent feedback, or don't create any more threads and abandon the 2015 Tab S2.
widevine L1 support added. we dont need patched netflix apks anymore
@ripee I make roms for myself and share them with others. What's wrong with that? And yes, I'm helpful and generous when you write me pm. Just curious, nobody asked for help in public. And yes, everything is depends on my spare time.
Nougat builds are really abandoned. You don't believe me or what? Or I should to write anything else there when people ask for update builds?
I see you worry about my git. Calm down, please. Why do you think I upload sources for you? I uploaded sources for you and you published your builds just right after that without understanding what exactly changed and instead of help to fix remain bugs. I told you few months ago to choose one author and try to fix something. You didn't hear me. I don't need any credits. But I don't like liars, if we talk about one person here. And I don't want more "we don't care" teams here. I don't need any daily public builds. It will be disorganized development. At least no one else haven't tried to fix anything in my (nougat) sources...
So, in short, I will do what I want. I will upload builds when I want. I will add/fix/change in builds what I want and in my own priority. I spend my own time for that. Don't like? Don't use. Make something yourself. Stop depend from me and let me do my work. Thanks in advance.
I just saw Shiny thread here ^-^ . I look twice to make sure it is 815 not anything else.
Thank you very much. We all appreciated your work and effort.
If you want any help test, logcat or even setup machine for build I'm ready for that ^-*
bonuzzz said:
I fixed drm stuff, so netflix is working now. I want to fix some small things before uploading new build, but I'm not sure I finish and make new builds today. @Androbots feel free to use all code from github
Click to expand...
Click to collapse
Thanks a lot. Appreciate your work for our Tab S2. Have a good day mate?