Using the HTC email app, no links are ever parsed. They just appear as standard, un-clickable text. I even tried forward/replying messages to see if they would appear as links there but they don't.
Does anyone else have this issue and/or a suggested fix? Thanks!
Are you debloated on AT&T? It seems we need HTCLinkifyDispatcher, which is removed as bloat
KitF said:
Are you debloated on AT&T? It seems we need HTCLinkifyDispatcher, which is removed as bloat
Click to expand...
Click to collapse
I am not, though I would love to be! (I am reticent to root my device, however.) I am running Apex, however, and perhaps this is related to the issue?
Thanks for the reply. Any further thoughts would be very much appreciated.
Well, apparently, I am not the only one experiencing this. Had not yet found this thread: http://forum.xda-developers.com/showthread.php?t=1639865
Does anyone have any idea why links would not be recognized as such?
i was having problems until i changed the maximum receive settings to max, and things started working much better. HTML emails that did not open correctly began opening and prompting for image downloads as expected.
coolren said:
i was having problems until i changed the message download settings to max, and things started working much better. HTML emails that did not open correctly began opening and prompting for image downloads as expected.
Click to expand...
Click to collapse
Thanks! I tried the "max" setting and this didn't resolve the issue.
However, our problems are different as HTML email display has never been a problem (and I am always prompted to download images)--my issue is that links do not parse in plain-text emails.
links in email are not hyperlinked
I am having the same problem. Hyperlinked words (seem) to be clickable and work fine. However, some emails I get where the address is typed out like the following (for example):
h t t p s://w w w. dropbox.c0m/el/?r=/link/65.Zf7E33Qbpe...
They look like regular text and are not highlighted, much less clickable.
Other times, I get emails with only the following in the body of the email:
"Please view the HTML of this email to see the message".
I'm going nuts because there is no HTML or anything to click on, let alone any kind of message. I've checked settings and nothing there is absolutely nothing to clue me into what might be wrong or how the situation can be resolved.
First of all, here is Ganster41's original post and HERE is a link:
Ganster41 said:
Hi, low-end devices users! I have good news for you
As you know, Qualcomm has ended support for their SoCs, based on ARMv6 core, and doesn't release OpenMax IL libraries for Android 4.0+. Someone was crying on Qualcomm's forum, someone try to understand, how to extend GB proprietaries to support new Google OMX extensions, but nobody try to modify libstagefright, and disable using new unimplemended functions...
I spent about a few weeks, learning stagefright architecture, and differents between GB and ICS OMX layers...and now I ready to show it to you
I have only ZTE Blade, and can make ROM only for it. You can download it here. In addition to worked hardware-accelerated video playback, and camcorder, it builded with Linaro GCC 4.7.1, and has a little UI speedup(if it not a placebo ). ROM based on KonstaT device tree, thanks him for it.
Oh, my Dropbox temporary blocked to public links. I upload ROM to letitbit too.
Modified framework's sources can be found on my github. Besides it, you need to add one global define to your device's BoardConfig.mk - COMMON_GLOBAL_CFLAGS += -DQCOM_LEGACY_OMX
UPD: I make same changes in CM10 sources tree, but it doesn't working, and I can't try to fix it, because haven't enough disk space to build CM10 ROM. I think, Google changes OMX API again, and it needs more fixes to get it working. You can download sources from here. For now I not interestid in CM10, because now it laggy and has some not good issues.
UPD2: Please, if you want my help with integration problem, attach logcat at the time, when you try to use vide playback/camcorder. I can't help without any information.
UPD3: If you trying to make port for your device, this post can be helpful. Thanks to cougarcougar for it.
UPD4: We still get errors, if trying to play videos from some apps(e.g. Android browser) in not-fullscreen mode. gralloc or mmap returns error, when try to map buffers from NativeWindow. If anybody have ideas how to fix it, please write it here, or to my PM...
Important addition!
Devices based on MSM7x27 chips has two different versions of OMX libs.
"Oldt"(for froyo?) has an unknown padding between color components parts of returning buffer. I have fixed that for most videos, but some strange resolutions are still gets broken colors with green line on top.
"New" version are present in Samsung/LG devices, who has official Gingerbread ROMs. It returns correct buffer in dfferent color format(YV12, instead of NV21), but it laggy on VGA+ videos. Now don't know why. May be it convert resulting buffer to YV12 on CPU... I will try to understand it later.
I think you can use "old" libs from ZTE Blade on any device, because "new" libs work on ZTE Blade too.
PS: If you want to thanks/support my work - you know where you can find button for it.
Click to expand...
Click to collapse
Now for this thread:
This is a project for porting this over to JB. Currently it builds. That's just about it. We need to make this work.
Current contributors are:
Rashed97
Bytecode
bieltv.3
erikcas
And the repos currently resides at: https://github.com/androidarmv6/android_frameworks_av and https://github.com/androidarmv6/android_frameworks_native
Anyone else wanting to work on this, just shoot me a PM and I'll add you to the list and the repo!
Good Luck with this project! Hope you get it working on JB.
Sent from my GT-S5570 using xda app-developers app
I'm interesting on get it working, but not sure if really I can help, I'll continue testing some fixes in my local, and if a discover something interesting I'll give you the info.
Enviado desde mi Wildfire S A510e usando Tapatalk 2
Im gonna give it a try, and see what happends.
Edit 1: Mine did boot how can I verify that its working?
Edit 2: Its complaining about a missing libwvm.so
Rashed, sent you PM. Done some things on this.
like I said in PM, it is some port from CM9 and result of a little out-of-the-box thinking
HQ stream comes in but lags (..we're much too late, skipping..." in logcat)
see https://github.com/erikcas/android_frameworks_av/
erikcas said:
Rashed, sent you PM. Done some things on this.
like I said in PM, it is some port from CM9 and result of a little out-of-the-box thinking
HQ stream comes in but lags (..we're much too late, skipping..." in logcat)
see https://github.com/erikcas/android_frameworks_av/
Click to expand...
Click to collapse
Are the errors something like this?
"The main process is doing to much work on its main thread. Skipping xx frames!"
If they are I get those too...
Sent from my iPod touch using Tapatalk
Rashed97 said:
Are the errors something like this?
"The main process is doing to much work on its main thread. Skipping xx frames!"
If they are I get those too...
Sent from my iPod touch using Tapatalk
Click to expand...
Click to collapse
Exactly those
Verstuurd van mijn GT-S5660 met Tapatalk
erikcas said:
Rashed97 said:
Are the errors something like this?
"The main process is doing to much work on its main thread. Skipping xx frames!"
If they are I get those too...
Sent from my iPod touch using Tapatalk
Click to expand...
Click to collapse
Exactly those
Verstuurd van mijn GT-S5660 met Tapatalk
Click to expand...
Click to collapse
I get those everywhere including messeges app with or without the omx hack, to me those errors can be ignore, that's android saying the thing it just doing it taking a lot of cpu power to the point the screen frame started to skip.
hcweb said:
I get those everywhere including messeges app with or without the omx hack, to me those errors can be ignore, that's android saying the thing it just doing it taking a lot of cpu power to the point the screen frame started to skip.
Click to expand...
Click to collapse
I got those on ICS too when lagging. When solved they dissapeared so in my opinion they cannot be ignored.
Also. Skipping frames equals lag implicitly imo
Verstuurd van mijn GT-S5660 met Tapatalk
erikcas said:
I got those on ICS too when lagging. When solved they dissapeared so in my opinion they cannot be ignored.
Also. Skipping frames equals lag implicitly imo
Verstuurd van mijn GT-S5660 met Tapatalk
Click to expand...
Click to collapse
I know its a more detailed way of saying the app just hanged and its laggin, its helpfull to identify if its running full at perfromance, but imo it does not give right now a reason why it does not work at all. Later this night im gonna post a more detail log about the errors.
hcweb said:
I know its a more detailed way of saying the app just hanged and its laggin, its helpfull to identify if its running full at perfromance, but imo it does not give right now a reason why it does not work at all. Later this night im gonna post a more detail log about the errors.
Click to expand...
Click to collapse
well, here is my logcat for 40 secs of video:
Code:
I/ChromiumHTTPDataSource( 608): connect to http://redirector.c.youtube.com/videoplayback?id=5f20aa830f9249fd&itag=18&source=youtube&uaopt=no-save&upn=Dp7QSj_dcks&el=user_uploads&devKey=ATpxuMO4AN5NR1nGmfaQDBQO88HsQjpE1a8d1GxQnGDm&app=youtube_gdata&ip=0.0.0.0&ipbits=0&expire=1352524595&sparams=id,itag,source,uaopt,upn,ip,ipbits,expire&signature=1F93E556DA16E6BC085D0445694060D308BD3315.D2FB8F933BAF64B5E643B42AB1CF25EB36D630E7&key=yta1&androidcid=android-google&dnc=1 @0
I/AudioHardware( 608): set device to SND_DEVICE_SPEAKER device_id=0
I/AudioHardware( 608): disabling post proc features with mask 0x0000
W/WVMExtractor( 608): Failed to open libwvm.so
E/OMXCodec( 608): failed to allocate node OMX.qcom.video.decoder.h264
I/OMXCodec( 608): [OMX.google.h264.decoder] Non-Interlaced format detected
I/OMXCodec( 608): [OMX.google.h264.decoder] AVC profile = 66 (Baseline), level = 30
I/OMXCodec( 608): [OMX.google.h264.decoder] Enable frame by frame mode
W/OMXCodec( 608): Failed to set frame packing format on component
I/OMXCodec( 608): [OMX.google.h264.decoder] video dimensions are 320 x 240
I/OMXCodec( 608): [OMX.google.h264.decoder] Crop rect is 320 x 240 @ (0, 0)
E/OMXCodec( 608): [OMX.google.h264.decoder] Ignore PortSettingsChanged event
I/OMXCodec( 608): [OMX.google.h264.decoder] video dimensions are 640 x 368
I/OMXCodec( 608): [OMX.google.h264.decoder] Crop rect is 640 x 360 @ (0, 0)
I/SoftwareRenderer( 608): Buffer color format: 0x13
I/SoftwareRenderer( 608): Video params: mWidth: 640, mHeight: 368, mCropWidth: 640, mCropHeight: 360, mCropTop: 0, mCropLeft: 0
I/AudioHardware( 608): set device to SND_DEVICE_SPEAKER device_id=0
I/AudioHardware( 608): Enabling post proc features with mask 0x0000
I/AwesomePlayer( 608): we're much too late (0.51 secs), video skipping ahead
I/AwesomePlayer( 608): we're much too late (0.52 secs), video skipping ahead
I/NuCachedSource2( 608): ERROR_END_OF_STREAM
I/AwesomePlayer( 608): we're much too late (0.50 secs), video skipping ahead
D/NetlinkEvent( 606): Unexpected netlink message. type=0x0
D/NetlinkEvent( 606): Unexpected netlink message. type=0x0
D/NetlinkEvent( 606): Unexpected netlink message. type=0x0
D/NetlinkEvent( 606): Unexpected netlink message. type=0x0
I/AwesomePlayer( 608): we're much too late (0.50 secs), video skipping ahead
I/AwesomePlayer( 608): we're much too late (0.51 secs), video skipping ahead
erikcas said:
well, here is my logcat for 40 secs of video:
Code:
E/OMXCodec( 608): failed to allocate node OMX.qcom.video.decoder.h264
Click to expand...
Click to collapse
Your device didn't allocate the hardware codec - see the line above. The reason why your video is laggy is simply because it's using the software fallback...
psyke83 said:
Your device didn't allocate the hardware codec - see the line above. The reason why your video is laggy is simply because it's using the software fallback...
Click to expand...
Click to collapse
yup I know. That is where I am in a loop. So gonna have a bear to get out of it
Edit: beer
erikcas said:
yup I know. That is where I am in a loop. So gonna have a bear to get out of it
Edit: beer
Click to expand...
Click to collapse
Insted of trying to play a youtube video I tried playing a .mp4 video and I got preatty much the same results as your logcat, but
Code:
W/WVMExtractor( 608): Failed to open libwvm.so
Came up alot to the point I needed to end the logcat to read what was going on. But right now im waiting for a phone call ( this is my main phone ), so i cant test my build, but as soon im done with the phone call gonna try again my build and report back.
I can play mp4 videos on gallery perfectly, only 3gp and youtube hq lags.
Enviado desde mi Wildfire S A510e usando Tapatalk 2
hcweb said:
Insted of trying to play a youtube video I tried playing a .mp4 video and I got preatty much the same results as your logcat, but
Code:
W/WVMExtractor( 608): Failed to open libwvm.so
Came up alot to the point I needed to end the logcat to read what was going on. But right now im waiting for a phone call ( this is my main phone ), so i cant test my build, but as soon im done with the phone call gonna try again my build and report back.
Click to expand...
Click to collapse
I think that can be ignored. The "error" has been there allways.
Hm... Try using the ICS libwmv.so file and see if that works. Also for some reason it keeps using the non-Qualcomm libs so that's why it insists on not working.
erikcas said:
I think that can be ignored. The "error" has been there allways.
Click to expand...
Click to collapse
Ok, thanks for the tip. The libwvm.so is something related to drm, its supose not to be needed by aosp or cm but the av framework asks for it.
I guss i should keep ignoring it, since i dont plan to play any drm files.
Hello everyone,did not see this thread before,anyways I think the problem is into the decoder select. When comparing my Jellybean roms with the Gangster41's hack,all I can see into the logcat are output from OMX.google video codec. Therefore,AwesomePlayer tells us we're too much late and skips the video. I think we need to revise that portion of the code.
Sincerely,
Bytecode
well, I guess one step forward is 4 steps back. Been playing for a while, and finally came up with attached media_codecs.xml (as .txt file )
When starting the YT, it seems to choose the HW encoder, which leads to a sigsev.
See attached logcat.
Used source on my github, https://github.com/erikcas/android_frameworks_av
Will try also with my additions reversed, will have to recompile
View attachment logcat.txt
View attachment media_codecs.txt
First off: This is my first post on XDA (looong-time reader, great site), and I posted this here because I don't yet have the required 10 posts to put this in the Dev forum, so I apologize for that.
Here's my question: I flashed the Cyanogen 10 Alpha 3 rom (upgraded from the CM 9 rom) a couple of days ago, fully clean install (wiped data/cache/dalvik) and I keep getting FC on the Contacts system app. I can receive calls just fine, but if I try and go to contacts / dialer, it immediately FC. Reboots haven't helped, clearing the contact app cache hasn't helped. I've been following the dev thread, but haven't seen this addressed, so I'm assuming it's just me.
Does anyone have any suggestions?
The rom is beautiful otherwise, keep up the great work korny!
First of all, we need to know what is going wrong. Make a logcat:
Install Terminal Emulator on Phone
open it , then :
logcat -c
Click to expand...
Click to collapse
after that , open contacts (it'll crash, that's ok for now)
then , back in terminal emulator :
logcat > /sdcard/logcat.txt
Click to expand...
Click to collapse
then pull logcat.txt from SDCard , and post in on Pastebin (don't forget to give us a link)
I'm running CM 10 Alpha 3 right now, and had same problem.
In my case - it was old SQLITE DB , so cleaning contacts cache solved it
Nusferatu said:
...then pull logcat.txt from SDCard , and post in on Pastebin (don't forget to give us a link)...
I'm running CM 10 Alpha 3 right now, and had same problem.
In my case - it was old SQLITE DB , so cleaning contacts cache solved it
Click to expand...
Click to collapse
Ah, sorry about that, knew I should've done that in the first place.
Sorry for plain text attachment, apparently you can't paste outside links until you hit 10 posts, either).
Thanks for your help, I really appreciate it.
So , a brief view lead to this:
E/AndroidRuntime(13173): Caused by: java.lang.NullPointerException
E/AndroidRuntime(13173): at android.text.SpannableStringBuilder.<init>(SpannableStringBuilder.java:44)
E/AndroidRuntime(13173): at android.telephony.PhoneNumberUtils.formatNumber(PhoneNumberUtils.java:1143)
E/AndroidRuntime(13173): at com.android.contacts.dialpad.T9SearchCache$LoadTask.doInBackground(T9SearchCache.java:257)
E/AndroidRuntime(13173): at com.android.contacts.dialpad.T9SearchCache$LoadTask.doInBackground(T9SearchCache.java:216)
E/AndroidRuntime(13173): at android.os.AsyncTask$2.call(AsyncTask.java:287)
E/AndroidRuntime(13173): at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:305)
E/AndroidRuntime(13173): ... 5 more
W/ActivityManager( 339): Force finishing activity com.android.contacts/.activities.DialtactsActivity
Click to expand...
Click to collapse
Try to clear cache for Phone app
Nusferatu said:
So , a brief view lead to this:
Try to clear cache for Phone app
Click to expand...
Click to collapse
So, I cleared the phone app cache then tried to open it again, and it FC again.
After a reboot, I tried to open it once more and it caused the system to hang for about 60 seconds, after which it resumed its FC.
Would another logcat be useful, or am I spinning wheels at this point?
Hmm... Are you syncing Contacts with GMail acc ?
Could you Disable contacts sync, and then clear cache? then try to open Contacts and if it's FC - get another logcat
It seems , like i found what is causing u'r problem.
One of you'r contacts have NULL-string phone number.
Last time i've seen that problem , that was Skype causing it.
Updating Skype from GPlay fixed problem.
Nusferatu said:
Hmm... Are you syncing Contacts with GMail acc ?
Could you Disable contacts sync, and then clear cache? then try to open Contacts and if it's FC - get another logcat
Click to expand...
Click to collapse
Good call, I turned off all sync, cleared Contacts app cache (the Phone app cache was still empty), re-opened the Contacts app, then re-enabled Sync and it would appear as though this problem may be resolved now. I'll give it tomorrow to see how it goes, hopefully this isn't going to be a recurring problem.
You, sir, are a scholar and a gentleman. Thanks again.
I'm happy to report that, after over 24 hours, I've still not had any more problems out of the contacts app.
Just wanted to thank you for your help one last time, cheers!
Sent from my MyTouch 4G Slide using Tapatalk 2
Hi,
I've got a camera app on the play store called "Snap Camera" and people have reported that it has problems with video recording on the galaxy-r.
If somebody could get me a log of it crashing and help with testing, I'd be really grateful. You can get a trial version here:
https://play.google.com/store/apps/details?id=com.marginz.snaptrial
and the full app is here:
https://play.google.com/store/apps/details?id=com.marginz.snap
The trial is identical to the full version but only starts when there is no network connection.
Send me a PM (or post here) with a log of the crash from the trial version, I'll try to fix it and in return I'll send you an apk for the full version.
Thanks
Just recorded a video with it, no issues.
Anyways I did a logcat with priority level Error and above. Find it attached.
The-Droidster said:
Just recorded a video with it, no issues.
Anyways I did a logcat with priority level Error and above. Find it attached.
Click to expand...
Click to collapse
Thanks, I'll take a look at the log and see if there's anything in there.
simple method
It can be rectified by simple method.....
goto settings >>video setting>>switch on both video snap shot and full size snap shot......
bit laggy nut works......!!
Hello
Im trying to use performance monitor apps that have floating windows to use while gaming to keep temperatures in the eye. But my problem is that whenever i open the floating windows, they will work and update the data for 5-10 seconds and after that they start to freeze and then they just close. I tried 'Simple System Monitor', 'System Monitor Float' and 'CpuFloat'. And all of their floating windows crash even when i just use it on the homescreen and outside of any game. I have given all necessary permissions too. Anyone have an idea please? Android 11 btw.
Thanks
Do a LOGCAT to get the reason why.
jwoegerbauer said:
Do a LOGCAT to get the reason why.
Click to expand...
Click to collapse
I have no idea what that is but i will research it. Thank you! Edit: ahh it logs system messages and stuff and with this its possible to see what exactly happens when the windows close. Thnx
jwoegerbauer said:
Do a LOGCAT to get the reason why.
Click to expand...
Click to collapse
now i have a log but i dont understand it :/ i just find the point at which i launched the "System Monitor Float" app and the rest is too much for me
edit: after the point where i started the app i found the point where it got killed by the activity manager saying: Killing 29860:a98apps.monitorfree/u0a192 (adj 200): user request after error
same thing it said when the other app got killed. theres some kind of error happening but i have no idea what it is
if anyone could check my log that understands whats happening between starting my apps and them being killed and maybe being able to give me a hint at what could be the cause of this errors, that would be awesome
cheers and greetings