LG Thrill

[GoogleCodeExporter]

Which device (manufacturer, type)?
LG Thrill
Which firmware is installed?
2.2.2
What version of wireless tether are you using?
3.1 beta 6
What steps will reproduce the problem?
1. Start tethering
2.
3.

What is the expected output? What do you see instead?
Wifi network doesn't show up. Probably not supported on this phone it's new. 
Just a heads up.
Please provide any additional information below.

Original issue reported on code.google.com by ZZE...@gmail.com on 9 Sep 2011 at 5:27

[GoogleCodeExporter]

It seems like the Thrill, using stock rom, will only allow connections to WiFi 
routers and not other devices via Ad-Hoc. I used my Tilt2 with WiFi Router and 
the Thrill will not tether to the Tilt2. If there's a way to enable Ad-Hoc on 
the Thrill, WiFi Tether will work.

Original comment by ChungLiu...@gmail.com on 23 Sep 2011 at 6:32

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Thrill has an OMAP4430 SoC, and what appears to be support for softap/hostap in 
the much the same manner as the Droid X.  Starting the AP up does appear to 
engage the built in tethering like it does on Droid X running stock 
Gingerbread. BTW, I don't have this phone, just got to poke around on a Thrill 
for a minute.  It also didn't have a SIM so not sure if the AP was passing 
data, but I could connect to it.

# wlan kernel module location
/system/etc/wifi/softap/tiap_drv.ko

service wlan_ap_loader /system/bin/tiap_loader \
    -i /system/etc/wifi/softap/tiwlan_ap.ini -f /system/etc/wifi/softap/firmware_ap.bin -e /data/misc/wifi/nvs_map.bin
    disabled
    oneshot

service hostapd /system/bin/hostap -dd /data/misc/wifi/hostapd.conf
    disabled
    oneshot

service ifcfg_tiap /system/bin/ifconfig tiap0 192.168.43.1 netmask 
255.255.255.0 up
    disabled
    oneshot

Original comment by tekah...@gmail.com on 13 Oct 2011 at 1:50

Attachments:

• build.prop
• init.p925.rc

[GoogleCodeExporter]

Oh. Thanks tekah... for sharing this. Will add a new profile ... but this needs 
to be tested.

Original comment by harald....@gmail.com on 14 Oct 2011 at 6:06

[GoogleCodeExporter]

Cool...  Also, moto phones running OMAP4 should all have a similar 
softap/hostap setup.  cvpcs has repo for the bionic that demonstrates this.

# tiap_drv.ko location: /system/lib/modules/tiap_drv.ko

I'm not actually 1000% sure about this, but cvpcs's repo has it with all the 
other kernel modules in that directory.

# bionic init.rc
# 
https://github.com/cvpcs/android_device_motorola_targa/blob/gingerbread/root/ini
t.mapphone_cdma.rc

service ap_fmloader /system/bin/logwrapper /system/bin/tiap_loader \
        -f /system/etc/wifi/fw_wlan1281_AP.bin -i /system/etc/wifi/tiwlan_ap.ini \
        -e /pds/wifi/nvs_map.bin
    disabled
    oneshot

service ap_fmloader_rfmd /system/bin/logwrapper /system/bin/wlan_loader \
        -f /system/etc/wifi/fw_tiwlan_ap_rfmd.bin -i /system/etc/wifi/tiwlan_ap_rfmd.ini \
        -e /pds/wifi/nvs_map.bin
    disabled
    oneshot

service hostapd /system/bin/logwrapper /system/bin/Hostapd 
/data/misc/wifi/hostapd.conf
    socket hostapd_tiap0 dgram 660 wifi wifi
    disabled
    oneshot

# Now, we don't have an ifconfig entry in the bionic init, but i'm thinking 
OMAP4 will use tiap0 in general. 
https://github.com/cvpcs/android_device_motorola_targa/blob/gingerbread/system.p
rop

Sooo....  I also just stumbled upon this guide, which would have been awesome 
to have during the droid x-prience. LOL

http://www.omappedia.org/wiki/Porting_WLAN_SoftAP_to_Android

I'm thinking that there has to be a way of targeting omap more as a platform, 
rather than on a per device basis.  Even though profiles as is would seem work 
more on a per manufacturer, per SoC basis, and likely apply to more than one 
particular phone.  Thrill/DroidX/Bionic all work off the same basic sequence.  
Load AP kernel module>Load AP firmware>Bring up interface>Start hostapd.  In a 
unified profile, compensating for differences in file naming/placement would be 
the biggest issue.  Database or a search algorithm maybe?  I dunno...  I'm just 
throwin' out brain farts....  heh

BTW, just wanna say the latests 3.1 beta rocks with cm4dx-gb!  

Aloha!

Original comment by tekah...@gmail.com on 15 Oct 2011 at 12:35

[GoogleCodeExporter]

Hi tekah...
I've tried to do something useful with all your information. 
http://android-wifi-tether.googlecode.com/files/wifi_tether_v3_1-pre99.apk
Hope this works on the thriller or targa.

Original comment by harald....@gmail.com on 24 Oct 2011 at 9:54

[GoogleCodeExporter]

hostapd is failing to start...

Seems that hostapd.conf is being generated with "interface=tiwlan0" when it 
should be tiap0.

I've tested it using a quick workaround with a hostapd.conf set for tiap0 and 
redirecting the .edify script to use it instead.  With the fixed .conf the AP 
comes up properly.  This is on thrill, dunno if the same thing would be 
happening on targa.

Original comment by tekah...@gmail.com on 27 Oct 2011 at 9:55

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Ok. Hopefully fixed here:
http://android-wifi-tether.googlecode.com/files/wifi_tether_v3_1-pre100.apk

Original comment by harald....@gmail.com on 2 Nov 2011 at 8:55

[GoogleCodeExporter]

All green for me.  ;)

Imma get some other folks to cross verify this.

Original comment by tekah...@gmail.com on 3 Nov 2011 at 4:32

[GoogleCodeExporter]

Seems like everyone ditched their thrill for a samsung or an iphone...  LOL

There is however confirmation on the targa profile working.  CZ is good 
verification.
http://forum.xda-developers.com/showthread.php?t=1260968&page=4

Original comment by tekah...@gmail.com on 5 Nov 2011 at 3:40

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Hostapd is failing when no encryption is enabled.  It works with encryption 
enabled.

Here is a "./tether start" without encryption enabled.  Actually, it is just 
the part that failed...

And hostapd.conf as well.

Original comment by tekah...@gmail.com on 8 Nov 2011 at 9:22

Attachments:

• tether.log
• hostapd.conf

[GoogleCodeExporter]

Ok, now I see it...  Without encryption enabled, hostapd.conf is getting 
generated with tiwlan0...

Original comment by tekah...@gmail.com on 8 Nov 2011 at 9:25

[GoogleCodeExporter]

Damn. Ok, will check that tonight. Stay tuned

Original comment by harald....@gmail.com on 9 Nov 2011 at 12:18

[GoogleCodeExporter]

Here we go. Hopefully fixed.
http://android-wifi-tether.googlecode.com/files/wifi_tether_v3_1-pre101.apk

Original comment by harald....@gmail.com on 10 Nov 2011 at 8:39

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Ahm. I've just checked here if the interface set to tiap0 ... seems to be 
correct (with pre101).

Ah. razr? really?

Original comment by harald....@gmail.com on 13 Nov 2011 at 9:02

[GoogleCodeExporter]

Maybe it's just the razr failing now?

Works with encryption like pre100 on bionic...

Encryptionless failure logs..

Original comment by tekah...@gmail.com on 14 Nov 2011 at 9:16

Attachments:

• hostapd.conf
• tether_start.log
• tether.edify
• init.mapphone_cdma.rc
• build.prop

[GoogleCodeExporter]

Ahm. All the files you've uploaded are from the razr? Which device-profile was 
used? Thanks.

Original comment by harald....@gmail.com on 16 Nov 2011 at 8:49

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

yessir...  targa... all the stock tether files are the same... the hardware is 
nearly identical to targa a.k.a bionic...  which you should probably call the 
profile Bionic/RAZR instead.... and the thriller profile...  "LG Thrill/O3D"... 
 are you using build.prop entries for device detection? Imma try to find an O3D 
build.prop, or atleast the entry you need..

Original comment by tekah...@gmail.com on 16 Nov 2011 at 10:17

[GoogleCodeExporter]

Hi. Yes, "ro.product.device" (build.prop) is used for device detection.

I probably need to rewrite some parts of tether.edify. Anyway I think I need an 
overview what works on which device (with what device-profile) - I'm a bit lost 
right now.

Tekahuna, it would be great if you could help and if you like ... I share my 
code (which will be published when version 3 has made its way to market) with 
you.

Original comment by harald....@gmail.com on 17 Nov 2011 at 8:44

[GoogleCodeExporter]

I'm down to help out.  I'd like to see AP mode for all OMAP3 WiLink 
6.0(WL1271/WL1273) & OMAP4 WiLink 7.0(WL1281/WL1283) devices with 
SoftAP/hostapd support built-in.  *The original Motorola Droid being the only 
OMAP3/4 device I know of, NOT to have WiLink SoftAP drivers built into the 
factory firmware*

Being able to see the source would definitely help me to better see how to 
integrate my knowledge into your existing framework...  And I truely don't 
think it will be that difficult to hit all of these devices...

Biggest issue to seems to be how to decide whether to use tiwlan0 or tiap0... 
Well..

ro.board.platform=omap3, uses tiwlan0 & /system/bin/wlan_loader
ro.board.platform=omap4, uses tiap0 & /system/bin/tiap_loader

I'm too tired to elaborate very much right now, but I'll have some free time 
between tomorrow and this weekend, maybe we can get the ball rolling and knock 
this thing out.  Email me, and let me know if you have another way you'd like 
to communicate...  Meanwhile, I'll try to gather my thought into a more 
conveyable/coherent form.

Lets do this!

Original comment by tekah...@gmail.com on 18 Nov 2011 at 8:55

[GoogleCodeExporter]

Which device (manufacturer, type)?
LG Thrill
Which firmware is installed?
2.2.2
What version of wireless tether are you using?
3.1 beta 6
What steps will reproduce the problem?
1. Start tethering
2. usb Tethering
3. portable WIFI hotspot

What is the expected output? What do you see instead?
Wifi network doesn't show up. Probably not supported on this phone it's new. 
Just a heads up.
Please provide any additional information below.
"Authentication Unsuccessful" there is a temporary network problem that 
prevents the 
enablement of mobile hotspot. please retry later.

Original comment by emmanuel...@gmail.com on 21 Jul 2014 at 11:36