• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help!! Recommendations please

The GSMArena site has a handy phone finder function that might help you narrow down your choices. Go here and go through the various options:
https://www.gsmarena.com/search.php...ailabilities=1&sFormFactors=1&sFingerprints=1

Above all else though, and this has more relevance depending on where you reside, is full compatibility with your chosen carrier. (i.e. -- Here in the U.S. where carriers are very territorial and hostile to interacting with competing services, phone models are very defined. Be wary when buying branded phones. In the E.U. it's not as anal.)

Also keep in mind that your £200 budget limitation is contrary to a phone's long term prospects. Since you referred to updates as a factor as to why you're looking into upgrading to a newer phone, while Apple tends to support its own products much longer on a more consistent basis, with Android it's really a mixed bag. Samsung only recently stated it will support some of its product line for four years, Google has supported its Pixel line for three years, Motorola is a very iffy at maybe two years, and most off-brands may support their stuff for a year or not at all. The point being with Android, only flagship model lines 'may' be getting long-term support, but phones in that £200 price range it's not as likely.
https://www.nytimes.com/wirecutter/reviews/best-budget-android-phone/
So one option that doesn't appeal to everyone is to get something like a Moto phone, and replace it every couple of years when support for it ceases. Motorola makes some really good models at economical prices that are solid day-to-day usage phones, just adjust your expectations accordingly. Another thing to consider is if you're pretty well immersed in the Apple iPhone environment, you might find migrating to Android a bit aggravating. Transferring your iPhone user account data won't be a trivial process. So do this because you have specific reasons, long-term phone support not being a real highlight in the Android platform.
https://www.nytimes.com/wirecutter/reviews/ios-vs-android/
One last thing, and this is just a subjective opinion, is you'll find it easier to migrate back to Apple if you don't find it appealing to use Android. Apple makes its wall-garden difficult to get out of, Google is by no means benevolent about this but it does use more open standards and protocols on a much greater scale. Moving data out of Apple's oversight is going to be involved, moving data out of Android not as much.
https://www.computerworld.com/artic...ch-from-iphone-to-android-ultimate-guide.html
But if you do move to Android, don't make direct comparisons between Android and Apple without the proper context. You'll be contrasting a new budget-class device with a dated flagship model -- this will involve countless pluses and minuses with both hardware and software aspects of both phones.

Coolpad legacy

if you are planning to root a device and wanted to know if it is possible, you should always start out over at https://forum.xda-developers.com/. it is a developers forum where the developers publish their root methods, custom recoveries, custom roms, and other root related goodies. if you do not find a forum for your device then that usually means that there is no dev community supporting it. just remember no devs=no fun. and that usually means that there is no root method for your device.

keep an eye out on this thread:
https://forum.xda-developers.com/android/help/help-rooting-coolpad-legacy-3705a-info-t3952579/page7

Yeah I know I'm a senior member on xda I created a form there a while ago about this phone

FLX - Android visual scripting app

FLX v1.2.3 is now available (https://play.google.com/store/apps/details?id=com.flx) and provides an API for implementing fully customisable MQTT clients. The app provides a project template for creating a simple client. v1.2.4 will provide a project template with UI for FLX applets that implement a generic MQTT client. Users can then modify this template based applet.

You can use this public web socket based front end for the HiveMQ broker for testing your MQTT applet: http://www.hivemq.com/demos/websocket-client/

Brave Browser Leak

From what I gather, the info that was leaked was anything searched for with the TOR alternative that Brave uses.

This was due to how the ad-blocker works.

So, anything searched for on the dark web was visible to your provider.

This is exactly what TOR is supposed to prevent.

The only thing 'brave' about Brave are the people that use it and think it is secure, lol.
I tried it once of my old PC, I did not like it one bit, kept piling up several different issues.

How do I find if I have background location services? I only use ACCESS_FINE_LOCATION foreground

I'm currently struggling with being compliant with new google play policies regarding localization permission.

I developed an app to call emergency numbers from (almost) any country in the world and I have a feature that allows the user to click on a button to locate himself and display the corresponding emergency numbers of the country he is in.

My issue is that Google sent me an email to reject my app because I quote : "Feature does not meet requirements for background location access".
The thing is : I do not ask for background location access, so I do not know what to do... I ask for "ACCESS_FINE_LOCATION" and I start a service declared as foreground.

Here is my manifest :

Code:
    <uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" />
    <uses-permission android:name="android.permission.CALL_PHONE" />

    <application
        android:allowBackup="true"
        android:icon="@drawable/er"
        android:label="@string/app_name"
        android:roundIcon="@drawable/er"
        android:supportsRtl="true"
        android:theme="@style/AppTheme"
        android:windowSoftInputMode="adjustPan"
        android:screenOrientation="portrait">

        <service
            android:name=".LocationService"
            android:enabled="true"
            android:description="@string/emergency_localization"
            android:foregroundServiceType="location"
            android:icon="@drawable/er"
            android:label="@string/emergency_localization_label"
            android:permission="android.permission.FOREGROUND_SERVICE"/>

        <activity android:name=".MainActivity">
            <intent-filter>
                <action android:name="android.intent.action.MAIN" />
                <category android:name="android.intent.category.LAUNCHER" />
            </intent-filter>
        </activity>
    </application>

    <uses-feature
        android:name="android.location.Geocoder"
        android:required="false" />

And the code plugged to the localization button :

Code:
            findMeBtn.setOnClickListener(v -> {
            if (!PermissionNeeded()) {
                DisplayIcon(true);
                locationIntent = new Intent(getApplicationContext(), LocationService.class);
                startService((locationIntent));
            }
        });

I asked for more information to Google, and the only answer was :

"We have re-reviewed your app, but your declared feature still does not meet the requirements to access location in the background because of the following reason(s):

Users may not expect the app to access their location in the background
It is possible to deliver a similar experience without access to location in the background"

Thank you very much Google for being more explicit...

I saw afterwards that I was not stoping the service in the onPause method in the main activity, so I added this and tried to publish it again, but same error, apparently I am still asking a background service permission, without currently asking it ...

Code:
@Override
public void onPause() {
    super.onPause();
    if (locationIntent != null) stopService(locationIntent);
}

@Override
public void onDestroy() {
    super.onDestroy();
    unregisterReceiver(broadcastReceiver);
    if (locationIntent != null) stopService(locationIntent);
}

So I'm pretty sure I'm missing something obvious somewhere, but since I have no idea where to look at, I really need a new pair of eyes on it... I am now losing faith on this app's future...

Thanks a lot by advance !

Filter

Back
Top Bottom