EskeRahn

A little foot note I'm not quite sure where to put. Just noticed on a Pro1X (not Pro1), when in OFF state pressing the power/button briefly, will have the led blink briefly, green if full, I do not know if it will use other colours in a lower state. So if a Pro1X will not boot, this might be helpful in telling whether it is a depleted battery or something else....

AFAIK this flag helps the Pro1 better than the Pro1X, but personally have set it on my Pro1X too - I never understood why this flag is not set by deault on ALL phones. I see the Auto-on function as a really odd function that it is hard to imagine a use case for. (Maybe auto-on could be usable for some with a handicap making it hard to use the powerswitch? But if so I guess they are unlikely to want a keyboard phone) But some things in Android are just oddly opposite to what you would expect. E.g we do not get a warning of risking privacy information when enabling location services, o

I beleive they had answered that. The problem is that there needs a minimal amount of charge in the battery to have enough power to boot enough to have the charging activated. AND combined with it not turning it self off early enough it is ALSO a future issue once it gets charged. So make sure it is never allowed to run flat....

Glad you finally got it, but sad that it is in a useless state... Well the only known remedy is to disassemble it and charge the battery directly with a suitable circuitry. That is what FxTec is doing with returned units. So sad that the road from production to delivery has been so long that this happens to several... So the only options I see is to return it/them to get fixed, or to disassemble it and charge. Rather than some fancy circuitry I have seen some suggest to use three 1.5A batteries coupled, as they have a limited power and thus are unlikely to damage the battery.

Necromancing this thread, please note that though this idea works fine on a pc (in a sufficiently large window), it does not work well on a all mobile browser landscape/portrait (*). Here you have to click the avatar and scroll down to "About" and "Rank" to see the info. On some mobile browsers you can select "Show as desktop site" or similar though, and have it appear. (*) ADD using Chrome it works in landscape, with my current "Font size"=Large and "Display size"=Small settings.

(lineage-20.0-20231028-nightly-pro1-signed.zip on Oct 6 security patch installed smoothly (*) using adb sideload and MindTheGapps-13.0.0-arm64-20230808_213316) Updates seem to have changed from Mondays to Saturdays for the Pro1

I think I can answer that part. If I remember correctly then at some point those with pre-orders were promised it would be with tax included (this might have changed for newer web-orders though). But I do not think such a promise were given on IGG. Hence the difference.

I do not know if it will ever be produced to stock. There are those with several years old orders that need to be served first, and they have not said when those will be all served... If you are in a hurry, it might be worth looking on ebay, occasionally some are up for sale. Also keep an eye out on this thread:

Last update 20231016 seems to have thrown the Developer options setting away, but can be reenabled, so adb connection works.. lineage-20.0-20231021-nightly-pro1-signed.zip on Oct 6 security patch installed smoothly (*) using adb sideload and MindTheGapps-13.0.0-arm64-20230808_213316 This update preserved the Developer options setting, as usual. Note the date, Not the usual Monday - not that it matters.

Working with Fastboot tends to be extremely picky on the connection. I have had good experiences with inserting a hub between the computer and the phone. Or to select a USB 2.0 port Fastboot can work with USB 3.0 but is really picky. When I go through my thunderbolt connected docking, and use a USB 3.0 port on that it works smoothly, but not directly connected to the laptop.... ...On windows it can also be quite picky on the driver...

Thanks, but could you give us a rough ball park figure of the fraction of the total covered after the 700+ ? E.g. which of these do you estimate to be the closest : 10% 30% 50% 70% 90% ??? Or the other other way round if you prefer, how large a fraction will be pending afterwards.

(lineage-20.0-20231016-nightly-pro1-signed.zip on Oct 6 security patch installed smoothly (*) using adb sideload and MindTheGapps-13.0.0-arm64-20230808_213316)

It was working fine, until seconds before I did the update. It seems to have crashed the user partition either during the flash of the boot.img, or the following attempted boot into recovery mode (That failed requesting a reformat). (I did retry several times, and also aborted and booted to fastboot-mode and retried the flashing - after doing a new download just to be sure, but the partition was smashed)

Lineage-20.0-20231009-nightly-pro1-signed.zip KILLED USER PARTITON, FORMAT NEEDED, From there it installed smoothly using adb sideload and MindTheGapps-13.0.0-arm64-20230808_213316, ends on on Sep 5 security patch.

Thanks for all the extra info. As you now know the count, l would love to know roughly how large a fraction of the waiting that will be served with the recovered devices

Can not say for sure, but I think it for security purposes is quite hard to get the information out if the OS will not boot. If you can get it to boot into Fastboot-mode, you might be able to access the partitions though, and most likely it is the User partition you are after. If you get that far, you will have to search for tools extracting from it. This might link you to relevant info

Sad that it took ths long, but at the least someone found the time to do it.

(lineage-20.0-20231002-nightly-pro1-signed.zip on Sep 5 security patch installed smoothly (*) using adb sideload and MindTheGapps-13.0.0-arm64-20230808_213316)

Note that the Titan comes with a nice little app called app blocker, that maybe its settings you need to adjust to your needs. I see I was a little late there, sorry...

Ah and BTW i restored from a Pro1 too, so that in it self is not a fix. A had turned off both Wifi and BT scanning from apps. But overlooked the "Notify for public networks" (under Wi-Fi preferences), so just turned that off). That would certainly indicate some scanning. My hunch is that it is when doing something like updating apps it fails, that is not continuous download, but paused by the installs, and it then fails to use it again.

Are you sure on "OCT"? Mine says 4.14.186.gd5b54dace-dirty #25 Wed Sep 14 14:02:09 CST 2022 (And yes, no n, so no dirty dance...) And the build number is Titan_Slim:EEA_20220810 (indicating a month earlier

@Rob. S. "EEA" here. I have noticed that using Netguard (that is a software VPN) helps a lot, though no silver bullet.

I have rarely used the pocket, but as they are so close to identical, I would expect that most pros&cons would be the same function-wise. The difference being the lacking 3.5mm port and the extended display. I can see in my mailbox that I got a letter from kickstarter on 20220922, about the system-update. So could make good sense that they then for the pocket, did the small adjustments, and released it stamped a few days later.

Just notice the "pocket" in the build name. I was talking the slim not the pocket. (The pocket is packed with protective plastic and everything, so will not try to start to update....)

Found this on the FAQ tab here https://www.unihertz.com/products/titan-slim No such app exists in the version I got, but there is a "System upgrade" and an "Upgrade app". Tried the trick on both - to no avail. This update https://www.kickstarter.com/projects/jellyphone/titan-slim-the-new-sleek-and-slim-qwerty-android-smartphone/posts/3503739 also talks about "wireless update". So tried to change the language from proper English to US, that had no influence.