Touchscreen problem on CyanogenMod 9 by sfc3001 - Milestone 2 General

Hei!
I am new to xda forums so please don't go crazy on me if I don't do something good in explaining this.
1st of all - i had a motorola milestone 1 before with CM7.2 so i have just a bit of experience with CM ROM.
2. Now (bought a few days ago) milestone 2 with 2.2.2 android and flashed (not sure if i used the correct term) it through Motorola Software Update (via USB) to GingerBread 2.3.4 official.
3. After searching the forum i found that CM9 Nightly (by sfc3001) reached a final release being more stable than buggy for Milestone 2.
4. after rooting my device with superoneclick -> I flashed CM9 using Caesarivs tutorial: http://forum.xda-developers.com/showthread.php?t=1758271 .
5. So after installing CM9 chinese kernel (i don't know if it's a good one - i would have prefered the EU one but everyone wrote on the forums that CH is less problematic) i started using the device properly for a few days.
Problem appeared at first with the brightness (automatic) - in direct sunlight it does no go on full brightness.
But now (since yesterday) when I touch one spot of the screen it registers multiple touches on the same vertical line (clicked the Pointer Location and Show touches box in the settings->developer options menu to see what is wrong with the screen).
Another problem with the touchscreen is that when I am scrolling (going up and down with the finger on the screen) it registers multiple touches also instead of just seeing one touch going up and down (sometimes opening apps without me wanting it)
I have to say that I used the stock android for 2 days and did not have these problems.
Could someone please help me? Maybe I followed the wrong steps in installing.
Thank you.
P.S. - I already did a factory reset once and reinstalled CM9 Chinese again - but after a few hours the problem starts.
P.S. 2 - My Milestone 2 is overclocked to 1220 mhz (58vsel) from bootmenu.
L.E. another problem with scrolling is that is a bit slower than it was on GingerBread. And sometimes when i try to scroll left/right it scrolls till half of the page and then goes on the opposite page (e.g. 1 - 2 - 3 > i try to go from homescreen 2 to homescreen 3 - goes halfway to homescreen 3 and then bounces to homescreen 1 when i take my finger from the screen) - this happens also when I try to scroll in different apps up/down.

pnkye said:
Hei!
I am new to xda forums so please don't go crazy on me if I don't do something good in explaining this.
1st of all - i had a motorola milestone 1 before with CM7.2 so i have just a bit of experience with CM ROM.
2. Now (bought a few days ago) milestone 2 with 2.2.2 android and flashed (not sure if i used the correct term) it through Motorola Software Update (via USB) to GingerBread 2.3.6 official.
3. After searching the forum i found that CM9 Nightly (by sfc3001) reached a final release being more stable than buggy for Milestone 2.
4. after rooting my device with superoneclick -> I flashed CM9 using Caesarivs tutorial: http://forum.xda-developers.com/showthread.php?t=1758271 .
5. So after installing CM9 chinese kernel (i don't know if it's a good one - i would have prefered the EU one but everyone wrote on the forums that CH is less problematic) i started using the device properly for a few days.
Problem appeared at first with the brightness (automatic) - in direct sunlight it does no go on full brightness.
But now (since yesterday) when I touch one spot of the screen it registers multiple touches on the same vertical line (clicked the Pointer Location and Show touches box in the settings->developer options menu to see what is wrong with the screen).
Another problem with the touchscreen is that when I am scrolling (going up and down with the finger on the screen) it registers multiple touches also instead of just seeing one touch going up and down (sometimes opening apps without me wanting it)
I have to say that I used the stock android for 2 days and did not have these problems.
Could someone please help me? Maybe I followed the wrong steps in installing.
Thank you.
P.S. - I already did a factory reset once and reinstalled CM9 Chinese again - but after a few hours the problem starts.
P.S. 2 - My Milestone 2 is overclocked to 1220 mhz (58vsel) from bootmenu.
Click to expand...
Click to collapse
Please refer to step 4 in my turorial, it says you must use EU kernel if you are on 2.3.6
4. For CM9 download latest European GB Kernel version this thread: http://forum.xda-developers.com/show....php?t=1623385 and latest ICS gapps from http://goo.im/gapps/ and put both zips on your SD Card
Click to expand...
Click to collapse
That should fix your issues

Caesarivs said:
Please refer to step 4 in my turorial, it says you must use EU kernel if you are on 2.3.6
That should fix your issues
Click to expand...
Click to collapse
OK - I will try that right now and come back with some news later, thank you very much!

pnkye said:
OK - I will try that right now and come back with some news later, thank you very much!
Click to expand...
Click to collapse
CH kernel is for Froyo... use EU Kernel for GB

Caesarivs said:
CH kernel is for Froyo... use EU Kernel for GB
Click to expand...
Click to collapse
Well i did what you told me and yes everything works very good for now, except:
1. a few random restarts (and overheated upper part of the case at those times, so i taught that might have been the cpu so i increased max vsel from 56 to 58 at 1,2ghz overclock)
2. but the touchscreen still has the same problem (multiple touching) if i use my phone while plugged for charging, and the problem persists for a few minutes after i unplug it.
So what could that be?

pnkye said:
Well i did what you told me and yes everything works very good for now, except:
1. a few random restarts (and overheated upper part of the case at those times, so i taught that might have been the cpu so i increased max vsel from 56 to 58 at 1,2ghz overclock)
2. but the touchscreen still has the same problem (multiple touching) if i use my phone while plugged for charging, and the problem persists for a few minutes after i unplug it.
So what could that be?
Click to expand...
Click to collapse
That's a known bug for this phone (crazy touchscreen while plugged), it happens even with stock firmware (It happened to me before even creating an accound here )

Caesarivs said:
That's a known bug for this phone (crazy touchscreen while plugged), it happens even with stock firmware (It happened to me before even creating an accound here )
Click to expand...
Click to collapse
Oh., well thank you then for the information.
Too bad that no one can do something for the problem but I'll work something out through the bug.....

Related

[UPD][Tracking] Andriod HD2 Open Issues

Let us track the OPEN issues on Android HD2, we will only discuss problems dealing with android alone, issues arised due to radio, WinMo rom and a specific android rom should be ignored.
AFAIK we still have 3 main Problems
1. GSensor/ Touchscreen Freeze.
Related Files in Android : \system\bin\akmd,\data\misc\AK8973Prms.txt and \system\lib\hw\sensors.xxxxx.so
(xxxxx = htcleo or default or qsd8k or ace or bravo based on the build)
This issue is not noticeable unless you a play game which uses Gsensor (Eg Abduction, NFS Shift ...)
This thread has lot more details about this issue and it could be a possible solution for you (it does not work for me though)
http://forum.xda-developers.com/showthread.php?t=803242
Possible Workaround :
1. Disable Auto-Rotate screen in Settings -> Display
2. Run the following commands in Terminal
mv \system\bin\akmd \system\bin\akmd2
killall akmd
To Restore
mv \system\bin\akmd2 \system\bin\akmd
Basically you are renaming the file 'akmd' which is responsible for the sensor to work
2. Data Disconnects
Related Files : \system\lib\libhtc_ril_wrapper.so
This thread has lot more details about this issue and it could be a possible solution for you (it does not work for me though)
http://forum.xda-developers.com/showthread.php?t=794309
Possible Workaround :
1. Switch Mobile Network OFF and then ON (Add a widget [Widget -> Settings -> Mobile Network])
2. Switch Airplane Mode OFF and then ON (Add a widget [Widget -> Settings -> Airplane Mode])
[EDIT]:
Guys looks like we got a fix.. this wrapper seems to work flawlessly as of now... you can try it here...
http://forum.xda-developers.com/showthread.php?t=824413
Just download 0.3 file and replace the file at /system/lib using root explorer
3. Occasional Black SOD and Accuracy in Auto Brightness
Newest kernals seems to have this issue, where the display stays black while the keypad lights glow.
Related Files : \system\lib\hw\lights.xxxxx.so
(xxxxx = htcleo or default or qsd8k or ace or bravo based on the build)
Possible Workaround :
1. Show the Sensor of your phone to some bright light source and your display will be back
2. Disable Automatic brightness in Settings -> Display-> Brightness
I will update this thread with Solutions as and when the developers fix it.
Whatever i have written is limited to my knowledge, it could be wrong, if so please correct me, Most of the vetarans know these issues and the work arounds, i have just put everything together for the new comers and to remind the developers of the existing bugs
Mods feel free to move the thread to General if need be.
Hi depakjan, This is great, thanks for tracking these issues.
can people confirm this "occasional bsod"?
i haven't seen it since light-sensor is calibrated.
i think the bsod is fixed with 2.12 radio and above..
Actually BSOD was introduced in the new lights file... it does not occur frequently... also if you have not upgraded you wont have it obviously...
depakjan said:
Actually BSOD was introduced in the new lights file... it does not occur frequently... also if you have not upgraded you wont have it obviously...
Click to expand...
Click to collapse
Just so people don't get confused.
BSOD normally refers to the Blue Screen Of Death on boot and should be fixed in the latest kernels.
The black screen due to no back-light is an issue with the auto-brightness and, AFAIK, only happens on CM6 builds that haven't had the correct levels setup.
I could be wrong though as I personally only used it for a few days for testing purposes.
Sent from my HTC HD2
hastarin said:
Just so people don't get confused.
BSOD normally refers to the Blue Screen Of Death on boot and should be fixed in the latest kernels.
The black screen due to no back-light is an issue with the auto-brightness and, AFAIK, only happens on CM6 builds that haven't had the correct levels setup.
I could be wrong though as I personally only used it for a few days for testing purposes.
Sent from my HTC HD2
Click to expand...
Click to collapse
I second that explanation ... and the auto backlight levels in CM builds may actually work better than Desire builds if tweaked properly... atleast for me the reaction time of the sensor is much faster ... accuracy still a problem
Accuracy is still a problem, so is Black SOD .. i have been getting this in Mdeejay's Revolution, HD .. latest ones...
it so happens when you have been talking over your phone for a long time(which blocks the sensor from light).. and then when you are finished with the call it wont wake up... maybe it did not sense light ... but after you show the sensors over a bright light source.. it comes back..
i have seen couple of posts and users mentioning about this...
lets see if everyone agrees that there is no Black SOD, i will modify the post for accuracy..
Support of HTC extended battery
I have tried a few android builds, but none of them seemed to support OEM HTC 2300mAH extended battery - after android booted up in the dual boot process, the HD2 powered-off by itself. I read some posts that acknowledged the problem, but I have not come across any android build that resolved this issue... Did I miss them? Thanks.
Can we also add tracking of Idle / Screen Off Battery Drain? Target is 5-8ma, some builds run at 100ma.
Is anyone's market busted?
Most apps won't install, but some do just fine. This started last night. I tested on 4 roms now and all exhibit identical behavior. This was NEVER an issue before.
(the stupid mount/unmount trick does nothing)
However, once they've d/led I can install them manually. Except for google voice. It refuses to install LOL. Google must have screwed something big here.
badmonopoly said:
Is anyone's market busted?
Most apps won't install, but some do just fine. This started last night. I tested on 4 roms now and all exhibit identical behavior. This was NEVER an issue before.
(the stupid mount/unmount trick does nothing)
However, once they've d/led I can install them manually. Except for google voice. It refuses to install LOL. Google must have screwed something big here.
Click to expand...
Click to collapse
There has been an issue internationally with access to the market for a while now. People were able to browse the market as normal but upon trying to install anything nothing would happen. This has been mentioned on several threads over this forum already and the problem is an intermittent one (obviously based on what server you connect to when trying to download anything).
Led Notification is not functioning, especially on Sense build.
backlight drivers are not working , it don't dim light when left without use (it closes the screen ) , as well as light sensor , doesn't dimm light only brightens the screen
jcc266 said:
I have tried a few android builds, but none of them seemed to support OEM HTC 2300mAH extended battery - after android booted up in the dual boot process, the HD2 powered-off by itself. I read some posts that acknowledged the problem, but I have not come across any android build that resolved this issue... Did I miss them? Thanks.
Click to expand...
Click to collapse
Try replacing the kernel from one of the Sense builds with my Alternative kernel.
Sent from my HTC HD2
hastarin said:
Try replacing the kernel from one of the Sense builds with my Alternative kernel.
Sent from my HTC HD2
Click to expand...
Click to collapse
. . . can I just 'tip my hat' to you hastarin . . . you 'd' man
And I'm hopeful that all the devs and chefs will have these problems solved before too long.
Viv la HD2 Android!
Reno_79 said:
There has been an issue internationally with access to the market for a while now. People were able to browse the market as normal but upon trying to install anything nothing would happen. This has been mentioned on several threads over this forum already and the problem is an intermittent one (obviously based on what server you connect to when trying to download anything).
Click to expand...
Click to collapse
What doesn't make any sense is that the app successfully downloads, but either stalls when it needs to d/l or tries to install and tell me it was unsuccessful.
hastarin said:
Just so people don't get confused.
BSOD normally refers to the Blue Screen Of Death on boot and should be fixed in the latest kernels.
The black screen due to no back-light is an issue with the auto-brightness and, AFAIK, only happens on CM6 builds that haven't had the correct levels setup.
I could be wrong though as I personally only used it for a few days for testing purposes.
Sent from my HTC HD2
Click to expand...
Click to collapse
I've found the backlight problem occurs (generally) if I unlock/lock the phone fairly quickly in a short space of time (and yes, I've only seen this on Hyperdroid 1.6 & 1.7, both CM6 builds). It's not consistently reproduce-able though, I can go several days without it happening, then have it happen a couple of times in a single day.
The touch screen is still active though, and swiping the unlock brings the screen back to normal brightness levels.
Tyrion84 said:
Led Notification is not functioning, especially on Sense build.
Click to expand...
Click to collapse
Works for me..could be your build ....try some other build...
hoss_n2 said:
backlight drivers are not working , it don't dim light when left without use (it closes the screen ) , as well as light sensor , doesn't dimm light only brightens the screen
Click to expand...
Click to collapse
this is already covered in the third point as accuracy
Works for me..could be your build ....try some other build...
Click to expand...
Click to collapse
Hi!
I wonder what "works for me" means. What exactly are your leds doing? On all builds i tried so far the left green led flashed about one time a minute green and nothing happened when the phone was charging. Are there some hidden settings or a special program for hd2 leds?
Cheers,
Otto

Slider unlock sometimes doesn't work with incoming call

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?

U8800 X5- random clicks problem

U8800 X5 having random clicks once it loads completely.
like when i start the phone the phone boots up all fine
home screen all fine no flickkering no problem even i touch or click any app.
within like 2 min of phone on---------it goes crazy.
just keep clicking whatever men opens it click the center of the screen and keeps moving AUTOMATICALLY.
is this a S/w problem or a H/W?
I tried hrd reset from the recovery mode but again the same.
do i have to update the S/W ?
i also realised that when i play some videos the graphics are not clear and somtimes the video is in monchrome (Green scren) only.
Expert Guys please help.
If you on .35 then Downgrade to .32
.35 kernel has problems with atmel screens.
Sent from my Huawei Ideos X5
well itz done i read somewhere to clean up the edge gap near the lcd and tried it. working so far. i belive there was someting stuck there...... causing random clicks as the touchpas is quite sensitive......... thanks to all your suggestions appreciate your kind concern and support.
Also Thanks to entrapmen........
I'm having the same issue with my U8800...
I've had this for at least a few weeks. At first, it only happened every once in a while, but yesterday I upgraded from 2.2.1 to 2.3.5 and now this happens almost every time I unlock the phone.
What part of the phone did you clean rynaaz? I really couldn't figure it out from your description.
I'm hoping that might solve my problem as well.
Thanks.
Same problem here to! Maybe digitizer problem?
It's a kernel problem. Atmel touchscreens with .35 kernel won't work.
Sent from my Huawei Ideos X5 using xda premium
Well I had this issue after upgrading to official 2.3.5.
Yesterday after reading about these issues with with the .35 kernel on multiple forums, I downgraded to the official 2.2.2 ROM and the phone is back to normal...
Is there any custom ROM with a fixed .35 kernel?
Or is there any other ROM with Gingerbread/ICS that works properly with Atmel screens?
Thanks!
Having the same problem while charging with Blackberry's
TTGWarheart said:
It's a kernel problem. Atmel touchscreens with .35 kernel won't work.
Sent from my Huawei Ideos X5 using xda premium
Click to expand...
Click to collapse
But i have synaptics!
Well I got the same thing, but couldn't tell what kind of touchscreen I have.
Sporadic 'ghost clicks' on the x5 screen
I have the same problem as described above. Except it appears to be 'self-clicking' in only one specific part of the screen (mid right). It sometimes 'auto clicks' irregularly several times over a couple of seconds, or long clicks, then disappears for a minute, then again... Depending what the screen content is, I can see the highlighted indication of a click. It wasn't doing this before, what caused this?
I followed this advice to find my screen type:
chinaben said:
Dial * # * # 2846579 # * # *
Go to projectmenu, veneer information query, apparatus type query,
then you will see all hardware types
Click to expand...
Click to collapse
Giving me "1. Touch screen type: Synaptics RMI4"
This is so annoying. I'm about to try cleaning the screen edge with a pin or something, and if that doesn't work I'll try different roms.
Any help MUCH appreciated.

[Q] Screen Shift ICS 4.0.4-Sense 3.5-Cm Scream Rom-Miui Rom Help Me

hi my phone is just working 7.2 CM nand rom. ICS 4.0.4 - Htc Sense 3.5 - Cm scream rom - Miui Rom shift of the screen is in them. Usually red, vivid color screen is moving.Screen shift off color doesn't cause. Please help me.
Sorry for my english google translate
please help?
you should return to windows mobile first...
looks like a screen replacement that is not supported by our kernels
schlund said:
looks like a screen replacement that is not supported by our kernels
Click to expand...
Click to collapse
I had broken my screen repair.But it works cm7.2. ICS-HTC Sense-CM scream doesn't work. Why? What should I do?
please help me
what about old ROMs
mustafa3m said:
please help me
Click to expand...
Click to collapse
did try to switch back to SD card version of android or WM6.5??
do you have this problem yet?
tm.bax said:
do you have this problem yet?
Click to expand...
Click to collapse
yes, the problem continues
Hello there,
I recently changed from Schlund's Photonic SD Boot to CM 7.2 NAND Version, where I started having this strange issue. SD Boot worked just fine once I managed to get over the critical first 10 minutes after booting without freezing. Now the screen shifts occasionally, especially when I'm opening white windows or menus like the shutdown menu or the one where you enter a wlan security key. It stops in every position, just like mustafas picture shows. If I turn it around, the line dividing the screen just stays where it is, both frames will turn. I tried changing every single option related to the screen, flashing different versions, without gapps, without update, even [ROM] Phonerty MIUI v4 (ICS). The bug is a bit slower in this one, but still there. In all cases everything is the way it ought to be after tapping the standy button and waking it up again. But in most cases it will wont stay that way. I can't even flash it back to WM (and I don't really want to since I know how useful this little thing can be with Android on it), every RUU i tried to use told me I was using the wrong one. Any ideas? Anything new about this one?

Atrix 4g kitkat ROM{by Zn7mkUKzN1r8aCIV} ROM problems and fix

Atrix 4g ROM Developer Zn7mkUKzN1r8aCIV's new ROM v2 gets you Android 4.4.4 KitKat and also fixes the battery percentage problem that is affecting most Atrix 4g users. check out his Development Thread here:
http://forum.xda-developers.com/atrix-4g/development/rom-cm-11-android-4-4-4-atrix-bigpart-t2847281
However, after flashing his ROM, most of you will get a "Setup Wizard has stopped" problem. Here's the fix I found:
1)On the screen that says "Choose language:" choose your language
2)On the screen that says"Insert sim card", you will find that when you press "next" or "skip", the setup wizard will stop. At that point, swipe down the status bar.
3)Touch the date at the top left corner of the status bar
4)It will then ask you to sign in to your Google account and WiFi.
5)After you do all that, you will be taken back to the calender screen.
6)Triple click fast on the back button or home button.
7)You will be taken back to the language selection screen.
8)Choose language
9)Now you will find that when you press skip on the "Insert sim card screen, it won't force close anymore.
10)Sign in to WiFi again, and you will then successfully finish the setup and can start using your phone.
The second problem, is that your phone most likely will not detect the sim card. Here's how to fix:
1)Go to settings
2)Turn on then off the mobile network.(MUST!)
3)Power off your phone, do not take sim card out.
4)Power your phone back on.
5)Your phone should now detect the sim card.
[EDIT]:New problems and fixes:
This problem is very rare and will probably not happen to your problem at all, but just in case, here's how:
After flashing ANY new ROM, some of you will probably get a black screen instead of the boot animation. DO NOT WORRY, you're phone is NOT bricked, it's just that the boot animation will work randomly sometimes and sometimes not. Just power on your phone and wait until the navigation bar buttons at the bottom of the phone light up, then you will know that the phone has finished booting up, and then simply just press the power button to open the screen.
AGAIN, this will most likely never happen to your phone, so far, I think I was the only one experiencing this problem.
Another problem that came up: Google Now voice search in the Google now launcher doesn't work. This should fix the problem:
1)Download the Google Now lib from this link (thanks to XDA Developer Jesco): http://d-h.st/EH1
2)Go to file manager and move it into /system/libs.
3)Now the Google Now voice search should work.
Ask any questions that you have and I will be happy to help you ASAP.
HackerXmaster said:
Atrix 4g ROM Developer Zn7mkUKzN1r8aCIV's new ROM v2 gets you Android 4.4.4 KitKat and also fixes the battery percentage problem that is affecting most Atrix 4g users. check out his Development Thread here:
http://forum.xda-developers.com/atrix-4g/development/rom-cm-11-android-4-4-4-atrix-bigpart-t2847281
However, after flashing his ROM, most of you will get a "Setup Wizard has stopped" problem. Here's the fix I found:
1)On the screen that says "Choose language:" choose your language
2)On the screen that says"Insert sim card", you will find that when you press "next" or "skip", the setup wizard will stop. At that point, swipe down the status bar.
3)Touch the date at the top left corner of the status bar
4)It will then ask you to sign in to your Google account and WiFi.
5)After you do all that, you will be taken back to the calender screen.
6)Triple click fast on the back button or home button.
7)You will be taken back to the language selection screen.
8)Choose language
9)Now you will find that when you press skip on the "Insert sim card screen, it won't force close anymore.
10)Sign in to WiFi again, and you will then successfully finish the setup and can start using your phone.
The second problem, is that your phone most likely will not detect the sim card. Here's how to fix:
1)Go to settings
2)Turn on then off the mobile network.(MUST!)
3)Power off your phone, do not take sim card out.
4)Power your phone back on.
5)Your phone should now detect the sim card.
[EDIT]:New problem and fix:
This problem is very rare and will probably not happen to your problem at all, but just in case, here's how:
After flashing ANY new ROM, some of you will probably get a black screen instead of the boot animation. DO NOT WORRY, you're phone is NOT bricked, it's just that the boot animation will work randomly sometimes and sometimes not. Just power on your phone and wait until the navigation bar buttons at the bottom of the phone light up, then you will know that the phone has finished booting up, and then simply just press the power button to open the screen.
AGAIN, this will most likely never happen to your phone, so far, I think I was the only one experiencing this problem.
Ask any questions that you have and I will be happy to help you ASAP.
Click to expand...
Click to collapse
Common fixes on most, if not all, devices. Nothing new reported.
palmbeach05 said:
Common fixes on most, if not all, devices. Nothing new reported.
Click to expand...
Click to collapse
I installed the ROM as follows:
1 - I installed CWM via fastboot;
2 - I made all the necessary WIPES;
3 - I installed the ROM,
4 - I installed the BASENBAND N_01.100.00R BELL,
5 - I started the phone because the first time it started not recognizing the operator,
6 - I rebooted again and installed GAPPS, then started normally,
bugs:
1 - YouTube closes alone
2 - I had a few reboots,
3 - Battery with this little income
4 - Flash does not work automatically, you have to touch the screen to activate the focus and the flash works well,
Work:
1 - GPS is working well,
2 - Telephone network is good,
3 - Games are running normally
4 - Wifi is working,
5 - Back and front camera is working well, taking pictures with good resolution.
working youtube
lucasrafael07 said:
I installed the ROM as follows:
1 - I installed CWM via fastboot;
2 - I made all the necessary WIPES;
3 - I installed the ROM,
4 - I installed the BASENBAND N_01.100.00R BELL,
5 - I started the phone because the first time it started not recognizing the operator,
6 - I rebooted again and installed GAPPS, then started normally,
bugs:
1 - YouTube closes alone
2 - I had a few reboots,
3 - Battery with this little income
4 - Flash does not work automatically, you have to touch the screen to activate the focus and the flash works well,
Work:
1 - GPS is working well,
2 - Telephone network is good,
3 - Games are running normally
4 - Wifi is working,
5 - Back and front camera is working well, taking pictures with good resolution.
Click to expand...
Click to collapse
http://forum.xda-developers.com/show....php?t=1529715 This youtube should work, never had any problems with it
---------- Post added at 10:18 AM ---------- Previous post was at 10:14 AM ----------
http://forum.xda-developers.com/showthread.php?t=1529715 link above doesnt work, this should be good
lucasrafael07 said:
I installed the ROM as follows:
1 - I installed CWM via fastboot;
2 - I made all the necessary WIPES;
3 - I installed the ROM,
4 - I installed the BASENBAND N_01.100.00R BELL,
5 - I started the phone because the first time it started not recognizing the operator,
6 - I rebooted again and installed GAPPS, then started normally,
bugs:
1 - YouTube closes alone
2 - I had a few reboots,
3 - Battery with this little income
4 - Flash does not work automatically, you have to touch the screen to activate the focus and the flash works well,
Work:
1 - GPS is working well,
2 - Telephone network is good,
3 - Games are running normally
4 - Wifi is working,
5 - Back and front camera is working well, taking pictures with good resolution.
Click to expand...
Click to collapse
For the Camera problem: Install the Cyanogenmod CameraNext.apk
GalleryNext
CM 11 Volume Mod attached below.
Is there a fix for YouTube app crashing when you try to watch a video?
Jacte said:
Is there a fix for YouTube app crashing when you try to watch a video?
Click to expand...
Click to collapse
idk, maybe if you learned how to search for youtube within Z's CM11 thread, you might have been able to find a link on page 35. But its ok, you're just like a lot of users who don't know how to use that simple feature known as a search bar.
palmbeach05 said:
idk, maybe if you learned how to search for youtube within Z's CM11 thread, you might have been able to find a link on page 35. But its ok, you're just like a lot of users who don't know how to use that simple feature known as a search bar.
Click to expand...
Click to collapse
I'm not one of those people you described, I searched on that thread but I didn't see because I was looking for Z's posts about YouTube problem. But thank you for information.
I downloaded that link, tried to install but I can't install it, It says "App not installed". How can I fix that?
I fixed the problem by renaming YouTube.apk in system/app folder and installing the new one. But there should be another, simple solution?
PS: Another question about that YouTube situation; the link that guy posted on CM11 thread is 5.2.27th version of YouTube, and I looked at "About" section of YouTube on my phone it says I installed 5.1.1.5 which is older. Why don't our phones update YouTube to latest version? Is this about the compatibility thing? Should we always follow the updates on somewhere else?
youtube
This might give some insight. My youtube has been working however ive never installed google play services even once, there may be a chance that gapps is causing the problem but i cant say for sure
hi kitkat user
could you confirm with this rom and last kernel that fonction bellow work fine (and without hang or problem when using it) :
- call (i think yes)
- sms
- gps
- video recording
- photos
thanls
However, after flashing his ROM, most of you will get a "Setup Wizard has stopped" problem. Here's the fix I found:
Click to expand...
Click to collapse
Another option would be, press top left, top right, bottom right, bottom left.
Setup wizard will quit.
Since i installed kk ROM in my atrix i didn't have troubles with my cellphone, the only problem came when i tried to download The gapps
J.M. Schatten said:
Since i installed kk ROM in my atrix i didn't have troubles with my cellphone, the only problem came when i tried to download The gapps
Click to expand...
Click to collapse
That's not a problem or a fix about the ROM....
palmbeach05 said:
That's not a problem or a fix about the ROM....
Click to expand...
Click to collapse
Well i have not found bugs yet... But i read about a lot of people who have bugs with the camera, WiFi or baseband or Radio... Maybe i only had a bit of lucky
Hi
My phone seems to be extremely sluggish when doing common tasks like opening or closing apps, opening app drawer, etc.
Also, any games I play on my phone seem to freeze for 0.5-3 seconds on touch input.
Is this a problem with my phone, or this ROM, or all CM ROMs on Atrix?
Send SMS
Hi There,
Is it only me or anyone else got problem when sending SMS? My Atrix on Z's KK is working great except the mentioned issue. I can receive SMS properly but could not send any SMS out.
Any helps would be appreciate!!!
Thanks.
txtsd said:
Hi
My phone seems to be extremely sluggish when doing common tasks like opening or closing apps, opening app drawer, etc.
Also, any games I play on my phone seem to freeze for 0.5-3 seconds on touch input.
Is this a problem with my phone, or this ROM, or all CM ROMs on Atrix?
Click to expand...
Click to collapse
Have you tried a different CPU governor? Or have you even unlocked the performance menu? There are some tweaks that you could apply and maybe you're missing them.
[Solved]
Hey guys, first of all, thank you Z and P! my atrix is now revived and I can enjoy it once more! what a great job. So far, really stable (although the screen don't light up until de end of some calls). Battery is doing great!
After some reasearch I found out I should be using the hporch32 recovery. Turns out I also needed to flash the hporch32 boot with "fastboot flash boot boot_olympus_kitkat_bigpart_hporch32_finalv2". I know it was silly, but the guides don't really cover this situation....
Anyways, thank you very much for this gift! Hope this helps other noobs!

Categories

Resources