Related
mssmison's Eclair V7 Updated 03-25
http://forum.xda-developers.com/showthread.php?t=643045
or
polymod 2.1g Full Market Update 23 Mar!!
http://forum.xda-developers.com/showthread.php?t=600154
Warm Donut version
Yes, I would like to know which is more popular for the Kaiser is well. Between polymod, mssmison, warm donut or something else...
pentagramII said:
Warm Donut version
Click to expand...
Click to collapse
mee too
Interesting, pretty much even 2-2-2-1.
I have yet to find a version that wifi worked.
hoatienii said:
mee too
Click to expand...
Click to collapse
I removed that option because it's an older version of android, which should work even better.
I just tried both versions (on zImage 23-03) with 2 ext2 partitions, mssmison is much faster all the time after a few boots (but can't get wifi to work (zImage 23-03), so I guess I will be using windows mobile for a while).
I use Polymod 2.1g on SDCard.
But mssmison's Eclair is faster and could be best if have working WiFi.
I not use NAND because i wish have "dualsystem" phone
Warm Donut version - best!
WarmDonut is much faster and very stable but as I get no cellular data it's not very useful.
Amaranthus said:
WarmDonut is much faster and very stable but as I get no cellular data it's not very useful.
Click to expand...
Click to collapse
Weird I use warmdonut also (Which I find to be the fastest) and my cellular data works perfectly. Sometimes I won't be able to use it and then that's when I restart.
DmK75 said:
I use Polymod 2.1g on SDCard.
But mssmison's Eclair is faster and could be best if have working WiFi.
I not use NAND because i wish have "dualsystem" phone
Click to expand...
Click to collapse
wifi works on mssmision using BT-fix from poly (and maybe other updates, look at another thread http://forum.xda-developers.com/showthread.php?t=653871
mssmison**********************
mssmison's version is super fast.
clean and looks good
stable out the gate.
except for:
not sure why but anything having to do with gps locks up the phone and it reboots to bootanimation. even if gps is off, any app that i use will lockup.
nothing is mentioned on mssmison's thread. so I am assuming it to be kaiser related.
btw I am using nhb, bt-patch and wifi fix from polymod's.
polymod***************
with polymod I get random results with out the gate stability.
usually following the installing tips from his OP works pretty good.
while the latest version is way faster than previous builds it still has
glitchy graphics and becomes bogged down easily compared to mssmison's, slm's kaiserdroid or myn donut.
but overall if installed good, it is pretty stable and looks and works nice.
Can you use 2 folders andboot and andboot2 (with same files except androidinstaller) on root SD card or must all files be in /andboot?
edit: only when using .img and together ext2 method.
First I tried mssmison, it was very fast but WiFi didn't work for sure, I don't have anything BT except for kaiser so I didn't install BT-fix. But I don't remember for sure but 3G might have not worked for me.
Polymod is slow, but other than that I have no issues with it. It catches WiFi, even adhoc(which G1 of my brother isn't capable of without playing around with some crazy files). On polymod USB doesn't work though, so it's little irritating to access memory card. Is there any build that has USB support?
Areinu said:
First I tried mssmison, it was very fast but WiFi didn't work for sure, I don't have anything BT except for kaiser so I didn't install BT-fix. But I don't remember for sure but 3G might have not worked for me.
Polymod is slow, but other than that I have no issues with it. It catches WiFi, even adhoc(which G1 of my brother isn't capable of without playing around with some crazy files). On polymod USB doesn't work though, so it's little irritating to access memory card. Is there any build that has USB support?
Click to expand...
Click to collapse
use another kernel (zimage).
wifi works
I prefer warm donut. Faster than the others, and I was able to get wifi working. Check out Warm Donuts thread. WifiRL_110 works for the kaiser. It's been running great.
Afraid I'm another donut fan - wifi and bt are working now and even from sd card via haret it's fast!
If I could find a droid with a working way to disable 3g then i'd move from windows and flash it
The new build of msssison contains a lott of bugs, better use polymod 2.1d
Both are still slow (using gmail takes 4-5secs)
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
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..
Alright, guys. I've been searching for an answer to this problem for about 2 weeks now and I can't find a great answer.
I converted my AT&T Tilt to Android successfully and I've been trying out a series of different ROMs to find the one that works the best for me. Currently, I am running 2.6.32_VOGUIMG-320-FROYO-01-16-11.NBH from l1q1d with barebones 5.1. However, I have tryied Incubus's Super Froyo, Myn's Warm Donut, etc. I've been very happy with most of the builds; however, I have problems playing video in every single release of Android that I have tried. This includes through Android's included movie player, Meridian, and the youtube app. I am using panel type 2 when I reconfigure the kernal using atools. I don't know if this is the correct panel type, as I don't know how to figure out which one I have. I don't know if this makes a difference for video.
Does anyone have any suggestions about how I could get video working in Android on my phone? It's the last missing link in getting my phone to work the way I want. Thanks.
Seriously. No one else has experienced this problem? I've literally spent hours searching XDA trying to find a solution.
Youtube works on mine... tell you what. Flash the nbh with panel type 1.
Even if you get screen artifacts, or other issues, try the video. If you can play, then you've isolated the problem to the panel type. If not... oh well.
I'll try meridian and see what i get.
Just out of curiosity, I tried flashing it with all three different panel types; same results. I have overclocked to 520 mhz; would this cause any problems? Every other program seems to work fine. I'm honestly baffled.
Via Atools or RogueTools ?
Via atools. Thanks.
Do not OC via Atools. Might not have nothing to do with it, but RogueTools seems MUCH more stable. Just and advice
Removing the overclocking from atools has not made any difference. Thanks for the suggestion, though.
Same problem. I managed to play some videos with poor quality, so maybe this is a performance related problem.
Looks like it's back to WM for me. The lack of video is a dealbreaker for me. Sorry that you're having the same issue, sloikas. Windows plays everything I've thrown at it.
Back to the dark ages on our kaisers lol? What may be affecting your video playback is the radio rom. It actually contains a little more than the radio and in my experience can affect playback of videos. Also if your trying to stream over edge, good luck with that. Over wifi I have next to no issues with Barebones 4.55, overclocked to 575 mhz and on wifi.
Thanks for the reply. Just out of curiosity, I tried three different radios: 1.70.18.02, 1.70.19.09, and 1.71.09.01. Same results with each of them. I don't have a data connection with my phone, so I am only using wifi. I have also tried to play MP4's on my SD card.
Video is supposed to be working. How exactly do you have it set up atm?
erickrause01 said:
Alright, guys. I've been searching for an answer to this problem for about 2 weeks now and I can't find a great answer.
I converted my AT&T Tilt to Android successfully and I've been trying out a series of different ROMs to find the one that works the best for me. Currently, I am running 2.6.32_VOGUIMG-320-FROYO-01-16-11.NBH from l1q1d with barebones 5.1. However, I have tryied Incubus's Super Froyo, Myn's Warm Donut, etc. I've been very happy with most of the builds; however, I have problems playing video in every single release of Android that I have tried. This includes through Android's included movie player, Meridian, and the youtube app. I am using panel type 2 when I reconfigure the kernal using atools. I don't know if this is the correct panel type, as I don't know how to figure out which one I have. I don't know if this makes a difference for video.
Does anyone have any suggestions about how I could get video working in Android on my phone? It's the last missing link in getting my phone to work the way I want. Thanks.
Click to expand...
Click to collapse
use KAISIMG, And mind that you need a corresponding kernel. Atools is creating problems for me in editing the kernels. I suggest you try a stock kernel with respective build. (FROYO kernel for FROYO, Eclair kernel for Eclair and Donut's for Donut). So far, Meridian is the best media player for me and I am using it on Donut (Warbyte's or Myn's ? your choice).
To check which panel type is nice and good is to check your SCREEN's colours. Are they perfect? is Touchscreen working good? and is brightness set good. First thing you notice after flashing wrong panel type is colours. Deformed Colours, usually u see each pixel as showing rainbows.
Flash a KAISIMG kernel I say and do not play with them on Atools / iHex or what so ever.
For instance try this,
http://phobos-lab.net/android/Warbyte Donut RLS04.zip
kernel is included and panel type is set to 1, Device keyboard is set to HTC Kaiser default. I say use iHex to edit the nbh for your suited panel type/keyboard.
Installing Data on SD Card can cause browsers to malfunction and almost Force Close on anything. Try installing on NAND (both SYS and DATA)
erickrause01 said:
Alright, guys. I've been searching for an answer to this problem for about 2 weeks now and I can't find a great answer.
I converted my AT&T Tilt to Android successfully and I've been trying out a series of different ROMs to find the one that works the best for me. Currently, I am running 2.6.32_VOGUIMG-320-FROYO-01-16-11.NBH from l1q1d with barebones 5.1. However, I have tryied Incubus's Super Froyo, Myn's Warm Donut, etc. I've been very happy with most of the builds; however, I have problems playing video in every single release of Android that I have tried. This includes through Android's included movie player, Meridian, and the youtube app. I am using panel type 2 when I reconfigure the kernal using atools. I don't know if this is the correct panel type, as I don't know how to figure out which one I have. I don't know if this makes a difference for video.
Does anyone have any suggestions about how I could get video working in Android on my phone? It's the last missing link in getting my phone to work the way I want. Thanks.
Click to expand...
Click to collapse
To play video, convert your clips/video to mp4 and use yxplayer to play them. This was the only working solution for video issues for me. Now I can play any video as long as it's in mp4 format and i'm using yxplayer to play it.
About youtube...are you on WIFI or mobile net? Youtube on wifi defaults to HQ video which our kaisers cannot play for some reason. Solution use 3G/H or if you're on wifi .......when the clip is loading click a HQ icon on the screen it should be in the right upper corner on the screen(depending on youtube app. version) that should load LQ/MQ version which plays fine on kaiser.
Thanks so much to dark_prince. His instructions worked perfectly for me. I now have a perfectly working (for me) Android phone. Awesome! Thanks to all that tried to assist.
Was just curious as to what build you were using. It basically sounded like he said to use a vanilla build with atools edit'd for whatever build you are going to use. I hate Donut just due to how old and slow it is. I do not think the build you are using matters, it sounds like you had a kernel configuration problem if it is now working.
erickrause01 said:
Thanks so much to dark_prince. His instructions worked perfectly for me. I now have a perfectly working (for me) Android phone. Awesome! Thanks to all that tried to assist.
Click to expand...
Click to collapse
I am glad that I was of to good use for humanity.
Cheers mate
aceoyame said:
Was just curious as to what build you were using. It basically sounded like he said to use a vanilla build with atools edit'd for whatever build you are going to use. I hate Donut just due to how old and slow it is. I do not think the build you are using matters, it sounds like you had a kernel configuration problem if it is now working.
Click to expand...
Click to collapse
for OLD I might agree. But for SLOW I wont ever. Donut is far far far far far far better than those eclairs or froyos out there. Particularly when my battery lasts for a day on Eclair / Froyo, it lasts for almost 48 hours crisp while using Donut. So please sir...
Well its like I said before, it is really the kernel that is making battery last longer. My barebones with a proper .32 kernel (Still waiting for clemsyn's .32 to be committed to git) and stock speeds is plenty fast and gets almost equal battery with more features and apps. I of course could overclock it but that drops battery to around a day which is more than adequate.
video doesn't work for me either....
I have VOGUIMG-320-FROYO-01-16-11 changed to kaiser and to panel 2 with atools... CM 6.1 barebones build both sys and data on nand... and is working really fine ( is the only one i've tried... )
already installed meridian and rockplayerbass the best i could get was with rockplayerbass with software render but the image was very ver slow... =(
erickrause01 , did you installed only kernel or entire build that dark_prince advised? and did you changed panel? what is the difference to change panel with atools and ihex? ( dunno how to use it ;P but if necessary will learn...
If only the kernel is needed to be changed, if i install new kernel do my installed build be ok or the process is re-installing kernel and then build again? i'm still with this doubt...
I would like to stay with this build because almost everything is running fine... little by little i'm getting my android to "perfection" hehe although some apps aren't working i'm finding solutions for almost everything.. video and camera is not one of that .. yet ;P
sorry for the bad english ;P
edit: when installing kernel i've changed name to KAISIMG
edit2: build is Scoot CyanogenMod 6.1 RLS5.5 not barebones....
Hey folks,
This is a completely new build, with all the new changes baked in. We wanted to do a semi-official test release to collect bugs and hopefully do a formal official release with everything settled. The main pain point is the CSV files (see pre-install prep).
So a brief overview:
New acoustic routing code baked in. Should fix most if not all audio routing problems, and will provide more debugging if stuff does go wrong. Also allows for more granular tweaking, see the CSV files.
GPS fixes for GB - GPS not only works in GB now, but it doesn't kill sleep! I was able to use GPS, get a solid lock, and put the device to sleep no problem.
BT should work & well with the new acoustic code. Post results.
RHOD users now have a choice of kernels. .35+ all have the new acoustic - so .35, .39, 3.0 and 3.1 are all fair game now... This is bundled with .27!!
Keep in mind, autobuild .27 kernels will produce no audio in this build... Obviously the bundled kernel will work, and the absolute newest .27 autobuild kernel does work now - Feb.27 2012 or newer.
rootfs tweaks - first, it will detect which kernel you're on (.27 or .35+) and automatically apply the correct firmware. Second, is it will always copy/extract the modules... failures there were getting annoying, and this is surefire if brute-force...
Few Easter egg apk's...
Probably a lot I'm forgetting, this might change
Pre-Install Prep REQUIRED!!!
This step is crucial, and I forgot all about it! You must copy all of the *.CSV file from your WinMo ROM - these are in the \Windows\ directory. There's a very easy way to do this. It involves the Total Commander app for WinMo (Direct Link for the perpetually lazy...) (included in EnergyROM and others probably).
Now you're in Total Commander looking at your \Windows\ directory. Whew... lots of files. Fear not! Hit the "CTRL" button, then the green "Plus" button. This opens the Select/Unselect files dialog. Put in *.csv, press "select" and voila. All CSV files are selected. Now - File -> Copy/Move -> I want you to copy these (should be 10) files to the ROOT of your SD card. No folders!!! This is hardset right now, until we get it all implemented into the build properly. Thanks!
Install
Assuming you've done the pre-install prep; this is installed just like the other XDAndroid builds - grab your startup.txt (don't forget rel_path= if you don't have it at the root of the SD!), ts-calibration and boot!
Download
Caveat List
CDMA users might get a crash in phone.apk and no service on boot. If waiting doesn't resolve the issue, then reboot. Should come up fine...
BT might still be flaky
The CSV files from a RAPH100 are attached for the lazy. I'd like to gather CSV's from each RHOD, I'm curious if any ROM devs have changed them out either... This could get interesting. If you folks don't mind, post up your CSV's, point out differences with mine, etc... We're trying to figure out how to unify these, if possible! Thanks!
Please post back any issues, enjoy!
GBX0C Changelog
Camcorder: Now works (tested on rhodium).
Acoustic: Bug-fix : correct random loss of dual(rear)-mic.
MMS: Bug-fix: Slides with zero duration on Sprint.
Gps: Bug-fix: Init/de-init sequence fix (correct gps not starting up after being unchecked in Settings).
Gps: Bug-fix: End gps session with a correct rpc call (relevant to amss6125 devices).
Gps: Bug-fix: Don't send delayed position requests after session has ended (possibly relevant to Navigation issues).
Gps: New feature: Xtra (aGPS) -> verified to work on rhodium/cdma raph.
X1 specific: Screen rotation patch.
Added tytung's GPS injector app to AndroidApps\Other as well as updating/cleaning up some apps in AndroidApps.
Modified rootfs for newest apsta firmware & wifi firmware - wifi tethering now works flawlessly in the newest kernels! .27 is still bundled for the record...
Test device: RAPH100 running latest NRG build w/sencity
Using everything supplied in the previous posts above minus my ts-calib file; everything seems to work on my RAPH100 (I'm not sure it matters that it has the orange brand on the back cover). Also, this does include sound! I booted without a SIM (yes, this is a GSM version RAPH). The first time I booted, it rebooted to winmo; second time was the charm.
Additional info(statistical maybe?):
Time to boot animation: 3 minutes
Time from boot animation to home: N/A (after 3 minutes my device rebooted to winmo on first try)
(Second trial)
Time to boot animation: 1 - 1.5 minutes (maybe 2 minutes?)
Time from boot animation to home: S/A (same as above)
*Successful boot to lock screen after second boot* (I wonder should this be expected behavior?)
NOTES: Hard keys "Home" and "left arrow"/back key remain highlighted after activated but deactivate after playing around(for the lack of a better word) and/or screen times out. (My opinion)At the very least it doesn't go crazy like earlier froyo builds. Also note that wifi should be working (works on mine) with this build and kernel package (included with package). (I like)New power off boot menu (long press of power key brings this up while short press seems to turn off screen, as usual). "Silent mode" (as expected), "Airplane mode" (as expected), "Kexec" (not sure yet, seems to be the same as "Reboot" or probably vise versa?), "Reboot" brings you all the way back before boot animation and "Power Off" (as expected).
Still test driving (more to come!)
R^7Z said:
"Kexec" (not sure yet, seems to be the same as "Reboot" or probably vise versa?), "Reboot" brings you all the way back before boot animation and "Power Off" (as expected).
Click to expand...
Click to collapse
So reboot didn't work properly?
Let's focus on what's changed. Audio mainly... I do appreciate the report tho .
Kexec is for swapping kernels. This way you can swap kernels and not have to go back to WinMo... Goooogle it .
I ran it for a day, and had no audio problems
only had a few small problems:
it did reboot once
orientation is inverted but i never use auto rotate
market is kinda slow
Edit:
had another reboot during gps app, and i think previous reboot might also have been while gps app was opend
but audio seems to be perfect atm
Greetings
Jeroen
DIAM100
So I've been in the Windows Mobile for quite sometime, came back and noticed the new Gingerbread Build, and it runs fine thus far... I have two issues, no google maps or facebook (incompatible with this device)? Is this something new, or unique to gingerbread?
Problem Solved...
An update to my previous post... changing the DPI back to 240 in startup.txt has resolved the problem.
I really want to try this, as the FRX build lacked the ability to use Bluetooth. Only problem is, I have no .csv files in my WinMo directory. I am running the Energy Sense ROM 2.5 29017.
What do I do now? Do I really need those files?
EDIT: Never mind. I'm an idiot! But I do only have 5 .csv files.
I have it running now, but I get no audio from the phone. Also, bluetooth pairs but I get no audio from it either.
I have a RAPH800, BTW.
SkinsFan said:
I really want to try this, as the FRX build lacked the ability to use Bluetooth. Only problem is, I have no .csv files in my WinMo directory. I am running the Energy Sense ROM 2.5 29017.
What do I do now? Do I really need those files?
EDIT: Never mind. I'm an idiot! But I do only have 5 .csv files.
Click to expand...
Click to collapse
I've also only 5 .csv files in my windows folder:
AudioFilterTable.csv
AudioPara.csv
AudioPara3.csv
AudioPreProcessTable.csv
TIAGC.csv
In the second posting from arrrghhh you will find the *.csv for the RAPH100 in a zip archive (http://forum.xda-developers.com/showpost.php?p=20869601&postcount=2 - it contains only 4 .csv files).
I've tested this Release on my RAPH100 and it is running well.
- Phone works
- Audio works
- Wireless works
- Camera works
On my phone, the hardware buttons light up irregularly (without touching or pressing them - see attachement). The result is that the focus on the screen jumps back and forth. This happens at irregular intervals. Has anyone else this problem?
(I think) It's a design flaw by HTC. This has been a long standing bug even without Android (it's just not as apparent in winmo) and unless we can figure out how to either ignore the additional key pressing being picked up by the touchpad sensor or possibly ignore the touchpad altogether, we may just have to "deal" with it as is. However, I think this is starting to get away from the actual intent of the XDAndroid team's intent to find out about noting any audio irregularities with these files. I'm guessing we either need to start posting our csv files or figuring out what the differences in changing the values mean in terms of audio(or perhaps both?). I really haven't had the time to do much testing aside from describing my experience with loading the GB test bundle.
R^7Z said:
(I think) It's a design flaw by HTC. This has been a long standing bug even without Android (it's just not as apparent in winmo) and unless we can figure out how to either ignore the additional key pressing being picked up by the touchpad sensor or possibly ignore the touchpad altogether, we may just have to "deal" with it as is. However, I think this is starting to get away from the actual intent of the XDAndroid team's intent to find out about noting any audio irregularities with these files. I'm guessing we either need to start posting our csv files or figuring out what the differences in changing the values mean in terms of audio(or perhaps both?). I really haven't had the time to do much testing aside from describing my experience with loading the GB test bundle.
Click to expand...
Click to collapse
Eh, we really just want to know if there are any dramatic differences in the CSV's between devices - XDAndroid tries really hard to support WAY too many devices .
So this thread is mainly to find out if all our new changes dramatically break any one device. Doesn't seem like it... so the next step is to aggregate all the CSV's together (why I asked everyone to post theirs) and see if we can make a big mix of them, or if we'll have to do it similar to the keyboard layout where each device gets its own folder... then it gets into proper variant detection, etc. Hairy!
But yes, the touch panel issue has ALWAYS been present folks. Let's not rehash old bugs, that doesn't do anyone a darn bit of good. Thanks!!
arrrghhh said:
But yes, the touch panel issue has ALWAYS been present folks. Let's not rehash old bugs, that doesn't do anyone a darn bit of good. Thanks!!
Click to expand...
Click to collapse
I haven't heard from this issue before. So it is good to know that.
I've compared your 4 csv files with mine (RAPH 100 - running with Energy ROM 29022) and there is no difference between them.
I've one additional csv file in my windows folder (TIAGC.csv). If you need it I can upload it.
I have a RAPH800 (Sprint) and I was in the process of doing the Pre-install Prep with Total Commander to get the .csv files. However after copying the files to my SD card, I see only 5 files.
AudioFilterTable
AudioFilterTable_Raphael#C
AudioPara3
AudioPara3_Raphael#C
AudioPreProcessTable
I don't see the AudioPara file. Am I doing something wrong? What should I do?
Also I did a Beyond Compare comparison between the files from my phone and the downloaded RAPH100 files and the files are not the same.
ericdabbs said:
I have a RAPH800 (Sprint) and I was in the process of doing the Pre-install Prep with Total Commander to get the .csv files. However after copying the files to my SD card, I see only 5 files.
AudioFilterTable
AudioFilterTable_Raphael#C
AudioPara3
AudioPara3_Raphael#C
AudioPreProcessTable
I don't see the AudioPara file. Am I doing something wrong? What should I do?
Also I did a Beyond Compare comparison between the files from my phone and the downloaded RAPH100 files and the files are not the same.
Click to expand...
Click to collapse
Every phone model will probably have different files. You didn't do anything wrong. Just use the files for your device.
Hi guys,
do you see any kind of battery consumption improvement over FRX release?
shinden said:
Hi guys,
do you see any kind of battery consumption improvement over FRX release?
Click to expand...
Click to collapse
Not really no. Weren't really expecting one either, the only thing that changed was userland. Same kernel (for the most part).
Been running GBX0B 2.3.7 Build on Fuze since the 31st.
I didnt have 10 .csvs, so i just used the his zip. Took me 3 times to get a stable build, they kept self destructing.
Sound: Perfect
Gps: Faster than FRX07.1, when it worked. I justed stop using it
Data: Only used Wifi, works fine
I have a sim in the Fuze, but i have no service.
FRX07.1 would drain my battery over night even plugged in to the wall. GBX0B 2.3.7 fixed that.
I get alot longer battery life. I got maybe 5 (est) hours with FRX07.1, 8 - 10 (est) hours GBX0B 2.3.7
This is the BEST android build for fuze (and i have tried them all).
Smoother, little faster. GPS works alot better. I think we finally got a build we can run full time
popetorak said:
Been running GBX0B 2.3.7 Build on Fuze since the 31st.
I didnt have 10 .csvs, so i just used the his zip. Took me 3 times to get a stable build, they kept self destructing.
Sound: Perfect
Gps: Faster than FRX07.1, when it worked. I justed stop using it
Data: Only used Wifi, works fine
I have a sim in the Fuze, but i have no service.
FRX07.1 would drain my battery over night even plugged in to the wall. GBX0B 2.3.7 fixed that.
I get alot longer battery life. I got maybe 5 (est) hours with FRX07.1, 8 - 10 (est) hours GBX0B 2.3.7
This is the BEST android build for fuze (and i have tried them all).
Smoother, little faster. GPS works alot better. I think we finally got a build we can run full time
Click to expand...
Click to collapse
hmmmmmmm, on my RAPH100 battery discharges faster than on FRX07.1
drugusv said:
hmmmmmmm, on my RAPH100 battery discharges faster than on FRX07.1
Click to expand...
Click to collapse
Honestly the battery shouldn't be different at all. The kernel didn't change much at all in the battery saving or sucking department.
As always, if you use the device a lot - and use a lot of the hardware (GPS, wifi, etc) it will suck your battery dry.