yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Player 4.0, 5.0] soulshinobu:
Yes, definitely. I had won a Galaxy Player 4 from a vending machine game at the mall after seeing a movie with a friend of mine, didn't spend a lot of time figuring out how to root it, but man did it take me a while to figure out the heimdall stuff, and that I had to uninstall kies every time I wanted to do something with it. It was extremely time consuming for me as a nooblet, especially since I had already been used to how I did things with the GS2.

Yes, basically. I don't mind though, it is a quick and easy process. As for updating a ROM, a simple clearing of cache and dalvik cache was enough to be able to update.

Sent from my SPH-D710
[Samsung Galaxy Player 4.0, 5.0] potatoman83:
My bad :D I'm gonna try this over therafs PA port. I'll tell ya what I think!
[Samsung Galaxy Player 4.0, 5.0] goldflame09:
Yes please let us know because I don't know if I actually want to stick with theraf pa rom. Possible for me to return to nebula.

Sent From My YP-G1 running Nebula beta 1
[Samsung Galaxy Player 4.0, 5.0] potatoman83:
Wow...well I would switch to this except the img file given to get back to recovery doesnt work for me with the PA2 port...just sits at the samsung screen. So Im stuck with PA2. I flashed the img in heimdall...it stayed on Samsung screen. I flashed the rom img..it booted back to PA2. I tried 3 other img's, and it sat at Samsung screen..so It would appear I will have no choice but attempt going all the way back to GB.
[Samsung Galaxy Player 4.0, 5.0] daniel644:
I went over the Heimdall vs. Odin driver issues in the video to some extent, first off don't bother with Kies AT ALL go here http://xdaforums.com/showthread.php?t=961956

1. Download drivers from the link above and install drivers (uninstall old drivers if any are installed and reboot)

2. Put player in DOWNLOAD MODE and plug into USB on one side of Laptop

3. Now setup Heimdall by opening the program ZADIG.exe that is in the driver folder of your Heimdall folder

4. In Zadig click Options and select List All Devices then from the dropdown select whatever the samsung device is and click "Install Driver"

5. When that finishes any USB on that "stack" (for laptops, that side) can only be used for Heimdall

6. Unplug player from that side of laptop and plug into USB on other side (keep player in download mode) and wait for computer to configure drivers.

7. this side is now your Odin side and now you can use both programs without having to install and unistall anything.
[Samsung Galaxy Player 4.0, 5.0] goldflame09:
Instead of returning to gb there is the option of installing the rom from cwm6. It works but just takes a few more steps to install.

Sent From My YP-G1 running Nebula beta 1
[Samsung Galaxy Player 4.0, 5.0] potatoman83:
That's what I'm trying to do except the img to flash in order to get to CWM isn't working. I tried from 3 sources. I think its this PA. Cause the first build of it worked with img.
[Samsung Galaxy Player 4.0, 5.0] daniel644:
use winrar or winzip or whatever you use to "pull" a copy of the boot.img from the linromV2.zip and use heimdall to flash it like normal there where changes that where kernel related in the latest Linaro build that is what the latest build of this is based on so you can't use the same kernel from the older build.

In-case what I just said doesn't make sense I have attached the boot.img that goes with the version 2 build.
[Samsung Galaxy Player 4.0, 5.0] goldflame09:
Thats not what I am taking about. Just try to get into the recovery which you have now. Don't try flashig the build switch kernel. Use the one you have now. Just power off and go into cwm6.

Sent From My YP-G1 running Nebula beta 1
[Samsung Galaxy Player 4.0, 5.0] potatoman83:
You can't normal reboot to recovery with these..I'm gonna try the img that's posted. BTW tell theraf about that.
[Samsung Galaxy Player 4.0, 5.0] hanthesolo:
Another update for you guys. Firstly, thank you everyone who's been providing support on this thread, as I truly don't have time to provide it adequately :).

As a semi-related side not, my sister's KF arrived, and is happily running fully linaro-optimized JB and a 3.0x kernel (basically what we hope to one day provide to you guys). Just comparing it's usability to our device (as it has a PVR 540 and a few other similar components), has helped to identify our bottlenecks with solid evidence. Perhaps it shows hope for our future, but the KF is as smooth, if not smoother than my N7, which is quite impressive (hats off to hashcode!).

There seem to be two bottlenecks: CPU and flash for us. One we can do something about, one we can't. CPU seems to be what is bottlenecking us ATM, and unfortunately, that pretty much rings the death-knell for our device, because there isn't anything we can do about it. I'm personally throwing my hopes on a 3.0x kernel as our saviour, as JB will not provide as huge a boost to us. Unfortunately, we're hitting the ceiling of what our device can do right now.

To be honest, there's onlo so much software can do before we're physically limited to what we can do. Since we're not a tens of devs community like the I-9000, we physically dont have the manpower to track down every last optimization there is to offer for our device. I guess that what i'm trying to get at, is that post-4.2 (maybe 4.1.2) android builds will probably NOT be usable on our device, at least not more than our current builds.

Linaro? Been there, optimized the heck out of it, and maxed out that possibility. 3.0x kernel? Possible, but seems more unlikely by the day, due to the fact that we need experienced C coders and experienced devs to help us, and since Oisis has mysteriously dissappeared, I don't know if this is feasible. JB? To be honest, we will not see a big boost from this. What we will gain in UI usability we will probably lose in system resources, and CPU clocks that should be sent keeping our apps running. Smaller kernel tweaks? Outside of a completely new, faster filesystem, there isn't much that will help, outside of some minor I/O tweaks. Am I wrong? Maybe, but this is all speculation. I'm not trying to be defeatist or pessimistic, but the reality is that our device is about as good as it gets right now, unless we find some magic sauce that can pull and extra CPU core out of thin air, or double our already insanely hacked up I/O speeds.

This doesn't mean the end of development, of course. There's always rom ports, or cool new features to work on, even though we have essentially maxed out our usability. I do sincerely hope though, that we can squeeze the last 15-20% out of our devices, before our last devs (including, unfortunately me eventually) fade out of the picture.
[Samsung Galaxy Player 4.0, 5.0] ti-pich:
I put all my hope on the 3.X kernel. I should help zaclimon with it when he is ready later in december. Also if you need some help with C/C++ you can ask me and I take a look at what I can do. I would really like to help more but I don't know much in android.
[Samsung Galaxy Player 4.0, 5.0] goldflame09:
I was afraid that this would hit us like a brick wall someday. But I guess to give you a boost in bugs, because theraf used your rom as his base, I thought I would give you the list of bugs also. Don't know if they apply to you but here they are:

List of bugs that I have found in this rom along with just a general report on it.

Hw acceleration: games run much smoother on this than they have in the past.

Browser: the stock browser works fine but chrome and dolphin html5 browser do not work.

Settings: the only problem that I have found is in the battery section. As shown in the one of the attached screenshots, it does not tell you which app is using the most battery life. Just gives you the graph and that's it.

Battery: battery life is slightly better than before. The other screenshot is of my battery.

Other; for some reason, weatherbug crashes after I install it and try to open it. Also not a big issue but the background image for system apps such as settings is gone. The only reason I mention this is because I like the image.

Otherwise, this rom is great and full if features. Keep up the good work and this rom has a ton of potential when it becomes fully optimized. Thank you for this rom port han and I will continue to reply bugs.

Btw: anyone else who has this rom installed, feel free to report bugs when you find them. Then more bugs that are reported, the better chance that they will be fixed in the next release. plus i actually dont have this rom installed. One ground rule I have to make on that, is sent report the same bugs over and over again. If one person already reported it, DON'T report it again.

Hope this somewhat helps

Sent From My YP-G1 running Nebula beta 1
[Samsung Galaxy Player 4.0, 5.0] hanthesolo:
Thanks, this hsould help me to track some minor stuff down :). As for HW acceleration (relating to the browsers and weatherbug), which build are you using? I'm running chrome just fine right now, and HW acceleration is working just fine.
[Samsung Galaxy Player 4.0, 5.0] goldflame09:
i am using the paranoid android but since theraf is using linics v2 as his base, might as well tell both of you. as for chrome, its not working on his build

i forgot the screenshots so here they are
[Samsung Galaxy Player 4.0, 5.0] indyssee:
Honestly not trying to sound ungrateful (because I'm very grateful) but wouldn't having a working recovery, BT, etc be considered optimizations? I'm astonished you guys have been able to get AOSP based ROMs working on the 4.0, but I think most would consider our device adequate, performance wise, and would much rather squash those remaining bugs than worry about the performance ceiling.

Again, I hope this doesn't come off as rude. Very impressed with the work and effort of the whole team.
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
I don't know for the others but I don't take it personnal. Also I would say that I prefered myself too to work on other things before going on linaro. But because it's han's project, don't put it together with nebula. :p
[Samsung Galaxy Player 4.0, 5.0] hanthesolo:
Hmm, i'm going to assume it's some weird issue on PA's side, because i'm not having these issues. If you can send me logcat/dmesg, maybe I can help theraf with that!

Haha NP, we need feedback like this to make it better :). I think zaclimon's working on BT, and i'm just fixing up smaller weirdness issues whenever I see them, so we should have things ironed out soon!

Yeah, this is a seperate project. Zaclimon considers it most beneficial to iron out all the bugs before concerning ourselves with performance, and I consider performance to be a priority at this point, now that we have a daily driver release. Nebula's supposed to be the "stable" base, and I just have an experimental base that I solely maintain myself.
[Samsung Galaxy Player 4.0, 5.0] goldflame09:
well I think that I am going to stay on PA for now and if things (bugs) get the best of me, which I hope they won't, ill switch to your rom. han, if you do want me to flash your build at some point so I can find bugs for you, I will but it wont be right away.
[Samsung Galaxy Player 4.0, 5.0] potatoman83:
How did you accomplish youtube /Netflix to work?
[Samsung Galaxy Player 4.0, 5.0] goldflame09:
Didnt you say your rom wasnt working right anyway? I think the way to fix your device is to go back to gb and re do the install. You also could try, but I don't think it will work, going I to setting and under backup and restore, do a factory reset.

Sent From My YP-G1 running Nebula beta 1
[Samsung Galaxy Player 4.0, 5.0] potatoman83:
Got to finally try to flash your rom. However I recieved "assert failed: run_program("/tmp/convert_to_mtd.sh") == 0"
[Samsung Galaxy Player 4.0, 5.0] crancpiti:
You have to install the ROM twice per CWM

1. in the Old CWM

2.Reboot and Flash it in the new CWM that will install it ;)
[Samsung Galaxy Player 4.0, 5.0] da1writer:
Wow is the words I got to say, bravo for linICS V2,it's absolutely wonderful! Finally a rom that works and works well for the 4.0! For the past couple months I've been stuck with the Ethereal rom, thinking forever I won't be able to use the apps I like on Android due to horrible ram management of the rom/GB. The only way to even enjoy GB roms was to hide the problems with launchers (Ethereal used golauncher, IcyFusion used Holo Launcher). I didn't bother using my 4.0 for games because they would be unplayable due to slowness, crashing, or freezing - same went for browsing the internet off the 4.0 - a horrible experience that required a very lite browser like Boat mini to do menial things. I ended up just sticking with Ethereal due to battery life increase, so I mainly used my 4.0 for my music and podcasts only.

Fast Forward to today after flashing linICS v2 and things have turned to the best experience I've had with a Rom on 4.0! Absolutely fast, Ram management is fantastic, All my apps that didn't work [well] before now run fantastically! Chrome is a bonus to being able to work on the 4.0 in general but Dolphin (and Beta) run extremely well on the 4.0 with music playing in the background [via the tunein app], again absolutely wonderful is the word I can only describe it as I could never use a Heavy Browser like Dolphin with music playing with it on any Gingerbread rom! Games run great as well - I can finally play Dead Space with no problems! You guys did a fantastic job on this.

While some sacrifices had to be accepted by me when jumping to this like no camera atm, it wasn't enought o be a deal breaker as I rarely used the camera anyhow (same with the bluetooth). I'm still fooling around with the rom but the only way I'll even change to something else is if you guys upgrade to a newer version (like Nebula went to linICS). Hope to see a V3 soon but I honestly don't know how you guys could improve this. Games, apps, and overall system of the rom itself run extremely well!

Would like help with something though hanthesolo or anyone. What is the recommended governor and i/o scheduler are you guys using? I'm using ondemand and CFQ but maybe there is a better combo - using nofrills btw.
[Samsung Galaxy Player 4.0, 5.0] potatoman83:
Yep thats usually how they work..however it usually restarts itself..it isnt, so I rebooted it..and a locked at the Samsung screen.

The other ICS ROMs would error..reset themself into the new CWM. This isnt.
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
Even though i'm not the maintaner of linICS I do like the fact that you love the rom (as it's based from nebula or it's indeed nebula but linaro optimized). As for myself, I can't really do something but I'm using ondemand and sometimes smoothass as a governor and deadline as a i/o scheduler.
[Samsung Galaxy Player 4.0, 5.0] crancpiti:
Thats weird perhaps your file is corrupted?

Try redownloading if you have the time for it.
[Samsung Galaxy Player 4.0, 5.0] goldflame09:
That is a possible issue. The thing that I am thinking is your issue is the problem with you having to use a jig to get into bootloader. Don't know how exactly this may affect it but it could.

Han, attached is the logcat for chrome. Don't know where it is but here is the while thing. Hope it is useful.

Sent From My YP-G1 running Nebula beta 1
[Samsung Galaxy Player 4.0, 5.0] iJimaniac:
Does anyone else experience the bug where the power button doesn't work when powered off and charging? To power the device on, I first have to unplug the player, then I can power it on. I never noticed this bug with nebula, and it is obviously kernal related.
[Samsung Galaxy Player 4.0, 5.0] da1writer:
ut I force myself to ignore until I figure out how to turn the thing off

Thanks, I will try those two tonight in combination to see what benefits me more. Would like to ask two questions more though - with your nebula rom and this rom, the no services message at the bottom of the notification slide down menu is kinda weird. I'm sure this is referencing to 3g/4g/cellular service but RemICS rom has this removed - is this possible to fix/implement in the next release? Everything about the rom is tweakable and clean but this part I mentioned was a bit jarring for a bit, I ignore it for now though. The one thing that also irks me a bit and rolling to the second question - what the heck is that red border box that flashes whenever I do anything fast like scrolling through my twitter/facebook widgets and so on. It's a bit annoying and wondering how do I turn that off or is it possible to turn it off in a future update?

Would to thank you for the home button workaround it works wonderfully! Do you think the Home touch button will be fixable? Glad you guys turned off the lights in it too, I rarely bothered liking the buttons lighting up and I'm sure it's a great battery savings!
[Samsung Galaxy Player 4.0, 5.0] zaclimon:
For the no service problem, because Nebula is built directly from source, I don't modify it to keep it as *pure* as it should (android is a smartphone/tablet OS not a media player one ;)). I know it is bothering but for the moment I don't concentrate on it (supermaster decompiled the framework in order to remove this). Anyway it's a modification in the framework-res.apk. For the red border box, you need a simple modification on the build.prop. In the build.prop replace ro.build.type=eng by ro.build.type=user. Also Nebula is slower than linICS because it's not optimized by linaro and it has some older commits of the kernel (like 329 mb of ram instead of 357).

Hope this helps.

---------- Post added at 10:32 PM ---------- Previous post was at 10:32 PM ----------

Yeah, I've seen this too. Maybe it's related to linaro?:confused:
[Samsung Galaxy Player 4.0, 5.0] hanthesolo:
I've noticed some power button issues when it's off and charging (for some reason, the LPM crashes after displaying the initial charging indicator), but pressing the power power button long enough to force a restart fixed it. It may be broken due to some code that I had to remove to allow linaro to compile successfully, but it's not a major issue, so I may not get around to looking into it.
[Samsung Galaxy Player 4.0, 5.0] ShawnZ248:
After I followed the installation video, everything worked perfect.. but on the last step when it rebooted. it says ENCRYPTION UNSUCCESSFUL? reset tablet.. and when i click reset tablet.. it just reboots and the same error comes back. How can i fix this?
[Samsung Galaxy Player 4.0, 5.0] daniel644:
Check further back in the thread (might be in the Nebula thread) some other people had this issue, I believe the fix was a restore to FACTORY GB via the restore thread and then reflashing, you could try going back into recovery and wipe cache and dalvick and go to Mounts and Storage and "FORMAT /SYSTEM" then reflash the ROM and GAPPS and follow the install video from from that point forward.
[Samsung Galaxy Player 4.0, 5.0] goldflame09:
If you would look in the original post on the nebula thread the way to solve that is in there. I had the same problem and by doing what I did it fixed it. It involves going into recovery and wiping data then coming and flashing a gingerbread kernel and then going back to the ICS kernel. like I said full instructions are in the original post on the nebula thread

Sent From My YP-G1 running Nebula beta 1

---------- Post added at 09:41 PM ---------- Previous post was at 09:39 PM ----------

I I won't dispute that that's an option but my way of fixing it I believe is probably easier and less complicated

Sent From My YP-G1 running Nebula beta 1
[Galaxy S I9000 Q&A, Help & Troubleshooting] Grigoris0r20r:
Hello.i want to know what settings do you use on your SGS for a good battery life but without losing to much performance.

I use x-bean 3.0 with semaphore kernel v2.4.0s.

Share your configs if you like.thank you all!:):):D:D
[Galaxy S I9000 Q&A, Help & Troubleshooting] bruetje:
As I don't own a SGS but a + I probably have different settings, but what always helps for me is downloading JuiceDefender. If you don't know this app, you should try it:)

For example: You can imagine your phone uses some battery life to stay connected to 3g, wifi etc. One of this settings disables your 3g/wifi whenever you turn your screen of, and enables it when you turn it on. For me, this improved my battery life big time. There are settings which allow your phone to enable wifi once while, but that's all up to the options.

As for what the best settings are for a 'decent' performance is quite different to what you experience as a decent performance.
[Galaxy S I9000 Q&A, Help & Troubleshooting] Grigoris0r20r:
Really?thank you i will give it a try.but i need wifi to be working all the time.i know that use a lot of battery but my biggest problem is my screen.this is what drains ny battery.lol.now i have checked the auto feature for the screen.we will see.thank you for your quick reply and for your help! :thumbup::D
[Galaxy S I9000 Q&A, Help & Troubleshooting] AllexSCV1:
You shold try Advanced Task Killer (as a widget especially, easy to use) - see attachement. It kills your background apps, saving RAM, and batterty. You must have 100MB+ free RAM at least...

Also, if you're not using 3G, you should turn it off, because this is one of "the biggest problems" for battery... (same thing with Wi-Fi or bluetooth).

So...if you have at least 100MB RAM free, and a little usage of 3G and Wi-Fi, you should have 2-3 hours of "screen on" batterty-life
[Galaxy S I9000 Q&A, Help & Troubleshooting] Grigoris0r20r:
Yeah i had this app on my wildfire but when i got this phine and i saw that there is a tasj killer onboard i thought that its not gonna help me.but i remember that with this app you have by far morr options of killing apps.

Btw whats the name of your clock widget? Beautiful widgets or something else? :thumbup:

Thanks for recommending the app btw! :thumbup:
[Galaxy S I9000 Q&A, Help & Troubleshooting] AllexSCV1:
the name of widget is "GO Weather EX"

your current ROM probably has Task Manager by default, but there are many ROMs without it by default, so ... then...you'll need it

anyway, for me, even if I have Task Manager by default it's more easier to just click on a small widget on the homescreen than open Task Manager...clear RAM...bla bla bla
[Galaxy S I9000 Q&A, Help & Troubleshooting] Grigoris0r20r:
hehe.you are right.its better to press one key than to press more.Go Weather Ex needs the GO Ex launcher or is a standalone?
[Galaxy S I9000 Q&A, Help & Troubleshooting] AllexSCV1:
standalone ... I have Holo Launched HD ...
[Galaxy S I9000 Q&A, Help & Troubleshooting] Grigoris0r20r:
Nice thank you!
[Galaxy S I9000 Q&A, Help & Troubleshooting] BlueFlame4:
Task killers? In what century do you live? They drain the battery more than helping anything which has been proven a zillion times. Linux is not Windows.

So at thread starter: Don't use task killers. The CPU will have to push the tasks into RAM again and thus won't go into deep sleep.

Everything else was already mentioned: Juice Defender, Underclocking to 800 MHz and using a decent governor.

Sent from my Gameboy Color
[Galaxy S I9000 Q&A, Help & Troubleshooting] erpurohit:
There are few things in my signature as well...

you might want to have a look.
[Galaxy S I9000 Q&A, Help & Troubleshooting] Grigoris0r20r:
I just saw your signature and yiur topic about saving battery etc is great!thank you!
[Galaxy S I9000 Q&A, Help & Troubleshooting] erpurohit:
great..keep checking it I will be updating it soon in this week.
[Galaxy S I9000 Q&A, Help & Troubleshooting] Grigoris0r20r:
Ok!:thumbup::thumbup::thumbup::thumbup: