yashsingh1/xdaforums huggingface dataset:
[HTC Rezound] winnernet5000:
The main bug I've noticed in this is the dreaded "Can't reach Google at the moment" bug which impacts google now exclusively (connections to google actually do work, contrary to the error message). Basically it completely breaks that functionality. It seems to be a very common bug based on my google searches, dating back over a year. I've tried clearing cache + dalvik + rebooting. Removing accounts and re-adding. Turning google now on and off. Removing velvet.apk from system and reinstalling it from market. 0 solutions worked for me.

I switched to iOS after being on android for a few years, this is my girlfriend's phone. I really think it is pathetic that google now seems to work better on iOS than android :S.

BTW other than the google now bug (which I think is just something google is pretending doesn't exist), the ROM works surprisingly well. I even turned on ART, and haven't had any issues other than google now. This is with the paranoid android gapps (but I imagine that I would have the same issue with any gapps since people on nexus devices are reporting the same issue).
[HTC Rezound] REV3NT3CH:
the big thing with iOS is the very little developement on it...as iOS is just a big kang of android itself (look at the comparitive linux backbone that iOS has) you have to keep in mind that this is a 2 yr old device running on brand spanking new android...A good example for you...take an iphone 3g and make it run iphone 5c software....you just cant expect everything to up and work in a developing rom...put this phone on pure stock ics and i guarentee you it will outperform your kanged device
[HTC Rezound] tholmes8291:
I set up Gmail IMAP and get calendar sync but still can't see body of email. Known issue or ideas?
[HTC Rezound] tlfromva:
Try BuildProp Editor. That worked for me.

Sent from my phone running CM 11.0
[HTC Rezound] Djay1809:
Worked, Do I need to reboot the shell? NVM I figured it out, that's amazing I'm beyond excited.
[HTC Rezound] DCnovicky:
is there a way to make voice typing permanently the default and then have swiftkey open as needed when selecting the "keyboard button" in the voice typing box. it seems no matter what I do swiftkey automatically changes to the default even if voice typing was selected as the default in language n keyboard settings.....
[HTC Rezound] Quadman:
http://www.engadget.com/2014/02/12/lg-reveals-the-g-pro-2/
[HTC Rezound] bshiznit:
Any of those "keep your unlimited data" "accident" things going on of late? I've been eligible since 1/3/2014... But may just stick around on this since [MENTION=4203241]IAmTheOneTheyCallNeo[/MENTION] and [MENTION=3419683]Snuzzo[/MENTION] and company have kept this thing alive! Any buzz about Verizon taking away unlimited data? Whatever I decide big thanks to both of you as always!
[HTC Rezound] Huachipato:
Here is an interesting article about upgrading. My wife has a dumb phone - I may just have to try this out.

http://gregloesch.com/980/verizon-u...and-keep-it-with-verizon-rep-chat-transcript/
[HTC Rezound] Dreistul:
Here's a weird one. I used to use feedly all the time. Then I found it would frequently cause system ui crashes and occasional reboots. I may have been using it when memory corrupted. And I may have been using it last time my phone rebooted and would get off the boot screen (had to reflash). Today I tried wiping the app data. Which forced a reboot. So I tried uninstalling...Reboot. Delete with TiBu? Reboot. Finally disabled with ROM Toolbox, wiped data, uninstalled. Reinstalled. Used for 2 minutes. Reboot. Uninstalled.

I'm kind of thinking that a Galaxy Note 3 is in my future.
[HTC Rezound] kodiak799:
I went back to Tachyon....just much better for what I'm trying to do.

Anyway, as an alternative to Feedly I recommend you check out GReader. It syncs with Feedly, and the Pro version ($4.69) has a pretty good widget and downloads articles automatically for offline viewing. The app itself is a pretty decent interface, but I usually scroll through a bunch of different widgets, click an article of interest, and it launches a nicely formatted cached offline story.
[HTC Rezound] Hobox10:
Has anyone noticed that system volume is no longer it's own volume? It seems to have been integrated into media volumes, which is extremely stupid and annoying.

Beyond that, I think volumes are bugged. When I play a video the browser, or system apps that make noise such as Google Now try speaking (voice commands, directions, etc) It is using the in-call volume. This means I have to turn up the call volume very high to hear things, and then if I forget to turn it back down (every time) when I get a phone call it is jarringly loud at first.

Please tell me this isn't some stupid new "feature" CM feels like forcing on everyone like they did with removing notification quicksettings.
[HTC Rezound] onthehole:
Did you get a ONE? Picked mine up and have s-off / root.

Sent from my HTC Rezound.
[HTC Rezound] Neo:
I will some time in March
[HTC Rezound] underscoredot:
Camera Problems

I've been working on building this rom for a few days and I finally got it compiled and it's running seemingly well. The problem is the camera. After installing I see the camera2 icon. When I clck it I get "can't connect to camera"- but then it gets strange. I click it again and it says "this program is not installed"... Then the icon disappears while I'm staring at it. At the same time a few more apps disappear- but, I'm not too concerned with that.

During the final stage of my build I got:

using device-specific extensions in device/htc/common
unable to load device-specific module; assuming none

Is this normal output? Is it not seeing the driver files? Thanks in advance everyone.
[HTC Rezound] Neo:
Did you:

cd vendor/cm

git revert --no-edit b71b47d72b129915327f41653b06edaea5008534 || retval=1

?

For whatever reason, the new boot ani sucks a good portion of the allotted system memory on startup and causes problems with the camera and other things. For tests, you could simply delete it from the rom zip, reboot, then see of your camera works again. We've been reverting the boot ani the the previous version.
[HTC Rezound] underscoredot:
Thanks for responding so quickly. No dice, unfortunately. Tried removing ani from zip and removing from output and rebuilding, same results.

Are you using cyanogens "cm-11" or "stable/cm-11" repo? Maybe I need to switch to the stable.
[HTC Rezound] el Filou:
You mean the memory used by the boot anim isn't freed when it has finished booting? Is that a PMEM/ION hybrid quirk?

Just out of curiosity, what is the reason KitKat on our Rezound has less user-accessible RAM (~726-737 MB depending on the ROM) than previous AOSP versions (~752), themselves having less than Sense (815 MB) ? That's something that's always been bugging me, but I can't find the answer on the Web. Guess you have to be a kernel dev to know why? ;)
[HTC Rezound] _litz:
It's less an issue with memory not being freed, and more an issue with the new boot animation stressing the video drivers and causing them to become unstable and crash. When this happens, the memory in use fails to be freed.

Reverting to the stargate style boot animation (which, IMHO, is far superior anyway) completely eliminates the issue.
[HTC Rezound] Neo:
There's your problem. Use the Hybrid branches for everything. device/htc/vigor does not have a hybrid branch fyi
[HTC Rezound] Neo:
2/25 build is out. Let me know if anything is broken/fixed from the last build to now
[HTC Rezound] tong6998:
Just dirtyflashed it. So far it feels same. Only thing I notice is I'm on 3g only, no LTE yet.
[HTC Rezound] Huachipato:
Dirty flashed it and noticed camera was not working right. Did a system wipe and clean install and camera is missing all together... Did I do something wrong?
[HTC Rezound] tong6998:
Make sure u flash gapps too
[HTC Rezound] Mercys Fallen:
I'm surely sure I can't flash it over on mine being s on. As I just broke my laptop I'll be hanging out on 2/5 awhile. :mad:
[HTC Rezound] tong6998:
Nvm camera not working here either...
[HTC Rezound] Jonman409:
Camera is broken because CM is in the process of removing legacy support for unofficial devices. Looks like cherry picks/fork will be needed if the camera is to work moving forward
[HTC Rezound] bacon612:
Camera not working but lte is for me
[HTC Rezound] tong6998:
Mine LTE came back after a couple reboots.
[HTC Rezound] hochoch:
Thanks for the update Neo!!!

But yeah - no camera here either. tried restoring a backup from TB with no luck.

Also, I flashed the latest 2/17 Paranoid Android (PA) full modular gapps after the updated rom and i'm getting this error: unfortunately, google play services has stopped.

I think it has to do with "people details" when syncing? never had an issue w/ this before.
[HTC Rezound] underscoredot:
Camera is broken because CM is in the process of removing legacy support for unofficial devices. Looks like cherry picks/fork will be needed if the camera is to work moving forward. -Jonman409

Well, looks like this explains my issues with the camera. Just flashed your latest build (25FEB14) and it's the exact same issue. Thanks though, Neo. Your advice still helped me fix some other issues.

---------- Post added at 02:55 PM ---------- Previous post was at 02:45 PM ----------

I know your computer is broken right now, but when you get it fixed, S-OFF is extremely easy now. No BS shorting out stuff with wires, just running code. Just go to rumrunner.us and grab the HTC Universal build. Takes about 15 minutes, but all you have to do is run it and you'll have S-OFF!
[HTC Rezound] whothefockatemychips:
Low signal and roaming issue
[HTC Rezound] bacon612:
This build incorporates cms fix on the sound profiles. Working now. So happy to have it back and functioning properly. Thanks for the build neo. Hope to see the camera back in the next one...
[HTC Rezound] Huachipato:
Thanks for mentioning this. I'm now S-Off! :)
[HTC Rezound] underscoredot:
No Problem

:good:
[HTC Rezound] Neo:
Ok so, in summary, Camera is now broken. Thanks for the update everyone
[HTC Rezound] dwasifar:
Is that just the stock camera, or any camera app?
[HTC Rezound] Huachipato:
For me it was any camera app. I would get an error message that said: Camera Error - Can't connect to Camera.
[HTC Rezound] thelunchboxosu:
Hey Neo,

What's the recovery image on the download page that was uploaded today? Anything special?
[HTC Rezound] Mercys Fallen:
I just need my damned rezound drivers.. which i can't find anywhere at all...was going to try [ to s-off ] on the work comp really fast but its bleak.

Sound at the cost of my camera is a bit high a price for me. I bike loads and take scenic pictues as I go, bit of a deal breaker to run as a day to day.
[HTC Rezound] Neo:
Some folks want the recovery that gets built with the rom. It's not necessary though.

Sent from my LG Optimus G Pro
[HTC Rezound] Chucktr:
This Looks to be more and more important...

[MENTION=3419683]Snuzzo[/MENTION], Due to the recent events, concerning the camera, it appears that your efforts may be our last hope. Any thoughts on when we might see something?? Will this camera catastrophe with CM affect your conglomeration???

Thanks,

Chuck
[HTC Rezound] draklin17:
He already relesed his rom. it is in the other development area.

http://xdaforums.com/showthread.php?t=2657961
[HTC Rezound] Neo:
Last hope? lol CM changed something that broke camera. If we'd stopped fixing issues that happen just like this every now and then, we'd have never made it to JB. I'll look into what cm changed that broke camera today.
[HTC Rezound] jhuckstead83:
I flashed 2/25 last night and my youtube isn't working. I can browse and search videos, but when I go to play them it just keeps cycling through the play and pause icons on the screen and never playing the video or even the advertisement. Can anyone else confirm?

BTW thanks Neo for everything!
[HTC Rezound] bacon612:
Yes. YouTube isn't working for me either. Says cannot play video
[HTC Rezound] mjones73:
Might as well pack up shop and go home.. :D
[HTC Rezound] Chucktr:
Ooooops... guess I did get rather rash. I jumped over to try out your Tachyon while we are waiting for a fix. Just now setting it up and learning...

Thanks,

Chuck
[HTC Rezound] El Schisne:
That happened to me with the 1/27 build. Updating to 2/3 fixed it. I haven't tried 2/25 yet.
[HTC Rezound] tong6998:
Dirty flashed back to 2/3.. Had a bunch of dropped data, when it didn't drop it was either weak or roaming, and camera too. Battery life was also lower but that might be due to signal. I get awsome signal on 2/3.
[HTC Rezound] dr_grudge:
The Google Now launcher is compatible, at least with the 1/27 build!

play.google.com/store/apps/details?id=com.google.android.launcher
[HTC Rezound] Uncleheff:
I'm still on the 2/3 build and camera is working fine on it but video is scrobbled. Maybe we can get video working on next build with camera? Also thanks Neo for all your hard work keeping our Rezound up to date. It really is appreciated.
[HTC Rezound] Snuzzo:
Last hope. Far from, just handing the torch over to something even bigger. :)
[HTC Rezound] Chucktr:
Well, it appears that I've removed any suspicions of my ignorance!! Actually, I was hoping to stir your efforts to present that conglomeration that you mentioned. Personally, I haven't been happy with most of the newer releases. Thought that your combo might make things more interesting. -And- I was feeling dejected cause the Camera didn't work in my latest build ... only to find out that it was broken. I had constructed a CM11 build the day before Neo and then while researching it found all the comments from others.... panicked and posted my message.

Thanks,

Chuck
[HTC Rezound] Neo:
Rebuilt today with a cherry pick to frameworks/av found by one of our own "damacy" which reverts all the changes made to that specific repo that was aimed at removing all legacy support. I have only just flashed the ROM to test but it appears that the camera is now missing due to the commit. I don't have time to see if the camera was built or not but if someone wants to play with it and drop a camera from a working build into it to see if it works that would be cool. 2/27 build is up. Will continue to undo the damage to legacy support cm has caused by disowning us.
[HTC Rezound] Neo:
[MENTION=3053300]wildstang83[/MENTION] and Neo like to MC :D

Probably can't share the link here so took it down lest I get a hand smack!
[HTC Rezound] bacon612:
Dirty flashed 2/27 YouTube working. Camera still says it can't connect. How do I drop a camera from an earlier build? Can I pull it from an earlier nandroid?
[HTC Rezound] REV3NT3CH:
i believe this is a source issue from cyanogenmod themselves so even if you pull the apk from an earlier build i dont think it will work....it is being looked into
[HTC Rezound] darienms1986:
Dropping in Previous camera didn't work for me, I never had the YouTube video playback issue on the last build.... an I the only one?
[HTC Rezound] bacon612:
I fried to restore camera app from nandroid backup. No dice...
[HTC Rezound] REV3NT3CH:
Again....source issue bud....not app
[HTC Rezound] Neo:
They're only doing what I asked them to do as I was unsure if the Camera was even getting built into the rom as it's now missing at first boot.

Does anyone know which is the closest build to date with working camera?
[HTC Rezound] draklin17:
I know 2/3 had it working just fine. Sorry, 2/3 was the latest one i flashed.
[HTC Rezound] darienms1986:
2/3 was the last I'm aware of
[HTC Rezound] bacon612:
Yes. 2/3 was the last. I've flashed them all.
[HTC Rezound] Neo:
So I need to check through all merged commits between 2/3-2/25.... yay..... lol

It actually won't take long to find them all

EDIT: Here's where it all started: http://review.cyanogenmod.org/#/c/59396/

I encourage those interested to read the comments below listed in that commit :eye roll:.. Just goes to show how these guys look to the newer devices and drop the older one's fast... Keep in mind the HTC Rezound, being a legacy and msm8660 device, was a flagship phone not even two years ago.

EDIT: ok SO... It looks like we need to revert the following two changes:

59396 and then 60053. I'm going to do this right now and then rebuild.
[HTC Rezound] Neo:
Neo's done coding for the day -_-

https://github.com/vigor/android_frameworks_av/commit/d14051be7a7f6c8c66a6446a9471c95f2e0f6bbe

I wasn't able to simply revert the legacy removed specific changes as these files have been modified frequently since then. Soooooooo I had to do it manually. Haven't done something like this in months. Plus I'm a vim guy and I had to use nano yuck

Building with it now. Hopefully the final product has a working camera.
[HTC Rezound] Chucktr:
Mine

I have a build that I created on Feb 10th and both camera and YouTube work.

Chuck
[HTC Rezound] Neo:
Fixed it

Fixed Camera :D

Now it's the borked video playback from camcorder to work on next week.

New build is up with the most updated source and fixed camera. Haven't tested youtube or any of that yet.
[HTC Rezound] PTuT:
Nice job Neo. Good we have you as a part of our community. Thanks goes to all Devs here for their time and willingness to keep Rezound up to date.
[HTC Rezound] foggytown:
Can verify that camera works on 2/28 build.

Thanks for this and all that you do, Neo!!
[HTC Rezound] Chucktr:
Thanks

Does this mean that I can do a fixrepo and build and get the same thing??

Thanks,

Chuck
[HTC Rezound] voldrix:
How to change vocoder settings

I have the 2/25 build installed. It is running fine, even with ART. But I have been unable to figure out how to change my voice codec. I am on Verizon. It used to be ##PROGRAM on stock rom. In the codes i've found for CyanogenMod, the *#*#4636#*#* info screen seems to be the only one that works. And I can't find it in the settings anywhere. How can I access the vocoder settings?

Thanks for the help and great work on the project.
[HTC Rezound] jhuckstead83:
Just dirty flashed 2/28... Nice work Neo!!! Camera works, and YouTube works... I tried the camcorder and it records but the video is all scrambled up...

Thanks for all the hard work!!!
[HTC Rezound] Neo:
Repo sync, then commit this to frameworks/av:

https://github.com/vigor/android_frameworks_av/commit/d14051be7a7f6c8c66a6446a9471c95f2e0f6bbe

Don't forget to git revert the merge in vendor/cm to use the older boot ani:

git revert --no-edit b71b47d72b129915327f41653b06edaea5008534 || retval=1

I'm going to be testing something to possibly fix camcorder in a min.

Working on it ;)
[HTC Rezound] dwasifar:
My wife broke her Rezound and I bought a replacement on ebay, meaning I was starting from zero when I installed this rom - a stock OTA ICS, locked bootloader, S-On. I thought I would be okay with doing htcdev unlock, juopunutbear S-Off, flash a recovery and then Neo's CM11. But when I got done, it was boot looping. Tried a couple of other roms I had on hand - Evervolv and LiquidSmooth - and they both did the same thing.

So I flashed this ICS RUU, unlocked again, flashed recovery and the rom, and everything was fine after that. I have never seen the bootloader say ***TAMPERED*** in either of my other Rezounds, but it did this time, and it went through the RUU load twice for some reason. So I don't know what the issue was. Maybe these builds just don't like the juopunutbear-patched HBOOT. But the final process of unlock, S-Off, RUU, unlock, flash recovery and rom seems to be what was needed.

Just a note in case it helps someone. I've seen others complain of boot loops, maybe this will help fix it.
[HTC Rezound] Neo:
It simply depends on the hboot you installed. Mine has said tampered since I first unlocked so all is good.
[HTC Rezound] bacon612:
Anyone confirm that USB tether is working for them? I hardly ever use it but I just tried and had no luck. HTC drivers loaded. Running win7 x64.
[HTC Rezound] dwasifar:
Well, it changed a few times. After the first unlocking it just read UNLOCKED, then during the juopunutbear process it went to TAMPERED and UNLOCKED. After finishing juopunutbear TAMPERED was gone and it just said Juopunutbear. During reflashing of the RUU it rebooted twice; the first time it came back to bootloader showing TAMPERED and LOCKED, and the second reboot just LOCKED.

I know the juopunutbear process loads an altered HBOOT, and I guessed that was the reason for both the TAMPERED notice and the boot loop.

Every time I use that thing I wonder why they didn't call it juopunutBEER. It talks about beer a lot.
[HTC Rezound] Neo:
It does. You need to troubleshoot the driver conflict on your PC and switch it to rndis I believe.
[HTC Rezound] pball52998:
Lol so does rumrunner. I don't get what's with s-off and beer/alcohol lol

Sent from my Rezound running sense 5/Liquid Smooth/Cyanogenmod 11. S-OFF
[HTC Rezound] dwasifar:
Did you have good experiences with rumrunner? I already had both Rezounds S-Off by the time rumrunner came out, and so with this new third one I just did what I was already used to. I saw a lot of people in the rumrunner thread complaining about problems with it, including one guy who seems to think it hard-bricked his device, but OTOH there's no shortage of people who couldn't master juopunutbear either.
[HTC Rezound] DCnovicky:
The hardest part of rumrunner was typing the word "yes" a couple times, Lol.

So does the unannounced 3/1 build fix camcorder? :)
[HTC Rezound] Chucktr:
Think this shows I still have a lot to learn...

I'm still new at this... How do I do a 'commit' ??

I presume that the 'git' is performed from the command line 'inside' vender/cm ... correct??

Thanks,

Chuck
[HTC Rezound] Neo:
Nope lol I'm going to keep trying though

cd into frameworks/av and then do this:

git fetch https://github.com/vigor/android_frameworks_av cm-11.0 && git cherry-pick d14051be7a7f6c8c66a6446a9471c95f2e0f6bbe

That is how you cherry pick from github.

git fetch urlOfRepo BranchName && got cherry-pick CommitID(sha)
[HTC Rezound] dwasifar:
Maybe I missed it, but does this latest build fix the LTE data drop issue?
[HTC Rezound] Neo:
I've been waiting to hear if anyone has noticed it fixed or not. I made some changes

Sent from my LG Optimus G Pro
[HTC Rezound] darienms1986:
Mine has been fixed. But takes about a minute upon boot to connect. Other than that switches great and reconnects when you do actually have a loss in service! So thanks neo
[HTC Rezound] dwasifar:
Great. I just dirty-flashed the 0301 build over 0127 to try it out. I rarely ever use camcorder, I can do without that for a while. Will report my findings.
[HTC Rezound] darienms1986:
Any big changes with 3/1 that I should even consider flashing?
[HTC Rezound] Neo:
no different than the previous day other than using a different repo for camera which did nothing.
[HTC Rezound] z3pp3lin:
Camera & camcorder both work again.
[HTC Rezound] Chucktr:
I presume that the 'got' should really be a 'git' ??
[HTC Rezound] Neo:
Yeah that autocorrect gets me every now and then
[HTC Rezound] Chucktr:
Problem child...

Ok. It didn't work. -But- before others get upset... can we move this conversation over to the Build Forum at

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

Thanks,

Chuck
[HTC Rezound] magwua:
Camera working in 3-1

Just clean flashed the 3/1 and banks Gapps 2-27 and was able to take a picture. Havent had too much of a chance to do much else yet but Thanks Neo .:D
[HTC Rezound] Neo:
This is the Developer's thread (me) and the conversation regards the rom and I do not mind the discussion taking place here.

However, for more immediate assistance, and and anyone else for that matter are welcome to message me "live" via hangouts at DavidEddlemon@gmail.com if you have any questions or concerns. All you need to do is cherry pick those two commits and build.

You're welcome.
[HTC Rezound] dwasifar:
So far so good. LTE has been consistent. Camera works. Haven't bothered to try camcorder.

Edit: posting that made me feel like a lazyass, so I tested camcorder. Stock camcorder appears to work but produced garbled videos. However, I also have Lenovo Super Camera installed, and the camcorder app on that works just fine. So I think this might be a gapps problem and not a rom problem.