Related
Hello,
I'm a new member and since I do not currently have 10 posts yet, I cannot post in the Android Dev Forum. stupid rule IMO. So I am creating a new topic to make the bugs I have found known since I have not seen anyone talk about them in the dev forum.
*MODS* If you could move this topic into the dev forum that would be great!
Nexus S running Cm7 Rc1 with Netarchy 1.2.1 kernel. Great work guys!
Bugs:
1. When taking pictures in a dark room, the flash is not timed correctly. The flash lights up then turns off before the picture is captured. ( this happens about every other picture I take)
2. Lots of random reboots when doing cpu dependent tasks.
3. When saving pictures from MMS, pictures do not copy to SD. I've tried rebooting and re saving the photo's.
4. Apps freeze up and FC when started. It seems to be a different app every time I reboot the phone and it doesn't always happen.
5. Wifi is semi-broken. Sometimes it works fine, other times it will try to connect but fail. Under wifi it says connecting like its going to work but then just says disconnected.
I will post more bugs as I find them. Others are welcome to post bugs as well and I will update the list of bugs in my original post.
Thanks for all the hard work with the ROM and Kernel development!
Just a question, did you do a complete wipe before installing the rom?
Running the ROM with same Kernal for 24 hours and not had a single reboot or force close.
WiFi also working fine.
Haven't tested for the other bugs .
I haven't had a random reboot, frozen app or broken wifi yet but I do have the flash timing issue.
I had a baseband crash 2 hours after I installed CM7. Back on stock for now
Sent from my Nexus S using Tapatalk
Mshanahan said:
Hello,
I'm a new member and since I do not currently have 10 posts yet, I cannot post in the Android Dev Forum. stupid rule IMO. So I am creating a new topic to make the bugs I have found known since I have not seen anyone talk about them in the dev forum.
*MODS* If you could move this topic into the dev forum that would be great!
Nexus S running Cm7 Rc1 with Netarchy 1.2.1 kernel. Great work guys!
Bugs:
1. When taking pictures in a dark room, the flash is not timed correctly. The flash lights up then turns off before the picture is captured. ( this happens about every other picture I take)
2. Lots of random reboots when doing cpu dependent tasks.
3. When saving pictures from MMS, pictures do not copy to SD. I've tried rebooting and re saving the photo's.
4. Apps freeze up and FC when started. It seems to be a different app every time I reboot the phone and it doesn't always happen.
5. Wifi is semi-broken. Sometimes it works fine, other times it will try to connect but fail. Under wifi it says connecting like its going to work but then just says disconnected.
I will post more bugs as I find them. Others are welcome to post bugs as well and I will update the list of bugs in my original post.
Thanks for all the hard work with the ROM and Kernel development!
Click to expand...
Click to collapse
1. works properly over here. when taking a pic with flash, there is a preflash first, then it focuses, flashes again and takes a pic.
2. whats your phone clocked to(setcpu)? is it overclocked? maybe your phone cant handle the overclock?
3. long press, press save attachment worked for me.
4. no problem like that
5. wifi works here. on the latest cm7 nightly with netarchys 1.2.4
Been running RC1 since it came out and haven't had but one random reboot. Wifi works perfectly, cell and data radios work perfectly, battery life is great, theme looks great, loving it. Seems like you're in the minority here lol
I haven't really experienced any of those problems actually.
Faced none of your issues although for me, if i get a random reboot due to overclocking my limit, my android.phone performs a force closed and i'm not able to have any cell signal until i do a wipe and to restore everything from my titanium backup.
Doing a nandroid restore doesn't help as well. Strange indeed.
you are running a outdated version of the kernel (1.2.1) 1.2.2 is the new stable version, and 1.2.4 is the latest beta. It could conflict with a newer version of CM7 (speculating).
Try wiping factory settings, cache and dalvik. Then reflash CM7 + gapps.
Not facing any of these problems, and this post wouldn't go into the dev forums at all.
i found a HUGE bug in cyanogenmod7 effecting all phone models. this might make ppl rethink using CM7. the info is posted here http://goo.gl/AZDtZ
I did a full data wipe and wipe Dalvik cache and almost all issues have been taken care of.
I still get lots of random reboots tho, I have switched to a stock kernel to rule out the OC.
Thanks for all the input
what exactly is the point of using CM7?
bcl0328 said:
what exactly is the point of using CM7?
Click to expand...
Click to collapse
More customization, better performance, deodexed rom for theming, larger developer base, better features (power controls in the dropdown, more options for lockscreen...), support for Bluetooth input devices like the wiimote...do I need to keep going?
Sent from my MattedBlues CM7 Google Nexus S!
When I have rooted my phone and then booted into stock ROM I have faced with nonworking wifi and camera. Then I have installed CM7, and problems with wifi and camera fixed.
Sent from my Nexus S
Everytime you change a theme using theme manager it changes all your ringtones to default ones.
bcl0328 said:
what exactly is the point of using CM7?
Click to expand...
Click to collapse
1. Custom Lock Screens
2. Edit Auto Light settings ( when system is set to Auto Brightness )
3. Enable Quiet hours so your phone will never ring out loud between set hours e.g 11pm - 6am
4. Music Control from lockscreen
5. Notifications area Power controls e.g WIFI / GPRS / SOUND
6. Faster Phone Speed in general
7. Sound Tweeks ( Boost Notifications / Ringtone / Speaker Phone )
8. Ability to use Voodoo sound and EXT4 hacks ( with custom kernals )
9. Better Battery Life ( further improved by lowering Light settings and disabling V/A settings )
10. Haptic feedback improvments
11. long press buttons settings ( I.E long press home and launch an app e.c.t )
12. Rom manager allows you to back up your whole system and Titanium backup allows you to back up all your apps and system data.
My G Sensor has always been screwy and used to be able to at least get it working moderately well in most applications other than Skymap. However the calibration is messed up again and the old method of using a terminal emulator to do
su
/system/bin/sensorcalibrutil_yamaha
isn't working as it is no longer there since I upgraded to the leaked Gingerbread (EF02) build. The config file that used to be located at /data/system/ms3c_yamaha.cfg also doesn't appear to be there anymore.
Any idea what happened to these and how to try to fix the sensors now? The sensor calibration from the settings menu doesn't fix the calibration for me at all.
Put the phone face down during calibration from the settings menu.
Or flash the ef02 plus kernel from the dev forum.... it accidently fixed my rotation lag
063_XOBX said:
Put the phone face down during calibration from the settings menu.
Click to expand...
Click to collapse
I've tried that but it doesn't fix anything. Only way I've fixed this in the past was to remove the .cfg file and run the calibration which created a new one with good values. All was good with that method until a firmware update but I was able to fix it again with the same method. However now with the Gingerbread update I can't use those methods anymore it seems.
Perhaps I'll try the EF02 Plus rom tomorrow but I'm at work with no ODIN ability right now. However this isn't really rotation lag, this is sensors are really off... every bubble level app I try won't level. Sensor readout always shows the up/down pitch between 150 to 175 degrees, never goes to 0 or anything outside those values no matter how I calibrate it.
D`Nyed said:
I've tried that but it doesn't fix anything. Only way I've fixed this in the past was to remove the .cfg file and run the calibration which created a new one with good values. All was good with that method until a firmware update but I was able to fix it again with the same method. However now with the Gingerbread update I can't use those methods anymore it seems.
Perhaps I'll try the EF02 Plus rom tomorrow but I'm at work with no ODIN ability right now. However this isn't really rotation lag, this is sensors are really off... every bubble level app I try won't level. Sensor readout always shows the up/down pitch between 150 to 175 degrees, never goes to 0 or anything outside those values no matter how I calibrate it.
Click to expand...
Click to collapse
No no no.... its a kernel named ef02 plus..... you can flash it right through clockworkmod....
Ahhh had just seen the rom when I looked earlier. Trying the kernal but no luck on any improvement with the sensor. Doh
Sent from my SPH-D700 using XDA Premium App
I found that flashing the Alpha EE03 rEVOlution Remix Theme fixed my screen orientation lag... Plus it's an awesome theme, so far.
Works fine with EF02, the only thing that really doesn't work is the glass lock screen. Other than that, it's all good.
wipe cache X3
wipe dalvik X3
FLASH
Alpha EE03 Revo Update: http://www.mediafire.com/?gd2yyth751cs5b8
hoffman1984 said:
I found that flashing the Alpha EE03 rEVOlution Remix Theme fixed my screen orientation lag... Plus it's an awesome theme, so far.
Works fine with EF02, the only thing that really doesn't work is the glass lock screen. Other than that, it's all good.
wipe cache X3
wipe dalvik X3
FLASH
Alpha EE03 Revo Update: http://www.mediafire.com/?gd2yyth751cs5b8
Click to expand...
Click to collapse
This worked for me when nothing else did. Thanks a lot, only thing that was giving me problems.
Sent from my SPH-D700 using XDA App
crcsboy said:
This worked for me when nothing else did. Thanks a lot, only thing that was giving me problems.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Don't forget to hit thanks
And the Theme is nice too, ya?
I have a serious problem.
I have HTC Evo 4G, My screen is getting dim (NOT BLANK), I cant see screen in bright sun, It's really dark.
But this happen only Sense based ROMs, but this doesn't happen with Cyanogen or MIUI.
I have tried many sense-based ROMS ( Infected, Runny, MikG, ICS,...etc).
With every Rom, I flashed it many times, sometimes with wipe everything. I though it's hardware problem why this doesn't happen with ASOP ROM. (I don't like Cyanogen, or MIUI... LOL), Also, I tried every setting related to brightness But the problem still.
I've read every thread, article about similar problem, but useless.
For additional info about my problem: after starting up my phone, Every thing is OK, but after screen off for first time the screen getting so dark.
(Only one workaround I found, Just set "Screen always on") I'm going to kill my Evo.
Please Help me, I'm getting Crazy.
Okay this may be a dumb question, but are you sure that you don't have it set for "automatic" brightness?
JB
Sent from my CIUI using xda premium
Yes I'm sure the automatic brightness is off.
and the brightness is so high.
What kernel are you using with the sense ROMs? Have you restored any apps after flashing the ROMs? Sounds like either an incompatible kernel, or a restored app limiting brightness to save battery, although it could be hardware related(LCD or a sensor) but since you said AOSP works fine it sounds like a software issue over a hardware issue.
-EViL-KoNCEPTz- said:
What kernel are you using with the sense ROMs? Have you restored any apps after flashing the ROMs? Sounds like either an incompatible kernel, or a restored app limiting brightness to save battery, although it could be hardware related(LCD or a sensor) but since you said AOSP works fine it sounds like a software issue over a hardware issue.
Click to expand...
Click to collapse
Currently I'm using : RCMix3D Runny
Android Version: 2.3.5
HTC Sense version: 3.5
Kernal Version: [email protected]
and I didn't Restore any apps after flashing the ROMs, and also I didn't change the kernal of Sense ROMs.(I did this one time with Cyanogen).
Hmmm do you have anything installed to save battery like juice defender or any similar apps?
-EViL-KoNCEPTz- said:
Hmmm do you have anything installed to save battery like juice defender or any similar apps?
Click to expand...
Click to collapse
no I don't
I'm not sure what else it could be you could try changing the kernel to another gingersense kernel and see if that helps search "goldenmonkey 1.1 evo4g" without the " and try that kernel and see if it changes anything
thank you. I'll try that kernal, I'll inform you the progress.
I'm not sure it will help but your downloads may have had a bad kernel or been slightly corrupt so flashing a fresh kernel may help out but it may not more than likely it wont but its the simplest fix you can try make sure to check the md5 sum on the download to verify your download is intact if you do it from your phone es fileexplorer has and option when you longpress the zip and select properties to calculate the md5 and then save it to a txt file, the txt will save in the same location as the zip
-EViL-KoNCEPTz- said:
I'm not sure it will help but your downloads may have had a bad kernel or been slightly corrupt so flashing a fresh kernel may help out but it may not more than likely it wont but its the simplest fix you can try make sure to check the md5 sum on the download to verify your download is intact if you do it from your phone es fileexplorer has and option when you longpress the zip and select properties to calculate the md5 and then save it to a txt file, the txt will save in the same location as the zip
Click to expand...
Click to collapse
I flashed that kernal but nothing happen. The problem still.
Have you possibly tried installing a stock rom for the phone? see if the problem still persists once you are on a stock rooted rom...at that point you can see if it is your brightness sensor/hw issue or user/rom error.
I've heard of this before. Im gonna say its a hardware issue.
Just for curiosity's sake, what happens when you adjust the screen brightness slider? Does it get even dimmer if you slide it to a lower setting, or is the dimness consistent regardless of where you have the brightness slider?
jesuspgt said:
Just for curiosity's sake, what happens when you adjust the screen brightness slider? Does it get even dimmer if you slide it to a lower setting, or is the dimness consistent regardless of where you have the brightness slider?
Click to expand...
Click to collapse
The dimness consistent, I mean it seem that brightness doesn't effect, and there is no change whether brightness 0% or 100%.
With a stock RUU, and still having brightness issues.. time to replace the cell. I have had this problem only one where screen filter app somehow got re-installed and enabled but other than that..replace your unit.
The only thing is it works on aosp but not sense if it was hardware failure it wouldn't work regardless
You mentioned that you SOMETIMES wipe everything when flashing new ROMS. I would definitely wipe everything clean every time when flashing a ROM to positively rule out that you don't have any left over garbage from a previous ROM. Just my two cents.
I'd say try wiping everything including your SD card do a fresh format and repartition the SD.
X2 on the wipe everything. Do NOT install any kernels when u flash the ROM. See if it works first, if it does then do a FULL nandroid, then flash a kernel.
Sent from my PC36100 using Tapatalk
Hello,
I just updatet to the newest CM RC2 and got a problem with the display timeout. After some seconds the display gets darker but it does not turn off. It just keeps dark to save energy or whatever but thats it.
I didnt set anything in the display settings so I dont get why this happens
Also it happens sometimes when I turn it off via the power button, I can't turn it back on via the power button, only after a few tries or only after trying the touch thing.
Is it plugged into your power adapter or PC at this time? What is your display off time at?
No it isnt. And its set to 30 seconds.
But now it seems to work more or less. But the other problem still exists with turning it back on again now -_- I have to press the power button several times to get it on again.
Som3guy said:
No it isnt. And its set to 30 seconds.
But now it seems to work more or less. But the other problem still exists with turning it back on again now -_- I have to press the power button several times to get it on again.
Click to expand...
Click to collapse
Do you have the box in developers area about not turning off if charging?
Its not checked
You mean the latest port of CM9 that someone just happened to call "Cyanogenmod9 Unofficial" by jerl.
It would seem that since he migrated it to the 3.0 kernel, that it's getting a lot of the jellybean related issues.
I'd probably recommend switching to an ICS release that's not using the 3.0 kernel until it's a bit more stable. Or see if that Rc2 can be flashed without the 3.0 kernel.
Yea I tried the CM9 RC2 version with the 3.x kernel. I'll try the non 3.0 version then I'll see
Som3guy said:
Yea I tried the CM9 RC2 version with the 3.x kernel. I'll try the non 3.0 version then I'll see
Click to expand...
Click to collapse
I'd recommend RC1 over RC2 personally, I've been having quite the amount of bugs even with it being an RC release. The 3.x kernel release only brought upon more bugs than ever from what I've heard.
Edit: If not the display timeout issue, you'll most likely come across another no matter which you switch to at the moment (text corruption, phone delay, etc.)
So far RC2 works ok but I just got started. Will take a look at RC1 if something happens again
I've had this issue with lag on the Nexus 4 lockscreen for quite a while.
The problem is that occasionally when I go to the unlock the phone, I press the lock, but the lock will freeze. Sometimes I have to turn the screen off, and turn back on a couple of times before I can unlock the phone.
I've had this issue running CM10.1 and stock rooted android 4.2.2. I've tried doing a complete wipe and re-flashing everything.
Has anyone else had this issue? I've asked a couple of people I know who have Nexus 4's and none of them have had this problem.
Did I do something wrong, is this a common issue, or this an issue with my phone?
nmunro said:
I've had this issue with lag on the Nexus 4 lockscreen for quite a while.
The problem is that occasionally when I go to the unlock the phone, I press the lock, but the lock will freeze. Sometimes I have to turn the screen off, and turn back on a couple of times before I can unlock the phone.
I've had this issue running CM10.1 and stock rooted android 4.2.2. I've tried doing a complete wipe and re-flashing everything.
Has anyone else had this issue? I've asked a couple of people I know who have Nexus 4's and none of them have had this problem.
Did I do something wrong, is this a common issue, or this an issue with my phone?
Click to expand...
Click to collapse
I also get this occasionally from time to time. I honestly have no clue what it could be, since the screen is completely dry as are my fingers when it happens. Its a minor bug so it doesn't bother me that much
brandonc0526 said:
I also get this occasionally from time to time. I honestly have no clue what it could be, since the screen is completely dry as are my fingers when it happens. Its a minor bug so it doesn't bother me that much
Click to expand...
Click to collapse
I also sometimes get lag when I do manage to unlock, scrolling through my screens is very laggy for 5-10 seconds, then it is usually fine.
I have a problem with lockscreen lag on a phone with a quadcore CPU and 2 GB of RAM.
Flash a custom kernel. You'll be less likely to experience lag
Don't get any lockscreen lag on my stock Android.
sigma392 said:
Flash a custom kernel. You'll be less likely to experience lag
Click to expand...
Click to collapse
Have any recommendations?
nmunro said:
Have any recommendations?
Click to expand...
Click to collapse
The latest trinity kernel (125) has perfected the lockscreen lag, It definitely unlocks instantly for me.
username8611 said:
The latest trinity kernel (125) has perfected the lockscreen lag, It definitely unlocks instantly for me.
Click to expand...
Click to collapse
Trying this out now. I especially liked how it told me my system was corrupted once it finished flashing...
First thing I've noticed is that the colour is a lot different. Do I need to play with any settings, or do I only need to have the kernel installed?
Also how often do updates come out?
Messing with the settings is totally up to you. It works great "right out of the box." I don't like the stock color settings, I use trickster mod to change them to rgb 255, 255, 255 and everything else at 0 except saturation and blacks all the way up. This kernel is underclocked to 1026mhz by default, I set it to stock clock speeds. It's also undervolted by default so if you are having stability problems, try bumping up the voltage on all steps by 25mv. Updates come out pretty often, prolly a few times a month.
username8611 said:
Messing with the settings is totally up to you. It works great "right out of the box." I don't like the stock color settings, I use trickster mod to change them to rgb 255, 255, 255 and everything else at 0 except saturation and blacks all the way up. This kernel is underclocked to 1026mhz by default, I set it to stock clock speeds. It's also undervolted by default so if you are having stability problems, try bumping up the voltage on all steps by 25mv. Updates come out pretty often, prolly a few times a month.
Click to expand...
Click to collapse
The colours bothered me so I'm trying the latest franco nightly. It seems to be at the stock clock speed, no weird colours, and it makes the haptic feedback when unlocking feel more like the GNex.
I'm still having this issue with franco kernel. I've been looking around a bit and people seem to say this is related to auto brightness. I'm going to turn auto brightness off for a bit and see if it still happens.
Also, does anyone know if using a 3rd party app for auto brightness would make any difference?
Okay, turns out auto brightness wasn't the issue. Still getting lockscreen lag. Help please.
If I put 5 fingers on the screen (when the screen is off), then press the lock button, when the screen comes on it will be completely unresponsive, some of the time. I'm not always able to replicate this.
for me, some releases of Franco have lockscreen lag, some don`t, try flashing the M2 or other post r121 builds, they are all great performers and maybe you`ll get lucky with one.
if ur using paranoid android, then its a stability issue i guesa cause the same thing used to happen with me...... or else try franco kernel... or update franco kernel if ur using franco, cause an older version had the lockscreen bug, which is now fixed!!!
sigma392 said:
Flash a custom kernel. You'll be less likely to experience lag
Click to expand...
Click to collapse
Flash a stock kernel. You'll be less likely to experience lag
I'm running CM 10.1 and the latest version of franco's kernel.
I've tried using a rooted stock and I had the same issue with lag.
I'm going to try franco's milestone build, see if I still get issues.
Would increasing the minimum clock likely help at all?
I had this problem no matter what custom ROM or kernel I would use I would get this problem I got a replacement phone and don't have this issue anymore
Sent from my Nexus 4
Good Guy Mark said:
I had this problem no matter what custom ROM or kernel I would use I would get this problem I got a replacement phone and don't have this issue anymore
Sent from my Nexus 4
Click to expand...
Click to collapse
I'm thinking this may have been the issue.
How does the replacement process work?
If I save a nandroid backup of my phone, can I just unlock it and restore from there?
Flash the reset kernel from _motley 's kernel thread, it replaces a lot of files that might of got changed via various other kernel flashes with stock ones.
the one that causes a lot of lock screen lag is the /system/lib/hw/power.msm8960.so file
N4_422_stock_kernel_and_components.zip
meangreenie said:
Flash the reset kernel from _motley 's kernel thread, it replaces a lot of files that might of got changed via various other kernel flashes with stock ones.
the one that causes a lot of lock screen lag is the /system/lib/hw/power.msm8960.so file
N4_422_stock_kernel_and_components.zip
Click to expand...
Click to collapse
Can I just flash this with CWM? And then flash back to franco m2?
I actually just got an RMA for my phone, because of this issue and that the back glass panel is a little loose and makes creaking noises. When I send the phone back to google, if I follow all the steps here and lock the bootloader, it should be fine to send back to them?
Google's RMA process was amazing. Took me all of 10 minutes. They're shipping a new one in 3-5 days, and they pay for the return shipping of my old device. The replacement is brand-new, not a refurbished device. My dad's iPhone 4S had a bunch of issues and he would have to book an appointment at the Apple store, which happens to be an hour away, and they would only replace his device with a refurbished one.