Infeasible
Status Update
Comments
ba...@gmail.com <ba...@gmail.com> #2
since these are in public API (:/) we need to do this in 1.2
ad...@google.com <ad...@google.com>
ad...@google.com <ad...@google.com> #3
since it is already marked as deprecated, we can probably do it by now.
ba...@gmail.com <ba...@gmail.com> #4
Opening diff shortly
ad...@google.com <ad...@google.com> #5
Project: platform/frameworks/support
Branch: androidx-master-dev
commit d576cbdc911cba16638a44fd8223391a90a07ef7
Author: Mike Nakhimovich <digitalbuddha@users.noreply.github.com>
Date: Tue Aug 11 09:30:34 2020
[GH] Hide deprecated internal API.
## Proposed Changes
* `RoomDatabase.java` has protected `mCallbacks` field which is leaking in the API docs, we should @Hide it.
## Testing
Test: Ran unit tests locally
## Issues Fixed
Fixes: 76109329
This is an imported pull request fromhttps://github.com/androidx/androidx/pull/61 .
Resolves #61
Github-Pr-Head-Sha: 6440daa3a63752c7f9d5ba2a390248cd85bc634f
GitOrigin-RevId: fe92d8466a59b44b218b6ca3cbd57dcda17992f7
Change-Id: Id599cdf5b02b32bdae0166266fb7da967598fe92
A room/runtime/api/current.ignore
M room/runtime/api/current.txt
M room/runtime/api/public_plus_experimental_current.txt
M room/runtime/api/restricted_current.txt
M room/runtime/src/main/java/androidx/room/RoomDatabase.java
https://android-review.googlesource.com/1396827
Branch: androidx-master-dev
commit d576cbdc911cba16638a44fd8223391a90a07ef7
Author: Mike Nakhimovich <digitalbuddha@users.noreply.github.com>
Date: Tue Aug 11 09:30:34 2020
[GH] Hide deprecated internal API.
## Proposed Changes
* `RoomDatabase.java` has protected `mCallbacks` field which is leaking in the API docs, we should @Hide it.
## Testing
Test: Ran unit tests locally
## Issues Fixed
Fixes: 76109329
This is an imported pull request from
Resolves #61
Github-Pr-Head-Sha: 6440daa3a63752c7f9d5ba2a390248cd85bc634f
GitOrigin-RevId: fe92d8466a59b44b218b6ca3cbd57dcda17992f7
Change-Id: Id599cdf5b02b32bdae0166266fb7da967598fe92
A room/runtime/api/current.ignore
M room/runtime/api/current.txt
M room/runtime/api/public_plus_experimental_current.txt
M room/runtime/api/restricted_current.txt
M room/runtime/src/main/java/androidx/room/RoomDatabase.java
ba...@gmail.com <ba...@gmail.com> #6
I already tried the same and flashed the device also... It's still not
working not sure what is the actual issue.
Regards,
BALASUNDARAM C.
+918148290728
On Fri, 17 Jan, 2025, 10:13 pm , <buganizer-system@google.com> wrote:
working not sure what is the actual issue.
Regards,
BALASUNDARAM C.
+918148290728
On Fri, 17 Jan, 2025, 10:13 pm , <buganizer-system@google.com> wrote:
ad...@google.com <ad...@google.com> #7
We have passed this to the development team and will update this issue with more information as it becomes available.
ba...@gmail.com <ba...@gmail.com> #8
Sure thanks for letting me know on this
Regards,
BALASUNDARAM C.
+918148290728
On Mon, 20 Jan, 2025, 7:49 pm , <buganizer-system@google.com> wrote:
Regards,
BALASUNDARAM C.
+918148290728
On Mon, 20 Jan, 2025, 7:49 pm , <buganizer-system@google.com> wrote:
ba...@gmail.com <ba...@gmail.com> #9
Can I have an update here.
I see few of the members are also getting struggle now.
https://www.reddit.com/r/Pixel6/s/l4gnbyLrBp
I feel like this is now becoming a global issue. Please treat this as
urgent or else this will become a critical.
Note : my device still not turned on.
Regards,
BALASUNDARAM C.
+918148290728
On Mon, 20 Jan, 2025, 11:30 pm Balasundaram C, <balasndrm348@gmail.com>
wrote:
I see few of the members are also getting struggle now.
I feel like this is now becoming a global issue. Please treat this as
urgent or else this will become a critical.
Note : my device still not turned on.
Regards,
BALASUNDARAM C.
+918148290728
On Mon, 20 Jan, 2025, 11:30 pm Balasundaram C, <balasndrm348@gmail.com>
wrote:
ba...@gmail.com <ba...@gmail.com> #10
Even after multiple follow ups I am not getting any updates here. Are we
really looking at this or just keeping aside for now?.
I see like the same issue been faced by another user also posted in the
reddit thread.
https://www.reddit.com/r/android_beta/s/XB6I8p8bwY
Regards,
BALASUNDARAM C.
+918148290728
On Wed, 22 Jan, 2025, 12:02 am Balasundaram C, <balasndrm348@gmail.com>
wrote:
really looking at this or just keeping aside for now?.
I see like the same issue been faced by another user also posted in the
reddit thread.
Regards,
BALASUNDARAM C.
+918148290728
On Wed, 22 Jan, 2025, 12:02 am Balasundaram C, <balasndrm348@gmail.com>
wrote:
ba...@gmail.com <ba...@gmail.com> #11
Hi Team,
Are you guys really focusing on this or this is getting ignored.
Could you please acknowledge is the below link will help me to recovery
https://www.gadgets360.com/mobiles/news/google-pixel-software-stuttering-issues-fix-report-7647874
Regards,
BALASUNDARAM C.
+918148290728
On Fri, 31 Jan, 2025, 7:47 am Balasundaram C, <balasndrm348@gmail.com>
wrote:
Are you guys really focusing on this or this is getting ignored.
Could you please acknowledge is the below link will help me to recovery
Regards,
BALASUNDARAM C.
+918148290728
On Fri, 31 Jan, 2025, 7:47 am Balasundaram C, <balasndrm348@gmail.com>
wrote:
an...@gmail.com <an...@gmail.com> #12
After updating my pixel 6 with the February 5 security update my phone is now stuck on the Google logo boot screen. Volume down brings up fastboot but will not enter recovery mode. Support wasn't able to help.
da...@gmail.com <da...@gmail.com> #13
Since the last update, my phone has started to randomly reboot. I am on a pixel 6 pro with Baklava. I have counted 5 today. I have taken the phone out of developer mode, but it is still happening.
ad...@google.com <ad...@google.com> #14 Restricted+
Restricted+
Comment has been deleted.
ad...@google.com <ad...@google.com> #15
ba...@gmail.com <ba...@gmail.com> #16
This hardware problem created by your latest version of Android.... It's not because we disturbed the hardwares right... Almost most of the people started facing this issue for last 5 months. Just wanted to ask is this the trick been performed to crash all the pixel 6 series device through such action performed with the updates and looks like it's a business tactics played to crash all their old devices so that people can buy your new devices. Could you please confirm this... And i want to see how many pixel 6 devices got crashed in the last six months can you please generate something on this.
Description
What
User experience
What type of Android issue is this?
Reboot, Crash or Device Hang
What steps would let us observe this issue?
What did you expect to happen?
Permenent solution for this fix
What actually happened?
When phone gets shutdown not turning up immediately
What was the effect of this issue on your device usage, such as lost time or work?
Extreme - device was unusable
Additional comments
Please look into this issue immediately
When
Time and frequency
Time when bug report was triggered: Jan 16, 2025 10:59 AM GMT+05:30
How often has this happened?
Frequently
Where
Component
Suggested component: <not visible> (1630575)
Build and device data
- Build Number: google/raven_beta/raven:15/BP11.241121.013/12873528:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
Debugging information
Google Play services
com.google.android.gms
Version 245032035 (24.50.32 (260400-705598854))
System App (Updated)
Android System WebView
com.google.android.webview
Version 683405642 (132.0.6834.56)
System App (Updated)
Network operator: Not available
SIM operator: Not available
Filed by Android Beta Feedback. Version (Updated): 2.46-betterbug.external_20241023_RC01 (DOGFOOD)https://developer.android.com/preview/feedback#feedback-app .
To learn more about our feedback process, please visit