yashsingh1/xdaforums huggingface dataset:
[Gen9, Gen10 General] x3ss:
no problem trevd, this is another way to learn even more stuff :)

Do you see anything interesting in cajl's dmesg?

I don't see a tty# assigned to his 3G stick nor the usb_modeswitch output.
[Gen9, Gen10 General] trevd:
I like that outlook, it's exactly how I see it. I know as much about what doesn't work as what does :)

Anyway there's nothing going on regarding mode switching in that boot sequence, It's just kicking up it's default mode.

I'm thinking it's probably doing it's magic In android it's self and you might gain some

insight from looking there.

I've been playing with the archos 3g stuff lately as I want to enable any dongle on the device.

I was originally going to patch UsbKeyManager.apk in the system/app folder as this is where everything happens with regards to the archos stick (It Seems! :) ) - The Apk does the modeswitching and starting/stopping of the Android Radio Interface Layer (ril) , which is along with your modem drivers and pppd (?) is all you technically need to get a connection through Android to the outside world

If you haven't already doing getprops from the command line will give you an insight into what android thinks it's got and have a look at logcat to monitor what's going on.

I'd Reset the modem back to how it was and try it in the unrooted stock to see if it works......It's suppose to, right. :) lol

I'd probably try all the different combination of modeswitch, but that's is very much at your own risk. :)
[Gen9, Gen10 General] x3ss:
I decompiled classes.dex from UsbKeyManager.apk and i'm looking through the .class files but i don't know java so i understand very little from it...

I've attached the .class files if someone knows how to read them better...
[Gen9, Gen10 General] x3ss:
just tried your modprobe method and is not producing any output.

none in dmesg and none with -v option.
[Gen9, Gen10 General] iourine:
Hmmm... really, my regular machine with Ubuntu 11.04 (kernel 2.6.38) sometimes work, sometimes not - I cannot figure out the reason yet. Test machines with 3.0 and 3.2 kernels appear to work... 3.0 still freezing sometimes.

x3ss, which kernel do you use?
[Gen9, Gen10 General] x3ss:
I used the 2.6 kernel that the tablet has but it's limited by the busybox installed and the modules on the g9 by archos..they have some checks of the software level and somehow they block my device to register in the system as a ttyHS# device
[Gen9, Gen10 General] cajl:
Great job !

Thanks
[Gen9, Gen10 General] scholbert:
Thanks for appreciation... but we should thank the authors of apktool.

Anyway this might be a start for some hackers out there :p

...some who in fact are familiar with smali!

I'm pretty sure that other Alcatel sticks could be used after tweaking UsbKeyManager.

There might be different ports (device nodes) to be set though.

The ril library on the G9 is compiled from source code of TCL (Tanta Communication Ltd.), which belong to the Alcatel group or vice versa.

And as you might know, Alcatel is the supplier of the stick.

Manufacturer of the hardware in fact is TCT mobile a chinese manufacturer for data modems and stuff. They mostly use a Qualcomm chipset for their designs.

Concerning hardware, the Archos 3G stick is very similar to X220 or X225 from Alcatel stock series.

If we look over to integrate other hardware, e.g. Huawei, it might be necessary to build our own ril library. See this project for some insights:

https://github.com/DerArtem/huawei-generic-ril

BTW, there are some kernel drivers required as well. This is already covered by the thread i mentioned in my previous post ;)

See ya!

scholbert
[Gen9, Gen10 General] trevd:
@scholbert

It's pretty much what I had figured out, although putting it into to words is not always my strong point. :)

I have managed to bring up a ppp interface on a huewai modem on ICS, However I seem to have ran In to some ppp connection script issues at the moment and I have not played around with it for a couple of weeks :(

Here is what I think I know! :)

I've been testing on an 02 UK branded Huawei E1752 which I got the connection on.

I also bought the Archos Dongle to have a look at what it was doing and also is the reason why my motivation to get other dongles working kind of decreased.

I picked up a T-Mobile Huawei E173s which I've not managed to modeswitch correctly yet - I'm still looking for the right config script.

Notes On UsbKeyManager:

The apk has some Interfaces defined in other libraries (probably the archos framework jars) so decompilation proved a bit of a pain. Although, like you mention, a straight up smali hack will do the trick :)was going on with it,

The UsbKeyManager seems to have these main tasks which is achieved using system services

1. React to the Archos 3G Stick Connection Only and UsbModeSwitch to the modem using switch_ms_to_3g service

3. Set the rild.libpath and rild.libargs properties (these are normally set at boot in the system/build.prop file on other devices

4. set the ril-pppd_tty properties so the pppd connection function properly

5. bring up the datakey pppd interface using the pppd_datakey service

5. Start Rild with the correct parameters using ril-daemon service

All things being equal the UsbkeyManager could probably be removed and replaced with a custom app which achieves the same goals.It is a lot less noisy on logcat without the usbkeymanager installed.

It seems to like tickling, I'm not laughing :D [Example Output:] I/Key3GService( 948): Tickling USB bus

The System Services are registered in the init.rc and /etc/init.d/init.<product>.rc

init.<product>.rc is also the place where the kernel drivers are installed when the device is booting

Archos have a "special" intent registered ( archos.intent.action.USB_DEVICE_ATTACHED ) which is sent from the usb settings manager which may be worth a listen to.

In Summary:

A good test, and one which I will try;

Remove the UsbKeyManager.apk

Manually bring up the Archos Datakey PPP Connection using either the system service method or more manually running usb_modeswitch and the scripts in /etc/ppp

If that is successful you should be able to use the android browser to browse the internet although android will report no connection.

Note: Most of this is written from memory so apologises if some of the info is off.
[Gen9, Gen10 General] trevd:
Hello Again.

I started running a couple of tests and I've managed to get the archos 3g dongle to connect manually

I removed the UsbKeyManager.apk and ran the following commands with the Archos Dongle plugged

A little bit of hacking in an adb shell resulted in me having to run the following

setprop net.dns1 82.132.254.3 ; setprop net.dns2 82.132.254.2 ;

setprop ril.use_data yes ; setprop gsm.sim.state READY ;

setprop rild.libargs "-d /dev/ttyHS3" ; setprop ril.pppd_tty /dev/ttyHS4 ; setprop rild.libpath /system/lib/libtcl-ril.so ; usb_modeswitch -c /etc/usb_modeswitch/1bbb_f000 ; start pppd_secrets ; start ril-daemon ;

The Dns servers on the first line are the ISP you are trying to connect to.

I'll explain more soon and give the Huawei dongle another try :)
[Gen9, Gen10 General] scholbert:
Hey trevd!

Thanks for this information. It seems there are only a few fiddling around with this stuff.

Yeah, i read your posts. Great work!!

Yupp, if it's working there's no need to change it :D

This far beyond the information i gave... Thanks for this insights!!!

Your brain is in a good shape :p

Thanks again!!

Wow, that's awesome. This description gives a good understanding what's happening under the hood.

If i where a good programmer i would start to write an extented USBKeyManager (with USSD support as well), but this is far beyond right now.

BTW, i asked one of the Archos software engineers for the libtcl-ril api, maybe they are willing to hand out something...

Do you know how USBKeyManager sends and receives commands to/from this library?

There are some tokens in the smali code...

Is the rild always involved?

Thanks for these great postings :)

Best regards,

scholbert
[Gen9, Gen10 General] trevd:
scholbert, Firstly, thanks for the kind words.

But Wait There's More

I remembered that the UsbKeyManager also performs the important task of powering on/off the UsbPort through rfkill functionality, I'm not sure about the exact behaviour but I suspect that this maybe why some folks have intermittent Usb Device Connection issues, but that's another story :)

the rfkinit service, which is essentially a wrapper for /system/bin/rfkill_chmod.sh seems to handle the power for usb devices, I also think that the [persist.ril.rfkswitch] system property might be of some importance/use although this is just a guess at the moment

I don't think good comes into it :) but that's just semantics :p It's should be fairly trivial (famous last words) and you can pretty wrap it up in a script as per that shell commands from my previous post

I did write a little Android Interface to handle the manual switching while I was testing, It also contained a service which registered on boot. That may evolve into something as yet.

I'm going to see if I can make any progress with my Huawei (wwan) dongles (now that I've topped them up :o )

I think there maybe some more drivers need for the Huawei e173s I have because It is control via cdc_acm and mounts at /dev/ttyACM* .

I'm still yet to confirm this but my research leads me to that conclusion.

All of which leads nicely onto

I'd be surprised if they do, however this is not something you need to worry about. the *-ril.so library are part of the android framework and have similiar implementations across all devices

I just grabbed a binary version of the libhuawei-ril.so from my tests with HoneyComb and I'm going to use this one for the ICS tests.

So thanks to all the people who solved this problem on numerous devices in the past :)

It is the rild executable which is controllled through the ril-daemon that handles all the connection side. The UsbKeyManager just powers on the device, mode switches it and sets up the properties ready for rild to take over.

This kandroid.org page might aid your understanding of how it all fits together.

Considering Telephony and connectivity are large parts of android, the documentation on this area seems very light and alot of the time all there seems to be is the code. :(

You can find plenty of 3g Hacks for other devices, I used this one for the Acer Iconia as a starter.

It's always worth looking to see what people are doing with other/similiar devices. It's a easy source of prebuilt binaries alot of the time :)

I hope this helps, in your quest. I will update with my other dongle testing. I don't really want to get into the finer points of pppd configurations but I feel I may have to If this testing doesn't go to plan!:D

Thanks

Trev
[Gen9, Gen10 General] scholbert:
some more research...

Hi geeks,

i know this is an old thread but there's something to add :fingers-crossed:

So here's some additional information about he Archos 3G stick i collected in the meantime.

Archos 3G USB Device:

Bus=USB\VID_1BBB&PID_00B7

USB endpoints (Windows PC):

Diag=USB\VID_1BBB&PID_00B7&MI_00	(Application Port 1)
Nmea=USB\VID_1BBB&PID_00B7&MI_01	(Application Port 2)
Voice=USB\VID_1BBB&PID_00B7&MI_02	(Application Port 3)
AT=USB\VID_1BBB&PID_00B7&MI_03	(Application Port 4)
Modem=USB\VID_1BBB&PID_00B7&MI_04	(3G Modem Interface)

As already stated Port4 (in Linux /dev/ttyUSB3) gives full AT command interface.

Playing around for a while...

The ATI command gives general information of the module:

Manufacturer: TCT Mobile International Limited

Model: HSPA Data Card

Revision: S21B47S1XX

IMEI: 3576320xxxxxxxx

+GCAP: +CGSM,+DS,+ES

The command AT+CLAC gives full AT command set (always add leading AT):

&C &D &E &F &S &V &W

A D E I H L M O Q V X Z T P

\Q \S \V

%V

S0 S2 S3 S4 S5 S6 S7 S8 S9 S10 S11 S30 S103 S104

+FCLASS +ICF +IFC +IPR +GMI +GMM +GMR +GCAP +GSN
+DR +DS +WS46
+CBST +CRLP +CV120 +CHSN +CSSN
+CREG +CGREG +CFUN +GCAP +CSCS +CSTA +CR
+CEER +CRC +CMEE +CGDCONT +CGDSCONT +CGTFT
+CGEQREQ +CGEQMIN +CGQREQ +CGQMIN +CGEREP +CGPADDR +CGDATA +CGCLASS +CGSMS
+CSMS +CMGF +CSAS +CRES +CSCA +CSMP +CSDH +CSCB
+FDD +FAR +FCL +FIT +ES +ESA
+CMOD +CVHU
+SSND +SYSSEL +HSXPAEN +CGEQNEG +PNNM +SPNM +SPDI
+FUNC +CRCFG +CDFC +NCID +IMEISV
+TRACE +SMPN +SMNW +SMLK +STIN +STGI +STGR +VTS
+CUREF +CSQ +CBC +CPAS +CPIN +CMEC +CKPD +CIND +CMER
+CGATT +CGACT +CGCMOD +CPBS +CPBR +CPBF +CPBW +CPMS
+CNMI +CMGL +CMGR +CMGS +CMSS +CMGW +CMGD +CMGC +CNMA +CMMS
+CHUP +CCFC +CCUG +COPS +CLCK +CPWD +CUSD
+CAOC +CACM +CAMM +CPUC +CCWA +CHLD +CIMI
+CGMI +CGMM +CGMR
+HWV
+CGSN +CNUM +CSIM +CRSM +CCLK +CLVL +CMUT +CLCC
+COPN +CPOL +CPLS +CTZR +CTZU +CLAC +CLIP +COLP +CDIP +CTFR +CLIR

$QCSIMSTAT
$QCCNMI
$QCCLR
$QCDMG
$QCDMR
$QCDNSP
$QCDNSS
$QCTER
$QCSLOT
$QCPINSTAT
$QCPDPP
$QCPDPLT
$QCPWRDN
$QCDGEN
$BREW
$QCSYSMODE
$QCCTM

Also USSD commands are supported, e.g.:

at+cusd=1,"*100#"

The response gives the balance of your pre-paid card.

Again, it would be awesome to get this integrated into USBKeyManager somehow...

What's inside the housing?

See below...

The data modem is built around MSM6290 chipset. Fhe firmware is stored in a Hynix NAND/SDRAM combination.

It does look pretty much like a OT-X22x series data stick from Alcatel and it pretty much is!

Except from the firmware, which might be specifically designed for Archos.

There's a Micro-SD slot underneath the SIM card holder, but right now i don't know if it could be activated.

EDIT:

Did a little research on this issue and it seems that some 3G sticks could be used as a MicroSD reader by using usb_modeswitch sequence.

I doubt that this makes sense for our tablets, if it will even work.

Stay tuned!

scholbert
[Galaxy Tab 8.9 General] the Doctor:
Like everyone else, I'm closely following the development of ICS ROMs for my SGT 8.9. Truth be told, I've been running Galaxian Soup for the better part of two weeks now, really enjoying the clean look of the stock Android interface and lack of TouchWiz bloat.

But I'm also concerned about performance because, well, I'm a geek. So I decided to benchmark the two ICS ROMs under development against the stock TouchWiz 3.2 ROM to see how they stack up. The contenders are the Galaxian Soup Beta 1.4 and unofficial CyanogenMod 9.

Method

Each ROM was tested 7 times with AnTuTu Benchmark so as to accumulate data. The first run was thrown out in each case as the first run with AnTuTu tends to be slower. Thus I collected and reported 6 runs for each ROM. Standard deviations were calculated and recorded to see how consistent the ROMs are in each area, and the mean scores chosen to represent each ROM. I did not overclock in Galaxian Soup or CM9, so the clock speed was 1ghz in each case to keep the playing field level. I almost forgot to mention that I ran the benchmark on a Honk Kong market GT-P7300 WiFi/3G.

Results (Scroll down to see totals)

TW 3.2	GS ICS B1.4	CM9 ICS
Mean	+/-	Mean	+/-
RAM	817	826	1%	702	-14%
CPU Integer	1421	1432	1%	1405	-1%
CPU float-point	1091	1098	1%	1111	2%
2D graphics	293	295	1%	262	-10%
3D graphics	904	627	-31%	616	-32%
Database IO	354	325	-8%	334	-6%
SD card write	115	129	12%	131	14%
SD card read	191	191	0%	187	-2%
Total score	5186	4922	-5%	4749	-8%

The results speak for themselves. Both ROMs being in alpha or beta status have some work to do, especially in the area of 3D graphics. But we know the devs are working on a host of issues (not to mention that they have lives of their own!), so let's be patient. On the other hand, both ROMs bring a lot to the table in terms of SD card write performance! As the devs put newer releases out there, I'll update the results here to see how they are coming along.

In the meantime, thanks to the devs for working hard on these for the community. Both ROMs look great and deserve a look! :D
[Galaxy Tab 8.9 General] pseudoheld:
Although these stats throughout show a performance loss, let me assure you that in the daily use it feels a lot faster and smoother!
[Android Q&A, Help & Troubleshooting] ce4ko:
I have a problem with my HTC Wildfire S.

From several days the display lightens in random intervals. Do you have any ideas what can make this happen? It just shows the lock screen for a few seconds and then again goes to stand by...
[Android Q&A, Help & Troubleshooting] Janzomaster:
Best ask you question here, they know you device the best: http://xdaforums.com/forumdisplay.php?f=1035
[Android Q&A, Help & Troubleshooting] jeyaganeshan.s:
i am also facing the same problem...

did u get it resolved?
[Android Q&A, Help & Troubleshooting] finance.resat:
U just need to add a line to build.prop. search for it u may find it. It happened to my phone after I s-off my phone (its also wildfire s). And I suspect my proximity sensor is collapsed. May be the same case with you.

Open es file explorer

Go to system/build.prop

Add a line (gsm.proximity.enable=false)

Without bracket. Restart.

You should search about it and confirm first. I did this to my wildfire s. When u do it will be at your own risk and responsibility. It should disable the proximity sensor.
[Android Q&A, Help & Troubleshooting] finance.resat:
Also I think its just happening because u enabled automatic brightness. Try display settings. Set a fixed brightness. That will help for sure.
[Desire Q&A, Help & Troubleshooting] kiwi3456:
Can someone let me know the ICS ROM for HTC Desire which has Qualcom Hardware decoder enabled.

All CM and MIUI ROMs seems to use software decoder with hardware acceleration hack.
[Desire Q&A, Help & Troubleshooting] danarama:
Have a look here:

http://xdaforums.com/showthread.php?t=1355660

Not sure how, but they say they have full HWA now.
[Desire Q&A, Help & Troubleshooting] kiwi3456:
I tried it. But it still uses software decoder.
[Desire Q&A, Help & Troubleshooting] danarama:
In which case, nothing will be using it. Dont forget we havent got driver source for GPU.
[Desire Q&A, Help & Troubleshooting] Undermyoath:
But you guys are making petitions to Qualcomm for getting those, isn't it?

Maybe i should write a letter of supporting too,

The many, the mere eh! ;D
[Desire Q&A, Help & Troubleshooting] danarama:
I actually e-mailed them the other day. They simply didn't respond.
[Android Q&A, Help & Troubleshooting] kinus:
hi, does anyone knows application that will notify me, when i recive forwarded call?

thanks in advice
[HD2 Windows Phone 7 Q&A, Help & Troubleshooting an] peterjr1:
My UP volume button broke ages ago and until recently i have been using android and in android there were ways of turning up the sound, however android is no longer working on my phone so i switched to wp7 which i love :D but the sound is on 0 and i cant turn it up?? this is a big problem for me as my phone is also my main music player?? does anyone know of any way of fixing this??

thanks in advance :)
[Android Q&A, Help & Troubleshooting] angrymoose:
Hi,

I can't find a support section on this site for the Motorola Fire, I wonder if anybody will post an Ice Cream Sandwich ROM for it?

Cheers,

Craig
[Android Q&A, Help & Troubleshooting] raiden93:
Same request, how can i update my Gingerbread 2.3.5 to Ice Scream Sandwich 4.0?

Can we get a complete tutorial and link for this upgrade?

Waiting for answer,

Bye.
[Android Q&A, Help & Troubleshooting] raiden93:
Upp
[LG Optimus Black] maludroid:
Hi,

U am wondering why do people advise to perform couple of reboots before custom roms start working optimally. I am a bit computer engineer and I can't imagine, what can happen after e.g. third reboot, that didn't happen before (unless you provide reboot counter), and what could speed up the device (or something).

Can anyone elaborate it?
[LG Optimus Black] Pondera:
Well... One time makes sense. You install new things, for them to fully activate a restart hence the reboot is logical. May be there is something to it that i don't know but i don't see how multiple reboots help... Some hardware becomes optimized after used for a while but software... Interesting. I'd like to know too. A
[LG Optimus Black] officialreloaded:
Well, when you shift to a new rom, the dev always insist to wipe the dalvik cache for clean install. So, at first boot, it is built. But after the first boot, when the system loads to a working state, all the services are automatically configured as per their functions and defaults. I mean, not the configuration of an app, but the settings and services (and perhaps their cache files as well)..... which should be playing a major impact, so that after next boot this doesn't repeat and device load fully optimized all the next reboots.

This may also be correlated as to why very often you don't need to wipe dalvik cache while upgrading existing rom; but you should always while trying a different rom.

cmiiw. :)
[LG Optimus Black] coxy47:
I agree that I dont quite understand why that is the case but it seems to help.
[LG Optimus Black] mdfaisal:
I gree too...

But it just me or anybody else feels diffrent -in term of good way- after couple of reboot. it just make my zeus work optimal especially in battery efficiency. :rolleyes:
[Atrix 4G General] nthon9:
I cannot stand the fingerprint sensor/power/lock button. Just because, it's ridiculously placed. If it were on either side - fine, that's good, I don't have to hold my phone like a tennis ball.

The placement isn't the main reason I hate the thing, though.. I have two more reasons - reasons which may be resolvable (input appreciated in that department :))

1. When you try to unlock the phone, the backlight comes on, but no display.. Have to lock and unlock again. Also happens when ending calls sometimes. - multiple ROMs.

2. ABSOLUTE WORST THING IN THE WORLD - makes me want to inject battery acid in to my eyeballs - fingerprint sensor navigation (as seen in cm7/cm9) - WHYYYYYYYYYYYYYYYYYYYYYYYYY DOES THIS EXIST? Not only will it be randomly navigating the screen whenever a finger goes near it, but every time you want to lock the screen - you first have to see an ugly yellow selection indicator fly across the screen.

The good thing about fingerprint sensor navigation is that you can disable it. The bad thing about fingerprint sensor navigation is that its settings in jokersax11's CM9 are seemingly unavailable.

"com.authentec.Truesuitemobile has stopped working."

I guess this is just me ranting. It is rather annoying, because the CM9 mod in question is rather cool, and I'd love to use it, but I can't ignore that annoying fingerprint sensor navigation. :mad:
[Atrix 4G General] kennytung:
I think there are mods around that can make you use the volume button as unlock button, also you can try other lockscreen app that can simulate this also.

1. I have no issue with this. Have tried many ROMs.

2. I think disabling the navigation should not make any problem, somethings must be wrong with your setup. But I have only used CM7, haven't try CM9 yet so not sure if CM9 behave differently with this disabling fingerprint navigation.
[Atrix 4G General] nthon9:
The problem with using the volume keys to unlock is that I use my phone as an mp3 player, and actually use the volume controls while the phone is locked in my pocket - though I have tried it, and I don't have the issue with the screen not waking properly when I do. ;x
[Atrix 4G General] firefreak664:
Here's a thought

If u don't like it that much get an Atrix 2. Not trying to be a **** but it's a thought.
[Atrix 4G General] nthon9:
The rest of the phone is great, though.

& the Atrix 4G seems to outperform the Atrix 2, so I don't think that'd be the phone I'd consider, if I were to make a change. ;o
[Atrix 4G General] celli123:
I have no problem with the placement of the fingerprintreader/unlockbutton and i have absolutly normal hands.

But the problem with the fingerprintnavigation can be solved easily.

Just go to setting-device settings- fingerprint sensor navigation and change "NAV Enable" to disable.

And after a restart your problem is solved.

But in the moment this is only possible with CM 7 , in CM 9 you can't disable it in the moment.