yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 10.1 (2014 Edition) Original Android D] diabl0w:
getting an error that the recovery is too large for target when trying to flash the CM recovery

the block is 8.3 mb and recovery is 8.7
[Galaxy Note 10.1 (2014 Edition) Original Android D] Orion116:
Try flashing with TWRP
[Galaxy Note 10.1 (2014 Edition) Original Android D] diabl0w:
thats what i did, sorry should have said that

EDIT: nvm i misunderstood, so okay yeah i just ended up flashing the CM ROM with TWRP and all is fine so far.
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
Yes, I clean flashed it with twrp, I also flashed open Gapps. Everything seems to be working, however it is using the narrow/small notification panel which is really annoying on a tablet.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Orion116:
Yeah, maybe we can get the larger panel added back to the tree.
[Galaxy Note 10.1 (2014 Edition) Original Android D] SamsungGalaxySamsung:
Hi all,

Is it possible to convert this file tot f2fs?

Could you reach out to me how i could do this?

Thanks in advance and thanks to the developers for all the hard work.
[Galaxy Note 10.1 (2014 Edition) Original Android D] diabl0w:
bug: if i lock the screen manually and then hit the home button, screen comes right on. If i let the screen timeout itself, the screen takes a long time to light up after pressing the home button

bug: screencast does not work with samsung tv
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
This ROM does not support f2fs.

---------- Post added at 03:59 PM ---------- Previous post was at 03:50 PM ----------

This ROM has the recents panel distortion, that was fixed in brokenos so could it be fixed here as well? I have not encountered the spen bug yet. The SD card is fully functional.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Orion116:
f2fs was why early builds were 6.5mb.

Just change the lock screen time out.

As for recents, I really don't remember how that was fixed, hahahaha.
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
In your Google plus post where you announced the fix, you said that you fixed it by a rebase to EOS's device tree. Link: https://plus.google.com/114933367381225581769/posts/LVQmhJMmjZT
[Galaxy Note 10.1 (2014 Edition) Original Android D] Orion116:
We will see if it can be added again.
[Galaxy Note 10.1 (2014 Edition) Original Android D] diabl0w:
That doesnt fix the fact that it takes 7-10 seconds for the screen to come on after pressing the home button to wake the device
[Galaxy Note 10.1 (2014 Edition) Original Android D] Orion116:
I don't know screen has always turn on.
[Galaxy Note 10.1 (2014 Edition) Original Android D] diabl0w:
Hmmm thats strange because i completely wiped the tablet before flashing and i have zero apps installed
[Galaxy Note 10.1 (2014 Edition) Original Android D] Stogie87:
Hello, i have to ask you two things:

1. ls there a way to use floating windows with this Rom? I installed Omniswitch with TWRP, but if i try to start a app in Floating Mod, the app only starting in it's normal form. With Temasek's Rom it works without any issue.

2. Has anybody else problems with the sound? If i listen to music on p600 with this rom, the sound crackles very oftently, but with the stock rom everything works fine. I had this problem already with temaseks cm 12.1 build.
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
CM doesn't come with floating windows so there are only two ways to get them:

1. Build the ROM yourself and include the commits for floating windows.

2. Use Xposed or some other mod, but don't report bugs if you decide to use Xposed, and don't start a whole discussion about which Xposed modules to use, or something like that since this is a ROM thread and not an Xposed discussion thread.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Orion116:
No, floating windows here until cm13 with multi window.

I listen to google music and local music on BrokenOS and have no issue with sound quality. What music app are you using?
[Galaxy Note 10.1 (2014 Edition) Original Android D] mising:
So far, so good! No issues yet, thank you!
[Galaxy Note 10.1 (2014 Edition) Original Android D] Stogie87:
Ok, thanks for your answers. I have the soundproblem with every musicapp. With Spotify, YouTube and even i realize it sometimes by pressing the keyboard-buttons. At first i was sure, that my speakers are defect, but as i went back to stock Rom, the sound was fine again. I also tried another sound-driver and installed viper4android on cm 12.1, but no change. I deleted completely my intern sd card and did a new clean installation of cm12.1, but even after this the problem remains. I only can explain myself this issue, that it depends on the cyanogenmod driver.
[Galaxy Note 10.1 (2014 Edition) Original Android D] maturb:
First of all I want to thank you all lt03wifi Maintainers for bringing us this official CM builds.

I've updated today with the latest nightly and it's better than on 13s nightly (were some performance glitches etc.).

I'm also happy to see that I don't have problems with handwritting notes distortion in Evernote - I had this problem on TeamEOS.

Good job guys, thank you and keep on rocking!
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
I just encountered the s-pen bug on the latest nightly. I was browsing XDA with the s-pen and all of the sudden my tablet froze and rebooted. Here are the logs.

//Edit

I looked at the changelog for the latest nightly and I noticed that there were a few device specific changes, so maybe those changes have something to do with the s-pen bug. Here are the changes:

device/samsung/lt03wifi

SLSI variant : use CyanogenMod SLSI (android_device_samsung_lt03wifi) http://review.cyanogenmod.org/124023

BoardConfig.mk : Add common flag NATIVE_SEC_NV12TILED (android_device_samsung_lt03wifi) http://review.cyanogenmod.org/124025

Galloc.h : update gralloc for slsi-cm (android_device_samsung_lt03wifi) http://review.cyanogenmod.org/124026

WFDService : disabled flag (android_device_samsung_lt03wifi) http://review.cyanogenmod.org/124027

Update cm.dependencies : for slsi-cm repos (android_device_samsung_lt03wifi) http://review.cyanogenmod.org/124029

//update

I just encountered the issue again. On the latest nightly the bug is occurring almost as often as on brokenOS. I'm going to revert to the previous nightly and I'll let you guys know if I encounter the bug again.

//update

I restored my backup of the previous nightly (cm-12.1-20151213-NIGHTLY-lt03wifi.zip), I have been using the s-pen for 44 minutes straight and I have not encountered the s-pen bug, so the changes in the latest nightly probably caused the s-pen bug in this ROM. Orion116, does brokenOS have those changes or something similar, could they have caused the bug?

//update

I have been using the previous nightly (12-13) for 3 hours and 10 minutes so far today, most of which I have been using the s-pen and I have not encountered the s-pen bug. I think it's safe to say that one of the changes in the newest nightly might be the cause of the s-pen bug, if so it could be fixed in the temasek builds and in brokenOS.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Stogie87:
Hello and sorry that i annoying you again, but is it possible that my soundproblem depends on the new Lollipop 5.1.1 Bootloader i had to install for the new stock rom? I read in some threads that people had in the past soundproblems as they upgraded from 4.3 KitKat Firmware to 4.4.2 and after downgrade to 4.3 or an similar custom Rom they had no sound. I think our Cyanogenmod 12.1 build was created for the p600 Kitkat 4.4.2 bootloader.

Has anyone here installed cyanogenmod 12.1 after he upgraded to Lollipop 5.1.1 stock Rom with the new bootloader and can give me a feedback, if he has soundproblems? You maybe have to listen a full song to check it, because the rustle of the sound isn't constantly.

Thanks for your replies...

//update. I now formated everything again, did a new installation of stock rom with bootloader update (no sound issues), formated everything and did a new clean installation of the latest cyanogenmod nightly -> No change, problem remains. It can´t be, that i am the only one with this issue...
[Galaxy Note 10.1 (2014 Edition) Original Android D] Tiemichael:
Same / similar problem here - when using S-Pen my device reboots ...

Also, although it should not be mentioned here, Xposed is not working at all

... going back to Temasek
[Galaxy Note 10.1 (2014 Edition) Original Android D] Stogie87:
Hello again,

i don't know if i am the only one again with this problem, but i can not install the cyanogenmod nightly recovery. I get the message, that the size of the image is larger than the space of the device or something like this.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Orion116:
Use TWRP and flash nightlies manually.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Stogie87:
Yes i do, but my intention was to change from twrp to cyanogenmod recovery. So i have to stay on twrp.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Orion116:
Why downgrade?
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
I just experienced the s-pen bug on the 12-13 build...
[Galaxy Note 10.1 (2014 Edition) Original Android D] Stogie87:
I think they are aware of the s-pen bug. My tablet reboots many times if i use the s-pen, but i had this problem also on temasek 18.4 build and later.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Orion116:
I am serious I will use the s-pen for 2hr straight or more and never had a reboot except for using up all the ram on my tablet?
[Galaxy Note 10.1 (2014 Edition) Original Android D] Tiemichael:
just wondering if there is any kind of change-log available?
[Galaxy Note 10.1 (2014 Edition) Original Android D] Stogie87:
I use the s-pen everyday for my studys in universaty for more than 2 hours and sometimes i have the reboot after 1 hour, sometimes after 10 minutes. On average 2-3 reboots in 2 hours. If it would be possible to send you a logfile about my user behavior i will do, but i don't know how.

//update: i had in the last 30 min. 2 reboots after 5 minutes using the s-pen. Impossible to work with the s-pen.

(No xposed framework installed!)
[Galaxy Note 10.1 (2014 Edition) Original Android D] Orion116:
I do the same thing for college. Like I said once I a blue moon does it reboot on my and usually it is because all the ram is used up
[Galaxy Note 10.1 (2014 Edition) Original Android D] Stogie87:
I envy you. I had to recover my Samsung stock backup today, because i wasn't able to write longer than 10 minutes without a reboot. I don't know what makes my system different from yours. Is it possible, that if i format data with twrp, that some specific datas won't deletet through this process? Is there a another way to format every data on the tablet and make a complete new installation of all datas including bootloader and download mode etc?
[Galaxy Note 10.1 (2014 Edition) Original Android D] jmark13:
If I'm going to flash a new nightly over the previous one, is it ok to dirty flash? Do I need to flash the open gapps I originally used? So far everything is working great for me. I do not use the S-pen.
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
It's in the op.
[Galaxy Note 10.1 (2014 Edition) Original Android D] jaypea500:
Has anyone encountered any sluggishness with the recent nightlies? My current is from the 14th Everything on my p600 is very slow. Especially Web browsing and email. Also, when I wake it up, it takes between 5-10 seconds for the lock screen to appear. And charging is slow - where it used to take 3 hours or so to charge fully, now charging overnight only gets it to 60-75%. The only thing that is not sluggish is power consumption. You?
[Galaxy Note 10.1 (2014 Edition) Original Android D] Aletheia:
I've noticed (on earlier CM builds) that this can happen if you enable LiveDisplay, even if it's not active. Might not be it in your case but it's worth mentioning.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Stogie87:
Ok friends, i am pretty sure now, that my sound problem and the s-pen reboot issue is related to the new bootloader which i had to install with Touchwiz 5.1.1. It would seem that CM 12.1 is only 100% compatible with the old bootloader from TW 4.4.2 and not with the new one. Is there a way to get the old bootloader back to my device? Otherwise i have to wait and pray, that the Cyanogenmod-Team will fix it in an upcoming update...

//update: forget my last statement! I made it to install the old bootloader with touchwiz 4.4.2 with odin and then i did a clean installation of cyanogenmod 12.1 and i was happy that everything startet very well (no red kernel warning at startup anymore), but the sound problem remains. So i give it up with cyanogenmod now....
[Galaxy Note 10.1 (2014 Edition) Original Android D] Tiemichael:
I never installed the new bootloader, and still the device froze and rebooted when using s-pen ...
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
I was also on the 4.4.2 bootloader when I experienced the s-pen bug. It also occurred for me on the 5.1.1 bootloader. Now I'm on stock lagwiz?. Orion116, which bootloader are you on?
[Galaxy Note 10.1 (2014 Edition) Original Android D] diabl0w:
maybe the devs such as orion are using local builds instead of the ones we are using that are downloaded from the CM website? ... that would make sense if the CM builds arent compiling properly just like how f2fs was creating 6.15 mb builds yet devs had local builds that were working fine

---------- Post added at 05:18 AM ---------- Previous post was at 05:14 AM ----------

i had same problem and had all sort of active display live display auto brightness all disabled. i think its a powersave deep sleep issue. i was getting 7-10 second delays between pressing button to wake amd then actual screen wake. flashing valex kernel reduced to about half that but still 3-5 second delay

sorry for double post.

either way guys, this is early official CM for our device. of course there will be bugs. im jjust grateful for these devs bringing cm to our device and it will only get better. of course there are gonna be some obstacles at first
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
The s-pen issue is occurring on multiple ROMs: brokenOS (maintained by Orion116), temasek (maintained by joshndroid), this one, and probably all of the other aosp ROM's. Also, the builds are compiled by cm's build servers so the maintainers do not necessarily try out the builds first. BrokenOS is compiled by Orion116, so we are using the same build that he uses, and it's the same story with the temasek ROM.
[Galaxy Note 10.1 (2014 Edition) Original Android D] diabl0w:
the devs probably are using the same build we are, but i dont know how you know for sure whther or not they are. have you asked them already? ...just because the CM servers compile doesnt mean a local build cannot be made.

orion reported that spen bug is not occuring on his device, so what yoir saying about it occuring over multiple roms is irrelevant.
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
He said that it's not occurring in his device on brokenOS. I'm just putting two and two together.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Tiemichael:
Alltough not a heavy s-pen user I do not have any problems with s-pen on Temasek ROM.

Maybe the problems are related to some other not fully compatible apps.
[Galaxy Note 10.1 (2014 Edition) Original Android D] diabl0w:
I thought you just said that spen reboot was an issue in all aosp roms, including brokenOS.
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
It is an issue on all aosp ROM's. The interesting thing is that some people, such as Orion116 are not experiencing the issue at all.

---------- Post added at 09:43 AM ---------- Previous post was at 09:41 AM ----------

I have experienced the issue on temasek, it occurs with every app, including multiple launchers.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Stogie87:
I agree with mosimchah. The S-Pen Issue is not relatet to an app or launcher. I had it also one or two times on the lockscreen, if i tryed to enter my pin code.
[Galaxy Note 10.1 (2014 Edition) Original Android D] toertchn:
I got this little problem. Every time i open something at full screen the tablet crashes.

Steps to reproduce:

- open google play

- click some app

- show image of app in full screen

- press back button

Same problem also with some other apps. Thx for your help.

I use:

cm-12.1-20151218-NIGHTLY-lt03wifi.zip

open_gapps-arm-5.1-nano-20151219.zip
[Galaxy Note 10.1 (2014 Edition) Original Android D] Bracher:
Hi, my experience so far: LT03WiFi with 4.4.2 bootloader, since yet with the unofficial Temasek 12.1. Tried clean install.

First thing trwp 2.8.7.0 did not work - that is my screen was frozen, no chance to do anything in Recovery. I had to go in download modus, start from the scratch and use trwp 2.8.6.0 - this worked, so no damage but lost time...

Next I tried xposed same problem the newest v79-sdk22-arm did not work, when I tried to install XposedInstaller, the screen went black and than I had bootloops. Ok back to v75 this worked but there is still one problem when I activate a Modul - for eyamle Greenifay or AppsOpsXposed, the screen goes black an I have to force the tablet to reboot (it does not reboot at least not in 5 minutes and after that I lost my nerve) but after the forced reboot the apps/modules work fine.

No Spen problem so far and I work a lot with Spen (LectureNotes for example). No sound problem, no video problem - it's only this xposed issue

Best regards
[Galaxy Note 10.1 (2014 Edition) Original Android D] Orion116:
Sorry I am on 4.4.2 bootloader.
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
So was I when I was on brokenOS, joshndroid's temasek builds, and cm, and I experienced the s-pen bug, so I guess it's not related to the bootloader version. This bug is very weird.
[Galaxy Note 10.1 (2014 Edition) Original Android D] diabl0w:
Latest nightly 12/20,Complete factory reset before installing, no apps, no xposed, same behavior after 2 hours

turning volume all the way down has no effect on volume along with the "crackling" audio previously reported

AudioService: stream was not muted by this client

AudioService: could not get client death handler for stream: 5

Also home button will not wake device at all for single click. Jamming it a few times will eventually wake the display > 10 seconds later

Relevant log next post
[Galaxy Note 10.1 (2014 Edition) Original Android D] adxamg:
Just wanted to say "thank you to the devs" for official nightlies!

But recent posts make me believe it's better to stay at temasek 18.4 atm, right?
[Galaxy Note 10.1 (2014 Edition) Original Android D] Stogie87:
Yes, stay at temasek. I think it will takes a while until this rom will get an snapshot release. I realized yesterday for the first time, that the most nightly changes are for all cyanogenmod supported devices and not specific for our device. That means there is no one at the moment who canstantly working on our cyanogenmod version to fix all bugs.

Maybe this is the reason why bug reports in this threat are normally "not accepted".
[Galaxy Note 10.1 (2014 Edition) Original Android D] Aletheia:
Stable enough on my end. Granted I've probably not used the spen for more then 20 minutes straight through. You'll lose some customization coming from temasek but personally I feel like it's an upgrade.

Full disclosure, I think I dirty flashed from cm 11 up untill now so no wonder...
[Galaxy Note 10.1 (2014 Edition) Original Android D] Stogie87:
Since the last nightly update xposed framework seems to working fine. :D
[Galaxy Note 10.1 (2014 Edition) Original Android D] murmlgrmpf:
I had issues with getting connected to my wifi. Is it possible that the wifi is configured for US and only works on low channel numbers in Europe?
[Galaxy Note 10.1 (2014 Edition) Original Android D] Shawn5162:
You guys want cm 13, we want cm 13...but we need your help. I am sure you are now wondering what we need from you...Right? Well, we need none other than some MORAL SUPPORT! :)

PS: On a more serious note, cm-13.0 nighties are only a matter of days away (we hope), so stay tuned.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Tiemichael:
Yes!!! Please make CM13 happen!

Thank you for spending your holidays working on CM13!
[Galaxy Note 10.1 (2014 Edition) Original Android D] StackOverflow13:
Deleted
[Galaxy Note 10.1 (2014 Edition) Original Android D] DirkStorck:
Yes would be fantastic. Using cm13 on my S5 and it has never been so smooooth ??
[Galaxy Note 10.1 (2014 Edition) Original Android D] qkdingus:
cant wait :highfive:
[Galaxy Note 10.1 (2014 Edition) Original Android D] StackOverflow13:
+1
[Galaxy Note 10.1 (2014 Edition) Original Android D] stevvie:
cm13 yes PLEASE
[Galaxy Note 10.1 (2014 Edition) Original Android D] theamazingaustin:
I'm having the same issue... Wiping all again and giving 1/5 a go.
[Galaxy Note 10.1 (2014 Edition) Original Android D] theamazingaustin:
Issue resolved by wiping and reflashing latest nightly.
[Galaxy Note 10.1 (2014 Edition) Original Android D] toertchn:
Can you tell me which bootloader version and recovery do you use? I had the same issue with 5.1.2016 nightly and the old 4.4 bootloader.

I use twrp 2.8.7.0
[Galaxy Note 10.1 (2014 Edition) Original Android D] theamazingaustin:
Recovery is TWRP 2.8.5.0 - when I updated to the latest TWRP things got wonky so dropped back to 2.8.5.0 - didn't have time to figure out what the issue was.

Bootloader.... honestly I'm not sure... noob question here, how do I check that for you? :eek:

I'll look into updating mine.

----------------

On a side note, I've also noticed that if I don't lock my tablet into landscape mode, it crashes and reboots when i do pretty much anything. Rotation locked into landscape and I haven't had one crash / reboot.

Log if anyone is interested. With SysLog by Tortel - never shared logs before, so apologies if I botched it up. :P

Google Drive link: https://goo.gl/8ZljJx
[Galaxy Note 10.1 (2014 Edition) Original Android D] scarmona:
Pleaaaaaase make CM13 happen!!!
[Galaxy Note 10.1 (2014 Edition) Original Android D] Stogie87:
Hello dear developers,

Is it possible to get a short status update how the work is going on?

Thanks for your hard work.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Stogie87:
Somehow i have the feeling, that CM-Development for p600 is dying...
[Galaxy Note 10.1 (2014 Edition) Original Android D] ruud:
+1
[Galaxy Note 10.1 (2014 Edition) Original Android D] Tiemichael:
Luckily we had some very good and active developments in the past (e.g. Joshndroid/Temasek) ...
[Galaxy Note 10.1 (2014 Edition) Original Android D] Stogie87:
You're right. Temasek Rom was great, except of the fact that miracast didn't work on my device. I hope one day there will be a stable release of this official cm 12.1 nightlies and they will fix the sound-,spen and miracast-bug and make the brightnessbar wider.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Orion116:
We are still working on it. Shawn and me both are busy with college and joshndroid is busy at work. We are trying to still get a lt03wifi tree booting. We can get a build for of lt033g booting on our device with a few tweaks.
[Galaxy Note 10.1 (2014 Edition) Original Android D] StackOverflow13:
Really appreciate the work you are all doing. I know it's it's hobby/spare time so super thankfull for all your hardwork
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
I flashed the unofficial It033g cm13 build by ShevT, and it booted without any tweaks whatsoever.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Orion116:
I am talking about reverted ril and cellular stuff.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Tiemichael:
Thank you for the update and thank you to you and the team for your effort!

This was the motivation I and maybe others needed ....