Database Develop

FroYo for Vogue, any plans?

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.

[Q] Froyo 2.2... Help me understand.

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

DFT TEAM has Android working on Nand PRO2

DFT team has released a video of Android running on nand pro2
RHO's CPU is too slow and screen resolution too high for sense, so we decide to make pure Android ROM based on Android 2.2
youtube.com/watch?v=yOGnQ3D5IDk

wow
hey , sound good,
i hope working an topaz,too
i think they both phones have similar technical data.
i dont understand why cpu is to slow, lenin reds built with sense
run much more faster from sdcard than this nand built ????
btw good work from the DFT Team , thx

hello there. let's hope topaz, aka touch diamond2, wont be forgotten.
I'll be willing to pay for good working rom

sounds promising
waiting for more updates

Hopefully it will be working on our phones as well.
BTW, one of the comments said to be using Neopeek's android roms. Can someone post a link, I must have missed them.

loadstone007 said:
Hopefully it will be working on our phones as well.
BTW, one of the comments said to be using Neopeek's android roms. Can someone post a link, I must have missed them.
Click to expand...
Click to collapse
Click here. Anyway its a little bit outdated but try it and be sure to update kernel, rootfs,...

ReWind402 said:
Click here. Anyway its a little bit outdated but try it and be sure to update kernel, rootfs,...
Click to expand...
Click to collapse
Thanks!
It's indeed outdated, perhaps I should just wait.

thijsdgier said:
RHO's CPU is too slow and screen resolution too high for sense, so we decide to make pure Android ROM based on Android 2.2
Click to expand...
Click to collapse
Well, i don't know if this will be the same decision for topaz. But if yes then it's a bad bad info for me
I just hate pure android and sense in android rocks!!
I also don't understand this because i have lenin build and it's fasttt from sdcard!!!
Shouldn't be even faster from nand??
Anyway thanks for all who make this possible even if it no feet my needs!!
Thank you

Zimaia said:
Shouldn't be even faster from nand??
Click to expand...
Click to collapse
AFAIK nand is not faster than sd-method. But it would allow you too get rid off winmo.

actually guys, your phone won't improve that much after NAND. believe me i'm hd2 user and i have used android since first versions based off xdandroid..
as far as speed goes, read/write is actually faster on sdcard!
only andvantage of nand is stability and power consumption, ofcourse after all quirks are polished.
qc's 528 msm's are too slow to run sense well. it can get slow even on 1ghz. wvga is too much to handle, and sense is very ram sensitive! maybe if someone could get it upscaled from hvga, but in that case it would be streched..
i also own both diamonds(I and II) and i would love to see winmo gone. but on good port like leo(feels like native device) we had advantage of few devices with same components built in and much work being already done, and i do not see wvga android with small screen and 528mhz released by htc.
i'm just being realistic here, not mean or anything else.

1 - Topaz is very small mobile phone. I am don't wants to use such big phone like HD2.
2 - Battary life in topaz is more longer
3 - It have smaler screan and that is why it is more clear.

Airpil said:
1 - Topaz is very small mobile phone. I am don't wants to use such big phone like HD2.
2 - Battary life in topaz is more longer
3 - It have smaler screan and that is why it is more clear.
Click to expand...
Click to collapse
you misunderstood my post, i'm just tryin to say how thing are and hd2 was best example i could think of. i like my diamonds very much. first gen was really awesome on looks, but low on hardware(slow and small ram..etc).
i wish there will be some goodies from dft soon

stirkac said:
actually guys, your phone won't improve that much after NAND. believe me i'm hd2 user and i have used android since first versions based off xdandroid..
as far as speed goes, read/write is actually faster on sdcard!
only andvantage of nand is stability and power consumption, ofcourse after all quirks are polished.
qc's 528 msm's are too slow to run sense well. it can get slow even on 1ghz. wvga is too much to handle, and sense is very ram sensitive! maybe if someone could get it upscaled from hvga, but in that case it would be streched..
i also own both diamonds(I and II) and i would love to see winmo gone. but on good port like leo(feels like native device) we had advantage of few devices with same components built in and much work being already done, and i do not see wvga android with small screen and 528mhz released by htc.
i'm just being realistic here, not mean or anything else.
Click to expand...
Click to collapse
quited d2 and joined moto defy~~~

What happened to this project??? I didn't see MAGLDR

Black.Heart said:
What happened to this project??? I didn't see MAGLDR
Click to expand...
Click to collapse
It was closed-source, and I don't believe they ever made a public release. Since none of the code is available to the public, no other dev can pickup where they left off...
Crappy model to go with. Were still pushing forward with NAND using open source concepts, and RHOD is getting there (just very slowly). I'm hoping each device will have at least one dev that will step up and get the dirty work done to look towards NAND on all devices... but that hasn't happened yet. There's not even that much (developer) steam behind NAND on RHOD...

arrrghhh said:
It was closed-source, and I don't believe they ever made a public release. Since none of the code is available to the public, no other dev can pickup where they left off...
Crappy model to go with. Were still pushing forward with NAND using open source concepts, and RHOD is getting there (just very slowly). I'm hoping each device will have at least one dev that will step up and get the dirty work done to look towards NAND on all devices... but that hasn't happened yet. There's not even that much (developer) steam behind NAND on RHOD...
Click to expand...
Click to collapse
I am very much upset with that you are right!

The Honeycomb Conundrum

Let me preface this by saying that I have nothing but the utmost respect for the dev community (NC and otherwise) and I really don't mean to step on any toes with this. I'm fairly new at all this and I've got some questions.
Alright, so as we've all heard by now, Google (whether their reasons are benevolent or not) are withholding the AOSP release of Honeycomb and that kind of rains on everyone's nook color parade. We've got a mostly working port of HC that kind of sags in the performance area. Its almost been enough to make me flash Gingerbread but there are a few things - namely the browser, email app, soft keys and notification system - that I'd miss. The new + screen is nice, but I've been using launcher pro as it runs seemingly faster than the stock launcher, so I'm already missing out on that.
Now, from what I understand, and feel free to correct me if I'm wrong, deeperblue's HC port uses parts of Gingerbread to make everything all hunky dory.
My question is this; would a viable solution to slow HC performance be to make a new rom and pump MORE Gingerbread in? i.e. Take HC's notification system replace GB's phone-style notification pane. Make it mostly gingerbread with some tablet friendly nip/tucks here and there.
I realize there are things like softkeys and the bottom taskbar mod, but HC's handling of the android buttons and the new notification system is just so appealing. Its making the choice of which rom to run unduly difficult. And while I can't cook a rom, I'm hoping someone who can sees this and runs with it, if it is feasible, that is.

Truthfully... It's up in the air like everything else, unless a DEV directly comes out of the shadows and saids, hey i'm going to do it... Then we just won't know. Honestly, I'm sad that we won't see HC right around the corner, but CM7 is pretty awesome. And the Xoom is scheduled to drop down to $599 (Wifi only) today, making it a lot more competitive than the 3g.
That's not to say that I personally have $599 to drop and go buy a new tablet, but it does mean that you'll probably see them on craigslist or ebay in a few months for a bit cheaper. =\

The honey comb preview is awsome but to many apps don't work.

Tyfighter said:
My question is this; would a viable solution to slow HC performance be to make a new rom and pump MORE Gingerbread in?
Click to expand...
Click to collapse
That was kinda the plan. CM7 development was going in a way that all the improvements (Bluetooth, partially working DSP, an accelerated interface) were going to be directly ported to Honeycomb once the source released. But without the source, that can't happen.
Basically Google has completely screwed any Nook Color fans wanting Honeycomb.
The only improvement that can be made is that a ROM could be made from the final SDK. That would be just as laggy, and will lack new features (Bluetooth, DSP, etc.), but it would be able to use Android tablet apps.
From the conversation about Google's move on the net, many are saying there won't be a Honeycomb source at all, and the next source dump will come with Ice Cream months from now.
So Honeycomb fans have a choice- either try out the CM7 modification that you talked about to make CM7 more Honeycomb-like, or start saving up for that Xoom...

[email protected] said:
The honey comb preview is awsome but to many apps don't work.
Click to expand...
Click to collapse
what apps dont work? most of the major ones have worked for me so far...
im finding that the hc rom is very usable for a daily driver...although bluetooth and dsp support would be very nice...

nolook said:
what apps dont work? most of the major ones have worked for me so far...
Click to expand...
Click to collapse
Any Tablet app that requires the final SDK version (aka all those Xoom apps) won't work on our preview build.

poofyhairguy said:
Any Tablet app that requires the final SDK version (aka all those Xoom apps) won't work on our preview build.
Click to expand...
Click to collapse
Thank you for your informative reply.
It seems now that my best bet is going to be t see what the cm7 guys cook up. Hopefully this aosp business will spark some of the innovation that the android community is known for. I'd love to help, but its not exactly my forte
With regards to what apps aren't working, my marketplace only seems to intall apps when the stars are right. I often have to attempt an install upwards of five times to have it succeed, if it even does. Otherwise i get insufficient storage errors or indeterminate error 18

sorry if i am hijacking this a bit, but i had thought that android was 'open source'. why the change in the plans to not release hc? is this to protect the hw manufacturers like mot who have hc on the xoom, and freeze out users who want it ported non supported platforms? Otherwise, I can't understand the logic.
I got the nc cause i had thought it had the best $/performance of any android based tablet. For half the price of others, it had great screen, and forgetting bt, etc., nice hw specs. With hc, it would be fantastic!
How else to counter ipads if not to get hc on as many tablets as possible?

I wonder if the fact that the playbook is running our apps has anything to do with it. If so, I don't mind anything that makes it rough for RIM.
Sent from my Desire HD using XDA App

jbinbi said:
sorry if i am hijacking this a bit, but i had thought that android was 'open source'. why the change in the plans to not release hc? is this to protect the hw manufacturers like mot who have hc on the xoom, and freeze out users who want it ported non supported platforms? Otherwise, I can't understand the logic.
Click to expand...
Click to collapse
It is open source and it WILL be released however at this time they don't think it's ready for final release (I've heard of various tweaks they need to make in the xoom) and are working those out prior to releasing it to devs

To-Do List For our device :)

Before any of you say anything negative this isnt to bug other devs this is a thread for people to request/ ask for things me and the other devs to do after they have finished their other projects.
-Firefox OS
-LG UI(fix lockscreen)
-CM7
-Sense 4.1
-cm10.1 WiFi and Bluetooth
-cm10 WiFi authentication issue
-S-OFF
-Roms for cdma version
-Sense 4.1.2
Just pop requests underneath and ill update reguarly.

Shad0wPanda said:
Before any of you say anything negative this isnt to bug other devs this is a thread for people to request/ ask for things me and the other devs to do after they have finished their other projects.
-Firefox OS
-LG UI
-CM7
Just pop requests underneath and ill update reguarly.
Click to expand...
Click to collapse
Sense 4.1 (If possible)

Shad0wPanda said:
Before any of you say anything negative this isnt to bug other devs this is a thread for people to request/ ask for things me and the other devs to do after they have finished their other projects.
-Firefox OS
-LG UI
-CM7
Just pop requests underneath and ill update reguarly.
Click to expand...
Click to collapse
Hahaha, heres an LG UI Rom, iv'e had it for a while, just lockscreen doesnt work at all! so slide down NC and hit settings to unlock, then install a custom locker such as holo locker! I'll post in the dev threads when i can be bothered, but test that out..
http://d-h.st/2V2
Click to expand...
Click to collapse

i think gettin bt and wifi implemented in cm 10.1 should be a good place to begin

lead3r1 said:
i think gettin bt and wifi implemented in cm 10.1 should be a good place to begin
Click to expand...
Click to collapse
+1
but we really need the devs to go back to work

CM7 FTW
CM7 first ... it would be super buttery smooth for us ...

How are you so certain it'd be "buttery smooth"? Cuz I'm not sure, if not totally negative on that matter.

How are you so certain it'd be "buttery smooth"? Cuz I'm not sure, if not totally negative on that matter.
Click to expand...
Click to collapse
Brnt you don't have to flash cm7... What's with all the gingerbread hate??
Sent from my HTC Desire C using xda app-developers app

I suggest we go back to XP then. It's going to run so much better on our new PCs!
It's not hate, you just get overexcited over nothing without even putting some though into it. Go on, prove me gingerbread will run smoother than JB/ICS, but without these facts your words are nothing.

brnt said:
I suggest we go back to XP then. It's going to run so much better on our new PCs!
It's not hate, you just get overexcited over nothing without even putting some though into it. Go on, prove me gingerbread will run smoother than JB/ICS, but without these facts your words are nothing.
Click to expand...
Click to collapse
I think you have your analogy wrong. Going from a newer version of Windows to an older version of Windows is pointless because...well...it's still Windows.
However, if you were to go from Ubuntu to, say, Slackware, you would definitely see a boost in performance because Slackware is far less taxing on the available resources. The same could be said about going from JB to GB. GB requires less resources and can therefore run smoother/faster on hardware designed for a higher version of Android. This is a well known fact throughout the Android community because nearly every JB or ICS based device has GB ROM development in some form or another.
It's still Android. Roughly 90% of the differences between JB/ICS and GB lie in the overall appearence, not the functionality.

IDEA
Or lets make CM10 even better
Like eliminate WiFi problems and hotspot problems etc :fingers-crossed:
What do you think?

S off would be good.
Not first priority though
sent from CM10'd Desire C

Phenziox said:
S off would be good.
Not first priority though
sent from CM10'd Desire C
Click to expand...
Click to collapse
It would be very useful though but it's more HTCs job
Sent from my HTC Desire C using xda premium

@soupmagnet, i agree entirely with that statement, however, where is the desire coming from for having GingerBread Roms? if it was desired so much, then why not buy a gingerbread phone in the first place? Would've been cheaper and there are still devices on the market, some with faster processors then the Desire C, if you wanted GingerBread, should've bought a GB Device, you don't go buy a brand new Windows 8 PC to deliberately downgrade it to a legacy OS like vista and limit the features you have access to. It lacks all logic in all honesty.. You don't go to sell a phone after use being all like, Yeah it has 2.3.5 GB on it, or brag to your mates, yeah my device is android 2.3.5, fact is 4.2.2 is the best android so far, Android has only improved over time, GB on our device is like an i7 with vista, you just don't do that kind of thing..

penguin449 said:
@soupmagnet, i agree entirely with that statement, however, where is the desire coming from for having GingerBread Roms? if it was desired so much, then why not buy a gingerbread phone in the first place? Would've been cheaper and there are still devices on the market, some with faster processors then the Desire C, if you wanted GingerBread, should've bought a GB Device, you don't go buy a brand new Windows 8 PC to deliberately downgrade it to a legacy OS like vista and limit the features you have access to. It lacks all logic in all honesty.. You don't go to sell a phone after use being all like, Yeah it has 2.3.5 GB on it, or brag to your mates, yeah my device is android 2.3.5, fact is 4.2.2 is the best android so far, Android has only improved over time, GB on our device is like an i7 with vista, you just don't do that kind of thing..
Click to expand...
Click to collapse
The problem with your logic is that Gingerbread based devices (with a few exceptions) only have hardware that is capable of meeting the low demands of Gingerbread.
For many people, the worth of their device is in its functionality, not its "bragging rights". I will never have Windows on my computer simply because of the features it provides. I use Linux, because of it's speed, stability and and overall functionality. ICS and JB do have some nice additional features, but at a noticeable cost of available resources and stability, and the overall functionality is still nearly the same. While higher versions of Android do provide some "improvements", they are mostly linked to the user interface (which many people don't necessarily like) and there are very few performance improvements. So for you to say that it "lacks all logic" is, well, illogical in itself.
While you may like what JB and ICS have to offer and prefer that for your daily driver, I don't think it's fair to ridicule others' personal preference in Android versions, considering the majority of changes between these versions are exclusive to the UI and not Android itself.

Off-topic... naughty naughty
Sent from my HTC Desire C using xda premium

Getting back on topic...
It would be nice to see more CDMA support though. I have a shell script, based on bin4ry's exploit, to root the CDMA variants, but it needs to be converted over to Windows' batch scripting language. If anyone wants to have a go at it, just let me know.
As far as ROMs are concerned, we can use the existing GSM ROMs, but a patch will need to be made. It wouldn't be that difficult to implement and would be much easier than creating all new CDMA ROMs.
The biggest problem would be getting a working recovery. I tried unpacking the existing (GSM) recovery and replaced the kernel with the phone's stock kernel but it didn't work out very well. I think a new recovery would need to be built from source, but I'm running into strange compile errors when compiling the stock kernel from source. I don't have experience building custom recovery so it's going to be challenging trying to figure everything out, but I think I can handle it.
Clearly, the need for CDMA support is low, but it's far from non-existent. I'm more than willing to take the reigns on this project, but I may have to take advantage of some of the experience around here, assuming there are those willing to lend a hand.

soupmagnet said:
The problem with your logic is that Gingerbread based devices (with a few exceptions) only have hardware that is capable of meeting the low demands of Gingerbread.
For many people, the worth of their device is in its functionality, not its "bragging rights". I will never have Windows on my computer simply because of the features it provides. I use Linux, because of it's speed, stability and and overall functionality. ICS and JB do have some nice additional features, but at a noticeable cost of available resources and stability, and the overall functionality is still nearly the same. While higher versions of Android do provide some "improvements", they are mostly linked to the user interface (which many people don't necessarily like) and there are very few performance improvements. So for you to say that it "lacks all logic" is, well, illogical in itself.
While you may like what JB and ICS have to offer and prefer that for your daily driver, I don't think it's fair to ridicule others' personal preference in Android versions, considering the majority of changes between these versions are exclusive to the UI and not Android itself.
Click to expand...
Click to collapse
I stand corrected, thankyou for clearing that up for me, i never thought to look at it in this way, however, when you do get a working recovering, i do so believe i added cdma support in SHTD, the rom was both configured for cdma and for gsm, as it is in the build.prop also!, however a cdma aosp kernel would be needed

cm10.1 wifi bluetooth fixed would be a cool rom... Devs plz fix it... We noobs will be greatfull to you......:laugh::laugh::good:

akashgartia said:
cm10.1 wifi bluetooth fixed would be a cool rom... Devs plz fix it... We noobs will be greatfull to you......:laugh::laugh::good:
Click to expand...
Click to collapse
Don't rush them. They have other stuff to do. If you want it done, you could learn and try it yourself.