yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ArmadiloDS:
Hey guys,

is CM12.1 more stable or why do you still compile it?^^

Btw. tried this piece of cake for 3 weeks now and only thing that is bad for me is the s-pen issue described one page ago. THANKS FOR THE AWESOME ROM!!!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] brkoMostar:
Link problem, https://basketbuild.com/devs/Joshndroid/Temasek Roms/lt03wifi

two .md5sum files?

no .zip file
[Galaxy Note 10.1 (2014 Edition) Android Developmen] franzli:
Thanks!

Yes, I initially didn't have the lt033g tree in the manifest, but I tried it out when i got build errors. Will yet again without it.

I tried a couple of times to flash the updated version you offer, but ended up in a bootloop every time for some reason. Should have raised this here earlier, I guess.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
V9.2 is up on both sites I spun a fresh build yesterday after fixing up my build machine... It has some test commits I had been playing with in stock cm testing.. Camera is still dead but hoping some other improvements
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
No more distorsions?!

[MENTION=4144316]joshndroid[/MENTION]!

Yeah, long story short, screen distorsions seems finaly to be gone! Unbelievable!!! :highfive:

I have no doubt you'll make a perfect job and finaly also get the camera back working!

Also battery runtime has improved with the last few releases.:good:

Keep up the good work, Joshndroid!:cool:
[Galaxy Note 10.1 (2014 Edition) Android Developmen] franzli:
Quick update, without the lt033g device tree, repo sync fails with the following (which was the reason why I tried to add that in addition in the first place):

fatal: repository 'https://github.com/CyanogenMod/ShevT/kernel_samsung_lt033g/' not found
fatal: repository 'https://github.com/CyanogenMod/CyanogenMod/android_packages_apps_SamsungServiceMode/' not found
error: Cannot fetch CyanogenMod/ShevT/kernel_samsung_lt033g
fatal: repository 'https://github.com/CyanogenMod/CyanogenMod/hardware_samsung/' not found
error: Cannot fetch CyanogenMod/CyanogenMod/android_packages_apps_SamsungServiceMode
error: Cannot fetch CyanogenMod/CyanogenMod/hardware_samsung

error: Exited sync due to fetch errors

This is with the manifest as follows:

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

If I uncomment the device tree or the various CyanogenMod projects, I get:

fatal: duplicate path device/samsung/lt03wifi in /media/georg/fastschloider/dev/temasek-cm12.1/.repo/manifest.xml
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DeanoD:
I downloaded the 9.2 zip file from basketbuild. My concern is the multiple MD5 files for that version. As well none of the MD5 files posted are a match for the 9.2 zip. If I flash this ROM without the MD5 match, what problems might come up? Or am I just being toomuch of a Noob? ;-DeanoD
[Galaxy Note 10.1 (2014 Edition) Android Developmen] enotar:
Still screen distortion here when rotating. Sorry.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
Your repo names are wrong check them

I have to wait till I'm home... Because I was using testing dog want pulled and u had to manually change

What bootloader u on? And you [MENTION=1399323]ollim[/MENTION]i
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Hey DeanoD!

Look at the date! Take md5 from yesterday it matches well!

---------- Post added at 09:03 ---------- Previous post was at 08:56 ----------

Hey Joshndroid!

I'm still on 4.4 bootloader and to my shame I must say I was too fast! :angel:

There are still a few distorsions but much less and the screen rotates so fast that it's hard to see it!

Tired eyes last night, lol!

Sorry!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] enotar:
9.2 has a problem with charging. Slow, in one night tablet did not charge completely. Masybe calibration?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DeanoD:
update:problem solved.

After multiple files dowloaded and MD5 CHECKS, I FINNALY found the right match. It also didn't help that one of the two file checker apps was giving me false numbers. So far, install is running solid and well. Thanks for all the replies, too!

;-DeanoD8
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
I put a note down to take a look... But go to here

https://github.com/CyanogenMod/android_device_samsung_lt03wifi/blob/cm-12.1/cm.dependencies

Use the cyanogenmod repos only don't use Joshndroid ones the cm ones are my trees pushed there anyway.

I also see that your repos have cyanogenmod/cyanogenmod which is incorrect in the names

Cheers for that. I was sure it wasn't completely gone but some remained but when u said it was fixed I did get a little excited and hoped there was something different firmware wise on your device that would have accounted for it lol

As I said for this one has a lot of testing commits picked from the tab s guys. I have alot of their camera based ones that work for them and it still won't fix our camera it's extremely frustrating. It also has different soc related trees and most up to date vendor and it still won't work... Is anyone on 5.1.1 bootloader? Kernel is right up to date, the vendor is from 5.1.1 and device tree is as Hugh as it will go

Sorry I didn't get back to u. What happened was I had a build and Google drive crashed overnight. I had a secondary external app for Google sync that I have no replaced the official one due to scoring it on a promo and it being a bit better in that it won't try to sync 5 files at once (making each go extremely slow) and it shoes a progress bar. So what I did was rebuild a fresh build and due to the md5sum being such a small file size as soon as I move those they sync and then will auto sync to basketbuild so while I thought they were gone they only were removed from drive and not basketbuild lol
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Hmm!

Charging speed is normal here and I'm also on latest v9.2!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
those of you stuck in a time warp, V19.5 of CM12.1 is up after tema updated some trees:p
[Galaxy Note 10.1 (2014 Edition) Android Developmen] franzli:
Great, thanks a lot!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Stogie87:
Can you bring up a cm 12.1 build with wide brightnessbar?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
Wide brightness bar I am unsure what your talking about?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Orion116:
Wide QS shade.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
Notification drawer size or a specific tile?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Orion116:
No clue. I think the entire thing.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Stogie87:
Lol, i was a little bit dumb, yesterday. ^^ I meant a wide dropdown menu. :)
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
[MENTION=4144316]joshndroid[/MENTION]!

Notification/quick settings drawer was meaned!

I know from time that the last 5.1 release have an inch or half inch smaller notification/quick settings area as the last build before!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
Sweet as, I used to do it manually each build I'll dig it up or look for an alternative
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Tiemichael:
Thank you for taking care for those us who cannot upgrade to CM13!

I installed C12.1 V19.4 a few weeks ago and encountered every few hours a 'strange hanging' of my device (sudden black screen and and only reacting to a 20 second long press of the power-button).

Reverting back to V18.5 immediately resolved the issue.

Now I tried the new V19.5 and I see the same issue again.

Logcat shows a lot of McDaemon-Errors

I/McDaemon( 7515): Daemon starting up...
I/McDaemon( 7515): Socket interface version is 0.2
I/McDaemon( 7515): *** t-base-300-Ares-2-Android-V001 ###
I/McDaemon( 7515): Build timestamp is Jun 14 2016 18:09:03
E/McDaemon( 7515): *****************************
E/McDaemon( 7515): *** ERROR: ioctl MC_IO_MAP_MCI failed with "Not a typewriter"(errno 25)
E/McDaemon( 7515): *** Detected in mapMCI/129()
E/McDaemon( 7515): *****************************
E/McDaemon( 7515): *****************************
E/McDaemon( 7515): *** ERROR: pMcKMod->mmap() failed: 190012
E/McDaemon( 7515): *** Detected in getMciInstance/418()
E/McDaemon( 7515): *****************************
E/McDaemon( 7515): *****************************
E/McDaemon( 7515): *** ERROR: getMciInstance failed
E/McDaemon( 7515): *** Detected in initDevice/129()
E/McDaemon( 7515): *****************************
E/McDaemon( 7515): *****************************
E/McDaemon( 7515): *** ERROR: Could not initialize <t-base!
E/McDaemon( 7515): *** Detected in run/137()
E/McDaemon( 7515): *****************************
E/McDaemon( 7515): *****************************
E/McDaemon( 7515): *** ERROR: Exiting <t-base Daemon
E/McDaemon( 7515): *** Detected in main/1389()
E/McDaemon( 7515): *****************************

Any idea what is causing these problems?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] franzli:
Unfortunately, for me the CM12.1 v19.5 yields a bootloop, just as with 19.4 before. This happens both when I dirty flash over 18.5 and when I attempt a clean flash.

I tried getting a logcat, but there's no output, so I guess it's not even getting to the point of enabling adb. [MENTION=1012406]tier[/MENTION]michael, you seem to have at least been able to flash without problems - I wonder what I'm doing differently.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Tiemichael:
In my first attempt of installing V19.4 I did the usual wipe Cache / Dalvik Cache / System

When I encountered the above mentioned problems for the first time I re-flashed V9.4 with a factory-reset, but I did not change anything

For V19.5 I just did the usual wipe Cache / Dalvik Cache / System

Do you have Xposed installed? I had problems with bootloops caused by Xposed ...
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DeanoD:
9.2 build is back to random reboots. Seeing the rate increasing as well. ;-DeanoD
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
We not on build 9.2 we up to 9.6 which will be building shortly
[Galaxy Note 10.1 (2014 Edition) Android Developmen] franzli:
Thanks for your reply. And no, no exposed. On my last attempt for a clean flash, i didn't even flash gapps just to see if at least the bare version boots. Strangely enough, it doesn't for me... How long did you have to wait until the boot animation stops and the optimisation screen starts? Normally after flashing this doesn't take longer than 5 min for me and I waited at least 10 min this time, and on another occasion about 30 min.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Tiemichael:
Usually I install 6 items at once: new ROM, GAPPS, SuperSu, Xposed (once in a while), V4A2.3 (audio amplifier / equalizer), Remove Pointer.

It takes about 2-3 minutes for the complete install before the optimization starts.

I remember having very long installation times (maybe 20 min) when using F2FS, but I prefer EXT4
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Strange! I've not a single reboot since month. [ironic]

You can cry about bad battery performance or sometimes higher temps as usual, but the rom self works stable, with no reboots or freezes at all!

I would in your place not post such unqualified statements because it's definately "not" the rom!

Better do a thorough troubleshooting to explore what is really wrong with your setup!

Would it be a rom related issue, the thread would be full of such statements like yours, Lol!!!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] israel_andrade:
I've experienced the random reboots also. a few times just browsing on the internet using chrome.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] mosimchah:
Were you using the s-pen when the random reboots occurred? There's a bug where surfaceflinger will sometimes cause the tablet to reboot when using the s-pen (it does not always happen though). I've seen it happen with chrome, Nova launcher, squid, OneNote, and a few other apps.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DeanoD:
You hit the nail right on the head. The reboots (that I've been experiencing)DO always happen when I am using my s-pen. And since my hands have limited motion, it is often when I unknowingly hit the side button on the pen. Although I have no functions for the button set.

Makes some sense for the glitch. And I'm sorry if I offend anybodys work with this ROM if I make simple observations and post them. I though that would be the purpose of having a forum. ;-DeanoD
[Galaxy Note 10.1 (2014 Edition) Android Developmen] israel_andrade:
No, I was just loading up an app. No temp issue, can not remember which app. Out of nowhere, it rebooted.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] mosimchah:
Are you using Xposed?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
Just merged a couple kernel commits from shevt and deadman in relating to charging hopefully we get a little better charging
[Galaxy Note 10.1 (2014 Edition) Android Developmen] israel_andrade:
No, using ROM as is. Nothing too invasive as far as apps go.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Bracher:
Sorry it looks as if I'm stupid but I did not find V19.5. Could you please help me?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Tony66:
Please;)

https://basketbuild.com/devs/Joshndroid/Temasek%20Roms/lt03wifi/cm-12.1
[Galaxy Note 10.1 (2014 Edition) Android Developmen] enotar:
9.3 is running ok. Same issues. Battery life looks better.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Shadehawk:
Sorry if this has been answered, but will this dirty flash on top of raymans build or will I need a fresh install?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Hey Shadehawk!

I would recommend do a clean install because there are many changes from stock cm12 to Temasek. And not forget do a nandroid backup in front of the installation and make sure you are on TWRP2.6.3.3 to avoid issues like bootloops or something else!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] josepr2012:
Wohooo...XPosed Module Coming soon for Lollipop

http://xdaforums.com/showthread.php?p=58282427
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Tarasque174:
Good find! Cannot wait for the release!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
Build v7.5.1 is up on basket build .. Comes with wider notifications panel
[Galaxy Note 10.1 (2014 Edition) Android Developmen] apokit:
Basketbuild seems to be down......it says:oops an unexpected error has occured.....
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
Gosh not having much luck last few days with anything. Only just finished updating and syncing to them and yet is now down. Shouldn't take to long to be back online
[Galaxy Note 10.1 (2014 Edition) Android Developmen] josepr2012:
Downloaded without problem...thanks for the new build.

Sent from my SM-P600
[Galaxy Note 10.1 (2014 Edition) Android Developmen] josepr2012:
Nice wider notification panel and new tiles ...wohooo

Sent from my SM-P600
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
@ Josh!

Great update! Bigger Notifications looks really good!

Little OT sidenote!

Viper_mod_2.3.3.0.zip!

I've removed not working AudioFX and DSP Manager and than flashed Viper_2.3.3.0.zip in recovery to increase the sound quality. Works really good here!

If someone is interested take it here:

https://mega.co.nz/#!6EExjS7R!WnJ1goxQjJ68TALQfXdjeoLgW5eFzJDPrEeUQwftEUY
[Galaxy Note 10.1 (2014 Edition) Android Developmen] rondera:
Great!!! Able to simply dirty flash it above a previous rom? :)

Edit: sorry, thought this was the full rom :)
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
Audio fx seems to work for me. Just use titanium backup to remove dsp manager I realised why there was both in there. Have removed the package for next release which will be uploading to basketbuild soon
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
Build v7.6 is now up on basket build
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Nameless One:
Just as I got 7.5.1 on and configured ;)
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
Not a lot of difference between them.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
[MENTION=4266699]josh![/MENTION]

AudioFX works now, thanks!

Quick settings tiles are mostly complete and works, only screen timeout tile have the known issues.

Rest is perfect as ever!

:good:
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
I think u mentioned a different user, think it only works to notify me when u put in the whole username lol

Anyway [MENTION=2332422]temasek[/MENTION] are u still getting different timing on the screen out tiles?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] hhairplane:
Xposed for CM12/Lollipop is ready to go... http://xdaforums.com/showthread.php?t=3030118
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
Please be careful with this alpha build. Many modules will not be working and in the future it can and will be likely that if you receive an error u will need to remove it and try again before posting saying something is broken. Many, many KitKat users blamed ROM defects on conflicting modules while using xposed.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] josepr2012:
This last update took me more than 1 hour to download...?

Sent from my SM-P600
[Galaxy Note 10.1 (2014 Edition) Android Developmen] koz:
On long press of the power button, there used to be an option to reboot to recovery. I'm sure there's a way to turn the option on somewhere, but I can't seem to find it. Can someone point me the way?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
Developer options - > advanced reboot
[Galaxy Note 10.1 (2014 Edition) Android Developmen] arough007:
Love the rom so far.

But is there any way to install S Note on this rom?

I found the APK but when I try to launch it crashes.

And I didn't find the pointer for the S Pen. The thing that shows where the pen is even if you are just hovering above the tablet.

Is this feature still in the rom?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] franzli:
I think it should be under settings-language and input-show icon when using stylus.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] arough007:
Indeed it is there. Should've searched a little more.

Thank you :good:
[Galaxy Note 10.1 (2014 Edition) Android Developmen] zikozoko:
Can i install this rom on p601 ?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Hi Zikozoko!

Only if you don't need full Sim functionality.

But there are other cm13.1 roms from [MENTION=3594812]ShevT[/MENTION] especially made for P601.

If you still want to try this rom make sure you did a nandroid backup in front of the Temasek installation only for the case something is going wrong!

http://xdaforums.com/galaxy-note-10-2014/orig-development
[Galaxy Note 10.1 (2014 Edition) Android Developmen] arough007:
I noticed lag and jitter while playing video and/or audio with this rom.

I first noticed while using Plex. The video seems to drop frames and the audio is full of distortions and jitter.

Next I tried Spotify and Youtube. Same problem, unfortunately.

I uninstalled the Viper4Android driver and restarted the device. Same.

The volume in general seems to be more quiet in comparison to stock rom, too.

But that could just be my imagination. It wasn't the loudest device to begin with.

If needed I could provide a catlog. Just describe the situations the log has to include.

Thanks in advance
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Hi arough007,

Did you ever installed Samsungs stock 5.1 TW rom on your device?

Sounds you are on the new 5.1 bootloader but for CM13 roms old 4.4 bootloader is necessary.

There is a how-to:

http://xdaforums.com/showpost.php?p=65631142&postcount=2293
[Galaxy Note 10.1 (2014 Edition) Android Developmen] enotar:
Anyone has problem with google services like play, keyboard etc I get a lot of popup.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] arough007:
I had the stock 5.1 installed before this rom.

This totally fixed my problem. Thank you very much ;)

I searched the thread but apparently used the wrong keywords. Sorry for the hassel
[Galaxy Note 10.1 (2014 Edition) Android Developmen] F_R_I_T_Z:
doesn't this mean that the CM partition size/table is wrong for > 5.0 bootloaders?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] epithetic:
I don't think so, but my partition table somehow got ****ed up when originally migrating from Lollipop temasek to Marshmallow (it also killed my SD card, but different story), and I lost 7 GB of storage. Flashing a factory image or anything else did not touch the errant partition(s) so completely nuking the nand and using a fresh pit was the way to go. Other people started reporting the same issue, so I outlined the process and the images I used, with due warning.

While doing so I accidentally discovered that having traces of the official 5.1.1 on the device also made the audio crackle and produced a lot of the other phantom issues people were much more commonly having.

tl;dr,

You shouldn't have to go to the same length if your partition table is fine, but it is a thorough solution. Not sure what exactly you'd have to flash if you wanted to do it selectively.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
[MENTION=4144316]joshndroid[/MENTION]

I've found many unknown alarms causing much more background activity(and battery drain) on this device.(Screenshot below)

My other device running temasek v9.4 also does not have such alarms(OP2, screenshot 2).

There is only one alarm called CONTEXT_MANAGER_ALARM_WAKEUP_xxxxxx on OP2 but there are 11 on p600 with mostly the same setup and they are not exsistent on OP2.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Deleted, double post!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
V9.4?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Yepp!

But OP2 is v9.3 currently!

Any idea what could be the cause
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
I moved this one back from testing branch to see if anyone noticed any differences for 9.4 I have a couple new commits from [MENTION=6176472]Orion116[/MENTION] in next release. I have read that tab s exynos5420 guys are having some issue with camera once again as well if I remember correctly..