I recently rooted my phone with Tweaked V2.2 (which I'm currently using with Transparent ICS, which looks and works amazing, by the way. Thanks for that!). It does occasionally start to lag over time and the battery starts dropping fast (which, realistically, is probably an app I have on there, I'll need to sort out which one it is later). I'm trying to look at ways to optimize the phone and I have read a decent amount about Voodoo lagfix helping with lag and battery life.
The question I had was, does Tweaked V2.2 w/PBJ come with Lagfix installed or is it something I need to add/activate? I apologize in advance if this is kind of a stupid question or if there's a fundamental understand I'm missing. I'm by no means a master with all this stuff and I'm still in the learning stage of all that I can do with a rooted device.
Thanks in advance!
jbrookley said:
I recently rooted my phone with Tweaked V2.2 (which I'm currently using with Transparent ICS, which looks and works amazing, by the way. Thanks for that!). It does occasionally start to lag over time and the battery starts dropping fast (which, realistically, is probably an app I have on there, I'll need to sort out which one it is later). I'm trying to look at ways to optimize the phone and I have read a decent amount about Voodoo lagfix helping with lag and battery life.
The question I had was, does Tweaked V2.2 w/PBJ come with Lagfix installed or is it something I need to add/activate? I apologize in advance if this is kind of a stupid question or if there's a fundamental understand I'm missing. I'm by no means a master with all this stuff and I'm still in the learning stage of all that I can do with a rooted device.
Thanks in advance!
Click to expand...
Click to collapse
I'm actually wondering the same thing. I just flashed to imoseyon's 4.0 kernel so i could convert to ext4 but im not to sure how? Does it do it automatically or is there anything i have to do? I plan to flash back to PBJ kernel after. (I'm really just trying to get wifi to work w Tweaked v2.2) but my phone is also very laggy as well.
As long as you don't have the file /sdcard/voodoo/disable_lagfix, it will automatically convert to ext4 on first boot. To be sure, install Voodoo Sound and check the options. There should be a lagfix section in the app if you are running a compatible kernel (imoseyon is the only one for GB).
If you flashed the version of Tweaked that is labeled as having ext4 conversion included, you shouldn't need this. You can always check your status by running terminal emulator, and typing 'su', followed by 'mount'. Scroll up in the list and find /system, /data, /cache, and /dbdata. They should be ext4 if you're converted. The rest will still be rfs.
shrike1978 said:
As long as you don't have the file /sdcard/voodoo/disable_lagfix, it will automatically convert to ext4 on first boot. To be sure, install Voodoo Sound and check the options. There should be a lagfix section in the app if you are running a compatible kernel (imoseyon is the only one for GB).
If you flashed the version of Tweaked that is labeled as having ext4 conversion included, you shouldn't need this. You can always check your status by running terminal emulator, and typing 'su', followed by 'mount'. Scroll up in the list and find /system, /data, /cache, and /dbdata. They should be ext4 if you're converted. The rest will still be rfs.
Click to expand...
Click to collapse
shrike is rarely wrong, however, I'm not so sure that installing the EXT4 version of Tweaked 2.2 will convert you from RFS to EXT4 (not saying that he is wrong, just don't know that is the case). the conversion takes places at the kernel level (I think). IMO's kernel makes the conversion (to/from EXT4/RFS), and I don't think dwith included that kernel is his ROM package (I could be wrong though).
if you want to convert from RFS to EXT4, try my guide posted here: http://forum.xda-developers.com/showthread.php?t=1763951
but first, make sure which version you have based upon shrike's recommendations.
jco23 said:
shrike is rarely wrong...
Click to expand...
Click to collapse
Yeah he's correct on this. The ext4 zip of the rom, from a /system perspective, is identical to the rom-only and with-kernel zips. The ext4 version does include a kernel (the same as what is in the with-kernel version), but it also includes the tools and script needed to format the usually-formatted partitions as ext4. The only difference between the ext4 and the with-kernel zips is the fact that the ext4 version has the formatting stuffs included.
Oops I made a dumb post.
Thanks for the help. Of course, after the matter, I found a detailed guide on google.If any other noob needs help just search "tonsit ext4" and it should be one of the first results from chargeforums, a post by jco on 10th July, 2012.
Hi guys,
for those of us who are waiting for at least the M1 of CM12 before switching lanes, I did a build of Carbon (and a few of CM11, previously) for our Photons.
This is an odexed ("user", not "userdbg") build, running on the cm-12.1 kernel branch and using the latest available f2fs_tools. It also features a modified init which can use either f2fs or ext4 for /cache and /data - so switching to f2fs is highly recommended, but not mandatory. Superuser is included.
This is esentially for those who switched to CM12 just for f2fs; it's miles faster than cm12, and a bit more responsive that the old official cm11 nightlies.
A word of warning. TWRP's "change filesystem" function formats the partition (PhilZ does too, but at least it makes that explicit).
So what you want to do when switching from an ext4 ROM is,
before you begin: copy everything in the internal sdcard somewhere on the external sdcard; this is needed, since the "internal sdcard" is actually a folder in /data;
in TWRP, begin by creating a backup of /data (that saves everything except the "internal sdcard" and /cache - that's why you need step #1);
do the FS change for both /data and /cache
restore the /data backup, on the freshly formatted /data partition; ignore the "different filesystem" warning, it's inconsequential;
install the ROM;
once you booted the phone, copy back the old contents of the internal sdcard
You only need to do this when you change filesystems, which will be exactly once if you like my ROMs And obviously, if you don't, you have to use the exact same procedure before flashing an ext4 ROM, if you don't want to lose data.
Though, in all fairness, I'd recommend flashing this cleanly - unless you're upgrading from an ext4 Carbon build.
A note on the radio
I have included a tool called radio-tool (of my own design) that allows people to enable/disable the US GSM lock and individual network bands;
if you're having the SIM mod, and are from, or have business in, the US, you can use it to kill the CDMA and Sprint LTE bands altogether, as well as to enable US GSM bands and disable the US GSM lock;
the source code is here
Use (as superuser)
Code:
radio-tool [dbg] [{+|-}opt [...]]
where opt is one of
uslock - US GSM lockout
cdma - CDMA bands (CDMA800 / CDMA1800 / CDMA2000 1xEV-DO)
usgsm - US GSM/HSPA bands (GSM850, GSM1900, WCDMA850, WCDMA1900)
eugsm - EU GSM/HSPA bands (GSM900, GSM1800, WCDMA900, WCDMA2100)
sprlte - Sprint LTE (LTE25, 1900)
vzwlte - Verizon LTE (LTE13, 700)
Download:
ROM: CARBON-KK-UNOFFICIAL_f2fs-20150526-moto_msm8960.zip
Recoveries: TWRP-2.8.6.0-20150526-f2fs-moto_msm8960_jbbl-xt897.img, PhilZ-6.59.0-20150520-crkk_f2fs-moto_msm8960_jbbl-xt897.
You do not need to use a su app with this; but if you want to, please use the latest SuperSU. Attempting to use a different, or older, su app could result in no radio.
Changes from stock Carbon:
alternative mount points support - this enables the ROM to work with either f2fs or ext4 for /data and /cache
tuned mount settings - kickass speed with both ext4 and f2fs
256MB of lz4-compressed swap space (zram0)
built on gcc-4.8-sabermod
build.prop tweaks - this defaults to GSM/WCDMA - plus a few radio and network tweaks;
added a few goodies that are present in CM builds (Term, Apollo, Calendar, CMWallpapers, VideoEditor, plus the cmdline utils);
removed the stats and the update apps (for obvious reasons)
added Romanian (programmers) keyboard support in Asanti Keypad
built with: twrp 2.8.6.0, cm12.1 kernel, cm12.1 f2fs-tools, cm12.1 e2fsprogs, cm12.1 exfat, cm12.1 fuse.
(this will allow me to pick up any improvements in kernel, file systems, and recovery, with great ease )
Quirks:
MTP doesn't start by default in TWRP, despite the fact that it claims to be enabled; disable and re-enable MTP, and it will work
in PhilZ' mount menu, entries for cache and data are duplicated; this is cosmetic - mounting and umounting works just fine, regarless which of the two entries for each partition you choose
.
Older, CM11 vanilla builds:
Download:
cm-11-20150427-UNOFFICIAL_f2fs-moto_msm8960_jbbl.zip - repo syncs, builds with TWRP, uses branch cm-12.1 of the kernel, uses latest available f2fs-tools
Use latest SuperSU with any of the CM ROMs - older, or different, su apps might make the radio not work.
NOTE. These ROMs are actually moto_msm8960_jbbl, so they should work on all devices for which official moto_msm8960_jbbl builds did, as long as they're still on the JB bootloader (jbbl) and you have a device-specific recovery that supports f2fs. A suitable PhilZ touch for non-xt897's can be found on the AtrixHD thread, courtesy of @palmbeach05, or you could use PhilZ-6.59.0-20150506-crkk_f2fs-moto_msm8960_jbbl-mb866 (note, despite the -mb866 suffix, it should work on any moto_msm8960_jbbl device except xt897).
The current repo is available here. To use,
repo init -u https://github.com/mionica/android.git -b cr_kk_gcc-4.8
repo sync
. build/envsetup.sh
breakfast carbon_moto_msm8960_jbbl
edit the .repo/local_manifests/roomservice.xml, changing the device project for android_device_motorola_moto_msm8960_jbbl to
Code:
<project path="android" name="mionica/android_device_motorola_moto_msm8960_jbbl" remote="mionica" revision="cr_kk_xt897" />
repo sync again
finally, (cd vendor/carbon && ./get-prebuilts).
After you do that, you're good to go - (optional) configure ccache (if it's your first build), (optional) enable ccache, choosecombo, then mka carbon 2>&1 | tee BUILD.LOG.
If you're not sure how to do any of these, either just use the provided ROM, or search on youtube for "building CyanogenMod" - that should help, I know it helped me Anyway, this thread is not the right place for learning how to build Android.
Mirrored for archival purposes.
This server WILL BE SLOW. You've been warned.
http://lionspaws.net/cm-11-20150401-UNOFFICIAL_f2fs-moto_msm8960_jbbl/
98e652a97965ba5d88cb9068fe7d4dbe *cm-11-20150401-UNOFFICIAL_f2fs-moto_msm8960_jbbl.zip
Using it for the last few days, seems good so far. Thanks
taking a break
Quick one. I'll take a break from this for now - my little sister's phone broke down, so she got my Photon. I just ordered one from the States today, but between that arriving and cornholiogsm doing the SIM mod, it might take a while (US to Ireland to Czech Republic to Ireland - and Tomas is pretty busy in my experience).
Thanks much for building this!
Forgive my ignorance, I've been using CM11 a while but other than the initial installation in which I followed wiki instructions, have only ever updated thru the phone. But since there hasn't been an update in a couple months, I'm considering installing this, particularly to solve the google service problems. If it makes the phone faster with better file system and ram stuff, that's a bonus, although concerned that might cause problems in the future. I don't fully understand what you mean by messed up build and odexed user stuff means. Basically I wonder can I just install this on top of the latest CM11 nightly without issues ("dirty flash")? My "recovery" is recovery-clockwork-6.0.4.4-xt926 clock but I only used that cuz that was what the wiki said, I've never used it since the initial install.
If the answer is yes, and I understand your post right, these are the install steps:
1. Download cm-11-20150408-UNOFFICIAL_f2fs-moto_msm8960_jbbl.zip
2. Download & install TWRP-2.8.6.0-20150408-cm11_f2fs-moto_msm8960_jbbl.img
3. Change filesystem of /cache and /data to f2fs using TWRP
4. Install cm-11-20150408-UNOFFICIAL_f2fs-moto_msm8960_jbbl.zip using TWRP
You said something about flash SuperSU alongside this. I don't recall having to do that before, can you provide a little more info?
Do I need to reinstall gapps, and if so, is it the same as I used before, gapps-kk-20140606-signed.zip?
And a couple more easy questions I could probably find by searching... how do I install that twrp....img file, can I do that thru clockwork... and how do I get into clockwork anyway, I remember it was holding some volume key during power or something but last time I tried to guess weird things happened with robots getting operations and such so if you happen to know the right keys/etc that would be convenient... will twrp replace clockwork and have the same keys to get boot to it, if not, what keys?
And last but not least... when CM11 M13 finally comes out, will I be able to upgrade to that from this, or perhaps because of the stuff you've taken from CM12 (f2fs/zram/etc) maybe I can't, or maybe I can if I set the filesystem back to default with TWRP first? How bout if one day I decide to use Lollipop (which I may never do anyway as I understand it's only recommended for phones with more than 1GB memory), will I be able to upgrade to CM12 the same way as regular CM11 user? I'd always used official stuff so this unofficial is making me nervous, but I really want my google stuff working right again and my battery to last all day like it used to...
Wait what wiki told you to use CWM for xt926!? CM's wiki?
enigma9o7 said:
Thanks much for building this!
Forgive my ignorance, I've been using CM11 a while but other than the initial installation in which I followed wiki instructions, have only ever updated thru the phone. But since there hasn't been an update in a couple months, I'm considering installing this, particularly to solve the google service problems. If it makes the phone faster with better file system and ram stuff, that's a bonus, although concerned that might cause problems in the future. I don't fully understand what you mean by messed up build and odexed user stuff means. Basically I wonder can I just install this on top of the latest CM11 nightly without issues ("dirty flash")? My "recovery" is recovery-clockwork-6.0.4.4-xt926 clock but I only used that cuz that was what the wiki said, I've never used it since the initial install.
If the answer is yes, and I understand your post right, these are the install steps:
1. Download cm-11-20150408-UNOFFICIAL_f2fs-moto_msm8960_jbbl.zip
2. Download & install TWRP-2.8.6.0-20150408-cm11_f2fs-moto_msm8960_jbbl.img
3. Change filesystem of /cache and /data to f2fs using TWRP
4. Install cm-11-20150408-UNOFFICIAL_f2fs-moto_msm8960_jbbl.zip using TWRP
You said something about flash SuperSU alongside this. I don't recall having to do that before, can you provide a little more info?
Do I need to reinstall gapps, and if so, is it the same as I used before, gapps-kk-20140606-signed.zip?
And a couple more easy questions I could probably find by searching... how do I install that twrp....img file, can I do that thru clockwork... and how do I get into clockwork anyway, I remember it was holding some volume key during power or something but last time I tried to guess weird things happened with robots getting operations and such so if you happen to know the right keys/etc that would be convenient... will twrp replace clockwork and have the same keys to get boot to it, if not, what keys?
And last but not least... when CM11 M13 finally comes out, will I be able to upgrade to that from this, or perhaps because of the stuff you've taken from CM12 (f2fs/zram/etc) maybe I can't, or maybe I can if I set the filesystem back to default with TWRP first? How bout if one day I decide to use Lollipop (which I may never do anyway as I understand it's only recommended for phones with more than 1GB memory), will I be able to upgrade to CM12 the same way as regular CM11 user? I'd always used official stuff so this unofficial is making me nervous, but I really want my google stuff working right again and my battery to last all day like it used to...
Click to expand...
Click to collapse
I agree with @arrrghhh you should use what your device maintainers recommend you use. I would also recommend you looking at what bootloader you have before trying this as there are KKBL builds in a different thread on I believe the RHD section. Odexed is like what you get from the manufacturer. It has .apk and odex files in it. odex assist the apk files. 6.0.4.4 is outdated, as 6.0.5.1 is the most recent. The install method you just recited is exactly what the OP just said. Per the OP, SU was not built into the 4/8 ROM, so you need to flash it as well. Yes you should be able to flash that Gapps, you just have to update your Gapps after finishing setup via playstore. Lollipop is able to be used on your device, as it currently has official builds. 5.0 had issues, 5.1 just got its official release yesterday. As far as unofficial builds go, I refer you to epinter and krystianp who both took an older device and provided unofficial updates that were very stable, despite the neverending work on a custom kernel. Furthermore, you can go talk to Quarx about unofficial builds, since his builds has been running the Defy for years. So being nervous about an unofficial build is like saying you're nervous about using a generic brand of something vs the more publicized item. Battery life will always be an issue if you have a bad setup (wifi and bt on all the time, max bright screen, hrs of listening to music or streaming, etc.)
@enigma9o7 Personally, I can't wait to do an unofficial cm11 build based on the cm11 m13 code base - with f2fs, and I expect, by then, zram (if it proves useful on cm11 at all - this thing works unreasonably well to begin with ). So I wouldn't worry about m13, as I'm pretty sure to release a parallel build on its side.
Now, I'm a bit impaired re. testing equipment atm but I have a mind to keep building this weekly or so anyway, while I judge the commits to be low-risk, and resume the riskier stuff once I get the new toy. Was away from Dublin this week, hence from my home PC , but that gets fixed tonight...
mionica said:
@enigma9o7 Personally, I can't wait to do an unofficial cm11 build based on the cm11 m13 code base - with f2fs, and I expect, by then, zram (if it proves useful on cm11 at all - this thing works unreasonably well to begin with ). So I wouldn't worry about m13, as I'm pretty sure to release a parallel build on its side.
Now, I'm a bit impaired re. testing equipment atm but I have a mind to keep building this weekly or so anyway, while I judge the commits to be low-risk, and resume the riskier stuff once I get the new toy. Was away from Dublin this week, hence from my home PC , but that gets fixed tonight...
Click to expand...
Click to collapse
One question i did have that i was wondering, when you built the kernel, did you set it up for GSM, CDMA, or both? I know we've talked via pm about things, but i've gotten it to boot up with your kernel, but no signal and baseband unknown
Sent from my ATRIX HD using XDA Free mobile app
palmbeach05 said:
One question i did have that i was wondering, when you built the kernel, did you set it up for GSM, CDMA, or both? I know we've talked via pm about things, but i've gotten it to boot up with your kernel, but no signal and baseband unknown
Click to expand...
Click to collapse
Mmm will have to check. For me it's working in the EU using GSM/HSPA on the xt897 with the SIM mod.
I used the stock config from the cm12.1 xt897 kernel - I'll have to diff that with the cm11 one.
Another possibility is that it wouldn't work because of SElinux mismatches between kernel and userland. The following has to be in the fstab:
Code:
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware ext4 ro,nosuid,nodev,noatime,nodiratime,barrier=1,[b]context=u:object_r:radio_efs_file:s0[/b] wait,check
If it doesn't, on the xt897 you get no WiFi, but I expect results might vary by device
All I'm saying is, it might or might not be a kernel config, would have to check when I get to my PC.
mionica said:
I used the stock config from the cm12.1 xt897 kernel - I'll have to diff that with the cm11 one.
Click to expand...
Click to collapse
I reviewed the entire changelog from cm-11.0 to HEAD, and couldn't find anything that looked even remotely radio-related, so I reckon it's most likely the SElinux thing. And now that I built a TWRP that has a chance of running on AHD, I guess you could tell me whether that's the case
arrrghhh said:
Wait what wiki told you to use CWM for xt926!? CM's wiki?
Click to expand...
Click to collapse
Yep, pretty sure. All started a year ago when I was looking for an android smartphone with a keyboard, this one was rated best, wikipedia itself said CM was required for kitkat, so looked into CM, found their installation wiki http://wiki.cyanogenmod.org/w/Install_CM_for_xt897 which step #2 is install clockworkmod recovery. Right now if I follow the link it leads to recovery-clockwork-6.0.1.3-asanti.img, but I'm pretty sure at the time I originally installed it lead to that version I used, which did work fine for installing CM as I do have it installed. But it's possible something else lead me to that version, I can't really remember for 100% sure, but I definitely started from CMs wiki.
---------- Post added at 10:17 AM ---------- Previous post was at 10:04 AM ----------
palmbeach05 said:
I would also recommend you looking at what bootloader you have before trying this as there are KKBL builds in a different thread on I believe the RHD section
....
The install method you just recited is exactly what the OP just said. Per the OP, SU was not built into the 4/8 ROM, so you need to flash it as well.
...
Yes you should be able to flash that Gapps, you just have to update your Gapps after finishing setup via playstore.
...
So being nervous about an unofficial build is like saying you're nervous about using a generic brand of something vs the more publicized item.
Click to expand...
Click to collapse
Thanks. My understanding is there is no KKBL for Photon Q anyway, but anyways I've always used the msm...jbbl roms.
Okay, will add installing SU to install steps.
Since I already have that version of gapps, my question is do I need to reinstall it then update everything. Shouldn't it already be good? I didn't have to reinstall gapps with the official nightlies, so want to know if I really need to for this.
My concern with unofficial is not that I dont trust it or think it's less stable, just that it may make it more difficult in future to upgrade or get back onto official path as I may not be able to follow the same steps as everyone else.
I'm still unsure if it's okay to dirty flash over CM11 nightly. I do actually use my phone for work so don't want to mess it up... but really want google stuff working again and can't keep waiting forever for official cm11.
enigma9o7 said:
Yep, pretty sure. All started a year ago when I was looking for an android smartphone with a keyboard, this one was rated best, wikipedia itself said CM was required for kitkat, so looked into CM, found their installation wiki http://wiki.cyanogenmod.org/w/Install_CM_for_xt897 which step #2 is install clockworkmod recovery. Right now if I follow the link it leads to recovery-clockwork-6.0.1.3-asanti.img, but I'm pretty sure at the time I originally installed it lead to that version I used, which did work fine for installing CM as I do have it installed. But it's possible something else lead me to that version, I can't really remember for 100% sure, but I definitely started from CMs wiki.
---------- Post added at 10:17 AM ---------- Previous post was at 10:04 AM ----------
Thanks. My understanding is there is no KKBL for Photon Q anyway, but anyways I've always used the msm...jbbl roms.
Okay, will add installing SU to install steps.
Since I already have that version of gapps, my question is do I need to reinstall it then update everything. Shouldn't it already be good? I didn't have to reinstall gapps with the official nightlies, so want to know if I really need to for this.
My concern with unofficial is not that I dont trust it or think it's less stable, just that it may make it more difficult in future to upgrade or get back onto official path as I may not be able to follow the same steps as everyone else.
I'm still unsure if it's okay to dirty flash over CM11 nightly. I do actually use my phone for work so don't want to mess it up... but really want google stuff working again and can't keep waiting forever for official cm11.
Click to expand...
Click to collapse
Yes, you can dirty flash this ontop of an existing CM11 after switching /data and /cache from ext4 to f2fs. Gapps will be fine since they install on the /system partition.
Sent from my ATRIX HD using XDA Free mobile app
Switched to Carbon, but preserved most of the goodies from CM; links in the first post.
Also added a note on how to hack your radio to disable CDMA/LTE - so you could go with this phone in the US and never register on Sprint's network (unless they have a GSM/WCDMA network in place too, which should be fine).
I decided to give it a try with your latest CM11. I installed the TWRP from your first post, was able to backup fine, but don't see how to reformat as f2fs....
enigma9o7 said:
I decided to give it a try with your latest CM11. I installed the TWRP from your first post, was able to backup fine, but don't see how to reformat as f2fs....
Click to expand...
Click to collapse
There should be an option to wipe things, go there
Sent from my ATRIX HD using XDA Free mobile app
palmbeach05 said:
There should be an option to wipe things, go there
Click to expand...
Click to collapse
Thanks, found it.
And now I'm stuck. But I bet it's an easy solution.
I changed filesystems, restored data & cache, installed cm (04/27), installed superuser (wasnt sure if needed, but figured it couldnt hurt), and I booted.
No wifi or phone service but I'm hoping the last step will fix that, restoring sdcard0. However, I can't figure out how to copy that back. I used ES File Explorer to copy it to a folder in sdcard1 before I started. But now I can't paste it back to /storage, always told copy fails. There is a 0 byte file called sdcard0 there, if I delete it, it comes back. Since it's not a directory I can't change to it and copy the contents of my previous save into it... I tried deleting it and making a folder called sdcard0 before it recreated the 0 byte file but that failed too.
I thought maybe I'd try command line, but I'm no expert there... I su'd and tried similar things as in EX but similar results.
I thought I'd try to copy it back with TWRPs file manager, but I couldn't figure out where to put it, there was no /storage directory, so I tried putting it in / and that started copying for a while but before it was done it rebooted and just hung at the TeamWin screen until I powered off...
So yeah. Dunno how to restore sdcard0. Help please....
edit: maybe superuser doesn't work? I tried to use default "file manager" and it wont let me switch to root mode. Then I noticed that while trying ES File Manager again I didnt see the popup about "root granted" or something like that that I normally see. But superuser is installed, its in the apps menu and runs and a quick look thru the settings seems okay to me, but I don't recall ever setting anything before.
edit2: I'm giving up and going to try to go back to last cm11 nightly and hope my phone starts working again. I tried reflashing multiple times, eventually tried supersu instead of superuser and that worked to get root explorer working, but I still couldn't copy over sdcard0 using ES anyway, but using default filemanager I could start (although I hate that filemanager cuz I dont know how to change directories, usually have to tap about 15 times before it opens a folder), but it would always start then reboot before it finished. So I still dunno how to copy that back.
enigma9o7 said:
No wifi or phone service but I'm hoping the last step will fix that, restoring sdcard0. However, I can't figure out how to copy that back. I used ES File Explorer to copy it to a folder in sdcard1 before I started. But now I can't paste it back to /storage, always told copy fails. There is a 0 byte file called sdcard0 there, if I delete it, it comes back. Since it's not a directory I can't change to it and copy the contents of my previous save into it... I tried deleting it and making a folder called sdcard0 before it recreated the 0 byte file but that failed too.
Click to expand...
Click to collapse
Superuser is probably not a smart choice on KK. Use SuperSU instead.
The very first boot is somehow handled differently - I discovered this when I worked on integrating SuperSU into a catch-all zip of mine (alongside Windows Mobile ringtones, Midnight Commander, patched hosts, and a few other goodies). I got no radio with my package, but if I flased SuperSU instead, it worked.
It took me a coupe of tries to find the culprit - a flag file in /etc that SuperSU created after the first boot (and I attempted to create that from my zip). Made my zip not create that, and bang! everything worked just fine. Btw, removing that file after the first boot had no effect, the phone'd be screwed until you wiped /data.
Now, the fact that SuperSU handles the first boot differently kinda makes me think that older su's might very well not work (properly) on KK - and what you're reporting seems to confirm that.
I would strongly suggest going Carbon instead; that includes a working su. It's essentially CM with a different boot logo and a good few extra customization options (which you can safely ignore if you're not into that sort of thing).
So if you didn't go back yet, try either
flashing carbon and being done with it, everything will work;
flash the cm rom alongside supersu, not any other root app,
Either way, root will work, phone will work, and you'll be able to copy stuff around to your heart's desire.
As for a FM, I strongly suggest an app called Total Commander. The UI is atrocious as of late (the author is obviously better at coding than designing icons ), but it' probably the most complete FM solution for Android, bar none. And it's free, without adds; wait til you try it in landscape
I'm sorry for you inconvenience, but I also somehow feel it's earned - the OP said SuperSU back before Carbon replaced CM; because that's what I was using, and it worked for me - no guarantees if you went your own way. I've re-added the limitation and made it bold+orange in the CM part of the post (Carbon has its own, fully working, su).
Added the 2015.05.03 build of Carbon; links to 2015.04.30 removed.
At this stage, CM users should have everything they liked about CM, already compiled in (except for WhisperPush, the point of which I don't quite see).
Changelog from 2015.04.30:
added Calendar (!!!) - why on earth would the Carbon guys build an ROM without this?!
built on gcc-4.8.x-sabermod-20150429
added CMWallpapers, Video Editor
added the previously-missed vim, unrar, zip and gdbserver
synced with upstream; in particular, there was a noteworthy GPU memory allocation improvement in the kernel
Todo:
add an app for messing with the NV settings (enable/disable bands, enable/disable US GSM lockdown)
enable zram.
Added the 2015.05.05 build of Carbon; links to 2015.05.03/04 removed.
Changelog from 2015.05.04:
set default governor to msm-dcvs - better out-of-box performance
imported the cm-12.1 init support (including swap enabling)
Changelog from 2015.05.03:
support for fstab alternatives, cm12-style (my own code in fs_mgr); now you can use the ROM with either f2fs or ext4 for /cache and /data
massively improved FS performance for both ext4 and f2fs - tuned the fstab settings for best performance;
added radio-tool to enable/disable US GSM lock and groups of radio bands (CDMAs, US GSM/HSPA, EU GSM/HSPA, Sprint LTE, Verizon LTE) - see spoiler in first post
Todo:
figure out why swapping doesn't want to start, despite the device being there and mkswap succeeding (error -16).
Updating the recovery to a 20150505 build is highly recommended.
This kernel was built originally only for private use, but some of you have asked for it so I've decide to share.
I'm not responsible: You use at your own risk.
This kernel is based on latest LineageOS source code, with only a few tweaks in config file and maybe any external commit. It's more a "proof of concept" than a development by itself. My philosofy is "keep it simple"... I don't look for a "overloaded super-kernel with steroids"... if you want many features (exotic governors, OC, etc...) and "bleeding edge" functionalities there are some good alternatives made by good devs here so this kernel is not for you. Maybe other kernels can benefit by this approach in the future.
The approach for BitO-K is a light and stable kernel optimized via some basic params in kernel config and built with latest Toolchain (TC) to get a very optimized code for our device's architecture.
Fronts attacked: Task scheduling (SMT enabled), task efficiency (CleanCache/FrontSwap and other minor tweaks) and IO optimization (the only commit you can see ATM in my source branch) and, depending on version, latest Toolchains from Linaro or UBER. ATM no more "magic"...
*In my personal device I'm also testing with /data and /cache partitions on F2FS instead of EXT4 (this also helps...). Maybe new thread in the future about this...
Download
You can get latest version here.
Installation
Make backup
Install via TWRP
Wipe Dalvik/Cache
Reboot and profit
Notes
You can disable thermal control bins from xiaomi to avoid some lag if you get your CPU hot... Revise your config to be sure you don't get a brick...
You can install on any ROM, but if MIUI based, then you can get some features not to work, like WIFI, etc... If you want to test on MIUI, you have info here, thx to @Hen Ry
How to delete thermal control binaries by Xiaomi
You need root permissions (I suggest Magisk 13.6+)
Go to /vendor/bin
Delete (I suggest to move to a backup folder into /vendor/bin or rename files, not delete):
perfd
thermal-engine
Additonally you can delete (or move/rename to *.bak) file:
/etc/thermal-engine-8996.conf
My Kernel Settings (Kernel Adiutor)
Not necessary the best ones, only the ones I usually set (battery/performance balanced, smooth behaviour, almost total lag free):
CPU BIG MAX: 1900 MHz
CPU LITTLE MAX: 1440 MHz
GPU MX: 560 MHz
Governor: Interactive
Other minor tweaks (sometimes I set them):
IO: Disabled statistics
...
Source Code
https://github.com/BitOBSessiOn/android_kernel_xiaomi_msm8996
How to convert FS's from EXT4 to F2FS (IO performance improvement)
Be prepared to break it all... Again: at your own risk
Your TWRP must support F2FS (look for my latest TWRP-MROM )
Your kernel (on primary or secondary) must support F2FS (usual if LineageOS based)
Your system (on primary or secondary) must support F2FS mounting (fstab.qcom file updated with F2FS entries for /cache and /data ) (usual if LineageOS based)
Make a backup of ALL your data you want to keep (/data partition via TWRP backup + DCIM, WhatsApp folder, etc... ) (I suggest copying/backup via USB from TWRP)
In TWRP go to: Wipe / Advanced Wipe / Change or repair file system / Change file system for /cache and /data and select F2FS
Restore your /data partition from TWRP backup and manually copy your extra folders (DCIM, Whatsapp, etc...)
Reboot and profit
Testing! :highfive:
Behaving awesomely both on RR and AICP, the two roms I've tested it so far with some minor kernel auditor tweaks.
Thanks dev!!!
Awesome with @marchetto96 ViperOS!!
Testing with LOS. So far so good. Thanks Dev
albertoduqe said:
Behaving awesomely both on RR and AICP, the two roms I've tested it so far with some minor kernel auditor tweaks.
Thanks dev!!!
Click to expand...
Click to collapse
Hello Mate. May I please ask if you can share the tweaks / config in Kernal Audiutor ?
It's all placebo or its doing its job very well and very quietly. Either way, its not breaking anything or making anything worse, so bravo.
VerucaSalt said:
Hello Mate. May I please ask if you can share the tweaks / config in Kernal Audiutor ?
Click to expand...
Click to collapse
Governors to interactive. CPU max to 1900 and 1440, GPU max to 560. Thermal bins deleted.
It's not my idea though, I just learnt and copied from the boss
Happy tweaking!
Sent from my MIX using Tapatalk
albertoduqe said:
Governors to interactive. CPU max to 1900 and 1440, GPU max to 560. Thermal bins deleted.
It's not my idea though, I just learnt and copied from the boss
Happy tweaking!
Sent from my MIX using Tapatalk
Click to expand...
Click to collapse
How to delete thermal bin?
rhong said:
How to delete thermal bin?
Click to expand...
Click to collapse
OP updated with little howto.
How to jump from EXT4 to F2FS
Second post updated with a little guide: How to convert FS's from EXT4 to F2FS (IO performance improvement)
BitOBSessiOn said:
Second post updated with a little guide: How to convert FS's from EXT4 to F2FS (IO performance improvement)
Click to expand...
Click to collapse
Cheers. I'm going to try this F2FS mod out but it's going to take forever just to copy everything off my phone (256GB model, almost full). If I switch data to F2FS will it kill the encryption (I don't want it to be encrypted anyway)? If not, I may as well get rid of it now when all my personal files are backed up to my PC.
gavin19 said:
Cheers. I'm going to try this F2FS mod out but it's going to take forever just to copy everything off my phone (256GB model, almost full). If I switch data to F2FS will it kill the encryption (I don't want it to be encrypted anyway)? If not, I may as well get rid of it now when all my personal files are backed up to my PC.
Click to expand...
Click to collapse
Ummhhh.. I always assume an unencrypted scenario... but indeed you lose encryption when reformatting to another FS, you must re-encrypt after formatting (target FS must be encryptable).
BitOBSessiOn said:
Ummhhh.. I always assume an unencrypted scenario... but indeed you lose encryption when reformatting to another FS, you must re-encrypt after formatting (target FS must be encryptable).
Click to expand...
Click to collapse
I copied everything off, took a backup of data in TWRP and copied it to the PC too. Wiped data/cache, changed both to F2FS and rebooted into recovery. Copied the data backup back to the phone and restored (gave a warning about it being from an EXT4 source but it restored ok). Rebooted into Resurrection Remix and in the settings it still says it's encrypted. To get it decrypted I had to use the 'Format Data' option in TWRP (as opposed to ticking data and wiping it).
Between the new kernel, some tweaks in EX Kernel Manager (mainly ondemand governor for CPU and performance for GPU), and decryption, I'm getting the highest Antutu scores I have for months. Just got 156k (60477/53925/31252/10475). Now I just have to wait while it copies 200GB+ of stuff back to the device.
gavin19 said:
I copied everything off, took a backup of data in TWRP and copied it to the PC too. Wiped data/cache, changed both to F2FS and rebooted into recovery. Copied the data backup back to the phone and restored (gave a warning about it being from an EXT4 source but it restored ok). Rebooted into Resurrection Remix and in the settings it still says it's encrypted. To get it decrypted I had to use the 'Format Data' option in TWRP (as opposed to ticking data and wiping it).
Between the new kernel, some tweaks in EX Kernel Manager (mainly ondemand governor for CPU and performance for GPU), and decryption, I'm getting the highest Antutu scores I have for months. Just got 156k (60477/53925/31252/10475). Now I just have to wait while it copies 200GB+ of stuff back to the device.
Click to expand...
Click to collapse
Battery? Stability? Smoothness...? Thx for feedback
BitOBSessiOn said:
Battery? Stability? Smoothness...? Thx for feedback
Click to expand...
Click to collapse
I always found ondemand to give the smoothest experience and that's exactly what I'm getting here. It feels like being back on MIUI (that's a good thing).
I can't give any input battery-wise as I'm rarely away from a charger and don't care about battery life (within reason obviously), so I never monitor it.
As for stability, I did temporarily lose WiFi connectivity (other network devices were fine), and when that dropped out I lost mobile data too. This happened when I was transferring the last batch of files I forgot to restore via USB. I've been using RR for weeks and it has never happened before, but it could just be a one-off. It took a reboot to resolve.
I have noticed the device can get very warm when transferring a large number of files over WiFi. It has always been like that regardless of kernel. I had the case on when I lost connectivity so I couldn't feel if it was that warm, but maybe that sustained high temp buggered the WiFi. If it happens again I'll let you know.
I should note that I had the thermal files removed (I've always deleted them from I first got the device). I also usually run the OC'd DragonXia kernel so my device is no stranger to a little extra heat.
I'm using it for a day now. so far so good. Latest Mokke rom, working flawlessly. using ondemand governor with stock clocks, CFQ and I/O Scheduler with 2Mb read ahead value.
only odd thing I have noticed so far is that WiFi signal seems to be a bit weaker. In places that I had connectivity before, now I'm not in range.
Otherwise all good! Keep up the good work, and thanks man!
BitOBSessiOn said:
How to convert FS's from EXT4 to F2FS (IO performance improvement) (-- WIP --)
Be prepared to break it all... Again: at your own risk
Your TWRP must support F2FS (look for my latest TWRP-MROM ) -- perhaps 4/128GB pending, WIP --
Your kernel (on primary or secondary) must support F2FS (usual if LineageOS based)
Your system (on primary or secondary) must support F2FS mounting (fstab.qcom file updated with F2FS entries for /cache and /data ) (usual if LineageOS based)
Make a backup of ALL your data you want to keep (/data partition via TWRP backup + DCIM, WhatsApp folder, etc... ) (I suggest copying/backup via USB from TWRP)
In TWRP go to: Wipe / Advanced Wipe / Format Partition and select /cache and /data and format to F2FS
Restore your /data partition from TWRP backup and manually copy your extra folders (DCIM, Whatsapp, etc...)
Reboot and profit
Click to expand...
Click to collapse
my rom is aicp,after converted，i can not mount the data,but the speed is really fast
315602494 said:
my rom is aicp,after converted，i can not mount the data,but the speed is really fast
Click to expand...
Click to collapse
Weird... seems that AICP does not include F2FS entries in fstab.qcom file...
If I have time I will try to make a zip to inject updated fstab.