Related
*There have been reports that this does not work on 6.5 roms. Please use at your own risk.*
Cab below!
It's discussed in this thread: HERE
Turns out its an issue with the htmlnote.dll file.
Thanks to all the help from everybody!
Cab replaces htmlnote.dll in the Windows directory with a friendlier one.
Both SMS and email work!
This has been a recent problem that's come up in many different threads but I still have yet to find a solution.
When selecting a message from the message tab in M2D the message is highlighted and you have to manually tap on the text box to start typing.
It's much easier to select the message and just start typing right away.
Is there a fix for this yet that I just can't find?
loserskater said:
This has been a recent problem that's come up in many different threads but I still have yet to find a solution.
When selecting a message from the message tab in M2D the message is highlighted and you have to manually tap on the text box to start typing.
It's much easier to select the message and just start typing right away.
Is there a fix for this yet that I just can't find?
Click to expand...
Click to collapse
I've been looking as well, and I haven't come across anything.
Why you open this thread addition?
I've seen it within many different ROM's threads with no final answer or fix. I thought I'd try to collect it into one place since I know there are many different people with the same situation.
I have this bug to all of my roms and if you have this bug also if take from same contact more than 1 sms and you go to read it become "read it" only the final sms and the other 2 or 3 or more new sms from this contact stay "unread it" you must tap on sms to become "read it"
i searching for this bug if found something i will post it here..
also i have problem with power button issue
also perlyp have this 2 issue and chef of PDACorner..
I have the same problem. Also if I have an SMS thread open while receiving messages to the conversation. It does not mark them as "read" I have to open the conversation for each message received. If I have 4 SMS messages from the same number I should be able to open it once and have all messages marked as read in that conversation.
theres a temp fix for the unread sms issue. if u search for unread sms fix (i think thats what its called) ull find an exe that will fix that issue. u have to run it every time it happens but like i said its a temp fix. Ill post a link or the file when i get home.
loserskater said:
theres a temp fix for the unread sms issue. if u search for unread sms fix (i think thats what its called) ull find an exe that will fix that issue. u have to run it every time it happens but like i said its a temp fix. Ill post a link or the file when i get home.
Click to expand...
Click to collapse
thanks i found it. this site is great, filled with all kinds of info but sometimes it is hard to find.
**a side note the fix you suggested also fixed the original issue in this post.
why you so lazy
I think its just the problem with cooking process (you know blending sys and oem packages and stuff like that!). Some of the ROM's here do have that problem. Usually G's tend not to, but it all depends on the flavor of the day!
kwoodyusa said:
thanks i found it. this site is great, filled with all kinds of info but sometimes it is hard to find.
**a side note the fix you suggested also fixed the original issue in this post.
Click to expand...
Click to collapse
Do you have the actual link and program??
kwoodyusa said:
thanks i found it. this site is great, filled with all kinds of info but sometimes it is hard to find.
**a side note the fix you suggested also fixed the original issue in this post.
Click to expand...
Click to collapse
I tried that fix but the original problem still happens whenever i get a new message
rush242 said:
Do you have the actual link and program??
Click to expand...
Click to collapse
here it is
Thanks to rsw686 and stylez this bug is finally fixed!
Works perfect!
Thanks!
loserskater said:
FINALLY SOLVED!!! Thanks to rsw686 for the file and stylez for the cab!
Cab below!
It's discussed in this thread: HERE
Turns out its just a missing dll file. Kind of strange IMO but oh well, it works!
This has been a recent problem that's come up in many different threads but I still have yet to find a solution.
When selecting a message from the message tab in M2D the message is highlighted and you have to manually tap on the text box to start typing.
It's much easier to select the message and just start typing right away.
Is there a fix for this yet that I just can't find?
Click to expand...
Click to collapse
Loserskater, what app are you using for sms that this apply's to?
TW,
That fixed the SMS issue for me, however it seems to have broken e-mail. The read/unread icon doesn't display, and I can't open any e-mail or start a new message. Any ideas?
Sunookitsune said:
That fixed the SMS issue for me, however it seems to have broken e-mail. The read/unread icon doesn't display, and I can't open any e-mail or start a new message. Any ideas?
Click to expand...
Click to collapse
Funny you said that as i just checked and same here?
Please other peeps check your email amd see if it's broke, seems like even renaming htmlnote.dll to htmlnote.dllold so as the ROM recreates the file does not seem to fix it......
That's a shame, it got the SMS to work perfectly. Though I suppose that an annoyance with the SMS is better than completely broken e-mail. Seems like there must be a way to have both though.
Sunookitsune said:
That's a shame, it got the SMS to work perfectly. Though I suppose that an annoyance with the SMS is better than completely broken e-mail. Seems like there must be a way to have both though.
Click to expand...
Click to collapse
Yeah i'll put up with the "slightly" anoying sms so i can read my emails
"here goes another couple of hours of my life setting up device "
Hey, not exactly sure about posting in the right sub forum but i have a little issue
i am currently using a CDMA Hero for Sprint and everything has been going well after fixing the battery issue with a different messaging app, but now a new little annoying issue has arised.
lately when i have opened my menu bar for all my apps i have been getting multiple icons for the same apps
Examples such as Bonsai Blast and Teeter have 2 icons right next to each other that are the same. They both work but its kinda annoying
also some of the applications names are incorrect. instead of ChompSMS its titles is now com.p1.chompsms along with Google Voice being voicemail.xxx... etc
i have tried searching the forums quite a bit and haven't quite found an answer for this issue and am not sure if it applies to the GSM version (thinking it might be a bug for Sense UI)
anyone have the same issue?
i have tried reinstalling the applications and rebooting and it still keeps happening. (not really wanting to hard reset...)
Any help would be very much appreciated!
Thanks!
you are not alone, yeah for i have two print voicemail apps one with a long com..... something same with google sky and google voice app its odd but hey hopefully we will get eclair soon
I don't think it is the Sense UI. I think it is Android. They show the long namsspace name for the application...and some apps show other weird names as well. It happens when you reboot the phone, at least for me. I think it has to do with the way the apps register themselves when the phone boots. Or it may be sloppy programming in the manifest files. Not sure.
Having the same issues. Google Sky will actually show up as the first application, and titled something with about an End User Agreement. When launched it pops up the EUA and only option is a force close.
Not sure what is causing it either.
ljmeli said:
Having the same issues. Google Sky will actually show up as the first application, and titled something with about an End User Agreement. When launched it pops up the EUA and only option is a force close.
Not sure what is causing it either.
Click to expand...
Click to collapse
I had that happen also. I uninstalled and reinstalled the app and it fixed itself.
thecodemonk said:
I had that happen also. I uninstalled and reinstalled the app and it fixed itself.
Click to expand...
Click to collapse
I bet if you reboot your phone the issue will return though...try it!!!
If that IS the case, see my post in this CDMA forum about app versions reverting. what has happened is that your app, in this case google sky, has reverted to an initial version, without telling you.
kmartburrito said:
I bet if you reboot your phone the issue will return though...try it!!!
If that IS the case, see my post in this CDMA forum about app versions reverting. what has happened is that your app, in this case google sky, has reverted to an initial version, without telling you.
Click to expand...
Click to collapse
Just tested this and you are correct! Google Sky maps and Google Voice are the ones that do this for me.
Ul
thecodemonk said:
Just tested this and you are correct! Google Sky maps and Google Voice are the ones that do this for me.
Click to expand...
Click to collapse
I've confirmed that this app version reverting issue happens with at least 16 apps, not just the two Google apps you mention. I have a support question open with Google, so hopefully they can figure it out soon. It makes people think something else is wrong entirely.
JiltedCitizen said:
I don't think it is the Sense UI. I think it is Android. They show the long namsspace name for the application...and some apps show other weird names as well. It happens when you reboot the phone, at least for me. I think it has to do with the way the apps register themselves when the phone boots. Or it may be sloppy programming in the manifest files. Not sure.
Click to expand...
Click to collapse
I really think this now too,
so far i reinstalled Flixster Movies and Handcent SMS and when my phone reboots i get some different weird icon for both that are not the original ones.
also with the reboot, one of my original problems happens with the names of ChompSMS and Google Voice with their com.xxx.etc names
it has to be something changed on a reboot.
Google Dev group is on it. No fix yet though unfortunately:
http://groups.google.com/group/android-developers/browse_thread/thread/3b7aced444a47425?pli=1
mercado79 said:
Google Dev group is on it. No fix yet though unfortunately:
http://groups.google.com/group/android-developers/browse_thread/thread/3b7aced444a47425?pli=1
Click to expand...
Click to collapse
Mercado, would you mind also informing them that a reboot also is causing apps to revert to their older versions? I think the problems are related. Thanks!
kmartburrito said:
Mercado, would you mind also informing them that a reboot also is causing apps to revert to their older versions? I think the problems are related. Thanks!
Click to expand...
Click to collapse
Oops! Sorry for making it sound like I am in on the android developer work. It is way over my head. Just thought I'd share a link I'd stumbled across. If it's kosher, perhaps you might want to share the url to your version reverting bug with that group. Not sure how that works.
In any case, it does seem like this is all related (missing icons, duplicate icons, renamed shortcuts, version issues, etc.). Unfortunately, it so far HTC has not acknowledged their role in the matter. Hopefully as the bug reports add up, they'll do something about it. Or, maybe they'll simply release Android 2.0 with Sense built in.
mercado79 said:
Oops! Sorry for making it sound like I am in on the android developer work. It is way over my head. Just thought I'd share a link I'd stumbled across. If it's kosher, perhaps you might want to share the url to your version reverting bug with that group. Not sure how that works.
In any case, it does seem like this is all related (missing icons, duplicate icons, renamed shortcuts, version issues, etc.). Unfortunately, it so far HTC has not acknowledged their role in the matter. Hopefully as the bug reports add up, they'll do something about it. Or, maybe they'll simply release Android 2.0 with Sense built in.
Click to expand...
Click to collapse
Ah, no worries. I have no shame, I'll put it in there whether it's kosher or not
After all, without visibility, a problem will never get solved.
Trying to build a rom, and keep getting an error stating "Resources appear in overlay but not in base. Use <add-resource> to add." Where do I add the resource? Noob question but I'm doing my best to learn, and have come a long way without any help. Any advice is appreciated :fingers-crossed:
So, if someone wanted to repeat your issue in order to try and help you, what would they do? Your message is giving an error message, but not telling anyone when that message appears, what is generating the message, steps to repeat, what device you are using, what you've changed, etc, etc.
In fact, your message is only a little better than creating a new thread containing only the words "it doesn't work." (without defining "it", etc.)
take care
Gary
garyd9 said:
So, if someone wanted to repeat your issue in order to try and help you, what would they do? Your message is giving an error message, but not telling anyone when that message appears, what is generating the message, steps to repeat, what device you are using, what you've changed, etc, etc.
In fact, your message is only a little better than creating a new thread containing only the words "it doesn't work." (without defining "it", etc.)
take care
Gary
Click to expand...
Click to collapse
Well, Gary...First off, thank you for responding. I understand the confusion as this is a dual device thread. I'm working on the SGS 3 (d2att). I figured my message was pretty much self explanatory as to the issue I'm having. When I stated trying to "build" a rom. I figured that would mean during the compiling script. Overlay issues generally seem to be related to vendor files as far as I can tell. I tried to add a device framework dimesion overlay to one of my vendor files (An s3 common folder I forked from Rootbox). I edited the arrays.xml and config.xml file inside the values folder under frameworks/base/core to allow such resources. This seemed to be the logical step, but then the error presented itself.
A overlay is supposed to modify a value in the base to the specific one you need for your device. So you must have added a value in your overlay that is not present in the base. Let's see if you can figure it out from there.
thewadegeek said:
A overlay is supposed to modify a value in the base to the specific one you need for your device. So you must have added a value in your overlay that is not present in the base. Let's see if you can figure it out from there.
Click to expand...
Click to collapse
You basically just paraphrased what I said in the previous post. I told you the steps I took to correct the error. Did it work? No....
Twiisted said:
Trying to build a rom, and keep getting an error stating "Resources appear in overlay but not in base. Use to add." Where do I add the resource? Noob question but I'm doing my best to learn, and have come a long way without any help. Any advice is appreciated :fingers-crossed:
Click to expand...
Click to collapse
Pretty sure I answered the one question you asked in your OP. Plus I believe this whole thread is better suited for Chef Central.
Sent from my SCH-R950 using Tapatalk 2
thewadegeek said:
Pretty sure I answered the one question you asked in your OP. Plus I believe this whole thread is better suited for Chef Central.
Sent from my SCH-R950 using Tapatalk 2
Click to expand...
Click to collapse
So you just looked at the OP and posted without reading any of the thread? Thats helpful :good:
Because we can all read your mind and your computer logs to know exactly what you typed. You asked a question and I answered it, without knowing what exactly you changed/added how are we supposes to provide any further support?
I did read your post...I don't see how it was supposed to change my answer though.
Sent from my SCH-R950 using Tapatalk 2
It's all good man...just frustrating. I've worked out sooo many kinks but this one has me stumped. The logs are gone and it takes 90 min to even get to that point during the build. I added device configurations to the vendor files. The ones giving me trouble are the resources in the vendor overlays files. Like I said, I added the resources to the config.xml and array.xml in the base...it still won't compile.
Twiisted said:
Well, Gary...First off, thank you for responding. I understand the confusion as this is a dual device thread. I'm working on the SGS 3 (d2att). I figured my message was pretty much self explanatory as to the issue I'm having. When I stated trying to "build" a rom. I figured that would mean during the compiling script. Overlay issues generally seem to be related to vendor files as far as I can tell. I tried to add a device framework dimesion overlay to one of my vendor files (An s3 common folder I forked from Rootbox). I edited the arrays.xml and config.xml file inside the values folder under frameworks/base/core to allow such resources. This seemed to be the logical step, but then the error presented itself.
Click to expand...
Click to collapse
You are still leaving out information. Based on some of the other replies, it's pretty obvious that I'm not the only one who thinks so.
For example, it seems to be (based on some of the things you are saying) that you are building a form of AOSP? CM? AOKP? Something else? What? Which version? (Yes, it DOES matter.)
It might help if you recreate your situation from a "known" starting point. For example, grab the cm10 (or 10.1) code as a starting point. Then make minimal changes to that in order to reproduce your problem. (I'm guessing this would mean just adding a couple xml files to the overlay.) If you get the same error, then you'll be able to post CLEAR instructions to repeat the issue - such as "started with cm10.1 and was able to compile for d2att fine. Added the following files (attached) to the x/y/z directory and then edited file a/b/c to what is also attached, and then when I run brunch, I get an error stating 'error message here'"
If you do what I suggested, then someone else would be able to reproduce exactly what you are seeing (or at least be able to understand the context of your issue) and might help.
...unless, of course, you are deliberately NOT sharing information. If that's the case, please state that. It would make things easier.
Twiisted said:
Trying to build a rom, and keep getting an error stating "Resources appear in overlay but not in base. Use <add-resource> to add." Where do I add the resource? Noob question but I'm doing my best to learn, and have come a long way without any help. Any advice is appreciated :fingers-crossed:
Click to expand...
Click to collapse
ur getting something like
(xml file):# (error message)
right?
if so, just open up the xml file and delete the part with whatever resource it tells you
cpu999 said:
ur getting something like
(xml file):# (error message)
right?
if so, just open up the xml file and delete the part with whatever resource it tells you
Click to expand...
Click to collapse
Not really neccessary anymore...vendor files were updated with latest sync. Fixed my issue and wasted a few days of my time :/
I have to type a number twice before my phone actually calls a number. Please have a look at the bug in action.
https://www.youtube.com/watch?v=ff7JeX_eNOQ
My life style is very busy and it is a huge huge let down since it does it on me at the most crunch moments.
NO ! I am not going to reinstall operating system or flash or anything. This is a bug which needs to be fixed. At least these aren't the kind of problems you face with iOS.
sami1255 said:
I have to type a number twice before my phone actually calls a number. Please have a look at the bug in action.
https://www.youtube.com/watch?v=ff7JeX_eNOQ
My life style is very busy and it is a huge huge let down since it does it on me at the most crunch moments.
NO ! I am not going to reinstall operating system or flash or anything. This is a bug which needs to be fixed. At least these aren't the kind of problems you face with iOS.
Click to expand...
Click to collapse
If you don't like to do anything to resolve your problem, why did you posted here?
zagorteney said:
If you don't like to do anything to resolve your problem, why did you posted here?
Click to expand...
Click to collapse
Of course I want to do something about fixing it. But not something which involves rooting, flashing, anything which mess with my current settings and apps.
I understand that this is a developers forum and most of the solutions here simply mention to reinstall the who freaking Operating system instead. Hopefully I made my point clear.
sami1255 said:
Of course I want to do something about fixing it. But not something which involves rooting, flashing, anything which mess with my current settings and apps.
I understand that this is a developers forum and most of the solutions here simply mention to reinstall the who freaking Operating system instead. Hopefully I made my point clear.
Click to expand...
Click to collapse
Yes you are. But with that statement this is all you will get here.
Are you on 5.0 or 5.0.1? I think it is an Android bug.
Sent from my Nexus 5 using XDA Free mobile app
it happened often with me to, its a lollipop bug,
and yes you should downgrade to kitkat if you want stabilty,
Its unfortunate that these issues occur
sami1255 said:
NO ! I am not going to reinstall operating system or flash or anything. This is a bug which needs to be fixed. At least these aren't the kind of problems you face with iOS.
Click to expand...
Click to collapse
Maybe get an iOS device instead?
Never had such Dialer issue here.
If it's an AOSP bug, then this is not the place to report it, tell Google instead, and also provide logs.
Get an iOS device.
I'm a Typeapp user for my mailaccounts. Since the latest upgrade to Android 13 it does not always show a notification. Randomly.
Typeapp suggested to alter the Battery Manager to allow the app running in the background. Did not help.
Then I tried a few other email apps for a week or so, but the same issue occured: not always a notification in time.
My idea is that this issue does not belong to the mailapp, but possibly Android 13 does something in the background that prevents a notification. Sometimes (and that's the irritating part!).
Somebody recognizes this?
Mauvan said:
Somebody recognizes this?
Click to expand...
Click to collapse
This sounds somewhat familiar to me already since Android 11 where several people had the same issue regarding SMS/text messages arriving in time in Android (according to the logcat) but the notification message was often triggered few minutes or much later.
For a workaround for the SMS/text messages notification delay problem, effective at least for the default SMS/text/messaging app com.android.messaging, see the following GitLab issue (for klte) which even lead to one of the LineageOS developers reporting the bug to Google with the corresponding issue still being unresolved/open.
[Update 23.10.2022 for the sake of completeness]:
Other users reported the same problem for different phones No SMS while screen off and Notifications for incoming messages are delayed after device has been sleeping for a long time
It seems to me that this is a typical SMS-issue. I think my issue is a more general thing and I will try a hard reset and start with a clean Android 13 setup.
I'll give feedback afterwards... (when time and availability let me fix it)
Mauvan said:
It seems to me that this is a typical SMS-issue
Click to expand...
Click to collapse
The reception of the SMS was/is not the problem in this case since it appears immediately after sending in the log but the notification triggers with a large delay/late.
Therefore I can imagine, that this is a general notification bug which also appears in other apps.
Simply trying out the command takes a few seconds and observing the behavior also only takes very little time.
Personally I would invest this little time before doing a hard rest ... but perhaps I am the only one who enjoys doing other things in his spare time much more rather than hard resetting his phone and going through the following tedious installation and setup of all apps from scratch.
I know, it is no fun doing those things like install and setup your phone
But what if I really cannot find the com.android.messaging app amongst all system apps? Or does it have a different name since A13??
Mauvan said:
I know, it is no fun doing those things like install and setup your phone
Click to expand...
Click to collapse
Mauvan said:
I will try a hard reset and start with a clean Android 13 setup.
Click to expand...
Click to collapse
I wrote my sentence in a "teasing" way but with the winking smiley because you seemed very determined reinstalling everything from scratch without trying the suggested workaround.
And since different people have different interests, there was still a small chance that you prefer having a clean Android installation anyway from time to time and simply want to make sure that the problem arose from a "dirty" upgrade from A12 to A13.
Anyway, I am now confused by your following statement:
Mauvan said:
But what if I really cannot find the com.android.messaging app amongst all system apps?
Click to expand...
Click to collapse
The way I understood you is, that your issue did (at the moment) only affect email apps.
1.
Did you also observe the notification delay with the stock SMS/text messaging app?
2.
If not, what is the reason why you now want to identify the stock SMS/text messaging app?
Mauvan said:
Or does it have a different name since A13?
Click to expand...
Click to collapse
This I don't know.
3.
If 1. == yes, is the app name displayed in the app info options menu (the place of the other settings like permissions, storage & cache, etc.) when you scroll all the way to the bottom (as it is the case in A12)?
4.
If 3. == no, then you can possibly identify it using the output of
Code:
adb shell pm list packages
or paste the result here so we can have a guess.
wireroot said:
I wrote my sentence in a "teasing" way but with the winking smiley
Click to expand...
Click to collapse
Of course I got the wink
wireroot said:
1.
Did you also observe the notification delay with the stock SMS/text messaging app?
Click to expand...
Click to collapse
No. Mail only.
wireroot said:
2.
If not, what is the reason why you now want to identify the stock SMS/text messaging app?
Click to expand...
Click to collapse
I was just scrolling through that "Gitlab issue" (the link you added before)
wireroot said:
If 3. == no, then you can possibly identify it using the output ....
Click to expand...
Click to collapse
I'm not sure how to do this.
Both technical and my language skills makes this a time consuming thing, but I'll try later.
Mauvan said:
No. Mail only.
Click to expand...
Click to collapse
Well, if it only occurs in the mail apps, then let's stick with those.
So, instead of whitelisting the SMS/text app, I suggest to try the battery optimization whitelisting procedure with those.
As a first step, please execute the current content of the battery optimization whitelist by calling
Code:
adb shell dumpsys deviceidle whitelist
and paste the result (list of apps) in this thread.
This should help us in better understanding whether the whitelisting step via ADB (which was either already done by you via the Android UI, or if not, which we'll do once we have the result from the above call) actually changes the whitelist content.
Mauvan said:
Typeapp suggested to alter the Battery Manager to allow the app running in the background. Did not help.
Click to expand...
Click to collapse
By "which was either already done by you via the Android UI" I am referring to the thing you have done as stated in your statement quoted above. Since the information how you did it is quite vague, I need the requested info.
Mauvan said:
I'm not sure how to do this [...] but I'll try later.
Click to expand...
Click to collapse
Since we are now ignoring the SMS/text ab, you can forget about the adb shell pm list packages command but need to execute the other (ADB) command mentioned above.
There are many tutorials on how to use ADB - I am only (randomly) posting the official instructions:
https://developer.android.com/studio/command-line/adb
So you mainly need 2 things:
PC: ADB executable - downloadable from https://developer.android.com/studio/releases/platform-tools
Android: Settings > System > Developer Options > USB debugging
There's not even an option in Settings > System for USB debugging and Developer Options in my Pixel.
In another life I was a programmer but this goes beyond my capabilities (and patience to figure it out).
I give up.
Thanks for all your efforts, but it's all abacadabra for me. A hard reset is almost faster
Mauvan said:
There's not even an option in Settings > System for USB debugging and Developer Options in my Pixel.
Click to expand...
Click to collapse
If you didn't enable it yet, then this is no rocket science. Simply read the manual which I already posted above where this specific step is answered in this section.
Mauvan said:
but this goes beyond my capabilities (and patience to figure it out).
Click to expand...
Click to collapse
I am sure you would manage that. But since my suggestions only have a small chance but no guarantee that they solve the problem, I understand that you are not eager trying it out.
Btw: Also clicking the thanks/like button is always a welcome gesture to people in the forum
Once you did a clean install and made some observations regarding your problem, please drop us a line here about the result as it may help others too with their decision!