yashsingh1/xdaforums huggingface dataset:
[Xperia Play Android Development] lightningdude:
The only difference between fxp125 kernel and Mjolnir is the governors and schedulers. If you're experiencing lag, you may be low on ram. Try V6 Supercharger and see if that helps. Forcing GPU rendering may help, too. You may also try clearing caches with something like cache cleaner ng.
[Xperia Play Android Development] idiotzach15:
Could the reason why so many people are experiencing lag is because they didn't do I clean wipe? Or cache wipe? Maybe it's just been a while since anyone's moved to a new rom.
[Xperia Play Android Development] Leraeniesh:
I never wipe, and I am not experiencing any lag. 125 is MUCH faster than 124.

Sent from R800x
[Xperia Play Android Development] RublJow:
Hi

is the Recom. Baseband in FXP's Signature only for R800x?

What i need to flash for the R800i?

I have Running AOKPlay with Baseband -56 ;) and all works Good

Thanks for Reply

Greets
[Xperia Play Android Development] 3dawg:
There recommended baseband for r800i is baseband 64 or higher. Although, I used 56 for a while with no issues.
[Xperia Play Android Development] Barguast:
Super-n00b question - where do I download the oft-mentioned FXP kernel for this?
[Xperia Play Android Development] Maverick_G:
It's inside the zip file, with name boot.img
[Xperia Play Android Development] Wario21:
Just updated from FXP122 to FXP125 (I was away for a few weeks).

But now WiFi doesn't work. Did I miss something?

..Maybe I did something wrong at the update procedure?:

-Flashed the new Mjolnir Kernel to try it out (the Mjolnir bootscreen is ugly!)

-Installed FXP125

-Wiped cache, dalvik cache as usual

-Installed following .zips: CM9 wifi fix, CM9 gamepad fix, FaceLock, GApps, wifi signal fix, PS Store update
[Xperia Play Android Development] 3dawg:
As far as I know, a wifi fix is not necessary for cm9 anymore, neither is the signal fix...assuming you are on r800i?

Also, where did you get a gamepad fix from, and does it fix the circle button acting as back?
[Xperia Play Android Development] Wario21:
They all are from earlier posts in this thread I think. You're right, they could be outdated.. I'll try it again without the zips.
[Xperia Play Android Development] simpson1991:
can u fix the link to FXP 7.2 and uplaodet? i just see the 124 version.

And fiberuplaod doesnt work.
[Xperia Play Android Development] crono141:
The lag is funny. The rom is super smooth most of the time, but every now and again switching between applications just chugs. Had to do a battery pull once because the whole phone froze up while trying to switch apps once. But this has only happened once, and may have been an abberation.

I'm running FXP125, 4/29 Gapps, Mjolnir kernel. Also using Link2SD with a class 10 card.
[Xperia Play Android Development] Wario21:
WiFi won't even turn on, tried both KeiCS and Mjolnir Kernel. Does anybody know what's wrong?
[Xperia Play Android Development] lightningdude:
KeiCS isn't meant to work with any version of FXP after 123. Mjolnir Kernel was updated, but it broke wifi. I'll be re-uploading soon with the fix. Thanks for the report.
[Xperia Play Android Development] AudioCreaper:
Have you tried stock rom? Cause if wifi doesnt work on stock the problem maybe your phone.
[Xperia Play Android Development] BuckM:
I'm also having problems with wifi. I was on 125 cm9 and wifi worked fine, flashed your kernel, no luck. Cleared the cache and dalvik, reflashed, still nothing. Flashed back to cm9 kernel and it worked fine. Too bad, kernel was great otherwise, now I miss having the scary gov'n lol.
[Xperia Play Android Development] lightningdude:
The problem was the kernel. KeiCS wifi doesn't work, and I accidentally broke wifi on Mjolnir.

Mine's fixed now, so you can go re-download Mjolnir, if you'd like. Sorry you guys don't like the bootscreen, but I do. If the bootscreen bothers you so much, stick with the FXP kernel that comes packaged inside the rom zip. The only thing you'll miss out on with not using Mjolnir is more governors, schedulers, and zram until FXP's next update.
[Xperia Play Android Development] Wario21:
Thank you for your reply and fix also! The bootscreen doesn't bother me much, I just think in comparison to the Sony or FXP bootscreens its a little too messy and has lower resolution. Anyways, it's a great kernel.
[Xperia Play Android Development] lightningdude:
The lower res on the bootscreen is because the image can't have too many colors. I had made a different one before, but it didn't work. The current one is from an official Marvel wallpaper. I should actually probably credit Marvel in my thread.

Edit: Could we take further discussion of Mjolnir Kernel to its thread, please? I don't want to clog this thread up with non-fxp stuff.
[Xperia Play Android Development] Mysticales:
Ok just trying to catch up here (And update my guide)

1: Do I still need to flash that cdma mega fix on fxp 125 or do I leave that out now?

2: zRam (Compcache) some people saying its improving games? Confirm?

3: V6 Super Charger, is it built in already or do I need to do the stuff from the v6 thread?

(Also anyone who is using these, does it fix that stutter GTA 3 and so had since CM9 (vs CM7)

Also finally, does this CM9 have cifs.ko support? I tried my app, but no joy atm, so was wondering if anyone knew anything about that or if there is a cm9 ready cifs.ko that I could just insmod load? Thanks.
[Xperia Play Android Development] lightningdude:
You don't need to do the CDMA mega fix. The only fixes from that pack that are still usable are the carrier fix (in case you made custom carrier text like me :D) and the gamepad fix. Other than that, the other fixes are unnecessary, afaik.

Supercharger is not built in.
[Xperia Play Android Development] simpson1991:
wifi works for me with both versions(9 and 7), and the kernel which is included inside of the zip.
[Xperia Play Android Development] Mysticales:
Thanks. =) Ok the gamepad fix. Explain please. =) Gonna update my guide now without the cdma patch thing heh.

Also I gotta learn this supercharger thing. Heh.
[Xperia Play Android Development] lightningdude:
For those who have problems with the O button acting as back in games where it should serve as an actual game button, there's a flashable zip that makes a slight change to one of the keylayout files in system/usr/keylayout. I used to have the zip, but since it was included in the mega zip, I got rid of it. You should be able to find it in this thread somewhere.
[Xperia Play Android Development] Mysticales:
Ahhh Lightningdude Yea NOW I know what you mean! HOWEVER we had a good discussion about just that!

http://xdaforums.com/showthread.php?t=1128216&page=274 right around this area.

Then this thread http://xdaforums.com/showthread.php?t=1561203

Basically, no, Key 304 is SUPPOSED to be "BACK_ALT" the issue is, some apps/games arent recognizing the alt+back. Which the devs of that app need to work on. The other study we found. Those of us who changed it to be "BUTTON_B" well... we messed up the OTHER apps which relied on that keypress mapping. So while the "fix" is more a personal preference to prevent O from acting like "back" (Only on apps that dont reconize alt+back keystoke) This fix isnt ideal as it would cause more issues with other apps that have it mapped as it was designed to be.
[Xperia Play Android Development] KeiranFTW:
If you want, I can ask for it to be changed to BUTTON_B in CM9?

Keiran
[Xperia Play Android Development] Mysticales:
I wouldnt. Again, alot of the specs the app devs go by is what the official thing is. I cant rem, I think Google has it to BUTTON_B, however by the time sony got done with it and officially gave it out they have it as BACK_ALT which is mappable if the person making their dev looks for this. So if you have CM9 change to default being BUTTON_B, then yea, alot of apps O button wont work on them unless the dev updates AGAIN for this.

Now what would be IDEAL. An option in the rom to choose "Gamepad mapping" so it could be BACK_ALT or BUTTON_B

Edit: For CM, I know they have the rom options built in, so wondering if that could even be done? Cause you see, if they did allow a choice, its not just BUTTON_B for O. Youd want the BUTTON_A for X as well. Since if you dont have O as back, No need for X to be the "Confirm" button or the one that opens apps either. (Which this would really turn the gamepad buttons into fully separate function that isnt for android. Cause atm X is DPAD_Center which is what alot of android os and apps treat that as.
[Xperia Play Android Development] 3dawg:
I'd also like to point out that after applying the cm9 gamepad fix, circle became funtional as circle in fpse. However, as soon as I applied the opengl plugin, it reverted to acting as the back button, as if I had not flashed the fix.

Once I removed the plugin, it functioned again. It's very confusing :/
[Xperia Play Android Development] Mysticales:
Gotta check FPSE settings, some emulators have gamepad mapping for the controller itself to use in game, then some have system mapping stuff. Where you have to disable the back button mapping. It is indeed confusing, but with some roms using it as "x" and others as "y" yea, each dev who makes an app, might code for one way or another. It is annoying.

Now if you find the mapping that makes GTA 3 buttons work.. dont be shy. However was suggested that the stock rom somehow.. had it as binary mappings, which is how GTA 3 read it. Which is odd.
[Xperia Play Android Development] Dudeness83:
I wonder if someone could write a script to toggle between the two settings. Have a widget on the home screen that you could press to swap em?

May not be able to work seeing as it looks like you have to flash something to swap it.
[Xperia Play Android Development] Mogul345:
I think this document, Input Device Configuration Files, is what we need. With root privileges we should be able to write something that can fire off a script to update the file with the desired mapping.

<speculation>I think the tougher part might be getting the updated configuration recognized without a reboot. I'm willing to bet that these files only usually get read on boot. May have to "unplug and replug" the gamepad somehow via software in order to pick up the new configuration</speculation>
[Xperia Play Android Development] Mysticales:
No, no one is flashing anything. Heh. Awhile back I wrote an easy how to have it remapped thing. http://xdaforums.com/showpost.php?p=24114936&postcount=9

You do have to however reboot your phone for it to work.

Now again, Ill mention this. If you DO use this BUTTON_B method, while O wont act as "back" alot of apps/games that look for O to be "BACK_ALT" (Which honestly is almost all of the ones I have used) you will mess these up unless that game/app supports true customizing button mapping so you can change it. (Like Emulators)
[Xperia Play Android Development] zetsurin:
FXP125 seem quite smooth on my XP. I moved over from the Sony ICS beta.

However, my phone locked up this morning and is now stuck in a boot loop for some reason. I don't seem to be able to access recovery. Is it supposed to be volume up or back key when I switch on?

When I installed I wiped data so it can't be that. I'm going to boot a recovery via fastboot and clear my caches as I can't otherwise see what else could be wrong.
[Xperia Play Android Development] lightningdude:
Fxp kernel is volume down, Mjolnir is back button.
[Xperia Play Android Development] crono141:
It would be nice if we could get a message like "hit back for recovery" on the kernel boot splash screens. It would solve the "how do I get into recovery" confusion.
[Xperia Play Android Development] idiotzach15:
Well it'll pretty much always be one of the two... so if it doesn't work with one, just try the other.
[Xperia Play Android Development] Mysticales:
Hey are we from the power button able to "Reboot" "Recovery" now or is that still bugged and have to use terminal su for that?
[Xperia Play Android Development] lightningdude:
If you hit the home button after the sd card unmounts, it will reboot into recovery. At least, it does on Mjolnir Kernel, not sure about FXP kernel.
[Xperia Play Android Development] notrodash:
As soon as I connect my phone to my computer and fire up LogCat, LogCat is SPAMMED with these messages:

06-19 16:45:52.529: D/DASH - select(206): device/semc/msm7x30-common/libsensors/sensors_select.c(67): sensors_select_callback: unlock
06-19 16:45:52.529: D/DASH - select(206): device/semc/msm7x30-common/libsensors/sensors_select.c(68): sensors_select_callback: unlock
06-19 16:45:52.529: D/DASH - select(206): device/semc/msm7x30-common/libsensors/sensors_select.c(49): sensors_select_callback: lock
06-19 16:45:52.529: D/DASH - select(206): device/semc/msm7x30-common/libsensors/sensors_select.c(54): sensors_select_callback: unlock
06-19 16:45:52.599: D/DASH - select(206): device/semc/msm7x30-common/libsensors/sensors_select.c(63): sensors_select_callback: lock
06-19 16:45:52.599: D/DASH - select(206): device/semc/msm7x30-common/libsensors/sensors_select.c(64): sensors_select_callback: lock
06-19 16:45:52.599: D/DASH - select(206): device/semc/msm7x30-common/libsensors/sensors_select.c(67): sensors_select_callback: unlock
06-19 16:45:52.599: D/DASH - select(206): device/semc/msm7x30-common/libsensors/sensors_select.c(68): sensors_select_callback: unlock
06-19 16:45:52.599: D/DASH - select(206): device/semc/msm7x30-common/libsensors/sensors_select.c(49): sensors_select_callback: lock

They are blue if that is of any importance.
[Xperia Play Android Development] Mysticales:
UGH. Ok someone please tell me there is a way to increase the volume gain tables? I mean this thing is so low now in volume.. Barely can hear anything when im out and about.

Also I see.. the same issue remains.. I updated from 124 to 125.. and once again I need to flash gapps and resign into google.. Why is that? Seems every update i have to do that.
[Xperia Play Android Development] lightningdude:
You have to reflash gapps every time you flash this rom. The Google framework stuff is stored in system. And since system gets wiped, and CyanogenMod technically isn't allowed to distribute gapps in their rom, you have to reinstall them.

The volume hasn't been a problem for me lately, which I suppose just goes to show that I've gotten used to them. You can use an app called Volume+ in the app store to boost the volumes. The ICS version is a paid app, but it's worth the money.

@notrodash I found where warnings are coming from, but not why you're getting them. It's all over my head at this point. paxChristos, any ideas, if you can hear me?
[Xperia Play Android Development] Mysticales:
Cool. Thanks for that info. Also Agraceful had done something with the CM7 builds.. that when you flashed updates, you didnt need to reflash gapps, kinda wonder what he did heh.

Also old days on my G1, I used to use LucidRems script which could increase the volume gain, are the newer androids no longer able to do that?
[Xperia Play Android Development] lightningdude:
I have no idea about the volume gain other than my own experience, which I've already stated. If you flash gapps immediately after flashing CM9, without a boot in between, you won't have to re-login.
[Xperia Play Android Development] Mysticales:
Yea the old stuff, http://xdaforums.com/showthread.php?t=480582 he even had the easier way for apps 2 sd linking and so. Few other things. But yea the volume one was <3

Ok that Volume+ with setting 8 seems to make the emulators sound abit better. Its still low, so I may try 10 for speaker setting. Least its better then before.
[Xperia Play Android Development] zetsurin:
Something quite strange happened to my XP running FXP125 a day ago. In the morning the launcher suddenly became unresponsive, so I powered it down. It took AGES to shut down, but eventually did. Then it boot looped after that. I couldn't access recovery at all. I was trying volume up & back, so that part makes sense. But after discovering it's volume down, I tried that and still couldn't access recovery.

I could however get my phone into fastboot mode, so I booted into CwM recovery via fastboot and cleared data & dalvik, ie. back to factory which I assumed was as it was when I first installed in the first place. However it continued to boot loop on me. Then I reflashed the ROM as well as gapps. More boot loops. The only thing I didn't do was reflash the kernel via the boot.img, so maybe something somehow had gone amiss with my kernel.

I restored the nandroid I took of the Sony beta ICS + the corresponding boot.img, and the phone is running as normal now. Sadly, it doesn't feel as smooth as FXP125 was.
[Xperia Play Android Development] fareeed:
Try a fresh flash of everything including firmware using flashtool? Then just flash the kernel via fastboot and install as normal? :)
[Xperia Play Android Development] Leraeniesh:
Is there a chance the R800x will have official Cyanogenmod support once CM9 hits release candidate? I don't think we deserve to be left out like in CM7.
[Xperia Play Android Development] KeiranFTW:
If its available for zeus then chances are it will be available for zeusc
[Xperia Play Android Development] Mysticales:
Anyone know if this has cifs.ko support for mapping network shares? Or if its even possible yet?
[Xperia Play Android Development] Mogul345:
Went from a Pax build to FXP125, and didn't install the entire 2.3.4 ftf, excluded everything but the baseband. Did do a full wipe.

Everything is working pretty good, although sometimes it does lag hard. Battery life is pretty good, I can see in CPUSpy that most of the time it's in deep sleep or 134mHz. It kinda seems like setting up/tearing down a wifi connection is one of the causes.

Still got a broken 3g connection once (full bars and 3g indicator, but grey instead of blue) which required an airplane mode toggle to get back running again. Way better than previous builds, though. Is there more of the ftf I should have flashed?

Also noticed that my logcat is spammed with the same messages as described in this post. Looks like a debug log flag didn't get unset.

Overall, nice work!
[Xperia Play Android Development] KeiranFTW:
Hey,

Thanks for the mini review ;)

DASH is Dynamic Android Sensor HAL (Hardware Abstraction Layer)

Basically, it is what interacts with the sensors.

Recently, we disabled logging on it :)

Interactive governor is good, yes :)

zRam and swap support will be in FXP126 kernel :)

We would be building with linaro tool chain but our kernel doesn't boot with it.
[Xperia Play Android Development] vemoxy:
Amazing work devs.

Can I just confirm that sensors are still not working in this update? I won't flash it, if it's not..
[Xperia Play Android Development] Mogul345:
Excellent! I used zRam on the Pax builds with your old kernel.

Oh hey one other thing I forgot to mention. I seem to have 2 Gmail widgets - one labelled "Gmail" and the other labelled "Google Mail". Any way to get rid of one? Know why that might happen?
[Xperia Play Android Development] jerpelea:
FXP126 released
[Xperia Play Android Development] gfraizer:
Wifi Tether Solution

Not sure if anyone else still having trouble with tethering on this otherwise excellent ROM, but after trying many,Many workarounds, net-searches etc. I've found an old friend BARNACLE WIFI TETHER, a free app in Play Store seamlessly connects my XPlay with Asus Transformer, iPad, etc. i'm now happily surfing and downloading in remote locations.
[Xperia Play Android Development] benben972:
First !!

Let's go baby :p
[Xperia Play Android Development] arian009:
Oh so quick! Didn't know FXP126 is released, gonna try it out! :P
[Xperia Play Android Development] nscxp2005:
Hi,

Could somebody tell me what offline charger is?

Thanks
[Xperia Play Android Development] Maverick_G:
Charging while the phone is off..
[Xperia Play Android Development] 3dawg:
I don't quite understand the warning/instructions next to the wifi init thing.

"(if you dont flash kernel and wipe wifi will not work properly)"

What does this mean?
[Xperia Play Android Development] lightningdude:
It most likely means do a full wipe on this one.
[Xperia Play Android Development] 3dawg:
Damn it, I was hoping I was wrong :(
[Xperia Play Android Development] Mogul345:
Titanium Backup is your friend in this situation...
[Xperia Play Android Development] DoubleByte:
Unfortunately, it does.
[Xperia Play Android Development] Mysticales:
So wait.. everyone with r800x or so has to do a full wipe for this build...?

Even with Titanium backup.. thats horrid. >.< Cause even when I try to restore, it doesnt seem to restore correctly where its supposed to. (Alot of apps try to stay installed to internal memory)

So someone fill me in, is a full wipe what we have to do here?
[Xperia Play Android Development] jonytestXD:
a question how do i use zram only tick the mark on the performance menu that says zram and which porcent should i choose?
[Xperia Play Android Development] Mysticales:
Im still wondering if zram is ideal for xperia.. I mean more ram free sure, but at the cost of more cpu cycles which could slow things down too. Would love to know from ppl are are hardcore gamers, emulators and true android graphic demand games, what settings for performance they are using.
[Xperia Play Android Development] Mysticales:
WHOA WHOA! GTA 3.. alla sudden my gamepad buttons are working on it?! Tho the game crashed out as soon as I hit triangle.
[Xperia Play Android Development] 1c3_5n0w:
If I remember correctly, GTA 3 10th Anniversary was working perfectly on FXP123 (On gamepad) But it kept lagging especially when driving without o/c
[Xperia Play Android Development] xRegrets:
zram is meant for multi tasking, not gaming.
[Xperia Play Android Development] Mysticales:
Thanks. Heh. =)

As for GTA, No the D-Pad worked, Gamepad didnt. Also in CM7 it ran smooth, CM9 its laggy, not even sure best OC settings for it tbh, but now its just constantly crashing right after a new game, not even a force close, it just silent crashes out. Anyone know what this new FXP126 did that causes it?
[Xperia Play Android Development] Leraeniesh:
How does Modern Combat 2 fair with the touchpads on this ROM?

Sent from R800x
[Xperia Play Android Development] notrodash:
Why am i unable to download the Xperia Play Games launcher from Google Play?
[Xperia Play Android Development] BuckM:
So far the ROMs running pretty great for me. Coming from CM7 there's a few features I miss, namely the ability to control cpu voltage and the selection of governors and schedulers. I realize the ROM is still in its early stages but I always found these options to greatly influence battery life. And before any one points to Mjolnir, it also lacks voltage control, also I would rather flash the official kernel especially at this point in dev - if there are any issues to report I want to make sure its a CM9 problem not anything else. Just wondering what your thoughts are on adding these features, thanks for the great work!
[Xperia Play Android Development] notrodash:
Overclocking works with this rom
[Xperia Play Android Development] BuckM:
It sure does, but that's not what I'm talking about. I'm talking about voltage control, ie being able to control the voltage the cpu gets at each clock speed.
[Xperia Play Android Development] stevecrox:
At FXP 123 I switched back to CM7.2 and accepted CM9 wasn't "ready". For various reasons I thought I would give FXP 126 CM9.0 s try.

Fixes:

Radiant HD Ship overlay bug fixed

Sonic 4 is no longer laggy

More responsive

Home screen slow redraw seems to be resolved.

Apollo Music Player (pretty Cool)

Battery life is improved, under gingerbread I get around 12 - 15 hours. Yesterday I got 11 hours battery.

It shuts itself off when it runs out of battery

Quite impressed overall
[Xperia Play Android Development] arian009:
Does anyone know which App i can use for WiFi tethering, the stock tethering feature still doesn't work. I can tell the difference however, it doesn't make the phone freeze or disable WiFi completely :P
[Xperia Play Android Development] lightningdude:
I think someone earlier mentioned Barnacle Wifi Tether.