but i'm having an issue... i'm using S2E and its the second time this happens... suddenly internal memory gets full... completely full... any ideas about what may be causing this?
[27/01/2013] Eco CM7 - A minimalist cm7 build
#61
Posted 10 December 2012 - 10:01 PM
but i'm having an issue... i'm using S2E and its the second time this happens... suddenly internal memory gets full... completely full... any ideas about what may be causing this?
#62
Posted 10 December 2012 - 10:17 PM
Rockas, on 10 December 2012 - 10:01 PM, said:
but i'm having an issue... i'm using S2E and its the second time this happens... suddenly internal memory gets full... completely full... any ideas about what may be causing this?
No idea, sorry.. I've never used S2E..
Obvious question: Are you sure your sd is not full?
#63
Posted 10 December 2012 - 11:39 PM
jventura, on 10 December 2012 - 10:17 PM, said:
Obvious question: Are you sure your sd is not full?
yep... absolutely sure :-)
it's the internal phone memory that gets filled up.
btw... do you have any flashable version of your mms auto retrieval fix that can be used on a "normal" CM7 ROM?
#64
Posted 11 December 2012 - 09:23 AM
#65
Posted 11 December 2012 - 11:13 AM
Rockas, on 10 December 2012 - 11:39 PM, said:
This is "normal" cm7 (7.2 to be more explicit)..
But if you want the mms patch in other cm7.2, you need to copy framework.jar and mms.apk. But it can have nasty effects, so attention for backups..
sam tyler, on 11 December 2012 - 09:23 AM, said:
Hum?
It is working fine to me.. Are you sure that you have not any virus in your computer or something like Internet Explorer plugins that are forcing you to download spyware?
#66
Posted 11 December 2012 - 11:53 AM
Edited by sam tyler, 11 December 2012 - 12:07 PM.
#67
Posted 11 December 2012 - 04:38 PM
#68
Posted 12 December 2012 - 02:40 PM
sam tyler, on 11 December 2012 - 04:38 PM, said:
Sam, if you read the third post, I give some suggestions about managing better battery life. But the thing I would stress more is to disable the auto-rotation.. I still think there is a bug on one of the drivers which is using the magnetic sensor (which draws too much battery) than the g-sensor (which uses much less battery) to control the auto-rotation. With the auto-rotation off, I think you'll improve your battery life by about 30%-40%, round numbers.
#69
Posted 13 December 2012 - 09:24 AM
jventura, on 12 December 2012 - 02:40 PM, said:
Edited by sam tyler, 13 December 2012 - 04:13 PM.
#70
Posted 14 December 2012 - 05:46 AM
jventura, on 12 December 2012 - 02:40 PM, said:
Sam, if you read the third post, I give some suggestions about managing better battery life. But the thing I would stress more is to disable the auto-rotation.. I still think there is a bug on one of the drivers which is using the magnetic sensor (which draws too much battery) than the g-sensor (which uses much less battery) to control the auto-rotation. With the auto-rotation off, I think you'll improve your battery life by about 30%-40%, round numbers.
I doubt it.
I've gotten so far with Mokee (neo kernel) that with five hours of use over 48 hours i got 10% left which will last for a while if someone calls (more than one hour) but it takes breaking some compatibility with ADB over network and some apps that require Wifi to be static.
It's daft, wifi should always be dynamic so while it's the fastest of all and certainly the one with best battery potential, it's all ruined by the sub par networking.
Edited by Snap.IT, 14 December 2012 - 05:47 AM.
CWM-6.0.1.1 Touch Stable
CWM-6.0.1.5 Touch Testing
Multiboot via loop, no partitioning needed
#71
Posted 14 December 2012 - 11:02 AM
Snap.IT, on 14 December 2012 - 05:46 AM, said:
I've gotten so far with Mokee (neo kernel) that with five hours of use over 48 hours i got 10% left which will last for a while if someone calls (more than one hour) but it takes breaking some compatibility with ADB over network and some apps that require Wifi to be static.
It's daft, wifi should always be dynamic so while it's the fastest of all and certainly the one with best battery potential, it's all ruined by the sub par networking.
Well, I don't have real numbers to back me up, just my perception!
But once I set some printfs in the g-sensor driver on the kernel, and I saw the initialization but never saw the logs on data coming. Also, with List Sensor, I could see that the graphic output of the g-sensor in the app was quite similar to the magnetic sensor. I went through the datasheet specs of the devices, and in the end, I came to the conclusion that the culprit could be a binary named AKMD2 for which we don't have source.. This akmd2 is a loop service which queries the g-sensor and magnetic sensor and sends the results to /dev/something through a pipe.. In the first versions of cm7, everything was ok, but when gen2 came along and some phones would not work with cm7, TomG changed the "old" akmd2 with a "newer" akmd2, and battery usage was never the same..
I play a lot of a single game (Sudoku) which does not use lot of cpu, mostly waiting for my input and process it (like 1 number each 2 seconds, which is a lot of time idling), and I can see perfectly the difference on battery drainage with and without screen rotation switched on. Of course, the drainage will only be most obvious in specific usages such as screen on with lots of idling. If you game a lot, the drainage will be as expected, and if you have the phone in deep sleep, the sensors are disabled..
So, you are right to doubt my previous 30%-40%, since you probably use your phone in different ways than me..
Edited by jventura, 14 December 2012 - 11:06 AM.
#72
Posted 16 December 2012 - 11:33 AM
Thanks a lot to allow me use a CM7 rom. In all the CM7 rom based, the mms doesn't work on my blade (with data off). I used the Swedish Snow, CM9 and CM10. CM9 and CM10 seems to be heavy for the device. The Swedish Snow dont have the same customization and themes.
But, in your rom, in order to receive mms and get a notification, I had to define in the internet APN the type as 'default' (and not 'default,supl').
Once again, thanks for resolving this old problem, that prevent some people use the CM7.
(really sorry about the english)
#73
Posted 18 December 2012 - 12:30 PM
Edited by sam tyler, 18 December 2012 - 12:33 PM.
#74
Posted 20 December 2012 - 08:32 PM
Thanks
Tom
#75
Posted 20 December 2012 - 08:52 PM
Tom Cox, on 20 December 2012 - 08:32 PM, said:
Thanks
Tom
Hi there, no idea.. Try to download it again, wipe data, cache and Dalvik-cache, reinstall again from the beginning...
#76
Posted 20 December 2012 - 11:11 PM
jventura, on 20 December 2012 - 08:52 PM, said:
Hi there, no idea.. Try to download it again, wipe data, cache and Dalvik-cache, reinstall again from the beginning...
Hi jventura, i've noticed this question a lot and you always seem to miss the obvious... overclocking.
In all cases with my previous work it's been the culprit.
CWM-6.0.1.1 Touch Stable
CWM-6.0.1.5 Touch Testing
Multiboot via loop, no partitioning needed
#77
Posted 21 December 2012 - 12:23 AM
Snap.IT, on 20 December 2012 - 11:11 PM, said:
In all cases with my previous work it's been the culprit.
Well, since Tom Cox said that there is no reason he could determine, I guess someone who overclocks his phone and sees reboots, logically will determine that overclocking is the culprit.. Or maybe not..
#78
Posted 21 December 2012 - 01:38 AM
jventura, on 21 December 2012 - 12:23 AM, said:
Well, since Tom Cox said that there is no reason he could determine, I guess someone who overclocks his phone and sees reboots, logically will determine that overclocking is the culprit.. Or maybe not..
Maybe not is a good guess, the usual reply after they tell me they are overclocking is "i used to overclock my other phone and it worked just fine, your ROM sucks".
This forum is one of the best though, but users are a bit overwhelming at times and for some reason reading earlier posts is not something most are capable of doing for some reason.
Anyway, this is a nice ROM and i appreciate your work both with this and generally, keep it up.
CWM-6.0.1.1 Touch Stable
CWM-6.0.1.5 Touch Testing
Multiboot via loop, no partitioning needed
#79
Posted 21 December 2012 - 06:54 AM
Revolution HD (Android 4.1.1) - Lava iris 501 (Android 4.0.4)
ClockWorkMod 6.0.1.5
DELL xcd 35:
Gingerbread MMHMP (Android 2.3.5)
#80
Posted 23 December 2012 - 01:54 PM
fahad.sagittarius, on 21 December 2012 - 06:54 AM, said:
Hi fahad, I left your post unanswered, did not see it!
Well, regarding Swedish Snow rls7, one user has already mentioned that can get more 12h of usage out of this Eco CM7 comparing to rls7. Here is what he said:
azidhaka, on 24 November 2012 - 04:16 PM, said:
To see the list of changes, check 2nd post, and for tips regarding battery, read the 3rd post. When I use Eco CM7 (sometimes I use Eco CM9 because of my girls which prefer cm9), I usually get 4/5 days of battery our of it, with some calls, sms, and some sudoku playing (light usage)..
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users







Sign In
Create Account


Back to top









