Im just using a qr code generator and scanning it from my phone for now.
There really isnt many apps I need atm.
There really isnt many apps I need atm.
[ROM+Kernel] Inferior Human Organs unofficial CM7.1
- Thread starter blarf
- Start date
It seems like everyone having this problem is using the latest build? I have this problem on a previous build, I believe it is the July 22nd one. Don't know if this is useful info... just putting it out there
Re: Web market problem
gsm.sim.operator.numeric is 31000.
Sorry I didn't get a chance to get my build.prop up last night. It'll have to wait for after work today, if it's still needed by then. Seems that Jerry may have figured it out.
gsm.sim.operator.numeric is 31000.
Sorry I didn't get a chance to get my build.prop up last night. It'll have to wait for after work today, if it's still needed by then. Seems that Jerry may have figured it out.
Blarf, I'm wondering if someone make a typo somewhere. 200053 doesn't really make sense for VMU, since the "200" MCC part of the MNC appears to be an invalid MCC (and is clearly not an MCC code for the US). However, if you substitute 310 for the 200, you get an MNC of 310-053, which very interestingly is listing in Wikipedia as the code for Virgin Mobile.
[Edit: Just saw your post on XDA after I posted this. Mystery deepens....]
Last edited:
I know the market issue is more important but wondering if anybody has any advise on this?
ETA: While looking my build.prop over I found there was multiple entries telling the phone to play the boot sound. So Im guessing it was just erroring out.
Also noted that in the key map file you have key 217 listed twice. And ommited key 216, which is the voice search key, its easily fixed for people that know how to edit the file. I used keymapper and remapped it to be used as a power button.
Last edited:
It's KeynumberTracker to find the key codes when pressing the keys.
It's ButtonRemapper to remap the keys to particular functions.
In regards to the keypad discussion. It's Zefies old .kl file that is being used. Not only is key 107 in there twice but you may notice the voice key is dead, I discussed this with Ath3nos at one point and he said he was working on getting Voice to work for Voice again. In the meantime the keypad zips found through my signature all work, minus the stock as voice still doesn't work to my understanding (I have not tested it specifically) but I have used all the other zips with my own iho builds. Than again I opted to just replace the .kl file in my local version of the source with the one I use the most anyway
Long story short, if you don't want to have to use a button mapping app you can swap the kl file itself.
--
In regards to voice. Being that voice is called by a standardized event 'VOICE' I find it unlikey that the key wouldn't work with the stock .kl file and the voice dialer from CM7, I just have not tested this. My assumption is that if it doesn't work it's do to the voice dial apk itself not having the key event properly tied to it. This leads me to believe if we ported the stock/sprint voice dial app to work in CM7 we should be able to regain the voice key functionality.
The other possibility is that the kcm.bin file controlling the key events doesn't have the proper event settings defined in it. If this is the case I would think we could replace that file with one from the stock rom (not knowing if anything has been changed in the kcm.bin files I'm not sure if this would do anything at all... could even break something depending).
This is all conjecture but if someone does have the time to test the stock .kl file to tell if voice does work that would be a great start.
Long story short, if you don't want to have to use a button mapping app you can swap the kl file itself.
--
In regards to voice. Being that voice is called by a standardized event 'VOICE' I find it unlikey that the key wouldn't work with the stock .kl file and the voice dialer from CM7, I just have not tested this. My assumption is that if it doesn't work it's do to the voice dial apk itself not having the key event properly tied to it. This leads me to believe if we ported the stock/sprint voice dial app to work in CM7 we should be able to regain the voice key functionality.
The other possibility is that the kcm.bin file controlling the key events doesn't have the proper event settings defined in it. If this is the case I would think we could replace that file with one from the stock rom (not knowing if anything has been changed in the kcm.bin files I'm not sure if this would do anything at all... could even break something depending).
This is all conjecture but if someone does have the time to test the stock .kl file to tell if voice does work that would be a great start.
I pushed the stock 2.2 thunderkeypad.kl it works no problem.
You are correct, its weird the app is called keymapper on my phone until I open it up.
Then it says buttonremapper.
This has to be picked up at xda.
Im not feeling lazy now so Ill grab the link.
Both can be found here.
][App] ButtonRemapper - Beta v0.2.4 (New Galaxy S version added) - xda-developers
Sorry about saying the wrong name, as I explained its weird as the app it named keymapper until you open it on my phone. /shrug.
On my build the 217 key was duplicate not the 107. But yeah voice key wasnt there. What I did was edit the keypad file and changed one of the 217 to 216. Then used buttonremapper to set it to what I wanted. The button is listed as a call button so instead of mucking around and breaking something I figured the app would be better as it can revert easier.
I tend to think the rest of your post could be possible, but I also have doubts as there are so many things that google changed in 2.3 from 2.2 that it seems highly likely it will break something badly.
One more thing..remember this is the V and we are a special case. Just look at how long our mms was goofed up.
You may be right about 107/217 keys honestly I was going from memory, still havn't double checked that... fail or laziness or both, I'll let y'all decide.
MMS has been an issue for the S aswell do to apn issues. In the case of the .kl files they are identical from both phones. That being said the kcm.bin files on the other hand I have no way of viewing because that's an undocumented bin format according to google and subsequently I can't find a way to decompile it to a point that it's readable.
I would go far as to assume the only changes to the kcm.bin files from 2.2 to 2.3 is the addition of default key events which can be found on the android developers site, as to whether or not swapping those would break anything I just don't have enough information to know for certain. I would go as far as to say it wouldn't effect anything unless you are trying to use the key events defined specifically in 2.3 and above. There again I havn't had a real need to test this so everything I've said on the matter is really conjecture anyway. All I can say for certain is that 2.3 has all the events defined in 2.2 and prior so the any of the stock .kl settings will work, which is why I there should be no issues using the keypad files that I linked.
thanks! everythings great, except for a small problem. when i plug my phone into my computer, and i turn it off, the phone just automatically reboots. never did that before. also, when i turn it off and then plug it in, the phone automatically turns itself on. any help?
I believe this is a 'feature' for all CM7.1 ROMs. It doesn't allow charging when the phone is off like in stock ROMs.
Similar threads
Trending Posts
-
[Chatter] "Where everybody knows your name ..."
- Started by zero neck
- Replies: 53K
-
-
-
-
S24 pictures... show us how they look!- Started by Walter Wagenleithner
- Replies: 381
Facebook
Twitter
Instagram