yashsingh1/xdaforums huggingface dataset:
[Huawei Ideos X5 U8800] Tcm9669:
Absolutely love this! Changed mine to this picture.

To all those having problems, this is how it worked for me:

Download Paint.NET

Add the rgb565.dll in the FileTypes folder (which can be found in the root directory of where you installed Paint.NET

Open Paint.NET

Open or design any image you want. Make sure that you resize it to Width: 479 pixels, Height: 798 pixels otherwise you will have an ugly little image with a bunch of ugly lines when you boot up your phone

Save it as rgb565 format (Apparently the file should be around 750kb, if not.. probably the image size is wrong and it won't look nice on the phone)

rename the file to oemlogo.mbn

put that file on your sd card

open root explorer on your phone and copy that file to /data/cust/logo (you will need to create a new folder named logo)

set permissions to OWNER: Read Write, GROUP: Read, OTHERS: Read

open Terminal Emulator and write su and press enter

wait for a bit and then write load_oemlogo

wait for a bit and write exit

press the back softkey on your phone to close Terminal Emulator

press and hold the power button and power off phone (I would not recommend that you use an applet to restart the phone, just do a PROPER shut down.. maybe it will need to save some files or something.. idk, this is how it worked for me)

Press the power button again and your new customized logo SHOULD be there.

I don't know how this will work on custom ROMs, this worked for me on B136 Stock Rom :) Hope it works for you too. Enjoy.
[Huawei Ideos X5 U8800] stockwell:
I might put together a zip template so that you can easily flash the logo from recovery. Shouldn't be hard to do.

I should warn though that changing the splashscreen *could* be dangerous. With my old phone (Samsung i5700) if the splash was over a certain size then it would overwrite a section of the bootloader and brick the phone.

This might not be possible with our phones but it's just something to think about.
[Huawei Ideos X5 U8800] Tcm9669:
If image is the right dimensions, apparently it should not exceed 750kb
[Huawei Ideos X5 U8800] Tommixoft:
well i loaded my girl's photo on splashscreen and i think there is no better one for me :DD
[Huawei Ideos X5 U8800] Tcm9669:
I thought of that.. but.. I'd rather put her as a wallpaper.. see her more often!
[Huawei Ideos X5 U8800] Tommixoft:
On wallpaper can put any jerk, but on slpashscreen only really in love ones :DD
[Huawei Ideos X5 U8800] darkado:
i get this error "could not load needed library 'liboeminfo.so' for 'load_oemlogo' (Library 'liboeminfo.so' not found) CANNOT LINK EXECUTABLE" and i'm on new geno's cm so i can't go back to 2.2 to flash the logo, is there any other way of doing it?
[Huawei Ideos X5 U8800] Msrag:
Hello I have the same problem ( Honor 4x , EMUI4.0 . Marshmellow 6.0 , rooted ) , I enter SU and it is ok but when i enter load_oemlogo it gives me not found , please help
[HD2 Android NAND Development] Hannes_HD2:
For as long as I am using Android on my HD2, I suffer from high mic gain in normale mode (not speakerphone). This is really annoying, so I'd definitely love to see that last glitch to be fixed!
[HD2 Android NAND Development] letama:
Hi there!

Here are the files, I included the kernel patch and the resulting q6audio.c. The patch has other crap in it, the only modification required is in q6audio.c. It was against a very old kernel, I'm not sure you can use it "as-is".

You also have the user space tool source and my script to compile it.

To dump values, you have to flash a working WinMo 6.5 to have winmo values in memory and launch android with Haret .

To use it, compile the kernel with the modification. It will somehow kill your audio as it won't set acdb to be able to dump acdb in memory untouched. The userspace tools expect to find a pure android default.acdb in the directory where it's launched, it will query kernel values, and remap it to a proper htcleo.acdb in /sdcard/acdb_out.acdb.

Good luck!

LeTama
[HD2 Android NAND Development] memin1857:
Thanks for the support LeTama
[HD2 Android NAND Development] codiak:
+1 for this issue.

With or without htcleo file its way too loud.

Would love to have that fixed.
[HD2 Android NAND Development] memin1857:
This issue deserves more attention. Bump.
[HD2 Android NAND Development] shorty1483:
+1

My wife's killing me after every call :D
[HD2 Android NAND Development] memin1857:
Guys, if you have the high mic gain problem that means your rom doesn't include "LeTama's" htcleo.acdb file. (113910 bytes, check the file size, your rom chef might have just copied original default.acdb as htcleo.acdb)

Just download the attachment below and extract it. Copy the htcleo.acdb file you just extracted to /etc/firmware with rootexplorer or similar file manager and reboot.

Your calls will be OK by then and people won't complain. But speakerphone mode will also be low gain from now on. But since most of the time you are calling in normal mode, it is better to have htcleo.acdb in /etc/firmware
[HD2 Android NAND Development] codiak:
What about /system/etc/firmware? I saw this path in other threads about this problem?

I have that file in /etc/firmware and /system/etc/firmware but still mic is too loud.

Edit:

OK, overwrote your file with the existing one. Mic seems better now, thanks!

But for me, its still about 25% to loud :(

I am a bit curios... is this file in somehow involved in bluetooth playback or music output at all?

Trough all the testing I made the last days I am unsure if at least the bluetooth playback is a little bit worse now?

I would be glad if that were not confirmed :)

Thanks soooo much dude yeah.. love it. kool. i love ya =)
[HD2 Android NAND Development] memin1857:
I think /etc/firmware and /system/etc/firmware are the same.

I am not sure about bluetooth or audio playback. acdb may possibly affect it but can you try reverting back to see and give feedback?

We really need to make this thread attract attention.
[HD2 Android NAND Development] codiak:
Its really hard to tell if you have to reboot your phone and have no real comparison.

I would need a second hd2 ;)

But more imported to me is that the mic is still about 25% too loud :(

Is there a way to tweak the file a bit more?

I have no programming knowledge.
[HD2 Android NAND Development] memin1857:
I am really disappointed that no one cares about this problem :(
[HD2 Android NAND Development] marcimix:
ONE CARES? ONE CARES!?

I'm not the developer and my english is badly too. So I keep only my fingers crossed to make this perfect. I can not much do :(
[HD2 Android NAND Development] Rick_1995:
on Android boot, /system partition is mounted and merged with "/" (root) which already contains the initramfs (the ramdisk provided with your kernel).

so just replacing the file in /system/etc/firmware and rebooting should remove and overwrite any clones thereof.
[HD2 Android NAND Development] RJ45:
I'm really hoping for a fix on this as well!
[HD2 Android NAND Development] Ambious:
Not a dev, but out of pure interest - is this the reason that voice commands seem to be so shaky? The wave form when using voice search looks like static half of the time, and it just doesn't hear anything the other half.

This happens on all Gingerbread Sense builds.
[HD2 Android NAND Development] jan-willem3:
Why is this thread pinned it is completely rediclious.

I can make a thread to

[DEV] Fixing camera bugs

[DEV] Fixing PPP data on clk

[DEV] Fixing I2C code

etc...

This are bugs that are annoying for you and you try to track attention of the developers. Let the developers fix whatever they want what they find annoying. They are not here to fix your problem.
[HD2 Android NAND Development] Stroid01:
Thanks for doing this OP good luck!
[HD2 Android NAND Development] gt2009:
WOW, you just prove that you’re not a developer that belongs to XDA. XDA is about helping others and not being selfish. I do hope you will change your attitude.
[HD2 Android NAND Development] memin1857:
It is pinned (stickied) because this is last "major" problem left that happens on every rom. All other problems can be considered minor. Please stay on topic and don't discuss about things unrelated to the problem mentioned in first of this thread. This is not only my problem, every hd2 user has it. This is the best way to get a developers attention, it is the "developers" forum.

I asked noellenchris to make this sticky for some time to see if it will get attention from a developer. I thank him here for that since I believe he shares my belief that this thread is important for the hd2 android project. Sticky making is a decision of a forum moderator.

I edited the opening post to be more detailed and specific btw.
[HD2 Android NAND Development] THANHVO31:
i flash tytung r12b1 and change value to 400 but many callers can not hear me, crazy! Back to r11 and wait final one
[HD2 Android NAND Development] clyder:
I played with levels and I for me 200/600 levels are way too low.

300 is much better but still could go little higher.

400/600 is OK, maybe it sounds just a little distorted but far from bad or unusable. I cant hear no background noise.

I have just set it to 350 and will see later how it feels.
[HD2 Android NAND Development] mdebeljuh:
You can try even higher values up to 1000. The fix was made so the people could set mic level according to their wishes. If you where happy with mic level during call you can set level -1, that means that the mic level will not be changed, and still you can change mic level in speakerphone mode (echo "1 700" > /proc/mic_level). Maybe we will never find unique mic levels which will satisfy everyone.
[HD2 Android NAND Development] tytung:
I compared r11 kernel + htcleo.acdb with r12 beta1.

It seems that background noise of '0 350' is more similar to each other.

P.S. I can hear background noise when using r11 with htcleo.acdb or using r12 with HANDSET mic gain >= 300 (i.e. '0 300') under a quiet environment at night.
[HD2 Android NAND Development] slashas69:
Even with 500/600 peoples hardly hear me, i hear them very well...
[HD2 Android NAND Development] mrchloo:
u can try to use call recorder to judge your settings BTW I set 800
[HD2 Android NAND Development] jolas:
Noticed that problems with other calling party loosing my voice, are starting when in convertation I change (using volume buttons) the incall volume.

I have posted about that, here and here
[HD2 Android NAND Development] dardasatla:
any one experience any Bluetooth problems with tytung r12? i cant connect to my car bluotooth.

when i change back to raf 1.9 i have no problem.
[HD2 Android NAND Development] eseregin:
For Sense builds it is not good idea use Tytung kernels... so raf almost the only solution, thats why you had problems
[HD2 Android NAND Development] odoss:
i did but no answer from him, he disappears :rolleyes::(

raf kernel is the way to go with sence builds...
[HD2 Android NAND Development] memin1857:
Maybe you have an incompatible libaudio. Try the one in post 97 and give feedback please.
[HD2 Android NAND Development] memin1857:
Try the libaudio.so on post 97 and give feedback please.
[HD2 Android NAND Development] jolas:
Thank you, I will try it :)

EDIT: Yes, using libaudio from post #97 made it work!

Thank you!
[HD2 Android NAND Development] windroidHD:
:) here you go... HD2 Mic Control in android market. I will put the code in git for others to tweak, will update this post once done. I put the app in market to make it easy to push updates.

All functionality is self explanatory. If you drag the seekbars mic levels will be changed immediately, if you click "Save Permanently" then mic levels will be saved to a script /etc/init.d/10mic_level. If you don't save then I guess mic levels will be lost on reboot.

If you don't have correct kernel then you will see a error message and will not be able to make any changes.

for future readers of this post: Market will have the latest version. No need to search for latest version. If you don't have market access then get it from http://code.google.com/p/hd2micctrl/downloads/list.
[HD2 Android NAND Development] ayyu3m:
Wow. Nice app. Now it will be easier for ppl to adjust the values. Good going.
[HD2 Android NAND Development] windroidHD:
let me know if the app is able to actually adjusting the mic levels as expected on your devices.
[HD2 Android NAND Development] clio94:
When we set in the app 600 level for speaker it writes in 989miclevel script file 400 and if we set 700 it writes 500. Handset level work ok.also to take the app work properly we must delete 10mic_level if there is in init.d folder or itsnt important to delete this file;

Sent from my HD2
[HD2 Android NAND Development] windroidHD:
I will change it to 10mic file in the next update and also delete 989 file and fix incorrect value. I put the code on code.google.com hd2micctrl, you can search and change the code. Will post the link from pc.

Sent from my HTC HD2
[HD2 Android NAND Development] THANHVO31:
Trying libaudio at post 97(size 60616) replace for 60600, set 450 still low mic, set 500 seems ok. Thanks memin1857 for feedbacks. Suggest to including libaudio with kernel to avoid incompatible.
[HD2 Android NAND Development] InfX:
Any chance the devs in this thread may finally fix the libaudio problems as well, such as hunging the nornal dialer after a viber call, hanging while switching audio from/to bt and/or speaker in voip apps such as fring, bt audio issues etc etc? All seem to be related in one way or another to audio routing switching.
[HD2 Android NAND Development] anand12:
HELP!

Could someone please help me? I am using Rafdroid 4.0.2 with Rafpigna kernel 1.9. I installed the volume fix and the rom got stuck at GO GO GO...

What is going wrong? Where can I find the fix for rafpigna kernel?
[HD2 Android NAND Development] robosapiens:
Here is the rafpigna kernels flash 1.9 or 2.0 http://xdaforums.com/showthread.php?t=940823
[HD2 Android NAND Development] memin1857:
Thank you very very much.

I have a simple suggestion.

Can you make the steps of the slider in 50?

Currently it has steps in 1 which makes adjusting difficult it becomes like 507-508 :)

AFAIK if there are multiple init scripts, the number at the beginning decides which one will go first. So 998 would be OK but yes 10mic_level would be better.

The code works btw.
[HD2 Android NAND Development] tmihai20:
Some people complained about low volume with bluetooth devices. Why don't you incorporate all the possible devices that can set mic gain?
[HD2 Android NAND Development] memin1857:
This is link is for the standart rafpigna kernel which should fix GO GO GO stuck roms with the tytung kernel. But it does not include the mic gain code. (as of 2.0 yet)

If someone modifies rafpigna kernel with the mic level code, rafpigna/sense users would be happy.

Please don't forget to delete/ignore htcleo.acdb
[HD2 Android NAND Development] memin1857:
Here is the info for that:

DEVICE ID:

0=handset (range 200-400)

1=speakerphone (range 400-700)

2=headset (100-1000 for now)

3=tty headset (?) (100-1000 for now)

4=bt (100-1000 for now)

But beware a high mic gain (louder voice) will also result in louder background noise/static.
[HD2 Android NAND Development] InfX:
10x :-)

BTW, windroidHD, can you add the headset and bt sliders to your app as well ?
[HD2 Android NAND Development] anand12:
Yes memin you are so right! This is exactly the reply I was looking for. But then the fix was developed on rafpigna kernel right? Does no one have that file? Which rafpigna users can install? I found only the tytung version even after a lot of searching!
[HD2 Android NAND Development] trex3300:
Tytung wants you to try kernel_r12_beta1 if anyone has the following audio issues, and please report back:

•Low Speakerphone Mic Gain. (It should be already fixed. Please visit this thread for more info.)

•Default (i.e. GSM) phone app FC after using VoIP app, e.g. Viber.

•Audio crashing when using BT voice commands.

•No sound bugs sometimes.
[HD2 Android NAND Development] tmihai20:
This is exactly what I was referring to a few posts up. There should be sliders for bluetooth at least.
[HD2 Android NAND Development] InfX:
Already did, but without changing the initrd (i am on the GBX-v12, a 2.3.3 based ROM, i cannot use the initrd included with in this zip). The audio lib i am currently using is the one recommended a few posts ago.

The mic gain is now, indeed, controllable. I did NOT manage to control the BT mic gain though, the BT mic volume seems to remain equally low (i've tried to echo 4 400 and 4 600 into /proc/mic_level to test).

The default GSM phone app still dies after using Viber the moment it (the GSM phone app) attempts to start the audio.

I did not try BT voice commands, i'll have to restore the APK that does them, i've removed it before (i'll probably just extract it from the ROM build later).

I don't know about the "no sound bug" mentioned, so i don't know what to test here.
[HD2 Android NAND Development] memin1857:
NO.

the fix was developed on tytung kernel but because rafpignas config file was used it stated rafpigna kernel while it was actually tytung kernel.

Rafpigna kernel doesn't have the fix (as of 2.0) yet
[HD2 Android NAND Development] memin1857:
While using tytung r12b1

Be careful about these:

1) The default 200 gain may be too low. Make it 350 (+/-50) by following 1st post instructions.

2) Delete initrd.gz from zip file if flashing on a rom other than tytungs nexushd2

3) Always make a full backup from cwm first.

4) Make sure you have the libaudio from post 97

5) For CLK follow instructions from tytungs post whose link can be found on 1st post.

EDIT: Tytung reuploaded his zip file with 350 default gain.
[HD2 Android NAND Development] alexfocus:
I can not download - "Application not compatible with your device HTC HD2".:confused:
[HD2 Android NAND Development] sprongebob:
please fixed tytung
[HD2 Android NAND Development] windroidHD:
you can try downloading directly from http://code.google.com/p/hd2micctrl/.

I changed filename to 10mic_level now and deleted the old file. speaker volume also should be correct now. market update should push version 1.3 which will have these changes.

Code is on http://code.google.com/p/hd2micctrl/. I will be out today, so either somebody here can add BT, Headset and push changes to googlecode or I will do when I get a chance.
[HD2 Android NAND Development] clyder:
I strugled with that issue yesterday, I was trying to edit build.prop to change the presence of the device to look like Nexus One and DesireHD but I was getting that error again. Today I realized that the issue is not because of what device market sees but because of the nonstandard LCD density, just like the no download button or missing apps issue. If you change LCD density to 240 you will get no more compatibility errors.
[HD2 Android NAND Development] alexfocus:
LCD density exhibited at 240 and it not solve the problem :(
[HD2 Android NAND Development] alexfocus:
Thank you very much;)
[HD2 Android NAND Development] clyder:
Yes you are right...I just checked it myself.....

New market is going to be downgraded today here....
[HD2 Android NAND Development] ayyu3m:
Patiently waiting for the universal fix, compatible with all the kernel versions. ;)

Of coz I m testing still.
[HD2 Android NAND Development] memin1857:
You rock man!

Can you make the slider steps in 50? (like 200-250-300-350-400 / 400-450-500-550-600-650-700)
[HD2 Android NAND Development] sprongebob:
hd2 mic gain

working good
[HD2 Android NAND Development] windroidHD:
does the kernel not support single increments?. didn't understand what you meant few posts back when you said adjusting by 1 increment (507-8) is difficult.

pushed version 1.4 to market. added bluetooth and headset control.
[HD2 Android NAND Development] THANHVO31:
For me, handset limit at 400 not working, 500 seems OK. Could you raise handset limit more say 550.
[HD2 Android NAND Development] eseregin:
Thanks for this app!

50 step will allow eyasier way to install for example level exactly 500 - now it is almost impossible.

Second quest - why the range of mic gain different in all 4 cases? And why its not starting from 0 and go to 1000 fot all?
[HD2 Android NAND Development] windroidHD:
hmm, I am trying to understand whole stepping thing, if kernel can actually set in one step increments and user can find the exact mic gain he wants why do 50 step increments?.

In your case if slider moved to 506 or 494 is there a significant difference in audio quality?.

for your other question read previous posts.
[HD2 Android NAND Development] zagzag99:
The market won't let me download the app, claims I don't have a supported device.

When I look at my market profile it states my device is "HTC HD2", go figure.
[HD2 Android NAND Development] smokin901:
which ROM?

try this market fixer http://www.mediafire.com/?wn07i9k4qxvdtiu

found here

http://forums.miui.us/showthread.php?1144-Apply-not-compatible-after-miui
[HD2 Android NAND Development] memin1857:
You are right, there is no difference in audio quality between 506 or 494. What I'm asking is purely cosmetic. You don't notice a difference in volume until about 50 is changed, so I thought it would look nicer and easier that's all. In my thought, less than 50 adjustment granularity is unnecessary.
[HD2 Android NAND Development] kaiserlein:
For me it worked after setting lcd density to 240
[HD2 Android NAND Development] alexfocus:
What market do you use?

With the new 3.1.3 does not work :(
[HD2 Android NAND Development] mdebeljuh:
I was able to set BT mic level but I had to use higher values 800 to 1000. So you can test with higher values:

echo "4 800" > /proc/mic_level
[HD2 Android NAND Development] InfX:
TBH, higher levels seems to "kinda" work, sounding as a low level mic digitally amplified (as in multiplied) from a really low level. I would expect the BT headset mic to be controlled through the "AT+VGM=" AT command, not through a digital "amplification". BTW, speaking about the BT headset AT commands interface, is there any way to access it, for the sake of testing, for example, via some kind of /dev/something ?
[HD2 Android NAND Development] kaiserlein:
I'm using the new market and it works after setting lcd density to 240 in build.prob
[HD2 Android NAND Development] memin1857:
what is your ro.build.fingerprint in /system/build.prop

I remember it affecting compatibility.

Mine is google/passion/ (which means nexus)

I am using nexushd2 rom by tytung
[HD2 Android NAND Development] mdebeljuh:
Sorry but i don't know how to control BT headset through AT commands.
[HD2 Android NAND Development] kaiserlein:
mine is htc_wwe/leo/leo:2.3.4 and i can dowload the app! I'm on Hyperdroid CM7 rom
[HD2 Android NAND Development] clio94:
hyperdroid has screen density at 167.Change it to 240 and it will let you to download the app
[HD2 Android NAND Development] kaiserlein:
That's exactly what I said :D For me it is working! I don't know which rom alexfocus is using :rolleyes:
[HD2 Android NAND Development] alexfocus:
Hi! Thank you for caring!

Today, everything will work out and I was able to download the application :)

Nothing rules, market 3.1.3, TyphooN 3.6.2

ro.build.description=3.14.405.1 CL96875 release-keys
ro.build.fingerprint=htc_wwe/htc_bravo/bravo:2.3.3/GRI40/96875.1:user/release-keys

LCD does not affect the density and I put 220 :D

I do not know can be corrected by the market or ....:rolleyes:
[HD2 Android NAND Development] themadproducer:
Nice work. Very useful. Thanks for v1.4
[HD2 Android NAND Development] windroidHD:
Version 1.5 beta up. made the slider to increment in 25 steps. increase handset max from 400 to 500. market should push you update soon.