[Xperia SP General] Parkside:
Latest Downloads

CM10.1 http://d-h.st/i3V

CM10.2 https://drive.google.com/file/d/0B1V_hMyelDz0Rm1nenlqT2JKWkE/edit?usp=sharing AS OF 21.11.2013

UNOFFICIAL FAQ FOR CM10.1/10.2

DOWNLOAD AND INSTALLATION

Q: Where’s the download?A: The initial FXP release had an incorrect kernel – you can download a working version of ROM from here. http://d-h.st/TPT

This ROM has since been updated a download can be located here. http://d-h.st/i3V

If you wish to try a CM10.2 (that’s Jelly Bean 4.3 – have Sony actually released a 4.3 ROM yet?) one can be downloaded from the link above.You can also download the correct version of GAPPS for Jelly Bean 4.3 here. http://brintaylor.info/Android/CM/gapps/

For the CM10.2 build you should use this link to report bugs. https://docs.google.com/forms/d/185s...9UINQ/viewform

Uberlaggydarwin plans to take a 'light touch' approach to support via XDA, so don't necessarily expect an answer to a query if you post in this thread ;)

It seems like FXP have delayed releasing for our device for now, but information about CM builds that are being actively supported and developed can be found in this thread for now.

Q: How do I install?

A: You need an unlocked bootloader and an installed recovery. BACK UP your current ROM to your external SD card. Put the ROM and GAPPS on your external SD card. Boot into your recovery, do the necessary wipes, flash the ROM, flash GAPPS, reboot, victory. Disclaimer: if it breaks your phone, it’s your fault.

Q: Do I need to install the supplied kernel before installing the ROM?

A: No, unlike older xperia models CWM is able to flash both the kernel and the ROM at the same time. There is no need to use fastboot or flashtools to flash the kernel first, just a working recovery and an unlocked bootloader on your phone.

Q: Can I use another kernel instead?

A: No, for now only the supplied kernel will work.

Q: I’ve installed the ROM but can’t find the play store?

A: Immediately after installing the ROM you should install the 4.2.2 version of GAPPS (Google Apps) – this installs the play store and several other applications that Google regard as essential to the Android experience. This can be found here – http://goo.im/gapps/gapps-jb-20130812-signed.zip

Q: How do I update to the latest version of the ROM?

A: Once you’ve downloaded the latest version to your SD card, boot into recovery. No need to wipe your data, though you probably should wipe cache and dalvik cache (I don’t know whether this is done automatically as part of the installation but it can’t do any harm). You don’t need to install GAPPS again as this is a firmware update, not a new installation.

However if you’re moving between versions i.e. 10.1 to 10.2 you should definitely do a factory reset – the ROM may well work fine without a data wipe, but it may not and any problems might not be immediately noticeable (making bug tracking difficult). I would advise you NOT to report bugs if you’ve moved between android versions without a factory reset.

Q: When will they release a version that works on a locked bootloader?

A: Never. Some the features of the ROM simply won’t work very well/at all on a stock kernel. If you are rooted you can simulate some of the features with apps and mods though.

POST-INSTALLATION QUESTIONS

Q: I’ve installed the ROM – I can use Titanium Backup to reinstall all my apps right?

A: Yes and no. They may work fine, they might not – you are better off letting Google’s back up service restore all your apps. If you restore an app using Titanium or similar software and it’s buggy, there’s no point reporting it – re-install the app instead, perhaps even the ROM.

Q: 4G isn’t working – what do I do?

A: It’s not enabled by default on CM10.1 so you must do the following.

Go to the dialpad/phone.

Dial in the this number: *#*#4636#*#* (This will bring up "Phone info").

Tap WCDMA from under "Set preferred network type".

Select "LTE/GSM/CDMA auto (PRL)".

The 4G LTE network should now be activated.

Q:Where’s USB mass storage?

A: After ICS Google stopped including it in their Android builds, as such mass storage mode is not a feature that was kept by CM for Jelly Bean. Individual manufacturers do what they want though, which is why Sony, Samsung and others still have it. Skilled modders may be able to add to ROMS based on this development, I reckon they might be able to patch this one to include it too

Q: This ROM is buggy as hell and drains my battery – how do I let the developers know?

A: Logcat and/or a kernel log - or it didn’t happen for bugs.

Better battery stats for battery drain.

There are lots of guides out there showing you how to take logs and how to record battery stats.

Anecdote – I activated Google+ yesterday as I like the auto-photo upload feature but wakelock detector revealed it was killing my battery (I think it’s dodgy on stock too). The choice was the app or the ROM, I chose the ROM.

Q: After installation something random doesn’t work – what do I do?

A: Check the thread to see if other users have mentioned the issue and to see if the developer has posted a solution. Also, you’re on XDA, you’re an advanced user, you have unlocked your bootloader, thrown out your warranty and accepted the consequences. So please try to resolve the issue yourself. In general if you are having a problem and no one else is, it will be a problem with your phone/download/installation.

Phone - obviously a hardware fault can't be foreseen by the developer and have you unlocked your bootloader!

Download - Most downloads are fine. But I've flashed enough ROMS to know that sometimes a file gets corrupted and sometimes they say they are complete when they are not. Sometimes I've been careless and clicked on the wrong download, sometimes the website hosting the site is haveing a a bad day, sometimes the developer puts the download in the wrong place too :) The first things to check are the name and size of the file - if these tally you're probably fine to install. If you want to be extra cautious you can check the MD5 hash to see if your download matches. Sometimes the file gets corrupted on upload - nothing anyone can do about that...

Installation - (Please back up your orignal ROM). Typically you'll be installing this ROM using a recovery from another ROM/kernel/MOD - so if you have problems installing , it might be that you have a bad recovery.

The wipes really need to be done to ensure the smooth running of your phone, but as you've backed up, the 15 seconds you spend properly wiping should not be much of a chore.

If you're one of the first downloaders, I guess there is some merit in saying you couldn't install, but if it's been out for a while and there are loads of posts saying 'what a great ROM' there's little point posting 'won't install'. Describe exactly what you've done and someone might help.

Bear in mind there are apps/hardware that the developers of this ROM won’t have heard of/care about - so if something doesn’t work properly on your phone it could be for numerous reasons. Either way, this may be something you have to live with. Alternatively, if the app is essential to you, you’ll have to return to a backup.

Remember this ROM is in development, there are no promises of perfection and no one is forcing you to use it. However, the right kind of feedback is always welcomed by the developers and may be acted on – the wrong kind will often be ignored.

Q: What does a perfect bug report look like?

A: Go here. http://xdaforums.com/showpost.php?p=46935640&postcount=313

Q: What are the known bugs?

A: FM radio doesn’t work.

A: Attempts to offline charge cause the phone to boot.

A: 4G activation is not remembered between boots for CM10.1.

A: For 10.2 there is a known battery drain issue related to WiFi. See the solution here. http://xdaforums.com/showpost.php?p=46923723&postcount=301

The following issues have been reported by some users, but others say it doesn’t affect them. They are regarded as hardware issues – anecdotal ‘me too’ posts will be ignored. However, supply a log and your phone’s date of manufacture and the developer may look into it (this might help you prove that your phone is faulty, so it’s a worthwhile exercise).

Erratic touch screen response.

Reading external SD Card in recovery and in use.

As others have said this is possibly the most stable first CM build they’ve encountered and I agree – it’s definitely suitable for daily use. I've been using it from release and haven't had a single reboot/app crash or freeze.