Log in

View Full Version : LG U81xx settings for easyMobile



Hands0n
20th August 2006, 08:58 PM
This article sets out how to configure GPRS and MMS for the LG U81xx series for the bargain-priced easyMobile (http://www.easymobile.com) network, which is an MVNO of T-Mobile. At the time of writing, MMS is priced at 20p a pop which must be the cheapest PAYG MMS on the go (unless someone says otherwise).

These days one can pick up an LG U81xx as cheap as chips - particularly when getting down to the U8110, U8120 and other early models. While these had their troubles with 3 when they launched the handset itself is a very functional piece of kit and well suited to being redeployed elsewhere. Essential is that the handset is flashed with the last/latest version of the firmware to ensure stability as the early LG firmwares are reknowned to be very buggy indeed.

Anyway, to business..... All the key items are in bold below. These are all that is needed to get the GPRS and MMS working - and can be readily adapted to other handsets. These are tested, working, on an LG U8120 and U8110.

Step 1 - Reconfigure the 3 APN
MENU - 9 - 5 - Edit (3)
Bearer = GPRS
APN = data.uk

Step 2 - Create the MMS GPRS APN
MENU - 9 - 5 - Options - Add new
Connection title = mmsGPRS
Bearer = GPRS
Username = user
Password = one2one
APN = general.t-mobile.uk

Step 3 - Reconfigure the 3 MMS
MENU - 1 - 8 - 2 - 6
MMSC URL = http://mmsc.t-mobile.co.uk:8002
MMS Proxy = 149.254.201.135:8080
Connection mode = TCP
Access Point = mmsGPRS

Step 4 - Reconfigure the Browser
MENU - 6 - 6 - 1 - Edit (3 Services)
Homepage = http://wap.easyMobile.com
Connection mode = TCP without Proxy
Security = NonSecure
Timeout = 300
Access point = 3


Edit: Occasionaly I am getting an "Unexpected Error" after 99% of sending an MMS and the message is saved to Drafts. However, the MMS does get delivered to the intended recipient without any loss! I suspect this is due to some kind of network timeout - but there is nothing configurable in the MMS or its specific APN settings. I'll update on here if there is a fix.