yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III Android Development] scooter1556:
Bit of an impossible question to answer! Is the hard disk in your PC going to crash today? But i've had no data corruption since using it if that helps :)
[Tilt, TyTN II, MDA Vario III Android Development] osilvan:
Is polaris supported in your new kernel? Thanks in advance
[Tilt, TyTN II, MDA Vario III Android Development] scooter1556:
Unfortunately not, I am yet to define the partition layout for polaris and vogue, it's definately on the list of things to do though, hopefully I can have a go this evening or sometime this week anyway :)
[Tilt, TyTN II, MDA Vario III Android Development] stheod:
It runs on my Polaris since Sunday with latest RIL, fast and stable, WiFi BT and GPS OK, no crashes yet. Checked with mount and df, it works as it has to. I modified the original nbh with attached ATools as usual.
[Tilt, TyTN II, MDA Vario III Android Development] scooter1556:
That's weird because I haven't modified the polaris partition layout in the kernel so if you select polaris in ATools it shouldn't partition NAND with a cache partition. It's the same as the kaiser anyway tho so it won't be hard to modify ATools so that it partitions correctly. In fact I might upload a new ATools in a second.

EDIT::

Ok, i'm being a turd, because the partition layout of the kaiser and polaris is the same, when I changed it in ATools it also changes polaris so your right, if you modify the kernel in ATools it will also work on polaris but NOT on vogue!
[Tilt, TyTN II, MDA Vario III Android Development] daedric:
Perhaps a quick edit of the first post, just to warn possible Vogue users :)
[Tilt, TyTN II, MDA Vario III Android Development] dark_prince:
I have installed the kernel and androidupdate inculded. I cant use my POWER button or END button to bring device into wake up after sleep. :/

Back to windows mobile... :( Android got me constantly falling into problems right in the 11th hour
[Tilt, TyTN II, MDA Vario III Android Development] scooter1556:
You give up too easily.
[Tilt, TyTN II, MDA Vario III Android Development] WnG88:
+1 on that. I almost tried installing the kernel on my Vogue. Good thing I saw this. Any way you can put a voguimg up as well when you put up the kaiser / polaris ones? I never know if I'm doing things correctly in Atools. Sounds like this kernel is quite stable.
[Tilt, TyTN II, MDA Vario III Android Development] PoXFreak:
I agree with Scooter, you give up too easily.

I understand it can be frustrating when something doesn't work the way it should (in our case "work at all"), but with each failure comes light of a new success.

I have been fighting to keep Android on my Kaiser now for about a year and, to tell the truth, I would NEVER be able to go back to WinMo after experiencing the epic win that is Android.

Perhaps the one mistake you made in the kernel was to not set the buttons the way you need them to be? In ATools the 3rd radio button down on the left (in-between boot script editor and rom mix) is the one where you can set almost all the buttons to do what you need them to do.
[Tilt, TyTN II, MDA Vario III Android Development] scooter1556:
It won't break your phone or anything, it will just be the same as all other .32 kernels without a cache partition. I can post a vogue img also if you want but theres really not much to do wrong in ATools, just select Vogue instead of Kaiser and save.
[Tilt, TyTN II, MDA Vario III Android Development] wangtrirat:
This ROM is beast. it 's eliminate reboot 256 to 5 problem out.

I've using this on my own cooking rom (not porting by myself) by combining good thing of any release to meet my requirement.

it's uptime for 2 days now. really good job !

using Whatsapp facebook Spriiing(Thai Chatting application) Trillian for instant messaging all day.

but I think battery is going too fast. can you increase battery life in kernel?

things like governor or CPUFreq (i don't know how hard it is but really exciting to see that)

thumb up for you :D

sorry with my bad English :(

Test on HTC Polaris 160 (AKA Asia Touch Cruise) Overclock to 500MHz (if more than that will cause touchscreen jerking) After Enough test I will release my Mod Androidinstall on forum :D with usage on your kernel.
[Tilt, TyTN II, MDA Vario III Android Development] scooter1556:
Updated for Vogue

I've uploaded a new ATools in the kernel package with support for Vogue (hopefully). I don't have a vogue so I don't know if it works but have a go anyway.
[Tilt, TyTN II, MDA Vario III Android Development] daedric:
Thanks for keeping us (kaiser, vogue and polaris users) supported scooter!
[Tilt, TyTN II, MDA Vario III Android Development] dark_prince:
being kaiser as a primary device for me, I think it is a bit true. lol.

I am getting an E71 tomorrow, so as I would be able to play with my kaiser whole heartedly.

Ok, now questions,

1. In Atools key mapping, when I edit the keyboard layout, power button seems to work, but my whole KEYBOARD stops responding (there was a problem with key layout I know, but I cant set sys permissions on it via windows). Is there an updated androidupdate with legit keyboard fix?

2. I do give up so easily because I lose contacts the right moment in next bootup and its frustrating when I have to urgently text or call someone, so are those problems gone? (or this question is same piece of junk as my init.rc crashing one :P)

Damn! I love this community
[Tilt, TyTN II, MDA Vario III Android Development] daedric:
E71... nice phone. It's a work horse, dependable and durable. It doesn't do much, but what it does, does well.

1. IIRC, keymaps where hardcoded somewhere in the kernel. Perhaps liquid could confirm this one, as being the developer of both Atools and the kernel.

2.Let's take this issue scientifically. What android are you trying ? What did you do in Atools ?
[Tilt, TyTN II, MDA Vario III Android Development] cycloid:
wiped everything off my Kaiser, put this and your RIL on and Fat Free Froyo just now, will see how things go :)
[Tilt, TyTN II, MDA Vario III Android Development] dark_prince:
My SD Card is dead slow, benchmarked at 322KB/s pfffft

Anyway, The builds I am trying to put are DZO's Fresh Froyo's latest, mine froyo, Thoughtlesskyle's NSS Froyo. I am not comfortable with CM builds as of the less snappy-ness. Havent gone through a single Eclair build with luck either, I get force closes right after installs etc.

My NAND isnt corrupted either as I have seen from the logs. I am just astonished how you people manage to seamlessly integrate things which I can't following the same way....
[Tilt, TyTN II, MDA Vario III Android Development] daedric:
NSS... had this one until recently, now with Gingerbones.

SD card speed can cause :)

What radio and SPL are you on ?
[Tilt, TyTN II, MDA Vario III Android Development] dark_prince:
Right now HSPL v3.29, and Radio is 1.65
[Tilt, TyTN II, MDA Vario III Android Development] PoXFreak:
Try radio 1.70.19.09, seems to be the best for our Kaisers.

Also, how are you installing kernels? via bootloader or RUU?

Just trying to be scientific about it dae, no "toe-stepping" intended...

One more thing, if installing via bootloader be sure to build an "install.sh" for the install after coming off a WM build. I have had some freaky data issues because the WM data was still intact and not formatted, showing as alot less space for /system or /data.
[Tilt, TyTN II, MDA Vario III Android Development] n2rjt:
Scoot, I think you can call this experiment an unqualified success. Let's get a nice tightly integrated initrd, kernel parameters, and atools into git. How can I help?

I also think your RIL is a good improvement. Maybe you could commit it as well?

Thank you so much for your hard work!
[Tilt, TyTN II, MDA Vario III Android Development] PoXFreak:
I agree... a nice clean kernel and initrd along with parameters not clogged with useless stuff might make this a complete enough build for day-to-day use.

I tend to like rounded intergers when it comes to memory sizes but if 20Mb is what works well, why fix it?
[Tilt, TyTN II, MDA Vario III Android Development] scooter1556:
I will probably have a go at committing some of this stuff next weekend. There's no point committing it until the ATools partition slider is working with the cache partition so I guess that is the most important thing. It will take some time to incorporate it fully into the initrd but i'm sure i'll get there :)
[Tilt, TyTN II, MDA Vario III Android Development] daedric:
I'm a little skeptical to the RIL, but perhaps i'm just the exception to the rule.

Other than that, for the first time ever, my kaiser is my work phone (with android).

Also, it's the first time i trust it to be my alarm.

Great work Scooter, congrats
[Tilt, TyTN II, MDA Vario III Android Development] dark_prince:
I flash em via bootloader, Already udpated to 1.70.19.09.

Is it mandatory to install androidupdate (its huge compared to the wifi one) or its fine without? I manually wipe data everytime I install (Wipe data first, then go for install and YES to wipe data again)
[Tilt, TyTN II, MDA Vario III Android Development] osilvan:
For polaris users: Is camera working with this kernel?

Thanks scooter1556 for this great kernel
[Tilt, TyTN II, MDA Vario III Android Development] dark_prince:
it must work, make sure u have proper radio version
[Tilt, TyTN II, MDA Vario III Android Development] daedric:
It's mandatory. You'll get a kernel error without them.

Also, don't wipe so many times, it's pointless, and might (MIGHT!) be causing issues. Keep it simple:

Copy KAISIMG.nbh to the sdcard root. Copy androidinstall.tar and androidupdate.tar to /andboot. Launch the replimenu, install android wiping data, and install update, should be done.

Also, how are you editing the kernel ?
[Tilt, TyTN II, MDA Vario III Android Development] osilvan:
As far as I know, kernel 2.6.32 didn't support camera for polaris until now. Can any polaris user confirm this?

I want to know it before flashing my only mobile.

Thanks in advance
[Tilt, TyTN II, MDA Vario III Android Development] PoXFreak:
I could throw dark_prince a copy of the kernel I'm using; only issue (if it matters) is the keyboard characters are mixed up a little when using "Fn" key.

OC to 500MHz

OC GPU

Batt MAH set to 1500... your Kaiser will self-adjust the battery value over 2-3 days if it's really wrong. Mine goes up quite a bit before settling down.

Outside of that I use Roguetools to underclock when I don't need the speed. :D
[Tilt, TyTN II, MDA Vario III Android Development] dark_prince:
mine is default HTC Kaiser keyboard layout.

And please, I do need a battery auto adjust. Since, on android, my phone never recharged past 88% (a frequent problem with .25 kernel for me, and I had to keep it for Dual mount SD)

Panel Type 1, Keyboard Type 0

I would be happy to throw in a few experiments on my shelf buddy, as I have got a ZTE Blade to play now :D E71, gah! aint keeping that
[Tilt, TyTN II, MDA Vario III Android Development] PoXFreak:
Here you go man, it's in 7zip format so download a copy of 7zip if you don't already have it.

Don't forget the androidupdate.tar file in the first post as this is needed for the kernel.

Install android and update together as both are needed. The /data file will be corrupt on boot if you don't do the update.

Specs as follows:

Kaiser on NAND

Froyo builds

Panel AUTO (never had issues with AUTO myself)

Keyboard 0 (normal)

OC CPU to 500MHz

OC GPU

Set batt MAh to 1500 (try it, it will auto-adjust as needed)

Flash as usual through HardSPL or RUU

Any issues just message me...

Built for dark_prince, but will work on any Kaiser 100
[Tilt, TyTN II, MDA Vario III Android Development] thefatty:
Been using this kernal for over 2 weeks now, no data loss at all! Brilliant work! Only thing I get is "System is not reponding - force close or wait" when i boot into android, i just lick wait and it never comes up again until I reboot so not really a problem!
[Tilt, TyTN II, MDA Vario III Android Development] n2rjt:
My only complaint with this kernel has been that I can't adjust system and data partition sizes. I usually run a minimal Fresh Froyo build, with /system adjusted to barely be large enough, and put the rest in /data, allowing a fair amount of apps to be installed.

I have a solution that works well. I simply installed the latest google apps (gapps-mdpi) from June onto /system, then I don't need those apps on /data. A few, such as maps, search, and voice, were updated after June. They install to /data automatically, and I then have to move them over to /system. But when all is done, /data has a good amount of space.

I see two kinds of crashes:

a) kernel crash, usually shortly after a reboot but sometimes at random times, caused by the zram module.

b) "White screen of death". Sometimes can recover using Fn-Left / Fn-Right sequence, but sometimes not.

I sometimes see jaffs errors on reboot, but none of my installed apps or configuration has ever been lost.
[Tilt, TyTN II, MDA Vario III Android Development] PoXFreak:
I have only had one actual problem related to the /cache partition due to the fact that any downloaded apps stay there until they are marked as "installed". I had 2 apks' get stuck there, both 6.91mb in size. Both were failed Google Maps installs that caused the phone to reboot (bootanimation came up after lock-up), but still no /data corruption.

I haven't had any zram crashes as of yet and the WSOD has only showed once so I must be lucky. Smooth, responsive and fairly stable compared to other kernels.

I'm with n2rjt on the partitioning values since /system only shows as using 77% under the "df -h" command in TE. My mtdblock3 shows 19.1mb remaining with 79% used.
[Tilt, TyTN II, MDA Vario III Android Development] n2rjt:
If /system is too empty and /data is too small, there are a few options:

app2sd: move some apps to /sdcard. I have never had luck with this.

odex: moves some dalvik cache content to /system. I have not had success with odexing a rom on my build machine, but it can be done after installation.

change partition sizes: this kernel needs minor work to re-enable this option.

manually move some apps from /data/app to /system/app. Be sure to remove old copies of apps, reboot, clear dalvik cache, and fix permissions after moving the files.
[Tilt, TyTN II, MDA Vario III Android Development] PoXFreak:
Ok kiddies, I had my first official crash just 2 hours ago (yes it took this long to get it back)...

I had been having an issue with "system not responding" after a reboot and would just hit wait. I have moved all the bigger apps to the SD card and had been using the phone normally.

Luckily I made a databackup.img to the SD because I hate reinstalling apps.

Basically, I had to rewrite the kernel again and do a complete reinstall and update for the kernel (no RIL just yet, waiting to see what happens).

The phone locked after playing with the camera (un-modified I might add), so I reset via stylus. Upon boot the phone went into a boot loop and stayed that way after multiple reboots/battery removals.

It's back up and running but still has the "system" error on boot.
[Tilt, TyTN II, MDA Vario III Android Development] cupidon192:
Hi All, because this kernel does not accept to modify the system and data size, so I could not install data in sdcard and I had to put it in NAND. So that I have problem "Low on space" with some builds (Scoot's CM7 and CM6, fresh froyo ...) in my phone's starting, and my android killed all apps. Help me solve this problem, please. Show me your Atool's configure.
[Tilt, TyTN II, MDA Vario III Android Development] Den15:
This particular kernal is made for NAND install. From what i've read, this kernal will partition your NAND for your system and data. This will reduce data corruption while on the sd card, it can have data corruption. Try another kernal if you plan to use data on Sd card.

After playing around with this kernal, it would seem that you should be left with a little more than 70 mb on the internal memory. Even when using CM7.02, i think it's sufficient for all the apps I'd like, but if you need more, you should try another kernal and data on SD. I'm left with roughly 23 mbs after the apps i like.

I think Poxfreak's KAISIMG has nice specs, try that one.
[Tilt, TyTN II, MDA Vario III Android Development] PoXFreak:
Be sure that when you flash KAISIMG.NBH from HardSPL that you remove the battery when it finishes. Flash Scoots CGM 6.1.2 via replimenu and be sure to install the "androidupdate.tar" file supplied with the kernel.

Once the install finishes and the phone boots, walk away from it for at least 10 minutes to let the file system settle down. In the apps drawer you will see "Terminal Emulator"... tap it.

If you can get a terminal emulator to come up with any build, open it and type "df -h" without the quotes. This will show you where the memory is allocated and how much remains.

Scoots Cyanogenmod 6.1.2 uses about 79mb, or 77% of the 102mb allocated to /system. the /data partition should be around 50% or 45mb of the 91 remaining.

If upon first boot you see a whole bunch of "block *** is bad" errors (star denotes numbers), then your problem lies in the phones NAND memory and you would need to free up those bad blocks via MTTY (if you don't know what that is, it might be easier to just get another Kaiser).

My ATools configuration is just the basic kernel thats overclocked to 500MHz and batt points set to 2400. No partition size changes have been made even though I like to set /system to 85mb on other kernels.

As Scoot says in the very first post, DO NOT move the partition slider or even check the box. This makes sure you get 102mb allocated to /system and 91mb to /data.

Post your findings here when done...
[Tilt, TyTN II, MDA Vario III Android Development] cupidon192:
Thanks PoXFreak, I saw "block *** is bad" errors in the screen, but I don't know how can I free up bad blocks via MTTY. I'm looking for the way to solve that problem and I have a problem with connecting to PC (my computer was installed win7). OK, I will solve 2 problems first.
[Tilt, TyTN II, MDA Vario III Android Development] PoXFreak:
How many bad blocks do you have coming up?

I have a total of 3 on my main phone and 600 on what used to be the main phone.

The second one will take a kernel install but fails on even the first Froyo builds of 45mb. I have yet to have a computer capable of running MTTY 1.42 since none of my computers have a COMM port, even a virtual one.
[Tilt, TyTN II, MDA Vario III Android Development] cupidon192:
I used MTTY 1.42 to free up NAND, after that I reinstall this kernel with Scoot's CM6, but there are a lot of bad blocks (about 100, I can't remember exactly because it's quite quick) appeared again. When my phone finished and started android, I saw "low on space" icon in Status Bar, many Message Box "The application *** (process.com.android.***) has stopped unexpectedly. Please try again" and android stop all system softwares even close any programs which I want to run. In short, I couldn't access any things.

The installed process:

- Put this kernel (modified with new Atool) in root of SDcard (the changings: CPU 500Mhz, OverclockGPU, batt 2160).

- Put CM6's androidinstall.tar and androidupdate.tar in andboot folder.

- Enter install menu

- Install system (wipe data)

- Install update

- Quit and wait until my phone boot android and error
[Tilt, TyTN II, MDA Vario III Android Development] daedric:
Those instructions should be in the wiki, android section.
[Tilt, TyTN II, MDA Vario III Android Development] cupidon192:
Yes, but it doesn't work, the bad blocks still present (info 8).
[Tilt, TyTN II, MDA Vario III Android Development] cupidon192:
After many hours to looking for the tips and stricks to format NAND, I used MTTY and made my kaiser brick. I try rescuse it with FrankenKaiser and when check bad blocks, it just have 3 bad blocks now and I can install Scoot's CM with this kernel no "Low on space" error. OK, if anyone can't format their Kaiser, try with FrankenKaiser.

thank everyone for help me so much
[Tilt, TyTN II, MDA Vario III Android Development] PoXFreak:
Glad you got through it!

I hope after the install you let the phone sit untouched for at least 10 minutes, that will smooth out performance considerably.
[Tilt, TyTN II, MDA Vario III Android Development] daedric:
Not really... :D

It just during the boot process, until everything is done. Windows is no different.

Now, if the version is DE-odexed, oh my... start opening and closing all apps :D

P.S. I HIGHLY ADVISE AGAINST DE-ODEX VERSIONS.
[Tilt, TyTN II, MDA Vario III Android Development] agungwap:
Hello Scoot, I've been using your kernel and the result was great.

I was fixing to vogue. I upload the file.
[Tilt, TyTN II, MDA Vario III Android Development] scooter1556:
Do you mean you have worked out the equations so that data and system can be resized keeping the 20mb cache partition? If so thanks, saved me a job which I haven't had time to look at :) If you have time, sort the polaris/kaiser section too :D
[Tilt, TyTN II, MDA Vario III Android Development] agungwap:
Yes I had.. :) But, I increased the cache partition to 30 mb, because I wanted to download AngryBird :D
[Tilt, TyTN II, MDA Vario III Android Development] scooter1556:
Fair enough, surely that doesn't run on the Kaiser! That barely runs on the HTC Hero!
[Tilt, TyTN II, MDA Vario III Android Development] n2rjt:
I tried it once but we don't seem to have enough ram. We don't generally want 30mb cache. Imho, 15 is sufficient.
[Tilt, TyTN II, MDA Vario III Android Development] WnG88:
Any compiled version of the kernel working for the vogue? maybe with 20mb cache?
[Tilt, TyTN II, MDA Vario III Android Development] a.s.j:
I'm for 15MB too... I guess it would be fair enough for our Kaisers
[Tilt, TyTN II, MDA Vario III Android Development] PoXFreak:
For those of us using small apps under 5mb, a 15mb cache is fine as long as you don't start downloading a whole bunch of apps at once. For the guys wanting 30mb because they want "Angry Birds" or any other 3D intensive game, I wouldn't bother because the OpenGL drivers aren't really made for our devices and the game will crash most of the time, especially when we're overclocked.

IMHO, I think Scoot got it right with the number 20. It leaves enough room to D/L multile apps from the market and still have a place to put them when they're done.

Although I like round computer numbers, "human interpitable numbers", 20 is a good placemarker. I like 16, which might have to do with me being a DOS fanboy ever since UNIX/XENIX came out. Hell, even BASIC worked with either 1, 2, 4, or 8 byte intergers.
[Tilt, TyTN II, MDA Vario III Android Development] MaRekRM:
Also I see no point in increasing the cache size. Let it be as it is.

It's depends on version of game. On overclocked Kaiser with autokiller set to agresive mode I played example Heavy Gunner 3D, Raging Thunder2, AngryBirds(v 1.3.5) and this working not bad (maybe small lags sometimes). But if someone wants download newer versions like AngryBirds Rio-so only get slideshow...
[Tilt, TyTN II, MDA Vario III Android Development] n2rjt:
Did you ever push the git changes for the separate cache? I'd like to get that into initrd, with cache size as a kernel parameter. Also, is initrd as small as we can make it, or does it still have extra stuff? We have drivers and utilities for ext4: do we also have separate copies for ext2?
[Tilt, TyTN II, MDA Vario III Android Development] PoXFreak:
This might come off as selfish but hear me out.

Why not just separate the kernels and have specific initrds for each phone.

Decide on ext2 or 4, build initrd and driver package for each and commit the packages to sourceforge. FORCE ATools to recognize not just one kernel but all 3 and build each kernel based on what each phone requires. Standardize it all, then we have a REAL way of knowing what needs to be built into the androidinstall.tar.

If I knew what to do with a kernel (other than pop them when making popcorn), I might be able to help.
[Tilt, TyTN II, MDA Vario III Android Development] Neo2SHYAlien:
Yeah standardization is a good idea.