tdm
-
Content Count
801 -
Joined
-
Last visited
-
Days Won
84
Posts posted by tdm
-
-
7 hours ago, claude0001 said:
Build 20210922 is available. It includes the September 5 AOSP security fixes.
As of this release, the build includes a backported patch, originally made by @Slion for LOS 18.1, which allows one to use "Fn-Tab" and "Alt-Tab" equivalently for switching Apps (see this thread). I find that feature really useful when holding the Pro1 by the keyboard.
I have used that modified keyboard driver for weeks without issues. Still, be warned that this code has not been merged into any official LOS branch yet, and should thus be considered experimental.
Edit:
I think I should clarify: the driver included here corresponds to @Slion's "patchset 7" in 315155, i.e. the version before "modifier passthrough" was introduced. I follow the discussions around improving the keyboard driver in LOS 18.1, but will probably backport to 16.0 only what seems useful to me personally ...
Maybe you can try this... I just uploaded it and will merge to 18.1 in a few days after I clean it up a bit.
https://review.lineageos.org/c/LineageOS/android_kernel_fxtec_msm8998/+/316402
-
3
-
3
-
-
27 minutes ago, Hook said:
oh, quick question before I go to bed. Is there an R boot image/recovery?
You should be able to use pretty much any recovery to install it.
-
1
-
2
-
-
This is now official. Builds are weekly, currently scheduled for Wednesdays.
Install instructions are exactly as LineageOS 18.1.
Download site:
Enjoy!
-
2
-
8
-
-
6 hours ago, pebert said:
Yes, it worked great, both with a simple USB-C to HDMI adapter and my Dell WD19 USB-C/Thunderbolt docking station, here I get both the 3 monitors and the USB-devices like mouse and keyboard.
Now the monitor gets activated, detects a source, but both the monitor and the phone display stays black until I remove the USB cable again.
This is most likely a kernel issue. I am using the Lineage 17.1 kernel as-is. I'll investigate.
-
12 minutes ago, pebert said:
Hmm... Have I missed one to install one update?
Oh my fault, I was thinking lineage. Did any previous aicp versions ever work properly with HDMI out?
-
3 hours ago, Rob. S. said:
Is there perhaps a chance to get ExFAT support in LineageOS 17.1+? As of now, it seems it isn't there, as i can't unload my camera that formats its SD cards as ExFAT, and my camera doesn't accept cards formatted as FAT32, either, so I'm out of luck (today, the camera maker's app somehow didn't function properly, either, so I had to go through my laptop...).
As @tdm seems to have successfully enabled ExFAT in AICP, it looks like it would theoretically be possible?
I might choose to switch to AICP at some point, but as of now I'm extremely happy that I have an excellent phone that does nearly all I want it to do with LineageOS 17.1, and, as is my tendency, I'm rather reluctant to change a working system. 😉
Sorry, the Lineage admins don't allow exFat unless the device shipped with it.
-
2
-
-
1 hour ago, pebert said:
Whith the latest OTA upgrade I have a bug with HDMI out. When I connect the USB-C cable to my device it goes tottaly black if I unlock it.
I can se the lock-screen, but when I entered my pin-code all is black until I remove the cable.
What is the date of the last working build?
-
I still have the AOSPX 9.0 tree. They were working on rebasing 10.0 at the time I was building it, so I never did an AOSPX 10.0 build. Which do you guys want, 9 or 10? There are pretty much no changes in 9 since the initial build.
-
1
-
2
-
-
17 hours ago, Jonathan said:
Just installed AICP. Still exploring, but love the extra features so far. Thanks @tdm. Your work on LOS and AICP has made the pro1 experience amazing!
I found a potential bug.
Looks like I can customize some advanced navigation commands. (in other words, when you long press/double tap navigation buttons.) I tried it out and it works for the most part. But I don't seem to get split screen functionality to work. Starting split screen the normal way works fine though.
Navigation command for camera don't work either, but I uninstalled the normal camera in favor of gcam, so that might be on me. Would be nice to be able to have it work with non-defaults as well though.Yeah split screen seems a bit buggy. I think R is far enough along that any bug reports should probably wait.
-
1
-
2
-
-
7 hours ago, Jacob_S said:
Had that with every OTA so far. But I can't tell you if it's a reason to worry. At least I never had any problems.
I've not seen the OTA updater crash. But then again, I don't use it much and never with official builds. What crashes and when? Can you get a logcat of it crashing?
-
2 hours ago, internationaltraitor said:
any wod of an update to AICP R ?? :))
There have been rumblings of starting official release builds, so I'm guessing in the next couple weeks.
-
7
-
-
4 hours ago, Hook said:
Just curious, given the small scale of this development effort. Will this be portable to the Pro1x with a different SOC. or will it remain Pro 1 (SD 835) only?
It builds off Lineage, so I will just wait for Nolen and Bruno to do the hard work... 😄
-
3
-
3
-
-
Indeed, all your data is still present. Do not believe any messages that tell you otherwise.
The Pro1 is an A/B device. If an update fails, you should be able to go back to the other slot using fastboot. There are myriad pages on the internet about where to find the fastboot binary for your PC and how to enter fastboot on your phone. Once you are ready, simply run "fastboot --set-active=a" and reboot. If that does not work, try "fastboot --set-active=b" and reboot.
Alternatively, @claude0001 is correct. You should be able to manually install the latest nightly. If you use gapps, don't forget to reboot into recovery and reinstall gapps before starting LIneage.
-
3
-
-
24 minutes ago, Hook said:
Sorry, forgot to ask, will the link in the op have the new version as before? I prefer to flash over ADB and may have to anyway when I gwt my Pro1 back from repairs. Could you change the date in the description of the linkin the OP when you load a new one? Not a big deal, but would let people know it's the newest file when the file has the same name always.
Yes the link in the op is always up to date. It is a symlink on the server.
I'll add the link to the actual file and the md5 hash for clarity.
-
5
-
-
New build is up. Build date is today, 2021/02/06. It is available via OTA (settings -> aicp -> updates) or direct download. Changes are virtually all security/bugfix updates, updates to the adblock hosts file, and language translation updates.
-
3
-
4
-
-
2 hours ago, pebert said:
where do I find, and how do I install the latest build?
Settings -> AICP Extras -> Update Center. You will get a notification when a new build is available.
2 hours ago, pebert said:Don´t remove it, sounds like a great function, just the one I have been looking for, only I could understand how it works.
I have edited a keymap, and put it in that folder. but I can´t manage to make it active. is there any documentation of this somewhere?
This is for the kernel keymap, by the way. I posted some instructions a long time ago in the Lineage 16.0 thread. Perhaps someone can find them. Here is the exact file location:
By removing it, I meant the toggle in the UI. The system should still read and apply a custom keymap, but providing an option to disable it when the custom keymap file is present isn't really useful. Why not just remove/rename the file?
2 hours ago, pebert said:sorry, strange question. What I should ask was, Which Is the phone calling app included in the build?
The default AOSP app, I believe.
-
8 hours ago, pebert said:
Hi
Have been running this as a daily since November now. It works pretty good, with some minor bugs, where do I report them?
Here is a good place. Or if you prefer discord, perhaps we can make an AICP channel in the Pro1 discord. Or we could make a Pro1 channel in the AICP discord.
8 hours ago, pebert said:Btw, I'm on an early november release, don't realy know where to look for the revision.
The bugs I seen are
1 sometimes the phone report "charging mode" or something similar in the status bar, did manage to caprure the logs for that.
I doubt this is AICP specific. It is more likely an issue with hardware or kernel.
8 hours ago, pebert said:2. a couple of times, like three or four, the touch screen and usb-port has stopped working, I hane note managed to capture the logs with this fault present. I have not been able to open settings by only using the keyboard, is that possible to do? and sine the usb isn´t working, I can´t use ADB either.
Again, this is most likely a hardware or kernel issue.
8 hours ago, pebert said:some questions:
how do I upgrade ´the software? always from my PC, or is there a OTA function?
There is an OTA function. This is an unofficial build, so there are only updates when I choose. And I have been busy with other things for a while. All the developers are working on R now, so Q is pretty stable. There have been a few security updates since the last build, so I may do another soon. But expect R to be available sometime in February.
8 hours ago, pebert said:there is a lot of different network modes to choose from, how do I know which one to use in sweden?
Sorry I can't answer this one. 🙂
8 hours ago, pebert said:how do I get the custom keymap working? I have tried some way, but not succeeded.
The custom keymap setting is not obvious. It is for advanced users. If you create a custom kernel keymap file and place it in /data/keyboard/layout (I think that's the correct path), the setting will allow that custom keymap file to be used. If you don't have a custom kernel keymap file, the setting is not useful. I should just remove that option entirely, to be honest.
8 hours ago, pebert said:which Phone app is best to use?
That is subjective. 🙂
8 hours ago, pebert said:is there any tips on how to get call recording to work?
I have never used call recording, and I do not know if AICP supports it. If it is important, perhaps you can ask in the AICP discord?
-
1
-
1
-
-
On 1/25/2021 at 2:21 AM, PokeParadox said:
Hello!
I have a Pro1 which is displaying nothing on its screen. I can get into EDL mode and I have access to both Windows and Linux PCs both in 32bit and 64bit environments...
I have only tried this flasher in Win10-64b, used Zadig, installed the WinUSB driver, phone is detected but flashing only gives "Unknown Error"
Where do I go from here?(Help!)
First, keep in mind that EDL is a "one shot" protocol. You must reset the phone between each attempt. You can tell the phone resets in Windows by watching the notifications and listening for the plug-in sound. In Linux, run something like "watch -d lsusb" and you should see the device disappear and then reappear with a new device number.
Things to try:
- Use a different cable.
- Use a different port on the PC.
- Try with/without a hub.
- Try a different PC.
Note these issues are not specific to Pro1, this is common with EDL. I recently used EDL on a OnePlus 7pro and it refused to work on one PC. I tried a different PC and it worked first try.
-
1
-
13 hours ago, shubell said:
I have a blob question. What is AICP's stand on using other blobs like those found on codeaurora?
I don't know exactly what blobs you are talking about. Can you be more specific? But generally AICP is pretty lenient with their policies.
-
6 hours ago, SteffenWi said:
Hey, hope you had a couple nice days and a happy new year 😉
I need it to be able to flash /e/ as it seems. When I try to flash from a LineageOS recovery iso I get a weird error. Apparently that doesn't happen with TWRP.
Setting aside that /e/ is basically a rip-off of LineageOS, the TWRP referenced in the Sailfish thread should work for this purpose. If not, perhaps @Sean McCreary or another developer can help. I simply don't have the time or desire to build TWRP right now.
-
2 hours ago, Laska said:
I just can't wait.
Also, is there any way to decrypt data partition for the same reason?
Not currently. If I could decrypt data, I'd have a decrypting TWRP released by now. 🙂
I am hoping that backing up an FBE encrypted data partition (eg. while in recovery) and then restoring it in the same environment will work. But I have to test that out.
-
2
-
2
-
-
19 hours ago, Laska said:
Thank you very much for your great work. But how exactly will it work? And how restoring process will look like? From PC or from the device itself?
Well, the standard Unix-y part of it will be a CLI tool with arguments more or less like tar. But the backup and restore arguments will likely be limited to block devices and directories, though that is not certain yet. Block devices will be backed up as a single unit of data (as you would get with "dd") and directories will be backed up recursively (as you would get with "tar"). It will also have a client/server mode similar to rsync, which will communicate over sockets (meaning remote backups are possible without using tools like stdio pipes or sshfs etc.)
Android will surely use the client/server mode in order to get the appropriate permissions for backup and restore. The backup will ideally be accessible from recovery, so this means an unencrypted directory under /data and providing a statically linked version of the tool.
After the CLI is working, I plan to write a simple app to drive it. Not sure exactly how that will look yet.
-
3
-
-
Just now, Laska said:
For me, it is mostly for backups, flash and build in file manager where you can revert changes when you make some errors and mistakes (example: broken xposed module).
Yes, backup and restore is far and away the biggest thing people want out of TWRP over and above the "standard" recovery.
The main thing I'm working on now is an archiver. It will be able to backup and restore directly from Android, no recovery required. Among other things, it will feature compression, encryption, incremental backups, and both local / remote storage. And it will work on any Linux system, not just Android. I plan to use on my own systems once it's working well.
-
7
-
-
On 1/4/2021 at 6:52 AM, Rud said:
Well, if the ProX comes with Android 10, I se no reason why us Pro1 owners shouldn't get an update at the same time, since it's basically the same phone. (2 more gigs of RAM shouldn't make that much of a difference OS wise)
You would be amazed at all the things that need to align for two revisions of the same model device to get the same updates. Not saying it won't happen, just warning you that it is not as straightforward as it seems on the surface.
-
1
-
PRO1, AICP 16.1 (Android R) Official Build
in General Discussion
Posted
No I've been off doing other things. Maybe one day...