Hello @all,
i'm trying to port Firefox OS on my P500, but actually im kind of stuck in creating the proper manifest file. I've got the armv6 cm repo running and building without error from https: // androidarmv6.github.io/.
So as i understand it the hard part is to create a working manifest.xml file for Firefox OS. I'm using this guid https: // developer.mozilla.org/en-US/Firefox_OS/Porting but unfortunately it is missing the whole part in how to transform a working CM manifest into a working Firefox OS manifest.
Here are the working CM manifest:
https: // gist.github.com/delijati/40823071d200bba422b9
https: // gist.github.com/delijati/1c71b8045710e6c81692
So if someone can give me a hint, that would be great.
Thanks
------------------------------------------------------------------------------------------------------------
Just remove the blank and the links are working
Related
Hi,
I have added the following code on my local AOSP copy (master branch) and it starts up fine but the .mp3 is not playing. After putting more logging message and looking at the logcat I notice that the code didn't continue after calling the MediaPlayer() class
mPlayer = new MediaPlayer();
if (mPlayer == NULL) {
ALOGE("Failed to create MediaPlayer()\n");
return false;
}
Anybody has any experience troubleshooting this or have successfully implemented this gerrit issue ?. I'm testing it using Nexus 7 (grouper).
I cannot post the link to this post so I'm going to spell the link to the gerrit issue out
android-review.googlesource.com slash # slash c slash 38222 slash
Cheers
Not sure how well this works now, I have not messed with the boot sounds in a while now.
https://github.com/lithid/Scripts/blob/master/Android/bootsound.sh
I used to be able to get the boot sounds working with this script I wrote.
lithid-cm said:
....I used to be able to get the boot sounds working with this script I wrote.
Click to expand...
Click to collapse
Thanks lithid-cm.
I managed to make it work, the problem was because the bootanimation.zip contains only .mp3 it should contain the bootanimation logo. I've made a short demo video of using the CyanogenMod logo on an AOSP
youtube.com <slash> watch <question mark> v <equal sign> b0uuHlrJpGI
Hi guys, i'm a newb at this but i wanna port and test firefox os to my galaxy ace 5830.....i'm stuck at :
Create the manifest file for the new device
Now you need to add the required repos to the manifest file for the new device; this manifest file is called default.xml. Refer to the b2g-manifest file on github for a template. Each device has its own branch; you can use the galaxy-s2 branch as a reference.
My question is do i git clone the fork i have of the b2g/manifest and edit the galaxy-s2.xml file to reflect the ace or what? I don't have the default.xml in my B2G folder......
dantheman1977 said:
Hi guys, i'm a newb at this but i wanna port and test firefox os to my galaxy ace 5830.....i'm stuck at :
Create the manifest file for the new device
Now you need to add the required repos to the manifest file for the new device; this manifest file is called default.xml. Refer to the b2g-manifest file on github for a template. Each device has its own branch; you can use the galaxy-s2 branch as a reference.
My question is do i git clone the fork i have of the b2g/manifest and edit the galaxy-s2.xml file to reflect the ace or what? I don't have the default.xml in my B2G folder......
Click to expand...
Click to collapse
Hi there,
im very interested in your project.
Did you getting through in the meantime?
To creating a manifest, you should use one from other device and edit it.
The best is Galaxy S II.
After this, you should open the manifest with gedit or any other editors.
Replace Galaxy S II device trees with yours and save the file as "default.xml" in directory that contains "build.sh".
Make an exact copy from your manifest and rename it to "<device_codename>.xml" for example "maguro.xml" for Galaxy Nexus Intl. or "i9082.xml" for Galaxy Grand Duos.
Now, open config.sh.
Copy one of the options in "case $1" section and use it as your template and add your device to it, like this:
Code:
"i9082")
echo DEVICE=i9082 >> .tmp-config &&
repo_sync $1
;;
Device variable is your device codename and name of your copied manifest file.
Note: this is for i9082 galaxy grand duos, you should edit it to yours.
Now, you can get the source using
Code:
ANDROIDFS_DIR=my_device_backup ./config.sh <device_codename> default.xml
Reference: "developer.mozilla.org/en-US/docs/Mozilla/Firefox_OS/Porting"
interesting..!!
dantheman1977 said:
Hi guys, i'm a newb at this but i wanna port and test firefox os to my galaxy ace 5830
Click to expand...
Click to collapse
Would definitely like to see this project being developed.
gonna keep an eye on this...
Good Luck
Good luck bro
dantheman1977 said:
Hi guys, i'm a newb at this but i wanna port and test firefox os to my galaxy ace 5830.....i'm stuck at :
Create the manifest file for the new device
Now you need to add the required repos to the manifest file for the new device; this manifest file is called default.xml. Refer to the b2g-manifest file on github for a template. Each device has its own branch; you can use the galaxy-s2 branch as a reference.
My question is do i git clone the fork i have of the b2g/manifest and edit the galaxy-s2.xml file to reflect the ace or what? I don't have the default.xml in my B2G folder......
Click to expand...
Click to collapse
It's 2014 . Any news about Firefox os on galaxy ace. This phone needs it. Firefox os is build for low end devices
dantheman1977 said:
Hi guys, i'm a newb at this but i wanna port and test firefox os to my galaxy ace 5830.....i'm stuck at :
Create the manifest file for the new device
Now you need to add the required repos to the manifest file for the new device; this manifest file is called default.xml. Refer to the b2g-manifest file on github for a template. Each device has its own branch; you can use the galaxy-s2 branch as a reference.
My question is do i git clone the fork i have of the b2g/manifest and edit the galaxy-s2.xml file to reflect the ace or what? I don't have the default.xml in my B2G folder......
Click to expand...
Click to collapse
This is inspiring. Imma start porting to some devices tomorrow
Hello all! I have downloaded and successfully build the AOSP for marshmallow (android-6.0.1_r79). Than I made some changes to the stockkeyboard (regarding to my other topic, but not relevant here). The file which I modified was this here:
packages/inputmethods/LatinIME/java/src/com/android/inputmethod/latin/LatinIME.java
I compiled the code and it was successfull too. But than I realize I face some problems.
I mounted the system.img and get into the path: /system/app/LatinIME/
I decompiled the app (jadx, apktool) to check if the modification there is available and here is the problem
This APK does not contain any Java sources?! Its just xml regarding to the layout. When I replace my old Stockkeyboard with this one, it is still perfectly working? So I got not clue whats going on.
Question regarding to this topic are:
How can I make a modification to the stock keyboard LatinIME
Building this new AOSP image with the new keyboard
And extracting the new keyboardj(APK) out of this image to install it on my device (Root permissions are of course available)
What I have tryed:
Modyfing the following Java file: packages/inputmethods/LatinIME/java/src/com/android/inputmethod/latin/LatinIME.java
Compiling the complete project (make -j4 and just the keyboard: make -j LatinIME)
Replacing my own keyboard with the modified stock keyboard
My steps are as described not working. The keyboard appears and its working but the modification seems to be missing. Also by decompiling it, there are no Java sources within it.
I am relly glad for any help to this topic! Thank you!
Hi,
I'm working on a native application that display the chipsetID.
When i test with a simple application HelloWorld and compile using ndk-build, it work and i found the apk under system/bin. But when i include nexus header,it generate errors "File not found" .
Best Regards.
Hey everyone,
Due to the lockdown in my country I have to stay home. What a better way to do this than working on a project right ?
The idea is to create a simple launcher with the basic functionnality :
having an app drawer
home screen with dock
possibility to create folder on homescreen
possibility to remove app / folder from homescreen
bonus : possibility to add icon pack
You see, very basic as I said.
I started from scratch, but yesterday I asked on Lawnchair's community telegram and someone talked to me about Launcher3.
I didn't know this launcher and I discovered that a lot of launcher are based on Launcher3, they are all a fork from it.
This motivate me to do a fork to.
But I have a lot of problems to build the launcher itself. I clone the project, open it with Android Studio and I have errors from gradle, when I fix them I have other errors. I think I'm doing wrong but I searched online and I don't find any ressources that can help to start this project or give me clues to understand better.
I am a beginner in Android dev, but trust me I have a really strong motivation I don't want to hear "This is to difficult for you mate, try something else"
Thank you for reading me
hello, you means you want to make a personal launcher project base on launcher3. so now what's your problem in make it build success?
Based on our previous experience, may be has fllow steps:
1.you need a aosp source(or you already have other rom code choose, it's ok), and build it;
2.get the framework.jar from the out path intermediates (for launcher3 has many class only system framework contain);
3.copy launcher3 code from aosp source to your owner path, and make an Android studio project;
4.copy the second step framework.jar to the launcher3 Android studio project(you can put it under app/libs/) and just compileOnly the framework.jar(we just need to declare some system class for compile, finally when the app work it still base on different devices owner framework in the system);
5.add flowing code in you build.gradle:
gradle.projectsEvaluated {
tasks.withType(JavaCompile) {
options.compilerArgs << '-Xbootclasspath/p:libs/framework.jar'
}
}
6.if you have a some v7 package implements may be some time will show you some <attr> conflict, like <attr name="icon"> conflict, just change it to <attr name="icon" format="string"> is ok.
Under normal conditions，above steps can help you to make your launcher3 project work well in AS, and also you can compare some open source in github, there has some launcher3 AS project. hope to work for you, if not work for you, you can show the error message you meet more detail, may be we can help to found out the problem
Bro I think you can use jadx decompiler and any working laucher3 to show their source code. Learn from it how the stuffs work. Then start a new project from scratch in Android Studio.. Modify for your own needs.
walker ice said:
hello, you means you want to make a personal launcher project base on launcher3. so now what's your problem in make it build success?
Based on our previous experience, may be has fllow steps:
1.you need a aosp source(or you already have other rom code choose, it's ok), and build it;
2.get the framework.jar from the out path intermediates (for launcher3 has many class only system framework contain);
3.copy launcher3 code from aosp source to your owner path, and make an Android studio project;
4.copy the second step framework.jar to the launcher3 Android studio project(you can put it under app/libs/) and just compileOnly the framework.jar(we just need to declare some system class for compile, finally when the app work it still base on different devices owner framework in the system);
5.add flowing code in you build.gradle:
gradle.projectsEvaluated {
tasks.withType(JavaCompile) {
options.compilerArgs << '-Xbootclasspath/p:libs/framework.jar'
}
}
6.if you have a some v7 package implements may be some time will show you some <attr> conflict, like <attr name="icon"> conflict, just change it to <attr name="icon" format="string"> is ok.
Under normal conditions，above steps can help you to make your launcher3 project work well in AS, and also you can compare some open source in github, there has some launcher3 AS project. hope to work for you, if not work for you, you can show the error message you meet more detail, may be we can help to found out the problem
Click to expand...
Click to collapse
Hey,
Thank you for your answer. I clone launcher 3 from here : ht tps:// android.googlesource.com/ platform/ packages/ apps/ Launcher3
But I can built it on android studio, am I doing it wrong ? (I'm on Windows 10 btw)
I open the folder Launcher3 (from which I cloned) and AS ask me for gradle location ...
Thanks again.