yashsingh1/xdaforums huggingface dataset:
[HTC Vivid, Raider, Velocity] rignfool:
Re: [ROM][JB][4.1.2]Unofficial PAC-man v19.3.0[02.05.13]

It seems to get stuck? at a frequency...

I can unstick it... but it gets stuck again...
[HTC Vivid, Raider, Velocity] XxSHaDoWxSLaYeRxX:
Re: [ROM][JB][4.1.2]Unofficial PAC-man v19.3.0[02.05.13]

Had that problem also. Using smartass. Just after rebbot. Change governed then switch back to smartass to fix

---------- Post added at 02:31 AM ---------- Previous post was at 02:30 AM ----------

Same problem.
[HTC Vivid, Raider, Velocity] rignfool:
Re: [ROM][JB][4.1.2]Unofficial PAC-man v19.3.0[02.05.13]

Rebooted before I went to sleep...

6 and a half hours at 1.18... overnight...

On smartass

I set all my kernel parameters with init.d scripts... so it isn't system tuner...
[HTC Vivid, Raider, Velocity] homeslice976:
Re: [ROM][JB][4.1.2]Unofficial PAC-man v19.3.0[02.05.13]

Mine was scaling properly. I'll double check it in a few hours though
[HTC Vivid, Raider, Velocity] rignfool:
Re: [ROM][JB][4.1.2]Unofficial PAC-man v19.3.0[02.05.13]

I have used both the one packaged with the ROM... and the one released a day earlier...

And when I opened tapatalk... I saw a rom labeled PAC 19.9.0
[HTC Vivid, Raider, Velocity] homeslice976:
Re: [ROM][JB][4.1.2]Unofficial PAC-man v19.3.0[02.05.13]

Probably the 4.2 cm10.1 base they started the last few days. We won't see that.. at least for a while anyway

After an hour and 30minutes on smartass mine appears to be scaling and sleeping as expected
[HTC Vivid, Raider, Velocity] rignfool:
Re: [ROM][JB][4.1.2]Unofficial PAC-man v19.3.0[02.05.13]

Hmm...

Are you undervolting?

If so... how far?
[HTC Vivid, Raider, Velocity] homeslice976:
Re: [ROM][JB][4.1.2]Unofficial PAC-man v19.3.0[02.05.13]

Not at the moment
[HTC Vivid, Raider, Velocity] XxSHaDoWxSLaYeRxX:
Re: [ROM][JB][4.1.2]Unofficial PAC-man v19.3.0[02.05.13]

You have to screw with the settings a bit to unstick it. I recommend kernel tuner. Much more clean interface them system tuner IMO. I set cpu0 to smartassV2 and cpu1 to conservative. Make sure both cores are on different governers or else it gets stuck. At least for me. And I uv'ed a crap load. Have my frequencies uv'ed at least -100 MV .

---------- Post added at 12:44 PM ---------- Previous post was at 12:43 PM ----------

You can view CPU states in kernel tuner also. Check it out. Replaced CPU spy and system tuner for me
[HTC Vivid, Raider, Velocity] rignfool:
Re: [ROM][JB][4.1.2]Unofficial PAC-man v19.3.0[02.05.13]

It appears the problem is when undervolting...
[HTC Vivid, Raider, Velocity] homeslice976:
Re: [ROM][JB][4.1.2]Unofficial PAC-man v19.3.0[02.05.13]

I've been UV 50mV at every freq for an hour now and its still scaling and sleeping properly. So the problem is coming from something else
[HTC Vivid, Raider, Velocity] jtsurfs:
Re: [ROM][JB][4.1.2]Unofficial PAC-man v19.3.0[02.05.13]

I have had no issues with getting stuck at any frequency and I am really undervolted. What I/O scheduler are you using?
[HTC Vivid, Raider, Velocity] camo_flage:
Re: [ROM][JB][4.1.2]Unofficial PAC-man v19.3.0[02.05.13]

Extreme noob when it comes to this. So say when the processor is running at 132 mega hertz and the voltage is 812 to under clock it 25 MV what would I set it too

Sent from my PACMAN HTC Raider on the Rogers Wireless Network
[HTC Vivid, Raider, Velocity] homeslice976:
Re: [ROM][JB][4.1.2]Unofficial PAC-man v19.3.0[02.05.13]

787.5
[HTC Vivid, Raider, Velocity] camo_flage:
Re: [ROM][JB][4.1.2]Unofficial PAC-man v19.3.0[02.05.13]

And I would minus 25 from all the other voltages too right?

Sent from my PACMAN HTC Raider on the Rogers Wireless Network
[HTC Vivid, Raider, Velocity] XxSHaDoWxSLaYeRxX:
Re: [ROM][JB][4.1.2]Unofficial PAC-man v19.3.0[02.05.13]

If you wanted
[HTC Vivid, Raider, Velocity] jtsurfs:
Re: [ROM][JB][4.1.2]Unofficial PAC-man v19.3.0[02.05.13]

Homeslice, I assume you will be merging h8rifts Bluetooth updates into PAC pretty soon?:D
[HTC Vivid, Raider, Velocity] homeslice976:
Re: [ROM][JB][4.1.2]Unofficial PAC-man v19.3.0[02.05.13]

Building now actually :)

Just restarted the build to include his BT tethering fix as well..which according to him hits battery way less than WiFi hotspot
[HTC Vivid, Raider, Velocity] rignfool:
Re: [ROM][JB][4.1.2]Unofficial PAC-man v19.3.0[02.05.13]

Is that build including a new kernel?
[HTC Vivid, Raider, Velocity] homeslice976:
the bt fix is in part of what becomes the ramdisk in boot.img, and the kernel (zimage) part of boot.img will include OC up to 1.72. So boot.img will need to be flashed.

I'm running the new build now. BT tethering definitely works, verifying other stuff now (not that I doubt h8rift, just doubt my implementation of his awesomeness lol)
[HTC Vivid, Raider, Velocity] XxSHaDoWxSLaYeRxX:
Re: [ROM][JB][4.1.2]Unofficial PAC-man v19.3.0[02.05.13]

Lmao, nice
[HTC Vivid, Raider, Velocity] sadoway:
Re: [ROM][JB][4.1.2]Unofficial PAC-man v19.3.0[02.05.13]

My jambox has been so lonely! He will be happy
[HTC Vivid, Raider, Velocity] Wolfhawke:
So is this a case of patience - give me a day to find bugs, or is this hot and ready?...I can live with the volume problem on BT, it's just the regular phone audio that sucked and caused me to revert back to ICS.
[HTC Vivid, Raider, Velocity] homeslice976:
I was waiting on h8 to put out his build - his fixes, didn't want to spoil it :) Thanks h8rift!

OP updated. BT tethering confirmed working, I'll need others to confirm the rest of the BT functionality as I can't find my one and only BT device :)
[HTC Vivid, Raider, Velocity] jtsurfs:
I am flashing now and will report shortly on BT. :good:
[HTC Vivid, Raider, Velocity] h8rift:
Lol thanks ;). I literally left bt on for over an hour and didn't drop one percentage of battery. This is how bt is *supposed* to be :). Now this will change as you use devices on it, but drain should be normal if not better than what was on Sense.

Bluetooth calling works, but gets crackily the farther you are away from the device (duh, thats how bluetooth works...its short range).

But man....Bluetooth music....holy ****. It sounds amazing.

EDIT: The method i employed previously (incorrectly) that turned on BT but that was it....it was eating approx 87% CPU at all times, causing the incredible drain (You should notice an incredible amount of lagginess removed going forward because of this).

To summarize the fix.....I couldn't get the tried and true method to initialize /dev/ttyHS0. After a month of working on it off and on....i found the permissions were just not called early enough that /dev/ttyHS0 wasn't opened up and ready for bluetooth to be initialized. Then i removed my (incorrectly used, dont ever do it!) hci-kickstart service and it was able to initialize correctly and with the right amount of battery usage. the msm_hs_serial_dma wakelocks no longer appear in BetterBatteryStats, and now we're in business ;).

Enjoy!
[HTC Vivid, Raider, Velocity] homeslice976:
That is absolutely wonderful. I'd have never even known where to start looking for that one - I was leaving it for the pro ;)
[HTC Vivid, Raider, Velocity] sadoway:
So awesome. Yay music. Works perfect for me so far!!!
[HTC Vivid, Raider, Velocity] ess.boyer:
Hey Homeslice,

For those of us playing along at home, are there any necessary changes to the local_manifest to bring in all your changes (including the 4.2 camera etc)? I haven't done a build in a while. Perhaps you could post the latest & greatest manifests? I think my PAC manifest might be out of date and not updating.
[HTC Vivid, Raider, Velocity] homeslice976:
tbh that stuff has all been done locally after the build completes. Haven't had a chance to add it to source to be built along with it. Also, I don't have any of the device repos forked, so nothing (that's not kernel related) has been committed. I may work on that later. I'm currently still syncing to msm8660 git (except for the kernel).
[HTC Vivid, Raider, Velocity] jtsurfs:
BT connected to a car works perfectly. Just had to go to a meeting which required driving, paired my phone and checked voicemail. No crackle this time. haha
[HTC Vivid, Raider, Velocity] Wolfhawke:
Bluetooth works good on Plantronics Voyager Pro+

Hey homeslice and h8rift! Bluetooth works as it should with Plantronics Voyager Pro+ headset, good sound, no jump/skips on music playback and people can hear me just fine. Battery consumption is about par for JB (as in need to find charger/external battery 2x in 24 hrs...)

We still have a problem with soft volume on calls, but compared to the phone speaker itself, it's minor and trivial...

Thanks so much h8rift for finding the answer to the bluetooth issue, you made my day!:p
[HTC Vivid, Raider, Velocity] rignfool:
Also... my liveview paired fine with my phone and connected beautifully
[HTC Vivid, Raider, Velocity] homeslice976:
Apparently I forgot to include the audio fix in this build. For those who don't know, this is for non in call audio. Makes audio sound less distorted at high volume

http://www.mediafire.com/?nu27bzzpmcw2c67
[HTC Vivid, Raider, Velocity] My Fault:
has anyone been able to get ATT Visual Voicemail to work with this rom? It sets it up, however when i try to listen to a voicemail it tells me "Could not play message. Please try again later or call Voicemail"
[HTC Vivid, Raider, Velocity] bsaman:
Yes, it works for me. Have you tried calling the voicemail to see if that sets off a trigger?
[HTC Vivid, Raider, Velocity] My Fault:
it makes you call the voicemail in the beginning when you set it up. And i call the voicemail to listen to messages because it won't play them.

and when i delete them when i call the voicemail, it is deleted from my visual voicemail list. So, i really don't understand it.
[HTC Vivid, Raider, Velocity] homeslice976:
Just shattered my $*#&@&$*-$ screen

Damn it...
[HTC Vivid, Raider, Velocity] lucasryan:
yea it sucks ass...i did the same thing a couple months ago and had to pay the 200$ for the insurance to get another one...so i have another vivid here that i been meaning to order the lcd and digitizer but havent yet..just lazy when i have the other one lol...but i sooo feel the stress and aggravation homie :/
[HTC Vivid, Raider, Velocity] ZeRo2o9:
that sucks man:(..i dropped mine and cracked the bottom left corner but its small enough not to go over the screen or the soft key buttons lol
[HTC Vivid, Raider, Velocity] camo_flage:
Will the audio fix work on CM10?

Sent from my PACMAN HTC Raider on the Rogers Wireless Network
[HTC Vivid, Raider, Velocity] homeslice976:
It should. but again - it's just for volumes outside of in call volume (i.e. music). The in call volume problems will not be fixed with this fix. Not only this but some people reported that it did nothing, but it definitely makes music sound better at higher volumes to me.
[HTC Vivid, Raider, Velocity] XxSHaDoWxSLaYeRxX:
Not too hard to fix yourself..
[HTC Vivid, Raider, Velocity] jtsurfs:
Looks like a LCD and digitizer are around $60 on ebay. Sorry to hear about your phone. I can pitch in for the screen if you feel like you can change it yourself.
[HTC Vivid, Raider, Velocity] homeslice976:
You guys are too kind. And you've both already pitched in so no worries there. I imagine ill get a new LCD/dig combo cause I'm not ready to quit on the vivid. At the same time I may go ahead and use that upgrade I've been due for (was really hoping to hold on to it for a little while longer though lol)
[HTC Vivid, Raider, Velocity] XxSHaDoWxSLaYeRxX:
I got it around $20 off amazon
[HTC Vivid, Raider, Velocity] My Fault:
Don't give up on the vivid for us yet! lol, the in call volume is the only thing left! I'd be happy to help as well.
[HTC Vivid, Raider, Velocity] Xemods:
ok so i downloaded this stuff and wth is up with the texting not working i got to text i like everything else
[HTC Vivid, Raider, Velocity] XxSHaDoWxSLaYeRxX:
Check your APN settings. Only problems I have is low quality MMS images.
[HTC Vivid, Raider, Velocity] homeslice976:
You are the first person to report anything like this in any version of the ROM. So it's something you've installed or restored that's not playing nicely
[HTC Vivid, Raider, Velocity] rignfool:
I recommend a reflash
[HTC Vivid, Raider, Velocity] homeslice976:
He posted the same problem in the PA thread, which leads me to believe he didn't fully wipe, or he keeps restoring/installing something that's not gonna work..
[HTC Vivid, Raider, Velocity] lucasryan:
Just been running the newest release for a couple days now....and have only used interactive for a day, and badass for a day....and am gonna try smartass tomoro with the same voltage that ive been running as before and have been getting great batt usage!! One ? i had, if you have the time to kinda explain the diff in the governors? I know the diff in koz's kernel and remember somewhat of how he explained it without going back and reading his definition in them...but didnt know if it could kinda be based off his explanation though, and you have couple more choices too!! So just if ya get the time to kinda briefly explain the diff....would appreciate it!! Hope ya havent in the past couple days as i havent read the last few pages since the new release...smh sorry
[HTC Vivid, Raider, Velocity] homeslice976:
This thread is great - excellent detail about all the different govs and schedulers

http://xdaforums.com/showpost.php?p=26884865&postcount=2
[HTC Vivid, Raider, Velocity] XxSHaDoWxSLaYeRxX:
Any chance to integrate hot plug governer? Also could you point in the right direction to start compliging a jb kernel for this device.
[HTC Vivid, Raider, Velocity] Xemods:
Is there gonna be a new ROM called slimbean 4.2 for HTC vivid released soon
[HTC Vivid, Raider, Velocity] homeslice976:
Mg said he was gonna try to get slimbean together. I'm gonna start looking at 4.2 next week too
[HTC Vivid, Raider, Velocity] camo_flage:
Stop asking
[HTC Vivid, Raider, Velocity] Xemods:
Cool I'm trying to work on a ROM myself
[HTC Vivid, Raider, Velocity] XxSHaDoWxSLaYeRxX:
Sexy
[HTC Vivid, Raider, Velocity] camo_flage:
Will the pacman ROM have pa 3.0.0?

Sent from my PACMAN HTC Raider on the Rogers Wireless Network
[HTC Vivid, Raider, Velocity] Xemods:
What you mean
[HTC Vivid, Raider, Velocity] joerolando2701:
Anyone know of a way to disable the proximity sensor during a call mine is bad. In stock sense 3.6 the power button would wake the screen this is not working in Jb. I have also tried adding gsm.proximity.enable=0 and =false as well with no effect any ideas how to override the screen off nothing seems to wake it
[HTC Vivid, Raider, Velocity] mobile_fan_2k5:
My battery stats so far... But I don't see a detailed usage like on ics. Rom is amazing.... :D

Sent from my Holiday
[HTC Vivid, Raider, Velocity] homeslice976:
What version of the ROM are you using? The latest version (1214) should have addressed this - and was confirmed to be working by the only other person who reported the problem. Or are you saying your proximity sensor is bad in general, it's not just this ROM?
[HTC Vivid, Raider, Velocity] lucasryan:
Touch the graph and it will drop down to more detail

---------- Post added at 09:35 PM ---------- Previous post was at 09:01 PM ----------

What are the differences in 1212 and 1214? Is it just that 1214 is a complete zip and dont have to flash kernel seperate, along with the prox sensor fix? What other changes were made if any in 1214 from 1212? Is there a change log if any changes besides those? Again i want to thank you for doing a great job on all these Roms buddy...Very good work!!
[HTC Vivid, Raider, Velocity] homeslice976:
That's it. Why?
[HTC Vivid, Raider, Velocity] lucasryan:
Because im still on 1212 and didnt know if anymore changes had been made, and if i needed the newer version. I havent had the black screen prob, so im good as far as any changes...
[HTC Vivid, Raider, Velocity] joerolando2701:
My sensor is bad ROM is fine
[HTC Vivid, Raider, Velocity] lucasryan:
Find Hardware Disabler app in the market, that allows you to disable it.

Be careful though...
[HTC Vivid, Raider, Velocity] homeslice976:
At your dialer press menu then settings. There is a prox sensor setting there, but would appear to be for when using a headset. You could try it though

Edit: also, this is old (hasn't been updated since 4/20/10 - happy holidays, lol) - but it sounds like it works like a prox sensor without the prox sensor (uses the gyro to detect orientation, blah, blah) http://xdaforums.com/showthread.php?t=488991

It's possible this was before the prox sensor, and wont' override current prox sensors, but keep searching - i bet you can find something software like lucasryan suggested - though i've never tried that app specifically
[HTC Vivid, Raider, Velocity] lucasryan:
You might could try to go to settings>display>Volume rocker wake...maybe that would be the same as before with ICS power wake
[HTC Vivid, Raider, Velocity] altanimi:
I'm getting unusually high RAM usage, even on boot, usually around 550-650MB. Anyone else getting numbers that high?

I remember hearing about a RAM leak in CM10 some time ago, and I'm fairly certain that was fixed...
[HTC Vivid, Raider, Velocity] lucasryan:
Can you post a screen shot whith your usage to compare?
[HTC Vivid, Raider, Velocity] haydnlj:
Has occurred to me that the issue (for me at least) is potentially related to dust covering the sensor. If you see dust between your LCD and screen in the top left (not uncommon in this model), you could have dust on the sensor. I have noticed today that a swift tap to the top left of phone during call will re-awaken screen. Confirmed the same using a prox sensor app - sensor reporting 0cm until tapped. Have been meaning to pull apart and clean, but might be that your sensor is just blocked.

Reports of dust

Screen take apart guide
[HTC Vivid, Raider, Velocity] joerolando2701:
Have but don't know which one to check none say proximity sensor
[HTC Vivid, Raider, Velocity] lilmikey201:
Where can you see your ram ?
[HTC Vivid, Raider, Velocity] FFXTDS:
Settings- apps and swipe till you see running
[HTC Vivid, Raider, Velocity] lucasryan:
CM3602 is the name of it, and cant remember witch directory it was in...but i do remember i had to scan the diff directories to find it before...ill look in little bit to try and find it for ya
[HTC Vivid, Raider, Velocity] streno513:
just tried to flash this and cant get it to work for some reason... im s-on i wiped the phone before flashing
[HTC Vivid, Raider, Velocity] thegogetter-:
which maps version works on this rom? my phone cannot find a GPS signal
[HTC Vivid, Raider, Velocity] homeslice976:
I installed the on from playvstore and it works fine. 16-20 ft accuracy
[HTC Vivid, Raider, Velocity] XxSHaDoWxSLaYeRxX:
The new version of pa
[HTC Vivid, Raider, Velocity] Wolfhawke:
Funky BT streaming, got me screaming!

Hi Homeslice and H8rift...

Weird...Initially I was going to let you folks know that BT wasn't streaming in these apps at all as noted...

Discovered that for some reason after connecting the multimedia sound level resets to 0 at random and can't be affected by software settings...making sure the volume is all the way up with the volume rocker makes big difference...Thought I had it set in Settings---->Sound, but apparently it doesn't hold well...

YouTube - initially no volume, but after manual adjustment worked.

Netflix - initially hung, but after a reboot and making sure HW overlays were disabled...worked ok

Veetle - Both work

MX Player - both work

Apollo no video (duhhh!, audio player), however will put audio to headset..

Skype - ??? audio seems not to go to headset, and sounds like it's trying to use handset mike...

Just some info and something others should watch for if using BT for AV Streaming...
[HTC Vivid, Raider, Velocity] lilmikey201:
cynogenmod just added HDR mode to camera for all phones..will it be added to this?
[HTC Vivid, Raider, Velocity] ZeRo2o9:
if its for cm10 then im pretty sure it will be
[HTC Vivid, Raider, Velocity] XxSHaDoWxSLaYeRxX:
Yup
[HTC Vivid, Raider, Velocity] My Fault:
i know homeslice's phone is down at the moment, but has anyone been able to make anymore headway with the low in-call volume?
[HTC Vivid, Raider, Velocity] XxSHaDoWxSLaYeRxX:
It might be a while until someone can fix it.. its not that bad. And if it is such a problem, I recommend flashing the sense 4.1 ROM. Pm me for the link
[HTC Vivid, Raider, Velocity] big_yute:
Don't recall ever seeing this in the almost two years I have had the phone. Light maybe medium usage, I freaking love this rom!
[HTC Vivid, Raider, Velocity] homeslice976:
It appears to have only been added on the CM 10.1 (4.2) camera. Right now I'm not using the camera that's built from Source anyway, I'm using a 4.2 camera that seems to work better. To better answer your question, not immediately, but maybe down the road.

Not yet, but I'm still digging. Confused, but still digging...
[HTC Vivid, Raider, Velocity] lilmikey201:
Do you know where I can find the camera so I can install it
[HTC Vivid, Raider, Velocity] homeslice976:
Find a CM10.1 build somewhere that's been updated in the last day or two and rip Gallery2.apk as well as the associated libs.
[HTC Vivid, Raider, Velocity] zippox180:
Ah I pulled the apk but did not think about the libs
[HTC Vivid, Raider, Velocity] XxSHaDoWxSLaYeRxX:
how would you find out which apks rely on which libs
[HTC Vivid, Raider, Velocity] bproulx:
Just wanted to say thanks again for the awesome ROM. Been running PAC for well over a month now..no complaints at all. Just flashed the new linaro kernel in the dev thread and now I'm running PAC at 2 GHz and my call volume was fixed in the kernel update. Way cool.

I showed my buddy who just got the nexus 4 and he just about shat himself.. lmao.. you guys are all amazing devs and guys like me, and the rest of us less skilled smartphone owners, are lucky to have you. Cheers.
[HTC Vivid, Raider, Velocity] XxSHaDoWxSLaYeRxX:
My phone always freezes around 1980.. How.?
[HTC Vivid, Raider, Velocity] jtsurfs:
Are you running the default kernel for PAC, the other guy said he has the Lenaro kernel. Could be why.
[HTC Vivid, Raider, Velocity] bproulx:
Yeah I flashed the sultan (linaro) kernel from the dev thread. Its at r2b2 stage now..pretty decent so far. And it totally fixes the call audio issue for everyone but AT&T users..sorry guys..mines a raider so yay rogers! Its got to still be the audience chip messing with at&t customers. Anyhow..been running at 2ghz max for 2 days now no reboots, crashes, etc..I like it with PAC.
[HTC Vivid, Raider, Velocity] Sultanxda:
I actually have to change that. After a certain voltage the voltage regulator refuses to change the CPU speed to the frequency with said high voltage, thus giving the illusion of overclocking to 2.052GHz when the chip itself is actually running at the last frequency that was specified before the change to 2.052GHz. Some additional proof of this is that if you change the CPU speed to, say, 1.944GHz then the phone will crash but if you change the CPU speed to 1.998GHz or 2.052GHz then everything will run fine and there will be no stability issues. Finally, since I'm a fan of overkill, benchmark scores remained unchanged when the CPU was running at 2.052GHz versus 1.836GHz.

The major problem with this 2GHz illusion is that everyone who is running at 1.998GHz or higher is getting worse performance because the CPU frequency is being set to what it was previously set to. That means that if the CPU frequency was 1.118GHz before setting it to 1.998GHz+ then the phone is actually running at 1.118GHz.

The voltage regulator refuses to enforce frequencies that have a voltage higher than 1400mV.
[HTC Vivid, Raider, Velocity] sadoway:
Updated v25 chrome works way better.
[HTC Vivid, Raider, Velocity] zippox180:
Yeah I'm digging the update big time scrolling is much improved
[HTC Vivid, Raider, Velocity] XxSHaDoWxSLaYeRxX:
what update.?
[HTC Vivid, Raider, Velocity] lucasryan:
Homeslice haven't been on in a couple days but wanted to ask you if you ever got a lcd and digitizer to replace your old one? Last I read you were gonna be looking for one or maybe even use your upgrade. ..anyways if not I have a extra one now along with a complete device. I went and used my upgrade on my netbook and got the samsung galaxy note 2...so I have 2 devices now