yashsingh1/xdaforums huggingface dataset:
[HTC Vivid, Raider, Velocity] homeslice976:
1. Youre the first to report random reboots

2.I have used the first three apps you mentioned without issue (though they need to be installed from the play store, not included in gapps) I have not tried translat

3.mic works fine for everyone but you, but yes in call volume cannot b adjusted, and is currently using a value lower than optimal.

5.you're the first to report this.

It sounds like you either got a bad flash, you restored data that shouldnt have been restored, and/or didn't flash the boot.IMG.
[HTC Vivid, Raider, Velocity] camo_flage:
I have gotten a random reboot but only one and then it never happened again

Sent from my PACMAN HTC Raider on the Rogers Wireless Network
[HTC Vivid, Raider, Velocity] RujinXERO:
I can confirm that translate works perfectly fine for me. No issues what so ever.
[HTC Vivid, Raider, Velocity] big_yute:
Flashed this rom last night and so far it's been good. Not worried about the battery as yet as I am still configuring my settings. :thumbup:
[HTC Vivid, Raider, Velocity] jtsurfs:
I can report that I have not had the 24% battery thing. I purposely let my battery get down to 24% and then after an hour it changed to 23%. Perhaps people are not letting this ROM cycle through a couple of recharges before they really start monitoring battery life? I never had that issue even before the overclock kernel. And after the overclock Kernel and a couple of days of use the battery life is excellent. I can also say the in call volume is not low for me.
[HTC Vivid, Raider, Velocity] homeslice976:
I got external and internal USB mounting to the computer via UMS :)

Testing some. Should have an updated boot.img tomorrow sometime

It now works like it would on Sense. You plug it in, you click Turn On USB Storage, both Drives pop up and ask what you'd like to do :)
[HTC Vivid, Raider, Velocity] jtsurfs:
Here are the screen caps of my usage today, odd that it doesn't show SMS and phone on the app usage...
[HTC Vivid, Raider, Velocity] camo_flage:
Even after putting the rom through its cycles this still occurs

Sent from my PACMAN HTC Raider on the Rogers Wireless Network
[HTC Vivid, Raider, Velocity] ess.boyer:
Sweet! Can you post code changes and or pm me?
[HTC Vivid, Raider, Velocity] magus_blackomen:
Patience.

Sent from my Vivid 4G using Xparent ICS Tapatalk 2
[HTC Vivid, Raider, Velocity] ess.boyer:
No. Now. Get me his phone number and I'll get his lazy *** out of bed.
[HTC Vivid, Raider, Velocity] big_yute:
Lmfao!
[HTC Vivid, Raider, Velocity] ZeRo2o9:
What is UMS ?

Sent from my HTC Vivid 4G
[HTC Vivid, Raider, Velocity] homeslice976:
I

Lol ill publish the changes as soon as its released

Universal media sharing is a USB transfer protocol. People like to debate whether it or mtp (media transfer protocol) is better

Oh and BTW.. it came to my attention last night that I broke the in call mic. So I'll have to rebuild this morning. Update should be this afternoon. As long as all goes well
[HTC Vivid, Raider, Velocity] rignfool:
If you dig... you can find his number on some screenshot of a text message...
[HTC Vivid, Raider, Velocity] homeslice976:
External USB Mounting to Computer Fix

Yup - in pulling my hair out over the last week or so trying to accomplish this, at some point I had replaced board-holiday-audio.c with the one from source without the fix. I have a fixed one now, waiting on the boot.img.

Lol no he won't, I removed it a day or two after I had it up :) Unless Google has a cached image he can find. But my online handle is the same over multiple sites - my number wouldn't be that hard to find, but I don't answer numbers I don't know lol

Edit: The following is mainly for my future reference or anyone else who might be looking for a similar solution, but I suggest the read anyway:

First, I used this (and the pages following) as a reference:

http://xdaforums.com/showpost.php?p=35918121&postcount=2616

I'm going to skip all of the things that didn't work - because it took about 20 attempts doing different things before I got one that worked (seemingly due to the fact that the source I was working with were either corrupted or incomplete). So here goes. I downloaded the attachment here (http://xdaforums.com/showpost.php?p=35920971&postcount=2628), looked at his board-ruby.c and the stock ICS board-ruby.c to see what edits were made. I used our board-holiday.c and .h, and in our .c, made the same edits, but also needed to add BCM LPM support back (https://github.com/htc-msm8660/andr...mmit/bddcdd3802d97220b6e4165cb6c5503b55c88539) to board-holiday.c. In the end, I needed to empty our current /drivers/usb/gadget and drivers/char/diag directories and replace them with the contents of the drivers I had previously downloaded from dcacklam. For some reason the source I had downloaded was giving me all sorts of fits, or I'd have had this done days ago... I did have to use the composite.h from the source I had, as I was getting compiling errors with the composite.h provided. In the end, we're now using the HTC ICS USB gadget so it performs the way we want it to.

Note for anyone else doing this at home. You will also need to update your BoardConfig.mk lun path, so that it creates vold properly to look for both luns where they should be. The lun path should be /sys/class/android_usb/android0/f_mass_storage/lun%d/file. Your next build should have vold created properly. In the mean time, you can use vold from PA or PACman, as they're both already setup like this (have been since I started trying to fix this weeks ago). If you're using CM10, you'll need our vold as well. I'll make flashables later.

PLEASE VISIT ONE OF THE FIRST TWO LINKS AND THANK DCACKLAM. WITHOUT HIS FINDINGS THIS WOULDN'T HAVE BEEN POSSIBLE!!!

HERE IS A FLASHABLE .zip for PACman and PA!

S-Off users - flash and reboot.

S-On users - flash, boot to bootloader, flash the boot.img that's included, reboot

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

HERE IS A FLASHABLE .zip for a CM10 user to test. It includes the vold that should be setup properly for the multiple luns. Please report back and let us know

S-Off users - flash and reboot.

S-On users - flash, boot to bootloader, flash the boot.img that's included, reboot

http://www.mediafire.com/?d54qp6ghjef587s
[HTC Vivid, Raider, Velocity] ess.boyer:
Very good work, thanks! Do you think that it's necessary to use the whole driver, or do you think that there are pieces we could extract? I hope to have some time to help you out with some of this. We'll try to get a cleaner, more JB patch so we can get the fix into repo.

(PS - I hope it goes without saying that I was being sarcastic in my reply to whoever felt it necessary to tell me to "be patient" when I commented asking for code/info without implying any kind of expected time frame for delivery of such).

This is going to be a big help for a lot of people!
[HTC Vivid, Raider, Velocity] homeslice976:
It's very possible not all of the drivers are needed. One day I may revisit that - If you have some time that would be awesome. In the meantime, no performance seems deteriorated, so it's not something I'm entirely worried about.

And yes, I knew that was sarcasm!

BTW - flashable .zip posted 2 posts above. I dd'd the boot.img if anyone is curious why it is so big.
[HTC Vivid, Raider, Velocity] ess.boyer:
By the way, which kernel repo are you syncing to for PAC?
[HTC Vivid, Raider, Velocity] homeslice976:
I forked htc-msm8660 and use mine now, when I wasn't really making any changes i used htc-msm8660's.

Having trouble committing the most recent changes, but it should be committed before too long

BTW - also a flashable .zip for CM10 users to try that includes our vold, that should give them access to external storage as well here (http://xdaforums.com/showpost.php?p=36742362&postcount=452). If there are any CM10 users lurking, give it a shot and let us know.
[HTC Vivid, Raider, Velocity] ess.boyer:
Speaking of intervigilium's commit for BCM LPM, I wonder if that was included in H8's kernel and if that will fix the horrible BT drain. If not, we must be missing the "switch" to turn LPM on somewhere when BT gets turned on. I might have a look into that while I'm at it, but I don't own any BT devices to pair with for testing. Is simply turning BT on on the phone w/o pairing it enough to cause the battery drain?
[HTC Vivid, Raider, Velocity] lilmikey201:
the new zimage fix makes it so my wifi doesnt work

??
[HTC Vivid, Raider, Velocity] homeslice976:
Yes - the BT LPM addition was in the htc-msm8660 source when h8 picked it up

And yes, as long as BT is on, the drain is there. But I don't use it either, so I don't necessarily know how bad it is, or if it's worse when something is paired

You need the bcmdhd.ko as well.

Are you s-on or s-off? I just removed the link to the zimage and .ko. Use the flashable .zip. If you're s-on, you need to flash the .zip, then flash the boot.img via bootloader
[HTC Vivid, Raider, Velocity] homeslice976:
delete me
[HTC Vivid, Raider, Velocity] lilmikey201:
.yea i did the mcmdhd.ko and z image just like u said and wifis off..im S-ON which zip and flash the original boot.img? or did u make a new one
[HTC Vivid, Raider, Velocity] ess.boyer:
Is that the correct kernel module Homeslice? Shouldn't it be a bcmdhd?

EDIT: Just checked the zip and it does have the bcmdhd.ko and not mcmdhd.ko.
[HTC Vivid, Raider, Velocity] lilmikey201:
i ment B..typing mistake
[HTC Vivid, Raider, Velocity] homeslice976:
You're missing something. Download the flashable zip, flash it, boot to bootloader and fast boot flash boot.IMG. or just s-off and make your life easy :)
[HTC Vivid, Raider, Velocity] :
Guess I'm one of those lurking CM10 users :).... Flashed it and both internal and external mounted correctly.
[HTC Vivid, Raider, Velocity] ess.boyer:
Hey Homeslice, since you already have the ICS USB stuff in place, you should try this USB OTG fix.

I tried to implement it in the JB kernel, but it still wasn't working as there was missing work to be done in the USB driver. It might just work with your latest changes.

I'm going to try to cherry pick the fixes you put in place, without replacing the whole works, otherwise I would try this myself today.
[HTC Vivid, Raider, Velocity] homeslice976:
I will look at it. I don't have any thing to test OTG with though. wheres 10000001?? lol

The commit will be up in a bit. I redid everything so the commit was a little more proper, and then you should be able to pull it. Just making sure the 'new' changes build and work properly before committing.
[HTC Vivid, Raider, Velocity] ess.boyer:
Scratch that for now anyway. I just discovered that (duh!) the OTG drive is absent from the JB kernel... I'm going to add it to my next build from the 3.0.40 kernel from HTC. I currently don't have anything to test with either. I think I will sacrifice one of my USB extension cables and just build one.
[HTC Vivid, Raider, Velocity] Garrykd:
Another CM10 lurker here. I can confirm both internal and external sd mount properly. I also transferred 2 gig from the internal and 7 gig from the external....all seems fine. Thanks.
[HTC Vivid, Raider, Velocity] bproulx:
Flashed the usbfix kernel and all is good. Thanks again! This ROM is getting better every day. Can't believe how much progress has been made already! You guys friggin rock!
[HTC Vivid, Raider, Velocity] homeslice976:
FYI - the USB fix for the Ruby was submitted and rejected (start at 3177 - http://xdaforums.com/showthread.php?t=1773274&page=318). So chances are pretty good it will never be fixed in CM's source (at least not this way - see 3180 in the previous thread, dcacklam is pretty sure it's impossible as is). It appears intervigil may think there's a better way (http://review.cyanogenmod.org/#/c/30332/), but until I see it, I'm leaving it alone on my builds.
[HTC Vivid, Raider, Velocity] ess.boyer:
Yeah, that's not too surprising really. That's pretty drastic, and is likely swatting a fly with a hammer, if you know what I mean. I'm sure we can cherry pick the things from the Ruby drivers that will fix it for everyone. I think MOST of the fix is in your vold.
[HTC Vivid, Raider, Velocity] homeslice976:
My vold has been setup the same for weeks - no matter what else I tried nothing worked until using the ICS drivers, which is what they don't like. So my guess is anything from ICS source is going to be rejected, and according to dcacklam it's impossible to do with the CM10 usb gadget driver.. If there's a way to simply do it with vold, that's awesome. But after battling with this for weeks, I just don't know.
[HTC Vivid, Raider, Velocity] ess.boyer:
There are changes required to the JB driver I'm assuming, but just blanket replacing 40+ objects is probably not unnecessary if it's really only a few bits and pieces. However the driver is working, the vold must be correct, or you'll never get both mounting.
[HTC Vivid, Raider, Velocity] camo_flage:
Dunno if anyone else is having this issue but with the new boot.IMG when I get a text and to a quick reply ( popup message thing ) from the notification bar sometimes it will say messaging has stopped

Sent from my PACMAN HTC Raider on the Rogers Wireless Network
[HTC Vivid, Raider, Velocity] homeslice976:
Nope..I've replied to a bunch of texts from the quick text window
[HTC Vivid, Raider, Velocity] big_yute:
I'm on a bell Raider, I haven't experienced that issue. Maybe try disabling the feature, reboot and re enable. If that doesn't work then another wipe and re flash could be in your near future..
[HTC Vivid, Raider, Velocity] ess.boyer:
Ok! I did a directory diff against all the changes you committed for the USB stuff...

95% of the changes were on "my" side (the htc-msm-8660 repo side) were bug fixes and minor changes. The vast majority has nothing to do with OTG or mass storage.

I included all the pieces that looked like omissions involving OTG or mass. I was conservative, because I wasn't sure all the time whether or not a change that has been left out on "my" side was done so because it was moved or refactored, so I took each change with a grain of salt.

If the vold changes are in the PAC source I've been syncing, then cross your fingers - I might have a build with double mass storage AND OTG in about an hour.

Homeslice:

Hmmm, the more I think of it, I don't think the vold changes are included in PAC... Can you message me with the details on what and where need to be changed? It's something in VolumeManager.cpp is it? I can always just temporarily make the change to vold.fstab though right?
[HTC Vivid, Raider, Velocity] homeslice976:
Check out the comment underneath of the latest commit. That should tell you what you need to know. I'll pm you tomorrow with more details if you're still having trouble. Now I'm going to sleep
[HTC Vivid, Raider, Velocity] ess.boyer:
Right. Thanks.

Oh, I also potentially fixed fast charge. If it seems to work I'll post the changes here.
[HTC Vivid, Raider, Velocity] XxSHaDoWxSLaYeRxX:
Happened to me once but I was getting a crap load of texts.

---------- Post added 16th January 2013 at 12:07 AM ---------- Previous post was 15th January 2013 at 11:58 PM ----------

Just curious.. what ever happened to aokp .?
[HTC Vivid, Raider, Velocity] Mr_Random:
Flashed it all again, working well now, must have done as you said and screwed up the first time. Gotta set up Voicemail, if all is well there and with the mic, this will be my DD :)
[HTC Vivid, Raider, Velocity] homeslice976:
Anyone out there have a wired headset with a mic and want to test this for me? It should enable the mic in wired headsets. I was able to confirm that the device mic was enabled when connected to aux out (aux to my car's head unit, so remote end came through car speakers, and could hear me through the device mic). Sounds like h8 thinks the two issues are the same (http://code.google.com/p/htc-msm8660/issues/detail?id=10) so it should fix wired headset mics as well. Please let me know

http://www.mediafire.com/?3idqhan1t064cr6

Flashable in recovery. If you're s-off, just flash and reboot. if you're s-on, flash, boot to fastboot and flash the boot.img that's included
[HTC Vivid, Raider, Velocity] big_yute:
Who does this apply to as I have been able to use my wired headset from day one of flashing this rom. I have a bell Raider though..
[HTC Vivid, Raider, Velocity] homeslice976:
No idea. The only reports I had seen were people saying it didn't work (I honestly didn't even try it before attempting to fix it, oops, making an ASS out of U and ME) - I haven't seen anyone report the contrary as seen here (http://code.google.com/p/htc-msm8660/issues/detail?id=10) and here (http://code.google.com/p/htc-msm8660/issues/detail?id=29)

Do you have an HTC headset, or is it another manufacturer? Can anyone else confirm whether this has worked for them previously?

Also - while we're at it, it would be nice to have a Velocity and Raider owner verify that they are unable to control in call volume? I want to make sure that's not isolated to the Vivid
[HTC Vivid, Raider, Velocity] big_yute:
I have the HTC headset. Never had an issue with anyone hearing me while using it.
[HTC Vivid, Raider, Velocity] homeslice976:
Yea - htc headsets appeared to already be enabled. This will probably be for non-htc headsets. Just need someone to tell me :) Or i'll figure it out when I get home.

Edit: Nevermind - found a headset with a mic and the mic still didn't work. At least I have one to play with now
[HTC Vivid, Raider, Velocity] bproulx:
Raider here ..in-call volume has been static/immovable for me in all builds so far up to and including current. Audio is clear but quiet. Music playback works fine, notifications OK as well.. just the in-call volume is stuck. Wouldn't mind so much if only it was stuck at "full" lol..

Regardless..this ROM is wicked cool. I have faith that all the little things will get sorted out. We've got some brilliant minds on it.
[HTC Vivid, Raider, Velocity] sadoway:
Volume controle

I have the rogers raider. And I while I can controle the volume. I have to have it at max always. Or I will not be able to hear the person talking on the speaker. I had the problem with holics ROM. And no mater what kernel I used it would never get as loud as it should. Other ROMs and kernel combos I have not had this problem.

I'd really like this fixed. Seems people are more worried about the ecco. But I honestly avoid making phone calls because I always have yo say *what*

And if they put me on speaker phone when they are driving. I cannot hear them at all. Its so faint.
[HTC Vivid, Raider, Velocity] homeslice976:
So one Raider volume control doesn't work, one Raider volume control works fine? I'm having some issues understanding that..

I know that the slider itself works, but, sadoway, you're SURE it's actually adjusting the volume?
[HTC Vivid, Raider, Velocity] Garrykd:
I'm on a Rogers Raider (CM10) and the volume rocker has no effect, call volume remains constant (and low-ish).
[HTC Vivid, Raider, Velocity] homeslice976:
This still doesn't allow in call volume control to actually work, but I'd like to know 3 things:

Is volume on your side improved?

Is volume on the remote side improved (can the remote party hear you any better)?

Did this make the remote party echo improve, worsen, or stay the same?

Flashable in Recovery. S-On users will need to flash, boot to bootloader and fastboot flash the boot.img. If you feel it's worse, just reflash the kernel I released yesterday.

-link removed- sorry again guys
[HTC Vivid, Raider, Velocity] Garrykd:
Yeah, that sucked haha

Remote party couldn't hear me (both outgoing and incoming calls)

They sounded like they were in a slow motion time warp (or some sort of demon) and the in call ringer also sounded odd

I guess echo would be n/a

It was fun though....I sure confused several people :D

Oh, and volume would be about the same, I guess
[HTC Vivid, Raider, Velocity] sadoway:
Yeah it for some reason dropped the pitch a lot. And they said they couldn't really hear me. Just seemed to my phone with the low pitch on speeker.. Phone is unusable now.

---------- Post added at 10:40 PM ---------- Previous post was at 10:39 PM ----------

Is there a small zip I can flash to revert. I should have backed up and didn't
[HTC Vivid, Raider, Velocity] Garrykd:
Flash the kernel that applies to your rom (below):

HERE IS A FLASHABLE .zip for PACman and PA!

S-Off users - flash and reboot.

S-On users - flash, boot to bootloader, flash the boot.img that's included, reboot

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

HERE IS A FLASHABLE .zip for a CM10 user to test. It includes the vold that should be setup properly for the multiple luns. Please report back and let us know

S-Off users - flash and reboot.

S-On users - flash, boot to bootloader, flash the boot.img that's included, reboot

http://www.mediafire.com/?d54qp6ghjef587s
[HTC Vivid, Raider, Velocity] camo_flage:
No LTE

No matter what I do including tweaking the apn's all over the place I can't seem to get LTE working.....can anyone point me in the right direction?
[HTC Vivid, Raider, Velocity] homeslice976:
Whoops. Sorry guys. Thanks for testing. It didn't do that to me or I wouldn't have shared! My bad
[HTC Vivid, Raider, Velocity] Garrykd:
No worries.

Can you make my voice sound like a demon to other callers?....that would come in handy :eek:
[HTC Vivid, Raider, Velocity] Mr_Random:
Been running all day;

Random auto-rotate failures (g-sensor, reboot fixes)... may be just this phone, I had the same problem with Kangbang 2.0 when running Holics ROM, but the kernel that came with Holics never had that issue (may be something to check out there?). Seems to happen after every battery pull, but sometimes just happens randomly otherwise.

Mic works, call volume non-adjustable (common problem, I know, but might as well say it)

Voice searching and typing works great, as does google now, but when using google now to search and call ("call pep boys auto" is what I used), it shuts the screen off and continues with call, but I have to battery pull in order to get the screen on again.

JUST tested normal calls; screen will shut off completely until call is completed (hanged up on remote end). I have no control of my phone until then... I'll research how to get a log of this happening.

One more weird thing; might be my thumbs, but when I touch the O or W on the keyboard, it sometimes doesn't register, almost like there is unreasonable lag for just those two buttons (I just got a new screen/digitizer, so I don't see how they are the problem).
[HTC Vivid, Raider, Velocity] sadoway:
Page or two back. Volume slider doesn't do anything. Stays the same. No louder no quiter when I adjust it
[HTC Vivid, Raider, Velocity] homeslice976:
I think I know why that last kernel got all crazy on you. I had forgot that I had made some other changes prior to that change (not in the kernel), that were probably working hand in hand. Cause I just tested with that kernel and everything was crystal clear on both sides. I'll have something else for someone to test later (after the kids are in bed) if someone's feeling up to it?

Yes, that's why i was confused, cause in that post you said "while I can control the volume, I have to have it at max or I will not be able to hear the person talking" That sounded like you were getting different volume levels at different settings, which I was confused about. Thanks for clearing it up.

Unfortunately I'm not in an LTE area, so I have no way of confirming or helping with that one..

I have not seen any auto rotate failures.

As far as the "black screen" proximity sensor issue in calls - this seems to be something that only affects some users. Try the fix suggested in this issue (http://code.google.com/p/htc-msm8660/issues/detail?id=14) and report back.

Also I have not had any trouble with any letters on the keyboard when typing. Just curious, does it behave the same way whether haptic feedback is on or off?
[HTC Vivid, Raider, Velocity] lucasryan:
I have a samsung headset that came with my focus, i could try if your still needing some info on the in-call mic info on the non HTC headset?
[HTC Vivid, Raider, Velocity] homeslice976:
Nope.. don't think that worked