Develop Bugs

[Q] Lock Screen wont come on< on any rom please help

Hi,
I have the T989 version, although i love my phone it seems that ever since ive started to use different roms my lock screen wont turn on, i cant get it to swipe, pattern, face unlock or anything. Its either screen on or off. Is this normal? Whenever i even restored my original gingerbread rom it still doesnt work.
One more thing, when you hold the power button it usually gives you an option to put it on silent or vibrate or plane mode, well when i press power and hold it it just turns off. What is really going on guy, any help would be great thanx!

Try using this first then reflashing
http://forum.xda-developers.com/showthread.php?p=17067
This will delete all your data and give you a clean base to do an install. Backup first with whatever backup utility you want.
Sent from the Darkside, ICS style

http://forum.xda-developers.com/showthread.php?t=1611796
That thread contains the fix. Worked perfectly for me.
Sent from my SGH-T989 using XDA

EFS Corrupted.

i went ahead and did a darkside superwipe, and that did not fix it, afterwards unrooted my phone and got it back to stock 2.3.6 gingerbread, i figured after that it should have been fixed, however still no lock screen and power button turns phone completly off, no airplane, vibrate or silent options! It really sucks i dont know what i did wrong!

okay well that thread seems to have the solution, well i just copletely unrooted my phone and gone stock, now i have to go and root again, the only reason i went and unrooted it to stock rom is that Kies wouldt recognize the device for the official ICS update, so ill get the official update and root it, i hope rooting the phone for ics is the same method for rooting it on gingerbread, thanx

Questions go in the Q&A section

Most of the problems with our devices are caused because of the Karnels that the developers put for this device (it's not like I'm not appreciative) but there is so much people having trouble because of that, so yea we need our own karnel but the ICS is coming tonight so I guess we would be fine from now on

[Q] Note II dying, Please help!

Hey guys.
This has only started to happen since I installed a rom that seemed to come with twrp and has removed my cwm..
My phone now seems to be very laggy when scrolling, even the notification noise lags and when it goes to into standby nothing happens it just goes off and the only way I can use the phone again is by taking the battery out.
I've tried flashing a new rom but thats not making a difference and i'm at a loss at what to do now....
Thanks for reading and any advice is appreciated.
*Forgot to mention, when being attached to pc via usb its not being recognised as being there, doesn't show as attached, just does nothing*

mrkupochan said:
Hey guys.
This has only started to happen since I installed a rom that seemed to come with twrp and has removed my cwm..
My phone now seems to be very laggy when scrolling, even the notification noise lags and when it goes to into standby nothing happens it just goes off and the only way I can use the phone again is by taking the battery out.
I've tried flashing a new rom but thats not making a difference and i'm at a loss at what to do now....
Thanks for reading and any advice is appreciated.
*Forgot to mention, when being attached to pc via usb its not being recognised as being there, doesn't show as attached, just does nothing*
Click to expand...
Click to collapse
Could you please specify what Rom and version that you flashed?
Sent from the rabbit hole.

Did you install one of the other custom recoveries manually yet? Btw. IMHO TWRP is the best anyways. Did you do a full wipe before installing new ROM? what kernel/version are you on?

I went from using the Android revolution HD 10.0 version with stock kernel, I changed to AllianceROM N7100 XXDMA6 JB V1.0 but didn't find it smooth enough so I swapped back to Revolution, thats when I found twrp had installed.
I've tried flashing the stock recovery and i'm still getting the same issue.
I've since reflashed cwm but this hasn't solved the problem unfortunatley.....No idea what to do

You should at least wipe cache/dalvik, or even after doing a backup with TB, a fullwipe.

Martux76 said:
You should at least wipe cache/dalvik, or even after doing a backup with TB, a fullwipe.
Click to expand...
Click to collapse
All done, several times, no difference

Have you considered it could be sudden death syndrome?
You should have nothing to worry about in terms of it dying, since you have a very recent base rom (dma6), which include safeguards against it.
When it freezes, have you tried waiting to see if the phone responds after you press the Home Button?
I ask this because I've read reports of people waiting for over 20 minutes for the phone to become responsive again after pressing the home button when in standby.
Another thing: have you ever flashed a full stock rom after DLL7 (including DMA6)? I ask this because DLL7 and later include a new bootloader that *supposedly* helps address the sudden death issue. It doesn't hurt to try anyway.
Sent from my GT-N7100

If ur pc recognises ur phone in download mode seaech the forum for rescue firmware (it comes with pit file) and flash it with odin..u should be sorted then.
Sent from my GT-N7100 using Tapatalk 2

[Q&A] [ROM][4.4.4/KTU84P][OMNIROM][LINARO/OPTIMIZED] FML: Fork My Life (10/08/2014)

[Q&A] [ROM][4.4.4/KTU84P][OMNIROM][LINARO/OPTIMIZED] FML: Fork My Life (10/08/2014)
Q&A for [ROM][4.4.4/KTU84P][OMNIROM][LINARO/OPTIMIZED] FML: Fork My Life (10/08/2014)
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:

kbfirebreather said:
Anyone having problems with torch on the beta build? Not turning on LED for me, and keeps force closing.
Click to expand...
Click to collapse
I'm having issues with it as well. Sometimes it sits there thinking it works, other times it waits a few seconds and then crashes. It worked for a day...not sure what I did past that to break it.

Is there anyway to overclock the latest update? I know I can't install a new kernel with this ROM.
Also, any option for Volume Rocker unlock? I'm new to this ROM, coming from CM. I kinda rely on that option, since my power button is kinda on the fritz.

Fml 4.4.4 beta
I love this rom but my after clean flashing it the gallery and the camera will not show
Pictures. Is there anything I can do to fix it so I can get camera and gallery to work?

vicious01 said:
I love this rom but my after clean flashing it the gallery and the camera will not show
Pictures. Is there anything I can do to fix it so I can get camera and gallery to work?
Click to expand...
Click to collapse
Which gapps package are you using? I'm using the modular mini. Try another clean flash (sorry) and use a different package than you are now.

aaa
nothing

I've tried a lot of KitKat ROMs, but each one with a lot of issues. So I came back to the 4.3, it surprised me for his stability (1 year with bugged ROM make you feel that your phone sucks more than it actually does [no, it doesn't, I love it!]) and I decided to don't try your FML. Now I can't wait for Lollipop, and even if I haven't tried your ROM, I trust in it and I think it will be the best choice. Good work and thanks!

Could some1 possibly upload a video of this good work ? Got a maguro and I'm very curious
thx in advance!

Samsung Galaxy Nexus FML Lollipop
Hello. I hope this is the right place to post this. I have less than 10 posts so I have to post here...
I've tried to install your FML rom (the lollipop beta) on my Samsung Galaxy Nexus, but I seem to be having the same issue that coleburns is having. Namely, I flashed the rom from recovery, but when I reboot the phone, it shows the Google splash screen and then keep rebooting over and over again.
I understand that the first boot is supposed to take some time, but I've left it for over an hour and it still won't boot into the OS. Is there a step I'm missing?
I'm using the custom version of TWRP that you linked to in the first post. I also formatted all the partitions to ext4. Before flashing the rom, I performed the factory reset from recovery and also cleared the /system folder.
I've managed to load on the KitKat version of your ROM just fine...I can't work out what I'm doing wrong!
Anyway, if you need some logs or something to help debug the issue, let me know. Or, if I'm doing something wrong, could you please let me know? I'm very keen to try Lollipop!
Thanks.

Could some1 possibly upload a video of this good work ? Got a maguro and I'm very curious
thx in advance!

lollipop build 2
Haven't seen anybody ask... In your changelog for lollipop you said the rom takes a VERY LENGTHY FLASH TIME. Are we looking at 5 minutes or more?
edit: VERY LONG... over 5 minutes for me

This is the best rom ever!
When you said, "These builds are very early! They aren't daily-driver-stable, but they are progressing extremely fast." I was expecting junk, then I tried it. I was a big fan of your kit kat rom as well but once I tried this android l rom I fell in love. I have used this all day and it is extremly stable. The only bug I have to report that isnt even a need is the app drawer is the app drawer animation is very laggy. I tried enableing 2d gpu acceleration just in case that had something to do with it but it still didnt help. Any suggestions would be great. Oh and yes I have tried closing other apps, multitasking is no issue with this rom, the memory management is great. I thank you so much for such a great rom, keep up the amazing work.

Installing TWRP Problem
So I am currently on CWM and am trying to switch over to TWRP. I'm have a slight problem. When I install TWRP (via twrp manager app), I am also using the recommended custom twrp from the first post. It installs successfully, then I go into reboot options and reboot into recovery...and it's still CWM. I've tried it multiple times. I am rooted, I do have busybox installed, I can't figure out what the problem is. IM STUCK WITH CWM, HALP!

Mondos said:
So I am currently on CWM and am trying to switch over to TWRP. I'm have a slight problem. When I install TWRP (via twrp manager app), I am also using the recommended custom twrp from the first post. It installs successfully, then I go into reboot options and reboot into recovery...and it's still CWM. I've tried it multiple times. I am rooted, I do have busybox installed, I can't figure out what the problem is. IM STUCK WITH CWM, HALP!
Click to expand...
Click to collapse
Download the file in the OP for FML (twrp 2.7.1). Flash with Flashify. Reboot to recovery.

Don't worry too much about it not working. It's fully working for me but it's pretty slow when you actually need to use it. If you get it going it will pick up the pace, but it's far from usable, being in an app for longer than a minute and touching the home screen button will freeze it up for 10 seconds before it takes you to an empty screen that takes another few seconds to load all the apps and widgets back in. I'd wait for a newer release.

Feedback
Hello i have tried the older version and it was great but i really need my camera so i went back to 4.4 but i appreciate you so much thanks !
Please fix the camera asap and i will definitely install this rom ! and i tried to install the new version but it said Error Binary something in TWRP recovery what can i do thanks!

Q
Is the camera fixed yet?

Notification Light
Is there a way to disable the notification light while the phone is plugged in via USB? It's a little annoying to be on while I'm sleeping. It's not a huge issue though.

TheIbanez97 said:
Is there a way to disable the notification light while the phone is plugged in via USB? It's a little annoying to be on while I'm sleeping. It's not a huge issue though.
Click to expand...
Click to collapse
I don't think so.

I found that the miscellaneous section of the battery stats was taking up most of the battery usage. I don't have any apps installed other than the stock standard.

[Resolved] Problem with first boot on stock based MM ROM

Hello guys.
May I ask your help for a weird issue I have since the MM based stock ROMs. Indeed, I run CM based ROMs since kitkat
But 3 weeks ago, I decided to test the Fulmics ROM. I did a full wipe (including internal storage), then I installed fulmics from internal storage, and after the first boot, I arrived on the lockscreen asking me to draw a pattern to unlock my phone (nothing about unlock SIM card).. But, obviously, I never configured the ROM to have that pattern, given the fact it's the first boot. And any of the random patterns I draw are working of course....
I tried different parameters in the Aroma installer (i double and triple checked that I had D855 chosen), I also tried with other MM based stock ROMs, but I still have this damn pattern. The weird thing is that I don't have this problem with LP based stock ROMs.
As I am using TWRP 3.0, I installed both official and unofficial versions. I even tried to reinstall TWRP 2.7, but the bug was still there.
Do you have any idea what's going on ? Thank you very much guys !!

After flashing, at first boot it sound take you through the setup stuff then take you to your home screen when you're finished. At that point you should be able to go into the settings and look at the lockscreen settings. Does it immediately go from the setup to the lockscreen, or is there a delay that causes the screen to get locked? Which other MM ROMs have you tried and had this happen with? I would think doing a full wipe beforehand would make this impossible unless it was maybe a bad build, which could maybe be possible if it was one ROM (maybe), but very unlikely multiple developers would happen to make this same mistake when building.

Hi akksnv, thank you for your answer !
akksnv said:
Does it immediately go from the setup to the lockscreen, or is there a delay that causes the screen to get locked? Which other MM ROMs have you tried and had this happen with?
Click to expand...
Click to collapse
Yes it goes directly to the lockscreen after the bootamination. I've tried different fulmics versions (3.1, 3.5, 4.0), the Nova Stock ROM, and the SeXy ROM, and yes, with all these ROMs I have this bug.
akksnv said:
I would think doing a full wipe beforehand would make this impossible unless it was maybe a bad build, which could maybe be possible if it was one ROM (maybe), but very unlikely multiple developers would happen to make this same mistake when building.
Click to expand...
Click to collapse
Yes, it's definitively a bug with my phone and not with these ROMs. And yes, it's very strange that after a full wipe, this locksreen stuff shows up... Because I use this pattern lockscreen on my actual Resurrection Remix ROM, but the wipe should erase every setting....
Other werid thing, I have 30 attemps to unlock the phone, and after the first try, the cycle counter goes to 29/30 and comes back to 30/30 after 3 seconds.

I saw something somewhere else that sounded like this kind of thing also happens if you have a locked/encrypted SIM card, could that possibly be the case? I don't know that this behavior would be different between LP and MM if this were the cause, but thought I'd mention it.

I have no idea about my sim card but maybe it worths trying to install without it in the phone.
Anyway, thanks for your help man !

For those it can help, I resolved my problem by installing a lollipop KDZ file, through LG Flashtool.
I don't know why, but my lockscreen problem disappeared after that.

bootloop/lockscreen freezed

hello. i bought an old wildfire; s-off, h-boot 1.0.xxxx and i installed new stock rom (method flashing zip via bootloader) and the boot is veeery long; i think i waited 10 minutes, and after that the stock lockscreen remained blocked...i cant turn off the display, actioning the volume or making any gesture...is freezed, dead... and still same if i remove battery and turn on again...what can be done?

straciatella said:
hello. i bought an old wildfire; s-off, h-boot 1.0.xxxx and i installed new stock rom (method flashing zip via bootloader) and the boot is veeery long; i think i waited 10 minutes, and after that the stock lockscreen remained blocked...i cant turn off the display, actioning the volume or making any gesture...is freezed, dead... and still same if i remove battery and turn on again...what can be done?
Click to expand...
Click to collapse
Hi there, I saw your comment on the other thread but decided to reply here. If you have reflashed the stock rom and its crashing at the lock screen you only have two choices really. 1: Try a custom rom like cyanogenmod 7 to see if the lighter rom runs on your old hardware. 2: Give up on the phone.
I accept that 2 may not be what you want to hear but this device is very old now (in phone years) and a lot of the services that used to support it well, like the android market (Google play) do not really support this device. If you only really want to use the phone for phone calls a cheap "dumb" phone will perform much better than this device in that regard.
If you do want to try though, cm7 is your best bet as it gave the best "performance"on this device back in its hayday.
Best of luck.

heavy_metal_man said:
Hi there, I saw your comment on the other thread but decided to reply here. If you have reflashed the stock rom and its crashing at the lock screen you only have two choices really. 1: Try a custom rom like cyanogenmod 7 to see if the lighter rom runs on your old hardware. 2: Give up on the phone.
I accept that 2 may not be what you want to hear but this device is very old now (in phone years) and a lot of the services that used to support it well, like the android market (Google play) do not really support this device. If you only really want to use the phone for phone calls a cheap "dumb" phone will perform much better than this device in that regard.
If you do want to try though, cm7 is your best bet as it gave the best "performance"on this device back in its hayday.
Best of luck.
Click to expand...
Click to collapse
mya...i tryed before to install cm7,9,10 etc, but still same... i was hoping that ill repair it not for daily use ,services.with apps ,etc, but only for calling and messaging. anyway, thanks for your answer