Related
THIS IS AN UNSUPPORTED EXPERIMENTAL BETA APPLICATION, BUGGY, USE AT YOUR OWN RISK. PLEASE READ THE ENTIRE POST BEFORE USING.
About
SuperPower attempts to save battery power by controlling various power hungry components and features of the device. Its features include managment of the cellular data connection, Wi-Fi, Bluetooth, CPU speed and 2G/3G band. It does all this automagically based on the options you configure.
There are more battery saver apps out there, but none that work the way I want them to. It is however meant to work relatively simply. If you want uber-fine-grained control use one or a combination of the other applications available.
SuperPower also serves as somewhat of an Android port of WMLongLife.
BETA, Development & Testing
This application is in beta stage and far from finished. There will be bugs, and the list of things that still need to added, changed, refactored, streamlineed, etc is long.
Primary testing and development is done on a Galaxy S (unbranded, EU, I9000) device, but I also run tests on a G1 and a Hero. Other users have reported it (mostly) works on the Droid, Milestone, Nexus, Desire, Pulse, EVO.
Android version
SuperPower requires Android 1.6 or newer. Some features require newer versions, and some features have a different code path on different Android versions.
For example, Bluetooth features require Android 2.0, while the download speed tracker (to not disable data while downloading) requires Android 2.2. Features are automatically disabled if they are not available for your Android version.
Main features
Control over
- Cellular data
- Wi-Fi
- WiMAX * Android 2.2+ *
- Bluetooth * Android 2.0+ *
- CPU speed * ROOT *
- Bands (2G/3G) * ROOT *
- GPS * ROOT, PATCH, Android 2.2+ *
- Auto-Sync
- Background data * ROOT, PATCH, Android 2.2+ *
Automatic management of the above based on
- Screen state
- Wi-Fi network connection state
- WiMAX network connection state
- Lock screen visibility state
- Download speed
- Foreground application
- Tethering state
- Sleep mode
- Low battery state
- Charging state
Other
- Schedule data connection to be available at certain times
- Schedule night mode
- Informative toasts in response to user actions
- Status bar notifications about the current state, which you can tap to change
- Provides handy shortcuts you can add to the home screen for easy access of a number of functions
Additional features
- Enable/disable data is non-persistent. APNs are not modified! This is no longer true on Gingerbread (2.3) and newer due to changes in Android security. Here either data is disabled entirely (Settings -> Wireless and network -> Mobile networks -> Use packet data, or APNs are modified (Access Point Names in the same menu).
- 2G/3G switching is supported in two different ways: RIL injection (highly experimental, any ROM, possible side effects) and Sidekick (AOSP ROMs signed with platform test keys, or using patching)
- Completely event based, no polling, ever.
Future features
I have a LOT of them already in my to-do list. However, if you have any ideas feel free to post them. To name a few that are already on my list: configuration wizard, widget, GPS control, mapper, signal-strength based 2G/3G. Of course improvement to current features, fixing bugs, etc are also on my (perpetual?) to-do list.
Screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Conclusion, copyright and download
NOTICE: At this time I may not respond to each and every posts and questions. I do guarantee I will read every post and take what you write under consideration! Please report all your findings.
Copyright: This app is fully my copyright. You may not distribute it without prior explicit consent from me! So no, you're not allowed to include it in your ROMs either
----
Release notes: The changelog (a few posts down) contains links to version-specific release notes, if there are any.
SuperPower can be found on Market under the name "SuperPower XDA-BETA". The QR code below will take you there:
Direct market link: market://details?id=nl.morose.superpower
Appbrain link: http://www.appbrain.com/app/nl.morose.superpower
It is on Market instead of being for download here because Market tracks force closes. This will help me debug
(Original APK downloads <<< 0.60: 705)
FAQ - Frequently Asked Questions
Index
- General
--- Will this prolong battery life ?
--- I want feature X, but it isn't included
--- I expected X to happen, but Y happened
--- I found a bug
- Data connections
--- The connection state changed, but didn't change back when I expected it to
- System popups
--- The PIN screen pops up sometimes
--- The locks screen pops up sometimes
- 2G/3G
--- A band switch is being performed even though I'm already in the mode it is switching to
--- What is the difference between the RIL injection and the Sidekick method ?
--- Even though I have root, the 2G/3G switching options are disabled (CDMA)
--- Band switching takes too long, is this a bug ? Can it be improved ?
--- I'm in 2G mode but my device switched back to 3G
- CPU
--- The device never wakes from sleep
--- Using tool X shows me that CPU speed is never changed
General: Will this prolong battery life ?
Quite probably, yes, significantly! BUT, there is never a guarantee. It all depends on how you use your device, the current conditions, and how you configure SuperPower. Some options in general save a lot of battery, but may be too inconvenient for you to use (specifically 2G/3G switching), and if you still want to use them, some playing with the various options may be needed to get it to work with the least amount of inconvenience to your usage pattern.
If you are a very heavy user, no amount of software is going to help you (much). You need a bigger battery (or a spare). If all you use your device for is streaming YouTube, chances are battery life improvements you will see are little to none.
CPU scaling may have less effect than expected. The amount of battery it saves has differed wildly between tests on different devices.
Using Wi-Fi may use significantly less power than using 2G/3G. Or, 2G/3G may use significantly less power than using Wi-Fi. It depends on the situation, the signal strength of both cellular and Wi-Fi, the transfer speed, etc.
Using 2G instead of 3G will generally speaking use less battery for most users, but this is not a given. It depends on the situation.
All in all however, the default SuperPower configuration will provide you with a setup that will save a lot of battery for the average user, with little to no inconvenience to the user.
General: I want feature X, but it isn't included
Feel free to request the feature in this thread, even if this feature is already listed in these posts that it will be implemented sooner or later. If feature X is posted about 10 times, and feature Y only 3 times, that may have an effect on the priority of implementation.
General: I expected X to happen, but Y happened
Please go through the entire configuration to make sure you haven't configured anything that causes this behaviour Y before posting here. Also read through this FAQ and the known issues. It is of course possible you have found an undocumented bug, if so please report it here (see "I found a bug")
General: I found a bug
If you post it here, perhaps we can do something about it. But first, please check your configuration first to make sure it is unexpected behaviour. When posting about a bug, always include the relevant SuperPower configuration options, exactly which device you are using, which ROM, etc. More information is usually better !
Data connections: The connection state changed, but didn't change back when I expected it to
In the default configuration, SuperPower will "upgrade" connection states as soon as possible, but general only "downgrade" them when you aren't looking.
For example, turning on data will be done as soon as you need it; while turning off data will generally be done only a while after the screen goes off. The same goes for for example 2G/3G. Switching to 3G will happen as soon as possible, switching to 2G will not be done immediately.
This does all depend on your SuperPower configuration, though!
System popups: The PIN screen pops up sometimes
On some devices certain actions can cause the PIN screen to popup when for example bandswitching or coming out of airplane mode.
If you enter your PIN code in the SuperPower configuration and you have such a device, SuperPower will attempt to automatically enter the PIN code for you - IF it understands it was one of SuperPower's actions that caused the PIN popup. An overlay screen will be presented to you while the PIN is entered and the SIM unlocked.
This is however an experimental feature, may not work 100% of the time, and can cause some inconvenience. If you find this highly annoying, but you do want to use the features SuperPower provides that may cause this behaviour, you can disable the PIN screen altogether in the device's settings application.
System popups: The lock screen pops up sometimes
Like the PIN screen, on some devices certain actions can cause the lock screen to popup. SuperPower actively counters this behaviour while it is performing actions. Should it still happen, please report it (and the exact situation that caused it), specific code that prevents this behaviour may need to be added to code in additional places.
2G/3G: A band switch is being performed even though I'm already in the mode it is switching to
It is not always possible to detect the current 2G/3G state. In that case, SuperPower will treat the current mode as undefined, and any trigger that will cause either 2G or 3G mode will result in a band switch being performed, regardless of what the current actual state may be. This is also a reason to not use the device's settings app (or any other app) to switch between 2G/3G when SuperPower is also using 2G/3G functionality. Always use SuperPower (and only SuperPower) to perform the band switch!
2G/3G: What is the difference between the RIL injection and the Sidekick method ?
RIL injection is as hackery as hacks come, and is currently only available for GSM devices. It completely circumvents most of Android and tries to force commands to be sent to the radio.
Sidekick on the other hand will use the same method as the device's settings screen to trigger a band switch, and is therefor both safer and faster to use. It does unfortunately require a compatible ROM. Carrier / manufaturer ROMs are usually not compatible, and not all custom ROMs are compatible either. Sidekick is available both on GSM as well as CDMA devices.
If your ROM is Sidekick compatible, Sidekick will always be used instead of RIL injection.
Both methods have not been extensively tested on a wide range of devices yet. So neither method may be compatible with your device. Please post here if neither method works on your device.
2G/3G: Even though I have root, the 2G/3G switching options are disabled (CDMA)
RIL injection is currently only supported on GSM devices. Only the Sidekick method supports CDMA at the moment.
2G/3G: Band switching takes too long, is this a bug ? Can it be improved ?
Band switching will take time, and inconvenience you. There is no way around this. The phone has to drop the network connection and completely reconnect to the tower.
However, in some cases it does take longer than in other cases. The Sidekick method provides the fastest band switching available, but is not compatible with many ROMs. If your ROM is compatible, though, Sidekick will be installed and used automatically instead of RIL injection.
When the RIL injection method is used (which will probably be for most users), band switching speed depends heavily on the device. Some devices are fairly quick with RIL injections, others are slow. If you have a device that requires your PIN code for operations such as band switching and coming out of airplane mode, band switching will also take significantly longer.
Depending on all these factors, band switching can take anywhere between 10 seconds and a minute. Band switching will usually save a lot of power, but you have to consider wether the extra battery life is worth the inconvenience.
2G/3G: I'm in 2G mode but my device switched back to 3G
Some devices are known to do this. If it happens to you, please post about it. An attempt a viable workaround is on the to-do list.
CPU: The device never wakes from sleep
Not all devices work perfectly with CPU scaling. If this happens, reboot your phone, go into SuperPower configuration, and switch the "ondemand" setting under "Root features". If that doesn't work, you'll just have to disable CPU scaling.
CPU: Using tool X shows me that CPU speed is never changed
The CPU speed cannot be easily changed on all devices. Some devices/firmwares are "perflocked". Disabling perflock is beyond the scope of SuperPower, and thus SuperPower will make no attempt to disable it. There are tools out there that can disable perflock on many devices that have it, for example, check out SetCPU.
Known issues
- IMPORTANT BUG - WARNING In various Android 2.1 (Eclair) builds there is a bug with push email. In case there is no data connection available, the background email service will go absolutely insane. It will use quite some CPU power constantly, and it will not let the device go to sleep - ever! I do not know if this bug existed before 2.1, and I have not seen the issue on 2.2 ROMs. If you are suffering from this, or suspect you are suffering from this, disable all the options in SuperPower to disable the cellular data connection.
- SuperUser: SuperPower does use a lot of root commands if you have root. You might want to configure SuperUser to not show toast notifications for every single request.
- State: Current state detection is not perfect yet and needs some improvements. I would advise trying to limit changing options in the application to times when Wi-Fi is off and you are in 3G mode as much as possible, just to be sure.
- Wi-Fi: Occasionally Wi-Fi and cellular data states will conflict, causing cellular data to be set to active when Wi-Fi is on. Happens sporadically.
- CPU Scaling: On the I9000 and family, you should (in my experience) enable the "ondemand" option if you are using CPU scaling. If you don't, and the device is in "suspend" mode, an incoming phonecall may crash the device.
- CPU Scaling: SuperPower makes no attempt to detect or disable perflock. If you have a perflocked device, you need to use SetCPU (or some other tool) to disable perflock on boot.
- CPU Scaling: SuperPower attempts to detect the possible CPU speed settings, and will choose the nearest value below half the maximum CPU speed as "low speed" frequency. The actual number chosen is stated in the description of the relevant option.
- CPU Scaling: I know some overclocked ROMs require the device to always be at this overclocked speed to prevent the device crashing during sleep. If you are using an overclocked ROM and encounter the "sleep of death", disable CPU Scaling.
- Roaming: SuperPower has not been tested while roaming at all. I suspect - but am by no means sure - there may be issues regarding the cellular data connection while roaming and you have set the device to disallow data entirely (while roaming). Let me know if you encounter any that seem directly related to roaming.
- Application specific: Applicatoin specific settings do not go into effect if the app is reached through the back-button, only if started through the launcher (or by some other app)
- Lock screen: Even if the "dont do ... while lockscreen visible" options are enabled, these actions may still happen if triggered by an application specific options
- 2G/3G: On some devices the device itself will automatically switch back to 3G, it will not stay in 2G for very long
Changelogs
14.03.2011 - v0.80 BETA - Release Notes
- Adjusted reboot code
- Adjusted preference save/load code
- Adjusted Sidekick install code (hopefully for the better)
- New version of Sidekick
- Uses ITelephony data controls on pre-Gingerbread
- Uses secure settings patch, Sidekick, or APN-based data controls on Gingerbread, depending on availability
18.11.2010 - v0.75 BETA - Release Notes
- Adjusted some description in config app
- Adjusted shortcut text for "wake up"
- Added "running" notification. This will make sure that there is always a SuperPower notification in the statusbar while SuperPower is running
- Adjusted when some notifications show or do not show based on other notification states
- Added WiMAX notification + 4G icons
- Added WiMAX shortcuts + 4G icons
- Categorized the shortcut selection screen
- Options the device is not capable of are now disabled in the shortcut selection screen
- Added low battery mode override: charging
- Added low battery mode override: screen on
- Added low battery mode override: lock screen
- Fixed option to disable cellular data when WiMAX is connected to a network
- Added "reboot" permission, may fix issue with patch on some devices
- Adjusted screen-on timeout cancel code
- Added option to delay service start at boot. May solve issues with users running a temp-root-at-boot like VISIONary (warning: not tested)
- Adjusted "application requires data when screen is off" handling
- Added option to kill app on screen off (partially working on 2.2)
- Added option to use "3G-only" mode for 3G to root features
- Fixed an issue with bandswitching (would sometimes detect "complete" before switching started)
- Fixed an issue with bandswitching (would not re-evaluate state after leaving lock state)
- Reworked state and wakelock clearing at screen on / screen off / unlock (fixes lockscreen data/wifi/etc on issue)
- Added option to not disable "other" interfaces (Wi-Fi, WiMAX, etc) while download speed is over X KB/s
- Update on MIUI issue: bug report submitted to MIUI devs. Hopefully they can devise a workaround
- Update on Wi-Fi error: still not properly reproducable. No closer to finding a solution (or the problem, even)
- Update on App Specific options: Still needs an overhaul and a lot of extra options!
04.11.2010 - v0.71 BETA - Release Notes
- Fixed FC on Sidekick install fail OK click
- Fixed checkmark on Sidekick install cancel remaining
- Bluetooth support changed to API level 5 and up (Android 2.0)
- WiMAX suppport changed to API level 8 and up (Android 2.2)
- Airplane bug fixed. Cause: WiMAX functions do not work on pre-2.2, SuperPower switches to airplane mode instead of turning off WiMAX
- Secure settings patch and force sidekick install limited to API level 8 and up (Android 2.2)
- Adjusted patching text for modify secure settings
03.11.2010 - v0.70 BETA - Release Notes
- AdFree workaround (may cause delay during first-time-since-reboot load)
- Updated AdMob SDK
- Fixed bug with AdMob
- Modify secure settings (Patch, ROOT), required for GPS and background data options
- Alternative method for Wi-Fi on/off
- Wi-Fi, Bluetooth, WiMAX, GPS, "turned off by screen off" states now persistent, will survive crashes
- Persistent states cleared on boot
- If service is restarted due to crash, it is now loaded correctly
- Fixed crash when entering app-specific screen
- Modified "changed settings" update in background service, should reduce lag in config app
- Renamed "sleep mode" to "night mode"
- PIN code setting now (correctly) states it requires 2.0 if older version detected
- Implement setting Auto-Sync (Android 2.0+) and Background Data (Patch, ROOT) based on network connectivity
- Added master switch to en/disable application specific options
- Nightmode bluetooth on wake is now disabled if bluetooth not supported
- Added GPS options (Patch, ROOT)
- Adjusted multiple config settings: if no root is detected but is needed, options now have the correct "root required" summary
- Added WiMAX functionality
- Scheduled data wakeup during sleep mode disabled
- Adjusted a number of default settings
- Scheduled data is now performed automatically when coming out of night mode
- Intensely modified handling of Sidekick-based switching to accomodate some devices
- Sidekick switching now disables the data connection before attempting a switch
- Added scheduled wake up time to night mode quick list
- Alternative Sidekick installation path for non-AOSP ROMs with root
28.10.2010 - v0.64 BETA (DEBUG)
- Attempted fix for WiMAX detection force close (Market reported crash)
- Additional logging in startup screen, hopefully help finds the problem for the "blank screen" issue
- Additional logging to test WiMAX features
- Possible fix for app-specific options listed apps that are no longer installed
27.10.2010 - v0.63 BETA
- Adjustment to data off during low battery, no longer turns off when battery low but charging and "do not turn off while charging" is set, when leaving airplane mode
- Adjustment to data off during lock screen, scheduled data and charging states now override this setting
- Adjustment to service keep-alive
- Refactored settings screen (50% code reduction)
- New functionality - sleep mode
- New shortcut - sleep mode
- New shortcut - wake up
- New notification - sleep mode + tap to wake up
- New sleep mode launcher + statusbar icon
- New wake up launcher icon
- Implemented set alarm detection code
- Added some code to detect set alarms. This is not available through an API so is trial-and-error. Seems to work on most devices I've tried.
- Added "Do not switch to 3G when Wi-Fi network is connected" option
24.10.2010 - v0.62 BETA
- Attempted fix for CPU functions force close on unknown model (Market reported crash)
- Attempted fix for AsyncCreate.onPostExecute force close (Market reported crash)
- Temporarily disabled AdFree detection, until a workaround can be devised
22.10.2010 - v0.61 BETA
- Left Sidekick in testing mode. Caused it to be unavailable. Fixed.
21.10.2010 - v0.60 BETA
- State detection improvements
- Changed GSM: RILD_AUTO --> RILD_GSM_WCDMA (for Nexus 1, works according to Jug6ernaut)
- Changed CDMA: RILD_AUTO --> RILD_CDMA_EVDO (for Droid, works according to Captainkrtek)
- Added download speed check option, before turning off data or switching to 2G. API Level >= 8
- Modifications to detecting application start, no longer requires root + bug fix
- Click app title opens thread on XDA-Developers
- Re-arranged user interface into sections
- Ad-supported version no longer runs when AdFree is installed
- Created APK that disables ads (for donator version)
- Removed a LOT of SU calls
- Data schedule aborts when airplane mode detected
- Bandswitch aborts when airplane mode detected
- Last wanted data-state / band-state applied when coming out of airplane mode
- Post-wakelock-release vibration now optional (debug section)
- Added per-app selection of 3G / data during sleep (new) options
- Adjusted some item titles and summaries
- Many speed and load improvements across several functions
- If PIN code is entered in configuration, SuperPower will show a screen and unlock the device during certain operations, if needed. API Level >= 5
- Added option to switch to 3G when tethering
- Bluetooth options added. API Level >= 5
- Screen off states no longer set when screen goes off due to phonecall+proximity sensor
- Added low battery mode
- New shortcut - override low battery mode
- New shortcut - cancel override low battery mode
- New notification - low battery mode + tap to override
- New notification - low battery mode overriden + tap to re-enable
- New notification - 2g mode + tap to switch to 3g
- New notification - 3g mode + tap to switch to 2g
- New notification - nag
- New generic statusbar icon
- New 2G launcher icon + statusbar icon
- New 3G launcher icon + statusbar icon
- New low battery launcher + statusbar icon
- New low battery override launcher + statusbar icon
- Application specific settings: re-arranged order, configured at top
- Added lock screen options, to specify wether or not actions may be performed during screen on or only after unlock
- Improved detection that band switch is complete
- New known issue: applicatoin specific settings do not go into effect if the app is reached through the back-button, only if started through the launcher
- New known issue: even if the "dont do ... while lockscreen visible" options are enabled, these actions may still happen if triggered by an application specific options
14.10.2010 - v0.51 BETA
- Settings activity: modified descriptions of "root features" to show why they are disabled, if they are disabled
- CreateShortcut activity: ads added
- Settings & CreateShortcut activities: automatic shutdown, prevents popping up the main screen when clicking a shortcut
- Portrait lock (prevents lengthy re-loading at rotate)
- Added screen state detection for API Level >= 5 (reflection)
- CPU scaling: detect if ondemand or conservative is available, and set it if current governor is something else. Should support more devices.
- CPU scaling: fixed a number of possible FC's by adding missing NullPointer checks
- Service load is now multithreaded (prevents ANRs)
14.10.2010 - v0.50 BETA - Initial release
Tested on the Moto Droid running CM6, works well tested some features
Thank you. Will also test your application.
Interesting for me is the function, turning of data connection when wifi is active because this month, I've only gprs speed.
My Galaxy S downloaded Asphalt through the Data Connection although wifi was available...and I did this 2 times -_-
One "error", maybe missconfigured: If the screen is off, and I turn it back on I've no network.
Even the network from my provider was not active. So there is no phone connection nor receiving sms possible.
When I turn the screen back on, it rapidly connects to my provider.
Maybe you can give me a hint what I missconfigured
great app, it is working very well for me. Turns off data connection when screen is off and turns on every 15 minutes for 2 minutes to allow autosync. Exactly what I need for power saving since with 2g only and no active auto-sync I am saving a LOT of power.
Works Excellently
Nice App on 2.2 JPM THX mate
will test it and report back to you
for now; THANKS
Madic said:
Thank you. Will also test your application.
Interesting for me is the function, turning of data connection when wifi is active because this month, I've only gprs speed.
My Galaxy S downloaded Asphalt through the Data Connection although wifi was available...and I did this 2 times -_-
One "error", maybe missconfigured: If the screen is off, and I turn it back on I've no network.
Even the network from my provider was not active. So there is no phone connection nor receiving sms possible.
When I turn the screen back on, it rapidly connects to my provider.
Maybe you can give me a hint what I missconfigured
Click to expand...
Click to collapse
When you mean the network is not "active", do you have a "white circle with a line through it" icon ?
Do you have 2G/3G switching enabled ? The above is exactly what would happen if:
- You have enabled switch to 2G when screen goes off, and you turn on the device while the device is switching to 2G
- You have enabled switch to 3G when screen goes on
In both cases it is a temporary situation that takes about 10 seconds to resolve. Unfortunately switching between 2G and 3G takes time.
Thanks Chainfire. I will try this app and I’ll let you know if I find any bug or I got any suggest.
I really like the option to disable data when the screen is turned off, it’s very good for those who sometimes forget to deactivate 3G when. The only bad pint that I can see to this particular feature is that I could stop downloads of big files unless you have the screen always turned on. By the way I still really like that feature.
titooo7 said:
Thanks Chainfire. I will try this app and I’ll let you know if I find any bug or I got any suggest.
I really like the option to disable data when the screen is turned off, it’s very good for those who sometimes forget to deactivate 3G when. The only bad pint that I can see to this particular feature is that I could stop downloads of big files unless you have the screen always turned on. By the way I still really like that feature.
Click to expand...
Click to collapse
Something is planned for this problem
mrruin said:
great app, it is working very well for me. Turns off data connection when screen is off and turns on every 15 minutes for 2 minutes to allow autosync. Exactly what I need for power saving since with 2g only and no active auto-sync I am saving a LOT of power.
Click to expand...
Click to collapse
Where can I set that data turns on every 15minutes?
Thanks
Chainfire said:
Something is planned for this problem
Click to expand...
Click to collapse
I guess you have something planned like a watchdog to see if there is any data transfer before stopping the connection. If thats the case I think it might be not so easy as some apps could be connected to the internet with very small data transfer. However, you are the expert on this.
I just tested in my SSGS with froyo 2.2 (JPM). I'm just using default options (disconnect data when the screen is turned off) and I have realised that when the data gets disconnected the phone makes a small vibration. It would be cool if we can avoid the vibration as it also spends some battery
Birba said:
Where can I set that data turns on every 15minutes?
Thanks
Click to expand...
Click to collapse
Under "Schedule data connection" section in SuperPower
titooo7 said:
I guess you have something planned like a watchdog to see if there is any data transfer before stopping the connection. If thats the case I think it might be not so easy as some apps could be connected to the internet with very small data transfer. However, you are the expert on this.
Click to expand...
Click to collapse
Likely it will be related to the download speed itself, not sure yet though.
I just tested in my SSGS with froyo 2.2 (JPM). I'm just using default options (disconnect data when the screen is turned off) and I have realised that when the data gets disconnected the phone makes a small vibration. It would be cool if we can avoid the vibration as it also spends some battery
Click to expand...
Click to collapse
As stated in the first post the vibration is a debug option. It will be removed / turned off in a later version. Remember this is beta
Chainfire said:
When you mean the network is not "active", do you have a "white circle with a line through it" icon ?
Do you have 2G/3G switching enabled ? The above is exactly what would happen if:
- You have enabled switch to 2G when screen goes off, and you turn on the device while the device is switching to 2G
- You have enabled switch to 3G when screen goes on
In both cases it is a temporary situation that takes about 10 seconds to resolve. Unfortunately switching between 2G and 3G takes time.
Click to expand...
Click to collapse
I activated both options.
Ok, if this is intended behaviour and just happens if I switch the screen back on, than it's fine.
Thank you
Madic said:
I activated both options.
Ok, if this is intended behaviour and just happens if I switch the screen back on, than it's fine.
Thank you
Click to expand...
Click to collapse
Note that if you turn off the "Automatic switch to 3G" option, SuperPower will switch to 3G when you start any of the programs selected in the "Applications requiring 3G" instead of every time you turn on your screen.
Wow this is great! I'll download and try when I upgrade to JPM this weekend! Nice to see a great Dev working on the SGS!
Nice app mate thanks, look forward to more development. And damn you have TONS of phones, mind giving us a HD2? haha.
Bug Report!
Bug Report!
Force closed on I9000M on when switching back from another app back to SP
reloaded SP and it went in properly
I9000M became unresponsive after enabling 2G/3G option
Force closed again...
still hung, can't do much with SP, need to uninstall to return SGS back to normal
no option to uninstall, it does not appear on Titanium backup or any apk manager
I've recently got Xperia J and flashed it with FXP 206 and then moved to FXP 207.
I love it, but i've encountered some bugs that are said to be "officially fixed" or there are no mentions abut them at all.
1. In Settings->More...->Mobile Networks->Network Operators should be list of available network operators. Unfortunately there are some lines, but each of them is labeled as "Unknown". On lock screen, operator name is displayed correctly.
2. While Charging, notification led displays battery state correctly (red while low, yellow, and green when full), but any notification (missed call, application notification, low battery) makes LED pulse pink/violet (blue+red, red slightly shorter, you can observe color go blue at the end of each pulse). You cannot modify that behavior in display settings (pulse length nor color can be successfully set).
3. Offline charging, "Fixed since FXP 204", does not work.
4. Camera (Gallery) Force Closes after recording a video. Starts working after deleting video (problem with creating thumbnail for camera? Camera shows thumbnail of previous picture just before FC)- Known problem. Is there any fix? Camera MX crashes right after clicking "camera" icon.
5. Phone eats through battery really fast. 1,5 day with phone lying on my desk, 2 SMS messages received, no WiFi, 2G mobile network with high signal level. Battery stats show surfaceflinger (Android System) to consume 40% of energy.
6. Music stutters. I know, it is known problem, but maybe someone has some solution. (I have used ROM provided by adfad666, music was crystal clear, but lock screen was lagging - sometimes for more than 30 seconds - and receiving phonecall made the interface freeze, ringtone to stutter, and after that device rebooted. Every time i tried).
7. Less serious bug: sometimes after turning GPS on and starting some app which uses it (any app, ranging from Sygic Navigator to Google Maps or GPS Essentials), the GPS icon does not show up, and only network location is used. After reboot everything works fine (same place, so not a problem with GPS signal level).
Any helpful hints about problems mentioned here?
Hello XDA, I've recently purchased an Android 9 device and like so many others, I've found the new Android 9.0 Intelligent Adaptive Brightness to be a massive headache when it's turned Off and manually adjusted below [50%] brightness.
I have tried for Literally months to track down the cause of this issue on so many various handsets and CPU manufacturing companies.
To begin with, it seemed like this was not a Device Dependent problem, but a problem with Android 9's Changes into Artificial Intelligence for Brightness Control - Mostly because it was a problem being found across-the-board..
How could it be a device problem and not a Firmware problem ?
It seemed very convincing that the cause was Android 9 because people have multiple reports online of this happening after updating the firmware, but not previously happening on any Prior Firmware.
After a while, I remembered having this problem Years Ago, When Android Devices did not have a Hardware Light Sensor - "Luckily I remembered what the cause was back then, it was called Content Aware Backlight"
The idea was that the Phone or Tablet doesn't need a Light Sensor, it can adjust the screen based on Content.
However, this feature provided to be More Problematic than Useful in Android 2.3 days, so they Removed the feature in Further builds up to Android 8.1
After Android 8.1 these features have enabled again to target Battery Consumption.
The Adaptive Brightness features are enabled permanently to enhance the Adaptive Battery AI.
Remember that these are not Simple A.i ... These are Advanced Neural Networks.
So enough with the background, here's the Juice.
Let's look at a Qualcomm CPU Device,
• Qualcomm
A Qualcomm Android uses a brightness feature called CABL "Content Aware Backlight", this feature is Fighting with Android 9's Adaptive Brightness feature and causes a Flickering Effect for the lack of a better word.
What About Others like MTK & Intel ?
• Intel
An intel device also has a built-in feature that fights with Androids Adaptive Brightness, called "Intelligent Backlight Control"
• MediaTek
MediaTek CPU's also have a feature called AAL "Advanced Adaptive Lighting"
To disable these features, is to make your Firmware Android 9.0 Compatible.
DISABLING GUIDES AND TIPS,
UNKNOWN DEVICE GUIDE,
Hi, I bought this phone six months ago and until today I struggled with the adaptive brightness. Even in dark rooms I had very high brightness if I set to adaptive brightness.
Click to expand...
Click to collapse
Today I found out how to solve. I had to edit a file located in /persist/sensors/registry/registry. If you have root access you have to edit the file tcs3701_platform.als.fac_cal so that it looks like that:
Code:
{"tcs3701_platform.als.fac_cal":{"owner":"sns_tcs3 701","scale":{"type":"flt","ver":"1","data":"0.905 537"},"bias":{"type":"flt","ver":"0","data":"0.000 000"}}}
If you aren't able to acces that file you can go to TWRP, copy it to internal storage, modify it with a text editor, go back to recovery and restore the file.
Before touching anything a persist partition backup is highly recommended.
GENERIC DEVICE DISABLE,
You've certainly noticed that when you're outside the screen brightness goes at max level and contrast is over saturated.
It comes from adaptive display, personally I don't like that so I've found a way to disable it in build.prop
Open build.prop and edit this:
Code:
ro.vendor.display.ad=1
Change value to 0, save and reboot
NO ROOT ?
People have reported that Disabling or Clearing Data for "Device Health Services" in Settings > Apps helps significantly... however I did not have improvements myself.
QUALCOMM
Seems that this service controls black vibrance and overall screen sharpness. In lg g2 forum i ve read that this is the dynamic screen contrast. I ve added those line in my build prop, changed everything to 0, but i cant notice any difference.
Code:
ro.qualcomm.cabl=1
hw.cabl.level=Auto
persist.qcom.cabl.video_only=1
If disabling this in Build.prop doesn't work, or you would like to try disable without ROOT ACCESS ..
• Open Settings
• Open Apps
• Open Content Aware Backlight App
• Select DISABLE to disable the Application
ROOT ?
• Try a removal of the APK File that handles Content Aware Backlight in Either System/App or System/Priv-App
More for G2 - https://forum.xda-developers.com/showthread.php?t=2466268
MEDIATEK CPU & AAL
I have tried multiple AAL Disabling methods in Build.prop and nothing works.
The only Sure-fire way to Remove or Disable it is by Removing the AAL Binary File
Code:
system/system/bin/aal
on my device, system is actually a subdirectory of system - so I write system/system/ as an example. Your device may use
system/bin/aal
And disable using build.prop Props,
Code:
ro.vendor.mtk_aal_support=0
persist.vendor.sys.mtk_app_aal_support=0
I'm still looking for Samsung and Speadtrum Props.
Please remember that this is a common issue found on everything... Personal Computers, Smartphones and T.V's.
I've found reports online for both Intel's Intelligent Backlight in products like T.V's, Laptops, Desktops, Smartphones.
The same goes for CABC, CABC is the most notorious for both Android and PC User's, Dominating the Google Search Results for Adaptive Brightness Issues.
CABC or Content Aware Brightness Control, is an absolutely disgusting design that they should have fired someone over a long time ago... The feature has reported up to 15% battery consumption improvement, however user's have reported up to 100% of headaches from viewing the screen are attributed to uncontrollable brightness and flickering - especially while gaming.
A PC Guys Write-up,
http://www.anandtech.com/show/8983/dell-xps-13-review/5
Hello,
Recently i upgraded my OnePlus 7 to OxygenOS 11 via OTA, and here is a list of a few annoying bugs(features?) that you'll need to know before upgrading:
(Note: I performed hard reset after upgrading, so any bugs here will be persistent and not because of some fixable issues, unless you are rooted/want to use adb maybe?)
(Also, this is the stock OOS 11, not rooted, and no modifications)
1) I'm not sure if it's just me, but the device heats up much faster. Though the temperatures here are high, I tried to maintain as close to a lab condition as possible, maintaining 30C ambient temp. Evaluation was done with a session of Call of Duty Mobile, and Youtube 4K video loopback test. Avg temps are: CODM : OOS 10: 41C, OOS 11: 45C, Youtube: OOS 10: 37C, OOS 11: 38C
2) Performance hit in games and frame drops (CODM, outside the ambient temperature maintained conditions), could be due to overheating? (As i mentioned, ambient temps are a bit high here). Also SystemUI lags sometimes. Adding to that, trying to bring up notification panel while playing a demanding game (like codm), the SystemUI (notification panel) opening animation is really choppy. (Is there some graphic driver issue?)
3) Brightness slider very slow to respond (seriously? Have to wait for 3 sec for the brightness to come up/go down on manually moving the slider)
4) Again, this one could be only me, but the audio seems to be a bit low after the update. All the ringtones and default notification sounds, with the same volume levels feels lower than how it was on OOS 10.
5) Battery drain - Device heat up and performance issues, translate to higher battery drain
6) This may not be a bug, but it's a change that i don't quite like (at least provide options?) : Double tap to wake doesn't give a vibration feedback like how it used to.
7) Everything, including UI and default font size is bigger than what I'm comfortable with (no, changing the font/display size doesn't give the expected results). But there's a workaround: Changing the display dpi from developer options from 384 to 420.
8) I had several app crashes (Instagram, Photos) even after disabling Android System Webview as suggested by some. But this issue seems to have been fixed magically for now.
9) This is a change, but to actually poweroff/reboot, you will need to reach your finger to the top of the screen with the new UI.
10) DC dimming has been removed
11) Weird QC issue-Someone thought any greyed out field in settings is because it's not supported by phone or HEADSET... Even in Private DNS settings.(See screenshot)
12) Natural colour calibration has a weird yellow tint (sRGB profile works fine tho)
13) Lots of missed/delayed notifications. Many times, notifications from apps like Instagram, Telegram doesn't arrive on time, with delays from 2 minutes to never arriving at all. Whatsapp seems to work most of the time. Sometimes, notifications don't make sound (weird), but only flash on the screen (Yes, I've verified all my notification settings, and I've set everything to make sound)
14) Now this might be a personal preference, but I don't quite like the way OxygenOS is trying to mimic OneUI (Huge heading and small contents beneath? Not my taste.) This style is followed in the phone, messaging, contacts, calculator, etcc
15) Quickly switching between recent apps, there's a split second of a black screen that appear before the app UI is displayed (not complaining, but this was not present in oos10, it seamlessly moved from the preview of the app on the recent apps screen to the actual app ui without any flickering, and no, this is not because of dc dimming being off or anything)
16) Google Play Music is still not removed (seriously, why still have it if it can't be used?)
17) FileDash - No longer has the DNS resolver for one.plus address. You will now have to manually type in the address displayed by filedash in your browser. Also, it still uses 2.4GHz and not 5GHz.
Edits: Added more bugs/missing features
Hem981,
I can confirm #7 is an issue on mine as well.
The power menu is an android 11 change not an OOS change.
I upgraded from OOS 10 to OOS 11 no wipe and don't seem to experience the other issues that you are having, except the obvious changes they made to the firmware. Have you tried clearing the dalvik-cache and rebooting? Mine was super buggy before doing this, but then again I just upgraded without wiping.
One issue I've personally noticed is the cell radios were a lot better on OOS 10, and I'm assuming that is the cause of the battery life to be worse.
Another that could be due to doing some debloating is when I take a screenshot and the little preview pops up in the bottom right corner if i click on it the UI will freeze after clicking back. The Nav buttons still work, like you can click on recents and the recent menu appears, back and home work but the screen is frozen otherwise until I force a reboot.
Yeah, I've tried factory reset and then wiping dalvik-cache... The performance was better before i performed the factory reset, i think. Anyway, there are quite a few games/apps where the performance impact is easily visible. Also, the power button thing is an Android change, but i really hoped OnePlus to have done something to make it more easily accessible (OOS is not pure Android). I couldn't find the issue with the cell radio you mentioned (as I've tried in areas in which i already had poor reception, and the performance was what was expected). Anyway, I really hope some of these (at least the performance, battery drain and the brightness slider issue) will be fixed soon over updates.
(For me, the SOT has gone down from 9.5 hours to 7 hours under similar use cases)
Yeah SOT has definitely taken a hit on mine as well, standby time seems the same. I also have noticed that the screen brightness needs to be set higher for the same brightness as OOS 10. The cell radio sometimes seem normal, but most of the time they are about 5-10 dBm higher at my house. I'll probably give a clean flash a try this weekend to see if it clears up.
One more issue found:
Weird red tint on screen auto dimming
The whole display has a weird red tint just before the device is about to lock/turn off screen after the timeout, when the display dims. It is easily noticeable if you have a white screen displayed. It only happens if you have set the brightness slider to anything other than the bare minimum (even a single step above the minimum brightness is able to replicate this issue)
I found something interesting: issue #3, the brightness slider being slow to respond to changes, seems to be fixed by disabling all animations from developer options. Should the window animator duration scale have any effect on the responsiveness/quickness of display brightness adjustment? I think that's stupid.
Also, I am starting to thing we need something like 0.1x duration scale for the animations (all animations on Android, or at least OOS), because honestly, with each new implementation, the animations are being too slow that it degrades the whole experience. 0.5x feels a bit better, but i really think something like 0.4x would match the animation speed of android 10.
You forgot to mention the vibration motor effect which has deteriorated since the update. The device now feels like any other cheap device.
It's kinda weird in my situation, just upgrading from 10.3.8 using an old version of xXx NoLimits to 11.0.0. The phone was super buggy when I first installed, but after rooting, wiping the delvik cache, debloating, removing the xXx module, and time to settle in the only issues I have are the screenshot popup, and the lower cell signal which I'm sure is causing a hit on battery life.
I was going to reinstall this past weekend, but for the time and inconvenience it's not worth the time compared to the minor issues I have.
Edit: Even the screen resolution seems normal now.
Again, don't know if this is an issue for anyone else (and i don't think OnePlus is going to change this): While everything else became bigger on the phone, the buttons/number keypad for typing in the screen lock pin became too small.
Hem981 said:
Hello,
Recently i upgraded my OnePlus 7 to OxygenOS 11 via OTA, and here is a list of a few annoying bugs(features?) that you'll need to know before upgrading:
(Note: I performed hard reset after upgrading, so any bugs here will be persistent and not because of some fixable issues, unless you are rooted/want to use adb maybe?)
(Also, this is the stock OOS 11, not rooted, and no modifications)
1) I'm not sure if it's just me, but the device heats up much faster. Though the temperatures here are high, I tried to maintain as close to a lab condition as possible, maintaining 30C ambient temp. Evaluation was done with a session of Call of Duty Mobile, and Youtube 4K video loopback test. Avg temps are: CODM : OOS 10: 41C, OOS 11: 45C, Youtube: OOS 10: 37C, OOS 11: 38C
2) Performance hit in games and frame drops (CODM, outside the ambient temperature maintained conditions), could be due to overheating? (As i mentioned, ambient temps are a bit high here). Also SystemUI lags sometimes. Adding to that, trying to bring up notification panel while playing a demanding game (like codm), the SystemUI (notification panel) opening animation is really choppy. (Is there some graphic driver issue?)
3) Brightness slider very slow to respond (seriously? Have to wait for 3 sec for the brightness to come up/go down on manually moving the slider)
4) Again, this one could be only me, but the audio seems to be a bit low after the update. All the ringtones and default notification sounds, with the same volume levels feels lower than how it was on OOS 10.
5) Battery drain - Device heat up and performance issues, translate to higher battery drain
6) This may not be a bug, but it's a change that i don't quite like (at least provide options?) : Double tap to wake doesn't give a vibration feedback like how it used to.
7) Everything, including UI and default font size is bigger than what I'm comfortable with (no, changing the font/display size doesn't give the expected results). But there's a workaround: Changing the display dpi from developer options from 384 to 420.
8) I had several app crashes (Instagram, Photos) even after disabling Android System Webview as suggested by some. But this issue seems to have been fixed magically for now.
9) This is a change, but to actually poweroff/reboot, you will need to reach your finger to the top of the screen with the new UI.
10) DC dimming has been removed
11) Weird QC issue-Someone thought any greyed out field in settings is because it's not supported by phone or HEADSET... Even in Private DNS settings.(See screenshot)
12) Natural colour calibration has a weird yellow tint (sRGB profile works fine tho)
13) Lots of missed/delayed notifications. Many times, notifications from apps like Instagram, Telegram doesn't arrive on time, with delays from 2 minutes to never arriving at all. Whatsapp seems to work most of the time. Sometimes, notifications don't make sound (weird), but only flash on the screen (Yes, I've verified all my notification settings, and I've set everything to make sound)
14) Now this might be a personal preference, but I don't quite like the way OxygenOS is trying to mimic OneUI (Huge heading and small contents beneath? Not my taste.) This style is followed in the phone, messaging, contacts, calculator, etcc
15) Quickly switching between recent apps, there's a split second of a black screen that appear before the app UI is displayed (not complaining, but this was not present in oos10, it seamlessly moved from the preview of the app on the recent apps screen to the actual app ui without any flickering, and no, this is not because of dc dimming being off or anything)
16) Google Play Music is still not removed (seriously, why still have it if it can't be used?)
17) FileDash - No longer has the DNS resolver for one.plus address. You will now have to manually type in the address displayed by filedash in your browser. Also, it still uses 2.4GHz and not 5GHz.
Edits: Added more bugs/missing features
Click to expand...
Click to collapse
Hi! Oneplus 7 ownere here.
Try to answer all the points:
1) i don't notice any difference between OOS10 and OOS10 on the heat of the phone
2) I don't know for the gaming performance but i don't play any games...overall, the performance are good, no system lags or freeze BUT I have the same issues with the notification...when i tap a notification, I often have delay, maybe it's just the animation but I remember the same issue on a Oneplus 8t that i tried for 20 days in last November
3) same issue here, very annoying
4) not just you, have same issue
5) battery drain is the same in my case, in standby maybe is less than before
6) me too, but maybe they change this as they planned?
7) yes, same thing. i changed the DPI from developer options too
8) no crashes here
9) this is an Android 11 change from Google, maybe they don't want your device to power off ahahah
10) never had this problem luckily
11) don't know, never tried this
12) i noticed this after reading this point, true on my device too
13) i faced the same issue on the notification sound, the other things works fine
14) me too, if i wanted One UI, i would have bought a Samsung...
15) sometimes happens to me, maybe it's bad ram management?
16) this is ridicolous, why they doesn't remove this app??
17) never tried
I also have an issue on the vibration. Now it's HORRIBLE, i have disabled because it's unusable
So, this is my question: change phone or rollback on android 10?
There's one more addition to the list: Always on display sometimes seems to override the notification lockscreen privacy settings. I have some notifications put as "view private content only when unlocked", but the notification contents are visible just when it arrives on the always on display (though it's content is hidden in the actual lockscreen)
I've reported almost all of these bugs, and hopefully we will see new updates fixing most of these.
Can someone on OOS 10 on OnePlus 7 confirm if the "style preferences" settings in sound settings is greyed out while the output is phone speakers (or no other sound output devices connected)?
New hotfix patch OTA rolling out now...
Here is what's fixed and what's not:
1,2 : Yet to test
3: Not fixed
4:Fixed
5: Yet to test
6: No changes
7: No changes(or not easily noticeable maybe?)
8: Not encountered any "ghost" app crashes yet
9: No change
10: DC Dimming is not back, so no change
11: Not fixed Is it that hard to remove 'headset' text from the UI?
12: Don't know if it's because my eyes adjusted to it, but it seems a bit better now
13: Not yet tested
14: What can I say?
15: Fixed
16: The ghost of Google Play Music still remains
17: Not fixed
Edits: Nothing much is fixed
Performance: Marginal improvements
SoT/Battery: Even worse. Getting almost half the SoT I got on OOS 10 under similar use case and network/tenperature conditions
Ghost app crashes reduced a lot (that might be the only fix) , but is not completely gone (saw that 1 or 2 times)
Haptics is still as bad as before
I'm just worried about this weired bug which has rendered my parallel whatsapp very difficult to use to share media. Any fix for this is highly appreciated - https://forums.oneplus.com/threads/whatsapp-media-problem.1411292/
Thanks and regards
OOS11 - Stable
I have no problems on my device until now (for games I dont know why I do not play)
I noticed, because I have tried both roms(beta4 & stable).Open Beta4 has better "battery management" than stable! Αs strange as it may seem but is a real for me..
Well yes .Battery drain higher than openbeta4
wifi works fine to 5ghz band & generally my device works quite well so far. Patience is needed and all problems will be fixed...
https://postimg.cc/gallery/YtQpVDm
After the recent OS 11 update ,the media in my device ( photos and videos) not being shown properly in Whatsapp. Some of the videos and pictures which I've already deleted in the gallery are appearing again only in whatsapp in unsupported file format.
I'll be glad if someone confirms that it's a bug in OOS 11.0.2 and that my phone is not the only one which is affected.
I'm using WhatsApp and Parallel Whatsapp. Also have setup a Work/Office profile on my phone.
Does anyone have any solution to this issue?
Thanks and regards!
For me, wifi no longer works. Whenever I try to enable it, it just immediately turns off. It also no longer recognizes my SIM card.
itdiestoday said:
For me, wifi no longer works. Whenever I try to enable it, it just immediately turns off. It also no longer recognizes my SIM card.
Click to expand...
Click to collapse
Try wiping cache from recovery
Update 11.0.1.1
I feel like this is a big joke.
Even more battery drain (yes, i did a factory reset).
Brightness slider issue still not fixed.
Performance still degraded (but i think there is a little bit of improvement)
Not sure about Wifi issues as i never had them.
Weird red tint on screen dimming
Still many ugly and inconsistent ui elements
Color profile is back to being broken (the yellow tint returned)
Update: I've started having the wifi disconnection issues, after 11.0.1.1 update. This is way too annoying.
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
Hi,
here you can find my version for the Samsung Galaxy Note 2 on LineageOS 19.1.
At first I want to thank @rINanDO, @ChronoMonochrome for all your work which was reused here and helped a lot.
Spoiler: Links
TWRP
ROM Android-Filehost
ROM Mega
Spoiler: Whats working
Boot
Audio
Bluetooth
Graphics
Cameras
GPS
Wifi
USB
Video playback (HW/SW)
OTA Updates
Tethering via USB, WIFI and Bluetooth
Sensors
RIL
Spoiler: Whats not working
NFC
Encryption
Maybe random reboots
SD card maybe can't formated as internal memory
Maybe more
I would recommend to use microG instead of gapps,
here you can find the installation instructions:
Spoiler: microG instructions
Download Magisk 24.1 and flash it via TWRP (yes, flash the APK file), reboot
Open Magisk and update the App (and do a reboot if it's asking)
Enable Zygisk in Magisk
Download and install microG installer in the Magisk manager, reboot
Download and install safetynet-fix in the Magisk manager, reboot
Check with a safetynet checker app and you should pass
Spoiler: Changelog
26.01.2022
08.03.2022
17.03.2022
25.03.2022
04.04.2022
19.04.2022
03.05.2022
15.06.2022
08.07.2022
22.09.2022
25.01.2023
Spoiler: How to install it?
Instructions
Wanna improve your sound configs, control your charging current and more?
Now you can use my app to access all boeffla configurations, there will follow more functions.
Exynos4 Kernel Manager - Apps on Google Play
This app provides Boeffla sound control and other kernel + charging tweaks
play.google.com
Telegramm group:
Samsung Galaxy Note II testing group
t.me
Do you like my work?
Than you can simply hit the thanks button and consider to spend me a coffee or a beer,
I'm doing this in my free time and it also costs a lot of money to buy hardware.
donate
XDA:DevDB Information
[ROM][12.x][N7100][BETA] LineageOS 19.1, ROM for the Samsung Galaxy Note 2
Contributors
html6405
Source Code: https://github.com/html6405
ROM OS Version: 12.x S
ROM Kernel: Linux 3.x
ROM Firmware Required: TWRP 3.3.0
Based On: LineageOS
Version Information
Status: Beta
Created 2021-12-30
Last Updated 2023-01-25
Alternative download link for the initial version:
File on MEGA
mega.nz
Originally posted in [ROM][UNOFFICIAL][11.0][N7100][Samsung Galaxy Note 2][LineageOS 18.1][ALPHA][TREBLELIZED]:
I just flashed the newly Android 12 LineageOS 19 build this morning.
It's currently a bit early to share my experience yet since I need some more time, but I already like to share my first impression.
First of all, I was surprised that I could just do a dirty flash over your current 18.1 dec build without any problems.
I did not perform a clean flash because I couldn't backup my Session messages, normally I always perform clean flashes.
I used TWPR 3.5.2 custom recovery to flash this ROM and only wiped Cache and Dalvik Cache/ART partition.
Everything went smooth. It didn't take too long for the first boot either.
Right after the first boot, just when it was booted, the phone rebooted.
After this reboot, I didn't encounter any random reboots yet.
Everything seems working smooth and snappy at the moment.
I can confirm that Magisk 23 is still working on this ROM. You just need to re-flash it after the first boot.
The only annoying thing I discovered is a blinking LED issue and the battery that last less longer, but that's maybe linked to the blinking LED issue.
Something I immediately noticed is that my notification LED is actually red now while charging and green when it hits 100%.
In previous 18.1 build, the LED always got a weird yellowish colour while charging.
Another thing that caught my eye was "Google Play System update" in settings.
I don't understands why it's there since it's supposed to be a degoogled ROM.
Google Play System updates is a part of the Google Play Services ecosystem.
I didn't install any GAPPS and this ROM didn't came with GAPPS pre installed.
Spoiler: What I can confirm is working
- It (re)boots correctly
- Able to receive and sending sms messages and phone calls (didn't try SIM unlock yet. I used the workaround that is mentioned in the main post)
- Camera's
- Wi-Fi (both, 2.4 GHz and 5GHz)
- Video's (YouTube in browser)
- Sensors, except compass (phone rotates correctly)
- Charge correctly to 100%
- S-pen (just as a regular styles, no button functionality)
Spoiler: What is not working + bugs
- An annoying blinking LED issue.
I never experience this before on any ROM.
Can be a coincidence, but after the battery drops below 75%, the notification LED is constantly blinking red, even when the screen is on.
I already tried to literary turn off all notifications options. I even disabled blinking LED option, but it still keeps blinking, even after a reboot. It only disappears after fully charging the phone but will come back in time.
I didn't find a way to fix this.
- Android 12 theme engine seems to be broken.
Some things like buttons (like emergency call button on lockscreen), text (search apps in launcher) and backgrounds in notifications icons in notification panel are still LineageOS teal.
Switching a wallpaper with different colours, but it doesn't change the theme colour of the device. Buttons, lockscreen clock etc. are still light blue. I try to add some screenshots to highlight this problem.
Also, the options to change the icon shape seems to be gone, even in developer settings.
Everything turned into circles after the update. Can't change it.
- USB (can't connect to pc (MTP))
- Extended screenshot beyond your screen
- There was a weird issue that my device is stuck at Samsung Galaxy II screen when turning on the device (not the LineageOS boot screen). I only had this once so can't describe how to reproduce it yet.
I just turned off my device in the power setting inside the ROM. The next time I turned on the device, it was stuck on that screen for 10 minutes. It was fixed by simply holding the power button for a while to turn off the phone.
After doing this, the phone rebooted normally again. I didn't got this issue again.
Besides the blinking LED issue, I had a very good first impression.
I really don't mind that some gimmick features are not working.
I only have this ROM for a few hours, so please keep in mind that I need more time for extensive and more in-depth testing.
Maybe there are some critical problems that I still need to discover.
I just wanted to give a quick update.
@html6405
If there are some specific things you like to try or things I need to keep an eye on, please let me know.
A big thank you to html6405 for this rom! Almost everything seems to work good.
The only thing i am missing is wake by proximity sensor. I use the app Waveup from F-droid for this. I know from trying other roms, that this is an unreliable feature. The sensor hardware is working, that much i know.
When using Lineageos 16, this is a built in feature in the rom, but it deactivates after every reboot. I have to manually turn it off and on every time to get it to work.
No big issue. Just glad to have latest Android on this device. I hope you get more appreciation from this than what you got from your Los 18.1 thread.
Let me know if you want feedback of any kind.
Happy new year!
It does work! I couldn't resist trying the future LOS19.
The overall impression is quite good, as the system seems to be more stable than the previous LOS18.1 for this phone. Still, the development options screen hanged a couple of times. At some point the system crashed and kept rebooting into recovery - fixed by erasing data partition. GPS works, although not well enough. The compass doesn't work in GPStest, but works in Compass app from Fdroid. I tried web browsing and viewing HD videos with Brave browser - very smooth experience. In order to access files on the phone I set up default USB mode in developer settings to files.
Two preinstalled applications are unsafe, contain trackers: camera and via. These had to be removed. Open Camera from Fdroid is installed - it works. The system web browser is preconfigured to ring Google; one may want to review its settings.
Installed Insular app (a sandbox made of the work profile) from Fdroid. The work profile works, but looses its filesystem after disabling and enabling it again. To bring the filesystem back reboot is required.
Phone encryption doesn't work, sadly. This is the same as with many previous custom ROMs for this phone.
A strange horizontal bar is seen at the bottom of the screen (nav bar home button??). Disable "Navigation hint" to get rid of it.
All together, it's an excellent result for the first attempt on LOS19. Looking forward to further releases!
Happy New Year everyone! Thank you html6405 for such an exciting present!
porcino said:
GPS works remarkably well, better than in the previous ROM, but compass doesn't work. I tried web browsing and viewing HD videos with Brave browser - very smooth experience. In order to access files on the phone I set up default USB mode in developer settings to files.
Click to expand...
Click to collapse
This are really great news, could some one else confirm that GPS is working?
I cant test it by my own...
If it's working fine, I will add it to the working list.
GPS seems to work better with "Force full GNSS Measurements" and "Use GNSS APIs" disabled in GPSTest. I also disabled "Force full GNSS Measurements" in "Developer options". From inside a room it locks on 3-5 satellites, although sometimes after a delay.
With GNSS it finds also Russian and Chinese satellites, but uses only the US constellation.
GPS performance, of course, is not as impressive as in new Samsungs, which lock on several constellations at the same time.
----------------
Added later... Still, GPS is not working well enough in this first release. It finds satellites slower than my ancient HTC DHD (ace) running cm13. Then it locks and in a moment loses the lock. I'll look into this in more detail...
porcino said:
GPS seems to work better with "Force full GNSS Measurements" and "Use GNSS APIs" disabled in GPSTest. I also disabled "Force full GNSS Measurements" in "Developer options". From inside a room it locks on 3-5 satellites, although sometimes after a delay.
With GNSS it finds also Russian and Chinese satellites, but uses only the US constellation.
GPS performance, of course, is not as impressive as in new Samsungs, which lock on several constellations at the same time.
Click to expand...
Click to collapse
Great, hopefully some one else can confirm this , you're the only person so far.
Yes indeed - working GPS very important, and needs to be confirmed by multiple sources.
But kudos to the developer for making progress on this.
hello, dear! tell me, what is the battery life? I use rr 5.8.5, the battery lasts for a day of average use. I tried to install lineage 16 - the battery was enough for several hours( now I would really like to switch to this rom, but everything depends on the battery life. thank you for the answers!
alexfire_s said:
hello, dear! tell me, what is the battery life? I use rr 5.8.5, the battery lasts for a day of average use. I tried to install lineage 16 - the battery was enough for several hours( now I would really like to switch to this rom, but everything depends on the battery life. thank you for the answers!
Click to expand...
Click to collapse
Just tried: flight mode, screen off, location off, BT and NFC off, no GApps, just sitting on the desk starting with fully charged. After half an hour the estimated battery life is 10h, 6m. Not great. The battery felt fine last night for a couple of hours of experimenting with secure messengers, then fully charged, then down to 2% by morning. I'll try uninstalling the messengers in case they are draining the battery - wait for an update.
I could not find a way of disabling the clock on the sleeping screen. It disappears after a while, but the screen power consumption is suspect.
Well, this is the first alpha release, the things with power consumption might improve soon.
----------------
Update: I found a way to disable the clock on the sleep screen and the battery life increased to 23 hours, mobile network 1% (still the flight mode is on), phone idle 1%.
The method to disable the display was to press the power button while the notification panel is open...- perhaps another bug.
porcino said:
Well, this is the first alpha release, the things with power consumption might improve soon.
Click to expand...
Click to collapse
The always on display will be turned off in the next build, this will improve the power consumption a lot.
You should be able to disable the always on display in the quick settings (AOD) and give your test a retry .
html6405 said:
You should be able to disable the always on display in the quick settings (AOD) and give your test a retry .
Click to expand...
Click to collapse
Just tried the AOD button: first enabled it and then disabled again... - it worked! Not sure, though, whether any of my previous attempts to modify the settings via adb played any role. I'll repeat timing of the battery with this setting. Thanks.
porcino said:
Just tried the AOD button: first enabled it and then disabled again... - it worked! Not sure, though, whether any of my previous attempts to modify the settings via adb played any role. I'll repeat timing of the battery with this setting. Thanks.
Click to expand...
Click to collapse
Theoretically it should be enabled by default (what I will change in the next build for sure), but anyway, it's good if you can turn it off yet.
Great news, another person confirmed with a video that GPS is working ,
so I will add it to the working list.
Nice to see, that this worked out nearly blindly, because I have no testing opportunities...
With AOD button on then off the battery life is estimated as "more than 2 days left" (flight mode, idle). Let's wait for a little longer...
-------------------
Update: after 11h it predicts "5 days left" and counting! Very good! The graph shows slightly increased power consumption in the first hour, and then it goes almost horizontal. I think it will be more than 5 days at idle, perhaps twice as many.
-------------------
Further update: after 1 day 5 hours it says 9 days left. The way the graph in Battery Usage page goes makes me think that it will last about 20 days if left idle. I don't know what caused the quick discharge in the first hour; after that the graph is a straight line pointing beyond 20 days mark...
-------------------
Yet another update: 28 days predicted after 23 hours of idling. Very good! This is with all wireless interfaces off, Always On Display off and NavBar off.
For reference - Note 4 with cdDroid 9 under similar conditions reports 45 days.
I checked this rom. the sd card is not mounted as internal memory, the phone falls into the bootloop before the lock screen, after which the bootloop again. wipe data or format does not help
-----------------
udp. the backlight of the hardware buttons does not work, although it is enabled in the settings
-----------------
upd. the indication of charge percentages in the status bar does not work when the display is selected with a circle inside the icon
alexfire_s said:
I checked this rom. the sd card is not mounted as internal memory, the phone falls into the bootloop before the lock screen, after which the bootloop again. wipe data or format does not help
Click to expand...
Click to collapse
Simply remove the sdcard.
alexfire_s said:
udp. the backlight of the hardware buttons does not work, although it is enabled in the settings
Click to expand...
Click to collapse
You're right, this will come later from lineageos.
alexfire_s said:
upd. the indication of charge percentages in the status bar does not work when the display is selected with a circle inside the icon
Click to expand...
Click to collapse
Ok, this will also be fixed from the linageos side.
html6405 said:
Simply remove the sdcard.
You're right, this will come later from lineageos.
Ok, this will also be fixed from the linageos side.
Click to expand...
Click to collapse
now I use the 7100 as the main device, I actively use it, I can quickly share bugs if I find them. is it possible to contact you directly without communicating on the formum? do you use a group of testers in telegram?