jkbuha
100+ Head-Fier
- Joined
- Jan 2, 2014
- Posts
- 284
- Likes
- 401
Sounds a lot (exactly the same perhaps) as my external_sd1 issue with 3.4.1 (further up the page). I even went as far as popping the card into sd1 after it had booted and settled down, and got the same freeze-up (it was fine trying this unorthadox approach in sd2, with files being happily read). Cannot be blamed on the card itself as I'm back on the stock setup with the same two cards and it's playing fine (and it shuffles across the two cards without hiccups too).
I have 2x 400GB cards fully loaded in both slots, and haven't experienced this before, nor indeed anyone on the 4pda forums (and trust me, they're a dedicated community). However, I do a lot of external card cleaning, so maybe there are some errors on your card. Also note that the kernel treats SD1 differently to SD2 (both custom and vanilla, the latter just doesn't use specific schedulers/scripting for it) so it may be something related to the new schedulers or script optimisation.
Do this:
1) Shutdown and eject both cards. Insert them into a laptop and disk check them. Fix any errors. Incidentally - what filesystem do they use?
2) If symptoms still persist, then (and only then) try changing the SD1/SD2 scheduler algorithm, let's see if this is the issue. You'll need to have root and a kernel manager program like Adiutor or SmartPack or EX. Change the external scheduler to row/deadline/noop and see if the situation improves.
3) If symptoms still persist nonetheless, then (and only then) should you try to disable the init.d scripts. You'll need to reboot into TWRP, mount system and rename/delete the init.d folder or the 30FSTweak/40EXT4Tweak or the renice scripts. Reboot and see if the situation improves.
It's highly likely that one of the 3 steps above will solve the issue.