Database Develop

[DEV] Adding your ROM to ROM Manager

It's easy, it's free. And here's how you do it!
You will need to create two simple JavaScript files:
A file that describes your ROMs that you send to me.
A file that you host that lists your ROMs, so you can update your ROM Manager section.
First, your developer/ROM description file:
Code:
{
// This is what name you want your ROMs to show up under.
developer: "CyanogenMod",
// Your id. This should have no spaces or other funny characters.
// This would ideally be your Github id, so when you send me your manifest
// I can verify who you are. But it can be anything really.
id: "cyanogen",
// The display summary. Two lines max.
summary: "Mods and bacon for Dream, Sapphire, Droid, and Nexus One",
// The location of the developer's manifest.
manifest: "http://gh-pages.clockworkmod.com/ROMManagerManifest/cyanogenmod.js",
// The list of devices that this developer's ROMs support.
// If you don't support a device, just don't list it!
roms:
{
vibrant: true,
sholes: true
}
}
Send me that file! [email protected]
Link to developer sample: http://gh-pages.clockworkmod.com/ROMManagerManifest/samples/developer.js
And now, create your ROM list file:
Code:
{
// The version of the manifest, so ROM Manager knows how to load it
version: 1,
// The homepage for your ROM, if you have one.
homepage: "http://www.cyanogenmod.com/",
// The donate link for yuor ROM, if you have one.
donate: "https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=3283920",
// Your list of ROMs
roms:
[
{
// Display name of the rom
name: "CyanogenMod 5.0.5",
// Display summary of the rom
summary: "Stable",
// Device that this rom runs on
device: "sholes",
// This is the download URL of your ROM.
// These URLs should have unique filenames per version!
// Ie, don't use a zip with the same name
// as that of a previous version with a new version.
// Otherwise ROM Manager will continue using the
// old cached zip on the SD card.
// This must be a direct download,
// and not a Mediafire type link.
url: "http://www.droidaftermarket.com/koush/motorola/sholes/cyanogen_sholes-ota-eng.koush_5.0.5.zip"
},
// Antother, older ROM!
{
name: "CyanogenMod 5.0.4",
summary: "Stable",
device: "vibrant",
url: "http://www.droidaftermarket.com/koush/motorola/sholes/cyanogen_sholes-ota-eng.koush_5.0.4.zip"
}
]
}
Link to manifest sample: http://gh-pages.clockworkmod.com/ROMManagerManifest/samples/simplemanifest.js
And you're done!
If you're a pro dev, you can even create a ROM customizer. But I won't get into that here
Follow this link for more information: http://www.koushikdutta.com/2010/03/rom-manager-and-third-party-roms.html

Excellent thanks Koush!!

very nice, I love koush lol

Nice
Sent from my SGS Vibrant using tapatalk

Damn Kouch, you seem to be making all this pretty easy for everyone. I'm new to all this rooting stuff, and I've gotta say you've got me really excited about all this. I paid for your Clockwork app to show my support for your hard work, and time you've put into this. Can't wait to see what ROMs hit the Vibrant within the next few weeks!
Thanks!

how can i rebuild 'libhtcgeneric-ril.so'?

previous i posted about korean sms.. but no response.
So i can find a way rebuild '.so' file. but i couldnt..
i must add this code in libhtcgeneric-ril.so
msg = new String( inData, "KSC5601" );
'----------------------------------------------------------
void decode_cdma_sms(char *pdu, char *from, char *message, int *is_vm,int *msg_len) {
unsigned int i=1;
int code,length;
strcpy(from,"000000"); // in case something fails
strcpy(message,"UNKNOWN");
if (is_vm)
*is_vm = 0;
while(i*2<strlen(pdu)) {
get_code_and_length(pdu+i*2,&code,&length);
if(code==2) // from
decode_number(pdu+i*2+4,length,from);
if(code==8) // bearer_data
// probably code add. msg = new String( inData, "KSC5601" );
decode_bearer_data(pdu+i*2+4,length,message,is_vm,msg_len); i+=length+2;
}
}
please.. help me.

You need to have an Android source tree to rebuild any components. The xdandroid guide would be the quickest:
http://xdandroid.com/wiki/Getting_the_Source
Any rebuilds of the RIL need to be placed in /lib/froyo/ of the rootfs rather than /system/lib where Android puts it.
BTW htcgeneric-ril.so is C, while the line you want to add is Java. Are you sure thats the right place to patch it?

Thanks Tremere.
Tremere said:
You need to have an Android source tree to rebuild any components. The xdandroid guide would be the quickest:
http://xdandroid.com/wiki/Getting_the_Source
Any rebuilds of the RIL need to be placed in /lib/froyo/ of the rootfs rather than /system/lib where Android puts it.
BTW htcgeneric-ril.so is C, while the line you want to add is Java. Are you sure thats the right place to patch it?
Click to expand...
Click to collapse
i am newbie in C and java.
So i can not figure out this code is wrong.
i am sure that postion of code is right.
but just android source is download and make then compile is complete ?
must compile whole android source but only 'libhtcgeneric-ril.so' ?
that's too difficult to me. i am newbie at linux, C .

Sorry i am totally wrong.
thas is too difficult.
mmmmm......
I am give up..

Theme Chooser themes, Windows, aapt, and uppercase letters in XML filenames

EDIT: A solution has been found, courtesy of XDA member titanic_fanatic, who compiled a Windows version of aapt that accepts uppercase letters in XML filenames! (Read his original message here.) I've attached it to this post. One of the biggest hurdles to effective theme creation in Windows is finally solved!
----------------------------------------------------------------------------------------​
Forgive me if this has already been asked, but I know that it's something that's annoyed theme developers under Windows for a while now. I seem to recall seeing hints about fixing this, but I've done search after search, and can't find it to save my life.
Theme Chooser theme developers under Windows are hobbled by the fact that XML filenames can't contain uppercase letters, which prevents us from theming certain applications (example: com_keramidas_TitaniumBackup.xml would be needed for Titanium Backup). I know that this is a problem related to aapt.exe. Has anyone come up with a workable solution for this issue? If not, I'd like to take a crack at it. I might not get anywhere, but I have nothing to lose.
Obviously, in order to do this, I'll need the source for it. I can do the heavy lifting regarding getting the source and working out how to compile it for Windows, but I need to know where the source is, what to get, and other requirements. If anyone can help and point me in the right direction(s), I'd really appreciate it!

MJPollard said:
Forgive me if this has already been asked, but I know that it's something that's annoyed theme developers under Windows for a while now. I seem to recall seeing hints about fixing this, but I've done search after search, and can't find it to save my life.
T-Mobile/CM7 theme developers under Windows are hobbled by the fact that XML filenames can't contain uppercase letters, which prevents us from theming certain applications (example: com_keramidas_TitaniumBackup.xml would be needed for Titanium Backup). I know that this is a problem related to aapt.exe. Has anyone come up with a workable solution for this issue? If not, I'd like to take a crack at it. I might not get anywhere, but I have nothing to lose.
Obviously, in order to do this, I'll need the source for it. I can do the heavy lifting regarding getting the source and working out how to compile it for Windows, but I need to know where the source is, what to get, and other requirements. If anyone can help and point me in the right direction(s), I'd really appreciate it!
Click to expand...
Click to collapse
Hmm .. + 1 with you .. but the only way is ... ask brut.all ....
Sent from my Galaxy Nexus using XDA App

qazsxdcfv said:
Hmm .. + 1 with you .. but the only way is ... ask brut.all ....
Click to expand...
Click to collapse
Thanks, I guess I'll have to after all (not that I mind doing it). Over 250 views and only one person to respond isn't giving me much hope that someone has an answer.

Have you found a solution for windows ?

Any solution?

Randomly came across this thread looking for info on compiling the aapt binary for Windows. I'm still looking for the answer for that but I do know the change that needs to be made and how to do that part, as I have already done this mod for aapt on Linux. You have to have a full build environment set up, and by that I mean set up to build a full ROM, like CM10 for example. The change to make is in the frameworks source code at frameworks/base/tools/aapt/Resource.cpp.
See this commit for the details:
http://review.cyanogenmod.org/#/c/24204/
Add the parts I highlighted in blue to the two lines below:
Code:
String16 baseName(it.getBaseName());
const char16_t* str = baseName.string();
const char16_t* const end = str + baseName.size();
while (str < end) {
if (!((*str >= 'a' && *str <= 'z')
[COLOR="RoyalBlue"][B]|| (*str >= 'A' && *str <= 'Z')[/B][/COLOR]
|| (*str >= '0' && *str <= '9')
|| *str == '_' || *str == '.')) {
fprintf(stderr, "%s: Invalid file name: must contain only [a-z[COLOR="RoyalBlue"][B]A-Z[/B][/COLOR]0-9_.]\n",
it.getPath().string());
hasErrors = true;
}
str++;
}

m4570d0n said:
Randomly came across this thread looking for info on compiling the aapt binary for Windows. I'm still looking for the answer for that but I do know the change that needs to be made and how to do that part, as I have already done this mod for aapt on Linux. You have to have a full build environment set up, and by that I mean set up to build a full ROM, like CM10 for example. The change to make is in the frameworks source code at frameworks/base/tools/aapt/Resource.cpp.
See this commit for the details:
http://review.cyanogenmod.org/#/c/24204/
Add the parts I highlighted in blue to the two lines below:
Code:
String16 baseName(it.getBaseName());
const char16_t* str = baseName.string();
const char16_t* const end = str + baseName.size();
while (str < end) {
if (!((*str >= 'a' && *str <= 'z')
[COLOR="RoyalBlue"][B]|| (*str >= 'A' && *str <= 'Z')[/B][/COLOR]
|| (*str >= '0' && *str <= '9')
|| *str == '_' || *str == '.')) {
fprintf(stderr, "%s: Invalid file name: must contain only [a-z[COLOR="RoyalBlue"][B]A-Z[/B][/COLOR]0-9_.]\n",
it.getPath().string());
hasErrors = true;
}
str++;
}
Click to expand...
Click to collapse
Thank you for your help but could you tell me where can I find frameworks/base/tools/aapt/Resource.cpp?
I don't understand where to find it?

Sorry to resurrect an old thread, but I've finally come across a Windows version of aapt.exe that accepts uppercase letters in XML filenames, courtesy of XDA user titanic_fanatic. I've modified the first post in the thread with the details. Happy theming!

MJPollard said:
Sorry to resurrect an old thread, but I've finally come across a Windows version of aapt.exe that accepts uppercase letters in XML filenames, courtesy of XDA user titanic_fanatic. I've modified the first post in the thread with the details. Happy theming!
Click to expand...
Click to collapse
That link does seem to work anymore (and the webpage gives malware warning in Norton).
Does anyone else have this file?

Error during kernel cross compiling.

Ok I am trying to compile a kernel for S5830 but everytime I use make clean && make mrproper command it gives me the error displayed in the screenshot. This is the first time I am compiling a kernel so please forgive my noobness if any. I am using Fedora 20 with ndk version r10b 64bit. Need Help.Thanx
I have installed ncurses-devel but still the same problem.

anyone??

Mandark52 said:
Ok I am trying to compile a kernel for S5830 but everytime I use make clean && make mrproper command it gives me the error displayed in the screenshot. This is the first time I am compiling a kernel so please forgive my noobness if any. I am using Fedora 20 with ndk version r10b 64bit. Need Help.Thanx
I have installed ncurses-devel but still the same problem.
Click to expand...
Click to collapse
I haven't much experience with it, but maybe @Mardon could give you a hand

Hello,
You have to make 4 small changes:
drivers/Makefile:
Search this line:
Code:
obj-$(CONFIG_RFS_FSR)
replace it with:
Code:
#obj-$(CONFIG_RFS_FSR)
Search this line:
Code:
obj-$(CONFIG_MSM_PARAM) += param/
replace it with:
Code:
#obj-$(CONFIG_MSM_PARAM) += param/
drivers/Kconfig
Search this line:
Code:
# for FSR
source "drivers/fsr/Kconfig"
replace it with:
Code:
# for FSR
#source "drivers/fsr/Kconfig"
Search this line:
Code:
source "drivers/param/Kconfig"
replace it with:
Code:
#source "drivers/param/Kconfig"

Mm7 said:
Hello,
You have to make 4 small changes:
drivers/Makefile:
Search this line:
Code:
obj-$(CONFIG_RFS_FSR)
replace it with:
Code:
#obj-$(CONFIG_RFS_FSR)
Search this line:
Code:
obj-$(CONFIG_MSM_PARAM) += param/
replace it with:
Code:
#obj-$(CONFIG_MSM_PARAM) += param/
drivers/Kconfig
Search this line:
Code:
# for FSR
source "drivers/fsr/Kconfig"
replace it with:
Code:
# for FSR
#source "drivers/fsr/Kconfig"
Search this line:
Code:
source "drivers/param/Kconfig"
replace it with:
Code:
#source "drivers/param/Kconfig"
Click to expand...
Click to collapse
Well I changed the code in drivers/makefile but the code in drivers/Kconfig was the same so no need to replace that one. After that I got this....

Mandark52 said:
Well I changed the code in drivers/makefile but the code in drivers/Kconfig was the same so no need to replace that one. After that I got this....
Click to expand...
Click to collapse
OK:
fs/Makefile
replace this
Code:
obj-$(CONFIG_RFS_FS) += rfs/
with
Code:
#obj-$(CONFIG_RFS_FS) += rfs/
fs/Kconfig
replace this
Code:
source "fs/rfs/Kconfig"
with
Code:
#source "fs/rfs/Kconfig"

Mm7 said:
OK:
fs/Makefile
replace this
Code:
obj-$(CONFIG_RFS_FS) += rfs/
with
Code:
#obj-$(CONFIG_RFS_FS) += rfs/
fs/Kconfig
replace this
Code:
source "fs/rfs/Kconfig"
with
Code:
#source "fs/rfs/Kconfig"
Click to expand...
Click to collapse
everything that you mentioned was as it was i.e. it was not commented in the fs/makefile and kconfig.

You should comment
Code:
obj-$(CONFIG_RFS_FS) += rfs/
and
Code:
source "fs/rfs/Kconfig"

Mm7 said:
You should comment
Code:
obj-$(CONFIG_RFS_FS) += rfs/
and
Code:
source "fs/rfs/Kconfig"
Click to expand...
Click to collapse
Still no luck. I guess you are very close in solving this.

You have to select a config or create one from scratch.
The base configuration for Galaxy Ace (cooper) is cooper_rev03_defconfig, I strongly raccomand you to use it.
So, If you want use it as is:
Code:
export ARCH=arm
make cooper_rev03_defconfig
and then you can build the kernel
Code:
make
Instead If you want customize it:
Code:
export ARCH=arm
make cooper_rev03_defconfig
make menuconfig
After changing, you can run the build:
Code:
make
If you want to create a new config from scratch:
Code:
make menuconfig
and then you can build the kernel:
Code:
make
P.S.: In your screenshot you mispelled "mrpropper" for "mrproper"

Mm7 said:
You have to select a config or create one from scratch.
The base configuration for Galaxy Ace (cooper) is cooper_rev03_defconfig, I strongly raccomand you to use it.
So, If you want use it as is:
Code:
export ARCH=arm
make cooper_rev03_defconfig
and then you can build the kernel
Code:
make
Instead If you want customize it:
Code:
export ARCH=arm
make cooper_rev03_defconfig
make menuconfig
After changing, you can run the build:
Code:
make
If you want to create a new config from scratch:
Code:
make menuconfig
and then you can build the kernel:
Code:
make
P.S.: In your screenshot you mispelled "mrpropper" for "mrproper"
Click to expand...
Click to collapse
That worked for me!!!

Creating xslx.-File in Android

Hi Guys,
I want to create a xslx-File in my Android Application. Im Using Apache poi-ooxml-3.12.jar for it. But while calling the XSSFWorkbook Constructor I get the following exception:
FATAL EXCEPTION: main
Code:
java.lang.VerifyError: org/apache/poi/xssf/usermodel/XSSFWorkbook
This is my Code (HSSFWorkbook Constructor is working btw):
Code:
Workbook workbook;
if (StringOperationsUtil.getFileExtension(file).equalsIgnoreCase("XLSX")){
workbook = new XSSFWorkbook();
} else {
//default xls
workbook = new HSSFWorkbook();
}
These are my gradle dependencies:
Code:
dependencies {
compile fileTree(include: ['*.jar'], dir: 'libs')
compile 'com.android.support:appcompat-v7:21.0.3'
compile 'com.opencsv:opencsv:3.4'
compile 'org.apache.poi:poi:3.12'
compile 'org.apache.poi:poi-ooxml:3.12'
compile 'com.android.support:multidex:1.0.0'
}
Also the apache team didn't answer me. I can't believe that it's not possible to create the newest excel file in an android application. Does really any Android Developer is not using xlsx files? I really can't believe this. Please let me know, if you guys know something about that issue.
Thanks in advance!

I tried to use the older poi.jar 3.8 and now i get this error:
Error:Execution failed for task ':app:dexDebug'.
> com.android.ide.common.internal.LoggedErrorException: Failed to run command:
G:\android-sdk\build-tools\21.1.2\dx.bat --dex --no-optimize --multi-dex --main-dex-list G:\Development\workspace\FPT\app\build\intermediates\multi-dex\debug\maindexlist.txt --output G:\Development\workspace\FPT\app\build\intermediates\dex\debug --input-list=G:\Development\workspace\FPT\app\build\intermediates\tmp\dex\debug\inputList.txt
Error Code:
1
does anybody know how i fix this?
thanks