Hello everybody,
I'm quite new to Android, but I have some good skill in programming. I saw that Android have some limitation on bluetooth applications.
For example it have a discovery timeout of about 120 seconds(300 seconds max) and after that the application need the user help to extend the discovery time.
Another limitation is that there isn't the possibility to create bluetooth connection between two unpaired device, this limit force users to know each other and limit the possibility to build great proximity application.
So I looked into the Android source code and I found some good point to change to bypass and change these limitation.
Now I want to know how to build a ROM from the my modified source for my Desire.
There is the need to build all the kernel and framework? or can I just to put a modified framework.jar inside the actual system?
I really cannot find any useful guide on how to build from the source android against Desire.
Thanks in advance, any help are very appreciated
Marco
Related
Hi, I am an android applications developer. I've been developing for a while now and i feel limited by the android library available. I would like to mod my galaxy nexus and modify the information available but I don’t know where to start.
I'm currently working with the signal strength libraries and the refresh rate is too low (i know its that way to be battery efficient) but for the needs of my application i need to boost that rate and to modify other. Should i look at modding the rom or modding the kernel directly for that kind of purpose? Any information on that subject is greatly appreciated
Alright so i'll assume you guys didn't understand what i am talking about.
I'm using android.telephony library. But the information it gives isn't accurate enough and the refreshrate of the listeners aren't precisse enough. Id like to modify it. But i'm not sure where to start. I've read a lot on internet but i can't find information about where to start. Can someone help me please ?
Yeah, I'm no expert, but that should be in the rom (radio interface layer).
Sent from my i9250
Hey thanks for the tip. I have read on ril and it might be about what I need. I'll be posing information about it if anyone needs it but googling ril gives pretty much all information needed.
This is hardcore hehe. I browsed trough all the ril libraries and i can't find the information. I really want to increase the sensitivity of the android.telephony.statelisterner and i am sure the hardware can dectect more information. It is just set like to prevent from battery drain... (imo)... There's not a lot of information on that topic. :S
Has anyone tried porting anything based on libnfc (libnfc.org), such as nfc-tools (code.google.com/p/nfc-tools), to Android?
I've heard of the odd person or two managing to cross-compile libnfc for Android and get it working with an external reader, but I'm more interested in getting nfcutils and mfoc to run on my Galaxy Nexus...
Hi,
I was looking for the same thing as you.
Indeed some people succeeded to compile libnfc on android (android 2.3 if I remember well) and they have published a little outdated tutorial.
The problem that is their porting use libusb and permits to use an external NFC reader connected via the phone USB link.
I think you are most interested in using the internal one.
On my galaxy SIII, the NFC device seems to use an I2C link (the device is /dev/pn544). So you will need to make a libnfc "driver" for your device wich link to the I2C. I you look into libnfc code, you have some code to mange serial links but it seems a little experimental.
Moreover, there is already a driver and a lib that manage your NFC device, so you'll probably have some conflicts by trying to add libnfc.
The built-in lib is libnfc-nxp wich also includes drivers, hardware abstraction and a upper level libraries (called "FRI") providing services to manage cryptography, NDEF messages and so on. This lib is completely different from the linux libnfc.
So if you want to get lib-utils working, you will probably need to compile them after developing a wrapper between libnfc functions using libnfc-nxp. (or something like this)
In my knowledge, nobody did the job yet.
I found some tries to recode mfoc utility in an android apk but nothing functional yet (and there is often no recent activity of these projects).
Sorry.
I found this:
https://github.com/ehabkost/nfc-tools (last activity two years ago)
It appears the Android API lacks some features to get the mfoc running.
It may be possible to overcome this modifying the libnfc-nxp source in the android repo....... who knows.
Porting [nfc-tools] libnfc to Android 4.4.2
Does anyone have news about this ?
I did some research though but instead of creating a new thread, I ended up here.
if anyone is still interested, I have compiled libnfc and nfc-list from last commit on git and works on my Nexus 5 5.0.1
You can find here github.com/etmatrix/libnfc and github.com/etmatrix/libusb01 for libusb
I attached an usb device SCL3711-NFC&RW and nfc-list show me a Mifare Classic and SRIX4K.
I need to improve external module libusb, libnfc look at /tmp/libusb-0.1.12 for linking.
etmatrix said:
if anyone is still interested, I have compiled libnfc and nfc-list from last commit on git and works on my Nexus 5 5.0.1
You can find here github.com/etmatrix/libnfc and github.com/etmatrix/libusb01 for libusb
I attached an usb device SCL3711-NFC&RW and nfc-list show me a Mifare Classic and SRIX4K.
I need to improve external module libusb, libnfc look at /tmp/libusb-0.1.12 for linking.
Click to expand...
Click to collapse
Hey! I'm just trying to get into this issue, and I would really appreciate if you could help with some piece of advice
I've digged up all google, but all instructables are dated 2010-2012, I am sure that there should be some progress in this area! My goal is to flash libnfc to Android and make it use an internal nfs chip
Can you contact me? It would also be great to have a compiled file to install libnfc to my galaxy s3 and some explanation, because unfortunately I'm just a beginner in this, though a really ambitious
Thank you!
Bump.
Any news on this? I'd really like to be able to read my public transportation pass to see how much I have credit left (It is mifare classic 1k). There is no official app to read it either (nor unofficial for what I know).
You can try the app "västtrafikreader" or vasttrafikreader. You have to google it yourself.
Classik k1 efter carry heavy encryption wich makes is almost impossible to ream them. But in vasttrafikreader they got the keys for the swedish system and the cards can even be manipulated.
Its rather safe to say that you basicly cant carry out the hack w/o the proper keys.
There have been ports of mfoc and similar tools for Android in the past, but only for externally connected NFC-Readers, since the Android APIs don't allow the necessary access to the internally embedded NFC chips. The best app for working with Mifare Classic NFC chips is the "MTC - Mifare Classic Tool", which is available on the Play Store. It's open-source on GitHub and supports reading and writing to the chips if you add the keys to the dictionary file or if the sector you're trying to access uses one of the default keys. This app could totally be expanded with mfoc-like functionality, at least on rooted devices, but for now you have to run mfoc on the PC once to get the keys, add them to the dictionary and afterwards you're able to get full read/write access to all sectors of the specific chip from a supported Android handset (hardware-wise, depends on the NFC chip used).
hello, its been 4 yearsany news on an internally embedded NFC chips mfoc functionality ?
We are looking for a person who is able write a customer Android ROM which we want to strip off many regular functions of android to increase speed of our auto data recorder. Running a customized app to act like black box of car. Together we need to connect to different sensors like GPS, Gyro, temp sensor etc. And have this person create updates for this ROM as soon as new updates are released. This would be temporary, with a full time option available based on performance.
Job Description
To write and edit the Android ROM to fit the device requirements.
Work at home!
Skills Required:
Familiar with Android programming
Experience in android ROM programming
Language: English (Chinese a bonus but not Crucial)
To Apply:
Please email blooming.tw.daniel (at) gmail.com to tell us a little bit about yourself, and what your past experience is relate to the project.
Salary:
YES! We will provide salary! We will talk about it when we receive your email.
Dear XDA members,
if you feel the same as the friends at https://postmarketos.org/ :
"We are sick of not receiving updates shortly after buying new phones. Sick of the walled gardens deeply integrated into Android
and iOS. That's why we are developing a sustainable, privacy and security focused free software mobile OS that is modeled after
traditional Linux distributions. With privilege separation in mind. Let's keep our devices useful and safe until they physically break!",
then it is time for you to step forward!!!
Last night initial support for the OPPO Find 7a was commited to the postmarketos pmaports git repo
https://gitlab.com/postmarketOS/pmaports with commit https://gitlab.com/postmarketOS/pmaports/commit/1f8095771c4659d31e8b228dd85018e9ca9963ca.
It was a pain to get this committed as I'm not used to the git workflow, nonetheless with the help of the maintainers over there
and after deleting a few merge requests ( a no-no, don't do that!!) at the end we got it done.
At the moment the device port is only for the Find 7a for the simple reason that I own one but I'm sure it can be extended to the
Find 7 and Find 7s.
The answer to the question that you dear reader have in your mind now: "what works?" is easy: NOTHING WORKS YET!!!
The only thing working so far is that the kernel compiles, you can flash it or fastboot boot it, start a rootfs on the microsd card
and ssh into the system over a usbnet connection to look at all that lovely processes running.
Lots of work still needs to be done, I'm pretty shure that I will not be able to do this myself as my knowledge about the hardware
part of the device is minimal and I would need to reinvent the wheel for every little progress.
As I'm sure that there are still a lot of knowleadgeable develepers (THAT'S YOU!!!) lurking around this list my hope is to lure them
to contribute to this project.
I personally dream of the Find 7 running postmarketos and KDE plasma-mobile but even maemo would be ok!!!
Come on, let's do it!!!
Best regards,
farmatito
Links to get more info:
https://postmarketos.org/
https://wiki.postmarketos.org/wiki/OPPO_FIND_7a_(oppo-find-7a)
https://wiki.postmarketos.org/wiki/Porting_to_a_new_device
Screen and touchscreen working!!!
Still a lot of work to do. Help is appreciated!
Progress report
New package for installing various firmware blobs merged!
Next big thing should be to try to make video hardware acceleration work,
if there are any experts here help is appreciated!!!!.
Progress report
The attached photo shows my Find7a running the XFCE4 desktop.
The interface is fast enough even without hardware acceleration.
As the Desktop is not optimized for mobile devices it is not
a such a great user experience, but the basics work.
Still a lot of work to do, help is appreciated.
Progress report
Wifi Works!!! and you can browse the internet!!!
Help is still appreciated!!
No progress
This time there is no progress to report:
video acceleration not working yet due to the fact that the kernel is rather old (3.4.113), backporting newer drivers did not work out as the codebase differs to much (so no KDE plasma).
making the various sensors work is also rather difficult as the kernel uses a Device Tree and so even if there are drivers for the sensors you need some board specific info to create the device tree nodes.
last but not least the last version of xfce4 in alpine linux is not touchscreen friendly. GTK combo-boxes are now unusable (will eventually try maemo).
Help is very, very appreciated.
Saw this post, has a Find 7 and want to know more.
Hey,
I created my own Lauchner and wanted to integrate the radio functions.
Since I didn't find any information on the internet about how the original app addresses the radio module, I reverse engineered the app.
To make it easier for others I decided to start an Android Studio project.
The project is only very basic to show how the radio module is controlled.
I also added an extension to it.
Using the RDS signal and a SQlite database the station name and logo are displayed.
I hope it is helpful to anyone.
I uploaded the project to Github:
-https://github.com/zebbel/MTCD-E_Radio-app
(Sorry I´m not allowed to post links)
Kind regards
David
Great work!
Hey,
I have compiled the CarManager module into a jar file for easier use in Android Studio projects.
To be honest I never tried to understand how it works exactly, because it just works :laugh:
I know that I downloaded the files somewhere on Github, but I have absolutely no idea where.
If the "creator" of the files is here please let me know so I can give him credit.
-https://github.com/zebbel/microntek_CarManager
(I need still more posts to create links )
Thank you very much for your work!
Thanks to your library I realized a widget that reads (and shows) the battery voltage value.
I have a question : do you have a complete list of "type" that can be used ?
In you example you attached to your handler the types:
- Radio
- KeyDown
In my case I used "CarEvent" :
Java:
CarManager carManager = new CarManager();
CarManagerHandler carManagerHander = new CarManagerHandler(this);
carManager.attach(carManagerHander, "CarEvent");
In this way my Handler is receiving all the CarEvents. The voltage is contained in the message tagged as "battery".
There are other types that we can use in order to catch other interesting events?
Thank you,
Salvo