Dear experts,
like many ppl, I am new to Android Development, and would be able to cook my own rom with amazing home-made features before the end of the week... and I want it to be easy, funny, and eventually Fast....
... Indeed, I don't want all of this, so I'll try to be realistic in my incoming questions and beg for your indulgence if some things sound stupid / inexact / already documented and so on : I have performed a long search process before I decided to post here and would not ask it otherwise.
So, first, here's what I have know about android:
- Android Architecture (various layers)
- Android + java programming (beginner with both but skilled with general OOP and smartphone -iPhone- programming)
- Rom flasing process : rooting, bootloader / recovery flashing , using adb, filesystem of a ROM
- Android official source building (from git repository) and patch apply.
- Basic cooking without any source code modification: use of dsixda's kitchen with xda members' home-made roms mainly
Then, the material I am working with :
- Max OS 10.6.5
- A HTC - Tattoo : rooted, with nandroid and busybox installed (also have an available HTC - Hero)
- adb 1.0.26
- HTC Android Kitchen 0.106 - by dsixda
- Android official source from http://android.git.kernel.org/
Now, what I don't know about is advanced cooking... I read a lot about ppl wondering the same, and generally there was no basic answers (not to mention guide/tutorials).
Since I will surely be the nth to ask this, let's try to ask a specific question.
I downloaded from Android github a patch I am very interested in. This patch applies on the framework and does not impact any other layer (especially not the kernel nor the hardware related libs). After building the source, I thus get a framework.jar I would like to replace some target framework.jar with .
I was quite sure it was not very bright to do such with a custom ROM, even a quite standard FroYo-based one, since there was little chance that such a cooked-rom used a virgin framework taken as-it from android github. But I tried anyway with some of the FroYo-based roms taken from the xda list for my tattoo device. I basicely replaced the framework.jar with mine.
... and indeed, it failed : I kept getting stuck at the boot screen everytime I do such.
So.... I am trying to understand what I do wrong.
- I am quite sure I miss some signing process, but although I read many threads about such a signing about apk files, I did not manage to figure out how to do this with frameworks / jar files. Could someone bring me some light about this?
- Provided the signing is not the (only) problem here, could someone explain where / why I am wrong?
- Eventually, since I did not manage to find full source for a FroYo-based (running) cooked rom , do you know of such a source repository I could work with instead of working with android official sources (including the framework java files + compatible with HTC-tattoo / HTC-hero if possible)?
Thanks for all of you for reading until here, whatever your answers (or silence) may be.
And thanks in advance to those who may have some answers or any constructive criticism.
Roger_Rabbit
--------------------------
An old fashioned rabbit
Good day, I just want to have an advise, probably in terms of resources, articles and tutorials about:
1. How can I compile an android source code?
2. I have a 2.7Ghz Dual core, 2GB Ram, and ubuntu x64, is it possible to build(kitkat) with this PC?
3. Is creating custom rom, different from building from source?
4. Can you give me an example(any) how to port the aosp for other phone?
5. After I made the Rom, how can I test it without flashing in a real phone for beta testing and risk prevention?
6. Can you site informations regarding my question, I am a beginner in Android source building/porting and are the things I have to learn first before diving into android rom development?
Thanks in advance
http://forum.xda-developers.com/showthread.php?t=2639611
this link isa guide on how to set up the build and enviroment and get going. im not sure that 2gb of RAM is enough, 4gb is the recommend amount of RAM just to run a 64 bit Operating system.
Announcing Sailfish for the Sony Xperia Z3 Compact!
This is not Android!
This should be thought of as a development experiment. It may be useful if you are a developer and want to write/port apps the the Sailfish operating system. It is not an end-user product, however, if you wish to experiment and try something different then feel free!
Please do not contact Jolla Care or Jolla Developer Care, as this is not the Jolla phone.
Special thanks to:
rss351 and locusf for the collaborative effort in porting SailfishOS to the Z3 compact
Everyone from the SailfishOS team/community, sledges and mal- in particular.
All Cyanogenmod devs, since SailfishOS uses drivers from Cyanogenmod to talk with the phone's hardware
Known issues:
Bluetooth isn't turned on, cause i've put no effort in for that so far
Camera doesn't work, cause it's not hooked up to interface.
No recovery inside hybris bootimage (you need to flash manually to return to cm/use recovery)
Sensors dont work (auto-adjust brightness, etcetera)
The Jolla account/store functionality is not enabled. This is being worked on by Jolla. In the meantime: use openrepo's warehouse (see bottom of this post)
What works:
Booting, basic usage of the OS itself (browsing, etc)
Texting, calling, data over mobile network (2g and 3g tested, 4g should work but is untested)
Wifi (both 2,4 and 5 GHz)
Power management seems to work fine (not tested much though)
Looking around and getting a feel for SailfishOS
Using your phone to develop and debug SailfishOS apps.
Installation guide/checklist:
Insert default warranty void message here. Your warranty is now void
Make a backup (just to be sure)
Depending on what you need from your phone, this may not be a rom suitable for daily driving with. But installation is non-destructive to your existing rom, so if you're curious, give SailfishOS a try
I have not tested this on locked bootloaders, but since I needed to modify the kernel, I guess that you need an unlocked bootloader.
Note this is not an official Sailfish OS build, and the Xperia Z3c is not a Jolla phone, so please don't report bugs to Jolla. If you want to report a bug, this thread is perfectly fine for that.
BEWARE: this image is NOT optimized for security. The phone boots in development mode by default. There is a root shell on telnet port 2323. This is not secure and will give anyone who wants it remote access to your phone. When the port matures this will be fixed.
The Sailfish OS image does not provide recovery, and since the Xperia Z3c does not have a recovery partition, you need a bootimage with recovery on it to flash cm/stock/sailfishos upgrade. I highly recommend using Nut's Xperia files for this. Use the boot.img from your Cyanogenmod installation.
The Sailfish OS image is based on a recent version of Cyanogenmod 12.1, so update your Cyanogenmod installation while you are at it. Use cm-12.1-20160523-NIGHTLY-z3c.zip if you encounter issues with other versions. Using another rom is not guaranteed to work, even if this rom is based on Cyanogenmod.
You can find the required zip in this Mega folder: https://mega.nz/#F!ucoRnDjD!WAHNWgxLQX5SK1Vdu8MRWw
Use your favorite recovery (but not CM's recovery since that checks for signatures, which this image does not have) to flash the zip.
If you want to return to Cyanogenmod, extract boot.img from your cm-12 zip and flash that with fastboot. Alternatively you can restore a previous backup. There is no need to re-flash Cyanogenmod because it was not removed by installing SailfishOS. You can remove the /data/.stowaways/sailfishos/ folder afterwards to reclaim disk space.
FAQ
You can find a FAQ which mentions most common user questions for SailfishOS here: http://forum.xda-developers.com/jolla-sailfish/general/qa-sailfish-n4-thread-devices-t2727330 . It's mainly aimed to the Nexus 4 and 5, but it's fairly applicable for all other ports as well.
Contributing
If you think this is awesome, and want to help fix the issues currently open: come by in #sailfishos-porters on irc.freenode.net!
Sources
You can find all used source code (may not be up-to-date to the latest image, but all key components are there) here: https://github.com/xperiasailors/
Installing OpenRepos warehouse
OpenRepos warehouse is like what F-Droid is versus Google's Play store. An unofficial, community-driven repository of open source apps.
Go to settings->developer options and set a password. Then open a terminal or connect over ssh to your phone (ssh [email protected]_of_phone).
Download the latest version of the warehouse app from here: https://openrepos.net/content/basil/warehouse-sailfishos
When you are asked to terminate packagekit anywhere in the steps below, answer yes.
Code:
$ devel-su
# zypper rr adaptation0
# zypper in <location_of_rpm_you_downloaded>
After this Warehouse app will be in your app launcher.
Impressive work! :good:
Sent from my Sony Xperia Z3 Compact using XDA Labs
Just having a go now.
Edit: just stayed on sony screen. Would it be because I came from SLiMM 1.8 ROM and not from a CM based ROM?
mrrflagg said:
Just having a go now.
Edit: just stayed on sony screen. Would it be because I came from SLiMM 1.8 ROM and not from a CM based ROM?
Click to expand...
Click to collapse
Probably, yes.
SailfishOS uses libhybris for hardware communication, which in turn uses the existing Cyanogenmod installation for drivers and proprietary blobs. But hybris is compiled against a certain Cyanogenmod version, so using other roms as a base might fail.
I've updated the TS and put the exact CM version I used in there, that should work fine.
There are any news? The project is in development?
Alexander3273 said:
There are any news? The project is in development?
Click to expand...
Click to collapse
No news, I don't spend much time on this port, every now and then I fiddle around with it an evening.
I'm currently trying to get AOSP based Sailfish port because Cyanogenmod for Z3c seems unmaintained, but progress is very slow.
Thank you for the info. Do you know when a version (sailfish port) comes out?
Hello! Thanks for your work. May i know the progress ?
it would be great to see a real "european" OS coming out of the dust...
i hate the thought that any company from the other side of the atlantic are wheels in the monster of patriot act...
@maikoool Any news about new build or something?
Yes, look here:
https://nokius.net/SFOS/scorpion/PreAlpha/
But still no Cam, no BT, No Sensors and No video playback
AFAIK is the 'scorpion' the Z3 Tablet compact, so not the Z3 compact. The base images will probably be the same.
I've recently rolled a build using AOSP 5.1 from the Sony Xperia developer pages, but my Z3c has developed an issue where the top and bottom of the screen don't function, so I cannot test properly.
Aries is device name, right? What's scorpion ?
kskarthik said:
Aries is device name, right? What's scorpion ?
Click to expand...
Click to collapse
Aries = Z3 compact, Scorpion = Z3 Tablet compact
I'm waiting eagerly to see SFOS on aries Do you know anything about our device support on jolla's list ?
Hi, this is my first post on xda, but i was reading it about 4 years and now i have unusuall question:
I have phone - samsung callisto (GT-I5510) with cyanogenmod 10.2 rom (android 4.3.1), and kernel sources are available for it, but only below 2.6.35.7 since phone is ancient. This is "latest" and probably "fastest" android phone with qwerty keyboard (not including this unrootable new blackberrys), so i think that it would be nice idea to deploy lightweight kali linux nethunter installation for hacking purpouses. I had some problems with oficial installer, and i had to modify it to allow install on device with such small /system partition, but the problem is that chrooting to Kali Roling is not working, becouse minimal kernel version needed is 3.2.*.*
Question is: Can i somehow "update" kernel sources of this device, so i can build 3.2.*.* kernel? I have much free time and even more determination to do this.
I've recently bought a surface go for school (64gb emmc, 4gb ram model) and I love the pen and the build quality however i found windows to be way to slow on a device like this and decided to try android. android-x86_64-8.1-r2 installed fine and it runs great on this hardware except for a few issues such as camera, auto rotate and the like. I've run into a pre-made kernel that fixes these issues and will link it below. I was wondering if someone could help me with implementing this kernel into android x86 to get the full set of features working. Thanks in advance!
Kernel:
(On github) /jakeday/linux-surface/releases
Could you tell me how you implemented that pre-made kernel into Android x86? I'm trying to do the same thing with Bliss OS 11.10 (Kernel 4.19), but I really don't know how. I could have missed something on the GitHub page, but I don't know how to implement a kernel into Android. To be honest, I never implemented a Linux kernel into an OS.
I hope you read this even though it's already been a few months.
Thank you