[Q] Bluetooth issue in KatKiss 4.3 #024 - Eee Pad Transformer Q&A, Help & Troubleshooting

I've setted the home button long press action to "Google Now", then i setted it to "none" but it still goes to google now, i've tried to set it to another action, but it remains on google now.
If I connect the Tf101 to a devices with bluetooth tethering it do not go online, but all seem to works, no problems with stock rom on this.

Phoenixct said:
I've setted the home button long press action to "Google Now", then i setted it to "none" but it still goes to google now, i've tried to set it to another action, but it remains on google now.
If I connect the Tf101 to a devices with bluetooth tethering it do not go online, but all seem to works, no problems with stock rom on this.
Click to expand...
Click to collapse
From what I've read, Bluetooth tethering to a cellphone is not supported in either 4.2 or 4.3 - strangely enough though, when I moved from ICS to EOS 4.2 my BT tethering continued to work all through the EOS and KAtKiss ROMs, but it failed after I moved up to KatKiss 4.3 - at which point it no longer worked on 4.2 either. My understanding is that this is an Android thing, rather than a KatKiss thing, and it may never be resolved as the newer versions of Android place restrictions on loading drivers that aren't originally included. I would love to be proved wrong on this by a version of 4.3 with working BT tehthering.
The only way I was able to get it working again was by going back to ICS.

Mike_NZ said:
From what I've read, Bluetooth tethering to a cellphone is not supported in either 4.2 or 4.3 - strangely enough though, when I moved from ICS to EOS 4.2 my BT tethering continued to work all through the EOS and KAtKiss ROMs, but it failed after I moved up to KatKiss 4.3 - at which point it no longer worked on 4.2 either. My understanding is that this is an Android thing, rather than a KatKiss thing, and it may never be resolved as the newer versions of Android place restrictions on loading drivers that aren't originally included. I would love to be proved wrong on this by a version of 4.3 with working BT tehthering.
The only way I was able to get it working again was by going back to ICS.
Click to expand...
Click to collapse
With Cyanogenmod this issue was present passing from android 4.1 to 4.2.2, but was resolved, but in that case was problem with the server side, i've problem from client side. maybe was the same bug?

Here's the bug resolved in cyano: https://jira.cyanogenmod.org/browse/CYAN-96

I think timduru have fixed this, in the 025 version changalog these is a "fix bluetooth tethering"

Confirmed, BT Tethering working in build 025!

frederuco said:
Confirmed, BT Tethering working in build 025!
Click to expand...
Click to collapse
Excellent news! - this is what was needed to get me to move from ICS back to JB again.

With Kitkat 4.4 around the corner there is some major features with bluetooth being introduced with 4.4. With 4.3 working so well currently I can only imagine how seamless 4.4 could be but I am probably getting my hopes up.
Sent from my Transformer TF101 using Tapatalk

Can someone tel me if in KatKiss 4.4 the bluetooth tethering is working ?
Thanks

saue0 said:
Can someone tel me if in KatKiss 4.4 the bluetooth tethering is working ?
Thanks
Click to expand...
Click to collapse
Yes, it works.

Related

Physical Keyboard not working with 4.1 <?

Hi Guys,
I have been running 4.1.2 stock and it's been fine with my samsung physical keyboard dock:
http://www.amazon.co.uk/Samsung-Key...sung+galaxy+note+10.1+keyboard#productDetails
However, I've really needed to get multiple user profiles on the device. I've tried a few roms such as cyagonenmod (10.1 and 10.2) and Illusion 4.2.2 to get Android 4.2.2, but every time I plug the tablet into the dock, it freezes up and restarts. Am I installing the wrong rom? Or am I missing a kernel or something? If needed, I would willing to unroot and go back to stock to get the keyboard working again, but I really wanted multiple users on the device
I've searched everywhere, but I couldn't find any sort of solution (on xda and google).
Thanks!

[Q] All apk that require location not working nexus 5

Hi
I am in a dilemma guys.... my nexus 5 is fully updated to 4.4.2 and i got it from the retailer already updated to 4.4.2.
Now, the problem is that any apk e.g. youtube, maps etc. that require my location aint functioning at all.
YOUTUBE CANT EVEN SIGN ME IN DAMN IT!!!.....
Also when i click any clip to watch, it just keeps on loading for ever and never plays JACK!!!
I am so frustrated & i am sure others have the same problem.
Btw, i am right now, located in kuwait wich is a country in the middle east (for those who would like to know).
LTE is fully functional, supported & working just fine because i have the international variant.
On a side note: i rooted my device and installed cwm but the problem persisted from the initial device boot up.
Questions:
A: Could someone help me pls??
B: Would downgrading my 4.4.2 to 4.4 or flashing a custom rom fix the issue??
fixed the problem with cm11 but google now not working
grinzlo said:
Hi
I am in a dilemma guys.... my nexus 5 is fully updated to 4.4.2 and i got it from the retailer already updated to 4.4.2.
Now, the problem is that any apk e.g. youtube, maps etc. that require my location aint functioning at all.
YOUTUBE CANT EVEN SIGN ME IN DAMN IT!!!.....
Also when i click any clip to watch, it just keeps on loading for ever and never plays JACK!!!
I am so frustrated & i am sure others have the same problem.
Btw, i am right now, located in kuwait wich is a country in the middle east (for those who would like to know).
LTE is fully functional, supported & working just fine because i have the international variant.
On a side note: i rooted my device and installed cwm but the problem persisted from the initial device boot up.
Questions:
A: Could someone help me pls??
B: Would downgrading my 4.4.2 to 4.4 or flashing a custom rom fix the issue??
Click to expand...
Click to collapse
hey guys i managed to fix the problem by flashing cm11 but i cant get the google now to work with my voice..... is there something i can do to fix this ? my cm version is based on 4.4... should i wait for the stable 4.4.2 version?
Is google supported or allowed in your country? If location is disabled then you wont get those things.

bluetooth not working after update

i updated CM11s and now bluetooth is not working anymore.
if i try to turn it on, it tries to activate bluetooth, then goes back off.
a full wipe didn't solved the problem, but it works with a clean rom (i tried mahdi, but i had to restore backup since monday i'm leaving for holidays and i don't have time to restore all i need on the mobile now).
i know i'm not giving many infos to have some help, but if you give me some directions i can try to fix it.
also, is it possible to reinstall CM11s with twrp or just through fastboot?
thanks!
I also have trouble with Bluetooth.
It tries to send file but either the app crashes or the file can't be sent.
Any info in that?
seems like noone has this kind of troubles
Hi! I just ran into the same problem: after upgrade to Cyanogen OS version 11.0-XNPH05Q, my bluetooth connection turns out to be unusable.
It first seems to connect (after "search for devices" is hit), but immediately when the call is initiated, the connection drops out (nokia BH-105).
Will check with my car installation too.
Is it possible to downgrade to previous Cyanogen OS version - I even don't know, which one was it... but at least it was working well!
Also having troubles with Bluetooth and my car-system since the 5Q update.
Before latest 5Q update everything works fine, but now neither of the devices can see the other one anymore
already deleted existing pairing in my car-system, but can't set up new pairing...
wondering if change of kernel can be a solution tho?
loth77 said:
i updated CM11s and now bluetooth is not working anymore.
if i try to turn it on, it tries to activate bluetooth, then goes back off.
a full wipe didn't solved the problem, but it works with a clean rom (i tried mahdi, but i had to restore backup since monday i'm leaving for holidays and i don't have time to restore all i need on the mobile now).
i know i'm not giving many infos to have some help, but if you give me some directions i can try to fix it.
also, is it possible to reinstall CM11s with twrp or just through fastboot?
thanks!
Click to expand...
Click to collapse
geri.st said:
I also have trouble with Bluetooth.
It tries to send file but either the app crashes or the file can't be sent.
Any info in that?
Click to expand...
Click to collapse
loth77 said:
seems like noone has this kind of troubles
Click to expand...
Click to collapse
nixnix33 said:
Hi! I just ran into the same problem: after upgrade to Cyanogen OS version 11.0-XNPH05Q, my bluetooth connection turns out to be unusable.
It first seems to connect (after "search for devices" is hit), but immediately when the call is initiated, the connection drops out (nokia BH-105).
Will check with my car installation too.
Is it possible to downgrade to previous Cyanogen OS version - I even don't know, which one was it... but at least it was working well!
Click to expand...
Click to collapse
J0ch3nK said:
Also having troubles with Bluetooth and my car-system since the 5Q update.
Before latest 5Q update everything works fine, but now neither of the devices can see the other one anymore
already deleted existing pairing in my car-system, but can't set up new pairing...
wondering if change of kernel can be a solution tho?
Click to expand...
Click to collapse
https://jira.cyanogenmod.org/browse/BACON-2822
nixnix33 said:
Hi! I just ran into the same problem: after upgrade to Cyanogen OS version 11.0-XNPH05Q, my bluetooth connection turns out to be unusable.
It first seems to connect (after "search for devices" is hit), but immediately when the call is initiated, the connection drops out (nokia BH-105).
Will check with my car installation too.
Is it possible to downgrade to previous Cyanogen OS version - I even don't know, which one was it... but at least it was working well!
Click to expand...
Click to collapse
this is still CM and not oxygen OS

[Q] Which unlock tool to unlock v4.1.1?

Hello I am still dealing with a weird problem that I posted on this forum over a year ago that was never resolved. Basically my tablet is stuck running Android version 4.1.1 (Build JRO03C.US_epad-10.4.4.25-20121228) because if I upgrade to any new versions (whether I do it as OTA or via micro USB) my wifi card stops functioning (it does not see any networks). Anyways I even went so far as to RMA it and Asus said they fixed it, shipped it back to me, but in reality all they did was roll me back to 4.1.1, saw the wifi was working and shipped it back to me saying they "fixed" it. Well of course the second I got it back I installed the OTA and wifi broke again... So I just rolled back to 4.1.1 and said screw it, I just won't update it anymore. Well this week I figured I'd try installing the latest OTA and hoped that this version would not kill my wifi, unfortunately the same exact issue has occurred and thus I have once again rolled back to v4.1.1 and my wifi works perfectly...
TLDR; Anyways apologize for the rant/story but basically I am stuck with using version 4.1.1 of Android and am considering flashing a custom rom to try and resolve some issues I am having with the stock rom's wifi, however the official bootloader unlock tools only say they work on version 4.0 (ICS) or version 4.2 (JB). I'm stuck on v4.1.1 so which tool should I use (or am I out of luck)? Thanks
v7 worked your JB version, but I think v8 will work as well. Just try them both - it's just an app. Either it works or not....
But that is the weirdest thing I've heard in a while (reg. WiFi).
What have you done on your router side? I cannot believe this is a problem with the tablet's wifi card.
Is this 'wifi not working' consistent on any router, any network?
Did you reset the router, change the channel?
Do you have possible interference: microwave, bluetooth speakers, bluetooth enabled or any other device that uses radio waves anywhere in the vicinity of the tablet?
berndblb said:
v7 worked your JB version, but I think v8 will work as well. Just try them both - it's just an app. Either it works or not....
But that is the weirdest thing I've heard in a while (reg. WiFi).
What have you done on your router side? I cannot believe this is a problem with the tablet's wifi card.
Is this 'wifi not working' consistent on any router, any network?
Did you reset the router, change the channel?
Do you have possible interference: microwave, bluetooth speakers, bluetooth enabled or any other device that uses radio waves anywhere in the vicinity of the tablet?
Click to expand...
Click to collapse
Thanks appreciate the reply - I just wasn't sure if using the wrong unlocker could brick my device... I'll give 8 a try first then 7 if necessary. The ironic part is that it requires a network connection to complete the unlock operation (I guess so Asus can cross your S/N forever off of their list of devices under warranty).
I agree that this is a strange problem as I have not seen anyone else report it. Basically I tried resolving this about 13 months ago with the help of this board and as mentioned I finally had to RMA it, but ASUS just rolled the version back instead of fixing anything and at that point I just wanted to enjoy using my tablet more than I wanted to fight with ASUS's customer service reps who effed up the first RMA job (the language barrier was also apparent in my interactions with them)...
Since over a year has gone by since the last time I tried an OTA, I hoped that the latest update would not have the same issues but alas, I'm not that fortunate.
As far as what I've tried - I have tried connecting to different networks and changing router channels and checking for interference, but the thing is, I'm quite certain the problem is with the tablet. When I first had the problem I lived in an apt building where I could 'see' 10+ wifi networks at any given time on all different channels with different routers/security settings etc. As soon as I applied the OTA the tablet could no longer 'see' any of them (even as I sat with my laptop/phone connected to wifi right next to it). I now live in a house (and have a different ISP, and a different router) and tablet works perfectly when on version 4.1.1. I don't have as many wifi networks visible from my house, but can still see a few of my neighbor's wifi networks both on the tablet (v4.1.1) and on other devices. But the second that I upgrade, all of them disappear from the tablet's view (but continue to be visible/work on other devices). I have turned wifi on/off, turned airplane mode on/off, tried connecting via wifi direct, rebooted, cold booted, booted into recovery, factory reset all data, etc. but nothing works because the tablet cannot see any wifi networks. And the second that I rollback to version 4.1.1 the wifi works perfectly... I have upgraded and rolled back probably at least 6 times and it is always the same result.
I do also get another weird side affect when I upgrade - the tablet refuses to turn off when I'm on any version higher than 4.1.1. So if I press "Shut Down", the tablet displays "shutting down" and the screen goes black and becomes non-responsive (as do the buttons, just as you would expect when turning off), but it does NOT actually shut down because if I come back 30 mins, an hour, 2 hours later I can feel it running very hot. The only way to truly shut it down is to let the battery drain...
So maybe a better question on my part would have been, do you think installing a custom ROM will even help resolve this issue? Or should I continue using 4.1.1 and not risk making the situation worse with custom ROMS?
WiFi problems are often kernel related..... Did you always take the update OTA?
Did you ever try to flash the latest firmware version manually? OTA updates do go wrong sometimes....
Although repeatedly???? It's weird. Maybe the server your tablet pulled the OTA from hosts a bad copy????
If you do not want to unlock, manually flashing the firmware would be one thing to try. OTA's patch the existing system, replace old files with new ones where necessary. Manually flashing the firmware replaces everything - a totally new installation of everything: bootloader, recovery, kernel, system and data.
But you cannot make it worse by flashing a custom rom. You unlock, flash a custom recovery (which does not change anything else on your system), then you make a nandroid (backup) of your current 4.1.1 system before you flash a rom. So you would always be able to go back to where you are now. On a custom rom you could even try out different kernels, which often are the root cause of wifi problems..
The thing is: If you want to flash a current custom rom like CROMi-X, based on Asus JB 4.2.2, or CROMBi-KK/CM11 which are KK roms, you always have to update your bootloader first. Your .25 bootloader is too old for any current rom.
You can easily do it once you have a custom recovery installed, but even easier would be to update to the latest Asus firmware 10.6.1.14.10 (after unlocking), then flash the custom recovery (TWRP 2.8.1.0), then flash a rom of your choosing.
Downside of this route would be you wouldn't have that 4.1.1 nandroid I mentioned earlier.....
Nahhh - thinking about it, I would recommend you go this route:
Unlock,
flash an older version of TWRP compatible with your current bootloader (TWRP 2.6.1.0 is ok)
make a nandroid of your current system
do a full wipe of cache, Dalvik and data in recovery
flash the 10.6.1.14.10 bootloader in recovery (I can talk you through it)
flash TWRP 2.8.1.0
flash a rom of your choice
Check out my guide, link in my signature, and let me know if you have questions
Thanks - I was able to successfully unlock my device with v7 of the unlock tool (v8 wouldn't even install). Thanks too for the advice on how to flash a custom rom safely. I've never flashed a custom rom before (have rooted a different android device before tho), so I appreciate any help.
I downloaded the blob file for TWRP 2.6.1.0 from here (techerrata.com/browse/twrp2/tf700t), but not sure how to proceed next, (also I don't see a link in your signature to your guide, but I am running a bunch of script blocking addins so maybe that's why) seems like all the guides I am finding say I need to get a copy of a fastboot program (but don't provide links), where can I find that? Again, I appreciate the help.
Sorry, my bad, I don't have a signature on XDA - wrong forum. LOL
My thread is here: http://forum.xda-developers.com/showthread.php?t=2688891
Ask any questions you may have in that thread, but it should cover your questions - I hope

How far can I upgrade my GT-N8013?

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

Categories

Resources