Jump to content

Welcome to CyanogenMod

Welcome to our forum. Like most online communities you must register to post, but don't worry this is a simple free process that requires minimal information for you to signup. Be a part of the CyanogenMod Forum by signing in or creating an account. You can even sign in with your Facebook or Twitter account.
  • Start new topics and reply to others
  • Subscribe to topics and forums to get automatic updates
  • Get your own profile and make new friends
  • Download files attached to the forum.
  • Customize your experience here
  • Share your CyanogenMod experience!
Guest Message by DevFuse
 

songohan

Member Since 13 May 2012
Offline Last Active Jan 01 2013 07:17 PM
-----

Posts I've Made

In Topic: [Cm10] Discussion Of Nightlies

01 January 2013 - 03:21 PM

What is an empty screen? From which ROM did you come from to CM10? Flash 10.1 again and see if its working.
What I do (and had no problems with 20 phones that I flashed so far) is going to this site http://forum.xda-dev...d.php?t=2036229 and downloading the ClockWorkMod Recovery(no superbrick bug) from the "Instructions" field, flash it then with ODIN and then flashing CM10.0 from internal SD card which I put in previously and then do a data/factory reset and cache reset and dalvik reset. Then (without rebooting) I flash 10.1 and gapps for 10.1 and then go to your settings, then "Apps" and search for the CLOCK App, in the clock app click "Clear Data" or something like that, That will do it.

In Topic: [Cm10] Discussion Of Nightlies

20 December 2012 - 11:09 AM

Im running:
-"cm-10-20121216-NIGHTLY-i9100.zip" from "http://get.cm/?device=i9100" with latest gapps and LQ6 modem on a Samsung i9100 (int).

So far I have had two cases of the phone asking for SIM-Code without no particular reason ( I did not restart the phone, maybe it restarted itself? I dont know )
Also I found out that if you start your camera and then quickly (after max. 1,5sec) close your camera with the "back key" your flashlight will turn on for a second.

Other than that: Phone works like a charm, battery drainage is exactly 1% per hour on standby with regular synchronizations,mail sync for 4 mailaccounts every 5 minutes and weathersync every 15 minutes on. When I use the phone (mostly whatsapp and browsing 9gag or googlenews and websites with videos and many pictures with the Dolphin Browser) I have after 15 hours (when I go to sleep) about 30% left. Once they fixed the bugs, this ROM will be perfect. It doesnt freeze and everything works smoothly, even if you work with many Apps simultanously.

Because at first I didnt know whether or not these matters were acceptable made me not wanting to change from CM9 to CM10. But now that I actually tried this ROM I can safely say, this is way more improved than CM9 and everyone should change to it, even if they are still Nightlies.

EDIT: Right after I posted this I have updated to 10.1 because I found out that development stopped for 10.0 and the team is focussing on 10.1. Short review, even if this is the wrong section, but I do this here because this way you can compare:

CM10.1 looks almost the same. Theres differences in the details though. The camerahandling has improved, now it is easier to change its settings, good work!
Only thing that bothers me right now, which hasnt been fixed since cm9 is, that if your phone is locked and you want to unlock it and press the power or home button, the phone shows still a blackscreen for about 1 second or so. After that you can unlock your phone. Also if you want to lock your phone and press the power/lock button, your phone doesnt lock instantly but needs a second or so to do so.
Other than that, pretty much same handling.

In Topic: [CM9] Instructions & Discussion of Nightlies

27 June 2012 - 12:06 AM

I installed CM9 RC1 today on my SGS2 but every single release AFTER 20120617 has this annoying "feature" that the "kill app back button" takes 2-3 seconds now to kick in!
before it took about a second! that was the whole fun of it! to kill apps very fast! but now? in the 2 seconds I can kill the app the way its supposed to be! please fix it or at least let the user decide how long it should take for it to kick in thanks!