yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Yeah, thanks

Hope we soon come to a solution for the countless battery consumption. Never see such high miscellaneous drain before!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] haimann95:
Yep, we are having Cam issues again. Is it working for you guys?

Gesendet von meinem SM-T705 mit Tapatalk
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
I talk with one of the developers over there regularly as well as the other lt03wifi and lt033g devs.. It still isn't working and many once working solutions even when changed and adapted to the new firmware no longer work.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
[MENTION=4144316]joshndroid[/MENTION]

Have you change rom name of the zip file or is it a unofficial cm13 rom in a wrong folder?

I see a new release named unofficial_lt03wifi instead of unofficial_temasek_lt03wifi..
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DirkStorck:
Just have flashed it. It's v9.5...
[Galaxy Note 10.1 (2014 Edition) Android Developmen] haimann95:
Did you check his fix? https://github.com/Schischu/android_device_samsung_chagall_klimt_common/tree/aosp-6.0/camera

That seems to work well for us in the Rom I'm currently using (6.0.1).

Gesendet von meinem SM-T705 mit Tapatalk
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
Yeah I did forgrt to rename it with temasek tag the one in the folder is v9.5

Cheers I'll take a look
[Galaxy Note 10.1 (2014 Edition) Android Developmen] rayik:
I noticed high battery drain and heat. Using 3C CPU Manager notice tablet was running at maximum cpu speeds at all times.

Remembered reading many pages back of a recommended change to hispeed_freq. I note default is 1900000. Recommended change was to 650000.

Made the change and all CPU speeds seem to be used, especially lower speeds and idle. No longer just highest speeds at all times. Battery time greatly increased as well as tablet runs much cooler.

Can make that change using 3C CPU Manager but it reverts back to 1900000 on reboot. How can this be permanently changed to survive reboot? Can this be changed in the ROM? Thank you
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Hi rayik!

There should be a "apply on boot" option in cpu manager next to the question mark but dont know if governor tweaks survives reboots.

Try Kernel Adiutor from plays!

Go to cpu page> governor tunables and set it to 650. Also make sure "apply on boot" option is enabled for cpu page.

It will survive reboots and also rom updates!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
Hmm I set this up in source a while back and you guys confirmed it for me - https://github.com/Joshndroid/andro...mmit/2f8c52ce9f1096781580123ac05ff39ba13494ba
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DirkStorck:
I have a small screen flicker if I download apps from Playstore...

Gesendet von meinem SM-G900F mit Tapatalk
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ZakooZ:
That's weird, I installed 9.4 [cm-13.0-20160622-UNOFFICIAL-temasek-lt03wifi-V9.4] yesterday and 3C CPU manager shows that my interactive governor has a hispeed of 1.9GHz
[Galaxy Note 10.1 (2014 Edition) Android Developmen] mosimchah:
Can you get a log of the issue? If it's a distortion then the issue is already known and is being worked on, however another log can't hurt.

Website signature
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DirkStorck:
It is only a small distortion during the download when I am inside the Playstore. I can try to grap one when it happens next time.

Gesendet von meinem SM-G900F mit Tapatalk
[Galaxy Note 10.1 (2014 Edition) Android Developmen] rayik:
Same here with 9.5. Hispeed is 1.9
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Orion116:
[MENTION=4144316]joshndroid[/MENTION] I can confirm that your kernel change didn't work. I had to change it manually for BrokenOS. It maybe changed by an init.whatever.xx file somewhere, lol
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ch!no:
[MENTION=4144316]joshndroid[/MENTION] Just want to do my part by reporting bugs on the new build 20160625.

1. flashlight doesn't work. pressed the button but no light.

2. screen tear (like thin black horizontal lines on the screen) whenever screen rotates and i put the device to sleep.

3. can't root just by toggling in developer's menu. i still had to flash supersu in twrp.

4. can't connect to camera

5. enabling appbar disables my hardware back button.

so far those are the issues I've encountered. thank you very much and you should know, your ROM is great! i'll keep watch for issues.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Yepp,

but hi_speed freq. switched back to 1900 for some reason but I dont remember at which point.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DanOpi:
Just switched over to this build. Followed the directions and seems to be quite buggy. Am I missing something?

Flashed TWRP-3.0.2-0-lt03xxxx-Joshndroid-F2FS.img file and then changed data, system, and cache to F2FS. Rebooted into TWRP 3.0.2 which worked fine. Flashed cm-13.0-20160622-UNOFFICIAL-temasek-lt03wifi-V9.4 followed by open_gapps-arm-6.0-micro-20160628 and then SuperSU.

Settings constantly crashes. Google Play takes forever to install (not download) apps. Hangs when trying to open apps for a few seconds.

Would love to get this going and help out with testing and such! Not knocking the build, just seeing if anyone has any ideas!

Thanks much!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ch!no:
[MENTION=7115214]DanOpi[/MENTION] you should try using the latest build (cm-13.0-20160625-UNOFFICIAL-lt03wifi), i haven't experienced any of your aforementioned issues with my time using it. but remember this ROM is basically a nightly or an early build, meaning expect loads of bugs. people are installing it to report bugs basically but build 20160625 (the one on the bottom without a version number) is usable except for the bugs i mentioned on my previous post.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] mosimchah:
Don't use f2fs on marshmallow (at least not on this device), it was previously said that it is causing issues. Switch to ext4 in recovery, if this doesn't solve your issue grab a logcat and post it here.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DanOpi:
So just flash a plain TWRP zip, switch to ext4, flash newest ROM, GAPPs, and SuperSU? Appreciate the help!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] mosimchah:
You can stick with joshndroid's twrp if you want (it works perfectly fine), yes for everything else, and you're welcome .
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DanOpi:
Worlds difference! Thanks again!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
V9.6 is up on Google shares and basketbuild.. You may notice a couple commits for ir blaster.. Unfortunately I didn't have much success with these.. I have another solution to try out
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Tony66:
Confirmation - Infrared no function!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ch!no:
Aforementioned issues are still present on v9.6

additional issues

1. sometimes when asking for permissions, the allow button can't be pressed. you have to manually go to settings and change permissions there.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Hi ch!no,

I confirm point 1-3 but I've no issues with 4 and your additional point. Have you installed and applied any themes? If yes, deinstall it, reboot and try again!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ch!no:
[MENTION=4174709]ollimi1[/MENTION] hey man, nope I haven't installed any themes. i always check right after i freshly flash (i use the clean flash method stated on the original post) all i have is the TWRP, ROM, GAPPS then SuperSU.

RE:Appbar

I do feel the haptic feedback of the tablet when i press the back button but it won't register an actual action whether i'm backing out of the settings or backing on a browser but as soon as i disable appbar the back button works again.

RE:Allow button on permissions

Sometimes it just won't press allow no matter how much i tap on it but as soon as i tap deny it works. easy to circumvent though, just by allowing permissions via apps on settings.

Thinking about it, I might need to wipe my internal storage. Could any app remnants be causing these? I'm just a tad scared to wipe internal because I have no data cable right now and the only way i could copy into my device is through a wifi transfer app which would be gone or stop working once i wipe internal. But seeing as these issues are mainly system related I don't think my internal storage has anything to do with these bugs.

Not really familiar with programming or android development so if you could suggest me installing something to maybe able to log this event please tell me what program to use so I can help.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] HSishi:
I wouldn't see the screen tears as a big issue since the tears only occur when the device gets rotated or turned off.

The missing camera is a more important issue (at least for me).

The flashlight is linked to the camera, so (for me) two issues have probably the same reason.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Hmm, strange!

You could safe your stuff on an external SDcard if you have internal and external memory not united to one big internal storage, which is not recommend because of some storage issues!

Another question is, did you ever installed samsungs 5.1? I ask because the 5.1 bootloader is known to cause problems with cm13 roms.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] AndyYan:
The occasional frame drop is also present in Temasek... See THIS POST.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ch!no:
[MENTION=4174709]ollimi1[/MENTION] no I came directly from a KitKat stock ROM, which I rooted using autoroot (odin3). I was using xposed back then though.

seems like buying an external SD is my saving grace, don't have one installed though. this tablet of mine is a notorious sd card killer. lost 2 cards already on this tablet, both have lost their ability to write.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] israel_andrade:
OK, Please explain, if possible, your last question. How does one address (fix) this if they did have Samsung's OTA 5.1 installed? Are there files involved that need to be flashed? Where are they and what do they specifically solve?

Thanks,

israel
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Have you tried to wipe and format them using your recovery or a pc?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ch!no:
the SD cards? yup, formatted them on the tablet and pc. no dice, it's like they've become read only. the data inside the SD card can't be erased or modified in any way. so I trashed them, and started relying on 16 gb of internal memory. anyways tnx for the help.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] HSishi:
Mh, I know the poststamp-sized SD cards have a "Read-only / Read-write" switch. Not sure how the micro-SD-cards handle that but there must be some kind of a switch too. Maybe the switch from a MicroSD card adapter can overwrite this.

I did a short Google search for "+MicroSD +Read-only". Most hits state the SD cards have a finite number of Write cycles and, after those cycles are done, the related cells became unchangeable.

Unfortunately the area where the FAT is stored is the area with the most write cycles so it becomes "worn-out" pretty fast, making it unchangeable. Not sure if there's a way to reformat the card in a way the FAT is stored somewhere else.

For me, there's a correlation between "cheap" and "Brand" cards in their durability - the cheaper the card, the earlier its death.

You should probably buy your cards a) from a good brand, known for their enduring cards and b) from a local dealer instead of (suspicious) shops which sell those cards for a bit of the price in the store. Your "Wow, that's pretty cheap" sense should become a "Wait, that's TOO cheap ..." sense, when it comes to "original" hardware. Labels can (and might) be faked.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ch!no:
like a digital switch? because there isn't any physical switch i could find. like back in the day of floppy disks wherein you flip a switch to make it read only.

yeah, I'm thinking I just got bad batch of microSD's. but i did buy them on an electronics store, not in ebay or any cheap stalls. the 64gb was samsung and the 2nd one i forgot. that's why i'm hoping huge internal storage becomes a practice for manufacturers. sd cards have left a bad impression on me, as unreliable. i'd rather have a 64gb or 128gb internal storage emmc or ssd.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Hi ch!no,

look at the screenies below.

Some sdcard adapters have a small manual switch for write lock!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ch!no:
unfortunately i don't have the MicroSD's with me now. but i'm quite sure my MicroSD's don't have those toggle and I never used the adapters because my card reader has a slot for MicroSD so I could just insert it directly.

just to add, i observed something new on v9.6 that I haven't experienced on the previous version of Temasek's CM13 ROM. The battery percentage keeps dropping dramatically (15%) then when I reboot it went back to almost 50%. Naturally this occurs to me even on kitkat but not this huge of a percentage difference and not a lot of frequency. this battery charge drop happened far too often to be normal here on v9.6. On the previous version I never observed this behaviour. might be something, might be nothing. I'll keep on observing. thanks!

funny, i was charging my tablet. doing some work on pc. went to pee then I saw my tablet reboot on it's own...
[Galaxy Note 10.1 (2014 Edition) Android Developmen] uno mas:
The Basketbuild Download link is incredible slow!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
That's why I have the google shares set up
[Galaxy Note 10.1 (2014 Edition) Android Developmen] StackOverflow13:
since v9.x I can't get mx player to play mkv files properly. Get video but no audio, it says codec not supported. Downloaded all available codecs including the AIO which is very old but still no joy. Any ideas anyone?

Works fine on v5, v6 & on stock
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ch!no:
tested an mkv file, plays fine on mine. i use mx player pro v1.8.4.nightly.20160125 (ARMv7 NEON)
[Galaxy Note 10.1 (2014 Edition) Android Developmen] StackOverflow13:
thats odd, wonder what it could be then
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ch!no:
can you verify what audio codec your mkv file has? it probably has dts... the one i played on mine was a simple aac. i'm gonna try and play dts and ac3, if i could find some files.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] StackOverflow13:
really odd uninstalled the codec then reinstalled & now works fine
[Galaxy Note 10.1 (2014 Edition) Android Developmen] mosimchah:
Try clean flashing it
[Galaxy Note 10.1 (2014 Edition) Android Developmen] taavaar:
I did once but now I´ve stopped anything trying to fix this. Thanks!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ch!no:
v9.7 known issues

1. flashlight doesn't work. pressed the button but no light.

2. screen tear (like thin black horizontal lines on the screen) whenever screen rotates and i put the device to sleep.

3. can't connect to camera

4. enabling appbar disables my hardware back button. NOW WORKING

5. Permissions - "Allow" button cannot be pressed occasionally
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Hi taavaar!

You should try one of the core gapps packages like nano or pico and install other needed gapps later from playstore. :good:

I'm doing this for years and hardly ever get such errors.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] taavaar:
Thanks, I did it and now it´s perfect working!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] shutin:
I never understood why they even bother with so many gapps packages. Just get the play store installed and then do the rest manually (or just let google's auto-restore do it's thing!!!). I found this helps you determine what apps you actually need versus what you think you need.

Just installed this ROM for the first time a couple days ago. I'm very impressed! I was coming from a year old LiquidSmooth rom that was good, but very out of date. I was a bit worried about installing a CM rom because they tend to be so damn minimalistic, and I like my roms packed to the brim with features. But wow! This build has WAY more features than my old one! Just wanted to say great work! I'm very thankful someone is keeping this tablet up to date. I refuse to run touchwiz and it's hard to part with the pen, even if i never use it.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] AndyYan:
Jul 4 package still has the SetupWizard fault (bypassable) and weird UI lag. It might not seem a big deal, but I'll have to give up all my games on this tablet if this is not bypassable.

Pretty much in a dilemma with the ROMs this tablet has:

Official: not up-to-date; UI too heavy even after debloating

CM12.1 Temasek: random black-screen and freeze

CM12.1 nightlies: same as above, plus takes 10 seconds to wake up from sleep

CM13 unofficial/Temasek: UI lag

Sent from Google Nexus 6P @ CM13
[Galaxy Note 10.1 (2014 Edition) Android Developmen] franzli:
Really, you get freezes on tenasek cm12.1? I sadly recently had to switch back to stock because all cm based ROMs have an annoying lag with my favorite Bluetooth (3.0) keyboard. Apart from that, I had been using the temasek ROM without issues since November last year or so.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] AndyYan:
It might have something to do with using Xposed. One freezing scenario I can easily reproduce is that, after opening Xposed Installer, do a few random actions and it will freeze and then reboot after a while.

EDIT: One more example: just discovered that the game "Pool Break" causes an immediate freeze and reboot on open.

Sent from Google Nexus 6P @ CM13
[Galaxy Note 10.1 (2014 Edition) Android Developmen] xdaSEx10:
I have flashed the latest version V9.7. Did any one experience flashing ripples when switching rotation mode (landscape & portrait change) ?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ch!no:
That is a known bug on this ROM. No fix as of yet.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Deleted!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] oqtavios:
CM13-20160715 in Google Drive has 0 kB size. Its corrupted. Please re-upload it to GDrive.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] aznsephyi:
so basically there's no stable/fully functional alternative to stock? I'm on temasek 12.1 and the only issue i've seen is distortion in recents menu
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
New build is online now!:good:
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Tony66:
Google Drive File is okay!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Stevethegreat:
About Official roms, I dispute that fact. Remember what we get is a Samsung fork which -still- is not the latest , but in certain parts is much more modern than any android version.

So it depends on what you mean by "not updated". Compared to stock android or CM12/13, it's them that lack crucial tablet features, not Samsung Roms.

Maybe CM14 will start getting up to date but even then it will probably not be the case. In other things stock android is more updated by definition... In short you cannot easily compare two different forks and it's slightly misleading to do so.

My experience with stock android on tablets is that it sorely misses crucial features, so it's stock android that is out of date. Then again (partly because of the lack of features) they're fast roms, so I prefer them for certain jobs.

Then again, the job done in threads like this is great, and I greatly appreciate it, so keep up the good work (both the ... testers and the devs).
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Hi Tony66,

this gdrive files are directly from joshndroid.

The message always occurs if a file is to big for gdrive/google to check,

so no problem,

install & enjoy!:good:
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Hey andi yan,

Xposed works totally normal here. If you get freezes then it's not rom or xposed related!

I'm with xposed v80 release because it was made for lollipop and has no nougat-changes and I'm using su2.65 for the same reason!

The only issues I can confirm is homebutton/deepsleep lag because it takes 2-3 sec. to wake up the device from deepsleep and the heavy battery drain compared to earlier roms!

But I'll try to optimize interactive governor this week to get better results but at first I have to do some tests to find the right freq for each job(e.g. video streaming, gaming, background tasks, updates and the likes!) Seems there is much space for optimizing!

Another thing you should do is, download kernel adiutor, open it and go to cpu page, there open governor settings and change hispeed_freq von 1900 to 650mhz if not already changed.

It solves a lot of issues when changed!

If someone is interested trying the same here is a good how-to:

http://xdaforums.com/nexus-5x/general/guide-advanced-interactive-governor-t3269557
[Galaxy Note 10.1 (2014 Edition) Android Developmen] okNNN:
Nice build so far. I'm on v10 now, but the camera isn't working (tested with Google camera, Skype & Open Camera). Horizontal lines appearing when screen rotates. Flashlight isn't working. Did a clean install with v9.7 and a dirty flash with v10.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] AndyYan:
For other devices I own, CM is often the only way to keep both the Android version and the features up-to-date, and since I'd like to keep a unified experience across devices, I'd naturally prefer CM on this tablet rather than Sammy's implementation.

Sammy's Lollipop is still better than KitKat for example (believe me, I resorted to CM11 and almost stayed), but small things like not being able to set the wallpaper without cropping and different multi-window layout certainly irks me.

On the other hand, I'm baffled that CM12.1 managed Nightly status with the critical bugs - when I bought the tablet, I saw official CM12.1 and thought, "ok at least I have something more stable to fall back to if CM13 goes wrong", but that's simply not the case.

I do agree that it's already amazing for the Exynos devs to have come this far already - it's much more work than Qualcomm devices, we wouldn't even have the ROMs to try out if it weren't for them. Sorry for the long rant.

Sent from Google Nexus 6P @ CM13

---------- Post added at 05:35 PM ---------- Previous post was at 05:34 PM ----------

Temasek CM12.1 is close, but I found out that it doesn't support one of the apps I often use (while CM12.1 nightly does), so I still had to give it up.

Sent from Google Nexus 6P @ CM13
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ch!no:
My known issues on v10

1. flashlight doesn't work. pressed the button but no light.

2. screen tear (like thin black horizontal lines on the screen) whenever screen rotates and i put the device to sleep.

3. can't connect to camera

4. enabling appbar disables my hardware back button. (problem persists)

5. Permissions - "Allow" button cannot be pressed occasionally.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] mosimchah:
Get a logcat for the last two mentioned issues, the others are already known and are being worked on.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
Which app is not working in cm12.1?

With temasek eventually retiring I have been learning/working on my own thing. There is potential light with I believe an exynos5420 based device getting m, where we can pick some device related stuff but I've been advised camera won't be one of them due to sensor differences