yashsingh1/xdaforums huggingface dataset:
[Fascinate Themes and Apps] TheSonicEmerald:
People just post up the icons and dock images on XDA and other places. Just download them and select the image after choosing custom icon/dock.

Rockin' DJ05, Liberty Gingerbread, Clocked at 1.2ghz Voodoo5

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

DD username: TheSonicEmerald
[Fascinate Themes and Apps] Bigloof:
I get most of mine from here - http://launcherpro.droidicon.com/
[Fascinate Themes and Apps] DarthCivicus:
Dio you have to use better cut our ninja morph to be able to change the icons?
[Fascinate Themes and Apps] Bigloof:
Long press on the shortcut to change the image.
[Epic 4G General] Esteway.619:
I don't know if this has been answered yet I was wondering why we don't have a overclock kernel for dk28. Thanks In advance for your answers.
[Epic 4G General] mrzood:
No source code for DK28 has been released.
[Epic 4G General] flopez76:
Questions in Q&A please, and No Source = No Overclock
[Epic 4G General] brian2220:
at least it went here instead of the dev section

good job op :D
[Epic 4G General] sryans2004:
Exactly!!
[Epic 4G General] thetruejay20:
So where did we even get DK28 in the 1st place?
[Epic 4G General] 063_XOBX:
It was leaked fully compiled
[Epic 4G General] thetruejay20:
So there is no way to make a custom kernel with no source?
[Epic 4G General] 063_XOBX:
Not a practical one, it can be done but takes a LOT of work in comparison to one based off of source code
[Epic 4G General] thetruejay20:
Ok thanks I was wondering about that for a bit now!!
[Epic 4G General] arashed31:
[derail]

DJ29, DK05, DK17, and DK28 were all leaked within a matter of days from each other. And after that we haven't been given any new leaks. Was the guy who released the builds fired?

On top of that, DK05 and DK28 were compiled within 23 days of each other. The differences between those two were pretty big and if development continued at that rate, we would have a released build by now. Perhaps Samsung took a break for the other phones?

[/derail]
[Epic 4G General] running_the_dream:
Nice observation.
[Tilt, TyTN II, MDA Vario III Android Development] clemsyn:
**** EXT4 for DATA (SD) install on second post *****

I've been slowly working on our Kaiser Kernel hoping to get extra life from it. Here are the changes I made so far.

1. Updated to the latest initrd and made a few changed in the init file

2. Changed the default I/O scheduler to noop.

3. Added block data integrity support and v4 support

4. Updated the latest yaffs2 filesupport up to changes dated 1/14/2011

5. Added PM module for Qualcomm 7500 chip

Will try to add BFQ I/O scheduler and see how the performance is compared to noop.

1/29/11 ** UPDATED KERNEL for better YAFFS2 best suited for Kaiser Samsung Memory chip **

Here is the nbh. This is type2 screen and keyboard1.

Will release my latest changes and update to git (need help on this one) when stable.

Please reinstall ROM and wipe data after flashing the kernel. The changes in yaffs2 code might cause issues. You can restore your data from BACKUP after installing the ROM.

************ TO FORCE CHECKPOINT IN DATA PARTITION PLEASE DO THIS IN TERMINAL *******************

su

echo 6 > /sys/module/yaffs/parameters/yaffs_auto_checkpoint

sync

This will change auto checkpointing to 2 and create a checkpoint.

This is just temporary, the checkpoint is deleted in reboot so the commands have to be done before every reboot.

One solution is to use Gscript.apk and type the commands in Gscripts. Execute via Gscript before reboot :)

**** To verify if you have checkpoint in Data Partition Please do in Terminal ******

To verify if you have yaffs2 checkpoint in the data partition Type the following in terminal

su

cat /proc/yaffs

Scroll down to Device 2 "userdata"

scroll down and look for "blocks_in_checkpt" should be 1 or 2 (not 0, if it is zero then you have no checkpoint in data partition)
[Tilt, TyTN II, MDA Vario III Android Development] clemsyn:
Update 2/7/2011

******************EXT4 FILESYSTEM FOR SD INSTALL***************

Because of bad blocks on my Kaiser, I have to give all NAND partition to install on system while installing data on SD with EXT4 filesystem. Here are the requirements:

1. An SD card with at least class 4

2. A way to partition and format your SD with FAT/ext2/Ext4 (ext2 should be as small as possible), I use Ubuntu for this.

3. Kernel with ext4 support (this will format your whole NAND partition to use system and use EXT4 on SD for Data)

Instructions:

1. FORMAT SD (I use Ubuntu DiskUtil) with FAT/ext2/EXT4, on my 8GB SD I use 7gb for FAT/8mb for ext2/1gb for EXT4 but it's your call. The most important part is that you only give the second partition (ext2) the least amount of size.

2. Download the KAISIMG.zip, extract and you will get a file KAISIMG.NBH

3. use Atools to edit accordingly with your Kaiser's screen type and keyboard (NBH is using screen 2 and keyboard 1)

4. Flash the KAISIMG.NBH

HERE IS WHERE IT GETS TRICKY!!! PLEASE FOLLOW THESE INSTRUCTIONS CAREFULLY!!!!

a. PRESS CENTER D PAD to enter ANDROID Installer

b. Choose (*) Sys on NAND

Choose (*) Data on SDCard Partition

c. Scroll Down to Install System and choose it

d. This will wipe your Existing system! Are you sure CHOOSE (YES)

e. Would you like to clear data too (Suggested) CHOOSE (NO) ***DO NOT CLEAR DATA OR THIS WILL CHANGE YOUR THIRD PARTITION TO EXT2 and will not work.

That's it. After installation reboot and you have an optimized ext4 on your SD for data. The mount options for ext4 in this kernel are:

data=writeback, barrier=0, nobh, noauto_da_alloc

Will use barrier=1 for better data security on next release, just enjoying the speed of barrier=0 for now :)
[Tilt, TyTN II, MDA Vario III Android Development] -Arturo-:
Yes, Clemsyn If it's not a big problem please update 2.6.25 too. Thank you.
[Tilt, TyTN II, MDA Vario III Android Development] mt1976:
updates kernel 2.6.25

This would be nice. Thank you :)
[Tilt, TyTN II, MDA Vario III Android Development] clemsyn:
It would take awhile though since I have to remove my 2.6.32 kernel to put 2.6.25 since I'm limited in space. Donations for a laptop HD would be appreciated :)

UPDATE:

1. I think one of the reasons of data failure is that YAFFS refuses to write a checkpoint for our data partition. It writes it in the system partition with no issues. The new yaffs2 (updated 1-27-11 which I will update shortly) allows forcing checkpoint so I'll try that one and see if I can create a checkpoint on our data partition.
[Tilt, TyTN II, MDA Vario III Android Development] clemsyn:
Finally got a checkpoint in my userdata partition...instructions posted on first post, no update on yaffs needed :)
[Tilt, TyTN II, MDA Vario III Android Development] aceoyame:
I have a 20 GB Sata laptop drive I could get to you. Used to be in a 360 and then broke the enclosure open for a hdd when the one in my laptop died. Drive works just fine, just small lol
[Tilt, TyTN II, MDA Vario III Android Development] clemsyn:
Sorry about your phone. I was hoping you could test out my new kernel. ANyways, I think yaffs2 was having issues creating a checkpoint on the data partition since yaffs was only creating a checkpoint on proper unmount (which was not done in our kaiser). The latest yaffs can make us force a checkpoint by simply typing the command in the first post and typing "Sync" on terminal automatically creates a checkpoint in data partition. I'm currently testing it now and seeing how it goes.

BTW, I'll take that donation re:HD since I can use it as an external HD and put the 2.6.25 kernel there and improve it (that is if wife permits).
[Tilt, TyTN II, MDA Vario III Android Development] aceoyame:
lol she's really not that strict, she just thinks my development for our devices is a waste of time. Just PM me where to send it and ill get it out to you.
[Tilt, TyTN II, MDA Vario III Android Development] clemsyn:
Agreed, that's what my wife thinks too :) I'll PM you my location

BTW, please make sure that the location of yaffs_auto_checkpoint is in /sys/module/yaffs/parameters (some ROM might have it on modules).

UPDATE:

Checkpointing is working great for me so far. Command on first post has to be executed in every reboot to create a checkpoint :( so typing the commands in first post before rebooting will create a checkpoint and save data partition (me thinks).

You can install Gscript and run the script before reboot

To verify if you have yaffs2 checkpoint in the data partition Type the following in terminal

su

cat /proc/yaffs

Scroll down to Device 2 "userdata"

blocks_in_checkpt should be 1 or 2 (not 0, if it is zero then you have no checkpoint in data partition)

Can anyone help adding this to the shutdown script?
[Tilt, TyTN II, MDA Vario III Android Development] clemsyn:
I've done 5 restarts, 2 battery pulls and 2 resets, made sure data partition was checkpointed before doing so....So far data partition has been OK with no FC's or errors, no lost apps with 18mb's left in data partition :) The thing that surprises me is that Phone Storage size hardly changes in size in every reboots so it's good news :) I have a feeling we finally nailed down this data corruption issue, but only time can tell since I will shift to prolong use before doing any restarts...

I have sent a PM to scooter hoping he can help me with a shutdown script so we won't need a Gscript. So far, Gscript is doing it for me. Upong reboot, I run the script and make sure I have a checkpoint in data partiion :)
[Tilt, TyTN II, MDA Vario III Android Development] scooter1556:
I've got it working in a script, i have it in a script which is run on startup and then again on a successful shutdown. I'll upload a couple of updates in a bit :)

EDIT: I have attached 2 updates to the post, one is for cyanogenMod based builds and the other is for all other builds such as fresh froyo etc.

Clemsyn, i have the latest yaffs source compiled into the kernel, i will commit it to git in a bit. With the latest yaffs a checkpoint is created every time sync is executed which makes scripts easier! :)
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
I downloaded the CM update, and it didn't enable the checkpoint, still had to enable it manually through terminal.

Testing the kernel right now however, and so far liking it.
[Tilt, TyTN II, MDA Vario III Android Development] clemsyn:
Thanks scooter, I'll try it out. I got stuck on a fake vsync and can't get out of it that I was unable to create a checkpoint and upon reboot without a checkpoint, everything was messed up. This is perfect, getting a checkpoint on startup and another in shutdown :) Thanks a lot.
[Tilt, TyTN II, MDA Vario III Android Development] scooter1556:
That's weird! So it didn't make a checkpoint on startup? I'm running the same script and init.rc and it works fine. I did push the file with adb though, did you fix permissions after updating?
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
Ooooooh.... Probably not, lol. I'll do that, and edit this post with my results.

*EDIT* Ok, I feel stupid. I still had an old androidupdate.tgz file in my sdcard andboot folder, and the boot menu used it instead of the correct .tar file... Hm, that explained why my Market stopped working, lmao.
[Tilt, TyTN II, MDA Vario III Android Development] scooter1556:
lol, rookie error ;)
[Tilt, TyTN II, MDA Vario III Android Development] clemsyn:
OK, it works on boot up since I get a checkpoint 1 every boot :) not sure about shutdown but if scooter says it works, I bet you it works in shutdown too :)

Scoot, I'm going to try to do a git diff and post it here so all the changes I've made in the config will be there.
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
Even with that little debacle, I had 0 corruption of data, or missing apps in my /data partition, and had to reboot 4-5 times, each time I used GScript to execute the command manually before shutdown. :)

And camera still works. ^.^
[Tilt, TyTN II, MDA Vario III Android Development] clemsyn:
That's great news and if my memory serves me right, you easily have data corruption in shutdowns and reboot. IMO, scooter's script is the best option we have for this issue and you don't have to remember to use gscript (especially from an old person like me with slight dementia :) Anyways, I'll continue on with my testing with this script. If it is still working after a few days, I'll try to add Namespace support, CIFFS, PPOE in our kernel.

BTW, here is my git diff and .config file. Please put it up in GIT. Thanks.
[Tilt, TyTN II, MDA Vario III Android Development] scooter1556:
Good stuff Clemsyn, i'll have a look through it :) So, apart from yaffs which has been updated is it just proc_comm.c and the defconfig which has been modified?
[Tilt, TyTN II, MDA Vario III Android Development] clemsyn:
yes, the only issue about the defconfig is that I forgot to enable yaffs to do it's own ECC and disable block refreshing (coz I think our memory is Single Layer Chip).
[Tilt, TyTN II, MDA Vario III Android Development] scooter1556:
No worries, i'll make sure those settings stay as they are :)
[Tilt, TyTN II, MDA Vario III Android Development] clemsyn:
Thanks, I just uploaded a new kernel with the following changes to yaffs best fitted our memory.
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
So far I haven't had any issues, but will know for sure tomorrow, but just saw your update and that you updated to YAFFS2 from the original YAFFS, which I'm looking forward to this update...

I'm backing up data, then flashing new kernel, installing system w/ data wipe, then wiping data again, then restoring /data from backup.
[Tilt, TyTN II, MDA Vario III Android Development] scooter1556:
How are things going using the noop I/O scheduler instead of deadline? I wasn't sure our NAND chip implementation was sophisticated enough to deal with optimising the I/O on chip. I haven't looked into it though so in theory if it does handle it ok noop should be faster!
[Tilt, TyTN II, MDA Vario III Android Development] clemsyn:
So far so good...I'm having no issues with noop :)
[Tilt, TyTN II, MDA Vario III Android Development] clemsyn:
Update...

Just performed a reboot and lost an app which was installed in sd-ext (I think it is installed in SD) which was Angry Birds :) but all the apps in data were still intact...performed another reboot and Angry Birds was back with all the apps :) Any ideas?
[Tilt, TyTN II, MDA Vario III Android Development] l1q1d:
maybe there is a problem on the cache.

Next time copy the logcat's output to a file.
[Tilt, TyTN II, MDA Vario III Android Development] clemsyn:
OK did a logcat and found this

D/vending ( 580): [14] LocalAssetCache.updateOnePackage(): No local info for com.rovio.angrybirds

So is it just the cache? Any idea on how to fix this?
[Tilt, TyTN II, MDA Vario III Android Development] clemsyn:
OK, just unmounted the SD card and Mounted it and everything is back again :)
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
Had corruption with framework, lost airplane mode and silent mode menu options in the "Power Menu".

Restored from backup, everythings normal.
[Tilt, TyTN II, MDA Vario III Android Development] clemsyn:
Thanks for the update...might need a bit more tuning
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
Corruption was definitely minor that time. :-) Keep it up!

*EDIT* Had an odd thing happen just now... I was in terminal emulator, just navigating the folders being retarded, when all of a sudden the physical keyboard froze while I was pressing ".", and it just kept looping it, over and over again.. Plus could not exit the app, as all the hardware keys were locked up except the power button on the side, oddly enough android was not affected performance wise, as I was able to pull up the power menu and power off the phone normally... Checking for data corruption now, and from the looks of it, no lost apps and no corrupted framework this time. :)

Will investigate this issue, and hopefully find the log file somewhere in the file system, lol.
[Tilt, TyTN II, MDA Vario III Android Development] clemsyn:
Are you still manually typing commands to create a checkpoint or using scoots? I have noticed that there are times that the userinit.sh still don't create a checkpoint that it should (I'd say like 5% chance of not creating a checkpoint). IMO, if the phone has not been turned off or rebooted for a long time, the checkpoint created at startup is not as reliable as the checkpoint created at shutdown and I'm not 100% percent sure that the shutdown script works since there is no way to check it. I still use my Gscript APK to create a shutdown script with these commands with su permission;

sync

poweroff -d 9 -f

this gives sync command 9 seconds to create a checkpoint and then it forces a poweroff. It works currently on my phone but I am also testing a different kernel with it, with different mount options for better speed. I don't even use my power button anymore, I just use the script :)
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
If I knew how to do scripts for Android, I would create a timer based sync program that would create a checkpoint every 30 minutes, that way we have a somewhat fresh checkpoint if the phone were to crash.

Maybe create one in the userinit.sh file during startup? Create a checkpoint at bootup (maybe give it about 30-60seconds after bootup before creating it), then continue to create checkpoints after that, every 15-30 minutes, give or take.
[Tilt, TyTN II, MDA Vario III Android Development] TuoNonno:
Don't worry, happens also to me sometimes, it's not an issue of this kernel because I use the kernel compiled on 29.11.2010
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
Well, got some bad news... Newest Kernel still has corruption occuring.

Here are the symptoms after about 1.5 days of use... Everything except LauncherPro was unusable. Apps were loading extremely slowly (including Market), and while the app is loaded, phone is extremely slow and barely responsive. Had 2 hot reboots occur because of the above, first time no corruption (at least as much as I can tell before the second reboot), second time, lost 5 apps, accounts & sync is broken (refuses to sync, and if it tries phone becomes unresponsive again and crashes)

Phone is also extremely hot, even when in standby...

Short list

All Apps except LauncherPro causes phone to become unresponsive or close to it

Lost 5-6 apps and Accounts & Syncs is completely shot as it refuses to sync or when it tries phone comes unresponsive and force reboots

Constant dialogs of FC or Wait buttons when opening any apps including Settings

Phone App now doesn't work (no signal or phone capabilities)

Going to try and do a full system reinstall (without backup restore this time -- ugh), and see what happens then.

Hope this helps. :)
[Tilt, TyTN II, MDA Vario III Android Development] clemsyn:
I've got a kernel cooking at the moment where I'm letting yaffs do all the work. I'll PM you a link later when I get it ready for you to try..I'll include an androidinstall.tar with it.
[Tilt, TyTN II, MDA Vario III Android Development] clemsyn:
UPDATE:

Finally got the filesystem to do auto-checkpointing :) Although sync command will still works and creates a checkpoint.
[Tilt, TyTN II, MDA Vario III Android Development] TuoNonno:
Nice news :)

Just a minor question: are you going to tune up also the camera driver or it is not in your plans?
[Tilt, TyTN II, MDA Vario III Android Development] dark_prince:
brother clemsyn, just a minor question over here.

Is there any way to fix the wake-up jiberish screen bug? Can it be made a "nicely Fade-in from black" rather suddenly giving a peek-a-boo of white?

Many thanks for your efforts brother
[Tilt, TyTN II, MDA Vario III Android Development] macondo62:
Hi Clem, thanks for your endeavor. I'd like to test your nbh, so I'm waiting for it... I have a minor question too: will be there any chance to get usb host under windows with .32nbh? P&L
[Tilt, TyTN II, MDA Vario III Android Development] n2rjt:
Thank you. I am also eager to try this.

Question for you, clemsyn: Would you advise a script that syncs periodically, like every 30 minutes, or is that more of a band-aid than a solution? In other words, does your new auto-checkpointing version eliminate the need for a periodic sync?
[Tilt, TyTN II, MDA Vario III Android Development] tiagoclc:
Donut?

I opened kaisimg.nbh from first post with atools and this file is made for donut!

Try to change it to froyo to solve FCs problems!
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
The Kernel is multi-supported in both Donut, Eclair and Froyo. Just set the kernel to which OS you plan on using, and you'll be fine.

I run Gingerbones which is Froyo 2.2.1, and I don't get any FCs.

Which I do want to ask if there are any updates on the latest kernel image? Last night my phone crashed while it was asleep, and after rebooting had corruption in the framework, calender was FCing, Gmail was GCing, Facebook FCed, and Google Framework FCed, plus lost a good chunk of apps. :(
[Tilt, TyTN II, MDA Vario III Android Development] mmec2:
When that happens, its often just the dalvik-cache that is corrupted, so if your terminal emulator is still working, you can

rm -rf /data/tmpcache/dalvik-cache

and then reboot.

The clear dalvik-cache option in the boot menu only clears the dalvik-cache for data apps and not system apps or framework. Anyone fancy changing this in git?
[Tilt, TyTN II, MDA Vario III Android Development] clemsyn:
Update:

Been looking at this kernel more closely and it seems like there is no actually issues with Yaffs file system. Checkpointing is good, but as more bytes is added to the data partition via writes, the more corrupt the data partition becomes. It seems like our issue is with the Nand driver rather than Yaffs, Yaffs detects our memory correctly but I'm not sure about the Nand driver. I've been attacking the nand driver but everytime I do, it keeps on adding bad blocks to my Nand so I'm being very careful with it. I have successfully made an NBH with an edited Nand driver to use our Samsung memory properly with sector size, write size and OOB but I cant seem to edit the erasefilesize and in the process of trial and error added like 4 bad blocks in every try. Will continue testing this NBH before release.
[Tilt, TyTN II, MDA Vario III Android Development] l1q1d:
hi clemsyn, i suggest you to look at this line

505 dma_buffer->data.cmd = MSM_NAND_CMD_PAGE_READ;

in the msm_nand.c, the original driver has MSM_NAND_CMD_PAGE_READ_ECC (as i remember). I think that it is the cause of the nand corruption.
[Tilt, TyTN II, MDA Vario III Android Development] mmec2:
That matches my experience too - I'm sure at least 75% of my corruption over the past months has happened while the phone was running "normally", not because of a freeze or bad shutdown.

eg I'll lose the settings for an app, then I look in the folder, and it seems there is now a new "settings.db" which has been created because the old one is now called "s5tyin&s.db"
[Tilt, TyTN II, MDA Vario III Android Development] hom.hom:
Random reboots

I have used this buil with both Scoot's Cyanogenmod 6.1 (RLS 5.5) and Gingerbones 5.25 ant both builds ran fine when just installed. I installed about five apps on both builds, and then shut down the phone. The next time I turned the phone, I really got a lot of hot reboots, even when I am not touching the phone it sometimes randomly reboots. Because this happened with two builds I suppose the problem is with the kernel?:confused: (I do realise Gingerbones is an stripped Scoot's, but still....)
[Tilt, TyTN II, MDA Vario III Android Development] Krazy-Killa:
clemsyn is looking into that. There's possibly a issue with the NAND Driver that clemsyn is checking into with the help of l1q1d.

Though my issue is different than yours, it's possible both issues are the same. :)

Sit tight!