yashsingh1/xdaforums huggingface dataset:
[Motorola Photon Q 4G LTE] enigma9o7:
1 . Resistance to change mainly. CM works well for me and over time have got everything setup exactly how I like, so see no need to mess with it. The time I did try installing your carbon, lots of errors came up anyway about stopped services, plus the homescreen looked different, don't want to debug more problems or learn how to use something different when everything is fine with CM. Unsure if all apps will work, what apps are missing or added, what settings differences there might be, etc, and dont want to take time to figure it out. etc etc.

2. CM has Bigger userbase, more support, and seems more "official". II tend to do a lot of web searching when looking for help, etc. Lot more info about CM than carbon.

3. Don't want to stray from the path so future upgrades to CM not so complicated...

I'm sure carbon would be perfectly fine if I clean installed and took the time to set it up. The only reason I wanted anything was to fix the google services bug as I'd get errors in g+ and my battery was draining too fast. Those now solved with your CM build.
[Motorola Photon Q 4G LTE] mionica:
Not sure you caught the previous post; if you want CM, I would suggest trying to run it on the "Carbon" kernel (which is 100% the same as the CM one - actually, Carbon is 85% CM :p)

If you're interested, just extract boot.img from the carbon zip and flash it from Boot loader / AP Fastboot mode by running, on the PC,

fastboot flash boot boot.img

You need fastboot (which is readily available), and if you're not happy with it, you can just flash boot.img from the CM zip the same way, to go back. But I reckon you'll find that performance with the latest boot image is kickass compared to what boot image I got into the last CM build provided. And yes, it is as simple as that - no need to backup anything, no need to do anything else, no need to enter recovery at all; it's flash-and-go.

Oh, I also strongly suggest flashing the most recent TWRP (or PhilZ, if that's your fancy) - I've cleaned up the build of those a lot since the last CM build. I was still learning how this all worked, back then :)

The reason I'm suggesting this is, the big perks of my Carbon builds (support for both f2fs and ext4, lz4-compressed swap, default governor set to msm-dcsv, optimized FS parameters) exist at linux level, below Android - and are conveniently located in the boot partition. So you'd reap the largest benefits that my builds provide, without disturbing CM in any way; and btw, AFAIK, this is the only cm11-based build with those two features, across the board (they were introduced in cm12.0 - which inspired me to backport them :D; or, when merging wasn't feasible, to reimplement - the mount alternatives case, in android_system_core).

This is temporary btw; I'll do a CM refresh sometimes in the next weeks; unfortunately, I hard bricked my xt897 two days ago (while trying to increase /data by another 1.2G by decreasing the sizes of /cache and /system :p), and it'll probably be some two weeks before the replacement I ordered arrives in Ireland.
[Motorola Photon Q 4G LTE] enigma9o7:
Thanks again. I fastboot flashed the carbon 05-06 boot.img onto phone with your 4-27 CM and indeed it was as simple as described. Will probably notice increased performance when I do something with it, although this is the only smartphone I've ever owned so never really noticed it slow before (as nothing really to compare to).

In regards to TWRP, are you saying there's more than one build of 2.8.0.6, or that you recommend newer version than 2.8.0.6, or that 2.8.0.6 is the most recent? When I first started trying to install this just over a week ago, I installed the 2.8.0.6 you had linked in the first post... which seems to work fine, other than what you pointed out about mtp enable/disable, and of course that it force re-formats /cache to ext4 when restoring backup if previously changed to f2fs.
[Motorola Photon Q 4G LTE] mionica:
Ummm yes, that's why I date them? :)

Nonwhitstanding the fact that version numbers don't change with every code change :), referring to TWRP is indeed a beet misleading; I should've said, "recovery partition" instead.

Here's how this works: that partition has its own kernel, its own "root" file system, and is a completely separate build of everything recovery-related (of which, the actual TWRP application is only one item). This kinda means that, if any updates in the recovery ecosystem happens, chances are, the recovery application would alse be affected. And besides, I've picked up at least two change in the source code of TWRP since the CM build, none of which changed the version number ;) - but I'm thinking more about the changes I made to the init code and the filesystem tools (for instance, the CM TWRP runs on an older version of the F2FS filesystem than the current one).

So yeah, I'd seriously suggest to update. And just for the crack, try the /cache thing once more on this latest and greatest; I'm not sure I understand why /cache would be formatted behind your back, ever (and if TWRP claims it had formatted it once again, just change FS after that to f2fs anew, and be done with it). Either way, I'd appreciate some "it works now" / "does the same" feedback. I can think of a number of things that could've caused that, only one of which actually having a root cause in the TWRP thing itself :)
[Motorola Photon Q 4G LTE] enigma9o7:
Ok, understand the TWRP img you create is more than just TWRP. Hadn't really even paid attention to the full filename, but makes sense and see the date there.

So since you wanted feedback, after installing your latest twrp (05-06) I tried restoring my previously backed up ext4 cache to current f2fs cache (as an experiment only, I dont actually need or care about that anymore), and result was the same, still reformatted it to ext4.

It behaved similarly when done vice-versa. Before I started messing with things again, I made a fresh backup in TWRP, so had a f2fs version of cache backed up. When I tried restoring that to the ext4 formatted cache, it reformatted it as f2fs ("formatting cache using mkfs.f2fs...").

I attached the full log FYI. It should show full backup, restore cache from an old backup (and turning it ext4), restore cache from recent backup (and turning it f2fs).
[Motorola Photon Q 4G LTE] Nuck-TH:
Maybe i have done something wrong, but yor TWRP stops phone charging from usb.

Oops, seems like false alarm.
[Motorola Photon Q 4G LTE] robobub:
The rom seems to be working nicely on my Atrix HD. I really appreciate getting F2FS working, as I was going nuts waiting for AT&T to release KKBL for my phone.

Could you add in the ability to adb shell into the recovery? It's worked on other recoveries for me, but when I try it on PhilZ-6.59.0_f2fs_20150506, it complains about not being able to exec /system/bin/sh
[Motorola Photon Q 4G LTE] mionica:
Will co, but it'll take a while (I'm out of testing equipment ATM - briked my photon recently - I should get another one within a week or so).
[Motorola Photon Q 4G LTE] palmbeach05:
Thanks for the heads up on this, this wasn't something that i had tested yet, so i wasn't able to report it up to [MENTION=1103233]mionica[/MENTION] thanks for taking the initiative and passing the issue up to him

Btw, since you have the AHD too, does torch work for you? I reported an issue up, but i'm not sure if its hw related or ROM related.

I'll post a link in a few about something with a KKBL ROM and some latest 12.1 kernel comits that may help out

http://xdaforums.com/showthread.php?p=60670362
[Motorola Photon Q 4G LTE] robobub:
Torch is working for me, I'm on the 0427 CM build.

Also, would it be possible to enable fstrim on encrypted mounts? There was the same problem on another device:

https://jira.cyanogenmod.org/browse/CYAN-2654
[Motorola Photon Q 4G LTE] robobub:
Here are the two commits for cherrypicking to enable fstrim on encrypted devices:

https://github.com/torvalds/linux/commit/772ae5f54d69c38a5e3c4352c5fdbdaff141af21

https://github.com/torvalds/linux/commit/498f0103ea13123e007660def9072a0b7dd1c599
[Motorola Photon Q 4G LTE] mionica:
Carbon KK 2015.05.20

Finally got a new Photon, so I did a new build.

Changelog from 20150505:

merged the CM APN's (Carbon's list was pretty outdated, and not maintained)

merged the CM11 android_system_core (except for healthd, which would require a change of the native framework)

enabled the boost-cpu-freq-on-detected-activity thingie in the 12.1 kernel

switched to the CM11 bionic library;

updated everything (good stuff happened in the kernel and twrp, in the last two weeks)

As usually, performance is fantastic.

Oh yeah, one more thing; I changed the storage provider to Google Drive - I got a good few people complaining about 4shared.

I had a change of heart re. CM11, and I'll bring it to date (I figured I could do some symlink-ing to avoid wasting SSD space on most of the CM11 tree).

After that, I'll look into enabling boot adb and encrypted fstrim (I'll have to fork the kernel for that, so let's get vanilla CM11 first).

Btw, the non-working flashlight report turned out to be a hw issue; flashlight is working.
[Motorola Photon Q 4G LTE] Nuck-TH:
In case of increasing performance, can you make a look into https://github.com/showp1984 kernael changes, especially msm_mpdecision and msm_thermal? Unlike their userspace variants(msm_'re kernel-based) they are more responsive, faster and highly customizable via sysfs.
[Motorola Photon Q 4G LTE] mionica:
TWRP with adb and su support

Hi guys,

here you'll find a xt897 TWRP build that has 1) adb support, and 2) superuser support within adb.

I made this because, after giving it some thought, I figured I really don't want to enable adb support during boot.

Nor do I plan to rebuild TWRP with this hack in; also, this will never make it to the OP. I had to hack a lot at the build process, in very unclean ways, so this isn't going to get on github ;)

So hold on to it ;)

Enjoy! I reckon while most of the time you won't need this, when you'll need it, it will prove a lifesaver ;)

Cheers,

Mircea
[Motorola Photon Q 4G LTE] mionica:
2015.05.26 release

I've just released Carbon 2015.05.26.

There isn't anything spectacular about this build; the main change is that it is build with cm11 packages wherever possible (also, some APNs were updated).

Remaining Carbon packages:

art, and its dependency stlport: the CM art simply wouldn't boot when built in the Carbon tree (frameworks, I assume?), and it couldn't be built using the CM stlport;

all the Carbon frameworks;

all the Carbon application packages.

From an end user's perspective, it is pure Carbon, however these changes allowed me to maximize the code reuse between Carbon and the (upcoming) CM build. This was one half of the meet-in-the-middle step I needed to be able to effectively build both.

On a side note, I figured why MTP wouldn't start on power-on on either the ROM or TWRP; the fix didn't get into this build, but will be in all the subsequent ones.

Oh btw, I'm not sure I mentioned this. This is built on gcc-4.8; I have attempted recently gcc-4.9 builds, and they wouldn't boot. I could probably build the kernel on arm-eabi-4.9 (I got TWRP working when building both kernel and userland with gcc-4.9), but something in the userland goes bananas - the full system refuses to start when built with (arm-linux-androideabi-)gcc-4.9. I'll probably give it another go sometimes, now that I swapped bionic and dalvik for the cm versions, but I wouldn't expect much. I'll definitely retry if/when SaberMod updates his arm-linux-androideabi-gcc-4.9.

I'm mentioning for the developers' benefit: some of you might note that a branch "cr_kk_gcc-4.9" exists; it does indeed, it will build just fine, and it will produce something that doesn't boot - so stay away for now :)
[Motorola Photon Q 4G LTE] enigma9o7:
Thanks again, looking forward to it! Been happily running your last CM11 rom.

Question - will you still recommend using the kernal/boot.img from the carbon rom, or will your new cm build include that already?
[Motorola Photon Q 4G LTE] mionica:
Absolutely not, I will provide full builds, which include a boot partition (kernel + root filesystem).

I'm working on sort-of-merging the two, really - I want to reuse as much code as possible. The next Carbon build will have even more CM apps (for instance, I realized the Carbon email support doesn't include the IMAP IDLE command, which is a big no-no); the rule of thumb is that if the Carbon edition of an app looks like, and behaves like, its CM counterpart, it will be replaced with its CM counterpart. Now, isolating all of these takes a fair bit of time, but I'm on it; the net result will be me publishing Carbon and CM11 builds at the same time.

The big question is whether I can build working CM on gcc-4.8; if that's not the case, I expect CM's performance will be borderline lower than Carbon's, and its memory usage, potentially higher (gcc-4.7, which is the official compiler for cm-11.0, is a tad less efficient than 4.8). Ironically, if this were the case, it'd still make sense to use the Carbon boot image with the CM build - but you certainly wouldn't have to, and the benefits would be less than outstanding.

In the longer run, the plan is to backport as much of the LP MR1 non-Android components as possible (I've already done that to some extent - TWRP is the android-5.1 branch and most of the filesystem utils are cm-12.1) - ideally, I'd end up with the latest and greatest support code while still running kitkat. I can't think of a case for the full 5.1+ experience on a Photon (with 1GB of RAM, that'd be flawed at best), but there's a lot of work that went into 5.0 and higher, that we could benefit from.
[Motorola Photon Q 4G LTE] enigma9o7:
Your goals sound excellent.

That gcc issue sounds odd. I'm not really a programmer although I was an engineering student and used gcc for very simple programs I wrote in school, but nothing beyond that. Seems to me odd that a newer version wouldn't compile something an older version would, wouldn't that be a regression bug or something in the compiler? Anyway don't have to answer, just struck me as odd. I could understand "must compile with version X.Y or newer", but not that something would only compile with one specific version.
[Motorola Photon Q 4G LTE] mionica:
Not really. Chances of compiler regression are slim, but there are pretty good chances you have code that incidentally compiled correctly with older compilers.

This usually happens when the code is flawed (say you're using an int to pass data from a thread to another, and you forgot to mark it 'volatile'; a newer compiler with better register allocator might hoist the load, and/or do register caching, and bang - you're left with code that previously worked, no longer working).

I'm pretty sure it's mostly IPC and multi-threaded code that goes bananas;the best known case is the so-called "race conditions", when correct execution depends on a resource lock being correctly used by all the clients of that resource, and at least one doesn't implement locking properly. These are pretty hard to track - you could get code that's formally incorrect (in a non-obvious way), but still works correctly 99.9% of the time - until you change optimization options, or the compiler, and then things change :)
[Motorola Photon Q 4G LTE] palmbeach05:
This might be a bit useful as far as your testing of gcc's go http://xdaforums.com/showthread.php?p=61149584
[Motorola Photon Q 4G LTE] palmbeach05:
[MENTION=1103233]mionica[/MENTION] looks like a snapshot (possibly final release) has been made for CM11. When you get some time, it might be a good time to release an update.

EDIT - confirmed, final release was released.
[Motorola Photon Q 4G LTE] enigma9o7:
I've been thinking the same thing but trying not to be impatient...

Mionica, are you still thinking of building an updated CM11 for us?
[Motorola Photon Q 4G LTE] palmbeach05:
In the meantime, you can take the latest f2fs boot.img and combo it with the final release. No issues to report about that combo
[Motorola Photon Q 4G LTE] enigma9o7:
Good idea, just flashed it that way, seems to work fine so far.
[Motorola Photon Q 4G LTE] ajislav:
Hi,

I am getting Google Play Services SystemUpdateService wakelocks on the latest ROM from mionica.

Enabling this service gets rid of the wakelock and the phone deep sleeps again.

Two questions:

- anybody else getting these errors? Especially you guys on the latest official CM+mionica's boot.img? What is your solution

- what is the preferred way of running user scripts on startup? I did not find any /etc/init.d directory and the scripts were not executed even when I created one

Regards

ajislav
[Motorola Photon Q 4G LTE] mauchito:
I had the same issue of wakelock.
[Motorola Photon Q 4G LTE] enigma9o7:
Ajislav,

I'm running CM+mionica's boot img, and haven't noticed any errors. Do they pop up, or do I need to check something to know they're happening? I did think I noticed less battery after switching to this but could be my imagination and I can usually still get thru a day if I'm careful...

The only "issue" I have with that rom combo is I don't have superuser (get popup about superuser denied when I run file explorer, if I try to su at prompt it says permission denied, even tho in the settings menu they're set to allow). Instead of trying to figure it out I thought I'd just wait until Mionica builds new CM, but seems to be taking quite a while... but it does drive me crazy that the home screen doesn't rotate (or actually usually it does rotate, back to portrait, if I press home from another app with phone held in landscape position), but I know how to fix that by adding a line to build.prop but can't do that without root.
[Motorola Photon Q 4G LTE] palmbeach05:
I moved onto C's CM11 builds, but is there an option in settings about superuser? Maybe even in developer options?
[Motorola Photon Q 4G LTE] ajislav:
Hi palmbeach05,

which is the final release you were referring to, is it the last build here? http://download.cyanogenmod.com/?device=moto_msm8960_jbbl&type=snapshot

Or is there anything newer?

Well, the problem shows up as phone never deep sleeping (many apps show you the CPU states, e.g. BetterBatteryStats app), ie bad battery life. Moreover BetterBatteryStats shows under the partial kernel wakelocks view, that GooglePlayServices is the culprit.
[Motorola Photon Q 4G LTE] palmbeach05:
6-26 is the final CM release. C, over in the main CM11 thread on one of the msm8960 devices (probably RHD i think), has a 8-9 build that is more up to date (see stagefright vulnerability)
[Motorola Photon Q 4G LTE] enigma9o7:
Yes, under system, Superuser. That's where I have them set to allow... I can also click logs from there and see all the denials. I assume its related to using Mionica's boot image with the CM11 final snapshot together... I'll look into C's builds, if they supports f2fs I will update.... don't really want to roll that back as it took me quite a while to get that working the first time.

---------- Post added at 07:00 PM ---------- Previous post was at 06:57 PM ----------

Ok thanks. Can't check that out for you unfortunately as it requires root to install, plus it isn't free, although I saw other free apps that probably do the job, but also require root. Sorry I couldn't help.
[Motorola Photon Q 4G LTE] mauchito:
Here is the link to the comment:

http://xdaforums.com/showpost.php?p=62260543&postcount=6230
[Motorola Photon Q 4G LTE] enigma9o7:
Thanks! Upgraded smooth, and got superuser back too.

edit: but now my phone keeps locking up and rebooting, 5 times since yesterday...

edit2: went back to Mionica's 0526 boot.img (but kept the rest of 20150809 unofficial cm11) and no more lockups/reboots.
[Motorola Photon Q 4G LTE] Logos Ascetic:
RazrHD XT925/XT926 ROM on XT897?

You installed a RazrHD XT925/XT926 ROM on your Photon Q?

I knew the XT897, XT925, and XT926 were all similar. I never knew you could install a Snapshot from a XT925 or XT926 on a XT897.

Or did I misunderstand your post?
[Motorola Photon Q 4G LTE] enigma9o7:
I haven't logged in forever so this may be irrelevant. But yeah I did, installed that image on Photon Q. But now that there are official PQ builds I use those.
[Motorola Photon Q 4G LTE] Logos Ascetic:
You found a more stable and usable ROM than Mionicas?
[Galaxy Note 4 Themes and Apps] IZI.Xav:
[Mod] [ Fast & SuperFast Launcher Toochwiz][5.0.1] Update More choice real difference

&

[Mod] [S.F&Famous Fast & SuperFast Launcher] [Toochwizz] [Lollipop 5.0.1]

Méthode 1# APK :​

Download the apk TouchWizHome.apk, copy it to your phone.

Then with a file explorer like Root explorer, ES explorer copy the apk is go to System / priv-app and open the TouchWizHome.apk file

paste the apk that it will crush and replace the current one, then grant him correct permissions "644" (look screenchot) and made a reboot.

I advise you before making a backup of your current apk, simply rename it by putting the extension .bak giving TouchWizHome.apk.bak.

Then if you want to re use your current apk delete and remove just the extension .bak

Méthode 2# ZIP FILE :

Copy / paste the zip on your phone, reboot into recovery mode and flash the zip file

#Fast & Super Fast Launcher :

New Launcher available:

Stock toochwizz launcher BOC3 Fast & Super Fast

Toochwizz Launcher 5x5 6 dock Fast

Note Edge 5x5 Toochwizz Launcher Fast & Super Fast.

​

OLD VERSIONS /​

[CENTER][B][COLOR="Sienna"]Firmware Lollipop BOC4[/COLOR][/B][/CENTER]

# [URL="https://my.pcloud.com/publink/show?code=XZMnEkZJJ4dAm6eLuYX9gut2oDvDjo1H06y"][B][COLOR="DarkOrange"]LolliFamous Fast Launcher.zip[/COLOR][/B][/URL]

[/CENTER]

& ENJOY !! :p​
[Galaxy Note 4 Themes and Apps] willowpc:
Installed on N910C on Masik 3.0 deodex ROM and worked fine.. thanks !!
[Galaxy Note 4 Themes and Apps] IZI.Xav:
ok cool thank you for the report ;)
[Galaxy Note 4 Themes and Apps] thiagoribeirorj:
Working N910C. Thanks.
[Galaxy Note 4 Themes and Apps] SUNUN:
dear [MENTION=4904213]IZI.Xav[/MENTION] and what removed here? what functions not work on launcher?

and os it for odex? or only deodex?
[Galaxy Note 4 Themes and Apps] demon28:
Will this work on 900T
[Galaxy Note 4 Themes and Apps] IZI.Xav:
I'm not much on understanding and are deodex apk
[Galaxy Note 4 Themes and Apps] SUNUN:
i am asking you why it is fast, you remove some functional or no? and i have rooted device but odex firmware can i install it?
[Galaxy Note 4 Themes and Apps] IZI.Xav:
Ah ok, no nothing is deleted it is modified xml is if you remove your toochwiizhome.odex, I think it should work but I can not assure you because I have not personally tested on a odex rom.

If you try it please let me inform
[Galaxy Note 4 Themes and Apps] SUNUN:
ok i do it but how now now it works, and i don's see any changes?
[Galaxy Note 4 Themes and Apps] IZI.Xav:
this is not a thème no visual change this is to increase the animation speed of the pages, folder, scrolling etc ..
[Galaxy Note 4 Themes and Apps] arch22rami:
Thanks my friend
[Galaxy Note 4 Themes and Apps] Paoul conetta:
thanks Dev ! all i need is in this your tread! a fast launcher for lollipop.. thanks and good work, continue the project!:good:
[Galaxy Note 4 Themes and Apps] andreasarxon:
flashed super fast launcher on n910f and get launcher forced close ... make factory reset still the same... had to reflash rom with odin to get the phone to work... n910f 5.0.1
[Galaxy Note 4 Themes and Apps] Paoul conetta:
I tried fast And super fast launcher, don t are a Big difference. Super fast launcher in kit kat rom is much much fast And whitout any lag in app drower. In lollipop is differenti. .
[Galaxy Note 4 Themes and Apps] Hitman42:
Merci a toi !
[Galaxy Note 4 Themes and Apps] IZI.Xav:
Big update, now real difference ENJOY !! :p
[Galaxy Note 4 Themes and Apps] crazynewfie:
Thanks. Just wondering if anyone has tested this on 910W8?
[Galaxy Note 4 Themes and Apps] alexxutzu:
I've installed on BOC3 stock rom rooted, flashed zip, and I get TouchWiz has stopped...... I installed the BOC3 SuperFast Touchwiz.
[Galaxy Note 4 Themes and Apps] 557953:
Superfast links seem to be down, was there a bug or other reason?

Looking forward to trying when sorted :)