24 replies to this topic

[MJScore]

Nice to have cyanogenmod on the 3d. Running great with a couple of bugs. one is the battery does not read well and i got an FC when accessing cyanogenmod setting/performance/cpu settings. Other than that it's been running very fast and stable. Is there a way to install the watch program?

[nfollin]

If I had to bet, it would be because it the stock HTC kernel with AOSP additions that's the problem with the cpu settings. I don't think its overclock right now. Could be/probably am wrong.

[wwjoshdew]

Not having any luck with the batter. it just turned off and wouldn't come back on. Plug it in, wait a few minutes, then it turns on but immediately shows green. Workaround, turn the phone off, then charge... It has been red the last 35 minutes, so I assume it's charging. Is it still charging when booting into system, and phone light is green?

[thewizord]

I don't know if anyone else also experienced this, but if you attempt to let the current market app provided with the latest gapps, recovery of previous apps fails on "loading" screen failing to allow you to accept the terms and conditions, it seems to fail every other app-recovery. Not a big deal if you use titanium, but worth noting for those that don't.

Edited by thewizord, 12 September 2011 - 05:21 PM.

[websterzx10r1]

Hey whats up i have been following CyanogenMod for a few months now and wanna thank u guys 4 working ur magic on the EVO3D. Looking 4 ward 2 installing this by the weekend. This is my first post on this sight but am on other sights as well. Thanks again.

[Telmathus]

i seem to have a small issue, cm alpha wont flash for me. now i don't know if this is the right place to post this but im usely just a reader on forums never a poster. when i flash the alpha build i just get stuck at the htc screen and that's it. i thought i had gotten a bad download retried. no luck. i had done a full wipe, cache, data, system, dalvik cache, but i think it may have to do with the clockworkmod im using to flash. im using revolutionary cwm v 4.0.1.4. now i have tried to flash a higher build of clockwork but then i just get the htc screen,then a black screen then it loads to my old Rom (when just trying to upgrade my recovery) i have tried to use rom manager but i get the same result. htc screen, black screen, boot.. is it because i have unlocked my evo 3d the official way through the Dev sight that might not be allowing me to flash certen types of recovery's? any help or point in the right direction would be greatly appreciated!

[GhostSonic]

I've been experiencing a bug with the touch screen that I've never seen mentioned anywhere else. I've only ever used CM7 through Boot Manager but I doubt it's an issue with BM, as no other rom I've tried has had this happen. I'm not sure how to describe it exactly, other than that the multi touch is pretty wonky.
When I try using touch test, I hold my finger on one place, then press down on another place on the screen, the marker for my first finger will jump to the one I just pressed down with. The issue is pretty clear with emulators, where they're pretty much unplayable thanks to this. Has anyone else had this sort of issue?

Telmathus, on 13 September 2011 - 01:07 AM, said:

i seem to have a small issue, cm alpha wont flash for me. now i don't know if this is the right place to post this but im usely just a reader on forums never a poster. when i flash the alpha build i just get stuck at the htc screen and that's it. i thought i had gotten a bad download retried. no luck. i had done a full wipe, cache, data, system, dalvik cache, but i think it may have to do with the clockworkmod im using to flash. im using revolutionary cwm v 4.0.1.4. now i have tried to flash a higher build of clockwork but then i just get the htc screen,then a black screen then it loads to my old Rom (when just trying to upgrade my recovery) i have tried to use rom manager but i get the same result. htc screen, black screen, boot.. is it because i have unlocked my evo 3d the official way through the Dev sight that might not be allowing me to flash certen types of recovery's? any help or point in the right direction would be greatly appreciated!

This IS because you unlocked through the official method, which does not give full access to the NAND through recovery.  http://forum.xda-dev...811&postcount=2 Try flashing by doing this and see if it works.

[Telmathus]

thank you for your quick reply! so once again i have been to put it nicely "tricked" by htc. >.< i will give this a shot and see if it works! thank you again!

[Telmathus]

GhostSonic, on 13 September 2011 - 01:37 AM, said:

I've been experiencing a bug with the touch screen that I've never seen mentioned anywhere else. I've only ever used CM7 through Boot Manager but I doubt it's an issue with BM, as no other rom I've tried has had this happen. I'm not sure how to describe it exactly, other than that the multi touch is pretty wonky.
When I try using touch test, I hold my finger on one place, then press down on another place on the screen, the marker for my first finger will jump to the one I just pressed down with. The issue is pretty clear with emulators, where they're pretty much unplayable thanks to this. Has anyone else had this sort of issue?


This IS because you unlocked through the official method, which does not give full access to the NAND through recovery.  http://forum.xda-dev...811&postcount=2 Try flashing by doing this and see if it works.

Ok so i tried that, and had no success BUT it did bring me around to a link with someone with the same issue and used twrp-1.0.3-modified to allow them to install cyanogenmod. i flashed twrp, and it worked! so if you need twrp cause you did official unlock here is a link. (i don't know if its ok to post this link, so if its not let me know?) http://forum.xda-dev...p?p=17418438  i really like this cyangenomod never got to use it before, till now, and i absolutely LOVE it! Great work guys!

^"have fun and happy flashing^"

[jahro]

First the goodness; the alpha build is super small,lot of freed memory,super fast on quadrant tests,keyboard looks funny but I love it (cause I have footballers hands) it will most likely be the best aosp ROM when its finished.
Bugs; heavy overheating when in use,battery don't read correctly,Wimax don't work ,had a bit of a problem loading apps from market (weird message saying not enough room on system to install) but a quick normal reboot fixed that .linkpak test seemed to be inaccurate (dont know maybe a problem with the kernal)g-talk not updated and what ever else I forgot to mention. Mind you I only used it for a few hours while at work so I didn't get to really dig into it.but i still got that awesome cm7 feel from it keep up the hard work folks will send something small your way next pay period

[CiDhed]

Didn't see this in the alpha post.

Quote

KNOWN ISSUES:
- bluetooth borked for now
- nextflix has a security issue
- wimax broken for now
- keyboard all massive. i use Gingerbread keyboard from the market
- taking 3d images and video not working
- 3d pictures (mpo, jps, ect) do not display in 3d
- FFC takes pics upside down
- battery gauge wonky

It still charges even if the green light is on. It also gets pretty awesome battery life. Here is my post about yesterday's use.

Quote

I took my phone off the charger yesterday morning at 5am, gave it a 45 minute charge on my drive home around 4:30pm and put it on the charger at 11pm for bed. I played quite a bit of drag racing and messed with the phone a pretty good amount. I know it isn't exact but it seems to be getting decent battery life at least.

[jahro]

Any1 try the alpha 2 yet.

Any1 try the alpha 2 yet.

[kneeldug]

Ghostsonic...regarding the multi touch issue:
Still no resolution though!
http://forum.xda-dev...=1267124&page=3
http://forum.xda-dev...d.php?t=1302001

[adventureoflink]

Just here to confirm that the battery is working, for the most part...

however, I go and recharge the battery, it green lighted at 91%, when I'm using to it going close to if not EXACTLY at 100% on green. so thinking "meh prolly my battery going bad already?", I discharge it a little bit. I recharge it, and this time it green lights at 90%. For S&G's, I just let it go and was going to revert back to stock to see if it was reporting 100% there, but I got sidetracked with some Angry Birds. At the end of my session there, I check the battery again and it's at 98%.

WTF? Oh yeah, and for whatever reason when I was running nes.emu and IIRC gbc.emu as well, the battery only recharges little if not none at all; is this normal even with the stock ROM?

Awesome job with this alpha/beta thing all the same, even if a few features are missing (but never fear, that's what nandroid backups of the stock firmware and titanium backup are for )

EDIT: Now my battery is at 99%... weird

Edited by adventureoflink, 24 October 2011 - 01:08 AM.

[kkrrp]

There is a horrible bug with the wifi/3g/4g signal being really low.  At my girlfriends house i used to always get almost full bars 4g signal, now 4g doesnt even connect there... in fact i only remember connecting 4g once since i put cyanogen on.  and the 3g is way lower also. i rarly ever have full bars now... I REALLY hope they fix this bug soon! i cant wait for an update also they need Cyanogen to support the 3D screen and camera.

As for the batery... Cyanogen IS better at battery life then the stock Sense(witch sucked so much it would rarely last a full day). But i think it could be way better.

Edited by kkrrp, 25 October 2011 - 04:21 AM.

[CiDhed]

kkrrp, on 25 October 2011 - 04:05 AM, said:

There is a horrible bug with the wifi/3g/4g signal being really low.  At my girlfriends house i used to always get almost full bars 4g signal, now 4g doesnt even connect there... in fact i only remember connecting 4g once since i put cyanogen on.  and the 3g is way lower also. i rarly ever have full bars now... I REALLY hope they fix this bug soon! i cant wait for an update also they need Cyanogen to support the 3D screen and camera.

As for the batery... Cyanogen IS better at battery life then the stock Sense(witch sucked so much it would rarely last a full day). But i think it could be way better.

Are you going to copypasta this into every thread?

[nfollin]

CiDhed, on 25 October 2011 - 12:40 PM, said:

Are you going to copypasta this into every thread?

I'm going to copypasta you.

@kkrrp, Does the word Alpha mean nothing to you?

[SnKy_Jay]

First off cyanogenmod 7.1 is beautiful besides the issues everyone has expressed the only major bug that i have come across is the fact I cannot receive phone calls i can receive all my text messages and emails and used titanium back up to restore my data but when people try and call me they are sent straight to voice mail. I tried to see if it is a bug where maybe all my numbers are blocked but thats not the case. Any information would be greatly appreciated to fix this issue.

Thanks in advanced,

SnKy_Jay

[gsmith462]

Anyone running alpha 3 have a problem with switching to the front camera? I don't use that camera much but when I tried earlier it just reverses everything on the main camera like a mirror image of whatever you are aiming the main camera at. I am running the tiamat e3d 1.1.0 kernel it that makes any difference.

[rstuckmaier]

adventureoflink, on 24 October 2011 - 01:02 AM, said:

Just here to confirm that the battery is working, for the most part...

however, I go and recharge the battery, it green lighted at 91%, when I'm using to it going close to if not EXACTLY at 100% on green. so thinking "meh prolly my battery going bad already?", I discharge it a little bit. I recharge it, and this time it green lights at 90%. For S&G's, I just let it go and was going to revert back to stock to see if it was reporting 100% there, but I got sidetracked with some Angry Birds. At the end of my session there, I check the battery again and it's at 98%.

WTF? Oh yeah, and for whatever reason when I was running nes.emu and IIRC gbc.emu as well, the battery only recharges little if not none at all; is this normal even with the stock ROM?

Awesome job with this alpha/beta thing all the same, even if a few features are missing (but never fear, that's what nandroid backups of the stock firmware and titanium backup are for )

EDIT: Now my battery is at 99%... weird

This is normal. There is nothing wrong with your phone or battery. Light is supposed to turn green at 90% and will continue to charge to 100%. It will take some time to get to 100% just be patient. Also, after it hits 100% it will slowly drop back to 95% and then charge back to 100% and cycle like this until unplugged. This is how the original kernel charged in the stock rom. This is totally normal.

kkrrp, on 25 October 2011 - 04:05 AM, said:

There is a horrible bug with the wifi/3g/4g signal being really low.  At my girlfriends house i used to always get almost full bars 4g signal, now 4g doesnt even connect there... in fact i only remember connecting 4g once since i put cyanogen on.  and the 3g is way lower also. i rarly ever have full bars now... I REALLY hope they fix this bug soon! i cant wait for an update also they need Cyanogen to support the 3D screen and camera.

As for the batery... Cyanogen IS better at battery life then the stock Sense(witch sucked so much it would rarely last a full day). But i think it could be way better.

Bars don't mean anything. If you have signal you are fine (for the most part). 4g is not yet supported as making a stable ROM is more important. It has been posted (at least on twitter) that 4g/3d/hdmi out are all being worked on be Shinzul. toastcfh is the main CM dev getting the ROM itself working while Shinzul is bringing the perks.

gsmith462, on 29 October 2011 - 08:06 AM, said:

Anyone running alpha 3 have a problem with switching to the front camera? I don't use that camera much but when I tried earlier it just reverses everything on the main camera like a mirror image of whatever you are aiming the main camera at. I am running the tiamat e3d 1.1.0 kernel it that makes any difference.

I am not having this problem. As with most issues like this it is HIGHLY recommended to try to duplicate issues on the stock kernel (just reflash the ROM). If the problem goes away then the issue is with tiamat (and the bug should be filed with them).