yashsingh1/xdaforums huggingface dataset:
[HTC Vivid, Raider, Velocity] Gene Poole:
I did have to change those, but I also had to add several lines to that file to get a working ROM to compile. Here's what my firmware section looks like

vendor/htc/holiday/proprietary/etc/firmware/a225_pfp.fw:system/etc/firmware/a225_pfp.fw \
vendor/htc/holiday/proprietary/etc/firmware/a225_pm4.fw:system/etc/firmware/a225_pm4.fw \
vendor/htc/holiday/proprietary/etc/firmware/a225p5_pm4.fw:system/etc/firmware/a225p5_pm4.fw \
vendor/htc/holiday/proprietary/etc/firmware/a300_pfp.fw:system/etc/firmware/a300_pfp.fw \
vendor/htc/holiday/proprietary/etc/firmware/a300_pm4.fw:system/etc/firmware/a300_pm4.fw \
vendor/htc/holiday/proprietary/etc/firmware/leia_pfp_470.fw:system/etc/firmware/leia_pfp_470.fw \
vendor/htc/holiday/proprietary/etc/firmware/leia_pm4_470.fw:system/etc/firmware/leia_pm4_470.fw \
vendor/htc/holiday/proprietary/etc/firmware/yamato_pfp.fw:system/etc/firmware/yamato_pfp.fw \
vendor/htc/holiday/proprietary/etc/firmware/yamato_pm4.fw:system/etc/firmware/yamato_pm4.fw \
vendor/htc/holiday/proprietary/etc/firmware/fw_bcm4330_apsta_b2.bin:system/etc/firmware/fw_bcm4330_apsta_b2.bin \
vendor/htc/holiday/proprietary/etc/firmware/fw_bcm4330_p2p_b2.bin:system/etc/firmware/fw_bcm4330_p2p_b2.bin \
vendor/htc/holiday/proprietary/etc/firmware/fw_bcm4330_b1.bin:system/etc/firmware/fw_bcm4330_b1.bin \
vendor/htc/holiday/proprietary/etc/firmware/fw_bcm4330_b2.bin:system/etc/firmware/fw_bcm4330_b2.bin \
vendor/htc/holiday/proprietary/etc/firmware/BCM4330B1.hcd:system/etc/firmware/BCM4330B1.hcd \
vendor/htc/holiday/proprietary/etc/firmware/fw_bcm4330_p2p_b1.bin:system/etc/firmware/fw_bcm4330_p2p_b1.bin \
vendor/htc/holiday/proprietary/etc/firmware/fw_bcm4330_apsta_b1.bin:system/etc/firmware/fw_bcm4330_apsta_b1.bin \
[HTC Vivid, Raider, Velocity] h8rift:
Running setup-makefiles.sh will write the vendor-blobs.Mk. you should run it after initial sync or after a repo sync to be sure.
[HTC Vivid, Raider, Velocity] Gene Poole:
Damn. I took the path of most resistance. Thanks for the heads up.
[HTC Vivid, Raider, Velocity] homeslice976:
So I've been effing with media_profiles.xml all weekend trying to get 1080p playback/recording working, then today, I came across this:

https://github.com/bruce2728/androi...mmit/8bf9619d2f47fd3198b722a0d42e9ba95dbbecbd

I edited ours with the edits suggested, wiped and reflashed. 1080p recording now doesn't force close gallery, but the recording doesn't actually start (sometimes it will say "Please wait", but then nothing). Which was where I was earlier this weekend with just adding a 1080p profile. Maybe there's more to it than that, maybe I'm missing something - but 1080 doesn't force close with this change, just won't start recording. Now the sensation and our media_profiles.xmls appear to have been exactly the same before and after edit, so my guess is we're still missing a piece.

I'll go ahead and start a build now - maybe this needs to be thrown in during compilation, but I doubt it. But maybe it's a step closer? What d'ya think?
[HTC Vivid, Raider, Velocity] mg2195:
I tried using the sense ics vidc_1080 file in the etc/firmware...instead of the included one...got no more force closes but no more recording at all lol...I didn't think it would fix it but thought I might as well try...tomorrow I'll look at the source and see if I can find anything...don't have time today
[HTC Vivid, Raider, Velocity] homeslice976:
i've tried a bunch of vidc_1080s from different places. Most of them seem to be the same, but none of them have improved anything...

Still playing :)
[HTC Vivid, Raider, Velocity] ess.boyer:
Did y'all update the media_profile.XML too?
[HTC Vivid, Raider, Velocity] homeslice976:
I've been editing media_profiles.xml all weekend

Also, using Sense ICS media_profiles.xml made recording not work at all, but no force closes (just like using the vidc_1080 from ics sense). I'm going to try with them both now. just for ****s and giggles :)
[HTC Vivid, Raider, Velocity] snorkle:
when i flashed the latest cm mod, and reboot it its just stuck at cyanogenmod screen =( its been like this for a good 30 min, idk is it just me or did anyone else go through this? or di di **** up.
[HTC Vivid, Raider, Velocity] ZeRo2o9:
You probably need to flash the kernel first

sent from my HTC Vivid
[HTC Vivid, Raider, Velocity] snorkle:
thanks how do i fix it and which kernal do i flash? i got into recovery but and tried reinstalling again but that didnt work either. was i supposed to use a ICS kernal? i basically unlocked bootloader, installed cwm, factory reset and wiped cache in cwm and then flashed.. it was from my internal harddrive does that make a difference or?
[HTC Vivid, Raider, Velocity] pod0087:
You're s-on? If so and you're using TWRP the easiest way is to use HTC Dumlock in the advanced section to be able to flash everything in recovery. Otherwise you have to use fastboot to flash the boot.img file
[HTC Vivid, Raider, Velocity] snorkle:
idk what S-on means lol i have unlocked the booatloader but whats twrp? sorry kinda nooby.
[HTC Vivid, Raider, Velocity] pod0087:
So you're s-on which means you can't flash the boot.img files from recovery and that's why your phone won't boot. Unlocking the bootloader doesn't fix this and the only way is the wire method which is risky and not necessary. You can do everything with S-on.

TWRP is a better recover than CWM (GUI interface, HTC Dumlock which allows flashing of boot.img files). So you can either flash this recovery or do the second method which is using fastboot. See http://xdaforums.com/showthread.php?t=1416836 and the section "(Optional) Flash a custom Kernel/Recovery (Three options, I suggest the THIRD)". Basically you need to get the boot.img file from the cyanogenmod zip file you've downloaded and use the fastboot commands from your PC to flash the boot.img file.
[HTC Vivid, Raider, Velocity] snorkle:
ok thanks so i should flasht his recovery and then do htc dumlock? and is it called goomanager? http://xdaforums.com/showthread.php?p=24686984
[HTC Vivid, Raider, Velocity] pod0087:
Goomanager is just a download manager for the android hosting site. Probably best to download the recovery directly from TWRP homepage http://www.teamw.in/project/twrp2/76. Look up how to use htc dumlock with it before using it though, because you still need to be able to boot into the original rom to get it to work (as ideally you have used dumlock before flashing anything involving boot.img, in your case you'll need to restore an older backup - as you've got CWM you'll have to do this in CWM as the backups aren't compatible with TWRP).

Actually you know what, the more I write about it, it's plain that the best course of action is for you to use fastboot instead. Then after that's working change the recovery. The information is out there and it's pretty straight forward so good luck, probably best to go to Q&A in future instead of derailing the topic.
[HTC Vivid, Raider, Velocity] rignfool:
Or... get flashimagegui from the themes and apps thread...

You can then flash both kernels and recoveries from in android with a nice user interface
[HTC Vivid, Raider, Velocity] snorkle:
i tried the option 3 and when i flashed the hboot zip it says failed =/
[HTC Vivid, Raider, Velocity] altanimi:
Okay, so how can you enable the navbar?

I decompiled framework-res.apk and set the necessary value to "true," but i get a nice bootloop when I push the modified apk.
[HTC Vivid, Raider, Velocity] rignfool:
Use aokp or pacman... they have simple toggles
[HTC Vivid, Raider, Velocity] h8rift:
I'm pretty sure i just got bluetooth going! Need to verify it pairs....and i need to make sure i have my bt headphones laying around to test audio. but bluetooth does now turn on ;). will commit changes and put a new build up after some testing and validation
[HTC Vivid, Raider, Velocity] lucasryan:
Awesomeness my friend....very glad to here that!!
[HTC Vivid, Raider, Velocity] big_yute:
Yeeeeaaaaaah buddy! Ok, ok, I'll wait for final confirmation. :)
[HTC Vivid, Raider, Velocity] snorkle:
my phone is still ****ed, can anyone help me ='(
[HTC Vivid, Raider, Velocity] hovadrive:
Way to go h8rift

---------- Post added at 05:40 AM ---------- Previous post was at 05:32 AM ----------

Whats stage is your phone F***ed right bro ?
[HTC Vivid, Raider, Velocity] XxSHaDoWxSLaYeRxX:
Whats wrong with it

EDIT: nvm just flash kernel (boot.IMG) from ROM zip in fastboot, then flash ROM in recovery
[HTC Vivid, Raider, Velocity] h8rift:
looks like bt audio is shot, need to test other things but it doesn't drop connection, so im assuming other bt peripherals will work fine. Gotta put in another line tomorrow morning and i'll commit and look into BT audio. I think A2DP is just shot atm.
[HTC Vivid, Raider, Velocity] snorkle:
omg yes ok !! i got it to work i was doing the 3rd optional step w00t omg xD you guys are awesome its up and running now yayyy sorry for everything.
[HTC Vivid, Raider, Velocity] sadoway:
Finally an apology for my burnt dinner. And the door that stubbed me toe this morning. I will remember your apology for the rest of my life. When ever something bad happens to me. I will remember "snorkle apologized already" whew. So happy.

I had to. Kept it tame.
[HTC Vivid, Raider, Velocity] meatwad0222:
I'm dying ...that was awesome
[HTC Vivid, Raider, Velocity] mg2195:
I think for cyanogenmod and other aosp based ROMs its actually just a build.prop edit....I'll have to look into it...
[HTC Vivid, Raider, Velocity] lolwutwin:
i downloaded and installed the most recent nightly and i was getting a android keyboard error... Any idea how to fix it?
[HTC Vivid, Raider, Velocity] homeslice976:
Awesome work h8! Look forward to seeing what it took.
[HTC Vivid, Raider, Velocity] Cor-master:
Awesome sounds like H8rft nearly has bt complete which means I'll be flashing very soon :)
[HTC Vivid, Raider, Velocity] Darkthefox:
Nope, but if you report the problem here in detail h8rift or one of the other devs will take a look.

Don't forget to mention if its stock keyboard or a modified one like swiftkey or swype.
[HTC Vivid, Raider, Velocity] h8rift:
K. newest build is up. Link in the OP changed to the newest location where holiday builds will be going to.

bluetooth works, but bluetooth a2dp is shot i think. I need some folks to verify the bluetooth headsets work (not headphones, the earpiece bluetooth headsets for phone calls only). If i can get an answer on that, we should be able to narrow the focus down to fix the remaining issues.

Also, please test usb, bluetooth and wifi tethering. Not sure if bluetooth tethering will actually work now or not yet.

Thanks guys,

-h8
[HTC Vivid, Raider, Velocity] Cor-master:
Ugh that sucks, a2dp is the only thing I use bluetooth for, but it's a step closer... Can't wait.

If I get time later I'll nandroid and flash and do some bluetooth testing for you.
[HTC Vivid, Raider, Velocity] homeslice976:
Downloading now. I'll report back. Way to go man!!

Also - been meaning to ask you, since you've gotten to play with the Vivid for a few weeks, what do you think of the device itself compared to the others you have?

You do an awful lot of complaining for as much progress that's being made :) lol

Edit: USB and Wifi tether/hotspot are working on ATT. Can't get BT tether to work, though I was able to pair my laptop (Ubuntu) to the phone. When I tried to stream audio to the computer, no sound - so it does not appear a2dp is working, as you stated. But BT turns on and pairs. I do not have a headset to test call audio. but hold on let me see if call audio works through the computer

That didn't work, but that doesn't mean a headset won't. Connected to my computer it says (No Phone) beside it, though Phone Audio and Media Audio are both checked. I'll dig around for my headset

Edit: also, if you see this, since i synced with the lasest changes, I'm getting build errors about the redefinition of struct winsize and struct termio that was originally defined in termios.h. i tried deleting the referenced projects, cleaning, and resyncing - but it keeps giving me the same thing. Also ran setup-makefiles.sh again, and for s and g's ran extract-files.sh as well, just to be double sure.. what am i missing?

Ah, is it ccache trying to be too smart? Let's see..

Nope. Now I'm confused.
[HTC Vivid, Raider, Velocity] Cor-master:
Nah I ain't complaining just commenting, like I said if I can find time tonight, I'll nandroid and do some bluetooth testing, got my old ps3 headset I could use to see if standard bluetooth headset functionality works.

Feel like I should do something to contribute after all. Sorry if it seems like I'm complaining, really the problem is I spend waaaaay too much time on xda, Tapatalk is too convenient lol
[HTC Vivid, Raider, Velocity] h8rift:
Ignore that error...I know whats broken with termios.h.
[HTC Vivid, Raider, Velocity] homeslice976:
Nevermind what used to be here. I'll wait to hear you got it! Thanks h8
[HTC Vivid, Raider, Velocity] h8rift:
k. sync now.
[HTC Vivid, Raider, Velocity] homeslice976:
Thanks again man. I'll let you know if I hit any more snags. And again, awesome work on the bluetooth, and everything else. This project's coming right along!

Edit: one other snag i hit was "hardware/qcom/display/genlock/genlock.cpp 33" linux/genlock.h does not exist. I edited it to #include <genlock.h> rather than #include <linux/genlock.h> (as i saw genlock.h was in the same directory) and it appears to be continuing. However, I also see "#include "genlock.h"" under this entry, so I'm confused if another genlock.h needed to be pulled from elsewhere?

now getting this lol. i just had a successful build last night

target thumb C++: copybit.msm8660 <= hardware/qcom/display/libcopybit/software_converter.cpp
hardware/qcom/display/libcopybit/copybit_c2d.cpp: In function 'uint32 c2d_get_gpuaddr(private_handle_t*)':
hardware/qcom/display/libcopybit/copybit_c2d.cpp:267:19: error: 'KGSL_USER_MEM_TYPE_PMEM' was not declared in this scope
hardware/qcom/display/libcopybit/copybit_c2d.cpp:269:19: error: 'KGSL_USER_MEM_TYPE_ASHMEM' was not declared in this scope
hardware/qcom/display/libcopybit/copybit_c2d.cpp:271:19: error: 'KGSL_USER_MEM_TYPE_ION' was not declared in this scope
make: *** [/home/greg/android/pacman/out/target/product/holiday/obj/SHARED_LIBRARIES/copybit.msm8660_intermediates/copybit_c2d.o] Error 1
make: *** Waiting for unfinished jobs....
[HTC Vivid, Raider, Velocity] :
Just an update on 12/18 build. I had it installed for about an hour and my battery% dropped from 89% to 66%. The responsible party is System (brcm_patchram_plus) which is linked to Bluetooth. I turned bluetooth on temporarily for testing and turned it off, but other than that my phone wasn't being used during the period of time the battery dropped.

Also added it to the tracker but just was wondering if anyone else has seen this or was it just a bad flash or something else.
[HTC Vivid, Raider, Velocity] h8rift:
That's not CM specific...assuming PAC has its own github repo.
[HTC Vivid, Raider, Velocity] hovadrive:
Hey h8rift sorry if i ask too much time but really wanna know , I will Try this latest upload when i get home to check out bluetooth wanna know if you guys getting a force close from gtalk when you click video icon ? and also when someone call you in video chat it answers with video working but no sound?
[HTC Vivid, Raider, Velocity] :
^ This is a reported issue on h8rift's tracker:

http://code.google.com/p/htc-msm8660/issues/list
[HTC Vivid, Raider, Velocity] snorkle:
idk if this is an issue or not but my Wifi wont turn on, plus im experiencing really bad Batterylife, like 6 hours from 100% =/
[HTC Vivid, Raider, Velocity] Scrog:
Quick check, did you flash the boot.img via fastboot?
[HTC Vivid, Raider, Velocity] snorkle:
Yes i did, is that why?
[HTC Vivid, Raider, Velocity] Scrog:
No, usually wifi issues are because the kernel (boot.img) is mismatched or not flashed via fastboot. Try flashing again just to be sure.
[HTC Vivid, Raider, Velocity] VinnyCh4se:
h8rift has all the issues including the newest one #15.	Battery drain System (brcm_patchram_plus) on his bug changelog here http://code.google.com/p/htc-msm8660/issues/list as for the wifi issue you should try to flash the kernal before and after you flash the rom tho idk if that will fix it ive heard it works
[HTC Vivid, Raider, Velocity] capt8210:
Is there any other kernels for jb?

---------- Post added at 05:01 PM ---------- Previous post was at 04:59 PM ----------

I have a Bluetooth headset what was thought to not work.
[HTC Vivid, Raider, Velocity] LQQKS:
H8rift thanks again for tthe awesome job, I just can't say that enough!

Bt works for me, it picks up devices. Unfortunately I also have broken bt on my tablet (haha experimental CM10.1) so i can't test file transfers.

I really only use bt to connect to my car, tho it will connect and receive an incoming call, it won't transfer the sounds to speaker - maybe an a2dp profile.

And it won't even pick up my iwave (connects any bt device with iPod docks)

And also noticing the battery drain.

Great improvement tho \o/

sent from my rooted, S-Off HTC Vivid 4G \o/

running CyanogenMod 10 JellyBean 4.1.2
[HTC Vivid, Raider, Velocity] hovadrive:
I Know its re-post , I have ask the question there I got no respond I just need to know Thats all
[HTC Vivid, Raider, Velocity] Darkthefox:
I am having the same build issue.
[HTC Vivid, Raider, Velocity] homeslice976:
Reverting the boardconfig.mk part of this (https://github.com/htc-msm8660/andr...mmit/ae08bb1a01b58c862725b874c7ea3606a06967ac) commit allows the build to complete. Not 100% on what that'll be leaving out though. We'll have to wait for h8 to comment (looks like intervigil thinks there might be a better way for this include?)
[HTC Vivid, Raider, Velocity] h8rift:
ah geez. that last commit to reemove N_HCI was supposed to remove that BoardConfig change...let me fix...

EDIT:there. done.
[HTC Vivid, Raider, Velocity] rassawyer:
Hi ya'll. I know this is reported on the issues list, but I was wondering whether anybody had any suggestions that I could try to get get the internal storage working so i could have camera and Gallery working. Any ideas let me know. Great work all you devs, deepest thanks!!!
[HTC Vivid, Raider, Velocity] XxSHaDoWxSLaYeRxX:
it works for me.. strange.
[HTC Vivid, Raider, Velocity] meatwad0222:
Works for me...I use astro file explorer
[HTC Vivid, Raider, Velocity] mobile_fan_2k5:
Hey h8rift, can we get a change/update log for the nightlies?
[HTC Vivid, Raider, Velocity] meatwad0222:
Are there nightlies now?
[HTC Vivid, Raider, Velocity] KCutrer1:
We'll probably have a change log once there ARE nightlies
[HTC Vivid, Raider, Velocity] mobile_fan_2k5:
This is up now

12/18 Nightly Build - Holiday CM10

http://code.google.com/p/htc-msm8660/downloads/detail?name=cm-10-20121218-UNOFFICIAL-holiday.zip&can=2&q=
[HTC Vivid, Raider, Velocity] cannothas:
Working for me and I'm using the default file manager. Browse internal and SD card...

Sent from my Vivid 4G
[HTC Vivid, Raider, Velocity] meatwad0222:
That's just incremental ...nightlies will come after Bluetooth...I think that's what h8 said
[HTC Vivid, Raider, Velocity] swirly05:
I know im in the wrong thread and please forgive me...

Im on the first thread and im trying to unlock my bootloader, and help/suggestions TIA PLZ!!
[HTC Vivid, Raider, Velocity] hovadrive:
Go here bro http://xdaforums.com/showthread.php?t=1498003 there is the all in one Vivid tool
[HTC Vivid, Raider, Velocity] cannothas:
#1 suggestion is read read read. Don't get in too deep if you're new at this. This is about the most difficult android phone there is to customize :)

Sent from my Vivid 4G
[HTC Vivid, Raider, Velocity] swirly05:
did that and put my bin file in data folder... it wont go any further

im not new to this or anything, its my GF phone. Just seem to be stuck, though that there was another way
[HTC Vivid, Raider, Velocity] meatwad0222:
Pm me
[HTC Vivid, Raider, Velocity] cannothas:
Have you tried the HTC way yet?

See here: http://xdaforums.com/showthread.php?p=20795908

[SUPERGUIDE] ICS-Root-Flash-Stock

Sent from my Vivid 4G
[HTC Vivid, Raider, Velocity] swirly05:
havnt but i thought this would be more effective

i dont want to run this thread up with my issue sorry :(
[HTC Vivid, Raider, Velocity] cannothas:
I said I'd report back, so here's what I got: a new DD :D I have nothing going on here that isn't on the list of fixes already! All y'all have done and are doing a superb job on this device! Thank you!

Sent from my Vivid 4G

Sorry if my responses to other off-topicness is spamming the thread. I thought of that after I posted.

---------- Post added at 11:08 PM ---------- Previous post was at 10:42 PM ----------

Sent you a PM

Sent from my Vivid 4G
[HTC Vivid, Raider, Velocity] camo_flage:
Htc dev.....

Sent from my HTC Raider on the Rogers Wireless Network
[HTC Vivid, Raider, Velocity] homeslice976:
Possible fix for more suitable in call volume (issue 10) and distorted speaker volume on max. Definitely sounds better to me anyway

Flash in Recovery and reboot:

Link Removed

Please let us know

Edit: must have been placebo, ess.boyer is exploring a few other possible leads atm
[HTC Vivid, Raider, Velocity] :
Definitely a volume boost, but I thought it was fine before the fix, still noticed that the audio sounds a little garbely; but I think it has been that way since the first fix

Sent from my Vivid 4G
[HTC Vivid, Raider, Velocity] ZeRo2o9:
Does sound a bit better thanks

sent from my Pac-Man HTC Vivid
[HTC Vivid, Raider, Velocity] theslam08:
Agreed on the fix, that seems to have made the volume louder (can hear them better).

EDIT: NVM, volume sliders are broken, its in tracker.
[HTC Vivid, Raider, Velocity] rassawyer:
It seems to be only two of us that have this issue. I'm going to try PA and see if it works there. When I go to Settings>Storage and click the first "Mount SD" it comes up with the memory breakdown like it's supposed to "Apps, Pictures, Audio, Downloads" but then that disappears and it goes back to unmounted. The external SD card works fine, but I can't download anything and I can't use Gallery or Camera. What's really strange is that when I try to open Gallery, It shows my albums from the SD card underneath the "No External Storage" error message.

Edit. Same issue on PA
[HTC Vivid, Raider, Velocity] lucasryan:
Just out of curiosity, have you used that sd card in another device, if so what device was it used in... or is it a new sd card? Also do you have another sd card that you could try to see if you get the same results...
[HTC Vivid, Raider, Velocity] sadoway:
Did nothing for call volume. I still turn it up all the way and can barely hear them.

Same as before.

I'm using rogers raider on telus.
[HTC Vivid, Raider, Velocity] rassawyer:
No, I haven't used this SD card in any other devices, although it worked fine before I came to CM 10. I can navigate to the SD card via file manager (SD card 1) but not internal storage (SD card 0) I'll see if I can find another SD card and see what happens.
[HTC Vivid, Raider, Velocity] rignfool:
Pull the external card all together...
[HTC Vivid, Raider, Velocity] big_yute:
Same results here as well. On bell Raider with bell.
[HTC Vivid, Raider, Velocity] :
For me my SD card is listed as exetrnal_SD and the internal storage is listed as SDcard. Both mount when connected to a PC.

HTC Vivid CM 10
[HTC Vivid, Raider, Velocity] cannothas:
This will work for S-on as well?

I'm trying now anyway :)
[HTC Vivid, Raider, Velocity] homeslice976:
It should but it sounds like there's mixed results. All I did was set headset volume and speaker volume to stock levels
[HTC Vivid, Raider, Velocity] cannothas:
I want to say it is a bit louder, I feel like it isn't quite where I'd like for it to be. No complaints though. Still usable.

Sent from my Vivid 4G
[HTC Vivid, Raider, Velocity] LQQKS:
Yup just flash just flash boot.img first. Its included in the downloaded zip file

sent from my rooted, S-Off HTC Vivid 4G \o/

running CyanogenMod 10 JellyBean 4.1.2
[HTC Vivid, Raider, Velocity] XxSHaDoWxSLaYeRxX:
My ext_SD works in galary etc. But doesn't mount to pc