XDA Connected

dimanche 1 mai 2016

Adoptable storage and apps updates move back the app in the internal storage

I have Android 6.0 non-rooted and installed my sdcard as internal storage (adoptable storage). I can move a lot of apps to the sdcard but as soon as these apps gets updated, the app move back to the internal storage. I thought that adoptable storage was there to say to android to use the sdcard by default!

I have searched the web and found a few blogs that explain how to tell Android that the sdcard as the default location but the command cannot be executed on my MotoG3 for security reason.

Code:

adb shell pm set-install-location 2

and i get

Code:

Error: java.lang.SecurityException: Package android does not belong to 2000

is there any other trick so the apps that are on the sdcard stay there for good?

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

How to achieve longest uptime without charge and SIM

Yea, sorry for the wierd thread name, but currently, I owne a S3 who is working as an local remote control. The crazy part is that it works for 1 or max 2 days and I need to put him to charge. I use it like once or twice a day, for like 5 minutes, so I am not sure ehat is sucking the life out of it...

There is no need for a SIM card, so is there a way to kill that part or disable it somehow, cause I believe that this is a battery drainer too.

Thanks in advance for your help!

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

OFFICIAL BUILD Lenovo K3 Note K50a40 6.0 Stock ROM Backup with TWRP v3.0.0.3

OFFICIAL BUILD Lenovo K3 Note K50a40 6.0 Stock ROM Backup with TWRP v3.0.0.3

Description :

Features:
. Fully Based on Official ROM K50a40
. Debloated
. Rooted
. Google Apps included, Multilanguage
. RAM & Battery usage optimized

Retained features:
. Two launcher styles are available by default (VibeUI and Android stock) To access them, press and hold an empty space on desktop > Preference > Default Launcher
. Pressing and holding the HOME button brings up the "Now on-tap" search, a stock feature of MM
. Dolby Atmos is installed (Not Maxx Audio)
. Colorful Settings menu like LP

What's Working:
. Everything!

What's Not Working:
. You tell me!

Instructions:
. Download the file extract it
Copy the folder "TWRP" into SD Card MEMORY
. Reboot into TWRP Recovery
. Select Wipe Dalvik cache, cache, data , system , data partision and internal memory except SD Card Memory Swipe to confirm
. Select RESTORE select storage select SD Card memory then click OK
. Select the [SLICK-S424-ROW-SHENGE] folder Swipe to restore
. Wait till it completes
. After that Reboot system… Done!

Downloads: All Links NO Mirror Plz....
Builds : LINK
TWRP Version 3.0.0.3 : LINK

ROM OS Version: 6.0 Marshmallow
Based On: Stock Lenovo OS

Version Information
Status: Stable

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

Google Keep Widget on Lockscreen not working

Hi,
System Information:
Samsung S3
CyanogenMod 11 (Android 4.4.4)
Stock Lockscreen

so i would like to use the google keep widget on my lockscreen but unfortunatly it's not working. the widget on my launcher is working so i know that the widget itself works.
when i press the "new note" button on the lockscreen widget nothing happens. i can see that a press has occured since the button flashes grey for a bit. then when i unlock my phone all i see is a white screen filling my entire phone. after a while a message appears that keep has been closed.
when i uninstall the app, use sd maid pro, restart my phone, install the app again, the widget on the lockscreen works only one time (though that time there was a help animation about new functions).

any ideas what i could do? is there a logging app that only logs a specific app?

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

OFFICIAL BUILD Lenovo K3 Note K50a40 6.0 Stock ROM Backup with TWRP v3.0.0.3

OFFICIAL BUILD Lenovo K3 Note K50a40 6.0 Stock ROM Backup with TWRP v3.0.0.3

Description :

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

Help Plz.......Bluetooth not pairing!!

I am having an a chronic bluetooth issue, which i failed to resolve. A help in this matter will be deeply appreciated.

The issue started after the February security update (at least thats what i observed). I was trying to pair my device to an external speaker (Beats Pill) and i had a hard time doing so; and i deleted previously paired devices (mainly my car bluetooth). The attempt was not successful. Then, i tried to pair the device to my car again, and i only see a code (instead of the car name) in the bluetooth search. When trying to connect, i got the message (Can't communicate with XXX device).

After multiple failed attempt, i decide to dive into Unlocking, rooting, and trying different ROMs hoping it would solve the problem. I literally flashed all available ROMs for the device with no use. I suspected it was a hardware issue, but my phone can connect to my Moto 360 with no problems.

I am puzzled with this issue to the extent of considering changing the phone. I use car bluetooth extensively as i spent much time commuting to work. If someone can help with the issue i would be gratefully. From reading around the forum, i think the system app "Bluetooth Share" is responsible for such function; could it be possible that i need a modified version of it, or maybe flash a radio of some sort??:(:(:(:confused:

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

Phone restarts automatically while turning on the feature:GCM push for greenified app

Hi, my phone is LG-Gx (Code: F310LR) with Android 5.0.2 and Xposed Framework, of which version is 83.
Problem is occurred from 2.8 to 2.9 beta2

However, I found this device will reboot itself without any notice especially when getting notifications from some apps or receiving messages from Line.
I've checked log file of Xposed,also.
But nothing abnormal information can be found except some "Fatal signal 13 (SIGPIPE), code 0" errors,and the following logs are one of them.

Code:

05-02 04:30:14.334 F/libc    (12786): Fatal signal 13 (SIGPIPE), code 0 in tid 12786 (tmp-mksh)
  05-02 04:30:14.441 I/DEBUG  (  298): [2016-05-02 04:30:14.440]
  05-02 04:30:14.441 I/DEBUG  (  298): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
  05-02 04:30:14.441 I/DEBUG  (  298): Build fingerprint: 'lge/omega_lgu_kr/omega:5.0.2/LRX22G/1506717071d79:user/release-keys'
  05-02 04:30:14.441 I/DEBUG  (  298): Revision: '10'
  05-02 04:30:14.441 I/DEBUG  (  298): ABI: 'arm'
  05-02 04:30:14.441 I/DEBUG  (  298): pid: 12786, tid: 12786, name: tmp-mksh  >>> tmp-mksh <<<
  05-02 04:30:14.441 E/DEBUG  (  298): AM write failure (32 / Broken pipe)
  05-02 04:30:14.441 I/DEBUG  (  298): signal 13 (SIGPIPE), code 0 (SI_USER), fault addr --------
  05-02 04:30:14.454 I/DEBUG  (  298):    r0 ffffffe0  r1 b646d3e4  r2 00000031  r3 b6f30ce4
  05-02 04:30:14.454 I/DEBUG  (  298):    r4 00000031  r5 b646d3e4  r6 00000001  r7 00000004
  05-02 04:30:14.454 I/DEBUG  (  298):    r8 00000000  r9 b6fac404  sl b646d3e4  fp 00000000
  05-02 04:30:14.454 I/DEBUG  (  298):    ip b6fad11c  sp be802468  lr b6ed0dd3  pc b6f30cf0  cpsr 20000010
  05-02 04:30:14.454 I/DEBUG  (  298):
  05-02 04:30:14.454 I/DEBUG  (  298): backtrace:
  05-02 04:30:14.454 I/DEBUG  (  298):    #00 pc 00037cf0  /system/lib/libc.so (write+12)
  05-02 04:30:14.454 I/DEBUG  (  298):    #01 pc 00000dd1  /system/vendor/lib/libNimsWrap.so (write+24)
  05-02 04:30:14.455 I/DEBUG  (  298):    #02 pc 0000f31d  /tmp-mksh/tmp-mksh
  05-02 04:30:14.455 I/DEBUG  (  298):    #03 pc 0000c37b  /tmp-mksh/tmp-mksh
  05-02 04:30:14.455 I/DEBUG  (  298):    #04 pc 0000dce5  /tmp-mksh/tmp-mksh
  05-02 04:30:14.455 I/DEBUG  (  298):    #05 pc 0000cf95  /tmp-mksh/tmp-mksh
  05-02 04:30:14.455 I/DEBUG  (  298):    #06 pc 00018f13  /tmp-mksh/tmp-mksh
  05-02 04:30:14.455 I/DEBUG  (  298):    #07 pc 00002d37  /tmp-mksh/tmp-mksh
  05-02 04:30:14.455 I/DEBUG  (  298):    #08 pc 0000fd11  /system/lib/libc.so (__libc_init+44)
  05-02 04:30:14.455 I/DEBUG  (  298):    #09 pc 00002e00  /tmp-mksh/tmp-mksh
  05-02 04:30:14.473 I/DEBUG  (  298):
  05-02 04:30:14.473 I/DEBUG  (  298): Tombstone written to: /data/tombstones/tombstone_05

So I turn modules on/off repeatably and find out device works fine when Greenify disabled from module list.
Then I've tested that system will reboot when turning on this feature－GCM push for greenified app.
However, I've never added Line to greenify list. How does that happen?
Last,here's my greenify list and excuse me for my poor English. I'm not a native speaker.
http://ift.tt/1Tec34O

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