I have a Moto G3 XT1543 and since december I have given this device a second life and have been using it as a secondary phone. I decided to install LOS 14.1 because I feel is better for this device than LOS 17.1. Since then I had been using the phone and installing the updates without problems until a few weeks ago.
I thought I couldn't install the update because my version of TWRP was so out of date. So I decided to install the latest version for this device (twrp-3.5.2_9-0) and I was able to update the rom but it got me a lot of bugs, basically forced close in many processes.
So I decided to do a clean installation but still had a lot of bugs. So I installed previous versions of the rom, including the first one that I installed and worked fine, but it still had a lot of bugs (basically forced close in many processes, as I said before).
So I decided to go back to the TWRP I had before (twrp-3.4.0-0) and the bugs disappeared and I was able to use the rom without problems, but no matter what I do I cannot get youtube working now.
The gapps that I have been installed are open_gapps-arm-7.1-pico-xxxxxxxx and I have done all the possible combinations: old gapps with the most recent rom (lineage-14.1-20210829-UNOFFICIAL-osprey), the most recent gapps with the oldest rom I have (lineage-14.1-20201221-UNOFFICIAL-osprey), the oldest rom I have with old gapps and the most recent rom with the most recent gapps, but youtube still doesn't work
As I said before, it doesn't matter what combination I do, even the first one I installed and worked since last december, nor what version of YouTube I have installed, the application closes. As a possible solution I have deleted cache and data of youtube but the problem still. The funny thing is all the applications that I have, including other google apps (chrome, gmail, maps) work without problem.
I have tried alternatives like YT Go, YT Vanced and New Pipe and all three work without problem, but honestly, although they are better alternatives, I don't want to use them.
So does anyone know how to fix this?
I used this weekend for testing and long story short I can use youtube but I have no idea how it was fixed.
But I will tell you about everything I did in case someone in the future is going through a similar situation to mine.
Following the indications that FNetV1 gave me in another post, I downgraded my TWRP version to 3.0.2-r5, then I installed the oldest rom I have (lineage-14.1-20201221) with the oldest gapps I have (open_gapps-arm-7.1-pico-20210112) but youtube was not working.
So with that same version of TWRP I installed the most recent rom available (lineage-14.1-20210829) with the most recent gapps and still youtube did not work.
So I installed the latest unofficial version that Squid2 developed for this device (twrp-osprey-3.2.3-r1) and then installed the oldest rom I have with the oldest gapps I have. The result was the same, youtube was not working.
I thought the problem was the gapps, so I installed the latest rom available with the most recent gapps but now with the Nano package. But the result was the same, youtube was not working.
So I gave up and for the last time I reinstalled the latest rom avaible with the most recent gapps, again with the pico package and as expected youtube was not working.
The funny thing is after I finished setting up my phone, I restarted it, reinstalled YouTube and voilà, I can now use YouTube without any problem.
As I said at the beginning, I have no idea how the problem was fixed, especially because I also rebooted my phone on several occasions with the previous tests.
So if anyone has an idea what I did wrong from the beginning or how the problem was fixed, feel free to comment.
Related
My Stock HTC One S has been superb until about 6 months back when I continually keep getting Google Play Store Errors. It seems to be about 60% of the time which is a major pain.
I finally bit the bullet and rooted / rom'd my phone and have been progressing through the list of roms in XDA to try and eliminate this problem.
However, the Play Store issues persist!!! I've tried about 6 roms and a couple of different Gapps, so what's the cause??
Is the problem in my
Boot
Kernel
The Main Rom
Gapps
The closest I came to finding an answer was this quote - "The issue lies with the wifi module in the kernel. I have a fix should be out by tomorrow" in here - http://forum.xda-developers.com/showthread.php?t=2523609&page=30
I've tried the usual clearing cache, uninstalling services, rebooting, try downloading on 3g rather than wifi etc etc etc. But the point is this barely ever works, and We Shouldn't Have to do this!!!! I've googled till my fingers hurt... Any suggestions gratefully received. I love this phone and don't want to change!
My Phone is currently, Hboot 2.15, S-On, cm-11-20140104-SNAPSHOT-M2-ville, gapps-kk-20140105-signed. S4 1.5GHz model. TWRP 2.7 (I think)
markb101 said:
My Stock HTC One S has been superb until about 6 months back when I continually keep getting Google Play Store Errors. It seems to be about 60% of the time which is a major pain.
I finally bit the bullet and rooted / rom'd my phone and have been progressing through the list of roms in XDA to try and eliminate this problem.
However, the Play Store issues persist!!! I've tried about 6 roms and a couple of different Gapps, so what's the cause??
Is the problem in my
Boot
Kernel
The Main Rom
Gapps
The closest I came to finding an answer was this quote - "The issue lies with the wifi module in the kernel. I have a fix should be out by tomorrow" in here - http://forum.xda-developers.com/showthread.php?t=2523609&page=30
I've tried the usual clearing cache, uninstalling services, rebooting, try downloading on 3g rather than wifi etc etc etc. But the point is this barely ever works, and We Shouldn't Have to do this!!!! I've googled till my fingers hurt... Any suggestions gratefully received. I love this phone and don't want to change!
My Phone is currently, Hboot 2.15, S-On, cm-11-20140104-SNAPSHOT-M2-ville, gapps-kk-20140105-signed. S4 1.5GHz model. TWRP 2.7 (I think)
Click to expand...
Click to collapse
U use outdated versions of CM11 and GApps as far as i see. BUT do you get a specific error message? Or does the playstore not connect?
LS.xD said:
U use outdated versions of CM11 and GApps as far as i see. BUT do you get a specific error message? Or does the playstore not connect?
Click to expand...
Click to collapse
I tried the latest CM11 nightly previously, and the suggested Gapps from the CM website - http://wiki.cyanogenmod.org/w/Google_Apps. I confirm I have TWRP = 2.7.0.0
I have now tried again cm-11-20140319-NIGHTLY-ville with the latest Gapps from here - http://forum.xda-developers.com/showthread.php?t=2397942 (I chose the minimal Gapps to allow everything else to update from the Play Store).
I'm still getting the "Unknown error code during application installation 960" - I've had others but this is the most common.
The play store does connect - and if an app fails to install, it may (or may not) work later on so it appears totally random.
markb101 said:
I tried the latest CM11 nightly previously, and the suggested Gapps from the CM website - http://wiki.cyanogenmod.org/w/Google_Apps. I confirm I have TWRP = 2.7.0.0
I have now tried again cm-11-20140319-NIGHTLY-ville with the latest Gapps from here - http://forum.xda-developers.com/showthread.php?t=2397942 (I chose the minimal Gapps to allow everything else to update from the Play Store).
I'm still getting the "Unknown error code during application installation 960" - I've had others but this is the most common.
The play store does connect - and if an app fails to install, it may (or may not) work later on so it appears totally random.
Click to expand...
Click to collapse
Which radio you're on?
LS.xD said:
Which radio you're on?
Click to expand...
Click to collapse
Hadn't thought of checking this, is it possible this could be the Problem? I'm currently on radio 1.11.50.05.28
Thanks for your thoughts so far
Hey there!
Sorry for creating a pull for asking help first, but I've been messing around the forum and Google with no results.
The thing is: I have a Motola Moto G 2013, it works pretty fine. Some time ago I'd like to try CM 12.0, and everything went okay. I didn't need to install the GApps cause, don't know why, it already has Play Store and Google Services, so, no problem.
Some days ago my phone started to work PRETTY bad, and reading in the web found that CM 12.1 were released, so i thought "lets give it a try"
CM 12.1 installed well, but without any GApp, so started to search the GApps packages. Tried with many of them, Pico, Nano, Stock, from april of this year, may of thies year, even from july this year! But none of them worked. When Android starts (after GApps install) appears a windows that says that a factory reset is needed. After that, starts the nightmare. Constantly, really constantly, appears two windows "Play Store has stopped" and "com.google.process.gapps has stopped" and after that, like pressing the "Ok" button10 or 15 times, almost every time, it gets on black and only can power off and restart,
As I could, went to settings > all > and cleaned and stopped every google service. When I made that the device perdormance goes pretty much better, but when try to acces mi gmail o opening play store, again, the same.
I thought that changing the recovery would do some change effect. Tried with CWM (the one i had from before), Philz Touch and now the latest version of TWRP (the one that looks like Material Design), with no effects. And finally, tried with other ROM. I downloaded AOSP http://forum.xda-developers.com/moto-g/development/rom-android-source-project-t3060704 but again, gapps error. Also tried with blisspop, but couldn't install it, it was like 4 a.m. and my mood wasn't good for keep trying.
Before you ask, yes, I made every goddamn wipe before and after the install (after only dalvik and cache partition)
It's like no matter what ROM, no matter what version of GApps, the doesn't work. I've been like this from two days ago, and really, the different options are starting to vanish.
Sorry again for creating a topic for this, but is this, or throwing the PC and mobile above the window.
And, also, sorry about my english, I'm from Argentina.
If you need more details, like Recovery versions, GApps versions, screens, anything, ask 4 it.
Cheers and thanks!
Hi guys,
My girlfriend purchased a brand new Xperia Z3 D6653 not too long ago (about 2 months ago?). I flashed the 5.1.1 pre-rooted firmware for her and it's working fine and all but it does a random reboot every day or so, at random times, with random applications.
I have tried 2 different pre-rooted 5.1.1 firmwares already (yes, the correct model D6653 as well) and it still does it. The System Incident reports don't really say much (in fact you only see details about when it crashed, nothing else), and it seems like Google Play Services is the only thing mentioned in the Application Report.
The same thing also happened (more frequently) when she was on the 5.0 pre-rooted firmware. I'm not sure why, I haven't unlocked the bootloader or anything, it's just stock pre-rooted ROM, that's it. I haven't flashed any other ROMs other than the official pre-rooted ones.
Furthermore, before I flashed the 5.0 and 5.1 firmware for her, the phone came with Android 4.4.4. She used it for a month and reported several crashes as well, so that's with the original factory firmware, unrooted, unmodified etc.
She doesn't run any dodgy or random apps, she's just a typical girl that use Facebook and texting, that's pretty much it. I've done a lot of research on this issue and it seems to be quite common, however there isn't really a solution to this. The same apps she currently use never caused any issues on her older phones.
Also in case anyone asks, the only reason I flashed the pre-rooted 5.1.1 firmware for her is because it makes it easier for me to manage her phone (with Teamviewer, you can remote into the phone as long as it's rooted). Also, I get to backup her phone and do tests etc, makes it easier for me.
Also, I'm not using any custom kernels or overclocking the CPU etc. Everything is just stock but rooted.
Could this be caused by a hardware fault in the phone? I'm not sure what else I can do and would appreciate some suggestions.
Nobody have this issue??
Well, how about you try to flash a full, clean, stock ROM, don't root it, don't install any unnecessary app and see where it goes? If the issue persists, try getting a logcat from the phone and we can take a look at it. If it works fine after returning to stock, there might be a problem with the ROM or some apps you are using.
If it really is Gapps that are causing all the trouble, go to APKMirror and download the latest apps available (Play Services, etc) and see where it goes.
As mentioned already, prior to flashing anything, my girlfriend was running a completely stock, factory version of the phone. It came with Android 4.4.
I could flash a completely stock 5.1 ROM but was hoping that someone would share their experiences or a potential solution to this, considering this is quite commonly asked. I would also like to avoid doing this if possible, because if I were to go back to rooting the device, I'd have to downgrade to v4.4 pre-rooted, then flash to 5.1 rooted with custom recovery. It's just a lot of work for a simple testing that could be answered by others if possible.
Anyway, she didn't have any apps installed other than Facebook and Whatsapp, that's it. I might test with GAPPS and see how it goes, but I thought I'd ask here in case someone knows it's definitely a hardware issue or something else.
i would definitely give a pure stock 5.1.1 a go. I used to get the random reboots on the previous versions but i no longer have such issue.. Make sure you do a clean wipe and do it a few times.
Hi all, it's been a while but I thought I'd post an update and share what I've found/learned so far....
Basically, I'm still getting the frequent random reboots. I've tried reflashing the ROM and also tested out the latest .232 pre-rooted stock ROM, still getting the same issue. I've noticed that other than Google Play Services, sometimes Gapps will crash as well. But most of the time, there's nothing reported in the system or application crash logs. I've tested with everything running as stock, no additional apps installed. I then decided to flash the Minimal GAPPS 5.1.x and that sort of made the phone a bit more stable, but still reboots randomly every now and then.
Later on, I decided to try a custom ROM that still works on a locked bootloader. I found this here:
http://forum.xda-developers.com/z3/development/d6603-23-1-1-28-t3102271
The chef has provided a .232 firmware for you to flash in recovery, as well as the ROM base for the D6603 model. Mine is a D6653, but luckily the chef has also provided a D6653 patch for you to flash as well. I've flashed the ROM like so:
1. Wipe everything except my external microSD in TWRP. So basically, wipe system, data, cache, dalvik, internal storage etc.
2. Install .232 firmware.
3. Install v10.5
4. Install v12.0
5. Install D6653 v5 patch
It boots up fine but after using it for a while, I still get the random reboots. What's interesting is that I've also tried without flashing the D6653 patch, which essentially means I'm running just the D6603 base ROM on my D6653. It works, but still crashes as well. I just found it quite surprising that a D6653 could run a D6603 ROM, but it does make sense considering the main differences is just the baseband/frequencies.
Anyway, I later on decided to flash the pure 5.1.1 stock ROM, still getting the crash. Again, everything is tested on pure stock, no additional apps etc installed.
I'm starting to think perhaps this is a hardware issue on my phone?? I noticed that sometimes, my screen will show a bit of tearing and then it'll crash not long after. BUT, I also know that as soon as gapps or google play services crash, the phone will crash not long after as well.....
In fact, I later on used Titanium Backup to convert Google Play Services from a System to a User app, the phone will just boot into the lockscreen and then restart every time. This is a bit ridiculous because I've done this several times on other phones before and they never had such an issue. Of course, I'm not saying I always run Google Play Services as a User app, but that was just for testing and I honestly don't think it should cause a bootloop just because of that. I've also cleared dalvik and cache by the way, so it doesn't make sense that the phone boots into the lockscreen and then just restarts randomly.
I haven't tried uninstalling Google Play Services completely, but at this point I'm back to square one as I've exhausted pretty much all my options and it's been a complete waste of time. I'm beginning to hate this phone more and more. The only thing left is to unlock bootloader and play with other custom ROMs. But yeah, flashing the .232 firmware didn't fix it, AND flashing pure stock 5.1.1 Android didn't fix it either...
Just wondering if others have the same issue and any ideas what could be causing it? If I provide some Logcat logs, would someone be kind enough to look into this for me?
Update:
I'm still getting the random reboots and I think it's very likely to be hardware related. But sometimes also a bit related to software, specifically with Google Play services. I've had more time to test out a few things since my last update, they are as follows:
- Tested complete stock 4.4 ROM without root. Still crashes every now and then, but not as much compared to 5.0 and 6.0 (doesn't matter if it's stock or custom ROM).
- Finally gave in and unlocked bootloader (backed up my DRM keys of course). I thought perhaps that the stock Sony roms (and even the stock-based Sony custom roms) have issues for some reason. They are all the same base, so I thought I'd do a fair test by trying a completely different based rom, such as AOSP. I've used CM 1.2.1 nightly here:
forum.xda-developers.com/z3/development/rom-cyanogenmod-12-nightlies-xperia-z3-t3010201/page117
And yes, I know that nightly have bugs, but the nightly build as of 2016-03-03 seemed pretty stable according to most users. I've tried various other AOSP based roms and stock based Sony roms (for unlocked bootloaders) and they all produce crashes.
I've flashed custom kernels as well and updated my recovery to TWRP 3.0, but all the same results. On all of the custom ROMs I've flashed, the only thing I've done was setup my Google account (so I have my contacts and Gmail) and that was it. No other apps installed. I wanted to limit the environment down to just the stock setup of the ROM itself, as this helps me rule out any potential bugs caused by 3rd party apps.
Having done all of the above and still resulting in crashes, it's safe to assume that this is most likely unrelated to the software, but hardware. I've noticed that sometimes when I scroll a page too fast and move it up and down with my thumb, the screen will freeze and restart.
However, sometimes I will get crashes related to Google Play Services. Anything that relies on Google Play Services will crash randomly. If you re-open the apps, it just crashes again. If you force stop the app and open it, still crashes. The ONLY fix is to restart the phone. I have tried flashing different GaPPs, starting with the pico and nano versions, as well as the ones recommended by the ROM chefs. Still the same result.
So the conclusion is, I haven't really gotten anywhere with this annoying issue. There's definitely an issue with the phone somewhere, maybe a bit of software related, but mostly hardware.
If the following table is correct then I have a GT-N8013. I'm running KitKat 4.4.2 on it: (N8010XXUDNE4_N8010BTUDNF1_BTU_N8013.tar.md5).
How close can one get to the latest version of Android and still have a working GT-N8013?
GT-N8000 - Wifi+3G+calling
GT-N8005 - Wifi+3G
GT-N8010 - Wifi (Except USA)
GT-N8013 - Wifi (Only USA)
GT-N8020 - Wifi+LTE
KK 4.4.2 is the last release from Samsung .
Android then see your models custom rom section .
JJEgan said:
KK 4.4.2 is the last release from Samsung .
Android then see your models custom rom section .
Click to expand...
Click to collapse
I've just picked up a used 10.1 (first edition) and am hoping to get it onto 5.1.1 or 6.01.
I see a custom CM ROM from Cyanogen, that states it's 6.0 official, but when I go to the site the release is really old for the 8013, and I'm not sure if it's been grouped in with the more recent beta group that is linked in the thread or if it's not.
I also see an older Cyanogen thread for 12, but that's pre 6.0 and appears to be somewhat abandoned.
My Note 3 is on phronesis 6.0.1, and I would like to get the Note 10.1 to as close to that as possible, without dealing with any major bugs.
Thank you for your assistance.
Some progress.
I managed to update mine to Marshmallow 6.0.1 (cm-13.0-20160523-UNOFFICIAL-n8013.zip) via CWM v6.0.3.6 but Google Apps keeps crashing.
I've tried both open_gapps-arm-6.0-nano-20160721.zip (Open GApps) and gapps-600-base-20151107-1-signed.zip. Both take hours to install and just keep crashing whenever you try to do anything.
Anyone have any luck getting cm-13.0-20160523-UNOFFICIAL-n8013.zip / and GApps.zip working?
Basil Rathbone said:
I managed to update mine to Marshmallow 6.0.1 (cm-13.0-20160523-UNOFFICIAL-n8013.zip) via CWM v6.0.3.6 but Google Apps keeps crashing.
I've tried both open_gapps-arm-6.0-nano-20160721.zip (Open GApps) and gapps-600-base-20151107-1-signed.zip. Both take hours to install and just keep crashing whenever you try to do anything.
Anyone have any luck getting cm-13.0-20160523-UNOFFICIAL-n8013.zip / and GApps.zip working?
Click to expand...
Click to collapse
I had it crashing initially too, with CM-13.
I reinstalled the ROM, root, twrp, everything. I also made sure to install the latest "Stock" Gapps, before rebooting once the ROM was in place. Since then I have not had any issues.
I did however have some issues using the nano package. Hope that helps.
Still no joy
I still can't get CM-13 to work. I use CWM. I made sure I was using the latest CWM 6.0.4.6.
I booted into CWM, factory reset and cleared cache. Flashed cm-13.0-20160523-UNOFFICIAL-n8013.zip.
I then factory reset and cleared cache again and flashed gapps-600-base-20151107-1-signed.zip.
I then factory reset and cleared cache again and rebooted.
No joy.
What actual gApps and CM-13 did you use? Maybe I need to use the same version of TWRP as you used?
I'm stumped.
--------------------------------------------------------------------------------
bladebarrier said:
I had it crashing initially too, with CM-13.
I reinstalled the ROM, root, twrp, everything. I also made sure to install the latest "Stock" Gapps, before rebooting once the ROM was in place. Since then I have not had any issues.
I did however have some issues using the nano package. Hope that helps.
Click to expand...
Click to collapse
Basil Rathbone said:
I still can't get CM-13 to work. I use CWM. I made sure I was using the latest CWM 6.0.4.6.
I booted into CWM, factory reset and cleared cache. Flashed cm-13.0-20160523-UNOFFICIAL-n8013.zip.
I then factory reset and cleared cache again and flashed gapps-600-base-20151107-1-signed.zip.
I then factory reset and cleared cache again and rebooted.
No joy.
What actual gApps and CM-13 did you use? Maybe I need to use the same version of TWRP as you used?
I'm stumped.
--------------------------------------------------------------------------------
Click to expand...
Click to collapse
I used the ARM 6.0 Stock version for CM 13. http://wiki.cyanogenmod.org/w/Google_Apps#Downloads
I ended up swapping to the 2014 model because I got a good deal on a Verizon version (which is locked but oh well), so I don't recall the TWRP that I ran. It sounds like that sometimes gives people issues.
I do recall that using the nano version of gapps was not working for me. Could be a coincidence, but I had constant crashes when I tried using it.
This is the thread I used to grab the ROM and TWRP: http://forum.xda-developers.com/galaxy-note-10-1/development/rom-lollipop-t3269375
It helps to read the installation notes properly
The problem(s) I was having were resolved by using twrp-2.8.7.0-gt-n8013 instead of N8013-CWM-Touch-6.04.6. I also used open_gapps-arm-6.0-stock-20160803 instead of nano but I really think it was TWRP that made everything work.
I'm now running cm-13.0-20160523-UNOFFICIAL-n8013 without any problems.
I consider this thread closed.
Basil Rathbone said:
If the following table is correct then I have a GT-N8013. I'm running KitKat 4.4.2 on it: (N8010XXUDNE4_N8010BTUDNF1_BTU_N8013.tar.md5).
How close can one get to the latest version of Android and still have a working GT-N8013?
GT-N8000 - Wifi+3G+calling
GT-N8005 - Wifi+3G
GT-N8010 - Wifi (Except USA)
GT-N8013 - Wifi (Only USA)
GT-N8020 - Wifi+LTE
Click to expand...
Click to collapse
How did you get KitKat on n8013. It was never released and no one successfully flashed 4.4 n8010 to n8013. Odin keeps giving an error. Please I've been trying for years now since it's been 2 years since update was released and doesn't look like it'll ever release (**** yoi Samsung with your update **** and regions)
Anyone have any luck? I've had this tablet since 2013 and I stopped using it because it has always been such a laggy sluggish experience. I thought I would try putting an AOSP ROM on it to see if that helped. Everything is so old for this device that it's nearly impossible to find the old files, ROMs, recoverys, etc. I can't even get TWRP or CWM to work on it. Maybe it's not worth the trouble anymore.
MrAwesome75 said:
Anyone have any luck? I've had this tablet since 2013 and I stopped using it because it has always been such a laggy sluggish experience. I thought I would try putting an AOSP ROM on it to see if that helped. Everything is so old for this device that it's nearly impossible to find the old files, ROMs, recoverys, etc. I can't even get TWRP or CWM to work on it. Maybe it's not worth the trouble anymore.
Click to expand...
Click to collapse
Well official only kitkat if you are international (Samsung decided not to release a lot of device updates in the us for kit kat including the s3, galaxy light, and this one). However I think you can get CM 13.1, idk about anything more recent but there is a (slightly) active community for it still left. Its a shame that this flagship tablet was neglected. I hope it doesn't happen with future Samsung ones but I've avoided buying any. I still use mine on jellybean for basic internet browsing and games
zMrAwesome75 said:
Quote:
Anyone have any luck? I've had this tablet since 2013 and I stopped using it because it has always been such a laggy sluggish experience. I thought I would try putting an AOSP ROM on it to see if that helped. Everything is so old for this device that it's nearly impossible to find the old files, ROMs, recoverys, etc. I can't even get TWRP or CWM to work on it. Maybe it's not worth the trouble anymore.
Click to expand...
Click to collapse
Not sure if you're still looking but I just installed Android Nougat v7.1.2 using the instructions provided here:
https://forum.xda-developers.com/showthread.php?t=2185119
I have a N8010 that topped out at 4.1.2. I flashed to a N8013 kernel/rom about 2 years ago which maxed out at 4.2.2 . I just recently found that link to the LineageOS build (Formerly Cyanogenmod) when I was contemplating buying a new tablet. The tablet was getting a bit sluggish so I decided to go ahead and blast it out and see what happened. I was VERY pleasantly surprised! Had some issues getting the Recovery flashed but once I did, it was pretty smooth from there. I had backed up all the apps so once I got it booted and restored all the apps, I was surprised how responsive it is. Oh, and you can say goodbye to all those SD card issues that the Note 10.1 had since this version of Android integrates the external SD with the internal SD so everything gets installed on the external card. No need for apps like folder mount, etc.
I highly recommend it. The only issue is that you lose the integrated S-Pen functionality but you can reinstall some of those apps from the play store and bring back a lot of those features. Some 3rd party apps actually work better.
Good luck!
7.1.2 on GT-N80013
I am currently running an unoffical build I picked up here on xda it is an unofficial Lineage OS build. I haven't currently found any bugs... camera works, bluetooth works, wifi works... at least for me. The build number is 14.1-20170810-unnofficial-n8013
Hannover2k said:
Not sure if you're still looking but I just installed Android Nougat v7.1.2 using the instructions provided here:
https://forum.xda-developers.com/showthread.php?t=2185119
I have a N8010 that topped out at 4.1.2. I flashed to a N8013 kernel/rom about 2 years ago which maxed out at 4.2.2 . I just recently found that link to the LineageOS build (Formerly Cyanogenmod) when I was contemplating buying a new tablet. The tablet was getting a bit sluggish so I decided to go ahead and blast it out and see what happened. I was VERY pleasantly surprised! Had some issues getting the Recovery flashed but once I did, it was pretty smooth from there. I had backed up all the apps so once I got it booted and restored all the apps, I was surprised how responsive it is. Oh, and you can say goodbye to all those SD card issues that the Note 10.1 had since this version of Android integrates the external SD with the internal SD so everything gets installed on the external card. No need for apps like folder mount, etc.
I highly recommend it. The only issue is that you lose the integrated S-Pen functionality but you can reinstall some of those apps from the play store and bring back a lot of those features. Some 3rd party apps actually work better.
Good luck!
Click to expand...
Click to collapse
I'd appreciate a link to the rom you installed. Thx.
I'm interested as well I'm still running original os. Also wondering if the rom update works well on these tablets since they are older. As Android matures the os gets bigger which can impact performance on older CPUs.
cloves said:
I'm interested as well I'm still running original os. Also wondering if the rom update works well on these tablets since they are older. As Android matures the os gets bigger which can impact performance on older CPUs.
Click to expand...
Click to collapse
I recently installed Lineage OS 14 and it is working great.
Tablet is stable, everything works, great battery life.
All devices work gps, etc...
The s-pen will not work like it did stock but there are apps you can get that seem to work better
Squid and Sketch for drawing....squid seems cool if you write with stylus
Install Magisk instead of supersu.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Hi guys, I'm new here, I've searched forum similar posts but I couldn't find anything.
I rooted my Nuogat 7.0 device with the last versions of twrp recovery and SuperSu. (The device is unlocked and S-ON)
A couple days ago I decided ti flash LineageOS 14.1 ROM and the super Gapps package. At the beginning all' ok, but I noticed that the HTC sense interface was absent.
So I tried install the last versions of it but it gave me crash problems everytime I tried to interact with it (like when moving apps or installing themes). I Also noticed that the layout is smaller than the one I had before installing lineageOS(app icons are smaller, and apps layout too (this doesn't happen when I launch Google home Launcher)).
I've tried installing older versions found on apkmirror, but they all give me the same problems.
LineageOS ROM was the correct one for my phone and GApps pack was the correct one for my CPU. Please help I like too much Sense home