FORUMS

Enable Multi-Window Mode on M Developer Preview

What was not mentioned in yeterday’s keynote was Android M’s multi-window … more

I/O Summary: Google Cardboard Virtual Reality

One year ago, Google introduced cardboard. Amazingly enough, that was all it took to fire … more

Android M Preview Images – XDA TV

Android M preview images are available. That and much more news is covered by Jordan when he … more

I/O Summary: How Android M Handles Power And Charging

In the spirit of improving the core Android experience, Google is changing Android … more

[MOD][4.2.1/4.2][JOP40D/JOP40C] Tethering/Wifi Hotspot for the Nexus 7 3G

Thanks Meter: 93
 
By stridger, Senior Member on 16th November 2012, 11:27 AM
Post Reply Subscribe to Thread Email Thread
17th November 2012, 10:40 PM |#11  
phonic's Avatar
Senior Member
Flag Florida
Thanks Meter: 412
 
Donate to Me
More
Quote:
Originally Posted by NORCALkID

What do you mean by customized?... there's a difference between an odexed apk and deodexed apk and that will change the size of it.

Sent from my SPH-L710 using Tapatalk 2

What I mean is, when I decompile, modify and recompile the framework.apk file, making only a 1 character change effectively, the filesize of the apk goes from ~9MB to ~5MB.
 
 
18th November 2012, 09:47 AM |#12  
Member
Thanks Meter: 5
 
More
Smile
I receive text messages. I think it is possible to have voice calls enabled, it is Just a matter of time.
18th November 2012, 09:55 AM |#13  
phonic's Avatar
Senior Member
Flag Florida
Thanks Meter: 412
 
Donate to Me
More
Quote:
Originally Posted by heliumv2

I receive text messages. I think it is possible to have voice calls enabled, it is Just a matter of time.

The two things have absolutely nothing to do with each other.
18th November 2012, 07:20 PM |#14  
Retired Recognized Developer
Thanks Meter: 240
 
More
I highly doubt the actual hardware is any different, it would be more expensive to produce two different pieces of silicon. They may be "disabled" physically, however I doubt it, it is most likely the radio's firmware.
19th November 2012, 06:16 AM |#15  
OP Senior Member
Thanks Meter: 93
 
More
Quote:
Originally Posted by ben1066

I highly doubt the actual hardware is any different, it would be more expensive to produce two different pieces of silicon. They may be "disabled" physically, however I doubt it, it is most likely the radio's firmware.

I agree with that. It will be similar to the 3G Galaxy Tab, where you can enable the functionality through a custom radio:

http://forum.xda-developers.com/show....php?t=1875024

I don't know whether this was a leaked or a hacked radio, but I'm sure it must be possible in software, it just may be very hard.
19th November 2012, 08:29 PM |#16  
Senior Member
Flag Toronto
Thanks Meter: 508
 
More
We're off topic here but just to point out, if it's a radio hack then part of the challenge is finding radio firmware for a comparable device that does have phone functionality enabled. On the Samsung devices, many of th em have parts in common that made it easy to cross flash radios.

Asus has not released very many phones as they have concentrated on the tablet market. Neither of the Padfones uses a Tegra 3 so I wouldn't imagine the radios would be cross compatible.
19th November 2012, 09:04 PM |#17  
brainmaster's Avatar
Recognized Developer
Thanks Meter: 4,530
 
Donate to Me
More
Quote:
Originally Posted by phonic

What I mean is, when I decompile, modify and recompile the framework.apk file, making only a 1 character change effectively, the filesize of the apk goes from ~9MB to ~5MB.

Because its been compressed.
25th November 2012, 06:40 PM |#18  
Senior Member
Thanks Meter: 7
 
More
details
Thanks for this. Would you please give more detail about how you did it? Where can I found the fixed apktool (latest one from google code site is not working for framework-res)?

Also after unpacking, which setting did you change to enable tethering?

Quote:
Originally Posted by stridger

PLEASE USE WITH CAUTION AND ONLY IF YOU KNOW WHAT YOU ARE DOING. I WILL NOT BE RESPONSIBLE FOR BRICKED DEVICES.

You may have noticed that the Nexus 7 3G does not have the tethering options enabled by default.

I couldn't live with that (that was partially the point why I got the 3G version), so have patched the framework to enable those options. Partial credits go to PaulOBrien@MoDaCo who has fixed the apktool for Android 4.2 .

To get it to work just flash the ZIP below. It will only work on the newest JOP40C release, and obviously only if you have a 3G device. Please do not try it on the WiFi-only Nexus 7 .

Please note that it doesn't do a backup of the original framework-res.apk, so you can either make one yourself, or you can reflash the factory system image if you want to go back to stock later.

https://www.dropbox.com/s/f9c2jslwq6...abletether.zip

27th November 2012, 05:58 AM |#19  
Senior Member
Thanks Meter: 258
 
More
Quote:
Originally Posted by phonic

Yes and no. You can enable the FUNCTION of voice calling in the framework (it's in values/bools.xml). All this does is allow the dialer to come up. However, so far, no one has been able to actually get voice calls to work through it.

---------- Post added at 11:29 AM ---------- Previous post was at 11:16 AM ----------

Is there a reason why customized versions of framework.apk are half the size of the original?

people have suggested, a build.prop modification might work - however noone has tried it yet. Have you tried this before? might be worth a shot
28th November 2012, 05:56 PM |#20  
Member
Thanks Meter: 0
 
More
The tethering function work but I got a problem that I can't use check in in Facebook and cannot use GPS navigation in Google map at 4.21
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes