Getting annoyed finding my phone off in my pocket. Is there anything I can do that will prevent the power off option from being displayed while the phone is locked, or is there a software shortcut I could use if I disable the dialog appearing on long press?

Originally Posted by JDog2pt0

Getting annoyed finding my phone off in my pocket. Is there anything I can do that will prevent the power off option from being displayed while the phone is locked, or is there a software shortcut I could use if I disable the dialog appearing on long press?

Wait, in your pocket you manage to long press power, and then tap on the screen to turn the phone? That's quite a feat indeed...

I'll poke around, not sure what options are out there. Are you sure the battery isn't just dying? That really does seem difficult to perform in your pocket.

Originally Posted by arrrghhh

Wait, in your pocket you manage to long press power, and then tap on the screen to turn the phone? That's quite a feat indeed...

I'll poke around, not sure what options are out there. Are you sure the battery isn't just dying? That really does seem difficult to perform in your pocket.

I've unlocked the phone in my pocket before and started apps. I'm not sure it's turning off, but pressing the power button turns the phone back on. Actually, something just came to mind. Shutting the phone down actually restarts it....I'm not sure what's going on here. If it is the battery, it shouldn't be dying that fast. I posted in the kernel thread asking what I should look for in the logs to make sure my phone is sleeping properly (have pm.sleep_mode=0). So far I haven't had any SOD and the screen wakes up as though the phone is still awake (with =0, =1, =2). But, I've posted all that in the kernel thread so :shrug:

Originally Posted by JDog2pt0

I've unlocked the phone in my pocket before and started apps. I'm not sure it's turning off, but pressing the power button turns the phone back on. Actually, something just came to mind. Shutting the phone down actually restarts it....I'm not sure what's going on here. If it is the battery, it shouldn't be dying that fast. I posted in the kernel thread asking what I should look for in the logs to make sure my phone is sleeping properly (have pm.sleep_mode=0). So far I haven't had any SOD and the screen wakes up as though the phone is still awake (with =0, =1, =2). But, I've posted all that in the kernel thread so :shrug:

Perhaps the battery isn't OEM? I had a Seidio battery in there for a bit, and it was just slightly smaller than OEM. It would consistently fail to make a good contact, and obviously the phone would just shut off. Happened all the damned time when I would slide the keyboard closed, I thought it was a hardware issue. Well it was, just not the kind of hardware issue I was thinking . Make sure the batt is snug...

Other than that, I can't think of anything. I don't know how you're unlocking the phone in your pocket either, that's also quite impressive. As for shutdown causing a reboot, that's not consistent... and at this moment I can't remember all the details, but I think the .35+ kernels behave differently than the .27 kernels in this respect. I haven't played with shutdown/restart in a while tho.

Just a quick message of support, particularly arrrghhh and detule I see a lot here Devs efforts continue to be appreciated

Been running this for a couple of weeks now. I really don't think it likes my radio. Texts will sometimes come back as unsent, retrying usually "fails" too. Then I get told I just sent a bunch of the same message haha

Phone calls also not brilliant, a lot of times, dialing ends up in near-instant failure but the call seems to continue without the phone's knowledge. Then I dial again and sometimes end up with two calls to the same person occuring at the same time. Sometimes it will lose signal for no reason until a reboot. When in a call the quality is good if not a little quiet, but seems to drop calls more than with WinMo. (used CSV's from one of Jackos's latest 6.5.3 ROMs) Oh yeah and battery life is terrible SODs but only every few days. GPS seems to work well but battery only lasts half a walk haha, wifi is great, not really played with bluetooth although it turns on & off fine Can't remember the last time I had an app crash on me but half of shutdowns freeze just at the point you would expect poweroff.

Not sure whether I will stick with it or go back to WinMo - the battery life is a killer although my 2 - 3 year old RHOD100 is still on it's original battery

Anyway I will GetLogs if that is useful. Is there much generated as I would be inclined to go through it & remove any personal details before sending. Just adding my support and 2p anyway On a GSM RHOD100 UK o/c to 714, 2011-12-30 GBX0B, class 6 microSD, radio 4.49.25.91, linux 3.2.9-gf38316d, updated non-ap wifi firmware & data on ext4.

Keep it up guys

Originally Posted by MadBeef

Just a quick message of support, particularly arrrghhh and detule I see a lot here Devs efforts continue to be appreciated

Been running this for a couple of weeks now. I really don't think it likes my radio. Texts will sometimes come back as unsent, retrying usually "fails" too. Then I get told I just sent a bunch of the same message haha

Phone calls also not brilliant, a lot of times, dialing ends up in near-instant failure but the call seems to continue without the phone's knowledge. Then I dial again and sometimes end up with two calls to the same person occuring at the same time. Sometimes it will lose signal for no reason until a reboot. When in a call the quality is good if not a little quiet, but seems to drop calls more than with WinMo. (used CSV's from one of Jackos's latest 6.5.3 ROMs) Oh yeah and battery life is terrible SODs but only every few days. GPS seems to work well but battery only lasts half a walk haha, wifi is great, not really played with bluetooth although it turns on & off fine Can't remember the last time I had an app crash on me but half of shutdowns freeze just at the point you would expect poweroff.

Not sure whether I will stick with it or go back to WinMo - the battery life is a killer although my 2 - 3 year old RHOD100 is still on it's original battery

Anyway I will GetLogs if that is useful. Is there much generated as I would be inclined to go through it & remove any personal details before sending. Just adding my support and 2p anyway On a GSM RHOD100 UK o/c to 714, 2011-12-30 GBX0B, class 6 microSD, radio 4.49.25.91, linux 3.2.9-gf38316d, updated non-ap wifi firmware & data on ext4.

Keep it up guys

Just curious, do you have any of these seemingly radio related issues on FRX07.1? I've noticed several people reporting issues that are service/phone call related - jonners, hyc to name a few...

Originally Posted by arrrghhh

Just curious, do you have any of these seemingly radio related issues on FRX07.1? I've noticed several people reporting issues that are service/phone call related - jonners, hyc to name a few...

Don't know, haven't really played with FRX07.1 in any depth. Will do a basic install now and let u know.

Phone calls also not brilliant, a lot of times, dialing ends up in near-instant failure but the call seems to continue without the phone's knowledge. Then I dial again and sometimes end up with two calls to the same person occuring at the same time.

Matches my experience.

Originally Posted by MadBeef

Don't know, haven't really played with FRX07.1 in any depth. Will do a basic install now and let u know.

Just sent and received a text now, no problems so far. Gonna try a call or two. Wi-fi did seem a little fidgety but everything seems fine so far.

Should have mentioned earlier that once with GBX0B the signal went AWOL, reboot didnt cure it, I had to boot into WinMo, disable then enable airplane mode (I leave it set to enabled so I dont pick up any texts in WinMo) then boot back into GBX0B before I got signal back. Only happened once and cant remember what kernel I was using at the time, sorry.

---------- Post added at 10:55 PM ---------- Previous post was at 10:39 PM ----------

Wow haha ... just tried calling voicemail with FRX07.1

Seems to initiate calls just fine, bringing up the dial pad caused the external speaker to start buzzing like when u leave a phone next to a speaker, other times it would go into a kind of speakerphone mode. Similar thing happens if u press speakerphone.

Just had one text fail on me. Not looking good for FRX07.1 either from here.

Originally Posted by MadBeef

Just sent and received a text now, no problems so far. Gonna try a call or two. Wi-fi did seem a little fidgety but everything seems fine so far.

Should have mentioned earlier that once with GBX0B the signal went AWOL, reboot didnt cure it, I had to boot into WinMo, disable then enable airplane mode (I leave it set to enabled so I dont pick up any texts in WinMo) then boot back into GBX0B before I got signal back. Only happened once and cant remember what kernel I was using at the time, sorry.

---------- Post added at 10:55 PM ---------- Previous post was at 10:39 PM ----------

Wow haha ... just tried calling voicemail with FRX07.1

Seems to initiate calls just fine, bringing up the dial pad caused the external speaker to start buzzing like when u leave a phone next to a speaker, other times it would go into a kind of speakerphone mode. Similar thing happens if u press speakerphone.

Just had one text fail on me. Not looking good for FRX07.1 either from here.

Really never had that much problems on FRX07.1 using a Rhod400 other than an occasional missed call because I couldn't answer in time because the UI would not let me or didn't start ringing the phone until 5-6 rings into it on the other end. GBX0B I have all the problems you describe phone call wise.

I have found a solution or work around on the no signal issue. If I boot into android and it never gives me a signal, I usually can't initiate airplane mode it just hangs(won't show the airplane icon), but I hit it anyway, then run an Kexec instead of restarting the phone, and then android pops up in Airplane mode and I can reactivate the radio and it comes up fine, without actually having to boot back into WM.

I noticed when I was in the mountains with low to no signal that after not having a signal for a significant amount of time (more than 10 minutes or so), it will never get back signal, or if it gets back signal data fails no matter what while voice will still work. I can easily fix that by either toggling airplane mode on and off or turning off and back on data. I never mentioned the issue because there are more important things for the remaining programmers to fix than to concentrate on this minor thing which I hardly ever have happen since most of the time I am always in areas with great signal! :) Was hoping someone would figure out the phone.apk issues to at least get it as good as FRX07.1 was!