yashsingh1/xdaforums huggingface dataset:
[HD2 Android NAND Development] noellenchris:
you can use root explorer or the like and long press and use a txt editor.

Goto the 2nd paragraph of settings and change the 240 to 220 or 200(thats what I use cause it's the best on my HD2 :P) then save the file and restart.
[HD2 Android NAND Development] RRibeiro:
Thanks.

Obrigado. ;)
[HD2 Android NAND Development] tyween:
Glad to hear it is working out great for you guys! Some might even be able to tweak lower.. However it won't be stable for everyone, but it's worth a shot. Here is the original thread for the voltage control interface: http://xdaforums.com/showthread.php?t=821372

As you can see in my script, I adjusted to the lowest possible value that I found stable for my phone on each frequency. I feel that is the best way, however.. if you want a quick and easy way, you can also do it this way:

incrementing/decrementing all levels by a specified amount* (mV):

echo '-25' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels

echo '+25' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels

All you would have to do is delete everything in the current script, and just have + or - the value you would like.. it would apply it universally. To see current levels type cat /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels . All of these commands can be done via adb shell, gscript lite, or editing the init.d script I have provided.
[HD2 Android NAND Development] Kameirus:
can anypne tell me the differernces between cwm 3014 and 3019

Thanks
[HD2 Android NAND Development] googlephone:
Your numbers worked on V2.7.0. Got frequent reboots on second animation after upgraded to V2.7.2.

Now I am using the UV925 values w/o problem:

245000: 925

384000: 925

422400: 950

460800: 950

499200: 975

537600: 1000

576000: 1000

614400: 1025

652800: 1050

691200: 1075

729600: 1100

768000: 1125

806400: 1150

844800: 1175

883200: 1175

921600: 1200

960000: 1200

998400: 1225

1036800: 1250

1075200: 1250

1113600: 1250

1152000: 1275

1190400: 1275
[HD2 Android NAND Development] windroidHD:
shouldn't it be 217?, I personally use 217 after I read about how it's calculated.

sqrt(800*800 + 480*480)/4.3 =~ 217.

Wiki Link, some values on wiki might be wrong.
[HD2 Android NAND Development] mikelt89:
Does it have battery percentage?
[HD2 Android NAND Development] Petulinek:
No, it doesnt
[HD2 Android NAND Development] lenarass:
now we are talking man.!!! RAM version.....!!! trying to load 1.8v and earlier and it was taking AGES to load.... just delete these crap versions coz they waist my time.. 1.9.v just installed and i will test them. i think many ppl agree with me if not say why
[HD2 Android NAND Development] tyween:
No, and it won't until this is a feature within CyanogenMod. As stated in the OP the purpose of this build is to be just like the Desire CyanogenMod with minimal changes. This includes me not adding apps or features like this.

Actually the RAM version takes longer to load on boot, and always will(in comparison to a normal version.. due to how it boots). The purpose of keeping old builds in the OP is in caes something bad happens, you guys can still find the old files instead of waiting for me to repost an old or fixed version. With the changelog you can pick which cyanogenmod nightly that the build is based on, and see what features are new or fixed. This helps you troubleshoot something if something is broken. I see that as an advantage, and imo none of the versions of my build are crap. They have all been relatively stable. If you want me to take you seriously I suggest that you don't call my work crap. It's not like I was going to in the first place as you cannot spell or write in complete sentences.
[HD2 Android NAND Development] Frank1924:
tyween,

Bravo!
[HD2 Android NAND Development] mikelt89:
Can someone helo I am stuck on hd2 logo bootloops and I have done everything as soppose to including the 125mb partitision form first page, Cyanogan mdj works just fine.. what am I doing wrong?
[HD2 Android NAND Development] [zozi]:
do you make a full wipe?
[HD2 Android NAND Development] noellenchris:
So what's the general opinion of the speed diff between v1.8 and SuperRam v1.9? How much faster does it feel. v1.8 feels faster now finally than the CM 6.X builds and now tyween has gone over the top and implemented Darkstone's SuperRam. Just curious to see opinions....:P

Chris
[HD2 Android NAND Development] mikelt89:
Yes I did clean install with task29 . and than just intalled the zip with CWM from SD recovery ( with magldr 1.13 of course and 1.3 CWM) I know that if I install MDJ Cyanogen 7 it will just work fine.
[HD2 Android NAND Development] DroidTh3ory:
I flashed it about an hour ago and it feels extremely smooth and very fast. A side from the lack of status light functionality it is near perfect. The switch to SuperRam was a perfect move for this ROM.

The feel or speed and smoothness is excellent.
[HD2 Android NAND Development] pack21:
This build has reached a new level of karma, is really very good, I do not know if the speed could be further improved, the only thing that may be can, is an approximation is the smoothness of the screen touch of an iphone, but this depends from kernel improvements.

EXcellent job.
[HD2 Android NAND Development] cheezusweezel:
+1

It's fast, it's smooth, nearly perfect.

But I'm a little confused that after the first reboot all of my installed apps were gone. Now I'm frightened about the upcoming reboots ... :D
[HD2 Android NAND Development] [zozi]:
i will install right now and i will see whats happens
[HD2 Android NAND Development] mikelt89:
You killing me here , I cant wait to load this build but I am stuck on bootloop can anyone explan what partitions size he used to boot it from CWM?
[HD2 Android NAND Development] DroidTh3ory:
I'm using the 150 Clockwork Image... and I used Clockwork to Partition the SD card. Using 256 with 0 for the EXT partition. No issues.
[HD2 Android NAND Development] lolmensch:
i used the recovery provided in 1st post.

just flashed the recovery (i was on wp7 and have magldr 1.13)

partitioned on 512mb ext 4 and rest fat32

flashed the zip and voila. no task29 or whatever
[HD2 Android NAND Development] [zozi]:
nothing here.. i can boot...

but the task29 dosent format your SD ext. may be its that... i need make a full wipe include de ext on SD....

i do and works form me...
[HD2 Android NAND Development] LordDeath:
After starting google maps once the GPS-icon in the notification bar doesn't disappear anymore. Can anyone confirm this problem?
[HD2 Android NAND Development] smickez:
What is the name of the Clock Widget shown in the print screens :-D?
[HD2 Android NAND Development] pack21:
It happened to me 1 time in V1.8, all my install app seems disapear..... but after a reboot they come back.... not a big deal....I'm just searching for nirvana performance. :D
[HD2 Android NAND Development] Conny:
UV stable - battery test

It would be fine to post tests from users how effective is to undervolt core

with forexample tyween numbers..

I mean in EXACTLY the same test (just 10 calls for 5 min, youtube vid using wifi, angry birds for 20min, other time standby.. something like this.. and make it comparable with original numbers and the UV ones..)

After such a test it can be proven this hack gives some between 5 to 10% more time (guess)..

Because all I can say is - it's stable.. But the more time on battery? Don't know HOW much :)
[HD2 Android NAND Development] tyween:
You are right, but try out 217 as your density. A lot of programs are really, really strange looking. 220 seems to work out for most programs, and is very close to what native res should be. I had strange things happen even in ADW launcher with 217.

As far as I am concerned, any battery saved is great. The screen is still the biggest battery hog and always will be. I haven't done any thorough testing, but right now I am getting the best battery life I ever had..
[HD2 Android NAND Development] mandy:
my adhoc wifi (WEP) does not work on 2.7.2.

my OS is win7 using adhoc wifi:

On tytung r7; for WEP does not do anything. WPA2 went up to Authentication only

On HyperKernel v5/6; for WEP works ok, connected with data. WPA2 same problem with tytung r7.

i am not sure about the battery drain on HK6.
[HD2 Android NAND Development] windroidHD:
tyween,

what governer do you use?.
[HD2 Android NAND Development] tyween:
I know that WEP works on tytung r7... My roomates at home do not remember the router login information so I cannot change it.. So I am forced to use such an insecure technology. I have been using it just fine on tytung r7.. Just so you know.. tytung and hyperdroid kernels are the same, they just have a different configuration.. so this makes no sense at all really. I made the choice to switch back to tytung because interactive governor did not work correctly in hyperkernel for me and several testers on IRC. I am not sure how that happened, but it did.. at least in HyperKernel v5.. I did not try it out in v6. Tytung kernel seems very polished and HyperKernel seems more experimental. You are free to use whichever kernel you want with my build, don't worry, it won't hurt my feelings :cool:

I use the interactive governor. I don't believe in the way smartass works.. I think that it can use more battery than interactive, by using more active cpu cycles when the screen is off trying to process something when the screen is off. I would rather the CPU scale up and complete the operation, then scale back down into its idle state. Try running fix_permissions via adb shell when the screen is off with interactive, and then with smartass.. you will see how slow and grueling this is with smartass. This is opinion, but also I feel that interactive is smoother in scrolling from my own use.
[HD2 Android NAND Development] pongster:
Actually, both kernels have the exact same config except for the default undervolting of the HyperKernel... (I followed michyprima's default which is actually the default 925 UV script in the source)

I checked the source and my interactive source is exactly like tytungs and raf's (which probably is a a reworked version of hastarin's based on michyprima based on huanyu's original patch) :)

I don't get the interactive lock but understand that other devices, which may not be up to the default 925 UV, may get the cpufreq stuck... It doesn't do this on my devices though... those users will need the init.d Vdd scripts to bump it up to their "sweet spot". :D
[HD2 Android NAND Development] raven_raven:
So now with tytung kernel this ROM should fully support extended battery, right?

And is it just me or there is problem with fully charging phone (it stays on 99% forever).
[HD2 Android NAND Development] CyberClaw:
Yes.

Also, extended battery takes much longer to charge. Taking it from 99% to 100% will take some time. The higher the charge, the longer it takes to charge the rest.
[HD2 Android NAND Development] mandy:
I like your build, this is the only build that works with me for more than two weeks now. I really don't understand why the adhoc WEP on tytung r7 won't work with me but anyway i use it only to download stuff/s.

great job anyway.
[HD2 Android NAND Development] cscott0108:
Does anyone know how to upgrade the CWM mod so I can make it the current 3.0.19 version, or what ever version we are on? I am unable to find this information on the net for the HD2
[HD2 Android NAND Development] xXZaufiXx:
first, really more than good build :) :) :)

now the question:

does the cpu frequenz change the boot time ? for example, i undervolted the kernel, starting '256000 850' ... each frequenz setp +25 - is this ok ?
[HD2 Android NAND Development] raven_raven:
Thank you. It took a while, but finally green LED lit up and my phone was fully charged. And nice to kniw that I can use my extended battery.
[HD2 Android NAND Development] Kameirus:
do a CWM backup, upgrade to the new recovery, then backup. Also, reinstall the ROM on top of your backup, just to be sure.
[HD2 Android NAND Development] Kupfel:
Tried that but it makes the statusbar icons all blurry (signal, wlan etc.). Too bad, I liked it otherwise.
[HD2 Android NAND Development] frankcilo:
with 2.7.2 I continue to have problem with gps fix....

Tomorrow, after upgrade to 2.7.2 all ok, but now ....no fix
[HD2 Android NAND Development] justaguyh:
tyween or anybody - i need help

took a video. "can't connect to camera."

ok. did a reboot, chose front camera and back one again, thinking it got it fixed.

nope.

after 1,2 videos my camera can't go back to functionality.

i'm running 2.7.1. but it's an issue i've been having with mainly i think the gingerbread biulds.

you think i should flash a camera zip file from other builds? if yes can you link me one? this isuue is annoying.

thanks...
[HD2 Android NAND Development] dumon:
I am just wondering if it is possible to decrease the minimum backlight level to

a lower value (to the level when the screen dims before the phones goes to sleep).
[HD2 Android NAND Development] Swenny:
When my camera stopped working, I installed Pudding Camera from the Market. Once I did that (may have needed to reboot) my regular camera started working again
[HD2 Android NAND Development] frankcilo:
after reboot, now gps is ok.... :confused:
[HD2 Android NAND Development] mknewman:
So you folks with reading problems, here's how to upgrade to new version of CWM:

Download 2.7.2 or whatever Typhoon build you want to your phone

Download CWM image for Magldr from http://xdaforums.com/showthread.php?t=987531 to your PC

Unzip the CWM image file and copy it over the one in your Recovery folder on your PC that you used to originally install Magldr and recovery

Boot into Recovery and do a full backup

Reboot into Magldr and go into USB Flasher mode. Run the DAF in the Recovery directory which will reflash the Magldr and Recovery images to NAND.

Once done reboot and go back into Magldr, enter Recovery, and INSTALL the 2.7.2 Typhoon build or whatever version you want.

After the install is done, go into Backup/Resotore and choose Advanced, and restore the /data directory.

Once /data is finished, in Advanced again, restore the /sd-ext directory.

When all that is finished, reboot, and you will get the typical slow first boot while it redoes all the cache and Davlik stuff, but once done you can reboot to Recovery and see at the top it says 3.0.1.9 and the new better menu stuff. All your state data will survive.

It worked for me, no problems, but if you brick your phone or something I take no responsibility.

Marc
[HD2 Android NAND Development] Charmacas:
Did anyone try it? :)

-- EDIT --

And how's the battery drainage with this kernel? :)
[HD2 Android NAND Development] Kameirus:
just updated to 272 and everything is working great

Thanks
[HD2 Android NAND Development] Swenny:
Does anyone else have a delay when unlocking the screen? When I unlock it, the screen will randomly freeze for 1-2 secs before it unlocks

Please note this is not the wakeup delay that I've seen mentioned before
[HD2 Android NAND Development] noellenchris:
the only fix I know of for the backlight, breaks the notification led. I used to replace this file all the time, but it's a picky fix anyhow and doesn't work 100% right. I used to use an older lights file. I can dig it up if anyone wants. Better yet, if we can get a dev to get both working that would great. I also use the phone to read in bed and it's usually dark and the phone is too bright atm.
[HD2 Android NAND Development] raven_raven:
Nope, everything is very, very smooth. No freezes or something like that.
[HD2 Android NAND Development] MatrimCauthon:
Here is the new cwm with 135/44

I think this is what you wanted. Tyween, I disabled animations in display menu and it is much faster. I would recommend everyone does this!
[HD2 Android NAND Development] Charmacas:
Which option in that menu do you mean exactly?
[HD2 Android NAND Development] buell75:
Setings/affichage ( don't know the name in English sorry)/animations/none

Just did it and waou ! so much faster ! :eek:
[HD2 Android NAND Development] MatrimCauthon:
No animations

Go to display in settings, then animation-change it from all animations to no animations. The animation brings the menus to you slowly. If you turn it off it will feel much faster.
[HD2 Android NAND Development] tmknight:
I haven't messed around with the settings too much but adding a Brightness toggle to the CM Widget and selecting a mode with "Dim" works for me. I have also set the custom dim level to a level below "Default" (i.e.10), but not sure if that does much (like I said haven't played around with it too much as it does what I need with the above settings).

Cheers
[HD2 Android NAND Development] TheCoutures:
I do get that as well from time to time I think it has to do with ADW Launcher loading all my widgets though from time to time
[HD2 Android NAND Development] the_scotsman:
I have mine set to 167...much much better and the icons are all sharp ;)

I use Launcherpro Plus to add more rows and columns to the homescreen so I have more icons....
[HD2 Android NAND Development] dlsniper:
There's no 100% support for the official or unofficial extended battery as the original (read HTC) battery driver doesn't exist for extended batteries on Android yet.

Arne's battery driver seems to work ok until now so you can use it for the official battery and from my knowledge no other battery that the official extended one is supported (I've read that other 2300 mah batteries might work as well).

Also for OP:

Can you please link to the change log of each CM_base_** build besides your own changes as I'm not sure where to find that information nor do I want to flask a rom/day given that fact that you are truly making this a 'nightly' build :)

Thanks for all your hard work for this rom.
[HD2 Android NAND Development] TheCoutures:
Running into an issue, can't move or edit any widgets from or off my tiles
[HD2 Android NAND Development] tyween:
You can try to correlate http://review.cyanogenmod.com/ to nightly changes based on date. They don't have it set to.. nightly 22.. or whatever.. there is no way to do what you have asked. If you don't want to upgrade on nightly then just check the site out, and see if anything has changed in the build besides the nightly that sparks your interest.
[HD2 Android NAND Development] TheCoutures:
Does Beautiful Widgets conflict with this build? I can't find anything in the thread that states other wise but it seemed to have freeze up my widgets in place had to reinstall build in order to get it to actually work again. Is this the widget?
[HD2 Android NAND Development] noellenchris:
I haven't had any problems and I'm almost positive that typhoon also uses beautiful widgets too. You might try removing it and re adding the widget.
[HD2 Android NAND Development] mattfmartin:
Im using it. Never had any problems with it
[HD2 Android NAND Development] TheCoutures:
I think it may have been a conflicting issue with weather widget (prior clock widget) and beautiful widget. I think it stayed running in the background even though the widget was removed. After complete install everything us running smooth and fast.
[HD2 Android NAND Development] windroidHD:
OP needs update?

tyween,

I think you should include below links in OP so people know what changes are being included with your bravo updates.

Desire Common Changes, Desire GSM Changes

Check both links to find the changes.
[HD2 Android NAND Development] mattfmartin:
ver 2.7.2 running silky smooth on cLK. Previous versions were sometimes sketchy as far as scroll lag from time 2 time. This one doesn't have that. Obviously this kernel is working out really well.
[HD2 Android NAND Development] pixine786:
market not working with 2.7.2

it FC on me. any one has patch for it?
[HD2 Android NAND Development] fcbarca17:
I got a lock on mine, same setup. Maybe reflash?
[HD2 Android NAND Development] zhensoso:
2.7.2 bug

andorid.com.phone always crash

I can't dia number
[HD2 Android NAND Development] philippebla:
hello ,no problem with beautifull W,
[HD2 Android NAND Development] sta1cs:
Getting SOD after SOD on 2.7.* after using the maps and navigation apps with gps, screen comes up but touch doesn't work.

Edit: So it seems my touchscreen stopped working out of nowhere, the above is just the last things I did with my Leo :( Flashing Ship ROM from TMO didn't work, calling in my warranty now.

I am looking forward to using TyphooN CM7 again :)
[HD2 Android NAND Development] MontAlbert:
got a link for the kernel/boot image you are using for clk?

thanks
[HD2 Android NAND Development] xxljmzlxx:
having no such problems with 2.7.2 its perfect. If your having problems try doing a clean install.

Can anyone post their UV values? I'm interested to see what everyone is getting.

This is my lowest value that is stable so far... anything under 900 for 245000 yields boot failure

#!/system/bin/sh
# set vdd_levels on boot by tyween (XDA Developers)

echo '245000 900' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '384000 900' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '422400 925' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '460800 950' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '499200 950' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '537600 975' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '576000 975' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '614400 1000' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '652800 1000' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '691200 1025' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '729600 1025' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '768000 1075' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '806400 1075' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '844800 1100' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '883200 1125' > /sys/devices/system/cpu/cpu0/cpufrq/vdd_levels
echo '921600 1175' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '960000 1200' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '998400 1200' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '1036800 1225' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '1075200 1225' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '1113600 1250' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '1152000 1250' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '1190400 1275' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
[HD2 Android NAND Development] mattfmartin:
Sure, its Typhoon _2.6.3_tytung_r7_clk_update.... Its on the first page of Cedesmiths thread;p I love how reboot to recovery is working and also rom manager.
[HD2 Android NAND Development] gav12345:
the boot animation is much better wow even my wife loves it

running great for me apart from it crashed when trying to open an app but i took the battery out and replaced it and then tried that same app and hey presto running great again

big thankyou
[HD2 Android NAND Development] MontAlbert:
thanks mate- i am using that one on , well, obviously, 2,6,3... :D
[HD2 Android NAND Development] TheCardPlayer:
hmm why changed to tytung kernel? does it still support extended battery? can i update without losing any data?
[HD2 Android NAND Development] Blubster:
I am using Hyperkernel V6 with the latest typhoon 2.7.2, seems to work perfectly for now for my cLK setup! :) It feels so much like a real Android device, with reboot to recovery and Rom Manager support (tricky to make work though!).

I installed typhoon 2.7.2, then hyperkernel v6 for cLK (here), and finally ppp.zip found here, all from CMR! :)

The cLK i used is this one, and finally the recovery is this one...

:)

have you tried "unlocking" your widgets? It is a feature of adm, accessed on desktop through "menu", "lock desktop"... :/
[HD2 Android NAND Development] raven_raven:
I'm seeing that cLK is really great alternative to MAGLDR, I'm thinking about transition to it. I think there is nothing left to do to call HD2 native Android device.