yashsingh1/xdaforums huggingface dataset:
[Defy Android Development] Shubhamqweasd:
same happens with me :(
[Defy Android Development] Sivaguru:
Boots fine.

Wiped data/cache

Installed the Zip file

chose 2nd boot

booted without any problems.

Volume buttons are not working.

Defy/Red lense
[Defy Android Development] Shubhamqweasd:
quarx , anything else that green lens users can try to make it boot ?
[Defy Android Development] 57op:
Tried on my red lense defy (mb525), booted fine.

Media server, indeed, affected performance and cpu max freq was at 300Mhz.

As others said, volume buttons aren't working.

Great work :)

p.s. cpu max freq autoset at 300Mhz on clicking power button (= display off).
[Defy Android Development] Quarx:
Try remove ./system/bootmenu/script/overclock.sh, then reboot and try boot android.

This script affect on 3.0 kernel(don't know how, but affect). Maybe not good for ES 1.1.

Defy has OMAP3630 ES1.1, defy+ OMAP3630 ES1.2

Can someone post which ES on red defy? This can be find in dmesg, first lines.
[Defy Android Development] birr97:
Re: [JB+] CM10.1 Android 4.2.1 for the Defy(+)

How long should it take to boot?
[Defy Android Development] 57op:
Mine is ES 1.2

<6>OMAP3630 ES1.2 (l2cache iva sgx neon isp 192mhz_clk )
[Defy Android Development] Husi10:
I will try to explain my though about the data issue

It happens just in this cases :

When you turn off wifi or airplane mode

When your phone changes antenna when you're moving

So every time the phone needs to establish the connection for data it will fail at first try (except if you're lucky). But after some unsuccessful tries it should work.

I see 2 solution. First, we should try to decrease the timeout between each attempts to connect to data. Or we could try to find why the phone doesn't connect at first time and fix it.
[Defy Android Development] Gianluca85:
sometimes my moto defy reboot in recovery, why?

and when I select reboot (in cwm recovery) and phone start, I see this message:

"the device rebooted due to a problem in the phone's layer"

thanks
[Defy Android Development] Kayant:
Data connection

During my somewhat failed attempt at porting 4.2.2 AOSP roms for our defy I found something interesting which I think should help make data work like it was in JB 4.1.2.... During my experimenting I remembered that I once tried two approaches with getting data working for our defy which was to just use Quarx's repo for hardware_ril and frameworks_opt_telephony and the other was to merge in the necessary patches from Quarx's repo into to my forked repo from SlimBean..... When I used the second method on Rootbox as it's the only one currently almost working perfectly I found that data behaves very closely to JB 4.1.2 and when I tried using Quarx's repo's it behaved like it is now in CM10.1 so I have just recently submitted a pull request to Quarx which I think will fix the issue but am not 100% sure it's the right patch as am not a dev :p..... Hopefully Quarx sees it and tests it out and the issue is somewhat fixed for you guys.

link to the pull request here for anyone is interested ---> https://github.com/Quarx2k/android_frameworks_opt_telephony/pull/1
[Defy Android Development] Blechd0se:
Does it really fix something? From a quick look at the snippet it only handles the visual part of RIL (how many signal bars etc you have)

and overrides them. Do we have "ro.telephony.ril.v3" somewhere in our system properties? If not, it won't be called at all.

Did you tried a fresh CM10.1 with this fix?

Source of SignalStrength

Edit:

Checked it, it gets called :)
[Defy Android Development] Kayant:
Yh the code was modified by the SlimBean team when they ported it originally we would need to have SignalStrengthgsm instead of SignalStrength in system.prop

Am testing it myself also ... Just need to finish syncing then leave my comp for 5 hrs or so to build :p
[Defy Android Development] Blechd0se:
I was a little bit curious about this and did some digging;

on 4.1 we had a patch by SlugZero, which (almost)

solved data problems.

I can't find it in 4.2, probably because its missing here ?

updateDataStallInfo()

should have this in the last else-clause;

if (VDBG) log("updateDataStallInfo: NONE");
//This is just a hack to get data connection up again, proper way would be to actually trigger recovery
mPhone.mCM.getDataCallList(this.obtainMessage(EVENT_DATA_STATE_CHANGED));

Don't know if its working, this would implement [MENTION=4514770]Husi10[/MENTION] first idea with a faster reconnect.

However like SlugZero pointed out; its an issue on all android versions and this is why i assumed its more like an hardware than an software issue.

Looks like i have to refresh my java skills...
[Defy Android Development] xinrag:
Hi!

Exactly - this is the main and only problem for me. In german it is called "modem" instead of "phone's layer".

Poorly it does not looks like someone could fix this(, soon.)

It looks to me that there may be no choice between anything else than a moto kernel with cm7/cm10 if you expect a stable working defy. Maybe, hopefully I am wrong and someone will find a work around for this issue.

Beste regards, Stephan
[Defy Android Development] major9:
The Reboot is a fix for Ril Bug which causes the phone to disconnect from the Provider. This is there in CM10 also.
[Defy Android Development] ccav2000:
More likely a software issue, but one we cannot fix directly since it is buried in the Motorola RIL binary shared library. All the fixes and workarounds in CM7/CM10 were in RIL.java and in the framework, since we can modify those, and there were working fine until CM10.1 came to be, there something broke either because of some change in Android or because some workaround was not ported from the earlier versions. Which is what [MENTION=4855459]Blechd0se[/MENTION] and [MENTION=4173406]Kayant[/MENTION] are trying to explore now.
[Defy Android Development] Kayant:
Update

It would seems the patch I sumbitted don't work :( but I have since then built a nightly using my repos instead of Quarx's and that has ended up in making it behave like in JB 4.1.2 ..... I have uploaded my build so people with data connection problems could please test it and report back so Quarx can find the patches that are needed from my repos.....

http://www.mediafire.com/?6un1ulwcl9u8jid
[Defy Android Development] ccav2000:
Installed and booted. First couple of attempts connected immediately. This has happened before at random however, so I will keep poking it until I am satisfied. Under testing for now, no certain conclusion yet.
[Defy Android Development] Kayant:
Yh so far so good over here as well am about to leave for school in an hour so I should be able to better test it while on the move.
[Defy Android Development] xinrag:
Hello!

Thank you! Ok, let's see. Now it is running here with sync enabled in 3G mode. (I keep my fingers crossed)
[Defy Android Development] DingoDingo:
For last hour and a half it seems OK. :)
[Defy Android Development] :
cant change files with root explorer (for example system/usr/keylayout) when I change them to make screenlock with search button it transforms to a 0 byte file and I have to revert the change
[Defy Android Development] FcukBloat:
doesn't seem a rom problem to me.. I always do the same after flashing a new build with ES File Manager and it works without any problems.. and search button turns the screen off correctly..
[Defy Android Development] :
thank you, it worked on last rom I dont know why it doesnt now :/

will try with es file manager, do you have a flasheable zip or something? ^^ incase I cant make it work?
[Defy Android Development] FcukBloat:
nope.. i just have the two modified files saved on the sdcard and after flashing a new build i always copy them in system-usr-keylayout overwriting the original ones ;)
[Defy Android Development] ccav2000:
Following up on the data connection issue, I've been running [MENTION=4173406]Kayant[/MENTION]'s build for about 3:30 hours now and the data connection connection works as it should, always connects with the first try after I turn off the WiFi within just a few seconds.

As far as I can tell the bug seems fixed if [MENTION=4173406]Kayant[/MENTION]'s repos are used. Up to [MENTION=513620]Quarx[/MENTION] and the rest of the team now to find the differences between their repos.
[Defy Android Development] Kayant:
I can also piggyback on that and agree since about 12:40 to about 5:08 I have had data on and I don't think it has once disconnected :D but I can't be 100% sure as I wasn't using it the whole time but when I do it was still connected so...
[Defy Android Development] shvelo:
Can someone port this to Bravo?
[Defy Android Development] niksy+:
Oh boy, are you well informed or what - http://quarx2k.ru/cm10.1-nightly-bravo(kobe)/
[Defy Android Development] okij:
Theory: Are memory leaks probably the reason for system slowdowns?

I know there just are some exciting news going on about the data bug thank to Kayant, but I also want to draw some attention to another serious problem we have with the CM10 / CM10.1 builds so far: System slowdowns after a couple of days of uptime :)

I'm currently on Quarx latest 05-27 nightly and after 5 days of uptime, my Defy+ became almost unusable and unrespondant. :silly:

I have the strong impression that the system became unrespondant because of too little available memory. Therefore, I compared the memory allocation of a couple of Android tasks before and after a fresh reboot with the app Android System Info. The numbers I got are:

Before reboot:

uptime: 5 days, 5 hours

free RAM: 38 MB (after closing all apps in the "recent apps" menu!)

The top memory consumers according to Android System Info were:

Android-System 81 MB

android.process.acore 67 MB

System-UI 64 MB

com.google.process.gapps 36 MB

Apex Launcher isn't even listen anymore, because it's been closed by the Android memory management in order to free memory for starting Android System Info!

After reboot:

free RAM: 81 MB (which is a normal amount for me after a fresh boot)

The above mentioned tasks now just occupied following amounts of memory:

Android-System 59 MB

android.process.acore 20 MB

System-UI 46 MB

com.google.process.gapps 17 MB

That means that those four tasks occupied over 100 MB more after some days of uptime! I didn't compare the memory usages of other tasks, but they probably also occupy unnecessarily more memory after some days.

This leads me to the theory, that there are some sort of memory leaks in the CM10 / CM10.1 builds, so that once allocated memory isn't freed properly afterwards. Because of this, the available memory gets smaller and smaller and in the end the system becomes totally unrespondant because when starting even a small app or task, the Android memory management has to kill the other tasks like the launcher and such. :eek:

[MENTION=513620]Quarx[/MENTION] and the other devs: Is something like memory leaks already known for memory allocation and freeing functions of the Android OS? If not: Could you please look into this issue? I'm quite sure that many system slowdowns that other Defy users reported are because of this.

[MENTION=535343]all[/MENTION]: could you please have a look and report if your systems behave similar, so that we get some feedback if there really is a correlation between memory occupation and system slowdown.

BTW, I'm sure that this slowdown hasn't to do with the governor, as I'm currently using Boosted but before it was the same with Interactive. Both governors are working well for me, both are also very comparable in terms of battery drain (both low with Quarx's latest build). :)
[Defy Android Development] DingoDingo:
Using almost a 6 hours, no drops, checked with Connection Checker.

It seems data bug is fixed!
[Defy Android Development] steelbreeze:
Guys I am attaching a screenshot of the battery screen under settings. I am on the 27/05 nightly and am having some really bad battery backup. I am also using Greenify and it has helped a little. As you can see in the screenshot, my phone has just run for about 12hrs and it is already on 15%. All I have used the phone for is a couple of calls lasting for 2 minutes each and whatsapp. Thats it!! Please help!!

Also, don't know if anyone has observed this or not, but when taking pics with the camera, you actually get more in the pic than what is visible on the screen. For eg, if I am capturing my laptop screen and I can see only that while taking the pic, when I check the pic in the gallery, the area above the screen and below it is also captured. This is true for every pic that I take with the camera. Has anybody experienced this?
[Defy Android Development] dab512:
I got same **** :(
[Defy Android Development] atulclassic:
Kernel reqd with data bug fixed

Dear Devs..since the data bug is seemed to be fixed now with Kayant's contribution :D..is it possible to update the same through kernel or any other flashable file only..since i don't want to format my phone again.
[Defy Android Development] DingoDingo:
I flashed Kayant's rom over 27052013 and did only clean cache and dalvik, it works.
[Defy Android Development] Feche:
I am downloading Kayant version, thanks :D

EDIT: I just installed it, the only problem is that I don't have network, on baseband selection I set the correct values, but on restart it says 'Unknown'.
[Defy Android Development] disadjusted:
16:9 mode in stock cam app?

That's due to pic's in CM10.1 stock cam app are taken in 4:3 aspect ratio, but our screen is 16:9. To fill the screen entirely the upper and lower areas of the sensor are cut at the screen edges.

That's also the reason why the taken picture (when shown in the gallery) doesn't fit your screen anymore and has blank spaces on both left and right.

I'm using a third party app (camerazoomFX) which has a setting to take pictures in 16:9 to workaround this issue.

But might make sense to integrate a 16:9 mode in stock cam app for taking pictures on 16:9 screens anyway...

Because Defy isn't the only 16:9 phone... perhaps there's already a patch for this somewhere?
[Defy Android Development] pakarbu:
about bug in camera which doesnt take wide picture,anyone success on porting cm7 camera to cm10.1?

wide picture work well on cm7 camera..
[Defy Android Development] vic160890:
Blechd0se Kernel

Hi guys.

After a few days of experiencing with Blechd0se's modified kernel I notice the following:

With the tunables:

-suspend_enable = 0

-suspend_freq = 1000000

there is almost no improvement on incoming call delay, the CPU stats show the same high usage and suspend on top of the list. The only thing that seems to be better is the wake up on power button time.

Now, in this latest ROM, with or without("youuuuuu") this kernel the phone becomes completely useless with 3G on and navigating on chrome. 2 pages in and if you turn off the screen it will take almost 2 minutes for it to wake up.

If the next ROM includes Kyants bug fixes, i'll make a completely clean install and hope for the best.

Regards.
[Defy Android Development] ccav2000:
Sounds like your installation was borked, try to clean install.
[Defy Android Development] Blechd0se:
Thanks for the feedback, you are right i found a bug with the suspend handling. It can't scale up (if avg_load > 80%) because its in the wrong function.

I will fix this as soon as possible.

However, disabling suspend_enabled has nothing to do with actual suspend (=deepsleep). It only allows the governor to raise frequencies just like before

while screen is off. Have you looked at the dmesg output? Would be nice to see on which frequencies this problem exits,

i have enabled them for a reason :)

Furthermore i finished backporting interactive from 3.4, but i need to test it more (there are around 20+ new commits just for interactive which i added

and lots of things i cleaned up).

So far it looks very promising, i managed to make it behave the way i want it :)

A really cool new feature is to change the target_load value depending on speed of the cpu.

Example: if cpu is at 300 we can set target_load to 60% (to scale up quickly), if it is at 600 we can change target_load to 80% and so on and all

is tunable! If desired i can make another nightly before i set the commit :)

I have to find proper values here for best batterylife/performance and after this is done, i will focus on some sort of kernel control app, i

think i will rework the hole defy parts in settings.
[Defy Android Development] ccav2000:
Sounds cool! If you manage to do all this, plus Kayant's finding that the solution to the data problems are in his repos, the only other major bug is Bluetooth. Of course many other things can be done too, like finishing the porting of ION, implement HW composer, etc but these are for later and the icing on the cake.
[Defy Android Development] darkvier:
hi all, i have one question for a long time with cm10.1

why the performance with webkit based browser is too poor?

i have tested dolphin (with cm7 this fly), chrome, firefox....

for example:

when I hit on the web address, the keyboard takes a long time to appear...

sometimes when I try to open urls in new tabs, they do not open...
[Defy Android Development] frozenwaverider:
In CM10 Settings, picture size 4MP(W) = widescreen

It would be strange if they removed it for CM10.1 as most new displays for anything are widescreen :)

MB525 Red lense
[Defy Android Development] kartrikpal:
thanks :0

thanks bro .. but some times whats app isn't working properly .. but i fixed it on reinstalling and cleaning cache ...

awesome with nightly 10.1 ..expecting for proper fix for battery
[Defy Android Development] Feche:
Okay, I installed it plenty of times until it got working haha :D

3G connects on first attempt, good job Kayant :good:
[Defy Android Development] Quarx:
[MENTION=4173406]Kayant[/MENTION], In your build, diffs only in android_frameworks_opt_telephony?
[Defy Android Development] Kayant:
[MENTION=513620]Quarx[/MENTION]

I wasn't too sure if android_frameworks_opt_telephony was only needed so am using hardware_ril aswell.... Here are the repos I used

https://github.com/Kayant/hardware_ril/commits/jb4.2

https://github.com/Kayant/frameworks_opt_telephony/commits/jb4.2

Good luck :D
[Defy Android Development] rol525:
Quarx.

You can add the camera voice control?
[Defy Android Development] Quarx:
Yes, confirmed, problem in frameworks_opt_telephon

Thanks:)
[Defy Android Development] edglaston:
help whatsapp

because whatsapp is not compatible with this rom?
[Defy Android Development] FcukBloat:
whatsapp is perfectly working. turn off the phone, remove battery, and reboot it, and see if whatsapp works.

if not try cleaning app data and cache, or reinstalling it
[Defy Android Development] edglaston:
thanks

now is ok!
[Defy Android Development] shubhu2604:
what problem are you facing..??

some error like "whatsapp is currently not supported on tablets"

or "whatsapp not supported on custom roms"

In either of the cases, please try re-installing whatsapp and then reboot your phone.:good:
[Defy Android Development] Kayant:
No problem :D
[Defy Android Development] FcukBloat:
quarx added the data fixes in his github.. can't wait to try new build! :p
[Defy Android Development] ccav2000:
Yes, and it was just 3 lines of code that needed to get out of the way! Curse them!
[Defy Android Development] YetAnotherForumUser:
A few notes on the current build

I noticed a few things on the build I'm currently running (based on Quarx' repo dd 20130606) which might be of interest.

The Motorola usb package ([FONT="Monospace, Courier New"]/system/app/Usb.apk[/FONT]) is unhappy about the current state of the usb subsystem. It complains (loudly, every two seconds) about not being able to write to [FONT="Monospace, Courier New"]/dev/usb_device_mode[/FONT]. That file is not present in current builds as they don't use the Motorola gadget driver (mot_android.c). As the package does not do much without access to the Motorola gadget driver it does not make sense to have it around. I moved it to backup without any negative consequences so far.

The interactive governor is currently in a rather unpredictable state. I also have my questions as to whether it is worth the effort to rig it up with all sorts of 'intelligent' behaviour to make its performance more predictable and, shall we say, likeable. I generally adhere to the k.i.s.s principle, especially when it concerns kernel code. For that reason I changed my build over to the boosted governor which performs quite well and, more importantly, is predictable. As we all know PowerHAL is only adapted to the interactive governor so using another governor leads to a deluge of log spam from OMAP3 PowerHAL about it not being able to write to interactive-related sysfs files ([FONT="Monospace,Courier New"]E/OMAP3 PowerHAL(XXXX): Error writing to /sys/devices/system/cpu/cpufreq/interactive/[/FONT]...). This is due to a bug in the way the PowerHAL code checks for the presence of these files - it only checks on initialisation. Since the kernel normally boots with interactive (something I'll change on the next build) PowerHAL sets a file descriptor to the boostpulse file and assumes it to be valid. The following patch rectifies this by invalidating the descriptor when a fault occurs. This makes it possible to use other governors without the log spam. It also makes it possible to have PowerHAL reopen the boostpulse file afterwards (something it tries to do on each and every interaction with the device).

diff --git a/power/power_omap3.c b/power/power_omap3.c
index 1fa3cb7..5066f22 100644
--- a/power/power_omap3.c
+++ b/power/power_omap3.c
@@ -211,6 +211,8 @@ static void omap3_power_hint(struct power_module *module, power_hint_t hint,
if (len < 0) {
strerror_r(errno, buf, sizeof(buf));
ALOGE("Error writing to %s: %s\n", BOOSTPULSE_PATH, buf);
+ close(omap3->boostpulse_fd);
+ omap3->boostpulse_fd=-1;
}
}
break;

The real solution to these problems would be to make PowerHAL governor-independent. It could check for the current governor and adjust its behaviour accordingly. If I get the urge I might implement something like that, for now I'll test with the boosted governor without any modifications for lack of time - have to get in the first harvest of haylage for the year.
[Defy Android Development] ccav2000:
[MENTION=1316716]YetAnotherForumUser[/MENTION], I'm also using boosted for the time being and I'm just deleting the power hal to get rid of the spam. In any case it's useless unless you use interactive, all it does is modify the governor's tunables.
[Defy Android Development] FcukBloat:
guys, is movie studio working fine for you?

it crashes here immediately when trying to create a new project.. but it could be due to the changes I made to the cm build (deleted about 30 apk's) so I'm just wondering if for you it works properly, if so, I will investigate which missing apk could be the problem :silly:

thanks
[Defy Android Development] ccav2000:
No idea, it's one of the first things I delete in every build.
[Defy Android Development] venkatp:
Crashing. I guess its still not usable.
[Defy Android Development] pakarbu:
same here...anyway,I'm not using it..so not big problem for me..
[Defy Android Development] FcukBloat:
thank you very much guys! so that's another apk to remove! :good::p:victory:
[Defy Android Development] TJKV:
The usb.apk isn't present in the builds that Quarx uploads. Maybe he too deletes them, if it is built. In CM10 it is not built when compiled, don't know about CM10.1.
[Defy Android Development] niksy+:
Can't find it, either... 27/05 CM10.1

And +1 on the Movie Studio, it crashes in all CM10.1 builds... I started pre-deleting it lately :rolleyes:
[Defy Android Development] TJKV:
It seems there are a few libs in /libs relating to video editing, I usually remove those too. Not sure though, at your own risk :P

---------- Post added at 08:44 PM ---------- Previous post was at 08:41 PM ----------

How do we delete power hal? Which file is it?