Related
I've got a v1605 flashed with Schap's 4.30 WM6, which seems to be working pretty well... However, I've got two slight issues:
Firstly, at some point, I've managed to lose my Operator Name. It said 'vodafone UK' when I first installed the ROM, but now it's blank (so I get nothing in the dialer, Phone Settings 'Home Service' and HTC Home just says 'Home' - is there any way I can fix this? I don't know what I did to break it... I did search, so I'm sorry if this issue's been covered elsewhere already.
Secondly, my camera seems to be much worse than examples I've seen taken with TyTNs owned by others. I've got serious colour 'banding', almost like applying the watercolour filter in Photoshop! At first, I thought it was just because it was on a 65k colour screen and that they'd look OK once transferred to the computer. However, they don't - the banding remains. It's really odd, because it's sharp and relatively noise free, and the macro is really good, it's just this banding issue that seems to have persisted through the original Vodafone ROM, a Black ROM and now the current Schap's ROM, all of which have had different versions of the camera app. I'm wondering now if it's a hardware fault, since there doesn't seem to be any setting I've missed...
I think I'd better bump this before it gets buried. I can't believe nobody has any idea how to get my operator name back since there are quite a few threads about changing what's displayed. However, I don't want to 'hard code' it in the registry - I just want it to display the actual name from the network/sim again...
I think the loss of operator name was caused by Radio 1.54.30.10... I guess some permanent damage has probably already been done from what I've read here. It looks like 1.5x is really dangerous, and to say that it's designed for a specific operator and wouldn't cause any problems there is stupid. If I was a customer of a network which officially distributed a 1.5x, I'd be really pissed off as I expect to be able to take my phone anywhere in the world and not fry the radio! At least, I've never heard of the radio in a Nokia or SE with operator-branded firmware dying when taken abroad!
Even though they've never been released as part of unbranded firmwares from HTC, they must be aware of its distribution, and should really put an official warning up stating the dangers of 1.5x radio builds. Odd thing is that if I stick another operator SIM in, the name shows up fine. I hope it survives in the long term. I've flashed it fine with 1.47.00.10 now, although after everything I read, I left it sitting on the ledge of an open window for a while before flashing it off the SD to make sure it was cold (it seems the likelihood of radio corruption is much higher when the device is warm...)
Any ideas on the camera issue?
Edit: By the way, is 1.48 a known safe radio build, because I notice people are reporting better performance with it than other 1.4x builds?
Azurael said:
Edit: By the way, is 1.48 a known safe radio build, because I notice people are reporting better performance with it than other 1.4x builds?
Click to expand...
Click to collapse
No known/reported issues up to radio 1.49.xx - It's only the 1.5x.xx where a potential link to hardware issues is being investigated - but it has not been confirmed (ie. no hard evidence) so it's more about using a bit of caution. 1.5x deaths are suspected in UK, Germany and Netherlands as they have large numbers of recent deaths where 1.5x was being used and the death occured "spontaniously" ie - just happened when things were working fine for a while but no proven link. I agree however, that the risk at the moment with that radio is fairly real and advise people to use it with extreme caution or at least do their own research on users sharing their own operator/area.
While a radio update may cause your network operator logo to change a bit (as can changes in the ext_rom etc) it certainly shouldn't cause issues with your camera and I suspect that's something else at play.
In terms of fixing your operator logo - I don't know any other way than tweaking the registry...
Have you tried other OS Roms with updated camera software to see if they cure your camera issues?
Good luck! (new motto - Radios fine up to 1.49)
As mentioned, try flashing another rom for resolution of both issues. Otherwise, u can tweek the registry for the op name or do a hard reset.
I had it apart since I wanted to tighten up the slide mechanism and the camera wasn't properly connected - it just fell off the PCB, only held above it's socket by the nearby flash LED PCB...
I cleaned the connectors out and plugged it in properly, and it seems to be much better now.
As for the operator name, it did seem strange that it could be caused by the radio, but somebody else reported it in the radio death issue thread, so I did wonder. I'll try flashing it with a different ROM soon, anyway, since this one's a bit heavy on the memory usage and has some irritating issues with the dialer anyway.
Edit: Fixed the op name as follows:
http://www.modaco.com/content/HTC-H...44537/Nature-Weird-operator-name-on-SPV-C550/
There was an entry in the registry with vodafone UK's carrier ID as a series of whitespaces. How odd. Deleted it and the name came back. I wonder how it happened though.
Upgrade & camera issues
FYI ... I loaded Schaps 4.30 Hermes ROM and loved it. Ran great for several days and then I ran the latest Radio update to 1.54.30.10. After I did, several things went wacky, including my camera. I could not access my camera, not even through the camera or video launchers on the HTC launcher. I had problems with my keyboard too, but found changing the keyboard to Cingular (instead of English) fixed that problem.
I reloaded Schap's 4.30, but it did not downgrade the radio and my problems persisted.
So, I reloaded AT&T's office WM6 upgrade and it downgraded the radio and from that point on, everything worked great. I've since gone back to Schap's 4.30 ROM and having no problems with camera or video. But I'm not planning on upgrading the radio (at least for now). Schap's 4.30 took the radio to 1.54.07.00
I have an AT&T 8525 a.k.a. HTC Hermes 100. I hope this helps you to better troubleshoot your camera woes!
P.S.
I'm considering loading Schap's 4.31 ROM (released today), but ... considering all my ROM woes lately ... I think I'm going to wait until I can read some of the reviews on his latest ROM.
Azurael said:
.......
Edit: Fixed the op name as follows:
http://www.modaco.com/content/HTC-H...44537/Nature-Weird-operator-name-on-SPV-C550/
HKEY_LOCAL_MACHINE>SOFTWARE>Microsoft>RIL>OperatorNames>23410 = O2 UK
23410 is o2 uk
23433 is orange uk
23415 is Vodaphone
23430 is tmob and virgin
23420 is 3
............
Click to expand...
Click to collapse
Azurael, thanks for the op id fix. Ever since I upgraded to Schaps4.01 BatteryStatus has not been displaying operator id correctly. Now its fixed!
FYI- Centennial Wireless is 31030.
Cheers.
Operator ID List
Here is a list of Operator ID's...
http://www.gsmcenter.pl/pg.php?tid=88&s=&dodruku=1
Summary of baseband bugs in Nexus s
1) Having network selection set to manual ( i.e selecting 302490) will result in No Service on a reboot.
Solutions:
- Have to cycle airplane mode to get it to pick up service (can be done with automatically tasker)
- OR Use automatic network selection. (you can force wcdma only but that will reset the SMSC which is annoying if you go in and out of wind away/home areas and you want to roam.)
2) Being in a area with no service for extended periods of time 5+minutes(subway, basement, etc) will result in a dead baseband, meaning once you come into an area with service the phone will not reacquire signal, airplane mode will not work as the baseband is now crashed, cant maunally search for a network. Have to reboot to get signal.
Solutions:
-Use tasker to cycle airplane mode on and off when in no service areas i.e) search signal 4 minutes, airplane mode on 10 minutes. This will keep the baseband from crashing and possibly save battery.
-Use NoBars to accomplish the same thing ( tasker gives you a bit more flexibilty of course but harder to use) http://www.appbrain.com/app/nobars-battery-saver/com.tomdryer.nobars
- Use airplane edit to avoid turning wifi/bt off when airplane mode is on. http://www.appbrain.com/app/airplane-edit/net.cenkalti.airplane
3) WCDMA perferred does not work.
- No solution.
These are all software bugs/baseband so hopefully they will be resolved soon by google. Voice your concern on the google mobile forum though. These are reproducible on stock, and any ROM.
http://www.google.com/support/forum/p/Google+Mobile/thread?tid=747f398a6c1bb2b9&hl=en&start=40
i have yet to encounter the issue on point 1
but yes i do find issue 2 very often, indeed i have set mine to WCDMA only to prevent roaming
since i installed NoBars, it seems to have taken care of the problem
need a few more days to confirm
AllGamer said:
i have yet to encounter the issue on point 1
but yes i do find issue 2 very often, indeed i have set mine to WCDMA only to prevent roaming
since i installed NoBars, it seems to have taken care of the problem
need a few more days to confirm
Click to expand...
Click to collapse
Still unacceptable that we even have to do that. This is a flagship phone and these are pretty major issues. What goods a phone that cant get signal. Pretty annoyed especially since this is a 500$+ phone.
This comes from these 2 topics
[Q] Nexus S & WIND Mobile 3G Connection Issues http://forum.xda-developers.com/showthread.php?t=928661
Sudden Loss of Data on Nexus S http://forum.xda-developers.com/showthread.php?t=882518
it's worth a topic of its own as it very clear states all the issues and work around to the problems
johoja said:
Still unacceptable that we even have to do that. This is a flagship phone and these are pretty major issues. What goods a phone that cant get signal. Pretty annoyed especially since this is a 500$+ phone.
Click to expand...
Click to collapse
I agree with that
Is there a bug report opened on google code?
I can confirm the second problem.... :/
ekerazha said:
Is there a bug report opened on google code?
Click to expand...
Click to collapse
I believe google code is for AOSP issues, for Nexus S related issues I would do the following:
1) Tweet the issue to googlenexus, and romainguy
2) Post on the forum http://www.google.com/support/forum/p/Google+Mobile/thread?tid=747f398a6c1bb2b9&hl=en&start=40
I'm surprised they still haven't acknowledged it.
johoja said:
I believe google code is for AOSP issues, for Nexus S related issues I would do the following:
1) Tweet the issue to googlenexus, and romainguy
2) Post on the forum http://www.google.com/support/forum/p/Google+Mobile/thread?tid=747f398a6c1bb2b9&hl=en&start=40
I'm surprised they still haven't acknowledged it.
Click to expand...
Click to collapse
The problem is distinguishing what is a Nexus S hardware bug and what is a Gingerbread AOSP issue, especially since the NS is the only device running 2.3.x, so we can't compare our bugs to other devices to determine if it's AOSP or device-specific.
Google does tend to close bug reports out as saying it's not a code bug.
The support/help forum does also tend to get more active replies from Google employees than you ever see on the code site.
distortedloop said:
The problem is distinguishing what is a Nexus S hardware bug and what is a Gingerbread AOSP issue, especially since the NS is the only device running 2.3.x, so we can't compare our bugs to other devices to determine if it's AOSP or device-specific.
Google does tend to close bug reports out as saying it's not a code bug.
The support/help forum does also tend to get more active replies from Google employees than you ever see on the code site.
Click to expand...
Click to collapse
Going through forums and bug reports & according to AllGamer the Samsung Galaxy S devices suffered the same issues initially but were fixed with updates (and as we all know SGS does not have 2.3+ (Also I'm not sure if it was completely fixed). Since the NS is pretty much the same device I'm not surprised.
See this for example:
http://www.howardforums.com/showthr...-after-disconnected-to-Mobilicty-to-reconnect
The work around for SGS users was a little bit better though they have an option to specify WCDMA Bands i.e) 1700mhz only. That seems to fix the problem on SGS. Unfortunately 'Pure' Google doesn't have that option built in. ( I can't confirm the fix only going on what I've read. Don't have a SGS)
Based on that I'm going to go ahead and say its not a Gingerbread issue, it's more of a baseband issue. Also I think you can flash Gingerbread to an N1 (Cyanogenmod) I sold my N1 so can't verify for sure its not a Gingerbread only issue.
back on the SGS, the problem was only with 2.1 Eclair
after upgrading to 2.2 Froyo all those voice/network dropped issues were resolved
so it's possible we might be seeing a re-lapse of the problem in 2.3 GingerBread, perhaps 2.4 might fix this?
johoja said:
Going through forums and bug reports & according to AllGamer the Samsung Galaxy S devices suffered the same issues initially but were fixed with updates (and as we all know SGS does not have 2.3+ (Also I'm not sure if it was completely fixed). Since the NS is pretty much the same device I'm not surprised.
See this for example:
http://www.howardforums.com/showthr...-after-disconnected-to-Mobilicty-to-reconnect
The work around for SGS users was a little bit better though they have an option to specify WCDMA Bands i.e) 1700mhz only. That seems to fix the problem on SGS. Unfortunately 'Pure' Google doesn't have that option built in. ( I can't confirm the fix only going on what I've read. Don't have a SGS)
Based on that I'm going to go ahead and say its not a Gingerbread issue, it's more of a baseband issue. Also I think you can flash Gingerbread to an N1 (Cyanogenmod) I sold my N1 so can't verify for sure its not a Gingerbread only issue.
Click to expand...
Click to collapse
First off, I think we need to stop saying SGS and Galaxy S phones. There are numerous existing models, and they all have slightly different hardware, including the radio chips. There are also at least four new as yet un-released, but announced models that will be called Galaxy S phones as well, and they are significantly different than the ones that are derivative of the original i9000.
For example, I have the Galaxy S i9000, and I usually specify that when referring to it. This is important, because the issues and solutions on the Galaxy S Vibrant are not the same.
My i9000 came with Eclair, and got updated to Froyo, and I NEVER had these problems with the phone on AT&T's US network. My friend is using a US Vibrant on AT&T as well and he never has had the issues, either on Eclair or Froyo. So I'm not so sure you can throw blanket statements like that around. But that's true of any issue.
More directly to your response to me, I didn't say this particular issue was or wasn't a hardware or software issue...my only point was that since the Nexus S is the only phone to have Gingerbread officially, the line between what is a device problem and what is a GB general software problem are definitely blurred. Any third party builds from the GB source may have had issues fixed on them. I remember from my N1 days that cyanogen often addressed Google bugs in his builds...
distortedloop said:
First off, I think we need to stop saying SGS and Galaxy S phones. There are numerous models, and they all have slightly different hardware, including the radio chips.
For example, I have the Galaxy S i9000, and I usually specify that when referring to it. This is important, because the issues and solutions on the Galaxy S Vibrant are not the same.
My i9000 came with Eclair, and got updated to Froyo, and I NEVER had these problems with the phone on AT&T's US network. My friend is using a US Vibrant on AT&T as well and he never has had the issues, either on Eclair or Froyo. So I'm not so sure you can throw blanket statements like that around. But that's true of any issue.
More directly to your response to me, I didn't say this particular issue was or wasn't a hardware or software issue...my only point was that since the Nexus S is the only phone to have Gingerbread officially, the line between what is a device problem and what is a GB general software problem are definitely blurred. Any third party builds from the GB source may have had issues fixed on them. I remember from my N1 days that cyanogen often addressed Google bugs in his builds...
Click to expand...
Click to collapse
I was referring to the Vibrant. Maybe it only affects that specific model as well.
http://forum.xda-developers.com/showthread.php?t=819589
http://forum.xda-developers.com/showthread.php?t=772849
I just think its a little suspicious that they have the very similar issues.
The Vibrant and the Nexus S both have the same baseband platform -
Infineon X-Gold X616 (PMB9801).
Either way. Your right until we actually hear from Google about the issue this is all speculation. Hope they fix it soon
Maybe the issue is only present for the phones that have the chipset to handle AWS ( 1700mhz)
Now the cellular radio freezing issue I complained is identified as #2? Good!
Hopefully the forthcoming radio ROM will fix this issue.
johoja said:
Summary of baseband bugs in Nexus s
1) Having network selection set to manual ( i.e selecting 302490) will result in No Service on a reboot.
Solutions:
- Have to cycle airplane mode to get it to pick up service (can be done with automatically tasker)
- OR Use automatic network selection. (you can force wcdma only but that will reset the SMSC which is annoying if you go in and out of wind away/home areas and you want to roam.)
2) Being in a area with no service for extended periods of time 5+minutes(subway, basement, etc) will result in a dead baseband, meaning once you come into an area with service the phone will not reacquire signal, airplane mode will not work as the baseband is now crashed, cant maunally search for a network. Have to reboot to get signal.
Solutions:
-Use tasker to cycle airplane mode on and off when in no service areas i.e) search signal 4 minutes, airplane mode on 10 minutes. This will keep the baseband from crashing and possibly save battery.
-Use NoBars to accomplish the same thing ( tasker gives you a bit more flexibilty of course but harder to use) http://www.appbrain.com/app/nobars-battery-saver/com.tomdryer.nobars
- Use airplane edit to avoid turning wifi/bt off when airplane mode is on. http://www.appbrain.com/app/airplane-edit/net.cenkalti.airplane
3) WCDMA perferred does not work.
- No solution.
These are all software bugs/baseband so hopefully they will be resolved soon by google. Voice your concern on the google mobile forum though. These are reproducible on stock, and any ROM.
http://www.google.com/support/forum/p/Google+Mobile/thread?tid=747f398a6c1bb2b9&hl=en&start=40
Click to expand...
Click to collapse
johoja said:
I just think its a little suspicious that they have the very similar issues.
The Vibrant and the Nexus S both have the same baseband platform -
Infineon X-Gold X616 (PMB9801).
Either way. Your right until we actually hear from Google about the issue this is all speculation. Hope they fix it soon
Maybe the issue is only present for the phones that have the chipset to handle AWS ( 1700mhz)
Click to expand...
Click to collapse
That is interesting.
I wonder if it's actually only with those that handle AWS while actually connecting to AWS. As I mentioned in my previous post, my friend is using a Vibrant I setup for him on AT&T and he has no issues like the ones described above.
I think there's just some level of black-magic or voodoo or karma with cell phones; for some of us, few issues, for others, nightmares.
Changed on its own from WCDMA only to GSM/CDMA auto (PRL)
so i was manually sync-ing my gmails
and all of the sudden i see i was from HSPDA and BAM! it changed to R (roaming)
i was like WTF !!!!!!!!!
so i immediately switched to airplane mode, and back to cycle it to see if it changes back and no, it was still stuck in Roaming mode.
so i ended up manually changing it manually back to WIND from the network selection screen
and then i went to check on *#*#4363#*#* and found out it was not on WCDMA only
which makes it really weird, as i didn't change it at all.
this is the first time it has done that to me.
have any body else seen this problem before?
good thing is, it did not enable data roaming, so hopefully i did not incur any roaming charges, ... i guess i'll see when the monthly Bill arrives
Mine switches occasionally when I lose reception. Like you, I generally keep mine on wcdma only. I have no idea why this phone does this, as it has happened on the stock rom, modaco, and cyanogenmod.
My old Nexus One never did this. Luckily it seems like that problem hasn't happened for me in the last week or two, so it isn't very common.
Never had this but on my nexus 1 I would use auto prl and would get more battery. I changed it on my nexus s and it goes back to wcdma.
If u have roaming off, u should be good.
it might be another bug related to the baseband
perhaps more people can confirm and or reproduce the issue
AllGamer said:
it might be another bug related to the baseband
perhaps more people can confirm and or reproduce the issue
Click to expand...
Click to collapse
Ive had it happen once or twice. Not sure how to reproduce it. I got annoyed because once that happens you have to re-enter the SMSC.
I leave mine on GSM/cdma (prl) and manually select the network I want. That keeps it from roaming as well.
I've got an I337M, locked to Rogers, using with a Rogers SIM. After tinkering with Google Play ROMS and CyanogenMod almost as soon as I got the device, I wanted to try shooting back to the Samsung Official firmware for a bit.
I've downloaded the "RWC" stock ROMS, two different builds numbers, and I'm getting caught up on one thing with both of them. The phone restores fine, works fine, carrier shows as the Rogers, however, the carrier bloatware that's installed is for Bell. Not that I'm missing the Rogers apps, by any means.
I'm curious as to why this is occurring. Not that I will ever use said software, but it'd be nice to know what's going on. Are the ROMS online actually Bell ROMS and being relabelled as Rogers because they work?
Or, is there a setting somewhere on my device that I'm missing that has persisted through multiple wipes/restores and is causing this? APN settings are correct, and carrier appears to be showing up correctly in anywhere that it's shown in Settings.
Anyone have any thoughts or input on this?
EDIT: I might add I found this thread which explains my dilemma, however, I could find no solid answers as to what was done to cure this issue.
EDIT for me answering my own question: Through an obscure series of connections, I figured it out. For those of you that may fall into the same boat. Here's the instructions I found.
How to Change the CSC code:
Please note that performing the CSC change action will factory reset your phone. It means it will take your phone to the status as it was when you bought it. All data present on the internal storage will be wiped. Therefore, do not forget to backup you data before you proceed.
Open your phone’s dialer and type the following code with your device IMEI number: *#272*Phone’s IMEI Here#
You can find your phones IMEI number on a white sticker beneath phone’s battery.
You will see a pop-up screen with a list of CSC codes. Change-CSC-SGS3
Select the CSC that you want and tap on “Install”.
Your phone will be reboot automatically.
Congrats! Your Samsung Galaxy phone’s CSC has been changed successfully.
Click to expand...
Click to collapse
Mods can delete or do as they please with this 95% useless thread.
Side.Step.Society said:
I've got an I337M, locked to Rogers, using with a Rogers SIM. After tinkering with Google Play ROMS and CyanogenMod almost as soon as I got the device, I wanted to try shooting back to the Samsung Official firmware for a bit.
I've downloaded the "RWC" stock ROMS, two different builds numbers, and I'm getting caught up on one thing with both of them. The phone restores fine, works fine, carrier shows as the Rogers, however, the carrier bloatware that's installed is for Bell. Not that I'm missing the Rogers apps, by any means.
I'm curious as to why this is occurring. Not that I will ever use said software, but it'd be nice to know what's going on. Are the ROMS online actually Bell ROMS and being relabelled as Rogers because they work?
Or, is there a setting somewhere on my device that I'm missing that has persisted through multiple wipes/restores and is causing this? APN settings are correct, and carrier appears to be showing up correctly in anywhere that it's shown in Settings.
Anyone have any thoughts or input on this?
EDIT: I might add I found this thread which explains my dilemma, however, I could find no solid answers as to what was done to cure this issue.
EDIT for me answering my own question: Through an obscure series of connections, I figured it out. For those of you that may fall into the same boat. Here's the instructions I found.
Mods can delete or do as they please with this 95% useless thread.
Click to expand...
Click to collapse
Excellent first post my child.
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.
Just want to clarify if changing region makes any difference other than enabling Themes etc.
Would love to have some clarity because if by changing Regions I can retain the Themes and high/increased headphone volume without any major issues then I'll stick with that rather than changing back to my actual region.
up to my knowledge, it affects theming. was not aware of the headphone volume thing.
lethalfriend said:
Just want to clarify if changing region makes any difference other than enabling Themes etc.
Would love to have some clarity because if by changing Regions I can retain the Themes and high/increased headphone volume without any major issues then I'll stick with that rather than changing back to my actual region.
Click to expand...
Click to collapse
If you choose India the phone has identify unknown number, different music player and different video player.im in the UK and if I chose that no themes....
lethalfriend said:
Just want to clarify if changing region makes any difference other than enabling Themes etc.
Would love to have some clarity because if by changing Regions I can retain the Themes and high/increased headphone volume without any major issues then I'll stick with that rather than changing back to my actual region.
Click to expand...
Click to collapse
I switched to Singapore region and everything is fine, themes are back as well as volume setting.
That just added local LAZADA shop apk and booking.com.
french phone number still identified.
lolo9393 said:
I switched to Singapore region and everything is fine, themes are back as well as volume setting.
That just added local LAZADA shop apk and booking.com.
french phone number still identified.
Click to expand...
Click to collapse
Good to know, my actual region is Pakistan but I am using United States and facing no major issues so far.
Themes are working great so is the caller ID etc.
I switched to India to get theme but when I switched back the theme was still there. I think once it is unlocked it doesn't go back even if you change regions.
It doesn't seem to have any other visible differences. Some were thinking that changing region might affect the maximum transmit power for wireless equipment and affect SAR value. I don't think anybody can verify that. On paper, if you switch to US, the max transmit power should be lower than Asian or EU regions. It's 20dBm vs 23dBm for Wifi standards, for gsm I have no clue.