Hi, I have rooted using Doomlord's method. But I have problems waking the note up from sleep. Upon pressing home/power button, the black screen displays random red/blue/green/white pixels appearing slowly until the entire screen is filled like in milkyway. I have to try repeatedly to get back to my widget locker screen. Anyone can help? Thank you.
I have never heard of your problem before, but it sounds like a cool effect.
Sent from my superior GT-N7000 using Tapatalk
Zamboney said:
I have never heard of your problem before, but it sounds like a cool effect.
Sent from my superior GT-N7000 using Tapatalk
Click to expand...
Click to collapse
Yeah it looks pretty cool. like the milky way. Haha I think it's just a problem with the set's display. I'm fine when on stock firmware and kernel. When I tried flashing franco kernel the problem recurred. Found a guy on franco.kernel's thread with the same issue.
iamastone said:
Yeah it looks pretty cool. like the milky way. Haha I think it's just a problem with the set's display. I'm fine when on stock firmware and kernel. When I tried flashing franco kernel the problem recurred. Found a guy on franco.kernel's thread with the same issue.
Click to expand...
Click to collapse
Did you recently buy your SGN? I remember reading somewhere that it is due to the newer notes' kernel sources. I get the same issues too. So atm, I just stick with a rooted CF kernel.
coolfire said:
Did you recently buy your SGN? I remember reading somewhere that it is due to the newer notes' kernel sources. I get the same issues too. So atm, I just stick with a rooted CF kernel.
Click to expand...
Click to collapse
Yes it's only a couple of weeks old someone with similar issues has rocket rom v22 and has no issues, so maybe you'd wanna try also.
Hi Guys,
mine is a few days old and has the exactly same problem with all not stock kernels. So do you think there will be a fix for this?
greets
phasA
phasA said:
Hi Guys,
mine is a few days old and has the exactly same problem with all not stock kernels. So do you think there will be a fix for this?
greets
phasA
Click to expand...
Click to collapse
I really have no idea man. I hope there'd be a fix. I tried flashing rocket rom v22 and got bootloop. Not sure if i did it wrong or if it's the new kernel causing the problem reverted back to stock.
iamastone said:
I really have no idea man. I hope there'd be a fix. I tried flashing rocket rom v22 and got bootloop. Not sure if i did it wrong or if it's the new kernel causing the problem reverted back to stock.
Click to expand...
Click to collapse
Hey, I have the same problem and after my research, our note from SG which I believe you recently bought too needs to use kernel 2.3.6.14 above. So suppose your rom is fitted with say a Franco kernel, what you can do is:
1. Flash the rom, then after which reboot and make sure it loads fine. Access back to recovery with VOL UP + MENU + POWER, flash a new kernel.
2. replace the kernel in the .zip of the rom and then flash it as normal.
Scared the **** out of me too, I thought I bricked my phone
Kernel related 100%
Hello,
I have actually a samsung galaxy s i9000 device, running on CM 10.1
After a reboot, the screen turns pink.
Ive flashed and changed roms, formatted, cleaned partitions, did just about anything and it only works with stock rom and no with custom roms
I think there is no problem with the LCD at all
Thank you for your feedbacks / your help !
Can you give us a screenshot pls when display is pink than post it here again.
Sent from my GT-I9000 using xda premium
DerRomtester said:
Can you give us a screenshot pls when display is pink than post it here again.
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
There doesn't seem any problem at all
What do you think?
flish3069 said:
Hello,
I have actually a samsung galaxy s i9000 device, running on CM 10.1
After a reboot, the screen turns pink.
Ive flashed and changed roms, formatted, cleaned partitions, did just about anything and it only works with stock rom and no with custom roms
I think there is no problem with the LCD at all
Thank you for your feedbacks / your help !
Click to expand...
Click to collapse
Settings > Advenced > Color tunning
Sent from my GT-I9000 using xda app-developers app
burakgon said:
Settings > Advenced > Color tunning
Sent from my GT-I9000 using xda app-developers app
Click to expand...
Click to collapse
All default
flish3069 said:
All default
Click to expand...
Click to collapse
Did you try playing with the GPU rendering?
Settings - Developer options - Force GPU rendering (actually all options under Drawing can cause problems if they are not set properly.
Do you use any specific kernel or you always stay with stock one? Have you tried SlimBean ROM?
edit: after checking pics again, I see that you have glitches even in recovery :blink: I would say it could be a HW problem, broken cable or something like that. Flashing custom roms and the broking of cable at the same time can be a serious coincidence (or have you tried going back to stock 2.3.6?)
aToS88 said:
Did you try playing with the GPU rendering?
Settings - Developer options - Force GPU rendering (actually all options under Drawing can cause problems if they are not set properly.
Do you use any specific kernel or you always stay with stock one? Have you tried SlimBean ROM?
edit: after checking pics again, I see that you have glitches even in recovery :blink: I would say it could be a HW problem, broken cable or something like that. Flashing custom roms and the broking of cable at the same time can be a serious coincidence (or have you tried going back to stock 2.3.6?)
Click to expand...
Click to collapse
Stock 2.3.6 works fine so I think there is no problem with the LCD at all.
Cyanogenmod with ClockworkMod kernel turns the screen pink, but then I flash stock rom 2.3.6 with stock kernel and everything is fine.
I've tried flashing other roms like MIUI with Kernel Mackay CMC and it turns the screen pink as well.
Something in the custom kernels is not working on my device.
aToS88 said:
Have you tried SlimBean ROM?
Click to expand...
Click to collapse
I've just flashed SlimBean rom with Semaphore kernel and it turns the screen pink as well
Yes my galaxy s is same to you
I try many custom rom but after 2 or 3 days my lcd was yellow but not pink
What am i do??
Galaxy s i9000
Dude also the same problem with the pink screen plz anyone help we turned back to 2.3.5 but it too slow software.....
Plzzzzzzzzz anyone give us an explanation why this was happened????any solution.....
Hello,
I flashed yesterday;s CM11 and everything is working perfectly fine but I am unable to take screenshots. I tried using some free apps as well and noticed it just takes a black screen image. Anyone have any ideas? or should I jus flash the new nightly? Kid of want to stay away from reflashing since I have to set everything up again.
Thanks
tozacchi said:
Hello,
I flashed yesterday;s CM11 and everything is working perfectly fine but I am unable to take screenshots. I tried using some free apps as well and noticed it just takes a black screen image. Anyone have any ideas? or should I jus flash the new nightly? Kid of want to stay away from reflashing since I have to set everything up again.
Thanks
Click to expand...
Click to collapse
I think CM 11 is still in nightly. So there might be some missing features and bugs. Try waiting for stable version to be released
Hi,
I flashed with CWM the stable Slimkat (Slim-galaxysmtd-4.4.2.build.3-OFFICIAL-3067) and I have to major problems:
- keyboard is not showing up. When it is supposed to pop-up. It doesn't.
- the 'back" button is not working at all. when I press it, the phone vibrates (it got the signal) but it doesn't proccess it.
I didn't have these problems with Slim-galaxysmtd-4.4.2.build.2.8.RC3-WEEKLY-2884.
Any ideas?
Thanx,
Sp
papage said:
Hi,
I flashed with CWM the stable Slimkat (Slim-galaxysmtd-4.4.2.build.3-OFFICIAL-3067) and I have to major problems:
- keyboard is not showing up. When it is supposed to pop-up. It doesn't.
- the 'back" button is not working at all. when I press it, the phone vibrates (it got the signal) but it doesn't proccess it.
I didn't have these problems with Slim-galaxysmtd-4.4.2.build.2.8.RC3-WEEKLY-2884.
Any ideas?
Thanx,
Sp
Click to expand...
Click to collapse
the same problem happened to me for the second time in 2 months, this is mind boggling, Nexus 10 stock 4.4.2
keyboard (stock and all other keyboards) stop working + back button also stops working out of the fkin blue..
I can't for the life of me understand what could cause this.. so f***in frustrating.. only a hard reset fixes this BS.
anyone has any info on this ?
This is due to flashing other gapps rather than the gapps provided by slimbean team. You just need to reflash the ROM with their gapps pack.
Sent from my GT-I9000 using xda app-developers app
leecorp said:
This is due to flashing other gapps rather than the gapps provided by slimbean team. You just need to reflash the ROM with their gapps pack.
Click to expand...
Click to collapse
:good:
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