Okay first of all I've fully installed WM5 on both devices, 1.60c on XDA II, and 5.03.02 patch 3 (newest for xda iis) and I've noticed major fast improvement and speed with the XDA II, its faster then WM2003SE, and its more stable and great! With the XDA IIs its a laggy piece of crap, I wish someone could make it faster somehow without overclocking it, (by the way even overclocking it) - doesn't make it run as fast as the XDA II, maybe there is a glitch someone can fix, there has to be something thats slowing it down for us XDA IIs users because they both have 400mhz, 128mb ram, I just can't put my finger on it!
I think personally that there is one major device driver causing the problem (And it seems to be with interrupts???). The keyboard driver is my initial guess with the way it behaves so badly but it could be one of many ...
I also have both XDA2 and XDA2s and notice the brutal difference between the two. I wonder if the DOC chip, (the internal Storage area) is of a different design/speed then the XDA2. Maybe the XDA2 has a much faster ROM read/write speed then the XDA2s.
I've mentioned to Buzz and mamaich to build a Storage=1/2 RAM build of the XDA2s ROM, (like they have for XDA2) but they haven't made it yet. If they do, and we are writing all Storage to RAM, (and therefore losing persistence) and its STILL SLOW... then I would think would have to be some other driver.
mamaich:Buzz: If you are seeing this, please build this ROM
I think "laggy piece of crap" is a bit harsh considering how far this rom has come since it was first released. With the latest release the speed increase is obvious and only browsing with PIE and email remain a bit sluggish. I'm sure if it was possible all issues would have been resolved by now and remember this is unfinished code we are running and work is still beig done on it behind the scenes. So rather than calling hours of others work "crap" just highlight what issues you still have and they will get to it if possible. At least with this rom I feel less of an urge to spend $800-1000 for the new devices.
efjay said:
I think "laggy piece of crap" is a bit harsh considering how far this rom has come since it was first released. With the latest release the speed increase is obvious and only browsing with PIE and email remain a bit sluggish. I'm sure if it was possible all issues would have been resolved by now and remember this is unfinished code we are running and work is still beig done on it behind the scenes. So rather than calling hours of others work "crap" just highlight what issues you still have and they will get to it if possible. At least with this rom I feel less of an urge to spend $800-1000 for the new devices.
Click to expand...
Click to collapse
I was wrong it's not a laggy piece of crap, it just needs minor work ;-).
All the above being said…, there are some significant speed differences... or maybe my case is special...I've asked others to try this, (consensus would be nice).
If you have Resco Explorer installed on ROM-Storage, run it in BA-WM2005 and it should take about 5-6 seconds to come up, (after a soft-reset so it’s not in the file cache). Run it in XDA2-WM2005 and it’s about 1-2 seconds; run it in BA-Wm2003 and its <1 second.
Now once it’s loaded, it runs fine, (as does every other app), that’s why I think it might just be a read/write speed problem with the XDA2s DOC chip, (and therefore unfortunately not solvable)… which is why I would LOVE to get a 64Meg RAM Storage, 64Meg RAM Program version to confirm that is the case, once and for all….
Guys the BA-5.0 still needs loads of work and patches, remember that mamaich doesn't have the fully time to tweak the ROM, not to mention that the Hima magneto rom has been released since long time and BuZz made lots of major updates on it, and still a lot to come, I'd rate the Hima rom for 80% of completion but the BA rom is still on it's early stages, lets wait and see.. Believe me "When there's a will, there's a way"
Buzz, Mamaich and others work will be written on stones.
maybe it's because the himalaya rom is a much more later version of WM5, might even be a final version compared to the BA rom that's obviously a beta or engineering ROM, hence, you can even see that the splash screen cannot even be changed
Dyzophoria said:
maybe it's because the himalaya rom is a much more later version of WM5, might even be a final version compared to the BA rom that's obviously a beta or engineering ROM, hence, you can even see that the splash screen cannot even be changed
Click to expand...
Click to collapse
I'm sure if we get into the splash screen offsets we could change it, nothing is impossible, thus I believe that the Hima's-BA's-Typhoon roms shares the same Beta built, if we had the right tools to allow us write into the ROM we would have got the perfect hacked rom ever thanks to everyone in this forum.
ramram said:
Guys the BA-5.0 still needs loads of work and patches, remember that mamaich doesn't have the fully time to tweak the ROM, not to mention that the Hima magneto rom has been released since long time and BuZz made lots of major updates on it, and still a lot to come, I'd rate the Hima rom for 80% of completion but the BA rom is still on it's early stages, lets wait and see.. Believe me "When there's a will, there's a way"
Buzz, Mamaich and others work will be written on stones.
Click to expand...
Click to collapse
I'm totally agree with what ramram said. Way to go Buzz & Mamaich!
Let's just be patient and wait until the next update
I remembered the time when mamaich released his 3rd patch which makes major improvement in performance of WM5 BA. I was so happy I can see more responsive BA, and thanks to mamaich
i own a large amount of htc phones, but my mainphones have always been wizard/hermes sofar. I recently bought a universal, but it's too much phone for me. Too big/i live in a bad triband area. i hate to part with it but ehwell.
my question is, i bought a kaiser yesterday. theres android ports for it, whats the speed of them like?
preferbaly a comparinson to the droid eris, it's the only android phone i've played with.
any input would be apperciated, thanksguys!
Kaiser/Tilt
I have two of them running Android. One is Using the Polyrythmic version the other is the KaiserDroid. Both seem to operate well. I like polyrythmics and Im using it for a daily phone. The other Im still toying with. I suggest you read both threads and make sure you understand what youre doing before you do it.Dont fall into the traps that are well documented. Good luck
What I have noticed
I am using Polyrythmic 2.1b, and love it. I have gone though a few versions with them, in Haret and NAND. I have found that the NAND is faster if you are willing to take the full plunge. I only have one phone and feel fully confident in the release that it has been my daily release since the 2/23/10. A few things don’t work, but they were not biggie items to me. Read as much as you can before making the plunge.
Have to say, both the main eclair versions of android are very good, and there are a number of other flavours as well, myn's warm donut is getting good reviews also.
Recommendations? personally I divide my time between Polymod and Kaiserdroid, and have tried another few 'distros' as well.
The main questions to ask before using android are :
Do I need a working Camera?
Do I need working Bluetooth?
Do I need reliable GPS?
Have I read the Stickies in the ROM development section, and/or flashed HardSPL, upgraded my radio, unlocked security,cid and sim?
If any of the first 3 are 'Yes I MUST have these working' then android is not yet ready for you, there is still some work to be done in these areas.
If you answered the last with 'WTF is HardSPL and why do I need it?' then
you are not yet ready for Android
If you know all this stuff already, then my main advice is this:
Run from Sd card, try a few different distros, get used to the installer, learn what panel type, keyboard and resolution suit your device best, and then it's time for the whole Nand experience
im not going to run into any problems flashing it, i've got no worried about that.
but nobody answered, a) is it faster than wm6 and b) whats the performance hit compared to a native android device?
a) Yes for almost everything I use it's faster than WM6. It has a much faster graphics driver, smoother animations and scrolling, MUCH faster screen rotation. Browsing is faster, messaging is faster, soft keyboard and touch events are MUCH better, SSH is much faster, browsing through photos is faster...
b) Depends on the build. Donut builds are basically as fast as a native device, Eclair builds are fast enough for daily use and getting faster all the time.
Donut runs great and is the most stable, much better user experience than windows all around.
Eclair if you can tweak it to suit you then its a great OS. Probably runs about the same speed as a windows on the kaiser. Still a little glitchy and for the most part all are still in beta form
Tattoo or Hero would be great if speed wasn't an issue
Alright i've recieved the kaiser, i've put kaiserdroid+droidion donut+polys version.
polys ran like hell, im unsure why. maybe ill try off nand, shame becasue its gsm was the only one that half worked.
they accept wifi-on, get an ip, but refuse to actually ping or visit a site. anyone have any input on this?
thanks.
i think most stable rom is here: [Android]The Android Thread [Site Update] on this rom dont work only bluetooth. else everythink other working fully. (exclude market.. it works but when i search ASTRO F. M. it show error something about bad network, but im connected with wifi) but i think its old rom whithout some new functions
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)
Ok, so I got myself a G1.
For those considering getting one of these I must post a few words.
It's really really not that much different regarding speed and stability from my nand flashed Kaiser (kais130), running a stable Eclair build, seriously, I kid you not, and I'm not talking raw processor speed here ( dammit it's nearly the same processor, top speed using setcpu is 576, really not much difference there), feels much the same, looks much the same. ( ok perhaps a little sharper, but that's a user-relative thing), all the same apps perform much the same.
The big shock was battery, it's quite frankly terrible compared to my Kaiser, ok so this may be the old 'battery calibration' thing, but I was shocked at it hitting 8% by lunchtime, my kaiser takes 2 days to reach that level, and yes, I did use a bit more data and gps than usual, but not enough to account for that high a drain. And it does get a little warmer, reminds me of the old days, (january-feb 2010), when we were first using Android on kaiser, hot phones and fast drain.
Flashing is scary, I mean Scary!, all sorts of warnings about bricking your phone, and it's not the nice gentle 'this may brick your phone' this is big red letters, DangerSPL is just that, accidentally flash an older radio with that and it's instabrick, and a visit to men in white coats who understand what JTAG is and have huge wallets.
So am I happy with my G1? Well yeah, I've got the only thing that gives it the edge over my kaiser, Google Sky Map, the Scotsman in me reminds me that £79 is a lot of money, the Uber-Nerd in me opens Sky Map and tells the Scotsman to shut up and look at spica, or the southern cross...........
Oh and with a load of 2 year contracts finishing in the next few months, Ebay is probably going to be seeing quite a few of these.
Why a G1 anyway? The keyboard, and Android, My Kaiser left me hooked on both, and really, there isn't much out there that offers both, so be kind to your Kaiser, it's a great little bit of kit, sure it's old now, but really, it's just as good as a G1, yes I can use Sky Map, but I gotta put it on charge afterward........
You mean the G1 I forgot to bid on lol
Nice write up !
i planned to buy G1, feel so good now
Sent from my T-Mobile myTouch 3G using XDA App
wyxpark said:
i planned to buy G1, feel so good now
Sent from my T-Mobile myTouch 3G using XDA App
Click to expand...
Click to collapse
I think this thread will make a lot of people smile, including me!! I too have been looking at G1's but I love my kaiser and it works so i've always resisted the temptations. Don't know how i'll resist if HTC bring out a new android phone with a keyboard though!!!
What do think about that rolly ball d-pad thing?
Sent from my T-Mobile myTouch 3G using XDA App
Ya I had considered the G1 too.
The screen is a 'little' bigger.
Doesn't it run a old version of Android, are there 'official' updates for it? will it run 2.2?
Personally I was thinking along the lines of getting a Milestone.
I have had my Stellar now for 2 years, (and that was 2nd hand too!) so why would I replace it with a phone that is just as old
I do like the Hero, my friend has one of those, but I miss the keyboard, I struggle to use the onscreen one since I can't 'feel' the keys, I need a hardware keyboard, so that limits the phones I can choose.
Guess I'll be sticking with my Stellar for a while yet, though you notice just how small a 2.8" screen is now, when everyone else has at least 4"!
leona said:
you notice just how small a 2.8" screen is now, when everyone else has at least 4"!
Click to expand...
Click to collapse
And you ladies have us believe size doesn't matter
Ok, day 2, battery life seems a little better, but that's with a 2300mah battery instead of the standard one, still say it's heavier on the battery than my kais though, it is a better handwarmer for certain, theres a discernible warmth to the lower part of the back right side after a call or using gps for a bit.
The trackball actually functions quite nicely, I have heard that some people don't like it, but I find it as useful as the scroll wheel on the kaiser, in other words, I don't use it that often, but when I do, it does what it needs to, no fuss, no messing about.
As far as customisation goes, it usually ships with 1.6 these days, but after rooting it'll go all the way to CM 6 ( Cyanogen Mod 6 = 2.2 ), although I went the CM5 ( 2.1), route myself, ( still requires DangerSPL).
With the stock 1.6 it does feel nice and fast, and has a decent amount of free space for apps, more than comparable donut builds on kaiser, but with Eclair it starts to get a little tight in there, in fact with a careful bit of tweaking I can get more free space on my kais than I can on the G1. ( at the moment both have nearly the same apps installed, G1 after taskiller = 31Mb, kais after taskiller 36Mb ).
No I am not saying the Kaiser is better than the G1, nor am I saying the G1 is better than the Kaiser, what I am saying is that I am finding they are very similar.
Can I recommend the G1 over a Kaiser with nand flashed Android, yes, but only just. The G1 has everything working after all, wifi, bt, gps, camera, video, etc etc, and so they should, the OS is designed for the hardware after all.
If you absolutely need a fully functional android phone with hardware keyboard, the G1 is a good choice, and you get what you pay for.
If you don't really need all the bells and whistles, such as video, autofocus and such, well why not stick with your kaiser, suitably nand flashed with a good stable build, it really is a lovely little machine, yes it is still work in progress, but I'm not ready to chuck mine out, I fully intend to keep it, and now I'm able to do some of the things I couldn't when it was my main phone, such as messing about with builds etc.
I had them both (2 kaisers and one G1): now only one G1.
It's slow if you use it to it's full potential (using lot's of widget's to display everything I need).
It had 1.6installed when I got it, but never used it, straight to CM 5.0.7 test3.
DangerSPL isn't really needed and isn't dangerous at all. MTD is very nice
I use fastboot all the time (is needed for CM6 too; fastboot erase system -x).
There are some nice apps like droidexplorer,... that son't work for the kaiser.
gps fix is really fast (copilot) and most gps offline programs work on hvga compared to the kaiser
The screen (much better for direct sunlight, sharper, multitouch, and finger friendly (not like kaiser!).
I'm on CM 5.0.8 (apps2froyo doesn't work good with tons off apps), waiting for CM 6.1 (but it's not really needed anyway).
Camera is actually very good compared to the windows mobile camera.
Don't use a taskiller (>1.6), use swap instead (swapper, 32-64 or 96MB swap, swappiness 40-60)!
I can multitask 6 GPS programs, read my mails,surf and go back without reloading.
Sound is actually very good compared to kaiser.
getting a Milestone
Click to expand...
Click to collapse
It's expensive compared to G1 (around 100€-80dollar) and the bootloader is a motorola, it's encrypted (no custom updates ).
I bought an unlocked telus milestone a few weeks ago, it came with 2.1 update. I paid close to $500 us. For what i do with my phone, the kaiser nand flashed to mynswarmdonut works fine.Not nearly as flashy. I gave my son the milestone, I'll keep the kaiser for now. I bet my old kaiser will last as long as the new motorola.
Hi zenity, so how are things with the G1 now you have had time to use it a bit more?
You don't mention that the G1 has a digial Compass and the motion sensors that the Kaiser doesn't have, do you use / notice them?
Been reading some of the threads on the G1 forums, they seem really active too, seems like 2.2 has been ported and working. Also see that over clocking the G1 seems common, did I see they had it up to 700Mhz! that must kill the battery and be really unstable. But its stock is 528Mhz whereas the Kaiser is 400Mhz that is quite a bit of difference.
I think I will keep my eye on Ebay and see if I can pick up a cheap one.
I would just like to try one to see how a 'proper' android phone works.
FlanFlinger said:
And you ladies have us believe size doesn't matter
Click to expand...
Click to collapse
Do you not remember the old Renault Advert, "Size Matters" !
If Anyone is interested, here is a comparison of the specifications from the HTC website
Kaiser/Dream G1
Processor Qualcomm® MSM7200TM, 400MHz / Qualcomm® MSM7201A™, 528 MHz
Memory ROM: 256MB / ROM: 256 MB
RAM: 128MB SDRAM / RAM: 192 MB
Display 2.8", 240 X 320 QVGA TFT-LCD / 3.2" 320 x 480 HVGA TFT-LCD
Size LxWxD: 112mm X 59mm X 19mm / 117.7 mm x 55.7 mm x 17.1 mm
Battery Type:Li-polymer / Type: Lithium-ion
Capacity:1350 mAh / Capacity: 1150 mAh
After making my head spin looking at milestones, Desire's and X10's I had a mad moment and have gone for a Galaxy S, this caused much muttering from the wife along the lines of "€100 for a phone!", then I just pointed out that it equated to about 5 pairs of shoes (she's a cheap date ) or one shiny chrome thing to bolt on her Harley (that I have to polish for her coincidently).
It should be arriving tomorrow, so if anyone is interested in an almost spotless Kaiser for €80 then let me know
leona said:
Hi zenity, so how are things with the G1 now you have had time to use it a bit more?
You don't mention that the G1 has a digial Compass and the motion sensors that the Kaiser doesn't have, do you use / notice them?
Been reading some of the threads on the G1 forums, they seem really active too, seems like 2.2 has been ported and working. Also see that over clocking the G1 seems common, did I see they had it up to 700Mhz! that must kill the battery and be really unstable. But its stock is 528Mhz whereas the Kaiser is 400Mhz that is quite a bit of difference.
I think I will keep my eye on Ebay and see if I can pick up a cheap one.
I would just like to try one to see how a 'proper' android phone works.
Click to expand...
Click to collapse
After a little while to settle in, I'm still of the opinion that it is not really noticeably faster in use, 400/528Mhz is not really a huge difference, nor is the extra 64Mb of RAM a huge advantage either, in fact as I said before it seems to run out of RAM faster than my kaiser.
I do love it on a decent Eclair build however, it does perform much smoother than my kaiser, perhaps CM6 is not quite as optimal on G1.
Battery life has stabilised a little, but in my opinion is worse than kaiser, however that may have something to do with the relative capacities of the standard batteries, that said, I have a charger at work, and I need it on occasion, and thats with the extended battery, ( my G1 is now about the same size as my kaiser, lol.
I do agree about the screen, it is larger, and more useable in bright light, the image is clear and crisp, and the surface feels nice and firm, unlike resistive touchscreens, which have a tendency to feel a little spongy.
Things I love? As I said before, google sky is to die for if you are a astronomy nerd like myself, and that uses the sensors to the maximum, just the idea of using a phone like a viewport to the stars amazes me, and it works, point it at your feet and it appears to look right through the earth.
GPS is faster to lock, but that may be due to cell tower assistance, however my favourite GPS app, (trekbuddy), has been ported to android, so I'm a happy bunny over that.
I love the new DSP additions to CM6, finally an android with real equalisation, and effects, for playing my favourite music, big bass and large room reverb has to be heard to be believed, can't wait until someone ports that to CM5, so I can have it on eclair too
My Kaiser isn't being neglected however, I am trying to keep up to date on the latest stuff, and the latest builds, however my secondary Kaiser may be getting a makeover, if I get the time it's gonna be a KaiserBot ( hint: http://www.youtube.com/watch?v=iIQ8VtDU3W8 ).
All in all, I'm lucky not to have to decide which to keep, because it would be a hard decision, both are about equal overall, the only major difference being the completeness of the android experience, g1 wins there I'm afraid, but then, it is the original Google Android Phone.
Can I recommend getting a G1? Hell yeah, If you are aware of it's potential problems it's a good replacement for a kaiser, if you demand a hardware keyboard, if you are not afraid to mess with it getting it rooted and flashable, if you know it really needs an extended battery and are prepared to put up with the added bulk, it's worth it, ( but try not to spend over £90, that'd be about my limit on it ).
Anyway, got to go flash back to my favoured eclair build, CM6 is being a memory hog again, so it's gotta go
Nice write-up Zenity, thank you for taking the time to follow this up, I will defiantly been checking ebay, but I'm even tighter then you, £50 tops ! (yes I do have lots of shoes and clothes, but I only buy in the sales and never pay over the ods).
I have been browsing the G1 Threads already, getting some information and getting a feel as to what can be done, I read what you said about reflashing the rom and came across this thread and wondered if you had seen it.
http://forum.xda-developers.com/showthread.php?t=627518
If I understand this correctly this means you don't need to install DangerSPL or anything to get a rom, if its 'shunk' down enough.
Reading though the G1 threads I wondered if there are things they are doing that could be useful for our Kiasers, aka shrinking Rom's using CACHE directory's, SWAP partitions and EXT3 (I know its not supported at the moment, but could it be?).
Is Android development done in isolation, or do devs look through different forums and use ideas from one to another? (if compatible?)
As far as DangerSPL is concerned, it is not needed if you can keep the system partition to less than 67Mb, however this pretty much restricts things, since theres only so much you can cut down before things get silly, that means on G1, Donut and maybe if you are really trimming out stuff, Eclair, forget Froyo, that's already over 90Mb, can't see how I would cut 23Mb out of that without really crippling something.
However DangerSPL is only dangerous if you go anywhere near radio, and as far as i have noticed, the minimum radio version for DangerSPL is fine anyway.
There is a certain amount of 'cross-pollination' between the devs, most tends to come our way, rather than us inspiring the 'main' android branches, however sometimes we add stuff too
As the main branch of Android customisation moves forward, so do we, just at a slightly slower pace, since in many cases it's not just as simple as copying a few files over, we have more restrictions, so we have to work harder, and smarter
Honestly, I gotta say.. the OP is right. I just recently traded my Kaiser and Rhodium for an Openmoko Neo Freerunner and a Rogers branded 911 patched HTC Dream, and the dream performs similarly to my old Kaiser....
.....until I rooted it and flashed Froyo with a kernel that allows for more that the 57some Mhz clock speed, enabled compcache and swap, and popped in an extended life battery, which incidentally makes the G1 more comfortable in my hands anyway. So now, that G1 out-performs even the Rhodium, and I just flashed the Freerunner with Froyo as well, and that's running rather smoothly too. So, all-in-all, I might have traded two awesome phones for (well, in my opinion two equally awesome phones, because I'm an OSS fanatic) two less-awesome phones, but after sinking a couple bucks and some time into them, I feel like I got a great deal.
agentfusion said:
Honestly, I gotta say.. the OP is right. I just recently traded my Kaiser and Rhodium for an Openmoko Neo Freerunner and a Rogers branded 911 patched HTC Dream, and the dream performs similarly to my old Kaiser....
.....until I rooted it and flashed Froyo with a kernel that allows for more that the 57some Mhz clock speed, enabled compcache and swap, and popped in an extended life battery, which incidentally makes the G1 more comfortable in my hands anyway. So now, that G1 out-performs even the Rhodium, and I just flashed the Freerunner with Froyo as well, and that's running rather smoothly too. So, all-in-all, I might have traded two awesome phones for (well, in my opinion two equally awesome phones, because I'm an OSS fanatic) two less-awesome phones, but after sinking a couple bucks and some time into them, I feel like I got a great deal.
Click to expand...
Click to collapse
Actually, as stock the G1 is clocked at 300Mhz or so, mainly due to the whole heat issue, (anyone who has a G1 knows what I mean, and anyone who ran early versions of android on Kaiser also knows what I mean ).
Tried various 2.2 builds, and have not really found any that compare in speed and smoothness to 2.1 builds, but as always the tradeoff is features, lower versions get less love for newer features, such as DSP.
The extended battery should be standard on G1, it really does perform badly on the standard one, I have to have 2 chargers, one at home, and one at work, and even on extended battery I find myself topping up in the afternoon.
No doubts, it is a damn good bit of kit, and as the first Android mobile it is still special, but all in all, it really isn't a great deal better than my beloved kaiser, it is better in some areas, mostly things that our kaisers either don't have, accelerometer, compass, capacitive touchscreen. And it has everything working, unless you play with less developed builds, ( Sense UI comes to mind).
I am pretty much settled with the G1 being my main phone, my Kaiser is getting used and slightly abused for experimental stuff, my secondary kais is out on loan, sold my Diamond, and the iffy HD,( it has a really weird sound issue, speaker works fine, but after boot it thinks the headset is plugged in, suspect a hardware fault), is lying on my workbench shelf.
Kaiser was my first love as far as android goes, always will be, the G1 is just a phone
zenity said:
Actually, as stock the G1 is clocked at 300Mhz or so, mainly due to the whole heat issue, (anyone who has a G1 knows what I mean, and anyone who ran early versions of android on Kaiser also knows what I mean ).
Click to expand...
Click to collapse
I know that. What I meant was that with the stock kernel the maximum you can set the clock speed to is around 576Mhz with SetCPU. What I have is an overclocking kernel that allows for over 800Mhz, but that's when it gets REALLY hot and battery drains super fast. I wouldn't suggest anything above 617Mhz though if you want it to be stable or usable.
As far as running android on Kaiser, I used that as an -almost- viable alternative to having an actual android phone. I was running android on my Kaiser from the very start of android-on-Kaiser because I'm a huge linux nerd and at&t didn't have any android phones until recently (I was just laid off from at&t in march from my middle-management position) so I definitely remember the extreme heat issues with early builds. Hell, that damn thing had such nasty heat issues that even when I was running winmo for tethering I had to take the backing off and stick thermal paste on the battery and apply a heatsink just to keep it from overheating to the point where it would stop charging completely, then discharge inside of 30 minutes from tethering on 3g.
zenity said:
Tried various 2.2 builds, and have not really found any that compare in speed and smoothness to 2.1 builds, but as always the tradeoff is features, lower versions get less love for newer features, such as DSP.
Click to expand...
Click to collapse
If you want a froyo build that's fast and smooth, try the Froyo Redux builds. They run better than any other build I've tried. Of course, I'm sticking with 2.1 at the moment for themes and absolute stability. Really, all that 2.2 has over 2.1 is native Apps2SD, and more multi-touch, but since I already have Apps2SD installed and 2.1 has MT capabilities if you force-enable it (find a version of the app you want to use MT with that someone has already patched MT into.. Brut Google Maps is a good example). As far as DSP, Meh. My Dream is a phone, not a stereo system. I applied the audio hack for louder volume and that's good enough for me.
zenity said:
The extended battery should be standard on G1, it really does perform badly on the standard one, I have to have 2 chargers, one at home, and one at work, and even on extended battery I find myself topping up in the afternoon.
Click to expand...
Click to collapse
Undoubtedly true. I have a 2200mAh battery, 2x 1400mAh, and a 1200mAh battery, and on days of heavy blogging and lots of photography, I find myself actually burning through all of them. I sometimes feel like I should be carrying a camera bag and be like the professional photographers but instead of changing rolls of film, I'm changing batteries.
zenity said:
No doubts, it is a damn good bit of kit, and as the first Android mobile it is still special, but all in all, it really isn't a great deal better than my beloved kaiser, it is better in some areas, mostly things that our kaisers either don't have, accelerometer, compass, capacitive touchscreen. And it has everything working, unless you play with less developed builds, ( Sense UI comes to mind).
I am pretty much settled with the G1 being my main phone, my Kaiser is getting used and slightly abused for experimental stuff, my secondary kais is out on loan, sold my Diamond, and the iffy HD,( it has a really weird sound issue, speaker works fine, but after boot it thinks the headset is plugged in, suspect a hardware fault), is lying on my workbench shelf.
Kaiser was my first love as far as android goes, always will be, the G1 is just a phone
Click to expand...
Click to collapse
I'm honestly more amped up about my Dream than I ever was about my Kaiser, except maybe the first time I successfully booted android via Haret. To me, the larger screen, it being capacitive, the accelerometers, and the compass are a big deal. I can actually -use- the screen for typing if I don't feel like opening the keyboard, and I can get a landscaped keyboard just by turning it sideways, and with the capacitive screen, typing is a lot more accurate and feels nicer. Standard resistive touchscreens feel kinda 'gummy' to me, and I don't like 'em. And the compass is great for photography. When you're wandering in the woods for the perfect shot, and can't remember which way is which, it can literally be a big lifesaver.
All-in-all, Once you overclock a Dream/G1 to 617Mhz or beyond and get a bigger battery (or several) it becomes a superbeast, and it's like apples and oranges when comparing it to the Kaiser. Hardware wise, it's closer to a Rhodium than a Kaiser when you get down to it. The Rhodium clock is 528Mhz, and I run my Dream well beyond that all the time.