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

Updated

Hot New

Updated

 Browse

Is there a phone with the features I loved, but much more powerful?

Papamalo
I am now using an LG V30, my faithful replacement for what I thought was the greatest phone for me ever, the Motorola Moto X Pure. If I had ever found a way to even hack at the hardware and just make it faster, I'd have never deviated from the Motorola Moto X pure.
Here's why:

Motorola Moto Voice had customizable commands for ANYTHING I wanted to do. Period.
Unlock Phone? Check
Take a picture? Check.
Read my messages? Check.
Play a youtube video? Check
Customizable security Password? Check.
Bluetooth remote shutter compatible? Check.

Why, you might ask, if it was so dammed great, did I give it up.
Speed and power. It started with 3 GB RAM, and some now-ancient specs: and started slowing down and I had to put her down. But it was a phone with all the features I want, just not the power and speed.

Motorola Moto X Pure ("Style" in the U.S.) Specs
OS Android 5.1.1 (Lollipop), 6.0, upgradable to 7.0 (Nougat)
Chipset Qualcomm MSM8992 Snapdragon 808 (20 nm)
CPU Hexa-core (4x1.4 GHz Cortex-A53 & 2x1.8 GHz Cortex-A57)
GPU Adreno 418

Even the 21 MP camera worked better for my job at grabbing license pates at a distance, in the dark, than my newer LG V30. (I work security and make nightly patrols and take plate numbers of visiting cars in our facility)

So, is there a camera that can be operated totally hands free, all by voice command including the unlock command, all by voice, and all customizable that has at least 8GB RAM, a recent chipset, and a really good camera?
(Preferably some proprietary voice command program like Moto Voice. I Fu**ing HATE google for not letting me customize my commands, and making me say their cursed name anytime I want something)

Thanks for listening to my niche rant, about some old-ass phone

PM
Click to expand...

LG V20

puppykickr
The batteries will usually say what the properties are on the batteries themselves.

The trick is if the connections are the same, and in the same location, and if the size and shape of the batteries are the same.

The best way I have found to get a perfect replacement battery is to enter the model number of the battery into my browser, and disregard any info about whatever phone(s) it is supposed to fit.

But, there is the chance that you could be able to use this info as a cross reference.
Click to expand...

App Inventor Problem with MediaPlayer.create() when recreating with same files after mediaPlayer.release()

A
I have a simple media player app that works fine for a while (like each song will play about 50 times) and then starts to crash on almost all the media files (a few still work but lag really bad; there is no lag until the errors). These errors continue even after stopping the activity and reopening!

These same media files work with other media players after they quit working in mine, so there is clearly something very wrong. I have to restart my device for my Activity to be able to call MediaPlayer.create() on the files without errors again. This behavior is so obscure!

One create:
Code: 
E/MediaPlayer: error (1, -38)
E/MediaPlayer: error (1, -2147483648)
E/MediaPlayer: Error (1,-38)
E/MediaPlayer: error (1, -2147479551)
E/MediaPlayer: error (1, -38)
Another:
Code: 
E/MediaPlayer: error (1, -2147479551)
E/MediaPlayer: Error (1,-2147479551)
E/MediaPlayer: error (1, -38)
Yet another:
Code: 
E/MediaPlayer: error (1, -38)
E/MediaPlayer: error (1, -2147479551)
E/MediaPlayer: error (1, -38)
E/MediaPlayer: Error (1,-38)

So the errors are inconsistent in order, but there are recurring numbers. One of the numbers are not in the MediaPlayer.java file for the target SDK 30, but the device I am testing is using Android 6.0.1 which I believe is SDK 23. I am not entirely sure how to find the relevent Android source. Using Google search "site:https://android.googlesource.com/ mediaplayer.java" is the best way I have found.

I did find
Code: 
MEDIA_ERROR_SYSTEM = -2147483648
and
Code: 
MEDIA_ERROR_UNKNOWN = 1
. I have an unknown media error from the system.

What about -2147479551? It appears to be MEDIA_ERROR_SYSTEM | 0x1001. 0x1001 does not appear in MediaPlayer.java. It is another unknown media error. What extra information was attached? What about -38?!

What could cause such a bug. I don't even know how to wrap my head around this behavior. Is MediaPlayer not releasing correctly? Am I leaking resources that don't go away when the app closes? My code is fairly simple and it appears to release everything like it is supposed to. How come a restart fixes the issue?

Here is the relevant code:
Code: 
    Playlist masterPlaylist;
    public boolean surfaceCreated;
    AudioURI currentSong;
    AudioURI nextSong;
    MediaPlayer mediaPlayer;
    MediaPlayer nextMediaPlayer;
    VideoView videoView;
    final Object lock = new Object();

    MediaPlayer.OnCompletionListener onCompletionListener = new MediaPlayer.OnCompletionListener() {
        @Override
        public void onCompletion(MediaPlayer mediaPlayer2) {
            synchronized (lock) {
                Log.i(TAG, "onCompletion started");
                currentSong = nextSong;
                mediaPlayer.release();
                mediaPlayer = nextMediaPlayer;
                if (surfaceCreated) {
                    mediaPlayer.setDisplay(videoView.getHolder());
                    mediaPlayer.start();
                }
                nextSong = masterPlaylist.next();
                executorService.submit(runnableNextMediaPlayer);
                Log.i(TAG, "onCompletion ended");
            }
        }
    };

    View.OnClickListener onClickListener = new View.OnClickListener() {
        @Override
        public void onClick(View view) {
            Log.i(TAG, "onClick started");
            currentSong = nextSong;
            mediaPlayer.release();
            mediaPlayer = nextMediaPlayer;
            if (surfaceCreated) {
                mediaPlayer.setDisplay(videoView.getHolder());
                mediaPlayer.start();
            }
            nextSong = masterPlaylist.next();
            executorService.submit(runnableNextMediaPlayer);
            Log.i(TAG, "onClick ended");
        }
    };

    ExecutorService executorService = Executors.newSingleThreadExecutor();

    Runnable runnableNextMediaPlayer = new Runnable() {
        @Override
        public void run() {
            synchronized (lock) {
                Log.i(TAG, "creating next MediaPlayer");
                nextMediaPlayer = MediaPlayer.create(getApplicationContext(), nextSong.getUri());                nextMediaPlayer.setVideoScalingMode(MediaPlayer.VIDEO_SCALING_MODE_SCALE_TO_FIT_WITH_CROPPING);
                nextMediaPlayer.setOnCompletionListener(onCompletionListener);
                Log.i(TAG, "next MediaPlayer created");
            }
        }
    };

    public void calledAtTheEndOfOnCreate() {
        videoView = findViewById(R.id.video_view);
        currentSong = masterPlaylist.next();
        mediaPlayer = MediaPlayer.create(getApplicationContext(), currentSong.getUri());
        mediaPlayer.setVideoScalingMode(MediaPlayer.VIDEO_SCALING_MODE_SCALE_TO_FIT_WITH_CROPPING);
        mediaPlayer.setOnCompletionListener(onCompletionListener);
        nextSong = masterPlaylist.next();
        executorService.submit(runnableNextMediaPlayer);
        videoView.getHolder().addCallback(new SurfaceHolder.Callback() {
            @Override
            public void surfaceCreated(@NonNull SurfaceHolder surfaceHolder) {
                surfaceCreated = true;
                mediaPlayer.setDisplay(surfaceHolder);
                mediaPlayer.start();
            }

            @Override
            public void surfaceChanged(@NonNull SurfaceHolder surfaceHolder, int i, int i1, int i2) {}

            @Override
            public void surfaceDestroyed(@NonNull SurfaceHolder surfaceHolder) {surfaceCreated = false;}
        });
        FloatingActionButton floatingActionButton = findViewById(R.id.fab);
        floatingActionButton.setOnClickListener(onClickListener);
    }
Click to expand...

S20 ultra screen burn

T
Hi can anyone offer advice pls
I have a s20 ultra that is displaying ghost icons from my home screen
Mainly visible on a white background
Ive had the phone for 5 months
Ive had dialogue with samsung and they arranged for a mobile engineer to come to my adress and replace the screen
On arrival i got the impression he was looking for a way out of repairing it siting miniscule marks on the edges of the frame (phone has been in a case with a screen protector since new)
He took the phone to his van but returned saying there was a crack on the screen so he couldnt do anything as the 2mm ,what i thought was a scratch, was a crack and the phones warranty was invalid because of it
So the tiny damage on the screen which has nothing whatsoever to do with the original screen burn issue has invalidated my warranty on a £1400 flagship phone
Im absolutely gutted and wondered if anyone has experienced similar?
Thank you
Click to expand...

Messages during loading

lunatic59
I can't find a whole lot of information about com.qti.diagservices but it seems to come from Samsung so I would guess it's a service to check the state of something on your phone. The callenhancement app or service seems to come from LG. I find it odd that they'd both be on your phone. The message you are getting means that both services have failed to load at startup.
Click to expand...
Load more

Filter

Back
Top Bottom