yashsingh1/xdaforums huggingface dataset:
[HD2 Android NAND Development] wheeliemonster:
I'm struggling with the 128MHz clock speed. I've used both the HierOS 1.7.5 btfix kernel and Tytung r12.4 and both have the same issue.

If I allow the CPU to scale down to 128MHz while playing audio using the default music player, the CPU seems to get stuck at 128MHz and the whole device slows to a crawl.

Anyone else seen the same. I've posted about it in the HierOS kernel thread too to see if anyone knows why.

When I saw the 3.6.9 update includes a change to the 98cpu_voltage script, I edited my own 98cpu_voltage to include the additional voltage level for 128MHz but it's done it again. :eek:

Is it worth increasing the voltage level for 128MHz or does that defeat the object of running at that speed? (i.e. battery life!)

This is all using the interactive governor. Should I be using a different governor with 128MHz?

Thanks
[HD2 Android NAND Development] cokyc:
Thank you master tween.
[HD2 Android NAND Development] tyween:
Some people might have problems with 128mhz, it might not be enough for wakeup and may cause the old "sleep of death." Tytung put this frequency in for testing but warned that it may cause problems. I am experimenting with it myself currently, and am not sure if I will keep using it. I am not even really seeing less standby battery usage by using 128mhz.. Though I have not had any problems to note yet.
[HD2 Android NAND Development] cokyc:
install 3.6.8 and 3.6.9

I you install 3.6.8 or 3.6.9 cleaning dalvik cache you will be stuck at android white screen.

if you update from a previous version without cleaning dalvik cache the phone boot ok.

Basically, every time you clear dalvik cache the phone stuck at first boot.
[HD2 Android NAND Development] Denkov:
I have problem when I am listening .flack music over Bluetooth even with 245mhz. I heve to use next frequency. When i use 128mhz and listen music I have SOD!

---------- Post added at 05:22 PM ---------- Previous post was at 05:18 PM ----------

I use ROM Manager and always clear Dalvik cashe and never have problems with upgrade since 2.5.8!
[HD2 Android NAND Development] xanthrax:
mmm ... i don`t think so ... i just wiped cache and dalvik cache and the phone boot was faster than previous builds updates so , it`s imperative to clean those caches . ... and there is no WHITE screen anywhere ... in fact it`s black , the android icon is ... white , or , am i wrong ? :D
[HD2 Android NAND Development] negativman:
Can be asked earlier? After restoration of programs from backup copy Titanium Backup all programs are displayed in a market as established, but after a while many established programs in a market aren't present. Their search in a market shows "the appendix not compatibly with phone". How it to correct?
[HD2 Android NAND Development] cokyc:
just cleared dalvik cache and my phone is at white android screen

here is logcat

seems there is some problem with dexopt core.jar.

Or maybe a problem with my nand memory?

PS.

I have an sd-ext partition on my sd card.
[HD2 Android NAND Development] uzi2:
Why do you say it is imperative to clean the caches?

I have updated several builds without doing so and have not encountered any problem. I see it as a thing to do only if you have problems...
[HD2 Android NAND Development] mrled:
I was using 128 mhz with 825 mv and all is ok.

First i was using 800 mv but is unstable.

Im using profiles on set Cpu

Screen Off 128-384 mhz

in Call 245-988 mhz

Normal 128-1152 mhz, i cant use 1190 because my phone freezes with any volts

with 128 mhz i have 1 mA lower when is in standby.

I'm using 3.6.9 and everything is OK.

Thanks Tyween and sory for my bad english..
[HD2 Android NAND Development] digitalgrafix:
I come back to tyween rom this day and i had the same problem.

Reboot your phone. If you take a look with adb logcat and will see that the phone loop at that line when the volume is setting to 100. Then just copy framework.jar and framework-res.apk from the last nightlies to your phone in framework folder with droid explorer. Then you will see the 2nd animation. After that everything is ok

The same trick works for Dorimanx rom too. I had it before.
[HD2 Android NAND Development] xanthrax:
bump ... , my bad ! i was trying to say that`s , as you say , necessary to do so ... you`re right , that word (IMPERATIVE) is ... too much ... :rolleyes:
[HD2 Android NAND Development] tyween:
Strange. I always wipe cache/dalvik and have never had this problem. Might have to do with modded framework?
[HD2 Android NAND Development] cokyc:
Just flashed v 3.6.9 without mods.

Same problem.

while phone is i white android I see (with droid explorer) only two files in /sd-ext/dalvik-cache folder

system@framework@boubcycastle.jar@classes.dex

system@framework@core.jar@classes.dex

then stop recreating the rest of cache.

After reboot looking at logcat there are some error when system trying access at these files in cache.
[HD2 Android NAND Development] digitalgrafix:
The boot loop at the line:

Setting in-call volume to 100

Few lines above is the error which cause the loop:

Size mismatch on inflated file

I don't have the logcat of your rom. Here is a part from Dorimanx rom logcat but the issue is the same: framework
[HD2 Android NAND Development] jolas:
I do the same cleanings without any problem.

Also, in last two ROMs I flashed the new ROM using modded framework (via UOT Kitchen) and after wiping cache/dalvik, everything loaded ok.

By the way, I installed zeppelinrox SuperCharger script and I have to say that it made my phone run smoother...
[HD2 Android NAND Development] KuZZo:
Flashing 3.6.9, wiping cache, Dalvik, fix permissions... first boot around 2 minutes, no problems, as usual.

But, same WLAN issue as in 3.6.8 - No WLAN connection at all! (even not if waiting 10 minutes)! Fix: enable flight mode, disable flight mode: WLAN works. very strange...
[HD2 Android NAND Development] MarkAtHome:
Feel free to give me a swift kick, if appropriate, but is it possible, upon boot, to delay all non-system apps from loading until the OS completely initializes?
[HD2 Android NAND Development] nilsk123:
upgraded from 3.6.8 to 3.6.9 via clockworkmod, cleared dalvik first, boots just fine.
[HD2 Android NAND Development] tyween:
Yes, you can use something like autostarts to accomplish this. I use it to stop certain apps from starting up that I would rather not automatically start. There may be another way to accomplish that, but I have been using autostarts for some time and it works very well.
[HD2 Android NAND Development] digitalgrafix:
Copy the framework-res.apk and framework.jar from the last nightlies (220) to your system/framework folder with droid explorer.

Try first with framework.jar

I had the same problem with Tyween and Dorimanx roms.
[HD2 Android NAND Development] wheeliemonster:
OK - that's fine. I'll disable it for now as I'm having problems. I never get SOD - everything comes back to me eventually, it's just you can really tell the device is running at 128MHz as it's deathly slow!

Thanks for the feedback.
[HD2 Android NAND Development] dainar:
zeppelinrox SuperCharger script

I have not yet had time to install the new rom (3.6.9) but I installed the script that you suggested in the rom version 3.6.6.

It seems to me that the device is much more fluid. Thank you.

PS: but you could not inclure these scripts in the rom?
[HD2 Android NAND Development] bzdemes:
3.6.8/3.6.9

I have had zero joy flashing 3.6.8/3.6.9. I was just getting stuck at the white Android of DOOM! I saw someone post NOT to wipe dalvik cache so I flashed back to 3.6.7 booted fine then went back to cwr and cleared cache then flashed 3.6.9 and its booted and looks to be working!

Cheers!
[HD2 Android NAND Development] PresidentMcCain:
Guess I'll stay with 3.6.8 for a while.
[HD2 Android NAND Development] nomad10002:
Once again great job. 3.6.9 installed without any problems. Everything is running smoothly.
[HD2 Android NAND Development] jc monkeyballs:
So I'm confused...

should I or should I not wipe the Dalvik cache ?
[HD2 Android NAND Development] tyween:
My stance is that the cleanest way to upgrade between builds is to wipe the dalvik cache and fix permissions. If this causes issues, something is wrong with the ROM. It seems like those with issues were using a modified framework rather than the stock framework.
[HD2 Android NAND Development] cokyc:
Correct me if I "m wromg, but isn "t cm7 build 220 the same as this v 3.6.9 ?
[HD2 Android NAND Development] tyween:
This is correct. Like I said above, if anyone gets an error with framework it is most likely due to using an old version of tablet tweaks or cLK wifi tether. The ROM includes the correct version of the framework for the CyanogenMod build. People just need to stop flashing old versions of framework modifications. Please stop declaring something is wrong with the ROM when you modify it incorrectly then break it.
[HD2 Android NAND Development] lslight:
Since 3.6.0,

If I upgrade with "wipe cache partition", "Wipe Dalvik Cache" and "Fix Permissions", I get 40 minutes for the first boot, a huge amount of FC and then another 30 minutes to boot.

If I upgrade with just "Fix Permissions", I get 12 minutes for the first boot and no FC.

And I don't use modified framework. I don't even know what it is.

Btw, this is a wonderful ROM and those littles problems are nothing compared to the happiness I have with my "old" HD2.
[HD2 Android NAND Development] tyween:
How many apps do you have installed? Wiping dalvik cache does increase boot time as the apks must be deodexed. The next boot should be faster. The more apps you have the longer the boot will be, it is as simple as that.
[HD2 Android NAND Development] digitalgrafix:
I had trying to install DM rom for about 1 week. I had trying everything, clear all, format the SD ext3 and ext4, task29, reinstall hspl, cwr and so on. The same issue - wrong size of inflated file. The problem was solved replacing the two framework files. Because of many problems of the DM rom I decided to switch to your rom. Then I facing the same issue with your rom. I had replaced framework jar and apk. Now I write from your rom and I installed the rom without any twaks.
[HD2 Android NAND Development] lslight:
76 apps

with /sd-ext : app 376 Mo, davlik-cache 128 Mo, System data 65 Mo.
[HD2 Android NAND Development] googlephone:
Why we need the 128MHZ thing when it costs more than bennifit?
[HD2 Android NAND Development] eddyedwards007:
Installed this Rom with Rom Manager Pro, after download on phone it took about two minutes to finish booting, in fact it was that quick, at first I thought it couldn't possibly have installed properly! Fantastic ROM, running smoothly.
[HD2 Android NAND Development] Panda_Face:
Last I checked it does help.
[HD2 Android NAND Development] FileFixer:
Is it possible to edit cpu0 settings for more then 1190MHz?
[HD2 Android NAND Development] Panda_Face:
You'll need a kernel which can allow that.
[HD2 Android NAND Development] tyween:
Not with the tytung kernel. You can switch to a different kernel if you wish to use a higher overclock. However, clock per clock the tytung kernel is faster if you test it with any benchmark. From my own personal testing a 1.5ghz overclock does not help performance enough to warrant the increased battery drain and required voltage to run the higher clocks. Past 1190mhz the performance increases do not scale as well. To each his own, so flash a new kernel if you would like to experiment!
[HD2 Android NAND Development] mzebrowski13:
Are you kidding me? 40 minutes? Even roms with Sense 3.0 and mass of stuff on ext doesn't boot that long. Do you have ext2 on your SD?

Sent from my HTC HD2
[HD2 Android NAND Development] mknewman:
That is consistent with what I'm seeing.
[HD2 Android NAND Development] Wickster:
this is just more of a try it out post to those who likes to change their phone profile to download more apps in the market by changing their build.prop. I thought I would post the latest phone profile (here in the U.S. anyway) for T-Mobile released phones.

Here is the latest values for Samsung Galaxy SII build.prop info.

This should trick the market into thinking you have a Galaxy S II. :)
[HD2 Android NAND Development] materoprodutions:
tried to update 3 times, downloaded the file 3 times form 3 different mirrors, md5 seems ok. copied both from card reader and from mount storage, still same problem.

when I install from CWM I get bad file installation abooìrted. any ideas?

Trying to update from 3.67 to 3.6.9 CLK...

Thank you
[HD2 Android NAND Development] mskip:
You cant flash a CLK Rom via CWM..

You need to download the MGLDR version and flash it via CWM Recovery and it should work fine.

Mark.
[HD2 Android NAND Development] xanthrax:
:D that`s a little bit funny ! :p
[HD2 Android NAND Development] themadproducer:
Here is the most recent version for 3.6.6 and might work with 3.6.9.

http://xdaforums.com/showpost.php?p=17964468&postcount=18297
[HD2 Android NAND Development] materoprodutions:
sorry I meant from recovery mode. I remeber I updated this way with other CLK roms.What I did was:

reboot recovery

install zip from sd card

choose zip

Of course clear dalcink cache and fix permission...

I get the same abort error. There is another way to update CLK without doing a clean Install?
[HD2 Android NAND Development] themadproducer:
with magldr, this is what I have done on occasion (not sure if the same is do-able in CLK)

- go to cwm and do a backup

- wipe everything (reset)

- install new rom

- after settling in and maybe a reboot...I go back into cwm

- I do an advanced restore of data and ext...(can't remember the fine details)

It takes longer when I do it this way but it has at least 2-3 advantages...

- no force close flurry followed by battery pull....routine

- installing the fresh rom initially tells you if the latest release is healthy (not corrupted) and there is nothing in the way to botch the install.

- sometimes has helped me install stubborn updates that with my usual install method, did not work.
[HD2 Android NAND Development] scariola:
They work great on 3.6.9.
[HD2 Android NAND Development] themadproducer:
Good to know...thanks
[HD2 Android NAND Development] yetinet:
first boot

I don't use any framework other that what you include in your ROM, and I don't modify your ROM at all. A clean install of 3.6.8 - task29, magldr, cwm (v4.0.1.4) (repartition and format both SD and System), TyphooN CM7 3.6.8 - First boot hangs > 30 minutes, pull battery. Second boot fine. No FCs.

The hanging first boot is not to do with many apps installed. There are none at that stage.

I'm using a 512MB HD2 with 1G ext3 partition and no swap on a 16G SD, 170M system, 5M recovery, 5M cache.

Tyween, I love your work, and have no intention of even considering another ROM.
[HD2 Android NAND Development] eclipxse:
Problems with themes CM7

Everything installed smoothly but im having some problems keeping the selected theme with the theme chooser after each reboot , also the ADWlaunchpad theme is resetting to its default setting...Anyone that know what may be the issue or some sort of workaround?
[HD2 Android NAND Development] materoprodutions:
having a weird problem. when people call me I hear fine but they hera themselves twice, some sort of echo....any fix? Thank you again
[HD2 Android NAND Development] seanyuan62:
Are you on latest version? Echo problem should be fixed in tytung r12.4-works perfect for me after echo issues in older versions of ROM
[HD2 Android NAND Development] fx.dcny:
Really!

So nobody knows why a US TMO running Tyween's rom wont pick up a network on a sim card in India from any network?
[HD2 Android NAND Development] gdsbalaji:
work good for me all of the tyween roms..check if you flashed the right radio

---------- Post added at 05:04 AM ---------- Previous post was at 05:03 AM ----------

move adwtheme to the phone memory

---------- Post added at 05:05 AM ---------- Previous post was at 05:04 AM ----------

A clean install of 3.6.8 - task29,

RADIO

, magldr, cwm (v4.0.1.4)
[HD2 Android NAND Development] tone_la:
FIOS Mobile Remote Blocked!

Trying to install the "FIOS Mobile Remote" app and the market says it does not support the HD2. I'm running the latest TyphooN 3.6.9.

https://market.android.com/details?id=com.verizon.android.wifios&feature=search_result

I know some have edited their build.prop file to change the market filter. Is this the only way to get this app? I did a search and could not find the latest apk anywhere.

Thanks in advance for any advice here!
[HD2 Android NAND Development] ph03n!x:
I have a T-Mobile HD2, using it in India for a while. I am on Typhoon 3.6.8, works great.

Does it work with another ROM for you? Windows Mobile worked alright?

Swyped from my HTC HD2 running CM7 (Gingerbread 2.3.7)
[HD2 Android NAND Development] negativman:
The market incorrectly works if to put screen density more low 240 by default. How it is possible to bypass it? The screen with density 192 looks very well.
[HD2 Android NAND Development] Tiller:
Hi guys,

I'm running the last Typhoon version, but I've a little problem.

My phone won't tranfer data. The upside arrow light up, but never the down one. Do anyone else experience this bug, or any idea to fix it?

Thanks :]

Edit: Fixed, Sorry it was my fault. Bad APN..
[HD2 Android NAND Development] geenyous:
I have had the same experience here and on other CM7 ROMs too, from time to time the cpu gets stuck at the lowest setting (beeing 245 or 128, also on interactive). I am sure others are experiencing the same but just don't realise that its caused by that. Whenever your phone is lagging, go into setCPU and check the frequency, you will see that its on the lowest possible level and won't increase. If you then manually set the lowest level higher, it won't decrease below that value anymore, unless you turn of your screen again and the "245 at screen off" profile kicks in (of course after you have already set the lowest level back to 245/128).

It fixes itself after some time, but is really annoying.

I think it might be related to setCPU conflicting with the cyanogen settings, but I'd rather disable the cyanogen management of the CPU somehow as I need one specific profile to prevent my phone from freezing during navigation.
[HD2 Android NAND Development] yetinet:
First boot hangs

Thanks BJ but installing

RADIO

made no difference at all I'm sorry to say. I waited over an hour to be sure. At least I'm now on 3.6.9 ;)
[HD2 Android NAND Development] Revhead:
Still having trouble updating here.

3.6.7 no problem - 3.6.8 or 3.6.9 hangs on first boot.

Never had a problem before _ has anyone worked out why it is working for some and not for others?

Nothing special about my phone or my installation.

There must be a point of commonality with those having trouble.

Have tried 5 different downloads and MD5 checks out okay?

What the hell has changed. . .
[HD2 Android NAND Development] yetinet:
All I know is that if I wait some time then pull the battery, the next boot works correctly and I have no further problems after that.

It really is a minor inconvenience that occurs once per clean install - I'll live with that and this fine ROM until someone cleverer that I finds a fix.
[HD2 Android NAND Development] cooper_s1:
I just pulled the battery after 5 minutes waiting. After that my phone booted right away. Had this with 3.6.8 and 3.6.9.
[HD2 Android NAND Development] geenyous:
Same here, started with 3.6.8.

I backed up, installed 3.6.9, installed tt & tether fix, wiped dalvik, cache and fixed permissions, then reboot, waited for 40min, then pull bat and all ok.

I have an ext-3 partition and a swap partition, maybe the swap causes some kind of error at first boot as someone mentioned before...?
[HD2 Android NAND Development] Gusti:
The same with me, starting with 3.6.8 and continuing with 3.6.9...

I guess there's a loop somewhere.

Resetting the phone after a few minutes (pressing the little red button inside) helped with both versions and after the reset the first boot took (as usual) 3 to 4 minutes...
[HD2 Android NAND Development] cokyc:
I have done a test.

I have removed the sd-ext partition from sd card

wiped caches and flashed rom with tablet and clk tether using ttmaker

reboot

The phone rebooted fine (first boot OK)

Seems there is asome problems with sd-ext and dexopt core.jar and bouncycaste.jar from recent cm7 builds.

I am not a expert but I think there is a sync problem from zipaligning and recreation of dalvik cache.

There are some errorn in logcat where is not possible access core.jar dex and bouncycaste.jar dex.

I think this problem not exists when no sd-ext because the speed of nand vs speed of sd.

This is just my thought.
[HD2 Android NAND Development] uzi2:
You may find it better when updating to install just the ROM first. This should be up and running in about 5mins. Then go back to recovery and install whatever other zips you need. No waiting 40 mins, no pulling battery (why can't people use the reset button?), no wiping caches, no fixing permissions.

I have a 1GB ext4 and small swap partition, so similar set up to yours.
[HD2 Android NAND Development] gear_rus:
;o

Strange issue... Is compass working for you guys?:confused:
[HD2 Android NAND Development] Rizsi:
I used Typhoon 3.6.8 clk. When someone call me and i pic up i say hello but, the other side not hearing me ca 2sec. Update to 3.6.9 the problem is not solved. The mobile network isnt work properly.
[HD2 Android NAND Development] ph03n!x:
Looks like the second phone is not unlocked, and that's why is works with T-Mo and no one else? Do you hey any prompt for giving it a Sim unlock code? If you are not, go back to Windows Mobile on it and but an unlock code for it...

Swyped from my HTC HD2 running CM7 (Gingerbread 2.3.7)
[HD2 Android NAND Development] geenyous:
Notification LED and custom brithness levels

Thx uzi, thought of that too after it didn't work for the second update and I read the framework related error infos..

Regarding the reset, I had no pen near, but I usually also don't pull the bat but reset the phone instead ;)

@ all:

If you want to have custom brightness levels and don't care if your LED stays solid amber when there is a notification instead of flashing amber (who could care??), get this file, copy it to system/lib/hw, remove the lights.htcleo.so file (best to back it up first), rename the file to lights.htcleo.so, set permissions to rw-r-r and reboot.

Voila, you now have working LED AND custom auto brightness. :D

Now the only thing to make this even better would be a green LED notification, that way you could immeadiately see when there is a notification when the phone gets charged if it happens at a time when you can be certain that the phone isn't fully charged yet, but that's now splitting hairs... ;)

EDIT:

....and done :D

see below, thx Looki75!
[HD2 Android NAND Development] Looki75:
Keep everything as you did (your mod with replacing the lights lib) and setup a solid green LED for notifications in CM7 settings.

You can even choose which notification gets which color!

My settings:

* green for: new Handcent sms, new TouchDown email, new Kaiten email

* red for: missed call, root call blocker

If you can't make it work, PM me and I'll send you a detailed step by step procedure!

Cheers
[HD2 Android NAND Development] letrain02:
3.6.9 wont retain any system data. Tired using titanium to restore. No luck. Did things manually...wont retain any changes I make to system, (I.e. status bar, email accounts, wifi, bluetooth
[HD2 Android NAND Development] mzebrowski13:
:D:D:D:D CLK with ext4, clean install without problems and I'm in shock, never-before-my phone does not stand so long without charge. Battery life is simply AWASOME!!! I'm quite heavy phone user and I've lost 30% in 7 hours with the mass of the phone call, browsing the Internet, checking e-mail. Yesterday on Hyperdroid CM at this time I was looking for a charger:D