yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S Original Android Development] SS2006:
Hi. Is this safe to flash alongside twrp now?
[Galaxy Tab S Original Android Development] UpInTheAir:
No idea about the benchmark, I'm still away working and use tab only to watch movies before sleep. No time to play. GUI smoothness may have nothing to do with benchmark.
[Galaxy Tab S Original Android Development] UpInTheAir:
Development is still suspended and release version 0.6 is same as last month. What doesn't work then still doesn't work now..... If you want to use it, you'll need to flash stock recovery after, otherwise wait until I fix some bugs when I'm home and have time. :)
[Galaxy Tab S Original Android Development] mitchellvii:
Yes benchmarks have always been a bit dubious in nature and as we have learned to Samsungs discredit, can be manipulated to an extent. What really matters is how does the damned thing run? That's why my curiousity for the embedded video lack of performance. It is the one thing which is truly awful on these devices.
[Galaxy Tab S Original Android Development] Enddo:
It's posted here - http://xdaforums.com/showpost.php?p=54662814&postcount=187
[Galaxy Tab S Original Android Development] mitchellvii:
That is exceptionally high for this tablet running stock. Can you replicate it? May have just been a one off result. That or you got the fastest ram, cpu and gpu ever built on this rig :) Antutu can give weird results. I can run 2 benchmarks right after each other and the second one be 2000 points higher than the first when it should be lower due to throttling from heat.
[Galaxy Tab S Original Android Development] Enddo:
Testing again right now

36,333 with regular AnTuTu this time :)

All I have done is loaded Google Now Launcher and frozen as much bloat as I could. And I went through the Settings and disabled all the Samsung/TouchWiz gimmicks like gestures and stuff. Trying to get it as close to Nexus/Stock Android as possible.
[Galaxy Tab S Original Android Development] mitchellvii:
All I can say is you lucked into a very fast rig there :) Those numbers are crazy high.

---------- Post added at 04:51 PM ---------- Previous post was at 04:31 PM ----------

Just installed Google Now Launcher. Am running EMSpilot's rom debloated. Just got two scores of LESS THAT 32,500. My scores actually FELL by 2000 points with Google Now. I would think I got a bum rig except that my numbers are completely normal compared to other benchmarks posted online.

Weird. Your T700 is destroying mine by every metric. I still don't see how you can be cranking out 2000 points better than my fastest run and 4000 points better than posted internet benchmarks.

What do you mean by "regular" Antutu? I'm running Antutu 4.0.

---------- Post added at 05:04 PM ---------- Previous post was at 04:51 PM ----------

Ok, got a 34862 running Nova Launcher with DVFS disabled fresh reboot. Lol. think that's all she is gonna do. :)
[Galaxy Tab S Original Android Development] Enddo:
regular AnTuTu is 4.0, like you're using. If you search AnTuTu X, that will pull up the beta.

OEMs like Samsung 'cheat' on regular AnTuTu. Sometimes they will disable thermal throttling to get the higher scores.

So people have been using AnTuTu X to bypsass this tactic. The loading screen for AnTuTu X says it's version 5.0

Oddly enough, I'm getting higher scores on AnTuTu X. I just got 39,291 with that app
[Galaxy Tab S Original Android Development] Stupid1337deer:
I haven't yet tried the x version. Will after this post. I was able to achieve this score after having the device unknowingly on an AC airvent.
[Galaxy Tab S Original Android Development] Enddo:
Nice. When I was doing my test it was on a generic tablet stand. I hadn't used it for about an hour so it would have been in a neutral state as far as temperatures go. It's good to see other Tab S tablets getting good scores like this
[Galaxy Tab S Original Android Development] UpInTheAir:
Do these benchmark tests in any way to this kernel development ? ;)

On a side note, I'm home later on this week and will start to take a look at things.

Also will be building kernels for the 10.5" providing I still have a willing beta tester ?? Heard you ditched the 10.5 ??
[Galaxy Tab S Original Android Development] mitchellvii:
My GF inherited the 10.5 and I picked up an 8.4 to see if I would like the smaller size better. But I'm sure there will be willing testers over in Shaheer's thread. :)

---------- Post added at 06:02 PM ---------- Previous post was at 06:01 PM ----------

Wow that is an incredible.score. Are you running the overclocked kernel?
[Galaxy Tab S Original Android Development] UpInTheAir:
I'll take a look over there and look for someone (profile) with experience and able/willing to give decent feedback etc. Not having the device, I can't hold their hand for every step or eventuality. ;) If not, more time for me. I haven't really looked into anything much due to my busy lifestyle :)

I'll probably look at my own 705 ROM, with just a few mods I want. Thinking I will keep it odexed (less RAM usage). I might release with Aroma de-bloat options but IF I do, I won't support it. Just a personal ROM and sharing the spoils. :) Thing is that I'll only have a few weeks before busy again and have to catch up on family time too.
[Galaxy Tab S Original Android Development] mitchellvii:
Flashed your kernel without incident on my T700. Tried overclocking in Synapse to the max, 2100 and run Antutu. Temps almost immediately shot to 108C and crashed out. Amazing they got so hot so fast. Tried just doing normal things with the overclock in place but while temps remained normal, the oc would not stick and kept reverting to stock.

---------- Post added at 07:09 PM ---------- Previous post was at 06:54 PM ----------

Seems I can up the GPU to 677 and run Antutu without issue but any increase in CPU at all sends me to over 105C almost immediately. Even with GPU at 677 wasn't able to get above 35000. Have no idea how some users are getting these crazy high scores. Webpage loads seem a little quicker with the GPU at 677 but that could be placebo. Seems the tablet will remain stable at 2000 on the cpu and wont get hot at all, just can't benchmark.
[Galaxy Tab S Original Android Development] suzook:
I'm willing to test 10.5
[Galaxy Tab S Original Android Development] mitchellvii:
Ok, seems stable at 2000 on the cpu and 677 on the GPU. Using stock browser have to say webpage loads seems quicker. Things just resolve themselves faster. No heating issues.

UPDATE: Take that back. CPU overclock keep dropping back to 1900 stock. GPU seems to stick.

---------- Post added at 07:36 PM ---------- Previous post was at 07:23 PM ----------

Ok, set CPU at 2100 max, GPU at 677 max and Gov at Performance. We page loads are definitely faster, even with Javascript enabled. A little confused by the Synapse interface. Temps acceptable.

UPDATE: 2100 eventually crashed out. Not a heat problem just unstable.
[Galaxy Tab S Original Android Development] UpInTheAir:
Did you disable knox with SuperSU and are you using official firmware ?
[Galaxy Tab S Original Android Development] UpInTheAir:
Thanks, I'll be on touch end of week :)
[Galaxy Tab S Original Android Development] mitchellvii:
I'm running EMSpilot rom and be has Knox off by default.
[Galaxy Tab S Original Android Development] UpInTheAir:
118× T700 DL's and no real feedback. Although essentially same between T700 and T705 (modem isn't compiled in T700), I never had issues with OC.

Another user (presume had official firmware) had issue with OC not sticking. I advised to disable knox with SuperSU and was fine after that. Another reported instability at 2100, so was the device hardware itself.

I can only suggest to test with official firmware and knox disabled with SuperSU.
[Galaxy Tab S Original Android Development] mitchellvii:
Where exactly do I disable Knox in supersu? I don't see an option. I assumed since it was already taken out?

Just checked with titanium. No Knox.

Wonder why temps are going nuts when benchmarking?
[Galaxy Tab S Original Android Development] edan1979:
the option were usually shown on first run of supersu. but since the rom that you use are knoxless... so no worry there... if you use stock and root... you will see that message.
[Galaxy Tab S Original Android Development] mitchellvii:
OK well not sure as to why I can't seen to make a CPU oc stick. The GPU seems to stick just fine. The heat problem when benchmarking is also odd. No heat issue In normal use at all.
[Galaxy Tab S Original Android Development] mitchellvii:
Noticed that when tablet goes to sleep for more than a few minutes it won't wake. Only way to recover (from pretty scary black screen, no lights, no nothing) was to 3 finger salute into download mode.
[Galaxy Tab S Original Android Development] UpInTheAir:
Official firmware ?

Work or without book cover ? (One user reported something earlier about black screen but not confirmed by others with T700 or T705).
[Galaxy Tab S Original Android Development] slackerz_86:
With for mine... it seems underclocking it causes it too
[Galaxy Tab S Original Android Development] mitchellvii:
With rom based on official and no speed tweaks, just deodexed, zip aligned, etc. One time did it with cover closed and one time not.
[Galaxy Tab S Original Android Development] UpInTheAir:
I have no issue with OC or UC CPU or GPU on official rooted SM-T705 firmware without any other mods or book cover etc.

Can you please post a bug report for your issue. There is a separate section for this in the thread Web view tab.

Please post (at a minimum):

1. Device type

2. ROM & firmware version (official/custom)

3. EXACT method to reproduce

4. Root with knox disabled via which method (SuperSU or de-knox via custom ROM)

5. Enable logging in Synapse and gather logs saved to sdcard (at time of issue). I might have time to look or analyse if capable, there also might be others with more knowledge too.

6. Any other pertinent information.

7. Try rooted official firmware

8. Try older/newer official firmware

Without this minimum information, myself and others are unable to try and help. I am not a Developer and struggle to read minds too. I'll add to and amend the above list and post it as an agreement to download and flash. In future, I might make Aroma installer with this and disclaimer as well.
[Galaxy Tab S Original Android Development] UpInTheAir:
As I said, please report if you have any issues with official rooted ROM with knox disabled via SuperSU (nothing else frozen or installed etc). I don't have the capability to form a educated guess from a custom or modified ROM of a device I don't own. My previous post explains what is required. ;)
[Galaxy Tab S Original Android Development] pibach:
I have had the same issue ("black screen crash").

But could not replicate it again.
[Galaxy Tab S Original Android Development] revthanki:
Thanks for your work on this [MENTION=3511708]UpInTheAir[/MENTION], makes me look forward immensely to getting my Tab S tomorrow. I've not come across Synapse before so that's something I will investigate, primarily for its fast charging capabilities. I know that my MacBook Air is capable of outputting a lot of power from its USB ports as it can charge an iPad relatively quickly - much faster than standard USB protocols dictate. As I travel a lot, the ability to get juice quickly from a simple USB connection is vital - something that always frustrated me about the Nexus 10.

I'll be happy to submit bug reports and help with general testing. I might even pen a guide for Synapse. Thanks again.
[Galaxy Tab S Original Android Development] UpInTheAir:
Maybe better off waiting until I release a minor update end of week. Current kernel will require you to flash the stock recovery directly after. I just need to trim the size down for the boot partition. Will probably just change the zImage compression during compile prior to repacking the boot.img. The boot time will just be 1 or 2 seconds slower, but the image will be much smaller. I might even rebase on the International T705 firmware instead of the current T700 source.
[Galaxy Tab S Original Android Development] revthanki:
Great, I'll hold off. Over the first few days I'm going to put the tab through its paces and make sure that the hardware is defect free before *gulp* tripping the Knox warranty bit. O Samsung, why? WHY? Why not make your security features optional for enterprises and allow the rest of us to use our devices in a reasonable way? I have no interest in Antutu scores, overclocking or pushing your thermal limits, I just want to make the software fit my needs. </endRant>

Cheers mate.
[Galaxy Tab S Original Android Development] mitchellvii:
Ok, flashed back to latest OTA from sammobile. Will run this up the flagpole again and see if we still get the same issues. What I am looking for:

1) OC sticks in Synapse.

2) No massive overheating when benchmarking.

---------- Post added at 07:58 AM ---------- Previous post was at 07:29 AM ----------

TEST RESULTS:

Running Antutu with kernel flashed and no overclocks resulted in VERY low scores. 30500 and 31500 (rounding) respectively.

Running Antutu with a 2000 cpu OC caused the heat spike to 106C resulting in a shut down.

Running Antutu with gpu OC to 667 resulted in freeze during the final animation sequence requiring reboot.

Cpu OC still not sticking.

So basically running stock rom with Knox disabled using SuperSU didn't fix any of the problems.

---------- Post added at 08:05 AM ---------- Previous post was at 07:58 AM ----------

Reflashed stock kernel and Antutu scores returned to normal: 34250 with no overheating.

Have no idea if the kernel is malfunctioning or Antutu is malfunctioning due to the kernel. OC's don't seem to cause heating issues when not running Antutu, but while the gpu OC seems to stick, the cpu does not.

---------- Post added at 08:53 AM ---------- Previous post was at 08:05 AM ----------

Interesting. After going back to stock OTA and stock kernel, this tablet runs smoother and faster than it did with custom rom and custom kernel. I think one thing we forget when doing customizations is the effect on how the whole ecosystem interacts together. There are so many little shared files and interdependencies we just can't possibly understand. By taking out one seemingly innocuous apk or file, you may be effecting 10 other things unknowingly.

Also, the effect of flashing a custom rom or kernel used to be much more pronounced when these devices were far less powerful. There is a bigger difference between going 80 mph and 50 mph than there is between going 180 mph and 150 mph. These new devices can simply overpower poorly optimized software (to a certain extent - lol, nothing can save the Touchwiz launcher).
[Galaxy Tab S Original Android Development] UpInTheAir:
Thanks for the feedback.

If you do have time, could you please flash back to earlier firmware base and repeat your efforts ? I'm still running T705XXU1ANF8.

Thing is works fine on my older firmware. Source may be in need of update/release from Samsung. I'm going to start fresh using the T705 source and not the T700 NA, may not make any difference though until international source update is released.

Yeah, I have posted previous info regarding the effect of OC. I don't personally see the need, but others love it :)

Your GPU OC issue may be related to your current problem. But thoughts are that your device hardware isn't stable at that frequency. You can only try push a little more voltage to it.
[Galaxy Tab S Original Android Development] mitchellvii:
I'm running the ANF9 firmware. Trying the original with it would be kind of pointless because even if it works I will want to upgrade and then the problem will persist. If you can get things sorted out with the newer firmware I'd definitely like to try it.

The overheating is odd though. Shouldn't see that kind of heat spike with just a small oc. Could be Antutu is going haywire somehow.
[Galaxy Tab S Original Android Development] UpInTheAir:
Not pointless at all. ....

Others had reported all working on earlier firmware for T700. The point is to determine (in your case and others) if it is/isn't related to the source itself. Maybe a source update from Samsung required for newer firmware. .... It happens

Edit: Also, there could be ramdisk changes from newer kernel that need to repacked into boot.img.

Edit: that's why I had added step #8 to the Bug Report requirements.

Let's try and narrow some things down. That's the point ;)
[Galaxy Tab S Original Android Development] UpInTheAir:
Okay, you hardly ever see me harp on about benchmark, but here is just a single run from device idle state. I'm sure i could squeeze a lot more because the GPU total was a bit lower than normal (usually 11200+ combined). I did not clear RAM or optimize the kernel values for my device or OC CPU fully etc.

AnTuTu Benchmark version 4.5.2

SM-T705

Official rooted firmware T705XXU1ANF8

No ROM tweaks, just a few apps disabled via settings and user apps with Greenify

SkyHigh kernel 0.6

CPU freq 200-2000 MHz

CPU volt -25 mV (200-1900)

GPU freq 100-677 MHz

GPU volt -50 mV (100-480)

All other kernel values at defaults (governor = interactive etc)

Device is stable and 99% lag free :)
[Galaxy Tab S Original Android Development] mitchellvii:
Interesting and no overheating issues either. Must be something in the latest update causing the problem because I could not even complete the benchmark with those values in place. How hot did your CPU get?
[Galaxy Tab S Original Android Development] UpInTheAir:
CPU temp did not exceed 90 degC at any time. Different (Edit: parts) of Antutu cause different stress and temp on CPU, so anywhere between 70-80+ (but did not exceed 90). Maybe during GPU test the CPU dropped into the 60's, can't remember.

Edit: I'm travelling home, so no time to play with things for a bit. My head is killing from lack of sleep. ...
[Galaxy Tab S Original Android Development] mitchellvii:
Ok, flashed back to original firmware.

Was able to overclock as you had here and it seems to be sticking. Also ran Antutu without overheating. Unfortunately my score was only 33242. I'm confused by this. Why are my scores so low?

UPDATE:Tried increasing cpu to 2000 - 2000 so 2000 would be minimum. Antutu caused cpu to immediately overheat and shut down.

Tried it again with your settings and Antutu just locked up. Could be the 700's and 705's are different in more than the obvious ways.
[Galaxy Tab S Original Android Development] UpInTheAir:
I don't know. Maybe CPU is a little inferior, Maybe kernel and ROM haven't let settle long enough, maybe partitions need formatting prior to flash firmware, maybe the device wasn't left too cool long enough, maybe test with other app. ..

Too many "maybe".

I assume you're using interactive governor or something else?

Setting max and min same can be counterproductive and invoke thermal throttling earlier as well as high OC and starting with a "warm" device.
[Galaxy Tab S Original Android Development] UpInTheAir:
Request for stock boot.img

REQUEST FOR STOCK BOOT.IMG

Could someone please post here their stock boot.img for:

T705XXU1ANG2

T700KXU1ANG1 or T700XXU1ANF9

I want to build with T700XXU1ANF7 source and test using the ramdisks extracted from the above boot.imgs.

If I don't get, you don't get ;)

Thank you :)
[Galaxy Tab S Original Android Development] edan1979:
T705XXU1ANG2 here it is....
[Wear OS Q&A, Help & Troubleshooting] TjPhysicist:
I'm getting an LG G Watch (btw, that's a seriously terrible name, its not too google-able) in a few days. Unfortunately my first major use for this watch will be whilst travelling out of country. So, here is my question:

What can Android Wear do offline? It will always be connected to my phone, but my phone will *Not* be connected to the internet most of the time. What about voice recognition? I know on my phone no matter what i do, offline I can only get it to accept the "call..." intent not even stuff like "open app" which doesn't need internet anyway.
[Galaxy S 4 Q&A, Help & Troubleshooting] paper13579:
Hey guys, i recently got a new Samsung galaxy s4 gt-i9505 and i want to root it. If so, do i need to unlock the bootloader first or do i just root my phone as is? Also can anyone link me directly to a thread where i can unlock the bootloader of my phone, thank you
[Galaxy S 4 Q&A, Help & Troubleshooting] paper13579:
Any help?
[Galaxy S 4 Q&A, Help & Troubleshooting] vpwrf:
The Samsung Galaxy S4 i9505 doesn't have a locked bootloader but rooting will void Knox warranty unless you use a method that doesn't. See http://xdaforums.com/showthread.php?t=2784433 to try and root without voiding Knox warranty.
[Galaxy Tab 3 Q&A, Help & Troubleshooting] LmObedoza:
After updating my sm-t211 to kitkat I can't find the developer mode, where can I find that? thanks
[Galaxy Tab 3 Q&A, Help & Troubleshooting] moonbutt74:
in settings about device

tap build number entry 7 times
[Galaxy Tab 3 Q&A, Help & Troubleshooting] LmObedoza:
thanks!

Thank you so much! :)
[AT&T Samsung Galaxy S 5] Heavy Metal:
http://samsung-updates.com/device/?id=SM-G900A

What caught my eye was to the right before area to download... the word UNLOCK...

???

SAMSUNG-SM-G900A, with 128gb SD & Rooted.
[AT&T Samsung Galaxy S 5] freebee269:
if you go to the site and look for sm-g900a in the list it is not there.
[AT&T Samsung Galaxy S 5] Heavy Metal:
Just downloaded it all inside the tar.md5 is a recovery img etc

Wonder if can use that? But the word UNLOCK has me curious?

SAMSUNG-SM-G900A, with 128gb SD & Rooted.
[AT&T Samsung Galaxy S 5] BigSexySCJCD:
Unlock? Wonder what is
[AT&T Samsung Galaxy S 5] freebee269:
the word unlock is just a link to a site for you to sim unlock your phone.
[AT&T Samsung Galaxy S 5] Heavy Metal:
Got it down was able to extract all from it. .. their is a recovery.img in it hmm wonder can I use it to recover to stock system etc and still retain root or not?

SAMSUNG-SM-G900A, with 128gb SD & Rooted.
[AT&T Samsung Galaxy S 5] shortydoggg:
I don't know what you're saying, but if you have safestrap, then you still have stock recovery too. Powering the phone off, then volume down + menu + power button will show that.
[AT&T Samsung Galaxy S 5] gabriel_dream:
It is the only firmware available for the 900A. Take a look at sammobile.com. The same change list. ..
[AT&T Samsung Galaxy S 5] shortydoggg:
And I keep trying to tell people that the firmware from Sammobile and Samsung-updates does not work on our S5 if you've updated to ND3. We must use the one from the general section, which is the same firmware, but different file.
[AT&T Samsung Galaxy S 5] GDofWR420:
S5 active here I downloaded my version of firmware from sammobile.com and it flashed fine. Just thought I would put that out there.
[AT&T Samsung Galaxy S 5] shortydoggg:
That's because you're still on that same firmware. You have not updated or received an update yet.
[AT&T Samsung Galaxy S 5] GDofWR420:
Oh. Sorry then yes that's correct. no updates yet but hopfully L is coming.
[Galaxy Tab 3 Q&A, Help & Troubleshooting] LmObedoza:
Will we get an update for android L?
[One (M8) Q&A, Help & Troubleshooting] 09eric09:
I know it's not recommended to restore system data when flashing to a different rom, but what if I'm just upgrading to a newer version of the same rom (newest nightly build)?
[One (M8) Q&A, Help & Troubleshooting] BenPope:
It would depend on what's been changed...

Take a backup and try it. Be sure to restore data, not system apps.
[One (M8) Q&A, Help & Troubleshooting] RoughNeck1971:
I'm also using TB a lot and trying here and there new ROMs. As long as you restore "Data only" you shouldn't have any problems. At least I didn't until now. Restoring the APP that way - I wouldn't recommend. I got issues very often like unmotivated reboots or APP just stops working after a while and so on. I would recommend do use APP Backup & Restore in combination with TB. After installing a new version of a ROM (mostly I do full-wipe) you can select the Apps you want to restore and they are running the installation process ! (so not just a recover). When I'm done with that I use TB to restore Data only. Didn't have any issues until now with that way. Hope that helps.