Develop Bugs

Best Android

Hi All,
Been looking around, (ive tried android on my kaiser once), and just wondered what is the best (most stable) android for kaiser, as a lot of them seem to have a lot under "not working"?
Thanks,
Tom,

Kinda hard to answer, since no one Android build has anything working 100%.
Myn’s Warm Donut will get you most of your stuff working, but there's still a lot of bugs.
Incubus26Jc's Super Eclair is pretty good, but you lose out on Camera and Bluetooth. Less bugs then Donut, but more stable IMO.

Although Polyrhythmic hasn't updated his 2.1D for a while, I still think it's the best of the eclairs. For Donut, Myn's is really the only game in town.
Eclair is still struggling with non-working camera, but GPS , WiFi, and BT are working reasonably well, if you are prepared to invest some time into hunting out the best combination of nbh and build.
Donut is reasonably complete, I have had Myns working with WiFi, GPS and Camera, or GPS, BT and Camera, but never managed all working at once, it is the most feature-complete and arguably the most stable build of all.
Given that we have only had Android on our kaisers since the end of last year, I still think that all the devs have done a remarkable job, and development continues.
Compared to the start of the year, when all that was possible was running from SD, with battery life measured in minutes, no wifi, gps, bt or camera, I think what we have now is a complete OS, it's been my everyday phone OS now for months, and once you get into a few good habits, it's stable and smooth, with decent battery life.

Thanks for replies guys,
I have installed Myn’s Warm Donut, but it seems the graphics are a bit weird, they seem like they are the wrong bit depth or something, not quite sure how to describe it.
Any help on this please?
Thanks,
Tom

XCougar said:
Thanks for replies guys,
I have installed Myn’s Warm Donut, but it seems the graphics are a bit weird, they seem like they are the wrong bit depth or something, not quite sure how to describe it.
Any help on this please?
Thanks,
Tom
Click to expand...
Click to collapse
Q: I installed Android but now everything is blurry.
A: It's due to wrong resolution. Kaiser phones have panel for 230x320 but you're probably using 320x480 build. Here is a post by user tatnai where he explains this situation for Vogue devices (it goes same for Kaiser).
Android FAQ: http://forum.xda-developers.com/showthread.php?t=683644
Click to expand...
Click to collapse
Myn's Warm Donut is basically a scaled down version of 320x480 resolution to fit 230x320 panels, with 110 density, hence the blurriness.
One build with native 230x320 I like is vilord's Tattoo Sense, but there is a camera and BT audio not working problem in that build - hopefully incubus26jc's next release will fix this.

milanche said:
Myn's Warm Donut is basically a scaled down version of 320x480 resolution to fit 230x320 panels, with 110 density, hence the blurriness.
One build with native 230x320 I like is vilord's Tattoo Sense, but there is a camera and BT audio not working problem in that build - hopefully incubus26jc's next release will fix this.
Click to expand...
Click to collapse
vilord's Tattoo Sense sounds pretty good, and it has rosie which I'd love to see working stable. I think I'll try this on the weekend, but just wanted to know, has anyone tried this? is it stable and/or fast? Its for the touch, but as far as I've seen, vogue builds work for kaiser... would this work too?

milanche said:
Myn's Warm Donut is basically a scaled down version of 320x480 resolution to fit 230x320 panels, with 110 density, hence the blurriness.
One build with native 230x320 I like is vilord's Tattoo Sense, but there is a camera and BT audio not working problem in that build - hopefully incubus26jc's next release will fix this.
Click to expand...
Click to collapse
Hi, thanks for reply, not that I don't believe you, but its not so much blurryness, there are pink and green bits everywhere? Or is this what your describing?
Thanks again,

Oh thats because you´ve choosed a wrong paneltype. Kaiser was built with 3 different Panels so you have to choose the right one. Look at the second sticky thread.

xPreSiDenT said:
vilord's Tattoo Sense sounds pretty good, and it has rosie which I'd love to see working stable. I think I'll try this on the weekend, but just wanted to know, has anyone tried this? is it stable and/or fast? Its for the touch, but as far as I've seen, vogue builds work for kaiser... would this work too?
Click to expand...
Click to collapse
I've tried it and believe it's the best Android build so far, despite BT and Camera problem (which we should be able to fix as it is Donut 1.6 Android).
For Kaiser you should use kallt_kaffe's update to get Wifi working and it also fixes Rosie and Market.

Thanks for info.
Ok please dont flame me, ive looked around and I used to flash windows mobile all the time, but I really dont understand these nbh files.
What are they, what do they do, why are there different ones e.g voguimg.nbh and kaisimg.nbh and polimg.nbh
Thanks for your patience with me

XCougar said:
Thanks for info.
Ok please dont flame me, ive looked around and I used to flash windows mobile all the time, but I really dont understand these nbh files.
What are they, what do they do, why are there different ones e.g voguimg.nbh and kaisimg.nbh and polimg.nbh
Thanks for your patience with me
Click to expand...
Click to collapse
VOGUIMG is for Vogue devices, POLAIMG is for Polaris devices and KAISIMG is for Kaiser. Think of them as some sort of bootloaders for Android. You flash the NBH, boot to the install console, install Android from SD to NAND/SD/EXT2 and boot Android. Also you have to choose the correct panel to avoid screen problems you're having. The only way to see which panel are you using on Kaiser is to test all three of them and see which one doesn't cause you screen problems.
To test which panel you're using you should first make an SD install with Haret, there you have the option to specifiy panel type in the config file default.txt and can change this before every boot. With NAND this is hard-coded into NBH file. Later you can flash to NAND if you decide to stick with Android.
Please go thru this Q/A topic, it should help you get the answers to most of newbie-type questions.

I´m not a developer and especially on android i´m a noob but i think the NBH contains all what is going to be flashed into nand. In case of WiMo it´s the whole Operating system, somtimes with radio too. In case of android the NBH contains the Kernel only. The kernel is designed for your device with all the drivers you need (touchscreen, wifi, BT, GPS, etc.). so kernels from other devices may not work becaus of other hardware specs. in worst case it may brick your device. I read alot before i flashed my kaiser an kallt_kaffe´s kernel seems to be the best for now. Nearly all funktions are available. Only the Camera have a bug, but i think it only takes only a little time to fix this too.
I use kallt_kaffe´s kernel and Myn´s Warm Donut RLS5 and i´m totally happy with it. Fingerfriendly (you´ll never need your stylus again except for reset ^^), and much more responsive then the fastest WiMo ROMs.
You only have to modify the nbh for your panel type. But you only can do trial & error to find out which type you have.
So... happy flashing.

Thanks everyone for your help, I have the tattoo sense rom on my phone now, my phone uses panel2 type of kaiser nbh.
I now understand the nbh better.
As im more then likely going to upgrade to a newer android rom when more stable ones come out, can anyone recommend a android application that will allow me to backup my txts, emails, contacts, and settings, etc.
Thanks all

What's working better/worse after flashing to Froyo?

Wondering if I should take the plunge or not, but I'm not sure if there's good enough reason to justify doing it, or if all signs point to no.
One big thing I want is Flash support.
I'll create a list for other readers on what some of the posters have to say.
-backup programs most of them don't work yet on froyo beta
-titanium backup does work with Pauls pre-rooted version but still, the lag kind outweighs that.
-froyo beta has some performance issues
-friendster is reportedly not working properly with froyo beta
-some problems with the external sd-card in the latest froyo ROM
-flashed it for about 2 weeks on my SGS and the performance is horrid, SO many FC's and so much lag
Click to expand...
Click to collapse

backup programs most of them don't work yet on froyo beta
froyo beta has some performance issues
friendster is reportedly not working properly with froyo beta
that's what i can remember so far

I was thinking of flashing a Froyo beta but when I read that Titanium backup will not work I stopped downloading a Froyo rom...
I really need all my apps... and the thought of installing over 160 apps manually makes me &
I will wait till Titanium Backup works

Titanium backup works for me.. but there are some problems with the external sd-card in the latest froyo ROM. The external SD is write protected so if tit. backup want to restore things to the ext. sd card it cannot. You cannot even move files over from your PC to the external SD card. I found some workarounds, but none that works very smooth.

FrezoreR said:
Titanium backup works for me.. but there are some problems with the external sd-card in the latest froyo ROM. The external SD is write protected so if tit. backup want to restore things to the ext. sd card it cannot. You cannot even move files over from your PC to the external SD card. I found some workarounds, but none that works very smooth.
Click to expand...
Click to collapse
Hi... so is the external sd card useable at all?
Say if I wanted to transfer a film / music to the sd card by connecting the phone to the pc via usb cable... could I do this? Or are you saying this is not possible with the beta froyo roms?
thanks

I wouldn't reccomend the latest JP3 release of FroYo, i flashed it for about 2 weeks on my SGS and the performance is horrid, SO many FC's and so much lag i got to the point where i couldn't take it anymore so flashed back to JM5 and used Setenza's SamSet 1.9c with One Click Lagfix, now my SGS is flying!
I say don't bother with the leaked FroYo releases, wait till Samsung releases the final versions and wait till there is more support from other devs here but still, it was nice and some visual stuff was changed plus Flash was good, otherwise i don't really miss it. Also as stated above, the SD Card error was crap, you cannot use your EXT SD Card if you connect it to your PC (meaning you can't write files to it) so that's pointless, it comes up with protected error. so flashing back to JM5 fixed that!

MAMBO04 said:
I wouldn't reccomend the latest JP3 release of FroYo, i flashed it for about 2 weeks on my SGS and the performance is horrid, SO many FC's and so much lag i got to the point where i couldn't take it anymore so flashed back to JM5 and used Setenza's SamSet 1.9c with One Click Lagfix, now my SGS is flying!
I say don't bother with the leaked FroYo releases, wait till Samsung releases the final versions and wait till there is more support from other devs here but still, it was nice and some visual stuff was changed plus Flash was good, otherwise i don't really miss it. Also as stated above, the SD Card error was crap, you cannot use your EXT SD Card if you connect it to your PC (meaning you can't write files to it) so that's pointless, it comes up with protected error. so flashing back to JM5 fixed that!
Click to expand...
Click to collapse
Hey mate. Thank you so much for replying. Great post! I will hold off from flashing a froyo release and stick to Samset 1.9C.
Cheers buddy

Titanium Backup works indeed in Froyo JP1, JP2 and pre-rooted JP3 by paul from modaco

jUsT2eXy said:
Hey mate. Thank you so much for replying. Great post! I will hold off from flashing a froyo release and stick to Samset 1.9C.
Cheers buddy
Click to expand...
Click to collapse
No worries mate and yeah titanium backup does work with Pauls pre-rooted version but still, the lag kind outweighs that.

I've been running Paul's rooted JP3 as my day-to-day ROM and - for my usage - it's very stable.
There is a trick to getting the stability (credit to whomever first did this, I just copied) - you need to edit your /system/build.prop and turn off JIT. The phone is much more stable after that, and browsing is still fast etc, I'm not that bothered by benchmarks myself. No real lag to speak of although probably not performing as well as my previous JG5+lagfix
Here's the relevant lines of my build.prop:
dalvik.vm.heapsize=24m
dalvik.vm.execution-mode=int:fast
Click to expand...
Click to collapse
Really annoying bugs:
1. GPS is still buggy, and the special code to put into dialer does not work on JP3
2. Viewing tabs in the browser results in a FC more often than not
3. When mounted to a PC the external SD is read-only
Things I like:
1. PIN code rather than pattern unlock as an option
2. Better memory management. No need for a task killer (though Samsung now include one in JP3)
3. Google search (on the phone itself) seems quicker and more useful
4. The culmination of lots of little things - the Market App comments, one checkbox to toggle mobile data, more voice recogniser languages
So, it is pretty borderline and if I'm honest it's not that different from an Eclair+lagfix. I primarily use it for Google services, twitter, and as a phone, so things like Asphalt not installing don't bother me.

On JP3 Froyo I couldn't get the following apps to work:
Googly Sky Maps
Aldiko eBook reader
The following apps were very unstable and prone to frequent crashes not present in builds of 2.1:
VLC Remote
ACV (Android Comic Viewer)
Skyfire

bogeyface said:
On JP3 Froyo I couldn't get the following apps to work:
Googly Sky Maps
Aldiko eBook reader
The following apps were very unstable and prone to frequent crashes not present in builds of 2.1:
VLC Remote
ACV (Android Comic Viewer)
Skyfire
Click to expand...
Click to collapse
I have no problems at all with google sky map. I have further more not had an application that did not work on JP3 yet. As far as stable goes I have had none problems with stability. I have applied lag fix, so everything is flying. Get a score of 1800+ with quadrant, froyo roms gets lower scores.
Sent from my GT-I9000 using XDA App

I don't know if anybody else noticed this, but my 3G data connection was woeful on JP3. It would frequently drop out and/or only be connected for a few seconds out of every few minutes. However it would still send data, which is still counted against my cap...

You have to understand that there is a reason why Samsung are releasing Froyo at the end of September, it takes time to optimize and debug everything that's new and retrofit the old stuff.

Well i do agree that some aspects were better, including animations, the pre-release of Froyo is still not stable IMHO, sure you can apply the new CFlagfix but Eclair atm runs much better than Froyo, there is a huge difference between the performance of both on our phones right now cause Froyo is in pre-release stage. When i flashed back to 2.1 my SGS works flawlessly now, evenn GPS, so no issues there. But GPS did work fine in Froyo, i did a whole 2 hour car journey (each way) and was awesome, there were some random drops and on the way back my phone was being so slow and difficult the GPS just wasn't getting a position. But yeah, if it works out for you, stay with JP3, or just go back to Eclair

- camera panorama doesn't work and many other things in camera
- clock delays

BlazerRazor said:
I have no problems at all with google sky map. I have further more not had an application that did not work on JP3 yet. As far as stable goes I have had none problems with stability. I have applied lag fix, so everything is flying. Get a score of 1800+ with quadrant, froyo roms gets lower scores.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
I just tried downloading and installing Google Sky Maps from Market and it failed. JP3 (Pauls's pre-rooted version r2).
I'm considering going to SamSet's JP2 Froyo which I think has less issues, not sure

After reading this I might flash to Samsets 2.1.
2.2 Is very unstable. I get constant crashes on my apps. I don't find any lag generally but the instability of apps is terrible (yes, I understand, its a pre-release!).
However I am enjoying flash! But Skyfire does the job (+ possibly better!).

BlazerRazor said:
I have no problems at all with google sky map. I have further more not had an application that did not work on JP3 yet. As far as stable goes I have had none problems with stability. I have applied lag fix, so everything is flying. Get a score of 1800+ with quadrant, froyo roms gets lower scores.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
same here... i've been using it for 2 weeks and with the lagfix it works great

Mobile AP is broken in JP3 too..
Anyway, the only thing better in JP3 at the moment is the new API's, which you possibly wont use anyway.

[ROM] AOSP rom from vibrant forum (by eugene373 et al.)

hi! like many of you i have been waiting for a clean aosp rom and it looks like we get some first taste of the forbidden fruit there. i found the following in the vibrant forums:
http://forum.xda-developers.com/showthread.php?t=757000
remember it's for the vibrant and it's alpha (no radio & other things) but i guess it should work for the i9000 as well. it's just a start but finally things are happening . i will give it a try shortly
thanks to eugene, barak and possible others i don't know of!

just flashed it and played a little bit and here is my report:
* wlan works but is slower than stock
* calling works but 3g-data doesn't
* camera doesn't work
i didn't test:
* bluetooth
* gps
everything else seems to work and is quite smooth!
quadrant-score: 859, 875, 845
very nice work for an alpha version! i'm quite excited for what's to come
edit:
* after sync and reboot wlan seems to be as fast as normal...maybe my isp f***** up (again).
* after moving /data/data to /dbdata/data (dbdata is not used by this rom) this thing is FLYING!
* everything seems stable so far
i think i will keep this for now even if data is not working. awesome experience to have stock android (again)!

Very nice to see a asop on the way. Lets hope some I9000 dev have the time to adapt this for galaxy

DocRambone said:
Very nice to see a asop on the way. Lets hope some I9000 dev have the time to adapt this for galaxy
Click to expand...
Click to collapse
after playing around with this i think there won't be a lot we have to change! just the kernel and the modules (i still use the JM2 kernel/zImage) and that's easy to adapt...

jodue said:
after playing around with this i think there won't be a lot we have to change! just the kernel and the modules (i still use the JM2 kernel/zImage) and that's easy to adapt...
Click to expand...
Click to collapse
How did you install this asop rom?
I guess some files mods are needed? Build.prop etc?

DocRambone said:
How did you install this asop rom?
I guess some files mods are needed? Build.prop etc?
Click to expand...
Click to collapse
nope. just flash the zip with clockwork over an existing firmware (in my case JM2). first boot will take a littel longer because of odex-ing.

Great to see some work on AOSP for the Galaxy S series. I've been surprised that no-one's done anything on it before, but confident that if the right people turned their minds to it they'd be able to get it running (even if all the drivers aren't sorted at first).
I don't really have a problem with TouchWiz, considering that I'm actually using LauncherPro and like the notification bar toggles etc. However, AOSP builds make me confident we'll see Gingerbread (and beyond?) because we won't have to depend on Samsung.

Wow, this is good news! I'm looking forward to having a stock Android. Although I want to try Sense more!
Im guessing once this becomes more stable, Sense is not far off?

wow, very good news.... when 3g-data will be fixed, surely i'll try this, even if i like touchwiz, i think that the sgs will be smoother without it....
hoping also in a AOSP FROYO ROM

report after ~17h use:
* gps doesn't work
* wlan works well and fast (i had 18-19mbit before with speedtest.net, same as my pc) but the driver seems to have some stability problems when it's idle for some time...
* short radio problem before, restart fixed it so radio probably is a little instable in the long run as well
quadrant scores of ~950 but linpack of only ~6.5MFLOPS? strange! everything is running very very fast and responsive (only fix aplied is: moved /data/data on /dbdata/data) and it boots faster. both definitely better than stock!
i am wondering why almost nobody seems to be interested in this. i had the feeling that more people wanted an aosp rom since we had a thread about that almost ever 2-3 days ...

I tried this asop for few hours: slower than best sgs rom's , no data connection, wifi slow, some app errors. Still not good enough for daily use but a very promising start.

Sounds really great, but I'm on JP3 right now and it seems to have less bugs than this :-/

This is only an alpha. I'll be more inclined to test when its in beta, as will many others I think. Especially as there are some troubles with core drivers.

Does this already run on a different file system (instead of RFS)? If not, will it be possible in the future to do so?

nrg said:
Does this already run on a different file system (instead of RFS)? If not, will it be possible in the future to do so?
Click to expand...
Click to collapse
no, it does not repartition anything.
yes, if you repartition the nand and have a kernel with e.g. yaffs2 support.
should both be possible atm with some effort...

i'm really interested,although Wiz notification bar is handy (but i could manage with standard power control widget)...i'm not able to program or do other too technical stuff,but i'd be happy to check for bugs (when it'll become a little more usable,i'm on h3g and i absolutely need 3g )

yeah, they are working on it and will soon release the source on github. i use it for almost 2 days now and except the missing data it's working fine for me. really fast and sleek. i guess that we will soon have a beta version with most of the stuff working....i think it's just amazing that this rom is only about half the size of the samsung firmware even with gapps!
although i like stock android more 2 things i already miss are the notification bar and the movie player which can play so many more formats than the stock one, but thats a small price to pay.

Can't the .apk's be ripped and installed anyway? I'm looking forward to try this when data is working!
Is this 2.1 or 2.2?

khsbenny said:
Can't the .apk's be ripped and installed anyway? I'm looking forward to try this when data is working!
Is this 2.1 or 2.2?
Click to expand...
Click to collapse
it's 2.1
hm. the apps could probably be ported but it would be more complicated than installing the apk. they rely on libraries, the custom ui stuff and probably other apps like content providers etc. the only thing i REALLY want is the movie player! it's just very comfortable to just copy some movies/series onto the device before a train ride without the need to transcode

jodue said:
i am wondering why almost nobody seems to be interested in this. i had the feeling that more people wanted an aosp rom since we had a thread about that almost ever 2-3 days ...
Click to expand...
Click to collapse
Interested, yea. As in "interesting to follow and see if it becomes functional." At the moment it's an alpha with no 3g data, wifi issues, bluetooth issues, no camera, and no GPS.
What more do you expect with it in its current state? Sheesh.

current differences between xdandroid and neopeek?

Hello, I am wondering, what are the current differences between xdandroid and neopeek for the rhodium?
Which one has better functionality? Which one has better battery life? Which one performs better and faster? And which one is more stable?

Eh those are all so subjective. Run 'em both for yourself, and draw your own conclusions.
With that said, the main difference is Neo is using cyanogenmod's stuff as the guts, and then breaking as much as he can out onto a separate ext2 partition - so his builds are a little trickier to setup, you have to partition your SD card to accomodate an ext2 partiton as well as a fat32 partition.

You can also run both versions on one card for testing. Just setup the Neo partitions first.

liveordie56 said:
Hello, I am wondering, what are the current differences between xdandroid and neopeek for the rhodium?
Which one has better functionality? Which one has better battery life? Which one performs better and faster? And which one is more stable?
Click to expand...
Click to collapse
Not sure why but neopeek's marketplace will let you download secure/encrypted market items so you will get more stuff in the market than xandroid. But with that said I always had issues with data either not working or going very slow a long with wifi issues and lots of things crashing nostop using neopeek.

Xandroid is nice and easy to setup and run... it works well but I've noticed that its a bit slow for me. Usually the items that work (wifi, bt, audio, ect...) typically work first on xandroid then become available within a week or so on Neopeek roms.
Neopeek is a bit trickier to set up and requires the ext2 partition that everyone before me mentioned. Once you do it once though, its pretty straight forward to use. There are several builds of neopeek roms (Superfroyo, Froyoredux, CM6 mods, ect) In my experience, Neopeek roms are more stable and have somewhat better battery life (especially the latest superfroyo).
From my experience, the same kinds of glitches show in both, data randomly not working, in call volume issues, low signal (or at least poor signal indication), the phone radio getting glitched, ect.
On neopeek builds, I have noticed that some roms have never ending android process crashes and random reboots. I have noticed that formatting the ext2 partition and then running mkfs.ext2 /dev/SDCardIdentifier seems to be a good idea when switching builds of a rom and seems to alleviate this issue. The latest version of SuperFroyo is working awesome, I have not had a single crash or anything.
Also, frequently updated is the glemsom builds of kernel and module files (found in a link below). These also may change your stability/functionality. for example. in the latest build of SuperFroyo (the build i typically hold my breath for) I could not get past the initial device setup (Android setup wizard) updating the kernel to the one that was latest at the time fixed my issue.
Also, Neopeek wireless for Rhodium is not necessarily finished although I have found a fix for it which I will post in a new thread for everyone to find.
Overall, Neopeek I Choose You!
Glesmom Link : http://glemsom.users.anapnea.net/android2/htc-msm-linux/

RickoT said:
Xandroid is nice and easy to setup and run... it works well but I've noticed that its a bit slow for me. Usually the items that work (wifi, bt, audio, ect...) typically work first on xandroid then become available within a week or so on Neopeek roms.
Neopeek is a bit trickier to set up and requires the ext2 partition that everyone before me mentioned. Once you do it once though, its pretty straight forward to use. There are several builds of neopeek roms (Superfroyo, Froyoredux, CM6 mods, ect) In my experience, Neopeek roms are more stable and have somewhat better battery life (especially the latest superfroyo).
From my experience, the same kinds of glitches show in both, data randomly not working, in call volume issues, low signal (or at least poor signal indication), the phone radio getting glitched, ect.
On neopeek builds, I have noticed that some roms have never ending android process crashes and random reboots. I have noticed that formatting the ext2 partition and then running mkfs.ext2 /dev/SDCardIdentifier seems to be a good idea when switching builds of a rom and seems to alleviate this issue. The latest version of SuperFroyo is working awesome, I have not had a single crash or anything.
Also, frequently updated is the glemsom builds of kernel and module files (found in a link below). These also may change your stability/functionality. for example. in the latest build of SuperFroyo (the build i typically hold my breath for) I could not get past the initial device setup (Android setup wizard) updating the kernel to the one that was latest at the time fixed my issue.
Also, Neopeek wireless for Rhodium is not necessarily finished although I have found a fix for it which I will post in a new thread for everyone to find.
Overall, Neopeek I Choose You!
Glesmom Link : http://glemsom.users.anapnea.net/android2/htc-msm-linux/
Click to expand...
Click to collapse
okay, thanks i think i have decided to go with the neopeek build's i have a question for you though, on the latest SuperF build (on neopeek's forum October 8, 2010) My data stops working after a call. did you run across this problem? I updated to the latest kernel too and it still did not fix the problem.

Are you on edge? That would disconnect data during a call... it should reconnect though when you are done

hmm it says 3g on android, but when i end the call and my friend tries to call again, it never reaches, and when i try to call, there's no ringing or anything, along with that, when i press hang up, it is stuck on "hanging up".

Yah I get that too sometimes (on xandroid and neopeek) I think its more of a general radio driver issue/radio image than the build honestly... dont forget that this radio was meant to be used with windows mobile not android.

ahhhhh, okay thanks for the information

wondering?
Is there any progress on a camera fix yet?

There will be fanfare and confetti all over the forums when camera works.
Seriously, you will know when it's working. It's not yet.

camera .. yuck..

[Q] Which version should i use? (Not asking which rom is better)

Hello guys! I need your help and advise.
I need to use my kaiser to work. That's uhh.. receiving calls, making calls, sms, WiFi @ night to sync new contacts to my Google account... you know, small tasks.
I'm using as of yet CM7 with 2.3.32 (#63 IIRC) Data on SD Partition. Now.. although stable (no reboots, no crashes... seems OK) Its painfully slow.
If someone calls me, i have to wait about 7 ringtones before i know who's calling me. So.. i need your advise! Should i use a Donut ? perhaps a 2.6.25 ?
Please be honest, state your opinion and its basis
UPDATE 20110304:
I'm using as of yet:
VaniljEclair RLS11 - A fast & stable CM 5.0.8 for Vogue/Kaiser/Polaris [2010-08-19]
Battery rocks (i'm using a 2.8Ah).
Calls work pefectly.
SMS's work perfectly
Some apps apear to have a .... strange issue. They simply... don't open. But thats temporary. And a reboot fixes.
WiFi works (using latest from liquid with module update).
Quite happy
UPDATE 20110306:
Still no issues. One thing is granted, when i turn the WiFi on and let it sync... bogs down considerably. OC via atools to 490.
Will try the other option now, incubus26c's versions.
UPDATE 20110309:
Using incubus26c's with kernel .25 downloaded and edited through atools.
Been sufering from random phone problems. Simply shutdown. Cannot enable AirPlane mode. Have to reboot.
BTW, anyone has any other sugestions about roms ??
UPDATE 20110310:
Noted that my hardware keyb is sometimes eating letters... notably.. space.
Will check settings to see if disabling something helps.

Try using builds like those by incubus26c's or VaniljEclair. I've had both and enjoyed them greatly, going back to WM for the only reasons of better camera (autofocus never worked on droid for Kaiser) and ad-hoc WiFi support.
And... a few tips.
1. Use phone prioritizer (probably in VanilJEclair). This cuts delay between calling and receiving a call by two times.
2. Odexed firmware is faster, than deodexed. Yeah, no themes anymore, but you want a working device, not a box for bells and whistles, aintcha?
3. 2.6.25 is still up to date. Sometimes you'll need a patch to make wifi work, but that is a reasonable price for better speed.
What about donut? No, it is not faster then any 2.x droids.

StripezZ said:
Try using builds like those by incubus26c's or VaniljEclair. I've had both and enjoyed them greatly, going back to WM for the only reasons of better camera (autofocus never worked on droid for Kaiser) and ad-hoc WiFi support.
And... a few tips.
1. Use phone prioritizer (probably in VanilJEclair). This cuts delay between calling and receiving a call by two times.
2. Odexed firmware is faster, than deodexed. Yeah, no themes anymore, but you want a working device, not a box for bells and whistles, aintcha?
3. 2.6.25 is still up to date. Sometimes you'll need a patch to make wifi work, but that is a reasonable price for better speed.
What about donut? No, it is not faster then any 2.x droids.
Click to expand...
Click to collapse
Clear enough.
Will report back with more info
Thank you

1st Post updated.

And again.

Still no issues. One thing is granted, when i turn the WiFi on and let it sync... bogs down considerably. OC via atools to 490.
1. get RogueTools from Market to overclock the device without atools
2. a question from my side: are Gingerbones worth it?

I actually used and tweaked a Gingerbones. Was quite good, not as fast of course, but then again, more eye candy.
I'm not getting any instability, just plain ... slow during sync. But this as been a standard with any version i've tested.

wifi sync lagging seems to be quite common for all low-end droids, both native and cooked. As long as it happens mostly with encrypted networks, i would suppose the reason is some sort of cryptographic calculations MSM72xx delegates to CPU.
Though, since all unsecured networks I encountered were very slow (256k or so), there's a chance the lag nests in higher bandwidth, causing data to be downloaded a bit too fast to be processed - sometimes HSDPA connection makes the gadget lag, too.

daedric said:
UPDATE 20110310:
Noted that my hardware keyb is sometimes eating letters... notably.. space.
Will check settings to see if disabling something helps.
Click to expand...
Click to collapse
There is strange polling behavior with hardware keyboard on 2.6.25
Though I love stability in 2.6.25 kernel, the Eating of Space button is quiet frustrating when I am texting my boss :| (which I often do) and I press Enter to send right away (just as I am chatting).

StripezZ said:
wifi sync lagging seems to be quite common for all low-end droids, both native and cooked. As long as it happens mostly with encrypted networks, i would suppose the reason is some sort of cryptographic calculations MSM72xx delegates to CPU.
Though, since all unsecured networks I encountered were very slow (256k or so), there's a chance the lag nests in higher bandwidth, causing data to be downloaded a bit too fast to be processed - sometimes HSDPA connection makes the gadget lag, too.
Click to expand...
Click to collapse
So... if the massive slow(ness?? is this a word??) is coming for a bogged CPU on SSL encode/decode, we could... say... use OsMonitor to check?
Which process should be giving lots of CPU usage ?? Android System ?

dark_prince said:
There is strange polling behavior with hardware keyboard on 2.6.25
Though I love stability in 2.6.25 kernel, the Eating of Space button is quiet frustrating when I am texting my boss :| (which I often do) and I press Enter to send right away (just as I am chatting).
Click to expand...
Click to collapse
So... perhaps moving to 2.6.32 should provide me with it a better keyboard polling, at a stability price ??
P.S.
Anyone else would like to suggest another rom ?? BTW... i'm going to try and strip a gingerbones (by Aceyome if i remember his nick right) to gain extra stability.

I think yes. Though I have used .32 kernel for so less time than .25 so as I need the Mass storage functionality, which works perfect with dual mount on .25 kernel. Try Fat Free Froyo by thoughtlesskyle, if you really want a vanilla build

dark_prince said:
I think yes. Though I have used .32 kernel for so less time than .25 so as I need the Mass storage functionality, which works perfect with dual mount on .25 kernel. Try Fat Free Froyo by thoughtlesskyle, if you really want a vanilla build
Click to expand...
Click to collapse
Hey dark_prince, OFF TOPIC question:
How is the Froyo 2.2 x86 ?

daedric said:
Hey dark_prince, OFF TOPIC question:
How is the Froyo 2.2 x86 ?
Click to expand...
Click to collapse
Still not to be used as Primary OS. Alot of things don't work and force close on my D420. Though x86 build works pitch perfect with an EEEPC. It's blazing fast and stripped down to just 80MB and has Hardware OpenGL ES support for intel 915,945,965 chipsets. 1280x800 isnt supported fully as of yet (You can run HDPI one). Market doesnt work, but a proprietary App downloader is provided. Also, keyboard works perfect and mouse emulation is nice. Ethernet + Wifi support depends if kernel supports.

Why doesn't the market work??
(market! y u no work?)

daedric said:
Why doesn't the market work??
(market! y u no work?)
Click to expand...
Click to collapse
It crashes randomly with the build, thats why it was removed. But there is another handy app installer which comes with every x86 build