Related
Hi, I have an SGSplus (i9001) and I've been using arco68's and ivendor's CM9 ROMs for a few months now. Right now I'm using ivendor's latest RC9 plus CastagnaIT's ExtremeUV (without any OC, I'm using the standard 245-1401 MHz range) and it's fairly stable.
I always had some problems in real-time performance: it seems to me that when there is a process background the application in foreground becomes incredibly sluggish, maybe needing 10 seconds to input a single key… then, after a bit, the background process finishes his business and things go back to normal. Using BetterBatteryStats I have pinpointed a couple of bad application and removed them and now this happens rarely enough (but still happens). But this is not my question…
On Friday I decided to try ivendor's new CM10 alpha 5 and it simply doesn't boot: no "blue boy" loader at all.
I tried both the straight ROM and with the addition of CastagnaIT's kernel. I tried both with and without google apps (but I guess that doesn't matter at all, since that's userland stuff and I'm not seeing the kernel boot yet)
I put CM9 ivendor+CastagnaIT(extremeOC) back and everything is back to normal, but I'm wondering why CM10 is not booting; I think I've done it all correctly… using the new CWM 6.0.1.9 and all.
What could it be?
lap0 said:
Hi, I have an SGSplus (i9001) and I've been using arco68's and ivendor's ROMs for a few months now. Right now I'm using ivendor's latest RC9 plus CastagnaIT's ExtremeUV (without any OC, I'm using the standard 245-1401 MHz range) and it's fairly stable.
I always had some problems in real-time performance: it seems to me that when there is a process background the application in foreground becomes incredibly sluggish, maybe needing 10 seconds to input a single key… then, after a bit, the background process finishes his business and things go back to normal. Using BetterBatteryStats I have pinpointed a couple of bad application and removed them and now this happens rarely enough (but still happens). But this is not my question…
On Friday I decided to try ivendor's new CM10 alpha 5 and it simply doesn't boot: no "blue boy" loader at all.
I tried both the straight ROM and with the addition of CastagnaIT's kernel. I tried both with and without google apps (but I guess that doesn't matter at all, since that's userland stuff and I'm not seeing the kernel boot yet)
I put CM9 ivendor+CastagnaIT(extremeOC) back and everything is back to normal, but I'm wondering why CM10 is not booting; I think I've done it all correctly… using the new CWM 6.0.1.9 and all.
What could it be?
Click to expand...
Click to collapse
Dont call it blue boy his name is cid hm i flashed aokp jb in cwm 5 and all works fine try to flash cwm 5 via odin and try again because cwm 6 are buggy i think..
EDIT: first boot can take long time so be patient
Sent from my GT-I9001 using xda premium
Jonboy2011 said:
Dont call it blue boy his name is cid
Click to expand...
Click to collapse
Wops. :angel:
Jonboy2011 said:
try to flash cwm 5 via odin and try again because cwm 6 are buggy i think..
Click to expand...
Click to collapse
I tried with CWM 5.5.0.4 but it also doesn't work.
Doesn't hang on boot like it did with 6.0.1.9, but just resets back into CWM5 menu after a few seconds.
Oh, nice, it also resets back to CWM5 using the CM9 zip file which always worken with CWM6.0.1.2.
(I guess I'll use Odin to put CWM6 back and CM9 with that and be content with that)
lap0 said:
Wops. :angel:
I tried with CWM 5.5.0.4 but it also doesn't work.
Doesn't hang on boot like it did with 6.0.1.9, but just resets back into CWM5 menu after a few seconds.
Oh, nice, it also resets back to CWM5 using the CM9 zip file which always worken with CWM6.0.1.2.
(I guess I'll use Odin to put CWM6 back and CM9 with that and be content with that)
Click to expand...
Click to collapse
Hm have you try to flash aokp jb rom by crybert ? Full wipe flash full wipe and wait.. If this doesnt work your s plus is a transformer and at night a toaster sorry O-
EDIT : wait system.boots every time in.recovery without any butten pressed ?
Sent from my GT-I9001 using xda premium
Jonboy2011 said:
system.boots every time in.recovery without any butten pressed ?
Click to expand...
Click to collapse
Yep. That's what it did.
Now I've put CWM6.0.1.9 back with Odin and using that I managed to put ivendor CM9 RC5 back, so that I can put AOKP rom in the /sdcard and try it.
Whops. I guess that the changelog might explain what was happening.
2012-11-22: CM10 alpha4 [1] [2]
No changes only a working build, instead of the crappy alpha3 build
Click to expand...
Click to collapse
lap0 said:
Whops. I guess that the changelog might explain what was happening.
Click to expand...
Click to collapse
Whops oh sorry for the work with cwm :/
Sent from my GT-I9001 using xda premium
No problem.I wonder why CWM5504 didn't work for me, but oh well, newer ivendor CM10 RC5 just booted correctly, case solved!
today i flashed your 4.2.1beta to galaxy note n7000 i got some problems
my bluetooth is not even working its not starting
camera got hanged after clicking some photos and have to restart the phont
my bettry was 80% and after only 2 restarts my battery is only 15% i restarted phone because of camera got hanged and it happened in 1 hour its so bad and i have isue with my that my phone some times hang and dont responds so i have to restart it some times it happen >3 times in a day and some times it wont happen this happen with every rom i installed and i tried most of roms kindly give me some instruction to do something
please reply as soon as posible because ur rom is very nice and dont want to change it. thanks in advance...
its beta 1 so bugs are expected...
those are known bugs and maybe fixed in time, maybe on next build...
didnt have that battery issue though...
slimbean lover too
I know that its beta version but this thing are needed so and please can you tell me why my phone habg a lot it happens with every rom
Sent from my GT-N7000 using xda app-developers app
The BT bug is a known one, I'm not sure about the camera one and definitetly not the battery sucker one.
Boot into recovery and wipe data , cache & dalvik cahe.....
Flash ROM again and then see if the problem persists.
If it does, get Better Battery Stats (from the play store) and see if there are any battery draining apps/services running.
As for the speed problem, I've never run into it but a full-wipe should solve it ( full-wipe means wiping cache, dalvik cache and data )
Before flashing a rom read about it..
If want a ROM like Stock Jellybean I suggest you:
CaynogenMod10
OR
Paranoid Droid
If you want Galaxy Note's Official I suggest you
Ultimate_N7000_XXLSC_JBv5.1
OR
JB RocketROM
Yiannis75 said:
Before flashing a rom read about it..
If want a ROM like Stock Jellybean I suggest you:
CaynogenMod10
OR
Paranoid Droid
If you want Galaxy Note's Official I suggest you
Ultimate_N7000_XXLSC_JBv5.1
OR
JB RocketROM
Click to expand...
Click to collapse
Why on earth are you giving a list of ROMs ? :silly:
He's asking for help on a problem not a list of ROMs to flash ?
Are you in the right thread ?
@warfareonky u r rught i m not asking about rom i am in androind from 2 years and i have knowledge about toms and how to flash bro my problem is that my phn some time hangs some time while working and i have to restart it and thnxx all to reply
Sent from my GT-N7000 using xda app-developers app
warfareonly said:
Why on earth are you giving a list of ROMs ? :silly:
He's asking for help on a problem not a list of ROMs to flash ?
Are you in the right thread ?
Click to expand...
Click to collapse
I give a list of roms cause Slimbean Is beta and the problems will not be fixed until an Slimbean 4.2.1 v2]
Anyway he can take files from CM10 or Paranoid DROID ROM
Yiannis75 said:
I give a list of roms cause Slimbean Is beta and the problems will not be fixed until an Slimbean 4.2.1 v2]
Anyway he can take files from CM10 or Paranoid DROID ROM[/QUOT]
thnxx for the list bro.....:good:
but can you solve my other problem that my phone hangs sometimes and have to restart to put it normal and this things happens in every rom i tried mostly all rom but dont no why this things happens
Click to expand...
Click to collapse
Yiannis75 said:
I give a list of roms cause Slimbean Is beta and the problems will not be fixed until an Slimbean 4.2.1 v2]
Anyway he can take files from CM10 or Paranoid DROID ROM
Click to expand...
Click to collapse
thnxx for the list bro.....:good:
but can you solve my other problem that my phone hangs sometimes and have to restart to put it normal and this things happens in every rom i tried mostly all rom but dont no why this things happens
Hello xda
I know there quite a few posts out there with people detailing their phones rebooting randomly but my phone just hit a new level of weird.
My i9000 reboots randomly into cwm recovery menu for no good reason (I know there is another thread about this but that instance is on the Nexus S and the thread has basically died). This started occurring shortly after I flashed slim ROM 4.2.2 build 5 (came from CM10.1 nightlies). Flashing the rom again and updating it to build 6 has done nothing to alleviate the issue.
I'm using the Semaphore kernel with no OC or changed settings, and having recently bought a new battery, I'm really not sure where to start looking for the problem.
If anyone can give me some tips it'd be greatly appreciate, thanks in advance.
HellDiv3r said:
Hello xda
I know there quite a few posts out there with people detailing their phones rebooting randomly but my phone just hit a new level of weird.
My i9000 reboots randomly into cwm recovery menu for no good reason (I know there is another thread about this but that instance is on the Nexus S and the thread has basically died). This started occurring shortly after I flashed slim ROM 4.2.2 build 5 (came from CM10.1 nightlies). Flashing the rom again and updating it to build 6 has done nothing to alleviate the issue.
I'm using the Semaphore kernel with no OC or changed settings, and having recently bought a new battery, I'm really not sure where to start looking for the problem.
If anyone can give me some tips it'd be greatly appreciate, thanks in advance.
Click to expand...
Click to collapse
hi
randomly i will got this problem if i m flashing backward. like from 4.2.2 - 4.2.1, or 4.1.x to 4.0.x. or repeatedly changing between kernel (i always do this to modified ROM to suits my settings n need) its probably due to changing partition in system or kernel clash (even i did all wipe) in internalsd.
Sorry to say. it will come worst sometimes if u ignore da problem or keep flashing ROM to avoid it. 'Luckily' about 2 hour ago my sgs just did. Constantly booting to recovery n its juz bootloop between kernel splashscreen n sgs white splashscreen after it.3 combo button will not working for recovery n only download mode accessible.
no more method for me . Juz flashing back to stock firmware JVU +CF-ROOT with odin was da answers
but if u dont familiar with odin.seek guide here
http://forum.xda-developers.com/showthread.php?t=2149455
but use it as ur last method!
clashing between titan.....no! kernel maybe da reason.do some wiping before changing kernel or ROM. n format system if necessary before flashing!
Sent from my GT-I9000 using xda app-developers app
---------- Post added at 04:45 AM ---------- Previous post was at 04:37 AM ----------
Now i m stick with GB Saurom for a while. really tired unbricking my fone as after my sgs softbrick,my pc went crazy :what: n i m stuck with repairing my pc first. then flash my ol lil i9000
Sent from my GT-I9000 using xda app-developers app
Reboots into CMW with Slim Bean 4.3 and Semaphore
Hi guys, any news on the subject? Exactly the same thing happening to me. I did a clean installation of Slim 4.3, after using CM10 and everything seems to be working perfectly except it reboots into CWM every 1-2h!!! I haven't changed any configuration and didn't mess with the kernel that came with the ROM, which is Semaphore... Is it a kernel issue? Should I try to flash the latest version?
HellDiv3r said:
Hello xda
I know there quite a few posts out there with people detailing their phones rebooting randomly but my phone just hit a new level of weird.
My i9000 reboots randomly into cwm recovery menu for no good reason (I know there is another thread about this but that instance is on the Nexus S and the thread has basically died). This started occurring shortly after I flashed slim ROM 4.2.2 build 5 (came from CM10.1 nightlies). Flashing the rom again and updating it to build 6 has done nothing to alleviate the issue.
I'm using the Semaphore kernel with no OC or changed settings, and having recently bought a new battery, I'm really not sure where to start looking for the problem.
If anyone can give me some tips it'd be greatly appreciate, thanks in advance.
Click to expand...
Click to collapse
I run into the same problem with my current update of my I9000 to CM 10.2.1 and the Semaphore Kernel 3.3.0 (JB).
Any ideas on this issue from the pros?
I realized that it was happening to me only when I was loosing the network coverage, like being in the underground or roaming or things like that... I don't know if it happens to everyone but in my case it's definitely this. If there is no network available my phone will boot into recovery after a while. If the signal is OK, it doesn't happen. Maybe it has something to do with the modem?!
mar0ni said:
I run into the same problem with my current update of my I9000 to CM 10.2.1 and the Semaphore Kernel 3.3.0 (JB).
Any ideas on this issue from the pros?
Click to expand...
Click to collapse
mlw_es said:
Hi guys, any news on the subject? Exactly the same thing happening to me. I did a clean installation of Slim 4.3, after using CM10 and everything seems to be working perfectly except it reboots into CWM every 1-2h!!! I haven't changed any configuration and didn't mess with the kernel that came with the ROM, which is Semaphore... Is it a kernel issue? Should I try to flash the latest version?
Click to expand...
Click to collapse
mar0ni said:
I run into the same problem with my current update of my I9000 to CM 10.2.1 and the Semaphore Kernel 3.3.0 (JB).
Any ideas on this issue from the pros?
Click to expand...
Click to collapse
mlw_es said:
I realized that it was happening to me only when I was loosing the network coverage, like being in the underground or roaming or things like that... I don't know if it happens to everyone but in my case it's definitely this. If there is no network available my phone will boot into recovery after a while. If the signal is OK, it doesn't happen. Maybe it has something to do with the modem?!
Click to expand...
Click to collapse
Deactivate Deepidle in Semaphore manager app and these reboots should be gone.
Did the trick for me.
hertzschi said:
Deactivate Deepidle in Semaphore manager app and these reboots should be gone.
Did the trick for me.
Click to expand...
Click to collapse
Yes, I did this and so far no reboots anymore.
When I install a custom ROM like cyanogen and AOKP I have a problem with the two capacitive buttons, they do not light at all. They are dead.. Any solution to this?
Now I use maclaw's AOKP 4.2.2
Thanks in advance!
Antialize said:
When I install a custom ROM like cyanogen and AOKP I have a problem with the two capacitive buttons, they do not light at all. They are dead.. Any solution to this?
Now I use maclaw's AOKP 4.2.2
Thanks in advance!
Click to expand...
Click to collapse
Try rebooting or wait awhile
AssToast said:
Try rebooting or wait awhile
Click to expand...
Click to collapse
I have the same problem. I try to clear chace and dalvik, reboot and waiting all day but the capacitive buttton still dead. is there another way to solve this problem?
Sorry my english, still learning
it happened to me i thought it's a CWM bug, it's just a Samsung bug, reboot using the power button and it will make alright to work!
enensales said:
it happened to me i thought it's a CWM bug, it's just a Samsung bug, reboot using the power button and it will make alright to work!
Click to expand...
Click to collapse
I rebooted a lot of times and waited and couple of minutes.. now i am back to stock
i will test the latest updates of AOKP or CM and we will see!!
Nothing happend again with the new update!!!
Maclaw Some HELP pls!!
I flash with TWRP and I have option on the stock for the buttons to stay only some secs on!!
Any SOLUTION HELP!
Also i cant restore only my data!! The phone is stuck in the cyanogen logo for a lot of time!!!
HELP I WANT A CUSTOM ROM!
Antialize said:
Nothing happend again with the new update!!!
Maclaw Some HELP pls!!
I flash with TWRP and I have option on the stock for the buttons to stay only some secs on!!
Any SOLUTION HELP!
Also i cant restore only my data!! The phone is stuck in the cyanogen logo for a lot of time!!!
HELP I WANT A CUSTOM ROM!
Click to expand...
Click to collapse
Me too. I think it was bug on our phone. :crying:
Wrong Thread
anyone managed menu and back buttons to work on CM ?
Ok, let's deal with it.
I need your:
- model (i8190/n/l)
- country
- baseband
Maybe we can figure on which phones problem exists and then eliminate them.
New Macław said:
Ok, let's deal with it.
I need your:
- model (i8190/n/l)
- country
- baseband
Maybe we can figure on which phones problem exists and then eliminate them.
Click to expand...
Click to collapse
i8190
GR
I8190XXAMD3
also tried over I8190XXAMG4_I8190OXXAMH1
I have the same codes
I8190
Gr
Amd3
New Macław said:
Ok, let's deal with it.
I need your:
- model (i8190/n/l)
- country
- baseband
Maybe we can figure on which phones problem exists and then eliminate them.
Click to expand...
Click to collapse
- model: i8190
- country: XSE - Indonesia
- baseband: I8190DXAMA2 (I have tried I8190DXAMA3 & I8190DXAMB1)
would be great if you fix our problem. Thanks Maclaw Team
irufun said:
- model: i8190
- country: XSE - Indonesia
- baseband: I8190DXAMA2 (I have tried I8190DXAMA3 & I8190DXAMB1)
would be great if you fix our problem. Thanks Maclaw Team
Click to expand...
Click to collapse
I HAVE THE SAME ERROR
i8190
tHX from germany
Try the newest cm 10.1 from maclaw. In the settings you can turn on the 'backlight' : homescreen>>press menu button>> system settings>> advanced settings >> make sure the option to disable it is turned OFF.
I'm sorry if it's not relevant.
Sent from my GT-I8190 using xda app-developers app.
this option is grayedout (unavailable). I bet is bug in custom recoveries (cwm and twrp) - because bug exist even if flash only recovery, (odin or from rom manager), without flashing any new rom. But on stock rom bug disappeard after some minutes.
my model is 8190N, poland.
Please Dev's, find solution for us.
danielsinnema said:
Try the newest cm 10.1 from maclaw. In the settings you can turn on the 'backlight' : homescreen>>press menu button>> system settings>> advanced settings >> make sure the option to disable it is turned OFF.
I'm sorry if it's not relevant.
Sent from my GT-I8190 using xda app-developers app.
Click to expand...
Click to collapse
that's for backlight, not for capacitive button. I have tried
same error
- model I8190L
- country BRAZIL
- baseband I8190LUBAMB1
thanks!
-model i8190
-GR
- 4.1.2 xxamg4 but have tried any other stock firmware. soft keys just wont work on a custom rom...
we will never be alone
Q&A for [ROM][LBL] CyanogenMod 11 weeklies
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
D.Sirakov said:
LOL best rom !! amazing performance and good multitasking with williams kernel v7 and pure performance x zeno edition...The best rom!!!
Sent from my Xperia SP using XDA Free mobile app
Click to expand...
Click to collapse
Is it actually possible to use Williams Kernel on LBL...?
zielonypasternak said:
Is it actually possible to use Williams Kernel on LBL...?
Click to expand...
Click to collapse
My BL is unlocked....
Sent from my Xperia SP using XDA Free mobile app
zielonypasternak said:
Is it actually possible to use Williams Kernel on LBL...?
Click to expand...
Click to collapse
No it is not made for locked bootloaders
build7 always brick my phone
hi
i'm trying to install build 7.
My phone has locked bootloader. Installed version is #build6.
I have used philz recovery to flash build 7. To flash #build7 takes 2 minutes long.
After flashing, i reboot the phone using reset recovery option of philz.
Phone gets stuck, black screen, without sony logo, and i have to reflash to .207 stock rom using flashtool.
What am i doing wrong?
thanks in advance.
D.Sirakov said:
My BL is unlocked....
Sent from my Xperia SP using XDA Free mobile app
Click to expand...
Click to collapse
TechnoSparks said:
No it is not made for locked bootloaders
Click to expand...
Click to collapse
Right. Got me confused there, as I was already pretty sure kernels are just for UBL. Why use the LBL version of CM11 on UBL then?
---------- Post added at 09:31 PM ---------- Previous post was at 09:24 PM ----------
jmmartinbravo said:
hi
i'm trying to install build 7.
My phone has locked bootloader. Installed version is #build6.
I have used philz recovery to flash build 7. To flash #build7 takes 2 minutes long.
After flashing, i reboot the phone using reset recovery option of philz.
Phone gets stuck, black screen, without sony logo, and i have to reflash to .207 stock rom using flashtool.
What am i doing wrong?
thanks in advance.
Click to expand...
Click to collapse
I guess it just happens sometimes. When I first flashed build #6 with twrp, everything went well, but something must have got corrupted along the way as the phone was stuck on Sony logo, and the screen just went gradually from orange tint to black from there on with continuous reboot loop. Fresh install helped though. And I've done everything the same.
Go back to stock,root, install recoveries, wipe cache, dalvik and system and install build #7. Should work just fine.
P. S. Another question from me, maybe not entirely related to only this ROM, but to flashing ROMs while using link2SD in general, as I'm sure some of you guys are using it. Is there any way to avoid some apps getting totally borked after each update? I know you need to recreate the mount scripts after flashing, but it just doesn't work for select apps each time, and I have to go through a tedious process of unlinking each one that is screwed, rebooting, and relinking. It's getting annoying with weekly updates (Thumbs up MRSteve <3).
MrSteve555 said:
(...)So, let's enjoy the lucky 7
Click to expand...
Click to collapse
Not sure if it's an issue with the nightly build you were working with this time, or something's actually wrong with build #7, but I don't seem to be able to install any CM Theme. Each and every one of them seems to install just fine, only to spit out "Failed to install <appname>" notification after a minute.
Anyone having this problem aswell?
zielonypasternak said:
Right. Got me confused there, as I was already pretty sure kernels are just for UBL. Why use the LBL version of CM11 on UBL then?
Click to expand...
Click to collapse
Well maybe he loves weeklies better than the normal daily nightlies.
This ROM or CM11 Official ?
Wich is better ? Keep my bootloader locked and use that ROM or unlock my bootloader and flash the latest CM11 Official Snapshot (M11) ? Few months, i flashed CM11 for locked bootloader and I had lot of anoying bugs/freezes. Can I expect better with that ROM ?
Thank's and sorry for my bad english.
This ROM is completely stable, and has no apparent bugs whatsoever. The only thing I noticed is worse than stock is the battery life.
Sent from my Xperia SP
zielonypasternak said:
This ROM is completely stable, and has no apparent bugs whatsoever. The only thing I noticed is worse than stock is the battery life.
Sent from my Xperia SP
Click to expand...
Click to collapse
- How long does the battery ? 1 day with a good use (Youtube, gaming etc) or less ?
- So that ROM is better or egal to CM11 Official ?
Thank's.
@MrSteve555
You use linaro optimization in your build?
win32r said:
@MrSteve555
You use linaro optimization in your build?
Click to expand...
Click to collapse
Nope, I only use 4.7 Google Toolchain. I thought about building with Linaro, but it just doesn't seem to be worth it(I have a life, you know, and buildijng with Linaro + O3 can take a long time )
MrSteve555 said:
Nope, I only use 4.7 Google Toolchain. I thought about building with Linaro, but it just doesn't seem to be worth it(I have a life, you know, and buildijng with Linaro + O3 can take a long time )
Click to expand...
Click to collapse
Okay. But I think using -o3 optimization ROM will be very fast
Help help help help, is my xperia sp dead?
Please i need imediate help!
I had this buid for a month and it worked flawlesly, but today i got an idea to install cm11 m11 update that was constantly bothering me in notifications center. I downloaded it and flashed it with recovery but then a stop. My screen wont turn on and there is no boot animation. When i hold power button i only get a slight vibration and then nothing, just black screen. I tried pushing that small orange button with pencil but nothing happens. Only my green led indicator shows up when the phone is plugged in wall and i hold volume down button. Please help, what should i do as my xperia sp is indespensable for me because i live in dormitory 200 kilometers from my home town. Please
brx1997 said:
Please i need imediate help!
I had this buid for a month and it worked flawlesly, but today i got an idea to install cm11 m11 update that was constantly bothering me in notifications center. I downloaded it and flashed it with recovery but then a stop. My screen wont turn on and there is no boot animation. When i hold power button i only get a slight vibration and then nothing, just black screen. I tried pushing that small orange button with pencil but nothing happens. Only my green led indicator shows up when the phone is plugged in wall and i hold volume down button. Please help, what should i do as my xperia sp is indespensable for me because i live in dormitory 200 kilometers from my home town. Please
Click to expand...
Click to collapse
Why on earth did you do that!? You'll need a computer with you. You will sadly however, have to start from the beginning. Get a stock ROM .ftf, flash it via Flashtool, then start over (root, install CWM, flash CM11 weekly build by MrSteve555)
The reason why your phone is bricked is because you have flashed a ROM for unlocked bootloaders (this being said is the M11 that you updated your phone). Your device does not have an unlocked bootloader. It does not start up due to the kernel installed on your phone is not stock (cyanogenmod's official kernel of course). On locked bootloaders, using a custom kernel is impossible and will cause bricks.
TheG0ldKiller said:
- How long does the battery ? 1 day with a good use (Youtube, gaming etc) or less ?
- So that ROM is better or egal to CM11 Official ?
Thank's.
Click to expand...
Click to collapse
I haven't used Official CM11 on my SP, as my bootloader is locked, so it's not me to ask. For me, the phones eats through battery really fast, with screen on, it's like 10 minutes for 1%. Definetely not a days worth of use when gaming.
Still not able to install themes in build 8
Sent from my Xperia SP
Добрый День!
Greetings to all! I do not know very well angliyskiy.V especially want to thank the developer to update the firmware! Can you make a as here
http://forum.xda-developers.com/xperia-sp/development/kk-nexus-pc-t2835662
in black upper-menu lets you change the transparency and shove Image (any) instead of black. And you can integrate SONY music (application) as well as on the katabatic to Megala lamp with repro
Thank you very much! Waiting 9))
Is there any kernel has inbuilt recovery for locked bootloader
Sent from my C5303 using XDA Premium 4 mobile app