Will it flash with s-on? Installed kernel by extracting boot and using fastboot
rooted 1.55.531.3 with clockwork recovery and SU
rooted 1.55.531.3 with clockwork recovery and SU
[CLOSED]doubleshot kernel project OC/UV ( 03-17-2012 )
- Thread starter Blue6IX
- Start date
-
- Tags
- development
- Status
I generally like to keep things simple myself, lol. The other thing I have never tried is the interactive governor, so I don't know how well it works in terms of battery life..... I know ondemand is the default governor, but I sometimes use conservative.
The other thing is that not all of these ROM/radio/kernel combinations have been tested, so I guess your mileage may vary. But I'm glad you are doing a bit better with it now. Good luck, and keep us posted
It sounds like you did the right thing, by fastboot flashing the boot.img. but yeah, maybe you need a different set of modules from that thread. The modules are being flashed to /system, so they should flash thru recovery.
Unfortunately not all ROM/firmware/kernel combinations have been tested, so we are all learning what works and what doesn't.
I generally like to keep things simple myself, lol. The other thing I have never tried is the interactive governor, so I don't know how well it works in terms of battery life..... I know ondemand is the default governor, but I sometimes use conservative.
The other thing is that not all of these ROM/radio/kernel combinations have been tested, so I guess your mileage may vary. But I'm glad you are doing a bit better with it now. Good luck, and keep us posted
I've been using the interactive governor for a while, I don't really notice it saving the battery more than conservative, in theory you would think that it would but im just not seeing it.
Sent from my Bulletproof_Doubleshot using Tapatalk
Which module package did you use? Pretty sure you would want the one for 1.28.531.9.
ac3theone: which modules did you use to make it work? You two are both on the very same setup I believe?
i used the one for 1.28.531.9
i fastboot flashed the boot img first then the zip package through cwm
Same thing I did and I have no WiFi... Facebook won't upload pics either.
Going to try original boot.img and see what happens
Going to try original boot.img and see what happens
Ok so I think I see a problem. My software matches the 2nd module but my radio matches the first. Neither work.
The stock bulletproof boot.img gives me WiFi. I'm thinking for whatever reason, these modules need to be built into boot.img. Is that something easily done?
I appreciate your advice and have applied your suggestions in the following way:
-Did a full wipe and reflashed the UV6 kernel.
-Allowed 10 minutes idle time after reflash
-Went into SetCPU and readjusted the lowend to 384 cycles then the upper to 972
(this seems plenty fast & smooth considering it's running on a dualcore)
-Changed profile from "ondemand" to "conservative"
I'll monitor the stability of these settings as well as battery use for 5 days or until/IF I have any problems. I'll keep you informed of what happens.
BTW, thank you for your quick response.
**Update:
About 48 hours into the application of your suggested mods and it seems to be much more stable than before. No reboots and the reduction in cpu frequency is no issue with this dual core processor......
**Final Update:
6 days after suggested adjustments and everything is smooth as silk. My DoubleShot seems to be getting between 24 & 30 hours on a charge with light to moderate use. I believe we have a WINNER! (and Thank You)
Last edited:
On break at work - but real quick:
The closest to building them into the boot.img you can get is wrapping it up into a flashable zip, the boot.img gets flashed to the boot partition but the modules go to the system partition.
Best thing S-ON and UNLOCKED can do is run the flashable zip from CWM (which installs the modules) then pull the boot.img out of it and fastboot flash that.
S-OFF need simply flash the zip in CWM.
Edit:
Got another break.
When you compile a kernel, part of the output are these modules - they get scooped up and kept with all the parts that turn into the boot.img - so the particular modules you need to use have to match the kernel that is installed.
If the modules aren't kept and distributed with the kernel, then no wifi. If the modules installed don't match up with the kernel that's installed, then again, no wifi.
Best thing to do is check your kernel version in:
Settings - About phone - Software settings - More
...and then just find the appropriate modules to match up with whatever you are running.
If someone makes a kernel and doesn't save or provide the modules...then that kernel won't have wifi.
The way yogi and I have been doing it is to wrap it all up in a flashable zip that includes both the finished boot.ing file and the necessary modules to complement it.
I just started a long contract, runs until june, so I'll have a predictable schedule for a little while, which happens to conflict with the few people I see in the real world, so I will have more time to donate towards getting things done here. Especially with S-OFF done for now, this project is back on the front page of my interest.
Sent from a digital distance.
Last edited:
Using the UV6 undervolt with undead's sensation 3.0 port. Moderate usage of phone, text, internet, light apps. Not bad at all!
Sent from my HTC Sensation Port using Tapatalk
Nice!!! Screen on time?
:thumbup::thumbup:Typed by ---- oh wait! I'm schizophrenic!
I've recharged since then but the screen time was just under 3hrs
Sent from my HTC Sensation Port using Tapatalk
Sent from my HTC Sensation Port using Tapatalk
- Status
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
12doubleshot Undervolt kernels
Gingerbread kernels:
UV5 HTC 2.6.35.10 (Gingerbread) kernel
- - 1.5GHz maximum CPU clock speed.
- - Undervolting? Yes
- - Insecure boot, see below:
kernel Info:Code:ro.secure=0 ro.allow.mock.location=0 ro.debuggable=1 persist.service.adb.enable=1
- - Hefty undervolting, especially at the lower frequencies.
- - Stock 1.28.531.9 or 1.28.531.10
- - Bulletproof 1.1
- - ?
- - 1.55.531.3 software base
- - ICS Roms
- - ?
MD5: a0b252d36bf39f788cdcb54e29717971
Size: 3.57 MB
UV6 HTC 2.6.35.10 (Gingerbread) kernel
- - 1.5GHz maximum CPU clock speed.
- - Undervolting? Yes
- - Insecure boot, see below:
kernel Info:Code:ro.secure=0 ro.allow.mock.location=0 ro.debuggable=1 persist.service.adb.enable=1
- - Even more undervolting, lowered voltages from UV5 on some of the mid-range frequencies.
- - Stock 1.28.531.9 or 1.28.531.10
- - Bulletproof 1.1
- - ?
- - 1.55.531.3 software base
- - ICS Roms
- - ?
MD5: fd8055865b09a645d3c3030ecce4ef40
Size: 3.57 MB
More Info:
- I made these UV kernels because i wanted to play with undervolting and see if i could extend the battery life on the device..... it seems to have worked out well for me so far, i have been using the stock battery since last night, and today am still at at least 85% battery left. I hope you too will experience improved battery life! I am surprised at how much I have been able to lower the voltages and still maintain stability..... i haven't had a single freeze-up or glitch yet! But if you do encounter anything like this, try the UV5 kernel above, which has slightly higher voltages than the UV6. And also I would keep a copy of the kernel with stock voltages handy
I have also been using SetCpu to set my min. frequency down to 192(default is 384 i believe), and i haven't had any lockups or problems with that either. So between that and the UV, my phone seems to be using little power while in sleep mode.
I will probably experiment with even more undervolting soon, and will notify of updates here in the thread. i can also post or provide the exact voltages for these kernels for anyone interested. enjoy!
11Team doubleshot kernel project.
Unfortunately the developer is unable to post source for these kernels at this time. Because of this, I am closing this thread and removing the download links. If you have any questions about GPL compliance, feel free to read this post.
Updates listed here:
-Added new version of 1.5 kernel in post 3.
-Added 1.7 kernel in post 3.
-Added CPU frequency table list in post 5.
Table of Contents:
- General:
Post 01 - Info & Stock kernels
Post 02 - Undervolt kernels
Post 03 - Overclock kernels
Post 04 - Reserved - yogi2010
Post 05 - Reserved - Blue6IX
Note:
A kernel takes at least a solid 24 hours to finish building caches and get itself fully installed and humming.
Even that depends upon usage to a degree, so make sure that you give your kernel ample time to settle in before you start to evaluate it's performance.
Stock kernels
Gingerbread
Stock HTC 2.6.35.10 (Gingerbread) kernel
- - 1.2GHz maximum CPU clock speed.
- - Undervolting? No
- - Insecure boot, see below:
kernel Info:Code:ro.secure=0 ro.allow.mock.location=0 ro.debuggable=1 persist.service.adb.enable=1
- - Unmodified HTC 2.6.35.10 kernel source, compiled from the HTC Dev kernel source download.
- - 1.2GHz maximum CPU clock speed.
- - Stock 1.28.531.9 or 1.28.531.10
- - Bulletproof 1.1
- - ?
- - 1.55.531.3 software base
- - ICS Roms
- - ?
-
MD5: b8aafcbc2447bae9839af4707bfcb38b
Size: 3.57 MB
Stock HTC 2.6.35.10 (Gingerbread) kernel Version 2
- - Same as above stock kernel, except:
- - Insecure boot with mock locations, see below:
File Details:Code:ro.secure=0 ro.allow.mock.location=1 ro.debuggable=1 persist.service.adb.enable=1
MD5: a6c227bf60ff4a100760fef0ef9bc68d
Size: 3.57 MB
Custom kernel management:
Installing custom kernels:
[1] - Download the kernel zip file to your sdcard.
[2] - Flash through clockworkmod recovery just like a ROM.- - If you do not know how to do this, you should learn how to flash ROMs before moving on to kernels.
SetCPU
- - SetCPU is an app that lets you regulate the clock speed of your device. ( and more! )
- - Check out the app in the XDA News page, and then check out the Dev thread.
- - Consider donating and buying the market app to support the developer if you really use the app.
Custom kernel information:
WARNING:
Flashing a kernel meant for 1.28.539.9 or 1.28.539.10 software on 1.55.531.3 software will most likely result in boot loops. The boot.img files are structured differently.
Make sure you are flashing the right kernel for your software version or ROM.
Undervolt kernels
Post 02 - Undervolt kernels
The post on undervolt kernels will contain kernels focused on the battery savings that undervolt can bring. Some undervolt kernels may be overclocked.
Undervolt kernels will send less power to your CPU and save you battery power.
In extreme cases this can cause brownouts or maybe not being able to recover from sleep mode - but no actual damage to the device can result from undervolting.
Significant battery savings can be gained through undervolting depending on usage and implementation.
WARNING:
Installing an Overclock kernel on your device could have negative physical consequences (Read: broken hardware) if misused/abused.
Please educate yourself on what overclocking does and how you can melt your processor.
You proceed at your own risk and any damage that may result is the sole responsibility of the end user.
Overclock kernels
Post 03 - Overclock kernels
The post on overclock kernels will be focused on pushing the limits of the clock speed for the device. Some overclock kernels may be undervolted.
Qualcomm, the manufacturer of the Snapdragon chip in the device rates them at 1.5GHz. Here is a Snapdragon Product Overview that may help you track down more information about the Series 3 Snapdragon processor in the doubleshot.
In extreme cases overclocking can melt your processor. Direct physical damage can result from increasing the CPU or GPU clock speeds above manufacturers recommended speeds.
Anyone intending to use an overclock kernel should first familiarize themselves with the device hardware and implement such things at their own risk.
Further information:
XDA Links:
- - [KERNEL][20 OCT][2.6.35.14] Kanged v0.1 | OC/UV
Thanks Romanbb for starting doubleshot kernel development!
- - Boot image info.
- - To be announced...
- - PDAdb entry for the doubleshot
- - PDAdb entry for Snapdragon Processors
- - PDAdb list of Snapdragon S3 Devices
- - More to follow...
8Overclock kernels
doubleshot Overclock kernels
WARNING:
Installing an Overclock kernel on your device could have negative physical consequences (Read: broken hardware) if misused/abused.
Please educate yourself on what overclocking does and how you can melt your processor.
You proceed at your own risk and any damage that may result is the sole responsibility of the end user.
Gingerbread kernels:
OC 1.5-A HTC 2.6.35.10 (Gingerbread) kernel
- - 1.5GHz maximum CPU clock speed.
- - Undervolting? Slight
- - Insecure boot, see below:
kernel Info:Code:ro.secure=0 ro.allow.mock.location=0 ro.debuggable=1 persist.service.adb.enable=1
- - Modified CPU table to accomodate Qualcomm 1.5GHz S3 Snapdragon chip speed.
- - HTC cuts it off at 1.2GHz on the stock kernel.
- - Re-scaled CPU table and L2 cache.
- - Max voltage 1.2 volts even at 1.5GHz (HTC was 1.25 volts @ 1.5GHz)
Voltage tables to be posted later - no voltages exceed what the stock kernel came pre-coded with, and we have undervolted the 1.5GHz frequency to 1.2 volts instead of the 1.25 volts HTC put it in for. Runs fine at 1.2 volts, has been for months for me.
(we used that 1.25volts at 1.7GHz instead...)
Otherwise all voltage tables are back to HTC stock, and new frequencies leading to 1.5GHz HTC did not put in had the voltage used from the lower frequency beneath it.
1.5 GHz is where the 'Two-Headed Snapdragon takes flight'.
(quote is the title of a Snapdragon white-paper)
The idea here is to give the superscaler dual-core processor the scaling options to choose from to take advantage of that ability...
Compatible ROMs:
- - Stock 1.28.531.9 or 1.28.531.10
- - Bulletproof 1.1
- - ?
- - 1.55.531.3 software base
- - ICS Roms
- - ?
-
MD5: e866dc2eed625dfdbcc22fec4e7a0b8f
Size: 3.57 MB
March 17th, 2012
OC 1.7-A HTC 2.6.35.10 (Gingerbread) kernel
- - 1.7GHz maximum CPU clock speed.
- - Undervolting? Slight
- - Insecure boot, see below:
kernel Info:Code:ro.secure=0 ro.allow.mock.location=0 ro.debuggable=1 persist.service.adb.enable=1
- - Modified CPU table to extend to 1.7GHz clock speed.
- - Re-scaled CPU table and L2 cache.
- - See post 5 for the list of CPU frequencies.
- - Max voltage 1.25 volts at 1.7GHz (HTC had 1.25 volts @ 1.5GHz)
We used the 1.25 volts HTC laid out for the 1.5GHz frequency for our 1.7GHz frequency instead. Runs great! ...and we stay within a voltage level that was already recommended to us through the code by HTC, so we are probably not putting too much voltage through the chip yet.
(we'll even see if we can knock that down a bit too, soon)
If 1.5GHz is where the dragon takes flight, then 1.7Ghz is where it starts razing villages ~ !
1.7GHz is where this device is most comfortable (in my opinion).
NOTE: 1.7GHz is above ANY manufacturer recommendations - you are your own warranty now. (pay out of pocket for breakage - you've been warned)
...The idea here is to give the superscaler dual-core processor the scaling options to choose from to take advantage of that ability:
I said that in the 1.5 kernel, but it's moreso true in this 1.7 one. There are a lot of options for frequencies that the Scorpions can use to scale to exactly the right level of effort needed to get the job done.
I am not sure at what point the table becomes too bloated and we see a hit on performance. I doubt very highly we've hit it yet, especially given the testing i've been doing - this is more a worry for pushing higher then 1.7GHz then here, but something to put out there now.
Compatible ROMs:
- - Stock 1.28.531.9 or 1.28.531.10
- - Bulletproof 1.1
- - ?
- - 1.55.531.3 software base
- - ICS Roms
- - ?
-
MD5: 8a55ea04d6f27bb142119b589fa7ea95
Size: 3.57 MB
March 17th, 2012
4
1188000 is considered the 1.2GHz rating by HTC/T-Mobile. (device manufacturer and carrier.)
Qualcom rates the chip at 1.2GHz recommended, 1.5GHz maximum. Every other device that has this chip runs at 1.5GHz.
...how is this fair to us?
Granted - they are trying to do a good thing - no doubt this is part of a solution to the battery issue after they got data back from the earlier Sensation launch.
In a lot of ways the doubleshot is singled out for being nerfed, Most of the people who would've gotten this device got the Sensation instead (basically the same device) because it launched a bit sooner. Then this gets nerfed on top CPU speed and turns away more potential buyers who go by the numbers in-store to compare.
So, now we fix - with HTC releasing the source code to the kernel a while ago, we can now do this ourselves and wake up the sleeping dragon at the heart of the doubleshot.
Suddenly, it's all okay - - the manufacturers decisions based on how they wanted to market the hardware are no longer something we have to just deal with and grumble about, now we can just go ahead and tailor the device to suit our needs.
I spent a significant amount of time crawling through the kernel source surrounding the specific hardware being used in the doubleshot, and ran around tracking down any scrap of information I could about the components and how they work. I bought the doubleshot based on it's hardware and what it was capable of.
Between all the device documentation found and the countless hours wide-eyed in wonder drifting through the kernel source for the device, I was able to employ everything I learned about overclocking desktops and graphics cards over the years.
I sat down with my calculator and ran all the numbers to make a nice, mathematically balanced table based on the various multipliers that make up the device's internal speeds across the hardware inside.
This project was, and is, a goal of mine since before buying the device, and thanks to yogi2010's help it's becoming a reality.
Please forgive me for not having my source set up for download yet, I will get to that as soon as I can - meantime i've kept very detailed records and will get it all together and available.
Thanks for your patience on this!
Look forward to a nice and re-scaled 1.7GHz kernel soon...
Then I can spend some time on experimenting above 1.7GHz...
Mathematically there should be a bunch of frequencies available, but they are not as harmonious to the various multipliers involved and theoretically some of them should be unstable.
I don't recommend anyone run over 1.7GHz as the risk of permanent damage to the device becomes pretty severe after that.
That all being said -
Increases in the system speed like this, beyond manufacturers ratings, can be very dangerous in a permanently damaging way. I continue on for curiosities sake, and I have a doubleshot that I purchased privately, out of manufacturers warranty and with no insurance plan.
In short, I have a device I can melt and there isn't a person I can cast blame on beyond myself, for surely no one else is at fault when I eventually break it doing this.
Even if no immediate damage results from pushing the device far past it's design limits, the long-term lifespan of the device is dramatically reduced. The types of stresses I intend to put the machine through are not anything near normal or what it was designed for.
I'm curious. I'm driven to know, and so I want to see for myself first-hand what it can do.
The rule to overclocking is to find your boundaries and then work out the maximum stable settings you can use in both directions.
...Finding the low end of the spectrum is no biggie, can't hurt undervolting or underclocking anything on it...
...Finding the top end of the operating range, though, is a destructive art by nature.
I wouldn't want to put something I wanted to rely on and last me a while through this - a desktop, maybe ... a small electronics device, especially one like this?
I will likely get a lot of use out of the second device because it shouldn't kill it in just finding the boundaries, but it will likely be replaced with another doubleshot when it starts to die and retire into salvageable parts for repairs.
In short: I bought a device to use for development and curiosities sake - it's not even attached to a plan. Be aware of the stresses overclocking can have on your device and think carefully before overclocking your device.
Once again, I do NOT recommend running above 1.7GHz - I do see a noticeable level of improvement in FPSE playing Castlevania: Symphony of the Night, and the benefit of reasonable overclock is real. Above 1.7GHz is not reasonable but possible.
If we had more RAM, we could hold a higher stable speed, but the device performs admirably and is something I am proud to own. HTC and Qualcomm did a damn fine job on the hardware this thread is about.
Just about any gripes I have about the device are limitations of software, be it apps, the OS or the kernel itself. Since we have the 2.6.35.10 source we can work on fixing things like this and more.
kernels take time to develop, but having control over how the device physically operates enables you to streamline it's processes and do it's job more efficiently.
I look forward to the HTC release of the kernel source for the 2.6.35.13 kernel from the OTA!
Projects like this would not exist without the open source community and places like XDA.
Thank you all.3here is a screenshot of my battery usage with the UV6 kernel, on the stock 1.28.531.10 ROM, rooted and debloated of course, and using the stock battery. granted, i slept 7 of those hours, and i wasn't on the phone constantly, but i put in at least moderate data and texting use, and a quick call or two. i'm decently happy with it so far.
there hasn't been a ton of support for what HTC has done, software-wise, with our device, but i tend to think it runs pretty well, and that kudos are deserved. the 1.55.531.3 ROM especially seems nice and balanced, with steady battery drain, and few bugs. we would like to develop for the that new update, but for now are basically learning and working with what kernel source we have.
