LightBlog

lundi 4 avril 2016

Adding permissions to hooked app?

Hi everyone!
In my Xposed module I modified hooked package (SystemUI) so that it needs some additional permissions that it normally wouldn't use (especially "android.permission.RECORD_AUDIO" and "android.permission.MODIFY_AUDIO_SETTINGS"). It seems that having both those perms in module's manifest is not enough. Any ideas how to grant them to SystemUI?


from xda-developers http://ift.tt/1UQOYvr
via IFTTT

Xiaomi Mi5 (Video Review) 5.15 Inch FHD, 3GB/32GB ROM, NFC, Snapdragon 820 - s7yler

Full Review


Full Unboxing


Camera Test Samples: http://ift.tt/1RXS9AR
Stagefright Vulnerability: No (Tested 04/04 2016 / Build MRA58K / MIUI 7.2.8.0)
AnTuTu Score: 114100
Geekbench 3 battery test: http://ift.tt/200Mvhp

Specifications:
- 5.15 Inch 16 LED light screen, 1920*1080 pixels
- 3D-Glass housing
- Qualcomm Snapdragon 820 1.8GHz Quad Core
- GPU Adreno 530 510MHz
- Front fingerprint scanner
- 3000mAh battery, fastcharge 3.0
- Built-in NFC
- 600Mbps 4G+ Download-Speed, VoLTE
- 3GB RAM + 32GB UFS 2.0 ROM
- 16 MP 4-axis OIS maincamera + 2µm-pixel 4 MP frontcamera
- USB Typ C, Bluetooth 4.2, IR Blaster
- MIUI 7 (Based on Android 6.0 OS)
- Supports 2G & 3G & 4G LTE Network
- Network: GSM 850/900/1800/1900MHz, WCDMA 850/900/1900/2100MHz, FDD-LTE B1/B3/B7




from xda-developers http://ift.tt/1RXSa7G
via IFTTT

Battery Issue (?) Weirdest thing ever. HELP!

Hey guys, I've been having a really weird issue for a couple of days now. For your better understanding I'll list the things that I did with my d855 (Including some stupid ones)

1. I was on a cm 13 nightly rom, I was getting pretty bored so I decided to try out the fulmics 4.2 . So, I did. I flashed it without any hiccups. Everything seemed to be going fairly well. (I did make a TWRP backup and i also checked md5 of the zip file. It matched out)

2. I installed all of my apps that i use, Set up my wallpapers, nova, etc. I used it for a whole day and i noticed that the sot improved quite a bit from cm 13.

3. I'm in my bed, obviously not sleeping, you know how we do. And an incredibly stupid idea came to my mind. I thought "Hey! It's 4'o clock in the morning and i have school tomorrow, BUT WHO GIVES TWO ****S?! why not try out the lg g4 camera app ?!? Now, I had tried it before a long time ago, The camera didn't work, But the phone definitely did. So I wasn't paying too much attention on what the thread said about which version of android it was for. And just like a complete moron i downloaded the thing and proceeded to place the apk and 'libs' folder on my phone. I did give them proper permissions.

4. After that I went ahead and rebooted my phone. It booted just fine. I tapped on the camera app and it gave me an error. So i rebooted again, same as last time it booted up just fine but the camera didnt seem to work. Then suddenly it just shut down and then the lg logo flashed. It booted to the homescreen just fine. Then it turned off again and rebooted again. This loop started to go on and on forever.

5. So I decided to boot into twrp and wipe my art/dalvik cache and normal cache. Then i pressed on reboot. This time the phone didnt turn off, it optimized all of my apps. It took a while but i was on my homescreen and it didnt turn off. So I went ahead and opened up root explorer, located to where i pasted the camera, deleted the libs folder and the apk and also renamed my original camera app from .bak to .apk . Then I rebooted again, and it started the weird looping thing once again.

6. I realized that it boots up just fine if it's plugged in. But it seemed to turn off after 5 mins or so even when plugged in. I thought I messed up my rom or something so i decided to check by entering into recovery. But the result was the same. It just turns off. So since it was turning off even when i was in recovery i thought it was a faulty battery.

7. So i busted out my ZTE pocket wifi router and proceeded to take its battery and hold it up against my d855's battery pins with my finger. (Probably not safe) And the phone seemed to work just fine. I could use it for days without any issues. So at that point im like 110 percent sure its a faulty battery. Fair enough.

8. But, just to be certain i thought lets try doing a factory reset and flash the fullmics again. Result = Wank.
Then I wiped the cache again. Result = Wank. Then i decided to restore to the backup i made earlier that day. Result = An oreo to be given to the one with the correct guess.

9. At this point i wasn't 110 percent sure that it was a faulty battery. I KNEW it was a faulty battery. I was feeling it in my left testicle. So I decide to finally sleep cuz you know, gotta get some sleep, got a big day ahead of me tomorrow. Cuz I dont have my phone. So, I prepare myself and go to sleep.

10. The next day I decide to give it one last shot. I was thinking about wiping it clean and restoring to the backup again.

11. This is where the interesting thing happens. Bear in mind, I am NOT plugged in. Im on my G3's battery. I hold down the volume down and power button. The lg logo shows up. I let go of the buttons. I press them again. The white factory reset screen shows up. Now, I left my phone on that screen for legit 20 mins ladies and gentlemen and it didnt turn off once. But as soon as i click yes for twrp to launch the phone turns off before the twrp logo can show up. I tried the same thing with the ZTE battery as well, and it worked just fine. Only this time it actually booted to twrp. And it booted into the system as well.

Now, wtf is this? Wouldn't the phone turn off in the factory reset screen if it was faulty? And if the battery isn't faulty, then why does it work with a different battery but not with the lg one?

Now, My question to you guys, WHAT SORCERY IS THIS?

Help me out people. Expert help needed. TIA

*sigh* :(


from xda-developers http://ift.tt/1RXS8N8
via IFTTT

[ROM][togari][NIGHTLY] [AICP] aicp_togari_mm-11.0-NIGHTLY-20160331 upgrade failed

Hi,
I tried to upgrade from AICP LP 5.1.1 to AICP MM 11.0 NIGHTLY-20160331 and after upgrade the device reboots and loops forever in SONY Boot Logo.

Device Details:
============
Device: Sony Xperia Z Ultra C6802
Bootloader Unlocked: Yes
Rooted: Yes
Firmware Used: AICP Togari LP 5.1.1 Nightly Build 20150805
(Working one before the upgrade)

Upgrade Steps:
============
I had copied the aicp_togari_mm-11.0-NIGHTLY-20160331.zip to external sd card and reboot the device to recovery mode and choose update to upgrade the firmware. (I forget to wipe the dalvik cache).

Please help me in steps for restoring the device to previous version (LP 5.1.1) which is working fine.

Thanks

- selvapsk


from xda-developers http://ift.tt/200Mr0V
via IFTTT

Snapchat encryption code

I forgot to screenshot a few pictures off snap chat. [Latest version 9.0] However I have managed to find all the no media files and have transferred them to my desktop [running windows 10] My question is if anybody could tell me how to get the encryption key ASAP as I need to access these photos by the end of the day. Thank you.


from xda-developers http://ift.tt/1RXS4Nx
via IFTTT

LG L90 D415 accidentally I changed the "bootloader"

I have a LG L90 D15 and accidentally I changed the "bootloader"; but now I can not turn, I can not even access the "S\W Update" mode.

I have the file ".kdz" but nothing yet, because I've put volume + and connect the USB cable to the PC, and nothing.

Some help me.


from xda-developers http://ift.tt/200Mnyh
via IFTTT

[Q] Performance/battery life on stock 6.0.1? Currently on 4.4.2 [Wifi]

Hello

I am currently on stock rooted rom on 4.4.2. I never bothered updating since it served my purposes of watching movies.

I need to gift my nexus to someone I know, so wanted to update and unroot before giving. Would anyone please tell me how the performance and battery life is on 6.0.1 stock (will be used unrooted most likely)? I have the Wifi 2013 nexus 7

I understand it may be too obvious of an answer butI searched the thread but could not find an answer. Been away from xda for a long time. Good to be back! :)


from xda-developers http://ift.tt/1RXS0gM
via IFTTT