Develop Bugs

[Q] random vibration pulses after DK28 update

I just updated to DK28 using the update.zip over stock software (no root) and on top of various new features and new bugs, I've noticed a strange new behavior.
At least several times per hour, my phone will give a quick vibration pulse, then maybe a second or two later will give two (or sometimes three) real quick pulses. I have no idea why it's doing this and whether it means something or not. Anyone know?
I can't seem to correlate the behavior to anything in particular the phone is doing at the time. It happens with the phone sleeping, and it does it while I'm using it. It happens when I'm on the home screen, when I'm reading web articles, when I'm playing with other apps, when it's on the charger, when it's off...

pilby said:
I just updated to DK28 using the update.zip over stock software (no root) and on top of various new features and new bugs, I've noticed a strange new behavior.
At least several times per hour, my phone will give a quick vibration pulse, then maybe a second or two later will give two (or sometimes three) real quick pulses. I have no idea why it's doing this and whether it means something or not. Anyone know?
I can't seem to correlate the behavior to anything in particular the phone is doing at the time. It happens with the phone sleeping, and it does it while I'm using it. It happens when I'm on the home screen, when I'm reading web articles, when I'm playing with other apps, when it's on the charger, when it's off...
Click to expand...
Click to collapse
I got that too, plus lag and other bugs when first went to 2.2 (rooted 2.1 and used update.zip). Did you wipe when you updated? I didn't so it was acting weird... Plus the GPS didn't work so I did the Odin thing and now it works fantastic.

Did you wipe when you updated?
Click to expand...
Click to collapse
No. I probably should.
I just wondered whether these little vibration pulses were meant to indicate something, or whether they're just a bug.

happens when an app crashes

My vibration was related to turning on the WIFI became very unstable. The DK28 I had came with clockwork mod so I did a recovery to Epic Experence 2.0.7 chosing the recover form a specific zip file I had copied to my SDcard. Fixed the vibration problem and my USB connection then agin worked on my Windows 7 laptop

[Q] Trouble with all android software

Hello all, First, I searched the forums for my answer with no such luck, that being said if Im repeating a question thats been asked I apologize. I have a problem with keeping android stable. I have flashed with different versions of windows several times all with success. I do however, prefer the android system, I find that it runs much better, faster and has better perks. Everytime I flash following the original how to, I run in to a couple similar problems.
The first is when I hit the power (not hold the power) the back light cuts off and the keyguard enables, the screen goes dark all as it should. Depending on the time ( the longer it is the worse it is) when I hit the power key to revive my phone, I often get a white screen, then it waits , then it goes dim, Sometimes If I hit the power button several times it eventually comes back to the key guard option, but others I have to remove the battery and reboot. This is the major problem, as I cant use my phone when I need it. This problem seems to get worse the farther it gets away from the flash date, e.g..,, after a brand new flash it works pretty good and then it goes downhill from there.
Second, it seems to lock up when I let it charge overnight, not always (but most of the time) I get up, click the power button to revive the phone and I have a white screen before me that is frozen solid. This like the previous problem seems to be linked to the distance from the last flash.
I hope that its something Im doing wrong, as Im currently using wmobile 6.5 and since Ive had a taste of the droid os, my wm phone is just disappointing. And as I was unsuccessful in finding a post that adequately describes my problem ,Im hoping that there is a way around this .
I have tried, Incubus Superfroyo, Wrym warm donut, and Cyanogens build. Im sure Ive tried others, they just escape me, I was re-flashing daily until I went back to windows. I truly hope someone out there has encountered what I have and has a solution. thank you all for what you do, these forums have been extremely valuable and helpful.

Sounds like you have the wrong panel type selected. Is it set to auto? if it is, try setting it to 2 instead. That cleared up the problem for me.

Tried all panels all have the same problem.

Well thanks for all the many replies. I give Ive tried everything on this site and m android is still really glitchy. Guess it will be windows until I get perhaps a phone capable of running android smoothly.

What kind of phone do you have?
Sent from my HTC Vision using XDA App

do you have an SD card you can try to boot from and share your settings?

What we need to know is which kernel you're using, or an image of the kernel you currently have. Also, we need to know which radio version you're using, as this can have detremental effects on stability as well.
Personally, I have been using radio version 1.70.19.09, which seems to be the most stable with kernel .25 IMHO.
I have also "personalized" ThoughtlessKyle's "Fat-Free Froyo", adding/removing apps that I need or don't use respectively (navigation, QQPlayer, Pandora, etc.).
Currently, I think I might be one of the only people not experiencing any issues with this phone running Android 2.2.1. I do get the occasional "hang" (I wait for it to finish what it's doing instead of force close), but that usually has something to do with network coverage or an app requesting something from an unopened port.
Old phone, new OS and runs smooth as could be expected.
Next for me will be the HTC HD2 (if I get one at the right price, the tilt was free)...

I know, I know that MANY PEOPLE THINK OF THE WAKE UP WHITE JIBBERISH SCREEN as NEVER WORKING.

PoXFreak said:
What we need to know is which kernel you're using, or an image of the kernel you currently have. Also, we need to know which radio version you're using, as this can have detremental effects on stability as well.
Personally, I have been using radio version 1.70.19.09, which seems to be the most stable with kernel .25 IMHO.
I have also "personalized" ThoughtlessKyle's "Fat-Free Froyo", adding/removing apps that I need or don't use respectively (navigation, QQPlayer, Pandora, etc.).
Currently, I think I might be one of the only people not experiencing any issues with this phone running Android 2.2.1. I do get the occasional "hang" (I wait for it to finish what it's doing instead of force close), but that usually has something to do with network coverage or an app requesting something from an unopened port.
Old phone, new OS and runs smooth as could be expected.
Next for me will be the HTC HD2 (if I get one at the right price, the tilt was free)...
Click to expand...
Click to collapse
Ill try that combination and post my results. The latest I tried was
Scoot CyanogenMod 6.1.2 RLS6 with 2.6.32 still no joy, white screen crashes and hang ups. and it seems progressively worse the longer the rom is on the phone. To whomever asked what phone I have, its the at&t tilt II

srlebonv said:
Ill try that combination and post my results. The latest I tried was
Scoot CyanogenMod 6.1.2 RLS6 with 2.6.32 still no joy, white screen crashes and hang ups. and it seems progressively worse the longer the rom is on the phone. To whomever asked what phone I have, its the at&t tilt II
Click to expand...
Click to collapse
I can't help you regarding panel selection but, please have Radio ROM version 1.65 or higher. And do give my fresh foryo a go with 2.6.25 kernel (everything is there in the thread on how to use it with 2.6.25 kernel).
the WHITE GLITCHY SCREEN IS THE PROBLEM WITH ANDROID DRIVERS. Install with Data on SD Card often causes lockups / force closes.
I am using panel type 1 and white glitchy screen stays for like half of a second and next moment I get a nice clean keylock screen. I don't know but its like 20th time I am explaining the problem related to LCD
Change Panel Type, Get a compatible Radio version (1.65.x or HIGHER)

You say that often install with data on the sd card causes lock ups and freezes. Can you explain further what you mean ?

dark_prince said:
I can't help you regarding panel selection but, please have Radio ROM version 1.65 or higher. And do give my fresh foryo a go with 2.6.25 kernel (everything is there in the thread on how to use it with 2.6.25 kernel).
the WHITE GLITCHY SCREEN IS THE PROBLEM WITH ANDROID DRIVERS. Install with Data on SD Card often causes lockups / force closes.
I am using panel type 1 and white glitchy screen stays for like half of a second and next moment I get a nice clean keylock screen. I don't know but its like 20th time I am explaining the problem related to LCD
Change Panel Type, Get a compatible Radio version (1.65.x or HIGHER)
Click to expand...
Click to collapse
Ok, so I installed your version of froyo, the accompanying 2.6.25, the radio that you use. For the most part the hanging up is fixed. Now the second problem is still in place. Sometimes when Its been in hibernation(or whatever you would call when you hit the power button once ) when I attempt to refresh my phone (hitting the power button once) nothing happens, the green light is still blinking at the top but the screen stays blank, normally have to remove the battery and restart to get back to using the phone. Is this a sleep setting? or is this something Ive done wrong during the installation.

Bewildering, consistent, recurring problem on CM6 and CM7

I first started using CM at 6.1.2. I'm now on CM7 RC2 and the same problem still occurs. I have no idea why this happens but I'll provide as much info as possible in the hope that someone will be able to figure it out.
My phone will work completely normally for several days after I initially flash CM6.1.2 or CM7. After a few days, a crash will occur where the screen stays on but the phone is completely unresponsive to all input -- touch, softkeys, or hardware keys. The power button stops functioning. After a while, the screen dims and the phone reboots. After the reboot the phone chugs along for a few hours and then the same thing happens. This crash almost always occurs in the Browser, in the middle of loading a page. I don't think it's a memory issue because I consistently have ~100MB free for RAM.
Also, I don't know if this is at all related, but I often notice just before the crash, the haptic feedback from the phone for keyboard presses and the softkeys becomes very erratic and inconsistent.
I can never get a logcat because the phone restarts after the crash. Has anyone else seen this or know what might be the problem? Again, this has been happening all the way since CM6.1.2 (and possibly earlier, I haven't tried anything earlier than 6.1.2 though). This is driving me pretty crazy, and I really love CM and would like to continue using it, but this is kind of a dealbreaker.

Did you wipe between flashing CM6 and CM7?

Yes, I always wipe data/cache/dalvik between flashing.

Weird Lag, Sense restart(no FC) then Hot Restart issue - I can reproduce it

Have a VERY weird issue going on. I've been using Burnt Droid 1.4.2 by Netarchy since it came out. I decided to flash his new 4.3.4 CFS-NoHavs,noSBC, with static undervolt (i wanted to try and see if it was stable since I had success using undervolted kernels last year). I used proper procedure and cleared cache/dalvik-cache before flash. I downloaded the new Angry Birds from amazon and started playing it for a few minutes phone started lagging very bad, then had to restart. I said forget this; undervolt is probably causing this, and reverted back to the original 4.3.1-cfs-nohavs-nosbc which I never had a problem with(used proper procedure above to flash back kernel as well).
Now a day later at night, I decide to run my phone down because I'm trying to recalibrate my battery(I'm at less than 10% at this point). So I load up Wifi, turn on Pandora, and browse the internet. Not even 5 minutes into it, here's whats occuring in order:
1) Bad lag.. Pandora starts stuttering, so I hit the home button
2) HTC Sense restarts, It doesn't even force close, or at least it's not telling me
3) a Hot restart occurs a few moments later... (no white boot screen, just starts bootin from ROM screen)
4) At this point, sometimes its still laggy, sometimes it's fine. If it's laggy I must do a battery pull because It will keep looping to this point.
I can rinse and repeat this running pandora + browsing the web, and the same 4 steps above will happen within moments of eachother. I've been using this ROM since January with no major problems like this
A few side notes:
-I have Evo hardware 0002 (launch day evo)
-Rooted with Toast's original root method, eng .76 boot loader
-Newest radio/PRI/NV/Wimax
-My phone does not randomly reboot on me normally. Reboots only occur when following the above steps.
-I do not use Set CPU
Here is where I am very superstitious. I've been closely monitoring the "Boot looping + no Recovery Access" forum, and similar forums to this. Within the past few months I have tried out a few different CM7 nightlies. I have never flashed RC2 but I have flashed some after and before and tried those out for a while. I just hope my phone isn't starting a dying phase in relation to the problems people are having now.
Is there anything else recommended before I end up doing a full wipe and reflash the rom?

bigblueshock said:
Have a VERY weird issue going on. I've been using Burnt Droid 1.4.2 by Netarchy since it came out. I decided to flash his new 4.3.4 CFS-NoHavs,noSBC, with static undervolt (i wanted to try and see if it was stable since I had success using undervolted kernels last year). I used proper procedure and cleared cache/dalvik-cache before flash. I downloaded the new Angry Birds from amazon and started playing it for a few minutes phone started lagging very bad, then had to restart. I said forget this; undervolt is probably causing this, and reverted back to the original 4.3.1-cfs-nohavs-nosbc which I never had a problem with(used proper procedure above to flash back kernel as well).
Now a day later at night, I decide to run my phone down because I'm trying to recalibrate my battery(I'm at less than 10% at this point). So I load up Wifi, turn on Pandora, and browse the internet. Not even 5 minutes into it, here's whats occuring in order:
1) Bad lag.. Pandora starts stuttering, so I hit the home button
2) HTC Sense restarts, It doesn't even force close, or at least it's not telling me
3) a Hot restart occurs a few moments later... (no white boot screen, just starts bootin from ROM screen)
4) At this point, sometimes its still laggy, sometimes it's fine. If it's laggy I must do a battery pull because It will keep looping to this point.
I can rinse and repeat this running pandora + browsing the web, and the same 4 steps above will happen within moments of eachother. I've been using this ROM since January with no major problems like this
A few side notes:
-I have Evo hardware 0002 (launch day evo)
-Rooted with Toast's original root method, eng .76 boot loader
-Newest radio/PRI/NV/Wimax
-My phone does not randomly reboot on me normally. Reboots only occur when following the above steps.
-I do not use Set CPU
Here is where I am very superstitious. I've been closely monitoring the "Boot looping + no Recovery Access" forum, and similar forums to this. Within the past few months I have tried out a few different CM7 nightlies. I have never flashed RC2 but I have flashed some after and before and tried those out for a while. I just hope my phone isn't starting a dying phase in relation to the problems people are having now.
Is there anything else recommended before I end up doing a full wipe and reflash the rom?
Click to expand...
Click to collapse
I'm not really sure what's causing your problem, and If i was in your situation, I'd most likely do a complete wipe, including calkulin's format all, and either restore a good nandroid, or reflash the rom from scratch.
That said, I don't believe CM to be 'dangerous' to run or anything like that. Yes, it is odd that an increasing number of people are reporting somewhat major issues, with boot looping the splash screen, and being permanently stuck there. However, that doesn't mean CM is the cause. It does seem to be a common denominator in the people that this has happened to, but there are soooo many other variables that come into play with something like this. There is no proof that CM caused it, but it does seem odd that everyone it happened to was running CM. Also, I'm sure there are thousands of CM users, and a select 8-10 people have reported these issues on here. That's a very low percentage, overall. With all that said, I myself won't be running CM in the near future, either until it's confirmed or denied that it has anything to do with these issues. I'll just be playing it safe, just in case.

I'm stock everything, no root or mods and it restarts at the 4g screen skips everything else...
Sent from my PC36100 using XDA Premium App

I think I will do the format all and completetly wipe it and reflash the rom from scratch. Thank you!

[Q] Problems with SyndicateROM Frozen

Hi all,
I recently installed SyndicateRom Frozen after I got stuck on Eb13 thanks to Sprint. It worked out really well (so fast!) for a while but I am now having problems varying from strange but tolerable to very bad.
Here is the exact order of what I've done:
1) from eb13, I used odin to get DI18, then modem only to EC05, installed CWM3 and wiped data/cache/dalvik cache 3x each.
2) I used CWM3 to flash SyndicateRom Frozen (the latest version)
3) it worked pretty well, but then I (stupidly I guess) installed Go Launcher Ex and then everything went to hell
4) it ran for a while then suddenly EVERYTHING force closed. restarting it just gave me 9000 more force close boxes. so I...
5) wiped data/cache/dalvik 3x, re-flashed syndicateROM
So here I am now with the following problems:
1) The phone randomly freezes irreversibly (only solution is to pull the battery). It seems like it happens in the browser only (stock Syndicate browser)
2) The phone randomly freezes for a little while only (all the time)
3) The email app force closed (fixed this for now by clearing its data, from forum)
4) With auto-rotate OFF, nothing rotates EXCEPT my phone page.. What the heck? The phone page (ie click the phone icon) rotates regardless of what setting auto-rotate is on
5) The phone sometimes just decides to restart itself. And rarely, the restart never finishes.
6) Whenever I open up google navigation, it says "checking navigation availability" for 5-10 seconds. This never happened before
Now, what do I have running?
-SetCpu (this was running before I had go launcher and I had no problems). it's set very modestly -- 200-400 with screen off (and I dont have the no-wakeup problems some people talk about) and 400-10000 with the screen on, on demand.
-Ultimate Juice
If anyone knows what I can do to fix this, I'd really appreciate it. Thanks.

Thanks for the detailed post - it helps. Your issues, though, are almost definitely kernel-related. Freezing is a sign you need to use kernel version 1.0.4 linked from the second post, or VisionKernel. Try VisionKernel first. If it solves your issue, you're good to go.
Anything related to screen rotation is outside of the ROM - run the sensor calibration process.

k0nane said:
Thanks for the detailed post - it helps. Your issues, though, are almost definitely kernel-related. Freezing is a sign you need to use kernel version 1.0.4 linked from the second post, or VisionKernel. Try VisionKernel first. If it solves your issue, you're good to go.
Anything related to screen rotation is outside of the ROM - run the sensor calibration process.
Click to expand...
Click to collapse
Thanks for the quick reply. I'll try installing a new kernel when I get home tonight. BTW, awesome work with the ROM.

Xinlitik said:
Thanks for the quick reply. I'll try installing a new kernel when I get home tonight. BTW, awesome work with the ROM.
Click to expand...
Click to collapse
Thanks for your support!

im having similar problems, but mine only occur when the battery dies
after i restart a lot of my apps are force closing without even running them, and when i press the home button the screen is blank. (i also use go launcher)

You kno this same thing happened to me. I finally realized it was probably because I was restoring my apps with titanium. I decided to just re-download my apps and restore only app data with titanium (angry birds etc.). This helped me. And this was all after installing launcher pro. So there was some sort of conflict there. Are you restoring apps?
Sent from my SPH-D700 using XDA App

i didnt restore my apps with titanium that time but i switched from go launcher to launcher pro and i dont have that problem anymore

Hmm...i guess just stay away from that launcher then...haha.
Sent from my SPH-D700 using XDA App

I'm not sure if his problems were strictly Go Launcher related. I've been using Go for 2 days now, with no problems (yet... knock on wood).
Sent from my SPH-D700 using XDA App

So here's an update:
-No, I'm not using Titanium backup.. I manually reinstall all my apps.
-I tried out the VisionKernel and it seemed ok for a bit, but I'm freezing again and my apps are all force closing. I uninstalled SetCpu completely in case that was causing a problem, but it didn't make a difference.
I'm going to try using v1.04 next... if that fails I guess I just can't use this rom
Would setting myself back to DI18 -> EC05 -> Syndicate possibly work? (as opposed to just re-flashing syndicate)

This was happening to me regardless of my kernel, and I even (twice) ODIN'd to [DI18?] then OTA to EC05 and then wiped everything 3 times, and flashed, 1st flash never works for me, so 2 flashes both times completely clean as well as when flashing kernels
1.0.2 worked just fine for me but as soon as 1.1.0 came I get freezes and FC's all over the place. I have given up on 1.1.0 and will try it when a newer version comes out

Media
First off want to say, love the ROM so far, you guys rock. After a few failed attempts at getting CWM 3 on my phone, I was finally able to do so and get everything installed. The only problem I'm having is with my media files. I get random FC when I play my music, my photo gallery doesn't appear, when I try to access my mp3's directly from my SD card, it says "file type not found" and it does not like the Zedge app at all. I've tried both the standard and fully loaded versions with the same results. I have the visionkernel downloaded, just in case I need to try it, but if at all possible, I'd like to stick with the twilight (I use the camcorder often). Any other suggestions? Thanks in advance!

androikid said:
This was happening to me regardless of my kernel, and I even (twice) ODIN'd to [DI18?] then OTA to EC05 and then wiped everything 3 times, and flashed, 1st flash never works for me, so 2 flashes both times completely clean as well as when flashing kernels
1.0.2 worked just fine for me but as soon as 1.1.0 came I get freezes and FC's all over the place. I have given up on 1.1.0 and will try it when a newer version comes out
Click to expand...
Click to collapse
Yea, did basically the same thing last night. It went fine for a day, but it went to hell again tonight. Oh well, we'll have to wait for a new version I guess.

Xinlitik said:
Yea, did basically the same thing last night. It went fine for a day, but it went to hell again tonight. Oh well, we'll have to wait for a new version I guess.
Click to expand...
Click to collapse
As noted many times in many places, if you're having issues with 1.1.0 that aren't freezing/battery life (these are both the kernel and have been discussed everywhere), a few simple troubleshooting steps will get you exactly where you need to be.
allheilkingmatt said:
First off want to say, love the ROM so far, you guys rock. After a few failed attempts at getting CWM 3 on my phone, I was finally able to do so and get everything installed. The only problem I'm having is with my media files. I get random FC when I play my music, my photo gallery doesn't appear, when I try to access my mp3's directly from my SD card, it says "file type not found" and it does not like the Zedge app at all. I've tried both the standard and fully loaded versions with the same results. I have the visionkernel downloaded, just in case I need to try it, but if at all possible, I'd like to stick with the twilight (I use the camcorder often). Any other suggestions? Thanks in advance!
Click to expand...
Click to collapse
Format your SD card.

As noted many times in many places, if you're having issues with 1.1.0 that aren't freezing/battery life (these are both the kernel and have been discussed everywhere), a few simple troubleshooting steps will get you exactly where you need to be.
Click to expand...
Click to collapse
My issue is freezing, and I tried all of the alternate kernels. Sorry if my language wasn't precise- I mean new kernels.
I've actually given it one last try...I'm wondering if the clock is set too low for my phone by default, so I've got setcpu on min400 max1000. I'll let ya'll know how it turns out... (Stable so far although suddenly my home key doesn't work, hah.)

Xinlitik said:
My issue is freezing, and I tried all of the alternate kernels. Sorry if my language wasn't precise- I mean new kernels.
I've actually given it one last try...I'm wondering if the clock is set too low for my phone by default, so I've got setcpu on min400 max1000. I'll let ya'll know how it turns out... (Stable so far although suddenly my home key doesn't work, hah.)
Click to expand...
Click to collapse
400mhz shouldn't be necessary. If your freezes were wakelocks, and you had your minimum frequency at 100mhz, that was your problem - not all devices can handle it, and need to be at 200mhz.

400mhz shouldn't be necessary. If your freezes were wakelocks, and you had your minimum frequency at 100mhz, that was your problem - not all devices can handle it, and need to be at 200mhz.
Click to expand...
Click to collapse
They were actually freezes during use-- I luckily never got a single wakelock.
I'm not sure if there was a pattern or not, but I think the Market, Go SMS Pro, stock Email, and stock browser were the main freezes. Then again, those are also the apps I use quite frequently

Sorry to double reply, but I can't edit yet.
@androikid
It just occurred to me that the freezes wouldn't be that bad if not for the force closes that occur afterward (due to data corruption). Maybe we should just turn journaling on so the a freeze just means a restart, rather than a re-flash.