Related
Hi, this thread is here for posts that has no room in technical discussion related to this rom. From tech discussion, irrelevent posts will be deleted without excuse, without reason. So here's the correct place for them...
Well done
I just wanted to say well done for the new fast clean rom. I'm finally over 2.5!
Everything I need to work works and well and fast. Thankyou !
Now how do we get the touch interface on the Charmer as they seem to be getting working on the Prophet??? Maybe wrong place to ask, will wait. In the meantime, thankyou again.
the bt works fine with car set
"Now how do we get the touch interface on the Charmer as they seem to be getting working on the Prophet??? Maybe wrong place to ask, will wait. In the meantime, thankyou again."
it's available for wizards - search their forums: http://forum.xda-developers.com/showthread.php?t=313656
"the bt works fine with car set "
nice to hear...go on with testing
WIFI confirmed
WIFI SDIO function has been confirmed by beta tester, loskarlitos - with some limitations like control panel not working , WIFI connection has been confirmed as stable and able to survive standby mode
Thanks Loskarlitos!
Excellent, a new rom to try!!
I can't believe I have only just found this. I could have been playing with it this evening. Its a little late to start messing now!!!
Thanks for all the hard work Nocturne.
nocturne.op.15 said:
WIFI SDIO function has been confirmed by beta tester, loskarlitos - with some limitations like control panel not working , WIFI connection has been confirmed as stable and able to survive standby mode
Thanks Loskarlitos!
Click to expand...
Click to collapse
i think the wifi control panel only works with built in hardware. thats why its removed from the official charmer roms.
hope you are right. i wil think about removal of it for the next ver.
nocturne.op.15 said:
hope you are right. i wil think about removal of it for the next ver.
Click to expand...
Click to collapse
I dont know if that's such a good idea. Some people use SDIO wifi cards and find those wifi settings useful.
Cheers,
vlodeck
as reported from my beta man, loskarlitos, and as reported above, this wifi settings applet seems to be working only with built-in wifi modules, settings are inactive for sdio cards.
Wifi SDIO owners, please share your experineces - than i can build fully functional rom stripped down from useless parts
Hi,
first of all amazing rom. Really really fast. It syncs great under Vista. To flash from Vista you have to use the "Another Flash Method". I encountered no problems with the 12 apps running, alarm or landscape problem.
Only the Calender and Contact buttons are still hardcoded to Start and Back.
problem with alarm was solved - it was really caused by underclocking charmer down to 95mhz (I'm using BatteryStatus for dynamic overclocking. 95MHz is simply not enough power to bring alarm window up and system behaves strange)
problem with changing landscape/portrait disappeared and never came back - but will keep it in buglist until this is really confirmed
lagge number of running apps stil remains - if lot of apps running, softkeys are not working as they should...hope somebody could try this on another wm6 device?
Calendar and Contacts issue
Been testing this rom for a day or two - I get the problem where Calendar and contacts won't start (whether from soft keys or the Start menu) and I have to soft-reset to egt it working. I admit I have been using iContact as well so I will uninstall that for a few days and see if the problem goes away.
closing some apps does not help? it helps for me...
customization?
Hi, when i flash yours new rom and make HR system was start and customization from old wm5 was started. In rom 4.4 customization was not started after HR, is this was changed in this release?
sorry for my english....
This was reported and will be modyfied in next ver. Till then, just skip the customization after HR
Ring tone changes....
Hi, next thing is that my ring tone changes to default without my command. I've seen this before in previous roms but in 4.4 it was ok.
I installed this last night. Seems nice and fast.
I noticed that the phone pad SIP and MMS are missing. (Installed these manually)
Also, i'm afraid the Bluetooth A2DP appears to still be the older, poorer quality version.
Cheers
phonepad sip is missing because i don't like it - it is not necessary. everybody can install it easily manually. but it will not eat precious memmory for us who does not use it ,-)
MMS support is there - no problem with it, thing you report is a bit strange...
it's hard with A2DP. Some testers were reporting it's the best A2dp they have seen - you tell the opposite. The worst thing is that i cannot test it - i do not have a2dp device :-( is possible that transfer quality is also dependent on used HW?
regarding those ringtone changes - i was testing this today (about 10 calls, some restarts etc - no problem. aren't you using any 3rd party software for phone profiles or things like that? I saw this with pocket zen phone..if not, try please to search for some dependency of this behavior so i can repair it
Thanks Nocturne.
I'm really starting to think I've flashed the wrong ROM. I've got so many on my PC now.
Can you confirm what I should be seeing under Device Information?
Thanks
Hello,
I setup my voip on the PK3.0 rom, its dialing and it almost works. Except that I can not hear anything, I can speak and the other party hears me just fine, but I can not hear them, anyone came across this? What can you recommend to fix this?
bump, still no resolution to this, it works fine one way. But I can't hear anything the other person is talking....
Anyone?
marek101 said:
Hello,
I can speak and the other party hears me just fine, but I can not hear them
Click to expand...
Click to collapse
This isn't going to help much but .... sounds like the perfect setup to me.
Hi Guys,
I am trying to run VoIP on my device (which is not athena by the way) and have absolutely the same issue. I have very good knowledge in the voip networks and very good experience and this thing makes me crazy (believe me)
As what i already found is there shouldn`t be any issue:
the RTP is going between the end points without any troubles on the correct ports and everything looks just perfect - i.e. there is no any network issue, SIP communication (SDP related) issue or whatever like that
The possible problems for me are as follow:
- codecs issue - actually if you can make a call and the other side pick it up without the line to be dropped, then this is not the case (at least the codec on windows mobile is working)
- the audio output device - the audio is trying to go out trough a device which is not present on your system - so you are not hearing anything.
I will be glad to chat to anyone who have the same issue and can help me to debug the problem and find the permanent solution. I don`t have big knowledge on windows mobile devices (but at least know how to install cab files and modify the registry settings - hehe) so to anyone who is in deep relationships to this system and can help me -- give me your msn/icq/skype/jabber contact and lets pray together
salasbg said:
Hi Guys,
I am trying to run VoIP on my device (which is not athena by the way) and have absolutely the same issue. I have very good knowledge in the voip networks and very good experience and this thing makes me crazy (believe me)
As what i already found is there shouldn`t be any issue:
the RTP is going between the end points without any troubles on the correct ports and everything looks just perfect - i.e. there is no any network issue, SIP communication (SDP related) issue or whatever like that
The possible problems for me are as follow:
- codecs issue - actually if you can make a call and the other side pick it up without the line to be dropped, then this is not the case (at least the codec on windows mobile is working)
- the audio output device - the audio is trying to go out trough a device which is not present on your system - so you are not hearing anything.
I will be glad to chat to anyone who have the same issue and can help me to debug the problem and find the permanent solution. I don`t have big knowledge on windows mobile devices (but at least know how to install cab files and modify the registry settings - hehe) so to anyone who is in deep relationships to this system and can help me -- give me your msn/icq/skype/jabber contact and lets pray together
Click to expand...
Click to collapse
I would be very much interested, how would you go about by debugin' this ?
salasbg said:
Hi Guys,
I am trying to run VoIP on my device (which is not athena by the way) and have absolutely the same issue. I have very good knowledge in the voip networks and very good experience and this thing makes me crazy (believe me)
As what i already found is there shouldn`t be any issue:
the RTP is going between the end points without any troubles on the correct ports and everything looks just perfect - i.e. there is no any network issue, SIP communication (SDP related) issue or whatever like that
The possible problems for me are as follow:
- codecs issue - actually if you can make a call and the other side pick it up without the line to be dropped, then this is not the case (at least the codec on windows mobile is working)
- the audio output device - the audio is trying to go out trough a device which is not present on your system - so you are not hearing anything.
I will be glad to chat to anyone who have the same issue and can help me to debug the problem and find the permanent solution. I don`t have big knowledge on windows mobile devices (but at least know how to install cab files and modify the registry settings - hehe) so to anyone who is in deep relationships to this system and can help me -- give me your msn/icq/skype/jabber contact and lets pray together
Click to expand...
Click to collapse
Hi!
I start by stating that I finally got it "working"! Yeahh! This "thing" costed me a hard reset and a lot of frustration. Let me write down what I think is the issue/"solution".
I say "working" because it is almost impossible to get the sound out of the Athena, unless you use a bluetooth headset (I haven't tried the wired one) and the supplied Voice Dialer.
To keep it short, for the Athena X7501 here is what you need to do to have "native" VoiP working partially as thought:
Connect the BT headset
Leave the Voice Dialer activated (Cyberon Dialer, provided in the original ROM). That means that the relevant entry in the registry shouldn't be set to '0': HKEY_LOCAL_MACHINE\SOFTWARE\OEM\VoiceCommand\LaunchAPEnable
Connect to your VoiP Servce and launch the phone. Now you should see your VoiP provider as agent. Dial the number (Good luck with the ipdialplan.xml) and you see that the Voice Dialer pops-up! Ignore it. The relevant communication port is happily already taken by the VoiP. You hear the sound on your bluetooth Headset. If you like, you can now transfer the sound to the speaker!
To my understanding, after having spent hours on this issue, I think that this is due to a DLL modified by HTC. Don't ask me which one. There is NO registry entry you can play with to solve it, unless you 're really lucky with the DLLs provided. It seems that there was some kind of agreement to make life very difficult to those trying to communicate through VoiP. I personally use VoiP only at home and don't bother too much. Maybe all this is history in the cooked ROM. Let's see.
If you don't need the Voice Dialer, then I suggest you use Fring. It works well both ways. However to use a Bluetooth Headset, you need to deactivate the Voice Dialer in the registry.
I hope this helps.
Rgds
Dod
P.S. The above are applicable to the original US Rom of X7501
There has been a discussion at Skype with respect to 6.1 and Skype failing to work correctly http://forum.skype.com/index.php?showtopic=112059
Maybe this might be of help.
Strange problem. Maybe you can try with software like fring.
Ran it on pk3 without any trouble and now running it with the 6.1 rom and still working fine
I'm not certain if this belongs here or in the WM6 forum, so mods please move if you must.
This question is for all of the chefs out there who cook ROMs for 6.1 and above. When doing your cooking are any setting changed with the bluetooth capabilities? I ask this because there are stark differences in how bluetooth functions when using the AT&T stock ROM and a cooked ROM.
I use, for example, my car radio, which has hands-free bluetooth capabilities. It also as the ability to download my contact list, call logs, and dial using the radio's remote control. However these functions only work on the stock ROM.
Whenever I flash a new ROM, no matter who the chef is, I lose most of those functions. Connection to the radio is very slow. My contact list is downloaded to the phone but not the call logs. Having the contacts in the radio does no good because I can't dial out from the radio, only from the phone and even that gives me trouble in that the phone's connection to the hands free is so slow, especially after making a call and trying another immediately after, which is never a prblem on the stock ROM.
Does anyone have an idea what the issue(s) could be? Could it be possible the bitpool settings were changed and if so what should it be to have it opened and optimized for the radio? Are there some type of change done to the registry?
I'd really appreciate if anyone could provide some guidance. I really love the new ROMs, but the issues with the bluetooth functions, as well as some new laws that have gone into effect here with regards to using cell phones now make it difficult to go without it.
Thanks in advance for any assistance.
Any ideas? Anyone?
Or am I missing something?
Hey wassup!
Well im new on chef world but this is related to the bluetooth car kit that is already answered in some other thread i suggest you to search about it... like "bluetooth car kit fix" or something like that no we dont touch BT its just the drivers that came from the new builds... i will search about that and see whats the problem youu must to search more too. and yes if you can post this on the unknown chef rom thread to let you know this issue.
In LG Optimus One endcall function does not work, so do not work correctly call blocker apps. Can this be fixed in a custom ROM?
telephonyService.endCall() function BUG
Hi everyone!
I confirm that there is a bug with telephonyService.endCall() function which consist in passing call to this function to nowhere, thus making ALL call blocking software useless, because they can't discard unwanted calls.
Can anyone fix this problem? I believe in you, GURU, take a look on this problem please.
With respect and hope, Max.
I really think this topic deserves a bump. And a solution.
Same problem here. End call function simply doesn't do anything on this phone making call blockers completely useless. I tried all O1 roms and even the original rom with the latest update and still doesn't work. Every call blocker says that call was blocked while you are watching it ringing.
By the way until someone comes with a fix, i found a temporary solution which requires Tasker or Settings Profile application.
If you want to send the blocked number to the voicemail, simply program Tasker to switch to airplane mode on and off or if you want to do the pick up and hang up action program Tasker to accept the call first then switch to airplane mode on and off.
As you can tell it will disconnect you from your network temporarily but Tasker is quite fast doing it so you will be on again very quickly. Putting your phone into airplane mode will end the call very quickly which call blockers can't do for this phone right now. You can do all these with Settings Profile too with the same steps.
Until a software fix, any other ideas are more than welcome.
(Unknown and private number value for Tasker is 0).
I have had the same problem and confirmed with Tasker developer that this is bug in LG Optimus One. Airplane mode is good solution if you do not protect your sim card with pin code. Else, after airplane mode is switched on and off, you will be prompted to insert pin and until you do so, your phone will not be reachable
I would prefer different solution...
I think we need to ask the guru to fix this problem. I said two weeks ago with mik_os about this issue, he replied that he might look, if not occupied by another.
Bump
This is something that is important as we cannot handle unknown calls.
If anybody has some solution, it would be appreciated.
I'm working on that.
For now I'd found by debugging phone with adb that endcall function really do something, but it seems that at the wrong time:
[ 02-16 20:27:52.451 1589:0x635 D/PhoneInterfaceManager ]
[PhoneIntfMgr] CMD_END_CALL: no call to hang up
Click to expand...
Click to collapse
That message appeared two seconds after we got the call (it's a mystery what phone was doing during those 2 secs), but before the framework starts to search corresponding contact to the calling number.
May be we have to wait several seconds after we get the call to invoke the encall() function again?
I'm a starter with android and I have not so much time for that, but I'm now trying to write a little program that will invoke endcall() function any time a want to prove/disprove my theory.
If anyone had written such program already, you can share sources with me to let me test that condition, or try it yourself.
UPDATE:
I've just tested it: there is no matter when you invoke endcall() function, the result is the same "[PhoneIntfMgr] CMD_END_CALL: no call to hang up". So digging deeper.
Last information from Android sources (how it should be in Android and doesn't work on our phone):
method handleMessage(Message msg) of class MainThreadHandler in PhoneInterfaceManager.java doesn't call method hangup(CallManager cm) of class PhoneUtils in PhoneUtils.java
Digging deeper...
First of all, that's environment I have:
- LGP500 device )
- "void" custom firmware
As I mentioned before, method handleMessage(Message msg) of class MainThreadHandler in PhoneInterfaceManager.java doesn't call method hangup(CallManager cm) of class PhoneUtils in PhoneUtils.java.
To check what's wrong I tracked that method to Phone.apk in /system/app/ directory of "void" custom firmware, which was grabbed from original LGP500 2.2 firmware, unpacked it and dedexed classes.dex file from it. To my great surprise I've found that it really omits call to hangup method of PhoneUtils class and do many things, that doesn't cross with Android sources. So LG programmers did their own "Android" with their own bugs. I have to say that it omits call to hangup method only for GSM call, but it has to be done for CDMA calls well.
I'll try to build Phone.apk from Android sources. This may take a while (maybe a week or so). Or maybe I'll edit dex file and repack Phone.apk with a new one. We'll see when I finally get some sleep
FYI, there is another way to block calls by diverting some call numbers to voice-mail. This is built-in Android function. That could be done in your phonebook by selecting a contact, pressing menu button, selecting options and checking "Incoming calls, Send calls directly to voicemail" checkbox. This way works more quickly than any other methods, used in callblocker software. So blocked caller immediately hear busy tone. I'll dig in sources how it works and maybe will find a better way for callblocking software.
Sorry for my English.
Thanks for your efforts noteb. The main reason that I want this function to work is to hangup on unknown caller id using Tasker. I am using company phone and cannot change my number. Let me know if you need any help.
Sent from my LG-P500 using Tapatalk
vault1965 said:
Thanks for your efforts noteb. The main reason that I want this function to work is to hangup on unknown caller id using Tasker. I am using company phone and cannot change my number. Let me know if you need any help.
Sent from my LG-P500 using Tapatalk
Click to expand...
Click to collapse
Of course I need help. What kind of help can you offer? Do you know how to build Android on Ubuntu 10.10? I've read couple of articles about that, but still it would be great if somebody familiar with that can join that topic. I'm familiar with linux only in network services administration and a little with programming in couple of languages.
BTW, I've found another bug in our LG firmware - Skype (and another one program, that I can't remember name of) can't switch sound to speaker. Instead it always playing sound (I mean voice of person you're talking with) through loud speaker. And again I think the problem is somewhere in standard *.apk files, which are Android framework.
Had anybody tried gingerbread?
Had anybody tried gingerbread from that topic http://forum.xda-developers.com/showthread.php?t=909242 ? Does it solve the problem? I'm currently reading that topic when I have time (there are a lot of words not in my native language) to decide whether it worth to be deployed on my device. Because of that currently I had stopped further investigation to solve the problem on froyo.
If anybody has some experience with that gingerbread build, let us know please.
I have flashed my phone with mik's Cyanogen rom and end call is working fine using tasker cyanogen-only press hardware key. End call will not be available in 2.3 as Google has removed call api's (read more on Tasker forum).
vault1965 said:
I have flashed my phone with mik's Cyanogen rom and end call is working fine using tasker cyanogen-only press hardware key. End call will not be available in 2.3 as Google has removed call api's (read more on Tasker forum).
Click to expand...
Click to collapse
Hardware EndCall works on our froyo with key remap also. I was asking is it API "endcall" function working (you can test it with simple "CallFilter" program from the market)?
BTW, that API works fine on Nexus One recently upgraded to gingerbread. So information about removing call api's is a fake. Also I can refute that information as I saw this API's in gingerbread sources with my own eyes.
I can confirm the API endcall function works perfectly in 2.3. Using CM7 for the ls670/optimus s.
cigman said:
I can confirm the API endcall function works perfectly in 2.3. Using CM7 for the ls670/optimus s.
Click to expand...
Click to collapse
Thanks for information.
Is there a solution for froyo? Or the problem can be solved only with cyanogen? I really wanted to block unknown callers :/
Sent from my LG-P500 using XDA App
migueel said:
Is there a solution for froyo? Or the problem can be solved only with cyanogen? I really wanted to block unknown callers :/
Click to expand...
Click to collapse
Try Gingerbread at http://forum.xda-developers.com/showthread.php?t=909242
It has to solve the problem
I just received this tablet with 3g stick - i would use it also for voice call not in internet but through the sim because i had a full phone plan with voice and internet -
i know that other tablet like sam.... with a software patch had enabled voice function -
we have to wait for a software upgrade or there is an hardware problem ?
in this case there is another usb modem with this function ?
thanks for your attention
newmave said:
I just received this tablet with 3g stick - i would use it also for voice call not in internet but through the sim because i had a full phone plan with voice and internet -
i know that other tablet like sam.... with a software patch had enabled voice function -
we have to wait for a software upgrade or there is an hardware problem ?
in this case there is another usb modem with this function ?
thanks for your attention
Click to expand...
Click to collapse
Hi There,
As far as I know the Archos 3G Stick is lacking voice capability at an hardware level so that is a no go, It theoretically possible using a Patched Huawei Dongle, I got it to successfully connect a silent call when I was playing around with it, It could be just a case of wiring up the audio policies in Android or something vastly more complex, I didn't bother investigating further. You also need to patch your framework-res.apk to make the rom voice_capable, you can also make it sms_capable as well, this allows you to use the stock mms app for sending and receiving messages
You might want to do a search before posting, because this question has been asked before and there's a couple of development threads regarding it, One is linked from my signature.
Thanks
trevd said:
Hi There,
As far as I know the Archos 3G Stick is lacking voice capability at an hardware level so that is a no go, It theoretically possible using a Patched Huawei Dongle, I got it to successfully connect a silent call when I was playing around with it, It could be just a case of wiring up the audio policies in Android or something vastly more complex, I didn't bother investigating further. You also need to patch your framework-res.apk to make the rom voice_capable, you can also make it sms_capable as well, this allows you to use the stock mms app for sending and receiving messages
You might want to do a search before posting, because this question has been asked before and there's a couple of development threads regarding it, One is linked from my signature.
Thanks
Click to expand...
Click to collapse
Correct. Sim cards do not have the phone radio in them. Its the device itself. Therefore, other than using voip phone apps there is no way to make voice call on the tablets, besides my galaxy note.
Sent from my ARCHOS 80G9 using xda app-developers app