yashsingh1/xdaforums huggingface dataset:
[HTC Vivid, Raider, Velocity] theslam08:
Agreed. Exactly my problem. SD not mountable.

I think whats going on here is the dir structure changed from ICS to JB (like for my app "my backup pro" would use something like /mnt/sdcard/ext_sd and it worked on ICS). Now the sd (the real extra card) is at /storage/sdcard1. Is the USB mount mounting that path (like the storage_lists.xml)? Maybe im thinking too simple, but I feel like that is the problem, the mounting is not for the correct directory (not there = not going to mount. because I can mount internal no problem, not the sd). Sorry if this was already looked over by devs just thinking aloud.
[HTC Vivid, Raider, Velocity] homeslice976:
Possibly. It actually looks like the correct mount points are /mnt/sdcard and /mnt/external_sd (and it looks like /mnt/sdcard is the only /mnt being called in storage_list.xml currently)

I have a build going now with storage_lists.xml set with the additional external_sd mount point, and I'll see what happens. In case anyone else with a faster build machine wants to try, here's what storage_list.xml looks like now on the first try)

<StorageList xmlns:android="http://schemas.android.com/apk/res/android">
<!-- removable is not set in nosdcard product -->
<storage android:mountPoint="/mnt/sdcard"
android:storageDescription="@string/storage_internal"
android:primary="true"
android:removable="false" />

<storage android:mountPoint="/mnt/external_sd"
android:storageDescription="@string/storage_sd_card"
android:primary="false"
android:removable="true" />
</StorageList>

Edit: looking at vold.fstab, this might should be "@string/storage_sdcard" for internal, and "@sting/storage_external_sd" for external (unless that is truly just a description, in which case it shouldn't matter?). We shall see

Or maybe the mount points need to be /storage/sdcard0 and /storage/sdcard1. Lol, looks like I know what I'm playing around with today

Also - looks like h8 was busy last night. Looking at htc-msm8660's git, he:

Increased USB transfer speed, enabled CRT animation, added a power power profile (which looks like it references higher clock speeds?), and some other adjustments

Edit: one last thing, the possible audio fix I posted yesterday evening must have been placebo. ess.boyer is exploring some other possible leads atm

CRT animation is cool, and USB transfer def seems faster.

Maybe this is what the power power profile does? Notice it no longer says that battery stats are unavailable or whatever

It's that way in both PAC and PA (builds will be going up shortly) - I assume it's there in CM as well.
[HTC Vivid, Raider, Velocity] XxSHaDoWxSLaYeRxX:
What CRT animation? I'm on PACman btw
[HTC Vivid, Raider, Velocity] lucasryan:
CRT stands for Cathode Ray Tube.... When you turn them off, then, the picture kind of zaps out of existence

Try google, it should show you what it looks like
[HTC Vivid, Raider, Velocity] XxSHaDoWxSLaYeRxX:
ik what it looks like, had many crt moniters+tvs, and had wajees rom. but when did they add this

---------- Post added at 08:33 PM ---------- Previous post was at 08:10 PM ----------

nvm, it was in the new update i just noticed.
[HTC Vivid, Raider, Velocity] lucasryan:
I couldnt tell with the ?....figured you was asking what it was
[HTC Vivid, Raider, Velocity] h8rift:
Yes power profile was to fix battery data is unavailable message

Also, jellybean 4.1 changed mount points. It is now /storage/sdcard#. 0 being internal and 1 being external.
[HTC Vivid, Raider, Velocity] homeslice976:
Right. I think what most are curious about is why only sdcard0 mounts to your computer. And why /sdcard0/ext_SD only has a small percentage of what is actually on sdcard1?
[HTC Vivid, Raider, Velocity] theslam08:
So im guessing

<storage android:mountPoint="/mnt/external_sd"

Should be changed to

<storage android:mountPoint="/mnt/sdcard1"

If that should work, Ill probably decombile framework and change that, for the time being
[HTC Vivid, Raider, Velocity] homeslice976:
K..but I tried that too
[HTC Vivid, Raider, Velocity] h8rift:
Pretty sure i found how to squash that nasty wakelock eating battery from bluetooth. Lemme test and verify....If it works i'll put up a build with all the newest stuff tonight / tomorrow.

-h8
[HTC Vivid, Raider, Velocity] snorkle:
I love you... marry me ?
[HTC Vivid, Raider, Velocity] Bl@ze:
man jb on this phone is really bring ppl together
[HTC Vivid, Raider, Velocity] meatwad0222:
Only if I get to bare his children...lol
[HTC Vivid, Raider, Velocity] snorkle:
thats fine im not going to pay for child support though.
[HTC Vivid, Raider, Velocity] meatwad0222:
Deal
[HTC Vivid, Raider, Velocity] Gene Poole:
Thanks MG and Homeslice. That worked. Building now.

Edit: spoke too soon:

During "repo sync" with new local_manifest.xml:

error.GitError: htc-msm8660/android_device_htc_holiday rev-list ('^a11571e895ec402c66b74da8e1f23046251c5642', 'HEAD', '--'): fatal: bad object HEAD
[HTC Vivid, Raider, Velocity] homeslice976:
If you just did the git reset, try mg's other suggestions, then create your local_manifest.xml
[HTC Vivid, Raider, Velocity] Gene Poole:
No dice.

I finally gave up, nuked the cm10 tree completely, re-init-ed and re-synced, copied the new manifest, and synced but I get the same damn error:

error.GitError: htc-msm8660/android_device_htc_holiday rev-list ('^a11571e895ec402c66b74da8e1f23046251c5642', 'HEAD', '--'): fatal: bad object HEAD
[HTC Vivid, Raider, Velocity] Cor-master:
Do you have to compile it or is there a flashable zip?
[HTC Vivid, Raider, Velocity] theslam08:
First post first line under Installation Instructions, download link has been there.

The other posts your reading about compiling, that you can do too but the link to install (already compiled) has been on OP since he started this new topic.
[HTC Vivid, Raider, Velocity] exynos5250x:
FYI, synergye/IOmonster got the vivid to where it was on cm9/cm10, mg2195 barely compiled it...
[HTC Vivid, Raider, Velocity] h8rift:
regardless, he had a hand in it. No need to be nasty ;/ (I'll add IOmonster, didn't know he was involved as I just got here).
[HTC Vivid, Raider, Velocity] meatwad0222:
Must be a wcx fan...jk...get out a here with that nonsense
[HTC Vivid, Raider, Velocity] sadoway:
Call volume is also very low. Rican barely hear it on max volume. I. A loud place I could usually hear it. There is no way I would hear a conversation on max volume with this rom. This is a deal breaker for me. But I'll keep it for a few more days. Then I'll wait for updates.

Chrome also glitches out.
[HTC Vivid, Raider, Velocity] meatwad0222:
Dude...if you take the time to read the original post you would know that that was already stated
[HTC Vivid, Raider, Velocity] sadoway:
I'm not talking about the mic volume. I was talking about the speaker. Unless I miss understood this is not what was mentioned. Sorry if I miss understood.

I'm also not using an att branded device.

It says in call mic. Not speaker. So I did read an my issue still seems unmentioned. I've had this problem with other ROMs aswell
[HTC Vivid, Raider, Velocity] meatwad0222:
Sorry for the misunderstanding...yeah....that's always been a vivid problem....I'm sure h8 will figure it out...he did something in a week nobody could do
[HTC Vivid, Raider, Velocity] LQQKS:
Go SMS crashes when trying to create a new text :(

and SD card is not accessible

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

running CyanogenMod 10 JellyBean 4.1.2
[HTC Vivid, Raider, Velocity] sadoway:
The ROM for the most part runs super well. Ones everything works I think this will be a daily for alot of people.

Does anyone know where I can get a play store that has the device restrictions modified
[HTC Vivid, Raider, Velocity] lucasryan:
Are you talking about being able to download the apps? If so, h8rift talked about that in the opening post about downloading JB Google Apps (make sure they are no later than October, you dont want 4.2 gapps)
[HTC Vivid, Raider, Velocity] XxSHaDoWxSLaYeRxX:
cant wait till i can make calls with this !!

---------- Post added at 06:54 PM ---------- Previous post was at 06:52 PM ----------

same.. cant rly download much
[HTC Vivid, Raider, Velocity] sadoway:
I didn't download Jb gapps
[HTC Vivid, Raider, Velocity] h8rift:
need to update fingerprint. I'll get on it soon :)
[HTC Vivid, Raider, Velocity] XxSHaDoWxSLaYeRxX:
same here. tried to download go backup to grab my texts, etc and it says its incompatible xo

@h8 ok man thanks :)

for now il see if changing the build prop will help
[HTC Vivid, Raider, Velocity] sadoway:
http://xdaforums.com/showthread.php?t=1837875

I'm just gonna do this for now

Update:

Couldn't get this to work. Guess I'll just have to wait. I wish I backed up everything lol. Only backed up some stuff

Should add. The battery life seems good. Went all day and night without any top ups.
[HTC Vivid, Raider, Velocity] Eddy130306:
How do you change mount points ?
[HTC Vivid, Raider, Velocity] theslam08:
Requiring the decompilation of framework-res.apk then going into res > xml > storage_lists.xml and changing in there. Then the apk needs to be recompiled and it should be good to go.

BUT! A great editor here, homeslice, already confirmed he tried the fix I was hoping would 'fix' it, and said it did not work. Read the post after mine, unfortunately. We still have to wait. In the mean-time, a pain, but I just boot into recovery if I need USB - SD mount.
[HTC Vivid, Raider, Velocity] homeslice976:
I have managed to bind the external SD mount to a folder on then internal successfully. But after I bind it, internal wont mount to the computer so you can't get to internal or external. Til you reboot, but the the bind is broken.
[HTC Vivid, Raider, Velocity] Eddy130306:
Alright thanks for the feedback!
[HTC Vivid, Raider, Velocity] h8rift:
Okay, so apparently bluetooth is acting weird with the fix I applied.

Good news: battery drain ceases while bluetooth is off.

Bad news: battery drain seems to happen while bluetooth is on.

Even greater news: Working on getting us up to CM for nightlies :).

Next build (hopefully from Jenkins) will contain several fixes:

* USB transfer rate increase

* Capacitive lights work w/o auto-brightness

* the above Bluetooth workaround for battery drain

* Power Profile so battery stats show up correctly

* Android CRT screen-off animation

More to come,

Thanks!

-h8
[HTC Vivid, Raider, Velocity] ZeRo2o9:
Sounds good haven't updated since the 12-14 build
[HTC Vivid, Raider, Velocity] :
Is that Leroy Jenkins ?
[HTC Vivid, Raider, Velocity] LQQKS:
I think

http://jenkins.cyanogenmod.com/job/android/
[HTC Vivid, Raider, Velocity] h8rift:
New build is up on the project page for download!

Also, have a great Holiday everyone! (pun intended :))

-h8
[HTC Vivid, Raider, Velocity] ZeRo2o9:
Thanks h8 have a great Christmas and new years thanks for all the work
[HTC Vivid, Raider, Velocity] GlowingStar:
Not sure why but the new build doesn't have wifi working.
[HTC Vivid, Raider, Velocity] mg2195:
Try flashing the kernel again?
[HTC Vivid, Raider, Velocity] GlowingStar:
Got it. Thanks man

---------- Post added at 08:16 PM ---------- Previous post was at 07:41 PM ----------

Actually, it's not working. I flashed the kernel as you said but no go.
[HTC Vivid, Raider, Velocity] meatwad0222:
Can I just flag on top of the old build?
[HTC Vivid, Raider, Velocity] Brand New:
Wow this new build is awesome. :good:
[HTC Vivid, Raider, Velocity] meatwad0222:
How so...I was wondering if I should take the plunge
[HTC Vivid, Raider, Velocity] Brand New:
To answer your other question, do normal wipes before flashing. The latest build runs great, it's almost daily-driver material!
[HTC Vivid, Raider, Velocity] Godrin:
Thanks for your big contribution in time and effort these past months. Much appreciated.

Happy Christmas
[HTC Vivid, Raider, Velocity] mg2195:
Are you s-on of s-off? Try a full wipe, flash kernel through fastboot (if s-on), then flash ROM

WiFi is working flawless on the latest build for me...so its not the ROM
[HTC Vivid, Raider, Velocity] LQQKS:
Battery life seems short and I haven't even touched bt yet

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

running CyanogenMod 10 JellyBean 4.1.2
[HTC Vivid, Raider, Velocity] mg2195:
Let the rom settle in before complaining about battery...its gonna take a couple charge cycles...the phone goes on overload after flashing a ROM as it rebuilds its cache directory, scans for any and all media (can often get stuck causing battery drains), an syncs all your accounts...as a rule of thumb I never worry about battery life of a ROM until I've been running it for a few days

As of right now I've dropped 40% in about 3 hours...but that's with an hour and half of screen on time, and about an hour or more of music...so in my opinion that's not bad...I'll get about 3 1/2 hours screen on time with the first charge cycle...and after a few days it will probably level out to about 4 1/2 hours screen on time...my usually battery life

Also...I listen to my music with some studio monitor headphones (not Tony ear buds) so I'm pretty sure those are more power hungry then the average pair of headphones

Anyways...solid build h8! Running nice and smooth :D couldn't be happier...gonna try and get some log cats of the DSP issue later and see if I can figure amything out...as soon as that's fixed this will be a perfect ROM for me...but for now its 99.99% perfect :P
[HTC Vivid, Raider, Velocity] LQQKS:
Cool thanks mg, I don't think I had that issue with the older build, but will happily run this as my daily :)

merry Xmas guys and a great 2013

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

running CyanogenMod 10 JellyBean 4.1.2
[HTC Vivid, Raider, Velocity] GlowingStar:
No idea why the wifi isn't working for me. The previously build worked for me. I even wiped my internal storage. I am S-ON
[HTC Vivid, Raider, Velocity] meatwad0222:
Did u flash the kernel thru fast boot?
[HTC Vivid, Raider, Velocity] GlowingStar:
Yes. I can run the 20121812 version perfectly fine but the wifi on 20122412 build doesn't work.
[HTC Vivid, Raider, Velocity] meatwad0222:
I dunno then I've got WiFi working
[HTC Vivid, Raider, Velocity] GlowingStar:
Did you do anything special? Please list the steps. Like what you did when you were flashing this rom.
[HTC Vivid, Raider, Velocity] mg2195:
Best advice I can give is this...

Fast boot flash kernel

Full system wipe

Flash ROM

Fast boot flash kernel

Reboot

As for me...I'm s-off...if your comfortable with it then I suggest going s-off...hat way all you have to do is wipe and flash the rom
[HTC Vivid, Raider, Velocity] zippox180:
A lot of people get really nervous about going s off because of the wire trick but it is really quite easy. It makes everything a little easier when it comes to roms. But always wipe and delete cache partition and i wipe dalvik as well. I also wipe internal sd but i have everything on my external. This build has been working flawlessly for me. Wifi has no issues and battery has been a bit better than before. Great work never thought i would have jb on the vivid.
[HTC Vivid, Raider, Velocity] big_yute:
Awesome work guys. Quick question, I am only able to adjust the camera to only 3mp for still images after this flash. Is this a change in the latest update or is it just a bad flash I was my end. Yes as always I do a full wipe when flashing a new rom.
[HTC Vivid, Raider, Velocity] :
I'm able to change up to 8mp on this build.
[HTC Vivid, Raider, Velocity] mg2195:
I've got 8mp...would a showed a screenshot...but it won't save while the camera is open
[HTC Vivid, Raider, Velocity] big_yute:
Fair enough, will wipe and flash it again in the morning before the kids wake up..

Merry Christmas fellas. :)
[HTC Vivid, Raider, Velocity] snorkle:
anyone know what i got to do to get the Voicemail working?

Merry christmas all!
[HTC Vivid, Raider, Velocity] ZeRo2o9:
Go to dialer then hit menu then settings then voicemail number then add your phone number
[HTC Vivid, Raider, Velocity] snorkle:
is it just my phone number or is it different? cause now it wants me to enter a password that i have never set up before.
[HTC Vivid, Raider, Velocity] i3am5not8real13:
im on att and dialed *#61# on phone to get my viocemail number, dont know about other carriers

Sent from my HTC PH39100
[HTC Vivid, Raider, Velocity] ptclik85:
I was wondering if bluetooth actually worked on this rom, because I flashed the pac-man rom with working bluetooth and all I heard was a crackling sound.
[HTC Vivid, Raider, Velocity] mg2195:
Its been stated more than once that it dies not yet work for audio
[HTC Vivid, Raider, Velocity] swatty43:
So I have been using this rom for a couple of weeks now, not having BT working/not having it for audio was completely fine. Then of course for Christmas, my brother got me Jaybird BT headphones haha so now I cant WAIT till BT works for audio, What are the chances? lol.
[HTC Vivid, Raider, Velocity] tromoly:
Is there any reason why text messaging keeps breaking nomatter the JB version I'm using? Tried PACman first and texting quit sending messages, went back to Virtuous Inquision and everything worked, moved to CM10 and texting is broken again. Data works, Wifi works, even Wifi tethering works, but texting keeps saying "Message not sent". Any reason why this keeps happening on Jelly Bean ROMs?
[HTC Vivid, Raider, Velocity] ess.boyer:
Fix your APN settings.
[HTC Vivid, Raider, Velocity] tromoly:
Nope, the APNs are correct. Using ATT LTE (pta) I get data, but no MMS. Trying ATT (wap), I get MMS but no data.

I'm jumping ship back to ICS, it's not worth my time to try and fix it and not worth you guy's time to deal with my issues. Everything else was working fine, best of luck with the project.
[HTC Vivid, Raider, Velocity] zippox180:
It's totally worth your time man cmon. Att lte has an mms apn as well take a look http://rootzwiki.com/topic/31135-att-apns-for-custom-roms/

Use apn 3 and 5
[HTC Vivid, Raider, Velocity] agentfusion:
I don't know if this helps any, but I'm using the PA build based on this CM build and with the 1220 build I had the same insane battery drain as everyone else so I flashed 1214 and compared them. First, everything works in 14. Literally everything. Even tethering. I'm using an HTC Vivid from July, which came with ICS.

My battery life is the best it has ever been.

Now, here's what I noticed: in performance with the CPU set to on demand, it constantly shot straight up to max clock in 20, where in 14 it often stays at 192 unless something needs processing power. I tried every single thing I could think of including downloading the ROM multiple times, using different external SD cards, flashing from internal, flashing without gapps, etc. Every single time the clock maxed itself and pretty much stayed there. In 14, this didn't happen.

So basically something is demanding CPU time consistently, something from the ROM itself. The only thing I can think of at this point is to shoehorn emdebian onto it to be able to install tools like 'top' if it's not already present and see wtf is eating so much CPU.

Since 14 works flawlessly for me, I'm just leaving it alone though. Just wanted to share the observation with the data I gathered to see if it's helpful.

(Note: I didn't check the version numbers and I'm going from memory so if they're not 14 & 20 you guys can figure out which I meant. Also, my device is S-ON since I forgot to mention that.)
[HTC Vivid, Raider, Velocity] meatwad0222:
Your Bluetooth works, since you said everything? Just wondering cause I got a headset for Christmas.:D
[HTC Vivid, Raider, Velocity] h8rift:
PA 12/20 doesn't have the bluetooth drain fix... That's why your CPU is floored and battery sucks.

CM 12/25 has those fixes and more.
[HTC Vivid, Raider, Velocity] meatwad0222:
Wait...where is 12/25
[HTC Vivid, Raider, Velocity] LQQKS:
I think he means 1224

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

running CyanogenMod 10 JellyBean 4.1.2
[HTC Vivid, Raider, Velocity] ClippinWings:
Has anyone else noticed that many of the issues people are mentioning are the same issues we experienced with the original ICS ROMs?

Take the low volume issue... Pirate Ghost had the same issue with the initial version of Rum Float... but it was fixed in subsequent versions...

Could any of those fixes be applied/modified and applied here?
[HTC Vivid, Raider, Velocity] h8rift:
PM me links to these fixes and i'll definitely look into it. Waiting on the team to merge to CM still before I continue further work on it.

I've been putting some One XL specific CM10.1 stuff in the last day or two. Its almost done for that phone then i'll be back full force on Holiday. I'm ping-ponging back and forth for both devices atm :).

Honestly, once this thing has stable 10, there is kernel, camera, and possibly RIL changes and this bad boy should be able to do 10.1 as well. The kernel stuff will take *awhile* though....this kernel is super old, but 8660s in general are the secondary focus across CM after the 8960/exynos5/exynos4/Nexus devices are going on 10.1 (well over half-way done), so 8660s will be getting 10.1 love in the near future. :)

Thanks guys!

-h8
[HTC Vivid, Raider, Velocity] agentfusion:
Is there a 12/25 (24?) For PA now?

Also

Thank you for this. Having jb on my vivid makes me very happy. I have begun using Google now for pretty much everything but not being able to update the app in ics and having a card telling me to update constantly was annoying. Now I have jb thanks to you and get to enjoy proper GN and can update whenever.
[HTC Vivid, Raider, Velocity] homeslice976:
Pa has not been updated. PAC has. This is the cm thread :)
[HTC Vivid, Raider, Velocity] agentfusion:
I know it's the CM thread. Every thread for the roms based on CM you guys keep saying to watch this thread for bugs to be fixed, etc.
[HTC Vivid, Raider, Velocity] ZeRo2o9:
Still nice to hear something is being done for the vivid :)
[HTC Vivid, Raider, Velocity] ClippinWings:
I'll see what I can dig up next time I'm on a computer.... a bit tough from the tapatalk app.
[HTC Vivid, Raider, Velocity] camo_flage:
I know its a little to early to ask this but when will project butter be implemented?

Sent from my HTC Raider on the Rogers Wireless Network
[HTC Vivid, Raider, Velocity] mg2195:
Rule #1 of cyanogenmod...never ask for ETAs

But to answer your question...I think its already in there
[HTC Vivid, Raider, Velocity] h8rift:
It will be a bit of time...

Project Butter = Triple Buffering + Hardware VSync.

Vsync is definitely not implemented yet, and im not sure if triple buffering is implemented yet or not.

It is all kernel based and is really difficult to implement due to HTC's molestation of kernels. (its getting better...but HTC 8960s are just now getting vsync enabled in cm 10.1).
[HTC Vivid, Raider, Velocity] Brand New:
Change your CPU governer to interactive, and watch that butter.
[HTC Vivid, Raider, Velocity] ess.boyer:
In case anyone is interested, I dimmed the capacitive backlights by changing the "full brightness" current draw limit from 40mA to 20mA. Still plenty bright, but uses half the power.

You can play along at home by changing line 4184 in board-holiday.c (/kernel/arch/arm/mach-msm/board-config.c) from 40 to 20 (or any other value you'd like. The "low power" value is 6, so presumably anywhere between 3-100 would "work").
[HTC Vivid, Raider, Velocity] RujinXERO:
not sure my PMs are getting through or not since they are not showing up in sent.. but i commented on the proximity sensor issue and also tried PMing h8.. but just in case that didnt go through i'm just covering all bases.. i found this while googling and it could be a possible fix to the proximity sensor issue.. http://xdaforums.com/showthread.php?t=1882725
[HTC Vivid, Raider, Velocity] homeslice976:
Has anyone confirmed the issue? I haven't had any trouble with the prox sensor
[HTC Vivid, Raider, Velocity] pod0087:
Personally I'd like the capacitive backlights to work within the autobrightness custom levels instead of being hardcoded to switched on (since the latest public build). I don't really see why people need them on as I'm sure they know the location of the buttons by now and they can save power by disabling them...but each to their own.