jjarmasz
-
Content Count
70 -
Joined
-
Last visited
Posts posted by jjarmasz
-
-
3 hours ago, Slion said:
Nokia E7-00
I used an E7 for a couple of weeks (thanks to old Nokia's very generous trial program for "bloggers" back in the day...). I thought I would love it but at the time it felt too heavy and the camera kinda sucked (and yet look at me with the Pro1 now...) I almost said the Nokia N97! Despite being criminally underspecced I loved mine, especially starting the camera by sliding the cover and just popping it open with one hand to type messages on it. Clearly I am quite comfortable nursing along hobbled devices...
-
1
-
-
Not missing my Samsung Galaxy Relay aka ApexQ, which I would boot up now and again just to feel the keyboard.
And oddly enough, don't even miss the Pixel OG (and its great camera) that was my daily driver before the Pro1. Or any other phone. Despite the phone's quirks (friggin' fingerprint scanner drives me nuts every day) I haven't had any of the major issues I've seen others report. The keyboard is a joy to use every time, I love the screen, the camera is fine with a GCam port and I haven't had any sound issues -music and podcasts sound great. Never looked back for an instant after I first booted it up...
-
I tried this app, and while it's a nice GCam implementation, it suffers from what all the other GCam ports for the Pro1 seem to, namely: the viewfinder in Night Sight mode is still upside down. Also the Nigh Vision algorithms aren't as good as some of the other ports, the results are kinda grainy. Too bad, I prefer the newer UI on this one.
-
Given how long the battery lasts I wouldn't be surprised if the OS is forcing the CPU into some kind of power saving/lower performance mode...
-
2
-
-
23 minutes ago, cerialphreak said:
I'm curious to see if anyone else is having this issue: when first opening the phone some keys wont type anything until another key is pressed. This seems to happen mostly to Y and H (qwerty varient) which is getting to be seriously irritating considering a lot of text messages start with "yes" or "hi." I've seen the repeating key issue as well, but only once.
Yeah, I think I'm getting the same thing. Notice it especially with the H key. Glad to know I'm not the only one, I thought maybe I was imagining it.
-
On 1/24/2020 at 4:57 PM, netman said:
I did not do a port, I installed a GSI which you can easily download. Because of googles Project Treble thing and the pro1 stock rom being fairly compatible with it, as long as you have their vendor and boot image, other versions of android mostly work by just flashing the system image.
At the time I installed it I wasn't aware there are instructions for it but it was reasonable straightforward and went without a hiccup 🙂, if you want to try it I recommend following this guide though https://github.com/phhusson/treble_experimentations/wiki/F(x)tec-Pro1
I'm curious, how's your battery life with Android 10 GSI? (Asking because I'm quite impressed with the battery life on the Pro1 so far).
-
3
-
-
-
12 minutes ago, EskeRahn said:
Interesting, could that be done over ADB / Fastboot?
I was wondering the same
-
1 hour ago, EskeRahn said:
Well the initial post has this link that includes a guide and a list of issues. (I have not tried it yet though)
That's the thing, that list of issues doesn't really give a sense of what it's like to use it...
-
Just wondering, since I am hesitant to take the plunge and flash my new phone: has anyone been using Android 10 GSI on their Pro1 regularly? How does it compare to stock? Any important functionalities lost or messed up?
-
Hmm... Any word on whether this also addresses some of the Bluetooth encoding (specifically aptX) issues?
-
5 hours ago, DieBruine said:
If you enable Developer Mode you can force APTX or any other codec for that matter under developer options... Try forcing it, maybe it will succeed. It could be just a handshake issue.
I did, it still didn't work for me, only SBC mode... I realize BT is generally cranky and it could just be that my headset and the phone don't like each other 😁
-
6 hours ago, DieBruine said:
I use an APTX HD receiver. No issues with sound on my end. It aso states APTX HD under Bluetooth/connection settings.
Interesting. My headphones only support aptX, not HD. Definitely sounds (excuse the pun) like a SW/firmware bug then...
-
1
-
-
1 hour ago, FlyingAntero said:
Yes, I can see big difference between those two ports. Please, see the examples below. Viewfinder is upside down and freezing in low light situations in both ports but only PocoPhone port can make great pictures.
Oh wow, yes, I see what you mean. The few pics I took with NightSight weren't good enough to do that kind of testing 🙂
Ok so the Pocophone port is definitely the better one.
-
1
-
-
9 hours ago, FlyingAntero said:
I noticed that Night Sight doesn't work right on Pixel Gcam port. The image quality in jank like @Serolfic mentioned. However, on Pocophone Gcam port Night Sight is working great except that viewfinder is upside down. So these two port are working differently on Pro1. I think that we should try to fix Pocophone Gcam port for Pro1. Has anyone built APK before. It shouldn't not be hard to changes those lines if you know what to do.
Example photos (low light situation)
Are you really seeing a big difference between both apps in Nightside mode? I'm finding both pretty much the same - both apps have the viewfinder rotated upside down, in both the viewfinder freezes when the light is too low, but both somehow also produce good and just about identical pictures for me.
-
I know this is an old thread, but I tried my BT earbuds that usually use aptX for the first time with the Pro1 today and they connected but got no sound. I didn't know about aptX issues until I checked the forum but it seems a few people have also encountered no music playback with aptX but yes with a downgraded codec. So this is definitely a live bug still. Hoping it will be fixed in a SW update soon...
-
On 12/11/2019 at 2:33 PM, ddark-il said:
Tried that, also with LDAC and other AptX variations, it's either falls back to SBC or got no sound at all.
But I still haven't seen confirmation that someone else got same behavior, so it might be limited only to my case.
Ah, so this is probably why my BT earbuds connect but don't produce sound... They usually run using aptX, haven't tried downgrading the codec but I'll try that next.
This is the first bug that is close to a showstopper for me. All the other quirks so far are livable for me as a price of having the keyboard, but my BT audio quality matters a lot to me. There had better be a software fix coming soon...
-
1 hour ago, david said:
I'd like to know this too, since, in theory, the Pocophone version could do better with focusing, due to the possibility it is using the depth sensor.
Interestingly you can install both side-by-side. And TBH the only difference I have noticed so far is the UI, the Pocophone port uses the older Gcam UI. And both have the additional bug with the Nightsight viewfinder that it freezes if the light level is too low, but starts up again if you point it at brighter light.
-
1
-
-
The rotated Nightsight viewfinder is definitely disconcerting but it still works - cool, you just have to frame the shot in normal camera mode 🙂
So far I've any tried the PX one and it's great. And I'm happy to launch it with a double press of the power button. Anyone had a chance to seriously compare the Pocophone and PX ones yet?
-
4 minutes ago, sequestris said:
Yes. I was surprised too.
Brilliant. Gonna have to try it out...
-
2 hours ago, sequestris said:
So this is a bit of a "Huh" moment.
@david recommended this clear bumper to me.
https://www.amazon.com/gp/product/B07L2SQLRC?ref=ppx_pt2_dt_b_prod_image
I just got it today and put it on.He had told me that some mods need to be done to get the buttons to align and the ports to be easy access.
I was trying to upload some pics to my PC and pried it off and stuck it on the front.
You know what?
YOU CAN TYPE THROUGH IT!
YOU CAN TOUCH THE SCREEN!You know what?
I can flip open the phone - with ease - and the entire screen is protected.
Sure there is a cut out for where the camera and flash holes are, but whatever!
I have a screen protector that arrived in 2 days and cost $7.39!
Seriously, you can flip it open with the protector on top? That's amazing.
-
1
-
-
1 hour ago, kartspeedster said:
No need to adjust things, if you press the edge of the screen right at the very bottom (it's not too hard to do or anything) it will click the settings icon so you can still easily get to it. The "button" for it is bigger than the icon basically.
Thanks for pointing that out, I was wondering about that too. But it would be nice if there you could see the settings icon in landscape anyway...
-
3 hours ago, Rayanth said:
Can't find a way on the Pro1 to get google to retrieve backup from prior device... any pointers? The backup screen just has Back Up, does not have any Restore...
Google "retrieve" is pretty flakey IMO... I don't think I've ever been able to restore a back-up from the settings menu. BUT I opted - for the first time ever - to restore from my previous device (Pixel OG) during the initial set-up of my Pro1 and astoundingly it worked like a charm! Apps, settings, wifi, SMS were all ported flawlessly. I still can't believe it worked 😂😂
-
1
-
-
So... is the consensus still that all the known Gcam ports are still a bit janky on the Pro1? Coming from a Pixel I would love it if there was a reliable port for the Pro1 with good Nightsight...
Thanks to the fxtec Pro1 I no longer miss my...
in General Discussion
Posted
Yeah, the durability of the Pro1 is uncertain at this point. I have no issues yet (knock on wood!) despite even a few very small drops 😬😬 but I scan the "Pro1 for sale" posts here now and then, maybe I'll buy a back-up one...