Related
As good a place as any to post this.
Pio-masaki.com is being shut down due to a Cease and Desist order sent against the host by Google and homeland security. I have no idea why, however until this is sorted out, and to avoid any possible or further legal issues, the site is down for a period of time that can be a day or forever. This includes any and all ROMs, kernels, gapps packages, for any and all devices, that were hosted on pio-masaki.com.
I apologize in advance for this as I know some ROMs are only available at pio-masaki.com, but it is out of my hands, the host has to consider their own safety, and has my 100% agreement and backing in taking down the site until the matter is resolved.
As this is a very large matter, and one that has us incredibly scared, I'm retreating from android for the time being, until I know what it was that I did that was illegal, and may return once this is cleared up and blows over.
After this is cleared up the hosting for pio-masaki.com may still remain offline as the hoster has some personal issues with me at this point and may or may not continue to host for me, should we resolve our differences it may return.
If by some chance Google or whoever sent the C&D notices this, I urge you to contact me as I was responsible for what was hosted, and would genuinely like to know what the issues are so we can get them resolved immediately.
I will be making similar postings or editings to any other ROM threads that link to pio-masaki.com.
What is CarbonROM?
CarbonRom is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look at, build, and use our code on CarbonDev GitHub.
We would like to thank CyanogenMod for their device trees, framework/settings mods and their code that was incorporated into this project. We also extend our gratitude to the devs whose code that we have incorporated. Proper authorship has been maintained and can be viewed on our repository.
Special thanks also go to Slim Rom for some of their features, PA, AOKP, and anyone else we may have borrowed commits from that hasn't been mentioned here. If you feel you have been unfairly left out, please - let us know.
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash! If you have questions, ask your fellow users or ask us in #teamcarbon on freenode IRC.
1.6 is a pretty big update for us! Check out the changelog on our goo.im page for more, but here are the highlights:
-PIE
-HALO
-Floating Application windows (long press app in recent apps list)
-Lock screen rotation is back
-Dark Carbon! Huge props to Slim Roms for coming up with this unique and awesome feature.
-Lockscreen theming
-CM skinny battery is back!
-Volume key lock on silent mode option
-Backup tool - if you're flashing a new version of Carbon and already have the required version of gapps installed, it will be backed up and restored during install. This applies to system apps and custom host files as well. Please note that you should only dirty flash from Carbon to Carbon. It's ok if it's another version or a nightly - just not over other roms. Super handy for you crack flashers. Make sure you've got the most recent Gapps though, and if you're flashing from a factory reset, you'll still need to install it after install of course.
-Long pressing the "clear recents" button clears the cache
-AOKP's awesome new navbar settings
-NFC polling mode for when you want to keep your screen off and scan tags
-MMS and call "breathe" feature. Makes the notification icon fade in and out.
-Mute dings when changing volume
-Disable/enable CRT effect on screen on/off.
-3rd party keyboard bug fixed
-deodexed again
-stability and speed enhancements
-a million other little things as well - we basically don't even sleep anymore.
*not all features are available on the A100 tablet.
Screenshots
{
"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"
}
Carbon Updates
Join us on these Social Media Channels to keep yourself up-to-date on all the latest Carbon news, updates, contests, and more! Join our completely open Google+ community for insider conversation with devs and other users!
Who is Team Carbon?
andros11
BigShotRob
dg4prez
Kejar31
mattmanwrx
morfic
nocoast
pixeldotz
slick_rick
winner00
Instructions:
Please clean flash this, there's so many extra settings that dirty flashing will likely cause problems. If you dirty flash, please don't report any issues until you flash clean and the issue occurs again!
Please use a proper 4.2.2 Gapps package, using inversed or any modded versions can and likely will cause issues, please use the current 4.2.2 from goo.im, if you use inverted or modded Gapps, please don't report issues until you clean flash with a proper package from goo.im!
Download the ROM
Download the current 4.2.2 Gapps from goo.im or pio-masaki.com
Place files someplace useful
Boot into recovery
This part assumes you know how to operate your installed recovery
Wipe system
Factory reset
Wipe dalvik
Flash CarbonROM
Flash Gapps
Reboot
Let settle for a few minutes after booting
Setup device as usual
If you have issues on first boot, flash the ROM only, then after it boots, reboot and flash Gapps then manually setup your device in settings.
Change Log
8.01.13-B1:
initial build for experimenting, didn't boot.
8.01.13-B2:
Next try, boots, SystemUI crash makes it unusable, no nav/status bars
8.02.13:
WiFi works, SystemUI persistent crashing still makes device unsable.
8.02.13-B2:
BT, WiFi, sound all work, persistent SystemUI crashes still occuring.
8.03.13:
All works, SystemUI crash fixed, PIE crashing, battery mods missing, Torch doesn't work.
8.03.13-B2:
All works, Torch works
8.03.13-B3:
Fixed PIE crashing, fixed missing battery mods. Rom is now fully operational.
FAQS
If you didn't read the bugs list below, go down and read that now, asking the same questions over and over is a trademark of xda and I hate it, please read the change log and bug list before posting questions or reporting issues.
Q. I want to use this build(s) as a base for my ROM, or I want to host/re release it in another country/forum, can I?
A. You may, but only if you send me a PM about it first. I've had a bit of trouble with people taking credit for my work, and I'm getting sick of it. I don't mind sharing and whatnot, but taking my build, adding a build.prop tweak and releasing it on another forum with no mention of my name is not acceptable. As for re releasing on another forum, you may if you just shoot me a link to the post about it, I would rather you link directly to this thread if possible. For those posting in forums of other languages (I know some users might in Russia, for example, use my ROMs) feel free to post for your native languages, and please include a link here also.
Q. I want to report an issue, can I just post it in your thread without reading or doing any basic troubleshooting, googling, reading or wiping?
A. Well you CAN, you may be ignored or flamed for it. Please read above, and please read the Bugs and Change Log lists before reporting anything. Please flash a clean download, flash a clean wipe, and don't restore stuff from TiBu, thats basic troubleshooting, check if the issue persists, if it does, then feel free to post about it.
Q. Is this daily driver ready?
A. Can't answer that, what a person needs from their phone varies from person to person, what I may consider fine for my use may be 500 kinds of broken for another user. Example, I don't use my camera often, maybe once a month, and my BT has never been turned on for the last 5 devices, for me broken BT audio and camera doesn't make it a non daily driver ROM. Please read and decide for yourself if features included outweigh the broken, or if broken things are required for your comfortable use of your device.
Q. How can I build my own versions?
A. I'm not going to write a guide, I did write one for CM9 which is 99.99% still a working guide aside from source urls for updated jellybean. Otherwise there are plenty of very well written guides on how to build ROMs, individual questions about build it can be asked here if you wish as this is a development thread.
Q. Can I use -insert kernel name here-?
A. You can probably use any kernel you want, but WiFi and such won't work. If you don't mind no WiFi feel free to use any kernel that will boot.
Q. Your files all download as index.php!
A. This happens on certain browsers, namely the stock browser and Chrome. You can either use another browser (naked and dolphin don't do this) or simply rename the file to something useful, like "piostotallyepicawesomesaucedrizzledromthatrocksyo urass.zip"
Bugs:
MIC doesn't work
Camera crashes when you change resolutions
WiFi may not connect after being turned off, needing a reboot to come back up
Google Search doesn't work (no MIC)
Headset MIC also doesn't work
ROM may get stuck booting, powering off and on will have it boot again, not sure where this is coming from.
More, I'm sure.
Downloads:
Please visit http://pio-masaki.com for all my ROM builds
CARBON-JB-UNOFFICIAL-20130803-2330-a100.zip
WHOA BUNDY! This ROM is amazing! Finally some 4.2.2 action on the A100. Thanks!
This looks very interesting indeed. Without MIC support it can't be my daily as I Skype alot, but a working 4.2.2 on this old tablet is amazing in itself! Great work as always Pio.
MrCubbins said:
This looks very interesting indeed. Without MIC support it can't be my daily as I Skype alot, but a working 4.2.2 on this old tablet is amazing in itself! Great work as always Pio.
Click to expand...
Click to collapse
Actually, try a headset, or plug then unplug headphones, it works on the thrive for audio to get working properly, may work here too, they use the same audio system, drivers and libs.
Well I didn't have time to play much last night but have had a proper look around the ROM today.
4.2.2 on A100 is FAST!! Very impressive. I noticed some issues so thought it might be helpful to catalogue them here.
MIC is definitely not working. Tried the headphone thing but nothing Voice Search force closes on launch and Recorder can't hear anything.
The Halo app (which I gather is one of the big draws in this ROM) force closes when you select it. Oddly, it's like it might be corrupted or something as the icon is showing as just a little droid and the app title is showing as HALO))).
Changing the camera resolution causes the camera to FC (front or rear camera) ... Afterwards a dialog box tells you that it "Can't connect to the camera". This was a problem in the older 4.1.2 ROMs as well but I believe Hardslog discovered a fix somehow so I am sure he will be able to give you the info.
If there is anything else I come across during my exploring I will let you know. I'm enjoying having new things to play with!
MrCubbins said:
Well I didn't have time to play much last night but have had a proper look around the ROM today.
4.2.2 on A100 is FAST!! Very impressive. I noticed some issues so thought it might be helpful to catalogue them here.
MIC is definitely not working. Tried the headphone thing but nothing Voice Search force closes on launch and Recorder can't hear anything.
The Halo app (which I gather is one of the big draws in this ROM) force closes when you select it. Oddly, it's like it might be corrupted or something as the icon is showing as just a little droid and the app title is showing as HALO))).
Changing the camera resolution causes the camera to FC (front or rear camera) ... Afterwards a dialog box tells you that it "Can't connect to the camera". This was a problem in the older 4.1.2 ROMs as well but I believe Hardslog discovered a fix somehow so I am sure he will be able to give you the info.
If there is anything else I come across during my exploring I will let you know. I'm enjoying having new things to play with!
Click to expand...
Click to collapse
There's two parts of Halo))), the part you're talking about, doesn't matter unless you want a specific app always to be in Halo, otherwise HALO itself works just fine. The app itself isn't required or the "big draw" to the ROM, HALO can be managed just fine without it, and originally the app wasn't included, I hadn't noticed it was included now anyways lol
The camera issues are partly due to we're using camera parts from 5 versions of android ago, I'm sure it can be patched up again but it's getting annoying having to fix storage, audio, cameras, and kernels EVERY SINGLE MINOR UPDATE to android. We're not talking 4.1 to 5.0, its 4.1 to 4.2.
AFAIK it wasn't reported my 4.1.2 builds ever had camera issues, though. Keep in mind I was doing that blind, if no one told me I would never have known.
Google search doesn't force close for me, but it also doesn't hear anything, so that doesn't count for much lol
pio_masaki said:
There's two parts of Halo))), the part you're talking about, doesn't matter unless you want a specific app always to be in Halo, otherwise HALO itself works just fine. The app itself isn't required or the "big draw" to the ROM, HALO can be managed just fine without it, and originally the app wasn't included, I hadn't noticed it was included now anyways lol
The camera issues are partly due to we're using camera parts from 5 versions of android ago, I'm sure it can be patched up again but it's getting annoying having to fix storage, audio, cameras, and kernels EVERY SINGLE MINOR UPDATE to android. We're not talking 4.1 to 5.0, its 4.1 to 4.2.
AFAIK it wasn't reported my 4.1.2 builds ever had camera issues, though. Keep in mind I was doing that blind, if no one told me I would never have known.
Google search doesn't force close for me, but it also doesn't hear anything, so that doesn't count for much lol
Click to expand...
Click to collapse
Does that mean I can safely remove the HALO))) apk without affecting the functionality of Halo itself?
I reported the camera res change issues quite awhile ago to hardslog, though I think at that point you had stopped development on the A100. I remember him saying he would look into a fix and I think awhile after he cured it. Can't remember if he listed on here what the actual cause of the problem is though.
This potential to customize how this ROM behaves is absolutely incredible. I spent the last couple of hours messing about with swipe bars and pop up menus and the various combinations possible... it really is clever stuff. Was rather confusing to figure out what is what at first. I've still not found a way to change the button size on the pie... any additional buttons added get squashed up at one end of it. Is there anywhere in the menu where this can be altered? Also, directly surrounding the pie buttons there is a thick bar which is partially blue... looks like a volume slider or something but I can't seem to get it to do anything??
All in all a very interesting ROM thank you Pio. Given that it is early days on 4.2.2 for the A100, do you think there is any chance that the MIC will be fixable in the future? Does it work ok on your Thrive?
MrCubbins said:
Does that mean I can safely remove the HALO))) apk without affecting the functionality of Halo itself?
I reported the camera res change issues quite awhile ago to hardslog, though I think at that point you had stopped development on the A100. I remember him saying he would look into a fix and I think awhile after he cured it. Can't remember if he listed on here what the actual cause of the problem is though.
This potential to customize how this ROM behaves is absolutely incredible. I spent the last couple of hours messing about with swipe bars and pop up menus and the various combinations possible... it really is clever stuff. Was rather confusing to figure out what is what at first. I've still not found a way to change the button size on the pie... any additional buttons added get squashed up at one end of it. Is there anywhere in the menu where this can be altered? Also, directly surrounding the pie buttons there is a thick bar which is partially blue... looks like a volume slider or something but I can't seem to get it to do anything??
All in all a very interesting ROM thank you Pio. Given that it is early days on 4.2.2 for the A100, do you think there is any chance that the MIC will be fixable in the future? Does it work ok on your Thrive?
Click to expand...
Click to collapse
Well as I said unless it was reported (to me) I wouldn't have known. Hardslog wasn't reporting issues or fixes to me so I never knew it happened or how it was fixed.
The mic should be fixable, and yes it works on the thrive, so its likely a minor routing issue on the vangogh vs Antares or Picasso boards. Sound is my weakest point though, I always have troubles with it for some reason.
As for pie, there's options for all kinda shiz in there, just gotta go through them all and restart systemui to make them active in some cases. That bar is, I think, just decoration, though.
Sad thing is I don't really use the camera features on the A100 so that's probably why I never tested them when going thru stuff on the recent CM10 builds. But yes I am getting the same issues MrCubbins has reported with changing resolutions FCing the camera app on this current CarbonROM build.
The only thing I am hoping for down the road is some kind of updated version Linuxsociety's Jelly Bean kernel that works on 4.2.2. I'm pretty sure the current build will not work on 4.2.2 ROMs due to there being enough differences between 4.1.x and 4.2.2. Love how that kernel worked in making things run just a bit smoother. :good:
AngryManMLS said:
Sad thing is I don't really use the camera features on the A100 so that's probably why I never tested them when going thru stuff on the recent CM10 builds. But yes I am getting the same issues MrCubbins has reported with changing resolutions FCing the camera app on this current CarbonROM build.
The only thing I am hoping for down the road is some kind of updated version Linuxsociety's Jelly Bean kernel that works on 4.2.2. I'm pretty sure the current build will not work on 4.2.2 ROMs due to there being enough differences between 4.1.x and 4.2.2. Love how that kernel worked in making things run just a bit smoother. :good:
Click to expand...
Click to collapse
I'm just curious why anyone
A: uses the crappy camera on these things for anything but Skype
B: bothers changing the resolution of the already low resolution cameras
The kernel included is already modified just hasn't had the juice turned on yet. I'm not a fan of his kernel for my personal device, it never got along with it. If you venture into its settings you'll notice it has some extras in governors and io, no longer stock CM.
Yeah I'm not really much of a fan of cams on tablets myself. Yet I've seen people using their tablets for taking pictures so what do I (and you) know, right?
I wasn't aware of what was going on with the kernel that you have in use. The Linuxsociety kernel or at least the one that was in hardslog's ROMs ran very well on mine. That's using Linuxsociety's kernel with mods done wasn't it? Then again we all know that you probably can have two A100's next to each other one will run the kernel perfectly yet the other one will have issues with it... so yeah.
AngryManMLS said:
Yeah I'm not really much of a fan of cams on tablets myself. Yet I've seen people using their tablets for taking pictures so what do I (and you) know, right?
I wasn't aware of what was going on with the kernel that you have in use. The Linuxsociety kernel or at least the one that was in hardslog's ROMs ran very well on mine. That's using Linuxsociety's kernel with mods done wasn't it? Then again we all know that you probably can have two A100's next to each other one will run the kernel perfectly yet the other one will have issues with it... so yeah.
Click to expand...
Click to collapse
I think he used ezterrys kernel, why he chose to over the godmachine kernel you'll need to ask him about lol. It was a nice kernel for sure, but my a100 just didn't like it. My thrive kernels love mine but hate some others, such is electronics I guess.
I'm still testing the kernel for when the juice is turned on so its a pretty basic kernel otherwise, bit it should wake up real nice when its let loose.
Looking over the notes from several of hardslog's ROMs he's mentioned they have used godmachine kernels (or as I mistakenly called them "Linuxsociety"). No idea on the latest ROM that he's released since there's no mention. Let me know if you need to me to test any kernels here. My A100 is ready.
Well the kernel has some odd issues, for one lulzactive seems to just stay at top speed, it doesn't seem to scale at all. In the overclock enabled builds anychanges to min/max speeds will result in no deep sleep, the kernel stays awake at all times. Not sure whats causing either of those, lulzactive can be gone over but why the speed change locks the system awake I have no clue.
I really wish I knew what I was doing with kernels lol
Edit:
Vote, who thinks I should just update the linux society/god machine kernel to 4.2 and leave it at that? lol
I was totally not aware about the deep sleep issue since I normally turn the tablet off when it's not in use. Does the ezterry kernel have the same issue? If not then maybe updating that to 4.2 might be better in the long run. As far as scaling I never seemed to have the issue at least from what SetCPU shows me. I'm about to go to my CYANOSAKI_FLEX_V2.0 backup and will let you know what I'm seeing as that I believe is using a godmachine kernel.
Also just noticed something weird. When I tried to backup the current CarbonROM build using TWRP 2.6.0.0 it shows 0MB in cache is used. Could there be something wrong with the routing/paths/etc on cache use on CarbonROM?
AngryManMLS said:
I was totally not aware about the deep sleep issue since I normally turn the tablet off when it's not in use. Does the ezterry kernel have the same issue? If not then maybe updating that to 4.2 might be better in the long run. As far as scaling I never seemed to have the issue at least from what SetCPU shows me. I'm about to go to my CYANOSAKI_FLEX_V2.0 backup and will let you know what I'm seeing as that I believe is using a godmachine kernel.
Also just noticed something weird. When I tried to backup the current CarbonROM build using TWRP 2.6.0.0 it shows 0MB in cache is used. Could there be something wrong with the routing/paths/etc on cache use on CarbonROM?
Click to expand...
Click to collapse
The deep sleep issues are only on the overclock enabled kernel that I use, it shouldn't appear in the released build, it only shows up if min/max speeds are changed from stock. Scaling issues appear only in lulzactive, its defaulted to interactive so unless you change it, its scaling properly.
I'm not using the ezterry or god machine kernels, so its a problem unique to mine I think.
It uses cache or it wouldn't be booting at all, and you shouldn't back that up anyways I think twrp has some bugs no one ironed out and its causing oddness with older devices.
Oops. I thought you meant godmachine's kernel had those issues. My bad. I should read better next time. :laugh:
Also checking CYANOSAKI_FLEX_V2.0 the kernel it's using believe it or not is by ezterry. SetCPU defaults to interactive on this for me as well running at 1.5 ghz max speed, 312 mhz minimum. No idea if hardslog has done any mods/changes to the kernel however. Run perfectly fine on my A100. :good:
And you are right about cache let alone the TWRP bug. Just finished wiping and restoring my CarbonROM backup by the way. Successful swapping from 4.2.2 to 4.1.2 and back via TWRP backups.
Ugh I hate kernels, and I hate working IN them even more. But, it's coming along. It'll basically be the GM kernel all over again when I'm done lol.
So far vs the source I began with:
GPU/CPU/system speeds are tuned a little more, voltages tuned a little more
Adding in those missing governors, like Smartass and lagfree.
Converted/updated to BCMDHD from BCM4329
OC up to 1.5, UC to 216
I'm building this to include with my 4.2 builds, and I suppose I could just release a flashable version, it may even work on 4.1, who knows.
{
"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"
}
Welcome to Eos! The Eos project originated with the AOSP release of ICS, and was originally founded by Solarnz and co founded by Bigrushdog. Since then, Eos has evolved into a multinational collaborative effort backed by top Android developers. Our objective is to provide a world class AOSP build with unique features and enhancements. Eos is an ongoing development project in which builds are released on a regular basis. Every release should be considered stable and highly functional.
Bigrushdog - Project lead, Chief Developer [Xoom || Galaxy Nexus || HTC One (M7)] || Nexus 7
RaymanFX - Co-leader, AOSP code maintainer [Xperia S || Nexus 7 (2013) || OPPO N1 || OPPO Find7a]
jrior001 - Jenkins/Gerrit Admin, CAF code maintainer [HTC One X]
anders3408 - Frameworks Developer [OPPO Find5 || OPPO N1]
Roach - Frameworks Developer [Nexus 4 || Nexus 7 (2013) || HTC One (M8)]
Connor Baker [Nexus 4 || HP Touchpad]
Code:
NX 2.0 Gesture Navigation Interface
EOS Weather Engine
Custom Quick Toggles Tiles with Brightness & Volume Seekbars
Softkeys Long-Press Actions
Network Indicator
Battery Indicator Mods
Clock Mods
T-Mobile Theme Engine
Force Navigation Bar on any device
Volume keys switch depending on rotation. So the volume up key is always either on the top or to the right of volume down. (Toggle-able)
Default Volume Control Stream (Ring or Media)
Advanced power menu with reboot options.
MORE...
We give love and much respect to Cyanogenmod. The AOSP scene would not exist as it does today without them. We implement some of their branches to support legacy devices and features that users have demanded.
Team EOS Nightly builds
Wingray, Stingray, and Everest Downloads
G-Apps Package
PA Gapps
These builds are designed to be installed from your favorite recovery. MAKE SURE YOU HAVE THE LATEST 4.4.x COMPATIBLE RECOVERY.
Detailed instructions:
Going to EOS4.4.x from a rom < 4.4.x:
Backup everything !
Go to recovery
Make a full wipe / factory reset
format /system
Flash the rom
Flash optional kernel
Flash gapps
Reboot
Updating from EOS 4.4.x #XX to #YY:
You can usually skip the full wipe step.
If ever you encounter an issue make sure you make a full wipe first before reporting though.
These are only for Bigpart enabled devices. IF YOU DON'T HAVE BIGPART SUPPORT DO NOT FLASH!
Many things are broke, including camera and radios on telephony enabled devices. I'm opening a thread here for the purposes of furthering development and discussion. These builds are only for folks that enjoy punishment and can give guidance on what i need to do to get the broke things fixed. The Eos project is now geared towards supporting modern qcom devices. However, we're fairly close to getting some proper Xoom builds.
I personally want to give a HUGE THANKS to @Schischu for carrying on the Xoom battle! I'm really glad Xoom users have been able to enjoy strong, stable 4.4 builds. Also, I want to give another HUGE THANKS to @Schischu for thinking up the Bigpart kernel patch. That is not my work and I just wanna make sure that's clear.
I am using @Schischu 's device trees and @flar2 's kernel for now. Once we can get reasonable stable, I'll bring in Backtrack support and all that fun stuff. Once again, I give huge props and respect to @Schischu for the amazing work he has done.
Also, I give a huge thanks to @shpitz for giving me what has turned out to be a VERY LONG TERM LOAN on his Stringray! If someone want's to take lead on maintaining and developing Xoom for me, please speak up! @shpitz i'm sure wants his Stingray back sooner rather than later.
Contribute
Gerrit Review
Jenkins Build System
Github
Kernel Source
Reserved for something
Come on in guys! I must really be a glutton for punishment these days!
Ok, let's start with the good news. Wifi, bluetooth, and it looks like the sensors all come up. And overall, the build feels stable. I haven't got random reboots or anything like that.
The bad news: camera and radios are broke. And those are usually the hardest to fix. Eos uses CM tele framework, including the new msim support from CAF. I've trolled every team's repo out there and can't see to get camera right. I do believe i'm close though. I've got about 5 or 6 open commits on Eos review pertaining to tegra2 related display stuff, yet they don't seem to work for me here.
Updated 6/22
What's broke, maybe broke, unknown
-- Problems with EGL config causing launcher wallpaper picker fail, as well as numerous user apps including Amazon Store and likely more.
-- Everest just released, waiting on radio reports.
-- Next day or two, stingray_cdma will release, we'll watch this radio as well.
-- That's all i remember, if i missed some derp, let me know and i'll add to list.
Upcoming and to-do list
-- Charge light on/off toggle (I know you guys missed that one ;D)
-- Boatloads of kernel modules!
-- Backtrack support for those who still want to use their Xoom to pwn Facebook passwords at the local Starbucks :angel:
-- Perhaps overclock by default so we get a stronger device experience out the box
Can a different camera be downloaded from play store and work? Or no the base has to be layed...?
kmcrane said:
Can a different camera be downloaded from play store and work? Or no the base has to be layed...?
Click to expand...
Click to collapse
A third party cam MAY work, but I'm not sure. The stingray I'm using has a deactivated Verizon sim card and I think it was being weird with gapps. I couldn't connect to Play Store. The peculiar thing is, I get a Camera fc. If something was borked with HAL i would get a "Could not connect to camera" error. Definitely worth a shot.
I have used banks gapps (minimal) Or PA gapps, and I used micro modular I think. A long as I get play store and I can download what I want I'm happy. I hate deleting tons of stock apps.
Anything for 2012 Nexus 7? I have one of those too, and dual eos would be perfect.
kmcrane said:
I have used banks gapps (minimal) Or PA gapps, and I used micro modular I think. A long as I get play store and I can download what I want I'm happy. I hate deleting tons of stock apps.
Anything for 2012 Nexus 7? I have one of those too, and dual eos would be perfect.
Click to expand...
Click to collapse
Ya, and as it turns out, looks like i'm maintaining that one too. Now, grouper is rock solid. I haven't opened the thread yet, but dig around the teameos downloads and you'll find it.
bigrushdog said:
Ya, and as it turns out, looks like i'm maintaining that one too. Now, grouper is rock solid. I haven't opened the thread yet, but dig around the teameos downloads and you'll find it.
Click to expand...
Click to collapse
Lol i have been digging around Google and anything i could find with EOS, bigrushdog, r. Ru**ing, I've been eos stalking for a few weeks trying to find a little break.
Thanks!
Sent from my VS980 4G using XDA Free mobile app
Awesome work!! Been using a self compiled build for 2 weeks or so and loving it! Great to see this coming out officially even though some things are broken.
Pls don't tell me will have to do full wipe coming from omni rom to EOS 4.4.2
Sent from my Xoom Wifi using Tapatalk
ahmed007 said:
Pls don't tell me will have to do full wipe coming from omni rom to EOS 4.4.2
Sent from my Xoom Wifi using Tapatalk
Click to expand...
Click to collapse
These builds are only for folks that enjoy punishment and can give guidance on what i need to do to get the broke things fixed.
Click to expand...
Click to collapse
Based on your post, you're not a candidate folk!
Will certainly be trying this out! I'm still glad I stuck with my xoom!
kmcrane said:
Lol i have been digging around Google and anything i could find with EOS, bigrushdog, r. Ru**ing, I've been eos stalking for a few weeks trying to find a little break.
Thanks!
Sent from my VS980 4G using XDA Free mobile app
Click to expand...
Click to collapse
I'm pretty sure there's a VS980 floating around somewhere too ;D
matt4321 said:
Awesome work!! Been using a self compiled build for 2 weeks or so and loving it! Great to see this coming out officially even though some things are broken.
Click to expand...
Click to collapse
Glad to hear you got it compiling. I wanted to wait to get a thread open before addressing all that. So, you wanna maintain the Eos builds? :highfive::highfive::highfive:
Well, for those of you who have flashed, perhaps we should start getting an inventory of what we gotta do still? I mentioned before that as it stands now, cam is broke. Thus Torch is broke. Radio is hard to assess because i don't have a activated SIM. Also, how is the Wingray build? Has anyone successfully loaded gapps yet? If so, please post up or link to the gapps.
bigrushdog said:
Glad to hear you got it compiling. I wanted to wait to get a thread open before addressing all that. So, you wanna maintain the Eos builds? :highfive::highfive::highfive:
Click to expand...
Click to collapse
I'm not a developer I'm afraid as much as I'd like to be.
I can always compile, bit of debugging, test experimental fixes. not sure I'd be able to maintain though. I have basic expeience in C#, not CPP though some practices are transferable.
I used BaNkS GApps back with the original EOS because of the limited System partition.
With Big Part CM11, I'm using PA GApps. Their Google Camera add-on is working with Photosphere and such.
Will give EOS Revival a shot when I have a little work downtime
Alrighty, just to report: I am currently using a wingray device. I have just flashed the rom (no problems there), and I have just flashed the gapps from here.
So far everything's fine. I can confirm that the camera is currently not functional. However, time does wonderful things!
I do have a question though: I have noticed that the settings app doesn't sport the tablet-optimized two pane layout from previous versions of android. Is that a feature of the rom or is that a kitkat thing?
Anyways, great work! Thank you so much too all who have contributed to it (and one day I hope I can learn how to contribute myself!)
yosterwp said:
Alrighty, just to report: I am currently using a wingray device. I have just flashed the rom (no problems there), and I have just flashed the gapps from here.
So far everything's fine. I can confirm that the camera is currently not functional. However, time does wonderful things!
I do have a question though: I have noticed that the settings app doesn't sport the tablet-optimized two pane layout from previous versions of android. Is that a feature of the rom or is that a kitkat thing?
Anyways, great work! Thank you so much too all who have contributed to it (and one day I hope I can learn how to contribute myself!)
Click to expand...
Click to collapse
Good deal. Wingray will be the first device fully on deck. I'll link to that gapps in the OP. I also noticed we didn't get dual pane on settings. I'll see what I can do. However, I do suspect the dual pane concept as a whole is going extinct. I could be wrong but it's just a feeling I get. Camera is close. Actually, there's a small possibility it's actually audio killing cam. Not sure just yet.
Thanks for being part of the brave elite!
bigrushdog said:
Good deal. Wingray will be the first device fully on deck. I'll link to that gapps in the OP. I also noticed we didn't get dual pane on settings. I'll see what I can do. However, I do suspect the dual pane concept as a whole is going extinct. I could be wrong but it's just a feeling I get. Camera is close. Actually, there's a small possibility it's actually audio killing cam. Not sure just yet.
Thanks for being part of the brave elite!
Click to expand...
Click to collapse
The Xoom CM11 build has dual pane settings. You could see how it was done there?
Sent from my Xoom Wifi using Tapatalk
I've been stalking the Team EOS Gerrit and constantly refreshing the Xoom Development on here. I did run an unstable version a while ago from the Team EOS download page, and even though it was buggy, I liked it.
I think I'll wait until the camera works to flash back to EOS, though.
I like this ROM, especially the NX 2.0. Is there anyway to make an Xposed Module to add the NX 2.0 to other ROMS?
ApertureAndroid said:
I've been stalking the Team EOS Gerrit and constantly refreshing the Xoom Development on here. I did run an unstable version a while ago from the Team EOS download page, and even though it was buggy, I liked it.
I think I'll wait until the camera works to flash back to EOS, though.
I like this ROM, especially the NX 2.0. Is there anyway to make an Xposed Module to add the NX 2.0 to other ROMS?
Click to expand...
Click to collapse
In theory, xposed can do anything. It would be VERY challenging to do a module for it. Especially when I merge http://review.teameos.org/#/c/142/
bigrushdog said:
I'm pretty sure there's a VS980 floating around somewhere too ;D
Click to expand...
Click to collapse
You weren't kidding! And I found a thread from EvilDobe, Grouper up and running great... Xoom will be in the next couple days.
Sent from my Nexus 7 using XDA Free mobile app
{
"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
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