Noha Samir’s Post

I would like to share a problem with the #Android #emulator, which is the cutting of screen pixels. It was solved by stopping the update for the emulator and replacing the emulator version with an old version from the website https://lnkd.in/d36yfzrx Thanks #android_studio #FlutterAppDevelopment #FlutterDev #flutter #dart #FlutterMobileApp #MVVM

Hey everyone 👋 It's #Day30 of my #100daysofcodechallenge. Today, I worked on: - Creating dialogs - Creating the process for Camera/Gallery images for latest Android APIs. I also worked on creating a model for a complex screen, which involved merging data from several sources into a usecase to populate the screen. I'm not done yet, but I'm making progress. That's basically what I achieved today. What were you able to achieve today? See you tomorrow 😌 #android  #kotlin  #datamodel #image #screens #dialogs #usecase

#android #android15 #android15update #androidgames #foryou #usa #android14  #mobile #viral #fyp #video #trending #scienceonline #science_online #hebasoffar Android 15 is the latest iteration of Google's mobile operating system, It builds on previous versions with new features focused on user experience, privacy, customization, and AI integration. Android 14 is already widely available, It focuses on privacy, with features like grouped widgets, Ultra HDR support, generative AI wallpapers, and the ability to use your phone as a webcam.

No need to memorize the Activity Life cycle Chart , just have a look 👇 . . . . 1. onCreate(): Initializes the activity. * Called: When the activity is first created. 2. onStart(): Prepares the activity to become visible. * Called: Just before the activity becomes visible. 3. onResume(): Makes the activity interactive with the user. * Called: When the activity starts interacting with the user. 4. onPause(): Pauses the activity; save changes and pause operations. * Called: When the activity is partially obscured or the user navigates away. 5. onStop(): Hides the activity from the user; release resources. * Called: When the activity is no longer visible. 6. onDestroy(): Cleans up before the activity is destroyed. * Called: Before the activity is completely removed from memory. 7. onRestart(): Restarts the activity after being stopped. * Called: When the activity is being restarted after being stopped. and that's it #android #androiddevelopment #mobile

#needhelp #android #timer #bug I have implemented simple timer but i faced time delay issue when device screen continues active and timer running after 15-20 mins it's show 0.5-1 minutes delay with exact time. long timerDuration = Long.MAX_VALUE; // Use a very large number to simulate indefinite counting // Create and start the CountDownTimer breakTimer = new CountDownTimer(timerDuration, 1000) { // Count down in intervals of 1 second @Override public void onTick(long millisUntilFinished) { // Increment the break time // Calculate hours, minutes, and seconds int h = totalBreakSeconds / 3600; int m = (totalBreakSeconds % 3600) / 60; int s = totalBreakSeconds % 60; // Update the UI breakHours.setText(String.format("%02d", h)); breakMinutes.setText(String.format("%02d", m)); breakSeconds.setText(String.format("%02d", s)); totalBreakSeconds++; } @Override public void onFinish() { // You can implement logic here if you want to handle the end of the timer // For this use case, it will not reach here because of Long.MAX_VALUE } }.start();

Did you know an #Android 'tap event' might cause issues if you boost application performance? Learn what Square engineer Inez K. has to say about these Android nuances, and #flakytests in general, in this conversation with Trisha Gee! Full conversation (26min) 👇 https://lnkd.in/gftGRV7u

A paging use case with room which returned just 10 items in whooping 40s. Cause: BaseViewModel with an init block containing 8 method calls. Now imagine an activity with 5 viewmodels that inherit BaseViewModel 5×8 = 40 method calls = 40s until we get paging results on screen :D Cheers to slowness .. again! #Android #Performance

Improved Frame Drop Visualization is now available for #Android! PS Tool now highlights fewer frames, taking into account clusterization to better focus on scroll performance analysis. This means we only highlight frames that take 2x longer than expected and clusters of several longer frames, even if they don’t reach the 2x threshold. This approach confirms the same frame patterns previously reported via PS Tool by performance analysts while significantly reducing noise. Learn more: https://lnkd.in/gEEXa6Wt

Are you writing your Android Compose Code Future-Proof? 🤔 - Composable functions currently run on the main thread, but future updates may allow them to execute in parallel on background threads, as indicated in Android documentation. - This potential change could optimize recomposition by utilizing multiple CPU cores and managing lower-priority composables more efficiently, which may improve overall app performance. - To ensure correct behavior in this evolving context, composables must be side-effect free, with side-effects triggered only through UI callbacks (e.g., button clicks) that execute on the main thread. - The execution order of composable functions is not guaranteed; they may run in any sequence based on priority, highlighting the need for careful design to accommodate possible future changes. 𝐅𝐨𝐫 𝐦𝐨𝐫𝐞 𝐝𝐞𝐭𝐚𝐢𝐥𝐬: https://lnkd.in/grEAyUYz 𝐌𝐞𝐝𝐢𝐮𝐦 𝐇𝐚𝐧𝐝𝐥𝐞: https://lnkd.in/gPaSvZRU Follow Kapil Sachan and tap on #cwkarticles for more interesting articles 🚀 #codewithkapil #android #androiddevelopment #compose #kotlin #performance #stable #future

Explained: #Android_overlays and how they are used to trick people https://vapt.me/OverLays