yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 10.1 (2014 Edition) Original Android D] rezad1393:
that is actually what I meant. the debugging.

it isn't even debugging, it's making it work.

when you said "build it yourself" I thought it was just compiling and packaging it , so it is not just "build it yourself".

I have done the "build it yourself" thing on other gadgets like my router (openwrt firmware creation) but they are straightforward and scripted.

this was a just rant. hope it didn't insult you. but please don't say build it yourself so easily when you yourself know it is not like that.

but thanks for the answer.

btw do you know that this image can be actually installed on sm-p601?
[Galaxy Note 10.1 (2014 Edition) Original Android D] rezad1393:
never mind

this ROM is also like shevt ROM. on both I get black screens many times and on this ROM the described method of escaping that doesn't work.
[Galaxy Note 10.1 (2014 Edition) Original Android D] joshndroid:
New build is up hopefully much better than prior release
[Galaxy Note 10.1 (2014 Edition) Original Android D] joshndroid:
New build is up... new kernel, new various stuff not currently within temasek rom
[Galaxy Note 10.1 (2014 Edition) Original Android D] goldensun7:
Great, rom has been working great except for the camera. It keeps crashing after taking a few pictures and system has to be rebooted. We're you able to fix it in this new build? Any idea how I can fix it?

Thanks again!
[Galaxy Note 10.1 (2014 Edition) Original Android D] joshndroid:
not fixed yet...

still working on it... made so many changes/reverts/whatever its hard to keep up. Sought some ideas from like devices and from a few other devs in our section... none of us have got the camera working yet. Its now getting further than it ever has but still not there yet unfortunately
[Galaxy Note 10.1 (2014 Edition) Original Android D] lloyddefrance:
Access to Share

Please add me to share
[Galaxy Note 10.1 (2014 Edition) Original Android D] joshndroid:
mate i dont recall seeing your PM? did you send one with the information?
[Galaxy Note 10.1 (2014 Edition) Original Android D] lloyddefrance:
Sorry. I'll check. Have a good one.
[Galaxy Note 10.1 (2014 Edition) Original Android D] joshndroid:
Fresh build up for u guys on Google shares and basketbuild.. I will start getting more regular and include it in my build script =)
[Galaxy Note 10.1 (2014 Edition) Original Android D] zikozoko:
please ,, what if I install wifi"600" cm13 on a cellular"601" device

is it just I`ll lose cellular capabilites ? or what?

thanks in advance
[Galaxy Note 10.1 (2014 Edition) Original Android D] joshndroid:
New build was uploaded
[Galaxy Note 10.1 (2014 Edition) Original Android D] AndyYan:
How do I build this from source? I have experience with building for official and unofficial devices. I added the 3 repos into my roomservice.xml and synced successfully, but when initializing, build/envsetup.sh threw the following error:

ls: cannot access /home/***/cm-13.0-build/device/samsung/lt03wifi/patches/*.patch: No such file or directory

... and "breakfast lt03wifi" threw:

including vendor/cm/vendorsetup.sh
build/core/product_config.mk:239: *** _nic.PRODUCTS.[[device/samsung/lt03wifi/cm.mk]]: "hardware/samsung_slsi-cm/exynos5/exynos5.mk" does not exist. Stop.
Device lt03wifi not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Found repository: android_device_samsung_lt03wifi
Default revision: cm-13.0
Checking branch info
Default revision cm-13.0 not found in android_device_samsung_lt03wifi. Bailing.
Branches found:
cm-12.0
cm-12.1
Use the ROOMSERVICE_BRANCHES environment variable to specify a list of fallback branches.
build/core/product_config.mk:239: *** _nic.PRODUCTS.[[device/samsung/lt03wifi/cm.mk]]: "hardware/samsung_slsi-cm/exynos5/exynos5.mk" does not exist. Stop.

** Don't have a product spec for: 'cm_lt03wifi'
** Do you have the right repo manifest?

It seems I need some patch prior to building, but it isn't offered in the source. What can I do, or should I follow totally different steps?

EDIT: Solved - thanks for help from OP!
[Galaxy Note 10.1 (2014 Edition) Original Android D] AndyYan:
Something I found annoying: even in clean flashed state, the UI occasionally but constantly produces stutters. I've hooked the tablet up to logcat and GPU profiling, and the former did not return any useful result. However, the latter provides some info:

The green part in the longer bars are abnormally long. Every time such long bars appear, the UI will pause momentarily. Switching on GPU compositing and else from Developer Options and build.prop didn't help.

EDIT: CM12.1 doesn't have such stutters, but other problems (e.g. sleep of death) prevent it from being a daily driver.

This problem looks trivial, but it affects gaming experience quite heavily. Hopefully a fix can be cranked out...

Sent from Google Nexus 6P @ CM13
[Galaxy Note 10.1 (2014 Edition) Original Android D] ZakooZ:
I have the exact same error. Can someone help with this one please?
[Galaxy Note 10.1 (2014 Edition) Original Android D] AndyYan:
Quoting the original PMs I received from OP:

(look inside the repos for cm.dependencies)

and this:

These should be able to get you going.

Sent from Google Nexus 6P @ CM13
[Galaxy Note 10.1 (2014 Edition) Original Android D] ZakooZ:
Thanks, I was able to get the build going quite quickly because of that, especially the mc_linux.h part

Weird that it was reverted in the device tree if it's needed to compile :eek:
[Galaxy Note 10.1 (2014 Edition) Original Android D] Mohammed alabri:
The camera is not working
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
This is a known bug, on a side note, in general if you want a bug to be fixed you need to provide a logcat.
[Galaxy Note 10.1 (2014 Edition) Original Android D] amitabh15:
Curious: Is there a reason why SELinux is set to Permissive and not enforcing on this rom? I'm curious since that's not the usual behavior on official CM.
[Galaxy Note 10.1 (2014 Edition) Original Android D] amitabh15:
Is there a way to disable capacitive touch keys after enabling on screen nav bar?

It automatically disables the capacitive touch keys in CM12.1 when enabling on screen nav bar. Which works great, because I accidentally keep hitting the back capacitive touch button when I use spen or hold it in portrait mode.
[Galaxy Note 10.1 (2014 Edition) Original Android D] AndyYan:
The easy way: Xposed + Xposed Additions.

The hard way: modifying kl files in /system/usr/keylayout. Requires reboot every time a modification is made.

Sent from Google Nexus 6P @ CM13
[Galaxy Note 10.1 (2014 Edition) Original Android D] amitabh15:
Xposed is too much of a ram hog. How could I do it through the kl files?
[Galaxy Note 10.1 (2014 Edition) Original Android D] AndyYan:
I currently own a P607T instead of a P600, but the touchscreen should be the same, so should be the procedure.

Go to /system/usr/keylayout/sec-touchscreen.kl. Open it with any root explorer capable of text editing. You should see something like:

key 139 MENU VIRTUAL
key 158 BACK VIRTUAL

Add #s in front of keys you don't want, for example:

#key 139 MENU VIRTUAL
#key 158 BACK VIRTUAL

Or you could map the keys to other functions if you want. If you want the menu key to open Recent Apps, here goes:

key 139 APP_SWITCH VIRTUAL
key 158 BACK VIRTUAL

Save and reboot.

I don't know which .kl file corresponds to HOME behaviour - multiple .kl files hold that and you'll have to experiment to see which one is in use. I personally leave the keys on so as to keep a clean look, so I won't bother looking into that.

Side note: people usually report Xposed hogs battery instead of RAM, if anything. It never seems to hog either for me - I get 2.0GB free RAM on my P607T on boot, and usually 1.6GB on my sold P600.
[Galaxy Note 10.1 (2014 Edition) Original Android D] amitabh15:
Perfect!! It worked great. I don't want to disable the home button anyways. Cince its not a capacitive touch button and I have a tempered glass screen so I don't accidentally press it anyways. Plus its useful for waking up the screen when it's laying flat on the table. The other 2 are disabled now and that's exactly what I was looking for. Thanks a million! :)
[Galaxy Note 10.1 (2014 Edition) Original Android D] toanau:
I pm you last week. Could you add me to list to share your ROM
[Galaxy Note 10.1 (2014 Edition) Original Android D] amitabh15:
Me too! I Pm'ed last week as well. I can download the the most recent build from basketbuild as it shows 0kb download.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Filiprino:
Will this ROM become officially supported?
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
Maybe when the camera is fixed, that's what joshndroid said anyway.
[Galaxy Note 10.1 (2014 Edition) Original Android D] ZakooZ:
This ROM is probably never going official because it doesn't work properly with official Cyanogenmod exynos5420 code (it uses an old version of the code), and CM team refuses to merge the old code. Same thing with pretty much every exynos5420 device on cm13
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
Not exactly, all the current ROMs for our device are currently running the old/proper code and we still have certain issues. Using the proper code helped with some lags and things like that, if you are using any recent Temasek build from joshndroid, then you are on the current code, the same goes with a ROM from myself or from Orion116. The cm team refused to merge the code because they didn't think that it was the proper solution, so the 5420 maintainers all merged it unofficially. The camera issue is completely separate. Another issue is that we are essentially taking shots in the dark with the other issues because we can't get detailed logs for mobicore (this is causing the battery drain), and for surfaceflinger (this is causing the distortions upon rotating the device, and is also causing the s-pen bug).
[Galaxy Note 10.1 (2014 Edition) Original Android D] phoneturf:
My menu key does not work to display the menu/settings on the homescreen or in any app, but it wants to open Google Now or some google thing I don't want.. I must be doing something wrong. I tried using All-In-One Gestures to set the key to menu, but then it does not do anything. Any ideas what is wrong?
[Galaxy Note 10.1 (2014 Edition) Original Android D] stevvie:
File Name: cm-13.0-20160716-UNOFFICIAL-lt03wifi.zip

File Size: 0 bytes

File MD5: d41d8cd98f00b204e9800998ecf8427e

Developer: Joshndroid

file on basketbuild has 0 size
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
Lol, your profile pic happens to go really well with your post
[Galaxy Note 10.1 (2014 Edition) Original Android D] bumbum.droid:
Has somebody a recent donwload of the ROM that they could mirror somewhere? [MENTION=4144316]joshndroid[/MENTION] seems to be busy atm
[Galaxy Note 10.1 (2014 Edition) Original Android D] Stogie87:
Use this build. Everything works, except of ScreenMirroring. Sometimes a little bit laggy, but it is the best we have atm.
[Galaxy Note 10.1 (2014 Edition) Original Android D] joshndroid:
new build incoming.... just testing and uploading
[Galaxy Note 10.1 (2014 Edition) Original Android D] joshndroid:
Alright fresh build uploading now.

NOTE - moving forward device using its correct name of n1awifi not lt03wifi so dont be confused/scared the rest of the naming convention will change with it
[Galaxy Note 10.1 (2014 Edition) Original Android D] joshndroid:
Righteo - new build

https://drive.google.com/open?id=0B_lVu2fo1C1IdHRxc19GZlpNRm8

camera is not working right now due to some commits that are being worked on

rotation should be fine (it is for me)

MTP is moved to samsung MTP so should be better and more stable

as i said camera is being worked on again.. i will build a fresh one once this is fixed
[Galaxy Note 10.1 (2014 Edition) Original Android D] joshndroid:
Camera working build is now up!

https://drive.google.com/file/d/0B_lVu2fo1C1IZTBuTEQyRl9kUlU/view?usp=sharing

Credit - [MENTION=4810273]ZakooZ[/MENTION] - for finding a related camera value in the stock binaries [MENTION=5795145]javelinanddart[/MENTION] - for developing a unified manner in executing the value across exynos5420 based devices
[Galaxy Note 10.1 (2014 Edition) Original Android D] wadken1:
Just installed this build. All is good so far. Great to have the camera back and working from within Onenote.

Many Thanks
[Galaxy Note 10.1 (2014 Edition) Original Android D] Stogie87:
Thanks for new build, but ir blaster is still not working. It works on ZakooZ build, so maybe you can also merge this fix?
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
Are you using the tree in the exynos 5420 repo? It has all the fixes, including the one for ir. Unless if ir is broken again.
[Galaxy Note 10.1 (2014 Edition) Original Android D] joshndroid:
IR must be broken
[Galaxy Note 10.1 (2014 Edition) Original Android D] hipocrazy:
Great Build! Thanks!
[Galaxy Note 10.1 (2014 Edition) Original Android D] deb75:
Hello,

I am on my way to purchase the samsung galaxy note 10.1, 2014 edition. I need it mainly for hand writing notes purpose.

I am sorry, I did not read the while thread before posting this question, I just want to know if these unofficial builds are stable enough to work with and if the s-pen also works well with it (sensitivity, pressure levels, ...) ? I heard that the s-pen was not playing well with lollipop.

Also, is there any significant differences between builds of this thread and those of Temasek's ?

Thanks for your advice.

Regards.
[Galaxy Note 10.1 (2014 Edition) Original Android D] hipocrazy:
Everything is nice and stable, a small group of dedicated developers keep it so. I dont find a vast difference between any of the builds but I find zakooz cm13 ROM is the best for me and he is currently heading a release of cm14. Great device, great community.
[Galaxy Note 10.1 (2014 Edition) Original Android D] jskov:
Rebuild image from revisions instead of HEAD?

Is the repo manifest (with revisions) available anywhere, so the build can be reproduced?

From the CM documentation I got the impression that it would be included in the system image (/system/build/manifest IIRC), but I do not see that file.

I ask because I tried building an image myself this weekend (based on cm-13 heads).

It did build after some tinkering related to the new naming.

But failed running with a missing EGConfig.

So I clearly did not get everything right - using manifest entries as documented elsewhere in this forum.

I would love to start by reproducing a working build, like this, your latest.

Thanks,

Jesper
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
Here's the local manifest: https://github.com/exynos5420/manifests/blob/master/n1awifi_CM_manifest.xml

Put it in .repo/local manifests

And then sync and you should be good to go
[Galaxy Note 10.1 (2014 Edition) Original Android D] jskov:
This is indeed the manifest I used.

But it will build from the current state of the trees (as of the time of synchronization).

And that did not work for me (at runtime) this weekend.

What I am after, is the "repo manifest -r" output, which identifies the specific states of those trees used to build the given image.

According to wiki.cyanogenmod.org/w/Doc:_Using_manifests it should be baked into the image, but I don't see it there (the path mentioned is /system/etc/manifest.xml).

Without this information, it is hard to reproduce a build without having to figure out each tree's commit state at the time of the build.

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

Duh! OK, so it was not after all. Dumb mistake on my part.

Still, my comments about recreating other builds stand.

Is that just not done? Or is the information captured somewhere else in the system image these days?

Cheers,

Jesper
[Galaxy Note 10.1 (2014 Edition) Original Android D] javelinanddart:
Uhh, pretty sure recreating builds only applies to CM Nightlies and Snapshots, we don't support that, sorry.
[Galaxy Note 10.1 (2014 Edition) Original Android D] vinayburman:
Could you please tell me where to download zakooz CM13 ROM, thanks.
[Galaxy Note 10.1 (2014 Edition) Original Android D] hipocrazy:
http://d-h.st/bXKj
[Galaxy Note 10.1 (2014 Edition) Original Android D] Revan335:
[MENTION=4144316]joshndroid[/MENTION]

Thanks for the Build!

Flash from temaseks its not running, correct?

Clean Install its running, right?
[Galaxy Note 10.1 (2014 Edition) Original Android D] deb75:
[/COLOR]

Hi,

I have just installed this ROM, all went well, but at boot, the setup wizard is constantly crashing after wifi setup and comes back to the beginning,

which makes the tablet unusable.

I just installed the ROM without anything else (no Gapps).

What should I do ?

EDIT1: I will try with zakooz'sbuild (on dev-host) that I was finally able to download.

EDIT2 : with zakooz build also the setting wizard crashes just after the wifi connexion and brings me back to the language selection.

I do not know what to do to fix this ??? it seems nobody had this issue before me. Here are the steps I followed :

- wipe everything except external sd card,

- wipe data,

- factory reset,

- install ROM

- install superuser.zip

- wipe cache /dalvik

- reboot

EDIT3 : I installed several gapps package, right after rom, but still get at one point the setup wizard failure.

So, I wiped everything, reflashed the ROM, mounted /system and deleted /system/priv-apps/*SetupWizard

and when rebooting to CM, I was led directly to the main window.
[Galaxy Note 10.1 (2014 Edition) Original Android D] deb75:
Hello,

I installed latest ROM cm-13.0-20160909-UNOFFICIAL-n1awifi.zip, but I do not want to install any google apps.

The setup wizard keeps on crashing so that I cannot enter the tablet.

Installing some gapps (pico, nano, mini) helped going further into the setup wizard, but it still crashes at one step and indefinitely brings me back to the langage choice.

Removing "/system/priv-apps/CyanogenSetupWizard" (from recovery directly after installing) works but then it seems that several things do not work, among which the notification bar (I have no notification) and also the welcome button is partially working.

Is there a way to bypass the cyanogen setup wizard without breaking everything ?

Thanks for your help.

Regards
[Galaxy Note 10.1 (2014 Edition) Original Android D] ammarr:
Here's what I did. Delete that folder, boot tablet, set up wifi and set lock screen to 'None'. Reflash the rom so the original files are restored. This should fix everything.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Revan335:
Is the Name from latest Build correct?

cm-13.0-20160909-UNOFFICIAL-n1awifi.zip
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
Yes, lt03 is the name of the qcom variants, for some weird reason RaymanFX used that name instead of the actual name of the p600 which is n1awifi, the exynos 5420 development team decided to go back to the proper name which is why the name on builds has changed.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Revan335:
Thanks!

A Full Wipe is recommended from temaseks build to the new builds from joshndroid, right?
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
Yes, always do a full wipe when changing ROMs, wipe the system, cache, data, and dalvik cache. For updates just wipe the system, cache, and dalvik, unless if you want to report bugs, in which case you need to do a full wipe.
[Galaxy Note 10.1 (2014 Edition) Original Android D] deb75:
Hi,

Thanks for this workaround.

Meanwhile, I did almost the same thing, I connected the tablet to my laptop and, through the adb bridge, moved away the

/system/priv-apps/CyanogenSetupWizard directory, then I rebooted and could access the tablet main window, I copied back the previous directory to its original place still through adb bridge, then rebooted : the SetupWizard showed up but it ended on the main window with everything working well so far up to now.

So : :) :) nice tablet with nice ROM without any gapps :) :)
[Galaxy Note 10.1 (2014 Edition) Original Android D] bschatzow:
I am a little confused with your directions. You say to download standard TWRP Vers 2.8.6.0 then you says to download your linked version F2FS and then you have the directions to run the TWRP. No where do you say to run your custom F2FS version.

Thanks in advance.

Bill
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
F2fs causes issues for us on marshmallow, just don't use it
[Galaxy Note 10.1 (2014 Edition) Original Android D] bschatzow:
Thanks. I used the F2FS with Marshmallow the 9/9 build and it seems to be working. A couple of freezes, but could not duplicate. I'll update I'd I get useful information.
[Galaxy Note 10.1 (2014 Edition) Original Android D] rayik:
I prefer not to use F2FS. I've used F2FSin the past and did not see any difference (good or bad)

But if you put another ROM on the system you have to remember to change the file system. Formatting will just clear the F2FS partition and not change the file system type. Twrp will install non-compatible roms into F2FS which will result in boot loops. It's just a nuisance that is easily fixable. But since I did not experience any difference, my preference is not to use F2FS.
[Galaxy Note 10.1 (2014 Edition) Original Android D] bschatzow:
Thanks. I'll switch back on my next Rom update. Seems silly to have this if not much faster and not compatible to many RIMs.
[Galaxy Note 10.1 (2014 Edition) Original Android D] blazzer12:
Camera

I don't see anything under the "Not Working" section but the FAQ says camera needs to be figured out.

So is the camera working with the latest build, or does it have any issues?
[Galaxy Note 10.1 (2014 Edition) Original Android D] bschatzow:
The camera works fine for me. Have problems with sounds being garbled and battery doesn't last as long as it should.
[Galaxy Note 10.1 (2014 Edition) Original Android D] blazzer12:
>The camera works fine for me.

Great!

>sounds being garbled

Like when playing a song or notification sounds?
[Galaxy Note 10.1 (2014 Edition) Original Android D] bschatzow:
YouTube video for example. Video is fine if I cast it.
[Galaxy Note 10.1 (2014 Edition) Original Android D] blazzer12:
Ah, ok.

---------- Post added at 03:09 AM ---------- Previous post was at 03:07 AM ----------

Cannot get past "Setup Wizard", with or without GAPPS.

Unfortunately, Setup Wizard had stopped.

:crying:
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
We need to get SELinux to a stable enforcing mode first, no ETA.
[Galaxy Note 10.1 (2014 Edition) Original Android D] chris_gee:
Hey, happily using your build now for a couple of days. Thanks a lot!

I have a few issues related to s-pen that keep appearing though:

1. when I am using the s-pen, the touch screen buttons don't get switched off, which means that e.g. the option key is permanently pressed while writing at the top.

2. I get frequent reboots when using the s-pen. This is quite annoying

I was installing from the most recent stock... I read the bootloader installed from there may cause issues. Related?

Apart from that my setup is very basic: TWRP 3.0.2, your rom from 9.9.2016, no GAPPS

Cheers,

C.
[Galaxy Note 10.1 (2014 Edition) Original Android D] hipocrazy:
I had terrible reboots while drawing with the spen on this Rom, switched to Zakooz CM13 and problem went away. Hope it helps.
[Galaxy Note 10.1 (2014 Edition) Original Android D] chris_gee:
Well, as far as I understand joshndroid's latest build includes the same kernel as Zakooz does (3.4.112-Deathly-0.3), if that's the reason for the reboots (kernel panic?)... right?

In fact I find after following the procedure here I have seen no more pen crashes and sound (klicking) was fixed too. So it's infact bootloader related?

Now I just need to find a way to have the touch buttons disabled while using the pen and I am in heaven... (happy already :) )
[Galaxy Note 10.1 (2014 Edition) Original Android D] hipocrazy:
No. Different kernel. Yes, bootloader related from what I've read.

I've never had a crash,freeze or reboot while drawing on Zakooz ROM. I don't know the definitive reason why.