yashsingh1/xdaforums huggingface dataset:
[HTC Rezound] HowardZ:
Yesterday I wiped Data and Cache, resetup the phone, made a nandroid backup, and tried the HIRO 6/12 version. I thought the wipes might help, but it didn't. A slowdown/freeze or even crash usually occurs while using opera browser. HIRO worked very well on the wildstang83 CM10.1 and I am confident HIRO will eventually work on the newer version.

So, after the wiping, I noticed the circle, but soon after posting the question, I figured out that it was a battery indicator.

All the pounding on the home and back keys during slowdown/freezes seems to have killed the capacitive keys on my Rezound . I am adding to Hzutils2 a button to modify build.prop to enable softkeys.
[HTC Rezound] Flyhalf205:
Fun Fact. Before May 1st. CM-10.1 roms being built wasn't full cm-10.1. Some framework gits were being built from evervolv jellybean branches.
[HTC Rezound] a.mcdear:
Yeah I think I may know whats up...

If you use a pin or pattern, I believe it will require you to unlock the device before sending the message. At least, I use a pattern, and it ALWAYS makes me unlock the phone. The only things I can do from the lockscreen without unlocking is answer a call or change a song that is playing.
[HTC Rezound] DCnovicky:
I don't use a pin or pattern...I've just changed the slider shortcuts and added/altered lockscreen widgets...
[HTC Rezound] lukester01:
XDA not displaying correctly

Off topic, but for the last two days XDA will not display properly in any browser. Anyone else?
[HTC Rezound] layneja:
This HIRO problem is also on Neo's Infection ROMs too. I'm sure it will get fixed soon.
[HTC Rezound] tigerxchaos:
I have been having repeated issues with pretty much all the 3rd party kernels that are floating around out there. Nothing is quite as smooth on my phone as the stock kernel included in Fly's builds and HIRO in particular was causing some fairly severe lag, which I'm guessing is the same as you experienced. IHWO seems to work on it quite a lot, so I'm hopeful this will get fixed eventually as I enjoy the extra governors, but for now I'm sticking with stock.
[HTC Rezound] PTuT:
Volume issue...

When I am on the call and push volume buttons up/down, visually I can see volume going up or down but volume in my headphones is all the time same. Also, at the end of the call, the beep is quite loud and I can't find the way to change that. I am on 6/10. Anyone experienced this and knows the solution? Also is there a way to split all volume settings to be separate? Thanks Fly for great work.
[HTC Rezound] dm5530:
[MENTION=2479397]mjones73[/MENTION], you nailed the problem re the kernel/driver mismatch! Thanks for helping me get to a solution. I wound up flashing Snuzzo's 3.5 kernel and I'm BACK IN BUSINESS... WOO-HOO!!!

I don't know how the 6/10 rom could have flashed without the kernel changing with it. Regardless, I'd like to suggest an addition to the last FAQ entry re wi-fi not working that suggests comparing the "ABOUT" info re the kernel and build # to see if there is a mismatch.

And thanks to all who shared to help me. Much appreciated.
[HTC Rezound] Flyhalf205:
Build 6/14 is now out. Built with SaberMod 4.9 GCC. Includes the proximity fixes under System Settings>Advanced.... And other CM Changes. Nothing much new with the kernel. You will need to flash the boot.img if your s-on and if you use stock kernel because WiFi will not work.
[HTC Rezound] bunchies:
Downloading now :D

Thanks flyhalf, feels to have improved smoothness

---------- Post added at 07:42 AM ---------- Previous post was at 07:31 AM ----------

Uhh is the advance settings. Vibration strength supposed to crash? Like is it not finished?
[HTC Rezound] izzaeroth:
[/COLOR]Uhh is the advance settings. Vibration strength supposed to crash? Like is it not finished?

I believe he said he was gonna push 06/14 with that not being fixed
[HTC Rezound] bunchies:
Oh, I assumed it wasnt finished lol

Just wanted to double check
[HTC Rezound] cristianpark:
Thanks for the new build Flyhalf, this ROM keeps getting better and better everyday. I'll test today build to see how proximity works.

I have noticed something in two builds now and I want to know if it's a known bug or if it's me. The thing is that I can't play any game with Snes9x EX+ (this is the best SNES emulator in my experience), in some games it shows some video glitches but the game is unplayable (see video [1] with Sunset Riders) in others, the menu freezes and kills the app. I'll test on 6/14 build but probably is the same

Please test this and let me know if I can help anyway giving logcats or so

Thanks in advance

[1] http://www.mediafire.com/download/261e2m0cc95ysej/SNES_Bug.mp4
[HTC Rezound] bunchies:
i actually use that exact emulator too lol and it works great. if your trying to use the full screen mode aspect ratio or the cpu>gpu fast copy than you might run into problems in my experience

snes works fine for me and so does PlayStation one and gameboy advance

try getting all setting back to default and do the setting one by one to see if it fixes
[HTC Rezound] cristianpark:
CPU>GPU Fast Copy was the problem, never had the issue on other device earlier so I think it was CM lol, thanks for the tip
[HTC Rezound] bunchies:
Np.

Hey flyhalf, is there a way (or going to be a way) to test the proximity value in the advance settings without making phone calls?

I was previously using the proximity app from chad and all you had to do was cover the sensor and it would indicate if it was to sensitive or not sensitive enough without making a phone call.
[HTC Rezound] Flyhalf205:
Just call your voicemail :laugh:. That is what I do Other than that. I don't know.
[HTC Rezound] iHateWebOS:
Yes, use the proximity sensor app. If it's already installed clear the data on it and then open the app. It will not change default values unless you change them yourself.
[HTC Rezound] bunchies:
I think I'll go with the voicemail idea lol :thumbup:
[HTC Rezound] a.mcdear:
The app "Sensor List" from the Play Store does show the "near" or "far" states for the proximity sensor.
[HTC Rezound] drt054:
Re: [ROM][JB-4.2.1][CDMA] Pure CM10.1 KANG for HTC Rezound [1-31-13]

I am on this ROM now, but I use tether quite often but seems in every jb build so far connectivity just drops. I am tethering my hp touchpad cm9. Anyone else? Usually have to put phone into airplane mode then reconnect to tablet. Is this a known issue?
[HTC Rezound] wildstang83:
Yes it is a known issue. This is one of the problems with all 4.2.1 builds at the moment. We are forced to use ad-hoc which isn't the best option to use when tethering.
[HTC Rezound] drt054:
Re: [ROM][JB-4.2.1][CDMA] Pure CM10.1 KANG for HTC Rezound [1-31-13]

Even on cm10 connected with netd using wifi tether or native tether I would have same connectivity issues.
[HTC Rezound] iHateWebOS:
Re: [ROM][JB-4.2.1][CDMA] Pure CM10.1 KANG for HTC Rezound [1-31-13]

This happened to me because i was right on the edge of a 4g zone. Phone continuously tried switching to 4g and data would drop. Recently i lost ALL 4g for a week. When vzw fired 4g back up i got full signal everywhere in my house and have had zero data drops regardless of rom (i flash about three times a day). Unfortunatley this means your problem will persist until vzw fixes it in your area. Until then sense roms perform the best when switching between 3g/4g
[HTC Rezound] wildstang83:
I'm sorry guys, there might not be a build tonight after all. I'm getting to many errors, and even if I did get it to build I wouldn't release it till I was absolutely sure it was good. That could take at least a day of testing.
[HTC Rezound] drt054:
Re: [ROM][JB-4.2.1][CDMA] Pure CM10.1 KANG for HTC Rezound [1-31-13]

Actually thinking its a RIL issue (my previous posts) , I know it is still being worked on and not perfect but flashed back to cm9 build 1/13 and signal strength is better and having no connectivity issues.
[HTC Rezound] wildstang83:
Made a new signature for you guys to use if you like this rom and want to show your support :)

​

Grap the code:

[center][url=http://xdaforums.com/showthread.php?t=2113140][img]https://dl.dropbox.com/u/27109805/XDA/CM10.1/ws83sig.png[/img][/url][/center]
[HTC Rezound] Neo:
Re: [ROM][JB-4.2.1][CDMA] Pure CM10.1 KANG for HTC Rezound [1-31-13]

in hardware/qcom/display:

git revert cbdefbc4de03307cccc7f133db8c917e87189f1f

Do that instead of what we talked about last night. Apparently a new commit was merged to tell it to build all qcom display devices which is why we were getting those "duplicate" errors.

So now we have 2 commits to revert :P
[HTC Rezound] shrike1978:
It looks like CM is in the process of adding official msm8660 support, so I'd expect more and more of these to pop up over time.
[HTC Rezound] Neo:
Re: [ROM][JB-4.2.1][CDMA] Pure CM10.1 KANG for HTC Rezound [1-31-13]

Yeah I'll git log next time instead of deleting source from hardware/qcom/display
[HTC Rezound] wildstang83:
Re: [ROM][JB-4.2.1][CDMA] Pure CM10.1 KANG for HTC Rezound [1-31-13]

Ok so Chad just fixed the problem so I'll try again tonight after work.
[HTC Rezound] mjones73:
I'll give it a shot too, I was able to build after reverting the new commit yesterday.
[HTC Rezound] wildstang83:
Re: [ROM][JB-4.2.1][CDMA] Pure CM10.1 KANG for HTC Rezound [1-31-13]

Ok thats good news, thanks
[HTC Rezound] wildstang83:
New build is ready guys. All seems good so far. Enjoy :)

EDIT: Couple of notes. IF camcorder records but doesn't render properly the first time, don't worry. Just close out of camera and open it back up, should record just fine. The second thing, this build has Chad's commit from tonight that fixes tethering until source is fixed. I tested it on my MacBook Pro and it does appear to be working fine.
[HTC Rezound] YTHero:
Nevermind. I just read your edit on the previous post.
[HTC Rezound] mjones73:
Hmm, I was getting a new commit error earlier, let me try again.
[HTC Rezound] scy1192:
Perhaps it's for the best
[HTC Rezound] wildstang83:
I just nuked my cm10.1 folder, re-initialized the repo, repo synced. After that I had to go to hardware/qcom/media

and

git revert 333d0e460bc6a6579c5193438fa69560abea658f

Built fine after that.
[HTC Rezound] mjones73:
Yeah I had to revert the same, it's building now.
[HTC Rezound] keyro:
Hi guys I was wondering Is there any way to make this rom work on gsm??!!.
[HTC Rezound] mjones73:
Chad's proximity sensor app does also.
[HTC Rezound] ANDR0lD:
I don't mean to sound ungreatful but I was wondering if we will ever get this "HALO mod?" I love all your work and dedication devs!

Sent from my ADR6425LVW using Xparent Cyan Tapatalk 2
[HTC Rezound] Luke1213:
it does not come with CM ROMs
[HTC Rezound] izzaeroth:
Anyone else experiencing the speaker phone turning on when answering a call?
[HTC Rezound] ANDR0lD:
I know its a PA invention but I do recall hearing someone that cm devs were going to attempt to implement HALO or something similar, was just wondering is all :) the ROM is running great!

Sent from my ADR6425LVW using Xparent Cyan Tapatalk 2
[HTC Rezound] TheBr0ken:
It can be implemented, but honestly unless you need another type of notification process cause you have a hidden task bar, the Halo novelty will wear off pretty quick. Especially if you are trying to do something like watch videos and hangouts notifications keep popping up. It's cool, but eh
[HTC Rezound] brenuga:
I mean if you just wanna try Halo , run shrike's PAC rom or wait for Neo to release TRON 2.2. I don't think its a good use of time to port over to CM, since its already available on another rom. Anyways, I think Neo looked at Halo and it basically depends on the PA framework, which is different than CM and AOKP, so it will probably be a PACman-only feature.
[HTC Rezound] itzloren:
Happens to me as well, not every time though
[HTC Rezound] izzaeroth:
Interesting, my happens everytime I place or receive. Gonna try another flash and see if that does anything
[HTC Rezound] mavpts:
+1
[HTC Rezound] wildstang83:
Not really related to this post, but who wants some free stuff? Ole' ws83 is in a good mood tonight :)
[HTC Rezound] Luke1213:
what is that?
[HTC Rezound] mjh68:
Swag ... :)....
[HTC Rezound] Snuzzo:
Whatcha got homey? Throw me a pm.
[HTC Rezound] wildstang83:
Edit: The give-away has now ended. Thanks to everyone for the support. I hope all that were able to get my apps for free will now enjoy them :)
[HTC Rezound] Flyhalf205:
Couldn't wait 2 more days. Had to upload 6/16. Flash the kernel if your s-on. Built with speed :)

You can find the changelog in CMUpdater. Just read the first couple lines.
[HTC Rezound] bunchies:
I wish I knew what major changes to the HTC rezound meant lol

Thanks flyhalf :D
[HTC Rezound] HowardZ:
I would like this bug/feature because 99% of the time I use speaker phone for my phone calls.
[HTC Rezound] layneja:
Thanks WS83.
[HTC Rezound] Flyhalf205:
Speed. Lol
[HTC Rezound] Neo:
^ ^ ^ This ^ ^ ^

I spent over 6 hours converting the open sourced code to work for cm by freehanding the individual lines for each framework and settings commit.. Even then the build would crash as there are still major dependencies involved with PA and their personal implementation of PIE. For those wishing to try st it with CM, save yourself 6 hours worth of time and pull the HALO modified repositories from my personal git. I uploaded it to look at it later should I ever decide to try and attempt it on cm again.

Personally, it appears to me to be one of those novelties that can get really annoying. I'm still trying to get used to it on my TRON2.2 build
[HTC Rezound] TheBr0ken:
XenonHD has Halo ;)
[HTC Rezound] HowardZ:
6/16 CM10.1 with 6/16 HIRO

are excellent.
[HTC Rezound] tigerxchaos:
Seems like a marked change in speed over 6/14. Thanks Fly!

Now if I could just sort out what is devouring my battery... From 100% to 55% in under 2 hours (most of which was on 6/14).
[HTC Rezound] mjones73:
What's the battery stats and wakelock detector showing using the most power?
[HTC Rezound] rgnicholas:
Thanks! In your opinion, is it best practice to wipe cache / dalvik and then simply dirty flash over for these consecutive builds? Does it matter if you have flashed a new kernel? Thanks again for all you guys do!
[HTC Rezound] bunchies:
Ok so this ROM has an auto update/installer, you can dirty flash builds unless the new version has changed android api version like android 4.2.1 to android 4.2.2 or if the dev said to clean flash the new build because of crazy wizard magic on the new rom version

But once you got it installed and you get an update for the ROM it'll notify you thank ask you to download it and ask to update when the download is finished and it will boot into recovery and install and wipe dalvik (and maybe cache, idk) Than it will automatically reboot. (Only works with twrp and i think cwm)

Just when it comes to kernel installing you don't want to wipe cache before or after installing a kernel zip. It can cause boot loop, but since the ROM auto reboots after updating you will have to manually reboot and install your custom kernel. So no issues there if you remember dalvik only

Lol how's that flyhalf? :thumbup: saved you like 2min
[HTC Rezound] wildstang83:
You're welcome :)
[HTC Rezound] rgnicholas:
Thanks again for the info! I have used the auto-updater for v.6/16 and all seems well. I may re-flash the latest FunkyBean to see how they play together :D
[HTC Rezound] izzaeroth:
So far on newest build no issues with speaker turning on when placing calls. Will let you know about incoming. Also for those others having issue I did a clean install of newest build.
[HTC Rezound] power950:
I didn't wanna get off topic so I created a post in questions and answers but I'm not getting anything so if anyone wants to take a look here its about my service

Http://xdaforums.com/showthread.php?t=2326750

Sorry I wanted to avoid posting here but I'm desperate
[HTC Rezound] Neo:
I'll check it out.
[HTC Rezound] bacon612:
Anyone else loose WiFi and Bluetooth going to the 16 build?
[HTC Rezound] Flyhalf205:
You flashed the boot.IMG ? Both of mine working perfectly.
[HTC Rezound] bacon612:
I'm s-off. Do I still have to flash the boot.img?

I dropped my phone yesterday and I'm wondering if I've pooched my BT and WiFi radios. 4g works perfectly. I even restored a nandroid from the 8th of June too and still have no WiFi or BT.

Edit: I've been using your new cm updater feature flawlessly for the last few builds. Not sure what's happening. I'm scared that I'm going to have to give up my rezound. Need WiFi and bt
[HTC Rezound] Flyhalf205:
You don't have to flash the boot.img if your s-off. I hope it isn't doing the same thing my 1st Rezound did. BT/WiFi broke forever :( and I update with CMUpdater so that isn't the problem....

I'd try flashing back to a sense rom just to make sure it works on that. If it still doesn't work. Flash stock recovery and factory reset inside of HBOOT. If that still doesn't work. I'm sorry man....but it might be broke forever :(
[HTC Rezound] wildstang83:
Yup, this. If resetting it by flashing all the way back with the ruu doesn't fix it, game over four the 'zound.
[HTC Rezound] Luke1213:
RUU is the last chance...
[HTC Rezound] PTuT:
I would check the back cover and all antennas molded into it + the pins that lead do it. Good luck.
[HTC Rezound] tigerxchaos:
Android System is the leader of the pack by far. I'm using GSAM battery monitor, and I'm not entirely sure how to read wakelocks or if this is a large number, but it says 113 wakelocks. Is there a good program you can recommend that will answer that question?
[HTC Rezound] Snuzzo:
How long were you off the charge? Some wake locks aren't bad and some are inevitable.
[HTC Rezound] tigerxchaos:
I'm not sure when it started polling. When I checked it to post that info, I had just plugged it in maybe a minute or two earlier. It's back on battery now and I'll post a screenshot at the end of the evening. Charged back up to 75% now.
[HTC Rezound] tigerxchaos:
Down to 50% after just plugging it in a few minutes ago. Battery seems solid for the most part when the screen is off, though not all the time. Using the phone causes the battery to plummet. (Most of that drop came from a 20 minute car ride, from 74% to 57%, where I was playing music).

Attached are screenshots from just before I plugged the phone in. I assume this represents the time in between my last post to this one.

EDIT: Forgot to mention, I'm using the Conservative governor for both cores and both are set to 384MHz minimum speed.
[HTC Rezound] wildstang83:
Just figured it all up, so far I have given away $192.00 in paid apps :)

Share with your friends and everyone else that might be interested. I want everyone to be able to get my apps for free, so because of that I am going to let this give-away roll for a couple more days. Don't wait around to the last minute though, because when I pull the links, that'll be all folks ;)

Get the apps here: http://xdaforums.com/showpost.php?p=42623587&postcount=2995
[HTC Rezound] Luke1213:
i am glad that [MENTION=3082717]Flyhalf205[/MENTION] you began using SaberMod like NEO did! gonna give 0616 build a try!
[HTC Rezound] bacon612:
Edit: Derp this was supposed to be in the Q+A thread. Sorry guys. Mods move if u want.

Hey guys. I posted in the main CM10.1 forum yesterday about my bluetooth and wifi not working. I dropped my phone the other day and i think thats what has caused the issue.

My phone is s-off running the latest hboot and radios. Had a pretty good fight with my rezy last night and heres what I've found.

1) I put a clean sd card in the phone with the latest RUU copied to it and renamed it to PH98IMG.zip. (got it here http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/)

2) rebooted to hboot, phone found the ruu and began flashing. ( i backed up my internal storage first, phew)

3) ruu completes without errors but when it reboots, I get the white HTC screen for a moment, then the dim one for a few more that says "quietly brilliant" and then bootloop.

4) I read that you have to relock your boot loader to flash ruu. So i dusted off adb and relocked. It errored in the cmd screen but hboot showed "relocked" so I think it relocked.

5)I then reflashed the RUU from hboot only to get the same results. Bootloop.

6) I teared up and complained to my girlfirend for 15-20

7) I flashed CWM and restored a nandroid and now im back on glorious 10.1 but without wifi or bluetooth. Right where I began

My question for the pros out there are as follows.

1) Am i not ruu-ing properly?

2) Am I ruu-ing properly but maybe its the fact that wifi and bluetooth are screwed up on my rezound (hardware issue) that is causing my bootloop after the ruu?

Any input here would be fantastic.
[HTC Rezound] Flyhalf205:
[MENTION=4429707]bacon612[/MENTION]

Sorry to break bad news but it's gone. Hardware issue.. You won't be able to flash a signed boot image. That is why it is boot looping. You'll be able to flash another rom. Maybe like Viral or I use Vigor360 personally on my broken Rezound still(has same problem as you). After a custom rom like that. You'll be able to flash Funky or HIRO kernel.

Same problem here with this guy. http://xdaforums.com/showthread.php?t=2281670
[HTC Rezound] HowardZ:
There is a tradition that one must run the PH98IMG.zip ruu file two times in a row. So, do it once, the phone might reboot a few times while doing the ruu. When it is all finished, then reboot into bootloader, and do it again.

If you still have a problem, then boot into bootloader and do a factory reset. The hboot factory reset makes use of the stock recovery to do unknown magical things in addition to wiping the data and cache partitions.

There is also sometimes an exe file for ruu which is run on a pc connected to the rezound via a usb cable. The exe ruu is supposed to handle errors better and thus be more reliable. I personally have not used the exe method.

Also, you need s-off to ruu backwards to an earlier version.

That's all I can advise, and I am no expert with this.

Regards

Howard
[HTC Rezound] bacon612:
You are saying that the BT wifi brokenness is what is disallowing my to flash a signed boot image. This is why your CM10.1 roms work with my broken wifi and bt. Correct?

Think Ill have luck with HTC RMA? My phone is still under warranty for a month. My rez has always worn a helmet and looks brand new. Im assuming i would just have to go back to s-on, relock the bootloader and use scotts hack so that the hboot reads "locked"?
[HTC Rezound] Flyhalf205:
Correct! Could just RUU back with it just boot looping and take it back to Verizon. That is what I did...
[HTC Rezound] bacon612:
ya, im about to do that.

Was concerned that it says "relocked" in my hboot but I'm hoping that shouldn't matter because my phone looks brand new. Thanks again for the support here guys and sorry for cluttering this thread with my issue.

Edit: New Rezound overnight-ed under warranty by verizon.
[HTC Rezound] tigerxchaos:
If all else fails, a friend of mine once suggested applying 12v of current across the SIM contacts. Ruins the mainboard and Verizon/HTC will not be able to resurrect the phone, thus won't be able to tell if you rooted it.
[HTC Rezound] :
I've returned 2 rezounds with hboot showing S-OFF & Unlocked still running custom roms. Any device i have ever owned and returned are never stock when returned and i have never ever had an issue.

I have only heard of 1 or 2 people people being charged (I'm sure there are more), but neither could show proof that vzw charged them for the above issues. And only for those issues.

Vzw will however charge you if the device has cosmetic damages that is more than superficial scratches etc. Damages that resulted from water or device was determined to have been damaged by other means. Or if wrong device was returned.
[HTC Rezound] scsnospam:
USB not working any more

1. After installing build 6/14, my phone is no longer being detected on USB. Does not even show up on device manager. Now what?

2. Also, I am s-on. If I update using the OTA updater to 6/16, do I have to flash the kernel separately? Where is the link to the kernel? Is it also OTA? Or should I download from the post#1 link mirror and that will have the new kernel already?

Thanks for the great work!