FORUMS

What Are the Best Looking Apps on Android?

As more developers are updating their apps with Material Design elements, we’re … more

Cyngn Explained: Who’s Cyanogen, What’s Cyanogen OS?

While Cyanogen, Inc has been the source of many headlines lately, there … more

Verizon Moto X 2014 Receives Root On Kitkat 4.4.4

The Verizon Moto X 2014 has finally received root, albeit only on Kitkat 4.4.4 … more

Android 5.1.1 Released, Google Cell Service – XDA TV

Android Lollipop 5.1.1 has been released. That and much more news is covered … more
Post Reply Subscribe to Thread Email Thread

External SD card and G PAD... try to clarify

25th November 2014, 08:25 PM |#131  
Senior Member
Flag Cambridge
Thanks Meter: 242
 
More
Quote:
Originally Posted by tskisiu

I have not had a single "bad removal" when running on a RedKernel and CM11 for 2 months (as tested with SD Card Monitor). RedKernel: http://forum.xda-developers.com/lg-g...ernel-t2856297
When I flash a "vanilla" kernel from any recent CM11 the errors are immediately back, usually when the tablet stays in deep sleep. Unfortunately, I have had also this issue with the new Lollipop from this thread: http://forum.xda-developers.com/lg-g...rx21m-t2941207

Actually the RedKernel is very good. I use v9 because on v10 I had strange battery drain during sleep. The only problem I have encountered is related to WiFi switching: when I move to a different network it does not re-connect automatically and the WiFi is unresponsive. The only way to fix it is to switch to the Airplane Mode and back., but while it works fine with the known networks it has some problems scanning for the new ones. It can be quite irritating while travelling for instance.

p.s. my sd card is exFAT formatted

Are you using 4.2.2 base or 4.4.2? I have noticed that if I am on 4.2.2 base then no matter what ROM/kernel I am on I don't get any bad unmounts of the SDcard. As soon as I switch to 4.4.2 base files then the unmounts start happening. This is annoying because I want to use redkernel with 4.4.2 base so I don't have the brightness issues. Any suggestions welcome!
 
 
25th November 2014, 08:33 PM |#132  
Junior Member
Thanks Meter: 3
 
More
I am on 4.4.2 base CM11 M12 snapshot + redkernel r09 + exfat sd card
15th December 2014, 02:46 AM |#133  
muiriddin's Avatar
Senior Member
Flag Mid-Atlantic
Thanks Meter: 130
 
More
Okay, my ext4 approach just crapped out for me on stock. I did run for a long time without having the bad removal storm, but I have now had one. My best approach at this time is to flash a rom and run either redkernel (in 4.4 based roms) or redkernel/manikernel (in lollipop roms). I have lots of testing without a problem with 4.4 and redkernel. So far with Lollipop I have tried both redkernel and manikernel but I obviously do not have as much time as redkernel on 4.4 (it hasn't been out as long).



I still hope that LG will release a new lollipop build which solves this issue, but the roms I'm running with the kernels I use seem to make the problem go away, stock just doesn't work well with sdcards from what I can tell. Yet I know it isn't a hardware problem since the problem did not occur on 4.2 and does not occur for me on slimkat with the redkernel...



If anyone has bad removal problems on lollipop with either one of these kernels please post here...
15th December 2014, 08:55 PM |#134  
Deltadroid's Avatar
Senior Member
Thanks Meter: 1,390
 
More
Just to bring the conversation over to this thread..

When I select a few gigs of video, it usually takes about 30 minutes or so to copy. While it's copying, the tablet goes to sleep after a few minutes and that is when the copy fails due to disk unmount.
The Following User Says Thank You to Deltadroid For This Useful Post: [ View ]
16th December 2014, 04:59 PM |#135  
muiriddin's Avatar
Senior Member
Flag Mid-Atlantic
Thanks Meter: 130
 
More
Quote:
Originally Posted by Deltadroid

Just to bring the conversation over to this thread..

When I select a few gigs of video, it usually takes about 30 minutes or so to copy. While it's copying, the tablet goes to sleep after a few minutes and that is when the copy fails due to disk unmount.

Okay, I can try something like that. I have been moving data around lately and the screen has been going off, however I typically am moving a bunch of small files that collectively add up to a large amount of data...

Additional Note:

The key thing I have been trying to reproduce is a scenario which results in a "bad removal" from the sdcard monitoring tool. From my own personal observations a bad removal will often result in a mount unmount storm occurring which then can put the tablet in a "bad state" as to sdcard usage. This "bad state" is typically a situation in which the card shows as mounted, but no files are visible and its capacity is listed as 0 in size. In addition I have also observed a situation in which the card could no longer be unmounted without rebooting the tablet itself.
Last edited by muiriddin; 17th December 2014 at 02:54 PM. Reason: added additional note
20th December 2014, 02:10 PM |#136  
Senior Member
Thanks Meter: 70
 
More
I was investigating the problem and I think I found the cause and the solution.

The cause:
According to my findings the bad dismount while deep sleeping is caused by the C3* state (Power Collapse) which is the deepest sleep state.
While in this state the sdcard check routine timeouts and a bad dismount occurs.

The solution (root required):
When I had the Nexus4 I remember the C3 state was off by default and enabling it caused issues in some cases...
So I tried to disable it on the GPad and this cured the bad dismount.

This may lead to a little higher battery drain while in standby.... the device deep sleeps just fine anyway.

Attached to this post you'll find the script (remove the .zip extension after the download) you need to place in system/etc/init.d (if your kernel supports init.d... stock one doesn't)... alternatively you may use Script Manager and execute the script with ROOT privileges.

I tested this on my GPad running Mahdi 2.9 ROM (KK) and mani.Kernel... It SHOULD work on any ROM/KERNEL combinations....

* Infos about C-States may be found here.

Merry Xmas!
Attached Files
File Type: zip 01externalsdfix.zip - [Click for QR Code] (676 Bytes, 134 views)
The Following 3 Users Say Thank You to domg73 For This Useful Post: [ View ]
20th December 2014, 03:59 PM |#137  
Deltadroid's Avatar
Senior Member
Thanks Meter: 1,390
 
More
I fixed my unmount problem by formatting my sdcard with cwm recovery. I had no idea my card was exfat, because it was mounting ok and it seemed to work ok most of the time.. But, it caused major instabilities in the system overall.

It seems to make a big difference which program you use to format the card with.
24th December 2014, 01:18 PM |#138  
muiriddin's Avatar
Senior Member
Flag Mid-Atlantic
Thanks Meter: 130
 
More
Quote:
Originally Posted by domg73

I was investigating the problem and I think I found the cause and the solution.

The cause:
According to my findings the bad dismount while deep sleeping is caused by the C3* state (Power Collapse) which is the deepest sleep state.
While in this state the sdcard check routine timeouts and a bad dismount occurs.

The solution (root required):
When I had the Nexus4 I remember the C3 state was off by default and enabling it caused issues in some cases...
So I tried to disable it on the GPad and this cured the bad dismount.

This may lead to a little higher battery drain while in standby.... the device deep sleeps just fine anyway.

Attached to this post you'll find the script (remove the .zip extension after the download) you need to place in system/etc/init.d (if your kernel supports init.d... stock one doesn't)... alternatively you may use Script Manager and execute the script with ROOT privileges.

I tested this on my GPad running Mahdi 2.9 ROM (KK) and mani.Kernel... It SHOULD work on any ROM/KERNEL combinations....

* Infos about C-States may be found here.

Merry Xmas!

Using what you said (and a helpful kernel tuning utility) I've done the following.

1. revert to stock 4.4.2
2. root
3. install sdcard monitor app
4. using Faux123 Kernel Enhancement Pro disable c3 and set it to always disable this state on boot.

And now I'm waiting to see if stock will crap out again with this change. What you wrote above makes more sense than any of the other theories on this issue that I've read and I knew it was somehow related to sleep and/or power. I never thought to disable one of the sleep states. Thanks for pointing me in a new direction!

-- Added stuff here later --

Okay your script will error out on the stock kernel however you can simply comment out the lines that cause errors and then it does work. This does cause battery drain while the tablet is idle, however it does seem to stop the sdcard from having a bad removal. If you must run stock this would solve the issue, although you would still need to root and run the script after each boot (either manually or via some tool).

The modified script should simply comment out the lines for cpu1-cpu3 as shown below:

echo "$C3" > /sys/module/pm_8x60/modes/cpu0/power_collapse/idle_enabled
#echo "$C3" > /sys/module/pm_8x60/modes/cpu1/power_collapse/idle_enabled
#echo "$C3" > /sys/module/pm_8x60/modes/cpu2/power_collapse/idle_enabled
#echo "$C3" > /sys/module/pm_8x60/modes/cpu3/power_collapse/idle_enabled

leave the rest of the script as is...

idle_enabled does not seem to exist for cpu1-cpu3 in that directory.
Last edited by muiriddin; 30th December 2014 at 06:02 PM. Reason: Fixed First paragraph which was based upon my pre-coffee state (and rated a D- in early morning reading comprehension)
The Following User Says Thank You to muiriddin For This Useful Post: [ View ]
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes