Database Develop

[Q] Galaxy S & CM 7 problem

Hi,
I'm using the last CM7 ROM (20110509 update)
I have two main issue:
1. My battery get down in ~10% every 1 hours mean my phone can work for only 10 minutes without heavy functions, I'm using sync every 1 hours not push and short phone call.
Any idea ?
2.
I can't send MMS, tried to restart, try using other MMS APS like goSMS but still can't send MMS

I cant get the google apps to work. I did install gapps in recovery mode but the apps does not show in my galaxy.

cm 7 faq & discussion thread : http://forum.cyanogenmod.com/topic/15278-all-models-cyanogenmod-7-faq-user-discussion/
You should post questions over there...
But anyways, for the battery, there are many things you can try.
1) go to the wifi advanced settings and put wifi sleep to "never", it may make the phone unable to sleep otherwise
2) disable sync.
3) look for any app that might be using battery in the background (in battery stats) and delete it (if you don't need it) or kill it every time...
4) try undervolting with a custom kernel such as tk-glitch's : http://forum.xda-developers.com/showthread.php?t=1041532
5) if you DO have a custom kernel, try reinstalling stock cm7 (or see if the kernel has an update) and see if the kernel is the culprit
6) lower your screen brightness, disable wifi/gps/bluetooth, the usual stuff...
7) reboot in recovery with a full battery and wipe battery stats (also, wipe cache/dalvik cache while you're at it)
For the MMS I don't know, I read something about it being fixed but I never actually tried it.
About gapps : factory reset? There might be another solution though, but I have no clue...

Check if your message center number has been set properly...
Sent from my GT-I9000 using XDA App

[April 2, 2016][MOD][FIX]MaxOpt R2 1.0.6 UPDATED CODE BASE

NEW EASY INSTALLER, RECOVERY ZIP
Total overhaul of code.
*HELP WANTED, PM FOR RELEVANT DETAILS*
This software package was originally just made for my personal use to rectify the issue of my phone not entering deep sleep when idle and me not having access to a charger for the majority of the day while also improving multitasking because being my phone is also my build environment/office environment, I am frequently jumping around various apps that I'd prefer to keep open.
Things this package accomplishes on your phone (very simple and brief summary):
*Forces entry into deep sleep as soon as the screen is off (if enabled, on by default). It also has audio detection so you can listen to music with the screen off without unwanted deep sleep entry.
*Improves multitasking, no more apps having to reload/redraw when you switch back to them.
*Automatic odexing of all apps, including new installs (if enabled, pre-lollipop ROM's).
*Easy management of swap.
*CPU management. You can set your own values to be locked (no other app can change them) or let its device manager automatically set CPU frequencies and the governor you specify.
*Dynamic Max CPU Freq: When enabled (on by default) it will automatically scale the max CPU frequency value depending on the CPU load. This can help with governors that favor the high end of the frequency table too much by allowing you to save battery but have the CPU power available when needed, without having to adjust anything manually whenever you go from doing something processor demanding to having your phone sit idle.
*Fixes issues with several kernels where the touch screen is unresponsive after waking the device. No more inconvenient force reboots.
*Enables all idle and suspend states available (they are disabled by default quite often) and can help get your device into the lower C-States.
*Fixes broken links to firmware files caused by buggy init scripts on some ROM's.
New/Other features:
*New recovery flashable installer
*Force system wide GPU rendering and faster framerate.
*Fixes Dt2w and Sw2w lock screen freeze bug.
*Now compatible with KSM.
*Faster app loading and responsiveness. Key android services are given priority status for I/O and CPU resources.
*Multitask over 20+ apps simultaneously without any redraws and low-latency app switching (provided you have the swap space)
Tip: I use the large amount of unused space on /system to increase the size of that MaxOpt managed swapfile.
*Fixed the crash on boot issue between MaxOpt and some kernels.
Default MaxOpt config:
•Swap on, default MaxOpt generated swapfile size is 64 MB, with one made on /data, one on /cache, and one on /system if mounted rw.
•Auto-odexing off.
•Hotplugging compatibility on.
•User CPU settings off, auto-device manager on.
•Deep Sleep immediately on screen off enabled.
•KSM off (you must have a kernel that supports it to enable this option and have it work).
•Kernel settings on.
•Everything is forced to be drawn by the GPU.
All of the above listed features are user optional/tuneable.
For those who wish to only use MaxOpt for fixing the lock screen freeze bug associated with some kernels/DT2W/S2W use the following link: http://forum.xda-developers.com/showthread.php?t=3061589
If you would like to just use individual components or adjust program settings from a terminal app, here is an example usage and description of their individual functions as well as other useful documentation (VERY OLD DOC, NEEDS LOTS OF UPDATES):https://docs.google.com/file/d/0B_hgNZE_j5sVbEN4ZUtkS2p0bW8/edit?usp=docslist_api
Terminal Emulator is what I would recommend for use with managing MaxOpts' settings.
System Requirements (not entirely sure due to lack of public testing):
Busybox
A terminal app
A kernel that can best be utilized by these programs.
Please make a nandroid backup before using.
And here is the MaxOpt installer ( R2 1.0.6 ):
* https://drive.google.com/file/d/0B_hgNZE_j5sVaGdxV0FfODdxbVU/view?usp=docslist_api
Changelog:
R2 v1.0.6- Adjustments to write buffering and multitasking memory performance.
R2 v1.0.5a- Fixed a bug present in both this project and MaxLife where data wasn't validated thoroughly enough before using it.
R2 v1.0.5- Added a new completely experimental new user tuneable (on/off, default off) that changes runtime memory allocation values. Only activate it if you have a large amount of swap.
R2 v1.0.0- Totally rebuilt the project, installable with a recovery flashable zip now, kernel image installer is no longer compatible and is scrapped.
For those still getting crashes:
The issue still appears to be related to the device radio when it happens, so, after a crash could you please force reboot your device and try to disable mobile data when it boots before it crashes again and please post a copy of /proc/last_kmesg. Thank you.
Screenshots of battery screen showing time spent in sleep:
https://docs.google.com/file/d/0B_hgNZE_j5sVSjRUU0ZlX0UwUWc/edit?usp=docslist_api
https://docs.google.com/file/d/0B_hgNZE_j5sVSmNjYThkUzAtNGM/edit?usp=docslist_api
https://docs.google.com/file/d/0B_hgNZE_j5sVcWxJd0JyV09nMDA/edit?usp=docslist_api
Please thank if my software has helped you and please leave logs and descriptions of problems if my software did not work for you.

Wow, this looks amazing. Very nice work.
I Will be playing with this for the next few days.
Sent from my Moto G using Tapatalk

Damn this looks complicated as hell haha. Good job OP

Very nice job

Thank you very much everyone. Glad for the positive feedback, this is my first public software release. I daylight in a machine shop, so this was far from my field of expertise and a long learning experience for me

I tried it on faux kernel 014m.
But my phone bootlooped
I have faux clock app.
Is it causing the problem?
Thanks

One possible problem could be the boot image it made was over 10 MB depending on the size of the input one. If that wasn't the issue, did you disable signature checking? Also this is currently not ART compatible. It is also important that you run the installer from a partition that supports octal permissions, so the emulated sdcard is a no go.
Edit: it may be worth trying disabling the faux clock app too. I don't have that kernel or app to try for myself but this mod does affect CPU settings so it could be a conflict. If none of those work, I may have to look into updating my installer with an alternate method for incompatible kernels.

elrod16 said:
One possible problem could be the boot image it made was over 10 MB depending on the size of the input one. If that wasn't the issue, did you disable signature checking? Also this is currently not ART compatible. It is also important that you run the installer from a partition that supports octal permissions, so the emulated sdcard is a no go.
Edit: it may be worth trying disabling the faux clock app too. I don't have that kernel or app to try for myself but this mod does affect CPU settings so it could be a conflict. If none of those work, I may have to look into updating my installer with an alternate method for incompatible kernels.
Click to expand...
Click to collapse
I followed steps as below:
I put that 2 files in the data partition.
Then boot.img of faux.
I set permission 755 for both files and boot.img
Then from terminal I executed the command.
I got new_image.img
I repack the zip using this new boot image and flashed it in recovery.
Then I reboot.
Phone booted and stuck on "optimizing apps 1 of 98"
Then again same.
Also I had 700mb of free memory when I tried this.
When I again booted using faux kernel I had 450mb of free memory.
Can you guess what's going wrong?

Did you disable APK signature checking?

elrod16 said:
Did you disable APK signature checking?
Click to expand...
Click to collapse
Sorry I forgot that.
Where exactly should I put those 2 files.
Was I doing right to put them in data partition?
And after first boot can I enable signature verification?
Do I need to disable it before every boot?

Unfortunately for now it needs to be off whenever an app is upgraded or added, but can be enabled after the reboot that that happens on, and yeah, /data works

Even after disabling signature verification it doesn't work on faux boot.img
Am I doing right?

For whatever reason it sounds like the dexy binary isn't playing well with your phone, I'll make a new installer with the option of disabling it for incompatible setups for the time being, but the other ones should still work. I'll keep ya posted.

My rom is stock 4.4.4
I will try again with disabled optimization.

kedar512 said:
My rom is stock 4.4.4
I will try again with disabled optimization.
Click to expand...
Click to collapse
OK, hopefully that should be the only part of this package not working for ya. Keep me posted, I'll continue trying to figure this out if it persists.

elrod16 said:
OK, hopefully that should be the only part of this package not working for ya. Keep me posted, I'll continue trying to figure this out if it persists.
Click to expand...
Click to collapse
No luck bro
Same problem.Stuck at optimization.
Should I try it on Xperience kernel?
Its not working with faux.

kedar512 said:
No luck bro
Same problem.Stuck at optimization.
Should I try it on Xperience kernel?
Its not working with faux.
Click to expand...
Click to collapse
I would say yeah, try it with it and see if it makes a difference

Also did you try the new build with a clean restore? (Before any of the failed install attempts) Try not wiping the cache/dalvik-cache after install and flash.

I tried again but this time booted upto lock screen and rebooted.
I tried with new build.

after placing ./maxopt boot.img appears running with dexy enabled.
That means it's already working? If yes, have to do anything else?
Every time you turn the meter will have to repeat the procedure?
Sorry my bad english

WiFi on -> Crash : Hardware or Software related?

Hey folks,
since yesterday I have a serious problem with my Xperia Z3 compact D5803:
After waking up my phone from Stamina it just crashed.
Then it was stuck in a boot loop.
With TWRP I was able to (temporary) fix the boot loop:
- Advanced -> Fix Permission (also SElinux)
- Mount -> System
- Advanced -> File Manager -> Copy build.prop to /system
- Reboot: System
However the system was very laggy, running hot and had a high battery drainage (like 1 percent per minute). In OS Monitor I saw dhd_dpc had around 20% CPU usage (which is related to WiFi), so I disabled WiFi, which fixed these issues.
However after reactivating WiFi system crashed and again stuck in boot loop. And now I can't even fix the boot loop....
So what do the experts say:
a) Is this software or hardware related? (Notice: While the system was laggy, I was still able to download data via WiFi, so the antenna cannot be broken completely)
b) What can I try to fix the boot loop?
c) I guess last resort is factory reset. What else can I try before that?
Thanks!

Anyone?

Unless you say what you actually did to break the device, you're really not going to get much help. Once you own up to what you did to it, perhaps someone can figure out how to fix it.
If you've messed up the ROM, a factory reset isn't going to fix it. You'll need to reflash.

As discussed on IRC, I did nothing on the ROM or the system at all!
However apparently my try on fixing the boot loop, with copying a backup of the build.prop, did in fact broke the boot due to wrong permissions. I was able to fix this with a chmod 0644 on the build.prop.
Now the phone boots fine so far and isn't laggy anymore, however I have still problem with high battery drainage. The phone merely lasts one day...
Under battery usage it is just listing "Android system" as main appliance.
So I hope this is somehow software related and will go with a re-flash. Also then I can use this opportunity to update to 5.1.1 - at least something....

Zte Axon Mini root or custom roms

Full Tutorial and clean Rom by @demenicis http://www.needrom.com/download/zte-axon-mini-model-b2016-only/
You can search on this thread to find the files for Android 6.0.1
You need to root and install TWRP for flashin Android Marshmallow
I recently bought a ZTE Axon Mini here in Europe. It is a pretty good phone, the only problem is the software part which has some lag and UI problems.
They certainly can be fixed with a custom rom or rooting and doing changes or by ZTE themselves.
Here I will write the problems
1) The touch responsiveness could be more fast and snappy, when scrolling etc.
2) random lag occurs from time to time, Some other lag issues with the background apps closing etc.
3) Notifications sometimes do not show at all even when keeping aps on whitelist (deactivate mi assistant to solve this)
4) Dolby Audio gets deactivated almost every time you use headhones .
5) Marshmallow release anytime soon?
6) the UI is too heavy for the phone, most stock apps have issues
7) You cannot adjust brightness inside camera app on auto mode, the HDR mode is really not good ( too blurry)
Click to expand...
Click to collapse
Most of these issues have been fixed on 6.0.1 Rom (search thread)
Summary and further tweaks by @demenicis http://www.needrom.com/download/zte-axon-mini-model-b2016-only/
Edit 1--------------------------------------------------
Root method has been found and works on all axon mini models Android 5.1.1
Credit for finding @orbitz52 and @Heze85
http://www.mgyun.com:81/thread-48100-1-1.html
Just translate the page on Chrome and follow the instructions
For 6.0.1 Marshmallow Root you need to have custom recovery and flash supersu via recovery
Edit 2--------------------------------------------------------
Notification issue has been solved (read pages 1-3)
!!IMPORTANT NEWS!!
Custom recovery for axon mini by @Bormental
TWRP 3.0.2 for ZTE Axon mini unofficial.
It works in all Axon mini mods (B2015 and B2016 with or without "Force Touch".
Installation manual:
1. ROOT device (see the manual in this thread).
2. Download the archive with TWRP.
3. Unzip twrp.img to phone's internal storage.
4. Install any terminal emulator from Google Play and open it.
5. Paste these lines one by one to terminal:
Code:
su
dd if=/dev/block/bootdevice/by-name/recovery of=/sdcard/stock_recovery.img
dd of=/dev/block/bootdevice/by-name/recovery if=/sdcard/twrp.img
6. Keep the file stock_recovery.img in safe place. It is your stock recovery image.
7. Now TWRP is installed. You can run it by holding vol+ and power button when phone is off or just reboot your phone while holding the vol+ button.
HOW TO ENTER RECOVERY WHEN ON BOOTLOOP WITHOUT EMPTYING THE BATTERY by @Crisvendetta
1. Hold volume up and power button the whole time of this procedure until the moment said below
2. Keep holding, the first time the device will be stuck on boot logo for 10 seconds and restart
3.Keep holding until the device is stuck on boot loop for 5-6 seconds before powering down.
4. RELEASE BUTTONS AS SOON AS SCREEN SHUTS DOWN ON THE 5 SECOND BOOT
5.Now Device is shut down
6. You can enter recovery normally by holding power plus volume+
What to do if the phone with android 6.0.1 is suddenly switching off during backup, restore, copying heavy files or installing ROM:
CLICK TO HIDE CONTENT
Install aboot image from 5.1.1
Reboot recovery
Make all needed operations
Return back aboot image from 6.0.1 before rebooting to system
Attention! Android will boot only with proper aboot image installed!
WARNING! Your warranty is now void! Any operation with firmware can break your phone!
Special thanks
1) @Bormental
2) @orbitz52
3) @demenicis

Hi,
I can't confirm 1), actually my device runs smooth. I have the Build Version ZTE B2016 FTV1.0.0B01.0
2) random lags occurs, but rare.
3) it seems that this is an issue by the power saving management, I also have some issues with it. I'm actually testing autostart and whitelisting for background the important apps like messengers.
4) I didn't tested this yet
5) I read something arround February this year.
If you google for root, you can find some work instructions, but OTA will be deactivated. I have not tested it yet, will give the phone a few months and ZTE for the update

Issues
I have a lot of problems with this phone. Sometimes apps doesn't work. Most of the times I can't recive notifications, sometimes is laggy, some options doesn't work or change to it's inicial configuration, force touch is not accurate.... A lot! Please ZTE do something!. BTW, how can I solve the notification problem?!
Thank you so much

Korgan1983 said:
Hi,
I can't confirm 1), actually my device runs smooth. I have the Build Version ZTE B2016 FTV1.0.0B01.0
2) random lags occurs, but rare.
3) it seems that this is an issue by the power saving management, I also have some issues with it. I'm actually testing autostart and whitelisting for background the important apps like messengers.
4) I didn't tested this yet
5) I read something arround February this year.
If you google for root, you can find some work instructions, but OTA will be deactivated. I have not tested it yet, will give the phone a few months and ZTE for the update
Click to expand...
Click to collapse
The notification part is the worst until now.
What I would add is that the camera app is unstable. It gets randomly on night mode and could be improved, on the focus and autoexposure part .
Overall the phone is great, it needs to be improved on the software part and I believe it could succeed and give ZTE a even better reputation
Now on the updates, does anyone know when marshmallow will be released for the Axon mini?

Notification
Crisvendetta said:
The notification part is the worst until now.
What I would add is that the camera app is unstable. It gets randomly on night mode and could be improved, on the focus and autoexposure part .
Overall the phone is great, it needs to be improved on the software part and I believe it could succeed and give ZTE a even better reputation
Now on the updates, does anyone know when marshmallow will be released for the Axon mini?
Click to expand...
Click to collapse
Yes, the notification part is the worse. It should be solved in the coming days...

ZTE AXON notifications FIX !
Aitex10 said:
Yes, the notification part is the worse. It should be solved in the coming days...
Click to expand...
Click to collapse
Ok guys, I have solved the notification issue, it seems ZTE had optimized the system for app cleaning, it even cleaned out some resources whatsapp and other apps such as this need to send notifications. Here is the solution for the ZTE AXON (all series)
1. Go inside settings /Power manager /manage background . Here deselect all the apps that you want to send notifications.
2. settings/power manager/auto start manager . Here select all the apps that you want to send notifications.
3. go inside Mi-assistant /Acceleration/ Whitelist . Here select all the apps that you want to send notifications. Otherwise, disable Mi-Assistant from the settings/apps.
It seems the tap to accelerate would remove all resources from these apps, With these changes, every notification will come as usual. CHEERS!!

Crisvendetta said:
Ok guys, I have solved the notification issue, it seems ZTE had optimized the system for app cleaning, it even cleaned out some resources whatsapp and other apps such as this need to send notifications. Here is the solution for the ZTE AXON (all series)
1. Go inside settings /Power manager /manage background . Here deselect all the apps that you want to send notifications.
2. settings/power manager/auto start manager . Here select all the apps that you want to send notifications.
3. go inside Mi-assistant /Acceleration/ Whitelist . Here select all the apps that you want to send notifications.
It seems the tap to accelerate would remove all resources from these apps, With these changes, every notification will come as usual. CHEERS!!
Click to expand...
Click to collapse
How come Axon on 5.1.1 doesn't have Power manager or Mi-assisant?

Crisvendetta said:
Ok guys, I have solved the notification issue, it seems ZTE had optimized the system for app cleaning, it even cleaned out some resources whatsapp and other apps such as this need to send notifications. Here is the solution for the ZTE AXON (all series)
1. Go inside settings /Power manager /manage background . Here deselect all the apps that you want to send notifications.
2. settings/power manager/auto start manager . Here select all the apps that you want to send notifications.
3. go inside Mi-assistant /Acceleration/ Whitelist . Here select all the apps that you want to send notifications.
It seems the tap to accelerate would remove all resources from these apps, With these changes, every notification will come as usual. CHEERS!!
Click to expand...
Click to collapse
Also remove the accelerator settings inside the mi assistant / software settings

Dooosu said:
How come Axon on 5.1.1 doesn't have Power manager or Mi-assisant?
Click to expand...
Click to collapse
I am also on 5.1.1.

Notification works better with enabling autostart and enabling background settings. I have disabled the Accelerator / Mi-Assistant, Android has its own power management.

Hello,
i did not find MI-Assistant, where exctely?

Crisvendetta said:
Also remove the accelerator settings inside the mi assistant / software settings
Click to expand...
Click to collapse
Hi,
where can i finf mi Assistant??????

ridowski said:
Hi,
where can i finf mi Assistant??????
Click to expand...
Click to collapse
Which version of Axon do you have ?

It seems the ZTE Axon A1R doesn't have mi-assitant or even power manger/ background manager, and it's on 5.1.1
Guess no way to get that without unlocking the bootloader?

Crisvendetta said:
Ok guys, I have solved the notification issue, it seems ZTE had optimized the system for app cleaning, it even cleaned out some resources whatsapp and other apps such as this need to send notifications. Here is the solution for the ZTE AXON (all series)
1. Go inside settings /Power manager /manage background . Here deselect all the apps that you want to send notifications.
2. settings/power manager/auto start manager . Here select all the apps that you want to send notifications.
3. go inside Mi-assistant /Acceleration/ Whitelist . Here select all the apps that you want to send notifications.
It seems the tap to accelerate would remove all resources from these apps, With these changes, every notification will come as usual. CHEERS!!
Click to expand...
Click to collapse
Tried this on mine and this made no difference in fact in an attempt to combat the delayed notifications I had done the above and unfortunately in my case made no difference? If anyone has any other suggestions please let me know.

hoppi05 said:
Tried this on mine and this made no difference in fact in an attempt to combat the delayed notifications I had done the above and unfortunately in my case made no difference? If anyone has any other suggestions please let me know.
Click to expand...
Click to collapse
Inside mi assistant remove the auto run on startup and then press exit the mi assistant.
This last few days every notification has shown on time, I did a fresh factory reset and the applied all the settings. Don't know if that would help everyone but I am satisfied until now

I didn't do a factory reset and stopped the Mi-Assistant. Notifications work well after that. But don't forget to do Step 1 and 2, that is still neccessary beside of stopping the Assistant.

I was wondering what is the difference between zte b2015 and b2016 models. I have the b2016 but it seems nothing changes with b2015.
My geekbench 3 scores single core 712 multicore 3107
Antutu 38051 .

Korgan1983 said:
I didn't do a factory reset and stopped the Mi-Assistant. Notifications work well after that. But don't forget to do Step 1 and 2, that is still neccessary beside of stopping the Assistant.
Click to expand...
Click to collapse
Indeed, disabling Mi-assistant together with the steps mentioned, solves all notification issues

Dooosu said:
How come Axon on 5.1.1 doesn't have Power manager or Mi-assisant?
Click to expand...
Click to collapse
What model is that? Sounds like the US version?

Battery Drain After New Update

After I received new update on oxygen OS, my phone's battery is draining like crazy. Initially it was not the case. Is this the same with everyone?

Not too sure, but with all the buzz around I want to downgrade without losing the data. I personally clocked in 5hr SOT with 15% juice still left on 3.5.4.
Ex Nexus 5 user, so all in all i am elated with such numbers. But the Nexus 5 rocked with its excellent Dev support.
Also, the encryption makes things a little weird for ROM flashers.

Was the same here. Reverted back to 3.5.3. Just unlock bootloader Install twrp, flash OOS 3.5 3 and lock bootloader and flash original recovery again. If you're unlocked, just flash 3.5.3.
My battery life is better now.

Yup, the new Oxygen OS drained the battery like mad. I changed to Hydrogen Os instead and it is ok.

yeah, it drain more on 3.5.4 than 3.5.3

Wrote this tutorial for another thread. If you are already bootloader locked and stock then there's no need to unlock bootloader or even use any ADB commands. The mechanism to upgrade/downgrade is built into OOS.
NOTE: This should only be used if running stock, bootloader locked and unrooted. Haven't tested this downgrade procedure on any other configuration.
CREDIT: Namanjr for the link to the OTA in his wonderful thread: http://forum.xda-developers.com/oneplus-3t/how-to/zip-flashable-firmware-modem-t3509015
1. Download the 3.5.3 OTA Full Zip from here: https://s3.amazonaws.com/oxygenos.o...8_OTA_027_all_1611222319_884473ff95304c30.zip
2. Connect your phone to your computer via original usb cable.
3. In your phone's notification shade, press on the "USB for charging" notification and select MTP file share for Windows and Mac.
4. Open the phone on your computer's file explorer. (You should see your storage contents and folders on your phone)
5. Copy the previously downloaded OTA into the root directory of your phone. (Don't navigate into any of the phones sub-folders just stay in the root directory)
6. Go to your settings menu on your phone and scroll all the way down to "System Updates" and enter into that menu.
7. Hit the gear icon in the Upper Right-hand corner and select "Local Upgrade"
8. It should list the OTA that you put in the root folder. Click on it and confirm "Upgrade Now" (The upgrade dialog box also indicates that this method does not affect your data so you should be good to proceed and keep you existing data)
9. It should begin the update process, reboot the phone and complete the "Upgrade" (Really a "Downgrade")
10. Once rebooted go into your Settings on your phone and confirm that it downgraded to 3.5.3. in the "About Device" section of the menu.
11. Hit the Thanks if this helped.
NOTE: You will probably see a notification in your settings menu and also your notification shade advising you of an update being available. This will be the 3.5.4 OTA again so don't choose to update to that until they have released a better fix for the battery drain issue.

I haven't experienced anything of that nature with the latest update. Battery life seems just like before.

Same here, i only can have 4h the SOT. The 3.5.4 is horrible for battery life.
Oneplus told me to do a factory reset, to solve the problem.

Same here, it's quite noticeable specially when it was behaving so good on 3.5.3

Hope they will fix it in next build. For now it lasts really bad.
Wysłane z mojego ONEPLUS A3003 przy użyciu Tapatalka

no drain.
must be your setup.

I don't run many applications and noticed a big difference in the battery life, reassuring to see its not just me, hopefully next update fixes or it'll be a rollback as well

Whizdumb81 said:
Wrote this tutorial for another thread. If you are already bootloader locked and stock then there's no need to unlock bootloader or even use any ADB commands. The mechanism to upgrade/downgrade is built into OOS.
NOTE: This should only be used if running stock, bootloader locked and unrooted. Haven't tested this downgrade procedure on any other configuration.
CREDIT: Namanjr for the link to the OTA in his wonderful thread: http://forum.xda-developers.com/oneplus-3t/how-to/zip-flashable-firmware-modem-t3509015
1. Download the 3.5.3 OTA Full Zip from here: https://s3.amazonaws.com/oxygenos.o...8_OTA_027_all_1611222319_884473ff95304c30.zip
2. Connect your phone to your computer via original usb cable.
3. In your phone's notification shade, press on the "USB for charging" notification and select MTP file share for Windows and Mac.
4. Open the phone on your computer's file explorer. (You should see your storage contents and folders on your phone)
5. Copy the previously downloaded OTA into the root directory of your phone. (Don't navigate into any of the phones sub-folders just stay in the root directory)
6. Go to your settings menu on your phone and scroll all the way down to "System Updates" and enter into that menu.
7. Hit the gear icon in the Upper Right-hand corner and select "Local Upgrade"
8. It should list the OTA that you put in the root folder. Click on it and confirm "Upgrade Now" (The upgrade dialog box also indicates that this method does not affect your data so you should be good to proceed and keep you existing data)
9. It should begin the update process, reboot the phone and complete the "Upgrade" (Really a "Downgrade")
10. Once rebooted go into your Settings on your phone and confirm that it downgraded to 3.5.3. in the "About Device" section of the menu.
11. Hit the Thanks if this helped.
NOTE: You will probably see a notification in your settings menu and also your notification shade advising you of an update being available. This will be the 3.5.4 OTA again so don't choose to update to that until they have released a better fix for the battery drain issue.
Click to expand...
Click to collapse
Nice. It took the downgrade/upgrade perfectly. I'll keep an eye on it today. Thank you and the OP!

To control battery drainage, use greenify donate version, it will automatically Hibernate background apps which are consuming much battery, if your phone is rooted, download kernel adiuter to control your kernel's CPU frequencies, use powersave mode in cpu frequency settings to lower down the frequency of the CPU, lowering down the frequencies of the cpu helps power savage