Develop Bugs

[ROM] CarbonROM Linaro GCC 4.7/-O3 JB 4.2.2 Unofficial 8.03.13

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.

[ROM] [4.4.4] SlimKat (Bacon) [STABLE/WEEKLY]

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?

[ROM][N10][7.1.2_r24]★ Pure Nexus ★ Substratum ★[15/07/17]

{
"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

[ROM][DISCONTINUED] LineageOS 18.1 for F(x)tec Pro1

{
"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...

Development [UNOFFICIAL][ROM][13.0][ENCRYPTION] Pixel Experience 13 Plus Edition for A52s 5G

{
"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"
}
PixelExperience for Samsung Galaxy a52s 5G [a52sxq]
What is this?
PixelExperience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, boot animation)
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
Based on Android 13
Whats working?
​
RIL !
5G
Audio
Wifi
Hotspot
Calls
WifiDisplay
Bluetooth
OMX
Camera
NFC
Fingerprint
Screen-Off-FOD
Mobile data
GPS
DT2W
...
Known issues
​
VoLTE/VoWIFI (Samsung's implementation doesn't work on AOSP)
Permissive SeLinux
Maybe more, feel free to report
DON'T FLASH GAPPS, THEY'RE ALREADY INCLUDED
Install Instructions
Make sure you are on OneUI 5 firmware (D bootloader or newer and U2 rev) before flashing this ROM, otherwise the installation might fail or not boot!
​
Make sure your device's bootloader is unlocked.
If not done before, flash blank VBMeta with Odin in AP slot.
Make sure to have the latest available version of TWRP/OrangeFox installed.
If wanted, backup all your necessary partitions (super, boot, vendor_boot, data, EFS) before flashing this in case something goes wrong.
Download the PE build for your device from the link below.
Flash the PE zip using the "Install" button.
Format data in TWRP/OrangeFox as the very last thing, otherwise you may end up in a bootloop if coming from stock ROM.
Wipe metadata and cache partitions. This only has to be done once when you install PE.
Reboot
DOWNLOAD LINKS
ROM
PE Recovery​
Credits
To...
Me, for spending my time on this project
@Simon1511 for his trees
@BlackMesa123 for his help with getting QKGI to work and general help
All the testers
Maybe more, feel free to tell me if I forgot someone
Android OS version: 13
Security patch level: May 2023
Build author/Device Maintainer: Ryzen5950XT
Source code: https://github.com/Simon1511/android_kernel_samsung_sm7325
ROM Developer: jhenrique09

PATCH NOTES
Code:
13/4/23
- Initial build
Code:
19/4/23 Build
- Adjusted powerhint for better performance and battery life
- Temporarily switched to prebuilt camera provider to fix camera lags and crashes at the cost of macro camera
- Fixed missing hardware accerleration for colours (Night light, Color Modes, Reading Mode)
- Fixed laggy/non-hardware accelerated video playback
- Switched to R RIL blobs to fix signal strength indicator
- Added single tap to show AOD setting
- Prevent booting failures ("SECURE CHECK FAIL: modem") - thanks to @BlackMesa123
Code:
28/4/23
- Actually fix camera lags and crashes
- Fix single tap to show AOD setting
- Dynamically link correct IPA/WPSS firmware for all different bootloader revisions to fix Wifi
- Correctly show "Charging slowly" and "Charging rapidly" on lockscreen
- Made PE recovery work by shipping prebuilt kernel and modules

Reserved

Reserved

Great job guys!

Many thanks and very well noted, I'll surely try it......
But.....
Is EvolutionX planned for this device ?
Thanks

Jack Droid said:
Many thanks and very well noted, I'll surely try it......
But.....
Is EvolutionX planned for this device ?
Thanks
Click to expand...
Click to collapse
Trees are available, build EvolutionX yourself if you want it. In the meantime, please stop asking every developer on here and also on the a52 4g xda page to build it. Thanks.

Ryzen5950XT said:
Trees are available, build EvolutionX yourself if you want it. In the meantime, please stop asking every developer on here and also on the a52 4g xda page to build it. Thanks.
Click to expand...
Click to collapse
I don't understand your reply.
Why stop asking ? This is a forum where people ask and other reply ( or not )
To ask for something is legit and doesn't break any Forum rules.
If you want, you can simply doesn't reply instead of trying to mute the users....
Moderator, pls tell something

Jack Droid said:
I don't understand your reply.
Why stop asking ? This is a forum where people ask and other reply ( or not )
To ask for something is legit and doesn't break any Forum rules.
If you want, you can simply doesn't reply instead of trying to mute the users....
Moderator, pls tell something
Click to expand...
Click to collapse
No, it's you who is in the wrong here. It's incredibly annoying having someone bothering you over and over and over again for the same thing, especially when you ask in a thread that has nothing to do with EvolutionX. I agree that you have the right to ask for the ROM to be built, but you should ask in your own thread or as Risen said, learn how to build it yourself.

I have installed PE this morning and so far everything works fine! Thanks for all the effort!

To all of you - early testers, is this ROM usable as daily driver?
Mobile payments? gcam/any other camera working? Is ROM faster than stock OneUI 5.1?
What about signal strength, battery backup, RAM management...?
I was very, very satisfied with this ROM on my previous device (Poco F1), so looking forward to try it, but I don't have enough time to do the clean install yet.

ShaDisNX255 said:
No, it's you who is in the wrong here. It's incredibly annoying having someone bothering you over and over and over again for the same thing, especially when you ask in a thread that has nothing to do with EvolutionX. I agree that you have the right to ask for the ROM to be built, but you should ask in your own thread or as Risen said, learn how to build it yourself.
Click to expand...
Click to collapse
This stops here. Flaming and disrespect will absolutely not be tolerated on XDA.
In addition, we would all do well to remember that developers who share their work on XDA are not compensated; this is a hobby for most of them, and the best thing you can do is be grateful for the time and effort they have put into their work.
That being said, it is the developer's own prerogative how much time and effort they spend on the project. You as the end user are NOT entitled to updates. DO NOT ask for updates/ETAs/etc; be respectful of the fact that each developer's time is their own. You did not pay for the software, and they owe you nothing.
I highly recommend you read and review the Forum Etiquette linked in my signature.

pp202ku said:
To all of you - early testers, is this ROM usable as daily driver?
Mobile payments? gcam/any other camera working? Is ROM faster than stock OneUI 5.1?
What about signal strength, battery backup, RAM management...?
I was very, very satisfied with this ROM on my previous device (Poco F1), so looking forward to try it, but I don't have enough time to do the clean install yet.
Click to expand...
Click to collapse
I have installed it and it sure is ready as daily driver, although I don't know how you use your phone.
Mobile payments: not using it myself but it seems to work.
GCam: available, with some tweaking tho
Signal strength, battery backup, RAM management: no opinion yet.

V0latyle said:
This stops here. Flaming and disrespect will absolutely not be tolerated on XDA.
In addition, we would all do well to remember that developers who share their work on XDA are not compensated; this is a hobby for most of them, and the best thing you can do is be grateful for the time and effort they have put into their work.
That being said, it is the developer's own prerogative how much time and effort they spend on the project. You as the end user are NOT entitled to updates. DO NOT ask for updates/ETAs/etc; be respectful of the fact that each developer's time is their own. You did not pay for the software, and they owe you nothing.
I highly recommend you read and review the Forum Etiquette linked in my signature.
Click to expand...
Click to collapse
Hi V0latyle,
thanks for your action and I agree with you about Flaming and disrespect .
Thanks again

Jack Droid said:
Why stop asking ? This is a forum where people ask and other reply ( or not )
To ask for something is legit and doesn't break any Forum rules.
Click to expand...
Click to collapse
We may not have a written rule specifically against requests, but this falls largely into the rules on disrespect:
2.3 Flaming / Lack of respect: XDA is about sharing and this does not involve virtual yelling (flaming) or rudeness. Flaming or posting with a lack of respect is unacceptable. Treat new members in the manner in which you would like to have been treated when you were a new member. When dealing with any member, provide them with guidance, advice and instructions when you can, showing them respect and courtesy. Never post in a demanding, argumentative, disrespectful or self-righteous manner.
Click to expand...
Click to collapse
As I pointed out in my post above, you need to remember that development projects shared on XDA are essentially hobbies. We do not allow paid software, so the developers are sharing their work for free. Because the software is free, this means that you are NOT entitled to updates, fixes, or even support. If you had specifically contracted someone to build you a ROM with an update timeline laid out in said contract, that would be different - but the point is moot because again, paid software is not permitted here.
The bottom line: It is rude to ask for updates when you're using something that someone developed on their own. If you can't wait for updates, I concur with @ShaDisNX255 - you should learn to build it yourself.
Be grateful for the fact that someone shared their hobby with you, but remember that because they shared it for free, they owe you nothing.

V0latyle said:
We may not have a written rule specifically against requests, but this falls largely into the rules on disrespect:
As I pointed out in my post above, you need to remember that development projects shared on XDA are essentially hobbies. We do not allow paid software, so the developers are sharing their work for free. Because the software is free, this means that you are NOT entitled to updates, fixes, or even support. If you had specifically contracted someone to build you a ROM with an update timeline laid out in said contract, that would be different - but the point is moot because again, paid software is not permitted here.
The bottom line: It is rude to ask for updates when you're using something that someone developed on their own. If you can't wait for updates, I concur with @ShaDisNX255 - you should learn to build it yourself.
Be grateful for the fact that someone shared their hobby with you, but remember that because they shared it for free, they owe you nothing.
Click to expand...
Click to collapse
Thanks again

Does the option to set the minimum refresh rate to 90Hz exist? Because on the default 60Hz the UI feels sluggish, and I don't want to set the minimum refresh rate to 120Hz because I think it would use more battery.

Arm1nas said:
Does the option to set the minimum refresh rate to 90Hz exist? Because on the default 60Hz the UI feels sluggish, and I don't want to set the minimum refresh rate to 120Hz because I think it would use more battery.
Click to expand...
Click to collapse
Nope, its either 60 or 120, or you can try using commands to set it to 90.

Are the Pixel goodies available too like unlimited photo backup?

chocowilliam said:
Are the Pixel goodies available too like unlimited photo backup?
Click to expand...
Click to collapse
Yes of course.