CyanogenMod 13 for the Sony Xperia XA Dual Sim
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0 (Marshmallow), which is designed to increase
performance and reliability over stock Android for your device.
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be
used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps).
CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Before you start
This ROM is only for the F3112 and the F3116
Code:
Code:
*
* Your warranty may be voided !
*
* 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.
*
Special Thanks
@Deepflex for his P9000 github repository used as base for sources.
@zacharias.maladroit for his CM13 guide for Z5 and who have heavily inspired me for this guide
-The Sonyxperiadev team for releasing their kernel sources to the public.
-The entire CyanogenMod team.
-All Xda contributors for their guides and HowTo.
-The Google searchbar
Known Issues
-Camera not working
-Video not working
-No Sim
-Screen not wake up after screen off.
-No sound
-"Security" settings not working
-"More... " settings not working
-NFC not working
-GPS (not tested)
-Full brightness
-And probably more...
Guides/Instructions
For now I will not explain how to flash because my Rom is in very beta stage and I need help for debugging,
it mean it's not user friendly and only skilled users will know how to flash it,
As soon as the rom will be stable I will update this part of the guide.
I will just say it's like any other CM Rom flashing.
Downloads
CyanogenMod Recovery https://mega.nz/#!EoJXyK6R!ORe1tBtn2LhkFsOIs0grhOo_jFDsYKT1wJKGGBJhBsA
ROM
Initial release: https://mega.nz/#!gx50yZZL!i1qL_Ab9_LubJCmuYefnazW4ddn_r5Z-a-8FXmKTsDg
Questions and bug reporting
The following questions will be ignored
- Inappropriate questions
- Requests for other devices
-Forced orders, EX. : "PLS FIX!!!!!!"
-ETA's
-Often repeated questions or requests usually by the same user
-Requests that are out of CM
How to report a bug/issue
Explain exactly what happens
Mention a log if you can (Please use hastebin or any other paste site to keep the thread clean)
If you can't mention a log, explain as precise as possible when, why and where it occurs!
Source Code
Source Code can be obtained from:
https://github.com/CyanogenMod
https://github.com/rrvuhpg
Kernel Source code can be obtained from: http://developer.sonymobile.com/downloads/xperia-open-source-archives/
I gladly accept any developers that are willing to contribute to this project! Please PM @rrvuhpg if you are interested in joining this project!
You can join my XA/Ultra channel on Telegram for dev questions: telegram.me/rrvuhpg_XA
ROM OS Version: 6.0.1 Marshmallow
ROM Firmware Required: 33.2.B.3.81 Recommended
Based On: CyanogenMod
Version Information
Status: Initial release
cool !! nice work.. if u can do the same on F3111 please !
first time i get sony and i use stock firmware ..with other brands i use custom rom
Nice! I've been waiting for this!
I'm learning C and JAVA myself, but guess it would take a long time before I can actually develop something!
Until then, I count on you! Thanks!
ObtuseFox said:
Nice! I've been waiting for this!
I'm learning C and JAVA myself, but guess it would take a long time before I can actually develop something!
Until then, I count on you! Thanks!
Click to expand...
Click to collapse
You know porting roms have nothing to make with pure developpment. More with analyse of codes and importations of libraries, etc... You won't really code a whole page
I am so happy to see this here
My old LG D295 just died and i pull the trigger for XA F3111 and i hope everything is going well with the port
Stersound said:
I am so happy to see this here
My old LG D295 just died and i pull the trigger for XA F3111 and i hope everything is going well with the port
Click to expand...
Click to collapse
It's on the good way, I'm waiting for my new computer to continue, my actual take 11 hours to build :silly: As soon as the "ril" (telephony features) will work I will release an update, for now I can enter pin code but sim stay locked
All other features are working or unstable, only NFC is not working. For XA single sim you will have to wait a little more.
Cyanogen means losing Bluetooth aptX.
saintsimon said:
Cyanogen means losing Bluetooth aptX.
Click to expand...
Click to collapse
Sir i believe this is not correct
Stersound said:
Sir i believe this is not correct
Click to expand...
Click to collapse
Well: aptX means licence fees. Does Cyanogen pay them?
I need facts, no beliefs. Cyanogen is not known for aptX support.
Or is there a file like "libbt-aptX-ARM-x.x.x.so" in the /system/lib/ folder? If not, your belief is unsubstantiated.
Can we expect CM 14 ? instead?
are you going to build a rom like cm or aosp for the xa ultra?
sexxualization said:
are you going to build a rom like cm or aosp for the xa ultra?
Click to expand...
Click to collapse
Probably no, I don't have an unlocked Ultra to work on it. As long as we don't know why Ultra devices can brick when flashing with Flashtool it will stay with locked bootloader.
rrvuhpg said:
Probably no, I don't have an unlocked Ultra to work on it. As long as we don't know why Ultra devices can brick when flashing with Flashtool it will stay with locked bootloader.
Click to expand...
Click to collapse
well i own an unlocked xa ultra with twrp recovery to help you try the rom out
sexxualization said:
well i own an unlocked xa ultra with twrp recovery to help you try the rom out
Click to expand...
Click to collapse
Thank you for your help but I need the device in my hands for many reasons (dump, debugging, reverse engineering, ...).
As you know XA and Ultra are not intended to have custom roms and I have to make my own sources, it mean a lot of work. Ultra is not a simple copy/paste of the XA system
saintsimon said:
Well: aptX means licence fees. Does Cyanogen pay them?
I need facts, no beliefs. Cyanogen is not known for aptX support.
Or is there a file like "libbt-aptX-ARM-x.x.x.so" in the /system/lib/ folder? If not, your belief is unsubstantiated.
Click to expand...
Click to collapse
Apt-x is a feature supported in vanilla android already.
Then it's true you should have the loading library (which isn't all that secret btw) but for some reason, it's reported to work nevertheless on Xperia S.
Regardless, I don't see why you couldn't just include stock libbt-aptX-ARM-4.2.2.so in android_vendor/proprietary (or android_device/prebuilt, Idk)
EDIT: https://review.lineageos.org/#/c/158337
Is there any chance this ROM will work on the f3111?
jolpool said:
Is there any chance this ROM will work on the f3111?
Click to expand...
Click to collapse
I think this project is kind of dead already since were no activities happening.
Jhayzt said:
I think this project is kind of dead already since were no activities happening.
Click to expand...
Click to collapse
As you know CM is dead and Lineage OS just launched. Other thing, Nougat for XA and Ultra will come soon and I know that users will ask for Rom based on it. We can say CM13 project is dead but new Lineage OS project will come for XA
rrvuhpg said:
As you know CM is dead and Lineage OS just launched. Other thing, Nougat for XA and Ultra will come soon and I know that users will ask for Rom based on it. We can say CM13 project is dead but new Lineage OS project will come for XA
Click to expand...
Click to collapse
Really looking forward for lineage OS for XA.
Please update this rom asap. Really need your help, i hate this stock version. The touch screen is very annoying. I can't touch the edge of the screen. Please help us
Related
This is crDroid for Sony Xperia Z3 Compact (Aries)
crDroid build will always mainly based on CyanogenMod with some extra and few features (Cool and useful)
Code:
#include
/*
* 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.
*/
Code:
IMPORTANT: Make sure you have an unlock Bootloader
Code:
WORKING
- RIL
- Mic
- FFMPEG Drivers
- Sound (Speaker and Headset)
- LED
- Thermal Manager
- Audio and Video Decoders/Encoders
- Cameras
- Torch
Code:
CREDITS
CM Rom
Slim Rom
Omni Rom
Many More.....
XDA:DevDB Information
crDroid Android, ROM for the Sony Xperia Z3 Compact
Contributors
davidteri91
Source Code: http://github.com/crdroidandroid
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Stable
Created 2015-05-25
Last Updated 2015-05-25
Enjoy to Our Site on Google Plus
Download
Help us with Translations
Donate to Maintain our build server
Demo Video
Download Gapps For Lollipop
No News
YAY for you!
Since it uses CM as a base and I don't see a "what's not working" section I guess it has the same "issues" as the latest CM build?
great to see some more development happening
many thanks for this probably will try this just still a little hesitant to unlock bootloader
edit: in sony download section i only find build for leo (z3)... do you have direct link for z3c?
i cant find download link either, i see only Leo (Z3)
Hello @davidteri91,
welcome to the z3c - community and THX for this build
The world is a small village
A small installation instruction is highly appreciated
Cheers
Rhonin
Rhonin86 said:
Hello @davidteri91,
welcome to the z3c - community and THX for this build
The world is a small village
A small installation instruction is highly appreciated
Cheers
Rhonin
Click to expand...
Click to collapse
Hi @Rhonin86 good to see you here I am development Z3 but compact is practically same platform 8974
First build ready at G+
ok
No issues here. ROM runs smooth and speedy. So far no bugs (although ill report any if ill find some). Thanks a lot for your work.
Edit: I was expecting the same issues with wireless and signal like in Cyanogenmod´s nightlies. But no! Everything is absolute OK. No issues, no hangings. Everything runs flawelessly. I even think that camera is better than CM´s/Mokee´s etc. Really GREAT job!
Carach_CZ said:
No issues here. ROM runs smooth and speedy. So far no bugs (although ill report any if ill find some). Thanks a lot for your work.
Edit: I was expecting the same issues with wireless and signal like in Cyanogenmod´s nightlies. But no! Everything is absolute OK. No issues, no hangings. Everything runs flawelessly. I even think that camera is better than CM´s/Mokee´s etc. Really GREAT job!
Click to expand...
Click to collapse
Can you briefly tell what aspect of the camera might be better? The noise? Or the fish-eye effect? ...or colors? Maybe you could upload one image... that would be great!
Thank you!
tomcatoggo said:
Can you briefly tell what aspect of the camera might be better? The noise? Or the fish-eye effect? ...or colors? Maybe you could upload one image... that would be great!
Thank you!
Click to expand...
Click to collapse
i have the fish-eye effect on that rom!
New build ready at G+ enjoy
davidteri91 said:
New build ready at G+ enjoy
Click to expand...
Click to collapse
Changelog please
shakkirk said:
Changelog please
Click to expand...
Click to collapse
Inside in ROM
Hey David,
is there any way how to increasy camera quality (noise in photos are horrible - many, many black dots everywhere )? If not, id have to use Rectify ROM (once Mutant make it with DRM keys mod integrated). Anyway, i really love your ROM.
New build available .. Enjoy
Looks nice, but still I dont know what to do first. I have z3 compact with LB, so i have to unlock first and then what? does I have to root first and install recovery?
goodvsbad said:
Looks nice, but still I dont know what to do first. I have z3 compact with LB, so i have to unlock first and then what? does I have to root first and install recovery?
Click to expand...
Click to collapse
Unlock,flash boot.img inside zip,flash multirom twrp recovery (you can use it with one rom only if you want),wipe, flash rom and gapps from recovery, go
where is download link?
Before to start flashing
This is an UNOFFICIAL version of CM12.1, so this means that have bugs that i hope to fix soon. So use it carefully at your own risk. The most important thing to say, after flash this ROM,is ....
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.
Installation Guideline
Install the lastest version of TWRP (it's in uploading state and have an important update in fstab file)
Power down your phone and go in recovery mode.
Copy the ROM file in your sdcard
Make a wipe data/factory reset
Install the zip you copied
Wipe cache
Reboot
What works
First Boot
Audio
RIL
SDCARD
Tethering
LEDS
Touchpad now works
Bluetooth (partial: pairing not works)
Some else i'm testing
Light and proximity sensors, Accelerometer, Gyroscope and Magnetic sensors
What not works
Camera
GPS
NFC
SMS
Anything else i will find and fix
Screenshots and Video
In the top of the pace, section Screenshots.
Download
M4 Aqua ProjectMarshmallow Official Site
Uploading in this moment. You will see a post on my site!
Installation
Be sure to have my TWRP installed on your device. If you don't have it go to my site and download it (see download section).
Download and copy the ROM and GAPPS in the root of your SD
Boot in TWRP
Wipe your data (wipe data/factory reset in TWRP)
Install the ROM (Install... in TWRP)
Install GAPPS (see more information in the following GAPPS Section)
Reboot
GAPPS
You can download your GAPPS here. Be sure to download the ARM64 version for 5.1. The pico version is the minimal one (save more space).
Bug Channel
Please report any bug and issues here!
http://projectmarshmallow.altervista.org/bug-channel/
Both the ROM and the new RECOVERY will be uploaded on my site. Stay in touch!
XDA:DevDB Information
CyanogenMod 12.1, ROM for the Sony Xperia M4 Aqua
Contributors
tonystark88
Source Code: https://github.com/projectmarshmallow
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.10.x
Version Information
Status: Alpha
Created 2015-12-12
Last Updated 2016-04-30
Thanks for the rom, but where is the download? All I see is the download page for TWRP
Still uploading. I will advice you when finishs. Anyway its a testing ROM...not for daily use.
Does this has any problem with battery draining more than the stock rom? because this problem existed in my old ? z1 and i can't find anything related to the camera, so am asking if is it working? and any chance of porting z4 camera framework so we can use superior auto in this rom? Thanks in advance
I think is a bit premature make these kind of discussions now. When i'll make this rome stable (now it's a test build, have some reboot problems probaby lrelated to thermanager config) we can face more problems. But don't worry, any problem/idea will be faced at right time.
Awesome! Thank for your work!
Thanks for excellent work! Hope some major bugs could be fixed asap [emoji481]
Sent from my E2312 using Tapatalk
put more SS please...
WiFi not working???About Sound too??
And This is Android M or Android LP???
CyanogenMod 12 is based on android 5.x so that means this rom is lollipop
I'm waiting for the upload because the rom boot loops for a thermanager problem. Anyway i have fixed also sensors. I'm not able at this moment to offer more infos because rom boot loops. When i fix the thermanager config and rom will be stable i could be more detailed. I'm sure that RIL and 3g connection works. Wifi powers on but not reveal available Wi-Fi but i think is a configuration problem too.
Let me work guys, we are so close
Great news. Thanks God for You.Good Luck and we will wait for results
Wysłane z mojego E2303 przy użyciu Tapatalka
tonystark88 said:
I'm waiting for the upload because the rom boot loops for a thermanager problem. Anyway i have fixed also sensors. I'm not able at this moment to offer more infos because rom boot loops. When i fix the thermanager config and rom will be stable i could be more detailed. I'm sure that RIL and 3g connection works. Wifi powers on but not reveal available Wi-Fi but i think is a configuration problem too.
Let me work guys, we are so close
Click to expand...
Click to collapse
If you can force enable adb and upload the rom I'm sure that we can send you logcats to find the problems. Also, could you upload the new TWRP that is mentioned in the OP?
@tonystark88
Hi, under GPL v2 license you are required to link a copy of the kernel you used, otherwise, would be in violation of the license. Thank you.
I have taken a look at your source, would it be possible if u rebuild it with Sony's Unified Kernel? Thanks!
boylush said:
@tonystark88
Hi, under GPL v2 license you are required to link a copy of the kernel you used, otherwise, would be in violation of the license. Thank you.
I have taken a look at your source, would it be possible if u rebuild it with Sony's Unified Kernel? Thanks!
Click to expand...
Click to collapse
I'm not violating anything, i'm not reselling or forcing someone else. I don't understand all this pressure, you have all the informations you want now, you saw my sources. The kernel is the same published from sonyxperiadev. I have to fork it to my page to be in rule with GPLv2? I don't think, i think is useless.
If you want that i publish my sources (already unstable) on the first page, i don't see the problem, i will do it.
Also, i see this discussion only a waste of time that i subtract to my work.
tonystark88 said:
I'm not violating anything, i'm not reselling or forcing someone else. I don't understand all this pressure, you have all the informations you want now, you saw my sources. The kernel is the same published from sonyxperiadev. I have to fork it to my page to be in rule with GPLv2? I don't think, i think is useless.
If you want that i publish my sources (already unstable) on the first page, i don't see the problem, i will do it.
Also, i see this discussion only a waste of time that i subtract to my work.
Click to expand...
Click to collapse
It's not out of nothing, cos ur sources must be able to build. You changed one of the defconfigs to cyanogenmod_blablabla so you have to fork and make the changes on ur end as well. Hope u understand
boylush said:
It's not out of nothing, cos ur sources must be able to build. You changed one of the defconfigs to cyanogenmod_blablabla so you have to fork and make the changes on ur end as well. Hope u understand
Click to expand...
Click to collapse
It's the temp .config file generated when u build the kernel. I renamed it and used because differently from the asp defconfig is formatted well.
boylush said:
It's not out of nothing, cos ur sources must be able to build. You changed one of the defconfigs to cyanogenmod_blablabla so you have to fork and make the changes on ur end as well. Hope u understand
Click to expand...
Click to collapse
I see no problem here especially since Sony hasn't exactly released the kernel code. There is no reason to be so distrustful. Heck he hasn't even released the rom yet so what are you complaining about. Please don't take offense. He is just trying to further this community
boylush said:
It's not out of nothing, cos ur sources must be able to build. You changed one of the defconfigs to cyanogenmod_blablabla so you have to fork and make the changes on ur end as well. Hope u understand
Click to expand...
Click to collapse
Supports developers, do not lock their work
I don't understand this mentality of 'Let the dev work and do his thing' and saying that he should be given space to himself to work and build CM12 for The M4 Aqua. As it stands, you all don't know what Open Source Means. The M4 Aqua is in a state where much dev work is needed and all you guys do is hamper the speed at which developers can build ROMs for you. Without Kernel Source code and all LOCAL modifications uploaded, other devs can't jump in and help out to build for the M4 Aqua. I work mainly in the Xperia SP Forums and when the Xperia SP got released, it barely had any source code given by SONY but now we're at CM13. CM13!!!! From a 2012 device to 2015 we have gotten CM13 while YOUR M4 Aqua is stuck at even building CM12! All the Xperia SP had going for it is the AMAZING DEV support with SO MUCH OPEN SOURCE CODE that we all learnt to share. We keep the credits individual to commits and we all gave credits which were due in every rom we built.
If I can't build the ROM with what you say uses the original sony kernel source code, then this ROM is violating GPL code. I will be back soon to test the results and see if it does indeed build and churns out the exact bugs reported. If you are unable to handle even a small request that Boylush has said and say that you're already stressed out due to ONE MEASLY request then there seems to be something wrong.
Those of you who have absolutely no developer experience I would advise you to refrain from trying to defend your individual parties and let this be easily settled by simple building on my end.
I don't like these kinds of reasoning about me and about my work only because in two months other people aren't been able to boot nothing, also a recovery. This is the last time i will respond to you because this is a DEV topic, and here will be DEV things.
Furrydaus said:
The M4 Aqua is in a state where much dev work is needed and all you guys do is hamper the speed at which developers can build ROMs for you. Without Kernel Source code and all LOCAL modifications uploaded, other devs can't jump in and help out to build for the M4 Aqua.
Click to expand...
Click to collapse
I repeat this thing again, all my sources are public. Just see the first page of this topic. And also, all sources are open on sonyxperiadev and are a intellectual property of Sony. All the LOCAL modifications are on my github page, in the commit area. Just click and see.
Furrydaus said:
I work mainly in the Xperia SP Forums and when the Xperia SP got released, it barely had any source code given by SONY but now we're at CM13. CM13!!!! From a 2012 device to 2015 we have gotten CM13 while YOUR M4 Aqua is stuck at even building CM12! All the Xperia SP had going for it is the AMAZING DEV support with SO MUCH OPEN SOURCE CODE that we all learnt to share. We keep the credits individual to commits and we all gave credits which were due in every rom we built.
Click to expand...
Click to collapse
And i'm happy for the Sony XPERIA SP, this means people work together. In the case of Sony M4 Aqua i just saw topics that bumps out after i started to develop, also if only the recovery, for this device. No one sent me a message for say, "Tony let's work together".
Furrydaus said:
If I can't build the ROM with what you say uses the original sony kernel source code, then this ROM is violating GPL code. I will be back soon to test the results and see if it does indeed build and churns out the exact bugs reported. If you are unable to handle even a small request that Boylush has said and say that you're already stressed out due to ONE MEASLY request then there seems to be something wrong.
Click to expand...
Click to collapse
I'm not stressed, i feel great thanks And again no one ROM violates the GPL license. Simply because there isn't yet on the site and will not be until will complete boot correctly. And about the request, i responded yet. I have to repeat that i used the same kernel published by sonyxperiadev site WITHOUT MODIFICATIONS ?
Furrydaus said:
Those of you who have absolutely no developer experience I would advise you to refrain from trying to defend your individual parties and let this be easily settled by simple building on my end.
Click to expand...
Click to collapse
Probably in the ROMS world this sentence is true. But i'm a graduated ICT Engeneer and i worked in past in Android. Maybe i know a little bit of devel things, and i say "a little bit" because i know i can do it, and i not let you and others to offend me without know who i am.
CONCLUSION
Without me, the unexperienced, this device today has a working recovery and i hope for ALL THIS COMMUNITY a working CM12.1 . And i repeat again this thing: THE SOURCES ARE PUBLIC ON MY GITHUB AND ON THE SONYXPERIADEV GITHUB. I'm not blocking the work of anyone and i will be happy if someone else will make the rom work better and efficiently than mine. I will learn where i failed from the other devs commits, like i always did.
I hope is more clear my point of view now to avoid future noisy discussions.
CyanogenMod is a free, community built distribution of Android which greatly extends the capabilities of your phone.
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.
*/
Issues:
Camcorder only works with Footej App
HW video decoding does not work (falling back to ffmpeg right now)
...?
Things that need to be improved:
Move to OSS audio driver again (works for everything but incall audio, problem might be with libsecril-client, reverse engineering that library...)
Full Exynos display IP acceleration
Move to Mali R7P0 Marshmallow drivers (currently not working because Samsung made changes to private_handle_t in Marshmallow that need to be reverse engineered)
Clean up hacks needed for camera (scene mode override in frameworks/av)
...?
GIT repos:
https://github.com/CyanogenMod?utf8=%E2%9C%93&query=noblelte
NOTE: You *must* first flash official Marshmallow before flashing CyanogenMod 13!
Downloads:
Build 1
Builds can be flashed by your favorite recovery.
If you like my work, please consider donating a few bucks, it will help buying new devices and maintaining them (Most probably Exynos ones that no one else likes doing AOSP development on).
A *huge* shoutout to Javi Ferrer, macs18max, gladiac and others!
Without you guys the Exynos Open Source platform on CyanogenMod would not be where it is today.
XDA:DevDB Information
CyanogenMod, ROM for the Samsung Galaxy Note 5
Contributors
RaymanFX
Source Code: http://github.com/CyanogenMod
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
Version Information
Status: Testing
Created 2016-12-16
Last Updated 2016-12-16
If we keep working on this, we may get a fully working CM13/14.1 build by Q1 2017
Hopefully this doesn't get taken down like all other CM13 projects and Skyhigh kernel.
Juadolfob said:
Does it work with sm-n920g ?
Click to expand...
Click to collapse
I don't know if it work with N920G but i tried it on my N920L and i can't even flash it. TWRP never finish flashing the file and i ended up turning off the phone. If you want to try flashing it i recommend backing up first.
Edusa said:
If we keep working on this, we may get a fully working CM13/14.1 build by Q1 2017
Hopefully this doesn't get taken down like all other CM13 projects and Skyhigh kernel.
Click to expand...
Click to collapse
I already have 14.1 running (actually I had 14.0 since Nougat came out), but there are some added instabilities.
I'd rather spend time on fixing our open source gralloc so we can use the camera with that and finally move on to the proper R7P0 Mali Marshmallow blobs.
Samsung will probably drop official Nougat by then, which will make it easier for me to debug and reverse engineer.
In fact, I just fixed a really nasty bug in gralloc (which would lead to segfaults aka system crashes if you play 2-3 videos): https://review.cyanogenmod.org/#/c/177606
And no, this won't ever be taken down
Apart from providing the full kernel source, the whole platform is available for anyone to download and build.
Juadolfob said:
Does it work with sm-n920g ?
Click to expand...
Click to collapse
I honestly don't know (can't test on anything but my N920T), but you can give it a shot I suppose?
Just be sure to edit the updater-script of the zip file to remove the version check in recovery.
Just flashed! One of the quickest roms to flash! Everything works so far! TYSM
Does the in-call audio works for N920T?
Sent from my SM-N920T using XDA-Developers mobile app
Everything's working outa the box, FINALLY I GOT CM13 ON MY NOTE 5
kkk121 said:
Does the in-call audio works for N920T?
Sent from my SM-N920T using XDA-Developers mobile app
Click to expand...
Click to collapse
yes call audio works with tmobile as everything works that ive tryed good work man .
Is it possible to get s6edge+support? I like using the soft keys, lol. Great work, love the rom
Everything works ....I LOVE YOU MAN keep up the great work
Hi will i able to install on my 920c. Thx
You did a great job. Keep up the good work!!!
Hello Rayman, i've tried flashing this on n920c but it stuck in patching system image unconditionally. Any tips? thank you very much
n920C would be awesome!
Great work!
How about KLS?
4g LTE cuts in and out sometimes doesn't work ...3g 2g full works, battery drains a little too fast
Jigz737 said:
4g LTE cuts in and out sometimes doesn't work ...3g 2g full works, battery drains a little too fast
Click to expand...
Click to collapse
Try another access point
Does the kernel support F2FS?.
Awfull said:
Try another access point
Click to expand...
Click to collapse
Tried that it doesn't stick for some reason
SlimRoms is a custom android operating system. Our main goal is to offer users a slimmed down yet feature rich alternative to other android operating systems.
The entire SlimTeam work together to bring you this tailor-made beauty straight from Android Open Source Project (AOSP) source code.
All of the sources can be publicly viewed through GitHub and you can stop by our public Gerrit to submit patches of any type.
Slim7 is the project name for SlimRoms based on Android 7.1.1 Nougat and offers the following original features:
Slim Navbar & Hardware key rebinding
Single tap action, long press action, double tap action!-We’ve got you covered.
Slim Actions & Chamber of secrets
Customise your device to the fullest -You’re a wizard!
SlimRecents
A Faster alternative to stock recents -Your device, your choice.
SlimLauncher
An Open source, feature filled launcher! -Make yourself at home
Status bar customisations
Clock and Date? Battery? -More fun than you can shake a stick at.
Important links:
slimroms.org - Our official website and your source for anything SlimRoms related.
Downloads - Slimify your device!
Unofficial Downloads J500F and M - Build0.13
Unofficial Downloads J500FN - Build0.13
For information on bugs, requirements, notes and more, read the second post.
Installation instructions - Follow these steps if you want SlimRoms on your device.
FAQ - Have a question? Consider reading our FAQ first, you might find your answer there!.
Report-bugs - Found a bug? Send it our way!
Kernel Source - The source of your device's kernel.
Get in touch! - You can contact SlimRoms at these places if you have questions, requests or feedback.
Google+
Twitter
Facebook
Disclaimer: We are not responsible for any damages to your device.
Can you pour me some coffee?
XDA:DevDB Information
SlimRoms Slim7 Android Nougat, ROM for the Samsung Galaxy J5
Contributors
EsromG5
Source Code: https://github.com/SlimRoms
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Bootloader LP and Modem MM (modem mm for FM works)
Based On: Aosp, Slim
Version Information
Status: Testing
Current Beta Version: Build0.13
Beta Release Date: 2017-02-15
Created 2017-02-15
Last Updated 2017-03-04
Reserved
What works?
RIL (Calls, sms, data)
Bluetooth (also with audio)
Camcorder
Camera general (1080p works fine)
Video Playback
Dados and RIL
Wifi
Audio
Sensors
LED
Flash
Hostpot
InCall
GPS
OTG
FM (use modem MM)
What does not work?
No, you tell me
Notice:
n/a
First
Good job, waiting for FN
second ....
good job bro.. i m so lucky that I own j5f :fingers-crossed:
wooow j5 developement is skyrocking this month, i will install it when theres the proper incall audio (im not crying for fix, just sayin)
Why don't you concentrate first resolving issues on the other roms? What is the sense of releasing every kind of roms but with the same issues?
Booted on FN, but System UI has stopped
Telepracity said:
Booted on FN, but System UI has stopped
Click to expand...
Click to collapse
Without patch?
Deleted
JosephDM said:
Why don't you concentrate first resolving issues on the other roms? What is the sense of releasing every kind of roms but with the same issues?
Click to expand...
Click to collapse
WelI think it is just as good making normal roms. The in-call isue and other bugs are related across all N roms so that means that if it gets fixed on one then you'll have all the other roms fixed in a small matter of time and now you have 3 working Nougat roms instead of one non functioning rom
EsromG5 said:
Without patch?
Click to expand...
Click to collapse
With a patch from lineage os
MM kernel
Amarius1 said:
WelI think it is just as good making normal roms. The in-call isue and other bugs are related across all N roms so that means that if it gets fixed on one then you'll have all the other roms fixed in a small matter of time and now you have 3 working Nougat roms instead of one non functioning rom
Click to expand...
Click to collapse
Not at all. At the moment you have a lot of not working ROM that are not going to work, because if you look at their github, you'll see that authors most likely lack knowledge needed to make them work. Building every ROM available using the same base is a waste of time (and distraction for users) if one can't even fix your issues in one of them. Plus moving to newer version of android without having the previous one fully working is a suicide run. Nougat has a lot of complex changes in it's sources and it doesn't even fully work on some officially supported devices, so don't expect a good ROM of Android 7.1.1 anytime soon and flooding forums with multiple ROMs having the same issues is not going to help it.
Koloses said:
Not at all. At the moment you have a lot of not working ROM that are not going to work, because if you look at their github, you'll see that authors most likely lack knowledge needed to make them work. Building every ROM available using the same base is a waste of time (and distraction for users) if one can't even fix your issues in one of them. Plus moving to newer version of android without having the previous one fully working is a suicide run. Nougat has a lot of complex changes in it's sources and it doesn't even fully work on some officially supported devices, so don't expect a good ROM of Android 7.1.1 anytime soon and flooding forums with multiple ROMs having the same issues is not going to help it.
Click to expand...
Click to collapse
Well... You are right sir. In-call audio is really really important and I wish someone knew why it was happening..
I didn't mean in call audio. I meant this ROM doesn't even boot normally and they have no clue why, yet instead of trying to debug they release bunch of not working builds. Camera doesn't work and it will not work since you'd either have to use updated open source HAL or revert Nougat media changes and it won't be a surprise if I'll tell you they have no idea how to do it. The only real devs, who knew what they were doing left because their work was posted by someone else and now he's making blind commits in hope that things will magically fix themself. They won't. I might as well tell you that development on J5 is dead unless someone new with actual knowledge steps in. Don't expect any significant changes. We can't even take patches from any other msm8916 devices, because they have more advanced development and use a lot of open source projects instead of prebuilt libs like we do. Even camera in CM13 is not fully fixed because open source cam doesn't work for us and after debugging it for 3 weeks I've still didn't come up with reliable solution to make it work (only made some errors dissapear).
Koloses said:
Not at all. At the moment you have a lot of not working ROM that are not going to work, because if you look at their github, you'll see that authors most likely lack knowledge needed to make them work. Building every ROM available using the same base is a waste of time (and distraction for users) if one can't even fix your issues in one of them. Plus moving to newer version of android without having the previous one fully working is a suicide run. Nougat has a lot of complex changes in it's sources and it doesn't even fully work on some officially supported devices, so don't expect a good ROM of Android 7.1.1 anytime soon and flooding forums with multiple ROMs having the same issues is not going to help it.
Click to expand...
Click to collapse
You're not totally sure.
Creating new roms is just to try to see if there are different results and not just to flood the forum with crap.
The name of the forum is XDA - DEVELOPERS, this means that it is of full use to developers, if the person does not know how to help, it just stays silent while someone else can do it. Your help in testing is much appreciated since we are trying to do something free for you, and still prefer to say things like that.
I thank you and respect your concept, but try to help instead.
Amarius1 said:
Well... You are right sir. In-call audio is really really important and I wish someone knew why it was happening..
Click to expand...
Click to collapse
The problem with incall and other stuff is already encountered by SoUnd001, but the big problem is that we're not hitting what it does so it's not booted, you're getting errors with incall and stuff because of the patch you're installing, not because of Rom or current kernel.
NOTICE:
I'm finishing a build for J500FN, we know it may not start properly, but I want to know the result for these users. I hope the sooner I have it all working.
Koloses said:
Not at all. At the moment you have a lot of not working ROM that are not going to work, because if you look at their github, you'll see that authors most likely lack knowledge needed to make them work. Building every ROM available using the same base is a waste of time (and distraction for users) if one can't even fix your issues in one of them. Plus moving to newer version of android without having the previous one fully working is a suicide run. Nougat has a lot of complex changes in it's sources and it doesn't even fully work on some officially supported devices, so don't expect a good ROM of Android 7.1.1 anytime soon and flooding forums with multiple ROMs having the same issues is not going to help it.
Click to expand...
Click to collapse
Considering our device only has Marshmallow we can afford to deal with some bugs. If i read correctly RR 6.0.1 only has the radio bug so we have a working Marshmallow rom. The next logical step is to make Nougat and they do not have a kernel thats Nougat based so thats why they are running into problems and why we have to use patches. Im almost 100% sure that once we get official Nougat to our device, 99% of the bugs in these roms will disappear
[email protected]@!3Z said:
Considering that they have built nougat from source when our device only has Marshmallow we can afford to deal with some bugs. If i read correctly RR 6.0.1 only has the radio bug so we have a working Marshmallow rom. The next logical step is to make Nougat and they do not have a kernel thats Nougat based so thats why they are running into problems and why we have to use patches. Im almost 100% sure that once we get official Nougat to our device, 99% of the bugs in these roms will disappear
Click to expand...
Click to collapse
I think there will not be an official nougat firmware from Samsung.
Gent' said:
I think there will not be an official nougat firmware from Samsung.
Click to expand...
Click to collapse
In the Skies telegram group there was confirmation for official Nougat
EsromG5 said:
You're not totally sure.
Creating new roms is just to try to see if there are different results and not just to flood the forum with crap.
Click to expand...
Click to collapse
FYI: ALL custom ROM are using the same hardware repo's maintained by CAF, CM(Lineage now) or AOSP. There won't be any different results. The most important repos are all the same. The fact that you don't know that and your friend's github sources show that there is nothing to be helped. You're just playing games with users pretending you could make things work. What for? In the end they will be the ones left with nothing but promises. People, who could actually do something left, because someone took their work and published it to take all the applause for it and now you're blindly trying changes hoping they would somehow fix things.
[email protected]@!3Z said:
Considering that they have built nougat from source
Click to expand...
Click to collapse
They built from the source already made by ganesh. Their own changes are blindly trying things that have no right to work in the first place. Builiding android from someone's ready sources is like walk in a park.
Gent' said:
I think there will not be an official nougat firmware from Samsung.
Click to expand...
Click to collapse
Certainly not for J5 2015, maybe 2016 but it could benefit us anyway since these devices are similiar.
I'm done, Moderator will probably soon come and delete my posts since all they care about is keeping forum clean. You may consider this device dead at the moment.
[email protected]@!3Z said:
Considering that they have built nougat from source when our device only has Marshmallow we can afford to deal with some bugs.
Click to expand...
Click to collapse
I understand from your post that Sound001 or EsromG5 did the hard work, but its not like that.
@Nick Verse and @ganesh varma were the ones who built cm12.1 and cm13 from source. They were also working on cm14 source while they were working on cm13.
So, please edit your post and dont mislead people.
Koloses said everything.
Since Nick and Ganesh left J5 development because their project which were working on was posted by someone else, the issues of Nougat CM/AOSP based roms wont be solved.
This:
I might as well tell you that development on J5 is dead unless someone new with actual knowledge steps in.
Click to expand...
Click to collapse
Code:
/*
* Your warranty is... still valid?
*
* 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.
*
*/
The main purpose of this thread is to unify all the useful web links, mainly other XDA threads, that contribute to improve and expand the development, guides, discussions and all other useful sources of data related to our device.
"HOW DO I KNOW IF THIS IS MY DEVICE?"
The device we are talking about here is a Huawei Mediapad T1 10, which consists in at least 3 different variants:
- LTE variant (T1-A21L)
-WiFi variant (T1-A21W)
-LTE chinese variant (T1-A23L)
They are exactly the same device in terms of hardware and software (this one vary a little), the only difference is that one has SIM slot (T1-A21L) and the other one no (T1-A21W).
An important point to keep in mind is the codename of our device, which is a technical name all Android device have and which identify exclusively to the device. This is very usual in development threads such as ROMs and Recovery threads, so you might see it in the thread title.
The codename of our device is hwt1a21l
-Technical information of our device. Specs are from the LTE variant but it applies for the WiFi variant expect for the SIM slot: [url]http://m.huawei.com/ukmobile/consumer/tablets/detail/mediapad-t1-10-uk.htm[/URL]
If you still have doubts about this topic i suggest you to ask you doubts or check other people's doubts.
RULES:
1- Please only discussions related to our device (Huawei Mediapad T1 10 T1-A21L/T1-A21W). See previous paragraph to know if you own this device.
2- If you want to report an issue or any other subject related to an existing rom, recovery or other subjects try to keep the conversations in the respective thread of what you want to talk. It's not mandatory but it's a good way to keep conversations in the proper thread so other people can check it.
3- Try to keep clean and proper conversations when posting in this thread.
ROMS:
- EMUI 3.0 Light: [url]https://forum.xda-developers.com/huawei-mediapad/development/rom-emui-3-0-light-mediapad-t1-10-t3609602[/URL]
- CarbonROM KK (Unofficial): [url]https://forum.xda-developers.com/huawei-mediapad/development/rom-carbonrom-mediapad-t1-10-t3662497[/URL]
RECOVERIES:
- Philz Touch 6.59.0: link
- TWRP: link
ROOT:
- SuperSU for EMUI 3.0 (may be valid for other ROMs): link. Credits to @mann1
MODS/OTHER DEVELOPMENT RELATED TOPICS:
WIP.
STOCK FIRMWARE:
-EMUI 3.0 Stock ROM (V100R001C232B009CUSTC100D001 for T1-A21w & V100R001C100B013CUSTC100D001 for T1-A21L) : link
HOW TO UNLOCK THE BOOTLOADER:
WIP.
UNBRICK THE DEVICE:
WIP.
Created 18/05/2017
Last update 23/02/2018
reserved
Updated post with a new ROM (EMUI 3.0 Light).
For those who pricked their devices and and have stuck in boot loop after rooting or trying new custom recovery, they need the stock BOOT or RECOVERY images from here.
Thanks, I love this.
I had my pc broken quite amount of time and i could not work on some roms that i was testing. I was planning to upload CarbonROM Kit Kat for our device, but unfortunately i see a lack of users activity for this device which makes me think that maybe it is not very relevant to create and upload the builds (which takes much more time than what it seems, and my time for this activities is quite limited).
If i see more interest for this then i could upload the rom, and maybe future ones.
MIRACAST
Hola podría alguien decirme como puedo activar el miracast en mi tablet huawei t1-a21l .
mustang_ssc said:
I had my pc broken quite amount of time and i could not work on some roms that i was testing. I was planning to upload CarbonROM Kit Kat for our device, but unfortunately i see a lack of users activity for this device which makes me think that maybe it is not very relevant to create and upload the builds (which takes much more time than what it seems, and my time for this activities is quite limited).
If i see more interest for this then i could upload the rom, and maybe future ones.
Click to expand...
Click to collapse
Dear mustang_ssc, I don't know if you are still wondering about usefulness of uploading CarbonROM KitKat for th t1 10 ? There is an important interest from my side for more than 1 device.
If I can be of any help to avoid important workload to you, I ll be pleased to contribute.
emmanuelix said:
Dear mustang_ssc, I don't know if you are still wondering about usefulness of uploading CarbonROM KitKat for th t1 10 ? There is an important interest from my side for more than 1 device.
If I can be of any help to avoid important workload to you, I ll be pleased to contribute.
Click to expand...
Click to collapse
@mustang_scc
+1 to that. I have the stock rom with root access.
The tablet mainly sits and collects dust right now so I wouldnt mind using it for testing.
Let me know if I can help.
emmanuelix said:
Dear mustang_ssc, I don't know if you are still wondering about usefulness of uploading CarbonROM KitKat for th t1 10 ? There is an important interest from my side for more than 1 device.
If I can be of any help to avoid important workload to you, I ll be pleased to contribute.
Click to expand...
Click to collapse
Apexaddicted said:
@mustang_scc
+1 to that. I have the stock rom with root access.
The tablet mainly sits and collects dust right now so I wouldnt mind using it for testing.
Let me know if I can help.
Click to expand...
Click to collapse
Though the bug are not solved yet, I will probably open a thread for the rom this weekend so people interested like you can install it, test it or keep it on his tablet without mind the current bugs.
I will keep you informed
The CarbonROM KK is ready for testing purpouses, i need testers. @emmanuelix , @Apexaddicted , @PinkOstrich or anyone who owns the LTE variant who would like to test it, please send me a PM.
PD: sorry for the delay about this, i was quite short of time and also had to port it again because i realized i lost all the ROMs when i formated my hard drive disk.
Deleted:
Duplicated post.
Sorry but I only own the WiFi version.
Apexaddicted said:
Sorry but I only own the WiFi version.
Click to expand...
Click to collapse
Don't worry, i will open the thread and people with the WiFi variant will be able to download it. I want people with the LTE one to test it because i own the WiFi Varian as well.
Also a reminder for everyone:
Keep in mind that the rom still has some few critical bugs which you may not be happy to flash the rom. The main bugs are:
-Camera not working
-Notification led not working
-Weird bug with the Play Store which does not allow to use it unless, on my experience, you wait for about 1 day to be able to use it.
mustang_ssc said:
Don't worry, i will open the thread and people with the WiFi variant will be able to download it. I want people with the LTE one to test it because i own the WiFi Varian as well.
Also a reminder for everyone:
Keep in mind that the rom still has some few critical bugs which you may not be happy to flash the rom. The main bugs are:
-Camera not working
-Notification led not working
-Weird bug with the Play Store which does not allow to use it unless, on my experience, you wait for about 1 day to be able to use it.
Click to expand...
Click to collapse
Thank you @mustang_ssc. I only own the Wi-Fi version also, sorry !
I have finally posted the ROM (CarbonROM). As mentioned it has not been tested on the LTE variant, but it should work properly as the Wi-Fi one.
Link: https://forum.xda-developers.com/huawei-mediapad/development/rom-carbonrom-mediapad-t1-10-t3662497
mustang_ssc said:
I had my pc broken quite amount of time and i could not work on some roms that i was testing. I was planning to upload CarbonROM Kit Kat for our device, but unfortunately i see a lack of users activity for this device which makes me think that maybe it is not very relevant to create and upload the builds (which takes much more time than what it seems, and my time for this activities is quite limited).
If i see more interest for this then i could upload the rom, and maybe future ones.
Click to expand...
Click to collapse
I would definitely appreciate it!
hooligan333 said:
I would definitely appreciate it!
Click to expand...
Click to collapse
You have the link for the rom on the previous post.
Alright, have good and bad news, let's start with the good one:
I have a completely working 5.1.1 Android ROM (EMUI 3.1) from the T1-A23L which works on the LTE and Wi-Fi variants (T1-A21L & T1_A21W), big thanks to @tenderVeteran who sent me this ROM and informed me about it. This means we finally have Lollipop for our device and we have the possibility to port another Lollipop ones.
The bad new is that i need to make it flashable but for some reason it does not boot. I need some more time to figure out about a solution on this topic and i will publish it as soon as i get it booting.
Glad to hear about the progress! Cant wait to try it out. Please let us know if there is anything we can do to help.
Additionally...Ive been looking for ways to compile a custom kernel for the mediapad. Have you tried this yet?
Rob