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

Updated

Hot New

Updated

 Browse

Help me with correct cpu / rom file

svim
Part of the problem is you need to use the correct ROM that matches the phone model. MT6735M and similar designations refer to the SoC, the processor chip inside the phone. Ignore that, it's irrelevant for what you're trying to do. ROMs are not interchangeable, they are each specific for a particular phone model. Hopefully you have only soft-bricked this phone, so you just need to re-flash it with its correct ROM. If you hard-bricked it, that's going to be a bigger problem. You might be able to have a local service shop fix it but hard-bricked phones often require a reset from the manufacturer.

What is the phone make and model is this phone? Also, is it a carrier-locked model? (Carrier unlocked models can typically be used on selected, different carriers, ones that use similar cellular networks, but carrier-locked models are basically only usable for the specific carrier.)
Click to expand...

Check your devices for these 'fleeceware' apps

MoodyBlues
Good for you, @The_Chief! :)

I have many credit cards--even multiple cards from the same company, e.g., American Express and CapitalOne--and use them differently depending on various factors.

Some, like one of my Cap1 cards and my Amazon Prime card, pay 5% cash back; I use them as old-school charge cards, paying them off monthly. Like you, they pay me for using them. :D

Other cards I use for major purchases, like appliances, when they're offering 0% interest for X months. That's how I bought my new washing machine a year ago--0% interest for 18 months. I did the math, and easily made monthly payments that would have it paid off well before interest kicked in.

I never have cards with membership/annual fees.

Also, I live by a rule that I implemented after life's hard knocks taught me a lesson: never charge anything, including new cars, I don't have money in the bank to pay off immediately, if need be. That served me very well when I abruptly, unexpectedly, and permanently lost my income [due to illness].
Click to expand...

Help Upgraded to 9 and it changed my messaging text to black so now I can't see the text

K
Hadron said:
There are 4 options I can see:

1) See whether there are any theming options (including night modes or similar as well as any actual theme options LG provide) in the device settings which have an affect in this. I don't have this device or any LG so don't know what options there might be, but I can imagine some device theme/display setting interacting badly with your message setting, in which case changing that (or even toggling it to something else and back again) might correct this.

2) See whether there is anything at all in the app's settings that changes this (yes, I know you've looked, just trying to cover all possibilities).

3) If the problem is due to an incompatibility between old (Android 8) setting and LG's "new" Android 9 system or apps then deleting those settings (i.e. resetting the app to defaults) might fix it. So you could start by force stopping the message app and clearing its cache, or clearing its cache and rebooting. More likely to work is clearing the message app's data. Unless LG are doing something very weird and non-standard that should not affect your messages: there's a system database that stores those independent of which SMS app you are using, so clearing data for the message app should only affect the message app's settings. If you are worried then back up your messages first (probably not a bad idea anyway), but I've cleared data for both system and third party message apps on other phones without losing messages (on my phone, running Android 10, it's the system app "Phone and Messaging Storage" which actually stores the messages. On other phones I've owned there was a separate "Message Storage" app. So don't clear data for any app that has "message" and "storage" in the name, because that will erase your messages).

4) I know you said you didn't want to, but the final option is to use a third party app. Personally I think there are several which are better than any manufacturer's own app that I've ever used, so I never use the built-in app, but it's your preference. But if nothing else works, this will.
Click to expand...


I have resolved the issue! So I first completely took off the theme and the background I was using and tried to reapply it to see if it helped. It didn't. So then I took it all off again and restarted my phone and then put it back on again and it was fine!

(I could have just unapplied the theme and I wouldn't have had the issue but the plain LG theme is God awful)
Click to expand...

Help Suggestions for data-only plan

The_Chief
It's not easy finding a GSM provider that sells a 1GB data only plan! I found US Mobile does, but it's 1.5 GB for $10/month. I think there is another one I found that's 1GB for $6/month. Of course, with all the taxes and "fees" that price doubles...

EDIT: @MoodyBlues I contacted Consumer Cellular and they never responded. Apparently either they don't need my business, or they don't have what I want and they're too rude to reply and tell me that. Oh well, I have a few weeks to lock down a plan...
Click to expand...

Hello, i am making tasks correctly but it still gives me sign up fail, whats wrong

shakoc
Code: 
package com.trashysofts.auct


import android.content.Intent
import android.os.Bundle
import android.util.Patterns
import android.widget.Toast
import androidx.appcompat.app.AppCompatActivity
import com.google.firebase.auth.FirebaseAuth
import kotlinx.android.synthetic.main.register_layout.*

class RegisterActivity : AppCompatActivity() {

    private lateinit var auth: FirebaseAuth

    override fun onCreate(savedInstanceState: Bundle?) {
        super.onCreate(savedInstanceState)
        setContentView(R.layout.register_layout)
        auth = FirebaseAuth.getInstance()
        buttonJoin.setOnClickListener {
            signUpUser()
        }

    }

    private fun signUpUser() {
        if (emailTextSignUp.text.toString().isEmpty()) {
            emailTextSignUp.error = "Please enter email"
            emailTextSignUp.requestFocus()
            return
        }
        if (!Patterns.EMAIL_ADDRESS.matcher(emailTextSignUp.text.toString()).matches()) {
            emailTextSignUp.error = "Please enter valid email"
            emailTextSignUp.requestFocus()
            return
        }
        if (passwordTextSignUp.text.toString().isEmpty()) {
            passwordTextSignUp.error = "Please enter password"
            passwordTextSignUp.requestFocus()
            return
        }
        auth.createUserWithEmailAndPassword(emailTextSignUp.text.toString(), passwordTextSignUp.text.toString())
            .addOnCompleteListener(this) { task ->
                if (task.isSuccessful) {
                    startActivity(Intent(this,LoginActivity::class.java))
                    finish()
                } else {
                    Toast.makeText(baseContext, "Sign Up failed",
                        Toast.LENGTH_SHORT).show()
                }
            }
    }
}
Click to expand...

Aiuto - Android App & MySQL DB

Unforgiven
Translation:
[QUOTE = "KatAlive, post: 7940738"] Hi everyone,
I'm mainly a JAVA developer, I've never worked with android and android apps; however, I was asked to try to create an app that would allow, writing data in the TextFields, to insert them later in a MySQL database (I use DBForge on Java, while for this exercise I used WampServer with PHPMyAdmin). Although the creation of the app itself was rather easy, the complicated part is to make the DB communicate with Android, apparently it is not as immediate as with Java. Searching on Youtube among various tutorials I found one that allowed me to get to the end of my work; however when I click on the "REGISTER" button of my program the alert that says "Data successfully registered" appears, but nothing has been entered in my database, I don't understand where he entered them or where those data went. Can I post my codes below for some help?

Thanks in advance . [/ QUOTE]
Click to expand...

Connecting Bluetooth Headphones to Hisense Android TV

ocnbrze
Rob said:
Maybe the solution is to buy a TV that's not so crappy but thinking it could also be something I'm overlooking, issue with Airpods specifically, or a conflict with the Sonos (which seems unlikely since the problem occurs with the Sonos unplugged)
Click to expand...
this.

Hisense is only good at one thing.....making cheap affordable tvs. but like with most electronics, you get what you pay for. not really surprised that you are having issues with bluetooth connectivity.

check out this article:
https://www.techradar.com/news/should-i-buy-a-hisense-television

i have better success with Best Buy's versions of cheap affordable products which is their Insignia brand. i have a Insignia tv that i use in my bedroom that works great. it is connected to my bluetooth soundbar i have......and i have my beats solo 3 headset connected to it as well.

https://www.bestbuy.com/site/tv-hom...vs/pcmcat363400050006.c?id=pcmcat363400050006
Click to expand...

Motorola G5 Plus , model number XT1686 has crashed (got into bootloop during manual restart)

ocnbrze
sorry but you most likely will have to flash a firmware to recover your phone. this will indeed wipe all of your data. in this situation there is no other alternative.

now as far as any paid programming goes, i think most of those that claim a full recovery of a phone without losing data is a scam. i would be very careful if you go that route.
Click to expand...

Root Monstro's Rom v3 SM-G360T & SM-G360T1 5.1.1 Fastest and Lightest Rom 6/12/2016

J
xXCool666GuYXx said:
So I loved this ROM on my phone I still have the phone and it's rooted so I don't know why yours bricked when you flash su and about this fm how you say every phone has it?! If so how would one enable it for it to work on there phone? Or any phone? I'm on a LG v10 now lol
Click to expand...

I know i'm a couple years behind the conversation, i had some...business...but i took a look through some of the code for this ROM, and its ****ed from the GATE!!! take a look for yourselves!!! and you'll then know why this rom has bricked phones.

#ASSERT
unmount("/system");
unmount("/data");
unmount("/data");
show_progress(1.000000, 0);
ui_print("");
ui_print("");
ui_print("Monstro's Rom v1 SM-G360T");
ui_print("Lightest and Fastest Rom Yet");
ui_print("Google’s definition of an upgrade?");
ui_print("");
ui_print("");
ui_print("Take old bugs out, put new ones in");
ui_print("");
ui_print("");
format("ext4", "EMMC", "/dev/block/platform/soc.0/by-name/system", "0", "/system");
set_progress(0.100000);
mount("ext4", "EMMC", "/dev/block/platform/soc.0/by-name/system", "/system");
mount("ext4", "EMMC", "/dev/block/platform/soc.0/by-name/userdata", "/data");
set_progress(0.200000);
ui_print("Calling The Zombies...");
ui_print("");
package_extract_dir("system", "/system");
#DATA
ui_print(""); ui_print(" ");
package_extract_dir("data", "/data");
set_metadata_recursive("/data/app", "uid", 1000, "gid", 1000, "dmode", 0755, "fmode", 0644, "capabilities", 0x0);
set_progress(0.500000);
ui_print("What does a slow & lazy Android phone say?");
ui_print("- Force Close");
#SYM
symlink("app_process32", "/system/bin/app_process");
symlink("dalvikvm32", "/system/bin/dalvikvm");
symlink("/data/misc/audio/mbhc.bin", "/system/etc/firmware/wcd9306/wcd9306_mbhc.bin");
symlink("/data/misc/audio/wcd9320_anc.bin", "/system/etc/firmware/wcd9306/wcd9306_anc.bin");
symlink("/data/rfs/apq/gnss", "/system/rfs/apq/gnss/readwrite");
symlink("/data/rfs/mdm/adsp", "/system/rfs/mdm/adsp/readwrite");
symlink("/data/rfs/mdm/mpss", "/system/rfs/mdm/mpss/readwrite");
symlink("/data/rfs/mdm/sparrow", "/system/rfs/mdm/sparrow/readwrite");
symlink("/data/rfs/msm/adsp", "/system/rfs/msm/adsp/readwrite");
symlink("/data/rfs/msm/mpss", "/system/rfs/msm/mpss/readwrite");
symlink("/data/rfs/shared", "/system/rfs/apq/gnss/shared");
symlink("/data/rfs/shared", "/system/rfs/mdm/adsp/shared");
symlink("/data/rfs/shared", "/system/rfs/mdm/mpss/shared");
symlink("/data/rfs/shared", "/system/rfs/mdm/sparrow/shared");
symlink("/data/rfs/shared", "/system/rfs/msm/adsp/shared");
symlink("/data/rfs/shared", "/system/rfs/msm/mpss/shared");
symlink("/data/tombstones/lpass", "/system/rfs/mdm/adsp/ramdumps");
symlink("/data/tombstones/lpass", "/system/rfs/msm/adsp/ramdumps");
symlink("/data/tombstones/modem", "/system/rfs/apq/gnss/ramdumps");
symlink("/data/tombstones/modem", "/system/rfs/mdm/mpss/ramdumps");
symlink("/data/tombstones/modem", "/system/rfs/msm/mpss/ramdumps");
symlink("/data/tombstones/sparrow", "/system/rfs/mdm/sparrow/ramdumps");
symlink("/firmware", "/system/rfs/apq/gnss/readonly/firmware");
symlink("/firmware", "/system/rfs/mdm/adsp/readonly/firmware");
symlink("/firmware", "/system/rfs/mdm/mpss/readonly/firmware");
symlink("/firmware", "/system/rfs/mdm/sparrow/readonly/firmware");
symlink("/firmware", "/system/rfs/msm/adsp/readonly/firmware");
symlink("/firmware", "/system/rfs/msm/mpss/readonly/firmware");
symlink("libGLESv2.so", "/system/lib/libGLESv3.so");






#ROOT
ui_print("Failed");
package_extract_dir("supersu", "/tmp/supersu");
#DATA
ui_print("Retrying"); ui_print(" ");
package_extract_dir("data", "/data");
set_metadata_recursive("/data/app", "uid", 1000, "gid", 1000, "dmode", 0755, "fmode", 0644, "capabilities", 0x0);
run_program("/sbin/busybox", "unzip", "/tmp/supersu/BETA-SuperSU-v2.72.zip", "META-INF/com/google/android/*", "-d", "/tmp/supersu");
run_program("/sbin/busybox", "sh", "/tmp/supersu/META-INF/com/google/android/update-binary", "dummy", "1", "/tmp/supersu/BETA-SuperSU-v2.72.zip");
set_progress(0.800000);
ui_print("");
ui_print("Falied");
ui_print("");
package_extract_file("boot.img", "/dev/block/platform/soc.0/by-name/boot");
set_progress(0.900000);
unmount("/system");
unmount("/data");
set_progress(1.000000);
ui_print("Bricked");


****alll the code was too long for the msg...
Click to expand...

Attachments

  • upload_2020-1-16_20-31-18.png
    upload_2020-1-16_20-31-18.png
    224.3 KB · Views: 204
Load more

Filter

Back
Top Bottom