Related
So now that the gingerbread roms have been out for a while, I'm very tempted to go ahead and flash one, however I'm seeing a lot of the roms are still in beta.
I'd like to know what are some known issues that i should be aware of.
Stability and battery life is very important. I'm currently still running Continuum v4.
What known issues are there with the gingerbread roms and any pros and cons of it compared to a froyo rom other than the obvious?
Personally I have had stability issues with all the GB ROMs (that I tried). Random freezes, and reboots. I experienced this with continuum, GR, Perception and Mosaic. I will say Mosaic was the best for me. But it was running TW 3, so it felt like FroYo but a little slower and buggier. GR and Perception are running TW 4, which is much nicer, but still very beta. I feel Perception is much more stable than GR-12. But even so, I get a freeze that requires a reboot after almost every 2 hours of use.
As far as battery, there is definately a charging issue. If you leave it charging after full, when you unplug you get a big drop. I tried all the FroYo calibration tricks, it they don't seem to work. I say this with a grain of salt. I haven't stayed on the same ROM for more than a few days. So I haven't given it much time to learn before I flashed a new ROM.
Its been a fun week using GB, but I think I am going back to FireFly until the ROMs lose the "beta"
Sent from my Captivate running Perception IIb3
Yes, there is a charging issue for some, but not all. Battery life (once charged) is unreal. I have found the roms I've used to be very stable. Juwe's, Continuum betas 1-3 and RC3 were great(missed rc1 and 2 while trying juwe's because of charging issue). C5.1 and 5.3 have been great also.
As with any rom, read read, and read some more before attempting a GB rom. Ask questions, use search, know exactly what you have to do. Also, have a jig (just in case). If you are one that doesn't have 3 button fix, read ALOT about that in regards to GB.
Good luck.
I've been on MikeyMike's GR-12 and talondev's kernel and have been doing farely well. Everything will have it's instabilities, but so far I've only noticed a couple of things (tips and otherwise):
1. be careful about which apps and stuff you restore from TiBu or others; LauncherPro was causing alota FC's with the new rom
2. be sure to read the WHOLE OP in whichever ROM you're flashing, since (though I'm sure you know this, just making sure) GR requires new bootloaders. Also, if you're flashing back to stock 2.1 you need to use one-click odin and not three-button fix.
3. I've read about charge-death/issues, but I haven't had much problem with that.
4. At least for the rom I'm using, the ambient light sensor seems to freak out sometimes.
5. also I don't think there is automatic ext4 conversion. Most roms just use rfs and give you an option of converting with an app. Some roms require you to reconvert back to rfs before flashing a new update or something.
PROS:
1. Touchwiz 4 (it's pretty nice, though still not as feature-filled as custom launchers)
2. GPS has been GREAT for me since upgrading to GR. not sure if this is common (also my gps on stock was horrid)
3. Smooth even without ext4 or OC.
Note I haven't tried alot of GR roms (did for froyo) so my experience in terms of diversity is rather limited. But as the above posts say, READ EVERYTHING.
As long as you're not going to be away from your computer for a long time, I'd say take a plunge.
glhf =)
The only real issue I've experienced is some problem pertaining to broadcom and the gps. You'll notice logcat flooded with this:
E/GPS ( 129): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(e
rrno = 2)
I/GPS ( 129): [gps_state_done][line = 293] : successfully called
E/GPS ( 129): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(e
rrno = 2)
I/GPS ( 129): [gps_state_done][line = 293] : successfully called
E/GPS ( 129): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(e
rrno = 2)
I/GPS ( 129): [gps_state_done][line = 293] : successfully called
E/GPS ( 129): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(e
rrno = 2)
I/GPS ( 129): [gps_state_done][line = 293] : successfully called
E/GPS ( 129): [gps_lcsapi_init][line = 442] : Failed to call BrcmLbs_init(e
rrno = 2)
I/GPS ( 129): [gps_state_done][line = 293] : successfully called
It's pretty annoying, but I don't know whether it has any sort of impact on battery life or gps performance.. at least, I haven't noticed any.
So far I would have to say the light sensor being a problem when trying to make a call.....but other then that battery life on GB is amazing compared to Froyo! In my opinion the GB Roms are fine for daily use!
Darky's V10.0
And you will never look back.
I"ve gotta say I've been using Darky's for the last week and it's been damn amazing. Had used Continuum before that.
I haven't had any charging problems on any of the roms I've tried. I only had one weird install where things didn't work right, and a quick factory reset and reflash seemed to work just fine.
Try the GR-11. Been using it over like a week to two weeks now (over 80 hours since last reboot), and been pretty stable. All the needed features like wifi, bluetooth, etc are working. And battery life on this ROM is better than 2.2 ROMs I have used.
I've been running Continuum 5.3 and it's been stable and fast for me.
I've been running both Continuum and Mosaic. I have had no real issues whatsoever. I haven't had the charge issue that others are reporting, lag issues that others are reporting or any other issues.
I consider myself lucky but I am glad that I upgraded to GB. For one, it makes flashing easier as I haven't had to go back to stock which means no messing with bootloaders and possibly bricking my phone. Two, I feel my phone is much faster than it was on Froyo or Eclair and three, my battery life has actually been better.
I'm glad I did the upgrade and have been happy with my phone again. However a word of caution. Going to GB has some steps that cannot be taken lightly. Please make sure you really research these steps and read as much as you can. If you aren't comfortable with what these steps are, you are only asking for trouble. If you understand them and follow them exactly, you should have no problems.
Good luck!!
Getting major battery drain. I know its not the rom im running as ive read people getting 15 hours+ on tweak stock . So im thinking this has to be app related. Only problem is I've read spare parts doesn't work on gingerbread. I need to view partial wake usuage. Any ideas fellas? I want to track down whats causing this.
Sent from my SCH-I510 using XDA App
Download CPU spy from the market. See if you are in deep sleep most of the time.
Sent from my SCH-I510 using XDA App
Ok ill try that
Update:
Says 42% deep sleep
Sent from my SCH-I510 using XDA App
Why do you need spare parts to view battery stats? What is wrong with going to settings/about phone/battery use?
I want to see whats running while phone is sleeping
Sent from my SCH-I510 using XDA App
luis86dr said:
Ok ill try that
Update:
Says 42% deep sleep
Sent from my SCH-I510 using XDA App
Click to expand...
Click to collapse
If you are using your phone about half of the time it is on, then that is your problem.
If not, then you have a rogue app that is running in the background and actively using the cpu, preventing it from sleeping and destroying your battery life. The best bet would be to back up your apps and then go to your favorite task killer (not the stock one) (i like the running tab of go launcher's app drawer). Don't auto kill, but uninstall apps that are always running that you suspect are draining your battery. Common culprits are games with notifications and social apps. Also look for something you recently installed, starting from when you noticed the battery problem.
Sent from my SCH-I510 using XDA App
I use my phone most of the time its on
Sent from my SCH-I510 using XDA App
Are you in a low signal area? Are you leaving GPS on?
Sent from my SCH-I510 using xda premium
luis86dr said:
I use my phone most of the time its on
Sent from my SCH-I510 using XDA App
Click to expand...
Click to collapse
What percent of your battery is being used by the screen (settings -> about phone -> battery use)? If it is high then your battery life is normal for your usage.
I get full bars at all times in my area. Gps is always off unless I use navi. Downloaded better battery stats. Not showing any apps acting up. Going to try a battery calibration.
Sent from my SCH-I510 using XDA App
How many power cycles have you gone through since flashing? Did you odin or CWM flash? Did you do a data wipe before flashing, and were you (relatively) fully charged at the time of flashing? Just as some food for thought - In my experience it seems that sometimes things take a bit of time to settle battery-wise after flashing.
Use this app to figure out what's keeping your phone from sleeping.
http://forum.xda-developers.com/showthread.php?t=1179809
Go to the first page, there is a free xda version for download.
Reflashed at 100% thru CWM and drained down battery after deleting batterystats.bin. Charged it back up so far no drain. Usually as soon as I take it off charge it will drop to 99 within 5 minutes. Gonna give it some more cycles. Thanks.for all your input guys.
Update:
Like I said everything looks normal according to betterbatterystats. Heres dump file info:
Wakelocks
=========
ActivityManager-Launch (Android System): 38 s (38 s) Count:74 2.4%
JuiceDefender.Service (JuiceDefender): 27 s (27 s) Count:127 1.7%
*network-location* (Android System): 16 s (16 s) Count:80 1.0%
*network-location* (Google Services): 14 s (14 s) Count:27 0.9%
RILJ (Dialer): 10 s (10 s) Count:19 0.6%
AlarmManager (Android System): 7 s (7 s) Count:260 0.5%
GTALK_ASYNC_CONN (Google Services): 5 s (5 s) Count:3 0.4%
*network-location* (com.boatbrowser.free.Boat Browser): 5 s (5 s) Count:2 0.3%
WakeLock.Local (com.netqin.mobileguard.Android Booster): 5 s (5 s) Count:54 0.3%
*sync* (com.google.android.gm.Gmail): 4 s (4 s) Count:2 0.3%
PowerAMP scan (UID): 3 s (3 s) Count:6 0.2%
WifiService (Android System): 2 s (2 s) Count:147 0.1%
sleep_broadcast (Android System): 1 s (1 s) Count:102 0.1%
NetworkLocationLocator (com.google.android.apps.maps.Maps): 1 s (1 s) Count:2 0.1%
GmailProviderProviderChangedBroadcastWakeLock (com.google.android.gm.Gmail): 1 s (1 s) Count:3 0.1%
Sent from my SCH-I510 using XDA App
luis86dr said:
Getting major battery drain. I know its not the rom im running as ive read people getting 15 hours+ on tweak stock . So im thinking this has to be app related. Only problem is I've read spare parts doesn't work on gingerbread. I need to view partial wake usuage. Any ideas fellas? I want to track down whats causing this.
Sent from my SCH-I510 using XDA App
Click to expand...
Click to collapse
Spare parts does work- download it from the Market. Something I have found is that if you have a ROM that usually doesn't drain battery life but now yours is, then back up everything and wipe it all and start over carefully adding to it and monitoring it. I run InfinityROM and was getting great battery life and two days ago it seemed to get worse. Not sure exactly what I did, but I reflashed it and started with one thing at a time. ICS Fugu tweak, then V6 Supercharger and so on. Today I am still running it and its not dead. Yesterday it was dead in 3 hours. Hope this helps.
andrewjt19 said:
Spare parts does work- download it from the Market. Something I have found is that if you have a ROM that usually doesn't drain battery life but now yours is, then back up everything and wipe it all and start over carefully adding to it and monitoring it. I run InfinityROM and was getting great battery life and two days ago it seemed to get worse. Not sure exactly what I did, but I reflashed it and started with one thing at a time. ICS Fugu tweak, then V6 Supercharger and so on. Today I am still running it and its not dead. Yesterday it was dead in 3 hours. Hope this helps.
Click to expand...
Click to collapse
Might have to do this still draining too fast. On second charge cycle and still draining fairly fast. Not as bad.as before
Sent from my SCH-I510 using XDA App
Hi. I have an extended battery but it doesn't last long at all. I used better battery stats and I noticed I have tons of wakelocks from things like "Alarm Manager" (2822 wakelocks), "keyguardWakeAndHandOff" (2363 wakelocks), "SCREEN_FROZEN" (2333), "sleep_broadcast" (2307), "ActivityManager-Launch" (2224), "LocationManagerService" (2154), "LocationManagerService" (2154), and "RILJ" (451).
With the exception of RILJ, they all fall under the category of "Android System", and RILJ falls under "dialer".
Honestly I have no idea what any of these names refer to. Betterbatterystats doesn't give you any options to disable or freeze these processes. Googling them leads to unanswered or incomplete threads. The creator of BBS tells someone who asked about "RILJ" to "search the thread". Except there's *nothing in the godawful thread*. I searched every one of those stupid piece of garbage 150+ pages (now it's at 250+). Someone late in the thread mentioned he did the same as well, and the app creator says "just google it". Well I tried, and it didn't help. No solution comes up. Thanks bud.
I've also used "Battery Monitor Widget" to determine mA drain during sleep, and I'm getting anywhere between 20-150 mA. Only once did I get 2 mA. Nowadays sometimes it sleeps at 20-50 mA, other times it's above 100. Sometimes it fluctuates. It's ridiculous.
I've tried infinity, Tweakstock, OTA stock rooted/non-rooted, and now I'm back on Infinity again. It's quite disheartening. Without the extended battery this phone would be little better than a paperweight.
Worst of all is when I look at my mom's iPhone, and see how it doesn't even need to be charged for several days. Granted my mom hardly uses it, but standby is perfect on the device. My battery is almost as big my mom's phone, and yet hers lasts longer. Sigh.
What's most frustrating IMO is that Google doesn't acknowledge any of this. Even on ICS GNEX users seem to have similar problems. It reminds me of the text resizing issue on Chrome. They just ignore everyone who complains about it.
The iphone inherently has better battery life because there is no multitasking. When you back out of an app, it freezes it, so there can't be any apps running in the background.
Sent from my SCH-I510 using XDA App
JihadSquad said:
The iphone inherently has better battery life because there is no multitasking. When you back out of an app, it freezes it, so there can't be any apps running in the background.
Sent from my SCH-I510 using XDA App
Click to expand...
Click to collapse
I've read some about iOS 5's multitasking, and it's not that simple. iOS limits programs that would like to run in the background with the Background API... very specific processes that iOS deems worthy of running incessantly in the background. Everything else can request 10 minutes of runtime, after which iOS forcibly shuts them down.
Google gives developers far more freedom, but with ICS they've enabled a "destroy every activity" option that limits background processes if you leave the program. In other words until ICS "stopping" a program might not actually stop a misbehaving program. This is obviously a problem because a lot of developers are terrible at managing battery life. It's not just the manufacturers and carriers with their ugly bloatware... Google themselves is guilty of this (I'm looking at you Google Maps).
You'd think Android would give users the option to enable an iOS-like environment to manage their battery life, but iOS is written in a way that the OS doesn't go bonkers when it forcibly suspends greedy programs. So instead on ICS all of that babysitting is left to us users rather than the OS.
On Gingerbread it personally feels more like constructing a building out of individual atoms.
One day I'm sure Google will get it right and I'll be able to wave my phone at an iPhone user and give off a Simpsons-like "Ha ha!" But not yet.
Try xda power user..great way to tweak phone settings.
ambrar12 said:
Worst of all is when I look at my mom's iPhone, and see how it doesn't even need to be charged for several days. Granted my mom hardly uses it, but standby is perfect on the device. My battery is almost as big my mom's phone, and yet hers lasts longer. Sigh.
Click to expand...
Click to collapse
Usage is a helluva drug.
KozmiKKernel
Features:
Max Possible OC Freq set at 1890
TUN - Module Built in.
Added VR, SIO, and BFQ I/O Schedulers in addition to the standard NOOP,CFQ,and DEADLINE.
AROMA setup - showp1984 - Removed until I get this setup completely
Faqs:
Should be compatible with any rooted ICS sense rom.
As with anything you flash to your phone there is always a risk. You are taking responsibility into your own hands when you flash this. It works perfectly on my phone but your hardware may not be able to withstand overclocking. It should work fine but don't complain if it breaks your phone.
Beta Downloads:
Beta 1b
Beta 1a
Beta 1
Installation:
This should be flashable for both s-off and s-on devices through your custom recovery.
CPU Frequency / Voltage Table:
Code:
384000: 850000
432000: 875000
486000: 875000
540000: 900000
594000: 900000
648000: 925000
702000: 925000
756000: 975000
810000: 975000
864000: 1000000
918000: 1000000
972000: 1025000
1026000: 1025000
1080000: 1050000
1134000: 1050000
1188000: 1075000
1242000: 1075000
1296000: 1100000
1350000: 1100000
1404000: 1125000
1458000: 1125000
1512000: 1150000
1566000: 1150000
1620000: 1175000
1674000: 1175000
1728000: 1200000
1782000: 1200000
1836000: 1225000
1890000: 1225000
Change Log:
Beta 1a/b
Removed LIFO scheduler
Fixed voltage issue in acpuclock for two two frequencies.
Set max clock setting to 1890
Beta 1
Initial Test Release
May or may not work
Credits:
klquicksall
Virtuous Dev Team
showp1984
Faux123
Chad0989
LeeDroid
Rafyvitto
HTCDev
amarullz - aroma installer
And many more...
Github:
My Source
Git Changelog:
Code:
********************************
**************Beta 1************
********************************
6858cd9 was Tim Nelson, 11 minutes ago, msg: kozmik_defconfig-Beta-1
7aa30dc was Tim Nelson, 18 minutes ago, msg: board-ville-regulator.c-Increasing-Max-voltage-to-1350
819fdf9 was showp1984, 10 weeks ago, msg: include-linux-filter.h-fix-missing-rcupdate.h-include
765169f was Tim Nelson, 31 minutes ago, msg: rpm-8960.h-Increasing-Max-voltage-to-1350
85d009b was Harsh Bhanvadia, 6 weeks ago, msg: Implementation-of-SNAPPY-for-zram-kernel-3.0.y
1815f49 was Peter Donka, 7 weeks ago, msg: Google-snappy-compression-decompression-support
53ee66b was Miguel Boton, 2 years, 7 months ago, msg: Add-support-for-previous-kernel-versions
357c63c was Miguel Boton, 2 years, 7 months ago, msg: LIFO-I-O-scheduler-v1.0
b385ff0 was Miguel Boton, 7 weeks ago, msg: Add-support-for-previous-kernel-versions-Miguel-Boton
e82cc43 was Dominic Duklas, 2 years, 1 month ago, msg: include-linux-slab.h-to-fix-missing-kfree
8114ec9 was Miguel Boton, 2 years, 5 months ago, msg: Improve-Kconfig-help-text
fcdd643 was Miguel Boton, 2 years, 5 months ago, msg: Fix-commentary
90198f4 was Miguel Boton, 2 years, 5 months ago, msg: Simple-I-O-scheduler-v0.2
8663c21 was Miguel Boton, 2 years, 5 months ago, msg: Simple-I-O-scheduler-v0.1
cd7a78e was Tim Nelson, 9 weeks ago, msg: adding-bfq-i-o-scheduling
a13418f was Ken, 2 months ago, msg: add-V-R-I-O-scheduler
b871d82 was Mircea Gherzan, 3 months ago, msg: ARM-net-JIT-compiler-for-packet-filters
194359d was Ashwin Chaugule, 3 months ago, msg: Optimized-ARM-RWSEM-algorithm
5761341 was Miao Xie, 3 months ago, msg: lib-string-use-glibc-version
b2b33fa was Miao Xie, 3 months ago, msg: lib-memcopy-use-glibc-version
bf8e335 was faux123, 3 months ago, msg: sched-disable-GENTLTE_FAIR_SLEEPERS-for-better-performance-on-Android
a8f976d was LeeDrOiD, 2 months ago, msg: Make-vfs_cache_pressure-configurable
f7230ab was jdkoreclipse, 12 months ago, msg: include-mm-increase-readahead-buffer
3d98394 was jdkoreclipse, 8 months ago, msg: mm-adjust-vm-ratios
ea69088 was Tim Nelson, 51 minutes ago, msg: avs.h-changing-vdd-min-to-850-and-max-to-1350
a5c85b8 was SebastianFM, 3 months ago, msg: Fixed-cpufreq
3f3d0e1 was showp1984, 3 months ago, msg: htc-battery-core-Fixing-once-again.-srsly-htc-That-was-already-there-in-2.6.x
8b48b27 was Tim Nelson, 70 minutes ago, msg: acpuclock-setting-up-overlocking-tables-removed-krait-variants-and-consolid
78461bf was Tim Nelson, 2 hours ago, msg: Temp-Fix-wenum-compair-error-in-mdp4_overlay.c
e7807e5 was showp1984, 3 months ago, msg: fix-warning-statement-with-no-effect-2
95d8009 was showp1984, 3 months ago, msg: net-netfilter-remove-annoying-comparison-will-always-be-true-warning
fa6e567 was showp1984, 3 months ago, msg: fix-warning-statement-with-no-effect
a0eff76 was Tim Nelson, 3 hours ago, msg: Fixed-warning-fmt-may-be-used-uninitialized
a148a1b was Tim Nelson, 3 hours ago, msg: Fixed-warning-return-with-no-value
f362783 was Tim Nelson, 3 hours ago, msg: Fixed-warning-buddy-may-be-used-uninitialized
f119dfa was showp1984, 7 months ago, msg: O3-compilation-fixups
45404b9 was showp1984, 9 months ago, msg: Makefile-Added-Snapdragon-optimizations
210523f was showp1984, 5 months ago, msg: Makefile-adding-config-variable-for-Os-O2-O3-compilation
aa6cd98 was Tim Nelson, 4 hours ago, msg: Adding-toolchain-to-makefile
9d416c2 was showp1984, 5 months ago, msg: kernel-return_address-hiding-warning-TODO
0b8ca12 was James Sullins, 4 months ago, msg: fix-GCC-version-check-4.5.2-for-arch_extension-use
85bf2e8 was James Sullins, 5 months ago, msg: rework-gcc-version-check-for-.arch_extension-sec
a9a3478 was showp1984, 5 months ago, msg: scm-only-use-.arch_extension-sec-if-the-compiler-is-newer-than-gcc4.4
87f63d5 was showp1984, 6 months ago, msg: mach-msm-add-.arch_extension-sec-n-to-scm.c
25fcce6 was showp1984, 3 months ago, msg: arm-mm-fixing-offset.un-may-be-used-uninitialized-in-this-function
bd4b1a6 was Tim Nelson, 5 hours ago, msg: ville-u-ics-3.0.8-e2a40ab
Reserve
Here is the first build of my kernel. My device is won't be here for a week so this is a test build of beta 1.
It should work but I am currently not 100% positive as I have not tested it
I just noticed an error. I would advice not selecting the 1620 or 1674 frequency. It appears that I set them at 1750 for the voltage! Everything else looks fine. I'm rather tired. If someone wants to flash this and let me know if it works I'll get this fixed in the morning.
Once my device gets here I'll be working on this regularly. adjustable voltage table may wait until then. I did however add a few extra I/O schedulers for you guys in the mean time
Thanks for this. Do you have an option to set the max freq, if not which app is recommended? What about voltages?
Sent from my HTC One S using xda premium
Only Sense or Stock-derivated compatile?... I'm under CM9, I just wanted to know if it could be compatible (but I expect to be desapointed... lol)
Last but not least : Are all settings tunable with SetCPU ? (undervolt? max freq, schedulers?...)
Anyway, good job done! I'll test it as soon as I can
plakers said:
Only Sense or Stock-derivated compatile?... I'm under CM9, I just wanted to know if it could be compatible (but I expect to be desapointed... lol)
Last but not least : Are all settings tunable with SetCPU ? (undervolt? max freq, schedulers?...)
Anyway, good job done! I'll test it as soon as I can
Click to expand...
Click to collapse
This wont work on CM9, MIUI and AOKP, this is just for Sense based Roms.
But since the Kernel sources for our phones have been released we can expect a better kernel for AOSP roms and derived work to be released soon.
kozmikkick have you edited stock UV table with a low voltage?
Just installed on my T-Mo USA One S, and while installation seemed successful (via TWRP recovery), my wifi is now broken, and no new frequencies or governors are available.
Seems like nothing happened but the broken wifi.
Any ideas?
Serveral problems observed. WiFi seems broken after flashing your kernel. Secondly, unable to find any more I/O schedulers other than default ones. Please fix them asap.
Sent from my HTC One XL using Tapatalk 2
I see in the changelog you added some commits made by me time ago.
LIFO I/O scheduler should NEVER be used, never never never. It was just a joke scheduler I made.
Waninkoko said:
I see in the changelog you added some commits made by me time ago.
LIFO I/O scheduler should NEVER be used, never never never. It was just a joke scheduler I made.
Click to expand...
Click to collapse
That would make sense why I couldn't find any documentation on it. I'll remove it for sure.
Sent from my HTC One X using xda premium
I'll look into the WiFi issue. Can someone post a last_kmsg for this kernel?
Sent from my HTC One X using xda premium
I updated the OP with Beta 1a and 1b. They are both exactly the same with the exception of a small edit in acpuclock.
I also removed LIFO scheduler. I didn't notice that it was a prank and enabled it. Opps
And lastly I fixed the voltage issue on two of the frequencies. Max frequency should be set at 1890.
Let me know if Wifi works now and which one of beta 1a or 1b works best.
Without a reason, the recovery said installation aborted when installing the zip.
Using 1b zip!
fxzy said:
Without a reason, the recovery said installation aborted when installing the zip.
Using 1b zip!
Click to expand...
Click to collapse
Yea I've tried 1a 1b both fail to flash useing cwm and twrp. Have no issues flashing other kernals. Maybe its a partition issue
Sent from my HTC VLE_U using XDA Premium HD app
JDenson77 said:
Yea I've tried 1a 1b both fail to flash useing cwm and twrp. Have no issues flashing other kernals. Maybe its a partition issue
Sent from my HTC VLE_U using XDA Premium HD app
Click to expand...
Click to collapse
Probably an s-on issue. I'm going to rebuild a post a boot.IMG to flash with fastboot tomorrow.
Sent from my HTC One X using xda premium
Hey guys.
I've done a quick search from the XDA app and I'm not really able to find any specific details on this topic.
Currently running 5.1.9 with xXx rom and Franco Kernel, which means I'm getting spoilt for battery life with around 7+ hrs SOT!
The info that I've been able to find on Android P for OP6 generally seems to indicate around 2.5hrs SOT.
For anyone using the latest beta, can you please share your battery life? Whether it be screenshots or general experience?
The latest beta seems to be pretty stable, but this is the last thing that's stopping me from taking the plunge!
Also, from the research that I've done, custom kernels seem to work with the beta but it breaks wifi? Is this true or am I way off?
Thanks in advance
For me it's not as good as 5.1.9 with Franco or Flash kernel, but not as bad as 2.5hrs SOT, more like 5 or 6 but with a worse idle drain. I'm with xXx module, viper and I spend way too much time on Youtube...
But if I was you, I'd wait for the next preview since Google pushed the last one beta 10 days ago.
The battery life is bad on p compared to 5.1.9
.. Been running it for almost 2 weeks here. I get around 4-5 hours on p while I used to get around 6-7 on oreo
---------- Post added at 02:12 PM ---------- Previous post was at 02:12 PM ----------
The battery life is bad on p compared to 5.1.9
.. Been running it for almost 2 weeks here. I get around 4-5 hours on p while I used to get around 6-7 on oreo
JahSam said:
For me it's not as good as 5.1.9 with Franco or Flash kernel, but not as bad as 2.5hrs SOT, more like 5 or 6 but with a worse idle drain. I'm with xXx module, viper and I spend way too much time on Youtube...
But if I was you, I'd wait for the next preview since Google pushed the last one beta 10 days ago.
Click to expand...
Click to collapse
Oh true I didn't think about the new one.
In saying that I'm quiet impatient ?
5 or 6 is way better than I was expecting though!
Thanks for the replies!
For me battery life on Android P has been amazing, running it since 2 weeks now. SOT from 5 to 7 hrs. Clean flashed.
smashdroid said:
For me battery life on Android P has been amazing, running it since 2 weeks now. SOT from 5 to 7 hrs. Clean flashed.
Click to expand...
Click to collapse
Yeah I don't have an exact comparison between 5.1.9 and DP4 beta 3, but i would say it's almost the same.
Don't feel a big difference.
Edit: did a clean flash too.
Great thanks guys!
Anyone know about the kernel situation?
This is my 2nd pixel 3 xl, the first one had lag in lockscreen and some choppy animations when going from app to another. My replacement is better but not by much, there's still stutter here and there. Specially when pulling the most recent apps.
I'm very disappointed in this phone, I really tried to like it but at this price point this is really annoying. Looks like google did very sloppy work optimising this phone, specially that it comes with the snapdragon 845.
Google will probably release an update, but there's no guarantee that this will be fixed.
Anyone else experience these issues ?
Update:
So I picked up the iPhone XS today and installed all my google apps and managed to sync all my contacts. The difference in my experience when it comes to fluidity between the 3 XL and the XS is night and day. Everything runs so smooth without any hiccups. I’ve also noticed the screen is better to look at as it has a more pleasing colour temperature. I’m keeping the XL to see what the December update is going to address but for now, the iPhone is just in a different league.
Yes, I have occurences of lags here and there. I reboot my phone every morning to hopefully clean things out but it doesn't seem to help.
garyHal said:
Yes, I have occurences of lags here and there. I reboot my phone every morning to hopefully clean things out but it doesn't seem to help.
Click to expand...
Click to collapse
I've been doing the same, rebooting my phone here and there.
Glad to see someone else have something similar. Sorry for being mean. It's just when Ive made my threads or post about these it looked as it was dusted under a rug, noone would answer. This is my second XL and I think it's slower than my first. Buttons on the side work better tho. Even before I bought the phone I had concerns. Looked to me like Google made a half as$ product. It's also very interesting as I'm ok with all physical aspects of the phone, even okay with new gesture setup, I actually love it, it works for my use but speeds, snappyness and transitions those piss me off
Returning this one soon and ordered a new one with black Friday discount.
I'm sucking everything up for this. Camera, love it.
I run a custom kernel and the phone runs great! So, we know Google is working on the memory leaks and will release a fix soon, maybe even in a week.
Sent from my Pixel 3 XL using Tapatalk
Waiting for the day OnePlus makes a pixel phone ?
virtyx said:
Waiting for the day Google buys out OnePlus ?
Click to expand...
Click to collapse
Fixed it for you.
---------- Post added at 12:41 PM ---------- Previous post was at 12:41 PM ----------
virtyx said:
Waiting for the day Google buys out OnePlus ?
Click to expand...
Click to collapse
Fixed!
zetsumeikuro said:
Fixed it for you.
---------- Post added at 12:41 PM ---------- Previous post was at 12:41 PM ----------
Fixed!
Click to expand...
Click to collapse
thjey can seriously learn a thing or two from OP.
virtyx said:
thjey can seriously learn a thing or two from OP.
Click to expand...
Click to collapse
For sure! As for the double post XDA didn't show my post even minutes after I typed and submitted it RIP.
My 3XL is starting to do the same thing. It stutters and lags switching between apps and using the lock screen. Good to see I'm not the only having this issue and hopefully it's something they'll address with a hot fix.
virtyx said:
Waiting for the day OnePlus makes a pixel phone ?
Click to expand...
Click to collapse
Nodrod said:
My 3XL is starting to do the same thing. It stutters and lags switching between apps and using the lock screen. Good to see I'm not the only having this issue and hopefully it's something they'll address with a hot fix.
Click to expand...
Click to collapse
Looking forward to that update . I’ve seen some on reddit having the same issue.
I was also experiencing this issue. I rooted and changed the CPU Governor to performance and I haven't had the issue since so it's definitely something that is easily fixable
Mine lags, stutters, and becomes completely unresponsive at times. I think it is all due to Ram management. Things just completely crash as it's trying to clear everything out. I really hope they fix this. I didn't have this problem on my 2xl with the same amount of ram so it's surprising
Sent from my Pixel 3 XL using Tapatalk
virtyx said:
Waiting for the day OnePlus makes a pixel phone ?
Click to expand...
Click to collapse
Nodrod said:
My 3XL is starting to do the same thing. It stutters and lags switching between apps and using the lock screen. Good to see I'm not the only having this issue and hopefully it's something they'll address with a hot fix.
Click to expand...
Click to collapse
skw5115 said:
I was also experiencing this issue. I rooted and changed the CPU Governor to performance and I haven't had the issue since so it's definitely something that is easily fixable
Click to expand...
Click to collapse
Good to hear but does the battery take a hit at performance ?
malek777 said:
Good to hear but does the battery take a hit at performance ?
Click to expand...
Click to collapse
definitely
it makes all cores run at maximum.... not recommended can cause over-heating, etc
Mine with stock kernel + Magisk 17.3 seems to run out of memory a few times a day, requiring a reboot.
This is even after multiple reinstalls of Android with full format of sdcard.
Logcat attached.
Code:
11-26 10:19:23.718 840 840 I lowmemorykiller: Killing because cache 154232kB is below limit 221184kB for oom_adj 900
11-26 10:19:23.718 840 840 I lowmemorykiller: Free memory is -452kB below reserved
11-26 10:19:23.718 840 840 I lowmemorykiller: Unable to free enough memory (pages to free=80753, pages freed=0)
11-26 10:19:23.719 840 840 I lowmemorykiller: Killing because cache 155376kB is below limit 221184kB for oom_adj 900
11-26 10:19:23.719 840 840 I lowmemorykiller: Free memory is -1808kB below reserved
11-26 10:19:23.719 840 840 I lowmemorykiller: Unable to free enough memory (pages to free=81092, pages freed=0)
11-26 10:19:23.720 840 840 I lowmemorykiller: Killing because cache 153804kB is below limit 221184kB for oom_adj 900
11-26 10:19:23.720 840 840 I lowmemorykiller: Free memory is -164kB below reserved
11-26 10:19:23.720 840 840 I lowmemorykiller: Unable to free enough memory (pages to free=80681, pages freed=0)
11-26 10:19:23.723 840 840 I lowmemorykiller: Killing because cache 150856kB is below limit 221184kB for oom_adj 900
11-26 10:19:23.723 840 840 I lowmemorykiller: Free memory is 2488kB above reserved
11-26 10:19:23.723 840 840 I lowmemorykiller: Unable to free enough memory (pages to free=80018, pages freed=0)
11-26 10:19:23.734 840 840 I lowmemorykiller: Killing because cache 147676kB is below limit 221184kB for oom_adj 900
11-26 10:19:23.734 840 840 I lowmemorykiller: Free memory is 4412kB above reserved
11-26 10:19:23.734 840 840 I lowmemorykiller: Unable to free enough memory (pages to free=79537, pages freed=0)
11-26 10:19:23.735 8111 8111 I android.tasker: The ClassLoaderContext is a special shared library.
11-26 10:19:23.746 840 840 I lowmemorykiller: Killing because cache 152720kB is below limit 221184kB for oom_adj 900
11-26 10:19:23.746 840 840 I lowmemorykiller: Free memory is -256kB below reserved
11-26 10:19:23.746 840 840 I lowmemorykiller: Unable to free enough memory (pages to free=80704, pages freed=0)
11-26 10:19:23.747 840 840 I lowmemorykiller: Killing because cache 151736kB is below limit 221184kB for oom_adj 900
11-26 10:19:23.747 840 840 I lowmemorykiller: Free memory is 248kB above reserved
smallsmx301 said:
Mine lags, stutters, and becomes completely unresponsive at times. I think it is all due to Ram management. Things just completely crash as it's trying to clear everything out. I really hope they fix this. I didn't have this problem on my 2xl with the same amount of ram so it's surprising
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
Same here, my 2XL didn’t suffer from the same issues or at least very were minor.
What’s surprising is that when the 3XL reviews came out , most reviewers agreed that the 3XL had the smoothest experience of all android phones. They either had no software issues or they actually didn’t use the phone long enough ?
malek777 said:
Good to hear but does the battery take a hit at performance ?
Click to expand...
Click to collapse
Overall battery life is about 4.5hrs of screen time on ~15 hour off the charger. Usually end the day with about 30% left. Haven't had any overheating issues though at all. Phone hasn't even gotten warm yet for me. That could be due to the multitasking bug though
Mine stutters from time to time. Restarting once a day usually solves it. Really hope fixes are coming on Monday with the security patch.
This is embarrassing for Google and especially at this price point.
It seems that the only time I had it really slow and steering was when I was trying to root it and, maybe, something got messed up. Once I ran the Google full factory 'reset' it was back to being fast and fluid again. I'm sorry that you're having so many issues with this particular phone. I do have all the animations turned off in the developer options, so that might be a reason why my phone may seem fluid and fast?