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.
Just want to see what everyone's take is with the battery life issues, etc
[highlight]Mod Edit: trolling and flaming are not allowed on XDA grounds. Consider this a friendly warning[/highlight]
If you guys seriously consider that either trolling or flaming, then your standards for such really are lackluster.
For the sake of the thread though, I went back to MCR r15. Runs amazing, and have much faster up and dl speeds. Paul said he will be releasing a ROM based on this soon anyway, so I can wait. FroYo was amazing though. Only real reason I went back was because of a wifi issue, LOL. Turns out it was just an IP address conflict. I reset the IP of my laptop and solved it, but only AFTER I'd reverted. Too lazy to go back again.
dictionary said:
If you guys seriously consider that either trolling or flaming, then your standards for such really are lackluster.
For the sake of the thread though, I went back to MCR r15. Runs amazing, and have much faster up and dl speeds. Paul said he will be releasing a ROM based on this soon anyway, so I can wait. FroYo was amazing though. Only real reason I went back was because of a wifi issue, LOL. Turns out it was just an IP address conflict. I reset the IP of my laptop and solved it, but only AFTER I'd reverted. Too lazy to go back again.
Click to expand...
Click to collapse
Why MCR R15 over CM 5.0.7.1?
hah2110 said:
Just want to see what everyone's take is with the battery life issues, etc
Click to expand...
Click to collapse
I have great battery life with FroYo, running stock FroYo kernel, and all... I do have a few small bugs that were clear signs to me it was unofficial to begin with, and am excited for the official release to see if it polishes out those few minor issues.
All in all, though, 99.9% of if works perfect. Super fast, great battery life, and so forth. Radio seems to be about the same as all the others, I get good 3G when I have it, good EDGE when I am on that. I still say I get better reception than my G1 did, but that is just me and my testing at my Dad's house (death hole for cell phone coverage) and my basement (it is where my "man dungeon" is located). Beyond that, I always get good coverage no matter the phone, so it has been a moot point to me... speed wise, I always edit my GPRS and HSDPA to 12 and 2.
hah2110 said:
Why MCR R15 over CM 5.0.7.1?
Click to expand...
Click to collapse
Why CM over MCR? Or Enom over CM? and so forth... personal preference is the likely answer. I like MCR since I have a pay account over there and can use his kitchens, thus making a ROM that is lighter. I like Enom because it is rock solid, fast, and great battery life (1.8.1 is best IMHO). I like CM because it is bleeding edge, fast, and while has its moments of instability, is still the gold standard for a full feature custom ROM, especially with all the extras pre-baked in. Desire has only 1 real option, Modaco.
And I like FroYo the most because it is new, super duper fast, good battery life, and I like frozen yogurt.
hah2110 said:
Why MCR R15 over CM 5.0.7.1?
Click to expand...
Click to collapse
MCR r15 for me runs soooo much smoother. I love CyanogenMod, as my sign indicates. LOL. After trying out r15 though I was hooked.
The poll options seem to indicate a dislike of Froyo. Even the positive options imply that by using it you are putting up with tons of bugs or something. Are people really having trouble with Froyo?
It's been working well for me. My battery life has been worse but I thought it was just because I had turned Latitude back on about the same time I upgraded to Froyo.
hexix said:
The poll options seem to indicate a dislike of Froyo. Even the positive options imply that by using it you are putting up with tons of bugs or something. Are people really having trouble with Froyo?
It's been working well for me. My battery life has been worse but I thought it was just because I had turned Latitude back on about the same time I upgraded to Froyo.
Click to expand...
Click to collapse
I LOVE FroYo but can't tolerate the battery consumption. Sorry if it came off bias
I love FroYo and I want to keep it but... I have some problems that I can't live with.
1. Reboot phone, resets widgets and some installed programs on SD
2. Double messaging notifications (stock messaging app conflict with other apps, even if I disable notifications)
3. Miss the tweaks and stuff from CM
Still using it but urging to switch back until custom roms are out.
Not only am I keeping Froyo, I'm being FORCED to use my TMobile Nexus(2.2) instead of my ATT Nexus(2.1) because Froyo makes 2.1 feel like a slow crappy beta.
I cannot even get voice plus data at the same time with my TMobile Nexus, yet I use it because, imo, Froyo is that much better.
Going back to my 2.1 Nexus feels like a pre launch beta device that I yell at because it's so damn laggy compared to Froyo, which is fast as a bullet.
Please Google give us 2.2 so I can go back to my freaking ATT Nexus!
wish I could have two nexus ones, LOL.
Overall I loved FroYo, and had I realized the IP conflict before switching back to MCR r15, I would still be on it.
Well, I just solved two of my problems, it's not so bad now. Going to stick with it
dictionary said:
wish I could have two nexus ones, LOL.
Click to expand...
Click to collapse
if I'd known the ATT version was going to follow so closely behind the Tmobile version, I would only have one as well. I just couldn't wait. I keep the Tmobile Nexus rather than sell it because if anything were to ever happen to my ATT Nexus, my GF will NEVER let me buy a third one. I've used up my smartphone quota for quite awhile
People get too caught up in the other ROMS when in all reality Froyo briings everything they need via a stock ROM but some folks would rather run Cyano or Modaco just to say they have have a custom ROM. In all reality if you install Froyo after a clean wipe the only real bug you will encounter is with some marketplace apps not showing up. A small price to pay considering they will eventually show up and life will be back to normal. The majority of ppl complaining about other bugs are folks who flashed froyo over a cyano or modaco etc.. rom and of course they are going to have problems as this update was obviously not tested with cyano or modaco as a base rom for obvious reasons. I'd say a good 90% plus of the problems some are experiencing are due to this and the rest of us are loving Froyo to death. I'm happy with it and anxiously awaiting the official release so I can reinstall those market apps that are missing as that's the only real bug I am encountering after a clean install of Froyo.
For everyday use I feel Froyo is definitely slower than CM5.0.7 with pershoot's latest kernel. I used CM's quick rooter with Froyo so I was also OC'd for a fair comparison. I'm still going to keep using Froyo because it's fun seeing optimizations and themes etc slowly tickle out for the new Android build.
bluehaze said:
People get too caught up in the other ROMS when in all reality Froyo briings everything they need via a stock ROM but some folks would rather run Cyano or Modaco just to say they have have a custom ROM. In all reality if you install Froyo after a clean wipe the only real bug you will encounter is with some marketplace apps not showing up. A small price to pay considering they will eventually show up and life will be back to normal. The majority of ppl complaining about other bugs are folks who flashed froyo over a cyano or modaco etc.. rom and of course they are going to have problems as this update was obviously not tested with cyano or modaco as a base rom for obvious reasons. I'd say a good 90% plus of the problems some are experiencing are due to this and the rest of us are loving Froyo to death. I'm happy with it and anxiously awaiting the official release so I can reinstall those market apps that are missing as that's the only real bug I am encountering after a clean install of Froyo.
Click to expand...
Click to collapse
I agree, to a degree, but there is no way most people are just caught up in the hype of a ROM. The assumption and assertion that custom ROMs are pointless is unjustified, and bias to your needs. I find the the enhancements custom ROMs bring can drastically alter my user experience in many ways. For example, MCR r15 runs circles around my stock ROM, in terms of speed, performance with games, battery life, etc. Prior to FroYo, these ROMs added the wifi/wired tethering, lower capacitive button fix (thanks kmobs), better battery life, smaller file sizes for installed system, homescreen rotation (which FroYo still doesn't do), trackball colors, and various other small tidbits. Now that FroYo is out (I wonder how much of what's in FroYo only came about due to the Dev community putting it out there, and Google taking notice.. hmm), I can only imagine what the Devs will cook up to enhance it even further.
Looking forward to the future Cyano ROMS based on Froyo no doubt but at this point in time Froyo brings everything I ever rooted for and gives me better battery life to boot. The dev community certainly had some influence in the features we see today in Froyo and for that I am thankful, don't mean to sound like i'm coming down on the devs. I just don't see much point in running anything other than Froyo right now but will consider it once I see what the devs can add to it.
bluehaze said:
...
I just don't see much point in running anything other than Froyo right now but will consider it once I see what the devs can add to it.
Click to expand...
Click to collapse
Well, if you want a good example - I want the option to have sd-ext partition (custom, pre-Froyo Apps2SD). Firstly because many apps I have currently don't support moving to SD - and I'm "overbooked" by at least 50MB that I have to offload to SD card to have some space left on the device, and also because I like the ability to mound SD card without loosing access to applications.
I also hate it that I don't have direct access to hidden system menus, and even for changing the browser user agent I need to write "about:debug".
Those things keep me with CM5.0.7.1 until better times.
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 ?
Ok, so from my reading, I've gathered that there are different kernels which are configured differently for different purposes. I've also read that there are different ROMs.
From what I've read, Android build (eg Eclair or Froyo) is changed by installing ROMs, not kernels.
So, I want to upgrade to Froyo because its iptables are updated for Wifi Tethering. However, I actually like most of the Samsung setup as is, and would like to keep the home screen as is with the four softbuttons (Phone, Email, Browser, Applications) along the bottom and the same basic home layout. I can't seem to find a ROM that has that though. Most have Launcher Pro on them. Why so? Is there a real big advantage to this?
I know, this is a lot of reading lol, so thanks for bearing with me.
In short:
-Samsung's UI or Launcher UI
-What's closest to stock but with Froyo instead of Eclair
Those are my primary concerns lol
Thanks
Regards
Smith
Well, there is advantages to using alternative launchers. More customizable, cleaner, less intrusive. Closest froyo to stock is obviously JI6, which is the leak that started it all for us.
As for the default launcher, there is a customizable version of the TW launcher compliments of gtg465x, check it out here.
geokhentix said:
Well, there is advantages to using alternative launchers. More customizable, cleaner, less intrusive. Closest froyo to stock is obviously JI6, which is the leak that started it all for us.
As for the default launcher, there is a customizable version of the TW launcher compliments of gtg465x, check it out here.
Click to expand...
Click to collapse
Awesome, that link and quick response basically answered my entire, long paragraph haha thank you!
Regards, and happy new year!
Smith
Why dont you download Launcher Pro now and check it out, you can put whatever 4 buttons on the bottom as you wish, it works much better than touchwiz.
When you change to froyo it wont be the same as far as the factory homescreen so just try out launcher pro now and see if u could deal with the change
One last concern. I've seen a lot of issues with custom ROMs like the bottom lights for the buttons not working, GPS being messed up, etc. Are those a real concern?
Is there anyway to upgrade to froyo without flashing a custom ROM?
Negative. Froyo IS a form of rom. The method that worked best for me was to install the froyo leak through odin...and then pull the kernel out of DG'S cognition 2.3b8 and swap it into my phone using neldars sgs kernel flasher. the reason for the kernel swap was to incorporate the voodoo lagfix which is by far the most stable and effective program of its kind. Eliminates most system lag. Theres still a minor lag when going to home screen sometimes....(2 seconds) for all the apps to pop up....but it makes navigating the phone and launching apps a LOT faster. It also improves your quadrant (if you care) to 1500's...and your linpack (again if you care) to 14 mflops
topiratiko said:
Negative. Froyo IS a form of rom. The method that worked best for me was to install the froyo leak through odin...and then pull the kernel out of DG'S cognition 2.3b8 and swap it into my phone using neldars sgs kernel flasher. the reason for the kernel swap was to incorporate the voodoo lagfix which is by far the most stable and effective program of its kind. Eliminates most system lag. Theres still a minor lag when going to home screen sometimes....(2 seconds) for all the apps to pop up....but it makes navigating the phone and launching apps a LOT faster. It also improves your quadrant (if you care) to 1500's...and your linpack (again if you care) to 14 mflops
Click to expand...
Click to collapse
I don't know what quadrant or linpack means lol could you explain briefly?
Ok, I'll try a different kernel for speed, the one I have now is... meh at best lol.
Regards
Smith
quadrant and linpack are benchmark tests obtained from the market that guage device speed/efficiency. Stock speeds on eclair are 800 ish quadrant and 8ish mflops.....froyo is a big boost....but beware....installing froyo has one known issue....bluetooth is comprimised.....although i havent tried it after the kernel swap
topiratiko said:
quadrant and linpack are benchmark tests obtained from the market that guage device speed/efficiency. Stock speeds on eclair are 800 ish quadrant and 8ish mflops.....froyo is a big boost....but beware....installing froyo has one known issue....bluetooth is comprimised.....although i havent tried it after the kernel swap
Click to expand...
Click to collapse
Great thanks, that's good info!
Alright, that's fine. I don't use bluetooth a whole lot. I'm still messin around with ROMs right now, I don't even have one I'm in love with yet lol. But hell, coming from WinMo, I love ALL of these comparatively haha
I've been using froyo ROMs on my phone (cognition and axura) for the past few months have had zero problems with Bluetooth.
Transferring files works as does streaming audio and headset functionality and headset controls.
Sent from my SAMSUNG-SGH-I897 using XDA App
cognition and axura are custom builds with modifications....bluetooth is "fixed" on those.....I was talking about the leaked rom itself that came out in early october. Bluetooth on that is a disaster
Came across a funny older article on a fruit based website about the nook color when it first came out. After reading it i couldnt help but chuckle.
This was the best part of it,
But unlike forthcoming Android tablets like the Samsung Galaxy Tab, this device is going to be locked down and will only be able to run a limited number of B&N-approved apps such as Pandora and Lonely Planet.
Click to expand...
Click to collapse
lol
Its a good read for a laugh.
I know that my nook color countinues to amaze me with more and more functionality everyday.
Its amazing what xda devs can accomplish. Take something and make it do something it was never meant to do and do it better than its competition.
That article is an unfortunate example of what a lot of tech journalists are doing these days. Hastily research a new product, then clip together a bunch of other coverage and bang out an article. By demonstrating his technical incompetence, sure he's got egg on his face now after the fact, however he also represents a large (the majority) percentage of B&N's customer base. The average purchaser would says "rooting what now?".
Amazingly, the NC has proven wildly popular and B&N's top selling item EVER, so obviously even with the limitations the author describes it's trouncing the competition. For those of use who know about ADB and scripts/img files, hey it's even better. Bought one for myself, then for my Dad (50's, tech savvy still). I rooted it, installed xeam and some apps then wrapped it back up and bang, best Christmas present ever!)
I've had a book 3g and then the NC which i rooted. Bottom line it rocks!!!!
Sent from my NOOTED NC using XDA App
I cannot wait for a fully functional froyo rom for the internal memory that will make this a true tablet
Sent from my DROIDX using Tapatalk
sp1kez said:
I cannot wait for a fully functional froyo rom for the internal memory that will make this a true tablet
Sent from my DROIDX using Tapatalk
Click to expand...
Click to collapse
Forgot Froyo. Gingerbread CM7. It's going to be B-E-A-UTIFUL
nicbennett said:
Forgot Froyo. Gingerbread CM7. It's going to be B-E-A-UTIFUL
Click to expand...
Click to collapse
Name 5 things that Gingerbread does better than Froyo....
Anywho, I too look forward to a tablet-friendly custom ROM.. I still really like the status bar on the bottom of the screen, but the stupid B&N shortcut thing gets on my nerves when I'm typing.
khaytsus said:
Name 5 things that Gingerbread does better than Froyo....
Anywho, I too look forward to a tablet-friendly custom ROM.. I still really like the status bar on the bottom of the screen, but the stupid B&N shortcut thing gets on my nerves when I'm typing.
Click to expand...
Click to collapse
You mean aside from the better Dalvik VM, better battery management, improved UI, improved hardware capabilities (improved camera handling, gyroscope, NFC), improved game API, improved audio API, new media (audio/video) support, and a new linux base kernel? I guess if you don't count those, you still have the new/updated core libraries, updated bluetooth stack, improved text selection, built-in VOIP, and of course, the better keyboard...
Seriously, i mean, really seriously, why would ANYONE have anything against getting the NEWEST OS? All our efforts should be on gingerbread, since it offers the most compared to Froyo. Its not like moving to GB has any shortcomings, so why NOT want it?
I just got my nook color last night - I've found BBuy that had it in stock about 50 miles and drove there - sure enough about 20 were on the shelve - forgot to mention I traveled actually from one state to another (about 50 miles) to get it right of the shelve ... so anyhow, I am happy with "locked" nook color has to offer - I am even more thrilled about rooting it soon and unlocking the full potential. NC here I come
Yeah, a lot of the reviews bemoaned its alleged "doesn't know what it is" status. I've rooted mine, OC'd it, isntalled dozens of apps and games. Yet I still use it primarily to read novels, and do some light web browsing. And for that, it's dead perfect.
In other words, even an unrooted NC is an outstanding gizmo. I mean that screen is just to die for.
I definitely love my Nook. People are always surprised when I tell them it was only $250. Froyo on teh emmc via dd ftw! It's much better than the stock OS.
rjsmith2007 said:
I definitely love my Nook. People are always surprised when I tell them it was only $250. Froyo on teh emmc via dd ftw! It's much better than the stock OS.
Click to expand...
Click to collapse
IN regards to emmc Froyo - what about the lag? I guess it may just be my SD card, but every Froyo build i have tried, has been painfully laggy - not slow, but things like gmail can take 1-2 minutes to actually show the mail. The app drawer animations are also oddly slow. Does emmc really make Froyo more usable for you?
Divine_Madcat said:
IN regards to emmc Froyo - what about the lag? I guess it may just be my SD card, but every Froyo build i have tried, has been painfully laggy - not slow, but things like gmail can take 1-2 minutes to actually show the mail. The app drawer animations are also oddly slow. Does emmc really make Froyo more usable for you?
Click to expand...
Click to collapse
Oh GOD yes. There is no lag on eMMC. Typing this comment to you on my Froyo'd NC right now
Divine_Madcat said:
You mean aside from the better Dalvik VM, better battery management, improved UI, improved hardware capabilities (improved camera handling, gyroscope, NFC), improved game API, improved audio API, new media (audio/video) support, and a new linux base kernel? I guess if you don't count those, you still have the new/updated core libraries, updated bluetooth stack, improved text selection, built-in VOIP, and of course, the better keyboard...
Seriously, i mean, really seriously, why would ANYONE have anything against getting the NEWEST OS? All our efforts should be on gingerbread, since it offers the most compared to Froyo. Its not like moving to GB has any shortcomings, so why NOT want it?
Click to expand...
Click to collapse
No, I agree that Gingerbread has small incremental improvements, but nothing that'd cause me to say screw Froyo, wait for Gingerbread. Especially if Gingerbread on the NC is well off.
khaytsus said:
No, I agree that Gingerbread has small incremental improvements, but nothing that'd cause me to say screw Froyo, wait for Gingerbread. Especially if Gingerbread on the NC is well off.
Click to expand...
Click to collapse
I guess what i am thinking - given that Gingerbread is already being worked on, and our Froyo build doesn't actually work that well, why not just move ALL the resources out there to GB, and the most recent right away. Why go incrementally?
Divine_Madcat said:
I guess what i am thinking - given that Gingerbread is already being worked on, and our Froyo build doesn't actually work that well, why not just move ALL the resources out there to GB, and the most recent right away. Why go incrementally?
Click to expand...
Click to collapse
I'd agree with that.. If the effort is the same for both, go with Gingerbread. However so far we have Nookie Froyo which is "mostly" there and I haven't heard of Gingerbread on the NC at all.
Just to add how amazing this gadget is I'm typing this comment using SlideIT and it has taken mea fraction of what it used to.
Sent from my rooted Nook Color
khaytsus said:
I'd agree with that.. If the effort is the same for both, go with Gingerbread. However so far we have Nookie Froyo which is "mostly" there and I haven't heard of Gingerbread on the NC at all.
Click to expand...
Click to collapse
WEll, there is a gingerbread branch that is being worked on here: https://github.com/fat-tire/android_device_bn_encore
And there is plenty of talk that CM7 is on its way (though, i admit that i still fall into the see it to believe it camp). http://forum.cyanogenmod.com/topic/11127-nook-color/page__st__40
But regardless, the froyo build really isn't that usable - its laggy, market is like sludge, etc. I really think that the devs working on it, should take the froyo lessons, and focus totally on GB. Let froyo be the sandbox for others to learn on, and let GB be the first real OS upgrade for the NC.