Related
Please could someone help or explain.I purchased the orbit II last week,I am still getting used to its power and capabilities.
In the manual it says it can play AAC files.I have downloaded some onto the storage card and the touch flo player hasnt recognised them, nor has the windows media player.
It recognises and plays MP3 files.The aac files are not protected they are ones that I downloaded myself from my own cds.
Also why can I not see photos that I have just taken that are saved to my storage card,in the photo viewer on Touch flo.
Thank you in advance for any help,
Peter
pocketmusic can play aac
Thansk for that,but I was looking to find out what the situation was with the phone rather than get a programme that will do something that the manufacturers are saying the phone should do.
I have noticed that the windows media player does add the tunes to its catalogue but files them under ARTIST "UNKNOWN" (as though the tags arent working).The touch flo or HTC player however doesnt even do this.
Does anybody know of a solution to this other than spending money on a progamme to do something that the phone should do already,
many thanks
Peter15965
It's really wierd. I have the same problem and also had this problem with my previous phone which was an O2 XDA Orbit 1 (i.e. rebranded HTC Artemis).
I'm afraid that I never found a solution that didn't involve third party software. I think the problem is that, although HTC have included the decoder to play AAC and AAC+ files, neither of the built in players seem to be able to read the tags from the m4a container format so, although they can play the contents, they can't incorporate the tracks in a meaningful way into the library (I also saw Windows Media Player putting everything as unknown).
I know it's not what you were hoping to hear, and I'd love for someone to prove me wrong, but right now I think you're stuck with going the third-party route.
If you don't want to spend money then I initially used TCPMP. It doesn't have any library browser built in but I found that by intelligent choice of the directory tree structure I used to store my files (My Music/<Artist>/<Album>/<Tracks>) then I could use the file browser in TCPMP to browse my collection in a fairly convenient manner. I now use Conduits PocketPlayer because that has a fantastic library browser and reads the m4a tags perfectly; the program is pretty resource hungry but for now I'm keeping the faith in the hope that they'll address that at some point in the future (their support is good).
- Julian
Thanks Julian at least I know its a common problem(does 2 handsets constitute common).
I will look into pocketplayer as a solution for the timebeing.I was hoping I wouldnt have to put other apps on that would slow the phone down.
Thanks again
Peter15965
peter15965 said:
Thanks Julian at least I know its a common problem(does 2 handsets constitute common).
I will look into pocketplayer as a solution for the timebeing.I was hoping I wouldnt have to put other apps on that would slow the phone down.
Thanks again
Peter15965
Click to expand...
Click to collapse
You're welcome.
In most cases putting other apps on shouldn't slow down the phone. The reason apps can slow down the phone (and/or drain battery) can be because they have a Today plugin which, if not well written or if it needs to keep accessing the network, can slow things down. If an app does have a Today plugin (as PocketPlayer does) then you can often disable it (as you can for PocketPlayer).
The other reason for third party apps to slow down the phone is because Windows Mobile default behaviour when you click the top-right "x" button is to minimise the app (i.e. leave it running in the background) rather than close it down completely. Again, in this case an app that does anything significant when it is running in the background can slow down the phone. Clearly a music player needs to keep running while it is playing music but, once finished, you can make sure it is out of memory completely by selecting Exit from the application's menu.
In short, if you're careful to fully close apps when you don't need them, then you shouldn't slow down your phone at all (except so far as having a music player running in the background, whether built in or third party, will always put a drain on the CPU and make other apps run more slowly while the music is playing).
- Julian
Oops. One big thing I forgot to mention. If you do look at PocketPlayer then don't download the latest version (3.51) from their web site. There is a nasty problem in that build specifically related to playing AAC files on HTC devices that I reported to them and has been fixed in an internal beta for 3.52 which, as the reporter of the bug, I have been given to test. You should email [email protected] and say that you want to use it for AAC on an HTC device and hopefully they (Carrie) will let you try out a beta build with the issue fixed.
The issue by the way is that 3.51 doesn't correctly detect end-of-stream when an AAC track has finished so (a) it doesn't auto-advance to the next track in the playlist because it thinks the current track hasn't finished yet and (b) even worse, if you forget to explicitly turn off your device after you've finished listening then PocketPlayer thinks it is still playing your last track and so the device will not put itself into standby and can drain the battery. The issue is fixed in the latest beta build and as an added bonus it also parses m4a tags natively (in 3.51 you could tag your collection by using an option in PocketPlayer to infer the tags from the filenames used in your folder structure but it now reads the real tags in the latest beta).
There is also one other more obscure problem I'm trying to help them diagnose related to AAC on HTC devices but I've been a bit busy recently so am due to give them some feedback and check status on that today or tomorrow. This may or may not be fixed at this stage, I can probably give more feedback in a couple of days so personally I would hold off until I give you an update. If you definitely want to go ahead with a beta build then I can give you a workaround that works most of the time.
- Julian
Thanks again Julian, a fantastic answer by all accounts.I will hold off until you get an answer back about the problems you mention.
Thanks again for a most comprehensive answer.How will we know when the fix is through?
Peter15965
peter15965 said:
Thanks again Julian, a fantastic answer by all accounts.I will hold off until you get an answer back about the problems you mention.
Thanks again for a most comprehensive answer.How will we know when the fix is through?
Peter15965
Click to expand...
Click to collapse
I emailed them this afternoon and got the answer. They've fixed the problem and I'm about to install a new beta to check it's OK. Apparently it was a Windows Mobile bug that they've managed to work around. I'll play with this new update pretty extensively tomorrow so you should get an answer from me in about 24 hours.
- Julian
peter15965 said:
I have downloaded some onto the storage card and the touch flo player hasnt recognised them, nor has the windows media player.
Click to expand...
Click to collapse
I found out some interesting thing: Some files are playing correctly but others refuse to work. I think that has to do with the bitrate of the files. All my m4a-files are bought from Apple Music Store. Most times my files are the unprotected ones with higher bitrate, but I have a few files which were protected (unfortunately I must have lost the copy protection somewhere, I'm really sorry for that ). The protected ones were encoded in a lower bitrate. What I found out is, that all my former protected files are played correctly. So maybe Windows Media Player can only handle files up to certain bitrate which obviously should be lower than 256kbps.
Further test: I created a playlist within windows mobile, but the Audio Manager (Touch Flo) wasn't able to read it. I managed that the playlist was recognized by the program, but it couldn't find any files.
So it is possible to play aac files (up to a certain bitrate) and to create playlists in Windows Media Player without any issues (yet). But I couldn't get it working in TouchFlo.
So, ok, I made half the way. Now it's up to you to make it fully functional.
have the same issue, I see the AAC file in the explorer and can play them from there but they are not loaded in the catalogue. anybody any other idea how to make the visible there? is buying pocket player the only solution?
thanks for the help in advance to everybody
JulianL said:
I emailed them this afternoon and got the answer. They've fixed the problem and I'm about to install a new beta to check it's OK. Apparently it was a Windows Mobile bug that they've managed to work around. I'll play with this new update pretty extensively tomorrow so you should get an answer from me in about 24 hours.
Click to expand...
Click to collapse
The news isn't as positive as I'd hoped. The latest build has improved the problem (so at least they've identified it and found the right area to make changes) but it hasn't fixed it completely.
The player is still usable with AAC files but there is one glitch. After it's been playing for a while, say about 2 hours, then something seems to get corrupted in the image or via a bug in Windows Mobile itself such that thumbnails of the artwork for the album covers no longer display properly when browsing your music library. With the previous build the device would lock up at this point and require a soft reset so at least they've fixed that problem but there is still some sort of issue unresolved.
The workaround seems to be to just fully exit PocketPlayer every couple of hours and then re-launch it again so it's not too arduous and shouldn't prevent you playing with the trial version (although this partially-fixed beta isn't publicly available so you will need to contact support to see if they'll give it to you and given that it still has a known issue they might just ask you to wait a bit).
I'm obviously still working with them to try and 100% nail this issue.
- Julian
Hi, new to the forums, and couldn't find an "omnia" section, so I guess this is the place to post this.
I just got an omnia and I am having a hell of a time trying to get it to play video.
I have tried:
tcpmp.pocketpc.0.72rc1.cab
tcpmp-0.72rc1-arm-ppc-recomp-03.cab
TCPMPMediaPlayer0.81RC1Beta.cab
divxplayer_PPC_0
coreplayer v1.2.5
coreplayer v1.3
and the instructions listed here http://www.pspmyspace.com/omnia/2008/11/watch-youtube-videos-on-samsung-omnia.html (theres a thread on this site with same post, just links didnt work...)
Long story short, I would love to watch the shows I download that are in mp4 format on this phone, its a big reason I picked this one.
Most of the time, I get errors back to the general extent of "cant play h.264" (even after load h.264.cab). Depending on which version I am using above, I sometimes get the crash.txt on TCPMP, or on the ARM-PPC version, it crashes when I try to open the file.
Any help is REALLY appreciated.
Thanks
*UPDATE*
I did get some video working using the 4 part steps provided in the link above. After some testing, .avi videos I have from 2005 and earlier seem to play no problem. newer .avi and .mp4 still refuse to play though.
I am unsure what could be causing this, but I assume its newer codecs that were used in these videos. Does anyone have any ideas here?
Dunno' how bumping is viewed on this board, but since i'm 3 pages back now, can anyone help with this?
Thanks
I think if you install Flash Lite 3, it should work as long as you view the video in PC/Desktop mode.
You are talking about ONLINE youtube videos right?
Unless it's incompatible with Omnia, although Omnia is WinMo.....it should work for you tube.
Just install the .cab
And open opera, and go to youtube
And click on view in Desktop/PC Mode
Then click on a video.
Update: I didn't read the MP4, AVI part. LOL Sorry.
Have you purchased a full version of Core Player Mobile? I had a symbian phone, for example, and I installed a cracked Core Player Mobile, and it couldn't play the videos or it couldn't install. So I bought the real full latest version and it worked miracle. I am not sure if it is just as good in WinMo though
I posted this in what I came to realise was a very old post in the Blackstone so I thought I would duplicate it here for my device.
I just purchased CorePlayer. It gave me v1.3.6 not 2.5. Anyway I have tried a divx and avi film. With both I just saw a green haze for a bit and I then needed to soft reset the device to recover.
I downloaded the cab not exe and installed it directly onto the device. My films are on storage.
I get a "Copy & Convert" dialogue box with "Convertion (None)" and it seems to do nothing for a while but it does seem to copy the file across ok. What that means is I can see it in explorer. That said it seems to take several runs at it and the bars never go beyond three or so.
Have I just got the wrong resolution?
Any ideas?
go to Tools > Settings... > Select Page > Video
Video output GDI
Smooth Zoom On
Spot on. Works a treat. Many thanks!
Last night I tried to play a video on my phone with Coreplayer (v1.5) and whilst it used to work perfectly and play videos REALLY well, it was now awful quality. Was as if the settings for video had reset to default so I tried changing them (smoothing and GDI or Directdraw output) but it keeps making the program crash when I try this, or immediately afterwards.
I've reinstalled Coreplayer (tried 1.3 and 1.5) and it just keeps crashing when I change the output settings, except for once when it let me change them but was still very jerky video, and then it crashed anyway a couple of seconds later. This is using video files that HAVE played fine in the past.
I've removed S2U2 again and rebooted as I had just installed it the day before, then reinstalled Coreplayer again and still get the same issues. It just seems incapbale of playing video properly now for some reason. I know the settings that work well for it as I did have it working perfectly before, but it just crashes now if I try changing them.
I can't think of anything else that I've added recently which may cause this. Not sure what else to check but there must be something I've changed on the phone that's caused this?
Videos work well if I play them by double tapping them in Total Commander, but silly as it sounds I don't know what player this is using to play them! It's not wmp anyway.
Looks like an HTC player maybe but I can't find an actual video player in winmo apart from WMP. There must be a place in the start menu somewhere for this player but I can't find it. It's not in the Multimedia folder in the start menu either so I'm confused!
Annoying because I'm halfway through a film this morning and after going back to home screen, I now don't know how to resume playback without restarting and trying to find the place I was at.
Any ideas? I've looked at other coreplayer related threads but they all seem to be along the lines of just the output settings being wrong and I got no results when I searched for the words coreplayer & crash.
When did 1.5 release?!?! Let me check....
BTW, what ROM are you on? Cooked or Official??
Oops! Sorry, I meant to write 1.3.2 and 1.3.5!!!
My bad.
I'm using the 1.61 official turkish rom.
You sure it is 1.5? Can't find a hint anywhere!
Duh.. ok, try the 1.3.6 yet?
Thought I was the only one to see this problem, though it did occur with previous HTC devices and Coreplayer for me. Occasionally the database file (Application Data\Coreplayer\library.db) seems to get corrupted (I think when Coreplayer is running, you attach the device to a PC in USB disk mode and say yes to a prompted database rebuild). If you delete the library.db file with File Explorer or an equivalent program. it should rebuild it OK. Quite annoyingly, this file doesn't get deleted when Coreplayer is uninstalled, so an uninstall/reinstall doesn't resolve this.
Hi--I have used this a long time, suddenly it has become non-functional, I suspect due to the 1.7.32 update, but not sure.
--Android 4.3 (I've avoided 4.4 to retain full functionality of the SD card...)
--MX Pro 1.7.32
--Samsung Galaxy Note 10.1 2014
--Could not follow directions for alogcat because the nature of the problem makes MX unuseable once it crashes--there is no way to hit the "settings" button in MX Player Pro at that point.
PROBLEM
So, I bring up my file list as per normal. I click on a vid. The vid does not play. In fact, there is merely a blank screen. Eventually I'm returned to the home screen of the tablet and advised that MX Player has crashed. Sometimes, I don't even get the blank screen. It just automatically disappears and returns me to the tablet's home screen. Once that happens, the program never works again (until reinstalled or data cleared) and won't even let me into the program. Clicking its icon simply brings up a blank screen, then I get "Unfortunately, MX Player Pro has stopped..."
Troubleshooting
I have tried clearing cache, data and also reinstalling. The last two DO allow me to once again bring up the File List from "folders view." It looks normal once again. However, once I try to play vids, the same, exact result occurs, i.e., nothing actually plays and the program crashes with the screen going blank.
CLUES
a) I also have this on my phone, where it continues to work fine, but on my phone, I only have a handful of FLVs. The tablet has lots of other formats, primarily mp4. On my Note 4 phone, however, I'm running 4.4 KitKat.
b) If I access the video in a roundabout fashion, by clicking on it from a File Manager, the File Manager then offers to play it with the native vid player OR Mx Player. Then, it works fine. The exact same video. Of course, then I can't access any other parts of the MX P program, and I am no longer able to use the file list Mx Player P builds.
c) I tried playing with various settings, like hardware decoder, and what not, but it did not seem to help much.
My thought is that the version supporting Lollipop has done something that Samsung does not like in conjunction with 4.3
Any thoughts welcomed. TIA
monsieurms said:
Hi--I have used this a long time, suddenly it has become non-functional, I suspect due to the 1.7.32 update, but not sure.
--Android 4.3 (I've avoided 4.4 to retain full functionality of the SD card...)
--MX Pro 1.7.32
--Samsung Galaxy Note 10.1 2014
--Could not follow directions for alogcat because the nature of the problem makes MX unuseable once it crashes--there is no way to hit the "settings" button in MX Player Pro at that point.
PROBLEM
So, I bring up my file list as per normal. I click on a vid. The vid does not play. In fact, there is merely a blank screen. Eventually I'm returned to the home screen of the tablet and advised that MX Player has crashed. Sometimes, I don't even get the blank screen. It just automatically disappears and returns me to the tablet's home screen. Once that happens, the program never works again (until reinstalled or data cleared) and won't even let me into the program. Clicking its icon simply brings up a blank screen, then I get "Unfortunately, MX Player Pro has stopped..."
Troubleshooting
I have tried clearing cache, data and also reinstalling. The last two DO allow me to once again bring up the File List from "folders view." It looks normal once again. However, once I try to play vids, the same, exact result occurs, i.e., nothing actually plays and the program crashes with the screen going blank.
CLUES
a) I also have this on my phone, where it continues to work fine, but on my phone, I only have a handful of FLVs. The tablet has lots of other formats, primarily mp4. On my Note 4 phone, however, I'm running 4.4 KitKat.
b) If I access the video in a roundabout fashion, by clicking on it from a File Manager, the File Manager then offers to play it with the native vid player OR Mx Player. Then, it works fine. The exact same video. Of course, then I can't access any other parts of the MX P program, and I am no longer able to use the file list Mx Player P builds.
c) I tried playing with various settings, like hardware decoder, and what not, but it did not seem to help much.
My thought is that the version supporting Lollipop has done something that Samsung does not like in conjunction with 4.3
Any thoughts welcomed. TIA
Click to expand...
Click to collapse
Already there is a sticky thread in which I have already explained the procedure to collect the log immediately after crash.
Install MX Log collector app
Open It immediately after the MX Player Crash
Save the logs & Upload here
Does it crashes in all decoders?
If you are using H/W+ disable it & Check again.
long press the video & select Play using | S/W decoder
Check whether it still crashes or not.
ktsamy said:
Already there is a sticky thread in which I have already explained the procedure to collect the log immediately after crash.
Install MX Log collector app
Open It immediately after the MX Player Crash
Save the logs & Upload here
Does it crashes in all decoders?
If you are using H/W+ disable it & Check again.
long press the video & select Play using | S/W decoder
Check whether it still crashes or not.
Click to expand...
Click to collapse
It does not matter whether or not I use HW or SW decoding.
I upgraded the tablet to KitKat. That did not matter either.
I tried to upload the log files from MX Log here. Each time (3x now!) it gave me "invalid file" and refused to accept the upload. Oh, well.
monsieurms said:
It does not matter whether or not I use HW or SW decoding.
I upgraded the tablet to KitKat. That did not matter either.
I tried to upload the log files from MX Log here. Each time (3x now!) it gave me "invalid file" and refused to accept the upload. Oh, well.
Click to expand...
Click to collapse
You can upload to any file sharing network like dropbox & post the link here.
If you are not allowed to post the links, use masking like h**p://www.google.com
ktsamy said:
You can upload to any file sharing network like dropbox & post the link here.
Click to expand...
Click to collapse
It would not let me post links even with asterisks. I took out the http in its entirety. That didn't work either. I took out the dropbox reference as well. That did not work either. Have no clue at this point.
*Indeed, it wouldn't even let me quote your post with the partial link you referenced.
monsieurms said:
It would not let me post links even with asterisks. I took out the http in its entirety. That didn't work either. I took out the dropbox reference as well. That did not work either. Have no clue at this point.
*Indeed, it wouldn't even let me quote your post with the partial link you referenced.
Click to expand...
Click to collapse
Uncheck "auto parse links" at the bottom of the post reply page.
drop****box.com/s/l4mzbrlj0sh1ajf/build.prop?dl=0
drop******box.com/s/n18by6pewz706de/log.txt.gz?dl=0
another data point
FYI, just in case it helps, not as a "zing," BS Player works fine and normally. MX continues to work (on tablet and despite recent updates) only when a file is clicked from My Files file manager. It just won't deal with its own list of videos.
monsieurms said:
FYI, just in case it helps, not as a "zing," BS Player works fine and normally. MX continues to work (on tablet and despite recent updates) only when a file is clicked from My Files file manager. It just won't deal with its own list of videos.
Click to expand...
Click to collapse
@monsieurms There was an issue on Note 10.1 2014 European ROM and it might be fixed on 1.7.34
Please try latest version also try clear app data, MX Player's internal database looks like corrupted. This issue is also fixed but once corrupted database will never be recovered.
bleu8888 said:
@monsieurms There was an issue on Note 10.1 2014 European ROM and it might be fixed on 1.7.34
Please try latest version also try clear app data, MX Player's internal database looks like corrupted. This issue is also fixed but once corrupted database will never be recovered.
Click to expand...
Click to collapse
I tried it again--I'd already done that after upgrading to 1.7.3.4---but it did not help. I am not in Europe---North America.
monsieurms said:
I tried it again--I'd already done that after upgrading to 1.7.3.4---but it did not help. I am not in Europe---North America.
Click to expand...
Click to collapse
@monsieurms Would you send log again using 1.7.34? Thanks!
Given your comment on list db corruption and the fact that some vids in small directories do work, I tried copying all the vids to a new directory. That didn't work.
I cleared data again and also downloade the arm7 Neon custom codec specified in the Decoder settings. That did not help either. (It did find and install the codec.)
With the clues you gave me, I experimented a little. In particular, I noticed that some vids in small folders (small in terms of # of videos), played fine. I thought at first, as mentioned earlier in the thread, it was a difference in format. But as we've seen, all the videos play fine if accessed from File Manager--so that's not it. With the addition of your clue on database corruption, I thought perhaps the issue was folder size. I divided the one large folder into two, 50-50. That fixed it.
I would say you have still an issue here---the program chokes with a large of vids in the database. It doesn't seem to bother other programs, including the native video player and BS, and it didn't seem to bother MXp Pro until the recent wave of updates. So, I suspect something went wrong somewhere.
monsieurms said:
With the clues you gave me, I experimented a little. In particular, I noticed that some vids in small folders (small in terms of # of videos), played fine. I thought at first, as mentioned earlier in the thread, it was a difference in format. But as we've seen, all the videos play fine if accessed from File Manager--so that's not it. With the addition of your clue on database corruption, I thought perhaps the issue was folder size. I divided the one large folder into two, 50-50. That fixed it.
I would say you have still an issue here---the program chokes with a large of vids in the database. It doesn't seem to bother other programs, including the native video player and BS, and it didn't seem to bother MXp Pro until the recent wave of updates. So, I suspect something went wrong somewhere.
Click to expand...
Click to collapse
Would you send log using 1.7.34 or test version on following link?
https://sites.google.com/site/mxvpen/translation/test-build