Leaderboard

Take it apart ASAP and disconnect the battery! First under the stickers on the back of screen there are screws (only under the 5 stickers that are accessible by screwdriver) then take off the screen but careful because you have to disconnect the big ribbon cable while doing that. Then there are 3 screws to take loose the hinge parts, then the whole screen side part of the phone should come off and reveal more stickers under which are screws (also two corners of the keyboard have stickers), after taking thouse out you should be able to remove the top of the keyboard part including the keyboard,

Eek, hadn't considered that, that could be harmful to userdata/sd integrity i guess. Also it could cause trouble during updates, although a/b system should make it so nothing bad happens. In short: if you mean shutdown by longpressing power rather than from menu there is a chance you could lose files from userdata or on sd card (especially fat32/exfat formatted sd), hardware would be fine though. You can decide for yourself if that is a risk worth taking in the situation.

I still can't understand why anyone would do it unless they were having a problem though. I've only done it a few times ever on all the devices I've owned.

Yeah, I measured the size of the plug on my earphones, so it is 6 mm in diameter in the case, but easy to modify 🙂

I think he speaks about long-pressing the power button which will do a hardware poweroff and not a software one.

Naw that is fine to do, why would you though?

If you don't see any boot logo or anything, that is surely a hardware issue. I'm afraid it's time to talk to support. 😞 It is possible... I'd say likely... that it's just a loose connector. But you and support need to decide whether you should disassemble the device or let them do it.

Yes. It does whatever lineage usually does. I'm not going to wait for the timeout 5 times to try. 😉 You, as a user, do not switch to enforcing. It is my job to fix all the enforcing issues and then enable enforcing mode.

Oh, and I found another hack to temporarily fix the audio...receive a text message. Or send one to yourself and QUICKLY go back in to the app with the problem. No need for a plug now. 🙂 Clearly this has nothing to do with power. I see this in the logs: audio_hw_primary: start_output_stream: enter: stream(0xe6d71000)usecase(1: low-latency-playback) devices(0x2) and other various things surrounding this. Where as when I start apps that have the issue, I don't see this. So this leads me to think it is indeed related to buffering. Though my attempts to adjust different buffer settin

Print finished, but it was a bit to small and stiff so it cracked in the top. But here are some images. It is very hard to get a good print with thin walls (about 0.5 mm thick), I think next time I will print with thicker walls to make it more robust.

Hi Gurus Just want to get technical opinion about a silly question. Does shutting down pro1 using powere button several times a day can cause any damage or any issue in the long run? thanks for your help

Try press and hold the power only for about 7s and release. That should force it to restart, and that should show something on the display within a few seconds. If not it is almost certainly a hardware issue. I assume we can rule out a completely flat battery, right? If not attach it to the charger and leave it say half an hour, and retry the about 7s power-press. It should at the least show a logo.

Just released v0.3.0 providing Quick Settings tile for managing screen brightness and improved color filter composition.

Just a small idea, shouldn't the headphone jack area be bigger in the case if someone wants to use for example PC-style headset with a big and thick 3.5mm jack? An issue I atleast have often faced is that with a case and a headset like that, many cases block the plug because the plug is too big for the hole in the case. This is just an idea, I know we aren't that far into making complete usable cases yet.

Not necessarily simpler, but simpler if you have the option set. If you've turned on the developer options for advanced reboot menu, one of the choices on the restart menu is recovery, and that does work to reboot directly into recovery. Dunno why adb fastboot recovery doesn't work tho, probably a slot thing.

... Or the more realistic 3) , they don't have anything they can send currently. If you should have missed out on it, they still have not got neither all the phones nor alle the parts they need.

Thanks, I'll review the pdf, and if I feel confident I'll break out my little tools, if not, I'll show the pdf to the mall phone fixer.

Wasn't sure where else to put this, but I have a bit of a nitpick (and sorry if this was already mentioned elsewhere): the wifi icon has the two little UL/DL arrow icons, but when the "Do Not Disturb" icon is displayed, it shifts left and right as the wifi arrow icons come on and off. It is annoying AF. I mean, could that not have been done better? Is this something that can be fixed?

I'd say fixing this stupid crackling/echo audio problem...still no joy here trying to resolve. If you want to reproduce, there are certain apps that ALWAYS do it. For example - Fishdom. But my experience so far is that most games do this. Even RetroArch emulator.

AFAIK they are electrically wired in parallel, so the 66 physical keys represents 64 'logical' keys.

No I don't really play games on my phones... or anywhere really. That's what happens when you have kids and an android hobby. 😉 Interesting to know that it's also in stock, thanks. That will surely help.

Okay I've spent several hours trying to get TWRP to decrypt userdata and still no joy. I am going to put that aside for now and focus on other things. So as I recall, the top 3 things people wanted were display margin, fingerprint mitigations, and TWRP. What's next on the list? I believe the only things blocking official builds are FM radio and selinux. And I could probably fudge on FM radio if nobody cares about it. Though I really should get it working soon.

Tried microwave oven, did not work. Then tried a metal biscuit container, did not work! Then tried a somewhat heavy cast iron pot with a cast iron lid. THAT killed all signals 💀😁

I was talking to a tutor at the college where I work, he lectures communications. He says he's seen it happen sometimes and believes it's something to do with band switching, but he's still looking at the phenomena, as he put it.

they pulled my version of the keyboard driver, the issue should be well and truely gone along with randomly missing keys and now multiple simultaneous keys should work too 🙂

Here is the post where I described how to change the keymap: https://community.fxtec.com/topic/2509-lineageos-current-status-160-test-builds/?do=findComment&comment=45512 Also, I realized that I may need to make a third keyboard layout "qwerty-intl" to support multi-lingual keyboards using the QWERTY keyboard, as @auvo.salmi is doing. I don't know how many others are doing this. Anyone?

Remember that they are small, so they easily will be pushed aside when a larger customer wants stuff. Hard to fight the giants. Even though they may already be using multiple sources for standard parts, their volumes are so small that doing so for specialised parts, would add heavy surcharges.

Installed it right away, thanks! It seems that security patch level is also updated to 5th October 2019. EDIT: I can confirm that keyboard issue is indeed fixed. I can now play Sonic and Mario or whatever like a charm. Super awesome! It looks like that all keyboard driver issues are fixed now. I can now press "7", "U", "J", "N", ".", "UP" and "Enter" keys (QWERTZ) right after I wake up the screen. I don't need to press some other key first.

I am not sure if I got everything right but I thought we have two options (source) Make the keyboard act like the PC version, or Make the keyboard act like the print So we should make QWERTZ units act like the print in the first place so that we can look at the print to press the right key. Then, if we want customize it, we can remap it to Scandic with as little as possible changes. Gigadoc2: "Personally, I am strongly in favor of the second option, to make the keyboard act like the print suggests. Not only because I sometimes need to look at the print to press the r

I also agree he should spend time getting Lineage perfect, with the hope that when ideallte does get back to work, they implement as much of it as possible in stock themself! My understanding is all of tdms work is open for ideallte to look at and straight out copy if they want, or maybe I should pay attention to licenses and stuff... but doubt they do unless forced to by whoever hires them 😉

Yes absolutely.

test9 is up. Changes: * Fix notification light. * Fix WiFi signal strength indicator. * Add fingerprint mitigations. Notes: The vibrator seems to work but I am seeing errors in the log. Please let me know if it works or not. Either way I will be looking into fixing the errors. The fingerprint backoff defaults to 2 seconds per attempt. This can be controlled via these properties: persist.vendor.fingerprint.auth_delay: the auth delay in seconds, defaults to 2. persist.vendor.fingerprint.auth_backoff: whether to backoff between attempts, d

I'm trying to push a release out today, but it may slip to tomorrow morning (Seattle time, naturally). The current fixes include fixed notification lights, fixed wifi signal strength, and a delay for failed fingerprint authentication. COVID-19 affects development because I am in Seattle which is currently in full freak-out mode over the virus. Fortunately it hasn't hampered me that much (yet).

Because @tdm's time is so limited, my personal take is it's best to just stick with Lineage related coding, despite his overflowing generosity. There are still important LOS issues like the notification LED to be worked out! ...just saying 😇

I was thinking about that too. I'm not sure how doable that is. That's also considered. Was even doing some brainstroming on how to cancel it optionally for situations where you just close the keyboard to go landscape. Filters are there to prevent those events to reach the focused application. For instance, as it is, if you close your keyboard while looking at Chrome, it will reload the page you are looking at because F5 reaches Chrome. Filter lets you fix that, optionally.

Suggestions 1) on the first one. I would suggest to immediately turn screen and touch sensing off BUT do not LOCK the device until the specified time-out Similar to Settings, Security&Location, Screen lock, Automatically Lock PERHAPS doing some pulsing with the notification LED to warn that it is not yet locked. 2) Why not offer an option to lock on keyboard close. Some of us are used to that from ancient devices. (I doubt I would use it though, but others in the forum have been asking for it) I do not quite get the four filters. Especially the

while You are waiting to get one, I'm already waiting for a warranty repair... let's say I'm not-that-happy to try their warranty service for You guys 😉

Roguelikes! The keyboard lets us play "real" roguelikes, not just the ones that have been simplified for mobile. Cataclysm: Dark Days Ahead Dungeon Crawl Stone Soup Nethack Brogue

Lucky me. I was adding water to my fish tanks, and when I lifted the 5 gallon bucket of dechlorinated water, it caught my phone holster, dropping it directly inside. I swiped it onto the couch before it even sank, then ripped it out of the holster. Of course, this caused me to hit the wake button; I saw the screen flash. Gripping the phone by the corners at the charge port end, I snapped it like a whip until the droplets stopped. To no avail, it is unresponsive. I've put it in a baggie of rice, in my oven heated to about 110F. I have little hope to see it work again. It was good while it laste

Hey all, I haven't had any problems with my Pro1 up until now, but my screen has stopped turning on, and I'm not quite sure how to fix it. I did what I had thought was a force reset (holding the power button and volume down button at the same time). It seems to have worked, as the music that was playing stopped, but the screen still will not turn on. I can tell that there is still power going to the screen, as I am able to plug the Pro1 into a charger and I see the red indicator light on the screen telling me that it's charging, yet nothing from the screen itself. Any help or advice

Is anyone having an issue with the speakerphone not working during calls? Pressing the speakerphone button during a call doesn't switch the speakerphone on. Edit: Disregard, wiping the phone fixed it.

So I decided to test the fingerprint sensor. I've had it disabled since the middle of December cuz it wasn't working well, but with fixes in place, felt like the time to test again. I spent my time recording three fingerprints, imagining all the digits I might use to unlock it. Locked, then tried, none would work. Okay, let's reboot, maybe it needs that. Nope, now it doesn't have my fingerprints saved anymore. Try again with just one fingerprint. Same deal; doesn't work, reboot it disappears.