yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 10.1 (2014 Edition) Original Android D] Wovermars:
I just wanted everyone to now that I am having trouble with my internet provider and will be changing in the coming days so I apologize if Google Drive mirrors aren't uploaded as quickly as they used to be.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Wovermars:
Google drive mirror for the latest build: http://xdaforums.com/showpost.php?p=57432940&postcount=220
[Galaxy Note 10.1 (2014 Edition) Original Android D] r4yN:
Hey, so apparently a Lollipop rom for the Exynos Note 3 has been leaked...

There is no source code of course, but maybe we can extract some driver-files or something (like for example wifi, mali-gpu, sound/dsp, etc)?

After all it's the same Exynos 5420 chipset

Here's the link to the xda thread (inc. Download link):

http://xdaforums.com/galaxy-note-3/general/lollipop-ota-note-3-n900-started-t2973773
[Galaxy Note 10.1 (2014 Edition) Original Android D] siralsmooth:
Dirty flashed the newest build. And the camera is still kicking. The only thing I can possibly think that made any difference since the beginning was that I started with Xkat rom and xluco kernel. Did a wipe and format and installed CM11. Once CM12 Was available, did the same thing. Hope this helps.
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Short feedback!

- Dirty flashed 12/18 over 12/15 and the screen distorsion in recents is gone now.

- Both camera apps are working well, but I dirty flashed all roms since 12/05(rom with the first camera-fix).

- But still impossible to select a music track as alarm tone. It switch automaticly to buzzer alarmtone!

- inbuild browser now have distorsions/artefacts (look at the screenshot)

Everything else works almost perfect, it's still amazing how quickly the tablet flies with Loll!pop!

Rayman, you are the man!

:good::good::good:

---------- Post added at 07:00 AM ---------- Previous post was at 06:59 AM ----------

[MENTION=5653992]Wovermars[/MENTION]!

Always thanks for the fast mirror!
[Galaxy Note 10.1 (2014 Edition) Original Android D] mikefnz:
OK, so followed the earlier instructions, wiped clean, installed 05/12 version, then dirty flash 18/12 version, then GApps & the camera is good. :D
[Galaxy Note 10.1 (2014 Edition) Original Android D] RaymanFX:
I already saw that thread yesterday and grabbed the new Mali blobs.

However, although their LP libGLES_mali.so and ours vastly differ (2mb vs 15mb), there's no gain sadly, the screen distortion and graphical glitches still occur, despite the fact Samsung doesn't link against libgui anymore.

This also means that unless I'm horribly wrong and nobody finds a different way around this issue, there will never be an official CM 12 build without screen distortion/glitching issues.

I'll discuss this with a few CyanogenMod people.

Also, those of you who say they did a 'full' wipe and the camera is still broken, are you sure you followed my instructions?

A data wipe is not enough, for a full SeLinux relabel (which might be required in your case), you need to wipe the INTERNAL STORAGE as well. Please check again if you really wiped *everything*.

This is my only guess since the located posted a few posts above does not contain any valuable hints to me...
[Galaxy Note 10.1 (2014 Edition) Original Android D] 7786:
I'm not sure if it's posted somewhere in this thread, but do you mind sharing what recovery/version you're personally using? I'm on TWRP 2.8.0.0 and have wiped everything (internal storage included), but still have the camera issue. Thanks!
[Galaxy Note 10.1 (2014 Edition) Original Android D] macmachine87:
I have 2.6.3.3. Did a factory reset wipe, installed the 12/05 build, wiped cache and dalvik, installed gapps, wiped cache and dalvik. Rebooted and camera worked, then I went back and dirty flashed (wiped cache and dalvik only) 12/18 build and camera worked like a charm.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Grykonmon:
With the SPen, I really love this app... https://play.google.com/store/apps/details?id=org.nattou.layerpainthd&hl=es try to use it! (and see the configuration) greetings :)
[Galaxy Note 10.1 (2014 Edition) Original Android D] xda_nikita:
Same thing here.

I use the original CWM based recovery that RaymanFX himself recommends for flashing.

When clean installing builds above 12/05/2014 the camera app brakes.

In the recovery there are only 3 options to delete stuff :

1) Factory reset

2) Delete cache

3)Advanced menu -> Dalvik delete

Anytime I install a new build I do all three of the above which gets me to a perfectly working ROM but camera isn't working.

Dirty flashing the 12/05 build first followed by whatever the latest rom is works perfect and gets the camera working everytime.

Unless "wipe internal storage" properly means that something needs doing outside of the Android recovery itself then this creeping camera issue lies elsewhere.

Just to say that this ROM is great and I am happy to donate when my cash balance allows for it.;)
[Galaxy Note 10.1 (2014 Edition) Original Android D] Pazzu510:
I hve dirty flashed everythig since the build on the 5th; still, what Rayman may be refering to is to go on mounts and storage, mount everything and delete and format everything but boot and system,. Hell, i would even recommend deleting system to make sure you got nothing on the tablet before installing. I will add that i am not responsible for any damages this causes if it might cause something. I have done it before on my s3 and it is the best way to change roms, no damage done.
[Galaxy Note 10.1 (2014 Edition) Original Android D] xda_nikita:
I am with you but that had no effect either.

What I did was to first mount all mount points under "mounts and storage " menu followed by formatting all but /boot and /sdcard1(stores my backups on the external card).

I then continued with wiping " factory reset ", cache and dalvik just in case.

Flashed latest 18/12/2014 build - camera crashes still.

There is nothing more to try in CWM-based recovery as far as I can see.

On the back of that I would say this CM12 is dirty flashing only ROM at the moment.

There is another error (guessing unrelated) when "wiping data" from the recovery.

-- Wiping data...

Formating /data

Formating /cache

Formating /sd-ext

"E: unknown volume for path [/sd-ext]"

Formating /sdcard/.android_secure...

Data wipe complete

This time I am attaching an adb log file of a clean 18/12/2014 build with camera app crashing occurrence.

Crash action is most likely logged at the end of the log file.
[Galaxy Note 10.1 (2014 Edition) Original Android D] kornelius1982:
What options do you have in "mount and storage' menu?
[Galaxy Note 10.1 (2014 Edition) Original Android D] xda_nikita:
CWM-based recovery v6.0.5.1

Mounts and storage menu :

-Mount /system

-unmount /cache

-Mount /data

-mount /storage/sdcard1

Format /boot

Format /system

Format /cache

Format /data

Format /storage/sdcard1

Format /data and /data/media (/sdcard)

+++++ Go Back+++++

As per suggested instructions I first mounted all m. Points except /boot and /storage/sdcard1 and then performed all formating leaving out the /boot and /storage/sdcard1
[Galaxy Note 10.1 (2014 Edition) Original Android D] kornelius1982:
Wiping internal storage means Format /data and /data/media (/sdcard). You just need that wipe and format /system as well as /cache to perform totally clean unstall as RaymanFX suggested
[Galaxy Note 10.1 (2014 Edition) Original Android D] xda_nikita:
Did everything that RaymanFX and "format /data and /data/media (/sdcard)" is meant to do but like I wrote a few posts earlier the 18/12/2014 doesn't work by itself if you were like me and still want to have your camera ability working.

To have the camera you would need a two part install with 05/12/2014 image intact and then whatever latest build is on top(dirty flashed).

Judging by other posters it isn't just an issue for me though.

I can only assume something is lost in builds after 05/12/2014.

Perhaps the first page of the thread can mention something about the dirty flashing situation ...
[Galaxy Note 10.1 (2014 Edition) Original Android D] kornelius1982:
To be honest it's kinda weird situation on CM12, dirty flashing has better results in terms of stability(I mean on galaxy s4 LTE-A also). Now I'm on 12/15 with dirty flashing over previous ones and have no issues on camera or other stuff. Had tried 12/18 with full wipe without success and back to 12/15.
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Jepp! +1

I've tried it also with a really clean install of 12/18 and camera does not working!

Restore 12/15 backup and dirty flashed 12/18 and Camera is still working like after the fix with 12/05.

Maybe we should consider any changes from 12/07 exactly again, maybe it's due google.services or some framework changes?
[Galaxy Note 10.1 (2014 Edition) Original Android D] paddycr:
I am wondering whether this could be gapps related? There has been problems with different gapps packages causing the camera to crash on the Nexus 6 (see http://xdaforums.com/showthread.php?p=57632208). I have been using slim gapps with this ROM and I have the same camera f/c issue with a clean flash of the 12/18 build.
[Galaxy Note 10.1 (2014 Edition) Original Android D] xda_nikita:
Does installing a none-Google camera app on a clean flashed 12/18 ROM provide definitive answer as to wheather its a Google apps issue?

Its a straightforward test ...
[Galaxy Note 10.1 (2014 Edition) Original Android D] lewmur:
Calender

I clean flashed 12\05 and dirty flashed 12/19 and the camera works fine. The only bug I have is with the calender. The I've tried the pre-loaded one, installed one from "widgets" and downloaded the Google app from the Play Store. Each one gives "Unfortunately the calender app has stopped" error.
[Galaxy Note 10.1 (2014 Edition) Original Android D] rondera:
Does anybody use a snote alternative daily with this rom? :)
[Galaxy Note 10.1 (2014 Edition) Original Android D] aelaan:
I use lecture notes - have the CM SPen add-on installed, like a charm
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Hi lewmur!

There are no calender issues in this rom on my side. Use it every day! Google calender works great! Have you tried to wipe the cache and dalvik cache incl. fix permissions?

If this not help, try a really clean install of 12/05(incl. system and data media wipe), test cam and calender and dirty flash the latest 12/18 release on top.

I would also recommend to use the gapps package that RaymanFX has provided at the first page.

There are other gapps packages for lollipop, like slim-gapps or micro-gapps, but not really tested with this rom.
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
I use google notes with the sketch and handraw! Works great incl. sync.!
[Galaxy Note 10.1 (2014 Edition) Original Android D] Thomi7:
Amazing work!

Thank you for the early porting of CM12 for the Galaxy Note 10.1 (2014 Edition). I'm currently downloading the latest version (where all the known bugs should be fixed) and I will try to find any bugs (if some of them are still here in this ROM).

Thanks to the devs !
[Galaxy Note 10.1 (2014 Edition) Original Android D] lewmur:
Well this is weird. Restored 12/04 again and checked the calendar. Works fine. Flashed 12/18 wiping only dalvik. Again, calendar no longer works. Tried "Fix Permissions" using TWRP 2.6 and I LOSE MOST OF MY APPPS!!!! Have to start all over again.

I guess I'll have to upgrade to TWRP 2.8 when I get the time.
[Galaxy Note 10.1 (2014 Edition) Original Android D] GaardenZwerch:
I had the calendar crash too, I just found out...

Went to settings, apps, choose force stop, clear data and cache, and it worked again...
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
I'm on 2.6.3.3, but if I say "dirty flash" I mean wipe nothing!!!

Only flash the latest release and the gapps package and reboot!
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
issue installing

Every time that I try to flash the latest version of the rom on TWRP 2.7.1.1 the procces fails and it says that it can not install on incompatible data. I did a wipe before flashing and it just does not work. Any Ideas?
[Galaxy Note 10.1 (2014 Edition) Original Android D] kornelius1982:
Update recovery to the latest one.
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
I already tried installing the latest recovery, but for some reason only 2.7.1.1 will properly install. When I try to install the latest or older versions all I get are a bunch of errors.
[Galaxy Note 10.1 (2014 Edition) Original Android D] aelaan:
What was your original version 4.4.2 or 4.3?

---------- Post added at 11:31 PM ---------- Previous post was at 11:26 PM ----------

What I did when this happens is flash my original firmware on it using Odin, keep the USB cable attached during first reboot. Setup minimal, then Odin TWRP 2.6.3.3 on it. Make sure you go into recovery mode immediately and install the ROM of choice.
[Galaxy Note 10.1 (2014 Edition) Original Android D] lewmur:
Didn't work for me. I went so far as to download 12/18 and 12/5 again as the latest backup I have is 12/4. Flashed 12/5 over 12/4 with no wipe. Calendar works. Flash 12/18 with no wipe, Calendar stops. Tried force stop and clear data and cache. No help. Flash 12/15 and Calendar works again.
[Galaxy Note 10.1 (2014 Edition) Original Android D] kornelius1982:
I`m using Philz advanced recovery (this one) and have no problems at all.

Flash original firmware via odin before install Philz recovery.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Wovermars:
Tbh I wouldn't mind an official version that has minor screen distortion. It's not a massive matter for me anyway because of what this rom already has to offer. So for me it doesn't necessarily need to be fixed because it's not a deal breaker at all but if it does get fixed, that's cool.

Also a benchmark from the latest version of Antutu which now outscored my Snapdragon 800 phone.
[Galaxy Note 10.1 (2014 Edition) Original Android D] jeanmarce:
Thanks

Thanks for the fast release
[Galaxy Note 10.1 (2014 Edition) Original Android D] toertchn:
I try'd the calculator on the last realease 18/12 with german locale and it can't be used.

12 + 1.2 = 132

there seems to be a problem with , and . digit separators.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Vitorbnc:
Not detecting touch and S pen

I'd like to report a bug that's happening to me. When I am with the S pen over the screen, the tablet won't accept any other finger input but the S pen, it will just respond if you press the S pen on the screen. I would be very thankful if you could fix this :fingers-crossed:
[Galaxy Note 10.1 (2014 Edition) Original Android D] RaymanFX:
That's actually a feature, not a bug.

It's called palm rejection and is used so you can use the S-Pen to draw/write while having your palm on the screen (otherwise it might be uncomfortable to use the S-Pen for a longer period of time.

Also, what's the issue with putting away the pen for a second and using the device normally again?

The current behavior is the only one that makes sense to me.
[Galaxy Note 10.1 (2014 Edition) Original Android D] mikefnz:
Same here.

Gave up on TWRP and installed Philz via Flashify.

So far, so good.

---------- Post added at 07:53 PM ---------- Previous post was at 07:50 PM ----------

Same here.

Gave up on TWRP and installed Philz via Flashify.

So far, so good.
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Hi toertchn!

You need to swipe up into the right green field and change hex/bin into dec!

Calculator works!

But there is another bug in calculator, like you can see on the screenshot.

Some space in the green area are used with double characters(first row/con, tan).

Maybe it has something to do with the distorsion bug?
[Galaxy Note 10.1 (2014 Edition) Original Android D] xcom923:
Is there a firmware that needs to be installed before flashing this? I'm coming from 4.3 ( skipped KK just because I had a setup that I liked and the jump wasn't worth it that close to 5.0)
[Galaxy Note 10.1 (2014 Edition) Original Android D] kornelius1982:
You should install official KK to update bootloader before install CM12
[Galaxy Note 10.1 (2014 Edition) Original Android D] xda_nikita:
I tried this on a "dirty flashed" and clean flashed installs ofRaymanFX build 18/12 with no success. Calender Force closes.

Used Philz recovery v6.48... with flashify from other posters suggestions but it makes no difference in terms of Calender or Camera.
[Galaxy Note 10.1 (2014 Edition) Original Android D] kornelius1982:
Just install 12/05 then run camera and calendar, then reboot to recovery and dirty flash 12/18.
[Galaxy Note 10.1 (2014 Edition) Original Android D] mbargerhuff:
Anyone having issues with amazon appstore not installing?
[Galaxy Note 10.1 (2014 Edition) Original Android D] toertchn:
I'm on dec mode. But after the source checkout of calculator2 i see its still unfinished. It don't handly android.intent.action.LOCALE_CHANGED so it crash after a change. And many things more. So please ignore this ... app related problem, not device based.
[Galaxy Note 10.1 (2014 Edition) Original Android D] bogderpirat:
just a brief question; this build doesn't include any CM features yet, right? just aosp adapted for the note 10.1 2014?
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
It's pure CM12! No additional features for now!
[Galaxy Note 10.1 (2014 Edition) Original Android D] lewmur:
No calendar with 12/18

Upgraded TWRP to 2.8 but still no calendar with 12/18. Clean install of 12/4 and both camera and calendar work. Dirty flash 12/18 and no calendar. Dirty flash 12/15 over 12/18 and calendar works. Tried clearing data and cache for the calendar apps while in 12/18 but that didn't work either.
[Galaxy Note 10.1 (2014 Edition) Original Android D] wasa67:
Thanks for the ROM Update

I actualy like that the S-Pen has a cursor, it allows me to track its movement, however, I dislike the arrow pointer image. I attempted to switch the arrow pointer located in the framework-res.apk with a circle (attached), however it kept boot looping when i rebooted.

The image for the pointer arrow is found under /system/framework/framework-res.apk/res/drawable-xhdpi-v4

Just my 2 cents.
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Have you tried to delete and re-install the calender.apk completely?
[Galaxy Note 10.1 (2014 Edition) Original Android D] lewmur:
Deleted the /system/apps/calendar folder and then install the Google calender app from the Play Store and that works.
[Galaxy Note 10.1 (2014 Edition) Original Android D] 7786:
Heres mine if youd like to give a try. Make sure you change the permissions before you copy it over the old one. This replaces the arrow pointer with the original spen circle cursor. For the 12/18 build only.
[Galaxy Note 10.1 (2014 Edition) Original Android D] paddycr:
Thanks very much for this. For some reason I found the arrow extremely distracting when I was writing with the spen. This is much better ?
[Galaxy Note 10.1 (2014 Edition) Original Android D] Nameless One:
I've been using a USB flash drive today with an OTG adapter, and have noted that with this ROM the system refers to the device as an sdcard and provides absolutely nothing in the storage part of settings or in the notification area to do things like safely unmount the device. file managers can see it and transfer files but it cannot be unmounted and as such the system complains that the "sdcard" was not unmounted properly. This doesn't affect any real external sdcard in use.
[Galaxy Note 10.1 (2014 Edition) Original Android D] dc959:
Has anyone else had any issues with the battery and it showing a lower percentage than it is then when you reboot into recovery and back into the rom there's a lot more battery left on the device? For example just before my device said it had 7% remaining but after rebooting into recovery then back into the device I had 49% which is also what recovery said I had. I am running the latest build but have dirty flashed since the 5th of december one
[Galaxy Note 10.1 (2014 Edition) Original Android D] kornelius1982:
I have such issue. Especially when playing heavy games (like Dead Trigger 2) battery drains very fast and after a restart it bumps up to much higher value.
[Galaxy Note 10.1 (2014 Edition) Original Android D] JSspezial:
I had the same problem. The only solution I found was to send it back to Samsung to have it fixed. After 2 weeks I got it back and everything was fine.
[Galaxy Note 10.1 (2014 Edition) Original Android D] kornelius1982:
There was no issues on stock KK rom. Pretty sure it is LP fault and hope will be fixed soon.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Stevethegreat:
Hey, can you make a flashable zip which would replace the arrow with nothing at all? I use my spen without any visible feedback (I prefer it that way) and I don't use a mouse to care about not having a pointer.

Thanks.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Vitorbnc:
Thanks for the explanation, I didn't know it, thought it was a bug ;)
[Galaxy Note 10.1 (2014 Edition) Original Android D] 7786:
Sorry its not a flashable zip, but heres the framework that should be without a cursor at all. Youll have to manually copy it over for now.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Stevethegreat:
That's no problem. Thank you very much. I'd try it shortly.

My idea is to be able to do that in TouchWiz and CM11 roms as well, I think what you do is depackage the apk and replace the cursor.png file with one of your own make (in my case a blank file, in other cases sth else) and then repackage. In fact I tried doing that in stock rom but it didn't work (no pointer.png?); but anyhow, I'm correct in my assumption that you do as I described above , right?
[Galaxy Note 10.1 (2014 Edition) Original Android D] 7786:
Correct, i just modified the arrow pointer png in gimp, replacing the arrow image with the original spen image. So for this one i just erased the pointer and kept the entire image transparent.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Kamikazy69:
I have this problem too, and i'm running KitKat build! I didnt have it with stock rom... So it must be something else..:(
[Galaxy Note 10.1 (2014 Edition) Original Android D] Wovermars:
I've had this issue with my old Galaxy s2 (now my mum's) running Cyanogenmod 11 currently.
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
The battery issues in heavy load situations have definately nothing to do with the rom.

I have this battery break-ins in Kitkat and also in Lollipo when playing Real Racing 3 or Asphalt 8 without power cord plugged-in.

I think the battery is in some devices are not good enough to deliver the needed power for a longer time as 5 Minutes.

The only way for me was to play with a longer usb cable(1,5m/5ft)!

Return it to Samsung with knox counter 0x3 is for me also not a good idea, but to change the internal battery into a new one maybe can help!
[Galaxy Note 10.1 (2014 Edition) Original Android D] aelaan:
I have noticed that even with simple games like Best Fiends and the charger plugged in cause overheating. At one time I had to turn off the tablet because the screen locked up. I think it is more related to how the CPU is not allowed to throttle and the 5.0.2 version might have better management. It is just something to be aware of for the tablet will shut itself down if overheating.