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

timduru

Senior Member
Apr 13, 2011
2,878
18,007
0
New Rom Version #031

New rom version available: KatKiss-6.0_TF701T_031.zip

Changelog:

TF701:
- Fix Autorotation
- Fix widevine DRM
- Fix Bluetooth (for bluetooth audio devices that have "phone audio" capability you need to uncheck the box in the bluetooth device settings)
- powerHAL: reimplement replacement base HAL for raydium
- powerHAL: add more perf boosts
- enable doze


TF701 KatKernel v002:
- tweak for more perfs
- reuse nvidia exclusive raydium touchscreen sleep pm
 

hitmancho

Senior Member
Jun 18, 2011
68
16
28
I managed to get the ROM working after some issues with formatting my partitions. This recovery really needs an update...

My brightness levels are constantly changing/flickering, even though I have adaptive brightness disabled in my settings. I know the light sensor in the tablet is buggy and always causes flickering, but now the flicker is ALWAYS there. Anyone else have this issue? Also, the interface and performance feels a bit laggy. Will it get better after the ROM settles in?
 

erzherzog

Senior Member
Mar 6, 2015
86
27
38
My brightness levels are constantly changing/flickering, even though I have adaptive brightness disabled in my settings. I know the light sensor in the tablet is buggy and always causes flickering, but now the flicker is ALWAYS there. Anyone else have this issue? Also, the interface and performance feels a bit laggy. Will it get better after the ROM settles in?
I can't confirm that. No flicker here. And it doesn't matter whether adaptive brightness is on or off.
 
  • Like
Reactions: timduru

timduru

Senior Member
Apr 13, 2011
2,878
18,007
0
I managed to get the ROM working after some issues with formatting my partitions. This recovery really needs an update...

My brightness levels are constantly changing/flickering, even though I have adaptive brightness disabled in my settings. I know the light sensor in the tablet is buggy and always causes flickering, but now the flicker is ALWAYS there. Anyone else have this issue?
No problems for me either,
if adaptive brightness is off in settings it doesn't rely on the sensor, so the brightness level is staying constant and shouldn't flicker.
It kinda sound as if something is bad with your installation.
You mention that you had issues formatting ?
Are you sure that it effectively formatted data and that you don't have left overs from a previous rom ?
That could definitely bring that kind of issues if settings are mixed up.

Also make sure that if / when you restore things that you never restore system apps / settings.
Overall if I were you I'd try to reinstall.
format /data
flash the rom + supersu + gapps in one shot
wipe cache
reboot.
In the setup process do not choose to restore apps and see if that helps.
That way you have a full clean setup.
As for lagging, I have no lags on 031 here with a fresh install and my main apps restored.
(performance on 030b were not as good, so it also depends which version you installed)

But after a fresh install it takes a bit of time to settle, it also depends what you restore and if you have lots of medias in your storage.
As apps are going to update and mediascanner is going to scan everything all around.
One of the first thing I do myself is set a mediascanner "white list" filter to /system/media and reboot
that way it doesn't scan everything all the time ;)
and I simply use a filemanager to open media I want :)
 
  • Like
Reactions: Sasisco

hitmancho

Senior Member
Jun 18, 2011
68
16
28
My problems with formatting were rather weird. I started by formatting my caches, which is always an issue with /cache not wanting to mount properly when formatting into ext4. What I always do is: format /cache into ext3, ext2, fat, and the back to ext4 where it finally works. After that I wiped /system with no issues, as well as /data. After that I tried the Format Data option from the Wipe menu, which wipes internal memory plus /data (?) but it just hanged and then it gave me an error and told me /data may not be mountable. Sure enough, after rebooting my recovery, /data had to be reformatted into ext3 and the back into ext4 to be mountable and usable. After that my internals were clean (including my internal storage) with the only space taken up by each partition being some sort of "backup size". I then proceeded to install your ROM but it took a while and then it gave me an error with the /system mountspace being busy. I realized I had accidentally left /system mounted in the recovery, so what I did was I reformatted /system back into ext3 then into ext4 after rebooting the recovery so it could be mountable. Then I just wiped all my partitions (caches, /system and /data) to make sure the ext4 command was working properly and indeed it was. I checked up on my internal storage and saw it was empty, save for the TWRP dir where the recovery keeps its settings. I made sure I didn't leave /system mounted and then I flashed the ROM again. It still took a while to flash (some minutes) but it was successful. I then flashed SuperSU which was fast, then I flashed nano GApps, which took a while as well, after which I wiped dalvik and /cache for good measure again (they ran fine, without issues). After that I restarted the tablet and the ROM started booting. It took a couple of minutes, like it says in the guide, then it started optimizing apps, which was surprisingly fast (there were 47 apps, if I'm not mistaken). Then the ROM started and I did the setup wizard, without restoring anything AT ALL, just logging in with my account. I noticed that it was quite laggy on that menu, but I guessed it was to be expected. After that I started playing around with everything (interface, etc.) and I noticed my screen flickering like with auto brightness left on. I had reduced my brightness to the minimum, seeing as it was nighttime, so I decided to raise it a little bit, since it was actually darker than CM12.1 (adaptive brightness was never on the whole time, I tried switching it back on to see if something would "reset" and then turning it off, it didn't help). My brightness kept moving around a few levels on its own, not matter how I set it up. I decided to use the tablet for a little bit, leave the ROM to settle in before installing anything. It kept doing a strange stutter on most of its menus, and some apps took 5+ seconds to open. I decided to let it do its thing and after installing an app or two I rebooted it. Note, I didn't have any media on my tablet whatsoever, considering it was wiped all the way. I installed a few apps, decided to reboot the tablet. It booted fast enough but the interface and app lag persisted. After that, for the heck of it, I decided to install Xposed framework (the one for Marshmallow, ofc). It worked without a hitch but the moment I decided to install a module and then start it and reset the tablet it just ended up in a bootloop. I gave up after that and decided to restore my previous installation. It went without any problems and it ran as before, but at least I cleaned up all my internal storage's empty dirs and whatnot :D.

How would you recommend I wipe and install the ROM, seeing as how I'm the only one having these issues? It was probably caused by all that wiping and failing to mount shenanigans (I sure hope my flash storage isn't dying or anything). I might try the ROM back again in some days, since I have work to do now and I don't have time to mess with it for too long, and I might even need it. I really want to try this ROM, since it's MM and has all these functions that really make life easier, but something is going wrong on my end :D.
 

timduru

Senior Member
Apr 13, 2011
2,878
18,007
0
How would you recommend I wipe and install the ROM, seeing as how I'm the only one having these issues?
Just like it says in the installation instructions ;)
definitely not the way you did ;P

It was probably caused by all that wiping and failing to mount shenanigans (I sure hope my flash storage isn't dying or anything). I might try the ROM back again in some days, since I have work to do now and I don't have time to mess with it for too long, and I might even need it. I really want to try this ROM, since it's MM and has all these functions that really make life easier, but something is going wrong on my end :D.
Could be the formatting that corrupted something yeah, might have some scan going on in the background.

Another difference I see is that I use pico gapps, maybe try it with pico next time.
Maybe there's something in nano that goes crazy.
For the brightness I just don't see why, if adaptive is turned off the level stays constant. So that would indicate that turning off the setting didn't work for your setup,
but I don't really see how it's possible.
Or maybe it was not able to save the setting because of data partition corruption if that's your root issue maybe.. difficult to say.

When you try again and if it happens again, grab a full set of logs as indicated in the "How to report" link
Maybe I'll spot something.
 

hitmancho

Senior Member
Jun 18, 2011
68
16
28
So I should just use the "Format Data" option in the main Wipe screen of TWRP for a full wipe (internal storage included)? Because what I've always done is to just go to Advanced wipe and pick all partitions (both caches, /system, and /data) and just swipe-to-wipe. This has also always lead me to problems with some partition (mainly /cache) always failing to format with ext4 and having to reformat it into another FS and back to ext4 to work again. I learned to live like that :D with this recovery - some partition never manages to wipe properly. Have I been doing it all wrong?!
 

erzherzog

Senior Member
Mar 6, 2015
86
27
38
Seems everybody tries to find his own way to circumvent the deficiencies of this recovery.

I newer wipe partions. I always reformat /system, /cache (and /data - if necessary :((( ) with an ext4 file system.
Before reformatting I always unmount all partitions.
In case the recovery complains about a partition - unable to mount - I reformat that portion ext3 and then ext4 again.

And yes, flashing KatKiss behaves a bit strange. Seems it only works on a freshly formatted unmounted /system partition.
 
Last edited:

erzherzog

Senior Member
Mar 6, 2015
86
27
38
I don't use xposed myself,
but I just flashed xposed-v86-sdk23-arm.zip + XposedInstaller_3.1.1.apk
and it booted fine for me and the app reports that the xposed status is active.
Same here. But the situation changes, when modules are activated.

I'm not a fan of Xposed. It gives more trouble than benefit. Most ROM creators refuse to support Xposed. Therefore I don't care if Xposed doesn't work for this ROM.
 
Last edited:

Jerry1996

Member
Oct 7, 2013
26
14
0
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!
 
Last edited:
  • Like
Reactions: timduru

erzherzog

Senior Member
Mar 6, 2015
86
27
38
If I plug in the power cable to the screen, the tablet battery isn't charging.
I need to connect screen and keyboard and plug in the power cable to the keyboard. Then both get charged.

Might this be related to the ROM or does the hardware starts dying?
 

Kashban

Senior Member
Oct 25, 2009
502
44
0
www.kashban.de
And yes, flashing KatKiss behaves a bit strange. Seems it only works on a freshly formatted unmounted /system partition.
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.