yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S Original Android Development] interfreak:
A couple of issues I've noticed on S2R2 after a quick play:

* Recent apps physical button does not vibrate, back button does

* Physical keys are still active after the screen is off

* Camera obviously non functional

Other than that, it does feel a bit more responsive and smooth. :) Fantastic work as always eousphoros!
[Galaxy Tab S Original Android Development] CrashTestDroid:
That would save me sooooo many headaches. It's painful to watch videos on the Tab S because my finger or thumb inevitably triggers one or the other hardkey.

Thx [MENTION=2346758]eousphoros[/MENTION] for the option of disabling hardkeys!
[Galaxy Tab S Original Android Development] eousphoros:
Looks like s2r3 will include theme support thanks to CM.
[Galaxy Tab S Original Android Development] Sporbillis:
Hey [MENTION=2346758]eousphoros[/MENTION] , really glad you are still trying to update this rom and make it as bug free as possible. What i didn't understand though ( haven't yet flashed it, was too busy ) is what hardware functions are not working? Buttons never shut off? and camera not working? Thanks again for building great rom! ( will flash soon )
[Galaxy Tab S Original Android Development] robson2222:
I had a strange situation with your ROM or kernel. I changed governor and chose performance. Then I locked my Tab and when I wanted to unlock I couldn't. I thought it was caused by turning the virtual buttons on and physical buttons stopped working. Unfortunately I couldn't reset my Tab too. The device didn't react inspite of connection with PC or a charger. I was afraid that the CPU or MOBO was damaged by overheat or something like that. Fortunately I pushed power button once again and Tab began to work again.
[Galaxy Tab S Original Android Development] eousphoros:
#include <std_disclaimer.h>

/*
* 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.
*
*/

That being said I haven't tested the performance governer, I primarily use interactive. Nor have I experienced the issue you described. If you have any logs that might be relevant I will take a look.

S2r3 is baking now. Disabling hardware keys now works from setting. App switch button now vibrates. And themes.. Omg themes!
[Galaxy Tab S Original Android Development] :
Gobernor performance does nothing else than locking all cores on the highest ppssible freq. I'm not quite sure if there is deepsleep support in performance. All optimazation regarding performance and battery life are for interactive and omdemamd (depending on which branch of my kernel git you are using).

That said there are some conclusions:

- Try interactive or ondemamd if you want a good balance between performance and battery life.

- I you use interactive, use it temporary and switch it back to interactive or ondemand after the usecase for performance has done.

- performance (while in use) has an other major draw back: 'cause you run cpu at max, thermal dripping is kicking in even if your task is not usimg much cpu cycles.

Considering that I think there is no need to debug performance. But that's only my oppinion. [MENTION=2346758]eousphoros[/MENTION]: if youmwant to debug performance take a look at the futex/mutex commits in [MENTION=3511708]UpInTheAir[/MENTION]s git as well as in [MENTION=3857343]crpalmer[/MENTION]s git - that's were I would start... The other point I would look in is interaction between performances freq max out and deepsleep.

---------- Post added at 07:45 AM ---------- Previous post was at 07:37 AM ----------

For those user, who want to use onscreen navbar: to disable capacative buttons issue the following commands in a shell:

su -
echo 0 >/sys/class/sec/sec_touchkey/touchkey_enable

Or wait for next release. Remember to repeat this after each reboot.

If you want to disable onscreen navbar and reenable capacitive buttons go to settings disable onscreen navbar and reboot (without above shell commands).
[Galaxy Tab S Original Android Development] moneytoo:
[MENTION=2346758]eousphoros[/MENTION] Seems like your profile for T700 has wrong power profile, just like https://github.com/barracuda7/android_device_samsung_klimtwifi/pull/1/files
[Galaxy Tab S Original Android Development] eousphoros:
I was having so much fun last night (and the baby was refusing to sleep) I cranked out a couple bugfixs and performance tweaks.

GPS improvements

Camera rotation and distortion fixed

Stereo audio and microphone

Graphic performance improvements

Latest sync of CM-12 tree

Updated link in first post.
[Galaxy Tab S Original Android Development] eujene:
installed the latest build. incredible!

a few moments: recents hardware key is not working, mtp is not working too. everything else seems to be okay
[Galaxy Tab S Original Android Development] eousphoros:
Glad you like it. :) yeah the recent app switcher button thing is weird. Its like its ignoring my gpio definition for that button.

Added mtp to the list of things to fix. Thank you.
[Galaxy Tab S Original Android Development] hassan_1000:
This isan amzing rom and stable enough for me!! Wonderful work! I want to download the 7th December build few questions, can I dirty flaSh, if so do I need to reflash gapps?

Edit my first flash was through twrp BTW with no issues
[Galaxy Tab S Original Android Development] eousphoros:
I did a dirty flash from release one to release two. Gapps remained intact however your mileage may vary and likely won't always be the case in future releases.
[Galaxy Tab S Original Android Development] NJ_RAMS_FAN:
great looking rom. I did noticed that 5ghz wifi band is not being recognized. From my G3 experience, this is a CM issue that fixes it self. But so far nothing. still doesn't find it.. not a big deal, but just thought I let you know..
[Galaxy Tab S Original Android Development] danny19901:
Downloading now great job
[Galaxy Tab S Original Android Development] eousphoros:
Release 3 is up.

The good:

Using [MENTION=4193974]Barracuda77777[/MENTION] 's klimtwifi kernel with a couple tweaks. This fixed a couple issues out of the gate.

MTP is now working

Samsungs book case cover toggle is now working

Boot time is improved

Kernel compiled with gcc 4.8

I was hoping to get the recent apps button working but my wife is cutting me off for the weekend.

The bad:

Dirty flash is no go. This will require a factory reset. Sorry guys, I'll try to keep this to a minimum.
[Galaxy Tab S Original Android Development] danny19901:
Oddly v2 I can't get to flash with TWRP or CWM CWM gives a load of recovery log errors as soon as entered
[Galaxy Tab S Original Android Development] eousphoros:
Weird, looks like you may have bad flash or a non-standard partition layout. Not sure what to suggest except maybe using odin to flash to stock and then back.
[Galaxy Tab S Original Android Development] danny19901:
I'm not sure I'm downloading V3 also formating system and cache fixed them errors but I'm getting errors when flashing towards end I will try flash V3 hopefully will work
[Galaxy Tab S Original Android Development] eousphoros:
Any luck?
[Galaxy Tab S Original Android Development] IcedCube:
Who deleted my post? :confused:

With every update I'm grtting more hyped with this ROM. Might test it out this week.
[Galaxy Tab S Original Android Development] eousphoros:
Not me, though to get you more hyped I just scored almost 39500 in antutu benchmark
[Galaxy Tab S Original Android Development] Barracuda77777:
gaming is now in par with samsung rom, this is looking very promising!
[Galaxy Tab S Original Android Development] inchrist1:
Thanks for CM12 on the TAB S
[Galaxy Tab S Original Android Development] Bluehacks:
THanks a lot dev! Amazing work- i m looking forward for a test drive!
[Galaxy Tab S Original Android Development] open1your1eyes0:
[MENTION=2346758]eousphoros[/MENTION] and [MENTION=4193974]Barracuda77777[/MENTION], you guys are amazing for working together on this! Let's show these tablets with the best displays of all tablets what they can really do! (long live AMOLED!) ;)
[Galaxy Tab S Original Android Development] kevman8396:
Noticed Netflix has audio but no video
[Galaxy Tab S Original Android Development] hhairplane:
Hoping this will eventually turn into an official build...
[Galaxy Tab S Original Android Development] interfreak:
Another issue I've noticed today, I appear to have lost root access with S2R2... Anyone else have this issue?

How do I get it back?
[Galaxy Tab S Original Android Development] casasroldan:
In s2r1 and s2r2 I has to flask supersu after flashing ROM.

No problem, you just has to remember it.
[Galaxy Tab S Original Android Development] Enddo:
CM12 recently moved root into the Developer Options menu. Are you able to enable it in there?
[Galaxy Tab S Original Android Development] interfreak:
This did not work, but..

..this did!! Thanks, I didn't even think to look under developer options lol! :)
[Galaxy Tab S Original Android Development] Enddo:
Awesome. I'm happy to help :)

CM's new changed root feature also puts a bash symbol(number sign) in the top right of the status bar whenever an application is actively using root. So if you give root access to battery stat apps or even a kernel apps, then the sign will always be up there
[Galaxy Tab S Original Android Development] kisypher:
Does Netflix still not work?
[Galaxy Tab S Original Android Development] dancress:
works for me with the new release, even with HW overlays unchanged. as does any other video.
[Galaxy Tab S Original Android Development] mordeith:
link for gapps ?..or did i scroll passed it ?:o
[Galaxy Tab S Original Android Development] thejase:
This bash symbol bothers me. I can see a reason to have it for certain situations, I just wish you could turn it off if you didn't want it. Enough clutter for me at the top as it is.

---------- Post added at 10:20 AM ---------- Previous post was at 10:16 AM ----------

As in theme chooser? System themes?
[Galaxy Tab S Original Android Development] dcshoes23:
Hi, I have a feature request, could you enable "Loadable module support" for the kernel? I am trying to load xpad.ko so that I can use my Xbox 360 controller with the tablet.

Thanks for all of your great work, your ROM is of such high quality!
[Galaxy Tab S Original Android Development] Enddo:
Yes, the latest CM12 nightlies have the Theme Engine built in. CM11 themes will not work though. They will have to be specifically designed for CM12(for now)
[Galaxy Tab S Original Android Development] kchinth:
The link I used to download mine isn't working now, but just google "gapps lollipop" or something like that and you'll find it. The name of the file I downloaded was "gapps-lp-20141122-signed.zip".
[Galaxy Tab S Original Android Development] eousphoros:
Sorry with the delay of s2r3. I found an issue with disabling the keys that could cause of soft brick of the cypress touchkey. S2r2 shouldn't be affected.
[Galaxy Tab S Original Android Development] kev0153:
wow this thing is fast! thanks
[Galaxy Tab S Original Android Development] jewnersey:
[MENTION=4405529]nvertigo67[/MENTION] : and would it be alright if I too use the kernel? UpInTheAir, had already given me permission initially to use his CM port repo

[MENTION=2346758]eousphoros[/MENTION] : can you share your defconfig please
[Galaxy Tab S Original Android Development] eousphoros:
s2r3

https://blck.io/cm-12-20150121-UNOFFICIAL-klimtwifi.zip
[Galaxy Tab S Original Android Development] Enddo:
Heeeeeey, where's the themes? :confused:
[Galaxy Tab S Original Android Development] eousphoros:
Settings -> personalization -> themes
[Galaxy Tab S Original Android Development] Enddo:
I only have Status Bar in the Personalization section of the Settings. I did a clean flash too

Oh wait, I think I installed the wrong zip lolol

my bad. very very sorry

edit - Bravo on the new release. Everything looks good so far. I'm even able to watch videos on MX Player without disabling the hardware overlays. As always, thank you for all of the hard work you have put into bringing CM12 to this device
[Galaxy Tab S Original Android Development] open1your1eyes0:
Very nice update! I feel like this build is a little more stable even than s2r2. :)
[Galaxy Tab S Original Android Development] qcjulle:
Sorry if I'm hijacking the thread but I've been following the T700 development even though I'm a T705 owner. What is unclear to me is that what is the reason for not having CM11/12 for the LTE variant? Is it just lack of development/testing devices or is it due to the external Intel LTE modem?

I already got burned with the lack of SW support for the previous Samsung AMOLED tablet P6800 so did I do it again? :D Even after freezing most of the bloatware and installing Nova this tablet still lags unacceptably. At least Dell has an AMOLED tablet coming out with probably the same screen so this will be my last Samsung tablet unless there is a working CM rom or the Samsung Lollipop update greatly improves things (doubtful).
[Galaxy Tab S Original Android Development] casasroldan:
Excellent release.

Capacitive keys disabled ok. Themes in its place. No need to flash supersu , enabled it in settings.

Video with VLC are perfect.

Only thing not working is the camera so no Skype.

Thank you very much.
[Galaxy Tab S Original Android Development] casasroldan:
Hello,

I think there is an issue with capacitive keys.

When the tablet is suspended for a long time, capacitive keys get back to work and you have to switch off and on the bar again in settings.

Other thing, Bluetooth headphones doesn't work pretty well. Sound is cut every second.

I don't know if this is new or it happened in previous releases because this is the first time I have tested.

Thank you for your great work.
[Galaxy Tab S Original Android Development] HobbitCy:
Installed smooth, only thing i have come across so far is camera doesn't work, tried google camera from store and a barcode app and they don't work either.
[Galaxy Tab S Original Android Development] fraser.dk:
Devs don't have the LTE variant therefore no dev support. Samsung will probably orphan this one soon but at least we have CM11/12 to fix the laggy stock TW behavior and nuisances like touchy hardkeys with ridiculously bright backlights.
[Galaxy Tab S Original Android Development] interfreak:
Thanks for S2R3 eousphoros, as mentioned it does seem to be ever speedier than R2! :D

Issues:

* Physical keys are still active after the screen is off

* Widgets sometimes don't appear when rebooted, I find rotating the screen makes them come back

* Camera obviously non functional
[Galaxy Tab S Original Android Development] killall:
+1 for the capacitive keys problem. After a while with the screen off, they are re-enabled
[Galaxy Tab S Original Android Development] eousphoros:
Sorry, thats as much effort as I am going to put into the "problem". Personally I am just going to call it a feature and be done with it. On that note s2r3 will be the last release till samsung releases an official lollipop for the device. If someone else wants to take over development feel free.

Just for clarification. I ended up stepping on my tablet today cracking it and effectively destroying it. Hence the sudden lack of interest.
[Galaxy Tab S Original Android Development] HobbitCy:
the other thing i found even though i had wifi off battery is reporting that it was on all the time and that it was awake all night : (

hopefully they release L so that development can continue
[Galaxy Tab S Original Android Development] casasroldan:
Thanks for your great job. You really made this device useful.

I hope Samsung shall eventually do their job and release a Lollipop ROM for our device.

Anyway, we'll keep and eye on this forum.

Thanks again.
[Galaxy Tab S Original Android Development] interfreak:
Thanks for all your efforts eousphoros!! If you get a new tab will develepments continue?

I'll probably shift across to BlissPop after they get the camera working.
[Galaxy Tab S Original Android Development] qcjulle:
So now is the perfect time to switch to the LTE version for further development! My $20 offer for CM to the SM-T705 is still valid :)
[Galaxy Tab S Original Android Development] dancress:
THANKS for your great work! And sorry for your loss. It's a fine little tablet and a shame to lose.

Q for everybody running the latest version: is it just me or does it seem to BURN through the battery? I can literally watch the battery counting down while it's on and it loses close to 40 per cent overnight when not plugged in. That's a total shame because I'd love to use this ROM but with 2 hours working time I can't.

The detailed battery stats aren't very helpful since it shows 2% display, 1% Android system and nothing else.

Could it be the hardware keys turning on and off every minute or so? Does this disrupt deep sleep? Could a full wipe after the dirty flash from S2V2 resolve the problem?
[Galaxy Tab S Original Android Development] danny19901:
Sorry to bother people but has anyone got this to flash on T705 ?
[Galaxy Tab S Original Android Development] interfreak:
Battery life is not good with this ROM, maybe try the BlissPop ROM as users are reporting extremely good battery life.
[Galaxy Tab S Original Android Development] killall:
Got to disagree, no complaints about battery life.
[Galaxy Tab S Original Android Development] interfreak:
Well, I've been running BlissPop for the last 12 hours, running exactly the same apps and I've noticed a significant improvement in battery life already. Try it yourself.
[Galaxy Tab S Original Android Development] Enddo:
Duuuuuuuuuuude!

I am so sorry to hear that :(

As always, thank you for all the hard work you have put into the device. I haven't had any issues with the buttons but I don't like them lighting up anyways, I disabled that 'feature'. The tablet runs so smoothly. I will report screen on time stats later. You really have turned my $500 regret into the exact tablet I was looking for before I bought it. I just can't thank you enough

---------- Post added at 10:31 AM ---------- Previous post was at 10:29 AM ----------

I think it's just you. I watched an hour and 11 minutes of video last night before bed and my battery is at 91% right now

---------- Post added at 10:32 AM ---------- Previous post was at 10:31 AM ----------

I have to disagree as well. I get 3-4 hours more of screen on time on this ROM than I did on stock
[Galaxy Tab S Original Android Development] eousphoros:
[MENTION=2779578]jewnersey[/MENTION] [MENTION=4405529]nvertigo67[/MENTION] I have updated my fork of your kernel with the touchkey interface and the klimtwifi defconfig I am using if you want to pick the commit its all yours. :)

https://github.com/eousphoros/andro...mmit/e69f10b6839cfe125413e8d9b09caaa5f71775cc
[Galaxy Tab S Original Android Development] jewnersey:
thank you very much

does Mic work in these builds?
[Galaxy Tab S Original Android Development] eousphoros:
Last time I checked. I hear camera is working too. So this weekend I am planning on putting together build instructions and doing a new build. Though I won't be able to test it so you friendly users will have to take a little more risk if you choose to use it.
[Galaxy Tab S Original Android Development] dknk99:
Hello, would you be willing to give out your build info for this?

I have the cm-12 repo synced, I think I just need your local_manifest.xml GitHub info in order to build for the Samsung SM-T700?

Any other tips would be nice as well. I'm new to this (android dev), but spent many years as a Linux admin.

Thank you for any help.
[Galaxy Tab S Original Android Development] eousphoros:
As I mentioned in my previous post when I recreate my build environment this weekend I will also be putting together documentation in the first post. Cheers from a fellow linux admin. (Though be prepared, those skills are not really transferable to android in any significant way.)

EDIT: Little spoiler, a couple exciting things are developing now that I am looking forward to sharing soon. :)

1st bit of exciting news. [MENTION=639045]miscom[/MENTION] has just put in the mail a replacement t700 which should be here in about a week so I can continue active development. 2nd bit of news is still in progress.
[Galaxy Tab S Original Android Development] Enddo:
This is amazing news! I have recently switched to Ubuntu so I can build nightlies for the G3 and N5. If you release the local manifest details then we could use those to build nightlies as CM12 development progresses. . .right? :fingers-crossed::fingers-crossed::fingers-crossed:
[Galaxy Tab S Original Android Development] eousphoros:
The local_manifest is basically the picassowifi local manifest but with my device repo and a local blob vendor directory that I don't have checked into git at the moment.

As for nightly builds that is related to my #2 news. I am just waiting to hear back.
[Galaxy Tab S Original Android Development] Enddo:
An official nightly, assuming that is what you are hinting at, sounds awesome.

Do you have the picassowifi local manifest or have a link to where I can get the full text?
[Galaxy Tab S Original Android Development] eousphoros:
brunch picassowifi

should grab it for you.

And I guess I was a bit obvious. I have begun the work to transition to official.
[Galaxy Tab S Original Android Development] kisypher:
That's GREAT news! Really appreciate your work on this. [emoji106]
[Galaxy Tab S Original Android Development] Enddo:
Is it really that easy?

I don't need a local manifest with something like this. . .

<manifest>

<project path="device/lge/g3-common" name="CyanogenMod/android_device_lge_g3-common" remote="github" revision="cm-12.0"/>

<project path="device/lge/d850" name="CyanogenMod/android_device_lge_d850" remote="github" revision="cm-12.0"/>

<project path="kernel/lge/g3" name="CyanogenMod/android_kernel_lge_g3" remote="github" revision="cm-12.0"/>

<project path="vendor/lge" name="TheMuppets/proprietary_vendor_lge" remote="github" revision="cm-12.0"/>

<project path="device/qcom_common" name="CyanogenMod/android_device_qcom_common" remote="github" revision="cm-12.0"/>

</manifest>

. . .but for Samsung details? Or are you telling me that I need to find out what the picassowifi local manifest details are before I start the build process?
[Galaxy Tab S Original Android Development] eousphoros:
That is how I get my initial local_manifest
[Galaxy Tab S Original Android Development] Enddo:
Thanks for that tip. I never knew since I have always used manual local manifest files and never used the breakfast command at all.

So after I do the breakfast picassowifi command, I can then run the brunch picassowifi command to start the build?

Will it will be the same builds that you have been putting out or will they be bug ridden?
[Galaxy Tab S Original Android Development] mrcet007:
Wow thats great news!!! Thanks a lot for the great work!!
[Galaxy Tab S Original Android Development] eousphoros:
Not quite, you still need to update the local manifests to pull my kernel and device repo. If you can hold off I'll have this all documented soon. It will also get easier after we go official
[Galaxy Tab S Original Android Development] Sporbillis:
What ?? You just made my day. After you stepped on your tablet i was seriously was going to sell mine on ebay. Now you are telling us official cm12?? That's awesome news. !!
[Galaxy Tab S Original Android Development] eousphoros:
Having a very kind person send me a replacement tab has changed my mind on officially maintaining the cm12 port for the t700. Also now that the last sensor is working we can actually submit our port. Keep in mind this will probably take at least three weeks. Crpalmer has been helping me with the logistics since this is my first time. I'll keep everyone updated as we progress.
[Galaxy Tab S Original Android Development] kisypher:
Sounds great, keep up the great work. Really appreciate your efforts!
[Galaxy Tab S Original Android Development] eousphoros:
I have begun the documentation in the first post.