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
Touch HD (Blackstone)
Rom: Dutty 6.1
I've spent several frustrating weeks now trying to get coreplayer to work properly.
Either the video playback is really choppy with frames frequently dropped or the video is out of sync with the audio.
I've gone through loads of configuration suggestions that I've found online, Before each test I've reset the settings to default by clearing out the config.xml file.
I've gone through the following Roms, in case it could be Rom related
Kwbr_Topix_3.5.10_Sense2.5_WM6.5
TOPIX_Kwbr_Win 6.5_Ver_21877_TouchFLO3D 2.1.38411.0
RUU_Duttys_HD_V3.9 _XT_Turbo_5.2.21051.1.6.4_1.59.709.0_Radio_52.62.25.34_1.14.25.24_V2.1
I've tested the wmv file on the phone memory to confirm it wasnt an issue with the speed of the storage card.
I've contacted coreplayer and submitted a ticket... All I got back from them was an automated response a week later saying my ticket had been closed.
Id also like to try setting up Coreplayer v1.3.5, where can I get a version to install?
Does anyone have any other suggestions as to how I can get coreplayer to work?
Thanks
I am having a problem with any media player except the stock one. I want to use a 3rd party media player, so that I don't have to convert my movies to something compatible with the stock media player. the problem is whenever I use a 3rd party media player, I hook the phone to my tv, and the movie plays for a few minutes, then it stops, and loses my place, this is very irritating. This doesn't happen on the the stock media player. Does anyone have any ideas? I have tried at least 6 third party media players, and they all stop every few minutes... For now I am just converting my movies for use with the stock player, but this is time consuming.
it depends on what app you're trying to use. you might want to see if there's an extra codec pack. i know that mobo player has a lot of add-on codec packs. if this is the case and the dev is smart, the codec packs are usually in the market, just like the original program.
also, you may want to try something with soft decoding included, if you're not already.
moe. said:
it depends on what app you're trying to use. you might want to see if there's an extra codec pack. i know that mobo player has a lot of add-on codec packs. if this is the case and the dev is smart, the codec packs are usually in the market, just like the original program.
also, you may want to try something with soft decoding included, if you're not already.
Click to expand...
Click to collapse
Most of the players had soft decoding, and it isn't a codec pack, the videos play, but suddenly stop. The only one that doesn't do that is the stock one. Has anyone else had this problem? Do you all use the stock player?
does it only do it when using tv out or does it happen on the device screen, also? what rom/kernel are you using?
Have you. Tried remote for vlc? I think you can play media on the sd card. Not sure haven't tried it but worth a shot if you haven't.
sent from my ice cream sandwhich MT4GS
moe. said:
does it only do it when using tv out or does it happen on the device screen, also? what rom/kernel are you using?
Click to expand...
Click to collapse
So it seems to only do it when using the tv out function, which is really cruddy, because I don't want to watch movies on my tiny phone, I want to watch them on the big tv. I am using Bulletproof 1.0, and the stock kernel. I am going to try remote for vlc right now, but I am thinking the problem is something to do with the tv out function.
I understand the frustration. My educated guess would have to be that it has something to do with a kernel conflict. Try a different rom and/or kernel. There are, also, some updates for bulletproof now, too.
Sent from my myTouch_4G_Slide using XDA App
moe. said:
I understand the frustration. My educated guess would have to be that it has something to do with a kernel conflict. Try a different rom and/or kernel. There are, also, some updates for bulletproof now, too.
Sent from my myTouch_4G_Slide using XDA App
Click to expand...
Click to collapse
If I remember correctly this happened on other roms too, but I will try again. I tried the new bulletproof, but I liked the old one better. I haven't tried a different kernel though, so I will start flashing different kernel/rom combos, to see if it makes a difference.
yellowjacket1981 said:
So it seems to only do it when using the tv out function, which is really cruddy, because I don't want to watch movies on my tiny phone, I want to watch them on the big tv. I am using Bulletproof 1.0, and the stock kernel. I am going to try remote for vlc right now, but I am thinking the problem is something to do with the tv out function.
Click to expand...
Click to collapse
Sorry, I missed this thread. I'm kinda skimming over the boards while i'm doing paperwork and such, so i'm skipping over things and not realizing it. (hate januaries, always so busy)
Anyways, it's a codec issue. You'll only get the problem when outputting to tv - and soft-decoding only solves part of the problem.
What's happening is your file format is too far away from what the hardware can handle easily while it's also trying to feed the video out and keep the screen active on the device.
Even though you check soft-decoding in the app, without proper codecs installed it defaults some or all of the work back to the hardware.
I use Mobo Player, free video app and is hands-down my favorite one on Android. It lets you choose soft-decoding in the settings menu, but they also supply a codec you can find in the market.
I'm using the ARM V7_VFP codec from the same author as Mobo Player, and don't have a problem with it. When I do reflash and forget to install it then it goes back to randomly cutting out while i'm enjoying my movie/show or whatever.
Edit: This Google Market Link will get you to the right codec for our device.
I suppose I should have mentioned something about it in my ROM thread, since I included it in Bulletproof for that reason - but, there's a lot going on here lol.
I should have seen this thread yesterday, but I suppose i'm looking at it the wrong way since I get to skim the forums while i'm getting work done. (as opposed to not being able to browse them at all.)
Anyways, Mobo Player is free, and so is the codec, so all you lose for trying is time - give it a shot and see where it gets ya.
---------- Post added at 02:39 PM ---------- Previous post was at 02:33 PM ----------
moe. said:
I understand the frustration. My educated guess would have to be that it has something to do with a kernel conflict. Try a different rom and/or kernel. There are, also, some updates for bulletproof now, too.
Sent from my myTouch_4G_Slide using XDA App
Click to expand...
Click to collapse
Nah, I haven't made any updates to Bulletproof recently, though i'd like to squeeze one out around work soon.
Blue6IX said:
Sorry, I missed this thread. I'm kinda skimming over the boards while i'm doing paperwork and such, so i'm skipping over things and not realizing it. (hate januaries, always so busy)
Anyways, it's a codec issue. You'll only get the problem when outputting to tv - and soft-decoding only solves part of the problem.
What's happening is your file format is too far away from what the hardware can handle easily while it's also trying to feed the video out and keep the screen active on the device.
Even though you check soft-decoding in the app, without proper codecs installed it defaults some or all of the work back to the hardware.
I use Mobo Player, free video app and is hands-down my favorite one on Android. It lets you choose soft-decoding in the settings menu, but they also supply a codec you can find in the market.
I'm using the ARM V7_VFP codec from the same author as Mobo Player, and don't have a problem with it. When I do reflash and forget to install it then it goes back to randomly cutting out while i'm enjoying my movie/show or whatever.
Edit: This Google Market Link will get you to the right codec for our device.
I suppose I should have mentioned something about it in my ROM thread, since I included it in Bulletproof for that reason - but, there's a lot going on here lol.
I should have seen this thread yesterday, but I suppose i'm looking at it the wrong way since I get to skim the forums while i'm getting work done. (as opposed to not being able to browse them at all.)
Anyways, Mobo Player is free, and so is the codec, so all you lose for trying is time - give it a shot and see where it gets ya.
---------- Post added at 02:39 PM ---------- Previous post was at 02:33 PM ----------
Nah, I haven't made any updates to Bulletproof recently, though i'd like to squeeze one out around work soon.
Click to expand...
Click to collapse
And another job well done.
Sent from my myTouch_4G_Slide using XDA App
Blue6IX said:
Sorry, I missed this thread. I'm kinda skimming over the boards while i'm doing paperwork and such, so i'm skipping over things and not realizing it. (hate januaries, always so busy)
Anyways, it's a codec issue. You'll only get the problem when outputting to tv - and soft-decoding only solves part of the problem.
What's happening is your file format is too far away from what the hardware can handle easily while it's also trying to feed the video out and keep the screen active on the device.
Even though you check soft-decoding in the app, without proper codecs installed it defaults some or all of the work back to the hardware.
I use Mobo Player, free video app and is hands-down my favorite one on Android. It lets you choose soft-decoding in the settings menu, but they also supply a codec you can find in the market.
I'm using the ARM V7_VFP codec from the same author as Mobo Player, and don't have a problem with it. When I do reflash and forget to install it then it goes back to randomly cutting out while i'm enjoying my movie/show or whatever.
Edit: This Google Market Link will get you to the right codec for our device.
I suppose I should have mentioned something about it in my ROM thread, since I included it in Bulletproof for that reason - but, there's a lot going on here lol.
I should have seen this thread yesterday, but I suppose i'm looking at it the wrong way since I get to skim the forums while i'm getting work done. (as opposed to not being able to browse them at all.)
Anyways, Mobo Player is free, and so is the codec, so all you lose for trying is time - give it a shot and see where it gets ya.
---------- Post added at 02:39 PM ---------- Previous post was at 02:33 PM ----------
Nah, I haven't made any updates to Bulletproof recently, though i'd like to squeeze one out around work soon.
Click to expand...
Click to collapse
Thanks, I am flashing bulletproof 1.1 again, and hoping to get things running well. I will keep you updated. I was running bulletproof 1.0, so I think that was what they were talking about , when they said there was an update.
So, you've motivated me to look a little deeper.
Looks like Wifi-calling is also causing a whole mess of trouble on the device.
It can't do something, and keeps trying, which is part (if not all of) why the system can't keep up with a movie.
I just removed it from my build a little while ago after I couldn't get it to play nice, and I can't describe how much more smoothly my system is running without it (minus a couple of hiccups because it's not there anymore and things are expecting it to be)
I'm going to rebuild a Bulletproof distribution without the wifi-calling and see what kind of data I can dredge up to compare to - but I have a feeling this is the other piece of the puzzle for why it's not working right.
I'm on the same version of wifi-calling that has been around for a while - I think there was an update to it in one of the OTA updates? Can't remember.
I'm pushing the edge of exhaustion, it's been a few days, so i'm probably not gonna get to it tonight, but it's the next thing on my list. Figured i'd mention it here in case anyone wanted to experiment with it in the meanwhile.
I'm not kidding when I say it's literally like a whole new device without wifi calling - I honestly can't believe what a difference it's absence is making.
Blue6IX said:
So, you've motivated me to look a little deeper.
Looks like Wifi-calling is also causing a whole mess of trouble on the device.
It can't do something, and keeps trying, which is part (if not all of) why the system can't keep up with a movie.
I just removed it from my build a little while ago after I couldn't get it to play nice, and I can't describe how much more smoothly my system is running without it (minus a couple of hiccups because it's not there anymore and things are expecting it to be)
I'm going to rebuild a Bulletproof distribution without the wifi-calling and see what kind of data I can dredge up to compare to - but I have a feeling this is the other piece of the puzzle for why it's not working right.
I'm on the same version of wifi-calling that has been around for a while - I think there was an update to it in one of the OTA updates? Can't remember.
I'm pushing the edge of exhaustion, it's been a few days, so i'm probably not gonna get to it tonight, but it's the next thing on my list. Figured i'd mention it here in case anyone wanted to experiment with it in the meanwhile.
I'm not kidding when I say it's literally like a whole new device without wifi calling - I honestly can't believe what a difference it's absence is making.
Click to expand...
Click to collapse
You deserve your rest! I just wanted to report back, that I am still having the same problem. I updated to bulletproof 1.1, and installed the codec that you linked to, still had the problem. The movie will play for a few minutes, and then suddenly stop. I then installed all the codecs for mobo player, and still nothing. I can't remember if this happened on the stock rom or not. My boyfriend is still on the stock rom, so when he come by tonight, I will test a 3rd party media player on his, to see if there is still the same problem. If it works on stock, I may just flash back to stock for now, to save me the trouble of converting a lot of my movies. Thanks for all your help Blue.
Also, I can't wait to see the rom without wifi calling!
If you have the android sdk set up on a computer you can plug into, set your phone to usb-debugging/charge only and plug it in and watch the output.
You'll see the wifi calling app (kineto) going nutzo - i've been trying to mak it behave for a while because some people mentioned liking using it (even though it doesn't work so well) but tonight was the last straw with it.
Now that it's gone from my device, I can't tell you how much smoother it's been running. The whole output on my screen going all the way back to before I posted last (so, i've moved past the buffer in the log) and not one error msg.
That was unheard of with the wifi calling app on the device, and it made it look like it was more then one app causing the problem. Got rid of that one, and it solved pretty much the whole thing.
I wasn't having an issue with it crashing out of the movie earlier today - but I just set a friend of mine up with rooting his new MT4GS, so I flashed mine fresh alongside when we did his yesterday (day before?) ...
You might wanna try just axing that real quick before you go flashing all over again - just a thought
Finishing up my last call of the night, i'll catch up with you all tomorrow - hope it works out for you.
Blue6IX said:
If you have the android sdk set up on a computer you can plug into, set your phone to usb-debugging/charge only and plug it in and watch the output.
You'll see the wifi calling app (kineto) going nutzo - i've been trying to mak it behave for a while because some people mentioned liking using it (even though it doesn't work so well) but tonight was the last straw with it.
Now that it's gone from my device, I can't tell you how much smoother it's been running. The whole output on my screen going all the way back to before I posted last (so, i've moved past the buffer in the log) and not one error msg.
That was unheard of with the wifi calling app on the device, and it made it look like it was more then one app causing the problem. Got rid of that one, and it solved pretty much the whole thing.
I wasn't having an issue with it crashing out of the movie earlier today - but I just set a friend of mine up with rooting his new MT4GS, so I flashed mine fresh alongside when we did his yesterday (day before?) ...
You might wanna try just axing that real quick before you go flashing all over again - just a thought
Finishing up my last call of the night, i'll catch up with you all tomorrow - hope it works out for you.
Click to expand...
Click to collapse
I do have sdk installed and working on my computer, but I am still a newb when it comes to actually using it lol. Just so you know, I had my boyfriend try to run a movie with tv out on my tv, with mobo player, and it crashed too, and he is on stock. The problem is definitely not rom related. I am going to try getting rid of wifi calling and see if that improves anything. I will let you know.
yellowjacket1981 said:
I do have sdk installed and working on my computer, but I am still a newb when it comes to actually using it lol. Just so you know, I had my boyfriend try to run a movie with tv out on my tv, with mobo player, and it crashed too, and he is on stock. The problem is definitely not rom related. I am going to try getting rid of wifi calling and see if that improves anything. I will let you know.
Click to expand...
Click to collapse
Appreciate the confirmation it's not ROM related - It's one thing for me to say it as the creator of the ROM, another thing for a third party to verify it.
Are you on a windows machine? If so:
In your SDK folder, go to the 'tools' folder. In it you will find a file called "ddms.bat"
Open this, and it will launch a DOS window, which then launches a GUI after a few mins.
Welcome to the dalvik debug monitor window.
Now what you do, is go to settings on your device. In the "Connect to PC" option, set it to "charge only"
Then, back in the settings menu, go to "applications" then "development" and make sure "USB debugging" is checked.
(also might be a good idea to check "stay awake")
Now you can plug the doubleshot into the computer without having it disable your sdcard access, and let it just run like normal.
Plug it into the computer, and you will see it pop up in the list in the dalvik debug monitor.
You can watch what it's doing and see if you have any issues.
It might help you to track down this problem, and see about a resolution. DDMS is one of the primary troubleshooting tools you should be using to figure out what's going on on your device.
Often times I just let one of my doubleshots stay plugged in to ddms while i'm sitting here, and just have the log running while i'm working on the laptop next to the pc. Familiarizing yourself with the device in this fashion will help a lot in terms of development, but even as just a user you will get a huge understanding of what the device is doing.
The first time it injected the A-GPS data while I was connected to DDMS was awesome - little things like that give you a huge understanding of what's going on.
Also, it'll keep running if you reboot the device while it's connected - lets you see what happens when it shuts down but also what happens when it first boots up.
----
Removing wifi calling has been such a great move - trying to fight with it and getting it to play nice is like trying to get water to flow uphill.
I just threw together a flashable Bulletproof zip without it and am getting ready to flash it to my phone, we'll see how this goes but I have a feeling that the wifi calling app is a large part of the remaining problem once the correct codec is installed and you have soft-decoding active.
Okay, something isn't right now.
For a while Moboplayer was working fine with soft decoding and output to television, but now I can't get too far before it fatally crashes out.
I am wracking my brain trying to figure out why it was working for a while but now is not - meantime, the generic player will output to television without crashing...but suffers the odd video issue present with hardware decoding that makes it not so great. Gets artifacts on-screen and doesn't properly display the video on the television smoothly, yet appears fine on the device itself.
There is an answer somewhere - i'm not sure what it is, but it'll be found ... we just need to keep trying.
Either need to figure out why any aftermarket player crashes (I think it has something to do with audio - but that could be misleading since the headphones jack we are using for video output counts as audio - at least in the logs)
Ive had the same issue with mx player,mobo player,v player with just the device itsel. I didnt have the codec packs for mx or mobo player installed at the time tho. I got vplayer working by changing the buffer & disabling hardware decoding. Here are the specs for the video I was playing at the time: Video 724 kbps xvid Audio 5.1 AC3 Resolution 640x272 2.35:1
pimppoet said:
Ive had the same issue with mx player,mobo player,v player with just the device itsel. I didnt have the codec packs for mx or mobo player installed at the time tho. I got vplayer working by changing the buffer & disabling hardware decoding. Here are the specs for the video I was playing at the time: Video 724 kbps xvid Audio 5.1 AC3 Resolution 640x272 2.35:1
Click to expand...
Click to collapse
Working as in it'll play the whole video through without crashing out?
Blue6IX said:
Working as in it'll play the whole video through without crashing out?
Click to expand...
Click to collapse
yea...the apps never force closed only randomly stopped for me intially but. ok so far now with no stops. I havent watched ne other movies since then to really test it out. I also found an
alpha build of vlc player here http://dl.cvpcs.org/android/test/common/VLC-noneon.apk
I have posted before with no luck, but hoping someone has found a fix for it in the past few months..
Whenever I use my browser (Boat Browser or all the others I've tried) to watch videos, I no longer have the option to "Open" or "Download" the file, it just automatically plays in the built in media player.. I want to use MX Player..I used to have the option of what to do with the video, but same thing happening with built in player..I have made sure all defaults were cleared, and I even tried uninstalling the Gallery that is linked with the camera.. No luck.
I'm running 4.3 on my tablet, and still have the option so obviously it is a 4.4 issue, and not a browser issue. So just hoping I get lucky and someone has found a fix for it.. Appreciate any feedback!
Bump after edit
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