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.
Related
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.
The audio sound quality and volume has been greatly improved on IncDoes's desire hd port. The audio through the headphone jack sounds better and is much louder. What file or files are in direct relation to this? Basically, what file or files do I need to rip out of his Rom to apply this to another Rom?
EDIT (10-10-10): about a week or so ago i did get the result i was looking for. i copied and pasted probably about a dozen or so files from the Desire HD rom to the Virtuous rom i am running and i did get this to work. i just have no idea whatsoever, which file actually did it.
i'd like to get this figured out so that i can apply this hack to another rom if i ever decide to switch to another rom. i'm running a very early version of Virtuous, 2.0 to be exact. if i update, i'll loose what i somehow did. 2.0 has been running pretty flawlessly though i gotta say.
jasonb1985 said:
The audio sound quality and volume has been greatly improved on IncDoes's desire hd port. The audio through the headphone jack sounds better and is much louder. What file or files are in direct relation to this? Basically, what file or files do I need to rip out of his Rom to apply this to another Rom?
Click to expand...
Click to collapse
Make it easy on yourself and just use the ROM ;p
DroidHam said:
Make it easy on yourself and just use the ROM ;p
Click to expand...
Click to collapse
ok, i would, but the rom is broken. streaming any kind of audio makes the phone unresponsive within about 10 minutes or so. it works fine for about 5-10 minutes and then the cpu usage gets maxed out and the phone becomes completely unresponsive. if that one issue was fixed i would continue to use the rom, but until then, it's useless to me. in the meantime i would like to get this kind of audio quality onto a more stable rom.
Probably the wrong section for this...
Sent from my ADR6300 using XDA App
GatorsUF said:
Probably the wrong section for this...
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
how so, this is development?
jasonb1985 said:
how so, this is development?
Click to expand...
Click to collapse
No Q&A threads in development is why... I can't help you(I am idiot), but any improvement that can be mashed into other roms is a plus.
ToyTank said:
No Q&A threads in development is why... I can't help you(I am idiot), but any improvement that can be mashed into other roms is a plus.
Click to expand...
Click to collapse
yea. thanks. if its in the wrong section hopefully somebody can move it.
none of the rom developers on here know the answer? whoever can help me with this gets a small donation... thats how bad i need this.
if it was me, i would probably pull the lib audio files out of the lib folder and make an update with those. I'm new to the incredible though.
incubus26jc said:
if it was me, i would probably pull the lib audio files out of the lib folder and make an update with those. I'm new to the incredible though.
Click to expand...
Click to collapse
how do i make an update?
use adb push and overwrite them. make sure to nandroid backup first. also, when you boot run adb logcat just in case you run into errors.
give it a few days, theres gonna be a big skyraider rip or a new version of RR with everything fixed i bet
DroidHam said:
give it a few days, theres gonna be a big skyraider rip or a new version of RR with everything fixed i bet
Click to expand...
Click to collapse
already tried the skyraider one, the audio isn't the same as it is on incdoes's rom.
Panda Fuzz said:
use adb push and overwrite them. make sure to nandroid backup first. also, when you boot run adb logcat just in case you run into errors.
Click to expand...
Click to collapse
i tried adb pushing, it told me i couldn't push a whole directory.
jasonb1985 said:
i tried adb pushing, it told me i couldn't push a whole directory.
Click to expand...
Click to collapse
do a backup and try this. Ive never made an update for this phone before.
http://www.mediafire.com/?mfs49tsbgk8gycn
If it donr work, im sorry it was just a guess
incubus26jc said:
do a backup and try this. Ive never made an update for this phone before.
http://www.mediafire.com/?mfs49tsbgk8gycn
If it donr work, im sorry it was just a guess
Click to expand...
Click to collapse
i'm gonna try it right now. i have plenty of backups. i'll report back in a few.
i think your update.zip worked like it should have( phone booted and is running), but the audio is still the same. i think it's a different file than the ones that are in your update. thanks for the try though.
is it possibly part of the framework, and not in the lib directory?
haven't installed that rom, but in other roms i've used where dspmanager is installed, that app greatly improved the sound quality. maybe it's built into the framework with tweaked settings already in place?
radiohead14 said:
haven't installed that rom, but in other roms i've used where dspmanager is installed, that app greatly improved the sound quality. maybe it's built into the framework with tweaked settings already in place?
Click to expand...
Click to collapse
yea i already have DSP manager. have been using it since the day that it was discovered to work on the incredible. this is something completely different. on incdoes's desire port the volume is considerably louder and just sounds better. there has got to be someway we can make this work on other roms.
i was just hoping a dev that knew which files controlled what, could lead me in the right direction.
have you tried just PMing ID and asking?
I assume this is the correct forum otherwise please move this.
What is the best article(s) to read if you want to start learning how to port roms from other android phones to the Evo? I've been searching on here and on google and it seems most articles are either outdated or only talk about editing existing cooked roms so I finally broke down and posted this. Yes I do use Linux and I do program in Java and .NET and do have a bachelors in software development but I have just never looked into doing this type of work until now.
Thank you, any direction I'm pointed in is appreciated.
I'll direct to you the Q&A forum.
Side Note:This goes in General,but im nice so ill answer you question.
There is no real BOOK to read, a java book is a good start, but you say you know java, so you can probably skip that.
Basically, this is all you have to do.
Download "Dsixda's Kitchen" to your linux distro(amazing software)
Grab a rom from another device.
Grab one of our(evo)stock roms(deodexed Stock 3.70 is good for froyo port,4.12 for gingerbread)
Open the kitchen, and find the option(#19 i think it is), and follow the steps to port it(hold on, your not done yet)
From there you will need do some manual work by tinkering with libs,tinkering with the boot.img, bascally just tinkering with everything related to booting(libs,ramdisk,hw-libs,etc.) untill you can get it to boot or bootloop.
If it boots, thats great, if it bootloops, youlle need to logcat it then debug it.
If you need help with something, pm me, other than that, thats basically(*note: i said basic, more complexed roms like sense 3.0 and non-htc device rom may require extra work)(*note2:alot of times, its going to be a no-booter, but just keep trying.)
sirmx said:
I'll direct to you the Q&A forum.
Click to expand...
Click to collapse
Thanks sirmx, I did do a search there but again came up short.
ThatSmartB0y said:
Side Note:This goes in General,but im nice so ill answer you question.
There is no real BOOK to read, a java book is a good start, but you say you know java, so you can probably skip that.
Basically, this is all you have to do.
Download "Dsixda's Kitchen" to your linux distro(amazing software)
Grab a rom from another device.
Grab one of our(evo)stock roms(deodexed Stock 3.70 is good for froyo port,4.12 for gingerbread)
Open the kitchen, and find the option(#19 i think it is), and follow the steps to port it(hold on, your not done yet)
From there you will need do some manual work by tinkering with libs,tinkering with the boot.img, bascally just tinkering with everything related to booting(libs,ramdisk,hw-libs,etc.) untill you can get it to boot or bootloop.
If it boots, thats great, if it bootloops, youlle need to logcat it then debug it.
If you need help with something, pm me, other than that, thats basically(*note: i said basic, more complexed roms like sense 3.0 and non-htc device rom may require extra work)(*note2:alot of times, its going to be a no-booter, but just keep trying.)
Click to expand...
Click to collapse
Sounds good, what I'll do is go ahead and start one, nothing special maybe even ones that already been done just to get the experience under my best.
ThatSmartB0y said:
Side Note:This goes in General,but im nice so ill answer you question.
There is no real BOOK to read, a java book is a good start, but you say you know java, so you can probably skip that.
Basically, this is all you have to do.
Download "Dsixda's Kitchen" to your linux distro(amazing software)
Grab a rom from another device.
Grab one of our(evo)stock roms(deodexed Stock 3.70 is good for froyo port,4.12 for gingerbread)
Open the kitchen, and find the option(#19 i think it is), and follow the steps to port it(hold on, your not done yet)
From there you will need do some manual work by tinkering with libs,tinkering with the boot.img, bascally just tinkering with everything related to booting(libs,ramdisk,hw-libs,etc.) untill you can get it to boot or bootloop.
If it boots, thats great, if it bootloops, youlle need to logcat it then debug it.
If you need help with something, pm me, other than that, thats basically(*note: i said basic, more complexed roms like sense 3.0 and non-htc device rom may require extra work)(*note2:alot of times, its going to be a no-booter, but just keep trying.)
Click to expand...
Click to collapse
Don't forget some of the most important stuff is in the build.prop and update-script.
Word of advice, look at a sense 2.1 and check out the base that was used. You can also use beyond compare and basically skip Linux all together. Using kitchen to deodex the ruu is a good first step. Choose option 11 in the menu.
Personally, I would start off with a working port and changing apps and moving stuff around. Also get a good list at which libs are associated with what. But use stock bins, etc, xbin, hw libs, and ported apks, framework, and software associated libs. Stock boot.img and a good updater-script. Also know key
Things like the EVO density is 160, vold_stab is usb, amkd is rotation, gsl hw accel stuff like that.
But first things first, Google is ur friend and use the q&a section.
Sent from my PC36100 using Tapatalk
Leoisright said:
Don't forget some of the most important stuff is in the build.prop and update-script.
Word of advice, look at a sense 2.1 and check out the base that was used. You can also use beyond compare and basically skip Linux all together. Using kitchen to deodex the ruu is a good first step. Choose option 11 in the menu.
Personally, I would start off with a working port and changing apps and moving stuff around. Also get a good list at which libs are associated with what. But use stock bins, etc, xbin, hw libs, and ported apks, framework, and software associated libs. Stock boot.img and a good updater-script. Also know key
Things like the EVO density is 160, vold_stab is usb, amkd is rotation, gsl hw accel stuff like that.
But first things first, Google is if friend and use the q&a section.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
ah yes, forgot about build.prop,and i think the kitchen takes care of updater script(unless the device has specific mount pointsor you want text or to clear cache and system). i was just getting the basics to boot, from ther he can debug the errors out of the log.
What about something A LOT simpler like adding the CRT animations to a ROM? any pointers? Any TUT you can point me to?
ThatSmartB0y said:
ah yes, forgot about build.prop,and i think the kitchen takes care of updater script(unless the device has specific mount pointsor you want text or to clear cache and system). i was just getting the basics to boot, from ther he can debug the errors out of the log.
Click to expand...
Click to collapse
Oh I hear ya. Just throwing in my 2 cents. Found that having a clean updater-script is half the battle.
Sent from my PC36100 using Tapatalk
I'm actually glad this thread is still here we don't get to learn much from the devs here. I mean its mostly do it yourself but a getting started guide isn't a bad thing. Mods are quick to move and people are quick to flame but I say leave it, where else is the knowledge pool? Can you really learn this stuff in Q and A seems like it would be mostly help my phone doesn't boot...
Sent from my PC36100 using XDA App
Check out the APKTool, APKManager threads. Lots of great valuable information in there.
I sometimes wish XDA focused more on the "HOW TO" and less on the delivery aspect. The more folks developing, the further we will be along
Another great way to get started is to mentor with another established developer.
evomattnc said:
I'm actually glad this thread is still here we don't get to learn much from the devs here. I mean its mostly do it yourself but a getting started guide isn't a bad thing. Mods are quick to move and people are quick to flame but I say leave it, where else is the knowledge pool? Can you really learn this stuff in Q and A seems like it would be mostly help my phone doesn't boot...
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Well said. People love to flame anyways and XDA is famous among other Android forums for being so harsh. This thread helped me out big time, and it's especially nice to see Leoisright and myn in here giving up a few pointers, because I too was curious about porting. I never worked up the confidence to ask, just too worried about it being passed over or getting flamed because I'm young and curious.
Sent from my PC36100 using XDA App
Yah, Q&A never got me anywhere, i learned off of trial and error, still learning now.
EDIT:OP:IF you want you can ombine mine and leo's tuts together, to make this thread permanent.
Subscribed!!!!!!!!
Good stuff!
Sent from my PC36100 using Tapatalk
Yeah I want to thank the devs that have stopped by so far and gave tips, already using them . Hopefully most of them drop In at least once and leave one tid bit that would make this thread awesome!
Sent from my PC36100 using XDA App
Ha, you taking applications for an apprentice myn?
myn said:
Check out the APKTool, APKManager threads. Lots of great valuable information in there.
I sometimes wish XDA focused more on the "HOW TO" and less on the delivery aspect. The more folks developing, the further we will be along
Another great way to get started is to mentor with another established developer.
Click to expand...
Click to collapse
Sent from my PC36100 using XDA App
Yes I was afraid to post this at first which isn't good, you shouldn't be afraid to ask questions but I get that sometimes the same questions have been answered 100 times prior so I understand the quick to judge portion of it. But I want to thank everyone who has contributed tips, advise and places to start. Thank you.
Leoisright said:
Don't forget some of the most important stuff is in the build.prop and update-script.
Word of advice, look at a sense 2.1 and check out the base that was used. You can also use beyond compare and basically skip Linux all together. Using kitchen to deodex the ruu is a good first step. Choose option 11 in the menu.
Personally, I would start off with a working port and changing apps and moving stuff around. Also get a good list at which libs are associated with what. But use stock bins, etc, xbin, hw libs, and ported apks, framework, and software associated libs. Stock boot.img and a good updater-script. Also know key
Things like the EVO density is 160, vold_stab is usb, amkd is rotation, gsl hw accel stuff like that.
But first things first, Google is ur friend and use the q&a section.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
So I've been looking at beyond compare, did you use this from everything and just edit all the non evo files to match existing evo ones from within windows?
Back in the days of Gingerbread nivron created this excellent tutorial on how to enable 1X / 3G to display correctly in the status bar.
Now that most people are moving over to ICS, the 1X/3G issue returns. It also seems that the files have been changed and rearranged. The smali edits are no longer located in StatusBarPolicy.smali. In fact, that file is gone completely in ICS.
I was able to locate 2 files that seem to contain the variables that need to be changed to fix the issue: TelephonyIcons.smali and NetworkController.smali. Since I am not a developer or a Java programmer, I wouldn't know how to approach the code. So if anyone is willing to take on this challenge, it would be greatly appreciated. The files are attached to the post for your viewing/editing pleasure.
6uPMAH said:
Back in the days of Gingerbread nivron created this excellent tutorial on how to enable 1X / 3G to display correctly in the status bar.
Now that most people are moving over to ICS, the 1X/3G issue returns. It also seems that the files have been changed and rearranged. The smali edits are no longer located in StatusBarPolicy.smali. In fact, that file is gone completely in ICS.
I was able to locate 2 files that seem to contain the variables that need to be changed to fix the issue: TelephonyIcons.smali and NetworkController.smali. Since I am not a developer or a Java programmer, I wouldn't know how to approach the code. So if any one is willing to take on this challenge, it would be greatly appreciated. The files are attached to the post for your viewing/editing pleasure.
Click to expand...
Click to collapse
OH YEA!! I have asked about this in several posts since I went to ICS. If other folks are wanting this mod, please speak up and let others know this is a desired mod...
I would love to see this in CM9 if it were possible.
Kenny987654321 said:
I would love to see this in CM9 if it were possible.
Click to expand...
Click to collapse
The 3G/1X is in CM9 by default. I will look into the ICS leaks tomorrow and see where the change needs to be... unless someone does it first.
Sent from my SPH-D710 using Tapatalk 2
nivron said:
the 3g/1x is in cm9 by default. I will look into the ics leaks tomorrow and see where the change needs to be... Unless someone does it first.
Sent from my sph-d710 using tapatalk 2
Click to expand...
Click to collapse
the savior returns!!!!
Sorry it took so long. The new version is here!
nivron said:
The 3G/1X is in CM9 by default. I will look into the ICS leaks tomorrow and see where the change needs to be... unless someone does it first.
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
Does anyone know if there is a working app mod or hack to enable the incredible2 to have nexus-like on-screen buttons and disabling the lights and functions of the hardware buttons like on ParanoidAndroid has it?
cowboyv said:
Does anyone know if there is a working app mod or hack to enable the incredible2 to have nexus-like on-screen buttons and disabling the lights and functions of the hardware buttons like on ParanoidAndroid has it?
Click to expand...
Click to collapse
This is the main reason I stick with PA. If someone can mod the framework of the rom you are using, it may be option, but most of the roms don't have that built in. You might mention it in the thread of the rom you use and see if someone can hook you up.
Yeah, I'm wondering if maybe you can copy and paste the frameworks folder from PA rom to the other rom and if that would activate the on screen buttons.
I doubt that would be a good idea, but I'm not the one to answer that one.
Sent from my Incredible 2 using xda premium
cowboyv said:
Yeah, I'm wondering if maybe you can copy and paste the frameworks folder from PA rom to the other rom and if that would activate the on screen buttons.
Click to expand...
Click to collapse
Just a warning, that very well may put your phone into a boot loop, if you decide to try it......BACKUP first
Sent from my Incredible 2 using xda app-developers app
@Phantom: according to this thread it's just a matter of decompiling framework-res.apk, making some changes and then recompiling the whole thing, which is why I'm thinking maybe it is as simple as copying/pasting the apk.
@Tricsuit: Yeah, I know. I already learned my lesson and before attempting stupid ideas like this one, I run a full back up of the rim, settings, apparently and data, and then make sure to save the back up file in my box to be able to retrieve it from my computer just in case something else hiccups.
cowboyv said:
@Phantom: according to this thread it's just a matter of decompiling framework-res.apk, making some changes and then recompiling the whole thing, which is why I'm thinking maybe it is as simple as copying/pasting the apk.
@Tricsuit: Yeah, I know. I already learned my lesson and before attempting stupid ideas like this one, I run a full back up of the rim, settings, apparently and data, and then make sure to save the back up file in my box to be able to retrieve it from my computer just in case something else hiccups.
Click to expand...
Click to collapse
Thanks for the share m8, I will try to look into this one more over the weekend. If you decide to give it a go with a copy and past let me know how it works out.
Yeah, I'm on call for the next couple of days so I won't be able to play with the rom, but if I'm able to make it work I'll post it here. :beer:
Welp, I began to toiler around with this, succeed in decompiling res-framework.apk, changing the bools, arrays and dimens values and added the menu images, basically all the way down to step 5, but I can't seem to recompile it back into .apk... uhm... a little help guys? ^^;