Hi friends,
Background: I have DirecTV Streaming Service for my home because it offers 5.1 surround.
I HAD their mobile app on my Sprint Note 4 but before Sprint was purchased by T-Mo I was prompted to update the app in the Play Store.
When I tried a dialog popped up saying that my Android 6 Marshmallow phone was no longer compatible and that DirecTV Stream now required Android 7, Android 8 recommended.
If I successfully flash an OREO 8.1 ROM will the Play Store permit me to update my app or will they see that I am a Note 4 and deny me ?
And although YTTV/Hulu etc apps still work on Marshmallow they have poor audio for my home surround system .
No, it will only see the actual version of Android.
I actually flashed CRDROID Oreo 8.1 and was then able to download the latest apk from the playstore.
Installed and ran perfectly...
BUT, my WIFI connection repeatedly disconnected.
So did my bluetooth.
And my S-Pen was neutered.
Battery life abysmal.
Also, OREO was simply baffling to me.
Nothing like the Marshmallow that I am used to.
I wish that there was a way to "spoof" my android version and APPEAR as Nougat 7.
The Note 4 itself proved that it can run the app A-OK.
When Sprint died I just assumed that the latest Samsung offering would be better than my 7 year old phone.
So I bought a brand new A52 in August 21.
$450.00 wasted.
I hate it.
Stupid aspect-ratio results in black bands while streaming.
The display IS an inch wider (in landscape mode), 6.7 inches vs 5.7 inches.
BUT, considerably shorter (in landscape mode) which translates to LESS screen area.
As a result, typing is nearly impossible on the diminished keyboard.
No replaceable battery.
No S-Pen.
Overall, a big step BACKWARD !
<rant off>
Maybe try https://forum.xda-developers.com/t/...experience-pie-trlte-tblte-trlteduos.3925885/ (PixelExperience 9)?
There are tons of roms and at least 1 will suit your needs
traman124 said:
Maybe try https://forum.xda-developers.com/t/...experience-pie-trlte-tblte-trlteduos.3925885/ (PixelExperience 9)?
There are tons of roms and at least 1 will suit your needs
Click to expand...
Click to collapse
Thanks pal...I have only flashed the OREO I mentioned so I am a very green newbie.
I have seen positive comments about Pixel so I will give it a shot.
Android 9 > 8. Any apps for 8 will work on 9 (or 10 and 11 and so on)
Hi Gang,
I thought that I'd update my results for those who are interested.
I eventually got comfortable flashing the Custom ROMs/GApps and tried many variants from 7(Nougat) up to Lineage 18.1(Android 11).
I tried a Pixel Experience package with included GApps that was very nice but on THIS particular ROM the DTVS(DirecTV Stream) APK would not install.
I suspect that the very comprehensive included GApps somehow betrayed my device's true identity.
All the other ROMs that I successfully flashed permitted the installation of the DTVS APK and it streamed flawlessy on each of them.
I do not understand why Marshmallow 6.0.1 is no longer considered sufficient.
Anyway, in the end I was really enjoying CRDroid 10 but something I had not considered made this entire exercise moot.
My home has terrible cellular reception and WIFI-Calling is indispensible for phone connnections.
What I had not realized was that WIFI-Calling is associated with each carrier's customization and cannot be incorporated into Custom ROMs as it is closely held proprietary information.
And so I have returned to the stock T-MO ROM I started out with.
Like anyone else I must be able to reliably contact emergency services for police, fire, medical, etc.
So my current solution is to leave my Mint Mobile SIM Card installed in the Note 4 while I am at home.
And if I wish to stream DTVS(via cellular) while I am out and about I must transfer the SIM to my Huawei Mate 10 which runs EMUI 12 (Android10).
It lacks WIFI Calling so it cannot be my home phone, BUT, it streams DTVS perfectly on a nice 16:9 display (no black bands on each side).
Swapping the card is a hassle but it's the best option I could think of.
I hope other users can somehow profit from my experience.
Weird. The app is not looking for the phone model; it's looking for the Android version.
Correct !
I can only assume that the model and droid version are conflated since the Note 4 was last updated in 2015 (marshmallow 6.0.1) and no further updates were/are authorized.
And so if the app sees Note 4 it can only be 6.0.1 max.
Just guessing here.
I spent alot of time studying build.prop mods to spoof my version but that never panned out.
I feel like I need to restate this: it doesn’t care if you have a note4 and limit based on that. It only limits based on version of Android.
Weird that PixelExperience didn’t work….
Lord_Ligonier said:
Correct !
I can only assume that the model and droid version are conflated since the Note 4 was last updated in 2015 (marshmallow 6.0.1) and no further updates were/are authorized.
And so if the app sees Note 4 it can only be 6.0.1 max.
Just guessing here.
I spent alot of time studying build.prop mods to spoof my version but that never panned out.
Click to expand...
Click to collapse
2016. That's when Marshmallow was released. 2015 was Lollipop
I Recently learned of a Magisk Module called "Hide Props Config"
that promises to fake my version...
How To Spoof/Fake The Android Version On Your Device
How to Spoof/Fake the Android Version on your device
In this comprehensive guide, we will show you the steps to spoof/fake the current Android version on your device to an older one.
droidwin.com
Trying to understand how this might work to make MY android version masquerede as a newer version that would permit the installation of the DTVS APK.
It appears that having rooted via Chainfire that I would need to unroot and then start over with Magisk.
Something about the stock boot.img being patched creating an obstacle to the installation.
Has anyone successfully installed Magisk while previously rooted ?
I tried and the app installs but two critical buttons are grayed out at the bottom of the app.
SU and Modules.
Anyone ???
Related
First of all, I'm new to Samsung devices. Just got the S7 Edge (Exynos variant).I know the basics to Android (I think) since I've been using Sony devices since forever. I have a few questions and while some of them may be easily answered with a quick Google search, I thought I'd just add them here in case a few of you are feeling helpful today.
1: (Optional) How does one root the S7 Edge (SM-G935FD)?
2: What are the dangers of rooting a Samsung device, specifically the S7 Edge? Are they similar to Sony devices or other Android devices?
3: Sony had a software called XperiFirm. It basically allows users to manually pull firmware updates from the servers themselves and pack them into a flashable ftf file. You can also choose which Carrier the firmware update is from. Is there something similar for Samsung devices?
4: Is there a future for our Exynos devices? I've heard that Exynos devices are near impossible to develop on (ROMs, Kernels etc). Is that true?
5: (Optional) When I use the S Health to measure my Heart Rate, it says my current profile is a Male born on January 1, 1980. How do I change it? My age is different on the Samsung account.
6: Are there any problems on the S7 Edge that I should try to avoid?
7: Lastly, if you guys can provide me some advice for this phone, be it to save battery, increase performance or any useful features I should know of, I'd appreciate it.
Sorry if these are repeated questions. Thank you all!
Edit: To add a bit of info, I haven't been active on XDA or reading any article about anything Android lately. Been really busy. So you could consider me a newbie, or a noob. Whatever you want.
Dude.... some reading would of been nice.
1: There is 1000 posts already. Just search
2: Loss in Samsung Pay. Other than that no different from any other device
3: OTA is not possibble to install. You can use Flashfire to install Updates without wiping, Allthough you are required to download the Full Firmware package and not just the Update
4: There is always a future, When Samsung Release the source code properly (AND FULLY) Then it will be possible, If not give it maybe 12 months and you will hear some news.
5: Top left corner in Shealth you can change your profile data
6: Dont put it in water or drop it LOL
7: Never tweaked Battery, Performance and battery life is outstanding on this device.
Dont touch what is not broken
1: You'll have to read on this one but it's easy and quick.
2: Loosing samsung Pay & warranty & straight OTA updates. However OTA updates are plain easy with the great work done with the app flashfire. In my case before samsung pay is used in this country I'll probably switch mobile again and warranty I don't really care, never needed a warranty since nokia gold era.
3: Answered in 1
4: It will take probably too long.. probably you will switch phone before it happens (less than 1 year) However I find the s7 rom pretty stable and low draining. Ofc I had to freeze a lot of apps and do some cleaning but along with greenify it pretty good. I usually would flash a custom ROM, now I just won't bother because they are coming out better (after the cleaning).
5: I don't use.. I use google fit.
6: Nothing that I'm aware of...
7: Out of the box the phone is pretty good. I just freeze the apps I'm sure I don't need them with titanium and use greenify. I get 6h30 screen.. I can say It's more than enough for a regular day for me... way WAY better than any previous samsung galaxy release.
Hello
Asking all developers to start a discussion on what the minimum API level is that you support, and have you decided to drop support for older APIs and if so what the reasons are. The reason for starting this discussion comes from the frustrations caused by having to support older API levels. Yes it's important to support as many users as possible - not everybody has access to the latest and greatest devices / Android versions, my own day to day device is a Samsung Galaxy S6 with Android 6.0.1. Although I have access to a device with Android 7.1 and one with Lollipop. However there is only so far back you can go in terms of support before development starts to get frustrating and in the end the question has to be asked if it is really worth it.
Please first take a look at https://developer.android.com/about/dashboards/index.html for the latest device stats.
For some background, I'm the developer of this app http://forum.xda-developers.com/android/apps-games/quick-gallery-photo-editor-t3394976 and https://play.google.com/store/apps/details?id=com.mobato.gallery. Currently min API 16 is supported, but I am thinking of making this 19 (KitKat), or dropping JellyBean support all together and just supporting Lollipop onwards. I will aim to explain why.
Recently I have added SD Card support. Anybody who has implemented proper SD Card support in their apps knows how frustrating this can be, especially with the new permissions required from the user in Lollipop onwards as part of the storage access framework (this is so bad that I even made a tutorial with screenshots showing the user how to grant access the SD Card, I have seen real users get confused by the SAF permissions activity). On KitKat it is impossible to write to the SD Card unless the device is rooted. This resulted in lots of negative reviews for apps when this limitation was introduced. Prior to KitKat all that was required was the write access permission to be declared in the application manifest. As you can see there are three different scenarios to write code for and test (pre-KitKat, KitKat and Lollipop onwards) which adds to development time/costs and bug fixing can become extremely cumbersome having to do full regression tests. However KitKat is still very popular. Since I don't even own a KitKat device it's impossible to test this scenario, let alone a rooted version (emulators only go so far).
Here are some additional facts:
KitKat devices account for 24% of checkins to Google Play
The 24% of KitKat users combined with older API levels (down to API 2.2) account for a whopping 39.3% of users checking in to Google Play.
Memory management for bitmaps just isn't great prior to Lollipop (lots of OOM can occur even with careful memory management as I have seen from crash reports).
JellyBean 4.4.4 got released in October 31, 2013. That's just over 3 years ago. In the world of mobile, that's equivalent to an entire period of geology such as the Jurassic Period.
JellyBean is discontinued according to https://en.wikipedia.org/wiki/Android_version_history
Fact: most of the bad reviews for my app are coming from users with low-end devices running older versions of Android, Lollipop onwards users generally leave more favourable reviews.
So in conclusion I am thinking about dropping support for KitKat and older at some point unless anybody believes it is worth supporting still? The question is how likely are those users ever going to make in-app purchases, although from a perspective of just showing adverts it might be worth it.
Please share your experiences with your apps and contribute your ideas.
g313 said:
Hello
Asking all developers to start a discussion on what the minimum API level is that you support, and have you decided to drop support for older APIs and if so what the reasons are. The reason for starting this discussion comes from the frustrations caused by having to support older API levels. Yes it's important to support as many users as possible - not everybody has access to the latest and greatest devices / Android versions, my own day to day device is a Samsung Galaxy S6 with Android 6.0.1. Although I have access to a device with Android 7.1 and one with Lollipop. However there is only so far back you can go in terms of support before development starts to get frustrating and in the end the question has to be asked if it is really worth it.
Please first take a look at https://developer.android.com/about/dashboards/index.html for the latest device stats.
For some background, I'm the developer of this app http://forum.xda-developers.com/android/apps-games/quick-gallery-photo-editor-t3394976 and https://play.google.com/store/apps/details?id=com.mobato.gallery. Currently min API 16 is supported, but I am thinking of making this 19 (KitKat), or dropping JellyBean support all together and just supporting Lollipop onwards. I will aim to explain why.
Recently I have added SD Card support. Anybody who has implemented proper SD Card support in their apps knows how frustrating this can be, especially with the new permissions required from the user in Lollipop onwards as part of the storage access framework (this is so bad that I even made a tutorial with screenshots showing the user how to grant access the SD Card, I have seen real users get confused by the SAF permissions activity). On KitKat it is impossible to write to the SD Card unless the device is rooted. This resulted in lots of negative reviews for apps when this limitation was introduced. Prior to KitKat all that was required was the write access permission to be declared in the application manifest. As you can see there are three different scenarios to write code for and test (pre-KitKat, KitKat and Lollipop onwards) which adds to development time/costs and bug fixing can become extremely cumbersome having to do full regression tests. However KitKat is still very popular. Since I don't even own a KitKat device it's impossible to test this scenario, let alone a rooted version (emulators only go so far).
Here are some additional facts:
KitKat devices account for 24% of checkins to Google Play
The 24% of KitKat users combined with older API levels (down to API 2.2) account for a whopping 39.3% of users checking in to Google Play.
Memory management for bitmaps just isn't great prior to Lollipop (lots of OOM can occur even with careful memory management as I have seen from crash reports).
JellyBean 4.4.4 got released in October 31, 2013. That's just over 3 years ago. In the world of mobile, that's equivalent to an entire period of geology such as the Jurassic Period.
JellyBean is discontinued according to https://en.wikipedia.org/wiki/Android_version_history
Fact: most of the bad reviews for my app are coming from users with low-end devices running older versions of Android, Lollipop onwards users generally leave more favourable reviews.
So in conclusion I am thinking about dropping support for KitKat and older at some point unless anybody believes it is worth supporting still? The question is how likely are those users ever going to make in-app purchases, although from a perspective of just showing adverts it might be worth it.
Please share your experiences with your apps and contribute your ideas.
Click to expand...
Click to collapse
You're right about bitmap memory management (I had an infinite System UI FC on CM 11 when I got too many notifications (from YouTube, by the way)
Sent from my GT-S7580 using Tapatalk
i want to run marshmallow apps on jellybean 4.1.2
g313 said:
Hello
Asking all developers to start a discussion on what the minimum API level is that you support, and have you decided to drop support for older APIs and if so what the reasons are. The reason for starting this discussion comes from the frustrations caused by having to support older API levels. Yes it's important to support as many users as possible - not everybody has access to the latest and greatest devices / Android versions, my own day to day device is a Samsung Galaxy S6 with Android 6.0.1. Although I have access to a device with Android 7.1 and one with Lollipop. However there is only so far back you can go in terms of support before development starts to get frustrating and in the end the question has to be asked if it is really worth it.
Please first take a look at https://developer.android.com/about/dashboards/index.html for the latest device stats.
For some background, I'm the developer of this app http://forum.xda-developers.com/android/apps-games/quick-gallery-photo-editor-t3394976 and https://play.google.com/store/apps/details?id=com.mobato.gallery. Currently min API 16 is supported, but I am thinking of making this 19 (KitKat), or dropping JellyBean support all together and just supporting Lollipop onwards. I will aim to explain why.
Recently I have added SD Card support. Anybody who has implemented proper SD Card support in their apps knows how frustrating this can be, especially with the new permissions required from the user in Lollipop onwards as part of the storage access framework (this is so bad that I even made a tutorial with screenshots showing the user how to grant access the SD Card, I have seen real users get confused by the SAF permissions activity). On KitKat it is impossible to write to the SD Card unless the device is rooted. This resulted in lots of negative reviews for apps when this limitation was introduced. Prior to KitKat all that was required was the write access permission to be declared in the application manifest. As you can see there are three different scenarios to write code for and test (pre-KitKat, KitKat and Lollipop onwards) which adds to development time/costs and bug fixing can become extremely cumbersome having to do full regression tests. However KitKat is still very popular. Since I don't even own a KitKat device it's impossible to test this scenario, let alone a rooted version (emulators only go so far).
Here are some additional facts:
KitKat devices account for 24% of checkins to Google Play
The 24% of KitKat users combined with older API levels (down to API 2.2) account for a whopping 39.3% of users checking in to Google Play.
Memory management for bitmaps just isn't great prior to Lollipop (lots of OOM can occur even with careful memory management as I have seen from crash reports).
JellyBean 4.4.4 got released in October 31, 2013. That's just over 3 years ago. In the world of mobile, that's equivalent to an entire period of geology such as the Jurassic Period.
JellyBean is discontinued according to https://en.wikipedia.org/wiki/Android_version_history
Fact: most of the bad reviews for my app are coming from users with low-end devices running older versions of Android, Lollipop onwards users generally leave more favourable reviews.
So in conclusion I am thinking about dropping support for KitKat and older at some point unless anybody believes it is worth supporting still? The question is how likely are those users ever going to make in-app purchases, although from a perspective of just showing adverts it might be worth it.
Please share your experiences with your apps and contribute your ideas.
Click to expand...
Click to collapse
i want to run marshmallow apps on jellybean 4.1.2 by decompiling particular app and editing its manifest.xml then change the minsdkversion to 16. is it possible? i tried it by decompling the file but i havent found any minsdkversion in manifest file after decompiling the apk.i downloaded an app called solid explorer and there is an option in it to open the apk file but that apk is not decompiled.so i took compiled apk ,i opened compiled apk file and then to manifest file after opening it i can see the minsdk version and other platform versions remember that was compiled apk file.
please tell me how to do this.
I'm not sure if this is news or not, but my Nexus 5X is updating to Android 7.1.2 Beta as I type this. I have seen articles stating that the Nexus 6P is getting the 7.1.2 Beta, but nothing on the 5X.
I stuck with the Nexus 6 for two years and loved it! I'm actually missing it in some ways. I picked up a New Sealed Carbon 32GB Nexus 5 X off eBay for $280 shipped, I've had it for two weeks now. I wouldn't call it a big "upgrade" but I am loving the fingerprint sensor and far superior camera! I wanted something a little smaller too so it is nice to be able to (easily) operate my phone one handed again. The 5.2" display is perfect for me. I'm not too worried about the whole "bootloop plague" with the Nexus 5X because the person I bought it from on eBay just received it from Google as a replacement for his 5X which was plagued by the infamous "bootloop". I would hope that Google wouldn't be replacing effected devices with potentially effected devices.
I use to be a "flashaholic" and loved trying out new custom ROMs. I stuck with Pure Nexus in the end. Now I'm happy just running Stock Android and stick to that. I use Android Pay daily (I've been out of the modding scene for a while, not sure if they worked around the whole Unlocked Bootloader / Rooted / ROMd and Android Pay dilemma) so that is a big part of why I just stay stock. It is good to know that the 5X has great dev support though so I'll have something to fall back on when Google abandons the 5X.
I'll update soon on what I think of 7.1.2 and any actual noticeable differences if anyone is interested.
Techbyte said:
I'm not sure if this is news or not, but my Nexus 5X is updating to Android 7.1.2 Beta as I type this. I have seen articles stating that the Nexus 6P is getting the 7.1.2 Beta, but nothing on the 5X.
I stuck with the Nexus 6 for two years and loved it! I'm actually missing it in some ways. I picked up a New Sealed Carbon 32GB Nexus 5 X off eBay for $280 shipped, I've had it for two weeks now. I wouldn't call it a big "upgrade" but I am loving the fingerprint sensor and far superior camera! I wanted something a little smaller too so it is nice to be able to (easily) operate my phone one handed again. The 5.2" display is perfect for me. I'm not too worried about the whole "bootloop plague" with the Nexus 5X because the person I bought it from on eBay just received it from Google as a replacement for his 5X which was plagued by the infamous "bootloop". I would hope that Google wouldn't be replacing effected devices with potentially effected devices.
I use to be a "flashaholic" and loved trying out new custom ROMs. I stuck with Pure Nexus in the end. Now I'm happy just running Stock Android and stick to that. I use Android Pay daily (I've been out of the modding scene for a while, not sure if they worked around the whole Unlocked Bootloader / Rooted / ROMd and Android Pay dilemma) so that is a big part of why I just stay stock. It is good to know that the 5X has great dev support though so I'll have something to fall back on when Google abandons the 5X.
I'll update soon on what I think of 7.1.2 and any actual noticeable differences if anyone is interested.
Click to expand...
Click to collapse
It's been available for a month on the 5X:
http://www.androidpolice.com/2017/0...cludes-pixels-nexus-5x-player-6p-and-pixel-c/
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
It's been available for a month on the 5X:
http://www.androidpolice.com/2017/0...cludes-pixels-nexus-5x-player-6p-and-pixel-c/
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Ahh I see. It must just be new to the 6P then.
Techbyte said:
Ahh I see. It must just be new to the 6P then.
Click to expand...
Click to collapse
Correct. It's was surprisingly delayed for the 6P.
Sent from my Nexus 5X using Tapatalk
My phone says that I have 4.31GB of data used on my sdcard. There is no way I should have that much, I only have a few apps downloaded and no games or media. Does anyone else notice a big chunk of data being used for no reason? I tried the Pixel ROM (which warns that there could be a 3GB file left on the sdcard) before flashing the Beta 7.1.2, but I clean flashed the Beta via the bootloader, which should have completely wiped the internal storage. I have tried looking for a big file, but can't find one. Any ideas would be appreciated.
The system uses nearly that much.
Sent from my Nexus 5X using Tapatalk
The ROM need that data for your System
lyall29 said:
My phone says that I have 4.31GB of data used on my sdcard. There is no way I should have that much, I only have a few apps downloaded and no games or media. Does anyone else notice a big chunk of data being used for no reason? I tried the Pixel ROM (which warns that there could be a 3GB file left on the sdcard) before flashing the Beta 7.1.2, but I clean flashed the Beta via the bootloader, which should have completely wiped the internal storage. I have tried looking for a big file, but can't find one. Any ideas would be appreciated.
Click to expand...
Click to collapse
Android System takes about 4GBs that why.Before the update if remember correctly didn't show all phone's memory (with android system). e.g. On my nexus 5x 16GB on android 7.1.1 it was showing used 3.7GBs of 10.67GBs, now it says 7.7GB of 14.68GBs.
Look at the picture that I've attached.
Billys20 said:
Android System takes about 4GBs that why.Before the update if remember correctly didn't show all phone's memory (with android system). e.g. On my nexus 5x 16GB on android 7.1.1 it was showing used 3.7GBs of 10.67GBs, now it says 7.7GB of 14.68GBs.
Look at the picture that I've attached.
Click to expand...
Click to collapse
I meant to say that I had 4GB of Apps. I ended up clean flashing back to 7.1.1 and when I first booted the phone there was only a few hundred MB's of Apps. After I downloaded all of my must have apps, I checked again and sure enough, I have about 4GB of Apps downloaded. I think it's mostly Pocket Casts and the downloaded podcasts. I'm not used to a 16GB phone, it's been so long since I've had to keep an eye on my storage.
Thanks anyway for the reply:good:
I couldn't edit my previous post and add this attachment.
any chance getting bootloop signing up with beta? would like the 7.1.2 fingerprint swipe
Do you have an older Android device? If yes, do you still use it in any way? ?, Share your story here.
Android OS is dynamic (I'd say unstable ?). The device you are buying today might become older enough in a couple of months in terms of the Android version. However if you're lucky to have a truly rich and supporting community, your device will be alive for an eternity.
In the revolution of Android ecosystem, you would possibly like to upgrade your device after major Android updates. Or you have to be satisfied and hanker after the newer Android features otherwise.
Now it's time to share mine ?. I got a local, cheap Jellybean device, when I was introduced to Android in early 2014. Now I have still that Android 4.2 device which I love more than the prettier material design or even the notification dots and others.
I have been using that device for my development purpose for a long time alongside my primary device. As I used it in my first step to Android root, mods, hacking and the system insight. I still remember the day I got this device into bootloop for the first time ?. Those days have passed away.
Now I am learning and developing Android apps. Since my laptop is even smaller than its small configuration (? You can call me a poor guy), it is quite impossible to test and debug apps on Android emulator while running Android studio in parallel with 4GB of RAM and i5. So, I started using my old friend as a helping hand in development. I keep it connected via USB while developing my apps, run and test them with it which frees nearly 700MB of RAM on my tiny machine and boost the build time also. For other Android versions, I have to do them on emulator separately ?.
What you're thinking of me I don't care ?. The phone is much more to me. Feel free to share yours...
What is your phone name and model?
Have you installed a custom rom on it yet?
What are your apps which you have developed?
I've never done anything like this before, & am a total newb when it comes to this kind of thing, so please bear with me.
I have an old 1st Gen Nexus 7 but stopped using it when the OS update slowed it down. Since getting a Nokia 1 Plus & seeing how relatively great that runs on Android Go Edition/Andriod 10, I thought it would be a good idea to break out the old Nexy & see if I could get her running on this as it's designed for devices with 2GB or less (the Nexus 7 has 1GB I think).
I have two primary concerns; firstly, I don't want to download malware onto my computer or pad, & secondly, some of the guides I've seen are way over my head when it comes to the tech side of it...
Any help would be very much appreciated.
EDIT: by the way, I'm on a Win 10 PC.
Sadly it does require a degree of technical knowledge to be able to do anything
However if you want a good ROM just use Unlegacy Android, it runs lightly enough for this tablet and is what I like to use personally
You probably could build it in theory, but it may not install, considering the small system partition the Nexus 7 has and how I can find absolutely no tutorials online on how to resize it (all the tutorials are for the 2013 model and don't work on the 2012 one). Any ROM past 7.1.2 can't use gapps at all, and any ROM past 6.0 can only use pico gapps (absolute minimum functionality).