yashsingh1/xdaforums huggingface dataset:
[Milestone 2 Android Development] blu2lz:
If you flash the new version over the old one you don't need to wipe data. Because you see the setup wizard I assume you wiped data.

Did you wipe data/cache/dalvik again?

Did you download the correct Gapps? Did you check the md5 hash?
[Milestone 2 Android Development] patrol-cz:
Just tested the BlueTooth. I'm using chan_mobile from Asterisk to call over the phone and it works as expected. Just the volume sent from the phone to the BT headset (Asterisk in my case) is a bit low and cannot be increased. The volume going in opposite direction is maybe a bit higher than necessary, but still usable.

So, thanks for repairing this!

Pavel
[Milestone 2 Android Development] lulli1:
This seems not to be a problem of only this device. There are some problems with the setup wizard in some other threads. So it might be a problem in the last cm source built.

There are two possibilities as a workaround:

1. Clean install last version

2. Go through setup wizard, log in google and s.o.

3. Dirty install CM 11 last version (as blu2lz mentioned above)

Or

You can delete SetupWizard.apk from the zipped rom file.. system/priv-app/SetupWizard.apk
[Milestone 2 Android Development] bruce7890:
Changing the governor to Performance had made a reasonable difference in the right direction. It was the best of all the other governors and the call display is activated much more quicly on an incoming call now. Maybe you'll have even more luck with something else in addition to this?
[Milestone 2 Android Development] blu2lz:
Of course it is the fastest…performance governor just let the cpu run at maximum speed all the time. If you want to use your phone more than five hours without charging you better pick another governor. :silly:
[Milestone 2 Android Development] bruce7890:
I've not found a reduction in battery life... the phone still sleeps and the cpu clocks at a lower speed when idle...
[Milestone 2 Android Development] blu2lz:
Then you did not choose performance governor. Go to "Settings>Performance>Processor" and choose performance as current governor. Then you can see that the current frequency is maxed out all the time. That's just how performance governor works, it is not android exclusive, in every computer system you can choose this governor. I'm sorry. :p
[Milestone 2 Android Development] bruce7890:
My mistake, thanks for the heads up...

---------- Post added at 12:12 PM ---------- Previous post was at 11:53 AM ----------

I've just installed BoostedAssV2 - thanks for that...
[Milestone 2 Android Development] Zinamo:
Same issue as MageMaster when coming from CM10.2, the procedure listed by lulli1 seem to solve! Thanks!
[Milestone 2 Android Development] rkrisi:
I have installed the last update, but I have to reflash some things which I installed from recovery (.zip). (Eg.: boostedASSv2 governor, Cerberus app, etc...) Is this a bug? Any other rom does not required reflashing these things after update....
[Milestone 2 Android Development] patrol-cz:
It depends on the ROM installation script. This one AFAIK reformats the /system partition, so things residing there are lost. Other ones just replace the old contents with new one, which may generally lead to problems when they are not compatible. Reformating the /system partition is cleaner and it isn't a bug.
[Milestone 2 Android Development] blu2lz:
[MENTION=4806452]czechop[/MENTION]:

Great to hear that the delay is fixed. I did not find a change in your github related to this. Did Quarx fixed it? Do you know where? I want to know the culprit. Thanks in advance for pointing me in the right direction.
[Milestone 2 Android Development] patrol-cz:
I'm also interested to know the cause. Now it behaves really differently - the standard lock screen appears almost immediately after the call comes, and a few seconds later, the dialer screen with caller data pops over it. I've done a little comparison of the zips and I've found a difference in build.prop, especially changing ro.config.low_ram=false from true, but I'm not sure, whether this change can influence the problem or whether it is just a secondary change, which doesn't have any relation to the problem.

With regards,

Pavel
[Milestone 2 Android Development] katchoo:
anybody has an idea why the autocorrect feature does not work while using the hardware keyboard?

normally i use autocorret to automatically exchange special chars (like ö, ä, ü one can just write o, a, e on software keyboard or hardware with stock rom)

Cya katchoo
[Milestone 2 Android Development] blu2lz:
First of all, I did not flash the new version because the screen delay is only one second on my phone and everything is working really well, so I'm not eager after breaking it…

I don't really see the fix then. Problem was, that the screen wakes up late resulting in not being able to answer it immediately. Now the screen wakes up immediately but you still cannot answer the call because there is the lock screen? That's not quite a step forward.

For anyone not knowing: With builds < 24.02. it is possible to press the power button and the screen will wake so you can answer the call. It just does not do it automatically. With 24.02. build I did not test it and I guess it is not working anymore because now the screen wakes but only showing lock screen so you may even turn the screen back off if you press power button.

The ro.config.low_ram option is a new feature in kitkat to ensure that ram consuming system parts are aware of the system being run on a low ram device (usually 512 MB, like the MS2). So it is feasible to set it to true on MS2. Downside is that you do not have the transparent status bar anymore for example. The builds < 24.02. are nearly lag free so I'd rather go with the transparent status bar. :p

You can change it easily via text editor or install build.prop editor from play store.
[Milestone 2 Android Development] :
Hey guys. Do I need to do full wipe or just wipe dilvik/cache after installing a new rom release ? Thanks in advance ;)
[Milestone 2 Android Development] blu2lz:
If you installed cm11 by czechop already just install without full wipe. If you use another rom and want to switch read first post under installation.
[Milestone 2 Android Development] patrol-cz:
OK, I've turned ro.config.low_ram option back to yes, and it hasn't any effect on the wake-up process during incoming calls. The lockscreen turned on almost immediately and about a second later the dialer screen appeared. I'm satisfied with it.

However, I lost the transparent status bar, exactly as you wrote. I can't find any other difference, the responses are very fast with yes as well as with no. For me, it will require further testing, which one to use.

Pavel
[Milestone 2 Android Development] PhatUgly:
Hi folks,

since a few days my milestone 2 keeps making the clicking sound that usually just occurs when you start the camera app. It occurs even when the phone is supposedly asleep. Has anybody experienced this and have a hint about how to solve this issue?
[Milestone 2 Android Development] patrol-cz:
Yes, mine now does also some sound, and I've identified it as a locking sound. I have the screen lock delayed for 10 seconds after switching the screen off, and exactly in this time the click appears. And when I lock it immediately by the power switch, it clicks immediately and not after this delay.

Regards, Pavel
[Milestone 2 Android Development] PhatUgly:
Thanks for the prompt reply Pavel! But I am sure that in my case the sound is not coming from the speaker but is the mechanical sound of the camera. It also happens sometimes while I use the phone.
[Milestone 2 Android Development] macmalon:
Then take care, big brother might be watching you !! :p
[Milestone 2 Android Development] Anonymous_:
I'm experiencing some strange shutdowns (yes, not reboots, but shutdowns) since last update. Did not experience such issue on "20.01.2014" build.

Anyone else experiencing something similar?
[Milestone 2 Android Development] Lukash_Master:
I've experienced one shutdown (while using Facebook app) and few random reboots (while using Facebook, Foursquare and WhatsApp) using 22.02 build.
[Milestone 2 Android Development] patrol-cz:
By chance, aren't you overclocking ? I've set a slight overclock (1200 MHz) on one of the devices and it started to reboot and shutdown. After setting things back it stopped again. I think that it's caused by worn-out battery, which isn't able to supply enough power (increased internal resistance), when overclocked CPU asks for it. If the battery status is even worse, it may cause this kind of problems even with standard CPU freqs.

Pavel
[Milestone 2 Android Development] divie:
I doubt that. My milestones battery is worn out to the bone, barely lasts a day, and I overclock to 1300 mhz @ 69 vsel. And it's quite stable. I had only about 3 reboots since the 3 months I'm using this rom.

Sent from my Photon Q with Tapatalk 4
[Milestone 2 Android Development] patrol-cz:
Me too. I installed this ROM in about 4 devices, three of them are perfectly running with overclock and no reboots, but one of them started to fail. I can (next week) make a test by exchanging the battery between two of them and verifying, whether the reboot/shutdown issue will move. BTW the suspected battery is so worn-out, that it's flat in about 8 hours after full recharge.

Pavel
[Milestone 2 Android Development] Anonymous_:
I'm suspecting the battery as well - because sometimes the battery is totally dead (I can't even power the phone), but when I connect it to charger, it says 60% charge... Anyway - random reboots/shutdowns are the biggest problem of the M2 IMHO... It is so bad and annoying, that I'm looking around for a new phone.
[Milestone 2 Android Development] divie:
I just received my photon q last week :)

Sent from my Photon Q with Tapatalk 4
[Milestone 2 Android Development] patrol-cz:
This is exactly what I'm talking about. The battery can't supply enough current (because of increased internal resistance) and the phone automatically shuts down and can't be started, because the undervoltage sensor triggers again and again. After connecting to a charger, the voltage increases, because the battery is now fed with a charging current, and, again due to the increased internal resistance, the voltage on it builds very quickly and the phone indicates maybe 60% of capacity. These factors prevent the battery from undergoing a full charging cycle, thus the battery is continuously degrading, until it's totally dead.

Maybe try to get a new battery instead of a new phone, if you like your MoMi2... I'm also planning to buy one somewhere, even my phone still doesn't exhibit these signs of advanced battery degradation.

Regards, Pavel
[Milestone 2 Android Development] yuriaps:
Thank you very much Fedroid!!
[Milestone 2 Android Development] Zinamo:
wow, this rom lloks very promising! anyone knows what buggy calls means?
[Milestone 2 Android Development] fanghongjian:
hi,thank you so much for this awesome work.

i just want to ask one question,

is based 2.6.32 or 3.0.8 kenerl ?
[Milestone 2 Android Development] dulocox:
I can't flash the rom, I keep getting the same error:

Starting Installation...

set_metadata_recursive: some changes failed

E:Error executing updater binary in zip '/sdcard/(...zip path)'

Error flashing zip '/sdcard/(...zip path)'

Updating partition details...

:confused:
[Milestone 2 Android Development] czechop:
Sometimes when you try to make few calls one after another, dialer app freezes.
[Milestone 2 Android Development] czechop:
The last one(25.11.2013) is still on 2.6.32... next ones most likely will be on 3.0.8:)
[Milestone 2 Android Development] czechop:
Have you followed installation instructions? Especially first point:

"Install my CM10.2 version >= 07.11.2013 first" ?

This is a requirement. You don't need to boot it(I mean CM10.2), just install it and reboot into bootmenu->recovery. Then it should work fine:)
[Milestone 2 Android Development] dulocox:
It worked! thank you! :)

The problem was the version (my bad =X). I was flashing from 21.11
[Milestone 2 Android Development] rabinhood:
Installed 25.11 version. Tried for a minute or 2. Main problems:

1. Cannot synchronize contacts & calendar to Google, even though correct username/pass is entered.

2. Answered one call - the person on the other side sounded very, very quiet.

After these "discoveries" reverted back to 10.2. :)

[EDIT]

But it has a great potential! (that's the sentence used most often to describe Polish soccer players)
[Milestone 2 Android Development] czechop:
Any chance that you haven't wiped your data? Haven't had any problems with the sound volume myself.

Regarding synchronization... have you used core gapps 24.11.2013(from the link on the first page)?

Great potential... good one;):D
[Milestone 2 Android Development] yuriaps:
For me, everything is good, except the sound of incoming calls. The sound is very low and when i put in speaker mode, nothing happens.
[Milestone 2 Android Development] rabinhood:
Thanks. That was the case.

[EDIT]

OK. Installed it again. It seems to be snappier than 10.2, but unfortunately I've encountered some more problems.

1. There are random reboots (during Titanium Backup restore). I've flashed only 25.11 ROM and 24.11 gapps.

2. During call speakerphone icon does nothing - doesn't turn on the speakerphone.

Came back to 10.2 again (today that's the second time). :) That's great that system backup/restore/reinstall is so easy and convenient, that one can perform them several times a day. :)
[Milestone 2 Android Development] rkrisi:
Hello everybody!

I have installed this rom i dont have problems with volume during call, and speakerphone button also work. [MENTION=4806452]czechop[/MENTION] i have one question. Later do you add the missing cyanogenmod features? Like battery percentage, etc?
[Milestone 2 Android Development] rabinhood:
Interesting. Maybe I'll try again... And does wifi work? Because I couldn't switch it on.
[Milestone 2 Android Development] rkrisi:
Yes wifi also works :)

---------- Post added at 10:29 PM ---------- Previous post was at 10:27 PM ----------

But i dont know how to use GPS :D location is turned on with, but Maps is waiting for location, and waze also...

Another question: why the notification line is not transparable?
[Milestone 2 Android Development] rabinhood:
Perhaps I'll never fully understand / control Android. I tried to install Kit Kat for several times, did full system wipes, but nothing helped - still had problems either with wifi, or with Google synchronization.

Then something broke, phone bricked, and I had to come from the beginning (stock GB flash). And...

Now KitKat's running well. Even more! It's visibly smoother than CM10.2 (which was very fast). I wonder if CM11 is not as fast as CM7. WiFi's working, mobile data's working, contacts/calendar sync's working.

So now I'm starting normal everyday use. I'll report if I find some bugs. [MENTION=4806452]czechop[/MENTION] - thank you very much for this port!
[Milestone 2 Android Development] rkrisi:
Sorry, I didn't said but I also bricked my phone, and I had to reflash and everything. And after that I have installed cm11

---------- Post added at 07:12 AM ---------- Previous post was at 07:11 AM ----------

firstly I also can't install cm11. I have to brick my phone first

---------- Post added at 07:30 AM ---------- Previous post was at 07:12 AM ----------

another thing which I dont know. Does the KitKat "new" features work in this rom? Like the smart caller id, sms with hangouts...
[Milestone 2 Android Development] czechop:
Interesting. Perhaps there is some bug in the recovery so that it doesn't actually wipe everything, while flashing SBF obviously does.

Anyway... so now everything is working fine? Is the the volume of incoming calls ok?

Could you try to make few calls in a row? On my phone first call breaks sound for a while, so that next call hangs the dialer... but maybe I just need to softbreak milestone:):D
[Milestone 2 Android Development] czechop:
They should work:)
[Milestone 2 Android Development] czechop:
GPS works fine on my device(tried with GPSStatus from the market and with the location mode set to "Device only" in the settings).

Regarding notification line not being transparent... that's a bug:)
[Milestone 2 Android Development] Lukash_Master:
Nope. I use standard ROM clock values (1 GHz).
[Milestone 2 Android Development] Linuxser:
There was a problem with the telephony layer of the phone

Hello,

I successfully installed this mod on revival my old MoMi2. Is working great. I can't believe KK running on this phone :cowboy:

Mostly error free for now. Maybe some battery drain I'm measuring. However, there one big problem coming from the network with the message There was a problem with the telephony layer of the phone

As soon as the error comes the phone loses the network connection and you have to reboot in order to make it work again.

I was reading other threads about an I can't get any conclusion if there is a real fix. I bought this phone back to early 2011 and changing the motherboard is not a option.

I remember to test on this same phone with CM 7 and CM10 over a year ago and no problem at all.

Any help would be highly appreciated.
[Milestone 2 Android Development] rxmeister:
Yup, I encountered such thing but it stopped at some moment.

Honestly, I don't know what happened it's working fine right now.

PS. I'm on 2 version behind the latest, I didn't upgraded to the newest yet.
[Milestone 2 Android Development] Linuxser:
Hello,

Since this last reply I've found an answer from czechop on 10.2 thread, suggesting to change the baseband. I changed mine to china baseband 850/1900/2100 and the problem is gone for last 12 hours.

I suggest you to test this. In fact you only need a compatible gsm baseband with your region no matter the name but the frequencies.

What suddenly stopped to work is cLock widget. When you hit the widget to open the extended weather nothing happens. Any ideas?
[Milestone 2 Android Development] rxmeister:
Okay, may be in your BTSs it's okay to enable this band but in my country there are a still cells with 900MHz band. :P
[Milestone 2 Android Development] Linuxser:
Hi,

Oh no. I'm just saying "changing the baseband could be the fix for the problem" and setting Chinese baseband instead my own´s country works for me. In fact, three days after without any error. :o
[Milestone 2 Android Development] angahith:
Hrmmm, just did an update from the 20.1 to 24.2 build and now I'm bootlooping...

cache and dalvik are wiped, even tried wiping data after a few attempts, but it won't boot up anymore.

What I found odd is that, after installing the zip, TWRP tells me that my device isn't rooted.

Any ideas?
[Milestone 2 Android Development] patrol-cz:
Are you able to enter the TWRP recovery from the bootloop ? If yes, you can make some diagnosis. At first, click on "mount" and mount /system. Then, go to "Advanced" / "File Manager" and examine the /system directory. There should be a lot of files, including /system/bin/su, which is important for acquiring root access. If you will get error from TWRP that /system cannot be mounted, something wrong went with the flashing and you can try to reflash.
[Milestone 2 Android Development] angahith:
Yeah, I can still get to TWRP, but...

hurrdurr, nevermind. I don't know HOW it happened, but despite passing the MD5 check right after I copied it to the SD, the zip doesn't pass it now. Maybe my sd card was somehow messed up. I feel stupid.

I formatted my SD, tried again and now it boots. I'm especially pissed that I wiped data, now.

Edit:

Well, this was unexpected. After the card getting corrupted two more times, I found the culprit. It's my goddamn USB hub.
[Milestone 2 Android Development] patrol-cz:
Yes, it can happen. Linux file systems are buffering last files in their internal caches, so it's possible, that when you do md5sum on a freshly stored file, it will be (at least partly) computed from the cache instead of the real media. So, the best way is to store the md5 file together with the zip and let the recovery itself check it - the phone had to be rebooted to enter the recovery, so all the caches are flushed and you are checking real media.

Pavel
[Milestone 2 Android Development] rkrisi:
Since the last update in Snapchat the camera doesn't works. Anyone has an idea to get working the camera?
[Milestone 2 Android Development] Kootee83:
Hi! I can't connect to Ad-hoc WiFi network (on other ROMs I could). Did anyone found any workaround?

I've found this: http://xdaforums.com/showthread.php?t=2405202

could you czechop apply this patch on the ROM?
[Milestone 2 Android Development] patrol-cz:
I have another wish on my list: As MoMi2 now has host mode USB available, would it be possible to compile usbserial.ko and pl2303.ko ? Together with a decent comm package, it would become one of the smallest serial terminals on the world :).

Pavel
[Milestone 2 Android Development] angahith:
Well, I got my phone to work again and all (still can't believe my USB hub was the problem) but now I'm running into the Telephony Layer issue others reported.

Has anybody found a 900/2100 baseband where it doesn't happen, yet?

I already went through six different ones. (None of the Central Europe ones work, for example)
[Milestone 2 Android Development] czechop:
On milestone2 we are using TI flavor of the wpa supplicant, so this patch won't work.
[Milestone 2 Android Development] czechop:
Both of this drivers are already in the kernel, so you should be able to turn your phone into a "smallest serial terminal on the world" :D
[Milestone 2 Android Development] czechop:
Switch to the laters build... telephony layer problems seems to be gone there:)
[Milestone 2 Android Development] angahith:
Oh sweet, guess that came out just a few minutes after my post, haha.
[Milestone 2 Android Development] Kootee83:
Thanks for your reply. I don't know how then, but on Engle_Mars CM11 Ad-hoc is working good. Maybe he would tell us, how to enable it on this ROM...
[Milestone 2 Android Development] patrol-cz:
Thanks for the new release, Czechop!

... and allow a small question. Is it possible to activate SELinux ? Is it compiled onto the kernel ? I've downloaded the "SELinux mode changer" app but it can't do anything, saying that the support is disabled.

Regards, Pavel
[Milestone 2 Android Development] Kootee83:
Could anyone place new version on other server please. I still get message from google: "Too many users have viewed or downloaded this file recently. Please try accessing the file again later" and he proposes to try after 24 hours... :(
[Milestone 2 Android Development] fanghongjian:
me too..the google driver mostly has problem.:(
[Milestone 2 Android Development] czajunia:
APN settings

Does anyone have problems with saving a new APN? I've tired several times and it doesn't work. Plus, it also wants me to provide MCC/MNC details even though my provider says I can leave them blank. It wasn't necessary to provide those on the previous builds. Any ideas? Thanks.
[Milestone 2 Android Development] Kootee83:
If anyone still have problems downloading, you can get it here.
[Milestone 2 Android Development] patton82:
The latest build works very well, no issues found till now, thank you

Inviato dal mio A953 utilizzando Tapatalk
[Milestone 2 Android Development] thenexor:
Latest build going well 'till now: I had battery problems before it, time will tell if they are resolved.

There is one possible issue I wasn't aware of: when upgrading, it may happen that connection to google services does no longer work. You would get orange signal icons in the quick settings panel, thus many notifications, play store and some other apps might no longer work. To avoid this, always reflash GApps package after flasging the ROM!
[Milestone 2 Android Development] tydiamond11:
Would this Rom work on the Droid 2 ? If not what would it take to get it working are they not the same phones? Just one is CDMA and the other GSM? Thanks
[Milestone 2 Android Development] adamantem:
Hi, can you ported to the Droid 2 Global???