Related
Since no one replied to this message in the official CM 5.0 thread. I have decided to create a new thread and hope to find a solution to this problem.
My alarm clock would stop working randomly ever since I flashed to CM 5.0, from Beta 4 to 5..2, the problem persists. If i set an alarm that is about one hour from now, it would go off. But the real alarm I need which is supposed to go off at 8 am in the morning never goes off. Anyone had similar problems? I read Cyanogen's warning about the alarm clock problem. But seems he's just trying to remind you to reset your alarm after flashing to CM. Unluckily, I've reset my alarm numerous times and it never goes off in the morning.
Anyone can give me a hand? Thanks in advance! Overall, CM is a great ROM which gives me the option to use open vpn, which is vital for me since I'm living in China behind the GFW.
Are you by chance using any taskillers?
I do use a task-killer program. But I always keep the clock app on while i'm sleeping to try to make sure the alarm goes off on time. But it never does in the morning.
Don't use task killers on the N1, there really is no need.
cyanogen said:
Don't use task killers on the N1, there really is no need.
Click to expand...
Click to collapse
I wouldn't say that's accurate... The phone does slow down noticeably when you have 20-30+ things open
Sometimes a lot of them are running as well (using TasKiller, a lot of Yellow, including Camera, Gmail etc even when not in use and no emails being downloaded). This probably affects battery life as well.
Paul22000 said:
I wouldn't say that's accurate... The phone does slow down noticeably when you have 20-30+ things open
Sometimes a lot of them are running as well (using TasKiller, a lot of Yellow, including Camera, Gmail etc even when not in use and no emails being downloaded). This probably affects battery life as well.
Click to expand...
Click to collapse
Do you have any evidence to back this up? Yes this was a problem on older devices because many things would be fighting over the tiny amount of RAM.
You'll see lots of processes running but that's just the way Android works. Since it doesn't really benefit from simple caching like a normal linux system would, it just keeps everything running and kills unused stuff when memory is low. Most of the things you see running are either paused and using no CPU, or are services that would be periodically launched anyway.
http://developer.android.com/guide/topics/fundamentals.html#lcycles
Keeping these processes alive should actually be saving you battery rather than using it. It's more expensive to launch and restore the state of an application or service after being killed than it is to simply resume one that's been paused.
cyanogen said:
Do you have any evidence to back this up? Yes this was a problem on older devices because many things would be fighting over the tiny amount of RAM.
You'll see lots of processes running but that's just the way Android works. Since it doesn't really benefit from simple caching like a normal linux system would, it just keeps everything running and kills unused stuff when memory is low. Most of the things you see running are either paused and using no CPU, or are services that would be periodically launched anyway.
http://developer.android.com/guide/topics/fundamentals.html#lcycles
Click to expand...
Click to collapse
Yes. The phone gets slow when TasKiller shows 30 things in it. I click close all, and it's faster. Do you know my personal experiences more than I do?
Paul22000 said:
Yes. The phone gets slow when TasKiller shows 30 things in it. I click close all, and it's faster. Do you know my personal experiences more than I do?
Click to expand...
Click to collapse
I think there is likely one or two specific misbehaving applications that are giving you trouble, rather than the way the system works as a whole, thats all.
I think what Cyanogen is saying is that android does not handle running processes the way other os's do They have a lifecycle that is non-obvious to someone just looking at a process list. If you insist on killing tasks outside of the activity/service lifecycle they you _will_ get service failures (like the alarm clock) its up to you what you value more.
I have not installed any sort of task manager (outside what's in astro but I don't use it) and never see any noticeable slow down.
Anyway - back on topic.
Yes I have the same issue, never had it before.
Since flashine 5.0.2 my alarm doesn't work in the morning.
The linux kernel keeps a buffer cache of recently used files in RAM. So whenever an application wants to access something on the flash, instead of going to the flash file system, it can just get it from the file buffer cache in RAM, a significant speed increase.
If the RAM is currently being taken up by unused android apps, then that leaves less room for the buffer cache, so in theory, by killing off unused android apps more quickly, that will allow the linux kernel to allocate more space for the buffer cache and thus speeding up the system.
Am I way off here?
Dave
cyanogen said:
Do you have any evidence to back this up? Yes this was a problem on older devices because many things would be fighting over the tiny amount of RAM.
You'll see lots of processes running but that's just the way Android works. Since it doesn't really benefit from simple caching like a normal linux system would, it just keeps everything running and kills unused stuff when memory is low. Most of the things you see running are either paused and using no CPU, or are services that would be periodically launched anyway.
http://developer.android.com/guide/topics/fundamentals.html#lcycles
Keeping these processes alive should actually be saving you battery rather than using it. It's more expensive to launch and restore the state of an application or service after being killed than it is to simply resume one that's been paused.
Click to expand...
Click to collapse
I would have to agree with Cyanogen on this one. When I first got my N1, I looked towards task killers to help alleviate slowdown, but in the end, I think it's just the placebo effect in a way; you did something to try to solve the problem, and so therefore you perceive a difference.
In other words, task killers aren't needed on this beast of a phone. As for battery life (if that's an issue), look into SetCpu.
Thanks for the reply Cyanogen. I think not using task-killer, or at least not killing the clock app got my alarm working this morning. But I use task-killer not for the purpose of saving ram, but for using less data. Some programs such as facebook or a twitter client would try to connect to the internet every once in a while. I'm on a low data limit plan in China. So I don't want those programs to eat up all my data. When I'm on wifi at home, I don't worry about that. Thanks again.
Same problem. Don't use taskkillers, flashed last CM last night and didn't wake up on time this morning - alarm didn't work, thought I checked that clock icon was on place on notification bar
amwayorlando said:
But I use task-killer not for the purpose of saving ram, but for using less data. Some programs such as facebook or a twitter client would try to connect to the internet every once in a while. I'm on a low data limit plan in China. So I don't want those programs to eat up all my data.
Click to expand...
Click to collapse
Have you thought about using something like APNDroid or Toggle Data, to just switch off the cell data when you don't want to use it?
Or, Modify the behavior of the applications you don't want using data?
I have my facebook and twitter for example set to manual update only (for battery saving purposes) because there's nothing there that is critical important info, and I don't need to be notified.
Nice thread though, I'm pretty sure I try to keep people informed that task-killers aren't needed and cause issues, everywhere where it comes up. I find humor that people will still argue, even with a developer, this fact. I've had 150+ hours uptime with no slowdown (and 30 apps running) on the stock rom (without highmem support).
bofslime said:
Or, Modify the behavior of the applications you don't want using data?
I have my facebook and twitter for example set to manual update only (for battery saving purposes) because there's nothing there that is critical important info, and I don't need to be notified.
Nice thread though, I'm pretty sure I try to keep people informed that task-killers aren't needed and cause issues, everywhere where it comes up. I find humor that people will still argue, even with a developer, this fact. I've had 150+ hours uptime with no slowdown (and 30 apps running) on the stock rom (without highmem support).
Click to expand...
Click to collapse
Then please inform us of a thread that can verify what you all are saying. Not in an argumentative tone, my linpack score drastically improves after 16 hours of uptime, and a task-killer.
Rom:CM 5.0.2 -OC Kernel
wesbalmer said:
Then please inform us of a thread that can verify what you all are saying. Not in an argumentative tone, my linpack score drastically improves after 16 hours of uptime, and a task-killer.
Rom:CM 5.0.2 -OC Kernel
Click to expand...
Click to collapse
This has basically been discussed into the ground. In my eye's, its a fight vs what I like to call "Windows XP mentality", and that there was benefit on phones like the G1. With the copious amounts of memory on the N1 and droid, they cause way more harm, and immeasurable good (if any).
Summary thread: http://forum.xda-developers.com/showthread.php?t=627836
I've linked to quotes from others.
Threads/posts of interest: http://forum.xda-developers.com/showthread.php?p=5494890#post5494890
And: http://forum.xda-developers.com/showthread.php?p=5298630#post5298630
Well, this discussion is very interesting, but lets return to our problem with non-working alarm.
Today I had been experimenting with my battery life again and stumbled across this.
If you download advance task manager from the market. *NOTE* It is a paid application or *NOTE* This is illegal but you can download an .apk but again it is illegal and I am not encouraging you do it. *NOTE* You can purchase it and return it within 24 hours with your money back.
Step 1- Get advance task manager.
Step 2- Go into your home system and go into your default home or your home system.
Step 3- Now choose a screen in the home. Eg: 1,2,3 etc...
Step 4- Keep your finger tap'ed on the empty screen or somewhere empty in the screen. You can also just press the menu button and tap *ADD*.
Step 5- Choose widgets and find advance task manager.
Step 6- Now when you tap the widget icon, it will terminate all your applications.
Step 7- It will then direct you to a choice for your home application/s.
Step 8- You can just press lock and not choose your home and it will stay draining very little battery.
*Note* I do not guarantee this to work but it worked for me since I had my phone on the lock where I had a choice of home screen since 3:00 PM and it is now 6:00 PM...
3 hours and still full battery.
I have also previously managed to keep the battery up for 3 days and in the 3 days I was left with 15 percent battery.
I will post images if you people are having trouble *JUST PM ME OR POST BELOW IF YOU WANT IMAGES*
Appreciate the tip but since the inception of the Android OS this was one of the first and biggest tips amongst all of the community. It's nothing new. The Android OS actually does a damn good job of killing apps by itself. Unused RAM is useless RAM. It's a *nix based system.
The only time where this is good is when you have a stray app that's using CPU when it opens in the background when it shouldn't. Especially when it's keeping things awake. I only advise that you use this before locking the phone intentionally, and when you'd like it to go into a deep sleep.
I use task killers only when I'm putting my phone away for a while. Works better than when I used task killers. I'm also mindful about the apps I install and I uninstall and reinstall when need be, format my phone occasionally (I am an extremely heavy user) and defrag my SD card because of the heavy usage.
bongd said:
Appreciate the tip but since the inception of the Android OS this was one of the first and biggest tips amongst all of the community. It's nothing new. The Android OS actually does a damn good job of killing apps by itself. Unused RAM is useless RAM. It's a *nix based system.
The only time where this is good is when you have a stray app that's using CPU when it opens in the background when it shouldn't. Especially when it's keeping things awake. I only advise that you use this before locking the phone intentionally, and when you'd like it to go into a deep sleep.
I use task killers only when I'm putting my phone away for a while. Works better than when I used task killers. I'm also mindful about the apps I install and I uninstall and reinstall when need be, format my phone occasionally (I am an extremely heavy user) and defrag my SD card because of the heavy usage.
Click to expand...
Click to collapse
I agree but this worked for me and I recommend trying this. Also I agree with everything you have said and sometimes when I am out somewhere I tend to keep the phone in a deep sleep but I do not want to miss any calls or texts happening to me so I do this.
Appreciate what you have told me as well.
Also what good does formating do? (NOT SAYING IN AN OFFENSIVE MANNER, I AM JUST CURIOUS)
zm4 said:
I agree but this worked for me and I recommend trying this. Also I agree with everything you have said and sometimes when I am out somewhere I tend to keep the phone in a deep sleep but I do not want to miss any calls or texts happening to me so I do this.
Appreciate what you have told me as well.
Also what good does formating do? (NOT SAYING IN AN OFFENSIVE MANNER, I AM JUST CURIOUS)
Click to expand...
Click to collapse
Bongd is absolutely correct in what he says, the whole android system is designed to manage apps automatically, therefore while an app may appear on the task manager, they do not necessarily waste battery as they are sitting "idle"- that also means that an app will load up quicker when you go to open it, rather than if you kill the task.
Also my other point, and this is the big one, killing tasks can not only corrupt an app from working correctly but also it can cause instability to your system in the long run (because you are also killing certain tasks which are system processes) thus you notice bugs ion your phone and required to flash firmware again.
I've used advanced task manager and task panel side by side quite religiously for a while, yes it is faster and battery life does SLIGHTLY improve but trust me your phone doesn't like it.
Sent from my X10i using XDA App
zm4 said:
I agree but this worked for me and I recommend trying this. Also I agree with everything you have said and sometimes when I am out somewhere I tend to keep the phone in a deep sleep but I do not want to miss any calls or texts happening to me so I do this.
Appreciate what you have told me as well.
Also what good does formating do? (NOT SAYING IN AN OFFENSIVE MANNER, I AM JUST CURIOUS)
Click to expand...
Click to collapse
Formatting is good because just like a computer, things can get f***ed up for no reason. You can have all the correct settings but things don't happen as anticipated. It happens with any complex electronic devices, so this is why I recommend it every few months but this varies depending on how intensely you use your phone.
I use mine like crazy and tweak the hell out of it. I do it about once a month, but then again I have cell phone OCD.
The task manager helps to close apps that constantly keep connecting to the Internet, it's not about freeing up RAM it's about using the Internet connection
Some "apps" are some bad hogs when it comes to the phones recourses
Some "apps" are quite some hogs when it comes to the phones recourses.
Internet connection, Syncing, Updating ads and so on.
Some of these "bad hogs" also keep running "at full speed" in the background.
They have no whatsoever routines to save energy/recourses once loaded (background or not).
Designers of these "bad apps" don't care about battery-life, or they simply have no whatsoever knowledge/experience about mobile devices and how an application should behave on a such device.
If one are the kind who downloads lots of "cool" applications from the market, a task-killer can help allot, depending on how many "recourse hog" application one have installed and loaded in the background.
SysGhost said:
Some "apps" are quite some hogs when it comes to the phones recourses.
Internet connection, Syncing, Updating ads and so on.
Some of these "bad hogs" also keep running "at full speed" in the background.
They have no whatsoever routines to save energy/recourses once loaded (background or not).
Click to expand...
Click to collapse
yeah but we don't have any app that tells us which app is using the battery and data connections right? sure the android OS tells us the battery usage, but data?
A app to stay away from is eBay it hogs cpu time and constantly refreshes in the background, my batt goes from 2days down to 8ish hours when the eBay app is installed
Sent from my X10a using XDA App
tookieboy said:
yeah but we don't have any app that tells us which app is using the battery and data connections right? sure the android OS tells us the battery usage, but data?
Click to expand...
Click to collapse
System Panel can do this
Taskkiller stuff is not welcomed by my X10. When I kill all the apps , sometimes my connection to my operator goes down. I don't know how many necessary process' this taskkiller stuff kills as well.. I avoid "kill all" , instead I kill the ones that I'm sure that they're using internet and cpu in vain. Wish all the mobile developers use the close() method , then we won't be facing that kind of problems..
Has anybody figured out a way to use the back button to exit out of programs instead of hiding them so that you don't have to go to "manage applications" in order to force close them and save battery life?...i know, run.on.
konsts said:
Has anybody figured out a way to use the back button to exit out of programs instead of hiding them so that you don't have to go to "manage applications" in order to force close them and save battery life?...i know, run.on.
Click to expand...
Click to collapse
From what I understand the MT4G is supposed to do a job on it's own of closing most applications most of the time, better then any other android had (at time of release anyway). I suppose if you think it's that big of an issue you could download a task killer, but I've heard over and over again to not use on on the mt4g because you just don't need it. That's just what I heard though.
Could be wrong, wouldn't be the first time.
Is there a setting for that then? because nothing closes on my phone
yeah i agree on NOT using those task killers. i have seen many posts from devs saying they cause more problems then there worth. interfere with apps causing force closes and some other thing that i cant remember off the top of my head.
Google up "Why you shouldn't be using task killers with Android", read, educate yourself, and stop doing unnecessary things with your phone. Understand how things work before you attempt "making them work better", and screw them up in the process.
Ok sounds good, but why then when you get rid of the bloatware like "amazon mp3" by disabilig them, do you get improved battery life? What am I missing?
You don't. Battery life won't be bothered by having or not having Amazon MP3. The only thing you get is more memory (which isn't used anyway) and more space on the /system (which isn't used anyway). Additional thing you get that IS used - is less cluttered app drawer.
konsts said:
Ok sounds good, but why then when you get rid of the bloatware like "amazon mp3" by disabilig them, do you get improved battery life? What am I missing?
Click to expand...
Click to collapse
Task Killers do more harm then they do good. any developer, any coder, any one with any Android knowledge will tell you "you do not need it, and they do more harm then good". In fact Google themselves has said that it's not worth it. and the dev team @ Cyanogen will not accept a event log for trouble shooting if you have used a task killer.
But the reason we delete bloat ware is to gain that memory for other applications and data. no all apps can be stored to the SD card and they do leave a foot print on the phone. So we delete them to gain the space back.
Android phones are Lunix based computers which can multitask lightyears better than any current windows based computer system, phone or server. They were designed with this very principle in mind. In fact if you have ever used Ubuntu 10.10 they have a 4 "work spaces" where you can do different stuff simultaneously. similar to the "home screens" on android.
as far as them "running" in the background they are not absorbing any data/battery/resources from your phone. They are setting in a "frozen" state until you open them. In fact, if you didn't know this, if you press and hold the home button you can access recently open apps. It keeps them in the "frozen" state so if you switch back to them they'll open where you left them.
Thanks for all the comments. But I don't need convincing on the task killers; I understand they're worthless. My intent was to find out how to make my phone perform better (battery life-wise). And although I think I have a better understanding on how android handles apps it also just confused me.
I used to get 8-10 hrs max on my phone and basically have to charge it all the time. Since I temp rooted (permroot isn't working for me) using VISIONary and disabled a bunch of apps using Terminal Emulator, I'm sitting on 23.5 hrs off the charger right now with 45% battery left!!! And all I did was disable apps. So I'm mad confused how I'm getting so much battery life when the only thing that's changed in my phone according to you wouldn't change anything.
konsts said:
Thanks for all the comments. But I don't need convincing on the task killers; I understand they're worthless. My intent was to find out how to make my phone perform better (battery life-wise). And although I think I have a better understanding on how android handles apps it also just confused me.
I used to get 8-10 hrs max on my phone and basically have to charge it all the time. Since I temp rooted (permroot isn't working for me) using VISIONary and disabled a bunch of apps using Terminal Emulator, I'm sitting on 23.5 hrs off the charger right now with 45% battery left!!! And all I did was disable apps. So I'm mad confused how I'm getting so much battery life when the only thing that's changed in my phone according to you wouldn't change anything.
Click to expand...
Click to collapse
battery life has alot to do with your social networks, and syncing. If i turn off everything, and turn the screen brightness to about 25%, i drop about 2% per 5 hours. So it really depends on what you disabled, and if they were absorbing any resources on your phone.
neidlinger said:
Task Killers do more harm then they do good. any developer, any coder, any one with any Android knowledge will tell you "you do not need it, and they do more harm then good". In fact Google themselves has said that it's not worth it. and the dev team @ Cyanogen will not accept a event log for trouble shooting if you have used a task killer.
Click to expand...
Click to collapse
That is correct. However, there is one situation in which I do end apps, and that is in the case of resource-intensive, 3D games. The MT4G has so much RAM, that even games like NFS Shift, X-Plane, and Jet Car Stunts never close. They stay running in the background forever, which is unnecessary. So I'll close those, but no other apps.
TeeJay3800 said:
That is correct. However, there is one situation in which I do end apps, and that is in the case of resource-intensive, 3D games. The MT4G has so much RAM, that even games like NFS Shift, X-Plane, and Jet Car Stunts never close. They stay running in the background forever, which is unnecessary. So I'll close those, but no other apps.
Click to expand...
Click to collapse
I do the same but i'll got to settings > apps > running > and sever them.
BTW Backbacker is a good 3D game.
neidlinger said:
BTW Backbacker is a good 3D game.
Click to expand...
Click to collapse
I'm not finding that one. The closest I can find is this one, but that's a GPS resource, not a game.
TeeJay3800 said:
I'm not finding that one. The closest I can find is this one, but that's a GPS resource, not a game.
Click to expand...
Click to collapse
look for backbreaker football. it was a the Amazon freebie yesterday.
konsts said:
Has anybody figured out a way to use the back button to exit out of programs instead of hiding them so that you don't have to go to "manage applications" in order to force close them and save battery life?...i know, run.on.
Click to expand...
Click to collapse
Settings/applications/development/stop app via long press.
Make sure you check the box. That's how you stop the app completely.
Sent from my HTC Glacier using XDA App
No such thing on stock ROMs. CM feature.
didnt know he had a stock rom till i read his sig. xda app doesnt show that sig. saw it now that im a pc. my bad.
I've rooted my phones but haven't rooted my NST yet.
I'm interested in doing it mainly to get access to Dropbox and one of the Dropbox apps that let's you get feeds put onto your NST daily (I want to get my local paper there--which is available). I already have the paper portion working locally.
I have a few concerns:
1. What's the absolute latest/best way to root the NST? I'm on 1.1.
2. Will rooting suddenly drive my battery life down while the NST is sitting idle? I can go a week without touching it. I don't want to have to charge it every time I touch it.
3. Are the latest approaches problematic? I'm seeing threads about people having some pretty serious issues. Should I just wait at this point assuming there's serious thought to a near-bulletproof approach right around the corner?
All roots are pretty stable, there have been some methods that have had issues. TouchNooter for example had a major issue just yesterday because of a space in an Apps name. But it's been resolved and is stable.
Battery Life won't be affected so much depending on your wifi settings, if you keep wifi off you won't notice the difference between root and non-root. If you keep your wifi on though you may find yourself needing to recharge more often if you have your nook doing data updates too often.
Each version has it's advantages and disadvantages:
MinimalNooter - If you're willing to use CWM Minimal Nooter is available and is easily one of the most customizable of all the Nooters with different packages ranging from the most basic of roots "Minimal" to a full root package with Gapps XorZone's Mods etc.
Advantages
Clear Instructions, lots of information, can be a little confusing/overwhelming.
More Customizable with multiple packages
Lowest chance of FS corruption due to CWM use
No One Day Market Wait
No extra Apps to fix Market Search
Disadvantages
More steps to get to root through using CWM (Not just pop it in wait and done)
TouchNooter - TouchNooter was the original Nooter for Nook Simple Touch using the original Methods used on it's sibling the Nook Color. It installs a few mods and the basics to make it as customizable as a person needs you can drop apps in or remove them without having any real technical know how.
Advantages
Customizable with most extra apps in /data/app
Lower chance of FS corruption due to new TouchNooter methods
No extra Apps to fix Market Search
Clear Instructions that go step by step through each requirement
Disadvantages
One Day Wait to get Market Working
I would use TorimuNooter, because theCPU underclocking saves the most battery power.
I'd be very curious to know why Gabrial originally included TorimuNooter but then edited his post to remove mention of it.
[NST]MinimalTouch 1.1beta5 (+Index to manual rooting)
http://forum.xda-developers.com/showthread.php?t=1346748
My favorite so far, easy install as long as you can follow directions.
Market works immediately, lightweight - only includes apps necessary for functionality and has had no problems since installing a few weeks ago.
Still waiting for XorZones NST launcher for my nook to be complete
Agrajag27 said:
I'd be very curious to know why Gabrial originally included TorimuNooter but then edited his post to remove mention of it.
Click to expand...
Click to collapse
After the update to 0.5 in which TorimuNooter is no longer really a derivative of TouchNooter, not even bothering to change bootloader images or disk names or a number of other things unique to TouchNooter, I feel that it no longer deserves to be recognized as it's own "Nooter"
GabrialDestruir said:
After the update to 0.5 in which TorimuNooter is no longer really a derivative of TouchNooter, not even bothering to change bootloader images or disk names or a number of other things unique to TouchNooter, I feel that it no longer deserves to be recognized as it's own "Nooter"
Click to expand...
Click to collapse
He's gonna freak about that...
*hides*
So do I take it that the "simple" act of rooting will drive my battery life down, possibly significantly?
Agrajag27 said:
So do I take it that the "simple" act of rooting will drive my battery life down, possibly significantly?
Click to expand...
Click to collapse
No.
Rooting just makes you gain root access, so you can modify your device.
It wont eat any battery just for rooting, but depends on what you do with your device, it will consume more or less battery.
On idle, except if some app is preventing your device to go to sleep, it should be the same.
If you read a lot of pdfs, play games, use web browsers, etc, the cpu will stay much more time active and there will be many more screen refreshes than when reading books.
Your battery will last less when doing more intensive tasks, the same when reading books, and the same when idle.
Just dont bloat it with trilions of apps you wont use, keep it minimal as more apps running, normally means more problems with battery.
If you wanted to lessen the cpu states, you could try SetCpu or follow this manual tuto http://forum.xda-developers.com/showpost.php?p=20069231&postcount=4 (I preffer this type of tricks, instead of installing extra apps).
Don't forget to never leave the wifi on for long periods of time, as it dosn't let the device go to sleep.
Agrajag27 said:
So do I take it that the "simple" act of rooting will drive my battery life down, possibly significantly?
Click to expand...
Click to collapse
No.
If you have too many applications running the background such as email and twitter and weather updates and etc. Your battery life will be significantly less than if you have just email running. Your battery life is directly affected by what you put on your device and by which settings you use.
My nook is rooted and without underclocking my battery life hasn't changed that much, if I leave wifi off I can go weeks before I ever need to recharge, if I leave Wifi on I can go maybe a few days to a week. Which isn't abnormal or extreme battery difference from root to non-rooted.
It's very much like your android phone, when you rooted it the battery life didn't actually change, if you install new roms, or different kernels you risk a difference between non-root and root. However the only real difference between root and non root on this device is your ability to install apps on the device and do things that require root such as directly modify the filesystem, or use root ADB.
If you don't overload your device with bloat and lots of apps that want to run in the background you won't notice a difference. If you decide to bloat your device up with a bunch of excess apps that like to stick around in the background you risk the chance your battery life will suffer.
Googie2149 said:
He's gonna freak about that...
*hides*
Click to expand...
Click to collapse
I'm a dev, I don't care if he freaks, it's my honest opinion. To me there's a fine line between derivatives and non derivatives, if he can't even bother to change the things that mark the image he used as TouchNooter than to me that is theft and nothing else, regardless of the changes or additions he makes to it.
I had read elsewhere that an app or two that got installed as a by-product of the rooting process was taking up CPU that wasn't there prior.
That was the concern. For me I'd think about adding passive e-mail support, another keyboard, possibly another reading app and would be likely to read more PDF's though now it appears I can get my newspaper (which is the primary goal) in epub format daily.
On WiFi, I haven't touched the default other than setting up access and it's been a good three weeks since I last charged and just re-charged it at 10%. I guess I could do better than that turning that off.
GabrialDestruir said:
I'm a dev, I don't care if he freaks, it's my honest opinion. To me there's a fine line between derivatives and non derivatives, if he can't even bother to change the things that mark the image he used as TouchNooter than to me that is theft and nothing else, regardless of the changes or additions he makes to it.
Click to expand...
Click to collapse
I understand that entirely, but Torimu will still be upset about it. He is kind of going around advertising his as the best nooter, and having it "insulted" (in his mind) will probably set him off. You know what, I should probably just leave this whole thing alone... :/
Agrajag27 said:
I had read elsewhere that an app or two that got installed as a by-product of the rooting process was taking up CPU that wasn't there prior.
That was the concern. For me I'd think about adding passive e-mail support, another keyboard, possibly another reading app and would be likely to read more PDF's though now it appears I can get my newspaper (which is the primary goal) in epub format daily.
On WiFi, I haven't touched the default other than setting up access and it's been a good three weeks since I last charged and just re-charged it at 10%. I guess I could do better than that turning that off.
Click to expand...
Click to collapse
Gapps does get added in with some other apps to make it more usable. Gmail runs in the background but with the right settings it isn't an issue. The launcher I believe could also run in the background with some settings (I believe there's an option in ADW so it doesn't close completely) but I pretty much find battery life between root and non root is pretty much negligible.
I forgot about the disk names...
But I will change that. I'm just trying to improve upon others work.
Thanks for your opinion Gabreil......
I'll try to stop advertising.
Torimu.Joji said:
I forgot about the disk names...
But I will change that. I'm just trying to improve upon others work.
Thanks for your opinion Gabreil......
I'll try to stop advertising.
Click to expand...
Click to collapse
It's more than just disk names there were other changes I made, big changes that would be rather noticeable if you bothered to test your work. Like for example the start up image which was left completely unchanged in both your most recent updates.
@Gabrial and the other nooters
While you're on the subject of images I just want to take the opportunity to emphasize the importance of you guys keeping your images within the size of the original NST boot partition.
Reason is, as said before, people regularly do the mistake of writing your image directly to the NST instead of writing it to the SD card.
Just this week I've had four cases where people have written "garbage" data outside the boundaries of the boot partition, and as you (should) know, the next one is the tiny /rom partition with the really important stuff.
Thank you
-Roger
ros87 said:
@Gabrial and the other nooters
While you're on the subject of images I just want to take the opportunity to emphasize the importance of you guys keeping your images within the size of the original NST boot partition.
Reason is, as said before, people regularly do the mistake of writing your image directly to the NST instead of writing it to the SD card.
Just this week I've had four cases where people have written "garbage" data outside the boundaries of the boot partition, and as you (should) know, the next one is the tiny /rom partition with the really important stuff.
Thank you
-Roger
Click to expand...
Click to collapse
I often keep this in mind. It's even addressed as one of my "Before you Begin" pieces. The problem is there's only so much you can do before it just falls to the user to pay attention and not screw up their device. When "You must have an external microSDCard reader or this will not work. Do NOT use the Nook Simple Touch." is apart of the "Before you Begin" and a user ignores that, then it's unfortunately their fault if or when they screw up their device by not following directions.
I've always limited my images to 128 because it's big enough for people to add what they want or to expand Nooter as needed. I'll actually be switching over to the CWM method which would be safer but you're stuck with the same issues with CWM that you will see with using TouchNooter's current image based method and that is people not following instructions and screwing up their devices.
While limiting images and such to 70MB (I think that's right) would be ideal the issue is the majority of that space is already filled, meaning you're very much limiting what you can do with an "automatic" method.
Mind you I've heard of methods like noogie which is the exact size if I remember for the boot partition completely destroy a device because someone wasn't following the proper directions. So the issue isn't the size of the image but how the user uses them.
GabrialDestruir said:
Mind you I've heard of methods like noogie which is the exact size if I remember for the boot partition completely destroy a device because someone wasn't following the proper directions. So the issue isn't the size of the image but how the user uses them.
Click to expand...
Click to collapse
True, but my experience is, and I get around three to four cases every week, is that they write it to the root device which means that 76MB (or 155648 sectors to be exact) is ok.
Beyond that you go into the next partition and the data there is only a couple of hundred kilobytes.
So you see, just 300KB beyond the size of /boot is enough to completely brick a NST forever :/
Yes, there's a backup zip in p3 (factory) but it's usually fragmented and I have only once succeeded in recovering it..
Let me end with a 2012 version of a famous (mis)quote:
"155648 sectors ought to be enough for anybody"
-Roger
ros87 said:
Let me end with a 2012 version of a famous (mis)quote:
"155648 sectors ought to be enough for anybody"
-Roger
Click to expand...
Click to collapse
I wish that were true, lol, but considering how much information we want to put on the device it's hard. Perhaps if CWM could grab zip files off of the internal media storage you could toss CWM on 155648 sectors then keep all update zips, etc on the internal storage partition
So i just squires an NST and already have a Fire and Sensation for most of my needs, i really only want to use this as a reader, but the restrictions blow. i really only care about fixing this partition silliness. Which is the best way for just getting that space available.
Today I've investigated suspicious activity from FMRadio.apk on the latest update of the system.
So I followed whois to discover IPs Firewall managed to block.
There are possibilities of brut attacks or personal data flows.
Stay away from this Chinese little present.
That's the answer to out donates guys.
Pissed off.
LoL. That's nice. How you figured out there is some data flow in the background? Just just started capturing the packets?
http://cyberwarzone.com/malicious-history-of-119-90-35-243/
At first I noticed high battery drain and high data usage. Investigation led me to the app that uses much processor time.
So I installed firewall and set an aggregative rules.
And voilà.
Also there are another dark IPs on the list.
PsyClip-R said:
At first I noticed high battery drain and high data usage. Investigation led me to the app that uses much processor time.
So I installed firewall and set an aggregative rules.
And voilà.
Also there are another dark IPs on the list.
Click to expand...
Click to collapse
Wow that's interesting, nice find. I always suspected Chinese OS leaked info through a backdoor, that's why I've never flashed them. Did you report it to the mokee maintainers?
Thanks for pointing this out, this is really weird. To be fair, I had a look and this FM Radio was directly forked off CM. If you want a fair comparison, you might wanna try to check on CM too (with similar setup of course).
EDIT: I did some extra research and AFWall+ did have this: "Q: I see data traffic consumed by application xyz which is blocked by AFWall+, why? A: It's possible false data traffic. AFWall+ uses IPtables which is at kernel level (low-level). Usage data shown by Android is calculated before it gets dropped by firewall."
So to prove that it's really FMRadio's fault (since interference is possible), a way is to do a test with clean install with nothing else. Feel free to voice your opinions, but I am not here to start a flame fest. I am interested in this weird behaviour too.
Ryuinferno said:
Thanks for pointing this out, this is really weird. To be fair, I had a look and this FM Radio was directly forked off CM. If you want a fair comparison, you might wanna try to check on CM too (with similar setup of course).
EDIT: I did some extra research and AFWall+ did have this: "Q: I see data traffic consumed by application xyz which is blocked by AFWall+, why? A: It's possible false data traffic. AFWall+ uses IPtables which is at kernel level (low-level). Usage data shown by Android is calculated before it gets dropped by firewall."
So to prove that it's really FMRadio's fault (since interference is possible), a way is to do a test with clean install with nothing else. Feel free to voice your opinions, but I am not here to start a flame fest. I am interested in this weird behaviour too.
Click to expand...
Click to collapse
Anyway if that's not FM radio, why does kernel / low level software connects to black IPs?
Can not provide in-depth testing 'cause I stopped using MK immediately after that issue.
PsyClip-R said:
Anyway if that's not FM radio, why does kernel / low level software connects to black IPs?
Can not provide in-depth testing 'cause I stopped using MK immediately after that issue.
Click to expand...
Click to collapse
Something else must have triggered the connection (all high level requests gets completed at low level), but I actually checked those IPs, they aren't really blacklisted, most of them are cloud providers/university
For example:
https://urlquery.net/report.php?id=1463689740716
http://www.iplocationtools.com/192.86.14.67.html
http://www.tcpiputils.com/browse/ip-address/23.251.100.132
This as mentioned in a previous post did not appear at all
http://cyberwarzone.com/malicious-history-of-119-90-35-243/
Ryuinferno said:
Something else must have triggered the connection (all high level requests gets completed at low level), but I actually checked those IPs, they aren't really blacklisted, most of them are cloud providers/university
For example:
https://urlquery.net/report.php?id=1463689740716
http://www.iplocationtools.com/192.86.14.67.html
http://www.tcpiputils.com/browse/ip-address/23.251.100.132
This as mentioned in a previous post did not appear at all
http://cyberwarzone.com/malicious-history-of-119-90-35-243/
Click to expand...
Click to collapse
Just fresh installed mokee, just wondering, why does it have to connect to servers to china and singapore all the time?
Another MoKee security issue
Android/AdDisplay.Waps.Q
I determined a lot of FMradio.apk´s in several ROM´s that ask for root privileges and was wondering why a FMradio needs those privileges.
Also firewall loging shows a lot of activity. I don´t use FM and always delete that apk but if someone is using it: Be careful and check out what´s wrong there.
PS; I don't know if that has anything to do with mokee, stating just about FM radio*s behaviour.
Wolfcity said:
I determined a lot of FMradio.apk´s in several ROM´s that ask for root privileges and was wondering why a FMradio needs those privileges.
Also firewall loging shows a lot of activity. I don´t use FM and always delete that apk but if someone is using it: Be careful and check out what´s wrong there.
PS; I don't know if that has anything to do with mokee, stating just about FM radio*s behaviour.
Click to expand...
Click to collapse
This FM radio asking for root rights .. i had this experience with Turbo, Cdroid ROM too .. Then i had thought that they are coz of rooted device in general. .. now i am afraid ..
When We root and flash any ROM, or Modify OS, Or use Cracked apps, We understand every risk of data leaking. So Posting this useless post is useless. Learn something then Say ****.
hoshang.govil12 said:
When We root and flash any ROM, or Modify OS, Or use Cracked apps, We understand every risk of data leaking. So Posting this useless post is useless. Learn something then Say ****.
Click to expand...
Click to collapse
oh really? you so smart? :laugh::laugh::laugh:
omg
the search for 'useless' in this thread only reveals 1 post
PsyClip-R said:
oh really? you so smart? :laugh::laugh::laugh:
Click to expand...
Click to collapse
zitronenmelissa said:
omg
the search for 'useless' in this thread only reveals 1 post
Click to expand...
Click to collapse
When I tell this on Mokee google+ group the other day, that guy straight to insulting me, so I had to just shut up and laughing instead. He so insist that I'm dumb or noob. Hahaha. What a pathetic group.
It's clear that something fishy is going on, and with no privacy guard control over fm apk, we can't do much aside of freeze the fm apk, and watch for other possible sketchy things from the rom. So if we don't want our data going to "that place", well, I'd say no to Mokee.
As for that guy, he apparently like to insist that we have to surrender our private data when using custom rom etc, and he like to insult us if we don't. :laugh: :laugh: :laugh:
Too bad. Unfortunately I am stuck on mokee because its the only one that still provides OTA Updates for the old Redmi 3 (Ido) after LineageOS dropped support.
I am not able to compile Android by myself.
For V500 and some other devices there is still https://www.los-legacy.de/ but nor for our old gem.
I am nor trying my best to restrict spy-activities using AF-Wall
best regards,
Bul