Announcements

ILLEGAL CONTENT I'd like to just reaffirm MoDaCo's position regarding piracy and illegal content in the light of some recent questions / postings. Posts will be censored by myself or my moderation team if the contain or link to: Illegal / pirated / cracked software or sites that host such softwareNintendo emulators / ROMs or sites hosting them (in light of Nintendo's legal stance)CUSTOM ROMS You may discuss and post links to custom device ROMs on MoDaCo, provided the following rules are adhered to: ROMs must not contain any illegal 3rd party software (this includes trial versions included without permission)ROMs must give full credit to the original authorISSUES If you have any issues with this policy, please contact PaulOBrien directly via PM.

Please note that selling items on the forum directly is not allowed by the forum rules. There is a forum for eBay auctions whereby you can list the items on eBay and link to them there. This is the ONLY forum for this type of activity. You may also advertise links to the eBay forum in your signature. Please note that selling directly in contravention of these rules will result in a warning / suspension / ban.

Share this post

Link to post

Share on other sites

Vega does not have mini-USB, not even on the docking station. PC connection is through a USB-A to USB-A lead (large USB connectors on both ends). They are fairly standard to buy from third-party dealers.

And, it eventually fails. Please, check your logcat (main logcat) to see why the pppd daemon is failing to setup a working connection ... probably you are missing to suid-root the pppd daemon...

Hi again,

suid-root was not the problem. Parsing of pppd logs in ril was the problem (Amlogic pppd do have some extra output into logs so parsing logs for local/remote and dns addresses was not good - that part is solved now). Now connection is up (can be seen on USB dongle (LED indicating 3g link is up) and in logs), but ppp connection status is not forwarded to Android itself and within Android 3g is not useable. Under about, status it reports that data is up but no ip address available and no 3g/E/H on service indicator. Old ril (DerArtem's repo libhuaweigeneric-ril_old works for 3g, but does not work for voice/text receive...). I will digg little more but if someone have some idea it would be great :)

Regards

0

Share this post

Link to post

Share on other sites

suid-root was not the problem. Parsing of pppd logs in ril was the problem (Amlogic pppd do have some extra output into logs so parsing logs for local/remote and dns addresses was not good - that part is solved now). Now connection is up (can be seen on USB dongle (LED indicating 3g link is up) and in logs), but ppp connection status is not forwarded to Android itself and within Android 3g is not useable. Under about, status it reports that data is up but no ip address available and no 3g/E/H on service indicator. Old ril (DerArtem's repo libhuaweigeneric-ril_old works for 3g, but does not work for voice/text receive...). I will digg little more but if someone have some idea it would be great :)

Regards

Seems something is still missing in the log parsing. The RIL should get the local and remote IP from the log and forward them to android. That is the only required thing.. Make sure of that ;)

Edited 27 Oct 2012 by ejtagle

0

Share this post

Link to post

Share on other sites

Do you know if one needs to disable ril in Beta 6 on a Vega without an inbuilt modem. I get a message "sim changed" when I boot up the Vega, although there is no modem and no sim installed. I am wondering if the OS is continuiously trying to find the modem/sim and that explains the high battery usage?

Should not be required, but you are right. The RIL starts polling for the port every 5 seconds. It would be better to start the RIL only if a 3G modem is present. And, it is a very simple thing to do.

You need to modify the init.shuttle.rc, and add the following section

# When a 3G modem is plugged in or removed, reinit RIL ... Otherwise, improper tty names are generated, as port is still in use by RIL...

on device-added-/dev/ttyUSB0

start ril-daemon

on device-added-/dev/ttyUSB1

start ril-daemon

on device-added-/dev/ttyUSB2

start ril-daemon

on device-removed-/dev/ttyUSB0

stop ril-daemon

on device-removed-/dev/ttyUSB1

stop ril-daemon

on device-removed-/dev/ttyUSB2

stop ril-daemon

So,when you disable the 3G modem, the RIL is stopped, and when you reenable it, it is restarted ;)

Share this post

Link to post

Share on other sites

Sorry to derail the current conversation. We're still having issues w/ HD video on our 3.1 kernel. All our avp code is the same as what scanno has on his git. I'm looking back through clocks and this is what you guys have active.

Share this post

Link to post

Share on other sites

Sorry to derail the current conversation. We're still having issues w/ HD video on our 3.1 kernel. All our avp code is the same as what scanno has on his git. I'm looking back through clocks and this is what you guys have active.

Share this post

Link to post

Share on other sites

But the source code of the kernel is bublished. Why isn´t it possible to add OC functionality?

Of course its possible, just no one is interested in doing it or at least has been interested in doing it ... Until this point stability was key and way more important than a few extra mhz.. undervolting is probably much more interesting...

1

Share this post

Link to post

Share on other sites

But the source code of the kernel is bublished. Why isn´t it possible to add OC functionality?

Of course its possible, just no one is interested in doing it or at least has been interested in doing it ... Until this point stability was key and way more important than a few extra mhz.. undervolting is probably much more interesting...

The answer is easy: We still have some stability issues. There are tablets that show strange behaviours. We don't want to add another cause of troubles here. And, just to be honest, i consider adding overclocking to the tegra2 kernel a bad idea. There is no cpu temperature sensor on the P10AN01. You can easily fry your tablet... There is no provision for evacuating the extra heat generated by the overclocked chipset. Look on this same thread for an extra detailed explanation on why we chose not to implement OC as a default, why it should not be offered to people that are unaware of the implications of overclocking (read: If abused, you WILL BURN your tablet! ...) ..

Share this post

Link to post

Share on other sites

You have to choose - latest rom, or OC. If overclocking is what you want, you can use Corvus, which I tihnk overclocks to 1.5. HoneyIce Chimera I think overclocks to 1.2. But if you want Jelly Bean, you have to use VegaBean Beta 6 without overclocking. The reasons were explained by ejtagle and Cass67.

Well, i have had such problems, but not on the p10an01 (as far as i can tell, has no eeprom...) ... The problems that i had were on the p10an10 (that DOES have the eeprom)... Not sure about LP0 problems... Did you manage to get a last_kmsg from the kernel when shutting down ? .. It could give a clue ...

0

Share this post

Link to post

Share on other sites

We are trying to build CM10 for samsung galaxyR-I9103. HW acceleration is not working, using Nvidia codec, it says "failed to allocate node" in OMXCodec.cpp. Tried with the changes of DerArtem(used for ICS), but it didn't worked, same error.

Also avp_init won't get performed in our kmsg.

Please help us.

If I posted wrongly, please forgive me! This is my first post in the modaco!!!

Edit: the ejtagle libraries helped, now Hw accelration is working!!! Thanks a million!