TWRP issues ?

TWRP in general for me has been a mixed bag. I remember using it back when I had my Galaxy S4, and it had problems making nandroids for Touchwiz, but not CM. Typically there was a problem with the kernel. Lately with my Nexus 6 periodically it will either freeze/stall. Tonight I created a nandroid and for whatever reason when I was trying to restore it, it showed it was restored then when I tried to reboot system, the phone rebooted into bootloader mode. I could not reboot the phone it just kept cycling into bootloader mode no matter what I did.

I did not have internet, all I had was a copy of the most recent TWRP and a custom ROM zip. I recommend always keeping a copy of these files. At any rate, there's something wrong with TWRP. Initially I went into fastboot and just re-flashed TWRP. Still had problems. Then I used fastboot to erase recovery, then reflash via fastboot the copy I had then used adb pull to pull in the custom ROM into the sdcard and started up.

I still don't know what happened, but clearly there was an issue with TWRP. I may have been able to recover using the toolkit although I didn't have internet, but for those who just use the toolkit, there's definitely merit to knowing the fastboot commands and using adb pull/push.

Download from this link

[DEV] Z5 Kernel issues & related stuff + fix(es)

The following is all on stock (out of the box), unrooted kernel + ROM

(from adb shell)

Seriously Sony, what is wrong with the other half of this octa-core CPU ?

Code:

---

dmesg | grep -i error
<3>[    5.226418] bcl_handle_hotplug: Error -1 onlining core 4
<3>[    5.226714] bcl_handle_hotplug: Error -1 onlining core 5
<6>[    6.471743] subsys-pil-tz fe200000.qcom,lpass: Subsystem error monitoring/handling services are up
<6>[    6.720171] CFG80211-ERROR) wl_event_handler : tsk Enter, tsk = 0xffffffc0bb348c10
<3>[    7.359383] bcl_handle_hotplug: Error -1 onlining core 4
<3>[    7.359854] bcl_handle_hotplug: Error -1 onlining core 5
<6>[    9.994728] pil-q6v5-mss fc880000.qcom,mss: Subsystem error monitoring/handling services are up
<3>[  12.646433] bcl_handle_hotplug: Error -1 onlining core 4
<3>[  12.646764] bcl_handle_hotplug: Error -1 onlining core 5
<3>[  51.139961] bcl_handle_hotplug: Error -1 onlining core 4
<3>[  51.140351] bcl_handle_hotplug: Error -1 onlining core 5
<3>[  56.007422] bcl_handle_hotplug: Error -1 onlining core 4
<3>[  59.416963] bcl_handle_hotplug: Error -1 onlining core 4
<3>[  59.417713] bcl_handle_hotplug: Error -1 onlining core 6
<3>[  59.418682] bcl_handle_hotplug: Error -1 onlining core 7
<3>[  59.938214] bcl_handle_hotplug: Error -1 onlining core 4
<3>[  59.938477] bcl_handle_hotplug: Error -1 onlining core 6
<3>[  59.939182] bcl_handle_hotplug: Error -1 onlining core 7

---

----------------------------

And the following looks like some usb gadget or usb f_fs related issue:

http://www.serverphorums.com/read.php?12,1379459

[FIX] ? https://lkml.org/lkml/2014/2/27/38 [PATCH] usb: gadget: return the right length in ffs_epfile_io()

Code:

---

<3>[16729.608668] ffs_epfile_io(): Error: returning -512 value
<3>[16729.882382] ffs_epfile_io(): Error: returning -512 value
<3>[16732.738660] ffs_epfile_io(): Error: returning -512 value
<3>[16732.969768] ffs_epfile_io(): Error: returning -512 value
<3>[16737.264389] ffs_epfile_io(): Error: returning -512 value
<3>[16737.600648] ffs_epfile_io(): Error: returning -512 value
<3>[16738.981945] ffs_epfile_io(): Error: returning -512 value
<3>[16740.424212] ffs_epfile_io(): Error: returning -512 value
<3>[16740.777312] ffs_epfile_io(): Error: returning -512 value
<3>[16741.298607] ffs_epfile_io(): Error: returning -512 value
<3>[16741.582891] ffs_epfile_io(): Error: returning -512 value
<3>[16741.929018] ffs_epfile_io(): Error: returning -512 value

---

----------------------------

The following hints at some issues with Bluetooth headphones. Call or sound output related issues could happen (?)

Anyone had issues with stability at the end of calling ? ( https://talk.sonymobile.com/t5/Kerne...s/td-p/1022774 what phone model is this ? )

Code:

---

<3>[    6.683139] msm-pcm-routing qcom,msm-pcm-routing.41: ASoC: Failed to add route VOICE2_STUB_DL -> Voice2 Stub -> INTERNAL_BT_SCO_RX_Voice Mixer
<3>[    6.840240] msm-dai-q6-dev qcom,msm-dai-q6-sb-2-rx.191: ASoC: Failed to add route SLIMBUS_2_RX -> direct -> Slimbus2 Playback
<3>[    6.840269] msm-dai-q6-dev qcom,msm-dai-q6-sb-2-tx.192: ASoC: Failed to add route Slimbus2 Capture -> direct -> SLIMBUS_2_TX

---

----------------------------

The following could lead to some sluggishness and/or instability:
CMA (memory fragmentation ?, exhaustion ?) issues
( https://lkml.org/lkml/2014/11/3/559 )

Code:

---

<4>[    7.398189] alloc_contig_range test_pages_isolated(c7818, c781d) failed
<4>[    7.398626] alloc_contig_range test_pages_isolated(c7820, c7825) failed
<4>[    7.399363] alloc_contig_range test_pages_isolated(c7828, c782d) failed

---

----------------------------

Code:

---

texfat: fail_safe is enabled

---

https://en.wikipedia.org/wiki/Transa...AT_File_System

uh - nice ?!

----------------------------

Lol :(

Code:

---

<4>[16728.136727] _cpu_up: attempt to bring up CPU 5 failed
<4>[16728.136922] _cpu_up: attempt to bring up CPU 7 failed
<3>[16729.674537] PM: Some devices failed to suspend
<4>[16743.410363] _cpu_up: attempt to bring up CPU 4 failed
<4>[16743.410617] _cpu_up: attempt to bring up CPU 5 failed
<4>[16743.410868] _cpu_up: attempt to bring up CPU 6 failed

---

----------------------------


Come on ! You can do better than that ! :silly:

Download from this link

Galaxy Note 3 encryption and boot issues

T-Mobile Galaxy Note 3 sm-n900T, ROOTED, custom rom Darth Stalker. Tried to encrypt device causing Brick. Hard Factory reset the device now the encryption wants to load on rebooting. Put in the pin and the broken android appears and the device goes black and is bricked again. Repeat process and same results. Where do I seek information on how to remove the encryption or keep it from allowing the device to boot properly?
Many Thanks

Download from this link

Android Pay Issues

I have had reliable Android Pay experience with two phones in the past at several businesses that I visit frequently (HTC M8, and Nexus 5X), but my Nexus 6P is not doing so well.

When I try and use Android Pay, it often doesn't register at all, or acts buggy. The last time I tried using it, the Android Pay screen kept popping up rapidly as I held it on the terminal, as if it was registering over and over. At another business it took me a couple tries and moving the phone around quite a bit to get it to work, but it eventually did.

I also have tried this with two different 6P's because my first one had a screen defect, and they both had similar results.

Does anyone else have this issue? Have you have that Android Pay works better with the phone face up or face down? Or maybe if you line up the phone a certain way on the terminal?

I absolutely love this phone, but this is disappointing because my past Pay experiences have been so seamless.

Download from this link

SD card issues

Having SD card issues with certain apps, specifically titanium backup and astro file manager. When I try to bakup with titanium backup to the sd card, I get this message: "Batch Backup interrupted: Insufficient free storage space". When I try to copy something to my sd card with astro I get the message: "Device missing label Due to a bug in Android to be able to write to an SD card or usb the device must have a label. . . ."

I am able to backup with TiB using internal storage, and able to copy things to the sd card with the stock file manager.

I have tried unchecking the "mount namespace separation" option in supersu and did not work. I also added made sure to name the card on my laptop, as suggested by the Astro help message. Neither worked.

It has been the same on two g4s, with two different sd cards, one formated exfat and one fat32.

Is anyone able to use an sd card to backup TiB?

Using internal storage now but would rather use sd card because of the size of the backup.

Download from this link

SD card issues with Titanium Backup

Having SD card issues with certain apps, specifically titanium backup and astro file manager. When I try to bakup with titanium backup to the sd card, I get this message: "Batch Backup interrupted: Insufficient free storage space". When I try to copy something to my sd card with astro I get the message: "Device missing label Due to a bug in Android to be able to write to an SD card or usb the device must have a label. . . ."

I am able to backup with TiB using internal storage, and able to copy things to the sd card with the stock file manager.

I have tried unchecking the "mount namespace separation" option in supersu and did not work. I also added made sure to name the card on my laptop, as suggested by the Astro help message. Neither worked.

It has been the same on two g4s, with two different sd cards, one formated exfat and one fat32.

Is anyone able to use an sd card to backup TiB?

Using internal storage now but would rather use sd card because of the size of the backup.

Device is VS986, if that makes a difference.

Download from this link

custom lolipop roms all have bluetooth a2dp issues

Sorry if this was mentioned before,i have searched the site and found many fixes for this and read most of them for hours:D.
Basically i wanted to create this thread to discuss all possible fixes with attachments or links to possible zips to flash to fix the bluetooth bug on most lolipop custom roms.
My issues are:bluetooth connects but no audio output(meaning music) to bt headphones.What bug fixes are there without flashing roms.
What i tried:read all fixes on this site,but nothing pertaining to tab2 p3100 flash zip fix.
Is there a fix:confused:.I tried slimlp and cm12lollipop 5.1.1.......both roms still dont produce audio streaming but strangely the slimlp allows me to hear when dialing out:good:
Can someone provide me with a link to possible fixes to try.
thanks and keep up the good work keeping this tab alive for another year:laugh:

Download from this link

Help!!! I have read too much!! S5 root and rom issues!

Hello all! I am newly signed up but i have been lurking in here for quite a while now. I am like that I usually try not to post and just figure out what I need to do by research and trial and error! But lately I think i may have too much research. I have spent the last week looking up and trying to figure out what I need to do to get what I want lol.

I have a Verizon SM-G900V which has been rooted with towel root, using the flash back to NCG method. I have installed SuperSU, Flashfire, and, BusyBox.

I want to upgrade my OS to the newest version,(5.1 Lollipop I believe?) while retaining root and allowing me to wi-fi tether. What I am not sure about is how to go about this properly. I was about to install Safestrap but I am not sure it is compatible with my build which somehow magically changed to NE when I looked at my About Phone in Settings. I am actually not even sure I need Safestrap either because I have read many conflicting tutorials and info in the past week of research. I am totally new to Safestrap and have never used a custom rom before. I have however rooted my S5 and gotten it to tether fine but then I made sure never to OTA update. Recently was forced to factory restore because if what I assume where Touchwiz problems(The problems have been gone since I reset) and now I would like to see if I can upgrade my OS .

Any help would be awesome and some points in the right direction much appreciated.

Download from this link

SMS/ Phone call Issues

Hello everyone!
I installed TKHD ROM and love it except i'm having 2 very big issues!

1. Text messages. I don't get messages friends send me even when they're right next to me.
I've tried AirPlane Mode, rebooted, cleared Data and Cache of the app itself and nothing :'(
2.. Phone calls. When placing a phone call it sometimes lags before making that little chime (the one that notifies you that you're now making a call before the ringer sounds) It could sometimes take a good 5 seconds before making the call. Or, sometimes i make a call and it goes straight to VM even tho the person im trying to call is right next to me. This is also the same when people sometimes try to call me. Tho i'm not even using the phone, when thye dial it goes straight to VM sometimes.
Once again i've tried rebooting, flashing the ROM clean all over again etc but the same thing persists.

How did i install this ROM? By following the exact guide provided on the OP.

ROM: Latest version of TKHD
Kernel: Whatever comes with this ROM tho i also use SkyHigh
Recovery: Latest TWRP
Bootloader/ Modem: The latest version (OKC?)

I know some may say its my device but we'll idk about that. It only happens on this ROM.

I really like this ROM and would love to stay with it but idk how i can do that if i can't get the basics to work

Please help XDA !

Download from this link

Internet connectivity issues

Does anyone have a problem with their mobile data sometimes not working? For example sometimes when I launch Google maps and go to search it will say "cannot connect to Google maps, try again later." I then have to close and reopen the app a few times before it connects. This also happens to my reddit app where I have to refresh a few times before it detects I have a connection.

I'm currently in the US on t-mobile. I tested and have received this problem with stamina mode on and off.

Download from this link

Serious issues with CM13 on Xiaomi Mi4 - please help!

Hi! I've been reading this forum on and off for few years, but never actually posted. Hope someone here can help me sort out my issue, thanks in advance!

Basically, I've flashed a cm13 via custom recovery on my second phone - Xiaomi Mi4, and I'm having all sorts of issues with it. I bought the phone in China, and for a while
used the stock MIUI interface, but I hated all the bloated apps and weird pop-up advertising, so decided to flash. it was the first time i've attempted it, so it took some
time to figure it out :)

My two main issues with cm13:
1. It crashes and restarts two/three times daily for me. I mean, I've cleared cache, I basically have no apps on the phone (apart from few messaging apps and facebook).
Is it just because it's an early cm13 build, or it's a nature of custom roms? I'm wondering if switching to a snapshot cm12 build would be better? I don't really care for
android 6 features on this phone that much, I just want a stable experience.
2. The charging became uber slow, painfully so. On MIUI it'd charge to 100% in about 3 hours or so. On cm13 it takes 3-4 hours to get to 30-40%! Never seen anything like
this. Also, if the battery depletes to 0%, the phone wouldn't turn on, even plugged in for charging. It'd turn on after an hour or two into the charging process. Seems weird,
as every other android phone I've owned previously would turn on even with 0% battery if I'm plugged in.

Anyone else experience any of the listed issues? Is it just an early build, or I've done something wrong in the flashing process? I really just want a stable simple os, no advanced
features or whatever, just need it to work :)

Thanks!

Download from this link

Shallow ibernation - issues or misunderstanding ?

Hi,
I'm using a Nexus 6P with stock MM 6.0.1 + root + xposed and using the paid version of greenify (currently testing v2.8b10)

(1) I'm trying to figure out how shallow hibernation works, what is the philosophy behind it compared to "normal" hibernation because it seems to me that the apps that I hibernate are more often awaken under shallow than normal hibernation, that their service seems to still be running in the background.

(2) In the description of shallow hibernation, it says that shallow-hibernated apps will be woken for a brief period of time periodically: Why and what does this mean exactly? by periodical wakeups are we not loosing the whole purpose of hibernation?

(3) Also with shallow hibernation, it seems impossible to cut some unwanted wake-up paths because greenify doesn't indicate which path has awaken an app. While in normal hibernation, greenify specify which "action" has awaken an app against your will so you can cut this specific wake-up path (for instance I have a stupid app that is being awaken everytime I make a phone call - but I need this app only when I manually launch it)

Download from this link