Database Develop

Caller ID Issue

ok first off here are my specs
Running Fresh Toast 2.1
Cricket Wireless
Kernel [email protected] #89
Software 2.27.651.5
Baseband 1.04.01.09.21
Ok now my problem..this is happening more recent now. The phones screen will be shut down(or i will shut it down) and it works fine. Then someone tries to call me and it rings and rings and rings but No caller ID shows up and sometimes it freezes my phone until the phone call stops. Then i can resume it just like before the call. Anyone Know whats going on?

Anyone????

You might want to check out DarchKernel, as it sounds like it was made with your specific problem in mind (I think it is)
http://forum.xda-developers.com/showthread.php?t=705074
urushiol said:
***Explaination***:
I, as many of us have, been using Toasts #89 Overclocked kernel since it's inception. I have been thrilled with it's performance, and that our community has produced kernel source code before one was avaliable to us from HTC. Thats quite impressive
The only cons with this kernel that I have found are:
1: Would occasionally (20% of the time?) get a Force Close when a phone call is coming in, resulting in the phone being borked, and me having to reboot the phone.
...
Click to expand...
Click to collapse

Left speaker issue

I'm running TD 9.1, and prior was on 8.0. Tried both stock kernel, and a few other ones with no luck. At first when the sounds starts playing, the left speaker works fine, then with in a sec, it will fad to almost nothing. Is this something someone else has encountered? For all I know it has been like this since day one.. But I don't believe so.
Edit: I have also tried clean installs. i have not tried other roms yet.
Double edit: My xda search is not working, but google did for me. Found one other person having somewhat the same issue, but it was never answered. I hate to bump an old tread like that, after i have posted mine already.
[Q] HTC One speaker problem - One speaker turning off / mono sound

vwmaniacx said:
I'm running TD 9.1, and prior was on 8.0. Tried both stock kernel, and a few other ones with no luck. At first when the sounds starts playing, the left speaker works fine, then with in a sec, it will fad to almost nothing. Is this something someone else has encountered? For all I know it has been like this since day one.. But I don't believe so.
Edit: I have also tried clean installs. i have not tried other roms yet.
Double edit: My xda search is not working, but google did for me. Found one other person having somewhat the same issue, but it was never answered. I hate to bump an old tread like that, after i have posted mine already.
[Q] HTC One speaker problem - One speaker turning off / mono sound
Click to expand...
Click to collapse
I have the exact same issue. Tried million ROMs, sound patches and tricks but nothing change. The easiest way to see the difference between the two speakers is to run the Audio Test using HTC Function Test by dialing *#*#3424#*#*
Finally, I managed to get S-Off and now I'm going to get back to 100% stock flashing RUU_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3.exe, I'll do the test again and update the post.
EDIT: I'm full stock and it didn't fix it I guess I have to send it back...
BTW, what did you do? Did you fixed yours?

Running Sinless 5.1.5 now with elemental, everything works 100%. I guess for some reason my phone just didn't like TD, we all know they have a personality of there own..
Sorry for the long wait before response, I don't pay attention very well.

[Q] Need to wait a while for the screen to turn on

Hey,
So my dad isnt exactly satisfied with the custom ROM I flashed on his device, he needs to wait about 4 - 5 seconds (!) when theres an incoming call for the screen to turn on. The ringtone will keep on going off during that few seconds, but the screen will be black.
So I tested it on my Nexus 4, and no such issue has been spotted by me. Although, on his device, no matter how many times I tried, the issue was never gone and I had to wait a couple of seconds for the screen to turn on so I could see who's calling.
I'm not sure whether it is a kitkat issue or not, I tried 2 different roms, first BeanStalk, and now CyanFox, both had the same issue.
I also tried to flash CM10.1, but the keyboard kept on crashing after a fresh flash, wipes didnt help (maybe someone could give me a hand here?).
Another question is, where can I find some good call recording app? the ones from the play store aren't good, they only record one side of the call, never both
tl;dr:
is there some setting that I should change for the screen to turn on quicker when theres an incoming call on kitkat?
what to do if I want to downgrade from kitkat to jellybean?
is there some GOOD call recorder app around?
thank you

Pawelss said:
Hey,
So my dad isnt exactly satisfied with the custom ROM I flashed on his device, he needs to wait about 4 - 5 seconds (!) when theres an incoming call for the screen to turn on. The ringtone will keep on going off during that few seconds, but the screen will be black.
So I tested it on my Nexus 4, and no such issue has been spotted by me. Although, on his device, no matter how many times I tried, the issue was never gone and I had to wait a couple of seconds for the screen to turn on so I could see who's calling.
I'm not sure whether it is a kitkat issue or not, I tried 2 different roms, first BeanStalk, and now CyanFox, both had the same issue.
I also tried to flash CM10.1, but the keyboard kept on crashing after a fresh flash, wipes didnt help (maybe someone could give me a hand here?).
Another question is, where can I find some good call recording app? the ones from the play store aren't good, they only record one side of the call, never both
tl;dr:
is there some setting that I should change for the screen to turn on quicker when theres an incoming call on kitkat?
what to do if I want to downgrade from kitkat to jellybean?
is there some GOOD call recorder app around?
thank you
Click to expand...
Click to collapse
If you still on cm10.1 then download keyboard from market and you are good to go Also stock 4.1.2 has this lag issue when incoming call its pretty annoying really

tuncay_93 said:
If you still on cm10.1 then download keyboard from market and you are good to go Also stock 4.1.2 has this lag issue when incoming call its pretty annoying really
Click to expand...
Click to collapse
hey, thanks for your reply
actually no, STOCK 4.1.2 didnt have this issue, it started to show when I flashed 4.4.2 on it, is there some sort of fix for this or do I have to downgrade to JB? I'd rather stick to KK as I prefer it more.
on the other hand my dad hated google hangouts and he wants the stock messaging app back, I guess I can only go with CM
also I cant install a keyboard from the market, because I cant even log in to my google account, I cant get through the setup without a few things crashing over and over again, every second or so. the keyboard doesnt even show up

delete the latinIme.apk from the zip file you are trying to flash and substitute it with one from the other roms you tried flashing.
I know how to control the delay with which the ringer starts but not screen :s
These commands I think only help when call ends but it doesn't hurt to try, add them (or check the values if already present)
to build.prop in zipfile before you flash it
Code:
ro.lge.proximity.delay=5
mot.proximity.delay=5
I am on kitkat right now and have no lag issue...have you tried changing kernel?

Rudjgaard said:
delete the latinIme.apk from the zip file you are trying to flash and substitute it with one from the other roms you tried flashing.
I know how to control the delay with which the ringer starts but not screen :s
These commands I think only help when call ends but it doesn't hurt to try, add them (or check the values if already present)
to build.prop in zipfile before you flash it
Code:
ro.lge.proximity.delay=5
mot.proximity.delay=5
I am on kitkat right now and have no lag issue...have you tried changing kernel?
Click to expand...
Click to collapse
hey, thanks for your reply
I flashed Nameless ROM and surprisingly the lag issue is gone, and due to stripped gapps I flashed, I got the old messaging app back, which is quite the perfect combo, now the only thing I am missing is a good call recording app, is there a chance you can suggest one to me?
thanks again!

Pawelss said:
hey, thanks for your reply
I flashed Nameless ROM and surprisingly the lag issue is gone, and due to stripped gapps I flashed, I got the old messaging app back, which is quite the perfect combo, now the only thing I am missing is a good call recording app, is there a chance you can suggest one to me?
thanks again!
Click to expand...
Click to collapse
Still havent tried nameless but i did red the thread about it. Seems everyone likes it. It should be good

tuncay_93 said:
Still havent tried nameless but i did red the thread about it. Seems everyone likes it. It should be good
Click to expand...
Click to collapse
well I tried it out, the rom is nice and all, but my phone is extremely slow, the lag issue with phone calls is back, sometimes turning the screen off is impossible, or takes up to 2 minutes (!). turning it back on isnt much better either, I dont know what the problem is, the same thing happened on the BeanStalk ROM so I assume it isnt a software issue, but a hardware one, do you have any ideas what could be the problem and how can I solve it?

I want to tell you my experience about custom roms.
I don't know if you tried this combo: CM11 + kicos kernel (modified iodak's kernel) + minimal PA gapps
I works for me very well.

LGaljo said:
I want to tell you my experience about custom roms.
I don't know if you tried this combo: CM11 + kicos kernel (modified iodak's kernel) + minimal PA gapps
I works for me very well.
Click to expand...
Click to collapse
yeah, but shouldnt all the 4.4.2 ROMs be quite snappy? doesn't kitkat reduce the hardware requirements? why would JB work fine (or so I think, I'll go back to stock in a few mins and see) and KK be laggy as hell?
I've got a theory, I'm not a hardware guy and I dont know if I'm right or not, but:
could be that one of the cores is damaged and the system tries to switch some tasks to the damaged core (if android handles different cores the way I think) and that core doesnt really work the way it should, causing the entire system to work like a granny?

Pawelss said:
well I tried it out, the rom is nice and all, but my phone is extremely slow, the lag issue with phone calls is back, sometimes turning the screen off is impossible, or takes up to 2 minutes (!). turning it back on isnt much better either, I dont know what the problem is, the same thing happened on the BeanStalk ROM so I assume it isnt a software issue, but a hardware one, do you have any ideas what could be the problem and how can I solve it?
Click to expand...
Click to collapse
This is probably some wake/lock problem with software. Also on my o2x i've noticed strange lag when i press the power key it has lag until the screen comes on buttons below the screen light and after a couple of seconds the screen. It has 4.3 CM rom there if your father is using this phone i would suggest you some stock based rom with custom kernel. They should not have problems like these.

tuncay_93 said:
This is probably some wake/lock problem with software. Also on my o2x i've noticed strange lag when i press the power key it has lag until the screen comes on buttons below the screen light and after a couple of seconds the screen. It has 4.3 CM rom there if your father is using this phone i would suggest you some stock based rom with custom kernel. They should not have problems like these.
Click to expand...
Click to collapse
That still the best sollution for him - optimized kernel with stable ROM. He probably isn't techno freak?

tuncay_93 said:
This is probably some wake/lock problem with software. Also on my o2x i've noticed strange lag when i press the power key it has lag until the screen comes on buttons below the screen light and after a couple of seconds the screen. It has 4.3 CM rom there if your father is using this phone i would suggest you some stock based rom with custom kernel. They should not have problems like these.
Click to expand...
Click to collapse
could be, however, it isnt only for the power button, when the screen is off and a call is coming, it needs a few seconds for the screen to turn on, after the call is done, the system is all choppy and laggy. Turning the screen off after that is also nearly impossible, due to power button malfunction. I went back to stock for now and I'll see if the lag is gone, if it isnt, then its probably a hardware issue.
edit:
yeah, I'm on stock 4.1.2 and the issue isnt gone.
crap.

sounds like a problem in the timing the processor uses for scaling frequencies...
hav no idea what could be causing it unless you have some kernel tweak app and set wrong values

Have you tried clean flashing the Roms you installed? Have you Factory-Reset, Cleared cache, cleared Dalvik cache, and maybe did a system partition format before flashing?
Inviato dal mio GT-P3110 utilizzando Tapatalk

General questions about One Mini 2

Hello!
I just got a One Mini 2 - untouched - with original android.
Any suggestions where can i find a solution step by step to unlock the bootloader, s-off, which is the latest "upadated" rom for this phone ?
Everything is so old here, hard to find what i need.
Thanks folks!

For step by step method go to htcdev.com, select unlock bootloader, selext one mini 2 as your device and all steps to unlock bootloader are explained there.
Once you have successfully unlocked bootloader, you will need to flash custom recovery (TWRP) to flash any ROM
Currently the only working method for S-Off is Sunshine ($25).
Most updated stock ROM you can check on HTCdev as well for your device. As for custom CM Roms the most updated is CM13.

Hello there!
Thanks you very much your quick reply!
Except the s-off, if im staying on S-on - i can swap the recovery and the rom?
Silly question, but in the past 3 year i did nothing on HTC phones.
What about the CM13 - bugs?
Stable?

collinsgemdict said:
Hello there!
Thanks you very much your quick reply!
Except the s-off, if im staying on S-on - i can swap the recovery and the rom?
Silly question, but in the past 3 year i did nothing on HTC phones.
What about the CM13 - bugs?
Stable?
Click to expand...
Click to collapse
Yes you can swap recovery and roms, however only after unlocking the bootloader (some devices are unable to unlock thr bootloader, for some unknown reason despite following the proper procedure).
I came across only 4 bugs in cm 13.
1 At times the keyboard settings crashed at times it wouldnt.
2 The NFC came one for no reason cannot be disabled resulting in battery drain.
3 Lately the device would stay awake in battery settings despite screen off causing maassive battery loss, this was an android issue in Marshmallow without any known fix, I reverted back to stock for now waiting for CM14.
4 If camera settings are set to highest for picture quality some times the camera would crash and no solution except to restart the device, clear cache and data in apps settings.
There are some other reported bugs such as wifi security settings where some devices wouldnt connect to routers with WPA2, more issues can be found in the CM13 thread, you might or might not come across this issue, I didnt.
Also, loud speaker in music is slightly noisy and not crystal clear as with BoomSound and in calls ear piece sound is way too low and so is mic in recording, the member said he would fix audio problems in the next bug fix.

TryllZ said:
Yes you can swap recovery and roms, however only after unlocking the bootloader (some devices are unable to unlock thr bootloader, for some unknown reason despite following the proper procedure).
I came across only 4 bugs in cm 13.
1 At times the keyboard settings crashed at times it wouldnt.
2 The NFC came one for no reason cannot be disabled resulting in battery drain.
3 Lately the device would stay awake in battery settings despite screen off causing maassive battery loss, this was an android issue in Marshmallow without any known fix, I reverted back to stock for now waiting for CM14.
4 If camera settings are set to highest for picture quality some times the camera would crash and no solution except to restart the device, clear cache and data in apps settings.
There are some other reported bugs such as wifi security settings where some devices wouldnt connect to routers with WPA2, more issues can be found in the CM13 thread, you might or might not come across this issue, I didnt.
Also, loud speaker in music is slightly noisy and not crystal clear as with BoomSound and in calls ear piece sound is way too low and so is mic in recording, the member said he would fix audio problems in the next bug fix.
Click to expand...
Click to collapse
Cheers mate!
Now i have a time, im so excited - i can unlock the bootloader or not...
NostromoPop 2.4.0 (25/10/16)[CM12.1][5.1.1] - looks good.

collinsgemdict said:
Cheers mate!
Now i have a time, im so excited - i can unlock the bootloader or not...
NostromoPop 2.4.0 (25/10/16)[CM12.1][5.1.1] - looks good.
Click to expand...
Click to collapse
The loud speaker issue, ear piece and mic low sound issue and nfc issue were present in CM12.1 as well for me, might be fixed I'm unsure.
You will have to try I can't say if your bootloader will unlock or not.

TryllZ said:
The loud speaker issue, ear piece and mic low sound issue and nfc issue were present in CM12.1 as well for me, might be fixed I'm unsure.
You will have to try I can't say if your bootloader will unlock or not.
Click to expand...
Click to collapse
Im successfully unlocked the boatloader, the lastest TWRP flashed, i did backup, and im looking which rom is the better.
Be honest, im just want a normal working rom, without big bugs.
I saw the NostromoPop has mic & sound issues.
The carbon has microSD issues.
I dont know, i cant decide...
Cheers mate your help!!!

"This package is for device: memul; this device is htc_memwl."
Both Carbon & Nostromo.
So, lets get enjoy the KitKat.

collinsgemdict said:
"This package is for device: memul; this device is htc_memwl."
Both Carbon & Nostromo.
So, lets get enjoy the KitKat.
Click to expand...
Click to collapse
Memwl is not One Mini 2, thats HTC Remix.
There isnt much support for it, apologies.

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.