yashsingh1/xdaforums huggingface dataset:
[Desire Android Development] cbanbury:
Using the uv kernel & MCR R3 now. Had battery huge battery drain problems with the BFS ov-uv kernel with mcr r2 (battery still recovering), anyone else have this similar problems or better luck with jus the uv kernel?
[Desire Android Development] bambobambo:
no problem battery e brightness with MCRnoBFS_uv-signed,but no overclock,only undervolt.

bye
[Desire Android Development] Dave Hagenaars:
So i was wondering, as a lot of people are using this now. How are the results? Better battery life? Even faster device? Or are the improvements minor?
[Desire Android Development] ivicask:
Battery life is better with any version than from stock. Perfomance is a bit better with OC version and you can feel it. But undervolted version withot overclock should give you max battery duration of them all.
[Desire Android Development] radiosilence:
Can confirm that the display looks uncontrasted at high brightness, and pink at low brightness. Using MCR oc uv.

Nand restoring :(
[Desire Android Development] :
The desire does not seem to like big drops in min cpu... i tried 1113 - 245 and i hung here and there, the best results i seem to have got from 1113 - 768 while on normal useage and sleep 3** - 245 for sleep;))

Now lets see if i save juice while having a super cpu;)

JD;)
[Desire Android Development] ieftm:
How about a OC only version (no UV) to see if that clears the contrast bug?

As stated by someone else, that might cause the contrast bug, because it's not getting enough juice on a too high clockspeed.

Currently trying to replicate the kernel build on my dev machine, so expect some support richard ;)
[Desire Android Development] stingerpl:
Can't you at least read the last pages before making suggestions?

http://xdaforums.com/showpost.php?p=6507574&postcount=93
[Desire Android Development] freddy87:
hi,

just 1 question

need no overclocking, just undvervolt - my rom -> modaco r3

what kernel should i install (with no display bugs contrast etc..)

thank you

:)

best regards from vienna
[Desire Android Development] Pyr0x64:
MCRnoBFS_uv-signed.zip
[Desire Android Development] freddy87:
thank you - installed - booted correctly and no display bugs!

and now the battery life should get better?
[Desire Android Development] asci:
MCRnoBFS_uv-signed?
[Desire Android Development] freddy87:
yes, installed this kernel!
[Desire Android Development] richardtrip:
Update:

Dropped the auto-detection. For undervolt+overclock use the new V4 version and use setcpu.txt from first post (put it in the root of your sdcard).

In setcpu select "Custom Frequencies". Please test. Can't find any contrast bug now, but it could be my eyes :-)
[Desire Android Development] Pyr0x64:
Thanks Richard

just flashed the new v4, overclock seems to be working and i don't have the contrast bug anymore :)
[Desire Android Development] DocRambone:
New oc version look good: tested on Desire with CM506 rom. Linpack and superpi shows that the oc kicks in.

BIG thanks :)

OOOPS: update, LOADS of errors in osmonitor: acpuclock: unable to drop ACPU VDD
[Desire Android Development] Pyr0x64:
looking at the readings in setcpu, the cpu is not dropping to 128MHz, only 245 *shrug*

[edit]

does that mean the uv isn't working?
[Desire Android Development] fstluxe:
Nice Nice Nice Work Richard!

I really Love your Active work !..:)

Groetjes,
[Desire Android Development] DocRambone:
Maybe, check with osmonitor if you have same errors. I may be my CM506 rom that is not compatible
[Desire Android Development] teitiel:
can confirm this, running MCR r3 i get the same fault messages
[Desire Android Development] fstluxe:
Richard :

is t possible to ad 1 more line the 1.17GHZ? just for fun/ testing(i just curious to wat the desire can handle.. or do i need to compile my own kernel for this testing ?

bye.
[Desire Android Development] coolbho3000:
The undervolt is too much for your phone. :confused:

Did the autodetection patch not work? This should make setcpu display an "autodetect frequencies" button. http://android.git.kernel.org/?p=kernel/msm.git;a=commit;h=163a6fc98e1796c0edf1e11041fe1b6ae06f2154
[Desire Android Development] :
V4 Running fine on MCR r2, since the setcpu txt fix, no lag at all, and contrast fixed;)

JD;)))
[Desire Android Development] stingerpl:
This will answer your question: http://xdaforums.com/showthread.php?t=620081

First post is by the author of the patch Richard uses.
[Desire Android Development] Pyr0x64:
just installed osmonitor, yes i'm getting lots of error messages too

[edit] quick system info also shows them in the dmesg logs
[Desire Android Development] DocRambone:
Auto-detection is ok, setcpu ok, but i get many errors in os monitor. I guess the voltage need a bump.

I had the same when oc my nexus... Voltage then to low to.
[Desire Android Development] coolbho3000:
I just found that this is using many remnants of the code aurora base, so it needs further modification to get OC to work. If you haven't already, change

switch (tcsr_spare2 & 0xF0) {
case 0x70:
max_acpu_khz = 768000;
break;
case 0x30:
case 0x00:
max_acpu_khz = 998400;
break;
case 0x10:
max_acpu_khz = 1267200;
break;
default:
pr_warning("Invalid efuse data (%x) on Max ACPU freq!\n",
tcsr_spare2);
goto skip_efuse_fixup;
}

To simply

max_acpu_khz = 1267200;

Try that. :D
[Desire Android Development] stingerpl:
I'm still using the old UV-only kernel and I have the 'Unable to increase ACPU VDD' errors flooding my OS Monitor screen :(

Guess that means UV is not working?

Edit: or it IS working? :D
[Desire Android Development] ivicask:
tryed MCRnoBFS_uvoc_V4-signed.zip with setcpu.txt on SD card.

It doesnt wana drop to 128, stays 245 MHZ
[Desire Android Development] atconc:
no error messages here but set cpu does seem to work - whatever i set is ignored and min is 245 - max is now showing 1113 mhz though. Going to keep running with it to see if the UV helps the battery life

*edit installed os monitor and have the same errors, think i'll nandroid restore for now - and keep trying the new releases
[Desire Android Development] DocRambone:
128 is not supported by the cpu
[Desire Android Development] :
yeah uv is definatly not working,

245 is min, but seems more responsive;)

JD;)
[Desire Android Development] stingerpl:
It's really great that coolbho3000 is helping us with that!

Thanks!:)
[Desire Android Development] ivicask:
What do you mean not supported? It did work with that contrast bug build, it was chilling at 128 MHZ, its just not working in this new builds.
[Desire Android Development] coolbho3000:
I would not recommend 128MHz anyway, it's on a totally different PLL and is not used by either google or codeaurora.
[Desire Android Development] ieftm:
Can't you tone it down a bit? Just trying to be helpful.

It sure as hell doesn't help to sound arrogant.

Anyhow: Seems like the problem was found, as the total CPU scaling range was too large for it to handle, in this case, the minimum freq.
[Desire Android Development] richardtrip:
Re: Kernels + ext4 + tun + cifs (1113 MHz oc-uv WORKING NOW)

Already changed that part. Will make some more changes tomorrow evening. Thanks

-------------------------------------

Sent via the XDA Tapatalk App
[Desire Android Development] richardtrip:
Re: Kernels + ext4 + tun + cifs (1113 MHz oc-uv WORKING NOW)

Thats what i thought.
[Desire Android Development] richardtrip:
Re: Kernels + ext4 + tun + cifs (1113 MHz oc-uv WORKING NOW)

245 is minimum.
[Desire Android Development] richardtrip:
Re: Kernels + ext4 + tun + cifs (1113 MHz oc-uv WORKING NOW)

Make the voltage changes tomorrow evening. Please give me some time :-)
[Desire Android Development] StrongOneX:
does wifi tether work on this kernel?
[Desire Android Development] richardtrip:
Re: Kernels + ext4 + tun + cifs (1113 MHz oc-uv WORKING NOW)

Yes it does.
[Desire Android Development] DocRambone:
Sure, no hurry ;)

Thanks for your work :)
[Desire Android Development] asci:
I'm using uv version and I also have installed set cpu, just to downclock in sleep mode. I noticed that device hangs the most when I resume it from sleep and sometimes in normal use too. In this last case, I noticed that cpu stays at 245 mhz, like if on demand cpu settings doesn't work properly. Did someone note this?
[Desire Android Development] stingerpl:
I'm setting the governor to 'performance' when screen is on and to 'ondemand' with max freq of 384MHz when phone sleeps. Works flawlessly.

Also, if you have the SetCPU widget try deleting it and check- it made my htc launcher take up to 30% of CPU :(
[Desire Android Development] fstluxe:
Dear richard,

Is it possible to add one extra line : 1.17Ghz? I really like to test this out just to see what the desire can handle (its to stable :p haha so it may can some higher.. , or do I need to compile my own kernel for this testing stuff ?

groetjes,
[Desire Android Development] coolbho3000:
Active or passive widget? Active drains a lot, it has to update like 5 textviews every 5 seconds :(

I can't really see how the autodetect patch can introduce bugs. It's pretty non-intrusive, exporting one thing to sysfs :confused:
[Desire Android Development] :
For the love of god do not use active set cpu widget, it will cripple your OS, thanks stinger for the heads up mate!! I was wondering what was the constant hanging and quick battery drain.

JD
[Desire Android Development] coolbho3000:
I should put a warning on the next setcpu version right after the user adds it.

Or remove the active widget completely. That's probably the best idea. A longer interval renders it pretty much useless.

Anyway, good work richardtrip!
[Desire Android Development] :
Yes mate, the active widget is detrimental to what your trying to achieve, but really great work guys, its fantastic what you have done in such little time;)
[Desire Android Development] stingerpl:
I was talking about the active one.

I would opt for removing it. It defeats its purpose IMHO :)
[Desire Android Development] hotweiss:
Can you upload your config? Thanks.

PS-I don't have a Desire to pull it
[Desire Android Development] freddy87:
can anyone confirm this scenario:

-) loading battery full at night

-) in the morning led -> green

-) plug out charger -> akku only 90%

-) it seems battery is charging full and then it takes battery and not from the charger

i hope all of you understand what i'm meaning ;)

BR
[Desire Android Development] MarvinFS:
Confirmed the same issue with battery not fully charging - just reconnect cable to continue charge as a quick dirty fix . this issue is discussed at modaco
[Desire Android Development] freddy87:
can u please link it 4 me? - this issue exists also with stock rom - am i right?
[Desire Android Development] stingerpl:
Re: Kernels + ext4 + tun + cifs (1113 MHz oc-uv WORKING NOW)

+1 on this. Kernel:uv (no oc)
[Desire Android Development] stingerpl:
Screen from Juiceplotter

As you can see I plugged it out around 8:07 (green line in the bottom indicates plugged charger).
[Desire Android Development] richardtrip:
No problem.
[Desire Android Development] richardtrip:
Check the first post for an OC only version (no bugs i hope :-).
[Desire Android Development] DocRambone:
Thanks, the non uv solved the errors issues, so far so good.

Confirmed functional on CM506 port for Desire.

Great work :)

Now time for additional req: how about sound level hack?
[Desire Android Development] DocRambone:
The behaviour is normal(?), charger should charge to 100% and start again when under 90% to not wear out the battery to soon.
[Desire Android Development] trion:
I find it strange, now i often take my phone of the charger with only 95% charge.

Normaly when charged it stays at 100%, as with all my previous phones and never had a bad effect on my battery. This has a bad effect because i start with my phone not fully charged :(
[Desire Android Development] Pyr0x64:
sucessfully flashed MCRnoBFS_OC_V1-signed.zip on an mcr r3 rom :)

thanks richard

the discharging battery 'issue' people are talking about is nothing new and has been discussed in other threads and on other forums previously.

it also affects stock unrooted phones, and so has absolutely nothing to do with richards kernels
[Desire Android Development] :
Doc, what rom for 5.06 are you using?

And are you geting better functionallity using this kernel with 5.06?

JD;)
[Desire Android Development] stingerpl:
Saw it for the first time on my JuicePlotter, I'm charging my Desire overnight daily. So I guess it was not happening on stock kernel.

Anyway.. we now have a working OC and semi-working OC-UV and UV-only?
[Desire Android Development] Pyr0x64:
yes it was

do a search and you will see others with the same problem

i had the battery discharge 'issue' even before i rooted my phone

it's not even a problem imho, it's a safeguard against the battery being overcharged

and no, it seems the UV is not working yet
[Hero CDMA General] Hero's Hero:
ADB was working for awhile then quit.

Can someone please help me?

In command prompt it says "ADB is not an internal or external command, operable program or batch file"
[Hero CDMA General] laufine:
Do you install the Sync software?
[Hero CDMA General] Hero's Hero:
Yes, I've tried it with and without.

I recently deleted the Sync, should I reinstall it?
[Hero CDMA General] laufine:
I'll post the drivers. Here is the link.

http://www.megaupload.com/?d=PU08Q26S

You can try manual install the drivers.
[Hero CDMA General] smw6180:
You have to either put it in your path, or cd to the directory where adb is contained.

Example:

cd \android-sdk-windows\tools

Then run your adb commands. That error message you're getting is because the OS doesn't know the adb executable exists.
[Hero CDMA General] Papa Smurf151:
i was just about to type this up then saw this as the last post. Good work man
[Hero CDMA General] Hero's Hero:
I have all the drivers
[Hero CDMA General] Hero's Hero:
I have them in the path, but no beauno
[Hero CDMA General] DevinXtreme:
Where is your SDK installed to?
[Hero CDMA General] Hero's Hero:
It's in C:/
[Hero CDMA General] DevinXtreme:
And you've tried running this before any adb commands, right?

cd C:\android-sdk-windows*\tools

*Or whatever you named that folder
[Hero CDMA General] thatdudepoops:
I've Had this issue. I Had to un-install the sync And sdk. Then install them right back on lol.Reloaded the vista drivers then Im back Tim. That is if its a Driver issue

-------------------------------------

Sent via the XDA Tapatalk App
[Hero CDMA General] regaw_leinad:
Do you still need help with this? I can help you out
[Hero CDMA General] Hero's Hero:
Yes I do.

Would really appreciate it.
[Hero CDMA General] Nicksil:
It seems you're on your way to receiving help. However, if you're still in limbo, locate your android folder or adb executable, right click, copy the location, and paste it into a follow-up reply. This is with respect to the diagnosis process.

Either way, I hope you're headed in the right direction to solve your slight dilemma. :)
[Touch HD Themes and Apps] hackertom:
I have lost the text page on my full qwerty keyboard English,

Can this be fixed?
[Touch HD Themes and Apps] stephan1:
maybe hard-reset, or install a new keyboard
[Touch HD Themes and Apps] hackertom:
Thanks

i tried re-setting my device - no luck, also tried using the other input methods - still no luck.

Any other ideas?

any link to download the original English keyboard...??
[Touch HD Themes and Apps] stephan1:
hmm....

I found no link to the original english keyboard

What makes me stunning is that the other input methods also don´t work...

download this keyboard:

http://www.jayceooi.com/2010/02/21/download-swype-v3-9-for-htc-hd2/

Try if it works... if not, you will have to reset windows mobile totally. This option can be found in the settings and it´s called something simmilar to reset/erase storage (i have a german version) there you have to enter 1234 and then you can reset the device

Cheers, stephan1
[Touch HD Themes and Apps] hackertom:
sorry but i will restore the original English keyboard...

if touch "up" keyboard button i see only my Greek language and not English and Greek...help!!!
[HD2 General] TheGreenManalishi:
Hi All, first post so please go easy on me........

I have a Leo coming in the next 2-3 days and wondered if anyone could offer an opinion on the quality of its audio playback (Mp3 and the like).

I have Sennheiser HD650 phones in my home, Benchmark DAC etc so i'd like to consider myself an audiophile of sorts - so please bear that in mind when answering.

Ive yet to read anything that is particularly enlightening about that aspect of the Leo, so something in depth would be great (Soundstage, Clarity etc etc)

Thanks, in advance, Shaun from the Uk.
[HD2 General] friend'scatdied:
No worries here, my friend. I have a pair of JH13 Pro and a pair of JH16 Pro custom IEMs as well as a Peachtree Audio Nova for home usage and the HD2 doesn't disappoint for on-the-go. It doesn't sound quite as good as the iPhone 3GS did but it does sound better than my old Milestone and Nokia phones (N95, N85, N97). I find Audio Booster very necessary since the HD2 tends to recess off the lower bass (sub-100hz) noticeably, so I just add a couple of dB to the bottom end.

Playback suffers from very slight hiss, but it's not a big deal. I don't think there's a portable player alive that doesn't hiss with the JH Audio earphones.

Relative to my phones other than the 3G and 3GS the Leo offers better 3D imaging and soundstage depth, with surprisingly holographic specificity. Detail resolution is actually very good, mostly comparable to the 3GS. The frequency response seems to be a little off-kilter as I mentioned the recessed lower bass. The treble is very polite and non-fatiguing (as opposed to grainy and etched on the Nokia phones) but I also suspect there may be a little recession going on up at the very top end as well; this doesn't bother me so much.

It is not quite up to the level of an excellent standalone MP3 player, but it is more than good enough to not make you think or worry about the differences.
[HD2 General] TheGreenManalishi:
Just the kind of information i was after, many many thanks.
[Desire General] muhid:
Hi, thanks to the guides here and its founder i have managed to root my desire successfully. I just wanted to know what it actually means when SWAP = 0 and ext2 to ext3. What do these mean? Also when we do ext2 512 i take it we are reserving 512mb for app installation and the rest is FAT32. Does that mean things like maps for copilot and photos will go in non reserved part of sd card?

Thanks for help. I just want to understand this more and apologise if this has been answered already.
[Desire General] The Professor:
Swap is a section of a disk that the file system uses when it's out of memory - it "pages" things out to swap as a way to free up memory, but still be able to retrieve the old data from swap when it's next called for.

ext2 and ext3 are different file systems. ext3 is an upgrade of ext2 that supports journaling - in other words, if you're in the middle of a write to the disk and something fails (yank the SD card, power dies, whatever), there's a better chance the file system can fix what went wrong afterwards.

Your ideas about where things go are correct. I'm not sure where maps are stored (if they normally store to SD card, they'll continue to do so), but photos, music, etc all live on the regular SD card in FAT32, not in the ext partition you created.
[Desire General] reddi:
The reasion why the sd card is divided in that way is because "apps2sd" is a kind of hack for the device. Android is currently not designed to save apps to the sdcard so removing the card would be fatal for the operating system which would miss its app data.

Now for using apps2sd, you've created a new partition (the reason why ext is because its only used by linux/android and very robust. no need to choose a differens fs here) which the system can always access and read/write.

Now we have another FAT partition, but this one is used in multiple scenarios - normally it's used by the phone to store data, but you can also use it with USB as a harddrive. While doing this, android cannot access this partition because its used by the host system exclusively. Thats why we cannot store our apps on that FAT partition and needed a completly new one. That's very clever actually.

Your maps are stored in tha FAT partition by the way - normal android users doesnt have plenty of space free, so they need to save their maps on the sd. The copilot/navigon/whatever developers know that and read them from there.
[Desire General] muhid:
Thanks for the replies. I am understanding a bit now. I cannot understand why an advanced device did not automatically allow it to save to SD card?

@reddi - just for clarification, are you saying that when a normal user installs an app - the SD card is disabled (because the host system is using the SD card??) and thus preventing the app from being stored on SD? If what i am suggesting is correct i dont understand how the SD card is being used when installing app?
[Touch Diamond, MDA Compact IV General] anilthakurta:
Hello,

In my previous rom, the msn avatars of pmy contacts where used by my phone in my contactlist. How can i apply that at my new rom?
[Touch Diamond, MDA Compact IV General] anilthakurta:
anyone?????
[G1 Q&A, Help & Troubleshooting] Blackman778g:
My G1 and went through many experiences.... but now this one is crazy.... My G1's screen goes blank and blurry/fuzzy to a black backlight screen whenever I touch the chin or bottom of the phone. Then to turn it back on I have to turn off the screen and turn back on or a battery pull.... Anyone experience this before? It does it especially when hot if that helps...

I'd hate to replace it... 'I remember that "Welcome To T-Mobile G1" screen from day 1 as it was yesterday

Sent from my Htcclay's SuperBad G1 using the XDA mobile application powered by Tapatalk
[G1 Q&A, Help & Troubleshooting] protomanez:
This is most likely a digitizer problem or a cable is loose. Definetly hardware. If you don't want to go to the hassle of replacing it yourself then by all means get another phone as it is a loss cause without a replacement.
[G1 Q&A, Help & Troubleshooting] b0ricuaguerrero:
happened to me. i would touch the keyboard and the phone went blank on me. like it faded black quickly and i had to put it to sleep and wake it up. that was my first replacement. i think im on replacement number 6
[G1 Q&A, Help & Troubleshooting] Blackman778g:
Do you think opening it up would be much hassle?

Sent from my Htcclay's SuperBad G1 using the XDA mobile application powered by Tapatalk
[G1 Q&A, Help & Troubleshooting] Blackman778g:
Yeap That's It! Man replacement number 6! I'm only on number 4. But I hope I can get a replacement... I just stopped paying the plan due to a data plan roaming charge..

Sent from my Htcclay's SuperBad G1 using the XDA mobile application powered by Tapatalk
[Upgrading, Modifying and Unlocking] osk70:
hi please can any one help me and tell me how can i flash my x1 phone it reached 0% and stopped there and then gave me error 262.

thanks in advanced.
[Desire General] jfran:
Hi

I am not able to get the device to go into sleep mode (blank display) by touching the power button unless its at the lock screen. Depressing the power button does nothing, other than to activate the quick menu unless pressed for a few seconds. The only time I am able to get the device to sleep via the power button is when the screen has timed out (based on settings) and before the screen in unlocked, otherwise I just have to wait for the screen to timeout.

I cant seem to find anything that would prevent the device going to sleep via the power off button, any suggestions?
[Desire General] thebarsteward:
Does this happen all the time or only while the phone is charging, as there is a setting that keeps the screen awake while the phone is charging:

Settings>Applications>Development
[Desire General] jfran:
happens all the time, and I am aware of the stay awake feature during charging :)
[Desire General] Whiterin:
If you're using a custom rom it may have something to do with that. Maybe the key isn't mapped or set correctly. Other then that, that's a pretty odd issues.