Thursday, September 1, 2016

Spontaneous issue no longer allows /cache or /data to mount

So last night, my kindle was working normally with my self-compiled CM13 build (7/1/16 version), 7/16/16 opengapps, and other miscellaneous tweaks I use to refine my experience. Anyway, I was using my device normally and set it down to charge earlier. When I came back to it, I noticed it was booting CM. A few minutes later, I see that it's rebuilding cache for all the (system?) apps. I check back in a little bit later, and it reboots again. Suspecting an issue, I typed fastboot -i 0x1949 erase cache to try to erase the cache, and it doesn't work. The terminal window just hangs until I unplug the device. I tried rebooting into TWRP before doing the cache wipe, and it ends up not fully booting into TWRP. After that /cache wipe command fails, I suspect that my /sdcard or /data partitions are full somehow, so I kick the device into TWRP via fastboot -i 0x1949 oem recovery. TWRP boots that time, but asks if it can remount /system as R/W, so something's amiss. I plug the kindle into my Ubuntu machine, and I don't see any files or anything. I don't even see the "Internal storage" icon that usually shows up. I find it really baffling. I try to browse /sdcard from TWRP's file manager, and nothing shows up there either. I check the TWRP log, and it says "Failed to mount '/data' (Invalid argument)" and "Unable to recreate /data/media folder." For /cache, it says "Failed to mount '/cache' (Invalid argument)". Note that I didn't flash anything or otherwise modify the device leading up to this. I checked the battery via TWRP, and I have a decent level of around 48%. The kindle's 3 years old (got it in 2013 as a birthday present, so I know it's at least 3). Any ideas, or is this the last leg for my 8.9"?


from xda-developers http://ift.tt/2bJLEOz
via IFTTT

Guide: edit build.prop to display all apps in dual window

This article is taken from the following post (which will require translation): http://ift.tt/2bF0dpf


By default enabling dual window only allows you the option to add a handful of apps. By modifying 5 lines to =true instead of =false you will be able to add ANY app installed on the device to the dual window. I've tested this on my H901. I'll also include a copy of the edited build.prop but I'm on V20J.....if you are not then you are probably better off modifying your own build.prop.

What does this require?

1) adb pull /system/build.prop
2) edit the build.prop to match below
3) do an adb shell, su to root and run "mount -o remount,rw /system" to make your system read/write instead of only read only.
4) rename /system/build.prop to build.prop.bak
5) adb push your modified build.prop to /system
6) type "diff /system/build.prop.bak /system/build.prop" in adb shell and verify the only changes are the 5 expected.
7) reboot. If for some reason it doesn't boot don't panic...you can get into twrp and copy the build.prop.bak back over the modified build.prop then reboot and start back at step 1.
8) press the app switching button and select the "dual window" button....you will now see you can scroll through ALL your apps to put in either the top or bottom window.

When you edit your build.prop the lines will NOT be in the same order as the example. You will need to do a search on each line so you can modify it. If you use the premodifed file attached make sure you remove .txt from the end of the filename which was required to attach it to the post.


Attached Files
File Type: txt build.prop.txt - [Click for QR Code] (13.0 KB)


from xda-developers http://ift.tt/2bF0PeJ
via IFTTT

Unlink Bluetooth volume control marshmallow

Hi everyone,

after multiple trys for finding something towards the mentioned topic, i want to ask the xda community:
Is there any way to unlink bluetooth volume from androids media volume in marshmallow in CM or AOPS based roms?
The problem is for example while listening to audiobooks in the evening. The lowest volume is just too loud.
Roms from multiple manufacturers (Samsung, OnePlus, HTC) have marshmallow roms and the volume levels are not linked to each other. There must be a way for powerful roms like cm or derivates of it.

Any suggestions?


from xda-developers http://ift.tt/2bF1axR
via IFTTT

Wednesday, August 31, 2016

Unlink Bluetooth volume control marshmallow

Hi everyone,

after multiple trys for finding something towards the mentioned topic, i want to ask the xda community:
Is there any way to unlink bluetooth volume from androids media volume in marshmallow in CM or AOPS based roms?
The problem is for example while listening to audiobooks in the evening. The lowest volume is just too loud.
Roms from multiple manufacturers (Samsung, OnePlus, HTC) have marshmallow roms and the volume levels are not linked to each other. There must be a way for powerful roms like cm or derivates of it.

Any suggestions?


from xda-developers http://ift.tt/2bJGVws
via IFTTT

Motorola RAZR m

My motorola 4.4 RAZR m is on soft loop how do I install a 4.1 version in other to upgrade it to marshmallow

Sent from my XT907 using Tapatalk


from xda-developers http://ift.tt/2bDI9h5
via IFTTT

No mobile data and unknown IMEI after flashing ARHD

I've successfully flashed ARHD, and I have bootloader unlocked with S-ON

After booting and trying to use the phone, I don't get signal and my IMEI appears as unknown.

Some info that might be useful:
Phone bought in Mexico, Telcel.
cid HTC__332
Bootloader unlocked
S-ON
ARHD installed based on Android 6.0

Thanks in advance, guys.


from xda-developers http://ift.tt/2bDWvJo
via IFTTT

Get ya stats out :D

Since upgrade to official MM and a immediate factory reset after, battery is no longer a issue..
I can completely forget the battery...
Yesterday , I took my phone off charge, after its first full charge after upgrade..@11.00 am , that's 21.30 hrs and still 35% left, moderate use.
Approx 5.30 hrs screen on time and approx 4hrs to go ;)
Stats coming soon ....
.
. Get ya stats out ...now !
:)
PS, lots of bricked threads popping up , check my signature :good:


from xda-developers http://ift.tt/2bDIGzr
via IFTTT