yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 10.1 (2014 Edition) Android Developmen] AndyYan:
App Settings (Xposed), which I use to modify some preferences of other apps. I tried all versions I can get, and Temasek simply refuses them all. By "not working" I mean no settings made in the app would have any effect. Even when saving the settings for an app it would not kill the app in question. This seems to also be the case for Temasek CM13 if I remembered right.

Sent from Google Nexus 6P @ CM13
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Stevethegreat:
[MENTION=4467696]AndyYan[/MENTION]

To me a tablet should not be a giant phone and that's (mostly) what the "stock feel" achieves. Then again a standardised look along devices is important too, so I understand why you prefer the stock experience.

I had the opposite travel than you. I started with stock roms (even bad ones) and then went back to (debloated) Samsung roms. My experience is that debloated Kitkat is the fastest (almost as fast as CM), but still ram-heavy and lacks some of the features of Lollipop.

Since there are periods that I reaaally need Linux on my tablet, I revert to Samsung Kitkat (like I said very fast, less features, but not necessarily very crucial, ancient looking, the best Linux experience though) and when I'm back to Tablet-only use I install Lollipop.

I gave a try to CM based roms, I even used some of them for a week or more, but I mostly do that in my off-weeks. When I really need my tablet (for both production and consumption) I revert to Samsung. The rest has yet to implement Multi-window and Spen so well...

Anyway enough with the off-topic. This is a Rom Development thread, so I leave it at that.

Good luck to squashing the last remaining bugs and hopefully (one day) we'd get a CM12.1 quality release. Thanks (once again) to the devs.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ch!no:
Here are the logcat. Hope I used it correctly.

Appbar Issue (after enabling appbar, can't back out because hw back key is not responding although haptic feedback is still felt when pressing on the button)

https://drive.google.com/file/d/0Bwekux9QCtWXR1RfazFjNWZWT00/view?usp=sharing

Permissions Issue (Tried installing my apps back from a fresh flash and the first app I couldn't press "Allow" was the PayMaya app)

https://drive.google.com/file/d/0Bwekux9QCtWXcldFWnVOVFEzdzQ/view?usp=sharing
[Galaxy Note 10.1 (2014 Edition) Android Developmen] wadken1:
OTG Ethernet

Hi.

Anyone know if this ROM supports networking via OTG Ethernet adaptors? It would be quite useful occasionally when setting up routers, switches, print adaptors etc.

Edit: Well I guess either no-one knows or no-one cares but just in case any does search this thread here's the answer ---- No. OTG Ethernet is not supported. The necessary drivers appear to be missing.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Governor tweaks for better battery and temperatures

For those with temperature issues and/or high battery drain, I've made a first Interactive governor profile, which optimize frequence usage and cpu temperatures for our beloved p600/lt03wifi!

The first screenshots are showing the cpu usage (3C Toolbox/CPU manager) with stock settings and the others are with my settings.

As you guys can see, much more frequencies are used and the average CPU temperature is between 5-10°C lower, depending on the task to be processed!

Antutu score is a bit lower(cm12.1 level, 46k), but over-all-performance is nearly the same!

The profile saves also some battery juice, but unfortunately it solves not the high miscellaneous drain, which is 3-5 times higher as in 5.1 roms and also not the sometimes at max. freq locked cpu frequence!(e.g. after heavy load conditions like plays updates or gaming)

For those are interested install and open up Kernel Adiutor app> cpu page> governor settings and use the following values for

- "above_hispeed_delay" and set it to 20000 650000:60000 800000:20000

- "min_sample_time" to 30000

- "hispeed_freq" to 650000

and at last

- "target_loads" to 90 650000:19 800000:80 900000:12 1000000:81 1200000:9 1400000:69 1500000:95 1600000:95

You can safe the settings in a profile and if you enable "apply on boot" it survives reboots.

You can also take another app like 3C Toolbox which is also able to do that.

I'm also very much interested to see governor tweaks from other users!!

[MENTION=4144316]joshndroid[/MENTION]!

Honestly appreciate your work, because you are the only one which supports our tablet with current cm13 roms!

Very much thanks!

I place much hope in the next updates, because of your other device with Exynos 5420, with more recent drivers, etc.

Maybe sometime we can get the too high "miscellaneous drain" under control.

In the meantime, you might have the possibility to perform your own tests with my interactive governor tweaks and if they are good, perhaps to implement it in future versions.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] mosimchah:
To solve the battery drain, and temperature issues when gaming you have to switch to the ondemand CPU governor, then go to the CPU governor turntables, and then set the powersave_bias to 5, if you still get the issue then you need to set it even higher, don't go too high though because if you do you'll end up getting a lot of lag.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] tincmulc:
- "above_hispeed_delay" and set it to 20000 650000:60000 800000:20000

looks good, we want to minimize switching clusters

- "hispeed_freq" to 650000

Also good, already mentioned in this thread

- "target_loads" to 90 650000:19 800000:80 900000:12 1000000:81 1200000:9 1400000:69 1500000:95 1600000:95

The first 3 are OK (with again trying to minimize cluster migrations), but what is up with that 12% and 9 % target load at 900Mhz and 1200Mhz?!, also the last two are redundant (1500000:95 already covers everything >=1500Mhz)

Can you explain how you got to those strange target loads for freq >800Mhz?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Hi tincmulc,

thanks for the reply and the critic.

All settings was found by trail and error! I've also made a lot of tests and also other "profiles".

This is the reason why I asked for the settings of other users!

I've made a new more conventionel profile for the target_loads with target on efficiency.

What do you think with this settings below?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] AndyYan:
[MENTION=3241008]Stevethegreat[/MENTION]

I've found the hard way out to my CM agony... I purchased another Note 10.1, but this time I went for the slightly more expensive Qualcomm variants. End up getting a T-Mobile variant, flashed CM13 and everything simply went as smooth as it should. I'll have the Exynos one sold later.

As Exynos 7/8 still hasn't gotten any usable AOSP development yet, I think I'll give up on Exynos as a whole...

Thanks for giving advice on my situation all the same, and of course, thanks Josh and other devs for even making CM possible for the Exynos variant - I wouldn't even consider the device had there not been CM builds for it. Good luck going forward!

Sent from Google Nexus 6P @ CM13
[Galaxy Note 10.1 (2014 Edition) Android Developmen] rayik:
I don't know why, but those settings resulted in my tablet heating up a lot with heavy battery drain.

For me this works the best:

"hispeed_freq" to 650000
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Hey rayik,

the cpu locks sometimes on max. frequencies when you install updates from playstore. This behavior have nothing to do with the tunables and I got it from time to time since using 6.0 in this device. A quick reboot solves it.

Try this one! It is more conventionel... with goal on effiency! When load comes to 90% the cpu switch to the next higher frequence which will do the job in most efficient way.

90 650000:73 800000:80 900000:81 1000000:75 1200000:77 1400000:84 1500000:84 1600000:84
[Galaxy Note 10.1 (2014 Edition) Android Developmen] toanau:
Download link doesn't work. Could anyone point me in the right direction
[Galaxy Note 10.1 (2014 Edition) Android Developmen] enotar:
I am not sure 100% but it looks the agony is on the Android tablets in general and soon we will see only Windows 10 and iOS. Really I don't like Ipad and I don't like the way Windows 10 interact in tablet but 2 in 1 are getting better only with Windows 10 and you can boot Linux or Remix (needs to be better). The only negative factor is the weight

The Surface is kind of appealing if you want to multiboot. Samsung TabPro S is interesting too.

I still using my equinox Note 10.1quite a bit but went back to stock, not better than this rom but I can use some Samsung features.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] AndyYan:
Very true. Intel almost killed the entirety of Android tablets with their Atom venture, yet still failed and eventually retreated out of Android, leaving nearly no usable (read: flashable and tinkerer-friendly) Android tablets on the market.

That's why I still had to buy Note 10.1s even if it's already 3 years old - alternative solutions are either not ARM, not tinker-able, too expensive, or any combination of the above.

If Z4 Tablet still won't get any development and Pixel C still won't drop to a reasonable price, then I guess the upcoming Shield X1 is the last choice in the modern Android tablet segment.

Enough talk of these in this thread - let's leave it to Josh for development.

Sent from Google Nexus 6P @ CM13
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ViRuS-MaN:
hello

with the release 9.7 when i put the cover in my screen the screen close automaticly and when i remove the cover the screen start but with the release 10 , this option no work , why ???
[Galaxy Note 10.1 (2014 Edition) Android Developmen] r4yN:
In V10 this behaviour is disabled by default.

You now have to manually activate it in the settings (display & lights -> smart cover)
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ViRuS-MaN:
thank it s ok now
[Galaxy Note 10.1 (2014 Edition) Android Developmen] mosimchah:
Joshndroid, MTP isn't working on your custom twrp. Here's the recovery log: http://hastebin.com/azabayiqac.vbs
[Galaxy Note 10.1 (2014 Edition) Android Developmen] rfrazier:
I'm replying to a very old post, but wanted to say thanks and that it solved three lingering problems with my P600.

1. Fixed sound crackling.

2. Fixed occasional freezing/rebooting when using s-pen.

3. Fixed "sleep-of-death". Wakeup times went from nearly 10 seconds to more like 3 seconds.

I followed the instructions, but didn't install stock 5.1.1. Instead, after the first boot to the Samsung stock ROM, I installed TWRP then restored my (TWRP) backup of vanilla CM12.1. It also got rid of the Samsung security messages which showed up in red at boot.

Best wishes,

Bob
[Galaxy Note 10.1 (2014 Edition) Android Developmen] amitabh15:
I used the same procedure a few days ago and got rid of all the problems you listed above and any other lags. I didn't update to 5.1.1 either. Installed TWRP through ODIN and did a clean flash of CM13. Works great now. Really happy with the performance and no freezing, lags or sound distortion.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] israel_andrade:
Good morning,

Great feedback. On my P600, it did go to 5.1.1 via Samsung OTA. I rooted my tablet and loaded this ROM a few months later. I am on the latest TWRP (3.1.2) I think....

I am experiencing the issues you described. What do need to reload before I reload the ROM to eliminate the issues discussed. And where do I find these files?

Your assistance would be appreciated.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] mosimchah:
I followed your instructions, however I'm still getting the security warnings on boot "kernel isn't seandroid enforcing", does this mean that I'm still on the lollipop bootloader? If so what do you suggest that I do to fix it? Thanks

Edit: CPU-Z says that I'm on the P600UEUDOK1 bootloader.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] amitabh15:
This is the post and download you need to follow. No need to update to 5.1.1. Everything works well with Jelly Bean bootloader.

http://xdaforums.com/showpost.php?p=65631142&postcount=2293

---------- Post added at 05:25 PM ---------- Previous post was at 05:22 PM ----------

Did you update to 5.1.1 after performing the procedure set in the link below? If so, I didn't update to 5.1.1, I simply flashed latest TWRP right after and went to CM13 with Gapps for 6.0. I've had no lags, sound crackling/distortion issues since. I stopped getting the red SEANDROID error on boot screen too. Perhaps try repeating the procedure again and not update to 5.1.1. See if that helps.

http://xdaforums.com/showpost.php?p=65631142&postcount=2293
[Galaxy Note 10.1 (2014 Edition) Android Developmen] mosimchah:
I did not upgrade to 5.1.1 afterwords, I'll try the steps again.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] amitabh15:
P600UEUDOK1 is a lollipop 5.1.1 bootloader. Not sure, why it stuck if you didn't update to 5.1.1. I would recommend repeat the procedure and not update to 5.1.1 this time. Go straight to Tamasek's rom after flashing latest TWRP with ODIN. No CF-Root required. Since CM13 has inbuilt support for Root through Developer Options.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] mosimchah:
Okay, I did the process again, and it worked this time, I'm not sure why it didn't work the first time.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] amitabh15:
Perfect! Is it all much snappier, lag free, distortion free? Then you've got it all right. There's still the issue of screen tear with black lines when rotating the screen but that issue has been persistent from Cyanogenmod themselves.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] planetf1:
I have an SM-P600 and in the past have had a variety of samsung android devices, all others having been flashed, often many times, often cyanogenmod or others.

So far I've resisted anything beyond later country variants on the SM-P600 but if I'm honest I'm getting bored/fed up with the old look. Having encrypted the device it also lags badly so a re-install (and removal of some corporate sw/management) is very likely. In addition I really struggle with the 16GB storage space & should do some links to ease app install

With that in mind I took a look back through the last 10-20 pages & a fair summary seems to be

* Ongoing issues with camera/led

* A few cosmetic glitches (ie tearing on rotate)

* some battery/lag tweaks/concerns in latest build

but otherwise pretty usable? I'm not usually against the wire on battery, so a 15% drop say in usage is fine, cosmetic doesn't bother me, and I can't remember the last time I used the camera.......!!!

Two further questions:

* How is the s-pen working in the latest build? I mostly use microsoft onenote with handwriting, not a lot else

* I assume the rom is pre-rooted (or at least via toggle switch). Has anyone unrooted and been able to use Sky-Go (UK tv streaming service) - it's perhaps the one app I like to have around for when travelling

* Any serious bugs I didn't miss below

* Extra points - anyone try encryption (though this could recipe for data loss ?). If so any feeling on performance impact

Of course I could & may backup/try with option to revert but good to ask first ;)

thanks!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Chalao:
Camera not working and cosmetic glitches confirmed (e.g. screen freezes for several seconds when powering off, tearing on rotation, statusbar in the upper left corner in portrait mode darkened)

Battery seems to be fine though

S-Pen works great, also with handwriting (using Evernote and LectureNotes)

Root can be toggled in developer options

No serious bugs as far as I've seen until today

Encryption not working
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
I've been a bit slack with the device. It would appear that development for it by others is also slowing.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Revan335:
The last release is from cm-13.0-20160716-UNOFFICIAL-lt03wifi.zip-V10?

When it's right, please update.

Thanks!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Seriously...?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Revan335:
What do you mean?

Is this Release correct or is the Releases on for example Google Drive newer than basketbuilds?

Thanks!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] HSishi:
20160716 is the latest release in the GoogleDrive folder too.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Hi Revan335,

I mean one of the oldest forum rules which says, never ever bother the devs with questions like: "when will we get the next updates, daddy?"

All the stuff here was done as a hobby and all of them (incl. you and me) have a real life too with a lot of work, a family, sometimes vacations and illness.

Updates come when they come...!:p
[Galaxy Note 10.1 (2014 Edition) Android Developmen] mosimchah:
I don't think he's asking for an ETA, I think he just wants to know what the latest version is.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] stevvie:
Also he never asked the devs, anybody with Google drive access can answer the question
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Sorry, my bad!

Thought you/he ask for an update because there are always the same versions on basketbuild and gdrive!

Brrr...!!

English is not my native language and many uses for the word update.

Next time I will ask what was meaned before I start to teach someone!

Regardless, again sorry!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Revan335:
[MENTION=4174709]ollimi1[/MENTION]

No Problem!

Its not my native language too.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] amitabh15:
I know you're the dev and you do this on your own time, but personally I would appreciate if we could see some more development. I don't care much for the distortion upon rotation and a few other things. I guess I'll be really happy if we can get the camera to work. It'll give my device the much needed life it deserves and will keep serving me for a few more years. It's sad to see such a great device that I use for my master's degree going to waste and having to spend hundreds of dollars to get a working camera. Marshmallow has really given my device that extra battery life that I need during the day. Granted, I had to open it up and re solder the battery plug socket because of the jumping drain issue (45% to 25% in 10 mins). Which is now completely solved since I re-soldered it.

Thank you for all you have done so far. I'm sure each one of us appreciates your time on it. :)
[Galaxy Note 10.1 (2014 Edition) Android Developmen] jstadnicki:
Forget my question. Working again.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] algieba:
Hi

can you give me a Link or something similar which shows the resoldering of the battery plug socket? Because I have the same problem and I have no idea how I solve it.

Thank you!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] amitabh15:
Let me go back and search all the links and videos I used to figure out how to do it. It's fairly easy, but I understand it makes more sense when one can see a picture or a video. I shall put together and post something for you soon. Until then gather a soldering iron, a tiny bit of flux and solder wire. :)
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DirkStorck:
Hi, I only have two problems with this overall fantastic ROM.

1) It looks like the battery level is wrong. The device show 15% and shortly after it shuts down.

2) as a result of 1 it ends up in a bootloop if I connect the device to the charger. I have to go into recovery and wipe dalvic and cache.

Any ideas please... I am using v10

Thanks!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] amitabh15:
Ok, I'm posting some instructions here. This is at your own risk though.

Step 1: https://www.youtube.com/watch?v=y7PP4tCJGAQ

Follow this video only for disassembly of your tablet. You're not changing the battery.

Step 2: See attached picture and area circled in red. https://postimg.org/image/w3r6l0d8b/

You will probably not be able to see any deficiencies upon close examination eye but these connections are now loose or cracked. So you all you have to do is add a very tiny bit of flux, a very tiny bit of solder and re-solder these 5 connections. Make sure your tablet is turned off during the procedure. IGNORE THE FINGERS IN THE ATTACHED PICTURE WITH THE TWEEZERS. YOU DON'T NEED TO DISCONNECT ANY PLUGS. I JUST TOOK THIS PICTURE OFF THE INTERNET.

Step 3: Re-assemble carefully. Turn on the tablet, you may still notice the battery jump which is okay. Restart the tablet couple of times. It will automatically re-calibrate. From here on if the procedure went well you will not have this problem any more. I performed this procedure a couple of months ago and the tablet runs strong 2 full days without any charge.

Hope this helps! :o
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
I hopefully have a small amount of time to have a look at the recurring issue i have been getting of the device not booting for me on building over the coming days off from work. I need to read the logs i am getting.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] amitabh15:
This may be a hardware issue which I had to fix on my tablet a couple of months ago by resoldering. If your battery level is jumping by over 10% in a matter of mins. Try rebooting to TWRP after if happens, if the level there shows significantly more than before you rebooted, then you have the cracked solders on battery connector issue.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DirkStorck:
Thanks, I will keep an eye on that and will check in recovery.

But why do I get bootlops after this happens that I only can fix with wiping dalvic cache?

Thanks.

Gesendet von meinem SM-G900F mit Tapatalk
[Galaxy Note 10.1 (2014 Edition) Android Developmen] amitabh15:
I've never had a bootloop problem. I use it as a daily driver. Perhaps someone else on this forum who is experiencing the same issue may be able to comment on it.

There is however a small chance that a dirty flash with non matching Gapps may have been causing the bootloop problem. I can't be too sure. Worth a try to clean flash perhaps?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DirkStorck:
I am getting the bootloop if the device shuts down because the battery is empty.....if I than plug in the charger I get a bootloop and the only fix for me is to wipe dalvic cache....but that can't be the solution!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] amitabh15:
I'd say that's not really a permanent solution. Then again I've had my tablet run out if battery and shut down. It turned on just fine after I charged it so it's hard to say what's happening.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DirkStorck:
Ok, thank you! :)
[Galaxy Note 10.1 (2014 Edition) Android Developmen] 0killer:
Having the same problem with the Battery percentage dropping rapidly within the last 10 percent and the following bootlop after auto shutdown.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DirkStorck:
Any chances you have Xposed installed?

Thanks

Gesendet von meinem SM-G900F mit Tapatalk