I had been using a 4.0 rom for a while, but I couldn't find any good Kitkat themes with the status bars and UI and such, so I install Gin2Kitkat. I had one or two apps that I liked that required a higher version of Android, so is there any way to force install an app that requires 4.0 or higher? For example Scribblenauts Remix, when I tried to re install that is has a "problem parsing the package". Any help is appreciated, thanks!
As far as I know, No. Every android upgrade that I've seen has always updated what's known as a API (Aplicaton programing interface) level (these range from 1-19 if I'm not mistaken) and every jump in these levels can't be backported.
So let's say you have a app like Greenify, this app has been built with the advancements and protocols of API level 14 which is ICS these standards were introduced in ICS so anything before it will not know how to run it.
Think of it this way, if you have a program built to run on windows 8 its not gunna run on windows xp. Why? Because windows xp has no idea how to run it.
But then what about apps that are built for android 2.3? how come they can run on 4.0? This is because when you update it you can still leave the old instructions on how to run the app.
So yea, sorry for the long explaination. If you need any other info refer to this http://en.wikipedia.org/wiki/Android_version_history
Sent from my Droid using xda app-developers app
but some of the apps can be ported froma higher api to a lower one
for example xperia z1 walkman that was made for jb 4.1 api i think but its ported to ics now
Yea some apps with modifications can be back ported...idk you can try to backport it but I doubt it will be worth your time
Sent from my Droid using xda app-developers app
Look, if like to start by saying I couldn't find the question section in tapatalk, and this seemed the most appropriate section to post in (move to correct one if necessary)
Anyway, my question:
I was wondering if it's possible to build either android honeycomb or tablet UI ICS (stock of course) for this kindle fire. I know that it seems weird to go back word in android versions, but honeycomb is my favorite and I wouldn't be able to build it as I don't have a Linux PC, and I'm having a surprising amount of trouble getting virtual box to work on my PC. (Yes, I'm using the correct cup architecture and have all required files) any feedback is welcome!
Edit: any way to edit the title? I didn't catch the typo... (Yet another reason to proof read)
Sent from my iPhone using Tapatalk
MeowDude said:
Look, if like to start by saying I couldn't find the question section in tapatalk, and this seemed the most appropriate section to post in (move to correct one if necessary)
Anyway, my question:
I was wondering if it's possible to build either android honeycomb or tablet UI ICS (stock of course) for this kindle fire. I know that it seems weird to go back word in android versions, but honeycomb is my favorite and I wouldn't be able to build it as I don't have a Linux PC, and I'm having a surprising amount of trouble getting virtual box to work on my PC. (Yes, I'm using the correct cup architecture and have all required files) any feedback is welcome!
Edit: any way to edit the title? I didn't catch the typo... (Yet another reason to proof read)
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
This would likely be better suited in the KFHD 8.9" Q&A forum. That being said, there will be significant work involved with porting. Honeycomb on these kindles would be like porting Windows 95 to run on a modern-day laptop. It might work, but it's unlikely. You'd have to spend a lot of time backporting Amazon's proprietary drivers (or even open source libraries, if such are still supported for older Android versions), and those are likely built with 4.0 in mind. Additionally, the underlying Android Honeycomb source code may not have critical components needed for proper operation on more recent devices like these. (It's worth noting that Amazon's stock firmware is based on ICS, so a large part of that work would likely be done already if you're porting that Android base.) Finally, I'd advise against porting older Android versions because they're not maintained or supported anymore by Google, so any compromising bugs or security holes (like the recent Stagefright issues) will not have been backported to those unsupported releases.
If you're still set on porting ICS, I haven't found any stock 4.0 build makefiles for the HD 8.9 on GitHub. You could use an unofficial prebuilt CM10.1 or CM10.2 ROM (look in the 8.9 development forum and use Xposed modules to modify the UI to tablet mode. I know of one Xposed module that backports tablet UI to JB ROMs, and it still works on KitKat/CM11. Those mods would save you a lot of time, as you wouldn't need to compile or backport older releases. If you want an up-to-date CM11 ROM to use the mods on, you'd need to compile with those sources (they're on GH here). If you're still having trouble, I'd be willing to compile CM11 for you.
Sent from my Amazon Jem using XDA Labs
monster1612 said:
This would likely be better suited in the KFHD 8.9" Q&A forum. That being said, there will be significant work involved with porting. Honeycomb on these kindles would be like porting Windows 95 to run on a modern-day laptop. It might work, but it's unlikely. You'd have to spend a lot of time backporting Amazon's proprietary drivers (or even open source libraries, if such are still supported for older Android versions), and those are likely built with 4.0 in mind. Additionally, the underlying Android Honeycomb source code may not have critical components needed for proper operation on more recent devices like these. (It's worth noting that Amazon's stock firmware is based on ICS, so a large part of that work would likely be done already if you're porting that Android base.) Finally, I'd advise against porting older Android versions because they're not maintained or supported anymore by Google, so any compromising bugs or security holes (like the recent Stagefright issues) will not have been backported to those unsupported releases.
If you're still set on porting ICS, I haven't found any stock 4.0 build makefiles for the HD 8.9 on GitHub. You could use an unofficial prebuilt CM10.1 or CM10.2 ROM (look in the 8.9 development forum and use Xposed modules to modify the UI to tablet mode. I know of one Xposed module that backports tablet UI to JB ROMs, and it still works on KitKat/CM11. Those mods would save you a lot of time, as you wouldn't need to compile or backport older releases. If you want an up-to-date CM11 ROM to use the mods on, you'd need to compile with those sources (they're on GH here). If you're still having trouble, I'd be willing to compile CM11 for you.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
Thanks for the feedback, my heart is indeed set on back porting honeycomb, I'll try later and see how it works out. I'm gonna have to research the recent stage fright bug (haven't heard of it). I figured I could just build android 3.2 from AOSP, set up the necessary drivers, and flash it. Even if that's not an option, I'll just try to build Stock ICS. I just like the older holo UI, and ICS and especially Honeycomb have it.
Sent from my iPhone using Tapatalk
MeowDude said:
Thanks for the feedback, my heart is indeed set on back porting honeycomb, I'll try later and see how it works out. I'm gonna have to research the recent stage fright bug (haven't heard of it). I figured I could just build android 3.2 from AOSP, set up the necessary drivers, and flash it. Even if that's not an option, I'll just try to build Stock ICS. I just like the older holo UI, and ICS and especially Honeycomb have it.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
If the holo UI is all you're interested in, you can use any recent ROM and this Xposed mod called Holo Themer that forces all apps that it can to fall back to the holo UI interface. Also, if you're running KitKat or below (CM11), you can use TabletKat, another Xposed mod to bring back the legacy tablet UI from Honeycomb/ICS.
Sent from my Amazon Jem using XDA Labs
monster1612 said:
If the holo UI is all you're interested in, you can use any recent ROM and this Xposed mod called Holo Themer that forces all apps that it can to fall back to the holo UI interface. Also, if you're running KitKat or below (CM11), you can use TabletKat, another Xposed mod to bring back the legacy tablet UI from Honeycomb/ICS.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
Sounds good, I'll check it out. On a side note, do you think it would be possible, after modifying the system UI, and all the system apps (framework.res,etc.,etc.) one could turn the stock Amazon OS into stock AOSP-like ICS? Just wondering, because it seems like every custom rom I find has some big I just can't stand (aside from the other ones) either it's too slow, no he youtube, the lock screen doesn't rotate, etc. while I've never had any problem with stock Amazon OS. (Other then that the may bar placement/UI/keyboard suck, but that's easily fixable).
Sent from my iPhone using Tapatalk
MeowDude said:
Sounds good, I'll check it out. On a side note, do you think it would be possible, after modifying the system UI, and all the system apps (framework.res,etc.,etc.) one could turn the stock Amazon OS into stock AOSP-like ICS? Just wondering, because it seems like every custom rom I find has some big I just can't stand (aside from the other ones) either it's too slow, no he youtube, the lock screen doesn't rotate, etc. while I've never had any problem with stock Amazon OS. (Other then that the may bar placement/UI/keyboard suck, but that's easily fixable).
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
It could be possible, but considering all the significant modifications Amazon made to the OS, it would most likely be a long, complex process. There may be xposed mods available to try to tweak the stock UI, and you could try to replace all the stock apps in the stock ROM with their AOSP counterparts, but there's always the risk of bootlooping the OS if you make modifications it doesn't agree with. I think you'd be better off using CM11 or a prebuilt custom ROM instead of trying to reverse engineer Amazon's source to reconcile it with AOSP.
Sent from my Amazon Jem using XDA Labs
I'm gonna try to work on that, there's no way I'm the only one who's thought to want the stock UI---interesting thing I found in the systemUI.apk, I found all the stock AOSP icons in SystemUI.zip/res/drawablehdpi even the tablet UI icons, which really through me off. Also, almost all the Amazon OS icons were in SystemUI.zip/res/drawable-- my idea, do some crazy xml/png editing, and get the stock UI I'm looking for. Your thoughts?
Sent from my iPhone using Tapatalk
monster1612 said:
...There may be xposed mods available to try to tweak the stock UI...
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
Do have a list of these modules? I've set up xposed framework on mine, but I'm having trouble finding modules meant for kindles, and I don't want to be constantly playing the "trial and wait 10min to restore my compressed TWRP backup" game.
Sent from my iPhone using Tapatalk
monster1612 said:
...There may be xposed mods available to try to tweak the stock UI...
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
Do have a list of these modules? I've set up xposed framework on mine, but I'm having trouble finding modules meant for kindles, and I don't want to be constantly playing the "trial and wait 10min to restore my compressed TWRP backup" game.
Sent from my iPhone using Tapatalk
I just figured out why it wasn't letting me send that last post...
Sent from my iPhone using Tapatalk
MeowDude said:
...almost all the Amazon OS icons were in SystemUI.zip/res/drawable-- my idea, do some crazy xml/png editing, and get the stock UI I'm looking for. Your thoughts?
Click to expand...
Click to collapse
You could do that, but I think it'd be easier to copy/paste icons from an AOSP/CM9 ROM. (CM9 is the corresponding version for AOSP 4.0.3, which is still ICS.)
MeowDude said:
Do have a list of these modules? I've set up xposed framework on mine, but I'm having trouble finding modules meant for kindles, and I don't want to be constantly playing the "trial and wait 10min to restore my compressed TWRP backup" game.
Click to expand...
Click to collapse
I haven't tried out the xposed framework on Amazon's stock OS, so I think you'll have to play with trial and error. However, you won't need to mess around with restoring TWRP backups - all you need to do to disable the framework is simply run touch disabled from the TWRP terminal in the /data/data/de.robv.android.xposed.installer/conf/ folder. Then reboot, uncheck the problematic mod in the Xposed Installer, delete that disabled file, and reboot to re-enable the framework.
Some people are still arguing about this purely from anecdotal experiences.
That's a very good question and now I want to find this out as well... I've installed Gsam Battery Monitor, Greenify, Servicely and Naptime.
I'm on Xiaomi.eu Custom ROM (Stable). I used to have better battery life (especially on Standby!) when I was still on an AOSP-based Custom ROM (ArrowOS). I have a feeling that the MIUI Always-On-Display causes Android Doze to not activate and that my device is essentially awake the whole time. I'm not sure about this observation, but Settings > Battery > Sort by "Details" tells me that my device is on. The whole time...
I've unrestricted the Battery monitoring apps I've installed, I'll leave AOD enabled, and see for another night if it is actually preventing my phone from going into Doze Sleep. Next night I'll disable AOD, and the night after that I'll enable Extreme Doze-Mode in Naptime and see the behaviour then.
Rant about Xiaomi LOL:
One thing I know for sure is that MIUI is so horribly coded. I don't need to be an OS developer to know this, you can just feel how dirty their custom implementations are. Ranging from their AOD, their Navbar/Gesture Controls, to the Adaptive Refresh rate.
It's like Xiaomi is trying to make the software deliberately feel cheap, because otherwise their phones would be too good, because their hardware is really good for the price. You can't just make a Poco F3 300€. The hardware is insanely good, but the Stock ROM is crap.
cyanGalaxy said:
I've installed Gsam Battery Monitor, Greenify, Servicely and Naptime.
Click to expand...
Click to collapse
I have stop using Greenify (it has not updated for 2 years) and lately have also replaced Naptime and Gsam/AccuBattery for BatteryGuru which combined both the main features (battery monitoring and aggressive Doze function).
I'm on ArrowOS 12.1 now, it seems Android11 gave me the best battery life, A12 was horrible and A12L is bearable.
I think it's time I stop worrying about battery and just replace the damn thing every 3 years lol.
mocmocmoc said:
I have stop using Greenify (it has not updated for 2 years) and lately have also replaced Naptime and Gsam/AccuBattery for BatteryGuru which combined both the main features (battery monitoring and aggressive Doze function).
I'm on ArrowOS 12.1 now, it seems Android11 gave me the best battery life, A12 was horrible and A12L is bearable.
I think it's time I stop worrying about battery and just replace the damn thing every 3 years lol.
Click to expand...
Click to collapse
I don't think Battery Life is related to the Android Version you're using, but more which brand's ROM you use. For example Samsungs OneUI seems more trustable than MIUI in terms of Reliability.
But you're likely best served on Clean Vanilla Android, in terms of Battery Life at least.
But also make sure to use a trusted and genuine AOSP ROM. Not one of those, where the Main Dev can't write proper English and uses some obscure Custom Kernel or whatever.. Use one that's known and popular.
I did figure out that MIUI's Always-On-Display kept the CPU awake at all times. I could see it in Settings > Battery, and changing "Ranking" to "Details".
I don't know if that's normal for AOD or if it's MIUI's implementation of AOD, but my god.. AOD shouldn't drain that much. But now my battery life is normal again. ^^
cyanGalaxy said:
I don't think Battery Life is related to the Android Version you're using, but more which brand's ROM you use. For example Samsungs OneUI seems more trustable than MIUI in terms of Reliability.
But you're likely best served on Clean Vanilla Android, in terms of Battery Life at least.
But also make sure to use a trusted and genuine AOSP ROM. Not one of those, where the Main Dev can't write proper English and uses some obscure Custom Kernel or whatever.. Use one that's known and popular.
I did figure out that MIUI's Always-On-Display kept the CPU awake at all times. I could see it in Settings > Battery, and changing "Ranking" to "Details".
I don't know if that's normal for AOD or if it's MIUI's implementation of AOD, but my god.. AOD shouldn't drain that much. But now my battery life is normal again. ^^
Click to expand...
Click to collapse
For all practical purposes, the best/definitive experience of Android is obtained on a Samsung device nowadays. So much so that Google released certain new features in some of their apps on Samsung devices ONLY to begin with, not even their own Pixel devices. And Pixel software experience is terrible. And Samsung has innovated so many new features that Google slowly incorporates into stock Android. Samsung Dex is still unparalleled. I personally don't like some aspects of Samsung UI. The squircle icons, the excessively round UI elements with large paddings.. Sadly, Google seems to have incorporated some of this into Android 12's Material You styling. Android 12 looks more like a Samsung One UI skin. That was my FIRST impression when I played around with Material You, i.e. how much it reminded me of Samsung's style.
I agree that Xiaomi's MIUI has a load of flaws in them. The latest is their custom per-app dark mode override has been broken since they released MIUI 13 and before that you had to do some funky things to make it show the list of apps. They never allowed us to see notification history for some strange reason. These are two issues I can think off right away. But otherwise I feel that the software is pretty decent and I had no major issues with it and the battery life with Stock ROM is quite good. I personally don't understand the vehement negativity towards MIUI. Perhaps in the past it was attrocious, but now it is decent. Just like Samsung's One UI. Remember the awful TouchWiz days!? I still have an old tablet with Samsung's touch wiz on it! Bottom line, MIUI is nothing exemplary, but definitely usable and fine, with some minor issues.
In fact, I do like some of the things in MIUI versus stock. I like the fact that the Settings button is immediately visible in the notification shade (like it USED to be on Stock Android) rather than having to swipe again to reveal the quick toggles. I do like some of their built in apps, like the Clock, Calculator (which is very feature rich) and Compass app. So, overall not too shaby.
But I ranted a lot in this thread and none of this is relevant for this topic! So back to relevance...
I do use GSam battery monitor and after a lot of usage I feel like my battery life on Stock MIUI is similar to Arrow OS. I used Arrow OS 11, I used MIUI 12 and 13 and the battery life on all of them was very similar. Arrow OS 11 had some weird bugs with incoming phone call sound and Bluetooth when using Navigation. But Stock MIUI has no such issues. I've slowly decided to stop paying close attention to battery life as it is mostly very good for my usage.
litetaker said:
For all practical purposes, the best/definitive experience of Android is obtained on a Samsung device nowadays. So much so that Google released certain new features in some of their apps on Samsung devices ONLY to begin with, not even their own Pixel devices. And Pixel software experience is terrible. And Samsung has innovated so many new features that Google slowly incorporates into stock Android. Samsung Dex is still unparalleled. I personally don't like some aspects of Samsung UI. The squircle icons, the excessively round UI elements with large paddings.. Sadly, Google seems to have incorporated some of this into Android 12's Material You styling. Android 12 looks more like a Samsung One UI skin. That was my FIRST impression when I played around with Material You, i.e. how much it reminded me of Samsung's style.
...
Click to expand...
Click to collapse
For me the hate for MIUI stems from all the little things.
Notification History & Log being hidden (Can be accessed through an Activity Launcher),
Holding a notification and clicking "More" doesn't bring to you to the specific notification channel,
No Gestures on 3rd Party Launchers,
Recents-Animations broken on 3rd Party Launchers,
Dolby Atmos Sound effect doesn't apply to the first volume step.
Touch Sounds are way too loud, regardless of users volume,
For Google Clock to work properly, you need to disable MIUI Battery Saver,
MIUI Boot Sound is way too loud, also regardless of users volume,
Annoying additional restrictions/permission-manager which cannot be turned off anymore,
Fullscreen Pop-Up with user-unfriendly 10 second timer when trying to change sensitive permissions,
Adaptive Refresh Rate only activating when Screen-brightness is >80%, and only after 2 second delay,
YouTube, Games etc are forced to 60 Hz,
MIUI Camera doesn't respect Default-Gallery setting and always uses MIUI Gallery,
Default Camera cannot be changed,
Monet Colours cannot be customised,
Almost all apps used to get forcibly themed dark (even when the app already had Dark Mode), and you had to individually disable it for all apps. This made text from some apps unreadable.
I do like a few changes Xiaomi has done to Android with MIUI, like bringing back down the Brightness-bar (retarded change from Google), Custom Fonts, the really cool Live Wallpapers, its Dolby Atmos and much more...
I also do like many of their apps like Mi Fitness and the Calc...
But all the little issues give me micro-aggression. It's not a 100% reliable OS in my opinion and I'm still a tiny bit concerned about its Privacy & Tracking.. it's still a chinese company and China is ruled by CCP. The chinese Gov't can control their Tech companies.
Samsungs OneUI does indeed seem like a good and stable experience. But I'm also not a fan of goofy rounded corners and padding.
I bought my Galaxy Note 8 when TouchWiz was still a thing. Then a System update came and upgraded me to OneUI 1.0 and I kinda didn't like it all that much. TouchWiz looked a bit more professional to me, but that's just personal preference.
I'm more into Edgy than Curvy ;D
Yes, Naptime still makes quite a difference with its agressive dove settings and disabling sensors.
Even with how optimized Android 12 is you cannot escape bad programmed third party apps, so use something like IceBox to freeze not often used apps too
cyanGalaxy said:
For me the hate for MIUI stems from all the little things.
Notification History & Log being hidden (Can be accessed through an Activity Launcher),
Holding a notification and clicking "More" doesn't bring to you to the specific notification channel,
No Gestures on 3rd Party Launchers,
Recents-Animations broken on 3rd Party Launchers,
Dolby Atmos Sound effect doesn't apply to the first volume step.
Touch Sounds are way too loud, regardless of users volume,
For Google Clock to work properly, you need to disable MIUI Battery Saver,
MIUI Boot Sound is way too loud, also regardless of users volume,
Annoying additional restrictions/permission-manager which cannot be turned off anymore,
Fullscreen Pop-Up with user-unfriendly 10 second timer when trying to change sensitive permissions,
Adaptive Refresh Rate only activating when Screen-brightness is >80%, and only after 2 second delay,
YouTube, Games etc are forced to 60 Hz,
MIUI Camera doesn't respect Default-Gallery setting and always uses MIUI Gallery,
Default Camera cannot be changed,
Monet Colours cannot be customised,
Almost all apps used to get forcibly themed dark (even when the app already had Dark Mode), and you had to individually disable it for all apps. This made text from some apps unreadable.
I do like a few changes Xiaomi has done to Android with MIUI, like bringing back down the Brightness-bar (retarded change from Google), Custom Fonts, the really cool Live Wallpapers, its Dolby Atmos and much more...
I also do like many of their apps like Mi Fitness and the Calc...
But all the little issues give me micro-aggression. It's not a 100% reliable OS in my opinion and I'm still a tiny bit concerned about its Privacy & Tracking.. it's still a chinese company and China is ruled by CCP. The chinese Gov't can control their Tech companies.
Samsungs OneUI does indeed seem like a good and stable experience. But I'm also not a fan of goofy rounded corners and padding.
I bought my Galaxy Note 8 when TouchWiz was still a thing. Then a System update came and upgraded me to OneUI 1.0 and I kinda didn't like it all that much. TouchWiz looked a bit more professional to me, but that's just personal preference.
I'm more into Edgy than Curvy ;D
Click to expand...
Click to collapse
I guess these can be frustrating issues for some, but none of this is an issue for me. I tend not to get overly worked up by minor software issues. In fact I do not mind the additional 10 second delay for sensitive permissions. For power users it maybe too annoying, but for ordinary users it is useful to show such warnings to help them avoid making big mistakes and messing up their phones or falling for scams. And anyway, it is just an extra 10 seconds delay. I do admit that blocking access to notification history is annoying but I have learned to live with it. Having the per app dark mode option is genuinely useful as it allows me to force dark mode on only some apps that I use that don't have a dark mode built in, rather than forcing it on all apps via Developer tools. Although this is not working anymore on MIUI 13.
litetaker said:
I guess these can be frustrating issues for some, but none of this is an issue for me. I tend not to get overly worked up by minor software issues. In fact I do not mind the additional 10 second delay for sensitive permissions. For power users it maybe too annoying, but for ordinary users it is useful to show such warnings to help them avoid making big mistakes and messing up their phones or falling for scams. And anyway, it is just an extra 10 seconds delay. I do admit that blocking access to notification history is annoying but I have learned to live with it. Having the per app dark mode option is genuinely useful as it allows me to force dark mode on only some apps that I use that don't have a dark mode built in, rather than forcing it on all apps via Developer tools. Although this is not working anymore on MIUI 13.
Click to expand...
Click to collapse
I think the Warning with 10 sec-timer is the most infuriating one. :x
About Notification History, you can download Activity Launcher, search "Notification History" and make a shortcut for that hidden Activity to your Home screen!
That's what I did, because I use Notification Log & Notification History regularly.
However Notification-History on MIUI is a bit broken. You have to enable Light Mode to see the text properly
cyanGalaxy said:
I think the Warning with 10 sec-timer is the most infuriating one. :x
About Notification History, you can download Activity Launcher, search "Notification History" and make a shortcut for that hidden Activity to your Home screen!
That's what I did, because I use Notification Log & Notification History regularly.
However Notification-History on MIUI is a bit broken. You have to enable Light Mode to see the text properly
Click to expand...
Click to collapse
Thanks a lot for the tip on how to get Notification History! That is very useful! It is stupid that Xiaomi blocks us from accessing this useful information natively and we need to use a third party app to expose this activity, but at least now I can see the history and get some info! Sometimes I get a ping on my phone and I am not sure which notification caused it. Now I can get more clarity! Yay!
BrokeBloke1969 said:
Yes, Naptime still makes quite a difference with its agressive dove settings and disabling sensors.
Even with how optimized Android 12 is you cannot escape bad programmed third party apps, so use something like IceBox to freeze not often used apps too
Click to expand...
Click to collapse
We are now 1 year on, and Naptime + Servicely doesn't matter one bit on new devices. I've been running Android 13 for a while now and have never felt the need to install these two apps.
With Android 14 around the corner, app efficiency will be addressed even further by TARE and the introduction of new background APIs.
I'm still using naptime since a9/10. And see no reason to not use it. Induce deep sleep faster.
BTW, anyone noticed that naptime was removed from play store?
lapirado said:
I'm still using naptime since a9/10. And see no reason to not use it. Induce deep sleep faster.
BTW, anyone noticed that naptime was removed from play store?
Click to expand...
Click to collapse
Yup i think Naptime and Servicely do improve my battery life! I can see from the Naptime Doze-logs that my phone goes to Deep Doze faster and the battery life does seem improved.
I just checked, and Naptime seems to be gone from Play Store, tho not Servicely. I think Google are being twats again...
cyanGalaxy said:
Yup i think Naptime and Servicely do improve my battery life! I can see from the Naptime Doze-logs that my phone goes to Deep Doze faster and the battery life does seem improved.
I just checked, and Naptime seems to be gone from Play Store, tho not Servicely. I think Google are being twats again...
Click to expand...
Click to collapse
Hi, I could not run Naptime on Oxygen OS without Root. Did you find a solution? It worked fine on OOS11.
skyNET said:
Hi, I could not run Naptime on Oxygen OS without Root. Did you find a solution? It worked fine on OOS11.
Click to expand...
Click to collapse
Does the app not start for you? You don't need Root, you can grant the permissions via ADB.
cyanGalaxy said:
Does the app not start for you? You don't need Root, you can grant the permissions via ADB.
Click to expand...
Click to collapse
First of all thanks for your answer.
Yes, of course, it doesn't start properly, it shuts down quickly. I gave permissions with adb in OOS11 and it was doing its job really well (Naptime). But after I upgraded to OOS 12, I saw that the following command string "adb -d shell pm grant..." did not work and gave an error. I can't get around this problem, have you tried it? Naptime is a really successful app and OOS needs it.
skyNET said:
First of all thanks for your answer.
Yes, of course, it doesn't start properly, it shuts down quickly. I gave permissions with adb in OOS11 and it was doing its job really well (Naptime). But after I upgraded to OOS 12, I saw that the following command string "adb -d shell pm grant..." did not work and gave an error. I can't get around this problem, have you tried it? Naptime is a really successful app and OOS needs it.
Click to expand...
Click to collapse
What error?
Enable USB debugging, connect your phone to PC, get the Google SDK Platform Tools, open the folder in Terminal, and type the commands exactly as written.
If you are on MIUI, you also have to enable "USB Debugging (Secure Settings)"
cyanGalaxy said:
What error?
Enable USB debugging, connect your phone to PC, get the Google SDK Platform Tools, open the folder in Terminal, and type the commands exactly as written.
If you are on MIUI, you also have to enable "USB Debugging (Secure Settings)"
Click to expand...
Click to collapse
Let me show you the simplest with BBS!
skyNET said:
Let me show you the simplest with BBS!
Click to expand...
Click to collapse
Try "adb shell" -> "pm grant ..........."
cyanGalaxy said:
Try "adb shell" -> "pm grant ..........."
Click to expand...
Click to collapse
Like this?
I'm currently on the summer 2021 release of the Verizon stock rom based on Android 11 and ONE UI 3.1, but have been hearing about newer versions based on Android 12. I'm fairly happy with the performance of the existing combination, (the speed and battery life are nothing short of epic) but have never found a solution for the longstanding bug where audio playback inside of Shazam is choppy.
My question to the community is if newer builds of the stock rom fix the choppy Shazam audio playback, and also, whether or not they break the Wichita version of the Google Camera app, which I rely on extensively (unless there's a less-broken distribution that I haven't heard about yet, in which case, lay it on me!).
Well, I finally bit the bullet and chomped down all the dirty/in-place updates for both the stock rom based on Android 11 and Android 12. After I inserted a T-Mobile-branded sim card, it set off a whirlwind of changes, including switching the stock rom from the Verizon rom to the T-Moible one all by itself somehow. Lots of nasty packages to disable, but it calms down well enough after doing so. Among other things, the T-Mobile stock rom is extremely aggressive about software updates. I let it push me around this time, but after getting through the batch, I did disable the obnoxious & pushy updater.
I can confirm that choppy Shazam audio was fixed by one of those (can't remember which one) and that the Google Camera app still works in the new rom, so that's a win. The sidecar widgets are degraded, and the little animation that appears when power is connected looks kind of weird, but everything else is alright, except for the horrible widget shaping on the newer stock Samsung launcher. Also, the friendlier band switching menu is stripped out, requiring use of the dialer code to prompt the more primitive one.
If anyone was on the fence about it, as long as you're okay with those minor caveats, I'd recommend going along for the upgrade.