yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 10.1 (2014 Edition) Android Developmen] dimex:
Hey OP, thanks for the ROM. Installed on my "new" used Note 10 2014.

Is there anyway to port the wacom hover indicator over to this ROM? Secondly, 2 more pen related functions would be great: the ability to disable capacitive menu keys (I'm not sure, but I may be able to set up a Tasker profile that does that and invoke it in certain apps), and the ability to disable the S-Pen recognition or what not so you can use a different stylus while keeping the S-Pen in its holder.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Tiemichael:
[MENTION=4144316]joshndroid[/MENTION]:

It seems a new release cm-12.1-20150730-UNOFFICIAL-temasek-lt03wifi-v15.2.zip is available at Basketbuild.

Surprisingly the size is only 39MB!

Is this ok? How to install?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Hi Tiemichael!

Haha! Someone flash addicted .. ? tse tse!

Seems he is uploading a new build in this moment.

Wait a half hour until the upload is ready and download the complete zip.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Tiemichael:
It seems I was too excited ... yes, seems I'm a flash-addict ...

Now it's already 70MB ... so have to wait another 20min or so .... whoow so exciting!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
yes currently uploading 15.2 - internet in my country sucks (especially for upload speeds) so it says at the moment about another hour until it is finished, then i will merge it over to romhut and all will be well
[Galaxy Note 10.1 (2014 Edition) Android Developmen] mosimchah:
Does 15.2 have the commit for flashing custom kernels?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] GreenRaccoon:
Would anyone be able to check whether I'm flashing this correctly? I've been using build 14.3 for a few weeks and decided to flash 15.2. It flashes great, but it won't boot up. (I let it sit at the "Samsung Galaxy Note 10.1" screen for a half hour before deciding that.) I tried reverting back to 14.3 (by flashing the zip, not my backup), but that didn't boot up for me either, so I'm guessing I'm doing something wrong. Here are my steps:

1- Boot into TWRP 2.6.3.3.

2- Wipe data, cache, dalvik-cache. (When that didn't work, I tried wiping system too.)

3- Flash the ROM zip.

4- Flash Google apps zip (jajb's minimal edition, latest version, the same one I've been using).

5- Flash Supersu zip (the latest version, which is what I've been using).

Am I missing a step? The md5sums for all of the files are correct, and it always says that they've been flashed correctly. I tried flashing everything through adb sideload too without success.

EDIT

Figured it out! Apparently I forgot to check the md5sum of the ROM zip AFTER I pushed it onto the device. For some reason, `adb push` didn't like the name of the file. I tried pushing the file onto the device a few times and the md5sum was always wrong afterwards. BUT then I renamed the file from "cm-12.1-20150730-UNOFFICIAL-temasek-lt03wifi-v15.2.zip" to "cm-12.1v15.2.zip", and now the md5sum matches every time. :confused: Maybe the original filename was too long for `adb push` or something. (I'm using Linux; it might be different for Windows or Mac.)
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
A couple of pages back orion116 whom highlighted the commit to me further stated that the commit was not the cause and that they were working on something else that may be the issue so i havent added it

I cant seem to find anything on name length regarding adb push but it does not suprise me that length could/would be a factor, the name of the rom is rather long but most of it is autogenerated on build. Either way good to hear your initial issue has resolved itself and it is working for you, thanks for further personal debuging as well its good to see:good:
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Orion116:
My partners left on vacation and didn't tell me what he was fixing, since it was his mistake during the porting of one of the features. And I think you still need that commit.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
alright ill take another look today for next release :good:
[Galaxy Note 10.1 (2014 Edition) Android Developmen] GreenRaccoon:
Yeah isn't that weird? I'm also using Arch Linux though, so maybe it has something to do with my USB drivers or something, which means that a distro like Ubuntu might not have the same problem as I'm having.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Tiemichael:
Not sure it's just my device, but since a few updates 'clock' is no longer running ...

Anyone having the same experience?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
Which clock.. The clock app or the cm lock screen 'clock'
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Tiemichael:
The clock-app has the FC issue.

I did not do a clean install for quite some time - only wipe Cache, Dalvik-Cache and System ...

Thank you for providing this great ROM!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Genebaby:
I had FC's in the clock app on the latest version of another Temasek based Rom. Did a second clean install and all ok.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] poloruiz714:
How is the battery running on this rom? On stock firmware the battery is horrible. Apps keep running in the background.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] dimex:
I'll get back to you on that. I've been using Windows tablets prior to this so I can't really comment except for saying it's definitely longer battery life than Windows counterparts.

However, does utlized RAM sit around 2GB for you guys? It seems like a lot of RAM is taken up by the system, even on first boot, leaving about 1GB free.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Tiemichael:
Interesting, and thank you for the detailed report!

Just yesterday I upgraded from TWRP 2.6.3.3 to 2.8.6.0 - until now no problem! (but it's not even 24 hours ....)
[Galaxy Note 10.1 (2014 Edition) Android Developmen] mosimchah:
The battery life is really good. It gets even better if you disable walelocks. I easily get 4-6 hours of screen on time even when I'm playing games, watching stuff on Netflix and browsing the web.

---------- Post added at 07:07 AM ---------- Previous post was at 07:02 AM ----------

It is normal for Linux (Android) to use a lot of RAM. Unlike on windows, when it comes to Linux unused RAM is wasted RAM and using up your RAM only makes everything faster, so yes, the system takes up a lot of RAM because their is so much RAM that using about a gigabyte of RAM for the system does not do any harm. In fact it makes it even faster.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] dimex:
I received my "new" used Note 10.1 with a completely black screen. I could faintly see touchscreen elements and touch input, capacitive buttons, and sound work. It's a common issue, I reseated the LCD cable which fixed the issue. I then proceeded to try different ROMs. Installed the latest version of TWRP which made the tablet unusable: touchscreen delays, failing flashes, etc, etc. Backed down the version and everything's smooth sailing.

So while I do believe older versions of TWRP work better on this tablet, I think your issue was the LCD ribbon cable.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] jm997:
Believe what you like. I read all the threads and at first I actually thought it was a hardware problem. I reseated the LCD cable first (obviously) and it did not fix the problem even after rebooting. Also I could definitely not see anything on the LCD, it was completely off (I know what you mean though).

The issue started right after I flashed the first ROM/TWRP, and before that it was running issue-free on stock for 1.5 years. I tested the different TWRP versions and got this issue every single day, and with 2.6.3.3 I've been issue-free for 4 weeks. So if it actually turns out to be a hardware problem, it's a super-weird one. It might be a combination of several things I did, and/or the combination of my exact model (European P600), the ROM, etc. I don't know. In any case, if you have issues try TWRP 2.6.3.3.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] dimex:
Interesting. I had issues too and found a thread where someone said TWRP 2.8.5.0 was issue free. That's what I'm running and it's been perfect. If you want to update to a higher TWRP (I'd just stay with what you have personally, cuz if it aint broke, don't fix it!), 2.8.5.0 seems to be good.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Hey guys!

It's a known issue and definately TWRP related. The most versions are more or less buggy. It is related by a wipe cache/wipe data error.

You can use 2.6.3.3 as the most stable release or you can fix the "wipe cache/wipe data issues" in TWRP recovery 2.7.1.0 or 2.8.5.1 by doing the following:

Restart into recovery go to Settings and check "use rm -rf…" and no more freezes at all.

This should fix the wipe errors and make the most releases usable, but not tested with all!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Masterchivo:
Hello im currently on the 5.0 build and its been working pretty well so far. Km tinking is update to the newest build bit i dont know if ist estable. Which build is the best now?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Tiemichael:
THis ROM runs smoothly without any crashes! For me it's always the most recent version i.e 15.3 at the moment - it's getting better and better with every builT
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ZanyG:
Are there any low-tech changelogs available that easily tell which bugs were fixed/which features were added?

For example: I could not tell from the detailed logs if the menu-button is working now?

Thanks
[Galaxy Note 10.1 (2014 Edition) Android Developmen] mosimchah:
The menu button is working now. As for the changelogs, the simplest one is the one built into the ROM. Also I assure you that this ROM is feature rich, and has very few bugs, in fact the only bug that can easily be seen is the recents distortion and it's not even that bad.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
new build 15.4 is now live, added the kernel enabling after further notification from [MENTION=6176472]Orion116[/MENTION] as outlined earlier. Havnt had a chance to test it with a custom kernel myself if anyone else is interested to try it and report back.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Orion116:
[MENTION=5617466]Andmoreagain[/MENTION] figured out it was a ramdisk issue, so his kernel will now work. BrokenNote will also work soon too.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Andmoreagain:
Yeah, it really has nothing to do with the kernel itself. I haven't done any diffing to confirm it but it probably has to do with subtle differences in the boot partitions (*.rc files) for different ROMs. As long as only the kernel zImage is overwritten by the installer there won't be an issue with custom kernels. :)
[Galaxy Note 10.1 (2014 Edition) Android Developmen] wtheiner:
THX for this great Rom. I do a FRESH clean installation and now my camera wohnt work. Ans Tipps?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Tiemichael:
No problem for me, even after dirty install ...

There have been some problems in the past, which disappeared after re-booting the device
[Galaxy Note 10.1 (2014 Edition) Android Developmen] koz:
I found the zip but not the apk. Could someone point me in the right direction? Thanks.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Tiemichael:
http://xdaforums.com/attachment.php?attachmentid=3383776&d=1435601440 - this seems to be the latest version for XPosed -apk and is working for me (with this ROM)
[Galaxy Note 10.1 (2014 Edition) Android Developmen] wtheiner:
My Bad, wrong gapps
[Galaxy Note 10.1 (2014 Edition) Android Developmen] koz:
Thanks! I guess I should have been a bit clearer on what I was looking for - glad you could decrypt the post.

For quick future reference, the link above is for a working Xposed framework apk for this ROM.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] pictorul20:
FIX.....

Please fix the incompatibility between TWRP 2.8.7.1( with f2fs support) and this rom ( error executing updater in zip). Thank you :highfive:
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Hi Pictorul!

I think it's twrp related and no incompatibility with this rom! 2.6.3.3 have no issues with the updater script.

There is a fix to get twrp fully working on the last page, this fixes at least the wipe cache/data errors.

Try it and for the incompatibility try asking [MENTION=2638973]bigbiff[/MENTION] from the twrp thread. Maybe there are some changes, that cause that twrp is thinking this rom is not compatible with the device!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
new build 15.5 is up on both site, cheers.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Tiemichael:
I also tried TRWP 2.8.7.1 ( with f2fs support)(from here: http://xdaforums.com/galaxy-note-10.../sm-p601-cyanogenmod-12-0-unofficial-t3052009) a couple of days ago, and was also unable to install this ROM.

It might be that this TWRP is specifically altered for a specific series of ROMs ([SM-P601] CM12.1 / RR / TeamEOS 5. Unofficial builds for the Note 10.1 3g (lt033g))

TWRP 2.6.3.3 seems the most stable release
[Galaxy Note 10.1 (2014 Edition) Android Developmen] kenny1991:
Another rom that has something to do with Temasek? :eek:

Im going to flash this, omg how could I miss this! Bye crapy TW :DDDDDDDDDD
[Galaxy Note 10.1 (2014 Edition) Android Developmen] dimex:
Is there any way to access a dialer on this ROM? I've read there are some codes to pull up Wacom calibration. I wanted to try and see if it could fix a pen offset.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
have you had a look at the log generated in TWRP it usually will tell you why it failed?:confused:
[Galaxy Note 10.1 (2014 Edition) Android Developmen] whynottoday:
Really great rom. ?

is there any way to disable only hardware back key and menu key BUT not home key?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] temasek:
You can disable hardware keys altogether.

When u enabled home button wake, the settings will honor home button wake even if u disabled hardware keys.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] whynottoday:
Yes I know that but I need to have home button key always working and not only to wake up the device

Thanks
[Galaxy Note 10.1 (2014 Edition) Android Developmen] mosimchah:
Go to settings-buttons and configure the menu key and the back key to not do any action when pressed.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] whynottoday:
It is not possible to configure the back key. Only menu and home available within settings buttons
[Galaxy Note 10.1 (2014 Edition) Android Developmen] mosimchah:
Oh, I didn't notice that. You could try covering it with tape or something so it can't detect touches.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
I'll take a look for you guys for next release [emoji1]
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Genebaby:
I'm on 15.5, seems really good.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] enotar:
Yeap and something change; battery life is a lot better.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
tried to emulate the manner in which the other keys are programmed to which doing the same for the back key does not do anything. potentially it is coded elsewhere due to at minimum a functioning back key is a must i would say.

new build is uploading currently.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
Build 15.6 is now up on both sites, cheers
[Galaxy Note 10.1 (2014 Edition) Android Developmen] whynottoday:
Thanks. I do not see back key within settings buttons yet. For next release I hope?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
If u read above I did answer it. I also asked temasek after my attempts to which he replied on twitter

[MENTION=4144316]joshndroid[/MENTION] Atm no. U can comment out the back key in /system/usr/keylayout/Generic.kl
[Galaxy Note 10.1 (2014 Edition) Android Developmen] enotar:
Keyboard still fc sometimes here even the downloaded google one now
[Galaxy Note 10.1 (2014 Edition) Android Developmen] temasek:
Turning on "Disable fc notifications" in dev options and forget about it.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] tron1911:
Excellent work, the Rom is running like a charm! (Already loved ur S3 Roms!)

Is there a way to disable the "cloud" around the wallpaper in Trebuchet? This kinda annoys me and I dont seem to find an Option for it...

Cheers,

Dennis
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
Not using trebuchet I have no idea. I use nova launcher. It would surprise me if there wasn't a setting for it somewhere
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
Build 15.7 is now live on both sites, enjoy. Sorry it took a few hours extra
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Bracher:
Unfortunately the link to the download does not work (I'm using Firefox)
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
Just checked both sites and as of 8/15 builds are there on both so I'm unsure how to assist further.. Romhut already has 18 downloads
[Galaxy Note 10.1 (2014 Edition) Android Developmen] enotar:
Works fine here even update auto this time.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] icon123:
Does anyone else have a problem with the app bar locking up the device when you are adding apps to it? It is doing it in the latest 2 versions. I haven't used this rom prior to them. I have done a clean install in both cases. Every time I try to add the 2nd app it locks the device. The image of the app i was trying to add remains in the screen. The hardware buttons still work, but no touch input works. I have to hard reset the device. Let me know if you need a logcat. Thanks for the rom.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Bracher:
Finally it worked, but had to rename the download it was named "devs" announced as a sort upstream file but the size was correct. So I renamed it into cm_12.1_20150815-lt03wifiue-unoff-temasek.zip and installed it. Everything works fine and I'm rid of all bloatware and spyware - Thanks a lot!!!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
[MENTION=2084304]icon123[/MENTION], @ joshndroid

Jes! I can confirm that the screen freeze if you try to add more than one app icon to the appbar. I have accessed the appbar settings over the app bar con.. button from the end of the list not from settings- temasek spare parts- appbar.

No idea if this could have any impact?

If you already have made a logcat it would be nice if you post it here.:good:

Thanks for the quick note!

:good:

---------- Post added at 07:30 PM ---------- Previous post was at 07:27 PM ----------

Hi Bracher!

Works here!

Downloaded "to the right folder" now with build-in ota-updater app, normal "zip" file!

:D
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Bracher:
sorry it still says "application/octet-stream (253 MB)" and the final download is named "devs" but don't worry I renamed it and flashed afterwards with success - so I'm happy
[Galaxy Note 10.1 (2014 Edition) Android Developmen] enotar:
Same here
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
Okay guys temasek is aware of the issue and no doubt week be looking into it. He advises to disable app bar for now of seeing the issue
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
also; recieved this from temasek via twitter

temasek ‏@temasek71 3m3 minutes ago

NOTICE: Do NOT attempt to use AppBar in temasek build. There is a major bug that causes screen to freeze. This AppBar will be removed temp.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] icon123:
Thanks for the heads up. For anyone that is addicted to app bar (me), you can add or remove apps by adding or removing one at a time, saving and rebooting. Then repeat.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] mosimchah:
Thanks for the update! There is only one issue: the ROM is vulnerable to the CVE-2015-3864 part of the stagefright vulnerability.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] dimex:
Isn't the exploit MMS related or accessible through messaging apps only, like Hangouts? I have the P600, so MMS isn't possible, and I don't use Hangouts on this tablet to chat.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] mosimchah:
Yeah, well like you said it's a problem for people like me who chat on hangouts.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] temasek:
AFAIK this issue is new and was just acknowledged by Google. Atm no fix yet
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
If u followed any of us on twitter you would have seen tema and I have a discussion about this a few days ago. If your an Aussie and watched 60 minutes and freak out about their sensationist story, relax. Cm have updater every fix possible thus far, google have acknowledged this further vulnerability after it was further discovered. There is no fix for it yet from google so in effect no ROM is immune, it will be fixed when there is a fix available. Till then disable auto retrieve MMS on all your android devices and essentially don't rely on messaging services to obtain photographs and video, text based seems to be immune as as far as I'm aware the vulnerability is video codec related. The exploit is actually hard to conduct if anyone read Google's and others responses you need to be extremely skilled
[Galaxy Note 10.1 (2014 Edition) Android Developmen] mosimchah:
Thanks for the info (I'm not Australian by the way), however I think that slim lp has a fix for it, I say this because I have a slim lp based ROM on my phone (lg l90) and the issue is fixed.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
Maybe

http://m.theregister.co.uk/2015/08/13/stagefright_patch_needs_repatch/
[Galaxy Note 10.1 (2014 Edition) Android Developmen] dimex:
Yea, well I think you're still overreacting.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] temasek:
I stand corrected.

CVE-2015-3864 was patched by Google & merged by cm.

I merged Android 5.1.1_r13 of frameworks/av sources which override the fix.

I'll push the fix back to frameworks/av later and next build will have it. CVE-2015-3864 is considered closed.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
ROM will be up in the morning is currently uploading while I sleep its 1am here. Will have latest fixes and appbar is fixed
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
New build 15.8 is up on both sites, all vulnerabilities thus far to stagefright have been implemented, should see no vulnerabilities. The appbar has been fixed which was due to an issue in frameworks so thats good.

After some good success i have changed the link in the second post relating to gapps to opengapps. They are realistically a daily gapps package which can be built for a multitude of devices. I have had some good results with the micro, mini and nano packages over my devices (mako, hlte, flounder and lt03wifi) so give them a try.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ultim:
I assume i will lose all spen features if I install this rom?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] dimex:
Do a search and buy the app S-Pen Command, works great for custom air command, screenshot annotation, etc.