yashsingh1/xdaforums huggingface dataset:
[EVO 4G Android Development] Lokifish Marz:
If this is directed at me, I'll gladly remove my links and data from the thread and not return if me being here is an issue but only per the devs request.
[EVO 4G Android Development] ViViDboarder:
I don't think it's you... He posted that trolling post a few pages back.
[EVO 4G Android Development] g12345:
Very excited to get this, went and flashed the kernel and it works as expected except I lost access to about 2/3rds of my apps on the phone, including maps and the market. When I click on my old shortcuts it says the linked program is no longer installed on your phone. Am running the latest Sprint lovers ROM so pretty much stock rooted. Any ideas? Recovering NAND backup now but I would really like to get this working!

Thanks for any help.
[EVO 4G Android Development] unknown1205:
how do i pair up my wiimote with my phone?
[EVO 4G Android Development] AmazingLarry:
You must be using CM7, Sense uses a crippled Bluetooth stack.

Get WiimoteController (free) on the market, it's pretty self explanitory. You set this as your active keyboard and then you can set Nesoid or whatever to use special controllers.
[EVO 4G Android Development] dkelle4:
download the wiimote controller app from the market
[EVO 4G Android Development] CruzECO13:
Wiimote controller
[EVO 4G Android Development] dkelle4:
10 chars...
[EVO 4G Android Development] dirkyd3rk:
Everyone's getting wiimotes I feel left out I guess ill get 1 also. At least they don't cost 50 bucks like stupid Xbox/PS3 controllers.
[EVO 4G Android Development] anthony92170:
just installed my phone is showing on my tv with the banner only nothing else is working i am using mikz hd rom any ideas as to why this wont go past banner?
[EVO 4G Android Development] Shinzul:
People seem to be having issues with the sense version... argh!

Let me go double check that everything is right...
[EVO 4G Android Development] Rem3Dy:
LOL why is Loifish Mars even in this thread. He us the biggest fullhdmi troll on these forums
[EVO 4G Android Development] KERKEDAGAIN:
+10 for the selected statements..not to mention that the wives n families may have a bit more say behind the decision to 'charge' for the app. Some guys can get away with not charging, others may be asked to 'show something for their time n energy'.
[EVO 4G Android Development] ViViDboarder:
He's not trolling in this thread.
[EVO 4G Android Development] Shinzul:
So I just found that I accidentally uploaded the wrong kernel (older build) and I think that is what was causing most everyone's issues...

The download links should be the same, but I updated the md5's in the OP.

I need to get more sleep apparently! :o:o:o
[EVO 4G Android Development] g12345:
Got it fixed by wiping cache and dalvik, programs slowly started reappearing was very strange but it is working now, can't wait to try it out when I get home.
[EVO 4G Android Development] Apo11on:
Actually, I read every single post in this thread, including your previous post you quoted. That doesnt mean I understand or accept it. (Same goes for your twitter flame about orrebmas, which toastcfh retwitted for unknown reasons). My comment about teamwin's kernel was meant to emphasize the fact this kernel is significant step backwards in android development for Evo and many people will chose not to use it because of the issues I mentioned. This community is based off combined brain storming efforts and there is nothing wring if hard work of others has paved the way to further improvement. Teamwin's reasons to take 3 steps backwards in Evo kernel development, just to make 1 step forward in different direction, are beyond my understanding. Surely you must realize kernel's like netarchy's are far superior to stock, and you dont seem to mind basing your work off the work of others because you used the root for Evo, toastcfh initially accomplished. You dont see Google creating push mail notifications as part of Cupcake -> Eclair changes and then saying "hey, you know what? we're gonna add wireless apps installations now and we're gonna add it to Cupcake, so you could chose which features you want to keep!" because giving up previously made progress and making people chose makes no sense. So, what is it that is preventing teamwin from taking a kernel, far superior to stock and adding HDMI modules on top if it?

About "dark alleyway kernel dealers" - you should not assume kernel developers would be available or interested to add HDMI support, because that may not be the case. Some, like netarchy, according to rumors may have stopped developing, some may simply not be interested... That leaves thousands of users who are used to fast speeds, great battery life and plenty of other goodies with a choice of old, outdated kernel but with HDMI modules, or keep the advanced software and live without HDMI... Perhaps teamwin should re-examine its "goals". Many pages ago in this thread, where agrabren went off for a long rant about GPL (he made good points, no beef there) one of the things that were mentioned is that teamwin wants credit and community wide recognition for their work on HDMI support - it seems to me the choice of basing this work of an old slow kernel software and therefore significantly reducing number of users who would opt out to make such sacrifice in favor of only gaining HDMI support is a direct contradiction to that goal, basically shooting yourself in the foot.....Just my 2 cents
[EVO 4G Android Development] ViViDboarder:
The project goal has always been to write HDMI open source drivers. Not release a bunch of kernels.

When this is merged with CM Source there will be no kernels at all. If you want to chose, then chose. Doesn't bother us. You can use your faster kernel, or use the latest CM kernel with HDMI. Why should we be more responsible to pull some other developer's kernel mods into our kernel than them pulling ours into theirs?

Again, the goal here is not to give people a flashable HDMI kernel... It's to make public source available to kernel devs and CyanogenMod.

Make sense?
[EVO 4G Android Development] dkelle4:
Old and slow? We based it off the latest HTC #15 kernel as well as continually rebase it off the latest AOSP kernel source.

Plenty of us just use the stock kernel. It isn't up to us to implement and support every kernel under the sun just because you want it.

And I'm sorry netarchy isn't devving for the EVO anymore.
[EVO 4G Android Development] kevank:
Ok. We get it. You consider the development of new functionality 3 steps backward in Evo development. I consider this point of view to be a bit close minded.

To me this is simple, when you develop new functionality you start with a simple non-tweaked kernel base. Eg. The CM7 kernel. You implement and debug all of your new functionality without having to worry that the tweaks (eg. overclocking / undervolting) are causing you issues. Once it works and works well (as it does) you release that code to the community under the GPL and let the kernel developers add the new functionality to their work.

When you develop your own kernel / new feature, you can do as you like. If you don't like the way TeamWin is doing it, don't use our kernel and wait until your favorite dev ports our work into their kernel.
[EVO 4G Android Development] Apo11on:
No, it does not. First of all, if you looked at my signature you would know I'm using SENSE rom, so none of your CM arguments apply. I prefer Sense to AOSP, so because cyanogen states on his website his roms will never have Sense - I'm telling you my Evo will never be running cyanogen.

And I would think the answer to your question "Why should we be more responsible to pull some other developer's kernel mods into our kernel than them pulling ours into theirs?" would be fairly obvious, but since apparently it's not I'll re-iterate: because these kernels were created way BEFORE yours and have a large base of users, who are accustomed to the performance they provide and you want these users to use you HDMwIn product. There is no telling when/if other kernel devs will make those HDMI modules imports, so if you want people to use HDMwIn *NOW* and not when/if that happens - you should consider doing the sensible thing. I refer you again back to my Google example and here is another one for ya: when ms79723 created his Superior Battery Charging/trickle charging kernels he didnt use stock - he based his work of the most recent, most advanced netarchy's kernels out there because those kernels have been around for a long time and it makes no sense to make people chose to give up all those features.

Development should be incremental, not alternative...otherwise it's not a progress, but a substitution
[EVO 4G Android Development] ViViDboarder:
Ok. Then I don't care. :p
[EVO 4G Android Development] BigRick10:
Tried this last night and was expecting a much clearer picture. I mean some of the videos I see on YouTube smoke what mine outputs. I have it set to 720p and that's what my tv is reading. I'm using the HTC HDMI dock.
[EVO 4G Android Development] :
You are more than welcome to offer me some direct compensation to port the kernel changes to any kernel you'd like. I'm more than happy to be a gun for hire, and as the guy who made the mirroring portion of the kernel code, and all the changes for PoonSense, I'm the best guy for the job. But for now, I'm not getting paid for my contributions, and I run CM7, not sense. Sense gets it's changes from the CM7 work and discoveries, and so it doesn't get the love that it deserves because there's nobody interested in loving on it.

I'm doing this because I love making things work. For everyone who wants to think we're all cocky annoying "rulers of the platform", we're not. I'm a husband, father, friend, and employee. In my little offtime, I've used my knowledge of GPUs and display driver models to create a method to mirror HDMI with nearly no CPU impact for the device. I personally would love to see Sam come clean with his kernel source code. Not because I want or need to steal it, I think we've proved that we know how to do it. I'm pretty sure I know what he's done, too. I'm sure some of the changes are shared between us.

Heck, I'm even willing to extend on olive branch to work with him on a unified kernel so his app and daemon work on the same kernels as ours. But so far, he's just been violating GPL to turn a profit and has made no effort to return to proper legal standing.

I'm sure you all love to complain and moan about what we're not doing for you for free, but how much have you given back for everything both teams have done?
[EVO 4G Android Development] aimbdd:
yep... the savaged zen team said they are looking to add support as we speak! :D

Edit: http://review.savaged-zen.org/#change,882
[EVO 4G Android Development] :
Actually, while he may be a fanboy of FullHDMI, he's actually providing very useful information. From the details he's provided, I've got a very strong idea of how FullHDMI does it's mirroring and how his "accelerated kernel" work, as well as his daemon. When you specialize in graphics for a living, you'd be amazed what details you can determine from what appears to be very simple data. It doesn't mean I have any intent or desire to mimick his work, it's just an interesting data point, and if people care what the benchmark reports back, can easily be enabled in our kernel. It's very similar to how our Alpha 2 worked, which we re-wrote for Beta to get the 100% frame-accuracy with no tearing on all scaling modes.
[EVO 4G Android Development] Lokifish Marz:
HW 003

CM7 nightly 18

Kernel from OP

HDMwIn 1.02

Still getting FC's when trying to access options to change resolution. Will continue to mirror after app FC's. Now I can't get anything but 720P to work. Flashed a beta backup and am unable to duplicate on betav1. Am I the only one that's getting these FC's? If so, I could just be my phone being picky, not like that hasn't happen before with our Evo's.

I'll check back later for progress

I personally don't care who wins in the end , just as long as the end result suits my needs/wants. Something in between the two would be great. That's why I make my findings pubic so everyone can have a go.
[EVO 4G Android Development] :
Damn, that was fast! I was about to offer some help to them, looks like they've got it well under control! But I'll keep with them to make sure they get all the good fixes. :D
[EVO 4G Android Development] :
You just gave me an idea. Now if only I wasn't in the doghouse at home for all the time I've spent on the kernel lately, I'd be able to implement it. :( But we may be able to give you better frame rates without losing our 100% frame accuracy.

I'm having to juggle a couple of key issues at once. Here's what is outstanding for me:

1. AOSP needs HDMI audio

2. HTC's EDID code is buggy, causes kernel crashes for some people (even with sense)

3. hdmi daemon needs auto-rotation support

4. Performance tweaking and improvements
[EVO 4G Android Development] Shinzul:
Hmm, the force closures you're getting are odd... can you uninstall the app, download the kernel from the OP (check the md5 to make sure you have the latest), flash the kernel, clear your caches, boot, then install the market app and test it again?

If you still get force closes, then something must be going wrong, because I have never seen those issues before...
[EVO 4G Android Development] Apo11on:
please consider opening a poll in this thread or elsewhere, to see how many people would be interested in you porting HDMI modules to the latest netarchy's kernels, such as the one listed in my signature...I think it will open your eyes on how popular they are, how many people want it and how much better they are than stock. I guarantee you would get donations and I will be among those who contribute too, to make your time worthwhile.
[EVO 4G Android Development] :
Savage-Zen is getting it. Honestly, it's easy work. I just don't know enough about Netarchy's tree to know which kernel source to pull and add the changes to. And I won't test an SBC kernel on my device, as I know too much about li-ion batteries and charging circuits to go anywhere near it with my only phone.
[EVO 4G Android Development] SolsticeZero:
When you say "Savage-Zen is getting it", you wouldn't happen to have an ETA, would you? :D
[EVO 4G Android Development] :
It's all the drama that makes most of us who make these things for free want to give up and just keep it for themselves. It already does everything I need . . .
[EVO 4G Android Development] :
I don't know their tree, but they merged already.

Oh, and FYI: The app auto-detects a supported accelerated kernel, so if/when they build that branch and share it, it'll "just work". :)
[EVO 4G Android Development] TImmyTheThumbs:
That worked, thanks a ton!
[EVO 4G Android Development] dkelle4:
I'm on 2.6.37.3

You're on 2.6.32

I've got you beat both functionality and time-wise :)
[EVO 4G Android Development] :
Wow, everyone needs to relax... I'm actually looking at making a netarchy kernel build, but I'm sure he won't like it cause it won't have SBC... The changes are very easy to the sense kernel.
[EVO 4G Android Development] CruzECO13:
Tried this step by step. Result: Still force closes when trying to get into display options inside the app. Mirroring is fine. Just cant access the options to disable/enable banner, etc...
[EVO 4G Android Development] :
You want to have TeamWin's babies? Um... Shift, this is all yours. :p

#blameshift

:D
[EVO 4G Android Development] Lokifish Marz:
How feasible would it be to reallocate the memory structure and find that sweet spot between primary and secondary displays? I'm in the doghouse too. I spent 14hrs Saturday beating the hell out of both apps to see where they break. (the stooopid user test)

MD5 checks out. Fresh install cm7 #18, flash kernel, wipe, install gapps, install app and 3dbench, plug in cable, start app , start mirroring, verify mirroring, stop mirroring, settings, change resolution, start mirroring *no change in res*, settings *app FC*, *mirroring still active*.
[EVO 4G Android Development] Shinzul:
Can you post a logcat of you doing that please? I need to see what the underlying exception is.
[EVO 4G Android Development] :
The request for cleanup is because some people are actually here to try to get things working and to help. You're here to troll like a child. Glad to see people like you make my time completely not worth it. Go buy the paid app, I won't cry over it at all. But you've helped me decide that my night would be much better spent with my family watching a movie than working on an unpaid project for people like you.
[EVO 4G Android Development] Shinzul:
In reply to your first question - in the next app release, there will be a button to enable/disable vSync - this will allow for very slight screen tearing (or none at all), but will increase your FPS dramatically.

And from the second - could you post a logcat of the force close please?
[EVO 4G Android Development] :
Who do you think made all the changes and builds PoonKang/PoonSense? Try something, check the build info for the TeamHDMwIn kernels and let me know what user it is. Now that you're the big man on campus, better get back to work on it, dude. People are expecting more fixes, and you're apparently the guy who will deliver the goods.
[EVO 4G Android Development] CruzECO13:
Here is a log of about 5-6 force closes. Let me know if you need more data.
[EVO 4G Android Development] Lokifish Marz:
Here you go.
[EVO 4G Android Development] DomSim:
savage-zen on the servers with HDMwIn included!

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

http://mirror.munkibizness.com/
[EVO 4G Android Development] BigRick10:
I noticed that my banners are going over the end of the screen. I have messed with every setting and they don't move. I noticed that the videos on YouTube have them a little inside the screen. Seems like my display is way too stretched. Here is where the banners are.
[EVO 4G Android Development] :
The banners don't adjust for overscan, only the mirroring does.
[EVO 4G Android Development] BigRick10:
So then my banners are normal??
[EVO 4G Android Development] :
Well guys, can't say that developing the stuff wasn't fun, but releasing it totally wasn't worth my time or aggravation. So thanks all, best of luck with whatever HDMI product you find works for you.
[EVO 4G Android Development] Dees_Troy:
If you are getting force closes with HDMwIn when trying to get into the Display Options, then clear the data for the app. Go into Settings > Applications > Manage Applications > HDMwIn

If possible, click on Force stop to stop the app if it is still running. Then click on Clear data. Force close should go away.

I'm sure that this issue will be fixed in a future release, but in the meantime, use this as a workaround.
[EVO 4G Android Development] Apo11on:
"superior battery charging" is just a general name ms79723 came up with for his collection of many battery tweaks he introduced into SBC kernels. What most people like myself are really interested in is the trickle charging. It's been said extended batteries don't get charged to the full capacity because Evo's stock battery is only 1500mAh and kernel doesn't know about higher cell counts, so it stops charging at 1500mAh. I'm not li-ion battery circuit expert, but Sprint's 2400mAh battery makes me think that is not the real reason... Either way, with trickle charging I get like half an hour of heavy usage before the battery even starts sliding down from 100% charge, which is phenomenal. With trickle charging after like 5 hours of moderate usage my battery is often still above 90%.

I'm a slingbox user, and having Evo run @ 1267mhz to avoid playback jerkiness + high screen brightness + streaming tv in high definition + using WiMaX radio for it is not a good combo for the battery...

I'm assuming what you don't like about SBC is the remote possibility of battery blowing up, so my question is - would it be possible to leave at least the trickle charging in the netarchy kernel with HDMI modules you're going to make? Thanks
[EVO 4G Android Development] CruzECO13:
+1 this is the only way i have been able to get into display options. It's a workaround for now, yeah!
[EVO 4G Android Development] ViViDboarder:
Haha, no. I wasn't referring to you. Don't worry. :)
[EVO 4G Android Development] deviouskater:
Thanks for your hard work Agrabren. You,teamwin and CyanogenMod have brought newlife to EVO once again. AOSP is my preferred rom choice.

I hope the devs continue working on the Evo. Everybody so angry and upset. I appreciate all devs work. I have no knowledge to even start developing and I am happy there are people willing to give up their time to better the community and bring people together with common interest.
[EVO 4G Android Development] fmedina2:
Is there any way to get rid of those white lines on the side of the screen when in landscape mode?
[EVO 4G Android Development] BigRick10:
Yeah remove banners.
[EVO 4G Android Development] ViViDboarder:
Here is a simple tip for XDA Members...

Post comments, post suggestions, post bug reports. Devs appreciate the input to make development decisions.

If you simply don't like someone or don't like their policies, grow up and don't post anything!

If you ask a dev for something and they chose not to implement it, don't get all butt-hurt. Just suck it up and either deal with it or learn to do it yourself. It'd be a great opportunity to learn! The source is all out there! And I'm not saying that to be snarky. Programming is tough, but honestly if you're only making small changes, try making some hacks and see what you can do.

The more people developing the better for the comunity.
[EVO 4G Android Development] :
Does anyone have the apk? I downloaded from the market, had to reinstall the app and now I continually get a message that says, "download unsuccessful." I've attempted to download from the market on my phone and the online market, both fail to download.

Frustrating...
[EVO 4G Android Development] Vandelay007:
I try to download it from the market and it starts to download then immediately says installation failure....no problems w the beta version
[EVO 4G Android Development] :
Thank you very much!
[EVO 4G Android Development] :
Come on guys, back on topic.

I tried two different cables, (one from Amazon, and another purchased from Monoprice.) I keep getting the message, "cable undetected."

Could this be a compatibility issue with my TV? I have an LG plasma.
[EVO 4G Android Development] sling:
Only way to get rid of the trolls is to buy them pizza :)
[EVO 4G Android Development] spiicytuna:
and I know just the guy still delivering :p:D
[EVO 4G Android Development] CruzECO13:
I get that sometimes and a quick reboot does the trick.

Sent using Tapatalk
[EVO 4G Android Development] Shinzul:
It's possible that it could be a tv compatibility issue.

I would download the kernel package that is in the OP and re-flash, clear your caches, and reboot just to make sure that it's not a problem from the original kernel.
[EVO 4G Android Development] spiicytuna:
Also try different positions with your cable... on mine I have to hold it to the left for it to work. I am considering a warranty replacement if I cannot find a solution to have the cable just "work" when plugged in.
[EVO 4G Android Development] tom1l21:
Teamwin, I would like to thank you for all your hard work, based on the 1% rule, these haters do not represent the majority, so don't let them discourage you. Keep it up guys!
[EVO 4G Android Development] tomh1979:
FYI: savage zen kernel was fail for me, back to CM7 kernel.

swyped from my gingerbread'd Evo 4G
[EVO 4G Android Development] Shinzul:
I just want to re-iterate this ^
[EVO 4G Android Development] IMiLL102911:
Is this still going to be branched into cm7 as a rom feature instead of the app?
[EVO 4G Android Development] aimbdd:
well thats helpful for people deciding what kernel :rolleyes:
[EVO 4G Android Development] BigRick10:
CM7 is currently feature frozen from what I heard. So it wont make it in till after CM7 final.