yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S Android Development] nishanta2006:
Tried both, internal as well as sd card

---------- Post added at 10:32 PM ---------- Previous post was at 10:27 PM ----------

I am running TWRP 2.8.4

---------- Post added at 11:04 PM ---------- Previous post was at 10:32 PM ----------

I have tried the TWRP uploaded by the developer here, still the same error.
[Galaxy Tab S Android Development] nishanta2006:
Finally got it to work.

But my laptop not detecting the device when connected. Enabled Mass storage and USB debugging
[Galaxy Tab S Android Development] xstatik:
i tried many times and still dont work here so i gave it up wait for the official
[Galaxy Tab S Android Development] Ts_sT:
i doubt there will be anything official when it comes to the t805 and cyanogenmod....

just use odin to flash the twrp version provided in thread op (no different version!), then boot into recovery and wipe everything (factory reset + manually wipe /system /data /internal storage /system and /cach), then flash rom, gapps and supersu and you should be fine.

edit: and please download the zip file again. like nvertigo said, it seems to be broken (maybe use a computer for download, just to make sure)
[Galaxy Tab S Android Development] nishanta2006:
What about USB? Anyone else facing problem connecting to computer via USB?
[Galaxy Tab S Android Development] Ts_sT:
confirmed.

this rom seems to have general problems with the usb port (no charging when turned off, no usb-computer connection).

AND i am pretty sure, though i cant really prove it atm - it charges very slowly. my tab is currently plugged in to power, but when i use it at the same time (clean build, almost nothing installed, except for es file explorer, titanium backup, xposed, greenify, better battery stats & amplify) its battery is constant or even decreasing...
[Galaxy Tab S Android Development] :
I'm still trying to explain people that Xposed is changing the rom to something completly different: xposed replaces art compiler, some frameworks and some system libraries. So after installing Xposed your NEW rom can suffer from any side effects that are not in control of the rom dev.

Don't get me wrong: I don't want to discourage anyone from using Xposed - but before reporting an issue you should reproduce it after clean flash and only gapps and supersu installed. And - of course - you should provide a detailed step-by-step discription on how to reproduce it and a logcat.

Short version: Xposed is NOT "almost nothing", but changes the entire rom to something new.

Perhaps you find this postings interesting:

http://xdaforums.com/showpost.php?p=58239877&postcount=3

http://xdaforums.com/showpost.php?p=58239877&postcount=2

http://xdaforums.com/showpost.php?p=59336710&postcount=561
[Galaxy Tab S Android Development] Ts_sT:
yes i know you are right. and this is why i flashed this rom at first without xposed - which gave me the same battery results. the problem i have atm is that i cant really prove it with numbers. so to find out where the battery drain comes from i installed xposed again and thus am able now to identify wakelocks more easily (using amplify for example).
[Galaxy Tab S Android Development] :
I use betterbatterystats. There's a free xda edition.

As stated: I don't want to discourage the use of xposed - but keep in mind the above.

As all the other information in my posting (particulary the parts on providing information and logcat) was not only for you. I just have taken your post as a hook. Hope you don't mind. I've following this thread, 'cause I try to help OP, who has stated that his time does not allow answering questions. But most of the posters here are not willing to provide sufficient information.... :(
[Galaxy Tab S Android Development] nishanta2006:
I did a clean install, no Xposed. Usb doesnt connect.
[Galaxy Tab S Android Development] :
No comment.
[Galaxy Tab S Android Development] pdolton2000:
The reason i believe if my understandings of roms and kernals are correct that there are problems with the laptop or pc detecting it is because of the kernal.,, the kernal has been originally used and designed for a t800...so there obviously are slight differences id imagine, but what ever they are rest assured they are being worked on.

Again youve been given advice that your power drain might be do to with the xposed distro...then again it might not, but to give you a bit more....you might be able to again suggest possibilities with the kernal needing more work as the xposed installers dont create battery drains on the t800 yet do on the t805, it could be that in the background certain system files that are being changed by xposed also work with the kernal...and because this kernal has been primaraly used on the t800 again its causing problems.

Please be patient things probably are being worked on but remember people have a lot to do in their own time and these things do take time anyway, so it could be weeks yet who knows.

[MENTION=4405529]nvertigo67[/MENTION] Hows my understanding of kernals...be brutally honest :) , if its all just crap then....well i tried lol
[Galaxy Tab S Android Development] :
No logs - no debugging - no fix.

I've never said Xposed drains battery - I said, xposed chances the rom to something different, no rom dev can support.

But you are right: instead of "expressing my self" I will use my time for something usefull. Thanx for pointing that out.
[Galaxy Tab S Android Development] eousphoros:
There is also no code available for this ROM that I have seen so that prevents others from helping as well.
[Galaxy Tab S Android Development] Ts_sT:
feel free to hook whenever you like :p

thats true. unfortunately i wasnt able to find any major source of excessive battery usage so far. unfortunately i just had samsung repair my battery one or two weeks ago. since then i have real trouble charging the battery of this tab again. so the reason might also be a faulty repair job by samsung....
[Galaxy Tab S Android Development] :
That's very sad, yes.

Since [MENTION=1636244]andyt12[/MENTION] stated he started off from chagallwifi code base, I belive the usb issue is not rom related - but thats just guessing, as long as we don't have logs.

(run out of thanx. :( )

---------- Post added at 09:19 AM ---------- Previous post was at 09:02 AM ----------

Can you check the time of of cpu states, please? I use cpuspy plus. And can you check partial wakelocks, also? On my manta play servives is preventing deepsleep and keeps the device most of the time at 400 MHz (instead of 200 MHz configured min freq).

(run out of thanx. :( )

For the powered off charging not working I'm quite sure it's a rom issue. It would be nice, if someone could save /proc/last_kmesg, after the reboot to recovery from powered off charging has happend. It's important to copy in the just boot recovery, 'cause it would be overwritten with the log from recovery itself, if booted to system from there. In twrp you can do this quite comfortable from Advanced->Filemanager.
[Galaxy Tab S Android Development] eousphoros:
Well one reason I bring it up is I know for klimtlte I had to work on the kernels defconfig to get it booting. It's possible some of the mtp stuff got messed up in that process. If we had that file (along with others) we could provide a peer review.
[Galaxy Tab S Android Development] :
If I should guess:

* cb7f25a - (vor 3 Monaten) enable CONFIG_USB_ANDROID_SAMSUNG_MTP again. — Nvertigo
* f1797d0 - (vor 6 Monaten) Compile stock and Samsung MTPs together [AndreiLux] — UpInTheAir

Reverting this two commits shouldn't effect mtp to win and linux machines - I don't know about others; I also doesn't think it effects charging - but who knows, everything is connected with everything....

An other piece of information that could bring some light to the usb connection issue, would be a look at win device maanager, when connected in mtp mode, as well when connected in ums mode. For writing in ums mode the rom deffinetly needs modifications to sepolicy:

git format-patch -1 --stdout current-12.0
From 35a7e8b64f4fdfd35fe5f7f226e6895cc3ef97f0 Mon Sep 17 00:00:00 2001
From: Nvertigo <nvertigo67@gmail.com>
Date: Sun, 8 Mar 2015 22:34:46 +0100
Subject: [PATCH] sepolicy: UMS: fix write access.

allow kernel and vold access to vold block files and sysfs files
---
BoardConfig.mk | 1 +
sepolicy/kernel.te | 2 ++
sepolicy/vold.te | 3 +++
3 files changed, 6 insertions(+)
create mode 100644 sepolicy/kernel.te

diff --git a/BoardConfig.mk b/BoardConfig.mk
index 4f761ca..5c30b37 100644
--- a/BoardConfig.mk
+++ b/BoardConfig.mk
@@ -151,6 +151,7 @@ BOARD_SEPOLICY_UNION += \
file.te \
gpsd.te \
init.te \
+ kernel.te \
mediaserver.te \
servicemanager.te \
system_app.te \
diff --git a/sepolicy/kernel.te b/sepolicy/kernel.te
new file mode 100644
index 0000000..fa9c9a9
--- /dev/null
+++ b/sepolicy/kernel.te
@@ -0,0 +1,2 @@
+# UMS: rw access to files in /dev/block/vold
+allow kernel block_device:blk_file rw_file_perms;
diff --git a/sepolicy/vold.te b/sepolicy/vold.te
index 7e83901..3e4ca77 100644
--- a/sepolicy/vold.te
+++ b/sepolicy/vold.te
@@ -1 +1,4 @@
allow vold vold_tmpfs:file create_file_perms;
+
+# UMS
+allow vold proc:file rw_file_perms;
--
2.0.5
[Galaxy Tab S Android Development] pdolton2000:
Lol i wasnt talking to you m8 I was talking to the guy I quoted?? The only bit that was to you was the last sentance where your name was fella??

I saw you tryna help someone, and decided to also tell them different possibilities, then just asked you at the bottom what your opinion was of my message to him....think this has got taken out of context slightly as there was nothing intended towards anything you said, actually everything youve said and say is always right lmao so i wouldnt ever throw a jibe at ya m8 :)
[Galaxy Tab S Android Development] :
Thanx. That's very interesting, 'cause I've seen that before - on my cm12 builds. On my cm11 builds sec-playlpm with proprietary sammy lpm binary this works flawlessly. Now we have reached the point, where I need to have a look at the sources actually used for the build. If I had to guess: lpm (or two libs lpm uses to display the animation) missing, or error in vendor tree makefile.

I'm still hunting for the play services wakelocks: seems to be a problem in interaction between some aosp based roms and latest play services. I will report on this topic, if I've found a solution.

---------- Post added at 11:30 AM ---------- Previous post was at 11:19 AM ----------

Read your posting again - had to wait till my tears of laughing had dried... Got it completly wrong. Perhaps it's a bad idea to debug two different roms, building a third and reading/answering postings at the same time... ;)

But everything has a good side: remembering to send debug info once is a good idea - begging (in one way or an other) for it is a waste of time; because the users who undersatnd will send logs and other info - after the first reminder, the others won't do it, beeing begged or not (not quite sure, about the last part of the sentence - but I'm sure you got the point).
[Galaxy Tab S Android Development] Ts_sT:
unfortunately, "the guy you quoted" does not even have the slightest clue in what way your comment could have helped him, nor did he gain any new knowledge about kernels, xposed or battery drains.

but thank you for briefing me on the fact that people also do other things in their lives than rom development. now i can see the world in a whole new different light.

and with that i hope the topic of your rude comment whoever you might have upset with is finished.

actually i spend some time last night on analyzing those wakelocks and there were only a few sources for the majority of the wakelocks and one of the biggest issues was indeed one service which was part of google play services....
[Galaxy Tab S Android Development] :
Wich gapps package do you use (exact date of package would be helpful)?
[Galaxy Tab S Android Development] Ts_sT:
i usually flash the latest pa pico gapps from here: http://xdaforums.com/paranoid-android/general/gapps-official-to-date-pa-google-apps-t2943900

with this rom build (03/07) i flashed this file: pa_gapps-modular-pico-4.4.4-20150221-signed.zip (obviously it was not the latest gapps package this time ;) )

and except for the chrome browser i did not install any other google services so far. as i said: i wanted to have the rom as clean as possible when analysing battery usage.
[Galaxy Tab S Android Development] :
Hmm, my idea was to use not the latest version... So you falsified my idea before you know of it... I hate you... ;)

What i will try now: delete data of play services, delete google account, reconfigure google account and reboot. Will report back later.

BTW: I found reports on this issue as well for cm11 as for cm12...
[Galaxy Tab S Android Development] pdolton2000:
Lol im glad thats cleared up, i was examining the kernal log he posted on here actually, and noticed part way down it refures to a driver status failure "power_supply sec-fuelgauge: driver failed to report `status' property" ...drivers as we know dictate how an os interacts with a device, wrong drivers cause incorrect instructions blah blah blah...but what exactly is the message refuring to....is it another clue maybe about the connectivity issues people are facing that all seems to be linked with the micro usb jack?
[Galaxy Tab S Android Development] :
Two diffrent issues: power off chaging is caused by not properly running lpm (sammy) binary - could be missing binary or missing libs, the binary uses for displaying - need a view on device tree and vendor tree to tell.

USB connection issue: I need in a first step a logcat. Ideally from a freshly booted device with mtp enabled and an other one from a freshly booted device with ums enabled. In a second step I need a view on device tree and kernel tree.

The first one is something "simple" (simple 'cause I know where to look) - the second one my be simple, but could be complecated, 'cause I haven't seen any logging about that... (Also: someone should have a look on both cases in win device manager.)

[MENTION=1636244]andyt12[/MENTION]: would be great if you could push your modification to a git server.
[Galaxy Tab S Android Development] pdolton2000:
I will get you your logcat for mtp and flash the rom now, i might even get you both if it goes smoothly, as for a view on device tree and kernal tree ive never heard the terminology before, im presuming its done in linux? If it helps considerably just tell me what to do and ill do it pal

EDIT

Ill also screenshot what device manager has to say :)

EDIT

Im about to upload the logcat file, theres a catch though , i cannot give you seperate logs for mtp and ums as i cant find a setting to change it to ums without first plugging it in and it has mtp enabled by default. Im not installing gapps or anything so it hopefully will make your log file smaller...the entries regarding the mtp and ums will be towards the end ill make sure of that much pal.
[Galaxy Tab S Android Development] pdolton2000:
Link to logcat file: http://www.mediafire.com/view/m1cxp77d1xic12u/Log_2015-03-13_19-25-38.txt

Line 19:24:06.809 is when I connected it to the laptop and it tried MTP

Line 19:24:36.834 is when I enabled UMS looking at it

Line 19:25:07.084 is when I enabled Connect as camera which seems to have same errors as MTP...guess theyre kinda the same.

Details relating to device manager for windows are as follows

MTP: One device appears in catogary:Universal Serial Bus controllers

SAMSUNG Mobile USB Composite Device

UMS: One Device appears in Disk drives

Samsung File CD Gadget USB Device

One device appears in Portable Devices

E:/

problem is when viewing the properties of the disk drive controller and trying to

make it populate the volume it refuses to, its like the tablet gives the laptop an empty memory card reader kind of.

PTP Camera

Showed up the first time in portable devices with an errror and something emplying there was a fault on the tablets end, something about the process hosting the driver has terminated, then later it showed up as my name followed by galaxy tab s after plugging it back in, then when i removed the driver to try and get the error message bacck it gave it a new driver just called MTP USB Device.

Hope all this helps someone lol...and yes i have just realised you can change the settings storage and select which connection you want so if you do want seperate logs let me know, but its all there mate.
[Galaxy Tab S Android Development] :
Oh yes it helps. First of all: the statement I've read so far was something like: nothing happens. So this is simply wrong.

Thanx for your detailed description. Can you confirm, that MTP is working after you deinstalled the win driber and win updated it on reconnect?

For mtp: [MENTION=1636244]andyt12[/MENTION], you need to cherry-pick the ums lun commit ( https://github.com/nvertigo/android...mmit/8e483e20ec424a3062ac3bbd9cd0e561c2c3c418 ) from current-12.0 branch. Perhaps you also need the commit https://github.com/nvertigo/android...mmit/35a7e8b64f4fdfd35fe5f7f226e6895cc3ef97f0 to enable write access to ums.

OT: ...hmm, formidable, I'll eat logcats for dinner... :lol: ...better then hotdogs... ;)
[Galaxy Tab S Android Development] pdolton2000:
Ive actually done some more playing around, I've uninstalled all devices and refreshed device manager and they all come up as what they were again and none working , except with the PTP camera, that shows up on the refresh as an MTP Device randomly and again does claim to be working properly, its only when the screen goes into standby it shows a yellow explanation mark with the error message mentioned earlier under PTP Camera section I made above, then if u unplug and replug the device the device claims to work pro0perly again....its like...and this will be technically wrong because I don't know all the correct terminology but...

Its like the locations of where the tablets built in drivers are looking for the storage volumes are incorrect, so when the laptop queries the tablet and says show me the goods, the tablet asks the drivers on the tablet and because they've got the wrong location info of the storage volumes it can't give the laptop what its asking, so windows can't access the volume in MTP as its just an empty card reader in its eyes.

ums can't work because again the tablets drivers internally are giving false info on where the volumes are, and so on.....

I mean take for example this line "03-13 19:24:49.659 2331 2500 E Vold : Unable to open ums lunfile /sys/class/android_usb/android0/f_mass_storage/lun/file (No such file or directory)" does that mean on the t800 it would of found this file but can't on here because it didn't get created in this location?

Really technical stuff this by the way lol , not the level I'm used too but I'm giving it my best lol, anything else I can do just give me some instructions, I looked into getting a vendor and device tree generated but I don't know if there is a way of doing it within android...I'm guessing that's a Linux job only.
[Galaxy Tab S Android Development] pdolton2000:
Interesting progress, just to verify if some of what I was saying were true I figured in theory DriveDroid should work as it works directly with the kernal I think? And guess what...IT WORKS :) I can successfully mount IMG files and access the data as a ums device no problem, this either empliys now that something isnt quite right with the part that tells the tablet where the parameters of the volumes are or something similar anyway, because the kernel seems to have no problem interoperating drivedroids instructions of the virtual drive parameters and forwarding them in ums mode, and the USB port is working fine when transferring data down it...this must be just an incorrect value somewhere has to be...wish I understood more to fix it :)
[Galaxy Tab S Android Development] :
That's what I tried to say: usb IS working. Some of the problems are addressed by my commits. Again: thanx for your detailed descriptions. Now it's a task for OP to make a new build with cherry-picking those commits (and hopefully publishing his source via git). Thanx.
[Galaxy Tab S Android Development] :
Thank you very much for gathering all that information!

Wakelocks, deepsleep and cpu-state relations look quite normal; deep sleep is not avooded by any wakelock - thats good news.

One more question: can you tell how long it has taken from 31% to 100%?

Now for the bad news: the cpu states are not the states I put in my kernel source for better battery life - that does not mean that this is the main reason for the bad bat life (in deed I manged to increase bat life over stock sources by about 7 - 10 % depending on use case), it just means, that the kernel source used in the build on your device is not based on my source (that's not bad it self, but in abscence of the real used kernel source I reduces the reliability of my guesses).

On the other hand, your detailed information makes me guess that the bad bat life could be kernel/rom related. We are down to the point where we need to have a look at the sources (kernel, device, vendor) used for build.
[Galaxy Tab S Android Development] eousphoros:
Since this dev appears to be missing. If someone wants to do the t805 here is a post to my device repo where I have an initially radio stack running on the t705. The same changes will probably work on the t805. You will need to add mlexe, rild, cbd, and the libril/libsec-ril binary blobs to your vendor repo

http://xdaforums.com/showpost.php?p=59466058&postcount=55
[Galaxy Tab S Android Development] :
Thank you. When asking for the time from 31% to 100%, I want that value for interpolating to The time it takes from 0% or 1% to 100%.

I'm completly with you: temperature is quite normal.

What definetly goes wrong is the duration of charging. My wifi-only device takes 5 to 6 h to charge. The next step would be to be sure it is not your device's battery or chatger - [MENTION=535343]all[/MENTION] users of this rom: does charging your devices roughly equal to 12 h or 6 h?

An slightly other topic related to battary draining: if your device refuses to deepsleep and you have google play servives wakelock, you will find this usefull.
[Galaxy Tab S Android Development] meexx:
Hi, i use also this Rom and my charge time is from 29℅-100℅4 houres . i have installed batterylog and i post a screenshot .... can you tell me wich Combo i must press for a Screenshot? My Tab is a 805 From Germany and i use this Rom for a Week and i have also this bugs at this tread. I dont use Telefon funktion. My sdcard runs in this rom ..... My PC connection runs not. I am happy with this Rom in Time ..... and i hope it comes a Update. Thank your gys for your works
[Galaxy Tab S Android Development] meexx:
OK this is my screen at batterylog, i use also amplify ..... What can i do for you ? I will help (-: i have a clean Installation with pa pico gapps i use this Tab at 2-3 days for 4-6 houres screen on time without charge, No games and normaly Browser and email and tapatalk a little bit eBay usw. I have a better performance with this Rom. When i use Stock Rom or Ironrom i must charge my Tab at a Day. My english is Bad and i hope it is ok....... My Modem for mobile Data 3g/H/H+ works fine and this was for me a special feature for this rom
[Galaxy Tab S Android Development] pdolton2000:
I can confirm it takes a longer time them normal, nearly double...and it takes nearly half the time to deplete the battery, for testing sake I decided to use barracudas kernal dirty flashed and found straight away battery life a lot better

http://charlesingo.mine.nu/ftp/barracuda/08_11_14_CM11_kernel.zip

You loose modem obviously, but maybe someone can run some tests to verify if this kernel makes a difference?
[Galaxy Tab S Android Development] andyt12:
Hey guys, Sorry for being away for so long, been flat out. New build in first post with most issues sorted. Had some missing some proprietarylibs.

[MENTION=2346758]eousphoros[/MENTION] what is mlexe?

[MENTION=4405529]nvertigo67[/MENTION] Im using your cm11 branch kernel with just changes to defconfig for the modem.

Could battery drain be unmatched libsec-ril and modem firmware ? Maybe get the libsec-ril.so from your stock rom and replace.