Hi, I am new here
I have a Samsung Galaxy Mini, updated to Gingerbread 2.3.5 from Froyo and rooted successfully using universal gingerbread v19.
Sometimes, when making a call to any number, after touching the large green button, the screen fades to black and the phone seems to hang, but it makes the call and I can hear it successfully, but I cannot interact with the phone anymore, I tried pressing all buttons, even when the call finishes, and I have to force reboot by long pressing the power button. I don't know if this has something to do with the rooting (maybe I will try to unroot and see if this persist)
Does anyone know why?
Many thanks
Try to update it to 2.3.6 and lets see if it still persist
Sent from my GT-S5570 using xda premium
kenjilucas19 said:
Try to update it to 2.3.6 and lets see if it still persist
Sent from my GT-S5570 using xda premium
Click to expand...
Click to collapse
Many thanks
Finally it was a stupid mistake from my end. The silicon cover was half covering the proximity sensor and it was activating it constantly sometimes, so the phone would "hang" (the screen turns off and it becomes non-responsible when making or receiving calls), I didn't know the proximity sensor was this
Anyway I'll try to update to 2.3.6 but I've read the phone would need to be unlocked from carrier (I do not have another SIM card right now, but I have the unlock code) or it would brick when installing the new ROM, is that true? Because I cannot find official (Samsung) updates to 2.3.6 at least from Kies...
Derek100 said:
Many thanks
Finally it was a stupid mistake from my end. The silicon cover was half covering the proximity sensor and it was activating it constantly sometimes, so the phone would "hang" (the screen turns off and it becomes non-responsible when making or receiving calls), I didn't know the proximity sensor was this
Anyway I'll try to update to 2.3.6 but I've read the phone would need to be unlocked from carrier (I do not have another SIM card right now, but I have the unlock code) or it would brick when installing the new ROM, is that true? Because I cannot find official (Samsung) updates to 2.3.6 at least from Kies...
Click to expand...
Click to collapse
flash a custom rom be very careful in flashing roms you need to follow the instructions
If you still dont know the basics in flashing
Ill give you a procedure how to flash a custom rom or update it 2.3.6
Sent from my GT-S5570 using xda premium
Related
I've installed 2 JB ROMS on my Gamsung galaxy S i9000
When I unlock the phone, some random touch or gestures are generated, without touching the screen. It looks like the phone is cursed.
I press the power off button to lock it, and when I unlock it, it all works well again.
It seems like there is a bug in the touch driver as it didn't happen in my previous Gingerbread ROM. I have tried to go back to GB again to validate and it works well. As soon as I get JB, then it starts doing that.
It only happens after unlocking. If it doesn't happen straight away when I unlock it, then it doesn't happen.
I have tried already 2 Jelly bean roms and they all seem to have the same problem, so I guess it's in the main source code as they both are coming from the same JB source.
Happening in
[ALPHA][ROM][4.1.1] CyanogenMod 10 for Samsung Galaxy S
[ROM] Helly_Bean [4.1.1], based on sources of cm10
Anybody has had this issue?
I had that when I was in a hurry but just one time.
robertical said:
I've installed 2 JB ROMS on my Gamsung galaxy S i9000
When I unlock the phone, some random touch or gestures are generated, without touching the screen. It looks like the phone is cursed.
I press the power off button to lock it, and when I unlock it, it all works well again.
It seems like there is a bug in the touch driver as it didn't happen in my previous Gingerbread ROM. I have tried to go back to GB again to validate and it works well. As soon as I get JB, then it starts doing that.
It only happens after unlocking. If it doesn't happen straight away when I unlock it, then it doesn't happen.
I have tried already 2 Jelly bean roms and they all seem to have the same problem, so I guess it's in the main source code as they both are coming from the same JB source.
Happening in
[ALPHA][ROM][4.1.1] CyanogenMod 10 for Samsung Galaxy S
[ROM] Helly_Bean [4.1.1], based on sources of cm10
Anybody has had this issue?
Click to expand...
Click to collapse
Be sure you don't have the phone connected to a USB3 port when trying that.
I've only seen that happen in that situation.
Sent from my GT-I9000 using xda premium
pmos69 said:
Be sure you don't have the phone connected to a USB3 port when trying that.
I've only seen that happen in that situation.
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
It happens randomly and without being connected to the USB at all.
As soon as I press the power button and I unlock it again it works well for the rest of the time I'm using it.
It seems that it could be related to the initialization of the touch driver or the screen.
Never happened in GB.
robertical said:
It happens randomly and without being connected to the USB at all.
As soon as I press the power button and I unlock it again it works well for the rest of the time I'm using it.
It seems that it could be related to the initialization of the touch driver or the screen.
Never happened in GB.
Click to expand...
Click to collapse
Same here
Have you found a solution now??
I have the same problem but in my case it happens when my phn is charging with blackberry charger when i unplugged it, it becomes normal..
Mayby try Elite JB RC12 (4.1.1) / JRO03L. This is not CM10.
eugenbljed said:
Same here
Have you found a solution now??
Click to expand...
Click to collapse
I installed GB Alliance JW6/ Semaphore and problem solved.
It works just as fast and it's got less problems.
Hello,so yesterday i noticed that my phone sometimes automaticly wakes up,its like i have pressed Unlock button or Main button.
Its really irritating and has someone expirienced this kinda of trouble?
I have Samsung Galaxy Note GT 7000,running 4.1.2
DzoNii said:
Hello,so yesterday i noticed that my phone sometimes automaticly wakes up,its like i have pressed Unlock button or Main button.
Its really irritating and has someone expirienced this kinda of trouble?
I have Samsung Galaxy Note GT 7000,running 4.1.2
Click to expand...
Click to collapse
what rom have you installed ?maybe reinstalling will help
pippilangkous said:
what rom have you installed ?maybe reinstalling will help
Click to expand...
Click to collapse
Its all stock,haven't done anything,didn't customized it
do you have any antivirus installed that scans automatically and wakes cpu clock?
When wakes up look to see if it showing that the battery is charging if it is try cleaning the USG port with a tooth pick or something when lent or dust build up in there it collects moisture and shorts out the plug which makes it think it is being charged this has happen to me and is how I fixed the issue
Sent from my GT-N7000 using XDA Premium HD app
you could use an app called wakelock detector from the play store to check
I don't have any antivirus,usb port is clean,it just wakes up randomly
DzoNii said:
I don't have any antivirus,usb port is clean,it just wakes up randomly
Click to expand...
Click to collapse
I would say flash the stock ROM again. No root needed.
Do a wipe data/factory reset, download the stock rom from sammobile.com and flash using pc odin. Make backup of your data before this on sd card and remove sd card. This wont root ur phone but just reinstall everything stock.
this may fix the issue as it seems to be a software bug or may be any of the app installed in ur phone is doing this.
Thanks folks,fixed it <3
Hello guys,
I have around 2-year old Note GT-N7000 which I tried flashing a week ago. I did a few steps (don't remember any though) and something went wrong. Everything with the phone was working fine except the keyboard was typing 'null' and the screen had a weird problem. The phone will boot normally and the screen would be fine until it turns off (auto off or manually by button). Now if I try to switch on the screen it would start as if it's warming up. A sky with tiny stars kind of scene would appear and the brightness will keep increasing. The phone is functioning at this point and so is screen but nothing can be seen. I know this because I can receive a phone in this state by guessing the swipe location and swiping. Once in this mode, I have no option but to restart the phone. And then again everything works fine as long as I do not let the screen go off.
I got panicked and after a full research of 5 days on XDA, I decided to flash another ROM, probably a JB. I rooted my phone, install CWMR, bought mobile odin pro only to mess the things further. I downloaded the Ultimate Alliance ROM v3 and tried flashing it using the mobile odin. I guess I didn't follow the instructions properly and the phone went into bootloop. I then flashed GB KJ1 using ODIN which landed me at N7000 screen freeze and not able to enter recovery mode. Then I flashed AbyssKernel which helped me boot properly. Once I was in I realized I'm still on GB so probably JB never got installed.
Now the current problems are:
1. The keyboard is still typing nulls
2. The screen is still going into comma
3. There is a yellow triangle at the GT-N7000 screen.
My phone version is:
Baseband version: N7000XXLSO (it was N7000DDLR1 two hours ago)
Kernel: 2.6.35.7-N7000XXKJ1-CL627135
Build No: GINGERBREAD.XXKJ1
Sorry all this is noob stuff and maybe there is a solution in the forum already but after 5 nights of research and lots of messing around, I am not sure what do I do next. I certainly don't want to hard brick the phone.
Desperately need your help to come out of this mess. Even I'm happy to have the oldest stock ROM.
Thanks in anticipation and sorry for the long post.
trunoob said:
Hello guys,
I have around 2-year old Note GT-N7000 which I tried flashing a week ago. I did a few steps (don't remember any though) and something went wrong. Everything with the phone was working fine except the keyboard was typing 'null' and the screen had a weird problem. The phone will boot normally and the screen would be fine until it turns off (auto off or manually by button). Now if I try to switch on the screen it would start as if it's warming up. A sky with tiny stars kind of scene would appear and the brightness will keep increasing. The phone is functioning at this point and so is screen but nothing can be seen. I know this because I can receive a phone in this state by guessing the swipe location and swiping. Once in this mode, I have no option but to restart the phone. And then again everything works fine as long as I do not let the screen go off.
I got panicked and after a full research of 5 days on XDA, I decided to flash another ROM, probably a JB. I rooted my phone, install CWMR, bought mobile odin pro only to mess the things further. I downloaded the Ultimate Alliance ROM v3 and tried flashing it using the mobile odin. I guess I didn't follow the instructions properly and the phone went into bootloop. I then flashed GB KJ1 using ODIN which landed me at N7000 screen freeze and not able to enter recovery mode. Then I flashed AbyssKernel which helped me boot properly. Once I was in I realized I'm still on GB so probably JB never got installed.
Now the current problems are:
1. The keyboard is still typing nulls
2. The screen is still going into comma
3. There is a yellow triangle at the GT-N7000 screen.
My phone version is:
Baseband version: N7000XXLSO (it was N7000DDLR1 two hours ago)
Kernel: 2.6.35.7-N7000XXKJ1-CL627135
Build No: GINGERBREAD.XXKJ1
Sorry all this is noob stuff and maybe there is a solution in the forum already but after 5 nights of research and lots of messing around, I am not sure what do I do next. I certainly don't want to hard brick the phone.
Desperately need your help to come out of this mess. Even I'm happy to have the oldest stock ROM.
Thanks in anticipation and sorry for the long post.
Click to expand...
Click to collapse
Jesus Christ, way to get yourself into a mess... The null keyboard just means you have to reflash the csc correctly. Extract the gb rom file and it should reveal a csc file, input that into the csc part of mobile odin and flash.
Screen problems... How old is your battery?
Triangle issue, just download triangleaway app from play store and run.
Hopefully you've learnt something about following directions to a t. Don't think you've done any lasting damage though, you're lucky.
Sent from my GT-N7000 using xda premium
Thanks a lot for the quick help.
The battery is as old as the phone i.e. about 2 years.
I had flashed the same phone around an year ago and I faced similar screen issue when I tried flashing ICS last year and then I reflashed GB (the current ROM I guess) and the problem disappeared. Do you think it could be because of wrong flashing as well?
Is there is safe route to a relatively safe flashing which could reassure whether I should buy a new battery or not? Or shall I go ahead and invest in the battery regardless?
Thanks once again.
trunoob said:
Thanks a lot for the quick help.
The battery is as old as the phone i.e. about 2 years.
I had flashed the same phone around an year ago and I faced similar screen issue when I tried flashing ICS last year and then I reflashed GB (the current ROM I guess) and the problem disappeared. Do you think it could be because of wrong flashing as well?
Is there is safe route to a relatively safe flashing which could reassure whether I should buy a new battery or not? Or shall I go ahead and invest in the battery regardless?
Thanks once again.
Click to expand...
Click to collapse
Safest flash would be to flash latest gb rom for your region. I'd be amazed if the battery wasn't dead though, they usually only last just over a year. Symptoms of dead battery are screen flicker, sudden power loss and gain, physical swelling (put on flat surface and spin) colour change on screen, amongst other things.
Sent from my GT-N7000 using xda premium
SpyderTracks said:
Safest flash would be to flash latest gb rom for your region. I'd be amazed if the battery wasn't dead though, they usually only last just over a year. Symptoms of dead battery are screen flicker, sudden power loss and gain, physical swelling (put on flat surface and spin) colour change on screen, amongst other things.
Click to expand...
Click to collapse
Thanks a lot for the help. I could successfully flash GB 2.3.6 from Dr Ketan's thread and everything is working like charm. The screen issue that I mentioned is gone.
Thanks once again.
trunoob said:
Thanks a lot for the help. I could successfully flash GB 2.3.6 from Dr Ketan's thread and everything is working like charm. The screen issue that I mentioned is gone.
Thanks once again.
Click to expand...
Click to collapse
Good news, well done
Sent from my GT-N7000 using xda premium
Hey guys,
a friend of mine gave me his Optimus Black. Someone installed a bricked rom on it.
It has some absolutely strange behaviour, cause the Screen doesnt respond in any logical reason.
Sometimes i manage to unlock the screen, but i cant do anything cause the 'hardware'-buttons are not recognized either.
Due to non responsive hardware buttons, i'm unable to enter any kind of recovery...
Volume control does work.
Is there any way i could possibly do sth about this problem?
Will post Screenshots or Video of the Rom later.
Thanks in Advance
Hi, maybe you can use SmartFlash tool and flash a rooted gingerbread rom with a recovery and from there, do a complete wipe then flash a new custom rom. You can refer to http://forum.xda-developers.com/showthread.php?t=1111771. Hope it helps.
Are you sure that the power button is working?
Try to push the battery cover next to the camera flash and press the power button at the same time.
If it works then its a hardware problem .
Seems like it is a Problem with The Touchscreen. Someone changed it and did something wrong, tgread can be closed
Sent from my XT925 using xda app-developers app
As we all know by now the official 4.3 came out for the xperia T which was de and rooted, i installed it on the my xperia tl following the step by step instructions on the thread, everything works smooth for a while until the screen standby. when it does and im trying to unlock the phone the touch doesnt respond, i press the power button and tired again still nothing, pressing the power button several times and then the screen start pressing random things on its on activating and deactivating settings task bar is being pulled down etc then the touch start working and im able to use the phone until the screen time out and it happen all over again. i switch back to the 4.1.2 and i have no problem at all with it but im jus curious has anyone of the tl users experience this problem and is there a bug for us on the 4.3 and or if there is a solution ? please help me cause i love the 4.3 but hate the problem i have with it
Umm I had the same problem using the leaked version.. Since I'm using the official one I haven't had the problem.
What helped for me was to power off the phone using power and volume up buttons
St.Jimmy90 said:
Umm I had the same problem using the leaked version.. Since I'm using the official one I haven't had the problem.
What helped for me was to power off the phone using power and volume up buttons
Click to expand...
Click to collapse
i tried all that .. i also wipe cache and those other things . are u using a TL also?
No Xperia t
i need to know if any TL users are having this problem
I'm on a TL with official 295...everything works for me like it did on 4.1.2
Sent from my LT30at using xda premium
Did you try if reinstalling solves your problem?
St.Jimmy90 said:
Did you try if reinstalling solves your problem?
Click to expand...
Click to collapse
i tried everything i did it over from the begining with a stock 4.1 firmware from att and then root install cwm 8 wipe cache and factory reset and wipe the dalvik install rom and then update superuser right after . then reboot . when it loads it works perfect for the first few mins then something got activated and thats it the screen jus went crazy it start jumping and touching all over the place and then stop .
My Xperia T has same problem. Maybe because i took the screenprotector off and the touch screen is a bit damaged by it now?
silasje1 said:
My Xperia T has same problem. Maybe because i took the screenprotector off and the touch screen is a bit damaged by it now?
Click to expand...
Click to collapse
i dont think the screen protector has anything to do with it because i would have had the same problem when im on 4.1.2 because i did remove my factory installed sony screen protector aswell. i really believe its the firmware or module or drivers .what ever it uses to control the touch
i think i might find the problem, well atlease for my device ... my usb port is acting up when ever i plug it in anything wall charger or pc is freezes and i also disable to slide to unlock and set time out to 10 mins .. idk if this works for anyone else but ive been on it for 30 mins now and nothing has gone wrong so far
I must confirm that removing the screen protector makes the screen touches working a little bit worse, because the glass gets easier oily. It's even more worse, when usb charging is connected. Cleaning the glass makes it better again.
No issues
http://forum.xda-developers.com/showthread.php?t=2647459 Flashed this via cwm 6. Read the whole thread first. CWM 8 has been reported buggy by the DEV. Flashed from rooted stock 4.1.2 AT&T TL bond
gpgon said:
http://forum.xda-developers.com/showthread.php?t=2647459 Flashed this via cwm 6. Read the whole thread first. CWM 8 has been reported buggy by the DEV. Flashed from rooted stock 4.1.2 AT&T TL bond
Click to expand...
Click to collapse
i didnt know 8 was buggy i thought it was most stable .. ill try 6 .. thanks
i tried 6 .. its the same s**t so im done with this im jus gonna go back to 4.1 i cant deal with this anymore ive been trying for days to get this to work properly and its not like im a complete noob cause i came from the x10 so im quiet familiar .. so thanks for all ur help guys but im done with this