yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Tony66:
https://download.cyanogenmod.org/?device=lt03wifi

CM12 for p600 - far as I know, there does everything.;)
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Hi edmondt!

V18.5 is the latest 5.1.1 Temasek release, if you want download is here:

https://basketbuild.com/devs/Joshndroid/Temasek Roms/lt03wifi
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Zionator:
The last few versions of the ROM don't work with the gapps. Every time I try I get system error.

Does anyone know how to get play store if gapps fails¿
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Stogie87:
Flash rom, flash gapps and flash rom again. Then reboot.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Genebaby:
18.4 was the last 12.1 without issues, it's better to use than 18.5.

There is a link to it a little way back.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
If someone can provide the link I'll re-up it...

I was playing with some commits for camera the other day but still seems to get issues with it crashing.. Been trying to learn what some of the errors are from the logs
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Genebaby:
18.4
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
V8.3 is up on Google shares and basketbuild
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Zionator:
I did but I still get spammed with play store fc. I have now gone back to 12.1 as 13 is way to f'ed up.

---------- Post added at 01:56 PM ---------- Previous post was at 01:55 PM ----------

BTW I am using 18.5 and it's working fine. What makes 18.4 better then 18.5 ?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] israel_andrade:
would it help if I send catlogs for different camera apps so you might be able to find a commonality between them?

---------- Post added at 08:11 AM ---------- Previous post was at 08:10 AM ----------

do not forget to clear the cache after loading gapps.

---------- Post added at 08:45 AM ---------- Previous post was at 08:11 AM ----------

do not forget to clear the cache after loading gapps.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Hey Zionator,

18,4 has a bigger notificatio/quick settings area so far I can remember the rest should be more or less the same!

---------- Post added at 16:25 ---------- Previous post was at 16:08 ----------

Have you tried to install an older Temasek release maybe v.7.5 or 7.7 with gapps, subsequently set up the device and then dirty flash latest release on top?

I never had this PS fc's. I would try to start from scratch with an older release and an up-to-date Open Gapps package(pico should work!) and look if the fc's are gone!

Another thing is, it seems if you ever had installed samsungs latest 5.1 touchwiz release on your device you have to revert to the old 4.2.2 bootloader to get CM13 roms to work without such errors!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Zionator:
Ok thanks. Yes I was in lollipup but 12.1 is working fine for me without errors so I'll stick to 18.4.

Thanks for the explanation.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] aronchav:
Is something wrong with multiwindow, or is it operator error? I was using multiwindow in an old version, and just updated to 8.1 but the little button for multiwindow is no longer on the recently used apps cards. I do have it enabled in developer options.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Orion116:
Did you enable it?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] aronchav:
Yes. It is enabled. I did it several times and rebooted just to make sure.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Genebaby:
There were reports of issues at the time of release so I stayed on 18.4 and then it turned to MM and 6.01, which I haven't installed yet.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Hi Genebaby!

I strongly disagree the most errors are user related!!

The rom is working like a charme here (except from non working camera, distorsions while screen rotates and a bit higher battery drain.)

The most issues users have are 5.1 bootloader related and they have to revert to the 4.2 bootloader.

I've never installed 5.1 touchwiz and use this rom for month from the first release and [MENTION=4144316]joshndroid[/MENTION] did a great job because at the starting point it was better and more complete like 5.1 in his beginnings!

You can try it securely with a fresh nandroid backup in background and you can always switch back!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Genebaby:
Have a look back to when 18.5 came out, there was a reason I didn't update, not realising that it was also the end of 12.1.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Hey aronchav,

I'm on v8.3 and have no issues with multi window feature using omni switch

Try the following:

Enable Omni-switch in setting>temasek spare parts>recents.

Press recents button on navbar, long press the app window which you want to open in split screen mode and choose left or right.

Should work!:good:

---------- Post added at 09:32 ---------- Previous post was at 09:28 ----------

Yepp!

Notificatios/quick-settings area was 25% smaller as in 18.4!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] aronchav:
Thanks olli! Turning on omni-switch worked. The last version I was using (a very old one) didn't go through omni-switch, but just used the standard recent apps cards.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] temasek:
Temasek spare parts, screen and animations, floating windows
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
[MENTION=4144316]joshndroid[/MENTION], [MENTION=2332422]temasek[/MENTION]!

I've found dmesg is reporting debug messages every 100ms from s3c-fb and s5p-dp, and battery usage is clearly higher like it should. See below for example output.

Was the debug flag left on during this build? Any way to disable this extra debug output?

I found this output since I'm using this rom and I've tried anything to get better battery results like on my other devices running also with Temasek cm13.

[ 1442.347377] [B1: surfaceflinger: 2439] s3c-fb exynos5-fb.1: s3c_fb_psr_exit -

[ 1485.523272] [B1: surfaceflinger: 2439] s5p-dp s5p-dp: FB_EVENT_PSR_EXIT time = 31086 us

[ 1524.528225] [B2: surfaceflinger: 2439] s3c-fb exynos5-fb.1: s3c_fb_psr_exit: FIMD is already on

[ 1558.453869] [L0: surfaceflinger: 2439] s3c-fb exynos5-fb.1: s3c_fb_psr_exit +

Another thing have to do with the governor tunables from the interactive governor like [MENTION=1738252]tincmulc[/MENTION] has found.

It seems changing hispeed_freq from 1900000 to 650000 like in 5.1 roms removes all of the warnings and errors in dmesg and it improves also battery life and SoC behavior and should be a standard setting in this rom.

Quote:

[MENTION=1738252]tincmulc[/MENTION], post #2775

What is different on this rom is the configuration of the interactive governor. So far I found the best thing to do is to set hispeed_freq to 650000 (which is the maximum A7 cluster frequency of 1300MHz), which mostly solves the "only using 250 and 1900".

Below a few screenshots from 2 sec. dmesg output and what I have changed on governor tunables.

---------- Post added at 19:28 ---------- Previous post was at 19:25 ----------

Hah, great!

Now that I have a questions you have a look to our thread!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Enzymaticracer:
Hey All,

I've been having issues where my device was taking forever to wake up, and battery life has been quite terrible. Updating to several newer versions (either dirty or fresh) haven't fixed the issues.

Earlier today, I accidentally enabled "Selinux" (fat fingered it... never intended to toggle it) and now Settings crashes any time I try to turn it off. After that, my device almost never wakes up.

I've been using this build for a few months now, but unfortunately, I think it's time I downgrade back to 12.1. I basically just need to download the 5.1.1 gApps and the 12.1 rom. wipe everything and then install right? I'm obviously already running TWRP 3.0.0-1.

Hopefully in the near future I'll be able to give this ROM another shot. Thanks for all the hard work!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Hi [MENTION=4144316]joshndroid[/MENTION]!

Yesterday I've searched for a possible bug in surfaceflinger behavior and I found out that guys in p900 forum had the same issue with surfaceflinger a year ago and it was identified as a culprit for the additional battery drain.

I have ask [MENTION=2047373]Valera1978[/MENTION](maintainer unoff. cm12.1/p900 thread) per pm how he solved that issue, but unfortunately no answer till today.

But I am confident that he will answer soon.

I've also posted the corresponding posts und dmesg outputs yesterday and hope you are able to verifiy if I'm right or wrong...

One thing is certain, there is a background process, sucking continuously on the battery and this surfaceflinger dmesg output occurs all 100ms and seems to be definately not normal!

I have it also Identified as battery drainer with 3C Battery Monitor, see screenshots below!

(I have 30-50min activity in two days on my other devices and 1h:55min in 2,5h of use on my p600)

And there is also much more activity while screen is off like you can see on BBS screenshot!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
i've looked through his commit history as well as other devices for that.... cant seem to find anything glaring out at me.

I also have looked through maybe it over logging surfaceflinger but even then is already incorporated for us.

I also have been looking through a variety of trees to see what can be done for camera... i have picked a few common commits people seem to be using but not having any success.. i need more time to work out what some of the issues within the log is... i can trigger the issue easily and can see it i just need to work out what it means, its not very descriptive...

I did find a way to limit the hispeed_freq and have added it for this now uploading release v8.4, prior to that i did a bit of research into what that actually does as well as some other kenerl aspects as i am not well versed in kernel stuffs. it seems rather harmless to experiment with so hopefully all good in that respect, my initial testing seems fine so far.

I lastly have been looking to see what may be a fix for the graphical glitches. I again have been looking through some trees, etc but havn't found anything yet. Ultimately i may be notified of the fix itself but ill keep looking once i have some more time.

I am currently undertaking a pretty intensive course for work... taking up on average 12 hours of my day from when i leave in the morning, till when i get home.... so time is at a premium once i return home and do assessments and further study. While its not necessarily hard, the short duration for the qualification means i must learn a significant amount of material both practical and theoretical in this time. I am still learning as i go, and the shortened time for the next couple of months does hamper me a bit.

Either way, v8.4 should be completed in a some hours and it will be sync'd to basketbuild while i sleep.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Cool, the first steps to make the kernel more battery friendly are done, let me hope for the future. :cool:

Sometimes 24 are not enough to stem the workload of a day!

I know exactly what you mean, Lol! :highfive:

Incidentally, I'm using 3C toolbox free version from plays to have a look into this kmesg outputs. You can add a shortcut to your home screen then choose warnings or errors for filter in kmesg window.

This output the occurs every few 100ms on both of my p600wifi.

Howsoever!

Many thanks that you spend your free time with reading tons of device trees;) :good:

Keep up the good work!

Edit: [MENTION=2047373]Valera1978[/MENTION] has answered but he unfortunately can't remember what it was because it was one year ago. But he have a T700 also with the same exynos 5420 base and will have a look if there is the same strange behavior.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Orion116:
OK. I have also been doing research for every thing from the camera to the distortions to screen recording not working. The last to are linked to the fact gralloc is not working right. This is also why in the logs you see SurfaceFlinger errors. SurfaceFlinger is part of androids graphics architecture and gralloc, along with HWC, is the device component of SurfaceFlinger. If anyone remembers during LP BrokenOS did not have the distortions that temasek or CM12.1 had. I believe this is due to the fact I was using older hardware repos then josh was. As part of the update to the new hardware we got switched from using 5420 gralloc to using 5422 gralloc, so what I am going to try is revert the offending commits for BrokenOS M and then let you all know if it worked. I have a few ideas that [MENTION=4144316]joshndroid[/MENTION] may have not tried for camera.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
V8.4 is up on Google shares and basketbuild
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Hey Orion 116!

Good find, realy!!!:cool:

It seems we come closer to a solution!

Thought I was going crazy, Lol!

I've also noticed much more activities while screen is off! BBS reported day for day 35% screen-of activitiy in deepsleep!

We should realy do a test with the "old" 5420 gralloc like you said to see if it solves things?

I'll place my hope in you!:good:
[Galaxy Note 10.1 (2014 Edition) Android Developmen] franzli:
MHL/HDMI support?

I've been using the ROM for ages, but recently wanted to start using an MHL adaptor to mirror the screen to a projector/monitor via HDMI. So far, I haven't been successful with the older CM12.1 v18.5 version. Does anyone have experience with MHL on this ROM, or do you know if there are some general problems? Any advice welcome!

(I'm pretty sure that I had MHL/HDMI mirroring running at some point with a CM12.1 ROM on my Galaxy Tab S, so I would think it should be possible in principle.)
[Galaxy Note 10.1 (2014 Edition) Android Developmen] F_R_I_T_Z:
I don't have time to do it and I[ m almost 3 years out from this things. But how about to do a diff between the exynos 5420 devices WORKING, in specific inside the drivers / video ( s3c*** and s5p*** )? And maybe doing a deeper diff insto EXYNOS video driver folder to find similarity and differences between them ( screens, gpu)... and and maybe a blind try to try with this?

Just wondering...
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Orion116:
I am working on doing at this week.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
V8.5 is up on Google shares and basketbuild. Will have some time over the weekend to play
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Masterchivo:
Hello. I just updated my old build to the latest 6.0.1. But now my otg usb is detected but i cant access the data inside. I change the format from fat32 to exfat but it still the same.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] algieba:
Hi,

I have the problem, that the Screen-Mirroring to the chromecast doesn't work. When I turn this option on, the screen of the TV is switching to black. With my Nexus 5 on cm13 it works perfect.

I'm running version 8.4.

Thank you
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Stogie87:
Screen mirroring never worked with any temasek build for p600. So don't expect this will be fixed in near future...
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DeanoD:
I'm darn glad that I backup all my stuff and keep the last confirmed ROM zip files! I got a bad download with v 8.5 with md5 errors, so I re-flashed v 8.4, then downloaded a new copy of v 8.5. Did an md5 check, first, tho. It seems to be fine now, and smooth&fast.

One thing that I have noticed is that I can no longer access a usb drive with a dongle. Been a while since I needed the jump drive access, but I do miss it. ;-DeanoD
[Galaxy Note 10.1 (2014 Edition) Android Developmen] enotar:
All ok here
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Jaydawgx7:
It's been a while since I updated, the last built I was on was still on Lollipop, but finally updated to the May 19th build. The IR blaster no longer works properly. I cannot seem to get it to send the right signal to my tv to control anything (using anymote which worked yesterday on the old build). Looking at the IR sensor on top through my phone's camera, I can still see it lighting up, so it's obviously still trying to send out some type of signal, but doesn't control anything. Anyone else have any ideas or similar issues?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Stogie87:
Infrared doesn't work since build 5.5 or 5.6. I'm also waiting for a fix, because i want to use anymote as well to control my tv and HiFi system. Until then i will stay on stock rom.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] enotar:
Same with me and Roku connecting but freeze
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
V8.6 is up on google shares and basketbuild
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
for those of you who still rock the cm-12.1 variant i have managed to get the latest version working from tema source v19.4 based on cm-12.1...... does not have large notification panel width tho, just stock size. Is contained within google shares for those interested under a seperate folder labelled cm12.1 the cm-13.0 releases will remain in the root directory. I may do another build if temasek updates, its mainly due to him keeping soem life into his tilapia so is not a definite thing.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DirkStorck:
Would it be possible to port the large notification panel width to cm13?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Tiemichael:
That would be great!

As long as the Camera is not working with CM-13, I cannot move on ...

Thank's for all your hard work!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
the overlay is alread there, same value as in cm-12.1 - https://github.com/Joshndroid/andro.../base/packages/SystemUI/res/values/dimens.xml

well i been working on the camera all weekend and seeking some advice from tab-s maintainer but still getting issues. The camera atleast boots further than before but still wont allow for a picutre lol
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DirkStorck:
Does this mean that it come in a few builds? :)
[Galaxy Note 10.1 (2014 Edition) Android Developmen] SamsungGalaxySamsung:
Hi,

Can I only download this from Google? Is this the same as the v18.5? If not, could you please put it on basket; I'm not in your gmail group.

Sorry for the inconvenience.

Thanks!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] planetf1:
Hi,

I'm currently running stock 5.1.1, though have flashed previous devices/samsung phones with odin many times. I can't promise to have read the entire thread but the gist of what I see with this rom is that it's generally ok, but the camera basically doesn't work at all. There's some animation issues on rotate, and some suspicion over power drain. There's ongoing changes by temask, and the guys here are merging in device tree updates as they can. Fair summary?

* Does anyone have any video or can elaborate on the impact of rotate? Just looks clunky or a functional issue? Is it only rotate or is other screen interaction a bit lumpy?

* Can anyone give a % figure to the battery impact. Are we talking not quite as good as stock, or is it massive. Is it that the device doesn't sleep? Too much active time? Or is it higher drain under load?

* What have I missed

* Has anyone tried running this rom non-rooted (in particular within /bin/su etc)... I ask since I may wish to run skygo, and I know it checks for root... years ago I used to try hiding root which didn't help, so it needs a more severe fix like file deletion :) As an aside anyone tried to see how MAAS360 works (corporate MDM : root not permitted)

Apologies again if I'm repeating popular topics here :( .. .Also I am quite happy doing a nandroid backup and restoring if it's not for me... but worth checking first

thanks!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
cant promise anything

just chill for now while it finishes uploading it will be there

1. Little artifacts come up on the screen as it rotates. It doesnt necessarily affect anything, it happens to almost all exynos5420 based devices

2. Battery life any rom other than stock samsung is goign to be worse.. cm-13.0 probably a little more moreso than cm12.1 but i dont see the drain others speak of

3. havnt missed to much most of cm-13.0 is working except for IR blaster, camera and the rotation.

4. hmm... rom is built is a userdebug build, so it has root but it is not activated until manually done so by the user but the files may still show. i can do a non root builds but that would require almost all users to be on board as long as they already flash supersu as root already
[Galaxy Note 10.1 (2014 Edition) Android Developmen] planetf1:
Thanks Muchly. SO a new build on the way? I'mm PM.

As to the clarification around the state of things -- thanks. I wouldn't worry about a non debug build for now (well not for me anyway). Personally I'd love root, but if I want to use sky go or corporate apps I know that's untenable. I can quite happily splat the files/experiment with adb :)
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
root is disabled by default so just dont flash anything like supersu and then try

V19.4 is up on basketbuild and google shares - CM-12.1 based only

V8.6 - cm-13.0 is already up
[Galaxy Note 10.1 (2014 Edition) Android Developmen] planetf1:
Is TWRP 3.0.2 the best to use currently? I see it's on josh's basketbuild...
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
It is the latest build built
[Galaxy Note 10.1 (2014 Edition) Android Developmen] mosimchah:
[MENTION=4144316]joshndroid[/MENTION], with the help of [MENTION=6176472]Orion116[/MENTION], I have extracted the lollipop blobs for our device: https://drive.google.com/file/d/0B6QpLGntMtYiNHdoeTJ5TUVNYms/view?usp=drivesdk perhaps you could implement them into the tree.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
The file itself u showed is only a text file, with many missing or listed as broken. Plus I have been looking at vendor along with shevt. We have both changed all the vendor files relating to camera as well as edited some of them. I want to look at it as well as remove some more radio stuff. I have some commits I have been testing not in my temasek branch but they will come eventually. I have been doing alot of testing with stock cm to eliminate as many variables as possible

V8.7 is up on Google shares and basketbuild
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Orion116:
https://github.com/CM-Tab-S/Android-Blob-Utility

Josh that is what Moshe used to pull the the needed blobs. ?*If doesn't not only pull the list it actually links what is needed in each blob
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DeanoD:
Odd results on 8.7 flash. An error message regarding a gapp version that was not being flash(?) And superSU will not accept the usual requested binaries update. Reflash or ignore? ;-DeanoD
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DirkStorck:
CM messed up the backup of gapps. They won't get restored if you flash the ROM.

Gesendet von meinem SM-G900F mit Tapatalk
[Galaxy Note 10.1 (2014 Edition) Android Developmen] enotar:
I am on 8.8 and cast to Chromecast launch corectly and I can see screen on TV on this version but tablet become not responsive and FC after few seconds.

Cast to Roku doesnt work but I suspect Roku software is the culpid.

Thanks for the update