Related
Just got my N5 yesterday and I love pretty much everything about it. One tiny thing I miss coming from CM 10.2 on my old phone, is the ability to customize the "tiles" in the notification curtain. You know, when you do a 2-finger pulldown and it shows tiles to toggle wifi, airplane mode, bluetooth, etc... what do you call that anyway? Is there an "official" name for it?
Anyway, a few of my old favorites are missing, and there's no way I can find to change what's there. I'd especially like a "torch" (flashlight) toggle -- I used to use that all the time. I know there are some apps that can install a toggle bar at the top of the notification curtain in older Android versions, but it seems silly to have 2 separate groups of toggles, one on each "side" of the curtain, just because the one that's already there can't be customized, and I don't know how well those play with KitKat anyway.
Ghengis042 said:
Just got my N5 yesterday and I love pretty much everything about it. One tiny thing I miss coming from CM 10.2 on my old phone, is the ability to customize the "tiles" in the notification curtain. You know, when you do a 2-finger pulldown and it shows tiles to toggle wifi, airplane mode, bluetooth, etc... what do you call that anyway? Is there an "official" name for it?
Anyway, a few of my old favorites are missing, and there's no way I can find to change what's there. I'd especially like a "torch" (flashlight) toggle -- I used to use that all the time. I know there are some apps that can install a toggle bar at the top of the notification curtain in older Android versions, but it seems silly to have 2 separate groups of toggles, one on each "side" of the curtain, just because the one that's already there can't be customized, and I don't know how well those play with KitKat anyway.
Click to expand...
Click to collapse
You'd need root. Why can't you root?
root + Xposed Framework + GravityBox Xposed module
rootSU said:
You'd need root. Why can't you root?
root + Xposed Framework + GravityBox Xposed module
Click to expand...
Click to collapse
I just spent a few hours setting up the phone, and it would be nice not to have to do all that over again when I unlock the bootloader (and thus lose all my data...). I guess it's only one evening's setup time, so not *such* a big deal, but the other thing is that I want to keep stock firmware / OTA updates if at all possible.
As fro Xposed, I have some concerns:
* I switched to ART just after getting the phone, because I read it improves battery life (Xposed has no plans to support ART in the near future)
* I've heard that it can have stability issues -- the reason I want OTA / stock is so I can spend as little time futzing with the phone as possible and just *use* it
* Xposed opens up some security issues, IMHO
I think if it comes down to root + xposed or just using a "plain" widget, I'll probably go with the widget.
Ghengis042 said:
* I switched to ART just after getting the phone, because I read it improves battery life (Xposed has no plans to support ART in the near future)
Click to expand...
Click to collapse
Correct. For me, the experimental ART feature is not worth losing Xposed for.
Ghengis042 said:
* I've heard that it can have stability issues -- the reason I want OTA / stock is so I can spend as little time futzing with the phone as possible and just *use* it
Click to expand...
Click to collapse
No stability issues here
Ghengis042 said:
* Xposed opens up some security issues, IMHO
Click to expand...
Click to collapse
Based on what information?
You didn't address the setup-time issue -- that's one of the big ones for me. I usually have at least 40 apps installed (and yes, I actually use them!) and reconfiguring them is time consuming. I *could* futz with Titanium Backup or similar to automate some of that re-setup process, but I'd rather just avoid it in the first place if possible.
rootSU said:
No stability issues here
Click to expand...
Click to collapse
Good to hear, at some point I might still investigate -- it's going to come down to how much customization / tweaking I really *need*.
rootSU said:
(Security issues...) Based on what information?
Click to expand...
Click to collapse
I guess it's about as "dangerous" as rooting -- basically, Xposed gives modules carte blanche to do absolutely anything on your phone, and since the modules aren't distributed through a controlled / centralized store (like Google Play) and as far as I can tell aren't (always) open-source, I don't have any way to be sure they're not doing something malicious. Of course there's a bunch of other attack vectors, but installing a framework that touches every corner of the device, that then runs scripts / mods that I downloaded from some forum somewhere (no offense, guys!) on a phone that holds sensitive personal data... it just worries me a bit, y'know?
rootSU said:
You'd need root. Why can't you root?
root + Xposed Framework + GravityBox Xposed module
Click to expand...
Click to collapse
What he said.
Ghengis042 said:
You didn't address the setup-time issue -- that's one of the big ones for me. I usually have at least 40 apps installed (and yes, I actually use them!) and reconfiguring them is time consuming. I *could* futz with Titanium Backup or similar to automate some of that re-setup process, but I'd rather just avoid it in the first place if possible.
Click to expand...
Click to collapse
I didn't think it needed addressing? Yes you'll lose everything as we all did. You can backup with Helium to an extent. Maybe even it backs up everything. I have 300+ apps
Ghengis042 said:
I guess it's about as "dangerous" as rooting -- basically, Xposed gives modules carte blanche to do absolutely anything on your phone, and since the modules aren't distributed through a controlled / centralized store (like Google Play) and as far as I can tell aren't (always) open-source, I don't have any way to be sure they're not doing something malicious. Of course there's a bunch of other attack vectors, but installing a framework that touches every corner of the device, that then runs scripts / mods that I downloaded from some forum somewhere (no offense, guys!) on a phone that holds sensitive personal data... it just worries me a bit, y'know?
Click to expand...
Click to collapse
Xposed modules are still apk's and list permissions as you install them. The same sense applies as installing any apk. Read the permissions, consider the source and either install it or not. The framework doesn't touch every corner of the device. It runs everything in isolation (which is the whole point of it) but yeah that's not really relevant.
All the xposed apps are distributed via XDA, google Play or teh Xposed repo http://repo.xposed.info/module-overview - if something malicious was going on, the module wouldn't exist.
Anyway I'm not here to convince you to install it. There aren't any apps that do it though.
Hi,
Maybe not all will be functional without root but take a look at this app: https://play.google.com/store/apps/details?id=de.j4velin.notificationToggle or https://play.google.com/store/apps/details?id=com.painless.pc.
Try these apps to see what you can/can't do with the quick settings without root.
But like it has been said, rooting your device is the best way to have (almost) all what you want.
viking37 said:
Hi,
Maybe not all will be functional without root but take a look at this app: https://play.google.com/store/apps/details?id=de.j4velin.notificationToggle or https://play.google.com/store/apps/details?id=com.painless.pc.
Click to expand...
Click to collapse
Do you know if installing a settings bar on the curtain like this will interfere with... what's the term? Extended notifications? Some apps (Pocket Casts is the first that comes to mind) will show media controls (play/pause/skip) in the notification tray, but only if they're the first entry in the list -- if anything comes above them, you can't use the controls. Is that a problem with these apps?
Re,
I'm sorry but I don't know (not tested and I'm rooted)... The best is to test by yourself and see. I just provide you a link to try to help...
Ghengis042 said:
...so I can spend as little time futzing with the phone as possible and just *use* it...
Click to expand...
Click to collapse
Well that doesn't sound like much fun at all.
Ghengis042 said:
You didn't address the setup-time issue -- that's one of the big ones for me. I usually have at least 40 apps installed (and yes, I actually use them!) and reconfiguring them is time consuming. I *could* futz with Titanium Backup or similar to automate some of that re-setup process, but I'd rather just avoid it in the first place if possible.
Click to expand...
Click to collapse
Yes, TB Backup's fail when I backup 400+ apps and want to restore them altogether. Who would click Next and Install for 400+ times!!! For your point, ADB backup's are slow they really help for Unrooted devices and Guaranteeing safe apk+app-data for sure...
{
"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"
}
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, build, and use our code at CarbonROM's GitHub... and at CarbonROM Gerrit.
Disclaimer:
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!
Support:
We spend an astonishing amount of time developing this software. We can't spend much time on XDA as a result, so if you need support, please try the following:
1) Search. Search, search, search. Yes, you. I don't care how unique or important your question is, it's very likely someone has adressed it already. Especially if you're even close to new at this.
2) Read our FAQ, which can be found on our website. Carbon FAQ
3) Ask a question in your device forum. Someone will no doubt try to help you. Warning: this help may come in the form of telling you it's a dumb question that has been asked before. See step 1 - such are the perils of asking questions when you haven't done the research yourself. Android is about helping yourself.
4) Join our Discord server! There, you can connect with other Carbon users and our developers, and you can get quicker responses to your bug reports. The invite link is right below.
We recommend MindTheGApps. OpenGApps should work, but please make sure you clearly mention the gapps you're using when reporting bugs.
Get CarbonROM
Changelog
Join the CarbonROM Discord server
GitHub
Gerrit
Kernel source
Remember, every penny you send to us goes right back into the rom. It's used for hardware, server costs, etc - all the things that help us make Carbon better with every release. Your support means the world to us! If you've enjoyed Carbon, please consider a donation toward this goal. Thank you, and we hope you continue to enjoy Carbon!
XDA:DevDB Information
CarbonROM, ROM for the Sony Xperia Z3 Compact
Contributors
Myself5, CarbonROM
Source Code: https://github.com/CarbonROM
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
Based On: AOSP
Version Information
Status: Stable
Created 2018-04-01
Last Updated 2018-07-19
Wow thats good. Thank you very much.
Hi, Myself5! Thanks a lot that you still support our device though you have newer devices.
User experiences and issue list for 2019-03-11 Release
First of all, thanks to @Myself5, @rcstar6696 and all other members of the CarbonROM team for the release of CarbonROM 6.1 Oreo for our device! :good::victory:
User experiences with CarbonROM 6.1:
Installation was smooth. I flashed cr-6.1 and OpenGapps ARM 8.1 on top of my working cr-5.1 installation (dirty flash), so all of my apps and their settings were kept. MindTheGapps 8.1.0 arm, which are recommended by the Carbon devs, are also working fine. Keep in mind that there is no guarantee that a dirty flash works in all cases, so you might have to wipe your data partition. This generally is recommended when updating to a new Android version anyway.
Besides of some small issues (see below), everything runs stable and the system is snappy and smooth. Thermal management and charging speed is fine.
Magisk 16.0 works fine, as well as Xposed Framework (SDK 27) v90-beta3 or alternatively Systemless Xposed (SDK 27) v90.1-beta3 Magisk module. However, there are some force-closes of background apps every now and then, caused by the beta status of Xposed v90.
My Xperia Torch Boost Magisk module is still working well on cr-6.1.
Selinux is set to enforcing, just as it was in cr-5.1.
I found out that Android Messages SMS/MMS app has a high battery drain, which e.g. is also reported for Pixel devices on Android 8 Oreo, so a general bug by Google. Because of this, I switched to Textra SMS (of course you can also use one of the other SMS/MMS apps around), which fixes the battery drain.
Improvements in comparison to cr-5.1:
The camera button now acts exactly like in Sony Stock ROMs, so now focussing and taking pictures is possible with Stock Sony Camera. You can also invoke the Stock Sony Camera by long-pressing the camera button, just like in Stock ROMs, but this doesn't work when the device is off or locked. In this case you can use a double press on the power button, which can be enabled in Carbon Fibers settings.
Booting the device is noticably faster than on cr-5.1.
Lower battery drain than on cr-5.1.
Better, more uniform design.
The ROM is being updated to the latest Android Security Patches.
Apps can be "locked" in the Recent Apps, so when pressing the Clean All button, they keep running.
4K video recordings are possible.
Missing features in comparison to cr-5.1:
There is no option to turn on Network Traffic Indicators yet. (This has been added in 2018-04-05 Weekly.)
Default Camera-App does not allow to save photos to sd-card, puts photos in wrong orientation and is all around very limited. However, there are good alternatives like Open Camera and the Stock Sony Camera. (Since 2018-05-01 Weekly, Snap Camera is used again.)
Issues in Carbon ROM 6.1:
Video recording doesn't work yet with the built-in Camera app, as well as with several other apps like Open Camera and the Stock Sony Camera. Until this is fixed, you can use Footej Camera for video recording as a workaround. (This has been fixed in 2018-05-08 Weekly by @AdrianDC and Milos Ratkovic.)
DoubleTap2Wake isn't working yet. (This has been fixed in 2018-04-11 Weekly.)
The SystemUI (Quick Settings etc.) always is shown in white theme. I know that this is Oreo's default design, but it should change to dark theme when using a dark wallpaper. (See @Myself5's reply in post #14.)
The gyroscope doesn't work properly yet with certain apps, e.g. Vr Tester - Gyroscope Sensor App and Accelerometer Gyro Tester. (Obviously this is a bug of those apps or of Oreo in general, since @Myself5 could reproduce it on his Pixel 2 XL device, running on stock ROM. Many other apps that use the gyroscope are working fine on cr-6.1.)
Saving and accessing files on SD card doesn't work for certain apps and tools, which could be a Linux permission or SELinux denial issue. For further information and partial workarounds, see post #45, post #49 and post #51. (This has been fixed in 2018-06-05 Weekly.)
Screen Cast still isn't working for me with 2018-04-11 Weekly (I tested this with a Sony and an LG Smart TV which both connected fine to my Z3c on stock ROMs), even with the new boot image from post #103 which is working with @Myself5's Fire TV stick and Wireless Display Adapter. This has been fixed in 2018-04-17 Weekly.
WiFi isn't working on 5 GHz band in some countries, as has been reported in post #1634 on the Z2 cr-6.1 thread, including links to posts with possible workarounds and fixes. There's also an article in the xda wiki with further information. Since 2018-05-01 Weekly, Germany (DE) is used as Wifi country code, but there have been several reports by users from other countries that this doesn't work for them, so is not an universal fix. As a workaround, until this is fixed, you can use my Magisk module from post #195, which you have to change to your own country code by following the instructions that I gave there. Edit: @marcogiannetta posted an improved Magisk module in post #373 which changes the Wifi Country Code accordingly to the system language. A similar issue (wifi dosent connect in Iran) also has been reported on the bug tracker and is being looked after by the devs. Edit: According to post #2092 on the Z2 thread, this issue can also be fixed by installing WiFi regional problem solver Xposed module.
Music files can't be played from SD card with Vanilla Music, Sony Music and several other players. This issue was fixed in 2018-05-08 Nightly, but reappeared on 2018-05-15 Nightly. Until this is fixed again, you can use jetAudio HD Music Player as a workaround. (This has quickly been fixed again in the 20180515-2340 Weekly build.)
When making a screenshot via the Power menu, most of the time the Power menu itself is visible in the screenshot. There should be a slight delay (just 1/10th second might already be sufficient), so the Power menu is already hidden again before the screenshot is taken. This has been fixed in 2018-07-05 Weekly.
Apps like Netflix, MyCanal and MagineTV don't work because DRM WideVine is not supported yet, whereas in CarbonROM 5.1 it was supported. This has been fixed in 2018-08-15 Release.
Lock screen rotation has been removed since 2018-09-11 Release. It was a useful feature when using the phone in landscape orientation e.g. in a car holder and IMO should be added again. Edit1: As a workaround, I made LockscreenRotationEnabler Magisk module which adds this functionality by adding a setting to 'build.prop'. Edit2: Lock screen rotation can also be enabled with GravityBox [O] Xposed module.
NFC extended length isn't supported, which is needed e.g. for reading identity cards with apps like AusweisApp2. (This has been fixed in 2019-03-11 Release.)
NFC-HCE isn't supported, which is needed for Google Pay. (This has been fixed in 2019-03-11 Release.)
Wish list for some further improvement of Carbon ROM 6.1:
Long press camera button to wake and launch camera app when the screen is off or the phone is locked. Edit: I found a workaround which I described in this post.
A toggle to switch to dark UI theme for quick settings. Edit1: The dark UI theme can be forced with ForceDarkModeOreo Xposed module. Edit2: ForceDarkModeOreo unfortunately is one of the Xposed module which cause random app crashes, so it's not advisable to use it. Let's hope that the devs will add this feature eventually.
About time this one got its own thread, huh
Everything works great, no bugs so far and no problem with camera recording (using Footej Camera), though missing hardware key rebindings and i cant enable power notifications
Downloading right now. Lets see how it compares to Omni 8.1
EDIT (my comment from a few pages later):
After a few days with it, I can say it's already suitable for daily use. Using MindTheGapps (tho I will switch to OpenGapps pico, I don't want Google app ), Magisk 16.
It's smooth and very stable. No crashes or major issues for me so far.
Battery life is acceptable, worse than stock (doh), and perhaps even LOS 14.1. Thermal management and charging speed is fine.
No idea about the camera, mine is broken (HW) and I never use front one.
A few suggestions and comments:
Add some power balancing options like with LOS (better performance or battery life).
Also, I love how you can customize RGB values on LOS to make it more yellowish even during day, plus night light. Any idea what workaround I could use? My blueish screen is killing me and I can't use night light all day.
Good to hear night mode is being worked on.
How to make quick tiles menu like on 7.x? I preferred auto expanding options for mobile data and silent mode. Can't find it in fibers.
Hi, Great that development is ongoing - Thanks a lot!
One thing, got the same problem with the none carbon Oreo Version:
got problems with whatsapp. Video isn't running. The phone doesn't build up a connection. Chat works, but whatssap call or video not.
Skype ist working without problems ...
Any Ideas?
I installed it with a full wipe - system, cache, dalvik, data, internal storage. Used TWRP 3.2 for ROM (to mind error 7) and TWRP 3.1 for installation of MindTheGApps.
Thanks for help!
Thanks for the ROM, working great for me.
I have accidently deleted live wallpaper picker. Tried download a few different versions from the internet but nothing works. Where can I get the one this ROM is using?
FYI: I now posted my first impression and experiences in post #4. I'm planning to update it when new Weeklies arrive or when other users report some issues that are worth listing.
@Myself5: Please have an eye on the missing features and issues that I postet there, so they will hopefully get fixed in the next Weeklies.
Happy Easter to all of you!
Nice post, okij
okij said:
[*]The SystemUI (Quick Settings etc.) always is shown in white theme. I know that this is Oreo's default design, but it should change to dark theme when using a dark wallpaper. Also, forcing dark theme via Dark Tricks Xposed module doesn't work.
Click to expand...
Click to collapse
It'd definitely be nice to have the dark theme overall. I'm not sure if I'm the only one, but I really dislike the white Oreo style. Is it possible to have it look more like Nougat, also in the 'settings' app? I, for one, always loved the color scheme that Goolge made from Lollipop to Nougat.
Kocane said:
Nice post, okij
It'd definitely be nice to have the dark theme overall. I'm not sure if I'm the only one, but I really dislike the white Oreo style. Is it possible to have it look more like Nougat, also in the 'settings' app? I, for one, always loved the color scheme that Goolge made from Lollipop to Nougat.
Click to expand...
Click to collapse
Doesn't substratum work?
Metall Boy said:
Doesn't substratum work?
Click to expand...
Click to collapse
Substratum works fine
Greets ted!
okij said:
FYI: I now posted my first impression and experiences in post #4. I'm planning to update it when new Weeklies arrive or when other users report some issues that are worth listing.
@Myself5: Please have an eye on the missing features and issues that I postet there, so they will hopefully get fixed in the next Weeklies.
Happy Easter to all of you!
Click to expand...
Click to collapse
For things like Networks indicator: Some additional features will surely come with time, as you said.
Video recording: I think it was the Z3 thread where I explained it in detail: The commits to fix Video recording do work (kind of), but are WIP, so we're all working on getting them stable and polished, then they will be merged as fast as possible. When that happens is rough to estimate, I wouldnt expect it to take much longer than 2-3 Weeks though.
DT2W: As you said. Fixed and merged, will be included in the Next Weekly.
For the Dark Theme: Isn't that a Pixel only feature? For that to work you'd need assets for a "dark theme". On Pixel devices those are on the /vendor partition, so obviously not present on our Z3C. Correct me if I'm wrong please.
Thanks for the detailed report, will gladly keep on checking it with followup builds.
Metall Boy said:
Doesn't substratum work?
Click to expand...
Click to collapse
It does. Install the Substratum app and flip the switch in CarbonFibers -> Privacy to make it work.
The Switch is disabling the Security measures Google merged in the March ASBs. By default Subs completely removes them, but we decided to go for an opt-in for those that want to use it while keeping the "security" Google intended to have with merging it for those that don't want to.
First off all, thank u for this amazing work! Rom is awesome.
1 - I saw that DT2W is fixed in the next build. It's possible add a feature present in gravitybox? When smartphone is in the pocket, sometimes screen turns on because DT2W. Gravitybox has an option to disable this when proximity sensor is covered.
2 - Someone can tell me if led notification works? Not work here...
Sorry bad English...
Sorry for asking again - anyone using this rom with working whatsapp video oder whatsapp call? When I try it the connection always hang up - no connection. Chat works.
Any idea anyone?
Thanks!
marlontravagli said:
1 - I saw that DT2W is fixed in the next build. It's possible add a feature present in gravitybox? When smartphone is in the pocket, sometimes screen turns on because DT2W. Gravitybox has an option to disable this when proximity sensor is covered.
Click to expand...
Click to collapse
Yes, this is a great additional feature when using DT2W and one of the reasons that I use GravityBox. @Myself5: It would be great if you could implement this feature for those of us who don't use Xposed. In GravityBox it can be found under "Power tweaks -> Proximity wake up" and the additional option "Ignore for incoming call" which is also worth implementing.
2 - Someone can tell me if led notification works? Not work here...
Click to expand...
Click to collapse
I can confirm that LED notifications are working here, just tested this with missed call (using Google Dialer) and incoming email (using AquaMail).
---------- Post added at 10:44 PM ---------- Previous post was at 10:42 PM ----------
Laus_bub said:
Sorry for asking again - anyone using this rom with working whatsapp video oder whatsapp call? When I try it the connection always hang up - no connection. Chat works.
Click to expand...
Click to collapse
I don't use WhatsApp, but I guess that the not working video call has to do with the not fully working video recording (see #1 in the issues list I posted here).
Hello All,
I just updated from CR5.1 to 6.1 this day, and tried to install Magisk.
But Magisk Manager failed to update, and if I flashd through TWRP (the good one, 3.1) I'm stucked in Sony logo.
Log said :
"Parsing boot image : [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
No boot image magic found!
! Unable to unpack boot image
Failed!
! Installation failed"
I have to "install" Magisk uninstaller in TWRP to bring life to my phone
EDIT : magisk 16.0, manager 5.6.4.
Some idea pls ?
ElLoloFR said:
Hello All,
I just updated from CR5.1 to 6.1 this day, and tried to install Magisk.
But Magisk Manager failed to update, and if I flashd through TWRP (the good one, 3.1) I'm stucked in Sony logo.
Log said :
"Parsing boot image : [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
No boot image magic found!
! Unable to unpack boot image
Failed!
! Installation failed"
I have to "install" Magisk uninstaller in TWRP to bring life to my phone
EDIT : magisk 16.0, manager 5.6.4.
Some idea pls ?
Click to expand...
Click to collapse
Did you try removing all other modules? For me the very same thing is happening if I try to use the fbind (Folder Bind) module. You can try to remove all modules, if u use the Magisk Manager for Recovery Mode (mm).
I tried and :
"No magisk installation found."
So I installed Magisk v16, then installed this one.
I could install mm, this was the only module installed.
I uninstalled mm, rebooted without uninstalling Magisk V16, and the phone booted !
But I can't open Magisk Manager v5.6.4, stucked in the app logo...So Magisk seems to be installed, but I can't use it :/
EDIT : Well, after a recovery reboot, reinstall f magisk V16, phone boot correctly and Magisk is alive.
I don't know how this is working, but it's working.
No doubt, you helped me, many thanks
Which one are you using? I'm currently using the Pixel Experience with a launcher added and it looks awesome. Seems better than Xposed, which right now I'm using for the Youtubebackgroundplayback.
I am currently using one for Digital Well Being. It is a new thing that tells you how much you are in your device. You can also set timers for apps and stuff to help you take a break from the "Digital Life". It is mainly for Android Pie and only a handful of devices. But I am using Pie on my Motorola Z2 now.
I was using the Pixel Experience, but I was having issue with contacts FC everytime I opened it up.. did not start until that module was installed...
Cloudflaredns, busybox, energized, wifi-bonding.
Blex or Magic charging controller. VoEnabler, debloater, youtube vance, single user mod, and google san MOD font.
XPrivacy Alternative?
Sorry for the dumb question, but I haven't found much with my somewhat weak google-fu. Does anyone know of a Magisk module that works similarly to XPrivacy/XPrivacyLua? I mainly used it for location spoofing, and it did that really well. I've tried Smali, but I must be configuring/patching it wrong because apps never grab the location I've set in a fake GPS app.
Thanks in advance for any help!
SpoonThief said:
Sorry for the dumb question, but I haven't found much with my somewhat weak google-fu. Does anyone know of a Magisk module that works similarly to XPrivacy/XPrivacyLua? I mainly used it for location spoofing, and it did that really well. I've tried Smali, but I must be configuring/patching it wrong because apps never grab the location I've set in a fake GPS app.
Thanks in advance for any help!
Click to expand...
Click to collapse
Maybe a dumb question, but why not just use magisk xposed module and use xprivacy/xprivacylua?
Update: Issue has been solved; however, don't ask me how. I simply don't know; all I know is all is working fine now!
Thread is going to be closed.
I'm pinging my post that I've made in a specific ROM thread here three days ago, because I haven't received any response (besides 5 thanks ).
*******************************
Two weeks ago, I purchased a used SM-G955F to become my daily used device. However, it came with stock Pie on a BL v5 i.e. I immediately knew that it will be impossible to downgrade to Oreo or even better to Nougat. For personal reasons, I rather use Nougat and all of our devices are currently running Resurrection Remix Nougat. But anyhow, no reason to lock back and I tried to make the best out of the current situation. And initially, it looked very promising. I discovered this great ROM, for which I'm very grateful to Stricted. So the current configuration of my SM-G955F is as follows:
lineage-16.0-20190922-UNOFFICIAL-dream2lte, unchanged kernel, rooted with Magisk v20.0
Magisk module as shown in screenshots but including EdXposed
as all of our devices, GApps free running with microG (powered by NanoDroid v22.4), signature spoofing patched by SmaliPatcher
Two EdXposed modules as shown in screenshot
Firewall (AFWall+), Adaway and XPrivacyLua not (yet) enabled
ROM is working really well, no issues except the below described ones but definitely no issues with root, Magisk, signature spoofing or EdXposed.
I'm not using and never will use anything of Google (only exception is the Google Play Store modified by Setialpha), Facebook etc. i.e. no Whatsapp, Google contacts or calendar etc. As messenger I use Conversations, a Jabber/XMPP client; in order to synchronise my contacts and calendar DAVx⁵.
And here are the issues that don't allow me to become the SM-G955F my daily used device:
Conversations doesn't connect to my existing Jabber account with the notification "server not found" (same applies when I try to create a new jabber account) but I can assure the server is working as I see on my other devices.
About the same applies to DAVx⁵, which is unable to connect to my email provider (posteo.de) for the synchronisation of contacts and calendar.
As far as I know the first one uses ports 8443 and 8843, the latter ports 5222 and 5269.
And I believe, very important: After I initially had the issues on LOS, I reverted back to stock Pie (i.e. bloated with all Google things and services as well as a lot of Samsung crap) but both issues are also existing on stock. First, I can clearly state they are not LOS issues or ones of this wonderful ROM.
However, as initially stated I've always been on (maximum) Nougat and don't know what Google additionally implemented or changed on the way via Oreo to Pie.
Can it be that the above mentioned ports are blocked?
Any means (e.g. via ADB) to open these ports?
Or any other idea that would allow me to become the SM-G955F with this LOS 16.0 my daily driver.
I'm happy and ready to provide any further information and logs...
try to completely disable af firewall by removing root permission and unchecking xposed and freezing it and then reboot and then try again ...sonetimes you block stuff in af that actually includes other dependencies under a general description like "system" ** only an example
also sometimes if you restore af firewall rules it might seem like you are allowing connections but af is blocking in background ...
KevMetal said:
try to completely disable af firewall by removing root permission and unchecking xposed and freezing it and then reboot and then try again ...sonetimes you block stuff in af that actually includes other dependencies under a general description like "system" ** only an example
also sometimes if you restore af firewall rules it might seem like you are allowing connections but af is blocking in background ...
Click to expand...
Click to collapse
Thanks for the advice but see what I also stated above:
...
And I believe, very important: After I initially had the issues on LOS, I reverted back to stock Pie (i.e. bloated with all Google things and services as well as a lot of Samsung crap) but both issues are also existing on stock. First, I can clearly state they are not LOS issues or ones of this wonderful ROM.
...
Click to expand...
Click to collapse
During the attempt with stock Pie no firewall or Xposed was installed. The issue must be somewhere else. By the way, on the Samsung SM-G935F that I just set up a few days ago with lineage-15.1-20191016-UNOFFICIAL-microG-signed-hero2lte, everything is working as advertised. That device is currently my daily playground.
Westfalenpfeil said:
Thanks for the advice but see what I also stated above:
During the attempt with stock Pie no firewall or Xposed was installed. The issue must be somewhere else. By the way, on the Samsung SM-G935F that I just set up a few days ago with lineage-15.1-20191016-UNOFFICIAL-microG-signed-hero2lte, everything is working as advertised. That device is currently my daily playground.
Click to expand...
Click to collapse
ok i understand . im also using a Samsung S7 as my daily driver. its still a good device despite its age .
is it possible that you have flashed a custom kernel along the way and when you returned to stock , you didnt return to stock kernel and that it is messing with the ip tables ..
have you tried looking into flashing kernel ?
KevMetal said:
ok i understand . im also using a Samsung S7 as my daily driver. its still a good device despite its age .
is it possible that you have flashed a custom kernel along the way and when you returned to stock , you didnt return to stock kernel and that it is messing with the ip tables ..
have you tried looking into flashing kernel ?
Click to expand...
Click to collapse
No custom kernel has been flashed yet. And currently no time available to dig deeper and/or to search for suitable ROM's and kernel. The S8+ sits on its case. I'll update this thread if situation changes.
Anyhow, I appreciate the advices and ideas.
Thread closed as per request of OP
Disclaimer
Your warranty is now void. We are not responsible for bricked devices, lost data, broken sd cards, or failure for your device to preform some important function. You are choosing to make modifications to your own device, and accept all of the risks involved.
Click to expand...
Click to collapse
LineageOS is a long standing android custom rom, derrived from AOSP with contributions from the community. By default, no google apps or frameworks are built into the rom.
microG is an open source, lightweight replacement for the proprietary google apps and frameworks. Maybe most importantly, it includes UnifiedNlp which provides wifi and cellular based geolocation which are necessary for location services apps to function properly.
This rom includes:
- fdroid & fdroid priviledge extension
- microG and sig spoofing patches to support it
Whats working:
everything, it seems
Whats not working:
nothing? Note that many camera apps don't support the camera cluster properly and instead just use one sensor. Instructions in the github repo are available to setup GCam which can use all of the sensors.
Please comment if you find something is not working properly.
Install Instructions:
https://github.com/SolidHal/lineageos-microg-oneplus-lemonade#install
Sources and Instructions to build your own images and custom recovery:
https://github.com/SolidHal/lineageos-microg-oneplus-lemonade#build
you can modify "build_lemonade.sh" to remove microG, AndroidAuto, etc if you like.
Download:
https://github.com/SolidHal/lineageos-microg-oneplus-lemonade/releases
Sources:
https://github.com/SolidHal/android-auto-stub
https://github.com/SolidHal/android_device_oneplus_lemonade
FAQ:
Q: Whats different from https://forum.xda-developers.com/t/rom-unofficial-lemonade-11-lineageos-18-1.4298845/ ?
A:
- fixed the camera cutout alignment (some fun math involved in drawing curves)
- aligned the status bar items with the camera cutout
- microG built in
- Android Auto support
Huge Thanks:
To andr01dfr3ak for the initial lemonade device tree.
To the folks in this thread about getting Android Auto working with microG: https://github.com/microg/GmsCore/issues/897 especially @dylangerdaly who figured out the Android Auto stub
Does stuttering still exist?
amonstercattt said:
Does stuttering still exist?
Click to expand...
Click to collapse
I have yet to observe any stuttering, but I can't promise it doesn't exist. In what situations do you see it happen, and using what rom?
SolidHal said:
I have yet to observe any stuttering, but I can't promise it doesn't exist. In what situations do you see it happen, and using what rom?
Click to expand...
Click to collapse
Even if I turn on 120Hz, there will still be the phenomenon of sliding out frames (lineage os).
amonstercattt said:
Even if I turn on 120Hz, there will still be the phenomenon of sliding out frames (lineage os).
Click to expand...
Click to collapse
I'm sorry, what do you mean by "the phenomenon of sliding out frames"?
and are you saying that you observe phenomenon on this lineageos build, or other ones?
Awesome work, I'm interested in the development process and was wondering what keeps an unofficial ROM like this from becoming an official LineageOS build?
SolidHal said:
LineageOS is a long standing android custom rom, derrived from AOSP with contributions from the community. By default, no google apps or frameworks are built into the rom.
microG is an open source, lightweight replacement for the proprietary google apps and frameworks. Maybe most importantly, it includes UnifiedNlp which provides wifi and cellular based geolocation which are necessary for location services apps to function properly.
This rom includes:
- fdroid & fdroid priviledge extension
- microG and sig spoofing patches to support it
Whats working:
everything, it seems
Whats not working:
nothing? Note that many camera apps don't support the camera cluster properly and instead just use one sensor. Instructions in the github repo are available to setup GCam which can use all of the sensors.
Please comment if you find something is not working properly.
Install Instructions:
https://github.com/SolidHal/lineageos-microg-oneplus-lemonade#install
Sources and Instructions to build your own images and custom recovery:
https://github.com/SolidHal/lineageos-microg-oneplus-lemonade#build
you can modify "build_lemonade.sh" to remove microG, AndroidAuto, etc if you like.
Download:
https://github.com/SolidHal/lineageos-microg-oneplus-lemonade/releases
Sources:
https://github.com/SolidHal/android-auto-stub
https://github.com/SolidHal/android_device_oneplus_lemonade
FAQ:
Q: Whats different from https://forum.xda-developers.com/t/rom-unofficial-lemonade-11-lineageos-18-1.4298845/ ?
A:
- fixed the camera cutout alignment (some fun math involved in drawing curves)
- aligned the status bar items with the camera cutout
- microG built in
- Android Auto support
Huge Thanks:
To andr01dfr3ak for the initial lemonade device tree.
To the folks in this thread about getting Android Auto working with microG: https://github.com/microg/GmsCore/issues/897 especially @dylangerdaly who figured out the Android Auto stub
Click to expand...
Click to collapse
I must say this is an awesome build. I have been away from this for awhile and this made it an easy return. I am going to switch phones. Any advice on how to get back to stock from this build?
Thank you
rulerofmydomain said:
I must say this is an awesome build. I have been away from this for awhile and this made it an easy return. I am going to switch phones. Any advice on how to get back to stock from this build?
Thank you
Click to expand...
Click to collapse
Always best way is MSM. Don't doubt this build is excellent but I would recommend EvoX. Head to the thread and go into the TG for the latest build. Have fun
pocho dobo said:
Always best way is MSM. Don't doubt this build is excellent but I would recommend EvoX. Head to the thread and go into the TG for the latest build. Have fun
Click to expand...
Click to collapse
Know of any good how to for MSM (don't know it )
Thank yo u
rulerofmydomain said:
Know of any good how to for MSM (don't know it )
Thank yo u
Click to expand...
Click to collapse
Device specifics would be a good start to guide you in the right direction!
pocho dobo said:
Device specifics would be a good start to guide you in the right direction!
Click to expand...
Click to collapse
Thank you
It is an Unlocked US OnePlus 9 8/128 Model LE2115