yashsingh1/xdaforums huggingface dataset:
[HTC Desire S] CdTDroiD:
Nice work dude ;) pitty all the drama from the virtuous side again lol... carry on chopper! open source for all lol
[HTC Desire S] Adidas108:
kernel is good but i faced with battery drain...
[HTC Desire S] bail.de:
battery is nice, but in combination with miui 1.8.26, everything feels a little bit slower / more laggy... just not as smooth as the included kernel that came with miui...
[HTC Desire S] amonrei:
Reflashing 1.1.0 in Hydrogen v4. Will see how it goes.
[HTC Desire S] bail.de:
don't know if it's a miui issue or tiamat:

i've been using the combination for 3 days now, but suddenly speaker and mic stopped working...

is this the audio issue i read about on the last few pages? i thought i downloaded the kernel after you announced that it is fixed.. reboot didn't solve it, should i wait for an update?
[HTC Desire S] tcchuin:
Overclocking seems has no actual effect on this kernel . On miui, I overclocked and set the governer to performance, the result is the same. While the result is better when on stock kernel. Both tested on similar maximum frequency
[HTC Desire S] superkid:
Well, i have that thing, overclocks works and everything is faster! but i get same scores as no overclocked :P
[HTC Desire S] tcchuin:
But why is the result improved when using stock kernel?
[HTC Desire S] amonrei:
Ah i guess it's Hydrogen that's causing the drain not Tiamat 1.1.1. Oh well i'm on MIUI now. :D
[HTC Desire S] vampire36:
I had told u...
[HTC Desire S] amonrei:
Yup. :p Just wanted to see the result myself.

On MIUI 1.8.26 with Tiamat 1.1.1.

Haven't undervolt & underclock and it just uses 10mA sleeping.

Will see what happens if i set minimum clock to 192mHz & undervolt by 75mV like i did with 1.1.0.
[HTC Desire S] tcchuin:
are you using battery monitor widget?or current widget?
[HTC Desire S] bioan:
New version of tiamat kernel is out! Here is the changelog tiamat-dev.com/7x30-changes/
[HTC Desire S] amonrei:
Battery monitor widget.

Undervolt & underclock doesn't seem to affect idle power usage. Still around 10mA. Not sure if full load.
[HTC Desire S] fosco_:
From the Tiamat 1.1.2 Changelog:

So we are close to getting official saga_CM7? Great! ;)
[HTC Desire S] tcchuin:
Still no improvement in benchmark when overclocked, does this mean overclocking is not supported on this kernel while stock kernel supports?
[HTC Desire S] docertabum:
unity kernel has 2-way call recording. does tiamat have something similar?
[HTC Desire S] sayeed91:
Does tiamet have any issues with the miui rom?
[HTC Desire S] amonrei:
Seems fine here.
[HTC Desire S] bjohv052:
Works with stock kernel for me, I'm on nexx's 1.0.5.
[HTC Desire S] Jan_Joris:
Nope, i use it without a problem. In fact, i love this kernel.
[HTC Desire S] nsmart:
Callers volume too loud with Nexx Cyanogenmod 1.05 and Tiamat 1.1.3 on DesireS

When I install Tiamat 1.1.3 on Nexx Cyanogenmod 1.05 the callers volume is much too loud. I know there is some kind of volume boost within this kernel.

After restart of device the callers volume is always on its maximum. For my ears the lowest setting is loud enough, so I set the callers volume to lowest possibe setting.

On outgoing call - when I press volume down - with one press the volume goes from max to low. It seems to remain so until restart of device.

On incoming call - volume always resets to maximum on every incomming call. I have to lower the volume on every incoming call as maximum volume is a pain the ear.

This way I cant use Tiamat kernel, although the smartassv2 is a real improvement, I experienced no Scrolling lags after recovering from standby as with smartass governor. I would like to change to Tiamat kernel because everyone using it says it is a battery saver. Is there a chance this will get fixed ?
[HTC Desire S] matthewsucks:
Erm. Noob question. Is my desire s a 8x60 or 8x50?
[HTC Desire S] nsmart:
Desire S has Snapdragon MSM8255 cpu.
[HTC Desire S] Fidoble:
The problem or "feature" has been reported by me and others in the CyanogenMod thread.

Nexx said that he will contact the devs of the Tiamat kernel to sort this out.

I personally don't think that the sound should be boosted, but just follow the standard behavior.
[HTC Desire S] amonrei:
I thought we have Snapdragon 8255?
[HTC Desire S] nsmart:
You are right, i got confused because on tiamat-dev.com the changelog for kernel 1.1.3 is listed under "Snapdragon 7×30".

Desire S has CPU Instruction Set "ARMv7" and Modell Number "MSM8255".

http://en.wikipedia.org/wiki/Snapdragon_%28system_on_chip%29
[HTC Desire S] amonrei:
Yup i'm confused why it's under 7x30 on tiamat dev as well. :o
[HTC Desire S] skumara:
I want to know also. is there a 2 way call recording in this kernal?
[HTC Desire S] shrome99:
The Msm8255 is under 7x30. It's confusing, but correct.
[HTC Desire S] shrome99:
Caynarib, have you 'fixed' the excessive volume boost?
[HTC Desire S] Tectas:
Has anyone else no sound at calls (I don't mean the ringtone), no matter if using speaker or not?

I'm using miui 1.9.23.

With cyanogen kernel it works but not with tiamant, any suggestions?

Update:

Read the answer, sry that I found it as late!
[HTC Desire S] Nexx:
MSM8255 is part of the MSM7x30 family, it's got a higher number because of the clock speed. Other than that they're identical.
[HTC Desire S] skumara:
Sorry just found the answer in changelog

sent from my desire s with cyanogenmod
[HTC Desire S] skumara:
version 1.1.5 is out with the volume boost fix.
[HTC Desire S] amonrei:
Thanks for the update. :)
[HTC Desire S] djsubtronic:
Does 1.1.5 also resolve the issue where in call volume is always reset to maximum after reboot no matter what setting you had it on before?

Edit: Never mind, just tested and confirmed this bug still remains. Surely this cannot be difficult to resolve? Is this thread even monitored anymore?
[HTC Desire S] gkenga:
I noticed there is no scary governer in this kernel, whats the alternative?
[HTC Desire S] Nexx:
This is a confirmed CyanogenMod bug djsubtronic, it's not something that a kernel can fix.

I know at least 1 other CM dev is aware of it and I believe it's actively being looked into.
[HTC Desire S] djsubtronic:
Interesting. Thanks for pointing that out. For some reason I thought the stock kernel didn't have this bug but it does.
[HTC Desire S] olyloh6696:
Will there be anymore updates to this kernel in the future again?
[HTC Desire S] Wody05:
Hey guys,

could need some help. So I'm on MUI 2.1.20 (Gingerbread) and of course my phone is a Desire S.

Now I wanted to flash Tiamat Kernel becuase I'm experiencing wake lags ._. which I really can't stand ^^

So now I downloaded Tiamt 1.1.5 -> recovery -> wipe cache/dalvik-> flash kernel...

1) Is it flashed? Because system info still says CM Kernel...but maybe that's normal?

2) Wifi doesnt work anymore

3) Is wake lag fixed with Tiamat? At least heard so...

...Tried to mount system partition first but didn't work either

Thx in advance
[HTC Desire S] Tectas:
Won't work, this kernel is for gingerbread not ics and even there it is outdated and not recommended to use.
[HTC Desire S] Wody05:
Well it is Gingerbread ;)

But thx for the info I will try Reaper Kernel...
[HTC Desire S] shrome99:
The tiamat kernel is outdated, and it causes problems with the latest CM7 source (on which MIUI is based). I recommend the Reaper kernel.
[HTC Desire S] Wody05:
Was my first idea too :) done that and it's great :)!

Thx anyway ;)!
[HD2 Android NAND Development] mally2:
thumbs up,

but angel, you said you tried try task 2a, one user claimed that bad blocks indeen get fixed with task 2a,

may be this tool will help, but the user is in his own rights to release it or not

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

another thread about bad blocks

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

regds
[HD2 Android NAND Development] AngelDeath:
The first Thread states task 2a, which I have performed, and has done nothing, if it worked trust me I wouldnt have made this post. The second is in the General section, not much of an attention getter, and I am part of that thread as well, but I gave a bit more detail.

Unless I did something completely wrong and some others I have read ith the same result of it not working, I'd love to know how the task 2a did it after 3 attempts back to back.
[HD2 Android NAND Development] ph03n!x:
Thanks @AngelDeath!

It would be helpful if the quoted part is elaborated, just so that people not in the know can know how do check the recovery logs.
[HD2 Android NAND Development] pyrorob:
my 2 cents, i had an hd2 for a whole year flashing winmo roms on it and not an issue, ive been runing android on my hd2 since January and ive had to send in my original and the replacement hd2 ive had into the htc service center. both started showing bad blocks, the second also froze and restarted when it got slightly warm. im on my third hd2 now, they ended up sending me a brand new one.. i hope this one lasts longer then the last 2...

from my understanding normally the device is supposed to mark off bad blocks so they dont get written to, so you dont get read errors and weird stuff doesnt happen, this doesnt appear to be happening..also try running a winmo rom and feeling how hot your hd2 gets.. from my experience it hardly gets hot at all, install android and you can feel the device cook, im thinking that the heat might be affecting the nand and various other chips leading to these issues.. and i believe this is due to something with how android is writing data to the nand (most apparent right at the initial setup after installing a android rom), its causing the chip to get wayyyy to hot and leading to these effects..
[HD2 Android NAND Development] marzinho:
+1 to this, i would also like to know how to check this...
[HD2 Android NAND Development] AngelDeath:
You may very well be right in your way of thinking, but I think it also has to do with what rom your using as for it getting hot, and the reason why I say that is aside from say navigation apps most non-sense roms run cool for the most part, and sense roms run warm normally, unless your playing a graphic intense game, I would think it getting hot under normal use would be if its not over clocked then the battery frequency could be the cause, but you could very well be right and it could have something to do with it. In my case though my phone has never gotten hot at all except using a navigation app, which i think is normal but doesnt omit that it can happen then too.
[HD2 Android NAND Development] AngelDeath:
Okay since people are asking, here is a short step by step for both EU and TMous:

1) Format your Boot, Data, Cache, System, Dalvik Cache (Eu users your Dalvik Cache is on your sdcard on the SD-EXT)

2) Flash your rom.

3) After flashing DO NOT REBOOT.

4) Go to Advanced, then Error Report.

5) This will copy the Recover.log to your SDCard.

6) Go Back and enter Mount & Storage.

7) Mount USB SD.

8) On your computer navigate your SD Drive.

9) Look for a folder called: clockworkmod.

10) Inside you will find a file called: recovery.log

11) Copy this to your Desktop.

12) Open with Wordpad or Notepad++

If you see in that whole log, Could not erase blah blah bad block, or anything that says bad block, with the exception of a location called "system/xbin/badblocks" (This location is normal hats a file name), then you have bad blocks, and the more you have, the smaller your cwr partition actually is.

Also added this to post 1 incase it gets lost as this thread probably will get large.
[HD2 Android NAND Development] jpl69:
Did you tried to flah stock HTC win 6.5 ?
[HD2 Android NAND Development] AngelDeath:
Yes hence using a goldcard to bring it back to factory default. I thought that statement would have been self-explaintory, my apologies if it wasnt.
[HD2 Android NAND Development] mootmetal:
i agree with pyrocop about what he said ... and i can see the difference in my phone ...here's the situation :

with wm the phone wors as it should be i can reboot the phone and do what i want.

with android i cant reboot the phone ... if i reboot the phone stuck on android screen ( the one befor the boot animation) no matter what i do ...and the same thing if i shut down the phone and turn it on after a short time ( less than 2 mn) i always ned to wait between 2 and 3 mn after the phon is off ...

for me the probleme is not the rom itself ...i get this probleme even with clean install and only recovery installed :

with magldr it stuck on go go go screen

with clk i get some caracters and " suspend" in the end ....nedd to wait 2 mn ...

so maybe the recovery it self has something to do ...befor arrinving to the rom
[HD2 Android NAND Development] Rick_1995:
This is a total myth that task 2a or task 29 fix bad sectors.

Bad sectors in hardware cannot be fixed unless the NAND itself is replaced on chip level which is impossible as manufacturers attach it to the main board using ball connection and with epoxy on top.

What does task 29 does then ? -> It clears out the partitions on your nand by writing 0x00 (which is 0 in binary) to them.

What does task 2a does then ? -> Well, even i was uninformed about this specific function of SPL, so studied it a bit and here are my conclusions.

Task2a cleans the nand COMPLETELY including the partition layout, try info 8 after and before task 2a (you must be having a stock WM before doing this, i did this using 3.14 stock). Well, it did clear the partitions including the splash which is totally white for me after this task.

Also, i had some interesting findings, after seeing that my splash was gone, i wrote a small ARM program to read NAND and display the data in terms of pixels on screen and wow, a pattern. Task 2a writes 0 and 1 alternatively instead of 0's or rubbish data as in task 29.

Here is the picture of my program running after task 2a:
[HD2 Android NAND Development] 05081983:
This would explain why my HD2 was freezing a lot whenever I used to install a new application, and this was not only happening in android but HD2 was freezing when I would install a new app in WM6.5 also. And then I would have to take out the battery and restart the phone again. Just for the information my HD2 was also getting very hot.

Hence I had to replace it with the other HD2 from Tmobile. Lets hope I dont face that problem again.

I would also like to know if we users can do anything to avoid this problem in future.
[HD2 Android NAND Development] arkatis:
Good posts and informative i must say!

Crying.............:(

So i will flash back to WinMo and will Never look for Android anymore! :o :confused: I don't want to fck up my phone!

Actually...if my phone fck$ up then i will trade with another Leo or Tmous from a friend of mine that sells/trades phones! So no worries about me! :rolleyes:

Also i read somewhere in Xda that task 2a MTTy commands can Brick your phone? CE, Radio, SPL, OS are deleted from phone..Is it true?
[HD2 Android NAND Development] mootmetal:
no ....and here's what get after running task 2a:
[HD2 Android NAND Development] arkatis:
Thanks for the info. As i can see the SPL can be backed up and you have an error block there which fails to delete it! Hmmm...

So the "doomsday" of HD2 will arrive in the nearest future?? I do not have this problem yet and i am flashing a new Rom every 1-2/3 days. Maybe i have bad sectors already but my phone is acting cool atm!
[HD2 Android NAND Development] Rick_1995:
As i mentioned in my post above, it formats EVERYTHING except SPL. so you can still enter the bootloader but the device will be void of Radio, Splash, OS and any other thing stored on NAND thereof.

It is suggested to flash an official ROM through sdcard after doing task2a to restore the splash, radio, Partition layout etc..
[HD2 Android NAND Development] Jimmersd:
I suspect that there are 2 possible reasons for this: Hardware failure due to heat or over use (overflashing). ROMs and to greater extent Ram and SSDs do degrade over time and are subject to loss of data. This is inherit to the device. Modern memory devices have enabled a TRIM feature and are much better at housekeeping but it is still an issue.

Software failure due to incorrect or malicious programming. Could it possibly be an issue having to do with low level permissions on the sectors? I can't think of a better way to hide a virus and permanently infect a device than to rope off a section of ROM.
[HD2 Android NAND Development] arkatis:
Ok some Sense Roms can Heat my HD2 really easy. Some others more light Roms aren't. So you can go to a more lighter Rom such as the Rom i have in my signature which is the smallest e.t.c. For me this Rom doesn't Heat up my phone because it doesn't use all that Resources like Sense Roms e.t.c

MY OPINION!

Now for the NAND flashing....I think it make sense to have some bad sectors due to 1000 flashing times. It's like an SD card, if it has bad sectors then your phone/PC says that the sd card has a problem and need to be fixed (Bad sectors)

On the other hand; NAND acts like crazy so you have SODs, WSDOs, reboots whatever. This is due to the unlimited flashing we are doing to the NAND thus the Bad sectors.

It's like Flashing a Custom Tuning Program on your Cars chip.(NAND), Professional Tuners says that they can only flash it about 10 times because after 10 times your Chip will fried. That's why you Buy a custom Tuned Chip for some cars like Japanese!

MY EXPERIENCE AS A STREETRACER :D

That's my 10 cents.:cool:
[HD2 Android NAND Development] AngelDeath:
Hey unconn, I was curious about something, sorry been away with issues the last few days, but I was looking at something, and wanted to know if you could do an info 8 with mtty 1.42, and then paste the output like I did in the OP.

I was doing some calculating of bytes and what not, but I wanted to see something. Thanks, will explain after, just dont have the time atm.
[HD2 Android NAND Development] Unconn:
AngelDeath, Did you get the info you wanted from the above post? I edited it and added the info.

On a side note: Last night I went back to a partition where 4 bad blocks where in my /userdata partition. I set my /system partition to 320mb, this forced the bad blocks closer to the start of the /userdata partition. Today I have noticed 3 random reboots. On the 3rd one my /userdata partition was 'reset'. I know this because my phone was reset to defaults and was asking me to set it up again (Touch the Android to start). I ADBed and found that all of the directories in /userdata were created today. I looked at the /data/data directory and all of the data was for only pre-installed apps. I can't really make a conclusion, but it sure seems like the bad blocks caused this. I have not had a random reboot for over week before this (when moving the partition addresses).

I am not sure what I will do. Maybe make a dummy partition to put my first bad block in. I want to test, but I also think that seeing more stability after this would be a test.
[HD2 Android NAND Development] TheInVisibleGoD:
Are you using cLK with the last 24Mb enabled in your /data part? I'm just asking because it seems there's a bug with latest cLK beta provided by daniel... if that's not your case, my bad!
[HD2 Android NAND Development] Unconn:
I am not using the last 24mb AFAIK. I never set it to. EDIT: I just reread his post about this. Thanks for pointing this out! But, I do not think this was my problem. I have just repartitioned so that my first 3 bad blocks are in /cache, my second one is way at the end of /userdata, and the last one has always been in last 24.

Let's see if I go back to having no random reboots.
[HD2 Android NAND Development] D3LTA:
Is there a way to easy check it through "Terminal Emulator" ?

or a easy tools to check for bad blocks (guide)?
[HD2 Android NAND Development] jcsy:
mtt 1.42?

let your device connect to Active Sync 4.5 or boot into Bootloaded (HSPL or SPL)

wait for it to connect via USB

on active sync, disalow USB connections

launch mtty 1.42

select USB instead of COM1/COM2 (if you did it correctly, u will see USB option)

type info 8 in the cmd area

PS : do not follow the infos.txt included in the zip unless you want to format everything :D
[HD2 Android NAND Development] sagarjawaress:
I flash MAGLDR ROM using CWM and i use 150 mb partition as suggested in the ROM thread. Also, i have noticed that if i do not wipe data/factory reset in CWM, i can boot the ROM successfully (in clk). But many a times i get bootloop(many times on mag and few times on clk). But most of the time, i get success on clk! Today i flashed ladymiui on clk which i could not boot with magldr. But i am worried that if such things goes on,i have to flash back win mo and boot Android only from sd. And for the SENSE ROMS which require EXT partition, boots both on mag and clk.
[HD2 Android NAND Development] D3LTA:
--- 2K bytes sector version ---

DEVICE NAME=hynix_h8BES0UQ0MCP
DEVICE ID=0xBC
DEVICE MAKER ID=0xAD
PAGE SIZE=0x800
TOTAL PAGE SIZE=0x840
BLOCK COUNT=0x1000
BLOCK PAGE=0x40

Checking block information

BLOCK 0 (0x0) is reversed block
BLOCK 1 (0x1) is reversed block
BLOCK 2 (0x2) is reversed block
BLOCK 3 (0x3) is reversed block
BLOCK 8 (0x8) is reversed block
BLOCK 10 (0xA) is reversed block
BLOCK 11 (0xB) is reversed block
BLOCK 12 (0xC) is reversed block
BLOCK 13 (0xD) is reversed block
BLOCK 14 (0xE) is reversed block
BLOCK 15 (0xF) is reversed block
BLOCK 28 (0x1C) is reversed block
BLOCK 29 (0x1D) is reversed block
BLOCK 30 (0x1E) is reversed block
BLOCK 31 (0x1F) is reversed block
BLOCK 439 (0x1B7) is reversed block
BLOCK 440 (0x1B8) is reversed block
BLOCK 441 (0x1B9) is reversed block
BLOCK 442 (0x1BA) is reversed block
BLOCK 443 (0x1BB) is reversed block
BLOCK 683 (0x2AB) is reversed block
Partition[0], type=0x23, start=0x2, total=0xFE
Partition[1], type=0x0, start=0x0, total=0x0
Partition[2], type=0x0, start=0x0, total=0x0
Partition[3], type=0x0, start=0x0, total=0x0

CE Total Length(with sector info) = 0x80800
CE CheckSum Length(without sector info) = 0x80000

hynix anyway better then samsung as it comes to Bad Blocks ?
[HD2 Android NAND Development] Unconn:
I am not sure. But you have nothing to worry about in the above report.
[HD2 Android NAND Development] D3LTA:
If i read here, i've got the idea that it is unavoidable

or am i wrong
[HD2 Android NAND Development] Hacksor:
So I booted into the bootloader (red, green, blue screen) and connected via usb (screen says USB and the connection sounded on the computer), but when I open mtty there is no usb option. =( not that I'm actually worried about bad blocks as I don't seem to have any issues as of yet, but I was curious...^_^
[HD2 Android NAND Development] roloracer:
Next time you flash your phone before your first boot, in cwm choose error report, and it will make a recovery log in the cwm folder in your SD card, then open it with notepad or something similar and you'll see them if you have any.

Honestly I don't worry about the blocks simply because until somebody finds a way to fix the bad blocks there's nothing anybody can do, we already know that they don't come just from flashing, also aging hardware is a factor , I know I have bad blocks but that's not going to keep me from enjoying my phone and my flashing to the fullest, if it dies oh well, it will be time for an upgrade for me.

Sent from my CM7HD2
[HD2 Android NAND Development] ph03n!x:
Something from logcat:

08:16:00.250 Info /system/bin/fsck_msdos 63 Next free cluster in FSInfo block (507813) not free
08:16:00.250 Info /system/bin/fsck_msdos 63 FIXED

Does this mean fsck scans or *can scan* the file system? At boot? And fix errors? Mark bad blocks??

Note: Am a Linux/ Unix novice - all I know is fsck scans/ fixes file system error :) Can someone enlighten me?