GetMyPOV F Hack 3.1.2 + Redeem Codes
GetMyPOV follower
Developer: Apps Di Pizzocaro S.
Category: Photo & Video
Price: Free
Version: 3.1.2
ID: com.stefano.pizzocaro.GetMyPOV-follower
Screenshots
Description
GetMyPOV is an app for iPhone (the name is for "Get my Point Of View"). The app allows a smartphone to transmit the output of its cameras to another smartphone and allows this second smartphone to control the way the local video capture and forwarding activities take place. The video capture by the device, if desired, feeds a proprietary motion detection algorithm that interrupts the further processing and the forwarding of the frames until the next detected motion event. The video streaming can take place in both the directions, even at the same time.
With version 3, the communication can take place even through the Internet, provided that a public-IP router is available for addressing one of the two sides: a smartphone "A" attending to the Wi-fi network provided by the public-IP router can get and control the output of the cameras of a smartphone "B" connected to the internet in its preferred way, and/or the smartphone "B" can get and control the output of the cameras of "A".
The receiving device can simply view the real-time video streaming coming from the other side (no audio is provided), freeze and/or save specific frames of the scene that is being received and record the video streaming.
The receiving device can "control" the most part of attributes of the remote side: which camera (front/back) to use, whether to use the flash light, which frame-format among those provided by the cameras hardware, the fine tuning of the portion of the video capturing surface used for processing and forwarding (remote zoom), the suspension of the whole camera activity, that occurs, moreover, in a natural way on disconnection. Then, depending on the networking scenario adopted or on the particular app of the GetMyPOV family, also the quality of frames (due to compression), the rate of use in frames forwarding and the activation/deactivation of the motion detection are controllable features.
The receiving side and the emitting side keep track of the frame traffic in which they are involved and present related data at the top of the screen. The receiving side, in addition, is informed about the remote battery charge status.
Recording can be tuned by picking up only a percentage of the received frames so that to slow down the rate of grow of the storage space occupation and can be set to segment files basing on a maximum size specified by the user.
Every frames collection can be viewed at a later time, either frame-by-frame (by tapping) or along its natural capture timing, with the use of an internal viewer that can do zoom actions both on single frame viewing and during video playing (the viewer lets you also pick a frame and save it as jpg file - each frame is identified by a native progressive number).
Secondarily every frames collection can be used to build a final mp4 file, becoming this way sharable with the external world. Also the jpg files coming from possible screen-shots are sharable (a frames collection, as such, can be transferred only to another device running the app too, by means of proprietary get/send commands).
Both remote side of the app and the local one work together to keep (by default) the observed scene always oriented as the human horizon, in order to make the understanding of "what happens" an easy matter, in every situation.
Beyond auto-discovery activity the app supports explicit network addressing that allows keeping track of already listening devices that could have their own camera session ready to be turned on (on demand), and to connect to them one at a time, in order to get and control the output of their cameras.
In version 3 the attitude to be (remotely) controlled by another peer becomes a configurable attribute and is enabled by default.
With version 3, the communication can take place even through the Internet, provided that a public-IP router is available for addressing one of the two sides: a smartphone "A" attending to the Wi-fi network provided by the public-IP router can get and control the output of the cameras of a smartphone "B" connected to the internet in its preferred way, and/or the smartphone "B" can get and control the output of the cameras of "A".
The receiving device can simply view the real-time video streaming coming from the other side (no audio is provided), freeze and/or save specific frames of the scene that is being received and record the video streaming.
The receiving device can "control" the most part of attributes of the remote side: which camera (front/back) to use, whether to use the flash light, which frame-format among those provided by the cameras hardware, the fine tuning of the portion of the video capturing surface used for processing and forwarding (remote zoom), the suspension of the whole camera activity, that occurs, moreover, in a natural way on disconnection. Then, depending on the networking scenario adopted or on the particular app of the GetMyPOV family, also the quality of frames (due to compression), the rate of use in frames forwarding and the activation/deactivation of the motion detection are controllable features.
The receiving side and the emitting side keep track of the frame traffic in which they are involved and present related data at the top of the screen. The receiving side, in addition, is informed about the remote battery charge status.
Recording can be tuned by picking up only a percentage of the received frames so that to slow down the rate of grow of the storage space occupation and can be set to segment files basing on a maximum size specified by the user.
Every frames collection can be viewed at a later time, either frame-by-frame (by tapping) or along its natural capture timing, with the use of an internal viewer that can do zoom actions both on single frame viewing and during video playing (the viewer lets you also pick a frame and save it as jpg file - each frame is identified by a native progressive number).
Secondarily every frames collection can be used to build a final mp4 file, becoming this way sharable with the external world. Also the jpg files coming from possible screen-shots are sharable (a frames collection, as such, can be transferred only to another device running the app too, by means of proprietary get/send commands).
Both remote side of the app and the local one work together to keep (by default) the observed scene always oriented as the human horizon, in order to make the understanding of "what happens" an easy matter, in every situation.
Beyond auto-discovery activity the app supports explicit network addressing that allows keeping track of already listening devices that could have their own camera session ready to be turned on (on demand), and to connect to them one at a time, in order to get and control the output of their cameras.
In version 3 the attitude to be (remotely) controlled by another peer becomes a configurable attribute and is enabled by default.
Version history
3.1.2
2022-07-29
The launch screen has been added.
A code improvement has been applied to make the app supporting forward compatibility in respect of the growth of the communication protocol that will be present in the future versions. This makes the update a recommended update even if the user does not perceive any change in the behavior of the app.
A code improvement has been applied to make the app supporting forward compatibility in respect of the growth of the communication protocol that will be present in the future versions. This makes the update a recommended update even if the user does not perceive any change in the behavior of the app.
3.0.1
2022-05-12
* An added network mode
It allows to deal with explicit network address information and separate the Auto-discovery feature adopted in the preceding versions to make it available as a preliminary job to run before running a session with the new "explicit network addressing" mode. This new mode allows keeping track of possibly already listening devices that typically have its own camera session ready to be turned on (on demand), and to connect to them one at a time, in order to get and control the output of their cameras. This means that even with "F" a surveillance system with many watchers becomes a reasonable usage target. This scenario is supported by two different sub-modes:
** (run) "As known address server that makes the app addressable inside the local network
** "Connect to private/public server" served by a small connections database, fed either manually or automatically during any Auto-discovery activity and along which the user can navigate before connecting as network client.
Being explicitly addressable in the local network means that if this network is sustained by a router that receives the assignment of a public-IP address from the Internet provider, the device running the app can be the target of the port forwarding configuration defined in the router. Then, considering the now-possible use of the data connection, that allows the app to access a public-IP address in the user preferred way, this scenario allows one (or many, one at a time) smartphone running the same app to connect from the "outside" to that one (or those ones) living in the router local network.
* A simpler and explicit way to drive the app to act as network server as result of the negotiation made in the Auto-discovery local network mode
This is provided by a clearer "Forced to be a server" attribute.
* The ability to act as controller
A big enhancement of "F", considering that this main feature was previously an exclusive of the paid GetMyPOV C app, is just that "control" now is possible even with "F" as follows:
Total control of "F"/"C" instances running in the Auto-discovery local network mode
"Almost" total control of "F"/"C" instances running in the direct network address mode, meaning that all features but Frame quality, rate of use in forwarding and activation/deactivation of the motion detection are controllable here.
It allows to deal with explicit network address information and separate the Auto-discovery feature adopted in the preceding versions to make it available as a preliminary job to run before running a session with the new "explicit network addressing" mode. This new mode allows keeping track of possibly already listening devices that typically have its own camera session ready to be turned on (on demand), and to connect to them one at a time, in order to get and control the output of their cameras. This means that even with "F" a surveillance system with many watchers becomes a reasonable usage target. This scenario is supported by two different sub-modes:
** (run) "As known address server that makes the app addressable inside the local network
** "Connect to private/public server" served by a small connections database, fed either manually or automatically during any Auto-discovery activity and along which the user can navigate before connecting as network client.
Being explicitly addressable in the local network means that if this network is sustained by a router that receives the assignment of a public-IP address from the Internet provider, the device running the app can be the target of the port forwarding configuration defined in the router. Then, considering the now-possible use of the data connection, that allows the app to access a public-IP address in the user preferred way, this scenario allows one (or many, one at a time) smartphone running the same app to connect from the "outside" to that one (or those ones) living in the router local network.
* A simpler and explicit way to drive the app to act as network server as result of the negotiation made in the Auto-discovery local network mode
This is provided by a clearer "Forced to be a server" attribute.
* The ability to act as controller
A big enhancement of "F", considering that this main feature was previously an exclusive of the paid GetMyPOV C app, is just that "control" now is possible even with "F" as follows:
Total control of "F"/"C" instances running in the Auto-discovery local network mode
"Almost" total control of "F"/"C" instances running in the direct network address mode, meaning that all features but Frame quality, rate of use in forwarding and activation/deactivation of the motion detection are controllable here.
3.0.0
2022-04-10
* An added network mode
It allows to deal with explicit network address information and separate the Auto-discovery feature adopted in the preceding versions to make it available as a preliminary job to run before running a session with the new "explicit network addressing" mode. This new mode allows keeping track of possibly already listening devices that typically have its own camera session ready to be turned on (on demand), and to connect to them one at a time, in order to get and control the output of their cameras. This means that even with "F" a surveillance system with many watchers becomes a reasonable usage target. This scenario is supported by two different sub-modes:
** (run) "As known address server that makes the app addressable inside the local network
** "Connect to private/public server" served by a small connections database, fed either manually or automatically during any Auto-discovery activity and along which the user can navigate before connecting as network client.
Being explicitly addressable in the local network means that if this network is sustained by a router that receives the assignment of a public-IP address from the Internet provider, the device running the app can be the target of the port forwarding configuration defined in the router. Then, considering the now-possible use of the data connection, that allows the app to access a public-IP address in the user preferred way, this scenario allows one (or many, one at a time) smartphone running the same app to connect from the "outside" to that one (or those ones) living in the router local network.
* A simpler and explicit way to drive the app to act as network server as result of the negotiation made in the Auto-discovery local network mode
This is provided by a clearer "Forced to be a server" attribute.
* The ability to act as controller
A big enhancement of "F", considering that this main feature was previously an exclusive of the paid GetMyPOV C app, is just that "control" now is possible even with "F" as follows:
Total control of "F"/"C" instances running in the Auto-discovery local network mode
"Almost" total control of "F"/"C" instances running in the direct network address mode, meaning that all features but Frame quality, rate of use in forwarding and activation/deactivation of the motion detection are controllable here.
2.0.3
2021-11-05
Main improvements:
* Motion detection
On the side of the camera session, a completely new proprietary processing of the scene is performed for detecting motion, in order to offer processing and forwarding of the frames (of the stream) only in presence of motion. This transforms the app in a concrete application for surveillance purposes because of the energy saving ( so battery life ) that derives for minor image processing, very low network traffic, and on the receiving peer the lower amount of storage used for recording. In the case the camera session is driven by a remote controller that commits the zooming feature, motion detection operates within the restricted area identified by the zoom-in action. This allows to reach a very narrow angle of analysis of the scene to detect motion in. Operating in "motion only" mode, then, is also a remotely controllable attribute (by a controller obviously).
* Suspension
Again on the side of the camera session, if the receiving peer disconnects for some reason, the session suspends itself (camera is stopped and, with it, any image processing). In this state only the network interface remains active but at a very low rate of listening, that one sufficient to resume from "sleeping" when a listening peer (re-)connects. Suspension can even be forced, either locally or remotely (by a controller). In case of forced suspension any connected device has notice of it and reaches a stand-by state that ends upon suspension resuming, once again, locally operated or remotely (by a controller). Once the forced suspension has been removed, the host of the camera session returns to be dependent on the living connections.
* Remote battery status availability
Every asset that implies the reception of video streaming is accompanied by the availability of the battery status of the source. When a repeater device is used, the receiver sees also the battery status of the "man in the middle" is available, in addition to that one of the source.
* The setting of the rate of use of the frames collected from the camera device that are effectively processed and forwarded
With the goal to diminishing the power consumption along the attendees to each GetMyPOV scenario, the rate can be reduced every time it might seem convenient, for example when the performance of the source is "too" high in respect of the needs of the context.
* Frame viewer shows date-time of each frame
The heading data presents the frame date-time, not only when the user goes frame by frame but even during playing. Then the saving of a frame makes the name of the target file be the effective date-time of the frame instead of the date-time expressed by the frames-collection name.
Other improvements
* Graphic user interface has been reorganized and restyled to make easier and more immediate the identification of the commands:
source device have been moved respectively in the title and in the body of the "remote device" section
Textual representation of commands has been replaced by a graphical one where it seemed convenient.
Remote device section is now equipped with the flash light status of the source.
* The verbosity of the first monitor line, during all transients, has been improved in order to follow all of the various status changes.
* Scene hiding.
Whenever the drawing of the receiving scene made some trouble in reading the monitor lines content or in locating some commands in the main panel, due to the inherent transparency, it can be stopped.
* Recording management has been improved with useful features.
* The communication protocol, a part from carrying the added features, has been re-engineered to reach a more efficient bidirectional streaming and to have more robust discovering/connection activities.
* Motion detection
On the side of the camera session, a completely new proprietary processing of the scene is performed for detecting motion, in order to offer processing and forwarding of the frames (of the stream) only in presence of motion. This transforms the app in a concrete application for surveillance purposes because of the energy saving ( so battery life ) that derives for minor image processing, very low network traffic, and on the receiving peer the lower amount of storage used for recording. In the case the camera session is driven by a remote controller that commits the zooming feature, motion detection operates within the restricted area identified by the zoom-in action. This allows to reach a very narrow angle of analysis of the scene to detect motion in. Operating in "motion only" mode, then, is also a remotely controllable attribute (by a controller obviously).
* Suspension
Again on the side of the camera session, if the receiving peer disconnects for some reason, the session suspends itself (camera is stopped and, with it, any image processing). In this state only the network interface remains active but at a very low rate of listening, that one sufficient to resume from "sleeping" when a listening peer (re-)connects. Suspension can even be forced, either locally or remotely (by a controller). In case of forced suspension any connected device has notice of it and reaches a stand-by state that ends upon suspension resuming, once again, locally operated or remotely (by a controller). Once the forced suspension has been removed, the host of the camera session returns to be dependent on the living connections.
* Remote battery status availability
Every asset that implies the reception of video streaming is accompanied by the availability of the battery status of the source. When a repeater device is used, the receiver sees also the battery status of the "man in the middle" is available, in addition to that one of the source.
* The setting of the rate of use of the frames collected from the camera device that are effectively processed and forwarded
With the goal to diminishing the power consumption along the attendees to each GetMyPOV scenario, the rate can be reduced every time it might seem convenient, for example when the performance of the source is "too" high in respect of the needs of the context.
* Frame viewer shows date-time of each frame
The heading data presents the frame date-time, not only when the user goes frame by frame but even during playing. Then the saving of a frame makes the name of the target file be the effective date-time of the frame instead of the date-time expressed by the frames-collection name.
Other improvements
* Graphic user interface has been reorganized and restyled to make easier and more immediate the identification of the commands:
source device have been moved respectively in the title and in the body of the "remote device" section
Textual representation of commands has been replaced by a graphical one where it seemed convenient.
Remote device section is now equipped with the flash light status of the source.
* The verbosity of the first monitor line, during all transients, has been improved in order to follow all of the various status changes.
* Scene hiding.
Whenever the drawing of the receiving scene made some trouble in reading the monitor lines content or in locating some commands in the main panel, due to the inherent transparency, it can be stopped.
* Recording management has been improved with useful features.
* The communication protocol, a part from carrying the added features, has been re-engineered to reach a more efficient bidirectional streaming and to have more robust discovering/connection activities.
1.2.0
2021-04-03
Now The frame viewer, in addition to the natural velocity in playing the sequence, provides new added velocities (x 2, x 4, x 1/2, x 1/4)
1.1.0
2021-03-05
New features:
- Verbosity of the monitor line during the connection process
Improvements:
- No need to restart the H instance (in broadcast modes) upon rejection of wrongly set video session (it is enough to turn it off)
bug fixes:
- streaming with large and heavy frames issues
- crash happening on "start" after a "get file" command made without net available
- Verbosity of the monitor line during the connection process
Improvements:
- No need to restart the H instance (in broadcast modes) upon rejection of wrongly set video session (it is enough to turn it off)
bug fixes:
- streaming with large and heavy frames issues
- crash happening on "start" after a "get file" command made without net available
1.0.8
2021-02-05
Ways to hack GetMyPOV F
- Redeem codes (Get the Redeem codes)
Download hacked APK
Download GetMyPOV F MOD APK
Request a Hack
