do any of the custom kernels currently developed for the Thunderbolt, support wireless "N"? Thanks in advance.
The phone supports the wireless n protocol by default out of the box. If it's not working, it's you, not the phone.
Kenerls help support the wifi. If the kernel does support "N", the the phone will not. Thanks for ur support tough guy.
Sent from my ADR6400L using XDA App
I wasn't being a jerk, you're just overreacting and assume my short answer was being rude and some sort of attack on your intelligence. I didn't see a point of giving a tl;dr answer you probably aren't interested in.
But here's the tl;dr version:
Instead of jumping on me, you could look up how drivers work. Your phone supports wireless n because the kernel in the phone has the proper wireless driver for it compiled in. On linux, there aren't a lot of choices for wireless drivers and since there's most likely only one choice for the wireless driver with this hardware and revision type (and it comes linked and ready to compile with the kernel source given from HTC that all the kernels listed in the developer forum are using). The phone's hardware supports wireless n and any drivers made for it by default will have it as well. So by that, if wifi works at all on your phone, so will wireless n--unless someone was specifically screwing with you and ripped out the wireless n protocol support in the driver source code, but happened to leave g and b, which most likely be a pain and be hard to do without breaking the entire driver itself.
If you want to be technical, all the kernels are based off the one that came with your phone in some way and have the same drivers compiled in; hence, they support the wireless n protocol. No developer is going to remove the wifi drivers to a kernel on purpose and if it were missing, someone would quickly notice. With that in mind, if the phone doesn't seem to pick up a wireless n signal, it's not the phone, it's you (or indirectly your router/hotspot location).
Honestly though, if a short answer doesn't work for you and assuming you are going to take a long answer at face value because it has some big technical words thrown into it that make it look credible and don't want to dig up an answer by googling or flashing one of the kernels to see for yourself, what is the point of writing it all out?
If that was all too tl;dr, the short answer is once again, yes, they all have "Wifi N kernel support."
Also, my answer is free, no need to donate to me
Not all customs kernels support wifi N. Ask a couple devs.
Sent from my ADR6400L using XDA App
Related
Hi,
Would like to know if there is plans on PS Groove development for Xperia x10. I think many people would appreciate this.
Thanks and good work btw on the bootloader so far.
Hey have a look at this link ;-)
PSGroove being ported to Android Devices!
Sony will have it patched before it gets done, so it's going to be quickly irrelevant anyways.
Do you know that for a fact or is it just one of your many assumptions...
Cuz last i heard from the "hacker" team that made the psjailbreak code that not even them are too sure on any of the sides, nobody actually knows.
And cuz the ps3 is open to homebrew, whats the difficulty of patching the update string? I mean they already have made "stalth gaming" possible by editing sertain files...
And the ps3 has a HUGE game library that personally for me just thats enough cuz i almost never play online on it.
I bought a AVR chip with PSGroove support so to speak. I will have it on Monday, but if i knew it would be developed for Android i wouldnt have bought it.
So belive me, not too many ppl care "if" Sony patches it... And even if they do, the exploit cannot be patched, its a lot like the iPhone Jailbreak.
Let the Cat&Mouse game begin...
This project tickles the very core of my geekdom. Not so much because it opens up the PS3 for piracy but but because it's a completely insane yet feasible and even kinda logical concept.
Emulating an 8mhz Atmel on the Snapdragon? Very doable.
Proper hardware access to the USB port? With rooted phone, you have it.
So theoretically it's possible and if it comes to fruition we'll be able to "root" the PS3 by hooking up our cellphones to it and running some software. I don't know about you guys but for me that would be a serious contender for the "Epic hack of the year" award.
ddewbofh said:
"Epic hack of the year" award.
Click to expand...
Click to collapse
Of the century i would say great moment in hacking history.
http://netzke.blogspot.com/
This guy is the closest to actually having something... Hope it works, so i can feel stupid for buying a USB Dev Kit ;-)
PSFreedom was release for N900 :
http://kakaroto.homelinux.net/2010/...k-ps3-with-n900-worked-finished-and-released/
KaKaRoTo said that the driver can be adapted to the others devices :
KaKaRoTo said:
By writing this exploit as a standard linux driver, this means that my module can be used on any other linux-enabled devices.. this means not only the N900, but also the 770, N800, N810, Android phones and future Meego devices. It might need a little porting for some devices though, but it should still work…
Click to expand...
Click to collapse
If someone can work on the X10's port
any devs willing to give it a shot?
Sent from my X10i using XDA App
brat81 said:
any devs willing to give it a shot?
Sent from my X10i using XDA App
Click to expand...
Click to collapse
I'm looking at what parts need to be modified and if porting it is even possible to begin with. Both Maemo and Android run Linux kernels but that's about it as far as similarities go. Even though it's a separate kernel module it needs to have certain options built into the kernel. If those bits aren't there we're SOL.
Update: The configuration file for the stock kernel indicates that the USB chipset supports HCD (Host Controller Driver) mode at least.
ddewbofh said:
I'm looking at what parts need to be modified and if porting it is even possible to begin with. Both Maemo and Android run Linux kernels but that's about it as far as similarities go. Even though it's a separate kernel module it needs to have certain options built into the kernel. If those bits aren't there we're SOL.
Update: The configuration file for the stock kernel indicates that the USB chipset supports HCD (Host Controller Driver) mode at least.
Click to expand...
Click to collapse
if you can figure this out, i would donate or send a reward. I might pay up 25$ for this.. the convenience of just using my phone when i go somewhere to hack a buddy's PS3 would be awesome.
JQE said:
if you can figure this out, i would donate or send a reward. I might pay up 25$ for this.. the convenience of just using my phone when i go somewhere to hack a buddy's PS3 would be awesome.
Click to expand...
Click to collapse
*meh* Screw donations, the hacking itself is reward enough.
Source code is @ http://github.com/kakaroto/PSFreedom
also taken form the blog
Q: What do I need to use PSFreedom on my N900 ?
A: First, you need a N900 (duh) and a PS3 (duh) with firmware 3.41. The N900 should be running the stock kernel (-omap1) not a modified kernel. Then you just need to scp the files to the N900 and run the -enable script.
Q: How much of the source is Nokia N900 specific? Are you using the Linux USB Gadgets library?
A: Very little is N900 specific, I’m using the include/linux/gadget.h if that’s what you mean. See next Q/A for more info.
Q: How hard is it to port it to a new device ?
A: Well, I’ve just separated my code from the N900 specific stuff, so it’s quite easy, there are mainly two functions to write, one to get and one to set the USB address.. two other functions that only return some static result depending on the configuration of the controller (the name of the endpoints, and whether the controller supports high speed or full speed mode).
Read the README file provided with PSFreedom, and check the psfreedom_machine.c file for specifics on what to implement.
Q: How can I port it to a new device.
A: Well, first, you need to figure out what controller your device uses, in the case of the N900, it’s ‘musb’..
Then go to the driver code for that controller (probably in drivers/usb/gadget) and look for ‘SET_ADDRESS’. In the case of musb, it was in drivers/usb/musb/musb_gadget_ep0.c. In there it was setting the address to the USB device, so just copy that code into the psfreedom_machine.c to allow setting the address, and add a similar function to be able to retreive the address.
Then add a function to return 0 or 1 depending on whether the controller supports HIGH, FULL or LOW speed mode (go to usb_gadget_register_driver for your controller, and in the first lines, it should validate the speed argument, it will tell you which ones are acceptable), set LOW speed mode to return TRUE only if FULL speed isn’t available .
Finally, add a function to return the endpoint names.. it will usually be something like ‘epXin’ and ‘epXout’ (where X is the endpoint number), or “epXin-bulk”, etc.. look at how the driver initializes its endpoints or grep for “->name” in the file to find where it sets it…
That should be enough!
Ok this is it for now with the FAQ. Next time, I’ll tell you all about my experience, what problems I encountered and how I fixed them, maybe it will help others!
Enjoy it!
KaKaRoTo
Click to expand...
Click to collapse
hope it helps
mean while over @ http://netzke.blogspot.com/
There's doesn't seem to much in development happening I've put my name down for beta testing but who knows if i get in.
Maybe if there's someone working on the netzke team build they could let us know some info.
Time for a quick update on my research.
From what I can find out about the X10 through config-files and /proc it looks like it uses the msm72k driver. By comparing that with the musb driver and looking at how PSFreedom uses musb it doesn't look impossible to get it running with the msm72k driver.
Right now I'm looking at how to get/set the device address and endpoint. Getting the endpoint name is pretty straight-forward but getting the physical address needed is slightly trickier. But I'll keep hammering away on it.
Warning: My attention-span is really short so odds are I'll keep working on this in bursts. So while there's a big chance I'll get it working soonish you shouldn't hold your breath.
Cool hope to see a update when i wake up thanks very much for your time.
I have a confirmed spot in the beta testing for the android port by netzke. I can let everyone know what it's like when it is released to beta testers.
Sent from my X10i using XDA App
Findee said:
I have a confirmed spot in the beta testing for the android port by netzke. I can let everyone know what it's like when it is released to beta testers.
Sent from my X10i using XDA App
Click to expand...
Click to collapse
Don't get your hopes up, the project is a textbook example of a scam.
It bugs me that he's raking in cash with nothing to show for it while others (like myself) are doing 12+ hour hackruns. :/
Well I haven't spent 12 hours coding, most of the time has been spent working on circumventing the limitations of the stock kernel and figuring out the hardware.
ddewbofh said:
Don't get your hopes up, the project is a textbook example of a scam.
It bugs me that he's raking in cash with nothing to show for it while others (like myself) are doing 12+ hour hackruns. :/
Well I haven't spent 12 hours coding, most of the time has been spent working on circumventing the limitations of the stock kernel and figuring out the hardware.
Click to expand...
Click to collapse
if there is anything i can do to help let me know. I have a bit of experience with stuff, but not much with android.
ddewbofh said:
Don't get your hopes up, the project is a textbook example of a scam.
It bugs me that he's raking in cash with nothing to show for it while others (like myself) are doing 12+ hour hackruns. :/
Well I haven't spent 12 hours coding, most of the time has been spent working on circumventing the limitations of the stock kernel and figuring out the hardware.
Click to expand...
Click to collapse
it does get that kinda vibe but i guess i always give people the benifet of a doubt i haven't sent over any cash to him. I feel he has got enough $15 to get in the beta is quite a sting and with 100 odd people signed up he sure has enough cash
Sent from my X10i using XDA App
http://forum.xda-developers.com/showpost.php?p=8006931&postcount=142
One thing that bothers me about my Android phone is the opaque, closed-source baseband firmware ("radio" as it's often called here). Since the baseband is interposed between the OS and most hardware functions, its firmware presents a major unknown in the total security of the device.
It's unlikely that the source code for any of this baseband firmware is going to be released, and the open source OsmocomBB baseband is a long way off from supporting Android or the dominant Qualcomm chips. But I would settle for decompiling an existing baseband firmware image, so that I can start to understand some things about it's behavior, and perhaps compile modified versions.
Does anyone know where to begin with this? Many thanks.
I wish somebody participated in this with you. I need it also /
funkydaemon said:
One thing that bothers me about my Android phone is the opaque, closed-source baseband firmware ("radio" as it's often called here). Since the baseband is interposed between the OS and most hardware functions, its firmware presents a major unknown in the total security of the device.
It's unlikely that the source code for any of this baseband firmware is going to be released, and the open source OsmocomBB baseband is a long way off from supporting Android or the dominant Qualcomm chips. But I would settle for decompiling an existing baseband firmware image, so that I can start to understand some things about it's behavior, and perhaps compile modified versions.
Does anyone know where to begin with this? Many thanks.
Click to expand...
Click to collapse
Good idea. Although most probably it'll all be native C code compiled into binary form, not amenable to decompiling.
So you'd probably need a very good debugger and a system call tracing facility in strace.
I guess hell might also break loose because SIM encryption(?), voice encoders(?), network locking(?) and god knows how many of those proprietary tidbits may be sitting in there.
SIM encryption broken leading to duplication of SIMs and leading to smartcard encryption and open source tools to reprogram your credit cards with more money.
That's not hell. That's hell in a hand basket with us enjoying the ride
Keep us posted. It's guys like you who think outside the radio that gave us the TV
For Qualcomm based devices you need to decompile Hexagon code.
For other Intel XMM6260 etc based devices suffice IDA (ARM).
In both cases the raw binary blobs may be encrypted, but extractable from running machine.
I'm working on it, in a fashion, and am writing up a document compiling everything that has been done on cellphone radio hacking. I've not found much on baseband firmware; there's a lot of info out there but it's been tough to find amongst all the other hacking that has similar keywords. Currently most quality info around this subject involve an extra (and depending on desired features; expensive) bit of hardware and two open source software packages with their decencies. As the hardware is currently outside my budget ($300 for the best bang for buck) I'll be working on getting the software to recognize the hardware built in my Android devices. Provided that all goes well I should be able to read and write on the frequencies that the in-built hardware supports and hopefully, as I always get an identical device when getting one, read and write with my backup android device. Be warned if you decide to follow me down this path; there are laws restricting what non-licensed persons/companys can do on certain RF frequencies and this depends on where you live, I'm no expert only a person capable of reading lots of dry informative documents, provided I do achieve direct contact between devices this hack could (and likely will) fry one of my antennas so be warned you'll likely do the same :banghead: so do this on an old device that you don't care about before ever trying on something you use daily. With the warning out of the way lets get down to the quick version.
~~~~~~~~~~~~
Currently all the developing I've found educational has involved the before mentioned "expensive hardware" known as software defined radio, shortened to SDR, go a head and pop open a new tab and Google search either. You'll eventually find that cellphone manufacturers have likely already put these into many devices. You'll also hopefully find the two kickstarters, HackRF ~$300 and bladeRF ~$400, these are likely what I'll be saving up for; HackRF for sure as the next release will likely be able to send and receive at the same time instead of switching quickly between modes. If you dig deep enough you'll find a blog post from a hacker that plugged an Android into a much more expensive SDR and was able to place calls and send/receive text; the blog poster stated something to the effect that this was not a useful hack but I believe that it's a great proof of concept and totally worth another look. However, this hacker has also almost been sewed for some of the demonstrations with this kind of technology involving the capture and description of calls and texts so tread carefully.
The software I mentioned before boil down to GNU Radio and Open BTS; there's dependencies for each but all seem to be installable on Linux running on top of Android. Furthermore I see that someone (I'll edit your name in in a sec Edit: idcrisis ) previous mentioned wanting c or c++ support, GNU Radio uses these languages perhaps I can ask for some help when I get a little further in porting this to run without Linux in the middle so much? I think if we use the GPS to set the time then the signal shouldn't drift to much.
I'm using an app called Debian Kit to give me a flavor of Linux called Squeeze for testing the software. If you choose to try what I'm doing then make use of the readme that the developer wrote or the guide I wrote for general Linux on Android installation and interaction fund in my sig to get started. If you want access to the document I'm compiling then you'll want to PM me at this moment as the chances of hardware frying is high and I'll share a link to Google docs; I'll be releasing a full guide when I've figured out how to avoid damage.
Eventually I hope to port many of the functions in GNU Radio into an app that makes use of internal hardware. Currently I've found a few that make use of hardware plugged into Android through USB "on the go" or "host mode" just search "RTL SDR" in the app store and you'll see'em, but, currently nothing making use of internal hardware. If any are interested in joining forces and helping figure out how to do all this I'd be glad to offer any support I can.
Other things related to cellular antenna hacking other than the above mentioned software and hardware that I'm compiling into the same document. Well this is where we get into the parts I'm hitting the wall on. It looks like I'll have to get into Kernel modification as this is one of the things used to communicate between software and hardware. There's also the flashable files known as radios and I'll be digging further in how these files are modified.
Basically this is a very tough question to answer and has taken many months of reading, searching, and more reading to get this close bit if we all work together I know that we'll be able to modify how the antennas in our devices work.
Edit 01142014- Found a guide on reverse engineering embedded device firmware, the guide is on a router but as the chips in our phones are embedded perhaps the steps are similar
http://www.devttys0.com/2011/05/reverse-engineering-firmware-linksys-wag120n/
Sent from either my SPH-D700 or myTouch3gs or M470BSA
Guide for running Linux on Android that I'm writing:
http://forum.xda-developers.com/showthread.php?t=2240397
^^ NO! The embedded chips in the Linksys routers are MIPS based and not ARM like all our Androids. Very different, although technique is the same.
But thanks, for taking time to check up on all this.
Any updates ?
Hey Guys,
I'm looking into this, I've successfully extracted files from the OnePlus One's baseband, its running RtOS called REX, QC calls it AMSS.
Have a look at the thread here: http://forum.xda-developers.com/oneplus-one/general/discussion-hlos-reverse-engineering-t3292829
Waiting for the OsmocomBB update it projects
QCOM modem leaked sources.
Type in google/bing: "AU_LINUX_ANDROID_JB_MR1_RB1.04.02.02.050.116_msm8974_JB_MR1_RB1_CL3904528_release_AU"
There are many explanations that people will tell you to the answer to the "what is a kernel?" Like this great one from Omnicide
Spoiler
Omnicide said:
The best way i seen it put was, think of the kernel as the engine and the rom as the body of the car. The body of the car (rom) just makes the car look nice and user friendly. Now when we talk about the engine (kernel) simply put red lining the engine will get you to go fast but burn gas. Keeping the rev down low will make you run slower but saving lots of gas. Thats just one way to look at it, rpms being the cpu.
Click to expand...
Click to collapse
or this great one from androidcentral.com
Spoiler
What is a kernel? If you spend any time reading Android forums, blogs, how-to posts or online discussion you'll soon hear people talking about the kernel. A kernel isn't something unique to Android -- iOS and MacOS have one, Windows has one, BlackBerry's QNX has one, in fact all high level operating systems have one. The one we're interested in is Linux, as it's the one Android uses. Let's try to break down what it is and what it does.
Android devices use the Linux kernel, but it's not the exact same kernel other Linux-based operating systems use. There's a lot of Android specific code built in, and Google's Android kernel maintainers have their work cut out for them. OEMs have to contribute as well, because they need to develop hardware drivers for the parts they're using for the kernel version they're using. This is why it takes a while for independent Android developers and hackers to port new versions to older devices and get everything working. Drivers written to work with the Gingerbread kernel on a phone won't necessarily work with the Ice Cream Sandwich kernel. And that's important, because one of the kernel's main functions is to control the hardware. It's a whole lot of source code, with more options while building it than you can imagine, but in the end it's just the intermediary between the hardware and the software.
When software needs the hardware to do anything, it sends a request to the kernel. And when we say anything, we mean anything. From the brightness of the screen, to the volume level, to initiating a call through the radio, even what's drawn on the display is ultimately controlled by the kernel. For example --when you tap the search button on your phone, you tell the software to open the search application. What happens is that you touched a certain point on the digitizer, which tells the software that you've touched the screen at those coordinates. The software knows that when that particular spot is touched, the search dialog is supposed to open. The kernel is what tells the digitizer to look (or listen, events are "listened" for) for touches, helps figure out where you touched, and tells the system you touched it. In turn, when the system receives a touch event at a specific point from the kernel (through the driver) it knows what to draw on your screen. Both the hardware and the software communicate both ways with the kernel, and that's how your phone knows when to do something. Input from one side is sent as output to the other, whether it's you playing Angry Birds, or connecting to your car's Bluetooth.
It sounds complicated, and it is. But it's also pretty standard computer logic -- there's an action of some sort generated for every event. Without the kernel to accept and send information, developers would have to write code for every single event for every single piece of hardware in your device. With the kernel, all they have to do is communicate with it through the Android system API's, and hardware developers only have to make the device hardware communicate with the kernel. The good thing is that you don't need to know exactly how or why the kernel does what it does, just understanding that it's the go-between from software to hardware gives you a pretty good grasp of what's happening under the glass. Sort of gives a whole new outlook towards those fellows who stay up all night to work on kernels for your phone, doesn't it?
. You probably didn't get it at all, so let me tell you what a kernel is in about 15 words. A kernel is "what makes the phone work, and with out it the phone will not function."
I don't want to be thanked for this, thank omnicide, and androidcentral.com for the great explanations.
~~~~~~~~~~~~~~~~~~~~~
Samsung galaxy s2
Rom: Jedi knight 6
kernel: Jedi kernel 2
~~~~~~~~~~~~~~~~~~~~~
And you thought celebrities weren't smart! =P
A kernel is a ring master who commands hardware and software.. Like it takes input from hardware and feeds to software and vice versa..
sent from cyanmobile powered Beni
Hi,
I'm interested in purchasing a Nexus 4 I have no cellphone plan, nor do I want one; instead I intend to use the phone as a tablet or PDA.
I would like to hear some feedback on how feasible it is to low-level remove the cell and gps antennas' capabilities. Is there a driver or kernel module of some sort that could be removed to 'neuter' the phone? Can the hardware run the antennas without the ROM or kernel's consent?
I've already read about the code to reach a developer menu and 'disable radio' as well as 'airplane mode'. Neither of these fit the bill, I want the phone to be incapable of transmitting cell/gps information.
I would love to join the android community, but I will not feel comfortable until I know that the device isn't going to hand over my location to anyone with a crafty enough story at the police department, which I believe makes this question one of security rather than battery life or functionality.
My apologies if this is posted in the wrong section, I decided that the android forum would be most appropriate because I'm curious about how android manages the cellular antenna rather than something specific to the Nexus.
Thanks!,
BigBubbaX said:
Hi,
I'm interested in purchasing a Nexus 4 I have no cellphone plan, nor do I want one; instead I intend to use the phone as a tablet or PDA.
I would like to hear some feedback on how feasible it is to low-level remove the cell and gps antennas' capabilities. Is there a driver or kernel module of some sort that could be removed to 'neuter' the phone? Can the hardware run the antennas without the ROM or kernel's consent?
I've already read about the code to reach a developer menu and 'disable radio' as well as 'airplane mode'. Neither of these fit the bill, I want the phone to be incapable of transmitting cell/gps information.
I would love to join the android community, but I will not feel comfortable until I know that the device isn't going to hand over my location to anyone with a crafty enough story at the police department, which I believe makes this question one of security rather than battery life or functionality.
My apologies if this is posted in the wrong section, I decided that the android forum would be most appropriate because I'm curious about how android manages the cellular antenna rather than something specific to the Nexus.
Thanks!,
Click to expand...
Click to collapse
I am also interested in this...
I bet if one can compile a kernel for his own device, it is possible to disable the GPS and related drives in the module/kernel config.
and this would completely kill the feature... so no risk of any spyware app triggering it etc...
however it may not make sense to use maps on the device... unless you want to bluetooth pair it to another GPS device.
Nexus is great... but I want to be able to do this for a different phone which may not be as popular on here.. than what ?
G
ghatothkach said:
I am also interested in this...
I bet if one can compile a kernel for his own device, it is possible to disable the GPS and related drives in the module/kernel config.
and this would completely kill the feature... so no risk of any spyware app triggering it etc...
however it may not make sense to use maps on the device... unless you want to bluetooth pair it to another GPS device.
Nexus is great... but I want to be able to do this for a different phone which may not be as popular on here.. than what ?
G
Click to expand...
Click to collapse
Hi ghatothkach,
I'm still working on this. First I need to assemble a x64 computer capable of compiling a ROM from source, then I'll see if I can find a way to nullify the radio drivers. If it's possible for the Nexus, I'm pretty sure a similar workflow will be available for your phone.
There are also some other aspects of Android that I'd like to look at for security concerns, such as the way that the phone currently broadcasts a list of wireless networks which it is associated with.
I apologize for digging up an old thread, but has there been any development on this subject? Or physically removing or disabling the GPS receiver on a phone?
6 years later..
Question remains.
Is that possible to root the device and delete the gps driver/kernel completely?
If yes which of the file as to be removed
0
Hi,
I'm working on a small project and am currently looking for a Tablet that I can use. As far as I understood, the "Sony Xperia Tablet Z2" (SGP 521) could be a good candidate for my project. I am asking this forum to potentially assist me with your knowledge and experience if the following is possible with the device:
(Some questions or comments seem to be obvious but I still write them down so that I can be sure we are talking on the same level. Please do not simply refer me to the search functionality of the forum, I did my homework and searched each of the topics before -- I just need a first-person-confirmation of someone if the below is really working.)
- I need to modify and compile the Linux (Android) Kernel of the device. Thus, the Source-Code of the Kernel for this device needs to freely available.
- The modified Kernel needs to be able to be uploaded and booting from the device, thus the Bootloader needs to be unlocked.
- The device needs to have running NFC and LTE communication, plus touch and usual tablet capabilities. For this, the necessary binary-drivers need to be able to be integrated to the custom kernel. I expect the drivers are not common (GPL-like) drivers but proprietary and at maximum available as binary-package to be integrated afterwards.
Is this all possible or can I expect major problems somewhere? The used LTE network most likely will be some LTE network in Germany. To my best knowledge, it is possible to unlook the bootloader and compile a custom kernel. Critical point is: Is NFC+LTE working and available as binary package to be integrated in the custom-kernel?
Thank you in advance for your time!
Best regards
Dennis
Perhaps you could first tell us (approximately) what you plan to do on the tablet.
That could probably save you quite an amount of superfluous time and work if your plan doesn't make any sense.
hasenbein1966 said:
Perhaps you could first tell us (approximately) what you plan to do on the tablet.
That could probably save you quite an amount of superfluous time and work if your plan doesn't make any sense.
Click to expand...
Click to collapse
Sure. Since I did not write much about my past experience, you simply can be sure that similar projects finished successful already. I've done similar things with Nexus and previous Google/Android developer devices, without much problems.
Back to your question:
The idea is to develop an application to be put on a nfc-capable external device to provide some external computed value. Afterwards, the tablet needs to communicate to the application on the external device, using a protocol I design that in the end uses common NFC communication and protocols. Finally, the Tablet sends results of the external-nfc-cabable device through LTE to the Internet, thus the LTE interface is only used to provide Internet functionality.
Does this answer cover your question properly?
Best Regards
Dennis
Really nobody uses a Sony Xperia Tablet Z2?
/push
I am really wondering nobody is using the Sony Xperia Tablet Z2 (SGP521) with LTE and once installed a custom Kernel (maybe Cyanogen Mod?) and afterwards used anything with NFC + Internet. Simply can't believe that.
If there is anyone, please confirm that NFC + Internet (using LTE) is working with a custom compiled kernel.
Best regards
Dennis