yashsingh1/xdaforums huggingface dataset:
[HTC Desire S] Nexx:
We're linked on the top device list now ;)

Sorry but that's a job for the other kernels. The CyanogenMod kernel is a stock MSM7x30 kernel with Saga support, it won't feature improvements not in the stock CM code.
[HTC Desire S] bjohv052:
I spoke too soon, it works with stock (I'm not on nightly btw, but on 1.0.5)
[HTC Desire S] superkid:
There is a new nightly but no much diference :P

http://download.cyanogenmod.com/get/cm_saga_full-1.zip
[HTC Desire S] runagate17:
number 2 is up now.
[HTC Desire S] csandjaja:
Market is always FC while opening..i think i will re-flash google aps with old market.

Mine is use this rom + tiamat kernel 1.1.3.
[HTC Desire S] shrome99:
Will this be available via rom manager?
[HTC Desire S] nsmart:
Still volume boost with Tiamat 1.1.4

I tested nightly 15 and Tiamat 1.1.4. I still get the same painful volume boost and echoing as with Tiamat 1.1.3.

After restart of device the audible volume is always on its maximum even though the visible volume slider is set to lowest value. For my ears the lowest setting is loud enough.

On outgoing call - when I press volume down - with one press the audible volume goes from max to low. The visible volume slider stays at its lowest value. This remains so until restart of device.

On incoming call - audible volume always resets to max on every incomming call. The visible volume slider stays at its lowest value. When I press volume down the audible volume decreases significantly and the visible volume slider still stays at the lowes value.
[HTC Desire S] skumara:
i have it too...
[HTC Desire S] NiruBhai:
I'm not getting video and audio option in Google talk :-(
[HTC Desire S] sharper00:
Yep I had the same. I got tired of putting up with Tiamat's audio "features" so I'm going with the stock kernal. Smartass governer would be nice but I'm not prepared the compromise the main use of having a phone for a fancy CPU tweak!
[HTC Desire S] e2zippo:
Same here, back to stock kernel until it's solved..

What govenor should I use on stock when following the battery guide now that Smartassv2 is unavaliable?

cheers!
[HTC Desire S] JackyJack:
On Demand, good battery save but, unlike smartassv2, you'll notice some lag at the moment you need the speed boost (waking screen)
[HTC Desire S] e2zippo:
It's OK now, didn't even have to reboot, weird! ;)
[HTC Desire S] sharper00:
I set interactive as the default and for when the screen is off. Possibly not as good on battery but it should be better for lag. For night time and low battery (less than 30%) I set it to the power save governer.
[HTC Desire S] Tectas:
Android is based on linux not windows there's no need to reboot ;)

Translate those pages with google translate and you know the difference^^:

Windows

Linux
[HTC Desire S] Nexx:
Little update:

After some discussion with the CM devs, we've agreed that the Smartass governor really isn't ideal and can cause more issues than it solves. It won't be brought into the stock kernel, however we're in the process of making "interactive" the default governor. It should solve all the "stuttering" when coming out of sleep and hopefully also improve battery life.

Hopefully we'll reach a stage where the stock kernel is the preferred default and the Tiamat kernel is an optional extra for anyone who wants more features.

Personally, if we can improve battery life in the stock kernel sufficiently, I'll likely use that.

I'll keep you posted =)
[HTC Desire S] djsubtronic:
Thanks for the update. Is there any chance you could elaborate slightly on the highlighted part?
[HTC Desire S] nsmart:
I would not bet to much on that. I switched the governor from "ondemand" to "interactive" one hour ago (Nightly 15 + stock kernel). On first sight everything was ok, recovering from standby was fast.

But now I just hold my phone in my hands and everything is really slow. Swiped through the homescreens for about 30 seconds and the cpu is still at 245MHz. I switched back to "ondemand" an everything is fast again. Seems that the "interactive" governor has some problems when recovering from standby. I never had these problems with "ondemand".

I dont have SetCPU installed.
[HTC Desire S] Nexx:
From what I understand, SmartassV2 was derived from the interactive governor, but it caps the CPU clock when it ramps up, leading to longer execution time for processes (because it won't jump quickly to a higher setting than what it is hard-encoded for) and then actually wastes battery due to all the policy switching it does do.

It's generally considered to be a bad governor and won't be implemented in the CM kernel I'm afraid.

Are you running SetCPU? Try uninstalling anything which messes with the CPU speed, let the kernel handle it and then see. I've been running the interactive governor since this morning without any sign of slowness of the CPU speed getting stuck.
[HTC Desire S] shrome99:
What about regular SmartAss?
[HTC Desire S] Adidas108:
cm_saga_full-17 is online
[HTC Desire S] amidabuddha:
So what is the conclusion then?

We have to stick to the stock kernel and use the interactive governor?

With your RC1 1.0.5 and the Tiamat I had great battery life (4+ days) but not anymore (Nightly 16 + Tiamat 1.1.4). My system configuration is the same*, I have calibrated the battery but it goes down much faster now.

Please advise...

EDIT: *one difference - now I am with the new radio
[HTC Desire S] nsmart:
I dont have SetCPU installed.
[HTC Desire S] Nexx:
Look, before I say anything more....

I'm not hugely familiar with the ins and outs of the kernel. Whilst I can patch problems when they occur and introduce small features, the workings of the CPU governors are way above my head so I have to go by what I'm told.

SmartAss: http://www.ziggy471.com/2010/11/07/smartass-governor-info/

SmartAssV2: http://xdaforums.com/showthread.php?t=730471

You're free to use whichever kernel you prefer. My original aim was to bring SmartassV2 into the stock CM kernel because that was what Cayniarb was defaulting to in the Tiamat kernel. The CM devs I spoke to disagree about adding it in and gave some compelling reasons as to why, but again, I'm not a kernel developer. I have to go by what others say. They say SmartassV2 isn't better than interactive and it won't be included, I have to go with that.

As for the power difference between RC 1.0.5 and the nightly builds, I don't know. My phone has been running nightly 11 with Tiamat 1.1.4 and currently has 35% battery remaining after 4 days and 14 hours of moderate use.

No major changes have occurred in the device code since the RC builds, certainly nothing relating to power management. If a change has happened in the actual CyanogenMod code, then it's not something I've touched and it'll be difficult to track down =\

Hmm. Like I said above, I'm using the Tiamat 1.1.4 kernel with the interactive governor, but there's nothing which would cause the CPU speed to stick in the stock code.
[HTC Desire S] allen oddest:
oh my god, have u noticed what the current is on your phone?

My standby current is 14mA-18mA monitored by Battery monitor widget pro, and last no more than 30 hours with moderate use.:(

Now I am trying to use Tiamat 1.1.4 with undervolting 25/50mV and wanna see what happens.
[HTC Desire S] e2zippo:
Is it possible to install nightly releases via rom manager when i have 4EXT Recovery instead of clockwork?
[HTC Desire S] Tectas:
Dear nexx^^

Cause you're such tight with the cyanogen developers i'm hoping you can help me with my problem, it's just a minor issue but it's out there since long time ago and no fix is in sight.

I know that not much people noticed this but it's still present.

I'm talking about the bluetooth Mac address of HTC devices running cyanogen, it looks like they all got the same.

I don't know if it's related to an damn cheap Bluetooth chip with no unique address (I searched for such an chip but haven't found any) or if the address isn't read the right way, but I would like to know if it's possible to fix it and if not why.

Would be a pleasure if you could handle this, cause changing kernel doesn't solve the problem and it's present in every cyanogen ROM and cyanogen based ROM, build for HTC devices as much as I know.

Swyped from my Desire S
[HTC Desire S] Tectas:
Sure^^

Swyped from my Desire S
[HTC Desire S] amidabuddha:
Can you paste your MAC here, I want to check this (but no other HTC with CM around :P )
[HTC Desire S] Tectas:
At the moment it's 43:29:B1:55:00:00.

I figured this issue out when I tried to pair with an wildfire of an friend of mine ;)

I also tried it with an ordinary desire, the same.

But when i tried it with samsung devices, they had different mac addresses (not only different to htc also in between the samsung devices), so it looks like it's related to htc devices.
[HTC Desire S] e2zippo:
How do I do that, when i go to Rom Manager and search for new releases it says i must have clockwork recovery installed?
[HTC Desire S] Tectas:
The easiest way would be to reboot to recovery, choose instal from sd, search for your zip file and flash it.

There's also an option at rom manager where you can set that it accepts another recovery than cwm, but I don't know where to find it, sry I haven't used it long time^^
[HTC Desire S] Sn0opy:
Flashed the ROM for the first time today. Flashing and starting worked well, but i cannot open the Cyanogen sub-menu from the settings. Everytime I open it, it throws me back to my homescreen. "adb lolcat" throws a big exception which I could provide to you if you wish.
[HTC Desire S] f0xy:
I remember this issue got brought up when I was on wildfire. I thought it got sorted then strange :(
[HTC Desire S] Tectas:
the command you wanted to execute is

adb logcat

before this type

adb devices (to be sure adb is running, at the second line it has to show somehow "random" digits and characters, if not instal htc sync, maybe a missing driver, after that uninstall it [the driver is still present, it's just to prevent future issues])

adb logcat

;)

But try first to wipe cache, data and dalvikcache and reflash the rom, maybe this solves the problem ;)
[HTC Desire S] amidabuddha:
Yep the same. Strange :) Thank you

Open ROM manger, press menu hard button, select Manual Flash Override, select version 3.x.x.x. 4EXT is fully compatible with ClockworkMod, so now you can flash.
[HTC Desire S] Sn0opy:
Try adb lolcat, it's the same ;) I just did a dalvic cache wipe, because i wanted my apps to stay on the phone. Do you think this could be the problem?
[HTC Desire S] Tectas:
Ok, thx didn't knew that :)

Yes, but before wiping data try just to wipe cache and dalvik cache, that's in most common solving the proplem and it doesn't affect your apps.

For next time i would recommend you to use titanium backup to store your apps (including app data) on your sd ;)
[HTC Desire S] amidabuddha:
What was your previous ROM? Maybe a Sense one? ;)

When you switch to a new ROM without a full wipe there will be conflicts. Use Titanium Backup for your apps and reflash the ROM with full wipe. Reinstall TB, restore the apps and enjoy your new phone :)
[HTC Desire S] Sn0opy:
I used MIUI.us before. Will backup my apps and do a fullwipe now.
[HTC Desire S] djsubtronic:
Is any progress actually being made to resolve the lagging issues on the interactive governor?
[HTC Desire S] amidabuddha:
The best thing to do. There is nice installation instruction on the first post of this thread. It is there with a reason.

After you use CM some time and you are happy with it then you can upgrade to a next version only with /cache and /dalvik cache wipe to keep all your files and settings untouched...
[HTC Desire S] Sn0opy:
Thanks for the tip, but I already knew that. I'm running CM7 Nightly on my ZTE Blade for ~6 months now.

Btw.: even Titanium showed some old Miui apps. After Fullwipe everything worked well. This problem have had fixed by myself ... thanks anyway.
[HTC Desire S] Tectas:
I don't know, but I'm using the interactive governor about one day know and got no lags.

I'm running nightly 17.

---------- Post added at 12:24 PM ---------- Previous post was at 12:01 PM ----------

Sry, but if you knew everything, then you should have also known that an dalvik cache couldn't be enough, also wiping cache is the minimum you should do.
[HTC Desire S] dohnjoe:
Sometimes my main dock buttons disappear, see screenshot. Anyone else have this? It automatically seems to re-appear after a while or after a reboot....
[HTC Desire S] Tectas:
I think this is the 2. dockbar of adw.

Try to pull an icon on it to test it.

In common swyping up at the dockbar should make it appear.

With swype down you change back to the 2. ;)
[HTC Desire S] dohnjoe:
Thanks, that explains it!
[HTC Desire S] Nexx:
Ok, huge reply incoming ^u^

My standby current was 6-8mA last time I had battery monitor widget running. Please bear in mind that I live in a great signal area and I don't have a lot of stuff running in the background, just a couple of widgets and the automatic google syncing.

I'll look into this today, I too have that BT MAC address.

Been running interactive for over a day now, no lagging here =\ Do you have anything installed that monitors or messes with the CPU clocks?

The first time that happened to me, I reinstalled the ROM because I didn't know how to solve it -.- I'm not sure if there's a way to disable the ability to "page" that bar.
[HTC Desire S] amidabuddha:
Settings -> ADW Launcher -> UI Setting -> untick Dockbar

But when you know how to use it it is very nice feature (actually one of the things that made me stick to CyanogenMod) - you have another 7 shortcuts on one swipe away :)
[HTC Desire S] Nexx:
Handy! Thanks!

Bluetooth MAC Address:

I think I've fixed this, testing now and if so I'll submit the patch to CyanogenMod.
[HTC Desire S] Tectas:
That's no reason for me, I used Go launcher also at my sense times, with root access you just can kill the sense homescreen and appdrawer^^

At Go Launcher there are 10 (up to 2 extra dockbars with 5 icons at each) with the ability to put folders instead of normal icons on it :P

---------- Post added at 02:01 PM ---------- Previous post was at 01:46 PM ----------

That was fast :)
[HTC Desire S] nsmart:
Do you also have some news about the volume boost which should have been fixed in Tiamat 1.1.4 but it is still there (same behaviour as in Tiamat 1.1.3). Several users confirmed it.
[HTC Desire S] djsubtronic:
Nope, but it happened a few nightlies ago. I've only just updated to the latest nightly and using interactive with stock kernel. I didn't hear anything announced regarding the lag issue being resolved so I thought it was still there, but so far so good.
[HTC Desire S] :
Picked this up whilst on holiday as my GPS broke on my sense ROM, and I decided downloading an 80MB CM7 ROM would cost me less on 3G than a 380MB Sense ROM. My wife is 9 months pregnant and I couldn't afford not being able to find the nearest hospital in an emergency!

Over a week later and I've kept CM7! Loving it! It has become my daily ROM in the lull between beta testing certain Sense ROMS.

Thank you Nexx and the Cyanogen team.

Have some beer tokens for the weekend: 4TR01792N0861701F

:D
[HTC Desire S] Nexx:
=) It's still compiling but I'm fairly sure it'll be fixed, I just want to be sure before I push the change to CyanogenMod.

Right, before 1.1.4 was released I spent a lot of time with the volume gain values in the Tiamat kernel. The values currently used are the ones I picked as "very loud but not distorting".

Here's a question open to anyone who wants to answer it though. Is the stock kernel volume loud enough?

Do you want me to just set the volume in the Tiamat kernel to match the stock kernel, or would you like me to try and find a middle ground?

Keep me posted. I want this ROM to be perfect, just like you all do =)
[HTC Desire S] Tectas:
According to my opinion yes :)
[HTC Desire S] Fidoble:
The stock volume is loud enough for me... you don’t have to mess around with the volume.

The volume boost is the main reason that I don’t use the Tiamat kernel.
[HTC Desire S] Nexx:
Bluetooth MAC address fix has been submitted to CyanogenMod, I see no reason why it won't be accepted and hopefully will be in the next nightly build.

As for the volume, assuming no-one feels the stock volume is too quiet, I'll see about pushing the stock volume levels to the Tiamat kernel for his next version.
[HTC Desire S] nsmart:
100% agreement. stock volume levels are perfect.
[HTC Desire S] JackyJack:
Yeah, on 1.1.4, I decrease the volume to the lowest but it's still quite too loud...
[HTC Desire S] e2zippo:
Stock volume is perfect, no need to change it.

Cheers!
[HTC Desire S] amidabuddha:
Strange, but my volume is good both with 1.1.3 and 1.1.4
[HTC Desire S] Nexx:
Out of interest, could you try the stock kernel and see if it's too quiet in your opinion?

Just flash the latest nightly and don't flash the Tiamat kernel to test =)
[HTC Desire S] Tectas:
Maybe your half deaf and you don't know it^^

Swyped from my Desire S
[HTC Desire S] Nexx:
I've created and submitted a patch to Cayniarb which changes the volume in the Taimat kernel so that it matches the stock kernel setting.

I need to speak to him later as to when this gets released, but if I can and if he's willing, I'll see if we can't just get a new build of 1.1.4 uploaded. If he would rather wait until the 1.1.5 release I'll see if he won't let me upload a patch you can apply after putting 1.1.4 on which will fix the volume.

Finally, and forgive me for keep saying this, but thank you so much to everyone who has donated, I really do appreciate you parting with your hard-earned money =)
[HTC Desire S] amidabuddha:
Hey man I really like you :)

...

Just flashed v18 with the stock kernel. The volume is exactly the same to me (set at 6/7 of the bar). I have not changed this since I firstly flashed CM, I have not played with DSP Manager. Yes I know that Tiamat's code is tweaked for boost but or it is not working or I am really deaf (but that makes my wife deaf also, because the volume is ok to her too). Or maybe the reason is that I am living in Eastern Europe and the Network quality here is far behind yours? :)
[HTC Desire S] Dylan '07:
Yesterday I switched the cpu governor from smartassv2 to interactive (Tiamat 1.1.4). It looks as if the battery life is like 33% shorter than before. I have a battery usage log file, I will have a look at it later for exact figures.

Anyone else having the same symptoms?
[HTC Desire S] skumara:
see doctor to check your ears,:D
[HTC Desire S] amidabuddha:
Nope the stock is just fine to me. Actually I can not see (hear) a great difference. The ratio when decrease/invrease are the same with both kernel. Only the 2 highest steps on Tiamat are too loud. But the lowest possible on stock I can still hear fine. Do you all by any chance have 3g enabled all the time? I have noticed that switching from 2g to 3g increases the volume intensity a bit on my device
[HTC Desire S] Tectas:
I'm changing it often, most of the time I stay at 2g and I only when I need it I switch to 3g.

But I also noticed that it's pretty loud.

I never compared 2g with 3g I must confess.

How should there be a relation between volume and network?

Edit:

I know that the quality and the signal strength are related to radio and cause of this to network, but the volume also, I would really like to know it, if someone can pls explain that, would be really nice :)

Swyped from my Desire S
[HTC Desire S] Nexx:
Update:

The BT MAC patch has been merged into CyanogenMod and will be in the next nightly. As for the kernel, Cayniarb and I are talking about how to handle that. I'll get back to you when I know anything more =)
[HTC Desire S] Tectas:
Thx very much, you solved this as fast :)

I'm interested where the problem was, if you want to tell and will there also be a patch for other HTC devices or only for ours?

I'm sure you two will find a solution everybody is happy with, thx for your hard work :)

Edit:

Found the answer at the cyanogen changelog, thx anyway :)

Swyped from my Desire S
[HTC Desire S] Tectas:
Maybe the seeming of higher volume is related to higher quality?

Swyped from my Desire S
[HTC Desire S] trismegistos:
Thx for your work nexx. You are cool, stay as you are.
[HTC Desire S] Nexx:
I classify these errors as PEBKAC errors...

Problem Exists Between Keyboard And Chair.

IE, it was a typo =P

Always =)
[HTC Desire S] Tectas:
The old story about the biggest problem within development, the user, unfortunately this time it was an IDE user^^

Edit:

Only for insiders:

How to get an random string?

Put an fresh IT student in front of vi and tell him to quit^^

Swyped from my Desire S
[HTC Desire S] Nexx:
xD

I like that one
[HTC Desire S] sharper00:
Can anyone test this behaviour:

-When I put the phone into airplane mode power usage increases to about 30ma in idle with screen off.

-When I take it out of airplane mode it remains at 20-30ma until I reboot, then it drops back down to 10ma

This is with nightly 16 and stock kernel.
[HTC Desire S] scrack26:
That was fast! Thank you! Mwah!
[HTC Desire S] e2zippo:
I can confirm that usage when in airplane mode is around 30ma.

Gonna try and reboot and see if it drops back down.

This is with nightly 16.
[HTC Desire S] amidabuddha:
10 mA @normal operation

~25 mA in Airplane mode. Comes back to 10 mA when turning Airplane mode off, no need of reboot
[HTC Desire S] aajk:
What clock app are you using? Looks nice!
[HTC Desire S] sharper00:
Good idea! It didn't occur to me to reboot while in airplane mode. When I did this usage dropped to 6ma.

I also tried disabling 3G data, that caused power usage to stay at 12-17ma so turning it off doesn't appear to save any power and it possibly uses more.

Switching to 2G with data disabled caused usage to drop to 8ma.
[HTC Desire S] skumara:
every time after install i need to enter my carrier APN settings manually. Is there a way to make this auto detect and set up my carrier APN setting like in sense rom?

I also noticed the data connection is very slow. I use USB theter and download from my laptop, the download speed in very significantly reduced compared to LBC mod sense rom 0.6. In LBC I get 200kb/s download speed and in cyanogen I only get 50kb/s.

im in nightly 20 now usb tethering working fine.
[HTC Desire S] neoliviu:
I found a bug in build 19, i can't change icon of aps. I had build 10 and it was posibble. please fix (probably ADWlouncher error)

error : no applications can perform this action

(errror present also in latest zulugen)
[HTC Desire S] amidabuddha:
My APN are always autodetected /upgrade and clean install/. Cannot say for the tethering...
[HTC Desire S] Tectas:
Same here.

Swyped from my Desire S
[HTC Desire S] amidabuddha:
Just checked and successfully changed the icons on a custom and app icons on the homescreen. Changed and reverted to the original just fine...

About the tethering (can you check the difference if swithing 2G/3G modes?
[HTC Desire S] Lobo13:
Hi,

I have problem with SIP/VOIP calling on night builds. Other caller don't hear my voice. And sometimes my phone freeze before make voip call and I have to do reboot.

Problems are with both of kernel - CM and Tiamat. I tried CSipSimple and system SIP client.

Thanks, Lobo.
[HTC Desire S] zas666:
What are your APN parameters? It can exist in cm database and being bugged,or it just doesn't exist yet.

We can manage to add it i think.
[HTC Desire S] neoliviu:
it was my fault, sorry, tks for reply

"amidabuddha : Just checked and successfully changed the icons on a custom and app icons on the homescreen. Changed and reverted to the original just fine..."
[HTC Desire S] Nexx:
This is, unfortunately, a frequently reported issue. I've tested on other devices running CM7 and they have the same issue too so this appears to be a CyanogenMod issue, not a device one.

All I can suggest is reporting it on the CM issue tracker, but only after 7.1.0 final is released. Please don't report nightly issues on the tracker.
[HTC Desire S] skumara:
What are the APN parameter you want? Is it this one?

my carrier is celcom malaysia so these are the parameter attached.

If you want same things for other carrier in my country I can find and give it to you?

And the USB tethering working fine in cyanogen 20