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
Related
I know that I am going to be verbally destroyed for asking this but...
lol
I have an AT&T Tilt. Is there any single android distribution that has Working sound, wifi, camera, keypad, gps etc. I've tried a few different versions and each seems to have something good and something bad. Feel free to burn me up with flames of hatred, but hopefully I can get a clear answer somewhere in the inferno
Thanks!
xtty said:
I know that I am going to be verbally destroyed for asking this but...
lol
I have an AT&T Tilt. Is there any single android distribution that has Working sound, wifi, camera, keypad, gps etc. I've tried a few different versions and each seems to have something good and something bad. Feel free to burn me up with flames of hatred, but hopefully I can get a clear answer somewhere in the inferno
Thanks!
Click to expand...
Click to collapse
Myn's Warm Donut is near perfect (android 1.6). The only problem I've noticed with it is that the battery status is inaccurate, but that's true for all android builds for the kaiser to my knowledge. Other than that, it runs perfectly fine, very stable and quick, even from the sd card.
Fantastic Thanks!
I'm an idiot, wrong thread ;0
kallt_kaffe produces excellent kernel binaries and VanilijEclair is great!
Alright next question. Everything works but the sound. I can go in to adjust the volume, but when I try to leave that menu option I get "Activity Sound & Display (in application Settings) is not responding."
And in the jewels game I can not hear any sound either.
Any ideas?
xtty said:
Alright next question. Everything works but the sound. I can go in to adjust the volume, but when I try to leave that menu option I get "Activity Sound & Display (in application Settings) is not responding."
And in the jewels game I can not hear any sound either.
Any ideas?
Click to expand...
Click to collapse
are you running haret? currently (to my knowledge) sound does not work.
updating your radio, if its not already, could help
I also have an AT&T Tilt.
To answer your question, it's all about the kernel.
Look for DZO's kernels, and use the newest.
If you use Haret get the newest zImage and pay attention to the correctly editing the txt file where things have to be configured correctly for a Tilt.
If you burn to internal flash, use the NZH editor.
sound: yes
wifi: yes
camera: yes
keypad: yes
gps: yes
Right now I have an ATT Tilt running VaniljEclair with the 6/25 dzo nbh file edied with the nbh editor for my panel type.
Build from here: http://forum.xda-developers.com/showthread.php?t=700669
NBH from here: http://it029000.massey.ac.nz/vogue/files/?C=M;O=D
NBH Editor here: http://forum.xda-developers.com/showthread.php?t=689813&highlight=nbh+editor
Has anyone tried running the latest zimages under haret? I've tried warm eclair and superfroyo, and both are having the same problem: If I put the phone to sleep, I get a solid white screen when I wake it up. Every time.
Frustrating that the latest distros of Android are unusable on my phone, warm donut worked like a charm.
TransparentHuman said:
Has anyone tried running the latest zimages under haret? I've tried warm eclair and superfroyo, and both are having the same problem: If I put the phone to sleep, I get a solid white screen when I wake it up. Every time.
Frustrating that the latest distros of Android are unusable on my phone, warm donut worked like a charm.
Click to expand...
Click to collapse
in default.txt change your panel type to 1,2 or 3
dadevil666 said:
in default.txt change your panel type to 1,2 or 3
Click to expand...
Click to collapse
Thanks, that worked, although I could swear I tried that already.
TransparentHuman said:
Has anyone tried running the latest zimages under haret? I've tried warm eclair and superfroyo, and both are having the same problem: If I put the phone to sleep, I get a solid white screen when I wake it up. Every time.
Frustrating that the latest distros of Android are unusable on my phone, warm donut worked like a charm.
Click to expand...
Click to collapse
Actually as far as I am aware this only affects panel 2 and 3, which appear very similar, but use slightly different power management signals, so if you use panel 2 on a device with panel 3, it looks fine, but suffers from strange issues when waking, although I have not heard any issues with setting panel 3 on a panel 2 device yet... maybe I should try it, just for research purposes
I get a solid white background as well, but it goes away after half a second.
I hate to reopen a dying thread but. . .
I have tried 5 different roms, from donut up, and have tried the roms suggested in this thread. I cannot get the camera on my tilt to work for anything. Not a single install has yeilded a working camera. I have the latest radio, newest froyo_tilt kernal, and im using VaniljEclair_RLS7c. . .i get nothing. . .nada. . .is there a fix anywhere for this damnable tilt camera?
Using a froyo kernel on an eclair build results in a non-working camera, you should be using an eclair kernel.
hmm. seems common sense. . .i will be annoyed if that is the issue. . .all the guides say grab the latest kernel and use the nbh editor to set parameters to whatever build ver. I will try the eclair kernel. thank you zenity
OMG common sense ftw!! sorry to waste your time with this, I really appreciate it! gravy!
No problem, it has been mentioned in a few other threads, but it's not that easy to find, unless you are a forum addict like myself
Note that when using the nbh editor, setting donut or eclair refers to the HW3d option only, since donut and eclair have different 3d settings.
And it's never wasted time, someone else with the same problem may read this, so it helps everyone
yea, helped me just now, doing exact same, using froyo nbh with donut,
thanks
^^ there are no stupid questions, and time spent answering questions is never wasted if it helps others also
Can I Run it using Haret?
I dont wanna install it.
Absolutely!!!!
I have been playing with Froyo on my Kaiser for weeks and loving it...I've always flashed to Nand, not worrying to much about putting winmo back on the device (but believe me, you won't want to) Just search this forum, there are excellent devs and tutorials on running Android from SD using Haret and flashing via Hardspl....Ive tried many ROM's and can recommend Icubus' Super Froyo RLS12 and Milanches Cyanogen mod 6 for Kaiser RLS4....
Id start here:
http://forum.xda-developers.com/showthread.php?t=680518
Then check out these two links:
http://forum.xda-developers.com/showthread.php?t=712310
http://forum.xda-developers.com/showthread.php?t=732040
XDA is truly the cutting edge for Mobile phone development....You have come to the right place...
All the credit goes to the genius of the many devs on this forum....
Does the camera,GPS and blutooth work?
Does the camera,GPS and blutooth work?
yes it works
Yes you most certainly can I am running CyanogemMod6 on mine quite happily, everything seems to work just fine. Enjoy.
Leona, got 1 question here, i've been a loyal dzo's fresh froyo, so far my favourite distro less hiccup no restart, but still the camera doesn't improve much, dark picture, how is camera on cyanogenmod6 doing? in terms of picture quality and brightness.
Thanks.
Kaiser 130 (panel 2)
radio/spl: 1.71* / 3.34
Dzo's fresh froyo 26-07 (Nand)
akmalxxx said:
Leona, got 1 question here, i've been a loyal dzo's fresh froyo, so far my favourite distro less hiccup no restart, but still the camera doesn't improve much, dark picture, how is camera on cyanogenmod6 doing? in terms of picture quality and brightness.
Thanks.
Kaiser 130 (panel 2)
radio/spl: 1.71* / 3.34
Dzo's fresh froyo 26-07 (Nand)
Click to expand...
Click to collapse
Hi Akmalxxx, I am possibly not the best person to ask that, since my sight isn't great, all I can tell you is that the camera works, seems the same as other builds I have tried.
Now as I understand it, cyanogenmod6 uses the same zImage as Fresh, (dzo's latest 26-07-10) so I would assume/expect that the camera would be the same?
oh i totally forgot about the kernel, thanks for the clarification, guess i should wait for new kernels.
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.
Dear Reefermattness and arrrghhh !
I apologize for making a new thread but I just want have your attention on the Neopeek Release for Rhodium.
In this forum stays that in FRG83.R5 release
http://www.neopeek.com/en/forum/Android-ROMs/2183-ROM-FRG83-Build-Froyo221-05-11-2010
Bluetooth IS WORKING !
I have no idea what this release can, but I saw its structure. Basically EXT2 Partition for Neopeek is the same thing that system.ext2 file for FRX03 !
And in andoidinstall.tar.gz file is the same stuff as in system.ext2 and roofts.img together.
Why we just not pick the working Bluetooth "driver-package-what-ever" from Neopeek and combine it with FRX03 ? I could do it by my self, but I don't have deep system structure know-how.
I must say that FRX03 is lot easier to handle (getting ready, install, edit etc) thats why I'd prefer working with it as with Neopeek.
And besides I just reached almost 8 hrs of working time with one charge on it with new kernel and startup change. Thats why I want to improve it. Can you help me to understand the structure of driver packages for BT ?
Thank you
-------------------------------------
----------------
EDIT:
Here it is, a repack of SuperFroyo in system.ext2 file.
http://narod.ru/disk/27385762000/system.zip.html
I didn't test it yet. But if some one want to try out - please download and report back !
d0nate110 said:
Dear Reefermattness and arrrghhh !
I apologize for making a new thread but I just want have your attention on the Neopeek Release for Rhodium.
In this forum stays that in FRG83.R5 release
http://www.neopeek.com/en/forum/Android-ROMs/2183-ROM-FRG83-Build-Froyo221-05-11-2010
Bluetooth IS WORKING !
I have no idea what this release can, but I saw its structure. Basically EXT2 Partition for Neopeek is the same thing that system.ext2 file for FRX03 !
And in andoidinstall.tar.gz file is the same stuff as in system.ext2 and roofts.img together.
Why we just not pick the working Bluetooth "driver-package-what-ever" from Neopeek and combine it with FRX03 ? I could do it by my self, but I don't have deep system structure know-how.
I must say that FRX03 is lot easier to handle (getting ready, install, edit etc) thats why I'd prefer working with it as with Neopeek.
And besides I just reached almost 8 hrs of working time with one charge on it with new kernel and startup change. Thats why I want to improve it. Can you help me to understand the structure of driver packages for BT ?
Thank you
Click to expand...
Click to collapse
1) as far as I understand Neopeek uses large parts of Xdandroid projects, starting from the kernels/rootfs. This is not hidden/secret, so he and xda devs may know each other pretty well.
Therefore I can't understand how he can have bluetooth working and Xdandroid not.
then ...
2) maybe he shares branches of code and patches with our devs, but while our devs decided that the code to make bluetooth working is still too buggy, he could have decided to shoot it in for good. In fact reading comments on the thread you posted you will see that at the end the people crying for not-working BT are a lot ...
I'd be interested to see if BT works fully. I've seen some where they scream that BT works, but then when they actually try to use BT... it fails. So if it pairs and nothing else, that's what state our build is in as well.
I just installed it, on a blank 2Gb I had spare.
At start it's quite a pain in the arse ...
cmdline was a little different, I just set correct keyboard.
But I immediately put the latest kernel (24.11.2010). Both in installer and main.
Much faster than Xdandroid. Much faster at boot, much snappier in launcher etc., but this may be related also to the age (of the FAT32 file system) of the other SD I use for Xdandroid. Will format it and see what happens swapping.
But then, when it went to sleep it just crashed.
I tampered with the startup, added pmsleepmode=2, this worked, tried =1 and works quite well.
As I expected, BT doesn't work on my RHOD100.
This neopeek build comes nearly all from xdandroid, so it seems it's not as up to date.
But while that guy takes most of development from XDA, he must work a lot on tweaks, therefore XDA should take something back ...
I'll try cleaning the other SD and check what happens.
Installed on extra card. Rhodium 400 . It is fast. Boots quicker. The initial setup screens are very friendly. Power off and other buttons work more like winmo. Bluetooth will not turn on. Phone works. Data does not work. Have to use WiFi for data. USB while in Android does work (sweet). Key board backlighting not working. I am going to reinstall with bluetooth enabled initially in winmo.
Neopeek SuperFroyo Repack into system.ext2
arrrghhh said:
I'd be interested to see if BT works fully. I've seen some where they scream that BT works, but then when they actually try to use BT... it fails. So if it pairs and nothing else, that's what state our build is in as well.
Click to expand...
Click to collapse
Here it is, a repack of SuperFroyo in system.ext2 file.
http://narod.ru/disk/27385762000/system.zip.html
I didn't test it yet. But if some one want to try out - please download and report back !
reinstalled Bluetooth not working. Rhodium 400
Only things that could make improvements to XDA android are Speaker phone is working. USB in android does work. Buttons function as they should. It works with SIM card installed. Speed. Boots faster. Screen adjusts to right profile on start lockscreen.USB headset works without line in startup.
Still not working
Data does work but have to manually set APN. Headset does not work ( Does work with line in Startup and calling during boot). Problems with the market downloading.
Does work tethering. pretty much everything
One nice thing is they have a seperate install folder so if your system is corrupted you just reinstall with file manager in winmo. It reformats the ext2 partition on the card. I assume the sizing of partition is in place of the sizing the data.img file on the card.
Being open source borrowing a few items should not be considered crossing a line.
d0nate110 said:
Here it is, a repack of SuperFroyo in system.ext2 file.
http://narod.ru/disk/27385762000/system.zip.html
I didn't test it yet. But if some one want to try out - please download and report back !
Click to expand...
Click to collapse
wait a minute.. you didnt test it and are spreading it like wild fire ?
before you cry wolf, at least pretend you saw one ..
First Full Day Of Testing
[ACL] said:
wait a minute.. you didnt test it and are spreading it like wild fire ?
before you cry wolf, at least pretend you saw one ..
Click to expand...
Click to collapse
I've tested this strange build a whole day today... I must say...I'm confused...
First of all I charged my battery to full 100% in WinMo. Then I've just replaced old system.ext2 with this one (my other files incl. kernel were untouched) and booted a clean Haret and saw, that this Android Learning Demo just didn't want to go on if I taped on it...
My device was locked and I must reboot it...then I delete my data.img file and tried again... success - SuperFroyo booted well.
- Bluetooth doesn't work as pessimistically expected
Other stuff works same like in our Froyo Reference.
- flash 10.1, loudspeaker, camera, usb connection and headphones don't work
- sleep_mode=1, wifi, phone, wake up on call and Market are working.
But Battery life was little better according to JuicePlotter... and I had a feeling, that all the system works little bit faster... I don't know if it is just placebo effect, but I thing its true...
I'll keep testing it for another 3-5 days and report back... and BTW you can test it too.
d0nate110 said:
I've tested this strange build a whole day today... I must say...I'm confused...
First of all I charged my battery to full 100% in WinMo. Then I've just replaced old system.ext2 with this one (my other files incl. kernel were untouched) and booted a clean Haret and saw, that this Android Learning Demo just didn't want to go on if I taped on it...
My device was locked and I must reboot it...then I delete my data.img file and tried again... success - SuperFroyo booted well.
- Bluetooth doesn't work as pessimistically expected
Other stuff works same like in our Froyo Reference.
- flash 10.1, loudspeaker, camera, usb connection and headphones don't work
- sleep_mode=1, wifi, phone, wake up on call and Market are working.
But Battery life was little better according to JuicePlotter... and I had a feeling, that all the system works little bit faster... I don't know if it is just placebo effect, but I thing its true...
I'll keep testing it for another 3-5 days and report back... and BTW you can test it too.
Click to expand...
Click to collapse
I'm on nand, so i cant run that abomination. However i did run the real cyanogen and it was a lil faster. But it took too many changes to the rootfs to get it to run.. i havent tried it since..
Also im not sure why neopeek isnt using our rootfs structure so you can swap the system.imgs easier .. maybe you should ask him
too buggy things would work then stop working. I could plug in a usb headset have it work in a call or music unplug it then plug it back in and it does not work. Many other things like that. Same with the 3.5 jack trick it would work sometimes then sometimes not. If u left it stock it works great and is very fast. Diamond users were happy. I have a diamond that I will try it on sometime next week, but it is not good for rhodium. It did something to the usb on my Rhodium in winmo would not work so gave me a chance to jack in energy rom like that so far.
[ACL] said:
I'm on nand, so i cant run that abomination. However i did run the real cyanogen and it was a lil faster. But it took too many changes to the rootfs to get it to run.. i havent tried it since..
Also im not sure why neopeek isnt using our rootfs structure so you can swap the system.imgs easier .. maybe you should ask him
Click to expand...
Click to collapse
Sorry for silly question, but what do you mean with "being on nand"?
And, lol, why abomination!?!?!?
It's clearly taken from FRX02 Xdandroid build, but tweaked to be more speedy.
These tweaks are something that Xdandroid should port back to main project.
I have only one crash a day with Neopeek's FRG83.R5, while Xdandroid FRX03 is not only slower on my TP2 rhod100, even with around 100Mb ram free, but keeps slowing down even more while using, so that I have to restart.
In the last week this led to process ".acore" crashing almost immediately after boot, with no solution known to me except reinstalling.
That's once a day.
Neopeek did this only once.
Still have to understand what leads to ".acore" process chain crashes.
I would prefer to use Xdandroid FRX03, because it's more up to date and standard compliant, but, strangely, it's not as stable as Neopeek's FRG83, on my phone.
Cheers.
EDIT:
uh, oh, d0nate, I think we are messing it a little bit here. I am testing FRG83.R5, not SuperFroyo.
They are 2 different builds.
What are you effectively testing?
Sorry about that
sad0felix said:
EDIT:
uh, oh, d0nate, I think we are messing it a little bit here. I am testing FRG83.R5, not SuperFroyo.
They are 2 different builds.
What are you effectively testing?
Click to expand...
Click to collapse
First of all I AM NOT Donate - I'm donatello written with numbers
I don't want any donations and hate money
Second I apologize, but I can't implement FRG83.R5 to use without formating my SD-card thats why I use a SuperFroyo. The member DmK75 gave me this link to system.ext2 file with SuperFroyo release in it...
I try though to repack FRG83.R5 also in system.ext2 file later... I just don't have the know-how yet...
sad0felix said:
Sorry for silly question, but what do you mean with "being on nand"?
And, lol, why abomination!?!?!?
It's clearly taken from FRX02 Xdandroid build, but tweaked to be more speedy.
These tweaks are something that Xdandroid should port back to main project.
I have only one crash a day with Neopeek's FRG83.R5, while Xdandroid FRX03 is not only slower on my TP2 rhod100, even with around 100Mb ram free, but keeps slowing down even more while using, so that I have to restart.
In the last week this led to process ".acore" crashing almost immediately after boot, with no solution known to me except reinstalling.
That's once a day.
Neopeek did this only once.
Still have to understand what leads to ".acore" process chain crashes.
I would prefer to use Xdandroid FRX03, because it's more up to date and standard compliant, but, strangely, it's not as stable as Neopeek's FRG83, on my phone.
Cheers.
EDIT:
uh, oh, d0nate, I think we are messing it a little bit here. I am testing FRG83.R5, not SuperFroyo.
They are 2 different builds.
What are you effectively testing?
Click to expand...
Click to collapse
Ahh you poor soul.. nand meaning i no longer have wince so i cant run his installer. Abomination is a strong word.. so i take it back . But i do think it's wicked and it's not a child of xdandroid like you think. The main chunk of the project comes from cyanogen. The only parts that were pillaged from xdandroid appear to be some of the roofs files (including the hardware libs). And of course, our kernel runs the whole show.
Now why would i run some hacked up version if i can run cyanogen directly? Plus cyanogen has everything open, so we can easy work and modify it as we need. I have not seen anything shared by neopeek, so i dont feel its fair to the xdandroid team since we pretty much share everything.
If it's stable for you.. awesome.. maybe there is future for it.
[ACL] said:
Ahh you poor soul.. nand meaning i no longer have wince so i cant run his installer. Abomination is a strong word.. so i take it back . But i do think it's wicked and it's not a child of xdandroid like you think. The main chunk of the project comes from cyanogen. The only parts that were pillaged from xdandroid appear to be some of the roofs files (including the hardware libs). And of course, our kernel runs the whole show.
Now why would i run some hacked up version if i can run cyanogen directly? Plus cyanogen has everything open, so we can easy work and modify it as we need. I have not seen anything shared by neopeek, so i dont feel its fair to the xdandroid team since we pretty much share everything.
If it's stable for you.. awesome.. maybe there is future for it.
Click to expand...
Click to collapse
Woah ... I am feeling soooo noob ... dang you!!!
Since I wrote my previous post my knowledge grew about ten times ... from 0.001% to 0.01%, so now I can see what you mean about Cyanogen and all the rest.
I know it's everything but a good excuse, but please notice that I got to Android just in the form of Xdandroid, and only in the last few weeks.
So I am learning. Maybe faster than mean people, still much slower than hardcores like you or the other devs.
----------------
In the meanwhile I reverted back to FRX03.
Mainly because of stabilities (better, instabilities are regular so that can be forecasted and behaviors provoking them can be avoided with good success rate).
Still I think that maybe (and I cap it, MAYBE) Xdandroid could (I don't say should, it would be excessive) benefit from the Neopeek/Cyanogen "thing".
You know, like when you have a crate of stuff, you dive hands in it and choose and pick up just the good things/those you like.
I just dream a Xdandroid snappy like Neopeek's whatever build (I tried 2).
... the speed ... the speed .... (put here Marlon Brando's voice in Platoon, when he repeats "the horror" ... ).
Cheers!
EDIT:
I fear that you did it all by yourself, but in any case I ask you.
Is there any public documentation about going nand? What are the advantages?
You put a thermite in my left ear, you know?!?!?!
Here's the PPCG thread on NAND boot testing. Not for the faint of heart...
sad0felix said:
Woah ... I am feeling soooo noob ... dang you!!!
Since I wrote my previous post my knowledge grew about ten times ... from 0.001% to 0.01%, so now I can see what you mean about Cyanogen and all the rest.
I know it's everything but a good excuse, but please notice that I got to Android just in the form of Xdandroid, and only in the last few weeks.
So I am learning. Maybe faster than mean people, still much slower than hardcores like you or the other devs.
----------------
In the meanwhile I reverted back to FRX03.
Mainly because of stabilities (better, instabilities are regular so that can be forecasted and behaviors provoking them can be avoided with good success rate).
Still I think that maybe (and I cap it, MAYBE) Xdandroid could (I don't say should, it would be excessive) benefit from the Neopeek/Cyanogen "thing".
You know, like when you have a crate of stuff, you dive hands in it and choose and pick up just the good things/those you like.
I just dream a Xdandroid snappy like Neopeek's whatever build (I tried 2).
... the speed ... the speed .... (put here Marlon Brando's voice in Platoon, when he repeats "the horror" ... ).
Cheers!
EDIT:
I fear that you did it all by yourself, but in any case I ask you.
Is there any public documentation about going nand? What are the advantages?
You put a thermite in my left ear, you know?!?!?!
Click to expand...
Click to collapse
nand is for the brave.. so if you are just starting. then stay away since we already had a brick happen. I also corrupted something myself so it can get nasty. Once we stabilize it will get better. The main advantage is that you no longer have windows. lol.. but the disadvantage is that you dont have windows to fall back on. It also lets us develop as if the phone would be native to android. Believe it or not but wince does alot of the dirty work for us. So the nand project lets us recreate all that ourselves.
Cyanogen is just a different animal. Xdandroid is based of pure google code as it was meant to be. It also lets us modify it for our devices that were never meant to have android. Cyanogen only supports devices that already came with android. You can modify it to run on other devices, but the main builds themselves are for specific devices. Xdandroid supports all with just 1 build. We forget sometimes about our other winmo htc brethren like topaz and blacstone. But they need a build too.. .
If you are really interested in this, you can clone both codes and compare just how different we are. If you find something you think will benefit, try it out and see what happens. Gotta love opensource.
[ACL] said:
nand is for the brave.. so if you are just starting. then stay away since we already had a brick happen. I also corrupted something myself so it can get nasty. Once we stabilize it will get better. The main advantage is that you no longer have windows. lol.. but the disadvantage is that you dont have windows to fall back on. It also lets us develop as if the phone would be native to android. Believe it or not but wince does alot of the dirty work for us. So the nand project lets us recreate all that ourselves.
Click to expand...
Click to collapse
Hep, I am just a curious guy.
One of those many that want to put their nose everywhere, but also one of the few that:
a) most of the times will need to read the guide just once (if guide isn't enough there are FAQs and Google),
b) will follow instructions easily because normally understands what they mean/what they are for
c) will never give it up until success
d) will never come to the forum writing: "I have a phonez, tried to put some android on it, doesn't work HELP1!!1!!1!"
Moreover, my TP2 is just 6 months old, is a gift, I use it for work, so to not void the warranty I didn't even install HardSPL on it.
So do not worry.
I am just curious to read how you can do it.
But will not die if I don't know yet
Cyanogen is just a different animal. Xdandroid is based of pure google code as it was meant to be. It also lets us modify it for our devices that were never meant to have android. Cyanogen only supports devices that already came with android. You can modify it to run on other devices, but the main builds themselves are for specific devices. Xdandroid supports all with just 1 build. We forget sometimes about our other winmo htc brethren like topaz and blacstone. But they need a build too.. .
If you are really interested in this, you can clone both codes and compare just how different we are. If you find something you think will benefit, try it out and see what happens. Gotta love opensource.
Click to expand...
Click to collapse
Basically you are suggesting me that all the (amazing) speed of Neopeek's builds comes just from using direct EXT/SWAP partitions on SD.
So, is there anyone trying to build a Xdandroid with EXT/SWAP structure?
sad0felix said:
Basically you are suggesting me that all the (amazing) speed of Neopeek's builds comes just from using direct EXT/SWAP partitions on SD.
So, is there anyone trying to build a Xdandroid with EXT/SWAP structure?
Click to expand...
Click to collapse
Not to my knowledge. I guess we should *try* it just to see if there's a big difference... perhaps Neopeek can help us here muhahahahaha!
But I think the theory was the tradeoff would be small - a lot more work for very little reward. However, I would be interested to see if there is a difference, and if it is big or not. At the very least just to know if it's our build or just the ext2 partition that's making it feel snappier.
In addition, AFAIK swap partitions on SD cards should be avoided, unless they have a write-levelling scheme (I believe they only put these in SSD's... I don't think any SD card has this tech because it's typically unnecessary) - I've heard swap partitions can just destroy a normal SD card because of writing and re-writing to the same area of the card many, many times... I mean physically on the card, not just logically in the folder hierarchy.
Just installed it on my diamond Bluetooth does work but it doesnt pair. The screen eventually graduates to the center dividing it in opposite. I thought maybe because I was running the hot version. Repartitioned reinstalled the normal clock version runs for a time then the same. Its no better than XDA
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....