Database Info

Multi channel recording studio...

Hey... I found a really cool recording studio app called Meteor
I installed the demo cab and it works like a charm (you just can't save your work on the demo version).
I'm amazed what our little phones are capable of doing. By the way... this is the first application I've seen where pinch to zoom is a real necessity. In fact... I always have it maximum zoomed and this way it's almost like a virtual desktop. (difficult to explain but I hope you know what I mean)
Brgds... /TubGirl

Thanks. Is it similar to Aurora ?: http://www.4pockets.com/product_info.php?p=125
{
"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"
}

arturobandini said:
Thanks. Is it similar to Aurora ?: http://www.4pockets.com/product_info.php?p=125
Click to expand...
Click to collapse
looks a quality program this!! you could lose days playing round with this, weeks even!!!! lol

****! I wish I'd never read this thread, that Aurora is addictive. I've just order a stylus

arturobandini said:
Thanks. Is it similar to Aurora ?: http://www.4pockets.com/product_info.php?p=125
Click to expand...
Click to collapse
Not quite... Meteor is a multi-track recording studio that lets you record audio (guitar & voice for example) and process it in many ways. I'm amazed that it really works! But as I said... you need to enable pinch to zoom because the buttons are incredibly tiny!
http://www.4pockets.com/scrshots.php?p=82&par=82

mickfarr said:
****! I wish I'd never read this thread, that Aurora is addictive. I've just order a stylus
Click to expand...
Click to collapse
oops!! lol there goes your weekends and any other free time you get! lmao.

Excellent! This will come in well handy!
Anyone know of a HD2 compatible version or something similar of this (see attached) ?
Would be really handy for doing rough mixes of my acoustic stuff!

Some nice apps on there. I just bought Chord Explorer, installed it ok but it will not start :-(. Tried re-installing on the phone memory, but still no good.
Anyone else had any problems?

Hexjibber said:
Excellent! This will come in well handy!
Anyone know of a HD2 compatible version or something similar of this (see attached) ?
Would be really handy for doing rough mixes of my acoustic stuff!
Click to expand...
Click to collapse
Haha.. .that looks very cool, but I don't think the HD2 has a stereo input... or does it?

Tubgirl said:
Haha.. .that looks very cool, but I don't think the HD2 has a stereo input... or does it?
Click to expand...
Click to collapse
I guess it would have to connect through the micro USB somehow, there's plenty of USB 2.0 mics around but I doubt they'd be compatible via a micro USB/USB 2.0 adapter?
To be fair though the sound quality of the phone mic isn't that bad for low level stuff, I'm amazed at what this phone can do!!
Thanks again for the heads up about MeTeor, excellent find!

Damn, love that Meteor-program!!! Allright, took some definite tweaking before it worked well enough to be functional on the hd2.
But now i've got a working 12 track harddisk recording system in cd-quality in my pocket....for only 30 bucks??!!!
I LOVE my HD2!!!!!
Thanx a million Tubgirl

I think the USB-Mic won't work...problem starts with drivers and ends up with 5V power-supply....

Well, the power-supply could be solved with internal batteries in the mic itself, or just using a dynamic microphone (needs no power to operate)....but drivers are probably the biggest issue...don't even know if one can even write driver software to WinMo, just like it's done to Vista etc.... ??

RasT666 said:
Damn, love that Meteor-program!!! Allright, took some definite tweaking before it worked well enough to be functional on the hd2.
But now i've got a working 12 track harddisk recording system in cd-quality in my pocket....for only 30 bucks??!!!
I LOVE my HD2!!!!!
Thanx a million Tubgirl
Click to expand...
Click to collapse
Yes it's incredible that it really works.
Do you want to share what tweaking you have done?
Brgds... /TubGirl

Well shure, I am afraid its a bit complicated. I'll try and see if I can describe it in a way that makes sense .
The first problem one might experience, at least i did on mine (using official htc 1.66 rom), is crackles, pops and dropouts in your recordings. This can be corrected with some adjustments to audiobuffersettings and the cachesize set by Meteor for your sd-card.
1. You need to find the "PREFS.xml"-file, in the Meteor directory. For me it would be here: My Phone\Memorycard\programs\Meteor\
2. You will need a browser that can open and edit XML-files, I used Adobe Dreamweaver.
3. Open the PREFS.xml and adjust the following:
AudioBufferSize="2048" -> AudioBufferSize="4096"
AudioBufferCount="32" -> AudioBufferCount="64"
ReadCacheSize="32768" -> ReadCacheSize="131072"
WriteCacheSize="65536" -> WriteCacheSize="262144"
These are maximum settings, and all in coherrence with what the manual suggests for troubleshooting by the way: View attachment Meteor_manual.zip
THE SECOND PROBLEM with the HD 2 as a multitrack harddisc recorder, as with any DAW-system, is mainly the question of latency.
(for info on DAW, check this: en.wikipedia.org/wiki/Digital_audio_workstation)
Latency refers to how long the system (meaning processor, RAM, disc etc) is to actually process the sound converted (ADC), recorded, replayed & deconverted (DAC) again.
For the DAW to work properly (avoiding sync-issues between different recordings), it most know its own latency - hence the calibrating/strange beeps when running Meteor the first time.
Only thing is, that even though HD 2 is fast, it appears to have either a slow soundcard/ADC-DAC-converter or pourly written driversoftware to support it. Either way, at least on my phone, Meteor simply cannot deliver ENOUGH LATENCY, to compensate sync-issues, especially not with the above buffer and cachesettings set to maximum, not even with "Synchronize Audio Threads" under <setup> ticked (Which should be done by the way!).
There is a workaround though, but it requires you to know with what BPM (120 bpm being default) you are running during your current recording session and what latency will fit the current bpm you are running with.
The point is that you SIMPLY ADJUST the recording BACK according to your starting point of recording.
EXAMPLE:
You plan to record on track one at 120 bpm, so you set the cursor at the 1-figure at the ruler in the upperbar. you then set your latency under "setup\audio setup" to "940 ms".
Press record. When finished recording you highlight the recording and simply drag it 1-line back (NOT 1-bar, but 1/4 of a bar).
Repeat this for next recording on track 2 or any other, still keeping the 1-ruler as starting point, and you should have two recordings in perfect sync!
This should of course be repeated for every new recording...always dragging it 1-line back to keep sync.
You can test this yourself by the way, by turning on the metronome letting it play thru the HD 2's speakers, simultanously recording it. Drag the recording back, and when playedback, still with the metronome on, you should hear the recording and the metronome playing synchronized. If it is NOT in sync, you need to adjust latency, untill it is, testing with the metronome as above.
120 bpm = 940 ms latency works on my system, but I have no idea if it will work as a standard on all hd 2 phones. Problem is also, that when changing the bpm, you will also have to adjust latency. But assuming that there is some consistency thru this on most HD 2 (though rom and tweaks probably have a huge influence on this), i have here made a list of these values with what bpm = latency: View attachment Latency.zip
Quite complex instructions, hope this will help though. Welcome to ask for clarification, and I'll see if can answer accordingly
Have fun!

[PORT] Doom 3 Android

{
"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"
}
Great news they have it running on Android. check it out for yourself!!
Edit (27/8/2013) - It now available to download latest version (Release) on Google Play
https://play.google.com/store/apps/details?id=com.n0n3m4.DIII4A
Made by the developer of Return To Castle Wolfestien and QIII4A (Quake 3 port). I have attached a few version's below as not on market yet and hard to download from where it is hosted for free (4PDA), if need any info or bits to make it work please visit this original thread (Link below). Thanks!!
ORIGINAL DOOM3 RUSSIAN FORUM THREAD
Frequent radio transmissions through the player's communications device also add to the atmosphere, by broadcasting certain sounds and messages from non-player characters meant to unsettle the player. Early in the game, during and directly after the event that plunges the base into chaos, the player often hears the sounds of fighting, screaming and dying through their radio transmitter. The ambient sound is extended to the base itself through such things as hissing pipes, footsteps, and occasional jarringly loud noises from machinery or other sources. Often ambient sounds can be heard that resemble deep breathing, unexplained voices and demonic taunting from the game's antagonists.
Click to expand...
Click to collapse
Demo on a Note2 -
Instructions (Old version please see top of page for Google Store version)
Install​
Download version and unzip
Install Apk
Create a folder on your SD cards (diii4a) with a folder named (base) inside that.
Move your Doom 3 pak files (and any other files in your PC's base folder) inside (diii4a>base)
Move folder (gl2progs) contained in this zip to (diii4a>base)
Start the game and have fun!!
NOTE - If RC1 or RC2 don't work for you try the AIC build as that mite. You will also need the PC Doom3 game files to be updated to the newest version 1.3.1 ​Effect Settings​In the command line entry on application main page, add these lines on to (game.arm) for less/more lighting effects!! (SCREENSHOTS OFF/ON CLICK HERE)
Full Light Effects = game.arm+set r_nolight 0
No Light Effects = game.arm+set r_nolight 1
NOTE - Having this set on full will impact FPS and you will need a powerfull device for it to work ok on.
​

I want to try this but I don't have all of the PAK files. I'll see if I can run the Shareware version.
EDIT: I guess I need all of the PAK files, I only have demo00.pak as I don't own the PC Version. Maybe I did something wrong too though since it crashes right after opening, maybe others can help.

I have the game tucked away somewhere (never could get it to run worth a damn on any newer Windows OS) but will it actually run at a decent speed on our Plays?

BrianChase said:
I have the game tucked away somewhere (never could get it to run worth a damn on any newer Windows OS) but will it actually run at a decent speed on our Play's?
Click to expand...
Click to collapse
I assume after a good number of optimizations, yes it should. I'm not making this though. I can't try it because I don't own the game.

Wow that is cool! How does it run?
Sent from my R800i using xda app-developers app

Yeah... How much FPS you are actualy getting from that thing ?
I would do fine with steady 20fps :I
But this is so cool, I remember how amazing it felt to know that in 2007 a Nokia N95 could run Quake 3"@ 20-30 fps! And my pitty N81 could still run QUAKE and Quake 2 regardless the lack of 3D accelration.
Now we are getting DOOM3 for android phones. Hooefully they can port other games running IDtech 4 in the future too (quake 4, Quake wars)

I mean, the Quake 3 port (id3) never ran that well on the Play and the id4 engine is quite a large improvement. I wouldn't imagine it gets more than a solid 10fps but I'd love to hear otherwise!

BrianChase said:
I mean, the Quake 3 port (id3) never ran that well on the Play and the id4 engine is quite a large improvement. I wouldn't imagine it gets more than a solid 10fps but I'd love to hear otherwise!
Click to expand...
Click to collapse
But as far as I know, Kwaak3/Zeus Arena doesnt have 3D accelration (doesnt take advantage of the GPU). If this DOOM 3 port does, we can expect better performance/GFX ratio.

Hmm I sure hope the dev comes back to this.....the last rime anything was modified was 9/11
Sent from my R800x using xda app-developers app

Thewonderboy said:
But as far as I know, Kwaak3/Zeus Arena doesnt have 3D accelration (doesnt take advantage of the GPU). If this DOOM 3 port does, we can expect better performance/GFX ratio.
Click to expand...
Click to collapse
You may be right since I'm not 100% sure but if I recall correctly Kawaak3 was ported to Windows Mobile and saw much better performance on the Omnia devices since they were the first to my recollection to use dedicated GPU's capable of OpenGL. I believe that would mean Kawaak3 is 3d accelerated but since my memory that far back is a bit fuzzy and I can't find any reliable information online I'd love to hear some second opinions since this could make all the difference in the world if you are right.

BrianChase said:
You may be right since I'm not 100% sure but if I recall correctly Kawaak3 was ported to Windows Mobile and saw much better performance on the Omnia devices since they were the first to my recollection to use dedicated GPU's capable of OpenGL. I believe that would mean Kawaak3 is 3d accelerated but since my memory that far back is a bit fuzzy and I can't find any reliable information online I'd love to hear some second opinions since this could make all the difference in the world if you are right.
Click to expand...
Click to collapse
Well, to be more precise. GPU is being used but only in a way Q3 originaly utilized GPU's.
meaning that like many old PC games, unmodified IDtech 3 and Quake 3 are very CPU heavy.
Newer IDtech 3 enhanchments put alot of workload to GPU to reduce any bottlenecks. Asuming that Kwaak3/Zeus arena is just a direct HW port it shouldnt have any GPU stressing features.
IDtech4 already has these features there by default so basic porting and optimization should involve full support for GPU
To give some kind of insight to the difference between stock IDtech3 and modified version that uses GPU heavily: 200%-600% performance increase on PC's (2007 and up) is guarantide !
On Xplay I would expect atleast 50%-100% increase if one would enhance that Q3 port.
Im not an expert by any means, just sayan what I have heard and seen.

Sorry for the off- topic noob question but gives gpu- rendering better game performance?

Ahhh thanks for the info Wonderboy, makes perfect sense and I hadn't even considered it.

cyraxx84 said:
Sorry for the off- topic noob question but gives gpu- rendering better game performance?
Click to expand...
Click to collapse
Ofcourse, GPU's are being used for GFX rendering so heavily because they are more efficient in it than CPU's. This bases on their difference in structure and dedication.
-------------------------
Spoiler
CPU is one unit with one or multiple high clockspeed processors. GPU however has one "core" that is relativly slow (clockspeed wise) but it has also alot of "minions" which can share the workload better. Their structure is more appropriate for fast rendering since thats what they were desinged to do.
GPU core can concentrate to GFX rendering with its other essential workers which can do multiple rendering things at once while CPU can throw orders and make sure the game is running properly and everythings behaving like they should.
There is various other stuff in PC world that can ease these tasks, like tessalation unit. If GPU has tessalation unit it basicly enables developer to use low-poly models and then tessalate them to look maybe even better than hand crafted high-poly models. Since tess unit is only being used for tessalation (and displacement mapping I think ?) you should experience performance BOOST since now GPU has to deal with lower poly models while tess unit makes sure those models look better
Xperia Play has only CPU and GPU, nothing super fancy. Only thing I think is noteworthy about Xplay's hardware is the dedicated videomemory. This allows developers to leave more room in RAM department and put most of the models and textures into this dedicated memory.
And anybody who knows this stuff better is free to correct.
--------------------
I made a small test to try if kwaak3/zeus arena is CPU or GPU heavy, it was pretty simple.
I launched Zeus arena and a mod called "Hunt" where you fight againts multiple AI enemys. Their AI is enchanced compared to stock Quake 3.
I was having 40-60 FPS during start up and when going againts ONE enemy my FPS dipped to 4-22, After 3 more enemies appeared and I was shooting them with a chaingun my FPS literaly went to diashow and caused the game to crash
AI calculations are being made by CPU and the FPS drop was so extreme that I doubt GPU had anything going on for the game.
Lets just wait and see, I bet you that DOOM3 port will run decently, after all, integrating multithreading (dual, tripple and quad core) support into any Quake engine is really time consuming and not really worth it so developer has to concentrate into other ways to increase performance
Okay, I will shut up now

Blahhh, I guess I'm going to have to test it when I get a day off. Its a bit of a pain in the ass since I have to clear a good amount of my full SD space but its a pain in the ass in the name of science!

not sure if anybody else has this problem, but http://dante.mobi/ is nolonger reachable for me.

stevvie said:
not sure if anybody else has this problem, but http://dante.mobi/ is nolonger reachable for me.
Click to expand...
Click to collapse
yeah , same with me . i want to try it . it looks cool .

kurosaki99 said:
yeah , same with me . i want to try it . it looks cool .
Click to expand...
Click to collapse
try download it from this page.
http://www.htcmania.com/showthread.php?t=483097
SD data, download from turbobit as others call premium account links. regards

If Doom 3 actually works on the Xperia PLAY I am gonna piss my pants

does not work on my Acer A700.
I'm getting an error:
Missing data files. Looking for one of:
/storage/sdcard0/external_sd/doom3/base/pak000.pk4
...
...
I tried copying my base folder of the full version so my external SD in doom3 or internal sd or even in /sdcard/external_sd/doom3
nothing works.

[GUIDE] Getting the max FPS (60) in PUBG Mobile without root from newbie to newbies

DISCLAIMER: This is not professional thread. This is just a simple guide to increase FPS from a newbie to newbies like me.
I really love playing PUBG. I have seen many people discussing the performance of PUBG Mobile for our lovely Mi A1 and I wanted to share with you few non-root methods to improve your performance in PUBG Mobile. I have been testing and experimenting with it and I have made a REALLY SIMPLE and EASY list with my recommendations which can really give you about 50-60 FPS, none of these methods require root, custom ROMs or kernels:
1) Download GFXTool app from Google Play
This app allows you to completly edit graphics settings for PUBG Mobile. You can change resolution, graphics, AA and even shadows and more. First pick your server and then edit those settings. Just skip all the ads.
For the best result set this:
Resolution: 960x540
Graphics: So Smooth
FPS: 60 FPS
Disable shadows and let the style be Classic
{
"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"
}
NOTE: If you want some playble graphics, set Anti-aliasing to ENABLE to reduce the "pixelness" - it may cost you a few FPS
2) Overheating slows the device
It is enormously hot outside, especially now in summer. And so hot is your phone when you play PUBG. I recommend to take a break for your phone after every longer game. I have noticed small performance decreases after playing longer game, that's because it is really hot outside and our phone doesn't cool enough. Overheating decreases your phone's lifespan and performance. Just don't play while charging the battery. A smaller thing is to correctly hold the phone with your hands while playing, because if you don't give a colder air for your phone, it can't cool down. It is recommended to put off your mobile phone case while playing to let the phone cool down.
3) Overlay windows and bubbles
Don't use any chatting or notification bubbles on your screen while playing. The most famous one is Facebook Messenger, pop-ups decreases your performace a lot.
4) DND
DND means Do Not Disturb. You may laugh, but this can highly improve your performance in PUBG. Notifications jumping on your screen like Messenger really lags the game. By setting the DND your apps won't disturb you while playing, but the thing is, that you have no sound. Let's hope that in future updates will Xiaomi let us use sound from media while DND.
5) Don't play with low battery
My Mi A1 shuts down 4 cores of my CPU while it is somewhere under 25% of battery percentage. This can highly slow down your phone while playing PUBG.
6) Other smaller tweaks
Turn of microphone and voice in the game
Don't use any security software which can run in the background
Close your recent apps which may run in the background
Reboot your phone before playing
Disable automatic updates on Google Play to reduce the updating of your apps while playing the game
That's all from me. Feel free to criticise me or even correcting me. These were the simpliest methods to keep your game running at 60 FPS without any modifications or root.
Happy WINNER WINNER CHICKEN DINNER!

I thought the 4 cores thingy triggered at 10% ? Or did they change that in newer versions ?

Can someone plz make Tweeks for asphalt 9 graphics as well , it looks grains and not smooth. Thnx in advance .

gougous3 said:
I thought the 4 cores thingy triggered at 10% ? Or did they change that in newer versions ?
Click to expand...
Click to collapse
I remember it triggered already at 25%, but who knows how it works... maybe in current version of Android it triggers lately.
Sent from my Mi A1 using XDA Labs

Just wow, amazing ?

arjiyunandar said:
Just wow, amazing
Click to expand...
Click to collapse
Graphics look horrible but FPS go up my friend, up to 60 without any problem

Few things:
Pubg removed frame rate access on 0.7 will return in 0.8
Source: official gfx tool changelog and in-app faq.
For our device fps is maxed at 30-40 fps. Why? read above text
Four cores shutting down happens when andriod battery saver mode is activated which can be set to 5% or 15%. not 25%.
Note: fps thing might wring. Welcome corrections based on screenshot using a fps meter.

alkesh95 said:
Few things:
Pubg removed frame rate access on 0.7 will return in 0.8
Source: official gfx tool changelog and in-app faq.
For our device fps is maxed at 30-40 fps. Why? read above text
Four cores shutting down happens when andriod battery saver mode is activated which can be set to 5% or 15%. not 25%.
Note: fps thing might wring. Welcome corrections based on screenshot using a fps meter.
Click to expand...
Click to collapse
I dont know how to do that, but I definitely have 60 fps. And no, even if battery saver is off, 4 cores still shut down - I've tried this.

TrueMS said:
I dont know how to do that, but I definitely have 60 fps. And no, even if battery saver is off, 4 cores still shut down - I've tried this.
Click to expand...
Click to collapse
Just curious how can you say you definitely know it's 60 fps.
When there was option available fps was in 40-60 range and try proning or going through smoke fps goes 18-30.
4 cores won't automatically shutdown until Android system tells cpu to do so and that happens to save battery.
First measure fps and see. There's an app called gamebench it requires pc.
And show screenshot for fps and cpu offline.
PS: this is an educational argument.

alkesh95 said:
Just curious how can you say you definitely know it's 60 fps.
When there was option available fps was in 40-60 range and try proning or going through smoke fps goes 18-30.
4 cores won't automatically shutdown until Android system tells cpu to do so and that happens to save battery.
First measure fps and see. There's an app called gamebench it requires pc.
And show screenshot for fps and cpu offline.
PS: this is an educational argument.
Click to expand...
Click to collapse
Thanks for educating, but none of this is new for me. I don't have currently PC available for few weeks. Then I would record the FPS for this thread. This thread doesnt say that it gives all time 60 fps, everything throttles and is not stable 60, it is guide to reach, again reach 50-60 FPS, not to play on 60 stable. I know how 60 FPS look like and I can say, that it is really close to it, sometimes it is 60.
Of course Android system tells the CPU to turn it off, I dont know where is the problem.
And come on, this thread is "from newbie to newbie".
Sent from my Mi A1 using XDA Labs

TrueMS said:
Thanks for educating, but none of this is new for me. I don't have currently PC available for few weeks. Then I would record the FPS for this thread. This thread doesnt say that it gives all time 60 fps, everything throttles and is not stable 60, it is guide to reach, again reach 50-60 FPS, not to play on 60 stable. I know how 60 FPS look like and I can say, that it is really close to it, sometimes it is 60.
Of course Android system tells the CPU to turn it off, I dont know where is the problem.
And come on, this thread is "from newbie to newbie".
Click to expand...
Click to collapse
Okay just bear with me.
In pubg we have frame rate settings like this:
Low - 15 fps (guess)
Medium - 20 fps (guess)
High - 30 fps (fact)
Ultra - 40 fps (fact)
Extreme - 60 fps (fact)
Fps shown here are the maximum allowed by game when those settings are chosen.
This means that when you set fps at High your game will not cross 30 fps.
Now do you see ultra and extreme options in 0.7?
If yes. Is extreme selected?
If yes. Then congratulations you can play pubgmobile at 60fps and thats awesome.
If No to any of those two questions then you cannot play at 60fps in 0.7.
And i have never said that you are talking about constant 60 fps.
This post isn't to challenge your experience as i don't whether you are new or old to this. I am just pointing out some inaccuracies.
Thanks.

Fps60

this is the settings that works very smooth for me
here's the screenshot
https://ibb.co/BgX9Kj6
https://ibb.co/QKXNkYN

VR headset?

Hi!
I was wondering if vr headset would have a good quality with this phone, and which ones are compatible?
If you have one or know one that could fit my poco f2 pro, please share your references below

Well,
As nobody has replied yet, I ordered a very cheap VR Headset. The phones seems to fit in there, I'll tell you more when I get it.
The headset can be found around 10€ instead of 60€ on amazon (I'm french ) and has good reviews. It's the Freefly VR beyond, and I know it looks kinda... weird.
{
"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"
}
EDIT: Please do not buy this one! I know it is cheap, and I managed to use it for a few hours, but the optics can't be adjusted so... You'll never have a proper image with it if you haven't the perfect IPD, and your eyes won't be able to properly focus...

I ordered an other model since last time which is this from the company Shinecon (re-branded as Hamswan) The optics seems very good (no Fresnel lenses), and you can adjust easily the IPD (interpupillary distance) and independent focus for each eye.
The only thing not practical on the one I chose is that there is no button to touch the screen and select things. Also the headset nose emplacement is a little weird and can hurt a little if you haven't a small nose. But overall the optics seems good and I think you could buy from this company, just you should choose another model with a button.
Here are some pictures from the one I got :
And the weird nose emplacement ^^' :
By the way you can place very big phones in this headset.
So I think you can choose a more recent option from Shinecon (or rebranded Shinecon) WITH A BUTTON and maybe a different kind of lenses adjustments as they are kinda sensitive (and also a better shaped nose ^^')

Quality effort, quality content.
Well done mate!

how do you use this and with what? It's possible to use it as an oculus to cast the screen of the pc?

Did someone figured out how to deal with VR on that phone?
I'm generally not using the VR for gaming, but for playing 180/360 degree videos (usually in SBS format). For few years I was using the ZTE Nubia Z7 Max with VR Box 2.0 goggles and AAA VR Cinema app for that with just the perfect result. The effect was always stunning, everything looks pretty close to the real with a nice 3D effect of the items (in some apps the image looks more flat, where that effect is not visible, but with that app mentioned above the result was very nice), especially if the video file resolution is good enough. Unfortunately, the Nubia had problem with playing videos in vr in 4k resolution and higher. Doing some experiments I've figured out, that the resolution 3684x1842 (which I'm calling 3,7K ) in H264 is max to provide a stable playback in 60 fps. The Nubia unfortunately has too weak components for something more. But anyway, the image quality is very good in that configuration.
Moving on to the POCO F2 Pro, I've decided for phone upgrade in recent days and was hoping for an absolutely stunning effect with the Super AMOLED screen. Unfortunately, the result is a nightmare as for now. The POCO fits quite well in the VR Box 2.0 Goggles, but that's the only one good aspect. Unfortunately, on the MIUI12 the AAA VR Cinema app have a problem with opening in the not-fullscreen mode. It could work only in a fullscreen mode, but everything is then stretched and the big part of the image is cut out! It's impossible to adjust the goggles with that image - you could only get a squint from that. I've tried a big bunch of the free apps for VR available on the play store and most of them simply doesn't work on POCO (can't read files, generate improper image for which is impossible to adjust the goggles or are simply a joke). The most promising is VRTV Free, but it's quite hard to adjust it, and the 3D effect is not quite visible as was in the AAA VR Cinema app on Nubia - everything looks more flat than 3D. I was also hoping for a stunning image quality on the Super AMOLED screen and you know what? On POCO, when you put out it into VR goggles there are noticeable, quite visible black gaps (a black holes, hehe) between the pixels, so in my opinion the image quality is a wayy much better on the Nubia despite its the IPS! Probably on the Nubia Z7 (NX506J), which had the 1440x2560 screen resolution it would be even better. About the POCO, I'm disappointed about the image quality of that Super AMOLED in VR. In normal it looks better on POCO than in the Nubia, but in the VR for me the Nubia clearly wins - it only has a little too weak CPU&GPU.
So what to do about that now? The VR is very important for me. Do you know the apps (could be the paid) for VR which are working good in POCO? And the same for the Googles? Cuz maybe the VR Box 2.0 Goggles are the problem too, because despite the fact that the POCO fits for them well physically, they are designed for phones from 3,5"-6" according to the specs.
EDIT:
Yeah, it looks like I've figured out some solution! Don't know why I haven't thought about that before, but I just came up with the idea of trying some earlier versions of the AAA VR Cinema. And yeah, on the 1.5.3 version I'm able to start the app in a non-fullscreen mode Buttons & etc. aren't stretched and the whole image fits the screen. And the image quality in the VR Box 2.0 (exactly it's an Esperanza model) is very nice! Maybe even better than on Nubia, because now the gaps between the pixels are hardly visible and are comparable to that on Nubia. But the performance gain is flawless and now I finally can play HEVC videos (had to use AVC before on Nubia). For me the AAA VR Cinema app is the best one out of the free apps (haven't tested the paid solutions - does someone know any worth trying?) - it has that stunning 3D effect due of what everything looks pretty realistic, which any other app doesn't have. That version of the app also in the fullscreen mode have the proper screen size, so it's not cut off and perfectly fits the screen, but in the fullscreen I have problems with adjusting the googles (maybe here other goggles will help). As for now I'm satisfied of using that setup on a non-fullscreen mode. And there's an additional problem on the POCO - the image is shifted to the one side of the screen:
so you can't properly place the phone inside the VR Box 2.0 goggles with the center line matching the notch, because there are not enough space in the tray to move the phone to the side. It's causing that the view is shifted a little and you can feel like you're not exactly in the center of the action. But the image is looking properly anyway. I've found that its caused by the system navigation buttons (because of some space reserved for them at the side of the screen). After changing the steering in the system options from buttons to the fullscreen gestures everything is allright!
There is also the option to cut a little piece of the plastic of the tray on the side, so the phone could be moved a lil more to the side. Or use other googles. In the meantime I've tested the googles from shinecon (the Box 5 mini model) which doesn't have that problem because they don't have the tray and they have the optics more comfortable to setup (but also not fully independent), end the lenses are probably better than on VR Box 2.0 so the image is more bright (at that's maybe to the plastic color which is white here?), but personally I prefer the lenses from the VR Box 2.0. They have a little blurry image (just a little) so the pixels shape isn't that noticeable. On shinecon I think everything is more sharp. I would say it's like a kind of antialiasing in the VR Box 2.0 So I prefer them, because they also are av little bigger, have the skin-like binding around the contract area (on shinecon it's just a sponge...) And the tray is much more easier to use. But they have worse ventilation s due to that, on the Nubia I've sometimes was thinking that the phone will explode due to the heat. But the POCO isn't overheating so it's not a problem.
But there one more little problem I've noticed on POCO - even on the latest version of the app - it has the tendency to crash the app on start after one use, do you can't stay it. The solution for that is to go into the information about the app and enable and right after disable the fullscreen mode for it, and when you start the app hold the phone vertically, not horizontally, after the successful start you can change to the landscape. So there are a little problems but finally everything is able to figure out, with some additional "ritual" to do but it works. I hope that maybe that informations would be helpful for someone
I will also willingly test any other solutions, if someone would come with them. Also it would be nice to know your propositions about the apps to use (free or paid), but as for now the AAA VR Cinema is for me just the best and probably only one which could generate the proper, stunning like realistic image (the effect is like on the YouTube or even better). It has some disadvantages (like no timeline of the video so you can forward or rewind with some limitations, and the control buttons aren't hiding but can only be always visible or always off, but that are the things capable to living with them, and for the image quality I could forgive that.

For me, its not worth it. Im using zeiss vr one (glass optic) but the pixel are very visible. Movie are ok i guess but not games.

It's because of the physical pixel density of the screen, probably. The screen diameter is large and the native resoluition is still only FHD+. Probably, with the higher resolution it would be better. That's probably why the overal impression for me was better on Nubia than on the POCO (almost same resolution, but smaller screen). I rather do not play games, but for the movies I've also bought the Fiit VR 2N goggles in the meantime and with the correct qr code setting it looks for me noticeably better for the pixel look. Maybe with games it would be better too.
I'm also wondering how it would work with the Baofeng Moijng S1.

@Oswald Boelcke
Shouldn't this be moved as well then?

Question Could have sworn there were HDR settings, what happened to them?

Have had a couple of bright daylight shots come out like garbage, low detail low quality smudged detail. so just happened to look in settings and no HDR/+. Maybe I'm getting it mixed up with my previous pixels but could have sworn there were HDR settings in Google camera on the 6a?

Strange. Reddit says...
Google is even more cryptic.
Raw mode be your next and better option. Those will require post processing which is done using a photo app that has an adjustable contrast curve option.

Thanks! Raw wouldn't have helped this shot. looks like needed the stacking that HDR provides. making sure I'm not crazy, the option was there before, no? It's definitely still kicking in in some cases but seems somehow auto / Left up to googles algorithms. Unfortunately that leaves us with a lot of garbage shots

Compared to a Canon pro cam all smartphone cams are a pain to use and limited especially for setup options and speed. I lose a lot of shots because that. I never liked HDR's; a properly exposed shot doesn't need it. Raws give you at least 2 full f-stop exposure and WB correction.
No option to shoot multiple burst exposures at different exposure settings either on smartphones.
Even on my Samsung N10+ the HDR setting when toggled on will decide for you if it will be used. That can and does screw up shots when on... sometimes. No real control
Perhaps Google will update that missing feature soon. Rather sloppy of them. Not near as inept as their lame idea implement forced scoped storage though.
That's a bomb I'm still running Pie and 10 to evade that terror.

The issue is these tiny sensors. The photo stacking/ computational photography helps exponentially. When it doesn't kick in, it can be very bad. You're right RAW can definitely help some but there's only so much it can do. Here's two shots, one when the computational kicked in and the other apparently not. These were taken on the fly (my gf and her kid, not random people), so obviously not great composition just an example of what I mean.
{
"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"
}

Not available for pixel 4a and above. It is default ON.

damian5000 said:
The issue is these tiny sensors. The photo stacking/ computational photography helps exponentially. When it doesn't kick in, it can be very bad. You're right RAW can definitely help some but there's only so much it can do. Here's two shots, one when the computational kicked in and the other apparently not. These were taken on the fly (my gf and her kid, not random people), so obviously not great composition just an example of what I mean.
View attachment 5770083
View attachment 5770085
Click to expand...
Click to collapse
That's not much difference.
On a raw file (or maybe even a jpeg) you could do that and better using an adjustable contrast curve with settable adjustment points. Takes a bit of practice and a color calibrated monitor.

Wow man, the difference is massive. Look again at the detail in all areas. Detail completely smudged out in the faces, the animal, the plants.

damian5000 said:
Wow man, the difference is massive. Look again at the detail in all areas. Detail completely smudged out in the faces, the animal, the plants.
Click to expand...
Click to collapse
Yeah just saw that. Not sure what the cause is though. The face is messed up. I suspect it's the jpeg processing algorithm.

It's also the animal, the plant life to the right can be seen easily. This is what I'm talking about in regards to the photo stacking, what enables these tiny sensors to get decent IQ.
But also, looking at the exif, the bad shot is at 1/7200 ISO 700, that's insanely dim for these little sensors, I'm assuming the digitally brightened. I'm GUESSING I may have been moving (or they were moving) and Google algorithm decides to snap a "sport" shot rather than have something completely unusable? In the case, if so, also no time for stacking in a "sport" shot. Just a guess.
The other 1/400 ISO 45, though I'm not sure how they calculate the latter with stacking/HDR. Whether it's an average of all shots or what.

damian5000 said:
It's also the animal, the plant life to the right can be seen easily. This is what I'm talking about in regards to the photo stacking, what enables these tiny sensors to get decent IQ.
But also, looking at the exif, the bad shot is at 1/7200 ISO 700, that's insanely dim for these little sensors, I'm assuming the digitally brightened. I'm GUESSING I may have been moving (or they were moving) and Google algorithm decides to snap a "sport" shot rather than have something completely unusable? In the case, if so, also no time for stacking in a "sport" shot. Just a guess.
The other 1/400 ISO 45, though I'm not sure how they calculate the latter with stacking/HDR. Whether it's an average of all shots or what.
Click to expand...
Click to collapse
The cam sensor temperature can also increase the noise floor level. With the lense and sensor size as small as they are it's a wonder they can do this good. The narrow depth of focus doesn't help things either.
Cam shake may also play a role as well; the lighter the cam the less stable the shooting platform. Smartphones have no handholds. Not near as easy to shoot with compared to a pro cam and lense that weighs 5 pounds. The larger lens are easier to shoot because of the added weight.
Smartphone cams are convenient but damn I lose a lot of keepers because of them in shutter lag alone.