How to fix it? Tablet p3100.Android 4.1.2. Maybe here is some CM mode or another solution. I cant reading from it.Help he please....
PS:Tablet is out of warranty.He was in a service but come back with upgraded/reinstalled firmware with this problem. I think it a software bug...
Turn up the brightness until it stops flickering and then install Screen Filter to lower the brightness. This is not a fix but a solution.
Dmwitz said:
Turn up the brightness until it stops flickering and then install Screen Filter to lower the brightness. This is not a fix but a solution.
Click to expand...
Click to collapse
When i do it i can see little lines running on the screen...
Mine was doing the same thing when i had cm10.1 installed too. My screen was flickering even at the highest setting. Switched over to carbon rom and havent had any issues with it.
ilyacool said:
How to fix it? Tablet p3100.Android 4.1.2. Maybe here is some CM mode or another solution. I cant reading from it.Help he please....
PS:Tablet is out of warranty.He was in a service but come back with upgraded/reinstalled firmware with this problem. I think it a software bug...
Click to expand...
Click to collapse
it is possibly the kernel..
as the screen flickering problem is faced when the power supplied to the device is not proper, try doing this:
1.Use your tab till the battery is red (critically low )
2. Use even more until its 1 %
3. Now open your file manager and start pasting something from internal memory card to external memory card
4. Connect it to pc via usb (when connected to pc via usb the tab does not get charged, neither it gets discharged, but whn you do a heavy process like copy pasting then it gets discharged )
5. This causes the hardware to be confused where to send the power and your screen starts to flicker, as the copy pasting process is given priority to use power .
and you have the flickering problem
Now in a kernel ,
there are scripts written in C , that are responsible for the supply of power to the device, so there might be some blunder in the scripting causing this problem.
so u can do ny one of these to solve it
1. Try finding a kernel that you can flash on your current rom
2. Try flashing the your current rom again (do not forget to wipe)
3. Use the stock rom for your region.
And if none of the three helps then i guess its a hardware problem..
But the changes of that hapening is real low.... Cuz there are resisters that protects the hardware from such things (atleast in all samsung devices they are present) ..
gizmo99301 said:
Mine was doing the same thing when i had cm10.1 installed too. My screen was flickering even at the highest setting. Switched over to carbon rom and havent had any issues with it.
Click to expand...
Click to collapse
What is "carbon ROM" and how to install it.Now it is stock firmware - Android 4.1.2 on my device.
gizmo99301 said:
Mine was doing the same thing when i had cm10.1 installed too. My screen was flickering even at the highest setting. Switched over to carbon rom and havent had any issues with it.
Click to expand...
Click to collapse
where i can find it(carbon rom)? help me please...
Look in the Samsung galaxy tab 2 7" development section, should be on first page. Most current version is from 10 apr
gizmo99301 said:
Look in the Samsung galaxy tab 2 7" development section, should be on first page. Most current version is from 10 apr
Click to expand...
Click to collapse
Do you know any ROMs where screnn flickering fixed............
Related
After rooting and getting CWM recovery 5.5.0.4 installed, a display issue has cropped up on my new BLU Elite 3.8.
It is hard to describe the problem and my keyword choices have not resulted in a match in our forums: screen flicker, auto-dim/auto-brightnes, jumping screen. I will post a video: http://www.youtube.com/watch?v=tyv-IRd2iqk&feature=plcp.
The issue is easily reproduced. It manifests itself only if you selected Reboot. The issue stops while plugged into a pc-connected cable, but not if usb is only plugged into wall. The moment you unplug, it flickers again. The flickering occurs on all screens except when in app-drawer. I also get flickering when I use ROM Manager to reboot into recovery (i.e. the cwm recovery menu is flickering, but not scrolling).
The only workaround is to Power Off, then turn on the phone on.
So, this leads me to my questions: 1) what is so differerent between reboot vs a cold start? 2) why would connecting the phone to a pc temporarily stop it? 3) any suggestions for a solution?
Thank you.
kuapao
bump
Anyone with ideas?
Alternative Roms to try
kuapao said:
bump
Anyone with ideas?
Click to expand...
Click to collapse
My wife has the blu elite and i was looking at the development page for the karbonn A9 because that phone is basically the same device with different branding and it has a development page with various roms. If you run out of options then u could try one of those roms as LAST resort. Let me know how it goes and give me a thumbs up if this helps.
adrianhall06 said:
My wife has the blu elite and i was looking at the development page for the karbonn A9 because that phone is basically the same device with different branding and it has a development page with various roms. If you run out of options then u could try one of those roms as LAST resort. Let me know how it goes and give me a thumbs up if this helps.
Click to expand...
Click to collapse
I already tried other roms for Karbonn A9. The problem has worsened now that a simply power off and on will not fix the problem. The only time the screen stops blinking is when I plug in the USB cable. The screen even flickers when I am in recovery mode.
Would it be possible for you to share rom dumps from your wife's Blu Elite? I am thinking I may need to restore the boot, recovery and system partitions.
Karbonn a9+ display blipping
KARBONN A9+ DISPLAY PROBLEM
HEY GUYS ITS SERIOUS PROBLEM HERE, I CONFIRMED ITS HARDWARE PROBLEM
KARBONN A9+ DISPLAY BLIPPING ALSO HEATING PROBLEM, NOTHING DAMAGED
JUST HEAT UP SOME TIME….
ITS BRIGHTNESS IS GOES VERY VERY DOWN…WHEN I PLUG TO CHARGING IT JUST LITTLE BIT
INCREASE *THE BTIGHTNESS
Please Help me out….
Published by pagefic.in
I flashed the JB ROM on my Tab 7 Plus. After the "succeess" of the flashing as said by Odin v1.85, I tried to turn on the device, but it didn't. I tried to access download mode or recovery mode but it didn't work either. I tried to hold the volume down button and connect the cable to the tablet. That opened the download mode but the screen was "flashing". The rate at which the screen "flashes" keeps increasing until it becomes very fast and the device turns off. I tried to flash a ROM, but Unfortunately it turns off fast that there will be no time for the flashing process to continue.
Any idea what should I do?
what model device do you have and what exact ROM did you flash? and which ROM did you have before flashing.
If you say I dont know to any of these.....
Reply
chrisrotolo said:
what model device do you have and what exact ROM did you flash? and which ROM did you have before flashing.
If you say I dont know to any of these.....
Click to expand...
Click to collapse
My Device is GT-P6200 and I got the GT-P6200 JB ROM for it.
______________
I left my device to charge all night. When I woke up I tried to see if the 'flashing' of the screen still occurs, but it didn't happen. I think I can flash a ROM now
I tried to flash the ROM again and it worked, luckily it was not a hard brick. Problem solved. It is weird that the flashing didn't succeed the previous time. Maybe the battery level was low (about 20%) when I flashed the ROM the previous time, can this be the problem?
yes, also a faulty or non-OEM cable would be the culprit.
SudoHalt said:
I tried to flash the ROM again and it worked, luckily it was not a hard brick. Problem solved. It is weird that the flashing didn't succeed the previous time. Maybe the battery level was low (about 20%) when I flashed the ROM the previous time, can this be the problem?
Click to expand...
Click to collapse
yess. flashing(blinking) screen is how download mode tells you that your battery is low. probably less than 10% since it even turned off by itself.
This Happend To me and I got it BACK
Hello... I totally understand your frustration... This exact same thing happened to me after my battery went dead just after I installed JB...
well here is the kick and it's kind of tricky...
If you want you can call me and I can tell you the instructions, it's complicated but if you follow the steps it will work...
I can also take the time to write it down, but i'm bad a typing.
let me know if you are interested...
Sorry for the late reply. It was fixed after less than a day from starting this thread.
Sent from my GT-I9001 using xda app-developers app
Hi, I am new at this forum and i would like to ask you the following question.
recently i bought a samsung galaxy ace 2 phone and today i decided to try a custom ROM with, being a Linux geek for years...
So i chose Kyrillos Rom for my phone and after several failures i got to understand that before i try to load the custom ROM i had to upgrade my firmware and kernel as described here :http://forum.xda-developers.com/showthread.php?t=1955679
So i used Odin tool , and tried to flash the new firmware as described here :http://forum.xda-developers.com/showthread.php?t=2118119,before proceeding to kernel flash.
Everything went smooth , Odin showed 'pass' indication and my phone after the procedure tried to reboot...and never woke up...
From then i cannot boot my phone at all, i mean neither in usual mode by pressing the power button nor in recovery or download mode. It does not respond to any of those, the screen and the buttons are completely black no matter how many seconds i press them
When i started the procedure my battery level was at 70% and just to be sure i connected it to USB port so as not to empty the battery during the procedure..Now that i connected it to its' charger it does not show the charging indicator
Any ideas as to what happened and how i can fix my problem?
Thank you in advance and keep up the good job!!!
seems motherboard is dead u need to get it replaced anyway did u follow the odin guide carefully cause it seems not
Blackwolf10 said:
seems motherboard is dead u need to get it replaced anyway did u follow the odin guide carefully cause it seems not
Click to expand...
Click to collapse
It seems that i followed the exact directions in the posts mentioned, but my phone is I8160P and not I8160 something that i had not noticed up until tonight,so i think that it has something to do with this, even though i cannot understand how my motherboard died because of the firmware upgrade even thw firmware is made for another model...
VisagenNoir said:
It seems that i followed the exact directions in the posts mentioned, but my phone is I8160P and not I8160 something that i had not noticed up until tonight,so i think that it has something to do with this, even though i cannot understand how my motherboard died because of the firmware upgrade even thw firmware is made for another model...
Click to expand...
Click to collapse
it does have everything to do with that but it seems more like a hardbrick to me so does the phone charge or have u tried a lot of times to boot it or maybe pull the battery out for 5 min then put it back in and try to go to recovery or download if none of these stuff work then i think its dead
Blackwolf10 said:
it does have everything to do with that but it seems more like a hardbrick to me so does the phone charge or have u tried a lot of times to boot it or maybe pull the battery out for 5 min then put it back in and try to go to recovery or download if none of these stuff work then i think its dead
Click to expand...
Click to collapse
Yes i tried both normal boot pressing the power button and recovery - download modes and it did not power on in any of those cases. Also i tried pulling out the battery for 5 - 10 minutes and it did not power on afterwards either.Is this something that happens often because it seems really strange to me. If it has nothing to do with the firmware upgrade and it is a hardware issue then ok, i can sent it to repair it but if i have already lost the warranty due to root and firmware - custom recovery etc.. then what exactly do i have to do..
VisagenNoir said:
Yes i tried both normal boot pressing the power button and recovery - download modes and it did not power on in any of those cases. Also i tried pulling out the battery for 5 - 10 minutes and it did not power on afterwards either.Is this something that happens often because it seems really strange to me. If it has nothing to do with the firmware upgrade and it is a hardware issue then ok, i can sent it to repair it but if i have already lost the warranty due to root and firmware - custom recovery etc.. them what exactly to i have to do..
Click to expand...
Click to collapse
i don't think they will know since the phone won't boot up at all they know by going to download so give it a try and take it to a service and if ur in europe rooting does not affect ur warranty hope this helps
Hi. I hope this is the correct forum. My Samsung Galaxy Tab 2 (10.1) won't shut down after the latest firmware update. I believe I had 4.2.1 and now I have 4.2.2. My device name is is GT-P5113. I plugged the Tab into my computer and Kies opened automatically. It said there was an update for my device so I updated.
All seems to be ok, but now when I choose to "shut down" the tablet shuts down and then cycles back on as if I had just pressed the power button to turn it back on.
I guess it could be worse - it could be refusing to turn on.
Is there a fix for this? Anybody else had this problem?
It is not rooted and I don't really want to do so.
Thanks in advance for any help!
I think u could wipe cache in stock recovery I would do that and see if that fixes it. Hold down vol up and power at the same time till the device reboots into recovery. Dunno how it is on the bigger ones but on the 7" I have to keeo holding the buttons for a second longer after the samsung gtab2 logo comes on to boot in to recovery.
Remember u dont want to factory reset just wipe cache
Sent from my GT-P3113 using xda app-developers app
wipe cache
Thank you for the reply. I tried that and got an "error". I was able to get to recovery mode and choose "wipe cache". It begins and I get an error message.
mymeatb18 said:
I think u could wipe cache in stock recovery I would do that and see if that fixes it. Hold down vol up and power at the same time till the device reboots into recovery. Dunno how it is on the bigger ones but on the 7" I have to keeo holding the buttons for a second longer after the samsung gtab2 logo comes on to boot in to recovery.
Remember u dont want to factory reset just wipe cache
Sent from my GT-P3113 using xda app-developers app
Click to expand...
Click to collapse
beezerhale said:
Thank you for the reply. I tried that and got an "error". I was able to get to recovery mode and choose "wipe cache". It begins and I get an error message.
Click to expand...
Click to collapse
What type of error?? :cyclops:
error
It just read "error" and a image of the little android on it's back.
mythi said:
What type of error?? :cyclops:
Click to expand...
Click to collapse
beezerhale said:
It just read "error" and a image of the little android on it's back.
Click to expand...
Click to collapse
can you take a picture of it ??
mythi said:
What type of error?? :cyclops:
Click to expand...
Click to collapse
mythi said:
can you take a picture of it ??
Click to expand...
Click to collapse
I just uploaded 4 pics to a section of a website that I already have running.
Here is the link:
http://6thgraderocks.wix.com/galazyerror
The images show the end process of updating through Kies (I screen captured), the current tab info, the recovery screen and the error I get when I try to erase cache. Keep in mind, I am able to reboot and my tablet comes on like normal - no issues except when I try to turn it off - it comes right back on.
beezerhale said:
I just uploaded 4 pics to a section of a website that I already have running.
Here is the link:
http://6thgraderocks.wix.com/galazyerror
The images show the end process of updating through Kies (I screen captured), the current tab info, the recovery screen and the error I get when I try to erase cache. Keep in mind, I am able to reboot and my tablet comes on like normal - no issues except when I try to turn it off - it comes right back on.
Click to expand...
Click to collapse
Did you try flashing pit?? did you flash jb bootloader ?? did your device be rooted before flash ?? were you on cm/aokp/pac/slim/etc ??? if yes whic h build did you flash black hawk next kernel ?? <--- may be it what caused it ---> did you try to downgrade to 4.0.3/4.0.4/4.1.2 if yes what happened what did you flash before going to stock rom like mod and etc ???? hope you answer these questions !!
also try this
enable usb debugging
turn off your tab fully
connect tab to pc pull a logcat dsmg ksmg and post them as txt or pastbin
does your tab stuck in recovery loop like rebooting always to recovery sometimes until you compeletly shut down the tab?
if it is under warranty return it to SAMMY TO FIX IT IT IS THEIR FAULT !!
i think it is not hard ware related don't worry !!
This tab is not rooted or tampered with at all. I have no desire to do so.
mythi said:
Did you try flashing pit?? did you flash jb bootloader ?? did your device be rooted before flash ?? were you on cm/aokp/pac/slim/etc ??? if yes whic h build did you flash black hawk next kernel ?? <--- may be it what caused it ---> did you try to downgrade to 4.0.3/4.0.4/4.1.2 if yes what happened what did you flash before going to stock rom like mod and etc ???? hope you answer these questions !!
also try this
enable usb debugging
turn off your tab fully
connect tab to pc pull a logcat dsmg ksmg and post them as txt or pastbin
does your tab stuck in recovery loop like rebooting always to recovery sometimes until you compeletly shut down the tab?
if it is under warranty return it to SAMMY TO FIX IT IT IS THEIR FAULT !!
i think it is not hard ware related don't worry !!
Click to expand...
Click to collapse
I have the exact same problem with BOTH my Galaxy Tab 2 10.1 (Wi-Fi only) It's a software problem for sure...
Also flashing back to 4.1.1 or lower will eliminate the problem
Sent from my GT-P5113 using xda app-developers app
I know I could probably do that (flash back) myself, but I just don't want to. I have bricked a Kindle Fire before while trying to make it do what I wanted it to. I don't want to mess with this Galaxy - it does exactly what I want it to --- surf the web, Netflix/Hulu, and comic books - I'm not too complicated!
I spoke with Samsung yesterday and they said to try a hard reset. That did not work. I spoke with another rep this morning and they are going to repair or replace it for me. He sent a shipping label to my email. This was a gift and I have no receipt. I am VERY pleased with the service from Samsung.
SebasC said:
Also flashing back to 4.1.1 or lower will eliminate the problem
Sent from my GT-P5113 using xda app-developers app
Click to expand...
Click to collapse
So you're going to replace a perfectly good product with a software mistake? I've two tablets, unrooted, 4.2.2 with the same problem... Your better off waiting for a fix..
Why shoukd he feel burdened for something he had no control over. Samsung sent the update, iys not his fault its not doing what it should. If he wants to return it cuz it doesnt turn off as it should he has every right to do so. At least he didnt brick it and is expecting samsung to pay for it.
Sent from my GT-P3113 using xda app-developers app
I had the same problem
Hello,
I registered here to just answer your question since I've been searching around on the internet as well for this problem. I have a Samsung Galaxy Tab 2 10.1 with version 4.2.1. I updated to version 4.2.2 and all hell broke loose. Before I get into it, I had a perfectly working tablet that never had any problems. I installed all updates through OTA or Samsung Kies. It's not rooted.
Anyway, after the update to 4.2.2 my tablet wouldn't turn on. I had to plug it into the wall outlet and then it finally turned on. After playing around with it, some of the widgets didn't work so I thought maybe I should turn it off and reboot it. When I chose "power off" it wouldn't turn off. Instead it would automatically restart. After trying several attempts it still wouldn't turn off so I contacted Samsung. They made me clear the cache and then wipe out the whole system and install a fresh copy of the software. The tablet then went black and now all that was shown on the screen was the little android bot with the error message like how yours is now. It wouldn't boot up to the main screen anymore.
So I had to return the tablet back to Samsung yesterday and they are going to attempt to fix it. It's still under warranty but I'll be pissed if I won't be able to install the new software on my tablet since I like the new updates they did for it.
Anyway, sorry for my long response but I hope this helps you out even though nothing was resolved. I'll post what happens once I get back my tablet.
Similar "Reboot after turn off" issue
I have the same "can't turn off" issue on my stock Tab 2 10.1 updated to 4.2.2 via Kies. After turning off and confirming on the screen, the tablet simply turns back on. This typically happens several times in a row before something happens and it stays off. I emailed Samsung to request support.
d86 said:
Hello,
I registered here to just answer your question since I've been searching around on the internet as well for this problem. I have a Samsung Galaxy Tab 2 10.1 with version 4.2.1. I updated to version 4.2.2 and all hell broke loose. Before I get into it, I had a perfectly working tablet that never had any problems. I installed all updates through OTA or Samsung Kies. It's not rooted.
Anyway, after the update to 4.2.2 my tablet wouldn't turn on. I had to plug it into the wall outlet and then it finally turned on. After playing around with it, some of the widgets didn't work so I thought maybe I should turn it off and reboot it. When I chose "power off" it wouldn't turn off. Instead it would automatically restart. After trying several attempts it still wouldn't turn off so I contacted Samsung. They made me clear the cache and then wipe out the whole system and install a fresh copy of the software. The tablet then went black and now all that was shown on the screen was the little android bot with the error message like how yours is now. It wouldn't boot up to the main screen anymore.
So I had to return the tablet back to Samsung yesterday and they are going to attempt to fix it. It's still under warranty but I'll be pissed if I won't be able to install the new software on my tablet since I like the new updates they did for it.
Anyway, sorry for my long response but I hope this helps you out even though nothing was resolved. I'll post what happens once I get back my tablet.
Click to expand...
Click to collapse
Reboot issues
avm1 said:
I have the same "can't turn off" issue on my stock Tab 2 10.1 updated to 4.2.2 via Kies. After turning off and confirming on the screen, the tablet simply turns back on. This typically happens several times in a row before something happens and it stays off. I emailed Samsung to request support.
Click to expand...
Click to collapse
I had a live chat with Samsung just now. It is interesting that the tech I communicated with did not know of any issue with the rebooting and there was no mention in their system that a problem even existed (so I sent a link to this page to him).
Anyway, the end result was that it I wanted to fix the problem, I would have to restore Android through KIES:
samsung.com/us/support/faq/FAQ00052690/61266/GT-P3113GRSXAR
This will delete all data and get back to Android 4.2.1
Since I have already have seen issues with KIES, I wonder if it wouldn't be easier to just use ODIN? Any suggestions from those who might have tried both?
update #1
Just wanted to give an update. Samsung sent me an email yesterday stating they "fixed" my tablet. I should be getting back my tablet by the end of this week or early next week. The receipt said that it was a "software problem" and they reinstalled new software with the latest update. I'm just wondering if it's 4.1.2(that worked fine with my tablet) or 4.2.2(which messed up my tablet)
I'll give another update once I get it in my possession.
---------- Post added at 05:33 PM ---------- Previous post was at 05:28 PM ----------
SamsungTab2User said:
I had a live chat with Samsung just now. It is interesting that the tech I communicated with did not know of any issue with the rebooting and there was no mention in their system that a problem even existed (so I sent a link to this page to him).
Anyway, the end result was that it I wanted to fix the problem, I would have to restore Android through KIES:
samsung.com/us/support/faq/FAQ00052690/61266/GT-P3113GRSXAR
This will delete all data and get back to Android 4.2.1
Since I have already have seen issues with KIES, I wonder if it wouldn't be easier to just use ODIN? Any suggestions from those who might have tried both?
Click to expand...
Click to collapse
I tried this when I chatted with Samsung and it messed up my tablet completely where as when I rebooted my tablet it would show an android robot with "error"
Plus, I don't know about you but I don't want to have 4.2.1. I want to have the 4.2.2 update on my tablet. It's a much more sleeker interface. Just the only problem is that it wouldn't shut off. I will see what happens once I have it. If 4.2.1 is on my tablet I will try again updating the software to 4.2.2.
There are some problems like boot fail or can't poweroff I've seen at some posts, they do the same things:
1.flash a 4.2.2 stock rom
2.have some problems: boot fail or can't poweroff eg..
3.boot to recovery and want to wipe the cache
4.get a error with the robot logo lie down
I found a post mentions that he've fixed this problem by using odin 3.07 flash the 4.2.2 stock rom with a matched kernel boot file.
The post is here, it's in chinese:
http://b.it168.com/thread-4690107-1-1.html
His solution is get to this site to find the 4.2.2 stock rom and matched kernel file of your device and use odin 3.07 flash them:
http://samsung-updates.com/
do it at your own risk maybe solve your problem.
Update #2
So I got my tablet today and I turned it on to see that it had android software 4.1.1. Then the software update icon popped up and I updated to 4.2.2. Then the same problem happened again like the last time. The tablet wouldn't turn off and it would automatically restart. I contacted Samsung Support again and they had me do a factory reset which then fried my tablet again. It doesn't turn on. So now I have to send it back again for a 2nd time. This time they said they may have to replace the tablet either with the same tablet or a different model tablet. But I stressed to them to make sure to update the tablet this time to 4.2.2 so they can see the problem I'm facing. We shall see next week I guess what happens.
while playing games with my android tab, my tab lag suddenly . then, the tab will power off by itself . and suddenly, the tab will come out with the word 'ANDROID' with a black background . and it will be like that for the whole day until it battery run out . it always happen frequently to me . so, how to fix this problem ?
calayz said:
while playing games with my android tab, my tab lag suddenly . then, the tab will power off by itself . and suddenly, the tab will come out with the word 'ANDROID' with a black background . and it will be like that for the whole day until it battery run out . it always happen frequently to me . so, how to fix this problem ?
Click to expand...
Click to collapse
It sounds like your tab overheated or it has a problem with one of the components.
Factory reset.
Problem persists.
Contact manufacturer.
To restart android manually you can hold volume up + power button combo.
Lgrootnoob said:
It sounds like your tab overheated or it has a problem with one of the components.
Factory reset.
Problem persists.
Contact manufacturer.
To restart android manually you can hold volume up + power button combo.
Click to expand...
Click to collapse
Lgrootnoob;48151871]
how am i gonna do the factory reset? i'm kind of new with android world . and i already did what u told me to do . hold the volume up+power button combo but nothing happen .
p/s: my tab haven't been rooted yet ...
calayz said:
Lgrootnoob;48151871]
how am i gonna do the factory reset? i'm kind of new with android world . and i already did what u told me to do . hold the volume up+power button combo but nothing happen .
p/s: my tab haven't been rooted yet ...
Click to expand...
Click to collapse
Go to settings > privacy > factory reset.
the key combo is only for getting out of a rut.
And you have to hold it to make it restart.
Lgrootnoob said:
Go to settings > privacy > factory reset.
the key combo is only for getting out of a rut.
And you have to hold it to make it restart.
Click to expand...
Click to collapse
already done that.. nothing happen too.
btw, i already did the 'factory reset' thing .. i lost all of my apps in the tab,,then , i download games,apps and i install it to the tab ..
unfortunately,the same thing still happen to me .the tab will power off by itself . and suddenly, the tab will come out with the word 'ANDROID' with a black background . and it will be like that for the whole day until it battery run out . how to solve this ... ? should i change it room..? if should, how am i going to change the rom? beside, im not rooted ... any idea(s)??
calayz said:
already done that.. nothing happen too.
btw, i already did the 'factory reset' thing .. i lost all of my apps in the tab,,then , i download games,apps and i install it to the tab ..
unfortunately,the same thing still happen to me .the tab will power off by itself . and suddenly, the tab will come out with the word 'ANDROID' with a black background . and it will be like that for the whole day until it battery run out . how to solve this ... ? should i change it room..? if should, how am i going to change the rom? beside, im not rooted ... any idea(s)??
Click to expand...
Click to collapse
Do you have the latest updates if any?
My point is that you should fact reset then wait a couple of days and see if it reboots etc.
Don't install any apps. (It is a test, you want to see if stock android causes no problems.)
You want to determine if an app is your problem.
Lgrootnoob said:
Do you have the latest updates if any?
My point is that you should fact reset then wait a couple of days and see if it reboots etc.
Don't install any apps. (It is a test, you want to see if stock android causes no problems.)
You want to determine if an app is your problem.
Click to expand...
Click to collapse
guess what? it happen again .. i already did what u told me to do , so here, i really need ur help on how to change the ROM.. a lot of my friend said that the ROM might be the problem ... hence, i really need ur help .please teach me how to change the ROM ...
calayz said:
guess what? it happen again .. i already did what u told me to do , so here, i really need ur help on how to change the ROM.. a lot of my friend said that the ROM might be the problem ... hence, i really need ur help .please teach me how to change the ROM ...
Click to expand...
Click to collapse
model number or name?
Lgrootnoob said:
model number or name?
Click to expand...
Click to collapse
model number=k105
name=7" Smart Pad Voice Call D4
Andriod 4.1 Jelly Bean
MT6577 CPU
Dual Core 1.0 GHz
RAM 512 MB
ROM 4GB
3G WCDMA / 2G GSM
Bluetooth
Dual Camera
Resolution 800 x 480
Your SOL man. :crying:
If you can find your support and downloads page from your manufacturer then maybe you can check to see if they have any updates.
Or it is a hardware defect so you must contact your manufacturer for a repair or replacement.
Nothing else to see here.