yashsingh1/xdaforums huggingface dataset:
[HTC Vivid, Raider, Velocity] rignfool:
I think the black screen after call is low screen off CPU max freq...

Question... I know its just a whistle and bell... but can you enable the CPU states file read by setcpu/cpuspy for time in state... pretty pretty please
[HTC Vivid, Raider, Velocity] lucasryan:
Homeslice, have you considered changing the kernel to where we can control the voltage?
[HTC Vivid, Raider, Velocity] homeslice976:
Feature requests? tisk, tisk!! lol just kidding..

But for real these things may come. What I'd actually love to happen would be an actual kernel dev come by and grace us with their work/tweaks.

In the mean time, the edits I'm trying to make are for core functionality, but I'll do a quick search of these things and see what it may take.
[HTC Vivid, Raider, Velocity] ess.boyer:
There's a guide somewhere (I think on Faux's kernel page) for tweaking the voltage tables for your kernel. It would be the same diff for JB kernel too I'm pretty sure.
[HTC Vivid, Raider, Velocity] rignfool:
I wouldn't normally ask but I'm working on battery life...
[HTC Vivid, Raider, Velocity] lucasryan:
Is this what you was talking about? Say for kernel devs and the code for under volting along with over volting...I would try to change it myself but am not sure about it as much as homeslice would be...

[ to over volt ALL frequencies by 25000 uv (microvolts) ]

echo "+25000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels

[ to under volt ALL frequencies by 25000 uv (microvolts) ]

echo "-25000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels

[ to set a specific frequency (ie 1.18 GHz)

with a specific voltage (ie 1.0875 volts) ]

echo "1188000 1087500" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
[HTC Vivid, Raider, Velocity] homeslice976:
Re: [ROM][JB][4.1.2]Unofficial PAC-man v19.0.0[01.15.13]

I did already slightly undervolt when I did the overclock. Can a Raider or velocity owner verify whether or not they had frequency speeds up to 1.5 before I released the overclock kernel ? Could you only go to 1.2 as well? If you could go to 1.5 before, the devices are using different frequency tables so I have to undervolt the other tables as well. Or just do the overclock/under volt properly and combine the tables into one..
[HTC Vivid, Raider, Velocity] haydnlj:
deleted
[HTC Vivid, Raider, Velocity] Garrykd:
Up until your overclocked kernel 1.2 was the max for me on CM10.

Originally the phone shipped with a clockspeed of 1.5 (stock gingerbread, then ics) though

Rogers Raider.
[HTC Vivid, Raider, Velocity] homeslice976:
Re: [ROM][JB][4.1.2]Unofficial PAC-man v19.0.0[01.15.13]

Thanks. I did know the velocity and the raider were 1.5 stock.. but in that case they're all using the same table so everyone is slightly undervolted
[HTC Vivid, Raider, Velocity] Spectrejester:
Re: [ROM][JB][4.1.2]Unofficial PAC-man v19.0.0[01.15.13]

My Velocity is running at 1.5 without using the over clocked kernel.
[HTC Vivid, Raider, Velocity] bproulx:
Re: [ROM][JB][4.1.2]Unofficial PAC-man v19.0.0[01.15.13]

Raider here - was stuck at 1.2 before your overclock kernel. Nice btw. :)
[HTC Vivid, Raider, Velocity] homeslice976:
Re: [ROM][JB][4.1.2]Unofficial PAC-man v19.0.0[01.15.13]

Spectre - Now I'm confused lol..any other velocity owners? And are you on cm10 with the included kernel? Or the non oc non external storage fix kernel from here?
[HTC Vivid, Raider, Velocity] ess.boyer:
I'm a Raider, and I was 1.2 as well. I can also confirm that -50 UV worked for me on Holics. I usually stuck with -25 just to be safe, and it never gave me any issues.

BTW the Raider was underclocked to 1.2 stock. I believe the Velocity was the only one running 1.5 stock.
[HTC Vivid, Raider, Velocity] camo_flage:
Re: [ROM][JB][4.1.2]Unofficial PAC-man v19.0.0[01.15.13]

The raider in Korea was 1.5 not ours

Sent from my PACMAN HTC Raider on the Rogers Wireless Network
[HTC Vivid, Raider, Velocity] Garrykd:
Oops, my bad...so much for my memory :o
[HTC Vivid, Raider, Velocity] HopelesRomantc91:
I did some searching in this thread and couldn't find the exact information I wanted. So I'm generally pretty experienced in things computer related, but I'm very new to flashing ROMs as a general thing. I have JuopunutBear and S-OFF on my bootloader screen (as per the SUPERGUIDE), but that guide says that the manual way to flash a new ROM is

fastboot flash boot boot.img

but the PAC-man guide says to flash both the ROM and the gapps. How exactly do I do that? Did I just miss something?
[HTC Vivid, Raider, Velocity] rignfool:
Re: [ROM][JB][4.1.2]Unofficial PAC-man v19.0.0[01.15.13]

S-off means you don't need fastboot
[HTC Vivid, Raider, Velocity] HopelesRomantc91:
Then I really have no idea what to do for how to flash the two things like I'm supposed to. But just so I understand, does fastboot mean that S-ON is completely acceptable, and I wasted two hours getting S-OFF?
[HTC Vivid, Raider, Velocity] homeslice976:
If you are s-off, all you need to do is flash the rom.zip, then flash the gapps .zip, then reboot.

The "fastboot flash boot boot.img" is an extra step that s-on users need to take, to properly flash the kernel and ramdisk. One of the best features of being s-off is not having to do this extra step, as the boot partition is writable from recovery (and boot.img is automatically flashed during the ROM .zip flash)

And yes, s-on is completely acceptable. There are a bunch of people who never took the s-off plunge. But 2 hours? ouch... i got it in about 10 minutes
[HTC Vivid, Raider, Velocity] HopelesRomantc91:
Never mind

EDIT:As in I think I got it

EDIT: How long should it appear to be loading the first time it starts up? Because it's taking forever...
[HTC Vivid, Raider, Velocity] N-rG:
Does this ROM only works with AT&T phones or can i use it in Germany as well?
[HTC Vivid, Raider, Velocity] jtsurfs:
You should be able to us this ROM as long as you have a Holiday. You might want to capture your APN settings prior to flashing as not sure what carrier you have and whether Homeslice has your carrier already incorporated in the build.

---------- Post added at 09:07 AM ---------- Previous post was at 08:57 AM ----------

Is it normal that the boot.img fix for the usb is 16MB? Most of the ones I have loaded in the past were only 4 MB.

Nevermind. Just loaded and it seems to be working ok.
[HTC Vivid, Raider, Velocity] HopelesRomantc91:
I had no idea what I was doing, really. I was all confused by the superguide because the one I did a while ago.

Also it apparently doesn't take long to start up at all if I remember to wipe data, cache, dalvik cache, and system before I flash...

EDIT: however it reboots every time I hit the start button...
[HTC Vivid, Raider, Velocity] homeslice976:
It's so big because I didn't do a full build to get the boot.img. I injected the zImage, then dd'd the boot partition into a boot.img - so that's the raw unpacked size.

You mean like everytime you hit the power button it reboots? Does it ever show anything on the screen?
[HTC Vivid, Raider, Velocity] Wolfhawke:
48 hrs with PAC-man - Thanks for your hard work devs!

Hello Thread!

Just spent my first 48 hrs with the PAC-man ROM... for a ROM that is still "under development" it is quite stable (no freezes). Recently took the S-OFF plunge and the bootloader has been unlocked for ages. I miss HTC Sense and the FM radio widget a little bit, but that's filed under the "get over it" section for now.

Once I got used to the differences between ROMs (coming from the Holics 1.3 Sensed) I found the ROM to be fairly quick, responsive and well behaved. Did note that the in-Call volume seemed to be preset to one level at all times (known bug) and Bluetooth is still broke (I got choppy playback on my Voyager+ with audio, known bug), I've not had the nerve to try a call with the headset. As an AT$T subscriber, the in-call mike worked the first time, no echoes when talking. The only pain in the arse was having to put my phone number in for voice mail (to be correctly handled as soon as I figure out from stock what that was...).

Headset audio is good, I used a generic headset/mic combo and it works...so that will do until a good bluetooth solution is found.

Control wise, I'm not sure if I want to run things in Phablet or Phone mode for settings menu. It's awfully small and for someone with big fingertips, it's hard to hit the right buttons in Settings. Any recommendations there ess.boyer or Homeslice?

*ID10T update 1/18/2013@1407est....use the rotation function (90 deg) with the huge font....reduced fat fingering...

Kudos to the development team as I've accepted it'll be a frozen day in Hell (and I ain't talking Hell, Michigan) before AT$T and HTC release a JB rom! Excellent work!
[HTC Vivid, Raider, Velocity] HopelesRomantc91:
Initial boot it tells me to choose a language and says "Start" I choose English (US) and hit start then it waits for a moment then reboots.
[HTC Vivid, Raider, Velocity] lucasryan:
Re: [ROM][JB][4.1.2]Unofficial PAC-man v19.0.0[01.15.13]

So we are undervolted by 50 or 25 ATM?
[HTC Vivid, Raider, Velocity] Wolfhawke:
On a note I missed here, I get flickering in the browsers occasionally, Driver issue? should I allow hardware or software to handle 2D rendering?
[HTC Vivid, Raider, Velocity] ess.boyer:
Disabling the HW overlay (which forces 2D stuff to be drawn via the GPU instead of the CPU - nothing really to do with software rendering) fixes the flicker. The bummer is that this setting doesn't stick after reboot, so you need to re-check it on every boot.
[HTC Vivid, Raider, Velocity] HopelesRomantc91:
Wait, was I supposed to flash the Kernel files first? Because it didn't say I had to flash a new Kernel...
[HTC Vivid, Raider, Velocity] homeslice976:
You can see the old table going out and new table coming in here (https://github.com/homeslice976/and...mmit/a821478ada5d74867a382d5be41fd3d744d7c5f6)

If you're s-off, you just need to flash the rom .zip, then the gapps .zip. The kernel is in the boot.img, which is flashed when the rom .zip is flashed automatically. However, if you want the new kernel with the external storage mounting fix, you'll need to flash that .zip after flashing the rom .zip
[HTC Vivid, Raider, Velocity] Wolfhawke:
Hey Homeslice, something you might want to mention is the gapps.zip (original 20121011 release) must be flashed first before the updated kernel (also named gapps.zip) is flashed if it is a first time install... I had that problem on install and ended up actually changing the name of the updated kernel so I could keep them straight...But it is fantastic to see everything mount on the Winblows 7 unit!:)
[HTC Vivid, Raider, Velocity] homeslice976:
The updated kernel is not called gapps.zip, unless you renamed it to that. the updated boot.img which includes the kernel is in a .zip called "Kernel_USBFix.zip" that can be downloaded from the OP.
[HTC Vivid, Raider, Velocity] Spectrejester:
Re: [ROM][JB][4.1.2]Unofficial PAC-man v19.0.0[01.15.13]

Here is a screen shot of my phones info if it helps.
[HTC Vivid, Raider, Velocity] homeslice976:
Interesting - yea that's a kernel before the OC kernel. So if you have speeds up to 1.5 it sounds like the Velocity is using a different table. I'm compiling a kernel now that should direct all devices to a single table, with slightly higher clock speeds... but we'll see how it goes.
[HTC Vivid, Raider, Velocity] Wolfhawke:
Did I just have another 1D10T error?

Interesting...I didn't rename it as such but when I d'loaded the files suggested.

I ended up with one gapps-jb-20121011-signed.zip file with a size of 90534kb and another with the same name that had a file size of 4732kb. Both of them were taken from the very first message on the thread.

Now I'm thinking I didn't get the right package for the usb fix but how was I still able to get and see all the drives properly mounted... :p

Well it works, and works well in any case my kernel reads as below:

3.0.53-ga821478-dirty greg@greb-VirtualBox #8

Tue Jan 15:08:30:47 EST 2013

Is this the right version of the kernel to have? or did I have yet another 1D10T noob code flash?:rolleyes:
[HTC Vivid, Raider, Velocity] homeslice976:
You definitely hav ethe right one. I just downloaded again and it's called Kernel_USBFix.zip. No idea what happened there - but as long as it works ;)
[HTC Vivid, Raider, Velocity] calikevin:
Re: [ROM][JB][4.1.2]Unofficial PAC-man v19.0.0[01.15.13]

Can someone try downloading Dolphin Browser with this ROM and tell me if it works? I keep getting force closes with Dolphin and Dolphin Beta, but all other browsers work, very odd

Sent from my Vivid 4G using Xparent Blue Tapatalk 2
[HTC Vivid, Raider, Velocity] HopelesRomantc91:
Well, balls to the wall, I'm in deep. I can't find my microSD to SD adapter, nor can I find a working boot.img that'll load to my phone via fastboot AND let it start up. It reboots if I push "Start" or "Turn on USB storage" on the initial screen for PACman, and the RUU executables I have keep giving me errors (all it says is there was an error). Is there anyone who wouldn't mind PMing me to help me try and get my phone to a place where it will at least boot to Android?
[HTC Vivid, Raider, Velocity] XxSHaDoWxSLaYeRxX:
Re: [ROM][JB][4.1.2]Unofficial PAC-man v19.0.0[01.15.13]

You should be able to boot into fast boot with out an is installed..
[HTC Vivid, Raider, Velocity] HopelesRomantc91:
Yes, that's not a problem. I started a new thread explaining my problem here, but in short I've tried 3 different ROMs, and none of them will work, basically. One has a reboot loop, the other two, as soon as I try to start the initial setup do a reboot. Getting into fastboot on the phone does nothing for me when I have no idea how to make the ROM work.
[HTC Vivid, Raider, Velocity] lucasryan:
sweet...thanks for the hard work
[HTC Vivid, Raider, Velocity] calikevin:
Re: [ROM][JB][4.1.2]Unofficial PAC-man v19.0.0[01.15.13]

Sorry, I thought I saw somewhere a volume fix for headsets? Sound quality is terrible but no issues with volume. A found the USB kernel fix

Sent from my Vivid 4G using Xparent Blue Tapatalk 2
[HTC Vivid, Raider, Velocity] i3am5not8real13:
Re: [ROM][JB][4.1.2]Unofficial PAC-man v19.0.0[01.15.13]

Dolphin browser works fine for me, i think dolphin jetpack will cause a fc, if u have that installed try uninstalling it
[HTC Vivid, Raider, Velocity] calikevin:
Re: [ROM][JB][4.1.2]Unofficial PAC-man v19.0.0[01.15.13]

Can't use Dolphin Browser or Dolphin Beta, but Dolphin Mini works for some reason. Doesn't matter if I have jetpack or not. What's the deal, the Vivid is compatible according to the Apps description, anyone else having force closes? Still only seems to be with Dolphin and Dolphin Beta.

Sent from my Vivid 4G using Xparent Blue Tapatalk 2
[HTC Vivid, Raider, Velocity] big_yute:
Re: [ROM][JB][4.1.2]Unofficial PAC-man v19.0.0[01.15.13]

Uninstall dolphin browser and jetpack and dolphin mini. Remove them from your Google app list in the play store, power off the phone, pull the battery for 10secs and then put it together, boot up and try to install dolphin browser first.

I was having fc's with dolphin after the latest pac update. I did the above and it resolved my issue. Hope it helps yours..
[HTC Vivid, Raider, Velocity] calikevin:
Re: [ROM][JB][4.1.2]Unofficial PAC-man v19.0.0[01.15.13]

Interestingly enough before reading your last post I uninstalled the jetpack after reinstalling it and Dolphin loaded up just fine but I still can't get Beta to load up. Thanks for the help! Any idea what's causing the crashes?

Sent from my Vivid 4G using Xparent Blue Tapatalk 2
[HTC Vivid, Raider, Velocity] bproulx:
Re: [ROM][JB][4.1.2]Unofficial PAC-man v19.0.0[01.15.13]

Installed dolphin and the beta..both work fine. Seems to be isolated to you.
[HTC Vivid, Raider, Velocity] XxSHaDoWxSLaYeRxX:
use another browser for the time being
[HTC Vivid, Raider, Velocity] devorama:
Has anyone gotten the AT&T Visual Voicemail working with this ROM? It seems to connect for me, but it can't play back any of the messages. It does connect, because it does have a list of messages. Perhaps a disconnect with the audio player? I'm on AT&T with the Vivid. Thanks for any input!
[HTC Vivid, Raider, Velocity] i3am5not8real13:
Re: [ROM][JB][4.1.2]Unofficial PAC-man v19.0.0[01.15.13]

having the same exact problem, messages get listed but cant be listened to
[HTC Vivid, Raider, Velocity] XxSHaDoWxSLaYeRxX:
Re: [ROM][JB][4.1.2]Unofficial PAC-man v19.0.0[01.15.13]

Use Google voice. Works like a charm. You need to do the web setup though
[HTC Vivid, Raider, Velocity] jtsurfs:
I noticed after loading the USB fix the in- call volume is much lower than it had been previously for me. I know there was a previous in call volume issue with the desensed ROMs before, has anyone tried checking with Synerge to see if he is familiar with a way to fix this?
[HTC Vivid, Raider, Velocity] briarwood:
This is my favorite ROM, the Paranoid tweaks are fantastic. I especially love the lockscreen weather app. By far the best lockscreen weather I've seen outside if the Sense weather app.

I hope the bluetooth issue is fixed, until it is and the 1080P video issue is I cant use this as my daily driver.

Great ROM, thanks for all the hard work.
[HTC Vivid, Raider, Velocity] ZeRo2o9:
that really keeps you from using it? 720p is not that bad
[HTC Vivid, Raider, Velocity] briarwood:
Bluetooth is the biggest issue

The bluetooth issue is what keeps me from using it. I use bluetooth headphones at the gym and I use VLingo in the car connected via bluetooth to my car stereo. I need bluetooth capabilities. I tried running Pacman during the day and restoring my ELEGANCIA backup to use at the gym and in the car and then restoring my Pacman when I won't be driving but that got old quickly.

As I said it's a great ROM but I need bluetooth.

I also have an HD2 and it had the same issues with bluetooth on its Pacman ROM, they had a fix rather quickly though.
[HTC Vivid, Raider, Velocity] ZeRo2o9:
Re: [ROM][JB][4.1.2]Unofficial PAC-man v19.0.0[01.15.13]

Oh OK I see your point now lol
[HTC Vivid, Raider, Velocity] bproulx:
Re: [ROM][JB][4.1.2]Unofficial PAC-man v19.0.0[01.15.13]

OK..here's a weird one.. two raiders running the same kernel and ROM but all of a sudden one is visually notifying that shell is gaining su privileges repeatedly after every power button wake / swipe unlock combo. The issue is recurring.. only on one phone tho so I assume its something my wife has installed... any ideas what could cause this?
[HTC Vivid, Raider, Velocity] shoalinagent:
Re: [ROM][JB][4.1.2]Unofficial PAC-man v19.0.0[01.15.13]

Sounds to me like 'remember my answer' is not sticking, try reinstalling/updating supersu.

Sent from my HTC Velocity 4G
[HTC Vivid, Raider, Velocity] Wolfhawke:
Some way to adjust touch sensitivity?

Hi All,

Was just curious if there was a means to tweak the touch sensitivity on the ROM? I might have missed the setting or it's buried somewhere away from noob users (like me) who know how to get to and use terminal...<LOL>

Anyway the only thing that frustrates me is it does take a fairly heavy hand to get something to work on the screen, but I barely touch the search button and off it goes...(typical for any rom on this phone...they really should have designed a hardware key for this)...

What I'm looking for is a means to set the touch screen sensitivity a little higher...any ideas?
[HTC Vivid, Raider, Velocity] tagriff:
Re: [ROM][JB][4.1.2]Unofficial PAC-man v19.0.0[01.15.13]

I do not believe there's a setting for that... Might be hardware?
[HTC Vivid, Raider, Velocity] homeslice976:
OP updated - PAC v19.3.0.

Also - sorry about not being around much the last few days. Busy week at work. I'll get back to it in the next day or two though.
[HTC Vivid, Raider, Velocity] Xemods:
i need help so i flashed the boot.img but why dont the sd card the i put in my phone work it wont lemme install apk because the sd card i put in my phone wont work it says cant mount /dev/block/mmcblk0p36 so what do i do
[HTC Vivid, Raider, Velocity] homeslice976:
Are you using ClockworkMod Recovery? If so, you shouldn't be..

Anyway.. you can try getting a good recovery (WCX or TWRP), and attempting to mount USB storage from recovery. Hopefully your PC tells you that it needs formatted and that's all it takes. Also try from within the ROM to turn on USB storage, and see if Windows tells you it needs formatted. If you can't get it to format, you'll probably need to relock your bootloader and run an RUU, then re unlock, flash a recovery that works, then install the ROM
[HTC Vivid, Raider, Velocity] Xemods:
whats a ruu
[HTC Vivid, Raider, Velocity] jtsurfs:
Re: [ROM][JB][4.1.2]Unofficial PAC-man v19.3.0[01.21.13]

An ruu is the stock image that was on your phone. There is a thread on here that lists the ruus and you need to get one specific for your phone and carrier.
[HTC Vivid, Raider, Velocity] ZeRo2o9:
Re: [ROM][JB][4.1.2]Unofficial PAC-man v19.3.0[01.21.13]

That might be how your phone messed up it doesn't sound like you know how to do anything you need to read the forums man. Just start fresh and run the ICS ruu then reunlock and root
[HTC Vivid, Raider, Velocity] Xemods:
can i please have some help why does it say security warning when i go back to relocked after doing command fastboot oem lock what do i do i really need help i dont know what to do and this time i need help please someone

---------- Post added at 01:03 AM ---------- Previous post was at 01:01 AM ----------

how do i run the ruu if i dont have windows i use ubuntu someone tell me how to fix this
[HTC Vivid, Raider, Velocity] Wolfhawke:
Patience...

First things first... learn the acronym RTFD (aka Read the (ahem) Fine Documentation), then search the Internet or the XDA Forums first before flashing a ROM. Reading and research will save you more time than screaming help, believe this junior member...

See these links before we go any further...

http://xdaforums.com/wiki/index.php?title=Flashing_Guide_-_Android

http://xdaforums.com/showthread.php?t=711303

Ok...given that I'm not an ubuntu/Linux power user this might take a minute. If you can work with WINE (windows emulator - there are How-to's on the internet) you should be able to run the RUU in WINE. If you can't, the second link would be helpful here...I would not be overly concerned about the security warning...

Failing that find a friend with Windows and do it there...even a netbook would work in this case! Double click the RUU and let it do it's thing...

Good luck!
[HTC Vivid, Raider, Velocity] Xemods:
ok
[HTC Vivid, Raider, Velocity] JohnL_83:
So i've finally got the taste of jb on my vivid, and just like everybody says here, its definitely a badass rom :)

Just a couple of things tho (it may have already been mentioned here - just didnt have time to read the entire post as they are already too many lol) i noticed after a reboot or shutdown, the signal bar drops down to two then completely disappear for maybe 30 sec, then goes back to full, and then again drops down then disappear. Second, i use an ap called tango where u can make video calls, when i installed it using this rom, i get a mssg regarding the app cant connect to audio of some sort. Can anyone help me?
[HTC Vivid, Raider, Velocity] Wolfhawke:
I'm guessing this bug is still in existence...as I've tried the patch and still no luck with the headset that worked in ICS...

Not a dealbreaker at this point...maybe when Google gets off their ass and fixes the bluetooth thing (a common problem with JB if my research holds true), I can use my bluetooth...Until then, either patient waiting or going back to an ICS based ROM...
[HTC Vivid, Raider, Velocity] homeslice976:
The signal bars are not accurate. It was either they didn't work at all, or they "appeared" to work, even though they were lying. I know that users have reported audio issues with GTalk Video Chats as well - probably the same issue.

That was not an attempt to fix BT Headsets. that was for wired headsets, but it didn't work for a couple of reasons. This issue has me stumped now though, as it appears some people's wired headset mics work fine, others don't work at all.. so i'm confused.