Closed steadfasterX closed 3 years ago
@ANDROID2468
Ok great rild cannot start as we still have an issue with the cam so
next is to take from 2BA these and push them here:
those files don't exist on 2ba. They’re similar files to those without the _open at the end
Can you show those? I have no access to my pc rn. Just list them or a screenshot
@steadfasterX
Then just take from 2BA these and push them here:
one thing that is strange is that it took more than 2 min for the rom to recognize the sim
one thing that is strange is that it took more than 2 min for the rom to recognize the sim
nope that isn't strange. It can take from 0 seconds to 2min until it gets recognized. That is the case since we had to switch the blobs for Oreo which are also used in Pie ofc. see Suicide-Squirrel/issues_oreo#6
so what does not work atm? only cell service? cam, sound, sensors all ok?
update:
http://leech.binbash.it:8008/lineage/oreo/vs986-UsU/experimental/
contains the latest version which has the above files included already.
Ah f... Pls remove the above attachment as it contains your imei. I guess the above logs are taken from my last build from today ?
thx, no more screenshots.
Screens are fine but just take care about sensitive data :) so what about my question?
yes, I took these logs today.
Ok my fault then.. I am rebuilding rn as the current one is not in permissive mode :( I started from scratch and missed to reset the mode from enforcing ..
Ok now again in permissive mode:
lineage_vs986_usu_2019-05-16-2205.zip
Pls again :)
ok some little changes . nothing obvious found yet but lets try fixing stuff. New build up:
lineage_vs986_usu_2019-05-19-1019.zip
procedure as usual pls ..
also pls tell me what works?
btw: you should always do this while trying my new builds:
ok some little changes . nothing obvious found yet but lets try fixing stuff. New build up:
lineage_vs986_usu_2019-05-19-1019.zip
procedure as usual pls ..
also pls tell me what works?
- [ ] sensors?
- [ ] sound?
- [ ] gps?
btw: you should always do this while trying my new builds:
- go in android settings -> mobile network -> deselect automatic networks (may failing - do it anyways)
- try to select another network type (switch between 2G, 3G.. and wait after each one 1 min at least)
Everything you mention above works. I couldn't find the setting to switch between 4G and 3G, so I didn't do that. I did deselect automatic networks though. here are the logs: full.log dmesg.log radio.log
good. wifi error is gone now. what about WiFi and bluetooth in general does those work, too? The settings is named "Preferred network type" and should be found in "Settings -> Network/Internet -> Mobile Network" or try the search lens in settings. They are somewhere and we def should test it. Will grab through the rest of the logs now..
WIFI and Bluetooth works. even playing music through Bluetooth works well!
the preferred network type doesn't actually say 3G, 4G, or any G, it just says this: (no leaking my IMEI this time. :/ )
anyway, that's why I got confused.
logs after changing the settings ( my cable fell out of my phone at the end before ending the logs, I need a new cable :) )
dmesg.log
full.log
radio.log
WIFI and Bluetooth works. even playing music through Bluetooth works well! the preferred network type doesn't actually say 3G, 4G, or any G, it just says this: (no leaking my IMEI this time. :/ ) anyway, that's why I got confused. logs after changing the settings ( my cable fell out of my phone at the end before ending the logs, I need a new cable :) ) dmesg.log full.log radio.log
thx for your report and sorry for the confusion. the way how 2G, 3G and such get displayed is different for each country .. I forgot that one. so I may figured out something not sure though. pls flash this file here in TWRP after clean flashing LOS: [file-removed] afterwards .. again as usual ... take the logs (and many thx again for your time working on this with me!!)
@steadfasterX & @ANDROID2468 - thanks both for working on this! 👍
I can't flash as much as @ANDROID2468 is, but once you get it heading towards stable (at least for data & calling), I can try flashing on my phone too. The VS986 is my primary device, so needs to work at least reasonably well before I can flash and test with you guys. :)
@numericOverflow this phone is still my main phone too! this rom is pretty stable besides calling and SMS not working on Verizon. and it runs fast!
@ANDROID2468 - Calling & SMS are the two deal-breakers that I need working ;)
@numericOverflow yeah, me too.:wink:
I PM'd steadfaster a vs986 i found on eBay for $50 USD. If we can get him the device he'll be able to make way faster headway
I'd chip in $25 towards testing hardware if it meant easier support for a developer.
@OnlineGravy @numericOverflow that is a great idea but I would be worried about ILAPO though. I can't help with the donation right now though I wish I could.
@ANDROID2468 new test-build up with some heavy changes inside (maybe making things worse or better - we will see).
proceed as usual and grab the logs pls.
This time do also this (wait at least 2 min after the boot has completed before doing so):
adb shell ls -la /dev/socket/qmux_radio
(req root access, so adb root
before or magisk it)
thx!
@steadfasterX ok downloading it now. I just saw the email from github just now.
@steadfasterX
here are the logs:
full.log
dmesg.log
radio.log
here is the output of runing adb shell ls -la /dev/socket/qmux_radio
:
total 0
drwxrws--- 2 radio radio 60 2019-05-28 17:33 .
drwxr-xr-x 10 root root 760 2019-05-28 17:30 ..
srw-rw---- 1 radio radio 0 2019-05-28 17:30 qmux_connect_socket
The sim no longer gets detected in this build.
Thanks will look into the logs ASAP. Well yeah the SIM does not detect issue was kind of expected while I hoped it would work. Anyways could you also check if camera and sound is still working?
@steadfasterX The camera and sound are still working.
@steadfasterX here are the logs: full.log dmesg.log radio.log here is the output of runing
adb shell ls -la /dev/socket/qmux_radio
: total 0 drwxrws--- 2 radio radio 60 2019-05-28 17:33 . drwxr-xr-x 10 root root 760 2019-05-28 17:30 .. srw-rw---- 1 radio radio 0 2019-05-28 17:30 qmux_connect_socketThe sim no longer gets detected in this build.
ok there is a new upload: vs986-ril-test.tgz download that one and boot to TWRP. then (if not flashed LOS atm, flash it first, then proceed):
adb push vs986-ril-test.tgz /tmp/
adb shell
mount /system
cd /system
tar xvzf /tmp/vs986-ril-test.tgz
sync
then reboot and grab just the full logcat
we may have to repeat that step several times as I currently replace RILD completely which has a lot of dependencies only showing (best showing) in the logcat after booting..
here is the log: full.log still no sim
here is the log: full.log still no sim
ok next one uploaded (v2). if you have the time join here: http://webchat.freenode.net/?channels=%23carbonfusion-user&uio=d4
say my nickname (stea [press TAB key] for auto-extend and ENTER) so I get notified. I also would like to have a tmate session on your system if possible as that would ease up the testing..
@steadfasterX I herd that Verizon is switching to GSM. could that fix this issue?
@steadfasterX sorry, I got false information. Verizon already use GSM as their base network. but January 1, 2020, they will discontinue CDMA
@steadfasterX I did more research on Verizon switching to GSM and I got more questions than getting answers. So the information I got was from here "https://www.quora.com/When-will-Verizon-Wireless-switch-to-GSM-in-the-US.", A Verizon Customer Service Representative said "Verizon already has GSM as its base network. and As of January 1, 2020, CDMA is no longer going to be supported OR EVEN FUNCTION on the Verizon network."
so I went to switch my phone to GSM on stock 2BA firmware and I got no signal. so maybe the support rep was wrong and they don't have GSM yet? So I looked at one of my family member's pixel 2 (for a newer example) to see what network type it was using and it was still on CDMA! I wonder how many peoples phones are going to break by January 1 after they shut off CDMA. And Sorry about the two paragraph comment. :)
@steadfasterX I did more research on Verizon switching to GSM and I got more questions than getting answers. So the information I got was from here "https://www.quora.com/When-will-Verizon-Wireless-switch-to-GSM-in-the-US.", A Verizon Customer Service Representative said "Verizon already has GSM as its base network. and As of January 1, 2020, CDMA is no longer going to be supported OR EVEN FUNCTION on the Verizon network."
so I went to switch my phone to GSM on stock 2BA firmware and I got no signal. so maybe the support rep was wrong and they don't have GSM yet? So I looked at one of my family member's pixel 2 (for a newer example) to see what network type it was using and it was still on CDMA! I wonder how many peoples phones are going to break by January 1 after they shut off CDMA. And Sorry about the two paragraph comment. :)
sorry for the long silence.. was a bit busy .. then a lot of LOS fixes.. anyways.. so hm no GSM really?! interesting interesting.. verizon is special in several ways yes..
freqs:
This carrier only accepts approved devices on its network....
when you say you went back to stock: how? did you just flashed system + boot or removed UsU completely?
@steadfasterX Yeah, I noticed. Sorry I wasn't clear. Stock as in just system and boot.
@steadfasterX Yeah, I noticed. Sorry I wasn't clear. Stock as in just system and boot.
good! I was a bit scared but that means we MUST be able to fix that..
@ANDROID2468
I need this from you:
requires strace: http://leech.binbash.it:8008/misc/ --> strace.bin
adb shell
su
setenforce 0
strace -y -f -a 120 -s 200 -tt -p 1 2>&1 | egrep "faccessat|fstatat64|openat|denied|fail" > /sdcard/Download/ril_stock.txt
(this will show nothing but should not exit. just go on.)
terminal B:
adb shell
su
stop ril-daemon
start ril-daemon
adb pull /sdcard/Download/ril_stock.txt
adb root
adb shell
setenforce 0
strace -y -f -a 120 -s 200 -tt -p 1 2>&1 | egrep "faccessat|fstatat64|openat|denied|fail" > /sdcard/Download/ril_los.txt
(this will show nothing but should not exit. just go on.)
terminal B:
adb root
adb shell
stop real-ril-daemon (hint: yes this differs from the stock guide above)
start real-ril-daemon (hint: yes this differs from the stock guide above)
adb pull /sdcard/Download/ril_los.txt
thx in advance
@steadfasterX That first command doesn't work. :( This one: strace -y -f -a 120 -s 200 -tt -p 1 2>&1 | egrep "faccessat|fstatat64|openat|denied|fail" > /sdcard/Download/ril_stock.txt
@steadfasterX That first command doesn't work. :( This one: strace -y -f -a 120 -s 200 -tt -p 1 2>&1 | egrep "faccessat|fstatat64|openat|denied|fail" > /sdcard/Download/ril_stock.txt
do you have telegram? send me a photo of the terminal and the commands entered or attach it
The command is cut-off but it's all there.
original report: https://forum.xda-developers.com/showpost.php?p=79380937&postcount=176
I am not able to test vs986 ROMs due to the fuses it blows on booting my h815 so this cannot be solved without help (mainly flashing and catching logs)
if you wanna help:
https://forum.xda-developers.com/showpost.php?p=79491366&postcount=191
chat / help / communication
https://webchat.freenode.net/ channel:
#carbonfusion-user
say my nick there (stead
TAB
,ENTER
)I am there from Mo-Fr, 9am - 5pm (UTC +2)
refs