Database Develop

Differences between CM 12.1 and SlimLP

Are there any major differences between these two firmwares respecitvely are there any specific strengths or weaknesses?

oliman99 said:
Are there any major differences between these two firmwares respecitvely are there any specific strengths or weaknesses?
Click to expand...
Click to collapse
I think it is personal preference tbh, however I prefer SlimLP since I have messed around with custom ROMs for a while and currently run SlimLP on my phone as well. Also I like the customization that comes with SlimLP more than the plainness of ordinary CM.

The SlimLP rom developers don't recommend using xposed due to some ART optimizations. If anyone really wants xposed someone did suggest trying wanams modified xposed version.

rjmxtech said:
I think it is personal preference tbh, however I prefer SlimLP since I have messed around with custom ROMs for a while and currently run SlimLP on my phone as well. Also I like the customization that comes with SlimLP more than the plainness of ordinary CM.
Click to expand...
Click to collapse
I have been considering switching from cm 12.1 to slim lp on my fire. When you say additional customization what does that elude to? Theming and visual, or performance customization?

blueberry.sky said:
The SlimLP rom developers don't recommend using xposed due to some ART optimizations. If anyone really wants xposed someone did suggest trying wanams modified xposed version.
Click to expand...
Click to collapse
I've got xposed on the cm 12.1 rom. Haven't tried yet on SlimLP though.

If you do try it on SlimLP go for wanams xposed. And of course let us know if it you get any problems.

blueberry.sky said:
If you do try it on SlimLP go for wanams xposed. And of course let us know if it you get any problems.
Click to expand...
Click to collapse
I successfully flashed v2.1 of SlimLP, and then I tried v75 and v78 of wanams xposed (preceded with the mandatory installation apk). Both versions led to bootloop; I was able to remove the bootloop by using the uninstallation apk.
Since I want/needed xprivacy I switched to CM12.1 but gapps has stopped working. When there's a new version of SlimLP I might try again.
EDIT: I fixed the gapps in CM12.1 (12/04 built) by (1) doing a factory reset and (2) uninstalling the Playpermissionfix module in xposed. In retrospect I probably could skip (1) and do (2) only. Play store is still slightly wonky but it mostly works, and youtube definitely works 100%.

Damn, it's really a pain that SlimLP doesn't support xposed. I want xprivacy as well.

I just had to uninstall SlimLP and go to CM12.1 because of no support for Xposed from the developers. It's upsetting that with their (or ezio's) modifications that they should want to control something so big rather than let us decide for ourselves.
Because any reasoning such as "it's too big of a security risk" is absolutely ridiculous as it's our choice rather to expose ourselves and at the same time, most people installing modules and Xposed Framework at this point should know what we are installing to by now.

misticalx said:
I just had to uninstall SlimLP and go to CM12.1 because of no support for Xposed from the developers. It's upsetting that with their (or ezio's) modifications that they should want to control something so big rather than let us decide for ourselves.
Because any reasoning such as "it's too big of a security risk" is absolutely ridiculous as it's our choice rather to expose ourselves and at the same time, most people installing modules and Xposed Framework at this point should know what we are installing to by now.
Click to expand...
Click to collapse
The decision to decide for yourself is always in your hands. It is their rom to develop it how they want. If you do not like it, don't use it (as you have indiciated), but don't throw blame on a dev for not including support for something.

[ROM][6.0][jem] CM redux

I'd like to start this out by stating that these are personal builds. I'm not trying to compete with @transi1's developer prowess; on the contrary, I feel he's done a fantastic job with TWRP 3.0.0 and porting CM13 over to the kindles, and he's part of the reason why I'm motivated to do this side project. I'm releasing these for the purpose of bettering the Marshmallow experience on our aging kindles. I want to see if a different build configuration will help improve performance and reduce lag. I'm also wanting to learn my way through the nuances of ROM development, so I intend on starting small.
Click to expand...
Click to collapse
READ THIS BEFORE PROCEEDING ANY FURTHER
I don't intend to fray any circuits when I compile these builds. However, there's always a chance that something could really go wrong and inadvertently damage your device. In such an event, I (and the awesome XDA community) will try our best to help get you back up and running. However, please don't try to sue me if your device:
doesn't work as a result of flashing this;
initiates a nuclear meltdown, or;
doesn't permit your alarm clock to function normally.
By flashing, you automatically assume responsibility for any loss of data, functionality, or facial hair. Although a 10% tip would be nice if it started printing out money.
Click to expand...
Click to collapse
Downloads:
click the Downloads tab at the top of the page, or just click here. I'm also mirroring this on Google Drive for convenience. Builds will go up on AndroidFileHost. Use this link to find and download the latest releases.
OpenGapps: use ARM, 6.0, package of your choice (I'll create a custom .gapps-config later)
SuperSU: make sure to run echo SYSTEMLESS=false>>/data/.supersu in the TWRP terminal (advanced -> terminal) before flashing SuperSU, or else you'll have to perform a restore via fastboot (credit to @r3t3ch for finding the solution)
Features:
[*]Compiled with UBERTC 4.9
UBERTC toolchain causes the post-compiled builds with the 3.0.72+ kernel to break in a really embarrassing way, so this isn't used for now
based on CM13
more to come!
Known issues in post #2
Changelog in post #3
Feel free to respond to this thread to comment or report a bug. I'm open to all feedback.
Credit where credit is due
@Hashcode, because we wouldn't have CM on our kindles at all without him.
@BuQQzz for some mentoring & advice
@transi1 for porting CM13 and providing some useful fixes for build errors
XDA:DevDB Information
[jem] CM redux, ROM for the Amazon 7" Kindle Fire HD
Contributors
monster1612, Hashcode, transi1, BuQQzz
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2016-03-29
Last Updated 2016-08-07

Known issues
Bugs affecting all CM13-based ROMs on the kindle
Screen artifacts when playing video from Snapchat, Vine, etc.
Audio chops in and out often
Other bugs currently afflicting the other CM13 ROMs for this device
Camera currently doesn't work (although it is functional in the 3/20 RR build and earlier ROMs for jem)
Side note: This camera issue is prevalent w/ transi1's CM13 3/28 build, so it's not specific to this ROM only.
Play Store & Setup Wizard FCs
CM pushed a commit to fix the FCs, so now every ROM built from this point forward should be OK with flashing the latest gapps. (thanks to @r3t3ch for the find)

Changelog
08/07/2016
experimental backtracking to kernel 3.0.84+
July '16 AOSP patches (hoping 8/1/16's patchset made it in there too)
07/01/2016
doing yet another revert to the 3.0.72+ kernel, prior to transi's backporting of the newer one (3.0.101+) that broke the camera
June '16 AOSP patches, plus just about everything CM pushed up until 7/1/16
reverting from UBERTC toolchains to native CM/AOSP one
05/20/2016
defecting to BlissRoms-Devices GH for newest device config files
05/2016 security patches from AOSP, et al.
04/27/2016
refreshing CM sources & obtaining latest sources from transi1
04/09/2016
revert the 4/4 kernel reversion; back to 3.0.101(+)
carry in latest edits from transi1 to try to fix the camera
04/04/2016
revert to kernel 3.0.72+
first build that's been mostly summoned from my local jenkins install - now future builds should automatically upload to the AFH server
03/29/2016
initial build!

Roadmap
The following is a list of features I think will make it onto future builds. Feel free to contribute any suggestions, bug reports, etc.
Layers/RRO theming support
Custom boot animation (or at least one scaled to the kindle's screen size)
Possible removal of some unused stock apps (I'll package them into a separate flashable .zip in case)
Publication of a custom .gapps-config file for use with opengapps packages

I'm going to attempt to resolve the infamous camera bug by starting from a known good point in time and backtracking up through transi's kernel commits. This means a lot more frequent builds (sometimes unstable!) in the next couple days. I hope you guys are ready for more testing.

So far, it seems like transi's github commits to the common device repos may have fixed the camera (thus the reason why I didn't release another backtrack through the kernel commits). However, I don't know for sure, as I haven't tested out today's build yet. Any testers coming from earlier builds should not dirty flash this release; a clean wipe would be preferable. Feel free to let me know how things go.

Today's nightly has nothing special in terms of features, etc. However, I'm going to start implementing features as outlined in the roadmap. As usual, do let me know if there's something you'd like to see.

Some updates...
I still haven't gotten around to trying to bring RRO to this ROM. Apparently, CM's theme engine (which should have been compatible with RRO, but isn't) has conflicts with RRO/layers, and those have discouraged me from bringing RRO in (so far).
I think TWRP 3.0.2 needs to be built for both jem & tate. That release has some important fixes regarding encrypted backups, and even the TWRP people themselves recommend you stop using 3.0.1 if you use encrypted backups. I'm going to build for another ROM (hai there, OmniROM!) and compile against that source for TWRP. EDIT: transi said he'd wait till TWRP 3.0.3 is released to compile it, so we can stand to wait for it.

More updates...
It's been a while since the last build. Obviously, this one I just uploaded is about 2 weeks old at the time of writing. You may be wondering why I took so long to drop this build. It's complicated:
I was seriously curious as to how the camera managed to break down during transi's kernel backporting in mid-/late March. Such curiosity led me to attempt to revert the device repos to a stable state so I could build against 3.0.72+ instead of 3.0.101+.
My reversion efforts were successful (for the most part). I was able to get the process to succeed like normal, but when I tested out the builds (compiled against UBERTC), there was a breaking issue. The camera worked well enough (as I expected), but as soon as I tapped any textbox at all (even the password prompt for a WiFi network that required one), the screen would glitch out and force a reboot. I thought that maybe it was an error on CM's part, so I waited a day or so and compiled again, getting the same issue. At that point, I was baffled and decided to recompile with CM's native toolchain instead of UBERTC.
That build was on 7/1, and is the build that was uploaded an hour ago. I had it built then, but was waiting for a good time to test it out to see if that issue was resolved. Sure enough, when I tested it out tonight, it didn't occur.
Also, you may have noticed that I changed the ROM project name to CM redux. I did this to signify that this project won't be a full-on verbatim port of CM. (right now it is, but that's beside the point.) The name won't officially show up in the ROM itself until the next build, most likely.
Finally, some planned changes:
I'm going to continue with my backtracking scheme. I want to know exactly which commit is responsible for the software failure of the camera.
Obvious name change in the ROM, mentioned earlier.
Replacing CM's theme engine with RRO(?)
CM bloat cleanup. The ROM itself boots in 30 seconds, which is nice and all, but I'd like to try to trim it down a little more.

Good version,thanks. But it often wifi reconnect , can it fix?

wizard_mini said:
Good version,thanks. But it often wifi reconnect , can it fix?
Click to expand...
Click to collapse
I have that same issue with other 6.x ROMs, but I'm not sure what the cause is. Could you get a logcat as soon as that issue pops up again?

monster1612 said:
I have that same issue with other 6.x ROMs, but I'm not sure what the cause is. Could you get a logcat as soon as that issue pops up again?
Click to expand...
Click to collapse
It looks like WiFi 2g link no problems, 5g often reconnect. Let me test more time

Android system cost battery drain more than screen, is it normal?

wizard_mini said:
Android system cost battery drain more than screen, is it normal?
Click to expand...
Click to collapse
That depends on what apps you have installed, how heavily you use the device, and other factors. Try installing BetterBatteryStats as a system app, using it for a few days, and then report back some of the data it collects.

I flash the opengapps pico,when I install G-mail app , it said I must add a Google account,but I already setup my Google account, then I can't open gmail. Why?

wizard_mini said:
I flash the opengapps pico,when I install G-mail app , it said I must add a Google account,but I already setup my Google account, then I can't open gmail. Why?
Click to expand...
Click to collapse
I ran into this same problem using RessurectionRemix. I had to install an older version of Gmail, then update it from the Play Store.
Try this version:
http://forum.xda-developers.com/showthread.php?t=1181033
That's not the one I used, but I used a similar version from here somewhere.

sirp0p0 said:
I ran into this same problem using RessurectionRemix. I had to install an older version of Gmail, then update it from the Play Store.
Try this version:
http://forum.xda-developers.com/showthread.php?t=1181033
That's not the one I used, but I used a similar version from here somewhere.
Click to expand...
Click to collapse
It's a good solution,, I fix it, thanks

monster1612 said:
That depends on what apps you have installed, how heavily you use the device, and other factors. Try installing BetterBatteryStats as a system app, using it for a few days, and then report back some of the data it collects.
Click to expand...
Click to collapse
I use 4hours screen on and 7hours screen off cost 92% battery.

wizard_mini said:
I use 4hours screen on and 7hours screen off cost 92% battery.
Click to expand...
Click to collapse
I have a similar issue when I let my kindle sit overnight. I'm guessing it might be a commit that I reversed when I reverted to the 3.0.72+ source. I'll do a new build within the next few days with a few kernel updates thrown in.

monster1612 said:
I have a similar issue when I let my kindle sit overnight. I'm guessing it might be a commit that I reversed when I reverted to the 3.0.72+ source. I'll do a new build within the next few days with a few kernel updates thrown in.
Click to expand...
Click to collapse
Thanks. I am expecting it!

[T710/T715][UNOFFICIAL] LineageOS 14.1 20180303 (ABANDONED)

LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community
There are lineage os builds for only tab s2 8.0 2015 models.
this version is stable without any known issues.
Root is not included here. For root install magisk or su-addon ( https://mirrorbits.lineageos.org/su/addonsu-14.1-arm-signed.zip )
install:
flash with twrp
don't forget to flash gapps ( opengapps.org ) you need version for android 7.1 arm
download:
20180102
t710: https://drive.google.com/open?id=1tkzdpZdGXNouu0ig-NHGErWfmUP_CICP
t715: https://drive.google.com/open?id=1cLX-gWvUM9miJ3JTmcnWeXrNxI0F3II5
test build 20180303 for t710 is here: https://forum.xda-developers.com/showpost.php?p=75756582&postcount=147
sources:
https://github.com/bonuzzz/android_kernel_samsung_gts2
https://github.com/bonuzzz/android_device_samsung_gts2-common
https://github.com/bonuzzz/android_device_samsung_gts28wifi
https://github.com/bonuzzz/android_device_samsung_gts28ltexx
https://github.com/bonuzzz/android_vendor_samsung_gts2-common
https://github.com/bonuzzz/android_vendor_samsung_gts28wifi
https://github.com/bonuzzz/android_vendor_samsung_gts28ltexx

WOW! This is the first build of Lineage that works great on my tab! Didn't test fingerprint but autobrightness and camera is working great. Thank a lot. On T710 by the way.

See my signature for twrp 3.1.1-0 for both gts28wifi and gts28ltexx.
Please note that twrp 3.2.0-0 has just been released! I'll be working on bringing it up to the Galaxy Tab S2 2015 tablets as soon as possible
On a related matter, I own a 9.7 wifi variant and I build for it daily. Netflix doesn't work with the official gts2-common repo, but if you use mine it will. I kept a long since abandoned fix which has worked very well in my builds.

Do we need gapps, thank you sooooooo much for this!!!!
Sent from my SM-T710 using Tapatalk
---------- Post added at 01:04 AM ---------- Previous post was at 12:45 AM ----------
ripee said:
See my signature for twrp 3.1.1-0 for both gts28wifi and gts28ltexx.
Please note that twrp 3.2.0-0 has just been released! I'll be working on bringing it up to the Galaxy Tab S2 2015 tablets as soon as possible
On a related matter, I own a 9.7 wifi variant and I build for it daily. Netflix doesn't work with the official gts2-common repo, but if you use mine it will. I kept a long since abandoned fix which has worked very well in my builds.
Click to expand...
Click to collapse
You sir, are a good among men, which gapps do you recommend? And we can install su manually whithout messing up the fixes you got to make this bad boy run? Once again thank you.
Sent from my SM-T710 using Tapatalk

lahegry said:
Do we need gapps, thank you sooooooo much for this!!!!
Sent from my SM-T710 using Tapatalk
---------- Post added at 01:04 AM ---------- Previous post was at 12:45 AM ----------
You sir, are a good among men, which gapps do you recommend? And we can install su manually whithout messing up the fixes you got to make this bad boy run? Once again thank you.
Click to expand...
Click to collapse
I flash pico on my phone and tablet, but even stock or higher should work if the builds are from official sources. I also recommend Magisk if you wish to root. If these builds have su root, Magisk simply uninstalls it before installing itself.

bonuzzz, you did what most (self proclaimed) devs failed to achieve and deliver for the T710/715 in the last months! i just installed the ROM and tried it out the last few hours. finally got a clean and reliable android for my T710.
it's working really smooth, no issues so far. everything - including bluetooth and fingerprint - is working perfectly [edit: haven't tried it, since not needed: according to some posts in this thread stock camera doesn't seem to be working properly]. i am really anstonished and amazed by this great initial release, thanks a lot. i hope you keep on delivering such a good work.
many thanks and best regards from germany

For me on my T710 the microphone did not work. So it isn't in perfect working order yet and the battery drains quite fast, but it's miles better than the previously shared builds here on XDA, and most certainly usable.
I also had issues with certain apps not working properly, so I ended up going back to stock for now. (more precisely: the Antutu 3D part and the Focus gallery application).

TWRP 3.2.0-0 for gts28wifi and gts28ltexx!
twrp-3.2.0-0-gts28wifi.img
twrp-3.2.0-0-gts28wifi.tar
twrp-3.2.0-0-gts28ltexx.img
twrp-3.2.0-0-gts28ltexx.tar

@ripee,
create your own topic please. dont spam here. thank you

bonuzzz said:
@ripee,
create your own topic please. dont spam here. thank you
Click to expand...
Click to collapse
Sorry if twrp is spam. Best of luck fiddling around with lineage recovery. For everyone's sake, I hope that Netflix works on your builds.

Thanks a lot for this build. An important progress for the T710/T715.
And also thx for the current TWRP link @ripee, missed that one.

Camera app force closed. Dont save any pictures

If you use a third party app like open camera, it actually works really well.
Either way, the microphone doesn't work at all, as in all roms for this device, and sadly it is a deal breaker for me since I use my tablet for video calls all the time.

azenyr said:
If you use a third party app like open camera, it actually works really well.
Either way, the microphone doesn't work at all, as in all roms for this device, and sadly it is a deal breaker for me since I use my tablet for video calls all the time.
Click to expand...
Click to collapse
open camera same problem.
My twrp recovery is old. I update this and I will try again

Having used this ROM for the last few days on a T710, I experienced a very stable system. UI was always smooth, no serious issues so far. :good:
However, I observed some strange behaviours/minor issues:
Fingerprint unlock isn't always working reliably. Sometimes, when trying to unlock the lockscreen, the finger on the fingerprint sensor doesn't seem to be detected and the PIN has to be entered manually.
LiveDisplay is not always active when the device comes from sleep and has to be unlocked. Upon the next sleep/active via short press on the power button iteration, the LiveDisplay mostly works as expected.
Once, presumably a wakelock drained the battery throughout the day until it was empty and the device turned itself off. I don't know why this happened and can't reproduce it.
Altogether a very successful start for this ROM, I will keep it on my device and hope the dev keeps on working on it to further improve it or even update to Lineage 15.x...
Thanks, @bonuzzz!

Sorry for intruding again, but we are about to get official TWRP support! I've been asked to test the "release candidate" images. As I don't have either a gts28wifi or gts28ltexx, I'd like to post the links here and ask for feedback. I'll create a separate TWRP thread once I confirm that these twrp builds work. I apologize again:
http://build.twrp.me/twrp-3.2.1-0-gts28wifi.img
http://build.twrp.me/twrp-3.2.1-0-gts28wifi.img.tar
http://build.twrp.me/twrp-3.2.1-0-gts28ltexx.img
http://build.twrp.me/twrp-3.2.1-0-gts28ltexx.img.tar

ripee said:
Sorry for intruding again, but we are about to get official TWRP support! I've been asked to test the "release candidate" images. As I don't have either a gts28wifi or gts28ltexx, I'd like to post the links here and ask for feedback. I'll create a separate TWRP thread once I confirm that these twrp builds work. I apologize again:
http://build.twrp.me/twrp-3.2.1-0-gts28wifi.img
http://build.twrp.me/twrp-3.2.1-0-gts28wifi.img.tar
http://build.twrp.me/twrp-3.2.1-0-gts28ltexx.img
http://build.twrp.me/twrp-3.2.1-0-gts28ltexx.img.tar
Click to expand...
Click to collapse
Hi! I tested gts28wifi for my SM-T700 but touch sensor is wrong. The interface is unusable for now. Best of luck. But you should start your own thread...

powerade001 said:
Hi! I tested gts28wifi for my SM-T700 but touch sensor is wrong. The interface is unusable for now. Best of luck. But you should start your own thread...
Click to expand...
Click to collapse
ripee said:
Sorry for intruding again, but we are about to get official TWRP support! I've been asked to test the "release candidate" images. As I don't have either a gts28wifi or gts28ltexx, I'd like to post the links here and ask for feedback. I'll create a separate TWRP thread once I confirm that these twrp builds work. I apologize again:
What would be the point of a dedicated thread if it doesn't work? Anyway, thanks for your feedback.
Click to expand...
Click to collapse

ripee said:
ripee said:
Sorry for intruding again, but we are about to get official TWRP support! I've been asked to test the "release candidate" images. As I don't have either a gts28wifi or gts28ltexx, I'd like to post the links here and ask for feedback. I'll create a separate TWRP thread once I confirm that these twrp builds work. I apologize again:
What would be the point of a dedicated thread if it doesn't work? Anyway, thanks for your feedback.
Click to expand...
Click to collapse
The point is,..
If your building it, wouldn't you want it all together so you could track it easier? Now you'll need to read all the threads that you've posted this into to find the results.
I know we all appreciate you doing this. But please make your own thread for it so we can all see what's going on. Without having to read through the 4+ threads this is in.
Keep it up. It's nice to see our tabs still getting some love. Thank you. ?
Click to expand...
Click to collapse

engine95 said:
ripee said:
The point is,..
If your building it, wouldn't you want it all together so you could track it easier? Now you'll need to read all the threads that you've posted this into to find the results.
I know we all appreciate you doing this. But please make your own thread for it so we can all see what's going on. Without having to read through the 4+ threads this is in.
Keep it up. It's nice to see our tabs still getting some love. Thank you.
Click to expand...
Click to collapse
Is it possible to make android oreo??
What are the basic requirements for it??
Click to expand...
Click to collapse

[ROM] [TEST] Miui 10 for Oneplus 6t

I am not responsible for anything that happens to your device.
This is a port of MIUI 10 for the op6/6t
Flash at your own risk and make sure to check what's working. Logcats would be appreciated!
Instructions:
1: Flash OxygenOS 9.0.7 twice, this is very important
2: Extract the download somewhere
3: Run the OnePlus 6t flasher (make sure phone is still in fastboot/bootloader)
4: Reboot to TWRP (fastboot boot it if it dissapeared, if you install TWRP you must install Magisk)
5: Flash or adb sideload NFC fix that is included in the download
6: Reboot and install V4A Magisk module and enable headset and speaker, this fixes audio
7: Enjoy!
Download (v3):
MOD EDIT: LINK REMOVED
What works:
Everything except stuff in what doesn't work
What doesn't work:
NFC
Flashlight toggle (3rd party apps work)
MIUI camera (3rd party apps work)
Fingerprint (top priority - @nima0003 - me)
Audio fix #2:
Credits to @dougie313
Flash viper4android module
Grab root browser
Go to vendor\lib\soundfx folder and rename or delete all files in folder
Source code: https://github.com/OnePlusOSS/android_kernel_oneplus_sdm845
Credits: @nima0003 me @ProtoDeVNan0 for the current build
Dylan Neve
Omar

What is it based on? And will you keep working on it?

dennisbednarz said:
What is it based on? And will you keep working on it?
Click to expand...
Click to collapse
Yeah, it'll be hard to do so because of school but I will. It's based off of mi 8 Dev miui (same soc)

nima0003 said:
Yeah, it'll be hard to do so because of school but I will. It's based off of mi 8 Dev miui (same soc)
Click to expand...
Click to collapse
Ah, so it doesn't use OxygenOS as a base?
I'm personally very interested in a MIUI ROM for the OP6T and seeing that someone is willing to work on it makes me pretty happy.
What about features like the mute switch and in-display fingerprint sensor?

dennisbednarz said:
Ah, so it doesn't use OxygenOS as a base?
I'm personally very interested in a MIUI ROM for the OP6T and seeing that someone is willing to work on it makes me pretty happy.
What about features like the mute switch and in-display fingerprint sensor?
Click to expand...
Click to collapse
It's uses AOSP as the base rom, I'm pretty sure alert slider doesn't work yet, hell I'm not sure it even boots yet. But if someone is able to test and it boots stable I'll get to work on those type of things.

nima0003 said:
It's uses AOSP as the base rom, I'm pretty sure alert slider doesn't work yet, hell I'm not sure it even boots yet. But if someone is able to test and it boots stable I'll get to work on those type of things.
Click to expand...
Click to collapse
My 6T is my daily driver. I may back everything up later and test it out.
Wouldn't it be easier to use OOS as the base for better performance, easier porting of features and so on? Would also make most kernels compatible.

Am I correct in assuming this supports treble? If so, I'm sure it'll make it easier to focus on 6/6t features being added rather than worrying about troubleshooting compatibility ??

champ784 said:
Am I correct in assuming this supports treble? If so, I'm sure it'll make it easier to focus on 6/6t features being added rather than worrying about troubleshooting compatibility ??
Click to expand...
Click to collapse
Yes it is treble based, but I didn't even think of the basic bootable gsi. I'll look more into this, thanks for the idea.

dennisbednarz said:
My 6T is my daily driver. I may back everything up later and test it out.
Wouldn't it be easier to use OOS as the base for better performance, easier portion of features and so on? Would also make most kernels compatible.
Click to expand...
Click to collapse
Yes that's a great idea actually, I was just worried some framework stuff would get in the way but maybe not.

nima0003 said:
Yes it is treble based, but I didn't even think of the basic bootable gsi. I'll look more into this, thanks for the idea.
Click to expand...
Click to collapse
Sure thing! We finally got treble support via lineage os for the Moto Z2 Force, which really helped keeping the device alive. Also makes flashing a TON easier, so maybe it's a good place to start

I'm downloading to test, report back in a bit.

champ784 said:
Sure thing! We finally got treble support via lineage os for the Moto Z2 Force, which really helped keeping the device alive. Also makes flashing a TON easier, so maybe it's a good place to start
Click to expand...
Click to collapse
My dad traded his z2 force for a 6t. Rom support was good but everything was messed up, camera didn't focus, no safteynet...

nima0003 said:
My dad traded his z2 force for a 6t. Rom support was good but everything was messed up, camera didn't focus, no safteynet...
Click to expand...
Click to collapse
There are workarounds, but I think it being one of the earlier devices having A/B partitions and basically being abandoned by Moto made it a task. I still have mine, but I wonder if there's something wrong with my device because I can't really flash anything beside rooted stock Rom, which leads me to think it's just a tedious device and I'd rather focus on my new 6t which is FAR superior in every way!

champ784 said:
There are workarounds, but I think it being one of the earlier devices having A/B partitions and basically being abandoned by Moto made it a task. I still have mine, but I wonder if there's something wrong with my device because I can't really flash anything beside rooted stock Rom, which leads me to think it's just a tedious device and I'd rather focus on my new 6t which is FAR superior in every way!
Click to expand...
Click to collapse
Yeah same thing happened to my Xperia xc, I could only flash stock rom, not even rooted.

Flashing failed, error: invalid zip file format.

Dark Nightmare said:
Flashing failed, error: invalid zip file format.
Click to expand...
Click to collapse
Great, thank you, working on it.

You would be my hero
It is great to see other types of roms, instead of only los type roms. Great to switch between them over time.

nima0003 said:
Yes that's a great idea actually, I was just worried some framework stuff would get in the way but maybe not.
Click to expand...
Click to collapse
Hopefully not. Lot's of people prefer stock-based ROMs specifically for the reason that they're usually more stable, almost always better performant and always better for battery (with the exception of TouchWiz). And the whole feature thing is also useful.
Lot's of people base the ROMs of Lineage as it usually has hardware specific support, but as we don't have official lineage yet and it would still be a lesser experience than a stock ROM, I strongly advocate for the OOS base.
Wish I could help out but I'm not a developer. If you need something designed, contact someone at Xiaomi, OnePlus or Google, or if you need some piece of code some person is sitting on, let me know (on Twitter or Telegram @dennisbednarz as i don't use the forum DM system).

So basically you just ported the OS and want testers? As of now, OP6T is just 3 weeks old and hardly would anyone dare to try something that says 'I highly doubt it'll work' in the OP.

Can Not installed
Sent from my ONEPLUS A6013 using XDA-Developers Legacy app

Lineage 17.1 and microg

Hey folks,
I'm trying to get microg on Lineage 17.1 for my Moto G7 plus. I know about the current situation, that motog is not working perfectly with Android 10 for now due to some problems with the Unified nlp. However, I would like to install it, but there are multiple problems:
- microg for lineage is not available yet for lake
- I would need to patch lineage to support signature spoofing for installing it manually. I tested nanodroid patcher which didn't work (I guess because I first have to deodex lineage, but am unsure about that)
- There is a new microg fork called minmicrog
Could you give me some recommendations on a preferred setup? I also thought about building micro for lineage with the docker image but am not sure if this will work out due to limited hardware.
Thanks a lot!

I just got this phone and the development on it i believe is still getting in gear.... I know for sure that you can get microg setup on a custom rom using the nandroid setup...as far as this goes Im gonna try it right now....Ive got every custom rom available for us and most are google pixel based so that just defeats the whole purpose... so Ill try and learn as I go....I believe that Havoc and crdroid have signature spoofing options in there respected settings menus....i will test and report back......Also you can do this with a stock rooted rom with magisk and twrp......
NanoDroid wiki....great instructions
this is what Im gonna follow if you want to try yourself and report back

cobra202 said:
Hey folks,
I'm trying to get microg on Lineage 17.1 for my Moto G7 plus. I know about the current situation, that motog is not working perfectly with Android 10 for now due to some problems with the Unified nlp. However, I would like to install it, but there are multiple problems:
- microg for lineage is not available yet for lake
- I would need to patch lineage to support signature spoofing for installing it manually. I tested nanodroid patcher which didn't work (I guess because I first have to deodex lineage, but am unsure about that)
- There is a new microg fork called minmicrog
Could you give me some recommendations on a preferred setup? I also thought about building micro for lineage with the docker image but am not sure if this will work out due to limited hardware.
Thanks a lot!
Click to expand...
Click to collapse
I got full Microg status with unifiednlp ....and man there is so much bad, old and wrong info.....I pulled it off with a vanilla Arm64 ab gsi which I love it is the best ROM ive tried.......also I found a new way to patch the signature spoof that I wasnt aware of using smaili patcher....and bare minimal installer just released.....seems since micro g and lineage got together more people are wanting to try..... I am so tired,,,,,,it seriously ate me up but I beat it.....if u need links or instructions private messege me .....I will create a forum post probably soon

KtownJeff said:
I got full Microg status with unifiednlp ....and man there is so much bad, old and wrong info.....I pulled it off with a vanilla Arm64 ab gsi which I love it is the best ROM ive tried.......also I found a new way to patch the signature spoof that I wasnt aware of using smaili patcher....and bare minimal installer just released.....seems since micro g and lineage got together more people are wanting to try..... I am so tired,,,,,,it seriously ate me up but I beat it.....if u need links or instructions private messege me .....I will create a forum post probably soon
Click to expand...
Click to collapse
Thanks, sounds interesting, will also give it a try! Finally managed to get lineage 17.1 working with microg building it myself, check github.com/lineageos4microg/docker-lineage-cicd/pull/70. So built went through, could flash it and seems to work like a charm

cobra202 said:
Thanks, sounds interesting, will also give it a try! Finally managed to get lineage 17.1 working with microg building it myself, check github.com/lineageos4microg/docker-lineage-cicd/pull/70. So built went through, could flash it and seems to work like a charm
Click to expand...
Click to collapse
you should try this FLOSS GSI ready made daily driver without any Google.... if you want root flash magisk after you set it up....
https://forum.xda-developers.com/pr...velopment/aosp-10-0-quack-phh-treble-t3992559[/QUOTE]
there is three versions FLOSS, Vanilla, and GAPPS..... make sure you choose ARM64 AB