{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 11 (R), which is designed to increase performance and reliability over stock Android for your device.
LineageOS 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). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Base source code is available in the LineageOS Github repo. And if you would like to contribute to the project, please visit our Gerrit Code Review.
GPL compliance:
Device tree source code: LineageOS/android_device_fxtec_pro1
Kernel source code: LineageOS/android_kernel_fxtec_msm8998
Working:
Camera (and flashlight)
WiFi
NFC
Bluetooth
Telephony (Calls and Data)
IMS (RCS, VoLTE and WiFi Calling)
Audio (Record and Playback)
Video Playback
Sensors
GPS
Encryption (FBE)
Built-in keyboard
Broken:
WiFi Display
Compatibility:
Compatible with all F(x)tec Pro1 variants.Builds are based off the F(x)tec's Android 9 firmware with proprietary blobs from 20200825231445 package.
Downloads:
Official download links
Notice:
No custom kernels are supported in this thread. Only stock kernel and official builds will be supported. No bug reports if that's not the case.
Installation:
Refer to the official Wiki (link bellow)
Credits & collaborations:
Special thanks to tdm and mccreary for early bringup. All LineageOS team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
Device wiki:
Official wiki link
Oh you are fast. A few days after Q R is coming, great.
nift4 said:
Oh you are fast. A few days after Q R is coming, great.
Click to expand...
Click to collapse
Yea, well... I did lineage-18.0 bringup even before moving the device to official lineage-17.1 weeklies. :laugh: Only decided to share now because lineage-18.0 is already rock solid and can perfectly be used as daily driver.
Today i did some flashing and noticed that you can't read the sd card from the 18 recovery.
bgcngm said:
Downloads:
lineage-18.0-20201115-UNOFFICIAL-pro1.zip
Click to expand...
Click to collapse
Thanks. Do you have a recovery/boot.img also, that I can use to flash this? Or can I use the 17.1 from the LOS repo?
I tried, it complains about mismatching signature, then, depending on date it complains about downgrading, and at the end, installation fails. (With kDownloadMetadataSignatureMismatch)
Do you have a v18 boot.img fitting (signature/version) your provided zip file?
@Kaustubhx, @khusika, @Wheeljack2k, @shubell, @nift4: how did u make use of this upload?
it is an 17.1 unofficial image but it works for flashing
https://drive.google.com/file/d/1lEuEmJ9q5-_kVd7pRS1lzv6-YTbIUesK/view?usp=sharing
and if you need gaps
Thanks, that did it.
lefr0nk said:
Thanks, that did it.
Click to expand...
Click to collapse
well you could get the boot image by extracting it from the image file with payload_dumper
lefr0nk said:
Thanks. Do you have a recovery/boot.img also, that I can use to flash this? Or can I use the 17.1 from the LOS repo?
I tried, it complains about mismatching signature, then, depending on date it complains about downgrading, and at the end, installation fails. (With kDownloadMetadataSignatureMismatch)
Do you have a v18 boot.img fitting (signature/version) your provided zip file?
@Kaustubhx, @khusika, @Wheeljack2k, @shubell, @nift4: how did u make use of this upload?
Click to expand...
Click to collapse
I didn't I still am on Q
Any word on if IMS will wind up working in the near future? I'm stuck on Verizon through work, and I won't be able to make any calls without.
altomes said:
Any word on if IMS will wind up working in the near future? I'm stuck on Verizon through work, and I won't be able to make any calls without.
Click to expand...
Click to collapse
Yes, VoLTE has been fixed already. Sadly, WFC is still dead. Just wait for the next build.
New build is up. Since this is based on the new AOSP feature drop, it's now Lineage 18.1. Enjoy.
New build works, volte working. The only issue is that the exists is with gapps (threre are no good ones yet), so if you don't use them the build is great. Upgrade from 18 worked. Open_gapps-arm64-11.0-micro-20201116-TEST which are the latest ones prevent you from booting, missing some permissions.
Recovery also fixed, you can select updates from sdcard again.
Nikgapps work, magisk works
Bought my wife a new phone and confiscated her Pro1, since she wasn't using the keyboard anyway (ghosting bug). Sick and tired of waiting on my phones (since september).
Anyway, took the plunge. Running LoS 18. Curious as to what I will find. Thanks to all!
After a day's use:
Physical camera button doesn't do anything (not that I ever used it). My bad, had to program it, works with all installed camera apps, nice!
One time the Caps lock LED got inverted, reboot fixed that.
Nice to see the fabulous camera app is still in use :s
Text ghosting gone (issue on LoS 17 for me and some others)
One nuisance; I use Swiftkey and used the shortcut bar for emoticons in Hangouts. But the Swiftkey bar doesn't show under/in Hangouts. Strangely enough it shows up in all other apps!!! It also shows you text predictions (landscape + physical keyboard). I'm assuming this will never be fixed since I'm probably on of the last that uses Hangouts.
So far so good
@shubell
Running your version and Nikgapps Omni, the dialer (call-interface) doesn't show when calling. I can call someone, but I do not see that the call is being made. No in interface, no dialer, can't hang-up... But the calls do succeed.
And I cannot accept a call since the dialer doesn't show up...
Die Bruine said:
So far so good
@shubell
Running your version and Nikgapps Omni, the dialer (call-interface) doesn't show when calling. I can call someone, but I do not see that the call is being made. No in interface, no dialer, can't hang-up... But the calls do succeed.
And I cannot accept a call since the dialer doesn't show up...
Click to expand...
Click to collapse
hmm strange, had no problems, try updated ones NikGapps-omni-arm64-11-20210104.zip
New build is up, with this month's Android security fixes already included and working WiFi calling.
I was down for a couple of days (torn muscle). Just tried new Omni and that did the trick, thanks.
Your version doesn't support HD-Audio over Bluetooth. And I'm having some issues with CAPS-lock interference with Swiftkey (always on). Also that little nuisance of me not being able to get that Swiftkey overlay under Hangouts.
Just downloaded lineage-18.1-20210105-UNOFFICIAL-pro1.zip, flashing now. By the way, haven't had a single issue apart from mentioned above.... Daily driver for me, heavy user I might add. Ow, Maps doesn't work. But judging by the response in the store, I don't think it's a LoS-issue. After first use I have to uninstall it.
But, let's just ignore it all. Updating to lineage-18.1-20210105-UNOFFICIAL-pro1.zip and flashing Omni again....
Update from shubell's version didn't go well, bootloop. Then I sideloaded both slots (reboots) flashed omni both slots. Now it's alive again. But some Google apps die out on me. I have to re-install them (clear cache didn't work).
By the way, how and /or why do you clear cache? Where is it located now? I thought it changed/merged starting form 10 or 11. So clearing cache wouldn't do JS right!?
bgcngm said:
New build is up, with this month's Android security fixes already included and working WiFi calling.
Click to expand...
Click to collapse
bgcngm tnx for all the hard work btw. Vowifi works made quite a few calls using it but sometimes it behaves strange... that vowifi volte switching thingy.
Die Bruine said:
doesn't support HD-Audio over Bluetooth.
Click to expand...
Click to collapse
Checked the bluetooth audio codecs and the only not grey-outed option is the basic SBC codec.
Don't really know how many options were on LOS 16 and my bluetooth device.
So basically if the HD-Audio option is also not availiable only the basic SBC version works and not the improved SBC-XQ
shubell said:
Checked the bluetooth audio codecs and the only not grey-outed option is the basic SBC codec.
Don't really know how many options were on LOS 16 and my bluetooth device.
So basically if the HD-Audio option is also not availiable only the basic SBC version works and not the improved SBC-XQ
Click to expand...
Click to collapse
HD audio is available and the codecs will appear and can be selected if device and headset support it. As far as it concerns to SBC-XQ, that wasn't ported over.
Seeing is believing I guess. Took me a couple of days, but I managed to try out two headsets and two receivers. None of them switch to LDAC. My ORA headset for example did switch to LDAC on LoS 16. Since I have no experience with LoS 18 and HD-audio I wouldn't know if there is a toggle switch. But under LoS 16 there was the option of HD-Audio under Bluetooth settings.
Also, I tried all different combinations of BT AVCR/MAP and re-pairing. LDAC does not show up in my case. It's worthy mentioning that all products I use (surely three out of four) use the CSR8675. So I'm guessing the handshake between LoS 18 and CSR8675 to switch to LDAC isn't going very well. Too bad, but I can live with that.
I do believe though, that the low brightness black values are of a lower quality than on LoS 16. I know this is an OLED-issue. But I can't recall it being this bad on my stock and LoS 16. Next week I hope to receive an additional unit on which I can test this.
Apart from Google apps crashing (gapps-issue easily resolved by manual de/re-install via Play Store) and the occasional CAPS-lock-issue (99% due to my usage of Swiftkey), I have absolutely no bugs to report as a heavy daily user. The latter is more a nuisance than a bug. Same goes for my delayed Hangouts messages, inability to connect via LDAC, always first-time-closing-Chrome (FireFox-user) and my wish for the floating Swiftkey-bar in Hangouts (which doesn't only in Hangouts ). And of course the ridiculous camera app and quality. Several decades ago I bought CameraZoomFX and forgot all about it. Now i'm using it again on this phone .
Thank you for the ROM. I see absolutely no reason to be running LoS 17.1 apart from it being official that is...
Related
SlimRoms is a custom android operating system. The main goal is to offer users a slimmed down but still 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 the public Gerrit to submit patches of any type.
SlimKat is the project name for SlimRoms based on Android 4.4 and offers the following original features:
The Real Dark Slim
Full system-wide dark interfaces. - If you like it smooth and classy.
Custom Shortcuts. Everywhere.
Hardware keys, Navigation Ring, Navigation Bar, Lockscreen, Tiles, Notifications etc. - We've got you covered.
System-Wide Keyboard Controls
Rotation, cursor control, optional emoticions, etc. - You'll be tapping away to your heart's content.
SlimCenter
Downloads, contact information, system app removal. - More fun than you can shake a stick at.
Camera Features
Trueview, Smart Capture. - Capture life moments with ease.
Important links:
slimroms.net - The official webpage where you find everything you need to know about SlimRoms.
Downloads - Download the rom, gapps and other addons.
Installation instructions - Follow these steps to the letter if you're about to install SlimRoms on your device.
Latest Changelog - Read here if you want information on changes in latest build.
FAQ - The most frequent asked questions with answers.
Kernel Source - The source of your device's kernel.
Get in touch! - Contact SlimRoms at these places if you have questions, requests or feedback.
Google+
Twitter
Facebook
Forum
Disclaimer: SlimRoms are not responsible for any damages to your device.
XDA:DevDB Information
SlimKat, ROM for the ONEPLUS ONE
Contributors
kufikugel, SlimRoms, Tylog
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: AOSP
Version Information
Status: Beta
Created 2014-07-21
Last Updated 2014-07-21
Hey guys,
will do a short introduction here due that we have especially on the One plus one a lot android newcomer. 3 weeks ago we got contacted by One plus if we want to be a recognized ROM for the 1+1. Of course it is a pleasure to support this awesome phone. So they send us the device and we worked on it the last 2 weeks.
Short note to SlimRoms as a whole....we are an AOSP based ROM. We are one of the rare roms which still develop a lot themselves. We have a user base around 1 million ppl. A lot in the custom rom scene already know and used a lot of our features on SlimKat as well on other roms. Even you guys on the CM11S stock firmware are already using 2 slim features (Privacy Guard Manager and forward/reverse lookup on the dialer and some other minor things). As well we use features from CM. Thats open source....we share our work and try to improve the things together. That being said, our main aim (and we are known) is to be as stable as possible. We have a clear vision of how our custom rom should be....and with a lot fun we try to achieve it to make us and a lot other ppl happy. We are always open for new suggestiongs or features....just raise them up and we can discuss them and see what we can do with it. But we are not a rom which kangs simply things from others. We basically want to have original ideas and with the ideas and the feedback of our users we will develop it then. So please do not start to we want to have this and that feature from this and that ROM.
SlimKat is in a lot parts pretty different then CM. Some features we do not have.....other features CM does not have. We have just two different ideas of an custom android OS. Both is good and fantastic....just different And this counts of course for every other original development rom like PA, Omni or AOKP.
Aside the original features mentioned in the first post....we have some other original features nowadays: SlimRecents, SlimPie, Slim heads up, Shake events, Chamber of Secret and a lot lot more.
A small word to myself...I am one of the main developers in SlimRoms and leading the development team we have. I like to have OT in my threads as well serious deep discussons about development (check the SlimKat hammerhead thread on xda....thats for me the perfect thread )
And now a last word to SlimKat
1. Read the above linked FAQ...as I said we are different....and this FAQ answers a lot questions. Especially the question about our lower default DPI (which can be changed of course) or that root is disabled by default.
2. Use and please only use our gapps (to get the google gapps like on stock) with SlimKat. On the website we have stable addons and beta addons (which are always on the bleeding edge). Basically both are stable.....so use the latest beta gapps.
3. Which leads me to the release schedule we do. We have every week a weekly. This are builds from latest source automatically builded. They can contain minor bugs but are known to be as stable as the stable build. Every 4-5 weeks we release a stable build for all supported devices. The difference is that they go to internal testing for some time so that our huge tester crew can give the OK that this build can be called as stable.
4. If you get a bug....please refer to the Bugreport section on the website. There it is exactly explained how to report a bug and how to do a bugreport. We have tools which will help you in this case. After that just report this on one of our official channels. We have a team off ppl who will either help you or recognize it as a bug and will throw it into our internal bug tracker.
5. Of course this device is pretty new.....slims code is in some parts pretty different to CM's....so I needed to adapt and change some stuff on CM's device tree to have it working with our source code. That beeing said the first build may have bugs we did not saw till now. We tested deeply everything and it seems to be all perfect...but that does not mean we know every device specific problem which may exist. Especially due that our tester team for bacon is at the moment not that big. But I hope that can change pretty fast
6. Which leads me to the known bugs: Till now only thing we know is that the mic level is a bit low on BT calls and with speaker phone. Headphones and normal phone mic level is completely ok.
7. Kernel....slim comes on most phones with an own kernel based on the stock kernel. Same here on bacon. Basic stuff I did this week on it. So give it a run and do not flash directly another one
8. And last one.....have fun....hoping for a nice thread here....as I said please always read the stuff on the website...FAQ, install instructions, change log etc etc etc
Thanks for your attention and lets slim up our bacon,
Lars
And third post for actual notes:
1. Currently I recommend Philz recovery. Seems to be the best working at the moment for the bacon
2. Do not forget to read the install instructions
:victory: Glad to see this here. Thanks!
Glad to see slim Kat, the more roms the merrier.
Sent from my One using Tapatalk
I am coming from nexus 5 to opo , my go to rom of choice was slimkat or nexus 5 .
I am so happy you guys are supporting opo as well cant wait for the download link
digweed4me said:
I am coming from nexus 5 to opo , my go to rom of choice was slimkat or nexus 5 .
I am so happy you guys are supporting opo as well cant wait for the download link
Click to expand...
Click to collapse
well say thanks to OnePlus They contacted us :good:
Waiting for the build..
And thanks to the op and opo ^^
Welcome to OPO, slimteam
If I understood correctly, you made and AOSP tree for bacon ???
(Every other rom is CM based so far, since omni removed their -non working- build)
kufikugel said:
well say thanks to OnePlus They contacted us :good:
Click to expand...
Click to collapse
most polished rom on nexus 5 and other devies for sure.
Aosp is better than cm we need aosp roms and kernel
Pinch Me I'm Dreaming . Can't wait for my oneplus one
Sent from my Nexus 5 using XDA Free mobile app
Damn can't wait !
bud77 said:
Welcome to OPO, slimteam
If I understood correctly, you made and AOSP tree for bacon ???
(Every other rom is CM based so far, since omni removed their -non working- build)
Click to expand...
Click to collapse
Well that is not so easy to answer....basically we have 3 parts
The base which is pure aosp and has nothing in common with cm.
Then there are hardware related repos. Due that opo is a qcom device it uses heavily caf based hardware repos (BTW aosp is doing this as well). But for opo we need to have some things which are ahead of current aosp source. Of course all ROMs share more or less the same caf code on this part.
Well and you have the device trees and kernel. Like on every device we try to use what the manufacture gives us. Just this time it is CM. But we are on the above mentioned hardware trees on some parts very different. Good example is the BT stack. We use for "caf" devices a completely other then cm which is more near to the aosp BT stack. Of course I needed to adapt this and changed the device trees accordingly. Other example is msim which we do not support at all. Needed to remove the tights to it and replace eg the location provider with the aosp one....etc etc.
To start to bring up a device tree from ground up would not make any sense....it is just double work and at the end you have the same. On Google devices eg we do not do this as well. We use what we get and then we start to change it for our needs and improve it. When you check SlimROMs github for the opo device trees you see that I changed quiet a lot already. Thing which still needs work is the kernel.
You can see here what is done till now:
https://github.com/SlimRoms/device_oneplus_bacon/commits/kk4.4
https://github.com/SlimRoms/device_oppo_msm8974-common/commits/kk4.4
https://github.com/SlimRoms/device_oppo_common/commits/kk4.4
And kernel which got most changes (4 or 5 pages of commits and fixes)
https://github.com/SlimRoms/kernel_oneplus_msm8974/commits/kk4.4
But yeah we will still work on the device tree and especially kernel. Want to change some things still.
Hope that answered your question
kufikugel said:
Well that is not so easy to answer....basically we have 3 parts
The base which is pure aosp and has nothing in common with cm.
Then there are hardware related repos. Due that opo is a qcom device it uses heavily caf based hardware repos (BTW aosp is doing this as well). But for opo we need to have some things which are ahead of current aosp source. Of course all ROMs share more or less the same caf code on this part.
Well and you have the device trees and kernel. Like on every device we try to use what the manufacture gives us. Just this time it is CM. But we are on the above mentioned hardware trees on some parts very different. Good example is the BT stack. We use for "caf" devices a completely other then cm which is more near to the aosp BT stack. Of course I needed to adapt this and changed the device trees accordingly. To start to bring up a device tree from ground up would not make any sense....it is just double work and at the end you have the same. On Google devices eg we do not do this as well. We use what we get and then we start to change it for our needs and improve it. When you check SlimROMs github for the opo device trees you see that I changed quiet a lot already. Thing which still needs work is the kernel.
You can see here what is done till now:
https://github.com/SlimRoms/device_oneplus_bacon/commits/kk4.4
https://github.com/SlimRoms/device_oppo_msm8974-common/commits/kk4.4
https://github.com/SlimRoms/device_oppo_common/commits/kk4.4
And kernel which got most changes (4 or 5 pages of commits and fixes)
https://github.com/SlimRoms/kernel_oneplus_msm8974/commits/kk4.4
But yeah we will still work on the device tree and especially kernel. Want to change some things still.
Hope that answered your question
Click to expand...
Click to collapse
You answered much more than I hoped
I will check all this in the morning
Thank you
Sent from my One
bud77 said:
You answered much more than I hoped
I will check all this in the morning
Thank you
Sent from my One
Click to expand...
Click to collapse
well I can answer it short.....no we do not track 50%-80% of CM repos like most other roms
BTW what I love most on this device is really the battery life.
Here from last 7h and still 50% left ... but without sim today and permanent wifi (with sim and full use I get 24h uptime and 7h SOT without a problem)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
kufikugel said:
BTW what I love most on this device is really the battery life.
Here from last 7h and still 50% left ... but without sim today and permanent wifi (with sim and full use I get 24h uptime and 7h SOT without a problem)
Click to expand...
Click to collapse
Whyyyyyyyyyyyy You people do That... Know, i shall not sleep....
have been a slim User since.. i dont know..
can you please... tell me if some of the exclusive apps Like(audioFX, Gallery and Camera) work on SK?
Please say yes...
dj_suca said:
Whyyyyyyyyyyyy You people do That... Know, i shall not sleep....
have been a slim User since.. i dont know..
can you please... tell me if some of the exclusive apps Like(audioFX, Gallery and Camera) work on SK?
Please say yes...
Click to expand...
Click to collapse
Honestly no idea due that I did not test it.
But the gallery is an app you can get on the play store...so no reason that it should not work.
Camera on opo does not have any real special tights into the framework which the other devices do not use as well....I assume it will work.
And audioFX absolutely no idea.
kufikugel said:
Honestly no idea due that I did not test it.
But the gallery is an app you can get on the play store...so no reason that it should not work.
Camera on opo does not have any real special tights into the framework which the other devices do not use as well....I assume it will work.
And audioFX absolutely no idea.
Click to expand...
Click to collapse
as soon the rom became available i will try it.. and test it... tnks for the hardwork...:good::good::good::good::good::good::good::good:
Oh yeah! at last. Since I received my 1 +1 every day looking to see if it appeared slimkat. And finally here it is. I love you more than my phone Thanks.
---------- Post added at 12:55 AM ---------- Previous post was at 12:49 AM ----------
Are DPI low as always?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The Pure Nexus Project
Disclaimer:
We are not responsible for anything that may happen to your phone as a result of installing custom roms and/or kernels. you do so at your own risk and take the responsibility upon yourself.
"This is a user friendly thread. All feature requests will be heard and considered. I am not against anything that doesn't stray too far away from the original idea of the ROM! Helping one another is also encouraged! Please be respectful and you will always be treated the same way, we are all here for a good experience."
About:
The Pure Nexus Project aims to bring stability and features to your Nexus device, while keeping Google's vision in line and not straying too far away from that. If you are looking for a stable ROM with true tested features and minimal bugs, then this is the place to be.
Keep in mind, this is an unofficial build, all credit to PureNexus team and scanno + khaon for their hard work
Working:
* Display
* Wifi
* BT
* Audio (including mic)
* Vibrate
* youtube
* Selinux is enforced
* overclocking + other features (see khaon kernel for the full list)
* Storage
Etc
Not Working:
* Camera: so this is the deal, camera isn't working, I see cm is bringing up manta and perhaps there's a chance that they may fix camera but right now the exynos framework of the camera keeps crashing, draining a ton of battery and keeping the CPU awake. Also some apps, mainly youtube don't work because of it. So I have disabled the camera all together and now youtube works. I don't think its as important as camera phones since its a pretty crappy camera anyway but if its fixed ill add it.
* DRM blobs broken
* Small delay in click sounds in UI
* you tell me if anything else is broken
Instructions:
1. Wipe everything
2. Flash rom
3. Flash gapps (make sure you flashed the one linked here or you get a FC in the wizard
4. flash root
5. Reboot and enjoy
Downloads:
ROM: Download Latest
Gapps: SlimGapps 7.1.2
Root: Download
Credits: @scanno , @Khaon , Team PureNexusRom
Rom Source: https://github.com/PureNexusProject
kernel source: https://github.com/sooti/android_kernel_samsung_manta
Device Source: https://github.com/sooti/android_device_samsung_manta
Local Manifest for those who want to build there own
https://github.com/sooti/local_manifest
Instructions to build your own:
1. setup android build machine (instruction on googles android source site)
2. init the purenexus repo using the instructions on their manifest repo
3. Create a file called roomservice.xml and place it into '.repo/local_manifests' in your build directory
4. copy the contents of my roomservice.xml from the link above into your roomservice.xml you just created
5. repo sync and build!
I am pretty busy so I won't have too much time to help all the time, please try to google issues before messaging me, goodluck
XDA:DevDB Information
[ROM][N10][7.1.2_r24]★ Pure Nexus ★ Substratum ★[15/07/17], ROM for the Google Nexus 10
Contributors
sooti, scanno, khaon
Source Code: https://github.com/PureNexusProject
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Based On: AOSP
Version Information
Status: Stable
Stable Release Date: 2017-07-15
Created 2016-10-22
Last Updated 2017-07-14
15/07/17 Changelog:
* Android July security update 7.1.2_r24
* Added doze to our device, it only supports light doze by default do to our sensors not being supported by doze but use greenify to enable deep doze
10/06/17 Changelog:
* Android June security update 7.1.2_r17
* Latest pure nexus commits
07/04/17 Changelog:
* Upgraded to 7.1.2_r6
* Latest pure nexus commits
11/03/17 Changelog:
* Latest March security patch
* Latest pure nexus updates
17/02/17 Changelog:
* Fixed cropping issue thanks to @scanno's commit
* Latest commits from pure nexus
* fixed a small bug in vendor files
09/02/17 Changelog:
* Updated to latest pure nexus updates
* added ROW IO to kernel and set it as default for better performance
18/01/17 Changelog:
* Updated to latest pure nexus updates
* added unified LED
22/10/16 Changelog:
initial commit:
* Updated kernel to 3.4.112 from 3.4.111
* Reverted touch2wake - it causes the device to stay awake and sucks the battery dry
* Disabled camera/fixed youtube
* Finalized selinux + addressed denials and set selinux to enforced
* added double tap to sleep to launcher background (try it out!)
saved
Flashed fine, bootup took a few minutes as usual. Not a fan of the default tablet Navbar though, tried editing it through the Navbar tuner but can't get it looking like it does in marshmallow/lollipop.
Everything feels really smooth. This might just give new life to my Nexus! :good:
EDIT: Nevermind, got it looking like I wanted too. Added a few spacers.
Sparkey159 said:
Flashed fine, bootup took a few minutes as usual. Not a fan of the default tablet Navbar though, tried editing it through the Navbar tuner but can't get it looking like it does in marshmallow/lollipop.
Everything feels really smooth. This might just give new life to my Nexus! :good:
EDIT: Nevermind, got it looking like I wanted too. Added a few spacers.
Click to expand...
Click to collapse
Ya the default navbar is the new navbar, google decided that was better for some reason... not a fan either
My nexus seems to be draining battery incredibly quickly while charging when using this rom. The only apps I have installed are youtube, greenify and adaway. (Brightness is on minimum)
Apart from that, it runs great! Multitasking is incredibly smooth, everything just feels faster.
sooti said:
Ya the default navbar is the new navbar, google decided that was better for some reason... not a fan either
Click to expand...
Click to collapse
If you want the centered default navbar back, just revert https://github.com/sooti/android_de...mmit/c034cb5e5637991be4e047da4de5375a2e31c7b6
I already port purenexus for manta, has been published in G +. But do you continue with this thread?
https://plus.google.com/+HatayamaYuuji/posts/2h4Wuj2Cmbm
scanno said:
If you want the centered default navbar back, just revert https://github.com/sooti/android_de...mmit/c034cb5e5637991be4e047da4de5375a2e31c7b6
Click to expand...
Click to collapse
Thanks for the tip! I think its best I revert this for now... since it really is annoying, maybe i'll bring it back if there is a demand for it on android 7.1
I'll upload a build later since there are a couple more selinux denial I addressed that help stability
voidz777 said:
I already port purenexus for manta, has been published in G +. But do you continue with this thread?
https://plus.google.com/+HatayamaYuuji/posts/2h4Wuj2Cmbm
Click to expand...
Click to collapse
Not sure what you mean.. in any case I had no idea, this version has youtube, selinux and uses khaon's kernel updated by me.
You can feel free to keep updating it and folks who want the basic omni kernel can use yours. just an idea
@voidz777 @sooti
The community is about helping each other. I am happy to see that the start I made with android 7 on manta means that other people are using that base to go further. @sooti made already changes that I might cherry pick into omni (selinux) to enable enforced selinux.
The more people work on the same device, the more chances that everything will work.
So help each other
Verstuurd vanaf mijn SM-T813 met Tapatalk
scanno said:
@voidz777
The community is about helping each other. I am happy to see that the start I made with android 7 on manta means that other people are using that base to go further. @sooti made already changes that I might cherry pick into omni (selinux) to enable enforced selinux.
The more people work on the same device, the more chances that everything will work.
So help each other
Verstuurd vanaf mijn SM-T813 met Tapatalk
Click to expand...
Click to collapse
Thanks for your advice.
Thank you for your great work.
I was deeply impressed to your work you are developing the N10, which was abandoned in the same way as the galaxy nexus.
I am port a custom ROM for galaxy nexus.
Recently I was impressed by your work, it was purchased want to port a custom ROM as well in N10.
I will not continue the PN for the N10 in this thing, but I am grateful for your work.
Sorry,my bad English.
voidz777 said:
Thanks for your advice.
Thank you for your great work.
I was deeply impressed to your work you are developing the N10, which was abandoned in the same way as the galaxy nexus.
I am port a custom ROM for galaxy nexus.
Recently I was impressed by your work, it was purchased want to port a custom ROM as well in N10.
I will not continue the PN for the N10 in this thing, but I am grateful for your work.
Sorry,my bad English.
Click to expand...
Click to collapse
I did not say that you should stop. The more people the better, more choice and more fixes (hopefully)
There appears to be a weird bug where played media zooms into the top left corner and stays there. I'm not really sure how to explain it. It happens in both YouTube and Crunchyroll so I assume the same problem happens with all played video. I'll try and add some photos tomorrow as its quite late where I am.
EDIT:
Here's the best I could explain it:
http://imgur.com/a/awBBp
Google doesn't come up with anything, and the same problem occurs after a reinstall of the rom.
Sparkey159 said:
There appears to be a weird bug where played media zooms into the top left corner and stays there. I'm not really sure how to explain it. It happens in both YouTube and Crunchyroll so I assume the same problem happens with all played video. I'll try and add some photos tomorrow as its quite late where I am.
EDIT:
Here's the best I could explain it:
http://imgur.com/a/awBBp
Google doesn't come up with anything, and the same problem occurs after a reinstall of the rom.
Click to expand...
Click to collapse
Hmmm... no idea but i'm uploading a new build that addresses more selinux denials, your issue could be caused by them... try that build, if it still happens, attache the logcat or i can't help
also i'm working on building 7.1 for you all
EDIT: i see the issue, its when we use 1440p... i think i can fix it
EDIT2: Temp fix for the issue: if you see the issue, press home then back to youtube, it will be corrected. for some reason when we raise the resolution the aspect ratio is not fixed, maybe @scanno has an idea how to fix this? in any case ill keep an eye out for solutions
Just wanted to see thank you for making this... works amazingly well Only issue i have noticed is that it doesn't detect headphones plugged in but i am sure you already knew that.. thanks again
Icetech3 said:
Just wanted to see thank you for making this... works amazingly well Only issue i have noticed is that it doesn't detect headphones plugged in but i am sure you already knew that.. thanks again
Click to expand...
Click to collapse
Nope, i didn't, thanks for the tip, ill check it out!
Hi,
I'm having trouble with the AOSP keyboard. Seems to crash just as I boot up. No keyboard, so no Wi-Fi and hence no alternate.
I'm not sure if this is an isolated issue, but will flash again.
Thanks for your hard with.
Hi! Thank you! ROM works very well!
I have noticed is that batterey percent switch does not work. The percentage of the battery charge is not displayed at the taskbar.
@sooti
Thanks a lot for this smooth rom, great job!
Flashed latest 10/22 with open gapps nano and I don't have any problems with youtube - works very well for me. I don't miss the camera as I don't take pictures with a tablet. Also percentage inside battery icon are shown for me in statusbar. :good:
The only niggle for me is audio focus...when unplugging the headphone the focus won't change back to speakers - a reboot fixes it.
Looking forward to your 7.1 build.
sooti said:
Hmmm... no idea but i'm uploading a new build that addresses more selinux denials, your issue could be caused by them... try that build, if it still happens, attache the logcat or i can't help
Click to expand...
Click to collapse
Is the link in the OP still the latest build? Since you said yesterday you were uploading a new build, i was expecting something with a later date than 10/22 on the linked page.
Thanks,
Joe
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
For your information:
LineageOS 14.1 is a distribution of Android 7.1.2 (Nougat), which is designed to increase performance and reliability over stock Android for your device.
What is different?
The builds provided in this thread are based on the previously mentioned LineageOS, all credit for such work belongs entirely to the LineageOS team.
There are four differences betweet this build and the official one:
1 - Debloated, a lot of the apps bundled by default on LineageOS were disabled on build time. This reduces the .zip file in around 25MB and saves some more on your userdata partition since no dalvik cache is generated for those apps.
I only left the very few core apps required to be able to use all the hardware on your phone. This is the list of stuff I removed:
/system/app/BasicDreams *Screensaver*
/system/app/BookmarkProvider
/system/app/CtsShimPrebuilt *Used for certain software upgrade scenarios*
/system/app/Development *Certain tools for app developers*
/system/app/EasterEgg *The easter egg that corresponds to Nougat*
/system/app/Eleven *Music player*
/system/app/Email *Email client (Gmail will still work)*
/system/app/Exchange2 *Used to connect to certain email accounts*
/system/app/FMRadio
/system/app/Gallery2 *Picture gallery*
/system/app/HTMLViewer
/system/app/Jelly *Web Browser*
/system/app/LiveWallpapersPicker *Used to apply Live Wallpapers*
/system/app/PhotoTable *Screensaver*
/system/app/PicoTts *AOSP text-to-speech service*
/system/app/Stk *Sim Toolkit*
/system/app/Terminal *Terminal emulator*
/system/app/TimeService *Proprietary app found in stock rom, makes no difference in my experience*
/system/app/WallpaperBackup
/system/priv-app/AudioFX *Modifies the behavious of the sound*
/system/priv-app(CMActions *Includes some gestures*
/system/priv-app/CMAudioService
/system/priv-app/CMUpdater *Notifies you of the official LineageOS updates*
/system/priv-app/CtsShimPrivPrebuilt *Used for certain software upgrade scenarios*
/system/priv-app/LiveLockScreenService
/system/priv-app/Recorder *To record audio and video*
/system/priv-app/WeatherManagerService
/system/priv-app/WeatherProvider
/system/priv-app/qcrilmsgtunnel *Proprietary qcom dialer app found in stock rom, makes no difference in my experience*
2 - Changed DPI from 480 to 400. By default build.prop sets UI density to 480 (maybe to give it a more phone-like feeling rather than a tablet, but the our screen has a real density of 400 and working at that settings feels amazing.
3 - Undervolted kernel, this patch is applied on many of the kernels avalaible for Moto X Play, reduces heat generated from the phone.
4 - Enabled doze mode even if Google Play Services are not avalaible and regardless of motion sensor reports. LineageOS team intentionally disabled doze mode if there's no possible tickle to wake up the phone in case of notifications. This indeed only affected users not running Google's proprietary framework.
If you expect this ROM to increase the performance because is debloated I feel like you are going to get mostly placebo. The patches applied on this build were stuff I made for myself in order to keep my phone clean of bloat I don't need, and stuff I have preferred third party alternatives to. In general it's meant to get more freedom/control on what is installed in my phone. The result of this was nice so I wanted to share it with anyone willing to try it.
Hopefully I'll be updating the builds once a month after every major security update happens.
Downloads
DOWNLOAD most recent build from:
https://github.com/Eskuero/patches_lineageos/releases
Outdated builds are still avalaible from:
https://www.androidfilehost.com/?w=files&flid=205174
You can get the root enabler package with the su binary from here:
https://download.lineageos.org/extras
If you are instead looking for the official builds you can find them in this thread:
https://forum.xda-developers.com/mo...ent/rom-cyanogenmod-14-1-moto-x-play-t3515135
Source Code
As said the builds are totally based of LineageOS base code, which can be found here:
https://github.com/LineageOS
With the following patches applied over it:
https://github.com/Eskuero/patches_lineageos
Substratum support?
Enviado desde mi XT1563 mediante Tapatalk
flopezm said:
Substratum support?
Enviado desde mi XT1563 mediante Tapatalk
Click to expand...
Click to collapse
I don't know if official LineageOS supports or not it but it will be the same on this builds since I didn't changed anything that could fix/break it.
Hi #Eskuero
Thanks for building this ROM. This is exactly what I was looking for and I am really impressed with the low heating and extended battery life(when lying idle).
I have been using your ROM for past two days and I loved the font resolution and other tweaks (like removal of default apps) that you have done with this ROM. Please don't abandon this project, I really really love this ROM.
Once in a while their is a hang with an app.... for me it was Amazon prime video.... rest everything worked perfectly fine.
Question?
Exactly which kernel you used it for this ROM.
Best Regards
Vinay (Happy User)
vinayybx said:
Hi #Eskuero
Thanks for building this ROM. This is exactly what I was looking for and I am really impressed with the low heating and extended battery life(when lying idle).
I have been using your ROM for past two days and I loved the font resolution and other tweaks (like removal of default apps) that you have done with this ROM. Please don't abandon this project, I really really love this ROM.
Once in a while their is a hang with an app.... for me it was Amazon prime video.... rest everything worked perfectly fine.
Question?
Exactly which kernel you used it for this ROM.
Best Regards
Vinay (Happy User)
Click to expand...
Click to collapse
Hi!
In fact I just build the ROM again to include all upstream changes and a few dirty but cool hacks by myself so expect it to be uploaded in a few hours. I plan to update the ROM at least once a month when the security patches are published so don't worry.
I used the same default kernel that comes with LineageOS, all I did was to apply the undervolting patch that other kernels such as squid's or Optimus already feature.
Thanks a lot for your words, they mean a lot to me.
I pushed a new build, this one, the older, and probably the next ones will appear on Android File Host and it looks better than Mediafire.
New changes in 20170808 in comparisson with the old 20170709 build:
- Applied all upstream changes from LineageOS
- Updated to August security patch
- Removed CMActions which is not needed for basic functionality (s just responsible for certain system-wide gestures).
- Force the phone to go into deep doze mode regardless of our lack of motion sensor *Read more about the implications at the end of the post*
You can get the new build from https://www.androidfilehost.com/?w=files&flid=205174
Notice that both are uploaded today, but one is the old build from last month and the other one is the new. Check the name for the date to make sure you get the correct one.
About Doze mode:
I hardcoded in an ugly but effective way the doze checks in framework to always ignore sensor reports and let the phone go into deep doze.
Until now we only had working light doze, also known as doze on the go, by default this mode kicks in after five minutes with the screen off and applies network and jobs restrictions even when you're carrying your phone in your pocket.
On the other side deep doze applies restrictions on alarms and wakelocks as well, thus saving a lot more of juice, but only gets applied if the phone has been stationary for 30 minutes. The only way the phone could know about this is by using a motion sensor that our X Plays sadly lacks of. So I simply made the system ignore the lack of this and continue behaving as it was there.
This is the same that some apps like Naptime and ForceDoze do but integrated in the system in a bulletproof way.
I recommend tweaking the Doze Settings with this Doze Settings Editor if you want your phone to go sooner or later into doze mode. GeraldRudi profile make the phone to go directly into deep doze (without going first through light doze) after 30 seconds of screen off.
Hi Eskuero,
Thanks for the new build. Everything is working perfectly fine with this build except the moto display. Phone doesn't wakes up on movement or by wave.
Regards
vinayybx
vinayybx said:
Hi Eskuero,
Thanks for the new build. Everything is working perfectly fine with this build except the moto display. Phone doesn't wakes up on movement or by wave.
Regards
vinayybx
Click to expand...
Click to collapse
Was it working on the previous release?
Eskuero said:
Was it working on the previous release?
Click to expand...
Click to collapse
Yes.
Eskuero said:
Was it working on the previous release?
Click to expand...
Click to collapse
I think it's a part of CMActions.
Copy this .apk to the /system/priv-app folder and reboot your phone. The settings for ambient display should appear on settings after a few seconds
https://www.androidfilehost.com/?fid=889764386195922155
Looking good so far. Thanks!
Any plans for updates following Lineage's development?
Eskuero said:
Copy this .apk to the /system/priv-app folder and reboot your phone. The settings for ambient display should appear on settings after a few seconds
https://www.androidfilehost.com/?fid=889764386195922155
Click to expand...
Click to collapse
Downloaded this apk and tried copying it to the designated folder, but it said the file is only readable and nothing happens.
I am really new to all this, please let me know if I am doing anything wrong.
danikane said:
Looking good so far. Thanks!
Any plans for updates following Lineage's development?
Click to expand...
Click to collapse
Yeah I'll try to update at least everytime the security patches are released. This is between the first and 10th day of every month.
vinayybx said:
Downloaded this apk and tried copying it to the designated folder, but it said the file is only readable and nothing happens.
I am really new to all this, please let me know if I am doing anything wrong.
Click to expand...
Click to collapse
System partition is always protected from editing unless you have rooted the ROM and you use a file explorer that supports root.
The other option is to copy the .apk inside recovery
Eskuero said:
Yeah I'll try to update at least everytime the security patches are released. This is between the first and 10th day of every month.
Click to expand...
Click to collapse
Great, many thanks!
Dual SIM Support
Is the dual SIM version of XT1562 supported?
Update
by update clean flash?
rakle said:
by update clean flash?
Click to expand...
Click to collapse
Flashing over the old version should be safe but I myself never got to do that because I test several different stuff so I like to refresh the ROM once a month to make sure nothing stays broken.
erik1970 said:
Is the dual SIM version of XT1562 supported?
Click to expand...
Click to collapse
If the official builds of LineageOS works for you on double sim versions this ones should work as well. But I can't confirme it myself because I don't own a device to test that.
MIUISTONE PRESENTS
THE XIAOMI RWM
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
XIAOMI RWM DESCRIPTION
BEFORE STARTING OFF, NOTE THIS:
THE XIAOMI RWM IS NOT A MOD, MODULE OR A ROM. IT'S A RWM, A READ-WRITE-MEMORY PACKAGE CONTAINING OPTIMIZATIONS,
AND CUSTOMIZATIONS FOR YOUR FAVORITE ANDROID OPERATING SYSTEMS. PLEASE READ ALL INFOS CAREFULLY TO AVOID PROBLEMS WITH YOUR DEVICES!
THIS PROJECT IS AIMING AT ENABLING THE HIGHEST POSSIBLE QUALITY ON ALL EDGES OF ANDROID. BASED ON YEARS OF RESEARCH, TESTING, AND BALANCING.
RWM IS A KIND OF PATCH/UPDATE WHICH CAN BE INSTALLED ON TOP OF ANY ROM RUNNING ON XIAOMI DEVICES. MIUI OR AOSP, YOUR CHOICE! SELECT YOUR FAVORITE ROM,
FLASH IT TOGETHER WITH THE XIAOMI RWM AND GIVE YOUR DEVICE A COMPLETE OVERHAUL UNDER THE UI. WE WON'T GIVE YOU FANCY UI FEATURES OR TOGGLES.
WE OPTIMIZE YOUR FAVORITE ROM WITH YOUR BELOVED UI AND WE WILL TAKE CARE OF THE QUALITY BEHIND THE SCENES. EVERYTHING NON-ESSENTIAL IS OPTIONAL.
YOU DON'T NEED TO CARE ABOUT ANYTHING AFTER THE FIRST INSTALL, JUST ENJOY! YOU WILL EXPLORE EXTRA FUNCTIONS IN THE SETTINGS OF YOUR ROMS AND APPS,
A BETTER OVERALL AUDIO IN-/OUTPUT QUALITY ON ALL SOURCES, BETTER CONNECTIVITY OVER ALL CONNECTIONS, UNLOCKED DEVICE AND ANDROID FEATURES,
AN ABSOLUTELY FLUID AND PERFORMANT OS AND SO MUCH MORE. THE LIST IS GROWING NONSTOP, AND THERE IS ALWAYS ON THING IN MIND: QUALITY
XIAOMI RWM FEATURES
NOTE: FEATURES MAY DEPEND ON THE ROM!
* ADVANCED GRID RECENTS WITH MULTI/SPLIT WINDOW SUPPORT
* BATTERY CALIBRATION AFTER EACH CHARGE
* ENABLES 4K HDR VIDEO PLAYBACK
* ENABLES ALL EXISTING PIXEL DEVICE FEATURES (AOSP)
* ENABLES ANDROID FOR WORK/ENTERPRISE FEATURES
* ENABLES ANDROID HEARING AID SUPPORT
* ENABLES ANDROID NIGHT LIGHT SUPPORT
* ENABLES ANDROID VIRTUAL REALITY FEATURES
* ENABLES DISPLAY ROTATION FOR THE WHOLE OS
* ENABLES HD VOLTE/VOWIFI + VIDEO CALLING
* ENABLES MANY HIDDEN ANDROID SERVICES & FUNCTIONALITIES
* ENABLES SETUP WIZARD EXTRA FUNCTIONS
* ENABLES VARIOUS EXCLUSIVE FEATURES ON MIUI
* ENHANCED AUDIO OUTPUT CONFIGS, LIBS, AND MAXIMUM QUALITY
* ENHANCED AUDIO RECORDING NOISE SUPPRESSION AND RESPONSIVENESS
* ENHANCED DISPLAY SERVICE CONFIGS FOR SUPPORTED DEVICES
* ENHANCED GPU RENDERING CONFIGS FOR UI AND APPS
* ENHANCED OVERALL PERFORMANCE AND APP RESPONSIVENESS
* ENHANCED SECURITY SETTINGS STARTING ON THE SETUP WIZARD
* FULL SAFETYNET CHECK PASSING
* IMPROVED APP START-UP TIMES
* IMPROVED BOOT AND SHUTDOWN TIMES
* IMPROVED OVERALL CONNECTION HANDLING (BT, WIFI, CELL, GPS)
* MAGISK STABLE AND BUSYBOX INCLUDED
* OPTIMIZED FOR XIAOMI SNAPDRAGON DEVICES ONLY
* TIMER BASED FILESYSTEM TRIMMING
* TIMER BASED INTELLIGENT ZIPALIGNMENT
* TIMER BASED SQLITE3 DATABASE OPTIMIZATIONS
* AND MUCH MORE THAT YOU WILL FACE AT THE RIGHT TIME!
XIAOMI RWM REQUIREMENTS
##### Android 9.0 (AOSP/MIUI ARM64)
##### Snapdragon 835 // 845 // 855
##### At least 4GB of RAM
XIAOMI RWM INSTALLATION
* Step 0: Install a Recovery Environment like TWRP and boot into it
* Step 1: Wipe Dalvik Cache, Cache, System, Data (Be Careful)
* Step 2: Install Your Favorite ROM (Go directly to Step 3)
* Step 3: Install the XIAOMI RWM (Go directly to Step 4)
* Step 4: Reboot to the System
* Done!
XDA:DevDB Information
XRWM, ROM for the Xiaomi Mi Mix 2
Contributors
Miustone, Miustone, Miustone, Miustone
ROM OS Version: 9.x Pie
ROM Firmware Required: ANDROID 9.0
Based On: https://github.com/Miustone/XRWM
Version Information
Status: Beta
Current Beta Version: 19.5.15
Beta Release Date: 2019-05-20
Created 2019-04-15
Last Updated 2019-05-28
XRWM Versions
Stable Releases (Released once per Month) can be found on My Website https://sites.google.com/view/miustone/HOME.
If You want bleeding Edge Builds alias Nightlies, just watch the Video for Beginners, or for the more advanced Users:
Decompress the Master Branch ZIP, Compress the Files inside the "gapps" folder to a ZIP and keep the Configs Folder where it is.
Go back to the Directory which contains META-INF and the other Files and compress the META-INF Folder to a ZIP.
The ZIP should include the META-INF Folder as Root Directory. If this is the Case can the ZIP be flashed!
Video for Beginners: https://youtu.be/_abbpzh7-50
Reserved
Patch Beta RC is uploading. People who know how can download from GitHub and repack to make it flashable!
Edit: Uploaded Chiron Patch. Enjoy!
Updated Thread and uploaded a new Version.
i install AEX Pie and try XASP, no boot system after install XASP zip in twrp
aureliomilitao said:
i install AEX Pie and try XASP, no boot system after install XASP zip in twrp
Click to expand...
Click to collapse
Possible that it's unsupported since it's unofficial. Do You waited some time? Format Data could also help after installing ROM and GApps and before installing Magisk and the Module. Havoc works just fine here... Would be nice to hear again from You!
Best Regards,
Miu
When a update comes out, only is a dirty flash? no need to make wipes?
emime12 said:
When a update comes out, only is a dirty flash? no need to make wipes?
Click to expand...
Click to collapse
Correct, another benefit over my last Patches. The next Update requires a deinstall with the actual Zip since I'm still translating from My last Patch and some rests are actually present in the actual Patch like the Module Prop which says FFUHD 8.0 (Last Patch before XASP). But after that can You just update without trouble!
I'm btw. the Maintainer for the Mix 2 besides doing the main Patch. If You face any Issues feel free to call Me on this Thread. I have also a Hangouts Group since some Years which will be soon added to the Patch, Threads, GitHub and the Website. It's easy to reach over the Web (Gmail or Hangouts Websites) or the App which will be also included next (As Support App since most People are using a Google Acc.).
Best Regards,
Miu
@jigs4wkiller (Keeping You informed about the Support Chat) https://hangouts.google.com/group/gxjqV5KGH884yj1BA
Extremely sorry for this Noob Question. But ...
What is this ??? I.e it's use, what does it do ???
Sorry but can you please explain about it ?
MatrixHack01 said:
Extremely sorry for this Noob Question. But ...
What is this ??? I.e it's use, what does it do ???
Sorry but can you please explain about it ?
Click to expand...
Click to collapse
In simple words... It does configure and optimize what the Most OEMs and AOSP ROMs don't do. They only Care about the UI and useless Gimmicks while XASP goes under the Hood. Better Audio Quality (In and Output), 4K Resolution Playback, HDR Playback Support, Battery calibration, Rendering optimizations (ui and Apps), responsiveness in all conditions (Apps Speeds, Multitasking), UI function unlocks (Display Rotation, Serial Number visible in Settings etc.). The list is endless. You need to expierence it before You think i'm talking BS
So we cant use this on stock MIUI 10?
Bluezzy said:
So we cant use this on stock MIUI 10?
Click to expand...
Click to collapse
You can, but it's made for Android 9 and we are running 8.0.0 not even 8.1. So Problems may happen and i can't solve them without breaking the Android 9 Support...
Miustone said:
You can, but it's made for Android 9 and we are running 8.0.0 not even 8.1. So Problems may happen and i can't solve them without breaking the Android 9 Support...
Click to expand...
Click to collapse
So MIUI 10 is based on 8.0.0 ,there shouldnt be any problems?
I flashed this on POSP (9.0) and it booted. I did remove the many APKs from the zip, but it still seemed to work. It might have been placebo but it did seem a tad smoother.
MintyB said:
But it's also broken charging. Fast charging is broken. I left it on charge for 30 minutes and it charged -1%. It seems to be limited to 100-120mAh according to Ampere. Setting Magisk to Core Only mode also doesn't fix this, so I've had to revert to a backup as removing via magisk + core only mode were still limited to the low charge level. If this is a systemless mod, why has it affected my system after disabling it ?
Click to expand...
Click to collapse
So ignore the above, it was just a coincidence at after flashing the mod, my charger/cable decided that it was going to report as 100mAh max. Nothing to do with the mod, so I'll do some further testing
MintyB said:
I flashed this on POSP (9.0) and it booted. I did remove the many APKs from the zip, but it still seemed to work. It might have been placebo but it did seem a tad smoother.
So ignore the above, it was just a coincidence at after flashing the mod, my charger/cable decided that it was going to report as 100mAh max. Nothing to do with the mod, so I'll do some further testing
Click to expand...
Click to collapse
I can really recommend You UGreen Cables and Chargers. I bought some for My GF with QuickCharge and USB 3 and they are really durable, have great quality and they are cheap. I ordered directly from the Seller and got My Stuff pretty fast from China. I think they are even beyond the most Premium flagship Chargers and Cables...
But OT, thanks for Your Feedback. Can't wait for more! And You are maybe willed to check out GitHub to get Nighlies!? I changed a lot of stuff since i have My Mix 2 (Almost a Week or so) and till the next Monthly Release will be added a lot that's maybe worth a flash...
Bluetooth Audio and GMail Sync is still broken but i cleaned out some stuff and added a lot already. The Issues will be fixed till the Weekend (Hopefully).
Miustone said:
In simple words... It does configure and optimize what the Most OEMs and AOSP ROMs don't do. They only Care about the UI and useless Gimmicks while XASP goes under the Hood. Better Audio Quality (In and Output), 4K Resolution Playback, HDR Playback Support, Battery calibration, Rendering optimizations (ui and Apps), responsiveness in all conditions (Apps Speeds, Multitasking), UI function unlocks (Display Rotation, Serial Number visible in Settings etc.). The list is endless. You need to expierence it before You think i'm talking BS
Click to expand...
Click to collapse
Ah !!! Please don't take it wrong !! i'm really new to this stuff as i'm one of those who developed (i.e i did it two years ago) custom roms for devices.
Btw , what you said sounds really interesting !! I would love to assist you in this project. But, as i mentioned, i left it all two years ago, and need some guidance to restart the whole process. What do you think about it ?? ( it won't take much time to get back on track ).
Miustone said:
I can really recommend You UGreen Cables and Chargers. I bought some for My GF with QuickCharge and USB 3 and they are really durable, have great quality and they are cheap. I ordered directly from the Seller and got My Stuff pretty fast from China. I think they are even beyond the most Premium flagship Chargers and Cables...
But OT, thanks for Your Feedback. Can't wait for more! And You are maybe willed to check out GitHub to get Nighlies!? I changed a lot of stuff since i have My Mix 2 (Almost a Week or so) and till the next Monthly Release will be added a lot that's maybe worth a flash...
Bluetooth Audio and GMail Sync is still broken but i cleaned out some stuff and added a lot already. The Issues will be fixed till the Weekend (Hopefully).
Click to expand...
Click to collapse
I'll have a look at those chargers, I think I must have just knocked the cable/charger, it's a bit weird.
I flashed the github release yesterday since that was the most visible (I honestly couldn't find any other release, I've only just now been able to find it) and I haven't noticed any issues with GMail sync or the like. Battery usage seems a little lower than pre-flash, but that's not totally unusual.
Looking forward to see what other changes you make, keep up the good work :good:
MatrixHack01 said:
Ah !!! Please don't take it wrong !! i'm really new to this stuff as i'm one of those who developed (i.e i did it two years ago) custom roms for devices.
Btw , what you said sounds really interesting !! I would love to assist you in this project. But, as i mentioned, i left it all two years ago, and need some guidance to restart the whole process. What do you think about it ?? ( it won't take much time to get back on track ).
Click to expand...
Click to collapse
It's all fine, i know that Questions already
I'm looking for since Years for someone who helps Me with AOSP (Making a own ROM based on AOSP (Actually a CAF GSI with own Vendors)) since People aren't taking My Work serious at all. I want to make a lot of Things different like with My Patches. If You're willed to help Me to realize My Visions feel free to PM Me!
MintyB said:
I'll have a look at those chargers, I think I must have just knocked the cable/charger, it's a bit weird.
I flashed the github release yesterday since that was the most visible (I honestly couldn't find any other release, I've only just now been able to find it) and I haven't noticed any issues with GMail sync or the like. Battery usage seems a little lower than pre-flash, but that's not totally unusual.
Looking forward to see what other changes you make, keep up the good work :good:
Click to expand...
Click to collapse
Dangerous stuff!
Glad it works well for You. I'm actually uploading a experimental Set which breaks a lot of stuff but also adds a ton of things. Feel free to test it, it's always good to get feedback from other Devices/Systems. :highfive:
Doesn't work with RR. Somebody mentioned that it didn't work on AEX either. So maybe it's something specific to AndyYan' s build since he's the only one building these specific ROMs for Chiron. Or maybe what trees his builds are based on. But I have absolutely no clue about it. Maybe worth a look for ya...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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
Besides selinux being permissive, you tell me
Note: Custom kernels are NOT supported!
If/When the device becomes officially supported, builds will be here https://paranoidandroid.co/downloads otherwise, check the second post for builds
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.
Instructions & requirements
This device runs under lg vendor, make sure you are coming from latest stock firmware.
Download the latest build
Reboot to recovery
Flash the latest build (Note: No need to flash GApps package separately, we include GApps in our ROM package), also make sure to enable TWRP injection
Reboot (In some cases, you may need to set the correct slot before booting ex. if you flashed while on slot a, switch to slot b then reboot, this isn't an issue on most devices, but after wiping data, the system will attempt to boot to the previous slot which most likely will be empty, resulting in a boot screen loop)
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.
Also be sure to join the Paranoid Android Community on telegram (link above), as this is where you'll get the best support from other community users and devs
Cheers and #StayParanoid!
XDA:DevDB Information
Paranoid Android Quartz, ROM for the LG V40
Contributors
sirhc
Source Code: https://github.com/AOSPA
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Unlocked Bootloader
Based On: CAF
Version Information
Status: Testing
Created 2020-05-14
Last Updated 2020-05-14
Hey guys, I'm the framework architect over at the PA team, working on a few Oneplus device, but a buddy of mine gave me this one brand new, so i decided to add some PA love for it. Haven't worked on LG devices in years so bare with me please lol. I've started conversion of the trees provided below to be used on CAFs infrastructure (hals, blobs, etc.) But the trees are based on @SGCMarkus work so huge thanks to him for getting development going. The goal is to get this enforcing and fully operational with CAF blobs etc. to improve performance and reliability. These are all unofficial builds and the team is still determining official support, this is based off of enforcing selinux and performance results
Device tree: https://github.com/Sirhc95/android_device_lge_judypn and https://github.com/Sirhc95/android_device_lge_sdm845-common
Vendor: https://github.com/Sirhc95/proprietary_vendor_lge
Kernel: https://github.com/Sirhc95/android_kernel_lge_sdm845
Builds
May 5th - Quartz 3
Be sure to format data if coming from another rom and remember, no need to flash gapps since we bundle them!
Glad to see more people here making ROMs
Yeah, never touched selinux (wanted to fix other issues first), and atm other stuff going on. If you have questions or anything, just hit me up on Telegram (im more responsive there than here) ^^
I built PA for the V50 not too long ago (just to check if a bug was source or device tree related), and i noticed you guys have a ton of common caf blobs there. The RIL Stack very likely wont work on LG devices (LG modified the modem, to the point the CAF stuff very likely cant talk to it... atleast the IMS part, idk about the rest). Just wanting to give you a heads up ^^
Tried that once on the V30, IMS services started, but calling/sms didnt work anymore (it stayed on LTE, but yeah, nothing happened during the call), logs indicated that it cant properly talk to the modem.
Somewhat working on reversing/wrapping the LG Ims implementation though, idk if that will ever work tough...
SGCMarkus said:
Glad to see more people here making ROMs
Yeah, never touched selinux (wanted to fix other issues first), and atm other stuff going on. If you have questions or anything, just hit me up on Telegram (im more responsive there than here) ^^
I built PA for the V50 not too long ago (just to check if a bug was source or device tree related), and i noticed you guys have a ton of common caf blobs there. The RIL Stack very likely wont work on LG devices (LG modified the modem, to the point the CAF stuff very likely cant talk to it... atleast the IMS part, idk about the rest). Just wanting to give you a heads up ^^
Tried that once on the V30, IMS services started, but calling/sms didnt work anymore (it stayed on LTE, but yeah, nothing happened during the call), logs indicated that it cant properly talk to the modem.
Somewhat working on reversing/wrapping the LG Ims implementation though, idk if that will ever work tough...
Click to expand...
Click to collapse
Great to know, I'm more so focused on getting it enforcing (if possible) before I continue, doesn't seem to be working, stays in permissive no matter what I do lol so far basic qti components we provide work, gonna update perf stack from caf to start, guess I can avoid ril for now
Glad to see more ROMs and devs on this. Will be trying this soon.
Would it be possible to make a build without GApps built in, I had planned to use MicroG. Thanks
Any luck with the Modem/Phone issue? I couldnt get it to work on my Sprint version. Thank you.
Hey, amazing rom. Just wanted to start with a positive But no matter what I do I can't get Bluetooth audio to function properly. It connects and I can choose a device, but no matter what, no audio. I've tried deleting all devices, I've actually reinstalled the rom, I've reset the audio device and no matter what, nothing. Also there are some quirks with audio volume overall. Sometimes it won't turn down the volume at all. It's really weird.
New build coming soon, OnePlus sent me a op8pro so I've been busy doing the bringup for that
sirhc said:
New build coming soon, OnePlus sent me a op8pro so I've been busy doing the bringup for that
Click to expand...
Click to collapse
Was going to install it but I'll wait until the next build
sirhc said:
New build coming soon, OnePlus sent me a op8pro so I've been busy doing the bringup for that
Click to expand...
Click to collapse
Just out of curiosity, would there be a possibility of the quad dac functionality being included?
When is the update coming? I'm having the Bluetooth issues as well as my face is causing things to happen on screen during calls even though the screen is off. So the proximity sensor seems to be working but the screen is still detecting touch. Odd..... Looking forward to the update!
Gurnzty said:
When is the update coming? I'm having the Bluetooth issues as well as my face is causing things to happen on screen during calls even though the screen is off. So the proximity sensor seems to be working but the screen is still detecting touch. Odd..... Looking forward to the update!
Click to expand...
Click to collapse
Don't ask for a eta, he's doing this on his spare time. Maintaining multiple devices. For free. In the meantime try to take logs using catlog. Reproduce the issues and save the logs to share.
R800x_user said:
Don't ask for a eta, he's doing this on his spare time. Maintaining multiple devices. For free. In the meantime try to take logs using catlog. Reproduce the issues and save the logs to share.
Click to expand...
Click to collapse
How about fill out an app to be a mod if you want to police the forum and tell people what not to ask. I use this as a daily driver and the issues I've brought up are easily reproducible. Perhaps I would have taken your suggestion better if you didn't feel the need to tell me what not to ask. It's a fair question. If the man doesn't want me to ask an eta, he can tell me himself. I highly doubt he's going to be annoyed that someone is excited to see the next build.
Gurnzty said:
How about fill out an app to be a mod if you want to police the forum and tell people what not to ask. I use this as a daily driver and the issues I've brought up are easily reproducible. Perhaps I would have taken your suggestion better if you didn't feel the need to tell me what not to ask. It's a fair question. If the man doesn't want me to ask an eta, he can tell me himself. I highly doubt he's going to be annoyed that someone is excited to see the next build.
Click to expand...
Click to collapse
Ehhh...still frowned upon to ask for eta....
I have this on my V40, anyone have any luck getting Magisk installed on it? I don't know if there is an anroid 10 magisk released for the v40 yet though.
NoburtM said:
I have this on my V40, anyone have any luck getting Magisk installed on it? I don't know if there is an anroid 10 magisk released for the v40 yet though.
Click to expand...
Click to collapse
All recent magisk versions support android 10
Gurnzty said:
How about fill out an app to be a mod if you want to police the forum and tell people what not to ask. I use this as a daily driver and the issues I've brought up are easily reproducible. Perhaps I would have taken your suggestion better if you didn't feel the need to tell me what not to ask. It's a fair question. If the man doesn't want me to ask an eta, he can tell me himself. I highly doubt he's going to be annoyed that someone is excited to see the next build.
Click to expand...
Click to collapse
Should've mentioned that it's a xda rule. Will take that into consideration thanks. But if you can capture a log. I'm currently not running this ROM to help the cause.
Ainz_Ooal_Gown said:
Ehhh...still frowned upon to ask for eta....
Click to expand...
Click to collapse
Ainz what is your APN settings for this? I can't connect my Sprint phones LTE.
Thank you
Droidman61 said:
Ainz what is your APN settings for this? I can't connect my Sprint phones LTE.
Thank you
Click to expand...
Click to collapse
The same one I always use but idk if my data works on this rom since I still owe Sprint a good amount of money