Database Users

Walking dead.... I can't be the only one

Ok I'm using newest energy cht rom radio 2.12.50 and shubcraft froyo android build with 384 zimage....
Heres the problem that I have had all week my phone works fine when I am stationary minimal screen freezes great speed but when I get up and walk with my phone and try to use it the screen freezes almost every time then the entire phone freezes. I have also noticed this on elevator and when I step out of my car.. this is weird and I know it can't be just me as its been going on for a week now.
So to sum it up stationary best phone ever...walking phone dead and I wanna slam it on the ground.
Sent from my HTC HD2 using XDA App

try the desire v5's zimage, no freeze at all

Im having same issues,with all the version i have tried, including V5 aparently this screen freezing is a known issue and makes the use of Android in our HD2 very very frustrating.
ive upgraded my SD to a class 6 and still suffering from it
Im wondering if there is a program that causes it or its just the OS...
in any case We have to be patient ,im sure pretty soon the amazing developers will come with a solution.

might be a screen rotation issue

Just came back from street, again same issue.
I thought it may be the network connection that was affecting the phone, so i switched to Airplane mode and turn off automatic updates,still this didnt help...
so im beginning to think this is related to yes,either the screen rotation (maybe as we walk it does affect the sensor )or gps..

miko3d said:
Just came back from street, again same issue.
I thought it may be the network connection that was affecting the phone, so i switched to Airplane mode and turn off automatic updates,still this didnt help...
so im beginning to think this is related to yes,either the screen rotation (maybe as we walk it does affect the sensor )or gps..
Click to expand...
Click to collapse
I've just learned to deal. Its better than SoD's or being in Winmo and having to pull the battery out.

I actually noticed it today as I went from a dark room to a very well lit room so Im with u guys it seems its either rotation issue or light sensor issue andvi have no doubt in my mind the devs will have it fixed in no time just didn't see it mentioned anywhere else so figured it was worth a mention. Thanks all I'm so glad I'm not alone on this one.
Sent from my HTC HD2 using XDA App

when in windows mobile make sure to disable all battery and back light settings and in android change blacklight settings and sleep setting to stay on

I am having the same issue - using ChuckyDroidROM + shubCRAFT CM6RC2, basically when I start moving or even moving the phone the touch screen becomes very unresponsive and sometimes even the hardware buttons don't function properly. At first I thought it was just my device until I saw this post...

Think its a bug with manusfreedoms 384mb ram enabled Zimage dident get this problem using past images.
sure it will be sorted next image release.

I thought i was alone in this case too !
We are not a lot with that screen touch lag, so maybe we did something wrong. Here is what i found so far :
-Changing build don't rix the problem
-tried another radio, another rom...nothing.
I tested 27/07 03/08 cotulla zimage, now manufeeedom 382mo zimage-nopc, the problem is still here.
changed from a class 2 to a class 4 and seems to be worse. (!)
You are right, it seems to be worse when i am moving from one room to another so maybe it is gsensor related.
Right now it is hard for me to type that text,
Don't know what to do... buy a class 10 sdcard ?

I just got my HD2 today and got android set up. I'm noticing the same thing as everyone else with the unresponsive touchscreen. It happens every time I tilt the phone to try to change the screen rotation. Usually hitting the hardware button allows it to respond once again, but it happens quite often.

hey hey hey first and formost i see u guys all hav the same issuse what i dont see is ur device info along with the rom, radio, android verison, and the location ur android is stored ... i have the lates verison of droid v5 also energy with cookie full and my radio is 2.8 i believe android is on the sd card and running smooth ... now that the intro is out of the way hav u guys read what was needed , reason askin i found the thread where the question and answer is... and yes u guys are the only ones... now please do a search go up to the first thread of android on hd2, and good day to u all

Wingtytn, can you be more precise in your answer ? I am a quite long user in Xda, always try to help when i know and i never ask a question wich have been answered somewhere. I don't think i have the noob profile you seems to write. If you think about formatting sdcard, of course i did. I have a 2.08 radio, latest shubcraft build with manufreedom 382mo zimage. My rom was changed to a light android dedicated one, the latest chuckydroid rom. Just don't know what else to do and waste a lot of time trying to fix that from myself.
Sent from my HTC HD2 using XDA App

The TS issue is kernel related, that's why using an older kernel say the no speedy one should fix it. This is also the reason why this issue is being seen over multiple builds.
Sent from my HTC HD2 using XDA App

shu8i said:
The TS issue is kernel related, that's why using an older kernel say the no speedy one should fix it. This is also the reason why this issue is being seen over multiple builds.
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
Thanks a lot shu8i, i will try an older zimage than the 27/07's cotulla.
Edit : Mmh exact same problem with the 23/07 zimage Cotulla_zImage_CABDET_NOSPEEDDY. That is weird.
I will order a clas 10 sdcard and see what happen...

Try the game ”Runners”. It uses both the camera and the g-sensor and freezes mad anytime, anywhere. Huge affirmation to the idea it's a bug of the g-sensor's or otherwize the screen's drivers.
DuperMan

Me too with screen freezes, i had tried all builds and same result. I think this is a problem with SD access because i noticed more freezes as more apps opened in backgroud.

Try to calibrate the g sensor

Found something ...
try disabling auto-rotation feature (settings -> display)
It works perfectly for me now.
Can you confirm that works for you too?
Did you dind a way to calibrate g-sensor on froyo?
Why the auto-rotation feature hangs so much for us?
Sent from my HTC HD2 using XDA App

(Possible solution) Freezing Issues

hardik119 has found out that going to account & sync and disabling background data has stopped his device from freezing and it has also stopped mine afer 1 hours use. Before it was freezing about every 5 minutes. With doing this I have also disabled setCPU, auto screen rotate and removed gsensor.dll in windows mobile. Please try this out and respond if this has worked for you because maybe we can get a perminant solution. Thanks and also thanks to hardik119 for his extensive testing and possible solutions he is finding all the time Android is usuable on my device hopefully will be for everyone else aswel. Also sorry for opening another thread but there doesn't seem to be any action on hardik119's original thread.

maybe suggested solution works...but...wot is android without data background?

If you disable background data, doesn't that like stop gmail and weather and such updating automatically??

leginag said:
If you disable background data, doesn't that like stop gmail and weather and such updating automatically??
Click to expand...
Click to collapse
Yep...sure does..

the_scotsman said:
Yep...sure does..
Click to expand...
Click to collapse
As has been suggested above...that is kind of /fail.
I'd prefer to live with the occasional few second freeze than not have constant updates.

I applied the RC 7 and my screen freezes are gone. Using this image with mattc nexus 1.0 rom,
http://forum.xda-developers.com/showthread.php?t=756513.

Pretty sure he's just looking for testers to confirm the association. That way developers can narrow down the cause of the issue and possibly fix it. Stop whining about the "solution" he suggested.

Touchscreen freezes still exist

No freezing issues as long as you get the right WM build and android port. Mine is 100% freeze free thanks to the awesome devs here at Xda.
I have auto screen rotate on and still no freezing or SOD. I am using Darkstone's 2.1 build full time now.
Fyi.
Sent from my Hd2 using XDA App

Giving some details about your setup, WM Rom, Current android build/zImage radio etc. might help people participate more. Data connection does cause some freezing but if your saying you were getting freezing every five minutes before you turned it off, then something sounds wrong as mostly people are reporting little or no freezing.
You mention the G sensor and this is a known problem and a work around is to calibrate the G sensor in WM before turning on android, this has helped me.
I also find the kernel has an impact, I found freezing in all the undervolted/ overclocked Images, although Michyprimas latest kernel is the best to date, I have not had a freeze yet.
I found that the stock ZImage from 23rd August had no freezes in my setup.
I've no doubt that the sd card is playing some role and you may wish to experiment with changing that.
Im sure you've tried all this but you need to have the latest Hardspl V3. Do a task 29 to wipe your nand. Install a very light WM ROM, Im using my own WM 6.5.5 ROM but there is a better one by Miri V18 extra light and of course the one listed here such as chucky's ROM etc.
Format the SD card before installing the Android ROM.
Use radio v2.12.50.02.
Try Xcelsior ROM when I tested it I found it very stable.
If you already tried these thing and have had freezing every five mins, then I would suspect your sd card, but its just a guess.
There is a thread somewhere by cotulla asking for participants to isolate this problem so you need to submit your findings there (again if you have not done that)

Thanks for the tips currently using maths 1.5b Rom with 23rd kernel
Hspl3 & radio .12 aswel also tried with calibration on the g sensor in winmo and also deleting sensor.dll also using energy light but have also tried with Miri light the only build I haven't tried so far is the one you mentioned so will give it a go. Thanks
Sent from my HTC Desire using XDA App

Hi I can confirm the disable background sync fix works for me.
Running
- Android O.K. v2.6 [Kumars Leo Touch Premium]
- Mattc 1.6
- Radio 2.12.50.02

LondonTownGuy said:
Giving some details about your setup, WM Rom, Current android build/zImage radio etc. might help people participate more. Data connection does cause some freezing but if your saying you were getting freezing every five minutes before you turned it off, then something sounds wrong as mostly people are reporting little or no freezing.
You mention the G sensor and this is a known problem and a work around is to calibrate the G sensor in WM before turning on android, this has helped me.
I also find the kernel has an impact, I found freezing in all the undervolted/ overclocked Images, although Michyprimas latest kernel is the best to date, I have not had a freeze yet.
I found that the stock ZImage from 23rd August had no freezes in my setup.
I've no doubt that the sd card is playing some role and you may wish to experiment with changing that.
Im sure you've tried all this but you need to have the latest Hardspl V3. Do a task 29 to wipe your nand. Install a very light WM ROM, Im using my own WM 6.5.5 ROM but there is a better one by Miri V18 extra light and of course the one listed here such as chucky's ROM etc.
Format the SD card before installing the Android ROM.
Use radio v2.12.50.02.
Try Xcelsior ROM when I tested it I found it very stable.
If you already tried these thing and have had freezing every five mins, then I would suspect your sd card, but its just a guess.
There is a thread somewhere by cotulla asking for participants to isolate this problem so you need to submit your findings there (again if you have not done that)
Click to expand...
Click to collapse
where to fing the original zimages not the overclocked

touch screen freez reason
I nenarly identified the reason of touch screen freezing ,,it is possibly in the touchscreen kernel ,download figure race from market and the touch screen fresez due to random pess of touch screen with both hands ,I think this is the main problenthl

hoss_n2 said:
where to fing the original zimages not the overclocked
Click to expand...
Click to collapse
http://oe.netripper.com/files/htcleo_autobuild/
23rd august is very stable, you also get usb sinc working and HTC sync.
You need to download the corresponding modules to extract the BCM and TUN files for wi fi to work.

INFO: BATTERY AND LIGHT or PROXIMITY SENSOR

i posted this in the mdjeey thread but i don't if it is of any use i will repost it here
" i thank mdj for his work , this morning i noticed something that could explain the eratic battery drain of our device , when i was filming for a friend some configuration instructions ( which is by the way , by far simple than writing it ). the proximity sensor emits flashing lights permanently ( not seen by eye but only with the film) thing i could not reproduce on wm.
my radio is the latest one , my wm rom the latest of dutty, my android build the mdj sense hd 4.4 with 7.7 kernel.if someone treated the subject before excuse then if not, has somebody noticed this , mdj what do you think about it ?
edit :http://www.youtube.com/watch?v=BkyYFLUjzaM and http://www.youtube.com/watch?v=M1hdqIFzquw "

You just might be on to something here...
I just tried this myself with the built-in iSight of my iMac. Apparently the proximity sensor is an infrared sensor, which uses ir light pulses to calculate distance.
Within Android it starts emitting pulses as soon as you unlock the phone. It stays pulsing until the phone falls asleep. So, that I can confirm.
Within Windows Mobile (see my WM ROM in my signature), it doesn't show up. However, I noticed, that my proximity sensor doesn't work anymore in WM. I don't use WM anymore, that's why I installed a minimal build.
Could someone check with a stock ROM when the proximity sensor is working (just keep it in front of your webcam to check). I suspect it only works when you're using the dialer, or when a call is in progress.
If the devs would be able to limit the activity of the proximity sensor to the dialer or use it in conjunction with the g-sensor, it might decrease the drainage.
Sincerely,
Mac

I just tried for myself and I can also confirm this. Build is NexusHD2 v1.6 by tytung. Kernel hastarin 8.1. Also, this is not visible by naked eye but is visible when filmed with camera.
update.
Just updated to v1.8, kernel hastarin 8.5.3_oldcam and same behavior occurs. In meantime I tried WM and sensor is offline until call is established

dusko_m said:
I just tried for myself and I can also confirm this. Build is NexusHD2 v1.6 by tytung. Kernel hastarin 8.1. Also, this is not visible by naked eye but is visible when filmed with camera.
update.
Just updated to v1.8, kernel hastarin 8.5.3_oldcam and same behavior occurs
Click to expand...
Click to collapse
Do you have stock WM ROM to check it's behaviour?

No. Energy cookie rom here. As I said before, in WM this "IR blinker" is off until I establish call. then goes off again after call is finished.

That is a really good catch and I can confirm that my HD2 in android also does the same thing. When I press the end call key for it to go in standby the light goes off as soon as I press the end call button to wake it up it starts flashing again.
Edit: I should also note that I'm using MDJ 4.3 Android build, and Windows Mobile is stock from TMOUSA

I've seen this mentioned before. I hadn't thought of using my webcam to view it.
I'm unsure if this is a bug with the kernel, or a side affect of the way Android works.
I've noted it on my list but unfortunately kernel development seems to have stalled lately and I'm not sure the main devs are even looking at my list.
Hopefully things pick up again in the new year.

I think it is the same chip that handles light and proximity sensing, called cm3602, so as long as you have auto backlight enabled, you will see the blinking.

drizztje said:
I think it is the same chip that handles light and proximity sensing, called cm3602, so as long as you have auto backlight enabled, you will see the blinking.
Click to expand...
Click to collapse
i am not an expert in the domain of electronics, so i'll take the thing about the chip for granted, but the thing about autoblacklight , i don't think is the answer cause the autoblacklight in WM is on and that blicking thing does not happen !
and my purpose was not to incriminate this or that , but to say just that ,that thing could be the reason why the battery drains so fast on android builds (other than the permanent internet connection )

sbibif said:
i am not an expert in the domain of electronics, so i'll take the thing about the chip for granted, but the thing about autoblacklight , i don't think is the answer cause the autoblacklight in WM is on and that blicking thing does not happen !
and my purpose was not to incriminate this or that , but to say just that ,that thing could be the reason why the battery drains so fast on android builds (other than the permanent internet connection )
Click to expand...
Click to collapse
I didn't make a hard statement, I just said what I think, so you should not take it for granted. I didn't test it extensively in WM, but I saw the blinking in WM for a short period before EBL started android boot. Are you 100% sure that the blinking is not there in WM even if the light sensor is working? I tried to find some info about cm3602, it seems to be a dumb device without any configuration interface.

check dmesg if it is full of "intr_status=0x02".
The problem is that when you use toolchain other than 2010q1 (http://www.codesourcery.com/sgpp/lite/arm/portal/release1293) ,
proximity sensor driver doesn't work properly. After its first activation, it just doesn't stop. It continuously polls in an infinite loop. That's why you see those blinkings which are probably infrareds. It was causing too much current drainage (65mA) for me even in suspend. Now, i used the above toolchain to compile the kernel and it is around 10mA in suspend.
So; if you are compiling your own kernel, use the above toolchain. If you are using someone else's kernel, tell him to use it.
EDIT: I realised that this isn't the problem that you observe, this was just another problem that I faced.

this need to be a sticky or in dev section.....imo

i saw a video of how proximity sensor work on a HD7
http://www.youtube.com/watch?v=wpvaEAJguWA&feature=player_embedded

vua777 said:
i saw a video of how proximity sensor work on a HD7
http://www.youtube.com/watch?v=wpvaEAJguWA&feature=player_embedded
Click to expand...
Click to collapse
Our problem is, proximity sensor is running even if there is "no call". It should be online only during the call for power saving purposes.

dapoharoun said:
this need to be a sticky or in dev section.....imo
Click to expand...
Click to collapse
+1 on this

Seeing this problem in miui builds when getting ~60ma standby

Should I be able to see it when recording with a regular hdv camcorder? I tried it but don't see the light.
Edit: My mistake, it is there just very small and I had to zoom way in. It's on as soon as the screen turns on and stays on. It does turn off though when the screen goes off. It does explain that I get good standby power drain but when typical useage time is not nearly as good as winmo.

oh man .. this is really good stuff .. if this is true .. and this really solves the high battery drainage on andriod(on HD2) .. i would be so damn happy .. no reason to sell my HD2 and get the Desire HD anymore.
thanks to threadstarter

I couldn't find anything to disable the proximity sensor but I found a small program that reports the sensor readings.
When I put my finger over the sensors, the light sensor takes about 2 seconds to go from 160lux to 10lux, while the proximity sensor changes instantly from far to near.

the blinking does not make the screen react more quickly when in call

[Q] andriod on htc hd2 struck on black screen after a call

Hi
I have a HTC HD2
and i installed andriod nand rom on it with the following things
HSPL 2.08
Radio 2.15.50.14
MAGLDR 1.12
i installed almost 10 andriod roms and find the same problem
after making or receiving a call screen goes into black screen and hangs up. i have to reboot the device by removing the battery. i would appreciate if any one can provide me the solution to fix this problem as i love andriod roms.
thank you

mohammedmazher said:
Hi
I have a HTC HD2
and i installed andriod nand rom on it with the following things
HSPL 2.08
Radio 2.15.50.14
MAGLDR 1.12
i installed almost 10 andriod roms and find the same problem
after making or receiving a call screen goes into black screen and hangs up. i have to reboot the device by removing the battery. i would appreciate if any one can provide me the solution to fix this problem as i love andriod roms.
thank you
Click to expand...
Click to collapse
I am facing this only when battery is bellow 15%. If this is the case then just charge it before it goes to 15%.
If that's not the case then you can try installl MAGLDR v1.3
Do you have this issue in Froyo or Gingerbread ROMs? or in both? What version of CWM are you using?

I have the same problem on MIUI since after approximately 1.3.18 (cutover from Froyo to Gingerbread). Also have this problem on CME DHD2 Compact.
It is also an issue if someone tries to call me.
Sometimes, if I try waking the phone from sleep (power button) and it hits the black screen, and I wait long enough, it will wake. But again, the only real fix I know is pulling the battery.
I am running MAGLDR 1.13
Also, another fix that works sometimes is plugging in the phone into a power source e.g. laptop USB port

It's something about light sensor, when you put your screen into a strong light it would be turn "unblack" again. I don't know how to fix it, is this a problem with this hardware because it's broken or my version of LEO doesn't support NAND full functionaly.
Begging for answer!
i know about my poor english

I have this problem too.. running latest Hyperdroid rom by pongster (magdlr version) and it's driving me crazy. Sometimes phone wakes up normally after a call like it shoud, sometimes is stuck with black screen for few minutes, hours even (although i can't wait that long so i pull out battery)..
Back on WinMo everything worked normally, so it's not an hardware issue with proximity/light/whatever sensors
Is there any fix out yet? I googled and searched this forum a lot and haven't found nothing much helpful, ony a couple of threads with bunch of people with same problem like me. An option for disableing those sensors would be just as good, i've tried few apps for keeping the screen awake and none of them actually worked..
Any help is appreciated.. thanks in advance.

Bump!
Anyone? :/

I have the same issue - running Gingerbread, MAGLDR 1.13
Very annoying cause everything else works super.
Temporary solution i use is to use headset / handsfree. Then there is no problem.
So experts on XDA, we are begging for a fix for this!

I have the same issue since first Android roms and never found a real solution for the problem.
Instead i found a bypass that works for me reasonably well (99% of the cases the screen turns on after a call).
I installed the following 2 applications that wakes up my screen after the call (install then enable each one):
1. Screebl - https://market.android.com/details?id=com.keyes.screebl.lite
2. Modified version of SpeakerShake - http://forum.xda-developers.com/attachment.php?attachmentid=449922&d=1290758421
I suspect this issue is somehow related to hardware failure in light sensor. Installing these programs solve this problem for me.
Also take a look on the following thread:
http://forum.xda-developers.com/showthread.php?t=835127

I have had the same thing happen to me but only around 2 or 3 times in a about 3 months of usage. Had it on both CM7 and MIUI Gingerbread ROMs regardless of battery percentage.
MAGLDR 1.13

Some users experience this using SetCPU
if you have a profile for screenoff and it's set to the lowest frequency, try to set the frequency to something above 500 MHz.
If you have smartass set as governor, then even setting the frequency to it's highest (without OC) during screenoff wouldn't change anything in battery performance, but the device will wake up faster.

Your setup works for me as well - until we`ll see a fix for it this will do

Quiethinker said:
I have the same issue since first Android roms and never found a real solution for the problem.
Instead i found a bypass that works for me reasonably well (99% of the cases the screen turns on after a call).
I installed the following 2 applications that wakes up my screen after the call (install then enable each one):
1. Screebl - https://market.android.com/details?id=com.keyes.screebl.lite
2. Modified version of SpeakerShake - http://forum.xda-developers.com/attachment.php?attachmentid=449922&d=1290758421
I suspect this issue is somehow related to hardware failure in light sensor. Installing these programs solve this problem for me.
Also take a look on the following thread:
http://forum.xda-developers.com/showthread.php?t=835127
Click to expand...
Click to collapse
Yup, this worked for my setup to - thanks!

hi guys ! i can`t realy figured out how to set it . shall i use only one app or both ? and wich settings should be ?

xanthrax said:
hi guys ! i can`t realy figured out how to set it . shall i use only one app or both ? and wich settings should be ?
Click to expand...
Click to collapse
(install then enable each one):
Click to expand...
Click to collapse
Incearca Sanity app, cauta pe Market, mie aceste doua nu mo ajutat

with me is so but only if I navigation (Navigon) and to have someone call me and then left the screen black and I can not make

try to change the kernel. that works for me

hey guys! i found the solution goin through the market!
download an app called "Sanity" theres a free version in the regular android market.
go to the settings > general > check "Reverse Proximity" (This will give you some warning about not using it if you DONT have a buggy proximity sensor). Check it anyways. Then go back to preferences then click "Proximity" scroll down and uncheck Turn off screen and leave leave the Turn on screen checked. this will force your phone to stay on during calls so that it never has to go through the proximity phase of calls this no more black screens. Hope this was helpful ^_^

Thanks!
I had this problem aswell. MIUI & Cyanogen mod were the ROMs I was using, and this problem started occuring after a few months use (my screen is also damaged from a fall, so maybe the sensors are a little damaged as well).
When I installed the WinMo 6.5 stock ROM again, everything was normal, except that my screen still turns black during calls BUT I can activate it again by pressing the power button.
Now I installed android again and the Screebl app (enabled it) and I have the same functionality! The only problem that remains is that my screen still turns black during calls, so I have to answer with the phone button and putt down phone with the power button. Still beats having to remove the battery though .
If someone has a fix for the black screen, it would be more than welcome!
But, thanks a million for the Screebl app tip! I can use my phone again .

papaganz said:
Thanks!
I had this problem aswell. MIUI & Cyanogen mod were the ROMs I was using, and this problem started occuring after a few months use (my screen is also damaged from a fall, so maybe the sensors are a little damaged as well).
When I installed the WinMo 6.5 stock ROM again, everything was normal, except that my screen still turns black during calls BUT I can activate it again by pressing the power button.
Now I installed android again and the Screebl app (enabled it) and I have the same functionality! The only problem that remains is that my screen still turns black during calls, so I have to answer with the phone button and putt down phone with the power button. Still beats having to remove the battery though .
If someone has a fix for the black screen, it would be more than welcome!
But, thanks a million for the Screebl app tip! I can use my phone again .
Click to expand...
Click to collapse
I also try with WinMobile and the problem was still there ...
I think the sensor is broken ....
I will bring my phone to service ... and when i take it back I will tell you whether it is repaired

Solution
I had the same problem with Android roms on my HD2. I saw in an other thread a member (z-o-r-r-o-, thanks btw) wrote "just clean dust on the screen, where sensor is situated". This looked like a joke to me, but it's not. On a review of the phone I found the place of the proximity sensor. This is on the top of your screen next to the speaker, on the left if you look at the screen. I just took off the protection layer of the screen and cleand the sensor and the problem was solved. So I cut of a bit from the protection layer so that the sensors arn't touched by anything.
I think the problem is that this sensor is much more sensitive with android roms.
Hope this works for you to.

["Somebody's" CM10 & "That" rom] Bug/fix reports & newest info (26-Oct-2012)

["Somebody's" CM10 & "That" rom] Bug/fix reports & newest info (26-Oct-2012)
Firstly, I would like to give a big Thanks to "somebody" as well as the dev team at the behind of these roms for their efforts to bring ISC & JB as great things to our device.
Recently, I've tried both the ICSROM (known as the tune of leaked Rom under CWM flashable zip - Let's click Thanks for Upndwn4par) and "somebody's" CM10 (let's click Thanks for ticiano_arraes) and saw that they both have identical issues as reported by people such as the battery life, the deep sleep, the camera flash... including working fixes. But the fixes spread over the pages of threads caused inconveniences for us to track or update info. So I would like to open new thread just for purpose of collecting bug reports and the fixes from and for both users and our devs to get latest info on these roms quickly.
Admins please feel free to delete if this thread is already opened or if it's just not neccessary.
Belows are lists of great things of ICS/JB given by these roms that you can taste right now, and also the list of bugs/issues along with the best possible solutions that you can try for workaraound while waiting for the perfect release. The lists will be updated upon report from you guys. So please provide any thing from your experiences on these roms.
* Great things:
** For both roms:
+ Touch sensitivity is a big improvement in speed and accuracy (this might be inherited from Butter Project)
+ HDMI mirror works fine.
+ Others (pls share your experiences...)
** Individually for each rom:
ICSROM:
+ Webtop 3.0: work like a charm!
+ New Camera/Camcoder by Motorola with various valued upgrades such as Auto continuous (live) focus mode even for camcoder, full HD capture...
+ FingerPrint scanner @first steps of working (worked but not yet supported by original ICS/JB).
+ New valued apps added, such as Smart Actions (similar to Tasker, Locale but more intuitive/friendly/efficient), MotoPrint (valued add not only for business man but even for home usage), Battery Tracer (for battery monitoring with rich info)...
"Sombody" CM10::
+ All great things from CM10 as you experienced with such as Epinter's rom...
+ Camera/camcoder: worked.
+ 2D hardware accelerator: worked.
+ Data/GPS/Wifi/Bluetooth...: worked fine.
* Bugs/issues and workarounds (Newest update info are sized in big text, this helps you guys to track info more quickly):
1. Camera flash doesn't work properly: (Fixing is in progress...)
- Temporary solution: Turn on the torch while capturing in dark (shouldn't keep the flash on continuously over 5 min for safety of the LED flash light)
2. Deep sleep problem (which causes your phone cannot wake up upon power key pressing): CM10 23-Oct build FIXED. But some users reported that the bug is still there on their Atrix. So, the best way is that you flash and experience yourself to check whether the fix works on your device
If this problem still persists on your Atrix, try one of solutions belows:
- Solution 1 (confirmed): Remove the external SD card.
- Solution 2 (Edited: seems not worked): Turn off any screen unlocker (Choose None in Screen Unlock Options)
- Solution 3 (needs more confirmation): Just reboot your phone once or serveral times after rom installation
- Solution 4 (provided by Pont91-unconfirmed):
+put all media files on internal SD;
+deleted all files created by any app on the external SD;
+set internal storage as main one for all the apps data (downloads, photo, rec, backups, etc.).
- Solution 5 (worked with many users): Set Never for Screen Timeout in Settings/Display, remember to press Power button to turn off the screen instead
3. Randomly reboot issue: (the phone suddenly reboots for unknown reason):
- Solution 1: (need more confirmations): Remove the SD card.
- Solution 2 ("Somebody's" CM10) : (need more confirmations): Turn off Wifi :cyclops: There are two guys who provided that:
+ Either turning off Wifi
+ Or set Wifi to NEVER SLEEP (Always on) by: Settings/Wireless & Networks/Wifi Settings/Advanced/Wifi sleep policy
can help stopping reboots. Not only for this problem, but even the issues of heat and deep sleep can also be improved. From their reports, it seems that there is some problem related to the Wifi driver with "those libs". So, try this solution at your own case and help our devs by confirming this way again. Tks.
4. The heat issue (the phone seems to keep hot all the time): The issue seems to walk along with the deep sleep problem, so the issue may be cleared when the fix for deep sleep is applied.
5. The battery life: So bad
Both ICSROM (known as the leaked ICS) and CM10 with "those libs" have an identical problem of battery life. As shown on my phone, the battery drains from 100% downto 50% just after a couple of hours in usual use, even if your phone is in idle state.
No fix yet for this issue But you can apply some of following improvements:
- Lock (freeze) unnecessary AT&T apps and services (ICSROM only)
- Turn off Auto Syn (Manually mode instead)
- Turn off or lock all tracking/reporting sevices you doubt
- Use static wallpaper instead of live one
6. Ram low or several other suggestions only for ICSROM: clike here
7. The I/O performance is a characteristic weakness of both roms which are using "those" libs. You can see this on the results report of Quadrant. Essentially, you can see that the data processing speed is significantly slower than the CM7.2 by using, for e.g, Call Log Backup & Restore, etc...
No yet improvement for this disadvantage of both roms
8. Blackscreen issue after a lock/unlock: CM10 23-Oct build FIXED. But some users reported that the bug is now still there on their Atrix. So, the best way is that you flash and experience yourself to check whether the fix works on your device
9. Black incoming call screen and blackscreen issue after a call: CM10 23-Oct build FIXED. But some users reported that the bug is now still there on their Atrix. So, the best way is that you flash and experience yourself to check whether the fix works on your device
...Other issues (please share and provide your own solution...)
Thanks for continuous reports from you guys!
(To be updated...)

flusshd said:
Firstly, I would like to give a big thanks to "somebody" as well as the dev team at the behind these this rom for the efforts to bring ISC & JB as great things to our device.
Recent days I've tried both the leaked Rom and "somebody's" CM10 and saw that they have the same identical issues as reported such as the battery life, the deep sleep, the camera flash... and some working fixes. But the fixes are spread over the pages of threads that cause inconveniences for us to track or update. So I would like to open new thread for collecting the bug reports and the fixes from and for people to provide quick update info on these roms.
Admins please feel free to delete if this thread is already opend or is not neccessary.
Belows are lists of great things and also the bug reports along with the possible or even just temporary fixes that you may should try to resolve. The lists will be updated upon report from you guys. Please provide any thing from your ecperiences on these roms.
* Great things:
+ Camera/camcoder worked.
+ 2D hardware accelerator worked.
+ Data/GPS/Wifi/Bluetooth... worked.
+ FingerPrint scanner @first steps of working.
+ Touch sensitivity is excellent (this might be inherited from Butter Project)
+ Others (pls share your experiences...)
* Bugs and most likely fixes:
1. Cammera flash doesn't work properly: No any fix yet.
2. Deep sleep problem (which causes your phone cannot wake up upon power key pressing):
- Solution 1 (confirmed): Remove the external SD card.
- Solution 2 (unconfirmed): Turn off any screen unlocker (Choose None in Screen Unlock Options)
3. Reboots issue: No solution yet.
4. The heat issue (the phone seems to keep hot all the time): The issue seems to walk along with the deep sleep problem, so the issue may be clear when the fix for deep sleep is applied.
5. Other issues (please share and provide your own solution...)
Thanks in advance for continuous reports from you guys!
Click to expand...
Click to collapse
Thanks For your report!
My phone is an US AT&T. Installed ICSROM yesterday (WOW!!!) and confirm what you posted.
Biggest bug is the battery. It seems to consume 1% every minute! In an hour I was down to 40% after full charge and using Play Store on wifi. Webtop/Mirror mode works awesome! Watched some HD videos and listened to some music... all good. After using the HDMI connection, I confirm that you will not get black screen until you reboot the phone. Turning off any screen unlocker does not fix the deep sleep bug. 1 reboot. Overall, it is very good.
Keep up the great work and thank you for your efforts! :highfive:

flusshd said:
* Bugs and most likely fixes:
1. Cammera flash doesn't work properly: No any fix yet.
Click to expand...
Click to collapse
I think I saw some workaround suggested by somebody to turn on the torch before using the camera. This way, you've a constant camera flash
Not sure whether it works as advertised, I've not used this ROM yet.

gkarthik16 said:
I think I saw some workaround suggested by somebody to turn on the torch before using the camera. This way, you've a constant camera flash
Not sure whether it works as advertised, I've not used this ROM yet.
Click to expand...
Click to collapse
Thanks for the suggestion !

gkarthik16 said:
I think I saw some workaround suggested by somebody to turn on the torch before using the camera. This way, you've a constant camera flash
Not sure whether it works as advertised, I've not used this ROM yet.
Click to expand...
Click to collapse
It works
Anyway, it seems i've stopped deep sleep reboot, with external SD inserted, in this way:
-put all media files on internal SD;
-deleted all files created by any app on the external SD;
-set internal storage as main one for all the apps data (downloads, photo, rec, backups, etc.).
Hope this can help you in some way
Sent from my beloved Atrix

Android03 said:
Turning off any screen unlocker does not fix the deep sleep bug. 1 reboot. Overall, it is very good.
Click to expand...
Click to collapse
Really this fixes the deep sleep bug? Have you made tests for a long time of usual use? Pls confirm.
Can anyone else confirm this fix again?

First of all, thanks for the report.
Regarding the FP reader - what's really working and what isn't? Could someone enlighten me there?

As I'm back to cm7 right now, I would like that if you find any bug/fix, PM me. I will put it on the OP in the dev section.
Oh, btw, the flash workaround was my idea

I heard removing the SD card fixes the reboots.
Sounds like this might be similar to what pont 91 talking about.

Is there any fix for the upside down front camera in "somebody's" cm10?
Sent from my MB860 using xda app-developers app

Not sure if this is a bug with the roms (Somebody's 10/19), but I'm not longer able to track total data usage on my phone. Some apps will show the amount used by individual apps, but none will actually total it up (They all say 0 total data usage).

Woah where you getting October 22 from???

Fixed
flusshd said:
Really this fixes the deep sleep bug? Have you made tests for a long time of usual use? Pls confirm.
Can anyone else confirm this fix again?
Click to expand...
Click to collapse
deep sleep fixed;
Fixed blackscreen issue after a lock/unlock
Fixed black incoming call screen and fixed blackscreen issue after a call
mediafire . com / ?p3cl9j16v828i6y
cm-10-20121023-UNOFFICIAL-olympus.zip

israelborges said:
deep sleep fixed;
Fixed blackscreen issue after a lock/unlock
Fixed black incoming call screen and fixed blackscreen issue after a call
mediafire . com / ?p3cl9j16v828i6y
cm-10-20121023-UNOFFICIAL-olympus.zip
Click to expand...
Click to collapse
So, no more random reboots?

quetzalcoatl2435 said:
So, no more random reboots?
Click to expand...
Click to collapse
Where is that link coming from?
Sent from my iPad using Tapatalk HD

Antieco said:
Where is that link coming from?
Sent from my iPad using Tapatalk HD
Click to expand...
Click to collapse
from here
http://forum.xda-developers.com/showthread.php?t=1934662

quetzalcoatl2435 said:
So, no more random reboots?
Click to expand...
Click to collapse
I'm trying it right now. I'll let you know

Antieco said:
Where is that link coming from?
Sent from my iPad using Tapatalk HD
Click to expand...
Click to collapse
israelborges pm'ed the link to me. He also pm'ed ticiano_arraes (and maybe more people), it seems.

quetzalcoatl2435 said:
israelborges pm'ed the link to me. He also pm'ed ticiano_arraes (and maybe more people), it seems.
Click to expand...
Click to collapse
Have you tried it? Can't stand black screen after call!!!
Sent from my iPad using Tapatalk HD

quetzalcoatl2435 said:
israelborges pm'ed the link to me. He also pm'ed ticiano_arraes (and maybe more people), it seems.
Click to expand...
Click to collapse
Yes, but it's not the first time he did this