yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III Android Development] l1q1d:
There are several problem to solve:

- the nbh is only edited by atools and it's not created every time from zImage and initrd so we must upload all the files for all

- there is now way to recognize the kernel commit from the zImage
[Tilt, TyTN II, MDA Vario III Android Development] PoXFreak:
Who says we have to use the same zimage for all 3 phones?

Why not just build all 3 kernels and apply the proper modules to their respective phone build?

It would eliminate a bit of bulk to the front end of the NAND and make it easier to track issues in specific phones. No OC, no extra settings, no changing partition sizes (unless the cache uses the percentage table I thought of earlier), nothing. You want an OC, get RogueTools from the market. If you OC to 575 and crash your phone, it's your fault.

I might be coming off as an ass, but I hate to have excess baggage...

Much love and respect l1q1d, I just feel it's time to take this project to the next level.
[Tilt, TyTN II, MDA Vario III Android Development] a.s.j:
I agree... I am gonna give my refurbished good old Kaiser to my son soon, cause I have a new phone to use as primary one, and it would be great to be sure, his phone can get really smooth and stable with perfect Android build. And we would even get some extra space for our phones am I right?

Anyway... Just an idea... Would it be hard to link phones "check updated software" button in settings to some repository with latest builds to enable automatic updates?
[Tilt, TyTN II, MDA Vario III Android Development] PoXFreak:
I see that as a possibility with the "system_froyo_us" build hosted on sourceforge, but for the vast amount of builds out there it would be near impossible unless the OP of each particular build were to link that update button to a site that they host. That means Dzo, ThoughtlessKyle, Scoot, Dark_Prince, and all other guys would have to have their own hosting site with their own updates.

And with the ease at which updates can be handled, I can see why that would be a problem for developers since most /system updates can be handled with a simple androidupdate.tar file.
[Tilt, TyTN II, MDA Vario III Android Development] scooter1556:
It sounds very simple when you say it like that, but when you look at the kernel code there are multiple paths which the compiler takes depending on the device you are building for. The Polaris, Kaiser and Vogue all come under the same path but sections of this path are routed for a specific device using an 'if polaris' etc... and this is detected by the kernel when the phone boots by the phone ID. You won't gain anything by seperating the code for each device because they are so similar, it is much more efficient to re-use code where possible and just take different paths depending on device when needed. You will make the kernel smaller by a few KB if you took out code for other devices and just built for the Kaiser for example, but there is an allocated amount of space for the kernel in the NBH regardless of how big/small it is so there is virtually no advantage, if anything it would be going back a level in my opinion.
[Tilt, TyTN II, MDA Vario III Android Development] Neo2SHYAlien:
scooter1556 do u think soon will be a possible to implement data partition be over SD card ??
[Tilt, TyTN II, MDA Vario III Android Development] PoXFreak:
I hate to tread thin ice to get an answer but the fact is that I'm still learning what I can, where I can and however I can.

Scoot, I think I get it... I would just like to see one implementation of the kernel for each of the three phones, stripped of anything not needed.

I come from the days when if you had too much bloat on your computer it slowed down and you HAD to keep it simple, unlike today where if you have too much garbage you move it to a larger hard drive and keep accumulating more.
[Tilt, TyTN II, MDA Vario III Android Development] scooter1556:
Don't worry, I won't bite your head off for asking, well, not all of it anyway :) You can compile the kernel for an individual phone by modifying the config file and just leaving kaiser enabled for example. What this does is compile only the code for kaiser and ignores the polaris and vogue pathways. As I said before though, this will only cut a limited amount of code and kb in the kernel so it's barely worth it. The main things it cuts out is IRQ addresses for the individual devices for example. So yes, removing the code for the other devices will make some difference but not a lot. It won't change any of the source code for the kernel, although, if I remember rightly, vogue is a dependency for both kaiser and polaris in the kernel so removing vogue from the config probably won't work. The code would have to be re-worked for it to work properly but the kaiser and polaris use a huge amount of code that was originally written for the vogue, hence why you can't remove much vogue specific code.
[Tilt, TyTN II, MDA Vario III Android Development] l1q1d:
the problem for the kernel code is due to the fact that dzo added kaiser and polaris as a subdevice of vogue so the shared code between the devices is all in vouge.

Also you can't create a kernel without parameters because there are settings like screen type and keyboard type that are different for the same device.

There is another problem, if you place all the particular device part in modules you can't access to the irq after boot (we don't figure out why) and you need to release the modules for every kernel.
[Tilt, TyTN II, MDA Vario III Android Development] PoXFreak:
Ok, thanks scoot and l1q1d... that explains quite a bit being I've never actually even seen a vogue or a polaris (except pictures of course).

So it basically boils down to if we need to shrink something to gain space, the kernel partition is not one to mess with.

I still have this suspicion that things still need to be worked out to finalize this, I just pointed at the kernel first because thats where I see most of the errors on boot.

Things like "cannot mount /system/bin/su, the directory does not exist" and the "bluez" directory not being there, even though I've installed builds with this file intact and in it's proper place.

I appreciate the understanding that I am a "stupid windows user" and I'm still soaking up knowledge. I also deal with a blurred line between this phone and the Fuze/Raphael, which Scoot has given me more insight on than ANYONE in the Touch pro/Fuze forum. Very much appreciated, Scoot!
[Tilt, TyTN II, MDA Vario III Android Development] scooter1556:
Well, my knowledge of the Touch Pro is very limited but i'm happy to give pointers where possible and thank you for the kind words. I've only realised since purchasing a new phone how pleasant this forum is, probably due to the limited users left with the device. I've been following some threads on the Galaxy S forum which is a pretty popular phone, which I thought would be a good thing, apart from every c*ck and their brother fills the threads with utter turd! I hope no-one from that forum reads this :D
[Tilt, TyTN II, MDA Vario III Android Development] PoXFreak:
I understand completely.

I hate to throw this post in another direction but...

I responded to a post on the main page in General Discussion about how the HD2 garners alot of the development. I basically said that people only want to deal with whats easiest to work with or newest on the block.

There's only a couple of devs out there really willing to put forth the effort to make something work. If there's not much demand for it, theres not much effort put into development.

That and the fact that 12 year olds are getting these older phones and wanting Android on them, asking this one and that one "hey, can u put android on dis, cuz it wood be reely kewl", instead of doing their own work, leeching off others to get what they want.

At least thats how I see it in America...
[Tilt, TyTN II, MDA Vario III Android Development] unilizer:
I've tried this kernel in combination with CM7.1 RLS3, but I'm having troubles to install android with this kernel. I've used Atools to modify the type of keyboard. Anyone having an idea of what goes wrong?

@ PoXFreak: I see that you're using a kernel of scoot with CM7.1 RLS3. Is this the kernel form this thread or an other one?

->Solved: I tried it a fourth time with flashing a new kernel (The same from this thread, but modified again with Atools) and now it's working. Don't know what went wrong, but it works... :)
[Tilt, TyTN II, MDA Vario III Android Development] PoXFreak:
You did apply the update attached to the OP, correct?

If not the /cache partition won't work and you'll get data corruption, if it even works at all.
[Tilt, TyTN II, MDA Vario III Android Development] mrbryan:
Have any vogue users gotten a version of this kernel working with Scoot's VyanogenMod 7.1.0 v3?

I've tried flashing the VOgue NBH here, modifying it or the kaiser one here and saving for vogue first...

All give me force closes for system & com.android.phone process when they boot up and won't connect to my mobile network or save info i put into APN

Sorry for the double post (this is in the ROM forum too) just thought I might get someone else knowledgeable here too

Cheers
[Tilt, TyTN II, MDA Vario III Android Development] mrbryan:
Have any vogue users gotten a version of this kernel working with Scoot's CyanogenMod 7.1.0 v3?

I've tried flashing the VOgue NBH here, modifying it or the kaiser one here and saving for vogue first...

All give me force closes for system & com.android.phone process when they boot up and won't connect to my mobile network or save info i put into APN

Sorry for the double post (this is in the ROM forum too) just thought I might get someone else knowledgeable here too

Cheers
[Tilt, TyTN II, MDA Vario III Android Development] PoXFreak:
AFAIK Scoot didnt include the Vogue in this kernel, but someone else posted here that they had reworked the kernel to work with the Vogue, only difference is instead of a 20mb cache he made a 30mb cache.
[Tilt, TyTN II, MDA Vario III Android Development] daedric:
Just for the record, i installed Scoots latest (RL3 EN) CM7, and i did not have to apply androidupdate.tar to get the /cache partition mounted.
[Tilt, TyTN II, MDA Vario III Android Development] scooter1556:
This is correct, I posted before but the post went missing overnight, CM7 includes the modules for this kernel so no need to apply any updates to it.
[Tilt, TyTN II, MDA Vario III Android Development] n2rjt:
I have a kernel that I built, supposedly with the separated cache partition support. I have an atools.py that I modified to allow selection of cache size as well as system/data size, for both vogue and polaris/kaiser variants.

Now I just have to gather the courage to wipe out the kernel I've been running so happily for so long, in order to test this. I need my Tilt to be a phone today, but tomorrow will switch to my Wizard phone and do testing on the Tilt.

The kernel is based on Scoot's changes, and the atools is strongly based on something posted a few weeks ago that only worked for Vogue. The resulting mtdparts parameter looks correct on paper but has not been tested.

Update: works nicely. I've tried several partition sizes. I'll post stuff tonight.
[Tilt, TyTN II, MDA Vario III Android Development] chromax64:
Just to confirm, I got scoot's kernel (20mb cache verified with df -h) and cm 7.1.0 rls3 working on polaris 100. woohoo, nice one!
[Tilt, TyTN II, MDA Vario III Android Development] PoXFreak:
Sounds great n2, I was hoping someone would push this through.

If you need a tester, I have fixed the 600 bad blocks on my spare. I can use it as a benchy tilt to check stability (won't be a true benchmark since it has 0 bad blocks now...hehe).

I'm also still playing with building a replimenu for the touch pro/fuze, just because there isn't one and noone wants to push the development of this phone.

Think Dream/G1 with more ram and NAND and better display properties... my #1 reason for working on it.
[Tilt, TyTN II, MDA Vario III Android Development] n2rjt:
Updated Atools

Thanks to scooter1556 for the cache fix! And thanks to l1q1d for Atools, and to agungwap for editing it to work with the cache partition on Vogue. I have put in my attempt to update Atools to allow editing the cache partition size.

I hope l1q1d will look at this and perhaps give me pointers if I have done anything the wrong way. I'd like to get it copied up to the main atools repository.

I have also changed the initrd slightly, but I don't think the changes are necessary to get this to work. I'll be uploading my source code soon.

This should work on Kaiser, Polaris, and Vogue, although I have only tested it on Kaiser (Tilt). I would appreciate feedback from Vogue and Polaris users.
[Tilt, TyTN II, MDA Vario III Android Development] beely:
I am using this kernel + cm v6

it works really good..

thanks, will try v7 soon.!!!
[Tilt, TyTN II, MDA Vario III Android Development] PoXFreak:
I'll give it a try n2... What did you need to change in the initrd?
[Tilt, TyTN II, MDA Vario III Android Development] n2rjt:
The change isn't required, just handles an unlikely case:

If you select 0 for cache size, cache partition is not created.

So if you install on NAND with 0 cache size, init will use the old method of symlinking /data/tmpcache to /cache. In other words, you'll get a corrupt-causing install and will complain that things are broken.

I didn't see Scoot's initrd changes in git anywhere, so I extracted them from an installed system. I can put it into the sourceforge git (bootenv) but first want to resolve a couple of things about busybox that had me puzzled.

a) tinboot comes with an initrd.lzma that has busybox with a different size. I need to search the forums to see why that changed and which is really the better version. For me, the tinboot version works but the bootenv version treats mostly all commands as if they were "su".

b) the initrd folder in bootenv has separate copies for things that should be hard links. I have a change to the build script that fixes this. However, in its current form, the script still ends up with two copies of busybox, and I'd like to get it down to one.

After I get those things straight, I'll commit and push. Then after figuring out the new RIL I want to build a new Fresh Froyo that uses the latest google apps plus the new RIL. Since I've finally figured out odexing, it boots quickly and leaves lots of room on the data partition.
[Tilt, TyTN II, MDA Vario III Android Development] cupidon192:
Hi n2rjt! Can I change the size of system or data partition?
[Tilt, TyTN II, MDA Vario III Android Development] n2rjt:
Yes size of system, data, and cache partitons can be adjusted. It is not tested by very many people yet. Try it and let me know good or bad results.
[Tilt, TyTN II, MDA Vario III Android Development] cupidon192:
Ok, I'm testing this kernel with Scoot's CM7.1. It run fast and accurately and now I'm checking partitions with "df -h", I see 4 partitions in screen. I hope my data would be lost like other kernels when I clear Davik cache

mmcblk0p1 : sdcard

mtdblock2 : system : 90M

mtdblock3 : data : 114.1M

mtdblock4 : cache : 10M

Edit: I tested with "clear Davik cache" function by reset some times, and no longer missing data, perhaps I would try more. Another things run well, thanks n2fjt, Scoot and l1q1d.
[Tilt, TyTN II, MDA Vario III Android Development] PoXFreak:
I believe I would stick to the bootenv version since "su" is the way to go in our case. Lets face it, we're not dealing with anything "stock" here and nothing is hard-coded IMO.

As far as the RIL goes, I think some changes need to take place.

a) When phone first boots, data is not available, forcing an airplane mode. :(

b) (Not sure if this is a worldwide issue but) when the modem app is used to drop the PPP and reissue an IP and subnet, if the data link was in HSPDA mode it upgrades to HSUDA mode (essentially "real" 3G). When the phone is moved far enough to connect on another tower, the phone changes the PPP and subnet again but returns to HSPDA mode. Also, even though data and phone are available, (no service) is shown on lock screen.

Will I have to reinstall CM7 after the kernel install, or is it possible to just "make room" for a larger cache?
[Tilt, TyTN II, MDA Vario III Android Development] n2rjt:
No, what I meant was that with the bootenv version of busybox, none of my commands actually work. I type "ls" and get just another prompt. Then I type "exit" and get a prompt. Then "exit" again and it exits. So the "ls" command actually issued "su" or "sh" instead.

For me, the data indicator shows no data after boot, but I really get data. If I go airplane mode and back, the icon shows correctly. Sometimes it corrects itself without me doing anything. Lately I just leave it alone and eventually it shows. I have never had problems actually having data connections with this ROM.

I have always understood "H" (HSDPA) to be faster than "3G" (UMTS), so that if both are available the phone chooses "H". I rarely see 3G indicator.
[Tilt, TyTN II, MDA Vario III Android Development] PoXFreak:
10-4 man, I couldn't see what you were doing on your screen...lol.

Anyway, I set mine up as 90mb sys, 96mb data, 30mb cache last night.

I had to reinstall CM7 but was able to get my settings back with the backup I made last week.

So far so good, and the ability to adjust cache size along with system/data sizes really made it a whole lot easier to adjust the system size accordingly.

Thanx for your hard work man, it's well appreciated.
[Tilt, TyTN II, MDA Vario III Android Development] l1q1d:
Good work n2jrt, please update it to the sourceforge repository and git.
[Tilt, TyTN II, MDA Vario III Android Development] n2rjt:
L1q1d, I put it on sf but forgot about git.

Should I increment the minor version and rename it to atools-1.2.2.py? I didn't want to change the version without your approval since it is your tool.
[Tilt, TyTN II, MDA Vario III Android Development] l1q1d:
change it to 1.3.0 and add you and scoot on credits :-)
[Tilt, TyTN II, MDA Vario III Android Development] PoXFreak:
One word...

NICE!!!

One (minor) change I would make is to the cache partitioner, where it now allocates memory in 5mb steps I would change it to 1mb blocks. Same with system/data partitions...

I wish I knew everything there is to know about this as I would help everytime I sit in front of the PC.
[Tilt, TyTN II, MDA Vario III Android Development] n2rjt:
Atools 1.3.0 is at sourceforge and git.

Enjoy!
[Tilt, TyTN II, MDA Vario III Android Development] MTom:
I tried several options such as

if the CPU is set to 520

cache 20 is a stable and fast but no 3G data connection.

I'm starting to go crazy into

what would be the best option

sys and data Nada?
[Tilt, TyTN II, MDA Vario III Android Development] Userius:
Haret

Hi,

Is there any way to extract this kernel so as to use it when booting from haret? I mean, how to get files zimage and initrd out of it?

Thanks in advance.
[Tilt, TyTN II, MDA Vario III Android Development] n2rjt:
The separated cache magic of this kernel is only needed for NAND installs.

It does nothing to improve haret, as far as I know.
[Tilt, TyTN II, MDA Vario III Android Development] WnG88:
Scoot,

Any chance you can figure out how to get .32 working with mass storage on windows?
[Tilt, TyTN II, MDA Vario III Android Development] cornelha:
Finally!!

I have been holding off on using android permanently on my kaiser, every now and then I would pop in, grab some new toys and flash then finally go back to winmo after a day. Been using this kernel with scoots CM 6.1.2 RLS6 for 2 days now and I havent had anything weird happen. Battery life is not what it is on winmo but this is way better. Great job man keep up the good work!
[Tilt, TyTN II, MDA Vario III Android Development] cliffdover:
i cant install

Hello,

I tried to install eclair but i receive messages of low disk space... What can i do?
[Tilt, TyTN II, MDA Vario III Android Development] PoXFreak:
You need to look for problems in NAND memory, specifically "bad blocks" errors on install. If you do have bad blocks, you need to reformat the NAND, which is tricky.
[Tilt, TyTN II, MDA Vario III Android Development] daedric:
I belive the issue is with eclair's (the one i'm thinking) extremly large /system.
[Tilt, TyTN II, MDA Vario III Android Development] cornelha:
Installed Scoot CyanogenMod 7.1.0 RLS3 and the battery performance is much better, no more waking up in the morning at 15-20% when it was fully charged before going to sleep. This just keeps getting better and better
[Tilt, TyTN II, MDA Vario III Android Development] Speedy1980:
Hey,

installed this kernel here and tried Scoot CyanogenMod 7.1.0 RLS3.

Everything is working perfect....

But does somebody know about the camera issus?

The camera is working for taking photos but if i´m trying to use some barcode software but problem seems that the software wants to autofocus....

Does someone has an solution or the same problem?

Many greetings and thx for this great job everybody has done.

THX
[Tilt, TyTN II, MDA Vario III Android Development] PoXFreak:
10-4, just shows how long I've been at this game.

I'm suprised you got the camera to work at all, I have not been able to take one picture with this build since installing it. I may go back to a generic froyo build because of it.
[Tilt, TyTN II, MDA Vario III Android Development] SpeedySurfer:
Try using the scrollwheel on the side to manually focus.

Also, this kernal is awesome, phone has been alive for the longest since I had winmo. If this got merged with Krazy-Killa's one it would be epic.
[Tilt, TyTN II, MDA Vario III Android Development] mattempus:
new froyo

Hi!

I've found this new froyo rom:

sourceforge.net/projects/androidhtc/files/2011-08-29-froyo/

Did somebody make this rom works with the cache kernel? If I want to apply the kernel's update it says "write error, not enough space".

Currently I'm using Fat Free Froyo, I think it is the fastest release. But it isn't stable, and none of the other roms are. They always freezes 1-2 times a day.

I'm using 1.70.19.09 Radio.

Does somebody have a stable phone? If yes, how?

I don't mind if it's slow, just don't freeze...

Thanks!
[Tilt, TyTN II, MDA Vario III Android Development] n2rjt:
That is Fresh Froyo from he Vogue forums. I built and uploaded it. You need to use atools to make sure your system partition in the NBH is large enough for what is in androidinstall.tgz plus the androidupdate.tgz that comes with the NBH. Try a large system partition first. After a sucessful install, you can resize and do it again with system being only as large as necessary.
[Tilt, TyTN II, MDA Vario III Android Development] mattempus:
Oh I see, great job anyway! And is it worth to try? I suppose you are using it. Does your phone stable?

I like every rom, all of them are great and i see much work on them but sadly i haven't found a rom that keeps my phone up for 2 days...

Everybody writes in the forums that his release is great, stable, super fast but how? I don't understand...

Anyway i appreciate your job, thanks!

Best regards
[Tilt, TyTN II, MDA Vario III Android Development] n2rjt:
I think mostly stability or lack of it is due to the kernel. Since June everyone is using the same kernel. Fresh Froyo is basic but stable and yes the only build I use.
[Tilt, TyTN II, MDA Vario III Android Development] mattempus:
Thanks, it seems it's working. I hope it will work forever :)

I edited the androidupdate.tar and get rid of the ipv6 modul, that was 5 MB. After that I could apply the update. I'm a little afraid of NAND flashing again :)

The only thing is not working is the built in hotspot tether, with wifi tether application it works.

Oh and the market can't find applications that i search for. Strange... but that doesn't bother me.