yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S Original Android Development] Narsil:
[MENTION=4405529]nvertigo67[/MENTION] Here we are :

It is a clean flash.

root@chagallwifi:/ # fdisk /dev/block/platform/dw_mmc.2/mmcblk1

The number of cylinders for this disk is set to 3880.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)

Command (m for help): p

Disk /dev/block/platform/dw_mmc.2/mmcblk1: 31.9 GB, 31914983424 bytes
255 heads, 63 sectors/track, 3880 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/block/platform/dw_mmc.2/mmcblk1p1 1 3881 31166944+ c Win95 FAT32 (LBA)

Command (m for help): q

root@chagallwifi:/ # mount
rootfs / rootfs rw,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/fuse tmpfs rw,seclabel,relatime,mode=775,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/dw_mmc.0/by-name/SYSTEM /system ext4 rw,seclabel,relatime,errors=panic,data=ordered 0 0
/dev/block/platform/dw_mmc.0/by-name/EFS /efs ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/dw_mmc.0/by-name/CACHE /cache ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,errors=panic,data=ordered 0 0
/dev/block/platform/dw_mmc.0/by-name/USERDATA /data ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/dw_mmc.0/by-name/PERSDATA /persdata/absolute ext4 rw,seclabel,relatime,data=ordered 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/dm-0 /mnt/asec/com.keramidas.TitaniumBackupPro-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
root@chagallwifi:/ #

and logcat is attached.
[Galaxy Tab S Original Android Development] :
What other then rom, gapps and supersu have you flashed? Please give the output frommthe following shell commands:

lsmod

which modprobe

/etc/init.d/01moduleload

Have you installed an alternate busybox? Which xposed modules do you use?

I refer to "clean flash" as described in #3.

I take a bet, the fat and msdos modules aren't loaded - I takema secound bet it's a sideeffect from your installed software that is not rom, gapps or chainfires supersu...
[Galaxy Tab S Original Android Development] jodeltje:
Just out of curiosity, not having any issues.

To get rid of old crap from other ROM's, such as as init.d script, just clear out the folder? Which?

If that's the case, I should start checking that.. If you clear all the crap while wiping, than great.
[Galaxy Tab S Original Android Development] hurray:
I have updated to the Christmas-version without any issues till now (dirty flash; only wiping cache, Dalvik-cache and /system).

Merry Christmas! :)
[Galaxy Tab S Original Android Development] maxrdlf95:
Would you mirror the link pls still slow speeds on the FTP :(

Merry Xmas and thanks so much for your work
[Galaxy Tab S Original Android Development] Barracuda77777:
Will post a mirror soon

edit:

here you go:

cm-11-20141224-UNOFFICIAL-nvertigo-chagallwifi.zip
[Galaxy Tab S Original Android Development] :
No need to. ALWAYS wipe /system.

Just to be clear: if coming from other rom then cm11 ALWAYS (no exception!) do a "clean flash" as described in #3.
[Galaxy Tab S Original Android Development] Barracuda77777:
anyone having SD card mounting issues please try this kernel:

chagallwifi_kernel_fix_fat.zip

Cheers

GOOD BYE EVERYONE
[Galaxy Tab S Original Android Development] Barracuda77777:
No worries, all good :)
[Galaxy Tab S Original Android Development] FormeriPhoney:
I dirty flash the xmas build and Jesus Christmas the battery is amazing.

Watched a 2 hour bluray movie and drained 9%. That's just stupid. Lol

I still can't get my SD card to be recognized though.
[Galaxy Tab S Original Android Development] :
Then pleeeeaaaaase!!!! Give me from a shell the output of:

ls -la /system/xbin/modprobe /system/xbin/busybox

/system/xbin/modprobe msdos

/system/xbin/lsmod

/system/xbin/busybox

And one more question: what do you flash besides rom, gapps and SuperSU, if any.? OK. And an other one: Do you use an app that comes with own busybox?

But most important: all people with sdcard issues: please post the output of the 4 commands above. Before we canmsearch for the culprit, I need to know the busybox enbironment of the broken installs!

Calling just /system/xbin/busybox should give among the command list the version:

BusyBox v1.22.1 bionic (2014-12-24 08:06 +0100) multi-call binary.
BusyBox is copyrighted by many authors between 1998-2012.
Licensed under GPLv2. See source distribution for detailed
copyright notices. Merged for bionic by tpruvot@github
[Galaxy Tab S Original Android Development] Narsil:
$ ls -la /system/xbin/busybox /system/xbin/modprobe /system/xbin/modprobe msdos /system/xbin/lsmod
-rwxr-xr-x root shell 1048328 2014-12-25 17:22 busybox
lrwxrwxrwx root root 2014-12-25 15:22 modprobe -> busybox
lrwxrwxrwx root root 2014-12-25 15:22 modprobe -> busybox
msdos: No such file or directory
lrwxrwxrwx root root 2014-12-25 15:22 lsmod -> busybox

I didn't flash anything else than rom and gapps, have Xposed with GarvityBox and Greenify, everything else is coming from playstore. I'll reflash a clean rom right now.

[edit] confirm : FAT32 SD card readable after clean "post #3" install. [/edit]
[Galaxy Tab S Original Android Development] :
But you have overwritten the roms busybox:

/ #ls -la /system/xbin/busybox
-rwxr-xr-x 1 root shell 538204 Aug 1 2008 /system/xbin/busybox

OK. Do you knoe which of them installs its own busybox?

Don't waste your time. After flashing (dirty) without overwriting system's busybox again module loading and therefor fat32 mounting will work.

Can you try to search your filesystem for a backup copy of system's busybox? Perhaps something like busybox.bak or busybox.save, something like this...

I'm just thinking out load now:

Though I belive it's just a lack of thinking of consequences and therefor extremly bad coding style to change systems busybox (which stock sammy roms just don't have) , I also belive that many apk developers don't change this habbit.

I also belive that changing busybox will have the strangest side-effcts on the long run (i.e.: will vold's auto fstrim will work any longer). So best would be to have apk developers install their non-system, proprietory **** in a save place outside $PATH.

But I know, I won't change their coding style... :(

So, what can I do from the point of view of a rom-developer, if I can't relay on system binaries??? I'm quite clueless. This **** take half a day of my lifetime and make me thoughtlessly hurt a close friend.

I had to think.

In the updater-script while flashing I could make a backup copy of cm's busybox and reference this one in the script. No problem just a little more work. But I can't change all references (again: i.e. vold is calling fstrim...); and I even don't know which side-effects that all will have.

So, question: Which app is it? Is it only one app? The same for every installation moduleloading doesn't work? Or are there many apps that change busybox? (nice interference - think it to an end... ;) )

I will provide hotfix later today.

---------- Post added at 03:15 PM ---------- Previous post was at 02:49 PM ----------

Thank you - now we now the reason.

And because I can't eliminate the cause, I will think of something other....

Other part I'm working on, cause you have a clean install please try the following for me:

In settings->buttons set "longpress recents" to "open/close" menu. Open app with 3 dot menu (contacts, k9, firefox i.e. but any with menu would do) and try to open meni with long press recents. Thanx in advance.
[Galaxy Tab S Original Android Development] :
Hotfix for alien busyboxes and module loading

If you have installed an app or xposed module that poisoned your system with an incompatible busybox multicall binary your best option is to remove that ****ty programmed app. Your second best (or should I say: last option) option is to flashed the attached zip:

It will put the original busybox from xmas build to /system/xbin/busybox.cm and install a modified version of /system/etc/init.d/01moduleload that uses /system/xbin/busybox.cm for modprobe.

WARNING: This will only fix the issue with modules not beeing loaded at system startup. It leaves alone all other potential damage done by installing an alien busybox instead of cm's busybox... You are lost...
[Galaxy Tab S Original Android Development] Narsil:
Doesn't work.

About what has overwrites busybox, could supersu or a xposed module do that ? Anyway, I can't investigate further on the FAT32 case because my backup is corrupted :(( : I had to copy it from a NTFS SD card to a FAT32 SD card (because TWRP doesn't read NTFS ...) and well, it broke something.
[Galaxy Tab S Original Android Development] FormeriPhoney:
OK so I have my tab in hand again and noticed this...

Only twrp can not view my SD card bc right now in root Explorer I can view and edit my entire card.

I'm gonna cough this one up to my card being formatted to ntfs.

When I'm back at my computer in going to format it again and see what happens.
[Galaxy Tab S Original Android Development] Offica:
Edit fixed bmp :)
[Galaxy Tab S Original Android Development] :
Menu mapped to cpacitive key

I can't get "menu" mapped to any key to work. This drives me crazy:

I can map any action (start camera, search, standby etc.) To any key (home, recents, recents longpress etc.) and it works. As soon as I map "open/close menu" to a button, it just does nothing... And now it gets mysterical: if I change ro.sf.lcd_density in build.prop to a value >= 356 (everything changed to the look of a phone with navbar on the right side) "menu" works again.

Logcat shows nothing, when "menu" is not working. In dmesg I can see the keycode is right (of course, otherwise the other mappings wouldn't work either...)

I can't find any commit in my device git, that breaks "menu". And I'm quite sure it works some time back. I'm looking for two days now for a solution, and will go crauy shortly... ;)

I'm lost - any idea or pointer would be highly appriciated!
[Galaxy Tab S Original Android Development] hurray:
I think that I can't help as I wish but just a few thoughts:

- did you perhaps disable the keys with the zip-file from me?

- I use "Auto Hide Software Keys" and have no problems with the menu. It will be in the software navbar and works as expected.

- I use my zip-file for deactivating the hardware keys and have set under settings-hardware buttons to "no action" to the menu button. Every time I touch the menu button there is no action (as expected) but I feel the buzzer from the haptic feedback. This means for me that not all things correlated to the menu button are deactivated.

Perhaps there is something useful in my findings for you.
[Galaxy Tab S Original Android Development] :
Not related to your zip - I am using capacitive keys. And this issue applys only to capacitive keys. Keys itself (including feedback) are working fine: any other action then "open/close menu" are working... really strange...
[Galaxy Tab S Original Android Development] :
And now it gets even stranger: Disable all mappongs to menu, make sure fitefox is not running and start it (three dot meni is shown), now go to settings and map menu to longpress recents: now longpress recents opens menu in firefox. Kill firefox from recents view, start it again (three dot meni is NOT shown) longpress recents does not work as menu any more... Wow.

I'm still lost at this... Now a little bit more... ;)

BTW: I have tested old backups - At least back to 5th of November this is not working. I'm not so sure anymore, that it had ever worked. Proppably my memory on working longpress some key for menu refers to on screen navbar: there - with broken disable capacitive keys as well as with [MENTION=3099085]hurray[/MENTION]s zip - it's working.
[Galaxy Tab S Original Android Development] :
At least we are not alone with this:

http://xdaforums.com/galaxy-tab-pro-12-10-8/help/cm11-usage-close-menu-botton-t2849978
[Galaxy Tab S Original Android Development] hurray:
So it seams to me not a problem with our T800 in detail but a issue with CM11 itself.
[Galaxy Tab S Original Android Development] :
CLOSED: OnePlus One Invites

[MENTION=535343]all[/MENTION]: I really appreciate your testing, feedback, helping each other, recomendations and ideas. So I decided to post the three invites for

OnePlus One, 64 Gb, sandstone black, 6 days left.

here first, to give the users of our rom the opportunity to claim them.

If you claim one of these, please send PM or reply, so I can mark them as claimed here, to avoid frustration.

https://account.oneplus.net/invite/claim/GL2K-SZVQ-RM0V-5CLT

https://account.oneplus.net/invite/claim/GLGR-WP2M-D0AB-0BPT

https://account.oneplus.net/invite/claim/GLU6-QS4W-MSXX-KFA3

ALL ARE GONE!

---------- Post added at 04:05 AM ---------- Previous post was at 03:58 AM ----------

Not quite sure: if so, tjere should be more complains about this to find with google. I think it's a small setting in device tree. But as stated: I'm not sure. No errors or something at all in logcat, so I'm guessing... :(
[Galaxy Tab S Original Android Development] naomile:
OPO claimed
[Galaxy Tab S Original Android Development] Offica:
Middle one claimed, check this thread every couple hours haha thanks alot mate
[Galaxy Tab S Original Android Development] Narsil:
Well ... I'm back with my SD card access problem !

Reinstalled everything from scratch : clean install and gapps -> access to SD card ok, then all my apps (nothing with root's right except Greenify, TB and BusyBox pro, no more Xposed) and the SD card access is gone again ... Fortunately you patch worked, thx.

I have a backup of the non working situation (before applying the patch), could I help in any way identifying the culprit ?

Diego
[Galaxy Tab S Original Android Development] :
Install busybox pro not in /system/xbin. Or install my hotfix. And - pleeeeease - read my postings regarding alien busyboxes break module loading.... For the last time: modprobe is busybox. cms rom included busybox (modprobe is part of it) looks for modules in /system/lib/modules - incompatible third party busnoxes look in /lib/modules, which is inexistant in cm.

So: we know what breaks the rom.

Why do you install busybox pro at all? What does it serve, what the internal busybox does not?
[Galaxy Tab S Original Android Development] Narsil:
Sorry man, I've carefully read all your posts about this and didn't find anything relevant, nor does CM's wiki talk about incompatibility of Stericson's BusyBox. Never had this problem with other CM ROM I've used on other devices (BosyBox pro is part of my first installed apps from years) ... so I learned something new today and will pass the year smarter I began it :angel:

Thx !
[Galaxy Tab S Original Android Development] :
Happy new Year for everyone!

I think cm-devs think it is unneccesary to install alternate busybox, 'cause they bring their own, and app devs think, they need to bring own busybox, 'cause sammy rom has no busybox.... Clean solition would be, if some special version of busybox is needed for my app, to install it in a place outside system path, and reference it directly. UKM i.e. installs its own busybox in /data/UKM/busybox, set "BB=/data/UKM/busybox" at the beginning of each script, and call somthing like "$BB echo 'this is echo of our own busysbox.'"

I learned that the hard way when running aokp on manta: I had purchased a busybox pro lic, and installed stericson every time I flashed a rom just out of habbit. When aokp went kitkat (which among many other advantages brought a vold, that do fstrim on ext4 filesystems, when idle some time), I searched logcat for weeks for fstrim - nothing happend... It took me really some weeks to realize (you guess it...) that external busybox had no fstrim (that time - I belive meanwhile stericson has fstrim when installed on devices, that support it) and break the whole mimik... :( So I become on aokp (and now on cm) very careful about changing systems own bsybox.

As I stated in postings before: I know it breaks module loading - I don't have enough imagination what else could get broken...

---------- Post added at 01:46 PM ---------- Previous post was at 01:26 PM ----------

I have made some mistakes when testing to much kernels in a too short time before Christmas:

I said, that the kernel with power efficient workques and bfq drained battery and lags on network i/o. I have to correct this:

The kernel with power efficient wq is the most battery friendly, when run with cfq. bfq seems to lag a very lttle bit on network i/o and interactive usage at the same time. There is no difference in bat usage between cfq and bfq. Perhaps bfq is slightly (very, very, very slightly - perhaps it's only placebo) better with bat usage then cfq.

So my current recommendation the kernel from December the 21th (20141221-b) with cfq. If you flash this kernel over christmas build it should boot up with my recommended settings.

Your milage about cfq and bdq may vary - just find out for yourself. You can change ioscheduler easly from Settings->Performance.

Again: happy new year,

Nvertigo
[Galaxy Tab S Original Android Development] TheGoD:
Any way to adjust colors in this ROM? Also,does it include APTX support?
[Galaxy Tab S Original Android Development] hurray:
Happy new year! :)

You should make a link to your post on the first site of this thread. It is a very good explanation how it is possible that multiple busyboxes are existent and the resulting sideffects and misbehaviours from this.

Btw: I have a new record with over 9 hours(!) screen on time with the latest rom! Most time of course with a very low brightness but a fabulous result for me. :)
[Galaxy Tab S Original Android Development] :
New Build in #5

Build 0101 (Happy New Year Build)

Mainly a maintain release. Small performance/battery enhancements: Added power efficient workques and bfq again (thanx to [MENTION=3511708]UpInTheAir[/MENTION]); added biomic optimizations again (we had them some time ago, but [MENTION=4193974]Barracuda77777[/MENTION] and me thought they were responsible for some unstabillity issues - after barracuda had found the reason was something else, I forgot to readd again - till now). f2fs code is updated and is no module any longer but build in kernel (I'm trying to migrate rom to f2fs with no success so far, it's not bootin at the moment).

I recommend the settings this build comes up with (cfq, 400 (aka 200) MHz min speed, interactive, to name the most important. But you can play with and find the best for your personal usecase. (simple settings via Settings->Performance; advanced fine tuning can be done in 01systemtuning in /system/etc/init.d - if you don't know what that means, leave file alone!). Brancheas are cm-11.0 for device and vendor and cm-11.0-sh for kernel.

01moduleload: remove f2fs module from loading, 'cause we need it in kernel to boot from. Nvertigo

change actual mounts of /system /cache and /data to f2fs Nvertigo

cleaned up overlay. Nvertigo

Fix Typo credit NBruderman barracuda7

tune bionic a bit - works on manta. Nvertigo

f2fs: filesystem version 3.4.y [20140903] dennes544

set permissions of block/bfq*[ch] to 0644. Nvertigo

enabled bfq iomscheduler. Nvertigo

workqueue: fix permission for power_efficient [neobuddy89] UpInTheAir

CPUFREQ: ondemand: use power efficient wq! [halaszk] UpInTheAir

workqueue: add system wide power_efficient workqueues (squash commits

bfq-iosched: tuning for SSD [anarkia1976] UpInTheAir

scheduler: update BFQ-v7r4 to BFQ-v7r5 for 3.4.0 [Paolo Valente] UpInTheAir

scheduler: BFQ-v7r4 for 3.4.0 [Paolo Valente] UpInTheAir

MD5: 0890de20a55f97c2a382ddbf9ec7b079

ROM: http://charlesingo.mine.nu/ftp/nvertigo/cm-11-20150101-UNOFFICIAL-nvertigo-chagallwifi.zip

[MENTION=4193974]Barracuda77777[/MENTION]: if time permits, would you please do your magic mirroring? Thanx.

[MENTION=3099085]hurray[/MENTION] and [MENTION=535343]all[/MENTION]: I have added a link to the busybox posting you likes under "Recommended in #5"

[MENTION=535343]all[/MENTION]: Perhaps I showed some impatience and eager when it comes to third party busyboxes - I'm sorry. It's difficult for a non native English writer to explain things as simple as possible and detailed as neccesery. The wide variety of preknowledge about android and linux makes it not easier for me. So when I get impatience again, please, be patient with me... ;) I really like the way we write to each other in this thread - and I don't want to be the bad exsample.
[Galaxy Tab S Original Android Development] UpInTheAir:
I do recommend to use the ondemand gov (patched for PEWQ), as it is quite a battery saver for those inclined that way @ minimal performance loss (although my eye can notice it, others not) ;)
[Galaxy Tab S Original Android Development] Barracuda77777:
Mirror for latest build:

cm-11-20150101-UNOFFICIAL-nvertigo-chagallwifi.zip

Cheers
[Galaxy Tab S Original Android Development] FormeriPhoney:
I just had to send my device in for a warranty fix.. Damn I was looking forward to flashing this latest build.

My power button sort of collapsed into the device body.
[Galaxy Tab S Original Android Development] :
Sorry, to hear that.

I'm very curious to hear what happend (knoxx flag). Whould be nice, if you report back. Thanx.
[Galaxy Tab S Original Android Development] FormeriPhoney:
They have to be out of their goddamn minds to not fix a hardware button bc of a Knox flag. One has absolutely nothing to do with the other.

That's like putting tints on my car and them not warrante the engine as far as I'm concerned
[Galaxy Tab S Original Android Development] :
You are right - I'm absolutly with you on that and keep fingers crossed you get a repalcment soon! As I said: I'm just curious how sammy is dealing this whole "konxx warranty flag" in real life.

Kidding: If you didn't have flashed so many roms, your Powerbutton would still be working... :lol: SCNR

---------- Post added at 03:18 PM ---------- Previous post was at 03:07 PM ----------

Kernel git was not pushed from my local git - done now. Branch cm-11.0-sh is what I build from.
[Galaxy Tab S Original Android Development] nishanta2006:
If i flash this on t 805 then the only risk is of not being able to use a sim card right? Can i otherwise flash it?
[Galaxy Tab S Original Android Development] :
Yes.

No.

Before you ask: no, I won't build for chagalllte.

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

Simple, untested (have just installed it - the only points I can make: it does not fc, it changes the values it shows and it doesn't overwrite /system/xbin/busybox... SCNR) and - IMHO - nicer then editing 01systemtuning:

http://xdaforums.com/android/apps-games/app-kernel-adiutor-t2986129
[Galaxy Tab S Original Android Development] :
Your patch for PEWQ for ondemand (and of course the one for system) is included. ondemand scales only down to 600 MHz (even if min freq for CPU ist set to 400 or 200 MHz), and I can't find a gov tunable for that. What do I miss?