Related
Introduction:So I see you have found my Android M Preview ROM thread. So... You all might of seen this. It's Sony announcing that it's AOSP open line of Xperia devices can now build Android M and is showing devs how to build it. Apparently things aren't exactly that way. Google created under it's source code, an alpha branch for the upcoming Android M, what that branch contains is mostly Android Lollipop code and some Android M stuff. This branch will evolve to become Android M, but at it's current state, the ROM is in between Android lollipop and M (kind of a weird mix of a sort that's why the build number is 5.1.51 and the easter egg is the one of lollipop). I will however provide weekly (hopefully) builds of Android M as it becomes more M than L. Keep in mind that the current release of the ROM (as of 25-6-2015) does not contain the new API's (for devs that are interested). You can see Sony's official explanation here. If you are still interested though in checking out the current state of Android M be my guest though keep in mind that in it's current state it is FAR from a daily driver (modem and camera are the most major of bugs currently) and most if not all of the cool features on Android M developer preview for the Nexus line probably are not currently included (as on 25-6-15).
Warning
This works only on UNLOCKED BOOTLOADERS. Keep in mind that the ROM was built for the D6603 I don't know if it will work with any other variant of the Z3. In addition flashing this might erase recovery on some devices. Also I take no responsibility of whatever may happen by using this ROM.
Downloads (please read the Introduction if you haven't, its important )Kernel
System
Userdata
Installation:1. Backup EVERYTHING (Your SD card included. This ROM has proven to be unpredictable as of storage on some handsets).
2. Download the Kernel, System and Userdata images
3. Get yourself a working ADB/Fastboot installation (more on that on the kernel page)
4. Flash the kernel as described on it's page (Steps 1-7)
5. While still in fastboot mode enter these commands in the command prompt:
Code:
fastboot flash system (directory of system image)
fastboot flash userdata (direcotry of userdata image)
6. Reboot your device and wait for it to start up
Bugs:
Graphical Glitches
Camera
Modem (no phone calls/messages/data etc.)
Bluetooth
Random Force Closes in most Apps
Recents (some times)
Random other stuff
Erases all storage (internal and external) on some handsets
Screenshots:
Here you go.
Credits:
The rest of team Pear Crew
akateha
My Family & Friends
Sony and it's AOSP project
XDA
Google
Changelog:
----- Build I -----
Initial release.
Synced the latest android-m-preview branch
Most Android M features completely missing, ROM is like a hybrid of Lollipop&M
Bugs:
Graphical Glitches
Camera
Modem (no phone calls/messages/data etc.)
Bluetooth
Random Force Closes in most Apps
Recents (some times)
Random other stuff
I can't believe what you just posted
Hahaha @Griffiths_Anna why so?
@CedArctic
it may be that the flashing the rom erase the baseband
have you tried to reinstall a baseband after flash the rom?
@Gustavo RD78
Actually I haven't, even Sony states that Camera & Modem are guaranteed broken. Even if the modem was fixed (which I believe it will in the next few weeks) the ROM still needs a lot of work for all the other bugs. Although about the baseband, I think M requires a special version of the baseband because even when you flash the official M preview over the Nexus 5, you have to flash a new baseband that is compatible with Android M. I am currently away from my Z3 but if someone tries it out and confirms it working I would gladly add it to the main thread.
Wow, that was fast, need i say more??
@corpsegrinder62 Actually, considering the announcement date it is fast. I dualbooted my PC with linux just 36 hours ago, downloaded the sources and compiled... XD
Gustavo RD78 said:
@CedArctic
it may be that the flashing the rom erase the baseband
have you tried to reinstall a baseband after flash the rom?
Click to expand...
Click to collapse
Some modem components are stored on /system and not included for legal reasons in Sony's AOSP binary releases. https://github.com/SuperBenevolent/aosp-vendor-qcom-proprietary
At least with L-MR1, the ONLY things missing for modem to work are the blobs above. Dunno about M, I'm not bothering to mess with it until official M release.
Woaw, nice to see android m being worked on even though it's in its early stages.
Is that my build you are running?
Installed a few minutes ago. Thank you for compiling the source code.
Am I wrong or can´t I flash GApps?
Edit: Also I cannot use any storage. Not internal and not sd card
@Silveryard Yeah there are like lots of bugs... I hope some will be solved in the future. Storage is definetely one of them. I never tried to flash gapps though
It´s because some .apk files (like the play framework) cannot be installed with adb install command and require a custom recovery kernel or root or root for writing permissions in "system"
I don´t know much about compiling a system image but is it possible to place the gapps files into the right folder right before compiling everything in one file? This would help much and would make this preview much more usable in daily life.
Thank you! I'll be trying this on my D6653.
Made an installation video.
How To: Flash Android M Alpha for Xperia Z3: https://youtu.be/rJgYnqv3ZPM
Good news
CedArctic said:
@Silveryard Yeah there are like lots of bugs... I hope some will be solved in the future. Storage is definetely one of them. I never tried to flash gapps though
Click to expand...
Click to collapse
http://forum.xda-developers.com/and...v-android-m-apps-framework-deodexing-t3166000
@squabbi Cool bro @M-Rom Congrats for your work bro, I saw the FlyMe OS port... simply loved it... although I'm curious how did you port it? Because I tried to do so in the past... @Aaahh I'll take a look into it. I think storage is just the storage-list.xml in the framework.... Thanks for the guide
CedArctic said:
@squabbi Cool bro @M-Rom Congrats for your work bro, I saw the FlyMe OS port... simply loved it... although I'm curious how did you port it? Because I tried to do so in the past... @Aaahh I'll take a look into it. I think storage is just the storage-list.xml in the framework.... Thanks for the guide
Click to expand...
Click to collapse
What? I'm not sure what your talking about
Just to repeat, those are the actual M preview apps and I "fixed" them so that you can add them to your rom
@Aaahh you posted a quote of me about storage and I said now that I think I know that the issue is in the storage-list.xml in the framework. I will include your apps in the next build, but for now I am focusing on a different project until M becomes more stable...
Hi ,
About:
This is an unofficial 6.0x build of Blisspop compiled using caf source from sultanXDA.
Changes from official build:
--
Code:
All sultanXDA's patch[/color][/b]
--
Code:
SnapdragonCamera[/color][/b]
--
Code:
android_hardware_qcom_media
-
Code:
android_hardware_qcom_display
-
Code:
android_hardware_qcom_audio
-
Code:
android_kernel_oneplus_msm8974
-
Code:
proprietary_vendor_oneplus
-
Code:
proprietary_vendor_oppo
-
Code:
android_frameworks_base
-
Code:
android_frameworks_av
Source used:
1.https://github.com/BlissRoms
2.https://github.com/sultanxda/android_kernel_oneplus_msm8974
Credits:
-sultanXDA
-Blisspop team
-XDA
-Google
Let me know if i have missed any of you .
Latest Download(08/02): (Refer the second post for the older builds)
Blisspop_CAF_MM_08/02
Screenshots:
Uploading..
XDA:DevDB Information
Blisspop, ROM for the OnePlus One
Contributors
Vivek_Neel
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Version Information
Status: Testing
Created 2016-01-20
Last Updated 2016-02-07
Changelog:
V8:
Here
V7:
Here
V6:
Here
V5:
Here
V4:
Here
V3:
Here
V2:
Here
V1 :
Initial release
Older Builds:
Blisspop_CAF_MM_19/01
Reserved
Just in case..
Happy To see bliss marshmallow first caf build
Downloading
Will tell u bugs after testing ?
is it necessary to use latest firmware ?
i mean this :
CM 30/12 from jgcaap
Will give it a test run later today. Looking for something to update to and test.
@Vivek_Neel
Mate...Bliss for MM called Bliss 6.0 and i think you need to drop the *Pop* in your first post + the thread title too just to avoid some confusion...peace
...thread sub/
storm119 said:
@Vivek_Neel
Mate...Bliss for MM called Bliss 6.0 and i think you need to drop the *Pop* in your first post + the thread title too just to avoid some confusion...peace
...thread sub/
Click to expand...
Click to collapse
Yeah sure mate. Will do once i am on my laptop
Is it 6.0 or 6.0.1 ?
shield1331 said:
Is it 6.0 or 6.0.1 ?
Click to expand...
Click to collapse
6.0.1
Just flashed the ROM booted up fine thanks for ROM vivek
Check your inbox when you have a sec bud
Does Bliss6 support encryption?
EDIT: Flashed on top of an already-encrypted device and it decrypts and works just fine.
Blisspop, my favourite lollipop Rom. Now I'm on Temasek 6.0 (CAF) but I will try this one in a few days. Excellent work Vivek_Neel.
Vivek_Neel said:
Older Builds:
Click to expand...
Click to collapse
lol, you should update the OP )
1. refer to post #3 for older builds
2. is the 20160120 latest or "Latest Download(19/01)"
3. nice job, been waiting for this one
Thanks a lot :angel:
Thanks for porting BP to MM!
So I had the last CAF build flashed and decided to upgrade with this rom and had the oppo.verify_trustzone error. Followed instructions posted on Cm13 thread here and it is booting fine
Here are the instructions I used:
If you get an error when trying to install ("oppo.verify_trustzone" error), then first you must install/use TWRP recovery 2.8.6.0 (TWRP 2.8.7.0 cannot properly update the modem). Next, download and flash the latest official CM13.0 nightly. Then, without rebooting from recovery, wipe /system and flash my ROM. This process is necessary to update various firmwares (including TrustZone), as the updated firmware is needed by my ROM. After flashing my ROM, flash a Google apps package, and then reboot.[/COLOR]
Installation instructions (for updating to a newer release):
If you are already running my CM13.0 ROM, then you can update to a newer version of the ROM via the built-in OTA updater or by simply dirty-flashing the new ROM build without wiping anything. HOWEVER, do NOT reinstall Google Apps after installing a new update.
Click to expand...
Click to collapse
flashed open gapps and it booted fine, let it sit for 5 minutes after boot, rebooted in to recovery, and flashed Xposed-v79-sdk23-arm.zip.
Restarted phone and it stuck in bootloop
went back into recovery, sideloaded xposed uninstaller, wiped cache and it boots again.
miss the custom pattern unlock too
OP feel free to continue these builds if you like. OPO builds from source with no issues now but I have no problems with you building unofficial. However if you would like to contribute to the OPO source just let me know via PM and we can get you sorted out.
Just messing with optimization routines and toolchains now. Thank you for all your help man! The team thanks you as well!
ahb83 said:
Thanks for porting BP to MM!
So I had the last CAF build flashed and decided to upgrade with this rom and had the oppo.verify_trustzone error. Followed instructions posted on Cm13 thread here and it is booting fine
Here are the instructions I used:
flashed open gapps and it booted fine, let it sit for 5 minutes after boot, rebooted in to recovery, and flashed Xposed-v79-sdk23-arm.zip.
Restarted phone and it stuck in bootloop
went back into recovery, sideloaded xposed uninstaller, wiped cache and it boots again.
miss the custom pattern unlock too
Click to expand...
Click to collapse
I think you will need newer version of twrp for this MM Rom:
http://build.twrp.me/twrp/twrp-2.8.7.1-bacon.img
RBwai said:
I think you will need newer version of twrp for this MM Rom:
http://build.twrp.me/twrp/twrp-2.8.7.1-bacon.img
Click to expand...
Click to collapse
didn't realize a new one was out, but that did the trick. updating to new one now.
Thanks
Hi Guys,
I have found cm12.1 and cm13 for our Xperia P in a Webstite.
Cm12.1 is really stable and works like a charm.But Cm13 has more Bugs like Camera,Wlan etc.
Lets start
Installation - CyanogenMod 12.1
Next, you need the CyanogenMod ROM.zip, the appropriate GApps, and the corresponding boot.img - which also contains the Custom Recovery TWRP to flash and successfully boot the Android 5.1.1 based ROM. Copy the CyanogenMod 12.1 ROM.zip to Euner Xperia P, and reconnect it to your PC in fastboot mode, as described in the previous section. For the next step, the boot.img must be in your fastboot folder. Opens the input prompt and returns there
PHP:
Fastboot flash boot cm121_boot.img
on. Next, you reboot your Xperia P by either turning the device off and back on again. Or the command in the input prompt
PHP:
Fastboot reboot
Or use Flashtool for flashing of kernel
. Once the SONY label appears with the graphic of the CyanogenMod STE project, press the volume down and power button several times to reboot the device. Swiped at the start in the query to the right to allow changes to the system partition. Now select the menu item "Wipe> Advanced Wipe" and tick "System, Data, Cache" and "Android Secure" and confirm the selection by swiping again. To complete the installation, go back to the Install menu and navigate to the location where you previously copied the ROM and GApps. Flashes them one by one and reboots the Xperia P.
The first boat takes up to 10 minutes, and ends in the menu for the initial setup, as you are used to with a new device. Congratulations, you have successfully installed CyanogenMod on your Xperia P! Bold among you, can also try the
Installation - CyanogenMod 13
It is same as CM12.1
CyanogenMod 13, which is based on Android 6, but is still in an early development phase.
Credits
@Xperia-STE Team
@smartphone-guru.
I tried_ this version of cm12.1 its most stable than any other version but not very fluent in use.
But almost perfect for dailyuse
GAPPS error
I have flashed cm12.1 into my LT22i. But have an issue with GAPPS. Play store isn't lunching and it keeps closing up. Otherwise it's good rom, UI felt like butter
sz_ashik said:
I have flashed cm12.1 into my LT22i. But have an issue with GAPPS. Play store isn't lunching and it keeps closing up. Otherwise it's good rom, UI felt like butter
Click to expand...
Click to collapse
You have to install Gapps via cmw again. The best one is open gapps
CM12.1 Works perfectly!, I have not yet seen the first bug
jao6622 said:
CM12.1 Works perfectly!, I have not yet seen the first bug
Click to expand...
Click to collapse
is it better than cm11 final (m12)?
Hi, I gave to my brother my old Xperia P, and I wanted to upgrade to KK because is almost the most bug free (just A2DP not working that is important to me), and I wanted to know the bugs for lollipop if someone can give that information. Thanks!
Enviado desde mi Xperia Z2 mediante Tapatalk
Dagalur said:
is it better than cm11 final (m12)?
Click to expand...
Click to collapse
sorry , I don't have tested that rom :s
This ROM is old and newer build are already out but latest is 20161002 i think . There is link https://drive.google.com/drive/u/0/folders/0B4AOy62JMc5gaUpYbUFMVkdGRUk those are build by @CBNUKE i will download cm12.1 source and compile at least the latest source if it will even compile since i tried to fix cm13.0 and cannot make it to compile but i will try harder and maybe one day i will do it but for now i have holidays so i will compile cm12.1 hopefully. For now use CBNUKE build.
Bugs
Meloferz said:
Hi, I gave to my brother my old Xperia P, and I wanted to upgrade to KK because is almost the most bug free (just A2DP not working that is important to me), and I wanted to know the bugs for lollipop if someone can give that information. Thanks!
Enviado desde mi Xperia Z2 mediante Tapatalk
Click to expand...
Click to collapse
Camera Recording is Sometimes not working
A2DP totally not working
NFC not even recognized by system
but other things work.
---------- Post added at 10:21 PM ---------- Previous post was at 10:18 PM ----------
Dagalur said:
is it better than cm11 final (m12)?
Click to expand...
Click to collapse
Well its stable fast and usable for daily use but dont know if its faster but its good ROM.
---------- Post added at 10:32 PM ---------- Previous post was at 10:21 PM ----------
Dont expect that we will ever get CM13.0 on Nypon cause of hard building part and that BT is disabled because if its not u will get boot-loop.
i would need a dev that already ported a rom to help me with this.
Its not easy to port it.
Any help from a dev or porter is needed to make CM13.0 to work cannot do it on my own.
Good and bad news
First good news : i have managed to build lineage OS 13.0 and not bad news TWRP looks ugly bad text and the entire UI is not right how it should be and next problem rom is not bootable after kernel screen there is no boot animation just black screen forever . But i will try to fix it i updated TWRP to 3.0.2.0 and still the same UI problem so probably Kernel Issue but weird that i didnt even touch kernel source and still problem.
Thats it for now I will try to fix it.
And if anybody who have experience in this can help me i will be happy.
Maybe @CBNUKE will have spare time to help me with it.
Thanks.
Update on Development (Not yet working but close)
Found the problems source: I did forgot to patch the source on my first build so of course it cannot even boot. But now i little bit screwed my source code of lineage OS by trying to find solution to errors that popped out by applying patches.
So will re download source and hopefully after patches i will get working bootable ROM (Really Hopefully)
I will post a new Thread about it if i get at least basic stuff working.
And of course i will post the ROM itself if it will work.
And again any help from somebody willing to help and knows basic stuff about ROM porting will be Welcome.
OK not Working but here is it.
Test on YOUR OWN RISK.
IM NOT RESPONSIBLE FOR ANY DAMAGE TO YOUR PHONE OR IF YOU GET BOOTLOOP !!!!!!!!!!!
SO IF ANYTHING BAD HAPENS TO PHONE IM NOT RESPONSIBLE FOR IT !!!!
MAKE BOOT AND SYSTEM BACKUP BEFORE FLASHING !!!!
I have builded the ROM with patches but the same errors remain like bad UI in TWRP and not bootable system it will not even show Boot Animation but if anybody want to test it here is the ROM:
HTML:
https://ufile.io/un7oe
.
i have some patches that i havent applyed so will apply those and see what errors will it fix.
And if anybody flash it and know this errors then please tell me how to fix them
EDIT: added another patches like build patch and external_icu patch hwcomposer patch libhwui patch ste mutimedia patch (3 of them) and still not even a boot screen im woried that i will not even make this rom bootable
EDIT2: maybe found a way to fix it i probably need edited frameworks and system/core folder so going to do this few days later then will post and update if its was sucess or again a fail.
So i downloaded cm 12.1 source and will build daily build for this device until i figure out what the hell is wrong with Lineage 13.0 and cm 12.1 build will come out in few days need to configure the source for our device.
EDIT: I dont want you to be unhappy but there is like 1% change that i can fix all the problems in CM13.0 without a good team of devs and testers i cant do anything so dont expect ever daily runner baser on CM13.0 or even basic stuff working on it im student 17 years old yes i have a lot of C experience 9 years but thats doesnt change that i cannot do everything alone or with help of @AGONTUK its just lot of stuff to fix mainly boot so if anybody with some experience in this can help i will be happy.
i have all needed sources on my github so if anybody can help do it on github: My Github.
Have first build of CM 12.1 but i can see boot animation this time but it doesn't boot yet but another biiiig problem is no TWRP.
Main priority is TWRP so faster I can fix it the better: Probably will use android 5.1.1 repo TWRP and update to 3.0.2.0 TWRP if this will not help then maybe it's releated to not bootable system maybe have a fix but it needs more time.
And second priority is bootable system: I might have solution to this one but not totally sure.
Third priority after we have bootable using ROM is to make it fast:
1. Linaro instead art.
So in few days or week or so will post update how it's going. Maybe sooner if I get working build.
Haxk20 said:
Have first build of CM 12.1 but i can see boot animation this time but it doesn't boot yet but another biiiig problem is no TWRP.
Main priority is TWRP so faster I can fix it the better: Probably will use android 5.1.1 repo TWRP and update to 3.0.2.0 TWRP if this will not help then maybe it's releated to not bootable system maybe have a fix but it needs more time.
And second priority is bootable system: I might have solution to this one but not totally sure.
Third priority after we have bootable using ROM is to make it fast:
1. Linaro instead art.
So in few days or week or so will post update how it's going. Maybe sooner if I get working build.
Click to expand...
Click to collapse
Can you make a deodexed CM12.1 build? all builds from CBnuke are odexed
jao6622 said:
Can you make a deodexed CM12.1 build? all builds from CBnuke are odexed
Click to expand...
Click to collapse
Checked system/app and dont saw any odex files so yes i can make deodexed rom.
And also i have fixed TWRP error and tested just kernel and can boot rom with it now just to make system boot
Main issue with TWRP is FIXED even on CM13.0 and CM12.1 its fixed but both still dont boot up cm 12.1 atleast show me boot animation but cm 13.0 didnt do even that and its stuck at black screen i send few people message to help me with this and waiting for reply. Im looking trought my CM12.1 boot.log and i cannot find the error still what is causing it to not boot. And also i changed CM12.1 boot animation to the one included in LineageOS.
The problem was in TWRP that it choosed wrong PIXEL_FORMAT_BRGA_8888 instead of our PIXEL_FORMAT_RGB_565 so now it looks good now.
Here is link to this build: CM12.1 NOT BOOTABLE WITH FIXED TWRP FOR HELPING WITH FIX.
PLEASE IF YOU DONT KNOW WHAT YOU ARE DOING DONT INSTALL IT ITS STILL NOT BOOTABLE ROM.
Well cm12.1 still not booting at all but I'm going to delete the source and redownload by tutorial by friend (helping a lot Thanks) and if that fails I don't know then but hopefully we will get working build of cm12.1 and for now I'm deleting cm13.0 source since it needs a lot of work to be usable but will talk with SergeyL (he have device with same cpu) and will see how will that work if his work will be usable then if everything works perfectly (unlikely) then maybe cm14.1 but as I said unlikely so wait in few days for hopefully build of cm 12.1
Its working !!!
The best news i can tell you i want to share my Working build of CM12.1 !!! The build will be avaiable to download in few days in new thread (will tell the name later) but best of all is that working stuff is exactly like CBNUKE builds and the boot took 10 seconds Wooow.
Got new security patches 1.11.2016 (no newer since CM12.1 got no new updates.
Thats all i wanted to share.
---------- Post added at 11:53 PM ---------- Previous post was at 11:42 PM ----------
Its still build on CM source but will download Lineage Source and compile again but with cm source it was just test if i can build it and yes i can so after compiling Lineage will publish here
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Unofficial Cyanogenmod 11 ROM ported from Sony Xperia M!
Should work on Lumia 520/521/525/526/720, please report if it works or has any problem!
This rom is based on thinhx2 port, but has been fixed on some things to increase performance/put things to work.
WARNINGS:
If it's the first time you install Android on your Lumia, please go to this post and read the instructions: Android4Lumia original post
This rom includes by default the unofficial touchscreen drivers, as I have one.
If you have an official touchscreen, please flash this to boot through fastboot/twrp (same kernel without touch patch): http://www.mediafire.com/file/lxmh9pgqrbnj2fq/cm11-boot-officialtouch.img
For Lumia 520/521 users: DON'T INSTALL GAPPS IF YOU DON'T WANT TO THROW YOUR PHONE OUT THE WINDOW!! It becomes excessively laggy until you disable some Google play services using an app like Service Disabler.
I still don't recommend using any Lumia 52x with an Android ROM as a daily usage device, until some things are done (for example, better RAM management or RIL fixed).
Download here
Working:
Wi-Fi
Bluetooth
Battery meter (if you battery is damaged blame it, not me )
Almost everything (if not listed at not working list).
Not working:
RIL
Camera
Light/proximity/accelerometer sensors
Headphone jack not tested. BT headphones works
Screenshots:
Thanks to:
Android4Lumia project and all of it's members, for the main project. Without they nobody would get Android running on our Lumias!
thinhx2, for doing the port long ago and giving me the basics to start learning.
TBM13, for including unofficial touch support into the kernel and helping me to make the wifi/bt work.
ROM Info:
Rom OS Version: Android 4.4.4 Kitkat
Rom Kernel: 3.4.x
Kernel source:
Unofficial touch included here, original touch kernel here.
Version Information
Status: Testing
Created: 2019-12-17
Last Updated: 2019-12-17
cool
it installed successfully on a lumia 521 & let me tell you something ,it blows all of the other lineage builds out of the water,it even comes with the option to set root out of the box ,it's also snappier & I've noticed the wifi scanning is not as clumsy as it was on lineage,& since my lumia 521 still has the official touchscreen i had to flash that boot img through twrp because after the initial rom flash i booted without it & the touchscreen was acting funny,thanks man
working on lumia 520
managed to install it on the lumia 520, seems to be working fine though the headphone jack is not working, which is a shame, i was hoping to be able to use this device as a music player among a few other things. anyone knows a way to fix that?
nicholas45 said:
anyone knows a way to fix that?
Click to expand...
Click to collapse
I've heard somewhere that using an app called SoundAbout you can setup the headphone jack correctly, but I'd not test that and as I'd give my 520 to a friend I can't test that anymore.
Sent from my Galaxy S5 using XDA Labs
It boots on lumia 525 but the touch screen is glitched please fix it! I can't even pass the welcome screen
Thank you
Manav Harsana
Manav Harsana said:
It boots on lumia 525 but the touch screen is glitched please fix it! I can't even pass the welcome screen
Click to expand...
Click to collapse
As said, this ROM comes with the unofficial touch patch, so if you have an original touchscreen please follow the instructions and flash the original kernel (also attached).
MLX said:
As said, this ROM comes with the unofficial touch patch, so if you have an original touchscreen please follow the instructions and flash the original kernel (also attached).
Click to expand...
Click to collapse
Thanks sir I totally forgot about that you made my day can I theme this rom like android Oreo I will show it to you and then I will post that on XDA.
MLX said:
As said, this ROM comes with the unofficial touch patch, so if you have an original touchscreen please follow the instructions and flash the original kernel (also attached).
Click to expand...
Click to collapse
Thanks sir I totally forgot about that you made my day can I theme this rom like android Oreo I will show it to you and then I will post that on XDA.
MLX said:
As said, this ROM comes with the unofficial touch patch, so if you have an original touchscreen please follow the instructions and flash the original kernel (also attached).
Click to expand...
Click to collapse
Just tried to flash it but I have Cwm recovery how do I get twrp back Cwm does not support image files please help
Thank you
MLX said:
As said, this ROM comes with the unofficial touch patch, so if you have an original touchscreen please follow the instructions and flash the original kernel (also attached).
Click to expand...
Click to collapse
Hey I did it I just downloaded the boot IMG and then placed it in the zip it worked. The ROM is really nice .
Sent from my lumia 525
Thank you
From where do I get gapps for this ROM I flashed plenty of them but none of them worked please send me the link . the ROM is too cool
Thank you
Manav Harsana
Manav Harsana said:
From where do I get gapps for this ROM I flashed plenty of them but none of them worked please send me the link . the ROM is too cool
Thank you
Manav Harsana
Click to expand...
Click to collapse
if you do have a Lumia 520, then I don't recommend using GApps because of they do make the phone UNUSABLE.
I'm used to have low end phones, my main phone currently has worse specifications than the 520 and still works better than a 520 with gapps. Really, don't do that. If you want to ignore this, just download ARM gapps for 4.4 at opengapps.org
MLX said:
if you do have a Lumia 520, then I don't recommend using GApps because of they do make the phone UNUSABLE.
I'm used to have low end phones, my main phone currently has worse specifications than the 520 and still works better than a 520 with gapps. Really, don't do that. If you want to ignore this, just download ARM gapps for 4.4 at opengapps.org
Click to expand...
Click to collapse
Tried it but no luck I am also used to low end devices I have a device with armv6 processor 256mb ram and 196mb storage (I partitioned SD card and expanded to 4 GB) it's limit is android 4.4.4 and can't go further than that that is also stable and gapps suck in that device so I don't use em but I have a Lumia 525 it is capable to run gapps I guess and if not it's ok I will let you know at least it will be worth trying . I will try to flash gapps again and lets see what happens. Can you help me to change back to Twrp Recovery please is there a way we can make a zip file for it instead of the IMG file which is not supported by Cwm I really want twrp back.
Thank you
MLX said:
if you do have a Lumia 520, then I don't recommend using GApps because of they do make the phone UNUSABLE.
I'm used to have low end phones, my main phone currently has worse specifications than the 520 and still works better than a 520 with gapps. Really, don't do that. If you want to ignore this, just download ARM gapps for 4.4 at opengapps.org
Click to expand...
Click to collapse
Hey every thing is now fixed I installed flashify APK and then I downloaded twrp glee IMG and installed it via that app now I have twrp and when I flashed gapps with twrp it worked really nice so the main problem was actually Cwm(Lol)
The rom Rocks even with gapps
Thank you
Manav Harsana
MLX said:
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Unofficial Cyanogenmod 11 ROM ported from Sony Xperia M!
Should work on Lumia 520/521/525/526/720, please report if it works or has any problem!
This rom is based on thinhx2 port, but has been fixed on some things to increase performance/put things to work.
WARNINGS:
If it's the first time you install Android on your Lumia, please go to this post and read the instructions: Android4Lumia original post
This rom includes by default the unofficial touchscreen drivers, as I have one.
If you have an official touchscreen, please flash this to boot through fastboot/twrp (same kernel without touch patch): http://www.mediafire.com/file/lxmh9pgqrbnj2fq/cm11-boot-officialtouch.img
For Lumia 520/521 users: DON'T INSTALL GAPPS IF YOU DON'T WANT TO THROW YOUR PHONE OUT THE WINDOW!! It becomes excessively laggy until you disable some Google play services using an app like Service Disabler.
I still don't recommend using any Lumia 52x with an Android ROM as a daily usage device, until some things are done (for example, better RAM management or RIL fixed).
Download here
Working:
Wi-Fi
Bluetooth
Battery meter (if you battery is damaged blame it, not me )
Almost everything (if not listed at not working list).
Not working:
RIL
Camera
Light/proximity/accelerometer sensors
Headphone jack not tested. BT headphones works
Screenshots:
Thanks to:
Android4Lumia project and all of it's members, for the main project. Without they nobody would get Android running on our Lumias!
thinhx2, for doing the port long ago and giving me the basics to start learning.
TBM13, for including unofficial touch support into the kernel and helping me to make the wifi/bt work.
ROM Info:
Rom OS Version: Android 4.4.4 Kitkat
Rom Kernel: 3.4.x
Kernel source:
Unofficial touch included here, original touch kernel here.
Version Information
Status: Testing
Created: 2019-12-17
Last Updated: 2019-12-17
Click to expand...
Click to collapse
Um... i need 2 helps :-
1. After flashing the rom it shows my device as lumia 520 [But it is actually 525] and because of that i cant flash the lineage os 14 on this [i can the fame version] but [cant install the glee version and that is giving me a lots of problems. HOW DO I FIX IT?
2. Please port cm12 for our devices. And BTW i am making a lollipop themed rom based on your rom.
thx si.r
@MLX Need your help I want to figure out how do you build Android rom for lumia from sources? I am looking forward to make a Oreo rom
Ragedpixel said:
@MLX Need your help I want to figure out how do you build Android rom for lumia from sources? I am looking forward to make a Oreo rom
Click to expand...
Click to collapse
Hi! just download aosp source and use repos at https://github.com/Android4Lumia/
Specially these:
android_kernel_nokia_msm8x27
android_device_nokia_fame
proprietary_vendor_nokia
MLX said:
Hi! just download aosp source and use repos at https://github.com/Android4Lumia/
Specially these:
android_kernel_nokia_msm8x27
android_device_nokia_fame
proprietary_vendor_nokia
Click to expand...
Click to collapse
What if I use android_device_nokia_glee
MLX said:
Hi! just download aosp source and use repos at https://github.com/Android4Lumia/
Specially these:
android_kernel_nokia_msm8x27
android_device_nokia_fame
proprietary_vendor_nokia
Click to expand...
Click to collapse
Are you on telegram is hard to communicate in xda as the notifications are on mails and it's easy to miss my telegram: t.me/ragedpixel
We are very excited to announce the release of Paranoid Android Quartz, based on Android 10.
On the first launch, you’ll notice a clean setup with a beautiful wallpaper from Hampus Olsson, who teamed up with us again to create several beautiful pieces of artwork. Hampus is a multi-disciplinary artist whose design stands for itself and we’re glad to have him onboard. We also added further UI touches that we believe enhance the overall user experience. You can find all of the Paranoid Android wallpapers and many more in the Abstruct app, included in our builds.
Our builds are based on the Code Aurora Forum Android base, which is optimized for Qualcomm platforms and has a higher degree of performance, battery life, and functionality compared to the Android Open Source Project platform. The Paranoid Android team and contributors are focusing on squashing existing bugs, and implementing and improving features, performance, and stability. We are dedicated to providing a user experience with the stability that you can expect from stock ROMs with best-in-class performance and features to help you get the most out of your device.
Device-specific issues
Logcat gets spammed by gralloc errors
Note: Custom kernels are NOT supported! It already comes with LunarKernel.
Downloads
Downloads (from Drive)
TWRP (download 3.4)
GApps already included, don't click on this link
Changelogs
Keep an eye on our Twitter account, @paranoidaospa, as we will be posting about new features getting included in the release builds, as well as links to betas for those devices that will get them.
Paranoid Android Quartz released
Instructions
Reboot to bootloader
Boot into TWRP recovery via fastboot
Code:
fastboot boot twrp-3.4.0-0-marlin.img
Wipe data
Flash the ROM (no need for GApps since they're included)
(Optional) Reboot bootloader, boot TWRP again, and flash any addons you want.
Reboot to the system
Important/Useful links
Paranoid Android Twitter
Paranoid Android Channel (Telegram)
Paranoid Android Community (Telegram)
Help us improve PA by submitting detailed bug reports with logs. Learn how to take logs here.
Send the logs to me, as this is a unofficial build.
Here's the various sources used for this ROM (feel free to fix stuff):
Kernel source (for GPL compliance): https://github.com/Lunarixus/LunarKernel-marlin
The rest (contains locations for all the device-specific sources required to build PA): https://github.com/yagyaxt1034/android_vendor_pa/blob/quartz/products/marlin/pa.dependencies
Cheers and #StayParanoid!
XDA:DevDB Information
Paranoid Android Quartz for Pixel and Pixel XL, ROM for the Google Pixel XL
Contributors
yagyaxt1068, Lunarixus, spezi77, AOSPA team, PixelDust-CAF, Qualcomm Android for MSM, probably a bit of Lineage in there somewhere, you get the idea.
Source Code: https://github.com/yagyaxt1034/android_vendor_pa
ROM OS Version: Android 10
ROM Kernel: Linux 3.1.x
ROM Firmware Required: Latest 10 bootloader and radio
Based On: CAF
Version Information
Status: Testing
Current Beta Version: 5
Beta Release Date: 2020-08-17
Created 2020-08-18
Last Updated 2020-08-27
Thanks for bringing PA to our device. The install went perfectly, but setup kept asking me to insert my SIM card. I have Verizon. I was able to connect to WiFi, but couldn't get it to recognize the mobile network. I did try turning airplane mode on and off, but no luck.
beeewell said:
Thanks for bringing PA to our device. The install went perfectly, but setup kept asking me to insert my SIM card. I have Verizon. I was able to connect to WiFi, but couldn't get it to recognize the mobile network. I did try turning airplane mode on and off, but no luck.
Click to expand...
Click to collapse
Oh sorry, that's my bad. I accidentally forgot to switch to AOSP's RIL, as CAF RIL will not work. I'll fix it and upload a new build soon.
Same here, will wait, thanks for the fix in advance:good:
yagyaxt1068 said:
{Mod edit: Quoted OP shortened for better reading experience!}
Click to expand...
Click to collapse
Usually when I flash other rom I copied the rom zip to internal storage. In twrp I wiped system/data/delvik and flash the rom but here the instructions is different. could you plz elaborate I am newbie
imna357 said:
Same here, will wait, thanks for the fix in advance:good:
Click to expand...
Click to collapse
I've pushed an updated build with fixed RIL. Try it out.
bhaskarjyotisarmah51 said:
Usually when I flash other rom I copied the rom zip to internal storage. In twrp I wiped system/data/delvik and flash the rom but here the instructions is different. could you plz elaborate I am newbie
Click to expand...
Click to collapse
Most ROM instructions usually tell you to wipe /system, but this is not actually necessary on Pixels, since there's an A/B setup, so that's up to you whether you want to wipe system. I usually don't. And a factory reset should wipe both /data and dalvik, so that's not too hard.
The mobile network fix worked !! Good Job.
I'm getting Carrier Provisioning Service force close. I sent you a PM with a link to a logfile and hope you can read it.
A feature I'd love to see in future builds is Volume Steps.
Again, Thanks for your work here.
No bells and whistles but fast and smooth as to be expected
from PARANOID ANDROID brilliant thanks love it ?.
Excited to install again once it becomes stable
Apps take over the screen and I am not able to access screen buttons. I love that it is a CAF ROM.
cranialbug13 said:
Apps take over the screen and I am not able to access screen buttons. I love that it is a CAF ROM.
Click to expand...
Click to collapse
Sounds like a hostage situation intriguing very very intriguing ?.
You gave the wrong zip for sailfish, it's actually marlin.
Hey there!
Can we expect an Android 11 build in the future? That would be amazing! :fingers-crossed:
Help The Peace said:
Hey there!
Can we expect an Android 11 build in the future? That would be amazing! :fingers-crossed:
Click to expand...
Click to collapse
I'll try it once 11 is available for marlin and PA updates to it.
As the description says pixel and pixel xl ..just wanted to be sure if it would actually work in sailfish cause there's no such thread for this rom in sailfish.please reply
shtma said:
As the description says pixel and pixel xl ..just wanted to be sure if it would actually work in sailfish cause there's no such thread for this rom in sailfish.please reply
Click to expand...
Click to collapse
Unfortunately, the sailfish build didn't work right, so it's only on marlin for now. However, I'll come back to building PA on 11.
yagyaxt1068 said:
Unfortunately, the sailfish build didn't work right, so it's only on marlin for now. However, I'll come back to building PA on 11.
Click to expand...
Click to collapse
I see. It would be nice if in the future we're going to see other builds for sailfish/marlin. (official ones would be really awesome)