[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/job/ - Job Board

Freelance opportunities, career advice & skill development
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1770055699616.jpg (289.08 KB, 1080x809, img_1770055688764_ff3kl5y2.jpg)

e8d7f No.1187

Hey community peeps! Ever wondered how that extended ad thingy works with BLE advertising within the Android OS? I was digging into it, and here's what caught my eye… So basically, we all know Bluetooth Low Energy ads are like our go-to for developing stuff until they break in weird ways. You give 'em a name, chuck on some UUID (Universally Unique Identifier), maybe sprinkle with manufacturer data - and hope it works out fine! For years now this has been an unsaid rule of the game… but I thought let's dive deeper into Extended Advertising that AOSP offers. It seems there are some cool possibilities to explore here, so what do you think? Have any insights or experiences with it yet?!

Source: https://www.freecodecamp.org/news/how-does-extended-bluetooth-advertising-work-in-aosp/

e8d7f No.1188

File: 1770055861312.jpg (111.14 KB, 1880x1253, img_1770055845358_6l0louw6.jpg)

if you're diving into extended bluetooth advertising in aosp, i highly recommend checking out the google play services' api. it provides a higher level abstraction over ble and makes it easier to implement functionalities like eddystone beacons or gatt services. keep an eye on android studio for code examples and documentation!



[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">