Related
So Im VERY new to this, first Windows Mobile phone. And this is my first post.
Right after receiving my HD2, I was disappointed with my purchase. I loved my Android powered G1, and fell in love with HTC. But when I got my HD2, the texting was terrible, and my phone kept freezing. After talking with a few friends about this, I was referred to this site.
From there, I did some research, and have learned a little bit. I decided to upgrade the ROM to the stock T-Mobile 2.13, through a link I found on this site. At the same time, I loved the interface of the CHT and CHTE, so I loaded those. Also, at the recommendation of Cookie's thread, I loaded Chainfire HD2 3D Driver Patch V2.0.
Well everything feels better, Ive started using Swype, and I havent had any freezing issues. I couldnt be happier...
But I recently notice (I dont do many phone calls, or talking. Im more web, email, and text) my incoming call screen isnt popping up. My phone will ring, I pull the phone out, and I see my home screen, and it is unlocked, like it should be when an incoming call comes through. I start tapping on the screen, and where I tap, icons/buttons start popping up. The "Mute" button, the "Answer/Ignore" bar, and SOMETIMES the caller's ID pic (if Im lucky enough for it to be someone who has a pic).
Now, this doesnt happen ALWAYS, but it does happen here and there. Ive also noticed, that the function that blacks/locks the screen when in call, against your face is running funny.
Does anyone know if this is related to my ROM? The 3D Driver Patch? CHT? Has anyone had anything similar???
I DID do a search, but only in this TMOus HD2 General sub forum. Should I be looking else where? Sorry for such a novel. I just felt that I should provide any possibly necessary info, since Im kind of clueless to this phone modifying world.
TIA.
Hmm...if it were me I'd definitely start with uninstalling that video driver and see if that changes the behavior.
Also, are you using the stock lockscreen or do you have CHT lockscreen enabled via CHTE? If you do have CHT's enabled, then next you might want to switch it off and see if it helps.
I don't know for sure that either of those will resolve that, but that's where I'd start troubleshooting.
After your new rom finished flashing, did you perform a manual hard reset (as recommended by most chefs)?
I've found that there is more chance of the rom being unstable if you dont.
(flashes dont always take first time, no clue why, but i'd estimate about 1 in 10 flashes just isn't stable, yet the next flash with the same rom is stable, , , I've also noted similar results when installing an OS on my PC, , , sometimes it just doesnt wanna take properly.)
theidealone said:
So Im VERY new to this, first Windows Mobile phone. And this is my first post.
Right after receiving my HD2, I was disappointed with my purchase. I loved my Android powered G1, and fell in love with HTC. But when I got my HD2, the texting was terrible, and my phone kept freezing. After talking with a few friends about this, I was referred to this site.
From there, I did some research, and have learned a little bit. I decided to upgrade the ROM to the stock T-Mobile 2.13, through a link I found on this site. At the same time, I loved the interface of the CHT and CHTE, so I loaded those. Also, at the recommendation of Cookie's thread, I loaded Chainfire HD2 3D Driver Patch V2.0.
Well everything feels better, Ive started using Swype, and I havent had any freezing issues. I couldnt be happier...
But I recently notice (I dont do many phone calls, or talking. Im more web, email, and text) my incoming call screen isnt popping up. My phone will ring, I pull the phone out, and I see my home screen, and it is unlocked, like it should be when an incoming call comes through. I start tapping on the screen, and where I tap, icons/buttons start popping up. The "Mute" button, the "Answer/Ignore" bar, and SOMETIMES the caller's ID pic (if Im lucky enough for it to be someone who has a pic).
Now, this doesnt happen ALWAYS, but it does happen here and there. Ive also noticed, that the function that blacks/locks the screen when in call, against your face is running funny.
Does anyone know if this is related to my ROM? The 3D Driver Patch? CHT? Has anyone had anything similar???
I DID do a search, but only in this TMOus HD2 General sub forum. Should I be looking else where? Sorry for such a novel. I just felt that I should provide any possibly necessary info, since Im kind of clueless to this phone modifying world.
TIA.
Click to expand...
Click to collapse
I read somewhere that the "unleaked official ROM" caused more problems than it was worth. I got the 2.13 ROM on the leaked version before it was made official and it has been working great since. I read that they made more changes and then made it official and that it was causing phones to be bricked and most phones ended up worse than they where before the the upgrade. The only "negative" thing i experienced was the screen sensitivity but it appears that the cab featured in the sticky at the top of the post fixed that!? Kinda strange If all else fails Factory Reset and try again. I always like to take a baseline reading. When my phone began acting screwy I would restore and run it stock for a few days to see if problems persisted...then after about three or four days slowly begin installing things...
Thanks for the responses! I will start with sirphunkee's suggestions. As I was typing, I started thinking the Driver Patch was a good possibility. Also, I have noticed that the phone doesnt just "sleep" the screen when I put the phone to my face, it locks. Im assuming this is something to do with CHTE's lock, because as sirphunkee mentioned, I am using the CHTE lock, instead of the stock.
Im going to start there, and see what happens.
Also, I did NOT do a manual hard reset. How would I go about doing so (yes, Im a HUGE noob. More of a car guy)? Im hoping I wont need to do this, as Im assuming I will need to restore all of my contacts, reorganize them, and reset everything else, as if the phone were new out of the box... Correct? But in case that is necessary, how do I do so?
As far as the leaked or official version... I couldnt find it on T-Mobile's site. I read a thread here, where it had been there then removed, due to people having issues with the download. I then was searching Swype or something, same forum, and found another thread, where someone had a link to the download through T-Mobile. Kinda hard to explain, but I will see if I can find the link, and the thread.
Thanks again guys! I really appreciate it. And thanks for taking it easy on me.
I just tried to post the links. I found them in my browser History. But because I have such a new account, I cant post.
theidealone said:
I just tried to post the links. I found them in my browser History. But because I have such a new account, I cant post.
Click to expand...
Click to collapse
Thanks for the effort though, you'll be able to put up links after just a few more posts (it's listed in the forum rules...hint, hint). Also, toreone already threw up a new thread in this section with that link for everybody, so don't sweat that
EDIT: oops, missed the rest of your questions there. The hard-reset is exactly what you said...resets the phone to factory-fresh condition. Yes, contacts will have to be reapplied, but sorting really shouldn't be an issue depending on your method of backing up and restoring them. I highly recommend using the built-in Microsoft Myphone utility for that (and it's wise to let it back them up regularly too, just in case, I just have mine set to do it each night while it's charging).
You can perform a hard-reset a couple of ways:
1. on your settings tab, hit "menu", then "all settings", then "system". You'll find an icon in there titled "clear storage". Run that, use 1234 as the code, and it will do its deed.
2. with the phone powered off, hold both the vol up and down buttons at the same time, and then press the end/power button to turn it back on, then it will take you into the same hard-reset process as the first method.
Ok so here is the deal, and yes i have been searching for hours to see if there is already a thread and yes I already posted this in the ROM thread i was using but no answers. I was running an Android build that runs on RAM and i messed up a setting. In MDJ's froyo Streak lite ram build there is a cyanagen setting for the lock screen. I was trying to set it back to the slide lock because i had it on the menu button and somehow my fat fingers set it to the trackball and locked the phone in one fellow swoop. So now i am locked out of Windows too. I rn task29 reflashed stock rom, changed radio, flashed a lite custom winmo rom and hard reset numerous times. If i let the HD2 go into sleep by itself it is fine most of the time but if I put it into standby with the end key hard button it will never unlock. The screen wakes up but i cannot move the lock.
I would greatly appreciate it if anyone has a suggestion for me, obviously this change has stuck to my phone somewhere and i cannot find where it is. Please help this idiot out. thank you.
Sorry but have I missed something here, How on earth can this lock you out of windows??
Just reboot the phone!
TheATHEiST said:
Sorry but have I missed something here, How on earth can this lock you out of windows??
Just reboot the phone!
Click to expand...
Click to collapse
i understand it seems weird but there is a software conflict some where because it will NEVER come out of sleep in any rom if i put it to sleep with the power button. the time changes so the phone is running when i wake it but the touchscreen does not recognize touch.
Sounds like your digitizer took a dump.
This is not an issue with Android or WM, you have a faulty piece of hardware.
Just an unfortunate coincidence that it happened while switching between Android and WM.
Unless your screen still responds to touch while in Android?
But then if thats the case, it's a problem with WM touch drivers, not Android.
I booted into Android and i was still getting sod but i was able to break out of it a couple hours ago but mostly it locked up. Now it is locking the screen completely even when it is not locked in Winmo so maybe you are right. But usually i can navigate through windows fine until it locks....Ok hard reset now i can maneuver around in windows again but standby still locks me out only if i use the power button to sleep it.
Its simple to disprove that it has anything to do with android.
Just remove sdcard and do a hard reset of windows mobile. No androind files are in your phone they are all on your sdcard.
Your problem is hardware based not software unless a hard reset solves it or another WM rom.
htc hd2 leo android built.
Was wondering why no matter what android bulit i try they work great but when my phone goes in sleep mode it wont wake up. I have to remove battery to get it going. I have a manila rom 2.13.531.1 radio 2.10.50.26 please help. Thanks
joykiller said:
Was wondering why no matter what android bulit i try they work great but when my phone goes in sleep mode it wont wake up. I have to remove battery to get it going. I have a manila rom 2.13.531.1 radio 2.10.50.26 please help. Thanks
Click to expand...
Click to collapse
What is your sd card?
Sent from my HD2 Droid using XDA App
Hi guys,
I would like to share an issue that I encounter since I installed the ICS v0.3.
Anytime I'm done using my HD2 device, I hit the "power down" button to save battery in "sleep mode".
So far (with android or WP7 roms), I usually hit back the "power down" button to display the lock screen thing. Then I either type in a PIN, or slide the lock to "unlock" the screen.
The issue I encounter is the following:
- If i try to resume my device with the use of "power down" button, then my screen is frozen, like the touch interface isn't recognized. Though, I must hit the "power down" button to enter sleep mode again, and use another button that randomly enables me to unlock my phone.
I have asked around (on a french forum) and it seems that I am the only one who encountered this issue so far.
Please, if you have any idea, or suggestions that would be very helpful.
I flashed the rom twice, used with the original or the dorimax 4.1 kernel and nothing has changed. I haven't tried yet the 0.4 TOSTI.
Kind regards
Hello, me again.
23 people way this thread no one did answer, probably because posting in this section is not the most efficient to bring feedback on a dedicated topic. But, having less than 10 posts prevents me from posting in dvpment section.
Anyway, could you guys please do me a favor and copy a link to my topic in this section:
http://forum.xda-developers.com/showthread.php?t=1441462&page=31
the main goal is to let the developer know about an unknown issue.
Thank you in advance
tonythrash69 said:
Hello, me again.
23 people way this thread no one did answer, probably because posting in this section is not the most efficient to bring feedback on a dedicated topic. But, having less than 10 posts prevents me from posting in dvpment section.
Anyway, could you guys please do me a favor and copy a link to my topic in this section:
http://forum.xda-developers.com/showthread.php?t=1441462&page=31
the main goal is to let the developer know about an unknown issue.
Thank you in advance
Click to expand...
Click to collapse
the ROM updated to V0.4 now. Do a clean install and see if the problem still exists
Hi,
I know about this update. It seems this version has some issues with the market. Around me, I am the only user with such an issue on V0.3, I don't think this might be fixed with an update. I even tried to update the kernel to dorimax what brought better battery life, but didn't fixe my screen problem.
Hello everyone,
I'm trying to install a new ROM on my girlfriend's HD2. I use a SGS4G, and everything is much simpler there. I have Cyanogenmod installed on her phone currently, but I did that a while ago and I completely forgot how I did everything for it.
I'm trying to do the following:
- Repartition a new 16GB memory card so it works with the phone
- Install a stable/smooth ROM for her to use (this one looks good -- is it?)
The problem with the SD card partitioning is that I'm not exactly sure how to boot into CWM (assuming that's where you partition the SD card at). I can get into the aMAGLDR v1.13 screen, but I have no idea how to progress into the CWM screen.
The second problem is that I'm not sure how to format the system to 200mb and the cache to 5mb.
If someone could at least point me in the right direction. I wouldn't mind trial-and-error with my phone, but I'd really like to avoid bricking hers. Thanks!
get the 'nand tookit'
start phone into magldr, and choose 'usb flasher'
connect usb, run the toolkit, magldr repartition, select 200, and hit repartition. This will partition teh nand AND install Cwm
then, restart, in magldr choose 'ad recovery', this starts cwm, , in cwm - advanced - partition sd car (or words to that effect, i'm not restarting my phone to check) - it WILL wipe your card, so back up anything you wanna save.
So much for the SGS4G being easier lol. Thanks for the information!
adobrakic said:
So much for the SGS4G being easier lol. Thanks for the information!
Click to expand...
Click to collapse
Lol, no native Android phone is as easy to flash as the HD2 is HSPL, MAGLDR, CWM, Partition SD, ROM with no chance whatsoever of bricking it providing you have an EU HD2
Yeah, now that I see how the HD2 is done, I wish the SGS4G did the same.
I came back here for another question, however. My girlfriend said that her phone randomly becomes unresponsive. When she hits a button, the backlight for the buttons comes on, but the screen doesn't turn on. She's forced to pull the battery to reboot and have it working again. It happened once yesterday, and just now as well.
The rom I flashed to her phone is this one. I tried searching that thread, but was unable to find anything. Is that a hardware issue, or software? If it's a software thing, what's a different rom I can flash that won't have the same issue?
Thanks guys.
I offer you my understanding of the issue and what I've read about it. It's not definitive, but hopefully it helps.
The issue is often referred to as the black SOD (screen of death), so you can search this to try to find more. It appears to affect some HD2 roms, as well as various other android devices. As for the cause (hardware or software) I've seen people claim it was certain apps, roms, kernels, even the SD card (some said changing to a 2 or 4 GB card stopped the problem).
I currently have an issue with this, but mine started after I had a cracked screen replaced. When my screen goes black during a call it will occasionally exhibit the same symptoms you described, and I believe my issue is due to the screen install and the proximity sensor. To bring the screen back I hold the screen towards a bright light (or flick a lighter near the proximity sensor) and it's worked every time for me. Not a fix, but if it works for you it beats pulling the battery.
Lastly, my personal advice would be to consider a Gingerbread rom for her phone instead of ICS if there are any other problems. The ICS roms are still undergoing heavy development , where GB roms are usually highly tested and polished.
adobrakic said:
Yeah, now that I see how the HD2 is done, I wish the SGS4G did the same.
I came back here for another question, however. My girlfriend said that her phone randomly becomes unresponsive. When she hits a button, the backlight for the buttons comes on, but the screen doesn't turn on. She's forced to pull the battery to reboot and have it working again. It happened once yesterday, and just now as well.
The rom I flashed to her phone is this one. I tried searching that thread, but was unable to find anything. Is that a hardware issue, or software? If it's a software thing, what's a different rom I can flash that won't have the same issue?
Thanks guys.
Click to expand...
Click to collapse
Hmm, as stated above it could be the SOD, but that's extremely unlikely. This problem never existed on NAND builds and was solved a long time ago on SD builds. I would suggest trying a Gingerbread build (probably CM7 or MIUI, Sense is RAM consuming) and using that instead. No matter what the dev says ICS is NOT stable or fast on the HD2, it's all just advertising. You will not beat the speed of MIUI and CM7 and these are the most stable as well. Assuming your girlfriend isn't a power user MIUI is better as it has a better UI with more eye candy, although you probably will want to replace the stock launcher with GO Launcher because it's simply better than the stock one.
Would you mind linking me to a stable gingerbread CM rom? The one I flashed for her before the ICS one she has now also had the problem of the screen turning off and staying off. I don't mean to seem lazy, but I don't think she'd let me have her phone for long enough to test out all the roms. Thanks again, guys. I appreciate it.
Typhoon, look for it in the nand section.
ALL the ICS roms are still works in progress, no matter how much the author types 'for daily use', they aren't daily useable for everyone.
Gotcha. Thank you!
This ROM is smooth as heaven, have a try!
Hi m8! try this one: http://forum.xda-developers.com/showthread.php?t=769026
it has everything and bat performance is great!!
Cheers!!
***TL;DR***I know now that 4.3 has this bug and it is something we will deal with. I understand the causes, but the problem is buried in the kernel vs the ROM, you can still read my semi adventure but I wanted to make this edit to save you time if you think I found an answer. Overall WIFI is a huge trigger for screen wakes along with shotty or chattery reception.***
First off SlimBean is pretty much the best ROM I've dealt with, so many options, faster then I've ever experienced, and sharp looking. I've been sharking around these forums for 2 years afraid to ever make a name and post due to my lack of knowledge. I love the search options for finding answers that this forum offers to visitors and I've surely used it to root an old AT&T Atrix 4G and now my current DD the Glacier. Now I feel as though I have a little bit of sense of what the heck I am doing and would like to share my path to figuring out how to make SlimBean 4.3 work for me. Who knows maybe this may help some people that have similar problems.
The problem::: On a SEMI clean install of [UNOFFICIAL]SlimBean 4.3 \\ Nightly \\ 22.08.2013 I noticed the Glacier in standby would suddenly illuminated with light although the screen was black. It was enough to light to catch my eyes as I was starting to fall asleep. I ignored it until morning then paid attention to it happening all day at work on and off constantly with the WIFI off and just mobile network, then mobile network off, reboot, nothing seemed to help and I couldn't bare the thought of the phone's screen just on all the time.
After reading threads about HTC's possibly having bad screen made from Taiwan I was in disbelief that it was the Hardware as coming from a year old version of MIUI, I never had a problem with the screen. Leading to the idea it must be a software issue / user issue in which I must of rushed the install of the ROM or it's a quirk in 4.3.
Prior to reinstalling the same ROM, I went with trying other similar ROM's finding [UNOFFICIAL] Carbon 4.3 \\ Nightly \\ 26.08.2013 literally was just released, also a super customizable fast ROM. Everything went smooth until I played music through headphones and the illuminated black screen was back. Now I'm definitely convinced it's the software so I move on to the source code of these ROM's ev_glacier-nightly-2013.08.27.
Ev_glacier-nightly-2013.08.27 Had no screen wakes after 2 hours idle on mobile network only. I wasn't in a location with WIFI as I believe a network with a lot of information chatter may be causing these standby black illumination wakes. Back to SLIM.
SUPER clean install. 1) Format SD card completely 2) fresh download w/ checked md5 of Slimbean 3) Full Wipe "wipe data factory reset" "wipe cache" 4) format/system & format/cache manually just in case 5) Clear Dalvik 6) And fix permissions since although I believe it has no point but it's just so easy to click just in case. Probably doing things double.
Here I am now.. Slimbean is back and nothing but the .zip has been installed along with updating Nova Launcher. I am waiting to reinstall GAPPS so I can first isolate this problem within the ROM itself. What I am noticing is on just mobile network 2g/3g/2g+3g I do not get the phantom wakes, but with WIFI on it so far is only happening about 20-30 seconds after the phone drops into Standby and at least now it's not long lasting, just a few screen black flashes and it's gone. The entire 20 minutes or so I've been typing this, keeping an eye on the screen it's been quiet. Progress is being made.
Now I have thoroughly read up on and used Better Battery Stats, Wakelock detector, and Greenify to help isolate problems prior to the clean install and am waiting to install any Google apps (play store) up until tomorrow so I can pay more attention to my phone and make sure it's just a WIFI wake lock causing the screen to illuminate black. Also was toying with the idea of installing 3.0.64 kernel. I'm curious as to see if it's not just the WIFI wake lock, but all wake locks that actually wake the screen. Once I'm ready to install the play store I'm going to start combing through the device using these fantastic guides and the aforementioned apps...
[GUIDE] The Total Newb's Guide to Wakelocks ::: [HOW TO] Fix Your Skyrocket's Battery Life ::: [GUIDE] Insanely Better Battery Life When Idle
My goal with this long post is to share my experience and also commended these developers on these awesome ROM's. I will post much shorter updates on how I fixed or found the exact problem. Mainly after searching I saw similar issues but not this direct "random black illuminated screen" problem. Thanks, and be sure to call me out on anything contained in this post.
the waiting game
At 9 hours from 100% charge, I'm at 40% battery with on 1.5 hours of screen time. I went through all my settings and disabled all sounds and haptic feed back. I have yet to install any apps and am running off the bare bones of just the ROM. WiFi & 4g mobile data were on all night with the screen flashing only if I used it then locked it with the power button.
Thinking I can live with these timeout 2-5 flashes, I start browsing the forum from my phone, put it down to get ready for work, look back at the phone as it is flashing black screen rampantly on it's own. Then it holds the black screen for a solid minute or two.
WiFi chatter wake lock must be doing this... Reboot to recovery - wipe dalvik - wipe cache - reboot phone. Now to test just 4g network, flash happens on first screen lock, but not as rampant. Hmmm. My next step will be to wait for full battery drain / charge then I want to try the kernal I mentioned above. 3.0.64 kernel.
Funny stuff
Realizing the Kernel I wanted to flash doesn't work with 4.3, I hope at least some of the 86 people that viewed my post got a laugh. Even the older version of SlimBean causes the random screen flashes and the screen on while charging even with the ROM settings for such off. WiFi seems to be the greatest cause. It's as if wakelocks are actually being represented as screen flashes since the kernel is so powerful.
I just don't want to use the CM ROM...
I'm going to dig around the forums further and type in different key words of my problem just to make sure I didn't miss someone already answering this question. Slim has all the functions I always wanted out of my droid and I'm dead set to make it work...or just live with screen flashes I guess.
Hope this is a comedy for someone.
only other link
I've found on the issue I have.
http://forum.xda-developers.com/showthread.php?t=1148057
Non-Stop ROMS
1) SlimBean 4.2 & 4.3 Both have this black screen flicker / black screen wake / black screen on while charging.
2) Carbon 4.3 Had it black screen on while listening to music / black screen constant while charging
3) Evolve 3.3 based of 4.3 seemed to work fine, but I wasn't a fan of the larger Icons and screen, similair to CM 4.3 so I didn't leave it long enough to test...
4.3 CM 4.3 black screen wake almost constant / black screen on while charging... also didn't last long to really test everything.
I am down the river if I want this to just go away. I have installed all these ROM on a completey clean formated SD card each time
I'm sticking with SlimBean as it has the looks and reacts like I expect my phone to. After doing some more searching and after a little time has passed for more 4.3 development there may be a kernel that will work better for me.
Oh here is another dead end I've found... http://forum.xda-developers.com/showthread.php?t=2185747&page=3 [KERNEL] Fixed the flickering screen problem,CM10,CM10.1,SENSE3.6 4.0 4.1 That goes no where...
wifi
WiFi is the biggest culprit for the random screen wakes. I've just been living with it since I dig the slimbean 4.3 ROM so much. Thought I might pop back on here to make some closure. I worked on removing some apk's from the already minimal gapps I installed and will soon start a separate thread on just that. As long as after searching I don't find the same info I figured out.
I think you've got the screen flicker bug.
Try flashing the .69 kernel, it claims to stop the flicker.
Also I know it's got something to do with the WiFi. I know a little about it though.
Sent from my myTouch 4g using xda app-developers app
thanks for the response
N_otori0us_ said:
I think you've got the screen flicker bug.
Try flashing the .69 kernel, it claims to stop the flicker.
Also I know it's got something to do with the WiFi. I know a little about it though.
Sent from my myTouch 4g using xda app-developers app
Click to expand...
Click to collapse
I see you all over the place when it comes to Glacier threads. Today at work I was searching around for a download link. I read through a ton of other ROMS threads hoping it was buried in the comments somewhere. So far I only turned up and old thread with a dead link and a couple of other threads you mentioning to other people to download the .69 KERNEL which I am guessing the full version number is 3.0.69, if it's not then there may be my first problem in finding the link...
*edit
this is the main thread I keep finding, you have so many other kernels on there
http://forum.xda-developers.com/showthread.php?p=43983635&highlight=+69#post43983635
I have a little idea about the screen flicker.
A member called zyGh0st told me. I've pmed Elgin but no response.
I'll pm coderzs too Lil.
Sent from my myTouch 4g using xda app-developers app
reading about kernals
N_otori0us_ said:
I have a little idea about the screen flicker.
A member called zyGh0st told me. I've pmed Elgin but no response.
I'll pm coderzs too Lil.
Sent from my myTouch 4g using xda app-developers app
Click to expand...
Click to collapse
All the Kernels in the Glacier Bible page you have been keeping up seem old. I'm nervous to try one since they obviously seem like they won't work. I'm game to try what ever and post on here my progress so if anyone else stumbles upon the issue they can guide their way through it.
I've been searching "kernel 3.0.69", "kernels 4.3 roms", "jb rom kernel", "4.3 jb kernel", sometimes including the term "glacier" or "MT4G" with little to no luck between XDA and just google itself. I always just find ROMS that just mention the kernel but have no downloads.
Reading your older posts I see that youve already tried the kernel.
Sent from my myTouch 4g using xda app-developers app
K is for kernel
N_otori0us_ said:
Reading your older posts I see that youve already tried the kernel.
Sent from my myTouch 4g using xda app-developers app
Click to expand...
Click to collapse
I tried 3.0.64 kernel, not this mysterious .69 kernel you have mentioned. If you have a link or mirror of it I'll be glad to give it a go.
___________________________________________________________________________________________________
Found how you added the 2 kernels to the Bible page, I just flashed .64 again and I'm nothing but bootloops. I'll give .62 a chance since now I'll have to re-flash Slim.
___________________________________________________________________________________________________
make the double bootloops with either of those 2 kernels. I waited like 5 minutes, restarted the phone to see if it would boot and it just stayed on the slim splash screen. Of course I wiped dalvik and cache before installing either.
Bottom of your 5th post
Sent from my myTouch 4g using xda app-developers app
addiction
N_otori0us_ said:
Bottom of your 5th post
Sent from my myTouch 4g using xda app-developers app
Click to expand...
Click to collapse
Oh yes, I head that already downloaded on the SD but the name CM_SENSE made me think it was a ROM not a kernel. The .66 kernel link is dead, but the .58 flashed & works but there is still the flicker on 4.22 SlimBean. 4.22 is so lame compared to 4.3. Even if there wasn't a flicker on 4.22 I don't think I'd keep it. Those big ICONS are just too much. I think that's why I like Carbon also. Anywho...
My addiction to messing with my phone is always in conflict with work. As if I don't have enough problem solving to deal with outside of cell phones.
I am going to try out the recovery I see in your signature, Recovery : 4EXT 1.0.0.5 RC8, just to see if it makes a difference. If you have the same phone without the same problem I must then eliminate the different variables to find the true problem. I found a "how to" and am either going to put in the time in a couple of hours or tonight. Then I'm going to start the rounds of testing ROMS / KERNELS all over again and I'll post my findings here.
I appreciate the back and forth, I actually got a can't thank anymore message because I used up my 8 yesterday~
Living with it
I've been just living with the screen flash. The ROM is just to sweet to give up. At some point if there it a completely stable 4.3 I may upgrade.
On a regular work day I don't have any available WIFI, so I toggle it off then reboot the phone every morning. I usually get a random screen flash everytime I manually lock / turn the screen off and that's it. With WIFI on I get random flashes at random rates and for random lengths.
Playing music invokes these random black screen wakes also, I've stuck to my old blackberry as my MP3 player...I know that statement seems extemely wrong and against all sciences, but the 9780 bold works perfect as a music player. They had the long-press song skip in the volume button well before anyone added it to Android.
If ever I find the correct ROM / KERNEL combination, or someone else figures out the problem and I find it, I will post it here. This winter I am going to get more into understanding & compiling roms + digging through code so maybe I'll find it myself...ha!
tonyMEGAphone said:
I've been just living with the screen flash. The ROM is just to sweet to give up. At some point if there it a completely stable 4.3 I may upgrade.
On a regular work day I don't have any available WIFI, so I toggle it off then reboot the phone every morning. I usually get a random screen flash everytime I manually lock / turn the screen off and that's it. With WIFI on I get random flashes at random rates and for random lengths.
Playing music invokes these random black screen wakes also, I've stuck to my old blackberry as my MP3 player...I know that statement seems extemely wrong and against all sciences, but the 9780 bold works perfect as a music player. They had the long-press song skip in the volume button well before anyone added it to Android.
If ever I find the correct ROM / KERNEL combination, or someone else figures out the problem and I find it, I will post it here. This winter I am going to get more into understanding & compiling roms + digging through code so maybe I'll find it myself...ha!
Click to expand...
Click to collapse
Have fun man, and If you ever need help or guidance just tell us, we'll be here