yashsingh1/xdaforums huggingface dataset:
[Desire Android Development] nvivas:
Currently I'm using the radio 32.47.00.32U_5.10.05.23.

This is the one i should be using right?
[Desire Android Development] nvivas:
Since i updated to that radio i get BOSD like every 30 minutes....:(

Using 4.6 with Havs. Dont have setcpu installed.

Any suggestions?
[Desire Android Development] @ngel:
As you can see in the dedicated thread, there's a newer radio out there.
[Desire Android Development] nvivas:
Thanks.

Are those radio all supported by Defrost/Richard?! Since i don't see mention to these versions in the 1st post....
[Desire Android Development] Marsbar:
The symptoms might have been, that doesn't mean that the cause is.

That was my point: setcpu is not required to achieve underclock. Try it: disable setcpu, run terminal emulator and type "cat /proc/kmsg" - you will see HAVS speed and voltage changes happily ticking along.

Of course, the universe has a sick sense of humour: 10 minutes after my post my phone hung for the first time in two days with HAVS + no setcpu. :(

I do stand by my i2c observation though; further it is still possible that setcpu increases the number of times the clock is changed and therefore increases the likelihood of a crash, so actually we could both be right :) :) :)

Of course I'm not even sure that i2c is how the clock speed is changed (is it?). That's why I said someone who knows how these things actually interact might be able to shed some light :)
[Desire Android Development] @ngel:
That's a good point.

I issued the shell command you suggested, and I've found that overclocking only is due to SetCPU: underclocking (and undervolting) are automatically managed by HAVS kernel itself.

<6>[ 313.630310] AVS setting V to 1150 mV @806 MHz
<6>[ 313.649932] AVS setting V to 1125 mV @806 MHz
<6>[ 313.669952] AVS setting V to 1200 mV @998 MHz
<6>[ 313.790191] AVS setting V to 1150 mV @844 MHz
<6>[ 313.800140] AVS setting V to 1125 mV @844 MHz
<6>[ 313.831054] AVS setting V to 1200 mV @998 MHz
<6>[ 313.870330] AVS setting V to 950 mV @384 MHz
<6>[ 315.191528] AVS setting V to 1200 mV @998 MHz
<6>[ 315.281646] AVS setting V to 950 mV @245 MHz
<6>[ 317.043304] AVS setting V to 1200 mV @998 MHz
<6>[ 317.203552] AVS setting V to 950 mV @245 MHz
<6>[ 317.858245] batt: 60%, 3903 mV, 165 mA (201 avg), 35.2 C, 817 mAh
<6>[ 322.188293] AVS setting V to 1200 mV @998 MHz
<6>[ 322.248474] AVS setting V to 950 mV @384 MHz
<6>[ 322.518676] AVS setting V to 1200 mV @998 MHz
<6>[ 322.608856] AVS setting V to 950 mV @245 MHz
<6>[ 338.023864] AVS setting V to 1200 mV @998 MHz
<6>[ 338.103942] AVS setting V to 950 mV @245 MHz

As expected, SVS kernels are completely silent about that: without SetCPU voltage and clock remains stable.

So, the story can be telled this way:

if you are interested in overclocking, you'll need SetCPU. Definitely.

if you are interested in underclocking/undervolting only, you'll need an HAVS kernel without SetCPU.

if you want a stock(ish) behavior, you'll need a SVS kernel without SetCPU.

if you want it all (UC/OC/UV), don't worry about HAVS/SVS choice: you'll need SetCPU. Again.

As a side note, and a consequence, a 1113 MHz HAVS kernel will run at 998 MHz only without SetCPU.

Now, the next step: reflash a 4.1 HAVS ROM and kernel, connect the phone to the PC, issue the cat /proc/kmsg command and sit back watching the screen.

In minutes, the Desire will lockdown and will be interesting to note down the last visible messages...
[Desire Android Development] m0nji:
interesting points. so i will try to deinstall setcpu and reinstall havs 1113mhz kernel again. lets see what happens
[Desire Android Development] Marsbar:
+1 for that. Don't really understand why there's a time limit other than the amount of free disk space.
[Desire Android Development] Lennyuk:
well as far as I know its to stop you burning your phone out, it gets pretty warm after 30 minutes recording.
[Desire Android Development] MThen:
Hi,

can't find an exact link at the moment, but the 30 minutes restriction is due to a European tax law, where devices able to record longer videos are treated as camcorders.

Greetz!

M.T.
[Desire Android Development] EViollet:
That's strange because the default Sense ROM allows for recording without limit.

I've already recorded videos that last 1 1/2 hours under Sense without any issue. Is there any other software that can manage video recording on this ROM?
[Desire Android Development] Marsbar:
Just for more clarity, here's what I'm talking about with i2c and voltage problems: this kind of thing is always in my last_kmsg shortly before the crash.

[ 1063.095977] AVS setting V to 975 mV @245 MHz
[ 1063.097045] PM: suspend of devices complete after 10.701 msecs
[ 1063.098114] power_suspend_late return 0
[ 1063.098815] PM: late suspend of devices complete after 1.341 msecs
[ 1063.098815] clocks on: uart_clk
[ 1063.098876] wakeup wake lock: i2c
[ 1064.096313] msm_i2c msm_i2c.0: Transaction timed out
[ 1064.096710] msm_i2c msm_i2c.0: Error during data xfer (-110)
[ 1064.097961] PM: early resume of devices complete after 998.202 msecs
[ 1064.098388] msm_i2c msm_i2c.0: error, status c8
[ 1064.099121] msm_i2c msm_i2c.0: Error during data xfer (-5)
[ 1064.099548] ds2482 0-0018: i2c write e1 f0 failed, -5, retries left 5
[ 1064.100372] acpuclock: Unable to drop ACPU vdd: 245000.
[ 1064.100769] msm_i2c msm_i2c.0: error, status c8
[ 1064.101470] msm_i2c msm_i2c.0: Error during data xfer (-5)
[ 1064.101898] ds2482 0-0018: i2c write e1 f0 failed, -5, retries left 4
[ 1064.102752] msm_i2c msm_i2c.0: error, status 43c8
[ 1064.103149] msm_i2c msm_i2c.0: Error during data xfer (-5)
[ 1064.103912] ds2482 0-0018: i2c write e1 f0 failed, -5, retries left 3
[ 1064.104431] proximity 0
[ 1064.104827] proximity 0
[ 1064.105499] msm_i2c msm_i2c.0: error, status c8
[ 1064.105957] msm_i2c msm_i2c.0: Error during data xfer (-5)
[ 1064.106414] ds2482 0-0018: i2c write e1 f0 failed, -5, retries left 2
[ 1064.107269] msm_i2c msm_i2c.0: error, status 43c8
[ 1064.107879] msm_i2c msm_i2c.0: Error during data xfer (-5)
[ 1064.108642] ds2482 0-0018: i2c write e1 f0 failed, -5, retries left 1
[ 1064.109191] msm_i2c msm_i2c.0: error, status 43c8
[ 1064.109893] msm_i2c msm_i2c.0: Error during data xfer (-5)
[ 1064.110351] ds2482 0-0018: i2c write e1 f0 failed, -5, retries left 0
[ 1064.111175] msm_i2c msm_i2c.0: error, status 43c8
[ 1064.112365] msm_i2c msm_i2c.0: Error during data xfer (-5)

I assume that

"acpuclock: Unable to drop ACPU vdd: 245000."

is a typo and it should be writing vdd here not the cpu speed... or maybe there's a missing % in the printf (lol) if only it were anything like that simple.

Anyway, that's what makes me think the CPU and i2c are connected and why I think it's likely that's what's causing my crashes. I have four last_kmsges and each of them has this or very similar.
[Desire Android Development] davdavo:
I have a dream....

that one day AOSP ROMs will be stable like Sense ROMs :p

C'MON GUYS, YOU CAN DO IT.

Cyanogen & Kali - stop implementing 120 new features a day. We just want a stable ROM that works stably like a sense ROM.

No, I don't like sense, don't anyone tell me to reinstall it :D

P.S - DF 4.6 I had to take battery out. The same thing with OpenDesire .28

Atleast the new camera works better on Defrost :)
[Desire Android Development] Latty:
Keep in mind that even the SVS lookup table is running at lower voltages than stock, so technically you're undervolting even without using HAVS ;)

Rule of thumb is the following:

If you want to experiment with potential battery savings but potential lockups, try HAVS.

If stability is of utmost importance, install SVS (or stay stock).

Use SetCPU at your own risk, and if you do, don't blame the kernel for any problems :)

[1113 MHz should be stable for most people, but each phone may have a different overclock tolerance]
[Desire Android Development] Marsbar:
I guess they have the same issues as any developer.

1. Fixing bugs is boring. Doing new stuff is cool and fun.

2. When people ask for new stuff they tend to go "hey, you're really smart, can you do this? it'd be ace!!"

3. When people complain about bugs they tend to go "dude, you suck! you can't make anything work! why don't you fix it, asswipe?"

4. Fixing a bug you can't reproduce yourself is really hard.
[Desire Android Development] WhiteChristmas:
Has anyone managed to get quiet time working?

I've enabled the on/off times to test it and ticked all the options. I was expecting to see the silent icon appear when quiet time starts but nothing so I phoned myself the phone and the phone rang.

It'd be a nice feature if I could get it to work.
[Desire Android Development] aalexandrou:
Hello guys,

This newbie had been using DeFrost4.0 for the past 3 weeks and loving it. I find it especially useful because i can log on to my work's ipsec vpn server using a program called VPN Connections.

Today I upgraded to 4.6 and also updated the radio to the recommended 5.10.05.23

Now every time i try to run "VPN Connections" my phone freezes for a while and then reboots.

Any insights?

Thanks
[Desire Android Development] UpSpin:
Set CPU:

SetCPU is a tool to customize the min/max frequency and the governor.

Without SetCPU Android dynamically reduces or increases the clock depending on the load. So when idle, it downclocks to the min clock 245MHz, when the CPU gets stressed it increases the clock, using governor 'ondemand', to 998MHz.

With SetCPU you can tell Android to go even higher than 998MHz or set the max clock to something lower. With SetCPU you can use a different governor, like interactive. With SetCPU you can create profiles, so you can tell Android that, when the display is turned off the max. clock is 500MHz, display on max clock is 998MHz.

However, without SetCPU Android dynamically adjusts the frequency, too, and jumps to a frequency between lowest (245MHz) and highest stock speed (998MHz).

Kernels:

SVS: Static Voltage Scaling

Each frequency has a specified voltage. If Android increases the clock to 998MHz it automatically increases the voltage to maybe 1.3V. If Android reduces the clock to 245MHz it reduces the voltage to maybe 0.9V.

Richard can change this voltage values and undervolt this kernel. This means that he just changes the voltage value for each clock, reduces the voltage until the first crash occurs. So he was able to reduce the voltage to 1.275V @ 998MHz, instead of the 1.3V. Similar things happened with lower frequencies.

HAVS: Hybrid adaptive voltage scaling

Each frequency has a specified voltage range. If Android increases the clock to 998MHz it automatically increases the voltage to a value between the specified range. This depends on the ambient temperature, cpu load, etc. The advantage is, that it can reduce the voltage further than SVS can, sometimes! So if it's cold outside it will reduce the voltage further than the SVS voltage.
[Desire Android Development] onyxogen:
Problem

2 days ago I rooted my Desire and then installed the newest radio and defrost 4.5

Everything ran perfectly since then. Until today. :eek:

What happenend is that I woke up my phone and then I saw my pattern unlock screen. That's OK. Not OK has it been that I could not draw my pattern on the screen!! It simply did not react. Power on and off worked, but the touch screen appeared to be dead. If I held Power long enough I could see the reboot/shutdown menu and could sometimes navigate with my trackball.

I switched on and off and on and off and so on. After some time I could enter my pattern successfully - the touchscreen worked again. This has been reproducable after every standby. At least until the next reboot which I did minutes after because I did NOT LIKE THIS BEHAVIOR :)

Anyone experienced the same? I think it was not the wakeup bug because the system did wake up, only without touch screen support (for a minute or two).

Hope anyone can tell my anything about it... Thanks!
[Desire Android Development] danarama:
Just to add to this...

The main risk of overclocking the CPU is frying it. This is caused usually by a combination of high clockfreq and excess power/heat. The latter accounting for most.

As these kernels run at stock mV, that's not really a risk.

If the CPU cannot handle the freq, you'll get reboots. if this is so bad you can't change the clock freq to a lower value, just ensure you have an alternate kernel on your SD that you can flash from recovery.
[Desire Android Development] louisebb:
With 4.6, Openvpn Setting is not working, it always reboot. Any fix for this?
[Desire Android Development] misterdev:
Is there any way to have green as the main color of the system, instead of the stock orange ?

I can't find any theme that does only that.

One more thing : can i flash the battery circle mod + standard icons for defrost 4.5 with 4.6, or do I have to wait for it to be available with defrost setup ?

No more bsod since 4.4 with SVS kernel btw.

Thanks in advance.
[Desire Android Development] hshah:
Is there a BlackBar MOD for DeFroST?
[Desire Android Development] weirdNumber:
After installing 4.6 I had to reboot as the top half of my touch screen wasn't working. After that 4.6 wouldn't connect to my WiFi. It would obtain an ip then disconnect and start over. Plus it wouldn't establish a data connection. I had to disable data then re-enable several times before it would work. Went back to 4.4 and have no problems.
[Desire Android Development] mrsimes:
I get this sometimes, usually if wifi is enabled and not connected to an access point.

Try turning wifi off and see if it happens then.
[Desire Android Development] richardtrip:
Update:

Version 4.7:

CyanogenMod fixes:

* camera: Only show video focus modes when available.

* Gallery3D: Fix CM issue 1797 by unloading textures from GPU

* Added Filemanager

* Added CMWallpapers

* Added CMStats
[Desire Android Development] BSAB:
As always, thank you for your work, Richard!
[Desire Android Development] richardtrip:
VPN bug: Reflash a kernel with defrost setup (reverted to 4.5 kernel versions).

reverted: yaffs: Cache object xattrib state (breaks VPN :confused:)
[Desire Android Development] aalexandrou:
Hi Richard,

Thanks for responding. I dont understand your instructions though. Do you mean I should install a rom version lower than 4.5?

Thanks
[Desire Android Development] Latty:
Just flash a kernel via his DeFroST utility
[Desire Android Development] onyxogen:
Thanks for this posting, I'm going to try wether this solves this problem. Does turning off wifi in such a situation resolve the problem for you?
[Desire Android Development] kjpp:
What is CMStats ?
[Desire Android Development] zAo_:
Argg, more apps toe remove. Can you make the "File Manager" an option please? Thanks :)
[Desire Android Development] aalexandrou:
Hey Latty,

Thanks to you too...

In the utility there are 4 kernels: havs, svs998, svs1190 and wifiNmodule

Flash one of these you mean?

Thanx once again
[Desire Android Development] aalexandrou:
@Richard ; Latty

I downloaded svs997 and it did the trick!!

Thanks a lot guys!!
[Desire Android Development] buchman:
once again everything running great using the havs kernel.

Sent from my HTC Desire
[Desire Android Development] puffy1980:
Excellent once again Richard. I think that file manager is a welcome addition and excellent cm wallpapers. Just a shame Google voice doesn't work in the uk. That's not your fault tho!
[Desire Android Development] jimmytboi:
I've never used titanium backup before, can someone explain the quickest and easiest way to make a backup of everything ive downloaded from the market please, and any other necessary things i need to backup before updating.

Thanks

Jamie
[Desire Android Development] BrainMcFly:
installed 4.7

FC with titanium backup

"clearing data" does not help

also clearing data, uninstallijg and reinstalling from market does not work

any ideas?
[Desire Android Development] Latty:
Try "clearing data" of the superuser app
[Desire Android Development] cgorki:
wifi N

Just switched fron AuraxTSense, ROM is looking nice and very smooth!

only maybe need to get used to a "senseless" ROM :)

but what do I miss to get WiFi N to work?

installed the module - restarted my phone - still shows only g networks around me :confused:

not compatible with 5 GHz?
[Desire Android Development] Theteenystar:
I have the same problem with the FC at Titanium Backup but at the 4.6 Version.
[Desire Android Development] mr_clean5953:
Do the old circle battery mods work? If not where are the new ones?
[Desire Android Development] dw515:
Just clear the data/cache of Titanium Backup and it should work (;

Removing and reinstalling also works (;

Circle Mod kitchen will be back on wednesday^^

I've tried to add them to the framework.. but failed.. :rolleyes:

Either got a working batterymod and some strange kind of bootloops or working framework + invisible battery :D
[Desire Android Development] Enhdojo:
Thanks... A lot!
[Desire Android Development] Latty:
Oddly enough, your DeFroST 4.2 framework version black bar seems to work perfectly fine for me still, on 4.7...:)
[Desire Android Development] bisko:
There is just one weird thing that I can't sort out since 4.6 camera patch - how to take photos with the OJ ? When I press it it just focuses and does nothing more, so I have to use the on-screen shutter button.

Is this intentional or is a setting somewhere I can't find? :)
[Desire Android Development] gpga:
Gmail issue

I don't know if it is related to Defrost or not, but from some days I have issue with the Gmail synchronisation as the changes done on the Desire are no more sunchronized on my google accounts.

Also I'm not able to include the new Gmail release, not able to install it after download.

Is there other people that face this issue.

I use Defrost 4.6, and the issue seems to have appear from 4.2.

Regards

Gilles
[Desire Android Development] milkynex:
so... tell me forum, why is this so? i have my ext partition formatted with ext4 and it mounts as ext2 on /system/sd?

/dev/block/mmcblk0p2 /system/sd ext2 rw,noatime,nodiratime,barrier=1,data=writeback 0 0
[Desire Android Development] BrainMcFly:
it also does not help. Still FC with Titanium Backup under 4.7 (Clearing Data of TB and deinstall and reinstall also does not work)
[Desire Android Development] danarama:
4.5, finding WiFi s bigger drain than other Rom / kernel combinations. Anyone else find this? How's WiFi drain on 4.7?
[Desire Android Development] claspath:
Is havs 1113 kernel for DF 4.5 available for 4.7 rom? Defrost setup just shows kernel mods for 4.5, not for 4.7
[Desire Android Development] m0nji:
for me, the havs 1113mhz was very unstable under 4.6 and 4.7. i hope there will come another 998havs kernel.
[Desire Android Development] Marsbar:
No change in kernels for 4.6 and 4.7, so you can just use the 4.5 one.
[Desire Android Development] MorbidBrain:
Waiting for FRG83 :D
[Desire Android Development] coxtor:
Has anyone ever tryed to scan barcodes ? I cannot scan any at all, no 2d or 3d codes.

Anybody else with issues ?
[Desire Android Development] cgorki:
Any ideas, anyone?
[Desire Android Development] mitchmao:
@cgorki

just flash the wifi-N kernel module from DeFrost Setup (in your app drawer).

EDIT: actually, DF 4.7 seems to have no wifi-N module available. try the 4.5 one.

@Richard, is this compatible with 4.7? I didn't test as I have no wifiN router =)
[Desire Android Development] Bart1981:
This is properbly a stupid question and maybe it has been asked a couple of times allready (if it's a really stupid question it has not allready been asked) but where can I find the Defrost Setup???
[Desire Android Development] Enhdojo:
It's with your apps.

There is a N module in the 4.7 setup.
[Desire Android Development] cgorki:
I flashed the module, still my N network is not appearing in the regular setup for wifi. Is there an extra menu or something for scanning for N networks!?
[Desire Android Development] photek1000:
Flashed 4.7 this morning from 4.5a and no issues with bar codes.
[Desire Android Development] Bart1981:
Well I cannot seem to find it in my apps..

Strange
[Desire Android Development] WhiteChristmas:
I've updated to 4.7 and don't have any problems. All the issues I had with 4.5 (BSOD) seem to been sorted out - excellent work Richard, Kal and the CM team.

Also, got quiet time working fine.
[Desire Android Development] richardtrip:
For a fully working market (paid apps) use this update:

DeFroST_0.7_marketupdate
[Desire Android Development] Simo'z:
"DeFroST_0.7_marketupdate" includes app2sd? Requires wipe?

Sorry for my bad english xD

Thanks..
[Desire Android Development] masi0:
Richard - I understand we can still use Marketenable instead?
[Desire Android Development] masi0:
Lads - are you able to send/receive MMS and transfer files over BT to the PC?
[Desire Android Development] vivmar:
About this:

what's mean that "99.9% of current apps it won't be possible to move"?

If i install a new appz can i move from internal memory to sd?
[Desire Android Development] @ngel:
Look for a yellow triangle item into Windows Device Manager and reinstall its driver heading to "C:\Program Files\HTC\HTC Driver".
[Desire Android Development] infexis:
Stock: you can move only the apps that support this

Internal: Everything goes into phone, cant move

Apps2sd: Everything goes to Sd, but you are able to move
[Desire Android Development] stewcp:
Thanks Richard... works a treat, appreciated ;)
[Desire Android Development] infexis:
Richie, you da man!

Btw, in the future please preffere to upload your files to mirrors instead of rapidshare.. more secure if one of the links breaks, an other still works.
[Desire Android Development] GhostR1der:
Nice ROM.:D
[Desire Android Development] Jabbypants:
I install these 2.2 roms but am yet to see what exactly they give over the 2.1's there is certainly no performance increase.
[Desire Android Development] kewell79:
marketenabler looks like its working, so why use this?
[Desire Android Development] @ngel:
Can you please mirror the market update? Rapidshare is not working for me. :)
[Desire Android Development] Simo'z:
Please, I'm deciding to flash this ROM on my Desire.
[Desire Android Development] Egan:
Anyone notice that auto-rotating isnt working anymore?
[Desire Android Development] e-mperor:
it's hard for me to find my way as I'm new here.

Can anyone advise me how to install this firmware? Any tutorials?

If I can understand well, I need to install a recovery first?

I've tried this: [Recovery] AM Desire Recovery v1.1 [29th May] via PC (can be removed later) (showthread.php?t=689778)

I installed HTC Sync. I enable debug on USB. I run the Recovery using Power and Vol button down. If I can understand well, I need to extract the package to my pc. Then connect using: recovery-windows.bat

I get the following error.

C:\Users\admin\Desktop\recovery>adb-nilezon push files /

error: device not found

C:\Users\admin\Desktop\recovery>adb-nilezon shell busybox --install /sbin

error: device not found

C:\Users\admin\Desktop\recovery>adb-nilezon shell recovery

error: device not found

C:\Users\admin\Desktop\recovery>pause

Press any key to continue . . .

What do I do wrong?? :( :(

any advice?
[Desire Android Development] l1nuxfre4k:
bluetooth file transfer not working?
[Desire Android Development] kewell79:
no problem with me
[Desire Android Development] @ngel:
I haven't downloaded that update yet, but I don't think it's a whole ROM. Just an update to flash over.
[Desire Android Development] @ngel:
Are you using Windows 64 bit? If yes, that could be the problem.

However, try to issue some 'adb-nilezon devices' commands before launching the batch file, see if a device is listed in the output.

If not, try to disconnect and reconnect the Desire to a different USB port.
[Desire Android Development] danarama:
You haven't been removing anything from System/app before flashing the rom have you?
[Desire Android Development] mrsimes:
Yes, turning wifi off when I'm not in a wifi area prevents this behaviour for me.

I've got a widget to toggle wifi on and off quickly.
[Desire Android Development] onyxogen:
Great... I think the so called wake-up bug in CM6 relates to WiFi too so this seems quite plausible to me. Since then I automatically disable Wifi when I'm not at home with "Tasker". Thanks!