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.
Related
Okay I understand that the official 2.2 will not be coming to the G1 due to the outdated hardware. But I also understand that a lot of the ROM dev's are trying to transport it to here.
My question is, When the dev's do release the 2.2 can we expect the same speed upgrade as the official 2.2 does? Froyo = 450% faster on g1?
Doubt it right?
It's possible they could get the speeds that high but your phone would eventually take a massive wear and tear from overclocking and constant swap usage.
Froyo won't be quite 450% faster, but it's definitely going to have some measurable level of speed improvement with 2.2 and a JIT enabled Over-clock Kernel.
That 450% number is misleading.
It is NOT 450% faster. SOME OPERATIONS are 450% faster.
The key word being SOME.
As for 2.2 being faster... the reason it is going to be faster is because of JIT, not because of overclocking/etc.
In other words, to do the same function, it needs to do ***LESS WORK***, and because it can do the SAME amount of work in the SAME TIME as 2.1, having to do LESS work will therefore take LESS TIME.
Kemekill Products said:
It's possible they could get the speeds that high but your phone would eventually take a massive wear and tear from overclocking and constant swap usage.
Click to expand...
Click to collapse
Are you MAD?
Who said anything about overclocking and swap.
Speedup due to JIT!
JIT means that there is LESS WORK TO DO = LESS TIME to do it.
Swap usage? A well implemented JIT can actually use LESS MEMORY = still no swap needed. Who the heck wants to swap? It just slows you down!
rofl, have you seen the attempts to getting JIT working right in the pass 3 months. it's been constant failure. every rom that has JIT runs faster without it enabled. It's a nice dream.. (haha get it dream like the phones name... FUNNY)
Kemekill Products said:
rofl, have you seen the attempts to getting JIT working right in the pass 3 months. it's been constant failure. every rom that has JIT runs faster without it enabled. It's a nice dream.. (haha get it dream like the phones name... FUNNY)
Click to expand...
Click to collapse
I'm pretty sure you need to stop answering questions until you read up on a few things. The speed improvement in Froyo is because JIT is officially supported in the build by the Android team at Google.
Some people already have Froyo "running" on the G1, but it's not useable as a phone. You can expect someone to perfect and port it just like people have done with Eclair.
DirectMatrix said:
I'm pretty sure you need to stop answering questions until you read up on a few things. The speed improvement in Froyo is because JIT is officially supported in the build by the Android team at Google.
Click to expand...
Click to collapse
I'm pretty sure I watched the I/0 conference and know all about it. But my point still stands every dev on xda who has attempted to get JIT working with the g1 has failed. All it's done is bog down the system. So you kind sir need to stop talking when you think you've felt intelligent.
Kemekill Products said:
I'm pretty sure I watched the I/0 conference and know all about it. But my point still stands every dev on xda who has attempted to get JIT working with the g1 has failed. All it's done is bog down the system. So you kind sir need to stop talking when you think you've felt intelligent.
Click to expand...
Click to collapse
You've missed the point. People were trying to wedge JIT into builds where it didn't belong, thus the problems. Froyo is built around JIT natively, so it just works.
Android 2.2 ("Froyo"), will be running on the G1 as soon as the Source Code drops.
With it being built around JIT natively, it will have noticeable speed improvements. I tested the SDK/N1 dump on my G1, and it was amazingly fast. One can only imagine how fast it is going to run once the source drops and it is actually built for the G1.
Right now, the Froyo release that is out for the G1 is working. It just has no external audio (IE: music, ringtones, notification sounds, etc). No BT, camera, wifi, etc; you know, the usual things that are broken whenever a new release comes out. Give it time, CR and enatefox will get a build done as soon as possible.
I downloaded the leaked froyo firmware to my captivate hoping it would solve a lot of the issues of lag but it still lags a lot like it's a phone from 2006. I downloaded the Ryan ZA one click lag fix and it still lags. I wanted to put voodoo on it but I have froyo and I don't think it will allow me to do it...what the heck is the problem and why is there so much hacking I have to do to get it to run smooth. The HTC Aria runs blazingly fast and quick from what I read and this Super Phone Galaxy S runs slower than a Hero? If anybody has an answer I'd like to know or if someone can offer some suggestions on how to improve this. It's pretty annoying.
crossover37 said:
I downloaded the leaked froyo firmware to my captivate hoping it would solve a lot of the issues of lag but it still lags a lot like it's a phone from 2006. I downloaded the Ryan ZA one click lag fix and it still lags. I wanted to put voodoo on it but I have froyo and I don't think it will allow me to do it...what the heck is the problem and why is there so much hacking I have to do to get it to run smooth. The HTC Aria runs blazingly fast and quick from what I read and this Super Phone Galaxy S runs slower than a Hero? If anybody has an answer I'd like to know or if someone can offer some suggestions on how to improve this. It's pretty annoying.
Click to expand...
Click to collapse
Its called RFS... call up samsung and complain to them about it...
so many problems with this
a) wrong section, Q&A or general please
b) notice that word "leaked" in what you said? it means this isn't OFFICIAL, which means it likely ISN'T the final release, so it's bound to have at least some bugs.
c) ryanza lagfix is placebo and awful and doesn't work at all (on top of that, ext2 is a bad choice)
d) if you understood how/where the lag was coming from, you'd know why voodoo is "necessary" on 2.1
e) the aria is built EXTREMELY different from the captivate, it's like comparing the iphone to the nokia n8... yes they're both android, but they're built different which leads to complications
f) voodoo is not yet available for 2.2 because we don't have source code for 2.2 (again, if you knew how voodoo worked, you'd know why it wasn't instant)... we can hack it in with initramfs, and there are people working on it... but it isn't top priority
g) and shockingly a SMALLER piece of hardware with a SMALLER resolution made by a company known for making quality android phones runs smoother? shocker. honestly.
h) if you actually had any other real world interactions with other android phones, you'd know the lag is occasional but not unusual (hell I've seen just as bad or worse on the droid x before)
i) I suggest you read, read, read, search, read, read, and think before you make posts like the above (why on earth you thought this belongs in development is beyond me)
/rant
There are two kinds of lag. I/O lag is caused by the delays in accessing data stored on your phone in some partition. This is largely due to the use of RFS by Samsung, and the voodoo lag fix gets rid of most of that. Unfortunately there is no voodoo on Captivate leaked Froyo yet, as the source code has not yet been released by Samsung. The OCLF type fixes will help some by masking this lag when the amount of data being written and read is small. When a large amount of data is involved, these fixes will lag, as they still sit on top of RFS.
There is a second kind of lag due to memory shortage. This will hit you after the phone has been on for a while. This is similar to the paging seen on Windows, where the data has to be fetched from the hard disk. This type of lag is best fixed by installing a memory management application. The one I use is called Autokiller. Despite its name, it is not a task killer. What it does is make sure that a certain amount of RAM is always free. I use the strict profile, and my phone can go days without having to be rebooted.
troll. go get an aria then^^
save a galaxy s for a person who can truly appreciate it.
by accident I posted this in the development area, I didn't realize until after the fact, my bad.
So do you think I should put my phone back to 2.1 on my phone and apply voodoo? My phone lags quite a bit, it's bad.
I'll try out that app you suggested, thanks.
..............
crossover37 said:
by accident I posted this in the development area, I didn't realize until after the fact, my bad.
So do you think I should put my phone back to 2.1 on my phone and apply voodoo? My phone lags quite a bit, it's bad.
I'll try out that app you suggested, thanks.
Click to expand...
Click to collapse
Look at the z4mod post in this forum. It works on 2.2
http://forum.xda-developers.com/showthread.php?t=811902
Kaik541 said:
f) voodoo is not yet available for 2.2 because we don't have source code for 2.2 (again, if you knew how voodoo worked, you'd know why it wasn't instant)... we can hack it in with initramfs, and there are people working on it... but it isn't top priority
/rant
Click to expand...
Click to collapse
There is a pre-release version out for froyo but I doubt it will provide more benefits than issues at this point.
cliffgardner said:
There is a pre-release version out for froyo but I doubt it will provide more benefits than issues at this point.
Click to expand...
Click to collapse
the "pre-release" version you're talking about is for the i9000... and guess what, the i9000 has source code, we do not
I had the same issue when I installed the leaked 2.2.
I did a master reset, flashed back to stock, master reset again, flashed to 2.2 cognition. Now I don't know if the second master reset was necessary, but my phone is faster than ever. Very few problems, in fact... less problem than the 2.2 leak.
Just flash to cog 2.1.6/2.1.7. I have absolutely no lag at all. Though even at stock my phone wasnt crazy laggy like your claiming your phone is.
rajendra82 said:
There is a second kind of lag due to memory shortage. This will hit you after the phone has been on for a while. This is similar to the paging seen on Windows, where the data has to be fetched from the hard disk. This type of lag is best fixed by installing a memory management application. The one I use is called Autokiller. Despite its name, it is not a task killer. What it does is make sure that a certain amount of RAM is always free. I use the strict profile, and my phone can go days without having to be rebooted.
Click to expand...
Click to collapse
Free RAM is wasted RAM.
And task killers, etc. are a great way to rape your battery life.
MikeyMike01 said:
Free RAM is wasted RAM.
And task killers, etc. are a great way to rape your battery life.
Click to expand...
Click to collapse
Autokiller is NOT a task killer. It changes the memory management profile that defines when the apps are closed. This is a combination of the amount of free RAM and the type of app and the state it is in. I also disagree that free RAM is wasted RAM. If you are trying to open a webpage and the amount of RAM is low, the system has to decide to close something else to free the space you need. If the profile of what to close is inefficient, you will frequently run into low memory situations, when the system has to continue to close some apps to free up the memory, and you will see lag as the system works it out for you. What makes you think that the profile that Samsung chose to determine when to close an app is necessarily the best one?
Can someone please tell me what exactly android 2.2 does that 2.1 can't? I'm having a lot of trouble finding features, apps, etc. that give it a distinct advantage which would make me want to switch to them. I have seen some sense ROMs on 2.1 that run every bit as fast as the 2.2 ROMs I have used (thank you Nfinitefx and Liquid!).
Thanks!
-mb
IMO they're mostly minor perks. For example, the new Gmail and Youtube apps, and in CM6.1 there is the nice Samsung Touchwiz-style connection widgets in the notification pull down. The modified music app is great, too.
To some the new, native apps2fat might be seen as a feature but it's really not.. apps2ext is better.
Here is an article that highlights the new Android 2.2 features:
http://developer.android.com/sdk/android-2.2-highlights.html
Nothing spectacular. Biggest 2 improvements in my opinion are the upgraded Browser (can handle more complex coding and has better page compatibility), and the increased speed and smoothness, an average of 2x-5x faster than 2.1 (using straight default settings/config I'm sure). This would likely be even better on our device if they could figure out how to get us the .32 or .34 kernels.
c00ller said:
IMO they're mostly minor perks. For example, the new Gmail and Youtube apps, and in CM6.1 there is the nice Samsung Touchwiz-style connection widgets in the notification pull down. The modified music app is great, too.
To some the new, native apps2fat might be seen as a feature but it's really not.. apps2ext is better.
Click to expand...
Click to collapse
chromiumleaf said:
Here is an article that highlights the new Android 2.2 features:
http://developer.android.com/sdk/android-2.2-highlights.html
Nothing spectacular. Biggest 2 improvements in my opinion are the upgraded Browser (can handle more complex coding and has better page compatibility), and the increased speed and smoothness, an average of 2x-5x faster than 2.1 (using straight default settings/config I'm sure). This would likely be even better on our device if they could figure out how to get us the .32 or .34 kernels.
Click to expand...
Click to collapse
Hey, thanks for the replies. And chromium... thanks for that link... that helped alot.
-mb
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 ?
Scoot CyanogenMod 7.1.0 RLS3
This is a build I have compiled from the official CyanogenMod source files and adapted for Kaiser/Vogue. Feel free to give it a go at your own risk!
Well, it still isn't quite as snappy as Froyo and the camera still doesn't work properly but it's probably about as fast as Gingerbread will get on our devices. I'm bound to have messed a few things up but i'll continue to work on it when I get time
All the usual things are working as far as i know, GPS works fine for me but the camera is as always not fully functional.
All of this is thanks to the guys working on the CyanogenMod roms and of course, none of this would work without all the hard work on the kernel so big thanks to dzo, vilord, l1q1d etc...
-------------------------------------------------------------------------------------
RLS 1:
Initial Release
Includes most of the Google Apps including Maps, Gmail etc..
Latest Market is included
RLS2:
Built from the latest 7.0.2 source
Optimised EGL for our devices
Updated Market
LDPI and PNG optimisations to save space & increase speed
ADW Launcher updated
Loads of tweaks and status bar changes
Updated RIL lib
Loads of fixes and optimisations
**I recommend leaving the phone for 5 minutes after installing to sort itself out and cache apps etc...**
RLS3:
I can't really be bothered to list all of the changes, there are quite a few but I just compile the thing, the changes are in the CyanogenMod repository. I have included the updated RIL and all of the Google Apps are up to date. The camera is still ****e but that's a driver issue. This release hasn't been heavily tested as I don't use my Kaiser as a main phone anymore So i'm sure you will find issues in which case we can sort them out as and when. Enjoy!
LINKS:
RLS1:
English: http://www.mediafire.com/?6708ud8kc9l9ex5
All Languages: http://www.mediafire.com/?amhd996w81xfldp
RLS2:
English: http://www.mediafire.com/?yhsc6jyl47wgpkv
All Languages: http://www.mediafire.com/?v3hhbh5tufoedfp
RLS3:
English: http://www.mediafire.com/?76vn9k0cx3debzd
All Languages: Coming soon!
Google Apps
28.04.11 : http://www.mediafire.com/?4yc9ubn2m513k3q
07.08.11 : http://www.mediafire.com/?c86rpae5kopdicc
Updates:
Vogue SD Fix : http://www.mediafire.com/?ojnj6drt3ad8mu1
Vogue Updates
Wow, thanks for all your hard work scooter. Will try right now and see how it runs.
Edit:
Vogues users have to install the SD Fix from you other thread for the SD card to work correctly.
http://www.mediafire.com/?ojnj6drt3ad8mu1
just to be clear, is this gingerbread? im just amazed at how awesome the vogue still is. i have an evo these days with cm7 but i use to have this phone. i wish i never lost it cause it would be cool to fool around with.
out of curiosity what kind of linpack scores do you get? what can you guys overclock up to?
damaph said:
Edit:
Vogues users have to install the SD Fix from you other thread for the SD card to work correctly.
http://www.mediafire.com/?ojnj6drt3ad8mu1
Click to expand...
Click to collapse
This is true, i forgot to add it, i have edited the first post with the update
hockey4life0099 said:
just to be clear, is this gingerbread?
Click to expand...
Click to collapse
It is Gingerbread indeed
I can usually overclock up to 520mhz before it starts crashing and randomly shutting down.
Though on a kaiser someone says he has gotten 576 mhz.
On a over clocked build we can get approximately 2.1 mflops.
jholtom said:
I can usually overclock up to 520mhz before it starts crashing and randomly shutting down.
Though on a kaiser someone says he has gotten 576 mhz.
On a over clocked build we can get approximately 2.1 mflops.
Click to expand...
Click to collapse
oo, is it relatively snappy? when i lost my vogue, the android development was in its baby stages so i never really got around to putting it on my device. i put it on my brothers and he loved having it. i would assume it runs froyo and gingerbread even better than it did donut. It seams like googles goal up to this point wast to streamline the os to make it quicker all around.
anyway, its hard to imagine 2 mflops when my evo is doing 36 non overclocked. im sure my phone isnt actually 18x faster than your in real use though.
yeah! I waiting for the first build to hit the shelves here. Will try soon, maybe this weekend.
hockey4life0099 said:
its hard to imagine 2 mflops when my evo is doing 36 non overclocked. im sure my phone isnt actually 18x faster than your in real use though.
Click to expand...
Click to collapse
Don't brag You'll make me want to change phones, hehe
hockey4life0099 said:
anyway, its hard to imagine 2 mflops when my evo is doing 36 non overclocked. im sure my phone isnt actually 18x faster than your in real use though.
Click to expand...
Click to collapse
its probably more than 18x faster lol
leoleotheiii said:
its probably more than 18x faster lol
Click to expand...
Click to collapse
well not in real world use. easily in raw computing power though. I used donut on my brothers vogue for a little bit and it was definitely faster than winmo.
Of course
Anything would be better than WinMo 6.1
CM 6.1 is insanely fast compared to donut when I tried them out
nice build!
enabling wifi crashes the device (polaris 100) /:
EDIT: After applying update it works!
By things like these is that I loved my HTC Vogue, hurts I had to sell it to complete the money and buy another device that placed in my signature is much more complete that our Vogue in hardware but even so the Vogue deal a place in my heart
any news if there will be an update in the near future?
Omegavirus said:
any news if there will be an update in the near future?
Click to expand...
Click to collapse
Your keen I'm running a slightly updated build at the minute, mainly experimental stuff but it's running ok for now. I'll see how things go and maybe upload a new build in a few days when i think there are enough changes to make a difference
scooter1556 said:
Your keen I'm running a slightly updated build at the minute, mainly experimental stuff but it's running ok for now. I'll see how things go and maybe upload a new build in a few days when i think there are enough changes to make a difference
Click to expand...
Click to collapse
oh, sounds good
whats improved?
What do I do with the vogue SD fix? I tried to search for it, but came up short.
Is the Vogue SD Fix specific to CM or is it for 0.32 kernels?
I thought that Scoots builds would only work with .32 kernels, and that .32 kernels didn't have USB mount for SD. Is the SD Fix fixing something else? I would really like USB mounting (with Win XP). I copy a lot of files over to my Vogue from an XP machine, but would like to use this build, but haven't moved over because I'm on .25 kernel.
Thanks.
WnG88 said:
Is the Vogue SD Fix specific to CM or is it for 0.32 kernels?
I thought that Scoots builds would only work with .32 kernels, and that .32 kernels didn't have USB mount for SD. Is the SD Fix fixing something else? I would really like USB mounting (with Win XP). I copy a lot of files over to my Vogue from an XP machine, but would like to use this build, but haven't moved over because I'm on .25 kernel.
Click to expand...
Click to collapse
I wouldn't recommend using this with the .25 kernel, it's too old. The Vogue SD Fix allows the SD card to mount and enables apps to SD for Vogue. It's because the Kaiser and Vogue differ in this area. As always with the .32 kernel, i have not had success mounting in windows from the phone, linux is fine though.
wow ginger on the vogue. now that's amazing. htc should make another version of this phone but with android on it.