Related
Seems sun_dream found yet another build, hes saying is pretty fast, i cant wait till he releases it, heres the link to his blog post
edit:heres a mirror thx to homam_france
He has sent me a beta, which I will be testing sometime between today and tomorrow. I will post some feedback on this. Stay tuned!
I hope the shell won't distort the OK and X Buttons anymore
egzthunder1 said:
He has sent me a beta, which I will be testing sometime between today and tomorrow. I will post some feedback on this. Stay tuned!
Click to expand...
Click to collapse
Great, I just installed Xplode's R3. But i want to try it too.
egzthunder1 can i test it too?
i better get my BA fix up ASAP, the hardware buttons are not so responsive, it seems I am going to be busy flashing
Well,
Day 1 after flashing sun_dream's latest. So far, very fast and stable. Here are the main points (in my opinion anyways)
*Titanium seems a lot more responsive than before (I still don't like it though )
*The removal of windows and menus animations make the device respond faster overall.
*Unbelievably responsive kinetic scrolling.
*The honeycomb is actually usable now!!
*Settings were put back into categories (Personal, System, Communications).
*Battery life seems good, no major drainage.
*"OK and X" bug fixed and working fine!!
*Wifi nice and steady (still need to test PIE8 and Iris Browser).
*Transparent Top bar looks awfully nice! (too bad the programs replace it with the Black bar)
Things I did notice were as follows:
*The Wifi icon seems to be getting cut off from the bottom down. In other words, you can only see half of the icon.
*Power in the Power Settings doesn't show a percentage anymore.
I still need to do some further testing (e-mail setup, etc), but overall this rom is superb!
Will report back later.
Good Job Sun!!!!!
he sent me a beta too but got a big problem...my cradle ain't working anymore!
red_hanks said:
he sent me a beta too but got a big problem...my cradle ain't working anymore!
Click to expand...
Click to collapse
You can always use mtty and flash via SD.
hey Egz...I'd like to try that but I need my cradle so I need to go to a local phone store first thing tomorrow. I tried to fix the cradle myself but ended ruining it more so how is the 2117x build vs xplode's r3? 21169 x2 is so buggy so I flashed my BA back to wm6.1....
red_hanks said:
hey Egz...I'd like to try that but I need my cradle so I need to go to a local phone store first thing tomorrow. I tried to fix the cradle myself but ended ruining it more so how is the 2117x build vs xplode's r3? 21169 x2 is so buggy so I flashed my BA back to wm6.1....
Click to expand...
Click to collapse
I havent' had a chance to test xplode's R3, but sun's is a very nice rom (so far anyways). I still have to test BT (headset and GPS).
One thing I did notice also, is that it seems that data transfer via AS is a lot faster than in previous builds... I guess M$ finally did something right
You can read the rest of my review in my previoius post. Good luck with your craddle situation
A little further testing...
*I purposely soft reset the device and it took approximately 1 minute to wake up completely and loading PointUI Home 2. So, it has a very fast wake up time!!
*I set up my g-mail account with no problem.
*I don't use SMS, so I cannot test that.
*Lock application seems a bit faster and more responsive than in older builds.
*PIE is a bit faster, but I still have other browsers that I like to use. I will test YouTube later (with both PIE and Iris).
Left to do...
*Test BT connection with headset, and GPS (Pharos BT receiver).
*Test IR/BT data transfer... (I have to find another BT and another IR enabled device to do this)
*Must finish going through the settings to ensure that they all work.
Will do more later...
ok seems like 2117x is a lot stable vs the older wm6.5 builds..waiting for your BT test result...
red_hanks said:
ok seems like 2117x is a lot stable vs the older wm6.5 builds..waiting for your BT test result...
Click to expand...
Click to collapse
BT = Bluetooth?
if so, it's always a trouble-maker
i found strange issue with lockscreen, when you have locked your device and pressed power (entered standby) and recieve a call the answer lockscreen part does not show upon device resume, this bug does not happen when device is locked and not on standby - you may try the scenario yourself, i think that this bug is present in 21169 too (no matter sun or my roms)
tested various rom configurations, rebuilded about 20 times this rom, but this nasty bug stays
as of now I am very contented with wm6.1 v3.02 by sun_dream. I need to use my BA so I think I will just wait for a more stable build of wm6.5
Well, I tested (tried to pair really), my GPS receiver, but no dice... For some reason, the device either looses connection or just flat out does not recognize the pass-code. The BT headset, on the other hand hasn't given me too much trouble. It paired up nicely...
@xplode,
I'll give it a shot, but I don't normally use my BA as a phone (unless I am traveling)... which I will do on Monday, so I'll let you know then.
Still stable and no SR so far, except for one time when I was using wifi and my device went into power saving mode (turned off the screen) and afterwards, it would only have a black screen... had to SR there. I tried to recreate the situation on a few occasions with no luck... I guess it was a one time thing.
More reports to come..
well i had the same thing today, blackscreen - only fixed with hard reset
soft reset gets me back to the black screen
This appears to be a secret and private talks thread
Why are others kept in dark about the build 2117x? Once its disclosed that such a build exists, every one gets interested in trying it. If there is a reason for keeping it hidden from others for the time being, better use private messages. Just my two cents.
if we just talk about it, Microhell can't do something about it... now if we link to it here DIRECTLY, then xda-developers is in Trouble.
April 1 said:
This appears to be a secret and private talks thread
Why are others kept in dark about the build 2117x? Once its disclosed that such a build exists, every one gets interested in trying it. If there is a reason for keeping it hidden from others for the time being, better use private messages. Just my two cents.
Click to expand...
Click to collapse
@April 1,
The reason is rather simple. If you release something that has bugs and things (something you would consider a pre-release), you will have an enormous amount of people asking the same questions over and over and over and over.... and over again (kinda like it is right now but worse).
It is a lot easier to develop something when the beta testers are finding all the minor things and not hitting themselves on the face with major bugs that might require hard resets and stuff.
We are not trying to keep anyone in the dark (that is why we are reviewing this build), but sun_dream will release it when he deems it is ready for public use. So far, he has not made mistakes (at least not many) in his ability to judge when a rom is suitable for release.
Just be patient... this should be out soon
Once in a while when trying to answer an incoming call the unlock slider won't respond. I will slide my thumb to unlock and ...nothing. When this happens the call will just go to voicemail . The workaround is to touch the power button to turn off screen , then touch it again to wake it up ,then the slider will work and I can answer the call. Sometimes this takes too long and I miss the call.
This is not a deal-breaker as it only happens 5% of the time , still it is annoying. I have tried different roms with no real difference. Anybody else have this problem? Any advice other than get a new phone under warranty?
Ditto. And I always act as you did to work around the issue, only difference is, I haven't missed a call due to this.
In any case, based on experience, the chance of this happening could be minimized (if not eliminated) by always locking the phone from the "desktop" (e.g. do not lock the phone when an app is running).
BACK STORY:
I remember this happening (more than once) when someone called me up after a train ride. And the last thing I could recall is that I have locked the phone while playing Angry Birds / Fruit Ninja / Zenonia 2, etc.
But it still sucks that it happens.
I guess my real question is , are all Nexus s doing this sporadically , even rarely , or is my phone defective?
question... are the phones plugged in to a wall charger when this happens?
Nope. Only happened to me when I under clocked the CPU with Setcpu using the powersave profile (I was just testing things out).
DKYang said:
Nope. Only happened to me when I under clocked the CPU with Setcpu using the powersave profile (I was just testing things out).
Click to expand...
Click to collapse
can happen any time any place
ransome7 said:
I guess my real question is , are all Nexus s doing this sporadically , even rarely , or is my phone defective?
Click to expand...
Click to collapse
I'm not sure if everyone's having this, but I'm with you on this. I'm on stock but rooted 2.3.3. Experienced this since 2.3.1.
EDIT: My wife has this problem too, since 2.3.1 until 2.3.3 (not rooted).
cygnum said:
I'm not sure if everyone's having this, but I'm with you on this. I'm on stock but rooted 2.3.3. Experienced this since 2.3.1.
EDIT: My wife has this problem too, since 2.3.1 until 2.3.3 (not rooted).
Click to expand...
Click to collapse
Mine did it stock , I rooted and loaded roms to see if that would fix the problem , lessened but still there
My nexus s (i9020T) has exactly the same problem. I've also tried to flash different ROMs, including CM-7rc2 and stock 2.3.3, and the problem remains.
I tried to bind Multi-touch Visualizer 2 to long pressing home button, and found the when screen is unresponsive, it can still detect press near edges very well, but not the center. While I press at the edge and drap across the center, it keeps tracking my finger correctly. In addition, Locking and unlocking the screen can solve the problem temporally. I connect my phone with adb, and tried to "cat /dev/input/event0" The behavior confirms what I see in Multitouch Visualizor 2: the when the center of screen is unresponsive, nothing can be read from the device node.
I read the mxt224 touch screen controller doc, and it seems the chip features self-calibration, and thus I believe the "lock & unlock" will trigger the chip to tune it self in some way. I've also read the driver code of nexus s, htc incredible and moto droid x, all using the same controlling chip. Both HTC and moto would send calibrate command to the chip during resume, but sumsang does not. I guess this might be the reason, but I'm not skilled enough to port the drivers
I experienced it twice so far i think, but only have the device for a little more than 2 weeks.
I am on stock 2.3.1 currently.
Beside the lock&unlock method, I discovered a new way of getting screen back to work: rub your hands a couple of times and touch again... Anyway it seem the screen is not well calibrated.
problem seems fixed with my customized kernel
Last night, I modified the touchscreen driver and mach settings a bit on the source of netarchy's nice kernel, and compiled a kernel of my own. The screen now seems working well with my new kernel
Never have experienced this on the nscollab rom which is cm7 and kernel together stable. I suggest give it a shot
Sent from my Nexus S using XDA App
swa2k4 said:
Never have experienced this on the nscollab rom which is cm7 and kernel together stable. I suggest give it a shot
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
May I know how to perform the suggested steps, i have been experience twice since i bought it on 2 weeks ago
I would like to bring this issue up again (after so long) as I am still randomly experiencing this exact issue even with Ice Cream Sandwich 4.0.3 (Stock & Custom ROMs). Any fix yet?
ROM: Royal Ginger 2.1
Radio: 26.08.04.30
Kernel: ckisgen-smartass-CM7-v1.5 Kernel
Used Navigation yesterday (don't use it very often or for long periods of time) to see how long it would take me to get to a golf course 35 minutes away. Picked up GPS and routing very quickly. However, after about 2-5 minutes, Navigation says "GPS signal lost" and never recovers. While Navigation is running, I check GPS Status and it says it's locked onto 7 satellites.
I exit Navigation, wait about 10 seconds, then re-enter the route, and it's rock solid for another 2-5 minutes (before it shuts off again).
I think this is a Navigation problem more than a GPS problem.
Anyone else having this issue?
Have you tried a different ROM?
I've had this issue on few different roms, never could figure out the cause. Try CM 7.0.3 or one of the latest CM nightlies its fixed in those.
I tired 7.0.3 for an hour, but it gave me some freezing/FC'ing/rebooting issues, so I went with RG 2.1. Maybe I'll wait to see if RG 2.2 will solve these issues before jumping to another one.
While I'm at it, my favorite Denver joke...
Q: What did Josh McDaniels do that John Elway never could?
A: He made Denver a baseball town!
pseudoswede said:
I tired 7.0.3 for an hour, but it gave me some freezing/FC'ing/rebooting issues, so I went with RG 2.1. Maybe I'll wait to see if RG 2.2 will solve these issues before jumping to another one.
While I'm at it, my favorite Denver joke...
Q: What did Josh McDaniels do that John Elway never could?
A: He made Denver a baseball town!
Click to expand...
Click to collapse
I was having similar problems myself. There is a new app that shows how many GPS' locks you have while in maps and since I installed this my GPS s finally working. It's free so maybe give it a try. https://market.android.com/details?id=eu.illyrium.tools.gpsmonitor&feature=search_result
Also have you tried the fixes on Team Royal's GPS fix page ? http://www.teamroyal.net/gps.html
pseudoswede said:
I tired 7.0.3 for an hour, but it gave me some freezing/FC'ing/rebooting issues, so I went with RG 2.1. Maybe I'll wait to see if RG 2.2 will solve these issues before jumping to another one.
While I'm at it, my favorite Denver joke...
Q: What did Josh McDaniels do that John Elway never could?
A: He made Denver a baseball town!
Click to expand...
Click to collapse
Hahaha that's awesome!!!
Sounds like you didn't wipe before installing or if you did all you needed to do was fix permissions
Sent from my HTC Glacier using
XDA Premium App
mark manning said:
all you needed to do was fix permissions
Click to expand...
Click to collapse
I did not do that.
So it worked yesterday the whole time without problems traveling 20 minutes to a friend's house, but it lost connection driving to a place 3 miles down the road. Strange stuff.
Hey fellow Coloradans and others,
I've got an HTC Inspire running MIUI- a CM7/AOSP derived ROM, but I'm having the same (I think) issue. I get a near instant lock every time, but soon after, Navigation "loses" the lock. It happens every time I use navigation. This doesn't happen in Sense based Roms. The other nav program I've used, Mapquest, does not have this issue. I've found that if I toggle GPS off then on again after I open Navigation, it holds the lock. While this is an improvement, its still annoying. I realized we're on different phones and ROMs, but have any of you found a solution that works? I've tried all the recommendations, including the one in this post, to no avail. Thanks for any updates!
metke said:
Hey fellow Coloradans and others,
I've got an HTC Inspire running MIUI- a CM7/AOSP derived ROM, but I'm having the same (I think) issue. I get a near instant lock every time, but soon after, Navigation "loses" the lock. It happens every time I use navigation. This doesn't happen in Sense based Roms. The other nav program I've used, Mapquest, does not have this issue. I've found that if I toggle GPS off then on again after I open Navigation, it holds the lock. While this is an improvement, its still annoying. I realized we're on different phones and ROMs, but have any of you found a solution that works? I've tried all the recommendations, including the one in this post, to no avail. Thanks for any updates!
Click to expand...
Click to collapse
In my case, I flashed to another radio and it fixed that.
metke said:
Hey fellow Coloradans and others,
I've got an HTC Inspire running MIUI- a CM7/AOSP derived ROM, but I'm having the same (I think) issue. I get a near instant lock every time, but soon after, Navigation "loses" the lock. It happens every time I use navigation. This doesn't happen in Sense based Roms. The other nav program I've used, Mapquest, does not have this issue. I've found that if I toggle GPS off then on again after I open Navigation, it holds the lock. While this is an improvement, its still annoying. I realized we're on different phones and ROMs, but have any of you found a solution that works? I've tried all the recommendations, including the one in this post, to no avail. Thanks for any updates!
Click to expand...
Click to collapse
I'm using the stock radio. I used to have that issue but was eventually fixed in cm nightlies. Not sure but sounds like the miui you are using is using older cm code
sent from my Google Nexus 12! yup I'm from the future
metke said:
Hey fellow Coloradans and others,
I've got an HTC Inspire running MIUI- a CM7/AOSP derived ROM, but I'm having the same (I think) issue. I get a near instant lock every time, but soon after, Navigation "loses" the lock. It happens every time I use navigation. This doesn't happen in Sense based Roms. The other nav program I've used, Mapquest, does not have this issue. I've found that if I toggle GPS off then on again after I open Navigation, it holds the lock. While this is an improvement, its still annoying. I realized we're on different phones and ROMs, but have any of you found a solution that works? I've tried all the recommendations, including the one in this post, to no avail. Thanks for any updates!
Click to expand...
Click to collapse
I'm having the same problems too, I haven't found any solution yet. I'm on an HTC inspire with CM7.1 RC1
Hello my name is Xan Steel. I've been trying out roms on this forum for my Epic 4G. However I've run across a lot of bugs in this rom "ACS ICS V6". I would love to be able to post them in the development thread pertaining to the rom, but since I'm under the 10 post limit to post in a dev thread. I would like to ask how I go about doing this the correct way without breaking forum rules.
Thanks in advanced
Xan Steel
Tell us what your problems are here.
1st you have to have 10 post. Go to other threads and comment on stuff like the off topic forum. Then you should be able to post on dev threads. Or you can pm them and let them know.
Sent from my SPH-D700 using xda premium
Well as Neckberg has said to post my issues here (Thanks) I shall.
[ROM] ACS ICS V6.
Where to began.
I came from ACS SyndicateFrozen 1.1.1 I could never get 1.2 to run. And this ROM was based on GB. Really wanted to see what GB was like. SO after installing the ROM. Everything started out normal (no issues at that point). It was sluggish which made me wonder if Carrier I.Q. was still in the ROM. It wasn't listed that it was removed.
SO I started trying things out. Everything was going good until I turned on the Wireless WiFi Tether. It crashed outright. Tried again, and crashed. It would open to a black screen and then crash. So I did some digging, and apparently this is a known issue. So I got a different one from the market that worked (Open Garden WiFi Tether).
I installed Opera. I like Opera for it's desktop mode that actually works over Dolphins. I would type in a address, and hit go, and it would act like its going, and then stop and remove what I had typed. Tried again, and it would load a blank page. Tried a third time, and got the HTML header to load the page in a text format. Uninstalled and reinstalled same thing happen. So I left it alone, and about 3 hours later it had uninstalled itself/completely missing on the phone and market stated it wasn't installed. Rebooted phone, still gone. Not idea where it went. After reinstalling it again. it would do the same thing.
So I flashed and wiped X3. And reloaded the ROM. Thinking I have a bad load.
reinstalled all my apps and even though Opera is still doing it's thing I mentioned earlier, it hasn't uninstalled itself... yet.
Now after the reload of the ROM. Last night I lost cell service (couldn't make calls) but I had data. Which was odd to me. Rebooted the phone, and same thing. Had data but not cell service. After about and hour or so, I have cell and data back together. Maybe it was someone working on the tower in the area at 11pm, or maybe the ROM decided it would be funny.
Another thing I noticed. If you hit the menu button to pull menus in apps and on the home screens. They are white on black. White text and image, on a black background. Now if you go into any sub-menu from the main menu, its black on black. You can't read anything unless your lucky to have a bright white page behind it, so that it can try to bleed through some of the transparency.
The battery icon when charging in portrait goes from normal to skinny (blinking), while in landscape mode it goes from normal to fat (blinking).
Also two music apps is not really needed. One is fine. Trimming down on unneeded apps would help save on space. Also remove Carrier I.Q. if it hasn't been yet.
Adding that super brightness, is actually bad. Not thinking about it, it's actually crashed the video HW of the phone. On a plain white screen at max brightness, it starts to artifact, and if what ever your trying to do doesn't complete. The video HW crashes, and you get a pretty rainbow on the screen until you pull the battery. Basically acts like a dying or dead video card in a PC. Also it can (and has happened to me) cause screen burn in. If you want a image of it let me know and I'll post one.
Also Rom Manager does not recognize any ClockWorkMod Recovery, if you manually install the recovery yourself.
If I find anything else buggy I'll post and update here.
Thanks
Xan Steel
Phone: Epic 4G
ROM: ACS ICS V6
Recovery CWM 3.1.0.1 purple
Note, I haven't tried this rom myself.
No, carrierIQ is not removed on this rom, nor has it been removed on any GB rom that I know of. Still, removed or not, it won't make any difference in the performance of the device.
Any apps that you fine are useless can easily be uninstalled, even if they are installed system/app folder. Rom chefs correct attitude about roms is that they build for themselves first. I personally have 3 music players installed.
We don't have official Rom Manager support so that will be an issue on pretty much all non AOSP roms for the epic.
Your lack of service issue it probably a carrier issue and not a rom issue.
shane6374 said:
Note, I haven't tried this rom myself.
No, carrierIQ is not removed on this rom, nor has it been removed on any GB rom that I know of. Still, removed or not, it won't make any difference in the performance of the device.
Click to expand...
Click to collapse
Ah makes sense. It's relatively new, and most likely not been worked on yet.
Any apps that you fine are useless can easily be uninstalled, even if they are installed system/app folder.
Click to expand...
Click to collapse
Ah, then I should be able to remove them myself fairly easily.
We don't have official Rom Manager support so that will be an issue on pretty much all non AOSP roms for the epic.
Click to expand...
Click to collapse
Do you know if that is something being worked on?
Your lack of service issue it probably a carrier issue and not a rom issue.
Click to expand...
Click to collapse
It's a good possibility since it only happened the one time, but since it is a beta, and I'm using it for the first time. I felt it needed to be brought up just in case it wasn't. Heh beta tested a lot of new software, and got into the habit of reporting everything, even if it looks like something else is the issue and not the software.
Many Thanks
Xan Steel
***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