Related
I'm pretty sure I'm the only person on the planet that actually has a set up like this... if I'm wrong, please post... there is no information out there about this old application.
I have a home surveillance system setup using 2 Q See DVR cards. Q See was nice enough to make a Windows Mobile 2003 application called "Pocket Camera" that connects to the Super DVR software used to record the cameras. You type in your IP and port, username and password and it connects to your home DVR system. Then it gives you a drop down list of the cameras you can view.
The software worked perfectly... until I got a VGA device. It only seems to work on qVGA. I know its a long shot... but does anyone know how to get this to work on a VGA device? The network portion works fine... it connects, authenticates and even gets the list of cameras. The software just has an issue rendering the video since (I think) it is expecting qVGA resolution.
Thanks!
Just wanted to post an update in case anyone is having this issue.
I emailed Qsee tech support and they actually called me back! I was amazed. It turns out that I was right and their old code does not support the new phones that have VGA resolutions. They said they were going to send this to their programmers for feedback. Hopefully they get it fixed, being able to view my cameras on my phone has been FANTASTIC.
If anyone has any idea on how to emulate a qvga screen on a vga device, please share.
I have not had any luck (as you had) with Q-see's tech support. In fact, it took nearly 5 weeks of daily emails and testing before they finally admitted to me that their software would not run on a vga device. Anyway, I installed ie 6.1 (I found a cab here) and it *for whatever reason* runs the pocket camera program.
pete
Since my last update, I've had horrible support from Q-See. They are not the strong customer service group I thought they were. I've had nothing but problems for the last 4 months... but I was just recently able to get this thing working on the vga touch pro 2 AND on windows XP.
I had to update to the newest version of SuperDVR, disable all of the activex protections so you can run their UNSIGNED ACTIVEX control. Why they refuse to sign the activex, I will never understand.
However, the cab that comes with the new SuperDVR actually works in VGA.
Basically, Q-See support sucks, but installing the new superdvr worked.
Did you have to buy the SuperDVR? I cannot find it on their website, or anywhere else for that matter.
scottmail said:
Did you have to buy the SuperDVR? I cannot find it on their website, or anywhere else for that matter.
Click to expand...
Click to collapse
Go to www.q-see.com and click on products
Then pick PC based DVR systems
Then pick your card
Then at the bottom, there is a table that has info in it. One of the column headers is "software".
Here is a direct link, but I don't know how long it will work. They seem to change their software direct links quite often and it keeps breaking my bookmarks.
Super DVR 6.2.2.4
Hello, I'm a newbie and I work as a junior software engineer. Actually I had been testing K700 and W902 phones by attempting to download GIF, AWB, MID, AMR, MP3, SIS, RMF, WAV and 3GP files from the server in the company where I work. Unfortunately I received the message that said 'Downloaded file corrupt. Could not be saved.' on both phones instead. My manager told me that the company's rivals allow their customers to download the files I've just mentioned and they prevent the customers from sending the downloaded contents to anyone else. Therefore I've got to test the Forward Lock that already exists in the company's system. By the way, I am able to download the contents in question on Nokia phone if you ask me. Please take a look at the code below;
PHP:
<?
header("Content-type: application/vnd.oma.drm.message; boundary=boundary-1");
print("--boundary-1\n");
print("Content-type: image/gif\n");
print("Content-Transfer-Encoding: binary\n");
print("\n");
fpassthru(fopen("133000001.gif", "rb"));
print("\n--boundary-1--\n");
?>
People, please help me out by suggesting something for me to add to the code above in PHP file.
Hey i need some help?
hey Every body....!! Any body knows which Sony Ericsson Mobile Phones are best for using office and for home... which have a long bettery time....
Thx in advance...
Why does no one release anything for LG E900 ( eg. full unlock, custom rom)? Is this phone so hard to hack or just no one cares? It was supposed tgo have 1,3 GHz processor – maybe it's jus underclocked? So many interesting issues here and catching no ones attention ;(
You just have to search. Use the old cheveron unlock (you may have to downgrade to do this) and follow these instructions
http://forum.xda-developers.com/showthread.php?t=1271963
LG has a registry editor in 1st gen phones so you can easily interopt unlock it.
@ROCOAFZ: Dev-unlock is just a registry tweak, same as interop-unlock. Do *NOT* downgrade your phone to try and use the original ChevronWP7 Unlocker; it's a total pain to use now and you lose data when downgrading. Just use the registry editor directly!! The thread you linked tells you all the values you need to change.
@paksio: There's tons of homebrew for LG! Registry editors all support it, since it's so easy. Provxml apps also support it, except for FileOperation commands. The current filesystem browsers don't support it (no OEM DLL for filesystem access), but Heathcliff74 has said that his upcoming WP7 Root Tools v0.9 does, and that should be out soon.
As for custom ROMs, if you want to get hacking on the LG bootloader, go right ahead. DFT will probably get to it in time, but like all the rest of us they have other time commitments and personal priorities. Hackers are hobbyists, doing this stuff on our own time. If a hack hasn't been promised, don't expect it or ask where it is. If a date hasn't been promised, don't ask when something will be available or how long it will take. You can't really predict these things even if we were being paid to do this; hacking takes time and experimentation.
For the record, pretty much all hacks for the LG Quantum should work just fine on the Optimus 7.
GoodDayToDie said:
@ROCOAFZ: Dev-unlock is just a registry tweak, same as interop-unlock. Do *NOT* downgrade your phone to try and use the original ChevronWP7 Unlocker; it's a total pain to use now and you lose data when downgrading. Just use the registry editor directly!! The thread you linked tells you all the values you need to change.
@paksio: There's tons of homebrew for LG! Registry editors all support it, since it's so easy. Provxml apps also support it, except for FileOperation commands. The current filesystem browsers don't support it (no OEM DLL for filesystem access), but Heathcliff74 has said that his upcoming WP7 Root Tools v0.9 does, and that should be out soon.
As for custom ROMs, if you want to get hacking on the LG bootloader, go right ahead. DFT will probably get to it in time, but like all the rest of us they have other time commitments and personal priorities. Hackers are hobbyists, doing this stuff on our own time. If a hack hasn't been promised, don't expect it or ask where it is. If a date hasn't been promised, don't ask when something will be available or how long it will take. You can't really predict these things even if we were being paid to do this; hacking takes time and experimentation.
For the record, pretty much all hacks for the LG Quantum should work just fine on the Optimus 7.
Click to expand...
Click to collapse
Thanks for the clarification on the downgrade. I had a surround so i had to do it the hard way as it doesn't have a built in reg editor. I forgot what it actually did.
I am one of the unlucky who've bought a new phone, unaware that android 4.xx contained even major changes compaired to the earlier versions. My phone is a HTC DESIRE 816, bought only because of the 8 gb internal memory and the promise that the phone supported additional 128 GB of memory
This has resulted in many of my programs no longer work because Android now blocks the direct access to the SD card and to the system.
What I find reprehensible is that these phones are sold without the producers inform us about this limitation, and I actually find that we have taking a step backwards concerning user freedom.
Furtermore HTC expresses thet they are 'excited to see what you are capable of. HTC eagerly anticipates your innovations'and also containes a complet guide to how to root your phone.
This, I find is hypocritical as they at the same time refuses to give us S-Off or to edit the platform.xml giving us access to our self paid SD CARD, and at the same time in their AD's makes a big deal about the fact, that we can add 128 GB of additional memory, but doesn't mention that we have no say over it.
A few Of my paid programs that doesn't work anymore:
Navigon, because of the amount of data it require you to DL.
My expensive Firewall / Antitheft.
My GPS tracking App
Nandroid,
Callrecorder
several of my paid Backup programs
many Jrummy App
etc etc.
We have to stand together an demand that the prducers find a solution, and we have to face up to Google, their excuse that it has to do with security don't hold water in court, they must have had other choices, but they chose the easiest and the one which made most trouble for their users.
Maybe instead they could have chosen to have apps that needed the R/W to apply for a signed certificate to get access to this and as the experts Google is to gather information, it wouldn't have been hard to monitor those apps who was awarded with the certificat to control if thet was abusing this.
This is just one solution, but I'm no expert, but guaranteed, there must have been lots of ways to solve and to achieve their goal.
Regards Sc0rpio
Hey,
Germany is implementing EU-Alert (ETSI TS 102 900 [1]) at the moment and referring to the local News, it is a huge mess [2].
But let's start at the beginning.
CellBroadcast is a core component of each mobile network generation (2G,3G,4G,5G,...) and part of the 3GPP spec. CellBroadcast basically allows the network to send a simple SMS to all mobile phones connected to a specific base station. Thes SMS-CB are sent with a Message Identifier (aka Channel, aka Topic) which gives them a special purpose by convention. e.g. ID / Channel 50 is often used for area related information [3], while channel 207 might broadcast local weather information. Since not all Channels are standardized, there is also the option to broadcast an Index that lists all channels with a description. And since users probably don't want any message broadcasted, users have to subscribe to these channels.
Since decades now, CellBroadcast is also used for public Emergency Warnings. This means that, by definition of a country, a specific channel is used to broadcast Emergency Warnings. Long time ago, in many countries it looks like Channel 919 was used for this purpose. For this to work properly, mobile phones were instructed to subscribe to channel 919 by default and also use a special ringtone (even if muted) to alert such a message.
Later - over 12 years ago - additional channels from 4370-4399 were standardized in ETSI TS 123 041 [4] for public warning systems like CMAS, EU-Alert, KPAS. All using the same channels which is beneficial for global roaming.
Android of course supports these public warning systems specified in ETSI TS 123 041 [4] since at least Android 4.2.2 [5]. And nations that use these systems already, like CMAS in the US, report very high and reliable coverage.
However, referring to German news [2] and government, not many phones that are currently on the market will actually support EU-Alert in Germany, despite already supporting EU-Alert in Netherlands or CMAS in the US.
How is this possible when exactly the same SMS-CB is broadcasted, just in a different country?
Golem [2] says that Samsung and Google already confirmed that EU-Alert is currently not supported in Germany, but updates will be rolled out to recent devices.
This strongly suggests to me that OEMs like Samsung and Google actually added country specific filters/configurations for these public warning systems to their phones without deploying a reasonable fallback. Public warning systems based on ETSI TS 123 041 [4] thus may only work in countries that were known to use these systems when the phone was released.
Isn't this an obvious issue?
Google said, starting with Android 11+ it will be possible to update the CellBroadcastReceiver App via Google Play. So devices with Android 11+ will likely receive an update to support EU-Alert in Germany. For Android 10 and older, OEMs will have to supply updates.
What also confuses me is the fact that all Android Phones I own (Nexus 4 with Android 5, Nexus 5X with Android 8, Pixel 3a with Android 12) here in Germany do actually offer the setting for Emergency Warnings and they are already enabled by default. So I assume they would work? Did Google actually deploy a sane default configuration here already?
But if they did - why isn't it working on ALL Android 11+ Phones already? I'm pretty sure my Pixel 3a uses Googles CellBroadcastReceiver App which is provided through the Play Store. So all Android 11+ phones should already use the exact same App?! Or am I wrong here? So what is this update Google actually needs to provide?
And does this also mean that with Android 11+ OEMs are not allowed / cannot implement their own Emergency Warning CellBroadcastReceiver?
This topic is really confusing to me
Shouldn't it be really simple?
All phones, regardless of the OEM, should have a proper SMS-CB Application which allows you to subscribe to custom channels, view the index, and manage your SMS-CB Messages.
Phones should also be aware of special channels to apply special ringtones etc if needed, but they should have a sane fallbacks!
A phone that knows about NL-Alert and CMAS may call messages on Channel 4370 received in the Netherlands "NL-Alert". But when it receives the same message in Germany, it shouldn't just drop it! It should display it as warning and call it whatever it wants. And if it doesn't know about CMAS / EU-Alert, it should just receive it as regular SMS-CB.
Can't be that hard?
Interestingly enough, Samsung phones allow you to subscribe to custom channels. Google phones do not :/
Should there be a better / more enforced standard, so that a country that wants to implement CMAS/EU-Alert in the future doesn't have to rely on OEMs help?
And finally some technical Questions:
I found zero Apps for Android that would allow me to subscribe to custom CellBroadcast Channels on my Google Android phones. Is this even possible?
Also, is it possible to test these CellBroadcasts somehow? Is it possible to write an App that can inject SMS-CB into the system?
Sorry for the long post, but I think this an important Topic.
Let me know what you think
Do you have experience with these Emergency Warnings already?
[1] https://www.etsi.org/deliver/etsi_ts/102900_102999/102900/
[2] https://www.golem.de/news/cell-broadcast-warum-es-am-warntag-ruhig-bleiben-koennte-2206-165822.html
[3] https://source.android.com/devices/architecture/modular-system/cellbroadcast#channel-50
[4] https://www.etsi.org/deliver/etsi_ts/123000_123099/123041/11.04.00_60/ts_123041v110400p.pdf
[5] https://cs.android.com/android/plat...ternal/telephony/gsm/SmsCbConstants.java;l=58
Hey! I was just researching something about this. Thanks for your detailed post.
I am from Chile and, in my case, my operator had subscriptions to two channels: 919 and 920.
In order to see the Cell Broadcast menu in the Messages app, I had to override a CSC setting (I use a Samsung device), particularly "CarrierFeature_Message_DisableMenuCBMessage") because it seems some Chilean operators ordered Samsung to hide it.
Even then, the Google Cell Broadcast app would not let me modify settings other than test alerts.
In my country these emergency alerts are quite unreliable and are often sent by mistake or to the wrong place (i.e. sending a tsunami alert to an area more than 100 km away from the coast).
Shooting Star Max said:
Hey! I was just researching something about this. Thanks for your detailed post.
I am from Chile and, in my case, my operator had subscriptions to two channels: 919 and 920.
In order to see the Cell Broadcast menu in the Messages app, I had to override a CSC setting (I use a Samsung device), particularly "CarrierFeature_Message_DisableMenuCBMessage") because it seems some Chilean operators ordered Samsung to hide it.
Even then, the Google Cell Broadcast app would not let me modify settings other than test alerts.
In my country these emergency alerts are quite unreliable and are often sent by mistake or to the wrong place (i.e. sending a tsunami alert to an area more than 100 km away from the coast).
Click to expand...
Click to collapse
Can you explain how you disabled this CSC setting and on what samsung phone/os?
You can see Googles/Androids latest default configuration for Chile (MCC 730) here:
https://cs.android.com/android/plat...apps/CellBroadcastReceiver/res/values-mcc730/
The config.xml really has some restrictive features enabled :/
Thanks for your reply!
Please note that all the following information assumes you have rooted your device. It's impossible to override this configuration otherwise.
My device is a Galaxy Note20 Ultra (Exynos version, SM‑N985F) running Android 12, One UI 4.1.
As you might know, Samsung devices include several packages named “CSC”, which define settings according to a sales code matching with a region. For example, a device sold in Chile without a carrier uses the sales code CHO, while one sold by operator Movistar uses the sales code CHT.
In the Galaxy Note20 Ultra, the CSC packages are stored in /optics/config/carriers/single (older Samsung devices might use /omc/).
Once you find the sales code matching with your current configuration, you can grab two files: cscfeature.xml and customer_carrier_feature.json. Taking CHO again as an example, the files would be /optics/config/carriers/single/CHO/conf/system/cscfeature.xml and/optics/config/carriers/single/CHO/conf/system/customer_carrier_feature.json.
These files are encoded, but OmcTextDecoder can take care of that.
In the case of CHO, customer_carrier_feature.json has the value "CarrierFeature_Message_DisableMenuCBMessage":"TRUE", which hides the cell broadcast menu in the stock Messages application. Just replace “TRUE” with “FALSE”, save the file and push it to its location. The next time you reboot your system, it will be applied.
Regarding the link you sent, I think we could get around that configuration by decompiling the GoogleCellBroadcastApp.apk through Apktool, modifying the restrictive values, and then pushing the APK to the device, replacing the original version.
Thank you!
Let me know if you managed to patch your original CellBroadcastReceiver.apk!
I actually tried using Runtime Resource Overlays (RROs) which is described on the official docu about CellBroadcast in Android.
You can find the result here: https://github.com/xsrf/android-de-alert
However, I didn't quite get these RROs. It looked like in Oreo you can use RROs to overlay any resource of any app without any permissions or matching signatures, which is quite a surprise to me?!
On my phones with more recent OS, I get signature mismatch errors and also it looks like apps now have to define what resources can be overlayed ...