yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
Lucky for me, i have had days off work so been able to churn builds and attempt to add support for others :good:

i too have the recents app glitches:confused:

No, the new exynos5 drivers have not been integrated i am hesitant at the moment to sync that source as im worried of breaking this build or others i am building (approx 5 devices). If i read correctly these changes were submitted to teameos github. I will have another look at their github and might fork a couple trees and give them a try tomorrow and see how i go for v4.3.

I have merged the recent changes made by [MENTION=3463426]RaymanFX[/MENTION] in relation to the camera in my fork of his device tree, it still wont work but looking at it he is doing a great job (far less errors in logcats). i will endevour to give a donation if he pulls this off as it benefits us all.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Okay, thanks!

Hope the drivers brings some benefits, but we will see! I understand that you won't break the build!

Latest 4.2 release works great so far, realy great over all performance!

My only question to improve the performance and to tickle out every last bit of performance is about App Performance Profiles. Is there a way to add it in future rom's?

Thanks indeed!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
tested a build with the exynos 5 drivers; seems to run alright - will have to see about my other samsung builds
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
Build V4.3 is now up - includes the TeamEOS Exynos5 repo worked on by RaymanFx
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Yeah!

Sounds good!

I will test the new build soon!

Clean install necessary? Or can I flash it on top?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
Dirty is fine, I dirtied.

was keeping to clean install got over it with so many flashes I just ensure I have a recent tibu backup just in case... So I just dirty flash till stuff starts breaking apps/forces closes etc
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Yepp!

Dirty flash was okay!

Seems all is running so far!

The only I see is a bad runtime performance in Antutu, but it's only a bench...

Let's see if there are other differences with the new drivers.

The feeling with the rom is okay.

Fast and snappy as always!

Little update!

All okay so far! Much less errors in logcat, most I see have something to do with memtrack modules or wifi.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] paddycr:
When you dirty flash 4.3 does the camera work? I have been dirty flashing this over RaymanFX's CM12 and have not had any problems until I flashed 4.2 over 3.8, which broke the camera.

On an off-topic note I cannot get TWRP 2.6.3.3 to restore this ROM properly. When I tried to restore from 4.2 to 3.8 the WiFi was broken. The cool boot animation was gone too, and was replaced with the generic LP boot animation. It was kind of tricky getting it all working again...

Thanks!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Hi Paddycr!

I have the same, camera is broken after dirty flashed 4.3. Also restore 4.2 will not solve the broken cam.

The cool bootanimation comes with 4.0 I believe, in 3.8 it was stock google I think. But I have another problem with my runtime performance. I think I will start from scratch with 12.05, restore the camera and try to flash latest on top after testing camera. Hope the cam is still working than! Maybe it have something to do with the new Exynos driver from the nexus10. I don't know!

Will post my results later!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
Raymanfx has been working hard on the camera. There are locations associated with files that were changed I merged these changes for 1 tree however even when just syncing the source, looking back, the camera would have broken anyway.. I'll look again may have to revert, fork a few things and revert those to get dirty flash camera hack back working but realistically camera isn't to far away
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Hi Josh!

I went into multiple issues yesterday after flashing 4.3!

At first it works okay, but later more and more issues comes up and at the end I have a nearly unusable rom! Started from scratch with 12/05 trying restore the camera and dirty flashed 4.3 on top, but the workaround is not working anymore! Later I get the same performance issues with 4.3 so I'm started again from scratch.

Now I,'m back at 4.2 release and the old drivers and rom works so far.

Any other with similar problems?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
re-read my previous post, file associations and locations were changed in device tree. This means the usual location for camera pointing to was no longer there, of course this will cause the old dirty hack method to break because its looking for a file(s) that aren't there. The up side is you can either stay on 4.2 and keep camera (i dont use mine) or keep using bleeding edge until it is fixed.

on a side note; was hoping to release 4.5 tonight, it was syncing while i was testing.. feels a bit derpy, not like previous releases (also have a low storage bug possibly from changes made to temasek source libart/toolchain). Going to hold off until tomorrows offering see how we go then
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Yes, I understand!

I want to say only did the workaround no longer works.

Good to hear it's not the drivers that caused my issues and its probably only just a bug in temaseks sources!

Will stay with 4.2 for now untill 4.5 was released.

Thanks for your support and for the hard work, you have done for us!

:good:
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Nackler:
I dirty-flashed 4.3 with gapps over 3.8 (without doing root fix) and it wouldn't boot. The Samsung logo appears once, then black screen (backlit) forever. Clearing data/cache didn't help, reflashing didn't help, changing from CWM to TWRP 2.6.33 and reflashing didn't help, reverting to 3.8 didn't help. I had to flash Rayman's 12/05 build to get it booting again, after which flashing 4.3 breaks it again identically.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] benand:
Could you give more details about that ? I didn't find the good way to enable it ?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Orion116:
It has to be done in ROM source. Because using a build script doesn't work.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
Tema moved back to 4.8 gcc toolchain which should aid in easier compilation. In saying that it still seems to be something source related on Tema side of things causing the issue, I suspect in either android build or in bionic at this stage
[Galaxy Note 10.1 (2014 Edition) Android Developmen] benand:
Bootlop debugging :

To get adb on boot after builiding the ROM i added/edited directly out/target/product/lt03wifi/root/default.prop (there must be a better clean way to do that but do not know how).

ro.adb.secure=0
ro.secure=0
ro.debuggable=1
persist.sys.usb.config=mtp,adb
persist.service.adb.enable=1
persist.service.debuggable=1

Then I launched again

mka bacon

Flashed the zip
[Galaxy Note 10.1 (2014 Edition) Android Developmen] benand:
Code involved is in kernel/samsung/lt03wifi/drivers/media/video/exynos/fimc-is-mc2/fimc-is-sec-define.c

fimc_is_sec_fw_sel in this code

int read_from_firmware_version(void)
{
char fw_name[100];
char setf_name[100];
struct device *is_dev = &sysfs_core->ischain[0].pdev->dev;

fimc_is_sec_get_sysfs_pinfo(&pinfo);
fimc_is_sec_get_sysfs_finfo(&finfo);

if (finfo->bin_start_addr != 0x5000) {
fimc_is_sec_set_camid(CAMERA_DUAL_FRONT);
#if defined(CONFIG_PM_RUNTIME)
dbg_ischain("pm_runtime_suspended = %d\n",
pm_runtime_suspended(is_dev));
pm_runtime_get_sync(is_dev);
#else
fimc_is_runtime_resume(is_dev);
printk(KERN_INFO "%s(%d) - fimc_is runtime resume complete\n", __func__, on);
#endif
fimc_is_sec_fw_sel(is_dev, sysfs_core->ischain[0].pdata, fw_name, setf_name, 1);
#if defined(CONFIG_PM_RUNTIME)
pm_runtime_put_sync(is_dev);
dbg_ischain("pm_runtime_suspended = %d\n",
pm_runtime_suspended(is_dev));
#else
fimc_is_runtime_suspend(is_dev);
#endif
}

return 0;
}

From there I can't find what's wrong device name ? device link ?

Perhaps [MENTION=3463426]RaymanFX[/MENTION] could help

---------- Post added 16th June 2015 at 12:16 AM ---------- Previous post was 15th June 2015 at 11:20 PM ----------

I managed to complete the boot process by editiing "kernel/samsung/lt03wifi/drivers/regulator/core.c"

By putting in comment line kernel/samsung/lt03wifi/drivers/regulator/core.c:1362

But I m not sure it's the right way to solve the problem ... (I m quite sure it's not)

/*_
r regulator_put - "free" the regulator source
* @regulator: regulator source
*
* Note: drivers must ensure that all regulator_enable calls made on this
* regulator source are balanced by regulator_disable calls prior to calling
* this function.
*/
void regulator_put(struct regulator *regulator)
{
struct regulator_dev *rdev;

if (regulator == NULL || IS_ERR(regulator))
return;

mutex_lock(&regulator_list_mutex);
rdev = regulator->rdev;

debugfs_remove_recursive(regulator->debugfs);

/* remove any sysfs entries */
if (regulator->dev) {
sysfs_remove_link(&rdev->dev.kobj, regulator->supply_name);
[COLOR="Blue"] [B] //device_remove_file(regulator->dev, &regulator->dev_attr);[/B][/COLOR]
kfree(regulator->dev_attr.attr.name);
}
mutex_lock(&rdev->mutex);
kfree(regulator->supply_name);

Camera seems to work fine
[Galaxy Note 10.1 (2014 Edition) Android Developmen] benand:
[MENTION=4144316]joshndroid[/MENTION] I noticed difference between your kernel_samsung_lt03wifi and RaymanFX one specially on drivers/regulator/regulator_put

Your contains de device_remove_file that is not on the RaymanFX code.

I reach my limit.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
[MENTION=4240943]benand[/MENTION] i think it is posisbly due to a previous error that i was having and I reverted it a long while back with regards to toolchain (it looks really familar)... have you just tried by syncing raymanfx cm-12.1 kernel and not from my kernel source?

is that the change you made to get a successful and booting build?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] benand:
No i didn't try Rayman Kernel yet I just saw that before going to sleep :)

The only thing I did was to comment device_remove_file.

If i got time i will try Ray kernel this evening
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Orion116:
Try building with this kernel: https://github.com/cannondalev2000/kernel_samsung_lt03wifi. It is based on raymanFX's kernel but a friend of mine added a bunch of optimizations to it, it is really fast. I have been building with it for a while. But I would try building with raymanFX's kernel first to see if it was the kernel you were using.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] benand:
Build with Rayman kernel Repo is ok for me. The roms boots ok Camera is ok front/back video ok mic is ok
[Galaxy Note 10.1 (2014 Edition) Android Developmen] apokit:
If you can Upload your rom please.....
[Galaxy Note 10.1 (2014 Edition) Android Developmen] benand:
Hello Apokit

Joshndroid will perhaps be able to release a version soon.

If not I will push my version if Joshndroid is ok for that.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
[MENTION=4240943]benand[/MENTION], sent a PM
[Galaxy Note 10.1 (2014 Edition) Android Developmen] benand:
[MENTION=4144316]joshndroid[/MENTION] I sent you a reply but I do not see it in my XDA sent box. Just tell me if you didn't receive it.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
and we are now back....

massive thanks goes out to [MENTION=4240943]benand[/MENTION] for his assistance. Can't believe something so small could cause me such a dam headache. I guess it just takes a fresh set of eyes to look at something

It would seem that i was missing some source and was able to get a build. I checked my source which was the same apart from this and once nuked/sync/built i now have a functioning rom

ROM is currently uploading for belated immediate release.:good:
[Galaxy Note 10.1 (2014 Edition) Android Developmen] djhampson:
Great work guys. I'll give it a whirl once it's uploaded.

We all appreciate your work on this
[Galaxy Note 10.1 (2014 Edition) Android Developmen] benand:
Great !! :good: wich repo did you missed ? the 5420 ones ?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
i swapped out my samsung/hardware as well as the inclusion of the 5420 kernel (whether there are actual calls to the 5420 kernel i am unsure, but whatever)
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
Alright guys massive update over the last one, obviously

Now - i would highly recommend a clean flash just to save yourself troubles down the line. Failing that i would recommend wiping system, cache and dalvik cache.

Have you latest 5.1 gapps ready to go also.

You can find the rom on romhut as well as basketbuild (OTA app functionality only works with romhut)

Hope the wait hasn't been too bad for those of you still sticking with me.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] lasentenza:
Thanks to both of you :)
[Galaxy Note 10.1 (2014 Edition) Android Developmen] enotar:
Dirty flash here and all smooth. Great update!

I will test a little more and clean flash.

Thank you for your job
[Galaxy Note 10.1 (2014 Edition) Android Developmen] apokit:
The rom is really smooth and xposed seems to work good(it didnt work with other latest roms)

The grafical glitches have been solved in other roms but on on this one.

Joshndroid thanks a lot for your work!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
Will further take a look and have h others first priority was getting something that worked
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Nameless One:
I hope there is nothing interfering with SELinux that would stop you from eventually re-enabling enforcing as default.

I think I'll have to search the various threads for the hardware button discussion that was going on a while ago, I currently can't disable the hardware back button which I never had a problem doing previously.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
just use se-linux mode changer and set it.

new build uploading.. with raymanfx lp5.1 exynos stuffs.... next build will have the wider notification bar again i forgot about it until after fresh build completed.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
Build V14.0 is live on both sites.. should get notification soon
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Nameless One:
I am well aware of the mode changer and I use it if I have to, in the absence of problems I have a preference for Android security to be set up as Google intended which in the case of SELinux is enforcing from the earliest point possible in the boot process. The mode changer is mainly a band-aid measure for when things don't work properly.

A question for those downloading the last two builds via a browser rather than using OTA, is your browser trying to save the ROM image with the file-name "devs" with no file extension?

my browser is for some strange reason.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ruud:
The download is a bin file how can i use this:confused:
[Galaxy Note 10.1 (2014 Edition) Android Developmen] r4yN:
Just rename the "devs.bin" file to "something.zip" and you're good ;)

Had the same problem when downloading from romhut, both on chrome desktop and chrome mobile

Edit: btw, I noticed that you've replaced the old Android System Webview App with the newer Play-Store version, nice :good:
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
Must be something wrong on romhut side at the moment with ota app just rename it to a .zip and is still good...

As for selinux - I am hesitant to play with repos as I'm at a good balance at the moment, yes selinux changer may be a bandaid solution but if your using it for enterprise stuff Tue fact that root can be enabled pretty much screws "security" in the first place
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Nameless One:
Despite that oddity they are one of the better sites in terms of download speed that I have experienced when getting ROMs.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DirkStorck:
I downloaded v14 over OTA without any problem and dirty flashed it....Thank you! :D
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Tiemichael:
There are some versions of Xposed around, which ones (zip and apk) did you use?

Thanks
[Galaxy Note 10.1 (2014 Edition) Android Developmen] apokit:
http://xdaforums.com/attachment.php?attachmentid=3356207&d=1433915273

Use this xposed zip
[Galaxy Note 10.1 (2014 Edition) Android Developmen] enotar:
Where is the apk?

Thank you

Found it, it works
[Galaxy Note 10.1 (2014 Edition) Android Developmen] tanguita:
Is hdmi Out (with audio) or miracast working?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
unfortunatley i don't know, i dont have nay of the associate cables

in any event - Build 14.0.1 is out, not an official build but trying to keep as many daily updates as possible like old
[Galaxy Note 10.1 (2014 Edition) Android Developmen] DirkStorck:
Does it include the bigger quicksettings panel? ?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] apokit:
Two things are missing:The bigger quicksettings panel and the fixed recents distortion....
[Galaxy Note 10.1 (2014 Edition) Android Developmen] temasek:
Grrrr

Your build newer than my fellow hlte users! :D
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
my hlte is restricted to official temasek branch ;) saves on build times haha
[Galaxy Note 10.1 (2014 Edition) Android Developmen] mikmock:
Thank you Temasek & Joshdroid

been waiting to see (read) you around this OP to thank you for all you do for my little part of the xda community and my tablet.:good::good::good:

You, joshdroid & his team have done spectacular work & I learn from all of you every time I logon.

Thanks from the hot desert sand of New Mexico :cowboy:
[Galaxy Note 10.1 (2014 Edition) Android Developmen] pictorul20:
pls fix the audio recording ( both sound and video ) for facebook messenger. it-s not working at all on this tablet. aand one advice, there-s something broken in provision ( the apk responsible for the entire network, as far as i know ) bcuz its the reason why this tablet has a little lag ( it had this kind of lag on other devices too, if you delete it, u will not have connection to anything related to network, but u will have a buttersmooth tablet). pls see what-s wrong with it. I think it`s wrong configured or the code is not optimised too well. Other than this, i love this rom , good job !!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] tanguita:
FYI I tried.. No miracast and only image through HDMI. Everything else works great.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] scarmona:
Really stupid and newb-like question here, I clean-installed v13 with Gapps mini and now want to dirty flash 14.0.1. Do I have to dirty flashl Gapps all over again as well?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
I recommend if u have a backup

Wipe cache, dalvik cache and system

Install ROM, gapps and SuperSU

Reboot

Win

I say this because it will limit chances of problems. Yes u may need up update the packages through google play if the gapps package is a tad old but I havnt had a problem yet

14.0.2 is currently uploading for release tonight
[Galaxy Note 10.1 (2014 Edition) Android Developmen] scarmona:
Thanks for the above

Another update? man.... you're good!!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
And were live unofficial 14.0.2 ;)
[Galaxy Note 10.1 (2014 Edition) Android Developmen] enotar:
Works great. Thank you

I have high power usage since 14.0. Any changes that could cause this? Maybe kernel?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
I would say check your battery under settings.. Play services and Google fit almost destroyed my battery for about 4 or 5 days in a row.. Check with wake locker app as well
[Galaxy Note 10.1 (2014 Edition) Android Developmen] enotar:
For now I have another issue, it looks something is not right with version number or last 14.0.2 from 6/22 doesn't install. I did a dirty flash 5 times and still on 6/21 auto update report that it is ready to install always. Any idea?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] artymarty:
That's strange, I've flashed it as an OTA and also manually, the version stays as build date 21st, not 22nd... Flashing the right file, checksum ok, no errors....

Is it just the version number wasn't updated?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] enotar:
Don't think so build number in setting is from 6/21 not 6/22
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
Was a quick update where kernel and build prop still kept the same but the frameworks and stuff listed in changelog only changed... Further stuff like ccache can keep frequently built and unchanged portions to save build time.. For time when's there is no official version by tema but a few changes and I spin a build just like this keeps builds coming and saves on time building 3 ROMs/uploading, etc

Edit - if there is a new date in the filename and a new build number it is new for future reference
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Genebaby:
My OTA says 14.1 is available.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] buhohitr:
Just upgraded, build is 6/23 and version 14.1. Everything is inline. Good!!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] enotar:
Anroid Keybopard FC with this new version.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
looks like there is a further merge in the keyboard for next release
[Galaxy Note 10.1 (2014 Edition) Android Developmen] chanhny:
14.1 all keyboard can not show or use. Force close. Wait for new build.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
Hey guys!

I've random keyboard fc's since install 5.1 on every of my devices, Note10 and S2/S3. Disable word prediction in setting helps a bit, but the FC's are definately a 5.1 bug!

ps. Yeah, nice indeed, it goes further again! Thanks [MENTION=4144316]joshndroid[/MENTION] and all the folks are helping debugging!

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

@ chanhny!

Try a clean install also, include system wipe!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] scarmona:
14.1.1 already live! Smooth as ever，keyboard seems to be fine as well.

You're a machine [MENTION=4144316]joshndroid[/MENTION] :D:good:
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
Tema won't be updating till next week but I might knock up a build tomorrow just to keep everyone updated with any cyanogemod and aosp changes
[Galaxy Note 10.1 (2014 Edition) Android Developmen] grimloktt:
Dude; I applause your dedication and effort to our cause. I just donated... Thnx! :good:
[Galaxy Note 10.1 (2014 Edition) Android Developmen] mosimchah:
Does this ROM have the same menu button bug (sometimes works, sometimes is not responsive, whether it's the hard key or the nav bar key) that the team eos ROM has?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
At one time yes.. However there was an issue with a commit that was removed a while back and it was fixed can someone chime in? I am at work at the moment
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
Thanks bud. Appreciate it.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] enotar:
Works fine here
[Galaxy Note 10.1 (2014 Edition) Android Developmen] SamsungGalaxySamsung:
How can i use my home button as a.. home button. I cant find the setting.

Thanks
[Galaxy Note 10.1 (2014 Edition) Android Developmen] joshndroid:
Go to settings, buttons, and scroll down u will find settings to wake device and long press etc with home button