yashsingh1/xdaforums huggingface dataset:
[HTC Rezound] Neo:
For those waiting around for a cm-11.0 or tachyon update, it will not come today. Still perfecting awesomeness
[HTC Rezound] darienms1986:
Now my night is ruined:(
[HTC Rezound] Neo:
lol sorry. Still trying to iron out the problems
[HTC Rezound] darienms1986:
It's all good man keep doing what you do.
[HTC Rezound] Scott586:
Thanks for the update Neo. Now I can quit checking for at least tonight ;)
[HTC Rezound] Hobox10:
People that are strict against others trying to learn are usually the most insufferable people on the planet. Also, that's not a statement towards Wildstang by any means so I don't want anyone interpreting it that way, but rather it is praise towards Neo for his encouragement.
[HTC Rezound] power950:
I know it kinda irked me when you couldn't say hey to your fellow xda member without him shutting the thread down but hey some people are strict with the rules some aren't he just follows the rules by the book nothing won't with that but enough talking about him sorry for bring that up was just trying to bust neos balls
[HTC Rezound] rageyoudown:
My phone is stuck :/

Hello, I installed the latest version of this released the 24th. I also flashed the 4.4.x PA gapps...Now when I rebooted my phone it's just at the Cyanogenmod screen spinning in circles. I've let it try to load for hours. It is just stuck there spinning, trying to boot up.
[HTC Rezound] mjones73:
Try re-installing is all I can suggest. Flash the kernel ok and/or you're s-off?
[HTC Rezound] rageyoudown:
Yeah my phone is S-off and so far i've reinstalled 3 separate times, same problem all times. I've even used both recovery, seeing if that was the case. I guess it wasn't. Maybe it's just the combo of Pa Gapps and this rom?

Edit 1 : I've flashed the rom alone with no Gapps. Does the same thing, just spins.
[HTC Rezound] bunchies:
What version of recovery are you using?
[HTC Rezound] mjones73:
Re-download the rom and check the md5 if you haven't, just guessing you may have got a bad download.
[HTC Rezound] rageyoudown:
I have redownloaded it, and also tried the different version. I've had it working once before but now it just doesn't work altogther. I have used both recoverys listed by NEO.
[HTC Rezound] darienms1986:
Are you downloading from your phone or computer? I've never had a bad download from my phone, just from the computer!
[HTC Rezound] scy1192:
Anyone else having occasional trouble with the touchscreen? I'm hoping that it's a ROM issue, but I'm not sure... I'm getting phantom touches in the center of the screen that don't go away until I turn the screen off and then on.
[HTC Rezound] darienms1986:
Sounds like a hardware issue
[HTC Rezound] Neo:
Digitizer to be exact
[HTC Rezound] scy1192:
well it seems to be working fine after a wipe, but we'll see
[HTC Rezound] darienms1986:
Mine did the and thing after wipes. But eventually went back to acting up.
[HTC Rezound] ninjabeaver:
Maybe its been posted already but when I use Google Now the screen goes black

Must be related to display issues in first post....
[HTC Rezound] bobbyjones69:
GSM Issues

hello all, im not sure where to post this so ill put it in the rom i wanna use. i am having issues with my rezound and a gsm sim. i have the latest global radio firmware and i have the latest hboot but when i try to send a text message on any non sense rom with att all of my signal drops and i have to restart the devices to get it back. i can receive messages and make calls and have data. can anyone send me in the right direction to fix this issue. thank in advanced.
[HTC Rezound] tmanschuette:
My phone started doing this the other day too...
[HTC Rezound] mjones73:
It is.
[HTC Rezound] kcipopnevets:
Wow...

I thought I was the only one... My screen is acting up as well. The problem leaps into other ROMs as well but I have not tried RUU since it always fails... I have up to two ghost fingers about 3/4 up the screen and it only goes away for a bit when I screen on/off.
[HTC Rezound] dlumberg:
What gapps work with ION? I keep getting FC's for chrome and voice after flashing gapps.
[HTC Rezound] darienms1986:
I'm almost positive that is the beginning of a digitizer failure. It has happened to me twice, I've bought Chinese made so they were cheaper

---------- Post added at 12:28 PM ---------- Previous post was at 12:27 PM ----------

Banks gapps worked for me, no fc's

http://www.androidfilehost.com/?a=show&w=files&flid=10306
[HTC Rezound] kcipopnevets:
?

Thanks for the lightning fast feedback, but is it possible that's not he issue? This may seem crazy, but when I flip the phone 180 degrees, the ghost touches only affect the first quarter of the screen, the OPPOSITE of where it was touching before! Isn't that a software issue if the problem can mirror itself like that without any reason? And maybe the ROM is stricter with wafers since I'm not alone and the problems have arisen since going to this ROM?
[HTC Rezound] darienms1986:
Weird thing is, when mine was going out if I rotated 180I could touch where it had issues in landscape. But yes I'm sure it's possible to be another issue but I'd out money on it being the digitizer. Only way to test would be to ruu and ruin it like that for a while and see if problem persists
[HTC Rezound] jtio21:
Off-Topic

I am either upgrading to a htc DNA or a Samsung s3 which one do you all recommended. From what I can see the S3 community is a much livelier community than DNA community and can I tether on the DNA without because as far as I can to tell the only way to tether is to unlock the bootloader by S-off ing
[HTC Rezound] Uzephi:
I have a DNA. It was given to me. (Buddy had a shattered screen and his work replaced it and didn't want the phone). My brother in law has an S3. I gotta say, the colors are more lively on the DNA compared to the S3. Beats on Sense 5 ViperDNA is amazing. Oddly, I hate older sense versions, but HTC finally did something right for once. Zoe is an amazing feature. Only downside is non removable battery (can get OEM replacements, but no extended) and no SD card slot. OTG works though.

I get about 4hrs screen time on sense roms and 3.5hrs on AOSP. I am a heavy user, so I don't know about stand by time, but one full battery drain for me is about 10hrs compared to 2hrs on the rezound, as like I say, I am a heavy user and have times I have the screen on for 1-2hrs at a time.

For the S3, my brother in law is always stuck to a charger. Don't know how well his battery life really is as he runs stock, not rooted and stock battery. He says he has to keep his phone plugged in at work or it would die by the end of his shift streaming audio with screen off. I tested streaming on my DNA and it just sips battery compared to his S3.

Sent from my DNA using my mind.
[HTC Rezound] Hobox10:
I'd recommend the Note 2 over either of those, but it comes with its own drawbacks too. If you really don't have the slightest care for battery life though, the Note might not be for you.
[HTC Rezound] jtio21:
Thank you. I think I am gonna go with the DNA but the note 2 was a consideration I just like HTC and the community here way better than my experience with the galaxy s captivate
[HTC Rezound] Thingula:
Sorry if you already covered this, but I just wanted to jump in (without backtracking to the beginning of the conversation) and offer some quick advice. The Rezound's digitizer is a little cheap and overly-sensitive, in my opinion. For example, it will respond to input when your finger is still a good distance from the screen. I'm currently on my third Rezound, and this problem has persisted with each of them.

The first one fell onto a linoleum floor. There was no visible damage, but the digitizer had "dead" and "mirrored" zones, so I just ordered a replacement.

The second lasted for about a year, before I noticed the same mirroring issue, as well as the touch coordinates going totally crazy (Developer Settings > Show Input). Considering how it was always handled with extreme care, it didn't make sense. Turns out, the battery went bad, and was messing it up (which makes a lot of sense - considering how they work).

That phone was later retired, due to a drowsy mistake, on a late night of kernel development. xD So here we are: Rezound number 3, with an overly sensitive digitizer, but otherwise fully functional.

Tl;dr

If you can, use/borrow a compatible battery, and see if that remedies the issue.
[HTC Rezound] darienms1986:
Very true about the battery.
[HTC Rezound] Neo:
Quite possibly an updated stock cm-11.0 release coming here in the next day or so...

Sent from my LG Optimus G Pro
[HTC Rezound] tmanschuette:
PMEM or Hybrid?
[HTC Rezound] Neo:
Hybrid

The code work involved recently is the result of team effort and comprised of everyone in team vigor but myself lol I will just be building it for you all.

The hybrid branch I will be building from is specifically _Litz handiwork
[HTC Rezound] bunchies:
is there any plans for a cm10.2 hybrid?
[HTC Rezound] Neo:
Yes and I believe Snuzzo had taken a head start on that

Sent from my LG Optimus G Pro
[HTC Rezound] iamwalterwhite:
Not to discourage from this thread, but Snuzzo just built CarbonROM (4.3.1) as a hybrid. It doesn't have a working camcorder (4.3.1 doesn't on the Rez anyways), but it works well.
[HTC Rezound] bunchies:
Oh, so taking pictures atleast works on ion 4.3.1 than

I don't care so much about video recording
[HTC Rezound] _litz:
At this point, any ION hybrid is basically a juggling act ... do you want THIS to work or THAT to work ...

The best we've managed is basically non-functional video playback ... or sometimes non-functional HD video playback.

Or sometimes camcorder ... or sometimes screenshot. Well you get the idea ...

The biggest issue to iron out (and if anyone has any ideas ...) is getting the interface to the EGL to work properly.

We can reliably make about three different errors occur ... ranging from outright failure, to config errors.

This is at least better than previously when we had media codec errors ...
[HTC Rezound] iamwalterwhite:
That's right. There are graphical artifacts when the screen rotates, and there are no task switching previews. Honestly though, with the ability to take pictures it's just fine for me.
[HTC Rezound] Jonman409:
Are the errors/findings documented anywhere?

I'm still working on figuring out the device layout as far as gpios go for a 3.4 kernel. HTC scattered them around and implemented some ugly hacks for our board.
[HTC Rezound] _litz:
All our work is on github under vigor ... http://github.com/vigor

Branches relevant here are the cm-11.0_hybrid ones

(see the various local_manifest files for the actual repos used for each type of build ... pmem, ion, or hybrid)
[HTC Rezound] Thingula:
Yep. Time for a fresh start..

Which is why I'm still working on my own (source) build. I have a long way to go, but have made a lot of progress. The biggest issues are radio hiccups (disconnect - connect) and some minor visual anomalies. But my battery life is noticeably better, no media hiccups, great signal strength (again, with an even better battery life), it's really smooth, and there are a few other "pros".. But I'm not making anything public, until I can consider it to be in the "Beta" stage - I don't want to release anything that's too unstable. I'm not referring to random reboots (I've only experienced two, in the past 3-or-so weeks of running it), or even small quirks with the display, but rather "brickability". The last build bricked my Rezound (new one on the way).

It was the result of an irresponsible, 72-hour, insomnia-induced, OCD-fueled code-fest. I broke my personal rule of always double-checking each edited line (Meld Diff Viewer <3 ), being fully concentrated and well rested, before flashing anything.

Thankfully, I have the ultimate backup system: My 3 laptops and desktop sync their filesystems automatically, with a Raspberry Pi, hooked up to a 2Tb External Hard-Drive, using my own (semi) git-like protocols - the name is TBD, but right now, it's "Raspberry Pickup". To save space and make it work as quickly as possible, the computer in use creates a "DD_MM_YY-HH_MM_SS.patch~" file, that contains a compressed list of all new/deleted/modified directories/files from that session. Of course, it's limited to my development folder. No need to back up the entire ~/Home directory :D . The file is quickly generated and pushed/pulled to/from the RPi via a simple script that runs before shutdown and immediately after start-up. This allows me to view (through ssh and CLI) all versions of my projects, and choose which one I want to restore (although the syncing is automatic, I need to backtrack, sometimes).

So (yeah, I have ADHD, haha), I still have the code for the safe(r) build, and reviewed the other one to find the issue that bricked my phone.

P.S. I've been meaning to release a build and the source code for "Raspberry Pickup", but there's just so much configuration required (as well as a modified Raspian image, for the RPi) that I never took the time to package it all up, and distribute it (Google Code, PPA, or otherwise). It's just at the bottom of my ever-growing to-do list, but feel free to send me an email if you'd find it useful, and (hopefully) I'll remember to try packaging it up and sending it to you! (Tested on Ubuntu 12.04-13.10) Seriously, though.. My memory

sucks

, so don't take it personally, if I don't reply.. :( [Masked]My Personal Email Address
[HTC Rezound] Chucktr:
The code...

Ah ha!!!! You may have answered the question I have presented in many places ... with no positive responses. This site/webpage: http://github.com/vigor contains all the code specific to the ReZound?? This code is what makes it different from all the others?? I knew there had to be some drivers and code that was "specific" to the ReZound somewhere but could not get a proper answer. And for all those who think that they did ... sorry. I'm getting denser in my old age and it takes the right words to trigger the memory.

Haven't learned GitHub ... yet, but I would imagine that IF I knew that I would see that what you have just presented is exactly what I want.?.?

Thanks,

Chuck
[HTC Rezound] Talguy:
[MENTION=4699600]Thingula[/MENTION], can you give us a little more information on the work you're doing. Is it a more stable ION Camera build, a 3.4 kernel or something awesome that we've never seen for this phone before?
[HTC Rezound] Neo:
Q

That is our "Device Tree". You have rom source which comes from CyanogenMod, and then you have our device specific source that required to build with CM based roms on our team vigor git.

I believe he was working on a pure google source rom. ie, built from google source and no other variants like cm, pac, etc

Sent from my LG Optimus G Pro
[HTC Rezound] Thingula:
Exactly. I just felt that we needed a fresh start, from the most bare-bones resources available. I've never attempted a project this risky and low-level (hell, I'm 18), but I wanted to do it for the community, as well as my own experience. I'm really new at this stuff, but my (really intense) OCD makes me work very slowly, but also pay a lot of attention to the details. I'm putting as much time into this as I can, in my chaotic life, and am making some really big progress, that I hope to share soon.

There are only 2 reasons that I have yet to create a public thread:

I don't want a (potential) mistake ruining anyone's phone

It would defeat the whole concept. I'm not ready for this to be a collaborative effort among the greater minds in the community, because I feel that all those random snippets of code that have been pushed and pulled over the years, from so many great people, created the byproduct of instability and messy code.

Just look, for example, at how stable the 4.3.X CM builds were in the first few months, then at the chaos, commits, and confusion that most of them were left in.

Sorry for the length, but I didn't want anyone getting the idea that I'm just playing around in NetBeans, have no idea what I'm doing (that's only half true ;) ), or BSing everyone. I'm doing my best! :p

Edit: Neo, not the whole ROM; just the more device-specific things (kernel) that are giving us audio hiccups, blank screenshots, corrupted recordings, bad battery life (and false readings, according to my voltmeters), mounting issues, crackling audio at higher volumes, reboots, etc. These are all things that I'm working on. For everything listed, I have been able to find the cause.. Now, I just need to find/add the solution.

Jeez.. I need to learn to say more, but write less.. xD
[HTC Rezound] Neo:
Just make sure you do not release anything publicly that has the potential to brick anyone. There probably wouldn't be much a problem with creating a thread for it either provided you feel it is something that is usable. I would put it in Original Android Development also.

Doesn't get any more original than that
[HTC Rezound] _litz:
As for the vigor github ... here's what's there

vigor/android -> our custom scripts and local manifests (note, this mounts to /vigor in your source tree)

vigor/device_htc_vigor -> all the vigor device specific settings/configs, special code, etc.

vigor/device_htc_msm8660 -> our customized version of the Code Aurora msm8660 device support stuff

vigor/kernel_htc_vigor-3.0 -> linux 3.0 kernel customized for vigor

vigor/vendor_htc_vigor -> vendor provided files (firmware libraries, etc)

In addition, there are also local copies of the following cyanogenmod projects, as we have customizations outside of their scope in these :

vigor/hardware_qcom_media-legacy

vigor/hardware_qcom_display-legacy

vigor/frameworks_native

Special note : you'll see in a lot of "build your own rom" instructions a reference to running a "extract-files.sh" script ... we don't do that; all our files provided by that script are already present in the various projects in the github.
[HTC Rezound] Thingula:
That's one of the reasons that I haven't made it public, yet. Bricked one, and still waiting for the next in the mail.. :silly: Can't really do anything until then, other than review and make small, safe changes/additions. I'm really slow and tedious, but hope to have a

safe

beta build, by the end of the month (of course, this just has to be one of the busiest months :p ). My only real-world deadline is finishing before anything higher than 4.4.X. But, after seeing the introduction of libart.so, I think we'll have quite a few incramental upgrades with KitKat.

The only downside, is that I doubt any of what we have now - my build, ION, the ION hybrids, etc. - will be functional when Key Lime Pie comes out. I think it's safe to say that 5.0+ will be 100% Dalvik-free, and introduce some really big architecture changes.

But, I'm not putting anything on hold, due to my own speculation. This has actually turned into a fun little project, and it may be worth citing in a future resume. :fingers-crossed:

P.S. A big thanks to you, Team Vigor, Flyhalf, Reventech (I hope I remembered that correctly), and everyone else who kept the Rez alive. This great community is what gave me the resources, support and motivation to learn something other than using Rom Manager and making miscellaneous apps, these past few months. :victory:
[HTC Rezound] Neo:
It is fun and I hope you're able to produce what you're hoping to.
[HTC Rezound] tmanschuette:
I give up...

Spoiler content hidden.

My laptop is gone and useless until I get the repair CD...
[HTC Rezound] nolig2278:
Amazing work. Installed flawlessly on the first try following steps for s on in op.

Only real issue is with html emails not showing. Seems like it is related to the stock browser issue. Is there any email app that works? Stock email should not connect to my provider. K-9 email connects but html based emails show up black.

I will try to wait this out.

Again great work guys.
[HTC Rezound] mjones73:
Gotta use a different browser like Firefox and webmail.
[HTC Rezound] nolig2278:
Using chrome which is what I would use anyways. Just would like an actual email client.

Thanks
[HTC Rezound] iamwalterwhite:
Not possible yet. They're working on a fix.
[HTC Rezound] hochoch:
I was thinking of flashing this but the DL link is dead. has it been pulled for some reason?
[HTC Rezound] Dreistul:
Flashed this ROM last night, upgrading from an older build of PAC-MAN rom.

It seems that, in addition to numerous stock browser based applications, also affects Dolphin. I didn't expect that one. I guess I can manage with Chrome and/or Firefox.

There are two things that really surprised me, and I suspect they are somehow related:

- My battery lasts significantly longer.

- My phone signal almost always shows 3 bars. Before flashing, I was always floating around 0-1 bar.

I'm guessing that the phone is spending much less energy looking for the network, but it might not be accurately measuring my signal strength. Network Signal Info app (by Kaibits) shows Net strength of 2147483647 dBm * -214783509 ASU, so I'm sure that app is wrong. OpenSignal app shows -85 dBm, which might be true... I'll have to keep an eye on it.

Anyway, great work!
[HTC Rezound] scy1192:
Dolphin works fine if you have Jetpack installed. Without Jetpack, Dolphin just uses the Android built-in web page rendering (which isn't working).
[HTC Rezound] yhli17:
Battery life is significantly longer if the phone can sleep well. However, I experienced that the phone wakes up and cannot sleep again, and drained battery rapidly, even screen is off. The only solution at that situation is reboot. This happens frequently. I have to switch back to CM 10.2.
[HTC Rezound] Jonman409:
Were you watching videos? I hit that the other day when using YouTube. Mediaserver held a lock and the phone wouldn't go into deep sleep.
[HTC Rezound] Dreistul:
I tried uninstalling and reinstalling, instead of restoring from TiBu. Yes, Dolphin does work now. Thanks.\

Edit: Hmm. Dolphin Zero still doesn't work. Silly Dolphin.
[HTC Rezound] yhli17:
No. I don't watch video on it. The phone wakes up itself even screen is off. For example, in midnight.
[HTC Rezound] mjones73:
Check your wakelocks...
[HTC Rezound] kcipopnevets:
For those of you still having touch problems, I may've found a fix. Since going back to 4.2.2, my problems with ghosting have subsided completely. I don't know if it'll stick if you flash 4.4 again but the weird touches and CRT animation are restored. Personally, I'm using Infection. (thanks Neo :))
[HTC Rezound] Dreistul:
New bug - mute during call

I was sitting in a conference call today and hit the mute button. After having a side-discussion with someone next to me, someone on the call asked if someone had a side-discussion going on...

so I did some testing by leaving myself some voicemails. It doesn't matter if I'm on handset or bluetooth, the mute button on the phone screen doesn't work. Yes, it shows the mute icon in the status bar, but the voice still gets sent.
[HTC Rezound] Neo:
Decepticons. We're working on getting them all out of the system.
[HTC Rezound] Hobox10:
Started having some strange issues that I didn't have before. For some reason now, whenever I boot the phone it it will cycle between my lock screen, home screen, and the screen that shows when you plug the phone into the computer. It goes through them very fast, but nothing is interactive on them. I have to hit the lock button a few times until it turns off, then I can unlock the device and use it as normal.

Secondly, apps aren't starting up on boot like they should. For example, I have to go into the Rezound proximity sensor app for it to adjust. I have set on boot check, I'm not doing anything differently than how I used it on other roms. It WAS working before too. After a boot, I'd get messages like "adfree as been giving root permissions" and then "proximity sensor has been given root permissions". Now I have to open those apps, THEN I get the notification, and then they function properly.
[HTC Rezound] Snuzzo:
Sounds like a clean slate is in order [MENTION=4641547]Hobox10[/MENTION]. Full wipe, deleting all items in internal storage, rom reflash without any app restores.