yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S Android Development] rspaulo:
Just installed. Had all the problems mentioned but now is awsome. The only strange thing that I've noticed is my Hangouts doesn't seems to be working as it should be. It isn't reciveing the messages at the time like my phone.

Enviado de meu SM-T800 usando Tapatalk
[Galaxy Tab S Android Development] brycegreen:
Every time I power on the device I get notification that says: "Process system isn't responding. Do you want to close it?"

I haven't noticed any issues yet, but it takes away from the overall smooth ROM experience. Should I re-install the ROM?
[Galaxy Tab S Android Development] Raod:
I'd the same error every reboot and already tried a format/install but it's still there...
[Galaxy Tab S Android Development] dknk99:
On my T700 I'm not getting that error. Try another install, wipe it totally clean first.
[Galaxy Tab S Android Development] bubenking:
could u compile cm13 ? :D

i would defenetly love that :)
[Galaxy Tab S Android Development] wbedard:
Did you post in the wrong thread? While there are two separate threads focused on CM 12.1 on the T800, this thread focuses on a ROM based on pure AOSP. Please read the first post for more details. Please use the search function to locate the threads for the CM-based ROMs.

R/

wbedard
[Galaxy Tab S Android Development] bubenking:
uhh yes :D
[Galaxy Tab S Android Development] Khar00f:
I know some oems don't disclose all their sources for certain aspects of their ROM. I thought maybe the video drivers would be maybe one of them given it's their own proprietary CPU SOC.

If that were the case then devs would have to come up with their own wrappers/drivers to interact with the hardware otherwise they could be in trouble for ip infringement, so I was thinking maybe it could be something the user can do on their end if they had the right files. That would the the heat away from the devs.

Don't know if that makes it clearer, but from what you were explaining I don't believe this to be the case.

My understanding from what you explained and I'm messing to say refers to libEGL which you mentioned you're already taking the files from Samsung ROM.

So in the end, don't mind me, just thinking out loud :)
[Galaxy Tab S Android Development] :
That's what I'm dreaming of: a device, which source is gpled (or apached for that matter). But I think that will never happen: even on pcs you can compile everything from source, but the graphics drivers (nouveau is not usable, if you want fast openGL and video de-/encoding)...

I would be very happy to get my hands on the mali egl/gl development kit - but that is only delivered to mali oems.

BTW: legaly spoken, the reason, why you have a working rom without violating sammy's copyright, is that you (the rom's user) takes the blobs from the original rom (which right to use, you have bought with the device). We (the devs) wouldn't use sammy's binaries... ...of course not! :angel::angel::angel:
[Galaxy Tab S Android Development] Khar00f:
Cool, thank you for your help.

Weirdly enough I have a weird issue and wanted to see if there's something I can get for you before I wipe.

My tablet ran out of juice a couple of days ago and I connected it to charge throughout the day yesterday as I wouldn't need it with everything happening for the holiday.

When I got home yesterday night, I tried turning it on, it started booting gets to the homescreen freezes there for a few minutes then reboots. It doesn't reboot to the samsung splash screen but instead straight to the marshmallow boot admission.

It's stuck in a bout loop until it ran out of batteries again and it shut down.

Once it's in the bout loop it's very hard to turn it off for some reason. I managed to get to recovery one, wiped dalvik and cache, but the issue is not resolved.

I'm about to do a complete wipe but wanted to know if there's any files you want me to retrieve and upload if they may be of any help?
[Galaxy Tab S Android Development] brycegreen:
Does formatting the SD card as internal fix the FAT 32 transfer limit of 4GB? My T700 has been rebooting in the middle of a transfer (over 4GB), and I just re-installed the ROM. I'm copying smaller folders.. So far so good
[Galaxy Tab S Android Development] gscollier:
Internal is f2fs encrypted, 4 terabyte limit! Thanks [MENTION=2371134]Schischu[/MENTION] for the info.

SM-T700
[Galaxy Tab S Android Development] brycegreen:
So it's not an issue of the size of what I'm transferring. It is still rebooting during file transfer from my PC(MTP).

This happened last night so I wiped everything and re-installed the ROM. Same issue. This is very troubling as I have no other way of transferring data to the card after it's been formatted.
[Galaxy Tab S Android Development] gscollier:
I've had reboots also. Now use Wi-Fi or OTG. Price to pay for alpha ROM. Just to clarify, portable is fat32, 4 gig limit. Internal is f2fs, no practical limit. I suspect that internal format and a clean ROM install would require reformat.

SM-T700
[Galaxy Tab S Android Development] brycegreen:
Is there a built in Wi-Fi file transfer, or will I have to go through TWRP's ADB sideload? Not sure what OTG is.

It's strange, I've had this ROM on my device 3 separate times (don't ask), and the first time I had no reboots while transferring 12GB+. Small price to pay for the smoothness of the ROM though!
[Galaxy Tab S Android Development] gscollier:
Numerous file managers can access LAN shares. Sync Me is great, not a file manager but I have a sync folder on device and pc. Solid Explorer works very well also. Google OTG.

SM-T700
[Galaxy Tab S Android Development] brycegreen:
Just rebooted in the middle of a Wi-Fi transfer with ES File Manager. I can't move my backup files to the device after a format. This is very discouraging. Love the ROM, but I can't enjoy it unfortunately. Hope it gets fixed.
[Galaxy Tab S Android Development] TheBashar:
Could you please detail exactly which steps you took to stop the crashing. My T700 is having that problem and I can't seem to figure out the magic order of wipes and installs. I've tried both the open-gapps and the benzo that someone else said worked for them.

Thanks!
[Galaxy Tab S Android Development] dknk99:
After following the install instructions:

I let it boot up to initial setup, Google services crashed

Shutdown via power button

Start up to recovery (vol up - home button - power)

Wiped Dalvik and cache

Install rom

Install opengapps

Install SuperSU

Wipe Dalvik and cache

Reboot system

Pretty sure that was the order
[Galaxy Tab S Android Development] TheBashar:
Thank you very much! And thank you Kholargol, I just found your post here.
[Galaxy Tab S Android Development] peterpan07:
Hi guys

First looks like nice Rom for our t805.

I did try the Rom for bit more then 24 hours and decided to go back to the iron Rom I used

Problems I run into was, all the apps i am usually use seem to use more cpu power what resulted in an higher temperature of the device

It's also was shown by a shorter usage of the devices cause battery was gone after 2 hours where I usually can use the tab up to 6 hours

Does anyone have the same problems and possibly could solve them?

Other thing, an easy to follow change log would be nice

Thx
[Galaxy Tab S Android Development] TheBashar:
A quick note for any other T-700 users out there. Enabling device encryption soft bricks the tablet. Some googling suggested it is an incompatibility with SuperSU. I reloaded everything without rooting and sure enough the device encryption worked without issue. I haven't tried it yet, but there might be a workaround detailed here.
[Galaxy Tab S Android Development] meboy:
Just my experience with this on my T700:

It was a bit tricky to install. Had to get the sequence right. Basically did the same steps twice I believe. (coming from Ironrom)

Really no other issues for me with my limited use of this tablet.

Not getting video play issues with vlc or youtube as some have mentioned. But I don't watch tons..

Battery life is roughly the same as Ironrom. Not worse at all that I can tell.

Speed is drastically improved.

I'm not happy about the way MM handles sdcards but that's another thing.

The notification bar acts a little strange. Sometimes it's top right, sometimes left, center. I'm using Nova.

The new brightness settings in MM are a little weird. Use the widget to see what the settings are for the ambiguous icons.. I can't find detailed info in settings. But again this is just MM.

Nothing else for my use. Some others have mentioned legit issues in their use. But if you're getting force closes, error at startup, major video issues, battery life issues, heat, etc. it would seem it's related to your device and not the rom.
[Galaxy Tab S Android Development] brycegreen:
Notification bar depends on where you swipe down on the screen. It's not moving on it's own.

I'm having a few issues with reboots while transferring files. Been told it's just due to the Aplha state of the ROM. The SD card sure is annoying. I.e., If your card is formatted as portable. Titanium Backup will not recognize your backups in the folder.
[Galaxy Tab S Android Development] Kholargol:
You're welcome! :)
[Galaxy Tab S Android Development] TheBashar:
I've found that "Star Wars: Galaxy of Heroes" also crashes unless you use the developer option to force 4X MSAA. With it enabled the game plays fine but there are irregularities with reflections or transparency, which thankfully are not too common in the game:

[IMG="Screen Grap"]https://lh3.googleusercontent.com/TYgfbeI9LO9pyUyFbjPo35UtUf73N27yiK_L_CUQF0fQxCIMCuD-W5kPJcXaMABgeTTT2ht7nTAAMnznP08xZJIUSyqQe-WeqcOha85m--gjC7FULKHDPFC77kd4tVoxhLHZqjAW5vOy8071nhtR7nBjAUAY04TfVTwbSwTI-S7X-C3rFqH2SEgSSSyHuWDL5kFBznCyJKJqS495WtJoWS9UMZ3HJwZZziksmcXjor5e-QT7vrUl-x3FEi_-LM7hCCDVFRnEatdQPmjOPZIB40BGuw7kZ2xUQwXCrMSaYkFr6TEkkeCc-dbjXb5Vi-STdMTvfaSFbKQtarN26D9vbkFmaSbRJEbW-65ASMV30dM9ZcuYE5B0qJ5EE9gjX-CA3i0VgNd4QQ3cPlWVnd11Cv_L8FWjXV3Fk1-i5BsCq8zXqeM_Y2vp7gIqjnYQ4WFsvcN2c9TWyx_bUbtuTWywPbxVkg58YjjoK4U0aW1l4Tj0p1CcopjsHrj1U_B6kL6-6mRnJPkmQ91iSyYmAePKBRVvC7tX04J5C6tC6DsUwK8bZaREOrNnxLfvLAIXcfBYmFIlvQ=w800-h600-no[/IMG]
[Galaxy Tab S Android Development] meexx:
Hi, csn i use f2fs on this rom for dalvic and cache ?

Gesendet von meinem SM-T805 mit Tapatalk
[Galaxy Tab S Android Development] samwheat:
Hi, yes, you can !
[Galaxy Tab S Android Development] wbedard:
After seeing this post by [MENTION=3884654]TheBashar[/MENTION], I thought I would "take one for the team" and experiment with device encryption on the T800. Having previous experience with device encryption issues, I first took a full "nandroid" backup and also copied off the sdcard/media area, since removing encryption involves reformatting /data, which will wipe those areas normally left untouched by a factory reset.

With that out of the way, I first tried to just YOLO it and encrypt my existing configuration. Since I was planning on performing a full wipe and experimenting on a fresh device, I figured it couldn't hurt to try. As soon as I gave it the final confirmation to encrypt the device, it went to the boot animation (similar to a soft-boot action...) and just stayed there. After ~20mins, I forced it to reboot and, this time, it got a bit farther (lit the hardware buttons...) but didn't make it to the home screen after ~5mins. After another forced reboot, it booted right up and, as it turns out, it was like nothing happened (no data loss...). OK, enough with the preliminaries.

After booting to recovery and wiping the device, I flashed the 12/12 release of the ROM and nothing else (i.e. no GApps, XPosed, SuperSU, etc). After booting into the ROM, I ensured that USB debugging was enabled, setup an ADB session and started capturing a logcat. Then, I setup device encryption and gave it the final confirmation. This time, it went right to the "robot" graphic along with the status of the encryption process. Once it completed, it rebooted and I got the normal PIN-input interface for encrypted devices. At this point, I started another logcat to capture the boot process. After entering my PIN the device just sat at the boot animation for ~20mins before I forced it to reboot. This processed repeated again so I called it off and went about restoring my device.

I have attached the compressed versions of both logcats for referral by both the developer (Happy Holiday's [MENTION=2371134]Schischu[/MENTION] !) and any interested users. In the logcat covering the device encryption process, I have filtered out lines indicating "Encrypting from sector xxx" and "Encypted to sector xxx", which reduced the uncompressed size from 182MB down to less than 1MB. The logcat covering the post-encryption boot was cut back to just after the errors started repeating themselves.

For most users, getting device encryption working probably rates down there with getting SELinux working in enforcing mode. However, it is nevertheless important to the more security-minded users and that was my motivation for running this test and seeing where we are, at least on the T800 device. Please let me know if you have any questions/comments about how I tested or ways I could run this test better. I'm certainly up to it as new builds get released.

R/

wbedard
[Galaxy Tab S Android Development] TheBashar:
Apologies that I didn't actually read the logcats. Your results differ from mine in that without SuperSU the encryption worked with no problem. I'm wondering if the encryption was working and you didn't wait long enough. (I should read the logs). Or if it was failing, I wonder if some SuperSU piece didn't get wiped from the previous test. Once it was borked from my test with the rooted ROM, I did have to format (as well as wipe) the internal storage.

I wanted to touch on why having device encryption working might be important. Google can remotely unlock devices unless they use encryption.
[Galaxy Tab S Android Development] wbedard:
No worries, I haven't even studied the logcats in any great detail. I just wanted to go through the process and capture the data in case there was a problem, as your post lead me to think I would encounter. I am reasonably sure that the encryption process completed fine. While your comments could be interpreted to suggest that I didn't wait long enough for all the apps to get "optimized" during the first boot, experience has show this normally takes ~5min on my device and that's with a full load of user-added apps. Although the process could take longer on an encrypted device, it would probably be offset by the greatly reduced number of apps that needed to get processed in my test. However, the logcat shows that something was definitely wrong during the post-encryption boot. While I doubt that anything was left behind after I wiped the device, I was using Chainfire's systemless root solution provided by his most recent releases of SuperSU. I'm not that familiar with the details of how it operates but it would be unfortunate if it required more than a factory-reset and wiping /system to fully "uninstall" it. That followed by flashing the ROM I would think pretty much took care of vestiges of the previous setup. That said, I'll keep that idea in mind when I review the logcats in more detail.

Thanks for the follow-up comments on your experiences!

R/

wbedard
[Galaxy Tab S Android Development] dknk99:
Maybe you just needed to wait longer, Samsung says in it's encryption set up that it takes 1 hour or more for the initial phase. Try it again, plug in the device and wait....
[Galaxy Tab S Android Development] wbedard:
The actual encryption process on my device took under 15minutes. As I mentioned, once that completed (it indicated 100% complete on the screen...), it automatically rebooted. While Samsung may have a more complicated encryption process associated with Knox, etc, my test followed what a Nexus device would use (which I have several of...) where it's just encrypt-then-boot and you're done.

R/

wbedard
[Galaxy Tab S Android Development] x5c0d3:
I get to the step where I install the AOSP for my T800. This seems to work fine (but doesn't really take long, just some seconds). When I now want to reboot into recovery again TWRP warns me that no OS is installed and if I really want to do it. I do.. I install GApps (stock)... I even install SuperSU... when I now reboot to System I just get to the first Bootlogo and get stuck there (I guess because of the missing OS). I cannot reboot into recovery again. My T800 even doesn't get off. Its stuck. All I can reach is the download mode where I can install an old stock ROM that is on my PC. Doing so everything works fine again.

What am I missing? :(
[Galaxy Tab S Android Development] wbedard:
While it doesn't happen very often for me, I have seen that error in TWRP on my T800. While they're not always connected, I have also had instances where rebooting to System from TWRP would get "stuck" and not make it to the home screen. When this happens, I have been able to just press Home+VolumeDown+Power (hold for ~10secs) and it would reboot. Just for clarity, the VolumeDown button on the T800 is the one closest to the power button. In almost every case, this second boot would make it through to the home screen.

If you want to try it again, start with just the ROM w/o any additions (i.e. GApps, SuperSU, etc) in order to validate that the ROM is working on your device (i.e. not corrupted, etc...). Good luck and let us know how it goes!

R/

wbedard
[Galaxy Tab S Android Development] dknk99:
SM-T700, turned on device encryption with SuperSU installed, all good. No issues encountered during the process.
[Galaxy Tab S Android Development] TheBashar:
What version of SuperSU did you have installed? Thanks!
[Galaxy Tab S Android Development] dknk99:
The one from the first page, v2.50
[Galaxy Tab S Android Development] TheBashar:
Thanks! Strange that we had the same versions and such different results.
[Galaxy Tab S Android Development] Yo_MaMa:
Redownload rom
[Galaxy Tab S Android Development] x5c0d3:
Hi there! Tried again with no luck. My next idea was to reinstall the Bootloader even if I had Lollipop installed before. Tried so and wham, it worked. I don't know which Bootloader I had before but it seems to be the wrong one ;)

Is there a way to get back the "menu button"? On Lollipop I could hold the task window button (left of home) to get into the menu of titanium backup for example. This doesn't work now.
[Galaxy Tab S Android Development] Klaus20:
I tryed to install but there is an error message:

This package is for "chagalllte" device; this is a "chanallwifi"

E: Error executing ....

But my Tab is a "Samsung T805 Gal Tab S 10.5 LTE bronze"

Should I flash the WiFi Version ??

Regards Klaus
[Galaxy Tab S Android Development] Yo_MaMa:
Already discussed, this is due to wrong twrp installed. See first post
[Galaxy Tab S Android Development] Klaus20:
The first post means ... TWRP 2.8.6.2 or higher....

I think I have the right bootloader and TWRP ??

Bootloader Version: T805XXU1BOCC

TWRP Version .2.8.7.0
[Galaxy Tab S Android Development] NeWONEx:
Flash chagalllte version

And update your bootloader!
[Galaxy Tab S Android Development] Klaus20:
Wich Bootloader should I flash ??

T805XXU1BOJ1_Oct.5.2015_18.30.20.zip --> should I rename *.zip to *.tar

T805XXU1BOCC_BOOTLOADER.tar

T805XXU1BOCC_T805OXA1BOC4_DBT

In Odin 3.10 into BL ??

TWRP into AP ??

Regards Klaus

P.S.: So the first part is done --> T805XXU1BOJ1_Oct.5.2015_18.30.20.tar and twrp-2.8.7.2-f2fs-t805.tar
[Galaxy Tab S Android Development] meexx:
Hi, i use this Rom now on t805 and my wifi drops out in standby, is this a bug or give it an fix for that ? Thanks for this great work

Gesendet von meinem XT1092 mit Tapatalk
[Galaxy Tab S Android Development] NeWONEx:
Yup in BL but I think you should make it .tar by 7zip

And you can say first step is done you can
[Galaxy Tab S Android Development] 2stardiver:
Any upgrade news for Rom? If i surf longer with chrome it starts clocking about after 15min and after two times waiting Tab S just reboots and looses battery 10 to 40% depending how hot it is
[Galaxy Tab S Android Development] wbedard:
I have also mentioned this happening on my T800. While you didn't specifically mention your settings, this happens for me even with "Keep WiFi on during sleep" set to Always. Even taking Doze into account, I believe this is likely a bug given that the behavior runs directly contrary to this setting. Additionally, apps that conduct extended data transfers are now failing unless they can be configured to use a full wake-lock during the transfer.

In short, it's certainly not a deal-breaker for me but I do hope it's at least on the "to-do" list.

R/

wbedard
[Galaxy Tab S Android Development] TheBashar:
Here's some uninformed speculation. I don't think that setting (keep wifi on during sleep) has anything to do with Doze. Does your "extended data transfer" take longer than an hour? I don't think Doze kicks in until at least 1 hour after the screen goes off and the phone stops being moved. If you do have an "extended" transfer that takes longer than an hour, try adding that app to the Doze whitelist. That way you can rule it out for sure.

You can read more about Doze and (the less known) App Standby that were introduced in Marshmallow:

http://developer.android.com/training/monitoring-device-state/doze-standby.html
[Galaxy Tab S Android Development] wbedard:
Here's some more uninformed speculation back atcha! Yeah, I know the WiFi sleep setting isn't connected to Doze...I probably could have worded that a bit better. I was trying to convey that with the new Doze infrastructure running in the background, it shouldn't alter the functionality of the WiFi sleep policy, as described in the interface. In other words, no matter what Doze is set to do, if I have WiFi set to never sleep then Doze had better not be doing something to affect that.

My uninformed speculation tells me that Doze is mostly about slowing down the rate at which apps and services make data requests but, as warned, I have not read up on it in detail. It wouldn't surprise me to find that Doze does save some power by powering down radios since this is such "low hanging fruit." I can see it being a "bug" in Google's code if they haven't fully reconciled Doze functionality with "legacy" settings such as the WiFi sleep policy. But again...that's all uninformed speculation on my part.

The extended data transfers that I referred to will get interrupted if they're any longer than a few minutes. Even Play Store app updates are regularly interrupted. The typical scenario is that I have several updates available so I tell it to Update All and then put the device down. When I pick it up ~10 minutes later to see what has been changed in some of the apps, Play Store is still downloading. The obvious sign that this behavior isn't normal for this scenario is that, when I wake my device and before I enter my PIN, I can already see the WiFi icon is a white unfilled outline meaning that it's asleep.

Again, this is more of an inconvenience than anything and just part of using a young ROM day-to-day to uncover the issues that still need some attention by the dev.

R/

wbedard
[Galaxy Tab S Android Development] suviralu:
Did you got TWRP using the link on the first page? The 'official' one give that dreaded error on our sm-t805.

sent from my sm-t805
[Galaxy Tab S Android Development] Klaus20:
With "twrp-2.8.7.2-f2fs-t805.tar" and "T805XXU1BOJ1_Oct.5.2015_18.30.20.tar" everything is fine.

Where can I find the "Advanced Restart menu" (switch off, restartr or restart into recovery or Downloadmod)

When I use the extSD for the first time it asks to chose Portable or Internal storage mode.

But in both Mods MM want to format the SD is this normaly ??

If anyone is interested - http://xdaforums.com/galaxy-s2/general/features-marshmallow-episode-1-using-t3279838

[MENTION=2371134]Schischu[/MENTION]

Thank you for the ROM

Regards Klaus
[Galaxy Tab S Android Development] wbedard:
That feature is not provided by Google in the AOSP codebase. Although there are probably several solutions that add this feature, I use Xposed along with GravityBox.

R/

wbedard