I have some graphic errors on the transparent notification bar.
This problim exists with different wallpapers and only while bar is transparent.
My phone is stock, no root.
Is there anyone with the same problem and know how to fix?
thats weird...
have you tried to see if the problem is still there after using a different scene / skin ?
if it is. Put back the stock wallpaper, and if it still doesnt fix it. try a factory reset.
has it always been like this ? or did it just happen out of the blue ?
It is still there with other scenes/profiles and with stock wallpaper.
I have this problem since first boot.
try a factory reset, if that doesnt fix it send it back
or root it and flash a different rom
Thanks! I will try to reset.
it seems to me its just a bug in the ROM or at least in the theme part of the ROM, providing there are no other issues with the phone i doubt it can be hardware related. So a wipe or a new ROM should fix it...
thats if you want to flash a new ROM ? Surely your into development and stuff because here you are.... on XDA lol
I will wait with unlocking until it is clear that there are no other problems with my phone, so i can send it back with warranty.
Hard resetting or flashing RUU will not solve this problem, I've tried it.
I have found more strange graphic errors in themes and background menue.
Can someone check this on his phone?
I will find out if it stands in context to the notification bar problem.
that looks like a damaged screen Is it only there on that particular app. or is it there all the time, even on homescreen..
have you checked for updates under settings ??
you could either root and flash a new ROM, or send it back and get a replacement.. i would send it back. because if it comes back after modding the device. They may not replace it.
Related
this has been going on for a few months now, when i try to shut the phone down completely it just reboots itself. the only way to get it to turn completely off is by pulling the battery and leaving it out. as soon as i put the battery back in the phone it autoboots up. at first i thought this was a CM7 issue but in the past 2 days ive tested leedroids rom, honeysenceHD, and a few others and the phone still acts the same. its never been an issue but i would love to be able to turn the phone completely off if i ever needed to. someone suggested that its possible my bootloader is corrupted. is there any way to fix this issue?
This is a problem with the Advanced Power Manger, search for the fix.
Sent from my Inspire 4G
ok well can someone point me in the direction to fix this problem.....search finds NOTHING for a fix
what apps do you have installed can you list them? They can sometimes cause problems...
Make sure "Fast boot" is UNchecked under Settings, Power.
i dont see a POWER sub menu in settings nor can i find Fast Boot.
apps are as follows
everything that comes stock with CM7
Battery Calibrator
Beautiful Widgets
COveroid
Dev Tools
DSPManager
FasterFix
Linpack
Quickboot- just to see if it would turn the phone off and it doesnt
setCPU but not using it currently
Spare Parts
thats about it a few of those apps i think are part of CM7 but im not sure
Look for fastboot in settings, applications.
Sent from my Desire HD using XDA Premium App
theres nothing in applications that allows me to turn on or off FASTBOOT
ok so i was told theres no FASTBOOT option in CM7 so anyone else out there have any clue as to why my phone will not turn off and stay turned off when i power it down?
Projectdwnshft said:
ok so i was told theres no FASTBOOT option in CM7 so anyone else out there have any clue as to why my phone will not turn off and stay turned off when i power it down?
Click to expand...
Click to collapse
Well at this point, if you think that continuing to try other roms other than what you've already flashed won't help, you might just try flashing a completely stock image, with the stock hboot/recovery, etc., and see if indeed something went haywire with your bootloader, as you mentioned someone had suggested to you.
Try the RUU in the stickied thread, for example. The recent OTA ROM by Attn1 has the hboot removed from it so I don't think that would be a good choice for this attempt, because you want to get the stock bootloader back.
Now, I can't speak to the validity of that suggestion about the possible corrupt bootloader... I don't know either way whether or not that could be the cause, but if you wanted to at least try it, then my suggestion above would be the way to do it, I would think.
There would be no reason for it to continue to behave like this on a completely stock ROM, other than there being something defective with the phone itself.
It's a clockworkmod issue with daylight savings time. Change your date from automatic to a date before the time change (I just go to Jan) and your phone will shut off and stay off.
"Change your date from automatic to a date before the time change (I just go to Jan) and your phone will shut off and stay off. "
i dont really understand what you mean by change it to a date/time before the time change. i turned off the auto time but dont see where your talking about with setting the date change
I wasn't going to try to help cause I didn't like yer tone. You could say please and thank you for peeps time..
http://forum.xda-developers.com/archive/index.php/t-1104835-p-2.html
Not sure if anyone has run into this yet, if so please share the fix. When selecting "power off" my Inspire 4G just reboots. I can no longer turn off my device. Thanks in advance for the help.
Download quick reboot from the market for now
Sent from my Desire HD using XDA Premium App
Click to expand...
Click to collapse
I stopped reading. But a search is easy on the thread. Google is your friend....
big ups for the useless reply but thanks anyways....CHEERS
oh and there was no tone, but whatever mr internet coolguy THUMBSUP to you. i wouldnt have made this thread if i didnt already search to see if anyone else has had this problem, and it seems noone else has. when the phone was flashed back to stock the problem stopped and as soon as i re-rooted it the problem started again
Projectdwnshft said:
big ups for the useless reply but thanks anyways....CHEERS
oh and there was no tone, but whatever mr internet coolguy THUMBSUP to you. i wouldnt have made this thread if i didnt already search to see if anyone else has had this problem, and it seems noone else has. when the phone was flashed back to stock the problem stopped and as soon as i re-rooted it the problem started again
Click to expand...
Click to collapse
I just linked a guy with the same issue .. Yes its on another rom, but its the same issue....
Download the app....does it work? Problem solved if it does? Or don't.. i could not care less, my phone works normally......
it was a rom issue but guess u didnt read the thread to see that, that app is just another way to reboot your phone, i appreciate the effort but ive tried it many times and it boots/reboots the phone in the same manor the phone boots itself
Scott_S said:
Well at this point, if you think that continuing to try other roms other than what you've already flashed won't help, you might just try flashing a completely stock image, with the stock hboot/recovery, etc., and see if indeed something went haywire with your bootloader, as you mentioned someone had suggested to you.
Try the RUU in the stickied thread, for example. The recent OTA ROM by Attn1 has the hboot removed from it so I don't think that would be a good choice for this attempt, because you want to get the stock bootloader back.
Now, I can't speak to the validity of that suggestion about the possible corrupt bootloader... I don't know either way whether or not that could be the cause, but if you wanted to at least try it, then my suggestion above would be the way to do it, I would think.
There would be no reason for it to continue to behave like this on a completely stock ROM, other than there being something defective with the phone itself.
Click to expand...
Click to collapse
so yeah you had a good point scott. i went ahead and got the phone all back to stock and problem solved, but its not what i want sadly. so i re-rooted the phone and immediately after the re-root i went to turn it off and there it goes again turning itself back on =(
Projectdwnshft said:
it was a rom issue but guess u didnt read the thread to see that, that app is just another way to reboot your phone, i appreciate the effort but ive tried it many times and it boots/reboots the phone in the same manor the phone boots itself
Click to expand...
Click to collapse
So you have re-flashed to stock and the issue went away.
What rom are you flashing after root?
Did you check the MD5sum of the rom?
Have you tried a second rom?
Try just flashing to a stock rom like TCP;
http://forum.xda-developers.com/showthread.php?t=982963
Edit, just read yer above post... None this is going to help. Lol
i havent tried flashing anything, i flashed it back to stock, rebooted worked fine. So i decided to just reroot it. its stil STOCK atm just rooted. its obvious that its a software issue id just love to know what and how to fix it.
When you're flashing to a new rom are you clearing all of your data every time? If not you might want to give it a shot when you try to flash to another rom.
When someone sends me a message they get this message automatically "Command not supported* Battery remaining 95%"
The battery % changes whatever my battery status is. It also shows in my list that I actually sent the message. Anyone have a clue what is going on here?
You've been around for a while, so hau about some more information such as:
When did it start?
Recent changes to the phone (before and after this started happening)? Specifically ROMs and applications.
Anything you've already tried to fix this?
Wulamoc said:
You've been around for a while, so hau about some more information such as:
When did it start?
Recent changes to the phone (before and after this started happening)? Specifically ROMs and applications.
Anything you've already tried to fix this?
Click to expand...
Click to collapse
Well, if any of the information was needed I would have said it. There have been no recent changes, this started today (hence the post). ROM is listed. This happens rather I use stock messaging or another. No fix has been done since I don't know how to fix and have never seen this issue (hence the post). If you can help great, if not that is fine too.
virusmonk3y said:
Well, if any of the information was needed I would have said it. There have been no recent changes, this started today (hence the post). ROM is listed. This happens rather I use stock messaging or another. No fix has been done since I don't know how to fix and have never seen this issue (hence the post). If you can help great, if not that is fine too.
Click to expand...
Click to collapse
Have you started simple - pulling the battery?
Also - any battery status apps installed? https://market.android.com/details?id=net.mobilemonkeys.Battery looks like some have the ability to automatically respond to a text with a battery level - one might be going rogue?? (SMS Commander is another that can do this)
homeslice976 said:
Have you started simple - pulling the battery?
Also - any battery status apps installed? https://market.android.com/details?id=net.mobilemonkeys.Battery looks like some have the ability to automatically respond to a text with a battery level - one might be going rogue?? (SMS Commander is another that can do this)
Click to expand...
Click to collapse
No battery apps. Tried pulling battery, nothing.
If this just started today, there had to be something that triggered it. Have you considered flashing your backup (assuming you have one) to see if it goes away?
pazzo02 said:
Never mind
Click to expand...
Click to collapse
That's about where I'm at.
Seems like an app issue, rather than a carrier/rom/w/e issue.
And given it's obscurity, one is going to have to clean wipe down to base ROM without any installed apps/widgets and see if the issue persists.
If it doesn't, then reloading Apps-Data and see if it persists...
If it does persist before reloading apps-data, then they would have eliminated some unfathomable number of variables...
pazzo02 said:
If this just started today, there had to be something that triggered it. Have you considered flashing your backup (assuming you have one) to see if it goes away?
Click to expand...
Click to collapse
If something triggered it, I have no clue what did. Last night, I charged my phone, woke up for work, the wife sent me a text and that is when it happened. I have a back up yea, which I might have to do.
Did you ever fix this or figure out what it was? My GS3 has started doing this. No ROM, rooted and unlocked. Only SMS app I have installed would be Mighty Text.
Moved to Q & A section.
Sent from my Galaxy Nexus using Tapatalk 2
That is weird!
Here's what I would do...
1. Check for any apps that updated through the Google Play Store overnight
a. If any updated, uninstall and see if that fixed your issue.
b. if none updated, continue to step 2
2. Reboot into CWM Recovery and wipe dalvik cache and fix permissions from CWM
3. Test your device
a. if problem is fixed stop here
b. if problem persists continue to step 4
4. Verify that you do have a nandroid backup of your phone
a. to do this, open file explorer and navigate to the you CWM folder on your SD card and verify a nandroid backup has been made
b. if one is not made, reboot into recovery and do this now!!!
5. Go to settings and reset your device.
6. When phone boots back up, test SMS
a. if issue persists, download CM 7.2 and re flash your rom and go to step 7
b. if issue is fixed, continue to step 7
7. If the issue is fixed, you know its a setting or app on your phone causing the problem.
8. If you have a previous nandroid backup, which you stated you did, flash the nandroid through CWM
9. Test SMS
a. if issue is fixed GREAT
b. if issue is not fixed, wipe your phone and install your apps back one by one from the google play store
Previously when I would flash a CM ROM I would dirty flash it so I didn't have to reinstall my apps back to my phone. If you are flashing nightlies of CM 7.2, I would do a regular flash to wipe the device completely.
On a side note, an Unofficial version of CM10 is available for the Inspire 4G... It will be picked up by the CM Dev team in about a month. That means we will have some Jelly Bean love official from CM.
Cheers!!!
hellow,
first of all sorry if this has bin asked before i tried searching came up with no founds .
entering the thread name gave me no results aswell.
anyways ,
when i changed my theme on my X10 running CM7 it seemed to reset my icons and downloaded apps meaning i was back on to factory settings.
my question is is this normal ? kinda scared to change my themes after that!
or am i going about it all wrong and should i pick ADW themes instead of the theme chooser itself ?
thnx in advance.
it's not.
Changing theme should not touch your app/setting, ony icons/colors/fonts. :|
Probably something goes wrong with that change.
Aha,
well its bin a while since i picked my theme but i seem to recall it going straight to rebooting after loading x amount of time.
after reboot sending me into the settings guide you get when doing a full wipe.
BUT as you said that it shouldn't do that i tried again .
and the result was changing evrything as it should exept offcourse the icons i selected manually so it worked cheers!!
Hi everyone
I have been having a problem with my theme store on my Rooted AT&T S7 and i am unable to download themes. i used to download and install themes before but i cant anymore. whenever i go into the theme store and identify a theme that i want and click download this window pop up "Theme Center mismatch - Theme Center could not support this content. (-1.0.300/S20002)". I have been searching endlessly for a fix and i didn't came across anyone who had or is having that problem. I unroot, factory reset several times, tried to flash to stock but no success with that , trying to find a stock firmware but unable and i created a new samsung account and the problem continues. I feel out of place being unable to theme my phone. Can anyone help please. i would really appreciate it. Thanks.
I assume you're using a Chinese rom - There is an option on Aurora settings to fix this but as that option is on Chinese I don't know where it is exactly. Though, after factory defaults you should not have any issue anymore - at least on me it worked but after I've played with Aurora settings this happened again.
Same problem I have been facing.
I'm having same issue as well after deleting theme center app and data reinstalled theme center straight from the rom I installed still getting same error
As you can see at the title, i just cant use it.
settings stops anytime that i try to change the lock method.
Im using LOS, this start to happen when i change to other ROM (AEX).
I cant make it work with any other ROM.
Here is a little vid.
I already deleted all the cache from settings
https://youtu.be/Jnoip6wIVNM
Someone recently had and fixed that kind of problem, see this post...