yashsingh1/xdaforums huggingface dataset:
[HTC EVO 3D] htabbach:
Very funny but true, the forum police are killing this site! My rule is if someone is not talking directly to me I will not reply to them no matter how I think of their post, I wish everyone would do the same.
[HTC EVO 3D] el poblano:
No dice for decks rom. Stuck on splash.
[HTC EVO 3D] ricocollege:
Thanks

Tiamat + CM Valpha+battery fix = sweet.
[HTC EVO 3D] norm12:
That rule should be the rule for every Internet forum----i miss manners and decorum

Sent by Logo the turtle
[HTC EVO 3D] J3STUR:
Thank you cayniarb!!!! Come on people lets stay on topic! Lol

Sent from my bed
[HTC EVO 3D] drewski83:
I had a question .. I see ppl talking bout wiping their battery stats.. well every time I try to wipe mine with whichever program it tells me either it cannot because it couldnt find right file or just fails. Is there a way to figure out what's up? I've tried in twrp n with apps...
[HTC EVO 3D] dkelle4:
Congrats on the (public) release!
[HTC EVO 3D] EniGmA1987:
If TWRP wont wipe then then you could try ClockWorkMod. Thats all I have ever used and it works fine through that for me

---------- Post added at 04:32 PM ---------- Previous post was at 04:22 PM ----------

I will try that and report back, although I am thinking what it says is just a bug and it wont really work. But maybe.
[HTC EVO 3D] nonpointtruth:
Agreed.. Running smooth in CM7 with the battery fix..
[HTC EVO 3D] Cayniarb:
Glad people are enjoying this.

No, this kernel will not make wimax work.

No, this kernel does not have toast's battery fix 'built in.' The fix is not in the kernel (but is in other parts of the boot.img). I use Koush's anykernel package, so installing the kernel will repack it into the existing boot.img (i.e. install the battery fixed rom, then install this kernel, then profit).

As for the WiFi issues on certain non-CM ROMs, take that up with those ROM devs -- they 'fixed' WiFi while using a very old kernel that I made that was never intended to get out to the public in the first place. That kernel had Sense WiFi drivers. Those ROMs are now set up to expect sense WiFi drivers. This kernel has proper AOSP WiFi drivers. So, those AOSP ROM devs should really make their ROMs use AOSP WiFi drivers as well. I am not going to be going back to the Sense drivers.

As for other feature requests (LED dimming I noticed here, but in general), you're much much more likely to get somewhere with me by dropping me a line in my IRC channel -- if y'all haven't noticed yet, I'm not often on XDA these days...
[HTC EVO 3D] r0cky0790:
I don't have access to a PC to hop on the irc. I wanted to know, will your kernel have dual core support in the future.

BTW, thanks for the work you put in for this community.

My "DU4L C0R3 SH00T3R" shot you down in 3D! Screw Tupac. "A,O,S,P BACK!" >_<
[HTC EVO 3D] cordell12:
^^^theres a app for that (irc)^^^
[HTC EVO 3D] r0cky0790:
Which one would you suggest?

My "DU4L C0R3 SH00T3R" shot you down in 3D! Screw Tupac. "A,O,S,P BACK!" >_<
[HTC EVO 3D] edgie168:
Anyone else running into issues with torch on the battery fixed valpha2? Mine keeps FC'ing with this kernel.
[HTC EVO 3D] vboyz103:
Yep torch is torched fo sho...
[HTC EVO 3D] jayharper08:
I'm on stock rom with valpha2 and its "torched", so I don't think it's this kernel.

Sent from the CM powered 3d
[HTC EVO 3D] sfld:
Can i flash the valpha2 with batt fix, boot once then flash tiamat? All via twrp or do i need to use a new method?
[HTC EVO 3D] EniGmA1987:
Can anyone explain these a little bit:

I am wondering, the SetCPU overclocking thing. That means the first core right? The reason I have to ask is the cores are actually named core0 and core1 so I just want to make sure.

Also, with the level2 cache OC and bus OC, where is that done? What app? Ive never seen it in SetCPU before I dont think.
[HTC EVO 3D] cordell12:
AndChat :)

http://www.andchat.net/
[HTC EVO 3D] r0cky0790:
I'm trying to connect to Cayniarbs IRC #tiamat channel using ANDROIRC (already downloaded before your suggestion was posted:)) but I'm stuck on how to get this started.

I also keep getting this message,

[23:50] -card.freenode.net- *** Notice -- You need to identify via SASL to use this server

Can anyone give me detailed instructions on how to get this working. Your help would be dearly appreciated. TIA

My "DU4L C0R3 SH00T3R" shot you down in 3D! Screw Tupac. "A,O,S,P BACK!" >_<
[HTC EVO 3D] -viperboy-:
That's a Sprint thing. IRC doesn't work on their network when trying to connect to freenode.
[HTC EVO 3D] r0cky0790:
Well why would someone suggest me use the app if it didn't work. I dunno, but thanks for the info Viper.

I just wanted to ask Cayniarb will his kernels have dual core support in the future. I did a little reading on his page and I guess he is trying to push his kernels to a stable 2.0MHz. I'm not sure if this coincides with what I'm asking but I hope it does.

My "DU4L C0R3 SH00T3R" shot you down in 3D! Screw Tupac. "A,O,S,P BACK!" >_
[HTC EVO 3D] rstuckmaier:
It will work with Sprint but you have to identify your log in first. Sadly you can't do that on the app (you should be able to over wifi).
[HTC EVO 3D] cheflarry:
Install alpha 2 with fix then kernel in same session
[HTC EVO 3D] jerofld:
Did you try this: http://androidforums.com/htc-evo-3d/361521-streaming-media-tyrrany-sprint-proxies.html

I could have sworn it was based off an XDA page somewhere, but couldn't find it in the Evo 3D section.
[HTC EVO 3D] ms79723:
Hey Cayniarb, when/if you see this, can you shoot me a message? Xda won't let me shoot you one -.-
[HTC EVO 3D] cordell12:
Were you able to get it working? I recall back before the 3D was released and shortly there after everyone was on IRC, waiting for r00t, alpha-rev, and all the goodies. There were many people who had no PC access and used this app to connect to #FREENODE, how it was done, I am not to sure. It is quite possible I linked you to the wrong app :o I never used IRC over my phone, I was just trying to help...
[HTC EVO 3D] dadoc04:
Runnin good for me. No fc's at all. Flashed over alpha2+battery fix

Sent from my Evo3D
[HTC EVO 3D] Cayniarb:
Nobody needs to do anything special to 'enable dual core support.' Anyone who tells you otherwise doesn't understand what they are talking about.
[HTC EVO 3D] bballer71418:
Hey cayniarb, I know this kernel will turn into something awesome eventually but I have one question. Will HAVS ever get ported over to the 3d? I'm not to sure exactly what it does but it drastically imporved battery life on my og evo
[HTC EVO 3D] Cayniarb:
cpu1 is the secondary core. cpu0 is the primary core.

There is a really good thread in the Sensation development section by BrokenWall that goes into a lot more detail about the challenges presented by our asynchronous processor. Unlike every other multi-core ARM processor on the market, the cores in the Snapdragon 8x60 are able to scale independently. This has caused problems in getting apps like SetCPU to enforce their settings on both cores. HTC 'solves' this problem with perflock - imposing the 4 frequencies and one governor that are ever available on everything. Removing perflock (and allowing user-selected frequencies) exposes the problem. I worked a lot with faux123 and morfic to solve this problem as best we could. The cpufreq code changes we have made allow SetCPU to impose it's settings on both cores - and for those settings to persist after cpu1 hotplugs offline then returns to an active state. However, this does not impact the governor settings (hence my uncharacteristic inclusion of ondemand - there is really no use to using another governor at this point).

As for L2 cache and bus overclocking - there is no app that can adjust these. Nor will there ever be and nor should there ever be. These tables are static. Each available cpu frequency uses a particular entry in the L2 table. Each L2 entry uses a particular bus speed. Hence, the overclocked L2 and bus only come into play at overcloced cpu speeds.
[HTC EVO 3D] Cayniarb:
Qualcomm included AVS in the kernel by default. Or, a form of it at least (decidedly not the same form that is common in 8x50 kernels).

As for adding the hybrid part of that, I really can't say - but I doubt it.
[HTC EVO 3D] aFoodStampBaby:
Works great on my EVO 3d. Thanks.
[HTC EVO 3D] bubbate:
+ 1

#Team3VO
[HTC EVO 3D] Cayniarb:
v1.0.1 is now available: http://tiamat-dev.com/tiamat_e3d/
[HTC EVO 3D] r0cky0790:
Nobody told me anything about what has to be done to enable dual core support. I just wanted to know will you support it in you future realease. Sorry if you misunderstood me.

Edit: About to flash v1.0.1 now.:)

My "DU4L C0R3 SH00T3R" shot you down in 3D! Screw Tupac. "A,O,S,P BACK!" >_
[HTC EVO 3D] Cayniarb:
There have been several ROM devs that claim to have 'true dual core support.' Which is to say that they used some scripts to force the second core online *all* the time. That's a horrible idea - all it does is waste power, create excess heat, and put unnecessary wear on your processor. The second core is *supposed* to turn off when it's not needed (and yes, even non-asynchronous multi-core ARM processors do that -- or, *every* multi-core ARM processor that exists).

I didn't mean to jump on you about it.
[HTC EVO 3D] r0cky0790:
Thats some good info. I was unaware of the non-asynchronous acting in the same manner as the processor on the 3D. Why do people say otherwise (ex.) as with the SGS2?

My "DU4L C0R3 SH00T3R" shot you down in 3D! Screw Tupac. "A,O,S,P BACK!" >_<
[HTC EVO 3D] J3STUR:
The new 1.0.1 update is making my cm7 run so smooth, better then 1.0.0., which made made my phone temp really hot, now its my phone isn't that hot now. Thank you and great work!!!!!
[HTC EVO 3D] edgie168:
You know, I didn't even notice that until you mentioned it -- running Sense enabled me to have a BBQ using the back of my phone as a grill.. just goes to show how terrible Sense is.
[HTC EVO 3D] r0cky0790:
Tiamat is living up to its name. Straight beast.

My "DU4L C0R3 SH00T3R" shot you down in 3D! Screw Tupac. "A,O,S,P BACK!" >_<
[HTC EVO 3D] ldominguez1986:
Do we download the 8x60 one?
[HTC EVO 3D] chrisfales:
correct....yes
[HTC EVO 3D] EniGmA1987:
I see. Thank you for the information about it. Helped me understand it a lot better.

I am wondering though, if the L2 and bus are overclocked by a set amount when the core speed is running at X speed, perhaps this is partly what causes some instability at high speeds? We all know a processor can only be overclocked so far, and that limit point is from the weakest link in the system. So perhaps the L2 and bus tables for what speed they run at could be swapped out for certain speeds. Like just as an example lets say that:

core = 1.5GHz

L2 = 1.0GHz

Bus = 1.0GHz

core = 1.8GHz

L2 = 1.2GHz

Bus = 1.2GHz

core = 2.0GHz

L2 = 1.35GHz

Bus = 1.35GHz

Perhaps it is the L2 and Bus that become unstable at those speeds and limit the OC. So what would happen if the L2 and Bus speed table could be swapped, so that at 1.8GHz core the speed of the L2 and bus frequency are only running at the speed of when the core runs at 1.5GHz? Thus providing a higher core speed while still maintaining stable L2 and bus speeds.

I might not have explained my example well enough, I hope you understand what I am trying to ask about.
[HTC EVO 3D] r0cky0790:
Cayniarb, can you explain this SmartassV2 governor. I thought Smartass was designed to scale up and down, instead it just sits at the highest frequency.

My "DU4L C0R3 SH00T3R" shot you down in 3D! Screw Tupac. "A,O,S,P BACK!" >_<
[HTC EVO 3D] Jaywan:
I used BigRushDog Tiamat on the Xoom. Will this one ever 2GHz? P.S. great kernel. This is hands down a tiamat kernel...
[HTC EVO 3D] Richkid:
What's your config?
[HTC EVO 3D] -viperboy-:
I see the Sensation guys have sysfs VDD interface now on a Sense kernel (too bad you don't put out your Sense kernels, Cayniarb!) Can't wait to see that in Tiamat 8x60!

And can you explain smartass v2, Cayniarb?
[HTC EVO 3D] r0cky0790:
What's so special about sysfs VDD interface. Can you please elaborate Viper?

I thought I was the only one concerned about this...

My "DU4L C0R3 SH00T3R" shot you down in 3D! Screw Tupac. "A,O,S,P BACK!" >_<
[HTC EVO 3D] -viperboy-:
Its what viperMOD is based on, allows the user to adjust processor voltage for better battery life. Can't wait to see it implemented!
[HTC EVO 3D] bballer71418:
Hey viper does the oc deamon work on aosp roms? Or does vdd interface need to be added first
[HTC EVO 3D] -viperboy-:
No it works. I ported it over when i tried CM. Works fine.
[HTC EVO 3D] AvidBlake:
I know ViperMOD / ViperControl was primarily created for your own ROM; however, since your ROM isn't ASOP, are you planning on making Viper Control available as a MOD?

I'm using the OC Daemon now without any issues now, but your controls make it so much easier to adjust on the fly!

Does Smartass basically serve the same function as the OC Daemon?
[HTC EVO 3D] -viperboy-:
Well there are two different things and they can be confusing but let me explain. viperControl is for my ROM. viperMOD is the voltage control script I have for quite a few phones and the app is almost done. At this time I don't plan to release viperControl as a standalone mod for other ROMs, sorry.

As for smartass, yeah, it is similar however the daemon may change governors faster.
[HTC EVO 3D] AvidBlake:
I'm interested to find out more about how the two interact, and if they play nice together. I'm on 1.0.1 but I also have the daemon. It seems like the daemon is allowing me to OC and both on demand and performance settings seemed to be enforced.

Interestingly, according to CPU Spy, I've been running at a slightly higher avg CPU state than I did on ViperROM. I might flash back to 1.0.0 and see if that has anything to do with SA. (unless someone more educated than me already has an answer and decides to share)
[HTC EVO 3D] -viperboy-:
If you're using smartass, you don't wanna use the daemon. You have 2 things fighting to control speed and governor. That may ne your culprit. I would just run smartass and see how it goes.
[HTC EVO 3D] r0cky0790:
It seems with latest release I get a lag phase far a lenghty period of time after a reboot. It goes away eventually but it seems to stay longer than expected. This never happened on v1.0.0.

Edit: After doing some testing, switching over to bcblend, just to see if I get the same results. From the looks of it the smartass governor on Tiamat is not scaling like the the smartass on bcblend. This is being indicated by CPU spy, also when I check in set CPU it seems as if it just stays scaled at the highest frequency. & I'm not experiencing any lag on reboot either. Just here to report my issue. I'm looking forward to your work and I'm waiting patient for your next release.

My "DU4L C0R3 SH00T3R" shot you down in 3D! Screw Tupac. "A,O,S,P BACK!" >_
[HTC EVO 3D] EniGmA1987:
Found a bug with the kernel (may be CM7 but it feels kernel related to me). After playing Ninjump for about a minute the screen goes crazy and starts getting hardware artifacting. The only way to get back to normal is by restarting the phone. I am on the ondemand governor. Problem happens whether at stock speeds, overclocked, or underclocked.
[HTC EVO 3D] I_Am_Lorde:
How do I use smartass? Through terminal emulator like the oc daemon?
[HTC EVO 3D] -viperboy-:
No, setcpu.
[HTC EVO 3D] AvidBlake:
I did noticed that Smartass was added to 1.0.1 - and I assumed it was automatically initiated. After I removed the OC Daemon, I noticed that my CPU has been running at the max stock speed the majority of my awake time very similar to "performance" setting.

I checked the Tiamat website and didn't see much about smartass other than it being a governor. I did a couple of searches (see below for most relevant topics), but couldn't really find anything about how to specifically control it. In fact, this thread ended up being a result for nearly all my queries.

My programming knowledge regarding Android is close to zero, so I (and I'm sure many others) would appreciate a little more insight. Is it just a setting within SetCPU that is added when a Tiamat Kernel is installed? Is there something I need to disable in order to use the OC Daemon to prevent conflict? I did notice that the daemon worked fine when with 1.0.1 installed.

I'm done rambling. Thanks in advance.

http://lmgtfy.com/?q=smartass+governor

http://www.droidforums.net/forum/droid-incredible-tech-issues/109934-smart-governor-setcpu.html

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

---------- Post added at 09:16 AM ---------- Previous post was at 08:57 AM ----------

I was writing my last post when you made this reply. So really, Smartass and the OC Daemon shouldn't ever interact? Using SetCPU would turn off the Daemon... I thought?
[HTC EVO 3D] r0cky0790:
Specific info on the smartass v2 governor

https://github.com/bcnice20/Shooter-2.6.35_mr/commit/b0a86fdab5257ec26bfda11f057dfdfe662162aa

My "DU4L C0R3 SH00T3R" shot you down in 3D! Screw Tupac. "A,O,S,P BACK!" >_<
[HTC EVO 3D] -viperboy-:
I haven't gotten to use this kernel yet but it might be a governor issue since this has smartass v2 from my understanding. Something in the kernel code may have been goofed up if you are on smartass and noticing it running at full speed alot of the time and other governors don't do that. I don't know what v2 brings to the table vs regular smartass and I haven't found anything about it either.

Governors can be changed in setcpu on any kernel but if you are using smartass you don't want to use the daemon. Yes the daemon should automatically not run but I can't be sure on a ROM other than mine. You never want two programs trying to do the same thing and smartass and the oc daemon are both trying to control speed and governors, not good.
[HTC EVO 3D] r0cky0790:
I posted a link about it above your post.:)

My "DU4L C0R3 SH00T3R" shot you down in 3D! Screw Tupac. "A,O,S,P BACK!" >_<
[HTC EVO 3D] AvidBlake:
I simply misunderstood the application of Smartass. I was under the impression it was like the OC Daemon on ViperROM (first ROM I flashed.. I got spoiled, what can I say) and started automatically. This is my first Android phone, so I'm still a "self loathing n00b" ;) Thanks for the helpful response!

Since the Daemon is more responsive than SetCPU, I have a tendency to just stick with that. I tend to turn my phone on and off frequently, so the faster switch is more valuable to me than the advantages Smartass may bring in battery life/performance.
[HTC EVO 3D] I_Am_Lorde:
When my screen is off for a few mins and I turn it back on and open set CPU it grants it superuser permissions. However, setcpu was already on before. Does that mean that smartass isn't running when mu screen is off?
[HTC EVO 3D] -viperboy-:
No. Just turn off the annoying notifications in superuser.
[HTC EVO 3D] I_Am_Lorde:
Thanks viper!
[HTC EVO 3D] Hooper44:
I flashed 1.0.1 running CM7 valpha 2+batteryfix. First time flashed fine. I wanted to reload CM7. Did complete wipe, back to factory. Flashed CM7 then Tiamat. Continuous bootloop. Have tried several times. Same thing. Nadoid restore boots fine. Still cannot flash Tiamat. Any ideas? Thanks in advance.
[HTC EVO 3D] -viperboy-:
Try wiping everything (even /system) and then flashing CM7 by itself and then reboot. Bootloop? If not, then try flashing Tiamat. Should work just fine. Also, maybe redownload the kernel just to be sure its not a corrupt download.
[HTC EVO 3D] EniGmA1987:
I have always cleared the cache and dalvik in between flashing a ROM and then flashing a kernel for the ROM. Never had a problem. Might want to try that. I am on Tiamat v1.0.1 right now with CM7 alpha2 + battery fix. Works great for the most part, found a couple bugs and I am not sure if they are caused by Tiamat kernel or CM7

My settings that have given me fairly good battery life, while being the smoothest I have ever seen are:

SetCPU profiles:

ondemand governor for everything

InCall:

priority - 100

max - 432

min - 384

Screen Off:

priority - 90

max - 486

min - 192

Charging:

priority - 80

max - 1026

min - 192

Battery < 35%

priority - 70

max - 702

min - 192

Battery < 70%

priority - 60

max - 972

min - 192

Battery < 101%

priority - 50

max - 1080

min - 192

Advanced Settings:

sampling rate - 10000

up threshold - 83

ignore nice load - 0

powersave bias - 280

Battery with light use and those settings lasts me 24 hours. Light use I mean a game for maybe 45 minutes total throughout the whole day, 50 text messages throughout the day, and 2 - 4 calls lasting 10-20 minutes each throughout the day.

Moderate use lasts me around 15 hours, which is enough to unplug it in the morning and plug it in at night before bed.
[HTC EVO 3D] aFoodStampBaby:
For some reason my WiFi is not properly. It will not pick up my router. It will scan and just disconnect. This started when I installed this kernel. Anyway this can fixed?
[HTC EVO 3D] cctaylor410:
Does that happen for all wifi connections? If not try changing the channel on your router. Fixed the issue for me on my netgear router.
[HTC EVO 3D] Cayniarb:
I left my explanations on this somewhat vague because it takes a decent understanding of the code structure used here to wrap your head around what's going on. The bus is the least able part to overclock. By default, it has only 3 frequencies. The frequencies given in the L2 table are irrelevant - it's the voltage values given in that table that are important. The instability that was rampant at high clock speeds in early kernels for the 8x60's has a great deal more to do with other factors than the specific values used. As development continues, I plan to keep testing the limits of the very-high-end cpu speeds -- but realistically, I doubt that we will see 2.0Ghz stable for the masses. The chip in out devices is the first major run of a new line from Qualcomm -- for perspective, the chip in the N1 is almost always less capable than the exact same chip in the Evo 4G - because the Evo chips are a much later production run. That's also why the 7x30 chips started their life at 800Mhz, then 1.0Ghz, then 1.2Ghz, and even 1.4 and 1.5Ghz. Also how the next 8x60 run is stable for 1.5Ghz on release.

So, I am by no means finished pushing here -- I've seen unstable 2.0Ghz, so getting it stable is still possible. But don't hold your breath either.
[HTC EVO 3D] Cayniarb:
via code documentation here:

SmartassV2

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

The CPUfreq governor "smartassV2", like other governors, aims to balance

performance vs battery life by using low frequencies when load is low and

ramping the frequency when necessary, fast enough to ensure responsiveness.

The implementation of the governor is roughtly based on the idea of interactive.

The idle loop is used to track when the CPU has idle cycles. The idle loop will

set a relatively high rate timer to sample the load when appropriate, the timer

will measure the load since it was set and schedule a work queue task to do the

actual frequency change when necessary.

The most important tunable is the "ideal" frequency: this governor will aim

for this frequency, in the sense that it will ramp towards this frequency much

more aggresively than beyond it - both when ramping up from below this frequency

and when ramping down from above this frequency. Still, note, that when load is

low enough the governor should choose the lowest available frequency regardless

of the ideal frequency and similarly when load is consistently high enough the

highest available frequency will be used.

Smartass also tracks the state of the screen, and when screen is off (a.k.a

sleep or suspended in the terms of this governor) a different ideal frequency

is used. This is the only difference between the screen on and screen off

states. Proper tuning of the awake_ideal_freq and sleep_ideal_freq should

allow both high responsiveness when screen is on and utilizing the low

frequency range when load is low, especially when screen is off.

Finally, smartass is a highly customizable governor with almost everything

tweakable through the sysfs. For a detailed explaination of each tunable,

please see the inline comments at the begging of the code (smartass2.c).