Hi everyone,
I have been using the F1 Galaxy nexus rom on my Galaxy s2 and have had a problem with it freezing on me a couple of times.
Today I finished making a Skype call and the phone froze as I tried to pull down the notification bar. It just sort of hung halfway down. After that it pretty much froze up apart from the fact that I was able to power off using the power button.
I am wondering if I have the right Clockworkmod recovery on my phone. I installed recently CF-Root XX_XEO-LPQ v5.4 as previously I tried out the official samsung Ics ROM XX_LPQ.
After this I flashed the nexus f1 rom using the same version of clockworkmod.
Can anyone advise me if this is the correct one to use to flash the nexus f1 rom or is there another version that is more compatible with this rom. I have read that you need the correct kenel to match your phone's firmware and that certain kernels down't work with certain roms.
Please excuse my general ignorance. I have tried searching for an answer on the forum but couldn't find what I was looking for
I have included a screenshot of my phone's settings if that helps
Just a quick question, did you factory reset after flashing?
Yes I did a clean wipe and factory reset before flashing the F1 From. To be honest 99 per cent of the time it runs just great. But it does have the occasional freeze
Sent from my GT-I9100 using XDA
seancyril said:
Yes I did a clean wipe and factory reset before flashing the F1 From. To be honest 99 per cent of the time it runs just great. But it does have the occasional freeze
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
I don't know what to say then. It is recommended to factory-reset after flashing new roms, and I would suggest you to do this if you haven't.
Anyway you can ask in the SGS2 development forum, I'm sure there is a thread for that ROM, and there might be more people experiencing that issue posting there.
Good luck.
Hi
I bought my device a few months ago and it was working perfectly, then one day, all of a sudden the keyboard just started lagging, alot, I couldnt type a single word properly without it getting stuck. I tried updating to Custom ROMs and also to the latest Stock Rom (2.3.6 XWLF3) but after a few hours, the keyboard goes back to lagging. I have tried formatting, factory reset, through the phone and the recovery, but it is still giving me the same problem. Please help.
And btw, I have looked through a lot of forums and websites, but I havent really got a proper answer
flash UC kernel pal. the latest version.
or you can also wipe dalvik cache. and also the most common solution is always activate autorotate screen. many experienced before in stock roms when you deactivate autorotate screen, the keyboard lags.
Okay Ill try it and let you know, thanks
Sent from my GT-I9003 using xda app-developers app
Okay Ill try this also and let you know, thank you
Sent from my GT-I9003 using xda app-developers app
marshygeek said:
flash UC kernel pal. the latest version.
Click to expand...
Click to collapse
Uhmm...can you give me the link for UC Kernel for XWLF3, cause i couldnt find it for this version
Thank You
try this. http://icxperia.com/napstar/sgsl/UC-KERNEL-v15-XXKPQ-GT-I9003_PDA .tar
OK so what happened was I had the latest CM10 build installed and wanted to try the paranoid android rom out and I flashed my device with the 2.50 build. I soft bricked it. I could still go into recovery but the device wouldnt load into paranoid android. I had an emergency so I had to leave the device the way it was in a bootloop state I came back the device was off. Obviously It ran out of juice. And now when I try to charge it i don't get any response...... could this be a hard brick?? ??
please guys any help would bbe greatly appreciated!
Sent from my GT-P6200 using XDA Premium HD app
Happened to once with a different model. Never had it fixed, as suggested by a technician, go to someone who has a JTAG. Same with what I was thinking, but I never bothered to had it fixed.
Good luck.
Sent from my GT-P6200 using xda premium
Well if I'm not mistaken I don't think there is jtag for our devices. well I fixed it now thank god! I took apart another p6200 and swapped out the batteries and as soon as I swapped them the one I thought was bricked booted up! I flashed the stock rom then rootedbit ahandball that now its working great! I guess it doesn't charge whenbits in a boot loop or something? Thanks man I really appreciate ur help
Sent from my GT-P6200 using XDA Premium HD app
I just had this problem too and couldn't find any answers about what can I do to solve it...
I was trying to flash ICS ROM over Odin (I hate it), and it always stucked on the process. When I tried to reboot, it did just not woke up again!
What may have happened? Does someone knows what to do now?
I really don't know what to tell you... for me swapping out batteries fixed it but it was a real pain to do so. You could try keeping it plugged into the charger for a while and ssee if the screen powers on. If it does just put your tab in download mode and flash from Odin. Maybe u had a llow charge when you tried flashing stock?
Sent from my GT-P6200 using XDA Premium HD app
Update: This issue has been resolved in CyanogenMod 11. As of now, there is no 'official' CM 11 for the Samsung Galaxy Tab 2 (GT-P3100, GT-P3110, or GT-P3113), but CodyF86 has a great build of it here. Anyway, here is the commit: (http://review.cyanogenmod.org/#/c/56562/3)
Hey Guys,
Let me first start off by saying this problem in no way effects overall performance and operation of my device. With that being said, this problem is just more of a cosmetic issue with CyanogenMod and the OCD I have towards it. Right after CyanogenMod upgraded from the 10 to 10.1 builds, the boot logo changed from landscape to portrait. What happened with my device (Galaxy Tab 2 7.0 GT-P3113) is slightly odd. The boot logo for CyanogenMod is now stuck in the upper right corner of the screen and appears squished. As I said before, this DOES NOT impact device operation, so if you have another thread to watch, I suggest you do that. But if you are inclined to help me fix this problem, please note that I have already done the following:
Flashed device to stock ROM using ODIN
Re-rooted the device using the auto root tool for this device
Flashed CWM Recovery latest version (Touch) using ODIN
Re-installed the latest version of CyanogenMod 10.1 Stable
There is an image of the issue attached to this post below if you are interested.
Thank you for your support!
-RespawnedEvil
RespawnedEvil said:
Hey Guys,
Let me first start off by saying this problem in no way effects overall performance and operation of my device. With that being said, this problem is just more of a cosmetic issue with CyanogenMod and the OCD I have towards it. Right after CyanogenMod upgraded from the 10 to 10.1 builds, the boot logo changed from landscape to portrait. What happened with my device (Galaxy Tab 2 7.0 GT-P3113) is slightly odd. The boot logo for CyanogenMod is now stuck in the upper right corner of the screen and appears squished. As I said before, this DOES NOT impact device operation, so if you have another thread to watch, I suggest you do that. But if you are inclined to help me fix this problem, please note that I have already done the following:
Flashed device to stock ROM using ODIN
Re-rooted the device using the auto root tool for this device
Flashed CWM Recovery latest version (Touch) using ODIN
Re-installed the latest version of CyanogenMod 10.1 Stable
There is an image of the issue attached to this post below if you are interested.
Thank you for your support!
-RespawnedEvil
Click to expand...
Click to collapse
Same problem here, only on my device it changes after about 5 seconds to normal. Already looked into this and, as far as I could find, there is no solution yet.
its common problem we all get that
Same here.
I rarely reboot the device and it doesn't seem to actually affect the device, so I just ignore it.
ddochi11 said:
Same here.
I rarely reboot the device and it doesn't seem to actually affect the device, so I just ignore it.
Click to expand...
Click to collapse
LET'S not ignore this bug, as this is not supposed to happen. If anybody else has this issue, please raise your hand and post it here. This has been going for a loong while and needs to be fixed.
Hey there is a way to get rid of it.
Please follow the instructions
1. Get the latest phillz recovery. Install it using ur present recovery.
2. Get the latest black hawk next kernel v1.8.3. Flash the zip file.
3. Get the vendor blobs (not necessary cuz the latest nightlies have them preinstalled)
4. Go to /system/buildprop file n change rf. so .hwrotation=270 to rf. so
.hwrotation=0
5. Reboot the device.
Press thanks if I helped.
Sent from my GT-P3100 using xda app-developers app
*EDIT: The screen is screwed up now. It's taking portrait touch responses instead of landscape ones, and the screen does not rotate.
I can confirm this works in landscape mode, but isn't portrait the intended orientation?
No I changed the settings wanting it to be in landscape mode cuz i use tablet ui n it makes my tab look better. Need to work around a way for portrait mode.
Sent from my GT-P3100 using xda app-developers app
Yes, but the touch screen reverses the input of my finger and rotates the screen opposite and to the left of the way I'm holding it. You have no idea how hard it was to restore the build.prop when you need to use a broken UI to enable USB debugging. Ugh..
OK but I have no such issues, been running it smoothly since a week.
Sent from my GT-P3100 using xda app-developers app
I have it aswell!
I have this same issue, not only with the rom, but ALL of them.
Report to CyanogenMod Developers?
Someone should forward this thread to the CM dev team. Maybe then, and only then will it be fixed.
i think all of the tab2 which use CM rom have the same problem, my tab2 p3110 too...
hope someone of the CM devteam can fix it
impliu said:
i think all of the tab2 which use CM rom have the same problem, my tab2 p3110 too...
hope someone of the CM devteam can fix it
Click to expand...
Click to collapse
I believe it is only a problem with the 7" models of the Samsung Galaxy Tab 2 tablets.
vehvariya said:
Hey there is a way to get rid of it.
Please follow the instructions
1. Get the latest phillz recovery. Install it using ur present recovery.
2. Get the latest black hawk next kernel v1.8.3. Flash the zip file.
3. Get the vendor blobs (not necessary cuz the latest nightlies have them preinstalled)
4. Go to /system/buildprop file n change rf. so .hwrotation=270 to rf. so
.hwrotation=0
5. Reboot the device.
Press thanks if I helped.
Sent from my GT-P3100 using xda app-developers app
Click to expand...
Click to collapse
I've tried to install black hawk next kernel,and my p3110 was stucked at the Boot Logo..
I must flash phillz recovery first? I'm using the CWM recovery.
The problem is there in almost every ROM except for AOSPA http://forum.xda-developers.com/showthread.php?t=2168670 . If we can just find whats the difference?
THpubs said:
The problem is there in almost every ROM except for AOSPA http://forum.xda-developers.com/showthread.php?t=2168670 . If we can just find whats the difference?
Click to expand...
Click to collapse
That seems odd indeed. I will compare the two tonight and hopefully get some results.
Also, thank you for introducing me to a lovely new ROM.
-RespawnedEvil
RespawnedEvil said:
That seems odd indeed. I will compare the two tonight and hopefully get some results.
Also, thank you for introducing me to a lovely new ROM.
-RespawnedEvil
Click to expand...
Click to collapse
You welcome. I used AOSPA but its a bit sluggish compared to CM. Might work for you but I want speed
Philz recovery is a must. Otherwise it won't boot. Use the latest version of it.
Sent from my GT-P3100 using xda app-developers app
I think this is the common bug for tablets
While back I wiped my device in clock work recovery and accidentally rebooted device after a full wipe (oops) afterwards it didn't respond to touch, but will respond to the s pen. At the time there was no easy fix for it, or really any fix at all, so I unrooted it and have been using the s pen. Im just trying to see if there have been any kind of changes in this issue. Looked around forums and saw nothing on the matter.
Sent from my GT-N8013 using XDA Premium 4 mobile app
SynysterSilence said:
While back I wiped my device in clock work recovery and accidentally rebooted device after a full wipe (oops) afterwards it didn't respond to touch, but will respond to the s pen. At the time there was no easy fix for it, or really any fix at all, so I unrooted it and have been using the s pen. Im just trying to see if there have been any kind of changes in this issue. Looked around forums and saw nothing on the matter.
Sent from my GT-N8013 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
hello, i ask if you already solve your problem sir?
hello, did u fix it by digitizer? thats also my problem but i dont know if digitizer is need to replce or program files