EvilDragon 164 Posted August 18, 2020 Share Posted August 18, 2020 SE215 Wireless, from 2019 Supports Qualcomm aptX, aptX HD, aptX Low Latency, AAC and SBC. Quote Link to post Share on other sites
Wheeljack 207 Posted August 19, 2020 Share Posted August 19, 2020 I bought a secondary prepaid SIM which I'm going to activate next week. For now it sits in slot 2. To not get warnings I've deactivated slot 2. In this state when I turn on the Pro1 it doesn't ask for the PIN of SIM1 right after startup. I have to lock the phone first and then unlock it again for the SIM unlock screen to pop up. 1 Quote Link to post Share on other sites
EskeRahn 5,350 Posted August 19, 2020 Share Posted August 19, 2020 11 minutes ago, Wheeljack said: it doesn't ask for the PIN of SIM1 right after startup Interesting bug! Does this mean that sim1 is active bypassing the pin? Or 'merely' that both are deactivated (despite you only requested sim2 deactivated). Can you do calls/sms/mobile data on sim1? Quote Link to post Share on other sites
Wheeljack 207 Posted August 19, 2020 Share Posted August 19, 2020 I don't have mobile until the PIN for SIM1 is entered. 1 Quote Link to post Share on other sites
EskeRahn 5,350 Posted August 19, 2020 Share Posted August 19, 2020 Thee first weeks after it went official we got weekly Monday builds. But not the last two Mondays. I see a lot of pending stuff described herehttps://download.lineageos.org/pro1/changes/ Anyone knows what is preventing these from going 'live'? 2 Quote Link to post Share on other sites
tdm 2,322 Posted August 19, 2020 Author Share Posted August 19, 2020 55 minutes ago, EskeRahn said: Thee first weeks after it went official we got weekly Monday builds. But not the last two Mondays. I see a lot of pending stuff described herehttps://download.lineageos.org/pro1/changes/ Anyone knows what is preventing these from going 'live'? Apparently there was an issue with the build server configuration. https://buildkite.com/lineageos/android/builds/25787#2280946e-4537-4166-9eaa-79e9dbfb50d5 You can track all Lineage builds here: https://buildkite.com/lineageos/android/builds Note the nice pretty shade of red all the way down the page... 😄 4 Quote Link to post Share on other sites
EskeRahn 5,350 Posted August 19, 2020 Share Posted August 19, 2020 2 minutes ago, tdm said: Note the nice pretty shade of red all the way down the page... 😄 Thanks for the info and link. and indeed the first green is on page 6 💚 Quote Link to post Share on other sites
Wheeljack 207 Posted August 19, 2020 Share Posted August 19, 2020 Interestingly no builds on August 10th. Quote Link to post Share on other sites
acrux 56 Posted August 20, 2020 Share Posted August 20, 2020 10 hours ago, Wheeljack said: Interestingly no builds on August 10th. 2 Quote Link to post Share on other sites
EskeRahn 5,350 Posted August 20, 2020 Share Posted August 20, 2020 17 minutes ago, acrux said: Good to know that it is not a thing specific to the Pro1, but a more general issue. 3 1 Quote Link to post Share on other sites
JooJooBee666 84 Posted August 20, 2020 Share Posted August 20, 2020 (edited) @tdm Just an FYI, but my VoLTE and WiFi stopped working some time ago and no matter what I do it won't work again. I put the sim back in to an iPhone7 and it works fine there. I've rebooted and toggled all the settings but still no go. So something is definitely not working right here and its not a direct carrier issue. I don't know if it's just LineageOS or also applies to stock as I don't have an easy way to test with stock. Just thought I'd let you know.🙄 Edited August 20, 2020 by JooJooBee666 1 Quote Link to post Share on other sites
EskeRahn 5,350 Posted August 20, 2020 Share Posted August 20, 2020 9 minutes ago, JooJooBee666 said: @tdm Just an FYI, but my VoLTE and WiFi stopped working some time ago and no matter what I do it won't work again. I put the sim back in to an iPhone7 and it works fine there. I've rebooted and toggled all the settings but still no go. So something is definitely not working right here and its not a direct carrier issue. I don't know if it's just LineageOS or also applies to stock as I don't have an easy way to test with stock. Just thought I'd let you know.🙄 Stock is even pickier on VoLTE it seems... https://community.fxtec.com/topic/3055-volte-voice-over-4g-data/ Quote Link to post Share on other sites
wilhelmfitzpatrick 47 Posted August 20, 2020 Share Posted August 20, 2020 11 hours ago, EskeRahn said: Good to know that it is not a thing specific to the Pro1, but a more general issue. The person who maintains all the Lineage infrastructure is currently moving house, so that may be connected. Quote Link to post Share on other sites
order#10248 65 Posted August 22, 2020 Share Posted August 22, 2020 Today I took the time to flash Lineage OS , following the instructions at https://wiki.lineageos.org/devices/pro1/install . My Pro1 has physical qwertz keyboard layout and I prefer German as system language. So i did the following steps (sorry for writing german setting names here): "Einstellungen" --> "System" --> "Sprachen & Eingabe" --> "Physische Tastatur" -> "Builtin Keyboard" -> "Tastaturlayout wählen" + "einrichten": Checked Deutsch (Android Tastatur). Still no change: Most keys seem to be "shifted" , i.e. pressing "f" then a "d" is printed . After searching and reading for ages here without success, I found the solution rather accidently: There is another option for keyboard settungs which is not translated and so can not be found by search (with german words ...): "Einstellungen" --> "System" --> "Erweitert" --> "Keyboard" (scroll all the way down) --> "Layout" where it is possible to switch between QWERTY and QWERTZ ! Searching in settings for "fn" (and tapping on one of the two matches) are leading there also. I think an appropriate hint belongs to installation procedure. Cheers, order#10248 2 3 Quote Link to post Share on other sites
dicer 36 Posted August 23, 2020 Share Posted August 23, 2020 On 8/19/2020 at 11:21 AM, EskeRahn said: Interesting bug! Does this mean that sim1 is active bypassing the pin? Or 'merely' that both are deactivated (despite you only requested sim2 deactivated). Can you do calls/sms/mobile data on sim1? I got this too: When I boot, Lineage is not asking for the SIM pin (only one SIM installed) and I can start using the phone. SIM is still locked though and of course no internet/calls. If I then turn off the screen and turn it back on, the PIN entry is shown. 2 Quote Link to post Share on other sites
GameboyRMH 15 Posted August 23, 2020 Share Posted August 23, 2020 Anyone know why exfat-formatted microSDs report as having an unsupported format? A kernel limitation, or this bug? https://gitlab.com/LineageOS/issues/android/-/issues/1404 Quote Link to post Share on other sites
tdm 2,322 Posted August 23, 2020 Author Share Posted August 23, 2020 13 minutes ago, GameboyRMH said: Anyone know why exfat-formatted microSDs report as having an unsupported format? A kernel limitation, or this bug? https://gitlab.com/LineageOS/issues/android/-/issues/1404 It is the pro¹ kernel. I need to add the exfat driver. Stock did not include it. 1 Quote Link to post Share on other sites
Wheeljack 207 Posted August 24, 2020 Share Posted August 24, 2020 The LineageOS signing server is back online since yesterday and new nightly builds are appearing again. The Pro¹ build from today (20200824) installed gracefully via OTA on my phone. 2 3 Quote Link to post Share on other sites
Jonathan 16 Posted August 25, 2020 Share Posted August 25, 2020 (edited) On 8/18/2020 at 4:12 PM, EvilDragon said: I'm not sure if this is related to LineageOS or something else, but I have a small problem with Bluetooth: I've got a headset (Shure) which is also recognized as headset (you can see that from the symbol). However, all apps (Audio Recorder, WhatsApp, etc.) I tried always use the internal phone microphone instead of the headset one. When I connect a wired headset, this works fine - it's only an issue with Bluetooth. Any ideas? I can confirm the same issue. I use Bose NC 700. It works as I can hear everything fine through the headset, but I need to hold the phone as a microphone for others to hear me. EDIT: This releates to apps (in my case Slack). The native phone app does not seem to have this issue. Edited August 25, 2020 by Jonathan Quote Link to post Share on other sites
agent008 238 Posted August 25, 2020 Share Posted August 25, 2020 (edited) HELP! The OTA update - 20200824 installed automatically but now the phone can't boot. The only thing I have done differently from the install instructions is I've used OpenGapps instead of MindTheGapps. After the update installed succesfully and prompted me to reboot the phone, I got a Lineage OS animation for a long time (about 5 minutes) and then an error message, something along the lines of "not possible to boot, you might try a factory reset" With options to either Try Again or Factory Reset. I rebooted into the bootloader and then powered off the phone from ther eto get to work. Tried to turn it on again, and now it's just stuck on the Lineage logo animation for maybe 15 minutes. Is it possible to get a boot console from the phone via USB? Maybe then I could try to find what's amiss... EDIT: I pressed the power button from the LOS animation, phone rebooted and got to the screen again, image below. Edited August 25, 2020 by agent008 Quote Link to post Share on other sites
marmistrz 93 Posted August 25, 2020 Share Posted August 25, 2020 Same here, no gapps at all. I tried downgrading (unsupported, I know), but the recovery doesn't accept sideloading in either case (both 20200803 and 20200824). I'm simply getting adb: sideload connection failed: no devices/emulators found adb: trying pre-KitKat sideload method... adb: pre-KitKat sideload connection failed: no devices/emulators found 1 Quote Link to post Share on other sites
_DW_ 628 Posted August 25, 2020 Share Posted August 25, 2020 Think I'll hold off updating! 😄 1 1 Quote Link to post Share on other sites
Hook 2,820 Posted August 25, 2020 Share Posted August 25, 2020 (edited) I will just say that manual sideloading of the 20200824 update went smoothly. I always sideload, have never trusted OTAs (not because I have ever tried them, so I don't actually have a good basis for not trusting them). So, AFAICT, there is nothing wrong with the nightly zip. (I also always resideload addonsu and Gapps-- I don't trust the "Preserving Gapps" stuff. 😉 Edited August 25, 2020 by Hook 1 1 Quote Link to post Share on other sites
agent008 238 Posted August 25, 2020 Share Posted August 25, 2020 (edited) I am waiting for any help before factory resetting. It'd save me many hours setting up all over again. EDIT: If I reboot to bootloader and select "Boot to Recovery", I still get the error screen. So at the moment sideloading the update is not possible. Edited August 25, 2020 by agent008 Quote Link to post Share on other sites
acrux 56 Posted August 25, 2020 Share Posted August 25, 2020 Interesting - shouldn't the A/B slot system be for just these cases - updated slot fails to boot and you can boot the previous slot which is still OK (without the update)? Can you switch the active slot at bootloader mode to previous one and try to boot that one? 3 Quote Link to post Share on other sites
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.