Anyone get the Gear S2 watch working in a custom rom like CM? CM13?
Still trying to get my gear s2 working on my galaxy s5 running CyanogenMod 12.1
Worked fine for me with oneplus one. Just make sure you light reset the watch any time you try a new rom
Sent from my A0001 using Tapatalk
Yea tried that. Normally thr gear app would pop up and try to pair with the gear s2 but its not doing that. Ive manually downloaded the three Samsung gear APKs on the other thread...believe it was the gear plugin, Samsung accessories, and Samsung gear app. The app is giving the error saying Samsung gear cannot install due to custom ROM.
Hi!
I tried to install the Samsung Gear App and get the same Error that the OS has been modified unauthorised... :-/
My Question is: Did someone try this App after insalling the stock ROM again?
I don't want to backup and reinstall all apps and data...
Thank you for your help!
I have been through this rodeo, and I have noted a couple things.
1) Unlocked Bootloader: Doesn't matter, I am currently running Phils Recovery on my TW Official OK4 ROM, Gear and android pay work fine.
2) CM12.1 or CM13, not rooted or removed root: Doesn't work. Root is not the only thing both apps are looking for.
3) TW Custom ROM: Doesn't work. Could not get it working on my MOAR 7 rom which is based on TW.
4) STOCK ROM with Phils Recovery: Works fine if I don't root.
So obviously the check goes beyond root, and probably some combination of Software Version / Build Number or some other reference point to detect the ROM.
The reports of hiding the root on a custom ROM to get Android Pay to work, simply don't work. My hunch is that whatever Android Pay is using, is the same mechanism as the Gear Manager app from Samsung.
In the end, frustrating, because TW stock is completely slow, and kills my battery, and does stupid things like turns on my screen anytime I put it on an inductive charging station, or won't allow me to turn the volume to max over BT because of communism... or socialism... or whatever.
[email protected] said:
I have been through this rodeo, and I have noted a couple things.
1) Unlocked Bootloader: Doesn't matter, I am currently running Phils Recovery on my TW Official OK4 ROM, Gear and android pay work fine.
2) CM12.1 or CM13, not rooted or removed root: Doesn't work. Root is not the only thing both apps are looking for.
3) TW Custom ROM: Doesn't work. Could not get it working on my MOAR 7 rom which is based on TW.
4) STOCK ROM with Phils Recovery: Works fine if I don't root.
So obviously the check goes beyond root, and probably some combination of Software Version / Build Number or some other reference point to detect the ROM.
The reports of hiding the root on a custom ROM to get Android Pay to work, simply don't work. My hunch is that whatever Android Pay is using, is the same mechanism as the Gear Manager app from Samsung.
In the end, frustrating, because TW stock is completely slow, and kills my battery, and does stupid things like turns on my screen anytime I put it on an inductive charging station, or won't allow me to turn the volume to max over BT because of communism... or socialism... or whatever.
Click to expand...
Click to collapse
Thank you "eatmeimadanish"!
So, if i install the stock rom (recovery stays the same) the app will start without a problem and the connection to the gear s2 is fine?
The only thing is that i'll have the standard samsung tw-rom again...
scorp1on1899 said:
Thank you "eatmeimadanish"!
So, if i install the stock rom (recovery stays the same) the app will start without a problem and the connection to the gear s2 is fine?
The only thing is that i'll have the standard samsung tw-rom again...
Click to expand...
Click to collapse
Yes. Unfortunately the TW rom does suck, and has a bunch of built in stuff you can't turn off. If you are used to (like me) with a ROM that makes any kind of sense in it's design, then it's a beotch to switch back (kiss the battery life goodbye). On a good front, the Gear S2 is pretty awesome....
Hey!
I got my Samsung Gear S2 today and i'm installing my apps again.
Gear Manager started without a problem and the connection to the Gear S2 was established in a second!
Of course i'll install another launcher!
Best regards,
scorp
Found the Answer... CM13 working with Gear S2
http://forum.xda-developers.com/gea...gear-manager-samsung-accessory-t3216240/page7
Found the answer with the help above. I just did this on my Ressurection ROM and the app now looks for the watch... Don't have my watch but it got past the error message so I will try it tonight and report back.
Lineage OS
Tested on Lineage OS for Samsung S7 Edge. It worked perfectly thank you
[email protected] said:
http://forum.xda-developers.com/gea...gear-manager-samsung-accessory-t3216240/page7
Found the answer with the help above. I just did this on my Ressurection ROM and the app now looks for the watch... Don't have my watch but it got past the error message so I will try it tonight and report back.
Click to expand...
Click to collapse
Tested on my galaxy s4 gt-i9500 whit lineage os 14.1 and works perfect
I have followed instruction and after editing i could not install gear and required apps from google play. I had to find apk outside and it worked. I`m using lineage 14.1 and n910v -Note 4 Verizon. Does anyone know why i could not download from google play ? Should i use some other brand in build.props or change something additionally?
Related
**PHONE INFO BELOW**
I feel as if my situation is really unique and I can only find help by posting
Okay, so it starts like this. I rooted my phone using odin3 and it worked splendidly and everything worked such as gapps. Then I decided to try installing roms... I installed cyanogenmod 10.1 or just ten, not sure. Once I did that everything went down the toilet. I didn't know you had to flash apps so for whatever reason only my app installs I did pre rom installation worked, such as facebook, twitter, instagram. Google playstore didn't work, and neither did gmail. also my contacts wouldn't open either sometimes which was strange. Then like an idiot I installed an update, mentally I was thinking it was a stable update, little did I know it said experimental, It ridded my phone of everything... gapps are all gone, even the play store. The solution I found online was to install flashed gapps, so I did. When I click to open it, it says there is nothing to support it so it won't open. so basically I use the internet browser for everything, and it is very tedious.
What I want to happen and need helping doing:
Either-
Uninstalling cyanogenmod and putting a stock rom on there, which would be heavenly (which i've tried to do and odin always fails to fully download it)
or,
getting my gapps on my phone and having whatever mystery software to support these files on there.
PLEASE HELP ME, I'M AT THE BREAKING POINT, I CAN'T TAKE IT
**PHONE INFO**
Samsung Galaxy SIII
Sprint
Android version 4.2.2
Cyanogenmod version: 10.1-20130304-EXPERIMENTAL-d2spr-M2
Uhm, why don't you just flash a table version..
Sent from my HTC One X using xda app-developers app
Beerad875 said:
Uhm, why don't you just flash a table version..
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
What does that do? Hardcore noob status
Galaxy S3 help
chrisusotattd said:
**PHONE INFO BELOW**
I feel as if my situation is really unique and I can only find help by posting
Okay, so it starts like this. I rooted my phone using odin3 and it worked splendidly and everything worked such as gapps. Then I decided to try installing roms... I installed cyanogenmod 10.1 or just ten, not sure. Once I did that everything went down the toilet. I didn't know you had to flash apps so for whatever reason only my app installs I did pre rom installation worked, such as facebook, twitter, instagram. Google playstore didn't work, and neither did gmail. also my contacts wouldn't open either sometimes which was strange. Then like an idiot I installed an update, mentally I was thinking it was a stable update, little did I know it said experimental, It ridded my phone of everything... gapps are all gone, even the play store. The solution I found online was to install flashed gapps, so I did. When I click to open it, it says there is nothing to support it so it won't open. so basically I use the internet browser for everything, and it is very tedious.
What I want to happen and need helping doing:
Either-
Uninstalling cyanogenmod and putting a stock rom on there, which would be heavenly (which i've tried to do and odin always fails to fully download it)
or,
getting my gapps on my phone and having whatever mystery software to support these files on there.
PLEASE HELP ME, I'M AT THE BREAKING POINT, I CAN'T TAKE IT
**PHONE INFO**
Samsung Galaxy SIII
Sprint
Android version 4.2.2
Cyanogenmod version: 10.1-20130304-EXPERIMENTAL-d2spr-M2
Click to expand...
Click to collapse
Which model of Galaxy S3 do you have? Settings -->About Phone
I have a i9300, with Cyanogenmod 9.1 on it. Phone model will decide which ROMs are available.
Soundwve said:
Which model of Galaxy S3 do you have? Settings -->About Phone
I have a i9300, with Cyanogenmod 9.1 on it. Phone model will decide which ROMs are available.
Click to expand...
Click to collapse
SPH-L710
re: Galaxy S3 help
Sent a message to you, chrisusotattd.
To anyone else with this problem, here is the long version of solving this issue. (I can not post links as I have not hit the 10-post minimum, so it is the long version.)
Okay, first step (important!) is to boot into recovery and wipe the Dalvik Cache. Second, wipe cache partition.
Third, wipe data/factory reset. (I did this on my phone.)
This could be part of your problem, as all the apps you installed prior to flashing Cyanogenmod are still there.
Go to the Cyanogenmod home page, hover over the 'get Cyanogenmod' link, and look under 'all devices' on the right. On the next page, select the manufacturer/vendor for your phone (Samsung). Find your Galaxy S3 version (mine is i9300) and click on the stable Cyanogenmod ROM button for your phone. (If there is not a stable version, a 'release candidate' will work too.)
Below the 'release candidate' button, you will find a link to instructions for installing Cyanogenmod. The page for this contains a link to a Clockworkmod (CWM) Recovery, which I'd recommend installing it before you flash the new ROM, if you do not already have it. (The page may be grumpy and not load. Hit refresh, it will work.)
I have a version of CWM, and it works far better than the stock recovery.
I used Odin to flash my S3 as well, so use that instead of Heimdall if you prefer. Once you flash Clockwork Recovery, you can flash the Cyanogenmod ROM thru the CWM recovery.
I just bought a Gear 2 Neo and when Pairing it with my S3 the watch stays on the startup screen all the while my S3 shows they are paired. The phone never connects to download the software from the watch, i did however get it to work with my Galaxy Tab 3 but not with my S3. Does anyone know a way to get this to work.
P.S. I did a factory restart and tried it with no additional software on the phone except for the Gear Manager from Samsung. I thought there might be something conflicting. The S3 is running android 4.4.2.
if you are running a custom rom then put your phone back to stock and it'll work properly. someone here was having issues with their phone & the gear 2 and it was all because they were running the latest Jedi rom.
rlee008 said:
if you are running a custom rom then put your phone back to stock and it'll work properly. someone here was having issues with their phone & the gear 2 and it was all because they were running the latest Jedi rom.
Click to expand...
Click to collapse
I am currently running stock and have not rooted my phone. I did factory rest it and tried to install the gear manager but it wont run correctly on my S3. the interface just keeps flashing white and wont pair properly. All this time the phone is still on the startup screen.
Hey all, As I'm sure other people are I am trying to get my Samsung Gear 2 connected to my Galaxy S5 running the latest CM12 nightly. Unfortunately, Since Lollipop, as far as I'm aware nobody has been able to get the Gear Manager to function correctly on Non-Touchwiz roms.
I have tried just about every combination of installing, uninstalling and restoring from TW roms with Titanium backup that you could think of. Nothing will allow my device to function correctly. Upon pairing with the app, the most common crash is HostManager. The watch will pair but as soon as it does, You get repeated messages of 'Unfortunately, HostManager has stopped.' and the Gear manager app stays at 'Conneting to Gear'. The only way to stop the crash loop is to turn of Bluetooth or Freeze the HostManager app.
Surely there is some way to fix this? I haven't seen a lot of people looking in to it despite the fact that a number of people must want to run their Gear device with an AOSP-type rom?
Here is the logcat from the installation of the HostManager APK (I don't think this is useful, as it all installs correctly but added anyway just in case): pastebin<dot>com/eWp2AuHd
And here is the Logcat from the crash of HostManager: pastebin<dot>com/N0eWGZRL
Sorry about the links, The logcat is too long to fit in an XDA post and I'm below the post count required for posting links, and I don't want to meaninglessly post just in order to insert links.
As you can see I left a large buffer of the logcat around the crash in case there is any other important information about what is going on.
Any help here would be appreciated. If you can fix it and have a PayPal I'll buy you a beer or two
So sad...
I just installed Resurrection Remix 5.1 on my S5. It looks really better than the Samsung Lollipop (and works better)... but no way to link my Gear 2...
Did you find something helpful ?
Albadros said:
So sad...
I just installed Resurrection Remix 5.1 on my S5. It looks really better than the Samsung Lollipop (and works better)... but no way to link my Gear 2...
Did you find something helpful ?
Click to expand...
Click to collapse
Unfortunately I was unable to get it to work. I went and bought a Gear Live insead.
Did this with unrooted HTC m9 and unrooted Gear 2 with latest FW.
Deleted all the files installed on phone from gear manager.
Download latest GM files (extract/ed from APK)
Install every apk except Host Manager and install Gear Manager App as last
Open GM and connect your Gear 2. As soon as it tries to install Host Manager hit home button/go to your file explorer App on your Phone and install Host Manager 2.2.14100299
Open GM again and cancel Host Manager installation.
Have a little patience and it should show you the option to accept the terms.
Set Notifications in GM App on your phone.
If you prefer Root for Gear then you can root your Gear without problems and you don't have to do this all over again.
Sideloading APK's working fine, had S Voice running but coulndn't connect to watch yet.
Changed Bootscreen, sounds and more without problem.
Redmen What OS are you running? 5.0.2? or 5.0.1?
daroota said:
Redmen What OS are you running? 5.0.2? or 5.0.1?
Click to expand...
Click to collapse
5.0.2 with software: 1.32.401.15
Mmmm, I'm running 5.0.2 CM12S on my OnePlus One, and a friend and myself cannot get it to connect in Gear Manager and activate on the watch itself. My thought was since none of the Samsung Galaxies have 5.0.2 yet, Samsung hasn't build a apk for that version yet. I hope they will update it soon.
Wondering the same thing, love my nexus but rendered my gear 2 pretty much worthless. Any advancements towards this?
Sent from my Nexus 6
There is one way I know how, but it's a royal pain in the butt.
Do a nandroid restore to 4.4.4, install the old gear software like it once was installed. then update to Lollipop like normal, and install the latest gear manager. The problem is that the watch has to BE paired already to your phone, and without wiping (so you don't loose your bluetooth unique ID) update to keep the pair.
In my case, I took a nandroid backup before I updated to lollipop, so I restored it, paired it, used titanium backup to copy my programs and data for the watch and the bluetooth ID, then restored back to lollipop because it was a OTA update which didn't change my settings... updated to the latest Gear manager, and restored my Bluetooth settings= Profit...
However 2 problems I am having, is my watch doesn't want to answer the phone, and Saproviders keeps crashing, so I removed saproviders... everything else works fine.
daroota said:
There is one way I know how, but it's a royal pain in the butt.
Do a nandroid restore to 4.4.4, install the old gear software like it once was installed. then update to Lollipop like normal, and install the latest gear manager. The problem is that the watch has to BE paired already to your phone, and without wiping (so you don't loose your bluetooth unique ID) update to keep the pair.
In my case, I took a nandroid backup before I updated to lollipop, so I restored it, paired it, used titanium backup to copy my programs and data for the watch and the bluetooth ID, then restored back to lollipop because it was a OTA update which didn't change my settings... updated to the latest Gear manager, and restored my Bluetooth settings= Profit...
However 2 problems I am having, is my watch doesn't want to answer the phone, and Saproviders keeps crashing, so I removed saproviders... everything else works fine.
Click to expand...
Click to collapse
This isn't a viable option for those of us that want to swap to an AOSP based ROM. I've tried this, and while it will pair with the phone OK, the gear manager software doesn't work, therefore you can't receive notifications on the watch. The only function that works when you do this is answering phone calls on the watch, as this can be done without Gear 2, as it uses A2DP (I think) so will work with any bluetooth phone for hands-free.
There is also no way to OTA update from a TW ROM to a custom ROM, unless you are referring to an OTA update from a 4.4.4 based AOSP like CM11 to 5.X/CM12?
Correct. I went from cm11 to cm12 on my one plus via OTA.
Sent from my A0001 using XDA Free mobile app
As in the title states I have the galaxy tab 2 7.0 and recently I installed CWM and a ROM and everything looked like it went right however after I reloaded my tablet nothing seems different it jus seems to return to stock setting and now I cant do the OTA software update which means now certain apps and games I can no longer uses as it says my device isnt compatible. My goal was to simple update from Jellybean to at Least Kitkat.
Can someone help me. where did I go wrong?
Fleacore210 said:
As in the title states I have the galaxy tab 2 7.0 and recently I installed CWM and a ROM and everything looked like it went right however after I reloaded my tablet nothing seems different it jus seems to return to stock setting and now I cant do the OTA software update which means now certain apps and games I can no longer uses as it says my device isnt compatible. My goal was to simple update from Jellybean to at Least Kitkat.
Can someone help me. where did I go wrong?
Click to expand...
Click to collapse
Go to sammobile and flash the latest stock firmware for your device .
Newyork! said:
Go to sammobile and flash the latest stock firmware for your device .
Click to expand...
Click to collapse
Well after a short research I found a ROM called Resurrection Remix, loaded with 5.0.2 (or Lollipop) however now everything is force closing and I barely got my laptop to see it as MTP again after installing a new Binary (glad that did that trick for that) but I cant get it to boot into CWM Recovery bc I cant access the app the only thing it will let me do right now is change the Binary.
How can I fix this issue?
Edit: Okay so I got that solved with doing a factory reset twice, booted in CWM, loaded up the GApps. Now just wondering if there is away to make it not seen with phone options like the dialer or msgs as its jus a plan old tablet, doesnt take a sim card and has no carrier. I do have the source code but I am not tweaking that til I get a better understanding of it.
After a lot of research and tries (amazingly without bricking) I am now running an even newer version of a CM 13 Marshmellow
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