Related
Is anyone going to build a FroYo rom for the vogue?
If memory serves, Eclair was announced/released on phones for months before AOSP ever had a hold of it.
If it takes months again for Froyo to be released, I'll probably have moved on. However, if AOSP does get Froyo in a reasonable amount of time, I'll do enough to at least dabble in it and create something. No promises on functionality.
I'll be at Google I/O next week, and I have plenty of questions, one of which is how soon we'll see Froyo on AOSP and if it'll be brought up to speed at faster, more regular intervals.
Tell them Google people that they promised me a pony!
Shidell said:
If memory serves, Eclair was announced/released on phones for months before AOSP ever had a hold of it.
If it takes months again for Froyo to be released, I'll probably have moved on. However, if AOSP does get Froyo in a reasonable amount of time, I'll do enough to at least dabble in it and create something. No promises on functionality.
I'll be at Google I/O next week, and I have plenty of questions, one of which is how soon we'll see Froyo on AOSP and if it'll be brought up to speed at faster, more regular intervals.
Click to expand...
Click to collapse
Isn't there a rom out for the Droid or Nexus already?
This is supposed to have a 250% increase in speed, that would be sweet
berardi said:
This is supposed to have a 250% increase in speed, that would be sweet
Click to expand...
Click to collapse
I heard it was a 450% increase... and I know theres at least a few people running froyo on thier Nexus
as soon as we see a froyo dump we'll see if our libs/kernel will work with it. If not we'll have to wait until the aosp is updated to compile the drivers for froyo.
loserskater said:
I heard it was a 450% increase... and I know theres at least a few people running froyo on thier Nexus
Click to expand...
Click to collapse
sure there's a 450% inc on systems with a FPU built in, we don't have one so we'll only see a 200% or so if that
mrono said:
sure there's a 450% inc on systems with a FPU built in, we don't have one so we'll only see a 200% or so if that
Click to expand...
Click to collapse
Let's not pretend a 200 percent increase wouldn't be awesome.
TheKartus said:
Let's not pretend a 200 percent increase wouldn't be awesome.
Click to expand...
Click to collapse
This is so true!
fyi, our libs don't work natively on froyo. We'll have to wait for the aosp to be updated so we can make the required adjustments and compile them for it.
mssmison said:
fyi, our libs don't work natively on froyo. We'll have to wait for the aosp to be updated so we can make the required adjustments and compile them for it.
Click to expand...
Click to collapse
How long is that usually from SDK release? 2.2 looks really fun.
looks fun, runs slow on the vogue. Mind you this is only the sdk build (which is usually slower and more buggy in the begining).
Hopefully it won't take too long.
It probably wont fit on nand.
Also they say froyo 2.2 is lik 5x faster than eclair.
My guess as to why its faster is 2 things;
better coding
More of the mobile operating system is in the ram
(which is why it will be running faster)
Since all the newer devices have a crap load of rom and ram, this wont be a problem.
But for us vogue users who have limited rom and ram, this will mean we will run it off the sd card; which is ok......
Overall i do hope it runs than i anticipate.
intimidatorx31 said:
It probably wont fit on nand.
Also they say froyo 2.2 is lik 5x faster than eclair.
My guess as to why its faster is 2 things;
better coding
More of the mobile operating system is in the ram
(which is why it will be running faster)
Since all the newer devices have a crap load of rom and ram, this wont be a problem.
But for us vogue users who have limited rom and ram, this will mean we will run it off the sd card; which is ok......
Overall i do hope it runs than i anticipate.
Click to expand...
Click to collapse
Couldn't it be possible to reduce it's size? Removing applications and unnecessary gadgets?
It is reasonable to assume that we could fit a stock build of Froyo onto the Vogue's NAND memory--especially given that Froyo natively supports transitioning applications to the SD card. It remains to be seen what size a stock Froyo build will be (roughly).
Froyo is optimized, sure--but the majority of the speed increase is coming from the trace JIT compiler. (The browser will be faster rendering Javascript as well thanks to the V8 engine being migrated in from the Chrome browser.)
Shidell said:
It is reasonable to assume that we could fit a stock build of Froyo onto the Vogue's NAND memory--especially given that Froyo natively supports transitioning applications to the SD card. It remains to be seen what size a stock Froyo build will be (roughly).
Froyo is optimized, sure--but the majority of the speed increase is coming from the trace JIT compiler. (The browser will be faster rendering Javascript as well thanks to the V8 engine being migrated in from the Chrome browser.)
Click to expand...
Click to collapse
Trace JIT has quite a bit of RAM overhead - that's one of the reasons it was originally not in Android (check out the Android overview talk from 2008's Google I/O for details). And it really only tends to make CPU-heavy loops (games, artificial benchmarks) faster. On the other hand, Google claim to have optimized low-memory handling and the low memory killer/ejector (check out the Android 2.2 new features page).
However, I *highly* doubt it'll fit in NAND - that's the reason Google's cited for never bringing 2.2 to the G1 (in a fireside talk with Gizmodo).
At any rate, if Froyo isn't coming to the G1 family, we won't get 3D drivers (which need to be updated) for the Vogue either, so we're probably dead out of luck. It'll run, but without GL drivers the experience will probably not be great. Someone might be able to shim/dummy in the older ones (especially once AOSP is out) but I wouldn't get my hopes up too far.
Don't get me wrong, I'd love Froyo on the Vogue, but there are a lot of reasons it's a pipe dream.
The V8 improvements have already been backported to Eclair (The Eclair branch of Cyanogenmod has had V8 is a compile time selection for ages - it's disabled by default mostly due to an incompatibility with some JS used in the Epocrates app) so we might see those. The stable JIT might get backported onto the existing hacky / open-source Eclair one as well.
Mmm...Android FroYo...
1. yes froyo fits on nand no problem,
2. the 3d drivers work just fine that we're already using
3. the reason it was slow (when I mentioned it) was becuase of the un optimized apk's, and of course the new launcher 2. it runs much better with an alternative launcher. Though it's not really any faster than eclair at this point. More testing is required.
4. yes once aosp is out we'll get the libs updated and get full compatibility. (or as close as we can)
bri3d said:
Trace JIT has quite a bit of RAM overhead - that's one of the reasons it was originally not in Android (check out the Android overview talk from 2008's Google I/O for details). And it really only tends to make CPU-heavy loops (games, artificial benchmarks) faster. On the other hand, Google claim to have optimized low-memory handling and the low memory killer/ejector (check out the Android 2.2 new features page).
However, I *highly* doubt it'll fit in NAND - that's the reason Google's cited for never bringing 2.2 to the G1 (in a fireside talk with Gizmodo).
At any rate, if Froyo isn't coming to the G1 family, we won't get 3D drivers (which need to be updated) for the Vogue either, so we're probably dead out of luck. It'll run, but without GL drivers the experience will probably not be great. Someone might be able to shim/dummy in the older ones (especially once AOSP is out) but I wouldn't get my hopes up too far.
Don't get me wrong, I'd love Froyo on the Vogue, but there are a lot of reasons it's a pipe dream.
The V8 improvements have already been backported to Eclair (The Eclair branch of Cyanogenmod has had V8 is a compile time selection for ages - it's disabled by default mostly due to an incompatibility with some JS used in the Epocrates app) so we might see those. The stable JIT might get backported onto the existing hacky / open-source Eclair one as well.
Click to expand...
Click to collapse
Now I'm no expert and only spouting off what I had read somewhere else, FROYO will really not benefit the vogue or kaiser at all. Its the JIT that will help us on other builds correct me if I'm wrong but there is something else in froyo that makes the big difference. Froyo utilizes a part of the processor in the N1 that's not been used in older builds this is where the added speed comes from. Granted it would be nice if I'm wrong though. I'm sure some of you others are more in the know than I am.
Guys you can recommend me some good android as i am bored using windows mobile since 6 years.
I want a good capable android probably with Capacitive screen and a good camera, processor and ram. I am thinking of X10 is that a good phone.
Thanks
Eh, I hear lost of bad about the X10. Why not try the Desire or Nexus one? Possibly the Galaxy S even...
i'm using a htc desire ATM and no complaint from here, running it on froyo custom rom
the n1 is good running froyo custom rom on it as well
My bro brought htc tattoo but either he or me liked it much as WM phones.
Reason :
1. Its hard to find apps for android. I know there are lots of apps for android but see #2
2. Even if you find one, 99% it will be a barcode/qc code download or phone download link but no pc download link so you will need phone with GPRS or WIFI or 3G to download and install. This is hard for Indian users
3. You cannot use pc to phone internet via USB or not even bluetooth, like WM phones.
4. You cannot install apps on sd but only on mainmemory, thank god tattoo has enough memory ( 512mb )
I think these all related to all android phones.
As you wish but I prefer WM phone the most!
Best Regards
CRACING said:
My bro brought htc tattoo but either he or me liked it much as WM phones.
Reason :
1. Its hard to find apps for android. I know there are lots of apps for android but see #2
2. Even if you find one, 99% it will be a barcode/qc code download or phone download link but no pc download link so you will need phone with GPRS or WIFI or 3G to download and install. This is hard for Indian users
3. You cannot use pc to phone internet via USB or not even bluetooth, like WM phones.
4. You cannot install apps on sd but only on mainmemory, thank god tattoo has enough memory ( 512mb )
I think these all related to all android phones.
As you wish but I prefer WM phone the most!
Best Regards
Click to expand...
Click to collapse
1. What? I seem to remember the Market app on Android that has plenty of applications to use.
3. Um, if he gets a new device: FroYo. If not, I've had tethering on my G1/Dream since I rooted.
4. FroYo, I've had it on my G1/Dream since I rooted.
I find your argument invalid.
Stick with xda support & a htc froyo device...
JAguirre1231 said:
1. What? I seem to remember the Market app on Android that has plenty of applications to use.
3. Um, if he gets a new device: FroYo. If not, I've had tethering on my G1/Dream since I rooted.
4. FroYo, I've had it on my G1/Dream since I rooted.
I find your argument invalid.
Click to expand...
Click to collapse
Ah sorry I forgot to mention, I'm using official ROM on my tattoo and there are no updates for it.
May be the new versions doesn't have such issues. But for our tattoo owners. :'(
Yes there are lots of app but something doesn't suits me then WM apps downloads.
Anyways, sorry if I said anything or totally wrong.
Best Regards
Now i think nexus one or htc desire would be good. Only problem with nexus one is no capacitive screen. I like x10 also because of its 8 mp camera and all other features are same as nexus one, what say guyz i am confused now.
CRACING said:
Ah sorry I forgot to mention, I'm using official ROM on my tattoo and there are no updates for it.
May be the new versions doesn't have such issues. But for our tattoo owners. :'(
Yes there are lots of app but something doesn't suits me then WM apps downloads.
Anyways, sorry if I said anything or totally wrong.
Best Regards
Click to expand...
Click to collapse
Ah, the tattoo. No wonder you like WM better with that phone, under-powered AND it has Sense.
samy.3660 said:
Now i think nexus one or htc desire would be good. Only problem with nexus one is no capacitive screen. I like x10 also because of its 8 mp camera and all other features are same as nexus one, what say guyz i am confused now.
Click to expand...
Click to collapse
Nexus One has a capacitive screen...
Thumbs down for X10 from me.
No multitouch means no full speed typing on the soft keyboard.
Outdated Android OS version.
Very plastic and cheap build.
Timescape performance is laggy.
Wide reports of battery drain. Likely to be software related.
As of this moment, I think you've got a choice between the following:
Nexus One, Desire, Droid Incredible, Evo (depending on geographic location)
Galaxy S
Droid, Droid X
ohyeahar said:
Nexus One has a capacitive screen...
Thumbs down for X10 from me.
No multitouch means no full speed typing on the soft keyboard.
Outdated Android OS version.
Very plastic and cheap build.
Timescape performance is laggy.
Wide reports of battery drain. Likely to be software related.
As of this moment, I think you've got a choice between the following:
Nexus One, Desire, Droid Incredible, Evo (depending on geographic location)
Galaxy S
Droid, Droid X
Click to expand...
Click to collapse
Nexus one doesn't have capacitive screen(Multi touch), i have checked it with pdadb.net and also on google official site
samy.3660 said:
Nexus one doesn't have capacitive screen(Multi touch), i have checked it with pdadb.net and also on google official site
Click to expand...
Click to collapse
"Capacitive screen" doesn't necessarily equal "multi-touch".
For example, the X10 has a capacitive screen but it doesn't support multi-touch. It's because of the hardware. Regardless of what software updates Sony Ericsson rolls out, the X10 will not get multi-touch support.
However, the Nexus One does indeed have a capacitive screen. And the hardware supports multi-touch. In fact, it's the same screen as used in the HTC Desire. Whether or not multi-touch works, depends on the software. For example, it was mentioned in reviews that there's no multi-touch support right out the box; but certain applications like Dolphin Browser can utilize pinch-to-zoom.
So i think i have 2 options now samsung Galaxy S and Nexus one.
Which one to go for and Why, please??
Do you guys think it is worth going for motorola milestone, if i am getting it lot cheaper than nexus one. i think only drawback in milestone is slow processor and ram. Do you think 600mhz processor and 256 ram is not enough for new android builds like froyo or future one ginger bread??
samy.3660 said:
Do you guys think it is worth going for motorola milestone, if i am getting it lot cheaper than nexus one. i think only drawback in milestone is slow processor and ram. Do you think 600mhz processor and 256 ram is not enough for new android builds like froyo or future one ginger bread??
Click to expand...
Click to collapse
Certainly the Droid/Milestone can handle Froyo since it's going to be officially released as an OTA update by Motorola. Not sure about Gingerbread though. There's not much information on that anywhere and there's conflicting reports on what are the minimum specs.
I'm not a fan of the Milestone/Droid, so I wouldn't recommend it. The hardware keyboard is a defining feature of the device and yet, it's so poorly designed and near unusable. But that's just my opinion; perhaps you're alright with it...
with the release of froyostone rom for the hd2 which is sense + 2.2 officially from htc, I believe it would be much easier to port sense to the captivate and completely remove touchwiz.
First your posting in the wrong captivate forum section...second the Android os isn't something that can be magically ported to XX device just because XXX device has it or its working on it, for starters the hd2 is a non native android device, which means its running an android port, with the help of a half working linux kernel, loaded with haret bootloader, android 2.2 is coming in September so just sit tight and be patient, or you can download CM6 vibrant source and port it over to the captivate(you would have to make the captivates kernel compatible with 2.2, meaning backporting/patching etc) which ever you like.
Rafyvitto
Yeah it ought to be about as easy as loading OS X on a Commodore 64.
gunnyman said:
Yeah it ought to be about as easy as loading OS X on a Commodore 64.
Click to expand...
Click to collapse
Well, maybe Steve can call Xerox for some help with that...
dressanderc said:
Well, maybe Steve can call Xerox for some help with that...
Click to expand...
Click to collapse
I LOL'ed +tenchars
gunnyman said:
Yeah it ought to be about as easy as loading OS X on a Commodore 64.
Click to expand...
Click to collapse
dressanderc said:
Well, maybe Steve can call Xerox for some help with that...
Click to expand...
Click to collapse
ROFL thats some good stuff guys.
who wants sense anyways, it's just a big shiney TURD!
designgears said:
who wants sense anyways, it's just a big shiney TURD!
Click to expand...
Click to collapse
+1
where's some good ol' fashioned AOSP when you need it?
*hint hint* DG *hint*
Personally, I cant wait till all manufacturers realize we don't want to be forced into sense, touch wiz etc.
Make it default if you have to, but provide an option to enjoy raw, unadulterated android!!!
I guess we wait and see what Gingerbread does about that.
To the OP, why don't YOU port Android 2.2 to the Captivate AND also port Sense??
Joking aside I am going to be cooking for the Captivate soon. I'm just waiting for Froyo so I can get my hands dirty with Android .
Maybe even a Sense port??
I've been working on porting sense to our the device for some weeks now but roms fail to boot, changing libs etc, got no clue of what else to try.
Sense is so deeply entangled into Android, kinda like trying to remove Internet Explorer from Windows 95, It is virtually impossible to get it working without all the kernel extensions HTC added to the OS.
gunnyman said:
Sense is so deeply entangled into Android, kinda like trying to remove Internet Explorer from Windows 95, It is virtually impossible to get it working without all the kernel extensions HTC added to the OS.
Click to expand...
Click to collapse
Just a historical footnote. Internet explorer was very easy to remove from windows 95. The original release of win95 didn't even include internet explorer. It was only available as part of the plus! Pack of addons. The SR1 release had IE v2 included but it could be easily deleted. It wasn't until IE 4 that active desktop became a part of the package and began making it difficult to seperate from the OS. IE 4 came sr2.5 but was an optional upgrade for most win95 instalations.
But i knew what you meant.
Sent from my SAMSUNG-SGH-I897 using XDA App
jaredc74 said:
Just a historical footnote. Internet explorer was very easy to remove from windows 95. The original release of win95 didn't even include internet explorer. It was only available as part of the plus! Pack of addons. The SR1 release had IE v2 included but it could be easily deleted. It wasn't until IE 4 that active desktop became a part of the package and began making it difficult to seperate from the OS. IE 4 came sr2.5 but was an optional upgrade for most win95 instalations.
But i knew what you meant.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
haha, I was literally going to add almost exactly this.
Sense seems only to be portable to devices that can run off of HTC-based ROMs. It seems to be much easier to remove it than to try and bring it over (I haven't heard of it being brought to a device that wasn't HTC based). The widgets haven't even been ported to the best of my knowledge to work on non-Sense launchers. And, as proven by our phones, they could have made Sense even MORE integrated considering removing touchwiz launcher causes massive force closes. Also, Sense is proprietary and cosed source, so we don't have any low-level access to remove the HTC restrictions (short of binary hacking, which I know nothing about and could indeed be wrong about)
Kaik541 said:
haha, I was literally going to add almost exactly this.
Sense seems only to be portable to devices that can run off of HTC-based ROMs. It seems to be much easier to remove it than to try and bring it over (I haven't heard of it being brought to a device that wasn't HTC based). The widgets haven't even been ported to the best of my knowledge to work on non-Sense launchers. And, as proven by our phones, they could have made Sense even MORE integrated considering removing touchwiz launcher causes massive force closes. Also, Sense is proprietary and cosed source, so we don't have any low-level access to remove the HTC restrictions (short of binary hacking, which I know nothing about and could indeed be wrong about)
Click to expand...
Click to collapse
Well how the huck did they get Sense on the HD2?? It doesn't even come with android from factory! We need someone to shed a little more light in this. Maybe its because they use some Qualcomm specific images or something.
rafyvitto said:
I've been working on porting sense to our the device for some weeks now but roms fail to boot, changing libs etc, got no clue of what else to try.
Click to expand...
Click to collapse
You got a PM
DJGonzo said:
Well how the huck did they get Sense on the HD2?? It doesn't even come with android from factory! We need someone to shed a little more light in this. Maybe its because they use some Qualcomm specific images or something.
Click to expand...
Click to collapse
notice how I said I can't see it being ported to a non-HTC device. The HD2 is indeed an HTC device and I believe the ROM that has Sense is one built off of an HTC ROM for another device. Much like how the Legend ROMs were able to be fairly easily/quickly ported to the Aria. In fact, many of the internals of the HD2 resemble a lot of the Android hardware produced by HTC (qualcomm snapdragon and all that good stuff I believe)... the difficulty of getting android on that device had nothing to do with the ROMs, but actually getting haret to boot a linux kernel properly.
Kaik541 said:
notice how I said I can't see it being ported to a non-HTC device. The HD2 is indeed an HTC device and I believe the ROM that has Sense is one built off of an HTC ROM for another device. Much like how the Legend ROMs were able to be fairly easily/quickly ported to the Aria. In fact, many of the internals of the HD2 resemble a lot of the Android hardware produced by HTC (qualcomm snapdragon and all that good stuff I believe)... the difficulty of getting android on that device had nothing to do with the ROMs, but actually getting haret to boot a linux kernel properly.
Click to expand...
Click to collapse
Unless they ported the whole ROM and re used drivers, I don't quite understand how they got it to work.
They got Sense 2.5 working from The HD2 onto the Omnia II (winmo), so its quite possible. We just need a team of developers willing to do the work. I can offer hosting and testing and little technical help since I am new at Android but I think we can get it to work if we start to tinker with it.
Maybe a ROM port is in order?
Maybe we should wait for a Froyo kernel though.
DJGonzo said:
Unless they ported the whole ROM and re used drivers, I don't quite understand how they got it to work.
They got Sense 2.5 working from The HD2 onto the Omnia II (winmo), so its quite possible. We just need a team of developers willing to do the work. I can offer hosting and testing and little technical help since I am new at Android but I think we can get it to work if we start to tinker with it.
Maybe a ROM port is in order?
Maybe we should wait for a Froyo kernel though.
Click to expand...
Click to collapse
I'm not saying it's impossible, I'm saying it hasn't been done. There are (correct me if I'm wrong) absolutely no non-HTC android devices with the Sense UI. I know nothing about the HD2/Omnia II Sense port, but that's WinMo... not even remotely close to Android in terms of interoperability. I also feel like any ROMs designed to bring Sense UI to non-HTC android devices would be hit with C&D's since it's their proprietary software (hence why both Fancy Widget and Beautiful Widgets got in trouble originally when they launched on the market).
Don't get me wrong, good luck in porting it, hell even I like the look of it and would love the option, but considering how long Sense has been out for android (and numerous devices) and we don't see it on any non-HTC android devices, I have to believe it's been tried and just doesn't work (which is why you also don't see MotoBLUR/NinjaBLUR anywhere else either... or even TouchWiz on the EVO)
Also I think the HD2 and the Desire are the same hardware. If not the Desire it's another phone. That also makes porting Android pretty painless.
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 ?
Here you go, Android 2.4 Honeycomb's music player apk. Yes, Android 2.4. It seems to go along nicely with gallery 3d.
Link to Source
I tried pushing this to my phone a few days ago and couldn't get it running on my eris. It wouldn't let me do a traditional install either. Do you have it running? If so, what ROM are you running?
synesthete said:
I tried pushing this to my phone a few days ago and couldn't get it running on my eris. It wouldn't let me do a traditional install either. Do you have it running? If so, what ROM are you running?
Click to expand...
Click to collapse
I have not even looked at it yet but for all I know, it may be HDPI only. That would be dumb of Google. I don't think many MDPI devices (if any) will get the official upgrade to 2.4 or 3.0, but rooters are like half or more of the user base right? I think google should be on the rooters side when it comes to this kind of thing. The G1 has gingerbread right? And that was not even supposed to get 2.0.
CPCookieMan said:
I have not even looked at it yet but for all I know, it may be HDPI only. That would be dumb of Google. I don't think many MDPI devices (if any) will get the official upgrade to 2.4 or 3.0, but rooters are like half or more of the user base right? I think google should be on the rooters side when it comes to this kind of thing. The G1 has gingerbread right? And that was not even supposed to get 2.0.
Click to expand...
Click to collapse
It probably has more to do with how much RAM this thing uses. I was reading reports of the guys in the original thread and they were saying it was sucking down 24-28mb of RAM, the Eris couldn't handle that drain, hell it pretty much takes being OC'd to handle the 3D gallery on these phones.