Webtop Hack? - Motorola Atrix 2

I have looked and have not found anything about a webtop hack for the Atrix 2 like the Atrix had. i was wondering if the original Atrix hack works for the Atrix 2 or not. i would be more than willing to try as long as i knew how to fix my phone if it does not work.

what is the hack?

I think he means the one that allowed you to enter web top without needing a dock, just hooking up an HDMI cable.

well, looking at the hack, all it does is push some modified files and libs to /system and 2 apks. as long as the libs and services match and currently reside in the same folders, then it should work.
anyone have an atrix 4g system dump? i can take a look at it tonight to see if this hack will work on your atrix 2
but, i don't have an hdmi cable to test it out. so you'll just have to trust me, lol

in theory it should be the same process right? just backup the files and see if it works and if it does not just replace the original files and everything is back to normal right? i am just curious if those files actually contain the webtop programs or if they are just the access to the actual webtop files.

duke8804 said:
in theory it should be the same process right? just backup the files and see if it works and if it does not just replace the original files and everything is back to normal right? i am just curious if those files actually contain the webtop programs or if they are just the access to the actual webtop files.
Click to expand...
Click to collapse
the hack contained several libraries and system files and if i remember correctly, it had 1 apk (but i can't remember and it's not here in front of me).
if the files that the hack replaces, are the same between the atrix 4g and the atrix 2 and in the same folder, then yes, the hack should work. if the files are the same, but in different folders, the script can be changed to move them to the correct folders. i can look at the files tonight if i get time.

ok thanks i will poke around and see if the files are in the same place and if so i will just try it and see what happens.

let me know if they are in the same place. not sure if the files are compiled or not, i can decompile them to make any changes and change the script. if cwm works, i can even create a nice little flashable package, no adb required.

so the files are in the same place. i followed the instructions at http://forum.xda-developers.com/showthread.php?t=1144119, and it completely broke the hdmi usage. i restored the files and everything was back to normal. I have no idea how to make it work but am willing to learn or try anything you need.

Related

can we get rid of the menu screen?

Does anyone know if there is a way to get rid of the menu screen? I hate having to press the menu button twice to get to the home page. Is there a way to get rid of it? I would like to replace it with the slide unlock that is on the market
If you have root you can edit framework.apk and remove /layout/ keyguard_screen_lock.xml I beleive that will do it but make sure you BACK UP YOUR PHONE FIRST
soundwire said:
If you have root you can edit framework.apk and remove /layout/ keyguard_screen_lock.xml I beleive that will do it but make sure you BACK UP YOUR PHONE FIRST
Click to expand...
Click to collapse
So can you give steps on this because many of us dont want to brick our phones.
Like tell me if im right.
1st step:Backup your phone with nandroid backup.
2nd:go to your computer and connect your phone to it via usb.
3rd:turn off your phone and go to the bootloader (camera+end)
4th: press back untill fastboot
Thats were i get confused on how to go further.
Any help
i hooked it up to my computer and deleted that file but i had no luck it still comes up
Step by Step Request
soundwire,
I am only finding either a .jar or .odex. Can you (or, anyone willing) guide me to the apk?
Appreciate it.
Which apk are you looking for??
Mikey1022 said:
Which apk are you looking for??
Click to expand...
Click to collapse
The framework.apk posted above. I would like top edit/delete the keyguard_screen_lock.xml to remove the menu lock.
thanks for the reply.
I think he meant /system/framework/framework-res.apk but wouldn't you need to resign it after deleting that file and wouldn't this just crash the phone?
d00m said:
I think he meant /system/framework/framework-res.apk but wouldn't you need to resign it after deleting that file and wouldn't this just crash the phone?
Click to expand...
Click to collapse
Thanks for that. I'm not sure about it crashing. Can we get anyone to confirm that this deletion was successful?
<EDIT> I resigned the the deleted the keyguard_screen_lock.xml in the framework-res.apk. I resigned the apk and attempted to push the new .apk. My G1 said there was not enough space on the device? -this is where I probably messed it up- I then manually deleted the original .apk and the phone crapped out. It is stucl on my custom boot screen. re-imaging device as I type.
ok, i've been messing with this and i'm quite sure (not 100%, obviously ) that it can't be done by simply removing the XML. I think they will need to be edited.
heres what i got:
if you remove any of these files, it crashes the phone:
keyguard_screen_unlock_landscape.xml
keyguard_screen_unlock_portrait.xml
keyguard_screen_glogin_unlock.xml
if you remove these it does nothing:
keyguard.xml
keyguard_screen_lock.xml
my guess, is that the images (or whatever's controlling how they are displayed) ais located within unlock_landscape.xml and unlock_portrait.xml
i'm gonna experiment a little more, maybe renaming blank files. I'll keep you all posted
EDIT: ok, changing the portrait and lanscape ones to blank files does nothing, it still crashes. i'm almost 100% sure now that these XML's need editing. the phone doesn't like it when you just remove them
You need those xml files in there, so deleting them would cause your phone to crash.
yeah, thats right. i've listed the ones that make your phone crash and which ones don't in my last post. As soon as we find a way of completely editing these XMLs it will unlock so many things. we'll be able to do nearly anything we want.
It seems like xml editing is pretty tough right now:
"Please be aware that in order to make these changes I actually didn't edit any of the raw xmls. I actually hex edited the values in the binary formatted files. I used HXD to do this."
http://forum.xda-developers.com/showthread.php?t=479019
i know, it's a damn shame google encrypted them.
they could at least let us play with some of them, like the layout ones etc.
so much for open source.
XML Edit
It looks like all the xml docs are encrypted. At least for now I am at a standstill.
I know stericson was able to edit some of the xml files. lol. im trying HXD, mmm interesting! =]
you guys are still trying to figure out how to do this? lol, ive accomplished this 2 weeks ago. it aint easy
IRIE4IPIER said:
you guys are still trying to figure out how to do this? lol, ive accomplished this 2 weeks ago. it aint easy
Click to expand...
Click to collapse
Care to explain mate?
IRIE4IPIER said:
you guys are still trying to figure out how to do this? lol, ive accomplished this 2 weeks ago. it aint easy
Click to expand...
Click to collapse
If your talking about disabling the lock screen.....I really doubt you did. It's not just a simple xml edit. It also has to do with the actual java files, which is what controls whether the keylock comes on or not. This may be possible in the future with cupcake, but not with T-mobiles builds.
If you have figured something out though, please share it.
Stericson
you guys are still trying to figure out how to do this? lol, ive accomplished this 2 weeks ago. it aint easy
Click to expand...
Click to collapse
Yeah sure, if that was the case you would be a linux programmer's and linux programmer's likle to help others P) and it looks like you want to keep it all for yourself... So i think that you didn't remove it.
But if you post a manual/tutorial i will believe you (after trying!)

[How To] Install AmazonMP3 on Haykuro, Dude's, and JF's Firmware

Hi everyone, as many of you guys have noticed, the newer firmwares do not come with the Amazon MP3 application. For those of you who want this, here is a tutorial on installing.
First, download the com.amazon.mp3.zip file uploaded, and place it on your desktop. DO NOT OPEN IT OR EXTRACT IT. Change .zip extension to .apk. For those of you who do not know how to do that, hit Start> My Computer> Organization> Folder and Search Options> and Uncheck "Hide Extentions for Known File Types". Then, delete the .zip extension and type in .apk. Have your G1 ready and plugged in, as you will be using ADB to install this program.
Open up command prompt and type:
cd desktop
adb install com.amazon.mp3.apk
exit
It should now be installed!
For those of you who do not have ADB installed for whatever reason, place the com.amazon.mp3.apk onto your SDcard. Then, using a file manager on your G1 (I use OIfilemanager) navigate to the location where the file is placed and install.
Also, the com.amazon.mp3.apk can also be extracted directly from RC and JF 1.4x builds.
NOTE TO MODS: I understand that Amazon MP3 is not an open source application. Therefore, if for any reason if you guys do not feel that uploading this apk is allowed, feel free to remove this post.
Paying $1 per mp3 can add up over time
With RC 33 i wanted to removed this program, now that JF 1.50 removed automatically, do you believe that i will tried this? But thanks anyway...
PS- People DL music MP3's on theirs PC' for free, Amazon Sucks!
Sometimes I find Amazon MP3 useful for previewing a CD while I am at the library.
By the way, there is no need to distribute the apk here when anyone can just extract it themselves legally from an official update.zip
jashsu said:
Sometimes I find Amazon MP3 useful for previewing a CD while I am at the library.
By the way, there is no need to distribute the apk here when anyone can just extract it themselves legally from an official update.zip
Click to expand...
Click to collapse
Yeah I understand that, I'm just saving them the trouble of having to do it themselves. However, when you say "legally" do you mean distributing this apk is illegal? If so I will remove it.
SolemnWishing said:
However, when you say "legally" do you mean distributing this apk is illegal? If so I will remove it.
Click to expand...
Click to collapse
It's not expressly forbidden. The general stance on xda is as long as the software in question isn't payware, then it is okay (of course a mod is free to make a judgement otherwise). However, everyone should have a RC33 or somesuch build lying around that they can extract the file from themselves anyway.
Seems that most folks don't appreciate the usefulness of Amazon MP3 as a source of track preview. I just wish that it still integrated into ShopSaavy and CompareEverywhere. Used to be you could scan a barcode of a CD and it would pull up the CD on Amazon MP3. If anyone knows how to make this work with current software versions, let me know.
Thank you for the explicit directions. This worked great on my G1 and my friend's using a mac.
Well, I guess that means we will wait for a mod to say something... next in line.. PDFviewer.
Okay, PDFviewer will not work on my JF1.50 build. Just for fun I also tried to push the H build camera and the H build dialer. The pushed camera resulted in the camera app disappearing all together along with the camcorder, gallery and picture frame widget. The H build dialer caused the phone to be completely unresponsive.
Remember, always use a Nandroid backup when attempting risky procedures
SolemnWishing said:
Well, I guess that means we will wait for a mod to say something... next in line.. PDFviewer.
Okay, PDFviewer will not work on my JF1.50 build. Just for fun I also tried to push the H build camera and the H build dialer. The pushed camera resulted in the camera app disappearing all together along with the camcorder, gallery and picture frame widget. The H build dialer caused the phone to be completely unresponsive.
Remember, always use a Nandroid backup when attempting risky procedures
Click to expand...
Click to collapse
If you want to extract features from Haykuro's H build for 1.50 installation, I suggest you hook up ddms so you can get realtime debugging and see what libraries/functions are being called that are causing problems. It should work in the emulator too.
By the way PDFViewer's dependencies have been well established, but the program checks some unknown properties of the build and will refuse to run for non-HTC builds. Decompiling the dex might lead to clues as to what it is and how to workaround it or patch the apk. I'm actually hoping it will just run unmodified on the official T-Mo 1.5 rom expected any day now.
jashsu said:
If you want to extract features from Haykuro's H build for 1.50 installation, I suggest you hook up ddms so you can get realtime debugging and see what libraries/functions are being called that are causing problems. It should work in the emulator too.
By the way PDFViewer's dependencies have been well established, but the program checks some unknown properties of the build and will refuse to run for non-HTC builds. Decompiling the dex might lead to clues as to what it is and how to workaround it or patch the apk. I'm actually hoping it will just run unmodified on the official T-Mo 1.5 rom expected any day now.
Click to expand...
Click to collapse
hehehhe! We can always dream can't we...
lol HTC dream.. well, I do not know how to work apps, or port them or anything, so that is pretty much out of the question. Ill just stick with the obvious ones.
Much thanks!! I wanted Amazon back.
thanks
works on JF flawless. no issue yet. Thanks.
I installed the Amazon MP3 apk night before last and found that the search function wouldn't open its search box. I uninstalled and then pushed it to /system/app via adb and now it works just fine. FWIW, I have apps on SD (the symlink version).
That is good, and does anyone know if the Teeter game from the original Haykuro H build requires some sort of special resource or something? As the game installs, but force closes on startup.
thank you very much for this... anybody got a fix for myfaves???
jashsu said:
If you want to extract features from Haykuro's H build for 1.50 installation, I suggest you hook up ddms so you can get realtime debugging and see what libraries/functions are being called that are causing problems. It should work in the emulator too.
By the way PDFViewer's dependencies have been well established, but the program checks some unknown properties of the build and will refuse to run for non-HTC builds. Decompiling the dex might lead to clues as to what it is and how to workaround it or patch the apk. I'm actually hoping it will just run unmodified on the official T-Mo 1.5 rom expected any day now.
Click to expand...
Click to collapse
hehehe. the properties aren't unknown. It's a library, and 2 framework files.
TheDudeOfLife said:
hehehe. the properties aren't unknown. It's a library, and 2 framework files.
Click to expand...
Click to collapse
So you have PDFViewer working without the "Only for HTC devices" nag screen?
Haha mind enlightening us??
someone run some diffs on thedudes libs and framework files =P!

"Core.xxx" files in /data/btips

I understand this directory has something to do with Bluetooth.
There are ten ~6.7 MB files in that directory with names like core.872 and core.19735.
I did a nandroid backup and then removed them. Everything seems to be OK, but I don't use BT for anything.
Any idea what these are? Could this be related to the BT ROM leak?
jonnythan said:
I understand this directory has something to do with Bluetooth.
There are ten ~6.7 MB files in that directory with names like core.872 and core.19735.
I did a nandroid backup and then removed them. Everything seems to be OK, but I don't use BT for anything.
Any idea what these are? Could this be related to the BT ROM leak?
Click to expand...
Click to collapse
I wish people wouldn't call it a "ROM leak"... it just sounds so silly. ROMs don't leak and the ROM in the Hero isn't leaking. *SOMETHING* is just occupying data space.
Having said that... those are core dumps. Weird, I'd have expected Android to disable core dumps. The phone doesn't have file(1), so it's a little difficult to tell what dumped, but the number in the extension is the PID of the faulting process.
Mine doesn't have any, or I'd yank one over to my desktop and investigate it.
They *are* taking up space in /data, which is going to make the phone look like it has less storage space available (the number in the Settings app will go down). Erase them, they're useless to you.
It might be interesting to search the whole phone with find(1)... that at least is there (or maybe it's in the busybox MoDaCo installs ^_^) and see if there are any other dump files hanging around.
posguy99 said:
I wish people wouldn't call it a "ROM leak"... it just sounds so silly. ROMs don't leak and the ROM in the Hero isn't leaking. *SOMETHING* is just occupying data space.
Having said that... those are core dumps. Weird, I'd have expected Android to disable core dumps. The phone doesn't have file(1), so it's a little difficult to tell what dumped, but the number in the extension is the PID of the faulting process.
Mine doesn't have any, or I'd yank one over to my desktop and investigate it.
They *are* taking up space in /data, which is going to make the phone look like it has less storage space available (the number in the Settings app will go down). Erase them, they're useless to you.
It might be interesting to search the whole phone with find(1)... that at least is there (or maybe it's in the busybox MoDaCo installs ^_^) and see if there are any other dump files hanging around.
Click to expand...
Click to collapse
Great info, thanks. I wonder if they're related to bluetooth crashes since they're in the btips directory?
I searched for other files named core* but nothing looks like a core dump. There's a core.xml and a bunch of "coredump_filter" in proc directories and that's about it.
I think leak is an appropriate term though. Applications that have memory leaks consume memory that they can't release. This is similar, just with the onboard flash.
I probably know the answer already but hoping...is there anyway to delete these core dump files in the btips folder without having to root the phone? Could an app or script on non-rooted device be able to just delete those files? I'm surprised there's no way through the phone to clear system dumps/cache, etc.
Looking for a way since a lot of people have this problem but not many will be comfortable rooting.

Install App From another Android?

I got my self the hero, and my wife the Moment. I am slightly jealous of the hardware she has..but that aside, I am in love with my Hero.
However, she does have one app that i really want and the market place does not have. I assume this is an app installed by sprint.
It is Photo and Video uploader. You set an email address or other location and after a video or photo is taken, it automatically uploads the photo to the predetermined destination. GREAT FOR BACKING UP PICTURES! But, her camera hardware blows. 3.2 MP and it is sooo slow. So picture quality is no where near that of the Hero's 5 MP.
So the real question here - -
Can I ADB into her phone and just take the .APK and ODEX file for this app and push it to my phone? Is it that easy???
Some apps are that easy. Give it a try and find out! The worst thing you'll get is some force closes.
However most stock apps require files from /system/lib that help run that apk. And they don't have the same naming convention therefore you won't know which one(s) it is amongst the 100s there. But I always say try and see what happens.
And if it works upload that .apk for the rest of us!
Thinking out loud here...well..you get the point.
Could I copy all of system/lib and only copy the files that dont already exist?
That could be a giant waste of space though, and it could still rely on a file that I have, not just one that isn't there....
Also since I am not "installing" the app, could Apps2SD hinder me? I am not entirely sure how a2sd works other than tricking the phone into using the SD card as a partition and unioning it with the existing part.
I love how open android is supposed to be, but how the darn manufacturers kill us with the different platform crap.
thedudejdog said:
And if it works upload that .apk for the rest of us!
Click to expand...
Click to collapse
Am I aloud to do that? I have seen XDA Mods get on to some people about uploading APK's. I guess I should read the EULA for that app before I do?
Kcarpenter said:
Thinking out loud here...well..you get the point.
Could I copy all of system/lib and only copy the files that dont already exist?
That could be a giant waste of space though, and it could still rely on a file that I have, not just one that isn't there....
Also since I am not "installing" the app, could Apps2SD hinder me? I am not entirely sure how a2sd works other than tricking the phone into using the SD card as a partition and unioning it with the existing part.
I love how open android is supposed to be, but how the darn manufacturers kill us with the different platform crap.
Click to expand...
Click to collapse
Copying the ../lib/ over and not replacing existing files could work. lol. As for apps2sd... you kind of have two ways you can try installing this. Without copying the lib and all that just try putting the apk on to your sdcard and browsing to it using astro or linda (a file manager) and click on the apk and installing it. See if it errors out or fails. If it does, THEN try copying it and the odex to /system/app (if it has an odex I'm pretty confident you won't be able to install it using package manager). If that still fails then you can go crazy and trying copying the lib ha.
Kcarpenter said:
Am I aloud to do that? I have seen XDA Mods get on to some people about uploading APK's. I guess I should read the EULA for that app before I do?
Click to expand...
Click to collapse
I don't remember if I read it on here or ppcgeeks but I believe officially the only stock apk's not allowed is quick office. But don't quote me on that.
So I hooked up to the Moment through ADB last night.
Found out really quickly that I can SU with it....
There is a "non permanent" hack out there to become root, but I tried it and still couldn't mount the file system to copy from it.
Any ideas guys?
From what I understand the Moment uses an FS16? file System? Something Odd that non of the other droids seem to be using.
Just an Idea, thought I would throw it out there.
Does the temporary root allow for running applications as root an the device itself?
There is an app in the market called root explorer that allows copy/paste/cut/delete from the system/app folder.
It may be possible to use that app to copy the needed filed to your sdcard and then extract them from there.
This would all be contingent on the app being able to mount the directory as r/w though, so who knows, worth a shot though i guess.
rockcrawler said:
Just an Idea, thought I would throw it out there.
Does the temporary root allow for running applications as root an the device itself?
There is an app in the market called root explorer that allows copy/paste/cut/delete from the system/app folder.
It may be possible to use that app to copy the needed filed to your sdcard and then extract them from there.
This would all be contingent on the app being able to mount the directory as r/w though, so who knows, worth a shot though i guess.
Click to expand...
Click to collapse
This root doesn't allow you to run Root apps. not sure why, seems like root would be root.
After some reading, the root method that is being used on the Moment is not the safest. Apparently if you skip a step you have a brick. And with no Nandroid backup at the moment(pun?) I would HATE to attempt it. Apparently though Root sticks until you reboot. There is an INit. script that runs and resets the permisions.
I know, "Don't skips steps and you'll be ok"
I may get brave and try it tonight...
as far as I can tell you cannot install this app on the hero. I'm not sure what the app is called and unless it starts in the /data folder it is under the system dumps
http://www.4shared.com/file/149766091/c3a7ee61/momentsystem.html
nelson8403 said:
as far as I can tell you cannot install this app on the hero. I'm not sure what the app is called and unless it starts in the /data folder it is under the system dumps
http://www.4shared.com/file/149766091/c3a7ee61/momentsystem.html
Click to expand...
Click to collapse
ROCK ON! Thanks for the link to the dump, I hadn't thought about looking around in one of these.
I will post what I find out.
WOOT IT WORKS!!!!!
So any how the application is in that Dump under apps, its only an APK
xms-android-1.0.42-prod.apk
If you are interested in what it does:
You setup predetermined "places" Flikr, FB, EMAIL, what ever.
Any picture or video you take automatically gets put in an upload queue and it sent to your predetermined places.
I am using it for back up, I have 2 kids and sometimes the cell phone is the quickest way to snap a great picture. Keeping these pictures in mutltiple places, like your 7 gig google account, is a nifty way to backup.
I am waiting for a Mod to get back to me if I can post the APK or not. I don't want to get in trouble.
wonder if their youtube app has better picture quality than ours?
BrianDigital said:
wonder if their youtube app has better picture quality than ours?
Click to expand...
Click to collapse
I will let you know in a few minutes. As soon as I get done with my WiFi teether I will compare the two. Pretty sure they should be the same.
EDIT: I am not sure if it is hardware or not. Running the same youTube video side by side - Our HERO has better color quality, Deeper blacker. The Moment has slightly sharper edges to the pictures, not quite as blurry. the moment does not go "Full Screen" for videos either which could be contributing to the sharper look to things. My assumption would be that this is a difference in the hardware. Quality of youTube videos seems to have diminished over the years anyways, none of the really look "good" any more. Probably in an effort to save bandwidth.
However, if you want to take a look personally, I will post the APK for you. Just please don't blame me if you forget to back up the original and want to revert....I love disclaimers.
I was trying to use that picture uploader, for me it stalls on picking a new location. Wonder if it is because I am on gutted rom and missing some pointers somewhere
BrianDigital said:
I was trying to use that picture uploader, for me it stalls on picking a new location. Wonder if it is because I am on gutted rom and missing some pointers somewhere
Click to expand...
Click to collapse
I am using MoDaCo + Optimizations w/ ZipAlign. Not sure if its worth the switch for you or not.
I have never used Gutted so I do not know what it offers/doesn't have.
Gutted is as vanilla as our Rom can get. It's quick too
that's pretty cool and sounds like a great idea for backing up pics so what all would I need to do to get this and install it I have root access already
Kcarpenter said:
WOOT IT WORKS!!!!!
So any how the application is in that Dump under apps, its only an APK
xms-android-1.0.42-prod.apk
If you are interested in what it does:
You setup predetermined "places" Flikr, FB, EMAIL, what ever.
Any picture or video you take automatically gets put in an upload queue and it sent to your predetermined places.
I am using it for back up, I have 2 kids and sometimes the cell phone is the quickest way to snap a great picture. Keeping these pictures in mutltiple places, like your 7 gig google account, is a nifty way to backup.
I am waiting for a Mod to get back to me if I can post the APK or not. I don't want to get in trouble.
Click to expand...
Click to collapse
Wow... that's a really cool program... and just so you know, you can "install" it using adb and it still works fine
Code:
adb install xms-android-1.0.42-prod.apk
Then it will install in /data/apps (or if you have apps2sd, on the sdcard under /system/sd/apps)
Works great on the Sprint Hero and MoDaCo ROM
Kcarpenter said:
I am waiting for a Mod to get back to me if I can post the APK or not. I don't want to get in trouble.
Click to expand...
Click to collapse
The only rule regarding it would be
6. Do not post warez.
If a piece of software requires you to pay to use it, either pay or find your cracks and serials somewhere else. We do not accept warez nor do we permit any member to promote or describe ways in which Warez, cracks, serial codes or other means of avoiding payment, can be obtained.
Click to expand...
Click to collapse
which your app doesn't fit in to. Posting it is not outside of the rules and should be fine.

Advice for porting a rom from one device to another

Hi all,
I'm reaching out to the Android community as a whole hoping to get some pointers. I'm having a hard time finding the information I need here and by googling (although I'm sure it exists) so I was hoping to get some tips or pointers from some people in the know. I've reached out to a few people privately who I know have already done this kind of work but no one is responding to me which is kind of a bummer.
While I'm specifically trying to port the latest Incredible OTA to the EVO, I'm hoping any information gathered here will be helpful to others and applicable to other devices.
Why port the Incredible rom to the EVO? Well for starters the hardware is virtually identical from what I can tell, so it's a good starting point to teach myself some basics and get familiar with Android and rom construction. Second, it's to solve a strange MMS problem for EVO users on Cricket and MetroPCS. We can't send MMS using Sprint based roms but can with Verizon based ones, or by putting the Verizon MMS app on our Sprint roms, but it doesn't work properly. Some people are looking to disassemble the MMS app and figure out what it will take to get it working properly on a Sprint rom. I'm attacking from the other direction (since I have seen it work with the avafroyo vcrc3 rom) by taking the entire Incredible rom and making it work on the EVO.
So my starting point was to install a copy of the latest rooted Incredible OTA on to my phone and then install the latest EVO kernel from HTC. This definitely got me up and running, however I could not use the hardware buttons below the screen (VERY difficult to do anything on the phone lol) and also quickly found out that the SD card was not being recognized either.
I think it was about this time that I found the Android Kitchen that had support for both the incredible and the evo, and starting using that instead of my entirely manual way.
I found that to fix the hardware buttons below the screen I just needed to remove the incredible-keypad.kl file from /system/usr/keylayout and replace it with the supersonic-keypad.kl file from a EVO rom. Maybe renaming the incredible file would have done the trick? Is the kernel somehow looking for a file by that name? I have no idea how this works and would love some explanation.
So now that I had the buttons working I was able to freely navigate the phone and find what else didn't work. It seems that all thing related to the BCM4329 broadcom chip are not working, which means that there is no wifi, there is no bluetooth, and there is no FM radio. All of these features produce errors or don't work within any applications that use them or attempt to turn them on. The SD card was not being recognized so I couldn't read or write to it. Also screen rotation is not working.
Since I'm interested in preserving the apps and framework from the Incredible verizon rom I stayed away from the /system/app and /system/framework folders and looked in other places. I found that bin, etc, and lib folders also look virtually identical between the two roms except for a few minor differences. These also appear to be mostly drivers and stuff. So what I then did was merge the two versions from each rom and replace duplicates with the EVO versions. After this I found that I had proper SD card access again and I know GPS is working as well (no clue if it did before or not).
So at this point I have a rooted Incredible rom running on my EVO with the verizon incredible apps and framework. GPS, 3G, buttons, USB, sd card all work, however still no wifi, bluetooth, or fm radio. It's all this one BCM4329 chip. The drivers and related files all seem to be the same. The incredible and the EVO both use the same chip from what I can tell. I don't know where the breakdown occurs now. Is it in the framework or app? Is the support for the wifi and stuff built directly into the kernel? I've noticed during repacking of the boot image that there seems to be a driver in there for the broadcom chip.
I found a sensor file in the /system/lib/hw folder called sensors.inc.so. I copied over a sensors.supersonic.so file from the EVO rom and also renamed a copy to sensors.inc.so just in case. This hasn't helped with any of the rotation though. It seems like the contents of /system/lib are almost identical between the Incredible and EVO roms and these seem like they're all hardware drivers.
Anyone have any input towards getting screen rotation and the wireless stuff working? I feel like I've made decent progress literally replacing stuff, but I've either replaced too much, or there now needs to be some real editing somewhere, or something.

Categories

Resources