I own a M250s which i have transformed it into S2 by installing a firmware from Singapore, It works perfectly but i have a small problem which is that when i long press the touchscreen off button, It is switching off my phone instead of showing a pop-up
I have found out a new problem that the lock screen is not coming up. The slide unlock is not working
Although i have solved the above 2 problems. Is there any fix for low vibration for the phone??
ronak_143 said:
Although i have solved the above 2 problems. Is there any fix for low vibration for the phone??
Click to expand...
Click to collapse
How did u solve the problems, i am also having them, please help
Roguesniper1 said:
How did u solve the problems, i am also having them, please help
Click to expand...
Click to collapse
if u use siyah kernel with Extweak app then u can set the Vibration intensity level
PS- siyah kernel wrks only with GT i9100 (international) model only, so not sure about m250s though
Related
When i press *#0*#, proximity value is change but when i call LCD screen wont to turn off.
In settings i thick turn the prox. sensor!
I try few stock roms, but nothing
Is there something like drivers to put with root explorer?
Please help
Hello,
I have exactly the same problem...
When I do a proximity test in *#0*# my proximity sensor turns on (goes red) and works perfectly.
But when I do a call it doesn't work... Not even turns on.
Is there any settings to enable it or is it related to something different?
Tried 3 stock roms but they all had the same results...
Thanks
Have you tried flashing CM7 or if your not on the latest Samsung rom, updating to that
If I have helped you, please feel free to press the thanks button below
danielsf said:
Have you tried flashing CM7 or if your not on the latest Samsung rom, updating to that
If I have helped you, please feel free to press the thanks button below
Click to expand...
Click to collapse
Nope I haven't tried CM7. And I want to stick with the stock rom
But my rom is I think one of the latest official roms. I got it today from here. It is DXKL3.
Armenium said:
Nope I haven't tried CM7. And I want to stick with the stock rom
But my rom is I think one of the latest official roms. I got it today from here. It is DXKL3.
Click to expand...
Click to collapse
my stock rom is xxki3, do you solve your problem Armenium?
danielsf said:
Have you tried flashing CM7 or if your not on the latest Samsung rom, updating to that
If I have helped you, please feel free to press the thanks button below
Click to expand...
Click to collapse
do you have the same problem please help!
Hey guys
I've following problem.
A while ago i've accidentally bricked my gorilla glass on my s2...but amoled and all is working fine though:highfive:....than i bought only gorilla glass part...i wanted to change it myself....but....when i ripped my s2 apart and started detaching whole screen from housing.....the LED's part got broken....so now my led's are gone....it's not such a big deal as i'm using button saviour from playstore.....BUT.....What i'd like to know is: Is there any way to disable BLN from within build.prop file?...because if i flash any other rom and if i make a full data wipe from cwm my s2 catches in a bootloop because BLN is enabled by default....so....is there any way to disable BLN?
Any help is highly appreciated,
Thanks in advance
>>>>>>>>>>>>>>>>>>>>>>>>>
Sent from my SGS-II powered by ~CyMod~10~&~DoRimanX v 7.0 kernel
<<<<<<<<<<<<<<<<<<<<<<<<<
That's hardware problem, so even if you leave BLN enabled you won't have any bootloops...
przemcio510 said:
That's hardware problem, so even if you leave BLN enabled you won't have any bootloops...
Click to expand...
Click to collapse
well...if that would be like u said...i would be happy...but it's not...i've found out that if i delete galaxy s2 settings before i flash a rom itcs ok...but with latest JB/CM 10/10.1 builds this method became useless...still searching for solution before orderjng new touch keys...anyone?
Sent fom my S-II running CM-10 by mcm811 powered with DorimanX kernel 7.35
Hi,
I'm a new member :fingers-crossed: and a new noob, that's how you call it here :highfive:
I have a lot of ROM's flashed (ICS and JB).
Maybe I'm the only one with this bug but that's my story:
I tried a few Jelly Bean 4.1.2 ROM's (NeatRom, NeatRom Lite and Simplistic), but on each ROM I had the same bug, if I receive a call or I'm calling someone after exactly 1 minute the call was broken suddenly!!!!!!
Each time I've done full wipe before flashing and tried to see in the settings if something is wrong but no idea at all.
Now I'm back to the Dilidroid ICS and everything it works well.
Also I tried the Pffitech 1.1.3 JB and it works, so no broken calls after 1 minute.
Does someone had the same bug? Could be a kernel issue?
Or maybe some idea what went wrong?
Now I'm gonna try also JoelDroid S2 2.1 ROM, who knows maybe I have luck and no call issues.
Thank you for your help, appreciated :good:....oh btw, sorry for my poor english
My phone:
Samsung Galaxy GT-I9100
Baseband version:I9100XXLS6
Kernel: 3.0.34-Siyah-v.3.3.24
Build number: Dilidroid ICS R4.1 UHLPS
It would not be a kernal issue, but a modem issue.
Try another modem but do not change the ril or you will have more problems.
There have been reported problems with the modem in certain areas.
Cosmic Blue said:
It would not be a kernal issue, but a modem issue.
Try another modem but do not change the ril or you will have more problems.
There have been reported problems with the modem in certain areas.
Click to expand...
Click to collapse
Thank you for your reply, what modem would you recommend? Maybe you have a link for me?
Btw, now I'm on JoelDroid S2 XXLSJ V 2.1 ROM and no call crashes at all
But I still want to use Neat Rom Lite, is more customizable but I'm afraid I will have the same call crash.
I will give him a second chance
adrianonimus said:
Hi,
I'm a new member :fingers-crossed: and a new noob, that's how you call it here :highfive:
I have a lot of ROM's flashed (ICS and JB).
Maybe I'm the only one with this bug but that's my story:
I tried a few Jelly Bean 4.1.2 ROM's (NeatRom, NeatRom Lite and Simplistic), but on each ROM I had the same bug, if I receive a call or I'm calling someone after exactly 1 minute the call was broken suddenly!!!!!!
Each time I've done full wipe before flashing and tried to see in the settings if something is wrong but no idea at all.
Now I'm back to the Dilidroid ICS and everything it works well.
Also I tried the Pffitech 1.1.3 JB and it works, so no broken calls after 1 minute.
Does someone had the same bug? Could be a kernel issue?
Or maybe some idea what went wrong?
Now I'm gonna try also JoelDroid S2 2.1 ROM, who knows maybe I have luck and no call issues.
Thank you for your help, appreciated :good:....oh btw, sorry for my poor english
My phone:
Samsung Galaxy GT-I9100
Baseband version:I9100XXLS6
Kernel: 3.0.34-Siyah-v.3.3.24
Build number: Dilidroid ICS R4.1 UHLPS
Click to expand...
Click to collapse
Your problem has nothing to do with modem version.
I once had this problem which i solved by reunlocking my sim card then i disabled the minute beep in call settings which was the real culprit.
Envoyé depuis mon GT-I9100 avec Tapatalk
Hey can you say where are you from. When I back home I will check modem for your contury
Send form Galaxy S2. But I don't have it :-\
I am using NeatROM Lite v4.0 for 2 weeks now and i dont get any problems
have you tried
to format the system, a factory reset and a reinstall? worked wonders an my s2
I repeat, just disable the minute beep in call settings
Like googy_anas said: minute beep in call settings
Mr.KiLLeR said:
I am using NeatROM Lite v4.0 for 2 weeks now and i dont get any problems
Click to expand...
Click to collapse
I like the Neat ROM's but I have downloaded the last Lite version 4.0 four times from different places but in the font settings I have only 2 font options, not 5-6 like here, for example there is no cool jazz font
Btw: In the stock Neat ROM (not Lite) the fonts are there.
Maybe someone has an idea why?
I'm the first one who saw this only? Could be but then please give me a link where the Neat Lite ROM has all the fonts option, thx.
Mr.KiLLeR said:
I am using NeatROM Lite v4.0 for 2 weeks now and i dont get any problems
Click to expand...
Click to collapse
Cosmic Blue said:
It would not be a kernal issue, but a modem issue.
Try another modem but do not change the ril or you will have more problems.
There have been reported problems with the modem in certain areas.
Click to expand...
Click to collapse
googy_anas said:
Your problem has nothing to do with modem version.
I once had this problem which i solved by reunlocking my sim card then i disabled the minute beep in call settings which was the real culprit.
Envoyé depuis mon GT-I9100 avec Tapatalk
Click to expand...
Click to collapse
chomsky101 said:
to format the system, a factory reset and a reinstall? worked wonders an my s2
Click to expand...
Click to collapse
Paulius7 said:
Like googy_anas said: minute beep in call settings
Click to expand...
Click to collapse
Thank you very much guys :good:
I have disabled the minute beep in call settings and now no call crash!!!!!!!! :fingers-crossed:
Now I'm using Disaster ROM v.5, very smooth and working good :highfive:
Btw, for that minute beep there is no solution yet?
adrianonimus said:
Thank you very much guys :good:
I have disabled the minute beep in call settings and now no call crash!!!!!!!! :fingers-crossed:
Now I'm using Disaster ROM v.5, very smooth and working good :highfive:
Btw, for that minute beep there is no solution yet?
Click to expand...
Click to collapse
No solution yet ... let's hope the final sammy release will solve ALL the issues
Hi guys! i just have rooted my galaxy s2, kernel siyah, and i have a problem with my home button it doesnt respond and if click on it 4 times i think the screen becomes neutral. help me please!!!!
0xx_Linux_ said:
Hi guys! i just have rooted my galaxy s2, kernel siyah, and i have a problem with my home button it doesnt respond and if click on it 4 times i think the screen becomes neutral. help me please!!!!
Click to expand...
Click to collapse
Did u flash a rom/kernel?
If yes try to flash it again.
If it not works, do it again.
If u didn't change anything u can try a factory reset (backup first!),
but it also can mean that ur device has a hardware defect.
Much success
CHEERS
It musn't be hardware problem, because the 4x home button feature is a natural feature on Siyah kernel. I used official AOKP, and the home button didn't responded too, so maybe it will be the problem, but I don't know how to solve the AOKP problem Maybe they will release a patch.
Re: Problem with home button </noob>
Did you run dorimanx before that?
Sent from my gt-9100 powered by dorimanx
You can thank me if i helped you
Re: Problem with home button </noob>
EverByte said:
It musn't be hardware problem, because the 4x home button feature is a natural feature on Siyah kernel. I used official AOKP, and the home button didn't responded too, so maybe it will be the problem, but I don't know how to solve the AOKP problem Maybe they will release a patch.
Click to expand...
Click to collapse
That's why I ask the question I asked, first
CHEERS
Sent from my GT-I9100 with RootBox
Re: Problem with home button </noob>
Ockay first of all, i m running on stock rom, and i'm gonna flash dorimanx soon to see.
on my s2 i9100 after installing jellysnap v 5.5 the screen decreased from the sides
I went back to stock firmware 4.1.2 but still have the problem
ahmed mo said:
on my s2 i9100 after installing jellysnap v 5.5 the screen decreased from the sides
I went back to stock firmware 4.1.2 but still have the problem
Click to expand...
Click to collapse
really ? and even after flashing stock fw didn't fixed it
sorry mate but it may be a hardware problem
did you used any app for changing something at the screen , color , density etc...
cuz i never heard of this problem before
Christian Nothing said:
really ? and even after flashing stock fw didn't fixed it
sorry mate but it may be a hardware problem
did you used any app for changing something at the screen , color , density etc...
cuz i never heard of this problem before
Click to expand...
Click to collapse
I don't think it's hardware problem it didn't appears until installing the rom and I saw someone suffers from this problem after using the same rom
no I didn't use any app for screen
ahmed mo said:
I don't think it's hardware problem it didn't appears until installing the rom and I saw someone suffers from this problem after using the same rom
no I didn't use any app for screen
Click to expand...
Click to collapse
really ?
ok try to make a clean install with the newer version 6 , i provided in OP an zip to get the same ui as v5.5 , but really who suffered from the same problem ?
if you can point me to that user thread
Christian Nothing said:
really ?
ok try to make a clean install with the newer version 6 , i provided in OP an zip to get the same ui as v5.5 , but really who suffered from the same problem ?
if you can point me to that user thread
Click to expand...
Click to collapse
ok I'll try
I cant't point because it was in other site not here
thank you
ahmed mo said:
ok I'll try
I cant't point because it was in other site not here
thank you
Click to expand...
Click to collapse
ok mate
i'm just surprised to hear that this problem happened to other men using v5.5 , in fact v5.5 isn't so stable , that's why i did my best to make v6 stable as rock