Database Users

Creating Custom ROM for nexus one

To save me "re-inventing the wheel" can any one advise me on the propriety files needed from the N1 to build a custom ROM for it? e.g. libhtc_acustic.so and libhtc_ril.so
I am trying build a ROM from the open source project, so if anyone has advice for me please let me know.
Before you ask, the only reason i am doing this is because i have system apps i want to try on it and they need to be signed with the same key as the shared system uid. If you no a way i can build a ROM from the Nexus to do this please let me know.
Ne0

I don't believe the 2.1 source has hit the AOSP repos yet. So you won't be able to build a complete framework/kernel until that is released.
You could dump your N1 and then just unarchive and resign everything, but it would be a hell of a job I think

I realise 2.1 is not a public resource yet, but i am attempting to roll back to Eclair, just for the purpose of testing my system apps.
I want to resign everything and i dont mind if its a hell of a job!! What do you mean by unarchive? and whats the best way to get a complete dump?
Thanks for your help.
Ne0

Roll back to eclair won't work. The binary blob drivers are tied to a kernel and the kernels are (kinda) tied to the platform releases. So the N1 can only house 2.1 right now (IIRC)
What I was alluding to is that each APK/JAR contains a signature that you want to replace with a sig made by the test keys right?
So if you pulled /system from you're N1 and re-signed each apk and the framework with test keys and pushed that back or made and update.zip holding the re-signed apks (like the theme-makers) you should then be able to test your platform app that is also signed with test keys and a shared UID.

I too would like to know the answer to this.

SilentMobius said:
Roll back to eclair won't work. The binary blob drivers are tied to a kernel and the kernels are (kinda) tied to the platform releases. So the N1 can only house 2.1 right now (IIRC)
What I was alluding to is that each APK/JAR contains a signature that you want to replace with a sig made by the test keys right?
So if you pulled /system from you're N1 and re-signed each apk and the framework with test keys and pushed that back or made and update.zip holding the re-signed apks (like the theme-makers) you should then be able to test your platform app that is also signed with test keys and a shared UID.
Click to expand...
Click to collapse
SilentMobius said:
I don't believe the 2.1 source has hit the AOSP repos yet. So you won't be able to build a complete framework/kernel until that is released.
You could dump your N1 and then just unarchive and resign everything, but it would be a hell of a job I think
Click to expand...
Click to collapse
Correct ... resigning everything with test keys would enable some1 to test out said system apps (also signed with testkeys) ... but only as a test, as it would not be suitable for everyday ROM use.
Resigning with test keys is trivial (search for it) ... but I'd recommend you use the de-odex'd system (see the nexus1 theme templates in my sig).
The reason this is not a everyday solution is b/c resigning everything with testkeys will break the google checkin process, meaning signing into google and using the market will largely break.
But if this is truly just for some sorta system app test, that shouldn't matter.
Other than that, the OP's question is fairly broad in scope. A question like "how to create a custom ROM for nexus1" ... implies many things and many answers.
~enom~

enomther said:
Resigning with test keys is trivial (search for it) ... but I'd recommend you use the de-odex'd system (see the nexus1 theme templates in my sig).
The reason this is not a everyday solution is b/c resigning everything with testkeys will break the google checkin process, meaning signing into google and using the market will largely break.
~enom~
Click to expand...
Click to collapse
Thanks enom, great work. My system apps are just for testing, though it would be handy to make it into a complete ROM so i dont have to keep reflashing when i need to use them. Are you saying that it is not possible to get google checkin working this way? or just that no one has done it yet?
Ne0
Just resigned, sync'd with google, market works and i can install my system apps. All thanks to ~enom~, thanks for posting the deodexed system, saved me a bit of time!

Can I download ADT manually

I've been messing around in google app inventor getting an idea for the flow of code and figured that it's time to step up to an actual coding environment.
So I went and downloaded the most recent SDK and eclipse. I installed all the available resources and revisions.
Then i hit a snag. The guide said that in order to properly set up Eclipse i need the ADT plugin. I opened the help menu and went to install new software and clicked on the add button. In the name section i put "ADT Plugin" and in location i put the exact web address they gave and it kept giving an error that said unable to connect to repository... i even tried http over https but still experienced the same issue. I entered the website enter my web browser in hopes that it would connect to a ftp server or start a direct download but unfortunatly it was a google site that was no longer available.
So i want to know if theres a mirror download somewhere that i can manually install to eclipse.
Also my eclipse info
Eclipse SDK
Version: 3.6.1
Build id: M20100909-0800
Sent from my futuristic phone

Yes mate, from here...
http://developer.android.com/sdk/eclipse-adt.html
Towards the bottom of the page it tells you what to do if the URL doesn't work.

johncmolyneux said:
Yes mate, from here...
http://developer.android.com/sdk/eclipse-adt.html
Towards the bottom of the page it tells you what to do if the URL doesn't work.
Click to expand...
Click to collapse
I freaking love you in a strictly platonic way.
I kinda feel like an idiot cause I didn't read farther lmao
Sent from my futuristic phone

ironlood said:
I freaking love you in a strictly platonic way.
I kinda feel like an idiot cause I didn't read farther lmao
Sent from my futuristic phone
Click to expand...
Click to collapse
lol - glad to help mate.

Okay just ran into another hitch
I downloaded the zip file and go to install new software but instead of the website i use the archive. It provides me with a list of 3 options
Android DDMS
Android Development Tools
Android Hierarchy Viewer
I put a check in each box and click next it says calculating Dependencies and requirements then i get an error that says
Cannot complete the install because one or more required items could not be found.
Software being installed: Android Development Tools 8.0.1.v201012062107-82219 (com.android.ide.eclipse.adt.feature.group 8.0.1.v201012062107-82219)
Missing requirement: Android Development Tools 8.0.1.v201012062107-82219 (com.android.ide.eclipse.adt.feature.group 8.0.1.v201012062107-82219) requires 'org.eclipse.gef 0.0.0' but it could not be found
Now this has me at a loss. If i downloaded the Archive in theory i shouldn't have to connect to any more sites to install the plugin. I want to know if there is a way to drag and drop the contents of the archive to a plugins folder then open eclipse and refresh the installed plugins in order to show that ADT has been installed.

Not sure if the 64 bit side of things could be an issue (either for you or for anyone), but this guy seems to have solved the same problem...
http://superuser.com/questions/221944/huh-jdk-not-found-on-windows-7-64-bit
Hope it helps mate.

KK ill see if i can follow this and come up with a fix to my issue. not too sure how this will work since im running a 32bit system with windows Vista

I'm still experiencing the same issue with eclipse unfortunately, i even downgraded to Galileo instead of Helios thinking that it was an incompatibility issue with the newest version or the most recent version. I even tried dragging the .JAR files in the ADT zip into the eclipse folder in an attempt to get Eclipse to recognize the plugins without having to install them through the "install new software" dialog.
Everytime I try to connect to the download server it gives me a message that says An exception stack trace is not available. Or Unable to connect to repository http://dl-ssl.google.com/android/eclipse/content.xml
Connection refused: connect

useful link

https://opensource.motorola.com/sf/projects/flipout
particular
https://opensource.motorola.com/sf/sfmain/do/go/rel1490?returnUrlKey=1294483663414

Wow! Cool!
It seems the china release is the latest. (That's what you link to). What I'd really like to fix is the x-y-z axis mapping of the accelerometer. So many apps don't work....
How do we use the files? Is it easy to pack roms, create Update.zip files, or just copy them to the right place?

ghostwheel said:
Wow! Cool!
It seems the china release is the latest. (That's what you link to). What I'd really like to fix is the x-y-z axis mapping of the accelerometer. So many apps don't work....
How do we use the files? Is it easy to pack roms, create Update.zip files, or just copy them to the right place?
Click to expand...
Click to collapse
Full ack with the accelerometer. But I fear it's not possible to install a custom rom without signing it with the Motorola key (at least that's what I heard).
/edit: After reading this, and this, its clear that the problem lies with Android 2.1: "FLIPOUT runs Android 2.1, or API level 7. The Display.getRotation() method is available as of Android 2.2, or API level 8. To handle this, you can detect the API version and on version 7 or below, use Display.getOrientation(), like this."
Nobody will use the workaround, so we will be stuck with a broken orientation sensor until (and only if) 2.2 is released for the Flipout.

zerghase said:
/edit: After reading this, and this, its clear that the problem lies with Android 2.1: "FLIPOUT runs Android 2.1, or API level 7. The Display.getRotation() method is available as of Android 2.2, or API level 8. To handle this, you can detect the API version and on version 7 or below, use Display.getOrientation(), like this."
Nobody will use the workaround, so we will be stuck with a broken orientation sensor until (and only if) 2.2 is released for the Flipout.
Click to expand...
Click to collapse
Interesting.
But I don't think this is the problem with the Flipout. Many apps actually adjust for screen orientation. Just the wrong way. No matter which way you hold the screen, orientation is off (e.g. Layar, wikitude).
And, the problem is old. It was around before 2.2 came out, or maybe when 2.2 was very young. So, I think most apps weren't written for 2.2 at that stage.
But to a question:
To produce a custom firmware we need to be able to sign stuff. (How was this found for droid?). But with root, we can overwrite anything on the phone, probably except for the init.rd, where the kernel is stored. Is that true? Could we patch by overwriting some files in, for example, /system/lib ?

Yes, with root you can change everything in the running system, but I don't know how far the kernel is protected. It could be possible that the kernel is signed and the system refuses to boot if it has been altered (but you should ask that a Motorola-pro, I'm new to that).
I think it's easier to modify the apps themselves. When they're open-source just apply the fix and recompile, if not...
maybe the developers will be grateful for some hints on bugs in their apps (I would be). And if they are not, it still appears easier to make a change to the bytecode of the erroneous apps than hacking something into the system to make some apps work (and maybe breaking others...).
If I have time, I'll read into the dalvik system and play around a bit with some apps.

[Q] How To Create A Theme.apk

Hi All
I have the most recent version of Oxygen which includes a "theme picker" app.
Similar to the one found in the HD ROM's it gives the opportunity to change the entire system theme, without flashing a zip. Which is good news
However, I have been trawling the internet trying to figure out how to create the .apk needed to create my own themes, failing miserably.
Could someone with the required knowledge post a tutorial maybe? Or a link to where the info is so that I can do my own research?
Thanks

i've not installed the test rom so cant check, but does it come with any theme.apk's pre-installed?
if so i'd start by pulling them apart and looking at the .xml and images and change them from there.

str355 said:
i've not installed the test rom so cant check, but does it come with any theme.apk's pre-installed?
if so i'd start by pulling them apart and looking at the .xml and images and change them from there.
Click to expand...
Click to collapse
Do you know I didn't even think of that
I shall do so and see what I can come up with

Well I downloaded the Android SDK and all the tools required, then I installed eclipse and started a tutorial on how to build an app - as I assumed this is what I will need to do... but then my brain started to hurt and I needed sleep!

[Q] Overdrive on Rooted NST--HELP!

Hello: I followed the directions on this site to root my NST. The only reason I wanted to root it was to be able to download public library books directly on the NST through the Overdrive app. I was successful in rooting, but cannot get the Overdrive app to work. By reading the other threads here, I learned about a site that had an older version of the Overdrive app that is supposed to work with Android 2.1. After downloading the app and trying to open it, I get the message "there is a problem parsing the package." I searched this error message and found I was supposed to go to "settings--applications and then click on the option to allow non market apps to be downloaded. However, the "settings" on my rooted NST does not have an "applications" tab or option to go to. Any idea how to get the Overdrive app to work or what I am doing wrong?
Thank you.

this error is related to API version of program. perhaps you can decmpile apk and low API to 7 (Android 2.1)

hshsh said:
this error is related to API version of program. perhaps you can decmpile apk and low API to 7 (Android 2.1)
Click to expand...
Click to collapse
Hshsh, thanks for the response. However, I am new to Android and do not understand your response . . . could you dumb it down for me?
Thanks, Lisa

Well a short explanation is that you have to take apart the .apk and change the required version of Android needed to run it.
You'll want to search this forum for apktool, the program that takes things apart.
Code:
apktool d someapp.apk \someapp
edit \someapp\AndroidManifest.xml
apktool b \someapp someapp.apk
jarsigner ...
I have OverDrive on my Nook but the reader is trash.
The OverDrive DRM and the Adobe Digital Editions DRM are incompatible,
so you can't load a book with the OD and read it on the stock Nook reader.
I still DL to the PC then transfer library books.
It's on my big list of things to do to look at this.

Renate NST said:
Well a short explanation is that you have to take apart the .apk and change the required version of Android needed to run it.
You'll want to search this forum for apktool, the program that takes things apart.
Code:
apktool d someapp.apk \someapp
edit \someapp\AndroidManifest.xml
apktool b \someapp someapp.apk
jarsigner ...
I have OverDrive on my Nook but the reader is trash.
The OverDrive DRM and the Adobe Digital Editions DRM are incompatible,
so you can't load a book with the OD and read it on the stock Nook reader.
I still DL to the PC then transfer library books.
It's on my big list of things to do to look at this.
Click to expand...
Click to collapse
Thanks for taking the time to answer and for your response. I will start researching this but was hoping it was going to be an easier fix.
Lisa

Did you get Overdrive 2.3.0.1? That should install fine without any decompile / recompile.