yashsingh1/xdaforums huggingface dataset:
[HTC Vivid, Raider, Velocity] martinmaxs:
The problem having with VOIP app Intervoip i wrote you about on PM , with this build is solved , thanks :)

Now i can tell that everything is working , great rom , thanks for your hardwork

EDIT : Proximity sensor is not working, albinoman887 did you have this issue ?
[HTC Vivid, Raider, Velocity] archioptrics:
Frustrated, will have to go back to 10/26
[HTC Vivid, Raider, Velocity] nguyenquyhoc:
Could you give me the post or link 26-10 version ? :rolleyes:

It's right???
[HTC Vivid, Raider, Velocity] archioptrics:
Got my problem sorted out, this rom is the only non sense rom that has captured my attention, a job exquisitely done
[HTC Vivid, Raider, Velocity] nguyenquyhoc:
so now u are using what rom :confused:
[HTC Vivid, Raider, Velocity] archioptrics:
I am using this 10/31
[HTC Vivid, Raider, Velocity] martinmaxs:
Im the only one who cant get proximity sensor to work ??
[HTC Vivid, Raider, Velocity] theslam08:
Proximity sensor working fine for me on 10/31.

Also not sure if it is (a sugar pill) but I feel like compared to 10/28, the speed went way up on the animations and such. Looks fantastic so far and it seems to be running great. Nice work :)
[HTC Vivid, Raider, Velocity] martinmaxs:
Is it your device at & t ?
[HTC Vivid, Raider, Velocity] theslam08:
We have 'signatures' on here for a reason. Yes, AT&T branded.
[HTC Vivid, Raider, Velocity] archioptrics:
I have recognised that if I try to set a custom ring tone I don't have access to my external sd
[HTC Vivid, Raider, Velocity] nguyenquyhoc:
Mine does. My devide from Korea. :eek::eek:
[HTC Vivid, Raider, Velocity] pitpit24:
Use the built-in file explorer from cm, or download file manager and select the file holding it you can set it as ringtone, or find the /system/ringtones filed.
[HTC Vivid, Raider, Velocity] albinoman887:
with what?

external sd card works here.

well i did optimize the kernel :P
[HTC Vivid, Raider, Velocity] albinoman887:
yeah if you download es file explorer then go select ringtines it asks if you want to do it with es or regular android. pick ES.
[HTC Vivid, Raider, Velocity] martinmaxs:
Then my sensor is broken , damn it
[HTC Vivid, Raider, Velocity] pitpit24:
Proximity sensor not working here, it was working in cm 10.1 but since 10.2 it don't work.

I remember their was an option to activate proximity sensor during calls, but now its gone.

I think The minimum value should be 0, but its 9...
[HTC Vivid, Raider, Velocity] theslam08:
Probably a bad flash, my proximity is working, but others isnt? Weird...would not flashing the boot.img cause that maybe?
[HTC Vivid, Raider, Velocity] NWinfuse:
I've had issues with my proximity sensor since 10.1, I just lock the screen in calls. I haven't been able to figure out what the deal is as it does function properly if I go back to CM10 or a sense rom. It really doesn't bother me much but of course it would be cool if it did work. I may look further into it now that I know this isn't a common issue.
[HTC Vivid, Raider, Velocity] Wolfhawke:
Prox sensor working on AT&T phone

It seems to be working for me, but then again I'm S-Off, and before jumping to Albinoman's ROM back about a month or two ago, I did factory reset, cleared all caches and installed from TWRP, clearing cache and dalvik after. Each update I've applied has been through TWRP again and again cache and dalvik cleared. I've not had 1/2 the issues reported.

On a BTW it looks like data and signal strength display as they should, but noticed that when I change data modes (WiFi to LTE/HSDPA Network, HSDPA to LTE), I have to allow a few minutes for it to settle out. HSDPA is the stronger of the two, but I keep flipping back and forth between HSDPA+ and 3g.
[HTC Vivid, Raider, Velocity] martinmaxs:
[MENTION=4799701]pitpit24[/MENTION] we have the same issue with the proximity sensor , here is my screenshot

Any idea how to fix it , because it was working when was on stock . Now is rooted , s-off.
[HTC Vivid, Raider, Velocity] rignfool:
To all you guys complaining about proximity sensor...

It is that you are pushing buttons with your face while on the phone?

That has happened to me since h8rifts cm10... And the only fix I have for you guys is to either turn off the screen manual... Or make sure the dial pad isn't on when making a call... It will turnnoff if you give it a second
[HTC Vivid, Raider, Velocity] martinmaxs:
unfortunately your solution is not a fix for the sensor , and you manually do the work that sensor has to do ( screen off , screen on during calls )

We need a fix for the sensor , maybe someone can post the values from the ps_kadc file located in /sys/devices/virtual/optical_sensors/proximity/ps_kadc , as i read on the other forums the fix is in this number but i can't solve it by myself .
[HTC Vivid, Raider, Velocity] patate331:
Proximity sensor working fine for me.

PS, I'm S-On
[HTC Vivid, Raider, Velocity] morpheus_1987:
My proximity sensor seems to be working, but it shows either all or nothing (9.0 cm or 0 cm). Is that right? I'm using Android Sensor Box from the Play store to check.

I seem to be having GPS problems on the 10.31 build. Sygic (GPS app) and Beautiful Widgets can't seem to get my GPS position. I also tried testing with GPS Test from Play store and although GPS is on, I have no readouts. Somehow I think Google Maps seems to be working but I'm not sure if that's getting my position based on mobile networks/wifi instead.

I'm S-On but I definitely flashed the Boot.img file again after flashing rom then G-apps.

Edit: GPS seems to be working after a few reboots, but Beautiful Widgets still can't get GPS position. I think it's the app's problem though since Sygic and GPS Test both work now.
[HTC Vivid, Raider, Velocity] nguyenquyhoc:
I see this ROMs fast decrease Battery :eek::eek:

Waiting for Optimizmt !

Who can suggest me the best Roms for batterry :silly: ?
[HTC Vivid, Raider, Velocity] TravisTheBeast:
WiFi Doesnt work? When I click turn on nothing happends. No networks show up or anything.
[HTC Vivid, Raider, Velocity] bkman08:
Fastboot flash the boot.img inside the zip.
[HTC Vivid, Raider, Velocity] TravisTheBeast:
Yea I did..... Still nothing.
[HTC Vivid, Raider, Velocity] Gene Poole:
Try this from an adb shell, or term emulator:

echo 0x5 > /sys/devices/virtual/optical_sensors/proximity/ps_canc

This worked for my old vivid. Experiment with different values between 0x1 and 0xf.
[HTC Vivid, Raider, Velocity] martinmaxs:
IT WORKED !!!! Thanks you're a genius :)

EDIT : It shows only 9cm and 0cm when it is covered , thats fine but lets fix it to show other distances ... Could you please run cat /sys/devices/virtual/optical_sensors/proximity/ps_* so i can see the other config's and apply it on my device . Or someone with working proximity please send me the log of this command . Thanks
[HTC Vivid, Raider, Velocity] morpheus_1987:
I think the proximity sensor being all or nothing is normal now when I compare it to my bro's S4 which is also all or nothing.

Anyway, here's my screenshot of that command you requested:
[HTC Vivid, Raider, Velocity] albinoman887:
its normal for it to say either 0 or 9
[HTC Vivid, Raider, Velocity] pitpit24:
Yes, but mine is stuck on 9 no matter what I do. It was working before but it stopped somewhere.
[HTC Vivid, Raider, Velocity] albinoman887:
oh and before it starts like it has in my sensation and htc glacier thread. dont ask if i will do 4.4. People are already pm'ing me and CM doesnt even have source merged yet. if its possible of course i'll do it... so dont ask please
[HTC Vivid, Raider, Velocity] albinoman887:
you try a full wipe and then dont install any apps via titanium backup or google? did you try what the above user tried with the echo command? whats the app you guys are using again? i would make a phone call to test but i dont have a sim to use right now...but i'll check my vivid but i'm pretty sure its works because my mom was using the phone last week and i highly doubt she would have put up with a bug like that
[HTC Vivid, Raider, Velocity] pitpit24:
The command is not working, or I don't do it right... I tried a full wipe and it didn't fix it.
[HTC Vivid, Raider, Velocity] martinmaxs:
Yes , you're right ..

Ive set the ps_canc value to 0x0 and the proximity works best on that value ( ive tested all of them )

So all of you having issues with proximity run command : echo 0x0 > /sys/devices/virtual/optical_sensors/proximity/ps_canc
[HTC Vivid, Raider, Velocity] pitpit24:
How to do it, I tried terminal emulator but it says I don't have permissions.
[HTC Vivid, Raider, Velocity] martinmaxs:
First run : su

then run : echo 0x0 > /sys/devices/virtual/optical_sensors/proximity/ps_canc
[HTC Vivid, Raider, Velocity] pitpit24:
Thanks it worked, but with 0x5.
[HTC Vivid, Raider, Velocity] albinoman887:
hmmm i wonder why some devices need different settings... does it save the setting after a reboot?
[HTC Vivid, Raider, Velocity] jhonny:
GR8 rom albinoman887

I have a 16g SD card , just wondering what every one else is using ?? as I can not turn on camera, it is telling me that I have no SD card.

blue tooth not working for me

I have good phone reception with this rom

thank you
[HTC Vivid, Raider, Velocity] imsleepy:
Did you try simply mounting SD card from Settings|Storage? This should help.
[HTC Vivid, Raider, Velocity] calikevin:
I'm s-off and didn't need to flash the boot IMG separate, simply flashed the ROM and the APNs loaded automatically, service works great. External SD mounts fine too, still need to test a few things but so far so good, great job!
[HTC Vivid, Raider, Velocity] Gene Poole:
Bluetooth does not work. Looks like something is missing (I can get more logs if necessary):

D/BluetoothAdapterState( 1227): CURRENT_STATE=PENDING, MESSAGE = DISABLED, isTurningOn=true, isTurningOff=false
E/BluetoothAdapterState( 1227): [COLOR="Red"]Error enabling Bluetooth - hardware init failed[/COLOR]
I/GKI_LINUX( 1227): gki_task_entry: gki_task task_id=1 [BTIF] terminating
D/HeadsetService( 1227): Received stop request...Stopping profile...
D/dalvikvm( 518): GC_CONCURRENT freed 2335K, 24% free 14621K/19044K, paused 8ms+7ms, total 140ms
D/dalvikvm( 518): WAIT_FOR_CONCURRENT_GC blocked 126ms
D/A2dpService( 1227): Received stop request...Stopping profile...
D/A2dpStateMachine( 1227): Exit Disconnected: -1
W/BluetoothHeadsetServiceJni( 1227): Cleaning up Bluetooth Handsfree Interface...
E/bt-btif ( 1227): btif_disable_service: Current Services:0x140000
W/BluetoothHeadsetServiceJni( 1227): Cleaning up Bluetooth Handsfree callback object
E/bt-btif ( 1227): btif_disable_service: Current Services:0x100000
D/BluetoothAdapterProperties( 1227): Setting state to 10
I/BluetoothAdapterState( 1227): Bluetooth adapter state changed: 11-> 10
D/BluetoothAdapterService( 1227): Broadcasting updateAdapterState() to 1 receivers.
D/HidService( 1227): Received stop request...Stopping profile...
D/BluetoothManagerService( 518): Message: 60
D/BluetoothManagerService( 518): MESSAGE_BLUETOOTH_STATE_CHANGE: prevState = 11, newState=10
D/BluetoothManagerService( 518): Broadcasting onBluetoothStateChange(false) to 7 receivers.
D/BluetoothA2dp( 518): onBluetoothStateChange: up=false
I/BluetoothAdapterState( 1227): Entering OffState
E/BluetoothA2dp( 518):
E/BluetoothA2dp( 518): java.lang.IllegalArgumentException: Service not registered: android.bluetooth.BluetoothA2dp$2@41de68a0
E/BluetoothA2dp( 518): at android.app.LoadedApk.forgetServiceDispatcher(LoadedApk.java:926)
E/BluetoothA2dp( 518): at android.app.ContextImpl.unbindService(ContextImpl.java:1546)
E/BluetoothA2dp( 518): at android.bluetooth.BluetoothA2dp$1.onBluetoothStateChange(BluetoothA2dp.java:121)
E/BluetoothA2dp( 518): at com.android.server.BluetoothManagerService.sendBluetoothStateCallback(BluetoothManagerService.java:495)
E/BluetoothA2dp( 518): at com.android.server.BluetoothManagerService.bluetoothStateChangeHandler(BluetoothManagerService.java:1125)
E/BluetoothA2dp( 518): at com.android.server.BluetoothManagerService.access$2900(BluetoothManagerService.java:48)
E/BluetoothA2dp( 518): at com.android.server.BluetoothManagerService$BluetoothHandler.handleMessage(BluetoothManagerService.java:864)
E/BluetoothA2dp( 518): at android.os.Handler.dispatchMessage(Handler.java:99)
E/BluetoothA2dp( 518): at android.os.Looper.loop(Looper.java:137)
E/BluetoothA2dp( 518): at android.os.HandlerThread.run(HandlerThread.java:61)
[HTC Vivid, Raider, Velocity] albinoman887:
new build posted. check 2nd post for changelog and download link
[HTC Vivid, Raider, Velocity] htcvividnoob:
Does this build address the Bluetooth issues? Not asking for an ETA or trying to be pushy, just curious since I need Bluetooth for a daily driver.
[HTC Vivid, Raider, Velocity] pitpit24:
I don't installed latest build yet, but the WiFi is not automatically switch off, but its set to in the WiFi options...

This is why my battery dies so fast. I hope its fixed in this build.

Thanks a lot for you great work!
[HTC Vivid, Raider, Velocity] albinoman887:
I forgot. I'll look into it now I think I know what it is
[HTC Vivid, Raider, Velocity] pitpit24:
The option to turn off WiFi is set to never, but look at that, WiFi never goes off... On 08/28 build.
[HTC Vivid, Raider, Velocity] csosbee:
Signal strength seems to be better with the latest build. The camera issues still exist as well as the bluetooth issues. Keep up the good work on it...it's definitely an awesome ROM :good:.
[HTC Vivid, Raider, Velocity] jh64dsb877r:
I get no service on the 8/29 build linked to in the second post (installed after a full wipe).

Are you using that build or a different one?

EDIT: After looking at my radio log, it seems it's not detecting my SIM card. I'll post the log here in the next few minutes.
[HTC Vivid, Raider, Velocity] albinoman887:
you didnt flash properly. both work... did you flash boot.img?
[HTC Vivid, Raider, Velocity] jh64dsb877r:
Since I'm S-off (and have been for quite some time), I didn't think that was a requirement. Is it now recommended?

I guess I'll try it and come back. I wiped everything on the system before flashing, so I guess that's the only thing it could be.
[HTC Vivid, Raider, Velocity] pitpit24:
It looks like this device needs to always flash the boot.img even if you are s-off, for some users. Look at what version of the kernel you have, it should always follow the ROM version for this ROM.
[HTC Vivid, Raider, Velocity] csosbee:
I'm using 8/29 and it does indeed work as far as the radio goes, at least on AT&T. I have a tower not 50 feet from my house. Previous builds would not get above 2 bars. This build give me the full 4 bars. While I can say that camera and bluetooth still do not work for me the radio does and that's a significant improvement. I am S-OFF and did not flash the boot.img. I don't know what's wrong with yours...all I can say is it works for me.
[HTC Vivid, Raider, Velocity] jh64dsb877r:
Okay, after restarting a couple times, ignoring the no SIM card message at boot, I get a signal registering but no bars.

Maybe it's because I'm using a microcell. In any case, just let me know if you want me to post a log.

And, just to confirm, my kernel shows as: 3.0.93-ChronicKernel-linaro-g9cbf469albinoman887@chronic-buildbox #1 Thu Aug 29 14:52:44 PDT 2013

So, I'm guessing I don't need to manually flash boot.img, but I could still try it out.

EDIT: Flashed boot.img manually, it didn't fix what I mentioned earlier.
[HTC Vivid, Raider, Velocity] Gene Poole:
Things have let up a little at work. I'd like to dedicate some time to do whatever I can to help on this. I've dug out my old Aria and will use it for my main phone. I've also got the Team-Hydra source tree synced and can build as needed. Let me know if there's anyway I can help. I'm 98% committed to getting a CM ROM on this phone (2% of me wants to dump it and get an HTC ONE Google Edition).
[HTC Vivid, Raider, Velocity] pitpit24:
If you know how to fix the camera, its not saving pictures and videos. Something with the SD card makes it not save pictures and videos. Focal pictures are rotated.

Thanks for your support!
[HTC Vivid, Raider, Velocity] jh64dsb877r:
I don't think anyone would blame you if you switched it out, but I'm glad you're here for as long as you stay with us. :good:
[HTC Vivid, Raider, Velocity] pitpit24:
I don't know why its like that. It don't stick a reboot.
[HTC Vivid, Raider, Velocity] martinmaxs:
sure it doesnt :) . Ill use Script manager and set on boot

And ive almost forgot , Maps 7 is running great in this 31/10 build , no glitches at all .
[HTC Vivid, Raider, Velocity] switchy85:
Can confirm maps is a whole lot better, but after a while of using it mine still goes pretty glitchy. Huge improvement, tho.
[HTC Vivid, Raider, Velocity] pitpit24:
I found that turning the device to landscape, then back to portrait, often fix the issue. Do it 2-3 times if its not working the first time.

After a reboot, I need to do the echo 0x0, which turns my screen off completely when I call and I need to press the hangup button fast when I see it appear for a microsecond when I try to turn screen on. Then do the command with 0x5 and the proximity sensor works as it should. If I do try 0x5 first it don't work, but after doing 0x0 and then 0x5, it works.
[HTC Vivid, Raider, Velocity] martinmaxs:
What about on adding sweep2wake feature ?
[HTC Vivid, Raider, Velocity] switchy85:
Super glitchy on this phone. Like, you don't want to go there right now. lol.
[HTC Vivid, Raider, Velocity] theslam08:
Yeah, not sure why, because on Sense X it worked fine (on any version) using kozmik's beta 13 kernel (dont test that on this rom, that kernel is sense only). But yeah, very buggy currently, screen will turn on and off or just the touch buttons will light up but not the screen then just freeze up most of the time.
[HTC Vivid, Raider, Velocity] glparke:
Installed 1031 last night and wiped everything. full charge when I went to bed and 7 hours later it was at 15%. all wifi, gps, and data was turned off.
[HTC Vivid, Raider, Velocity] martinmaxs:
You have the kernel source with sweep2wake added ? It will be fine if someone send me the sources of the Kernel , so i can try to solve the sweep2wake option
[HTC Vivid, Raider, Velocity] morpheus_1987:
I'm having similar battery problems which at first I thought was associated with GPS/location tracking, but once I resolved the issue with Beautiful Widgets and did some testing with airplane mode to rule out connectivity issues, I'm still getting 10%/hour drain. BetterBatteryStats only shows PowerManagerServices.WakeLocks under Kernel Wakelock and NLPCollectorWakeLock under Partial Wakelock. Regular system battery just shows it's Google Play Services as the next highest battery eater after the screen.

I tried uninstalling Google Play Services via TiBu as there are some topics that suggest doing so and reinstalling via Play store but I've been unable to uninstall it since TiBu just crashes.

Edit: I seem to also be having an issue with keyboard constantly defaulting back to the AOSP one as opposed to Swype.
[HTC Vivid, Raider, Velocity] mbze430:
NLPCollector wakelock is associated with Google now and Google maps. If you Google those words there will be some "fixes" for it. Mostly disabling Now and Maps
[HTC Vivid, Raider, Velocity] mbze430:
on another note... anyone having issue with the ROM not recognizing the SIM card. My daughter is saying it won't recognize it.

Tried rebooting and reseating the sim card.... nothing.
[HTC Vivid, Raider, Velocity] pitpit24:
You need a new sim card i think.
[HTC Vivid, Raider, Velocity] albinoman887:
i actually had this battery drain issue on my s4. the fix is to go to apps then the "All" tab and find Google Services Framework. click it. then clear data. that should fix your battery drain. you can usually tell this is an issue if google framework services is using most of your battery in the battery info screen

edit: the reason i think this is needed even after a fresh install is the gapps package has an outdated google frameworks services and as sson as you connect to play it updates, and then it needs data cleared for some reason
[HTC Vivid, Raider, Velocity] mbze430:
That's what happens when you have a teenage daughter... she put in the sim card the wrong way....

Anyways.... is there a way to get the speaker phone to go louder???

I don't know anyone here are familiar with the Viper4Android app. In any case I noticed something is strange. I was going use V4A to make the speakerphone (internal) speaker louder, but it has no effect. Like it can't control it. V4A works fine with the headphone jack. Anything changes made is noticeable through the headphone jack. Just not the external speaker on the Vivid.

Anyone using V4A also noticing this. Anyone else using "mods" that can put out a little more volume from the speakerphone?
[HTC Vivid, Raider, Velocity] morpheus_1987:
I ended up rewiping and reflashing since I had problems with the keyboard defaulting to AOSP all the time as well. I must have had a bad flash previously as I noticed the browser in this 10.2 is different now compared to the previous time I flashed. In the last 4 hours or so after restoring apps and fiddling around, I managed to let it idle for about 2 hours and it seems that my battery drain issue is gone. One of the steps while I was trying to get my play store to auto download my apps again was clearing its' cache/data since it wasn't downloading my apps automatically so I'm not sure if this did it or the reflash in general.

Either way, I'm glad it's resolved as I can finally enjoy the rom and use it as a daily driver without being tied to a charger. I had battery problems previously when I was on the PACman rom too.
[HTC Vivid, Raider, Velocity] mbze430:
Anyone try an OTG cable with this phone/rom?? apparently i couldn't get it to work.
[HTC Vivid, Raider, Velocity] haydnlj:
Followed this, and was getting a "unfortunately the process com.google.process.location has stopped" after multiple reboots. Cleared Dalvik and fixed permissions, and problem went away - just in case anyone else has the same.

Just thought I'd add that my phone has not worked this good since I got it almost 2 years ago - thanks for all the hard work. Am on 10/26 and relunctant to change now :)
[HTC Vivid, Raider, Velocity] Ghitim:
i liked 10/26 too, 10/31 is tons faster
[HTC Vivid, Raider, Velocity] Dav.Nio:
excuse me , can you send me the link of 10/26 , i want to try it :laugh:
[HTC Vivid, Raider, Velocity] positiveg:
Using the 10/27 version.

Have the worst data connection

You'll go from wifi to data and if you are not aware have no data till you try to toggle off and on. Think 10/15 wa one the best this have been. Plus the sound quality for calls gone bad again

G

---------- Post added at 12:53 PM ---------- Previous post was at 12:31 PM ----------

Hi guys check this problem

I flashed a friend on mine Vivid.

After doing this her phone can't detect the external SD card.

She bought a new card same thing

You plug the card itself directly into the computer it works

and it also works if you try mounting using TWRP in recovery mode

So would really like some help thanks
[HTC Vivid, Raider, Velocity] theslam08:
Um maybe use the latest version, maybe? Oct 31 build has 0 problems, data, sd, sound, all work. Why would anyone flash old builds?
[HTC Vivid, Raider, Velocity] positiveg:
Cause when I flashed it first only 10/28 was out. I myself had experienced similar issues one time back but I can't recall exactly what I did to get it solved.

Will try the latest flash and see what happens . I just flashed my phone with the 10/31 and data seemed to have improved
[HTC Vivid, Raider, Velocity] SteelBreaker:
Not mount MicroSD Card on USB to PC, Mount only InternalStorage. How fix this ?
[HTC Vivid, Raider, Velocity] rignfool:
You wait for albinoman to fix it...

Or... You pull the card and put it straight into the computer...

Or... You mount it in recovery...
[HTC Vivid, Raider, Velocity] bsaman:
Mine mounts fine as a mtp media device.
[HTC Vivid, Raider, Velocity] SteelBreaker:
I mount it in recovery ))

How mtp devices on this rom?