I'm running JAChero 2.3.3 and just have a few questions to see if what I'm experiencing is normal.
Firstly, when I'm at the home screen, the trackball cannot select any of the apps, just switch from one screen to the other. Kind of annoying sometimes cause I've gotten used to using it more than the touchscreen. I'm assuming this is a problem on all hero builds, but is there any way it can be fixed?
Secondly, every time I do an adb reboot, the phone boots up then about 5 or 10 seconds later, reboots again. Not that big a deal but just wondering whats happening.
That's really all the problems I have with it, everything else runs great.
Yes the first thing about selecting apps is normal. The second thing, could you be more clear? Do you mean like the htc screen shows again? or does your phone like actually vibrate and go through the 3 screens?
Yes the first thing about selecting apps is normal.
Click to expand...
Click to collapse
Thats depressing
The second thing, could you be more clear? Do you mean like the htc screen shows again? or does your phone like actually vibrate and go through the 3 screens?
Click to expand...
Click to collapse
After rebooting through adb, the phone goes through all the boot loaders, then it starts loading, and while its loading it reboots itself. The once it reboots, everything works fine.
The rebooting is not normal. Dont really have a solution except a fresh format of your ext partition, a data wipe, and then a reflash.
The rebooting is not normal. Dont really have a solution except a fresh format of your ext partition, a data wipe, and then a reflash.
Click to expand...
Click to collapse
I think I'll just live with it, don't really want to go through all the set up again and it isnt really causing any harm.
Thanks for the quick answers alritewhadeva
No problem Cash. Any other questions just PM me
Related
Well I know it happens, and it happens to multiple people but I haven't pegged an answer why phones will just randomly soft reboot like this.
But more importantly I'm wondering why mine soft rebooted into a boot loop?
Currently reflashing the rom Open Eclair hoping it works cause I don't want to loose all the data BUT it looks like my phone won't go past the G1 screen now.
Hmf.
Well what do you know, lost all my data. That's fantastic.
Wipe + Flash.
Icebergxx said:
Well what do you know, lost all my data. That's fantastic.
Wipe + Flash.
Click to expand...
Click to collapse
:/ good thing contacts and stuff are in the cloud
Ever since i manually updated to frf91 sometimes when i try to wake my phone my screen freezes an i can't unlock it also when i try to power my phone back on it will vibrate 7 times an it wont come on. I guts take the battery out an put it back it to get my phone to turn back on. I've never had this problem until i manually updated my phone. I did a factory reset an it helped for a while but the problems come back. Has anyone had this problem an does anyone know how i can fix this? I'd really appreciate any help i can get
Help please
Is the bootloader unlocked?
this seems to be a common issue with FRF91, although most people's phones will unfreeze after a minute or two, does your backlight turn on and off when you press the power button?
Jep4444 said:
this seems to be a common issue with FRF91, although most people's phones will unfreeze after a minute or two, does your backlight turn on and off when you press the power button?
Click to expand...
Click to collapse
whether it unfreezes after a minute or two depends on what it's doing..there have been many times where i have to pull battery...........
rensky said:
whether it unfreezes after a minute or two depends on what it's doing..there have been many times where i have to pull battery...........
Click to expand...
Click to collapse
ya i have had to as well but most of the time it wakes just fine
No my bootloader is not unlocked an yea the backlight will come on but it won't unlock. Ive never tried waitin a min to see if it fixes itself i just usually pull the battery when it happens an sometimes when i try to turn my phone back on it does the 7 vibrating thing. Like i said before it never happened until frf91
I have an app called AutoKiller installed. It tweaks the Android system's inner memory management routines. it was set to something other than default. I changed it back to default, and haven't had a problem since. if you have this installed, maybe try and switch it to default settings.
Sounds like a data issue. A factory reset only wipes user data, You must wipe in recovery to wipe rom data. Also make sure you have the correct radio for the build especially coming from lower build. If that's the issue flash radio first to support the build. Then flash the rom.
Sent from my Nexus One using XDA App
How do u wipe in recovery? Yea im a newb lol
Also if i wipe in recovery will i still be on 2.2 or will i have to update to it again?
Hey guys,
I could need a bit of help! It's now the third time I'm having this problem, don't ask me why. I've got the feeling that I read the whole forum here, but didn't find anything similiar.
The 1st time I didn't change anything (ok, rooted it, but nothing else)
The 2nd time I overclocked it slightly (~850-900 MHz)
Now I'm using MIUI.
But back to the problem:
I'm unable to use the keyboard, every time I'm sliding open the keyboard (even when it's turned off), it "crashes". The screen stops working or it freezes, the only way to turn it off is taking out the battery.
However, the bigger problem comes now: I'm barely able to restart it. It tries booting, but is restarting all the time or the screen is just turning on (in some angles you see that it is turned on but it's black). After many retries, it starts working, sometimes the bootloop is running 15min or i have to manually restart it 10 times or more. The strange thing is that the keyboard works fine, nevertheless I have to choose between using it opened (taking it with me becomes difficult ) or closed...
...the main problem now is flashing a new Rom, I'm currently trying it through the android sdk and adb, but using the power-button + x is easier
I don't think that I can solve the problem, I sent the device two times back (warranty till may 2012), but maybe someone here knows a bit more. My guess is that one of the sensors is broken, or some parts of the display that should manage the sliding process...
Anyway, thanks for your attention!
Web
If you already have Rom Manager, just click Reboot into Recovery..
inches0 said:
If you already have Rom Manager, just click Reboot into Recovery..
Click to expand...
Click to collapse
Tried to use one a time ago, but it wasn't working right....
However, now I'm not even able to boot it, the screen just flashes and turns off itself before trying to restart a few moments later....guess I lost my Milestone
Sbf back to stock?
taptaptouch said:
Sbf back to stock?
Click to expand...
Click to collapse
the computer isn't finding it anymore...I'll back up the data and try use my warranty... I hope that they don't complain about MIUI...
But I'm still not getting the point, why my mobile had these issues three times, although they "repaired" it twice...and nobody else is having the same problem
Sorry for the vague title, but I couldn't think of a concise way of describing this.
I have a T-Mobile HTC One with the GPe ROM installed on it. I'm on 4.4.2 and using ART. I woke up this morning to find my phone in a boot loop. It would come up with the screen that shows the "Google" logo and the icon showing my phone is unlocked, remain on that screen for longer than normal, then reboot and do it again before getting to the actual ROM boot sequence.
I held down the power button to shut the phone off. When I turned it back on, it made it to the ROM boot, where the four colored circles fly around, but then came up with a screen asking for my disk encryption password. I've never set up encryption on the phone. I didn't want to try passwords I use in case this was some kind of phishing, though I'm not sure how that would be possible. At this point I wasn't really in the mood to do much troubleshooting so I did a factory reset from the bootloader and it seems fine now.
I'm just wondering if anyone knows what happened.
kernco said:
Sorry for the vague title, but I couldn't think of a concise way of describing this.
I have a T-Mobile HTC One with the GPe ROM installed on it. I'm on 4.4.2 and using ART. I woke up this morning to find my phone in a boot loop. It would come up with the screen that shows the "Google" logo and the icon showing my phone is unlocked, remain on that screen for longer than normal, then reboot and do it again before getting to the actual ROM boot sequence.
I held down the power button to shut the phone off. When I turned it back on, it made it to the ROM boot, where the four colored circles fly around, but then came up with a screen asking for my disk encryption password. I've never set up encryption on the phone. I didn't want to try passwords I use in case this was some kind of phishing, though I'm not sure how that would be possible. At this point I wasn't really in the mood to do much troubleshooting so I did a factory reset from the bootloader and it seems fine now.
I'm just wondering if anyone knows what happened.
Click to expand...
Click to collapse
Just don't use ART for now, stay with Dalvik. Much stable atm.
alray said:
Just don't use ART for now, stay with Dalvik. Much stable atm.
Click to expand...
Click to collapse
I wasn't planning on switching back to it. But that's not really answering my question about if anyone knows what happened. Unless you're saying that this is a known problem that happens to people who use ART, but it sounds more like you're just saying since I was using ART and something went wrong, it's a good chance that was why.
kernco said:
I wasn't planning on switching back to it. But that's not really answering my question about if anyone knows what happened. Unless you're saying that this is a known problem that happens to people who use ART, but it sounds more like you're just saying since I was using ART and something went wrong, it's a good chance that was why.
Click to expand...
Click to collapse
What most likely happened is ART corrupted the system and it forced a bootloop. You may have to full wipe and reflash. I would also advice to stay away from ART. It is not made for users.
zelendel said:
What most likely happened is ART corrupted the system and it forced a bootloop. You may have to full wipe and reflash. I would also advice to stay away from ART. It is not made for users.
Click to expand...
Click to collapse
I did a factory reset and so far everything is fine. Are you saying there might still be an issue and I should wipe and reflash to be safe?
kernco said:
I did a factory reset and so far everything is fine. Are you saying there might still be an issue and I should wipe and reflash to be safe?
Click to expand...
Click to collapse
I would just to be safe. Mainly with the pre-Alpha tag of the ART compiler. I mean it may not even make it to be official.
Hi, this happend already to me few times so I decided to put it on here.
Sometimes when I pick up my phone and try to unlock it nothing happens, fingerprint and button all the same it looks like it completely Off. Then i have to press few times a button to actually start it and it's booting. There is huge battery loss after it boot up. See image.
I am in Stock 4.0.2 no root just few standard apps installed. Nothing fancy. This happend already few times to me. I left the phone locked and when I want to unlock its dead. Also it is behaving weirdly, when I turn it off manually I just need to press longer a button and it's turning on, but here I need to press it few times to work.
Does it happen to anyone else?
terragady said:
Hi, this happend already to me few times so I decided to put it on here.
Sometimes when I pick up my phone and try to unlock it nothing happens, fingerprint and button all the same it looks like it completely Off. Then i have to press few times a button to actually start it and it's booting. There is huge battery loss after it boot up. See image.
I am in Stock 4.0.2 no root just few standard apps installed. Nothing fancy. This happend already few times to me. I left the phone locked and when I want to unlock its dead. Also it is behaving weirdly, when I turn it off manually I just need to press longer a button and it's turning on, but here I need to press it few times to work.
Does it happen to anyone else?
Click to expand...
Click to collapse
Honestly, there's not enough information to understand exactly why it's happening. You need to get a logcat in the time before the reboot; unfortunately, logcats get erased during a reboot so it might be a little tricky getting it if the reboot is seemingly random. Someone had posted this as a possible way of getting the log:
"Retrieving the logs is tricky, since the log cache gets erased on reboot. If the phone reboots even while sitting on a charger, try running adb logcat continuously (you will need Android SDK and USB drivers installed and configured on your PC.) When the phone reboots, look at the last several pages in the command prompt window for any errors or abnormalities."
Click to expand...
Click to collapse
Otherwise, it's hard for anyone to help. I'm not much help in actually figuring out the issue, but I know if you can get the log, someone else probably can help.
For more information on logcats: Logcat Tutorial
Yeah I was trying to connect it to PC but nothing, so it is turned off. I will try next time to run command when turning on, maybe there will be something but I do not see it working before it gets erased. I was hoping that anyone else is having this problem so it might be rom related. It is completely random so you can;t guess when it happens.
I had it only few times so it's not super annoying but still it is not normal behavior. In addition it is weird that battery went from 55% to 33%, just phone reboot will not drain that much... I hope there is nothing wrong with the phone itself.
terragady said:
Yeah I was trying to connect it to PC but nothing, so it is turned off. I will try next time to run command when turning on, maybe there will be something but I do not see it working before it gets erased. I was hoping that anyone else is having this problem so it might be rom related. It is completely random so you can;t guess when it happens.
I had it only few times so it's not super annoying but still it is not normal behavior. In addition it is weird that battery went from 55% to 33%, just phone reboot will not drain that much... I hope there is nothing wrong with the phone itself.
Click to expand...
Click to collapse
Check in advanced to see if schedule off is on
Nope it's off
Happened to me to on 4.0.2. Rebooted twice a day.
Solution to me was Qualcomm flash back to stock 3.5.1 and uodate from internal to 3.5.4. OTA 4.0.2.
The theard "how to unbrick".
Not one reboot until now in days.
I think I found a culprit responsible for it. It is Hill Climb 2 game which doesn't close properly sometimes and I think it causes some kind of crash in the system. Is it possible?
terragady said:
I think I found a culprit responsible for it. It is Hill Climb 2 game which doesn't close properly sometimes and I think it causes some kind of crash in the system. Is it possible?
Click to expand...
Click to collapse
It's possible. Not necessarily the reason, but it might be. Either uninstall the app or freeze it using Titanium. Greenify might also work, but that allows the app to start itself up and potentially continue the issue. See if that stops the crashes for a couple of days.
The problem is that it doesn't happen often and only when I quit the game and lock the phone immediately after that. I am not sure if that's a reason though, just guessing because it happens after this last time. I will uninstall this game anyway, it's just time eater