yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 10.1 (2014 Edition) Original Android D] Bracher:
S-Pen Bug

Is there any news on the S-Pen Bug?!

Unfortunately I got it finally as well, went back to Temasek, but it occured with this ROM as well. As the Pen (with Lecture Notes) was the main reason to buy this tablet I was/and I am still pissed off strictly speaking. What did Samsung? I have no problem with Note 3 but on lt03wifi it is a problem no matter which Bootloader you're on - is the only solution to go back to TW or has somebody found a solution??? The tablet is for me more or less worthless as long as the Pen does not work and TW is a real problem - bloated with software which tries to spy on you....
[Galaxy Note 10.1 (2014 Edition) Original Android D] ruud:
i have a P600 but flashed a 5.1.1 Rom for a P601 and everything is working even my s pen
[Galaxy Note 10.1 (2014 Edition) Original Android D] GCSortes:
Can I install SM-P600 (wifi) ROM in my SM-P601 (3g) ???

Ps.: I just use WiFi, I don't put Sim Card :o
[Galaxy Note 10.1 (2014 Edition) Original Android D] Bracher:
Sorry for disturbing you: nothing new on the S-Pen? It crashes now after 5 minutes...
[Galaxy Note 10.1 (2014 Edition) Original Android D] x000111:
Random Reboots

I just got this ROM ruining with pico Gapps and it looks great and runs smooth. The only major problem I'm finding is that the device will randomly reboot without warning. Other times it will crash when a certain app is loaded. Two apps that consistently cause a reboot are Adobe Acrobat Reader and Quill. Has anyone found a solution for this or even experienced it?
[Galaxy Note 10.1 (2014 Edition) Original Android D] Jakvett:
I experienced random reboots pretty frequently at various instances: initial setup menu, sitting idle at the launcher home screen, etc. I only used the ROM for maybe a half hour on a couple different builds over the past 3 weeks, because the reboots were too disruptive and unpredictable.

I'm sorry to report that I don't have specifics as far as logs, build dates, or specific usage cases that caused reboots, but I tried both clean installs and fully formatted internal SDs with pico gapps to no avail. I also restored all my apps with TiBu, so I don't want to rule out that it may have been an app causing the misbehavior.

I'll probably try the latest build in the near future to see if I can get more definitive results.
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
Nobody can help you, or fix the issue, if you won't provide logs. This is a really good app for that: https://play.google.com/store/apps/details?id=com.tortel.syslog

You can also use adb.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Jakvett:
That's why I stated that although I didn't take logs previously, I intend to try again with logs to help with troubleshooting. I just wanted to share now that I had also experienced the random reboots. I understand that just saying "it doesn't work" is useless for the devs :)
[Galaxy Note 10.1 (2014 Edition) Original Android D] TruThug407:
Has anyone confirmed screen cast option working with smart tv...?
[Galaxy Note 10.1 (2014 Edition) Original Android D] Stogie87:
I tested it before 20 minutes because i was also interested. It's hardly to say but i don't realize any improvement since the first Nightly was released. Things only become more worse. Screen Mirroring still doesn't work, still sound crackeling on my device, display sometimes doesn't react if i press the homebutton and the display is off.

I also got a black screen during first configuration process after a complete clean fresh installation. I think it is useless to wait for a stable release of this rom. The much better solution is CM 13 by joshndroid.
[Galaxy Note 10.1 (2014 Edition) Original Android D] TruThug407:
How is DAT cm13 working for u battery an all else is good besides camera?
[Galaxy Note 10.1 (2014 Edition) Original Android D] Stogie87:
It's ok but i don't use it as a daily driver because of the spen bug and miracast shows only a black screen. I need both. Joshndroid still works on the batterylifetime. The only stable solution with very good batterylifetime is the b6 stock rom by enotar in batterysaving mode.

I recommend to install Nova Launcher on stock rom because it is similar to trebuchet Launcher from Cyanogenmod but you have much more possibilities to customize your dashboard and you can change your app icons.
[Galaxy Note 10.1 (2014 Edition) Original Android D] TruThug407:
Yea I was using enotar's b6 but he said he was using da cm13 by joshandroid now so he probably ain't gna be doin any more work on it plus I like to customize theme system wide an I can't customize da stock ROMs theme system wide until I get a better computer an I don't think anyone else is doin any work on da stock ROM theme wise or customizing....
[Galaxy Note 10.1 (2014 Edition) Original Android D] Stogie87:
Yes i also like it to customize and for this CM is great, but i use nova launcher even for CM because you can customize some things you even can not do with trebuchet launcher. And for the Brightnessbar i use the AOSP Theme by supergrobi94. Enotar is only testing CM 13 and he will finish his work on beta6 if he find time. We still need a kernel with permissive rights and i am sure he won't end his work until he has a rom with such a kernel.

-> be patient :)
[Galaxy Note 10.1 (2014 Edition) Original Android D] TruThug407:
Yea u rite, I'm patient tho dis is wat we do just wanna further my exp in development myself too so I can help out wit some of dis stuff I pretty much stay on my note 10.1 trying to get sbreen94 to update da hyperdrive ROM to 5.1.1 DAT would be nice....
[Galaxy Note 10.1 (2014 Edition) Original Android D] joshndroid:
Tbh I have neglected cm12.1 since getting it to nightly status. Cm13.0 was already a thing and that has been all I cared about.

Probably the last Samsung device I'll have once this dies and my note 3.. My daily devices are nexus and Samsung really just doesn't care about the dev community.
[Galaxy Note 10.1 (2014 Edition) Original Android D] TruThug407:
Yeah u rite I just don't wanna give up on dis note tab it's still a pretty decent tab but as long as we have devs like u it will live on I'm just gna stick wit your cm13 bcuz u stay on top of it an it really does run a lot better than dis nightly 12.1, don't give up on it we appreciate your hard work....
[Galaxy Note 10.1 (2014 Edition) Original Android D] gavilan2010:
+1
[Galaxy Note 10.1 (2014 Edition) Original Android D] Stevethegreat:
While I can see the point of (it) not being enjoyable to support a device with so little documentation IMO it's also the kind of devices that actually *need* the most support.

Most of us either lack the knowledge or the time to begin developing for such devices (I can scarcely find the time support my patchy Linux solution), so -it seems to me that- it makes the work of yours or Orion's or Valera's all the more important...
[Galaxy Note 10.1 (2014 Edition) Original Android D] joshndroid:
I see where your coming from, but I have also witnessed the mass exodus of good quality devs over to devices with better support, devs far far better than I. Why drop 800$+ on a device when the 'openess' of android isn't there by the manufacturer. You either have to 'try' do everything yourself and come up with hacky solutions that end in thread posts consisting of the same issue over and over. Manufacturers understand sales, and sales alone, they only support something as long as they get something out of it, dollars. I'm not saying don't buy them, but I'm just pointing out I am not necessarily willing to fork out my hard earned cash on a device where even the manufacturer couldn't give 2 poops about supporting us. At the end of the day, I guarantee you, it would not be so hard for a manufacturer to release good quality and consistent source code, they have to generate it anyway in house to get the device to work, slap it in a tree, hell you could slap it in a tree before you release it as a package to the public.

Again im not ditching the device, TBH the only action the device is seeing at the moment is being flashed multiple times a day, I work on it 5 times as much as I do any other device. I'm just highlighting once it dies I wont be rushing out to buy another.
[Galaxy Note 10.1 (2014 Edition) Original Android D] joshndroid:
well here is a beta version of cm13.0 stock rom.

stable enough to use s a daily.

make sure u have updated gapps package for 6.0

https://s.basketbuild.com/devs/Joshndroid/CM13.0/lt03wifi
[Galaxy Note 10.1 (2014 Edition) Original Android D] Stevethegreat:
Of course it's easy to them. But they don't, partly because they don't want to. Android is a semi-closed system. Apart from AOSP most of everything (and everyone) else is proprietary. I'm sure companies like Samsung only release their half-arsed code only to be compliant with GPL and avoid legal battles, *nothing else*. Of course and they don't care about the community or supporting their devices for long. How else are you going to buy their next device?

All I'm saying is that for better or worse some of the best hardware is manufactured by companies that literally drive away the community. The community (IMO rightly) stops development, but then we're all left with one solution. Google products. Which as you may well know are not for everyone. Android increasingly becomes like iOS (one real player) and it saddens me, because it used to be that much more vibrant (in choice and support) a few years back. If everybody moves to a Nexus product, I may as well move to iOS and jailbreak it...

I do think that those that develop for non Google-based product -still- do the most important job because they retain the hardware choice that android used to have semi-alive... Then again it's a hurdle for them, and they should be compensated by the community (in whatever ways possible).

Anyway, enough with the off-topic. Keep up with the good work and thanks :good:
[Galaxy Note 10.1 (2014 Edition) Original Android D] TruThug407:
Thanks bruh I'm gna flash it rite now thanks for keepin it alive....
[Galaxy Note 10.1 (2014 Edition) Original Android D] sylvainXDA:
Flashed it and all went fine so far! Gonna play around a bit now!

Gesendet von meinem 2014818 mit Tapatalk
[Galaxy Note 10.1 (2014 Edition) Original Android D] goldman60:
The beta seems to run pretty well for the most part, especially considering its a first build. Great work!

Issues I've run into so far:

Major: Tablet runs hot (Bottom right corner gets uncomfortably warm, I'm still trying to figure out what's causing this as it might just be my setup)

Camera doesn't work

Screencasting does not work (casting to Chromecast 2 and Nexus Player)

Minor: Bluetooth identifies the tablet as an SM-P601 by default

Edit: Just remembered I dirty flashed over CM12.1, so I'll have to see if the running hot issue is resolved by resetting the tablet

Edit^2: Many issues fixed in newer build below!
[Galaxy Note 10.1 (2014 Edition) Original Android D] joshndroid:
Base is the same as my temasek (temasek tree gets a few more additions/optimizations) so issues pretty much going to be the same.

Will have a new build up, have not worked on anything tree related tho been away last couple days
[Galaxy Note 10.1 (2014 Edition) Original Android D] joshndroid:
You can find a new cm-13.0 stock build here - (device tree changes, some merges from shevt also)

https://s.basketbuild.com/devs/Joshndroid/CM13.0/lt03wifi
[Galaxy Note 10.1 (2014 Edition) Original Android D] goldman60:
This build seems to have fixed the heating in the lower right corner (I'm assuming the processor was pegged). :laugh:
[Galaxy Note 10.1 (2014 Edition) Original Android D] thirdcoastraised:
So, just throwing this out there, but if you guys need testers for CM13, I'm happy to help. Awesome work on this version to date guys, can't wait to see what's next!??
[Galaxy Note 10.1 (2014 Edition) Original Android D] joshndroid:
Fresh build incoming for you guys =]

Some good work been done last few days...... snappy, no ril stuff, battery life better.... surely you guys will see if =]
[Galaxy Note 10.1 (2014 Edition) Original Android D] Stogie87:
You mean for lollipop or your MM build? LoL:p
[Galaxy Note 10.1 (2014 Edition) Original Android D] joshndroid:
New cm13.0 build - https://s.basketbuild.com/devs/Joshndroid/CM13.0/lt03wifi
[Galaxy Note 10.1 (2014 Edition) Original Android D] ruud:
i need gapps arm 64.?????? for this rom
[Galaxy Note 10.1 (2014 Edition) Original Android D] joshndroid:
No still use arm gapps only
[Galaxy Note 10.1 (2014 Edition) Original Android D] kleanth1s:
This rom can be flashed on my rooted 5.1.1, as you instructed, am I right? I mean I do not need to go to a rooted kit kat rom.
[Galaxy Note 10.1 (2014 Edition) Original Android D] goldman60:
There is no reason you'd need to go to KitKat, ROMs entirely replace /system
[Galaxy Note 10.1 (2014 Edition) Original Android D] kleanth1s:
So, after flashing the rom only, everything is ok. If I flash gaps, as soon as I enter my account, screen goes black. I am not using the arm 64 gaps, as you stated. Please advice
[Galaxy Note 10.1 (2014 Edition) Original Android D] joshndroid:
Try using a different sized package.. Like micro, nano or pico
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
There's a fix for the s-pen bug, and the audio crackling bug. Here's the fix.
[Galaxy Note 10.1 (2014 Edition) Original Android D] Stogie87:
Is it actually possible to replace official cm 12.1 support with official cm 13 support, now? Because i think the latest release could be stable enough for this.

I remember the words by orion116:

"I can tell you that the p600 will get official CM13 if joshndroid, Shawn and myself can figure out why we get a black screen after rebooting from recovery."

;)
[Galaxy Note 10.1 (2014 Edition) Original Android D] joshndroid:
Can't really submit to cm when camera is broken.. Kinda fundamental to support. It will get there eventually been extremely busy when I have time I'll have to run some logs see what is happening..
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
It was already fixed by RaymanFX and a few other developers. http://review.cyanogenmod.org/#/c/119445/
[Galaxy Note 10.1 (2014 Edition) Original Android D] Stogie87:
Ahh, i understand. I think it's not really necessary to get official support as long as we get updates by temasek. Thanks for the information.
[Galaxy Note 10.1 (2014 Edition) Original Android D] joshndroid:
That's a supporting commit but not a fix. That was merged a few days prior to build. There is something else needed for us.
[Galaxy Note 10.1 (2014 Edition) Original Android D] joshndroid:
New build up on basketbuild, if interested I can start a Google share for these builds if u want?
[Galaxy Note 10.1 (2014 Edition) Original Android D] ddyxda:
Have a Note 10.1 Stuck in a boot loop...

Can someone tell me if it's possible to recover my 10.1 that is stuck in a boot loop? How would I go about fixing it?

Thanks,

Doug
[Galaxy Note 10.1 (2014 Edition) Original Android D] Orion116:
Boot into recovery????
[Galaxy Note 10.1 (2014 Edition) Original Android D] thirdcoastraised:
Orion, you crack me up bro, great answer though!????
[Galaxy Note 10.1 (2014 Edition) Original Android D] ddyxda:
Right, I should have elaborated on the situation. I'm unable to boot into recovery... When I try it just flashes and then cycles through the boot menu again. Currently it's just sitting on the Samsung animation.

Is that the description of a bricked device? Or is there a way to get a new recovery installed using Odin or some other means? I'm assuming the recovery got uninstalled somehow.

Thanks for any help,

Doug
[MTCB Software Development] Brendo:
author MVG-V70

(translated from Russian| ORIGINAL)

New xposed-module xposed-mtc-manager (MTC Manager.apk recorder contains the basic functions of our family)

Capabilities:

1. The module functionality moved xposed-mcu, not allowing the radio to go to sleep while scrolling starter.

When you receive a signal to shut down the unit produces a delay of 5 seconds, if at this moment reappears food, nothing happens in the absence of power cassette player goes to sleep.

Because of the implementation of inclusion in our MCU, for the period of voltage loss goes off the screen.

2. The module is implemented whitelist applications that do not allow the system to cover the necessary services and applications in the care to sleep and when you press the "Acceleration" in the curtain. Thus, the module eliminates the need for mtc-wakeup-service.

File exceptions must be on the outside of the map in the catalog mtc-manager. Filename whitelist.ini

The file should list the names of the application packages whitelist.

example

add to the white list and MTC-Volume MapCamDroid:

/external_sd/mtc-manager/whitelist.ini

com.mvgv70.mtcvolume

info.mapcam.droid

The names of packages and services can be taken from the application manifest file or with a program like Package Viewer.

3. Alternative screensaver with a list of exceptions that runs in any (even abnormal appendix). Staff alternative mechanism is activated screensaver.

Probably it will not work on all firmware versions.

Settings in settings.ini file in the directory mtc-manager on the outside of the map.

settings.ini

# Including an alternate screen saver, if you specify false mechanism will work full-time:

screenClock = true

# Time off the screen when not set will be used the value of the full-time settings:

screenTimeout = 60

# The name of the software package screensaver

screenPackage = com.microntek.screenclock

# Name aktiviti screensaver

screenClass = MainActivity

# If the name of the package and Activiti not specified, will use the standard screensaver

The list of exceptions is in the file ss_exceptions.ini - should list the names of the packages, for example:

ss_exceptions.ini

com.microntek.music

ru.yandex.yandexmaps

Also, the screensaver does not start when talking on the phone, rear view camera, navigation, and turn off the radio.

If instead of a beautiful clock screensaver MTCSreenClock.apk called conventional digital clock on a black background, it is necessary to make sure that the application is installed MTCScreenClock.

If the application is installed, you can try to set the parameters and screenPackage screenClass in settings.ini

All apps by MVG-V70 (EXTERNAL LINK)
[MTCB Software Development] ttoton:
Could someone please help me with configuring the mentioned whitelist?

I have not found any *whitelist* file in my device.

Do I have to create such file?

If so, how and where?

I also found something on moving some MTC folders to ext_SDcard?? why should something like this be necessary?

I have not moved anything, all cathalogues are as installed in the Booroondook's ROM.

My purpose is to STOP system from closing the apps when the device goes to sleep (like when I turn off the car for 5 minutes, etc.). Every time all the apps that were running are closed and I have to start them again.

I don't want ANY app to close.

Thanks in advance!

[EDIT]:

I found some more info on a Russian forum and:

I manually created a folder "mtc-manager" on External_SD location, in which I created a whitelist.ini

file including:

pl.neptis.yanosik.mobi.android

com.maxmpz.audioplayer

com.petrows.mtcservice

I also created a start_services.ini file with the same content, as this was to speed up launching these apps during boot.

Neither of it made any difference.

The apps are still being closed during device goint to sleep and I noticed no diferrence whatsoever.

Any ideas why this doesn't work?
[LG V10 Q&A, Help & Troubleshooting] YrrchSebor:
Has anyone used stock recovery? I couldn't get past the Android on it's side.... Usually I can press some button combination to get to the recovery menu options, but nothing seemed to work on this device. Anyone know? Possibly a simple question, so sorry bout that!
[Thinkpad Tablet General] Sinista2015:
Hi

i tried installing xposed and somehow the device won't boot up anymore

The device shows the LENOVO BIOS but the animation never starts.

I used " [Unofficial]Xposed For Zenfone Lollipop Rom by arun483 "

Can't access the device at all, is there anyway i could just start twrp and restore my nandroid ?

Otherwise i'm gonna have to give this a go (back to kitkat)

Thx!
[Thinkpad Tablet General] ionioni:
answered here
[Thinkpad Tablet General] Sinista2015:
Fixed !

Whoa thx for that !

But i have to admit i guess i over reacted, when i woke up i turned the pc on and after connecting the tab the battery screen turned on and i heard the usb on the pc connect! I guess the usb connection was acting up or something after multiple connect/disconnects ?

Anyway, after the usb did connect i tried using the Intel FB_RecoveryLauncher and it actually worked! I then fully recovered from my previous nandroid backup using twrp.

Even better, i went back to the xposed page here on xda and downloaded the latest x86 build (sdk21) + the alpha 4 installer, installed and flashed the zip, now everything is working 100% OK.

Again, thanks so much for your quick response and solution.

And to anyone in the same situation, please, use this information to your benefit!

BTW: You rock!
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] channing173:
Has anyone found out how to get double tap to wake to work on the turbo? Is it in development?
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] meskes:
CM doesn’t have that feature, though Resurrection does.
[Galaxy Note5 Q&A, Help & Troubleshooting] 1980aksoy:
Anyway to create app folders in the app drawer of the Galaxy*note 5
[XDA Assist] mjkuhne:
I have a original rom kyocera hydro c6530n rooted and used lucky patcher and messed things up royally from there after installing or trying to rather modded play store never worked all kinds of google errors gapp, service, no network connection and than no play at all applied all (as far is google concerned) fixes. never back to normal need less to say i uninstalled reinstalled all kinds of play stores reset rooted device to later find out I dont have any clue what I am doing obviously. I have reset to factory and hard reset and now I am stuck in bootlooper because I thought that re flashing with flashify would be the answer and yes I may have to get a new phone because wow but I flashed a boot image from the system uid I think I figured they wont give me an option if not viable. So now i am boot looped I do think i know that i can download my original jellybean 4.3 and flash to this device which is another matter and how would i do this i thought odin but not for kyocera and i find that there is no custom roms etc or recovery for this device.

My quetsions are

1. where do i get the download for jellybean factory image

2. how would i install from pc (my computer recognizes it still)

3. can i install a new rom persay and again back to #2

Thank you so much
[XDA Assist] GuestK0087:
Greetings,

Thank you for using XDA Assist. There are no specific forums for your device on XDA. However, you may ask for more help here:

Android Q&A, Help & Troubleshooting

Good luck!