[ROM][MM 6.0.1] [ KatKiss - KatshMallow #033 ] [MultiWindow]

[karapoutsoglou]

Good Lord, the Master is here in 701????

Sent from my SM-N930F using XDA-Developers mobile app

 

[francois77950]

instalation sur f2s partition

Is it possible to install on a micro sd in f2s partition.
If so, is it possible to refer to a link to another
thank you

 

[Kashban]

Ok, tried #31 of KitKass on my TF701 and while it works in general performance is mediocre at best. I ran some benchs and Geekbench 4 shows a single core performance at 2/3 of what it should be and the multicore performance is even lower (!). Same goes for 3D Mark: about 6500 instead of 9300 points.

Back at CM 12.1 performance is good again.

So there seems to be a problem with the kernel on this build which prevents the Tegra4 in the TF701 to run at it's usual speed.

Any idea how to fix this? Do you need more intel on this for a fix?

 

[timduru]

I can't beleive it's hapenning, thank you a lot for giving this device a new life.
I read that you did boot Nougat and Plan to move to 7.1.
Do you know if this will be son or did you have heavy issues ?
Thanks a lot!!

surface flinger crashing is heavy enough
So I have to fix that first, then move one step further and so on.

I confirm that TRWP and KatKiss are very fragile about partitions... I had to reformat with ext3/ext4 and unmount too before I was able to flash KatKiss to my TF701.
Perhaps a good hint to put on the first post.

Next version will unmount /system first in case you didn't follow the instructions in the 1st post and formatted /system in the recovery

Is it possible to install on a micro sd in f2s partition.
If so, is it possible to refer to a link to another
thank you

It'd require ramdisk changes, but first we'd need a recovery that supports f2fs at all
using f2fs on the internal storage should help as the first step

 

[timduru]

Ok, tried #31 of KitKass on my TF701 and while it works in general performance is mediocre at best. I ran some benchs and Geekbench 4 shows a single core performance at 2/3 of what it should be and the multicore performance is even lower (!). Same goes for 3D Mark: about 6500 instead of 9300 points.

Back at CM 12.1 performance is good again.

So there seems to be a problem with the kernel on this build which prevents the Tegra4 in the TF701 to run at it's usual speed.

Any idea how to fix this? Do you need more intel on this for a fix?

That's definitely interesting,
I did some testing and also comparing with CM-12.1: I get about the same single core performance (CM=884 vs KatKiss=892)
So that would mean that something was using about 1/3 of the cpu when you ran your test, most likely you didn't wait for things to settle, mediascanner didn't finish and so on...

But indeed the multi-core performance is slightly lower than single-core on KatKiss, we're basically running on one core currently ))
would need to restore on hotplug as it resets the cpuset prefs to using only one core.
And MM new cpuset rules simply obey the constraints of using only one core

I'll see either deactivating cpuset for the moment in the next version, or backport more from 3.10 for cpuset /hotplug .
But with it deactivated I get multi-core perf of 2231 in Katkiss vs 2207 for cm
so about the same

 

[Kashban]

That's definitely interesting,

But indeed the multi-core performance is slightly lower than single-core on KatKiss, we're basically running on one core currently ))
would need to restore on hotplug as it resets the cpuset prefs to using only one core.
And MM new cpuset rules simply obey the constraints of using only one core

I'll see either deactivating cpuset for the moment in the next version, or backport more from 3.10 for cpuset /hotplug .
But with it deactivated I get multi-core perf of 2231 in Katkiss vs 2207 for cm
so about the same

That explains a lot .

Would love to use and test KatKiss MM on my TF701 but that performance issue kills it for me.

So once you bring up a new version with this fixed I happily give it another try.

 

[Sasisco]

Hi to all! And especially to Tim-The_Greatest_Rom_Maker
Little offtop. I'm so happy that our tablet is now will be working under android 6.0 (and I hope 7.1 in future It is (and will be) the best day of me (and many others) having this beautiful transformer)) Thank you!
Back to business. Installing instruction is not complete as I think. It should contain "information for dummies": "If you using kang twrp - you need to format data to ext3, then.. etc." But it's not critical.
About what bugs I've found:
1)Touchpad not working (but pressing "enabling/disabling touchpad" button on keyboard causing "Touchpad able/disable" toast-notification. But nothing happens. working. Dont know why it starts to
2) (it's hardware problem, as I think) wifi does not working in "40MHz" HT-mode (in 2,4GHz). Only in "20MHz/40MHz" or "20MHz" modes. Second is in 5GHz mode it only see max 140 channel (5,700 GHz). All channels above it is invisible.
Thats all for now.

 

[timduru]

New Rom Version #032

New rom version available: KatKiss-6.0_TF701T_032.zip

Changelog:

- init: fix writepid wrong pid written in file(s)
- wifi: misc fixes and enhancements

- TF701 installer: unmount system if mounted before formatting
- TF701: disable use_cpuset
- TF701: fix Dock battery icon not hiding when undocked

TF701 KatKernel v003:
- xt_IDLETIMER android-upstream merge
- disable cpuset
- interactive freq tweaks
- fix io_is_busy perms

 

[Neccie]

Ahh so much better now, thanks!

 

[Lopburi]

Version #32 is faster and smoother than previous versions but Wifi on my tab still see only 2.4Ghz not 5Ghz.

 

[timduru]

Version #32 is faster and smoother than previous versions but Wifi on my tab still see only 2.4Ghz not 5Ghz.

I'm connected to 5Ghz on my wifi.
what is your wifi characteristics ?

 

[Kashban]

New rom version available: KatKiss-6.0_TF701T_032.zip

Changelog:

- init: fix writepid wrong pid written in file(s)
- wifi: misc fixes and enhancements

- TF701 installer: unmount system if mounted before formatting
- TF701: disable use_cpuset
- TF701: fix Dock battery icon not hiding when undocked

Vielen herzlichen Dank / Thank you very much!

Will give it a try when I am back at home in about 8 hours.

 

[hitmancho]

This time I flashed without any problems. Just be aware it takes some minutes for the ROM to flash.

The ROM is a lot faster now, I haven't noticed any crashes or other issues as well. It still gets a little bit choppy but I can't be sure it's because of all the stuff I always install on my devices. Just a heads up, you need to use the latest Xposed v87 test if you want to use Xposed framework at all, I think it is related to the AOSP implementation of the November security patch. Otherwise it'll bootloop like it did to me the last I tried using the tablet. Also, if really want to use GravityBox, be aware that it will mess up the buttons if they're at the edges of the screen (when you enable master switch for navigation bar). Other than that it is an excellent daily driver. I tried resolving the lags by using L Speed Balanced profile (with some tweaks from me) and I think it's slightly better but it is no miracle cure by any means.

I like that the RAM managment is alright here, on CM12.1 (granted, I've been dirty flashing updates for half a year and I had installed a load of crap) I think I had memory leaks that reduced RAM to 200MB and caused massive lags until I cleaned apps from recents. It'd be amazing if we can have more interface tweaks and visual tweaks baked into the ROM for more compatibility. A night mode blue light filter would also be good, because I've been using f.lux (which hasn't been updated in months and I think was one of the buggy things in my tablet since before). Also, I think I found out what's causing my flickering issues I had reported before. The minimum brightness of the tablet is lower than CM and I think when I have a very bright white screen on, the backlight just starts upping its brightness. But only then. I increased the brightness a slight, but comfortable bit, and the issue seems to be a lot less visible. Still, it only occurs on mainly lit up pages. Sometimes you can't observe it at all.

 

[francois77950]

Is it possible to update version 31 to 32 without losing the data and applications, as well as the layout icons shortcut on the desktop
It would be faster than installing applications one by one (2 hours each time)
thank you

 

[Lopburi]

I'm connected to 5Ghz on my wifi.
what is your wifi characteristics ?

Fixed it by changed channel from 149 to 44 now my tab can see both 2.4Ghz and 5Ghz. Thanks so much Timduru for spend time and energy bringing your Rom to our tab. :good:

 

[berndblb]

Is it possible to update version 31 to 32 without losing the data and applications, as well as the layout icons shortcut on the desktop
It would be faster than installing applications one by one (2 hours each time)
thank you

Yes, minor version updates like this you can dirty flash, meaning no wipes at all or max cache and Dalvik. Just flash rom, gapps and supersu.
Your setup will be as it was before.
Tim will usually mention if you need to clean install a new version update.
My experience is you get away only with so many dirty flashes though. If you experience weird issues that's the first thing you do: Wipe and clean install. If that doesn't help you can ask for help.
So get a good backup and restore routine going:
Use a launcher that has a backup/restore function
Get familiar with Titanium Backup or Carbon to backup your apps and their settings. Although Google got much better in restoring your apps they still push crap you uninstalled because you never use it or not on this device. (Reminder to myself: Have to go through the My Apps list again)
Use Dropsync/Dropbox, Google Drive or something similar to sync data between the device and online storage if you need data locally on your tablet. Then at least you don't have to copy the data after a full format, just setup the app.

Custom roms and flashing does not mix very well with intricate device setups - at least not for me. If you use Xposed, Gravitybox, themes, Greenify and elaborate home screen setups each rom flash turns into a PIA unless you love to do that stuff... And I don't. The longer I've been flashing the more bare bones my device setup became :cyclops:

 

[Sasisco]

ppsspp (psp emulator) is working very slow and lagy. Changing cpu to perfomance governor and cpu-quiet to runnable is't resolve the problem. CM 12.1 are used before. Settings of ppsspp is the same as on cm 12.1.
Also. Dirty flash is turn first start to infinite loading of system ("loading apps..."). Wiping cache and dalvik before first start is not working. Only wipe cache,dalvik,data resolves this problem.

 

[Kashban]

It's a great rom!
The first thing I noticed is, using another launcher (tested with Action Launcher and Nova Launcher), you can't see the wallpaper. Instead you will only see a black wallpaper...

Edit:
Found an option, it is working now!

I hate it when people post about solving their issues but omit to describe how exactly they solved it, so that others with the same issue could follow up.

That said, I am going to ask politely: Which option and where to find?

---------- Post added at 04:04 PM ---------- Previous post was at 04:02 PM ----------

Vielen herzlichen Dank / Thank you very much!

Will give it a try when I am back at home in about 8 hours.

I confirm Performance is now normal with this version. Great work!

 

[timduru]

I hate it when people post about solving their issues but omit to describe how exactly they solved it, so that others with the same issue could follow up.

That said, I am going to ask politely: Which option and where to find?

See post #2

I confirm Performance is now normal with this version. Great work!

good

 

[Jerry1996]

I hate it when people post about solving their issues but omit to describe how exactly they solved it, so that others with the same issue could follow up.

That said, I am going to ask politely: Which option and where to find?

I'm sorry Sir,
Indeed as mentioned in the second post in Settings --> Display there is an option "Wallpaper modes" which you have to set to normal.