yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] heineken78:
Really unbelievable, dude!

I have done so many bad things with this phone: experimenting with drivers, flashing and nothing happend during more one and half year.

I had in my hands Glofish x700 that was bricked on 2nd day, fortunately had jtag guys closeby ;)

I think during production of i780 was diversion from htc that they put malitious code and many of "Mirage" (i780 factorys name) became timebombed and spreaded around the world.

Actually i780 was first Samsung sized 320x320 with ts and keyboard , so I can imagine its more experimental and same time EXPENSIVE looking model in old samsung style "business. made in korea. battery made in japan", thats upgrading was broken up by world crysis company project...

Omnia I and Epix, young american i780 brother, came later and more developed than i780. But whats wrong with epix? It has new keyboard shortcuts but doenst has samsung task manager :) poor at&t capped, if want - was a nice phone!

Just seen many Omnia 1+ till upcoming Omnia 4 they are not standing close by impressions(toy looking, cheaper materials, samsung/msm processors- economy class with "Pro" preffics?). Sure bigger amoled screen is part of deal!

Dude Im not about your choise. b7610 is really nice phone. But question how do you answer palringo when driving? Its so hard to slide and write on it with one hand :)

I love this small smart more than phone speedy undead handy and keeping waiting for wm7 phone:cool:
[HD2 Android Q&A, Help & Troubleshooting and Genera] jasmo1984:
Does anyone have the file for the keyboard used in the froyo version
[HD2 Android Q&A, Help & Troubleshooting and Genera] palosjr:
it wont work on eclair builds, or desire builds. It is tied into the framework.

but, FWIW.... i attached the file

which brings up a good point... most of the items from the Desire builds, (and froyo builds) which are part of the Sense UI (or were added in Froyo) are not compatible on other builds. For instance, you cant just take FriendStream and put it in a froyo non-Sense ROM. Also, you cant take things from a froyo ROM and just throw them into an Eclair build. The API level is different as well as the framework.

There have been strides at getting things like HTC Music and the HTC Calculator ported over to builds, so before you go asking if it is possible. Just search, not mainly in this forum, but on XDA in general.
[Captivate Themes and Apps] Belaflek:
any way to change em without having to pay 99 cents a pop?
[Captivate Themes and Apps] inku:
You can follow this guide (can't post direct links yet)

xdaforums.com/showthread.php?t=735148
[Captivate Themes and Apps] phlunkie:
thank you!:d
[Nexus One Android Development] piaxVirus:
I don't know why no one else has done this yet since it's a problem that affects every nexus one music lover that has a car dock. This file will fix it so that the volume level remains at max when the phone is inserted into the car dock.

I commented out the code that Google added in Froyo that cuts the volume level by -10dB when the headphone output is used at the same time as bluetooth (car dock).

This library was compiled using the Cyanogen 6.0 source, so I can't guarantee that it will work with any of the nightly releases of CM6. I have only tested it with the finial release of CM 6.0.

Requirements:

* Android SDK

* Nexus One

1. Download the libaudiopolicy.so file from http://www.mediafire.com/?nocgpiypp10jcpt and place it in the <path to sdk>/tools/ folder.

2. Open a comand prompt/console and navigate to the <path to sdk>/tools/ folder.

3. Type in the following:

adb push libaudiopolicy.so /sdcard/libaudiopolicy-new.so (copy fixed library to sdcard)

adb shell (login to the shell of your phone)

su (enable super user mode)

mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system (Remount /system to allow writing)

cp /system/lib/libaudiopolicy.so /sdcard/libaudiopolicy-bak.so (backup old library file)

cp /sdcard/libaudiopolicy-new.so /system/lib/libaudiopolicy.so (replace current library with fix one)

chmod 644 /system/lib/libaudiopolicy.so (set the correct permissions on the new file)

exit (exit superuser mode)

exit (exit shell)

4. Restart the phone.

Recovery:

If for some reason your phone doesn't make it past the first animated X graphic, don't worry it's not bricked. You need to restore back to using the old library by doing the following. I'm going by memory on this so I might be a little off on the details.

1. Pull the battery to power off the phone.

2. Boot into recovery. (If I remember right, hold the trackball and press power.)

3. Enter the shell (it's somewhere in the menu)

4. Type in the following:

mount -o rw -t yaffs2 /dev/block/mtdblock3 /system

mount /sdcard

cp /sdcard/libaudiopolicy-bak.so /system/lib/libaudiopolicy.so

chmod 644 /system/lib/libaudiopolicy.so

exit

5 . Reboot the phone.

For those of you wonder what I did, here is a rough description:

1. I grabbed the source for Cyanogenmod 6.0.

2. Commented out lines in hardware/msm7k/libaudio-qsd8k/AudioPolicyManager.cpp.

3. Compiled the module by doing a "make modules libaudiopolicy".

New version compiled from the Nov 23rd source. Should work on CM 6 nightlies from Nov 13th forward.

http://www.mediafire.com/?cfht17py4hvat42
[Nexus One Android Development] JHaste:
is it always going to be at max or can we adjust it?
[Nexus One Android Development] cigar3tte:
Instead of commenting out the lines, would it work if you simply changed "-10dB" to "-0dB"?

Going to look for replies of people trying this. I haven't rooted yet, but if this works, I will.
[Nexus One Android Development] piaxVirus:
I haven't had time to look too far into it, but it looks like the volume gets reset to max and it's reduced under certain conditions. All I did was remove the -10dB cut for the specific condition that happens when playing music from the headphone output in the car dock.

There must be a good reason why Google is overriding the existing media volume level. Changing it so that the volume controls function would probably break bluetooth headset compatibility. I was thinking about adding a drop down list in the car dock settings to allow different volume reductions, but that requires modifying a lot of files which would break compatibility with CM6 and it's spawn. Then I would have to start rolling my own rom. Right now I'm focused on leaving town and going where there is no cel reception. :) I posted this to help those that had switched back to 2.1 just to use the car dock with their car audio.
[Nexus One Android Development] piaxVirus:
The actually value used is 0.316 for -10db. In a previous version of the file they were using a value of 0.400 for -8db. I didn't have time to figure out what scale these values relate to in order to find a 0dB.
[Nexus One Android Development] cigar3tte:
I've actually bought the BluBridge just so I can use the Car Dock with audio. Going back to 2.1 is unacceptable for me. :D

What do you mean by breaking volume control functions? The volume controls on my Car Dock have never worked for me. What situation are they supposed to work?
[Nexus One Android Development] piaxVirus:
Since i only keep my volume at max when playing through the car dock, I never bothered trying to use my car dock volume controls with 2.1. I think using software to change the media volume still worked in 2.1, but that changed with 2.2. I suspect google had planned on having working car dock volume buttons (why else would you add them), but ran into issues keeping things compatible with other car docks, bt car stereos, and bt headsets.
[Nexus One Android Development] ibegary:
Fantastic.

I've loaded on a Stock FRF91 and reboot was successful. When I get off of work at 5PM, i'll be able to test the functionality.
[Nexus One Android Development] cigar3tte:
How did you modify system files w/o root?

I just rooted my phone and flashed CM6RC2 and made it to Home. Going to test after work ends as well.
[Nexus One Android Development] cigar3tte:
Seems to work fine on my way home from work. Thanks man.
[Nexus One Android Development] bpjmcg:
Works fine on the Evo running Fresh Rom 3.3.0.1 as well just btw thanks!
[Nexus One Android Development] boldfilter:
Finally someone fixed this! Glad I'm not the only one who noticed. Maybe now I wont have to pit a piece of paper on the second pin so it wont activate carmode. Is there a flashable version on the roadmap? Hate to redo all that abd everytime I update.
[Nexus One Android Development] kofruge:
Just curious... Anyone know if this has been rolled into the CM6 nightlies already? If not, I wanna go ahead and use this since I use my car dock a lot, but if it's already in the latest CM6 nightlies, I don't wanna potentially overwrite newer code from TeamDouche :p
[Nexus One Android Development] piaxVirus:
What do ya know, the Evo uses the same Qualcomm msm7k chip. This fix could also work for any other phones using that chip.

I just checked and it looks like there were changes committed for AudioPolicyManager.cpp on Aug 5 and 16th, so I will need to look at compiling a new version for those of you on nighties.

github.com/CyanogenMod/android_hardware_msm7k/commits/froyo/libaudio-qsd8k/AudioPolicyManager.cpp

I won't have time to work on this in the next few days, but some time next week I will be able to. At the same time I'll look at getting this added to CM.
[Nexus One Android Development] mic_:
How about 1.0? ;)

The attenuation is 20*log(1/scaling) dB. So e.g. scaling==0.400 gives 20*log(2.5), which is approx 8 dB. scaling==1.0 gives 20*log(1) == 0 db attenuation.

Why they're attenuating the volume in this case, I don't know, since I haven't looked into it in any detail. With A2DP you'll usually want to send it the audio data at 0 dB and let the accessory handle the volume control itself. Though when audio effects enter the picture (equalizers, for example) you're pretty much forced to leave a few dB of headroom for the effects.
[Nexus One Android Development] kofruge:
Awesome! That'd be great, thanks!
[Nexus One Android Development] Saphroxx:
Waiting for this to be implemented into CM6.0
[Nexus One Android Development] ianken:
Yeah. But we'll still have the same busted car home with the retarded 'exit' button and the new media framework... Grrrrrr.
[Nexus One Android Development] liam.lah:
What's wrong with the 'exit'? thats my most use button.
[Nexus One Android Development] kofruge:
New Car Home App

Yeah... I know it doesn't fix all of that but the new car home app is definitely an improvement over the stock one. You can finally add shortcuts to third party apps (and I suppose you could remove the Exit button if you really wanted to :p) as well as set the car home to launch when the phone is connected to any bluetooth device (although I don't think you can tell it to not launch the car home app when inserted into the car dock :\). Check it out if you haven't already. It's supposed to be available in the market, but I wasn't able to find it when I tried Friday (apparently it was improperly signed). If you can't find it there, I put a copy up on MediaFire though.

CarHomeGoogle-2.2.1.apk: http://www.mediafire.com/?31b3q1f5xibbg0j

MD5: 83f6d27105abd4da8bb0721d118fa8fa

Cheers.
[Nexus One Android Development] piaxVirus:
I found the libaudiopolicy.so file I compiled back on Aug 28th using the CM6 source. I didn't bother posting it since work was really insane back then, I found the older version was working with CM6, and I didn't expect there to be any changes between versions.

So anyone looking for a version for CM6 this should work.

http://www.mediafire.com/?nocgpiypp10jcpt

For anyone using a newer nightly release, this may work for you, but if you want a version that is compiled from the latest nightly source, you will have to wait a few days.

I have been testing the new Car Home. For the moment, it has replaces the Car Dock v2 that I was using. I'm still finding it lacking in a few areas, so I still plan on building my own Car/Desk Home/Dock app.
[Nexus One Android Development] Techshark1:
I have NOT been able to get this to work with my EVO running FreshEvo 3.3.0.1. Is this only for bluetooth volume or should it work also with AUX out volume (headphone), which is what I am using?
[Nexus One Android Development] obscure.detour:
I can confirm that as of the last CM6 nightly 204 (4 days ago) the car dock volume is still not working. I just received my card dock today. Everything else seems to work fine, I don't use it for music, although it did work when tested except the volume rockers didn't do anything.
[Nexus One Android Development] korguror:
I have tried both of those files and none have made a change for me. I use my N1 in my car for music all the time on a daily basis. This is horrible what Google did to it. I am more than happy to help test anything else that might be able to fix this problem. Keep up the good work!

N1 CM 6.0
[Nexus One Android Development] clashcity:
I don't understand why this coding hasn't been fixed in most ROMs by now. This is a pretty annoying "feature".
[Nexus One Android Development] boldfilter:
Indeed. 10char
[Nexus One Android Development] piaxVirus:
I have been busy with switching careers, houses, and cities over the last month. When I did have some time 2 weeks ago the nightly source must have been borked since I was running into constant issues and didn't have time to spend on finding out why.

Yesterday I gave it another try and everything compiled without issue.

Here is a newly compiled and tested version of the libaudiopolicy.so file. It used the source from Nov 23rd and spent the day testing it on a nightly cm_passion_full_263 build. The last changes to thelibaudio-qsd8k code happened on Nov 12th, so this library should work on all nightlies since then. I can't say if it will work on the CM6.1 RCs.

I have been reading that a patch for this issue has been submitted for CM and that it will be fixed in the gingerbread release. Here is hoping.
[Nexus One Android Development] korguror:
Thanks man. I'll get it a shot and reply back here to let everyone know my experience with it.
[Nexus One Android Development] piaxVirus:
Forgot to post the link. :)

http://www.mediafire.com/?cfht17py4hvat42
[Nexus One Android Development] korguror:
Yay!!! It works. Just went out and tried it. Thanks so much! Now how can we get Cyanogen to add this to the rom? lol
[Nexus One Android Development] korguror:
Works fine with 6.1 stable. Yay!
[Nexus One Android Development] Fitchman:
Anyone with a knowledge of how patches work for AOSP vs. Cyanogen know if this can get patched in the nightlies or if we can check the 2.3 code for such a patch?

Here is the awful "thread" (ahem, bug report) about it

http://code.google.com/p/android/issues/detail?id=9445

Glad this works on 6.1!
[Nexus One Android Development] ellesshoo:
Is this something that can be flashed from recovery?
[Nexus One Android Development] oelakkad:
did not work for me

for some reason it did not work for me, there is still a significant volume difference (when connected to audio jack) between being car docked and undocked

I'm running 2.2.1 FRG83D

Any help please?
[Nexus One Android Development] oelakkad:
I hate this app. I "rm -f"'d that apk so fast. That app kills music player and almost every app other than navigation when you dock.
[Nexus One Android Development] venelar:
Is this problem found only during music playback? I find that the call volume while docked is nowhere near loud enough. The volume rockers do nothing during a call.

Running CM6.1 stable
[Nexus One Android Development] 1gr8ftoy:
Can anybody make this fix for Myn's Warm twopointtwo? I have been asking for the source file or a fix in that thread and I can't get an answer on there....HELP! PLEASE!!!!
[Nexus One Android Development] piaxVirus:
I have been able to recreate the issue with the audio still being cut by ~25%. It is not as much as originally, but still enough to be noticeable. There must be something new messing with the volume.

The rumor was that this "bug" was going to be fixed in Gingerbread. I think my last repo sync included the new 2.3 CM7 source. We will see if that is really the case.

I have switched to using Car Dock v3 instead of the latest Google Car Home. If you try that one out make sure you enable the speaker phone in it's settings. It took a few awful phone conversations before I figured that out.

I will see about creating an update.zip next time which can be applied much easier.
[Nexus One Android Development] rockdawg:
I just tried this on my EVO running Fresh 3.5.0.1 and it works! Thanks so much!
[Nexus One Android Development] venelar:
finally got brave enough to dive into adb and sort this out, thanks for the wonderful guide!
[Nexus One Android Development] 1gr8ftoy:
Ok so I have been doing a lot of searching and I haven't been able to find the whole /hardware folder downloadable. I have figured out how to edit compile the source so I can make a fix like this, but it has includes in other folders that I cannot seem to find. This fix ended up working for Warm TwoPointTwo, but HTC FM Radio doesn't work with it. I want to get setup so I can play with it until I get the radio working as well. Thanks.
[Nexus One Android Development] D200P13:
what is the purpose of this? the problem/solution. i recently had a problem with my car dock being able to lower the volum but not make it higher. i got an app that allowed me to up the bluetooth volume and that fixed it. unsure if this is related.
[Nexus One Android Development] 1gr8ftoy:
When the phone is in the dock and using the headset jack, it sets a lower max volume than usual. Is that your situation too? If so what was your app you downloaded?
[Nexus One Android Development] D200P13:
oh then no this isnt like my case. i did almost try this on a long trip with people that dont like music even when nobody talks for a while or boring stories. anyway back to topic, i used 2 apps. my default is AudioManager Pro and that handles alot of audio options to higher or lower them except bluetooth so i found A2DP Volume on the market and that worked. the problem i had was i lowered the car dock volume and for some reason it never was able to get louder so i used that app and it was super loud again. worked well. i used it to higher it as much as the app allowed than killed the app so it didnt do some sort of restore and while music was playing i undocked the phone. the music was still playing very loud while i was about to leave the car so i just turned off bluetooth on the phone and everything seems to have worked. so its worth checking out dont know if that will solve something in this case too.

btw to check the sound i used stock music player. for some reason pandora was playing via phones speaker not dock speaker.
[Nexus One Android Development] rickytenzer:
I have an issue that isn't quite like the one described in this thread:

I have a BT stereo in my car but I use the dock as a charger/holder. I also use the "docked" status in conjunction with Tasker to turn off WiFi and turn on BT.

My problem is that the dock seems to set the call volume at something like half and max out the media volume. I have trouble hearing calls, so I want to bump up the call volume but even then, the media volume is WAY to loud. For some reason though, changing the media volume does nothing (I can decrease the BT media volume using a "dial" in PowerAMP). The volume is full blast unless I drop the media volume all the way to 0 in which case it mutes.

Does anyone know a way around this? I want to have the call volume at max and the media volume at half.

Thanks!

EDIT: Apparently the in-call volume being changed does nothing. It's like the dock sets the bluetooth volume in general and it cannot be changed.
[Nexus One Android Development] ninjai117:
Why hasn't google fixed this yet? Whenever I use the above mentioned app, sometimes I go to resume music on my earphones to result in music being blasted into my ears at full volume. But so far it's the best fix that's worked for me...
[Nexus One Android Development] D200P13:
to tweak my audio settings, i must use AudioManager along with A2DP Volume from the market then i can set individual volumes to my preference. this is one of the things android should have stock not making us buy apps to do this.
[Nexus One Android Development] piaxVirus:
I have been running CM7 nightlies (Gingerbread) for a couple of weeks now and as far as I can tell the issue is fixed in gingerbread. I also remember the volume levels not getting set to max when docked. So if your media volume is is below max before docking it will remain at that level once docked. I have only been driving my car once a week, so my ability to test has been limited.
[EVO 4G Q&A, Help & Troubleshooting] twigums:
How do you guys do it? Do the roms support HDMI play? Are there any apps to use to view videos on the phone or to use it to show on a tv? What file type does the file have to be? Ive downloaded a couple of the movies i had on my computer on to it and it said it didnt support the file type. Also right now i am using netarchy toastmod 3.7.4 and damage control 3.2.3 if that changes anything.
[EVO 4G Q&A, Help & Troubleshooting] oOflyeyesOo:
Not supported by any ROM's at the moment, but Cyanogen is working on it to include in one of the final release's.
[EVO 4G Q&A, Help & Troubleshooting] twigums:
Awesome thanks for the info.
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] Ghost_ghost123:
I have recently got into upgrading my ROM into custom ones, browsing the correct forum and I have found many which I like.

But nearly all of them appear to be for the 6.5x version (with the start button on the bottom left) and I have the original with the start button at the top.

Can I use those ROMs? Is there anybody still working on the old 6.5 ROMs?

Cheers

Ghost :)
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] Wil Badger:
Yes you can use these ROMs and yes there are still ROMs out there being made with the older more stable 6.5.

I suggest you start reading some of the sticky threads in the ROM section because there is plenty more you need to know before flashing.
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] Ghost_ghost123:
Sorry, I should have made myself much clearer.

I have already installed one and have read as many stickies and posts as I can handle lol.

I have adjusted the title to suit.

What will happen if I install the ROMs made for the 6.5x?

Cheers
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] Ghost_ghost123:
Oh, and appreciate the reply :)
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] Wil Badger:
Then you'll be running 6.5x.

You can run either, one is just more stable then the other. You do realize that a ROM is the entire OS right? It's not that it's just changing a few things on your current phones OS and that a ROM is built for a particular OS that is already on your phone. You are wiping it clean with a new OS each time you flash.
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] M_T_M:
Start button on top=6.5

Start button on bottom (and little unstable)=6.5.X
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] Ghost_ghost123:
Cheers,

Yeah I am aware this is the case, slightly hazey, but aware....ha. Mostly in part to the knowledge on the forum. That is the main reason I asked the question, as I wanted to find the one that seems to have the options that best suite me and there seemed to be many working on the 6.5x, for which I was not entirely clear.

You gotta love n0obs!

Thanks for the replies.
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] Wil Badger:
It's all good.......don't mean to come off as an ass either so sorry if I did. Hope you find what you need worst case you just flash to another ROM and give it a whirl.

Try giving NRG's ROMs a try he has both styles.
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] Ghost_ghost123:
Not a problem, you didnt. I would understand as it sounded like a completely pointless question until explain (my bad).

Looks perfect for what I am after and will give a base to play with, much appreciated. Will get flashing as soon as I can.

:)