Timeline for Android Version differs from expected API level
Current License: CC BY-SA 4.0
13 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Jun 25, 2020 at 21:42 | vote | accept | Karampistis Dimitrios | ||
Jun 25, 2020 at 21:42 | answer | added | Karampistis Dimitrios | timeline score: 1 | |
May 26, 2020 at 21:00 | history | tweeted | twitter.com/StackAndroid/status/1265387257554448396 | ||
May 26, 2020 at 16:43 | answer | added | Fidz | timeline score: 0 | |
May 26, 2020 at 10:31 | comment | added | Karampistis Dimitrios | @Robert Yeah I have a CM 10.1 copy but it stuck in bootloop | |
May 26, 2020 at 10:17 | comment | added | Robert | You are a little bit late searching a for a custom ROM. There was a CyanogenMOD release for that device but the download links have long gone dead. | |
May 26, 2020 at 10:09 | comment | added | Izzy |
@KarampistisDimitrios the warning comes from the adb executable on your computer (unfortunately, it looks like adb backup shall be dropped, leaving non-root users in the dark again). The second one is the interesting one here: it indeed seems the ADB daemon on the device doesn't know about the backup command; as you're unlikely to be on Android 11+, this must mean you're on < 4 then – and the "5.0.1" is fake.
|
|
May 26, 2020 at 10:08 | history | edited | Karampistis Dimitrios | CC BY-SA 4.0 |
added 2 characters in body
|
May 26, 2020 at 10:02 | comment | added | Karampistis Dimitrios |
@Izzy I tried running adb backup the result was adb backup -apk -shared -all -f mybackup.ab WARNING: adb backup is deprecated and may be removed in a future release adb: unable to connect for backup: closed The device is getting recognized when I use adb devices .
|
|
May 26, 2020 at 7:21 | comment | added | Izzy |
@Robert that can be verified easily: adb backup was introduced with ICS (Android 4.0). If it's indeed only "surface polishing" of a Gingerbread OS, adb backup won't work. If it does work, it's a clear indicator of at least Android 4.0 (or higher) being present, and the ROM dev maybe just forgot to update ro.build.version.sdk in build.prop .
|
|
May 26, 2020 at 7:15 | comment | added | Robert | May be the ROM author was only aiming for the look-and-feel of Android 5? | |
May 26, 2020 at 2:02 | review | First posts | |||
Jun 1, 2020 at 19:43 | |||||
May 26, 2020 at 2:00 | history | asked | Karampistis Dimitrios | CC BY-SA 4.0 |