yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Player 4.0, 5.0] iJimaniac:
I have similar issues with it getting to 100% then starting to drop, and it has been around since at least JB 4.2. To get it to charge again, I just have to unplug and replug it in.

Concerning the powering off, I may be having that as well, although with me I'm pretty sure it's just freezing, not actually shutting down (which is why it requires removing the battery or holding the power button for around 10 seconds). It seems to be most likely to happen after unplugging from the charger and then turning the screen off.

Up until now though, I was thinking it was something with tasker, which I have disabled and have yet to see it occur again. I'll let you know if it shows up again.
[Samsung Galaxy Player 4.0, 5.0] WHib96:
Well I don't, nor have I ever had tasker installed, so that's definitely not the case for me.
[Samsung Galaxy Player 4.0, 5.0] trainman261:
I've got pretty much the same thing - at least with the battery. It often will go to 100%, then eventually (sometimes not right away) start dropping. Sometimes, though, it does hit 100% and stay there - I still don't get a notification or anything (maybe that feature was removed in JB or was just something Samsung?) - but the battery icon does change from a charging icon to a plain old full icon. What I haven't checked is if it makes a difference which battery I'm using - I have 1 stock and 2 third-party batteries. It hasn't been a huge deal for me, I've set AutomateIt (basically like Tasker) to fire off a notification when the battery hits 100%. It's not perfect, but it's good enough for me. As with it randomly restarting, I've had that three times - interestingly, all three times seem to have been when I was biking and using Google Maps (I have a waterproof phone mount on my bike). One other thing I've had was me not being able to wake it, meaning I had to hold the power button for 10 (?) seconds to restart it, but that only happened once, maybe it was also me not realizing that it sometimes takes a little longer to turn on when you allow your lock screen to rotate :) . I have to say, this is still more stable than the default GB build, which crashed so often... And I'm not even on the newest version with all the under-the-hood optimizations - if I'm not mistaken, I'm still on the first 10.2 build (I didn't have time to upgrade yet).
[Samsung Galaxy Player 4.0, 5.0] iJimaniac:
Yup, same experience as you with the battery. Concerning the not being able to wake it, which is what I have been experiencing a lot, I think I have discovered it only happens when overclocked (I had tasker set to overclock automatically, which is why tasker was causing the freezing for me). Also, it only happens when unplugged, which makes me think it is something with deep sleep+overclocking. So far I haven't had it happen again after disabling overclock.
[Samsung Galaxy Player 4.0, 5.0] daniel644:
the wake issue for me only occurs if I use the 1.4 GHz, its fine on 1.2 GHz, so I think it may be a voltage issue or something with that profile.
[Samsung Galaxy Player 4.0, 5.0] trainman261:
I haven't played around with OC or voltage, so for me, it doesn't have anything to do with that. Again, though, I am not on the latest version, so it could be that this was fixed (or maybe not, if you are still having it, it could be unrelated to OC).
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
Hey guys, new update to the OP (09/29)

I resized the /system partiton from 385 to 445 mb (we were missing a bit of space before). Also fixed the bt internet tethering.

Other than that, nothing really, it's mostly bugfixes (upstream changes) and smoother feel.

Enjoy!! :)
[Samsung Galaxy Player 4.0, 5.0] dorfd1:
Installed just fine. No brickage because of partition resize.
[Samsung Galaxy Player 4.0, 5.0] WHib96:
Does /system or /data need to be wiped since this has some /system parition changes? Or can I just wipe the cache and dalvik and be fine?

Thanks!
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
Well in theory, I was fine flashing over. Thing I forgot it that I moved the efs partition and maybe some files will get removed from it. Just be sure to backup in case you haven't and restore the backup so everything will work.

Envoyé depuis mon Nexus 7 avec Tapatalk 4
[Samsung Galaxy Player 4.0, 5.0] meats:
my home button no longer works with the new flash, any ideas?
[Samsung Galaxy Player 4.0, 5.0] goldflame09:
i would restore your efs an do a clean flash, wiping system, data, etc
[Samsung Galaxy Player 4.0, 5.0] trainman261:
What's the story with FM radio? Is there a risk of breaking the speakers like with the GT-i9000 on spirit fm (or should there be one)?
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
I don't know, I don't play fm radio with speakers. But the ypg1 having nearly the same hardware as the i9000, there should be maybe a risk of Breaking them.

Envoyé depuis mon Nexus 7 avec Tapatalk 4
[Samsung Galaxy Player 4.0, 5.0] dorfd1:
I never had problems with the speakers with FM radio. I would use the digital audio method.
[Samsung Galaxy Player 4.0, 5.0] :
@zaclimon

As I said, the first thing I did was grab the libcamera folder from CM aries 10.2. Then I did a diff to see what changed. After that I removed some preview initialization stuff and that got it up and going...
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
Oh well. As for ourselves we're basing from p1 because we have the same camera. Thing is FFC was working when we were using the 2.6 kernel. Then taking a picture with FFC was borked when we began to use the 3.0 one. I'll continue to investigate that basing on your commits.

Thanks again. :good:
[Samsung Galaxy Player 4.0, 5.0] :
Let me just add one last thing. [MENTION=329237]inur[/MENTION]ait's cm-10.2 for the YP-G70 has the same issue on the FFC. Preview worked but it would not save images. I didn't change anything that would fix that. Rebasing the camera HAL is what fixed that. All of the FFC commits are little things like fixing orientation and taking out code that was ment for another device.:good:
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
New update available in the OP (10/14)

- Android 4.3.1 (JLS36I)

- CWM updated to 6.0.4.4

- Updated the libcamera (now it won't crash when trying to go from front cam to back cam, but there's a flash mode now... Just nevemind it)

- Nothing new really aside from that except upstream CM changes

For the front cam, it looks like the P1 guys (The original galaxy tab) are having the same issue as us. I'm contacting their devs to see if it can be resolved, if not then well I guess we can leave like it. (it can still record and take panoramas though)
[Samsung Galaxy Player 4.0, 5.0] dorfd1:
I installed this ROM. Facebook, twitter and linked disappeared from the list of accounts in settings. The apps work fine.

Focal is also missing.
[Samsung Galaxy Player 4.0, 5.0] Choucas06:
Hi all,

I've installed the new version and no issue until now. As always, it works perfectly.

I have no sync with facebook, but my other accounts (twitter, linkedin, skype, google) did not disapeared from settings menu like dorfd1.

Focal was missing also on the previous version, but as this application is too slow with our device, it's not really important.

And thanks for the impulse kernel too :good:
[Samsung Galaxy Player 4.0, 5.0] joemhewitt:
They aren't in cyanogen mod. And this build isn't recent enough for focal.

Sent from my zx spectrum
[Samsung Galaxy Player 4.0, 5.0] :
I'm not sure if this is why it's missing but focal is available in the playstore....;)
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
I didn't feel the need of multi quote you all so here it is. The reason as of why focal got removed is because it's dev removed it from CM and quitted it at the same time. (CM) the cause of this is mostly licensing stuff due to cm becoming a company. I could still build it but honestly it was running painfully slow on our devices. That said like [MENTION=4400604]Meticulus[/MENTION] said, you can still download it from the play store.

About the Facebook thing, it's the first time I see something like this. Let's in the next days if this got fixed upstream. (either this or its a problem with the Facebook app)

Envoyé depuis mon Nexus 7 avec Tapatalk 4
[Samsung Galaxy Player 4.0, 5.0] Emperor Newo:
Omg hoping that the front camera can be fixed!!! So far its the only reason i haven't gone to one of these ROM's, I just use the front cam to much to loose it (e.g Snapchat) Hope you can work it out!! But thanks anyway for such an awesome looking ROM, I am seriously thinking about flashing it anyway, no matter the camera :D Out of curiosity do you know whats wrong with the camera to begin with?? I'm just curious is all :)
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
Well the front cam is working the only thing that isn't working is that you can't take pictures with the stock camera app (works great using camera zoom fx) . Snapchat looks great so far only thing is that it is from the side while with the stock app, it looks great though. Also the back cam show some wonky stuff with snapchat as it looks like it take a screenshot of the preview. I'll look to make a zip for those want to use external apps and don't want their front cam to look weird.

Also I don't know what's wrong with the camera as we're based from the galaxy tab drivers. So I think of the issue are fixed right there, it will come to us as well.

Hope it helps! :)

Envoyé depuis mon Nexus 7 avec Tapatalk 4
[Samsung Galaxy Player 4.0, 5.0] theraf:
any thoughts on releasing other roms like slimbean?
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
Hmm well you can build or port it if you want. I wanted to build it 2 weeks ago but I didn't find a reason to use slim as I find cm plenty enough.

Envoyé depuis mon Nexus 7 avec Tapatalk 4
[Samsung Galaxy Player 4.0, 5.0] Emperor Newo:
Thanks a bunch!!! I'll just check the installation video (to make sure i understand it) then i will download this great looking ROM!!!
[Samsung Galaxy Player 4.0, 5.0] Emperor Newo:
Ok I'm having a few issues.... I'll Explain step by step what i have done so far.

1. Put all files on my internal memory and flashed terrasilent (I'm coming from R.E.D.D, which is pretty much stock)

2. Flashed the cm9 preflash zip.

3. Flashed the Cynagenmod zip.

Ok this is where things get weird, I have tried it multiple times (luckily i can still get back to stock or my ROM beforehand) when i start the flash it does what was happening in the video, it reboots three time, but doesn't continue the installation. I try to continue the installation myself and it will install without much fuss... but then when i reboot it just hangs at the Cynagenmod screen (the one with the moving circle). It doesn't go any further... it seems like it just can't. I'm really confused and i hope this is something easy to fix and just something that i missed. Please help!!! I got my original files all from your first 2 posts, did i miss something?

*edit*

dw, I think i know what i did wrong... I'll see how it tuns out in a sec and keep you posted.

*edit*

Ok i pretty much stuffed up the prefalsh zip, i used one i had downloaded for the old 4.1.2 paranoid android by accident. It's working now but i hard to flash the zip 3 times... but still yayyy it works now!!!
[Samsung Galaxy Player 4.0, 5.0] Emperor Newo:
Ok I feel like a complete noob now... My middle button for the US version of the galaxy player 4.0 doesn't work at all. Have i forgotten something?
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
Your efs isn't full completely good then. You can take your backup in sdcard/backup/efs and then copy it to your /efs folder, then it should work.

Envoyé depuis mon Nexus 7 avec Tapatalk 4
[Samsung Galaxy Player 4.0, 5.0] WHib96:
Zaclimon, this is not the case with me, and I'm running the latest version of the rom and impulse. My back camera (the one that is NOT facing my face) works absolutely fine. No problems with it. However, the front facing camera (the one facing my face) does not hardly work at all. In Camera Zoom FX, I can switch to the front facing camera but the preview is rotated sideways, so for example, in the preview the top of my head is facing the right when it should be facing upward.

I also am unable to take any photos on the front facing camera, even when in Camera Zoom FX. When I try to take the picture, the preview just goes black and no photo is saved.

Maybe I misunderstood you, but this doesn't seem to be what you were explaining in your post. Is anyone else experiencing this? A reflash might fix this perhaps.

Hoping the camera can get fixed soon :) It's pretty much the only major bug left :)
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
Maybe it was an isolated case from my side but indeed the front cam while taking a picture isn't working. However the only thing I can say is using something like fastburst to take a picture with the front cam. As I said in my other post, I will try to do something related for external apps getting sideways looks.

Also [MENTION=4757337]goldflame09[/MENTION] I've seen your pull request concerning pac and the dynamic changelog, I'll incorporate it in impulse r4.1.
[Samsung Galaxy Player 4.0, 5.0] goldflame09:
Alright cool [MENTION=4000778]bbelos[/MENTION] said that maybe we should have a separate pac branch cause he doesn't know how it'll effect cm builds
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
Hi it's yet again another new build in the OP (26/10)

It's basically the newer and last kernel version of 3.0.x series,(3.0.101) CM changes like phasebeam wallpaper and upstream fixes. I do find it a tad smoother but it may vary.

I will do maybe 2-3 other builds before stopping with cm-10.2 if google decides to put a release date for KK... After this the work will begin for KK when it will be due.

Enjoy!! :)
[Samsung Galaxy Player 4.0, 5.0] Emperor Newo:
Ok i have had it working for awhile now and i wanted to share some of my own experiences with this ROM. First of i would love to thank you for such a wonderful port, all the features is quite amazing and so is how smoothly it runs. Apps work great, once i fixed my efs the home button started working smoothly :) The only thing plagueing my system now is the charging (I know, I'm an idiot, and unlucky)... Sometimes it says its charging but it will still drop down in percentage. It happens even when I'm not using it, I believe it has something to do with DSP sound manager but my actual battery statistics point towards the display (which makes no sense when its sleeping). So yeah if you can work out why the DSP is doing this (or whastever it is, I'm probably wrong) then just say. Apart from that, EXCELLENT!!!!
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
Hmm I don't know what to say. Actually I've seen people talking about this issue. My guess would be maybe there's a wakelock causing it to drain battery while sleeping. As for myself, I've never seen this issue because I'm mostly charging while the device is turned off.

Envoyé de mon Nexus 7 en utilisant Tapatalk
[Samsung Galaxy Player 4.0, 5.0] dorfd1:
installed this rom update.

facebook, twitter and linked are still missing from the accounts list even though the apps still work fine.

taking a picture using the front camera causes the camera app to crash.

pressing status under about tablet causes settings to crash.

the messaging app force closing appears to be fixed.
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
1. The facebook thing is because of it's crappy API that isn't following google's guidelines, I could cherry-pick the fix but I want to keep cm as clean as possible

2. That's been known since CM 10.1... Otherwise I would say it has been fixed

3. My settings doesn't crash when I try this, must be from your side. Can I see a logcat to see what's this error about?

4. At last it's been fixed! :)
[Samsung Galaxy Player 4.0, 5.0] dorfd1:
I have patched in the combined bar using autopatcher. I will have to see if restoring the stock 4.3 ui fixes the settings crash issue.
[Samsung Galaxy Player 4.0, 5.0] trainman261:
Just out of curiosity: would it technically be possible to get OpenGL ES 3.0 on a device like this? I'm not suggesting anyone work on this, because I have no idea how it would work performance-wise, if at all. I just know the "device manufacturer" needs to support this, but I'm wondering if the hardware needs to support it or it's a drivers issue. I remember, back in the days when I was using my 2nd gen iPod touch, I got the iOS 4.0 update, but being on a 2nd gen device, I was locked out of multitasking and wallpapers. I was able to get multitasking activated by changing a couple of files on the device, but on iOS 4.3, Apple tried to lock those devices out of multitasking, even with changing the file, by using those device's incopatibility with OpenGL ES 2.0 (arrrrrggghh! one of the many reasons I got the player to replace this!). The way to get it back was by flipping a switch in a different file, basically telling the system that it supported OpenGL ES 2.0. I'm not sure it properly supported OpenGL ES 2.0 - it definitely did have bugs, including odd lines and other things in certain interfaces - but it did enable the multitasking animations, meaning you could multitask without it crashing at the multitasking animation. Long story short, I'm wondering if it would be technically possible to enable OpenGL ES 3.0 on our devices, or any similar devices - but by no means am I suggesting or requesting it.
[Samsung Galaxy Player 4.0, 5.0] dorfd1:
Flashing stock ui back did not fix the settings crash issue. Also the phone app is missing from the app drawer.
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
Opengles3.0 support is decided by the hardware and not the software. Because our gpus are really old, it doesn't support it and only restricted on the 2.0 version. Even if I define it on the device configuration, it could either do anything because it doesn't satisfy the requirements or odd things would happen.

Hmm maybe something happened with upstream causing some devices to not have the phone app anymore. (my guess would be because our device is defined as a tablet still)

Envoyé depuis mon Nexus 7 avec Tapatalk 4
[Samsung Galaxy Player 4.0, 5.0] dorfd1:
android 4.2 and above for tablets has a feature in it that allows for multiple user to have there own profiles. we do not have that feature because I thought you built the phone version of the rom, using the tablet thing as a device id hack to get play store working.
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
I don't know how completely the stuff works. (there's some variables that enters as of what uses multiple users and what not) However, that thing is only supposed to say to app like play store that the device is a tablet which is why there was some kind of deviceid hack.

Envoyé depuis mon Nexus 7 avec Tapatalk 4
[Samsung Galaxy Player 4.0, 5.0] iJimaniac:
In case it's unclear, I had the phone dialer in 4.2, but haven't seen it again since upgrading to 4.3. Something else I've noticed in 4.3 is the battery life seems to have degraded. Looking around online though, it seems perhaps this is a common issue with 4.3, and not device specific? Anyways, good work as always zaclimon, and I look forward to 4.4! XD (actually I'd be more than satisfied if you completely dropped development right now, as you have already made the 4.0 a new device!)
[Samsung Galaxy Player 4.0, 5.0] trainman261:
Alright, another question, sorry for spamming this thread in recent times :D

I've had a lot to do lately, so I'm on an earlier build, but it just occurred to me that my issues might be EFS-related. For one, my device has the oddest ID in ADB (something like ABCDEFG1234), wasn't recognized by the backup and restore system when I booted it up - none of those are big issues, but here is the issues that is actually getting in my way every once in a while - none of the default interactions with my windows 7 computer over bluetooth work - when I try to enable any of the services in the control panel, I get "the parameter is incorrect". On the other hand, a third-party app which I use to control my computer, BTremotePC, works fine. I'm won't get around to doing anything of that sort for the next while, but should I do an EFS restore some time? I have millions of EFS backups, your guys' warnings worked ;) .
[Samsung Galaxy Player 4.0, 5.0] dorfd1:
Now that android 4.4 is released, are we going get some more cm10.2 builds, or are we going to wait for cm11?
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
Hmm efs won't do anything for the moment. The only thing I can say would be keep the app for the moment.

As I said a few posts earlier, I'll do 2-3 Builds before considering going to cm11. Anyway cm isn't going to release something soon so let's concentrate ourselves with cm10.2 for the moment.

Envoyé depuis mon Nexus 7 avec Tapatalk 4
[Samsung Galaxy Player 4.0, 5.0] WHib96:
There isn't really much left to do on cm10.2 though is there? I mean the only couple bugs I know of that are left are the camera and the discharging while plugged in thing.
[Samsung Galaxy Player 4.0, 5.0] goldflame09:
ok literally the source was out an hour ago. cm is fast but not that fast. dont expect anything for a bit.

NO ETA's
[Samsung Galaxy Player 4.0, 5.0] WHib96:
Lol sorry. I should have stated that I wasn't trying to promote kitkat development. I was just wondering what might be left to actually improve on JB, not push you guys into porting kitkat. I'd be fine if development stopped at JB honestly.
[Samsung Galaxy Player 4.0, 5.0] dorfd1:
With kit kat's low memory requirement, I think android 4.4 may perform better on our devices. I can wait for the release.
[Samsung Galaxy Player 4.0, 5.0] iJimaniac:
I think the misconception here is that anyone CAN do anything right now. Zaclimon and the others have to wait for Cyanogenmod to be updated to 4.4 before they can work on porting it. Additionally, I believe there are sources and such that need updating from other teams before anything can be done. I'm not sure I have this last part right (I don't really have a clue about the magic that goes on behind the scenes), but I think that is the case.
[Samsung Galaxy Player 4.0, 5.0] goldflame09:
There is a plentiful amount of updating that needs to be done before we can do anything
[Samsung Galaxy Player 4.0, 5.0] trainman261:
OK well in case anyone else has this problem, pairing and unpairing a couple of times fixed the bluetooth issue.
[Samsung Galaxy Player 4.0, 5.0] Emperor Newo:
Ok it's good to see that this thread is still going to be active for awhile :) I've been brainstorming a couple of ideas that will fix my (and probably others) discharging while charging problem, I've looked at the wakelocks and nothing has really jumped out at me which suggests that it is the problem. Do you guys think simply wiping system data, davlik etc. will fix this problem?? I'm willing to backup my apps and stuff and try it out soon (but school has gotten in the way), so do you think this may help?? or just be a waste of time??
[Samsung Galaxy Player 4.0, 5.0] goldflame09:
Wont fix it but might make it less drastic
[Samsung Galaxy Player 4.0, 5.0] iJimaniac:
I haven't really been having the battery drain at all recently (that I've noticed). I can't think of anything I've done that would have fixed it, although I do use daydream, which might possibly prevent the bug by keeping the device awake.
[Samsung Galaxy Player 4.0, 5.0] goldflame09:
I had that (look at attached) the past few days. Look where its charging. Drastic drops
[Samsung Galaxy Player 4.0, 5.0] WHib96:
I've had the charging/battery dropping issue myself. I ran a test today by letting it charge from ~15% to 100% and then let it sit for a couple hours. It actually seemed to charge up and then stay at 100% the whole time. Not sure what the deal is and why it happens only sometimes.