yashsingh1/xdaforums huggingface dataset:
[HTC Rezound] Po1soNNN:
true, my phone is from one of the first few production batches(manufacture date is 9/28/11) and it handles 1.8 ghz and really low undervolting with ease. Plus i've never had heat issues so I'm sure others might be different.
[HTC Rezound] tazman19:
I only get lag on aosp/aokp/cm9 with 2d rendering turned on. No lag on sense.
[HTC Rezound] RoyalDrew:
I just thought I'd chime in and maybe shed some light on this.. if it's the same issue.. here's my post in the CM9 thread.

http://xdaforums.com/showthread.php?p=31743914
[HTC Rezound] chad0989:
Hmm. Good find. I wonder if the calibration values aren't being stored properly during suspend. A workaround will be easy but I wonder what the root cause is.

Thanks for helping out. I really appreciate it.
[HTC Rezound] magicmycote:
Slow for me as well on AOSP.
[HTC Rezound] wlmeng11:
Let's try not to clog up this thread.

Sent from my HTC Rezound
[HTC Rezound] MaulingDeOso:
Seems that Sense is manually calling the unlock sysfs interface when the lock-screen unlocks, setting it to 2 (RECALIB_UNLOCK). I can tell because it reports a debug message like this:

printk(KERN_INFO "[TP]unlock change to %d\n", unlock);

when the only way such a message can pop up with a number other than 1 is through said interface. Investigating even further, the driver can never actually enter this "advanced" state on its own. Quite conniving of HTC. :(

This means it might be a little difficult to fix. I'm not sure if we have an event for the lockscreen like Sense's, so we'll probably have to somehow discard the driver's "limited" calibration state.
[HTC Rezound] chad0989:
I have an idea on how I can change the driver to make it work. I'll test when I get home and if it works I'll push it.
[HTC Rezound] iHateWebOS:
Multi touch issue is noticed in all non nexus ics roms. Cm9 merged a multi touch driver update that is thought to be the cause

http://rootzwiki.com/topic/21728-cm9-404-kang-v03-working-ffccamcorder/page__st__20
[HTC Rezound] chad0989:
Pushed a fix for the multitouch issues. It should probably be revisited / revamped in the future, but this should work for now.

Thanks MaulingDeOso for figuring out the problem.
[HTC Rezound] siulmagic:
Awesome chad, this is my que to permantly move to cm9, apreciate your work man.
[HTC Rezound] MaulingDeOso:
This is pretty much identical to what I came up with :). As I'm sure you noticed, the driver normally requires a first touch (supposedly from the swipe on the lockscreen) before recalibrating. The only thing that might need revamping is to re-add this check, but into the unlock_work callback, and poll for the first press there, pushing back the callback with the existing timeout until the press is received.

But if it still works perfectly without that extra data for recalibration, then I'm sure we're fine with just this fix.
[HTC Rezound] RoyalDrew:
First of all I'd like to thank you for all you do. I wish I had the Linux and programming knowledge you have. I do, however, still have a touch issue but I'm not certain that it is related to the multi-touch issue you have fixed. As I have said before I don't want to hijack this thread but I have a good explanation of my issue in the post linked. Only trying to help out.

http://xdaforums.com/showthread.php?p=31743914
[HTC Rezound] apophis9283:
Chad, I am new to this but I have a quick question. Any fix for not being able to turn screen on during call?
[HTC Rezound] siulmagic:
i just tested, multytouch with the multytouch testing apps form the playstore, and i can confirm the issue is completely gone, awesome job chad
[HTC Rezound] luis86dr:
Sounds like a sensor issue. Does your phone lock up during calls and you are unable to do anything until call is ended?

HTC Rezound
[HTC Rezound] wlmeng11:
Yes, that is what happens.

It is most definitely a proximity Sensor issue because it always reads "near" in Elixir 2's sensor tester.

Sent from my HTC Rezound
[HTC Rezound] apophis9283:
Works fine on sense 4 roms
[HTC Rezound] luis86dr:
I thought that as well, until it started happening on sense 4. Here's a mod if you want it disabled.

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

I went thru two Rezounds over this.

HTC Rezound
[HTC Rezound] chad0989:
Did you try a new build...?

Yeah, its not the most elegant solution but it seems to work. Haha.

Its a proximity sensor issue. They sensors HTC used are junk. Might be able to find new calibration values that work for sensor despite being dirty/worn. I just haven't had the time to sit down for hours and figure it out. That could be a good project for someone who may have some time to tinker though. Either that or if anyone has documentation for the sensor that would probably help.
[HTC Rezound] luis86dr:
Capellamicro is the manafacture for these sensors and according to them, the 3602 model has been discontinued. Can't find any documentation other then its next model which would be the CM3605. Not sure if it helps....

http://www.capellamicro.com.tw/EN/products_view.php?id=45&mode=16
[HTC Rezound] chad0989:
We need a datasheet with calibration info. Otherwise its all guess and check to figure out what values do what.
[HTC Rezound] luis86dr:
Just contacted the manufacture to try and receive a datasheet on this product. Waiting for a response.

HTC Rezound
[HTC Rezound] RoyalDrew:
Wow guys sorry I had read in the changelog on the cm9 thread that it was fixed and mistakenly thought I read it on Neo's new build. My bad! =/

Keep up the good work!
[HTC Rezound] dyetheskin:
here's some logcat info on what could be causing lockups on all aosp based roms. beyond me figuring out why lockups occur on everything
[HTC Rezound] Neo:
Which rom in particular was this log pulled from?
[HTC Rezound] dyetheskin:
your new rage rom. same errors are on your aokp, all of the remaining cm9 builds and miui. so it's not generally specific to one rom
[HTC Rezound] ej1911:
I'm not sure if this is helpful or not with the proximity sensor, but evidently the Desire HD uses the same sensor. Evidently someone wrote an app to calibrate the sensor because of familiar sounding problems. . If the app itself is not helpful, the source is on github.

http://www.google.com/url?sa=t&sour...GgoOahyC8_WtyOuYA&sig2=Z_EDisxz_Y7XjaGHI3SU_w
[HTC Rezound] luis86dr:
Wont work with our kernels, but we may get some useful info from Github. Still waiting on a response from the manufacturer. It's Saturday so I'm sure they won't contact me back until Monday during business hours.

HTC Rezound
[HTC Rezound] chad0989:
Good find. Pretty sure I can easily modify it to work for us. We can use it to find solid default values for the majority that I can incorporate. If there are any crazy outliers beyond that then they can use the app.

Thanks man.
[HTC Rezound] chad0989:
Okay. I modified that app to work for us and got some values that work great for my sensor. I'm going to contact the guy who wrote it and make sure he's cool with me distributing the modified version.
[HTC Rezound] kryptik06:
nice! also I may have a fix for Bluetooth. I have been playing around with it. Will post if it works
[HTC Rezound] Snuzzo:
I get this when trying to build from a fresh synced source

http://pastebin.com/vQqbegVe

Going to look into it further later on.
[HTC Rezound] chad0989:
Prox sensor app guy never got back to me. Guess I'll just have to write my own app, should only take a few hours as its pretty simple.
[HTC Rezound] chad0989:
Almost done. Just need to have it write the values when they change, which is really simple to do. I'll finish it up tomorrow if I have the time.
[HTC Rezound] renzo.olivares:
meh still cant get JB to boot if anyone wants to try https://github.com/Joelz9614 it compiles fine just doesnt boot
[HTC Rezound] xFonzie:
Have you any clue as to what may be causing it not to boot? If I had more time tonight, I'd go ahead and build to try it out.. but unfortunately, that isn't the case.
[HTC Rezound] Snuzzo:
Had to git reset back to commit 1cd7487594055690d88804b8751c3dd6d81a20ce to get it to build.
[HTC Rezound] MaulingDeOso:
Here's why the speaker is discarding the right channel:

On Sense:

<6>[ 5.912353] [AUD] htc-acoustic: open
<6>[ 5.912384] [AUD] htc-acoustic: support_a1026: 0
<6>[ 5.912384] [AUD] htc-acoustic: release
<6>[ 5.922546] [AUD] htc-acoustic: open
<6>[ 5.922637] [AUD] htc-acoustic: get_speaker_channels: 1
<6>[ 5.922729] [AUD] htc-acoustic: release

When the device is opened (sound plays):

<6>[ 384.346954] [msm8x60.c:msm_device_put] device speaker_mono_rx set 1
<6>[ 384.347076] [AUD] snd_soc_msm8x60: [ALSA] msm_en_device (dev speaker_mono_rx, id 24, enable 1, opened 0)

AOSP:

<6>[ 5.493286] [AUD] htc-acoustic: open
<6>[ 5.493408] [AUD] htc-acoustic: open
<6>[ 5.493591] [AUD] htc-acoustic: support_a1026: 0
<6>[ 5.493713] [AUD] htc-acoustic: release
<6>[ 5.493896] [AUD] htc-acoustic: setting size = 72798

Then

<6>[ 430.129516] [msm8x60.c:msm_device_put] device speaker_stereo_rx set 0
<6>[ 430.129669] [AUD] snd_soc_msm8x60: [ALSA] msm_en_device (dev speaker_stereo_rx, id 2, enable 0, opened 1)

Note that it never polls the speaker information and assumes instead that we have stereo speakers. We're also missing a whole block of device enumeration right afterwards ala:

<6>[ 5.923675] [msm8x60.c:msm_device_put] device handset_rx set 0
<6>[ 5.923767] [AUD] snd_soc_msm8x60: [ALSA] msm_en_device (dev handset_rx, id 0, enable 0, opened 0)
<6>[ 5.923919] [msm8x60.c:msm_device_put] device handset_tx set 0
<6>[ 5.924102] [AUD] snd_soc_msm8x60: [ALSA] msm_en_device (dev handset_tx, id 1, enable 0, opened 0)
<6>[ 5.924194] [msm8x60.c:msm_device_put] device headset_mono_tx set 0
<6>[ 5.924346] [AUD] snd_soc_msm8x60: [ALSA] msm_en_device (dev headset_mono_tx, id 3, enable 0, opened 0)
<6>[ 5.924499] [msm8x60.c:msm_device_put] device speaker_mono_tx set 0
<6>[ 5.924591] [AUD] snd_soc_msm8x60: [ALSA] msm_en_device (dev speaker_mono_tx, id 4, enable 0, opened 0)

I think the bluetooth calling problems might be intertwined in this.
[HTC Rezound] chad0989:
Good find. That's interesting. Hmm...
[HTC Rezound] MaulingDeOso:
Things first deviate from Sense at the second line here:

<6>[ 5.045654] [AUD] apr_tal: apr_tal:Q6 Is Up
<6>[ 5.484283] [AUD] snd_soc_msm8x60: [ALSA] msm_end_voice
<6>[ 5.485198] [AUD] q6voice: auddev_cb_function, evt_id=64,
<3>[ 5.487182] msm_reset_put:Resetting all devices
<6>[ 5.488464] [AUD] audio_dev_ctl: msm_clear_all_session:

Really seems like at least one of our device drivers is giving up. We see the msm_end_voice function, indicating to the driver to end a call, when no call has started. Then a subsequent collapse of the audio drivers. There should be more reports from the snd_soc_msm8x60 driver, but it disappears completely without an error message. The audio subsystem is only partially initialized, which might explain a lot of our remaining problems.
[HTC Rezound] Flyhalf205:
I know this doesn't effect anything. so it isn't a big deal but in https://github.com/Chad0989/device_htc_vigor/blob/ics/recovery.fstab

Isn't /dev/block/mmcblk0p37 Gingerbread? Shouldn't it be mmcblk0p38 for ICS firmware?
[HTC Rezound] chad0989:
Dimming works fine. 100 is noticeably dimmer than 255, and 50 even more dim. Change the setting and blank and unblank the screen.

As for them turning off. That's the way CM9 is, not a bug.
[HTC Rezound] chad0989:
Yes it should be. I never bothered to fix any recovery stuff since we don't use it.
[HTC Rezound] chad0989:
Prox sensor recalibrator app:

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

DO NOT reply in this thread (Dev thread) regarding the app. Use the thread dedicated to the calibration app.
[HTC Rezound] Vashypooh:
Thanks, I guess the black and unblack screen is what I was missing.
[HTC Rezound] chad0989:
Merged upstream commits into frameworks_base. There's a commit in their that should fix video calling w/ skype etc. Thanks to tbguy for pointing out the commit.
[HTC Rezound] GrayBoltWolf:
I shall go build....

That will fix google hangouts also?
[HTC Rezound] chad0989:
You'll have to try it. I don't use skype or hangouts so I'm going on what the commit says.
[HTC Rezound] Snuzzo:
I want to apologize to you Chad. No errors in compiling after I raised memory from 2gb to 4gb in my Vmware machine.
[HTC Rezound] GrayBoltWolf:
I don't either. :)

I go by what the people complain about in the megathread.

---------- Post added at 04:50 PM ---------- Previous post was at 04:50 PM ----------

I rock it out with 2gb.
[HTC Rezound] TheBr0ken:
You both got me beat. My VM VirtualBox builds on 1536mb (Mint 13 x64). Only got 4gb on my work PC and I probably should also use it for work :p. It builds real slow, but it builds. Syncing a new repo will take me a day, easy. I started building at about 10 this morning and its 4pm now and its still going. Im in no rush, if I need to I can always boot to my secondary build drive running full Mint for an hour and a half build, but that makes work much harder.

Using the VM strictly for cm9 through Chads sources, and the secondary drive for AOKP and my efforts towards pure AOSP, and that's kicking my butt. Couldn't be done without your efforts Chad, appreciate you keeping our devices relevant.
[HTC Rezound] a.mcdear:
Number of cores on the machine may have something to do with how much RAM is required to complete the compile without errors.
[HTC Rezound] TheBr0ken:
Intel E6300 2.8Ghz Core 2 Duo. Probably wouldn't be much different building on my VM that it would be if I could build on my Rez, lol! I just brunch vigor, which probably defaults to -j4. Have not tried anything larger.
[HTC Rezound] GrayBoltWolf:
Well, I allready have it built and uploaded. Seems faster than usual.

Is there a way to only build what has changed and merge those changes into an older build? Would save a ton of time.

Seems silly to build the whole thing for one tiny change.
[HTC Rezound] antp121:
Depends where the commit is. Most likely yes if it's app/kernel related idk about anything else lol
[HTC Rezound] GrayBoltWolf:
Hmm.....

If I could just pull that certain app.....

Chad, what do you think?
[HTC Rezound] antp121:
You can build apps seprately. Like one at a time. I don't remember how though :confused:
[HTC Rezound] Neo:
He said Frameworks_Base so I just deleted my Frameworks_Base folder and repo synced. Didn't take long with my modified manifest that pulls from his Gitbhub.
[HTC Rezound] Snuzzo:
Keep your out folder and don't do a make clobber.
[HTC Rezound] GrayBoltWolf:
Sorry Chad, tester says that it still crashes. :(

And Snuzzo, where is the repo stored at locally? So I can just pull stuff from there and pop it onto the .zip?
[HTC Rezound] Snuzzo:
Come again?
[HTC Rezound] chad0989:
I don't recommend this. It often doesn't build the changes in the device tree if you don't clobber.
[HTC Rezound] chad0989:
Resync and rebuild. I forgot to push the commit that sets the flag. And make sure you clobber because changes in BoardConfig often don't rebuild.
[HTC Rezound] GrayBoltWolf:
oh....

Yay, wated 4 hours on nothing..... -_-

:)
[HTC Rezound] Snuzzo:
Completely forgot about that. Sorry wolf. I apologize, bad adivce on my part. :o

@Wolf

The project's .git files and manifests are stored in a hidden folder, .repo.
[HTC Rezound] apophis9283:
Nvmd.
[HTC Rezound] GrayBoltWolf:
Sweet. I'll take a look tonight.

Got a guy testing the new new build, we will see what happens.
[HTC Rezound] wildstang83:
You sure it's a guy?
[HTC Rezound] howellcp:
Yes. I'm a guy and I love testing roms.

---------- Post added at 08:44 AM ---------- Previous post was at 08:17 AM ----------

It works! Good Job Chad, Thank you Graywolf for letting me test!
[HTC Rezound] Snuzzo:
I think the culprit has been found for the wifi wake lock. Got a test build to another member.
[HTC Rezound] cslingerland:
Thank god! Its so annoying lol.
[HTC Rezound] wildstang83:
lol https://twitter.com/wildstang83/status/252120541916446722
[HTC Rezound] Snuzzo:
Lmao

I don't use wifi. ;)
[HTC Rezound] MaulingDeOso:
Got the sound channel problem fixed. Not as deep of a problem as I thought. There are two ways to fix this, in the kernel or in the AudioHardware module in qcom/hardware/media. Attaching both patches--take your pick.

In the process I noticed a property that might help with the issue reported where one's own voice can be heard during a call:

persist.audio.vr.enable

An AOSP-only property for the Fluence Voice recognition (http://www.qualcomm.com/solutions/multimedia/voice/fluence). Setting it to 'true' allows the dual microphone device to be opened, and probably enables voice cancellation.

There's also a couple of permission inconsistencies in /dev. Not sure if those will be a problem; I still have to go over them.
[HTC Rezound] Snuzzo:
Oooo thank you thank you!!! I will incorporate it into the kernel, you caught me right before I started brunching and updating the kernel to reflect the wifi wakelock fix.
[HTC Rezound] chad0989:
Interesting. I'm glad it turned out to be relatively simple.

I appreciate all your help. I'll build/test and push it sometime today. Probably going to go with the kernel change as that way we can keep using the CM mainline qcom/hardware/media.
[HTC Rezound] Snuzzo:
Got native tether working using the AOKP binaries from hardware/broadcom_wlan. Doesnt seem to like WPA2 though.

EDIT:

Doesnt work with any type of security.
[HTC Rezound] shrike1978:
Got init.d working.
[HTC Rezound] cslingerland:
curious! how... :)
[HTC Rezound] shrike1978:
It was a ramdisk issue. run-parts was never getting called on the folder from init.rc. The commit is in my git: https://github.com/shrike1978/device_htc_vigor/commit/e6a644216085edf85a7002e4d9fb554f36fe2d0c

A little birdie told me you might be seeing it show up in a ROM really, really soon. ;)
[HTC Rezound] Snuzzo:
Thank you thank you thank you!!!! Now to get that collaboration going and get this build rolling. I got a another goodie that you're going to be seeing soon too. Now do a pull request to Chad0989.
[HTC Rezound] kingpin003:
https://github.com/Chad0989?tab=activity

Chad's too fast for you, Snuzzo. :P
[HTC Rezound] shrike1978:
Already done. ;)
[HTC Rezound] docbutts:
Rezound dev community RULES!

Sent from my apple IIgs
[HTC Rezound] Snuzzo:
Oh hell. Now I feel embarassed.
[HTC Rezound] michaelnhf:
Hey guys, I've been working with snuzzo on an issue where 5ghz wifi can be seen but won't connect. It works on sense roms with his kernel but fails on all aosp rooms with his kernel or not.
[HTC Rezound] Snuzzo:
Ok if he's not able to test(I know I can't due to being afk) someone try the binaries from the global ruu on a fresh synced build from Chads repo in github. This is what I have him looking into as I'm believing it not be kernel related.
[HTC Rezound] a.mcdear:
I connected to a 5ghz network last week just fine....
[HTC Rezound] Snuzzo:
Whoa wait, what build?
[HTC Rezound] darienms1986:
I connect to my home network on 5ghz on rage rom
[HTC Rezound] michaelnhf:
What security settings are u using on ur wifi
[HTC Rezound] darienms1986:
Wpa2 i think. I can't remember off the top of my head. My guest network is running on 2.4ghz and my home is 5ghz
[HTC Rezound] Hanger84:
Works just fine for me. Using my build from yesterday with Funky Kernel.

*EDIT* Forgot to mention that the security is WPA2/WPA Mixed Mode on a Linksys E3000 router. No loss of speed or an issues at all.

I think the issue may be subjective to router and security settings. If anyone has issues, try restarting the router and change the security setting to None and go from there. Some routers implement security differently depending on manufacturer.
[HTC Rezound] scy1192:
Are you sure your router doesn't broadcast at both 2.4 and 5.0 at the same time? AFAIK most of them do and if the connection to 5Ghz fails it'll use 2.4Ghz.
[HTC Rezound] darienms1986:
Yes I'm sure. I have 2.4ghz shut off for my connection. I have the option for either or both to be on
[HTC Rezound] kingpin003:
Actually have the same router and I'm connected to a 5ghz network now. WPA2 security.
[HTC Rezound] michaelnhf:
Hmm I have an e4200 and an e3000, I use the 4200, tomorrow I will try the 3000. But the fact is I can connect to my current 5ghz on a sense from and not an aosp. I use wpa2 on an n broadcast
[HTC Rezound] scy1192:
I guess I can confirm 5 Ghz wireless working too, if the "5 Ghz only" option in the advanced Wi-Fi settings is doing its job. I don't know the router because the internet is provided by my university, all I know is that it's Cisco, probably enterprise class, with WPA2 (802.1x EAP).
[HTC Rezound] michaelnhf:
Just changed my router from n only to mixed on the 5ghz band and it will now connect. But it would connect under n only on sense.
[HTC Rezound] Deathbyfugu:
This isn't development, people. Post in the CM9 thread regarding WiFi frequency issues.
[HTC Rezound] Snuzzo:
That was my error then, if you felt it was wrong for me to have him post here report my previous post. Read where I had him mention it.

http://xdaforums.com/showpost.php?p=32467791&postcount=479

At the time I tended to beleive it was a development issue and I've been (Read: was) digging to correct it (Read: and since stopped dwelving). Everyone else just started chiming in.
[HTC Rezound] papaavi:
Crowdsourced responses for developers that need testers could be in a separate thread in association to this thread, while still keeping this one clean for dev talk. Could be good to use whenever a dev here needs lots of readily available people of varying skill levels to test something out.
[HTC Rezound] dmeadows013:
Well since Chad's been busy I'm stepping in for a few :p gonna have a test build for a certain tester tonight of JB. When we get JB booting, do you think we should start another R&D thread for it or keep this one? I'm asking since they're two different platforms and I don't want things to get crowded. I would make a poll but idk how lol
[HTC Rezound] Neo:
I'll test if you promise not to brick me :P
[HTC Rezound] dmeadows013:
I'm not gonna try and brick lol. I'm using Siul's ramdisk for the time being. Just getting it to boot
[HTC Rezound] wildstang83:
Make a new thread. DUH
[HTC Rezound] wlmeng11:
Stay s-on or get a jtag kit to revive your phone.

It would be nice if someone had a jtag kit so they could test everything. Bounty time? Lol

Sent from my HTC Rezound

Oh and new thread of the of course.
[HTC Rezound] RoryHe:
Make a new thread and you can send me the test too devin! xD if you want
[HTC Rezound] Neo:
Let me know when it's ready then :)
[HTC Rezound] evilstewie23:
Thought you only cared about ics. :p

I think we should start a new thread though also

Sent from my Rezound high on cm9!
[HTC Rezound] antp121:
;) I'm excited.
[HTC Rezound] GrayBoltWolf:
New thread. Idiots will post and get confused.

Chad disappeared, so it is good to see someone filling in for a bit.
[HTC Rezound] dmeadows013:
New thread will be started when it boots. For now, posts in this thread should be stopped per Chad's request in the OP :)
[HTC Rezound] MaulingDeOso:
Well, it strikes me that it's not correct to specify our own core init.rc in the device tree; there should only be a init.vigor.rc file. The custom one (at least the one in Chad's tree) is overwriting the system file, which has changed a bit in the transition to JB. We really should just use the AOSP version, and put any necessary customizations for it (are there any?) into the device specific file..

That said, in that file, aside from the permission differences and lack of a couple of daemons, we're missing this particular line:

exec /system/bin/sysinit

whose absence might have consequences.

In the init.vigor.rc file, there's the new /storage mounting location, and the handling of some services like wifi have changed, both are pretty simple.
[HTC Rezound] shrike1978:
FYI, CM updated the android_build repo this morning and it broke my build environment. I had to run "touch ~/.netrc" to fix it.
[HTC Rezound] Snuzzo:
Ok let me check my log( I havent sync'd recently) and see if I can push it to my hub.

EDIT

Done
[HTC Rezound] Neo:
I'm going to be resyncing tomorrow so that's good to know Shrike
[HTC Rezound] wildstang83:
This post has nothing to do with this subject. I just love how tight knit the community has come here. Keep up the good work guys.