rubiX Focused 1.8.9/1.9.3

[NattyBee]

ok, I don't recall reading anyone else with this bug, but if it's been reported and I missed it, I apologize:
I've noticed that the in-call tilt sensor isn't acting right, meaning: when I'm on the phone, the screen turns off when I hold the phone to my ear, but-when the phone is tilted to, let's say, 45 degrees or so, the screen turns back on, and then I unknowingly hit the "mute" with my ear/cheak/whatever, or I end the call that way too...I hold the phone with my shoulder while my hands are busy, very often. Tonight alone I hung up on my girlfriend about 5 times due to this...
I remember pretty much all the D1 Froyo roms had this issue, except Simply Stunning and 1 or 2 others (or so), but I didn't notice it on Focused 1.6 or 1.8.6....can anyone else confirm/replicate this issue?

 

[Inkarnit]

So tonight I successfully walked my girlfriend through installing rubiX 1.8.9 on her X via skype (she's in AZ, I'm in VA). She's all excited about her "new phone."

Swyped from my Droid X using DroidForums App

 

[sephtin]

ok, I don't recall reading anyone else with this bug, but if it's been reported and I missed it, I apologize:
I've noticed that the in-call tilt sensor isn't acting right, meaning: when I'm on the phone, the screen turns off when I hold the phone to my ear, but-when the phone is tilted to, let's say, 45 degrees or so, the screen turns back on, and then I unknowingly hit the "mute" with my ear/cheak/whatever, or I end the call that way too...I hold the phone with my shoulder while my hands are busy, very often. Tonight alone I hung up on my girlfriend about 5 times due to this...
I remember pretty much all the D1 Froyo roms had this issue, except Simply Stunning and 1 or 2 others (or so), but I didn't notice it on Focused 1.6 or 1.8.6....can anyone else confirm/replicate this issue?

Awesome! That Anti-Significant-Other feature that drod implemented is working perfectly!

j/k. This is the first time I've hard of this for Focused. Looks like perhaps another bug that Focused and Fission share?
Issue 27 - fission-rom - Screen turns on during calls - Project Hosting on Google Code

I'll have to test. Anyone else that can confirm this? If so, I'll add to the list of known issues.

 

[DJSketch]

Same thing here. Is that normal?

Other than that, so far so good. Thanks Drod

Sorry I want to bump this one more time.

Is it possible the install did not take? I want to know before I install Black Juice again.

It will report in about phone as 1.8.6. If you are unsure which version you have, you should be able to tell by the new transition animations. If you still can't tell, open a terminal and type:

su
cat /proc/sys/vm/dirty_ratio

If it comes back as 95, then you've got 1.8.9 loaded.

I tried that in the terminal emulator an it came back not found? An suggestion on why?

Sent from my DROIDX

 

[DJSketch]

Sorry I want to bump this one more time.

Is it possible the install did not take? I want to know before I install Black Juice again.

It will report in about phone as 1.8.6. If you are unsure which version you have, you should be able to tell by the new transition animations. If you still can't tell, open a terminal and type:

su
cat /proc/sys/vm/dirty_ratio

If it comes back as 95, then you've got 1.8.9 loaded.

I tried that in the terminal emulator an it came back not found? An suggestion on why?

Sent from my DROIDX

Nvm mind dayumm my fat fingers!
This one is amazing loving it.

Sent from my DROIDX

 

[superleon]

I tried rubix1.8.9 from blurry 1.5.2. Rubix 1.8.9 is fastest rom I have used.
But I have a little problem,I can't find install-recovery.sh in /etc or /system/etc. I need this file to auto run a program since the phone boots.
I tried to create /etc/install-recovery.sh ,but it wouldn't run at all.
Has rubix1.8.9 got another way to run some scripts since boots?
Thanks.

 

[sephtin]

I tried rubix1.8.9 from blurry 1.5.2. Rubix 1.8.9 is fastest rom I have used.
But I have a little problem,I can't find install-recovery.sh in /etc or /system/etc. I need this file to auto run a program since the phone boots.
I tried to create /etc/install-recovery.sh ,but it wouldn't run at all.
Has rubix1.8.9 got another way to run some scripts since boots?
Thanks.

Install-recovery.sh conflicted with jrummy's OC app, I believe (was overwritten when installing his app.. ?).

Try looking into /system/etc/init.d/
or /system/usr/bin

 

[droidxchat]

ok, I don't recall reading anyone else with this bug, but if it's been reported and I missed it, I apologize:
I've noticed that the in-call tilt sensor isn't acting right, meaning: when I'm on the phone, the screen turns off when I hold the phone to my ear, but-when the phone is tilted to, let's say, 45 degrees or so, the screen turns back on, and then I unknowingly hit the "mute" with my ear/cheak/whatever, or I end the call that way too...I hold the phone with my shoulder while my hands are busy, very often. Tonight alone I hung up on my girlfriend about 5 times due to this...
I remember pretty much all the D1 Froyo roms had this issue, except Simply Stunning and 1 or 2 others (or so), but I didn't notice it on Focused 1.6 or 1.8.6....can anyone else confirm/replicate this issue?

Awesome! That Anti-Significant-Other feature that drod implemented is working perfectly!

j/k. This is the first time I've hard of this for Focused. Looks like perhaps another bug that Focused and Fission share?
Issue 27 - fission-rom - Screen turns on during calls - Project Hosting on Google Code

I'll have to test. Anyone else that can confirm this? If so, I'll add to the list of known issues.

lol.... it's a proximity sensor and not a tilt sensor that triggers the screen turn off. the proximity sensor is near the phone led. it sounds like you're not keeping your head close enough to it since you hold it with your shoulder (recipe for dropping it by accident!). or if you hold it to your ear, then tilt it to a 45 degree angle, you're increasing the distance too much btw the top of the phone (where the sensor is) and your head. thats why the screen will turn back on.

additionally, tilting it too much will allow for light to pass through horizontally where the speaker is too... it's pretty sensitive. you can test this out just by calling vmail and holding your finger over the proximity sensor then tilting it. the screen will stay off all the way to 0degrees(horizontal) if you keep your finger over the speaker part too...

 

[droidxchat]

I tried rubix1.8.9 from blurry 1.5.2. Rubix 1.8.9 is fastest rom I have used.
But I have a little problem,I can't find install-recovery.sh in /etc or /system/etc. I need this file to auto run a program since the phone boots.
I tried to create /etc/install-recovery.sh ,but it wouldn't run at all.
Has rubix1.8.9 got another way to run some scripts since boots?
Thanks.

Creating install-recovery.sh should work. Additionally, you can install jrummy's app to put it there, but as sephtin said, anything you put inside of the script will be overwritten anytime you change your boot OC settings (however, if you're just going to set OC boot settings, and then not touch them again, you will be fine with modifying the script).

Here is what I would suggest though... firstly, it sounds like your command isn't working in the first place. Test it out in terminal emulator, because if it is working then simply creating an install-recovery.sh with the command SHOULD have worked.

After you get the command working, put it into /system/bin/startup_smc.sh (throw it all the way at the bottom) <<trade secret

 

[sephtin]

ok, I don't recall reading anyone else with this bug, but if it's been reported and I missed it, I apologize:
I've noticed that the in-call tilt sensor isn't acting right, meaning: when I'm on the phone, the screen turns off when I hold the phone to my ear, but-when the phone is tilted to, let's say, 45 degrees or so, the screen turns back on, and then I unknowingly hit the "mute" with my ear/cheak/whatever, or I end the call that way too...I hold the phone with my shoulder while my hands are busy, very often. Tonight alone I hung up on my girlfriend about 5 times due to this...
I remember pretty much all the D1 Froyo roms had this issue, except Simply Stunning and 1 or 2 others (or so), but I didn't notice it on Focused 1.6 or 1.8.6....can anyone else confirm/replicate this issue?

Awesome! That Anti-Significant-Other feature that drod implemented is working perfectly!

j/k. This is the first time I've hard of this for Focused. Looks like perhaps another bug that Focused and Fission share?
Issue 27 - fission-rom - Screen turns on during calls - Project Hosting on Google Code

I'll have to test. Anyone else that can confirm this? If so, I'll add to the list of known issues.

lol.... it's a proximity sensor and not a tilt sensor that triggers the screen turn off. the proximity sensor is near the phone led. it sounds like you're not keeping your head close enough to it since you hold it with your shoulder (recipe for dropping it by accident!). or if you hold it to your ear, then tilt it to a 45 degree angle, you're increasing the distance too much btw the top of the phone (where the sensor is) and your head. thats why the screen will turn back on.

additionally, tilting it too much will allow for light to pass through horizontally where the speaker is too... it's pretty sensitive. you can test this out just by calling vmail and holding your finger over the proximity sensor then tilting it. the screen will stay off all the way to 0degrees(horizontal) if you keep your finger over the speaker part too...

Bleh, should have thought of that.
In THAT case.. this could be caused by a build.prop tweak. The stock setting, is 450 for how long the prox sensor takes to bring the screen back.
Beesley's tweaks include changing this to 150, so it's more sensitive.

To resolve, probably changing the 150, to the stock setting of 450 would probably make a big difference in your situation??
Just move build.prop to sdcard, edit, and move it back (mounting RW before you copy it back in).. then reboot.. give that a shot...

#Proximity sensor debounce time
mot.proximity.delay=150
# disable touch below 60 pixels
mot.proximity.distance=60

 

[droidxchat]

alright... this 3g hotspot thing is pissing me off.. i dont even use it, i just want to fix it because its so elusive... i spent like 4 hours today trying but the problem is too deeply tied into the android system

 

[sbkillz]

Can someone please post another link or the zip file for 1.8.9. Link is dead for me :frown:

 

[droidxchat]

Drod! It's too easy to find your security measures with just the search feature of any file manager and Changeset Viewer or Colored Diffs. Ima cook up something better for you i have a good idea. In the mean time you should put those [retracted] into comments within essential system files rather than standalone files and then use a file date changer on em so that a thief at least wouldnt know where to look (although you can't hide filesize). Another idea is just create a custom string only you know and MD5 it, add it to a script where the line is never even called (but hard to notice).

Can someone please post another link or the zip file for 1.8.9. Link is dead for me :frown:

yah its down for me too... i dont have the file to upload at the moment

 

[randyb69]

What kind of scores are you getting in quadrant? I read back a few pages that the scores are low on this release, but overclocked I'm getting 1060 or so. Is that about right? Previous roms were 1400+

Sent from my DROIDX using DroidForums App

 

[NattyBee]

ok, I don't recall reading anyone else with this bug, but if it's been reported and I missed it, I apologize:
I've noticed that the in-call tilt sensor isn't acting right, meaning: when I'm on the phone, the screen turns off when I hold the phone to my ear, but-when the phone is tilted to, let's say, 45 degrees or so, the screen turns back on, and then I unknowingly hit the "mute" with my ear/cheak/whatever, or I end the call that way too...I hold the phone with my shoulder while my hands are busy, very often. Tonight alone I hung up on my girlfriend about 5 times due to this...
I remember pretty much all the D1 Froyo roms had this issue, except Simply Stunning and 1 or 2 others (or so), but I didn't notice it on Focused 1.6 or 1.8.6....can anyone else confirm/replicate this issue?

Awesome! That Anti-Significant-Other feature that drod implemented is working perfectly!

j/k. This is the first time I've hard of this for Focused. Looks like perhaps another bug that Focused and Fission share?
Issue 27 - fission-rom - Screen turns on during calls - Project Hosting on Google Code

I'll have to test. Anyone else that can confirm this? If so, I'll add to the list of known issues.

lol.... it's a proximity sensor and not a tilt sensor that triggers the screen turn off. the proximity sensor is near the phone led. it sounds like you're not keeping your head close enough to it since you hold it with your shoulder (recipe for dropping it by accident!). or if you hold it to your ear, then tilt it to a 45 degree angle, you're increasing the distance too much btw the top of the phone (where the sensor is) and your head. thats why the screen will turn back on.

additionally, tilting it too much will allow for light to pass through horizontally where the speaker is too... it's pretty sensitive. you can test this out just by calling vmail and holding your finger over the proximity sensor then tilting it. the screen will stay off all the way to 0degrees(horizontal) if you keep your finger over the speaker part too...

I am aware that the proximity sensor is what turns phone off, but if I hold phone with my hand and tilt my head to this angle (keeping phone firmly pressed to my head) I still encounter the issue...I'll double check this situation again when I have a chance, for now I gotta get to work...
**edit** I'll try the finger over the sensor test when I have a chance as well.