Best Flash Player? - Tilt, TyTN II, MDA Vario III General

I am confused on which flash player I should install on my device to get the most functionality out of. I am visiting quite a few websites that require a flash plugin. Should I install Macromedia's flash player 7 or should I install Adobe Lite 2.1? Are they very similar when it comes down to functionality or do these two flash players I mentioned have very different purposes..?

Related

[Q] Flash 10.1 on Elcair

I recently sideloaded flash 10.1 on Eclair. It installed with now errors. I was just wondering if anyone know why it still will not work when I browse website that support flash 10.1. Is there a perticular browser I should be using? Or is it not supported on eclair? Thanks
if you are able to go through android sdk change list, you will see Flash is only supported starting from Android 2.2.

Is there any method to install Flash Player in our Motorola Razr i?

I want to know if there is a new method to install Flash player and if you do not have to tell me where there is a thread to install it ... many thanks!:good:
There was never a flash player compiled for the x86 android platform .. so there is nothing to tweak. And there will be no flash for x86 since Adobe pulled the plug on the Flash player for Android.We will have to learn how to live w/o it.
ro_explorer said:
There was never a flash player compiled for the x86 android platform .. so there is nothing to tweak. And there will be no flash for x86 since Adobe pulled the plug on the Flash player for Android.We will have to learn how to live w/o it.
Click to expand...
Click to collapse
There was a flash player on the "Orange San Diego" (first Intel phone).
But it was for android 2.x
Some tried to use it but doesn't work, as far as I know
http://forum.xda-developers.com/showthread.php?t=1952878

[Q] General questions about ROMs and the rooting how-to

Hi, many thanks for the great and detailed how-to. However, I think it may lack some answers to a few important questions that people who come from other phones could ask. Until now, I've been used to rooting and flashing my Galaxy Nexus which appears to be rather different from the methods on this phone. Anyway here goes: I just got my Z3 Compact. I'm willing to give the stock UI a try, especially because it has some very nice features (noise removal on camera, STAMINA mode) and a clean enough look, however I need root and don't want to put up with some of the preinstalled apps. I can then either create my own pre-rooted image or flash a custom, stock-based ROM w/ root such as SLiM. Here are my questions:
Based on the how-to, if I want to install a custom ROM such as SLiM, at which step do I need to flash it? In particular, that ROM requires "root and recovery", does that really mean that I first have to root a stock ROM and install a new pre-rooted ROM + recovery, and only then flash SLiM from recovery, or can I install it during the various stages of the how-to?
I was used to TWRP recovery remaining on my Galaxy Nexus for pretty much all its life. I don't understand: why are there so many different recoveries for the Xperia phones and why do you apparently need to flash them so often? Can't you put one there and never touch it again? Why do they sometimes come with the ROM?
Why do some custom ROMs have requirements to be running a specific version of the firmware to be installed? Can't they just be flashed from recovery? Oh and btw, is there a difference between a ROM and a "firmware" as far as Xperia-specific vocabulary goes?
Putting those questions into words, I realize I may be missing something crucial about these phones that ties recovery, ROM and kernel together in a way I'm not used to. If there is any documentation about how these general concepts work on Sony phones, I'd be happy to read it!
Thanks in advance.
Answering myself, hoping it can be helpful to people who are new to the Z3C and wondering about the same questions:
SLiM is a complete ROM, it only requires "Root and Recovery" to mean that it must be flashed from recovery -- and recovery must be installed from root anyway.
If you want to install SLiM on your first root, you must follow the how-to down to the point where you've downgraded, rooted and installed XZDualRecovery. After that you're good to go, you can wipe everything (or not) and flash SLiM.
There aren't in fact that many recoveries. Basically, the CWM recovery and its derivatives (PhilZ Touch) and TWRP. Both have different UIs and a few different extras in the way they manage backups, but they really serve the same purpose.
And then, there are things like XZDualRecovery, which includes both standard recoveries and allows to choose between them. Why include both? I don't know -- it may be related to CM ROMs needing their own recovery or just user preference --. Anyway, I suppose what makes XZDualRecovery the standard on Z2+ Xperia phones is its ease of install and the fact that it works out of the box.
Now, you need to reflash XZDualRecovery after installing a new ROM. There's a part of it that resides in the system partition and you'll lose it when you flash a new ROM; that's a big difference from what I was used to on the GNex, and many custom ROMs already include the necessary files. Be sure to check that before you flash, though.
I was mistaken, no ROM comes with a "previous ROM" requirement. Some packages (debloat releases such as serajr's for example) require an already present and rooted ROM to be installed, as they don't contain the whole system + data. They are not complete ROMs and must be flashed onto an existing, rooted ROM of the same version.
There is no real difference between ROM and "firmware", the latter is mostly what Sony uses to describe their flashable tool format releases while the former is more often used to describe custom releases. As a consequence, you'll more often see Sony's stock .FTF files described as "firmwares", and custom flashable .zip files as "ROMs".
In the end, here is what I ended up doing yesterday to my new Orange FR Z3C:
Follow the how-to to:
install the PC drivers;
downgrade to 23.0.A.2.93 stock firmware;
root the phone;
install XZDualRecovery;
Download Pandemic's pre-rooted stock 5.1.1 rom (23.4.A.0.546), reboot to recovery and flash it;
Download serajr's debloated, pre-rooted system and flash it;
Download and flash RICDefeat just to be safe;
Download and flash/install the Xposed framework and serajr's Xperia Xposed, although right now I only use it for its ability to load custom icon packs.
Huge thanks to everyone involved in the development of these tools, apps and ROMs.

[XT1900-7] No media audio and stuttering video after LineageOS install

Yesterday, I tried to install LineageOS 15.1-nightly, but missed the need for the copy-partion.zip, resulting in an unresponsive phone. With support by people in the LOS IRC channel, I managed to blankflash the phone and redo the install, this time with copy-partition.zip. I decided against rooting or installing GApps, and the phone booted perfectly fine.
Today, after installing some apps, I noticed that media audio will not play (Notifications and ringtones work, tho.) and video playback is extremely sluggish/stuttering, no matter whether it's youtube or a video I recorded myself.
While I didn't find anything similar for the X4, I found threads with similar issues for other phones that pointed towards bad/wrong firmware.
Could this be a lingering results from the blankflash?
If so, how to best fix it? Is there a way to reflash with stock firmware? (I looked at threads on this, but was overwhelmed with the variety of fimware versions and unsure which would be the correct one for my phone.)
As you can probably tell, I'm not terribly well-versed in this, so any help is greatly appreciated.
xoth said:
Yesterday, I tried to install LineageOS 15.1-nightly, but missed the need for the copy-partion.zip, resulting in an unresponsive phone. With support by people in the LOS IRC channel, I managed to blankflash the phone and redo the install, this time with copy-partition.zip. I decided against rooting or installing GApps, and the phone booted perfectly fine.
Today, after installing some apps, I noticed that media audio will not play (Notifications and ringtones work, tho.) and video playback is extremely sluggish/stuttering, no matter whether it's youtube or a video I recorded myself.
While I didn't find anything similar for the X4, I found threads with similar issues for other phones that pointed towards bad/wrong firmware.
Could this be a lingering results from the blankflash?
If so, how to best fix it? Is there a way to reflash with stock firmware? (I looked at threads on this, but was overwhelmed with the variety of fimware versions and unsure which would be the correct one for my phone.)
As you can probably tell, I'm not terribly well-versed in this, so any help is greatly appreciated.
Click to expand...
Click to collapse
Hi, i am in the same situation like you right now. No Sound and very low FPS at Sound/Video playback.
First i installed LineageOS15.1 without the copy-partitions.zip.
After a reboot, my device was bricked but with the blankflash.zip i was able to repair my Motox4 and boot into twrp-recovery.
In TWRP I successfully installed the copy-partitions.zip and LineageOS15.1.
LineageOS seems to work really nice EXCEPT of Sound/Video playback. No Sound and very low FPS (Youtube Videos in Stock browser, Recorded Videos, etc.)
I Also tried different LineageOS15.1 and 16.0 versions including the newest LineageOS16.0 (lineage-16.0-20190312-nightly-payton-signed.zip) but the issue still exists.
Maybe someone has a clue what we could try to do Thank you
alarko said:
Hi, i am in the same situation like you right now. No Sound and very low FPS at Sound/Video playback.
Click to expand...
Click to collapse
Buggy Phone Buddies!!! :highfive:
Exact same probleme here.
Moto x4 paython, XT1900-7.
blankflash was needed since the lineageos wiki did not mention the copy-partitions.zip.
Symptoms are: No sound (and very slow progressbar), low FPS for videos.
Right now my phone is garbage.
OK, I have it working now.
The solution was to install a stock android version or android one (I used android one).
After installing stock android like this:
https://forum.xda-developers.com/moto-x4/how-to/guide-how-to-flash-official-factory-t3808348
flash lineageos (using copy-partitions.zip again!).
vimablanka said:
OK, I have it working now.
The solution was to install a stock android version or android one (I used android one).
After installing stock android like this:
https://forum.xda-developers.com/moto-x4/how-to/guide-how-to-flash-official-factory-t3808348
flash lineageos (using copy-partitions.zip again!).
Click to expand...
Click to collapse
Oh, cool, I will try that!
Which version of the x4 do you have? Also the -7? If so which firmware did you use? (Looking through the dozen pretty cryptic links in that stock firmware page has me worried about picking the wrong one.)
I don't think that failure of flashing copy-partitions has that result. I haven't flashed copy partitions since returning to stock and applying ROMs after that... and my flashes all come out fine. Perhaps something else is happening. But yes, when in question, always flash back to stock. Then try again.
Ok, Update:
Today I flashed the Stock Rom and tested a random youtube video in chrome: Video playback and Audio worked fine.
I then flashed the current Lineage 16 nightly and tested it again: Same problem. I tried a youtube video, a downloaded mp4 video and a downloaded flac audio file, they all had no audio and the videos were very slow and stuttery. Youtube ****ery happened both in the default browser (I'm guessing Chrome or something?) and a current Firefox Klar I installed.
Additional weirdness: I also tried youtube playback on Torbrowser, where I think it falls back on HTML5 video or something, AND THERE IT WORKS!!!
Audio plays and Video playback is nice and smooth.
I ... don't get it.
Help?!?
I noticed the same thing yesterday with my xt1900-1. Video playback with chrome gas black lines and video appears to stutter. I tried the default browser and it appeared to be better. I'm currently using the 6/12nightly of lineage
Some more testing also showed additional wonkiness: Audio also doesn't work when using making a call.
Which ... makes it a but of a dealbreaker, tbh. :/
I had the same problem after installing LOS16.
New X4 1900-7 (Stock ROM) as described on the Lineage website installed the LOS16
(without "copy-partitions-payton.zip").
After booting, the smartphone was dead
Then as described here the smartphone repaired.
https://forum.xda-developers.com/showpost.php?p=77847374&postcount=44
Then install the "copy-partitions-payton.zip" and install LOS16.
After the boot was no sound when calling or playing videos.
The videos were also played very stuttering.
I then installed the Stock ROM as described here.
https://forum.xda-developers.com/moto-x4/how-to/guide-how-to-flash-official-factory-t3808348
I used Stock Rom from here:
https://mirrors.lolinet.com/firmware/moto/payton/official/
Stock ROM: XT1900-7_PAYTON_RETEU_DS_9.0_PPWS29.69-37-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
I did not use the flash-all.sh. I do everything step by step.
After the start of the Stock ROM OS, I checked call and videos.
The function was correct.
Then I reinstalled LOS16.
I proceed exactly as described here. (GAPS installation skipped).
https://www.youtube.com/watch?v=NWOBa88eJRs
Now the sound works in calls and videoas or MP3 files.
The smartphone works correctly so far,
only FM radio app does not work.
I have not found a solution yet.

Stock firmware, drivers, and flash tool available

Came across this. Hopefully, someone can use it to unlock the bootloader, root, and make custom ROMs for the Razr 5G.
Motostockrom.com
Another site with stock ROMs for Razr 5G can be found here
wow, thanks! Great site for many firmware packages
What tool do I use to flash these?
The Motorola Rescue and Smart Assistant doesn't seem to let me pick an image; it just detects the phone and downloads/installs the latest released image, which is not the one I want to install.
Ok I noticed the RSD Lite application but it doesn't seem to detect the phone. It doesn't seem to do much of anything. I used the latest version of the application, 6.2.4. I tried both versions of the driver -- 6.2.0 and 6.4.0 -- on the website. It looks old. Does it still work?

Categories

Resources