Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

1 Neutral

About univall

  • Rank

Profile Information

  • Your Current Device(s)
    Viewsonic 10s 3g
  1. Thanks for pointing the above out. It is losing signal strength as it is getting in to standby. I recollect that it was happening with the earlier beta also. Also, not getting the '3g' or 'H' icon as in earlier beta.
  2. Eduardo, Wondering if you could have a look over at the logcat I am posting for Scanno's VegaBean Beta 6. This log is posted from after a couple of reboots on an Nvflash Rom flash. Everything seems to work fine but I tend to lose the mobile network from time to time. The network comes back on mostly after a few (8-12) seconds always. I am sure it is not the mobile network here because it works absolutely fine with the earlier beta and the Beta 5. I will keep this ROM for sometime; so if you need any further logs, please advise. Thanks in advance. FYI, I am on a Viewsonic internal 3g modem EM770W. radio-logcat-vegabean-beta6-nvflash.txt
  3. [Edit] Well, checked for volume increase on view pad 10s. Still very faint on the tablet. On the phone side, there is a lot of feedback/echo with some latency
  4. Hi. - 3g works - to airplane mode and back, no issues with 3g or phone - suspend and back, no issues with 3g or phone - tablet in sleep, incoming call wakes up tablet, no issues with 3g or phone - not sure about voice volume, unable to fully test. HTH.
  5. Ah! Would've loved to have tested this. Not near my dev machine. :-)
  6. You seem to be getting somewhat better audio as well as better dial-out performance than I am on the Viewpad 10s. Wonder if I should try with another service provider as it may have something to do with cell reception in my area. Just wondering if that would affect the quality of voice/other sounds in the call. Is noise cancellation already built in the RIL specific to the hardware or not possible with the EM770W that we have. The tablet unlike a smaller phone is held some distance away and may be more susceptible to ambient noise distortions. Not only 3g, even the phone features work only in awake mode. Cannot receive call or SMS when sleeping as the modem switches off. When the tablet is brought back from sleep, the cell signal indicator is blank or greyed out and takes a while to come back. If the sleep has been long, say over 3-5 minutes only a reboot can bring the cell network back on. To counter this, I increased display time out to 30 minutes or more... no issues now for cell network, but battery runs out faster. Battery discharge can be extended a bit in this case by reducing the screen brightness to as low as possible so as to be able to see clearly. :-)
  7. Ok. libhuaweigeneric-ril.so in attached archive. libhuaweigeneric-ril.so.tar.gz
  8. will post test reports soon. please note that on compiling I am seeing (just a fyi) --- No private recovery resources for TARGET_DEVICE shuttle target thumb C: libhuaweigeneric-ril <= device/nvidia/shuttle/huawei-generic/agc.c target thumb C++: libhuaweigeneric-ril <= device/nvidia/shuttle/huawei-generic/audiochannel.cpp target thumb C: libhuaweigeneric-ril <= device/nvidia/shuttle/huawei-generic/audioqueue.c target thumb C: libhuaweigeneric-ril <= device/nvidia/shuttle/huawei-generic/echocancel.c target thumb C: libhuaweigeneric-ril <= device/nvidia/shuttle/huawei-generic/huaweigeneric-ril.c device/nvidia/shuttle/huawei-generic/audiochannel.cpp: In function 'void* modemAudioIOThread(void*)': device/nvidia/shuttle/huawei-generic/audiochannel.cpp:121:25: warning: comparison between signed and unsigned integer expressions [-Wsign-compare] device/nvidia/shuttle/huawei-generic/huaweigeneric-ril.c: In function 'decodeUSSD': device/nvidia/shuttle/huawei-generic/huaweigeneric-ril.c:5921:2: warning: pointer targets in return differ in signedness [-Wpointer-sign] device/nvidia/shuttle/huawei-generic/huaweigeneric-ril.c: In function 'requestSendUSSD': device/nvidia/shuttle/huawei-generic/huaweigeneric-ril.c:6243:2: warning: pointer targets in passing argument 1 of 'strlen' differ in signedness [-Wpointer-sign] bionic/libc/include/string.h:52:15: note: expected 'char const *' but argument is of type 'cbytes_t' target SharedLib: libhuaweigeneric-ril (out/target/product/shuttle/obj/SHARED_LIBRARIES/libhuaweigeneric-ril_intermediates/LINKED/libhuaweigeneric-ril.so) target Symbolic: libhuaweigeneric-ril (out/target/product/shuttle/symbols/system/lib/libhuaweigeneric-ril.so) target Strip: libhuaweigeneric-ril (out/target/product/shuttle/obj/lib/libhuaweigeneric-ril.so) Install: out/target/product/shuttle/system/lib/libhuaweigeneric-ril.so [EDIT] Difficult to be completely sure but this seems to be better but not by a big margin -- 1) The call from tablet to phone did engage for longer but ended on its own in about 5-7 seconds 2) On the call made from phone to tablet: - - The call takes a while to kick in after one accepts the call - There are a lot of crackling noise/sounds - The latency seems to have improved but the voice-sound is still lagging - The voice on call coming off from the tablet speakers is faint. On the wired headphone is a bit better but with more 'bass' than expected needs more 'treble' or a somewhat higher pitch - USSD is fast and you seem to have removed the @@@ from the response, so is neat. All in all seems better than last one, but do not have a yard stick so I will make one. If the previous one was 1/5 :: this one is 1.5/5. Maybe I am a little generous with the rating. ;-) Someone else might get better results. Do you recommend I post the *.so files as requested by Arja above. Could you tell me which files should be posted that would help him run tests that will be useful to us/you. log691.txt
  9. My primitive Nokia bh-200 Bluetooth headset is paired but I am not sure if the headset services are on. Maybe we can request Eduardo to look at the Bluetooth interface layer next. :D Suggest you should try without a headset or with a wired headset. Since we are on a similar hardware, it will be interesting to compare notes. Also, looking at Scanno's GIT status, not sure that he got the latest RIL from Eduardo in to the device tree and thus, Vegabean 2.3 maybe a small step behind from what is currently being tested.
  10. Agree in toto. Trying it with a wired headphones. Same observations as above. But it is exciting to see this is working!
  11. Attaching logcat -b radio. Dialing out ends immediately. Call in to the tablet established, volume is louder, good enough to hear from about 3-6 feet away from the tablet. But there are too many overlapping sounds including a continuing ringing of the call in spite of accepting it. It takes a while for the call to kick in and there is latency but somewhat better than the earlier version. This may need more intensive checking though. log-v3.txt
  12. Few observations -- - Call dialed to tablet -- ring received on tablet, call established after a while, voice going through from the tablet to the phone but with a big (~5 seconds) latency and faint volume. The microphone icon is crossed out. - Call dialed to phone - call ends abruptly. Compared to earlier, the modem is not hanging anymore. More tries to call are possible but with similar results. The speaker button is on mute when the call is dialed. On setting the speaker button on, hear a crackling sound much like the one heard at the time of reboot at the lock-screen. Call ends quite abruptly and soon, no chance of really checking if there is sound/voice on the call. But, I did hear the call end sound off the tablet speaker maybe two or three times. The microphone icon appears crossed out in the phone screen. - 3g connection is somewhat stable and comes back on quite fast after a short idle - display time out. But after a long idle of 3-5 minutes, either hangs or takes a long while to come back on - entirely unpredictable. Needs a reboot to function again.
  13. testing, will revert asap... USSD works just fine!! Will post a logcat -b radio for academic interest shortly. :D radio-ussd-works.txt
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.