[Q] Blue Studio C 5+5 help, custom rom or downgrade to kitkat - Blu Studio 5

So i just bought me and my wife theses phones blu studio c 5+5, they seem to be alright phones in my opinion. Mine does everything i want, but my wife's does not and mine has the same issue. there is no default voice dialer for a head set to initialize. ive tried every trick i can think of with no success. 1 click does nothing but will answer and hang up calls and 2 clicks will redial( of the head set). ive tried different apps and Bluetooth remapping tools and sucking to see if i could get the google voice search to active on 2 clicks since thats seem to be the only thing that will initialize something but nothings worked. it will not let you use a different dialer app. Once you hit send it still reverts back to the default and it takes over the call. No way to replace the default one and if uninstalled completely it does not calling what so ever out going or incoming. Had to do a factory reset to get the default dialer back so it was a usable phone again. I thought about downgrading it to kitkat from lollypop or installing a custom rom but see no tutorials on that just for the stock roms. unless my lingo is wrong i don't want the stock rom thats what its got on it right. Thought maybe with a downgrade or different rom wouldn't have this bluetooth issue or would have more likely of a chance of having a better dialer or being able to change it at least. I always been able to do the things and never had an issue like this with any other phones. Any thoughts or help would be much appreciated, Thank you

Related

Sound Problems

I am running the stock ROM from Sprint (WM 6.1). To my knowledge I do not have anything really wacky installed...and have not installed any new programs...but the following problem has developed...
Periodically my sound will jsut stop working. If I turn the phone off and back on, the sound seems to come back (by phone I mean the screen using the power button on a short press -- not actually causing the phone to power off). Sometimes that works and sometimes if doesn;t the first time...
Sometimes the sound will simply come back on it's own.
I have not done a hard reset yet, becuase I do not want to spend another three hours rebuilding my phone....
Any ideas?
Try installing a new radio. Some radios don't work well with ROMs, therefore giving intermittent sound.
(Also, for the sake of making a hard reset easier, use Sashimi to preload your cabs )
First, as a side note, if you spend 3 hours rebuilding your phone, sounds like you don't backup, I highly suggest doing that.
Anyways, there could be a number of reason why the sound is out. Since you say you hve installed nothing, I would guess a hardware issue. I would go pickup a new device.
TheChampJT said:
First, as a side note, if you spend 3 hours rebuilding your phone, sounds like you don't backup, I highly suggest doing that.
Anyways, there could be a number of reason why the sound is out. Since you say you hve installed nothing, I would guess a hardware issue. I would go pickup a new device.
Click to expand...
Click to collapse
I have backups....I back up several times a week...but since I do not know what is causing my problem...will restoring the backup help...
I did not say I did not install anything ... I said I did not think I installed anything wacky...and have not installed any new programs for a while...
Hopefully by restoring, it will work properly, then you can narrow down the problem.

Incoming Call Screen

So Im VERY new to this, first Windows Mobile phone. And this is my first post.
Right after receiving my HD2, I was disappointed with my purchase. I loved my Android powered G1, and fell in love with HTC. But when I got my HD2, the texting was terrible, and my phone kept freezing. After talking with a few friends about this, I was referred to this site.
From there, I did some research, and have learned a little bit. I decided to upgrade the ROM to the stock T-Mobile 2.13, through a link I found on this site. At the same time, I loved the interface of the CHT and CHTE, so I loaded those. Also, at the recommendation of Cookie's thread, I loaded Chainfire HD2 3D Driver Patch V2.0.
Well everything feels better, Ive started using Swype, and I havent had any freezing issues. I couldnt be happier...
But I recently notice (I dont do many phone calls, or talking. Im more web, email, and text) my incoming call screen isnt popping up. My phone will ring, I pull the phone out, and I see my home screen, and it is unlocked, like it should be when an incoming call comes through. I start tapping on the screen, and where I tap, icons/buttons start popping up. The "Mute" button, the "Answer/Ignore" bar, and SOMETIMES the caller's ID pic (if Im lucky enough for it to be someone who has a pic).
Now, this doesnt happen ALWAYS, but it does happen here and there. Ive also noticed, that the function that blacks/locks the screen when in call, against your face is running funny.
Does anyone know if this is related to my ROM? The 3D Driver Patch? CHT? Has anyone had anything similar???
I DID do a search, but only in this TMOus HD2 General sub forum. Should I be looking else where? Sorry for such a novel. I just felt that I should provide any possibly necessary info, since Im kind of clueless to this phone modifying world.
TIA.
Hmm...if it were me I'd definitely start with uninstalling that video driver and see if that changes the behavior.
Also, are you using the stock lockscreen or do you have CHT lockscreen enabled via CHTE? If you do have CHT's enabled, then next you might want to switch it off and see if it helps.
I don't know for sure that either of those will resolve that, but that's where I'd start troubleshooting.
After your new rom finished flashing, did you perform a manual hard reset (as recommended by most chefs)?
I've found that there is more chance of the rom being unstable if you dont.
(flashes dont always take first time, no clue why, but i'd estimate about 1 in 10 flashes just isn't stable, yet the next flash with the same rom is stable, , , I've also noted similar results when installing an OS on my PC, , , sometimes it just doesnt wanna take properly.)
theidealone said:
So Im VERY new to this, first Windows Mobile phone. And this is my first post.
Right after receiving my HD2, I was disappointed with my purchase. I loved my Android powered G1, and fell in love with HTC. But when I got my HD2, the texting was terrible, and my phone kept freezing. After talking with a few friends about this, I was referred to this site.
From there, I did some research, and have learned a little bit. I decided to upgrade the ROM to the stock T-Mobile 2.13, through a link I found on this site. At the same time, I loved the interface of the CHT and CHTE, so I loaded those. Also, at the recommendation of Cookie's thread, I loaded Chainfire HD2 3D Driver Patch V2.0.
Well everything feels better, Ive started using Swype, and I havent had any freezing issues. I couldnt be happier...
But I recently notice (I dont do many phone calls, or talking. Im more web, email, and text) my incoming call screen isnt popping up. My phone will ring, I pull the phone out, and I see my home screen, and it is unlocked, like it should be when an incoming call comes through. I start tapping on the screen, and where I tap, icons/buttons start popping up. The "Mute" button, the "Answer/Ignore" bar, and SOMETIMES the caller's ID pic (if Im lucky enough for it to be someone who has a pic).
Now, this doesnt happen ALWAYS, but it does happen here and there. Ive also noticed, that the function that blacks/locks the screen when in call, against your face is running funny.
Does anyone know if this is related to my ROM? The 3D Driver Patch? CHT? Has anyone had anything similar???
I DID do a search, but only in this TMOus HD2 General sub forum. Should I be looking else where? Sorry for such a novel. I just felt that I should provide any possibly necessary info, since Im kind of clueless to this phone modifying world.
TIA.
Click to expand...
Click to collapse
I read somewhere that the "unleaked official ROM" caused more problems than it was worth. I got the 2.13 ROM on the leaked version before it was made official and it has been working great since. I read that they made more changes and then made it official and that it was causing phones to be bricked and most phones ended up worse than they where before the the upgrade. The only "negative" thing i experienced was the screen sensitivity but it appears that the cab featured in the sticky at the top of the post fixed that!? Kinda strange If all else fails Factory Reset and try again. I always like to take a baseline reading. When my phone began acting screwy I would restore and run it stock for a few days to see if problems persisted...then after about three or four days slowly begin installing things...
Thanks for the responses! I will start with sirphunkee's suggestions. As I was typing, I started thinking the Driver Patch was a good possibility. Also, I have noticed that the phone doesnt just "sleep" the screen when I put the phone to my face, it locks. Im assuming this is something to do with CHTE's lock, because as sirphunkee mentioned, I am using the CHTE lock, instead of the stock.
Im going to start there, and see what happens.
Also, I did NOT do a manual hard reset. How would I go about doing so (yes, Im a HUGE noob. More of a car guy)? Im hoping I wont need to do this, as Im assuming I will need to restore all of my contacts, reorganize them, and reset everything else, as if the phone were new out of the box... Correct? But in case that is necessary, how do I do so?
As far as the leaked or official version... I couldnt find it on T-Mobile's site. I read a thread here, where it had been there then removed, due to people having issues with the download. I then was searching Swype or something, same forum, and found another thread, where someone had a link to the download through T-Mobile. Kinda hard to explain, but I will see if I can find the link, and the thread.
Thanks again guys! I really appreciate it. And thanks for taking it easy on me.
I just tried to post the links. I found them in my browser History. But because I have such a new account, I cant post.
theidealone said:
I just tried to post the links. I found them in my browser History. But because I have such a new account, I cant post.
Click to expand...
Click to collapse
Thanks for the effort though, you'll be able to put up links after just a few more posts (it's listed in the forum rules...hint, hint). Also, toreone already threw up a new thread in this section with that link for everybody, so don't sweat that
EDIT: oops, missed the rest of your questions there. The hard-reset is exactly what you said...resets the phone to factory-fresh condition. Yes, contacts will have to be reapplied, but sorting really shouldn't be an issue depending on your method of backing up and restoring them. I highly recommend using the built-in Microsoft Myphone utility for that (and it's wise to let it back them up regularly too, just in case, I just have mine set to do it each night while it's charging).
You can perform a hard-reset a couple of ways:
1. on your settings tab, hit "menu", then "all settings", then "system". You'll find an icon in there titled "clear storage". Run that, use 1234 as the code, and it will do its deed.
2. with the phone powered off, hold both the vol up and down buttons at the same time, and then press the end/power button to turn it back on, then it will take you into the same hard-reset process as the first method.

[Q] Random problem forces hard reset

Since flashing Duttys WM6.5 Leo Holy Grail ROM to my HD I have been very impressed with it's performance, 99% of the time it is responsive and stable and seems happy even though several programs are running. It has made my HD a really nice phone.
But every now and again something weird will happen, usually activesync reports a problem, or all of my contacts vanish, sometimes files on the device (not SD) cannot be accessed. So I soft reset and it doesn't boot, it will get stuck on the orange splash screen.
In total it has happened about 4 times since I flashed the ROM on Dec 29. It happened last night and eventually the device loaded the background picture, then popped up an error dialogue saying something about being unable to open a file, there was no mention of the file name. I did a soft reset and it then automatically performed a hard reset.
The other times the phone just hangs on the orange splash screen every time, causing me to perform a hard reset manually. Sometimes it will work fine for a good few days, or sometimes fail after only 1 day.
Its really annoying. I cant seem to get a HTC that works at the moment. My TP2 is rubbish, I've tried several ROM's and it is consistently unstable, so I go back to my HD which was always reliable... And now this happens.
please Help or I'll be forced to turn to the darkside and get an iphone and I really don't want to do that!
Why not just return to the "reliable" firmware version used previously?
I'm not a fan of custom roms or 6.5, especially on this underpowered model, it's definitely the most reliable handheld I own or have owned with oem roms though, especially without it's resource gobbling pretty face on.
Not really the most helpful answer, but i suppose i cannot argue the reasoning behind it.
In defence of this ROM it is BRILLIANT when it is working, i'd actually argue that the device feels smoother with this ROM than it did with the stock Orange UK ROM.
deejayry said:
Not really the most helpful answer, but i suppose i cannot argue the reasoning behind it.
In defence of this ROM it is BRILLIANT when it is working, i'd actually argue that the device feels smoother with this ROM than it did with the stock Orange UK ROM.
Click to expand...
Click to collapse
Have you tried asking your question in one of Duttys threads. You may get a better response. Also, try flashing a different rom
Thanks.
Since posting the message the problem has not come back.
I have been thinking that there is a possibility that my server was hacked, i noticed a few things had changed on the server, i also had notices when i logged in to facebook and paypal, informing me that someone from New York had accessed my account. the server and facebook used to have the same password.
Is it possible that the problem i had was caused by a hacker on my exchange server issuing a command to reset the device? i know it can do something like this to protect data in the event of a phone going missing.
what does the device do if exchange server performs this routine?
Please help me find this problem... i dont want to buy an Iphone!
Ok I tried a different Rom, this time i used one of KWBR's:
http://media.celogeek.com/roms/kwbr/..._5.7_Sense.rar
a month down the line and its just started to go wrong again.
this time, i find that the device slows down a little bit, prompting me to soft reset, when it boots i find that my contacts are missing, active sync will not load properly, it briefly flashes on screen but lower 1/3rd of active sync window is missing (appears transparent or black) only way to get contacts back and active sync working again is hard reset!
Anyone got any ideas what might be going on?
its been doing this now on both ROM's but i have no idea what may be causing it, as far as additional software i only install a few apps: Slimcontrol 1.5, Core player & GcZ2 (geocaching tool) which all have been running fine before.

call log ( missed calls) not working after root.

I had recently had my phone flashed to the best carrier for the area im in ad noticed a few problems. im rooted with cm11 but sticking with the stock debloated rom. the carrier flash had actually cased some issues initially with the screen turning on and fully lighting up, but when i started flashing new roms that issue was fixed. I thought it had fixed all my issues, but as I found out yesterday, my call log is still completely null and void. it shows no calls in or out, and ive made plenty. but the bigger part is that I dont even know about a missed call until I get the voice mail notification. ive tried apps to record them but im guessing they work off whatever stock files control that and thy read nothing as well right now
has anyone had this problem or possibly know of a fix?
Me too!
Bam9 said:
I had recently had my phone flashed to the best carrier for the area im in ad noticed a few problems. im rooted with cm11 but sticking with the stock debloated rom. the carrier flash had actually cased some issues initially with the screen turning on and fully lighting up, but when i started flashing new roms that issue was fixed. I thought it had fixed all my issues, but as I found out yesterday, my call log is still completely null and void. it shows no calls in or out, and ive made plenty. but the bigger part is that I dont even know about a missed call until I get the voice mail notification. ive tried apps to record them but im guessing they work off whatever stock files control that and thy read nothing as well right now
has anyone had this problem or possibly know of a fix?
Click to expand...
Click to collapse
I am also experiencing the exact same issue. Rooted Vzw g2 on page plus. I've searched phone for a log file that looks like it corresponds to the call logs but no love. It is a little obnoxious as I have no idea who calls me if I miss the call.
Have you found a solution?
me, too!
Any insight?
I've not found a thing that will help us, I've found others experiencing the problem, but no solution. I'm running a stock debloated rom and i think therein lies the problem. Something that was removed that was seen as bloatware is most likely what actually tracks the call log. I've been searching for a rooted bloated stock rom, but to no avail. I ran a few other roms and had a call log, but the roms overall sucked and i like the ui of the stock especially the camera app....I'll keep looking, but hopefully someone in the know sees this post and helps us out
I was flashing different stock roms and differet Gapps and whe it boots into the backup scree to set the phone up the number it was showing saying my sim was already set up wasnt actually my number. I dot know where or why the number was coming from. but alas, my call log worked ad on called id's it still showed up as the right number. so i began puttig all my stuff back on it and updating things and something i updated chaged that and now im back where I was without a call log.
i dont know what files i had flashed excatly, so now its just a guessing game and lots of flashing..
I am running through the same issue, no recent and missed call history, my messaging is fine. The G2 was rooted and flashed to PP. I am wondering if you have solved the problem, if so, could you please share your solution, very much appreciated.
Bam9 said:
I was flashing different stock roms and differet Gapps and whe it boots into the backup scree to set the phone up the number it was showing saying my sim was already set up wasnt actually my number. I dot know where or why the number was coming from. but alas, my call log worked ad on called id's it still showed up as the right number. so i began puttig all my stuff back on it and updating things and something i updated chaged that and now im back where I was without a call log.
i dont know what files i had flashed excatly, so now its just a guessing game and lots of flashing..
Click to expand...
Click to collapse
same issue
I am having the same issue. I flashed to pageplus, rooted and installed xdabebbs rom. I dont see call history in my recent calls app. Please let me know of a solution
No solution yet, see someone say it could be because of flashing, so how you do the flash, yourself or someone help you.
Find out solution, simply reflash NAM only, i used DFS.
same problem here.
@gjbwj what for you mean reflash NAM?
Running VS982.5 ROM if it maters.
Pretty sure it was something I restored with TiBU that caused it. My wife's phone has the same ROM but I didn't restore anything but apps on her phone.
I would rather not have to start over for what should just be one file corrupted.

[SOLVED] Weird Phone app behaviour when trying to make a call on custom ROMs GT-I9506

Hi, I recently got an S4 and installed Nougat RR custom ROM on it. It was all working mostly fine, but one day I tried to make a phone call and saw this strange behaviour. Once I put in the number and press Dial, the screen goes black and I lose control over the phone - can't evoke the keyboard, cancel the call or do anything else apart from hard reset. Interestingly the call actually is under way - it connects and you can have a conversation.
I don't use the Phone function often, mostly communicate via IM, but it is crucial that it's working, just in case. Therefore I tried few different custom ROMS from the I9506 dev thread- Lineage 15/16 and Cyanogen 13 - the same stuff happens on all of them. It works ok on a stock rom though. I also tried flashing different modem than recommended XXUDOJ2, to no avail.
I'm not very experienced with all this stuff, so not sure, perhaps I'm doing something basic wrong way. Though, my old phone S3 with CM 11 works fine on the same SIM card.
-phone: S4 LTE GT-I9506 according to IMEI
-bought in Europe (Poland) but now I use it in Taiwan
Can provide other details on request. Any help/ideas would be most appreciated.
If you are not concerned with loosing data or taking the time to go to the extreme step, to get a phone back from the dead, the best bet in a lot of peoples mind would be to reset the phone by flashing the original firmware. There are numerous threads here on XDA on how to do that.NB: Custom ROMs are not bug free, but even more likely to have issues than stock.
The hard question now becomes what is the correct firmware for your phone.
Sorry, just noticed you have tried and have no issue going to stock
First thing to remember is that each specific ROM has been built to work with a specific bootloader-modem combination. Using the wrong one could cause issues.
If you have matching ROM/modem/bootloader and still an issue, try a dalvik ad cache wipe and reboot. If you still have issues, get a logcat and post it somewhere on a text hosting site like www.hastebin.com and paste a link to it with your issue in the ROM specific thread. Also, I would suggest Oreo, as its still early days for Pie and most people have probably moved off of Nougat.
DiamondJohn said:
If you still have issues, get a logcat and post it somewhere on a text hosting site like www.hastebin.com and paste a link to it with your issue in the ROM specific thread.
Click to expand...
Click to collapse
Thanks again for replying DJ, but perhaps I wasn't very clear The phone itself is not dead - it works fine. The issue is with the "Phone" app. Basically, when I try to make a call, the aforementioned weirdness happens - call is underway but screen goes black and I can't access any functions like keypad or cancel. I can Power Off and then the rom reboots and works again (though it always goes into Don't Disturb mode). When I try to make a call again, the same stuff happens.
I tried a stock rom and the Phone app did work. I don't want to use it though because it has all the google stuff and avoiding it is the main reason I use custom roms in the first place.
So far I have tried most of the custom roms the first two pages here. I tried to follow instructions and also to use the appropriate modems/bootloaders (actually, it's always UDOJ2 one). On all of them the Phone app has the same behaviour. Actually, I did sort of manage to get it to work on the latest unofficial RR (7.0.0) - it goes black too, but then screen comes back after some weird keypresses combo...bit sketchy, but workable. But then Line is not working on this rom and I really need this app too, so...
I can try and get the "logcat" from one of your roms (I really liked your RR and used it for some time on this phone) and then post in the appropriate thread...or would you recommend Havoc one instead?
henryakeley said:
Thanks again for replying DJ, but perhaps I wasn't very clear The phone itself is not dead - it works fine. The issue is with the "Phone" app. Basically, when I try to make a call, the aforementioned weirdness happens - call is underway but screen goes black and I can't access any functions like keypad or cancel. I can Power Off and then the rom reboots and works again (though it always goes into Don't Disturb mode). When I try to make a call again, the same stuff happens.
Click to expand...
Click to collapse
No, I got it on a second read, and hence the strike out of the first part, on my first go at responding.
A logcat is best for a mostly working phone. Otherwise a last_kmsg; which still may provide some info on your startup/initialisation.
If you can't access the screen, setup and connect via adb before the phone becomes unresponsive.
henryakeley said:
I can try and get the "logcat" from one of your roms (I really liked your RR and used it for some time on this phone) and then post in the appropriate thread...or would you recommend Havoc one instead?
Click to expand...
Click to collapse
I would suggest to do it on a LineageOS ROM as it would have less possibly buggy customization. Also, it would possibly have more users, and those threads are created by the guy who builds the base for nearly all ROMs for this device.
You may be better off to try Lineage16 as that thread is more alive, but Los15.1 would be more stable. I personally would try LOS15.1 first, and then if you get no help, flash 16.1 and try your luck on that thread.
Once you get a stable phone, then I personally would recommend HavocOS. It has the most customisations, even more than the old King RR, and hence I've moved from RR to Oreo Havoc; with a short step in between of Oreo crDroid.
Just realised, you said you historically used my RR build, which I assume that back then you did not have the issue. I will assume that it now has the issue? have you tried restoring from an old TWRP backup?
DiamondJohn said:
Just realised, you said you historically used my RR build, which I assume that back then you did not have the issue. I will assume that it now has the issue? have you tried restoring from an old TWRP backup?
Click to expand...
Click to collapse
No, I susppose the issue was always there, I just did not need to make an actual phone call fro few weeks since i installed your rom. I'm in Asia and all the communications needs here are covered by Line messaging app. Then I went to a phone shop to recharge my credit, they needed to call some service and access the keypad and it all came out then.
I could still use it as a Line device, but in reality do need the working phone app too, for some emergencies when traveling and so on.
Will try to do a logcat from Lineage, thanks for your help. If it comes to nothing might try to pester you again in one of your rom threads
Issue solved, thanks to DiamondJohn: https://forum.xda-developers.com/showpost.php?p=79050487&postcount=980
It's the proximity sensor's fault.

Categories

Resources