Hi,
I'm looking for a developer to implement features into a ROM. The features are as follows:
Note: An Ethernet adapter (with a charging functionality) will always be physically connected to the device.
Switch on the device once the power source has been switched on.
Enable Ethernet Tethering (ET) after boot-up and check its status frequently in the background e.g if it's off at some point, then enable ET
Implement an icon to show that Ethernet Tethering is enabled in the top bar.
Replace the stock boot-up animation with a custom animation/image.
Turn off the device after some minutes once the charging source has been switched off.
Unfortunately with Android 11+, Ethernet Tethering is a limited functionality relative to checking status, enabling on boot/charging.
I recently used a macro with Tasker/Automate but I'm not happy with the reliability of the result. I have tasks such as check/enable ET after boot, after AC charger input (because the Ethernet adapter has a charging port as well), and check/enable ET after unlock. This is all done via the UI and obviously has its bugs and limitations. So my only other option (that I know of) in terms of greater reliability would be to root the phone and implement the features, as mentioned, into the ROM.
In terms of the ROM and Android device, there is a probability that the device will change over a long period of time. After doing some research, I understand that a GSI ROM would therefore be more suitable. What do you think?
If you are interested, please PM me and we can discuss the financial side of this project.
Related
I was trying to be able to use USB/OTG while charging my gnex, but after looking an while the only solution I got is to modify the kernel.
As one post in rootzwiki sais:
"The Galaxy Nexus OTG kernel code does not evaluate a single resistor. So no Battery Charging Spec implemented here.
However, I was able to modify this kernel to make it accept a charge while in OTG host mode. A Y-cable is connecting my phone to a powered USB hub. The hub has a USB-to-Ethernet dongle, connected to a router. The hub is also powering the Gnex via the other end of the Y-cable. The phone can now, say, act as a WiFi access point (wired + 3G!) and it's battery level will never drop below 100% or 99%. One disadvantage: in a real on-the-go situation, this kernel will not anymore power slave devices. One could fix this by allowing the user to switch between OTG host mode charge-out (default) vs. OTG host mode charge-in. Should be possible with the N7 as well."
The guy posted the modifications, but I was hoping to get the selective mode like he said, and I think this is something that should be in the cm10 kernel, so everyone can do that without the work of updateing cm10, and then flashing a new kernel everytime.
Wrong forum dude. This brings in Q&A.
Sent from my Galaxy Nexus using xda premium
caioketo said:
I was trying to be able to use USB/OTG while charging my gnex, but after looking an while the only solution I got is to modify the kernel.
As one post in rootzwiki sais:
"The Galaxy Nexus OTG kernel code does not evaluate a single resistor. So no Battery Charging Spec implemented here.
However, I was able to modify this kernel to make it accept a charge while in OTG host mode. A Y-cable is connecting my phone to a powered USB hub. The hub has a USB-to-Ethernet dongle, connected to a router. The hub is also powering the Gnex via the other end of the Y-cable. The phone can now, say, act as a WiFi access point (wired + 3G!) and it's battery level will never drop below 100% or 99%. One disadvantage: in a real on-the-go situation, this kernel will not anymore power slave devices. One could fix this by allowing the user to switch between OTG host mode charge-out (default) vs. OTG host mode charge-in. Should be possible with the N7 as well."
The guy posted the modifications, but I was hoping to get the selective mode like he said, and I think this is something that should be in the cm10 kernel, so everyone can do that without the work of updateing cm10, and then flashing a new kernel everytime.
Click to expand...
Click to collapse
I would like to know as well, i know its possible but im still a noob at this sort of stuff.
I think there is high demand for charging while otg and it will probably be in CM10 or similar soon. But if i can get it working today i no longer need a laptop.
Could we be pointed in the right direction to making these modifications?
USE FORUM SEARCH, READ THE RULES BEFORE YOU POST
how to build tuna kernel
I am pitching an idea that I have no idea how to implement. I am NOT a developer nor would I be able to acquire the skills necessary quickly. the reason for this post is to ask the community if it would be possible to create a ROM for the Galaxy Nexus or some other old easily unlockable phone that would mimic the functionality of an Android wear watch for use as a head unit in a vehicle similar to Android auto. Of course the ROM would not be the only custom aspect of this project one would also need to create or modify the wear UI in order to facilitate the functions of Android auto. the reason I believe Android wear API would be a good starting place for this project is because internet connection is shared between client and server devices. this would facilitate sharing of information between the devices without needing an Internet connection on the vehicle side. this would also allow the phone to automatically connect wirelessly to the head unit. the current Android auto hacks all require USB OTG. let me know your thoughts and try not to flame me too badly.
Which "Android auto hacks" ?
You mean my Headunit app ?
Android Auto has code to do AA over WiFi direct.
I will try to find a way to enable it, and make it work with my app.
USB is a PITA for anything besides charging.
WiFi Direct P2P will have it's own problems of course, but I'm really getting a hate-on for USB and the Host mode issues.
Android Auto has code to do AA over WiFi direct.
Click to expand...
Click to collapse
Is AA here short for Android Auto?
Will WiFi direct allow for automatic connections without removing device from holster/ pocket?
The other issue with using a real Android Auto app is the lollipop requirement. My Daily driver is a droid turbo and there's no telling when my phone will get its update. ( and the bootloader has a damn chastity strap)
I have a Pumpkin model KD-C0109-US-A single DIN RK3188 800x600. I would like to use my cell phone to provide a network connection to my HU through USB reverse tethering. The cell phone connects and shows itself as tethered but the HU does not show any network connection. Pumpkin customer service says that reverse tethering is not supported. They suggest using wi-fi hotspot from the cell. I would prefer hard wire through USB so that the phone would be powered while using it as an internet source. The reverse tethering apps have not worked. Is there a firmware upgrade or other work around that will un-cripple the HU and make reverse tethering possbile? Has anyone had success with this? I would also be interested in learning about tried-but-failed approaches to avoid repeating mistakes.
I am really perplexed. The following is the "explanation" I received from the reseller of my unit:
"Thank you for your message/email!
Sorry for replying you late due to different timezone and working time!
Actually as you can see, this is the car radio player, not cellphone, so the Android system was deep modified by the factory, which is already do not have the USB tethering function, cause the USB on the radio is only for USB reading and 3G USB dongle to plug. It is not support that any more. I hope you can understand. If you need to charge your phone, could you mind use your original car USB port to charge it?
Best Regards!"
Does this make sense? Reverse tethering seems to be a common thing in android as in
http://forum.xda-developers.com/showthread.php?t=2287494
Help!!
Good luck with this..
Not as easy as you may think, and as that thread points out, there are many that can't get it going on multiple units..
I think you are up against an Android coding layering problem in general.. As I have used reverse tethering alot on windows based machines, as in laptops to throw internet out to rooms that have been to far out of range of signal.. And or hotel rooms so I can use a tablet.. But those setups are using dedicated software that is adding another set of drivers into the windows operation system and setting up a new communication set..
So as been pointed out by your supplier..they don't have the necessary "modules" loaded into thier Android base to service this want..
Not saying that it wouldn't be impossible to implement via scripts.... But there will be a bit of work that needs to be done..
i wouldn't mind do this aswell i have the same headunit (well mine is eonon but yeah)
I have a 1st generation XBox that only has an Ethernet port. Is there a way to connect it to the Fire TV to get it access to my network through WiFi?
When Ethernet port is plugged in it disables wifi connectivity. after that a bunch more work making wifi the default gateway with routing... if it is possible. . prolly worth your time to just spend the $30 on an adapter for it or install dd-wrt on an old router you have laying around. . I had a similar request where I wanted to know if my firetv can double as a coffee maker but no-one has solved where to put the k-cup.
Its not so much the device in this case that is unfit for the purpose (well - unless it is, as described above.. ) - it is, that the minds that are interested in and forming around solving those problems are working on much better (reputation) and wider known projects - AND the devices they support cost anywhere from 10-30 bucks used already. So dont tell them why you bought a Fire TV instead.
I know that current "technophiles" see the world as app based solutions that will come to them if they ask around often enough - but really, we already are at the minimal knowledge and minimal cost stage - and they are in essence complaining about convenience.
I have a problem - and see the solution in this one ethernet port another device I bought already has. Let the internet work out the rest, I am waiting for my app - its already rooted, how hard could it be.
And thats not how this works.
First of - why should they be working on an app based solution? A functionality layer if you will - if they dont have control over the entire ecosystem and networking, I heard has something to do with security. Sometimes. And with devices that have to work longterm - quite unlike the little plastic box that currently sits under your TV. And that today is rooted but tomorrow might not be - because, well its not yours to decide. Entirely.
dd-wrt and openwrt are what you are looking for - but that was already mentioned by the person posting before me.
I'm just here to explain why the "asking for a service" mindset ultimately breaks, when it comes to open source movements. Especially when your demands get more and more specific. ("I have bought a...")
I can say all this, because I currently use ddwrt to service some of my needs and it works perfectly well, creating all kinds of synergies I actually actively use - many of which actually are real enablers for owners of Android based Kodi boxes.
Well - then again, it might actually work already... (Turn off WLAN in the gui, then enable it via the shell (maybe that way both can be set active at the same time) and start configuring iptables).
http://forum.xda-developers.com/showthread.php?t=444004
But understand that this would be very much a hack. So usability, interfaces, security concerns are not on the forefront of peoples minds. Also - have fun configuring ports that way (ftp mostly I suppose.. ) - if you dont want everything to be open.
Google and 2 minutes - btw.
When you read through the thread you start to recognize - that what you are actually looking for is implementation and support (Hence dd-wrt or openwrt). Also - it becomes very clear why this probably never will become an app (needs root, needs to install a new library (think of stuff only busybox does as a core function on android - this has to be vetted not to cause unexpected problems), still only circumvents Androids core functions (either ethernet OR wlan), isnt fully featured, and most of all - most technically inclined people who actually need the functionality simply buy into the dd-wrt or openwrt ecosystem and its all there already).
So to break it down to a few sentences - if you get a person willing to establish a very specific function for his/her own purpose against prior design on an open source OS, you are golden. But, you wont get them by randomly asking around for help on an internet forum. And dont expect to get entire featuresets or usability options alongside it. If you want those - and you do - go with the communities that are known for solving those problems and buy into the devices/ecosystems they use. 10-30 USD should be well worth it.
But if you are in a hacking state of mind - go for it and make those devices work like you want them to.
First off, I have a rooted Pendant and we now have recovery, so working with system files
should not be a problem.
I know that this feature is present on the Cube, but not on the Pendant. But they share almost
identical hardware and sometimes the same software. So what makes this work on one device and
not the other?
It is my understanding that this is done by software, so I am assuming that certain apps are
loaded or features enabled based upon the hardware id.
Can someone give me an idea of what to look for, so that I can try and enable this feature?