tdm
-
Content Count
801 -
Joined
-
Last visited
-
Days Won
84
Posts posted by tdm
-
-
8 minutes ago, Craig said:
THANKS!! Does this include netman's kernel fixes (keyboard chording/etc), and mccrearys work on keyboard and slider stuff?
Nope, not yet. That will come soon.
-
3
-
-
test3 is up on my server. I haven't fixed FM radio or the fingerprint reboot issue yet, but I'm tossing this out because it's been way too long since any updates.
-
2
-
2
-
-
2 hours ago, Gigadoc2 said:
@tdm: Is the switch from test2 to test3 requiring a wipe because of switching from stock vendor to lineage vendor? I am asking because I've built from your repositories already and for me it does, but I could be doing something wrong.
I have not tested this, but it is plausible.
-
36 minutes ago, Gigadoc2 said:
To my great surprise, I have to object here. I just re-locked the bootloader after flashing a self-singed LineageOS build, and it still boots. I even disabled OEM unlock...
I don't really know whats happening here. This does not sound like what the android documentation says, and also not how other bootloaders behave. But I have a re-locked bootloader now that boots my LineageOS...
That should not be possible. Perhaps the boot loader lock is disabled or ignored.
-
33 minutes ago, D1ggs said:
Hey @tdlnxhow far along is the ROM? Is it cause for a daily driver or should we wait until it gets more stable.
That will be up to you to decide. If you are hesitant, wait for a few days after I release test3 tomorrow and see what others say. But I believe it will be mostly on par with stock except for the FM radio.
-
1
-
4
-
-
1 hour ago, skrilax said:
I see. Could you also provide an userdebug build?
I don't see why not, but I'm curious why you want userdebug?
-
Sorry I don't actually know what's going on with Verizon or VoLTE. I use AT&T and old fashioned GSM voice. But after things are stable in a few days, I can start investigating VoLTE.
-
3
-
-
That screen is the adups updater. The OEM tossed the adups files into the build as binary blobs (not source code), so I doubt they have access to fix it.
Personally I'm less annoyed by the spelling and grammar than the fact that you cannot get out of setup without agreeing.
-
1
-
-
13 hours ago, skrilax said:
Just for me to understand: this rom contains all the physical keyboard / launcher tweaks that can be found on stock ROM? And is this an userdebug build?
Yes this has everything from the stock build. It is user/release same as stock, not userdebug.
13 hours ago, skrilax said:Also, why can't you just do this "fastboot flash --disable-verity --disable-verification vbmeta_a vbmeta.img" to disable verity and then install gapps (feels like that from OP).
That may work, feel free to give it a shot and report back.
13 hours ago, skrilax said:And speaking of disabled secure boot - is there a way to boot the device into PBL without having to disassemble it (i.e. when people are repartitioning etc.)?
EDIT: Yeah I see the filename, it's user build.
See my factory restore thread. Start with the device off, hold both volume buttons, press power for about 3 seconds. The device should be in EDL mode.
-
I think I'm now back where the original test2 build was:
- Cell radio works same as before (still can't make voice calls).
- Notification light works. I still need to review and cleanup the code though.
- Front camera works (I was missing some camera libs).
Additionally:
- I've added the keyboard layout file to the vendor partition and that seems to work.
I'll try to fix the FM radio and the fingerprint issue today. Both of those may be more involved. In any case, I'll have a test3 tomorrow at the latest.
-
1
-
3
-
-
I worked with @EvilDragon today and we were able to revive the device. The xbl_a partition was corrupted. This should have been written with the factory tool, so I need to investigate why it did not get written properly.
-
1
-
8
-
-
Hmm, there should be one. I'll take a look after Lineage is stable.
-
1
-
-
On-device audio and nfc now work. I'm out of time for the day, so I'll try to get this wrapped up tomorrow.
Remaining "big" items blocking test3:
- test/fix cell radio (should be working or require minor tweaks).
- fix front camera (it's not recognized, probably a missing file).
- fix notification light.
- fix FM radio.
- figure out why the fingerprint sensor loses its data at reboot (at least for me).
- add keyboard layout file.
-
3
-
8
-
-
Okay it looks like Bluetooth, WiFi, GPS, and Fingerprint work.
Still need to test/fix cell radio, on-device audio, and NFC.
Note the WiFi signal strength indicator is still broken. That's going to be toward the end of the to-do list.
-
5
-
6
-
-
Progress! After waaaaaaaay too long, I've finally fixed the wlan subsystem restart. Turns out the open source power HAL isn't working properly. The vendor power HAL works. So I'll use the vendor one for now and continue on with all the other stuff.
-
7
-
6
-
-
WiFi is starting now but it's crashing the device. I've been trying to figure that out. Shouldn't be long.
-
3
-
-
1 hour ago, Derecho said:
First of all, thanks for working on LineageOS support for this phone.
I've obtained the phone yesterday and I put your test build 2 of LOS on it and I've been playing around with it since. I noticed the WiFi symbol issue, but it doesn't seem to affect anything so that's nothing really. I did also notice the problem wih the / key, especially when typing URLs, which was a little problematic. When I then noticed that Esc and other modifier keys weren't working well on ConnectBot, I got FinQwerty's keyboards installed and I'm now using a US International one, this solves most of those issues.
One thing remains with the keyboard though, regardless of whether I'm using stock keyboard mappings or FinQwerty's, and that is that I can't type special characters from the locale I set the keyboard to. From my Photon Q and previous keyboard phones I'm used that if I long press for example an l, I see a menu popup with characters similar to it that I can then tap to insert, like the ł symbol. I normally use this to be able to somewhat comfortably type Polish on such a hardware keyboard. However, when on this build (not sure about stock Android, hadn't tried really) I long press a key, it just repeats itself endlessly. Is there any way to configure this behaviour? Is a modification to the OS required?I haven't really investigated keyboard things yet. I've been busy getting the vendor image working in order to fix a2dp. But I know that idealte put the keyboard config files in system instead of vendor, which is why its broken. I'll put them in my lineage vendor once it's working. As for other locales, I haven't tried at all yet.
-
3
-
-
35 minutes ago, Gigadoc2 said:
But I thought it was officially not wanted anymore? The xda post and https://review.lineageos.org/c/LineageOS/android_device_lineage_sepolicy/+/257100 kinda sound like it is being dropped deliberately.
Well, I'd be glad to be wrong 🙂
I've not seen a thorough discussion on the subject, even on internal lineage slack. With several hundred people making up lineage, there are undoubtedly people who want it and people that don't. The major reason it's been dropped is that the security changes in Q make it even more difficult to support. Since it's not really a core feature it will get done last. And if it turns out to be really difficult or intrusive, it may just get dropped. At least until someone with the motivation and ability comes along.
-
4
-
-
9 hours ago, Polaris said:
Sadly, I believe it's more correct to say Lineage HAD a su addon package.
Indeed, sad but true. It's currently not working in 17. I'm hoping they will figure that out. And if they don't, me or someone else likely will.
-
2
-
3
-
-
2 hours ago, Gigadoc2 said:
@tdm: I figured out what went wrong with the doze apk, and someone else did simultaneously: https://github.com/tdm/android_device_idealte_msm8998-common/issues/1
Good catch thanks. Obviously I started with a lineage tree that had built other devices which pulled in these dependencies previously. I'll make a note to fix that.
-
6 hours ago, VaZso said:
I don't think encryption is a huge problem unless the keys are hidden from users...
...and here comes the problem with it.If system locks you then prevents you to reach your data in case of a failure as not giving its keys - then it means this encryption is definitively not made for you.
...so that way I rather would like to see my phone unencrypted.So nobody should say encryption is for users till the OS is not willing to give keys for users to able to access encrypted data.
...as they don't do it, then it means basically encryption go against the user thus it allows the manufacturer to have access of data (being the "God" there) but prevents user to do anything with it even in case of a failure. It is very sad anyway.
So in such a word, I don't need encryption - simply because I would like to keep the possibility to assess my _OWN_ data also in case of a hardware failure.
Who need it is the manufacturer, including G and not me.Yes this is true. The actual encryption key is not accessible. There are valid(ish) reasons for this. If that is not acceptable to you, feel free to change your fstab and run unencrypted. I won't do it and I won't support it. IMO the benefits far outweigh the lack of knowing the actual key.
If the hardware fails to the point that you cannot decrypt using the Android scheme, how do you expect to extract unencrypted data? And don't say backups, because backups can be made in both cases (TWRP will happily decrypt and backup).
-
8 hours ago, Ralf said:
Thank you for all this work! I have some questions regarding "official support": what part of your code will later go into the "official" LOS sources, is it all that is in android_device_fxtec_pro1 (this is what people call the device-tree I suppose) or are there other changes in the "generic" LOS sources needed as well?
In other words: as long as the device code is not included in the LOS sources the builds are "unofficial", once it is included it becomes "official"?
Also: what happens if the code became "official", but for whatever reason you stop to maintain the pro1 part. Will it be removed from the official sources?
These are rather LOS generic questions, but I could not find this information on xda and since you are here I decided it would not hurt to ask 😉
The device tree and kernel tree will be imported into Lineage github for official support. Any changes needed for this particular device in the other Lineage code will need submitted and approved by the Lineage team. I don't have any of these changes yet, and may or may not eventually need them.
The device becomes official when I tell the Lineage team that it's ready and request that they import the code. I also need to add a Lineage wiki page and etc.
The device will continue to receive builds add long as at least one person is maintaining it. (There are at least 3 people with the pro1 and the ability to maintain it so far.) When nobody is left, official builds will stop.
-
1
-
-
2 hours ago, silversolver said:
I'd be very interested to know why you hate magisk. Also, I want my device unencrypted. I am much more worried about being able to recover my stuff if things go badly than I am someone else getting it.
By its nature, it hijacks basic system functions and hides/overrides things. That's bad in my book. Same as xposed. After 7 years of working with Android ROM development, I've seen the trouble these types of things can cause.
And since they usually work fine, the device maintainer (me) gets blamed when they break in odd ways. Lineage (and previously CyanogenMod) bug forums are littered with crashes caused by these things. So the first thing the alert developer does is look for evidence of these tools and reject the bug report if found.
So basically, they cause much pain and lost time for people like me. It's so not worth it.
-
3
-
-
2 hours ago, EvilDragon said:
What do you suggest to use for rooting if not Magisk? Good old supersu?
Lineage has an su addon package. AOKP (which I love and always use) has su builtin.
But most of the time, I keep su disabled and use "adb root" from my PC if I need to tinker with things.
-
1
-
1
-
LineageOS, Current status : 16.0 Test Builds
in Support
Posted
Found the issue with the fingerprint reader. The hardware and Android keep separate lists of registered fingerprints. When you wipe data, Android list is cleared but the hardware list is not. Eventually the hardware has all 5 slots filled and won't accept any more. So the new data only exists in memory and fails to write to persistent storage.
I'll investigate more to see how this is supposed to work, and I should have a fix soon. In the meantime you can delete the fingerprint files under /persist to fix it.