Related
i saw a post about ringer delay for AT&T user and they just need to disable the dialer and the problem solve but what about us sprint users? Here is the original post about that http://forum.xda-developers.com/showthread.php?t=449417
i tried to disable the dialer on registry but still get 2-3 second delay before my Touch Pro actually ring.
Download and install DiamondTweaks. There is an option to disable the ringer delay. Works well.
convert your ringer to .wav file
temperamentalman said:
Download and install DiamondTweaks. There is an option to disable the ringer delay. Works well.
Click to expand...
Click to collapse
The ringer delay that this changes is the pause between when the ringtone ends and it repeats. Not the delay from when the LED starts flashing (because a call arrived) till the phone actually starts ringing.
If you wish to turn off the HTC dialer and use the WM Dialer, simply goto the following registry entry,
[HKEY_LOCAL_MACHINE/Security/Phone/Skin]
"Enabled" = dword:1change the Enabled value from 1 to 0 which will disable the HTC dialer.
I vote for converting to WAV files as well.
If you would like to complain to Sprint about it, the following is the thread I started on Sprint's forum regarding this very subject.
http://forums.buzzaboutwireless.com/baw/board/message?board.id=SmartPhones&thread.id=5304
Thanks smotrs...
Know anyway to get the light sensor to turn off the screen when on a call (Sprint) other than S2U2?
temperamentalman said:
Thanks smotrs...
Know anyway to get the light sensor to turn off the screen when on a call (Sprint) other than S2U2?
Click to expand...
Click to collapse
Depends on what you may have done (adding programs, etc..) to your phone. By default, our devices will turn the screen off to conserve battery while a call is in session. However, if you have added one of the S2A dialer GSM versions which was taken from the Touch HD, that feature was disabled because of the InCall curtain. The CDMA versions (my signature and others) were taken from the Sprint Diamond ROM that was released and still contains the necessary code to turn off the screen display while the call is in progress.
Smotrs...just HR'd and installing now. I haven't tried that one, and actually think I ended up with the GSM version I WAS using.
I'll let you know how it works.
Thanks...
Well, it still sits there while the screen "times" out. I thought the light sensor was supposed to dim the screen almost immediately. I'm on the call for 30-40 seconds before it dims, and then cuts off.
Is this a Sprint thing?
temperamentalman said:
Well, it still sits there while the screen "times" out. I thought the light sensor was supposed to dim the screen almost immediately. I'm on the call for 30-40 seconds before it dims, and then cuts off.
Is this a Sprint thing?
Click to expand...
Click to collapse
It should Dim after about 10 seconds (or whatever you have in the backlight Advanced setting under Battery). After about 40 seconds or so (same location) it should turn off the screen.
At least that's what mine does, just verified it again. Sounds like maybe your values are too high. After a HR they usually are by default.
Somehow it was at 30 (dim) and 1 min (off). That is a little high. Changed it to 10 / 40. We'll see what that does.
Thanks for the tip. I'll keep you posted.
Seems to now be working the way you explained!!! Thank you for the help!
Is there anything else out there, other than S2U2 that allow FULL SCREEN Caller ID pictures??? I don't want to reinstall that because the dialer is actually working right. I just miss full screen caller ID.
Thanks again.
That I don't know, sorry.
Eh...it's ok. I'd much rather have a dialer that works than a full screen picture of my ignorant brother.
you can also change the Slot Cycle Index in the epst settings... you'll need your MSL though
it's under "Modem Settings"
What is slot cycle and where are these settings? How do I find my MSL? I don't see "Modem Settings".
not trying to be an ass, but i suggest you do some searching. there is plenty of info on the subject
check out this thread - http://forum.ppcgeeks.com/showthread.php?t=48775&highlight=epst+poll
or here - http://forum.ppcgeeks.com/showpost.php?p=625185&postcount=14
and here - http://forum.ppcgeeks.com/showthread.php?t=42730&highlight=epst+poll
I don't think you are an ass...I'm thinking thanks for the threads!
I know search is my friend LOL
lol, no prob man...
Changed the SCI to 1. We'll see if that helps. There is always "0"!
I'm also seeing mixed reports/opinions on ACCOLC - Access Overload Class. Mine was defaulted at 8 on Sprint. People say leave it alone. People say set it lower. Others say set it higher.
i found that setting SCI to 1 is good enough, i'm able to catch my calls and haven't noticed decreased battery life from it so that's where mine stays.
Just wondering, did anyone else notice that when you try going to max brightness (from settings->display) it only goes to 99%? And if you try going to 100% with widgets, the screen gets brighter all the way till 99% and then when it hits 100 it gets a lot dimmer
Anyone else noticed this? Or is this bug specific to my poor unrooted X10a ?
I went to the Setting -> Display and Un-check Auto but I did not get the % scale, it just a scroll bar without any number in it, but it went all the way up and down as well. Maybe depends on the firmware in the phone...
roaringhere said:
I went to the Setting -> Display and Un-check Auto but I did not get the % scale, it just a scroll bar without any number in it, but it went all the way up and down as well. Maybe depends on the firmware in the phone...
Click to expand...
Click to collapse
Yea you can't see the number over there.. you need a widget for that. But if you slide it to the maximum possible, and then look at the number in a widget(I've tried 4 so far, so its not a widget problem) it says 99%, if you make that 100 through the widget, it dims.
I guess SE knew this and made the max brightness 99%?
Yea it happens to me too. I use Quick settings and when I slide to 100%, it dims. But it's not really a big deal cuz I set my phone at 18-20%. Saves a lot of battery
same here ...
100% is just like 10%
Yes i noticed that to! I was looking for a widget to controll backlight, found one that looked pretty and got a bit sad couse i thought it was faulty for not working correct so i uninstalled it. Nice to know the reason for why things not work
Sent from my X10i using XDA App
I used to use s.e. W810, recently switched to xperia mini. Everything is pretty nice but the vibration level. It's barely sensible. When I have my phone in my jean pocket switched to silent mode, I feel nothing and when I check it to see whether there is any notification, usually I got ,say, 3 messages and 2 missing call
So, it's obvious that I don't feel the vibration. Searched a little about it, but neither could find anyone suffers from that problem like I do nor a solution to increase vibration level. However thought that maybe by reaching the phone's system files that can be feasible. So, is it possible to do that, if so, how ?
Thanks in advance.
I've not had a problem with it, but there are also apps to allow you to make your own vibration patterns. So maybe something with a bit more stop/start would help?
melenko said:
I've not had a problem with it, but there are also apps to allow you to make your own vibration patterns. So maybe something with a bit more stop/start would help?
Click to expand...
Click to collapse
Thanks for your suggestion but the problem is not the pattern but the level of the vibration definitely. I compared it with other phones and it's really not that high like old phones.
Go sms pro can help you define how many miliseconds the vibration for a notification for a new text should last. haven't used any app which can do the same for incoming calls, but it should exist somewhere in the market!
Actually what I'm looking for is to be able to increase the power of the motor inside the phone which creates those vibrations. This is adjustable for sure, cause for instance as typing it vibrates very slowly. So, by playing with codes they can be achieved, at least as theoretically
This ROM is working very well on my UK Rhod 100. Very stable & fast and since the latest update I have the correct HW keyboard layout. Battery life is limited but carrying a second battery is an easy solution.
The previous problems where the screen would not turn on after several pushes of the power button almost never occurs. However when the battery runs down to about 30% the screen always changes such that a red overlay occurs visible mainly on screens with a white background (see pics). Also when the screen changes ghost images remain from previous screens. Also at this point sometimes the screen will not turn on despite repeated use of the power button. Strangley, even though there is nothing visible on the screen I can unlock the phone by swiping in the expected area (and get haptic feedback) and long press the power button and turn off the device by pressing in the expected areas. Upon a reboot the screen will initially be back to normal but then if the battery is below 30% the problem will return. These issues never occur if the battery is above 30%. If I take screenshots with shootme the pics captured look normal when viewed after a reboot before the problem recurs. Not sure what the system does when the battery falls to this level but the screen is definitely affected. This problem also occurs with a fresh install with no apps installed.
If anyone has any ideas as to what could be the cause (and even better a solution) it would be most welcome. Thanks to all those behind this project.
Sorry you are having troubles. Unfortunately as noted in the first post for that thread we only have RHOD400s to test with. No one else has reported any similar issues. The 100s are known to be the problem children of the RHOD family. If you come up with a fix let us know, and we will try to include it in any future releases.
wizardknight said:
Sorry you are having troubles. Unfortunately as noted in the first post for that thread we only have RHOD400s to test with. No one else has reported any similar issues. The 100s are known to be the problem children of the RHOD family. If you come up with a fix let us know, and we will try to include it in any future releases.
Click to expand...
Click to collapse
Did you look at ACL's work on RE'ing that panel code...?
He said something about the panel power up/power down sequence on the 100's (the AUO panel specifically) to be quite a bit different.
arrrghhh said:
Did you look at ACL's work on RE'ing that panel code...?
He said something about the panel power up/power down sequence on the 100's (the AUO panel specifically) to be quite a bit different.
Click to expand...
Click to collapse
arrrghhh, I noted your post in the ROM development thread regarding the start up sequence in the OMGB kernel for the AUO panel. Perhaps this would solve my issue as well. If this change could be added to the next edition of this ROM my device would be virtually bug free.
As noted in the thread, we do not have any RHOD100s to test with. It is very unlikely that this will happen. If you would like to make your own kernel with these changes I can post it.
issue or not?
hi,
thanks a lot, first of all.
I've been trying to figure out how to get an Italian keyboard layout.
any suggestion?
-p.
paolora999 said:
hi,
thanks a lot, first of all.
I've been trying to figure out how to get an Italian keyboard layout.
any suggestion?
-p.
Click to expand...
Click to collapse
try using AItype Keyboard Plus which supports multiple languages and keyboard layouts
Sorry I didn't express myself properly. I meant the physical keyboard. In other thread I read something about a startup.txt file, I don't know if it applies to this ROM (and moreover I can't find it).
paolora999 said:
Sorry I didn't express myself properly. I meant the physical keyboard. In other thread I read something about a startup.txt file, I don't know if it applies to this ROM (and moreover I can't find it).
Click to expand...
Click to collapse
startup.txt files are only for the SD card versions of the android roms.
You would need to edit the keyboard map. Here is generic android keyboard map info.
There may be apps out there than can change your keyboard map, but I don't know any details about that.
Also in the future it would be best to start your own thread, rather than using an unrelated one. Better yet, post the questions about the rom you are working with in the thread for that rom.
i am having also a screen problem with that Rom and Kernel:
My screen is not calibrated. When i press it's being pressed on somewhere else on the screen.
P.S.
My RAM is not 100 +- this rom showing me 33 for usage on the device :S.
Can someone help me with those two ?
MTN_Cool said:
i am having also a screen problem with that Rom and Kernel:
My screen is not calibrated. When i press it's being pressed on somewhere else on the screen.
P.S.
My RAM is not 100 +- this rom showing me 33 for usage on the device :S.
Can someone help me with those two ?
Click to expand...
Click to collapse
Did you read the link that covered screen calibration listed under related goodies, or did you search for the threads that cover screen calibration under android? Tell us what you have tried, but didn't work.
No idea what you mean by the ram is not 100.
What the heck is going on here? Is this just the thread to jack?
Let's focus on the display issues please folks, as in your response should be related to the original post.
arrrghhh said:
What the heck is going on here? Is this just the thread to jack?
Let's focus on the display issues please folks, as in your response should be related to the original post.
Click to expand...
Click to collapse
idc if they will move my question the the original one...
but i can't fix my calebration points...every time i need to launch the HTC program :\
Problem resolved?
akk29 said:
This ROM is working very well on my UK Rhod 100. Very stable & fast and since the latest update I have the correct HW keyboard layout. Battery life is limited but carrying a second battery is an easy solution.
The previous problems where the screen would not turn on after several pushes of the power button almost never occurs. However when the battery runs down to about 30% the screen always changes such that a red overlay occurs visible mainly on screens with a white background (see pics). Also when the screen changes ghost images remain from previous screens. Also at this point sometimes the screen will not turn on despite repeated use of the power button. Strangley, even though there is nothing visible on the screen I can unlock the phone by swiping in the expected area (and get haptic feedback) and long press the power button and turn off the device by pressing in the expected areas. Upon a reboot the screen will initially be back to normal but then if the battery is below 30% the problem will return. These issues never occur if the battery is above 30%. If I take screenshots with shootme the pics captured look normal when viewed after a reboot before the problem recurs. Not sure what the system does when the battery falls to this level but the screen is definitely affected. This problem also occurs with a fresh install with no apps installed.
If anyone has any ideas as to what could be the cause (and even better a solution) it would be most welcome. Thanks to all those behind this project.
Click to expand...
Click to collapse
In an attempt to bring this thread back on topic I thought I'd report back that the original problem has not happened for a few weeks. My setup is essentially unchanged, the only change is that I have been using One Power Guard to try and improve battery life, which by the way seems to be effective. Managed 13hours with light use (few calls/occassional data for email web browsing)
Anyway it could be coincidence but it is possible that one of the tweaks performed by the app has sorted this issue. Since nobody else has reported the same problem I'm not sure how useful this info is but hopefully it may be of use to someone.
With my Note 4, it would wake up from Android Doze, or simply not enter that state if there was movement of the phone. I felt stupid needing to pick up my phone every 10 min to give it a small shake, but at least it seemed to work. I keep my phone in my pocket when I'm working outside and that always kept the Note 4 from falling into Doze mode. Not so with the S9+. It drops into Doze even in my pocket. Anyway to stop that from happening? Like others here, I feel frustrated needing to activate my screen to find out if there are notifications.
Brokk said:
With my Note 4, it would wake up from Android Doze, or simply not enter that state if there was movement of the phone. I felt stupid needing to pick up my phone every 10 min to give it a small shake, but at least it seemed to work. I keep my phone in my pocket when I'm working outside and that always kept the Note 4 from falling into Doze mode. Not so with the S9+. It drops into Doze even in my pocket. Anyway to stop that from happening? Like others here, I feel frustrated needing to activate my screen to find out if there are notifications.
Click to expand...
Click to collapse
That's not Doze mode. Doze is when Android puts apps to sleep that are in memory not being used. This is done to save battery (and processing time?).
So what is happening here, if I understand, is that your phone display is going blank when you pull it from your pocket?
Scott said:
That's not Doze mode. Doze is when Android puts apps to sleep that are in memory not being used. This is done to save battery (and processing time?).
Click to expand...
Click to collapse
Doze was originally described as putting your phone into a power saving sleep mode after 20 min of "inactivity". The issue that caused me problems back then was not about the apps, but that notifications pushed to the device were queued up by the system until your phone "woke up", then the notifications would come rolling through. This happened at the system level regardless of app.
Perhaps in the latest version of Android they have changed the definition of Doze, but another poster was having a lot of issues with notifications (mostly email) and the culprit was deemed to be Doze.
Scott said:
So what is happening here, if I understand, is that your phone display is going blank when you pull it from your pocket?
Click to expand...
Click to collapse
No. My display is blank (as it should be) when I put it into my pocket, as well as when I pull it out. I always shut the screen off before putting my phone down, or in my pocket.
If I put my phone in my pocket, and 5-10 min later I get a notification, it comes through loud and clear and I pull my phone out and check it. If 20+ min has gone by without me having a reason to turn the screen on, then I stop getting notifications. When I pull it out to check the time or send a message, suddenly the notifications come rolling through.
Again, I was used to this if the Note 4 was put down, but this behavior is new to me if the phone is moving about.
Brokk said:
Doze was originally described as putting your phone into a power saving sleep mode after 20 min of "inactivity". The issue that caused me problems back then was not about the apps, but that notifications pushed to the device were queued up by the system until your phone "woke up", then the notifications would come rolling through. This happened at the system level regardless of app.
Perhaps in the latest version of Android they have changed the definition of Doze, but another poster was having a lot of issues with notifications (mostly email) and the culprit was deemed to be Doze.
No. My display is blank (as it should be) when I put it into my pocket, as well as when I pull it out. I always shut the screen off before putting my phone down, or in my pocket.
If I put my phone in my pocket, and 5-10 min later I get a notification, it comes through loud and clear and I pull my phone out and check it. If 20+ min has gone by without me having a reason to turn the screen on, then I stop getting notifications. When I pull it out to check the time or send a message, suddenly the notifications come rolling through.
Again, I was used to this if the Note 4 was put down, but this behavior is new to me if the phone is moving about.
Click to expand...
Click to collapse
I concur. Same happens to me.
I don't have this issue at all. I have my phone in my pocket most of the day and don't need to "wake" the phone up for notifications. I can leave my phone unattended for hour or 3 and it still receives the notifications without issues. I don't know if I have turned on a setting that mine works different, but I must say that my battery life isn't that great....as if the phone never sleeps/doze at all
termdj said:
I don't have this issue at all. I have my phone in my pocket most of the day and don't need to "wake" the phone up for notifications. I can leave my phone unattended for hour or 3 and it still receives the notifications without issues. I don't know if I have turned on a setting that mine works different, but I must say that my battery life isn't that great....as if the phone never sleeps/doze at all
Click to expand...
Click to collapse
I'm curious. Do you have any of the power saving modes turned on? Do you use "always on display"?
I never use the power save modes. Aod is on from 5 in the morning till 8 at night
termdj said:
I never use the power save modes. Aod is on from 5 in the morning till 8 at night
Click to expand...
Click to collapse
AoD could be keeping your phone awake, preventing Doze. The power saving features talks about putting apps to sleep, so unless you use them, that could also be disabling Doze. I could try changing the power saving settings, though it seems like a shame. I have zero interesting in AoD for multiple reasons, so it's not worth it for me to use that to solve my problems.
Thanks for the information!
Doze changed in Nougat, I believe, so that motion no longer prevented Doze from working. Since most men, at least, carry their phone in their pocket Doze hardly ever kicked in, greatly limiting its power saving capability.
You can exempt specific apps from Doze if you want to get notifications from them even when dozing.
Settings / Apps / 3 dot menu / special access / Optimize battery usage. Select All Apps from the drop down. Turn off the toggle for any apps you don't want to Doze.
Brokk said:
Doze was originally described as putting your phone into a power saving sleep mode after 20 min of "inactivity". The issue that caused me problems back then was not about the apps, but that notifications pushed to the device were queued up by the system until your phone "woke up", then the notifications would come rolling through. This happened at the system level regardless of app.
Perhaps in the latest version of Android they have changed the definition of Doze, but another poster was having a lot of issues with notifications (mostly email) and the culprit was deemed to be Doze.
No. My display is blank (as it should be) when I put it into my pocket, as well as when I pull it out. I always shut the screen off before putting my phone down, or in my pocket.
If I put my phone in my pocket, and 5-10 min later I get a notification, it comes through loud and clear and I pull my phone out and check it. If 20+ min has gone by without me having a reason to turn the screen on, then I stop getting notifications. When I pull it out to check the time or send a message, suddenly the notifications come rolling through.
Again, I was used to this if the Note 4 was put down, but this behavior is new to me if the phone is moving about.
Click to expand...
Click to collapse
Yes, I am confusing Doze with the Samsung power saving options. Blah!
I know the battery life will decrease with aod, but I have noticed that even without aod on my battery drop 2% per hour, so I leave it on...There are days that I can go 1 day and 8 hours before charging, but then my sot is only 2 hours....In general I'm happy with the battery life
meyerweb said:
You can exempt specific apps from Doze if you want to get notifications from them even when dozing.
Settings / Apps / 3 dot menu / special access / Optimize battery usage. Select All Apps from the drop down. Turn off the toggle for any apps you don't want to Doze.
Click to expand...
Click to collapse
Thanks!
It seems oddly redundant needing to do essentially the same thing in two places. One well advertised under the battery settings, and the other one hidden under settings/apps/special access.
Hopefully this will fix my problems. Glad to know there is a work around.
Brokk said:
Thanks!
It seems oddly redundant needing to do essentially the same thing in two places. One well advertised under the battery settings, and the other one hidden under settings/apps/special access.
Hopefully this will fix my problems. Glad to know there is a work around.
Click to expand...
Click to collapse
The two settings really are doing different things. Samsung's (in the battery settings), puts apps to sleep after 3 to 7 days (depending on your settings). The won't wake up again until you use them. Doze (the pretty much hidden option in Apps), lets the apps wake up on their own, when you start using the phone, even if you don't access those particular apps.
I'm not sure why the Doze setup is buried so deep in settings, though. I guess Google (or Samsung?) really doesn't want you interfering with it.
meyerweb said:
The two settings really are doing different things. Samsung's (in the battery settings), puts apps to sleep after 3 to 7 days (depending on your settings). The won't wake up again until you use them.
Click to expand...
Click to collapse
I made a mistake of putting an app to sleep that I use to keep my screen awake. It uses a widget to toggle it on/off, but will shut off along with the screen if you intentionally shut your screen off. After putting that app to sleep, the widget stopped working. I had to go find the actual app, start it, then quickly flip back to my home screen and click on the widget. I couldn't undo my "sleep" action on that app. I changed it to "unmonitored", so that the S9+ would never put it to sleep. I rebooted. I shut off the power saving options. Nothing worked. Everytime I would go to the widget (unless I just started the actual app), it wouldn't react to clicking on the widget.
I finally gave up and uninstalled the app from my phone. Rebooted. Reinstalled it and now it works fine. So I'm not sure I agree with "puts the app to sleep in 3 to 7 days". Maybe 3-7 minutes...
Well, 3 to 7 days is what Samsung says, and the optional range you can set in the app. Don't know what specifically happened with that widget, though.
meyerweb said:
Well, 3 to 7 days is what Samsung says, and the optional range you can set in the app. Don't know what specifically happened with that widget, though.
Click to expand...
Click to collapse
Where is the setting(s) for optimal range? I don't remember specifying that. I thought it was more of an on/off thing. White listed (unmonitored resource consumption) or black listed (never let it run in the background). Then apps in neither list it reports to you and you can force them to sleep or not.
Brokk said:
Where is the setting(s) for optimal range? I don't remember specifying that. I thought it was more of an on/off thing. White listed (unmonitored resource consumption) or black listed (never let it run in the background). Then apps in neither list it reports to you and you can force them to sleep or not.
Click to expand...
Click to collapse
Samsung does bury things....
Settings / Device maintenance, click Battery at the bottom.
Then click the 3 dot menu at the top, and Advanced Settings.
Tap App power monitor (the text, not the toggle).
Tap Put unused apps to sleep (again, the text).
You can set the slider anywhere between 3 days and 7.
I spent several days just wandering through every settings option I could find after I setup the phone. Discovered all kinds of hidden things. Sometimes I can even remember where I saw them.