-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Help Bricked(?) Huawei WAS-LX1A
- By Hadron
- Ask a question
- 17 Replies
"Rooted" refers to the state of the ROM, i.e. whether it has been modified so that the user can grant admin rights to user-installed apps. So if the ROM part of the sequence of files you flashed was stock (official software) then your phone will not be rooted. My guess would be that it isn't rooted, since a process that replaces TWRP with a stock recovery and locks the bootloader doesn't sound like one that will install a rooted ROM.
.
I guess this is a device where they built one set of hardware and then disabled the dual SIM functionality via firmware in some regions or for some carriers, because that's the only way I can see what you've done here actually working. But my point is that being able to do this is a special case, so probably the only people who could say with confidence what to expect would be those who have performed similar mods on this model, or at least another Huawei of similar age. You could ask in one of those XDA threads, if there is anyone still watching them, but it's not a question I can answer.
I'm not familiar with modifying Huawei phones, so can't say. But yes, it is possible that the update path for one model, or one firmware version of one model, doesn't go as high as for another. If you've been flashing firmware for one model onto a different model it's also not impossible that the official update process looks at your device and says "hang on, something's not right here" and refuses to install any further updates, though in that case I'd think it more likely that it would apply no updates at all than that it would update so far and no further.
Well the "normal" thing that happens if you succeed in flashing a different model's firmware onto a phone is that the phone is hard-bricked
.I guess this is a device where they built one set of hardware and then disabled the dual SIM functionality via firmware in some regions or for some carriers, because that's the only way I can see what you've done here actually working. But my point is that being able to do this is a special case, so probably the only people who could say with confidence what to expect would be those who have performed similar mods on this model, or at least another Huawei of similar age. You could ask in one of those XDA threads, if there is anyone still watching them, but it's not a question I can answer.
App Inventor Google TV remote volume up/down not registering
- By stealthrt
- Android Development
- 0 Replies
Hey all I have been trying to get my remotes volume up/down buttons to register in my app but they never seem to do anything when I press them?
I have tried:
and also
But like I said, every time I hit the buttons they never fire any of those above. The only ones that register are the Dpad up/down/left/right, center button and the back button.
I cam change the volume just fine using this code:
But that does me no good if I cant detect the volume up/down being pressed...
The google TV remote looks like this:
Anyone know what I am missing?
I have tried:
Java:
public class CallBroadcastReceiver extends BroadcastReceiver {
@Override
public void onReceive(Context context, Intent intent) {
int volume = (Integer)intent.getExtras().get("android.media.EXTRA_VOLUME_STREAM_VALUE");
Log.i("Tag", "Action : "+ intent.getAction() + " / volume : "+volume);
}
}and also
Java:
@Override
public boolean onKey(View v, int keyCode, KeyEvent event) {
if (event.getAction()!=KeyEvent.ACTION_DOWN)
return true;
switch (keyCode) {
case 20:
return false;
case 22:
fastForward();
return false;
case 21:
rewind();
return false;
case 23:
if (mTransportControlGlue.isPlaying()) {
mTransportControlGlue.pause();
} else {
mTransportControlGlue.play();
}
return false;
getActivity().finish();
return true;
}
return false;
}But like I said, every time I hit the buttons they never fire any of those above. The only ones that register are the Dpad up/down/left/right, center button and the back button.
I cam change the volume just fine using this code:
Java:
AudioManager mAudioManager = (AudioManager) getContext().getSystemService(Context.AUDIO_SERVICE);
int actualVolume = mAudioManager.getStreamVolume(AudioManager.STREAM_MUSIC);
mAudioManager.setStreamVolume(AudioManager.STREAM_MUSIC, 1, AudioManager.FLAG_PLAY_SOUND);But that does me no good if I cant detect the volume up/down being pressed...
The google TV remote looks like this:
Anyone know what I am missing?
App who want access of our contact list and photos are safe to use?
- By Hadron
- Ask a question
- 3 Replies
Both contacts and photos access are things that you should have to allow yourself (unless you have a very old phone), so you can just not grant the app access.
I do not find that the majority of apps ask for these, but maybe you just install a different type of app from me. I'd always ask "why does this app want that?", and if I can't see a reason I'm wary: it could be data mining, or it could just be badly coded, but either way I don't want it.
But it's not always obvious why an app might want a permission, e.g. a flashlight wanting Contacts access is a red flag, but a flashlight asking for Camera access is not suspicious because on some phones that's needed to turn the flash on. Many audio apps want phone access not to make calls but so that they can mute when a call comes in. Often apps will tell you why they ask for a permission, but if not it may require a little thought. Personally my default is that if an app asks for things I can see absolutely no legitimate reason for, even if I can deny it that access, I don't install it, but you do need to understand the range of reasons why a permission may be requested.
I do not find that the majority of apps ask for these, but maybe you just install a different type of app from me. I'd always ask "why does this app want that?", and if I can't see a reason I'm wary: it could be data mining, or it could just be badly coded, but either way I don't want it.
But it's not always obvious why an app might want a permission, e.g. a flashlight wanting Contacts access is a red flag, but a flashlight asking for Camera access is not suspicious because on some phones that's needed to turn the flash on. Many audio apps want phone access not to make calls but so that they can mute when a call comes in. Often apps will tell you why they ask for a permission, but if not it may require a little thought. Personally my default is that if an app asks for things I can see absolutely no legitimate reason for, even if I can deny it that access, I don't install it, but you do need to understand the range of reasons why a permission may be requested.
