yashsingh1/xdaforums huggingface dataset:
[Milestone 2 Android Development] patrol-cz:
I did something different - I modified it, so it now contains the command

rm /data/battd/*

instead of

rm -rf /data/battd

because I've found errors in logcat that /data/battd doesn't exist, so I created it, and upon the next reboot they were there again, so I searched for the cause and found this. If only the contents of the directory is removed, battd creates new files immediately and doesn't complain. I don't know, why the battery data have to be removed, but this method keeps them removed but keeps the directory in place.
[Milestone 2 Android Development] bruce7890:
Increasing the speed and responsivness of the phone

Great ROM! Does anyone want to share tips on how to make the phone run faster? Given we've got a single core chip and 512MB ram, I'm always trying to find ways to increase the speed of the phone.

I've found that turning the 3 animation scale settings down to 0.5 in developer options helps. Using the BoostedAss2 cpu governor seems to help too.

Does anyone else have any tips/suggestions they can share to increase the speed and responsiveness of the phone?
[Milestone 2 Android Development] adripred:
Hi,

Add the following line in the build.prop file:

ro.config.low_ram=true

Regards!
[Milestone 2 Android Development] bruce7890:
Great - thank you!
[Milestone 2 Android Development] dat00:
what makes this line?
[Milestone 2 Android Development] adripred:
This disables some system resources.
[Milestone 2 Android Development] czechop:
No, it shouldn't be hard to port it to milestone2. Only a few sensors are left to be ported, but it's still not very stable, so will stick to 2.6.32 for now:)
[Milestone 2 Android Development] czechop:
Hi,

I personally don't use OTG, but haven't seen anybody on the defy forum complaing about it. Beside before OTG was added to our kernel, there were also random reboots:)

Cheers,

Czesiek
[Milestone 2 Android Development] czechop:
Beside the keyboard there are also few other changes(some sensors are different). But that's not a huge problem. It just not as stable as 2.6.32 yet, and it drains battery lot more:)
[Milestone 2 Android Development] patrol-cz:
Many thanks for updating to 4.4.4, Czesiek! First few hours of testing show only positive changes!

One of the last things I would like to improve in this ROM is very low volume of the phone conversation in both earpiece and loudspeaker modes. Especially, the earpiece mode volume is really weak on my device, even the setting is of course on the max. I believe there is some "coarse" setting, available in some config file, property or something like this. All your releases are exhibiting this problem on my device, while original Moto firmware as well as for example Engle_Mars's ROMs haven't this problem. Is there a possibility to fix this without recompiling ?

With regards,

Pavel
[Milestone 2 Android Development] patrol-cz:
Hi!

I'm a little bit confused. Was OTG removed from the latest release, or not ? It doesn't work for me now :(. Simply nothing happens, the device doesn't get powered etc.

With regards,

Pavel
[Milestone 2 Android Development] dat00:
[18.07.2014] I'm just checked - OTG works fine.
[Milestone 2 Android Development] patrol-cz:
Thanks for info! So, it's not removed intentionally, it's just not working for me.

When I plug the device in, the following appears in the logcat:

W/ContextImpl( 1654): Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcast:1187 com.android.server.usb.UsbSettingsManager.deviceAttached:621 com.android.server.usb.UsbHostManager.usbDeviceAdded:156 com.android.server.usb.UsbHostManager.monitorUsbHostBus:-2 com.android.server.usb.UsbHostManager.access$000:38

and nothing happens on the UI level of the phone.

Pavel
[Milestone 2 Android Development] dat00:
full wipe and reflash )))
[Milestone 2 Android Development] patrol-cz:
I did. Didn't help :(. Still the same. BTW on two devices (two different users).
[Milestone 2 Android Development] steve8x8:
Changes 0530->0718

Thanks for your wonderful ROM!

I may have missed the ChangeLog, so I went and diff'ed the build.prop files of both ROMs.

I found that most "Defyisms" have gone, but there's still one: in cm.updater.uri ... apparently, there's no ROM repository for the MS2 right now, so CMUPdater doesn't find anything.

Nice to have ro.config.low_ram set to true by default, but where did persist.sys.usb.config go? That one seems to be the only setting that hasn't been preserved, I presume there was a reason to do so?

As a bonus, what about a tun.ko module?

Addition: With both ROMs, I found the proximity sensor only half-working within Z-DeviceTest: Approximating triggers the sensor, but removing the finger again won't flip it back, and Z FC's the corresponding thread. So far, that's the only glitch I could detect. (and I'm not even sure it's a software bug, not a hardware one - and the only way to find out would be to go back to stock :()
[Milestone 2 Android Development] lampwarez:
What a wonderful work here, Czesiek.

Call recording is working, but sound is very low. I got a little better selecting the Normal voice profile in the Dialer properties (default is none selected). Equalizer make it worse.

Best regards.
[Milestone 2 Android Development] Geomatic:
My Milestone's alive (and cooler than ever)! Thanks, Czechop!!!
[Milestone 2 Android Development] saddambea:
stuck on Motorola logo

I was running CM 10 and updated to CM10.2 (http://xdaforums.com/showthread.php?t=2451742), the latest one.

Then, after booting up, was all running well.

Reboot to recovery, went to team win recovery to flash the zip, and i´ve got an error while flashing.

Now, my phone don´t boot, and freezes in the M logo at startup.

Anyone can help?
[Milestone 2 Android Development] n1phantom:
Can you check a checksum of zip file you downloaded and compare it with value in md5 file? If it is not equals then try download it again and reflash.
[Milestone 2 Android Development] Scalabis:
Missing Governor?

Are you guys missing SmartAss since last update?

I select in Stock Recovery, but when the MS2 boots, there is no SmartAss available in Performance menu.

Thanks!

BTW, what amazing ROM!
[Milestone 2 Android Development] lampwarez:
Is it possible to make voice level higher? Even with normal voice profile selected is hard to use outdoor...
[Milestone 2 Android Development] steve8x8:
This should be fixable without modifying the ROM (for now at least).

1st tre the "Equalizer" app, move all the sliders up to max, this will give you a few dB

If I ever manage to find out where the system settings are (I have no access to the device right now) - unfortunately I cannot find any alsa* utilities inside the ROM itself - I'll get back...
[Milestone 2 Android Development] rabinhood:
IMHO one of best features of this ROM (maybe all 4.4.4?), besides fancy looking dialer, is the fact, that finally Android calendar shows 6 months history of past events, instead od 1.5 months, like in all ROMs I tried before. In my job I have to check exactly what I was doing during last 2-3 months, and Android history limitation was really annoying.

Neverthless I had some troubles on fresh install - settings manager kept crashing, couldn't be skipped, so phone was unusable. Luckily when I restored /data from a previous build, settings manager didn't pop up on reboot.

In general good job Czesiek! Keep providing us with updates. Thank you!
[Milestone 2 Android Development] Nataniel4:
Men, you are the best! 4.4.4 the last Android in a 2011 device without bugs. thanks, this is for the people that can't buy these Samsung Galaxys :)
[Milestone 2 Android Development] steve8x8:
[MENTION=2028466]Nataniel4[/MENTION]: I have one of "these Samsung Galaxys" from 2011 (a 551 aka Callisto aka GT-I5510) which I hope some day will run 4.4.4 as well ;)

Thanks to czechop for demonstrating it can be done - and to everyone involved in CM development!
[Milestone 2 Android Development] ---UFO---:
I have problem with Setup wizard FC after full wipe. Is there any solution for this? I'm using 18.7. version. Thanks
[Milestone 2 Android Development] patrol-cz:
Just close it. It can be done by tapping on the corners of the screen. The order is important, try various combinations until it goes away. You can then normally configure all the things manually.

Pavel
[Milestone 2 Android Development] Nataniel4:
I founded many bugs today :( from one day to the other the notification bar don't show anything but the led turns on the lockscreen don't open and turn on directly on the desktop and the shutdown menú don't show any option except restart and shut down and i setted more options here. the total free memory in the system partition after install the minimal Gapps is: 1 MB*.
[Milestone 2 Android Development] ssjoker:
hi

first install CM11.0 30.05.2014 then update to 18.07.2014
[Milestone 2 Android Development] PhatUgly:
Why is this necessary? I just installed 18.07 directly coming from Stock (via CM10, then CM10.2, each latest version) and all seems to be running smoothly so far.

Will I run into what Nataniel4 describes too eventually?
[Milestone 2 Android Development] Nataniel4:
I fixed the problem, I installed exactly as czechop says, first system, boot, reboot and gapps because i modified the gapps package removing the SetupWizard.apk but the system have these bugs if i do that. In my first modification, i added the moto g "light version" boot animation and Moto notification tone, now i use the system as czechop says and works, the one thing, is that sometimes the phone freezes and reboots, that don't happens with cm10.2 by czechop, but this system refresh the Wi-Fi and don't have that kind of bugs, i don't speak english and i don't use translator, sorry for my english.
[Milestone 2 Android Development] PhatUgly:
Just wanted to report back.

Been running the newest version of this rom for four days now without any problems. The "modem stopped working" bug didn't appear once.

I flashed from stock via the recommended method (first cm 10, then cm 10.2 then finally cm 11) always sticking closely to the suggested procedures (rebooting before gapps, formating to ext4 and so on).

Works very good, only downside compared to stock is the reduced battery life.
[Milestone 2 Android Development] steve8x8:
Re: battery life: Did you change the governor?
[Milestone 2 Android Development] PhatUgly:
Nope, not yet. But good point, which one would you recommend me to try?
[Milestone 2 Android Development] Nataniel4:
I extended the battery life close to 50% more than the stock rom, you must to go to Hwa Settings and deselect all except browsers, games, hard applications, Camera and Maps. Next you must to calibrate the auto brightness to change the 47% of screen battery drain into 23% with very visible brightness levels.

I recommend this levels:

In the first screen, change the Adjustement sensibility to medium

and tap on Adjust and set as:

0 lux = 0%

8 lux= 3%

15 lux = 12%

100 lux = 25%

3000 lux = 37%

8000+ lux = 50%

this levels are the best for visibility and battery life.
[Milestone 2 Android Development] Fedroid:
OTG worked fine con previous version. But on this one not. When I plug a USB device is detected but content is not shown. Any clue?
[Milestone 2 Android Development] steve8x8:
Could persist.sys.usb.config be the culprit? (see http://xdaforums.com/showpost.php?p=54438551&postcount=511) That seems to be the only important regression between the build.prop files of both ROMs...
[Milestone 2 Android Development] Nataniel4:
EDIT: OK no... the phone keeps rebooting...

No bugs :D Finally!!!

Now the phone is very stable and does not reboot anymore, what is the problem?

The Hwa settings, keep all applications enabled and not open this application anymore (I hid the app from the app list), but, why?

When the phone change from an application with HWA to other application without HWA so many times (generally when you multitask) the phone freezes and reboot, some applications does not work or have glitches and bugs if you don't enable the HWA, and the battery/performance is not really affected, on the contrary, the overall performance is better that is why I recommend to enable all application in the Hwa Settings and never use this app again.
[Milestone 2 Android Development] czechop:
OTG is still there. There were some(plenty) of patches to the kernel recently in the 17.07 version, so perhaps one of them break OTG for you. What device are you trying to connect? Could you provide dmesg logs?

Cheers,

Czesiek
[Milestone 2 Android Development] czechop:
Was removed... sorry... will(if won't forget) bring it back in the next release :)
[Milestone 2 Android Development] Scalabis:
Thanks Czechop!

The best part of your replay is: "next release"! :D
[Milestone 2 Android Development] patrol-cz:
Sorry, but not now. I've flashed to the KitKatPlus, which uses your ROM as a base, and OTG works perfectly there. It was probably something wrong with flashing. If there will not be a new KK+ release based on your 10.03 release soon, I'll flash your 10.03 and I'll let you know.
[Milestone 2 Android Development] dat00:
Where is mininmal gaps now? Topic about minimal is closed((((
[Milestone 2 Android Development] dat00:
http://xdaforums.com/showthread.php?t=2397942

????
[Milestone 2 Android Development] dat00:
even PICO MODULAR PACKAGE not install - not enough space.
[Milestone 2 Android Development] L3ibnitZ:
FYI:

http://www.xda-developers.com/android/motorola-defy-repartition/

That could solve the "not enough storage" problem
[Milestone 2 Android Development] dat00:
How Can I use it? copy and paste in terminal?
[Milestone 2 Android Development] L3ibnitZ:
I dont think that it is usable for our ms2 yet. Someone has to port and adapt it.
[Milestone 2 Android Development] relaxxrr:
Hi czechop, thank You for developing new roms for our oldy M2! Your CM 10.2 was stable and perfect, I guess CM 11 will be also awesome :)

Please, can anyone upload minimal GAPPS package for this ROM (not JB), as in the first post, link redirects to closed thread, and all GAPPS were deleted, the new GAPPS "PA-GOOGLE APPS" (http://xdaforums.com/showthread.php?t=2397942) are too big for our partition (smallest 36MB). Thank You!

Thank You and Good luck, Czesiek!
[Milestone 2 Android Development] czechop:
Just uploaded gapps I use(not brand new, but they work just fine), and updated link on the first page :)
[Milestone 2 Android Development] relaxxrr:
Thank You very much! :good:
[Milestone 2 Android Development] mik2929:
What happens to have access to the application google play store ?
[Milestone 2 Android Development] ssjoker:
hi

if anybody wants full gapps see this thread
[Milestone 2 Android Development] patrol-cz:
Hi!

Does it mean that you will not issue a new KK+ ? Should we just install plain Czechop's CM11 + your ported Gapps ?

Pavel
[Milestone 2 Android Development] katchoo:
i still am in desperate need of the autocorrect bar without any 3rd party application (swiftkey would have this feature but slows down the whole phone imho)
[Milestone 2 Android Development] patrol-cz:
Hi Czesiek and others!

Thanks for this release. I'm using it with ssjoker's ported pa-gapps and it seems to work perfectly.

OTG also works again, just tested it!

The only problem I can see now is that the Back and Volume buttons seem somewhat ill.

They don't work as usual - for example, I can't use the Back button to go back in the stack of chained apps (like an app started from the Store) or in a menu hierarchy. However, when I recall the Quick menu, the Back button cancels it, and in this menu even the Volume buttons are active (and regulate the volume as expected). However, the Back button is dead most of the cases and Home must be used instead, which is very stupid.

I've looked onto logcat and pressing Back doesn't emit even a single line onto it.

I've tried to google these symptoms and I've found similar problems reported for recent snapshots of CM11 for Samsung devices, but with no solution reported.

Does anybody know more, especially, how to fix this ?

With regards,

Pavel
[Milestone 2 Android Development] rabinhood:
I'm not sure what's the problem. Volume buttons, and capacitive back are working fine for me. Exactly what actions should I do to repeat problems you describe?
[Milestone 2 Android Development] patrol-cz:
For example open the Settings menu and then Wireless. Pressing Back for the first time should bring you back to the Settings top menu and for the second time it will close the menu and you'll be on your Home screen. For me, it doesn't work, I'm frozen in Wireless settings and I have to press Home button to return.

I've done some experiments. I reflashed with full data wipe. After that, the phone was unusable, because there was no launcher running (black screen) and in the settings it was not possible to enter the Google account. However, the Back button WORKED as usually I tried to recall Factory reset once more from the phone UI and after that, it ended in a boot loop, however the recovery was accessible, so now I'm again on my latest working backup. I'll experiment more later.

Pavel
[Milestone 2 Android Development] rabinhood:
Here it's working OK. Settings -> Wireless, <back> -> Settings, <back> -> Homescreen (and not the first page, but the page I had opened before going to settings). I'm using the latest build. I don't have problems similar to yours, so I think they are not related to software. Maybe you have a faulty phone?
[Milestone 2 Android Development] patrol-cz:
So, which Gapps are you using ? I tried with that ssjoker's pa-gapps and had this problem.
[Milestone 2 Android Development] patrol-cz:
OK, I think I found it.

The problem appears, when I'm trying to dirty-flash CM11-141003 from ssjoker's M2 KitKat+ with either minimal gapps or ssjokers pa-gapps. Full data wipe is necessary. I tried both gapps packages with full wipe (of course the wipe was done BEFORE flashing, because I know that the pa-gapps use symlinking some apps to the data partition). However, I still had problems with this package, so I ended up with Czechop's recommended minimal gapps. After defeating still crashing first-time wizard, all seems to be OK. Now I'm restoring my environment, but it seems that this is the way to go.

Thanks Czesiek for your new release!

Regards, Pavel
[Milestone 2 Android Development] steve8x8:
Have you tried ShapeWriter? (I know it's pretty old and not supported anymore, but I'm still using it.)
[Milestone 2 Android Development] santi1993:
im to hyped about this rom, how about battery life and 3d acceleration? D:
[Milestone 2 Android Development] dat00:
battery life is good, but on this rom i can't view any on line TV stream((( only on Puffin browser with big lag and drops
[Milestone 2 Android Development] thenexor:
Italian users are suffering of constant crashing on low battery, due to this issue: http://review.cyanogenmod.org/#/c/74572/

The fix would be switching to another language, until Czechop publishes an updated ROM.

The problem is in /system/priv-apps/Keyguard.apk, but the one from the Defy's rom doesn't work, i tested! :(
[Milestone 2 Android Development] steve8x8:
Any progress?
[Milestone 2 Android Development] santi1993:
is it rom intended for daily usage? anyone can sync quarx november's 15 build to this device? they already're in december's 1 build but i have readd that nov/15 it's a lot better.

It's camera fully usable?
[Milestone 2 Android Development] rabinhood:
IMHO it can be used on daily routine. It's smooth enough, and quite stable (including camera). Only thing is that occasionaly it auto-reboots reporting problems with telephone layer, but it's definitely worth trying.
[Milestone 2 Android Development] PhatUgly:
Totally usable as daily driver. Of course it get's kind of laggy here and there due to hardware limitations but when you are not up to anything fancy it gives you a reliable phone with up to date software.
[Milestone 2 Android Development] santi1993:
Hi, how can i fix it? now im collecting info about my device to proper upgrade it to 4.4.4, which is the best version at the date? for experiencie i assume that latest isn't better, so well, you tell me please!

Ohh, hardware limitations are very noticeable in this device? for example, is it smooth as ginger is?
[Milestone 2 Android Development] rabinhood:
These problems are quite rare. IMHO the latest build is the best. Also sometimes there were problems with non-functioning wifi tether, but there was a flashable zip to fix them.

Again IMHO the fastest was Froyo based CM7, then all GB based ROMs (including stock). CM10 was slowest, CM 10.1 a bit better, and CM11 (KitKat) runs smooth, only a bit slower than stock GB. MS2 meets low end hardware specifications for KitKat (1x1 GHz, 512 MB RAM), so it struggles, but is usable.
[Milestone 2 Android Development] santi1993:
Well, ill check it if worth...

Im on 2.3.4 retail @ 70.12.

All i will do is:

Bootstrap, wipe, instal cm10.2, reboot recovery, install cm11, intialize, bootstrap, 2ndinit, gapps, and dats all?
[Milestone 2 Android Development] steve8x8:
I don't have access to my notes (which I took back in summer) right now, but if you follow the instructions for 10.2 in the separate XDA thread (which IIRC include *early* rooting and debootstrapping to get the recovery replaced, and wasn't there the requirement to install pure cm10 in between as well? my memory isn't as good as it was when I was younger) you can't fail.

I'm still running czechop's 20140718 here, and it's pretty solid.
[Milestone 2 Android Development] rbr1991:
I recently bought a replacement battery, but to make it work I think I need to disable the 1% battery steps in CM11. How can this be done? Have the Cyanogenmod Settings vanished?
[Milestone 2 Android Development] rabinhood:
I don't think you have to do anything with 1% battery steps. At least I didn't have to do anything. Just put a new battery and it should be working. You can use 'battery calibrator' app to calibrate the new battery.
[Milestone 2 Android Development] fanghongjian:
Thanks for your new update , Happy new year.
[Milestone 2 Android Development] patrol-cz:
Many thanks and Merry Christmas!
[Milestone 2 Android Development] Scalabis:
Thanks for the update!

Happy X-mas and New Year!
[Milestone 2 Android Development] Geomatic:
Thanks for the update, works great!
[Milestone 2 Android Development] dat00:
give me please Calendar_Sync_4.4.4 for this ROM

---------- Post added at 10:28 AM ---------- Previous post was at 10:05 AM ----------

I have tried minimal gapps with Calendar sync from Defy http://xdaforums.com/showthread.php?t=2779598 and it's working. whether it is possible to use these gapps without trouble?
[Milestone 2 Android Development] relaxxrr:
Thank You for update! Happy New 2015 Year! :)
[Milestone 2 Android Development] rbr1991:
Thanks so much for keeping our oldies running! What is the update precedure from your previous release, just flash in recovery, no wipes, nothing?
[Milestone 2 Android Development] Bocskay:
Hi,

I made a dirty install and works fine.:good:

Just copy zip files to device, reboot to recovery and install. That's all.