Hello all. Thanks for bearing with my 2 quick (potentially newbie) questions posted today. I have spent a while lurking and searching while planning out my project here for my Apache.
This thread is really in hopes that I go about the means to my end goal correctly.
I currently have an HTC Apache with Sprint (PPC 6700 - WM5) and am looking to do a few things with it.
First, I'd like to streamline the phone some - taking out some of the unnecessary fluff that I don't use and anything that isn't required for basic use under Sprint's network.
Second, I'd like to add additional flexibility and utility with such things as the streaming media player, HTC home plug in (or potentially a third party such as WisBar Advance, phoneAlarm, etc.), HTC dialer (skinned), comm manager, a new contacts manager program, VGA mod (with ability to turn this on/off), Opera Mobile, and a mem card with a few add on programs/games/emulators/etc. I'd like this all to run with some speed here, as my first attempts in expanding the capabilities of the phone slowed it to a crawl (working on spare Apache to learn.)
Neccesary (or unnecessary?) details? I use primarily Sprint's EvDO service for internet essentially exclusively. WM5 on sprint's latest ROM (though this may change here I suppose?) My skill level is probably 5-6/10 on a newbie rating here.
Should I go with a custom ROM here for the phone to meet these goals? Pick a preset up ROM package or attempt to home cook one up with the required array of files? Leave the Sprint ROM and just add on the items I am looking for?
Thanks so much for input on this. I would like to attempt things here in a logical fashion this time with my everyday phone instead of simply trial and error.
Adam
AVE...
Is it possible to have Push To Talk function on phone, which doesn't have native software/hardware support? Of course, there are special programs that add this function, but they implement their own solutions and can work only when all phones have the same software installed. My GSM network is PTT-capable, so I'm asking, if there is some kind of standard application that will let me use my Rose to communicate with PTT-capable phones, i.e. Nokia E50...
if i'm not mistaken, keeping a PTT link opened is not as keeping a regular conversation opened and i'm pretty sure your device has to support that option, not just your network..
The race to Android 2.3 updates is on. Yesterday several users started reporting that Samsung was rolling out a new version of Kies, the desktop software used to update Galaxy S phones. We were wondering what the latest release was for and it appears this update is laying the groundwork for Android 2.3 updates of the Galaxy S.
In a Facebook posting Samsung said, “You need this update to be able to get the 2.3.2 update to your Samsung Galaxy S, Vibrant, Fascinate. 2.3.2 will be worldwide but carriers will be delayed.”
Samsung previously said on their Romanian Facebook page that the Android 2.3 update would be out by the end of March. That has yet to occur, but it looks like things are on schedule now that the new Kies is out.
Just as we saw with the Android 2.2 updates, the international versions of the Galaxy S should be updated long before the US versions of the phone. The delays might have been the carriers fault, but Samsung took a real beating since they arrived so long after the competition.
Hopefully this time around Samsung will work more closely with the US carriers to ensure their phones are updated in a timely manner.
http://drippler.com/samsung-galaxy-...utm_medium=social&utm_campaign=facebook-pages
I am positively shocked that they mentioned the US versions on Facebook. Just checked Mini Kies for the Vibrant and it is updating.
If Sammy makes this happen soon (official Gbread) it will go a long way in ensuring repeat customers.
Would be nice...but some of us just got froyo...naturally I want it though.
Sent from my SCH-I500 using XDA Premium App
Would be nice...
What are the benefits of the update? All I've seen is speed. I don't need download speed - I use wifi and don't download much anyway - just a few apps. The speed I want is processor. Read my PDF files and books faster. I might not want it as the phone is working just the way I want it. How do you refuse it in that case?
I just looked it up and the only interesting thing is VOIP. I had that on a Nokia.
1. New user interface has a simple and attractive theme in black background, which is designed to give a vivid look while being power efficient too. Menu and settings are changed for ease of navigation.
Don't care - use my own photos as wallpaper
2. Redesigned soft keyboard is optimized for quicker and accurate text input and editing. And the word being edited and dictionary suggestion is vivid and easy to read.
Don't care about that, either.
3. Multi touch key cording to input number and symbols without changing input mode
PITA on the Blackberry
4. Selection of word and copy/paste made easy.
Don't use
5. Improved power management through application control.
Might be interesting
6. Provide user awareness on power consumption. Users can view how the battery is used and which consume more.
Same as above
7. Internet calling – supports SIP calls to other users with SIP account
Very interesting - But Skype over wifi works
8. Support Near-field communication (NFC) – high frequency high speech data transfer within a short range (10 cm). This will be useful feature in m commerce.
No
9. A new download manager facility that supports easy storage and retrieval of downloads
Have no problem now.
10. Support for multiple cameras
Mostly use separate camera - As far as I'm concerned, the 5mp camera in the Nokia C6 was superior to the one in the SGS4G.
I use the phone as a PDA/phone. I don't see much there to benefit me.
Z
I have an AT&T Home Manager by Samsung, Model SMT - i8110 and am wondering if anyone knows what OS Samsung used on this unit and if it can be converted to something that will allow the web access to work with again. The desk frame/phone unit is the i8110 number. I am not sure what the base station is that connects to the actual Ethernet connection of the Internet router. These were supported for limited web access by AT&T when they were being sold but that access was discontinued not long after AT&T stopped selling the units. If they could have a version of Android put on them they would be great for desk or counter top access for things like appointment calendar, weather, and recipe access through the available apps. Since I am not a dev, and know nothing about coding and development I have to ask those here that are much smarter than myself.
Thanks,
Gary
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 ...