Related
Hi
Sorry if this has been cleared up in another thread, but I cannot find the answer to this problem.
I am running Gingerbread 2.3 (Cynogen) on my phone via the file manager method. Everything was fine until one day after I booted back into Android after a normal soft reset - The keyboard would keep hitting "Q" no matter what I pressed. I could not open The browser as I would get an error message.
I thought maybe it was the extended battery I was using, so I reformatted my sd card, re booted gingerbread and everything was back to normal.
Then last week it happened again. I dont remember installing anything new. It is also not the build Im sure, because this did happen a while ago on another Cynogen mod I used.
I am pulling my hair out wondering what to do. There is no point in reinstalling it because it will happen at a seemingly random time again.
Does anyone have any clue or suggestions on how to fix this??
Thanks
Frosty1148 said:
Hi
Sorry if this has been cleared up in another thread, but I cannot find the answer to this problem.
I am running Gingerbread 2.3 (Cynogen) on my phone via the file manager method. Everything was fine until one day after I booted back into Android after a normal soft reset - The keyboard would keep hitting "Q" no matter what I pressed. I could not open The browser as I would get an error message.
I thought maybe it was the extended battery I was using, so I reformatted my sd card, re booted gingerbread and everything was back to normal.
Then last week it happened again. I dont remember installing anything new. It is also not the build Im sure, because this did happen a while ago on another Cynogen mod I used.
I am pulling my hair out wondering what to do. There is no point in reinstalling it because it will happen at a seemingly random time again.
Does anyone have any clue or suggestions on how to fix this??
Thanks
Click to expand...
Click to collapse
Maybe it's a bug in the ROM
Try different rom and see if this problem still persists, if yes, maybe a hardware problem related issue
Cheers
There are a few roms with 100% support for the official extended batteries(s). Your best bet is to go with one of them.
Sent from my HD2 using XDA App
Hello everyone!
I encountered two problems with my HD2 having installed Gingerbread 2.3.7 Nexus-HD. The first one; sometimes, I don't know sure why, and what causes this, but when I lock the phone and I try to unlock it( immediately, I didn't try to wait for longer) it doesn't unlock, but the display turns from dark(as locked) to a little bit grey, as if it would work, but I cannot see what I am doing.
The second one, sometimes, I think after I run a game, or something that requires more power and I press the HOME button, when I try to enter the Menu, it flashes continously.( as if it would change rapidly from Menu, to Home screen)
Where these problems might come from and what can I do in order to fix them ?
Really sounds like a hardware issue, try pressing the buttons hard and releasing a few times.
Did any liquid get on the phone ?
CruceruCalin said:
Hello everyone!
I encountered two problems with my HD2 having installed Gingerbread 2.3.7 Nexus-HD. The first one; sometimes, I don't know sure why, and what causes this, but when I lock the phone and I try to unlock it( immediately, I didn't try to wait for longer) it doesn't unlock, but the display turns from dark(as locked) to a little bit grey, as if it would work, but I cannot see what I am doing.
The second one, sometimes, I think after I run a game, or something that requires more power and I press the HOME button, when I try to enter the Menu, it flashes continously.( as if it would change rapidly from Menu, to Home screen)
Where these problems might come from and what can I do in order to fix them ?
Click to expand...
Click to collapse
Had alot of this issue on slow dying sdcard. My experience is your card have some problems. Try to check your card windows pc, start CMD and type- chkdsk (drive letter of sd card): /x /f or try to format your card with sdformatter pc freeware.
Sent from my HD2 using xda premium
You can try flashing the rom again. Before doing it, remeber to format your sd card. Try other roms too. If the problem persists in evry rom, then try a different sd card. after this the only problem will be your hardware.
Give a thanks if you found this Helpful
I don't think it is a hardware problem, beacause it worked all fine a few days ago, and the phone didn't took any damage in this time. I have this HD2 from a friend and when he gave it to me, I wanted to reinstall the ROM,bacause I wanted not to appear anymore his google account. I am a beginner in HTC and I installed this ROM following a tutorial, but I am not sure I did eveything all right. I wonder how I could erase everything and install a good,stable ROM from scratch, but I need an exact tutorial for this.
Meanwhile, those problem solved by themselves, but now I get the same freezing screen when I try to call or someone calls me. I can hear them, but it just freezes and I cannot do anything, unless I remove the battery. It doesn't happen all the time, but very often...
LE: Right now I'm trying another ROM, I installed a version of CWM of 150 mb( as requested by this ROM) and wiped everything and now it is installing hyperdroid CM7 v5.5.2.
I have to say that with the previous ROM I tried to remove the SD and the same error, so I thought that changing it may be a solution.
CruceruCalin said:
I don't think it is a hardware problem, beacause it worked all fine a few days ago, and the phone didn't took any damage in this time. I have this HD2 from a friend and when he gave it to me, I wanted to reinstall the ROM,bacause I wanted not to appear anymore his google account. I am a beginner in HTC and I installed this ROM following a tutorial, but I am not sure I did eveything all right. I wonder how I could erase everything and install a good,stable ROM from scratch, but I need an exact tutorial for this.
Meanwhile, those problem solved by themselves, but now I get the same freezing screen when I try to call or someone calls me. I can hear them, but it just freezes and I cannot do anything, unless I remove the battery. It doesn't happen all the time, but very often...
LE: Right now I'm trying another ROM, I installed a version of CWM of 150 mb( as requested by this ROM) and wiped everything and now it is installing hyperdroid CM7 v5.5.2.
I have to say that with the previous ROM I tried to remove the SD and the same error, so I thought that changing it may be a solution.
Click to expand...
Click to collapse
Well did you try mtty
http://forum.xda-developers.com/showthread.php?t=623356:confused:
OK. so you want to flash a new NAND rom from scratch? deleting everything in the process. please contact me through the private messaging function i will take you step by step through evrything. all links, steps, etc. arite?
Hi!
I put my MAGLDR on my HD2 and tried tytungs ICS ROM, was not happy with the performance, went back to Boxmax GB Sense build, but after restoring data+apps the phone will start rebooting every few minutes.
I boot andorid from the SD card, so I tried a few versions of the ROM, v8.5 and v7 ([BoxmaX.S3.5.v8.5][Runny HTC Sensation XL][Kmarc2.1 + KTytung r14]).
Same result, sooner or later it'll start rebooting.
The weird thing is that I got another HD2 which is set up identically (magldr+BoxmaX.S3.5.v7) and is working perfectly for months.
I'd appreciate if someone could give me a few ideas on how to debug this?
kosmarnik said:
Hi!
I put my MAGLDR on my HD2 and tried tytungs ICS ROM, was not happy with the performance, went back to Boxmax GB Sense build, but after restoring data+apps the phone will start rebooting every few minutes.
I boot andorid from the SD card, so I tried a few versions of the ROM, v8.5 and v7 ([BoxmaX.S3.5.v8.5][Runny HTC Sensation XL][Kmarc2.1 + KTytung r14]).
Same result, sooner or later it'll start rebooting.
The weird thing is that I got another HD2 which is set up identically (magldr+BoxmaX.S3.5.v7) and is working perfectly for months.
I'd appreciate if someone could give me a few ideas on how to debug this?
Click to expand...
Click to collapse
When it reboots, is it when you're heavily using the phone? Do you feel the back of the phone getting warm before it reboots? Do other SD ROMs work perfectly? Logically since another HD2 with the exact same setup works fine, I would assume that it's something to do with hardware but I don't really know why something like this would happen so suddenly (assuming it worked fine before you changed the ROM)
Nigeldg said:
When it reboots, is it when you're heavily using the phone? Do you feel the back of the phone getting warm before it reboots? Do other SD ROMs work perfectly? Logically since another HD2 with the exact same setup works fine, I would assume that it's something to do with hardware but I don't really know why something like this would happen so suddenly (assuming it worked fine before you changed the ROM)
Click to expand...
Click to collapse
Ah, some more info: Phone was working perfectly with wm6.5+haret, and with magldr+ICS (albeit with ICS bugs) but no reboots ever though it was always overclocked.
As to reboots, they happen for no reason, even when on stock frequency. I don't even have to use the phone, it'll be sitting there sleeping and I just hear the boot up sound.
And here we go: swapped the sd and sim cards, and it is rebooting even in the other HD2, so it's a software OR SD card problem.
I'll move my data to another SD card to exclude it from the equation, but I doubt it's the card.
Ok, so my procedure to setting up a rom is:
after the 1st boot, either log in in to google or not
install TB, restore apps+data
use MyBackup to get SMSes back
Only after or in the middle of that does the rebooting start happening, once it starts it's game over as I only get a minute or two before reboot.
My idea is that something I'm restoring is causing it, but have no clue what it could be.
My last backup was in ICS, but I have no clue how could that be a problem, apps are apps :|
I'm only backing up/restoring regularapps+data not any system stuff.
How could get to the logs from the data.img? Maybe they'll give me a clue about this?
kosmarnik said:
My idea is that something I'm restoring is causing it, but have no clue what it could be.
My last backup was in ICS, but I have no clue how could that be a problem, apps are apps :|
I'm only backing up apps+data not any system stuff.
Click to expand...
Click to collapse
Hmm, so if it reboots after you restore then perhaps you're right, it may be a problem with something you're restoring. Apps may be apps, but some apps are different for ICS and GB (e.g. YouTube, Launchers, Google Chrome etc.) so it's quite possible it may be causing a problem. Try doing the following:
Fresh install the SD build
Restore apps which you KNOW are the same on ICS and GB. This includes all games and many other apps.
For apps which you aren't sure about, download them for the play store.
Manually restore specific app data for the apps you downloaded
Hopefully, if the problem's to do with an app being restored, this will sort it out.
Nigeldg said:
Hmm, so if it reboots after you restore then perhaps you're right, it may be a problem with something you're restoring. Apps may be apps, but some apps are different for ICS and GB (e.g. YouTube, Launchers, Google Chrome etc.) so it's quite possible it may be causing a problem. Try doing the following:
Click to expand...
Click to collapse
Could be, but I only had ICS running for 10 day and did not install any new apps. I don't have any games
Fresh install the SD build
Click to expand...
Click to collapse
Done that ~10 times.
With different approaches. (Restoring more/less)
Tried both newest v8.5 and v7 (gf's [email protected] is running the v7).
Restore apps which you KNOW are the same on ICS and GB. This includes all games and many other apps.
For apps which you aren't sure about, download them for the play store.
Manually restore specific app data for the apps you downloaded
Hopefully, if the problem's to do with an app being restored, this will sort it out.
Click to expand...
Click to collapse
Yeah, I'll have to do that. I'll see if have the backups before ICS and just put the latest data.
What a chore
Tried another SD card, same happens, so at least I know it's 100% software fault.
How could I check the logs?
This is actualy a dual question because I don't know if the two are related. But one problem came up after solving the other.
My wife and I both have a Galaxy S4 i9505. We are Dutch and on the Vodafone network I rooted mine but hers is untouched. Recently after the update I began to experience a bootloop. I thought it was related to the rooting. Keep in mind I didn't flash another rom. Just rooted my S4. The flashing comes maybe later. :silly:
So I did a complete factory reset and much to my surprise I found out in Samsung KIES that the use of my internal memory decreased very much. After reset and new install of all my apps ( and placed them as much as I could on the sd card as before) I had a total use of 1.68 GB from the 9 I got. Before the update I used almost 6 GB of 9 GB
The bootloop however was stopped. And everything works fine. Except acalendar but to that point I will come later on.
Recently my wifes S4 started bootlooping. She also had the update a while ago. Ther only option I could think of was a factory reset. I went on doing that and again all works fine. Exept...... acalendar offcourse
So my questions are:
Has anyone experienced the bootloop after the update?
And could the update causing acalendar to stop functioning.
The problem with acalendar is that the 4x4 widget won't stick to the homescreen. I tried everything but whatever I do, if I hit OK or the return button the screen comes up empty and no widget. The app itsel;f works and the app icon will attach to the homescreen. But I don't want the app icon I want the widget.
can anyone help plz. I allready posted a question on the developers website but so far no comment.
grtz Maverick ®
Just got a reply from the developers. Ok time off I can imagine... but 1 1/2 month vacation???? And ALL of there developers on vacation? Ths makes the app less appealing
QUOTE.......Hi, this is an automatic out-of-office reply. We are sorry, but also developers need some vacation once in a while, thus for deeper technical problems you'll have to wait till mid-November for me to get back to you. For less technical issues Tapir Apps support will get back to you.......
Just got a rply from Tapir support:
Try uninstall and reinstall it... maybe that helps... deuheuuu
Do you have acalendar installed on your sd? Because then that will probably cause those problems.
If so, then I think that also caused the bootloops.
Lennyz1988 said:
Do you have acalendar installed on your sd? Because then that will probably cause those problems.
If so, then I think that also caused the bootloops.
Click to expand...
Click to collapse
Mine was installed on the SD card.. My wifes was not..... still bootloop
tnx 4 reply
Do you use an app or script for moving your apps to the SD? I still think that moving the apps to the SD is causing the bootloops. Based on your information, that is my conclusion. Maybe it was not caused by Acalendar but some other app.
For the problem with Acalendar you should stay in contact with the developers and hope they will fix it. Or you can try to flash a custom rom and hope it will work on those roms.
tnx 4 the reply,
the S4 came with the option to move apps to the sd card after the update. So no external script used. I fixed my problem with aCalendar. I made a backup in Samsung Kies so I reverted aCalender back to my S4 and that worked. But my wife doensn't have the backup. Tomorrow I will try though toput aCalendar back using my own backup. Still finding it strange though...
grtz
Well, here is my story...
My cell phone is a Samsung Galaxy S3 mod. GT-I9300. Locked for Digitel (Venezuela mobile carrier). Android Stock Rom version: 4.1.2.
Preamble:
I bought this cellular a year ago, and it worked flawlessly almost for 12 months straight. I haven't experienced any single freezing or rebooting problem. I downloaded KIES and the program detected that a new version of Android was available for downloading for my phone. Bump! Error. I should have backed up my EFS first before doing the upgrading. BACKUP YOURS, IMPORTANT!)
NOTE: Backup your personal data as well since any ROM installation will remove for sure your personal data and info.
After upgrading and a few days later, my cellphone started to act somewhat funny. I started to got some freezing. To be specifically, my phone started to freeze, the screen just froze and nothing happened when I touched the screen, pressed any button. The only thing worked was to restart the cell (by pressing and holding the POWER button or by removing the batteries). Anyway, the freaking freezing problems continue occurring.
By the way, the warranty expired just a few days ago...
Since I couldn't do anything to stop the freezing problems, I decided to root the cell and install a new version of Android not official for Samsung and test its performance. But before that, I factory reset my cellphone, but it didn't work at all.
I tested several Android version I could find on internet: cm-11-20140....-i9300.zip, specifically, the SNAPSHOT, STABLE, NIGHTLY version. None of that worked, I also tested the cm-10-20... without luck. In fact, the freezing problems with those versions got worse and worse.
Taking the above in consideration, I decided to re-install the stock rom version (ver. 4.1.0) the one that was shipped with my phone when I bought it. You can find these version for any carrier in the world at: sammobile
I flashed and I used it for almost a day or so. During that period of time, I could feel that the freezing issues were gone, not even a freezing event. But unfortunately, I couldn't connect to any Mobile Network!!, so I had just bricked my cell phone !!! I took it to the cell carrier company (DIGITEL) and they could not do anything since my warranty already expired. WTF ! I was alone with my own problem now to sort it out.
SOLUTION !!
By no means I mean this is a cure but I have just stopped getting the hellish freezing and rebooting problems, and I just wanna share my experience with you so maybe I could help you to get rid of this annoying issues for the time being.
Picking up where I was left off, all I had was my bricked phone and a working ROM: ver. 4.1.2, So I decided to to reinstall this version back on my phone and see if it connected to the mobile carrier.
I reinstalled it and of course, after erasing cache partitions and making a factory reset. The procedures to install any ROM on your cellphone you can find it on internet (for instance, youtube may help a lot).
After I installed the version 4.1.2. my cellphone could connect to the mobile carrier once again... phewww!! But the freezing problems continued to appear in the fuc# phone. Well, now the only option I had to test thoroughly my cell was to install any application one after another but testing if the application was the culprit for the freezing issue.
But right after installing the stock Rom, I got a error message when my phone run to the first screen (Home Screen): TOUCHWIZ stopped responding... it lit my LIGHT BULB! I searched the web for the TOUCHWIZ and found out reports regarding many problems with Touchwiz.
Holy craps! The TOUCHWIZ is a BUGGY APPLICATION that comes with the STOCK ROM developed by SAMSUNG.
My friends there is no way to UNINSTALL that application but to use another LAUNCHER. I fired up and decided to download KIT KAT Launcher. Well, I downloaded the launcher and when you first run this application a windows pops up so you can decide what launcher the cellphone may use and the time to use it. I select ALWAYS I press the HOME button, the launcher to use is KIT KAT.
In addition to that I disable various stuffs, follows (you have to go through the setting app):
Disable Touch wiz (delete CACHE, and FORCE STOP)
Disable GPS
Disable Multi Windows
Disable Swipe Lock ( I found my cellphone freezes a lot while this is on)
I don't use a lot of widgets... but only one: The Clock and Alarm widget.
So far (it has passed 5 days straight without freezing). My phone froze on me while I was downloading something (maybe the phone was updating an app) and at the same time I was texting someone. I am suspicious that there is something to do with the downloading system too and the phone that could trigger a freeze.
Anyway, if you have experienced the freezing issue on your Galaxy S3 just like me, then try what I just outlined and give it a test. But do not download a bunch of program at the same time, just pick one by one, and allow some time to test your application and check if your phone is stable before continue with the next app to download and so forth. I have downloaded so far: whatsapp, BBM, sudoku and other games.
Hope you can get rid of the freezing problems just the way I did, any question feel free to ask.
I will continue posting any advance with my phone.
FROYCARD
PS: excuse my standard English.
Flashing a custom rom would help with the freezing issues too!
Try temasek's 4.4 rom its a lot more smooth than ur stock ull feel u have a new phone
You also lost ur carrier signal because ur efs partition was read only or something so backup ur efs before flashing the rom
kariiim said:
Flashing a custom rom would help with the freezing issues too!
Try temasek's 4.4 rom its a lot more smooth than ur stock ull feel u have a new phone
You also lost ur carrier signal because ur efs partition was read only or something so backup ur efs before flashing the rom
Click to expand...
Click to collapse
Nope,, it didn't work with my cellphone. I already tested it. As a matter of fact, I can name you all the ROM I flashed to my cellphone:
cm-11-20131115-UNOFFICIAL-i9300-V2
cm-11-20140104-SNAPSHOT-M2-i9300
cm-11-20140117-UNOFFICIAL-temasek-i9300-V36
cm-11-20140125-NIGHTLY-i9300
cm-10.2.0-i9300
None of the above rom I used stopped the freezing issue, that's why I needed to return to stock rom, and since then I am using it without experiencing any laggy or freezing.
Thanks anyway. :good:
Isnt it possible to create a rom with all of Samsungs bloat ripped off (TouchWiz included) and replaced with stock apps?
The problem is that non stock kernel roms use up a lot more battery than the stock one...
what?
i havent got this
Dude, you seem like a total beginner at this. You might want to start by trying a proper wipe, install a rom like Temasek and install a kernel like Boeffla.
Touchwiz is not the problem for your freezing. Get a custom kernel on there and try undervolting to lower the temp your phone. It may be too hot and may lock up.
You don't have to stick to roms available from your carrier either. You might just want to try any recent 4.3 rom from Sammy.
jinosong said:
Dude, you seem like a total beginner at this. You might want to start by trying a proper wipe, install a rom like Temasek and install a kernel like Boeffla.
Touchwiz is not the problem for your freezing. Get a custom kernel on there and try undervolting to lower the temp your phone. It may be too hot and may lock up.
You don't have to stick to roms available from your carrier either. You might just want to try any recent 4.3 rom from Sammy.
Click to expand...
Click to collapse
Yeah,,, you may be right I am a newbie... but since I stopped using TOUCHWIZ, I have experienced fewer a fewer lock-ups. I dunno what it is happening with my phone, but that is a fact. I am using KITKAT launcher.
The current stock ROM I am using is: 4.1.2 .... (I9300UBEMH2)
I am not familiar with undervolting to lower my phone's temp... maybe you can guide me about using it, or I could search the web for it.
UPDATE: I installed TWITTER Apps yesterday and each time I used it, it froze my phone for 12 min approx. Any suggestion?
Read the freezing thread sticky .
Delete this non working fix as well .
JJEgan said:
Read the freezing thread sticky .
Delete this non working fix as well .
Click to expand...
Click to collapse
Why should I? Are you a moderator of this forum?
Well I just want to update my post.
Yesterday I just wanted to continue figuring this freezing problem out. Since I published my experiences about freezing until yesterday the problem appears to have reduced significantly. I was using stock ROM ver. 4.1.2 flashed with KIES.
But I wanted to continue testing other ROM's. I tried to install a ROM named SAMMY'S ROM developed by guy named JustArchi (that I found in this forum). However I could not install it on my phone (SGS3 - GT-I9300) since it gave me some errors when I tried to install: ERROR STATUS 7
A margin note: This techie or nerdie called JustArchi gave me the boot from his thread for trying to seek help on this error.. so I trashed this SAMMY'S ROM and move on with another solution.
Whatever, I downloaded another official stock Rom ver. 4.3, released by SAMSUNG, intended for IRELAND - I am not from Ireland, but Venezuela (I founded it at SAMMOBILE under the top 10 latest firmware just released). By using ODIN, I flashed my phone, and to tell the truth, my phone feels differently. I haven't experimented any sluggish or lagging, not even a freezing so far (knocking on wood).
For precaution, I am installing one app at the time, and giving it time to see if everything is stable.
Conclusion: to any guys who is getting the annoying freezing, I think you must stick with it until your mobile carrier makes ROM ver. 4.3 available. Otherwise, if you are like me, wanting to work things out for yourself, download any ROM (ver. 4.3 compatible with your phone model) and test it on your phone. Before doing that, you just have to search the Internet for directions to do so, I am not responsible for what you do with your phone. I'll keep updating if another problem arises.
Note: since I am getting some rude comments from senior members who think they are too techie to read newbie's comments, queries, etc. I am not interested in their replies since they are not helping at all, thus I just ignore your lame comments from now on. Just scram.
Dude, you're really not helping anybody here with your information here. I don't know what you think you're sharing. The error 7 pertains to recover error which can be eliminated by installing an alternate recovery version.
I don't care if you're a newbie or not but you are spreading false info.
I'll scram now.