[LG V20 Guides, News, & Discussion] emdroidle:
Huh. I've tried this and didn't find any indications of problems. I've got an updated `kdzwriter` written which should provide additional diagnostics, but I need some more time testing before I'll release it.

Right now I have to remain skeptical of this. If they're now using another sensor, which requires additional software, and haven't released that software; then they are in clear violation of the GPL. A number of companies do this, but they're not supposed to.

I'll try to bring this up to their attention, could be someone merely missed releasing a tarball.

Drat. Now I wonder whether it was the extra changes to the kernel that made things work, versus merely some additional file(s) which effect this problem. :(

Sounds like your analysis of aboot was wrong on the location of the SIM slot count. Luckily this is fixable, but may take some experimentation.

Very interesting. Good news is this shouldn't be too complicated to fix, in fact depending upon your comfort area you might be able to fix this yourself. This is also very interesting because it hints that even the single-SIM devices have most of the software for dual-SIM functionality present on them. It may be possible to install a H990 KDZ on a H990DS and vice-versa.

This is actually very much like one of the things that happened during early development. With my initial kernels once I got the screen working, I had to get dual-SIM working. One part of this was simply adding "lge.sim_num=2 lge.dsds=dsds". Without that the menus supporting dual-SIM functionality didn't show up. Sounds like the area in misc [MENTION=2764901]exadeci[/MENTION] came up with for finding the SIM count was off and as such now we need to search for an area which has the correct count (note even though [MENTION=2764901]exadeci[/MENTION] was wrong here, [MENTION=2764901]exadeci[/MENTION] was crucial to getting the modem functioning). For a single-SIM device it instead would need "lge.sim_num=1 lge.dsds=none".

The inelegant fix is simple do `dd if=/dev/block/bootdevice/by-name/boot of=boot.bin`. Transfer this file to somewhere a binary editor is handy and simply change the "lge.sim_num=2" to "lge.sim_num=1" and "lge.dsds=dsds" to "lge.dsds=none". Then simply copy the modified file onto boot. I'd like to get some information about your phone though since we now know about this issue.

This could be due to parts of the software thinking it is dual-SIM while other parts think it is single-SIM (could also be some of the software doesn't work dual-SIM). I'd target fixing that first, since it may very well take care of this issue.

I'm attaching a small program for trying to identify viable areas of misc. This needs to be run as root. The invocation for you would be `h990-siminfo -1 -o matches.dat`. This is simply searching misc for the character '\x01' and '1' which should occur near where the SIM count is, post the "matches.dat" file and I'll be trying to compare and see whether anything works (we need something which is 1 on a H990 and 2 on a H990DS). There is a distinct chance the program will fail, but it is quite unlikely to do any damage if it fails (haven't done a lot of testing yet, but it was written carefully). This will give a bit of output about how many matches it finds. This should run perfectly fine either in Android or TWRP.

MD5: d9988cd6f39ba62baf806016a74f0a2a

SHA160: 2c4a9a38caf6fbbeab2a03621dba098501a8e8e6

SHA512: 2275949f2c660f6bc33734604050686db2c956df3a02d38975d9775f044194ae36ac9a9eeee63a36ee69255ff84673b2920c7fe2a848b01f87ef6877c6c12a22