yashsingh1/xdaforums huggingface dataset:
[Xperia Play Android Development] KeiranFTW:
@FreeXperia, I have looked around the forum over many devices and have noticed that most phones have problems with WiFi in ICS, sometimes dropouts and inability to connect, this seems a common issue in ICS.

The problem happened when some SIM cards were used the WiFi would behave strangely, changing the country code of the WiFi in the Sensation XE roms fixed the issue, I think they made an app for it :)

Keiran
[Xperia Play Android Development] Nhialor:
I'm having very bad wifi problems on my HP touchpad. Its early alpha though so it is to be expected.
[Xperia Play Android Development] Bin4ry:
Thanks,

but until we have not fixed RIL completely its not need to investigate into that problem. Maybe it solves itself with the fixed RIL ;)

Regards
[Xperia Play Android Development] KeiranFTW:
Maybe it does :)

edit: I think the current issue with RIL is either baseband or kernel related, because it is happening across all ROM's, even with prebuilt semc RIL libraries, using the .32 kernel and -64 baseband.
[Xperia Play Android Development] Roshi69:
Installed nova launcher instead it's soo much smoother
[Xperia Play Android Development] KeiranFTW:
As FreeXperia has said, it is an alpha and is unnoficial until stable release. Some things do not work potentially because we are using an outdated kernel, data is related to RIL and FreeXperia is working on a fix for this.

Sent from my R800i
[Xperia Play Android Development] igor_anta:
It really doesn't hurt do do a bit of research. That is the date of the stable release, all the FXP updates are nightly builds. And, again, if you just went through all the trouble of clicking a link or two you'd see that all the nightly CM builds are uploaded a day after the FXP builds here.

So yeah, it's the same rom. 100% sure.

---------- Post added at 07:13 PM ---------- Previous post was at 07:02 PM ----------

Install Pimp My Rom from the market:

https://play.google.com/store/apps/...wxLDEsImNvbS5hbmRyb2d1aWRlLnBpbXAubXkucm9tIl0.

There is an option to flash the new Walkman with all the audio effects. But take in consideration that there is no widget. Sony's music widget works with the Xperia Home and you can't use it with any other launcher.
[Xperia Play Android Development] Slothboy:
Where is that option? All I see is Beats Audio and xLoud? o_O
[Xperia Play Android Development] igor_anta:
Hmm, if it isn't there anymore then they removed it. Just google "Xperia Walkman V for CM9 xda" and you should get something helpful.

Remember people, Google knows everything :)
[Xperia Play Android Development] Dany XP:
So to sum up: the nightlies on cm official forum and the fxp on this thread are the same. Ok, I got it and your right, it was easy to see (never gone on "Nightly Builds" page, sorry.

But i think the question was what's the difference between the nightlies and the stable. Since it's obvious that nightlies have some sort of improvments (they are more recent), what are these improvments exactly. WHat's missing in stable?
[Xperia Play Android Development] cj360:
Check the changlelog that's on the left side on fxps download page.
[Xperia Play Android Development] simonrussell77:
@Dany XP

This is good for change logs; http://mobile.cm9log.appspot.com/?device=zeus

It sums up the change log in a detailed way - I use this for comparing differences between official cm 9.1 and latest official *nightly* from get.cm

If you're looking at differences between official cm and fxp, then like poster above me said - look at fxps Google sites page in fxps signature.

Hope that helps. That's all I know anyways. The above link helps my semi noob brain figure it all out in layman's terms lol.

I never really use the fxp releases, as I prefer the stable and or occasional nightly via get.cm itself. But thats my own personal preference ;)

Essentially all changes fxp and cm wise, get merged into the git repository for our device, so both versions are pretty much identical.

So with that assumption, the link above plus fxps Google sites page sums up the differences pretty well. It's just a case of reading through it all when you're in the mood for a spot of light reading hehe.

Apologies for the long reply. I'm not the best person for straight to the point answers lmao.
[Xperia Play Android Development] andiemerchcomia:
Just installed this rom and fell in love with it. very stock android which i want. cm9.1 update poped up. should i update to that? very noob on cm version.
[Xperia Play Android Development] jerpelea:
FXP149 released
[Xperia Play Android Development] Lefteris Fragiadakis (Frago):
Still not for play the update only for

Arcs
[Xperia Play Android Development] Slothboy:
They fixed the Proximity Sensor.
[Xperia Play Android Development] Lefteris Fragiadakis (Frago):
Yes I go to download it and ther is on file called anzu,should I download this for play?
[Xperia Play Android Development] rashid.fairus:
zeus for gsm..zeusc for cdma..
[Xperia Play Android Development] Slothboy:
He's right, there's no zeus or zeusc on the download page :eek:
[Xperia Play Android Development] rashid.fairus:
uploading in progress..
[Xperia Play Android Development] Dany XP:
OK I HAVE A PROBLEM:

A little history first: i came from LOCKED bootloader with NXT Rom 1.3 (based on stock rom)

Unlock Bootloader days ago and immedietly flash FX148 (kernel inside zip + rom): paradise, everything (except proximity sensor of course) worked, browser WAS OK.

2 days ago i wann try markphyton so flash lupus kernel and nxt rom from markphyton. Seeing some fc in stock browser when i open more then 2 or 3 tabs...unacceptable. Yesterday re-flash FX148 and...browser stock forces closes too! How's that possibile?!?! Coincidence???

Did i something wrong???

P.S Of course i did all Factroy reset, wipe cache and wipe dalvik cache everytime

EDIT: Just tried the Xperia Mini Pro's mom with locked bootloader, stock sony ics...force closes too?!?!? OK, baybe it's the site? Guys can u do me a favor? can u go to http://www.badtaste.it/ and open at least 3 or 4 news with tabs and tell me browser closes itself please?

EDIT 2: Just tried FXP149...proximity sensor still doesn't work!
[Xperia Play Android Development] andiemerchcomia:
which is the best way to update:

1. download the rom in the computer and flash it via cwn recovery or

2. download the update via OTA on the phone itself?

thanks...
[Xperia Play Android Development] Slothboy:
@Dany XP

It force closes for me too, might just be the site dude.
[Xperia Play Android Development] simonrussell77:
Out of interest, I tried today's fxp release, as well as the official nightly from get.cm, dated 2nd Dec, and both versions the proximity sensor is *not* working still. It still dials numbers with your face if it happens to touch the screen while you're in a call lol.

They may have updated sensors - like Sony DASH, etc, but the proximity sensor on the Xperia play is still borked. And yes - I did a clean install when doing my little tests. I flashed their respective kernel, blah, blah too ;)

Its kinda frustrating, as my other Xperia the smultron / mini, doesn't have this problem anymore - its sensors are fixed. So clearly something is very unique to our play, as far as the proximity sensor goes, despite the hardware being similar over the 2011 xperia range (minor hardware differences obvs)

So can anyone else confirm that its still bust in the latest fxp / official cm nightly?

Thanks.

P.S. its only a minor annoyance, and no biggy. Its just frustrating for our devices track record lolz. I'm very grateful to fxp for all their hard work. At the end of the day, we're getting their work for free, giving only donations via PayPal - which they deserve, as they've made our play more awesome than Sony ever could lol.
[Xperia Play Android Development] rashid.fairus:
the 2nd option are impossible..so the 1st way win
[Xperia Play Android Development] andiemerchcomia:
Did the first one instead. I am still finding the best keyboard for the phone as ics keyboard is only qwerty layout. Still in love with the alphanum keypad in usual touchscreens.
[Xperia Play Android Development] ten_tickles:
The screen is very dull on this rom, even on maximum brightness.....is there a fix? :confused:
[Xperia Play Android Development] Leraeniesh:
Flash the auto brightness disabler in the PACman thread.

Sent from R800x
[Xperia Play Android Development] Lefteris Fragiadakis (Frago):
guys i have a bib problem,i installed the new 149 version when is my xperia play open and try to conect it to pc all ok in mass storage when i reboot and go in the recovery and chose mount usb in the pc shows new device conected r800i but windows cant find driver,,,why?

update

it happen only with this recover-kernel,with doomlord all ok

why???
[Xperia Play Android Development] Lawliet918:
does the DL file have a mirror site? i'm always getting maxed out at uploaded.net. :crying:
[Xperia Play Android Development] nickholtus:
use unrestrict.li
[Xperia Play Android Development] Lawliet918:
awesome! thanks, nick! i used to DL at uploaded.net without any prob but now, it seems its downloaders have been thriving. tried to use the cooking thing at coder143.com but didn't work either so, yeah, you're my savior! haha! thanks, man! :victory:
[Xperia Play Android Development] Dany XP:
I don't know if it's a bad or good news? So no way to improve browser?

Anyone else confirm this "bug"?
[Xperia Play Android Development] andiemerchcomia:
Day two with this rom and im very happy with it. I love the smooth and silky vanilla stock interface with cm tweaks and feautures. Loving this much. Dont care too much about the games. Btw, i believe this is nightly rom, however what are the pros and cons of the stable vs the nightly roms? So far the fxp nightly rom is perfectly stable!
[Xperia Play Android Development] Lefteris Fragiadakis (Frago):
Tried a lot rom this one the best ever
[Xperia Play Android Development] xElvizlex:
is there anyway to improve the performance of this rom? my phone seem to be running slow. it takes a few seconds for any command to go through. any advice is very appreciated thanks in advance.
[Xperia Play Android Development] Slothboy:
idk about you guys, but I get a lot of random FC's on random apps with this, so I'm going back to Gingerbread for a while. :3
[Xperia Play Android Development] MonY960:
Does the in call proximity sensor working in FXP149 ??

because it doesn't work here !!!!
[Xperia Play Android Development] Dany XP:
Same here
[Xperia Play Android Development] xElvizlex:
same over here.

---------- Post added at 06:08 PM ---------- Previous post was at 06:07 PM ----------

did you try to fix permissions in recovery? that helps out when i get some FC's
[Xperia Play Android Development] SE_iCEQB:
The proximity sensor never worked for me since I'm using CM 9.1.

I opened the issue on google code twice by now and everytime hesays he fixed it, it actually never is.
[Xperia Play Android Development] devguy22:
Proximity sensor doesn't work for me either. I updated with CWM, and reflashed the kernel included in the package. No dice.
[Xperia Play Android Development] Dany XP:
If proximty sensor and x-Loud (the volume is slighlty low compared to stock rom with xLoud activated), then we would have the perfect ICS rom for Xperia Play.

Although i see stock browser FC often!
[Xperia Play Android Development] CosmicDan:
Actually, the Proxy Sensor does work (or at least, it did). Did you actually try making a call, and then pressing buttons while covering the top of the screen? It's true the screen won't turn off, but it will disable touch input. At least it did for me a few versions back.
[Xperia Play Android Development] Dany XP:
If i said so, it's because i try it...i'm not that dumb...

Did you try it?
[Xperia Play Android Development] CosmicDan:
I said it *did* work once, I have not used it for a while. Rude much? Last time I try to help anyone.... *unsubscribes*
[Xperia Play Android Development] Dany XP:
If u say "The application xxx doesn't work" and somebody answer to u "Have u try it?", don't u find that a little insulting?

For me, THAT'S rude, man.
[Xperia Play Android Development] Trakinão:
I Agree! +1
[Xperia Play Android Development] andiemerchcomia:
Good day. Would like to ask if using the stock or includd kernel in the zip is way better than using custom kernels by doomlord and lupus? I know that both kernels are heavy performers because of tweaks but im more concerned with other issues and bugs with the three kernels.... Please enlighten me.
[Xperia Play Android Development] Dany XP:
about the xLoud issue...has somebody used this? http://www.modaco.com/topic/358472-modicsjb-acd-audio-engine-update-1129-testers-needed/

But u know, that's not even very important, the volume is not incredibly high like in stock rom, but i'd say it's acceptable, like in the other phones.

The real very "bug" for me is the proximity sensor. I'm searching all over internet but i can't find any actual solutions: some of them are for CM7.2, some of them are for very old FX, some of them are for other Xperias...somebody else got more luck?
[Xperia Play Android Development] Dany XP:
Please guys, report your issue too, maybe we can help FreeXperia / Cyanogenmod http://code.google.com/p/cyanogenmod/issues/detail?id=6806&thanks=6806&ts=1354791240
[Xperia Play Android Development] MonY960:
Nooo you are using unofficial cyanogenmod from freexperia team you have to report in http://code.google.com/p/freexperia/issues/list

:)
[Xperia Play Android Development] Dany XP:
Are u sure? FreeXperia is part of Cyanogenmod official....
[Xperia Play Android Development] Slothboy:
FreeXperia are the maintainers of the Xperia side of CM.
[Xperia Play Android Development] Dany XP:
Yes, they reply me. So i guess i have to track the issue on FreeXperia code google
[Xperia Play Android Development] CosmicDan:
Regarding Proximity Sensor, nobody seems to be paying attention to Jellyzeus so I'll share my research here.

Firstly, DASH configuration flags in board makefile are incorrect - it specifies that the proxy sensor is APDS9700 but it's actually a APDS9702. I changed that, didn't help anything. Secondly, I found that the APDS9702 config flag in my kernel was not set so I set it and rebuilt it, still no effect.

My guess is that AOSP needs more changes that are not documented on the wiki to work with Sony DASH.

My BoardConfigCommon.mk:

# DASH (Jellyzeus)
SOMC_CFG_SENSORS_COMPASS_AK8975 := yes
SOMC_CFG_SENSORS_ACCEL_BMA150_INPUT := yes
SOMC_CFG_SENSORS_PROXIMITY_APDS9702 := yes

I know this is the CM9 thread and I'm ON JB, but yeah. I also don't know why ALS/autobrightness doesn't work on other JB ROM's, because it works perfectly fine on Jellyzeus r2 (not out yet) and Turbo kernel.

If you see this J, have any ideas?
[Xperia Play Android Development] jerpelea:
check dash mk and ajust name according to that

depending on dash version adps name has changed

br

J
[Xperia Play Android Development] CosmicDan:
Thanks. I did check this, and it is being built. All my flags are correct and matching the latest DASH source values which I am using. I can see these files:

./target/product/zeus/obj/SHARED_LIBRARIES/sensors.default_intermediates/sensors/apds970x.P
./target/product/zeus/obj/SHARED_LIBRARIES/sensors.default_intermediates/sensors/apds970x.o

However upon further research on whitepapers, it seems the Xperia Play actually uses the Sharp GP2 proximity sensor. I will reconfigure my kernel/ROM and see how I go.

EDIT: Confirmed. J, I just added these to my zeus-common board mk file:

SOMC_CFG_SENSORS_COMPASS_AK8975 := yes
SOMC_CFG_SENSORS_ACCEL_BMA150_INPUT := yes
SOMC_CFG_SENSORS_PROXIMITY_SHARP_GP2 := yes

And now all sensors work 100%.
[Xperia Play Android Development] Dany XP:
And with that, i guess this rom has no other bugs now....

It's just perfect right? Besides of course the lack of xLoud?...
[Xperia Play Android Development] jerpelea:
uploafing FXP150a with fixed kernel
[Xperia Play Android Development] Jay Ros:
Kinda have the same question. :confused:

The xLoud is now the only thing that doesn't work?
[Xperia Play Android Development] CosmicDan:
Source needs to be modded to use prebuilt ICS_AUDIO_BLOBS for xLoud. Not sure if FXP/Cyanogenmod want to make that change however, it may be legal grey area.
[Xperia Play Android Development] XDM inc:
* Comment Removed*
[Xperia Play Android Development] Dany XP:
Yes but besides xLoud? There's no other bugs right? This rom is basically perfect, correct?

By the way, even without xLoud i find the volume just fine...
[Xperia Play Android Development] XDM inc:
Sorry but XLoud, touchpads and wifi are the most important things for me on my phone. especially xloud. why do you think i tried so hard to get it working on my rom.
[Xperia Play Android Development] gopin:
anybody successfully flashed FXP150a? i have not been able...

phone boots but trigger to enter cwm does not happen (purple led) and the screen just goes black after the kernel logo, so i was not able to flash the rom. i am using kernel included in zip and fresh install from .62 fw
[Xperia Play Android Development] jimmyvau:
I'm having the same problem with the zeusc version.
[Xperia Play Android Development] Dany XP:
i don't have problems with touchpads and wifi....

and for xLoud, i heard that we can do something about with some app on play store, don't remember the name's app...
[Xperia Play Android Development] CosmicDan:
As I said, source needs to be modified for ICS_AUDIO_BLOBS to use prebuilt Sony proprietary libs. Jellyzeus already has it, soon SlimBean and PAC too. But I don't work on ICS anymore so it's up to J if he has interest or not.
[Xperia Play Android Development] Dany XP:
What problems do u have anyway with touchpads and wifi on cm9.1?
[Xperia Play Android Development] CosmicDan:
What? As I said, I don't work on ICS. I can't comment on CM9. I'm just saying what needs to be done for CM9 to support xLoud, needs sources changes.
[Xperia Play Android Development] Dany XP:
Ok i get u now.

So if u ever had used CM9.1 on this thread or in your JB roms (i guess Xloud is missing in those too), you think the lack of xLoud is so important? You think that without it, the volume is really so "low"?
[Xperia Play Android Development] CosmicDan:
I never really used CM9 TBH, for ICS I was always using MIUI Australia (which is stock based and had xLoud fine). And no, as I said Jellyzeus is a JB ROM and has 100% xLOUD - try it yourself and see - soon P.A.C. and SlimBean will too (when they get time to make my changes). The sourcecode needs to be modified to use stock ICS audio libs, then we get 100% stock-like sound experience. But I don't know if CM9/10 will ever use it because (1) They are proprietary files and it might have a legal issue, and (2) I think it breaks DSP Manager.

My opinion on whether xLOUD is essential or not is irrelevant, the goal of Jellyzeus is to get as close to 100% working as possible - unlike other JB projects, new features are not a priority. Because other JB source builders like FXP, Wedgess and cj360 can use my code to improve theirs (which they have all done already with e.g. proxy sensor). Also ALS works in Jellyzeus but I'm not sure it's compatible with other kernels and ROM's.

Regardless, I'm off topic. This is about CM9. If J wants more info on making patches to use stock ICS prebuilt audio libs then he can contact me, when or IF that happens there will be no xLoud support at all in CM9 (it cannot be hacked in without source changes).
[Xperia Play Android Development] gopin:
Hey Dan, this guy is wasting your time, he's confusing u with xdarkmario. lmao

Back on topic: has the new kernel worked for anybody? I have downloaded twice and have had no success getting it to boot into CWM
[Xperia Play Android Development] Dany XP:
Ops, you're right, i'm a mess.

Anyway everything is clear on xLoud now.

Probably in the future we will see it working on CM9.1 but for now i consider the volume normal, so for me the next FX151 will be finally a 100% working ICS Rom for Xperia Play.
[Xperia Play Android Development] Dany XP:
Mee to now...
[Xperia Play Android Development] Jay Ros:
You right, 151, because 150a definitely not booting :p
[Xperia Play Android Development] Dany XP:
I used kernel from fx149...it boots...
[Xperia Play Android Development] gopin:
Did you apply farenheith's fix? I did using FXP148 kernel and lost reboot and profile options in power menu, so I think that framework.jar changed in fxp150a. I used the fix for fxp148 and later btw.
[Xperia Play Android Development] Dany XP:
Of course i use farenheit's fix (i use it since fxp147). Event this time with fx149's kernel + fxp150a rom. Everything works fine, power menu has reboot and profile like usual...
[Xperia Play Android Development] gopin:
I must've done something wrong then
[Xperia Play Android Development] Slothboy:
A bit of advice to everyone using this rom

Go to Jellybean, it's so much smoother.
[Xperia Play Android Development] Dany XP:
I know that, but i see farenheit's fix has problems with JellyBean right?...

---------- Post added 12th December 2012 at 12:10 AM ---------- Previous post was 11th December 2012 at 11:56 PM ----------

I think i found a bug that seems nobody noticed.

Open Camera app > Video. Then choose any Effect: "Unfortunately, Camera has stopped"!!!!!
[Xperia Play Android Development] farenheith:
The fix works okay... the problem is the touchapd lag, that have nothing to do with the fix. Maybe you need to replace the framework and build.prop right in the ROM zip due to space problems in the system partition, that's all.

I noticed this too some months ago... it's an old bug and you'll don't find any ROM with silly effects working.

The most is the preview with the effects work, but the record FC
[Xperia Play Android Development] Dany XP:
I wouldnt know how to replace the framework. Although i always replace the build.prop "modified" with the correct informations inside the zip before even flash it
[Xperia Play Android Development] farenheith:
you just need to grab the framework.jar from the fix zip and put it in the /system/framework folder of the ROM. The instructions is in the touchpad fix thread.

Maybe you can't just replace it, then you have to decompress the ROM, replace the file and compress again.
[Xperia Play Android Development] Dany XP:
That's it? Ok i got it...maybe i will give it a try...
[Xperia Play Android Development] Dany XP:
"- wifi sleep bug (all 2011 except play)" in fxp151 changelog. What sleep bug!?!?!?!
[Xperia Play Android Development] wedgess:
We dont need this its not a problem for our PLAYs as we use bcm. For the devices which use Tiwlan, such as PRO, ARC ect when there phone is idle sometimes wifi locks up randomly and only way to turn wifi back on is a reboot.

So basically nothing to worry about for us :)

Sent from my GT-I9300 On Official JB
[Xperia Play Android Development] jerpelea:
FXP151 released
[Xperia Play Android Development] XDM inc:
Nothing wrong with wifi or touchpads just to be clear, I was only making a reference. What I was focusing on was xloud. :o
[Xperia Play Android Development] Dany XP:
Just downloaded FXP151:

STILL DOESN'T BOOT WITH BOOT.IMG INSIDE THE ZIP!

Had to use kernel from FXP149....and now proximity sensor works at least...
[Xperia Play Android Development] CosmicDan:
I'll make an update ZIP to add xLOUD to any ROM soon.
[Xperia Play Android Development] farenheith:
wow, nice! I thought this isn't possible
[Xperia Play Android Development] CosmicDan:
Yeah, it works on any ROM. Jellyzeus and Turbo UI use source-built sound libraries now, because native ICS audio blobs breaks Video Recording (on Jellybean anyway). But xLOUD still works with any audio driver as long as the kernel supports it (which it does). The downside is that the audio policy is ignorant to it, so it sometimes kills the audio-effect service.

I just need to write a script to modify (not just replace ) the build.prop and audio effect files, so it will take a while.
[Xperia Play Android Development] Dany XP:
Excellent.

But in editing build.prop, keep in mind what we already have to edit (farenheit fix) to make touchpads working