[Q] How to fix bluetooth broken after 4.3 upgrade - Sony Xperia T, TL, TX, V

Bluetooth in my XperiaV was broken by the upgrade to 4.3, which I have performed using PC Companion.
It tries to turn on for a few seconds and turns off.
Have you experienced that kind bluetooth behaviour and found solution, which you could share with me?
I would be thankful.
EDIT:
FM tuner does not start too. It seems there is problem with a driver for IC responsible for BT and FM.

Did you ever figure this out? Mine isn't working. On Xperia T LT30A version

link1227 said:
Did you ever figure this out?
Click to expand...
Click to collapse
No. At first I have waited for some help from here. Later I have found an information about ROM upgrade for LT25i and LT30a, which is apparently on it's way [here], so I have decided to wait for the new ROM. I expect it will solve this and maaany other bugs introduced by the recent upgrade.
As to the other bugs, to list a few:
- FM tuner does not work,
- there are spontaneous restarts,
- Skype crashes instead of starting.
Interestingly it happen once that after one of the spontaneous restarts BT started to work, but WiFi has stopped. I was able to turn on/off BT, connect to BT headset and use it. As Wi-Fi is more important to me I have tried to make it work once again and when I eventually managed to do so BT stopped to work. So far I wasn't able to make it work once again.
If the timespan between ROM certification and availability for the newest ROM will be the same as it was for the current one, then it would mean we should get it within one week from now. I hope it will fix all the bugs.

I actually figured it out.
Using root explorer, go to data and rename the usf folder to usf1. Reboot the phone and the nfc should do an update.

Bluetooth works well on my phone and my wife's phone as well (two different lt25i which were upgraded from stock 4.1.2 to stock 4.3).
I see many complains about bluetooth, wi-fi, battery drain, volume bar, etc and I can assure you that none of the two lt25i phones suffer from that.
The only bugs we have noticed are:
- the camera video recording autofocus buzz noise and some low-light inability to focus
- gps may sometimes reboot the phone
- ocasional (and rare) reboots
Battery drain is similar to 4.1.2 and we are not even using Stamina.
(FYI, if you turn off Google location services you'll notice the difference)
Our radio works well too.
Maybe you have flashed a ROM which does not tune FM frequencies acording to your geography ?
I believe that many "bugs" reported are due to incorrect flashing.
My 50 cents...

arturiu said:
Bluetooth works well on my phone and my wife's phone as well (two different lt25i which were upgraded from stock 4.1.2 to stock 4.3).
I see many complains about bluetooth, wi-fi, battery drain, volume bar, etc and I can assure you that none of the two lt25i phones suffer from that.
The only bugs we have noticed are:
- the camera video recording autofocus buzz noise and some low-light inability to focus
- gps may sometimes reboot the phone
- ocasional (and rare) reboots
Battery drain is similar to 4.1.2 and we are not even using Stamina.
(FYI, if you turn off Google location services you'll notice the difference)
Our radio works well too.
Maybe you have flashed a ROM which does not tune FM frequencies acording to your geography ?
I believe that many "bugs" reported are due to incorrect flashing.
My 50 cents...
Click to expand...
Click to collapse
What about 100% charge bug? (At 100% phone shut down-->no alarm at morning for example).
Did you notice this bug into your XV?
I noticed that on stock branded rom (official via seus).
No BT issues at all btw.
Sent from my SK17i using xda app-developers app

link1227 said:
Using root explorer, go to data and rename the usf folder to usf1.
Click to expand...
Click to collapse
Is there a way to root 4.3 stock ROM with locked bootloader?

przemhb said:
Is there a way to root 4.3 stock ROM with locked bootloader?
Click to expand...
Click to collapse
The only way I know of doing it, is downgrading to an old 4.1.2 rom and rooting, and then upgrading back.
I unlocked my bootloader because it was much easier

link1227 said:
The only way I know of doing it, is downgrading to an old 4.1.2 rom and rooting, and then upgrading back.
Click to expand...
Click to collapse
My 4.1.2 was rooted before the upgrade to 4.3. Upgrade has broken root.

przemhb said:
My 4.1.2 was rooted before the upgrade to 4.3. Upgrade has broken root.
Click to expand...
Click to collapse
You should still have cwm recovery. Boot into it by hitting volume down at the sony screen until it vibrates. Then install the root supersu package

link1227 said:
You should still have cwm recovery. Boot into it by hitting volume down at the sony screen until it vibrates. Then install the root supersu package
Click to expand...
Click to collapse
Now I regret, I haven't installed CWM.
Is it possible flashing latest upgrade didn't succeed due to lack of free space on data partition? When it has finished there was only about 90MB left.
On the one hand it changes only system partition, but on the other it may use data partition for some temp data (although should use cache first place).
I hope that upcoming update will fix the bug. If it won't be the case, then I guess I will have to reflash ROM.
Does repair procedure of the PC Companion leave data partition intact?

alfanumerica said:
What about 100% charge bug? (At 100% phone shut down-->no alarm at morning for example).
Did you notice this bug into your XV?
I noticed that on stock branded rom (official via seus).
No BT issues at all btw.
Sent from my SK17i using xda app-developers app
Click to expand...
Click to collapse
Oh yes, I forgot to mention that "bug".
No, both my phone and my wife's charge properly up to 100%
Not an issue here...
That's why I'm surprised with so many of these "bugs", while I have two phones at home that work (almost) perfectly.
And with 4.1.2 it was the same story. People complaining about so many things, and I could see bothof our phones with no such issues.
I only had an issue with SD card corruption, which seemed to be related with overheating and bad contact in the card slot.
I had .145 firmware and my wife had .140 (we're now both on 4.3 stock) and the upgrade even kept all our settings.
FYI, my phone was rooted but locked BL (I just installed a couple of tweaks).
My wife's was not even rooted.
I think that if we use the phone as close as factory settings, life will be easier.
Anyway, I'm always looking for potential tweaks to improve my experience, and because of that I'm waiting for a root exploit that doesn't require unlocking BL or flashing code that doesn't come directly from Sony servers.

przemhb said:
Now I regret, I haven't installed CWM.
Is it possible flashing latest upgrade didn't succeed due to lack of free space on data partition? When it has finished there was only about 90MB left.
On the one hand it changes only system partition, but on the other it may use data partition for some temp data (although should use cache first place).
I hope that upcoming update will fix the bug. If it won't be the case, then I guess I will have to reflash ROM.
Does repair procedure of the PC Companion leave data partition intact?
Click to expand...
Click to collapse
I have no idea. Have you tried unlocking your boot loader?

link1227 said:
I have no idea. Have you tried unlocking your boot loader?
Click to expand...
Click to collapse
I'd rather leave it locked, as I don't need to flash custom ROMs. At least at the moment. So far KitKat based CM is not stable, stock KitKat is "under investigation" and stock 4.3 update, probably bug fixing release, is about to be available.

przemhb said:
stock 4.3 update, probably bug fixing release, is about to be available.
Click to expand...
Click to collapse
As the mentioned update (.199) has fixed only NFC issue and not BT and FM ones, I have decided to give PC Companion's "repair" a try.
To put it short - it did the trick. BT and FM radio are working fine now.
Apparently something must have gone wrong, when I upgraded from 4.1 to the 4.3 (.0.295) and there was free space shortage.
As I had not root I have used stock backup and restore app. It managed to backup and restore all apps installed from the Google Play (with data).
The only thing I am missing right now is a root.
I have not decided to unlock the bootloader to make rooting possible, because I do not want to loose NFC capability, my data (some sources claim even SD card contents would be deleted), Bravia Engine etc.

przemhb said:
As the mentioned update (.199) has fixed only NFC issue and not BT and FM ones, I have decided to give PC Companion's "repair" a try.
To put it short - it did the trick. BT and FM radio are working fine now.
Apparently something must have gone wrong, when I upgraded from 4.1 to the 4.3 (.0.295) and there was free space shortage.
As I had not root I have used stock backup and restore app. It managed to backup and restore all apps installed from the Google Play (with data).
The only thing I am missing right now is a root.
I have not decided to unlock the bootloader to make rooting possible, because I do not want to loose NFC capability, my data (some sources claim even SD card contents would be deleted), Bravia Engine etc.
Click to expand...
Click to collapse
For most of the so-called "bugs" that these forums report, a simple PC Companion repair would do the trick.
This is the Sony recommended way to overcome issues during flash process.
You will end up with a stock rom, no root/UBL, but your drm keys will be back (important for Bravia Engine, ...).
From my experience, too much hacking = messy device.
Personally, I'll root my lt25i 4.3 device based on an exploit for locked boot loaders when it is found.
Until then... using stock with almost no bugs at all.
And so does my wife, which also has an lt25i with stock 4.3.
The only relevant bugs we found on 9.2.A.0.295 (yep, still waiting for latest ota update to be available :-/:
- camera background noise and slow focus issue
- gps random reboots

Related

My experience in downgrading from 4.2.2 to 4.1.2

DISCLAIMER: This is my personal experience, it may not be the same for you, YMMV and all that.
Well, short story is that I got fed up with my Nexus 7 having performance of my ancient Win Mobile smart phones. It got to a point where no matter what ROM I ran, be it stock 4.2.1, 4.2.2 or custom Roms from XDA, my Nexus would struggle with even simple tasks.
Examples:
closing tab in chrome - 2-3 seconds
Rotating a screen (nova launched home, only 1 page total) - 3-6 seconds
Launching NFS (game) - 3-6 seconds before I'd see the loading screen, would load for about 15-20 seconds. In game fps would dip to what felt like around 25-30 fps.
Battery dying at 10-15% (tried everything, including disassembly).
After trying everything I decided to ditch the 4.2+ and go back to how it was when I bought it. Reason being that I remember sudden increase in overall system lag when Google released 4.2.
So, here I am running 4.1.2, so far on my second day of use. Here's what I see:
Chrome - much more responsive, tabs client immediately, pages redraws quicker on scroll.
Rotating screen - 1, maximum 2 seconds.
Launching NFS - immediate, loads for about 5-7 seconds. Game interface way more fluid and responsive. Game runs at what feels like fluid 60 fps most of the time, with many cars on screen dips to, I'd say, around 40 fps.
Battery is now at 5%, not shutting down, which is good news to me.
Obviously, things like performance can be very subjective, but overall I do see huge improvement in performance.
Maybe it will work for other people as well who are as annoyed by 4.2.2 sluggishness as I was.
Did you reinstall 4.1.2 from scratch - including fastboot erasure/formatting of file systems suggested by the factory install instructions?
I'm wondering if you would see essentially the same performance if you now reinstall 4.2.2 using exactly the same procedure. (Obviously, you might want to make a full Nandroid backup of the 4.1.2 install so you could nuke 4.2.2 and restore back to 4.1.2 easily).
For instance, if the performance issues were related to filesystem corruption or just simply buildup of app "cruft" over time, or a misbehaving app due to some fault condition happening sometime after the original 4.2.x ota upgrade. (Kinda like re-installing the same version of Windows always seems to speed it up, LOL)
I guess the point is that the most likely root-cause of "lag" is something to do with flash memory (filesystem) I/O as it is the slowest operation in the device. A fair comparison would be fresh install vs. fresh install.
cheers
Try using Clemsons Elite 1500 Extreme Kernel and Cookies and Cream if you can find them, they blow away any 4.2 Kernel/Rom combo and its not even close.
I agree with darkdvr with games being laggy on the 4.2.2. Playing nova 3 stutters a lot.not too pleased with it.the battery drain is also pretty crazy compared to what they say the battery should last with certain usages.I'm also going to downgrade to 4.1.2 to see the difference.hopefully it works and plays better than this 4.2.2. I also think that rooting has something to do with a lot of lag. When stock its smooth and fluent opposed to after rooting. You get pauses and stutters.gonna give it a go tonight
I never delete fastboot, but I formatted sdcard/system, and all caches. I holy doubt that this case is that "build up" that we are all familiar with on Windows, since 4.2.2 was laggy for me right away, as soon as apps are installed and launcher configured - nexus immediately becomes a slow ass lag sloth. It was always rather terrible for me, although I am hyper sensitive to lags and delays on any system. I know most people aren't that anal about it.
Interestingly enough, I restored almost all my apps with titanium, including their data, s I can say that its not the apps, its the system. Using android since 2.1, I can safely say that 4.2.2 is the laggiest and most messed up release since, probably, eclair. They really dropped the ball here. I hope 4.3 will be QAed more thoroughly.
bftb0 said:
Did you reinstall 4.1.2 from scratch - including fastboot erasure/formatting of file systems suggested by the factory install instructions?
I'm wondering if you would see essentially the same performance if you now reinstall 4.2.2 using exactly the same procedure. (Obviously, you might want to make a full Nandroid backup of the 4.1.2 install so you could nuke 4.2.2 and restore back to 4.1.2 easily).
For instance, if the performance issues were related to filesystem corruption or just simply buildup of app "cruft" over time, or a misbehaving app due to some fault condition happening sometime after the original 4.2.x ota upgrade. (Kinda like re-installing the same version of Windows always seems to speed it up, LOL)
I guess the point is that the most likely root-cause of "lag" is something to do with flash memory (filesystem) I/O as it is the slowest operation in the device. A fair comparison would be fresh install vs. fresh install.
cheers
Click to expand...
Click to collapse
I'm interested. Could you post the steps to do the downgrade?
hotsync100 said:
I'm interested. Could you post the steps to do the downgrade?
Click to expand...
Click to collapse
It's really easy with the Nexus 7 toolkit - get it HERE (dev forum).
Basically, I backed up user apps with Titanium Backup and copied the backup to my PC.
Launched the toolkit, created nandroid backup of 4.2.2 ROM (option 4 in the Toolkit AFAIR).
Booted into the recovery, formatted everything (sdcard, system, all caches).
From recovery booted into fastboot mode (all volume buttons + power button).
With toolkit, downloaded and installed 4.1.2 factory ROM and installed it onto Nexus.
For some reason first one didnt boot for me (stuck at nexus X), so I cleared cache/system data, redownloaded it and flashed it again. Thankfully, Toolkit guides you through the steps.
Then, an optional step, I used a hack apk from xda to prevent nexus from checking for ROM OTA updates. Now I'm at 4.1.2 and my Nexus is finally back to its original snappiness.
is it possible to run 4.1.2 with 4.2.2 bootloader?
RobYyY said:
is it possible to run 4.1.2 with 4.2.2 bootloader?
Click to expand...
Click to collapse
I highly doubt it, and it would ruin your experiment "cleanliness", I'd say.
I recently attempted to downgrade to 4.1.2, to see what all the fuss is about... but without flashing the bootloader. My attempt didn't get very far...
Code:
checking product...
OKAY [ 0.031s]
checking version-bootloader...
FAILED
Device version-bootloader is '4.18'.
Update requires '3.41'.
finished. total time: 0.250s
Press any key to exit...
I'm loathe to unnecessarily flash the bootloader (unless absolutely required to do so). So I abandoned my attempt...
----
All I can say is 4.1.2 must be pretty damned fast, because I've never had any problems with 4.2.2.
I have noticed though (and this could just be the 'placebo' effect), that wiping CACHE and DALVIK CACHE does seem to make for a marginally more smoother experience.
LagFix (fstrim) Free is also widely reported as fixing lag issues in 4.2.2... although I can't say I've noticed much difference after running it.
But then, as I say, 4.2.2 (custom ROM - see sig) runs liquid smooth for me anyway.
Rgrds,
Ged.
hotsync100 said:
I'm interested. Could you post the steps to do the downgrade?
Click to expand...
Click to collapse
If you wanna try manual method here is step by step guide to downgrade from 4.2.2 to 4.1.2 using fastboot.
Following instruction in this thread http://forum.xda-developers.com/showthread.php?t=1907796 except for
1.Download the Nexus 7 4.1.2 factory image from the link instead of 4.2.2 .
2.On Flashing the Factory Image step.
Change following line
fastboot flash bootloader
and
fastboot -w update
to match the name of 4.1.2 factory image instead of 4.2.2 for example
change from
fastboot flash bootloader bootloader-grouper-4.18.img TO fastboot flash bootloader bootloader-grouper-3.41.img
and
fastboot -w update image-nakasi-jdq39.zip TO fastboot -w update image-nakasi-jzo54k.zip
Downgraded for a bit, and did not particularly enjoy 4.1.2, and I wound up going back to 4.2.2 after completely wiping the system and accidentally having to re-update my recovery. I've noticed my battery life has finally gone back to the way it used to be when I first got my N7, and the performance seems better to me when I play Voxel Rush (only game I really play on here). I believe my problems with 4.2.2 earlier were indeed caused by a lot of crud built up from flashing previous ROMs and kernels over time.
dwxvi said:
Downgraded for a bit, and did not particularly enjoy 4.1.2, and I wound up going back to 4.2.2 after completely wiping the system and accidentally having to re-update my recovery. I've noticed my battery life has finally gone back to the way it used to be when I first got my N7, and the performance seems better to me when I play Voxel Rush (only game I really play on here). I believe my problems with 4.2.2 earlier were indeed caused by a lot of crud built up from flashing previous ROMs and kernels over time.
Click to expand...
Click to collapse
4.2.2 after flashing seems to be somewhat on par with 4.1.2, but please report back to us in several days, I bet it will slow down to a crawl.
Another easy way to downgrade would be to install cyanogenmod 10.0.0. Also, please don't start downgrading your bootloader. It shouldn't be necessary for flashing stock 4.1.2 and it might complicate things if you want to flash custom kernels in the future.
For what it's worth, I'm running 4.2.2 with no noticeable lag. I just bought it used so I did a factory reset just before updating. Maybe that has something to do with it?
Sent from my Nexus 7 using xda app-developers app
Hm. I have none of the problems you had on 4.2.2. I'm running 4.2.2 and it's pretty snappy.
Rotating the screen takes about 1-2 seconds.
Closing tabs in Chrome is instantaneous.
Apps launch quickly.
Battery holds out to about 3% before I plug it in.
Hm. Maybe you had a lot of apps installed? I have quite a few but not as much as some people
Do you guys have multiple user accounts? I've been playing around with it a bit, and maybe it's just me but I feel it's a bit slower when you have more than on user. Anyone else noticed this? I did a quick Google search and seems others have noticed it too.
dwxvi said:
Downgraded for a bit, and did not particularly enjoy 4.1.2, and I wound up going back to 4.2.2 after completely wiping the system and accidentally having to re-update my recovery. I've noticed my battery life has finally gone back to the way it used to be when I first got my N7, and the performance seems better to me when I play Voxel Rush (only game I really play on here). I believe my problems with 4.2.2 earlier were indeed caused by a lot of crud built up from flashing previous ROMs and kernels over time.
Click to expand...
Click to collapse
My battery life also sucks,I want to try this.
Which way did you downgrade?
demolition23 said:
My battery life also sucks,I want to try this.
Which way did you downgrade?
Click to expand...
Click to collapse
You won't have to downgrade to do this, you would just have to back up your data (the important stuff) and completely wipe your internal storage so that everything is cleaned up and ready for a re-install of 4.2.2. Then you can re-load your data. I would reccommend using Wugfresh's Nexus Toolkit for this.
dwxvi said:
You won't have to downgrade to do this, you would just have to back up your data (the important stuff) and completely wipe your internal storage so that everything is cleaned up and ready for a re-install of 4.2.2. Then you can re-load your data. I would reccommend using Wugfresh's Nexus Toolkit for this.
Click to expand...
Click to collapse
I just did that, and will post results when I have a clear picture.

[Q] should I get the 4.3 update or not??

Hey all,
I've been noticing many people complaining about various issues on the 4.3 update and m really confused that shud . Get the update or not! What are the major issues with the 4.3 update?
sumedha52 said:
Hey all,
I've been noticing many people complaining about various issues on the 4.3 update and m really confused that shud . Get the update or not! What are the major issues with the 4.3 update?
Click to expand...
Click to collapse
The main issue is poor ram management, seems to consume huge amounts of ram.
I would recommend waiting for kitkat 4.4update before updating
Regards
raziel123 said:
The main issue is poor ram management, seems to consume huge amounts of ram.
I would recommend waiting for kitkat 4.4update before updating
Regards
Click to expand...
Click to collapse
Thankx
Actually I did not see anything wrong with the Ram Management on 4.3. I think update to 4.3 it's a good idea, the battery was improved like 35% and is more efficient than 4.2.2. Camera was fixed in the case you will want to unlock bootloader. 4.3 can be rooted without unlocking the bootloader.
If you do a clean fresh installation you should not have issues of any kind. Of curse is not a big deal, we still can't move the apps to SD and this is a very bad thing but the 4.3 can be rooted so many option will be available. You can wait for 4.4 but at the moment still no eta of when it will be released so I think is a good improvement, for now, for your phone.
molecular
eclyptos said:
Actually I did not see anything wrong with the Ram Management on 4.3. I think update to 4.3 it's a good idea, the battery was improved like 35% and is more efficient than 4.2.2. Camera was fixed in the case you will want to unlock bootloader. 4.3 can be rooted without unlocking the bootloader.
If you do a clean fresh installation you should not have issues of any kind. Of curse is not a big deal, we still can't move the apps to SD and this is a very bad thing but the 4.3 can be rooted so many option will be available. You can wait for 4.4 but at the moment still no eta of when it will be released so I think is a good improvement, for now, for your phone.
Click to expand...
Click to collapse
Thanx... So I am supposed to wipe off everything before I update as in all games nd stuff?? M sorry for the silly things m asking but I dont know much about this stuff found this forum usefull so...
sumedha52 said:
Thanx... So I am supposed to wipe off everything before I update as in all games nd stuff?? M sorry for the silly things m asking but I dont know much about this stuff found this forum usefull so...
Click to expand...
Click to collapse
If you don't have a official update from PC Companion and you have to use Flashtool v0.9.13 and a FTF .290 Android 4.3 from here http://forum.xda-developers.com/showthread.php?t=2469191 Yes, you should wipe all because it's recommended for a clean installation. You still can keep your data anyway, just uncheck the option Wipe Data in Flashtool before flash the FTF.
I give you few tips: backup all what you need to SD, switch off your phone and keep pressing volume down and connect to pc via usb, keep pushing the volume down all the time when do this, let windows install the drivers and when your phone will be connected in Flashmode open the Flashtool, select the firmware (put the firmware in the flashtool folder) leave the flashtool in default (or unclick "Wipe Data" if you want keep your data, do it on your own risk) and flash the FTF, remember to keep pushing volume down all the time, when the green bar of the progress will start you can leave your phone alone.
All the FTF XXX.X.A.0.290 in the list are Android 4.3, download Central Europe if you are there and flash. You can use also NCB.

problems after root

Well, since I rooted my xsp it seems to have lots of lags but those lags start after using the phone for a while and opening a few applications.Then it usually goes slower and slower until it completely crashes and reboot automatically or I reboot.
I also noticed that ram is getting full for no reason and as I said above, before it completely crashes it is trying to open the settings and then needs reboot.
Maybe I need to unroot? Just know that I unlocked the bootloader and rooted correctly without problems if it matters.
billaras481 said:
Well, since I rooted my xsp it seems to have lots of lags but those lags start after using the phone for a while and opening a few applications.Then it usually goes slower and slower until it completely crashes and reboot automatically or I reboot.
I also noticed that ram is getting full for no reason and as I said above, before it completely crashes it is trying to open the settings and then needs reboot.
Maybe I need to unroot? Just know that I unlocked the bootloader and rooted correctly without problems if it matters.
Click to expand...
Click to collapse
Try another kernel?
Nanostray said:
Try another kernel?
Click to expand...
Click to collapse
How can I do that? I don't want to root it with another kernel. Ι prefer to unroot if it's possible but I don't know how.
billaras481 said:
How can I do that? I don't want to root it with another kernel. Ι prefer to unroot if it's possible but I don't know how.
Click to expand...
Click to collapse
Root cannot affect your phone's performance, because all it does is give you root priviliges (acces to the system itself). I don't think unrooting will solve anything
Nanostray said:
Root cannot affect your phone's performance, because all it does is give you root priviliges (acces to the system itself). I don't think unrooting will solve anything
Click to expand...
Click to collapse
Then what should I do? I need to reboot my phone about 3 times per day..
Maybe I need to relock the bootloader? Is that even possible?
billaras481 said:
Then what should I do? I need to reboot my phone about 3 times per day..
Maybe I need to relock the bootloader? Is that even possible?
Click to expand...
Click to collapse
connect your device to pc companion and choose repair...that should flash the latest firmware to your device and wipe out the root...
headache59 said:
connect your device to pc companion and choose repair...that should flash the latest firmware to your device and wipe out the root...
Click to expand...
Click to collapse
If bootloader unlocked, PCC or SUS will not recognise your phone, so relock first. OR you can flash another kernel with better RAM management. Are you using Doomlord's kernel?
May be a solution
billaras481 said:
Well, since I rooted my xsp it seems to have lots of lags but those lags start after using the phone for a while and opening a few applications.Then it usually goes slower and slower until it completely crashes and reboot automatically or I reboot.
I also noticed that ram is getting full for no reason and as I said above, before it completely crashes it is trying to open the settings and then needs reboot.
Maybe I need to unroot? Just know that I unlocked the bootloader and rooted correctly without problems if it matters.
Click to expand...
Click to collapse
Hi !
I've experienced such sort of problems. I was on stock 4.3, I've unlocked the bootloader, install a Doomlord kernel (CWM) with flashtool.
I thought installing a custom rom (Advance XPERIA v1.2) will solve the problem, but it didn't ...:crying:
In desperation, I thought going back to a stock kernel.
To do this, I've download a full firmware (ftf), and with flashtool, I've flashed the firmware in flashmode but with these options :
_ Wipe: all unchecked
_ Exclude : all checked but kernel
_ Misc : all unchecked.
Reboot : no more recovery, but I haven't lost root, Titanium Backup doesn't complain, Terminal su remount -o remount,rw /system work, root browser Ok, ...
I've past the last two hours trying to make the phone laggy and instable, without success
Games, Album, Google Photo, Google Play music, switch fastly settings, camera with effects ...
Only the time will tell me if this is working ...
Sorry for my poor english...
Fred.
PS: The very last DoomLord kernel (v5) seems to suffer from the same problem about the RAM ...
fred_pitoizet said:
Hi !
I've experienced such sort of problems. I was on stock 4.3, I've unlocked the bootloader, install a Doomlord kernel (CWM) with flashtool.
I thought installing a custom rom (Advance XPERIA v1.2) will solve the problem, but it didn't ...:crying:
In desperation, I thought going back to a stock kernel.
To do this, I've download a full firmware (ftf), and with flashtool, I've flashed the firmware in flashmode but with these options :
_ Wipe: all unchecked
_ Exclude : all checked but kernel
_ Misc : all unchecked.
Reboot : no more recovery, but I haven't lost root, Titanium Backup doesn't complain, Terminal su remount -o remount,rw /system work, root browser Ok, ...
I've past the last two hours trying to make the phone laggy and instable, without success
Games, Album, Google Photo, Google Play music, switch fastly settings, camera with effects ...
Only the time will tell me if this is working ...
Sorry for my poor english...
Fred.
PS: The very last DoomLord kernel (v5) seems to suffer from the same problem about the RAM ...
Click to expand...
Click to collapse
hello,
i have rooted my xperia sp device successfully. Now i have problem of volume keys not functioning. When i receive call i try to volume up the speaker but it doesnt affect. note: my speakers were working perfectly before root and speaker hardware is also good in condition. please help me out to solve this problem.

[Q] WiFi issue in JB, is there a router setting to change?

I just bought a Droid 4 that came with JB 4.1 from previous owner. Now I'm facing some issue with my home WiFi (I have an US Robotics USR9111 router): when I try to connect, wifi status remains stuck on "connecting.." phase and doesn't change.
I read that this can be a JB issue, so I tried also changing ROMS but got bootloop, so I restored to stock.
From what I understood, it is not possible to move to another Android version unless I unlock the bootloader, right? So all roms with another Android version that I see, will not work on my Droid for now?
I'm wondering if there can be some setting that I can change on my router to get it work with my phone, or at least if there is a way to unlock my bootloader (done some googling, but no luck)
Thank you in advance
Hi,
Have you tried a factory reset first?
The bootloader of OMAP devices cannot be unlocked. But there is a workaround, an application called SafeStrap. It's basically allows you to create multiple ROM partitions and install ROMs on them. Your stock ROM can remain untouched and you can switch between ROMs. You can install any custom ROM for the D4 this way. You can find the Safestrap topic in the development section.
This way you can test it if your issue is a ROM issue or not.
BTW, SafeStrap requires root.
Sent from my DROID4 using XDA Free mobile app
Thank you. I already installed Safestrap, but i come from a Sony device (Xperia Pro) and thought that SS worked like a normal recovery, and i could not install a rom with a different kernel than that on the phone. I'll try it.
Anyway, issue is rom-related and router-related: with the router at work it connects without problems, and i tried another jb rom that also worked with mine at home (came back to stock because it had other bugs).
axxel84 said:
Thank you. I already installed Safestrap, but i come from a Sony device (Xperia Pro) and thought that SS worked like a normal recovery, and i could not install a rom with a different kernel than that on the phone. I'll try it.
Anyway, issue is rom-related and router-related: with the router at work it connects without problems, and i tried another jb rom that also worked with mine at home (came back to stock because it had other bugs).
Click to expand...
Click to collapse
Stupid question, but are you using the same security settings for wireless on your router and your phone?
nagim said:
Stupid question, but are you using the same security settings for wireless on your router and your phone?
Click to expand...
Click to collapse
Sorry for the late reply: of course, I tried first with my WPA password, and then, since I experienced the problem, I've unsecured my network and tried another time setting an open network type on the phone, but same issue

[Q] Unlocked BL, relocked BL - haven't lost DRM?

Hello everyone!
Some time ago I became bored of slow stock firmware and decided to install CM11, following my good experience with Sony LWW. I unlocked BL via fastboot on ubuntu (making no backups. I will learn someday...), then installed CM11 using CM's instructions for Xperia SP. I've got a working phone, it worked for two months, but was not as fast as I thought, and in addition to that it gave me frequent all-system ANRs with a reboot, when I browsed large pages in firefox. So i decided to go back to stock.
I downloaded a stock firmware called "C5303_12.1.A.1.205_РСТ" and flashed my phone using Flashboot. Rebooted and got a working phone. Then I relocked a bootloader, rebooted again, and again got a working phone. What's more interesting, all features which need DRM still work, i.e. Bravia, Walkman information downloading, TrackID (used to break after flashing back in time).
So I have some questions. Does that mean that I've got a fully stock phone with all features and DRM's somehow? Can I check that? Do I need to worry about DRM anyway?
airbus_sai said:
Hello everyone!
Some time ago I became bored of slow stock firmware and decided to install CM11, following my good experience with Sony LWW. I unlocked BL via fastboot on ubuntu (making no backups. I will learn someday...), then installed CM11 using CM's instructions for Xperia SP. I've got a working phone, it worked for two months, but was not as fast as I thought, and in addition to that it gave me frequent all-system ANRs with a reboot, when I browsed large pages in firefox. So i decided to go back to stock.
I downloaded a stock firmware called "C5303_12.1.A.1.205_РСТ" and flashed my phone using Flashboot. Rebooted and got a working phone. Then I relocked a bootloader, rebooted again, and again got a working phone. What's more interesting, all features which need DRM still work, i.e. Bravia, Walkman information downloading, TrackID (used to break after flashing back in time).
So I have some questions. Does that mean that I've got a fully stock phone with all features and DRM's somehow? Can I check that? Do I need to worry about DRM anyway?
Click to expand...
Click to collapse
you unlocked it you lost the DRM for sure ...but when re locking everything will ne working again don't worry
flash- said:
you unlocked it you lost the DRM for sure ...but when re locking everything will ne working again don't worry
Click to expand...
Click to collapse
But how is it still working then? I just finished downloading info on my music collection, and bravia seems to work... I don't understand what I did wrong to get it working perfectly.
airbus_sai said:
But how is it still working then? I just finished downloading info on my music collection, and bravia seems to work... I don't understand what I did wrong to get it working perfectly.
Click to expand...
Click to collapse
some users even showed us the x-reality engine with UBL...so it could be working normally in some way ...so i don't know how is that could be possible ...but maybe you are lucky ....try to backup your DRM keys see if the exists (that is impossible but try it,, you won't lose anything ) :silly:
can not find camera app in menue
Hi,
I have flashed build 06/26 (dirty). Sometimes I can not find the camera - app in menue.
Under settings -> app -> activ app I can find the camera app (is installed) but I can not start them. In menue I doesn't find the app.
Has somebody the same problem?
Sorry for this "survival" englisch and I hope everybody know what I mean
flash- said:
some users even showed us the x-reality engine with UBL...so it could be working normally in some way ...so i don't know how is that could be possible ...but maybe you are lucky ....try to backup your DRM keys see if the exists (that is impossible but try it,, you won't lose anything ) :silly:
Click to expand...
Click to collapse
Yup, does not allow me to make a backup. "Backup" and "Restore" options are grayed out in Flashtool, and only "S1 dump" is available. I assume DRM keys are gone. But as long as the features are working, I won't care. I will surely make a backup of everything before doing something to a phone next time. Thanks for an answer.
wenfosi, you may have either:
1) changed the way menu is presented. Swipe from left side of the screen in menu, and select "show apps by alphabet"; or
2) accidentally disabled the Camera app. Locate it in Settings - Apps, click on it, and look if there is a button called "Enable". It should be at the top, near the "Force stop" button. If it is there, then click on it. It will change to "Disable".
Maybe more experienced users will provide more advices. Try these at first.
wenfosi said:
Hi,
I have flashed build 06/26 (dirty). Sometimes I can not find the camera - app in menue.
Under settings -> app -> activ app I can find the camera app (is installed) but I can not start them. In menue I doesn't find the app.
Has somebody the same problem?
Sorry for this "survival" englisch and I hope everybody know what I mean
Click to expand...
Click to collapse
Have you tried another camera app from the Play Store? This information helps to find the error.
By the way, your English is OK. Is it possible that you are German?
Gesendet von meinem
Sony Xperia SP - Cyanogenmod 12.1

Categories

Resources