Search results

Unable to file report as the Yuga isn't in the dropdown list. That might need raising as an issue in itself.

I believe he's still working on Carbon ROM. But he has been telling people he was going update the Xperia Z Revolution ROM to KA08 and incorporate the .235 fixes - apparently he was going to do it within the week when the thread went down - but that was a fortnight ago.

Apologies if this has been covered already, but is anyone else having problems with using the dock buttons when the phone's in landscape? I only noticed it yesterday as I got the Kidigi dock, tried to access app drawer and nothing happens when you push the on-screen buttons!

Apologies if this has been covered already, but is anyone else having problems with using the dock buttons when the phone's in landscape? I only noticed it yesterday as I got the Kidigi dock, tried to access app drawer and nothing happens when you push the buttons!

The NFC firmware update zip (from .253) for people coming from .434; is that purely for Carbon ROM or would it work with other custom ROM's, like CM 10.1 etc?

It's just a question man, and a valid one at that. Closing a thread on the 20th of May, 2 days after you've said you'll have uploaded new KA firmware, then posting on 21st May here on the Carbon thread that you're going to be updating the KA firmware, but the KA thread is still closed? What gives?

But the thread was closed 4 days ago! What gives, Krab?

Update the KA Rom? But you've closed the thread!

Move it to the root of system first, then adjust the permissions as stated above, then drop it into system/apps

Hi krab, ETA on KA08? Thanks in advance and for previous sterling efforts!

I think you'll find unlocking the bootloader *does* void the warranty, otherwise Sony wouldn't be saying, "if you unlock your bootloader, your warranty will be void": http://unlockbootloader.sonymobile.com/what-does-it-mean-unlock-boot-loader

I used the KA ROMs last year for a while and found them pretty good for the most part. Interested to see krabappel is now working on the Xperia Z, but are the godawful WiFi issues resolved in this ROM?

I think you'll find the camera isn't working - it's only working internally at Sony as it's using their own proprietary binaries. They're not being released at this stage. Quite why this is, I don't know, as I think Sony have shared their binaries in the past with the FXP and CM teams.

Anybody having problems with the Z and a Netgear router, the problem isn't completely fixed in FXP215, but I did find changing my WiFi channel on the router helped pull in a much steadier signal. Previously when I was on channel 1, the phone could access wifi and facebook etc, but couldn't see...

There seems to be some sort of clipping issue when using headphones on FXP215. Mainly with the right channel, once it gets past a certain volume it just starts cutting out. I've tried 3 different sets of earphones with it to verify the problem - some cheap Logik earphones, the earphones that...

My wifi and mobile signal bars were always blue prior to FXP210, don't think it's anything to do with strength; if you've got wifi, your wifi signal is blue. Period. Had another look. I wiped the dalvic cache before I applied 210. Went back in the recovery, flashed gapps again 20121011 (or...

Seems to be some sort of problem on the XS with wifi/mobile signal in the status bar. It's not changing colour when connected to a signal. Staying grey. Due to the glitching with the colours, I'm not able to access the Play Store. Other apps, like Facebook, I can still access.

In other news, it seems there may be some corruption in the .ftf file originally provided. Three of the T users I know have updated to JB, two succesfully, but one is experiencing severe difficulties with associated suspected internal memory corruption. Is anybody able to provide a new .ftf and...

Perhaps when you allowed Superuser access, the 'remember' box on the Superuser notification somehow got unticked? Just a thought, as I've installed Rundgong's fix, the receiver apk, and the original store Illumination Bar apk, allowed root access and haven't had to grant anything since the...

Trouble with that is, the original post makes no mention of a new kernel. And there's nothing on the FXP Google site, either about a new kernel for 201. I would've thought a problem with wifi would definitely be a problem with the ROM/kernel/mod. Trouble with this site is there are far too many...

If the Walkman supplied with this mod is the latest version of Walkman...there is no widget for Walkman in the latest version of ICS from Sony.

Hmmm. Coming soon - perhaps the date in the title bar of this thread is dead giveaway the update is coming today?

Well that's obviously balls, as the updates have been coming thick and fast across the board; phone and tablet. It's just a shame Sony has overload its portfolio to a point where there can be a wait, as they've bogged themselves down in terms of making updates for the S, P, U, Ion, Sola, Go...

Root it with Bin4ry's backup/restore root kit. Install CPU Master, set both the speed bars to 1GHz, choose performance, apply. Then reboot. Might fix the issue.

Why would you need to see the battery icon if you're plugged into the mains? The charge level is displayed on the lockscreen anyway, and if you run CPU Master, it'll be displayed on a widget.

Install ROM toolbox, navigate to where you can install fonts. Install the Roboto font, either from the server list provided or from the phone. Simplicity itself.

The other reason for saying no to root at that particular point in 2.7's steps was that because the AiO tool wasn't copying the update over like it should, there was nothing to root until I manually moved everything about. Pretty important step to make sure was working - can't believe Condi...

I've already installed your 5.1 kernel, on the basis it's perfectly suited for SSpeed ROMs? So now I have to flash back to Doomkernel to reflash 11.1?

It's great you managed to upload it again. However, the goddamn AROMA installer won't work now, so yet again there's a problem.

I have to agree with the above from Gassity: as much as I appreciate the work put into these ROMs, it would be really great if you could release them to other people to test before you release them and it would be really great if you could upload the fix tonight. I updated to KA11 over the...

No - you need an unlocked bootloader and a different kernel than the one provided in the official ROM.

Use the volume buttons and home key to navigate through the menus

KA09 working fine and dandy with the latest systemUI patch, though I don't seem to be able to get QuickPanel running. Hopefully this will be fixed in the KA09 patch coming out today. Fingers crossed for krabappel!

Doom, Is there any chance of this being assembled as a recovery flashable package? There's a lot of people on here having trouble activating things like ClearBass too, could this be incorporated as well? Thanks

Ooooooooooooooooooooooooooooooooooooooooooooooh I finally sat down with this for an hour yesterday, installed Doom's v3a kernel, a .73 pre-rooted img then KA02 and finally KA03. What a great ROM! Clean, smooth, fast. Worth the wait and the argy bargy to get it installed. Just messing around...

It's all well and good offering a little wink and saying I need to install KA02 first apart from two problems: 1) There is no link for KA02 in your first post 2) You completely missed a previous post I made, saying there is no KA02 link. Link. Please. ---------- Post added at 10:07 AM...

1) I installed Doom v3a through fastboot. Rebooted fine 2) I installed the pre-rooted .73 through fastboot. Rebooted fine. 3) I installed KA03 through recovery - bootloop every. single. time. Why would I flash with a kernel and baseband - all the prerooted firmwares I've seen have been .img...

This ROM seems really interesting, however for new users it says in your instructions to flash KA02 and then KA03. Seems simple enough, except you don't provide a link to KA02!!!! ---------- Post added at 08:24 PM ---------- Previous post was at 08:11 PM ---------- Ok. So I've followed this...

You should do - have you installed Busybox?

Hi Guys, Thought I'd post again, try to make a tidier post and also bring information to people who might not have waded through the 400 posts to get to my little walkthrough. So: 1- Download US ICS FIRMWARE from post #1 on this thread. 2- Copy it to external SD, 2- Download, install and run...

Yep, the tool creates a hack-recovery for you, so if you're having problems, delete the file from both the AiO folder on the PC AND the SD card, then start again. Worked wonders for me, along with following djlars and mine's tips

Replying to myself: Anyone who has tried and failed with the update, make sure you wipe the hack_recovery from the SD card AND the PC. 1- Download US ICS FIRMWARE from links to All in One 2.7 in post #1 here. 2- Copy it to external SD, 2- Download, install and run v2.7 AiO - goto 'Custom...

Anyone who has tried and failed with the update, make sure you wipe the hack_recovery from the SD card AND the PC. 1- Download US ICS FIRMWARE from post #1 here. 2- Copy it to external SD, 2- Download, install and run v2.7 AiO (also in post #1)- goto 'Custom Rom' submenu, choose '1 - Decrypt...

Looks like djlars is on the money with this - I post something here http://forum.xda-developers.com/showpost.php?p=25374728&postcount=43 rambling on about problems with the tool and it looks like I and djlars were right - there is a bug in the AiO - I pulled my card after decryption, copied the...

After loads of tinkering, I finally got something sorted with this, only to get the same message as bandrea15! Gaaaaaaaaaaaaaaaaaaaagggghhhhhhh!

EDIT: So yeah, I was up until 02.00 last night, spending 90 minutes messing about with this. This morning I've done a factory reset on my device and run the whole thing again, TWICE, only to get the same damn message: assert failed: mount("ext4", "EMMC", "dev/block/mmcblk0p8", "/datapp")...

So yeah, I was up until 02.00 last night, spending 90 minutes messing about with this. This morning I've done a factory reset on my device and run the whole thing again, TWICE, only to get the same damn message: assert failed: mount("ext4", "EMMC", "dev/block/mmcblk0p8", "/datapp") E:Error in...

So yeah, I was up until 02.00 last night, spending 90 minutes messing about with this. This morning I've done a factory reset on my device and run the whole thing again, TWICE, only to get the same damn message: assert failed: mount("ext4", "EMMC", "dev/block/mmcblk0p8", "/datapp") E:Error in...

You signed custom zip will be in the _signed folder in the AiO 2.7 folder - where you unpacked the .7zip files for the tool itself.

You're welcome. Let me know how you get on, I couldn't get ICS to install on my first go. Having another bash now!