yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 10.1 (2014 Edition) Android Developmen] redbaron:
MD5 don't match
[Galaxy Note 10.1 (2014 Edition) Android Developmen] soza971:
Build is corrupted i think [MENTION=4144316]joshndroid[/MENTION]
[Galaxy Note 10.1 (2014 Edition) Android Developmen] StackOverflow13:
Works ok for me from google drive install
[Galaxy Note 10.1 (2014 Edition) Android Developmen] soza971:
Yeah the build i am talking about is from basketbuild
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
U sure? Both rom sizes are the same have u checked md5 of your download
[Galaxy Note 10.1 (2014 Edition) Android Developmen] buhohitr:
I just download from basketbuild and flashed without issue. Thanks!!!!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
You must have downloaded halfway through the auto import to basketbuild

;)
[Galaxy Note 10.1 (2014 Edition) Android Developmen] dapat:
V5.2 from baketbuild installed just fine.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] danerrickcuba@gmail.com:
Hello, being very well aware that this is for p600, does this ROM exists for p605?

Thank you
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
Sorry mate it does not.. I don't think my upload speed would support another rom I'm kinda at my limit pushing out 7 roms at a time (it takes multiple hours).. Dont get me wrong I want a better connection but just waiting till I get my own place again where I will have control over who I use as an ISP... Plus I don't own the device to test
[Galaxy Note 10.1 (2014 Edition) Android Developmen] franzli:
Hi, just moved to temasek CM13 v5.2 from temasek's 12.1 v18.5. Generally quite smooth, but so far I noticed two issues (sorry if they came up earlier in the thread, just managed to read the last 5 pages or so):

1) On first try I had everything set up and then activated OmniSwitch, which seemed to break everything - the screen would blank and the tablet reboot. From then on, I wasn't able to get past the lock screen as it would blank out directly after. Now I'm set up new and it might be working, but this leads me to problem two.

2) Under Settings-Buttons there doesn't seem to be a setting for the Menu button anymore. It's there in the temasek CM13 for the Note 3/hlte, but seems to be missing on the Note 10.1 2014. Am I overlooking it, or is there a special reason why it is missing? Would really appreciate getting this back, as I use it as my Recents/OmniSwitch button.

3) A third little inconvenience relates to the external SD card. I've got two partitions on mine, which worked fine on CM12.1 (Android only saw the first partition, which I used for data, the second partition is for my Linux install). On CM 13, it sometimes correctly mounts the first partition and then tells me that the second one is corrupt (that's kind of ok as I can just ignore it), sometimes it mounts the second partition twice (!) and complains that something is corrupted. In that case, I have to go to Settings - Storage and USB, unnmount both partitions (actually both mounted partitions are the same small linux partition), and remount the first one, which then correctly mounts the data partition. This also happens on the Note 3 build, actually, so it might be a general issue with the way Marshmellow handles external SD cards, but if it would be possible to get a stable behaviour here, that would be great. However, this is mostly just a matter of convenience, as it works ok with the workaround.

Apart from that (and the known Camera issues), it seems off to a nice start. Thanks a lot for your work!

I used to have problems using the s-pen in ezPDF reader (quite a lot of lag in CM12.1), but it appears to be working quite smoothly on this ROM (almost as smooth as papyrus, which for some reason didn't lag on CM12.1 either).

PS: I can confirm it's a problem with Omniswitch, just crashed on me again.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ruud:
i am getting fc,every time, when i start the game wordon hd.

i have removed and installed again but stil fc.

what do i wrong or ??
[Galaxy Note 10.1 (2014 Edition) Android Developmen] epithetic:
1. Open /system/usr/keylayout in file manager

2. Edit Generic.kl and sec_touchscreen.kl (Open With -> Editor) and change 139 MENU to 139 APP_SWITCH in both files.

3. Reboot.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Ozark_8125:
I didn't see anything in the thread, but my bike trainer transmits via ANT+. Is this supported in this build?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] franzli:
Thanks [MENTION=4630882]epithetic[/MENTION]! This felt familiar, so I've probably done it once before on CM12.1, I guess.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] israel_andrade:
Greeting,

I am unsure if anyone has noticed this issue...

If you change the default 320dpi, the tablet gets into a reboot loop.. The only way to get back to a working status is to do a total wipe and reload. Any ideas?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] franzli:
Just changed to 280 dpi without problem, sorry. Takes a moment, but no reboot loop here.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] mosimchah:
Do you have any themes installed? That could have been the issue because some themes don't support a lot of DPI values.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] israel_andrade:
No themes installed. Using this ROM as developed. Thanks for your reply.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] benand:
Temasek build

Hello [MENTION=4144316]joshndroid[/MENTION],

Could you share the way you build the Temasek Rom ?

repo init -u https://github.com/temasek/android.git -b cm-13.0

Put a local manifest ? Could you share it ?

repo sync

brunch lt03wifi
[Galaxy Note 10.1 (2014 Edition) Android Developmen] franzli:
Yes, I second [MENTION=4240943]benand[/MENTION]'s request. In particular, I was wondering with respect to the kernel, as I was trying to build a version with virtual terminals enabled (to use the framebuffer option of running Linux, see [MENTION=3241008]Stevethegreat[/MENTION]'s tutorial thread). I managed to build a kernel, but must have done something wrong as my Note wouldn't boot with it. In fact, I also tried compiling the kernel with just the plain standard config: "make cyanogenmod_lt03wifi_defconfig", but the resulting kernel also didn't work for me, so I must be doing something wrong.

I tried compiling with the "arm-eabi-4.6" toolchain and with "arm-cortex-linux-gnueabi-linaro_5.2-2015.11-2". Maybe those are wrong? I never compiled an android kernel before (and not many - working - Linux ones either).

I'd be very happy with a brief pointer at the moment, and would try to work my way from there (unless I get stuck again :o ).

Would be much appreciated!!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Hawk600:
Hey Folks I need help with the root, Tab had root and I installed this rom fine (cm-13.0-20160312-UNOFFICIAL-temasek-lt03wifi-V5.0) but suddenly I started getting msg from busybox saying the device is not properly rooted. I also cannot find SuperSu anymore under programs.

Ok, I put again in download mode and re-run cfAutoroot in Odin, the process went fine and after the tab restarted to my surprise there was still nor root!

What to do now?

Thanks in advance!

By the way went to the options menu, SuperSu and got a nag that SuperSu nedds update, tried do that and it says update failed, reboot.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] franzli:
Have you tried just grabbing a zip file of SuperSU and flashing that with TWRP?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Hawk600:
I did not do yet, I wanted make sure there is no harm in doing so since the Samsung devices rely heavily on Odin for mods.

I have rotted and modded many android devices but I am a bit cautious with the Samsung ones.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] benand:
[MENTION=4144316]joshndroid[/MENTION] Thanks for tout work Donation 5LU21703Y0405280S

Envoyé de mon SM-P600 en utilisant Tapatalk
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
appreciate it kind sir :good:
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
essentially yes..

i wont share my manifest as mine is very specific to my pc.. As i have multiple devices, files, file locations, etc that are not exact.

suffice to say all you will need is my device, kernel and vendor trees (cm-13.0-temasek branches) as linked in the first post.

then within the device tree you will see cm.dependencies file. Within there you will see the other needed files for your local_manifests for lt03wifi specifically. re-sync repo and you should be good to go.

see here for the local_manifests.xml formatting (the contents you need, like the headers and how the repos are set out)

- https://wiki.cyanogenmod.org/w/Doc:_Using_manifests

create a folder called 'local_manifests' within your .repo folder and within that 'local_manifests' folder then you have your local_manifests.xml

i dont do anything special with kernel. Infact i just run it in-line and do most of my mods to ensure it will run inline. If you want to just build the kernel the simplest way is to lunch the device then run make bootimage, within the out folder u will see all the important kernel files you can use whichever is necessary. again i dont do to much other than make small mod to ensure outside toolchain will work and thats about it (but to ensure it runs inline requires a small mod to device tree, something you can get away with when building kernel on its own). I tried playing with kernel for various devices and learnt a bit but i need more experience with it. I dont even really use another toolchain for lt03wifi kernel specifically at this time.

lastly... dont use arm-eabi-4.6 it is not going to work for our device and is far outdated...
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Hi franzli,

SU is part of the rom. No need to flash it seperately! Go to settings> developer options and scroll down to the superuser entry and enable root for app and/or adb.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DirkStorck:
Isn't that the cm root you are explaining?

Gesendet von meinem SM-G900F mit Tapatalk
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Hawk600:
This did not work for me, after many unsuccessful attempts with Odin, the way it worked was uninstalling SuperSU, reinstalling it again from Google store and rebooting.

I am not sure if something is messed up but SuperSu works ok now witht he pop permission for new apps, should I do a clean rom install again?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
Just install supersu when flashing the rom using the flashable zip...

V5.4 is up on Google shares and basketbuild
[Galaxy Note 10.1 (2014 Edition) Android Developmen] namsir:
Chrome seems to lag like crazy for just 2 tabs.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
Seems to be a chrome thing... I get it at times on my Nexus 9 and nexus 6p both with copious amounts of power
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Yes, it is!

Never need to install su seperately since 6.0.

---------- Post added at 10:23 ---------- Previous post was at 10:09 ----------

Hi again!

Sounds like some permission errors to me!

But if its working now, no! No need to start from scratch with a clean install.

But I've another question: have you ever installed the 5.1 Samsung update?

Some people have reported widespread problems after switching from Samsung 5.1 to 6.0 Temasek. Probably bootloader issues! There is a solution therefor a few pages back and it is also mentioned in OP!

BTW, here is a flashable zip of latest su:

http://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Orion116:
I have always had to flash su. The built in one didn't even let me grant permission to settings.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] klight69:
Please help I'm having a Gapps issue with this rom. Every time I try installing them I keep getting messages saying that the setup wizard has stopped working and play services has stopped working. This issue keeps repeating and I cannot even get into the main screen. I downloaded the smallest gapps package for arm 6.0. I did just port over from an older rom and I wonder if this is the issue. Do I need to first install an older version of this rom before jumping into this one?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Orion116:
Did you clean wipe. System, caches, data, etc. If you are coming from 5.1.1 LP wipe everything but the kitchen sink :silly:
[Galaxy Note 10.1 (2014 Edition) Android Developmen] aridity:
Hi everybody.

I have a small question regarding using the SD card as internal storage. I just bought a new card, formatted it as internal storage and migrated data onto it successfully. But when I boot into twrp recovery (I'm using joshndroid's twrp 3.0), I cannot save a backup onto this SD card. Or even find a downloaded update... Twrp says that the SD card has 0 bytes capacity. But on my LG G3 this works. What am I doing wrong? On my LG I use twrp 3.0 with cm13 as well. Our do I have to go back using the SD card as external memory, which is not that easy as I have read... Thanks for your help...

Sent from my LG G3 (d855) with Tapatalk
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
Which gapps u using, try suing the pico gapps package from opengapps

Just don't use sd card as internal storage tbh something is weird
[Galaxy Note 10.1 (2014 Edition) Android Developmen] icebergisonfire:
Hello all and greetings. This is an awesome app. I have a question about 6.0 though. Since folder mount doesn't appear to work yet, I converted my SD card to internal storage. I thought I would fine,started to down all my apps and I got stopped with plenty space to spare.

[IMG="My data"]http://i.imgur.com/kDKVhHR.jpg[/IMG]

My question is how do I get around this? Thanks!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Hi!

Read one post above, your question is already answered!

It's always a good idea to read at least the last 5 pages and the OP!!!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DirkStorck:
I think there is an problem with the OTG. I have copied some mkv's on an USB Stick that I have formated as fat32 with in the tablet. If I use the build in file explore I can see the files but any other app like root explorer or kodi (xbmc) can't see the files.

Gesendet von meinem SM-G900F mit Tapatalk

---------- Post added at 04:33 PM ---------- Previous post was at 04:32 PM ----------

And if I insert a stick formated as anything else than fat32 I get an force close of the storage.

Gesendet von meinem SM-G900F mit Tapatalk
[Galaxy Note 10.1 (2014 Edition) Android Developmen] benand:
How to build

Hello [MENTION=4144316]joshndroid[/MENTION]

I manage to compile "a" rom :

repo init -u https://github.com/temasek/android.git -b cm-13.0

mkdir .repo/local_manifests

vi .repo/local_manifests/note2014.xml

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="Joshndroid/android_device_samsung_lt03wifi" path="device/samsung/lt03wifi" remote="github" revision="cm-13.0-temasek" />
<project name="Joshndroid/android_kernel_samsung_lt03wifi" path="kernel/samsung/lt03wifi" remote="github" revision="cm-13.0" />
<project name="Joshndroid/android_vendor_samsung_lt03wifi" path="vendor/samsung/lt03wifi" remote="github" revision="cm-13.0" />

<project name="CyanogenMod/android_kernel_samsung_exynos5420" path="kernel/samsung/exynos5420" remote="github" revision="cm-13.0" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" revision="cm-13.0" />
<project name="CyanogenMod/android_hardware_samsung_slsi-cm_exynos" path="hardware/samsung_slsi-cm/exynos" remote="github" revision="cm-13.0" />
<project name="CyanogenMod/android_hardware_samsung_slsi-cm_exynos5" path="hardware/samsung_slsi-cm/exynos5" remote="github" revision="cm-13.0" />
<project name="CyanogenMod/android_hardware_samsung_slsi-cm_exynos5420" path="hardware/samsung_slsi-cm/exynos5420" remote="github" revision="cm-13.0" />
<project name="CyanogenMod/android_hardware_samsung_slsi-cm_openmax" path="hardware/samsung_slsi-cm/openmax" remote="github" revision="cm-13.0" />
<project name="CyanogenMod/android_packages_apps_SamsungServiceMode" path="package/apps/SamsungServiceMode" remote="github" revision="cm-13.0" />
</manifest>

breaksfast lt03wifi

brunch lt03wifi

Flashing ok

boot black screen

Logcat :

03-24 16:58:43.745 8677 8677 I SurfaceFlinger: SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
03-24 16:58:43.746 8677 8677 E libEGL : load_driver(/vendor/lib/egl/libGLES_mali.so): dlopen failed: library "libstlport.so" not found
03-24 16:58:43.746 8677 8677 F libEGL : couldn't find an OpenGL ES implementation
03-24 16:58:43.746 8677 8677 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 8677 (surfaceflinger)

I saw the name of Temasek in forums near the libstlport.so on other devices.

Do you think it's my local manifest or a temporary problem that will be fixed in a future commit (i just need to retry later ;) ?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
Mate if I can build roms all day everyday it's not an issue with my tree or setup.. You have done something wrong somewhere. If your not using custom toolchain you can't use the Temasek branch of device tree
[Galaxy Note 10.1 (2014 Edition) Android Developmen] israel_andrade:
Has anyone noticed a fast drain of the battery with the test release?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DirkStorck:
I am getting bootloop if I dirty flash 5.4....it comes till that dialog saying "preparing apps" and after that a bootloop
[Galaxy Note 10.1 (2014 Edition) Android Developmen] mosimchah:
Well, dirty flashing is risky. Did you clear the system, cache, and dalvik cache? If you didn't, then you should wipe those and then reflash the ROM and Gapps and it just might solve the bootloop without you losing your data. If it doesn't help, then you need to clean flash.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DirkStorck:
currently trying that :)

EDIT: Still getting a bootloop
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
Try this... Restore a last backup.. Dont wipe anything flash rom and supersu and then wipe cache and dalvik cache let me know how u do (i had to do this on hlte for about 6 releases for some reason, I bet related to setup wizard)
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DirkStorck:
Thanks! I will try that.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
Try swapping the temasek specific one for the stock cm-13.0 it should work just fine (i use a custom toolchain for my builds)

<project name="Joshndroid/android_device_samsung_lt03wifi" path="device/samsung/lt03wifi" remote="github" revision="cm-13.0" />

And, stlport repo i use. I believe this is to constrain certain c++ library

<project name="CyanogenMod/android_external_stlport" path="external/stlport" remote="gh" revision="cm-13.0" />

Dont bother using breakfast, your using a local_manifests and it is unnecessary....

just run;

. build/envsetup.sh

brunch lt03wifi

and you should be good:good:

edit - I've so far added 118 people to google shares across devices, if your interested see the second post for the link to what i need and get on board
[Galaxy Note 10.1 (2014 Edition) Android Developmen] aronchav:
Definitely. Before CM13 I was running Scott's clean ROM and it seemed like I could go a week without charging. After installing CM13, battery fell through the floor. Even when it was sleeping. I was assuming I had something set up wrong (or had just been spoiled by Clean ROM), but checking the battery menu doesn't show anything that looks unusual. I will say that after using CM13 for about a week, the battery still drains more than it did with Clean ROM, but it seems to be stabilizing and improving. Maybe Marshmallow with it's new power management just needed time to adjust?

Also, it takes FOREVER to charge. One day it took me like 13 hours to get a full charge. I plugged it in when I went to bed one night and when I woke up in the morning, it said it still needed 5 hours to finish charging.

If there is some setting I should be turning off or on, please let me know :)

Last thing: What you guys do is amazing. I can just barely follow instruction to load custom ROMs. I have no idea how you build them. :good::cool:
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DirkStorck:
I have seen that you have removed V5.5.zip :confused:
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ridicul0us:
Hi, Could anyone tell me whether I can use this for P601 If I'm willing to lose the gsm functionalities?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
Nah man it was built few hours ago and is yet to finish uploading

Based on same tree so u will be fine
[Galaxy Note 10.1 (2014 Edition) Android Developmen] benand:
Thanks [MENTION=4144316]joshndroid[/MENTION] for the answer.

I managed to build a working rom with the following manifest yesterday night with standard toolchain:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="Joshndroid/android_device_samsung_lt03wifi" path="device/samsung/lt03wifi" remote="github" revision="cm-13.0-temasek" />
<project name="Joshndroid/android_kernel_samsung_lt03wifi" path="kernel/samsung/lt03wifi" remote="github" revision="cm-13.0" />
<project name="Joshndroid/android_vendor_samsung_lt03wifi" path="vendor/samsung/lt03wifi" remote="github" revision="cm-13.0" />
<project name="CyanogenMod/android_kernel_samsung_exynos5420" path="kernel/samsung/exynos5420" remote="github" revision="cm-13.0" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" revision="cm-13.0" />
<project name="CyanogenMod/android_hardware_samsung_slsi-cm_exynos" path="hardware/samsung_slsi-cm/exynos" remote="github" revision="cm-13.0" />
<project name="CyanogenMod/android_hardware_samsung_slsi-cm_exynos5" path="hardware/samsung_slsi-cm/exynos5" remote="github" revision="cm-13.0" />
<project name="CyanogenMod/android_hardware_samsung_slsi-cm_exynos5420" path="hardware/samsung_slsi-cm/exynos5420" remote="github" revision="cm-13.0" />
<project name="CyanogenMod/android_hardware_samsung_slsi-cm_openmax" path="hardware/samsung_slsi-cm/openmax" remote="github" revision="cm-13.0" />
<project name="CyanogenMod/android_packages_apps_SamsungServiceMode" path="package/apps/SamsungServiceMode" remote="github" revision="cm-13.0" />

<project name="CyanogenMod/android_external_stlport" path="external/stlport" remote="github" revision="cm-13.0" />
</manifest>

I'm allready on board for the Google share. :good:

Compiling the Rom is just for my pleasure/learning and if/when I have some spare time try to investigate by myself on some problems.

Thanks again for the time passed on our device.

---------- Post added at 02:07 PM ---------- Previous post was at 02:03 PM ----------

Same here.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
Well atleast you got a build..

As for battery life, device has gotten better since the removal of alot of the cell stuff considering it was polling for data when nothing was there so it was constantly trying. Further in the early stages the device for me wouldn't charge at all essentially remaining at constant percentage.. Personally I use greenify and naptime both root apps to control sync and wake locks.. Poor apps that significantly reduce my battery are Facebook, Facebook messenger, android wear and Google fit.. I can't find a featured solution for Facebook and I have tried/paid for a few alternatives now but I don't get the sync and ease of use as the developed one. I further reduce /remove location polling for facebook/twitter/ and social media app that I don't need it for, as really that polling in the background borks battery as well
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
V5.5 up on basketbuild and Google shares