Apologies if this isn't the correct place to ask (if this is the case please by all means move this thread) - but I've discovered some chinese tablets don't support the 32 bit rendering which FMH2013 is using to display its screens.
I've written a 16 bit renderer which will allow people with these devices to play the game HOWEVER the devices don't appear to know they can't render 32 bit so I'm having to detect the devices individually via. their device specs.
At the moment I'm mainly using the android.os.Build.DEVICE field - if anyone has issues with a device running FMH where it fails to display the games start page once the splash page then please let me know with the name of your device and if at all possible the android.os.Build information for that device, that way I can ensure its detected properly in the forthcoming update (and the game works upon it).
For example:
android.os.Build.DEVICE
"nuclear-f721" = Versus TouchPad7
"crane-a721" = CNM Touchpad7
Thanks,
Marc
Hello All,
I was thinking that we should start a discussion which would help companies with feedback in giving up a phone which related to current market situation and components available. It is very simple everyone would have a configuration they would be looking for to own. A configuration that the phone maker is unable to give at a certain price or model. We put in our specification , name the phone the specification is derived from, and relate to the Phone manufacturer with the configuration.
We can have the following Specification that make the phone worth:
Processor -
RAM -
OS - (Multiple Options here)
Storage -
Micro SD card Support - Yes/No
Display - (Size/Type/Screen Protection)
Sound - (Not many options here)
Connectivity - (DLNA,HDMI, NFC, BLUETOOTH, WiFi etc.)
GSP - (We have limited options here)
Other feature you would want on phone - IRIS Scanner, Fringerprint Scanner, Touchpad
Let us think and see if we can really help the current market and make the manufactures listen to us and our needs.
I'm up to buy a used Samsung Galaxy S9 and wondering about how can I check it's processor health.
Let's say, the person from whom I am buying has intensively used this device for high graphics gaming, etc.
And, do smartphone processors really age like Computer's do?
PS: Yes, even in 2021, I still want this phone.
AFAIK there´s no way to check the health of a CPU ( at least not on consumer level ).
jwoegerbauer said:
AFAIK there´s no way to check the health of a CPU ( at least not on consumer level ).
Click to expand...
Click to collapse
What about stress testing? Is this any better than nothing at all for an estimate of CPU health/performance? And, is it reliable?
IMO this only makes sense if you can do the same test on a brand new device of the same manufacturer / same model, so that you can find differences.
It's your decision to waste your time with this ...
EDIT:
Have AndroidStressTest apk atteched
Go to setting / about phone / build number. Tap build number to turn on developer option.
Now under developer option find SHOW CPU USASE.
You can check usage of CPU. There are android app for processor testing.
You can use diagnosis tool of android mobile. Use *#0#. You will get Display test, sensor test, hardware test and more test.
For desktop computer you can use Intel processor diagnostic tool.
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 ...
Hi
Please be gentle with me if this has been covered somewhere, I've searched high and low and been unable to find an answer...
There is a free app available on the playstore (made by a large home automation company) which I have downloaded on both an android phone and tablet. The app is missing one specific function on the tablet which is available on the phone, this is "intercom" functionaliy. According to the developer, this is by design - this is intended to promote their own hardware product for this task (also an android touch screen interface). However, I cannot afford to buy their device ($$$$s) and would like to have the app pinned and running on a cheap tablet. This works fine, apart from the lack of intercom.
The intercom function is a voip service and does not require a cellular connection, only a camera, microphone, speaker and network connection. I have proved this by turning off mobile data on the phone and can simulate the functionality on the tablet by using a seperate voip app and registering the tablet on the voip network.
My question: From my research it would seem likely the app is using the display size / resolution, "telephonymananger" or a combination of both to enable / disable the intercom function depending on the device type. Is there a way to circumvent this? i.e. is there a way to emulate a different screen size & property in telephonymanager? Ideally I could do this on a 10" fire HD tablet 9th / 11th generation, but if there is a similarly cheap tablet that would be much easier I would be willing to invest in that.
Grateful for any answer, advice, or direction anyone can offer.