Leaderboard

Apparently Ethan Chen[*] has a Pro1 and he's been hacking on it lately. So Nolen and I are going to be massaging the device code to incorporate his changes. Nolen says that Ethan has incorporated a lot of cool stuff to make the device perform better. [*] Who is Ethan Chen? He is arguably the best active Lineage device maintainer out there. I worked with him at Cyanogen, and he is truly a whiz at doing device stuff.

Not sure exactly what you are asking. All updates within the same major version (16.0, 17.1) will keep all add-ons. But when you update major versions (say, 16.0 to 17.1) then you will need new gapps. The su add-on isn't available for 17.1, yet anyway, but you would also need an updated su if/when it is. When you switch from my test builds to official Lineage, you will need to do a manual install of the official zip just like you install/update my builds. After that, the OTA system is engaged.

If you got stock assigned, it's coming. Another week or even two, what does that matter at this point? Be happy. You'll have a great keyboard phone soon. why waste so much energy on whining when you could be happily anticipating. Sheesh, at least wait to see if it's Monday or Tuesday (OMG, one to two days late). If they stopped to do updates for every phone, they wouldn't have time to actually see to it that they get out. They said it is coming. It will. Be excited.

Digging this out again, ignoring the last part of the thread title as you do. Today I've received the unit replacing my old #344 which had been lost in transit back in February: #89. Yeah that's not a digit missing or anything. Odd, if nothing else.

Same update procedure as always. Once you have Lineage, you don't need to bother with the boot img. Reboot into recovery. Sideload the update. Reboot recovery (to switch slots). Sideload gapps, su, etc. Reboot to Lineage. And as soon as this goes official (later this week?) the OTA system will do the updates for you, just like stock. And it keeps all your addons (gapps, su) through the updates.

Thanks bro, your right. But all excitement is actually over now.... anyways lets wait some more days..(hope this time days not convert in months....☺️☺️☺️)

Don't think I've seen that bug reported for lineage. But then again, if the issue is not specific to the pro1, some lineage developer probably saw and fixed this in lineage before the first pro1 ever rolled off the assembly line.

I tried filming my WT745 earlier tonight but I noticed I can't film with stereo audio for some reason, and the audio itself is very quiet. Wat do?

test21 is up. Changes: * Update blobs and string to stock 2020-07-07. * Switch back to custom livedisplay implementation. * Import changes from Ethan Chen (thanks to Nolen for doing this). Note the changes from Ethan are too extensive to enumerate in a few lines. There are some cool performance improvements along with lots of under-the-covers cleanup.

Just a quick note: It finally worked for me! I just ignored the device for 4 or 5 weeks, supposedly letting the battery drain completely just like suggested above. Then, I held down both volume keys and the power key before inserting a standard USB cable. I let go of the power key after a while and the QUSB__BULK device appeared in the Windows device manager. The flash tool detected the device and flashing a stock firmware image worked on the first try! Thanks to everyone!

Thanks. Given the timing of your message, I don't think you got the latest device tree change (the livedisplay switch). You might want to re-sync and make sure you are up to date with the test20 tag on all three projects.

test20 is up. This is pretty much the final code that will be imported into the official Lineage trees unless any issues are found. Changes from test19: * Update kernel to latest code from Qualcomm and IdeaLTE. * Update device blobs and strings to latest stock (2020-06-20). * Switch to standard livedisplay implementation. * Add WiFi MAC address setting from stock.

The past 48 hours or so my phone spontaneously rebooted around 3 times. BUT I also seem to find out that if I use the Debug shortcut (Power + Volume Down) it rebooted my phone as well, so I do wonder if some of the reboots were actually triggered by the hard keys in the pocket and not actually spontaneous. Captured a debug report anyways, not sure if FXtec/IdeaLTE wants to look at it.

Just a quick follow up... F(x)tec Support sent my replacement screen out on Friday, I received it less than 24 hours later, replaced it as per their video instruction, and it's now working perfectly again! Only had one moment where I had the two side by side, and nearly forgot which was which... I hope you get your replacement soon @hka. For me it's top marks for F(x)tec's support, and also for the easy repairability of the Pro1. I lost my Sony Z5C for weeks for a repair under warranty, and had to send it straight back again because it hadn't been repaired pro

So, we add to $PATH, as our bug report system and most debugging relies on it being installed -- no point in expecting it to be in local dir/explicitly called by path each time. I'll make sure to do end-to-end tests of the install instructions and get the wiki up to par as needed - I work on Lineage's Wiki too pretty frequently. Also OT: Am the guy TDM is talking about above. Stoked to help out with the device.

There is no dream OS. Everything has tradeoffs. But mainline linux with real X support with good touch UI window manager and full android app support with optional full google safetynet (tap-to-pay etc). And if we're dreaming it can run x86 and x64 apps too. And since already getting ridiculous with dreams, also it can run dos & windows apps.

Frankly, I just want smoothly operating Android, which Lineage is fast becoming. I've used Android for 10 years and have assembled a fine set of Apps that do what I want in pretty much the way I want them to do it, allowing me great productivity, especially with a physical keyboard.

For me, an up-to-date Maemo with Android app support...

On the bright side, as far as my understanding goes, the crackling can be patched without having Google to certify the new version (only needs to happen for security patch levels). So let's hope they can get to that now. Long overdue anyways, considering how often they put gaming into the spotlight on the Twitter account.

What a dick.

https://akiba-pc.watch.impress.co.jp/docs/news/news/1264/831/amp.index.html You can see and buy the real thing in the store.