yashsingh1/xdaforums huggingface dataset:
[HTC Rezound] tong6998:
Been using this since the beginning of the year when I got the phone from a co-worker(upgraded from a Dinc). Was on older h-boot and radios and running the latest release dirty flashed over the early January one. Only problems I've had were : Intermittent data loss (just click the radio off and on and its back), lock screen would go blank but if you remember your pattern and put it in the right spot it still unlocks. The later I determined That as long as I left it in my home screen ( not in an app) it would not happen... And hugely atrocious GPS I mean so horrid its dumb founding.

Great ROM nice and fast otherwise.

Spent all day yesterday redoing phone, falshed latest hboot/radios. Cleared everything (but my SD) and dropped this in clean (didn't do a backup so lost all NY stuff). So far no disappearing lock screen, no data issues (but that only happened at about 10am ish EST every time and after 1pm). My phone hasn't heated up like usual (think I got a hot one), but the GPS really really sucks...

Will update after a few days if anything changes.
[HTC Rezound] pball52998:
Dang I thought I was the only one having these problems to... Lol obviously not. And even on my just internal storage I get like KB/s or bytes per second -,,,- took me 15 minutes to put a grateful dead album on phone this morning. Lol... any reason why this would happen? And neo having the same problem with the roaming when it should be 3G :$ loving the ROM though!! Besides the roaming and data transfer everything is great :D the Rezound community is the best!!! :D
[HTC Rezound] darienms1986:
I've got amazing gps.... wonder what gives with yours
[HTC Rezound] dwasifar:
Yeah, I've tried the Team bar, but it doesn't work as well as baked-in. With default settings, it stays on over my night clock; setting it to hide with the status bar fixes that, but then it doesn't return from sleep reliably. No big deal, I don't really need it.

Back on topic: data connection seems steady so far on the 0127 build. Was out driving around all day and it never lost data. I have 2.22 base, if that matters. The only thing I haven't tested yet is bluetooth calling, but that was fine on the 0203 build and I expect it to be no different on the 0127.

Regarding GPS, mine is pinpoint accurate. In Google Maps last night, it put the map pointer not just on the little white box that depicted my house, but actually in the right place inside the box for where my bedroom is.

FWiW: I know most people here prefer TWRP, but I flashed using Amon Ra with no problems. Did all recommended wipes 3x, just because.
[HTC Rezound] tong6998:
Don't know at all, spent at least an hour trying to get a lock with GPS stats and got nothing. What are you guys using for location settings to get yours to work great? Is there another radio or somethign I can update or need to update?

On another note, all day no data loss, and as far as heat, big difference, updating the radios/hboot now reduced the heat that was being put out of the phone. It used to get to the point where it was almost too hot to touch, now after at least all morning surfing, and trying to get a GPS lock, it is warm but not too bad, according to GPS stats, it only got to 111F after 1/2 hour drive looking for GPS. Noteworthy: OEM extended battery with OEM case with the otterbox defender with no rear plastic cover, just the rubber and front cover.

Lock screen disappearing: was doing real good, in fact I thought it was gone but to no avail.... happened once already, but as with before I had left in an app, so as long as I'm at my home screen it doesn't happen.

Tong
[HTC Rezound] darienms1986:
Just a thought but try your stock battery and back cover! It may be tied to the antennas on the back cover.
[HTC Rezound] scy1192:
You can get one through Xposed
[HTC Rezound] ncfoster:
I don't know if this helps, but I have been on the 0112 build for a while, having major silent data drop issues as well. So, I will try 0127 to see if that resolves it. But, I don't think that the problem is unique to the 0203 build. I somehow missed that people were doing okay with 0127, or I'd be on it already. Otherwise really happy with the ROM. Only a few very infrequent reboots.
[HTC Rezound] darienms1986:
I've had the data drop on all 3 of those builds. But after a 2nd clean full wipe I no longer have it on the 2/3 build
[HTC Rezound] ncfoster:
Thanks for the tip. I guess that I will either bypass these builds, or do some serious wiping.
[HTC Rezound] darienms1986:
Yeah I was about to just come to the realization of just dealing with it lol glad it worked itself out with a few wipes
[HTC Rezound] ncfoster:
I have Titanium Backup Pro, but I haven't ever really used it to its potential. It seems like I've read that it is often not worth the trouble, especially with recent ROMs. In any case, I am a bit leery to reinstall everything over again if the result is in doubt...decisions, decisions.
[HTC Rezound] darienms1986:
I don't use any back up apps. Ever. I just clean install always to ensure I have no residual issues
[HTC Rezound] dwasifar:
Thanks, will check it out.
[HTC Rezound] Rigo 74:
I've been playing with this for a day now trying to recreate the dissapearing lockscreen with only statusbar displayed that I was getting ,only when bringing phone up from sleep the one thing that seems to be fixing it up is setting min CPU to 384 its happened once in the last 8 hours and I was able to click home button and get back to home screen anyone else confirm this? Or just a fluke
[HTC Rezound] Neo:
May look into that
[HTC Rezound] :
I need to get you a T-Mobile device or two Neo, I haven't had a good ROM since I left the Rezound.
[HTC Rezound] Neo:
What did you move to again?
[HTC Rezound] :
Nexus 4, S4 Active, Xperia Z, Note 2, Xperia Z1s for Android, I haven't really held down one device for long, especially working for tmo. I've had a Note 8.0 for a while though
[HTC Rezound] gunzup3:
Figured i would throw this out there, I've been runnin the litz version from pg 72 i think with no issues to speak of, cpu min 384 and maxed out on top. I switched to straight talk about a week ago and couldn't get gsm workin so i flashed a gsm zip from evervolv and been working great, do kinda miss my 4g but can live with it for now.
[HTC Rezound] whothefockatemychips:
My rezound no longer reads the internal sd card what do I do?!?
[HTC Rezound] pball52998:
Every time I reboot my phone I have to redo my CyanogenMod stuff. And my Google play services keeps "not responding". Don't know what could cause that. But still good :$

Sent from my Rezound. CyanogenMod 11. S-off
[HTC Rezound] draklin17:
Would anyone know why my phone doesn't have USB mass storage when i plug my phone into my computer? It will charge but i no longer gf=et the option to turn on USB mass storage. I clean flashed the 2/3 build.
[HTC Rezound] netookska05:
http://xdaforums.com/showthread.php?t=2619828
[HTC Rezound] pball52998:
Go into settings, click storage. Click the 3 dots in the top right hand corner. Then click the 3rd one. "Mass Storage (UMS)"

Sent from my Rezound. CyanogenMod 11. S-off
[HTC Rezound] bacon612:
I am getting the CM message from time to time on reboots requesting me to login and select my time zone etc as if its a fresh install. Strange. I also lost all of my saved SMS messages the other day. Not sure if its all related to the issues with data loss people are reporting. Who knows.

In other news, it looks like cm11 milestone 3 dropped

http://www.xda-developers.com/android/cyanogenmod-11-milestone-3-now-available-for-50-devices/

Will we be seeing a fresh new build? :D
[HTC Rezound] pball52998:
Well from what I see its like a lot of peoples phones for CyanogenMod 11 are still nighties. Not stable at all. But then there's us and its like, wow were pretty stable, running a old device and being relatively stable with most things working. I would like to see this thing as stable it can :D so I can expect neo to be building some good stuff ;) thank you devs :D

Sent from my Rezound. CyanogenMod 11. S-off
[HTC Rezound] onthehole:
Just bought an HTC One. Already see some familiar names over there and am excited for neo to maybe pop by in the future. My rezound is still banging and I can't wait to come back here and try future neo builds on my rezzy. Best development community period You guys are amazing. Thank you so much for everything Neo and team Rezound.

Sent from my HTC Rezound.
[HTC Rezound] Jonman409:
I believe they're unrelated. I've noticed signifigantly more files/filesystem corruption since the kernel optimization changes.

I believe the issue with a lot of the data issues should be fixed with this commit. http://review.cyanogenmod.org/#/c/59171/

I haven't been able to test since i've been on a business trip, but it might be worthwhile to check Neo.
[HTC Rezound] Mercys Fallen:
Does coredroid not work with cm11? I currently can't open it or get the old zips to flash effectively:confused:
[HTC Rezound] el Filou:
Isn't CoreDroid designed for Sense ROMs?
[HTC Rezound] Mercys Fallen:
I worked when I was using infected a few months ago. However I could be mistaken
[HTC Rezound] bacon612:
I just tried to download a torrent using ttorrent and I get errors about ten seconds into the download writing to either sdcard0 or sdcard1. It worked fine a few builds back. I also wonder if this is related to the kernel changes people are talking about.
[HTC Rezound] dwasifar:
I did eventually experience the data drop on the 0127 build once or twice, and I also noticed a little bit of interface hesitation with the music player going (dsub). Snuzzo thinks he's licked the data problem in Carbon, maybe this will help: http://xdaforums.com/showpost.php?p=50185850&postcount=1186

As an experiment I flashed Evervolv last night to see if it had the same issue. It looks like the data's okay so far, and it's pretty responsive. But I miss some of the baked-in things in CM (DSP manager, quiet hours, expanded volume control that decouples ring and notification) so I'll probably come back to CM11 by the end of the week if not sooner.
[HTC Rezound] acejavelin:
Not to go too off topic, but how could you not have had a good ROM on those devices, especially the N4? There are like a bazillion different ones, Beanstalk being my personal favorite... But almost all of those have very active developer communities.

Not to detract from Neo, who is awesome!
[HTC Rezound] bacon612:
Logcat attached. Not 100% sure if i did it correctly. If anyone out there wants to take a stab at looking and needs me to do it again, gladly will.
[HTC Rezound] tlfromva:
Soft keys losing sensitivity. I saw a post somewhere about changing a build prop setting but can't find it. I've not modified a build prop before. Can anyone walk me through it. It's frustrating to use the phone now.

Sent from my phone running CM 11.0
[HTC Rezound] YTHero:
I had an issue where my capacitive buttons stopped working altogether. I ended up editing the build.prop to enable the Nav bar, and I haven't looked back since.

Basically, you just need to add "qemu.hw.mainkeys=0" to your build prop to enable the Nav bar. I'm still on CM 10.2, but I assume it would work for CM 11.

Here's the thread where my issue was discussed, I want to give credit where credit is due.

Edit: If you are timid about editing build.prop, just google the topic, there are plenty of guides out there. Moreover, it's really not a big deal, so don't worry about it.

Just make a backup of the file first so you can go back if you need to, then after that it really is just as simple as adding a line of text in a text editor.
[HTC Rezound] dwasifar:
I tried loading Carbon to see if that was any better, but for some reason I can't get a successful Carbon flash; it works fine until I reboot and then hangs on startup. Probably I'm not using the right recovery. Evervolv is okay but I missed the polish of CM, so I am back on CM11 0127 build. I experienced the data problem twice today, but in both cases a quick toggle of LTE fixed it.

Thanks again to Neo for this excellent work.
[HTC Rezound] ncfoster:
Ended up dirty-flashing 0203 build over 0112. My "silent data drop" problem seems to have changed to a less-silent "often roaming" situation. As best I can tell, they are the same problem with the only difference being whether I can tell it happened or not. Hope that whatever snuzzo thinks that he figured out on Carbon will migrate back soon. Will probably be moving to a Moto X on T-Mobile soon, thanks for all the work, Neo.
[HTC Rezound] tlfromva:
Thanks. It worked fine and I'm back in business. Much relieved.

Sent from my LG G-Pad 8.3 Google Play Edition
[HTC Rezound] dwasifar:
I reported earlier that I'd had general interface hesitation when using the music player. That seemed to have gone away on its own.

This morning I discovered that DSP Manager had crashed, and even though its settings page appeared to be working, it wasn't having any effect on the sound, even after a reboot. I cleared DSP Manager's data in Apps, and rebooted again; afterwards, DSP Manager was working again, and the hesitation in the interface was back.

So it now looks like the interface slowdowns were caused by DSP Manager, and not the music player as I previously thought.

Has anyone else noticed this happening?
[HTC Rezound] bacon612:
I have noticed the slowdowns from time to time. I see it mostly in the swipe down from the top when it happens. Becomes choppy. I've never even opened DSP manager before though. I would imagine that it wouldn't be DSP manager. Who knows.
[HTC Rezound] swing4thefence:
It worked for me. Also for the guy nervous about editing build prop room toolbox had a build prop editor built in.
[HTC Rezound] dwasifar:
I think unless you disable DSP Manager in Settings > Sound, it's active any time sound is playing. Could be wrong though.
[HTC Rezound] dwasifar:
Wow, looks like Snuzzo's thrown in the towel on Carbon for the Rezound. He left a "that's all, folks" message and closed the thread.

Neo, did you get anything useful from Snuzzo on the data-drop problem before he wrapped it up? Or did that turn out to be something else?
[HTC Rezound] Huachipato:
I had good luck with this ROM using BaNKS core GAPPS (most of BaNKS GAPPS builds are designed for the Nexus 5 - but the Core on just puts the Play Store in there and you can download the rest from there). Running in ART caused a few error messages to pop up every now and then - but in Dalvik it seems quite stable for me.
[HTC Rezound] REV3NT3CH:
theres a certain method on install but use banks standard gapps for art...no force closes at all bud
[HTC Rezound] Huachipato:
It was Picasa upload that would close when I took the phone off the charger. There was some other app that would close less often and randomly - can't remember which one it was at the moment. It was very stable for me aside from that. I don't feel a need to be running ART - just wanted to see what it was all about - to be honest I did not notice much of a difference in the way I use my phone. I switched back to Dalvik yesterday and have not seen any errors show up since then.
[HTC Rezound] REV3NT3CH:
well if you set up art correctly your phone will run alot smoother for games and other stuff....handles your memory alot better....BUT as i stated theres a certain method you have to use when switching to it....yo wont notice a difference really if it was setup improperly
[HTC Rezound] magwua:
1st post, 4.4.2 working on my rezound

My 1st post, but I wanted to say thanks for all of the hard work.

I rooted and flash my Rezound for the 1st time today and with the exception of accidentally making it s-on and having to do a couple extra steps things went really smooth.

The Rom (2/03/14) is working great so far and I am glad I upgraded from the stock 4.0.3. Thanks! :good:
[HTC Rezound] :
Dumb question here... I definitely want to install this ROM but noticed on the first page that certain features don't work depending on if your Rezound is ION vs PMEM vs HYBRID. I tried googling these terms to figure them out, but I still cannot determine which one applies to my particular Rezound. Could anyone point me in the right direction?

Also, assuming my phone is HYBRID (which seems to have the least number of things not working), would people say it's mostly fully functional for day to day things (internet, calls, gps, camera, etc)?

Thanks for all your help!
[HTC Rezound] dwasifar:
Those describe the memory allocation scheme, not the hardware they run on. When Neo first put this rom up and made that first post, he had a version that used PMEM, one that used ION, and eventually one that used some of each (the hybrid). Each version had its own limitations. Now those have been mostly sorted out, and the download page contains only the Hybrid, which is what you will use.

As far as day-to-day functionality, I am using the 0127 build for my daily driver, and it's very smooth and stable and works well; all the things you mention work perfectly except for a small problem with data connectivity. Occasionally LTE drops and the indicator doesn't tell you it's gone; when that happens, toggling mobile data or airplane mode sets things right again. I notice it happens most when moving through areas where the phone has to constantly reacquire signal. This is an issue that crept in sometime during the last few releases, so I expect we'll see a fix soon.

Compared to the other KitKat builds I've tried, this rom is more stable and more full-featured.

Hope this helps.
[HTC Rezound] Neo:
It was time to move on like many before him. We still chat and share ideas in Google hangouts. I too will be upgrading at some point next month and development for this device from me will even further slow down. I will continue to do what I can of course but as many of you have already noticed, I haven't been nearly as active as I used to be. I hope to at least get my personal rom update out with tachyon-2.0 before then and hopefully with the data issue resolved. Same with this vanilla build.
[HTC Rezound] pball52998:
Hey neo what device will you be moving onto? I think I saw that snuzzo moved to the g2? What are you moving to? But anything from any Dev especially you or Snuzzo is appreciated. I think a lot of the Rezound community can say that :D the Rezound community will miss you and Snuzzo a lot! :( Good luck with later devices!!! :D
[HTC Rezound] Snuzzo:
[MENTION=5642430]pball52998[/MENTION]

Even though you did hear correctly, I might stay and build for the Rez for a little while longer. Working on a small project that involves a rom strictly made for the Rezound.
[HTC Rezound] mengma021:
about the battery button

Great thanks to everyone, but also I have an issue that sometimes when I push the battery button, the screen doesnt turn on, but the four LEDs is turn on, so I have to push the battery button again. I dont know how can I do to resolve...
[HTC Rezound] :
That's super helpful, dwasifar!! I appreciate it. Two follow-up questions:

1) is there a way to know when those LTE issues will be fixed? I saw that there is no changelog being posted for CM11, so I'm not sure how to follow when fixes are made

2) when a new build comes out, do you re-flash the new ROM build (which I'd assume entails wiping your internal data each time), or is there some other method for always having the most up-to-date build?

Thanks again!
[HTC Rezound] Hobox10:
Okay, so I switched the preferred radio from LTE to 3G because I wanted to force the phone into 3G only for a bit. The radio would not switch over and showed R only. Not just that, but it wouldn't switch back to LTE after I had done so. So I rebooted the phone...

And now it won't boot. It has been on the CM boot logo for about half an hour. Why would switching the preferred network cause this..?

EDIT: I wiped cache/dalvik and dirty reinstalled the 2/3 build and it won't boot still...
[HTC Rezound] Chucktr:
Can you all leave any hints...

Is there any chance that you and Flyhalf, Snuzzo and _litz could leave some hints on the changes that you make to get the CM11 software to work on the ReZound??? It appears that the repo just goes out and gets the latest CM11 code from their site and then we use the stuff in the Vigor directory. I know it is NOT all that simple, if it were, more people would be doing it.

So, I ask again, is there anything that you and the others can leave for us that "don't want to leave" but would like to update?? I finally have been able to get successful builds. Just had to get my directory structure straight.

I realize that this is a lot to ask... but then the worst that could happen is you say no. At any rate, to you and all the others,

Thanks a lot for all your efforts,

Chuck
[HTC Rezound] DCnovicky:
Currently on 1/27 build. Has been rock solid. Found a reason to use camcorder today but play back is fubared! Can anyone else confirm this. Thx

Well after trying it on my wife's phone I can confirm its broken.

Can anyone comment on 2/3 build?
[HTC Rezound] Snuzzo:
[MENTION=4881300]Chucktr[/MENTION]

I'm a makefile, bash scripter, and themer type of guy. Usually can get stuff to boot/build out of existing code with minimal modification.
[HTC Rezound] dwasifar:
The LTE issue seems specific to the unofficial Rezound port, so you wouldn't hear anything from Cyanogenmod proper. The answer is, watch this thread. We know Neo will be moving on to another device soon - which will be a tragedy for us, btw - but he is as frustrated by the data issue as anyone else and is working on getting a fix out before he moves on. This fix is also intended to appear in his more-highly-customized rom Tachyon; he's working on v2.0 of that right now, which I presume will be a KitKat build. Read the last few weeks of this thread, that'll bring you up to speed.

For new builds of the same rom, you have the option of trying a "dirty flash," which means just flashing the new version without wiping anything except cache and Dalvik. If the changes aren't major, that can often work fine. Best to back up anything important to you first, of course. The worst that can happen is that the phone gets unstable, and then you just do a wipe and clean flash instead.
[HTC Rezound] magwua:
2 issues

So I am pretty new to rooting and flashing (Haven't done anything since flashing my OLD Audiovox PPC-6700) but I flashed this 4.4.2 (2/03) rom using CWM Touch 6.0.3.6. My phone is "s-on" so i used the steps listed in the FAQ "Q3: Is this ROM S-On compatible?" to flash my device.

I have 3 issues with the first one being the most important..

1. External SD card does not mount properly. I say that because the Camera does no recognize it and I cannot open any pictures on anything off of it in the OS. i can browse to files using the built in file manager but not open anything up

2. My phone is no longer recognized by my computer. I checked the items in "Q10" of the FAQ but it still isn't recognized.

3. Trying to open "wallpapers" gives me an error that Google Search has stopped.

Thanks again everyone!
[HTC Rezound] pball52998:
Just dirty flash over. I do it all the time with all the new builds (with switching from a other ROM wipe everything but external SD). Always do a backup before doing any flashing though. But I've read that doing a clean flash is good after every couple of good dirty flashes, don't know if its true, but I just follow that, I clean flash like every 3-5 new builds. Keeps me running smooth. Although after dirty flashing or clean flash, always wipe cache and dalvik. Then if s-on boot to bootloader and do "fastboot flash boot boot.img" (without quotes) all that good stuff. Then yeah if s-off none of that applies and just reboot after flashing.

and [MENTION=3419683]Snuzzo[/MENTION] all work from you and [MENTION=4203241]IAmTheOneTheyCallNeo[/MENTION] is appreciated. Love to see any work from you guys :D with the G2 though, are you staying with the Verizon G2 or are you moving on to another brand?
[HTC Rezound] play3r:
3G boot problem

There used to be a problem on the stock Rezounds, that it wouldn't boot properly in 3G ... mine would boot loop. A workaround was to remove the back, thereby disconnecting the anttenna. Then it would boot. And, you could change back to LTE

Maybe this would help you? Hope so,

Play3r