yashsingh1/xdaforums huggingface dataset:
[HTC Rezound] chad0989:
Yes. I pulled in and based it on some JB stuff. Makes it easier in the future. HTCVigorQualcommRIL will probably disappear eventually. JB seems to have the right idea where radio stuff is headed by separating SIM states from radio states .
[HTC Rezound] chad0989:
If someone has a lot of spare time to and a fast build machine It would be really great if you could go through the vendor files and figure out which prebuilt libs we can get rid of and build from source instead. I'm sure there's a ton of stuff in there that's not necessary.
[HTC Rezound] dmeadows013:
I'm gonna see if I can get this to build on AOKP... I'll need to merge the frameworks/base stuff first.
[HTC Rezound] dmeadows013:
Repo sync took way too long... Building now...
[HTC Rezound] dmeadows013:
Ok got a libcrypto error... Idk what the problem is... Gonna check with Roman

Edit: Roman says it's a problem with the recovery that koush edited for CM code. Trying to revert it
[HTC Rezound] pwned3:
Or you could use amon ra:rolleyes:
[HTC Rezound] dmeadows013:
No it's causing it to not build lol. I think I fixed it though...
[HTC Rezound] antp121:
So protekks loss of power doesnt affect you at all?

Btw, chad, does this use the gb wifi drivers since we don't have ics source?
[HTC Rezound] wlmeng11:
Yeah he said it uses the old drivers until we get kernel source.

Sent from my Rez with fangs
[HTC Rezound] live2die:
i remember when we were in the age of cm7，most people thought the camera didnt work due to the kernel source，but a guy from China made some tweaks and then the camera worked，can anyone else recall this？maybe we can take that way
[HTC Rezound] dmeadows013:
Still working on AOKP but I tweeted a CM build
[HTC Rezound] antp121:
This does NOT have gapps, correct?
[HTC Rezound] dmeadows013:
Correct. This should be the last post in this thread about it. :P Its a dev thread lol
[HTC Rezound] quepaso:
Ive booted up with CM9 and its so amazing. AMAZING work chad and dmeadows. I get Roaming Indicator On, but according to twitter you guys get that too. Wonder if thats normal?

Edit -

AOKP M6 from DMeadows here: http://t.co/5dyljWG1
[HTC Rezound] chad0989:
The roaming indicator problem should be fixed now thanks to joelz
[HTC Rezound] localceleb:
How long did the 4G dropout take? I have been running aokp for a little while now and using data like a mad man and haven't broke a strong 4G signal yet. No roaming issues either.
[HTC Rezound] Insidious:
Downloading meadows cm9 now.

Edit: didn't mean to post this delete please.
[HTC Rezound] chad0989:
Except that it makes it harder to get logs. Haha. Only when its rock solid stable.
[HTC Rezound] dmeadows013:
Agreed.
[HTC Rezound] dmeadows013:
Chad do you think you'll have the AOSP changes up by tomorrow on git? Kinda hesitant to merge linux changes cause I wanna merge things cleanly
[HTC Rezound] chad0989:
To use the kernel? Probably not. Kind of busy the next couple days.
[HTC Rezound] dmeadows013:
All good. What kind of init work would need to be done? Got the PMEM merged but not sure about init
[HTC Rezound] winged mantis:
Did you try upping the data warning limit? It eliminated the lag for me and a few other people.
[HTC Rezound] GrayBoltWolf:
Chad knows. That is a temporary fix.

Please, Devs only in this section.
[HTC Rezound] chad0989:
Just an update:

New kernel builds and boots. All the hardware that works before still works. I updated the wifi stuff to use NL80211 and the bcmdhd module instead of wext/bcm4330b2, it seems to work quite well. Data monitoring works without any lag and you can set the limit in settings (just drag the slider to where you want the warning). Camera works, still no camcorder. Internal/external storage / usb mass storage both work.

However there is one major bug that I'm still working on. For some reason after the display initializes it won't refresh until it is blanked and unblanked, so it will stick on the white HTC screen for the entire boot (no animation) until it is fully booted and you manually blank and unblank it. Then the homescreen comes up and everything is well.The boot animation still works if a run it manually after boot. Not sure what the cause of the bug is, but it definitely seems to be a kernel issue. I think maybe the display is initializing before something else it requires. I'm working on it though and once its fixed I will push everything up.
[HTC Rezound] chad0989:
Oh, fixes the cm9 tethering too.
[HTC Rezound] chad0989:
If anyone wants to be a huge help it would be greatly appreciated if you could go through and find the best screen brightness levels for each light level. You can use z device test to get all the light levels and then in display options in cm9 you can edit the table to set the brightness levels. Once you have what you feel is best please post it here and I'll see about using them as defaults. Correct brightness settings should help battery life considerably.
[HTC Rezound] dmeadows013:
Did you github the tree?
[HTC Rezound] dyetheskin:
I was actually concerned with this myself and would like to figure them out but just need to know how
[HTC Rezound] Neo:
I'll flash cm9 in the morning and come up with the brightness levels requested. I'll also post them here in hopes that any feedback might show a majority acceptance of the chosen levels.
[HTC Rezound] Po1soNNN:
You could always just ask joelz to borrow the levels used in his rom.
[HTC Rezound] chad0989:
Not yet. Need to fix the display not refreshing when it first initializes issue.
[HTC Rezound] dmeadows013:
Alright. Sounds good. Working on merging Linux stuff to my kernel now
[HTC Rezound] dyetheskin:
so far I only found 11 light levels from the sensor. correct me if I'm wrong. once I find em all I'll figure a smooth transition of the brightness
[HTC Rezound] dyetheskin:
here's what I came up with after using various light level apps and looking around for smooth transitioning while making bright enough for each level. if this isn't the best we can do at least it's a great step in that direction :)

automatic backlight

light sensor filter

enable check

window length is 60s (optional choice)

reset threshold is 800 lux

sample interval is 2s (optional choice)

screen dim level is 20(default)

allow light decrease

decrease hysteresis 50‰

now for the custom levels is in screenshot but notice I didn't set to max of 255 when exposed to most possible light. I noticed no difference between 240 and 255 so I figured it'll be a tiny amount of battery saving
[HTC Rezound] Neo:
Thanks for this. I will not be doing this today then as you've already provided the levels. To those who are on a AOSP rom, please try the these levels listed in the image in the post above mine. Only post a reply if you are adamantly against them.

Thanks
[HTC Rezound] chad0989:
Fixed display init issue, hopefully it doesn't cause any unforseen problems. Building now and if everything goes well I will push everything in a bit.

And how does everyone feel about the brightness levels that dyetheskin posted? I think I may got a hair brighter at each level but I'd like everyone else's opinions so that we can please the majority before I make anything default.
[HTC Rezound] Snuzzo:
Can they be completely turned off in addition to those brightness levels? They get turned completely off here on anything i run so my input is going to be vague. Awesome work on the init issue btw!! I'll start my sync after you do the push. :)
[HTC Rezound] chad0989:
Everything should be up. Good luck have fun.
[HTC Rezound] Snuzzo:
Thank you again. I got a little too excited and started syncing a little too early LOL

-----------------

Cooked it up and everything EVERYTHING works great EXCEPT bluetooth.
[HTC Rezound] chad0989:
Camcorder still doesn't work either. Going to start working on Bluetooth finally though.
[HTC Rezound] Snuzzo:
Oh ok. I just sync'd again and brunching away. I saw your commit this morning and wanted to try it out. Neither are a big deal, if I can tame battery life some I can then start to run this as daily now and help report any bugs I find.
[HTC Rezound] kingpin003:
Hey Chad I agree that the brightness levels are a tad too low especially the highest ones. I would go a little higher and those who like their screens dimmer can customize from there.
[HTC Rezound] a.mcdear:
As long as the screen is at its lowest setting in a dark room. I always have yo take it off auto cause it will never turn the screen all the way down, even in a pitch black room.
[HTC Rezound] antp121:
The brightness levels are fine here. Idk what you guys are talking about...
[HTC Rezound] kingpin003:
I dunno, ant. But I was trying to use my phone earlier with light level 640 and I could see my reflection more than I could see what was on the screen. That to me is too dark.
[HTC Rezound] GrayBoltWolf:
I'm working on and orange theme for CM9 as soon as I can get the repo to sync.
[HTC Rezound] antp121:
Follow my instructions and you'll have a build lmao
[HTC Rezound] dyetheskin:
everyone has their preference. I like mine dark since I'm mostly in low light rooms anyway. the sensor levels are accurate cause I used multiple apps to read them off the sensor. I matched them with the custom brightness values from a cm7 thread for the dinc which had a nice smooth scaling of light. if you find it too dark boost up the values from 640 and below but remember the idea is to have lowest possible brightness to save power. adjusting these values only means you care more about reading then saving battery. adjusting means you like a brightness of 25‰ or more which isn't very handy for saving juice since our screens suck more power than any dinc will. because of this I took lower settings into consideration
[HTC Rezound] antp121:
I keep mine nearly off lmao. I like to save battery and I usually have decent light :p
[HTC Rezound] GrayBoltWolf:
I used your trick and it worked. I wanted to use the most recent build, (not that the UI changed probably at all), but it just makes me feel better. :)

It is running smoothly, been going for about 20 minutes now.
[HTC Rezound] antp121:
Been running for like 12 hrs :P great job Chad.
[HTC Rezound] GrayBoltWolf:
Building usually takes around 2 hours on a dual core pentium clocked at 2.1 GHz?
[HTC Rezound] antp121:
Took me like 4 hrs on single core 2.0 ghz. Also when you repo sync, especially a fresh sync, use repo sync -j4 (or more then 4 if you have a faster internet.) The higher the number, the faster the sync and the more bandwidth.
[HTC Rezound] GrayBoltWolf:
Jx with x being the number of cores you have +1. So I did j3. Next time I should do 4?

I have decent internet, usually around 18 mbps hardwired.
[HTC Rezound] antp121:
Oh you could do like j8 then lmao. I'd advise to not use the internet if you use a high number. It'll be like unusable. I used j4 and my internet lagged like a mofo.but it was done in like 20mins.
[HTC Rezound] MaulingDeOso:
Keep in mind that the build process is very RAM-heavy, and more threads will use more RAM. If the disk is swapping at all, use fewer threads. Don't use more threads than you have cores (or HTT threads). Android's build process is very I/O bound, so it won't help.

And if you don't have a SSD drive or at least 8GB of RAM, the random-access behavior of repo sync with multiple threads will nearly dead-lock a traditional hard drive, in which case you'll be better using just the one thread.
[HTC Rezound] antp121:
I have 2 gb and an hdd. Worked fine.
[HTC Rezound] MaulingDeOso:
Hmm. When I had 4GB a while back the hard drive easily got pegged and it took much longer (because of all the small files). Now with 16GB, I don't have any problems, so I obviously can't test it. They've probably changed the update script since then.

My note about not using extra threads still stands though. Except it should have said not I/O bound. :p
[HTC Rezound] Flyhalf205:
You think you could help me learn to build. I have a fast machine. SSD. 8GB. 4.1ghz i7.

Meant to send a PM. lol My bad!
[HTC Rezound] Neo:
+1

-j1
[HTC Rezound] antp121:
http://xdaforums.com/showpost.php?p=31005599&postcount=43 this is a good base. then read the rest of the thread for fixes and troubleshooting.
[HTC Rezound] GrayBoltWolf:
I followed the guide he just linked below.

I feel like we are destroying Chad's thread with all of this nonsense. People read this thread to get vital info from chad and we are basically spamming it.
[HTC Rezound] renzo.olivares:
you could just build a single apk if u wanted to for theme manager....instead of the whole rom
[HTC Rezound] yojoe600:
exactly that's how the orange theme is online it makes it easy to use them
[HTC Rezound] GrayBoltWolf:
Hopefully it will be easier. I was just going to make a flash able zip.
[HTC Rezound] dmeadows013:
Fixed camcorder :)
[HTC Rezound] antp121:
He sure as hell did, I guess the new kernel did it?

---------- Post added at 11:08 PM ---------- Previous post was at 11:07 PM ----------

Here's my professional test video... http://www.youtube.com/watch?v=CEmNZV3shkQ&feature=youtu.be
[HTC Rezound] Antoine.WG:
Did the new kernel fix Bluetooth too?
[HTC Rezound] wlmeng11:
By that statement, I can logically deduce that HW video acceleration works now?

If so, flash time!
[HTC Rezound] dmeadows013:
No what fixed camera was a change I made to the source kernel code. I may have just fixed bt tho :D. I'll look further tomorrow. Gotta do hw for now.
[HTC Rezound] chad0989:
Lol @ what fixed camcorder. Ridiculous change on HTCs part.
[HTC Rezound] chad0989:
Was already working with the new source from HTC.
[HTC Rezound] Vashypooh:
I ported HTCVigorQualcommRIL to MIUI V4 through smali,

It has working 4g data and everything but for some reason carrier text is returning as {0}:Not Forwarded, and when you use #*#*4636*#*# if you go into phone properties, you will lose 4g as it is not an option in there.

I am trying to learn this stuff, so is there any way to adjust or figure it out?
[HTC Rezound] chad0989:
There were other changes to telephony that are required for the til to work properly. May need to try to bring those over also. Or the whole telephony jar.
[HTC Rezound] Snuzzo:
@dmeadows

Just following up reg. the comment on bluetooth (not asking for eta). Haven't had a chance to go in there and dwelve into my attempt at getting it to work yet haven't really had time, just was wondering if you have been able to so I don't waste my time, with double work you know? Picking up what i'm throwing down? :)

@chad

It has been a very interesting looking through all the source, quite a bit of it has changed but there are still some small similarities. Still not quite there yet to where I was with Froyo. Yeah it's been a while, like i am relearning all this stuff .... =/

Right now, I'm just playing around with the source. Starting to theme a little.
[HTC Rezound] Neo:
Pulled D's kernel repo and all of Chad's and compiled CM9 last night. Pleasantly surprised that front facing camera was working... I must've missed that bit. However, although I'm unsure if it was capable before or not, I wanted to know about the Governor changing ability. It stays locked on Interactive despite the numerous options available. Was this something that was working before? I feel like it was for some reason.
[HTC Rezound] chad0989:
Its most likely the mpdecision daemon resetting the governor when the phone sleeps and wakes. I plan to ditch it and implement the kernel version someone wrote. I just have to do some thorough testing first.
[HTC Rezound] a.mcdear:
If I were to disable mpdecision in the meantime, that would essentially limit me to only one core, right?
[HTC Rezound] chad0989:
No. Both cores would be on at all times.
[HTC Rezound] Vashypooh:
I'd need to know more of what changed in what files I guess MIUI has its own changes to those files that would prevent a straight port of the whole thing.

I think they can just deal with it IMO, 3g,4g,call,sms,mms all appear to be working, so that's good enough I suppose.

Thanks.
[HTC Rezound] chad0989:
Fixed the pmem stuff and possibly any residual blue flickers. Plus I should be able to get rid of the rebuilt init.rc now, which should help with getting JB going.

The downside is that it requires me to steal another 16-48mb of ram away from what can be used for apps, just need to determine how little I can get away with. Shouldn't have any noticeable negative effect though.

Testing today and if all goes well I'll push it tonight.

Still no luck on bt.
[HTC Rezound] Snuzzo:
Send me a pm as to what was tried so far. I'm playing around with it myself.
[HTC Rezound] chad0989:
The changes I've tried are commited. I also tried a few different firmwares as well.

Most other msm8x60 devices use the same wifi/bt chip so it should work if we replicate what others have done. Its probably something small I'm missing.
[HTC Rezound] Snuzzo:
I'm looking at the Sensation's vendor files currently. I think it uses the same chipsets which it calls upon bcm4329.hcd for both wifi and bluetooth in msm8660 common.

https://github.com/CyanogenMod/andr...mmit/dddc55a8ab9a26d56287dfe7bf7305a06285f073

I haven't made any changes to any of the .mk's yet to reflect a change. Wanted to throw that to you see what you think.

EDIT:

Yup, 99% sure that's where it lies.
[HTC Rezound] keolawills:
-delete please-
[HTC Rezound] chad0989:
I already tried it. However we use the newer bcm4330 chipset and are now using the bcmdhd module which complicates things slightly. Other devices use the identical chip though (e.g. HTC vivid) and they have working BT.
[HTC Rezound] Snuzzo:
Hmmm also noticed some firmware isn't in system/etc but rather vendor/firmware.
[HTC Rezound] a.mcdear:
hmm, speaking of the wifi module, bcmdhd isn't compatible with iwconfig for controlling wifi tx power is it? So far I haven't been able to get it working on my Rezound since ICS with the bcmdhd module, whether using HTC's ICS or the recent AOSP builds.
[HTC Rezound] chad0989:
No its not. We're using nl80211 now instead of wext. Wext and iwconfig are obsolete. You would need to use iw instead but I'm not sure if someone has built an android binary.
[HTC Rezound] a.mcdear:
Awesome, thanks for help.

Found this on how to build a iw binary for Android. Figured I'd share in case anybody else is looking for putting this into a ROM or something.

http://webcache.googleusercontent.com/search?q=cache:http://www.onlyxool.net/porting-iw-tools-to-android/
[HTC Rezound] dmeadows013:
Chad working on getting JB AOKP building and got this error. Any idea what could be causing it? http://pastebin.com/GGQmmvNG
[HTC Rezound] antp121:
whose trees and vendors are you using?
[HTC Rezound] dmeadows013:
Mine

Via my Google Galaxy Nexus with Butter
[HTC Rezound] antp121:
ok. i had the same issue with... jonmans i think?
[HTC Rezound] dmeadows013:
Did you fix it?
[HTC Rezound] antp121:
nope lol i didnt look into it at all.
[HTC Rezound] Snuzzo:
--Delete--

Still working on it.
[HTC Rezound] MaulingDeOso:
Might want to update the Adreno drivers in the vendor tree. I'm using the 2184622 version pulled from the global leak, and it runs slightly better than the current set. It still seems to be falling back to software on a few operations, though.

There are new Jellybean-compatible drivers posted on Qualcomm's dev site, but I haven't tried those, as I'm not sure if they're a strict superset of the ICS drivers, and the API might be lacking.
[HTC Rezound] chad0989:
The drivers in the tree are the latest from the qcom site. I'll look into it though. I haven't tried the jb ones with ics yet though either as I was thinking the same thing. If you do try them let me know.

On another note I have a couple ideas for bt that I'm going to try later if I get a chance. That and now enough stuff works that the signal indicator being off is starting to bug me. Haha.
[HTC Rezound] dmeadows013:
I don't have the source in front of me but try removing the BOARD_HAVE_BLUETOOTH_BCM := true line in BoardConfigCommon.mk in msm8660-common. I don't think we have broadcom bluetooth

EDIT: If that doesn't work I think I found another thing that could :) hold on lemme check
[HTC Rezound] MaulingDeOso:
The Qualcomm site's ICS libraries are outdated. Both the latest Rezound global leak and the Galaxy S3 have these new 2184622 drivers, and they actually do seem to help with speed when used with AOSP frameworks as opposed to Sense.

Tried the Jelly Bean libraries, and they're no go on ICS. The EGL libraries hook into the compositor libraries, and the compositor libraries seem to rely on code from a new SurfaceFlinger.
[HTC Rezound] chad0989:
We have broadcomm Bluetooth.

http://developer.verizon.com/content/vdc/en/verizon-devices/pages/htc_rezound.html
[HTC Rezound] chad0989:
Okay cool. Thanks for letting me know. I update them.
[HTC Rezound] dmeadows013:
K. Did you ever fix the PMEM issue? I think that's why wifi wont turn on or scan. Just spazzes on and off on AOKP. Seems fine on CM
[HTC Rezound] Neo:
That's exactly what I was getting on my build from last night btw
[HTC Rezound] Snuzzo:
WiFi works fine ...... ??
[HTC Rezound] dmeadows013:
Not with aokp :(

Via my Google Galaxy Nexus with Butter
[HTC Rezound] chad0989:
Is your firmware right?
[HTC Rezound] dmeadows013:
Yea and it's not just me. Neo gets it too. At first I thought it was a problem with the wifi defines but no. Also ffc is just main camera upside down lol

Via my Google Galaxy Nexus with Butter
[HTC Rezound] Neo:
I deleted my aokp and repo folder. Starting fresh lol. When pulling the camera apk over everything works as it should (for ffc, camcorder etc). Only thing is wifi. I'm playing around with the repos tonight to see if I can find the right combination
[HTC Rezound] Snuzzo:
@meadows

Tried pushing your modules to system/etc/firmware instead of vendor/firmware?
[HTC Rezound] dmeadows013:
Will in a bit. Calibrating battery now :p

Via my Google Galaxy Nexus with Butter
[HTC Rezound] RoryHe:
I thought i read somewhere from a google engineer that as long as you charge your battery to 100% that it calibrates itself or something.

Edit: her name is Dianne Hackborn
[HTC Rezound] GrayBoltWolf:
Charge to 100% and then run all the way down to 0% in one sitting (no short charges in between) will calibrate the battery.
[HTC Rezound] TheBr0ken:
Think she's the one that debunked the theory that clearing battery stats has anything to do with battery life, probably different than what Devin is trying to do.
[HTC Rezound] Neo:
Here's something new... After initializing and running the wifi tether app once and then ending use, wifi will turn on and off without glitching every time as if the problem never existed.... Explain that one?
[HTC Rezound] RoryHe:
It's a sign that using wifi tether is just right.
[HTC Rezound] Vashypooh:
That is damaging to a lion battery and should not be done.
[HTC Rezound] Neo:
http://batteryuniversity.com/learn/article/do_and_dont_battery_table
[HTC Rezound] chad0989:
Lets stay on topic.

On a better note. I got BT to turn on. I'd say that's progress. Now to just get it to function.
[HTC Rezound] Snuzzo:
Nice! I got mine ot turn on but once connected to a device, hot reboot.
[HTC Rezound] chad0989:
Got it. Need to do some more testing then I will push later, along with the pmem stuff. Sorry about the delay on that.

Next up: Fix torch properties (should be easy) and fix the signal bars and we'll be pretty much at 100%.... Then its peanut butter jellybean time.
[HTC Rezound] Snuzzo:
Darn straight it is. I need to learn how to do Theme Manager themes now. I think I might try working on porting over my 4 themes. Wonder how they would look.
[HTC Rezound] Marine6680:
When this is running 100% and we get full functioning AOSP/CM ICS, it will be great... JB will be awesome. How hard is it going to be to get the JB kernel working 100% compared to the ICS kernel?

(to address the off topic battery talk and give clairification)

Full discharge of a Li Ion battery is 3v... Smart phones shut down when the battery reaches 3.45-3.5v... the battery at 3.5v still has around 20-25% of its total maximum charge capacity... this is a safe discharge level to prevent premature wear on the battery.

25%-85% is the ideal range for Li Ion... they don't like to be at 100% charge for long periods. Luckily, unlike laptops, cell phones tend to not stay plugged in for very long periods of time.