What about blackscreen bug??? Rome kernel used to have it on N2....
Yesterday I tried with this kernel on #24 and got blackscreen bug. I could not do anything and finally had to remove the battery, goto recovery and do a clean flash
What about blackscreen bug??? Rome kernel used to have it on N2....
@amit. ..switch off phone! Then power on and immediately try volume up+home!
Sent from my LG-P500 using Tapatalk
bro not working still stuck ???? i m fade up with these neither enter in recovery nor in fastboot mode ! what the hell is this ?
I can't guarantee, but my final shot (after trying all kinds of solutions and failing) would be boot on emergency mode, flash a stock ROM through KDZ and boot up the first time wiping data (using the well known keys combination instead of just turning on the first time with the old data).
Then you would have to redo all you want (recovery, rom, etc).
Again, I don't guarantee its success.
P.S.: The emergency mode doesn't pass through the LG logo, so I guess you can enter that mode with no problem.
Got a link for the kernel?I have installed the latest 24th Nightly and this is what I would like to share. Instead of the default kernel, install zacks Rome and see the amazing leap in performance! I am getting 74.9fps in Neocore! Never before on any ROM/kernel combo have I got this score! Quadrant scores are also great!
Hi, can you tell me about any bugs with this ROM and Rome kernel?
Does camera work without rotation bug? How about random reboots?
What about blackscreen bug??? Rome kernel used to have it on N2....
Have been on the ROME kernel since yesterday.
1) No black screen bug yet (Have turned off screen on/off animations as I think these are stupid and do not affect the functionality of my phone in any way)
2) Yes camera works without any rotation bug...I am using Lg Camera and not CM stock one.
3) NO random reboots...not even once...
Phone is fully bug free till this moment....
Here is the Zacks ROME page...
http://www.androidworld.it/forum/mo...-gingerbread-phoenix-|-v1-3-3-|-14-nov-30042/
now i got emergency Mode some how so is there any way to get back my mobile normal or i will get CMW RECOVERY ? bcoz i don't want to lose my data unfotruna i don't have backup of it unfortunately
Have been on the ROME kernel since yesterday.
1) No black screen bug yet (Have turned off screen on/off animations as I think these are stupid and do not affect the functionality of my phone in any way)
2) Yes camera works without any rotation bug...I am using Lg Camera and not CM stock one.
3) NO random reboots...not even once...
Phone is fully bug free till this moment....
Here is the Zacks ROME page...
http://www.androidworld.it/forum/modding-e-firmware-lg-optimus-one-114/%5Bkernel%5D-rome-kernel-2-6-35-14-cm7-6-6-x-gingerbread-phoenix-%7C-v1-3-3-%7C-14-nov-30042/
Yoy should already have CWM if you flashed the rom. Just press Home key + Volume Down + Power until the lg logo disappears.
Sent from my LG-P500 using XDA App
How's battery life? People reported drains especially with wifi!
Sent from my LG-P500 using Tapatalk
Can u give me an alternative link to that kernel?????,cuz the link u provided is not workin at this moment......... thanks
Dude i m on new baseband and i try all key combination but nothing is happening i just only getting emergency mode when i press back key + home + power..now what should i do next ?
Dude i m on new baseband and i try all key combination but nothing is happening i just only getting emergency mode when i press back key + home + power..now what should i do next ?
night·ly /ˈnaɪtli/
adj.
- Of or pertaining to the night, or to every night; happening or done by night, or every night.
- A Fresh CyanogenMod ROM automatically built with the newest available code, usually compiled at night. Often contains many bugs.
I noticed its difficult to get the pop-up menu when I hold the power button down.
I'm getting an error when trying to turn wi-fi on after flashing the testing kernel and the last nightly.
With screen on animation there are white noise before animation and when receive a call, need some time before i can answer.
Ok. As you know, init is the first process after kernel started. Init parse /init.rc and /init.[device_name].rc and execute early-init action in it. Ueventd is one of the very first services started by the default init.rc. It proceeds to read its main configuration files, /ueventd.rc and /ueventd.[device_name].rc, replays all kernel uevents (i.e. hotplug events), and then proceeds on to wait, listening for all future uevents. Kernel uevents are delivered to ueventd through a netlink socket, a common way for certain kernel functionality to communicate with user-space tools and daemons. [device_name] we get from "androidboot.hardware" kernel commad line - in our case it "thunderg" (look BoardConfig.mk). In early builds we got file /uevent.thunder.rc , after typo fix we have /uevent.thunderg.rc and have problem with /dev permissions - ril, sensor, gpu not work. Download latest nightly, flash, then apply patch in attachment - and manual network selection was work :fingers-crossed: