yashsingh1/xdaforums huggingface dataset:
[HTC Rezound] dmeadows013:
Actually fairly easy. The jellybean kernel is Linux 3.031, so no major jumps there. Just a few changes for gcc fixes etc etc

Via my Google Galaxy Nexus with Butter
[HTC Rezound] Marine6680:
Good to hear. I was thinking that would be the case, I knew the kernel change was minor. Most of the JB changes seemed to be higher level.
[HTC Rezound] chad0989:
Hardest part is getting the init stuff right so it'll boot.
[HTC Rezound] Vashypooh:
Edit: Thanks for the link.
[HTC Rezound] GrayBoltWolf:
We need to stop.

What I said was how to calibrate the battery percentage meter on the phone, never said it was good for it.
[HTC Rezound] MaulingDeOso:
The Linux Kernel != Android Kernel. The changes might be more than just the vanilla Linux patchsets.

There's some problems with recent binutils, too. At least a few changes are required because the armv7-a arch no longer implicitly allows security extensions. Most of the userspace libraries seem to be OK, for obvious reasons.

Compiling with a fully modern toolchain brings a significant optimization advantage, so it's in everyone's best interests to do so. :)
[HTC Rezound] antp121:
Well we already have 3.0.42 kernels sooo....
[HTC Rezound] Bensky91:
Chad, nice work on all of this. I am jobless but start at my new job on Monday hopefully. I'll have a donation for you soon.

Question: does the latest kernel on your github have the camcorder fix found in "uberkernel" integrated? I'm planning to build CM9 myself soon since I don't use bluetooth.
[HTC Rezound] MaulingDeOso:
By pulling the patchsets for the Linux Kernel (kernel.org). These are bug fixes on a stable branch. Not any major changes that were made strictly for Android. This is one of those cases where the version number doesn't matter that much.

I've got the kernel building fairly easily with the latest NDK toolchain after applying changes similar to this patch: http://review.cyanogenmod.com/#/c/12224/

and by suppressing some fairly pedantic warnings.
[HTC Rezound] dmeadows013:
Yup. If you look at intervigilum's jb kernel it just has a few changes for wifi and gcc fixes.

Via my Google Galaxy Nexus with Butter
[HTC Rezound] chad0989:
Everything is up. Good luck have fun.
[HTC Rezound] Neo:
Rock on thanks. Hoping to have the first AOKP nightly up tonight with the revisions.
[HTC Rezound] dmeadows013:
This should fix the wifi issue by the way. Only issue I know of atm is FFC toggle just makes it main camera upside down lol. Investigating it now.
[HTC Rezound] Neo:
No it doesn't? Not on my build?
[HTC Rezound] dmeadows013:
Gonna see if it's my hardware... Flashing Sense :p
[HTC Rezound] dmeadows013:
K so the wifi issue still persists... Wasn't PMEM. Heres a log http://pastebin.com/ZK9Nr76u

On another note, got a tree for JB going. I think I can get it to boot with the init stuff I have. I'll keep updating
[HTC Rezound] renzo.olivares:
well heres my jellybean tree/vendor/and msm8960-common

if anyone wants to help or anything https://github.com/Joelz9614

will be working on it throughout the week doesnt boot yet, but it wont brick you either
[HTC Rezound] dmeadows013:
Think I may have gotten it booting we will see :)
[HTC Rezound] MaulingDeOso:
Chad, the Adreno drivers you committed don't seem to be the same as mine.

https://sites.google.com/site/bearoso/misc/adreno2184622.zip

Using these instead hilariously produces a smooth 60fps home screen for me, while your current ones lag just as things did before. I pulled these from a Galaxy S3. I don't honestly know what the difference is, considering the version numbers match, but there you go. :confused:
[HTC Rezound] Po1soNNN:
If they're the same version as our latest would it be okay to maybe flash on cm9?

A little off-topic, sorry...
[HTC Rezound] MaulingDeOso:
They're not the Jelly Bean version, so they definitely work. I'm using them with my build and they're fast enough to get Trebuchet and Nova up to 60fps. It's actually nice to finally have the stock launchers smooth on this phone. :)

Note that the zip I posted is just the libraries, so you can't flash it. If you want to try them you'll have to copy them into place or into a build tree. Or get someone who, unlike me, is familiar with recovery scripts to make a zipfile for you.
[HTC Rezound] Po1soNNN:
Thanks, I think I can handle copying them. Just copy and reboot?
[HTC Rezound] fo0you:
Updated drivers in flashable zip attached
[HTC Rezound] Po1soNNN:
Thank you. I just looked at them and realized that werent organized by directory they are supposed to go in.:good:
[HTC Rezound] MaulingDeOso:
There's still a little something off, like with Chrome and Nova's app drawer. But performance is acceptable enough for me now, and I'm sure Qualcomm's Jelly Bean drivers will have to completely accelerate the relevant operations in order to be compatible.
[HTC Rezound] dmeadows013:
Put my Jellybean trees on Github. Everything needed for AOKP is there. Just clone to where it goes :P here's the device tree in case anyone wants to check out the ramdisk. Still won't boot.

https://github.com/dmeadows013/platform_device_htc_vigor

If you want to download it all plus the AOKP source, here's the manifest to initialize.

https://github.com/dmeadows013/platform_manifest
[HTC Rezound] chad0989:
Sure, I'll give them a shot.
[HTC Rezound] Obaterista93:
Not a developer, but I did copy them over and try them and as mentioned, things are much smoother, but things like the app drawer and such are still a little buggy.
[HTC Rezound] chad0989:
Just tried them. Way way better. Quadrant jumped about 300 also. Will update to them in my tree.
[HTC Rezound] Vashypooh:
There currently is a call quality issue where you can hear everything you say in the headset played back in the speaker when you talk.

Is this an issue at your level Chad? Or a general AOSP issue for our phone to be fixed in the roms?
[HTC Rezound] chad0989:
I've never gotten it. Can anyone confirm it after they built directly from my trees with no changes?

Its pretty hard to fix something when I don't have the problem. Haha.
[HTC Rezound] howellcp:
Chad. Its not you issue. It's a particular Rom.
[HTC Rezound] TheBr0ken:
I built directly from your trees this morning and have placed quite a few calls today, I have not had that issue
[HTC Rezound] antp121:
it cant be. not every one has the issue. its strange. some phones get it, some dont.
[HTC Rezound] Vashypooh:
I've had it in every CM9 build released so far. Every one, built by dif people.

I flashed to a sense rom to see if my phone was bad, but it was not present.

Not sure.
[HTC Rezound] antp121:
im running mine. absolutely no problems. idk.
[HTC Rezound] keolawills:
I get that issue randomly no matter what rom, radios, firmware, etc I've tried. It even happens to me stock un rooted.

Sent from my ADR6425LVW using Xparent SkyBlue Tapatalk 2
[HTC Rezound] chad0989:
New adreno libs have been pushed. I fixed the torch yesterday too, not sure if anyone noticed.
[HTC Rezound] Neo:
First AOKP nightly building now. Successfully so far.. With all of Chad's changes. I will let you guys know if the call quality issue is present in it or not (should it actually complete)

-Neo
[HTC Rezound] howellcp:
Just an fyi, video from front camera keeps force closing. I've tried it on all cm9 roms out right now. Flashed back to sense an it worked.
[HTC Rezound] shrike1978:
Just took a pic with the FFC and it worked fine for me.
[HTC Rezound] howellcp:
Picture works. Try doing a video chat from google+ or Skype.
[HTC Rezound] wlmeng11:
Front facing video works in the camera app.

It's only 3rd party apps that utilize the front camera.
[HTC Rezound] Neo:
Yeah video recording works fine but the integration with skype and Gtalk fc's. I'm pretty certain it will on this build that completes as well. As with all things though, it will inevitably be fixed!
[HTC Rezound] MaulingDeOso:
It actually seems like Qualcomm is adding acceleration piecemeal with new releases, replacing the software fallback functions far too slowly and incompletely. Some things get faster, others remain the same. Sometimes newly fast GPU operations get mixed with unaccelerated software ones and force GPU framebuffer reads, which ends up slowing things down.

The boon of Jellybean is that the rendering path is supposed to remain entirely on the GPU. So those fallbacks will hurt significantly more, and they'll hopefully be forced to fix them. I guess we'll have to wait and see.
[HTC Rezound] dmeadows013:
Made a couple changes to the ramdisk but it did nothing. If anyone can get it dl my tree and submit a pull request :)
[HTC Rezound] kryptik06:
OMFG.. spent 2 hours trying to find out why i kept getting stuck on repo sync with chad's github. Turns out cyanogen changed up the default.xml to point the android_prebuilt to asop. So with that being said if your like me and tried syncing from Chad's repo make sure you edit line 254 on the default.xml and replace

<project path="prebuilt" name="CyanogenMod/android_prebuilt" />

With this

<project path="prebuilt" name="platform/prebuilt" remote="aosp" revision="refs/tags/android-4.0.4_r2.1" />
[HTC Rezound] chad0989:
Thanks. I'll fix it.
[HTC Rezound] Neo:
Also, if you had not noticed, it looks for a required file extracted from term.apk that returns a 404 error as it is no longer on github. Google for the file or extract it yourself, create the directories it's required to be placed in, place it in there and modify your get-prebuilts script to # out those two lines regarding that apk. Remember to change permissions in order to run that script again after you've pushed it back.
[HTC Rezound] young0ne:
Hey devs i just finish talk to one of my guys here at AT&T who works with wireless and land-line regarding the hear yourself issues. he told that it could be bandwidth allocations for the voice so this issue is most likely at the software level I hope that that can help.
[HTC Rezound] af974:
Thread temp closed for cleaning.

LOL 1 report was enough not 14 !! ROFL

EDIT: Up again, there were not so much to clean, only 10 posts.

Please guys, when you see that a thread needs a cleanup just report the first off-topic post writing " clean needed" or PM us.

Do not report any single off-topic post.

Thanks.
[HTC Rezound] siulmagic:
Im not sure if this happens on stock aosp kernel ,but the multy touch driver is very broken, if you download an app like, multytouch tester or multytouch visualizr, you will notice , once you make more than one touch it will eventaly start to skip around or jump around the touch points, if you place 4 fingers it will completely go crazy, and barely detected any touch input. logcat does not seem to report anything wrong, so i grabbed a dmesg,

Here it is http://pastebin.com/YnmMepHN

Hopefully this helps abit to solve this issue.
[HTC Rezound] wlmeng11:
That happened to me as well.

It happened on stock sense as well if I used a third party lock screen, though I doubt that is the issue here.

Sent from my ADR6425LVW
[HTC Rezound] Snuzzo:
That's false. I'm not having an issue with pinch to zoom on the aosp browser.
[HTC Rezound] wlmeng11:
I found that there are only issues if you are using two fingers, then lift one finger.

It doesn't affect pinch to zoom.

However, it makes gaming nearly impossible.

Sent from my ADR6425LVW
[HTC Rezound] siulmagic:
this is how i first notice something was wrong, playing mc3 was imposible.

---------- Post added at 05:10 PM ---------- Previous post was at 05:09 PM ----------

its not a false, you have to give it time and move around the 2 touch points to trigger it, i doubt pinch to zoom would be affected by this, since the action is so brief.
[HTC Rezound] Snuzzo:
Interesting, so it only effects more than 2 touch points?
[HTC Rezound] siulmagic:
its does affect 2 touch points, but they would have to held for a couple of seconds, its clearer to see if with a multytouch test app.
[HTC Rezound] z0mghii:
I knew it! I felt that the pinch to zoom was a little bit glitchy while browsing. It just felt like something was wrong.
[HTC Rezound] chad0989:
Updates pushed
[HTC Rezound] Bytecode:
Hello! I'm not a rezound developer,but I am posting here because I am facing an error you guys had too:

I am getting this on JB AOKP also. If you don't mind,can you guys tell me how did you fix this annoying error? :)

P.S: I am working for a msm7x27 device,the LG-P500 ;)
[HTC Rezound] MaulingDeOso:
Here's what's wrong with wifi:

https://github.com/Chad0989/device_htc_vigor/commit/5e15edf51827607e1f2f7781221e333816546e84

You've changed it so several of the permission setting and directory creation lines occur "on init", when /data is only mounted r/o. These need to go back into "on boot". Also make sure to properly indent that bcmdhd.ko module line.
[HTC Rezound] dmeadows013:
Yea I thought it was something there lol. Was gonna fix it today. The :)

Via my Google Galaxy Nexus with Butter
[HTC Rezound] chad0989:
Wifi works fine...
[HTC Rezound] Po1soNNN:
aokp wifi?
[HTC Rezound] chad0989:
Oh. Don't know about that. I don't do or keep up on aokp.
[HTC Rezound] MaulingDeOso:
Try wiping your /data, like for a clean install. It erases some necessary directories and they're not able to be recreated properly with said commit.

This is the problem they've been experiencing with recent builds in the other thread: http://xdaforums.com/showthread.php?t=1885553&page=12, and why with dirty flashes it still works.
[HTC Rezound] chad0989:
Oh. Okay. I'll fix it then. Thanks I appreciate it.
[HTC Rezound] GrayBoltWolf:
Awesome.

We had to pull links. And a few people mentioned that Bluetooth wake lock was still not fixed but I have no idea.
[HTC Rezound] siulmagic:
Chad have you had any chance to take a look at the multytouch issues.? thanks again for your hard work.
[HTC Rezound] chad0989:
I think its fixed now. The latest changes I made seem to allow me to disable Bluetooth quick switch where before it would freeze and cause reboots. This seems to let it release the lock.

I'll take a look.
[HTC Rezound] GrayBoltWolf:
You rock.

So you just pushed changes?

Any luck on wifi?
[HTC Rezound] chad0989:
I pushed that too.
[HTC Rezound] GrayBoltWolf:
Wifi fix?

Awesome. Building now.
[HTC Rezound] Snuzzo:
Wifi was never broken.
[HTC Rezound] Max725:
See these posts on the previous page:

Also, AOKP Wi-Fi has been having issues.
[HTC Rezound] Snuzzo:
And also see my proven screenshots.

http://xdaforums.com/showpost.php?p=31644994&postcount=116

AOKP I know is without a doubt an issue.
[HTC Rezound] apophis9283:
As soon as wifi is fixed, I am jumping on the AOKP train!
[HTC Rezound] wlmeng11:
There is a workaround for the wifi issue on aokp.

Toggle the built in wifi tether on and off.

Unfortunately, you have to do this every time to turn on wifi.

Sent from my HTC Rezound
[HTC Rezound] GrayBoltWolf:
Dirty flash it worked. Clean install and it wouldn't even turn on.
[HTC Rezound] Snuzzo:
I don't do any dirty flashes. It was working fine here. Again no idea how/why if everyone else was having issues.
[HTC Rezound] kryptik06:
Clean install worked also for me but Wi-Fi would not sleep
[HTC Rezound] dmeadows013:
Got JB to logcat using ICS ramdisk and JB kernel. Getting this iptables error

E/BandwidthController(3892): runIptablesCmd(): failed /system/bin/iptables -A bw_INPUT -i lo --jump RETURN res=65280

EDIT: here's the full error that just loops in the logcat

I/Netd (11059): Netd 1.0 starting
I/Netd (11067): Netd 1.0 starting
E/BandwidthController(11067): runIptablesCmd(): failed /system/bin/iptables -N bw_INPUT res=65280
E/BandwidthController(11067): runIptablesCmd(): failed /system/bin/iptables -A bw_INPUT -i lo --jump RETURN res=65280
D/MDnsDS (11067): MDnsSdListener::Hander starting up
E/Netd (11067): Unable to start MDnsSdListener (Success)
E/SocketListener(11067): Obtaining file descriptor socket 'mdns' failed: Success
I/Netd (11154): Netd 1.0 starting
I/Netd (11146): Netd 1.0 starting
E/BandwidthController(11154): runIptablesCmd(): failed /system/bin/iptables -N bw_INPUT res=65280
E/BandwidthController(11146): runIptablesCmd(): failed /system/bin/iptables -N bw_INPUT res=65280
E/BandwidthController(11146): runIptablesCmd(): failed /system/bin/ip6tables -N bw_INPUT res=256
E/BandwidthController(11154): runIptablesCmd(): failed /system/bin/iptables -A bw_INPUT -i lo --jump RETURN res=65280
D/MDnsDS (11154): MDnsSdListener::Hander starting up
E/Netd (11154): Unable to start MDnsSdListener (Success)
E/SocketListener(11154): Obtaining file descriptor socket 'mdns' failed: Success
E/BandwidthController(11146): runIptablesCmd(): failed /system/bin/iptables -A bw_INPUT -i lo --jump RETURN res=65280
D/MDnsDS (11146): MDnsSdListener::Hander starting up
E/Netd (11146): Unable to start MDnsSdListener (Success)
E/SocketListener(11146): Obtaining file descriptor socket 'mdns' failed: Success
[HTC Rezound] brando56894:
WiFi hasn't worked for me using Joel's BAMF kernel using the last two CM builds, IDK if it's his fault or CM's fault. It works fine for me with the stock kernel. Either way keep up the good work.
[HTC Rezound] shrike1978:
The kernel for AOSP is in constant flux until all the issues are resolved. Any changes that Chad makes in the ROM that require kernel changes will break custom kernels until they are rebuilt with the new code.
[HTC Rezound] chad0989:
Can anyone get me a logcat while making a call on a bluetooth headset on an ICS sense rom? Thanks.
[HTC Rezound] RoryHe:
Hey chad, i was wondering if you were planning on taking a look at mhl? Wolf says it doesn't work in cm9 so i guess im asking if you were planning to look at it.

It would be cool if you could look into it and a lot of people would probably like it too. you've already done so much i feel weird asking :/ you're great man for all of this, i don't know how you do it.
[HTC Rezound] kingpin003:
Here's a Pastebin of a call. It should be pretty close to the end of the logcat.
[HTC Rezound] chad0989:
Sense rom?
[HTC Rezound] chad0989:
Said I was going to. I can't make any guarantees though.

Edit: it might actually be easier than I thought. Still no guarantees though.
[HTC Rezound] kingpin003:
No. That was from kryptic's 9/18 build. Clean flash. I had just flashed it and didn't want to immediately flash the vanilla just to logcat. I can now if you'd like now since I've got all my apps reinstalled and nandroided. Would that help you?
[HTC Rezound] roosxter:
I was on the cm9 build for about 45 min, no drop in 4g at all
[HTC Rezound] tihs:
Great work guys - Loaded CM works great saw no issues with 4g -

here are the things that I did see -

1. Bluetooth does not turn on.

2. Unable to get to the external SD card. ( this is prob a ROM issue )

thanks again for all your hard work!
[HTC Rezound] jclendineng:
I'm doing a repo sync with aokp source code atm will try to build a aokp rom tonight.
[HTC Rezound] maniac2k:
TO WHOM IT MAY CONCERN:

This is a DEV ONLY thread.

Please respect the OP's request.

Thank you!
[HTC Rezound] chad0989:
Updated dsp presets and audio profiles. Audio sounds much better now.
[HTC Rezound] dmeadows013:
Nice work Chad. Question... After a while I go from 4G to Roaming (R). Is this the drop you were talking about and R is really just 3G?
[HTC Rezound] a.mcdear:
Gonna go ahead and give this a shot tonight to see if I can get EOS2 ICS to compile and run.
[HTC Rezound] chad0989:
No. The roaming thing was a eri.xml issue according to joel. I updated it but I'm not in an area where it happens so I can't test it. Pull down the changes and rebuild and see if that fixes it.

The 4g dropping is a separate issue. It drops from 4g to 1x, then you must go in and change the network type to CDMA/LTE and you'll get 3g.
[HTC Rezound] con247:
Chad, will these run at all on a stock Linux 3.x kernel pulled from the leaked OTAs? Or is a 2.x kernel required because changes need to be made in kernel source?
[HTC Rezound] chad0989:
One could probably use the stock kernel if they wanted to make the changes to the trees for it. I used the 2.6 kernel in case I needed to make modifications to the kernel, but I didn't need to other than what was required to get it to boot in ICS.
[HTC Rezound] con247:
I asked because it would allow camera to be fixed I think.
[HTC Rezound] Vashypooh:
Hoping this to be the last non dev thread here.

Would you be offended if we created another topic to discuss the rom in question, or could you make one meadows to keep people out?
[HTC Rezound] con247:
I think meadows is gonna post a thread dedicated to his builds so stuff can be discussed in there.
[HTC Rezound] Jonman409:
Chad. I believe I fixed the SD card issue. I'm rebuilding right now to test. I will submit a pull-request if it works.
[HTC Rezound] chad0989:
Awesome. Sounds good.:good:
[HTC Rezound] zone23:
Any chance of getting a little help on setting up the device folder structure for compiling the source? Basically what I have now is "cm9/device/htc/vigor" (see attached image) which I placed the "device_htc_vigor" files in from the git. When I run . build/envsetup.sh i see "including device/htc/vigor/vendorsetup.sh" which to me looks good. So then I've been running "brunch vigor -j" (I don't know if thats correct or not) then I get:

including vendor/cm/vendorsetup.sh
build/core/product_config.mk:189: *** _nic.PRODUCTS.[[device/*/vigor/cm.mk]]: "device/htc/msm8660-common/msm8660.mk" does not exist. Stop.
Device vigor not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Repository for vigor not found in the CyanogenMod Github repository list. If this is in error, you may need to manually add it to your local_manifest.xml.
build/core/product_config.mk:189: *** _nic.PRODUCTS.[[device/*/vigor/cm.mk]]: "device/htc/msm8660-common/msm8660.mk" does not exist. Stop.

** Don't have a product spec for: 'cm_vigor'
** Do you have the right repo manifest?

No such item in brunch menu. Try 'breakfast'

Any help on the device structure tree would be great.. Thanks..

edit:

Figures after posting I get it, it was the naming of the msm8660-common folder.. on to the next error...
[HTC Rezound] Jonman409:
I've been successfully building CM9 images and you can see how I have it laid out on my github if it helps: https://github.com/JB1tz
[HTC Rezound] chad0989:
Working on the roaming indicator thing. The ERI file didn't help. I think I might have it though.
[HTC Rezound] zone23:
I think I got the structure now but when I go to build I get

-bash: build/tools/roomservice.py: No such file or directory

so trying to work that out.. ever get that error?
[HTC Rezound] squidder:
He plainly stated he needed a log from an ics sense rom
[HTC Rezound] kingpin003:
D'oh. My fault. Sorry Chad. I'll flash my nandroid back to sense and get one up tonight.

Edit: Pastebin is back up. Dropbox link for good measure(and because I had to delete the first 75 kb to fit under pastebin's file size limit).
[HTC Rezound] MaulingDeOso:
Got a handle on the multitouch issues.

Seems the touch threshold isn't properly being raised when the screen is unlocked.

For instance, you can do

# echo 2 > /sys/android_touch/unlock

to raise the threshold and fix it temporarily until the screen locks again. During this time it once again works like Sense.

I'll have to investigate further to figure out why it's not unlocking, or whether it simply can't automatically with AOSP and necessitate raising the default threshold.
[HTC Rezound] tazman19:
That's a great find...I would imagine that is causing some of the delay issues in swiftkey as well.
[HTC Rezound] GrayBoltWolf:
No. Turn on GPU rendering in dev options.
[HTC Rezound] brando56894:
Even with GPU Rendering enabled and the phone at Max clock speed, I've still had a ton of lag with swift key on both CM9 and Sense based roms.
[HTC Rezound] wildstang83:
I think that would be an app problem then. Their last update might have been a dud or something.
[HTC Rezound] Po1soNNN:
No way swift key is solid for me on both sense 3.6 and 4 so unless it's an aosp related bug...
[HTC Rezound] z0mghii:
Slow for me on AOSP also.
[HTC Rezound] wildstang83:
You know how it is, what works perfect for you may not work at all for the next person, even with the same phone, etc...