auvo.salmi

I also freaked out when I dropped my Pro1 for the first time. Now I have dropped it quite many times, and looks like it is really rugged as I haven't managed to break it yet. Looks like the black coating on the alloy shell is fairly thin and wears out easily. All the corners of my pro are more silver than black nowadays, but this is a mere beauty issue.

Lineage is mostly about privacy, and it gives you more control on what the apps may do behind your back. It is also much more customizable than stock Android, and it basically gives you access to all the available options in Android system. Some of them doesn't work as they should, but at least you have the freedom to make the choice 😄 Also Lineage has most those bugs existing in stock, fixed. I haven't used the stock for a while so I don't know whether they have fxed the bugs on stock too, but basically Lineage is more usable than the stock. The disadvantage is that banking apps and some comp

I have been on LOS and GCam port for a while, but IIRC there was two separate camera apps on stock. Like Snapdragon camera app and a second camera, probably named just as "Camera". Both of those UI's look familiar to me, so I think I had them both on my device, but in different apps. Like EskeRahn said, the top one was the preferred. But I saw the bottom one also on stock.

The tapping doesn't work on my device in this situation. Although it tries to focus to tapped point, it doesn't really get there at all or/and focuses back to close again, and continues sawing the focus back and forth for few seconds. But looks like it really can't focus to infinity, and that's why it never gets it to focus outdoors.

Just to clarify: So if you try to shoot a landscape photo outdoors, it will correctly focus to infinity and result as a focused image? My photos look like the attached image. Could the devices have slightly different camera modules or something like that, if the issue exists only on handful of devices? Could @EskeRahn or @fxtec-preorder-47xx provide the logs? I would rather not flash stock if I can avoid it 😄

Can someone confirm this? Does someone have their rear camera focus working properly on LOS? Also, I wonder if @tdm has seen this thread or has any idea what's wrong with the camera. Can we help somehow by producing some data/logs/tests?

I have exactly the same issue on LOS. and it doesn't depend on camera app used. Also I have wiped my system several times, which doesn't help. Seems like not everyone has this issue on LOS though, because it isn't listed to 'official' bugs in Github..

I tried and can confirm it works. At least for now on.

Just updated to newest Nightly build. Turns out I was running test11 and not 16 as I said above. I also did wipe because wanted to have a fresh start and see how many of my existing bugs/issues will follow me... Update went well and everything works... well, almost everything. Shortly after update I realized why I hadn't done this before; Because of losing MagiskHide. I know this is not the favorite topic of our main Lineage developer, but is there still a way to get 'ctsProfile: true' or some other working way to hide root in the official build?

Side question: Should wifi hotspot work on Pro1 LOS? Because it doesn't work on my device. Currently I am running test16 build IIRC, but I haven't seen anybody mentioning hotspot neither with older test builds or newer test or official builds. So the issue on my device is that the hotspot can't be switched on.

Strange thing; I had this haunted phone issue for two-three weeks, then it was gone. Nowadays the display is acting almost normally, maybe it is like "overly sensitive" sometimes. For example, when I try to scroll through app drawer, it reads my finger swipe as a tap instead and opens the app I was swiping over. So no need for a screen replacement atm. Glad that the issue went away, but overall it is becoming quite difficult to consider this phone as a reliable device, as I have had all the common issues (accidental reboots, haunted screen, frozen screen) plus some more random issues, like cam

I can't remember anymore, but I was probably among the first in Europe to receive their Pro1's. So about half a year I guess. Seems like the issue fluctuates a bit on my device. For example, at morning, the device acts normally for some time, but those ghosting issues start after I have been using the device heavily for a while. But still, now I have been surfing, browsing social media etc for at least an hour in a row, and have had zero issues. But earlier today I couldn't input my screen lock code even using the keyboard only, because the ghost taps filled the prompt screen all the tim

My Pro1 also started to do this yesterday. Perhaps not the worst condition yet as I can still make this post on the Pro1, but sometimes it doesn't allow me to input unlock code but fills the field with random digits instead. And now the cursor started to warp to address field, which makes typing quite annoying 😄 Just going to start a three week trip today, what a great moment for the device to go mad.

I haven't had this issue for a while, but IIRC the Caps led didn't work.

Yeah, could be because of this. I have had only swype as screenlock, and I have thought that it should be enough to prevent accidental logins (or at least it used to be enough in older Android versions, but looks like nowadays any kind of tapping/toughing the screen will unlock it if power button is pressed earlier). So I added code lock, let's see if it fixes the problem.

Have anybody else noticed an issue with screenlock? Or what it should be called, I don't know. But the point is that sometimes, while the device is in my pocket and screen is off (by pressing power button), looks like the digitizer still works and receives touch input. This results the same way as the old non-smartphones when you forgot to lock buttons before putting the phone in your pocket; it may call somewhere, opens apps, opens new tabs in browser, opens random websites etc, and spends quite an amount of battery. First time it happened when I had Google Maps navigation on but screen power

I agree. Even in my case, the network is never that bad. I mean, that just based to my experience, the reboots don't happen when the network drops completely off, but when it switches temporarily from lte to 3g or from wlan to mobile data. I know that if the issue was really be that simple, every Pro1 owner would suffer accidental reboots all the time. So it has to be something more complicated.

As I have reported before, my device has been having random reboots once a while. It has been almost daily. Typically, when I wake up, I come to kitchen from upstairs and start to make breakfast. Looks like I have better network upstairs, because these reboots almost always happen in the kitchen, usually at morning when having breakfast. Also I have those reboots sometimes when I travel to places with weaker network coverage. But what is strange, is that I don't have these reboots anymore. Like, at all. Let's say no reboots in 7 days at least. Nothing have changed in my phone lately, and I hav

I don't know where I should post this, and I guess I am too lazy to search the forum for similar issues. But my main camera doesn't focus anymore. It tries though and rolls the focusing back and forth, but never gets anything in focus. Seems like auto exposure is also gone with the focus. I am running Lineage and the problem exists both on Lineage stock camera and Open Camera. Focus still works on front camera, so I believe this is more like a hardware issue. I have taken some otherwise great photos during this week, but they all look like this:

I seem to have auto capitalization in most of the apps. Like Whatsapp for example. But not in browser, atleast when typing forum posts like this.

Yesterday I had two spontaneous reboots while having a call. I was working on my garage, and had working gloves on. First time I really thought that the device rebooted spontaneously, and the second time I was ready to throw the device towards concrete wall... But then I realized that I had accidentally long-pressed the power button on both of times and this caused the reboot 😄

It is intended to work that way. To be close to the same as in pc keyboard. So you should mostly forget the yellow markings on the keyboard and use shift+number shortcuts as they are on your pc. I'm too lazy to search the post for you, but if you search these pages for at least five pages back, you should find some discussion and explanation for this.

Oh no. Today I had the unresponsive keyboard bug for the first time in Lineage. It was already fixed in stock too, so I hoped that at least this bug could be forgotten already. But looks like it still exists, at least occassionally. Reboot fixed the problem, at least temporarily, as always.

@Craig @Hook or anyone willing to answer: Going a bit off from the topic, but I just started wondering this Verizon/Sprint business. So why would you like to use it on Pro1? Do you have to do so for some reason? Why is that so important, is it like your favorite operator or is it also the only available one? As in Finland we basically have three big network operators, and all of them work pretty well everywhere around Finland. Of course some blind spots exist, but basically they all have full coverage. People tend to switch between the operators all the time, depending on discount campaig

Oh. Stupid me, apparently. Now it works! Thanks guys!