Im looking for a developer that has experience with google services especially the google calender.
We have a fully fleshed out idea. I have one developer now but he does not have much time.
native android code will be used and we are developing with android studio. We have a git repo (currently empty) setup and notes and slides from the initial discussion phase of the development process.
I can not reveal specific details about the app only that it will tie in directly to google calendar and that most of the code for the app can be pulled from the current calendar app and reworked for this project. This will be a pay app (might have limited free version) and there is definite potential for profit.
If you are interested please contact me via PM so that we may discuss it further.
Hi folks,
I am a huge LifeLog fan, and I like all the more details this platform has over Google Fit. Last year, Sony had made the web API open. (REST + Oauth based).
https://developer.sony.com/develop/services/lifelog-api/
I had just started working on an app for the LifeLog platform and realised there is certain need for a android java library (as a wrapper over the REST API) for LifeLog. As an app developer wanting to quickly take advantage of LifeLog, it is too much to ask for to implement oauth and rest client side functionality.
So here goes a Work-in-progress repository
https://github.com/championswimmer/Lifelog-Android-Library
As of Apr 22, 2015, Login, auth_token generation is working. Also fetching location history data is also working. The activities data implementation is yet to be done. I intend to finish that in a couple of days maybe.
Code can be shoddy. If you can help me improve, I'd definitely love that.
Feel free to open up issues on the github repo to report any bugs or problems you have with it.
Honestly I'm not sure if this is allowed (sending others guides) but I simply followed 2 guides after I had installed ArCore, one was to check the status of my Cameras capabilities for Google API 2 and the other was a guide to change my phone to support API 2, basically the mi a2 DOES SUPPORT Google API but on my stock ROM this is NOT ENABLED, but after a quick tweak to a buildprop file using Terminal, and a simple restart, all features are WORKING nicely, this is tested on a modded version of Google Camera and the beta for Minecraft Earth. Happy Gaming I hope this works for you all as well
Please try Following these Easy guides
[Type in the front part here/enable-camera2-api-xiaomi-mi-a2-lite-guide/]
[Type in the front part here/check-camera2-api-support-android/#How-To-Check-Camera2-API-Support-on-Android]
(P.S If these links are blurred thank xda for being extra safe :| hopefully you can see enough of them to Google the website yourself, hope this helps!)
(P.P.S the website was from the custom droid dot com)
Hi fellows
I need your help
I bought some WITMOTION sensors (USB and BLE) wich includes accelerometer, gyro and other cool things)
They have sample code APK to pair / read data from their hardware, that's ok but....
... what I really need is to broadcast that data (if possible) to android kernel, to ensure that apks like GMaps, Waez, Torque pro (accelerometer) and other stuff use that data as if the data came from embedded Android sensors.
Do you think that this project is doable ?
?
Hi
Found this tread and was hoping you had a win with the search for information as I am thinking of getting a 9 axis WitMotion sensor to use with an android car head unit that has no built in magnometer.
Cheers
GitHub - vicnevicne/witmotionDemoAndroidApp: Source of the Android app demonstrating use of Witmotion IMU sensors
Source of the Android app demonstrating use of Witmotion IMU sensors - GitHub - vicnevicne/witmotionDemoAndroidApp: Source of the Android app demonstrating use of Witmotion IMU sensors
github.com
and for windows at
Google Drive - Virus scan warning
drive.google.com
LineageOS 20 UNOFFICIAL for 2014 Samsung Galaxy Tab S 10.5 LTE/WifiModel: SM-T805 (LTE) - chagalllte - 10.5" screen, Exynos 5420 SoC, LTE
Model: SM-T800 (Wifi) - chagallwifi - 10.5" screen, Exynos 5420 SoC, Wifi
These are the ONLY models that the ROM will work on.
You MUST READ posts 1-4 (about 10 minute read) before deciding to install this rom. If you think this is an unreasonable request, then stop reading now and find another rom. Thank you.
DISCLAIMER
I am not responsible for lost data, identity theft, lost money, security vulnerabilities, bricked devices or any other hardware or software malfunctions that comes as a result of flashing this rom.
All involved in bringing this build to you are working voluntarily on it in very limited spare time, and their other life commitments have much higher priority. Don't expect a prompt, or even any, response to questions and bug reports.
Before attempting to install this ROM
1. Ask yourself: would bricking your device be a disaster for you? If yes, don't try this ROM! It can't be guaranteed stable and reliable enough to depend on for daily use.
2. BACKUP YOUR DATA AND EXISTING ROM. Be prepared for a complete restore if anything goes wrong.
3. RESEARCH adb, fastboot, Odin/heimdall, and TWRP and how to use them, if not already familiar with these.
What works
1. bluetooth
2. wifi
3. brightness
4. external audio
5. audio through headphone jack
6. audio over bluetooth
7. selinux enforcing
8. DRM level 3 (SD definition)
9. deep sleep
10. camera
What doesn't work
1. Fingerprint is completely removed in 19.1 (According to @retiredtab it was not compatible with keystore2)
2. DRM level 1 (no HD definition).
3. Workaround to disable scoped storage. In 18.1 there was a workaround to disable scoped storage, but that no longer works in 19.1. So if you have a lot of apps or data on an external microsd, the performance may be severely degraded.
4. GPS (Works For Chagallwifi)
5. RIL (LTE/4G)
6. Aggressive Low Memory Killer ( Might Cause Apps to crash in some cases, @bluess57 Explained Here)
Thanks
1. LineageOS team for source code.
2. @bluess57
- Helping Debug Issues and sending needed patches
3. @retiredtab
- Did Most of the work on the Device Trees for chagallwifi which i based on, Helped with patches from his guide for the tab S2
4. exynos5420 team
- Most of the work for the los 18.1 bringup for 5420 devices
5. @garak elim
- Made Initial LOS 19.1 device trees which i used too
6. @SirRGB
- Helped with debugging, helped me figure out why device was not booting
7. @phhusson
- Helped with selinux enforcing and debugging
8. @Linux4
- Helped with Getting HWC working on Los 20
9. Los-UL Team
- Patches For LOS 20 on 3.4 devices
Sorry if i missed anyone
Source Code:
- Device Tree: https://github.com/davigamer987/android_device_samsung_chagalllte
- Kernel Source: https://github.com/davigamer987/android_kernel_samsung_exynos5420
- Others can be found on my GitHub profile: https://github.com/davigamer987?tab=repositories
Download (LTE) : Download (GitHub)
Download (Wifi): Download (Github)
Broken: GPS (Works on Wifi Model), Fingerprint, RIL/LTE, DRM L1
Use NikGapps for Google Apps
Note: Some of this post's text was taken from the @retiredtab post for the Tab S2
Reserved #1
Image:
Possibly Android 13 soon!
Probably worth mentioning some other things that need testing/may not be working
- Wifi security mixed mode wpa2+wpa3 (broken on 18.1, likely not working)
- logitech usb mouse + keyboard
(HID code in kernel you may not have)
- Bluetooth headset in phone calls (broken since 17.1?)
bluess57 said:
Probably worth mentioning some other things that need testing/may not be working
- Wifi security mixed mode wpa2+wpa3 (broken on 18.1, likely not working)
- logitech usb mouse + keyboard
(HID code in kernel you may not have)
- Bluetooth headset in phone calls (broken since 17.1?)
Click to expand...
Click to collapse
My ****ty isp does not allow me to change router settings so i can't test wpa2+wpa3 and i don't have a logitech mouse or keyboard, i'll try bt headset in calls
ROM_gamer987 said:
My ****ty isp does not allow me to change router settings so i can't test wpa2+wpa3 and i don't have a logitech mouse or keyboard, i'll try bt headset in calls
Click to expand...
Click to collapse
Got another router? Bridge the ISP router to the 2nd.
Ditch that isp
Great Job man! we should work together and get LOS19.1 for the Samsung Galaxy S5 3G which is based on a very similar SoC Exynos5422. As far as fingerprint is concerned, I think you should be able to use the HAL me and @VDavid003 wrote for the S5 with some extra binderizing as long as the Tab S has same fp sensor.
Feel free to DM me or on Telegram.
Akhil99 said:
Great Job man! we should work together and get LOS19.1 for the Samsung Galaxy S5 3G which is based on a very similar SoC Exynos5422. As far as fingerprint is concerned, I think you should be able to use the HAL me and @VDavid003 wrote for the S5 with some extra binderizing as long as the Tab S has same fp sensor.
Feel free to DM me or on Telegram.
Click to expand...
Click to collapse
This is the kernel fingerprint sensor driver code
android_kernel_samsung_exynos5420/drivers/fingerprint/vfs61xx.c at lineage-18.1 · exynos5420/android_kernel_samsung_exynos5420
Contribute to exynos5420/android_kernel_samsung_exynos5420 development by creating an account on GitHub.
github.com
According to this , they are using same chip
[Q] Fingerprint Reader Encryption?
Once a user swipes his finger on the sensor, the resulting fingerprint image is compared to a set of stored fingerprint images. Does anybody know if these stored images are encrypted (and if so, what type of encryption)? Are the stored images...
forum.xda-developers.com
Akhil99 said:
Great Job man! we should work together and get LOS19.1 for the Samsung Galaxy S5 3G which is based on a very similar SoC Exynos5422. As far as fingerprint is concerned, I think you should be able to use the HAL me and @VDavid003 wrote for the S5 with some extra binderizing as long as the Tab S has same fp sensor.
Feel free to DM me or on Telegram.
Click to expand...
Click to collapse
Sure if you can send that I'll try it out
bluess57 said:
Got another router? Bridge the ISP router to the 2nd.
Ditch that isp
Click to expand...
Click to collapse
I have an old router that i can try with later
ROM_gamer987 said:
Sure if you can send that I'll try it out
Click to expand...
Click to collapse
HAL Source Code:
android_device_samsung_k3gxx/hal/fingerprint at cm-14.1 · VDavid003/android_device_samsung_k3gxx
Contribute to VDavid003/android_device_samsung_k3gxx development by creating an account on GitHub.
github.com
Compile both HAL and Lib, should work fine. IIRC, will require a service too.
Akhil99 said:
HAL Source Code:
android_device_samsung_k3gxx/hal/fingerprint at cm-14.1 · VDavid003/android_device_samsung_k3gxx
Contribute to VDavid003/android_device_samsung_k3gxx development by creating an account on GitHub.
github.com
Compile both HAL and Lib, should work fine. IIRC, will require a service too.
Click to expand...
Click to collapse
Sorry I'm a bit dumb with FP Stuff, do i just add the Hal to dt? Is the lib/service separate?
ROM_gamer987 said:
Sorry I'm a bit dumb with FP Stuff, do i just add the Hal to dt? Is the lib/service separate?
Click to expand...
Click to collapse
Yes tha hal code would go into a suitable place in the devices tree
vcsFPservice in the vendor bin might need replacing see
android_vendor_samsung_chagall-common/proprietary/vendor/bin at lineage-18.1 · exynos5420/android_vendor_samsung_chagall-common
Contribute to exynos5420/android_vendor_samsung_chagall-common development by creating an account on GitHub.
github.com
bluess57 said:
Yes tha hal code would go into a suitable place in the devices tree
vcsFPservice in the vendor bin might need replacing see
android_vendor_samsung_chagall-common/proprietary/vendor/bin at lineage-18.1 · exynos5420/android_vendor_samsung_chagall-common
Contribute to exynos5420/android_vendor_samsung_chagall-common development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
What would i replace it with? (Sorry if I sound dumb, really don't know how these FP blobs work)
adrod 13 btw
Akhil99 said:
HAL Source Code:
android_device_samsung_k3gxx/hal/fingerprint at cm-14.1 · VDavid003/android_device_samsung_k3gxx
Contribute to VDavid003/android_device_samsung_k3gxx development by creating an account on GitHub.
github.com
Compile both HAL and Lib, should work fine. IIRC, will require a service too.
Click to expand...
Click to collapse
i was able to add it to dt based on the commits made to that tree, fingerprint enroll is no longer an option now (Device does not give fp option)
heres logs: https://realmeme.realmemecloud.workers.dev/0:/tl
ROM_gamer987 said:
i was able to add it to dt based on the commits made to that tree, fingerprint enroll is no longer an option now (Device does not give fp option)
Click to expand...
Click to collapse
From memory and what Akhil99 said above, you will need to create a service which starts fingerprint hal
You'll have to read thru
Android OS Source Documentation | Android Open Source Project
source.android.com
See topics about hal
As an example see service.cpp
biometrics/fingerprint/2.1/default - platform/hardware/interfaces - Git at Google
bluess57 said:
From memory and what Akhil99 said above, you will need to create a service which starts fingerprint hal
You'll have to read thru
Android OS Source Documentation | Android Open Source Project
source.android.com
See topics about hal
As an example see service.cpp
biometrics/fingerprint/2.1/default - platform/hardware/interfaces - Git at Google
Click to expand...
Click to collapse
oof that looks hard to do, i really don't have c++ coding skills to make a service ( I tried and didn't figure it out )