Database Develop

Tutorial For building custom rom for G1

Can any body post tutorial for building a custom rom for G1 and Hero?

wrong area to post this... probably should take it off.

were should i put this thread then

Q&A buddy.

I wrote a few how-to's on compiling your own android build from source, i recommend starting here:
http://robblue2x.blogspot.com/2009/07/how-to-set-up-ubuntu-virtual-machine.html
it is a bit out of date now because android moves so fast, its incredibly hard to keep up to date!

robblue2x said:
I wrote a few how-to's on compiling your own android build from source, i recommend starting here:
http://robblue2x.blogspot.com/2009/07/how-to-set-up-ubuntu-virtual-machine.html
it is a bit out of date now because android moves so fast, its incredibly hard to keep up to date!
Click to expand...
Click to collapse
Just visited this link But how do modify the existing files of android OS ?

If you have to ask how to change the files then you probably shouldn't be messing with the code for an OS. There is alot to it. You need to know how to set up linux, Git, repo, sdk, emulator, learn java,maybe some C++, edit xml files, and compile the edited code just to name a few.
read this
If you get that working then all you need is a text editor to start changing code.
Good luck!

What about modding existing roms?
Here is what I know so far...
system apps are not individualy signed
Rom must be packaged in zip having 3 root directories.
data (holds apps normaly)
META-INF (holds some kind of build files... and android manifest)
system (holds the OS and scripts and such.)
Also boot.img in the root dir.
The update.zip needs to be resigned if repackaged.
=) that is it all that I have gathered after hours of searching.
I dont want to recompile a kernel as I dont need to modify one. I would rather leave that to the more experienced DEVs. All I want is to remove/replace few apps...
My questions:
How do you sign a file... (tried the sign java thing in ubuntu and I get some king of error... could not find library and what not...)
There is a windows batch file floating around I have not tryed that.
I have some basic understanding of code language and I can flollow instructions even if I have to find my way around some stuff... but this rom building is like black magic... Everyone is doing it no one wants to explain how its done... If its too damn hard then so be it. I can modify it on the back end after installing. I just believe in clean simple installs.
What generates the META-INF directory and the files in there. Seems like there is some instructions on setting permissions for certain files and (manifest) seems like signiture keys..
Is that generated when the file is signed?
is it manualy generated?
is can those files be modified?
I know if this is answered it would be helpful in letting people optimize the builds for their own needs.
Sorry for the long post. I hope this gets explained or I dont care if I have to read, give me a bunch of homework (links).

zambezy said:
What about modding existing roms?
Here is what I know so far...
system apps are not individualy signed
Rom must be packaged in zip having 3 root directories.
data (holds apps normaly)
META-INF (holds some kind of build files... and android manifest)
system (holds the OS and scripts and such.)
Also boot.img in the root dir.
The update.zip needs to be resigned if repackaged.
=) that is it all that I have gathered after hours of searching.
I dont want to recompile a kernel as I dont need to modify one. I would rather leave that to the more experienced DEVs. All I want is to remove/replace few apps...
My questions:
How do you sign a file... (tried the sign java thing in ubuntu and I get some king of error... could not find library and what not...)
There is a windows batch file floating around I have not tryed that.
I have some basic understanding of code language and I can flollow instructions even if I have to find my way around some stuff... but this rom building is like black magic... Everyone is doing it no one wants to explain how its done... If its too damn hard then so be it. I can modify it on the back end after installing. I just believe in clean simple installs.
What generates the META-INF directory and the files in there. Seems like there is some instructions on setting permissions for certain files and (manifest) seems like signiture keys..
Is that generated when the file is signed?
is it manualy generated?
is can those files be modified?
I know if this is answered it would be helpful in letting people optimize the builds for their own needs.
Sorry for the long post. I hope this gets explained or I dont care if I have to read, give me a bunch of homework (links).
Click to expand...
Click to collapse
my advice for signing files would be to read through this thread. stericson says that JF's autosigning tool will work in linux. if you still can't get it pm stericson, he is a very nice member and should be able to help you

Thanks... That worked in windows.
Im getting some FC's but I can at least work on that now...
I did remove everything from the MANIFEST before signing just in case something did not get overwriten correctly.

I don't mess with the manifest files, so try not touching them and see if that helps

Can any body describe what does these files do while building a theme and how to edit these files:
android.policy.jar
framework.jar
services.jar
build.prop
build.sapphire.prop
build.trout.prop

sabin123 said:
Can any body describe what does these files do while building a theme and how to edit these files:
android.policy.jar
framework.jar
services.jar
build.prop
build.sapphire.prop
build.trout.prop
Click to expand...
Click to collapse
the prop files are configuration files and should NOT be replaced if your making a theme.
the .jar's should only be messed with if your adding stericsons lockscreen. you will have to decompile them for it to work

How to decompile the services.jar files?

Check out my theme thread. It's from when I was porting Android but most of these questions are explained in pretty good detail with links for more info. That should help you out quite a bit:
http://forum.xda-developers.com/showthread.php?t=578421
Go to the second post

Thanks for the link..

Editing 9.pngs unparsed error?

Okay, i need a little help, I try to add a 9.png to a sample app in eclipse so i can export it and have it show up corectly, however i get this error everytime i move the file into a drawable folder-
Description Resource Path Location Type
Unparsed aapt error(s)! Check the console for output. com_example_android_softkeyboard Unknown Android ADT Problem
This also makes it so i cannot export the apk, I have been reading and searching for a long time, but have no success.
I've followed the thread on how to edit 9.pngs also found on xda but i seem to have a problem not mentioned.
Any Help?
Shooot, i thought i was in a diffreent section my bad! Please move this!

How many other .9.png's do you have in that drawable folder? I found that if I had too many in one of the sample apk's that it would not compile. I finally just started a new one, and it hasn't let me down.

I only add one extra 9png file into the folder along with the already existing files in the folder (its a sample fromthe 2.1 sdk)

That error usually means that you have more than two stretching points on either the top of left side of the .9.png borders. Anything over two seperate points will seriously cause errors and won't let you compile. Fix it. and it'll compile.

Because you are making an app its different if you have never used it before check out draw9patch.bat in the SDK tools im sure google android wiki has something on it.
Best way to mod .9.png's is to just use the orig image and copy and paste your new stuff over old. I have been working with alot of .9.png images and this is easiest way to get around problems.
If you continue to have issues try compiling what you have without your mods maybe its the project itself.

[Q] Location of wpa_supplicant.conf on I9000 roms

Hi guys,
I've got a customer who is having a problem on my app which has to read wpa_supplicant.conf. Normally this file is located at /data/misc/wifi/wpa_supplicant.conf and requires root to read.
Anyways, according to the errors he's getting and based on his own exploration, his wpa_supplicant.conf file is not located there. I'm not sure which ROM he has (am waiting for a reply to that question now), but does anyone know if this file is normally located in /data/misc/wifi ?
Thanks,
James

Its not there on Darky 7.0 based on latest JPY firmware.
Search in progress ;]
/etc/wifi/wpa_supplicant.conf
and symlink
/system/etc/wifi/wpa_supplicant.conf

Thanks for the tip. On my customer's phone that file is just a template and not actually storing networks. I'll poke around in that ROM though. Thanks again.
Sent from my Nexus One using XDA App

Stock Froyo location is etc/wifi
jje

Looking at /system/etc/wifi/wifi.conf on Darky 7.0 I see the following
Code:
FIRMWARE_LOADER=wlan_loader
DRIVER_PROP_NAME=wlan.driver.status
SUPPLICANT_NAME=wpa_supplicant
SUPP_PROP_NAME=init.svc.wpa_supplicant
MODULE_FILE=/proc/modules
IFACE_DIR=/data/misc/wifi
DRIVER_MODULE_NAME=dhd
DRIVER_MODULE_TAG=dhd
FIRMWARE_LOADER=
[b]SUPP_CONFIG_TEMPLATE=/system/etc/wifi/wpa_supplicant.conf[/b]
SUPP_CONFIG_FILE=/data/wifi/bcm_supp.conf
DRIVER_MODULE_PATH=/lib/modules/dhd.ko
MFGDRV_MODULE_ARG=firmware_path=/system/etc/wifi/bcm4329_mfg.bin nvram_path=/system/etc/wifi/nvram_mfg.txt
DRV_AP_MODULE_ARG=firmware_path=/system/etc/wifi/bcm4329_aps.bin nvram_path=/system/etc/wifi/nvram_net.txt dhd_watchdog_ms=200 dhd_poll=1
DRIVER_MODULE_ARG=firmware_path=/system/etc/wifi/bcm4329_sta.bin nvram_path=/system/etc/wifi/nvram_net.txt dhd_watchdog_ms=10 dhd_poll=1
DRIVER_APS_FIRMWARE_NAME=bcm4329_aps.bin
DRIVER_STA_FIRMWARE_NAME=bcm4329_sta.bin
INTERFACENAME=eth0
WAPI_SUPPORT=false
[b]SUPP_CONF_FILEPATH=/data/misc/wifi/[/b]
SUPP_WAPI_AS_CERT_FILE_PATH=/data/misc/wifi/cert/as/
SUPP_WAPI_USER_CERT_FILE_PATH=/data/misc/wifi/cert/user/
SUPPLICANT_STATUS=wlan.supplicant.status
This tells me I would expect the conf file to be in /data/misc/wifi and the template to be in /system/etc/wifi.
Argh, this is very frustrating.

Code:
SUPP_CONFIG_TEMPLATE=/system/etc/wifi/wpa_supplicant.conf
is what you are after.
-(e)

Sweetlime, would you mind elaborating?
Do you see your networks in that file on your device?
On every device and ROM that I've been able to inspect that file is just the template and contains no specific network information.

Sorry I am an idiot I copied the wrong line, that should have read:
Code:
SUPP_CONFIG_FILE=/data/wifi/bcm_supp.conf

[null]

[Q] How to enable mass storage in CM 10.1 ?

Does anyone know how to enable USB Mass Storage on our phones under CM10.1? I've searched around and found this thread. But since I'm not familiar with changing build.prop I don't dare to do it myself. There are some CWM .zip files around to enable it, but they are on other phone's forums and I'm sure they just replace/change the build.prop so it's definitely not a good idea to flash those on a different phone than the ones they were intended for....
Long story short, does anyone know how to enable it on ours?
TIA!

Update on the process:
I was able to edit the build.prop according to the instructions, but that alone doesn't seem to do anything.
So I decided to try the next step, but where it tells me to do the changes below I wasn't sure what to do.
Thom75 said:
in framework-res.apk/res/xml/storage_list.xml
where oryginal line look like this:
Code:
<storage android:mountPoint="/storage/sdcard0" android:storageDescription="@string/storage_sd_card" android:primary="true" android:removable="true" android:maxFileSize="4096" />
after change look like this:
Code:
<storage android:mountPoint="/storage/sdcard0" android:storageDescription="@string/storage_sd_card" android:primary="true" android:removable="true" android:allowMassStorage="true" android:maxFileSize="4096" />
Click to expand...
Click to collapse
I was able to find the framework-res.apk file, copied to my computer and tried to open it with an XML editor... looked too complicated so I left it alone.
Does anyone know how to mess with that?

Open the .apk file with WinRar
-Drag the file you want to edit on your computer
-Edit the file on your computer
-Delete the old file in Winrar from the apk file
-Put the new file from your computer back in Winrar and save the "new" apk file
-Put the new .apk file on your smartphone
Before you install the new .apk file take a Root Explorer and look at the permissions of the old .apk file and set this permission on the new once...
I hope i could help you

Sivvis said:
Open the .apk file with WinRar
-Drag the file you want to edit on your computer
-Edit the file on your computer
-Delete the old file in Winrar from the apk file
-Put the new file from your computer back in Winrar and save the "new" apk file
-Put the new .apk file on your smartphone
Before you install the new .apk file take a Root Explorer and look at the permissions of the old .apk file and set this permission on the new once...
I hope i could help you
Click to expand...
Click to collapse
Thank you very much for your help! I didn't know apk files were just a compressed library of other files.
Now I am stuck trying to edit the "storage_list.xml" file... I tried to open with a few different xml editors, but could not get clean text like the example before. Any sugestions?
I attached the file below:

Apoena said:
Now I am stuck trying to edit the "storage_list.xml" file... I tried to open with a few different xml editors, but could not get clean text like the example before. Any sugestions?
Click to expand...
Click to collapse
Well, how about decompiling the .apk file with APK Tools instead of just opening it with WinRar? :laugh:
Yes, now I get a clean, editable, decompiled xml file.
I'll try editing both when I get home tonight and will post the results.

I guess this is a problem because of the emulated layout. There is a trick with setprop sys.usb.storage.config mass_storage but it does not work.
Keep me informed if you find something valuable (i'm on original CM10.1, latest nightly 0423 actualy).

Ok, here's the update from last night:
I started over since I flashed the nightly, which is good so I restarted with a clean slate.
- Edited build.prop - OK
- Copied framework-res.apk to my computer
- Decompiled framework-res.apk
- Edited storage_list.xml
- Recompiled framework-res.apk with new storage_list.xml
- Copied framework-res.apk back to my phone
- Deleted original framework-res.apk
- ...... instant restart & bootloop before I could paste the new framework-res.apk in its place
No big deal, just restored a nandroid backup I made before messing with anything and I'm back in business.
Apparently you can't mess with the framework-res.apk while your phone is on (with the OS running)... so now I need to research the right way to push/pull these files from ADB while on CWM recovery. I appreciate if someone could point me in the right direction since I'll be busy at work today.
To be honest, my gut feeling tells me that this is not going to work anyway. But look at what I learned so far... two days ago I wouldn't even think of compiling/decompiling anything... this is what XDA is all about, right?

Imho, the framework_res.apk and various tricks are all enabling or disabling a sys.usb.storage.config key. I'm not understanding nor finding informations about CM10.1 emulated layout, and if there are any reasons to forbid mass storage (because, yes, it seems it is disabled because it is not compatible).
This is something i have hard time with. On Android, you have tons of improvement for rom or kernel XY, but generally undocumented. If you apply this 'per device', the information is very fragmented and difficult to grab.
I was looking for a simple brief on base MTD partitions layout for LG P880, it seems the only way to have this is to dig KDZ files. Perhaps a Wiki would help the wannabe contributers like me to start ?

Any Solution For This Problem ??? I Can't Transfer Any Files To My O4X , What's The Point Of Cyanogenmod Then ??????????????

Nooby305 said:
Any Solution For This Problem ??? I Can't Transfer Any Files To My O4X , What's The Point Of Cyanogenmod Then ??????????????
Click to expand...
Click to collapse
Flash the latest nightly. MTP is working and you cab transfer files that way.
Sent from my tree using a ladder

effectively, if you are flashing for USM, you should stay on LG stock.

I know that the topic got a little old but I'd like to refresh it since more people (e.g. Ubuntu users) could be interested in enabling Mass Storage.
What I've done is:
1) pulled /system/framework/framework-res.apk
2) decompiled it with APKtool
3) added
Code:
android:allowMassStorage="true"
in storage_list.xml
4) builded a new apk
then I've rebooted my phone into recovery and (@Apoena you may be interested in it - there is a possibility to access /system through adb connected with phone in recovery mode) pushed the new framework-res.apk. I've also changed the entry in build.prop to
Code:
persist.sys.usb.config=mass_storage,adb
Everything seemed fine until I've tried to reboot the phone: instead of CM boot logo I got a black screen. Anybody has an idea what went wrong (maybe something during recompilation of the apk)?
And of course sorry for any language mistakes, I'm not a native speaker

How to fix bluetooth on cm13 (Or any other rom)/ How to fix amazon jem not recognized

Hello guys, I'm here to show you how to fix it without repeatedly turning it on and off. (I provided the stock bluetooth for you guys, that don't have it)
This is only for LTE jem, sorry for any convenience. (For bluetooth.)
1. Download this https://www.dropbox.com/s/29pw4nm27pgl8aj/Bluetooth fix.rar?dl=0
2. Extract it.
3. Replace /System/etc/Bluetooth/bcm2076_20mhz.hcd with BCM2076_26MHZ.HCD
4. Replace /System/vendor/firmware/bcm2076_20mhz.hcd with bcm2076_20mhz.hcd (The one I provided for you)
Then tada! Bluetooth works, you can only connect to compatible devices it seems but bluetooth finally works.
Now onto how to fix amazon jem not being recognized, on your pc/laptop.
I'm going to be honest here, this will be very short lol.
So anyways, go to this link https://windows10skill.com/kindle-fire-not-recognized-on-windows-10/#2 and follow the steps provided. Method 2 helped me, so try that first if you want. (This can work on windows 7 too, I forgot where I found it at but you can try following it still.)
That's all I have, for now. I hope all of you guys get everything fixed! Please let me know if this was helpful for you, I would appreciate it.

This RAR file won't open

Out of curiosity, I tried this with the latest CRdroid 3.8.7 from @transi1 in the other thread (which is useless because the ROM has functional bluetooth out of the box, at least with keyboards and mice). I was able to download and unpack the RAR, and install the files as described (had to remount /system for read-write in an adb shell in order to write in those directories). However, after replacement, the bluetooth didn't work any more, completely dead. When I restored the original files, it started working again. Maybe this is only for the LTE variant of the Jem (which reportedly has another Bluetooth chipset)?
EDIT : I checked that the HCD file above differs from the original one built into the ROM.

bapi28 said:
Out of curiosity, I tried this with the latest CRdroid 3.8.7 from @transi1 in the other thread (which is useless because the ROM has functional bluetooth out of the box, at least with keyboards and mice). I was able to download and unpack the RAR, and install the files as described (had to remount /system for read-write in an adb shell in order to write in those directories). However, after replacement, the bluetooth didn't work any more, completely dead. When I restored the original files, it started working again. Maybe this is only for the LTE variant of the Jem (which reportedly has another Bluetooth chipset)?
EDIT : I checked that the HCD file above differs from the original one built into the ROM.
Click to expand...
Click to collapse
Oh my god, I'm so sorry I forgot to mention this is only for lte devices. Sorry!

Understood step 4. But on step 3 when it states replace a file with a file having a different name, does that mean 1) delete original file and put new file in that folder, or 2) rename new file to existing files name and copy over top of existing file replacing it?

Ok, answered my own question and figured it out.
I did not have such a file in the /System/etc/Bluetooth folder.
I renamed the 26mhz file to 20mhz and replaced (overwrote) the file in the /System/vendor/firmware folder.
It is working great finally after issues for the past few years. Awesome. Thanks.