For convenience, latest MicroG & Open GApps enabled MTCB/MTCC firmware, in a suitable thread.
Updated on July 3, 2018:
(reason in post #636)
MicroG in post #396, and here:
Mod Edit :- Links Removed
Mod Edit :- Links Removed
Open GApps in post #416, and here:
Mod Edit :- Links Removed
Mod Edit :- Links Removed
They are interchangeable, same partitioning, I would switch between them with a wipe all in recovery. I'd also say equally fast.
I currently use the Open GApps version, recommendable, since it does not require special settings or workarounds, as being 100% Google compatible. It also performs a one time nice Google setup of the unit, beginning with language, account, and so on.
Note to all using this firmware for the first time: since it is differently partitioned from what you had before, you must also perform a wipe all in recovery, ideally just before the first startup (to avoid wasting time), or at any time now.
WARNING: MicroG Core and LP don't work well: contacts are not seen from apps like Hangouts, Google/Voice Search, while True Contacts needs local loading of profile & contacts - from vcards on the internal SD. Therefore I strongly recommend the Open GApps version!
Note also that with the MicroG version, the gms core app must be configured, and Hangouts' service called NetworkConnectionCheckingService must be disabled, for Hangouts to work:
Code:
pm disable com.google.android.talk/com.google.android.apps.hangouts.service.NetworkConnectionCheckingService
TomTom GO storage support is explained in post #45.
TT GO spoofing is in post #392.
Poweramp's early start&restart is also supported by default.
Phone calls via a BT connected phone could be dialed by (always) selecting the MTC Service(aka Headunit), as the preferred dialer.
MTC Sound direct sound control is readily supported, if the associated hardware mod is also done.
Automatic screen brightness control based on location&time is also implemented by default.
Blank logo kernels are in post #600 (get them while they last).
Developer Mode in post #332.
Firmware is also rooted and xposed.
To those who make outlandish claims about this firmware: they are either trolls or firmware is not for them. However firmware supports all rk3188 MTCB or MTCC units. Make your own judgement, and don't get scared away.
===
BTW, be careful, don't ruin this thread of mine, because I won't open another ever again...
===
Here's another one: in principle, unless an unlikely bug is reported, I don't reply in this thread to users who are not listed as saying thank you to this post.
===
Mod Edit :- Content Removed
Thanks @dsa8310 .. your rooms are great .. I installed microg rom yesterday . Works great . Will try the new one soon. The only question I have is the performance of both roms similar coz I have 1GB Ram
dsa8310 said:
For convenience, latest MicroG & Open GApps enabled MTCB/MTCC firmware, in a suitable thread.
MicroG in post #396.
Open GApps in post #416.
They are interchangeable, same partitioning, I would switch between them with a wipe all in recovery.
I currently use the Open GApps version, recommendable, since it does not require special settings or workarounds.
===
BTW, be careful, don't ruin this thread of mine, because I won't open another ever again...
Click to expand...
Click to collapse
Hi @dsa8310, is it possible to find what version of your firmware that I have installed in my radio. I think I updated yesterday, but not sure if it the recent one that you posted yesterday.
Maybe a tall tell signature or something to look for.
Again, thanks for your work on the firmware. And I hope this section works out for you.
Wayne
The Open GApps firmware has DPI 240 (as the original) while MicroG has DPI 210 and it appears shifted slightly to the left on 800x480 screens, at least.
It's a detail that could be easily adjusted (parameter ro.sf.lcd_density in file /system/build.prop).
The MicroG specific (gms) app is also present in its corresponding flavor lineup, plus the extra xposed module (for fake signature).
Other than that I don't keep track of versions - it's only the last one that matters.
As usualI I ll be putting the ROMs on the fileserver for everyone.
Where is the donate button ?
Thank you very much for your hard work
I am running right now DSA Rom 5.1.1 with MicroG and its awesome.....
So fast and stable, highly recommended.
Should I switch to open gapps ? I am very happy with MicroG, is it worth it ?
Best regards
dsa8310 said:
The Open GApps firmware has DPI 240 (as the original) while MicroG has DPI 210 and it appears shifted slightly to the left on 800x480 screens, at least.
It's a detail that could be easily adjusted (parameter ro.sf.lcd_density in file /system/build.prop).
The MicroG specific (gms) app is also present in its corresponding flavor lineup, plus the extra xposed module (for fake signature).
Other than that I don't keep track of versions - it's only the last one that matters.
Click to expand...
Click to collapse
I have the 6/28 one.. MicroG I guess. Getting Gapps..
Thanks bud.
Like to donate as well..
EagleSoldier said:
Where is the donate button ?
Thank you very much for your hard work
I am running right now DSA Rom 5.1.1 with MicroG and its awesome.....
So fast and stable, highly recommended.
Should I switch to open gapps ? I am very happy with MicroG, is it worth it ?
Best regards
Click to expand...
Click to collapse
I now use the (pico) Open GApps enabled version. I like it because I don't have to configure things and it is 100% Google compatible. I dislike it because of Google ads' undisturbed presence, unlike the MicroG version that avoids them, partially, at least for my set of apps.
There might be observable differences in their footprint size (necessary RAM) and load of system (background tasks). I can't say for sure, since I have a 2GB RAM (upgraded) unit. Furthermore, I run the same set of apps most of time: Poweramp and TomTom GO which have the same heavy requirements (TT mainly).
Perhaps 1GB units should use MicroG while 2GB ones could afford the Open GApps version.
A technical comparison between versions could be done, in a terminal (termux), with commands like "free -m" (free memory) and "uptime" (busybox uptime) (for load average); "busybox ps", too, if implemented.
But, ultimately, it's a matter of feeling: if you feel that one version is more responsive, feel free to use it.
(switching back and forth is facilitated by the same partitioning, though going through a wipe all in recovery seems necessary)
I've got a 1gb joying radio. I can confirm that system boot is much faster than Malaysk 4.4.4, BUT apps like Pandora and Google maps take ages to load and sometimes even freeze. So I'll go back to KitKat.
ankerede said:
I've got a 1gb joying radio. I can confirm that system boot is much faster than Malaysk 4.4.4, BUT apps like Pandora and Google maps take ages to load and sometimes even freeze. So I'll go back to KitKat.
Click to expand...
Click to collapse
Have you tried both MicroG and Open GApps? If yes, was it any difference for you?
The system is tuned for TomTom GO, for example, if you make a folder called tomtom/com.tomtom.gplay.navapp/foobar on any of your external storage (the GPS card, usually) then big maps will stay externally. While TT GO, the "free" version (v1.16.1_Build_2077, if I recall correctly), lays around the internet...
(making the folder above will help even if TT is not installed, because the system will stop looking for it, in a loop)
dsa8310 said:
Have you tried both MicroG and Open GApps? If yes, was it any difference for you?
The system is tuned for TomTom GO, for example, if you make a folder called tomtom/com.tomtom.gplay.navapp/foobar on any of your external storage (the GPS card, usually) then big maps will stay externally. While TT GO, the "free" version (v1.16.1_Build_2077, if I recall correctly), lays around the internet...
(making the folder above will help even if TT is not installed, because the system will stop looking for it, in a loop)
Click to expand...
Click to collapse
So far I I only used your latest micro G. I thought it might be quicker , because of less Google apps
ankerede said:
So far I I only used your latest micro G. I thought it might be quicker , because of less Google apps
Click to expand...
Click to collapse
Well, if you expect all your apps to be supported, try the Open GApps version. It's the pico flavor, minimal setup for Google support.
(make a wipe all from recovery, just before first reboot)
dsa8310 said:
For convenience, latest MicroG & Open GApps enabled MTCB/MTCC firmware, in a suitable thread.
MicroG in post #396, and here:
mxupdateKLD1024x600LP5.1.1.rk3188.MTCB-C.December.part2.rar
mxupdateKLD1024x600LP5.1.1.rk3188.MTCB-C.December.part1.rar
mxupdateKLD800x480LP5.1.1.rk3188.MTCB-C.December.part2.rar
mxupdateKLD800x480LP5.1.1.rk3188.MTCB-C.December.part1.rar
Open GApps in post #416, and here:
oxupdateKLD1024x600LP5.1.1.rk3188.MTCB-C.December.part2.rar
oxupdateKLD1024x600LP5.1.1.rk3188.MTCB-C.December.part1.rar
oxupdateKLD800x480LP5.1.1.rk3188.MTCB-C.December.part2.rar
oxupdateKLD800x480LP5.1.1.rk3188.MTCB-C.December.part1.rar
They are interchangeable, same partitioning, I would switch between them with a wipe all in recovery. I'd also say equally fast.
I currently use the Open GApps version, recommendable, since it does not require special settings or workarounds, as being 100% Google compatible.
===
BTW, be careful, don't ruin this thread of mine, because I won't open another ever again...
Click to expand...
Click to collapse
Are these versions different from what you posted on the other thread? You said on the other thread to wipe before installing the GApps version.
If I can switch between them without a full wipe, I'll give some feedback on which one is faster on 1GB.
elyl said:
Are these versions different from what you posted on the other thread? You said on the other thread to wipe before installing the GApps version.
If I can switch between them without a full wipe, I'll give some feedback on which one is faster on 1GB.
Click to expand...
Click to collapse
No, they are not.
It's possible, but then uninstall by hand three apps: com.google.android.gsf, org.microg.gms.droidguard, FakeGapps1.1, and then reboot.
Hi dsa,
i'm on your latest microg version of your firmware with the playstore. But when i open the playstore and try to connect i get this error: [RH-01]
any idea?
problem iam facing now i cant play music while using google maps, any help?
dsa8310 said:
Well, if you expect all your apps to be supported, try the Open GApps version. It's the pico flavor, minimal setup for Google support.
(make a wipe all from recovery, just before first reboot)
Click to expand...
Click to collapse
I give it a + for GApps. Still works nice with Google Play and able to use what you paid for with no issues.
Finally got more play time with the latest and I like it.. Using 1G, no upgrade memory at all..
Still need to add a few more apps.. but good to go..
Thanks @dsa8310
Yes, the MicroG version is not 100% compatible, and also needs some extra configurations (described in the other thread, see the mentioned posts - in the OP of this thread - and subsequent ones).
While the Open GApps version is fully supported, and equally fast, no drawbacks at all.
The speed is determined by the mix of apps run on the HU, in any case.
I would suggest that you check out the Open GApps version - make a wipe all (from recovery) just before the first start, and you will enjoy a nice one time Google setup of the unit, commencing with language, account, and so on.
And once you go black you'll never go back!
dsa8310 said:
Yes, the MicroG version is not 100% compatible, and also needs some extra configurations (described in the other thread, see the mentioned posts - in the OP of this thread - and subsequent ones).
While the Open GApps version is fully supported, and equally fast, no drawbacks at all.
The speed is determined by the mix of apps run on the HU, in any case.
I would suggest that you check out the Open GApps version - make a wipe all (from recovery) just before the first start, and you will enjoy a nice one time Google setup of the unit, commencing with language, account, and so on.
And once you go black you'll never go back!
Click to expand...
Click to collapse
Exactly what I did. A setup that I have never seen before had to be done. Great Job.
It's Open GApps' merit, not mine. Once the setup is done, everything else falls into place.
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Current Events
Dodo released! This means this ROM is now extinct. Sorry! If links below fail, try this one!
OTA is in Beta. Will be included in CM 13 release once both are stable. OTA will be available before full-sized versions due to the testing process (updates are tested first).
SnapChat will not work without some help. This is entirely SnapChat's fault for trying to control your device. Please read this thread before flashing and how you can make it work. Or just open Xposed installer, install Snapprefs and reboot.
Introduction
Welcome to the fastest and most stable ROM for your OnePlus. This thread is mainly a support thread for Jgcaap's awesome work, allowing him to spend more time working on "M" and less time answering questions. His latest builds will be tested by me, hand selected for stability, and the best of the crop will be repackaged, enhanced, and placed here. If you are new to this ROM, check the screen shots for benchmark results and battery life screenshots. Be amazed, then download the ROM and be even more amazed! Smooth as glass and flows like water! As one person has said, "Disgustingly Fast!"
Please read this entire post! Check back often for updates. Also, current jgcaap users will get additional information and tips that can be useful. Check out all the links! And if you want to try some Bacon wrapped Marshmallow, click the bent arrow in the Announcement's line.
Wildlife
Each ROM will be named by an animal, starting at A for Aardvark. A picture of the animal will be placed here so you can see at a glance which release is current. The original jgcaap ROMs often have multiple releases in a single day, and every country has a different date format, so the animal names will allow us to represent specific "official" releases with memorable names.
Release (CM 12.1 - jgcaap 11/30): (click image to update)
Downloads | Other Stuff | Links
Features & Changes
The ROM gets repackaged so that new users don't have to go about tracking down which files they need and which order to flash things. The firmware is included and everything is set and ready to go. For legal reasons, just add your own GApps and go. This ROM currently has the following feature's prepackaged and already included with the ROM ...
SuperSU (pre roooted)
Xposed (special jgcaap version)
Moab Ad Blocker
--- ZooKeeper can configure this!
ColorOS Camera
--- with manual focus option
Viper (Audio Eargasm)
Dolby ATMOS! (Dodo+)
Send Reduced (send small pics)
CatLog (for bug reports)
Show On Lockscreen (wallpaper)
OmniSwitcher (optional)
Init.d Support (Badger+)
Governor: blu-active (Badger+)
Low call volume fix
OTA Support (coming soon!)
Support, Questions, Feature Requests and Bugs
Please report all bugs for CM12.1/Lollipop based Jgcaap ROMs to this thread. Even if you didn't download one of the Wildlife pre-packaged ROM sets! Feel free to ask questions. This thread will have the same warm inviting atmosphere that jgcaap's development thread has always had. Newb-friendly and all are welcome!
Getting Started
There will be two ROM images available. The update packages will be designed with a smaller download size with only the files that have actually been changed. The installer will not remove things you have added nor re-install programs you have removed. If you are already using a WildLife ROM, use the Update packages to upgrade. This does not apply to full versions. The full versions should be clean flashed.
The next post will have Step-by-Step instructions telling you exactly what you need to do and how to go about flashing your phone or upgrading. The post after that will have all the tips and tricks for maximum tweaker power. Finally, we'll have instructions on how to rescue your phone when something goes wrong.
Sponsored by Eddon Systems
Additional Downloads at Eddon Systems Download Page
XDA:DevDB Information
Wildlife Android, ROM for the OnePlus One
Contributors
uudruid74, jgcaap, purerawenergy
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: INCLUDED
Source Code: Jgcaap's Github Repo
Based On: CyanogenMod 12.1
Version Information
Status: Stable
Current Stable Version: See Post
Stable Release Date: 2015-11-16
Created 2015-11-16
Last Updated 2015-12-11
Flashing WildLife
Flashing Instructions - Full ROM
Step 1 - Backup
If you don't have a backup program, you can grab a really fast and free one, Backup+. XDA Forum | My Mirror - Direct Download. Be sure you keep the APK on your Internal Storage so you can install it easily and restore the rest of your apps. Also, I strongly recommend you copy your internal storage (or at least the backup directory) onto a PC, a harddrive, a flash drive, or cloud storage such as Google Drive. Get it off your phone and make it safe.
Step 2 - Boot into Recovery
Even if your reboot menu doesn't have a Recovery option, you can always just hold down the Volume Down button when your phone boots and you're good. I recommend Philz Recovery from this XDA thread or you can download the exact ZIP I use.
Step 3 - Wipe Carefully
This step is what is known as a "clean flash". Do not perform this step if you are flashing an upgrade or addition. If this is the first time you've flashed this ROM, you want the full version and you want to do it cleanly. Failure to clean flash leads to odd problems. For example, Agent stopped reading my calendar, or my Camera plugins would start to disappear.
You do not want to do a Factory wipe or anything like that or you'll lose all your data. Do not format /data. Here's where it gets confusing. Many recovery systems treat /data and Internal Storage as if they were separate partitions, but they are not. Your internal storage is on the same partition as /data. If you are from Windows, image your /system is your C: drive, and /data (where your apps are at) and your internal storage are both on D:. Your recovery has a specific wipe designed to safely wipe /data without wiping out your internal storage by erase directories individually, yet automatically.
Philz makes this simple and direct. Select Wipe and Format Options, then select Clean to Install a New ROM. Confirm the wipe, and you are ready to go.
Step 4 - Flash the ZIP
This is pretty easy. Select the option to flash it, find it on your device, and away it goes. If you downloaded the file to your PC (or wiped your internal storage and now have no files on your phone), you can use the "sideload" option you see in the menu. Just plug in a USB cable and type: adb sideload Aardvark.zip This does require that you have adb drivers set up on your PC, but you needed that to unlock your bootloader, right? More tips like this in a later post!
Step 5 - Flash your Gapps
The most important part of Gapps is making sure its for Lollipop. The more up to date, the better. You should download the smallest GApps that fits your needs, just so you don't have to download so much. You can specifically control which Gapps are installed with a config file. Just drop the gapps-config.txt into the same directory as your gapps ZIP file. This file can even delete crufty Cyanogen apps that you don't need or want (you have better ones from Play store right?) and reduce bloat considerably.
About the Gapps Config | OpenGapps is the recommended Gapps package | Newer Sources for Gapps | My gapps-config.txt ... note: you might not want to use my config unless you want almost all your Cyanogen apps to go away. When the system comes up, you won't have a file manager to install Backup+. I install it with "adb install BackupPlus.apk" or if its on the phone, you can log in with adb shell and then install with pm install $PWD/BackupPlus.apk
TIP: If you have Chrome installed from Gapps, you can open it and type "file:///sdcard" in the URL window and then select your Backup+ or Titanium Backup APK to install it. Be sure you have "Install from unknown sources" turned on. Now you can restore your good File Manager (like FX File Manager mentioned in Post #5) from your Backup and don't need Cyanogen's!
NOTE: If you have trouble with OpenGapps, then you can try my stable mirror or SlimGapps (which is now recommended by jgcaap, but I've not tried it myself yet ... but expect it to be the new recommended after I run it through the paces).
Step 6 - Reboot your Phone
After flashing, the first time your phone comes up, its going to optimize itself and you should expect it to take awhile. Don't panic, and wait a few minutes. I refuse the CyanogenMod account (you already have a Google one, and Cyanogen doesn't offer anything extra and defintely do NOT send bug reports or analytics to Cyanogen!). I also go into Settings, About Phone, tap the Build Number like a mad monkey to turn on Developer options, and from there, I enable the Reboot Menu, Fast Boot, Cut the animations down to below 0.5, and turn on ADB since I'll be installing Backup+ over ADB.
Step 7 - Restore your Backup
Use your file manager (or ADB) to install your backup program and then restore the rest of the apps from your backup. I keep my Wifi off so that Google Play won't freak out and try upgrading stuff while its restoring. Do not use ROM Settings Backups to try to move settings from one ROM to another (thats what Update files are for). You can usually restore your Desktop with Backup+ by restoring the data for Trebuchet if you formerly used another Cyanogen release. The next reboot I go to Play Store and upgrade any apps that need it.
Step 8 - Final Config / Updates
I haven't found a perfect way to back up Trebuchet and my desktop ... but Backup+'s system backup tool (paid feature) can be used to restore the Trebuchet data, which gets everything but the widgets. If you use OmniSwitcher, just turn it on. If you use Xposed, it should already be working and active. If you don't use Xposed, jgcaap's version won't slow down your phone or cause glitches. However, if you really don't want it on your phone, you can flash this to deinstall it and can reinstall it without flashing the whole ROM by flashing this file.
MaxxAudio is gone ... use Viper. Set it to Super Audio Quality and reboot when it says to (Aardvark only, no reboot required for Badger and above). More about Viper here. I strongly recommend reading as there are a lot of optional add-ons (convolvers and such for emulating other tones and systems) but many of these will use significant battery power. I don't even use it for the built-in speaker. You can control it per output device, and have different profiles, such as if you have multiple pairs of headphones or different USB Audio devices.
Please Donate to the developers when you use an app. It is only through your support that you get to use high quality apps. This ROM has ads blocked, so developers of free apps will go poor and hungry since they won't be getting any revenue from your ad clicks!
Flashing Instructions - Updates
An update is a slimmed down version without any apps (unless they've been updated), no firmware, no media files, etc. And it avoids flashing over files you may have changed or deinstalled, like the hosts file or various bundled apps. It doesn't touch your settings, you don't need to wipe anything, and it just upgrades in-place. All you need to do is Steps 2 and 4 and 6!! Updates are clearly labelled. Never wipe your phone when installing an update! No OTA yet.
Tweaking
Tweaking, Trimming and Theming
Kernel
There is a UKM for jgcaap's kernel which is in the download area. You'll need Synapse from Play store to use it. I don't recommend tweaking the kernel, but if you want the option it is there. Just download the ZIP, flash it in recovery, and you can start tweaking some kernel parameters! Personally, I use 3C Android Tuner (see below) because it can tune more than just the kernel, but you might find something UKM does that 3C doesn't. As as Badger, you can use the init.d script option for restoring settings imposed by kernel tweakers.,
Governor
Your governor controlls when your CPU is at full blast, when it throttles down, and how quickly it changes and by how much. This will affect battery and performance (and "lag") considerably. As of Badger, the default CPU governor is "blu_active". You won't need to ever change to "Performance" mode to squeeze out more power, its runs even more fluid than before, and battery life is as good as ever. There are a couple ways to select the governor. The one I use is 3C (below). The only source of lag is memory. If you run out and Android has to swap stuff out, there will be a noticeable delay. If you rarely get lag, but get it rather severely, I bet its when you have 20 apps open and a million installed with their own background services and content providers! Suddenly the OOM (Out Of Memory) killer attacks and your phone stops for a second or two. I'm testing a possible solution, but everyone's phone is different.
CPU Temp
How hot does your CPU get? If you run Cardboard like me, you might be concerned. If you have to switch to an app to find out, then your CPU will have already cooled by the time you see the temp. This CPUTemp App displays an overlay anywhere you want that will show you your exact temperature. It can also save the data and give you in-depth graphs of CPU speed, load, and temperature. Alternately, you can just use this Xposed module to always show the CPU temperature in your status bar. (WARNING: I've not tested this Xposed module myself).
Xposed
Wildlife already has Xposed installed. If you have heard of requirements that your ROM must be deodexed or odex or and that you will have compatibility issues or slowdown, the current news is that the latest Xposed works on odexed ROMs and jgcaap has personally blessed some modifications to increase speed and compatibility with this ROM, and final result is packed into Wildlife. However, until you install some Xposed modules, it lies dormant. Fire up the Xposed Installer and you can start searching for tools to tweak how your phone looks, how it acts, how it sounds, and tweak some more battery life. Once you install a module, activate it, and then reboot.
Please be aware that not all Xposed modules are compatible with Lollipop and not all modules are created equal. I have heard mixed reports on GravityBox in particular. If for some reason your phone gets horribly confused and won't boot because of some Xposed module you have installed, or if you just hate the idea of having Xposed and want it gone. There is a solution! Flash this Xposed Uninstaller and if you flash this and want Xposed to come back, just Flash Jgcaap's modified v75 Xposed framework.
Ones I use are the 3C Toolbox helper, Clarity (makes your contacts in better definition), No Device Check (privacy), RootCloak (hides root), Smart Network (auto switches between 3G and LTE to conserve battery).
3C ToolBox
If you like tweaking, this toolbox has a little bit of everything. You can view logs, including last kernel boot log (the one that ran before you crashed), open a terminal, set a firewall, change CPU and GPU governors, disable services, remove programs from the start-up list, change network congestion control ... the list goes on and on!
Here is the XDA thread (with download links) for this tweaker's toolbox.
Battery Extensions
The first step to checking battery problems is Wakelock Detector and Better Battery Stats. These tools will tell you where your juice is going. If an app is holding a wakelock, ditch the app or alert the developer. Once you see what is chewing the most battery you can launch an assault on it with these tools:
Xposed Modules - Again, I'm going to defer to an expert source, @V7 's Extreme Battery Life Thread for all the goodies on PowerNap, Greenify, Amplify, and all the others that you've heard about.
Underclocking - I simply do NOT recommend this. Why? Well I checked Better Battery Stats! And my CPU had only been at full speed for 6% of the time. The next speed was under 2Ghz. So, is it worth slowing down your phone by 20% in order to achieve an overall savings of about 1.2% battery? The reason for this is that your system has what's called a governor that predicts how much CPU you need at any given moment and adjusts accordingly. This means you only use max CPU when you need it! If you underclock, then you are slowing down your phone when you need it most. You might even waste more battery because you'll be keeping your screen on longer waiting for your phone to finish!
Undervolting - I don't like this idea either. Basically, the voltage is how much strength it takes to open the transistor gates, like little doors. When your CPU gets busy, the voltage can fluctuate by small amounts, and if you undervolt your CPU, you can occasionally get a gate that doesn't open, and your get a CPU doing really crazy things and some app with crash or your whole system will crash. Generally, higher speeds require higher voltage to keep your CPU stable, and less voltage at lower speeds. Imagine trying to open and shut a door really fast ... you'll need more force than just shutting the door gently.
Can I get 9hrs SOT? - Sure! See the screen shot, but here's the secret. WASTE battery power! If you have a flip-case, remove it. Take your screen timer and set it REALLY high and don't turn off your screen. Let it BURN! This will ensure that your screen is on for a really long time. Cheating? Well, yes and no. The point is that someone who is chatting on their phone over Wifi and rarely touches it, but leave the screen on while doing so will get great SOT. The guy streaming Bluetooth audio all day long and has their phone tethered to use LTE internet with a low signal will waste tons of battery and may not have the screen on at all. The 9hr screen on time was done while doing all the above, plus some web browsing using ....
Ultimate Browser - This browser is said to use less battery than Chrome and others. You can check it out and see for yourself on The Ultimate Browser XDA thread.
Themes
Many people ask about the themes pictured in the screenshots. This is the Deep Darkness Overhauled Theme but with the thinner fonts from Cosmos CM12. Just select which parts of each theme you like before clicking the Update button.
I'm now using an Add-On package for this theme that gives icons that aren't so dark. It has a cool font, too, but I don't know if I like the Cosmos or Deep Darkness Add-On better. I'm also using a compromise between the 400 DPI (real) and 480 DPI (stock) of 440 DPI. This still gives me 5 icons wide on the home screens without throwing off apps that expect stock DPI (much).
Rescuing Your OnePlus From Disaster
Rescuing Your OnePlus From Disaster
I sure hope you never need any of this information! The following links are from Heisenberg's OnePlus One thread
Device Recovery/Unbrick Tools
[TOOL] One-Click Backup & Restore EFS on OnePlus One
[TOOL] OnePlusRecovery Tool | Restore Stock (CM11S) | Fix Bricks | ETC
[TOOL] OnePlus One Return To Stock - Automated!
[GUIDE] [UNBRICK] Unbrick Oneplus One
I originally intended to post a step-by-step, but instead I'll defer to existing/tested sources. Heisenberg's thread has tons of useful information and is well worth checking out.
More Info
Link Database
Someone has an awesome thread listing all the links you could ever ask for, so I'll defer to those that are already maintaining this. Here you are ...
http://forum.xda-developers.com/showthread.php?t=2843675
Recommended Apps
Please note that these are some of the best of the best, and most of them are not free!
Email - [email protected] Mail This is a fork of K-9, which is the Android Mutt (from Dr Who) .. mutt being a classic Unix mail program. I love Dr Who, but [email protected] was such a big improvement, I had to go with it. If you need full folder support, multiple accounts, and support for email cryptographic signing and encryption, multiple identities, and html editing of email and html signatures!
Music Player - PowerAmp - this is by the best music player I've used, bar none. If you don't want it messing with your custom lockscreen wallpaper, you can tell it not to, or add a whole second/custom lockscreen over the original. It has its own EQ, but I don't need it with Viper. To make PowerAmp compatible with Viper, simply turn off the direct volume control. You can use Xposed to add more volume steps if you like the extra control that PowerAmp's default has.
Video Player - VLC Video Lan Client Plays everything, does everything, streams videos, and has remote control apps to connect to other VLCs anywhere on your network.
QuickPic - QuickPic is a replacement for the stock Cyanogen Gallery. It works and acts much the same only its much much faster. Another good choice is Piktures, but new users may find it a bit more complicated, and it doesn't seem to be nearly as fast.
Agent - While much of what Agent does can be duplicated with other tools, the ease of use and flexibility of this tool can't be beat. It monitors your calendar for meetings and silences your phone, knows when you are driving and responds to your texts (and/or reads them to you), detects when your sleeping and makes your phone quiet (even if you sleep at different times). Has a battery saver mode, and can even remember where you parked. The Meeting agent works best if your calendar supports the "Busy" flag, which Google removed about a year ago, so ...
Today Calendar - The Today Calendar is just a really beautiful app and has some nice widgets (although I just use cLock from Cyanogen to show my calendar and make appointments via Voice commands, so I don't see Today much, I still bought it). It has the Busy flag and all sorts of features. If you want one a little less flashy (and free), try Boxer Calendar.
File Manager - The FX File Manager is by far the greatest file manager. It has everything built in, including SMB to network with Windows and SFTP to network with any machines running SSH. App Management, Media Refresh, and nice clean material design! Bloat free!
FXR Wifi Repair - Get this app and install it NOW! You will thank me the day you end up needing it!
Project Toolbar
For those on Tapatalk that don't get the toolbar, here it is ...
Downloads
ScreenShots
Reviews
Feature Requests
Bug Reports
.
I'm running 12.1-20151030 deodexed version. Could you provide me links to proper Xposed installer? Or is it ok to flash that one package with all that installed?
Sent from my A0001 using XDA Free mobile app
Tyga187 said:
I'm running 12.1-20151030 deodexed version. Could you provide me links to proper Xposed installer and Viper? Or is it ok to flash that one package with all that installed?
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Don't know if 10/30 needs deodex or not but if its before jgcaaps hacks you'll need the older Xposed. I have it and Ill upload it for you to my site (Eddon Systems Download Page ... link in first post). Viper is already there (look for LolliViper).
If you don't mind taking the time to do a clean flash, Aardvark is based on the 11/08 build with the Apple code. All works out of the box Dirty flash possible, but can lead to weird problems.
I'll upload Xposed v75 right now
More about me at https://eddon.systems
Ok so it is possible to run odexed version and have Xposed working? I've heard that I need deodexed version for exposed that's why I'm on 20151030.
Thanks a lot for fast response!
Sent from my A0001 using XDA Free mobile app
Deodex and Xposed
The newer builds are made in such a way that you can use them with Odex builds without problems. We even have a special "Hacked" version of Xposed that prevents the possible slowdown issues and bypassing jgcaap's ART improvements.
So yes, use Odex and new builds and preferably the "Hacked ZIP" for the framework, although normal v75 still works. Or flash Aardvark. I've got maybe a dozen Xposed modules active.
The reason you don't see newer Deodex is because they aren't needed anymore
uudruid74 said:
The newer builds are made in such a way that you can use them with Odex builds without problems. We even have a special "Hacked" version of Xposed that prevents the possible slowdown issues and bypassing jgcaap's ART improvements.
So yes, use Odex and new builds and preferably the "Hacked ZIP" for the framework, although normal v75 still works. Or flash Aardvark. I've got maybe a dozen Xposed modules active.
The reason you don't see newer Deodex is because they aren't needed anymore
Click to expand...
Click to collapse
Which build has Apple code ? Normal odexed build , deodexed or bionic build ?
lokesh.3440 said:
Which build has Apple code ? Normal odexed build , deodexed or bionic build ?
Click to expand...
Click to collapse
It varies based on date and jgcaap's whim. The 11/08 builds do. I don't think any deodex builds do because he stopped making those before the Apple assembler code experiments.
Since 11/08 has it, Aardvark has it.
Bionic isn't a ROM build, its the Android low level C library to which the Apple code is being added.
More about me at https://eddon.systems
uudruid74 said:
It varies based on date and jgcaap's whim. The 11/08 builds do. I don't think any deodex builds do because he stopped making those before the Apple assembler code experiments.
Since 11/08 has it, Aardvark has it.
Bionic isn't a ROM build, its the Android low level C library to which the Apple code is being added.
More about me at https://eddon.systems
Click to expand...
Click to collapse
I m downloading latest build now.
Good job Evan. This will definitely help Jorge and the Marshmallow project. Thanks in advance brother.. See you on the testing ground.
Tom 2.0
Purerawenergy said:
Good job Evan. This will definitely help Jorge and the Marshmallow project. Thanks in advance brother.. See you on the testing ground.
Tom 2.0
Click to expand...
Click to collapse
I'm going to be stealing your post you made in the other thread about battery tweaks ... Greenify, Amplify, PowerNap and all that. It will go in the tweaks post. Let me know if that info is changed and if you can remember the date or post number for when I go digging.
More about me at https://eddon.systems
uudruid74 said:
I'm going to be stealing your post you made in the other thread about battery tweaks ... Greenify, Amplify, PowerNap and all that. It will go in the tweaks post. Let me know if that info is changed and if you can remember the date or post number for when I go digging.
More about me at https://eddon.systems
Click to expand...
Click to collapse
You may want to link my buddy @v7 in there somewhere if you want. He's the wake lock master Bro. And his helpfulness is awe inspiring.
Tom 2.0
---------- Post added at 03:36 PM ---------- Previous post was at 02:50 PM ----------
Oh and it's not stealing if you ask someone. Haha
Tom 2.0
Purerawenergy said:
You may want to link my buddy @v7 in there somewhere if you want. He's the wake lock master Bro. And his helpfulness is awe inspiring.
Tom 2.0
---------- Post added at 03:36 PM ---------- Previous post was at 02:50 PM ----------
Oh and it's not stealing if you ask someone. Haha
Tom 2.0
Click to expand...
Click to collapse
Actually, I put your name in as a contributor (and obviously @jgcaap) which gives you a lot more access. That way, if I'm hit by a bus tomorrow, other people can step in (its the admin in me). You might be able to edit the project page and initial reserved posts yourself.
My routed here is getting old so I'm doing a reflash and adding a captive portal to disconnect people when there isn't a human body using it. I need to cut down on everyone's bandwidth usage. So ... gonna be a busy night.
More about me at https://eddon.systems
uudruid74 said:
Flashing Instructions - Full ROM
If you don't have a backup program, you can grab a really fast and free one, Backup+. XDA Forum | My Mirror - Direct Download.
Click to expand...
Click to collapse
Hi,thanks for this thread. I've downloaded aardvark but for the backup+ download from : https://eddon.systems/Download/Backup+_Beta_1_R2.apk I get a 403 forbidden.
Verstuurd vanaf mijn A0001 met Tapatalk
I am going to download your rom and test it in a couple of days
Wysłane z mojego A0001 przy użyciu Tapatalka
Well this came around at a perfect time! I haven't been actively flashing my phone much this year and my current ROM is from July 5th lol. So I'm not really new, but could use something pre made like this. Reading, backing up, and downloading this afternoon, then flash later tonight. Thanks for putting this up.
Is the rom ok to flash on system/data/cache on f2fs ?
Updated and revised, 11-29-20
In this post I am presenting a way to slightly extend the practical range of the 8 gb Nook Tablet by using microG for Google Services Framework spoofing rather than the resource-hogging GApps. Although I have tested these ROMs thoroughly on the BNTV250a, they would all likely run just fine with GApps on the 16 gb model (I currently run AOSP 7.0 with microG on my 16 gb tablet), while only CM 11 runs acceptably on the 8 gb model with GApps. Let's get that simple setup out of the way first.
I selected the unofficial CM 11 ROM with the final security patches by Chris Hoffmann [https://www.mediafire.com/?gq1y21uz11lr1c0]. It is serviceable for me. The main drawback is the old WebView (which cannot be updated) resulting in the inability of browsers to display many sites properly, including the current default skin for XDA. Despite this, I've come to feel that it's perhaps the best option, with or without GApps. Installing this ROM is easy. Flash with the recovery listed in post #2, reboot, then flash a pico GApps package from Open GApps. To run the ROM without GApps, read on.
I made a quick tour of CM 12.1, CM 13, AOSP 6.0 and AOSP 7.0, and Lineage 14.1. In the following post I'll lay out some pros, cons and hints based on my experiences. I flashed each ROM several times, trying different things, building the system from scratch each time rather than restoring apps from backup. That gave me a chance to work with each OS and see how it would perform not only during setup, but also during a shakedown/tweaking phase. What I can say about all of these ROMs is that GApps effectively kills each and every one on the BNTV250a.
Life without GApps
I, of course, tried side-loading apps without GApps. Easy, right? I thought so until I came to a few that whined about requiring Google Play Services to run. Even mundane things like the NPR News app, my local newspaper and MX Player are "GSF dependent" (Google Services Framework). Then I tried another app that would not install at all. Turns out it did a license verification check (it's free!) and saw no Google anything, so forget it. This was sort of news to me I suppose because even my lowly NST had GApps installed once upon a time, so I never encountered this issue before. You can hunt around for apps elsewhere but if you pick up an app that happens to be featured in the PlayStore, you may be out of luck no matter where you got it from. Or maybe not.
There is a project called microG by XDA member @MaR-V-iN. It consists of a lightweight set of apps (two at minimum, a third if you want location services) which provide the needed authentication to Google servers and/or inquisitive apps. There is a catch: the ROM must support "signature spoofing".
These ROMs do not have that option. You can Google "signature spoofing" to read the pros and cons. This is just information. Caveat emptor, etc. There is an Xposed module called FakeGapps which enables signature spoofing. I tried this on a few ROMs and found it worked fine. At the time I started this there was no official Xposed update for Android 7.0 and as that was one of my targets, I started looking for something else [note: Xposed has since been updated to include Android 7.0 and beyond]. That led me to Tingle by XDA member @ale5000. This is a Python/ADB based method of automatically patching framework.jar to enable signature spoofing. This seemed to me a more direct and elegant approach. Although I was intimidated by it at first, I eventually just dove in. The only thing I didn't already have was Python and that was easy enough to install. The process is basically automatic once it gets going. Unfortunately it does not work for ROMs that are odexed or deodexed. The AOSP 7.0 ROM turned out to fall in that category. Xposed must be used there.
OK, what can all this do for you? It can get you a spoof of Google Services Framework without GApps. Period. There are a few simple additions to allow for location services. It used to be that you could also enable Calendar and Contacts syncing. No more. As for PlayStore access, this is possible running microG with CM 11, but not beyond. It's just too resource intensive. For ROMs beyond CM 11 I found the Aurora Store (F-Droid) to work OK, although not always in the same way. On some ROMs you can use the anonymous Aurora Store login, on others you need to supply a Google account (email). Trial and error.
The General Process
If you have never "flashed" anything before that you can talk about at work, then you need some basic instructions for creating an SD card that will allow you to try out these procedures. The excellent instructions by @digixmax here will get you started with the SD card. You need to follow steps 1-2 to prepare the card, although the version of TWRP you use will depend on the ROM you want to try out (see second post for links). Also, the ROM itself will vary (see second post for links) and you will not want GApps (unless you are just installing CM 11 with GApps). The remainder of the steps (3-10, skipping 9) also describe the general process of flashing a ROM (or other "flashable" files like Xposed, etc.) using the SD card.
1. Flash the ROM using an appropriate recovery (I have listed the ones I used in the following post)
2. First boot, enable root, USB debugging and ADB
EITHER
3. Connect tablet to PC via USB and access via ADB ("adb devices"--some of these ROMs require that you approve PC access to the tablet via ADB, so check the tablet screen to approve that option if needed)
4. Open a command window on the PC and navigate to your Python installation directory. Because I was not sure what I was doing I just dumped the entire contents of Tingle into the Python directory. That simplified path issues for me. Type "python main.py" and select option 1. Wait for the "all done", hit CTRL-c and kill ADB server. Disconnect tablet from USB and reboot.
OR
3. Flash appropriate Xposed for the OS; reboot
4. Install Xposed installer app and FakeGApps.apk; use Xposed installer app to enable FakeGapps (signature spoofing); reboot
5. Install root file manager of choice if desired (the CM stock file managers are totally capable of the following operations if given root access; the stock file explorers of the AOSP and Lineage ROMs may allow the same, although I have had mixed results. You can always install a root file manager via ADB before continuing if all else fails) A copy of ES File Explorer is attached below.
for CM 11 without GApps but with the PlayStore:
6. Move Phonesky.apk--i.e. the PlayStore-- (old, lightweight version from a KitKat ROM: http://www.mediafire.com/file/1c2f0n3k3cwsln7/Phonesky.apk/file) into /system/priv-app; set apk file permissions to rwx-r-r.
7. Move microG component apks into /system/priv-app; set apk file permissions to rw-r-r (you need a minimum of Services Core, Services Framework Proxy for this step)
8. Reboot
9. Check microG Settings to be sure spoofing is enabled and other permissions are given; set to enable Google device registration; add an account. This process can be slow. Be patient. If you end up at a black screen, reboot and try again or see if the account is already established.
10. Open the PlayStore. Do some searching. You want to give it time to auto-update (this process may be completely silent). Exit. Check Settings>Apps>Downloaded to see if PlayStore has shown up there. If it has, then it may be updated. You can check yourself to see if the version number is higher. If there is no update, access the PlayStore again and check again. Once you have an update, you're good to go.
OR, for ROMs beyond CM 11:
6. Use root file manager to create the folder "Phonesky" in /system/priv-app. Set folder permissions to rwx-rx-rx. Use root file manager to move "FakeStore" apk into /system/priv-app/Phonesky and set apk file permissions to rw-r-r.
7. Move microG component apks into /system/priv-app; set apk file permissions to rw-r-r (you need a minimum of Services Core, Services Framework Proxy for this step)
8. Reboot
9. Check microG Settings to be sure spoofing is enabled and other permissions are given.
It's a lot, but if I could do it many times over you could do it once
In the end you'll have a tablet spoofing Google Services Framework so most apps will run without whining, but without the crushing weight of the PlayStore or the full GApps.
Contacts and Location
Life without GApps doesn't mean you have to give up these services. Just keep in mind that running background services can compromise a system that is already on the edge.
I tested the instructions that follow on a BNTV250a, using the stock Contacts and Calendar apps.
1. Contacts
There are some places in "on-line land" that describe a method for enabling contacts sync. I have not found the various methods to work any longer. It is possible to sync Contacts using DavDroid. There is only one version that will run on CM 11 and the same app will run on the other ROMs as well (attached below). However, you are adding more overhead to a device that is already pushing the limits. In the end I opted to export my contacts in vcard format and read them in as a local file. The more socially active may find this unacceptable, but it works for me.
2. Location
To enable location you will need to install an app which coordinates WiFi triangulation (something usually handled by GApps). There are two possibilities. You can get a Unified NLP apk from the microG download page. After installing the app you can check your microG settings to see if everything is OK. Then you can check Settings>Location and set it up the way you want.
If you want to use Maps you will also need to flash a maps.zip file from microG. This contains a couple of library files for Maps. As far as the Maps app itself, I have never had good performance from any version of Google Maps on my devices--until now. That's because I went fishing for an older, less bloated version that would run on the BNTV250a. It works beautifully on all my devices from KitKat to Nougat and allows pre-cache of map areas which don't expire. I've attached a copy of the apk file below.
Email
The stock Email client works great (at least for GMail accounts) and looks a lot like GMail (no surprise there). If you have your heart set on GMail, version 4.5.2--from GApps for Jellybean--seems to run just fine with a footprint of about 11 MB. I've attached a copy below.
The ROMs
Updated and revised 2-5-23
Generally I disabled any stock stuff I could that I would not use. Anything past CM 11 has a maddening issue I call "peek-a-boo keyboard", most noticeable when using the browsers. The keyboard drops out while you are typing or simply refuses to open without a struggle. You can solve this problem in CM 12 and minimize it in CM 13 by installing Simple Keyboard.
CM 11 is beginning to show expired certificates and SSL issues. You can try replacing or adding new certificates, but it's not easy and you're left with warning artifacts in the status bar. Ditto with CM 12 and CM 13, but they are not nearly as bad--for now. The stock browsers, fortunately, allow you to "ignore" security warnings which makes browsing more pleasant. You may not feel that's a great idea, but the reality is that browsing is the Achilles Heel for all these ROMS, and it's worse the higher you go. The stock browsers may give the best overall performance, whatever their shortcomings.
Because of the SSL issues, I don't recommend CM 11 any longer unless you are not going to do much in the way of internet stuff.
Note: I have noticed that both my Nook Tablets (8 and 16 GB) run better if they've been on for a bit. If yours is cranky when it gets up in the morning, pouring coffee on it won't help, but a little siesta after boot may be just the thing
CM 11 (but with issues as described above)
https://www.mediafire.com/?gq1y21uz11lr1c0
Flashed with SD-based TWRP 2.8.6.0, enabled signature spoofing with Tingle
This is arguably the best choice for the BNTV250a if you want something other than the stock B&N ROM. It runs smoothly enough that you could even keep the PlayStore app on it and it would still behave reasonably. It's even better without it. The only drawback with this ROM is that Android Webview cannot be updated. This means that some websites will not display properly or may simply crash, regardless of what browser you choose to use. I found the antique stock browser to be surprisingly good, but Via also works well. Also, the SSL is in need of updating, so you will run into issues with some websites and apps like OverDrive.
The lesson that this ROM taught me is that these tablets are for casual use. You can't just load them up with apps and expect them to run well. Think about what you really would like to use the tablet for. Consider older versions of apps that will probably still have more features than you will ever want but are less taxing to the system. You can see from the attached screenshot how I eventually pared my choices down. I should probably pare it down even more. Most of the apps are older versions and I've kept the total count low, certainly less than on my 16 GB tablet and other devices. You don't want to exceed about half of the internal storage capacity.
CM 12.1 (potential WiFi issue as described below)
http://www.mediafire.com/file/7zxc2e...K6-acclaim.zip
Flashed with SD-based TWRP 2.8.6.0, enabled signature spoofing with Tingle
Edit 9-30-22: I recently booted this up to find that it would no longer connect to my fairly new ATT router. Puzzled, I took the tablet to my local library and had no difficulty connecting there (open network, though). Next I started restoring backups of each of the other ROMs in this list and each one had no trouble with WiFi at home. I installed a fresh copy of the CM 12.1 ROM. It also refused to connect to the router. I scrounged around the web and found two more versions of CM 12.1. Neither would connect to my router. So...I'm not sure if there is some additional security ATT has built into their WPA2 authentication or what, but I mention this just to alert you that this might be a problem. I was even able to connect to a mobile hotspot generated by my Windows 10 machine (password needed). Why this new(?) problem for the 12.1 ROM only, I have no idea.
Before you start installing apps the behavior is sprightly, even on the BNTV250a. As the internal space decreases and RAM use increases, it becomes a little less so. Even so, when running well I think it comes close to CM 11 (with GApps), albeit with more lag.
The stock browser seems like the best bet (I tried many), though it can be slow.
For me this ROM has two major issues. When it is unhappy, it will simply shut down the tablet, literally turning it off. This used to sometimes happen when I ran it on my 16 GB model, so it's not the fault of the BNTV250a. The other issue is problems for apps writing to the external SD card. For a tablet with precious little internal space, you just don't want apps downloading into internal space or storing lots of data there. There is an edit to the file /system/etc/permissions/platform.xml which corrects this issue for some apps. Find the section of platform.xml below and add the last line:
Code:
<permission name=”android.permission.WRITE_EXTERNAL_STORAGE” >
<group gid=”sdcard_r” />
<group gid=”sdcard_rw” />
<group gid=”media_rw” />
This change enabled OverDrive and Kodi, for example, to download files to the external SD card. It might work for others.
Not as fluid as CM 11, but WebView issues are gone and you can access most up-to-date content (if slowly).
CM 13
https://archive.org/download/cmarchive_snapshots/cm-13.0-20160819-SNAPSHOT-ZNH5YAO0IN-acclaim.zip
Flashed with SD-based TWRP 2.8.6.0, enabled signature spoofing with Tingle
Never having tried this ROM on my 16 GB tablet, I was actually pleasantly surprised by its behavior on the BNTV250a. There's a funny WiFi thing where if you leave WiFi on when you shut down and then boot up again, it will not automatically connect (unless the lockscreen has come on, which is pretty fast after booting, so no biggie). Otherwise it's pretty much like CM 12 although maybe a little more stable--if you don't overdo it. The Sound Recorder app is somehow broken on the CM 13 ROM. If this is something you'd like, you can replace the broken version in /system/app/SoundRecorder with the one attached below. Make sure the permissions are rw-r-r and reboot.
Some apps can't write to the SD card (as portable storage). Kodi is an example, I'm sorry to say. I've tried many "solutions" to this problem but the only one that worked for me is to edit /data/system/packages.xml, adding the permission for each specific app you want. This is a long file and I did this using the editor from the CM File Manager. There are probably easier ways. After locating the app you want in the xml file, add this line anywhere between the <perms> and </perms> tags:
Code:
<item name="android.permission.WRITE_MEDIA_STORAGE" granted="true" flags="0" />
This change will be overwritten if the app updates, so you might want to keep that in mind.
This is the ROM I've settled on for my BNTV250a (screenshot of home screen below)
AOSP 6.01 "Marshmallow"
Box
notredame.app.box.com
(you want aosp_acclaim-ota-MOB30Z.160820.zip)
Flashed with emmc-based TWRP 3.0.2-0, enabled signature spoofing with Tingle
This is one of the ROMs built by @amaces. The AOSP builds are very lean compared to CM ROMs so I was hoping this might perform somewhat better than CM 13. But I don't think it does.
The first big hurdle is enabling root. My thanks to @digixmax for pointing out the right tool. After first boot (or maybe even before, but I did it after) you need to flash UPDATE-SuperSU-v2.46.zip. Works perfectly.
The stock launcher is, well, funky. I replaced it with Nova Launcher but after installing a few other apps it was clear the system was under great stress. Lots of black screens and crashes. Not a good option for the BNTV250a.
AOSP 7.0
https://www.mediafire.com/?5vcw8l603d3r5sc
Flashed with emmc-based TWRP 3.0.2-0, enabled signature spoofing with Xposed
This is another ROM by @amaces and what I run on my 16 GB tablet. On that device it is virtually flawless. I really wanted to say the same for the BNTV250a, but I can't.
Enabling root for the ROM is achieved with Magisk.
The ROM appears to be odexed to Tingle and so you must flash the correct Xposed (for 7.0 and Magisk) and install the installer app along with the FakeGapps app as described in the previous post.
The stock launcher is pitiful and you need to install a root file manager to get anything done. The system is laggy and video is not smooth. Not even a potential option for the BNTV250a.
Lineage 14.1
Box
notredame.app.box.com
(there are many versions of this ROM. The link takes you to the "obsolete" folder where you need to hunt down lnos_acclaim-ota-NJH47F.180211.zip. This seems to be the only version without the shut-down bug)
Edit 2-5-23: Well...no, it does not have the classic shut-down bug (tablet reboots right after it "shuts down"). Instead, it often shuts down just fine, but occasionally locks up during shut down and has to be forced off with the power button.
Flashed with emmc-based TWRP 3.0.2-0, enabled signature spoofing with Tingle
This is a third ROM built by @amaces (his most recent for the NT). I didn't have much hope for this because if 7.0 was an issue, I didn't expect 7.1 to perform well.
The only native root capability is for ADB. To enable full root, you need to flash addonsu-14.1-arm.zip (attached below). I did that after first boot but perhaps it can be done along with the ROM.
Not surprisingly the ROM has the feel of CM. There appears to be a file manager but it is only a partial reflection of the native file explorer and is useless for the manipulations that need to be done, so you need to adb install a root file manager as described in the previous post.
The stock browser is complete rubbish. It looks to be Gello(?) but it is the most infuriating collection of electrons I have ever encountered. There are no navigational buttons, no bookmark button--no buttons at all! I really tried. I used gestures (some rude), I tried magic words (many of which do not appear in children's books). Nada. When I finally managed to reach my test site it was like wading through, well, Jello! So....attached below is the nice lightweight stock browser from AOSP 7.0. Navigate to /system/app/Browser and there you will find Browser2.apk. Rename it to something else and copy in the Browser2.apk attached below, setting file permissions to rwx-r-r. Reboot. If you are successful, you can delete the old, useless browser apk. To enable bookmarks, navigate to /system/app/BookmarkProvider and inside you will find the apk file. Tap to install. I don't know why this needs to be done, but it does even on AOSP 7.0. Reboot and you've got a functioning browser (rife with "peek-a-boo keyboard")
The ROM hates Kodi, crashing constantly. Video from other apps is not smooth. Not a viable choice for the BNTV250a.
For a lark I tried it on the 16 GB model and it's actually not bad, but then I saw that embedded browser videos (like YouTube, for example) were funky colors, so... It may be that later versions corrected this, but those likely have the shut-down bug. In any event, a terrible choice for the 8 GB model.
Took a bit of trial and error to get the perfect version of playstore to not give an error, but I got it working. Thank you a lot for this write-up!
Yes I am breathing life back into a BN Nook in 2020 (quarantine will do funny things to a guy). Thanks for the comprehensive guide. I had installed CM11 years ago and it kinda sucks as is, so looking forward to seeing how this shakes out. I have to re-educate myself on all the various steps like adb, installing root file manager etc, it has been a long while since I played around with android's innards!
denmalley said:
Yes I am breathing life back into a BN Nook in 2020 (quarantine will do funny things to a guy). Thanks for the comprehensive guide. I had installed CM11 years ago and it kinda sucks as is, so looking forward to seeing how this shakes out. I have to re-educate myself on all the various steps like adb, installing root file manager etc, it has been a long while since I played around with android's innards!
Click to expand...
Click to collapse
While you're becoming familiar again with the procedures, give me a day or two to update the post. I recently redid my BNTV250a with CM 13 to try some things and then finally went back to CM 11 using the MicroG components rather than GApps. I'm really happy with it, but I have to say that the tablet (just like my BNTV250 with AOSP 7) behaves better if it's been on for awhile. It can be really cranky if you try to start using it right after boot.
So I'll update the post title to include CM 11 and add some details about CM 11 to the second post in a few days.
Hey thanks for keeping up with this thread! I installed CM11 as suggested but hitting a snag with tingle. I just dumped the tingl directory into the python folder as you did and ran main.py. This was the output.
C:\Python27>python main.py
MENU
1 - Patch file from a device (adb)
2 - Patch file from the input folder
> 1 adb
ERROR: Missing adb => ['adb']
NOTE: Only one binary per type is required
ERROR CODE: 65
Not sure what I'm doing wrong
denmalley said:
Hey thanks for keeping up with this thread! I installed CM11 as suggested but hitting a snag with tingle. I just dumped the tingl directory into the python folder as you did and ran main.py. This was the output.
C:\Python27>python main.py
MENU
1 - Patch file from a device (adb)
2 - Patch file from the input folder
> 1 adb
ERROR: Missing adb => ['adb']
NOTE: Only one binary per type is required
ERROR CODE: 65
Not sure what I'm doing wrong
Click to expand...
Click to collapse
I don't remember seeing the "adb" after "> 1", but I may just not remember. So, just in case and to be really clear (in case I wasn't before):
1. I assume you have adb working on your PC or you wouldn't have gotten to the Python step. Did you ever set the PATH for adb? I confess I never bothered until I tried this procedure. But you have to be able to access adb from the Python folder for this to work. If you're not sure, just cd to the Python folder and try starting adb. If it doesn't work then the PATH needs to be set. Here's a good description for Windows (scroll down to "Step 2"): https://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
2. When I said I dumped the contents of Tingle into the Python folder, I meant that literally. There is no "Tingle" folder in my Python folder,but there are a bunch of extra files that are "Tingle". Just want to be sure.
Those are my only ideas at present. I hope one of them does the trick!
Ah yes path variable did the trick! On to the next steps, I'll keep you posted!
Ok, now i am at the play store step - keep getting error "unfortunately google play store has stopped." Over and over again when attempting to open. After reboot too.
denmalley said:
Ok, now i am at the play store step - keep getting error "unfortunately google play store has stopped." Over and over again when attempting to open. After reboot too.
Click to expand...
Click to collapse
Did you
1. Check microG settings to be sure everything is OK?
2. Sign in to your Google account from the microG settings (add account)?
3. Then try the PlayStore (check permissions on Phonesky folder and app)
One part I'm not clear on. I placed all of the apks where you say to (steps 6-8), once I reboot, is play store supposed to just appear? When I do self-check in microg everything is checked except playstore and the bottom two (location). I got the impression from your instructions that I'm supposed to wait for some background processes to appear.
denmalley said:
One part I'm not clear on. I placed all of the apks where you say to (steps 6-8), once I reboot, is play store supposed to just appear? When I do self-check in microg everything is checked except playstore and the bottom two (location). I got the impression from your instructions that I'm supposed to wait for some background processes to appear.
Click to expand...
Click to collapse
Yes, the PlayStore icon should appear--admittedly a very old and funky one with this old version.
The Playstore automatically updates. I wish it did not, but there is no way to stop it. But to have that happen you have to access the Playstore at least once, maybe even download an app, and leave wifi on awhile.
On my main microG settings screen I show Google device registration ON. On the self-check screen, everything is checked except the last box. I have the location stuff installed.
So if PlayStore is unchecked, something is not right. Perhaps the app got corrupted when I uploaded it. I am shut down right now but can reup tomorrow. Or you can just get another app from Apkpure or similar. I used to use something around 8.02 to get started.
I am very much stuck at this point (unless I guess I continue with regular gapps which goes against the whole point of this approach). I tried nuking and redoing the whole process with the same result. Attached screenshots of all relevant screens to show permissions/settings/etc.
Also I can't find a "phonesky.apk" anywhere, only full-blown google store apks which are much larger than the phonesky.apk you provided and so I must assume are not the correct thing.
denmalley said:
I am very much stuck at this point (unless I guess I continue with regular gapps which goes against the whole point of this approach). I tried nuking and redoing the whole process with the same result. Attached screenshots of all relevant screens to show permissions/settings/etc.
Also I can't find a "phonesky.apk" anywhere, only full-blown google store apks which are much larger than the phonesky.apk you provided and so I must assume are not the correct thing.
Click to expand...
Click to collapse
Phonesky=PlayStore, just renamed--microG expects to see Phonesky
Something is not right with the app. I have to run, but here is a link to v. 8.02 which I have used in the past:
https://www.apkmirror.com/apk/google-inc/google-play-store/google-play-store-8-0-23-release/
Rename to Phonesky before using. It will be a little more cranky but it will work to get you going. I hope.
Edit: or, if you prefer, go to OpenGapps and download a KitKat pico GApps. Extract from that zip the Phonesky app and use it.
Edit, Edit: yeah, I tried reupping a copy of the Phonesky app but when I downloaded it the file size did not match. So I changed the first post and inserted a link to a copy on my mediafire account. That downloads with the right file size.
Well, I think I'm giving up. I've redone the process three times now. I used your new Phonesky.apk this last time and I still can't get the play store to show up. Only other thing I can think to ask - if I add a google account through microg settings, is it supposed to change to indicate that account is now added? Because if I go in there it will still say "add acount" even though I can see in the regular settings under accounts that a google account is present.
edit
The only other thing I haven't yet tried is redownloading everything and maybe even using a different PC. Ah heck who am I kidding, like I've got anything better to do. I'll keep cracking at it.
denmalley said:
Well, I think I'm giving up. I've redone the process three times now. I used your new Phonesky.apk this last time and I still can't get the play store to show up. Only other thing I can think to ask - if I add a google account through microg settings, is it supposed to change to indicate that account is now added? Because if I go in there it will still say "add acount" even though I can see in the regular settings under accounts that a google account is present.
Click to expand...
Click to collapse
I'm really baffled by this behavior. When you add a Google account via microG nothing changes on the microG settings page, but the account should show up in the CM11 settings under "accounts".
When you prepare the system for flashing, do you do an Advanced Wipe? I'm a little AR about this sort of thing, especially as my devices have been flashed with different OS's many times. I start with an Advanced Wipe, clearing out everything except, of course, the microSD card, and then I follow that by a regular wipe. Then I start flashing.
If you are still having trouble, let me know and I'll wipe my current system (I have a backup) and start again from scratch, downloading copies of the files I have posted to see if I can duplicate what is happening to you. Maybe Google has changed something in the time since I did my newest configuration and the microG folks have not caught up with it yet. This appears to be true for Contacts because I cannot get them to sync up or even see my Google contacts. This was not the case in the past. There is chatter about it on the microG site, but none of the "solutions" go anything beyond what I have already related and some of the conclusions are like "and it just started working..."
I did not do the advanced wipe, so let me try that. I'm also going to redownload everything and give it another go. No need to wipe your device just yet - you've already done WAY more than I expected to help! I will do this over the next few days and keep you posted.
Well I tried six different ways, full wipe, change the "group" set for the group permissions to "root" (it had been set to sdcard), redownloaded every last bit of software used in this process, used a different computer, etc etc etc. Nothing is working. Still no play store. Everything else seems to be fine except that.
So anyway, I finally just did a full wipe, flashed the CM11 unofficial that you provided in second post, and grabbed a kk gapps package and flashed that. Switched from trebuchet to nova and I've got a tablet I can live with! Working much better then the cm10 rom I had on there before (like swipe to unlock screen, wait 5 seconds....touch app drawer, wait 5-10 seconds....touch an app, wait 30 seconds....slooooooow).
Thanks for pushing me along in this direction, before I started back into this process I had completely forgotten all the little intricacies which would have gotten me hung up and possibly bricked. And all the of the other guides out there have broken links, outdated info, etc. So I'm happy with where I landed and very much appreciate the help, even if we didn't quite get there with your proposed improvements! I now have a capable e-book, backup songbook for gigs, and a spare digital mixer controller that I can clean up the personal stuff from and hand off to an assistant.
denmalley said:
Thanks for pushing me along in this direction, before I started back into this process I had completely forgotten all the little intricacies which would have gotten me hung up and possibly bricked. And all the of the other guides out there have broken links, outdated info, etc. So I'm happy with where I landed and very much appreciate the help, even if we didn't quite get there with your proposed improvements! I now have a capable e-book, backup songbook for gigs, and a spare digital mixer controller that I can clean up the personal stuff from and hand off to an assistant.
Click to expand...
Click to collapse
I'm glad you reached a point where you feel good about the outcome but sorry that you had to waste so much time.
I will run through the procedure again in the next few days. Maybe there's something that got garbled in the updating of the post. In any case I'd feel better if my instructions actually achieved the intended result.
nmyshkin said:
I will run through the procedure again in the next few days. Maybe there's something that got garbled in the updating of the post. In any case I'd feel better if my instructions actually achieved the intended result.
Click to expand...
Click to collapse
Well.....I'm not sure how the error crept in, but it looks like the creation of the Phonesky folder was the issue. This is needed for ROMs beyond CM11, but there are no folders in /system/app or /system/priv-app for CM11. Thus for CM11 only, the files like Phonesky.apk are simply dropped into /system/priv-app and the permissions set as described, Then everything works as it should.
I've corrected the instructions. My apologies.
SpacesungGalaxy J727P
(J727PVPU3ARC2)Disclaimer:
I am not responsible for what you do with your device. If you decide to flash this software then you are accepting any risks involved. Including, but not limited to; bricking your device, missing alarms, missing calls, loss of your job, repossession of your car, and maybe even spilt milk.
About:
This is very much a personal project that I felt others would appreciate. I enjoy retro gaming very much, and as some of you may know, emulation is very CPU intensive. Hence the reason for making Spacesung. My goal was a stock rom that was lag free, debloated, and buttery smooth for gaming. I believe I have achieved this, and so, I give this to the you, to enjoy, use, modify, and share at your discretion.
Features
•Deodexed
•Debloated- I have removed all unnecessary Samsung, Google, and Amazon apps.
•Removed all Amazon symlinks. (Libs are next.)
•Deknoxed- Note: Some leftovers may be present. If you find any please let me know.
•Rooted- SuperSu is included.
•Up to 10gb+ of internal storage is available. This number will change depending on what you install afterwards, and what you have already stored on your internal SD.
Instructions:
1. Download the ROM from here.
2. Download GoogleKeyboard. You will need this after installation because the Samsung keyboard has been removed.
3. Make sure both files are on your internal, or external storage. Either is fine.
4. Reboot to recovery and wipe, data, system, cache, & dalvik cache.
5. Install Spacesung.
6. Reboot and wait. SuperSU will cause it to boot loop once. This is just root sinking it's teeth into the system. Don't interrupt it. After the aforementioned loop, it'll take about ~5-8min to start up. This only applies to the very first boot. Afterwards it only takes ~10 seconds to startup.
7. Skip all the setup steps that require typing. This can be done after you install GoogleKeyboard.
8. Enjoy!
Special notes:
*Google play, and Google services are still installed. You can disable both if you want to. You must disable it as a device administrator under the security options first, or it will be grayed out.
*Syncing will not work, since it has also been removed.
*Device encryption and secure storage shouldn't work either.
*Chrome is still installed. It can also disabled. There is no way to remove it yet, as the 7.0 framework uses it for webview. I'm still searching for a workaround to save more space.
*Anything not listed, should be working perfectly. If something is broken, let me know. And please remember, that anything already listed is not a bug, it is intentional. If you have any issues with 3rd party apps, I will try to help you, though I make no promises.
New!: Spacesung Oreo Debloat ScriptNotes:
1. Flash in recovery after the first boot.
2. Wipe dalvik cache ONLY! (Oreo cleans up data from removed apps automagically after rebooting.)
3. Profit!
*If you want to modify what's removed, simply open the updater-script with a text editor (preferably Notepad++) and add or remove the # sign. All apps in the stock Oreo system are listed in alphabetical order. This script should be safe to flash as is. Touchwiz, Theme store, Google play, and Samsung keyboard, are not removed by default. No files will be added to your OS either.
Ex.
delete_recursive("/system/app/AmazonMP3"); ← This would be deleted. #delete_recursive("/system/app/AmazonMP3"); ← This would be ignored.
*As always, anything that I make is free to use for other projects, public or personal, without my permission. No need to ask me, just do it! Credit is always appreciated, though not required.
J727P
Spaceminer said:
SpacesungGalaxy J727P
(J727PVPU3ARC2)Disclaimer:
I am not responsible for what you do with your device. If you decide to flash this software then you are accepting any risks involved. Including, but not limited to; bricking your device, missing alarms, missing calls, loss of your job, repossession of your car, and maybe even spilt milk.
About:
This is very much a personal project that I felt others would appreciate. I enjoy retro gaming very much, and as some of you may know, emulation is very CPU intensive. Hence the reason for making Spacesung. My goal was a stock rom that was lag free, debloated, and buttery smooth for gaming. I believe I have achieved this, and so, I give this to the you, to enjoy, use, modify, and share at your discretion.
Features
•Deodexed
•Debloated- I have removed all unnecessary Samsung, Google, and Amazon apps.
•Removed all Amazon symlinks. (Libs are next.)
•Deknoxed- Note: Some leftovers may be present. If you find any please let me know.
•Rooted- SuperSu is included.
•Up to 10gb+ of internal storage is available. This number will change depending on what you install afterwards, and what you have already stored on your internal SD.
Instructions:
1. Download the ROM from here.
2. Download GoogleKeyboard. You will need this after installation because the Samsung keyboard has been removed.
3. Make sure both files are on your internal, or external storage. Either is fine.
4. Reboot to recovery and wipe, data, system, cache, & dalvik cache.
5. Install Spacesung.
6. Reboot and wait. SuperSU will cause it to boot loop once. This is just root sinking it's teeth into the system. Don't interrupt it. After the aforementioned loop, it'll take about ~5-8min to start up. This only applies to the very first boot. Afterwards it only takes ~10 seconds to startup.
7. Skip all the setup steps that require typing. This can be done after you install GoogleKeyboard.
8. Enjoy!
Special notes:
*Google play, and Google services are still installed. You can disable both if you want to. You must disable it as a device administrator under the security options first, or it will be grayed out.
*Syncing will not work, since it has also been removed.
*Device encryption and secure storage shouldn't work either.
*Chrome is still installed. It can also disabled. There is no way to remove it yet, as the 7.0 framework uses it for webview. I'm still searching for a workaround to save more space.
*Anything not listed, should be working perfectly. If something is broken, let me know. And please remember, that anything already listed is not a bug, it is intentional. If you have any issues with 3rd party apps, I will try to help you, though I make no promises.
*As always, anything that I make is free to use for other projects, public or personal, without my permission. No need to ask me, just do it! Credit is always appreciated, though not required.
Click to expand...
Click to collapse
One question did you add any kernel tweaks to your build ? An why can't I find any system tweaks ? Sorry two Questions !!
peter couniaz said:
One question did you add any kernel tweaks to your build ? An why can't I find any system tweaks ? Sorry two Questions !!
Click to expand...
Click to collapse
There are no kernel tweaks. I have been trying to build a custom kernel from source for this, however, ubuntu/virtualbox are not playing nice with my hardware. (Ubuntu stops using my CPU completely after ~10min.) This is just a very bare bones stock Rom, with Trebuchet as a launcher. There are no special system tweaks added to it. Regarding that topic, I am working on tethering, it has been very difficult though. Samsung's smali files are a huge mess to work with. I can get the "you are not subscribed to this service" notification to stop, but tethering still won't start. Are you missing any options that would normally be available on stock? If so, I would definitely like to fix that ASAP.
J727P
Spaceminer said:
There are no kernel tweaks. I have been trying to build a custom kernel from source for this, however, ubuntu/virtualbox are not playing nice with my hardware. (Ubuntu stops using my CPU completely after ~10min.) This is just a very bare bones stock Rom, with Trebuchet as a launcher. There are no special system tweaks added to it. Regarding that topic, I am working on tethering, it has been very difficult though. Samsung's smali files are a huge mess to work with. I can get the "you are not subscribed to this service" notification to stop, but tethering still won't start. Are you missing any options that would normally be available on stock? If so, I would definitely like to fix that ASAP.
Click to expand...
Click to collapse
Thank you for getting back to me an good luck with your build on a custom kernel for this phone we can really use one !! Thanks again !
Spaceminer said:
SpacesungGalaxy J727P
(J727PVPU3ARC2)Disclaimer:
I am not responsible for what you do with your device. If you decide to flash this software then you are accepting any risks involved. Including, but not limited to; bricking your device, missing alarms, missing calls, loss of your job, repossession of your car, and maybe even spilt milk.
About:
This is very much a personal project that I felt others would appreciate. I enjoy retro gaming very much, and as some of you may know, emulation is very CPU intensive. Hence the reason for making Spacesung. My goal was a stock rom that was lag free, debloated, and buttery smooth for gaming. I believe I have achieved this, and so, I give this to the you, to enjoy, use, modify, and share at your discretion.
Features
•Deodexed
•Debloated- I have removed all unnecessary Samsung, Google, and Amazon apps.
•Removed all Amazon symlinks. (Libs are next.)
•Deknoxed- Note: Some leftovers may be present. If you find any please let me know.
•Rooted- SuperSu is included.
•Up to 10gb+ of internal storage is available. This number will change depending on what you install afterwards, and what you have already stored on your internal SD.
Instructions:
1. Download the ROM from here.
2. Download GoogleKeyboard. You will need this after installation because the Samsung keyboard has been removed.
3. Make sure both files are on your internal, or external storage. Either is fine.
4. Reboot to recovery and wipe, data, system, cache, & dalvik cache.
5. Install Spacesung.
6. Reboot and wait. SuperSU will cause it to boot loop once. This is just root sinking it's teeth into the system. Don't interrupt it. After the aforementioned loop, it'll take about ~5-8min to start up. This only applies to the very first boot. Afterwards it only takes ~10 seconds to startup.
7. Skip all the setup steps that require typing. This can be done after you install GoogleKeyboard.
8. Enjoy!
Special notes:
*Google play, and Google services are still installed. You can disable both if you want to. You must disable it as a device administrator under the security options first, or it will be grayed out.
*Syncing will not work, since it has also been removed.
*Device encryption and secure storage shouldn't work either.
*Chrome is still installed. It can also disabled. There is no way to remove it yet, as the 7.0 framework uses it for webview. I'm still searching for a workaround to save more space.
*Anything not listed, should be working perfectly. If something is broken, let me know. And please remember, that anything already listed is not a bug, it is intentional. If you have any issues with 3rd party apps, I will try to help you, though I make no promises.
*As always, anything that I make is free to use for other projects, public or personal, without my permission. No need to ask me, just do it! Credit is always appreciated, though not required.
Click to expand...
Click to collapse
Downloaded and installed nicely. Tried to switch superuser with magisk but no go, need stock boot image but all in all a good clean debloated Rom. You should include a keyboard though, your link did not work so I downloaded one on my PC and transferred to internal sd and installed. If you can get magisk instead of superuser, you will have a winner !
Sent from my SM-J727P using Tapatalk
J727P
Spaceminer said:
SpacesungGalaxy J727P
(J727PVPU3ARC2)Disclaimer:
I am not responsible for what you do with your device. If you decide to flash this software then you are accepting any risks involved. Including, but not limited to; bricking your device, missing alarms, missing calls, loss of your job, repossession of your car, and maybe even spilt milk.
About:
This is very much a personal project that I felt others would appreciate. I enjoy retro gaming very much, and as some of you may know, emulation is very CPU intensive. Hence the reason for making Spacesung. My goal was a stock rom that was lag free, debloated, and buttery smooth for gaming. I believe I have achieved this, and so, I give this to the you, to enjoy, use, modify, and share at your discretion.
Features
•Deodexed
•Debloated- I have removed all unnecessary Samsung, Google, and Amazon apps.
•Removed all Amazon symlinks. (Libs are next.)
•Deknoxed- Note: Some leftovers may be present. If you find any please let me know.
•Rooted- SuperSu is included.
•Up to 10gb+ of internal storage is available. This number will change depending on what you install afterwards, and what you have already stored on your internal SD.
Instructions:
1. Download the ROM from here.
2. Download GoogleKeyboard. You will need this after installation because the Samsung keyboard has been removed.
3. Make sure both files are on your internal, or external storage. Either is fine.
4. Reboot to recovery and wipe, data, system, cache, & dalvik cache.
5. Install Spacesung.
6. Reboot and wait. SuperSU will cause it to boot loop once. This is just root sinking it's teeth into the system. Don't interrupt it. After the aforementioned loop, it'll take about ~5-8min to start up. This only applies to the very first boot. Afterwards it only takes ~10 seconds to startup.
7. Skip all the setup steps that require typing. This can be done after you install GoogleKeyboard.
8. Enjoy!
Special notes:
*Google play, and Google services are still installed. You can disable both if you want to. You must disable it as a device administrator under the security options first, or it will be grayed out.
*Syncing will not work, since it has also been removed.
*Device encryption and secure storage shouldn't work either.
*Chrome is still installed. It can also disabled. There is no way to remove it yet, as the 7.0 framework uses it for webview. I'm still searching for a workaround to save more space.
*Anything not listed, should be working perfectly. If something is broken, let me know. And please remember, that anything already listed is not a bug, it is intentional. If you have any issues with 3rd party apps, I will try to help you, though I make no promises.
*As always, anything that I make is free to use for other projects, public or personal, without my permission. No need to ask me, just do it! Credit is always appreciated, though not required.
Click to expand...
Click to collapse
You may want to try this Build I Built on TomeGJ7p's WIFI BUILD it's a good one I THINK YOU WILL LIKE IT !
https://mega.nz/#!aUlU3CiD!QERLRerFDA8497aKopbqZqZh-ZSTVfZ9GhfQQy2mBrs
PS if you like it you can use it to Build on you have mine an tomeGJ7p's Blessing !!
Spaceminer said:
There are no kernel tweaks. I have been trying to build a custom kernel from source for this, however, ubuntu/virtualbox are not playing nice with my hardware. (Ubuntu stops using my CPU completely after ~10min.) This is just a very bare bones stock Rom, with Trebuchet as a launcher. There are no special system tweaks added to it. Regarding that topic, I am working on tethering, it has been very difficult though. Samsung's smali files are a huge mess to work with. I can get the "you are not subscribed to this service" notification to stop, but tethering still won't start. Are you missing any options that would normally be available on stock? If so, I would definitely like to fix that ASAP.
Click to expand...
Click to collapse
This ROM is totally debloated. I went back and tried it again, very smooth, very fast but Contacts would not sync so I could not call anyone. Google account would not sync so no play store apk update from old account.Samsung account missing so no way for me to bring certain apks and utilities from stock ROM. Bare-bones android op. But I will keep it on my sd card.
PS
I just remembered those system apks that are missing that I need, I could have installed thru Titanium Bkup! [emoji846]
Sent from my SM-J727P using Tapatalk
is there anyway you can upload a copy with sync enabled and would it be possible to also use a modified or even stock touchwiz launcher?? and Magisk... If I could have sync magisk and touchwiz Id run this as my daily driver
JeepinxJosh said:
is there anyway you can upload a copy with sync enabled and would it be possible to also use a modified or even stock touchwiz launcher?? and Magisk... If I could have sync magisk and touchwiz Id run this as my daily driver
Click to expand...
Click to collapse
You can flash gapps for sync, I don't have the sync apps on hand or I would attach them. I've flashed pico without issue. I forget which one(s) has the sync apps, it's possible that all of them do. Magisk can be installed fairly easily. Grab Magisk v16. Open SuperSU, look in settings and choose full unroot. Select yes when asked to restore the stock boot image, and no to recovery. As soon as it reboots, hold Vol↑+Home to catch TWRP, then flash Magisk. As for Touchwiz, try installing the one in the attachments below. If it gives you any problems, let me know. If I update anything I will definitely be using Magisk, and I'll keep these options in mind for separate builds in the future.
Spaceminer said:
You can flash gapps for sync, I don't have the sync apps on hand or I would attach them. I've flashed pico without issue. I forget which one(s) has the sync apps, it's possible that all of them do. Magisk can be installed fairly easily. Grab Magisk v16. Open SuperSU, look in settings and choose full unroot. Select yes when asked to restore the stock boot image, and no to recovery. As soon as it reboots, hold Vol↑+Home to catch TWRP, then flash Magisk. As for Touchwiz, try installing the one in the attachments below. If it gives you any problems, let me know. If I update anything I will definitely be using Magisk, and I'll keep these options in mind for separate builds in the future.
Click to expand...
Click to collapse
Thanks man
I used this rom as the base for my gaming phone and then stripped it down to only system framework apps. If the latter were removed it would crash the phone. Anything I removed to get to that point, had minimal impact on space (fifty or so megs) and bootup times compared to a fully loaded phone (5 seconds). Spaceminer did an excellent job on this.
Video here of bootup comparison between two Galaxy J7 Perx, one with the Spacesung rom:
https://www.youtube.com/watch?time_continue=2&v=z9bcqwLVIAA
Is the Oreo stock ROM a battery chugger?
It's just me or anybody have experienced less stamina from their battery with the Oreo stock ROM even with all the de-bloat applied. Compared to the latest ARG2 Nougat it's almost halves the lifetime of the battery, even when on standby it consume a lot more.
ct760ster said:
It's just me or anybody have experienced less stamina from their battery with the Oreo stock ROM even with all the de-bloat applied. Compared to the latest ARG2 Nougat it's almost halves the lifetime of the battery, even when on standby it consume a lot more.
Click to expand...
Click to collapse
Have you tried turning off all the scanning features? Also in the dev options, the switch that keeps mobile data always on, is enabled by default. It's normally off in Nougat. Turning that off should help tremendously.
That being said, I do think Oreo is a battery hog, and I don't think there's any performance gain over Nougat. My best benchmarks with this phone are running Nougat (ARG2), debloated. My battery gives me 51-52hrs on Nougat, with 17-18hrs of that being screen on time. I plan on running Oreo this week to get a good comparison between them.
A word ahead, I am far away from beeing an expert. I read and tested a lot, but can't answer all your question.
Instead this thread is intended to share experiences as I spend quit some days to become my phone as free from Google.
I did this on a Galaxy A3 (2017) with LOS.
First of course is not to install Gapps. We can replace many of its functionality. First of all we need a store to download apps. I highly recommend FDroid as a first choise. You can download the app at their website.
With this you get a variety of apps for almost all, but not all problems. Nevertheless I recommend to take your time and check what is offered there, even if you used other apps before.
If you don't find an equivalent, you might want access the google playstore. In FDroid there are two apps available for this purpose. With both you can anonymously access all (not payed) apps on Playstore. You can of course login with your google accound, but ... ok, that's not so anonymous anymore
What else do we miss without Gapps. There is a way of receiving push notifications, that is often handled via GCM (google cloud messanging).
First of all we need to enable spoofing. This was quite a challange, as usual tools (tingle, ...) work with non-odexed ROMS, while that for A3 is an odexed ROM.
Finally I found a zip here, that works for me:
https://forum.xda-developers.com/showpost.php?p=77456471&postcount=3775
Download that zip, goto TWRP.
Before installing it you have to do two steps.
Mount /system
Create a link (with advanced/terminal): ln -s /system/vendor /vendor
Otherwise install of this zip will fails. Be patient, it takes around 5..10min to pass.
Now we can work with microG, that will replace some google-APIs.
Add the repo "microg.org/fdroid/repo"
Then install micoG core, fakestore and proxy.
To get unifiedNLP running (this is for location services) the microG core must be a system app.
So do a reboot in the TWRP. Mount system first.
Than copy with integrated filemanager the folder com.google.android.gms-xxxx
from /data/app/
to
/system/priv-app
and reboot.
You will find in your app-overview the microG app - please open and let selftest run.
Enable permissions there and also disable battery optimisation
unifiedNlp should be registered. Next is to enable them.
Download from FDroid these two apps:
Local GSM Location (with this you can download a database of cell towers and their location, giving you a chance to get a rough estaimatin where you are, without waste of energy for GPS)
and
NominatimNlpBackend (to get your position as street/city/country instead of coordinates).
Very important:
Apps that require this gapps need to be installed after microG. Otherwise they will not work properly.
I guess that are usually apps that needs location.
Feedback for microG installation
I´ve tested your microG installation these days. Worked like a charm ! Thanks for your post.
The Nanodroid patcher referred in your link was gone, so i used http://downloads.nanolx.org/NanoDroid/Stable/NanoDroid-patcher-18.1.20180909.zip.
I had the same problems with Yalp downloads you´ve described earlier, after reboot it worked.
GCM works, but just not with Threema ;-( But it´s a known problem.
Getting NLP to work was a little bit of hassle, but I found many articles about it. Was not sure which of the backends to use, there are many.
What is interesting - I didn´t use encryption and patched the ashyx_no_encryption patch right after flashing LOS and I didn´t use SU or Magisk right now. Result: absolutely no boot loops and no reboot after power off !
From which stock variant you came ?
@cyberbix:
The patcher for spoofing was quite beta at that time. Did you have to do any preparations to let it run? I remember in TWRP I had to mount /system and create that /vendor-link. Is it still required? I reported my issued there but I am not sure he cooked it with these patches finally.
The Yalp issue is completely independent on microG. It seems that there is a bug in the Downloader of LOS15.1. There are others suffered from this issue, not just the A320FL. The workaround to use internal download works.
Can you give more details about the NLP-hassle? That might help others to not go that painful way. Imho all is fine if you copy (or move) the folder I described above and reboot.
About the backends ... I think there is no alternative for Nominatim, which works only online. For the cell bases location I prefer a offline solution, I found that "Local GSM Location". The microG-Packages usually contain the mozilla-online backend.
BTW: Did you use one of the zip-packages to install microGSMcore, fakestore, GsfProxy ... or manually via FDroid as I did?
I had latest Oreo 8.0 installed before. But I am not sure whether or not I updated the bootloader too with Odin.
@starbright_
Did you have to do any preparations to let it run?
Yes. I did exactly the same as you did in TWRP.
Can you give more details about the NLP-hassle?
I wasn´t sure if its needed at all and even if microG went green, the backends seemed not wo work at all.
BTW: Did you use one of the zip-packages to install microGSMcore, fakestore, GsfProxy ... or manually via FDroid as I did?
I did it in the same way as you. Flashed the patcher, installed the rest from FDroid. That´s it.
Moreover: i didn´t install Magisk or any other root and I didn´t use Xposed. I used the push notification tester to test GCM. Everything was fine.
I can check if installing an su package or Magisk will lead into the same problems.
Installed Magisk on top of your microG setup. Everything works, see McFys thread. I guess you just didn´t read what TB tells about SU.
starbright_ said:
A word ahead, I am far away from beeing an expert. I read and tested a lot, but can't answer all your question..
Click to expand...
Click to collapse
My experience below:
-LOS by McFy with Magisk+Xposed+nanodroid
- installed only. MicroG package +all backends+yalp
- the self check is good except the last box which is noto green
-yalp works fine, i like it, but in the end i had to use my goggole account instread of the experimental 'internal account' and this because of gmaps
-gmaps works fine BUT it doesn't find the current gps position unless i restart it (long press on back arrow). This is odd because other map-apps (openstreet, tomtom..) work! Also, when i need to use the google account to save some locations or simply the offline maps, it does work only for the first time, later it doesn't recognize my (already set) googke account
-i don't know if it's related to microg but camera doesnt find the gps, while opencamera yes, fotej camera neither
-again, i don't know if it's related to microg but each time i add the google account i loose my contact list
-apps that need to talk with playstore doesn't work at all, I wanted to use Europe3D by geoflier and it didn't load properly until i installed also the playstore
- the same for those apps that need to purchase some addons
-BUT worst, above all (crying) is that the speechTotext is not wotking and it's a feature I really miss!
I don't know if a proper patched rom would work better, I always hope that mcFy finds some time to release the rom already patched.
Anyhow next days I will try to reinstall the stock rom to see if these behavioours happen also there.
I did another installation again. More details next.
But finally I gave up. I couldn't solve two issues
- neither telegram nor whatsapp works after a few minutes (doesn't wake up at incoming calls)
- heavy instabilities with LOS15.1/Magisk/Xposed/microG
I didn't find which component is responsible for that, but I remember that I didn't always get SU with Magisk. After a reboot it works again.
Even such components as DuckDuckbrowser crashed.
I couldn't recover my apps backup by TB from my previous S5mini on A3 with TB and Magisk (Parser error).
I need a rest from all this stuff.
starbright_ said:
I
I need a rest from all this stuff.
Click to expand...
Click to collapse
it took it some days and many reinstallations before i found out the right sequence!
i think everything related to microg is stable enough except what i wrote before
pink0 said:
it took it some days and many reinstallations before i found out the right sequence!
i think everything related to microg is stable enough except what i wrote before
Click to expand...
Click to collapse
So what is the sequence? This:
"-LOS by McFy with Magisk+Xposed+nanodroid
- installed only. MicroG package +all backends+yalp
- the self check is good except the last box which is noto green"
And it is stable for you? Never get problems with not granted root?
What is last box: cell based location? Same for me... But I am not sure what exactly means this.
I installed localGSMbackend which created an offline database with celltowers. This works fine in energy saving mode I get a rough position without any waste of energy or privacy (as offline).
Altogether I did at least 20 complete wipes and started from scratch.
At the first I started early with root (either Magisk or LOS-addsu).
Than there are two options to get a spoofed ROM.
Either via Xposed/Fakestore module or via nanodroid patcher.
Both works in general.
Than installed microG (different ways - manually, nanodroid, unofficial installer, that are the 3 options I know).
But it always become instable. Apps don't get root anymore or does FC ....
So I did it another way around.
I first installed all required via FDroid (without any root, Xposed ...). That seems to me rather stable. The good thing: this are around 80% or apps I need. Than I did a backup, so that I don't have to starts from scratch, which is painful as hell with around 40 .. 60 apps.
My last attempt was after that install Magisk, Xposed, Fakestore. Spoofingchecker was red, but a microG gets green.
I installed it with nanodroid (created first with setup wizard a file, so that only microG and mapsapiv1) gets installed.
This was first time my apps work fine with maps. Other attempts to manually install the maps framework/lib wasn't succesful (why ever).
Problems started when installing TB. First it doesn't get root permission. After a restart it works, but I get parsing errors. If I understand FAQ this is due to different busyboxes ?!? Ok, the backups I created at another device with LOS14.1 and addsu.
But this was not the only issue. Browser crashed and I never get neither Telegram nor Whatsapp to get wake up after a few minutes of deep sleep (they arn't get registered at microG too, so this might be another issue).
@pink0:
Did I understand it right, you use GMaps?
@cyberbix:
My problems with whatsapp and telegram (not registering in GCM) - did you found a way, maybe with an older version of whatsapp?
Does your system keeps stable after all?
To be honest, that Magisk and Xposed seems to add to much intrusive stuff that might fail altogether. But even with the manual way it wasn't perfect. Maybe after a rest and with the next version from McFy I try this again. Good luck I didn't sell my old S5min til now.
starbright_ said:
So what is the sequence? This:
"-LOS by McFy with Magisk+Xposed+nanodroid
- installed only. MicroG package +all backends+yalp
- the self check is good except the last box which is noto green"
And it is stable for you? Never get problems with not granted root?
What is last box: cell based location? Same for me... But I am not sure what exactly means
@pink0:
Did I understand it right, you use GMaps?.
Click to expand...
Click to collapse
it's here i writed down because my personal memory buffer, at my age, is really small
yes gmaps is working quite good except the behavour I wrote, but enabling developer options I can easily kill the program to get the new/current position (also I noriced tgat because of this gps problem ir cannot calculate any route while navigating)
I also dislike the idea of using xposed bexause I never needed it but now it's different
about telegram/whatsup i'm not using such softwae so I can't say what's wrong
starbright_ said:
...My problems with whatsapp and telegram (not registering in GCM) - did you found a way, maybe with an older version of whatsapp?
Click to expand...
Click to collapse
I do not use WhatsApp, I use Threema and Threema has known problems with microG GCM.
starbright_ said:
Does your system keeps stable after all?
Click to expand...
Click to collapse
Yes, but I didn´t flash Xposed, just Magisk.
Ok.That spoofing can happen via Xposed Module or nanodroid patcher. For non-odexed ROMs are more options (tingle,...) but not for ours.
So after all I am now happy with my current installation:
- install TWRP via ODIN
- Wipe in TWRP (system, data, cache, dalvik)
- install Lineage via TWRP
- boot into system
- install FDroid
install and setup most of needed apps - there is a good selection of apps in FDroid now
- Create Backup (via TWRP)
- Install Magisk (viaTWRP) and Magisk Manager in LOS
- Setup adaware and afwall (both from FDroid as they need root)
- Installing microG (via TWRP) with packets from here:
https://forum.xda-developers.com/apps/magisk/module-nanomod-5-0-20170405-microg-t3584928
( use patcher for spoofing the ROM, setup to create a control file and than a minimal setup with microG, maps-api, FakeStore).
- install Yalp from FDroid and via Yalp the missing apps that are not available via FDroid.
I found that Telegram (and Whatsapp not 100% sure yet) push-notification work. I disabled battery optimization for both.
starbright_ said:
So after all I am now happy with my current installation:
[...snip..]
- Installing microG (via TWRP) with packets from here:
https://forum.xda-developers.com/apps/magisk/module-nanomod-5-0-20170405-microg-t3584928
( use patcher for spoofing the ROM, setup to create a control file and than a minimal setup with microG, maps-api, FakeStore).
Click to expand...
Click to collapse
thanks for your post!
- did you run the nanodroid patcher itself or you deodexed tje rom by hand?
- do you notice any difference between a magisk-through instlation of nanodroid and a direct one?
- which build of LOS are you using?
pink0 said:
thanks for your post!
- did you run the nanodroid patcher itself or you deodexed tje rom by hand?
- do you notice any difference between a magisk-through instlation of nanodroid and a direct one?
- which build of LOS are you using?
Click to expand...
Click to collapse
I am not sure, but the LOS15.1 for A3 2017 (by @McFy from 08/21) ROM is in a state you need the patcher. Other methods (as tingle - what I used before with other mobiles) don't work.
Not sure what is odexed and deodexed. The only other method works for spoofing is Xposed framework. There is a module that fakes this. But until now I did't see a need for Xposed and I don't want to increase complexity. (From that point of view I rather should go for addsu instead of Magisk)
I did first a Magisk installation, as root is more important and you have later the chance to chose between microG and Gapps. (Did it step by step with backups not to start again from scratch).
But I didn't use Magisk for installation, but TWRP. How does it works? I am a Magisk newbee.
An update of LOS15 requires to redo it. I also updated microG in this sequence. Just as a short summery:
- boot into TWRP
- wipes system/cache/dalvik
- installed new LOS
- installed Magisk
- reboot into system (just for curiosity, probably not required) and back to TWRP
- let run uninstaller of microG (I used the zips from here: https://forum.xda-developers.com/apps/magisk/module-nanomod-5-0-20170405-microg-t3584928)
- install (run) the patcher (be patients, that takes long time, maybe 15min)
- install (run) setup wizard (selected only few things, as maps-api, can remember exactly)
- install the real package (install what has been selected in setup).
check this out https://hackernoon.com/e-first-beta-soon-to-be-released-82d7ec950dd
basically, this is a LOS-based rom including microG, aiming at avoiding google applications/usage.
or https://download.lineage.microg.org/a5y17lte/
Nominatim backend
Has anyone using microG got the NominatimGeocoderBackend to work ? On the LOS15 or on LOS16 builds of McFy ? With Nanodroid or with microG core setup ?
The Self-Check in the microG Settings app on the LOS16-microG-build-20190412 with Nanodroid 20190310 from McFY fails the self-test "UnifiedNlp do not have Location to test Geocoder"
The NominatimGeocoderBackend is installed, activated and configured for OSM.
No big deal, everything else works fine.
cyberbix said:
Has anyone using microG got the NominatimGeocoderBackend to work ? On the LOS15 or on LOS16 builds of McFy ? With Nanodroid or with microG core setup ?
The Self-Check in the microG Settings app on the LOS16-microG-build-20190412 with Nanodroid 20190310 from McFY fails the self-test "UnifiedNlp do not have Location to test Geocoder"
The NominatimGeocoderBackend is installed, activated and configured for OSM.
No big deal, everything else works fine.
Click to expand...
Click to collapse
My selfcheck gives just 2 unchecked points:
Playstore signature (I installed Fakestore+Yalp and Fdroid)
Radiocell based location (altough Nominatem is setup).
"Playstore signature" I could manage after apply permission spoofing to Fake Store (system app).
But, I don't get any app registered, although I have enabled Google registration and GCM.
I even deinstalled ebay and installed it again - no effect. ?!? What can I do?
I remember @cyberbix mentioned the Push notification tester:
It fails for me with step1 - "No register" ?!? How can that be? What did I miss.
[/COLOR]
starbright_ said:
?!? How can that be? What did I miss.
Click to expand...
Click to collapse
Did you do the device check-in ?
See https://f-droid.org/en/packages/com.thermatk.android.xf.fakegapps/
What is push notifcation exactly claiming ? Unable to register or missing Play services ?
I just tried to flash open gapps 6/4/2020 stock for version 9 arm64, after I wiped cache and dalvik and rebooted all my gapps were gone but google pay was showing. I could see all the others were installed looking in system apps though. Trying to run google pay produced an error, see attached. Play services version seems to be broken? Help?
Confirmed, definitely broken. Logs attached. If anyone finds anyone in the open gapps project that actually cares feel free to let them know but from my past experiences it looks like open gapps stock is now over for 9. Might try a larger package, I'll post here if I do and it solves the problem.
Update: The Super package has the same issue.
There are other GAPPS like Nik GAPPS.
ChazzMatt said:
There are other GAPPS like Nik GAPPS.
Click to expand...
Click to collapse
True, but that's another set of issues, and wouldn't I have to get Open Gapps off first?
callihn said:
True, but that's another set of issues, and wouldn't I have to get Open Gapps off first?
Click to expand...
Click to collapse
Yes, but let's back up a step...
What LOS custom ROM do you have installed, for which you need GAPPS?
Just want to make sure we're all on the same page.
LOS-16 and LOS-17 need different GAPPS and of course stock firmware doesn't use GAPPS.
ChazzMatt said:
Yes, but let's back up a step...
What LOS custom ROM do you have installed, for which you need GAPPS?
Just want to make sure we're all on the same page.
LOS-16 and LOS-17 need different GAPPS and of course stock firmware doesn't use GAPPS.
Click to expand...
Click to collapse
Of course stock uses gapps, unless you like wasting your storage to hold the updates and then having to re-update if you land up having to restore or do a factory reset, been doing it since Gingerbread and it works great, or it did, although the majority of updates can easily be moved to the system using Link2SD I have yet to find any realible means to move play services to the system without breaking things which is a major headache, gapps solves that issue and also allows me to choose which apps I want included in a rooted stock rom. The reality is that custom/non-stock ROMs are generally broken in one way or the other and more often than not it's just not something I'm willing to deal with, in addition there's useally too much junk included that I just have no need for and if I did I'd change my stock rooted ROM to fulfill that need. I've actually never seen a stock ROM that didn't use gapps. I'm perfectly happy with rooted and reasonably de-bloated stock and change things I feel are needed, for example adding in call recording, most custom ROMs would actually leave me doing more work to take things out and put things back in, like why take out the native sms, clock, calculator, calender, keyboard etc. they work, they are free and ad free, they are useally small and thus not really bloat and they are often hard to replace with similar function anywhere near their size.
callihn said:
Of course stock uses gapps, unless you like wasting your storage to hold the updates and then having to re-update if you land up having to restore or do a factory reset, been doing it since Gingerbread and it works great, or it did, although the majority of updates can easily be moved to the system using Link2SD I have yet to find any realible means to move play services to the system without breaking things which is a major headache, gapps solves that issue and also allows me to choose which apps I want included in a rooted stock rom. The reality is that custom/non-stock ROMs are generally broken in one way or the other and more often than not it's just not something I'm willing to deal with, in addition there's useally too much junk included that I just have no need for and if I did I'd change my stock rooted ROM to fulfill that need. I've actually never seen a stock ROM that didn't use gapps. I'm perfectly happy with rooted and reasonably de-bloated stock and change things I feel are needed, for example adding in call recording, most custom ROMs would actually leave me doing more work to take things out and put things back in, like why take out the native sms, clock, calculator, calender, keyboard etc. they work, they are free and ad free, they are useally small and thus not really bloat and they are often hard to replace with similar function anywhere near their size.
Click to expand...
Click to collapse
No, you never flash custom ROM GAPPS on STOCK firmware. It already has built in GAPPS. GAPPS are usually only for LOS/AOSP custom ROM, not even stock based custom ROM. So there's your problem.
If you want to do it, go ahead, but I just know what I've been told by several devs.
When I read your question again, it seemed strange the way the wrote it, so that's why I wanted to clarify.
ChazzMatt said:
No, you never flash custom ROM GAPPS on STOCK firmware. It already has built in GAPPS. GAPPS are usually only for LOS/AOSP custom ROM, not even stock based custom ROM. So there's your problem.
If you want to do it, go ahead, but I just know what I've been told by several devs.
When I read your question again, it seemed strange the way the wrote it, so that's why I wanted to clarify.
Click to expand...
Click to collapse
No my problem is that suddenly play services in Open Gapps does not work, worked fine until this flash. Open Gapps is just Gapps, all versions should be the same as released by Google, as stated I've been doing it since Gingerbread and the only issues it's ever caused is when Open Gapps is broken as mentioned in the first post and photos has also been broken for awhile now as it no longer runs in system/app so I install that from play store and move that myself with Link2SD which puts it in system/priv-app where it works. Not sure which question you are referring to, Open Gapps is broken currently and it's my understanding that all Gapps have to be removed to switch to any other and then there's the learning curve that will come with it. If I had the time I'd just create and maintain a package for just core that wouldn't touch the rest. That will likely become a necessity in the future at the rate things are going. So yes, after all these years I'll continue doing it since it's proven to work, assuming it ever gets fixed though I doubt it will as photos has yet to be fixed and that just requires a change in the install script.
callihn said:
No my problem is that suddenly play services in Open Gapps does not work, worked fine until this flash. Open Gapps is just Gapps, all versions should be the same as released by Google, as stated I've been doing it since Gingerbread and the only issues it's ever caused is when Open Gapps is broken as mentioned in the first post and photos has also been broken for awhile now as it no longer runs in system/app so I install that from play store and move that myself with Link2SD which puts it in system/priv-app where it works. Not sure which question you are referring to, Open Gapps is broken currently and it's my understanding that all Gapps have to be removed to switch to any other and then there's the learning curve that will come with it. If I had the time I'd just create and maintain a package for just core that wouldn't touch the rest. That will likely become a necessity in the future at the rate things are going. So yes, after all these years I'll continue doing it since it's proven to work, assuming it ever gets fixed though I doubt it will as photos has yet to be fixed and that just requires a change in the install script.
Click to expand...
Click to collapse
How long have you owned the V30?
You'll need to factory reset the phone to remove the extraneous GAPPS you installed when stock firmware has GAPPS and different resolution versions of the apps.
You still haven't explained why you need gapps on stock firmware. Every V30 dev who creates a stock firmware ROM says do not install GAPPS.
From Aeron Li, the A.IS. and A.I.X. (stock firmware based ROM) dev, who says NOT to do what you are trying to do:
the bad thing is that he can flash/install mismatched gapps and that may make firmware work wrong, or even make safetynet issues and not working Gapps-related things
Click to expand...
Click to collapse
Boombox dev (another stock ROM) and JohnFawkes one of the devs who create the TWRP flashable zips has said not to flash GAPPS over stock firmware.
You're probably going to cause conflicts. But it's your phone.
ChazzMatt said:
How long have you owned the V30?
You'll need to factory reset the phone to remove the extraneous GAPPS you installed when stock firmware has GAPPS and different resolution versions of the apps.
You still haven't explained why you need gapps on stock firmware. Every V30 dev who creates a stock firmware ROM says do not install GAPPS.
From Aeron Li, the A.IS. and A.I.X. (stock firmware based ROM) dev, who says NOT to do what you are trying to do:
Boombox dev (another stock ROM) and JohnFawkes one of the devs who create the TWRP flashable zips has said not to flash GAPPS over stock firmware.
You're probably going to cause conflicts. But it's your phone.
Click to expand...
Click to collapse
I dunno never had any issues and flashed open gapps a few weeks ago, 20200513 to be exact on this phone, no issues. Actually it was explained in detail. Updates take up space, wiping data removes them and hence bandwidth and time is wasted. Moving updates into system saves space and bandwidth. Again I don't do anyone's ROMs I use stock and make the few changes I desire. The only real issue that requires it is moving play services to the system since everything else is movable using Link2SD.