yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Smokeey:
Well obviously the media scanner is stuck. It might just be CM9. Clear cache and let it repopulate your media.

Return with results.
[Samsung Galaxy Nexus] Mitchmoney:
I had the same thing and realized that I was losing the battery after updating Google chrome..

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] crossover37:
I removed Chrome before and it still ate battery. I think it was the v8.2.1 Popcorn Kernel. I don't have that issue with the kernel bundled with CM9 BUT the Kernel bundled with CM9 isn't as fast or fluid.

Should I change my governor settings for best performance? If so, to what?
[Samsung Galaxy Nexus] KWKSLVR:
On previous devices where I had Media Scanning running rampant like that, the easiest fix that worked every time was to backup the data on my internal and external SD cards (internal in our case), format them both then copy my data back over.
[Samsung Galaxy Nexus] mackrox:
Any luck on this? I have two batteries and I am having trouble making it 8 hours. The extended & Standard battery.
[Samsung Galaxy Nexus] LocoTSX:
That kernel may not run well with CM9. I know the frankokernel horribly reduced my battery on gummynex and I was also getting a lot of media use in the stats. I switched back to lean kernel and its all good now.
[Samsung Galaxy Nexus] G0belet:
I had that problem once on my Nexus One. It stemmed from a corrupt jpeg file on my storage, it was a picture I took. The media scanner choked on that, and so did Windows when I transferred it back to my computer. As soon as I removed the file things got back to normal.
[Samsung Galaxy Nexus] mackrox:
I've ran every kernel, and still get bad performance :(
[Samsung Galaxy Nexus] crossover37:
Yeah. I hope that the next update from Google makes things smoother with better frame rate transitions for graphics and also that battery management is improved.
[Samsung Galaxy Player 4.0, 5.0] tradeJmark:
For those of you coming into this post looking to have Ubuntu on your Galaxy Player, it looks like we have found an acceptable solution.

First of all, due to our single-core processor, it doesn't look like we'll ever have the official Ubuntu for Android that is on the Ubuntu Site.

However, it has been tested, and you can use this app on your Galaxy Player to actually run Ubuntu, with either a Gnome or LXDE desktop. You use a terminal emulator to get it started, and after that, your terminal emulator becomes a terminal for your Ubuntu, and you can access the Desktop through vnc to localhost:5900. You can also access the gui from any computer with vnc using [your.galaxy.players.ip]:5900.
[Samsung Galaxy Player 4.0, 5.0] dunca123:
http://xdaforums.com/showthread.php?t=1502862

As far as I know, this is it.
[Samsung Galaxy Player 4.0, 5.0] m@thw1z@rd:
Possibly but unlikely since this seems to be advertising the large amount of power in multi-core phones while the Galaxy Player is a single core. However I have the Ubuntu that dunca123 suggested installed on mine and it does work fairly well although not extremely so. Maybe about as well as any lightweight linux distro would work on a single core with not a lot of RAM (crunchbang being the exception because that will run on just about anything)
[Samsung Galaxy Player 4.0, 5.0] EcHoFiiVe:
Im able to run BackTrack 5 on my SGP just fine. Its 5.0 US and as we all know, BT5 is a linux distro based on GNOME. Hoped I helped in some way.
[Samsung Galaxy Player 4.0, 5.0] SirRhor:
Any links with instructions toy could provide please?

Sent from my YP-G70
[Samsung Galaxy Player 4.0, 5.0] tradeJmark:
This seems like an ok solution, though i could do without having to use vnc.
[Samsung Galaxy Player 4.0, 5.0] EcHoFiiVe:
For backTrack5? I'd be happy to give you what you need. You need 3.25 on your SGP and ill link the files and you need to be rooted. Ill tell you the rest when you reply.
[Samsung Galaxy Player 4.0, 5.0] SGP4isokay:
After unboxing my SGP 4.0(USA) I applied Steve's kernel which I cannot recommend enough. Anyway, I was so happy with it that I decided to try Klin's Klassic ROM. In Klin's instructions he stresses to make a backup via CWM prior to flashing so I booted into CWM, had my device create a backup, then rebooted. I ended up in bootloops like others have experienced.

Before anyone flips out on me, yes I was fully aware that Steve said, "NOTE: Don't use ROM Manager". I did not use the Rom Manager app. I booted into CWM and felt I was safe in doing so. No experimentation took place. I made a backup to the internal storage and rebooted.

Anyway, I was getting bootloops so I tried the fix in Hyperrunner's thread. I followed the instructions. The first portion of his recommended fix did not work so I proceeded to step two where I included the pit file and followed the instructions verbatim. I was stoked when I saw that his steps meshed with what I was seeing on my screen to include the booting into Recovery Mode. I Wiped Data and Wipe Cache. The data wipe got rid of a bunch of errors. The cache wipe did not.

I am now stuck in Android system recovery <3e> with the following errors:

-- Copying media files...

E:failed to mount /dbdata (Invalid argument)

E:copy_dbdata_media:Can't mount /dbdata

your storage not prepared yet, please use UI menu for format and reboot actions

Meida files copy failed.

# MANUAL MODE #

-- Applying Multi-CSC...

Successfully applied multi-CSC.

E:failed to mount /cache (Invalid argument)

E:Can't mount /cache/recovery/recovery_kernel_log

E:copy_kernel_file :: Can't open /cache/recovery/recovery_kernel_log

E:failed to mount /cache (Invalid argument)

E:Can't mount /cache/recovery/log

E:Can't open /cache/recovery/log

E:failed to mount /cache (Invalid argument)

E:Can't mount /cache/recovery/last_log

E:Can't open /cache/recovery/last_log

E:failed to mount /cache (Invalid argument)

So I'm stuck in system recovery with the options to

:

reboot system now(Done several times)

apply update from sdcard(Have not seen that discussed)

wipe data/factory reset(Did that. It cleared some errors.)

wipe cache partition(Cache errors persist)

I cannot get the device to Download Mode, into the mode with the PC and phone), or connect via Odin. I saw this thread about getting back to download mode but it is for the 5.0 and I'm looking for help as to what my next step should be.

Thanks for your time.

[UPDATE]

1. I purchased a jig(link further down) and the jig got me into "Downloading..." mode

2. Once in download mode I flashed a ROM and pit file as from Hyperrunner's thread(again, link further down)

3. Using Yaph's experience on AnythingButIpod I flashed Steve's kernel again and gained access to CWM

4. I tried using the restore I was making before the bootlooping started and it went through but I am still stuck in CWM

[UPDATE 2]

All fixed. Big thanks to everyone, especially Zaclimon!
[Samsung Galaxy Player 4.0, 5.0] klin1344:
Adb should work in recovery; type Adb reboot download and you should be in download mode. In download mode you have to flash zaclimon's full recovery rom for the 4.0.

Link: http://xdaforums.com/showthread.php?p=23290249

Sent using Tapatalk
[Samsung Galaxy Player 4.0, 5.0] SGP4isokay:
Thank you. I've never worked with Android Debug Bridge but it looks drop dead simple from Androidsamurai's guide, so I'll give it a go along with Zaclimon's work. Much appreciated.
[Samsung Galaxy Player 4.0, 5.0] minimeofctown:
have you flashed the stock recovery for the 4.0? or did you already fix it?
[Samsung Galaxy Player 4.0, 5.0] SGP4isokay:
I haven't flashed anything yet. I just downloaded the guide, the All In One tool, and the Google USB drivers. I'm trying to load the drivers now.
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
For ADB you need samsung drivers not google's

Link to samsung drivers: http://xdaforums.com/showthread.php?t=961956
[Samsung Galaxy Player 4.0, 5.0] SGP4isokay:
Thank you. Unfortunately my Windows XP machine is not recognizing my Galaxy Player as anything other than a two drive mass storage device(with the "Safely Remove Hardware" icon in the system tray). The command adb devices returns

With nothing following.
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
Ensure that Usb debugging is enabled: settings-->applications-->developpment-->enable USB debugging.

also ensure that you don't turn on USB mass storage (which means the little android remains green.) Then try again. (Before trying again do this command: adb kill-server.
[Samsung Galaxy Player 4.0, 5.0] minimeofctown:
youll have to have usb debugging on. it might give you that at first. just input the command again.
[Samsung Galaxy Player 4.0, 5.0] SGP4isokay:
Yeah, I saw that I needed debugging on when I started going through Androidsamurai's guide. I neglected to enable that before I tried making a backup and now there appears to be no way to enable it since I am stuck in "Android system recovery". A little Googling leads me to believe that any effort to recover at my device hinged on that being enabled.
[Samsung Galaxy Player 4.0, 5.0] minimeofctown:
might wanna invest in one of these(; http://www.ebay.com/itm/Micro-USB-J...ccessories&hash=item3372a56243#ht_1175wt_1141

mine came in. im getting it tomorrow hopefully. so if you wanna wait until i test if it works then ill let you know if its safe to buy
[Samsung Galaxy Player 4.0, 5.0] SGP4isokay:
Thanks! I'll wait for news from you. I'm in no rush and this experience has been a pretty decent learning opportunity.
[Samsung Galaxy Player 4.0, 5.0] Vilai:
so i have the exact same problem BUT i can access download mode and it is recognized by odin, the next post says to use the zaclimon's recovery rom but it is closed for US. also use ADB but idk if that would apply to my case and if so what do i do exactly because for someone like me its very confusing.

Thank you for any help.
[Samsung Galaxy Player 4.0, 5.0] SGP4isokay:
I purchased a Jig from here(USBJig). With it I was able to get back to the "Downloading..." screen(Android with shovel). I plugged the USB cable in and Windows XP recognized my device. So...hooray! :D

Indeed, Zaclimon's rom is a No-Go. I have been following Kwipper's "[STOCK ROM]" but it says that, "Your phone should be rooted prior to doing this." I did root my device but I'm so hesitant to do anything at this point that I wanted to check with XDA before I do anything.

I'm going to drop a note in Kwipper's thread and ask for guidance. Vilai, I will update you as I progress. Any other input from XDA posters is obviously welcome.
[Samsung Galaxy Player 4.0, 5.0] Vilai:
i actually did that one too a no go for me :( just gonna wait out what i see here in the coming days.
[Samsung Galaxy Player 4.0, 5.0] SGP4isokay:
I found someone who has recovered from these errors but I don't know how to replicate his fix being that this is my first experience with Android/Odin. I will try to contact him and see if I can get a step-by-step repair process.

Here is his last post on the thread I linked just above:

He mentions at the top of his post that he successfully applied Steve's Kernel to regain Clockwork Mod recovery access so I tried that and now I have CWM working.

[EDIT]

I tried to restore my device from the backup. It seemed to go through successfully(the restore process) but then it just keeps booting into CWM regardless of what I do.

Meh, progress. =- D
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
I've decided to remake the rom for the US (I will not include bootloaders this time) just /cache /system /dbdata and zImage only. I will post it later today. (your error is the recovery can't mount /cache so reinstall it would work.) I will send you a PM for testing if you want before sending it to the recovery thread.
[Samsung Galaxy Player 4.0, 5.0] SGP4isokay:
For Vilai and anyone else wanting a progress report, I tried the ROM supplied by Zaclimon and it cleared all errors in Samsung Recovery but I am still stuck there. Apparently the next step was to try flashing the bootloader but that failed in Odin. I still have access to Samsung Recovery and "Downloading..." mode.
[Samsung Galaxy Player 4.0, 5.0] axvk97:
I am having the same problem. I get no errors but keep booting into recovery. Tried flashing Steves kernel and it loaded into CWM with no errors. Still no system though. :(
[Samsung Galaxy Player 4.0, 5.0] iJimaniac:
Hmm, sorry for being late into the game, but I had these exact same errors, back before we really knew what we were doing, lol! I couldn't ever get rid of the errors, but I think that was because I was flashing the wrong partitions, so glad you got rid of them! I'm not sure why it still boots to recovery, I'll stay tuned to see what happens! Let me know if you need anything...

Sent using the XDA app.
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
SGP4isokay: If you do have these problems again try to do the following:

1.If you do have the bootloaders I sent you you can continue otherwise I'll send you a PM.

2. In odin chose the pit and check phone bootloader update.

3.In the bootloader space chose the bootloader file I gave you.

4. Ensure that re-partition is checked.

5.After this flash, Try to reflash the recovery rom.
[Samsung Galaxy Player 4.0, 5.0] axvk97:
Could you send me the bootloader file also (if it works for SGP4isokay)?
[Samsung Galaxy Player 4.0, 5.0] SGP4isokay:
Followed your instructions and the pit and bootloader flashed just fine. I loaded your full recovery rom and it now boots to the Samsung splash screen with chime but then it stuck with at the "SAMSUNG" text with black background...for 3 minutes then it

finally loaded

.

Right now my device is charging(almost dead) but I got to the initialization screen where you start picking language, etc. so I'll play with it when it's charged but holy **** I think it's fixed! :D

I will not post Zaclimon's files. They are his work and more importantly I don't know squat about Android. What worked for me may not work for others so please contact Zaclimon or wait for him to give a thumbs up for wider distribution.

So that we're clear

:

1. I loaded Steve's Kernel on the US SGP 4.0(no problems)

2. I went to go make a backup in Clockwork Mod and did so successfully

3. Upon coming out of CWM I experienced "bootloops"

4. I tried recovery ROMs and pit files and ended up in Samsung Recovery mode

5. Using a jig I got into Download Mode

6. Combinations of other default ROMs and PIT files did not work

7. Zaclimon's bootloader and the US 4.0 PIT file with Re-partition checked flashed successfully

8. I then flashed his full recovery ROM

9. I'm back to the "out of the box" login screen and it looks like I'm good to go

I am beyond amped right now. Once my device charges I'll set the time, date, and all that then run it through its paces to make sure everything is okay.

XDA is wonderful. This experience has taught me tons. Huge thanks to everyone who contributed to this thread, all the folks who were will to answer PMs, and finally Zaclimon for his efforts.

[EDIT 1]

Got to home screen. Customizing settings. Looks perfect.

[EDIT 2]

Device is working perfectly as far as I can tell. After it fully charged I downloaded all my apps and gave put it through its paces with no discernible issues.
[Samsung Galaxy Player 4.0, 5.0] Trae329:
Unfortunately, before I saw the fix for this, the same thing happened to me; I tried all of the fixes available (at the time) to get out of the bootloop but NONE of them worked for me.

I sent my SGP to MobileTechVideos.com for a JTAG Repair + a USB Jig for around $50.

That was the only option available for me; although I had to spend a decent amount of money just to get this fixed, oh well, I'm happy to have my SGP back :3

--Trae

P.S: I'm still wondering if CWM caused bootloops in Steve's 3.0 kernel, did anyone try it?
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
Congrats about your device running up again :D I think I have the way now to make the recovery rom for the US 4.0. The problem is the way the things are flashed on the US SGP. Also when you used my recovery rom did you re-partition?
[Samsung Galaxy Player 4.0, 5.0] SGP4isokay:
I did not re-partition when I flashed you recovery ROM. I only re-partitioned when I flashed the pit and bootloader at the same time prior to the ROM.
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
Ok so it seems that when people are experiencing bootloops or other things you aren't obligated to re-partition but if someone are from CM7 they need to re-partition (/system is ext4 instead of rfs.)

EDIT: Anyways have you found any issue after playing a few time with it?
[Samsung Galaxy Player 4.0, 5.0] Trae329:
Hello,

Pardon my interruption but I really need that bootloader that you sent to SGP4isokay. I am having the same errors w/ being stuck in recovery :/

Please PM me the files; it would be HIGHLY appreciated.

Thanks,

Trae
[Samsung Galaxy Player 4.0, 5.0] SGP4isokay:
Either I've gone a little insane or I can't get to Download Mode/CWM after powering the device down. I've done all the standard combinations of Volume, Home button, and Power button that should work. No dice. I ended up using my jig to get into Download Mode so that I could flash Steve's Kernel again. Beyond that I'm stumped to think of anything that is even remotely off.

So far I tried the following to make sure everything is okay

:

1. Took pictures and made a video

2. Used Wi-Fi

3. Just used GPS

4. Loaded music from an SD card

5. Bluetooth turns on but I don't have anything to test it with

6. Speakers, radio tuner, and headphone jack all work

7. Tons of apps downloaded, installed, and were used without any hiccups

8. Powered the device down and back up probably 20 times without any errors, freezes, or flickers

9. Flashed Steve's Kernel and all of the Voodoo Sound benefits checks out just fine

So yeah, the only thing I can't do is CWM/Download Mode. I can get to Download Mode using the jig. I can use the Volume Up/Volume Down rocker switch when the device is powered on. So both of those things work I just can't get into CWM/Download Mode in the conventional manner(Volume Down + Power for Download Mode and Volume Up + Power for CWM).
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
Hmmm I don't know normaly when I try to enter recovery I press power volume+ and home and when the samsung logo shows up I release the power button. I make the same thing with volume- for download mode but in your case that's strange. At least you have the jig
[Samsung Galaxy Player 4.0, 5.0] klin1344:
@ zaclimon: did you give sgp4isokay the bootloaders for the INTL version? I remember someone else doing that before and download mode wouldn't work either. But anyway at least it works. And you can always use terminal emulator and type 'su' 'reboot download' or 'reboot recovery'.

Also if coming from CM7 no need to repartition because tdmcode hasn't converted to mtd partitions yet. A factoryfs.rfs and zImage flash will do the trick.

Sent using Tapatalk
[Samsung Galaxy Player 4.0, 5.0] axvk97:
The same thing happened to me. Although I have only flashed the pit and bootloader. I havent been able to flash the ROM because I can't access Download mode. :confused:
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
I know but the problem is with a Intl bootloaders it seems that the 3 button combinaison aren't working in a US 4.0 so I need US bootloaders to do the trick.
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
The fact is you're not obligated to be in MTD/Yaffs2 to re-partition. Everything that not RFS needs to be re-partitioned in order to work (in the case of CM7 it's ext3 or ext4.)
[Samsung Galaxy Player 4.0, 5.0] Euphoric_Three:
@ zaclimon:

Looking forward to the update. Registered just to be able to keep track of this thread as I'm in the same boat as OP; player's stuck in that endless /cache loop.
[Samsung Galaxy Player 4.0, 5.0] dktfoster:
I have the same issue, if someone could supply me with the proper US 4.0 rom and a bootloader, it would be much appreciated.
[Samsung Galaxy Player 4.0, 5.0] Euphoric_Three:
Alright, so tried the same method as SGP4~ using zac's files (Thanks zac~).

Hyperrunner's pit flashes.

Zaclimon's bootloader fails to flash at param.lfs saying Complete (Write) failed.

Zaclimon's Recovery ROM flashes, but leaves my SGP stuck in recovery mode... but *without* mount erros.

I'm goin' to work atm, but will attempt this again when I get back.
[Samsung Galaxy Player 4.0, 5.0] SGP4isokay:
It didn't go into the thread because this took place over PMs, but the first time I tried the bootloader I flashed it by itself with Auto-Reboot and F.Time Reset checked and I received the following error:

After it failed I unplugged the phone, removed the battery, and successfully got back into "Downloading..." mode. The only thing that eventually worked for me was the files and procedure(Pit and bootloader together, then the ROM afterwards BE CAREFUL which boxes you check) listed on page 3. There is a gentleman on AnythingButiPod that supposedly flashed items section by section using Heimdall(link is in this very thread somewhere) but he never responded to my question on ABI. TDMcode was willing to walk me through it(can't thank the dude enough for his patience) but by the time I was about to try it out Zaclimon had posted his fix.

tl;dr Flashing the bootloader by itself failed for me also. Zaclimon's procedure on page 3 worked.

Unrelated

:

After having my device back in a working condition for three days I cannot find any errors/issues other than not being able to access Downloading Mode/CWM. Yes, that's kind of a big deal but absolutely everything else works. Probably 3 hours of active usage per day(movies, music, texting, surfing, etc.).
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
SGP4isokay: I have a new set of bootloader from a US device (Thanks Klin1344). If you want to try it I can send you the link however you can lose all of your things (or your device might brick.)
[Samsung Galaxy Player 4.0, 5.0] SGP4isokay:
I'd love to but I can't. I was in no position to replace my Galaxy Player the first time around, so now that it's working again my short lived tinkering days are over. :(
[Samsung Galaxy Player 4.0, 5.0] Euphoric_Three:
If you need a guinea-pig to test it, I'd be willing. Despite how annoying not bein able to have music at the gym may be, I have a backup plan should I not be able to recover from my tinkering. :D

[edit] Results of Attempting to reflash: So everything seems to work jsut fine *except* the bootloader. After flashing the stock .pit, Odin errors out on param.lfs

I can get to recovery mode with no mount errors. Download mode is still available. So my guess is that the error loading param.lfs causes the rest of the OS to fail loading.

Still... it's a sign of hope.
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
Dont touch anything yet.
[Samsung Galaxy Player 4.0, 5.0] Euphoric_Three:
Haha, too late.

However, I was able to duplicate how I got to having the mount errors. I've also been able to duplicate getting back to recovery mode without mount errors, so so far so good.
[Samsung Galaxy Player 4.0, 5.0] Jon49522:
Would it be possible for me to get the bootloader as well? I have the same problem, and so far nothing has worked.
[Samsung Galaxy Player 4.0, 5.0] axvk97:
This bootloader worked for me

but after you flash it you will not be able to use the Power button + vol down to access the downloading mode... So you need a USB Jig if you want to restore your device
[Samsung Galaxy Player 4.0, 5.0] SGP4isokay:
Not that this helps a ton, but I can confirm that this was the scenario that developed when my device was recovered by the fine people of XDA. Flashing the bootloader did indeed work but since then I have not been able to access CWM or Recovery Mode. The device is now recovered and fully functional other than the two aforementioned issues(mundane statement but one of my happiest tech moments ever).

So yeah, you're going to need a jig. Regardless of whether you buy one or fashion one, a jig is a small but miraculous investment if you find yourself painted into a corner.
[Samsung Galaxy Player 4.0, 5.0] pipng13579:
Hi Zaclimon,

If it is possible, could I have the bootloader too? Thank you soo much!