Related
do we really need so many competing roms? it;s hard to choose between the many 2.1 roms for my hero
steelbytes said:
do we really need so many competing roms? it;s hard to choose between the many 2.1 roms for my hero
Click to expand...
Click to collapse
Yeah, we do. The ROM devs are in most cases developing the ROMs to suit their own needs for a ROM, but also so kind that they share them with others, while other devs are doing it to learn about android, development etc. If you have problems choosing which ROM to use, stay with the stock - otherwise flash, experiment and have fun!
As a general rule, the more chefs you have, the better the overall quality of all the ROMs.
Whilst it is "logical" to try to have several chefs work on a single ROM, the reality of the situation is that tight collaboration is very difficult when you are talking about something that is generally only developed in peoples spare time.
Regards,
Dave
It is a bit annoying to see 6 replicas of one rom, just with a few different apps chucked in. That's the nature of Android development these days though. I think it was Cyanogen that suggested that a proficiency with Winzip makes you a 'developer' these days...
Personally, I don't see it as a competition. If I could help out Benhaam or Lox in any way with one of their roms, I would.
To be totally truthful, pick ANY of the current Eris builds, and the chances are there isn't much of a difference between them. It's better to pick a rom with an active dev and following in my opinion.
don't worry i have flashed happily, as I can't live with stock 1.5 (come on htc, please release 2.1 for the hero). just felt like whinging after studying this forum to try and guess which rom would best suit me and finding not much clear info.
am running neo 1.3 (2.1+sense) on my hero, and stock 2.1 on my nexusone. very interesting to compare and contrast the two - unsure if I prefer sense or not, but do like (need) the htc exchange client having calendar support (hey googgle, why doesn't stock android have this?)
as i tested all Eris rom here villain3.3 is most stable but i still revert back to SenseHero 1.6 which more smoother run & it is an ART WORK! Hope the offcial 2.1 for hero will out soon ='(
ahh finally i can vent my frustration. its not the amount of roms that are available that bothers me as the devs on here are quite good but the way they dont seem to work together nor communicate. i may be rom. all the devs on here are busy working with this bugged up Eris dump and everything else has been neglected. All the Eris roms are more or less the same and all more or less offer the same positives and negatives. Vanillian which is a fantastic rom has all been neglected so all we have to flash apart from Ahero 0.52 are all the same thing. it doesnt take long to flash all the 2.1 Eris dumps roms on offer before you find yourself running back to MCR or Sensehero due to that bugged up dump. it would be nice to see some form of variety in this forum and not every chef offering 2.1 Eris roms which are far from complete. each dev adds something different to their roms but alas they do not make that mucvh different to the end product. come on guys not all of us want to use 2.1 Eris dumps, we also like the vanilla options too. soon when Legend dump is available we will have similar 6 roms with Legend roms. there is not much vareity in this forum and it be nice to see more vareity on here. i have flashed them all, yep all the bugged up Eris ports and always head back to 1.5 for various reasons...........however Ahero 0.52 is there to save the day and offer a different alternate solution.
please dont flame me for expressing my opinion. feel free to express yours as i have done mine.
shingers5 said:
its not the amount of roms that are available that bothers me as the devs on here are quite good but the way they dont seem to work together nor communicate.
Click to expand...
Click to collapse
Actually, the devs communicate quite well via Twitter. If I'm not mistaken, Lox and Behnaam likes to communicate via Gtalk (from what I followed).
steelbytes said:
do we really need so many competing roms? it;s hard to choose between the many 2.1 roms for my hero
Click to expand...
Click to collapse
No, we don't. And we shouldn't. Why?
Look at the Linux distribution arena (and not only).
They're a lot, but none is really viable on everyday desktop/laptop use.
The reason is simple: fragmentation.
Fragmentation of (scarce) human resources.
Fragmentation of (even more scarce) economic resources.
Fragmentation of the (ever growing) user base.
The same goes for the graphical desktop environments (KDE, GNOME, Xfce to name a few).
On the opposite side we have the internet browser and the *BSD OSes.
We actually have much fewer actors, with stabler products, better engineering.
What I'd like to see in the Android arena is a very stable and effective software base on top of which a relatively large number (I'd say about 5 and less than 10) of UI tweakers and developers push the user experience to the max.
But, again, a single high quality software base (that is the kernel, the system libraries and so on).
This's my EUR 0.005 contribution.
Linux technically is not the OS Linux it is the kernel, its not fragmented at all, as the developers submit the changes and its decided by a set group, the same as any closed dev team would do but they are at different world locations.
Because of how BSD is closed off it takes 3x longer for new software to be implemented..and driver are a nightmare
If the rom dev sub foum was not so cluttered with things that don't belong in it like this thread that should really be in the Q&A section, it would be easier to keep track of the roms..
my 1p woth..
anarchyuk said:
Linux technically is not the OS Linux it is the kernel
Click to expand...
Click to collapse
Linux is the kernel. And GNU/LInux is the (basic) OS with all the GNU stuff.
So I can say that 99% of Linux kernel based distros are Linux.
anarchyuk said:
its not fragmented at all, as the developers submit the changes and its decided by a set group, the same as any closed dev team would do but they are at different world locations.
Click to expand...
Click to collapse
It is fragmented. Take an application at random, let's say Openoffice or GIMP.
You cannot just download ONE aplication and install it on any distro. That's not because of the packaging medium (RPM, DEB, TGZ etc.) but because of software and library dependecies and other system dependent choices.
If you choose, let's say, Ubuntu 9.10 and the package (version) you need is not available for it, then it's up to you to invest in time in makeing an hand made installation ...
anarchyuk said:
Because of how BSD is closed off it takes 3x longer for new software to be implemented..and driver are a nightmare
Click to expand...
Click to collapse
That's because the human resources are scarse, not because of the "closed" model. And then you have a choice among super-distributions on top of FreeBSD, though.
anarchyuk said:
If the rom dev sub foum was not so cluttered with things that don't belong in it like this thread that should really be in the Q&A section, it would be easier to keep track of the roms..
my 1p woth..
Click to expand...
Click to collapse
I can count not less than half a dozen of 2.1 based ROMs all with very minor differences each other. And the same goes for the 1.5.
I cannot swear on it, but I think that the biggest gap is in less than 5% of the whole system.
EUR 0.005 ~ GBP 0.01
Uqbar said:
I can count not less than half a dozen of 2.1 based ROMs all with very minor differences each other. And the same goes for the 1.5.
I cannot swear on it, but I think that the biggest gap is in less than 5% of the whole system.
EUR 0.005 ~ GBP 0.01
Click to expand...
Click to collapse
5%? How did you come to such a precise conclusion?
Do share your calculations with us.
I guess you didn't take into account some of the AOSP based ROMs.
I do agree; there's A LOT of cloning; a guy taking someone's ROM, repackaging with some "customization", and calling it his own work.
This is one of the reasons I totally left the WinMo devving, but I knew it was a matter of time till the same happened to the Android scene.
That's sad, but true.
I don't even care about some of the guys calling themselves "devs", just because they "released" a few roms, who don't even give credit to the people, thanks to whom they learnt/started.
As long as they get enough attention to their thread, they no longer care about the aformentioned. What for? ... It's like a machine which just turns itself after a while.
The more ROMS we have the better, the thread title is a backwards title.
No calculation. Simply I compare performances and features from 3.3 to 3.4.
3.4 is no more stable or fast than 3.4, to me at least.
Memory footprint is almost the same. Not FC in aither ROM ...
And I bet that if nprussel brought anything bigger than 5% he would have put it into the annoucement.
Instead it shows little more than new application list and a GUI theme.
Uqbar said:
No calculation. Simply I compare performances and features from 3.3 to 3.4.
3.4 is no more stable or fast than 3.4, to me at least.
Memory footprint is almost the same. Not FC in aither ROM ...
And I bet that if nprussel brought anything bigger than 5% he would have put it into the annoucement.
Instead it shows little more than new application list and a GUI theme.
Click to expand...
Click to collapse
My point about the fragmentation was in relation to the kernel not a minor thing like dependency's that really has no relation to fragmentation, The Distribution is called a Linux based distribution not "Linux" in an entirety!
Anyway... I know what the above posters are getting at when it comes to people making a minor change to other peoples dumps and claiming to be dev's when really they are nothing more than cooks.
No to take away any credit for what the produce but if you look at the g1 forums it seems a mass of good work, but very little low level development actually happens on the hero side.
adwinp said:
5%? How did you come to such a precise conclusion?
Do share your calculations with us.
I guess you didn't take into account some of the AOSP based ROMs.
I do agree; there's A LOT of cloning; a guy taking someone's ROM, repackaging with some "customization", and calling it his own work.
This is one of the reasons I totally left the WinMo devving, but I knew it was a matter of time till the same happened to the Android scene.
That's sad, but true.
I don't even care about some of the guys calling themselves "devs", just because they "released" a few roms, who don't even give credit to the people, thanks to whom they learnt/started.
As long as they get enough attention to their thread, they no longer care about the aformentioned. What for? ... It's like a machine which just turns itself after a while.
Click to expand...
Click to collapse
Hey man.. Am I missing something or aren't you cooking anymore?
OT: i totally agree by what you say about releasing a rom that just doesn't need any hardcore coding. Even I without any linux skills can "cook" (read: remove / add apps) This is not creating a rom. This is personalizing one to suit your needs.
Creating a rom imho is coming up with new (speed) hacks or options to make it more functional. Or better looking. From what I "learned" even creating a skin isn't that easy as it was with winmo with all that scripting.
my 2k
Meh, I have a G1, its pretty obvious when roms stand out, for the G1
SuperD (1.6)
FastTest (1.6) based on SuperD, but bleeding edge
CyanogenMod (1.6) Stable, more than anything
OpenEclair (2.1) Collaborative project between ChrisSaywer/WesGarner
and for 2.1 sense roms, I normally run a KingKlick rom...
it seems, for stability, and general acceptance that Fresh is the way to go, but there are other builds that use his stuff for a base that are more bleeding edge but have improvements... its pretty easy to see whats popular just by a view/post count on the thread.
Uqbar said:
No calculation. Simply I compare performances and features from 3.3 to 3.4.
3.4 is no more stable or fast than 3.4, to me at least.
Memory footprint is almost the same. Not FC in aither ROM ...
And I bet that if nprussel brought anything bigger than 5% he would have put it into the annoucement.
Instead it shows little more than new application list and a GUI theme.
Click to expand...
Click to collapse
VillainROM 3.3:
1. Linpack: 2.336 MFLOPS (more is better)
2. BenchmarkPi: 13664ms (less is better)
3. Benchmark: (more is better)
* Graphic: Total graphics score - 123.18746
* CPU: Total CPU score - 157.91457
* Memory: Total memory score - 139.30379
* Filesystem: Total filesystem score - 25.63833
VillainROM 3.4:
1. Linpack: 2.372 MFLOPS (more is better)
2. BenchmarkPi: 13049ms (less is better)
3. Benchmark: (more is better)
* Graphic: Total graphics score - 129.06668
* CPU: Total CPU score - 149.84908
* Memory: Total memory score - 131.71753
* Filesystem: Total filesystem score - 34.176556
I suppose 5% is close. I didn't claim it would be significantly quicker. It's definitely quicker though.
Anyway, that's besides the point.
Benham is leading the way right now in my opinion, but I have just got my hands on a Legend leak, that I have got to boot on the Hero. I'm currently trying to get all the hardware working (Wifi, mic, back speaker, GPS all not working). I have asked a couple of other developers for some help, and we'll probably release it as a community release.
I think the rom developers should start working together and create teams. Maybe some could focus on fixing stability issues, some on improving speed and compatibility, some on implementing features from other rom releases and some on optimizing and implementing themes. There is a optimum for the OS, so why put a lot of time and effort into fixing the same bugs and problems over and over again in different rom releases? The differences lay within the themes and included features, which could be made available as separate (and optional) installer packages. So I say..... organize and collaborate! Independent Android development (independent from the manufacturers) as a community will be much more powerful and professional.
Different branches could emerge from the Hero branch easily, making the developers base grow and 'interaction' between the different branches a lot easier.
Bram77 said:
I think the rom developers should start working together and create teams. Maybe some could focus on fixing stability issues, some on improving speed and compatibility, some on implementing features from other rom releases and some on optimizing and implementing themes. There is a optimum for the OS, so why put a lot of time and effort into fixing the same bugs and problems over and over again in different rom releases? The differences lay within the themes and included features, which could be made available as separate (and optional) installer packages. So I say..... organize and collaborate! Independent Android development (independent from the manufacturers) as a community will be much more powerful and professional.
Different branches could emerge from the Hero branch easily, making the developers base grow and 'interaction' between the different branches a lot easier.
Click to expand...
Click to collapse
So, err..in other words; Workers of the world unite? well, im a keen supporter of that
Should we wait for FroYo or robe a bank and buy the Nexus/Desire ? FroYo should be 350% faster than 2.1? Even 30% will be miracle for Kaiser. What do you thing?
The Nexus One wasn't having it's FPU used in older Android versions. FroYo simply takes advantage of the FPU in the SnapDragon chip. So us getting FroYo won't do anything.
On the other hand, we could get a JIT compiler like the G1's have. It's a pretty big performance improvement.
The one good thing about FroYo is battery life.
Dukenukemx said:
The Nexus One wasn't having it's FPU used in older Android versions. FroYo simply takes advantage of the FPU in the SnapDragon chip. So us getting FroYo won't do anything.
On the other hand, we could get a JIT compiler like the G1's have. It's a pretty big performance improvement.
The one good thing about FroYo is battery life.
Click to expand...
Click to collapse
Thx for this information. I hope that someone will have time for that port.
The froyo code is out on googlecode start your porting
froyo looks promising
www.pcworld.com/article/196833/google_android_22_questions_and_answers.html
I read up on froyo recently on pc world and it looks fairly promising. No more "apps2sd", much faster, better performance. Lets try to get this fully working on kaiser asap! Especially on NAND.
mssmison from the Vogue forums is already working on it. We might see a build from him soon.
Dukenukemx said:
mssmison from the Vogue forums is already working on it. We might see a build from him soon.
Click to expand...
Click to collapse
can you post the link?
Here's the link. Just remember he's playing with it. Doesn't guarantee that we'll see a FroYo build from him.
http://forum.xda-developers.com/showthread.php?t=680603
Does TP2 meet ANDROID 2.2's hardware requirements?
Nope. most devices that would get a froyo update have snapdragons under the hood something our rhodiums dont have
ive read in several places and posts frm owners that the FROYO is overhyped. or not really all that much different frm the previous releases. i know its supposedly alot faster with the JIT Compiling. i guess thats the main difference and the fact that the new flash player10 wrks great with it. people sleeping on Rhodium. its always like that with new devices. they get upgraded processors. there are ways around that, which i hope someone figures out soon ;-) just like with cars, we can tweak it to at least get closer to Snapdragon speeds.
overclocking the processer or tweaking froyo
rsmith675 said:
overclocking the processer or tweaking froyo
Click to expand...
Click to collapse
well i meant overclocking the processor to where its faster and still stable. tweaking could probaly also be done on the software(FROYO) side of things. if older phones with even less processing power can port Android, then we can get the Froyo. i know its not that simple but it can be done. just depends on how much wrk someone is willing to put in on it. like for instance, i edited my startup txt to overclock my processor in the android build. im at 633MHz. stock max processor speed in windows mobile is like 528MHz. so with that overclock alone, increased the horsepower..lol, by more thn a hundred. now my live wallpapers fly across the screen instead of stuttering. i have virtually no lag now. plus i could even go up somemore on the overclocking. . it does have a drawbck. if i put the phone to sleep, it wont wake up..lmfao . who cares, just dont put the phone to sleep then. Android on Rhodium is more of a research and testing things out, at least for me. im luvin it so far, so i cant complain about what its missing at the moment. Im grateful for what wrks at the moment. this is the best cab by far that ive ever downloaded, and its free. u cant beat that. basically a free Android OS.
rsmith675 said:
Nope. most devices that would get a froyo update have snapdragons under the hood something our rhodiums dont have
Click to expand...
Click to collapse
bull****.
there is no such "requirement" for froyo.
furthermore, TP2 never had an official android release to have an official denial that it will ever be ported.
i'm sure devs are already looking at porting froyo to TP2 and other phones.
Best/easiest case solution is to backport some of the parts of compatible Froyo into the TP2 AOSP Eclair build. This has been a common practice in custom roms. There's already G1 roms with Froyo partially working. There's no reason not to have at least some Froyo features baked into TP2 Eclair.
At this point, whats the use of moving on to Froyo on the TP2? We'll migrate just to restart back to a point where nothing works? Backport some parts of Froyo onto Eclair and beef up Eclair to a point where the major issues are resolved.
<rant>
Also, there needs to be more people that have a better working knowledge of Android/linux than just the devs. Fixes, hacks, mods all come from a community effort. Not enough information is shared on this forum, and it comes at the cost of progression for our devices.
</rant>
cashless said:
There's no reason not to have at least some Froyo features baked into TP2 Eclair.
Click to expand...
Click to collapse
so do it. talking is easy, actually doing takes skills.
In theory 2.2 should run better on the rhodium than 2.1 ever has now that it has a huge upgrade to the Dalvik vm JIT, meaning this makes much better use of the processor, this is proven in the current builds on the nexus one. I agree that we would essentially be starting over as far as useability but the developers have already done the ground work so a full upgrade to 2.2 will not take as long as the first porting of android. So if you all just want to sit back and be happy with what you have than go ahead, but in my opinion 2.2 would be a very valuable upgrade as i'm sure that 2.3 and beyond will be.
No, It can be done on every Android Phone, so also the TP2 would be able (if you look at the specs) to run Android 2.2.
http://www.androidpolice.com/2010/0...t-even-the-g1-google-io-blitz-coverage-day-1/
And it will make the devices faster So I think there is a possability. I hope the android devs for TP2 will give it a try
Yes it can, but it will take a lot of work
rsmith675 said:
Nope. most devices that would get a froyo update have snapdragons under the hood something our rhodiums dont have
Click to expand...
Click to collapse
HTC will release official froyo rom for HERO and later devices, TP2 has same hardware installed as HERO
but the key problem is drivers, HERO's screen solution is lower than TP2, so HERO have different GPU driver to TP2
i hope hackers will give us some good idea..hah
I'm ready.. been duel booting android and I have to say I like it.. Didn't think I would but I do. It's faster and easy to use
03hdfatboy said:
I'm ready.. been duel booting android and I have to say I like it.. Didn't think I would but I do. It's faster and easy to use
Click to expand...
Click to collapse
how did you do that?
i tried flash dual boot rom which found in TP2 CDMA, but it is always mess up during first time loading
mxxcon said:
so do it. talking is easy, actually doing takes skills.
Click to expand...
Click to collapse
It is actually easy, I've done it and pretty much anyone can do it with simple common sense on any native Android phone. Making your very personal use ROM with backported parts is really common. It doesn't actually take that much skill because all you're doing is replacing (sometimes) compatible parts and modifying the init.rc and flashing in recovery for the most part.
bestfan said:
how did you do that?
i tried flash dual boot rom which found in TP2 CDMA, but it is always mess up during first time loading
Click to expand...
Click to collapse
Are you using the .cab or .rar, I never got the .cab to work, the .rar works perfectly everytime and I do quite of bit of "flashing".
I am willing to stick with 2.1 for the long haul until everything is working.
seeing as 2.2 is supposed to have some drastic changes i think 2.1 is going to be the final for most things, 2.2 codebase while being similar has been drastically enhanced (in some areas)...
I myself cannot wait till the TP2 gets Android 2.2+ (and the COMPLETE ability to boot into android without having to load ANY WM aspects)
hi all, i'm still here
i installed android on my kaiser (scooter's cyanomod build froyo), and i'm happy (exept for the camera... still hoping) but i have a question :
it's normal that the animation are slow, the menu are ... don't know... "fat" to appear even with a fresh installation...
i mean, i know that kaiser is not the fastest phone on the Earth, but i think that a completely empty android coud be handeled by it..
i tried to play with compache settings, but i dont have manu results, and i prefere not to overclock, due to the high battery drain
ps : i tried to search in the forum and in google, but with no results
thanks !
I know what you mean. I wasn´t here in the Kaiser thread for a long time because i have a HTC HD2 now. But i loved Android for my Kaiser.
I can say that the older Donut builts runs much faster/smoother than froyo. The Kaiser is an old Phone but quite good. But it is like as it is on PC. You can run Vista on an old machine but the experience is... uhm...
I had Myn´s Warm Donut on my Kaiser but it seems that there is no further development. But RLS5 was fast an stable...
Another thing for smoothiness is the kernel you use. I changed to an older kernel because under a newer one the animations seems to be laggy. I dont know how it is now with the kernels. But you should test some different kernels.
I should dig out my Kaiser an play a little bit around with the new kernels and androids... ;-)
@ highcoder:...
2 builds of Froyo I would suggest is ThoughtlessKyle's NSS (Not So Super) Froyo and Incubus26Jc_'s Super FroYo RLS15 with .25 for a kernel. You have to put in a wireless update, and either 1.65 or 1.70 radio ROMs (both work great), but so far so good. 520MHz OC and everything on NAND and the only app that FC's on me is Pandora radio (I guess because it uses so much memory for each song)
I will probably be trying ThoughtlessKyle's Fat Free Froyo soon with the same .25 kernel here soon, but the 2 suggested above seem to be what I like to use.
Fat Free Froyo is by far the fastest release I tried.. But I'm still facing some problems with my battery, it drains so fast.. I think i will go a release back and try Donut for a change
EIDT:
highcoder said:
I can say that the older Donut builts runs much faster/smoother than froyo. The Kaiser is an old Phone but quite good. But it is like as it is on PC. You can run Vista on an old machine but the experience is... uhm...
Click to expand...
Click to collapse
Best explanation quote
thanks for reply
poor kaiser, is a little oldie phone =) but with android maquillage tadaaan, it seems brand nes (ehm...)
i'll try with a stable .25 kernel version then
but htc touch (touch dual) is better than kaiseR? the cpu freq is the same... (even worst, in compasrison wih the first touch 200mhz)
thanks again
I'm running the .35 kernel with an overclock at 500Mhz done using Atools.I have always overclocked to 500 using this method & my battery lasts for a good couple of days with moderate use.well,texting,the odd phone call and a bit of data usage.
Sent from my CyanogenMod Kaiser/Kaiser using XDA App
scooter1556 said:
I'm running the .35 kernel with an overclock at 500Mhz done using Atools.I have always overclocked to 500 using this method & my battery lasts for a good couple of days with moderate use.well,texting,the odd phone call and a bit of data usage.
Sent from my CyanogenMod Kaiser/Kaiser using XDA App
Click to expand...
Click to collapse
I found using Vaniji Eclair with the .25 kernel is the fastest, and gives me decent battery life (about 12hrs with moderate use). I've been using Gingerbones with the .32 kernel, but because of how unstable .32 kernel is, I kept getting crashes, data corruption, etc...
Scooter, how did you get the .35 kernel? Can you IM me how or where you got it, so I can maybe compile my own version? The thought that you get several days under moderate use makes me want to get inside the kernel to check out if CPUFreq is indeed working on that kernel.
can i have your kernel too? or where to get it
thanks !
Krazy-Killa said:
Scooter, how did you get the .35 kernel? Can you IM me how or where you got it, so I can maybe compile my own version? The thought that you get several days under moderate use makes me want to get inside the kernel to check out if CPUFreq is indeed working on that kernel.
Click to expand...
Click to collapse
The kernel i am using is compiled from dzo's original .32 git repo, i have made a few adjustments to it which i can't remember because it was before christmas. Once i've got my jan exams out the way i will do a git diff and push any changes i have made. Life's a little chaotic at the minute though. I am running my 5.5 build, phone came off charge at 9 this morning and was reading 97%, after a day of texting, some data usage and general gaming on the toilet (as you do!!) my battery is reading 70%. It's the original samsung battery too, so it's quite a few years old.
scooter1556 said:
The kernel i am using is compiled from dzo's original .32 git repo, i have made a few adjustments to it which i can't remember because it was before christmas. Once i've got my jan exams out the way i will do a git diff and push any changes i have made. Life's a little chaotic at the minute though. I am running my 5.5 build, phone came off charge at 9 this morning and was reading 97%, after a day of texting, some data usage and general gaming on the toilet (as you do!!) my battery is reading 70%. It's the original samsung battery too, so it's quite a few years old.
Click to expand...
Click to collapse
Oh nice! Looking forward to compiling this myself, though really don't mind trying it out now. lol
Well back on topic, since everyone here is saying go Donut, I think I'll be a rebel and say go Eclair, it's not far from Froyo, and ahead of Donut, so you kinda get the inbetween of the two.
today i tried to overclock my kernel to 500 mhz...
now, i see a lot of artifatcs... now i rollback, but anyone had the same issue?
with "atools" can i set something that can help me to inmprove performance?
thanksy
update : rolled back to base kernel... but artifacts still here
another update : downloaded from frash the kernel, applied the overclock to 500 and no other options : no more artifacts
Ok i´ve reactivated my Kaiser to try around a little bit.
The last one i´ve tried was Fat Free Froyo with the latest 2.6.32 Kernel from DZO and it´s a very fast & stable built. Not as fast/smooth as Myn´s warm Donut (with an older Kernel) but for a Froyo on Kaiser much impressive.
@bboygolem
Overclocking ist not the best way to improve performance. Better... its a poor way. Even if you have a new big battery the batterylife is not so long... one day or so... and if you now speed up your CPU your batterydrain is much higher, the thermal stress for CPU and other components is higher and the chance of force closes, app hangs, artifacts, system crash, data corruption/loss is very high. On the other side you have only a little performance increase. Too little that you dont recognise it in all day use. Of course a calculating benchmark will show you maybe a 20% performance boost but only for calculating things. But the Speed of an operating system is defined by the weakest thing in the whole chain.
Better get a good optimized android built. building a android for kaiser nowdays is easy as going to toilet, but cook a highly optimized, smooth runnin, slim rom is the real deal...
So you have to test and compare the builts and the kernels (the newest is not always the best).
The best (fast,smooth,stable) built on the first Forumpage is Fat Free Froyo.
But still the best (most suitable for Kaiser) built i´ve ever tested is Myn´s Warm Donut RLS5 in conjunction with an older Kernel from Kallt_Kaffee. The best combination ever.
It is an Android 1.6 so it is older but smaller too. So it runs faster and smoother and you have more RAM for apps. Especially when you run resourcehungry programs like Navigon Mobile Navigator you need the extra Memory. With eclayr, froyo you have only force closes...
But at least it´s on you. Your favors, your taste, your choice...
highcoder said:
it´s a very fast & stable built. Not as fast/smooth as Myn´s warm Donut (with an older Kernel) but for a Froyo on Kaiser much impressive.
Click to expand...
Click to collapse
May I ask about the battery consumption in Myn's warm Donut release? is it the same as Froyo built?
highcoder, thanks for you reply, but i have some questions:
1 - i know that overclocking the cpu , i have a more battery drain and disease percentage, but i noticed a little performance increase.... can it be "placebo effect"?
2 - I thought to use the old kernel, but i read somewhere that is slower than the new one. It's true?
3 - I can install the donut, i don't care about eyecandy's, but I'm afraid that a lot of apps in the market shall not work with the "donut" distribution.. am i wrong? using fat free froyo with the old kernel shall improve my performance?
thanks again
sorry, dobule post
Oh that are a lot of questions i cant answer properly.
The overclocking has of course an effect. But it is only a little average performance increase. Hard to notice that. the most of that is really placebo. But the risk of brick something or to have an instable system ist sigificant higher... so its not worth it...
i dont know about the older kernels because i have a HTC HD2 since 6 Month so there was a lot of change here. Froyo have got a real performance increase the last months. So the kerneldevs and the chef´s here do a good work. But the best Foyobuilt (2.2) here with the newest kernel don´t beat the smoothieness and felt speed of Myn´s warm Donut (1.6).
I never had a problem with market apps and donut. Shure there will be apps that wont work with donut anymore but for that case there are enough alternative apps that will work.
If you want i can search my HDD´s for the kernel i used an give it to you...
But now i´ll go to bed.
thanks highcoder, it'd be very kind from you =)
have a good night
@bigboss2200 & bboygolem
Battry Drain Test with newest DZO Kernel and Fat Free Froyo is in progress. After that i will test Myn´s war Donut with a NEW Kernel. So i can compare these builts about batterydrain and Speed. May be the speed improvements of the new Froyobuilts i´ve noticed are only Kernel related. In this case Myn´s warm donut should benefit from this kernel optimizations too an we will have a real performance boost. I'm curious about it.
I will post my results...
in the meantime, i installet latest dzo kernel and fat free froyo, and it seems stable and usable
but if using the .25 kernel i will be able to use the camera and to shut down the phone permanently, keeping an accettable speed, i think i'd downgrade the kernel
i'm looking forward to see your test results
ok i have tested Myns warm donut with .32 kernel = laggy animations
so i downloaded the latest .25 kernel from here. After that i downloaded the mandatory update for all older builts from here. Without this update wifi won´t work. In newer builts it is cooked in already.
Flash the kernel.
Install Myns
Install Update
Weeehaaaa! It works with the newer .25 too. Smooth animations, very responsive and snappy. WLAN works fine... battery drain will show a longer test...
I always made some adjustments. Go to spareparts -> Window Animation = fast and transition animation = fast, fancy input animation = on
Give it a try... Let your Kaiser feel "young" again ;-)
EDIT: Dont use the builtin Astro filemanager. Its outdated... Download a newone from market. My Favourite is Estrong ESfileexplorer. Because it can handle FTP and SMB. That mean Windows network shares too. So you can exchange your files over wlan with your PC.
Hello everybody,
I do respect all the work most of you invested in creating new Android roms. The only problem I see is that most of the roms are based on latest Android versions as Froyo. We need to admit that we have a pretty slow device so from my point of view a Donut rom is something more feasible for our hardware. I was wondering if there is any stable Donut rom you could recommend.
Thank you
Considering that there are G1s out there running Gingerbread already, and they have half the memory of the TP2, I'd say your concern is misguided.
candin1977 said:
Hello everybody,
I do respect all the work most of you invested in creating new Android roms. The only problem I see is that most of the roms are based on latest Android versions as Froyo. We need to admit that we have a pretty slow device so from my point of view a Donut rom is something more feasible for our hardware. I was wondering if there is any stable Donut rom you could recommend.
Thank you
Click to expand...
Click to collapse
if you are so desperate to get an donut rom you could check over @ neopeek, i saw an eclair and donut rom there if im correct.
One of my first work has been a port of Myn's Warm Donut with working 3D on Diamond! If more people request this I may have a look but can't say atm if all of the newer kernels would work...
Hi. I agree if we consider the Ram. What about the processor? Both devices have processors of the same generation.
candin1977 said:
Hello everybody,
I do respect all the work most of you invested in creating new Android roms. The only problem I see is that most of the roms are based on latest Android versions as Froyo. We need to admit that we have a pretty slow device so from my point of view a Donut rom is something more feasible for our hardware. I was wondering if there is any stable Donut rom you could recommend.
Thank you
Click to expand...
Click to collapse
I felt the same way until I tried Gingerbread. GB0XA is the best (speed wise) option I have found for a non-OC RHOD400.
I'll throw in a +1 for this as well,I would love to see donut running on here,froyo and gingerbread are nice,and yes,the g1 technically does run gingerbread,but have you ever actually used it? It's painfully slow compared to donut,and I have a feeling our phones are probably the same way considering how similar they are.
msnuser111 said:
I'll throw in a +1 for this as well,I would love to see donut running on here,froyo and gingerbread are nice,and yes,the g1 technically does run gingerbread,but have you ever actually used it? It's painfully slow compared to donut,and I have a feeling our phones are probably the same way considering how similar they are.
Click to expand...
Click to collapse
Donut was abandoned. There's probably some old images around, but they won't run very well. Enjoy!
arrrghhh said:
Donut was abandoned. There's probably some old images around, but they won't run very well. Enjoy!
Click to expand...
Click to collapse
The only thing I liked about Donut was the codename.
....Mmmm.... Donuts...
From what I understand froyo shouldnt be much more of a system resource hog than donut was (I believe reading it was actually supposed to be faster but I'm not sure) so it really shouldn't have too big an impact on performance. I've found froyo speeds on certain builds to be quite acceptable.
killerkhatiby009 said:
From what I understand froyo shouldnt be much more of a system resource hog than donut was (I believe reading it was actually supposed to be faster but I'm not sure) so it really shouldn't have too big an impact on performance. I've found froyo speeds on certain builds to be quite acceptable.
Click to expand...
Click to collapse
lol cute. I assume you mean that speeds on XDAndroid's Froyo is not acceptable.
We found the vast majority of the populace would rather take a *slight* performance hit, for better resolution (HDPI vs MDPI).
I assume that's the sore spot as far as speed goes. I find FRX06 to be quite snappy, thank you very much.