Does anyone here know which part of the framework also controls TV-OUT? Its not just the apk.
There's also a libtvout.so file as well as mentions of it in a few of the makefiles and sources in the incredible specific folders. Grab the 2.1 source and grep it to point you in the right direction.
What are you trying to do? I have plans of digging into it a bit more in a couple of weeks...
Sent from my Incredible using XDA App
tdiman said:
There's also a libtvout.so file as well as mentions of it in a few of the makefiles and sources in the incredible specific folders. Grab the 2.1 source and grep it to point you in the right direction.
What are you trying to do? I have plans of digging into it a bit more in a couple of weeks...
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
I'm guessing he is trying to add tvout functionality to a rom that doesn't have it.
Sent from my ADR6300 using XDA App
Wrong jd.
I have an Evo Froyo port, but TV-Out doesn't work correctly. It has to do with the Framework, because I didn't change any of the drivers or libraries for tv out.
Its one of the last bugs I need to clear up...
adrynalyne said:
Wrong jd.
I have an Evo Froyo port, but TV-Out doesn't work correctly. It has to do with the Framework, because I didn't change any of the drivers or libraries for tv out.
Its one of the last bugs I need to clear up...
Click to expand...
Click to collapse
Oh.
Btw the evo froyo port is great. I used it for a while and really liked it.
Sorry I can't help you.
Sent from my ADR6300 using XDA App
It's in services.jar. you will see the extra code. com/android/server/TVCableObserver.java
adrynalyne said:
Does anyone here know which part of the framework also controls TV-OUT? Its not just the apk.
Click to expand...
Click to collapse
Turns out that there are kernel drivers necessary - there's a framebuffer TVOut driver as well as a USB projector gadget driver. These are built into the CM6 kernel (the one packaged in the nightly builds, not the cm-kernel tree) and obviously the latest RUU from HTC.
Not only that, at least under CM6, there's both fb0 and fb1 display devices present (/dev/display/). I'm assuming the fb1 display is for TV Out.
This leads me to believe that it is most definitely a non-kernel matter, which should help focus efforts (unless you have a vanilla AOSP kernel, in which case it will require kernel driver porting).
logcat/the kernel still doesn't recognize the USB device when I plug in the cable, and I'm not sure what to do at this point.
Related
Hello,
Can someone whom is on a default, unmodified htc brand 2.2 kernel please post, link or email to me /proc/config.gz?
Thanks.
The file doesn't exist.
Sure it does. What does the OP need it for? Its the same as the defconfig in the source code.
Most likely for the PSGroove port. Already working for Desire!
Farenhe1t said:
The file doesn't exist.
Click to expand...
Click to collapse
it 100% exists...i know, i dabbled with making kernels......
and OP, I am going to be working with that file tonight, so ill post it
Sent from my Incredible using XDA App
Here ya go. My current config is not default, but this is identical to stock.
Thanks all! And to answer your question(s), I'm doing a learning exercise trying to trace back TVOut functionality to specific drivers in the kernel. Its a huge shot in the dark, but its a useful task to learn a bit about android, packages, activities, etc. etc. etc.
Good luck. It also depends on framework
adrynalyne said:
Good luck. It also depends on framework
Click to expand...
Click to collapse
tvout is in services.jar as well
Sent from my Incredible using XDA App
adrynalyne said:
Good luck. It also depends on framework
Click to expand...
Click to collapse
So far I ripped out the TVOut stuff from services.jar and got it into the CM6.0.2 services.jar, copied libTVout.so into the the right place, and got the TVOut.apk over, and... it boots! but nothing else. logcat shows an error when I plug in the cable as unrecognized headphones.
Lots to be done to diagnose from here. That was the easiest / longshot solution.
tdiman said:
So far I ripped out the TVOut stuff from services.jar and got it into the CM6.0.2 services.jar, copied libTVout.so into the the right place, and got the TVOut.apk over, and... it boots! but nothing else. logcat shows an error when I plug in the cable as unrecognized headphones.
Lots to be done to diagnose from here. That was the easiest / longshot solution.
Click to expand...
Click to collapse
PM incoming.
My apologies to those who were waiting for me to post a super-clean build. I've been doing absolutely nothing with the Continuum for the last 2+ weeks.
I've finally come across the solution to one of the fixes I've been really wanting for this phone, and one of the primary reasons that come September 20th, I'm ordering a new phone with my wife's free new-every-2.
I want to see USB debugging enabled by default, without timing out. To do so, the default.prop file needs to be edited, which is located in the boot image. I've taken a look at posts like http://forum.xda-developers.com/showthread.php?t=443994, but I don't know where to start. If anyone could point me in the right direction, it would be a great addition to custom roms.
What all do you want the kernel to do/have?
imnuts said:
What all do you want the kernel to do/have?
Click to expand...
Click to collapse
maybe compatibility with CM builds.. gingerbread support maybe or some porting of already completed fascinate builds.
Is it feasible/conceivable to build a kernel with BLN mod in it?
That's about the only thing I miss from the Fascinate world.
Sent from my SCH-I400 using XDA App
we have tried before on eclair to get it working, but with no success... The fact that our soft keys are built into the screen makes it probably impossible...... Sorry for the bad news :l
Sent from my SCH-I400 using xda premium
Yeah, that makes sense. I hadn't thought about the soft keys being part of one display. Oh well, that makes the 5th or 6th app I've purchased that I'll never use again.
Sent from my SCH-I400 using XDA App
imnuts said:
What all do you want the kernel to do/have?
Click to expand...
Click to collapse
I want to have adb enabled by default, and have the persist flag enabled as well. I get so damn annoyed when usb debugging disables itself. I want to usb tether my phone for internet access when I'm traveling, but the phones default settings make this impossible
EDIT: I just realized that Josh's EC07 ROM includes the necessary edits to the defaults.prop file. From what I had read elsewhere, the file was located in a boot image that required extraction and editing, and repacking. So as far as this thread is concerned, my problem is solved, or at least it appears to be.
EDIT: Damn I hate Samsung! Just another 10 days and I can order my DInc2 for free from Wirefly. I just tested whether or not USB debugging would auto-disable after a few minutes. Sure enough, after being tethered for about 5 minutes with EasyTether, USB debugging turns off. Problem NOT solved.
Credits goes to st.matt, he gets full credit for the programming. He seemed a little busy, so I thought I'd spread the news so you guys can implement into your builds.
st.matt said:
Also just a run-down of how it works for anyone that is interested:
I use three different elements to get it working. Firstly, I use a small addition to surfaceflinger to set a system property (sys.orientation.landscape) to 1 when it is in landscape mode (either 90 or 270 degrees rotation) and 0 when it is in portrait mode (0 degrees rotation).
When this is set an init service will start depending on the value of sys.orientation.landscape, which in turn starts a script (/system/etc/rotate_lights.sh) which takes the brightness value from the expected led class (ie. if it's changing to landscape it will look at /sys/class/leds/button-backlight-portrait/brightness) and then set this to the new orientation's led class.
The third part is a small modification to the lights lib which also checks that system property when making changes to the button backlight brightness so that it sets it to the correct class.
Click to expand...
Click to collapse
The necessary files/code are on Virtuous' ICS vivo repository: https://github.com/vivo-ICS/android_device_htc_vivo, and you will also need the patched proprietary libsurfaceflinger.so that references to the changes.
Any way to make this backward compatible with cm7.2?
Un1c0de said:
Any way to make this backward compatible with cm7.2?
Click to expand...
Click to collapse
made a CM7.2 kang for you Inc2 users.
All I did was put in the latest commits as of March 03 2012 and added the rotating softkeys. I can't really test it because I don't have an Inc2, so back up your data in case you are not sure if it will work.
You can flash this without wiping if you are on 7.x already.
For the IncS, I know the rotating buttons for them are not perfect. Sometimes you have to toggle the brightness to get it working. Other times it might take a few seconds to rotate instead of immediately. This is because this script was originally written for ICS roms in mind, but it's backwards compatible with GB.
http://www.mediafire.com/?lggqggdx1m4n656
Wow thanks Kaijura. Downloading now, will post back with results
Sent from my Incredible 2 using xda premium
Thanks Kaijura for posting the info, and the CM7 build. Appreciate it a lot
Is this rom dependent? It will only work on cm 7.2? has anyone tried it on miui? Or any other roms?
Sent from my Incredible 2 using xda premium
Ihatepullups said:
Is this rom dependent? It will only work on cm 7.2? has anyone tried it on miui? Or any other roms?
Sent from my Incredible 2 using xda premium
Click to expand...
Click to collapse
Will be trying on miui.us shortly.
Never mind its beyond my knowledge and time.
Sent from my Incredible 2 using xda premium
knipp21 said:
Will be trying on miui.us shortly.
Never mind its beyond my knowledge and time.
Sent from my Incredible 2 using xda premium
Click to expand...
Click to collapse
Ah, that blows would have been cool... Hey if someone points me in the right direction, I'll try: I know how to use adb and the sdk and I'm an experienced ROM'aholic
Sent from my Incredible 2 using xda premium
Awesome. Hopefully I have time tonight to check it out. Thanks
knipp21 said:
Will be trying on miui.us shortly.
Never mind its beyond my knowledge and time.
Sent from my Incredible 2 using xda premium
Click to expand...
Click to collapse
Ihatepullups said:
Ah, that blows would have been cool... Hey if someone points me in the right direction, I'll try: I know how to use adb and the sdk and I'm an experienced ROM'aholic
Sent from my Incredible 2 using xda premium
Click to expand...
Click to collapse
its different for miui, because we dont build it from source and cant cherry pick commits
miui is more like a sense rom port that uses cm9 or another aosp rom as a "base"
any significant changes have to be done in smali, which is more involved than java source....i k nowwhat has to be changed (or at least part of it) and where for rotating buttons in miui by diffing the builds from aerovan before and after it was implemented but it was a no go on my part...and didnt seem worth the effort to keep pursuing it atm
I tried this yesterday. My phone wouldn't get past the HTC boot screen. I ended up having to pull the battery and reflash my current ROM.
zohner said:
I tried this yesterday. My phone wouldn't get past the HTC boot screen. I ended up having to pull the battery and reflash my current ROM.
Click to expand...
Click to collapse
Hmm, well I guess that didn't work. If you push /system/lib/libsurfaceflinger.so from an earlier working build you should probably be able to boot.
I just copied the file over from the vivo build which seems that it doesn't work with the vivow.
Guess the vivow surfaceflinger is done differently.
kaijura said:
made a CM7.2 kang for you Inc2 users.
All I did was put in the latest commits as of March 03 2012 and added the rotating softkeys. I can't really test it because I don't have an Inc2, so back up your data in case you are not sure if it will work.
You can flash this without wiping if you are on 7.x already.
For the IncS, I know the rotating buttons for them are not perfect. Sometimes you have to toggle the brightness to get it working. Other times it might take a few seconds to rotate instead of immediately. This is because this script was originally written for ICS roms in mind, but it's backwards compatible with GB.
http://www.mediafire.com/?lggqggdx1m4n656
Click to expand...
Click to collapse
Just tried a flash over but didnt work for me. I guess I can always try a wipe and install.
This wouldn't be hard to add to Miui -- as long as they have no weird additions to libsurfaceflinger. You just need the patched liblights, patched libsurfaceflinger (built for CM), script in /system/etc and changes to init.vivo.rc (or init.vivow.rc for Inc2).
Requires no changes to smali or framework.
The other thing is that if someone wants to clean it up and submit it to CM then the MIUI team will pick it up themselves (someone already did this but didn't seem to have to skill / couldn't be bothered to clean it up to their standards and also didn't really submit it correctly).
I would do this but I don't really have the time these days.
Also: I suspect the problem with the lights not working sometimes could be solved just by adding the conditional I have that checks first to see if the brightness is zero to both orientations (in rotate_lights.sh). I will have a quick look at this soon.
just wanted to share a slight modification in the script. When the brightness level is set to the least the leds turn off completely. The attached script makes sure the leds do not turn off completely at this instance. Unzip the file and replace the file in your /etc/ folder. You may want to make a backup of your existing rotate_lights.sh just in case. Ensure the permissions on the file are the same as before after copying.
Just realized that the settings work only the first time when the phone is rotated. I guess I need a better fix. Sorry, remove the attachment as it has undesired issues. Fix No damn good.
Cm10.1 only ...
Fix blue artifacts glitch !!
Don't see bsof since update
Reference a Nexus 4 of the high-pass APQ8064 ...... 3.4 kernel
KGSL drive reference NEXUS 4 3.4 kernel
System transition animation smooth some improved game performance (without increasing power consumption)
Original link:
http://bbs.gfan.com/forum.php?mod=viewthread&tid=5823366&mobile=yes
Sent from my LG-P930 using xda app-developers app
Can someone mirror this file? I registered and it still won't let me download... Something about not enough credit. But the translation is difficult at best.
I didnt try it though because there is no driver source
lyfkevin said:
I didnt try it though because there is no driver source
Click to expand...
Click to collapse
You mean no source code, or they didn't say where the files came from?
These are qcom proprietary files, there is no source code available. But I would be interested to find out where the files came from.
tdmcode said:
You mean no source code, or they didn't say where the files came from?
These are qcom proprietary files, there is no source code available. But I would be interested to find out where the files came from.
Click to expand...
Click to collapse
oh, either. I thought it came from this http://forum.xda-developers.com/showthread.php?t=2107530
not sure BTW
lg has a tendancy to accidentally leak stuff into the development community, if you ask me they like the custom development for the phone but they can't directly support it because of contracts with carriers, either that or its just a few of their employees who don't mind risking their jobs
KronicSkillz said:
lg has a tendancy to accidentally leak stuff into the development community, if you ask me they like the custom development for the phone but they can't directly support it because of contracts with carriers, either that or its just a few of their employees who don't mind risking their jobs
Click to expand...
Click to collapse
Is anyone having issues with clipping with the graphics? scrolling menus or the app drawer produces all kinds of graphical glitches. should i just let it calm down after the flashing?
I hope some devs will take on the task and bring Chameleon OS to Sprint devices like the s3 or Note2. I'll be donating to the cause.
www.Chameleonos.org
Sent from the Mars Rover.
Prolly wouldn't be to hard if a dev was interested as they already have it for vz and att s3's...I also wouldn't doubt some of our more advanced users around here could get one of those 2 versions working on a sprint phone.
If there's source code, it's totally possible. Using the cm10.1 branch as a base, that is.
Sent from my SPH-L710 using Tapatalk 2
Thats a yes. Sounds cool from what I read, could be easily ported since its based on CM as well and the d2vzw has it
Since we originally based ChameleonOS off of CyanogenMod, any device that has official support for CM 10.1 will be easy to convert so that it builds for ChameleonOS
Click to expand...
Click to collapse
I'll try to port it over from the d2vzw, but would need some testers. Someone run this command for me and upload the file it gives (my s3 suicided)
Code:
mount > /sdcard/d2spr.txt
Also this one:
Code:
cat /proc/emmc > /sdcard/d2spr_proc.txt
Thanks
Why? It's CM10 and that's it from what it looks like. Nothing special.
MikeyLee said:
Why? It's CM10 and that's it from what it looks like. Nothing special.
Click to expand...
Click to collapse
A lot of roms resemble each other, but that doesn't mean it shouldn't be used or seen as something "special."
AOKP didn't seem special, neither did PA, but that's in the past now
Sent from my SPH-L710 using Tapatalk 2
MikeyLee said:
Why? It's CM10 and that's it from what it looks like. Nothing special.
Click to expand...
Click to collapse
Read the details on the site
But as always, each is entitled to his/her own opinion
I'd like to try this. Read it briefly and it sounds a bit like JBSourcery. Ran only that when I had my GNex.
I'd test but I live in the sticks with only 3g to download, and I'd only be able to mesa with it at night.
Certainly count me in as a tester. I was about to flash the other versions just to play around. My s3 has become more of an testing device anyways.
Sent from the Mars Rover.
CNexus said:
Thats a yes. Sounds cool from what I read, could be easily ported since its based on CM as well and the d2vzw has it
I'll try to port it over from the d2vzw, but would need some testers. Someone run this command for me and upload the file it gives (my s3 suicided)
Code:
mount > /sdcard/d2spr.txt
Also this one:
Code:
cat /proc/emmc > /sdcard/d2spr_proc.txt
Thanks
Click to expand...
Click to collapse
The second command says 'no such file or directory exist'.
Sent from the Mars Rover.
JohnnyEpic said:
The second command says 'no such file or directory exist'.
Sent from the Mars Rover.
Click to expand...
Click to collapse
Thanks, but just got everything i needed over here: http://forum.xda-developers.com/showthread.php?t=2224232
I'll start the port today, if you wanna test just PM me because I don't have a functional S3 at the moment
PM sent.
Sent from the Mars Rover.
Some unknow person contacted me some minutes ago....
I´m downloading the sources atm
I compiled chameleon os for some devices before and there should be no problem
CNexus said:
Thanks, but just got everything i needed over here: http://forum.xda-developers.com/showthread.php?t=2224232
I'll start the port today, if you wanna test just PM me because I don't have a functional S3 at the moment
Click to expand...
Click to collapse
Why do you need thos files? Everything´s up at cyanogenmods github, thought.
I'd like to test if you can be patient while I download. Will leave up to you, just PM if you'd like.
I need those files so I can change the updater-script mount points appropriately, if necessary. I can't compile it from source because my S3 isn't functional and so I wouldn't be able to pull the proprietary blobs from it, and my computer takes forever to compile too...
CNexus said:
I need those files so I can change the updater-script mount points appropriately, if necessary. I can't compile it from source because my S3 isn't functional and so I wouldn't be able to pull the proprietary blobs from it, and my computer takes forever to compile too...
Click to expand...
Click to collapse
I have a tip for you
---> https://github.com/TheMuppets/proprietary_vendor_samsung.git
Its the repo where the cm / hacksung team is storing every up-to-date proprietary blobs
fuss132 said:
I have a tip for you
---> https://github.com/TheMuppets/proprietary_vendor_samsung.git
Its the repo where the cm / hacksung team is storing every up-to-date proprietary blobs
Click to expand...
Click to collapse
Wow, hax
Whelp, looks like it's time to set up the ol' build environment again
EDIT: So my computers messed up. Some hardware issue causing kernel panics. If anyone wants to compile from source, be my guest, but I'll be porting it over (or at least trying).
First port attempt uploading now.
PM me if you'd like to test (unless you already have), I would be infinitely thankful.
Give me a few days. I'll give this a go at porting.
Sent From My Rooted, S-OFF'd Blackberry Curve using the iOS XDA Application for Android.
Ok. Now that this has touched a bit of spark of interest, should one of you like to start a thread in the dev section, be my guest. I believe this could gain traction in the development section.
Sent from the Mars Rover.