yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Player 4.0, 5.0] :
INT KERNEL 4.4.2 FIX?: http://www.4shared.com/zip/-XwUM3-6/SlimKat_442-YP-G70-INT-KERNEL_.html

Please let me know if this works!:laugh:
[Samsung Galaxy Player 4.0, 5.0] Lorddemonrage:
hey meticulus, thanks for all the work.

was just wondering if its possible implementing this into slimkat also. it was posted in the cm11 thread a few posts down. Several of us have been trying to get an app called viper4android working on both cm 10.2 and cm11 with no luck. apparently the links in this post should do the trick.
[Samsung Galaxy Player 4.0, 5.0] :
I took a quick look at the 3 commits and commits 1 and 3 do not apply to this device. The added lines in commits 1 and 3 only apply to Qualcom devices that have FM capabilities indicated by "QCOM_FM_ENABLED". That only leaves commit 2, with only one line that changes for this device.

I'll put it on the list, if... there is anyone who can gather any relevant debug data and post it here (help me help you! I don't use Viper4Android!). I got a lot on my plate, so it might take awhile too...
[Samsung Galaxy Player 4.0, 5.0] angelos208:
it works! :victory: :laugh: :highfive: :p
[Samsung Galaxy Player 4.0, 5.0] joemhewitt:
Works for me as well.

Does this ROM support FM radio?

Sent from my zx spectrum
[Samsung Galaxy Player 4.0, 5.0] :
No, but I'll put it on the list....

Just FYI... there really is a list.:o
[Samsung Galaxy Player 4.0, 5.0] Lorddemonrage:
not sure how to gather debug data, but if you hum a few bars i might be able to.
[Samsung Galaxy Player 4.0, 5.0] :
do wa diddy log-cat's diddy dmesg....

Well, detailed description of the problem.

Does the app crash

Does it make noise

When in the process of using it does the problem occur.

Does it make fun of you when it thinks your not listening?

what does adb logcat say when the problem happens...

Is there an error box and what does it say...

Can you get me a screenshot of it messing up...?

What have you tried to do to fix it and what was the result?

Did you ask it to play nicely?

Does changing your wallpaper help?

:highfive: I kid... but you know just detailed info on what the problem is... look up "how to get a log cat" and "how to get a dmesg" and get a logs while it's having the problem.

Does the developer of the app have a web page or something that details the problem or is there info where people are discussing the problem?

ya know, that sort of stuff;)
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
Btw you don't need a commit for Fm radio... You only need to execute the si4709 module at boot, then it should work like normal. (if not already :p)

Envoyé depuis mon Nexus 7 avec Tapatalk 4
[Samsung Galaxy Player 4.0, 5.0] Lorddemonrage:
didn't get a logcat yet but i can tell you what its doing. the app itself copies a sound driver into system/lib/soundfx, the file is named something like libv4a_fx.so. it modifies audio_effect.conf to reference this driver file. Now the problem lies in that after it does all this, the app itself says "driver install failed etc....." even though the file copied over and the system file is altered.

I already tried getting a response from the dev, as have other people on the thread. There is a list of stuff that you can do that has helped some people but not all, so i think for the rest of us we are SOL.
[Samsung Galaxy Player 4.0, 5.0] gmillz:
The Galaxy Player still alive? Nice to see people still working on it :)
[Samsung Galaxy Player 4.0, 5.0] :
I bought my Player 5 at best buy like 2 years ago. "Still my favorite device!" :victory:
[Samsung Galaxy Player 4.0, 5.0] aznflawless:
I bought my device for about 17 months now at Micro Center! My first and my main device to use. I don't have a phone. This is the closest thing to a phone
[Samsung Galaxy Player 4.0, 5.0] Lorddemonrage:
got mine from newegg earlier this year. paid 141.00 for it, was refurb but works like a champ still! I have a thing against owning a cell phone so when people saw me with it they were saying "AHA! you do have a phone!!" nope, not a phone...
[Samsung Galaxy Player 4.0, 5.0] :
LVMv2 Comming Soon...

If anyone wants to see what I've been working on for the YP-G70:

https://github.com/Meticulus/slim_d...mmit/7ccd47c874f9a00c0397c8e8f17f3faaf72e256b

Basically FULL- GAPPS.

I was fracking frustrating, enlightening and fun! ;)

EDIT: forgot a few lines - https://github.com/Meticulus/slim_d...mmit/6dd83396dcfa853119c840306fe8f10dbf142411
[Samsung Galaxy Player 4.0, 5.0] luraziel:
^ this. is. AWESOME!!!!
[Samsung Galaxy Player 4.0, 5.0] ArdDarvis:
I got mine last june on ebay, used for 120. basically the best thing thats ever happened to me. for serious.

i just came from slimbean, CWMR touch 6.0.3(?). i had to do a dance to get it to work, but slimkat is perfect so far. i'm about to go thanks everyone involved.

i immediately noticed that the DPI is different than in slimbean? i probably have no idea what i am talking about.

EDIT: the torch doesn't work. other flashlight apps don't work either.
[Samsung Galaxy Player 4.0, 5.0] bakakun028:
What would ha happen if I flashed international kernel on a Korean device?
[Samsung Galaxy Player 4.0, 5.0] mr_ggcstop:
When i flashed Korean kernel (on 2.3.6) on international device there were not working camera only.
[Samsung Galaxy Player 4.0, 5.0] :
OTA coming soon too! (Still Unofficial)

More Galaxy Player 5 love! ;)
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
Cool!

Is binary blob lvm the normal way to do it? Seems kinda hacky to me, but whatever works.

Following up on my kernel progress: I couldn't get UART or USB out of anything newer than 3.0, because our chip has no support past that (like the OMAP4/Galaxy Nexus). I didn't try very hard with the AOSP kernel/samsung (made for crespo), but the cyanogenmod aries kernel works with no modification. I'm going to build up a new kernel for us that we can hopefully upstream to aries so we don't have to maintain a separate one ourselves (or at least, anything but our device's part).

To continue the discussion: I got my SGP in January 2012 from Newegg and promptly black-screen bricked it. So I sent it back and got a refurb off Amazon. I got a smartphone (GNex) that August, so I lent it to a family member. She got a smartphone last month, so I have my SGP back as purely a development device.
[Samsung Galaxy Player 4.0, 5.0] :
Actually, the blob is supposed to go in the kernel initramfs like: https://github.com/Mevordel/android...ree/3.0Venturi/usr/galaxysmtd_initramfs_files

I'm going to move them there a little later but this works for now.

If I get time, I'm going to try to create a 2.6 kernel base off the original samsung code. ICS+ will run on 2.6 kernel right?

Also, getting in line with aries would make new bring ups much easier!:good:
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
It worked on ICS, required a hack in vold for storage to work on 4.1, and did not work at all on 4.2+. There's really no point though, because the WiFi driver in 3.0 is a lot better, as well as pretty much everything else (interactive, ext4, ipv6).

Sent from my Nexus 5
[Samsung Galaxy Player 4.0, 5.0] :
The only reason I want to do it is to see if I can get the rear cam working..;)
[Samsung Galaxy Player 4.0, 5.0] bakakun028:
I flashed the international kernel on my Korean galaxy player. It appears to be working flawlessly besides the camera which is to be expected. Have not tried out the bluetooth yet however.

Meticulous, you said you would try to post a Korean kernel. What would be the point in that as the international kernel seems to work just fine? Would there be any benefits over the international kernel?

One more question: isn't the status bar supposed to be transparent in 4.4? Mine remains opaque in all apps.

Sorry but one last question : I cannot seem to find a way to enable lockscreen widgets. Tried fiddling with the lockscreen and security settings but no luck.
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
Makes sense. I believe Jackpot had hacked together a working lib/kernel combination on cm9 or cm10 once right before we got 3.0 working, but it has since been lost to the dungeons of time. My newer kernel is uploading now. I'm going to add hardware support piece by piece, first power management (rebooting), then eMMC, the FSA switch, then the screen and whatnot. I noticed though that a couple hundred lines of camera code was in mach-venturi.c, so maybe that is what needs to be updated.

The latest work on the 2.6 kernel is at https://github.com/Mevordel/android_kernel_samsung_venturi_2.6 I believe, unless iurnait did some later work after I left. Koala888' had an unstable kernel, but I think it was just performance tweaks. The order of work was Entropy512 -> Ambrice -> JackpotClavin -> me -> iurnait.

There's so much cruft in that tarball dump it's disgusting, though. IIRC, a diff of the vanilla 2.6.35.7 and what Samsung gave us is like 51 MiB! :gasp: And if you do go to their site, don't get the US one. That's for a never-released froyo version (2.6.32). Interestingly, we do get the source for their sound enhancements that made some people stay on 2.2.

Edit: I can confirm the power/volume buttons do in fact work at the moment. Such an important part, I know. cat /dev/input/event1 :cowboy:

Edit2: Upload is done https://github.com/smaeul/kernel_samsung_aries
[Samsung Galaxy Player 4.0, 5.0] :
1. I can't say what the benefits would be, I didn't do the work on the kernel. There is a configuration that is specifically for the KOR version. If I had a KOR device I'd just try it and then I could tell you but I don't. I haven't forgotten that I said I would release it and it will be released with the next build ( building now). Then you tell me what the benefits are ;)

2. The status bar transparency has been discussed in the CM11 thread. Check it out...:silly:

3. I have been building SlimKat for the YP-G70 as if it were a tablet. The reason being that building as a phone might cause unforeseen issues because our device doesn't have a cell radio. Recently the option has been re added to SlimKat to build as a hybrid-wifi-only device. I'm building with that option now, which (I'm hoping), will open up more options. such as lockcreen settings..:good:
[Samsung Galaxy Player 4.0, 5.0] :
That's good info man, per she ate it!

I'm running a clean build in preparation for a release. Once I get the release out, I'm going to build this kernel and see what I can see!:good:
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
The advantage to a Korean kernel is twofold: it would fix your back camera (s5k4ecgx I believe, the same one as crespo. International has a s5k5ccgx), and enable the tv tuner.
[Samsung Galaxy Player 4.0, 5.0] :
New Build!

Update to 4.4.2 beta 1.7 (check the change log @ slimroms.net)

LVMv2 implemented (Full GAPPS!)

SlimCenter Ota (Will update you when I post a new build!)

Download: http://www.4shared.com/zip/nkBjRoSR/Slim-venturi-442beta17-UNOFFIC.html

Device Changelog in OP 3

Gapps: http://slimroms.net/index.php/downloads/dlsearch/viewcategory/978-addons4-4/downloads/ Yes use 4.4.1 until they update them.

INT kernel: http://www.4shared.com/zip/hIpDJYGP/SlimKat_442-YP-G70-INT-KERNEL-.html

KOR: kernel: needs a little work, so hang tight. Use INT for now...

MERRY CHRISTMAS!!!
[Samsung Galaxy Player 4.0, 5.0] ratyfu:
Thanks for your great work, meticulus!

With all these changes to partitions and recovery, and users reportedly not being able to get back to stock, is it safe to flash these betas, or is there a chance for a hard brick / getting stuck on a ROM?

I've revived my player before, so if it's theoretically possible I wouldn't mind having to do it again. I just don't want to put my device into a terminal state.
[Samsung Galaxy Player 4.0, 5.0] :
There are no "REAL" changes to the actual partitions. They are still there and their sizes and properties have not been changed...( if you type fdisk -l /dev/block/mmcblk0 in adb shell, it will be the same as it's ever been. What has changed is that we are grouping the space on a couple of partitions to create one large virtual disk the we can repartition to get a larger /system directory. I've gone back and forth several times between 4.3 and this newest 4.4. As always, you flash custom roms at your own risk. I am not responsible!

Would you like to know more? Read the changelog entries tagged LVMv2 here : http://xdaforums.com/showpost.php?p=48453702&postcount=3

or google Logical Volume Management....

NEW INSTALLATION INSTRUCTIONS POSTED HERE: http://xdaforums.com/showpost.php?p=48453687&postcount=2
[Samsung Galaxy Player 4.0, 5.0] ratyfu:
Thank you!

About the "own risk" part, I think that only idiots would blame you if something went wrong.

I just want to know, if there have been changes (for example due to twrp recovery) in this ROM, that make it more likely to hard-brick the device, than previously (<4.3.1).

One user stated, that he was "stuck" on your first version of SlimKat, which I don't really understand. Because if he was stuck, then you would have been stuck as well, assuming that you flash your own builds.
[Samsung Galaxy Player 4.0, 5.0] :
There have been no changes that would "increase" the likelihood of a hard-brick period. The risk in 4.3 and this one are the same. I do flash my own builds and test them before I post them. I don't however, have a INT, or KOR device....

That one user is stuck because he doesn't realize that all he has to do is:

Flash a different kernel with a different recovery using Odin or Heimdall

At this point the device may not boot properly but.....

Power off the device....

Hold volume up to get to NEW Recovery.

FULL Wipe

Flash like normal

????

Profit!!

I tried to tell him but...
[Samsung Galaxy Player 4.0, 5.0] ratyfu:
Ok, that's good to hear. Thanks for your patience! ;)
[Samsung Galaxy Player 4.0, 5.0] FweaKiid305:
You Told Me A While Back And I've Already Done Exactly That But Thanks For The Support.
[Samsung Galaxy Player 4.0, 5.0] joemhewitt:
Erm, I was trying to flash the new build and suddenly i have twrp. Wtf did that come from? Also on trying to flash the build, it booted up but then stopped on the "galaxy s / cyanogen mod" screen. I think I did something wrong though.

Sent from my zx spectrum
[Samsung Galaxy Player 4.0, 5.0] :
SlimKat has always had TWRP...:p

Just try flashing again and let me know how it goes...:o
[Samsung Galaxy Player 4.0, 5.0] joemhewitt:
Oh OK, will probably try again tomorrow. Merry Christmas fellow galaxy player users!

Sent from my zx spectrum
[Samsung Galaxy Player 4.0, 5.0] akashsgpgi:
thanks to all the devs who are still developing for galaxy player:good:

this rom is very nice and fast though i get get some reboots

im happy that galaxy player has still life in it thanks to the devs
[Samsung Galaxy Player 4.0, 5.0] :
I'm starting to notice the reboot's too.:( Hope fully it's been addressed in beta 1.9....
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
SD cards are working now. Do you think we should move kernel work to its own thread or is it fine here?

Sent from my Nexus 5
[Samsung Galaxy Player 4.0, 5.0] :
It's up to you, I'm good either way....:highfive:

EDIT: I kinda got side tracked creating a "build release system" that automatically creates change-logs and updates the OP and....
[Samsung Galaxy Player 4.0, 5.0] :
About Lockscreen Widgets

It seems that Lockscreen Widgets are disabled in devices that are designated "low ram" and you can get them back by changing the build.prop (see images)

Note: It seems like some apps are having trouble re-mounting /system rw. To overcome that just do adb root the adb remount.

EDIT: Also, don't know what other consequences "low_ram" flag has...

EDIT2: Did a build to test my release system....
[Samsung Galaxy Player 4.0, 5.0] FweaKiid305:
Is It Safe To Update?
[Samsung Galaxy Player 4.0, 5.0] akashsgpgi:
im getting bootloop when i installed beta 1.9 after a full clean wipe

will try again and report
[Samsung Galaxy Player 4.0, 5.0] annoyingduck:
What app are you using to get each build entry separately listed like that? It looks like root Explorer on the bottom, but not the rest...
[Samsung Galaxy Player 4.0, 5.0] iurnait:
Its ROM toolbox
[Samsung Galaxy Player 4.0, 5.0] bakakun028:
Ever since the update with the inclusion of OTA updates (1.7 i beleive) I've been having severe graphical glitches in menus in all apps including settings. Whenever that happens, the device would slow down considerably and eventually reboot by itself. Anyone else having this problem?

This happens even if I do a completely clean flash.
[Samsung Galaxy Player 4.0, 5.0] :
Yes, I am aware of the issue and I'm trying to hunt it down... Something happened in 1.7 because it didn't happen in 1.6....:good:
[Samsung Galaxy Player 4.0, 5.0] :
I'm still trying to hunt down this graphical reboot problem. No more releases till further notice....
[Samsung Galaxy Player 4.0, 5.0] annoyingduck:
Cool, thanks....
[Samsung Galaxy Player 4.0, 5.0] :
Graphics/Glitchy/Reboot Problem

OK so, I think I got a handle on the graphics/glitchy/reboot problem. For me, the problem happens when/or after , I use MX Player. MX Player is my favorite video player and I always use it. The problem comes from using HW+ (Hardware +) video decoder. I ran a completely clean build and have MX Player on HW ( not HW+) and I tried last night to get it to reboot and I couldn't.

I am convinced that the problem is MX Player. (HW+)

I am convinced that it's not any of my changes

I am convinced that it's not SlimKat code.

EDIT: I spoke too soon. Problem persists this morning without MX Player :(
[Samsung Galaxy Player 4.0, 5.0] annoyingduck:
[MENTION=4400604]Meticulus[/MENTION], have you read slims changelog for beta 2.0? If not, check out the framework addition of "chamber of secrets"...

This has nothing to do with what you're trying to fix, but had to point that out because it's pretty awesome whatever it is!
[Samsung Galaxy Player 4.0, 5.0] :
I'm not sure what that is, I remember seeing it awhile back and thinking that the name was some sort of "Harry Potter" reference. It looks like it might be custom settings shortcuts or maybe tile shortcuts....:good:
[Samsung Galaxy Player 4.0, 5.0] :
I've been looking around and it seems that other devices that have our same gpu on SlimKat are having graphical issues/freezes and reboots... I don't think it's anything I'm doing.

So, keep in mind this is a beta ROM for now and is not stable. If the problem persists when SlimKat is out of beta, I'll resume the hunt.

New release in the next few days....:good:

EDIT: " (devices with problems are still: maguro, toro, toroplus, crespo, galaxysmtd)" -slimroms.net

When it comes to graphics, we use the same graphics blobs and have the same gpu as crespo...
[Samsung Galaxy Player 4.0, 5.0] annoyingduck:
That issue (especially with mx) has been there in all builds 4.0+ on this device. Sw encoding temp fixes it. Fixing that would be sweet, but it may not happen....
[Samsung Galaxy Player 4.0, 5.0] :
I'm sure this will get fixed upstream because there are supported devices that have the issue:highfive:
[Samsung Galaxy Player 4.0, 5.0] annoyingduck:
Check this out..."The chamber has been opened"

https://www.youtube.com/watch?v=jWsY9wAq_9M&feature=youtube_gdata_player
[Samsung Galaxy Player 4.0, 5.0] :
Hmm... looks interesting...:p Should have beta 2 out today.... then we will see!:good:
[Samsung Galaxy Player 4.0, 5.0] :
NEW BUILD

Download: Slim-venturi-4.4.2.beta.2-UNOFFICIAL-20131231-1223

Slim-venturi-4.4.2.beta.1.9-UNOFFICIAL-20131223-1727 --> Slim-venturi-4.4.2.beta.2-UNOFFICIAL-20131231-1223 changes

Meticulus/slim_device_samsung_venturi

[*]2013-12-31: boot logo: revert to stock boot logo <@Meticulus>

Meticulus/android_kernel_samsung_venturi

[*]2013-12-30: init: Load modules a little earlier <@Meticulus>

[*]2013-12-30: cleanup: BoardConfigCommon.mk <@Meticulus>

[*]2013-12-30: twrp: Custom graphics not needed by twrp <@Meticulus>

-As of SlimKat beta 2

[*]2013-12-30: Merge branch 'kk4.4' of https://github.com/Meticulus/slim_device_samsung_venturi <@Meticulus>

[*]2013-12-30: boardconfig: Align graphics values with Slim crespo device tree <@Meticulus>

-We have the same gpu as the (Nexus S) aka crespo.

[*]2013-12-29: Update README.md <@Johnny Dennis>

Correct a little derp

[*]2013-12-29: Update README.md <@Johnny Dennis>

Update for SlimRoms

[*]2013-12-26: LVMv2: change default_data_alignment <@Meticulus>

-According to https://raw.github.com/steven676/android-lvm-mod/master/HOWTO-MOD
the default_data_alignment parameter should be our devices
"erase block size" and that the erase block size can be found by
cat /sys/block/mmcblk0/device/preferred_erase_size. I get a value of
2097152 which is exactly 2MB.

-I looked for this value before the initial LVMv2 implementation but
was unable to find it.

[*]2013-12-26: vendor setup: add eng <@Meticulus>

[*]2013-12-26: charger: disable vblank. <@Meticulus>

-Doesn't really do anything now but might assist in charge mode
seg fault.

[*]2013-12-26: init: Install busybox in sbin and adb shell before mounts. <@Meticulus>

-This commit is similar to https://github.com/Meticulus/slim_device_samsung_venturi/commit/a2d1425fdc22b28c143bc150274e1cb5f45cde28
in that it enables adb shell before /system is mounted but
this is for normal boot instead of recovery.

-This also installs busybox in /sbin (all symlinks) for diagnostic purposes
such as getting adb shell for logs when system wont boot.

-This commit also fixes the above mentioned commit by placing busybox in /sbin.
I was looking for the most prudent way to do that, and I think I've got it.

[*]2013-12-26: overlay: use original samsung logo. <@Meticulus>

-The kernel has the CM galaxy (s) logo in it which seems odd when
running SlimKat. This file restores the original samsung boot logo.
[Samsung Galaxy Player 4.0, 5.0] raventothepowerofpi:
Camera

The back camera is getting closer and closer to working as I see it :D I can see it completely working a week or 2 from now :)
[Samsung Galaxy Player 4.0, 5.0] :
No one is working on the rear cam atm, so I seriously doubt it....:)
[Samsung Galaxy Player 4.0, 5.0] :
I am hopeful that this patch will resolve the graphics/reboot issue https://gerrit.slimroms.net/#/c/1287/

EDIT: I'm testing it now - According to my test conditions I should have had graphical glitches by now, HAVENT HAD ANY!!! :good: Going to keep testing for awhile...

EDIT2: Still no graphic glitches or reboots!

EDIT3: I think the graphics issue is resolved, plus something else to look forward to in the next release! (see attached):victory:

EDIT4: Just got Spirit FM working!

EDIT5: I made progress with the rear camera, It's a compromise but it is something ??? ;)
[Samsung Galaxy Player 4.0, 5.0] :
Man, I got alot done today! The next release is going to be awesome! I can't believe that I actually made progress on the rear camera. It's not much, but I can snap photo's on the rear cam with the stock camera app and Camera MX @ 640x480 and 800x480. It's a little wacky though, sometimes after the photo snap, preview gets wonky....
[Samsung Galaxy Player 4.0, 5.0] heet1:
I have a question. So I was flashing 4.4.2 Beta 2, yet i am not familiar with TWRP, and after I wipe factory/data reset and wipe system and data, I flash the .zip, yet after i press reboot system it says that it has no OS installed but the flash says it was successful... I do not know what to do. any help would be appreciated thanks :)
[Samsung Galaxy Player 4.0, 5.0] joemhewitt:
:)

Sent from my zx spectrum
[Samsung Galaxy Player 4.0, 5.0] :
Yeah, I know! I had given up on the camera. I worked on it for a long time and never got anywhere but lately, I had this crazy idea and [MENTION=5338948]raventothepowerofpi[/MENTION] 's comment got me thinking again and I decided to take a stab at it....
[Samsung Galaxy Player 4.0, 5.0] :
Got the flash working on the camera! Probably doesn't work in Torch... YET! ;)
[Samsung Galaxy Player 4.0, 5.0] Mevordel:
Is the source uploaded? I want to decypher this magic!