Recent content by mjb

Before anyone asks, yes, it can run ingress. But due to the display size, it's not usable. (although, having ingress installed means I get notifications, which is a bonus)

sorry - should have mentioned. It's nominally 240x240, ldpi.

Chainfire, I've just recently taken delivery of my Omate TrueSmart smartwatch - nice device so far... Anyway, the prompt dialog from SuperSU is 'too big', so I can't actually see the allow/deny buttons (See attached image). Would it be possible to create a reduced size dialog for small...

Roku Remote please?

Ahhh.. yes, I understand where you're coming from then. Here's another theory: buggy wear leveller hits a certain threshold where it starts overwriting critical blocks on the eMMC. The first few start to cause the behaviour you saw, until a few later, a super critical block is overwritten that...

Right - I assumed (probably incorrectly) that BL updates can be performed from OTA updates as well. Earlier, when you stated "WHAT'S THE PROBLEM" - this is it - we don't know if historic usage has any bearing on SDS. It either: 1) does and previous 'bad wear' cannot be corrected by a fix 2)...

Oranav, could you use the same read function that's used to fetch the firmware date to read the entire firmware (while in the vendor specific debug mode)? or is that what the code you've found does? How did you get on?

@rootSU: I'm not trying to pick on you, honest! I also don't think you can say that either. We know next to nothing about what the fix to the eMMC firmware does, and if it's a bug like Entropy512 describes, then your analogy falls down flat - it'd be like you are still being exposed to...

Right, I understood that, but the point still stands - we can't actually definitively say that there is more than one date on those chips - so it's safer to say "Unknown, but assume you're vulnerable.", rather than "some chips are not affected". Since we cannot (currently) retrieve the date in...

[Please excuse the excessive quoting, but I think it's needed for context] Try reading Entropy512's post on this subject. Basically, the wear will still occur, but at a certain point, the amount of wear will not trigger a bug in the eMMC firmware with the soft-fix applied.

Where did you get that idea? ---------- Post added at 07:54 PM ---------- Previous post was at 07:39 PM ---------- I don't think you can actually say that - I find it hard to believe that a given FW Rev would have more than one internal date - or that this bug only existed for one potential...

Fw Rev Fx1 is not valid. The revision is in hexadecimal, which is represented by the characters 0-9 and A-F. The first two characters are usually "0x", which helps to disambiguate between hex and another number base. (for example, "23" vs. "0x23"). So, to answer your question, the...

Yes. Same key combination to enter stock recovery as custom recovery. It's the bootloader that does that (starts recovery or download based on key combinations)

Oh, good point. So, we'll need an updated sboot at some point, or it'll be a risky endeavour to upgrade the OS via non-OTA means.

Certainly possible that the fix in the stock kernels has been through a few revisions before getting to ELLA/Update7.. probably need to trawl the whole thread to try and find definitive examples of SDS on previous kernels. Personally, I think that this 'fix' isn't the one we're looking for...