Disclaimer /. Your warranty is now likely void. I am not responsible for bricked devices, dead SD cards,. spontaneous combustion, or any other host of cosmic penalties.

• Htc Pc36100 Evo

which may befall you, your family, or your phone./ Features. AOSP No longer in development until I can get my phone fixed Instructions. MUST be s-off. Flash it! Download. Source.

Special Thanks. Intervigilium. Tbalden. Showp1984. Faux123 XDA:DevDB Information D.I.R.T y MAC, Kernel for the Sprint HTC EVO 4G LTE Contributors Kernel Special Features: Version Information Status: Stable Current Stable Version: macstable Stable Release Date: 2013-12-19 Current Beta Version: macexperimental Beta Release Date: 2013-11-01 Created 2013-12-20 Last Updated 2014-05-22. (6th March 2013), (6th March 2013), (19th December 2013), (6th March 2013), (6th March 2013), (7th March 2013), (6th March 2013), (6th March 2013), (20th October 2013), (6th March 2013), (6th March 2013), (7th March 2013), (6th March 2013), (6th March 2013), (26th February 2014), (6th March 2013), (6th March 2013), (6th March 2013), (12th December 2013), (6th March 2013), (7th March 2013), (29th January 2014), (6th March 2013), (6th March 2013), (6th March 2013), (7th March 2013), (6th March 2013), (8th April 2013), (7th March 2013), (6th March 2013). Disclaimer /.

Your warranty is now likely void. I am not responsible for bricked devices, dead SD cards,. spontaneous combustion, or any other host of cosmic penalties.

which may befall you, your family, or your phone. This will be updated regularly Why do I need to be s-off?. First off you should already be s-off if you are using any aosp rom. Second, s-off fixes many issues people come across when flashing roms. Sense kernel will have SOn option. Why do I only have two point multi touch with this kernel?.

The synaptics 3k touch screen driver handles multiple touch events by default but do not work with htc gestures enabled. Go to Settings, Display, gestures & buttons, disable htc gestures and you will have more than two point multi touch. Kernel Info Sweep2Wake. echo 0 /sys/androidtouch/sweep2wake (disable s2w). echo 1 /sys/androidtouch/sweep2wake (enable s2w) GPU Control. If you want to use kcontrol's gpu control without using kcontrol. Paste into a new document and name it '03GPU'.

Follow the directions in the script to get the speeds. Paste the speeds in the insmod command according to the how to. Save and reboot Governor Info.

Lagfree Lagfree is similar to ondemand. Main difference is it's optimization to become more battery friendly.

Frequency is gracefully decreased and increased, unlike ondemand which jumps to 100% too often. Lagfree does not skip any frequency step while scaling up or down. Remember that if there's a requirement for sudden burst of power, lagfree can not satisfy that since it has to raise cpu through each higher frequency step from current. Some users report that video playback using lagfree stutters a little. Sysfs included.

Smartass v2 Version 2 of the original smartass governor from Erasmux. Another favorite for many. The governor aims for an 'ideal frequency', and ramp up more aggressively towards this freq and less aggressive after.

It uses different ideal frequencies for screen on and screen off, namely awakeidealfreq and sleepidealfreq. This governor scales down CPU very fast (to hit sleepidealfreq soon) while screen is off and scales up rapidly to awakeidealfreq (500 mhz for GS2 by default) when screen is on. There's no upper limit for frequency while screen is off (unlike Smartass). So the entire frequency range is available for the governor to use during screen-on and screen-off state. The motto of this governor is a balance between performance and battery. Sysfs included. BadAss Badass removes all of this 'fast peaking' to the max frequency.

On a typical system the cpu won't go above 918Mhz and therefore stay cool and will use less power. To trigger a frequency increase, the system must run a bit @ 918Mhz with high load, then the frequency is bumped to 1188Mhz. If that is still not enough the governor gives you full throttle. (this transition should not take longer than 1-2 seconds, depending on the load your system is experiencing) Badass will also take the gpu load into consideration. If the gpu is moderately busy it will bypass the above check and clock the cpu with 1188Mhz.

If the gpu is crushed under load, badass will lift the restrictions to the cpu. Wheatley Building on the classic 'ondemand' governor is implemented Wheatley governor. The governor has two additional parameters: targetresidency - The minimum average residency in µs which is considered acceptable for a proper efficient usage of the C4 state. Default is 10000 = 10ms. Allowedmisses - The number sampling intervals in a row the average residency is allowed to be lower than targetresidency before the governor reduces the frequency. This ensures that the governor is not too aggressive in scaling down the frequency and reduces it just because some background process was temporarily causing a larger number of wakeups.

The default is 5. Wheatley works as planned and does not hinder the proper C4 usage for task where the C4 can be used properly. For internet browsing the time spend in C4 has increased by 10% points and the average residency has increased by about 1ms. I guess these differences are mostly due to the different browsing behaviour (I spend the last time more multi-tabbing). But at least we can say that Wheatley does not interfere with the proper use of the C4 state during 'light' tasks.

For music playback with screen off the time spend in C4 is practically unchanged, however the average residency is reduced from around 30ms to around 18ms, but this is still more than acceptable. So the results show that Wheatley works as intended and ensures that the C4 state is used whenever the task allows a proper efficient usage of the C4 state. For more demanding tasks which cause a large number of wakeups and prevent the efficient usage of the C4 state, the governor resorts to the next best power saving mechanism and scales down the frequency. So with the new highly-flexible Wheatley governor one can have the best of both worlds. Obviously, this governor is only available on multi-core devices.

I/O Scheduler Info. Noop Inserts all the incoming I/O requests to a First In First Out queue and implements request merging. Best used with storage devices that does not depend on mechanical movement to access data (yes, like our flash drives).

Advantage here is that flash drives does not require reordering of multiple I/O requests unlike in normal hard drives. Advantages: Serves I/O requests with least number of cpu cycles. (Battery friendly?) Best for flash drives since there is no seeking penalty. Good throughput on db systems. Disadvantages: Reduction in number of cpu cycles used is proportional to drop in performance.

Deadline Goal is to minimize I/O latency or starvation of a request. The same is achieved by round robin policy to be fair among multiple I/O requests. Five queues are aggressively used to reorder incoming requests. Advantages: Nearly a real time scheduler. Excels in reducing latency of any given single I/O.

Best scheduler for database access and queries. Bandwidth requirement of a process - what percentage of CPU it needs, is easily calculated. Like noop, a good scheduler for solid state/flash drives. Disadvantages: When system is overloaded, set of processes that may miss deadline is largely unpredictable.

CFQ Completely Fair Queuing scheduler maintains a scalable per-process I/O queue and attempts to distribute the available I/O bandwidth equally among all I/O requests. Each per-process queue contains synchronous requests from processes. Time slice allocated for each queue depends on the priority of the 'parent' process. V2 of CFQ has some fixes which solves process' i/o starvation and some small backward seeks in the hope of improving responsiveness. Advantages: Considered to deliver a balanced i/o performance. Easiest to tune. Excels on multiprocessor systems.

Best database system performance after deadline. Disadvantages: Some users report media scanning takes longest to complete using CFQ.

This could be because of the property that since the bandwidth is equally distributed to all i/o operations during boot-up, media scanning is not given any special priority. Jitter (worst-case-delay) exhibited can sometimes be high, because of the number of tasks competing for the disk. BFQ Instead of time slices allocation by CFQ, BFQ assigns budgets. Disk is granted to an active process until it's budget (number of sectors) expires. BFQ assigns high budgets to non-read tasks.

Budget assigned to a process varies over time as a function of it's behavior. Advantages: Believed to be very good for usb data transfer rate. Believed to be the best scheduler for HD video recording and video streaming. (because of less jitter as compared to CFQ and others) Considered an accurate i/o scheduler. Achieves about 30% more throughput than CFQ on most workloads.

Disadvantages: Not the best scheduler for benchmarking. Higher budget assigned to a process can affect interactivity and increased latency. SIO Simple I/O scheduler aims to keep minimum overhead to achieve low latency to serve I/O requests. No priority quesues concepts, but only basic merging. Sio is a mix between noop & deadline. No reordering or sorting of requests. Advantages: Simple, so reliable.

Minimized starvation of requests. Disadvantages: Slow random-read speeds on flash drives, compared to other schedulers. Sequential-read speeds on flash drives also not so good. ROW The ROW I/O scheduler gives priority to READ requests over the WRITE requests when dispatching, without starving WRITE requests.

Requests are kept in priority queues. Dispatching is done in a RR manner when the dispatch quantum for each queue is calculated according to queue priority. Most suitable for mobile devices.

I cant wait for the EVO. Ive had the iPhone for 3 years and am looking forward to a change especially since the iPhone has grown stale (design and OS). Ive used Android before and its pretty much the same as an iPhone to me. The major thing I love is the fact that the phone runs at 4G (and 4G is available in Charlotte, NC) and its a mobile hotspot. I also like the idea of choice on the Android compared to the Apple way. Apple has really gone over the edge lately and I love their stuff! Cant wait for the summer!

If it's not over priced and Sprint still offers the $69.99 everything plan the Evo maybe my next phone. I've owned every version of the iPhone and enjoy using it, however ATT's lack of tethering and poor 3G coverage has me thinking about the move. My main concern is if while tethering on the Evo can I make a phone call? I've heard yes and no.

No on 3G, yes if on the 4G network? Will have to clear that up before deciding for sure. Another item I have to investigate is the ability to connect to Exchange for work? I don't use Gmail and if it's limited to that it's a no go. Aside from those few issues it will come down to the UI and ease of use. The iPhone may have it's limitations but the multitouch UI makes using it the best smartphone experience I've used to date.

Htc Pc36100 Evo

I have played around with numerous BB's including the Storm and Storm 2, a friends Droid and a few Web OS based phones. Assuming the network and the OS can deal with a few requirements I have the Evo will probably get a '30 day trail' and see how the UI performs. I'm sure it will take some getting used to, and if the 4G is as fast as they claim I'll make a few concessions for the speed factor.

That is one of the main reasons for me to switch anyhow, tethering and mobile speed for my job. Looking forward to June! Impressive, though I'm not sure I want to go on sprint's network.

They're still losing more customers then adding and I still here bad things from them. Also while they are the first out of the gate with a 4G phone, the question is much of their network is 4G. I was asking a customer rep this in NH and he said that not in New Hampshire, but maybe Boston, but couldn't be sure. Double checking their coverage map, it only looks like they have 4g in 11 states and even then its city by city. I'm not saying AT&T or Verizon is going to be better, just that 4G look to be premature and I'd not use that as a deciding factor.