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

[berndblb]

Edit: I was able to get back into the recovery without it rebooting, but it will not let me do a wipe. This is what comes up:

I can't read the exact messages, but it seems to be the well known problem with TWRP on this device.
Change file system type to ext3 on /system and /cache. Revert back to ext4 after successfully having done this.

A link to the instruction?

This is where it first reported, right in this thread: http://forum.xda-developers.com/showpost.php?p=69597289&postcount=26

I had the same thing happening, TWRP didn't want to mount anything after just formatting data. I only formatted /data to ext3 and then back to ext4 and rebooted recovery to fix it. Don't think cache matters. It's a bug in TWRP I guess...
Next time I want to format data, I would do it in fastboot or adb, not in this recovery.

Maybe @lj50036 would not mind to have a look at this? Josh, you listening? Any idea why TWRP would mess up all the mount points after a format?

 

[mikekoz]

Thanks. I was able to get it installed once I tried to format again. The recovery recommended I restart it. After I did, it did the wipe and format with no problems, the install went smooth, and it is running great so far!!

 

[GrouchyPunisher]

Tim,

One thing I've noticed is that wi-fi seems to turn off after sleeping, even though I have Keep wifi on during sleep set to Always. Does anyone else have this happening?

What's the best log to pull to give more info to you on this?

 

[andyB911]

First ROM I've put on my tf701t and its breathed new life into it!

All smooth bar the twrp mount issue but as above perseverance works. Many thanks... Donation sent.

 

[BeerGogglesFTW]

Tim,

One thing I've noticed is that wi-fi seems to turn off after sleeping, even though I have Keep wifi on during sleep set to Always. Does anyone else have this happening?

What's the best log to pull to give more info to you on this?

I have this issue too. I may have had this with stock as well, I don't recall. Luckily I don't often need it to stay connected while asleep but it is occassionally an issue. Never found a solution.

---------- Post added at 04:35 AM ---------- Previous post was at 04:31 AM ----------

Just wanted to say how happy I am that I switched from CM12.1 to KatKiss KM 033.

I originally went from stock to CM12.1 last year because it was acting up and missing features I wanted.
Recently CM was running slow, occassionally freezing, and simply not running that great... But I stuck with it because it was still better than stock.

With KatKiss I haven't noticed any hiccups, runs great, more features, and I swear I'm getting twice the battery life. Awesome stuff.

 

[Neccie]

New rom version available: KatKiss-6.0_TF701T_033.zip

Changelog:

- use cpusets
- move background tasks to higher cores

TF701 Kernel #004:
- Add ExFat support
- sync: don't block the flusher thread waiting on IO
- writeback: fix race that cause writeback hung
- writeback: fix occasional slow sync
- disable hotplug
- enable cpusets






6.0.1 "December" update is for the N5 and has a security patch level date of October...
We're currently on the November security patch level for the N6,
so until google fixes its tag and branch mess we'll stay on that



Try V033 & report

Fixed for video/media hickups! Yay super thanks!

Also here wifi goes off even when said to be always.

 

[blubba83]

Thanks for this Great Rom... Would be nice to see the 7.1 Version soon.
Where i Can get the right cifs.ko for the Rom? Maybe you can always put it into the next Versions.

Greetz from Germany, Tobias

 

[lj50036]

This is where it first reported, right in this thread: http://forum.xda-developers.com/showpost.php?p=69597289&postcount=26

I had the same thing happening, TWRP didn't want to mount anything after just formatting data. I only formatted /data to ext3 and then back to ext4 and rebooted recovery to fix it. Don't think cache matters. It's a bug in TWRP I guess...
Next time I want to format data, I would do it in fastboot or adb, not in this recovery.

Maybe @lj50036 would not mind to have a look at this? Josh, you listening? Any idea why TWRP would mess up all the mount points after a format?

I need LOGS!!!!!

I need a fresh boot log., a log after a full format, and a log after the next reboot to recovery...

Thx Josh

 

[silverchairbg]

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.

I get 10533 points in 3d Mark (on the ice storm extreme) on kit Kat 4.4.2 default Rom. Why would I want to update to CM 12 or MM besides being current. I never felt any annoying lag on this device so far (not alike tf700 where it became unusable with time..)

 

[racer290]

With KatKiss v33 I get 10720 points in 3d Mark (ice storm extreme). I'm very satisfied

Sent from my P9000 using XDA-Developers mobile app

 

[silverchairbg]

With KatKiss v33 I get 10720 points in 3d Mark (ice storm extreme). I'm very satisfied

Sent from my P9000 using XDA-Developers mobile app

Thanks for the reply. So it would seem recent fixes from Tim did bring the rom up to par with others. I guess the people that says things in the line of "thanks for bringing our device back to life" mainly refer to keeping it on current Android version.

 

[DarkPaLadin]

v033 seems to be more efficient in some games.

 

[Kashban]

I get 10533 points in 3d Mark (on the ice storm extreme) on kit Kat 4.4.2 default Rom. Why would I want to update to CM 12 or MM besides being current. I never felt any annoying lag on this device so far (not alike tf700 where it became unusable with time..)

You want to change to a newer ROM because of Security.

Every Android Version below 5 is considered highly insecure because of Bugs that won't get fixed anymore and as such pose a Threat to Everyone using it.

http://www.computerworlduk.com/secu...ld-versions-remain-big-security-risk-3633697/

With Katkiss you have the Option to update to a much more recent Version and from my Experience it's running very good in it's latest Iteration.

 

[racer290]

And don't forget, the KatKiss Rom is so much battery friendly, it's absolutely amazing. In all other Roms the battery life was terrible.

Sent from my P9000 using XDA-Developers mobile app

 

[andyB911]

Thanks for the reply. So it would seem recent fixes from Tim did bring the rom up to par with others. I guess the people that says things in the line of "thanks for bringing our device back to life" mainly refer to keeping it on current Android version.

I can comment as one of those people. Your mileage may differ but for me, v33 vs is notably quicker (vs stock). 3d mark ice store unlimited just gave a score of 16228.

Its less scientific but slither.io (i know... I know...) was lagging on stock, so I did a factory restore which didn't help and then installed this rom and now working fine. Personally not overly bothered about the security issues and if you aren't having performance problems then the gain is less obvious (and it does take an hour or two to work through the process).

Now wondering if there is something better than HairyBean for my old tf201...

 

[hitmancho]

After using this ROM after last Sunday evening, I'm happy to report that all previous problems I had with it are gone. It's a lot smoother now, and there are no stutters while playing anything which means it's 100% usable for me. I'd even say it's better than CM12.1 as far as performance and the better functionality of Marshmallow go. I can also confirm that the dock works completely fine with all the additions in the ROM. Other stuff like Xposed Framework (v87 for the security patch) and many modules work with 0 problems. Substratum works as well (only in RRO, is it possible to have OMS in the future?) with all modifications. I have Viper4Arise installed and it works perfectly as well.

The problems I saw first were that some apps FC when using the MultiWindow feature but that's completely understandable and not an issue for me (the apps in question were Firefox and Facebook getting squished). Also, it seems the battery is draining a bit faster while in use than before but that's also fine because it's not more by a large margin and I use my tablet in places with easy power access anyway . Another minor issue was attempting to use GravityBox to control the navbar. It still makes the buttons smashed together, no matter how I set them up, but that is a completely separate thing. Still, it'd be nice to have some extra cosmetic option in the ROM.

Other than that I haven't seen anything else NOT working in the ROM. I have no regular use FCs, no lags and stutters this time, the dock works without a hitch with USB drives and SD cards inserted into it, all playback is 100% fine, and the keyboard layouts and extra button functions are problem-free. I'm not sure how easy it was to get Tegra going . I do get an occasional 1 sec screen glitch when switching volume and pulling down notifications but it's rare (once a day for visible glitches). I do hope this ROM continues being developed and we'll get to see a Nougat ROM in the future that's just as good, if not better .

For now the biggest problem with using my tablet is the recovery, and only where wiping is concerned. Restoring backups seems to be doing OK, it manages to wipe the different partitions and restore them with no problems. Still, doing /cache wipes is still a bit painful .

 

[Jonbest]

Tim,

One thing I've noticed is that wi-fi seems to turn off after sleeping, even though I have Keep wifi on during sleep set to Always. Does anyone else have this happening?

What's the best log to pull to give more info to you on this?

I had this, in developer settings change dhcp to legacy. Did the trick for me! This appears to be more of a Marshmallow bug than anything to do with this particular rom.

 

[DarkPaLadin]

There is a problem with battery. The device is plugged in the charger, but it wont charge. The LED's are red on the tablet and on the keyboard-dock, but the tablet still says that it has low battery.
Screenshot: https://www.dropbox.com/s/glyy3ys2ztccji6/Screenshot_20161227-125436.png?dl=0

---------- Post added at 01:03 PM ---------- Previous post was at 12:57 PM ----------

Reboot and re-pluging of the wire helped. So I think it is a problem of the software.

 

[GrouchyPunisher]

I had this, in developer settings change dhcp to legacy. Did the trick for me! This appears to be more of a Marshmallow bug than anything to do with this particular rom.

Thanks Jonbest. I tried it and it did not do anything for me
@timduru - Trying to see what is different between this and the old 4.4.2 ROM I was running. I've been pulling logcats and comparing to some old logs I had stored from the KitKat build I had on here. One difference I see, is that I used to have a ton of D/WifiController (1434): Never sleep messages. Now, if I pull logs at any given time, I don't see any of those messages.

Not sure if that's just a change between version 4 and 6, or if that is something that is missing?

Thanks again for your work on this.

(Oh, regarding the previous post by @DarkPaLadin, I have not had any battery issues whatsoever with this ROM.)

 

[GrouchyPunisher]

Working now...

Thanks Jonbest. I tried it and it did not do anything for me

@timduru - Trying to see what is different between this and the old 4.4.2 ROM I was running. I've been pulling logcats and comparing to some old logs I had stored from the KitKat build I had on here. One difference I see, is that I used to have a ton of D/WifiController (1434): Never sleep messages. Now, if I pull logs at any given time, I don't see any of those messages.

Not sure if that's just a change between version 4 and 6, or if that is something that is missing?

Thanks again for your work on this.

(Oh, regarding the previous post by @DarkPaLadin, I have not had any battery issues whatsoever with this ROM.)

Ok, looks like I stumbled across a fix for this (at least for me), and @timduru , please tell me if this makes sense to you:

I had my governor set to OnDemand. I changed it to Performance, then rebooted, and my wifi has been up for the last 20 minutes with the screen off, while I stream Sirius radio (it was turning off after about 3-4 minutes before, shortly after the screen turned off.)

Tim, does that make sense? Is that the governor you're using?