keyborad mapping while in call FIX - 8525, TyTN, MDA Vario II, JasJam ROM Development

This will allow you to type normally while in a call, without the numbers being locked on in other applications. I could not find this anywhere so I did so tinkering and found this key to be the problem. I saw many other people that had the same problem here is the fix. Quite simple.
Just change the following key.
\ HKLM\Software\OEM\PhoneSetting\
“enablekeyboardmaping” to 1
Update. this fix is not currently working

Wow nice tips!
Was wondering how to get rid of this in my rom.
This was very helpfull
EDIT: Didn't worked for me. Tried some different typo but still no luck :/

fun_key said:
Wow nice tips!
Was wondering how to get rid of this in my rom.
This was very helpfull
Click to expand...
Click to collapse
no problem, thought I had to share it would only be fair.

thepcguy85 said:
no problem, thought I had to share it would only be fair.
Click to expand...
Click to collapse
Can you maybe elaborate a bit more you tweak? I am maybe missing something

Nope, this is not working
Either 1 or 0, DWORD value

oh man.. are we close to finding a fix?!?

this worked for me. I am running
WM6 5.2.1620 build 18125.0.4.2
ROM 3.61.502.1
the AT&T version
after I changed this it worked right away no reset needed

post a cab please

i dont see this in the reg at all.....

Might have to create it.
It's already built into the ROM im using so I can't check.

before i changed this key it did not work after i changed it it did. so i just changed it back and the numbers didnt come up. i will post the other keyboard cab i found as soon as i can.
i thought i had it
i will also try setting to 0 and soft rebooting just to make sure.

mcorrie1121 said:
Might have to create it.
It's already built into the ROM im using so I can't check.
Click to expand...
Click to collapse
Can you re-confirm the key, sans typos (no offence thepcguy85 )

after reboot the keys did not revert back. so now i am puzzled, l also loaded this cab with keyboard mapping. please note this cab is only for the AT&T 8525. but i am not sure if it was this cab or not.
we may be able to pull the setting out of this cab if it is the fix.

The cab is the same old 8525 keyboard mapping fix.
The key referenced in the OP has typos at the very least.
The ROM referenced in post #7 is the latest AT&T ROM, in which the problem has been fixed.

vp3G said:
The cab is the same old 8525 keyboard mapping fix.
The key referenced in the OP has typos at the very least.
The ROM referenced in post #7 is the latest AT&T ROM, in which the problem has been fixed.
Click to expand...
Click to collapse
it was not working when i first Flashed the ROM this is however to the best of my knowledge.
could you be of help vp3g?

thepcguy85 said:
it was not working when i first Flashed the ROM this is however to the best of my knowledge.
could you be of help vp3g?
Click to expand...
Click to collapse
Many many people have asked him what he did in his 3.61 rom thread. You may read his full response there, but, in short, he cannot replicate it.

I checked to see if this would work but my OEM/PhoneSettings Doesn't even have registry key as An Option.
fun_key said:
Wow nice tips!
Was wondering how to get rid of this in my rom.
This was very helpfull
EDIT: Didn't worked for me. Tried some different typo but still no luck :/
Click to expand...
Click to collapse
If your saying This , Then that means it has more to Do with Just the Build. I thought it Was the Build that The vp3G ROM was using that corrected the Error but if Fun_Key ROM is using the same Build than It's more than Just the Build .I"ll try Combing Over the Registry Keys in the vp3G ROM and then maybe get some Answers. I"m sure it's been done But what else can we do right now....

EQUiLiiBRiUM said:
I checked to see if this would work but my OEM/PhoneSettings Doesn't even have registry key as An Option.
If your saying This , Then that means it has more to Do with Just the Build. I thought it Was the Build that The vp3G ROM was using that corrected the Error but if Fun_Key ROM is using the same Build than It's more than Just the Build .I"ll try Combing Over the Registry Keys in the vp3G ROM and then maybe get some Answers. I"m sure it's been done But what else can we do right now....
Click to expand...
Click to collapse
Right now...load down vp3G's ROM and try and pull out as much of the AT&T as I can!

i dont think funkeys is based on 3.61 cuz i was diggin thru the reg and found 3.60 as a ver not 3.61.....hmm

jakeypoo said:
i dont think funkeys is based on 3.61 cuz i was diggin thru the reg and found 3.60 as a ver not 3.61.....hmm
Click to expand...
Click to collapse
I made some mix, but most part should come of 3.61. When I first built my rom there were some issue that denied me to use a full 3.61 through pandora.
But this is in fact a good hint which could allow me to troubleshoot the key mapping issue.

Related

Build 19949 Locked After 16th June

My device has been locked. It now shows a screen with the following:
This concludes the beta test of this software release. Thank you very much for your time and effort in helping make this a great product for our customers.
To obtain a newer release or further information, please revisit the web site that you used to obtain your current beta release.
Click to expand...
Click to collapse
I couldn't do anything with my device now, and soft-reset doesn't help. Perhaps another build helps, but I like my current ROM. Any solutions to this?
----------
For those who were using PDAVIET 2G, a solution has been posted by elivne at http://forum.xda-developers.com/showthread.php?t=400388
I have tried it and it works without the time bomb. Cheers..
kwangchin said:
My device has been locked. It now shows a screen with the following:
I couldn't do anything with my device now, and soft-reset doesn't help. Perhaps another build helps, but I like my current ROM. Any solutions to this?
Click to expand...
Click to collapse
I believe you will have to flash a different ROM...
Cheers.
can you establish activesync to flash a new/different ROM?
Anyone else seeing this? Is it all ROMs builton 19949 or just a particular one?
zim2dive said:
can you establish activesync to flash a new/different ROM?
Anyone else seeing this? Is it all ROMs builton 19949 or just a particular one?
Click to expand...
Click to collapse
Set your date to 16th June and you will know~ =)
my hermes also locked 2
now flash back to 19588 version
same problems here, device lock >.<"
is there not a fix for this? registry change?
My device locked too .... my rom is pdaviet rom build 19949 and not come back until I did a ahrd reset.... going back to 19900
the same here
the same here, can some one raise this point in pdaviet web sit
the same for me, pdaviet version build
I have the same problem... I can't connect with my active sync.. how can I update or change my rom? help please...
P.S. I can't do the "Flashing with your Memory Card" as 1, I don't have another device or a reader for it and 2, I have 1.3GB of impt files in it..
kwangchin said:
My device has been locked. It now shows a screen with the following:
I couldn't do anything with my device now, and soft-reset doesn't help. Perhaps another build helps, but I like my current ROM. Any solutions to this?
Click to expand...
Click to collapse
I believe this should fix it. use a hex editor to edit shell32.exe's S000. search for 0000004AB2FFFFEB, change it to 0000004A0000A0E1.
@trashcan: how am I to do the editing? Will it work even though my unit is not connected with activesync?
to update to a new rom, even if you can't connect with activesync, press the power + left ok buttons and press reset until a 4 color screen appears. then you should be able to update to any image using RUUWrapper.exe
@destro: thanks alot. it worked
me too.. yesterday get lock..
trashcan said:
I believe this should fix it. use a hex editor to edit shell32.exe's S000. search for 0000004AB2FFFFEB, change it to 0000004A0000A0E1.
Click to expand...
Click to collapse
I found shell32.exe but I can't really edit it. Can you give a more detailed explanation on what we have to do.
Thanx
Eran
jocool said:
I found shell32.exe but I can't really edit it. Can you give a more detailed explanation on what we have to do.
Thanx
Eran
Click to expand...
Click to collapse
Quote:Originally Posted by trashcan
I believe this should fix it. use a hex editor to edit shell32.exe's S000. search for 0000004AB2FFFFEB, change it to 0000004A0000A0E1.
I found shell32.exe but I can't really edit it. Can you give a more detailed explanation on what we have to do.
Thanx
do this code will fix the timerbomb?
Same...
Same...
First thing I'm doing from now on with all new ROMs is:
Set year 2050 right after flashing!
And see.

Rom for HTC 8525

I just updated my at&t 8525 and well i got the i guess official rom its kinda laggy on my phone which is alright but ive uploaded some programs on it and i got my sms threaded which im loving just wondering what would be a good rom for it and would it be the same affect as me updating the official one so i dont brick my phone and mess it up cause there too much to be getting a new one thanks in advance for any help
If you want one that is simple, safe, and made for at&t, you should go with VP3Gs last rom. Its nice, and stable.
Holy Repeat Noob thread openers batman
Jeez how many of these threads are we gonna see? Someone should count them and keep track for the noobs!
Ya, and its always people with the 8525 lol.
I would use Binkys or MRH if I were you, thats what I use on my 8525. But in reality with SPB Mobile Shell you can use almost any ROM which is what im doing now.
jblakk said:
If you want one that is simple, safe, and made for at&t, you should go with VP3Gs last rom. Its nice, and stable.
Click to expand...
Click to collapse
I ran his roms for about a year.
While they are VERY good roms, if you're up for manually inputting Data, SMS settins, and tweaking a few other things, the new 6.1 roms FLY.
I am using this one:
http://forum.xda-developers.com/showthread.php?t=388523
And it is damn fast.
sorry
yes guys i am a noob i just would like to get my 8525 goin good for me im sorry for the stupid noob ? but i just feel that the official rom does not perform that great. can anyone tell me where to download these roms at
We were all noobs at one time. You need to read this first:
http://forum.xda-developers.com/showthread.php?t=299462
It explains everything you need to know to flash ROM's. Then you will need to flash many different ROM's and see which one has what you want. No ROM is the same, and everybody wants something a little different.
Hmmm
GldRush98 said:
I ran his roms for about a year.
While they are VERY good roms, if you're up for manually inputting Data, SMS settins, and tweaking a few other things, the new 6.1 roms FLY.
I am using this one:
http://forum.xda-developers.com/showthread.php?t=388523
And it is damn fast.
Click to expand...
Click to collapse
I havent tried the new ROM that he just posted but I flashed his rom on the 17th of June and it was SLOOOOW... I mean really slow - boot menu etc and it also sucked the battery down fast w.o WIFI and BT on. Really buggy for me. So, I switched back to a Schaps win 6.0 Rom - stable for now. But if you say this new one works pretty good and is stable, I will give it another shot.
Also, I cannot find out how to fix my QUERTY effin Keyboard. The blue buttons are all effed up - i.e. @ is ? etc... I have seen people talk about this encounter, but I do not know how to fix it. Has this happened to you at all? If so, do you know how to fix it?
so if i get one of these other roms i gotta flash it is there not any already on here made for the 8525 thats already flashed for cingular i mean im not getting this
tombstone said:
I havent tried the new ROM that he just posted but I flashed his rom on the 17th of June and it was SLOOOOW... I mean really slow - boot menu etc and it also sucked the battery down fast w.o WIFI and BT on. Really buggy for me. So, I switched back to a Schaps win 6.0 Rom - stable for now. But if you say this new one works pretty good and is stable, I will give it another shot.
Also, I cannot find out how to fix my QUERTY effin Keyboard. The blue buttons are all effed up - i.e. @ is ? etc... I have seen people talk about this encounter, but I do not know how to fix it. Has this happened to you at all? If so, do you know how to fix it?
Click to expand...
Click to collapse
I'm running his version in my signature and it is fantastic.
With his rom there is a utility that lets you change the keyboard settings. It's called Advanced Config or something like that.
joshkoss said:
Jeez how many of these threads are we gonna see? Someone should count them and keep track for the noobs!
Click to expand...
Click to collapse
Everyone was a noob sometime .. does it mean we shouldnt help?
I cant talk for AT&T but I use CRC v11 .. very good
Remember most importantly step 1 is to use HARDSPL V7 this will prevent your mobile phone becomming a brick. You can find details about flashing and hardspl in MRVANX's sticky at the top of this forum.
Good luck .. become an expert and give back to the community.
GldRush98 said:
I'm running his version in my signature and it is fantastic.
With his rom there is a utility that lets you change the keyboard settings. It's called Advanced Config or something like that.
Click to expand...
Click to collapse
Schaps advanced config .. search and you will find it v2.1.0.0
so is there any unofficial roms out there that are faster and stable then then official one that is already flashed i mean what do i have to do just explain it to me i gave up a iphone for this and its alot better but iw anna make it faster
Ok
Step 1 : Read Mrvanx guide on how to HARDSPL your phone (and do it)
Step 2 : Load CRC's V11 rom
Step 3 : Enjoy
You will have to read MRvanx post
You will have to read CRC's post
Its all there so no one will repeat it here for you.
Heres the Link to Mr Vanx to start you off
http://forum.xda-developers.com/showthread.php?t=299462
The CRC Thread and Rom are here
http://forum.xda-developers.com/showthread.php?t=387990
You do need to put in some effort.

RUU_PPST_Vogue_SPRINT_WWE_3.03.651.4_Radio_3.42.30 ...

i think this is just one bugfix in OEM, dont really have any details.
Mirror - thanks walla
Mirror - thanks kevank
Megaupload
Rapidshare
again i will update with fast mirrors if posted.
whoa! Thanks DCD! Anyone have any details yet?
thank you again
dont know how you do it DCD!!!!
::bows down::
so when can we expect an updated DCD Vogue rom/kitchen???
-someone donate this man a Vogue-
Ahhh...lol
I just freaking installed the last one and installed all my software....AHHH!!...LOL
mirror
http://www.megaupload.com/?d=9KGYNEWO
http://rapidshare.com/files/1287341....651.4_Radio_3.42.30_AM_NV_2.04_Ship.exe.html
dcd1182 said:
i think this is just one bugfix in OEM, dont really have any details.
http://rapidshare.com/files/1286743....651.4_Radio_3.42.30_AM_NV_2.04_Ship.exe.html
again i will update with fast mirrors if posted.
Click to expand...
Click to collapse
Has anyone found out the difference between this update and the last one?
Thanks,
Coldheat1906
Thanks again DCD!!!
Coldheat1906 said:
Has anyone found out the difference between this update and the last one?
Thanks,
Coldheat1906
Click to expand...
Click to collapse
it corrected a bug where telenav did not show the keyboard.
binary changes ... except for registry changes and dsm files
CHANGES:
NEW FILES:
OEMAPPS\ContactMapper.dll
OEMAPPS\Core.dll
OEMAPPS\feeds-distrb_2.xml
OEMAPPS\LiveSearch.exe
OEMAPPS\LiveSearch.lnk
OEMAPPS\LSLaunch.exe
OEMAPPS\mxipupdate_LiveSEarch_100.provxml
OEMAPPS\RadioInfo.dll
CHANGED FILES:
OEMAPPS\phcanhtc.dll
OEMAPPS\phanrc.dll
OEMAPPS\sprint-navigation-htc-touchmr-2.0.16-noreboot.cab (from 2.0.15)
OEMAPPS\TaskManagerApp.exe
OEMAPPS\taskservice.dll
OEMDRIVERS\msm7500usbfn.dll
REMOVED FILES:
OperatorPKG_PT\LiveSearch3.0.cab
Click to expand...
Click to collapse
Fast HTTP Mirror:
http://www.geek-pages.com/rom/RUU_PPST_Vogue_SPRINT_WWE_3.03.651.4_Radio_3.42.30_AM_NV_2.04_Ship.exe
Kevan
hummmmmmmmmmmm???? should i risk a perfectly working device (with GPS) for a newly released "unofficial" official ROM????? considering that the Radio number is the same, can i extract the nbh file and flash via microSD?
does this require hard-spl since its not really out yet?
my dad and uncle have a sprint touch and i dont want to mess up their phone since ive already bricked my uncles(i fixed it but still)
kidnamedAlbert said:
does this require hard-spl since its not really out yet?
my dad and uncle have a sprint touch and i dont want to mess up their phone since ive already bricked my uncles(i fixed it but still)
Click to expand...
Click to collapse
nope, its signed. since they are sprint, youre fine.
Can the new Sprint Navigation CAB be taken from the ROM (after breaking it down in the kitchen) and installed on a custom ROM?
Can the Sprint Navigation CAB be taken from this ROM to install on a custom ROM?
Kinda looks like there's a fix in telenav plus LiveSearch is pre-installed.
Well, since I don't care about telenav (do I?) and its easy to install LiveSearch (it seems to work great), I guess I don't need this new ROM, right ? (hoping to avoid feeling bad about installing the last one and sticking with it since it took a bit of work to get it "just right")...
Maybe someone can extract out just the files that changed so we can just add them to the previous ROM...
Does any one have a problem with during a texting session the black line that suggests words blocks messages half the time. You either have to exit out and go back in or start a new message to delete the last word you typed and then cancel out.
It has been like this on both of the roms and it is driving me nuts. I haven't changed any of the input Touch Keyboard options from the default either so other have got to be having some issues with this.
My Mogul on WM6.1 doesn't do this.
DCD where do i get latest dcd kitchen for VOGUE right now?
I have noticed with the 6.1 official ROMs for the Mogul and the Touch that when you receive a text message, you get no notification. Even after I set it with a sound, it goes away. Is there a problem with it?

Unable to install cabs from device after messing with registry policies...

Hi!
I'm using ricky/kavana v24 wm6.1 ROM and while trying to install the 96-131 dpi change cab I changed a number of keys in my registry in the policies (HKLM\security\policies\policies) and now I'm unable to install cab files - when I try to open/"click" them nothing happens...
So, I guess I has something to do with my registry changes, which I didn't keep track of (I changed beyond the 101b, 1001, 1005, 1017 keys...).
Can someone please export and post it's excalibur policies registry entries for me to compare with mine and correct it?
It'll also be useful for people willing to app unlock it's excalibur/dash in the future...
I'll really appreciate it!
Thanks in advance and cheers!
just hard reset the phone
vwgtiron said:
just hard reset the phone
Click to expand...
Click to collapse
why don't YOU just export your reg for him?
showaco said:
why don't YOU just export your reg for him?
Click to expand...
Click to collapse
duh...that takes [email protected]
/me goes back to staring at the sun
showaco said:
why don't YOU just export your reg for him?
Click to expand...
Click to collapse
Thanks showaco, that's the whole idea.
Is it that hard to get that the post is primarily intended for me not to have to hard reset the phone?!
Still, anyone willing to post their reg entries?
I'll wait some more for a good willing soul an leave hard resetting my phone as the last resort...
Cheers!
Here you go Cassiano:
Code:
[HKEY_LOCAL_MACHINE\\Security\\Policies\\Policies]
"0000102e"=dword:00000D80
"0000101b"=dword:00000001
"0000101a"=dword:00000001
"00001017"=dword:00000090
"00001005"=dword:00000040
"00001001"=dword:00000001
"00001027"=dword:00000001
"00001034"=dword:00000001
"00001033"=dword:00000001
"00001032"=dword:00000001
"00001031"=dword:00000001
"00001030"=dword:00000000
"0000102f"=dword:00000C80
"0000102d"=dword:00000C80
"0000102C"=dword:00000000
"0000102B"=dword:00000000
"0000102A"=dword:00000001
"00001029"=dword:00000001
"00001028"=dword:00000001
"00001026"=dword:00000001
"00001025"=dword:00000001
"00001024"=dword:00000001
"00001021"=dword:00000C00
"0000101f"=dword:00000001
"0000101e"=dword:00000001
"0000101d"=dword:00000001
"00001019"=dword:0000008C
"00001018"=dword:00000010
"00001011"=dword:00000001
"0000100f"=dword:00000E94
"0000100e"=dword:00000040
"0000100d"=dword:00000C00
"0000100c"=dword:00000800
"00001009"=dword:00000003
"00001008"=dword:00000001
"00001007"=dword:00000040
"00001006"=dword:00000001
"00001023"=dword:00000001
Registry fixed but problem continues... might be something/where else...
Mikey1022 said:
Here you go Cassiano:
Code:
[HKEY_LOCAL_MACHINE\\Security\\Policies\\Policies]
"0000102e"=dword:00000D80
"0000101b"=dword:00000001
"0000101a"=dword:00000001
"00001017"=dword:00000090
"00001005"=dword:00000040
"00001001"=dword:00000001
"00001027"=dword:00000001
"00001034"=dword:00000001
"00001033"=dword:00000001
"00001032"=dword:00000001
"00001031"=dword:00000001
"00001030"=dword:00000000
"0000102f"=dword:00000C80
"0000102d"=dword:00000C80
"0000102C"=dword:00000000
"0000102B"=dword:00000000
"0000102A"=dword:00000001
"00001029"=dword:00000001
"00001028"=dword:00000001
"00001026"=dword:00000001
"00001025"=dword:00000001
"00001024"=dword:00000001
"00001021"=dword:00000C00
"0000101f"=dword:00000001
"0000101e"=dword:00000001
"0000101d"=dword:00000001
"00001019"=dword:0000008C
"00001018"=dword:00000010
"00001011"=dword:00000001
"0000100f"=dword:00000E94
"0000100e"=dword:00000040
"0000100d"=dword:00000C00
"0000100c"=dword:00000800
"00001009"=dword:00000003
"00001008"=dword:00000001
"00001007"=dword:00000040
"00001006"=dword:00000001
"00001023"=dword:00000001
Click to expand...
Click to collapse
Thanks a lot Mikey1022!
I had wrong values on keys 1006 and 1007, which i fixed according to your reg entries, but it didn't solve the problem... i guess the problem is somewhere else in the reg or with some app i might have installed right before the reg changes...
I'll try uninstalling whatever was installed prior to that and look further into solving the problem.
I'll post any progress i have.
Cheers.
Sounds Familiar
Yesterday I put on 6.1 with no problem and tried using the keyboard mapping cab file and it wouldnt do anything just opend the file and showed the details.
I knew there was something wrong and I wasnt crazy
Throwing the towel... hard resetting...
thegunna37 said:
Yesterday I put on 6.1 with no problem and tried using the keyboard mapping cab file and it wouldnt do anything just opend the file and showed the details.
I knew there was something wrong and I wasnt crazy
Click to expand...
Click to collapse
Good to know i'm not crazy as well (even tough there's a slight chance we're both...lol).
I searched some more on the web and found this:
http://www.everythingq.com/forum/motorola-q/cab-file-association-broken-7117.html
Hope it helps you cos i didn't work 4 me, so i'll be hard resetting my phone in the next few minutes
Anyways, i thank to the ones who helped in this thread and hope the info helps someone in the future.
Cheers.
there is one place that i make mods for .cab installs which you may want to take a look at first.
HKCR-->cabfile-->Shell-->Open-->Command-->(Default) .... the value is: wceload.exe "%1" /nodelete ...personally i take the /nodelete off so it removes the .cab after the install. but check that to see if that's whats listed.
Also check here:
HKCR-->cabfile-->EditFlags and make sure the value is: 65536
Dude Do A Hard Reset
Do the math...........!

BT issue on Schap's WM6 Pro 3.54b

Hi all,
I've upgraded my HTC hermes to this *nice* ROM. I'm having some issues with BT. It seems configuration stay in a read only mode. Every time I change the config (for example "enable file sharing") , next time I enable BT it's not keeping the options...For example..every time I start tomtom I have to type the security code for the BT receiver. Everytime...it just loose it all the times. Is there a workaround?
anyone using Scap's rom is having this issue?
Sky1979 said:
anyone using Scap's rom is having this issue?
Click to expand...
Click to collapse
yeah this is generally known. I had a problem too with BT, so I reflashed to the org. HTC WM6.0 ROM.There isn't a fix. Use a later version of Schaps ROM.
Thereby you already ask the same question here Like my experience is there too. Why start a new thread again?
Is this a known issue? I've search but found nothing on this...I don't want to upgrade to latest Schap's rom cause there is just 2 supported languages...
Sky1979 said:
Is this a known issue? I've search but found nothing on this...I don't want to upgrade to latest Schap's rom cause there is just 2 supported languages...
Click to expand...
Click to collapse
Read the thread you post your message before about the 3.54b ROM.
No man you failed to read my post. I don't have of these issues. I don't have any dutch version. I don't get any bluetooth disconnection. I don't have any crash activating BT or deactivating bt. I work perfectly BUT BT pairing doesn't keep the passkey! So everytime I have to manually provide it...
Sky1979 said:
I work perfectly BUT BT pairing doesn't keep the passkey! So everytime I have to manually provide it...
Click to expand...
Click to collapse
No man. It doesn't work *perfectly* It doesn't keep the password!
Solution. Upgrade to another version 4.xx Schaps ROM
Schaps probely reads these threads
hendrixus said:
No man. It doesn't work *perfectly* It doesn't keep the password!
Solution. Upgrade to another version 4.xx Schaps ROM
Schaps probely reads these threads
Click to expand...
Click to collapse
OMG. Seems you don't understand. Compared to the issues posted in that thread, bt for me is working. NO crash, file transfer it's ok and so on...Do you see any user reporting an issue for rom loosing the passkey? NO
Sky1979 said:
OMG. Seems you don't understand. Compared to the issues posted in that thread, bt for me is working. NO crash, file transfer it's ok and so on...Do you see any user reporting an issue for rom loosing the passkey? NO
Click to expand...
Click to collapse
I understand perfectly what the problem is. I don't understand why you have to start another thread if you have ask that same question in 2 different relevant threads, in English and Italian.I am now gonna unsubscribe this thread now.
Lets face it, that is a very old ROM and if you can't find previous mentioned issues in the original ROM thread then you're probably not going to get any solutions. There is hardly anybody still using that ROM who still visits this forum.
Hard reset or reinstall the ROM see if that changes anything, use a newer ROM or just live with it.
hendrixus said:
I understand perfectly what the problem is. I don't understand why you have to start another thread if you have ask that same question in 2 different relevant threads, in English and Italian.I am now gonna unsubscribe this thread now.
Click to expand...
Click to collapse
Hendrixus, the problem is that you never understood what my issue was and you started with this "read this read here read that". So please don't start questioning about threads. Do you mind if I reply to one user reporting the same issue? Seen Wam? Se replied with a clear answer READING what I wrote.
Lets face it, that is a very old ROM and if you can't find previous mentioned issues in the original ROM thread then you're probably not going to get any solutions. There is hardly anybody still using that ROM who still visits this forum.
Hard reset or reinstall the ROM see if that changes anything, use a newer ROM or just live with it.
Click to expand...
Click to collapse
Very old rom? It's 1 year old and unfortunately the newest version has been translated just in EN and FR. I've also tried an hard reset but nothing...
And I found out that also some users with the mAdkoE ROM reported the same problem...
thanks anyway Wam

Categories

Resources