Develop Bugs

[Q] MIUI ROMs - Problem with touchscreen randomly becoming unresponsive and rebooting

Hi All,
Been having a problem with the touchscreen randomly becoming unresponsive or the phone rebooting on its own ever since when I'm (trying) to run MIUI ROMs.
By "random" I mean that it sometimes occurs while typing, switching home screens, opening an app, or even just when the phone's idle.
Not experiencing any unexpected FCs throughout the MIUI ROMs that I've tried however... so at least that's a good thing?
I don't experience any of these problems at all when running a stock Sense ROM, so I'm hoping it's not the same rebooting problem described in another thread that requires sending it in for repairs as that would be very troublesome.
The phone's a HKCSL Desire that was rooted using unRevoked. The problems occur even when I don't install any apps onto the phone and when the phone's just idle with the screen off (for randomly rebooting).
Any suggestions would be greatly appreciated =) and I hope I'm not just SOL for MIUI ROMs since no one else seems to really be having these problems.
---
List of things I've tried:
1. Full wipe with Dalvik & cache before flashing a ROM (many, many times)
2. Updating to 32.48.00.32U_5.11.05.14 radio and downgrading to the suggested 32.44.00.32U_5.09.05.30_2 (Thought it might've been caused by WiFi connection as I always have it on... but doesn't seem like it)
3. Using different versions of Clockworkmod (2.5.0.7, 2.5.0.1, 2.5.0.1 modified by MIUI.cn)
4. Repartitioning/formatting SDCard before/after flashing a new ROM
5. RUU-ing the phone and redoing everything from scratch
6. Using an untranslated base MIUI-Desire ROM
7. "Upgrading" the ROM by flashing on top of the 10.15 build
Versions of MIUI ROMs I've tried:
Pretty much all the releases of 10.15 and 10.22. Currently fiddling around with eevek's stock 10.29 and mobiousdigital et al.'s 10.29 builds.

Hopeful bump =)

[Q] HELP! My Incredible has frequent crashes and reboots

Can't find an answer to this on google or xda. Didn't know if I should post this in General or Q&A.
I have been using my Incredible since it came out. I quickly learned about rooting, roms, s-off... with no problems. I have been running Skyraider almost from the beginning.
Here is the problem: A few days ago, I noticed on the SR thread that there were updates for the radio and hboot. So, I went ahead and flashed them. Almost immediately I started noticing the screen becoming unresponsive. After a minute or two I did a battery pull, rebooted, and again after a little while, freeze and reboot. I also noticed that even when the phone is awake but screen off, it would wake itself up. The rebooting and freezing makes it impossible to use my phone.
I tried everything I could think of:
Nandroid restore (obviously didn't work since this doesn't effect hboot or radio).
Reinstalled fresh SR Rom wiping everything, including dalvik, and did factory reset.
Finally, I downgraded back to the hboot and radio versions I had before, still no effect. (Baseband version 2.15.00.07.28, hboot .79 ).
I tried installing another ROM (Uncommon sense) to make sure it wasn't a ROM issue, ..same problem.
Please, any help would be much appreciated. I don't know what my next step should be.

do you overclock at all?

g00s3y said:
do you overclock at all?
Click to expand...
Click to collapse
No overclocking, I don't use setcpu, and I have been running the stock kernel. But it does feel like overclocking.

I wonder if the timing of events is just coincidence and its a hardware issue. I've had my Inc since June... rooted s -off in july and had no problems until about a month ago. I don't oc I use the new stock kernel but my phone hates change. Even flashing a small mod will cause rebooting.... and navigation always causes it. Phone heats up fast with these particular activities too but sometimes it will reboot at only 35c after a flash. I'm thinking hardware
Sent from my ADR6300 using XDA App

Thanks,
You may be right.
For now things are working, let's hope they stay that way.

[Q] Desire seems to restart when using 3G

I've been using my desire for about 1 year now and never had any problems until I decided to go back to Leedroid gingerbread rom and install the patches for A2SD+ with ext 3.
I was having restarts every 10-15 minutes on Leedroid, went back to CM7, currently on cm7 7.0.2 and I'm still getting restarts when I wasn't previously.
I have asked this question before and thought it was an issue with the SD card. Now the reason I thought it was the SD was when I was having loops of restarts I would take it out and it would be quite stable for a while. Formatted everything (SD and internal + cache) put on the latest radio rom and then put on the latest CM. Seemed to run fine for a while and then started restarting again. It locks up on the HTC screen occasionally and requires me to pull the battery.
I've noticed that it only happens when I'm using 3G internet connectivity. Just recently it tried to get a lot of updates and would start downloading them only to restart. It does eventually get the updates though.
To test this I can start watching a youtube video and it will crash. For example I just watched 1 minute of one video before it crashed, after reboot I started youtube again and it crashed immediately.
Can I stop log cat removing all the logs when the device restarts so I can have a look what's going on? Any other ideas on how to diagnose or fix would be much appreciated.

What's your radio?

My Radio version is
32.56.00.32U_5.17.05.23 and I'm running CynogenMod 7.0.3
I used something else before I switched to leedroid an old one, I changed it to go to Leedroid then changed it to this hoping it would help.

Flashed newest correcspondig ril 2.2.1003G?
Thread for radio/ril here on xda:
http://forum.xda-developers.com/showthread.php?t=902752

No I have never flashed a RIL before, didn't even know what these where. I'll give that a shot and see what happens.

DeliveryNinja said:
No I have never flashed a RIL before, didn't even know what these where. I'll give that a shot and see what happens.
Click to expand...
Click to collapse
RIL (by System of a pWne!^)
Radio interface layer. This is a layer between the Radio and the ROM. It communicates with the hardware over the Radio and supplies an interface for the ROM so it can use the hardware. This is similar to a driver.
Whenever you flash a new Radio, you should also consider flashing the corresponding RIL for it. This makes sure, the Radio is getting adressed correctly.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=805247

I was running the RIL suggested above yesterday, had about 11 hours and no issues, updated all my apps, was watching youtube etc.. I was trying to do stuff that usually would make it crash. Eventually I turned on my wifi at home and as soon as it came on the phone rebooted. It then proceeded to reboot every time I tried to go on the internet, with either 3g or wifi, I tried about 3-4 times. Leaving it with internet off for about 30 mins, I came back to it and it started working on wifi fine. Strange. TL;DR ril didn't seem to fix it. Seems like if I can get it back to stock I can go to the shop and change it.

SOD even in stock

Hi Guys really need help on this one.
As a brief background on the problem, from stock I have flashed a few custom roms mainly paranoid android, carbon, android revolution hd. Flashing was always successful. No problem with odin flash as well. My concern is this. I noticed that I was getting SODs after flashing a few custom roms. So in order to fix it, I tried to flash stock rom. No problem with flashing however SODs continue to exits. Have tried flashing quite a few stock roms but basically SOD problem still exists. By the way when flashing through ODIN I always just flashed with the PDA option never with the others. Getting really frustrated about this. I can get rid of the SODs temporarily by using SoftLocker. However, I wish to get back to a stable rom base before I try any new customizations. Hope you can help me. Thanks.
On an added note, when I connect my phone to the PC the phone is not automatically detected. I still have to input *#7284# change modem to pda in order for it to be detected. I think this is somehow related because this happened during my encounters with SODs.
Your help would be greatly appreciated.

By the way, I have already checked for the SDS chip and happily my phone doesn't use the insane chip.
Just wondering about this SOD thing.
Should it be enough that I flash into stock (PDA only) to get factory stock?
Should mention that original ROM of phone did NOT have SODs.
So I'm guessing the culprit is flashing the customized ROMs.
However, I cant get stability back even when flashing back to stock.
I can still see some residual effects of previous roms in my current stock rom (like the usb connection not detected).
Just looking for some clues and glad if someone could help.

t3kn1ks said:
By the way, I have already checked for the SDS chip and happily my phone doesn't use the insane chip.
Just wondering about this SOD thing.
Should it be enough that I flash into stock (PDA only) to get factory stock?
Should mention that original ROM of phone did NOT have SODs.
So I'm guessing the culprit is flashing the customized ROMs.
However, I cant get stability back even when flashing back to stock.
I can still see some residual effects of previous roms in my current stock rom (like the usb connection not detected).
Just looking for some clues and glad if someone could help.
Click to expand...
Click to collapse
HI Guys,
Just an update on this, in case someone is experiencing the same problems, it seems I got the SOD fix. I found it out by switching back to an AOKP rom. Suddenly, no more SOD. After a bit more experimenting, I found out that it had something to do with the kernel (stock kernel even!). My basic fix is this: install a stock rom then switch kernel to Note2Core. It seems certain "configuration updates" within the kernel prevents the device from going into sleep of death. (Note that my device now can "sleep" properly ... saw this using cpu spy ... deep sleep is still attained with NO SOD). Hope this helps people out there with the frustrating SOD problem.
Incidentally, if someone could point out how the kernel change fixed the SOD problem it would be a great help.
By the way, usb connection is still not detected by default but fixed by doing *#7248" and then choosing pda for usb.

Fixed! and Solved!
t3kn1ks said:
HI Guys,
Just an update on this, in case someone is experiencing the same problems, it seems I got the SOD fix. I found it out by switching back to an AOKP rom. Suddenly, no more SOD. After a bit more experimenting, I found out that it had something to do with the kernel (stock kernel even!). My basic fix is this: install a stock rom then switch kernel to Note2Core. It seems certain "configuration updates" within the kernel prevents the device from going into sleep of death. (Note that my device now can "sleep" properly ... saw this using cpu spy ... deep sleep is still attained with NO SOD). Hope this helps people out there with the frustrating SOD problem.
Incidentally, if someone could point out how the kernel change fixed the SOD problem it would be a great help.
By the way, usb connection is still not detected by default but fixed by doing *#7248" and then choosing pda for usb.
Click to expand...
Click to collapse
As an end note, I was able to bring back the ROM to stable state.
I believe my mistake was that I accidentally flashed an S3 ROM to my Note 2.
Probably corrupted some files.
The fix seems to be this:
Flash N7100_OXA_N7100XXDLJ2.
It will fail at sboot.bin.
Flash another stable rom (I did it with stock rom Stock_Deodex_Rooted_N7100XXDMC3_N7100OLBDMD1_N7100DXDLK5_THL)
Finish up.
Test for SODs.
CPU spy is the best way to check for it.
If deep sleep occurs without SOD then your phone is back to stable state.
USB connection is working properly as well as bluetooth (which I failed to notice was defective as well).
Hope this helps someone as it took me almost 5 months to get the phone stable. Cheers.

t3kn1ks said:
As an end note, I was able to bring back the ROM to stable state.
I believe my mistake was that I accidentally flashed an S3 ROM to my Note 2.
Probably corrupted some files.
The fix seems to be this:
Flash N7100_OXA_N7100XXDLJ2.
It will fail at sboot.bin.
Flash another stable rom (I did it with stock rom Stock_Deodex_Rooted_N7100XXDMC3_N7100OLBDMD1_N7100DXDLK5_THL)
Finish up.
Test for SODs.
CPU spy is the best way to check for it.
If deep sleep occurs without SOD then your phone is back to stable state.
USB connection is working properly as well as bluetooth (which I failed to notice was defective as well).
Hope this helps someone as it took me almost 5 months to get the phone stable. Cheers.
Click to expand...
Click to collapse
Thanks man i thumbs up ur account....i was changing my dead screen to a new one and i thought it was the new screen that kept turning off even after trying stock kernels and even pegasus but because of ur note2core recommendation and worked like a charm ....thanks man

[Q] CM10.1 Nightly Softkeys not working and often reboots

I'm on CM10.1-20130526 Nightly. Often times, the softkeys (the ones at the bottom of the phone) don't work. This requires me to reboot the phone in order to get it to work. Also, the phone reboots (on its own) several times during the day (upwards of 3 times a day). Is there any way to fix these problems? Thanks.

thatlaoboi said:
I'm on CM10.1-20130526 Nightly. Often times, the softkeys (the ones at the bottom of the phone) don't work. This requires me to reboot the phone in order to get it to work. Also, the phone reboots (on its own) several times during the day (upwards of 3 times a day). Is there any way to fix these problems? Thanks.
Click to expand...
Click to collapse
Software keys is not a common issue so maybe you should change roms. The reboots are common with cm 10.1 builds since they are in testing phase still. A new RC3 build should be out late tonight or tomorrow at the latest maybe you should try that. Also did you use the odin update firmware it really helped with the reboots and screens of death for a lot of people. It just udgrade your firmware and radio to the newest available for this phone here is odin and the uvmc6 tar file if you need it. First hook phone up in download mode make sure odin sees it in (yellow) box for whatever port it's hooked up too. Then place tar file in PDA section and hit start. Once finished it should say PASS in (Blue) box. After phone reboots unplug from computer. This will not erase anything on your phone at all. It just upgrades it.
UVMC6 TAR
https://www.dropbox.com/s/3ccjzq3rkt3ylfg/UVMC6.aio.tar.md5
ODIN
https://www.dropbox.com/s/lczw3kg1s02g3ol/Odin3_v1.85.zip

soft keys and slow down to reboot
running new firmware and radio doesn't fix the soft key issue. It seems very random and rebooting doesn't always fix it. I've switched to uber stable 2.0 rc1 kernel and it hasn't happened for a day now. Still having what might be memory issues as the phone slows down to not doing anything then reboots. If I manage to look at the memory usage before it is unusable there is 30mb available which is almost nothing but it is still some. So is the slow down and reboot related to an inability to run the process to free up memory? I'm not sure since I'm not 100% familiar with the "garbage collection (.Net terminology, I know android has something similar for activities I think)" of android. The slow down/reboot seems to speed up with the number apps opened/activities started over time.
The only thing that fixed the SOD for me was using a different kernel than the cm10.1 kernel.
Update: just took a while but still have issues with soft keys and rr