Database Develop

Cyanogenmod 13??????

Will cyanogenmod 13 come to the kindle fire hd 7 (Tate)?

Yep, @BuQQzz and I (mostly him, haha) are working on porting CM13 to this device, as well as the 8.9" (jem). I'm not exactly sure when a usable build will be uploaded, but it should be in the not-so-distant future.

I'm running 12.1 on mine and even though the rom is very lean the Kindle is always running slow. I have 2 questions concerning this. One, based on what you're seeing so far during development, is the rom running at a better speed?
Two, what steps can I take to make sure I am running the best I can for the best results?
The system was wiped completely. I did a super clean install, I've made a backup and moved it to my desktop (in case I need to push it), and I usually only do an update about once every two weeks. Mainly due to the fact that I have to jump through all the hoops of reinstalling Google Play Services, Google games, and the SuperSU beta.
If there are other things you think may help please give suggestions and advice. I can add external storage, however at the moment I do not have an SD card in the slot. To me since storage and RAM are two different things I am thinking it would make little difference to add external storage since I have very few apps downloaded on it.

Jaybone073 said:
I'm running 12.1 on mine and even though the rom is very lean the Kindle is always running slow. I have 2 questions concerning this. One, based on what you're seeing so far during development, is the rom running at a better speed?
Two, what steps can I take to make sure I am running the best I can for the best results?
The system was wiped completely. I did a super clean install, I've made a backup and moved it to my desktop (in case I need to push it), and I usually only do an update about once every two weeks. Mainly due to the fact that I have to jump through all the hoops of reinstalling Google Play Services, Google games, and the SuperSU beta.
If there are other things you think may help please give suggestions and advice. I can add external storage, however at the moment I do not have an SD card in the slot. To me since storage and RAM are two different things I am thinking it would make little difference to add external storage since I have very few apps downloaded on it.
Click to expand...
Click to collapse
1) The ROM currently doesn't even boot up at this point. It's an issue with SELinux that we're working to resolve.
2) I would suggest that you avoid having too many apps on the device - doing so tends to make app optimization take longer (which usually occurs after an OTA or a manual cache wipe). Also, try not to have too many xposed modules or other android mods on your device - if modules or frameworks conflict with each other or the base system, system stability and speed can be negatively impacted. As for the issues with having to reflash gapps, xposed, etc. after an OTA, I use CM Downloader (which is available on the Play Store) to automatically handle flashing other zips after the CM base ROM.
You're right - storage and RAM are two different things. Unless you're low on storage and/or need to share files between multiple devices, I wouldn't see a need for an SD card. Also, I'm fairly certain that the 2012 HD 7" (tate) doesn't have an SD card slot (are you using a 5th generation device?). This discussion is for the 2012 HD 7" models, not for other (or later) models; flashing a ROM meant for another device can and most likely will brick your kindle.

monster1612 said:
1) The ROM currently doesn't even boot up at this point. It's an issue with SELinux that we're working to resolve.
2) I would suggest that you avoid having too many apps on the device - doing so tends to make app optimization take longer (which usually occurs after an OTA or a manual cache wipe). Also, try not to have too many xposed modules or other android mods on your device - if modules or frameworks conflict with each other or the base system, system stability and speed can be negatively impacted. As for the issues with having to reflash gapps, xposed, etc. after an OTA, I use CM Downloader (which is available on the Play Store) to automatically handle flashing other zips after the CM base ROM.
You're right - storage and RAM are two different things. Unless you're low on storage and/or need to share files between multiple devices, I wouldn't see a need for an SD card. Also, I'm fairly certain that the 2012 HD 7" (tate) doesn't have an SD card slot (are you using a 5th generation device?). This discussion is for the 2012 HD 7" models, not for other (or later) models; flashing a ROM meant for another device can and most likely will brick your kindle.
Click to expand...
Click to collapse
I stand corrected. There is no external slot. I was mistaking the back logo panel as a possible external storage cover. My son has had the device for quite some time and he asked dad (me) to give it the "works". The device was running atrocious and much slower than it does now. I've had it for about 2 months and after installing the 2nd bootloader, rooting, twrp recovery..... You get the idea, I had it very stable and clean. It's been running quite well on 12.1 and I am pleased to see development still happening for such an older device.
As far as apps go, I have only installed what he likes. A few games (about 4) and a couple of social ones like Instagram and facebook for him. The real slowdown was actually with Facebook continually not updating and having errors. A recent reboot has fixed that. It also appears that the occasional reboot is actually helping the rom settle in.
I had previously tried the CyanDelta Updater on the play store and it didn't work well. I will now give CM Downloader a try to see of that keeps me from having to reflash the GApps and other apk that seem to force close that I had previously mentioned.
Thanks for the quick response and advice.

Jaybone073 said:
I stand corrected. There is no external slot. I was mistaking the back logo panel as a possible external storage cover. My son has had the device for quite some time and he asked dad (me) to give it the "works". The device was running atrocious and much slower than it does now. I've had it for about 2 months and after installing the 2nd bootloader, rooting, twrp recovery..... You get the idea, I had it very stable and clean. It's been running quite well on 12.1 and I am pleased to see development still happening for such an older device.
As far as apps go, I have only installed what he likes. A few games (about 4) and a couple of social ones like Instagram and facebook for him. The real slowdown was actually with Facebook continually not updating and having errors. A recent reboot has fixed that. It also appears that the occasional reboot is actually helping the rom settle in.
I had previously tried the CyanDelta Updater on the play store and it didn't work well. I will now give CM Downloader a try to see of that keeps me from having to reflash the GApps and other apk that seem to force close that I had previously mentioned.
Thanks for the quick response and advice.
Click to expand...
Click to collapse
If you go into the CM Downloader app settings, you should be able to add in the zips (maximum of 6) you want flashed after a ROM update. Once that's complete, all you need to do is download an update and initialize the install process from within the app, and it'll handle flashing the zips. From personal experience on CM nightlies for jem (the 8.9" version), I tend to see stability break down after about 24 hours of device uptime without a reboot, so reboots do help significantly.

Any progress so far?

Pix12 said:
Any progress so far?
Click to expand...
Click to collapse
Currently, the generated zips take longer than cm12.1 to flash (but they still flash successfully). As for a functional ROM, that hasn't happened yet - it refuses to boot after about 5 seconds. last_kmsg says it's an SELinux issue.

Fix dec 2016/jan 2017: Snapchat on rooted android device running xposed.

POST IS UPDATED REGULARLY.
LINK 1 - Parallel Space: https://play.google.com/store/apps/details?id=com.lbe.parallel.intl&hl=en[/URL][/URL]
LINK 2 - Parallel Space 64-Bit Support: https://play.google.com/store/apps/details?id=com.lbe.parallel.intl.arm64&hl=en[/URL][/URL]
Salutations. (That means 'Hello').
NOTE: For those who are interested, I will include background information about how I came to the solution. All that other jazz too. First and foremost however; the fix!
SOLUTION:
Right at the top of the post, you will find two links. This being a new account and all (don't ask), until I create 10 posts I cannot include any outside links. So once I've done so, I will update the post.
STEP **: So at the top of the post, there are clearly two links. 64-Bit Android devices are becoming increasingly common. This architecture may pose a few problems. give the application framework. Should you own a 64-Bit device, I recommend installing this application too (LINK 2). This will theoretically prevent any obstacles.
Pre-requisite(s): Make sure you have the 'Snapchat' application installed. It is recommended to have installed the latest update from the Google Play Store.
STEP ONE: Download the application appended to LINK 1. This is called Parallel Space. You might recognize the name (its creators are the same who allow you to seamlessly virtualize Windows OS on Mac OS).
STEP TWO: Launch the application.
STEP THREE: You should be prompted with a grid-like interface. Here you will be greeted with a range of familiar icons. In the top right corner of each icon, you will notice a blue check-mark. Make sure that there is one next to the 'Snapchat' icon. This will ensure that the app is 'cloned'.
STEP FOUR: In the 'Parallel Space' app, tap on the 'Snapchat' icon. This will launch the application.
STEP FIVE: From here it is pretty self-explanatory. You are greeted by the standard 'Snapchat' interface. Tap on 'Log In'. Then proceed to do so.
STEP SIX: 'Snapchat' should be functioning as normal.
STEP SEVEN (BONUS): During testing, this worked on and off. --
Remain logged-in to the 'cloned' 'Snapchat' application within the 'Parallel Space' application.
Then proceed to launch the stock 'Snapchat' application.
Next attempt to 'Log-In'.
Should this operation be successful, you are then free to uninstall 'Parallel Space' and any related assets from your device.
HOWEVER, I personally do not recommend this. When logging out or updating the 'Snapchat' application, errors may be re-encountered.
Instead, I recommend that if possible, do use the stock application, but leave 'Parallel Space' installed. Using the stock app will improve efficiency and reduce the load on system resources. But keeping the 'Parallel Space' application on the device, well; you get the point.
Enjoy the fix! If it does not work, please let me know [Device Name and Model No.]. I've tested on various devices, succeeded every-time. Do keep in mind that this is a loop-hole, so may be patched in future or not work at all for some devices.
Background (Because I know someone will ask): The idea came to mind while using a LG G5 as a daily driver. I had tested every custom ROM available for the device. The problem was that with custom ROM's, there was always an issue, Malfunctioning sensors, camera's not working persistently, etc , etc.
The G5's stock ROM left me wanting more. The overbearing interface made it a living hell. Plus, the device just being rooted (NO XPOSED) meant that 'Snapchat' did not work. I looked for fixes for a time, but could not find any.
Development of ROM's for the device is on-going, and I am an active member. But I just couldn't handle not being able to use the camera (one of the device's best features) and no accelerator, screen-rotation, etc. So I went back to stock again. Do keep in mind that I was alternating/dual-booting between custom and stock ROM's just because of the camera; mainly.
This most recent time. instead of flashing stock MM, I flashed stock N for the G5. For 850, it has been officially released in some countries, and a manual flash via TWRP was a peice of cake.
This update is a lot better. I am running Nova Launcher again. So it makes it look a little better. Themes have also been improved. I am using an in-built dark one which makes the device look a lot better aesthetically. Additionally, I'm rocking a white carbon-fibre skin on the exterior; improving grip and overall security. The only issue was again, no 'Snapchat'.
After a few days, I had the idea to attempt this. I tested my theory and it worked! That's it.
Please do keep in mind that I will update this post as often as possible.
P.S This was tested just after updating to the latest version of 'Snapchat' which was a significant update. It included Shazam, Groups, etc. So you know, pretty cool that it worked.

Did not work on Google Nexus 5 running Android 7.1.1. Still gives error message saying that I can't connect to the server.

Same here, not working on freshly reinstalled and rooted 7.1.1 Nexus 5x. No Xposed, no nothing. I get the infuriating "temporarily failed" message in both cloned and regular modes.

It didn't worked. S7 edge exynos (6.0.1)

Holyphe said:
It didn't worked. S7 edge exynos (6.0.1)
Click to expand...
Click to collapse
I'm pretty sure if you get Xposed framework, there's a module that allows you to hide root from apps. Problem is that there is no Xposed framework for Android 7 yet. Hope this helps.

hot_potato said:
I'm pretty sure if you get Xposed framework, there's a module that allows you to hide root from apps. Problem is that there is no Xposed framework for Android 7 yet. Hope this helps.
Click to expand...
Click to collapse
Whats the name of it?

Holyphe said:
Whats the name of it?
Click to expand...
Click to collapse
I personally tried the module on cm13 but it doesnt work for me. I think that somehow snapchat knows when you use xposed too.
The thing is that on aosp roms with root already build in sometimes snapchat do not catch it but if you have xposed, no way you can get in. For that freaky snapchat app here is what i did: install any rom, if if had root build in i then install su uninstaller zip with twrp then log in into snapchat and after that, rooting with super su zip again. The catch is that once you log out of the app and attempt to log in again, you cant get in and you have to repeat the proccess. It's annoying as hell!!! They need to disable the security check, if people want to cheat che system somehow they will, so whats the point. Also there are much more tweaks for jailbroken iphones and they have no problem with it .
Sorry for the rant here buqt im super frustrated.

AndroidFL said:
I personally tried the module on cm13 but it doesnt work for me. I think that somehow snapchat knows when you use xposed too.
The thing is that on aosp roms with root already build in sometimes snapchat do not catch it but if you have xposed, no way you can get in. For that freaky snapchat app here is what i did: install any rom, if if had root build in i then install su uninstaller zip with twrp then log in into snapchat and after that, rooting with super su zip again. The catch is that once you log out of the app and attempt to log in again, you cant get in and you have to repeat the proccess. It's annoying as hell!!! They need to disable the security check, if people want to cheat che system somehow they will, so whats the point. Also there are much more tweaks for jailbroken iphones and they have no problem with it .
Sorry for the rant here buqt im super frustrated.
Click to expand...
Click to collapse
That's the only solution I've seen working so far. unroot and reroot. Root cloak doesn't work, parallel doesn't work. I should've logged in before rooting and I hate to do it again.

Any work arounds yet? I've seen ppl do it using titanium backup but I'm not sure if that works. Can anybody help?

Samsung s5 G900v Not working
I have been searching and searching and still haven't found a way to sign into snapcat. It took me about 6 months to be able to find out how to root my phone.

Dukeboyty said:
I have been searching and searching and still haven't found a way to sign into snapcat. It took me about 6 months to be able to find out how to root my phone.
Click to expand...
Click to collapse
Well todays your lucky day.
Step one turn off xposed.
Step two reboot
Step three sign into snapchat
Step four turn xposed back on
Step five reboot
You should be able to snap now.

Okay. I will try this on monday and will let youknow how it goes. Right now I decided to unroot to use snapchat, so I didn't loose my streaks. Thanks in advane will let you know how it goes.

immorality said:
Well todays your lucky day.
Step one turn off xposed.
Step two reboot
Step three sign into snapchat
Step four turn xposed back on
Step five reboot
You should be able to snap now.
Click to expand...
Click to collapse
Now that i think of it, when i uninstalled xposed it didn't work still. but after i "fully unrooted" through Super su and tried to sign in it worked. so it has to do with root or maybe both but the xposed didnt work for me. Thanks even though it didn't/wouldn't have worked for me!

Dukeboyty said:
Now that i think of it, when i uninstalled xposed it didn't work still. but after i "fully unrooted" through Super su and tried to sign in it worked. so it has to do with root or maybe both but the xposed didnt work for me. Thanks even though it didn't/wouldn't have worked for me!
Click to expand...
Click to collapse
Snapchat detects xposed framework.
Though at a time they did do root they since moved to blocking xposed due to the security concerns with money and also privacy of the user.
Though with certain phones and ect that could be the case I am using a s5 and have no issues.

just install magisk and systemless xposed and turn on magisk hide in magisk manager now snapchat won't detect root
then when u wanna log in just turn off xposed in xposed installer and reboot "it won't take time booting optimizing app when reactivated now" so reboot is easy
and u can have multiple accounts by backing up snapchat with titanium backup and don't ever log out just wibe its data and when u want to relog just restore the backup
and if u want to have multiple accounts access just patch the titanium backup with luckypatcher and have multiple backups (accounts)

ahmedsasker said:
just install magisk and systemless xposed and turn on magisk hide in magisk manager now snapchat won't detect root
then when u wanna log in just turn off xposed in xposed installer and reboot "it won't take time booting optimizing app when reactivated now" so reboot is easy
and u can have multiple accounts by backing up snapchat with titanium backup and don't ever log out just wibe its data and when u want to relog just restore the backup
and if u want to have multiple accounts access just patch the titanium backup with luckypatcher and have multiple backups (accounts)
Click to expand...
Click to collapse
Can u make a instructions how to do it step by step? How can i turn off xposed in xposed installer? It also works when SuperSu is installed or i have to unistall it first?

Fnn.09 said:
Can u make a instructions how to do it step by step? How can i turn off xposed in xposed installer? It also works when SuperSu is installed or i have to unistall it first?
Click to expand...
Click to collapse
make a nandroid backup if u want
1- full unroot by opening supersu and going to settings and press Full unroot and wait till it finishes and restart
2- download xposed uninstaller if u have xposed framework installed and flash it
3- install magisk manager from playstore
4- download and flash last magisk which is (12v) now from : https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
5- flash magisk v12.0 which you downloaded now your phone will have systemless root
6- go into magisk manager app and go to settings and toggle "Magisk Hide" (ON) and restart now your root is hidden
7- remove your current xposed app and install this one : https://forum.xda-developers.com/xposed/material-design-xposed-installer-t3137758
8- flash systemless xposed : https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
9- reboot and go to the xposed installer app and toggle the xposed off or on as you want when u restart it won't take time optimizing apps like before so fast now
your root is hidden now but xposed is not but you can disable it and enable it easily

Instead of using Parallel Space (which I believe to be insecure) use Island to clone your apps. It's a little more advanced to setup, but it's a lot more secure. It works for rooted and non-rooted devices. On the 1st page of the thread, it explains how Parallel Space and others repack the apk file locally, which is dangerous. https://forum.xda-developers.com/android/apps-games/closed-beta-test-incoming-companion-app-t3366295
Island never repack apk file locally, which is inherently insecure for users, since all your app data (including password input) are technically in the hand of MoboClean. (The same applies to other similar tools, e.g. LBE Parallel Space)
Instead, Island takes advantage of the underlying mechanism used by "Android for Work". This ensures that all your apps run natively in Android system and their data are securely stored in internal location of Android which is never accessible by Island. It has the same level of security as "Android for Work".
Click to expand...
Click to collapse
Be sure to read the disclaimer!!! The app is still only available in closed beta at the time of writing this, and could possibly cause you're device to bootloop or even possibly brick it, but root, xposed, or other modifications {in my opinion) has a higher chance of bootloops or bricking your device.
You follow the same steps in island to clone snapchat as you would in Parallel Space to login to snapchat. It might be possible to use the play store inside island to download snapchat inside island and login that way. I can't remember exactly how it works. I believe that island is a good way to test apps in a "sandbox environment" to keep the data excluded, safe and secure from the regular apps that you have installed outside of island.
I use Magisk now which bypasses SafetyNet which is what snapchat uses to "block access" to modified/rooted devices.
Probably the easiest method is to download Casper which is an alternative snapchat client that allows you to save snaps, and many other features that the official snapchat client can't do. Find Casper at www.casper.io
FYI Netflix has started to change how they do things as well by hiding the app's play store page from devices that have been modified or rooted, but it's still possible to simply sideload Netflix for now.

[TESTING] libhoudini for Android N ROMs (7.1.0a_y.49344 / 8.0.0_y.49374)

NOTE: This is only for Nougat (7.1) custom ROMs (such as Lineage 14.1 based)!
Make sure you do a proper nandroid backup before flashing!
I made a flashable zip for updating the libhoudini stuffs for Nougat (7.1) ROMs to 7.1.0a_y.49344. Not sure if this has been posted elsewhere before, though.
Before flashing, check your current libhoudini version by typing "houdini --version" either from adb shell or from terminal emulator. (UPDATE: Use the built-in Terminal as it doesn't work in Termux)
You should only try to flash this if your houdini version is below 7.1.0a_y.49344. Current custom ROMs usually have a houdini version of 7.1.0_y.48901 (DotOS 1.2 for example).
Flashable zip (It's about 34MB in size) (Dropbox link here)
The original source is from here, apparently taken from Nexus Player (fugu).
After flashing, "houdini --version" should report something like this:
Code:
[14902]
[14902] Houdini version: 7.1.0a_y.49344
[14902]
TESTING NEEDED: I'm not sure what this version of houdini might fix or break, so try this at your own risk. If you're currently not having problems with apps then there's no need to flash this. Compared with existing device files (7.1.0_y.48901, in /system/lib/arm/), several library files are changed, plus an additional "libgate.so" which I could identify it as being an ARM library file (so it'll also be placed in /system/lib/arm, although I'm not sure where it might be used).
EXPERIMENTAL (UNTESTED!): Here's another version in case someone might be interested. This build is 8.0.0_y.49374, and the version number literally means it's to be used for Oreo, so I'm not sure if it'll work on a 7.x ROM. The original source of this version is from Android-x86.
Flashable zip (Dropbox link here)
If the zip works, it should report the following version:
Code:
[19729]
[19729] Houdini version: 8.0.0_y.49374
[19729]

What is the use for this ?

PedroCaseiro said:
What is the use for this ?
Click to expand...
Click to collapse
It's just to put updated libhoudini libraries into the device, in hope that those updated stuffs might help with fixing some native libhoudini crashes on certain problematic ARM-only apps.
I had some ARM-only apps that always FC with native crashes (SIGSEGV) from libhoudini on Zenfone 2. Although the updated binaries unfortunately could not fix the problems entirely, at least the they work as intended as I haven't discovered anything broken by the updated stuffs yet.
However, this won't help if your app crash is due to the developer shipping an incomplete set of x86 native binaries (this can happen). You need to sideload it through adb and force it to use ARM abi, like this:
Code:
adb install --abi armeabi xxx.apk
Note that the abi name varies among apps, armeabi is just an example, it might be arm, or armeabi-v7a, depending on the app itself.
EDIT: Say, is there a way to report device incompatibilities to Play Store so I can explain the device's situation and let Play Store always ship the last known good version for our device? There seem to be some apps that previously worked, but not now due to updated native libraries that would cause native crashes on libhoudini (Play Store will still treat our device as compatible due to the device exposing the ARM abis thanks to libhoudini), and I often need to disable the app in question's auto-update to prevent Play Store updating it to the native-crashing version.

Running "houdini --version" in a terminal emulator results in:
"houdini: command not found"
for latest version of Groovy Android

deckinghalls said:
Running "houdini --version" in a terminal emulator results in:
"houdini: command not found"
for latest version of Groovy Android
Click to expand...
Click to collapse
Are you using Termux? It seems I'm getting the same result there as well, but houdini outputs just fine in the built-in Terminal as well as in the T-UI launcher.
And as for file lists:
In /system/bin there's the "houdini" binary.
Then there's "libhoudini.so" in /system/lib/ (this is the main library which is of i386 architecture).
And the rest of the files (ARM libraries) in /system/lib/arm/. These consist of the exact same set of files as the ones provided by the custom ROMs, plus an additional one (libgate.so).

LSS4181 said:
Are you using Termux? It seems I'm getting the same result there as well, but houdini outputs just fine in the built-in Terminal as well as in the T-UI launcher.
And as for file lists:
In /system/bin there's the "houdini" binary.
Then there's "libhoudini.so" in /system/lib/ (this is the main library which is of i386 architecture).
And the rest of the files (ARM libraries) in /system/lib/arm/. These consist of the exact same set of files as the ones provided by the custom ROMs, plus an additional one (libgate.so).
Click to expand...
Click to collapse
I am not sure what is meant by "the built-in Terminal" (I don't recall any ROM coming with one?) but I did use Termux as well as the terminal in TWRP. I figured out if you type "su" to get root access first, then the command works fine in Termux.
Flashed the .zip file. So far, I haven't noticed any changes, good or bad. I don't remember which apps would FC (maybe the Amazon Echo app and Disney Infinity 3.0?) but I'll keep you posted.

deckinghalls said:
I am not sure what is meant by "the built-in Terminal" (I don't recall any ROM coming with one?) but I did use Termux as well as the terminal in TWRP. I figured out if you type "su" to get root access first, then the command works fine in Termux.
Flashed the .zip file. So far, I haven't noticed any changes, good or bad. I don't remember which apps would FC (maybe the Amazon Echo app and Disney Infinity 3.0?) but I'll keep you posted.
Click to expand...
Click to collapse
Some ROMs do have built-in terminal app. However, you need to enable it, which can be done in Settings -> Developer Options (assuming you know how to enable Developer Options as well). There would be an option to enable "Local terminal" which is the built-in terminal app.

Which means it will help the x86 device run ARM ???
I do not understand. Please analyze me

Mkey_34 said:
Which means it will help the x86 device run ARM ???
I do not understand. Please analyze me
Click to expand...
Click to collapse
libhoudini is Intel's ARM binary translator that helps x86 devices run ARM apps, albeit with some limitations and performance reduction due to overhead. Without it, most apps won't be able to work at all, as they don't have x86 native libraries.
Zenfone 2 already has houdini included, that's why it could run as many apps as any other devices. The flashable zip here contains updated files (for 7.1 ROMs) in hope it could help with some problematic ARM-only apps that refuse to work with libhoudini, though in most cases the differences are barely noticeable.

LSS4181 said:
libhoudini is Intel's ARM binary translator that helps x86 devices run ARM apps, albeit with some limitations and performance reduction due to overhead. Without it, most apps won't be able to work at all, as they don't have x86 native libraries.
Zenfone 2 already has houdini included, that's why it could run as many apps as any other devices. The flashable zip here contains updated files (for 7.1 ROMs) in hope it could help with some problematic ARM-only apps that refuse to work with libhoudini, though in most cases the differences are barely noticeable.
Click to expand...
Click to collapse
Thank you
---------- Post added at 02:58 AM ---------- Previous post was at 02:53 AM ----------
something's wrong I can not download it. I need another link. thank you

My device is running Groovy Android 7.1.1, 18 May Build.
so i have successfully upgraded houdini version using your flashable file. Thank You for your work.

what if i want to revert to the houdini version that comes preinstalled with the rom, will dirty flash rom zip work?

sushuguru said:
what if i want to revert to the houdini version that comes preinstalled with the rom, will dirty flash rom zip work?
Click to expand...
Click to collapse
The zip is meant to be flashed every time you reflash the ROM, so yes, dirty flashing should be able to revert it.
But again... you're supposed to do a nandroid backup before flashing, and there's no need to flash this if you aren't encountering any native code crashes from arm-only apps at the moment.
Unfortunately, as Intel had already left the mobile market and no more Intel-powered smartphones produced anymore, some developers started to "move on" and use libraries or compiler options incompatible with houdini in order to make their apps run more efficient on modern ARM smartphones, without having to be "constrained" for compatibility reasons...
The houdini binaries I found only seems to be a minor update, and I'm not sure if Intel is still working on this or if there are possibilities to obtain an even newer houdini version with "y" suffix, which our phone uses.

Added an experimental (UNTESTED!) version found from Android-x86 (8.0.0_y.49374). This version was originally meant for Oreo, so I'm not sure if this would work on a Nougat ROM.
Currently on Android-x86 only the "y" version (which our devices use) is available. The other versions ("x" and "z") are not present, and the link would simply give you a "not found" error.
Although I don't mainly use the phone anymore, I could still conduct some tests with the device if I have time.

Bit the bullet and tested the 8.0.0_y.49374 build. Does not work. Evie force crashes right off the bat. Haven't tested further than this, but if I cannot even use my launcher of choice, that isn't a good sign.

[ROM][Pie] Unofficial LineageOS 16.0

This is an unofficial build of LineageOS 16.0 for the Motorola razr I, (XT890/SMI).
Lots of thanks to Hazou. This rom is based on his los-14 rom and I got help from him with los-16.
This rom has full hardware support and should run stable. It has been tested by me in daily use. I'm using the rom without google apps, but with microg. Installing google apps requires some apps to move to data partition because of limited system size. See install description for more info.
Special Features
-All features of Hazous 14.1 rom
-MicroG signature spoofing patch is included.
-Adaptive icons can be disabled in homescreen settings.
I can include more features if requested
Known Bugs
-The camera preview image sometimes shakes at random
Download
https://mega.nz/#F!5fBWlIAQ!Jlq9Bj789iJ0iIIptK00tg
Update
If you already run an earlier version of this rom, just boot to twrp and install the latest flashable zip file
Install
1. Backup everything you don't want to loose.
2. Download and install TWRP 3.2.3 (download in attachments. Can be flashed with fastboot or with another recovery)
3. If you come from another rom do a full wipe with twrp
4. Download and install the rom flashable zip (download from mega.nz link is in section download)
5. If you want to install opengapps or need system partition space for other things. Install the move_to_data.zip file from the attachments. This will move the Webview and the LatinIME app to data partition.
6. Choose one of the following options:
-either install google apps (download form https://opengapps.org/. Choose x86 9.0 nano or pico)
-or install MicroG (can be installed with the unofficial installer https://forum.xda-developers.com/android/development/microg-unofficial-installer-t3432360) this is lighter in ram and cpu usage but you will get problems with google chrome and other apps
7. If you want root access install the addonsu-16.0-x86.zip (download in the attachments)
8. Reboot the phone. First reboot will take some time
Changelog
Code:
20191018:
fixed problem with sms receiving
20191012:
mobile network connection works now after boot
Fixed problems with network switching
Show taps option is working now
intel art extension enabled
Call recording enabled
text relocation warnings disbaled
(untested) encryption. Needs special configuration (see below)
20190819:
SELinux is now enforcing
Notification access feature enabled
solved crashes with houdini emulated apps
20190713:
usb configuration works properly
battery light works now
July security patches
20190704:
first stable release of this rom
DATA Encryption
If you want to enable data encryption this would break the pds partition backup. To prevent this, the cache partition can be used as backup location:
-edit /system/bin/pdsbackup.sh
-change PDS_FILE=/data/misc/pds/pdsdata.img to PDS_FILE=/cache/misc/pds/pdsdata.img
-resize data partition in TWRP:
Code:
umount /data
umount /sdcard
e2fsck -f /dev/block/mmcblk0p17
resize2fs /dev/block/mmcblk0p17 1367079
-reboot the phone
XDA:DevDB Information
unonfficial LineageOS 16.0, ROM for the Motorola RAZR i
Contributors
julianwi, Hazou
Source Code: https://github.com/julianwi/android_device_motorola_smi/tree/lineage-16.0
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.0.x
Based On: LineageOS
Version Information
Status: Stable
Stable Release Date: 2019-08-19
Created 2019-07-04
Last Updated 2019-08-19

This if I did not expect it, I'll try to see how it goes. Thank you.

Download links and install description are up now. Download from mega.nz because xda download section is broken at the moment. I'm waiting for your test reports

It's really great works, thank you!!
I quickly tried and found several points.
- USB connection with PC
All USB connection option including File Transfer, USB tethering, PTP are grayed out.
Disabling/Enabling android debug in setting didn't work.
- Wifi with storage encryption
When you enable storage encryption, WiFi always become disabled, not be able to enable.
Just FYI, it required deleting /system/bin/pdsbackup.sh AND reducing partition size of 'data' (/dev/block/mmcblk0p17).
- SElinux
Although it is designated as permissive in device.mk, it's actually worked as "disabled".
I'm not sure it's related or not, however, when building "user build", it's failed with "ERROR: permissive domains not allowed in user builds".
I know "user build" is not officially supported in Lineage release, however, it's really helpful if we can do it for AFW usage.
Previously I could use Lineage 14.1 smi build for AFW and safetynet app with user build.
BTW, performance is really great, seems to be almost same as Lineage 11.

dumkm said:
It's really great works, thank you!!
I quickly tried and found several points.
- USB connection with PC
All USB connection option including File Transfer, USB tethering, PTP are grayed out.
Disabling/Enabling android debug in setting didn't work.
Click to expand...
Click to collapse
I also noticed that. Will see how this can be fixed. It is just a problem with the option dialog. Usb connection works fine. As a workaround you can set a default USB configuration in developer options
dumkm said:
- Wifi with storage encryption
When you enable storage encryption, WiFi always become disabled, not be able to enable.
Just FYI, it required deleting /system/bin/pdsbackup.sh AND reducing partition size of 'data' (/dev/block/mmcblk0p17).
Click to expand...
Click to collapse
I have not tested storage encryption yet. Will have a look at it later
dumkm said:
- SElinux
Although it is designated as permissive in device.mk, it's actually worked as "disabled".
I'm not sure it's related or not, however, when building "user build", it's failed with "ERROR: permissive domains not allowed in user builds".
I know "user build" is not officially supported in Lineage release, however, it's really helpful if we can do it for AFW usage.
Previously I could use Lineage 14.1 smi build for AFW and safetynet app with user build.
Click to expand...
Click to collapse
I think lineage trust doesn't differentiate between permissive and disabled. Selinux support is planned for future releases

Thank you for quick check.
Regarding USB connection, I also confirmed that Ubuntu can recognize as external storage with above option, besides Windows still does not recognize. Maybe depending on my environment.
Also I noticed that Chrome, Chrome Beta and Chrome Canary (therefore another Chrome based apps such as Maps Go) always crash. This is also maybe my environment only, though. BTW, I could install MicroG, besides couldn't install OpenGapps 9.0 pico due to partition size limit.
Additionally, I couldn't find any LED settings, currently LED is always off during charge or any notification.

dumkm said:
Thank you for quick check.
Regarding USB connection, I also confirmed that Ubuntu can recognize as external storage with above option, besides Windows still does not recognize. Maybe depending on my environment.
Also I noticed that Chrome, Chrome Beta and Chrome Canary (therefore another Chrome based apps such as Maps Go) always crash. This is also maybe my environment only, though. BTW, I could install MicroG, besides couldn't install OpenGapps 9.0 pico due to partition size limit.
Additionally, I couldn't find any LED settings, currently LED is always off during charge or any notification.
Click to expand...
Click to collapse
Notification Led should work. Can be configured under settings->apps and notifications->notifications->notification light. I don't know what happened with the battery light. It will hopefully come back if I upgrade the driver to hidl.
Google Chrome is a known problem with MicroG. It requires official gapps. I will check if some of the unprivileged lineage apps can be moved to data partition to make place for google apps

Newbie question
Hi all, I know someone who's selling her old RAZR i XT890 and I'm interested (for experimental reasons but also the oddity that it's Intel powered). I've never owned a RAZR i so I've got some questions:
-The phone is from 2012 so quite old and has 1GB RAM, does it work well with this Lineage 16? Because usually newer software would perform bad on older SoC (I used to have iOS 7 on iPhone 4 back in the day and it was painfully slow compared to 6).
-On Lineage 16, can it run any Android app as a standard new Android Pie phone? I ask because this is an Intel x86 CPU, so can it still run Android apps as normal or are most of them only designed for ARM and therefore unusable?
If I get the good news, I may buy the phone and try this Lineage OS custom ROM.

Regarding LED, maybe it became working after modifying some option of notification light. Battery connection light is still always off.
Regarding opengapps, I moved webview and LatinIME from app directory to external SD in TWRP, then installed as normal app after system boot. Webview worked fine besides LatinIME always crash. I'm using different IME, so it's no problem. With this environment, opengapps nano can be installed, then Chrome, Maps and other google apps worked.

dumkm said:
Regarding LED, maybe it became working after modifying some option of notification light. Battery connection light is still always off.
Regarding opengapps, I moved webview and LatinIME from app directory to external SD in TWRP, then installed as normal app after system boot. Webview worked fine besides LatinIME always crash. I'm using different IME, so it's no problem. With this environment, opengapps nano can be installed, then Chrome, Maps and other google apps worked.
Click to expand...
Click to collapse
That's good. Than we can make a flashable zip to automatically move and symlink them to data partition.
I will provide a new build till end of the week with improved usb and notification LED implementation. I already got it working in my local setup
flameseewa said:
Hi all, I know someone who's selling her old RAZR i XT890 and I'm interested (for experimental reasons but also the oddity that it's Intel powered). I've never owned a RAZR i so I've got some questions:
-The phone is from 2012 so quite old and has 1GB RAM, does it work well with this Lineage 16? Because usually newer software would perform bad on older SoC (I used to have iOS 7 on iPhone 4 back in the day and it was painfully slow compared to 6).
-On Lineage 16, can it run any Android app as a standard new Android Pie phone? I ask because this is an Intel x86 CPU, so can it still run Android apps as normal or are most of them only designed for ARM and therefore unusable?
If I get the good news, I may buy the phone and try this Lineage OS custom ROM.
Click to expand...
Click to collapse
Newer android versions have been designed while keeping low ram devices in mind. Ram hungry special features like the picture in picture mode are excluded from builds for older device. So the situation is much better then on iOS. But a newer phone would run better thought.
Most android apps are available for x86. But some are still arm only and get automatically emulated. The intel houdini emulator integrates these apps natively into the system but they are a bit slower then x86 apps. These are for example Skype and a few unity based games

julianwi said:
Newer android versions have been designed while keeping low ram devices in mind. Ram hungry special features like the picture in picture mode are excluded from builds for older device. So the situation is much better then on iOS. But a newer phone would run better thought.
Most android apps are available for x86. But some are still arm only and get automatically emulated. The intel houdini emulator integrates these apps natively into the system but they are a bit slower then x86 apps. These are for example Skype and a few unity based games
Click to expand...
Click to collapse
Thanks for the response. So I should be alright with it then, hopefully. I just hope it won't lag on that old SoC. I'd love if you could upload a quick video of it in action.

TWRP error 70
julianwi said:
This is an unofficial build of LineageOS 16.0 for the Motorola razr I, (XT890/SMI).
Lots of thanks to Hazou. This rom is based on his los-14 rom and I got help from him with los-16.
This rom has full hardware support and should run stable. It has been tested by me in daily use. I'm using the rom without google apps, but with microg. I don't know how smooth it runs with official gapps.
Special Features
-All features of Hazous 14.1 rom
-MicroG signature spoofing patch is included.
-Adaptive icons can be disabled in homescreen settings.
I can include more features if requested
Known Bugs
-Mobile cell connection doesn't connect after boot. You have to turn airplane mode on and off to let it work.
-selinux is set to permissive for now (reduced security)
Please report more bugs if you test this rom
Install
1. Backup everything you don't want to loose.
2. Download and install TWRP 3.2.3 (download in attachments. Can be flashed with fastboot or with another recovery)
3. If you come from another rom do a full wipe with twrp
4. Download and install the rom flashable zip (download from mega.nz https://mega.nz/#!ICwXRC6D!VZqe3o5zeWbmMiZvka_BtUTW5T_V7_OdMS57Oe9CbMk)
5. Choose one of the following options:
-either install MicroG (can be installed with the unofficial installer https://forum.xda-developers.com/android/development/microg-unofficial-installer-t3432360)
-or install google apps (download form https://opengapps.org/. Choose x86 9.0 pico)
6. If you want root access install the addonsu-16.0-x86.zip (download in the attachments)
7. Reboot the phone. First reboot will take some time
XDA:DevDB Information
unonfficial LineageOS 16.0, ROM for the Motorola RAZR i
Contributors
julianwi, Hazou
Source Code: https://github.com/julianwi/android_device_motorola_smi/tree/lineage-16.0
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.0.x
Based On: LineageOS
Version Information
Status: Stable
Stable Release Date: 2019-07-04
Created 2019-07-04
Last Updated 2019-07-05
Click to expand...
Click to collapse
I've installed the OS without problems, but when i try to get GApps Pico or any other version TWRP prompt error 70. How should i proceed? There is any additional configuration needed?

Kazvko said:
I've installed the OS without problems, but when i try to get GApps Pico or any other version TWRP prompt error 70. How should i proceed? There is any additional configuration needed?
Click to expand...
Click to collapse
Yes, system partition size is limited on this phone. To install GApps some files need to be moved to data partition.
I created a flashable zip to automate this process. Take a look at the modified install description in the first post

New build is up now.
flameseewa said:
Thanks for the response. So I should be alright with it then, hopefully. I just hope it won't lag on that old SoC. I'd love if you could upload a quick video of it in action.
Click to expand...
Click to collapse
Sorry don't have enough time to make a video in the near future. Maybe someone else can record a video of it

I could confirm that notification LED and USB storage works fine with lineage-16.0-20190713-UNOFFICIAL-smi. Thanks.
Still WiFi with storage encryption does not work.

julianwi said:
New build is up now.
Sorry don't have enough time to make a video in the near future. Maybe someone else can record a video of it
Click to expand...
Click to collapse
Alright, thanks. I bought my friend's RAZR i and I am planning to use it as a daily driver with this ROM (I'm a light user anyway), I can't thank you enough for making this LineageOS for such an old device. I wonder if such a recent Lineage has been developed for the 2011 Atrix, haven't seen one.
I have questions though, firstly I've never used a custom ROM before, can I simply follow the instructions on this thread to get it working, or is there anything that has to be done beforehand like rooting? Secondly, are any other OSs successfully booting on this x86 phone, as I can't find it on XDA? (it surprisingly hasn't gotten much attention as a hackable device like HTC HD2 or Nokia N900 got).

dumkm said:
I could confirm that notification LED and USB storage works fine with lineage-16.0-20190713-UNOFFICIAL-smi. Thanks.
Still WiFi with storage encryption does not work.
Click to expand...
Click to collapse
I know, haven't looked at the storage encryption for now. It will maybe be in the next update next month
flameseewa said:
Alright, thanks. I bought my friend's RAZR i and I am planning to use it as a daily driver with this ROM (I'm a light user anyway), I can't thank you enough for making this LineageOS for such an old device. I wonder if such a recent Lineage has been developed for the 2011 Atrix, haven't seen one.
I have questions though, firstly I've never used a custom ROM before, can I simply follow the instructions on this thread to get it working, or is there anything that has to be done beforehand like rooting? Secondly, are any other OSs successfully booting on this x86 phone, as I can't find it on XDA? (it surprisingly hasn't gotten much attention as a hackable device like HTC HD2 or Nokia N900 got).
Click to expand...
Click to collapse
If the phone never had a custom rom yet, you have to unlock the bootloader first. Description is in this thread: https://forum.xda-developers.com/showthread.php?t=1928551

julianwi said:
If the phone never had a custom rom yet, you have to unlock the bootloader first. Description is in this thread: https://forum.xda-developers.com/showthread.php?t=1928551
Click to expand...
Click to collapse
That's an old guide, will everything still work?

flameseewa said:
That's an old guide, will everything still work?
Click to expand...
Click to collapse
Yes, it should still work the same. If some links are outdated you can google them yourself

Thank you for bringing my old RAZR i back to life! I really appreciate the time and effort you spent for this obselete phone. Looking forward for more updates and for a bug free ROM. Using it now
dumkm said:
- Wifi with storage encryption
When you enable storage encryption, WiFi always become disabled, not be able to enable.
Just FYI, it required deleting /system/bin/pdsbackup.sh AND reducing partition size of 'data' (/dev/block/mmcblk0p17).
Click to expand...
Click to collapse
I'm not sure if I misunderstood but when you said "it required deleting....." and "reducing partition size of data", did you mean you can get WiFi to work if you do those things? I'm no expert at these but I can atleast apply the "fix" (if it really is) given that you guide me, if it's okay with you. Thanks!

Debloated stock -without Google apps- for best performance/privacy

One word ahead: I am a huge fan of Custom Rom (LOS). Nevertheless some feature will be missed (volte) and performance might be not perfect (camera, dolby) due to proprietary firmware.
On the other hand I like to keep away from data collecting companies as google.
Isn't than a rooted and debloated stock image with microG instead of Gapps the best possible option? I did this once for an older Samsung and results was fine. But there is one thing I don't know: How it will act on updates. I don't want to miss security updates.
Any ideas? Or is it a bad idea at all? Curious to your feedback
I will extend this posts. Not only writing a step by step howto, but also explain the ideas behind. Maybe also some steps aside, mistakes I did.
So for the first steps look https://forum.xda-developers.com/t/...est-performance-privacy.4240057/post-84573619
EDIT Mai 1st 2021:
I get for some time a second phone and did some experiments. From what I see new - there is no real need to go the long, long way to root it. Even on a stock RAM you get get back control over your data!
The gapps are less important than I ever thought. If you get curious, just switch over here to get more information:
https://forum.xda-developers.com/t/...est-performance-privacy.4240057/post-84909643
(To avoid misunderstandings: I will not provide a ROM. There are some steps to go with existing stock ROM - as only this gives you full features.)

Isn't than a rooted and debloated stock image with microG instead of Gapps the best possible option?
Click to expand...
Click to collapse
I will assume you are comparing it with the latest LOS available.
Privacy-wise? Not really. Even if you remove GApps from the stock rom, Samsung will still collect data. You can limit that by:
1. Not using Samsung Account/Pay/Pass (as on why, read privacy policy)
2. Removing "com.hiya.star", which collects your location, tho it will break the "Places" feature in the Phone app.
3. Replacing Samsung Keyboard with an open-source alternative or disabling the autocorrect feature as it sends corrected texts to Samsung.
4. Not using Samsung Weather app/widget (as on why, read privacy policy)
After that and using some F-Droid apps I would say you have a pretty decent privacy.
Performace-wise? Absolutely. The battery life is a lot better compared to AOSP ROMs and thats not even taking into account that OneUI has the Ultra Power Saving Mode. The camera is miles ahead too and of course, VoLTE actually works.
How it will act on updates. I don't want to miss security updates.
Click to expand...
Click to collapse
I have tested that. If its just a security update, then it will install flawlessly. If its a feature update, some bloatware and Gapps may reinstall. I haven't experienced any update failing, but that may change in the future.
Any ideas? Or is it a bad idea at all? Curious to your feedback
Click to expand...
Click to collapse
If you really care about privacy, but dont want to miss out on features, then go ahead with debloating and degoogling the stock rom. Just note that some problems with compatibility and some rare random crashes may occur.

Retrecd said:
...
1. Not using Samsung Account/Pay/Pass (as on why, read privacy policy)
2. Removing "com.hiya.star", which collects your location, tho it will break the "Places" feature in the Phone app.
3. Replacing Samsung Keyboard with an open-source alternative or disabling the autocorrect feature as it sends corrected texts to Samsung.
4. Not using Samsung Weather app/widget (as on why, read privacy policy)
After that and using some F-Droid apps I would say you have a pretty decent privacy.
Click to expand...
Click to collapse
Sure, that was the ideas to remove as much of Google/Samsung stuff as possible and also use AFWall to limit data transfer. I am using FDroid already, there are good tools, respecting privacy.
So you went already same approach? There is already a thread about debloating, but I think what I want to do is even behind that. If you like, you can share more details. I would like create some kind of a howto ...

starbright_ said:
Sure, that was the ideas to remove as much of Google/Samsung stuff as possible and also use AFWall to limit data transfer. I am using FDroid already, there are good tools, respecting privacy.
So you went already same approach? There is already a thread about debloating, but I think what I want to do is even behind that. If you like, you can share more details. I would like create some kind of a howto ...
Click to expand...
Click to collapse
Here is an article on using ADB to remove bloatware: https://www.xda-developers.com/uninstall-carrier-oem-bloatware-without-root-access/
Now here is a list of bloatware on the S10, remove it the way showcased in the article: https://forum.xda-developers.com/t/galaxy-s10-s10-debloat-bloatware-removal-list.3912073/
The list is a bit older, but most of the bloatware is still present in the latest version.
The same way you removed the bloatware, you remove the Gapps. Remove the following core Google packages:
Code:
com.google.android.gsf
com.android.vending
com.google.android.gms
If you want to remove more packages that aren't listen in the article install the "App Inspector" from Google Play or any APK site and find out the names of the packages.

Please read and share your ideas. I am sure that we only together can create the best possible solution. Maybe you know othere ways/apps to solve a problem. As of now I share my point of view.
My hope is, that at the end of this to have an "howto" covering as many aspects as required for this.
First thing nevertheless is install TWRP/Magisk, which seems to be more tricky than usual.
While you can debloat your ROM without root, there are imho 3 reasons for doing that:
microG needs be installed as a system-app to have working location service (get your location by GPS or by offline database)
you will have problems to install a firewall and adblocker. There are solution with don't need root (Netguard and Blockada), but both base on a "virtual" VPN connection and you can have only one at a time. So you do have either a Firewall or an AdBlocker, but not both.
The way of create and restore backups are much better with root. I can recommend TWRP itself for a general backup and migrate for apps/settings.
For those like me, coming from unrooted stock fw the recommendation is to
root with Magisk - details here
flash the TWRP - details here
spoofing the signature for usage of microG instead of playservices
install microG and "friends"
debloat stock ROM
migrate data from old to new device

starbright_ said:
First thing nevertheless is install TWRP/Magisk, which seems to be more tricky than usual.
Click to expand...
Click to collapse
Tricky indeed and even more tricky is installing updates. Once you know the procedure it's ok, but it is still a major hassle compared to a stock OTA update.

here
jelbo said:
Tricky indeed and even more tricky is installing updates. Once you know the procedure it's ok, but it is still a major hassle compared to a stock OTA update.
Click to expand...
Click to collapse
Sure, I am aware of that. I just read about it. But there is no other way except you are happy with stock. First time is always a nightmare, but I hope once get used to it.

Retrecd said:
Here is an article on using ADB to remove bloatware: https://www.xda-developers.com/uninstall-carrier-oem-bloatware-without-root-access/
Now here is a list of bloatware on the S10, remove it the way showcased in the article: https://forum.xda-developers.com/t/galaxy-s10-s10-debloat-bloatware-removal-list.3912073/
The list is a bit older, but most of the bloatware is still present in the latest version.
The same way you removed the bloatware, you remove the Gapps. Remove the following core Google packages:
Code:
com.google.android.gsf
com.android.vending
com.google.android.gms
If you want to remove more packages that aren't listen in the article install the "App Inspector" from Google Play or any APK site and find out the names of the packages.
Click to expand...
Click to collapse
How did you managed that switch from Gapps to microG? I assume if you delete Gapps without MicroG installed you will get lot of problems.
How did you manage to spoof Stock Rom? Are you on 11?

Hi all. Very interesting conversation. Has someone successfully used microG on stock rom on a daily usage? In my past experience, using microG without signature spoofing is making a lot of apps not working properly...

lp35 said:
Hi all. Very interesting conversation. Has someone successfully used microG on stock rom on a daily usage? In my past experience, using microG without signature spoofing is making a lot of apps not working properly...
Click to expand...
Click to collapse
I think spoofing is a must have. I just evaluate how this can be done.
With Android 11 it is more difficult. I found that one (but not sure whether signature spoofing works):
https://forum.xda-developers.com/t/module-smali-patcher-7-3.3680053
this one:
https://forum.xda-developers.com/t/signature-spoofing-on-unsuported-android-11-r-roms.4214143/
or via NanoDroidPatcher
https://forum.xda-developers.com/t/...7-microg-pseudo-debloat-f-droid-apps.3584928/
It says:
11.0 / SDK 30 (R)
Patcher does not work from TWRP
Patcher works from Magisk if your ROM's services.jar already contains classes.dex
I checked that and /service/framework/service.jar contains that classes.dex
So I give this a try, downloaded the patcher and started it out of Magisk. Log looks ok so far. It requires reboot.
The problem with enabling Magisk is - you have to boot with "recovery" mode - and not sure, it fails several time (although USB is plugged) or phone reboots again and than Magisk is disabled - while booting into TWRP still works.
So my guess is: This causes some problem.

Step 3) - Spoofing
Have been successful:
I followed that thread:
Signature Spoofing on unsuported Android 11 (R) Roms
How to get Signature Spoofing working on Android 11 (R) Roms that have no support for Signature Spoofing? In my Case here I use a Samsung Galaxy S8 with an unofficial LineageOS 18.1 (Android 11) by stricted I use TWRP recovery but this should...
forum.xda-developers.com
But I just created a spoof_AVDapi30.zip. My thinking just flashing that one for spoofing seems to be wrong. Also flashing both: spoof and microG_AVD....
So what I did was flashing out of Magsik (Module install out of memory) NanoDroid-microG-23.1.2.20210117.zip and followed by spoof_AVDapi30.zip.
Power off. And take care you boot with Power + Vol+ + Bixby + USB Cable pressed until you see the splash-screen.

I really hope stock + MicroG takes off!

It is already. I started debloating - that is another step. See this thread:
Debloating S10e
I am still in testing phase and I would like to see once an FW-update via OTA will happen. Curious what will happen with my system.

starbright_ said:
It is already. I started debloating - that is another step. See this thread:
Debloating S10e
I am still in testing phase and I would like to see once an FW-update via OTA will happen. Curious what will happen with my system.
Click to expand...
Click to collapse
Amazing! Keep us posted!

Debloating is done.
Final step is takeover of my previous installation. I do that with the tool/app migrate. That works rather fine.
I am not using the special sections to export contacts, SMS ...
Contacts will be exported from the app itself and than imported in new device.

Is this dead? Hehe

No it is working. Have you tried that?
I couldn't deinstall com.samsung.android.kgclient and blocking its UID (with awfall) causes some battery drain. Maybe I have to live with not blocking this.
Anyhow, I am wondering whether debloating is required at all. Cutting the connection to Ethernet (to not talk "home") might be enough.
I don't not have enough understanding of what will be better: remove or just block.
A removed app might not spend time on connecting servers again and again, while a missed service can cause trouble if you don't expect that.
Probably it is best to uninstall apps you are really sure there are no dependencies to others and block the others-

starbright_ said:
Step 3) - Spoofing
Have been successful:
I followed that thread:
Signature Spoofing on unsuported Android 11 (R) Roms
How to get Signature Spoofing working on Android 11 (R) Roms that have no support for Signature Spoofing? In my Case here I use a Samsung Galaxy S8 with an unofficial LineageOS 18.1 (Android 11) by stricted I use TWRP recovery but this should...
forum.xda-developers.com
But I just created a spoof_AVDapi30.zip. My thinking just flashing that one for spoofing seems to be wrong. Also flashing both: spoof and microG_AVD....
So what I did was flashing out of Magsik (Module install out of memory) NanoDroid-microG-23.1.2.20210117.zip and followed by spoof_AVDapi30.zip.
Power off. And take care you boot with Power + Vol+ + Bixby + USB Cable pressed until you see the splash-screen.
Click to expand...
Click to collapse
So just install those inside of magisk and reboot? I'll give it a shot.

Dead thread, I see.

steventorres said:
Dead thread, I see.
Click to expand...
Click to collapse
What are you continuously posting about dead thread? Any question or any feedback? Strange. It is is all set and done. What do you expect?
@VenfefulRat:
This wasn't a real question, right. It was stated to do it out of magsik. It would be great to have some feedback.
@All: A forum lives from reading (to gain knowlegde ) and posting (sharing experience, ask questions, give feedback). If someone ask and he gets answer I would expect a feedback or at least a like (as a sign it has been read). Otherwise people stop posting and the only left here are those who ask or feed the troll.