yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 8.9 Android Development] vengeancezak:
Could I also get the name and password please?
[Galaxy Tab 8.9 Android Development] jolinnard:
Please send me a PM.
[Galaxy Tab 8.9 Android Development] chaostoasty:
Hi, could i please get the name an password to download?
[Galaxy Tab 8.9 Android Development] tueurdemouche:
Mod edit - translated by https://translate.google.com/. Oswald Boelcke, Senior Moderator.

Hello, I would be interested in the password as well. Thank you.

*********************************

Bonjour, je serais intéresser par le mot de passe également. Merci
[Galaxy Tab 8.9 Android Development] Oswald Boelcke:
Hello and good afternoon, @tueurdemouche Welcome to XDA! I hope you'll always get the support you require and have enjoyable times on our Forums.

However, as a one-time courtesy I've translated your above post. With reference to rule no. 4 of the XDA Forum Rules, please post in English or add at least an English translation to your French posts.

Spoiler content hidden.

Regards

Oswald Boelcke

Senior Moderator
[Galaxy Tab 8.9 Android Development] tueurdemouche:
hello, i am sorry to that.

I am happy to going here for more information.

see you on the forum. bye
[Galaxy Tab 8.9 Android Development] jolinnard:
I thought bootanimation black out was a Nameless feature... I'm not sure why f2fs kernel do that... Maybe last tweaks in ramdisk and init.d are implicated. Anyway, this is not a problem for me :)

We should do a complete benchmark comparing ext4 and f2fs. If I have time, will do tomorrow. I want to see if there is a real advantage using f2fs.
[Galaxy Tab 8.9 Android Development] L3R0N:
I guess its not because its completely fine on the ext4 ROM and kernel. Its no biggie here either because it only lasts for about 6 seconds. Which set of benchmarking apps do you intend to use? You can do for the p5wifi and I'll do for the p5 3g. Need to know since there are multiple benchmarking tools out there. Tried using you kernel on the old cm11 build and it boots and seems fine but the figure settings script won't run and manually running it from terminal emulator shows permission denied. This was present in an earlier build of this kernel for nameless...whaddya change to make it work? Would be nice to see how it would change cm11.

BTW you forgot to add f2fs tools to the latest build 20141124. I had to add it myself.
[Galaxy Tab 8.9 Android Development] jolinnard:
Ok. I need to think about it...

I fixed Nameless build, thanks.

For init script, IDK... If you are running with root should work. Can you post the exact message you see?
[Galaxy Tab 8.9 Android Development] L3R0N:
Cool. I'm on nameless now but I will flash cm11 tomorrow and post that message. Also I noticed that the tab reboots to the charging screen each time it is put to charge. If I plug it in and use it then it stays on and functional but if I plug it in and leave it for a while it will reboot to the charging screen. Mobile network disconnects any time the screen goes off even for a few seconds and it will only reconnect after a reboot. I flashed and tested every kernel you released and that only surfaced in v7 of the kernel and upwards. Not sure why its that way...not a real big issue because I don't use 3g that often but its nice to know that its there and functional. Also it seems like it is indeed the device control app that causes the device to not wake from deep sleep unless rebooted. I used no frills CPU to change governor and over clock and the tab worked fine, however, when I used device control to do the same thing the tab wouldn't wake until rebooted.
[Galaxy Tab 8.9 Android Development] jolinnard:
I suppose all modem stuff in p5 can cause a lot of troubles... Unfortunately I can't debug myself. Could be something related to p4 firmwares or modem app? Maybe p4 and p5 have something different, I don't know.

I was experimenting with a universal partition flash zip. After many tries, I've found a solution. So with these new kernels you can format your partitions in ext4 or f2fs and a script will generate a correct fstab every time.

Figue-kernel-autofstab-p5-v1.zip

Figue-kernel-autofstab-p5wifi-v1.zip

Please, this is the first release, it can bootloop your tab if I forgot something. Don't worry, a simple flash of a "classic" kernel should fix it.
[Galaxy Tab 8.9 Android Development] L3R0N:
Thanks for this I will be testing. I ported slimsaber rom from the p4 and my oh my does this thing fly.
[Galaxy Tab 8.9 Android Development] jolinnard:
More ROMs! Yeah :)

I'm gonna convert /data to f2fs now...
[Galaxy Tab 8.9 Android Development] L3R0N:
I will upload tomorrow because my internet is still slow. Called my ISP and I was told that this should be fixed by tomorrow so I will be able to upload. Good thing too because I just noticed that when I turn WiFi off it won't come back on unless you reboot. Looking into this and will see if I can fix. And its Android 4.3. Will try porting the WiFi version tonight.
[Galaxy Tab 8.9 Android Development] andray:
hmm, flashed nameless-4.4.4-20141108-p5-HOMEMADE.zip with cwm 5.5.0.4. Stuck on boot animation. I had cm11 and did factory reset before flashing. What am i doing wrong?
[Galaxy Tab 8.9 Android Development] L3R0N:
Update your recovery to the latest available for our device. Then do a full wipe system, data, cache after which you should reflash the rom. If it still hangs at the bootscreen then you can pull a recovery log so [MENTION=2002216]jolinnard[/MENTION] can have a look.

Latest TWRP for P5

http://mirror.lnx.im/android/galaxy-tab/recoveries/twrp2710_p5_f2fs.zip
[Galaxy Tab 8.9 Android Development] jolinnard:
I never tried these ROMs with CWM, but always the best is to pull /tmp/recovery.log so we can see exactly if something is wrong in the flash process.
[Galaxy Tab 8.9 Android Development] jolinnard:
I'm runing a long benchmark... comparing read and write in 3 types of filesystems: ext4, f2fs and xfs with different values in read_ahead and all of our schedulers. Will try to post the results later.

Also I updated recovery kernel, so we can charge the battery (benchmark is taking a few hours, so the most stable environment is recovery). I added xfs support too.
[Galaxy Tab 8.9 Android Development] L3R0N:
Me neither I moved from cwm the moment twrp became available for our tab which was quite a while back.

That's great. ISP still hasn't fixed their problem so I'm still unable to upload the slimsaber ROM....I fixed WiFi and now the ROM is perfect. Hoping to have a look at Lollipop when I'm done with exams.
[Galaxy Tab 8.9 Android Development] jolinnard:
Benchmark is done. I spend one hour to analyse the data, but I'm not an expert. I choose two tests: the first writes 2560 blocks of 4 KBytes = 10 MBytes. Second: 128 blocks of 1024000 Bytes = ~125 MB. Every file is read too. Those writes and reads are done for every scheduler (noop, deadline, row, bfq, sio, sioplus, vr and tripndroid) and every read ahead value (128, 256, 512, 1024, 2048 and 4096 KBytes). That process is done in a partition in EXT4 other in XFS and the last in F2FS. Tab was in TWRP recovery, without touching screen in whole process.

Script used

Output

Spreadsheet

A nice PDF with all data.

The results

Reading files: all read values are almost exact. So all the combinations are quite good, for instance, it means that keep /system in ext4 is a good option.

When we are writting a 10 MBytes file, in blocks of 4 KBytes, XFS seems the best option, very similar to F2FS. In absolute values, using deadline + 4096 KB read ahead in XFS seems the best. In average, ROW seems the best scheduler for XFS, followed by NOOP, also ROW and NOOP are almost equal for F2FS in this situation. EXT4 seems a bad idea... Look at EXT4 + BFQ (OMG!).

When we are writting major blocks (1 MB/block) all numbers are more similar than before. EXT4 isn't so bad, but XFS and F2FS are quite better. In XFS: NOOP, DEADLINE, ROW, BFQ, SIO and SIOPLUS are pretty similar in performance. For F2FS the best scheduler seems NOOP. The hightest bitrate is for the combination: XFS + SIO + 2048 KB read ahead.

Those benchmarks are not "the real life". I need to find how to do multithread writes and reads to do more tests. For this first benchmark (the first in my life) I choose those two tests, but maybe others should be more real. If you think that those values doesn't mean anything, please, expose your opinion. I want to find the best combination possible.
[Galaxy Tab 8.9 Android Development] L3R0N:
This does show promise. However, since these are not real life values I won't get my hopes up yet as these numbers can be very different out in the real world. But I think this shows promise even though they're liable to change out in real life. Keep up the good and hard work on our tab. If we can't get Lollipop we might as well make the best out of what we got. BTW, I think we need a newer recovery for Lollipop but that's talk for another day. Many thanks even though I can only click the button once.
[Galaxy Tab 8.9 Android Development] jolinnard:
You're welcome. My next step is to try xfs in /data partition. Maybe with that we can increase a little the performance.

Why do you want a new recovery L3R0N?

I need to figure out how people in p4 is building Lollipop. I don't have experience in ROM building and I couldn't find a manifest or something like that. I asked them in its thread but never had an answer With it, it's easy to start... Maybe somebody here knows how to build it. If we can build a Lollipop ROM, we can try to patch the rotation screen like before and have a working system.
[Galaxy Tab 8.9 Android Development] andray:
okay, i flashed twrp ...and it didn't help until FULL wipe.))

pico gapps can't be installed cause it checks that tablet is gt8.9wifi before install. Mini version can't be installed too because of not enough memory. It says smth like "u have 217000kb but 220000 is needed" (i may be wrong with numbers). But firmware already has google play so i don't need gapps.

After installing it has already switched off several times. Don't know what's wrong but will try to flash stock with odin, and then reflash this one, cause tablet is still inadequate after cm11.) e.g. battery charge animation is broken
[Galaxy Tab 8.9 Android Development] jolinnard:
Ok. Download pico gapps again, p5wifi restriction is fixed.

Anyway, flash Nameless the first time, pico gapps and my new autofstab kernel (check the first post). Check that all is fine. Then you can try to switch to ROM you want.
[Galaxy Tab 8.9 Android Development] L3R0N:
Why do I need a new recovery? Well I've noticed that more people have success flashing lollipop with twrp 2.8 compared to twrp 2.7. Its no use posting in the aosp 5.0 thread since decatf mostly posts with updates and the like. I think you'll have a greater chance at a response if you post in the omni 5.0 thread since AAccount seems to reply more to questions. Unfortunately I have no experience in building ROMs from source either but I'm sure there's someone here who can be of help.
[Galaxy Tab 8.9 Android Development] decky006:
I have been having the issue of switching back on from deep sleep with the v17 f2fs kernel on the latest nameless f2fs rom. Then yesterday it wouldnt switch on at all. i eventually managed to get it back into recovery mode by connecting usb cable to laptop. i tried to install a non f2fs rom but it stalls at the start where the screen has the text Samsung galaxy tab...

I tried installing non f2fs recovery, wiped the folders, tried changing the kernel , different roms but now I can only install 1 of the f2fs roms.

What method should I follow to get back to a non f2fs rom? Do I need to flash a stock rom via odin first?
[Galaxy Tab 8.9 Android Development] L3R0N:
I've had that happen to me as well. The only non f2fs ROM that would get my tab back to ext4 was the nameless 20141108 homemade ROM. It seems like the other ROMs install without formatting the filesystem back to ext4 hence it won't boot. If that fails for you then I guess its Odin for you.
[Galaxy Tab 8.9 Android Development] andray:
ok, i installed

1 twrp2710_p5_f2fs.zip

2 nameless-4.4.4-20141124-p5-NIGHTLY-f2fs.zip

3 Figue-kernel-autofstab-p5-v2.zip

4 pa_gapps-modular-pico-4.4.4-20141110-P75xx-P73xx.zip

cannot say that it's smoother than stock 4.0.4.)

i installed needed apps and went to the kitchen, and when came back tablet was switched off and battery initialization animation was on the screen.

upd. and it continues to do this. maybe i installed faulty builds?
[Galaxy Tab 8.9 Android Development] jolinnard:
Flash the autofstab kernel, it's in the first post. You can flash it in all recoveries. That kernel zip will detect and write a right fstab in initramfs, so your tab will boot again. Then do what you want. If you want to get back to ext4, I can do a zip to format all partitions. But, with autofstab kernel should always boot.

And, of course, if you flash the stock Odin image, you will get back to Samsung stock.

Anyway, with my p5wifi I don't have any issue switching back from deep sleep. Maybe once, but always it wake up after another try. If not, a hard reboot fix it (:p).
[Galaxy Tab 8.9 Android Development] jolinnard:
Should work. But if anything goes wrong, and tab rebooted itself (caused by a kernel panic, for instance), then it will remains in battery load animation if it's plugged. Simply, press power button until tab turns on.

I'm a little frustrated because in p5wifi I'm very stable, I can play, read, navigate... And I don't have almost any issue... Sorry guys, but I don't know why you have those issues.
[Galaxy Tab 8.9 Android Development] L3R0N:
This only happens if you use the device control app that comes with the ROM. This apparently hasn't been fixed because the problem is still there and much complained about. I stopped using this app and the problem stopped as well.

The tab always does that regardless of whether or not its plugged in. No idea why it would do that. However for those to whom this is a problem then they can flash the p5wifi build, it should work just fine except that 3g will be missing. Hopefully it won't be missed since most people are glued to WiFi anyway.
[Galaxy Tab 8.9 Android Development] jolinnard:
XFS working fine ;)

root@p5wifi:/ # mount | grep tegra
/dev/block/platform/sdhci-tegra.3/by-num/p4 /system f2fs ro,relatime,background_gc=off,discard,user_xattr,inline_xattr,acl,errors=recover,active_logs=6 0 0
/dev/block/platform/sdhci-tegra.3/by-num/p5 /cache [B][SIZE="4"]xfs[/SIZE][/B] rw,nosuid,nodev,noatime,attr2,delaylog,noquota 0 0
/dev/block/platform/sdhci-tegra.3/by-num/p8 /data [B][SIZE="4"]xfs[/SIZE][/B] rw,nosuid,nodev,noatime,attr2,delaylog,noquota 0 0
/dev/block/platform/sdhci-tegra.3/by-num/p1 /efs ext4 rw,nosuid,nodev,noatime,errors=panic,user_xattr,acl,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc 0 0

Thanks to [MENTION=4177759]exabit[/MENTION] to compile xfs tools for android: link
[Galaxy Tab 8.9 Android Development] L3R0N:
Thanks for this.....maybe you should release a ROM with xfs included so we can test. To fix the issue with the device control app you simply need to replace the one in the ROM with one from a build released before October 19. I just ported the Nameless-20141204 build, replaced the device control apk and it worked well no problems waking from deep sleep. Only issue is tab loses 3g connectivity when the screen goes off at times....not a real issue for me because I don't make use of it but its an observation.
[Galaxy Tab 8.9 Android Development] jolinnard:
F2FS and XFS improves performance when they are in /data. If you want to format your /data in f2fs or xfs, you will need to do manually. I can't include it in ROM zips, because it should writes only in /system. So, if you want, I can make a zip that will format /data in f2fs or xfs.

Please, upload Device Control apk somewhere, and I will replace it in p5 ROM. In p5wifi I don't have any issues with it.
[Galaxy Tab 8.9 Android Development] L3R0N:
Oh I get it. I can do it manually but a zip would be welcomed as well.

Edit: Here you go [MENTION=2002216]jolinnard[/MENTION]
[Galaxy Tab 8.9 Android Development] L3R0N:
[MENTION=2002216]jolinnard[/MENTION] the reboot and mobile network disconnect issues being experienced by p5 users come as a result of the linaro toolchain used when compiling you kernel. Try compiling with another version of the toolchain or use another. Did [MENTION=4800636]OmarEinea[/MENTION] compile using the linaro toolchain? I ask because I took the boot.img from one of his nameless Roms and used it in one I ported 20141206 homemade and their were no issues whatsoever.
[Galaxy Tab 8.9 Android Development] jolinnard:
Hi my friend. Can you try this? It's built with Linaro 4.6.4-2013.05. It has XFS module too.

I was also been playing a bit with /extra partition. It is an old partition used by Samsung in stock ROM, but not used anymore (/dev/block/platform/sdhci-tegra.3/by-num/p10). It has only 300 MB... so I decided to play with swap into it... It doesn't look an improvement... for now I think to use it to store f2fs tools and xfs tools. Could be used too to store some scripts or /etc/hosts file that could survive any data wipe.
[Galaxy Tab 8.9 Android Development] mattsternc:
Has anyone confirmed whether or not the latest version of Netflix will run without error on this combination? I am on an older Nameless 4.4.4 build and have to use an older version of Netflix with the Xposed framework workaround for things to work without it crashing while starting up.
[Galaxy Tab 8.9 Android Development] L3R0N:
So I had three reboots using the kernel you attached above as compared to 0 when using the one taken from one of OmarEinea's Nameless builds. Overall all seems smooth mobile network also disappeared twice needing a reboot to fix it.
[Galaxy Tab 8.9 Android Development] jolinnard:
Ok. I'm sorry... Maybe I need to revert some patches for 3G...
[Galaxy Tab 8.9 Android Development] L3R0N:
No need to be sorry :) that's the way it is with development...might work or might not work. What's different between the way you compile your kernel and the way OmarEinea compiled his? Maybe if you can spot the difference we might figure out what's causing the problems.
[Galaxy Tab 8.9 Android Development] graug:
I installed TWRP 2.7.1.0, followed by twrp2710_p5wifi_f2fs.zip. This part worked fine. After that I tried to install

nameless-4.4.4-20141108-p5wifi-HOMEMADE-f2fs.zip

but TWRP complained about

E:Error executing updater binary in zip '/sdcard/nameless-4.4.4-20141108-p5wifi-HOMEMADE-f2fs.zip'

Installing LS-KK-MileStone-3.2-p5wifi-system-cache-f2fs.zip worked fine. Any idea what the problem with the nameless-rom could be? I even downloaded it a second time, but the problem persisted. I can open the zip file without problems on windows. I just downloaded

nameless-4.4.4-20141124-p5wifi-NIGHTLY-f2fs.zip

and tried to install it, but it twrp gives the same error message. I have a P7310-WiFi only.
[Galaxy Tab 8.9 Android Development] L3R0N:
It could be that [MENTION=2002216]jolinnard[/MENTION] forgot to add f2fs tools to the ROM zip. Pull a recovery log and post here. We'll see if we can figure this out. I don't have a p7310 tho. Or you could open the zip and check if there is a folder named "tmp" in there. If there isn't then copy it from the LS-KK-MileStone-3.2-p5wifi-system-cache-f2fs.zip that you have. Then flash again. If problems persist the you can pull a recovery log and post here

adb pull tmp/recovery.log
[Galaxy Tab 8.9 Android Development] jolinnard:
Hi! Please, attach /tmp/recovery.log next time. As fas as I can remember, Nameless should work... I'm uploading 2 newer versions if you want to try. Latest is ext4, but for my benchmarks, in /system partition ext4 is equal as f2fs in performance... So it's not important what version you choose. Remember to flash my latest auto kernels to patch your fstab.
[Galaxy Tab 8.9 Android Development] graug:
thanks for the reply. I've installed custom roms on a couple of devices but so far I didn't have to install/use adb. Did that now and pulled the requested logfile.

I checked the zip-files and they contain a tmp folder, so I guess that's not the problem.
[Galaxy Tab 8.9 Android Development] L3R0N:
Do a clean install then. Wipe /system, /cache and /data then try again. I've had many errors when flashing but never this one....and I'm a flashaholic. My poor nexus 6 goes through 4 different Roms in one week so yeah I'm a flashaholic and haven't seen this particular error. [MENTION=2002216]jolinnard[/MENTION] should have a better understanding of it if a clean install doesn't work.
[Galaxy Tab 8.9 Android Development] graug:
Sorry about the missing recovery.log. Next time I'll know :) Looking through the attached recovery.log, it looks as if the following errors make it fail:

grep: /tmp/gapps.prop: No such file or directory

df: /tmp: can't find mount point

sh: Available: bad number

sh: Available: bad number

sh: Available: bad number

mount: failed to mount /dev/block/platform/sdhci-tegra.3/by-num/p8 at /data: Device or resource busy

about to run program [/tmp/otasigcheck.sh] with 1 args

You have an installed system that isn't signed with this build's key, aborting...

run_program: child exited with status 1

script aborted: Can't install this package on top of incompatible data. Please try another package or run a factory reset

Can't install this package on top of incompatible data. Please try another package or run a factory reset

I:Legacy property environment disabled.

E:Error executing updater binary in zip '/sdcard/nameless-4.4.4-20141124-p5wifi-NIGHTLY-f2fs.zip'

Not sure what is different in the LS rom, because it worked.

The 2 new versions you uploaded seems to have permission problems. I get

Forbidden

You don't have permission to access /android/galaxy-tab/ROMs/Nameless/nameless-4.4.4-20141127-p5wifi-NIGHTLY-f2fs.zip on this server.

when I try to download them. Thanx a lot for your work and your support!!
[Galaxy Tab 8.9 Android Development] graug:
Thanx for the quick response. I'm also sensitive to left over files and already did a full wipe, but this didn't change anything. Even after the installation of the LS rom I get the same error message when I try to install the nameless one.
[Galaxy Tab 8.9 Android Development] L3R0N:
Then the ROM is probably the cause. Try another. [MENTION=2002216]jolinnard[/MENTION] has uploaded new ones nameless-20141215-nightly. I wont try them because im running nameless-2014-1206-homemade and im quite content with it. But that's weird...the only error I've ever had flashing his nameless builds to my tab 8.9 3g is during conversion to f2fs when he forgot to include f2fs tools and once when he used a wrong file in the recovery so it mistook my 8.9 3g for a 8.9 WiFi and wouldn't flash the 3g ROM.
[Galaxy Tab 8.9 Android Development] jolinnard:
It's not an error of missing tools. It fails because of binary updater script. [MENTION=5983022]graug[/MENTION], please, try the releases I uploaded yesterday, permissions are ok now.
[Galaxy Tab 8.9 Android Development] L3R0N:
I was saying that it was one of the only errors I ever got when flashing ur Roms. Thanks for keeping our tab alive tho.....keep up the good work. Maybe one day we can enjoy Lollipop on our tabs as well when a rotation fix is found. :) :good:
[Galaxy Tab 8.9 Android Development] jolinnard:
Yeah... Maybe OmniROM could fix rotation setting... Would be a new reborn for our tab.
[Galaxy Tab 8.9 Android Development] L3R0N:
Reborn indeed!! Been talking to other devs about rotation but none seem to have an idea where to look. So yeah we'll just have to wait for a fix from omni. But it really flies on the tab 10.1 . Hopes up for a Lollipop build that works for our tab.
[Galaxy Tab 8.9 Android Development] kirby_hegner:
I this maybe something that can be used to rotate in our device?

http://xdaforums.com/showthread.php?p=58153985

Skickat från min LG-D855 via Tapatalk
[Galaxy Tab 8.9 Android Development] L3R0N:
I don't think it would. It says its for launcher and lockscreen. Unfortunately our rotation problems go further than just these two.