Related
It’s been far too long since our last official release, but I’m happy to present CyanogenMod-7.1! I apologize for the long delay, and I hope to speed up our release process in the future. We originally planned to release this last weekend at the Big Android BBQ but some issues with our automated build system held it back.
You’ll find many new features (read the CHANGELOG) and support for building on 68 devices! Upgrading from any previous CM-7 release or nightly build should be smooth and no wipe should be required.
New devices since 7.0 included in today’s release are:
HTC Desire S
HTC Incredible S
HTC Incredible 2
LG Optimus 2X and T-Mobile G2x
Motorola Backflip (Motus)
Motorola Cliq / Cliq XT
Motorola Defy
Motorola Droid 2
Motorola Droid X
Samsung Captivate
Samsung Fascinate
Samsung Mesmerize
Samsung Showcase
Samsung Vibrant
Samsung Galaxy S
Samsung Galaxy S2 (multiple carriers)
Sony Ericsson Xperia X8
Sony Ericsson Xperia Mini
Sony Ericsson Xperia Mini Pro
Sony Ericsson Xperia Neo
Sony Ericsson Xperia Play
Sony Ericsson Xperia Ray
Sony Ericsson Xperia Arc
ZTE V9
There are many devices still in beta status (Pyramid, Doubleshot, Shooter, HP Touchpad, Optimus 3D, several more) that we will be promoting to release or release-candidates in the next few weeks when the code is merged to our main branch.
The preferred method of installation is via ROM Manager, but you can directly download the latest release from our mirror network. Head over to our forums to discuss the release or get help. Installation instructions and other information can be found on our wiki.
As we continue to grow and improve CM, we are starting to see support from the industry grow- something that was unheard of previously. Recently, Sony Ericsson assisted our developers by providing over 20 devices, technical assistance, and compatible hardware drivers. CM-7.1 now has support for all recent SEMC devices thanks to this effort. Various other vendors have reached out to us, but we understand that it is still somewhat of a difficult situation. We will soon be providing a porting guide and some information on how vendors can get involved with the project and how/why it will benefit them.
Thanks again for the support, and for making CyanogenMod the #1 community Android distribution. We’ll be following up with a few minor releases and soon it will be time to start work on CM9!
Click to expand...
Click to collapse
courtesy : CyanogenMod.com
For Full Guide On CM7:
http://forum.cyanogenmod.com/topic/32755-cyanogenmod-7-for-the-xperia-arc-v7101-11-oct-2011/
Guys is this the guide to actually make this happen?
http://wiki.cyanogenmod.com/wiki/Sony_Ericsson_Xperia_Arc:_Full_Update_Guide
Bushmaster78FS said:
Guys is this the guide to actually make this happen?
http://wiki.cyanogenmod.com/wiki/Sony_Ericsson_Xperia_Arc:_Full_Update_Guide
Click to expand...
Click to collapse
Yup....this is the official guide to install cyanogenmod for arc...i will install it today and see what happen....is this a 2.3.4 or 2.3.3 version....can it do a overclocking...?
I think it said 2.3.7 ...
http://www.androidcentral.com/cyanogenmod-71-released-brings-android-237-pure-form
I didn't unlock my bootloader since my purchase a few months ago, so I am behind times. I am kind of concerned about the whole warranty issue... If you guys give me good performance and feature feedback, I might just get on the CM7 bandwagon...
Why in the phone list
Code:
http://wiki.cyanogenmod.com/wiki/Latest_Version#Sony_Ericsson_Xperia_Arc
there is no Xperia Arc? And they say Arc fully supported?
Which to download there then?
a guide with no rom. Yes thats so helpful.
Link to ROM
http://forum.cyanogenmod.com/topic/32755-cyanogenmod-7-for-the-xperia-arc-v7101-11-oct-2011/
Edit:
I just installed this ROM, camera is working.
There... i updated my theme to "XDA 2010" just to be able to thank you!
Anyway... will only go CM7 when I get bored of the stock but doomkerneled UI.
Tempting, very tempting.
The two things i'd really miss from the stock ROM are SE's home launcher (i know, i'm weird) and the panorama camera app. Anyone know how likely these are to work on top of CM?
SE Home Launcher is working on CM7, you can find modified versions on xda, I don't know about camera but I doubt it's working.
I installed this rom and did flash a clean 368 before. I am unable to add an APN for att and cannot use mobile data. It looks like I am not the only one. I have a LT15a, generic global was flashed though so it looks like a LT15i.
Sent from my LT15i using XDA App
joecool1029 said:
I installed this rom and did flash a clean 368 before. I am unable to add an APN for att and cannot use mobile data. It looks like I am not the only one. I have a LT15a, generic global was flashed though so it looks like a LT15i.
Sent from my LT15i using XDA App
Click to expand...
Click to collapse
For any issues, u should check out ORIGINAL cm7 thread by fxp in development section.
I would except it won't let me post there
Sent from my LT15i using XDA App
i really want to unlock bootloader for my ARC and install CM7 but i'm afraid about 3 things one is Bravia Engine which i will miss the crispy look on my pictures and videos and secondly i'm afraid that i won't find alternative for Track ID and thirdly facebook integration =__= which my calendar and address book will be missing...
joecool1029 said:
I would except it won't let me post there
Sent from my LT15i using XDA App
Click to expand...
Click to collapse
All the issues are listed and solved in the 139 pages of thread, u just need to find your issue.
PS: u just need one more post and u are good to go to post in dev section
mr.alawi said:
i really want to unlock bootloader for my ARC and install CM7 but i'm afraid about 3 things one is Bravia Engine which i will miss the crispy look on my pictures and videos and secondly i'm afraid that i won't find alternative for Track ID and thirdly facebook integration =__= which my calendar and address book will be missing...
Click to expand...
Click to collapse
have the same troubles.
mr.alawi said:
i really want to unlock bootloader for my ARC and install CM7 but i'm afraid about 3 things one is Bravia Engine which i will miss the crispy look on my pictures and videos and secondly i'm afraid that i won't find alternative for Track ID and thirdly facebook integration =__= which my calendar and address book will be missing...
Click to expand...
Click to collapse
u can always revert back to stock.
Try to flash older version or a 2.3.4 stock ROM with DoomKernel until the problem of APN is solved.
I've managed to flash CM7.1 with out having any issue... (seems there's battery drain... but not confirm yet)
The way I did from unlocking bootloader till flash CM7.1:
- Flash using flash tool to LT15i 4.0.A.2.368 Generic Global
- Unlock Bootloader
- Extract the boot.img from the CyanogenMod update.zip and copy it to the same folder as fastboot (the /tools folder within the Android SDK folder).
- Disconnect the Sony Ericsson Xperia Arc from the computer and power it off.
- Download CM7.1
- Unzip it and copy all the zip file frm the 7z you've downloaded into your microSD
- Press & hold the Menu button while connecting the Sony Ericsson Xperia Arc to the computer.
- On the computer, open terminal and run the following command:
fastboot -i 0xfce flash boot boot.img
fastboot -i 0xfce reboot
- Once the device boots into the ClockworkMod Recovery, use the side Volume Rocker to move around, & the Power button to select.
- Select the option to Wipe data/factory reset.
- Then select the option to Wipe cache partition.
- Select Install zip from sdcard.
- Select Choose zip from sdcard.
- Install the CM7.
- Install Google Apps.
- reboot.
NOTE: IF YOUR CONTACT IS IN SYNCML/SONY ERICSSON SYNC, PLEASE COPY YOUR CONTACT TO GOOGLE BY PERFORMING BELOW STEP:
- Go to Contact
- Setting > Backup Contact > choose memory
- Setting > Import Contact > choose gmail account
- Once you have successfully installed CM7.1, it will autosync the contact from gmail contact to your phone one you have setup the google account.
thank for your info
Source: Android™ Ice Cream Sandwich beta ROM available for unlocked 2011 Xperia™ smartphone models
Official thread by Kalle: [ROM] Official Sony Xperia ICS Beta ROM for arc S, ray, neo V
As a follow-up to the previous alpha, Sony has released the official beta of the upcoming ICS update for 2011 Xperia models. Unfortunately, this beta is currently only available for Xperia arc S, Xperia neo V and Xperia ray and they must be already running the latest firmware (4.0.2.A.0.42).
What's new?
Updated UI – We hope you will be happy to see that we have added a number of UI elements from ICS, as well as some new UI features already introduced in the Xperia™ S we announced in January.
Lockscreen and Face Unlock – We have added a shortcut to the camera directly from the lockscreen. Also, when you’re listening to music you can control the music player without unlocking the phone by using the music control icons on the lockscreen. In the coming final ICS upgrade, we will also include the face unlock app from Google for all phones that has a front-facing camera. The Face Unlock feature uses the front-facing camera in combination with advanced object recognition algorithms to provide a new way to unlock the phone. However, since Face Unlock is a Google Mobile Services (GMS) app, it is not included in this ICS beta ROM.
Connectivity turned on – Since we published the ICS alpha ROM, the GSM modem and FM radio have passed the certification and type approval, and they are therefore turned on in this ICS beta release.
Updated email client – The UI has been updated, and simplified email management has been added.
Quick dial – We have added a quick and easy way for you to make phone calls. See how it works in the ICS beta ROM demo video.
Please note that the Google Mobile Services (GMS) apps (for example Gmail, Google Maps and Face Unlock), Bluetooth™ and Wi-Fi™ are not included in the beta release due to that they are still waiting for the certification and type approval to be finalised.
Let's hope someone who is skilled out there to make it available for arc users. Also, I thought we were going to get the UXP NXT interface, but it seems like we don't.
What do you guys think?
Is this ROM maybe http://www.youtube.com/watch?v=qJbDl8aikUk&feature=player_embedded
EDIT:Sorry, I didn't see this video in the link below
Woohoo ..! Can't wait to test
I wish i had the technical knowhow to port it to Arc =/
Making now
don't forget you can talk to us any time on gtalk and as always xbox live
Wow, we're getting almost all of the Xperia S features with the ICS update too!
Assuming it will work on stock kernel - can it be installed and a CWM backup made???
I have already restored my ARC S backup to an ARC without any issue (BOTH Locked bootloaders)
Just a thought
----Edit----
Just to be clear - Could someone with an UNlocked bootloader install the rom and then make a CWM backup of which can be restored in another phone (Locked bootloader)?
I am guessing the UNlocked bootloader is needed to get the rom installed because its not signed.
Can we flash this on original Xperia Arc? I am asking this because I know that roms for Arc are compatible with Arc S. I also know that Arc has different partition table, but maybe since I have a modded rom it has changed.
Someone uses it on an Arc, so yes
Sent from my LT15i using XDA Premium App
Sony logo bootscreen! Awesome!
E: Quick Dial, great function!
2 features that I love on my N8 are decline with SMS and quick dial...
Now coming to ICS on my ARC!
1/2 Some sample screenshots taken on my LT18a. (Taken with No-Root Screenshot. This ROM has NOT been rooted as far as I know.)
Also available for download/viewing in original size here: https://secure.flickr.com/photos/jptn/sets/72157629441693667/show/
2/2 More screenshots... (Taken with No-Root Screenshot. This ROM has NOT been rooted as far as I know.)
Also available for download in original size here: https://secure.flickr.com/photos/jptn/sets/72157629441693667/show/
Curious... GSM is working, but does that only mean 2G networks?
EDIT: Never mind, didn't check the page 2 posts -_-;
Zeph_Ng said:
Curious... GSM is working, but does that only mean 2G networks?
EDIT: Never mind, didn't check the page 2 posts -_-;
Click to expand...
Click to collapse
The page 1 posts show 3G and H in the top. 3G/data works fine. Will need to do more tests.
BluechipJ said:
(This ROM has NOT been rooted as far as I know.)
Click to expand...
Click to collapse
It has been rooted. Just hotboot a kernel with recovery and flash the Superuser package.
http://downloads.androidsu.com/superuser/Superuser-3.0.7-efghi-signed.zip
this just in..
ICS baby..
http://www.youtube.com/watch?v=qJbDl8aikUk
here are some of my shots from my arc (not S although the model says lt18)...
got everything working and is rooted... downgraded baseband to 32... also installed the cosmicflow live wallie to complete the xperia s experience boot time takes around 30 secs for me...
cryogenix said:
here are some of my shots from my arc (not S although the model says lt18)...
got everything working and is rooted... downgraded baseband to 32... also installed the cosmicflow live wallie to complete the xperia s experience boot time takes around 30 secs for me...
Click to expand...
Click to collapse
did you just flash it normally?
Sent from my Arc using telepathy.
yes.
i followed this: http://forum.xda-developers.com/showthread.php?t=1513172
and this: http://forum.xda-developers.com/showthread.php?t=1513305
Hi, I have seen news about Oppo releasing the Kernel Source and supporting the AOSP community (the same Sony and HTC right now).
My question is, when Android 5.0 and a CM11 is released, does this source or information already released today about the device works for future releases of AOSP based ROMs without the support of the company?
Trying to be clear, Oppo (Sony and HTC too...) release some source today, but the next year they don't support this model, can the AOSP ROMs implement a new stable version using that last year released source from a prior Android version?
Thanks
pedroren said:
Hi, I have seen news about Oppo releasing the Kernel Source and supporting the AOSP community (the same Sony and HTC right now).
My question is, when Android 5.0 and a CM11 is released, does this source or information already released today about the device works for future releases of AOSP based ROMs without the support of the company?
Trying to be clear, Oppo (Sony and HTC too...) release some source today, but the next year they don't support this model, can the AOSP ROMs implement a new stable version using that last year released source from a prior Android version?
Thanks
Click to expand...
Click to collapse
No one knows. We would hope so, but no one would really know. Maybe.
Sent from my Oppo Find 5
kernel-wise - the cyanogenmod team has been able to merge it with the Qualcom sources, so if Qualcom keeps it up to date (most likely yes), then that's no problem (also, nexus 4 shares a lot of the same underlying hardware: CPU/SoC, GPU... that device will get updates, which could be ported over)
http://forum.xda-developers.com/showpost.php?p=40671515&postcount=5
proprietary library-wise - maybe? sometimes, they're compatible cross-android version, sometimes not, and you have to do workarounds to make it work on the new version.... could also steal libraries from other devices (see nexus 4 again)
Hi. I'm a 17-year old developer from the Netherlands, who was the first to get Ice Cream Sandwich booting on the HTC Desire. Then I released MIUI, CM7 and AOKP for the HTC Flyer and I was the first with every one of them
I have also been repackaging factory images for Android 4.3 for the Nexus 7 to make flashable ZIPs, and I released a nightly build of OmniROM. In case you're wondering why OmniROM Unofficial Build is not getting an update: I preferred to spend my time to prepare for KitKat.
But now that KitKat is available, I want to work as quick as possible to give you the latest best stuff for our Nexus 7. A custom ROM with features from Android 4.3 custom ROMs is what I strive to. However, I don't have a server or fast machine which is capable of compiling Android in a few hours (my machine with a dual core E2180 takes about 9 hours). This is really counter-productive as I need that box for other purposes as well. So I was wondering if anyone can give me access to a Linux box, with SSH access, and at least about 50GB free space (Ubuntu preferred). That way, I can release updates for unofficial builds of KitKat with new features much quicker.
If you think you have a machine that may be suitable for this, please reply And thanks in advance!
Sorry, I do not own such a machine, but I came here to vouch for this guy.
He was an excellent guy to have around the Flyer forums, and is sure one heck of a developer.
If you do have a box to spare, I would recommend giving it to Chaosz-X
Hi sailors out there
When I'm going to read through the available sailfish threads the question about how to set up multirom & sailfish have been asked many times. So I thought I'm writing this little guide. I describe the procedure along the nexus 4 mako. But it have to be very similar on other devices like nexus 5 for example. The important parts that differs from mako are the kernel and modem image you've to use. I will describe the easiest way in my opinion. Experienced users have more capabilities to reach the goal. I will not describe how to install twrp recovery and unlock bootloader. Both are prequesites. Please use xda search or google to get this. But this little guide want's to be simple as possible. So let's begin .
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Beginning:
First we have to detect you're actual setup and where you want to go. Because nexus 4 is up to date I think the most common goal is to run android 4.4 as primary and sailfish os as secondary. Atm I have only paranoidandroid 4.4 on my device and will show you how to get everything working.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Requirements / Download following parts:
kernel aosp: http://d-h.st/A99
kernel cm: http://d-h.st/CCn
aosp = android open source rom. Ask in you're rom thread what version you're on with the rom
cm = cyanogen mod rom. Ask in you're rom thread what version you're on with the rom
Modem for nexus4 in version 0.84: http://d-h.st/cIJ
or
through an app in play store: https://play.google.com/store/apps/details?id=com.bpear.makomodem&hl=de
sailfishOS ea4: http://releases.sailfishos.org/sfa-ea/sailfishos-mako-release-1.0.8.19-EA4.zip
cm 10.1.3: http://get.cm/get/aWH
Multirom manager in play store: https://play.google.com/store/apps/details?id=com.tassadar.multirommgr&hl=de
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Before we're going on check up the following
1. All zip's you've downloaded have to be transferred on the device
2. Apps from play store are installed
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Installation process
Reboot in twrp recovery
Flash the new kernel
Flash the modem 0.84 in twrp. Or via the modem flasher from playstore. It's you're decision.
Boot back into android
Proof the functionality in android withe the new modem and kernel. Wlan working? Bluetooth? NFC?
Open mutlirom manager. Follow the installation steps.
After some time you'll be back in android. You have now the right modem, kernel and and a twrp multirom version on you're device
After this. Please reboot back into twrp recovery
There select the advanced button.
Then the multirom button
Select add rom and mark up the entry sailfish os
Press next.
Now you can choose two zip files to flash
zip1: Select the cm10.1.3 zip file
zip2: Select the sailfish EA4 zip file
Installation process is beginning.
After this select reboot
You automatically went into multirom where you can cancel the automatic boot process for the primary rom. Then you can select which rom you want to start.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
And the most important thing is to read: http://forum.xda-developers.com/jolla-sailfish/general/qa-sailfish-n4-thread-devices-t2727330 for further question before you ask. I have described there many things to start with sailfish. If you find this useful think about to press the thanks button.
I'm a bit confused why do you insist on updating the modem? I checked my modem version and it is newer so I imagine there is no need to update. Also why use such an old version ov CM?
Just asking because I did all according to your instructions except I used newer CM build and didn't update my modem firmware as it was already newer. But for some reason Sailfish wont boot. It just hangs showing Google at start.
anttimonty said:
I'm a bit confused why do you insist on updating the modem? I checked my modem version and it is newer so I imagine there is no need to update. Also why use such an old version ov CM?
Just asking because I did all according to your instructions except I used newer CM build and didn't update my modem firmware as it was already newer. But for some reason Sailfish wont boot. It just hangs showing Google at start.
Click to expand...
Click to collapse
lol. and you ask why it won't work? It gave reasons for the instructions. Also look in the linked q&a thread at the bottom of first post. And here for you the relaese notes. Hope things becomes clear now. enjoy
Release Notes:
This release is based on SailfishOS 1.0.8.19 (Tahkalampi).
The Nexus 4 port is considered to be of alpha quality.
Though depending on your usage it might be stable enough for daily use.
Download & installation instructions:
* Install adb and fastboot
a. Debian/Ubuntu: apt-get install android-tools-adb android-tools-fastboot
b. Fedora: yum install android-tools
c. Mac OS X: Install Homebrew from http://brew.sh/, then: brew install android-platform-tools
d. Windows: See http://wiki.cyanogenmod.org/w/Doc:_fastboot_intro for instructions
MultiROM ≥v28 ability is in the image. See options of how to layout your MultiROM in #2 post below.
Alternatively, just have it as your primary ROM:
* Install Android 4.2.2 (JDQ39) to your Nexus 4
a. Instructions here: https://developers.google.com/androi...s#instructions
b. Download links can be found here: https://developers.google.com/androi...ges#occamjdq39
* Download CyanogenMod 10.1.3 for your Nexus 4
a. Perform Factory Reset and wipe contents of the /data/ partition in case of leftovers from previous ROMs
b. The file you want to download is cm-10.1.3-mako.zip
c. Download links can be found here: http://wiki.cyanogenmod.org/w/Install_CM_for_mako
* Download the Sailfish OS for Android image for "mako"
a. The file you want to download is http://releases.sailfishos.org/sfa-e...0.8.19-EA4.zip
b. Another flavour filled with demo content: http://releases.sailfishos.org/sfa-e...mo-content.zip
* Install CyanogenMod 10.1.3 on your Nexus 4
a. Follow the instructions at: http://wiki.cyanogenmod.org/w/Install_CM_for_mako
* After flashing the "cm-10.1.3-mako.zip" file, flash the Sailfish OS .zip file in the same way ("on top of it")
* Reboot bootloader, Sailfish OS should boot and be visible
We recommend reading through http://jolla.com/guide/ -- some parts may not apply to Nexus 4
HW Support status:
(Look for Nexus 4 row): https://wiki.merproject.org/wiki/Adaptations/libhybris
Click to expand...
Click to collapse
Also I stated in first post why I only described the way I've did
Ahh ok nevermind got it working once I used the older CM image. Wifi seems not to be working but I guess that is because I didn't downgrade my modem firmware. I guess I'll wait for a more stable builde or better yet buy a Jolla phone. Just like having the nexus 4 as I can test bunch of operating systems on it.
anttimonty said:
Ahh ok nevermind got it working once I used the older CM image. Wifi seems not to be working but I guess that is because I didn't downgrade my modem firmware. I guess I'll wait for a more stable builde or better yet buy a Jolla phone. Just like having the nexus 4 as I can test bunch of operating systems on it.
Click to expand...
Click to collapse
yes. that's a great benefit of this device Do you like sailfish?
With modem version 0.84 you have all parts working in sailfish and android
Ok thanks for the hint. I used to be one of the early adopters of Jolla, but couldn't use it as my daily phone so I sold it, but now that the OS has matured I think I maybe swithing back. Even though I still think Nokia N9 had far better UI experience. If only some would port N9 UI to Sailfish
anttimonty said:
Ok thanks for the hint. I used to be one of the early adopters of Jolla, but couldn't use it as my daily phone so I sold it, but now that the OS has matured I think I maybe swithing back. Even though I still think Nokia N9 had far better UI experience. If only some would port N9 UI to Sailfish
Click to expand...
Click to collapse
I feel the same, don't know why, but i just loved the N9 and the way the OS worked. I am not saying that sailfish is bad or something, but there Are somethings missing ...
v3ng3anc32002 said:
I feel the same, don't know why, but i just loved the N9 and the way the OS worked. I am not saying that sailfish is bad or something, but there Are somethings missing ...
Click to expand...
Click to collapse
They've practically done nothing since pre-release to improve and refine the UI, and so many incredibly basic features are missing (voicemail notifications, global copy and paste etc). The pulley menus are ropey and the active covers feature hasn't really been made use of much. They seem to be mainly concentrating on the Jolla Launcher for Android, which will definitely make them higher profile ... but if all their software engineers and UX guys are working on that instead of Sailfish itself, then it seems like cutting off their nose to spite their face.
I'm not a fan of Android and I can't see myself ever using WP or iOS, but the lack of progress and their production priorities are a bit dispiriting. I'm hoping that they're holding a lot of big and waited for improvements for update 1.1 (October).
Anyway, I'll keep it as my main phone for a bit longer, despite the fact that I have a Z3C coming early next week. Hope to see a decent Sailfish port for it soon.
mudnightoil said:
They've practically done nothing since pre-release to improve and refine the UI, and so many incredibly basic features are missing (voicemail notifications, global copy and paste etc). The pulley menus are ropey and the active covers feature hasn't really been made use of much. They seem to be mainly concentrating on the Jolla Launcher for Android, which will definitely make them higher profile ... but if all their software engineers and UX guys are working on that instead of Sailfish itself, then it seems like cutting off their nose to spite their face.
I'm not a fan of Android and I can't see myself ever using WP or iOS, but the lack of progress and their production priorities are a bit dispiriting. I'm hoping that they're holding a lot of big and waited for improvements for update 1.1 (October).
Anyway, I'll keep it as my main phone for a bit longer, despite the fact that I have a Z3C coming early next week. Hope to see a decent Sailfish port for it soon.
Click to expand...
Click to collapse
hope the same for the z1c, but don't how is the chance to see this port (soon or later).
Works nicely on my n4. Looking for getting gapps to run....
mudnightoil said:
They seem to be mainly concentrating on the Jolla Launcher for Android, which will definitely make them higher profile ... but if all their software engineers and UX guys are working on that instead of Sailfish itself, then it seems like cutting off their nose to spite their face.
Click to expand...
Click to collapse
This is just wrong
mudnightoil said:
I have a Z3C coming early next week. Hope to see a decent Sailfish port for it soon.
Click to expand...
Click to collapse
I bought a z1c after my N9 broke and I totally regret it. But I'll go on and try using it with Sailfish one day
paulle said:
hope the same for the z1c, but don't how is the chance to see this port (soon or later).
Click to expand...
Click to collapse
I tried using the hadk but like some other devices, there are gpu-problems with the z1c (see https://wiki.merproject.org/wiki/Adaptations/libhybris/gpu).
Keep an eye on IRC logs and on the status matrix in mer wiki
sorry for off-topic
iuno said:
This is just wrong
I bought a z1c after my N9 broke and I totally regret it. But I'll go on and try using it with Sailfish one day
I tried using the hadk but like some other devices, there are gpu-problems with the z1c (see https://wiki.merproject.org/wiki/Adaptations/libhybris/gpu).
Keep an eye on IRC logs and on the status matrix in mer wiki
sorry for off-topic
Click to expand...
Click to collapse
thank you for information, followed your links to look at. It seems there for the z1c is a lot of remaining, we will need patience.
iuno said:
I bought a z1c after my N9 broke and I totally regret it. But I'll go on and try using it with Sailfish one day
I tried using the hadk but like some other devices, there are gpu-problems with the z1c (see https://wiki.merproject.org/wiki/Adaptations/libhybris/gpu).
Keep an eye on IRC logs and on the status matrix in mer wiki
sorry for off-topic
Click to expand...
Click to collapse
Don't think I'll regret getting the Z3C, from a hardware perspective ... held one the other day, as a friend had been gifted one by Sony. It's absolutely superb. Granted, I despise Android .. but for when the Jolla ****s itself / runs out of battery / when GPS or a camera is needed / roaming / skype /outdoor use, I can suffer it until there's a Sailfish port.
Hopefully as work is already under way for the One Plus One, the identical SoC used in the Z3 & Z3C won't be too much additional work.
For all the moaning and groaning about Mediatek, I'm guessing the simplest and best port of Sailfish will probably be for the Meizu MX4, as there'll be an Ubuntu ROM for it, and libhybris is used by Ubuntu Phone ...
Also, hopefully future iterations of the HADK will smooth out some of the problems porters are facing.
mudnightoil said:
Don't think I'll regret getting the Z3C, from a hardware perspective
Click to expand...
Click to collapse
it's the same for me...
The SoC in your z3c and 1+1 is actually the same as in z1c, I guess – 8974 vs 8974ac – only higher clocked.
You should not suppose that mediatek SoCs will be easier in general just because of is one working device. Jolla runs a Snapdragon and it works perfectly, most of the devices sailfish is currently ported to run snapdragons – with very different results.
iuno said:
it's the same for me...
The SoC in your z3c and 1+1 is actually the same as in z1c, I guess – 8974 vs 8974ac – only higher clocked.
You should not suppose that mediatek SoCs will be easier in general just because of is one working device. Jolla runs a Snapdragon and it works perfectly, most of the devices sailfish is currently ported to run snapdragons – with very different results.
Click to expand...
Click to collapse
I wasn't saying Mediatek in general will be easier (though it's possible), but any device with an official Ubuntu ROM certainly will (should) be - Meizu MX4 (Mediatek) is the first of those.
P.S. The Z3C is fantastic ... though unfortunately in black as opposed to the red I ordered (it's being swapped tomorrow).
Thank you very much for these instructions. i have one question though. In order to download CM 10.1.3, it says to click that link which takes you to download CM installer app. Ive used that app before and as far as I kmow, it doesnt let you choose which version of CM you want to install, instead it just sets you up to install the newest CM 11. I downloaded 10.1.3 from their site. Either way, no big deal.
Also, which kernel do I download to install? Aosp or CM?
Thank you
Still up to date
Hi,
are these steps still up to date or should we follow a different set up guide to install the latest sailfish OS on the Nexus 4? Because most, if not all, the links on the first page end up 404...
Bluetooth sync from Jolla to Nexus 4
Flashed my Nexus 4 with the factory 4.2.2 from google with radio .48 and then flashed cm-10.1-20131003-SNAPSHOT-TREATFORCOOPER-mako-signed.zip because that seemed to be the 10.1.3 mentioned in the guides to end up flashing the latest sfos from this guide http://forum.xda-developers.com/nexus-4/development/rom-sailfish-os-community-port-t2969823.
I didn't try calling, it has 3G network working and wifi is working but I can't seem to get the contacts from my Jolla phone using the Bluetooth sync from the settings.
Anybody has some advice on this?
Just had a good look at the wiki of devices on the mer website and found out the bluetooth is not yet working on the Nexus 4...
Works perfectly on my oneplus one