yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Player 4.0, 5.0] Stylezor:
I cant get more space than 6.1mb, and im getting the error: "error while restoring /system"

The md5 checksum pass, but then i get this error.

=t
[Samsung Galaxy Player 4.0, 5.0] rumirand:
No, md5 doesn't change.

To get the md5, do "md5sum file".
[Samsung Galaxy Player 4.0, 5.0] Higgsy:
Thanks for putting me straight there guys!
[Samsung Galaxy Player 4.0, 5.0] Stylezor:
Still no luck, getting the same error... i change the extensions on both(archives and nandroid). I cant make more space than 6.1mb on system, and while using titanium to do so, i almost bricked my device, restored it with my backup :s
[Samsung Galaxy Player 4.0, 5.0] rumirand:
Strange. I have 16mb of free space using stock /system (with root).

I'll see more in depth if I can tweak the ext4 format options in order to get more free space without sacrifice in performance.
[Samsung Galaxy Player 4.0, 5.0] turbanator:
Stylezor: Try removing / downgrading Google maps.
[Samsung Galaxy Player 4.0, 5.0] Stylezor:
Yup, i removed some stock apps, and it worked!

did a backup with like 19mb left on system, and now its in ext4 format, thanks everyone.

Ill be visiting the thread to help on the tests.
[Samsung Galaxy Player 4.0, 5.0] maxq1:
i was getting errors restoring /system too. uninstalled (then eventually restored via market/ti backup; all work afterwards, btw) the following from /system/app:

samsung kb (retained swype & i'm more comfy using modded htc hi-res kb which is less on memory, btw)

gmail

flash

all share (have no need for now)

my files (lots of better file navigation alternatives on the market)

this got me 12-15mb of free space & happily rockin' ext4

oh, and..when booted, "su" then "reboot bootloader" via terminal - which i prefer over button combos - to go to cwm recovery IS so far safe to use. hth someone..
[Samsung Galaxy Player 4.0, 5.0] Entropy512:
I'd do a "sync" before "reboot bootloader" or "reboot recovery".

Extended power menu will be safest once someone gets around to it.
[Samsung Galaxy Player 4.0, 5.0] aillez:
previously I flash this kernel to G70XEKP2(Latest Russian ROM)

in Odin return me failed & My player was soft brick.

but not a big deal.

I used 1 Click Unbrick & it's fine.

I try 2 times & fail everytime.

so it's proof That "NOT"Flash this kernel to other ROM otherwise G70XXKPF or G70ZSKP8.

I flash back to G70XXKPF & Enable ghetto lagfix

OMG !! It's faster than original

thanks to dev !!!!!!
[Samsung Galaxy Player 4.0, 5.0] rumirand:
Ok, will post on the first page that is not working with XEKP2.
[Samsung Galaxy Player 4.0, 5.0] WT Ho:
I am getting very close to completely deodexing /system/framework and /system/app. One benefit is the sizes of resulting APK and jar files are smaller which will make it easier for the conversion to ext4.
[Samsung Galaxy Player 4.0, 5.0] maxq1:
i'm gettin quite a batt drain on r8. yesterday around 6am i'm kinda sure i still had 90%. never used it after that until around 5.30pm the same day. lo & behold, i'm left with just 75%! turned for the night around 11pm, sure i had 60% left. 6am today, juice is down to 45%! then less than 5mins on wifi use & i'm left with 40%.

on previous versions, when i leave my device for long idle periods & wake it up my batt usually drains by about 0-5% - no more than that. settings (1.2ghz oc with underclocked profiles for lesser freqs/lazy gov/ext4) & background apps are very much the same.

anyone else having this? i'm on release 7 for now & so far this morning my batt drain is back to normal. i'll update the thread later on in the day

EDIT: it seems r7 is more batt friendly than r8. 35% in the morning. 30% now. will keep to r7 atm...
[Samsung Galaxy Player 4.0, 5.0] WT Ho:
I think I have similar observation. Typically, my player's battery can last over 2 days for my typical usage pattern, but it drops to about 1 day recently after using r8. This is a bit subjective though. May be I should switch back to r7 for a few days to compare the difference.
[Samsung Galaxy Player 4.0, 5.0] eerie_silence:
check it,
[Samsung Galaxy Player 4.0, 5.0] aillez:
oops ! it's doesn't work for me.

maybe I didn't wipe data/cache

thanks for info.
[Samsung Galaxy Player 4.0, 5.0] Entropy512:
I'd recommend dsixda's kitchen for deodexing.

Note that if you want to actually have it create a flashable CWM zip, you need to generate your working folder from a nandroid backup, not an RFS dump. (Generating from an RFS dump will result in any symlinks in bin and xbin not being extracted properly) You also need to manually edit the partitions in the updater-script. As far as dsixda's kitchen is concerned, we're closer to a Galaxy S II than a Galaxy S (due to using emmc instead of stl/bml.)
[Samsung Galaxy Player 4.0, 5.0] rumirand:
Thanks for the report.
[Samsung Galaxy Player 4.0, 5.0] rumirand:
Thanks for the report. On weekend I will look into it. I also have the feeling that battery drains faster.
[Samsung Galaxy Player 4.0, 5.0] WT Ho:
Thanks for the suggestions! As for deodexing, I am currently using a rather old script from Daneshm90. The only things broken is the Samsung keypad and the Camera. I will try the dsixda's kitchen and see if it works better.
[Samsung Galaxy Player 4.0, 5.0] calgop:
I try to lagfix last night,

before backup I do a full wipe then backup with CWM.

After restart and change file name to ext4 and edit .md5 then reboot to cwm

and do a restore it look like everything work (I saw file name that restoring).

After restore for a while it said Error restoring system , but after I reboot.

my player is boot like normaly. after that I use "cf-root-ext" to check free space of system but it said my system is already ext4.

I dont know if it because I use G70XXKPF-rooted-rj8 ROM from http://xdaforums.com/showthread.php?t=1446774 by WT Ho or my step is working.

sorry about my English :P
[Samsung Galaxy Player 4.0, 5.0] WT Ho:
I suspect that your /system partition is running out of space when restoring. It was mentioned earlier in this thread. If the restore was already in progress, that means CWM had formatted your system to ext4 already but failed to copy all files back to the partition.

What you can try is to re-flash the rooted ROM and then delete some system apps before you attempt lagfix again.
[Samsung Galaxy Player 4.0, 5.0] andi016:
Hey!

I just found this thread:

http://xdaforums.com/showthread.php?t=1450298

(actually I found "Usb Host Controller 0.1 Ad-Free" app first)

Now I wonder, is it possible to put this usb-host driver into YP-G70 kernel?

Will it work?

Greetings!
[Samsung Galaxy Player 4.0, 5.0] Entropy512:
I think Samsung Keypad issues result from some weird font handling stuff - see the Galaxy S II dsixda thread.
[Samsung Galaxy Player 4.0, 5.0] Entropy512:
Possible? Maybe.

Worth it? Not likely. The Galaxy S USB host functionality has some very severe and extreme limitations - it requires an external power supply for the device connected, and many devices don't work because they can't re-enumerate.

There's a thread on this in General or Q&A
[Samsung Galaxy Player 4.0, 5.0] jamieelockey:
hello everyone :) was just wondering do i need to root froyo before this? and will this wipe my device? thanks! and also is the "soundalive" option still availible in this? :)
[Samsung Galaxy Player 4.0, 5.0] Entropy512:
This is a kernel, not a ROM - it is flashed using Odin.

Note that it will not work with Froyo - it's for Gingerbread.

(It can be used to flash WT Ho's Gingerbread firmware though.)
[Samsung Galaxy Player 4.0, 5.0] jamieelockey:
Which version of gingerbread should I install? Is there any links in this forum? I have an English device, and can I still.root gingerbread with superoneclick thanks for the reply
[Samsung Galaxy Player 4.0, 5.0] rumirand:
This kernel is not for your device. Use Entropy512 kernel.
[Samsung Galaxy Player 4.0, 5.0] jamieelockey:
i dont have a us device though? now im confused..

EDIT: my device has mechanical home button :P

Model: YP-G70

Firmware: 2.2.2

Kernal: 2.6.32.9 se.infra@SEI-27 #1

bulid: FROYO.XXKD6
[Samsung Galaxy Player 4.0, 5.0] rumirand:
You have the international version. You can use WT Ho's rom, which comes with this kernel already.
[Samsung Galaxy Player 4.0, 5.0] andi016:
Last year I had "one of those" china tablets, it was way below Samsung quality/speed but it supported usb-host mode. So using usb hard drive (yes, externally powered), I had access to 500gb of movies/music/photos - witch was very useful (usually on the trip).

So is it worth it? - if external power supply is that major limitation, the answer is: YES! :-)

I will be happy if it supports just general storage driver (like most of usb-hdd's).

So, what I don't know is "what needs to be done" and how hard is it.

Or, in another words can I use some "donate" button to "make it happen"?

Greetings,

Andi
[Samsung Galaxy Player 4.0, 5.0] rumirand:
Bump to r9.

Tentative fix for battery drain problem. Please give some feedback to see if it's really fixed.
[Samsung Galaxy Player 4.0, 5.0] Fulaeetoy:
I updated to r9. I left it at 100% last night and after 9 hours i still got 95%. Same in r8. Don't know if it's good.

____________________________________

~ Sent from iOS/Android device
[Samsung Galaxy Player 4.0, 5.0] Entropy512:
I'm wondering if somehow your cpuidle patch didn't get applied properly - your kernel would be the first time I've ever seen it cause drain problems.

Usually the difference with that patch isn't too noticeable, but in a few corner cases (such as weak-signal syncing) it was a major improvement on Infuse and I777, and it never hurt battery on Infuse, I777, or my Galaxy Player - my battery life has been incredible.

Did those who had drain issues look for wakelock problems?
[Samsung Galaxy Player 4.0, 5.0] rumirand:
It doesn't seem to be the case, but will repatch and see if it works.
[Samsung Galaxy Player 4.0, 5.0] WT Ho:
I think the battery drain is still there in r9. My player lost almost 20% overnight and it was in airplane mode.
[Samsung Galaxy Player 4.0, 5.0] maxq1:
testing r9 for at least 4hrs now. wiped /cache, dv cache & batt stats for good measure. seems good so far. will update my post later in the day

as for init.d, are there any other modz required to use it? except of course for creating the /system/etc/init.d (is this correct?) folder and placing startup scripts in there?

EDIT: unfortunately, batt drain's still there as WT Ho reported.

didn't get this though, if it's any help...
[Samsung Galaxy Player 4.0, 5.0] Entropy512:
Those experiencing battery drain - use BetterBatteryStats (search for it here on XDA - it's normally a paid app but the author gives it to XDA users for free in his thread) to hunt for wakelocks.

Most high-level sign of wakelocking:

1) CPUSpy reports low deep sleep percentages. BTW, charging inhibits deep sleep, so always enter CPUSpy and do menu->reset timers after pulling your device off the charger.

2) In Settings->About->Battery Usage, if you tap the graph to bring up the detailed graph, you see a lot of "Awake" time that doesn't have "Screen On" time associated with it
[Samsung Galaxy Player 4.0, 5.0] maxq1:
good lord! took wakelock for something else. sorry 'bout this. is this it then?
[Samsung Galaxy Player 4.0, 5.0] Entropy512:
SOMETHING is definitely waking your phone up on a regular basis.

What's at the top of your Battery Usage screen?

Use BetterBatteryStats to determine what is holding wakelocks and causing all of that awake time with no screen-on time.
[Samsung Galaxy Player 4.0, 5.0] rumirand:
Ok, after some testing it seems that SoD patch was preventing the player to go to Deep Sleep state. Using it, half the time the player is at maximum freq and Deep Sleep mode isn't used. Without it, it stays >60% in Deep Sleep. Is this behavior expected?
[Samsung Galaxy Player 4.0, 5.0] Entropy512:
This is not even remotely expected. 60% deep sleep is what I consider to be EXTREMELY poor for a device sitting idle.

For example, my GS2 (with the same patch) routinely has deep sleep of 97% when on wifi. It'll go up to 98-99 when on airplane mode. Same deal back when I had an Infuse.

I haven't taken statistics from my Player, but I have the SoD patch applied and no trouble with deep sleep.

I wonder if there is something about your source base that caused the patch to not apply cleanly...

What you should see if the SoD patch is applied AND you have a screen-off profile that is set to less than 800 MHz in SetCPU is that the CPU hits 800 MHz occasionally (basically, when entering/resuming suspend), but if it spends a lot of time here something is waking up the phone often (some kinds of wifi traffic patterns can cause this. See http://xdaforums.com/showthread.php?t=1308030 and http://xdaforums.com/showthread.php?t=1409513 for examples - most of the stuff from the first thread will also apply to the Player.

On first review of the patch, I don't see anything different than my source base unless SLEEP_FREQ is defined differently from the source base I'm using. The other possibility - are those who are having problems using tegrak's stuff to overclock? God only knows what injecting unknown binary-only cruft into your kernel is doing if you are.
[Samsung Galaxy Player 4.0, 5.0] rumirand:
EDIT: Using your source and works as it should.
[Samsung Galaxy Player 4.0, 5.0] Entropy512:
Weird... What are the wakelocks listed by BBS?

Right now my deep sleep percentage is at 96%, and that includes a few minutes of usage.
[Samsung Galaxy Player 4.0, 5.0] rumirand:
Nevermind. Now I'm getting >90% deep sleep with your source. I will switch to your source code.

Thanks for always helping us.
[Samsung Galaxy Player 4.0, 5.0] kiwijunglist:
Hi I have the following device/firmware, which I bought today so that I can use it as a car computer.

Stock Samsung Galaxy S WiFi 5.0

YP-G70 (International Version, from New Zealand with physical home button)

Firmware 2.2.2

Kernal 2.6.32.9 seinfra@SEP-53 #1

Build FROYO.XXKG1

I can't seem to root the tablet, tried superonclick/z4root/another method.

1. If I install this custom kernal using odin will I get root privileges?

2. After installing this kernal, which ROM would you recommend? (I understand that since I am using Froyo, I have to install a GB rom post installing this kernal)

3. Does the above rom that you suggested come with root if the kernal doesn't provide root.

4. What is the best stock ROM for this device?

Thanks

Mike
[Samsung Galaxy Player 4.0, 5.0] aillez:
superoneclick can root almost rom of this device except Chinese ROM (2.3.6)

so what version of superoneclick you use to root it ?

if it don't really work with superoneclick

you can try DooMLoRD's Easy Rooting Toolkit (can find in the forum)

anyway

for your question

1. yes

2. like you understand it. You need to install GB ROM. for me I use XXKPF (Italy rom) it's fine.

3. you can use superoneclick latest version to root it

4. I don't know but XXKPF has a lil' bug that not important at lease for me. so I think this rom is OK but I have try Russian Rom it's almost the same but have some stock app more than italy rom (but I don't use that app anyway lol)
[Samsung Galaxy Player 4.0, 5.0] kiwijunglist:
Hi

Thanks for quick reply

I tried using superoneclick 2.2 ; latest version, tried all 3x methods, with latest usb driver after mulitple reboots with usb debugging on / off.

I already tried DooMLord's rooting tool, which seems to use the zerg method that is already included in superoneclick.

I will try flashing Wt Ho's G70XXKPF-rooted-rj8 stock based rom +/- your r9 kernal post flashing.
[Samsung Galaxy Player 4.0, 5.0] Higgsy:
Agree -

-Italian XXKPF 2.3 ROM

-Root with Superoneclick

-Install the lastest rj kernel

I used WT Ho's zip which worked but I couldn't get into recovery form cold boot via key combo and also all google stuff was missing (not sure if the google stuff was meant to be missing or not) I then started again with the above method and all ok.

That was my experience anyways
[Samsung Galaxy Player 4.0, 5.0] rumirand:
Bump to r10.

Changes:

- Battery drain is gone (SoD patch removed FOR NOW).

- Latest patches/fixes from Entropy512's source.

Later will update my Github.
[Samsung Galaxy Player 4.0, 5.0] kiwijunglist:
I'm using r8 kernal + Wt Ho's XXKPF

Can I flash using CWM 5.0.27 if so do i use install zip from sdcard or apply update from sdcard?

Thanks

Mike

PS. The reason why I ask if I can use CWM is because I understand it is safer than odin.
[Samsung Galaxy Player 4.0, 5.0] rjsmith2007:
I'd like a CWM zip as well. Can you upload one of those too?
[Samsung Galaxy Player 4.0, 5.0] rumirand:
Ok. In the next release I'll include a CWM zip.
[Samsung Galaxy Player 4.0, 5.0] Entropy512:
In the meantime, it should work if you take the zImage from rumirand's tar and replace the zImage in one of my zips with it.

Other option is, on the device (ADB shell is the best way)

dd if=zImage of=/dev/block/mmcblk0p11

NOTE - ONLY USE THE ABOVE LINE ON AN INTERNATIONAL OR USA 5.0. IT WILL EITHER FAIL OR BRICK ON ANY OTHER DEVICE.
[Samsung Galaxy Player 4.0, 5.0] WT Ho:
Thanks! Flashed it last night and the battery lost less than 5% overnight. That's much better than before.
[Samsung Galaxy Player 4.0, 5.0] Entropy512:
Heh, I was about to suggest you consider rebasing to the US codebase, but you already did.

My guess is there was some sort of bug in the International codebase that didn't play well with the SoD patch - that's a new one... I believe the USA codebase is newer.

(Kind of like how the I777 codebase was popular with I9100 users until they got the update3 source drop.)

BTW, I see you've been manually giving me credit for patches. Here's a neat git tip:

Pull up a commit summary on github, for example: https://github.com/Entropy512/linux...mmit/ef4e5d96e343b518cd4a5a9eb1ddc236a8bf8667

Add .patch to the URL: https://github.com/Entropy512/linux...f4e5d96e343b518cd4a5a9eb1ddc236a8bf8667.patch

Download the patch somewhere with wget:

wget -O usb_unplug_fix.patch https://github.com/Entropy512/linux_kernel_galaxyplayer/commit/ef4e5d96e343b518cd4a5a9eb1ddc236a8bf8667.patch

Apply with "git am":

git am usb_unplug_fix.patch

That'll get you the "authored by/committed by" annotations on github.

There are a number of other sources for "git am" formatted patch files - read up on "git am" for details. It's designed so that a developer can automatically send emails for a patchset, and someone can automatically apply those emails directly. :)
[Samsung Galaxy Player 4.0, 5.0] WT Ho:
Hi rumirand , I am poking around the recovery, trying to find out some more about how ext4 works because I am toying with the idea to force wipe user data before flashing a rom.

But what I notice is that there is no mkfs.ext4, but if I format a partition using mkfs.ext2, it will be converted to ext4 on boot. Is this how it suppose to work?
[Samsung Galaxy Player 4.0, 5.0] Higgsy:
R11 working sweet here on my UK yp-g70 with the Italian XXKPF firmware. Cheers to Op and also Entropy512 for his contributions
[Samsung Galaxy Player 4.0, 5.0] rumirand:
Thanks for the tip. I'm a happy linux user, but always you have something to learn.
[Samsung Galaxy Player 4.0, 5.0] rumirand:
No. mkfs.ext2 is only a symlink to busybox. Busybox has built-in support for formatting (mke2fs) ext2, ext3 and ext4 volumes. You have to tell specifically you want a ext4 drive:

mkfs.ext2 -t ext4 /dev/block/mmcblk0pXX

or

busybox mke2fs -t ext4 /dev/block/mmcblk0pXX

Creating ext2, ext3 filesystems and converting to ext4 is possible, but you'll lose some ext4 features.

Some reference for you here.
[Samsung Galaxy Player 4.0, 5.0] kiwijunglist:
Flashed from r8 to r11 using cwm, no immediate problems. THANKS
[Samsung Galaxy Player 4.0, 5.0] WT Ho:
Thanks for the information about ext4!
[Samsung Galaxy Player 4.0, 5.0] rumirand:
Bump to r12.

- OC 1.2Ghz & UV (use SetCPU or similar for UV control).
[Samsung Galaxy Player 4.0, 5.0] Higgsy:
Is that 1.2ghz by default or overclockable up to 1.2ghz.

Cheers

sent from my mind using telepathy
[Samsung Galaxy Player 4.0, 5.0] rumirand:
EDIT: 1000 mhz default.
[Samsung Galaxy Player 4.0, 5.0] Entropy512:
RANT ON: (in your thread because it was the only one with new posts and I'm lazy):

Samsung seems to have put crap in their battery charging algorithms that causes the charger to stop charging at fairly low voltages. This is why people often see their devices stop charging at around 80%.

I tried to port my charginghacks code from the Infuse over today. This was the result:

It charges at 800 mA, then switches to constant-voltage mode, at 4.041 volts. (CurrentWidget provides a much nicer current graph, but does not show the voltage. :( )

Then I plugged in USB and I wound up back in a constant current state.

This is what it SHOULD have looked like (this is historical from my Infuse:)

800 mA, then 700 mA when the battery got closer to full, then 600 mA, THEN entry into constant-voltage charging. (hmm, must be from one of my first charginghacks variants... Later versions also had a 550 mA step)

This would enter constant-voltage mode at around 4.18 volts (just a shade under the Li-Ion limit of 4.2 volts.)

A bit more technical detail:

Lithium ion batteries should normally charged as follows:

Current limited (constant current) up to around 4.2 volts

Voltage limited (constant voltage) past this - current will slowly drop as charging completes

Charging should be terminated when current drops below a specific threshold.

What the Players seem to be doing is entering CV mode at 4.041 volts instead when on a wall charger. :(

grumble grumble frustrating Samsung
[Samsung Galaxy Player 4.0, 5.0] rumirand:
That's why charging takes forever.

Is there a possible fix? It seems to be a lot of work/coding needed.
[Samsung Galaxy Player 4.0, 5.0] Entropy512:
Bumping it to 800 mA from 600 is easy - but after looking in more detail, I think it is fully charging the device.

However - Samsung really ****ed some things up. Because they're not using a proper fuel gauge, they are doing all sorts of janky crap to try and estimate the battery's state of charge.

https://github.com/Entropy512/linux...blob/master/drivers/power/adc_battery.c#L2322

So they have all sorts of compensation values that alter the voltage depending on what the device is doing. AC charging has an offset of -230 - it appears that the compensation values are (millivolts*1.5) - so this is about 153 millivolts. 4200 mV-153 mV = 4047 mV, not far off from where the battery topped out.

So when someone sees their battery stuck at 80% after charging - that's actually full!!!!!

Fixing charginghacks should not be hard. Getting accurate battery state of charge estimates - that'll be difficult, if not impossible (depending on whether the MAX17040 components of the MAX8998 are properly wired...)
[Samsung Galaxy Player 4.0, 5.0] noisyfox:
Really nice job. And if it support voodoo then it's perfect. Thanks to your hard work! By the way, g70's battery level state only increase 5% each time, is it influenced by kernel or the fw?
[Samsung Galaxy Player 4.0, 5.0] Entropy512:
G70 has a Yamaha MC1N2 audio chip, not the Wolfson WM8994 in the 4.0 - no Voodoo Sound.

As to battery indicator having 5% increments - see my rant above. The method our device uses to estimate battery state of charge is inaccurate crap - even 5% is too fine grained, it can be off by as much as 20%.

There is no way to do this without completely overhauling the battery management code to use the MAX17040 fuel gauge inside the MAX8998 power management IC - this assumes that the MAX17040 portion is even wired up, which I'm guessing it likely is not.

So it's a kernel limitation best case that would require MAJOR work to fix, and it's a hardware limitation more likely.
[Samsung Galaxy Player 4.0, 5.0] noisyfox:
Thanks a lot.

---------- Post added at 07:32 AM ---------- Previous post was at 07:12 AM ----------

By the way, there is a question. I'm using r11 kernel and if I connect the USB to computer then turn on the power, my computer will say 'unknown device'. But if I use r10 or older, and everything goes right. What's the problem?