Develop Bugs

BackTrack 5 ARM (with GUI via TightVNCServer)

Backtrack (http://www.backtrack-linux.org)
Backtrack-Linux.org, home of the highest rated and acclaimed Linux security distribution to date. BackTrack is a Linux-based penetration testing arsenal that aids security professionals in the ability to perform assessments in a purely native environment dedicated to hacking. Regardless if you’re making BackTrack you Install BackTrack, boot it from a Live DVD or thumbdrive, the penetration distribution has been customized down to every package, kernel configuration, script and patch solely for the purpose of the penetration tester.
Here is a guide to getting ARM Backtrack Running on the Xoom (tested on Wifi Only Version, running 3.1)
After much frustration I have gotten the GUI part of the backtrack 5 arm release working with the Motorola Xoom.
This has only been tested to work on the Xoom. But it should work just fine with any other device that supports linux, and should work especially well on anything with a dual-core processor (G2X, Atrix, etc.)
Pre-requisites:
- Rooted Motorola Xoom
- androidVNC from the Android Market
- Terminal Emulator from the Android Market (which you should already have)
- Backtrack 5 for ARM with Gnome downloaded and setup (check the README file, and follow the instructions.)
Link: Backtrack 5 http://www.backtrack-linux.org/downloads/. This tutorial will assume you put Backtrack 5 in the folder /sdcard/BT5 like the README says.
Launch the terminal emulator and enter the following commands:
Code:
cd /sdcard/BT5
su
sh bootbt
BackTrack will start up in shell. You will get a red line that says "[email protected]:". To verify if you type:
Code:
ls pentest
It should echo back the folders in pentest, stuff like 'backdoors','database',etc.
At this point enter the following commands:
Code:
export USER=root
vncpasswd
When you type in 'vncpasswd' this is to the the password for the tightvncserver. Since I only connect locally I just use 'qwerty' for my password, and then confirm the password. [Edit] Apparently you can skip this step, as the default password for vnc is simply, 'toortoor' (root backwards, twice).
When it asks if you want to create a view only password just type 'n' and hit enter. After you have your password setup for vnc start the server up.
Code:
tightvncserver -geometry 1280x800
When this happens you will get a message confirming that "New 'X' Desktop is localhost:1" and a bunch of other random stuff below it (it isn't important unless there are errors listed).
At this point, press the "HOME" button on the Xoom and then open the application "androidVNC".
-In the "Nickname" box, you can name it whatever you like.
-In the "password" entry, use your password (mine is 'qwerty').
-In the "Address" box you can type in localhost (or leave it blank).
****Change the port from 5900 to 5901.
[Edit] TightVNCServer uses 5901 by default, but if you are having connection errors it may have changed to something else. View the TightVNCServer logs (which I believe are under /root/.vnc/, do an 'ls -a' and a 'nano logfilename') to check to see what port was in use.
I also recommend setting the color-depth to 24-bit. After that press the "connect" button, and bam! You're rocking Backtrack 5 on your motorola xoom!!
You're welcome to repost this on other message boards of on your website, please just give me credit though. Thank you and enjoy!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

what is backtrack?
uses?

But can our wireless go into monitor mode... can it inject? New to backtrack... but know what.it can do
Sent from my LG-P999 using XDA Premium App

Whoa!!!
This is big...I'm going to do this immediately after I update to 3.1. Great job!!

renocivik said:
But can our wireless go into monitor mode... can it inject? New to backtrack... but know what.it can do
Sent from my LG-P999 using XDA Premium App
Click to expand...
Click to collapse
It would depend on if the BT developers provided a driver that has monitor mode enabled. I have it installed but haven't investigated that yet. I do know that tcpdump is on the box, so at least you can monitor your own web traffic.
OP: You don't necessarily need to change the vnc password. It comes with a default password of "toortoor"

As an aside, I'm going to spend some time this week/weekend looking into getting this to run natively. I'm doubtful that it will work but you never know.
I do know they are using Tiamet 1.3.0 as the kernel they are running, so it's possible that this can be done with a good bit of work.

There is a slight error in your commands I believe. To change the VNC password it should be vncpasswd rather than vpnpasswd.
Port for me was 5902 btw. I was stumped until I looked at the tightvnc log.
Monitor mode does not appear to work and maybe some things have changed since Backtrack 3 but I couldn't locate aircrack-ng.
Sent from my Xoom using XDA Premium App

Thanks for this. Going to try it on my nook color tomorrow. If it works, ya mind if I x-post this in their dev forums?

The command should be vncpasswd.
also BT image already contains startvnc as a command which will start the vncserver for you.
I am working on porting BT image to Xperia X10 (thread marked in Sig.)

all of these steps work on all devices or just xoom only??

fauz33 said:
all of these steps work on all devices or just xoom only??
Click to expand...
Click to collapse
I haven't tested it on anything else yet, but like launching "Ubuntu" from chroot, it should work as long as your device has a fast enough processor. The only other phone I have to test this on would be my nexus one, but I haven't gotten around to actually testing it out yet. This installation cannot hurt your phone any, so feel free to give it a shot and post your results!
chesh420 said:
Thanks for this. Going to try it on my nook color tomorrow. If it works, ya mind if I x-post this in their dev forums?
Click to expand...
Click to collapse
You're welcome to repost it, if it works, please just give me credit.
I really hope this arm distribution starts to take off, as I use the x86 all of the time on my laptop, and it would be great to have a completely functional tablet version... but they won't keep developing it if no one uses it.

i have this installed as well.
to answer the above, this only works on the xoom and the atrix. it could work on other tegra 2 devices, but is unknown on stability and support. it was made pretty much for the xoom.
also, you cannot do any wifi attacks or injections, just the nature of the beast.

How did you copy the bt5.img to the sdcard because it says file too large with fat32
Sent from my G2X using Tapatalk

This runs great man. Great work
Sent from my Xoom using XDA Premium App

Does anyone know where I can get this not as a Torrent. My work Blocks torrent traffic.

You are AWESOME!!!
I was working on something like this.
Doing this RIGHT now. You are the MAN!

vdub804 said:
How did you copy the bt5.img to the sdcard because it says file too large with fat32
Sent from my G2X using Tapatalk
Click to expand...
Click to collapse
clay_atx said:
i have this installed as well.
to answer the above, this only works on the xoom and the atrix. it could work on other tegra 2 devices, but is unknown on stability and support. it was made pretty much for the xoom.
also, you cannot do any wifi attacks or injections, just the nature of the beast.
Click to expand...
Click to collapse
For both of you check my post on Xperia X10 thread (link in sig)
file directly won't copy as 4 GB is max file size fr vfat.
i have posted a log file which contains all the instructions for resizing and getting your file out.

whould it be safe to run this on the htc evo 4g?

lewi3069 said:
Does anyone know where I can get this not as a Torrent. My work Blocks torrent traffic.
Click to expand...
Click to collapse
http://www.backtrack-linux.org/downloads/
you should see two options a direct download or a torrent
remeber you using the GNOME (arm) file

yoboii23 said:
http://www.backtrack-linux.org/downloads/
you should see two options a direct download or a torrent
remeber you using the GNOME (arm) file
Click to expand...
Click to collapse
Yea i only see torrent, but its ok i found an alternative method...

[ROM][30 June] Jellybean for the One X [Nexus Port] [JB 4.1]

This is old. See this topic
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Banner thanks to Sebianoti​I've just noticed that this has made the XDA portal. It's been up on quite a few websites today that I've noticed, and I just wanted to say a big thank you to all the writers who have helped spread the word. If you are one of them, you're awesome!
This is a port of Jellybean, based off of the roms for the two nexus devices that were released yesterday. I'm working to add in all of the key features at the moment, and it's going pretty well, so you can probably expect to see some kind of Alpha release fairly soon.
It's based off the porting work done for CM9 for our phone in the topic here, with some help from randomblame in the #cyanogenmod-dev channel. (Thanks!)
Working
Core system with little to no crashes
Not working
Wifi
Radio
Audio
Camera
Ironically, the issue we've been trying to resolve with CM9 for this phone, the rotation bug, appears to be fixed here. Not sure whether to laugh or cry
Images
http://i.imgur.com/CgWMF.png
http://i.imgur.com/DLd2U.png
http://i.imgur.com/eQRbc.png
http://i.imgur.com/htOEO.png
http://i.imgur.com/ewQrl.png
http://i.imgur.com/y4R30.png
Video (Thanks to Vere850211)
http://www.youtube.com/watch?v=whavUiVkYq8
DOWNLOAD
Remember to flash the boot.img in the zip.
Progress log
Now based off of the Nexus 7 tegra rom. Things are running a lot smoother and with little to no crashes
Wifi firmware loaded, just need to get it talking with netd and we'll have wifi
I have been able to manually configure wpa_supplicant and it successfully scans for networks. The problem now is that the rest of Android seems to be having trouble communicating with wpa_supplicant.
To those PMing me asking about porting info: Don't expect there to be a simple cut and paste way to port. If you have no experience with porting or don't at least have an understanding of how android is structured, then I would advise you to read up before attempting this. I can provide targeted help if you have a specific issue, but I won't port it for you, and please don't be offended if I suggest you go do some reading.
If you still think you can do this, then here's a checklist of the major things you should look at to get it booting:
boot.img - Grab mine or any other jellybean boot.img, and pull the entire init.rc and init.traces.rc, and package it up with a cm9 boot.img
/system/lib/modules + /system/lib/hw - Modules must be brought across from a cm9 rom, and unless your device runs the same chipset as the base you're using (tegra for the n7, omap for the gn), you'll probably need to put all of the hw libs into there too
/system/etc/firmware + /system/vendor - You'll most probably need to pull both of these dirs into the rom
/system/lib/egl - You'll want all of the egl libs and egl.conf
Various /system/etc files - There's usually some configs, firmware, and other stuff in here
/system/lib - There's tons of files in here, a lot of which you'll need to bring over, and a lot of which you'll need to leave alone. Best advice I can give you is to find an open source cm9 tree for your device and check the proprietary-files.txt file
That's it. By now you should at least have it showing the boot animation. Now it's up to you and your debugging tools. strace is invaluable if you have a specific binary that doesn't want to load, it'll show you all of the system calls it makes and the errno if one gets set. Read through the logcat carefully and it'll probably tell you if you're missing any libraries or other files. Good luck.

Nice work so far! Can the 4.1 apps be ported back to 4.0.4?
This way we can use the new apps like the launcher and what not without using 4.1?

Holy S..t! That was fast .... Awesome work mate

can you take a screenshot on the multi-language keyboard please?
they said they have changed the way to switch between languages
thanks

i ported galaxy nexus dump
only bt, hw accel, sensors works for now.
need nexus7 system dump for fix others crap

thanks
wow that was fast! great work!

Woah, fast work there buddy, btw there is a proper stable Jellybean for Galaxy Nexus released now, would that help?

Sebianoti said:
Woah, fast work there buddy, btw there is a proper stable Jellybean for Galaxy Nexus released now, would that help?
Click to expand...
Click to collapse
It would, see mdeejay's post above, but like I said in the first post my interest basically stops here, I'm not really looking to maintain this rom.

tgascoigne said:
It would, see mdeejay's post above, but like I said in the first post my interest basically stops here, I'm not really looking to maintain this rom.
Click to expand...
Click to collapse
Understandable, no point continuing tbh until source is out

Sebianoti said:
Understandable, no point continuing tbh until source is out
Click to expand...
Click to collapse
Exactly, when the source is out we can have fully working builds rather than ugly cooked up things, and I'm willing to live with ICS until then.

I don't get it... there is no Blackscreen while roating bug...
Overall nice to see!
I also worked on that the whole night got it nearly bootet up, my ramdisk was fine, the bins of my sdk may where broken...

the|gamer said:
I don't get it... there is no Blackscreen while roating bug...
Overall nice to see!
I also worked on that the whole night got it nearly bootet up, my ramdisk was fine, the bins of my sdk may where broken...
Click to expand...
Click to collapse
Haha, you're right, there is no rotating bug! As I said, I probably couldn't have done it without help from the other SDK port that was done for another phone, if I'd known you were working on it too we could have worked together and had it done faster.

System dump here apparently
http://www.androidpolice.com/2012/0...ystem-dump-is-out-modders-start-your-engines/
Is that what you guys need or am I reading wrong?
Sent from my HTC One X using Tapatalk 2

The only System dump that is really helpful is the one for the Nexus 7 cause that is an Tegra 3 driven Device!
What we really want is the AOSP Sourcecode so we can build up a nice and clean build!

Ahh fair enough mate
Sent from my HTC One X using Tapatalk 2

the|gamer said:
The only System dump that is really helpful is the one for the Nexus 7 cause that is an Tegra 3 driven Device!
What we really want is the AOSP Sourcecode so we can build up a nice and clean build!
Click to expand...
Click to collapse
The 3.0 tegra kernel for the Nexus 7 is already in the AOSP repos as part of their legal obligation. The kernel is GPL licensed and the device was released today.

tgascoigne said:
The 3.0 tegra kernel for the Nexus 7 is already in the AOSP repos as part of their legal obligation. The kernel is GPL licensed and the device was released today.
Click to expand...
Click to collapse
So nvidia have released the source code for Tegra 3?
Cause i was reading a few weeks ago they had no intentions to do so, because it might release some code that's currently used as leverage against the competition.

Atrixx said:
So nvidia have released the source code for Tegra 3?
Cause i was reading a few weeks ago they had no intentions to do so, because it might release some code that's currently used as leverage against the competition.
Click to expand...
Click to collapse
Check out the kernel/tegra repo on aosp, theres a 3.1 (I believe) kernel source in there. Not sure on nvidia's stance.

Hmm... well there are some https://android.googlesource.com/kernel/tegra.git but they are from 15th of June...
I am checking them out and will look for a "nasaki" config file

good job .. great work! :cyclops:

[Q] USB Tethering

Any word on getting around the Sprint blocks (error 67) on a stock-derived ROM? WiFi tether works fine, but I'd rather use USB since it is faster, more secure, less of a PIA, and saves battery on my phone and laptop. I'm looking for a real solution where the phone relays the PC's packets, not some janky solution that involves an application running on my computer and/or the phone changing packet headers.
I'll probably switch to Cyanogen when a stable build is out, but until then...

So, no one knows how to USB tether? Damn.

You want rndis. This has been in the Linux kernel since 2.6 or so, but I haven't seen a prebuilt kernel that has it enabled.
(I'm a Linux guy, not an Android guy, so take the following with a grain of salt...)
I've been trying to get this working, which I thought would be a fairly trivial task (Set up a cross-compiler, download the Samsung kernel sources, turn on iptables and rndis, build kernel and modules, copy over, and go home happy.)
What I've found is:
1) Setting up the toolchain and building the cross-compiler is easier than expected because folks have automated most of it. (Look up crosstool-ng... sexy!)
2) Downloading the Samsung sources is easier than expected; Samsung has 'em right on their web site.
3) Stepping into Samsung's kernel source tree is like walking into a horror movie. You can almost see little sticky notes reading "OK GUYS I GOT THIS THING WORKING, DON'T KNOW HOW, NOBODY TOUCH IT" hanging off things. Maybe I'm just spoiled by being used to kernel source trees where changes are vetted by committee.
Part of the problem is that the stock kernel that comes on the phone is not compiled with CONFIG_IKCONFIG_PROC (which would let you check out the config at /proc/config.gz), and extract_ikconfig doesn't like it either. (This means that instead of starting with a known-good configuration and changing things slowly from there, as you would on a Linux box, you get to start with a "sounds-good-to-me" configuration and hope it works, which is extra-fun given that a lot of the things Samsung added are undocumented (and occasionally unlabeled).
Anyway, I'm working on it, but just building a kernel has turned out to be nontrivial. Once I get the stock Samsung kernel compiling, getting rndis and iptables going should be pretty easy, even if the code for them has to be merged in (this stuff has been in the linux kernel forever).

As an update, I got Garwynn's newest community kernel to build using a somewhat modified config extracted from the whompasaurus kernel (which is Perseus) (I did that because I didn't want to make sure I had drivers for all the twiddles and bobs in whompasaurus). The new kernel is running great!
It turns out that a little kernel hacking is going to be involved for those who want RNDIS and the android gadget driver; config makes them mutually exclusive. It will bear some looking into to see why that is (it might not need to be set up that way). One of the gadgets excluded is the Samsung Exynos Superspeed USB 3.0 device, which I do not think is an issue for the Note 2, but could well be a deal breaker for upcoming Exynos 5 phones. I'm too tired to dig through all the drivers and see what exactly is being broken, but that would need to be done before I declared this to be a good tradeoff.
For now, I'm just going to build it with RNDIS and without android gadget, and see how my phone likes it (and how USB tethering works).
Late breaking update: The RNDIS code in the kernel appears broken. Looks like a scope-of-function problem (conflicting functions named rndis_bind_config); will hack it into submission tomorrow.

I was about to look to see how you can enable USB tether till I realized my wifi tether is just as fast
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Any updates, really need usb tether for my car stereo
Sent from my PG86100 using xda app-developers app

I tried to build kernels with all three RNDIS kernel drivers. I did some hacking to try to get the samsung gadget that includes RNDIS to build, but have stopped work on this because:
1) I think getting this to work would take a significant investment of time
2) Samsung has announced that my phone will get Android 5; Android 5 is supposed to be Linux 3.9.x; so any work I do now will be obsolete in a couple months.
Note that I am not talking about getting Sprint's paid tethering app to work; I am talking about using the native rndis support in the linux kernel. (Frankly, that's probably all theirs is too, but they got the driver to compile.
I want this to work too, but I am done messing with it until Android 5.

What is Kernel?

Hi
Guys i hear about kernel and can be flash into the device
What kernel can do?
if it helpful for the device can i have a new kernel for my device
Thanks guys

Search for kernel in Google. Kernel is the heart of our mobile. You can flash modified kernels.
Sent from my GT-I9082 using xda premium

IRAQIGHOST said:
Hi
Guys i hear about kernel and can be flash into the device
What kernel can do?
if it helpful for the device can i have a new kernel for my device
Thanks guys
Click to expand...
Click to collapse
Try google like maxxinn said for better info.
But basically, Kernel the the software between your firmware/ROM and our phone. Kernel is how your ROM governs your phone. So kernel has to be different for each phone model.
Stock kernels usually just have the essential things, just to run the phone like it should. Custom kernels have tweaks to make your phone better in several ways like faster, less lag, overclocking and better response and input options.
For our phone there is custom kernel but only for 4.1.2
k2wl is working on 4.2.2 kernel but it's not finished yet, but it's up for testing

What is KERNEL ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
A kernel isn't something unique to Android -- iOS and MacOS have one, Windows has one, BlackBerry's QNX has one, in fact all high level operating systems have one. The one we're interested in is Linux, as it's the one Android uses. Let's try to break down what it is and what it does.
Android devices use the Linux kernel, but it's not the exact same kernel other Linux-based operating systems use. There's a lot of Android specific code built in, and Google's Android kernel maintainers have their work cut out for them. OEMs have to contribute as well, because they need to develop hardware drivers for the parts they're using for the kernel version they're using. This is why it takes a while for independent Android developers and hackers to port new versions to older devices and get everything working. Drivers written to work with the Gingerbread kernel on a phone won't necessarily work with the Ice Cream Sandwich kernel. And that's important, because one of the kernel's main functions is to control the hardware. It's a whole lot of source code, with more options while building it than you can imagine, but in the end it's just the intermediary between the hardware and the software.
When software needs the hardware to do anything, it sends a request to the kernel. And when we say anything, we mean anything. From the brightness of the screen, to the volume level, to initiating a call through the radio, even what's drawn on the display is ultimately controlled by the kernel. For example -- when you tap the search button on your phone, you tell the software to open the search application. What happens is that you touched a certain point on the digitizer, which tells the software that you've touched the screen at those coordinates. The software knows that when that particular spot is touched, the search dialog is supposed to open. The kernel is what tells the digitizer to look (or listen, events are "listened" for) for touches, helps figure out where you touched, and tells the system you touched it. In turn, when the system receives a touch event at a specific point from the kernel (through the driver) it knows what to draw on your screen. Both the hardware and the software communicate both ways with the kernel, and that's how your phone knows when to do something. Input from one side is sent as output to the other, whether it's you playing Angry Birds, or connecting to your car's Bluetooth.
It sounds complicated, and it is. But it's also pretty standard computer logic -- there's an action of some sort generated for every event. Without the kernel to accept and send information, developers would have to write code for every single event for every single piece of hardware in your device. With the kernel, all they have to do is communicate with it through the Android system API's, and hardware developers only have to make the device hardware communicate with the kernel. The good thing is that you don't need to know exactly how or why the kernel does what it does, just understanding that it's the go-between from software to hardware gives you a pretty good grasp of what's happening under the glass.
​
Click to expand...
Click to collapse

j.posarekar70 said:
​
Click to expand...
Click to collapse
Nice 1 buddy

Special Thanks
Thanks guys for replay
I Will try to install a new one for my device

Features (of chipset and/or hardware) which aren't supported (yet)

Hi there, this is my first thread. Just trying to list some of the things the G7's S845 chipset and underlying Android Oreo OS would allow for but which are not available in the current state of the LG G7. This concerns the European model, although it may share the feature aspects with its other counterparts.
I shall concentrate on the sheer existence of a feature, not on how one likes or even needs it. This aims to avoid posts like "yeah, it's not there but nobody needs it anyway" and ensuing discussions of any kind.
Feel free to correct me on my conclusions and also add your points if you like. I aim to update the list in a timely manner.
Reference docs and links
Link to the Snapdragon's 845 capabilities: https://www.qualcomm.com/snapdragon/processors/comparison
And in more detail (plus PR speak): https://www.qualcomm.com/products/snapdragon-845-mobile-platform
Android Oreo (PR and overview): https://www.android.com/versions/oreo-8-0/
GSMArena's feature and spec overview (not to be taken as 100% accurate)
Hardware stuff
Qualcomm Quick Charge 4 technology
Is it available? Does the included charger support it? My current understanding (source: threads in this forum) leads me to think that there's a Quick Charge 3 charger and technology in use.
USB C to HDMI and/or DisplayPort
Not sure if this is a dedicated hardware limitation (missing chip, etc.) or something LG has disabled in the OS. I haven't tried this output method so far but from forum reports, it seems like it's not available.
[Edit] Seems like LG disabled it.
Software items (might overlap with hardware stuff at times)
Ultra HD 4K (3840x2160) 60fps video recording
[Edit] Came with "V10f" update in July. It therefore is available.
Slow motion HD (720p) video up to 480fps or FHD (1080p) up to 240fps
I saw the 240fps feature being available but only in 720p whereas the Snapdragon is capable of 480fps at that resolution.
Android Guest mode (account). What is this?
There's an option to add other accounts on your device but not the dedicated "guest" feature which enables some more restrictive rights than just adding another user.
WIFI calling (VoWiFi)
[Edit] available since the update -see VoLTE text for details-
Voice over LTE (VoLTE); VoWIFI
[Edit] There was an update today which seems to have added some carriers, which includes mine. I guess LG is on it to provide the functionality to more people as it becomes more relevant.
Additionally, the corresponding update is called ""VoLTE VoWIFI Enabler" and came automatically via the integrated updater. So there's reason to believe that VoWIFI also gained more support (which I cannot test personally). I shall mark both points as being available form now on.
Format SD card as internal storage
Does not work. Enforcing "allow apps on external" via developer options does not touch on this functionality but may serve to help in some cases where apps, by default, do not offer the option to use the sd card.
Scramble PIN entry keypad
A small item, but I kinda liked it in other OS versions. I actually have that option with other phones but not with the LG G7.
(auto) "OK" after PIN entry
Adding to the above item, it would be neat to not being bound to press ok after entering the correct PIN.
Use volume keys (long press) to change to next/previous track
I'm actually amazed that this feature isn't available. Seems like a trait most original OS implementations share, while every custom ROM I owned of course supported it.
Misc
(Officially) Unlocked bootloader
[Edit] Done: https://www.xda-developers.com/international-lg-g7-bootloader-unlock/

G6 didn't, and someone else here mentioned that the G7 doesn't either, support video out with a USB-C to HDMI cable.
Sent from my LM-G710 using Tapatalk

That's a point to make indeed, but can we deduct that it should work from the specs of the chipset and/or the Oreo features and that LG has just disabled the feature?
Anyway, I shall add it to the hardware section. Thanks for the input.

Actually, G7's bootloader is unlockable in Europe, see https://www.xda-developers.com/international-lg-g7-bootloader-unlock/
And another thing, I'm on V10d branded TIM IT (which is my SIM provider) and I have VoLTE without doing anything in particular (screenshot attached).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Inviato dal mio LG-G710EM utilizzando Tapatalk

Erpinoob said:
Actually, G7's bootloader is unlockable in Europe, see https://www.xda-developers.com/international-lg-g7-bootloader-unlock/
Click to expand...
Click to collapse
Ah, must have missed that. Will edit my list to reflect it. Thanks for the heads-up.
And on the VoLTE feature, as mentioned in the list, it seems like it's a combination of vendor and carrier work, so it shall remain in the index for as long as some fellows still report the lack of the feature while using major carriers in their country. O2 for example is not supporting it in full, although they are selling the device.
I will update the list accordingly.

USB C to HDMI and/or DisplayPort
It is a shame.
Lg has disabled this feature via software.
I have revised the kernel sources and you can see that they have disabled it.
Furthermore when you connect a displayport adapter, the smartphone detect it properly and told you that is not allowed. If somebody konw how to compile a new kernel we may take back this great feature.
Kernel source:
http://opensource.lge.com/osSch/list...ME&search=G710
You can compare it with lg v30 or galaxy s9, both support HDMI output.View attachment 4542686
Sent from my LM-G710 using Tapatalk

ricxgp said:
USB C to HDMI and/or DisplayPort
[...]
I have revised the kernel sources and you can see that they have disabled it.
Furthermore when you connect a displayport adapter, the smartphone detect it properly and told you that is not allowed.
Click to expand...
Click to collapse
Thanks for researching the issue. I've added your input to the list.

BasicallyCP said:
Thanks for researching the issue. I've added your input to the list.
Click to expand...
Click to collapse
May you can move this issue to ROM, Kernel Section? I am sure that a good developer can solve this problem and take back HDMI output.

ricxgp said:
May you can move this issue to ROM, Kernel Section?
Click to expand...
Click to collapse
Not sure how to move things but I've added a heads-up to my signature, so that other folks are able to see our small list and perhaps add to it or even work on enabling certain features.

LG g7 Indonesia supports HDMI out, adoptable storage
G7 camera sensor (imx351) only supports up to 240fps
QC4 / USB PD is locked at 18W max

Thanks for those details. Do you happen to have some sources for them?

Android Pie update brings this feature to LG G7 . Just got the update today and tested this function. Soon after connecting, get black bars on all 4 sides. Just pinch out, you get a normal display on TV. Nice