Hi,
I am trying to figure out (tried searching the forums), why doesn't the phone gives me any notification when battery fully charged.
Running stock, with no cwm recovery, no root. (Just restored it yesterday with odin. Previous rom: CM10.1 (May 18th) nighly)
I tried a couple of times deliberately charge at 90%... and an hour later... no sign of notification...
turn the screen on... lock screen shows charged.
Any insight?
Detail:
Stock 4.1.2
N7000XXLSO
Kernel: 3.0.31-1042383
Build: JZO54K.N7000ZSLO2
ensure clean installation [wipe everything (system, preload, data, cache, dalvik cache)]; then flash the official firmware
PS: don't wipe on stock kernel - BRICK CAUTION; always wipe on custom safe kernel with emmc erase disabled
majdinj said:
ensure clean installation [wipe everything (system, preload, data, cache, dalvik cache)]; then flash the official firmware
PS: don't wipe on stock kernel - BRICK CAUTION; always wipe on custom safe kernel with emmc erase disabled
Click to expand...
Click to collapse
have you tried wipe battery stats?
majdinj said:
ensure clean installation [wipe everything (system, preload, data, cache, dalvik cache)]; then flash the official firmware
PS: don't wipe on stock kernel - BRICK CAUTION; always wipe on custom safe kernel with emmc erase disabled
Click to expand...
Click to collapse
Tried manually wipe everything in cwm, still doesn't work
Anyways, I installed an third party app (noLed) as workaround.
Thanks for the help anyways.
Related
I always wipe cache/dalvik cache, battery settings and rotate setting before flashing a new kernel. I have heard people suggesting it is good to wipe all the above after flashing the new kernel as well. Is there a reason for doing this? Is it really helping anything?
There is no reason to wipe anything while doing a kernel upgrade.
I disagree.
It's always advisable to wipe at least dalvik-cache when changing kernels.
Indeed, the preferred, no loss, logical and recommended thing to do is always wipe cache and dalvik-cache when you upgrade /boot/ or /system/.
Any new rom, kernel or radio - wipe cache and dalvik-cache. It costs you nothing and eliminates most issues people experience.
I've just changed my rom, Kang-o-rama, to force wipe cache and dalvik-cache because not enough people follow simple instructions.
Just wondering... If i wipe cache will i lose all my data and settings/preferences? Especially data in my apps like messaging...etc?
Because i plan to try this out before updating to FRF85B, ive heard claims that wiping cache helps improve speed though some stated otherwise.
cr0wnest said:
Just wondering... If i wipe cache will i lose all my data and settings/preferences? Especially data in my apps like messaging...etc?
Click to expand...
Click to collapse
nope .......
JonInAtl said:
nope .......
Click to expand...
Click to collapse
Thanks, maybe i'll try that out before i flash to FRF85B and see if theres any difference.
Agree.
Wipe dalvik-cache
Wipe Dalvik but leave the other. I have had Batterylife dropping horribly after wiping my cache. But i reflashed my radio and all was back to normal. So not a Kernel issue.
But i would leave cache alone no matter what and wipe it if you experience any boot problems.
Thanks
Thanks for asking this questions. I was going to ask the same one but I just came here and read the answer already. Sweet..
I want to flash franco kernel with TWRP.
Is it advisable or necessary to wipe dalvik AFTER flashing the kernel? Would it do any harm if I didn't wipe dalvik after flashing?
Smoosh1 said:
I want to flash franco kernel with TWRP.
Is it advisable or necessary to wipe dalvik AFTER flashing the kernel? Would it do any harm if I didn't wipe dalvik after flashing?
Click to expand...
Click to collapse
You should always wipe caches to be safe, they may contain unexpected data. If you don't wipe and your device operates correctly then no problem.
I've always been flashing franco kernel with FKU. Next time I want to flash with TWRP, just to see how it goes. Thanks for your reply, I'll wipe dalvik after flashing then.
Hey guys
i want to know i need to wipe anything before or after flashing kernel or rom " Custom" - " Official " Roms ?
Clearing data and cache would ensure you have clean installation.
Yes, you should clear data/cache before you flash a new rom.
For kernels (data wipe/reset is not necessary) there's jbroid script, flash it before you install a new kernel.
Boy124 said:
Clearing data and cache would ensure you have clean installation.
Yes, you should clear data/cache before you flash a new rom.
For kernels (data wipe/reset is not necessary) there's jbroid script, flash it before you install a new kernel.
Click to expand...
Click to collapse
It all depends though. If you change ROMs and they are pretty different you really should wipe data, cache, and dalvik. That's what every OP says on ROMs. Just read the OP.
so i have rooted by my xxla6 note, cf-root with cwm, am i safe to flash any rom now? looking to flash checkrom, so i just follow the following instruction?
Q: I'm coming from a different ROM how can i install this ROM ?
A: Follow the steps below
Get into the CWM recovery
Wipe Data/factory reset
Wipe Cache
Wipe Dalvik-Cache
Wipe Battery Stats
Wipe Data/factory reset
Wipe Cache
Wipe Dalvik-Cache
Wipe Battery Stats
Install the wipe version of this ROM
Yes, that what I did for my rooted GB rom. In fact I just went through the wipe once and I had no problem. However you should follow the instruction from their website.
Normally you can just boot to recovery, flash the rom you like ie. CheckRomHD, then wipe data/cache/Dalvik (no need to wipe battery stats) and reboot.
If you get stuck in a bootloop or getting other weird issues you can reboot to recovery and do the 3-wipe again.
You just stick to what the CheckRom Dev wrote, and follow his instructions to the letter.
Completely disregard alternative ways you have been offered here.
And you guys, please don't try to confuse a man who is already uncertain of how to flash
by offering other options. What a Dev says is always the right way.
or can i just dirty wipe and wipe dalvik cache and im good to go?
thanks
Jamal Ahmed said:
or can i just dirty wipe and wipe dalvik cache and im good to go?
thanks
Click to expand...
Click to collapse
Not sure about this particular case, but I'll tell you my approach is to *always* do a full wipe + format partitions and internal sdcard before flashing *any* ROM. This way I'm sure there's nothing old left (app data, config etc.). Using this approach I've been running many ROMs without most of the bugs users report (using XXLSA now), I think it's worth the time to reinstall and reconfig everything. If you don't need to keep old data and config:
1) Wipe data & cache
2) Wipe dalvik cache
3) Format /system & /preload
4) Format internal sdcard (make sure you save anything you need before)
5) Flash ROM
6) Wipe cache again
7) Wipe dalvik cache again
8) Reboot
(Not sure if 6 and 7 are needed, but I prefer to be a bit paranoid in this case.)
Jamal Ahmed said:
or can i just dirty wipe and wipe dalvik cache and im good to go?
thanks
Click to expand...
Click to collapse
I think it depends on which custom rom u r currently on & which one you are gonna flash..for ex: flashing Ultimate v5 XXLSA over Alliance v1 XXLS7 may not work..
dbolivar said:
Using this approach I've been running many ROMs without most of the bugs users report (using XXLSA now))
Click to expand...
Click to collapse
I agree with you. If you perform a full wipe before to install a new rom, the probabilities of occur in some rom's issue (like FC or just a "simple" weird lag) are low. Tested personally.
It always better/advised to perform a full wipe.
In the end, you could do a nandroid backup of your last used rom, wipe everything, install the new rom, and then try to restore the data partition only. If you get some errors or general issue, you can easily full wipe everything again, and reinstall the new rom again... at least, you tried
Jamal Ahmed said:
or can i just dirty wipe and wipe dalvik cache and im good to go?
thanks
Click to expand...
Click to collapse
What does the OP states? Flashing ROMs is STILL a dangerous business.
Read the OP for the ROM you are installing
Jamal Ahmed said:
or can i just dirty wipe and wipe dalvik cache and im good to go?
thanks
Click to expand...
Click to collapse
leaks always require full wipe for it to function properly.
I'm want get the current cm10.1 nightlies to run on my n7000. I'm using cm-10.1-20130511-NIGHTLY-n7000.zip with 20130301 gapps package but the furthest I can get is the welcome screen. Selecting my language will freeze the phone. I've tried re-installing wipe cache, wipe data etc.. even retried to whole install a few times but nothing works. Any ideas? Sucks cos I just finished a mod on my p7510 to display now playing in status bar and want to port it over.
that is an unclean install,
on cm kernel on its recovery format system, data,preload cache an dalvik and reinstall. also make sure you have latest gapps for that version
baz77 said:
that is an unclean install,
on cm kernel on its recovery format system, data,preload cache an dalvik and reinstall. also make sure you have latest gapps for that version
Click to expand...
Click to collapse
Heres what I'm doing:
Flash abyss kernell (I have emmc bug and have had to recover from it twice now),
factory reset,
Flash cm10.1 in order to install kernel and recovery a reboot recovery,
Now in cyanogen mod recovery:
wipe cache,
wipe dalvik cache,
wipe system
wipe date,
wipe preload,
re-install cm10.1
install gapps 20130301 (the latest gapps)
what can be going wrong?
thats pretty thorought. I would recommend not abys but cm kernel instead.
tried it with both
Then I dont know. What gapps version are you flashing?
I havent read it being an issue with latest cm, maybe bad download? md5 matches download?
Also try on stock gb rom (for your phones csc), if none of above, if with emmc brick check app some sectors are damaged. Thats what I would do. If damaged, or still weird lags check warranty.
Using the 201301 gapps from goo.im. Downloaded a few times now same issue, its probably my phone as partitions are a little strange from emmc recovery.