Related
Does anyone remember the video adobe put up demonstrating flash on g1? It's a video of kevin lynch showing flash 10 working what seems to be flawlessly on the g1, more than a year ago!
link--->http://www.youtube.com/watch?v=YT__RDRVb4c
just a couple days ago cm6 got released and its running beautifully on my "old bed-ridden" so why not flash? i'm no developer but there must be a way to make flash specifically for g1's or mytough 3g's, after all the video is living proof. hopefully a developer can take the flash app from another phone running froyo and work their magic on it to make it work on our devices. c'mon devs keep the g1 alive
It really is heartbreaking..
Seeing this video makes me remember why I was bragging to Iphone users that have no flash what-so-ever... I remember this video now and I guess the G1 has the flash capabilities but, the app that adobe released is coded to only work on Froyo and Snapdragon devices.
I think their plan is to get us all to upgrade to the newer snapdragons or soon to be dual core snapdragons... Man I hate how technology ages.
Well from the sounds of it the Flash that is available now and to the public for Android Phones won't work on the older processors of the G1 and such. In it's current form anyways.
People keep throwing around that Flash is "not possible" on the G1 and I just don't buy it. I'm no developer and I'm sure it's not easy, but I don't for a second believe it's "not possible."
I could however believe that it just isn't worth it. But that's totally different. It'd be nice to hear a dev say they don't want to bother with the headache and that it would just be too large an undertaking rather than just hear that it's "not possible."
It is possible it however is not probable. As flash isn't open source it would have to be backwards engineered(unreasonable amount of effort) and recompiled for the arm6 architecture..far to much effort for something that would function questionably..
Sent from my iPhone using Tapatalk
@Blackman778g
yea definitely agreed, but i don't see why not someone can screw around with a couple of files or code or whatever developers do and recompile to operate on older devices, or devices with different hardware. sure it's probably not gonna be an easy task, but if we can get a whole operating system that's suppose to cripple the **** out of our hardware, why not just an app? sense has done it, not in a specifically good way but it can maybe spark hope?
@dezvous
yea it'd be pretty sweet for someone to take a jab at it, and personally i believe the "it wont work with our processors" is a load of bs, because i think the phone in the link is running cupcake, which underclocks the g1 at 386 and it looks perfectly fine. now-a-days we can get to 725mhz without jacking up your battery, i run 614 and i just sit and watch it fly
@ftruck90
yea thats true, but it'll be cool to see someone try
why not dump adobe flash alltogether and work on an open source flash replacement, there's one available for linux, i think its called GNUFlash or something..
ps: i think this was already mentioned somewhere else on xda..
here you go...
http://www.gnu.org/software/gnash/
Cyanogen has told us full flash will never work on G1. However, there's a think tank for getting flash lite to run in Froyo.
http://forum.xda-developers.com/showthread.php?p=7177455
Flash not working is not bs.
Flash as it is now was built for a certain processor architecture (The G1 has Arm6 where flash was built to run on Arm7). Its like saying that its BS that I can't run software built to run on PowerPC on a x86 processor. The PowerPC processor has different instruction sets that the x86 does not.
We need an open source mobile flash alternative.
That we could try to recompile for our devices and build a plugin around it.
Or someone disassembles the curreent flash froma dobe and recompiles it for Arm7...wich i don't think is possible.
i dont understand something. everytime i see one of these flash topics, every1 says it was never compiled to run on arm6 and everything else.... but how did this video come to life? OVER A YEAR AGO. that video is flash, running on a g1, pretty solidly too. and i mean...whats that...cupcake?
that video is pretty incriminating stuff if you ask me. adobe got some explaining to do.
but...if CM says it cant be done, i'll believe him.
CM said it can't be done (with the adobe flash)
What you saw was a (probably unstable?) version of flash compiled by adobe probably as a testrun on the G1.
Adobe CAN compile it for the G1 IF they want to.
What we can do in the meantime is ask adobe to compile flash for the Arm6 and hope that it'll make enough rucus for them to notice.
havikx said:
i dont understand something. everytime i see one of these flash topics, every1 says it was never compiled to run on arm6 and everything else.... but how did this video come to life? OVER A YEAR AGO. that video is flash, running on a g1, pretty solidly too. and i mean...whats that...cupcake?
that video is pretty incriminating stuff if you ask me. adobe got some explaining to do.
but...if CM says it cant be done, i'll believe him.
Click to expand...
Click to collapse
1.that video could very well not be legit lots of companies release mocked up videos as ads
2.if it was real adobe have the source code for flash as it's their product so they very well may of compiled a version for arm6 and never released it. But as its not open source that means exactly zero to us. The argument isn't that it's impossible to run flash on this processor it's that it is impossible to run current releases of flash on it
Sent from my iPhone using Tapatalk
mr.johnsexydavis911 said:
@Blackman778g
yea definitely agreed, but i don't see why not someone can screw around with a couple of files or code or whatever developers do and recompile to operate on older devices, or devices with different hardware. sure it's probably not gonna be an easy task, but if we can get a whole operating system that's suppose to cripple the **** out of our hardware, why not just an app? sense has done it, not in a specifically good way but it can maybe spark hope?
Click to expand...
Click to collapse
OK, you obviously aren't a dev. Here's the basic version. Programs these days are written in a more human readable format (called "source") and compiled into a format the computer can understand. Most compilers build for a specific CPU type, and the code they generate won't run on anything else. Interpreted languages like BASIC, Python, and Java either don't really get compiled, or get compiled to a neutral format called "bytecode". Then you need a CPU specific app to run the source or bytecode.
Flash is a bytecode language. That's why it can run on so many platforms. The problem is the bytecode interpeter. That's proprietary code that Adobe wrote and has not released the source for. It's also native CPU code, so it's compiled for a specific CPU family. Which is a somewhat retarded thing to do on a platform like Android, but they probably did it for performance reasons. Though with a working JIT, I imagine a Java based version would work. Adobe has never been known for writing very efficient code.
Now, the Flash runtime engine was compiled for a different CPU type than the one we have in G1, MT3G, and others. In order for the Adobe code to work with our devices Adobe would have to compile it for us. Or give us source code, which they will likely never do. Or we could try to write an emulator to fake the CPU type differences, but those are SLOW. The rule of thumb is you have to have a CPU 10x as powerful as the CPU you are emulating. Our CPU is slower than the one we would need to emulate.
Another option is to attempt to do dynamic compilation on the binary to translate it to our CPU architecture. This is an incredibly complex undertaking and is rarely attempted. There are just too many things to go wrong with this sort of thing. In this particular case, the existing code is close to the same architecture, so it might be a little easier, but it's still very difficult. You have to translate every instruction at the machine code level and account for differences in the available instructions, registers, size of data fields, CPU cache, RAM size, and various other side-effects that are not obvious at first glance. The devs here are good, but this is the sort of thing that billion dollar companies try and fail at. It's a LOT harder than it looks.
If you want flash, learn to dev and work on one of the open source Flash engines to try to get it up to snuff. Then try to optimize it to run well on our low end CPU and RAM starved machines. By then we'll likely be running dual or quad 3Ghz ARM12 phones.
has any1 tried contacting adobe about it?
Dead platform. Probably not worth their time and money to compile on ARMv6. As ttabbal stated above, by the time any of these solutions come to fruition, we'll probably all have upgraded.
I would say its definitly worth adobes or a devs time and money. Because even tho g1s are getting old. I would still pay 20 or 30 bucks just to download a nice operating flash player for the g1 off the market. There's so much money in it. Its sick. That dev would be rich fo sure!!!!!
sent from my superfroyo dream
dead platform
Ok, in the last 4 weeks over a million Phone with android and ARM 6 processors were sold world wide. So I would say that Adobe may listen.
It took adobe SEVERAL YEARS to support AMD64, and that was with the entire world nagging them about it several times every day, and it is an ADVANCEMENT from intel32.
Adobe is just a bloated hog, they are COMPLETELY out of touch with consumers, selling you the JUNK that they WANT to sell you and not the product that YOU WANT to buy from them.
To be honest though, LET FLASH DIE. I don't want flash on my phone, or, for that matter, even on my desktop. It doesn't offer ANYTHING that is even REMOTELY useful.
dhkr123 said:
It took adobe SEVERAL YEARS to support AMD64, and that was with the entire world nagging them about it several times every day, and it is an ADVANCEMENT from intel32.
Adobe is just a bloated hog, they are COMPLETELY out of touch with consumers, selling you the JUNK that they WANT to sell you and not the product that YOU WANT to buy from them.
To be honest though, LET FLASH DIE. I don't want flash on my phone, or, for that matter, even on my desktop. It doesn't offer ANYTHING that is even REMOTELY useful.
Click to expand...
Click to collapse
Agreed. Is there any way we can make this thread disappear? I don't want another necromancer to appear after Gingerbread drops and people go nutso there too.
Will it be possible for us to get 2.3 ported on the milestone?
We haven't even got official 2.2 yet...
cherrybombaz said:
Will it be possible for us to get 2.3 ported on the milestone?
Click to expand...
Click to collapse
needs higher memory requirements like 512Mb, so only Miletone2 and in 2012..
(it took 1yr for milestone1, so thats easy to estimate from now+12months)
Dexter_nlb said:
needs higher memory requirements like 512Mb, so only Miletone2 and in 2012..
(it took 1yr for milestone1, so thats easy to estimate from now+12months)
Click to expand...
Click to collapse
Is that really true? What would require higher memory than Froyo? I don't see anything in the features which would require 512MB..
Guys: let's focus on what is REALLY important from 2.3. We don't need all those features...I mean: we WOULD like to get them all but I think it's a hard challenge for developers (the upgraded kernel hasn't even been released for 2.2, I don't want a 2.3 with battery draining and kernel_issues just becuase of Motorola laziness...). I just need a 2.1 (which covers all the "basics" of what a smartphone MUST do) with some improvements from 2.3! I'll start with mine:
1) New Keyboard: I really want to try the new keyboard and think shouldn't be so difficult to port it to 2.1 (just a hope!)
2) Download manager: not a must-have but hey...would be useful!
3) New UI and "smoother" animations: I'm quite sure this is almost impossible to port..
4) Support for WebM: see above...
By the way maybe the whole gingerbread can run on 2.6.32 kernel! So a good porting would be ready when motorola releases the official 2.2 sbf. Am I correct?
EDIT: Look at these:
http://www.youtube.com/watch?v=6AAFF9PN-WU&feature=channel
Youtube 2.0 is also available for 2.1! I can't notice any difference with 2.3!
http://www.youtube.com/watch?v=OCgf8RW7B88&feature=channel
Newer streetview and Maps navigation are available on 2.1...No voice controls though!
Dexter_nlb said:
needs higher memory requirements like 512Mb, so only Miletone2 and in 2012..
(it took 1yr for milestone1, so thats easy to estimate from now+12months)
Click to expand...
Click to collapse
And also (correct me if I'm wrong)
Probably some features like GPU accelleration in openGL 2.0 may be a little difficult to port over right?
mardurhack said:
3) New UI and "smoother" animations
Click to expand...
Click to collapse
it's a sweet dream... but i would be awesome
@89luca89: I didn't see anywhere that 2.3 supports GPU acceleration! This would be AWSOME especially for the browser!! How have Opera's guys been able to enable hw acceleration on their browser? Do you think it would be also possible on custom browsers like Dolphin or is that a "Presto" (the Opera's rendering engine while Chrome's one is Webkit) feature? Thanks!
@razer54: Being sincere...I'd really like (read as NEED) a smoother browser than smoother animations...Launcher Pro is smooth enough for me! And menus scrolling is too! The only one who lacks smooth interaction (scrolling, pinch2zoom etc.) is the browser! But, as I wrote above, there could be the possibility to port Opera's hw acceleration on a browser like Dolphin (or the stock one being the source code public). Couldn't it?
I presume everyone has seen this:
http://developer.android.com/sdk/android-2.3-highlights.html
Heaps of the new improvements look awesome, improved responciveness, native audio control, new keyboard, dalivik garbage collector, native voip, updated video drivers - all this stuff would make lots of apps (including games!) much better on Android.
I really hope game devs start getting serious about Android with the approah of the Playstation phone and Android 2.3 available. I'm no expert but I assume while some things like the new keyboard may be possible to port back to 2.1 or 2.2 on milestone, we will never see the bulk of 2.3 on our phones.
Ballinor I almost forgot to ask if copy&paste can be ported from 2.3!!
EDIT: Ok I changed my mind...I NEED Gingerbread!! PLEASE PLEASE PLEASE tell me that will be possible to install it on Milestone!
can someone port the new keyboard? there´s already a couple of leaked keyboards but they all appear small on our precious .... its like a hyper compact keyboard ....
Dexter_nlb said:
needs higher memory requirements like 512Mb, so only Miletone2 and in 2012..
(it took 1yr for milestone1, so thats easy to estimate from now+12months)
Click to expand...
Click to collapse
I'm sorry but what you're saying is mostly a dull statement. I wouldn't expect this coming from you at all, seriously. You didn't even explained what would need more memory. Its clearly stated the most of the higher specs would be used for new Multimedia standards and gaming improvements (Concurrent garbage collector being one of them!).
It took a bit more then half of year for Milestone 1 to get unofficial 2.2, the biggest problem being unlocked boot loader.
This is the same thing as telling its impossible to get Froyo to G1. Officially, that is correct. Unofficially, Cyano and everyone in XDA and other communities are doing everything to keep G1 alive. And I can tell you, Froyo on G1 is working smooth and without problems.
greglord said:
I'm sorry but what you're saying is mostly a dull statement. I wouldn't expect this coming from you at all, seriously. You didn't even explained what would need more memory. Its clearly stated the most of the higher specs would be used for new Multimedia standards and gaming improvements (Concurrent garbage collector being one of them!).
It took a bit more then half of year for Milestone 1 to get unofficial 2.2, the biggest problem being unlocked boot loader.
This is the same thing as telling its impossible to get Froyo to G1. Officially, that is correct. Unofficially, Cyano and everyone in XDA and other communities are doing everything to keep G1 alive. And I can tell you, Froyo on G1 is working smooth and without problems.
Click to expand...
Click to collapse
The 512mb of RAM is a statement from Google. They just want less fragmantation in android devices.
What that really means is it'll probably run on the Milestone if we didn't have that damn bootloader..
It'll probably be ported to the Droid.
It will be ported to Milestone too..
greglord said:
It will be ported to Milestone too..
Click to expand...
Click to collapse
Yup,but without proper kernel
I hope so!!!
Unfortunately I'm not an expert in programming, but I'll give all my support for testing!
Milestone is too young do be abandoned, it is still an optimum phone in my opinion!
mardurhack said:
@89luca89: I didn't see anywhere that 2.3 supports GPU acceleration! This would be AWSOME especially for the browser!! How have Opera's guys been able to enable hw acceleration on their browser? Do you think it would be also possible on custom browsers like Dolphin or is that a "Presto" (the Opera's rendering engine while Chrome's one is Webkit) feature? Thanks!
@razer54: Being sincere...I'd really like (read as NEED) a smoother browser than smoother animations...Launcher Pro is smooth enough for me! And menus scrolling is too! The only one who lacks smooth interaction (scrolling, pinch2zoom etc.) is the browser! But, as I wrote above, there could be the possibility to port Opera's hw acceleration on a browser like Dolphin (or the stock one being the source code public). Couldn't it?
Click to expand...
Click to collapse
you got a point, i wanted to speak about browsing experience when i wrote animation ^^
max_3000 said:
The 512mb of RAM is a statement from Google. They just want less fragmantation in android devices.
What that really means is it'll probably run on the Milestone if we didn't have that damn bootloader..
It'll probably be ported to the Droid.
Click to expand...
Click to collapse
Can you please post a link where I can see such Google statement? Thanks.
(And to be clear, I'm not interested in links to the old rumors that have been denied and ridiculed directly by a google engineer a long time ago.)
mardurhack said:
Guys: let's focus on what is REALLY important from 2.3. We don't need all those features...I mean: we WOULD like to get them all but I think it's a hard challenge for developers (the upgraded kernel hasn't even been released for 2.2, I don't want a 2.3 with battery draining and kernel_issues just becuase of Motorola laziness...). I just need a 2.1 (which covers all the "basics" of what a smartphone MUST do) with some improvements from 2.3! I'll start with mine:
1) New Keyboard: I really want to try the new keyboard and think shouldn't be so difficult to port it to 2.1 (just a hope!)
2) Download manager: not a must-have but hey...would be useful!
3) New UI and "smoother" animations: I'm quite sure this is almost impossible to port..
4) Support for WebM: see above...
By the way maybe the whole gingerbread can run on 2.6.32 kernel! So a good porting would be ready when motorola releases the official 2.2 sbf. Am I correct?
EDIT: Look at these:
http://www.youtube.com/watch?v=6AAFF9PN-WU&feature=channel
Youtube 2.0 is also available for 2.1! I can't notice any difference with 2.3!
http://www.youtube.com/watch?v=OCgf8RW7B88&feature=channel
Newer streetview and Maps navigation are available on 2.1...No voice controls though!
Click to expand...
Click to collapse
i agree...
obviously we won't get all the new implementations, but it would be nice to have some of them... the easier ones to port...
I think one of the most important think to port it"s the jit no ? if i remember well, the jit from froyo was ported to eclair, so the one from gingerbread can be ported to froyo no ?
Since many people asked what I was doing these days:
The Nook Color running a healthy mix of Android 3.1 Honeycomb from the Xoom and Android 3.1 from Google's SDK.
As can be seen towards the end the Launcher application suffers from some drawing issues. The same issues can be observed in Google's SDK 3.1 emulator. The emulator and the nook both are doing software UI rendering instead of the new in 3.0 hardware accelerated UI rendering. Sadly the PowerVR SGX530 drivers that are (publicly) available right now are lacking some features to activate the hardware UI rendering on the nook. (like support for EGL_SWAP_BEHAVIOUR = EGL_BUFFER_PRESERVED
and the GL_OES_EGL_image_external extension). I started patching around those issues, which is hard without the access to the Android source, and can confirm that the nook's hardware is more than capable of running 3.0/3.1 hardware accelerated even though the source might need some patches if we don't get updated drivers for the SGX530.
So the status right now is: software UI with redraw issues or hardware UI with a working home screen but tons of more issues in other applications.
Other than that sound, wifi and opengl works. (no DSP/video decoding so far)
So who's up for solving the redrawing issues?
Possible solutions are:
getting our hands on a newer SGX530 driver than 1.1.16.4061
unpacking, patching and repacking Launcher2
?
waiting until Google releases the 3.1 AOSP source
-Rafael Brune
It sucks but I feel our best bet is just to wait for source. There are a lot of honeycomb tablets slated for release over the next few months, I think once it becomes more widely available we'll see source.
Since we dont know when will be... all the time, effort, and trouble to get it fully working witout source - will be in vain once the source drop happens.
So unless the people involved don't care, cm7 is more than enough for now. We are lucky to even have that, my phone doesn't even have cm7 working for it.
My .2 anyways
Sent from my SCH-I500 using XDA App
The problem is, Google has stated they won't be releasing Honeycomb source until it's integrated with the phone branch. I personally doubt that we see real source until Ice Cream is out.
honeycomb source will never be released, google said so, we'll get Ice Cream Sandwich source which will be awesome on our nook's i'm sure
ok all of you guys are real downers when you pretty much say "give up, source is the only way" now i know thats not what your literally saying but thats what im getting from your posts
@deeper-blue
good job dude, i would love to see a beta for this if its as stable as honeycomb v4(knowing your work it will be) a side from a few graphical errors(im assuming the same ones from the first SDK port) i think it can and probably will be a daily driver for most people here
Any hope for USB host support with the port or once again not till source
Sent from my Vision using XDA Premium App
deeper-blue said:
Since many people asked what I was doing these days:
http://www.youtube.com/watch?v=RJ_k4kdsaMk
So who's up for solving the redrawing issues?
Possible solutions are:
getting our hands on a newer SGX530 driver than 1.1.16.4061
unpacking, patching and repacking Launcher2
?
waiting until Google releases the 3.1 AOSP source
-Rafael Brune
Click to expand...
Click to collapse
hey THANKS for posting up what you've done and this very cool video... that was just awesome to see how far someone has gotten to get 3.1 running WELL on the nook.
mad props.
Nice work rafael!
Sent from my NookColor using Tapatalk
can't really help you out, but I'd just like to cheer you on
+1 !
Keep up with the excelent work !!!
botossi said:
+1 !
Keep up with the excelent work !!!
Click to expand...
Click to collapse
luigi90210 said:
ok all of you guys are real downers when you pretty much say "give up, source is the only way" now i know thats not what your literally saying but thats what im getting from your posts
@deeper-blue
good job dude, i would love to see a beta for this if its as stable as honeycomb v4(knowing your work it will be) a side from a few graphical errors(im assuming the same ones from the first SDK port) i think it can and probably will be a daily driver for most people here
Click to expand...
Click to collapse
Completely agree, there are a couple of interesting apps in the market that take advantage of HC and would be great in the Nook.
If you ask me waiting for AOSP don't look as such a good idea, since it's release is not so sure.
deeper-blue: Quick question: which HC image are you running in the posted video?
Since the initial SDK image you did, I've not seen any run that smoothly.
arrjaytea said:
deeper-blue: Quick question: which HC image are you running in the posted video?
Since the initial SDK image you did, I've not seen any run that smoothly.
Click to expand...
Click to collapse
He is running 3.1, which he has been working on and has yet to release because of the bugs he demonstrates in the video.
Great work DB, really excited to see the progress on this. I'm just wondering - would it be feasible to run this with ADW or similar as a holdover until the Launcher2 rendering issues are resolved?
Sounds like patching the launcher will be the easiest route. This is why I love you DB ahhaha, your work is amazing.
Hi deeper-blue,
If you want, I can offer you my help. I would be able to try to patch launcher2. I've been able to work out a few stuff in launcher2 when I was doing test builds of HC 3.0 and 3.1.
I'm trying to look if I can find some drivers for the PowerVR SGX530, but I unfortunately can't help by making 3.1 available on AOSP.
Is there a pointer to instructions on how to cook from SDK ? Have been looking around and have not found anything useful.
Wanted to take a crack at the graphics driver portion.
Very nice work deeper-blue.
Don't let the lazy people uninspire your work. If the Android and Open-source community in geral would wait for corporations solutions linux would never have been created. This is the open-source spirit, guys. If you come here to say that open-source hackers should wait, you're on the wrong place doing the wrong stuff.
Back to honeycomb, even before this 3.1 news I was noticing that one of the main limitations we have on honeycomb is the laucher. I suggest that while we can't hack it (but we will keep trying), we use honeycomb with another launcher just for the sake of using the great tablet oriented apps we can't have on cm7.
About the source code, for me Google made clear that they weren't releasing it for a while. So, I think this is more motivation to make a honeycomb daily driver.
Keep up the great work, Good luck everyone and all hail to this awesome community.
--
Marlon Moura
Keep at it man, we appreciate the work.
Unfortunately I lack the technical expertise to help keep this moving forward; however, I think an earlier poster was dead in his argument that waiting for source code is defeatist mentality for the open source "hacking" gurus out there.
I imagine that Deeper-blue could turn this into a truly polished machine....if he had the time to devote endless amounts of hours to this, but who does and that's why he's seeking assistance from other willing and capable hands.
If anything I hope others who are capable find some inspiration in the challenge and ultimately crack this one into something special.
Thanks in advance to Deeper - blue and other who continue to provide users with a cost effective tablet experience.
-Rt
I have been working on porting CM9 to the VS910. So far I have gotten it to boot to the lock screen.
What Works
Boot animation
Lock screen
SurfaceFlinger
logcat/adb shell
3d accel is half working. I have gotten SurfaceFlinger to load up and interface the proprietary drivers (from GB) correctly, but HardwareRenderer (java framework) fails because the drivers don't give up a valid config.
What Doesn't Work
Touch screen
HardwareRenderer (fails because HardwareRenderer.chooseEglConfig() returns null value)
Everything else
Currently this ROM is totally unusuable for anything except for development. At this point, I do believe it is possible to get CM9 running, but it will take a good bit of developer effort. It would be helpful for any other developers around here to give some insight on the errors that come up in the adb logs.
How To Build
Follow Google's instructions for setting up a Linux system or VM for Android AOSP building
Follow CM9 build instructions up to brunch command
git clone git://github.com/andyichr/makerom.git to a location, such as ~/android/makerom
Overlay the files in ~/android/makerom/cm9-system/overlay onto the cm9/system directory (this adds vs910 brunch)
Adjust values in makerom.sh to match your own paths (MAKE SURE TO POINT IT AT A VALID KERNEL --I didn't include instructions for building a kernel)
Adjust values in makecm9.sh to match your own paths
Run ~/android/makerom/makecm9.sh to build cm9 (this takes a long time, depending on your system)
If build is successful, run ~/makerom/makerom.sh which will output a ROM which may be flashed to the device for testing
This is very rough work, but it proves that the basic parts of CM9/ICS do function on the Revolution. The cyanogenmod developers have already added some patches to the android source which allow ICS to run using video drivers from Gingerbread. This means it should be possible to get things working.
The current major problem with this ROM is that the HardwareRenderer does not initialize. Immediately after this, the main trebuchet process is killed and the system reboots itself after a while.
I will be happy to do what I can to support the process of porting CM9 to our phones. I read that a couple of other devs may be looking into porting CM7, but I think focusing on 9 might be more worth the effort, since we already have Gingerbread.
I have also attached a logcat to this post which should give developers some idea about what exactly is broken, which will lead to the first steps of debugging and porting.
Any interested developers should fork my repo on github (git://github.com/andyichr/makerom.git) which has the build scripts and patches.
That's about it for now. I very well may have left out some steps along the way. If you try to follow this process and it doesn't work out, let me know and I'll help you out.
ROM Download (very broken --only use for testing and development)
http://www.multiupload.com/GI0MLQYTE0 - Flash this if you want to see ICS boot to the lock screen or help test/debug. It's not useful for much else at this point.
We're getting there! I've already patched the android egl framework code slightly and built a kernel. CM team already patched frameworks/base for 2.3 video drivers. We'll patch what we have to to get this thing running! I am pretty busy but I will follow this thread and I hope for this to be a collaborative, transparent porting process! Good luck!
Nice, get with Mtmichaelson and Cubed, they are working on Cm9 also!
Sent from my VS910 4G using Tapatalk
Great! I saw in the CM7 thread that thecubed put up a git repo. I'm not sure exactly what his development plan is, but I'd be happy to fork his repo and trade patches, logs, etc. The more devs we have on this, the better... it's not a trivial task and I'm sure my wife hates me by now for spending so many hrs on it so far.
If I read correctly, thecubed just got a master repository set up for the revolution, so maybe the files that are needed could be lurking in there? I'll see if I can find the link and post it here.
Here's the link: https://github.com/thecubed
BLITZ ledded adshot nitro supercharged Gingerlution
I know in irc tonight cubed was talking about it. Guess they have to work on a few things but it's coming along. Wish I knew more so I could help out in this to. Guess I could be the Guinea pig.
Sent from my VS910 4G using Tapatalk
aichrist said:
Great! I saw in the CM7 thread that thecubed put up a git repo. I'm not sure exactly what his development plan is, but I'd be happy to fork his repo and trade patches, logs, etc. The more devs we have on this, the better... it's not a trivial task and I'm sure my wife hates me by now for spending so many hrs on it so far.
Click to expand...
Click to collapse
Awesome job so far! For a lot of things to work correctly, it's my understanding that you'll need a new kernel. For at least the touchscreen issues, you need the "idc" file in the "/system/usr/idc" directory (not sure if you have that or not, I didn't get a chance to check yet)
Either way, if you'd like to get in contact with me, hop on IRC and I'd be happy to answer any questions you may have.
Excellent work!
indyred99 said:
I know in irc tonight cubed was talking about it. Guess they have to work on a few things but it's coming along. Wish I knew more so I could help out in this to. Guess I could be the Guinea pig.
Sent from my VS910 4G using Tapatalk
Click to expand...
Click to collapse
Yeah I see thecube's repo at https://github.com/thecubed/android_device_lge_revolution. His CM files are a lot cleaner than mine... I just copied the crespo config and haven't had time to clean it up yet. I'll do some diffs of his vs mine and see about getting things merged. My github repo has some additional files so what I could do is replace my vs910 device folder with a fork of thecube's repo.
I'm not sure whether his files are for CM7 or CM9 (or if it doesn't matter). I'm new to CM porting, but I'm not new to linux or android app development.
thecubed said:
Awesome job so far! For a lot of things to work correctly, it's my understanding that you'll need a new kernel. For at least the touchscreen issues, you need the "idc" file in the "/system/usr/idc" directory (not sure if you have that or not, I didn't get a chance to check yet)
Either way, if you'd like to get in contact with me, hop on IRC and I'd be happy to answer any questions you may have.
Excellent work!
Click to expand...
Click to collapse
Thanks for the tip. I'll check that out. So far I've mainly been banging my head on getting the adreno205 drivers working, but it sure would be nice to have touch working. That'd be the next priority.
I'm tempted to switch of 3d acceleration but I am focusing on one thing at a time.
I'll hop on IRC. Which channel are you on specifically?
As always guys, I'm happy to assist in testing. Nor very knowledgeable on coding or porting, but I can definitely put my phone at risk
BLITZ ledded adshot nitro supercharged Gingerlution
wish I knew more about this stuff so I could help
keep up the great work!
crossing fingers, hoping I'll get the chance to start making themes for CM9!
aichrist said:
Thanks for the tip. I'll check that out. So far I've mainly been banging my head on getting the adreno205 drivers working, but it sure would be nice to have touch working. That'd be the next priority.
I'm tempted to switch of 3d acceleration but I am focusing on one thing at a time.
I'll hop on IRC. Which channel are you on specifically?
Click to expand...
Click to collapse
Head over to #lgrevolution and I'll be there as IOMonster.
Yep, for ICS we need a lot of work in the KGSL department in kernel for getting proper Adreno support working... Tiamat is working on adding the new KGSL/USB/Genlock support to his MSM7X30 repo here ( http://git.tiamat-dev.com/7x30/htc-kernel-msm7x30/ ) and after that we need to merge our kernel sources with his (boardfiles, includes, configs, etc)
Booting to lockscreen is great, but there's a LOT of work to be done before we can have a "working" ICS by any stretch of the imagination... ICS is a whole new beast, unfortunately...
Cubed beat me to it.
Sent from my VS910 4G using xda premium
thecubed said:
Head over to #lgrevolution and I'll be there as IOMonster.
Yep, for ICS we need a lot of work in the KGSL department in kernel for getting proper Adreno support working... Tiamat is working on adding the new KGSL/USB/Genlock support to his MSM7X30 repo here ( http://git.tiamat-dev.com/7x30/htc-kernel-msm7x30/ ) and after that we need to merge our kernel sources with his (boardfiles, includes, configs, etc)
Booting to lockscreen is great, but there's a LOT of work to be done before we can have a "working" ICS by any stretch of the imagination... ICS is a whole new beast, unfortunately...
Click to expand...
Click to collapse
Great --I'll be on the channel as achristianson or achristi.
Thanks so much for all that info.
I'm sure it is a long road to a fully working ICS. I see it as a challenge and will just keep fixing the next broken thing...
I'd be happy to test this. I got a spare revo cuz I had a warranty and this dent on the outer corner was driving me nuts.
Gingerfused Gingervolt 1.3 + Blitz
It's really awesome to see everyone working on this. I really wish I knew more about this stuff to be able to help. All this is really making me wanna read up on this stuff and learn how to do some of it. Until that happens, I'll be more than happy to help out with any testing or in any other way within my capabilities. I got a Revo just sitting there deactived waiting for that ICS goodness.
Thanks a lot for everyone working on this. Those of us that aren't as gifted really aprreciate the work you guys are putting in.
Grizzy3 said:
It's really awesome to see everyone working on this. I really wish I knew more about this stuff to be able to help. All this is really making me wanna read up on this stuff and learn how to do some of it. Until that happens, I'll be more than happy to help out with any testing or in any other way within my capabilities. I got a Revo just sitting there deactived waiting for that ICS goodness.
Thanks a lot for everyone working on this. Those of us that aren't as gifted really aprreciate the work you guys are putting in.
Click to expand...
Click to collapse
If you've noticed my post in the CM7 Thread, which somehow 'feels' like it's sparked something off here (maybe just timing, lol), I am beginning to work on this stuff.
Anyone can do it, but the problem is motivation and the willingness to learn something new. You will never learn this stuff unless you're willing to fail and fail again. You learn by mistakes and mistakes sometimes turn into innovation for new things and ideas.
There is a lot of Dev's all of a sudden and I do agree, it's great to see. I was almost about to start looking at the Nexus. When I realized I would lose out on the $130 of extra accessories for my Revo (Car Dock, home dock, extra battery, car charge, etc.), And the fact the the Nexus had no External SD Card, I was like... Nah.. Time to step up and see what I can do to make the Revo a well-supported, up to date, kick-ass device. If LG and Verizon wanna sit on their asses, let'em. We make the phone better anyhow, right? MT, Cubed, and anyone else who has already contributed so much, has made this phone 10X's what it ever was out of the box. And, unlike LG and Verizon, Dev's like MT (and others) don't give us the run around on the next release, but a timeline.
-Cybie
Cybie257 said:
If you've noticed my post in the CM7 Thread, which somehow 'feels' like it's sparked something off here (maybe just timing, lol), I am beginning to work on this stuff.
Anyone can do it, but the problem is motivation and the willingness to learn something new. You will never learn this stuff unless you're willing to fail and fail again. You learn by mistakes and mistakes sometimes turn into innovation for new things and ideas.
There is a lot of Dev's all of a sudden and I do agree, it's great to see. I was almost about to start looking at the Nexus. When I realized I would lose out on the $130 of extra accessories for my Revo (Car Dock, home dock, extra battery, car charge, etc.), And the fact the the Nexus had no External SD Card, I was like... Nah.. Time to step up and see what I can do to make the Revo a well-supported, up to date, kick-ass device. If LG and Verizon wanna sit on their asses, let'em. We make the phone better anyhow, right? MT, Cubed, and anyone else who has already contributed so much, has made this phone 10X's what it ever was out of the box. And, unlike LG and Verizon, Dev's like MT (and others) don't give us the run around on the next release, but a timeline.
-Cybie
Click to expand...
Click to collapse
Exactly how i feel. Forget LG and Verizon. You guys are the ones taking these average phones into something great. I definitely gave up on getting any real support from either of them.
I really want to start getting into this. I have a little bit of time on my hands and will definitely be reading up on all this. I think you sparked something with your post lol. I know other people like MT and theCubed were already working on some things but I think you definitely added a little spark lol. Very happy to see other people jumping on board to help out. Hopefully I can too
Grizzy3 said:
Exactly how i feel. Forget LG and Verizon. You guys are the ones taking these average phones into something great. I definitely gave up on getting any real support from either of them.
I really want to start getting into this. I have a little bit of time on my hands and will definitely be reading up on all this. I think you sparked something with your post lol. I know other people like MT and theCubed were already working on some things but I think you definitely added a little spark lol. Very happy to see other people jumping on board to help out. Hopefully I can too
Click to expand...
Click to collapse
Yup! The motivation for me has been that support by LG and VZ is diminishing. This is the beauty of open source, though. Now the community can support it.
I believe the Revolution really is a good phone. It's got a good GPU and CPU. It's not dual-core, no, but with a good ROM on there, it can be much more efficient than a dual-core phone that is loaded with crapware.
Cybie did inspire me to put my work up sooner so that we can all focus on it and not duplicate our efforts as much.
thecubed said:
Head over to #lgrevolution and I'll be there as IOMonster.
Yep, for ICS we need a lot of work in the KGSL department in kernel for getting proper Adreno support working... Tiamat is working on adding the new KGSL/USB/Genlock support to his MSM7X30 repo here ( http://git.tiamat-dev.com/7x30/htc-kernel-msm7x30/ ) and after that we need to merge our kernel sources with his (boardfiles, includes, configs, etc)
Booting to lockscreen is great, but there's a LOT of work to be done before we can have a "working" ICS by any stretch of the imagination... ICS is a whole new beast, unfortunately...
Click to expand...
Click to collapse
OK so I was doing more debugging last night in the EGL/SurfaceFlinger/HardwareRenderer code. I also looked at some of Tiamat's work on the MSM7X30 kernel.
I can see now what you mean with regard to merging parts of that kernel into our own. I am assuming that kernel is being crafted to work with ICS-friendly EGL blobs for the adreno205. Is that correct? If so, then that kernel would have code that would be required to talk to the binary blob EGL drivers for Adreno205 that we would pull from some device that has the same chip and has official proprietary drivers for ICS available. I believe the HTC Droid Incredible 2 is one such device. Is this roughly what you were thinking?
I initially had thought of going down a different path: Instead of using newer ICS proprietary drivers and updating our kernel to support it, I was planning on keeping the kernel we have and the binary drivers we have, which are already made to work with each other. The work then required to get ICS working would be to change parts of the ICS userspace code such that they'd work with our older drivers. I don't have the links on hand, but I believe this is possible because I read about others taking this strategy on other devices that do not have ICS support officially but do have proper GB support. It also makes sense to me logically that the userspace code could be changed to our heart's content to work with older drivers, since we have full access to that source code. One option that I read about that we could potentially do is write a wrapper for the *adreno200*so librares that would implement the newer API that ICS is expecting and would translate the calls into the older API that is supported in our GB proprietary drivers.
It looks to me like we have two possible ways forward with regard to getting hardware acceleration working: upgrading the kernel and drivers to have "proper" ICS support, or patching ICS userspace code to work with GB drivers and kernel. I believe that patching the ICS userspace code would get us up and running faster while upgrading the kernel and adding newer drivers would be the better long-term solution.
Here are a couple of patches that people have already implemented to support older EGL blobs/kernels:
https://github.com/VorkTeam/android_frameworks_base/commit/429e922fb6f2660fc40472e939175688af52b1d2
https://gist.github.com/CyanogenMod...mmit/5d689bd02531f8ff256b3b1eddcaa8040c9f3559
https://gist.github.com/CyanogenMod...mmit/f8e2430be2d6b3e88afd7190f6712f3bc1df0cbf
Let me know what you think.
Also, what do you think about using the BOARD_USES_QCOM_HARDWARE := true directive to our CM board configuration? I noticed references to the QCOM_HARDWARE flags all over the video code. It seems we would want this since we are using a QCOM video chip. The only problem is the build failed for me when I added this flag. There's an issue about it on github: https://github.com/CyanogenMod/android_hardware_qcom_display/issues/3#issuecomment-3457179.
aichrist said:
OK so I was doing more debugging last night in the EGL/SurfaceFlinger/HardwareRenderer code. I also looked at some of Tiamat's work on the MSM7X30 kernel.
I can see now what you mean with regard to merging parts of that kernel into our own. I am assuming that kernel is being crafted to work with ICS-friendly EGL blobs for the adreno205. Is that correct? If so, then that kernel would have code that would be required to talk to the binary blob EGL drivers for Adreno205 that we would pull from some device that has the same chip and has official proprietary drivers for ICS available. I believe the HTC Droid Incredible 2 is one such device. Is this roughly what you were thinking?
I initially had thought of going down a different path: Instead of using newer ICS proprietary drivers and updating our kernel to support it, I was planning on keeping the kernel we have and the binary drivers we have, which are already made to work with each other. The work then required to get ICS working would be to change parts of the ICS userspace code such that they'd work with our older drivers. I don't have the links on hand, but I believe this is possible because I read about others taking this strategy on other devices that do not have ICS support officially but do have proper GB support. It also makes sense to me logically that the userspace code could be changed to our heart's content to work with older drivers, since we have full access to that source code. One option that I read about that we could potentially do is write a wrapper for the *adreno200*so librares that would implement the newer API that ICS is expecting and would translate the calls into the older API that is supported in our GB proprietary drivers.
It looks to me like we have two possible ways forward with regard to getting hardware acceleration working: upgrading the kernel and drivers to have "proper" ICS support, or patching ICS userspace code to work with GB drivers and kernel. I believe that patching the ICS userspace code would get us up and running faster while upgrading the kernel and adding newer drivers would be the better long-term solution.
Here are a couple of patches that people have already implemented to support older EGL blobs/kernels:
https://github.com/VorkTeam/android_frameworks_base/commit/429e922fb6f2660fc40472e939175688af52b1d2
https://gist.github.com/CyanogenMod...mmit/5d689bd02531f8ff256b3b1eddcaa8040c9f3559
https://gist.github.com/CyanogenMod...mmit/f8e2430be2d6b3e88afd7190f6712f3bc1df0cbf
Let me know what you think.
Also, what do you think about using the BOARD_USES_QCOM_HARDWARE := true directive to our CM board configuration? I noticed references to the QCOM_HARDWARE flags all over the video code. It seems we would want this since we are using a QCOM video chip. The only problem is the build failed for me when I added this flag. There's an issue about it on github: https://github.com/CyanogenMod/android_hardware_qcom_display/issues/3#issuecomment-3457179.
Click to expand...
Click to collapse
You guys are great! I hope this is doable, keep up the hard work..
Sent from my Nexus S 4G using XDA App
Before any of you say anything negative this isnt to bug other devs this is a thread for people to request/ ask for things me and the other devs to do after they have finished their other projects.
-Firefox OS
-LG UI(fix lockscreen)
-CM7
-Sense 4.1
-cm10.1 WiFi and Bluetooth
-cm10 WiFi authentication issue
-S-OFF
-Roms for cdma version
-Sense 4.1.2
Just pop requests underneath and ill update reguarly.
Shad0wPanda said:
Before any of you say anything negative this isnt to bug other devs this is a thread for people to request/ ask for things me and the other devs to do after they have finished their other projects.
-Firefox OS
-LG UI
-CM7
Just pop requests underneath and ill update reguarly.
Click to expand...
Click to collapse
Sense 4.1 (If possible)
Shad0wPanda said:
Before any of you say anything negative this isnt to bug other devs this is a thread for people to request/ ask for things me and the other devs to do after they have finished their other projects.
-Firefox OS
-LG UI
-CM7
Just pop requests underneath and ill update reguarly.
Click to expand...
Click to collapse
Hahaha, heres an LG UI Rom, iv'e had it for a while, just lockscreen doesnt work at all! so slide down NC and hit settings to unlock, then install a custom locker such as holo locker! I'll post in the dev threads when i can be bothered, but test that out..
http://d-h.st/2V2
Click to expand...
Click to collapse
i think gettin bt and wifi implemented in cm 10.1 should be a good place to begin
lead3r1 said:
i think gettin bt and wifi implemented in cm 10.1 should be a good place to begin
Click to expand...
Click to collapse
+1
but we really need the devs to go back to work
CM7 FTW
CM7 first ... it would be super buttery smooth for us ...
How are you so certain it'd be "buttery smooth"? Cuz I'm not sure, if not totally negative on that matter.
How are you so certain it'd be "buttery smooth"? Cuz I'm not sure, if not totally negative on that matter.
Click to expand...
Click to collapse
Brnt you don't have to flash cm7... What's with all the gingerbread hate??
Sent from my HTC Desire C using xda app-developers app
I suggest we go back to XP then. It's going to run so much better on our new PCs!
It's not hate, you just get overexcited over nothing without even putting some though into it. Go on, prove me gingerbread will run smoother than JB/ICS, but without these facts your words are nothing.
brnt said:
I suggest we go back to XP then. It's going to run so much better on our new PCs!
It's not hate, you just get overexcited over nothing without even putting some though into it. Go on, prove me gingerbread will run smoother than JB/ICS, but without these facts your words are nothing.
Click to expand...
Click to collapse
I think you have your analogy wrong. Going from a newer version of Windows to an older version of Windows is pointless because...well...it's still Windows.
However, if you were to go from Ubuntu to, say, Slackware, you would definitely see a boost in performance because Slackware is far less taxing on the available resources. The same could be said about going from JB to GB. GB requires less resources and can therefore run smoother/faster on hardware designed for a higher version of Android. This is a well known fact throughout the Android community because nearly every JB or ICS based device has GB ROM development in some form or another.
It's still Android. Roughly 90% of the differences between JB/ICS and GB lie in the overall appearence, not the functionality.
IDEA
Or lets make CM10 even better
Like eliminate WiFi problems and hotspot problems etc :fingers-crossed:
What do you think?
S off would be good.
Not first priority though
sent from CM10'd Desire C
Phenziox said:
S off would be good.
Not first priority though
sent from CM10'd Desire C
Click to expand...
Click to collapse
It would be very useful though but it's more HTCs job
Sent from my HTC Desire C using xda premium
@soupmagnet, i agree entirely with that statement, however, where is the desire coming from for having GingerBread Roms? if it was desired so much, then why not buy a gingerbread phone in the first place? Would've been cheaper and there are still devices on the market, some with faster processors then the Desire C, if you wanted GingerBread, should've bought a GB Device, you don't go buy a brand new Windows 8 PC to deliberately downgrade it to a legacy OS like vista and limit the features you have access to. It lacks all logic in all honesty.. You don't go to sell a phone after use being all like, Yeah it has 2.3.5 GB on it, or brag to your mates, yeah my device is android 2.3.5, fact is 4.2.2 is the best android so far, Android has only improved over time, GB on our device is like an i7 with vista, you just don't do that kind of thing..
penguin449 said:
@soupmagnet, i agree entirely with that statement, however, where is the desire coming from for having GingerBread Roms? if it was desired so much, then why not buy a gingerbread phone in the first place? Would've been cheaper and there are still devices on the market, some with faster processors then the Desire C, if you wanted GingerBread, should've bought a GB Device, you don't go buy a brand new Windows 8 PC to deliberately downgrade it to a legacy OS like vista and limit the features you have access to. It lacks all logic in all honesty.. You don't go to sell a phone after use being all like, Yeah it has 2.3.5 GB on it, or brag to your mates, yeah my device is android 2.3.5, fact is 4.2.2 is the best android so far, Android has only improved over time, GB on our device is like an i7 with vista, you just don't do that kind of thing..
Click to expand...
Click to collapse
The problem with your logic is that Gingerbread based devices (with a few exceptions) only have hardware that is capable of meeting the low demands of Gingerbread.
For many people, the worth of their device is in its functionality, not its "bragging rights". I will never have Windows on my computer simply because of the features it provides. I use Linux, because of it's speed, stability and and overall functionality. ICS and JB do have some nice additional features, but at a noticeable cost of available resources and stability, and the overall functionality is still nearly the same. While higher versions of Android do provide some "improvements", they are mostly linked to the user interface (which many people don't necessarily like) and there are very few performance improvements. So for you to say that it "lacks all logic" is, well, illogical in itself.
While you may like what JB and ICS have to offer and prefer that for your daily driver, I don't think it's fair to ridicule others' personal preference in Android versions, considering the majority of changes between these versions are exclusive to the UI and not Android itself.
Off-topic... naughty naughty
Sent from my HTC Desire C using xda premium
Getting back on topic...
It would be nice to see more CDMA support though. I have a shell script, based on bin4ry's exploit, to root the CDMA variants, but it needs to be converted over to Windows' batch scripting language. If anyone wants to have a go at it, just let me know.
As far as ROMs are concerned, we can use the existing GSM ROMs, but a patch will need to be made. It wouldn't be that difficult to implement and would be much easier than creating all new CDMA ROMs.
The biggest problem would be getting a working recovery. I tried unpacking the existing (GSM) recovery and replaced the kernel with the phone's stock kernel but it didn't work out very well. I think a new recovery would need to be built from source, but I'm running into strange compile errors when compiling the stock kernel from source. I don't have experience building custom recovery so it's going to be challenging trying to figure everything out, but I think I can handle it.
Clearly, the need for CDMA support is low, but it's far from non-existent. I'm more than willing to take the reigns on this project, but I may have to take advantage of some of the experience around here, assuming there are those willing to lend a hand.
soupmagnet said:
The problem with your logic is that Gingerbread based devices (with a few exceptions) only have hardware that is capable of meeting the low demands of Gingerbread.
For many people, the worth of their device is in its functionality, not its "bragging rights". I will never have Windows on my computer simply because of the features it provides. I use Linux, because of it's speed, stability and and overall functionality. ICS and JB do have some nice additional features, but at a noticeable cost of available resources and stability, and the overall functionality is still nearly the same. While higher versions of Android do provide some "improvements", they are mostly linked to the user interface (which many people don't necessarily like) and there are very few performance improvements. So for you to say that it "lacks all logic" is, well, illogical in itself.
While you may like what JB and ICS have to offer and prefer that for your daily driver, I don't think it's fair to ridicule others' personal preference in Android versions, considering the majority of changes between these versions are exclusive to the UI and not Android itself.
Click to expand...
Click to collapse
I stand corrected, thankyou for clearing that up for me, i never thought to look at it in this way, however, when you do get a working recovering, i do so believe i added cdma support in SHTD, the rom was both configured for cdma and for gsm, as it is in the build.prop also!, however a cdma aosp kernel would be needed
cm10.1 wifi bluetooth fixed would be a cool rom... Devs plz fix it... We noobs will be greatfull to you......:laugh::laugh::good:
akashgartia said:
cm10.1 wifi bluetooth fixed would be a cool rom... Devs plz fix it... We noobs will be greatfull to you......:laugh::laugh::good:
Click to expand...
Click to collapse
Don't rush them. They have other stuff to do. If you want it done, you could learn and try it yourself.