Hey, I've been working on porting CyanogenMod 9 to my phone (Sony Xperia E - we already have CM10, but stock ICS is faster than it, and I decided to try CM9). I'm trying to follow the guide here: http://wiki.cyanogenmod.org/w/Doc:_porting_intro I've already built CM10.1 for the Nexus 7, so I'm okay with all the breakfast nanhu and stuff.
My question is this - to make the device and vendor folders, I can use mkvendor.sh, but it says it works only for devices that:
use a standard boot.img file, using the standard Android conventions and headers. It won't work for devices that deviate from this standard (Nook Color, Touchpad, etc.).
Click to expand...
Click to collapse
Since the Xperia E doesn't have a recovery mode, the recovery has to be built into the kernel, ie. the boot.img. Does this mean I can't use the stock ICS boot.img file for this?
Related
Hi,
I know there are a lot of guides out there but you still might want to read it
What are the different things I need to know ?
Well you will hear three terms very often. Baseband, Kernel and the ROM. Lets see what they are.
Baseband :
A firmware to drive the radio (2G/3G) chipset in your phone. Most of the time you don't need to bother thinking about it. But you might need to upgrade this firmware in order to get optimum performance. Just think of it as something you won't need to apply unless explicitly specified. For you xperia neo v, you can find out the baseband version by going into phone info and looking up baseband version number. I have not flashed any baseband. I recommend if you have not rooted/flashed your phone, install the official sony update you'll get the latest baseband without any troubles, this is what I did. Although if you need to flash it, there are very many tutorials available on this forum. You can check out the flashtool androxyde . github . com / Flashtool (sorry for the spaces in the links. I can't post outside links because of some forum rules which don't make any sense whatsoever)
Kernel:
This is the Linux (android) kernel image that drives all the hardware. Always install (flash) the recommended kernel for any ROM. Installing kernel and ROM is an absolute must.
ROM:
This is the actual thing you see running on your phone. It consists of the modified android source, user interface tweaks, the apps and some under the hood modifications done by the ROM developer for ex. cyanogenmod.
Now lets setup you linux (ubuntu) install fo installing a custom ROM on your phone.
Follow this wiki : wiki. cyanogenmod. com / wiki / Howto:_Install_the_Android_SDK
Don't forget to setup Udev by making a file /etc/udev/rules.d/51-android.rules with contents as
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="0fce", MODE="0666", GROUP="plugdev"
now restart your udev daemon by running "sudo restart udev".
Now yo have the necessary kernel and ROM flashing tools at your disposal. I am going to tell you how to achieve a fast and very battery efficient cyanogenmod install.
1) Download CM9 ROM and gapps(for google apps) from here
ROM: download. cyanogenmod. com /get / jenkins/4630/cm-9.0.0-RC2-haida.zip
Gapps: cmw. 22aaf3. com/gapps /gapps-ics-20120317-signed.zip
Copy these two zips to your phone's sd card.
2) Download night elf's kernel for cyanogenmod 9 from here mediafire. com /?nm7g0zid8aazfl1
3) Follow this guide wiki. cyanogenmod. com/wiki/Sony_Ericsson_Xperia_Neo:_Full_Update_Guide
But instead of flashing the kernel inside the zip, flash the night elf's kernel (just provide the path to night elf's kernel instead of the ROM's boot.img).
4) As told in the link given in above step flash both the zips. Before flashing you may also clear the Dalvik cache by going into advanced options in the recovery menu.
5) Reboot your phone. Don't turn off the GPS !!! There is a bug in CM9 RC2 which results in substantial hit on battery life. Just let it be. Anyways the GPS antenna is turned off unless any application is using it.
I am having approx more than two days of battery life with light/moderate usage (No data connection, occasional wifi).
CM9 may not be the best looking ROM. But I can assure you nothing beats it in the performance and the default setup (its very sane !!! No need to change anything at all). Also I only trust cyanogen community with all my very personal information (its my phone, it has everything !! ). If you need eye candy more and are comfortable with taking privacy risks, you may try MIUI and the dozens more ROM in the thread. I am not trying to offend anyone, its just my opinion, feel free to call me paranoid.
Always keep in mind that there are no stupid questions only stupid answers Ask away !!
I wish you a free and serene future.
I am however more interested in using the source code provided by Sony with AOSP and compiling the system image by myself.
I know how to compile AOSP, but the files provided by Sony doesn't seem to contain the `device` directory.
Also is it possible to use the AOSP and compile a ROM that is exactly the same as the stock ROM?
I haven't done any reading or experimentation on the subject but as far as I know, Sony only provides the stock kernal sources, some hardware support libraries (not all for ex HDMI, xLOUD still not provided). You can compile the kernel from Sony sources. Android image and apps are not provided by sony. All the ROM makers who are releasing ROMs based on stock are modifying the stock ROM image to do it.
For compiling your own ROM, you will have to do it form AOSP or cyanogenmod (FXP) sources.
I need help and guidance to port CM10 to my tablet.
I have setup everything needed (Ubuntu with the source code and so on).
I built CM10 for my Phone (Xperia Mini Pro) without any problems (FreeXperia source), am using it right now.
If someone can point me in the right direction to port CM10 for the tablet. The tablet is rooted, I have all the system files backed up.
I followed few guides, but it fails at unpacking boot.img, do I need a custom boot img? I found one for another tablet with RK3066 cpu, how to add it to my project? Which files do I need from the tablet? The whole lib dir and etc or what?
Any help would be appreciated.
mexusbg said:
I need help and guidance to port CM10 to my tablet.
I have setup everything needed (Ubuntu with the source code and so on).
I built CM10 for my Phone (Xperia Mini Pro) without any problems (FreeXperia source), am using it right now.
If someone can point me in the right direction to port CM10 for the tablet. The tablet is rooted, I have all the system files backed up.
I followed few guides, but it fails at unpacking boot.img, do I need a custom boot img? I found one for another tablet with RK3066 cpu, how to add it to my project? Which files do I need from the tablet? The whole lib dir and etc or what?
Any help would be appreciated.
Click to expand...
Click to collapse
any progress with cm port?
MarvinFS said:
any progress with cm port?
Click to expand...
Click to collapse
Not so far
Ok so I have built cm11 for my device (galaxys s 4g), and ported cm11 from another device to (aries -> galaxy s 4g). CM11 has too much going on IMO and I just want pure aosp on my device, the problem is that there are no (recent) aosp roms for my device, or any similar devices.
So how do I port my device to a different flavor of android when there are no roms of that flavor?
What have I tried?
So far I have setup the aosp 4.4 repo to a different folder than my cm11 repo (the build environment files should be the same right?)
I tried using the manifest from the cm11 rom and buidling with aosp,that didnt work it didnt even finish compiling =(.
I browsed the aosp source for other devices by the same manufacturer, but everything looked completely different from what I am used to.
The most helpful guide in this direction sofar has been cyanogenmods guide but it has left me with more questions than answers.
What [I think] I need to know
Custom recovery - aosp doent seem to include a recovery, the cm guide says to start with the recovery. So i need to know if I need to add a custom recovery to aosp, or if i can install aosp roms from twrp without breaking it.
Binaries - It is safe to use the binaries used in CM11 for aosp/any other flavor, or are the binaries flavor specific? (im thinking they are safe to use, but not entirely sure).
Device files - what files should be safe to use for any flavor?
Kernel - Cm builds the kernel when you compile the rom (or so it says), does aosp build the kernel when you build the rom, or do I have to build the kernel separately? Is it safe to say use a CM11 kernel with an aosp rom?
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 ?
We are happy to announce that we now have launched AOSP build instructions for Android 13!
The Xperia Open Source Project (Xperia Open Devices) is an initiative created to guide the developers step-by-step on how to build AOSP for their unlocked Xperia devices. Our instructions will show you how to prepare your environment, how to download all the necessary tools, and how to download and configure the code before you can build AOSP images and flash them on your own device.
New AOSP build instructions for Android 13 | Developer World
developer.sony.com
Many thanks! I was wondering if you could help me with the following two issues:
Can't find binaries SW_binaries_for_Xperia*.zip (for Xperia 1 III Android 13) for step 7 "Flash vendor image to your device".
(Never mind, I read you said elsewhere to use the Generic Android 12 Vendor Image.)
Also DSU loader crashes when trying to load Android 13 experimental or any other GSI through "Developer options".
KillSkill said:
Many thanks! I was wondering if you could help me with the following two issues:
Can't find binaries SW_binaries_for_Xperia*.zip (for Xperia 1 III Android 13) for step 7 "Flash vendor image to your device".
(Never mind, I read you said elsewhere to use the Generic Android 12 Vendor Image.)
Also DSU loader crashes when trying to load Android 13 experimental or any other GSI through "Developer options".
Click to expand...
Click to collapse
At this stage the Android 13 release is tested only on a full build according to the build intructions
jerpelea said:
At this stage the Android 13 release is tested only on a full build according to the build intructions
Click to expand...
Click to collapse
And everything actually works? That has not been the case in the past with SODP code.
thatguy222 said:
And everything actually works? That has not been the case in the past with SODP code.
Click to expand...
Click to collapse
It depends on what the expectations are. The basic functionality is already working
jerpelea said:
It depends on what the expectations are. The basic functionality is already working
Click to expand...
Click to collapse
Define basic functionality...like texting, data and phone calls???
what is the use of all these instructions if there are no developers who have made and supported at least a normal firmware based on android 12