an experiment to drastically improve battery life consumption - AT&T, Rogers HTC One X, Telstra One XL

so I had almost decided to give up my One X for something newer (I have been looking at Xiaomi MI3 ), but I wanted to give the One X one last shot.
I have no other problem with my Evita except for the battery life - so that is the one thing I wanted improved. This post is not for people who are already getting 4-5 hours of screen-on time. But I was barely getting through HALF A DAY on my evita.
WARNING: this will format your entire phone - including SDCARD and the whole system. So make sure your system is backed up. Also make sure that you are S-OFF.
step 1 - upgrade the firmware/hboot to 2.18. A lot of you will flash the RUU for this - I went for the simpler method (thanks @timmaaa ) using the firmware here.
Code:
fastboot oem rebootRUU
fastboot flash zip 218firmware.zip
If the output ends with "FAILED (remote: 90 hboot pre-update! please flush image again immediately)", run the previous command again. If it ends with "INFO..... OK", just reboot to the bootloader with this command:
fastboot reboot-bootloader
step 2 - upgrade recovery to TWRP 2.7.1.0
Code:
fastboot flash recovery openrecovery-twrp-2.7.1.0-evita.img
step 3 - boot to recovery. in TWRP run a full wipe . EVERYTHING. Reboot to recovery.
step 4 - boot to recovery. advanced -> fix permissions. Reboot to recovery.
step 5 - boot to recovery. copy your ROM and gapps to "internal_sd" (note if you see your folder as "/sdcard", then try wiping and rebooting again). I used cm-11-20140718-NIGHTLY-evita.zip and pa_gapps-modular-micro-4.4.4-20140716-signed.zip
step 6 - boot normally and setup your android. reboot to recovery
step 7 - download bubba kernel as well as normalToQV script. install from recovery.
step 8 - Download PurePerformanceX and install through recovery.
step 9 - boot normally
step 10 - go to your brightness settings and click the small settings icon next to the brightness bar. Set sensitivity to "very high" and click adjust (this will cause the evita to react quickly to ambient light changes). Also (and this bit is a little hard to explain) you need to set the system so that it is dimmer than necessary. The Evita's backlight is actually too bright for its own good and consumes a lot of power. So reduce the intensity of backlight at all "levels"
Step 11 - remember to turn off NFC. You can switch off other networks off too, but I keep GPS at high accuracy most of the time.
Ste 12 - with full credit to @timmaaa through this post. I have made some changes in the text below
"First (and I'm not sure if this is relevant because I am still waiting for my OPO to be delivered) thing is to enter Privacy Guard through Settings (if it exists), then click Advanced or Show Built-In Apps. From here you can select Google Play Services and turn off everything except for location.
Next you need to download Android Tuner. Open it and go to Android Tuner -> Sidebar Menu -> Apps Manager -> Application Startups, open the box at the top and change it to All, click the button in the bottom-right until it says System, scroll to Google Play Services and select it, a huge list will open, scroll to very near the bottom and find the Wakeup option, uncheck the box.
Again, open Android Tuner it and pull out the side menu on the left, and go to Android Tuner -> Sidebar Menu -> Apps Manager -> Application Manager. Then select the "Apps" tab and Click the centre box at the bottom until it says System, scroll to find Google Play Services and highlight it, press the Manage button in the bottom-right and select Permissions. This should bring you to the Perms tab, swipe across to the Services tab. In this list you want to uncheck anything that starts with Ads or Analytics, you also want to uncheck anything that starts with com.Google.android.location.reporting as well.
Doing all of this has completely stopped Play Services from draining the battery for me."
Click to expand...
Click to collapse
I am now getting close to 4 hours screen on time. Keeping my fingers crossed - will update this thread if there power consumption goes down. Do note that I already have whatsapp, facebook, truecaller, twitter running - so power consumption is a realistic indication.

Good guide. I think it might belong in General though, I'll ask for it to be moved for you.
Sent from my Evita

Yes. Very good guide. Question, what would one benefit by setting that brightness thing to very high? I noticed there are very high,high,medium and low. I never understood those settings. Could you help me understand ? ?

marknoll said:
Yes. Very good guide. Question, what would one benefit by setting that brightness thing to very high? I noticed there are very high,high,medium and low. I never understood those settings. Could you help me understand ? ?
Click to expand...
Click to collapse
What you're doing is setting the sensitivity to high, it's kinda like fooling the phone into thinking the ambient light is brighter than it actually is and therefore lowering the brightness of the backlight. Of course this is only relevant for auto-brightness. It's to combat the fact that this device over compensates for ambient brightness and unnecessarily raises the brightness of the backlight.
Sent from my Evita

So on that note,its safe to say that having it on very high helps battery? Would it help in the aspects of making the phone brighter in let's say..daylight?

@marknoll - let me elaborate. What I meant was that the screen should be dimmer than default. And sensitivity is very high,so that the screen responds fairly quickly to changes in ambient light. I did NOT mean screen should be brighter than normal. The Evita screen consumes a LOT of power. My apologies if my language was a bit confusing. I'll correct it once I get to my laptop

@sandy. Dude. I'm not referring to u . I was asking in my behalf. Not yours

really glad you shared your method with us........ me too thought of mi3 but my attraction for evita is still enough to use though my only problem is battery life like you..... does your method works for sense roms as well.... il give it a try anyways though...

paras33 said:
really glad you shared your method with us........ me too thought of mi3 but my attraction for evita is still enough to use though my only problem is battery life like you..... does your method works for sense roms as well.... il give it a try anyways though...
Click to expand...
Click to collapse
@paras33 - I suggest you dont try this method with sense ROMs. I'm not sure about the interplay of recovery 2.7.1.0 with sense roms. Especially the whole "internal_sd/sd0" vs "/sdcard" differences. I do recommend that you try the particular CM rom that I pointed to - you might really like it !

How to change settings for PurePerformanceX ?

sandys1 said:
@paras33 - I suggest you dont try this method with sense ROMs. I'm not sure about the interplay of recovery 2.7.1.0 with sense roms. Especially the whole "internal_sd/sd0" vs "/sdcard" differences. I do recommend that you try the particular CM rom that I pointed to - you might really like it !
Click to expand...
Click to collapse
Ok so i'm gonna try this with rom u said but how to revert back if want go back to sense 5..?
Also is pure performancex compatible with sense rom.?..thanks
Sent from my HTC One XL using xda premium

paras33 said:
Ok so i'm gonna try this with rom u said but how to revert back if want go back to sense 5..?
Also is pure performancex compatible with sense rom.?..thanks
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
I think you should go and ask this on the Evita sense rom thread (e.g. ViperXL). I'm not sure if TWRP 2.7.1 and PurePerformanceX are compatible with sense

I am unable to boot up with bubba. I always get stuck on the boot animation. No matter how long I wait it just stays there. I've tried with and without the voltage script.
Sent from my One X using XDA Free mobile app

Did you follow the exact steps that I have outlined? This means your phone was clean-wiped. You shouldn't have had this issue - can u confirm?

Yes. I wiped everything. I wiped several times just to make sure it was clean. O forgot to mention i am running candykat rom, which may be the issue. I asked in their q/a thread about bubba with no answer. I had tried bubba before this also and had same issue. I can run torched OK. When I have time I may try again with a full wipe but I need to back some things up first.
Sent from my One X using XDA Free mobile app

So I found the problem. I had been using art runtime. I switched back to dalvik and booted fine. Apparently it does not like art.
Sent from my One X using XDA Free mobile app

Related

Htc Touch Pro (Raphael 500) Running Android , How to overclock?

Alright so Yesterday I installed the android os on my touch pro (raph 500)
i orginally have windows mobile 6.5 which is preety fast
but android is really slow!
i turned off all the settings which i would think it used alot of memory but still no help, so i started seeing videos on overclcking?
can someone explain to me on how to do this,
with links to the download
i really need to speed this up ,it would be amazing if it worked.
also if you give me a response that helps me , ill donate 10.00+ to you .
I do not require funds as I enjoy helping out!
From THIS thread and THIS post:
Overclocking
acpuclock.oc_freq_khz=XXXXXX ( suggested 600000-640000 )
but it is very unstable if you try to get higher than 650000-700000
Click to expand...
Click to collapse
Basically, you add that to the startup.txt file somewhere between the parentheses with an added space between the next command. Keeping in mind, with added OC, you may and may not notice a difference in stability. I honestly never use OC and I am using FroYo from THIS thread. Additionally you can try out Gingerbread Alpha from THIS thread. Please leave feedback in their respective threads, thanks!
n-Joie! (Enjoy)
thanks but this is my startup text :
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2182
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=210 msmvkeyb_toggle=off physkeyboard=raph board-htcraphael-navi.wake=0 gsensor_axis=2,-1,3 acpuclock.force_turbo=1"
boot
Click to expand...
Click to collapse
so which am i supposed to edit, sorry im a noob lol
& u said that was the one you used,
is it fast?
Actually, I can't use that one because I have an at&t Fuze. If you have a RAPH500, you might want to use the following:
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2182
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=210 msmvkeyb_toggle=off physkeyboard=raph board-htcraphael-navi.wake=0 gsensor_axis=2,-1,3 pm.sleep_mode=1 acpuclock.oc_freq_khz=XXXXXX"
boot
Click to expand...
Click to collapse
Where XXXXXX is equal to a value between 600000-640000
Additional note: make sure you type something like 600000 or any value up to 640000
lol thanks im trying to see if theres a difference in speed.
but you used froyo?
is that running fast?
It's running fine with sync and a few other apps running in the background. I would be mindful of livewallpaper and HQ video at the moment as this project is currently still under development, at best. At least that is what I have noticed as far as performance is considered. I have also run a stripped Gingerbread alpha build (the one I linked you to earlier) and it is running faster/smoother than FroYo. To be expected without all the bells and whistles...
NOTE: Speed is relative to performance at the moment. Hence why I say it's still under development...
intresting ill test that out in about 15 mins
but does yours take a long time to come out of sleep mode?
Hmmm, that might be the notorious sleep of death SOD. I usually do something that most don't like but I sort of turn off the screen time out by first making the screen time out greater than 10 or 30 minutes. After that it should make things easier as far as disabling the auto back light/screen timeout feature. Keep in mind this is only a work around, I believe there is mention of actually fixing this issue. You'll need to download a free app called batterybooster (use the link if you want to read up on it a little). Once installed, run it and look for the far right icon and tap it. Set the timeout to Never and you'll notice a decent performance enhancement in the screen off and screen on.
NOTE: You will need to manually turn it off from here-on. You can try to play around with the setting but I find it somewhat problematic. Meaning that if you enable the timeout, it might and it might not work.
alright well i tried the gingerbread and that didnt work it lagged .
i tried froyo , it was amazing then i found out wifi didnt work
so now im back to the regular android one i had before ill be trying to see if theres a difference now that i "overclocked" it .
but thanks for all the help.
ill post back if i need something!
Odd, wifi(wap not wep) works for me... Must be a random occurrence? Have you attempted to update any files and are you using OC? Probably best to stick to a stock-like startup till you get a good feel of most of the basic functions, which may or may not include wifi, gps, 3d and camera; these should be on the "to be worked on" list of things for the devs to complete.
R^7Z said:
Odd, wifi(wap not wep) works for me... Must be a random occurrence? Have you attempted to update any files and are you using OC? Probably best to stick to a stock-like startup till you get a good feel of most of the basic functions, which may or may not include wifi, gps, 3d and camera; these should be on the "to be worked on" list of things for the devs to complete.
Click to expand...
Click to collapse
it works for you?
wth!
and i havenet updated any files on the deive.
no im not using overclock on this onr,
but on another android version which is on my sd card i am
& is there a way i can lock my screen so it doesn't touch any buttons in my pocket &kepp it from going into SOD .
ndnmaster096 said:
it works for you?
wth!
and i havenet updated any files on the deive.
no im not using overclock on this onr,
but on another android version which is on my sd card i am
& is there a way i can lock my screen so it doesn't touch any buttons in my pocket &kepp it from going into SOD .
Click to expand...
Click to collapse
NVM I got the wifi to work now .
Glad to hear about the wifi success story I don't know if I could walk you through that as it seems that wifi can be temperamental ( or just mental )
The only way I could get out of the SOD issue was to try for that work around (setting it to never timeout with the app mentioned) and to set a pattern unlock
R^7Z said:
Glad to hear about the wifi success story I don't know if I could walk you through that as it seems that wifi can be temperamental ( or just mental )
The only way I could get out of the SOD issue was to try for that work around (setting it to never timeout with the app mentioned) and to set a pattern unlock
Click to expand...
Click to collapse
well i set it to never timeout and i have a lock pattern
but since it never times out it wont lock .
also now im starting to notice froyo is rebooting for some weird reason automatically .
Calm down, that is kind of "usual behavior" . There are quire a few things going on and the OS is attempting to "handle it". Sometimes it can't and just quits instead of freezing up ( which would be the lesser of two evils ). To get it to lock, you will have to turn it off manually (power button). Unfortunately, I think if the keyboad slides out, it self unlocks (kind of a self defeating purpose, more or less). If you turn the screen off and wait like 10 seconds then turn the screen on (power key), you should see the lock. I can't say for sure but it does work for me. I don't really have much time for troubleshooting today, as I am at work currently but do look over the threads I linked you to earlier if at all possible.
okay so i turned it off using the power button and it booted to windows mobile (odd)
then i tried running haret.exe & got this message:
"The file HARET cannot be opened. Either it is not signed with a trusted certificate, or one of its components cannot be found. IF the problem persists, try reinstalling or restoring the file."
im not sure what to do.
i tryed reformatting the card and installing fresh files, which didnt work so now im left questioned?
When you say you turned it off, did you hold the button or just press it once? If you pressed it once, then, that is definitly not "usual" behavior. I recall having that issue once upon a time but for the life of me, I don't recall what I did to recover from it. However, it sounds like you are attempting to run from a shortcut that references the program(haret) that is no longer there. To resolve this, I need you to confirm that you are running from the microSD and not a shortcut. Also, you aren't formatting under windows, right? If you are formatting from windows, that would be a "no-no"
Find something like the HP tool (can be googled) that everyone else talks of or even something like the free version of partition wizard should work.
i held the button and it gave me options
1) airplane mode
2)shutoff
3)vibrate
i did try to make a shortcut but i deleted it and now when i checked i was running it from the actual application.
lastly, i did format from windows but i downloaded hp format tool
and formated my device in quick format.
reinstalled the programs and it still gave me the same error message,
please help, i really miss android =(
Try deleting data.img and letting it recreate the file. To clarify about the screen off issue, when you press the power button once (not hold), what does it do? Also, which kernel package are you using and have you attempted to download a newer kernel package yet?
Also, try THIS kernel package; I got it from THIS site. It looks like that kernel package is specific to our devices.

Touch key brightness

Hey all, I'm trying to figure out how to get some brightness settings for the touch key brightness to stick. I've used LG 2x Notifications and O2x Touch Key Brightness, and they both work up until the point where i put the phone to sleep by tapping the power button. As soon as I wake it up, the brightness goes straight to zero unless i head back to the app and raise it up again. And if i uninstall the apps, the brightness on my keys stay off until i re-flash or reinstall the app again. Help!
My issue is a little different but similar. It worked fine for me on every basic gingerbread rom, but when I switched to a cm7 based rom the lights change with the brightness of the screen. I turned off all the light notifications but it did not help.
If anyone has any ideas, I'd love to hear them.
What rom?
Sent from my LG-P999 using XDA
redmonke255 said:
What rom?
Sent from my LG-P999 using XDA
Click to expand...
Click to collapse
On SinghUI but it doesn't have built-in LED notifications, if that's what you're getting at.
If the setting from one of those apps doesn't stick, then it's most likely being set by your ROM or Kernel. Have you tried checking if you get the same issue with other ROMs?
@jcbofkc That's a built-in setting that can't really be changed unless you get a custom ROM or Kernel cooked up to remove the link between the brightnesses.
xBIGREDDx said:
If the setting from one of those apps doesn't stick, then it's most likely being set by your ROM or Kernel. Have you tried checking if you get the same issue with other ROMs?
@jcbofkc That's a built-in setting that can't really be changed unless you get a custom ROM or Kernel cooked up to remove the link between the brightnesses.
Click to expand...
Click to collapse
90% sure the ROM doesn't have built in notifications. I'm noticing now that very rarely the settings do stick. Perhaps there is a way to force the app to stay in memory?
rrroach said:
90% sure the ROM doesn't have built in notifications. I'm noticing now that very rarely the settings do stick. Perhaps there is a way to force the app to stay in memory?
Click to expand...
Click to collapse
That wouldn't work. All that those apps do is write a number from 0-20 to the text file:
/sys/devices/platform/star_touch_led/wled
in your root file system.
When you read the file, it shows you the current output to the LEDs (from 0uA to 2000uA).
When you write to the file, it interacts with the Kernel and sets the brightness.
The Touch Key Lights type apps, all they do is when you move the slider they write a value to that file, and that's it. The only reason it wouldn't stick is if your ROM or Kernel is changing the value in the background. For example it will set it to 0 when you turn the screen off, and then it should set it back to wherever it was before when you turn the screen on again.
The closest you could get is to take the source for LG Touch LED Notifications and modify it to set the brightness every few seconds or something, but that probably wouldn't be too good for your battery life.
Based on your symptoms it appears that either your ROM or your phone doesn't really handle the modifying of the brightness very well. It looks like SinghUI does use a kernel from CM7, so I don't think your kernel is the problem. I'd suggest flashing the most recent CM7.2 RC, and seeing if you have the same problem there. CyanogenMod will change your LED brightness based on your screen brightness though.
EDIT: Ignore all that for a moment, try this first. It is a post from January 21st in the SinghUI thread, so it might not work now, but go ahead and try it: http://forum.xda-developers.com/showpost.php?p=21652744&postcount=293
Also I'd suggest posting in the SinghUI thread as everyone there is using your ROM, so they might be able to help better.
xBIGREDDx said:
That wouldn't work. All that those apps do is write a number from 0-20 to the text file:
/sys/devices/platform/star_touch_led/wled
in your root file system.
When you read the file, it shows you the current output to the LEDs (from 0uA to 2000uA).
When you write to the file, it interacts with the Kernel and sets the brightness.
The Touch Key Lights type apps, all they do is when you move the slider they write a value to that file, and that's it. The only reason it wouldn't stick is if your ROM or Kernel is changing the value in the background. For example it will set it to 0 when you turn the screen off, and then it should set it back to wherever it was before when you turn the screen on again.
The closest you could get is to take the source for LG Touch LED Notifications and modify it to set the brightness every few seconds or something, but that probably wouldn't be too good for your battery life.
Based on your symptoms it appears that either your ROM or your phone doesn't really handle the modifying of the brightness very well. It looks like SinghUI does use a kernel from CM7, so I don't think your kernel is the problem. I'd suggest flashing the most recent CM7.2 RC, and seeing if you have the same problem there. CyanogenMod will change your LED brightness based on your screen brightness though.
EDIT: Ignore all that for a moment, try this first. It is a post from January 21st in the SinghUI thread, so it might not work now, but go ahead and try it: http://forum.xda-developers.com/showpost.php?p=21652744&postcount=293
Also I'd suggest posting in the SinghUI thread as everyone there is using your ROM, so they might be able to help better.
Click to expand...
Click to collapse
Thanks for the link. It turns out that the ROM does have led notifications. However, disabling them didn't help the problem. :/ the g2x has just been an awful experience for me! :/

Android 5.0-5.1 Bugs/Annoyances

1. On 5.1 there is still no option to add hidden SSID WIFI network on first setup steps ("Select WiFi network" after selecting language), if there is no other visible WIFI networks in the range.
2. Still no silent mode, and still bug after restarting phone with volume level on 1 changes it to 0 (silent mode?). What if I want to use my ringer on level 1 volume?
3. No option to turn off automatic network change to mobile data when WiFi has no internet connection.
4. ART is slow on booting times after cleaning cache in recovery, or after flashing stock image, or after flashing custom ROMs, and when installing new apps, etc. Also it eats more space than dalvik. And after all it is not saving battery life or offers better performance (try to flash some kitkat ROMs after 5.x and you'll notice how fast your Nexus on dalvik).
5. Power saving's orange bars. Why orange? Why I can't change color? Why it changes to orange at all?
6. Still no reboot menu.
7. Still no option to clear all recent apps and no option to stop keeping them after reboot.
8. Very slow dialer app, especially when power saving is turned on. There is more than 3 seconds lasts before caller screen appears.
I'm sure there is still a lot of bugs and annoyances in the latest android. But I don't know why they're (Google) not fixing it. And not listening to customers. Android 5.1 just arrived - and ruined all hopes that many things will be better.
1. Cant help you there. It would be a good option. I do agree.
2. You do have silent mode. Its just implemented differently to allow for certain priority events (configurable)to occur which I personally like.
But it would be nice if they added a pure silent mode too.
3. For me, I simply turn off cellular data if I don't want it to switch to mobile data.
4. No argument there. But my N5 is fast enough its not really bothersome for me.
5. I guess orange so you are aware the mode is active? CM Themer can change the color in many custom ROM's (I think)
6. Agreed. This should be an option in stock Android. But for me, a custom ROM such as euphoria fixes the reboot shortfall.
7 Again I agree. This should be an option in stock Android. Custom ROM fixes this except no option to stop keeping them after reboot that I can find.
8. I guess its slow because battery saver has lowered your cpu in an attempt to extend battey . For me it is ok, life is full of tradeoffs.
Flying spaghetti monster. I'm so sick of people pitching about the new silent mode. I wish these people would stay on KitKat or switch to iPhone.
Is there anyway to fix number 3 with some app or module on xposed?
AndrasLOHF said:
Flying spaghetti monster
Click to expand...
Click to collapse
LOL dude.
Pastafarians ~ LMAO
I learn something new here at XDA every day!
krugdenis said:
1. On 5.1 there is still no option to add hidden SSID WIFI network on first setup steps ("Select WiFi network" after selecting language), if there is no other visible WIFI networks in the range.
2. Still no silent mode, and still bug after restarting phone with volume level on 1 changes it to 0 (silent mode?). What if I want to use my ringer on level 1 volume?
3. No option to turn off automatic network change to mobile data when WiFi has no internet connection.
4. ART is slow on booting times after cleaning cache in recovery, or after flashing stock image, or after flashing custom ROMs, and when installing new apps, etc. Also it eats more space than dalvik. And after all it is not saving battery life or offers better performance (try to flash some kitkat ROMs after 5.x and you'll notice how fast your Nexus on dalvik).
5. Power saving's orange bars. Why orange? Why I can't change color? Why it changes to orange at all?
6. Still no reboot menu.
7. Still no option to clear all recent apps and no option to stop keeping them after reboot.
8. Very slow dialer app, especially when power saving is turned on. There is more than 3 seconds lasts before caller screen appears.
I'm sure there is still a lot of bugs and annoyances in the latest android. But I don't know why they're (Google) not fixing it. And not listening to customers. Android 5.1 just arrived - and ruined all hopes that many things will be better.
Click to expand...
Click to collapse
well first of all none of the things you mentioned fall in Bug category.
second all options you asked for were never be on stock rom and never will be...stock android remains as simple as Google wants ..if you need other options use custom roms with their bugs/problem !
3rd we moved on from Kitkat and we are Ok with some difference in Lollipop...this is not Crappy iOS or Laggy Touchwiz who always looks same & have same funtions ...you are not Ok with it stay on Kitkat , No one if forcing you ! or Buy device with one of those -_-
Finally don't start thread for only giving your opinions or desires or well known things ...there are thousands of nexus 5 owners on XDA , imagine what will happen if all of them will do same as you ! ( we already have 5.1 discussion thread you could have place your so called "bug list " there ! )
4g lte
in italy,with vodafone, the phone does not connect more in 4g but only in 3g / h.
before 5.1 (with 5.0.1) everything was ok
AndrasLOHF said:
Flying spaghetti monster. I'm so sick of people pitching about the new silent mode. I wish these people would stay on KitKat or switch to iPhone.
Click to expand...
Click to collapse
LOL. If you didn't know what is true silent mode, here is an explanation: http://forum.xda-developers.com/showpost.php?p=59333086&postcount=85 :laugh:
jineshpatel30 said:
well first of all none of the things you mentioned fall in Bug category.
second all options you asked for were never be on stock rom and never will be...stock android remains as simple as Google wants ..if you need other options use custom roms with their bugs/problem !
3rd we moved on from Kitkat and we are Ok with some difference in Lollipop...this is not Crappy iOS or Laggy Touchwiz who always looks same & have same funtions ...you are not Ok with it stay on Kitkat , No one if forcing you ! or Buy device with one of those -_-
Finally don't start thread for only giving your opinions or desires or well known things ...there are thousands of nexus 5 owners on XDA , imagine what will happen if all of them will do same as you ! ( we already have 5.1 discussion thread you could have place your so called "bug list " there ! )
Click to expand...
Click to collapse
So, when device can't connect to hidden wifi on first run, it's not a bug, it's feature?
Or, when device volume set to 1 and after reboot it becoming completely silent, it's feature too? No bugs on stock Android?
You people complain about these "you-can-live-without" issues. Haven't you seen the 5.1 changelogs? It has 14,694 commits. Again, 14,694! Most of them are of MEMORY LEAK bugs and other necessary optimizations to make the phone usable at the moment. Then you'll complain about not having that silent mode? Dalvik won't consume that much if you remove some bloatwares. Then the orange status and navi bars coz of the battery saving mode? Seriously?! Can't you find more serious bugs than that?
krugdenis said:
So, when device can't connect to hidden wifi on first run, it's not a bug, it's feature?
Click to expand...
Click to collapse
I never used hidden SSID on android so i don't know what problem is occurring to you and i also don't know whether older verson like 4.4.4 was wroking with it or not.
I use MAC restricted WAP2 and it connected without problem in 1st bootup
Btw why you are using hidden SSID ? More security ? Then here you Go if any other reason tjen you should probably ask other user using SSID about this
Or, when device volume set to 1 and after reboot it becoming completely silent, it's feature too? No bugs on stock Android?
Click to expand...
Click to collapse
I justs checked it and this is not happening to me , it stays on 1 after reboot also.....so may be something wrong with your device you should try factory reset if you didn't already
Real annoyances I have on stock 5.1:
1. Name of provider above data toggle in quick settings randomly dissapears
2. After phone restart there is allways "No internet connection" warning in Google app
3. Scrolling bug is really there
4. And I still don't now, how the h*** you integrate updates of system apps into rom

notification fix

OK guys I hope this hasn't already been covered but here goes anyway. I have found this fix for notifications not arriving when doze is enabled. Iff you go into the particular app e.g what's app then into data usage you must select the following settings see pic below. then all the notifications will arrive straight away regardless of doze state.
sam00561 said:
OK guys I hope this hasn't already been covered but here goes anyway. I have found this fix for notifications not arriving when doze is enabled. Iff you go into the particular app e.g what's app then into data usage you must select the following settings see pic below. then all the notifications will arrive straight away regardless of doze state.
Click to expand...
Click to collapse
Yes that seems to be the problem. I had made a post months ago. It's very hidden feature by Lenovo and I think it's wrong to pre-restrict all background data. User should decide what to do.
I think they lenovo did it to block unnecessary data usage but i agree it is not needed and people are thinking their is something wrong with their phones.
Thanks for the tip
Thanks Sam, I saw this on the JJ review of Nougat. Is this for Nougat as my MM P2 settings don't look like the screenshot.
Sent from my Lenovo P2a42 using Tapatalk
Hi yes it is for Nougat the comment posted on JJs review regarding this fix was posted by me also.
Confusing settings these as the first one makes it look like enabling the "Restrict background data" option will disable background data, when in fact it does the opposite. You need to have both of these options enabled so the sliders are green, then you need to open Settings > Power Manager > Battery Optimization
Then you need to search for the apps that you need to fix notifications and change the option so it says "Don't optimize". Then the phone won't 'helpfully' close the app when the phone has been unused for a long time. This is why notifications are stopping.
precisely i agree quite confusing it took me a while i had to get a friend to send me whats app messages continuously untill i figured all this out but im glad i finally did.
If you make the changes to fix the notifications, shut down and power the phone back on rather than do a reboot. The settings don't seem to work until the phone has properly rebooted.
Is it worth noting that elsewhere it's stated that turning off doze altogether (using ADB) might be a saner option? Consensus seems to indicate it's basically a curse with little value, and that would certainly hold water in light of the battery capacity of the P2.
https://forum.xda-developers.com/lenovo-p2/help/regretting-purchase-t3611968
I think the following helps. Credit goes to JasonMR and manototh (Taken from oneplus.net forum)
JasonMR
KitKat
JasonMR, Nov 2, 2016 :
Guys, to avoid having to run the ADB command after each reboot follow these instructions (please note, the files should be downloaded to a PC and then transferred to your phone via USB otherwise they mess up sometimes):
You need to enable USB debugging mode in Developer options first
Download and install this apk and transfer it to your phones storage - https://drive.google.com/file/d/0BxD...w?usp=drivesdk
Then connect phone to PC and allow the drivers to install
Download and install ADB here - https://drive.google.com/file/d/0B0M...ljU2NPR0k/view
Go into the ADB folder, hold shift, right click and select "Open command prompt here"
Type the command: adb devices (now hit enter)
It should return your phones serial number is connected correctly
Run this command in ADB: adb -d shell pm grant com.adamioan.scriptrunner android.permission.DUMP (now hit enter)
Download this file and transfer it to your phones storage - https://drive.google.com/open?id=0Bx...VA4YmxGTS1OX3c
Open the SH Script runner app and tap the three dots in the top right corner, select "Load" and locate the file from teh previous step
Click the Circle button with the play sign at the top of the screen
You should see the message "Idle mode disabled" which means that Doze has now been disabled.
Whenever you reboot your phone, open the SH Script runner and the command will still be there, just click the play button to run the script again.
And that is it, two clicks to disable Doze after each reboot.
Full credit to manototh for putting this together originally.
Doze does not need disabling iff you follow my advice in the initial post i have tried and tested this and can confirm it works fully.
This is really frustrating. No matter what settings I use I still don't get notifications after a while. I don't want to go modifying my phone, can someone post a step by step if they have it working properly?
Spacedog79 said:
This is really frustrating. No matter what settings I use I still don't get notifications after a while. I don't want to go modifying my phone, can someone post a step by step if they have it working properly?
Click to expand...
Click to collapse
Follow my ordinal post and also go into battery optimisation and disable optimization for things like sms eggs what's app Facebook etc all the things you need notifications for should be disabled from sleep mode under battery optimization.
Like this
sam00561 said:
Like this
Click to expand...
Click to collapse
Yes thats exactly how I've done it. I've also tried every combination of settings under Apps for Unrestricted data usage.
And also the setting here
sam00561 said:
And also the setting here
Click to expand...
Click to collapse
Yep doesn't work either.
Perhaps your only option left is to try the disable doze app which has worked for many people but it's a paid app.
Just to update it does seem to be working properly now. I'm not 100% sure but I think turning the phone all the way off and on again instead of rebooting with the settings correct had the desired effect.

My phone's stock firmware broke my power button

Hello everyone. I would like to know if anyone experienced this, and if anyone has a solution (or at least an idea why).
The power button of my Samsung Galaxy A7 (2018) (SM-A750G) phone does not work at unlocking the screen (if it works in the rest of the functions such as opening the shutdown menu, entering recovery, etc.) when I am using stock firmware, but it works perfectly when using a GSI or any other custom OS.
Do you have any idea what could happen? It should be noted that this happened to me when my phone had the stock firmware and I had never modified my equipment at all... It just happened suddenly and for that reason I switched to a GSI. But now I would like to use the stock firmware, but I will not be able to do it with this "bug".
Thanks 4 the help
You mean unlocking or just turning the screen on an unlocked phone?
The app DoubleTap does away with using any buttons to turn the screen on/off. Simply 2x tap it. https://play.google.com/store/apps/...apk&pcampaignid=APPU_1_oD7zX7-SMMvesAWsh5_ADA
blackhawk said:
You mean unlocking or just turning the screen on an unlocked phone?
The app DoubleTap does away with using any buttons to turn the screen on/off. Simply 2x tap it. https://play.google.com/store/apps/details?id=com.vinance.lockdown&hl=en_US&gl=US&referrer=utm_source=google&utm_medium=organic&utm_term=double+tap+apk&pcampaignid=APPU_1_oD7zX7-SMMvesAWsh5_ADA
Click to expand...
Click to collapse
I mean turning on a phone screen. Since if it allows me to unlock it, but not turn it on.
P.S: I did not know the app you mention (it did not occur to me to look for something like that XD) I will try it, thanks for the link
gsosacristian said:
I mean turning on a phone screen. Since if it allows me to unlock it, but not turn it on.
P.S: I did not know the app you mention (it did not occur to me to look for something like that XD) I will try it, thanks for the link
Click to expand...
Click to collapse
That's strange. Have you tried remapping the button? Are there options to do so in settings?
Possibly another 3rd party apk remapped without you being aware of it?
I been using this app for over a year. To spite the ad warnings, it has none. Uses almost zero battery, never connects with the internet and is rock solid stable. Saves button life just keep the screen pointed away from your flesh when in your pocket to avoid accidentally taps.
Note: I never gave it administrator privileges as I never use a lock screen. So not sure about its behavior in that mode of operation.
blackhawk said:
That's strange. Have you tried remapping the button? Are there options to do so in settings?
Possibly another 3rd party apk remapped without you being aware of it?
I been using this app for over a year. To spite the ad warnings, it has none. Uses almost zero battery, never connects with the internet and is rock solid stable. Saves button life just keep the screen pointed away from your flesh when in your pocket to avoid accidentally taps.
Note: I never gave it administrator privileges as I never use a lock screen. So not sure about its behavior in that mode of operation.
Click to expand...
Click to collapse
I tried the app a few moments ago and it seems to work fine, the flesh thing is apparently configurable (assign the volume key, which is the most similar).
Regarding the mapping or 3rd party apks using the button, I see it almost impossible, not only because I don't use any app of this type (that reassigns keys) but in completely clean installations of stock firmware this happens to me (and I don't have any option key remapping that I know of).
It's very weird, at least for me. Because not only does it "break" to unlock, but it is only with stock firmware and even if I change the kernel (I tried using the quantum kernel) the key does not work when turning on the screen. But with the GSI it works without problems.
I even googled questions related to Always in display, power or something similar and nothing, there seems to be no conflicts.
gsosacristian said:
I tried the app a few moments ago and it seems to work fine, the flesh thing is apparently configurable (assign the volume key, which is the most similar).
Regarding the mapping or 3rd party apks using the button, I see it almost impossible, not only because I don't use any app of this type (that reassigns keys) but in completely clean installations of stock firmware this happens to me (and I don't have any option key remapping that I know of).
It's very weird, at least for me. Because not only does it "break" to unlock, but it is only with stock firmware and even if I change the kernel (I tried using the quantum kernel) the key does not work when turning on the screen. But with the GSI it works without problems.
I even googled questions related to Always in display, power or something similar and nothing, there seems to be no conflicts.
Click to expand...
Click to collapse
Make sure there's no remapping options for it in settings. If so it may be buried or under accessibility options... I've seen hidden Sammy drop down menus with no indication they are there until you double tap the top label. Swell.
Or simply bypass and double tap it!
blackhawk said:
Make sure there's no remapping options for it in settings. If so it may be buried or under accessibility options... I've seen hidden Sammy drop down menus with no indication they are there until you double tap the top label. Swell.
Or simply bypass and double tap it!
Click to expand...
Click to collapse
hehe, if it is true that there are really hidden things XD
Anyway, I am testing this app and if I see that it works I will be encouraged to install the stock firmware and by the way I will try to dig deep into the configuration in search of an option that I have overlooked
blackhawk said:
Make sure there's no remapping options for it in settings. If so it may be buried or under accessibility options... I've seen hidden Sammy drop down menus with no indication they are there until you double tap the top label. Swell.
Or simply bypass and double tap it!
Click to expand...
Click to collapse
Update:
I have installed the stock firmware and used the app you recommended, but no results: / The same thing keeps happening.
I have checked the accessibility options and there is nothing blocking the button :O
gsosacristian said:
Update:
I have installed the stock firmware and used the app you recommended, but no results: / The same thing keeps happening.
I have checked the accessibility options and there is nothing blocking the button :O
Click to expand...
Click to collapse
You enabled the appropriate buttons in it's settings?
I'm running Pie; it may not be compatible with 10 and up because of the overlay crap.
blackhawk said:
You enabled the appropriate buttons in it's settings?
I'm running Pie; it may not be compatible with 10 and up because of the overlay crap.
Click to expand...
Click to collapse
Oh! There is the problem, the firmware is Android 10
Bad luck for me, it will be time to return to a GSI momentarily XD
gsosacristian said:
Oh! There is the problem, the firmware is Android 10
Bad luck for me, it will be time to return to a GSI momentarily XD
Click to expand...
Click to collapse
Can't verify that but suspect it... Q sucks.
Lol, Google wants to protect you... I feel safer already. Not.
gsosacristian said:
Hello everyone. I would like to know if anyone experienced this, and if anyone has a solution (or at least an idea why).
The power button of my Samsung Galaxy A7 (2018) (SM-A750G) phone does not work at unlocking the screen (if it works in the rest of the functions such as opening the shutdown menu, entering recovery, etc.) when I am using stock firmware, but it works perfectly when using a GSI or any other custom OS.
Do you have any idea what could happen? It should be noted that this happened to me when my phone had the stock firmware and I had never modified my equipment at all... It just happened suddenly and for that reason I switched to a GSI. But now I would like to use the stock firmware, but I will not be able to do it with this "bug".
Thanks 4 the help
Click to expand...
Click to collapse
It seems like I have a similar problem. Do you have any recommendations ROM for SM - A750GN?
droidz94 said:
It seems like I have a similar problem. Do you have any recommendations ROM for SM - A750GN?
Click to expand...
Click to collapse
Personally, the one that I liked the most (and the one that works best) is the Google official (Android 10): https://developer.android.com/topic/generic-system-image/releases But one problem is that it is very outdated.
Anyway, here is a list of some GSIs that you can check and test which one works on your device: https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
And here is a tutorial that worked well for me to install GSI: https://forum.xda-developers.com/t/guide-workings-gsi-best-treble-gsi-roms-for-a7-2018.4069121/
gsosacristian said:
Personally, the one that I liked the most (and the one that works best) is the Google official (Android 10): https://developer.android.com/topic/generic-system-image/releases But one problem is that it is very outdated.
Anyway, here is a list of some GSIs that you can check and test which one works on your device: https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
And here is a tutorial that worked well for me to install GSI: https://forum.xda-developers.com/t/guide-workings-gsi-best-treble-gsi-roms-for-a7-2018.4069121/
Click to expand...
Click to collapse
Thanks! I'll try that
EXACTLY same problem here. I will not repet your words, I'll just say you described EXACTLY what is happening with my phone, a Galaxy A7 2018 (128GB RAM, Brazilian model - A750G/DS).
I can confirm that:
1 - Problem of screen never turning on after being turned off for the first time happens at all stock ROMs. Tried at android 10, downgraded to 9, couldn't downgrade to 8 because odin would not write the image, but the problem persisted on ALL stock ROMs up untill now.
2 - Problem DOES NOT happen at the TWRP recovery. Flashed TWRP just now, so I can flash a GSI, and I can turn the screen on or off as many times as I wish at TWRP screen, without any problem.
These informations corroborate, almost without a shadow of doubt, the idea that this is actually a software problem, not a hardware one. I'm gonna flash the google 10 GSI now, with quantum kernel V3 (seems to be a requirement, I would like to make as litle changes as possible) and post the results.
Having a hard time installing the GSI, gets stuck at bootloop all athe time...
joaodalvi said:
Having a hard time installing the GSI, gets stuck at bootloop all athe time...
Click to expand...
Click to collapse
[GUIDE][A-ONLY][A750x] Guide on How to flash GSI (Updated: 10.06.2019)
I'm not responsible for whatever damage this could possibly cause to your device. If you appreciate the work i have done, Feel free to buy me a cup of coffee @paypal Welcome to GSI For Galaxy A7 2018 ONLY FOR A750F/A750FN/A750GN Some...
forum.xda-developers.com
Try this. You need flash a "GSI Boot Fix" to use a GSI on A750.

Categories

Resources