Was running blazer 1.7 with no problems updated to 1.8 did full data/factory reset wipe all caches and everything was great but no vibrate when receiving texts. Checked settings and all. Waited for 1.9 wiped caches as usual several times then factory data rest/wipe several times flashed update same problem no vibration..... any ideas?
Sent from my SPH-L710 using xda app-developers app
Related
I am running CM7 with the stock kernel. When I install Chad's Incredikernel (2.6.37.6), my ringtone disappears and I just get vibrate. I looked at every single setting in CM settings, Android sound etc..... Nothing ever fixed it. I reverted back to the stock kernel and the ringtone comes back.
What may be the problem.
Never heard of that, but did you wipe Dalvik Cache and normal Cache before flashing? I've ran that kernel on CM7 and MIUI without any ringtone problems, and I always wipe those 2 caches before flashing.
That may be the problem. I wiped dalvik.vm.heapsize, but not the other. I will try again. Thanks for the reply.
Sent from my ADR6300 using XDA App
The auto-sync option is randomly, at least as I can tell as there seems to not be a pattern, not working; when I go into settings the box is unchecked. When I enable it again it will be fine for awhile (1-3 days) and will "shut off" again.
The phone is rooted with clockwork mod.
Is there some known bug?
Hmmm sounds funny to me what ROM are you running
Sent from my SGH-T989 using xda premium
ROM: Stock
That sounds odd I hate to recommend it if stock because sounds like cache issue.
If stock you have to factory reset.
If you have cmw or other custom recovery you can wipe your cache partition, then your dalvick cache, then run fix permissions.
Factory reset wipes caches and is only way to do so the way you need to if running stock.
In extreme cases I have had to re-image a phone that acted like this (via kies if using stock phone) to fix it, but again is rare and normally over kill.
Sent from my SGH-T989 using Xparent Green Tapatalk
The dialer program crashes after a call ends. Any way to fix this?
Try a full wipe and clean install. This problem shouldn't be happening. I'm on the same build and I've never experienced this.
Task650 AOKP 4.1.2 JB. 11/18 Build
Underwear kernel (Intellidemand/Deadline)
I only had this problem after dirty flashing. Once I FULLY WIPED!!!!!! it hasn't been a problem since.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
zaisaroni said:
I only had this problem after dirty flashing. Once I FULLY WIPED!!!!!! it hasn't been a problem since.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I just reread task's OP and realized I forgot to wipe davlik cache. I've flashed a couple ROMs and haven't done that (only wipe data/factory rester & wipe cache partition) and it has worked fine. Should wiping davlik cache be part of my standard procedure before flashing a ROM?
mikecantreed said:
I just reread task's OP and realized I forgot to wipe davlik cache. I've flashed a couple ROMs and haven't done that (only wipe data/factory rester & wipe cache partition) and it has worked fine. Should wiping davlik cache be part of my standard procedure before flashing a ROM?
Click to expand...
Click to collapse
I think you answered your own question there...
Sent from my A510 using Tapatalk 2
That worked. Thanks!
im still getting wifi connected notice after updated to 6.2...anyone else having this issue
britdude said:
im still getting wifi connected notice after updated to 6.2...anyone else having this issue
Click to expand...
Click to collapse
Did you factory reset, wipe data, wipe cache, wipe dalvic cache at least 3x each before flashing? I have not had a problem with any of seans roms watsoever......maybe make sure u have the recent recovery?
Sent from my Galaxy Note 2 running SkyNote5.0.1
re: skynote 6.2
jyazzie110 said:
Did you factory reset, wipe data, wipe cache, wipe dalvic cache at least 3x each before flashing? I have not had a problem with any of seans roms watsoever......maybe make sure u have the recent recovery?
Sent from my Galaxy Note 2 running SkyNote5.0.1
Click to expand...
Click to collapse
I just started from a fresh , wiped 3x all 3 ..and started with base 6.0 then update 6.1 then update 6.2........
no mods or anything, not even an account added...
i still get the connected to wi-fi network coming up..
its no biggie but just curious as to what i may be doing wrong as i have had no probs myself with skynote till this..
the battery charged has stopped coming up so that sure worked..
*Thx for all replies...going to look into it again when i get home.....would wiping internal storage do anything to help..i have been on 4.2 and back on 4.1 *
britdude said:
im still getting wifi connected notice after updated to 6.2...anyone else having this issue
Click to expand...
Click to collapse
I would re download ROM and mods again. I'm now on 6.2 and no wifi notification notice.
Or it may be a modification causing it. I'm using 75% transparency, blue theme, and circle blue battery.
Sent from my SAMSUNG-SGH-I317 using xda premium
Maybe if you're doing a tibu restore there is something being restored from a previous backup.
Currently I'm running 6.2 (flashed 6 base then when .2 came out I only wiped caches and flashed)
Mods: new green circle battery, light saber s pen sounds.
Check the mods you have on your sd card maybe one of them are dated prior to the files that are on Sean's goo.im the naming could be throwing you off because I know that some of the mods are labeled as V3 but have been updated more than 2-3 times without actually changing the version number.
~PsyCl0ne
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
martinezma99 said:
I would re download ROM and mods again. I'm now on 6.2 and no wifi notification notice.
Or it may be a modification causing it. I'm using 75% transparency, blue theme, and circle blue battery.
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
jyazzie110 said:
Did you factory reset, wipe data, wipe cache, wipe dalvic cache at least 3x each before flashing? I have not had a problem with any of seans roms watsoever......maybe make sure u have the recent recovery?
Sent from my Galaxy Note 2 running SkyNote5.0.1
Click to expand...
Click to collapse
Update.......ok, i have cleaned my internal storage( as all my needed stuff on external)....i redownloaded 6.0 and update 6.2...
i wiped cache and system 3 times each,and installed base 6.0 with 6.2 update in same procedure.....
no other mods and none of my original apps restored..i have a basic system with just skynote 6.0 and 6.2 update on....but sadly still get the wifi connected message coming up ...
i must be doing something wrong..but what..lol..
any ideas??
Is it possible to get the AOSP 4.2 messaging / MMS with skynote ROM? They currently have a flash for AOSP version but it's missing the group messaging that is in the latest 4.2 version. This would eliminate the requirement for a third party app to use group messaging.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Ok I had purchased the ZL battery and have been using it since day 1, however today i got home around 11:25pm. i had put my phone on charge @ 3PM. I just finished my 3rd cycle for the battery so i'd figure its done charging as it indicated it was, and turn it on and now all of sudden constant bootloop out of nowhere.
What could have caused this? it was working just fine before i didn't change anything at all.
I'm Running Stock TW w/Saber Kernel. I had purchased the ZL battery a week ago and ever since no problems, nor did i flash anything at all. I've been on TW way before i even thought of buying the battery.
So what could have caused this to undergo a bootloop session.
I went into recovery and wiped dalvik and cache and still is doing a bootloop. Should i do a factory reset however i have no backup because i have been fine since and I've been on Stock TW figure this wouldn't happen.
This used to happen on my epic if I ever left the battery out too long. I always just reflashed either the rom or the kernel. Worst case scenario you just nandroid and restore data.
Sent from my SPH-L900 using Tapatalk 2
xopher.hunter said:
This used to happen on my epic if I ever left the battery out too long. I always just reflashed either the rom or the kernel. Worst case scenario you just nandroid and restore data.
Sent from my SPH-L900 using Tapatalk 2
Click to expand...
Click to collapse
my battery was on the charger in the phone not out at all.
Plus i just re-flashed the kernel still no luck it bootloops and i feel it vibrate and notice the blue led flicker once it restarts the bootlogo.
Factory reset still in bootloops WTF
XxLostSoulxX said:
my battery was on the charger in the phone not out at all.
Plus i just re-flashed the kernel still no luck it bootloops and i feel it vibrate and notice the blue led flicker once it restarts the bootlogo.
Factory reset still in bootloops WTF
Click to expand...
Click to collapse
Try going into Advanced then format system, data, cache, and dalvik cache.
Then swipe to confirm and repeat this 2 more times for a total of 3 Advanced wipes
If that still doesn't help then follow the same procedure but after performing an Advanced wipe 3x go into Format Data to format your internal storage.
Sent from my SGH-T999 using xda premium
LuigiBull23 said:
Try going into Advanced then format system, data, cache, and dalvik cache.
Then swipe to confirm and repeat this 2 more times for a total of 3 Advanced wipes
If that still doesn't help then follow the same procedure but after performing an Advanced wipe 3x go into Format Data to format your internal storage.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I just did the one click mc2 root restore stock
Sent from my SPH-L900 using xda app-developers app
Seems like you already did a full stock restore. I had the same symptoms, different rom tho. Reflashing the rom without wiping allowed me to boot up normally and with all of my data is intact. FYI for next time.
Sent from my SPH-L900
coiledwire said:
Seems like you already did a full stock restore. I had the same symptoms, different rom tho. Reflashing the rom without wiping allowed me to boot up normally and with all of my data is intact. FYI for next time.
Sent from my SPH-L900
Click to expand...
Click to collapse
I said I was on stock and had no nandroid of stock seeing how I shouldn't have needed one. But thanks for the info. I'll have to back it up today.
Sent from my SPH-L900 using xda app-developers app