elvissteinjr

Got tracking for Friday, Germany, IGG, QWERTZ, #12XXX. Finally.

Got the email as everyone else here, IGG, QWERTZ EU 12XXX, checks out. But my order status is still "Processing"... really hope that's nothing to be worried about at this point.

Any particular reason? Or is that just IdeaLTE's hacky solution getting in the way? Any signs of Fx being interested into bringing these improvements to the stock rom yet? Not even sure if it still sounds reasonable at this point, but I'd kind of prefer to just run stock on my device once I have it. Seems like I'd be missing out on more and more by doing so, however. I appreciate the work you're putting into this either way. Thank you!

Is the 12 minute limit in 4k a real world issue? Ignoring that the video quality ain't all that great to justify recording in 4k, if the next file is written without a hitch or interruption, stringing the files together without re-encoding on a PC is a pretty simple. Or keep some internal space free and record to there once it's supported in the future, I guess. I won't believe if you're gonna tell me you want to juggle around these large recordings without any further processing done on them later on.

Dispatch could mean to customers, as all units are sent straight from Hong Kong this time around. They'll likely leave the factory on the way to Hong Kong on the 18th, on which they obviously have to be done making them already.

Hm. Assuming just putting "PAGE_UP" on there instead of "fallback PAGE_UP" doesn't work... I've seen a "replace" keyword in one of the vendor kcm files in the android source tree. That's not documented, but perhaps "replace PAGE_UP" would work? Just theorizing however. I don't have any practical experience with fiddling with these.

Regarding key character map functionality, take a look at the documentation if you haven't yet: https://source.android.com/devices/input/key-character-map-files I don't see the issue of doing fn+digit in theory reading this, but perhaps it doesn't work that well in practice?

FTP over wifi is probably faster and more reliable than anything you get over that shoddy MTP over USB to be honest. If you had mass storage mode, that would be a different story of course.

It's kinda sad how this video also shows right away how prone the display is to accidental touches on the edges. Hopefully we'll have some solution for that working with both orientations in the future.

(Calm down, it's just a meme)

Yeah I cannot believe how people can be upset after being repeatedly baited for 6 months straight. Even worse, they dare to have some doubt about statements when others have not turned out to be true before! Shame on them! If we're having a patience contest here, I have a Pyra pre-pre-order from October 2015. It's all about how it's handled.

Unmodified letters and digits should be fine in any layout (except the adapted German QWERTZ) on QWERTY Pro1s as the driver sends the correct key code for those. Everything else probably not. And since QWERTZ Pro1 is just a different keymat and nothing else, every unadapted layout will be shifted. At least that's what I've gathered from looking at the driver source. Can't confirm this theory myself due lack of phone.

Appears I've been slightly misinformed, though I swear at least for the Pro1 stuff there was stuff going around along the lines of "flash back original boot.img, take OTA update, then flash patched one back", but it seems Magisk Manager can actually take care of all that and it should just work. My ramblings were completely unnecessary if that turns out to be working just fine (I don't look exactly smart now, right?). I apologize for wasting your time there in that case. I take the EDL tool is not something that exists for the Pro1 yet, right? Having something like that could come handy,

Magisk root modifies the boot image and does not change the system partition in any way. This leaves us with the issue of not being able to pull the new boot image from the device as root is gone after the OTA... and in order to restore root we need to flash a patched boot image... which can only be the old one in this case. Unless some other way to grab the partition data surfaces or someone succeeds stringing together the intercepted incremental OTA packages, I suppose. In any case, doesn't seem like something you can help us with after all, unfortunately. Just hope Fx will provide upda

What was asking was if the boot image can be used with the official Android builds as Fx themselves appear to only provide updates through OTA so far. For Magisk however, we need a boot image file to patch, so keeping up to date with the kernel while keeping root doesn't appear possible right now. And I personally want to root right away when I get my phone. Not asking for direct assistance on that, but knowing if it could work that way is useful. Perhaps Fx does eventually update their flashable files, but it could take a while, knowing them. With the lack of a device I'm on in imme

That's neat. Thank you! Not sure if I'll use this (lack of device makes it hard so far), but does this "stock" mean plain Android without any extras or like the official Fx images but without Google and OTA? Not quite the point of this ROM and since the sources are from November it doesn't actually help, but I was wondering if they were more current, would the boot.img be pretty much the same as the official one and be usable for Magisk patching?

Uhm, sorry, but what kind of planning is that? It's not like the Chinese New Year date moved or anything. Did some factory worker suddenly convince you or something? You really shouldn't have pretended to be doing weekly shipments either. If anything, maybe skipping the "small batch" would've been smarter. But what do I know? I'm just angry dude, it's just another "small delay"... how many of those do we stacked up now?

Overall a nicely balanced review with a hidden negative point of the mushy two-stage camera button I suppose (as it should be able to take photos). While I certainly can't judge the opening mechanism for myself yet, some people easily open theirs one-handed by now. Perhaps it's not learning how to do it, but rather stopping to do it wrong based on expectations how to do it. Well, that's still "learning" in a way, but this is not your average sliding mechanism, so don't force expectations of one on it.

Root switch would be convenient, though probably not allowed on Google's Android indeed. Magisk does more than just simply provide root though. On that note I'd like to urge F(x)tec to provide updated flashable images along the OTA updates or at least updated boot.img that can be patched with Magisk later. It appears to be not technically impossible to scramble together the image file from an intercepted incremental OTA archive and the initial image, but I don't think there's been success in this yet. Root is technically not an advertised feature like the alternative OS support, but I hop

The Simple Mobile Tools apps are also available on F-Droid. Surprisingly In their pro versions even. The gallery might not receive any updates there in the near future though as the dev decided to use a closed source SDK for the new photo editor. Just recently switched after QuickPic started behaving a bit weird in the recent versions... and well now I know why. The only thing I'm missing so far is a true folder browsing mode. The one in the app is odd with folders that only contain additional sub-folders with images and displays those one level to early or something... Somewhat missing th

I dare to ask: Has anyone here received the fabled Monday shipping email? I know, small batch, yada, yada. It's not unlikely that everyone who was in it just doesn't post stuff, but Erik isn't celebrating more sent out devices either so nobody knows what's up.

To be fair, neither Chromium* nor Firefox appear to support hardware accelerated video decoding even on Linux desktops. Though it's typically less dramatic there. *works with certain forks, but not official builds mpv might be worth testing for that, but keep in mind it doesn't use hardware decoding by default, so lookup how to enable that.

I know it's Monday and soon Christmas, but looking back how that shipment from the beginning of December got either lost or landed somewhere else... not necessarily asking for an update as there probably isn't anything to say yet, but do you think there will be any more units going out to customers this year?

EvilDragon himself said on the Pyra boards that EdgeNull works fine for the screen edges. So that's a thing at least.

The Note 9 has faster hardware for sure, though it's up in the air by how much. You can try comparing benchmarks or maybe even find some tests made with that game in particular on similar hardware. Something of note are the different screens however. As a blessing in disguise, the Pro1 will only have to push about 54% of the pixels the Note 9 has to render in native resolution.