A friend retired her Fassy, indicating that it was dog slow, wouldn't hold a charge, and took foreva to take a charge. She asked me if I wanted to play with it for a bit.
I got it, and kept it off to charge it up - seemed to top off in a reasonable amount to time - not too quick, not too slow. Once charged, I hopped on it and, woah, she definitely had something corrupted.
I went into eff it mode, pulled down all of her pics/vids/audio/dls/snaps/etc. and proceeded to root it and install a recovery. Having only owned my GS3, I have only ever been exposed to 4.x versions of android. With this device having a 2.x flavor onboard, I felt the rush of discovering something old and admiring changes for the better and observing trusted old ways of the wise.
I actually struggled a bit finding a good way to root it and get a recovery installed. I ended up following Section 4 herein and got CWM installed. From there, it was gravy getting AOKP 4.2.2 installed.
I ran some testing over the last few days, just to see how the battery survived this current generation version of Android on some older chassis' hardware. Frankly, I am really surprised that it lasted as long as it did. I kept WiFi on and have a reasonable amount of apps installed (the norm social media, gapps, etc.). I think it is safe to say that her battery and hardware are very likely fine.
Of course, real-world use will predicate a much shorter battery life. But, I think it will work fine for her, for now. And, yes, she wants it back... :crying: I was hoping she would say 'just keep it' as I was looking forward to having another droid to play with, besides my main phone (GS3) that I can't afford to be playing with too much, as it is my link to work here at the home office.
Anyways, wanted to drop a note confirming a positive experience with the Fassy and Android 4.x. Peace. Out.
-t
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i was running 4.22 based Jellybro version 7-17(the last one before they stopped developing for it) for a while. Without the devil Kernel, I got battery life of about a day and 8 hours. With 7-19 Devil Kenel I was getting around 2-3 days total. Granted I ran without mobile data turned on but I did use it with Talk and Text plus wifi so without the 3G radio to sap the battery, my results might be a little biased. Also I use 3500 mah batteries.
I am playing with Paranoid Android(4.4 based ROM) on that Fassy and battery life is even better. It;s got some glitches in it though but I like where it;s heading.
Back from the dead
Hi.
I'm trying to resurrect my old samsung fascinate from verizon. It's rooted with EH09 but it won't charge my new battery. Can you post the link for the AOKP 4.2.2 rom you installed?
Thanks,
Devan
this might be what you are looking for.
http://forum.xda-developers.com/showthread.php?t=2185502
stay with the 4.22 versions, the 4.3 and 4.4 versions are more experimental and mobile data might not be working correctly or a littlle flaky.
I've been having an extended text issue with Geewiz 4.2.2 so I might give this a look. Thanks.
Related
So last night I flashed CM9 on my mom's Epic 4g after she had complained about repeated problems with FC09. This isn't a "thank you" to the devs of CM9 in particular, although you certainly deserve it.
It might help if you know my history. I was a 0-day adopter of the Epic 4g. I had been on a local carrier with a crap dumb phone for quite a while. My family made the choice to move to Sprint and on August 31st I picked up the Epic 4g. First impressions were ok... it had power (at the time), but the OS was fairly buggy. I think it shipped with DG27... Anyway, it was a great phone, with a few flaws. I saw the initial development, I saw ACS form, Bonsai, Frankenstein, Quantum, and Midnight. I spent a considerable amount of time on the Eclair version of Syndicate Rom (I forget the name now), and moved on to the DK28 Midnight ROM until finally the ACS version of Froyo came out. Between a gingerbread theme, Launcher Pro, and ACS I was able to get a phone finally in March of 2011 that performed well, was stable and looked clean.
I really started to get sick of the hardware at this point, the screen on my Epic was horribly loose. It made the phone feel cheap and flimsy. I was waiting for something, May 8th I found out what exactly... I ended up picking up a Nexus S 4g a day later on the 9th off-contract (because I hated the epic that much by then). I sold off the epic, my game-gripper, and my spare battery... It was a pretty big decision and a pretty significant financial loss... Probably a mistake after enjoying using one again so much last night.
Anyway, I've had my Nexus S 4g and helped my family learn to live with their Epics. I've kept up slightly with the Epic community and have seen the kinds of changes that have gone on. It's incredible how much things have changed. It's incredibly to think that when I sold my Epic we hardly had CM6 rom that'd boot. CM7 was a dream and no one even knew what ICS would bring (or whether it'd be 2.4 or 4.0 or 3.3).
So like I said, last night I pulled out an out-dated version of Odin, flashed my mom's phone back to EB13 and ran one of the first "one-click" root exploits available. With ClockWork 2.5 installed I flashed the 5.0.2.7 CWM over it, and then started flashing CM9 finally. It was absolutely incredible seeing an Epic finally boot with CM9.
Seriously, this isn't for the CM9 team, it's not for anyone in particular, it's for the community... really, thank you. You've breathed life into a phone I had given up on a year ago, and my family had recently given up on... that is until they tried it with a new fresh perspective that is touchwiz-free.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Full agree with OP. CM9 is the best thing to happen to my Epic 4G.
austin420 said:
Click to expand...
Click to collapse
I thought so
I originally had the 10.1 (2014) Wi-fi version. It is not rootable without tripping KNOX and it had horrible battery life.
I now got the LTE version (T-Mobile P607T) and after rooting with TowelRoot (KNOX 0) and disabling all the bloatware, I got GREAT battery life right out of the box! I charged my tablet 100% while it's off for the 1st time and now I got:
- Almost 24 hours since last charged
- Almost 5 hours of screen on time with LTE and Wi-fi both ON
- 15% remaining
This is AWESOME!! I am sure it will get better after subsequent use and charge.
Sorry for the excitement, but I got much better battery life than my Nexus 7 (2nd Gen)!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Same here man! Even with 3d gaming (which I've seen many posts complaining about that in particular causing "massive" drain). I do use Greenify, Unbounce, etc. I'm easily good for the full day with it fully charged. My perspective is relative though, as I upgraded from a Note 8, which burned close to 10% just rebooting! So IMO, the battery life on this tablet is excellent, and easily comparable to my heavily modded / optimized Note 3.
This, perhaps, deserves it's own topic (and after explaining the procedure at length, decided I should just post one ), but especially after flashing ROMS, kernels, etc., make sure to calibrate your battery correctly! I think those instructions are worthy of a new topic (the info's here, but spread all over the place). AFAIK, none of the calibration apps work nearly as well as this, which is kind of the "old school" method, but it works very well! So I'll post that up, and definitely would recommend checking it out... It took me a while to figure this out, but I did discover how to do this on a tablet (without a phone / dialer) so hopefully that will be helpful to many here
Edit: Rereading your post, I was wondering what method you used to debloat? I'm currently semi-debloated, running xKat and freezing many system apps in Titanium (without negative effect), but then I've encountered permissions errors uninstalling system apps via that app. Just wondering specifically what method you used to debloat. TIA!
My phones battery decided to increase in size for the last two days and now i have replaced it. Does anyone know why this happens and what I can do in the future to avoid it?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ya my note 3 did the same thing, i thought it was tye battery caz of the 8 dollar price. That is the conclusion i came up with too the phone was never really hot and 2 of those batteries swelled up making them unusable. I did upgrade the battery didnt have any more swell. I would like to know how that does happen though, i thought i was the onlu person that ran into this im glad read this post and hopefully can get an answer as im very curious if it was the type of battery or if was kernel. I cant remember the kernel i had but thought might be from putting too much speed in my rom.
31aces said:
Ya my note 3 did the same thing, i thought it was tye battery caz of the 8 dollar price. That is the conclusion i came up with too the phone was never really hot and 2 of those batteries swelled up making them unusable. I did upgrade the battery didnt have any more swell. I would like to know how that does happen though, i thought i was the onlu person that ran into this im glad read this post and hopefully can get an answer as im very curious if it was the type of battery or if was kernel. I cant remember the kernel i had but thought might be from putting too much speed in my rom.
Click to expand...
Click to collapse
Yeah. I want to know this too. These days i have been swapping between stock and cm 12.1 and on stock the battery amp ranges from 1200mah to 1800mah but on cm12.1 it always stayed at 1800mah and also phone got hot. It may be due to that or it may be because discharged this battery once to zero and then recharged it to 100 and then jump charged a couple of times. A lot of factors and this one was abused a lot so I can't put my finger on exactly what I did that caused this.
Hi everyone!It's my first time posting here. I have a problem where everyday I have been getting both Android OS and Android System at the top of my battery stats.
I am running the Android N Dev 5 and getting less that 3 hours of SOT. The phone is only 4 months old.
I have tried to clear the cache and only did a factory reset only once. The reset helps a little but then creeps back. The cache clearing doesn't make a difference.. Something is eating up the battery and I have yet to try to place it on safe mode and hunt for the apps which I find such a time consuming process.
I attached a screen shot of my battery stats. I unplugged it at 11 and connected to wifi, fell asleep and woke up with 85%. Left for work and that's when I started using Data. I see that there are dots at the awake even when was asleep. It's odd and frustrating as I expected to have good battery life on the 6P but was bellow average on 6.0.1 and with N was better but not great.
Its a new phone of just 4 months and am just so tempted to have it checked out.
Any suggestions on the software side of how to fix this battery drain ?
Thanks :fingers-crossed:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
For what it's worth my 6P is behaving the same way on the N5 dev build. I went back to M and the battery drain went away. I did a full wipe then downloaded N5 again today, will update if anything improves. I'm not too concerned as the apps are not optimized for N, nor is this the final build.
Keep in mind that Developer Previews aren't designed to be daily driver ROMs and are exactly as they're titled - for developers to get their apps ready.
Flash factory images (all of them; Recovery, Boot, System, etc.) and after things have settled down - an hour or so after all the app install/updates are done, reset your battery stats and confirm SOT from 100% is still as poor as you said on DP5.
With PureNexus July23, the stock settings and kernels and everything that come with PN, systemless root/xposed, Greenify Pro, and using Tasker to disable mobile data while connected to WiFi (and subsequently re-enable Mobile Data when WiFi Disconnects), I get 2 days of battery life.
Hi everyone! Thanks for the views and help.
I went back to M and it's been great so far. Battery life is better than N and got nearly 4 hours of SOT on average.
But thinking of the apps and how they're not optimized makes me think that I should maybe hold back on the next N update till the apps are efficient and work well on it. It sounds silly now as it's still in beta but makes me cautious in some way.
Should maybe root my phone soon giving it more options.
Anyways thanks again everyone. :victory:
zarriskem said:
...I am running the Android N Dev 5 and getting less that 3 hours of SOT....
Click to expand...
Click to collapse
Until it is stable release, you can expect all kinds of craziness. It doesn't mean something is wrong.
Google most likely has a lot of debugging going on as this is supposed to be the last beta release.
Expect the public release to be much better.
Post your battery and the period you have the phone,
to get there you need dial*#*#service#*#* on the numbers and scroll to "battery health test" (work on any stock ROM xperia)
mine is 2429 (out of 2700Mah) got my Z5C for 1.5 years
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
for fun here my old sony phone (for 4years)
Actual Batt(uAh): 2697000
Bought my Z5C December 2015
Bought in 2015 December. I'm quite heavy user, played games alot etc.
chripz said:
Actual Batt(uAh): 2697000
Bought my Z5C December 2015
Click to expand...
Click to collapse
wow really good score, its seems you really save your battery.
(if you reflash\factory rest its need 2-3 charges to get accurate again)
but.. in the other hand ,my phone was 2850 when was new even its 2700 on specs.. so it could be
(maybe the charge optizmion bug i've got ruin's my battery life)
Superrman said:
wow really good score, its seems you really save your battery.
(if you reflash\factory rest its need 2-3 charges to get accurate again)
but.. in the other hand ,my phone was 2850 when was new even its 2700 on specs.. so it could be
(maybe the charge optizmion bug i've got ruin's my battery life)
Click to expand...
Click to collapse
yeah I was surprised too. Actually I was expecting something worse due to the age of the phone, the fact that I never used the "battery optimization option" and my Z5C is often charged with almost full battery (using it in the car as alerter for speed cameras/traffic jams <- USB connected). Maybe the result is influenced by the fact that I lost the original power supply early, since then I am using the one from my old S4 mini with less output (I think 1.0A).
Last factory rest was when Android 7.0 was rolled out in Germany (by Sony - without provider branding). I checked it for the first time, so I can't say which value was shown when my phone was new , but I am looking forward to see results from other users.
2672000 here.
In use since Jan 2016 - 1 year 7 Months .
I'm one of those who become nervous when getting near 50% so it frequently hangs on the wire - several times a day, actually.
I was worrying about ruining my battery by this treatment, due to reading a lot about having to 'train' your battery by sucking it down to 15-20% at times. So this is all crap information, obviuosly.
Thank you for posting this code, btw.
Useful information!