Leaderboard

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.

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.

So here's an unexpected twist. It took me a while to get around to actually packing up the phone to send it, but friday I finally made some time. I figured I'd flash it back to stock before sending it - it was still running the test12 or test13 build. I'm not sure but I don't think this was a requirement per sé as long as it was running android - I figured it be less work for support. Anyhow as I was going to box it up, I thought I'd just check the camera one more time ... and lo and behold it's working again. I took it from the firmware in the guide through all the updates so it

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!

I got mine a good month after stock got assigned. Most of the time was wasted in customs though. Luckily the paperwork went through fine.

So, I recently received my new screen incl. digitizer from ali(express). It had unfortunately cracked the screen from the speaker and down about 3.5cm to the left edge (from a 20cm drop, but still my fault, so nothing to pun fxtec about) First thing I noticed when I was taking the phone/screen apart, was the the "glue" was rather uneven distributed, and that the screen had cracked between the glued part and the "not so glued part". Perhaps they have to look into that process? Second thing, it seems like this screen is better at displaying colors at lower brightness than the original

Installed Test20 smoothly, both with and without addonsu root.... 😄

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.

...yess...thats normal on "untracked/uninsured" packages from china (wish/ali/ebay etc.). I have record 11 days delivery time and another record 5 months 😄

Okay I'll look into it when I get a chance.

It still got the bug that holding the LiveDisplay icon in notifications fail to launch it. Sure it is a trifle....

@tdm built and installed. I'll let you know if I see anything amiss and get some avc logs over.

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.

Vendor is not part of roomservice, you need to update that manually.

Have you tried asking info@fxtec.com, or by using the support form on this site or by asking @Erik? If a mistake was made, they can ferret it out.

And how do you know when this retailer ordered the ones they allegedly got or expects to get? They might be "pre-orders" too for all we know. Just saying.

Long story sort, my problem seems to be a software / SD Card handling issue and not hardware-related. A few days ago, I have noticed my phone lighted up its display a few minutes fter I have connected it to charger, but in the morning, it seemed okay, however, it wrote I have to give my passcode after reboot - hmm. Later, it also restarted after charger connection and it was not able to boot up for a few hours (Android tried it again and again, so it is not a cold boot.) Then the latest update came on the very same day - I have installed it late evening / early in the morning, the

Couple updates, especially for the developers out there... I'm working with one of the upper level Lineage guys on getting the device/kernel officially imported. He has made quite a few comments and suggestions for cleaning and improving the device tree. So the lineage-16.0 branch on my device tree is going to be rebased and rearranged quite a few times in the next couple days. I tagged test18 so it doesn't get lost. Said Lineage guy is actually interested in the Pro1 and I will probably send him a prototype unit. So that's even more development support. Which is g

Can I get some folks to review this before I submit it...? https://harryyoud.co.uk/lineage-previews/280778/4/devices/pro1/ Thanks!

Received tracking number for #54XXX, QWERTZ, paid May 7th 2020. Yay!* *Feeling confused? Just poking fun. This was a replacement order for my phone that got lost in transit to Fx for a repair back in February. They've been nice enough to let me skip the queue on it, but it still took a while as you can see.

When talking using MTP/PTP for backups I will point the attention to a nice bit of code by Christophe Geers, that I have modified slightly to offer incremental backups, and not just totals. Source and program available here

To answer your question directly, Android has its own unique init system (not based on sysvinit or upstart or anything else). The init "language" declares various things, including services (eg. daemons). Services by default are restarted when they crash/exit, infinitely many times. They can be marked "critical", in which case the device reboots when they crash too often (5 per minute, I believe), or "oneshot", in which case they are not restarted at all. Your symptoms could be either software or hardware. Software issues might be a service that continually crashes or even mayb

I experienced a lot of reboots since the 202006 update. Today I tried to use OsmAnd for navigation, and my phone lasted no more than a few minutes until it decided to reboot again. Very frustrating ... Unfortunately I was not able to pinpoint the problem 😞

I have received mail on 6th July 2020 stating that "we have now allocated stock to your order, which is due to be shipped on Thursday/Friday this week" but still date no update...even after whole one year..still Fx Tec is not confident about the delivery.....i can understand they face many technical issues like bugs, screen leaks etc, after that production issues but they cant even do.. proper management of orders delivery. Should be done in systematic manner...so what is the point of pre-order.