yashsingh1/xdaforums huggingface dataset:
[HTC Rezound] HokieCoder:
[MENTION=3082717]Flyhalf205[/MENTION] Thanks! I ended up just downloading from Dev-Host once you said it matched what you had on your phone. The MD5 checked out and the flash went successful. Hopefully a newcomer can report back on downloading from goo.im.

One "issue" I noticed with the 6/1 build was that when I connected my phone via USB to my computer, it created a LOT of removable media drives (6 extra, if I remember correctly) in addition to the internet and external storage drives. It was repeatable every time I connected to the computer. I was not able to test this on multiple computers, however, before flashing 6/3. Good news is that on 6/3 the problem is no longer there. Not sure if it was just a random oddity with my particular flash of 6/1 or a problem for everyone on 6/1, but it might be something to check out in future builds just to make sure!

We can't say it enough....thanks for your hard work with this great ROM!!
[HTC Rezound] Snuzzo:
Check back into the AOSP dev thread. It's been reported already and corrected. :) I'll be bringing the fix over soon.
[HTC Rezound] Flyhalf205:
When I brought over the USB Tether fix. I didn't finish cleaning up the board-vigor so it created the extra 6 devices. I finished it up yesterday with this commit https://github.com/Flyhalf205/vigor_aosp_kernel/commit/09614f7774b5a0c03a4577c3375ff467208f8d64 so it's working great now. Thats why I posted 6/3.

If you flash any other kernel. You will get the extra 6 devices btw. Just until the other devs add that commit into their kernels
[HTC Rezound] HokieCoder:
Sweet, glad to know you were aware of the issue and it's already fixed! :highfive:
[HTC Rezound] lukester01:
kernels

I tried HIRO 5/31, but it still seemed to have serious issues with getting bogged down so bad that I would get black screen of death. So went back to Funky 3.4
[HTC Rezound] tigerxchaos:
I've been getting the bog-down issue on Funky, HIRO, and on the stock kernel. I finally clean wiped again and installed 6/2 and have left it with the stock kernel. I reinstalled all my programs manually instead of letting Titanium do it, and only restored the most essential app data from my backup. Installed the most minimal gapps build and manually installed the rest. The bog-down issue seems to be minimized now but hasn't been completely eliminated. I've noticed it happening most frequently when running Facebook. This stuff wasn't happening before the 5/25 build, so I'm not sure what the deal is, but I'm out of ideas for how to circumvent it.
[HTC Rezound] bacon612:
SMS working for everyone on 6/2? I'm downloading 6/3 now but cant seem to send texts
[HTC Rezound] Flyhalf205:
I had problems on 6/2 also.
[HTC Rezound] bacon612:
Cool. Glad its not just me. Functional on 6/3? Anyone know yet?
[HTC Rezound] Flyhalf205:
For me it's almost like the first 10 seconds after I turn screen on. The phone is extremely slow but then speeds up. [MENTION=3419683]Snuzzo[/MENTION] any fix or idea for this? Almost like it can't wake up from a deep sleep.
[HTC Rezound] Flyhalf205:
So far so good with SMS on 6/3.
[HTC Rezound] Snuzzo:
[MENTION=4218522]tigerxchaos[/MENTION]

How full is your int/ext storage? Can you get me a kmsg when it happens next(doubt its kernel) although...

[MENTION=3082717]Flyhalf205[/MENTION]

It could be too many apns in ril

Sent from my ADR6425LVW using Xparent Red Tapatalk 2
[HTC Rezound] Flyhalf205:
That would slow it down a reboot wouldn't you think? Not during the waking process
[HTC Rezound] Snuzzo:
Unless its slowing data down to 1x.

Sent from my ADR6425LVW using Xparent Red Tapatalk 2
[HTC Rezound] Flyhalf205:
Data speeds are normal. Just happens when waking up the phone.
[HTC Rezound] Snuzzo:
When screen is blanked?

Sent from my ADR6425LVW using Xparent Red Tapatalk 2
[HTC Rezound] Flyhalf205:
Yes... It appears it only happens when waking after it goes into deep sleep.
[HTC Rezound] hceuterpe:
Heh, was that a mention from my earlier post about USB tether? :)

I think I know what's going on with encryption. It looks like qcks is getting loaded too early. I noticed /data/qcks files change every time on boot for nonencrypted, but not when it's encrypted anymore. I think those are the radio firmware files. I suspect the offending line is:

service kickstart /system/bin/qcks lc

class main

oneshot

The combination of the 'class main' and 'oneshot' means it's starting before the encrypted data partition (class main), and it's not getting restarted after decryption of data (oneshot). I'm going to try tweaking how that starts...
[HTC Rezound] tigerxchaos:
For me, the slow-downs weren't happening just when waking up the phone. Some apps (Facebook, Pandora, and if I recall a couple others) were triggering the issue when trying to scroll, using the back button to exit the app, and sometimes rotating the phone as well. Usually when this would happen, the screen would go black except for the status bar, which would seem to go back and forth from being normal to frozen and back again while the issue was going on (I could tell due to the rotating battery icon when plugged in). In general, the phone would never fully recover from this, making it near-impossible to use until I fought to the reboot menu or simply pulled the battery.

Snuzzo, I'm happy to try and get you a kmsg, but I don't know how to do that. I did a google search and found this: http://bootloader.wikidot.com/linux:android:kmsg Is this what you are looking for? I'm not sure how to find it after it gets dumped either, or how to turn off the dumping. Sorry, I'm still learning my way around linux.

Sizes: I noticed something odd when I checked this.

External SD Card: 25.33GB free of 29.81GB

Internal storage: 1.51GB free of 2.34GB

Internal SD card: 10.48GB free of 10.49GB <---shouldn't this be closer to 16GB? When I did the juopunutbear S-OFF wire trick, I installed the wrong hboot at first and it screwed up a previous SD card by messing up the file system on half of it. I now realize that in TWRP when I'm doing a wipe, the "Internal SD" is listed twice there. I'm wondering if that's part of my issue here...
[HTC Rezound] HokieCoder:
I am pretty sure I am correct on this.....the answer is no. The phone has 16GB of internal storage, which approximately 5.5GB of it partitioned off for the system/data/whatever partitions. So after the ROM allocates all the space that it needs, we end up with 10.49GB of usable space on the "internal SD". Mine is like that, too, as I never put anything on it since I have a 64GB microSD card in mine.
[HTC Rezound] lukester01:
bog-down

What you describe with the bog-down is exactly the issue I've experienced with HIRO. I rarely have had it with Funky, but rarely, and only when I was using a governor like Scary, but not when using a governor like Lulzactive or Badass. Also with HIRO but not with other kernels I've had the black screen of death when it is waking from deep sleep, a big problem for the morning alarm, IHWO thought it had to do with MPdecision.
[HTC Rezound] Hobox10:
There might be something wrong with widgets in 6/1 and I haven't updated to 6/2 yet to check if it's in it also, but it might just be a bug with UCCW. None of the widget sizes are correct, if I try to pick 4x1 it keeps doing 4x2. UCCW had an update at the same time I installed 6/1 so I can't tell which.
[HTC Rezound] lukester01:
widget size

This happens with Nova as the launcher, but then I just resize the widget. It's been doing that with Nova for as long as I can remember.
[HTC Rezound] wildstang83:
Yea I'd check that all the default android widgets are correct first. If so then you can lay blame on uccw.
[HTC Rezound] Hobox10:
I'm using action launcher but yeah I think the issue is with UCCW now.
[HTC Rezound] tigerxchaos:
Yeah, my widgets all have to be resized in both Nova and Trebuchet, and repositioned as well, if I change away from 4x4 grid size. I figured it was just a limitation of those launchers. ADW still works properly but animations are pretty choppy in that launcher on this ROM, so I switched away from it.

---------- Post added at 05:53 PM ---------- Previous post was at 05:51 PM ----------

I was pretty consistently running Wheatley on both HIRO and Funky, both before and after this issue started. I don't think it's the governor for me, since it's still happening now (just to a lesser extent) with the stock kernel. I believe both cores are running the interactive governor.
[HTC Rezound] cristianpark:
I need the patch in order to have EDGE (without flash it I only have GSM Call capabilities), maybe some APN missing for my region in default CM. GSM patch doesn't break anything in my cell for the moment. Great advances on CM10.1 for our Rezounds thanks FlyHalf
[HTC Rezound] Flyhalf205:
Just don't do a factory reset after flashing the gsm patch. Do you known what your APN is and I can add it into cm?
[HTC Rezound] cristianpark:
Thanks for the tip Flyhalf

The APN's for my country carriers are (my current carrier is Tigo Colombia):

<!-- APN'S COLOMBIA START -->

<apn carrier="COMCEL" mcc="732" mnc="101" apn="internet.comcel.com.co" user="COMCELWEB" password="COMCELWEB" type="default,supl" />

<apn carrier="COMCEL MMS" mcc="732" mnc="101" apn="mms.comcel.com.co" user="COMCELMMS" password="*********" mmsc="http://mms.comcel.com.co/mms/" mmsproxy="198.228.90.225" mmsport="9201" type="mms" />

<apn carrier="Movistar CO" mcc="732" mnc="102" apn="internet.movistar.com.co" user="movistar" password="movistar" type="default,supl" />

<apn carrier="Tigo MMS" mcc="732" mnc="103" apn="mms.colombiamovil.com.co" user="mms-cm1900" password="mms-cm1900" mmsc="mmsc.colombiamovil.com.co" mmsproxy="190.102.206.48" mmsport="8080" type="mms" />

<apn carrier="Tigo" mcc="732" mnc="103" apn="web.colombiamovil.com.co" type="default,supl" />

<apn carrier="OLA" mcc="732" mnc="111" apn="internet" user="internet" password="internet" type="default,supl" />

<apn carrier="OLA MMS" mcc="732" mnc="111" apn="mms.comcel.com.co" mmsc="http://mms.ola.com.co" mmsproxy="200.058.228.081" mmsport="9201" type="mms" />

<apn carrier="Movistar CO" mcc="732" mnc="123" apn="internet.movistar.com.co" user="movistar" password="movistar" type="default,supl" />

<!-- APN'S COLOMBIA END -->

It'll be great if you can add them, I'll test it as soon as you release some build with them on it

This lines of the script in the GSM Patch:

sed -i 's/telephony.lteOnCdmaDevice = 1/telephony.lteOnGsmDevice = 1/g' /system/build.prop

sed -i 's/ro.telephony.ril_class = HTCVigorQualcommRIL/ro.telephony.ril_class = HTCQualcommRIL/g' /system/build.prop

sed -i 's/ro.telephony.default_network = 8/ro.telephony.default_network = 9/g' /system/build.prop

Aren't necessary because of the option of select network type or because you added them to build.prop already?? Just curious

Thanks
[HTC Rezound] Flyhalf205:
The thing that will break the rom if you do a factory reset after flashing the patch

sed -i 's/ro.telephony.ril_class = HTCVigorQualcommRIL/ro.telephony.ril_class = HTCQualcommRIL/g' /system/build.prop

We can't use HTCQualcommRIL anymore. CM did crazy stuff with it. We have to stick with HTCVigorQualcommRIL

But i'll ad the APNs when I get the chance.
[HTC Rezound] Flyhalf205:
[MENTION=4484713]cristianpark[/MENTION] Been added into our builds now. Should be in during the next release.

https://github.com/Flyhalf205/device_htc_vigor/commit/d1fd1765d0aa1d669a2f4c88d6d38feb1c4c5bc5
[HTC Rezound] hceuterpe:
Encryption (stuck)

I tried everything I could think of to get the radio back after I enabled encryption, and nada :(

I'm attaching my logcat, flyhalf205, you think you have time to look at it?

logcat-e is with encryption, logcat-n is without.
[HTC Rezound] Flyhalf205:
I'll see what I can find.
[HTC Rezound] _litz:
FWIW, I'm also seeing the "delay when waking up" issue when waking the phone from a deep sleep.

Lasts for a good 10 seconds or thereabouts ... everything is just major laggy, then it gets caught up.
[HTC Rezound] Jwezesa:
Me too. Also when I get a phone call the screen won't turn on for a while so I basically miss all calls and its super lagged. On 6/2 build. I can't download the 6/3 build it just keeps saying error..
[HTC Rezound] Talguy:
Alright guys, I'm about to update my phone to the latest version. I'm currently on the 5/20 build and I love it. It has its quirks here and there. So I just have a few question before I do an update which most likely will be a clean flash since I don't really trust dirty flashing since it seems like there have been a lot of kernel changes.

So question:

1) should I RUU my phone to the latest firmware, I'm currently on radios 2.22.10.080(1r/3r). Would it give me better reception or better performance when interacting with the ROMs mobile network settings.

2) hows the bluetooth battery life with the current update. Does it really drain your battery if you're streaming pandora over your car stereo via BT.
[HTC Rezound] HokieCoder:
1.) The radios you listed are from the latest RUU, am I correct? Which HBOOT do you have? Would be interesting to know if the RUU gives the phone something other than radios and HBOOT that aren't provided by whichever ROM you flash. But to answer your question, according to the OP and general knowledge, the latest RUU is highly recommended, if not required for support.

2.) In my experience it doesn't drain hardly any faster with BT just being on. If you're connected to something and streaming, then the majority of the battery drain is coming from the music player using CPU cycles, not BT. But in any case, in my experience so far, it's not any worse than stock or other ROMs.
[HTC Rezound] Talguy:
Thanks. I'm probably going to use this zip file to update to the latest firware, radios and hboot. Hopefully it don't have to reinstall my ROM or recovery partition.
[HTC Rezound] HokieCoder:
That's cool! I took a look inside the ZIP and there seem to be a lot of parts to what it's flashing, so I guess there is a lot more to it than just new radios and HBOOT.

I highly recommend a full backup before you try it, though! Good luck!
[HTC Rezound] HowardZ:
I had a similar problem on 4/27 version.

It turned out to be the proximity sensor calibration.

When you make or answer a call AND the phone is near your ear (as sensed by the proximity sensor) the screen goes black to prevent you from pressing any buttons with your ear.

My solution was to use the Rezound proximity sensor calibration app. I used settings around 20 and 60.
[HTC Rezound] hceuterpe:
If it helps at all, before I enter the PIN to decrypt /data, I was able to make a 911 call (and yes I actually tested that! But hung up the moment I got dialing tone:))

Once it continues into the full boot however, no radio, and it thinks it's stuck in airplane mode.

I suspect it's one of the proprietary services/binaries that run in the init.vigor.rc file, and more importantly, when it runs. Possibly qmuxd or netmgrd, qmiproxy, qcks.

The timing for the stock init.vigor.rc file is very different...
[HTC Rezound] zkrp5108:
Bump your minimum clock speed to up to 392. The default of 192 causes instability and the black screen you're taking about.
[HTC Rezound] Flyhalf205:
Uploaded 6/5. Flash it! Thanks to [MENTION=4203241]IAmTheOneTheyCallNeo[/MENTION] if you think it's smooth!

gapps is included fyi
[HTC Rezound] iHateWebOS:
Smoothest aosp ROM hands down, but downloading updates is soooo slow. Is goo always this slow?
[HTC Rezound] Flyhalf205:
It is. I do have a d-h.st host in the OP. Snuzzo has let me upload to his server. So I can get copies up to his server soon. I'll share a link when it gets uploaded.
[HTC Rezound] Flyhalf205:
Thanks [MENTION=3419683]Snuzzo[/MENTION] for letting me upload my builds to you... New mirror is up guys.

New Mirror!
[HTC Rezound] Talguy:
So reading your changelog on github this version is nice and fast due to you compiling the build witht he Linaro toolchain?????? This isn't an ION build as I thought we were still having problems getting everything to work with the ION memory manager.
[HTC Rezound] Flyhalf205:
Yes. This new build is full linaro. Thanks to neo.

But we probably will never see ION in this thread. Neo will be the one pushing out the ION builds. Until camera works. I might be able to pull a few ION commits into our kernel to help the FB a little but probably won't have any effects.
[HTC Rezound] manchucka:
Yes, it's been terribly slow lately (read: always). However, I'm quite fond of the the MD5 check built into the GooManager app. Assures a proper download (if you can wait that long, that is.)

I love you.
[HTC Rezound] _litz:
How do you get this to build with linaro?

I keep running into errors like :

prebuilts/gcc/linux-x86/arm/linaro-4.7/include/bfd.h:37:2: error: #error config.h must be included before this header
[HTC Rezound] Flyhalf205:
Neo and I are still working on this. We have a simple way of getting you guys to be able to build full Linaro. Just wait. It will soon be ready.
[HTC Rezound] Neo:
What you're running is cm-10.1 built with over 30+ linaro patches and kernel using the 13.05 4.7 linaro chain. A rom built COMPLETELY linaro. Just to let the secret out of the bag and all....

By the way, I just completed a script with about 8 more linaro patches. If this build completes, it will be used to allow anyone to build a 100% full linaro rom :)
[HTC Rezound] _litz:
Standing by ...
[HTC Rezound] jetrobolas:
Thank you for the alternate download source. Goo just plain sucks.
[HTC Rezound] iHateWebOS:
I don't want gooinside.me ever ;)
[HTC Rezound] Flyhalf205:
I might switch over to OTAUpdater if I can figure out how the thing works. Would you guys enjoy that? or Keep it the way it is and have the Goo and Snuzzo server as the mirrors?
[HTC Rezound] iHateWebOS:
I think stang had issues with OTA updater. The only thing wrong with goo is download speed, i'm actually rather fond of everything else about goo manager.
[HTC Rezound] Snuzzo:
Get with me if you want to learn. It will take your own special touch to system.prop to get it running. Not too difficult to set up.
[HTC Rezound] Neo:
to answer your previous question,

https://github.com/VigorCM/linaro-4.7/commit/3b94d1643f45cc7581dde041081564f3016d06f7
[HTC Rezound] Flyhalf205:
Wildstang showed me how to setup the system.prop but the actual website would never let me add a rom.

I might stay with GooManager because it does a pretty good job of letting us know of updates. If the download speeds kill you. Download when you go to sleep or when your at work and can't use your phone. Or just come to forum and grab mirror link
[HTC Rezound] iHateWebOS:
Does anyone remember goo-inside.me or did I just make it awkward?
[HTC Rezound] hceuterpe:
OTAUpdater doesn't quite work right for people S-ON, with HTC unlock right? If so, you're going to get even more complaints if you enabled that, imo, with them forgetting over and over about flashing kernel second...
[HTC Rezound] bunchies:
Latest build is snappy as hell, makes me wonder how crazy ion will be of we get it
[HTC Rezound] Flyhalf205:
For devs..... https://github.com/Flyhalf205/android/blob/cm-10.1/README.mkdn
[HTC Rezound] power950:
I'm s-off and it didn't work quite right for me n e ways do I need to stick to the stock kernel to keep it as quick and snappy as it is?
[HTC Rezound] Flyhalf205:
Shouldn't. I think funky kenrel builds linaro also. I don't know about Ihatewebos kernel
[HTC Rezound] Flyhalf205:
I might have a solution to how to update the roms. It doesn't require GOO or OTAupdater. :) I will hopefully get out a test build tonight if someone wants to try it out.
[HTC Rezound] _litz:
Well, I got the build to build, with no problems ...

Except now TWRP won't work. I can't backup.

Says it can't mount /emmc ...

Tried installing CWM ... it says "can't mount backup directory" ...

Any ideas?

Near as I can tell, everything is functioning correctly on the phone when in CM ... /emmc and all.

It's just the recoveries that won't work.
[HTC Rezound] Flyhalf205:
That isn't the roms fault. That happens a lot over the in the Q&A. usually to format it you must or just try a different recovery
[HTC Rezound] jgiceman30:
Re: [ROM][JB-4.2.1][CDMA] Pure CM10.1 KANG for HTC Rezound [1-31-13]

S-on
[HTC Rezound] shrike1978:
Re: [ROM][JB-4.2.1][CDMA] Pure CM10.1 KANG for HTC Rezound [1-31-13]

Pmem, but it's smoother in every way than CM10 ION.
[HTC Rezound] RebelShadow:
Just read every page getting caught ou on this rom (new to rezound as of yesterday) and got it unlocked, rooted, and s-offed and just flashed this. I am coming from the incredible so know a little about this stuff. Can some one tell be if fast charging is enabled in the kernel in this rom. I have looked in both incredicontrol and kernel tuner and cant find the setting so I assume that it is not. If not can someone recommend a decent kernel that has it. I am using tiny's kernel on the Dinc and would like to find something similar for the rezound. Thanks in advance.
[HTC Rezound] scy1192:
Funky Kernel and Ermahgerd both have Fast Charge

edit: Overclock kernel too, evidently
[HTC Rezound] jskolm:
Re: [ROM][JB-4.2.1][CDMA] Pure CM10.1 KANG for HTC Rezound [1-31-13]

I really like Funky Kernel on this ROM.
[HTC Rezound] jgiceman30:
Re: [ROM][JB-4.2.1][CDMA] Pure CM10.1 KANG for HTC Rezound [1-31-13]

Thanks! Just what I needed. Now time to play. Thanks to all!
[HTC Rezound] iHateWebOS:
Re: [ROM][JB-4.2.1][CDMA] Pure CM10.1 KANG for HTC Rezound [1-31-13]

Mine does to ........ :(
[HTC Rezound] VancouverDroid:
root info / guide you followed?

I too am coming from the incredible. Rooted etc. flashed CM7 almost 9 months ago, i figured it out through a mishmash of forum threads, any ones that you followed for the rezound that you thought was useful?
[HTC Rezound] DarkRazorZ:
I personally prefer this ROM + iHateWebOS's kernel. Very smooth and great battery life.
[HTC Rezound] VancouverDroid:
I have latest ICS

I'll check out the stickies, in the middle of that trying to organize a plan of attack. I cal live without Sense, not that big of deal for the benefits of added features. Please let me know if this is what I need to flash your JB ROM:

Root, S-Off, Replace bootloader (I like Clockwork mod), then flash this ROM. That may sound basic anything I'm missing than may guide my research a bit? Thanks
[HTC Rezound] RebelShadow:
Re: [ROM][JB-4.2.1][CDMA] Pure CM10.1 KANG for HTC Rezound [1-31-13]

Thanks all for the kernel help! I think I will give FunkyBean a try for a few days.
[HTC Rezound] iHateWebOS:
Re: [ROM][JB-4.2.1][CDMA] Pure CM10.1 KANG for HTC Rezound [1-31-13]

Validation.... thanks I'm new @ this and have sort of been looking for a few posts like yours.
[HTC Rezound] jtwebfusion:
I second that. Thanks iHateWebOS!
[HTC Rezound] iHateWebOS:
Re: [ROM][JB-4.2.1][CDMA] Pure CM10.1 KANG for HTC Rezound [1-31-13]

Stang made an OC kernel for CM9, it's why I started doing this in my spare time. I don't think he ever released it though...
[HTC Rezound] wildstang83:
Re: [ROM][JB-4.2.1][CDMA] Pure CM10.1 KANG for HTC Rezound [1-31-13]

Hearing these good things about your kernel so far makes me want to give it a try :)

BTW, I'll likely be releasing an update tonight. Some pretty big things have been happening on the CM side so I think it might be worth it.
[HTC Rezound] jtwebfusion:
Re: [ROM][JB-4.2.1][CDMA] Pure CM10.1 KANG for HTC Rezound [1-31-13]

That would be awesome!!!
[HTC Rezound] jskolm:
I have been giving your kernel a run today to see how it is... got to say... very smooth and nice on the battery. I turn my setup down th 1296Mhz and it runs get on this ROM.
[HTC Rezound] ericsignals:
Re: [ROM][JB-4.2.1][CDMA] Pure CM10.1 KANG for HTC Rezound [1-31-13]

Any hints as to what's happening or is it a bunch of technical stuff over us casual users heads lol..
[HTC Rezound] wildstang83:
Thats super G8 top secret classified info........but you can find all the changes here: http://changelog.bbqdroid.org/#/cm10.1/undefined :) :) :)
[HTC Rezound] jtwebfusion:
Re: [ROM][JB-4.2.1][CDMA] Pure CM10.1 KANG for HTC Rezound [1-31-13]

I was wondering if r1.2 got merged in and that answered my question. Thanks.