pebert
Members-
Content Count
102 -
Joined
-
Last visited
-
Days Won
6
Everything posted by pebert
-
forgot to confirm this, but yes, this is the correct connector for pro1
-
regarding chargeing the battery, I did it by soldering wires directly to the connection tabs on the battery cell. the hooked it up to a lab PSU, 500mA @4.2 V do requires soldering skills and and good knowledge on how to treat Lithium cells though.
-
Hi I guess you coul do it the other way around, send your PCB to me and I can replace your USB-connector
-
so, managed to bring new life in my beloved device. 1. disassemled the unit to accss and manually charged the battery, this stopped the strange boot loop. (phone still only goes to fastboot) 2. instead of using my pretty new computer running win10 I connected it to my 13 year old laptop running Debian made it able to communicate in fastboot. 3. flashed original ROM via fastboot (phone still only goes to fastboot) 4. (almost a bit embarresed to say but...) manually change active slot via fastboot. Now it boots π 5. flash Lineage again and change active
-
Hi guys I had me pro1 in the drawer box for i while now since it won't boot. Tried today to EDL flash it, everything seems good, device is detected as it should, flashing progress is going as it should. When flashing is done, i see the message that I can remove the device. But, it only boots in to fastboot, don't boot normally and won't boot to recovery. Any ideas?
-
LineageOS 19.1 Official Release for Pro1
pebert replied to wapsi's topic in Pro1 - Thoughts & questions
Will give it a try with the last nightly OTA Would prefer not to set everything up again π -
LineageOS 19.1 Official Release for Pro1
pebert replied to wapsi's topic in Pro1 - Thoughts & questions
Maybe I was a bit unclear, I just went from the previous nightly release -
Possible to replace Pro1 key caps?
pebert replied to lawliett's topic in Pro1 - Thoughts & questions
it was issues getting them off, might be a bigger issue putting them back though π I i belive the keys on a gamer keyboard is pushed a little bit more frequent than the keys on my phone π -
Possible to replace Pro1 key caps?
pebert replied to lawliett's topic in Pro1 - Thoughts & questions
I'm planning to cast key caps in transparent acrylic or epoxy resin, paint them black on the top and then laser etch the new characters on them. -
was more thinking that itΒ΄s a more relaiable source with a MOLEX connector that you can buy in a lot of different places, with short delivery lead time. I will order some from Mouser to test with. Looked a the USB-PCB from my crashed phone, if I could reuse that PCB to prepare it for a fast swap. But that PCB is quite bent, so I doubt it will work. //Per
-
Molex 1054500101 Maybe this can be the correct connector?
-
I have a Dell dockingstation for my laptop, think it's a WD19. I tested to connect my pro1 to it and it worked like a charm even if I got the same picture on all 3 monitors. audio out worked, as did keyboard, mouse and wired ethernet. Didn't test the microphone input though. Planning to put that dock in my car.
-
maybe something like this would do the trick? https://global.microless.com/product/l-tsa-tp4056-micro-usb-5v-1a-lithium-battery-charging-protection-board-te585-lipo-charger-module-black-blue-bcbg0011/?currency=usd
- 1 reply
-
- 1
-
guess you already solved it, otherwise use one of these next time https://global.microless.com/product/l-tsa-tp4056-micro-usb-5v-1a-lithium-battery-charging-protection-board-te585-lipo-charger-module-black-blue-bcbg0011/?currency=usd TPA4056
-
LineageOS 19.1 Official Release for Pro1
pebert replied to wapsi's topic in Pro1 - Thoughts & questions
also the long press pop-up for the keyboard looks strange now. -
I managed to do the same thing when I upgraded the firmware on all my spare displays. something got shorted and the ribbon cable was sending smoke signals... fourtnatley I managed to dissconnect it fast enough to not make ane permanent damage, except the ribbon that de-laminated in a few millimeters
-
LineageOS 19.1 Official Release for Pro1
pebert replied to wapsi's topic in Pro1 - Thoughts & questions
OTA updated to 19-20220620-NIGHTLY So far I havet noticed a few strange behaviours * My NFC is not working anyomore, doesen't react at all when trying to activate it. * Celluar connection is unstable, and having harder to keep up the connection during hand over. * Wi-Fi is really unstable, sometimes i don't find any networks, sometimes I can connect but don't get a proper IP assinged, meaning no internet access. * the device is generally slow, takes really long time to launch apps * apps like Vanced and parallel space stoped working * Magisk lost root access -
Display units with large tap-insensitive margin
pebert replied to EvilDragon's topic in General Discussion
for me the touch worked perfectly after flashing OTA 2020-08-25. And the fastboot flashing worked fine as well after removing the "rem" from the line in the script that flashes the system image π So now I have upgraded all the 4 spare displays I have, hopefully I can stay on LOS for a while now. //Per -
Thanks I will give this a try tomorrow.
-
Display units with large tap-insensitive margin
pebert replied to EvilDragon's topic in General Discussion
How do I preform a adb sideload on that? Or do you mean fastboot? -
Display units with large tap-insensitive margin
pebert replied to EvilDragon's topic in General Discussion
Where do I find the latest software? And why is the OTA endpoint no longer responding? Is fxtec out of business? -
Display units with large tap-insensitive margin
pebert replied to EvilDragon's topic in General Discussion
Oh, yes, EDL i mean. Pretty close though, M is only one step away from L. The software I used is dated 2020-07-07 on this page http://files.nwwn.com/android/pro1/factory.html I did a check for a OTA system update, but there where none. Isn't that a bit strange? -
Display units with large tap-insensitive margin
pebert replied to EvilDragon's topic in General Discussion
Fastboot flashing procedure went flawless under win10. Unfortunately the phone got stuck in a boot loop, changed the active slot, but still didn't boot. Did a EDM flash instead, so now the phone boots up as it should on stock software. The reason for flashing my phone was the fix the issue with the touch unresponsive margins on the sides, but this time it didn't work, so I still have that behavior. Any idea why? -
Fastboot flashing procedure went flawless under win10. Unfortunately the phone got stuck in a boot loop, changed the active slot, but still didn't boot. Did a EDM flash instead, so now the phone boots up as it should on stock software.
-
Interesting reading, Maybe the easiest way is to boot from my previous harddrive with windows 10 then.