yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 10.1 (2014 Edition) Original Android D] DeanoD:
Mate -- I have great news--if you use the Hacker's Keyboard App. Look at the setting under this specific app as it HAS a setting for Spanish built right in to it! I just accidently "added" multiple language support to it! Check the settings!

There is a Spanish board layout there. Not a real fancy app, but it is clean and REALLY configurable. Hope this makes it easier, but it looks like you can even switch bdtween language layouts on the fly! ;-DeanoD
[Galaxy Note 10.1 (2014 Edition) Original Android D] njones23:
My SM-P600 stock android 5.1.1 supports widevine L1, so HD streaming is supported in apps like Netflix and Vudu. A fresh install of lineage-14.1-20180505-nightly-n1awifi-signed.zip only supports widevine L3. I confirmed this using the "DRM Info" app. Due to this, HD streaming from major streaming apps is not supported. I noticed this right away after installing LineageOS because I could only stream in SD from Vudu. Is there anything that can be done about this? The stock android for this runs like a pile of $h*T and I really don't want to go back.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Goudhaantje:
This has worked ok for me, combined with the lineageos install guide

twrp-3.0.2-0-lt03ltexx-4.4.img (3.1.1 didnt work)

Heimdall git (stable released heimdall didn't work in ubuntu 18 LTS)

open_gapps-arm-7.1-nano-20180613

lineage-14.1-20180608-nightly-lt03lte-signed

whenever you are in loops or the device seems to hang during the update, press powerbutton very long 1m+ this will shut the device down.

left with some minor issues:

- on low battery button leds go on but dont go off (when buttons lighting is disabled)

- screen on when connecting charger (screen goes very bright, doesnt go back off, charging icon doesnt update or go green)

- at boot it complains the settings app didnt start and I have to manually restart it
[Galaxy Note 10.1 (2014 Edition) Original Android D] x61tab:
I have had this ROM for a while now but lately, its taking a very long time to charge. I have even updated the ROM to the recent released but the problem persists. It's been 15 hrs since I started charging and its only 68% changed. Anybody else having the same issue?
[Galaxy Note 10.1 (2014 Edition) Original Android D] rayik:
Maybe the battery is starting to go bad. My battery would take overnight to charge and would run out in a couple of hours. Changed battery and back to normal. Its easy to change.
[Galaxy Note 10.1 (2014 Edition) Original Android D] ^tyrant^:
Does anyone else have problems with apps like AZ Screen Recorder taking screen shots? video capture works with it just not screenshot. And also Calcy IV for pokemon go is not able to get a screen capture as well.. I can manually take them, and they work from the extended power menu..

Any ideas?
[Galaxy Note 10.1 (2014 Edition) Original Android D] louvass:
Thanks

This runs great on my Tab. Thank you for your hard work keeping this tablet alive.
[Galaxy Note 10.1 (2014 Edition) Original Android D] diabl0w:
Same here... mine coincidentally was also at 68% when I got to it this morning. I wonder if it stops charging at 68
[Galaxy Note 10.1 (2014 Edition) Original Android D] forcecorn2001:
is it not possible to PORT Tab S3 for the Note 10.1 2014 edition?
[Galaxy Note 10.1 (2014 Edition) Original Android D] louvass:
I installed this and tried doing the update and install after but it boots to TWRP but there is no file showing up to install where is the download file located so I can update it manually. Thank you for bringing us this for our tab
[Galaxy Note 10.1 (2014 Edition) Original Android D] Goudhaantje:
the download location has changed in lineageos, its now a shorter path /data/data/org.lineageos.updater/app_updates
[Galaxy Note 10.1 (2014 Edition) Original Android D] Garrett1972:
I've had several ROMs on my Note 10.1 2014 Edition. Generally always worked well, but ended up going back to stock just due to some random issues here and there. Loved this ROM, seems like new life on my Note 10, but I can't get a GPS lock. GPS not found error. Wasn't an issue on the stock ROM.

I've wiped and re-installed a few times, everything else looks great, but the GPS lock issue comes up.

I like this because it is certified, and I can run Pokemon Go without issue, except for no GPS lock. On stock, it will lock, but it is so much slower and laggy.

Anything I am missing? Thanks in advance!
[Galaxy Note 10.1 (2014 Edition) Original Android D] internetpilot:
Anyone else having trouble getting S-pen command working on the 8/11 nightly? It says there's no S-pen compatible device under minimal requirement checks when SPC is loaded at boot. Dirty flashing the 8/4 nightly gets it working fine again.
[Galaxy Note 10.1 (2014 Edition) Original Android D] DeanoD:
Battery Issues?

I'm currently trying this ROM on my spare smp600. It installs nicely and seems to run smoothly and quick. I've also tried the Resurrection Remix which I like with all the extra features and settings. But, it runs a wee bit wonky and crashes often. I don't seem to have any of the issues that others have had with this build. The only issue I have is poor battery functions, and slow charging, which may also be due to a battery that needs replacing. I'm wondering if I shouldn't just crack it open and put a new battery in it. IIRC this is the only one of our trio of tabs in the family that has not had a new battery installed. I'm just tired of paying someone else to do the install. Has anybody else here had expeiences with battery changing? Is it something that CAN be done by a person with some limited electronics skills? Anybody else running Titanium Backup? There are some compatibility issues, but it does seem to work well.

But I am seriously thinking on this ROM for a daily driver. I like having the reliability levels that it gives me. ;-DeanoD
[Galaxy Note 10.1 (2014 Edition) Original Android D] wadken1:
Yes, I've changed the battery in mine and it's not too difficult - shouldn't more than 30mins. If yours is still the original then it's almost certainly on the way out and I would recommend a change. Batteries are easy to get hold of (think I bought mine on Ebay). You'll need some plastic tools and possibly a small Torx driver. Sometimes you can get a battery along with the necessary tools then there are dozens of listings small inexpensive kits that will do the job. I recommend you look up one or two of the "tear-down" or "replacement" videos on Youtube -helps to avoid making silly mistakes like snapping the plastic case clips.
[Galaxy Note 10.1 (2014 Edition) Original Android D] DeanoD:
Thanks for the reply. With keeping three smp600's all current and clean, I actually have a battery ready to go. I've had some experience building PC's over the years. I did things with PC's that worked if only because I lacked the fore knowledge of "not knowing things that shouldn't work".

Heck, I ran BATCH FILES IN DOS! (Yep, I'm THAT old) I have the videos and the toolkit for the battery job. But, my hands might not be up to the detailed work needed. But, I do have an old Acer a500 to sacrifice as a training trial. If that goes well, I may jump in on the samsung tab.

Wish me luck! ;-DeanoD
[Galaxy Note 10.1 (2014 Edition) Original Android D] wadken1:
Yes indeed!! Good Luck.......BUT ..... it's really not that hard -it's nothing like breaking down and rebuilding a mobile phone which I've done more than once recently and I suspect I'm a similar age to yourself. I too wrote DOS batches files.

Cheers
[Galaxy Note 10.1 (2014 Edition) Original Android D] vinayburman:
Flash Prime kernel, it will work.
[Galaxy Note 10.1 (2014 Edition) Original Android D] zole2112:
I changed my battery as well, one of the easiest I've ever changed actually. this is what I followed https://www.ifixit.com/Guide/Samsung+Galaxy+Note+10.1+2014+Battery+Replacement/86078
[Galaxy Note 10.1 (2014 Edition) Original Android D] RuBB3rBunZ:
Kernel

This is a wonderful ROM! I been using it since its inception. I am using it now to type this post! Reason why I haven't bought a new tablet. Only problem I have is the battery life. I am still on its OEM. Anyway, I am wondering if you all are still using deathly kernel? I can't seem to find a post regrading its development. Is it abandoned? If so, what kernel do you use with this ROM and kernel app for settings? Thanks in advance!
[Galaxy Note 10.1 (2014 Edition) Original Android D] meekspace:
You wrote DOS files? That means me feel old.

I used to write machine code for the Z80
[Galaxy Note 10.1 (2014 Edition) Original Android D] louvass:
Charging

Is anyone else having problems charging, with the stock ROM its takes about 5 hours with lineage it takes 8 hours and never seems to charge as I am using the tab. Could it be the kernal I don't feel it's the battery because stock takes a lot less time. Thank you for your continuing work to bring us this.
[Galaxy Note 10.1 (2014 Edition) Original Android D] RuBB3rBunZ:
8 to 10 hours on lineage with OG battery and tablet off from like 10%. As far as stock goes, 5 hours sounds about right.
[Galaxy Note 10.1 (2014 Edition) Original Android D] TVscandle:
some problem

As of August 11, 2018, the deathly auditor application does not work with alert windows. Please confirm.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Hustensemal:
I contacted the developer of the app SPenCommand and he told me to test something in a console:

getevent -t /dev/input/event9

Event9 is the one that concerns the SPen-events for my device (SM-P600).

This command should show an event when the SPen is attached or detached from its dock. But these events did not appear. There were many events by hovering the SPen over the display, but not when detaching out of or attaching in the dock.

So the developer told me that there has to be a problem with the Rom, maybe it's a kernel-issue.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Leoxur:
Latest update
[Galaxy Note 10.1 (2014 Edition) Original Android D] Leoxur:
can someone tell me how to recover it?
[Galaxy Note 10.1 (2014 Edition) Original Android D] meekspace:
Is anyone else experiencing problems with LiveDisplay?

It's always off and can't be changed to auto, day or night.

It used to work. Hasn't been for a while.

I thought it might have been a ROM problem but after a few updates it's still not working.

I'm wondering if it's something I've done?

Any ideas?
[Galaxy Note 10.1 (2014 Edition) Original Android D] Ozark_8125:
Has anyone found a replacement battery that actually is decent??? I've tried three different batteries and they all suck after a week. One charges to 38% and the other dies if I increase screen brightness to max.
[Galaxy Note 10.1 (2014 Edition) Original Android D] wadken1:
I bought one that was sold as " Genuine original Samsung........etc etc" from Ebay. That was 2 years ago and it's been fine. I can' t really comment on any of the alternatives.
[Galaxy Note 10.1 (2014 Edition) Original Android D] internetpilot:
Out of the blue starting a few updates back, I started having problems with stuttering audio in all games, Google Play Music, YouTube, movies, etc. I reverted back to a known good version, but still had stuttering audio. I wiped everything, clean flashed (both an older known good and the latest), restored everything, and YouTube and Play Music still stuttered. Clean flashed again without restoring anything and still stuttering. I then tried a couple different kernels, but it didn't help.

I was beginning to think it was a hardware problem, but then I wiped everything again and flashed Resurrection Remix and same Gapps and no problems. Even restoring everything I still had no audio stuttering problems.

I like this ROM (especially the frequent updates), but I really just need a working tablet. Don't know if anybody else is encountering this or if this helps the dev at all, but I thought I'd mention it in case someone else has the same problem. I would love to get back on this ROM, so any suggestions would be appreciated.
[Galaxy Note 10.1 (2014 Edition) Original Android D] bschatzow:
I had the same problem on this device as well as my Samsung S2 tab 2016. It came out of no where and the only fix that I confirmed that worked was a complete wipe. I have asked many questions in a number of forums and never found out a definite cause or a fix. On one device I left it stuttering and it went away by itself after a few updates. Clearing cache, data, etc did nothing.
[Galaxy Note 10.1 (2014 Edition) Original Android D] internetpilot:
Yeah, a complete wipe didn't work for me. I even pulled my microSD card (stranger things have happened because of a bad microSD card), but that didn't help either. I really thought it was a failing hardware issue, but then tried the other ROM (Resurrection Remix) as a last resort.
[Galaxy Note 10.1 (2014 Edition) Original Android D] amitabh15:
You've got the same problem I had. The solder on battery connector on main board is cracked internally. I resoldered it after battery was falling from 90% to 40% in minutes and tablet was shutting down on 35%, Works fine now. Still on the original battery, lasts several days. Look online, you'll find pictures and solution to your problem.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Ozark_8125:
I had never run across that one - but sounds plausible. Thanks for the heads up!
[Galaxy Note 10.1 (2014 Edition) Original Android D] bschatzow:
Maybe I didn't understand what you meant by wipe. I had to go back to a factory restore first. Did you try a wipe and reflash after installing the remax? When I did my wipe I had to install one of the Samsung images first before I installed the Lineage rom.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Remy2099:
I can not get twrp to install the latest linage os zip.

I get error 7 and i have no idea why its the wrong.

can not install this package on top of incompatable data please try another package or run a foctory reset.

Updater process ended with error: 7

error installing zip file ...
[Galaxy Note 10.1 (2014 Edition) Original Android D] louvass:
You need a newer version of TWRP
[Galaxy Note 10.1 (2014 Edition) Original Android D] Remy2099:
I figured out what the problem was. I turned off zip Authentication or whatever it was called and it install just fine
[Galaxy Note 10.1 (2014 Edition) Original Android D] Joost53:
Did the same as ''louvass''.

- download update (via settings)

- reboot into recovery

- nothing happens in recovery

- had to go to /data/lineageos_updates/ and select the zip file there

- than update

I also have installed Open GApps updater.

This app does the same for GApp's than the update does for the OS

But when I choose there REBOOT TO RECOVERY AND INSTALL it actually reboots into recovery and starts installing (flashing) the new GApps.

So I think that manually having to select he OS update in TWRP is a small bug in the OS updater.

Question: Would it be possible to change to OS update location.

In Open GApps updater you can choose between internal storage and external.

This keeps your internal storage free for actual usage.

Using TWRP twrp-3.2.3-0-lt03wifiue.img
[Galaxy Note 10.1 (2014 Edition) Original Android D] 00schneider:
https://xdaforums.com/showpost.php?p=77613694&postcount=1817

"

Is anyone else experiencing problems with LiveDisplay?

It's always off and can't be changed to auto, day or night.

It used to work. Hasn't been for a while.

I thought it might have been a ROM problem but after a few updates it's still not working.

I'm wondering if it's something I've done?

Any ideas?

"

Sry something went wrong with quick reply.

Same here. GPS on/off - location cache, data protection/security reset + reboot doesn't work.

Also the battery optimization does not work. At the battery app, only Display and Standbay are shown, no other apps.
[Galaxy Note 10.1 (2014 Edition) Original Android D] leonelsr:
How did you guys manage to make S-Pen Power Saver work on LineageOS?

I seriously need this on Note 8.0 (N5100) but I don't even know where to look on the code. Can someone point me some directions? Then I could clone the repositories and try to port it on my spare time.

Thank you!
[Galaxy Note 10.1 (2014 Edition) Original Android D] DeanoD:
Lineage 15 At All Possible?

Sorry for the taboo O/T. In my searches, I keep getting mentions of a version of Lineage 15 (Android Oreo) that MAY or may not work on the smp600 notes.

There was a beta forum here on XDA, but it seems to be in limbo at this time.

Does anybody know of ANY effort to bring our tablets up to oreo. Even if we have to hack the new storage changes. I'm ready for testing ANY TIME.

;-DeanoD
[Galaxy Note 10.1 (2014 Edition) Original Android D] louvass:
Thank you for keeping our note 2014 alive with updates though I find major lag in games with all the nougat roms. I keep going back to stock for this reason, anyone else notice this with the latest roms?
[Galaxy Note 10.1 (2014 Edition) Original Android D] gmo18t:
searching for older 14.1 n1awifi downloads

Hi,

does anybody have still available some images (zip's) from end of september 2018 or

knows where I could find a respective download archive.

With the current available releases (back to 27th. of Oct. ) i get stuttering / crackeling audio !

Thanks

- gmo18t -
[Galaxy Note 10.1 (2014 Edition) Original Android D] GTLC60:
I had this problem, too. No update (dirty flashed) of LineageOS up to and including 14.1-20181123 solved this.

However, a full wipe (system, data, cache) and reinstalling 14.1-20181123 solved this audio issue for me :)

-GTLC60
[Galaxy Note 10.1 (2014 Edition) Original Android D] Poulpi06:
I've read that there's no more update for n1awifi, no more development

A chance for 15.1 or 16?????

Regards
[Galaxy Note 10.1 (2014 Edition) Original Android D] internetpilot:
For me it didn't matter which version I flashed back to (dirty or clean), the stuttering audio problem still existed. It started out if the blue. I had just about given up and was thinking it was a hardware issue, but I tried a different ROM and it worked fine. Tried this one again and the problem returned.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Bracher:
Hi to everybody!

unfortunately I've got a serious problem and need help: after I updated to the latest nightly my SM-P600 does no longer recognise my router. So no chance to get wifi enabled, it does in fact recognise all other routers near by, but unfortunately not mine even it its in a distance of 10 cm (ok after some time it suddenly does it recognise for a short time but looses the contact very soon). I got back to all available nightlies (because my last version was in fact an old one) but no chance at all, I tried without and with Magisk - no change. I made a complete new install, TRWP is the newest one, has anybody a proposal for me?

Solved

I went back to Stock ROM and flashed afterwards TRWP and the newest nightly of LOS now everything functions, obviously the WLan could be distorted after to much updates
[Galaxy Note 10.1 (2014 Edition) Original Android D] elvin3:
Could the developer answer this question ? that would be nice...

Regards,

JF
[Galaxy Note 10.1 (2014 Edition) Original Android D] Poulpi06:
Source:

https://www.nextinpact.com/brief/li...inaux--le-travail-sur-la-16-0-avance-6763.htm
[Galaxy Note 10.1 (2014 Edition) Original Android D] demmo81:
Looks like we will be stuck with Android 7.1.2 forever
[Galaxy Note 10.1 (2014 Edition) Original Android D] wadken1:
Boot Problems

I'm not able to get any Official build after 10/23/18 nor any Unofficial build after 11/10 to boot after flashing whether it's a clean (formatted Data partition) or dirty flash. The zips install without error usin gthe latest TWRP 3.2.3-0 but just get stuck on the Lineage boot animation screen. (a good clean install takes only a couple of minutes to get past this point). Anyone else having this problem?
[Galaxy Note 10.1 (2014 Edition) Original Android D] clioman:
Hello,

I have the same problems. Clean install after install latest lollipop rom from Samsung didn´t solve the problem. I´m confused.
[Galaxy Note 10.1 (2014 Edition) Original Android D] wadken1:
Well, at least that likely means that it's a software rather than a hardware problem. So it should be fixable for us once the fault is found .. and that's the tricky part as there are now maintainers actually working on this device and I don't personally have the necessary knowledge. The only thing I can think to do now is to try to attract the attention of the LineageOS team through their bug reporting system. In the meantime I might just try to update the bootloader if, I can find one, just to rule that out as an issue.
[Galaxy Note 10.1 (2014 Edition) Original Android D] DeanoD:
Yes!! I KNEW there had to be other users with this same prob. But every search I do on "boot loops" gets me nada. I'm currently running two P600 happily with Resurrection Remix Nougat 7.2. So far, no major problems with keeping them up. But, I have a 3rd tab, the oldest, that I was using as a guinea pig with several different ROMS including Linneage. And, sadly, that tab will now only run ROMs prior to Nov 17 of last year. And EVERYTHING that I've tried has crashed and stopped at the bootscreen animation for the ROM.

-did full wipe & format, re-downloaded all files, swapped out SD card,

-even tried a wipe and a restore from my other tabs.

I'm open to any suggestions to try, or I may end up with triple DOA tabs. I have some limited experience with most aspects of flashing -- I can offer my help, but this is a wee bit outta my pay grade.

Keep out tabs ALIVE! ;-DeanoD
[Galaxy Note 10.1 (2014 Edition) Original Android D] DeanoD:
Back with several observations. Because I have three tabs in my "stable", I can confirm that the boot loop problem(at least this one) is specific to the Lineage ROMs, but not in the current Resurrection Remix ones. I can say this since my other two tabs have NEVER run Lineage. Since the only difference with these tabs is simply that I've never flashed Lineage on either of them, we have to look into what is different between the RR or Lineage builds. So, we need to get the guys who KNOW about the builds makeups ,and we may find what causes the bootloop lunacy. ;-DeanoD
[Galaxy Note 10.1 (2014 Edition) Original Android D] clioman:
Hi. Which version of RR do you use? I have the same bootloops in RR Luis Roms.

Best regards

Gesendet von meinem LYA-L29 mit Tapatalk
[Galaxy Note 10.1 (2014 Edition) Original Android D] wadken1:
[MENTION=5482809]DeanoD[/MENTION] 's experience may point to a possible approach. Try flashing a stock Samsung lollipop rom first (you'll need a PC running Odin or Heimdall for that I think - don't think I've ever seen or heard of a twrp flashable stock zip ) and then do a completely clean flash (i.e. format data, wipe system & dalvik) of RR. Might try this myself but can't do that for a couple of days or so yet.
[Galaxy Note 10.1 (2014 Edition) Original Android D] DeanoD:
Where might we find a stock lolipop build as that would not be an original build for any of my tabs? Just curious if there is such an aminal these days. And just how "stock" it would have to be?

We need it to be just enough to reset the skewed parameters that we have acquired. THEN we could move forward. ;-DeanoD
[Galaxy Note 10.1 (2014 Edition) Original Android D] msbln:
It probably does not help. I had no issues when flashing LOS 14.1 over stock, but back then I used TWRP 3.1.0-1 (and still do, no need to change yet). Installing OTAs always worked fine, with the last one from 23rd of Jan'19. Magisk is not installed, instead SuperSU 2.82 is providing root.
[Galaxy Note 10.1 (2014 Edition) Original Android D] evitas:
Could anyone give me on advice on what to do?

My tablet is currently stuck on the boot animation after trying to update to the latest nightly, so I decided to do a clean install. I formatted data, and did an advanced wipe on everything. After that I tried to flash older versions and it's still stuck on the boot animation. I left it over night and it's still loading. I'm pretty sure I have the correct bootloader as well, since I've flashed lineage os before this happened.

Going from complete stock, flashing custom recovery and reflashing a custom rom still doesn't fix the issue.