Database Develop

Idle screen timer + Voip == Dropped calls.

I have managed to get M$-Voip working, but when the screen goes black so does my call. Also, when the screen goes black no amount of touching keys will bring it back from standby, but if I slide the keyboard unit it will come back out of its crypt ( i think the wifi drops). I had initially installed SPL-1.00-OliPof or what not, and upon discovering that is an old piece of software I upgraded to HardSPL-3.29 [through jumpspl-1.5x] hoping that this would relieve my issue. The SPL upgrade was after a radio upgrade, and the radio upgrade [er downgrade from a 1.7x rom to a 1.6x rom made the camera and phone work ]. At this point, I'm not sure if this is a OS rom issue, or Radio Rom issue. My oem setup had 3.57 within a version number if that is any thing I believe it was for the OS rom, other than that I cannot be sure of anything else. Bringing me to ask, are radio roms for the kaiser dependant upon minor hardware alterations between kaiser models, or are they more dependent on the alterations contained within the software side of things ( SPL's, Os Rom's )?
(I have a at&t tilt 8925 (kais 100) )
Also any suggestions in getting this phone where it should be would be greatly accepted. I am hoping to get the best graphics I can, the best speed I can bargain for, while maintaining the native voip capabiltiy unless someone can recommend a good voip client that integrates well into the phone I tried fring but it doesn't have a keypad [WTF?!] (i.e. your in voice mail and need to press 2 to hear your mail, no keypad makes me feel impotent at such junctures)..But yes right now my main issue is this display-standby problem..
Thank you!
Ty

You could use this DontSleep to stop it going to sleep add it to a hardware button for quick access "Start\Settings\Buttons", you could try and use advanced config but not sure if voip calls are the same as voice.

Yeah maybe I will look into that for an extremely temporary workaround. But, I don't want kill my tilt by pulling the keyboard in and out to see whats up. Seriously it just dies black and stays that ways. so uncool.

tyler51773 said:
Yeah maybe I will look into that for an extremely temporary workaround. But, I don't want kill my tilt by pulling the keyboard in and out to see whats up. Seriously it just dies black and stays that ways. so uncool.
Click to expand...
Click to collapse
Sorry i was under the impression that it only does the black screen during VOIP but your actually having this issue all the time when the phone goes into sleep.

Weird Bugs

Ive installed the latest cyanogen mod rom and i have been using it for a while. There are a few bugs i have noticed through my use of the phone and they are kinda getting annoying.
First of all i have noticed randomly while i am listening to music the music app that came with cyanogen will freeze up and then it will start again but after it does that there is no sound. And when i force close the application, i use the controls on the side of the phone to change the volume and it will only change the media volume not the ringer volume. to fix this when it happens i have been having to restart the phone and go on from there.
Another bug i have been noticing is when i turn the phone to vibrate mode using the controls on the left of the phone when i recieve a text i do not get a notification. I would excpect that it would vibrate as well.
Another one is that when i am listening to music and i recieve a text it will turn off the sound similar to the first bug i talked about. It says it is still playing but there is no sound coming from it. To fix it i have been having to restart the phone.
To listen to my music with my earphones i have an adapter and some times when i am using that the phone will go into a reboot loop until i take out the adapter and then once the phone is back up plug the adapter back in.
These are all quite annoying and i would like to see if you guys have any input on the matter. Thank you

I don't think that any of these are platform bugs, but rather are cyanogen bugs. I suggest you post bug reports to cyanogen's bug tracker.

lbcoder said:
I don't think that any of these are platform bugs, but rather are cyanogen bugs. I suggest you post bug reports to cyanogen's bug tracker.
Click to expand...
Click to collapse
Well i thought about that as well but i looked at the rules for the bug tracker and i am currently in the process of making more accurate bug reports for the bug tracker. I came here to see if i could get any quick fixes or to ask if these are common things or i may just have to format my phone and reinstall cyanogen. So yeah i hope i can get some feedback from other users. I may just have to format as i said but i hope that there could be something else i could do. dont want to just go to all that trouble to not get it fixed.
edit: I looked further into the bug tracker for cyanogen and i dont have the required materials to make a report as i dont have a log of the issue. its just something that tends to happen.

Its happening alot today and well yeah its getting really bad, i dont think there is anything wrong with my phone. So i think i am just going to format and reinstall a new rom. idk if i will stay cyanogen or not. anyone have any recomendations for the rom i should install?

Super D is pretty awesome. It's an improvement on the Cyan roms. So you get Cyan plus some extras.

Could i get a link to the correct version i should use?

Yep here is the link for Super D

thank you installed it and i am no longer having any issues. Wonderful

[HELP] my touch screen of milestone is crash

my touch screen was crazy when I get my phone out of my pants. I did not touch the screen but it still automatically run the app and drag the taskbar up and down .........

nobody is like me???

care to share more details and/or what ROm you're running? 2.2?

it happened randomly to me too, with any rom 2.1 2.2, but I still didn't figure the reason out yet..

Same for me.I have cronos 1.6.1 on phone with adw launcher.But happens only ones or twice.
Sent from my Milestone using Tapatalk

You guys probably overclocked it too much damaging the touchscreen.

Crypto_ahash said:
You guys probably overclocked it too much damaging the touchscreen.
Click to expand...
Click to collapse
this makes no sense mate. The overclock affects the cpu and not the touch screen. Anyway I didn't use any extreme overclock, beside using for a while the Telus Lite with 1.1ghz oc stock. And well I barely played any game, just a lot of emails and surfing on the web, very few calls. I noticed it happens when i move too much, like dancing or when i leave it on the shelf for the night and by the morning it acts crazy

lapy said:
this makes no sense mate. The overclock affects the cpu and not the touch screen. Anyway I didn't use any extreme overclock, beside using for a while the Telus Lite with 1.1ghz oc stock. And well I barely played any game, just a lot of emails and surfing on the web, very few calls. I noticed it happens when i move too much, like dancing or when i leave it on the shelf for the night and by the morning it acts crazy
Click to expand...
Click to collapse
I used to have that issue with stock 2.1 roms.
CM6, Sense mod, fastest Eclare and now MIUI does not bring that night mare back to me.
Also, if you charge using a 2-pin socket [the one without the earthed pin, popular in Asia], it'll show up.

OP needs to be a little more clear, but let me say my results.
Ever since flashing 2.2.1 SBF and then applying a few Froyo Mods and even goign back to ECLAIR,
I noticed that multitouch screws up. Sometimes it things I have a finger on the screen already, so by putting a finger on, it does a pinch zoom on me even though I only have 1 finger on it. Then sometimes it doesn't let me press an icon on my screen insisting my finger is elsewhere. Other times the notification bar starts getting pulled down randomly.
Perhaps Kadalban can explain his Multitouch fix, but for me it seemed to solve a lot of issues. Granted it was only pushed out in CM6 12/4/2010, which gives me 1 day to test so far, but some of those freak-incidents have been disappearing. You'd have to give me 3-5 days to conclude anything, but for now it seems to have done the trick.

i have issue with eclair 3b and CM6....it crazy when i I get my phone out of my pants....
is it FW error or HW error? in my country, in my country there are many like me.and we do not have a solution for this problem rather than the touch screen
google translate

duytrum444 said:
i have issue with eclair 3b and CM6....it crazy when i I get my phone out of my pants....
is it FW error or HW error? in my country, in my country there are many like me.and we do not have a solution for this problem rather than the touch screen
google translate
Click to expand...
Click to collapse
Update to the new CM6. 12.04.2010 solves it for me.

i'm using it....and now,i don't have issue again. i testing it.
Sent from my Milestone using XDA App

how did you fix your screen.my homebutton does not respond

I just changed to some mod roms and the problem disappeared for me.
Some of my friends got really big issue with the touch panel and when they came to Motorola service point, the technicians said there is a known issue with the panel they used but not all customers are affected (hence some people are OK after trying different roms).
So if one experiences it then just needs to go to Moto and they'll change to a healthy-guaranteed panel obviously, if you're still under warranty, it's free!

M7 801n pick up call delay

Hello,
I'm using this phone for a while. But there is very noticeable delay when I answer the call, meaning it takes a while after i answer the call to pick up line so I can actually hear the calling side and contrarwise. Sometimes it is like 2 seconds. Doesn't matter if call arrives when phone is asleep or not. This is not because of sim card or career.
It is HTC-dev unlocked and doing this on both stock firmware (latest update, newest hboot and radio etc...) and on revolutionHD latest rom. Seems like it didn't take as much time as on 5.1 google edition software (stock, rooted) but still it was there then.
And
Somtimes when the phone is ringing (volume max or not) the upper speaker - which is used for calling - doesn't ring ... sometimes rings sometimes not. I am confused of this. The hardware is in good condition.
:good:
Do you have any ideas of mods or smth?
Or pure explanations
Thank you

stanomx said:
Hello,
I'm using this phone for a while. But there is very noticeable delay when I answer the call, meaning it takes a while after i answer the call to pick up line so I can actually hear the calling side and contrarwise. Sometimes it is like 2 seconds. Doesn't matter if call arrives when phone is asleep or not. This is not because of sim card or career.
It is HTC-dev unlocked and doing this on both stock firmware (latest update, newest hboot and radio etc...) and on revolutionHD latest rom. Seems like it didn't take as much time as on 5.1 google edition software (stock, rooted) but still it was there then.
And
Somtimes when the phone is ringing (volume max or not) the upper speaker - which is used for calling - doesn't ring ... sometimes rings sometimes not. I am confused of this. The hardware is in good condition.
:good:
Do you have any ideas of mods or smth?
Or pure explanations
Thank you
Click to expand...
Click to collapse
If you already flashed stock and custom rom and issue is the same on both then it's most likely an hardware problem.
Sent from my HTC One using XDA Labs

So nobody have theese issues. MMMkaay

stanomx said:
So nobody have theese issues. MMMkaay
Click to expand...
Click to collapse
I do, on both my phones. The rooted one, and the bone stock one. I'm used to that already, so when I'm ansvering, I wait for those 2 seconds before I speak [emoji4]
dey tuuk ur juurbs

Question Device rebooting during calls [Exynos)

It has been a very long while since this is happening. I don't even remember if this was happening at the very beginning, in February when I bought it but it has been at least 4 months since I remember. I don't do much calls over the SIM network but I talk a lot over Messenger, Teams and Whatsapp. It is happening randomly but quite often. I can hear the other person's voice dropping like it simply dissappears suddenly. First I hear a few milisecond crack and then it dissappears for a second or two during Messenger. When I am doing Whatsapp calls it does the same and sometimes even drops the call and shows that I got Mic problems (Whatsapp shows that ). And when I am in a Teams call the phone might even reboot during talking. It is not hardware because when I was on Android 11 before the Update, it had similar problems but instead of rebooting the phone it simply freezes and makes a glitchy noise continuously until I reboot the phone. If I dont rboot it, The microphone simply won't work. When I am on a call via the Bluetooth Buds I don't have this issue. Both microphones work fine. The bottom one and the top ones.
It feels like it is the baseband....or whatever it is called... I don't want yet to put a cutom ROM as I lose the warranty. It is an Exynos version with 512 Gb space and I am looking for a solution first, and if I find out that a different ROM will fix this, I am OK but if I find out that it is hardware I would rather post it back to Samsung and get a replacement.
Many people like me here?

Found a small workaround. I installed an early version of the ROM via Odin and everything is working fine so far. So I assume it is Software/Hardware not just Hardware. I installed version G998XXU3AUE1 because you can't downgrade from Android 2 to an more earlier version than this. It has to do something with "3" after XXU which I think is the version of the baseband. We need Samsung to fix this so we can use the Phone with the latest ROMs... I did not test other versions asd this one works fine and the battery is even better than on newers ones. I actually missed the battery life from old verions to be hojnest, since the updates it could be noticible that it drains faster.
Another theory is that after installing Samsung weareble and starting using the buds that spoils the audio codecs ...I still didint connect it since flashed this ROM so after completing the testing with all calling apps I will put the Wearble again and see if it works.