Database Info

Flash 10.2 Leak

Has anyone had any luck getting the leaked 10.2 Flash player on Hero CDMA? If so, could you share what you did to get it working and what setup you have? If you followed a specific forum post, could you link it? I have searched but none of the forum posts here I've tried have worked.
I've tried changing the user agent in the browser, however, I could not find 'Desktop' as some of the other posts have suggested. At this point, I've tried installing the leaked version directly: no joy.
I'm running CM7 RC2 with no mods at the moment.
Here is the link I used for the leaked Flash 10.2:
http://www.crunchitech.com/2011/03/15/download-flash-player-leak-version-10-2-for-android-2-22-33-0/

its not going to work, never will the reason why has been answered on here atleast 100000000000000000000 times, good find but wasted in here

ARMv6 vs. ARMv7 = Adobe refuses to set compiler flags.
thoughtlesskyle said:
its not going to work, never will the reason why has been answered on here atleast 100000000000000000000 times, good find but wasted in here
Click to expand...
Click to collapse
I should have been less specific in my use of the search tool. You are right. Hero is ARMv6 and Flash is compiled for ARMv7. Oh well, thanks for at least replying to me.
Now it would be nice if there was a module you could load into memory that would do machine code translation from v7 to v6... at least make it runable/compatible or make v7 programs 'think' they are running on v7. I'm sure that what be a nightmare of processor faults. And if it did run, it probably wouldn't be fast at all. Perhaps a v7 virtual machine? Again, another pipe dream because the Hero has less memory than a 486.
It's Adobe's fault anyway. A v6 plugin would not be hard to compile from the source. Just set the compiler flags and go. Grrr.
Thanks again.

Your right it probably wouldn't be hard but I think they did it this way because on the hardware acceleration side phones with v7 usually have the resources to spare to make flash run smoothly even flash lite is clunky at times on our v6 phones
They will chalk it up to delivering a consistent experience on their supported devices
zansatsu said:
I should have been less specific in my use of the search tool. You are right. Hero is ARMv6 and Flash is compiled for ARMv7. Oh well, thanks for at least replying to me.
Now it would be nice if there was a module you could load into memory that would do machine code translation from v7 to v6... at least make it runable/compatible or make v7 programs 'think' they are running on v7. I'm sure that what be a nightmare of processor faults. And if it did run, it probably wouldn't be fast at all. Perhaps a v7 virtual machine? Again, another pipe dream because the Hero has less memory than a 486.
It's Adobe's fault anyway. A v6 plugin would not be hard to compile from the source. Just set the compiler flags and go. Grrr.
Thanks again.
Click to expand...
Click to collapse
Sent from my PC36100 using XDA App

Unfortunately, the ARMv7 logic doesn't hold much truth as I was not able to run flash on my Samsung moment. I think there may be more factors involved.

aqualls said:
Unfortunately, the ARMv7 logic doesn't hold much truth as I was not able to run flash on my Samsung moment. I think there may be more factors involved.
Click to expand...
Click to collapse
I thought samsung used something other than ARM whatever it is I don't think they are using arm v7 I think the processor is close to what apple uses in the iphone 4 the cortex but I am not sure.
Sent from my PC36100 using XDA App

aqualls said:
Unfortunately, the ARMv7 logic doesn't hold much truth as I was not able to run flash on my Samsung moment. I think there may be more factors involved.
Click to expand...
Click to collapse
samsung moment is ARM11 which is ARMv6... not v7

I learned this one the hard way...
At first glance, ARM chip designations can be confusing but the difference is the ARM Family version vs. ARM Architecture version:
Note that architecture version names contain a 'v' and the family version names do not:
http://en.wikipedia.org/wiki/ARM_processor#ARM_cores
The Hero and Moment are ARMv6 architecture whereas newer phones are ARMv7.
It sucks, d00d! You are SOL just like me and many other Hero owners.
EDIT: Technically: The one notable exception to the 'v' observation is the ARMv5TE: Bulverde. But, heh, it works for me.

bk718 said:
samsung moment is ARM11 which is ARMv6... not v7
Click to expand...
Click to collapse
Not according to the the specs and every hardware app on the market. Trust me. If it was I could have run flash and apps for .avi video without audio sync issues.
Sent from my HERO200 using XDA Premium App

aqualls said:
Not according to the the specs and every hardware app on the market. Trust me. If it was I could have run flash and apps for .avi video without audio sync issues.
Sent from my HERO200 using XDA Premium App
Click to expand...
Click to collapse
what specs are u looking at??
Click here and scroll over to samsung moment.. ARM1176 which is ARMv6
refer to the link that zansatsu posted... its in there as well
or this link
or where its discussed here
i could go on and on or u can google it if you like and see for yourself..
im not trying to downplay you, but just trying to inform you that the information that you've been given is incorrect regarding the samsung moment having an ARMv7 chip..

The Samsung SPH-M900 (Moment) processor is an ARM11 Family, ARMv6 Architecture CPU:
http://en.wikipedia.org/wiki/ARM11#ARM11-based_products

zansatsu said:
The Samsung SPH-M900 (Moment) processor is an ARM11 Family, ARMv6 Architecture CPU:
http://en.wikipedia.org/wiki/ARM11#ARM11-based_products
Click to expand...
Click to collapse
i think with my links and ur links are point should be driven by now..

What is all the obsession over dual core phones?

I have to ask: Why does everyone want a dual core phone which cant even currently be used?
I say it cant be used because dual core processors cant be used on Android 2.3 Gingerbread/Linux kernel 2.6.35, there is only multi-core processor support in A3H/L2.6.36 (only avaliable (officially) on tablets). We will see problably support in in "A4I"/"L3.6.37" for both phones and tablets.
So whats everyones obsession? The only thing you are problably gaining is a SLIGHT speed boost (not even close when a kernal that supports it is released) and more battery drain.
On a counterside this could bring good marketing to Google: They release "A4I", current dual core phones get a HUGE speed boost and everyone praises Google. Could work good for them.

Interesting, I never knew Gingerbread couldn't support dual cores on phones. Good info, I guess I'll keep my Evo for another year.

It's pretty easy to compile the kernel to use multi core processors. The current one may not, but hold your judgement until it's actually released.

crazy25000 said:
It's pretty easy to compile the kernel to use multi core processors. The current one may not, but hold your judgement until it's actually released.
Click to expand...
Click to collapse
So true............. Currently 0.0000000000000000000000000000000000000000000001% of users AND developers of applications can and are willing to complie a custom kernel not used by the rest and use/make multi core supported applications with its multi core supported kernel.

I guess progress has to begin somewhere?

i don't think i'll ever need / want a dual core phone for my daily rutine, my SGS is perfect for me, what more could you need from a phone? don't think they'll be able to fit jet packs on them any time soon...

riahc3 said:
So true............. Currently 0.0000000000000000000000000000000000000000000001% of users AND developers of applications can and are willing to complie a custom kernel not used by the rest and use/make multi core supported applications with its multi core supported kernel.
Click to expand...
Click to collapse
What I'm saying is the kernel can easily be compiled by Google or Samsung and used as the stock kernel on the GSII.

maranello69 said:
i don't think i'll ever need / want a dual core phone for my daily rutine, my SGS is perfect for me, what more could you need from a phone? don't think they'll be able to fit jet packs on them any time soon...
Click to expand...
Click to collapse
Yeah its logical to think like that but 3 years ago who thought you need phone with such big screen and processor/RAM almost match PC speed?
As someone said somewhere they have to start but interesting thought by thread creator

ksavai said:
Yeah its logical to think like that but 3 years ago who thought you need phone with such big screen and processor/RAM almost match PC speed?
As someone said somewhere they have to start but interesting thought by thread creator
Click to expand...
Click to collapse
Honestly those arent needs either. But as of right now the only purpose of a dual core phone is to brag.

Open source driver for FIMG 3DSE (GPU of Galaxy 3)

I am posting here as I am not allowed to do so in development subforum.
Anyway, I am the developer of the OpenFIMG project (formerly GLES6410), which is aiming to provide proper OpenGL support on devices with FIMG 3DSE 3D engine, found in S3C6410, S5PC100 and probably also in S5P6442. The project is in a pretty advanced state as it is already capable of running Android 2.3 with hardware acceleration. Still many OpenGL extensions and some core features (like lighting) are still missing. More info can be found here: https://github.com/tom3q/openfimg/wiki.
It is very likely (and almost confirmed) that the SoC used in Galaxy 3 (S5P6442) contains the same GPU as the one in S3C6410, which is the chip inside Galaxy Spica and similar phones, at least basing on what Quadrant and GLbenchmark show and on GL libraries supposed to be dumped from Galaxy 3.
What I am trying to say is that my project may also be useful on Galaxy 3, but I am the only developer working on it and I am doing it in my free time, so it does not progress as fast as one may expect. In other words, I am looking for some other developers interested in this project.
If you are interested, then do not hesitate to drop me a PM.
Mod EDIT : moving this to development
EDIT: Attached some documents about FIMG 3DSE (based on S3C6410 documentation and my reverse engineering)
EDIT: The project has been successfully used on G3. Builds of ICS for G3 use OpenFIMG as primary graphics driver currently and there are update packages for CM7.

Very interesting .. I send you PM.

Galaxy 3 has no GPU.

mpbm23 said:
Galaxy 3 has no GPU.
Click to expand...
Click to collapse
Based on what?
All my sources state that it has exactly the same FIMG 3DSE rev. 1.5 as in S3C6410.

Based on the fact that no site says that the I5800 has a GPU and that graphics on games are really laggy.
Unless you are not talking about a discrete GPU.

No mobile phone contains a discrete GPU. All of them are embedded inside some SoC chip, some are better (SGX, Adreno), some are worse (FIMG 3DSE).
It is exactly the same as with Spica and similar phones. Games are laggy because the hardware is not a speed daemon and the performance is even more impacted by really _broken_ drivers.

Then why nobody write that it has GPU like all the other phones like Galaxy S ,Nexus S etc?

mpbm23 said:
Then why nobody write that it has GPU like all the other phones like Galaxy S ,Nexus S etc?
Click to expand...
Click to collapse
Because it is a low end phone, software support for this GPU is very bad and the GPU itself is not a speed daemon.

tom3q said:
Because it is a low end phone, software support for this GPU is very bad and the GPU itself is not a speed daemon.
Click to expand...
Click to collapse
Okay..so your project involves developing real good drivers so that even the g3 low end gpu can perform better, right?
Sent from the 3rd Galaxy !

Yes. Of course, it will not work on par with Adreno 200 or similar GPUs, but should at least work a bit better. The main target is to run Android 2.3 (and future versions, which will not work will original drivers, because of missing extensions) with full hardware acceleration and without bugs found in Samsung drivers.

Hmmm.. Nice .. Good luck with your project.. One of our devs marcellusbe is working on porting CM7 to G3.. This would surely help him ..
Sent from the 3rd Galaxy !

cool... if so this is gonna make new benchmark .. pun intended ... best of luck man.... I had thought of throwing this phone a long time back but you guys always give hopes... and ofcourse result..

Wow interesting!
This should be moved to dev section I have sent a PM to haree

Cool. So what can others help with?

Too interesting
I'ld like to help with whatever i can

I'll back you up in spirit, sorry,i know nothing about programming

VERY intresting!
and yes the galaxy 3 does have a gpu and yes it has been confirmed (or atleast i heard) that it has this gpu..cant wait to see the outcome!

Actually, I will need some people who would compile, test and eventually fix the code for Galaxy 3, because the only phone with this GPU I have is a Galaxy Spica (i5700) and there may be some subtle differences between them. (Especially in the kernel part, where kernel modules may require changing of some addresses or some other fragments of code.)
Preferably, I would like someone to help me with the project, but I understand this is not an easy task, so not everyone can apply.

I don't mind being a tester
Edit: also will we be able to play gameloft games and nfs shift?
Sent from my GT-I5800 using XDA App

dilzo said:
I don't mind being a tester
Click to expand...
Click to collapse
Nice, thanks.
However, you have to understand that it is not a simple drop-in replacement of standard GL libs. This project replaces the whole graphics subsystem of the phone, including some kernel modules and this makes testing a bit more complicated as it needs pretty big modification of the phone software.
If it is not a problem for you then ok.
dilzo said:
Edit: also will we be able to play gameloft games and nfs shift?
Click to expand...
Click to collapse
It all depends if all the extensions required by these games will get implemented. Also, there may be some problems with screen resolution of Galaxy 3, which is a not standard one. I cannot give any claims regarding the performance as the real performance of this hardware is unknown.

Android 4.0 for a Lg optimus 3D

Hey people does anyone know if android 4.0 will be available for the Lg optimus 3D when it comes out around December

Virus711 said:
Hey people does anyone know if android 4.0 will be available for the Lg optimus 3D when it comes out around December
Click to expand...
Click to collapse
No........................

Virus711 said:
Hey people does anyone know if android 4.0 will be available for the Lg optimus 3D when it comes out around December
Click to expand...
Click to collapse
almost had heartattack reading topic name :S
we dont have 2.3.3, and you are dreaming about 4.0?

Well let me read the cards...errrr
Some one is flying high. Anyways I can't see why not with a little magic of the dev community.
Sent from my LG-P920 using XDA App

i'm shire it will come also for o3d by lg or through the great developers in this forum.
but why do you what it already? maybe it's crap? i doubt it but maybe....
and one of the golden rules:
be patient, good things need their time

I wouldn't be surprised if 4.0 won't run on this phone due to the ram, even if it does its going to be well into next year before we get it, I would be surprised if we have it for next summer judging how far behind LG are now, this phone and the Optimus X2 should have launched with Gingerbread.

if cyanogen support this device, there will be 4.0 for us

the already support this device

typhex said:
if cyanogen support this device, there will be 4.0 for us
Click to expand...
Click to collapse
but 3D will be useless without the drivers for the cameras and the screen

mmace said:
but 3D will be useless without the drivers for the cameras and the screen
Click to expand...
Click to collapse
True but all the S3D core code it open to the devs thanks to TI as I understand it.
Also it's not even sure it's called 4.0, they haven't set a version number have they? and the number is just a indicator, the jump from 2.3 will be stuff like optimization in the system for dual core, and people still talking about too little RAM is just poppycock.
Most likely performance for the O3D will be better with Ice Cream Sandwich, might even beat all other phones as it's (so far) the only one with dual RAM and dual Channels which keeps the dual-core CPU from being bottlenecked by the rest of the system.

I have to admit, this talk of "ooooh it might not run version xx.yy of Android" or "ooooh what if the new uber fantastic app doesn't work because it ONLY has 512MB RAM" makes me laugh.
Why? Well lets look at what the problems have been in the past:
OS Partition is too small:
This was a problem when the OS was written to fit inside the small flash built-in to the CPU package. As the OS has gotten bigger this had to be solved one way or another. I'm not sure of the specifics, but I think its enough to say this is solved now.
Not enough RAM:
Fitting an advanced OS into 64MB or even 256MB of RAM is tricky, especially when the core OS is based on code from PCs with a lot more RAM than that and the luxury of a swap partition.
However 512MB was the turning point on PC where RAM became less of an issue and in the right configuration you could live without swap. So logically this should hold true, probably moreso, for Android. Because Android until recently was already running in 128MB/256MB without the advantage of swap space.
No Drivers:
Many are open source, we are also working with hardware a lot more standardised than it once was.
I can see from a glance that there are a lot of similarities between my N900 at the hardware level and the O3D. If you are dealing with devices that are basically upgrades of old hardware designs, drivers are a lot easier to deal with - especially if they are open source.
Lack of GPU or certain CPU instructions:
Many older devices could not handle newer Android because they lacked a proper GPU or the CPU did not have the right instructions. This is similar to what happened on PC for a while, when multimedia suddenly became big. Like on the PC once all these multimedia instructions became commonplace it was no longer really an issue. I believe we are at the same place now with high-end Android hardware.
So I really would be surprised to find a newer version of Android outright not be able to run on the O3D, for quite some time.

[Q] Questions about Blaze and Roms

Ok so please forgive my noobness here but I'm dying to ask a few questions... I have been an android fan for years and always had lots of options for my phones, and now that I am switching phones I would like to help out more. I see that development is going slow on this phone and had a few questions...
What would it take to port over some roms from say the galaxy s (I'm thinking possibly CM7 or MIUI)? What is the closest phone to ours if not the galaxy?
If the kernel is open source (https://opensource.samsung.com) then is over/underclocking possible with much effort?
Is all I need to build a functioning rom available from the android sdk and the samsung open source website? (I understand this is no easy task, just wondering if I need more than this)
FM transmitter... I hear this phone has a FM transmitter, is this true? Oh man what I wouldn't give to get this working. I would love to hear any opinions/suggestions/comments on this subject as this interests me most.
I'm sorry once again for all the questions, I am looking forward to helping out however possible.

I suggest you look up the wiki's on cyanogenmod on building. You'll need some sorta POSIX environment (ie.. linux or OS X). Here's the one I used:
http://wiki.cyanogenmod.com/wiki/Samsung_Galaxy_S_II_(AT%26T):_Compile_CyanogenMod_(Linux)
The SGS family largely uses samsung components (CPU's, GPU's, etc). The Blaze uses the qualcomm snapdragon stuff. The blaze is using the msm8660 arch, which isn't really present in the cm7 sources. The only thing kinda there is the sgs2 for at&t (skyrocket). Finding other examples using similar hardware has not been easy for me. The audio subsystems for sgs2 seems to be yamaha based, where as ours isn't. You'll want to be VERY careful to make sure all the partitions are set up properly in your work as otherwise you may end up wiping the radio or other supporting partitions, and that would be very, very bad. And etc... etc... etc...
It would help to have a working knowledge of unix/linux. You'll definitely want to root your phone (obviously) and install busybox so you have a decent toolset to go poking around the OS.
I wish you luck and I hope this helped!
---------- Post added at 02:00 PM ---------- Previous post was at 01:56 PM ----------
Oh, forgot about the Kernel.
The kernel itself is always open source (legally required). The changes and binary blobs for drivers aren't.
You apparently tweak the kernel seperately from a cm7 build. OC and UV are about playing with the timings inside the CPU and is not for the feint of heart. My understanding is that there is a whole series of equations and calculations you use to arrive to the frequency table for such things. Since other hardware uses our CPU, that's probably the place to start looking... i.e... the EVO 3D.

Thanks for quick reply! I currently dual boot ubuntu/win7 and have a small working knowledge of linux, so hopefully that helps there. I will start messing around with the phone in another week or so when my schedule allows, but will gladly help beta test until then! Please feel free to hit me up when you need something tested
Also, since you are the hardware man.... what about that FM transmitter? Is that only a receiver or is it a combo? I personally have never seen a FM transmitter in a phone and would love to have one.

dr4stic said:
The SGS family largely uses samsung components (CPU's, GPU's, etc). The Blaze uses the qualcomm snapdragon stuff. The blaze is using the msm8660 arch, which isn't really present in the cm7 sources. The only thing kinda there is the sgs2 for at&t (skyrocket). Finding other examples using similar hardware has not been easy for me. The audio subsystems for sgs2 seems to be yamaha based, where as ours isn't. You'll want to be VERY careful to make sure all the partitions are set up properly in your work as otherwise you may end up wiping the radio or other supporting partitions, and that would be very, very bad. And etc... etc... etc...
Click to expand...
Click to collapse
As far as being close to the Blaze, what about the Galaxy Note? It has a msm8660 while the Blaze has a msm8260. Both have the adreno 220 gpu, same ram, and release around the same time. I see there is a larger screen and a different camera, is there something we can use there?
I only ask as I ran across this thread: http://forum.xda-developers.com/showthread.php?t=1573568 and was wondering if maybe this phone would be the place to start a port.