System apk titanium restores maybe?

Plus, everybody runs a different Xposed module set. It might just be some of these modules causing the FCs, they ARE modifying system files AFTER ALL.

More power to us, though it's sad that the N3's power is wasted due to Knoxy. Personally I can handle stock rooted ROMs, but no access to custom recovery (without tripping) is not acceptable, at least to me.

Hopefully this changes in the future, with help from our hardworking friends over at XDA.

This post has been edited by Eiraku: Nov 24 2013, 04:53 PM

You mean the official upgrade? Must be the Note 3 browser they jammed in there. My MI6 4.3 browser still works fine with flash over here.

This post has been edited by Eiraku: Nov 24 2013, 11:33 PM

Tried Dr Ketan Custom. Liked the rom but I absolutely HATE the N3 browser and how all the N3 stuff are "white" rather than dark = dark is best on amoled as bright colours actually makes it die faster.

So I rolled back to my old Wanam MI6 backup, and I have a problem with Wanam Xposed - which was there ever since I updated to the new WX, actually even before I went up to KetanV5. Every time I start the app (or when it autostarts at boot), it vibrates as if something is force closing in the BG.

Now trying to investigate why, so far I'm stumped though. Reading logcat reveals a reoccurring "error reporting failed" thing, but that's it.

I tried turning stuff on and off, and rolled back to a prev WX and the "ghost FC" is still there. Damn.

This post has been edited by Eiraku: Nov 25 2013, 08:30 PM

Fasterer and biggerer. For at least 20 more years until miniaturisation catches up and we can get decently powered wearables.

Real dead end development we have right there huh.

As for why I want it to last? For one, black = battery life. For another, being a really heavy user means that my screen degrades twice as fast compared to a normal consumer (on average). Means that I might not even last through through a year without suffering permanent burn in damage and yellowing (due to dying blue diodes) with such a white heavy UI.

More importantly, I like black lol.

This post has been edited by Eiraku: Nov 25 2013, 09:31 PM

If anyone bumps into a way to get the old MI6 browser (or any AOSP browser) back in DrKCustom, do share. It's my biggest issue with it as of now.

I really don't like the new Chrome based browser one bit.

Finally managed to track the culprit of the "ghost FCs", and it's so ridiculous I don't even...

It was actually...



Hopefully nothing else breaks after after this, so far everything's back to normal.

This post has been edited by Eiraku: Nov 26 2013, 05:18 AM

That said, lots a people had FCs with MK4, especially those not running the latest BL and using the wifi patch. Although my short experience with DrKCustom was totally smooth and FC-less after flashing (with Philz, not TWRP).

Now back to MI6. Not having the full N3 experience is sorta sad but I'll manage - I love the old browser too much to go anywhere else.

You mean the Scloud fix thing? Yeah it supposedly fixes (or at least lessens) the random reboots. I'm back on MI6 so the only issue I have is the occasional AWOL G-account bug lol.

This post has been edited by Eiraku: Nov 26 2013, 08:00 PM

Now wondering if a matte, > 0.02 mm glass protector with rounded edges will ever appear for the N2. SGP already slowly throwing away stock of N2 items, so I'm expecting our devices to be slowly forgotten by other accessory makers, which is sad.

We're not "cutting-edge" anymore, so there will not be as many new accessories made for us. The newest Gen4 0.15mm Glas M is ONLY available for the N3 and the 5c/5s for instance.

Which is sad because I don't really feel like upgrading any time soon.

On another note, I went on and tried Capdase's Xpose TPU and Alumor cases, and ended up NOT buying both. The TPU used were too soft and felt filmsy.