yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S Android Development] zigonneux:
too early to tell, let's just wait and see... if you absolutely want to know right now, send a PM to schishu and ask him if he will provide what's been asked. Only HE, has the answer to your question.
[Galaxy Tab S Android Development] robhug:
Im gonna wait :) it's already good to know what happened
[Galaxy Tab S Android Development] amateurhack:
Right, which is why it does not exactly jibe with: http://xdaforums.com/showpost.php?p=68656615

If its a GPL issue, and that's all, then closing the thread is fine, but we should have some clarity. I certainly didn't think that someone took the time to reverse engineer the kernel to find the relevant issues.

Since we have a few that say they can compile the kernel with the N ROM and make it work, then I pose a challenge to them: Make a video. Perhaps we can see why some are able to get it work and others cannot, and then figure out what the real issue is.

And, until someone can come up with good reasons why I should not, I will continue to use the N ROM. I have no reason to believe [MENTION=2371134]Schischu[/MENTION], who has been a long-time developer on XDA, should not be trusted. I trust the mods to do what they believe they should and do not blame them, but seeing as we now have two groups claiming different results from the same code, perhaps we will figure out that Schischu is justified.
[Galaxy Tab S Android Development] cicciobastaro:
urgent help: request urgent help. My SM-T705 is locked and requires reboot after ever

Title: My SM-T705 is paralyzed and requires reboot after each call incoming or outgoing

I was hoping to find a bit of peace, but it seems they can not.

Who will help me to solve the problem described in the title of this post without resorting to a clean reinstall, the configuration of the many apps etc, etc.

I tried and failed to install the latest release compatibille with MM dialer from google apkmirror.

I hope someone can help me
[Galaxy Tab S Android Development] LenAsh:
Interesting...

Never seen a development thread hijacked quite like this before.

We will review the status of the other thread soon. We have received dozens of PMs related to this - and a real mixed bag too.
[Galaxy Tab S Android Development] hajah:
Ok, so basically, what the mod is telling us is that:

- OP posted a kernel source that according to some people, is not the real kernel, the N rom is really using.

- N ROM has "issues"

Yeah, I can understand that, but my understanding is that some dev kept scratching his head to understand how OP made his N rom work so well and so quickly, and out of jealousy, nagged some mod, using security/GPL crap arguments, to force OP to publish the real source. Was that the real reason? Or maybe, said dev, just wanted to replicate OP'S solution onto his own ROM??

Regardless, mod should never have closed the post! OP should have published the kernel source (and maybe he did, who can REALLY say he didn't?) and the mod should have discussed the matter with OP.

The way it was done, who loses the most? The users...

Was the real kernel published? No

Was the GPL issue cleared? No

Were the security 'issues' fixed? No

Were there any fixes at all? No

Was the ONLY tab S dev alienated? Yes

Are we hijacking a dev thread cos of dumb mod politics? Yes

Good for you, XDA mod..

Some really neutral and clever thinking on your part!!

Congrats
[Galaxy Tab S Android Development] deadman96385:
Your post seems to be aimed at me, i could care less about the kernel source there is nothing new there. The fixes would be in the device tree which is he is allowed to keep private and in this case he did. The problem is even though it may be inconvenient you have to follow GPL by publishing the kernel source. Users may not like it but that is the rules of XDA. [MENTION=2371134]Schischu[/MENTION] is not the only dev for the Tab S, he is just the only one doing AOSP which is very different then doing other roms which are primarily caf based, which is why they have different bugs.
[Galaxy Tab S Android Development] hajah:
Hi,

It wasn't aimed at you, specifically because I don't know who rattedd on OP. But if the hat fits...

I'll rephrase that "only dev", cos obviously there are others... I ran my tab on a few CM flavors for quite a while. I'll replace it with "most popular dev".

For the rest I stand by it.

The issue, if there really is one, should have been handled differently, and it's up to XDA to defend user's interests and XDA rules. Read N's last post and tell me what value did that post bring to the discussion?
[Galaxy Tab S Android Development] deadman96385:
The mod did not need to bring anything to the discussion, before a mod closes a thread they reach out to the person of interest to fix the problem if they do not respond or do fix the problem the mod locks the thread until it is fixed. I have already explained in a previous post what the issue is with his kernel source.
[Galaxy Tab S Android Development] ashyx:
I'm afraid I have to agree here. While it's highly frustrating for a dev to have his hardwork simply copied and used else where, especially without credit, its important to keep it in check.

At the end of the day Android IS about being open and sharing. So it gets frustrating for others when devs refuse to post or hide their code.

I would guess pretty much all devs are guilty of it at some point, but when a dev still refuses to release it when requested or simply doesn't respond then there needs to be some recourse.

For example look how frustrated people get with the big boys like Samsung who consistently break the GPL.

Rest assured that any dev will have been given ample opportunity to respond and/or given the opportunity to explain.

Mods don't usually just lock major threads for nothing and neither do they have to divulge the details of their decision. Usually the mods are in discussion with the dev while all this is going on.

The issue will be resolved one way or the other.

It will be a sad state of affairs if schischu decides to discontinue the project as it does knock the wind out of your sails when something like this happens.

There's no point in mod calling or calling out other devs. At the end of the day decisions need to be made based on the facts and rules enforced. If this wasn't the case XDA would be in a right state and would suffer as a result as would the whole open source nature of android.
[Galaxy Tab S Android Development] marmo:
[MENTION=2371134]Schischu[/MENTION], [MENTION=4222965]deadman96385[/MENTION], [MENTION=3830277]LenAsh[/MENTION], this a no sense for most of us, but I understand that rules are rules.

[MENTION=2371134]Schischu[/MENTION] I think it's time for you to finish this and make a decision, please provide what was requested, no matter the reason of the request, but please do it. Then [MENTION=3830277]LenAsh[/MENTION] will reopen the thread.

Do not let it go just like that. You put too much effort. I'm following you since the very first build for Xoom, that was years ago...

You are all senior members and devs, please do it for the sake of the forum. Talk to each other and solve this situation.

Thank you.
[Galaxy Tab S Android Development] Hannibal226:
[MENTION=2371134]Schischu[/MENTION]

Maybe this giving some motivation back, seeing how much standing behind ur work.

I fully understand ur position of stoppping developing, but maybe this can "overshadow" the complaining in bg.

Even there is/was something wrong, nobody things it happens on purpose!

CHEERS and thanks for gr8 work! (N7 is running fine here on T800 :P)

That's the point and I hope nobody will complain about the work from mods doing their job in freetime and primarily can only decide by rules!

CHEERS and let's see what [MENTION=3830277]LenAsh[/MENTION] can do ;)
[Galaxy Tab S Android Development] Orion116:
Actually looking at his response I believe it was on purpose. My reasoning is two fold: one, he called a legitimate compliant bogus without proving evidence that it wasn't true; two, if he just forgot to upload the new kernel why didn't he just upload it and not quite?

All in all if it was an accident, which I doubt, why quit over it. Explain why it works or upload the updated kernel. But quitting makes you look guilty no matter if you are or not.
[Galaxy Tab S Android Development] InkSlinger420:
So much fail in this thread....Just do like every other dev in the site is supposed to do, and upload your kernel source FOR THE COMMUNITY...That's just simply the rules of the forum...Running , and crying about quitting cause you don't wanna share stuff you KNOW isn't 100% your own source in the first place, is a joke...Handle your business, and stick around as an asset, or don't, and feel free to walk... Adult decisions....
[Galaxy Tab S Android Development] Schischu:
Ok so I am back. A lot happened since I wrote my post.

Some thinks to clarify.

The branch of my kernel may be named cm-12.1 but that is just a name. It is indeed the source for my nougat (1:1 the same as my marshmallow) kernel.

And that is where you are wrong. While it is true that Android N changed some things regarding SELinux it is not true that I thereby had to update the kernel.

The other solution and which I used was to simply disable this new feature in the init binary. Which is APACHE btw. and I don't have to make public.

BTW. if you are the cause for this stupid issue than I am deeply disappointed in you, as we have worked well before.

Did you even test if you can boot my nougat rom with a custom build kernel with my sources? I guess not. So thanks for that...

And yeah, NOBODY asked my about how I got it running.

Just 2 requests in my thread to point the to the current source of my kernel, which I did!

Nobody asked my follow up questions.

I wasn't even informed that my thread has been closed.

You can guess how surprised I was.

After asking LenAsh to reopen my thread I got an response stating that it is being investigated cause of complains.

No information what they complained about, and till today nobody asked me any questions.

Nevertheless the thread is still closed...

This is a complete cluster****....

That's my point which seems to be totaly ignored. The sources are up to date!!!!! I have not made any changes since marshmallow.....
[Galaxy Tab S Android Development] amateurhack:
I know I speak for a lot of people when I say I'm glad to see you back on here!!!

We've got at least three people that are on here saying that the Kernel you posted will boot the N ROM. I can only hope that those who are saying that the kernel will not boot have actually tested it.

Either way, all we need is proof. I know it would take time, but if we had a video of someone compiling, loading, flashing, and booting the ROM with that kernel, then we could put this to rest, and the mods would have evidence to support reopening the thread, and you would be justified. I would do it, but it would take me days of getting up to speed on all of that to do it, and quite frankly I don't have time.

I hate that the mods closed the thread, and I really don't think that they needed to if they investigated it a little more. But I would rather that they play things safe, and that means sometimes they will do things that seem heavy-handed at the time. Thankfully, in this case, they are willing to listen to you and those of us who have voiced concerns.

So, lets stop antagonizing each other, and lets figure out what is real and not real, and go from there.
[Galaxy Tab S Android Development] Orion116:
Then why the heck didn't you just say this to start with! I also don't think disabling a vital function of Android was the answer. In fact I think that is a security risk.
[Galaxy Tab S Android Development] Schischu:
Ah yes thank you for that. Hm maybe it is because that post is the only information I have regarding why my thread has been closed?!?

So how the hell should I know what I have to write to keep you happy?

Btw. if you want security, don't use an alpha. That should be clear. If not, than it is know.
[Galaxy Tab S Android Development] Orion116:
Um. Why didn't you just fix the kernel instead of using a dangerous hack? If I was an user of the ROM I would stop using it immediately. It is one thing to run permissive it is another to remove a security check in order to be first!
[Galaxy Tab S Android Development] LenAsh:
So, folks - not wishing to continue the hijacking of this thread (!) I'm happy to re-open the other thread under certain "reasonable" conditions.

!) If the other thread IS re-opened, it must be made clear to members within the OP that they are taking a degree of risk. While this applies to ANY flashable code, of course, it must be made CRYSTAL clear.

2) Anyone who makes a valid complaint will be taken seriously and the thread's viability will be reviewed again.

3) Any "dissenter" posts MUST be reported to allow appropriate Moderation.

It is the spirit of XDA that open and collaborative development takes place in a cordial manner. Development means just that - taking something and shaping and improving it when it has a degree of promise within it. Like Cyanogen and all it's derivatives, one supposes.

Views?
[Galaxy Tab S Android Development] LenAsh:
On balance, I shall re-open the thread - bear in mind the comments made in my post above.

I will also clean this thread of the "OT" dialogue - any or all of it can be reinstated if necessary.

Thanks
[Galaxy Tab S Android Development] ashyx:
So you've never compromised a device by invalidating knox or rooting or even installed a questionable app?

I take it you also never used a device before SElinux was introduced ? Otherwise Gingerbread must have scared the bejesus out of you everytime you went on the net.

Honestly be sensible, it was a simple mod to get the device booting, not a total shut down of all security.

Android security and SElinux often gets in the way of progress so a temporary disable allows things to move forward and bigger bugs to be squashed.

Stability is more important. The security part can be drilled down afterwards.

If your main concern is security then you really shouldnt be messing with your device.

Stay on stock and let others do the leg work then come back when it's up for official release.
[Galaxy Tab S Android Development] stopa10:
Thanks. One way or the other, this incident helped to clarify a few things about [MENTION=2371134]Schischu[/MENTION]'s AOSP Nougat ROM.

Having said this, I think we should not forget that the ultimate interest of the community is *development*, and [MENTION=2371134]Schischu[/MENTION] has surely done a great job in developing this device, which in this respect seemed pretty much dead a few weeks ago.

I hope we, and especially [MENTION=2371134]Schischu[/MENTION], can put this behind our back and look forward to the new and promising opportunities that AOSP and stock MM together offer.
[Galaxy Tab S Android Development] SferaDev:
I had PA booting using exynos5420 sources on the T800 with actual support for the disabled security features. Shortly after when I got a chance I pushed everything to GitHub. The fact you don't see other builds around doesn't mean he's the only one with nougat up and running (with different sources).
[Galaxy Tab S Android Development] Ricardo Silvestre:
How can I remove google search bar?

How can I remove the Google Search bar on the home screen?

Google Search bar
[Galaxy Tab S Android Development] Limakos:
Probably you can't without installing 3rd party launcher

Sent from Samsung T800
[Galaxy Tab S Android Development] mrzzheng:
Thanks for all the great work. Will this ROM be updated using official samsung MM drivers and September security patch?
[Galaxy Tab S Android Development] Ricardo Silvestre:
How to install Xposed and Gravity Box?

Can anyone please make a step by step on how to install xposed and gravity box? Or a link if there is already one for Tab S 8.4 Wifi only T700. I'm new to rooting/flashing and I just followed the step by step on the first post and it worked wonderfully on my Tab S 8.4 T700. I just want to have the clear all recent app button on my recent apps drawer. It would be much appreciated. Thank you very much.
[Galaxy Tab S Android Development] Schischu:
Yes security patch will be coming soon, drivers may take a little while longer.
[Galaxy Tab S Android Development] mrzzheng:
Thank you :good:
[Galaxy Tab S Android Development] zigonneux:
i'd be curious to know what type of drivers was used, if they were not the MM drivers !
[Galaxy Tab S Android Development] vykana:
help im having an issue with installing apps. When i install apps through play store everything is fine. when i try to manually install app with i get "insufficient storage error". I cant install 2 MB apk manually while i can install 50 MB app with play store. All this While i have 2gb left in internal storage. please help.
[Galaxy Tab S Android Development] c411umuk:
Anybody had any issues with WhatsApp? I searched the thread but couldn't find an issue similar to mine - I couldn't send any videos (Kept saying "This video can not be sent, if this problem persists please reboot).

In the meantime I have gone back to using IronROM until my new phone arrives this week.

Cheers
[Galaxy Tab S Android Development] drshan:
Hey dude. Flashed this bad boy on my 805Y. Everything is working spot on.

Thank you.
[Galaxy Tab S Android Development] Schischu:
LP as before, no need to rush to MM drivers.
[Galaxy Tab S Android Development] roselanguste:
Hello Schischu!

(Please forgive my not so good English!),

I am now testing Your awesome ROM, and so far installation works like a charm, and the Device/ROM is now installing all my daily used apps from Playstore! What i see so far is, that all works very smooth, and i like it very much! I have not much, but surely i will donate You for Your hard work on that beautyfull ROM! I let You know my further experiences with Your ROM!

Thanks a lot!

RoseL.
[Galaxy Tab S Android Development] ashyx:
Please don't quote the whole OP. [emoji52] [MENTION=2371134]Schischu[/MENTION] would have done.
[Galaxy Tab S Android Development] goeybones:
help help

please need guidance...

after smooth installation of CM13 and all the apps, i want to reboot my tab s 8.4 LTE, so when i push the power button there is only "power off" option, so i missing the reboot and flight mode option, so what should i do to fix this problem...

thanks...
[Galaxy Tab S Android Development] rookie12:
Download quick reboot root

And reboot there
[Galaxy Tab S Android Development] cmcole101:
Oh how I hope I'm not one of those #whinnylittlebitches to which you refer because I absolutely LOVE this ROM. Except getting the Exchange Services to work, which I did and now this ROM works exactly as I was hoping to find online, please do not let grumps that couldn't turn on a light switch much less install and run a ROM as sweet as this one.

Believe me when I say there are WAY more people who love your work than those #whinnylittlebitches. ;)
[Galaxy Tab S Android Development] sheng1337:
[MENTION=2371134]Schischu[/MENTION]

I tested your sweet ROM on my T805. Great work.

Fingerprint is not working. I added three prints, they are not detected to unlock device and i can not delete the print anymore once added.
[Galaxy Tab S Android Development] SalsaForte:
Fingerprints scanner works fine for most users. I doubt it is related to the rom. Maybe a clean reinstall or reflash would fix your problem.

Envoyé de mon SM-T800 en utilisant Tapatalk
[Galaxy Tab S Android Development] mightywhites29111971:
I am really liking this ROM however there is one thing that concerns me. When it boots up there is a message on the top left hand of the screen that says 'kernal is not seandroid endforcing'. I have read conflicting things with some people saying it is not a problem and some saying it is. Does anyone know how I can solve it, if I need to? I was on the NZ 6.01 MM before I rooted so I wouldn't have thought it was an issue with the bootloader. Any help appreciated.
[Galaxy Tab S Android Development] roselanguste:
Accu-Temperature!

Hey People!

I used also this awesome ROM for a few days, and it is realy good!

But a little Problem, when i activate LTE instead oft 3G, my accu goes very hot and drain to 0% in 30 Minutes!?

Have anybody seen the same in there devices, or knows a solution!?

My device is SM-T705.

Thanks!
[Galaxy Tab S Android Development] UncleMarty:
I think im going to have to stop using this ROM, like many others, I too have been hit by the battery drain bug. With my screen on lowest and minimal things running my battery is now drwining faster than it can charge with just browsing/whatever. If not plugged in my battery will drain in under 2-3 hours. The microphone bug is still happening too, totally unable to make a phonecall due to such poor quality :(

I've looked into the battery drain and on the battery section it just shows "misc" is by far the highest drainer, and in more detailed apps it shows System_server as cpnstantly using 30% of the CPU non stop.

This version of marshmallow isnt usable till its fixed so im waiting for the official files to get rooted and just uninstall all the bloat manually instead. Its a real shame because i'd rather use an AOSP.

*edit* it looks like one or more of the cores isnt ztepping down in speed and locking at 1.9ghz. Anyone else able to verify?
[Galaxy Tab S Android Development] roselanguste:
Have You LTE enabled? In my case i have the same accu-drain as You, but only when LTE is enabled!? When i disable LTE and use 3G instead, the accu-drain Problem is gone! And with 3G the accu holds in my case even better than with Stock-ROM!
[Galaxy Tab S Android Development] gniblack:
I have the SM-T800, and after receiving the Marshmallow update I decided to purchase a Samsung Pro Plus 128GB MicroSD card. After installing it I noticed that I do not have an option to format it as internal storage (adoptable storage). Is there a way to use it as adoptable storage? I have someone from Samsung looking into it, but they're not as knowledgeable as you guys it seems. I feel like I am not posting this in the correct place as I am not using this ROM. However, if it will work with this ROM I'd like to know.
[Galaxy Tab S Android Development] Duskycub:
there is a thread in general that has a patch for adoptable storage don't think its needed for this rom but it is for the new TW version. Worth a look at least http://xdaforums.com/galaxy-tab-s/general/patch-adoptable-storage-enabler-t3460478
[Galaxy Tab S Android Development] CyphusBlue:
SM-807R4

So I bought resold Tab S that was billed as an SM-T800 but I received an SM-T807R4 (us cellular LTE). If I can still root it and put a good rom on it then I don't think I'll fight to return it. Is the T805 image compatible?

The T807R4 is a Qualcomm and the device says it is chagallteusc.
[Galaxy Tab S Android Development] haimann95:
What does it say in CPU Z?

Gesendet von meinem SM-T705 mit Tapatalk
[Galaxy Tab S Android Development] CyphusBlue:
Here's a bunch of the details.

CPU:

Model: Qualcomm MSM 8974

Cores: 4

Architecture: Krait 400

Revision: r2p0

Process: 28 nm

Clock: 300 MHz - 2.27 GHz

...

GPU Vendor: Adreno (TM) 300 @ 450 MHz

GPU Clock: 320 MHz

Device:

Model: SM-T807R4 (chagallteusc)

...

Board: MSM8974

Hardware: qcom

System:

Bootloader: T807R4TYU1ANK1

Build ID KOT49H.T807R4TYU1ANK1
[Galaxy Tab S Android Development] haimann95:
This rom won't run on those Snapdragon devices, this is Exynos only ?

Gesendet von meinem SM-T705 mit Tapatalk
[Galaxy Tab S Android Development] databoy2k:
I use Pinned Apps on a semi-regular basis. Unfortunately, because AOSP assumes that you've got the navigation bar (unlike Touchwiz), and because there is no navigation bar, my only way out of my pinned apps is to reboot the tablet.

Any tips on how to get a "long press of overview" out of the Tab S? I've tried adding qemu.hw.mainkeys=0 to my build.prop, but couldn't get the navigation bar to appear. GravityBox doesn't seem to list "overview" as an option when customizing the hardware keys (let alone the command that is being sent when long-pressing it). All that I've figured out is that long-pressing the app-switch key is menu, which is NOT how you get out of pinned apps.

Thanks!

--Databoy2k