yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] Borkse:
So what? I can only tell you what I am experiencing with my phone and battery times are pretty decent. And your screenshots show the reason why you have such a bad battery life. Take a look at the great amount of wakelocks when your screen was turned off. During that time, your phone has never been in deep sleep mode, thus consuming a lot of battery even when screen was off. There is definitely something wrong with your individual configuration. I don't care why, it is your turn to find it out all by yourself. There are numerous apps or tools to do so.

Attached you'll find my battery time with CM13. I am really satisfied. With your battery times I would be disappointed, too. But it's not the failure of the ROM, but of your own individual config. You can have much better battery life with this ROM.

Btw phone in stand by should survive at least 3-4 days with this ROM (cf. the first plateau with almost no consumption of battery). However, I don't want to try it out ;)

Trolling, um? We are not responsible for what you are thinking or not thinking. If you reproach people of lying intentionally I want to see some proves for this. Otherwise you should leave the thread as soon as possible to not become reported or banned eventually.

Again, to put it in a nutshell: This ROM is in development phase, which means there is still an amount of uncountable bugs. However, these bugs don't have to appear for everybody. Sometimes, certain bugs only appear with a certain configuration. Therefore, it can be dependent on your individual configuration whether you have problems or not. You can't exclude that this ROM is a convenient daily driver for some (not for all). I don't want you to lose our time and continuing your provokation in this thread. This here is the place to report bugs and as soon as the devs have time, they will become fixed.
[Galaxy S III Original Android Development] lukaaa477:
With very agressive lmk i got unusable phone after a while, freezes and need to put battery out, i use zzmove relax
[Galaxy S III Original Android Development] rlon23:
Is there something that might differentiate our devices? Like some sensor or cpu revision?

I wonder why so many have issues with stock kernel.
[Galaxy S III Original Android Development] rchtk:
Thanks for your feedback.

I began looking in detail at signal levels and saw that it would go from 64% (-70dBm) the best I can get (which is sort of OK) down to 9% (probably more than -110dBm o_O) that would actually mean no phone call possible.

Then I installed a dozen of 3G apps to look in detail. And I discovered my phone hopped between 3 antennas... The worst being a femtocell (I think.. or the NSA snooping on me). I have to catch the neighbour in the next days.

I just ordered a femtocell myself (my provider gives it for free) to pollute air a bit more eh. I hope it stops antenna hopping..

I didn't have this battery drain on KitKat because my WiFi kept connected as there was less aggressive power management than in Lollipop or M...

So for people like me who have bad data connection, battery will drain and could drain even more than with screen on with wireless..
[Galaxy S III Original Android Development] whoadood:
Maybe baseband version?
[Galaxy S III Original Android Development] lukaaa477:
What is femtocell and how to get it?

What apps did u download from playstore regarding 3g?
[Galaxy S III Original Android Development] FadeFx:
It is normal that cores are off at times when they are not used, sometimes even two of them, althou never more as with only one core active we had reboots on bluetooth a2dp back in the days of 12.1 and justarchi...

Edit: another way arround that mighr be to disable hotplugging completely by setting min_cpu_lock = 4

not sure about the outcome, but i know that hotplugging isnt used in new systems at all because it sayed to not save so much power anyways.

You are still running out of memory, how big is your zram?

Gesendet von meinem GT-I9300
[Galaxy S III Original Android Development] nkirk:
CPU bug was fixed by Andy couple if weeks ago. It's a matter if time till the fix to be applied to the cm13 stock kernel.

http://xdaforums.com/showthread.php?p=64540103
[Galaxy S III Original Android Development] Flummi.FFM:
Good morning,

you was right.

until yesterday evening everything was fine with the very low lmk values. Then the phone got incredibly slow.

Five minutes ago then one more soft reboot.......
[Galaxy S III Original Android Development] Francesco0301:
Simple review of this ROM:

-Smooth and no lago, performance no problem, perfect in all kind of use;

-cannot active the battery saver, but its activate automally at 15%;

-its not battery friendly for now;

-Wi-Fi have a low speed and a bad network
[Galaxy S III Original Android Development] FadeFx:
Thats two weeks ago, unfortunarely simon hasnt been working on the device tree since christmass... maybe i can convince someone else to do that one patch... ([MENTION=3208754]codeworkx[/MENTION]?)

Edit: meanwhile the min_cpu_lock 4 seems to work in governor.

Gesendet von meinem GT-I9300
[Galaxy S III Original Android Development] rchtk:
Femtocell is a kind of small cell. That's a small baseband tower that you can have at home. It uses your internet dsl line to connect you to your operator network. Some internet and telephony providers allow their users to install these home station to enhance coverage.

The main app is specific to my operator and will not work for you. The general 3G apps that I kept are

Realsignal

Opensignal

Lte discovery

If you have further specific questions on 3G, you should find a thread other than this one to talk about it.

This night was a bad test for me, lost all my stats as battery drained 50% in my 6h night..

As seen from others report, this indeed seems specific to bad data connection. My experience with this is that Lollipop and M are much worse than KitKat. I will need a lot of others tests...
[Galaxy S III Original Android Development] sunny1234590:
Anyone got new Gello browser?
[Galaxy S III Original Android Development] galen2:
I asked to you a few days ago and i have to ask again.. What have to be that question with a development device based thread? Why u dont stop spam with trivial question this thread and go to Q&A thread?
[Galaxy S III Original Android Development] Bojmjma:
Hi,

to all who complains about cpu stuck at 1400 MHz,

In (Kernel Adiutor) or any other app, change the governor to (ondemand), and see if it helps.
[Galaxy S III Original Android Development] deny191:
Interesting how this still isnt addressed in second post.
[Galaxy S III Original Android Development] deny191:
Okay, this thread is getting interesting. We need some moderators ASAP.
[Galaxy S III Original Android Development] FadeFx:
If forkbomb444 was available to do the change in second post, he could as well just fix the bug, as it just needs to merge a pull request...

Gesendet von meinem GT-I9300
[Galaxy S III Original Android Development] Scorpionea:
u can change to ondemand but after that rom will not be as fast as it was on stock governor,it feels sluggish,but it is a workaround for stuck 1.4ghz problem or as someone previously reported latest boeffla dont have this issue any more so pick what u want :)
[Galaxy S III Original Android Development] FadeFx:
Another workarround would be to go to pegasusq tunables and set min_cpu_lock to 4, this disables hotpluging and prevents the issue.

Gesendet von meinem GT-I9300
[Galaxy S III Original Android Development] ackzsel:
Please, that's not how it works. He's pointing out that you disregard the rules of this thread. If he answered you then nothing would prevent you and others to spam this thread even more with stuff that really belongs in the Q/A thread. Grow up and go to Q/A.
[Galaxy S III Original Android Development] Hawaiihemd:
You are absolutely right! But to be fair, [MENTION=5725811]sunny1234590[/MENTION] is not the only one disregarding those rules.

I read this thread every day, and 99% of it is not development related in any way whatsoever. It is wasting MY time, and anyone elses, that this thread has degraded to the general CM13 chatroom.

Far be it from me to play the moral shepherd here, but it has been said by [MENTION=5405215]forkbomb444[/MENTION] multiple times, that this thread is for development related discussion only. That's why the Q&A thread has been created. And users should respect that.

AND any user serving to uphold those rules by reminding others about them is clearly NOT in the wrong.
[Galaxy S III Original Android Development] deny191:
But somehow in the end, post count is the thing that makes the ROM popular. When I started custom ROMs and stuff, I first started ROMs with higher post count. And the more posts we have, the more people will use this ROM, and the more popular it will be, which will eventually lead to someone actually caring about its development.
[Galaxy S III Original Android Development] buukarim:
Stop it u guys. Your way of finding the most popular rom has nothing to do with the development of this rom. U being stubborn could actually end up getting in the way of the development.
[Galaxy S III Original Android Development] sunny1234590:
Chuck it everyone! Instead of telling me such things you could have just answered my question . It's only you all who went out off topic now.

Anyways, I saw Simon online today at 6:00 a.m! So, he is definitely developing for our device.
[Galaxy S III Original Android Development] sanguinesaintly:
This is a development thread - end of. Stop posting just to keep the post count up, and don't encourage others to do the same.

Moderators - please clean up the thread and remind users (yet again) of the rules.
[Galaxy S III Original Android Development] deny191:
Seeing all the previous posts made me think this is Q&A thread. Yes definitelly as I stated earlier we need moderators.
[Galaxy S III Original Android Development] lukaaa477:
I use recommended 380 with 1device , after day or less lagging then freezeng and rrboot, so very agressive lmk are not good values, any reconendation about lmk and governor and zram?
[Galaxy S III Original Android Development] Vix_Sk:
I don't know why all have this problem of lago..i use boeffla kernel and use zzmove governor and zzmove battery plus ..and don't have any lag o.o
[Galaxy S III Original Android Development] ackzsel:
LMK: I would leave the low memory killer settings on default since it's extremely complicated stuff and without knowing what happens under the hood EXACTLY you're probably not going to improve your experience (other than the usual placebo effect). I didn't touch it and have no stability problems. Don't try to fix not having enough RAM. You just can't fix a lack of RAM other than using less.

Governor: I used both lulzactiveq and pegasusq and I'm still not sure which one is best. Maybe this can be left default as well since the 1400 MHz lock bug *should* be fixed by now. Please correct me if I'm wrong.

ZRAM: I have ZRAM disabled. Same argument as LMK. Don't fix lack of RAM with anything other than more RAM or less processes.
[Galaxy S III Original Android Development] Francesco0301:
link for the best kernel + settings for this rom? Thanks!!
[Galaxy S III Original Android Development] sanguinesaintly:
Not #1439 #1950
[Galaxy S III Original Android Development] viktor92:
Zram is a must, like it or not, on the s3. I use 600mb on 1 device, lulzactive tunable with deadline, OC to 1.6, GPU 266/300/400/500/600, all from KK to MM, and never had cores stuck at max frequency, neither reboots and the performance is always good. I leave LMK boeffla stock.
[Galaxy S III Original Android Development] sanguinesaintly:
We "guys" are dealing with it by trying to stop it. If by "bikeshedding" you mean we are trying to get the thread back on track, then you are spot on.

Have a go by all means and watch the thread go down the drain - after all - as you said, the more posts, the better the thread eh ?
[Galaxy S III Original Android Development] whoadood:
It was not me who said that. ;P
[Galaxy S III Original Android Development] sanguinesaintly:
Quite right - my mistake - the second para was directed at deny191 - I apologise for that. The thread has overwhelmed me !
[Galaxy S III Original Android Development] whoadood:
By the way I don't understand what do you guys have against zram. It's not as fast as real memory, but it's a ton faster than regular swap, compresses well, etc. Also, regular swap wastes IO cycles which, as we know, are finite.
[Galaxy S III Original Android Development] rchtk:
Yeah zram is supposed to be quite efficient. But just wondering what are your use cases that you need to change lmk or zram?

Edit: forgot to mention I'm using boeffla and only installed Google play from Google.
[Galaxy S III Original Android Development] whoadood:
Hmm, almost everybody here has agreed that the default LMK values are pretty bad. In my experience, those values are configured in a way that make the phone keep too many apps in memory, to the point where it starts paging violently to the internal storage (and you have to stare at a white screen for 10 seconds or so) or even goes OOM and the phone reboots.

I'm not sure how the Linux OOM killer works on Android, but I think it doesn't kill anything, it just reboots the phone--I guess it is because the OOM killer is aware of the existence of the LMK and if an OOM condition is reached, it is because the LMK has pathetically failed, so it's time to pack up and start over. Once again, this is something I'm guessing, as dozens and dozens of spamblogs have hidden any kind of useful technical information when you do a search for "lmk" on Google. :D
[Galaxy S III Original Android Development] Berta Paneslowski:
For people using myphoneexplorer and have problems with writing on external SD card: load this beta client www.fjsoft.at/mpeclient.apk (it's beta12) and it will solve this problem! external card is visible and writable via wifi.
[Galaxy S III Original Android Development] FadeFx:
Please in future post these kind of non development related stuff, even if it is helpfull, to the q&a thread where it belongs. Thank you.

Gesendet von meinem GT-I9300
[Galaxy S III Original Android Development] lanx:
Updated to latest nightly from CM Updater and now I have problem with Camera (from Google Play, used to work fine) it can't save a photo, just shows error message, anyone have the same problem?
[Galaxy S III Original Android Development] xyzwqt:
I have bootloop with the last update. :(
[Galaxy S III Original Android Development] racky29:
No bootloops here,
[Galaxy S III Original Android Development] Drollach Gûntar:
Problem with playing .flv files.

Screen colors turns ugly when i play downloaded .flv videos.Colorful lines fills the screen.
[Galaxy S III Original Android Development] arifnasirshaikh:
On Playing video in facebook app causes green lines on screen..
[Galaxy S III Original Android Development] Llun:
I have installed Nightly 20160111 and i have a few bugs: Gmail and Nova Launcher Prime crashes sometimes and battery led turns green at 90%.

(Nightly 20160111, Boeffla kernel 5.0 beta8 and Xposed Framework)
[Galaxy S III Original Android Development] viktor92:
I'm still waiting for mDNIe scenario and mode...
[Galaxy S III Original Android Development] whoadood:
Has CM ever had that? I'm curious.

On the stock ROM, letters have a white halo. I think it's because of that feature. It's some kind of image post-processing.
[Galaxy S III Original Android Development] viktor92:
Yes, on CM 12.1
[Galaxy S III Original Android Development] belumada:
Yeah, me too. I have 'sorry camera has stopped' error. Cannot get pass through the welcome screen in Camera app ( DLed from Play Store). Once I swipe left to get to the video capture intro screen, the error shows up.
[Galaxy S III Original Android Development] FadeFx:
First of all, do not report any bugs or issues that occure while your system is modified (custom kernel in your case)

The battery led is intended to behave like this.

Gesendet von meinem GT-I9300
[Galaxy S III Original Android Development] mahe.:
Deadline is slow. Use ROW instead of deadline arter made some videos regarding governor you can check the comparison in that video.
[Galaxy S III Original Android Development] vkopzon:
Looks like removing "android.hardware.audio.low_latency.xml" from /system/etc/permissions, is the only thing to solve the BT stuttering issue.
[Galaxy S III Original Android Development] lanx:
Just to be sure did you uninstalled Camera (system app) from GA first?

I got this error before but with Camera from GA only.
[Galaxy S III Original Android Development] N-TheAndroNoob:
I'm not sure if this question is supposed to be asked here or not, but I was wondering what the state of the ROM is like, as of this post? You know, the major bugs that are plaguing users that are on the stock kernel, with no other mods such as Xposed? Thanks.
[Galaxy S III Original Android Development] sunny1234590:
Have you even tried this? I mean did it actually work? No other issues caused by this?

I think [MENTION=5405215]forkbomb444[/MENTION] can comment on this
[Galaxy S III Original Android Development] chirag2718:
i can confirm..

i deleted that file n rebooted the phone..

then audio via BT works like a charm and even if ppl who r having problem with sound distortion can delete this file as it will solve the distortion problem
[Galaxy S III Original Android Development] Llun:
My system is already modified by using CM 13. I use Lord Boeffla kernel so i can control CPU, GPU and other parameters. Why is the battery LED turn green with 90%? The logic is to inform the user when the phone is charged.
[Galaxy S III Original Android Development] senaferdy79:
Is this your first android phone?

Your question is extremely dumb af
[Galaxy Note 10.1 (2014 Edition) Original Android D] ShevT:
​

/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*/

Attention!

If You are using

Xposed

and You have problems, it is Your personal problem. No need to report them to me.

​

Special thanks:

Christopher N. Hesse - RaymanFX

The guys of the Exynos 5420 team

What works:

3G (Fully fixed 20160826)

Sound

Microphone

Bluetooth

WiFi

WiFi direct (Fixed 20160911)

GPS (Fixed 20151216)

InfraRed (Fixed 20160819)

Stylus

All sensors (compass, gyro...)

OTG

SD card

Camera/Torch (Fixed 20161013)

Screen Record (Fixed 20161014)

Screen cast/Wireless display (Fixed 20161118)

What does not work:

ANT+

Call record - Partially it works. Recording goes, but drops the phone program.

Downgrade bootloader to 4.4.2 (if previously used stock 5.1.1 firmware)

Download:

Lineage OS 13 (Instead Cyanogenmod)

MoKee Open Source

CyanogenMod 13. Updating will not. Latest update - 20161230.

ResurrectionRemix M. Updating will not. Latest update - 20161230.

GoogleAPPS:

Open Google Apps project

My TWRP 3.1.0-1 for SM-P600/SM-P601 (20170326):

AFH - zip file.

AFH - img.tar (for ODIN)

Sources in github:

Device

Vendor

Kernel

TWRP

Programs that I use for s-pen:

SPenCommand - action menu

MyScript Smart Note - notes

MyScript Stylus (Beta) - Keyboard for Handwriting

​

Donated:

---

XDA:DevDB Information

SM-P601 Android 6.X, ROM for the Samsung Galaxy Note 10.1 (2014 Edition)

Contributors

ShevT

ROM OS Version: 6.0.x Marshmallow

ROM Kernel: Linux 3.4.x

Version Information

Status: Stable

Created 2015-12-17

Last Updated 2017-06-13
[Galaxy Note 10.1 (2014 Edition) Original Android D] ShevT:
Reserved
[Galaxy Note 10.1 (2014 Edition) Original Android D] ShevT:
CyanogenMod 13

CyanogenMod

About | Home Page | WiKi | Git page​
[Galaxy Note 10.1 (2014 Edition) Original Android D] ShevT:
ResurrectionRemix M

ResurrectionRemix M

Home Page | Git page​
[Galaxy Note 10.1 (2014 Edition) Original Android D] ShevT:
MoKee OpenSource

MoKee Open Source

About | Home Page | Git page​
[Galaxy Note 10.1 (2014 Edition) Original Android D] ShevT:
Lineage OS

Lineage OS

About | Home Page | Git page​
[Galaxy Note 10.1 (2014 Edition) Original Android D] ShevT:
Downgrade bootloader to 4.4.2

This will fix the problem with the sound (crackling) on my firmwares in the transition from the official 5.1.1 firmware.

Attention! I do not take any responsibility for possible negative consequences.

1) Make a backup copy of all data (including sections EFS, Modem, Preload)

2) Copy backup on PC

3) Download Odin 3.10 and Bootloader (You must rename the file, so extension was .tar or .tar.md5. For example - BL_P601XXUCOF1_CL5054848_QB5172195_REV00_user_low_ship.tar)

4) Run "download" tablet mode.

5) Connect tablet to PC

6) Run Odin

7) In the BL (bootloader) field, insert file BL_P601XXUCOF1_CL5054848_QB5172195_REV00_user_low_ship.tar

8) Start.... The bootloader will be installed and the tablet reboots.

9) You can go to TWRP and restore the backup (It is enough to restore the data and /data partition).

10) Installing firmware and OpenGapps-nano.

P.S. If you have not switched on my firmware (use stock 5.1.1 firmware), it is recommended to remove all of the data (not to restore /data partition)
[Galaxy Note 10.1 (2014 Edition) Original Android D] acemarco:
Great news ShevT... Thanks a million! :D
[Galaxy Note 10.1 (2014 Edition) Original Android D] apokit:
From where can we downoad it.?
[Galaxy Note 10.1 (2014 Edition) Original Android D] Aletheia:
Good job!

I hesitate to mention the "no placeholder" rule, especially to a dev who do original work, but...

Anyway hope to see a release soon, keep up the good work!
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Nice!

Will it work on P600 like other P601 roms?

Hope we see a download link in the next few days!

That would be an awesome xmas gift!

Impatient to test it!

Keep up the good work, ShevT!:good:

Merry xmas!!!:angel:
[Galaxy Note 10.1 (2014 Edition) Original Android D] ruud:
is there stil no download link?
[Galaxy Note 10.1 (2014 Edition) Original Android D] ShevT:
Not yet.

I now have a problem with time. It will be some time - will build
[Galaxy Note 10.1 (2014 Edition) Original Android D] CodeDroid:
Thanks for the good work ShevT, looking forward to Marshmallow. Hopefully, we'll have a build before the end of the year?
[Galaxy Note 10.1 (2014 Edition) Original Android D] ShevT:
see firmware
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
Can this be flashed on the SM-P600?
[Galaxy Note 10.1 (2014 Edition) Original Android D] ShevT:
Yes
[Galaxy Note 10.1 (2014 Edition) Original Android D] ruud:
can you give a link to it. i only see the 5.1.1 rom
[Galaxy Note 10.1 (2014 Edition) Original Android D] mosimchah:
It's in the OP. Link: https://www.androidfilehost.com/?fid=24345424848487946
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
Hi pcparaosamigos,

crackeling sounds while playing videos is a typical issues of LP bootloader.

If you've ever installed a TW5.1 rom on your device you should change back to KK bootloader.

There is an how-to in general section, I believe...
[Galaxy Note 10.1 (2014 Edition) Original Android D] ShevT:
I see Youtube today. At the moment, my tablet is empty. You hawe LP bootloader?
[Galaxy Note 10.1 (2014 Edition) Original Android D] faridsenior:
No, I don`t think so. I have some little noise or interruptions in watching TV or playing games. Another example, when I scroll down in browser or in play store there is that noise or lag. :rolleyes::crying::crying::crying:
[Galaxy Note 10.1 (2014 Edition) Original Android D] ollimi1:
If you're not sure about LP bootloader I would test it....:p

You need only to flash a kk repair firmware via Odin, than flash TWRP and restore your backup or start from scratch with a realy clean install.

The how-to is foolproof...

... and if your issues are indeed bootloader related they will be gone if you follow the steps carefully.:good::cool: