yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
Haven't made much progress with the kernel lately :-(. I have a new phone on the way which will free this one up for full-time testing. :-D

I currently modified my kernel with a hack to allow caching using the mtdblock3(data partition on NAND), which has sped up my kernel's performance as well. But stability remains the same which proves it's something else.

I want to try using Power Collapse instead of Apps Sleep. Hopefully I will have some success in getting that mode to work. I have some ideas I would like to try, and will attempt to test them during the week.

Also I'm going to implement Scoot's caching technique to help with stability, and faster loading of apps. :-)
[Tilt, TyTN II, MDA Vario III Android Development] PoXFreak:
I think the separate /cache partition on mtdblock4 is your next step towards good stability. If not for EXT4, I would give this one a try. Only one kaiser to use right now (600 bad blocks on the other one, nearly new phone).

Anyway, really good work on this build. There's not many Devs out there still working on this because of the technology it's built on, but you guys ROCK for keeping the lowly Kaiser alive!
[Tilt, TyTN II, MDA Vario III Android Development] dany547:
any news man?sorry but my PC was "down" ,now i can make you the splash screen :D just tell me what do you want me to implement in the design?
[Tilt, TyTN II, MDA Vario III Android Development] dany547:
PNG-8bit,tell me what you think man :D i will refine it tomorrow it's a lil pixelated!
[Tilt, TyTN II, MDA Vario III Android Development] mbze430:
has this kernel project been close or abandon?
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
I haven't fully abandoned it, just haven't had any time to work on it, but not a day goes by I want to get back into working on it.

Now that my Kaiser is no longer my primary phone, when I do get time I plan on working on the kernel without regard to what happens to the phone.
[Tilt, TyTN II, MDA Vario III Android Development] mbze430:
thank you for the reply... now I feel more comfortable to try it out. Seems like you are the only person that has added CPUFreq in to the kernel. (then again, I haven't been able to read through all the threads... I haven't even looked at my Tilt since 2009)

I will assume what has been written on OP still stands?
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
The files on the OP should still be valid, but if they are not let me know and I'll fix it. :)
[Tilt, TyTN II, MDA Vario III Android Development] mbze430:
RLS 5.9.2.2 (No Boot Logo)

I downloaded RLS 5.9.2.2 (No Boot Logo) and I wanted to know if I need to make any changes in aTool?

Apparently I did have to... since I have about 100blocks of bad NAND and didn't fit by the "default value".

just to make sure I only changed the Panel type and the System and Data. I didn't change any thing with the CPU/GPU setting.. I am assuming your CPUFreq will take care of that?

--------------------------

Also I didn't read much in regards to the the broken USB Mass Storage in this thread since it was mentioned in FEb/11. Has that been addressed or it's a lost cause?

--------------------------

Finally got some time to test out the CPUFreq. I am using CPU Spy. It was able to pick up the CPU marks

528mhz, 384mhz, 245mhz, 122mhz, 81mhz, and Deep Sleep

During the 2:34hr of charging it was @ 384mhz the whole time. Once unplugged I was able to put it to sleep and it started to count in the Deep Sleep.

However as of right now I am unable to get the cpu to anything else besides 384 even on heavy use.

Gonna try a CPU management control App tomorrow.
[Tilt, TyTN II, MDA Vario III Android Development] PoXFreak:
Incorporate mtdblock4 for cache, decrease CPUFreq thresholds to better manage full-speed as opposed to sleep modes and this will be one killer kernel!
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
Unfortunately I noticed it too lately as I went back and checked on my Kaiser. I believe it's due to the actual android build not supporting CPUFreq. The kernel now supports it, and before the Android Build boots, the CPU is changing frequency constantly (and if you sit at the Boot Menu, it drops to 124MHz), but as soon as the Build loads it locks at 384MHz.
[Tilt, TyTN II, MDA Vario III Android Development] jairoch:
Haret installation problems

Hi KK,

I Have not been able to do haret installation (after click run, phone freezes). I wanna install system and nand on ext4 partition as you have it.

I got default.txt from atools, just added "pm.sleep_mode=2" and set system sd partition sp2, data sd partition sp3, swap sd partition sp4.

In order to match with default.txt settings, the install-seq.sh mounts system on sp2, and data on sp3.

Obviously, I partitioned my sd card this way: SP1 (2G) on fat32, sp2 (250M), sp3(1.4G) and sp4 (450G) on EXT4.

I compared the "install-seq.sh" generated from atools with your "install-seq (Full SDCard)" and the only difference is that yours mounts system on sp3 and data on sp4, isn't it?.

Please let me know where is the error, and how I must install it.

Thx in adavnce.

--

set RAMSIZE 0x07300000

set RAMADDR 0x10000000

set FBDURINGBOOT 0

set MTYPE 1553

set KERNEL zImage

set initrd initrd.lzma

set cmdline "no_console_suspend pm.sleep_mode=2 ppp.nostart=0 clock-7x00.ahb_div=4 clock-7x00.a11=450 hw3d.version=1 mddi.width=240 mddi.height=320 board-kaiser-battery.battery_capacity=2160 board-htckaiser.panel_type=2 board-kaiser-keypad.atttilt=1 clock_7x00.grp=0xa99 sys_partition=/dev/block/mmcblk0p2 data_partition=/dev/block/mmcblk0p3 swap_partition=/dev/block/mmcblk0p4 lcd.density=120 fstype=4 haret_divisor=2200"

boot

--
[Tilt, TyTN II, MDA Vario III Android Development] mfsr98:
Look, I'm a noob. I don't know how to install :s. Is it just format, paste files and run haret.exe?

thanks
[Tilt, TyTN II, MDA Vario III Android Development] drfno1:
Thanks for the effort on our Kaisers, thought I'd check this out. When data and system on nand using wifi (test sim) the combo was rock solid. When I put in my sim (can only get EDGE because of my location/provider), the connection service drops frequently (I saw this reported in Scoot's thread). Also started getting lockups white screen and black screen on wakeup. Clearing dalvik cache fixes the problem but sometimes apps are lost. I tried 2 different radio's, same results.

Tried the latest nbh to move data to sdcard. I formatted my card to 1 fat32, 2 ext4, and linux swap partitions. The install failed to mount and create the /data and changed one ext4 partition to ext2. Tried this with 2 ext2 partitions, same result no /data mount.

Hope this helps you, looking forward to this working.
[Tilt, TyTN II, MDA Vario III Android Development] gnatto:
KO!

mmm, don't know if it is only for me, but I am stuck on the blue arrow circling round and round at the beginning of the system booting... Where did I go wrong? Was my kaiser too old perhaps? ;-)
[Tilt, TyTN II, MDA Vario III Android Development] gnatto:
OK!!

mmm, don't know why, after the third reset it started correctly...

I will appreciate any update...

Thank you!!!
[Tilt, TyTN II, MDA Vario III Android Development] tiagoclc:
Backup

The problem persists. Fails when backup script tries to mount databackup.img.
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
I have corrected the issue.. Though currently from what I had gathered, I had to erase my databackup.img, as it was pretty messed up to begin with.

I'll be uploading the new kernel to my OP. I'll edit my post when the new kernel is up. :)
[Tilt, TyTN II, MDA Vario III Android Development] WnG88:
Will this kernel work on Vogue (I guess through atools)? and will your modified Scooters CM7 work as well? I haven't had much luck with Atools, can someone post a vogue version of this kernel please if it is possible?
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
This Kernel will work for the Vogue, infact the baseline coding is Vogue, so I can't really remove support for the Vogue without removing support for the Kaiser and Polaris, lol. Atools will work with this Kernel, I have been using atools to test my EXT4 features, as well as adjusting /system and /data partition sizes.

My re-packaged Scoot's CM7 build should work with Vogue. Basically it should have the same capabilities as the original. :)

I'm going to be out of town this weekend (getting together with Family), so I won't be able to do much updating until Monday.
[Tilt, TyTN II, MDA Vario III Android Development] Leryan:
mmm, Polaris support.

sounds very good for me, i'll try as soon as released. :D
[Tilt, TyTN II, MDA Vario III Android Development] czar_au:
Has something changed in Bluetooth between Rls1 and Rls3?

In Rls3 I can't activate Bluetooth. Seem to work fine if I Drop kernel back to Rls1
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
I've enabled Polaris support in my latest version, but testing for stability yet again.. Probably not the greatest build to run but ran into some problems while trying Polymod 2.1D. Very fast with my kernel, but phone showed signs of corruption, even before rebooting: Apps refused to load, either FCing and just not opening. Couldn't open Settings, only thing that worked was LauncherPro and that was the latest app installed.

Nothing's changed with Bluetooth across all RLSs. In fact Bluetooth still works here, and I'm using Polymod 2.1D at the moment. Which build are you running, and did you apply the androidupdate.tar file?
[Tilt, TyTN II, MDA Vario III Android Development] daedric:
Doubt: How about trying to implement USB OTG?

It is it completly IMPOSSIBLE on the kaiser ?
[Tilt, TyTN II, MDA Vario III Android Development] tiagoclc:
Same problem here.

Bluetooth doesn't work in Rls3 combined with cyanogenmod 6 - 5.25...
[Tilt, TyTN II, MDA Vario III Android Development] tiagoclc:
Data corruption!!!

Lost 2 apps after reboot pressing soft reset button...

What about implement another filesystem, like jaffs?
[Tilt, TyTN II, MDA Vario III Android Development] czar_au:
I'm using Customized CM7 RLS1 from post 1
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
I'll look into it. Though not sure why Bluetooth is not working, it's no longer a module, so should be enabled regardless if you have the androidupdate.tar or not. Try checking the androidupdate archive, and see if there is a bluetooth.ko file in it.

I'll do some research on JFFS, and see what can be done to integrate it into the init and kernel, if it's safe to use it inside the NAND, and what changes to the NAND need to be made to make it compatible with JFFS2

After going through JFFS2's features, advantages, and disadvantages towards NAND devices, I have concluded that using it would not be wise. JFFS2 is VERY sensitive to read/write blocking and buffering. Until the developers, or heck even myself can confirm that our data corruption is a File System problem (YAFFS), or our NAND driver, JFFS2 will not be implemented into my next kernel. Also, the JFFS2 source needs re-write to be compilable as there is a problem with the source code that controls the node writes for JFFS2. If I had a spare device to where I can torture test the NAND driver (therefore possibly permanently damaging the NAND), I would gladly do it myself using the tools built into the MTD subsystem.

Ok, from the sounds of it, it's not isolated to builds, but hardware. czar_au and tiagoclc, what is your Kaiser model?

OTG? I think you're refering to fixing the mounting to computer issues that has plagued kaisers since day 1. I'll take a look at the adbd daemon, and see what's up.
[Tilt, TyTN II, MDA Vario III Android Development] daedric:
USB OTG:

USB On-The-Go, often abbreviated USB OTG, is part of a supplement[1] to the USB 2.0 specification originally agreed upon in late 2001 and later revised.[2] The specification allows for devices that generally fulfill the role of being a slave USB device (e. g. digital audio player or mobile phone) to a USB host (usually a desktop or notebook computer) to become the host themselves when paired with another USB device. The latest version of the supplement also defines behavior for an Embedded Host which has targeted capabilities and the same USB Standard-A

As in, connect a usb pen to the usb port and access its contents, or a keyboard and use it on the kaiser, or other devices.

(Though USB Mounting of the SD card is also a request!!!! :D)
[Tilt, TyTN II, MDA Vario III Android Development] l1q1d:
i can confirm that it's a nand driver issue (my polaris is now destroyed).
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
I had a feeling it was the NAND driver. I'm currently looking at the code right now, to see what's wrong.

One thing that caught my eye is when I check the actual directory structure of YAFFS2 after awhile, I begin to see garbled file names and directories, which could indicate that the NAND driver is not using correct specifications for our Kaiser's NAND chip.

Anyone have the NAND chip specifications for our Kaisers?
[Tilt, TyTN II, MDA Vario III Android Development] scooter1556:
http://xdaforums.com/showthread.php?t=320994
[Tilt, TyTN II, MDA Vario III Android Development] l1q1d:
The only difference (after my latest update on nand driver) is the ecc check (/drivers/mtd/devices/msm_nand.c):

/* CMD / ADDR0 / ADDR1 / CHIPSEL program values */
if (ops->mode != MTD_OOB_RAW) {
dma_buffer->data.cmd = MSM_NAND_CMD_PAGE_READ;
dma_buffer->data.cfg0 =
(chip->CFG0 & ~(7U << 6)) |
((chip->last_sector - start_sector) << 6);

MSM_NAND_CMD_PAGE_READ should be MSM_NAND_CMD_PAGE_READ_ECC but generate errors.
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
Well, should of saw this coming, but I now have about 100MB worth of bad blocks near the front of my NAND. Unable to install /system on NAND no matter how far I move /data. Currently only way to go for me is /system on SD Card and /data on NAND or both on SDCard. I tried working on the msm_nand.c file, tried the _ECC change liek above, ended up getting constant msm_nand_read_oob errors. I guess I didn't restart the phone fast enough....

I'll release my "fixed" Kernel, once my android installation boots up, and no other issues pop up with NAND.

Unfortunately, as this is my only Kaiser, I won't be making any more changes or contributing, unless another hammydown Kaiser falls on my lap.
[Tilt, TyTN II, MDA Vario III Android Development] tiagoclc:
It could be usefull

* DaVinci DM6446 EVM board which utilizes the Samsung k9k2g08 part...

http://www.mail-archive.com/davinci-linux-open-source@linux.davincidsp.com/msg08865.html

https://source.ridgerun.net/svn/leo...tloader/u-boot/src/cpu/arm926ejs/da8xx/nand.c

*plus* http://www.mail-archive.com/davinci-linux-open-source@linux.davincidsp.com/msg08905.html
[Tilt, TyTN II, MDA Vario III Android Development] daedric:
Isn't it possible to clean all the (possibly) bad sectors and let the driver re-check ??

I can't possible belive you simply damaged 100mb of sectors on one try.

Wasn't there a mtty command to clean that?? i vaguely remember that... perhaps from other devices...
[Tilt, TyTN II, MDA Vario III Android Development] tiagoclc:
Krazy, try this

Tutorial explaining how to format nand using a program called task29

http://xdaforums.com/showthread.php?t=644781

Remember, if ur going to try "task 2a", flash 1.65.17.10 radio before. It will be necessary to unbrick phone if something goes wrong.

There's something about MotoQ Drivers. You'll need this to proceed with unbricking stuff.

This method works to unbrick if task 2a break your phone: http://xdaforums.com/showthread.php?t=394584 / Follow from step 4

Some other stuff:

http://xdaforums.com/showthread.php?t=371154

http://www.youtube.com/watch?v=DtTDuc4V4cU

http://xdaforums.com/showthread.php?p=3433851#post3433851

Found this too: "-Run 'task 2a' via mtty to fix bad blocks", but be careful. Red this first: http://xdaforums.com/showthread.php?t=352381

and this: http://xdaforums.com/showthread.php?t=412200#post2457194

this too: http://xdaforums.com/showthread.php?p=1966166

also this: http://xdaforums.com/showthread.php?t=439360

post #6 of this thread: http://xdaforums.com/showthread.php?t=657654

one more: http://xdaforums.com/showthread.php?t=425922

:) http://xdaforums.com/showthread.php?t=393337

this post could help if something goes wrong: http://xdaforums.com/showthread.php?t=394584

unbricking after task 2a: http://xdaforums.com/showpost.php?p=5369709&postcount=438

Well, good luck!
[Tilt, TyTN II, MDA Vario III Android Development] tiagoclc:
2.6.25 nand driver

what happens if i use 2.6.25 nand driver with 2.6.32?
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
You'll run into incompatibilities and plus the nand driver from 2.6.25 will not compile for 2.6.32 without beng rewritten.
[Tilt, TyTN II, MDA Vario III Android Development] tiagoclc:
Krazy

Did you try to fix bad blocks?
[Tilt, TyTN II, MDA Vario III Android Development] l1q1d:
The 2.6.25 has the same bug but it's less problematic (we don't know why).
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
Not yet, will be reading up on that actually here in about an hour or so. Will post the results soon.

After reading up on what task 2a does, i'm very skeptical on using it, as unfortunately as I've said, this is my main phone, though stupidily I shouldn't have tried tinkering with anything that could damage the phone itself, but i'm not bickering, it was my mistake and I'm accepting that.

Currently, no commands in MTTY work with my Kaiser except getdevinfo, info 8 or all other commands that I've come across on different forum posts, do not work, hell task 29 doesn't even work from what I saw. So for the moment, I'll just have android on an SD Card. My NAND is far more damaged than I thought. My /data partition cannot hold information now. I receive data corruption within 20 minutes of android being installed on NAND /data side. Even rolling back to l1q1d's "develop" kernel 2.6.32 corrupts around the same time.4

So for the moment, my NAND is pretty badly damaged, and possibly loading WinMO will not work, so I've just loaded android completely on SD Card, which granted my EXT4 modification is working wonderfully, no slow down of any kind using android on SDCard now. :)
[Tilt, TyTN II, MDA Vario III Android Development] tiagoclc:
speed up download

I'm using data on ext4 partition.

I've made a nand partition of 60 mb on mtdblock3.

I don't know how to edit initrd. So, I put a symlink on sysinit.rc, linking this partition to /cache folder.

******

Doesnt work well. only 8KB/s on market downloads

I decided to try something new.

Using an hex editor I've modified system partition to 1MB and gave the rest of nand space to data partition.

Installed system on sdcard.

I noticed no speed decrease and an increase on the battery's life.

No data corruption until now.

******

>>CM 6.1.2 RLS6<<

sysinit.rc lines:

mount yaffs2 /dev/block/mtdblock3 /data/tmpcache
symlink /data/tmpcache /cache

______________
userinit.sh lines:

mount -t ext4 -o remount,noatime,data=writeback,barrier=0,nobh,errors=remount-ro /data

rm -R /data/data/com.android.vending/cache
mkdir /cache/marketCache
ln -s /cache/marketCache /data/data/com.android.vending/cache

rm -R /data/data/com.android.browser/cache/webviewCache
mkdir /cache/webviewCache
ln -s /cache/webviewCache /data/data/com.android.browser/cache/webviewCache
[Tilt, TyTN II, MDA Vario III Android Development] l1q1d:
warning: use nand as tmp dir will destroy blocks faster.
[Tilt, TyTN II, MDA Vario III Android Development] tiagoclc:
Its only for downoadfile.apk.

Its already downloading to /data/tmpcache...
[Tilt, TyTN II, MDA Vario III Android Development] n2rjt:
Bluetooth doesn't work for me either, using RLS3 kernel and Fresh Froyo.

I have an AT&T Tilt. Maybe the problem is specific to radio versions?

What radio version is known to work with this kernel?

And, how do I confirm my radio version from Android or bootloader?

Regarding NAND, we have a kernel problem with the NAND driver, but unfortunately every developer so far who has tried to fix the problem has fatally damaged their phone. Back when DZO was developing for Vogue, he mentioned that the NAND driver had a bug. I think we are all in agreement on that issue. How to fix it? We are at an impasse, until someone finds a way to experiment without killing the phone.

So, last question: what is the status of the git repository for the 2.6.32 kernel? Last time I tried, I couldn't build a working kernel from git.
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
Hm... Well, to be on the safe side, here is my current kernel, that I'm currently using on my Tilt right now. It's about as stable as all other kernels out there, and no issues with NAND being corrupted so it's safe, lol.

There is a minor modification to msm_nand.c, but it refers to the ECC checking algorithms, and since those are disabled in the driver, they do nothing. I'll post my msm_nand.c file in this post for any developer wishing to take a look. Changes were made to the msm_nand_oob_64 function.

ECC is still currently "disabled" in msm_nand.c, and YAFFS is now configured to fully utilize it's own ECC checking without help from the NAND driver.

Now, I am able to do /data on NAND, but I still get corruption, but I'm ruling this as possible NAND damage now as it happens very frequently, even with older kernel builds. If anyone wants to test this kernel out, feel free to do so, but I will warn you, I do not know what will happen now that my NAND is damaged.

I quoted "disabled" as there are command lines that enable ECC in the msm_nand.c, but they are not used, and even so I am unable to tell if ECC is in fact disabled by the driver. With YAFFS doing it's own ECC checking and doing it's own ECC tagging, it might help alittle bit with corruption but I can't guarantee that.
[Tilt, TyTN II, MDA Vario III Android Development] scooter1556:
The git source is fine, it hasn't changed since the last time i commited changes and it built fine then :)
[Tilt, TyTN II, MDA Vario III Android Development] tiagoclc:
Differences between Davinci nand driver and our nand drvier

Its about DaVinci:

* We actually have 40 bytes of ECC per page, but the nand_oobinfo

* structure definition limits us to a maximum of 32 bytes. This

* doesn't matter, because out page_layout_item structure definition

* determines where our ECC actually goes in the flash page.

__________________

The nand chip used in DaVinci is the same used on Kaiser.

The following lines is present on the last msm_nand.c posted by Kaazy_Killa

/**
* msm_nand_oob_64 - oob info for 2KB page
*/
static struct nand_ecclayout msm_nand_oob_64 = {
.eccbytes	= 40,
.eccpos	= {
0, 1, 2, 3, 4, 5, 6, 7, 8, 9,
10, 11, 12, 13, 14, 15, 16, 17, 18, 19,
20, 21, 22, 23, 24, 25, 26, 27, 28, 29,
46, 47, 48, 49, 50, 51, 52, 53, 54, 55,
},
.oobavail	= 16,
.oobfree	= {
{30, 16},
}
};

/*
* msm_nand_oob_128 - oob info for 4KB page
*/
static struct nand_ecclayout msm_nand_oob_128 = {
.oobavail = 32,
.oobfree = {
{70, 32},
}
};

Lines used on nand.c (DaVinci nand driver) https://source.ridgerun.net/svn/leo...tloader/u-boot/src/cpu/arm926ejs/da8xx/nand.c

static struct nand_oobinfo nand_dm355_hw10_512_oobinfo = {
.useecc = MTD_NANDECC_AUTOPLACE,

.eccbytes = 32,
.eccpos = {6, 7, 8, 9, 10, 11, 12, 13, 14, 15,
22, 23, 24, 25, 26, 27, 28, 29, 30, 31,
38, 39, 40, 41, 42, 43, 44, 45, 46, 47,
54, 55,
},
.oobfree = {{0, 6}, {16, 6}, {32, 6}, {48, 6}},
};