yashsingh1/xdaforums huggingface dataset:
[HTC Vivid, Raider, Velocity] RujinXERO:
At least one other than myself. Here is the qa post http://xdaforums.com/showthread.php?t=2068682
[HTC Vivid, Raider, Velocity] ess.boyer:
You could disable them the same way too if you like by setting the allowed current to 0mA.
[HTC Vivid, Raider, Velocity] rignfool:
I would actually be willing to bet you do... but based on the way you hold the phone its not a problem...

I only noticed it when I hold the bottom of the phone away from my mouth as I yell at my kids... when I pull it back, I hit dial buttons... or worse... I hang up
[HTC Vivid, Raider, Velocity] homeslice976:
So the issue isn't that it doesn't work, it just doesn't reengage after disengaged? I will keep my eye open..but I do ablotbof pulling the phone away for the same reason
[HTC Vivid, Raider, Velocity] ess.boyer:
Not sure how much of a "problem" it really is, at least on my device, it seems to behave normally.

Using a market app called "Proximity Sensor Finder", you can tell where you sensor is (near the ear piece) and how long it takes to trigger on and off. You can also test of the sensitivity of it. A 9 means that the sensor doesn't detect anything, and 0 means that the sensor is covered. Some prox sensors can detect distance, but ours just detects on or off.

In testing, mine seems to be about 1000ms on, and 100ms off. On a call, it seems more like the other way around.

I believe there is a build.prop change you can make that will change the timing of the proximity sensor to your liking. Try mot.proximity.delay=25 (which I'm assuming is msecs, so, if you wanted it to wait a long time, try: mot.proximity.delay=2000 (for 2 seconds). Me, I like it shorter, because I end up calling a lot of IVR's and it's really annoying to have to wait a few seconds for my screen to wake up everytime I need to hit a button. I realize that this will be the opposite for most users.

Hope that helps!
[HTC Vivid, Raider, Velocity] positiveg:
How were you guys able to root your Vivid prior to installing this ROM? I have been unable to get this phone rooted since I got it 3 weeks ago. Thanks
[HTC Vivid, Raider, Velocity] homeslice976:
Just unlock your boot loader through HTC dev, flash a custom recovery via fast boot, then flash the ROM, then flash the boot.IMG via fasboot. There's more in depth threads in the forum. All the roms here are already rooted
[HTC Vivid, Raider, Velocity] ess.boyer:
Disable hw overlays option in developer options is required for chrome to behave, but I have to re-check it after every reboot.
[HTC Vivid, Raider, Velocity] cwhittl:
Love this Rom! The only issue is that it won't detect my rocket fish Bluetooth hands free unit. It will detect my roku and tune link but not my hands free.
[HTC Vivid, Raider, Velocity] LQQKS:
There are some ongoing issues with BT that h8 is working on. Ad2p profiles don't work yet. I can for instance connect to my car but not take calls. I can't detect my iWave..

I'm sure once the holidays are over he'll be looking into it :)

using the BT atm also has a big battery drain h8 is working on

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

running CyanogenMod 10 JellyBean 4.1.2
[HTC Vivid, Raider, Velocity] ZeRo2o9:
I have the problem with the Prix sensor I'm the one who reported the error and it doesn't do it on ICS. I tried using a fix I found while searching Google and it disabled the sensor

---------- Post added at 12:24 PM ---------- Previous post was at 12:22 PM ----------

I used that app it doesn't register the distance
[HTC Vivid, Raider, Velocity] cwhittl:
Was pretty sure of that just wanted to report just incase it was new..... I really love this Rom!
[HTC Vivid, Raider, Velocity] cwhittl:
Ok got what I think is a new one. When anyone calls me 9 times out of 10 when I answer I can heard them but they can't hear me. When they call back the call goes just fine both ways. I'm on AT&T
[HTC Vivid, Raider, Velocity] homeslice976:
Is it the first call after a reboot or after a fresh flash? This is the only time that might happen and anyone has reported it happening. Also..what carrier, and vivid raider or velocity?
[HTC Vivid, Raider, Velocity] joerolando2701:
This has happened to me on att as well if I cycle speakerphone on and off then they can hear me
[HTC Vivid, Raider, Velocity] dexim:
I installed this ROM on a friends phone. I did a factory reset and wiped cache, so it's a clean install. Anyone calling this phone hears a loud echo. Has anyone else experienced this? Any suggestions for a fix? Other than that, the only problem is the Bluetooth not working, which is a know bug.
[HTC Vivid, Raider, Velocity] cannothas:
To anyone else using Google talk: I know on the issues list it states that mic isn't working in gtalk. I seem to be having issues with the speaker not working as well, both in video and non video modes. I do not year the other party, and they don't hear me. I've commented on the issue and uploaded log cats there.

Just curious what your mileage has been? Do you hear the other person?
[HTC Vivid, Raider, Velocity] Ldbrown01:
Does FM Radio work?
[HTC Vivid, Raider, Velocity] rignfool:
There is no FM radio app in the ROM...

Maybe spirit radio might work...
[HTC Vivid, Raider, Velocity] emmissary1:
Yea I put this rom on my wife's phone and had the same issue. I was getting a bad echo and sounded like she was on speakerphone or in a bathroom the whole time. Had to reset the phone and go stock.
[HTC Vivid, Raider, Velocity] ess.boyer:
I can second that people are complaining about echo, though it doesn't seem to be everyone.
[HTC Vivid, Raider, Velocity] theslam08:
People have also been telling me there is waay to much background noise usually (not everytime though), like when I am driving they can hear me speeding up and they say it sounds like im hanging out the window, but all my windows are up and radio off (quiet as can be - but obviously not a silent room). On ICS the car driving noisiness was not a problem. Wondering if the noise cancellation mic is working? Or maybe too high of input gains? The problem of them not hearing us is no longer for sure lol
[HTC Vivid, Raider, Velocity] rignfool:
The noise cancelling mic is the att in-call issue
[HTC Vivid, Raider, Velocity] homeslice976:
Not exactly. The second mic is just a second mic. The audience a1026 chip used that second mic for noise suppression. The raider and velocity don't have that chip, but still use the second mic for noise suppression through software. The in call audio fix circumvents the a1026 chip but doesnt disable the second mic. Does enabling noise suppression in call settings help anyone?
[HTC Vivid, Raider, Velocity] theslam08:
Can it be enabled in the build prop? I see hac and alt a1026 lines but not sure I have noticed any changes with them being 1 or 0 (on or off). They could be doing nothing (or not the 'correct' one).
[HTC Vivid, Raider, Velocity] homeslice976:
I don't know for sure. I think the build.prop entry just tells the rest of the system whether or not the a1026 is present. Even so, the kernel now tells the device to act the same way/perform the same function whether or not the a1026 is present, so I'm guessing that entry is now moot - but I could be way off.
[HTC Vivid, Raider, Velocity] rignfool:
When I use the software noise suppression... I get complaints that I sound like I have a mouth full of marbles
[HTC Vivid, Raider, Velocity] camo_flage:
I can't seem to get lte working apns are fine

Sent from my HTC Raider on the Rogers Wireless Network
[HTC Vivid, Raider, Velocity] homeslice976:
Okay. And they hear themselves echo or do they hear you echo?
[HTC Vivid, Raider, Velocity] :
I've run into that same problem from time to time. Reboot or changing APN usually fixes it.
[HTC Vivid, Raider, Velocity] hovadrive:
No difference here same thing as you have it also force close
[HTC Vivid, Raider, Velocity] homeslice976:
Possible fix for this here (https://github.com/dzo/hardware_qcomm_media/commit/01792b063e847d6ddd17f64695168d12a17b34bb). I'll give it a shot later when I have a moment, or someone else can give it a go now.

edit: the build process didn't seem to like this change
[HTC Vivid, Raider, Velocity] rignfool:
From what I understand... with suppression on... there is no echo... but I can't be understood... with it off... they hear themselves echo but I can be understood...

And the echo is not always the same amount... sometimes its worse than others...
[HTC Vivid, Raider, Velocity] ZeRo2o9:
Yes this happens to me too
[HTC Vivid, Raider, Velocity] Monkeymannnn:
Try entering *#*#4636#*#* into your dialer. Phone information. Scroll til you see preferred network type and if it's not already set to it select gsm/lte auto.

If that doesn't work try reflashing the ROM. Lte is working for me and just about everyone else as far as I know.
[HTC Vivid, Raider, Velocity] homeslice976:
I just recorded and played back with 1080p :)

I have a little more testing to do, but will share this afternoon.

Definitely appears to be doing what it should. 720p recorded at 1280x720, 12,691kbps bitrate, 27 frames/sec. 1080 recorded at 1920x1088, 17,011kbps bitrate, 25 frames/second (at least according to Windows) - it required these edits:

To media_profiles.xml:

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

(I also bumped bitrate for 720p to 14000000)

And I used the media_codecs.xml from the Samsung Hercules CM10 build ("SII X", though the Skyrocket shared the same as well. The Hercules and Skyrocket are both MSM8660 devices like ours, and the Hercules is actually an APQ8060, like ours - source - though it says both variants are APQ8060, phonearena says the Skyrocket is MSM8260. Either way - those official CM10 builds might shed some light on some of our issues as well - but probably not all of them).

Here's a flashable fix. Note that since this is just a flashable fix, the first time you try to record or playback your 1080 videos, it might hiccup and appear to do nothing. Just try again and it should start. And also please note that although this has enabled 1080 recording and play back, it appears that the garbled/glitchy stuff hasn't completely gone away in HD recording (720 or 1080), though it doesn't appear to be part of the video (when I view on my computer its not there, and if I watch it again on the phone it's not there).

https://docs.google.com/open?id=0B8HUFb41pK2ednlHZndRVFJSTW8

File>Download

Feedback is welcome.

(located at /device/htc/msm8660-common/configs if you're making the changes manually :))
[HTC Vivid, Raider, Velocity] ideaLduK:
Blocked for TOS violation?
[HTC Vivid, Raider, Velocity] homeslice976:
wtf..

https://docs.google.com/open?id=0B8HUFb41pK2ednlHZndRVFJSTW8

File>Download

Edit: Just made the link available without requesting permission, sorry about that.
[HTC Vivid, Raider, Velocity] homeslice976:
h8 - is this a cleaner fix then the one we're using? It looks a lot cleaner - like is it actually a fix rather than a workaround?

http://review.cyanogenmod.org/#/c/29011/

Confused why we haven't seen it? Compiling a build now..

You sure have been quiet :)
[HTC Vivid, Raider, Velocity] ess.boyer:
That only seems to ensure the fix is only done to the holiday. This is probably to make it compliant with the msm-8660 tree under the cm project.

Also, I believe that commit was by h8
[HTC Vivid, Raider, Velocity] homeslice976:
Yes it was. That's why i was wondering why we hadn't heard about it.

Decent explanation though - but it's reverted the original workaround I provided. Which leads me to believe it's not in addition to, but instead of. My guess is it's probably a proper fix (maybe it will work the first time everytime?) I'm compiling a fresh build with the 1080p fix and this in call fix, rather than my in call fix. It won't be done til about midnight and I'll be passed out. But i'll know in the morning

Edit: In case anyone was wondering - like h8rift said, this is the same fix, only done a little cleaner. I just tested and still didn't have audio first call, like we do now, and the echo was still there.
[HTC Vivid, Raider, Velocity] Garrykd:
OMG!

This is what I've been waiting to hear!

Homeslice you never cease to amaze me. You have the tenacity of a pitbull...great work!

It's like xmas all over again.

I'll wait for the new build and then test.:D
[HTC Vivid, Raider, Velocity] h8rift:
That commit is a way of doing what you did, but in 3 lines. Its identical. Just cleaner
[HTC Vivid, Raider, Velocity] ZeRo2o9:
hi h8 lol :eek:
[HTC Vivid, Raider, Velocity] h8rift:
Yo ;)
[HTC Vivid, Raider, Velocity] h8rift:
Intervigil will be back from vacation next week so I will discuss merging the 1080p vid fix with him.

Also, one xl is almost done for 10.1, and I'm still waiting for device tree to be merged to CM. Hopefully both if those will be done soon and I will continue work on the holiday, including working on 10.1 when intervigil and deck are ready to move their devices forward. 4.2 will very likely take *awhile* to get going, so don't expect that in the near future...but it will come :).
[HTC Vivid, Raider, Velocity] homeslice976:
Sounds good! Hey, was just nosing around and saw that in the msm8660 common files, BoardConfigCommon.mk shows "TARGET_BOARD_PLATFORM_GPU := qcom-adreno200". I thought our board used the adreno220 set? (source 1 source 2)

would changing this improve things for us? I'm not familiar enough with it... and if someone can answer the question excellent, if not, guess I'll start a build and we'll see
[HTC Vivid, Raider, Velocity] jtsurfs:
I could have swore the Vivid had the Adreno220. I even remember trying to load updated drivers when I was on a previous desensed ICS ROM.
[HTC Vivid, Raider, Velocity] homeslice976:
It is..which is why I was confused
[HTC Vivid, Raider, Velocity] RagnarDanneskjold:
I just came here to thank the devs. I love this ROM. I decided to try it so I could patch and run Pdroid. Its actually very stable and visually beautiful.

Thanks! Looking forward to future builds.
[HTC Vivid, Raider, Velocity] LQQKS:
Just cracked my screen :(

Wondering whether I should upgrade to a One XL or buy a new screen....

Finally happy with this phone running CM10 *sigh*

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

running CyanogenMod 10 JellyBean 4.1.2
[HTC Vivid, Raider, Velocity] hovadrive:
Oh hush I know the feeling, I broke mine 2 weeks ago I bought the screen last week and am enjoying my CM10 again
[HTC Vivid, Raider, Velocity] LQQKS:
Where did you get the screen from and how much?

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

running CyanogenMod 10 JellyBean 4.1.2
[HTC Vivid, Raider, Velocity] hovadrive:
Well I live in Jamaica, but I had a friend that was coming from New York ask him to buy it so I couldn't tell. But he got it for around $80
[HTC Vivid, Raider, Velocity] LQQKS:
Ouch I found one on eBay for $55 but for a little more they'll let me upgrade. Thanks anyway :)

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

running CyanogenMod 10 JellyBean 4.1.2
[HTC Vivid, Raider, Velocity] h8rift:
Well, either way, you'll get CM maintained by me haha :)
[HTC Vivid, Raider, Velocity] LQQKS:
Haha good to know.

Do you do just the One X or also the One XL from Telstra?

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

running CyanogenMod 10 JellyBean 4.1.2

---------- Post added at 01:36 PM ---------- Previous post was at 01:05 PM ----------

Telstra One XL = AT&t One X = Rogers One X

( I think) all with dual core

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

running CyanogenMod 10 JellyBean 4.1.2
[HTC Vivid, Raider, Velocity] h8rift:
I do the Evita (One XL / ATT One X)
[HTC Vivid, Raider, Velocity] LQQKS:
\o/ happy days that's what's being delivered

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

running CyanogenMod 10 JellyBean 4.1.2
[HTC Vivid, Raider, Velocity] homeslice976:
gonna test this for a while, but should be able to share tomorrow as long as battery doesn't get crushed :)
[HTC Vivid, Raider, Velocity] Mike S.:
I just flashed this ROM today and also have the problem with the internal SD card not being accessible. Am I correct that a fix has not been implemented yet?

Not a show-stopper except that Camera, Gallery, and Swiftkey3 all require and "SD Card" in order to work.

I have a external SD card that seems to work fine.

Is there anything I can do to help with debugging or testing? I'm a longtime CM user (not developer) on my Cappy and I know this is an Unofficial build, but it's very nice so far. Kudos to the devs.
[HTC Vivid, Raider, Velocity] homeslice976:
bet youre using cwm recovery? flash wcx or twrp recovery, do a factory reset (will wipe internAl), and you should be ok. wish people would stop using our version of cwm, or better yet, someone should fix it
[HTC Vivid, Raider, Velocity] RujinXERO:
I use swiftkey3 and I don't have a sdcard. Am I missing something?
[HTC Vivid, Raider, Velocity] Mike S.:
Yes, that's correct, I was using CWM recovery. I can try flashing twrp recovery and doing a factory reset from there.

When I try and run the app for the first time on this ROM it pops a box and says it requires an SD card to run. I guess it's trying to access my internal_sd which is unavailable.

Thanks for the replies, I will see what I can do.
[HTC Vivid, Raider, Velocity] homeslice976:
Yea our version of CWM has borked partitions from the start. As far as swiftkey, you are having trouble because it requires access to your internal sd (as does the camera), and that's what got borked.
[HTC Vivid, Raider, Velocity] Mike S.:
I flashed twrp recovery and when I tried to run Factory Reset it failed.

Quite a string of "unable to mount" messages.

It does format Cache and Data, but cannot mount /emmc or internal storage.

Thoughts?
[HTC Vivid, Raider, Velocity] homeslice976:
You may need to relock your bootloader, run the ruu, unlock bootloader again, flash a proper recovery, then business as usual. If it won't factory reset - that's your next step. Did you try a factory reset from bootloader? You may wanna try that before taking the RUU route
[HTC Vivid, Raider, Velocity] Mike S.:
I think that's what I'm going to do, re-lock, ruu, then flash the twrp recovery and then try it again. I'll report back if *that* doesn't work. Appreciate your help and suggestions. Thanks!

---------- Post added at 08:18 PM ---------- Previous post was at 07:36 PM ----------

I know it's bad form to quote one's own post, but I wanted to mention that I believe my problem is fixed. I just re-did everything with the exception of using twrp recovery instead of CWM recovery. I had only used CWM recovery because it was what I was most familiar with.

I might suggest updating the OP to indicate in the instructions that it's strongly advised to use a recovery other than CWM?

Again, thanks for the help!
[HTC Vivid, Raider, Velocity] rignfool:
Yeah... H8 has CWM mentioned in the OP...

That needs a fix-in
[HTC Vivid, Raider, Velocity] hovadrive:
Whats new ??
[HTC Vivid, Raider, Velocity] theslam08:
Depends on when your 'new' is. Like when you last read what was 'new' at the time.

Some overview: Some new mic fixes, new oc kernel, and other minor tweaks. Just read. Your the only person who will know what 'new' news is, for you.
[HTC Vivid, Raider, Velocity] haydnlj:
Can't determine from the thread, did the 12/24 update fix a2dp? Issues register doesn't show this, and the current issues in the OP suggests "Audio Skipping" and battery drain while on as the only bluetooth issues. tks in advance
[HTC Vivid, Raider, Velocity] ycode90:
I can't seem to get lte . Preferred network settings won't take nor *#*#info#*#* won't change either . Att Vivid s-on twrp . Everything else is great.
[HTC Vivid, Raider, Velocity] hovadrive:
I meant with the last built 12,24 like gtalk mic
[HTC Vivid, Raider, Velocity] Avidgamer:
If somebody could answer this that's be great.

So, I actually have read all of the posts on this, I've also read everything on MG's old post. I was wondering how the fc issue is? Is it still present? Also, screen tearing, I heard about vsync being required. Also how would this work for me as a daily driver, I basically only listen to music (off an sd card) and use youtube, occasionally play a game.
[HTC Vivid, Raider, Velocity] hovadrive:
I run this for 3 weeks i had no fc no screen tearing , there are nothing thats there that i couldnt live with as a daily for me only thing is gtalk fc when starts a video call or when some one does call you video call it answers and video works but no sound from either way other users have different experience thou like sdcard not showing up . battery drain is a little bit on the bad side but its been working on so go ahead try it out your vivid will lights up lol
[HTC Vivid, Raider, Velocity] jscarano:
Are there the same in-call volume and speakerphone issues with this rom like Pacman rom? thanks
[HTC Vivid, Raider, Velocity] homeslice976:
Yes
[HTC Vivid, Raider, Velocity] jscarano:
Thanks. Must be an issue with the Vivid. I have JB rom on my Rezound and volume is plenty loud.
[HTC Vivid, Raider, Velocity] homeslice976:
Yea, its an issue with our builds. One of the bigger ones we're battling with
[HTC Vivid, Raider, Velocity] Avidgamer:
I really wish I knew how to code, I can maneuver around ubuntu easily enough, but can't get near a cmd terminal without needing help.
[HTC Vivid, Raider, Velocity] DreamPCs:
Hey guys I need help. My vivid was running a custom de-sensed rom on ice cream sandwich but I wiped and flashed per a custom recovery. Neither this rom or any other jellybean rom works for me. It flashes but sits at the boot screen. I've left them sitting at the boot screen for 20 minutes, no dice. I'm s-off. What gives?
[HTC Vivid, Raider, Velocity] XxSHaDoWxSLaYeRxX:
I thought the Att one x was the endeavour.. it might be the international version though correct me if I'm wrong
[HTC Vivid, Raider, Velocity] Apatche69:
Same thing happens to me whenever I tried to flash the stock rom.zip that's floating around somewhere on this site. I'm not sure why it happens either. I guess you could try flashing the boot.img via fastboot first and then flash the .zip as if you were s-on.
[HTC Vivid, Raider, Velocity] h8rift:
The international quad-core one X is the endeavor.

The AT&T One X (poorly named since its actually the One XL) is the evita. the L in One XL is for LTE-enabled.
[HTC Vivid, Raider, Velocity] BTJustice:
Are you guys also flashing the boot.img file after installing the ROM? I like to use the Vivid All-In-One Tool. Get the boot.img file from the ROM and place it in the following folder where you have the AIO tool installed (I'll use C:\Vivid AIO as an example)...

C:\Vivid AIO\Data\Kernels

Make sure to turn on debugging mode prior to connecting your phone with a USB cable.

After you copy boot.img there, open the tool, highlight where it says WITH THIS COMMAND under KERNALS and click the button to FLASH KERNAL.

I like to use ClockWork. After installing the ROM while still in ClockWork, I will flash the kernal then do a backup before rebooting the phone.

EDIT:

Also make sure to install gapps-jb-20121011-signed after installing the ROM.
[HTC Vivid, Raider, Velocity] ZeRo2o9:
Or you could s-off and just flash the zip

Sent from my HTC Vivid 4G
[HTC Vivid, Raider, Velocity] rignfool:
Using CWM will give you partition problems...
[HTC Vivid, Raider, Velocity] BTJustice:
No partition problems I am aware of.
[HTC Vivid, Raider, Velocity] Mike S.:
I experienced problems with partitions after trying with CWM. You can find my posts about it up-thread. Going to TWRP solved my issue. Maybe everyone doesn't have the issue, though. I am S-on if that makes any difference.
[HTC Vivid, Raider, Velocity] h8rift:
Just got the device tree merged to CM. waiting for gerrit permissions and then we'll be back in business.
[HTC Vivid, Raider, Velocity] cwhittl:
So New Build Almost Ready For Consumption?
[HTC Vivid, Raider, Velocity] h8rift:
Nothing has changed on the build yet, but we're talking getting nightlies started in the very near future. Then work can continue :).
[HTC Vivid, Raider, Velocity] camo_flage:
Still learning terms here but what does that mean?

Sent from my PACMAN HTC Raider on the Rogers Wireless Network