Related
I was one of the many Evo users who's flash video was killed after the last Flash Player update. After much searching, couldn't find a single thing on why so many of us were having this problem so decided to do a little tinkering.
In my phone, I found a 2nd "libflashplayer.so" file under \system\lib\ which was also a different size from the one under \data\data\com.adobe.flashplayer\lib.
It also remained there after completely uninstalling the current version of Flash.
Installed the latest update and confirmed it as not working
Renamed the \system\lib\ file to "libflashplayer.bak" and flash instantly worked again! Putting the file back to normal instantly broke flash again too.
Also tried replacing it with the copy from \data\ (since it was the latest version) and flash still works just fine and didn't revert back to the older file after a reboot.
So - If any of you also have problems with the latest 10.2.157.51 version of Flash Player - check your \system\lib\ folder for this file and either rename or replace it and see if it solves this for you too
(Note - Always backup stuff first, and I am not liable if you fry your phone. ^_^)
It never ceases to amaze me up buggy and poorly controlled Flash is.
Thanks man.
Interesting i just updated flash NOW after trying twice before only to find video playback broken and it seems like they fixed it themselves now it is works, without doing anything on my end lol - Thank anyhow though!
Now you know why Steve Jobs doesn't want to see flash on Iphone or Ipad.
By the way - thx for the info.
To be fair, this is less adobe's fault, and more HTC's fault for putting the libraries in a read only filesystem. Even that would be alright if that path didn't superscede the ones in /data. I've been doing this on my own phone for a while now, and it does fix a lot of problems with flash. I wish more devs would take care not to put market apps that are subject to frequent updates in /system anyways. It doesn't really save any space in the long run.
Sent from my PC36100 using XDA Premium App
How are you guys renaming this file? When I try it says "insufficient permission". Tried with Astro.
zenmasta said:
How are you guys renaming this file? When I try it says "insufficient permission". Tried with Astro.
Click to expand...
Click to collapse
Found the answer here: http://forum.xda-developers.com/showthread.php?t=609866.
Download Etrong file explorer and give it root access.
Wouldn't upgrading to 10.3 fix the issue even easier?
mattykinsx said:
Wouldn't upgrading to 10.3 fix the issue even easier?
Click to expand...
Click to collapse
10.3 wasn't working for me either (I'm on the SprintLover's ROM), but after doing this, it works!
Thanks, OP!
I used ROOT EXPLORER to do this... thats the only program I know that works. it allows you to make the folder R/W instead of R/O then you can rename..
Im glad I found this.. now I am updates to 10.3 .. is there any difference in anything in 10.3 ?
Thanks! This fixed it on my EVO (running Fresh's 3.5.1 Froyo ROM), I used EStrongs file manager to make the necessary changes (you have to enable root options and mount system under settings first). Spent like half an hour trying to find a solution, since the search terms for the problem can be so generic ("Flash", "broken", "black box", etc. just returns a million different results).
WHY do some sites still say you need adobe flash when I go to them?? they worked with the old version.. could it be I have my browser agent set for desktop and the flash installed on the evo is reporting android?
My flash was also broken after the 10.2 (and 10.3) update. I used the method from the OP and it worked. Has anyone noticed though that after doing this fix if you have your "enable plugins" setting on your browser set to "on demand" that all flash content will say: "you need to update flash player to watch this video"? When the "enable plugins" setting is set to "always on" everything works flawlessly. I guess I should be happy that i got flash back at all but it kind of sucks because I like having my browser set to on demand so flash doesn't slow down my browsing experience.
At any rate big thanks to the OP
THANK YOU!!
This finally solved my problem, but in addition to renaming the libflashplayer.so file, I had to also rename libflashsnddec.so. Until I renamed the second file, Flash v10.3 kept giving me that blue Lego block with the question mark.
Thanks again!
Edit: Whoa...don't rename or delete libflashsnddec.so! Doing so causes both DolphinHD and the stock Android browser to abend on some websites (even simple ones like Amazon, etc.). I tried various combinations, uinstalls, reinstalls, clearing cache, backing out to an older version of 10.2 that worked previously, etc., and all ended up pointing to renaming/deleting libflashsnddec.so.
One question though. Would changing the .so to .bak affect when trying to update from the market? It worked like a charm by the way. Thanks.
Sent from my EVO using XDA App
Using that fix causes the stock browser and Dolphin Browser HD to abruptly close without even a Force Close warning.
I replaced the lib in /system/lib with the one from the latest Flash Player update and also placed the lib in /data/data/com.adobe.flashplayer/lib which was actually empty before I put the file there.
Edit: Nevermind. Got it. Removed the APK from /system/app and installed via Market. This placed the libs in the right folder and then I just copied them to /system/lib.
Edit 2: Alright, I'm trying to get this fix to work for my ROM so people don't have to do this manually.
So, I put the files in /data/data/com.adobe.flashplayer/lib so they get copied over when the ROM is flashed by the updater-script. However if I do this while the install_flash_player APK is present in /system/app, it seems to erase the contents of that folder causing Flash Player to not work again. I need to find a way to make it so the libs stay in /data/data/com.adobe.flashplayer/lib.
Any suggestions?
does your "new" flash lib file read
01 OCT 09 6.87 MB
I moved the file to the proper folder using r/o and root explorer, and rebooted
both files are in place, but I still get the blue ? mark on certain sites
Hello all, this morning I was using the newest version of the ES File Explorer, and I selected a new audio file I made to use as a notification tone. I played it in ES, and used the "Set as Notification" option. it said successful, so I went to make sure it took, and now any time I try to change the tone (tap on the Notification Sound button to browse the list) I get a FC in android.process.media. Any idea what happened or how i can fix it? I uninstalled ES but that didn't help.
Maybe try wipe dalvik and cache
Spliff_Sanders said:
Hello all, this morning I was using the newest version of the ES File Explorer, and I selected a new audio file I made to use as a notification tone. I played it in ES, and used the "Set as Notification" option. it said successful, so I went to make sure it took, and now any time I try to change the tone (tap on the Notification Sound button to browse the list) I get a FC in android.process.media. Any idea what happened or how i can fix it? I uninstalled ES but that didn't help.
Click to expand...
Click to collapse
Sent from Mako⁴
spicediablo said:
Maybe try wipe dalvik and cache
Sent from Mako⁴
Click to expand...
Click to collapse
My phone is completely stock right now, so I guess I will have to unlock the bootloader, etc. I'll try it tonight when I get home.
Try restarting your phone first and see if it solves the problem
Spliff_Sanders said:
My phone is completely stock right now, so I guess I will have to unlock the bootloader, etc. I'll try it tonight when I get home.
Click to expand...
Click to collapse
Sent from Mako⁴
spicediablo said:
Try restarting your phone first and see if it solves the problem
Sent from Mako⁴
Click to expand...
Click to collapse
Restarting did not help, but strangely deleting that sound file did....I guess there's something about it my phone doesn't like. Thanks for the suggestions though. :good:
Yes, try the easy way before the hard way
Spliff_Sanders said:
Restarting did not help, but strangely deleting that sound file did....I guess there's something about it my phone doesn't like. Thanks for the suggestions though. :good:
Click to expand...
Click to collapse
Sent from Mako⁴
After searching around for similar issues (and finding none with MTP devices, all with USB Mass Storage), I have concluded that I need to ask here for help. I recently tried to delete an ond backup through a computer (Win7) and after I deleted it, it stll showed up on my N7. I've tried every method I can think of for deleting the files, but they always re-appear after I reboot. When I try to delete them through Astro the progress bar stays at 0%. The only articles that I've found with "corrupt file" and "mtp" as search keywords are articles about how mtp issupposed to prevent this from happening. Please help!
Have you tried to use Solid Explorer? It is much more advanced than any other file manager I have encountered.
Other than that, command line and wiping the partition.
Sent from my LG-P999 using xda premium
Well, I still can't delete the files, but at least Solid is giving me a "can't delete file" error. I guess I'll have to try to back up my SD storage and reformat. Oh well. Thanks anyways.
Ok, if for any reason a standard re-format doesn't work, PM me, I have something which will do a bit more.
Sent from my LG-P999 using xda premium
When I connect my Nexus 4 to my PC things get a little weird. I've attached an image to show my problem. Some folders (for instance TitaniumBackup) show up as 0kb files. Also, some files that I deleted like the LTEhybrid zip still show up in explorer. Trying to delete the file does nothing in explorer, likely because it doesn't exist. Sometimes I can't copy files to or from my phone. I'll get an error that my phone is no longer responding or the copy dialog box will simply disappear. I'm hoping this issue can be resolved without restoring to factory settings.
I should note that changing to PTP seems to function better, but I can only access DCIM and Pictures.
Debugging on or off makes no difference. I'm running stock rom 4.3 rooted, although I've had this problem for as long as I can remember. The file system works perfectly fine on any app on my nexus 4. Does anyone have any ideas as to what is wrong or how it can be fixed?
Thanks.
I've not found a way to fix as of yet. It's a bug in mtp.
A quick reboot will force it to update properly then you can get your files. But the bug will happen again
Sent from my Nexus 4 using xda app-developers app
Alex240188 said:
I've not found a way to fix as of yet. It's a bug in mtp.
A quick reboot will force it to update properly then you can get your files. But the bug will happen again
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Rebooting does not help. I've tried using a program named MyPhoneExplorer which seems to work well. I can copy things to and from my phone's storage and everything is displayed accurately.
Would it be safe to assume it's a problem with windows and not with my nexus?
Hi, I just wondered if anyone else is having issues after the Kit Kat update? Maybe we could start a list here.... I'm on the stock recovery and not rooted (and have been since day one). If you add issues, please could you tell everybody whether or not you're rooted etc.
1.Can't write files so MicroSD card using file manager apps (but I can do it if I connect the Note to a PC in MTP mode, then drag and drop files from internal to external storage
2. MC3 doesn't work - this one may bring about the end of civilisation as we know. No really, it might.
3. Stuttering when playing movies over HDMI to a TV (this was present in 4.3 too, but not 4.2.2)
4. Options to use auto-correct, double tap of the space bar etc when a hardware keyboard is connected do not work (this extra menu only appears when your keyboard is connected).
5. Various slow downs and pauses.
6. Battery life, as mentioned by foxxorrrorororors (approximate spelling)
7. GPS - still pretty bad for me, even with GPS Test....
Anybody else got the same, or perhaps other issues?
*UPDATE* I just tried a full factory reset and the microSD card write issue remains. You also can't write files to an external USB drive either. Clearly Nvidia doesn't have a very thorough procedure for testing these updates before pushing them to our devices. Muppets.
**UPDATE** If you are rooted, the tutorial in this thread fixes the write to SD card problem as far as I can tell http://forum.xda-developers.com/showthread.php?t=2617921
1. jup, vlc cant access sdcard either - seems they changed something here.
2. na
3. na
4. na, using swiftkey
5. not yet
6. maybe, time will show
7. jup
wonders who this foxxoorrroxororors person you speak of is.
Sent from my TegraNote-P1640 using XDA Premium HD app
foxorroxors said:
wonders who this foxxoorrroxororors person you speak of is.
Sent from my TegraNote-P1640 using XDA Premium HD app
Click to expand...
Click to collapse
Sorry dude, I couldn't remember how to spell your username - too many letters for me
cars10k, thanks for responding - do you mean MC3 does work for your, or that you haven't tried it? Sorry if I'm being a bit dumb
Writing to Sd card was killed by Samsung in their KitKat update - apparently the permissions are set wrong in platform.xml. I don't know if this is the case for us. I can't even use Helium Backup to write to the MicroSd card. Darn.
yeah my sd cards isnt working either, moving or with es file man. that sucks i use it daily.....
Sent from my TegraNote-P1640 using XDA Premium HD app
did not try MC3.
surprisingly, mx player works for me, even with files on the sdcard.
cars10k said:
did not try MC3.
surprisingly, mx player works for me, even with files on the sdcard.
Click to expand...
Click to collapse
Thanks
Reading files from the MicroSD card works fine, writing does not unfortunately
foxorroxors said:
yeah my sd cards isnt working either, moving or with es file man. that sucks i use it daily.....
Sent from my TegraNote-P1640 using XDA Premium HD app
Click to expand...
Click to collapse
Yeah, I use it daily too. Really frustrating. I'm tempted to cut my nose off to spite my face and just take the tablet back to Currys. There's no point Nvidia throwing out updates with newer versions of android and extra features if they break basic stuff in the process (USB OTG hard drive unmounting being one example of something that was broken by the 4.3 update).
foxorroxors said:
yeah my sd cards isnt working either, moving or with es file man. that sucks i use it daily.....
Sent from my TegraNote-P1640 using XDA Premium HD app
Click to expand...
Click to collapse
I think it's actually a KitKat thing: http://www.androidpolice.com/2014/0...at-and-even-samsung-may-be-implementing-them/
---------- Post added at 09:14 AM ---------- Previous post was at 09:07 AM ----------
Ouzo said:
5. Various slow downs and pauses.
Click to expand...
Click to collapse
Do you mean like the whole tablet becomes unresponsive at times? You can't even get to the home screen or turn the screen off? Then after anything from 30 second to 2 minutes it just comes alive again? I was experiencing that even before the update - with very few apps installed (same as my Sammy 7.7 which never froze). I've reset to factory and haven't had it again... Yet...
cars10k said:
did not try MC3.
surprisingly, mx player works for me, even with files on the sdcard.
Click to expand...
Click to collapse
Ditto for me. I keep my vids on the SD card. Watched a couple today. Oh, and I've never rooted this; still stock.
fbales said:
Ditto for me. I keep my vids on the SD card. Watched a couple today. Oh, and I've never rooted this; still stock.
Click to expand...
Click to collapse
Here's a thread about how to solve the problem of not being able to write to the SD card. You need to root first though unfortunately. On the plus side there's absolutely no reason why Nvidia Shouldn't push a fix out very quickly if they are paying attention.
http://forum.xda-developers.com/showthread.php?t=2617921
After rooting I used ES File Explorer. Before you can do anything, in ES File explorer turn on Root Explorer in the side menu by tapping the button next to that entry, then tap on the Root Explorer text itself to enter the options menu for root access. In the menu that pops up tap "Mount R/W" and press the radio button to mount "/system" as RW, then press ok. After that you can follow the instructions to edit the Platform.xml as laid out in the link above. I used ES File Explorer's in built text editor to do this. After you've made the changes to platform.xml, you to set the correct permissions for the file, again using ES File Explorer (long press platform.xml, press the menu button in the bottom right hand corner, then tap properties) change the permissions to rw-r-r-. That should be it, in theory you can now write files to external storage.
Ouzo said:
Here's a thread about how to solve the problem of not being able to write to the SD card. You need to root first though unfortunately. On the plus side there's absolutely no reason why Nvidia Shouldn't push a fix out very quickly if they are paying attention.
http://forum.xda-developers.com/showthread.php?t=2617921
After rooting I used ES File Explorer. Before you can do anything, in ES File explorer turn on Root Explorer in the side menu by tapping the button next to that entry, then tap on the Root Explorer text itself to enter the options menu for root access. In the menu that pops up tap "Mount R/W" and press the radio button to mount "/system" as RW, then press ok. After that you can follow the instructions to edit the Platform.xml as laid out in the link above. I used ES File Explorer's in built text editor to do this. After you've made the changes to platform.xml, you to set the correct permissions for the file, again using ES File Explorer (long press platform.xml, press the menu button in the bottom right hand corner, then tap properties) change the permissions to rw-r-r-. That should be it, in theory you can now write files to external storage.
Click to expand...
Click to collapse
Thank you, thank you. I just spent about 3 hours trying to edit the file, but I couldn't figure out how to get the permissions to do so. That did it.
Brew
Ouzo said:
Hi, I just wondered if anyone else is having issues after the Kit Kat update? Maybe we could start a list here.... I'm on the stock recovery and not rooted (and have been since day one). If you add issues, please could you tell everybody whether or not you're rooted etc...
Click to expand...
Click to collapse
Clear your dalvik cache and normal cache using the recovery kernel options.
e8hffff said:
Clear your dalvik cache and normal cache using the recovery kernel options.
Click to expand...
Click to collapse
Haha I just FAC reset before I read this, but everything is nice and spangly after reset, try SD card now
Sent from my TegraNote-P1640 using XDA Premium HD app
foxorroxors said:
Haha I just FAC reset before I read this, but everything is nice and spangly after reset, try SD card now
Sent from my TegraNote-P1640 using XDA Premium HD app
Click to expand...
Click to collapse
Google's KitKat is supposed to be restrictive on allowing apps to be installed to sdcard1, but you maybe able to trick installs using symbolic linked folders.
Damn this game mapper is awesome arcane legends rocks with it
Sent from my TegraNote-P1640 using XDA Premium HD app
e8hffff said:
Clear your dalvik cache and normal cache using the recovery kernel options.
Click to expand...
Click to collapse
Wiping dalvik cache isn't an option in the stock recovery on Kit Kat. I just looked a few mins ago. Wiping cache is there and I used it, but it still isn't solving the slow booting/loading time.
titetanium said:
Wiping dalvik cache isn't an option in the stock recovery on Kit Kat. I just looked a few mins ago. Wiping cache is there and I used it, but it still isn't solving the slow booting/loading time.
Click to expand...
Click to collapse
Ok You'll need root mode and either use a custom recovery partition options.
e8hffff said:
Ok You'll need root mode and either use a custom recovery partition options.
Click to expand...
Click to collapse
That's fine, I'm not going bother with rooting, I'm rolling back to stock 4.3. This whole kit kat update left a really sour taste in my mouth and rooting the tablet just to put in a dirty hack to fix it is ugly, IMHO. The fix isn't even guaranteed to solve it completely as others have expressed other issues. At least with 4.3, I know I didn't have much problems with it, and I need my sdcard for hosting files (25GB worth) for an app that putting them in the cloud isn't workable when I can't access them on the road or at places sans wifi.
titetanium said:
That's fine, I'm not going bother with rooting, I'm rolling back to stock 4.3. This whole kit kat update left a realthy sour taste in my mouth and rooting the tablet just to put in a dirty hack to fix it is ugly, IMHO. The fix isn't even guaranteed to solve it completely as others have expressed other issues. At least with 4.3, I know I didn't have much problems with it, and I need my sdcard for hosting files (25GB worth) for an app that putting them in the cloud isn't workable when I can't access them on the road or at places sans wifi.
Click to expand...
Click to collapse
Agreed. While I think Nvidia have done a great job at pushing out updates in a timely manner, the quality of those updates has been poor. Each time they have added some useful features, they have also either introduced new bugs or failed to fix existing bugs. On the one hand, I want the latest update due to the game mapper functionally and the fact that they fixed the bug regarding unmounting external hard drives (which they introduced in 4.3), but i don't want to have to employ a workaround to use my microSD card or an external hard drive freely. It's such a shame as this device has so much potential. I don't think I'll be buying the next Nvidia device.
To roll back to 4.3 involved installing unsigned drivers on my PC (a real no no) and unlocking the boot loader (which means my warranty is now void). What a stupid end user experience Nvidia and Google have created between them. At a time when I want to move away from rooting my device and flashing custom recoveries and ROMs they are actually making doing so more and more of a necessity. If I'm going to have to keep tinkering with my devices to get them to function in the way I want, then I would like a better OS that does less dodgy stuff with my data and is truly open....