So I flashed my phone to the HyperDragon III ROM a few months ago. Everything works smoothly and I had no problems at all. Only small issue was the keyboard lag and that issue was addressed in a separate post.
After using the Keyboard Lag fix, my phone does not fully load. I get to the splash screen and everything and then the Start Bar loads as well as the bottom Calender and Contacts menu. The screen will display my background and it will say "Tap Here to launch TouchFlo". I tap there and nothing happens.
I've been patient and I let it sit there and nothing happens. I can get to my text messages but it runs unusually sluggish and will display an overview of all messages but when I try to open a specific message, it freezes up.
This is actually the second time this has happened. The first time I removed the Keyboard Lag CAB but the issue continued. I left the phone alone and reset it a few times and miraculously it started working fine.
I have since removed the Keyboard Lag CAB completely yet it has still happened. Anybody else have the same problem or have a solution? Any help would be great.
Never flashed HDIII rom's so I have no idea why you are having that problem. Have you already post this issue on the rom's threat?
not-available said:
Never flashed HDIII rom's so I have no idea why you are having that problem. Have you already post this issue on the rom's threat?
Click to expand...
Click to collapse
Not on the HDIII thread. I did originally post my problem on the Keyboard Lag thread. 10 minutes after posting the first time my phone went back to normal so I went back and edited the post.
So try it on the HDIII threat. That's the best where you can get help related with that rom.
Also, maybe some other user had already that problem and have some solution or is waiting for some. Ah, before post the question, that some time to read the full threat... your answer can be already there.
Thanks. I just figured I would post. I've been reading the thread for a while now. Its over 900 pages so I thought I would ask first
You can also try to do a search on that threat http://forum.xda-developers.com/showthread.php?p=3102963&nojs=1#goto_threadsearch
Happy New Year
So my phone just started working again. After about an hour or so of resetting and stuff it displayed Lauching TouchFlo and its normal again. I'm just afraid to ever turn it off again.
did anyone solve this problem?! cause mine just randomly stopped launching touchlo and I dont know how to get out of it?!
Closing thread
Please post issues with HyperDragon rom in the HyperDragon thread, instead of opening new ones.
Peace,
Joshua
Hi,
Please move this thread to the right section on the forum if it is not already. I got my new MT3G and flashed it with Cyan's latest mod it was working great. Then I flashed KSpec_BlurSpec_v1.00. One thing more i did here is move the media/audio to my phone too and at that time the phone just rebooted. Since then my phone goes to sleep and it wont wakeup with MENU or none of the buttons will work, only option is to take the battery out and put it back in. When it goes to sleep i can still see the green light flashing which means phone did not power off.
I dont know if it maters or not but have noticed if i am connected to wifi and no cell signal it wont happen, but if i get the cell signal it reappears.
I moved back to cyan's latest flash, cyan's stable, wiped, reformated sdcard everything i can think of but problem is still there.
Please suggest or help if you came across something similar. I am planning to move back to stock rom and see if it happens on that too.
Thanks,
There are all kinds of wake issues with cyan's updates and the mytouch.
I found running the overclock widget fixed a lot of flicker and hesitation apon awakening.
Usually problems that occur are from not wiping and or alteration of original files.
Try always including a logcat when posting problems. It usually tells right away what's causing what to act funny. I believe Cyan adds a log report app to his ROM as well.
Pm me if I can be of help.
I would post this in the Developer forum, in reply to a poster who has the same problem, but I just registered and therefore do not meet the requirements to post there.
I'm wondering if anyone else has observed this behavior. In short, I installed TriForceROM 3.0 (after performing a "Wipe User Data" operation in TWRP 2.6.0.0) and all was well for about 12 hours. During the ROM installation, I chose the "Standard" option, as I believe it's called. (I didn't elect to customize anything.)
After 12-18 hours of having the ROM installed, I noticed that my phone was simply powered-off. I hit the power button and nothing. Then I held-down the power button, which is how I normally power-on the device, and then realized that the device was, in fact, powered-off when I came back to it after a few hours of being in the other room.
After powering-on the device, the same thing happened a few hours later, and the issue seems to be occurring more and more frequently as time passes.
I have not changed any of the ROMs settings, and I haven't installed any type of third-party "tweaking" app.
Another individual has the same problem:
http://forum.xda-developers.com/showpost.php?p=43942167&postcount=1466
Could this be due to kernel, power, or CPU settings? I noticed that when I opened KTweaker for the first time, the application warned me:
"Your KThermal values do not match current, Apply values?"
and
"Your vibration Strength does not match current, Apply Vibration Strength value?" (this one seems unrelated)
The CPU temperature seems to hover around 45 degrees Celsius. (Is this a normal range?)
Another observation is that when I long-press the Home button (to bring-up the app-switcher), I see a little Android icon with the title "MIPErrorActivi...". If I click on it, I'm simply dumped to the Home Screen. I don't know if this is at all related.
Thoughts or suggestions, anyone?
My phone is model SPH-L720.
Thanks in advance!
I went into KTweaker and clicked "Load Defaults" and rebooted, and everything seems to be stable. No reboots in 18 hours or so.
Also, the ROM author has mentioned this issue, as well as an interim fix (related to the KT kernel), and says that he will release v 3.1 within a few days, which should fix the issue entirely.
Good stuff!
UPDATE:
Well, the phone rebooted itself, eventually, so setting KTweaker settings to defaults was not the solution.
However, I downloaded the kernel update that the ROM author suggested ( http://forum.xda-developers.com/showthread.php?t=2288309 ) and that does seem to have fixed the problem. No reboots in over two days. Yay!
An interesting aside is that with the new kernel and accompanying KTweaker app, the warnings that I was receiving with the old kernel when launching KTweaker disappeared. All is well!
DrRichardQuack said:
I went into KTweaker and clicked "Load Defaults" and rebooted, and everything seems to be stable. No reboots in 18 hours or so.
Also, the ROM author has mentioned this issue, as well as an interim fix (related to the KT kernel), and says that he will release v 3.1 within a few days, which should fix the issue entirely.
Good stuff!
UPDATE:
Well, the phone rebooted itself, eventually, so setting KTweaker settings to defaults was not the solution.
However, I downloaded the kernel update that the ROM author suggested ( http://forum.xda-developers.com/showthread.php?t=2288309 ) and that does seem to have fixed the problem. No reboots in over two days. Yay!
An interesting aside is that with the new kernel and accompanying KTweaker app, the warnings that I was receiving with the old kernel when launching KTweaker disappeared. All is well!
Click to expand...
Click to collapse
Thanks for noting this. I actually started my account for the same reason, but haven't had enough useful input to get the posts to leave feedback in the dev forums. I sure don't want to spam useless posts :angel:
Lsd-Pulsar said:
Thanks for noting this. I actually started my account for the same reason, but haven't had enough useful input to get the posts to leave feedback in the dev forums. I sure don't want to spam useless posts :angel:
Click to expand...
Click to collapse
Haha. Well, glad I could be of help and that we both garner a couple of "useful posts" out of it.
I'm pretty sure that the reboots continued for me (although, less frequently with the kernel patch in place), but upgrading to TriForceROM 3.1 seems to have fixed the issue altogether. It's worth noting that I chose a different kernel this time (I forget what it's called; the name is four letters, all capitals). No reboots in the first 24 hours.
I doubt it makes a difference, but I also upgraded to the MF9 firmware from Samsung. Happy to answer any questions in that regard, too.
DrRichardQuack said:
Haha. Well, glad I could be of help and that we both garner a couple of "useful posts" out of it.
I'm pretty sure that the reboots continued for me (although, less frequently with the kernel patch in place), but upgrading to TriForceROM 3.1 seems to have fixed the issue altogether. It's worth noting that I chose a different kernel this time (I forget what it's called; the name is four letters, all capitals). No reboots in the first 24 hours.
I doubt it makes a difference, but I also upgraded to the MF9 firmware from Samsung. Happy to answer any questions in that regard, too.
Click to expand...
Click to collapse
I would wager that you moved over to AGAT's. Several users reported lag with that kernel, so I stuck with KT.
After more reboots and a lot of tweaking, I've got my issue nailed down. Raising the voltages on the low end cpu frequencies (where a phone would normally be with screen off) has corrected the stability issues. I also had to up the voltages at the high side. That helped Antutu to run for a while, but now that's crashing back to desktop for me. When it does run, I usually hit around 25,000 with the Triforce 3.0 + Ktoons kernel with overclock enabled. I have not overclocked the GPU (yet). Running KTmod, but not crossbreeder.
I may back this all up tonight and reflash with Triforce 3.1. I've been fighting battery issues: Google Location Services and Android Widgets Pro seem to be behaving badly.
I feel like I'm very close to a fast, stable rom install with good battery life. Once I get there, I'll wait a couple months until the existing ROM's and kernels are polished a little more. And now I'm one post closer to being productive in the Dev forum.
That's the one; AGAT's kernel. I haven't noticed any sluggishness with the ROM's (and or kernel's) default settings. So, I'm happy!
No random power-downs or any other abnormal behavior since upgrading to 3.1 and switching to AGAT's three days ago.
I don't know if it was upgrading from 3.0 to 3.1 or switching kernels that fixed the random power-downs; I'm just glad I have a very fast and stable ROM at this point.
My battery life has been good. Moderate usage throughout an 8-10-hour work-day leaves me with about 70% battery when I get home.
My hat's off to the developer. I think I'll kick him a few bucks.
Hi there
First some specs:
Nexus 4
PA3.99-RC2
Franco.kernel.plus 188.
SuperSU root
Latest gapps
I have tried asking in the the Paranoid Android Google+ discussion forum, but no useful answers yet. This is x-posted in N4 forum as well, but I thought asking here in general could give give answers from people with other devices too.
The problem:
When I use my phone I get random glitchy/clicky sounds from the top speaker (I'm pretty sure it's from there). It's a very quick glitch/click, and then it stops. It doesn't happen in a specific pattern, meaning that it's not like it comes whenever I press the back button or anything - it just happens sometimes. Sometimes more often than other. When I try to recreate the sounds (tapping a lot of menus, settings, apps, etc.) I find it difficult to recreate. It is REALLY random, perhaps mostly after I haven't used my phone for a while, and I turn it on!
Have anyone tried this, and knows a solution? It didn't annoy me at first, but now it really does.
As far as I remember it started when I upgraded to PA3.99. However, I have tried RC-1 and RC-2 and I have also tried stock kernel, Hellscore kernel and different Franco-kernel versions.
New to posting here but I have been lurking for quite some time. I'll keep it brief here.
Suddenly, since flashing a 5.1.1 ROM, my N5 has been experiencing a sleep of death issue. Namely, once the screen turns off, it does not respond to anything. Pressing the power button does not wake the phone, and neither does plugging it in. After some time (~1 minute), the phone will reboot itself.
I know that this is not an uncommon issue, but the reason I have been forced to query the forums is because I have been unable to solve it by flashing ANY other rom. I've tried 5.1.1, 5.01, 5.0, and 4.3.3. I've searched and searched these forums and others to no avail. I've done countless restores to stock firmwares and 3rd party roms alike, removed apps and added them again, but nothing has solved my issue. I'm beginning to wonder if it is a hardware problem- that would be truly tragic.
I've pulled a kmsg but cannot attach it here as I have never posted, so I pulled a line that I believe is of interest, and would really appreciate it if you guys would look over it and tell me what you think.
Thanks!
KMSG
Code:
msm_vfe40_process_error_status: violation
[ 1066.509891] msm_vfe40_process_violation_status: camif violation
[ 1066.710201]