Well, I came to the point where I want to try android. Here we go!
I am acceptionally fluent in LWJGL, and I was wondering if there is a way to use LWJGL on android devices? Or do you have to use the given API from android?
No, it only works on a desktop.
Also, no offense, but saying you’re exceptionally fluent is ignorant and makes you sound bad.
Although, there is OpenGL ES. That’s pretty much OpenGL, but its a little different.
OpenGL ES is the api you will use in the standard Android libraries (at least one of them). Make sure you use OpenGL ES 2.0 (the setup can be a little troublesome), make sure you don’t cross 1.0 with 2.0 and make sure you know what features OpenGL ES doesn’t have (it is essentially a watered down version of OpenGL as you would expect). If you are so exceptionally fluent then you will have no problem.
Also, I’m sure it was just a typo but, I found it really funny that you spelled “exceptionally” with an “a.” Not sure why. Not sure why I told you.
Oh my god, the number of times I’ve done that on my phone.
Or You could use LibGDX and have less worries
I think scrapping everything you have created so far and swapping over to a new library that requires learning and experience of the api all over again and yet does not serve any extra purpose required of it over the original would not lead to less worries. Quite the opposite.
In fact we have pointed @wessles to a library that is standard in Android, requires no specialised setup and shares 100% of the core features and api to what he is used to. I have no interest in starting a grudge match between LWJGL and LibGDX - people can use whichever library they want to. But I do think you should extrapolate that thought out into not badmouthing other libraries purely because they are not your own choice.
Easiest path to use direct openGl with no android spesific hassle is use libgdx but make all openGl es related by yourself. Just use it as windowing , input api and main loop.
Are you going to use it as a backend for MERCury? If you are, that would be really cool! I’ve myself thought of an Android backend, but never on how I would implement it.
If this was directed at me, then I do not know what You mean by “badmouthing”. I did no such thing. As the op was asking a question of “does it work”, with libgdx, there is no such question, because it sure does work, hence the reference of “use libgdx and have less worries”.
Also as the OP did not specify how much code there is already in place, the point about “scrapping and swapping” is moot. In case multi-platform support is desirable then the time spent to learn the library is well spent.
I myself have rewritten my game from java2D -> slick -> libgdx, as such I am well aware of the effort needed and I do not regret doing it.
The question boils down to if the OP wants to make something workable, a product, in which case productivity is the key and libgdx offers more than lwjgl. In case the OP wants to tinker and write stuff, experiment, learn etc., then the question presented in by the OP has less weight since even if lwjgl doesn’t work on andriod, the OP could just make it work (or learn that it’s unfeasible) as a learning exercise as a sort.
I do not see any bad-mouthing lwjgl nor even any negative attitude by me towards the library.
If it wasn’t directed at me, well then… sorry and carry on.
Edit: Also, not really comparing and am well aware of the differences. I was just suggesting something that in my mind might suit better.
Simmer down folks… you can’t compare libgdx and lwjgl. libgdx is built on top of lwjgl.
Cas 
@xsvenson The first paragraph was directed at you - apologies if you took offence (honestly that was not my intention) - I was just expressing that I didn’t feel your statement was relevant in this instance. The second paragraph was a more general statement.