yashsingh1/xdaforums huggingface dataset:
[Defy Android Development] kryptonitiko:
Excuse me master Quarx....how can I have 15 steps volume? :)
[Defy Android Development] FINEEEEE:
editing the framework-jar ;)..
[Defy Android Development] kryptonitiko:
Mmmmm....how? :p

---------- Post added at 10:19 AM ---------- Previous post was at 10:14 AM ----------

Mmmm.....how? :p
[Defy Android Development] hsrars-d:
http://www.guidingtech.com/14998/customize-media-volume-loudness-android/

y u no use google?? ;)
[Defy Android Development] kryptonitiko:
Sorry but for now I have just internet on my phone.....
[Defy Android Development] maniac103:
I've uploaded a new set of builds. Everyone with the infamous battery drop problem is invited to try it; it should at least fix it for some (permissions for /pds/public/battd/* were incorrect, so battd couldn't read them).
[Defy Android Development] oSandmaNo:
I want to fix the permissions without flashing ROM. Im on Fuzz's build now. What permissions should i give?
[Defy Android Development] juan296:
@Maniac: I use render effects, I mean... when I go to, CM settings -> interface -> render effect -> I use "N1 cool" .. so, sometimes I reboot my phone and my phone is by default again (I lost this config)

Can you write a little script, that my defy save this change? (remain on N1 cool)

Thanks a bunch :)
[Defy Android Development] popadic022:
changelog for manic new release "cm-7-20121002-UNOFFICIAL-jordan_plus-signed"??? stable?
[Defy Android Development] Steveletack:
Changelog:

-Batterydrop Fix

-Telephone can be completely disabled now

-ADB in the Bootmenu is working again

-DroidSSHd is working good now
[Defy Android Development] maniac103:
Permissions 0660, owner system, group system

I'll check it.

'telephone' should read 'phone blacklist' ;)

Gesendet von meinem MB525 mit Tapatalk 2
[Defy Android Development] [] AL []:
Wow thanks!. Although, my new phone battery seems to be doing OK for now on this issue, I still saw small drops @~ 30% marks and the more I use recovery (to backup/restore), the more it seems this happens... so I will sure try it out. I though I read about those permissions not set right in one of those million thread about batt drops, but I was just too lazy to try it out and honnestly thought that it couldn't be so "simple"...

Thanks also for this; I greatly appreciate your quick response on this - cheers and thumbsup.

OK a few other things rapidly:

1- Bitrates: after a few days of testing [still no new SD... backordered when placing the p/o], I seem to be settled for this: target (average): 3.75Mb/s - max: 5.5Mb/s (4/6 froze a couple times - but it was close to be fine)

2- there seems to be something going on with recovery for me. I mentioned a while back that TWRP touch recovery stopped working [and I stopped using it since then] and throwing errors at me and made the whole recovery unusable. Well now, it seems that I can no longer installed zip patches!! With every new build, I always make myself an fix zip [where I put extra stuff like ringtones, bootanimation, the VoiceSearch that actually work with CM7, the transparent stausbar tweak to SystemUI.apk, etc.]. Well today, I've tried to reinstall the Sep 27th nightly and then my patch for that nightly and I got an error - something like this:

...
Installing update...
E: Error in /path/file-signed.zip
(Status 0)
Istallation aborted

The funny thing is that I did install that exact same patch on that nightly before; so why it stopped working now? The proof is that I even restored a nand backup of that build where I previously applied that patch and I have tranparent statubar, but if I go in recovery and try to re-apply the zip, I get the error again... really bothers me. I;ve tried another cwm patch earlier today and got same error but then thought I did that patch improperly...but I don't think so now... In fact, tried it two times with two different updater-script that should have worked (1 using just package extract and another using busybox...) So I don't know what's going on here and I'm afraid to lose the ability to flash my own cwm patches...

3- A very tiny detail here, but since the new FM radio is pretty much your baby... [thanks a lot for that also btw]. I was wondering if you'd agree with me that the stereo icon [see pic - the word "stereo is actually something I added in my blue themed radio] should not appear by default when there is no signal reception.?? In fact, it almost only goes away when we're on a badly tuned station..

I understand that the 'system' might be treating noise as stereo since the signal is then quite different between the two channels (L/R) and it might be complicated to "fix" though. Anyhow, that is just a little observation and no big deal at all - just a little strange.

EDIT: I've just tried with the Oct 02 build and same problem: I can install the nightly, but I can't install my patch.zip like I did a 100 times before...:crying:
[Defy Android Development] FINEEEEE:
maniac is necessary calibrate the battery again? on your new build?..what happend if i was using your old build..and upgrade for your new build?.. ;)..
[Defy Android Development] juan296:
Maniac,are you sure that your fix is working correctly? I mean, I was testing today with some links and I believe that we have problems still.

Page test: http://www.mulliner.org/security/telstop/test.html

Arch Linux User ..
[Defy Android Development] kapil_dheer:
Did anybody face any issues for the new defy+ nightly? After install, the phone hot stuck at bootlogo after the blue and green led.

Again going to the bootmenu, it have some error....don't recollect what...

Afterwards put back the Nandroid of earlier release.....followed all procedures the normal way.
[Defy Android Development] maniac103:
That test page looks absolutely fine to me, no IMEI window is appearing. It's desired behavior that the digits appear in the dialer. The problem was that they were dialed without confirmation.

Gesendet von meinem MB525 mit Tapatalk 2
[Defy Android Development] [] AL []:
Yo, well I'm sorry to say that with anything past the August 27th nightly, I had problem with the recovery; I cannot reliably flash my own cwm updates nor install the TWRP touch recovery.

First pic: error returned after trying my zip on Oct 2nd (defy)

2nd: after trying to install TWRP (seems to install fine, but..) and going back into recovery.

Luckily, nightly build installs seem to work OK.

So I went: Nordic sbf --> Aug 27th build --> restore nand of Sep 27th build--> Aug 27th nightly install--> reboot and finally, my cwmr zip for that build installed properly.

I was holding my breathe because that nandroid (1.2GB in size) is the only one I got for this new phone...

So I guess to reproduce this, just try to install TWRP and go back to recovery.

Just be warned that both custom or stable recovery will no longer work and it will be sbf flashing time...

[or bootmenu adb push?- I didn't try that though...]
[Defy Android Development] kapil_dheer:
I have this problem ever since I got to cm7 . I used to use night mode and it happened on each restart.

It had render effect widget which I used to apply after every restart.

Thought it is As is. Will be great if such settings stick.
[Defy Android Development] maniac103:
Hmm, 5.5 max may be a little too low for 720p recording on Defy+. Let's wait for your new SD card.

What version was 'that nightly before'? If it's before Sep 10th, the problem very likely is the TLS support; updater-binary probably needs to be recompiled for TLS support.

Can you check whether it works when taking updater-binary from the last nightly and putting it into your update.zip?

The mono vs. stereo state is signalled from the (proprietary) Moto FM stack, so if the symbol appears, the stack very likely has 'said' there's stereo reception, in which case I can't do anything. I'll check it again, though.
[Defy Android Development] prashjack:
can flash a defy+ cm7 build on defy red lens ??if so which kernel to flash??
[Defy Android Development] [] AL []:
yep-yep: my goal was only to get 'wide' problem -free (on this card...) Sorry, I might have attached a media_profiles.xml where I also lowered the HD max bitrate by mistake (and left it like so by lazyness...).

Well from a few buid comments I kept and what I can remember now (I'm getting old and forgeting, + it was a pretty hectic day here today - I had to nand restore under the shower to give you an idea...), here's the chronology of events again:

Aug 27 build: all fine

Sep 7 build: TWRP crashed big time when I first accessed recovery - result: unusable recoveries + sbf flashing

Sep 23-Quarx: limited testing / seemed all fine- touch boot menu is cool but no more [no landscape lock, no ringer volume change mute]

Sep 27 build: did not install TWRP and things were fine with my cwm patch [-was testing camera..]

On Oct1, created [my unique] nandroid backup from Sept27 build

Today:

- Installed Oct 2nd: cannot install my cwm patch so wiped cache and Dalvik (as usual) and re-installed Sept27th nightly + my patch: no go!

- Full wipe and restored Sept 27th nandroid, booted up, back to recovery and then tried my patch on top (already effective from the nand restore but reflashed it anyway as a test): no go!

- Then right after: rebooted, wiped cache+Dalvik and installed TWRP: seemed to install fine but failed when rebooted to recovery - same result/errors as with Sept 7 nightly.

- Then I flashed Nordic sbf, Sep 27 nightly, nand restored and finally Aug 27th nightly + patch.

-->> So the answer is it was Sept27th nightly that the patch worked before but failed today.

-->>>I really want to help here and I will try my Oct 02 patch again including the nightly's update-binary, but just not today...

I do not feel like repeating the steps of 3 lines above again before going to bed... ;-P

Dang I hate that "P" word... :p - thanks for the reply and interest in it anyway.

Cheers!
[Defy Android Development] ktmbikerman:
This happened with CM 10 builds after a certain date too. You can get recovery back by copying the recovery folder from a cm7 zip into the correct folder and setting the permissions.
[Defy Android Development] maniac103:
I've explained the reason above already ;) That certain date was the TLS support introduction in CM10, so the behavior of CM10 and my CM7 should be exactly equal now. That means copying recovery folders shouldn't do anything now. Using the new updater-binary, as mentioned above, should help, though ;)

Gesendet von meinem MB525 mit Tapatalk 2
[Defy Android Development] [] AL []:
Just did and it didn't work.

I got error and installation aborted again; now with Status (7) [- as oppose to (0) without the new updater-binary].

From my updater-script comments, I can see that it stops right at the mount system step.

So still no go for recent nightly... at least no sbf flashing required this time....back to August 27th.
[Defy Android Development] maniac103:
That's actually better. It means updater-binary ran instead of crashing (error with status 0 means it crashed), and 'just' the script failed for some reason.

With return code 7 there should be some 'script aborted' message with a reason. What's that reason?

Can you upload your zip somewhere so I can have a look at it?
[Defy Android Development] [] AL []:
I did not see anything more than what I wrote...no reason given.

Sure, here it is (the last one with the nightly's update-binary).

I removed a (~8MB) bootanimation.zip from the /system/media/ folder and resigned it in order to be able to attach it here though.

[..and re-signed it with apkmanager as usual]

It's not the best updater-script - I know [please don't flame me], but it worked for me probably over a 100 times before...

Cheers,

Attachment removed since script was wrong and there was at least a font which I do not own copyright/license...
[Defy Android Development] maniac103:
For me, the error message is pretty clear: ;)

mount() expects 4 args, got 3

I wonder how that ever worked - the install script parsing code wasn't touched in ages.

The CM update script does this:

mount("ext3", "EMMC", "/dev/block/mmcblk1p21", "/system");

and the GApps do this:

run_program("/sbin/busybox", "mount", "/system");

both of which should work.
[Defy Android Development] [] AL []:
OK! thanks I'll try this next...

I did re-check older fix and the script was the same; so yes very strange that it worked for so long and now get the (7).

What about TWRP touch recovery?

Why do you think that it stopped working lately (since Sept 7th I believe - but I did skipped a couple install or nightly)?

Is that more likely to be because of the TLS support?

So from now on (if this was the issue), I should keep using the update-binary from each nightly within the patch?

As always, thanks a bunch for all your help.

Edit:

everything went fine with the proper mount script (and update-binary) so thanks for that. Sorry to have been so alarmist about it and I really don't care much about TWRP... At least we know that your builds now ask for properly written update scripts.

v1.7 of WizAL theme just uploaded!

I'm pretty happy with my (very) simple tweaks to the CM7 camera; go check it out!
[Defy Android Development] maniac103:
Yes, definitely.

No, you can use updater-binary from any post-TLS nightly. In other words: You can keep using the updater-binary that you're using now.
[Defy Android Development] kryptonitiko:
Anybody tried maniac's build for fix battery drop?? Have you already got battery drop? :/
[Defy Android Development] ziki:
I just had the battery drop with cm-7-20121002-UNOFFICIAL-jordan-signed.zip build (more or less from 35% to 19%)

Yesterday I came back to CM7 after a short jump to CM10 (good stability, but....too slow for me).

Flashed the zip and charged to 100% for 1-2 hours. I did not execute a battery calibration.
[Defy Android Development] patriiice:
I did, and it seems to be fixed! I have just ended a discharge cycle and didn't notice the 34%-19% drop I used to have. I will see in the following days but it's on good way.
[Defy Android Development] maniac103:
Please note I didn't say

all

battery drops are fixed. I fixed only one reason (wrong permissions of the battd files), but the other one (aging battery) obviously remains ;)
[Defy Android Development] diogo.sena:
@maniac103: will you join the kernel development?
[Defy Android Development] eboIa:
Hello and sorry for ask my question but search for the solution more then a year on every channel without any usable problem solve.

I have 5 Defy at my company but all had this problem and simply could not help on it.

With latest (or earlier) official MIUI and with CM 7.x also. Usually half of our outgoing calls simply could not going out for first time. Just the caller interface without ring out. Silence. When we stop the call immediately after the second try is usually successful but some times we need more try. This is the only problem but with all devices with MIUI and CM also. Of course with any type of reset, restock, etc. At the end we get this thing always. Baseband is ok, I'm in Hungary with Europe baseband, but we tried the others just for sure. Nothing. Basically everything working but this needing of multiple try of outgoing calls simply make me crazy.

Anybody know the problem our maybe a solution for it?

Lot of thanks in advanced.
[Defy Android Development] businessman9:
my wifi cant connect wpa/wpa2 on 20120921 & 20120923 defy+ nightlies

it was ok on 0506
[Defy Android Development] kryptonitiko:
if I have a red lens defy, Should I try the defy+ build or the defy one?? With the defy+ it seems that accelerate the drop, now I'm trying the defy one! :confused:
[Defy Android Development] FINEEEEE:
Battery dropa is still alive for me xD...of 29 to 20 :)..sometimes 30 to 19...:D...what permissions i need change.?....i just have the maniac build for the defy+ on my red lense

Desde cualquier lugar de mi ciudad con el 4x4 de motorola
[Defy Android Development] krkdesigns:
Try changing the Security Encryption to WEP and try once.
[Defy Android Development] ofmb:
New build by maniac103.

Changed mainly the render effect handling.

https://github.com/maniac103?tab=activity

P.S would love to try a build with Qkernel :P
[Defy Android Development] popadic022:
is there any difference betwen new maniac103 and fuzz relese?
[Defy Android Development] maniac103:
In fact, quite a few of them. Features that are in my builds, but not in his:

Automatic download of GPS helper data

Adjustable render effect color

Configurable root access (apps only / ADB only / both / none)

Optional boot menu PIN

Option for completely disabling the phone black list feature (so that long pressing end call doesn't throw black list dialogs anymore)

MIUI-like battery bar

Revamped FM radio app (with lockscreen integration, system-wide volume control and a few additional options)

includes Motorola's voice dialer

His feature list is here. Some features of that list are also in my builds, as I wrote the code for a couple of them. Features that also are in my builds include:

Bluetooth: Always follow the user's preferred contact display name format

Make some aspects of VCard generation subclassable (belongs to the former)

Bluetooth: Send local time, not GMT, in timestamp

Calendar: Allow custom calendar reminder snooze times

Camera: Allow focus sound muting

Contacts: Add format number option to dialer

Contacts: Add individual contact call history and show groups yes/no setting on call log

Music: Let music player fade smoothly when playing/pausing/seeking

Add option to disable volume key beep sounds

Toggling the flashlight from the lock/pattern/sim unlock screens (I have implemented this differently, allowing to reconfigure not only long press menu, but also for menu and search; and to also assign different actions, such as controlling the music player and toggling the ringer mode)

Add possibility to change the style of lock pattern screen

It's up to you whether which of the feature lists you find more compelling :)
[Defy Android Development] popadic022:
thx, just 2 question. all new updates (your or fuzz) contain changes from "20121007 cm7 nightly for jordan"? i have mb526, stock 2.3.5 and i want to update to cm7.2, do i need to apply any battery fix or kernel? i have rooted phone with 2ndinit. And 1 stupid question :), is the battery life (normal use), gps, wifi, data connection,...works good on your rom? cheers
[Defy Android Development] maniac103:
Sure.

At least not for my builds, I don't know about FuZZ' ones.

For me, everything is fine, as is for most other people.
[Defy Android Development] popadic022:
thx, i will try.
[Defy Android Development] LeopardSurd:
But where can I download the Defy+ build from maniac?
[Defy Android Development] Gazm4n:
Here you go: https://github.com/maniac103/android_device_motorola_jordan-common/downloads
[Defy Android Development] LeopardSurd:
Thank you!
[Defy Android Development] snaky90:
I have a defy with red lens, What version I have to install, Defy or Defy Plus?
[Defy Android Development] Anands3:
Defy plus
[Defy Android Development] measel:
You can install both.

Defy+ has the advantage of 720p but

the Defy- has the advantage of thorough testing by Maniac. He doesn't own a Defy+.
[Defy Android Development] Steveletack:
You can only install the Defy+ Version if you have the gingerbread kernel.

If youve got the Froyo kernel install the normal version
[Defy Android Development] G3Sidhu:
curious.....

http://download.cyanogenmod.com/?type=stable&device=jordan

is that^ build by maniac?

how did it got into stable section?.... isnt it should be in the nightlies section?:confused:
[Defy Android Development] measel:
Hm maybe you're right - thouht it was a new official version. Maybe Maniacs builds are the new official builds?!
[Defy Android Development] G3Sidhu:
but the build on cm official site is of 102 mb and the latest build from maniac is around 116mb...

which rom to flash? :confused:
[Defy Android Development] LeopardSurd:
Great build anyway, just installed the last unofficial Defy+ build from maniac and works „ausgezeichnet/wunderbar”! Hope it is quite stable so I'll test it few days until a new install.
[Defy Android Development] G3Sidhu:
u installed from cm site or from maniac's repo?
[Defy Android Development] maniac103:
It's not my build, it's a CM one. I merged Defy+ support into CM today, and this build was to test whether the build still works.
[Defy Android Development] SlaveSrbija:
How to change fps from 12 to 30 on video rec in Maniac's build????
[Defy Android Development] popadic022:
whether it will be the official version of cm7.2 for defy+?
[Defy Android Development] LeopardSurd:
That would be great! :)

I've installed Defy+ build from maniac repo. Still nothing to complain.
[Defy Android Development] popadic022:
check this, defy+ stable release?? link http://get.cm/?type=stable
[Defy Android Development] androidtester80:
+1

cyanogenmod got hacked ? :laugh:
[Defy Android Development] popadic022:
maybe defy+ gonna get official release cm 7.2 i hope :) i think , maniac103 last release is very stable.
[Defy Android Development] snaky90:
720p only rec with 12 fps ???
[Defy Android Development] maniac103:
This build wasn't supposed to appear as stable (I wanted it to appear as experimental), but a stable version will come eventually.

If anyone of you who owns a Defy+ could try that build, I would appreciate it.

Gesendet von meinem MB525 mit Tapatalk 2
[Defy Android Development] popadic022:
Is this version for defy plus "https://github.com/maniac103/android_device_motorola_jordan-common/downloads" same as "http://get.cm/?type=stable". i download and install version from 1st link. its good, but it seems the battery drains little faster than on stock rom, i fully charged phone on stock rom, then install your rom, and after 12hours (almost in standbuy, 2g, no wifi, ....) battery is 65%.
[Defy Android Development] SlaveSrbija:
I have defy+ and i try your build (previosly i was on quarx 24.09. build) those two builds almost are the same very fast on 1.2 OC and very responsive great work :good: ,only thing that bothers is 12fps.
[Defy Android Development] popadic022:
SlaveSrbija - Do you have battery drain on your defy+ with maniac103 new rom? pozdrav
[Defy Android Development] G3Sidhu:
sorry for post....:o
[Defy Android Development] SlaveSrbija:
Actually, when I realized that both rom-s are the same I back to quarxs build (too lazy to back all aps and customized settings) where no battery drain average use 2 days...pozdrav!
[Defy Android Development] popadic022:
my battery on my defy plus drops from 69% to 49% after 3 hour in standbuy. :crying:
[Defy Android Development] Justch:
maniac103 CM10 is almost stable, why don't u join cm10 developement?
[Defy Android Development] oSandmaNo:
There are many who still need cm7 ;)
[Defy Android Development] popadic022:
maniac103 last cm7 i stable, fast,...but it drain battery realy fast (mb526). and "bug", when disconect phone from usb its show message "com.android.media.stopwork,.." always. Is there any fix for battery drain drain?? i dont want to change rom if i can fix this.
[Defy Android Development] measel:
Please: maniac103 (and all the other devs) need logcats for easy debugging. So, try attaching a log.

Other ideas:

go into Airplane Mode and check how much battery that sucks per hour

check Cpuspy if deepsleep is ok

use Betterbatterystats to find wakelocks if the above shows strange behaviour
[Defy Android Development] maniac103:
Because

The definition of 'stable' varies between people, and CM10 doesn't fulfill my definition of it (main problem being the lack of RAM and the camera issues)

I only have one Defy I use as a daily driver, so I need a phone that fulfills my definition of stable

I seriously lack time that's needed for following the quick CM10 development
[Defy Android Development] popadic022:
cpuspy and after reset stats