yashsingh1/xdaforums huggingface dataset:
[Defy Android Development] abhirulz94:
Thanks man for the reply but i can't find the latest build anywhere.

I would be grateful if post the link. :)
[Defy Android Development] UncleDan:
http://xdaforums.com/showpost.php?p=47074377&postcount=777
[Defy Android Development] juancollado2003:
corrupt zip file

hi, i've downloaded bravo versions of this rom 3 times and always is a bad ended zip file, a corrupt zip file, any help?
[Defy Android Development] UncleDan:
This rom is very outdated. On my mirror you can find the Defy versions but no clue if Bravo version is still around.
[Defy Android Development] ProfesorYeow:
Thanks for the mirror, I download for my defy+ from your link.
[Defy Android Development] AndroidJohny:
I found Defy and Defy + version + Paranoid Android Kernel. Here it is the download links:

https://www.mediafire.com/?me70ol9jdr7sn

And in my side, Paranoid Android works perfectly for me, and i don't care about Nightly Cyanogen Mod 11 Kit-kat 4.4.4 Quarx Rom, so many reasons.
[Defy Android Development] @ARC-S@:
Thanks for the download links! Didn't think I'd find it at all haha

If you're wondering why on Earth am I flashing this on a Defy in 2018... My dad has a Moto X Pure but he prefers older smaller Android, plus Defy is rugged haha.

Thank again for the links and the dev for the hard work!:victory:
[Defy Android Development] Iks Pipl:
Thank you!!!!

Сommunity of Motorola is immortal :cool:

Yeah Moto Defy in 2k18 :laugh:

UPD:i can`t see kernel in this link
[Defy Android Development] skeevydude:
It is the problem exactly. I checked, but I had the file sizes backwards in my head. It'll be resolved in the next release. Two quick questions --

Can expressions like *mb526 be used in the makefiles? Like in "adb push PA*.zip".

ifeq ($(TARGET_PRODUCT),*mb520)

instead of

ifeq ($(TARGET_PRODUCT),cm_mb520)

Can more than one else be used and can ($(TARGET_PRODUCT),cm_mb520) be added to the else lines?

# Specific binaries
ifeq ($(TARGET_PRODUCT),cm_mb520)
PRODUCT_COPY_FILES += $(vendor_path)/bin/opprofdaemon_mb525:system/bin/opprofdaemon
PRODUCT_COPY_FILES += $(vendor_path)/bin/battd_mb525:system/bin/battd
else ($(TARGET_PRODUCT),cm_mb525)
PRODUCT_COPY_FILES += $(vendor_path)/bin/opprofdaemon_mb525:system/bin/opprofdaemon
PRODUCT_COPY_FILES += $(vendor_path)/bin/battd_mb525:system/bin/battd
else ($(TARGET_PRODUCT),cm_mb526)
PRODUCT_COPY_FILES += $(vendor_path)/bin/opprofdaemon_mb526:system/bin/opprofdaemon
PRODUCT_COPY_FILES += $(vendor_path)/bin/battd_mb526:system/bin/battd
endif

EDIT: Also posted this in the group.
[Defy Android Development] Kayant:
Not too sure about this one you need to ask quarx about that :)

I think it should be ok since all the rule does is check what product is being made and tells it to copy the right vendor files for the device as it's the common tree and some stuff are specific to each device...... or I may be totally wrong :p
[Defy Android Development] Snikeer:
I'm having 2 annoying bugs:

On Stock UI (haven't tried others, I'd rather sticking with this one), sometimes upon reboot my status bar will disappear and the wallpaper will change to solid black on it's own. The wallpaper can be set manually to what it was previously, however the status bar won't come back. Changing from/to Expanded Desktop does nothing. Since I'm using Apex Launcher, also tried to use the Toggle Status Bar option from it, no success as well.

The previous bug is mild imo, the worst one is the following:

Sometimes upon entering on recovery it'll get changed back to stock recovery on it's own. I'm not sure how this happens, might be upon pressing Vol- on reboot. Seems like restarting with the Recovery option when PA is already alive and kicking works erverytime (again, can't confirm. Everytime it got changed to stock I had to reflash sbf, and install everything from scratch, since I couldn't just flash PA again. Therefore, I didn't try to reproduce it, being such a hassle to recover. However it happened 3 times by accident).
[Defy Android Development] sebx_g1:
Well it is very nice rom, after fixing problems with bootloop and screwed battery on my own it is most interesting rom for Defy. Can't wait for next builds :thumbup:

I have suggestion for developers why not to save rom settings backup on sdcard to save them for later use eg. after sbf flash?
[Defy Android Development] J_M_V_S:
First of all, thank you skeevy420 for picking up the work from brajesh.sharma87.

I've tested the last release from brajesh.sharma87 and the last release from you and the phone feels really laggy now whereas brajesh.sharma87 version was pretty fast! Do you know what could be causing this? I'm on a MB525 Red Lens defy using your Defy ROM version. Maybe I should try the Defy+ version? Any ideas anyone?
[Defy Android Development] skeevydude:
The first release was to test my build scripts and identify problems. Now that I know them I'll be able to adjust as necessary. I'd already have new ones out but I've just been busy these past three days. With my Dad on extremely light duty and no helper on my job right now I'm just either busy or tired -- the 105 temps don't help much either.

If all goes well I'll be able to get all the merges done and some compiles starting tonight. I'd like a new build as well, I don't particularly care for this release compared to my last 2 (on the Bravo).

I haven't had that stock recovery bug.

The biggest reason why you can't save the rom settings on flashes is if new features are added (options in settings menu for example) your sqlite table will be different and values might not correspond to the new ones. PA has an option to back up its settings and Google syncs back most of my settings on a new flash.

While a pita if you don't know what your looking for, you could checkout some of the boot scripts in WIUI and Pikachu. One of them writes values to the sqlite database -- you could make a similar script with your preferred settings.
[Defy Android Development] Snikeer:
Just giving some feedback on my previous bug, regarding the stock recovery, just now I've had another one of those.

Everything was fine, and I simply rebooted my phone, nothing special here. However it got stuck on PA animation, on a loop. I tried to get in recovery, so pulled off the battery, annd turned it on while pressing Vol- and there it was. The good old triangle with an "!" in it, signaling stock recovery. Now, once again, I'm stuck on the loop. Data factory does no good, so the only solution is reflashing a full SBF, and then later applying the ROM.

I own a red lens defy, using the Defy+ build, with gb kernel.
[Defy Android Development] AnkurBedi:
1)

ifeq ($(patsubst cm_%,%,TARGET_PRODUCT),mb520)

OR

ifeq ($(TARGET_PRODUCT:cm_%,%),mb520)

2) YES

:good:
[Defy Android Development] maguz01:
thanks, im triying this rom i had the 2.00 of brajesh and the battery was great, almost the double duration than cmx
[Defy Android Development] skeevydude:
Starting Bravo PA 2.10 compile. If all goes well expect new Defy\Defy+ roms either really late tonight or sometime tomorrow. It takes around 4-5 hours per rom to compile and since I have to build for my phone first ya'll gotta wait :)

Next release will have the battery issues fixed, no patches, and a few addons -- gonna replace smartass with V2 since it works better, gonna use the DX GOV pack SIO init script since the overclock.sh method doesn't always work as expected,

I'll be glad once today is over -- it should be the last of the 100 degree plus temperatures (with 87% humidity -- that's what makes it so bad). After today we have highs in the mid to upper 80's. Hooray. :laugh:
[Defy Android Development] deffyplus:
hi all,

just to ask some noob questions

what's about average battery life of ur defy with PA?

what kernel is best to use with PA?

how about 4.5.2-109_DTH-22-kernel by walter79

i have strange bug...but I'm not sure that is bug:

when in call switch on speaker, my mic switch to camera mic on back? and my caller hears me very poorly

MB526
[Defy Android Development] skeevydude:
I don't have that problem on my Bravo and all I use is speakerphone -- I have to since a Verizon music dial tone blew my earspeaker :(

I'm not sure the about recommended kernel for PA Defy Plus, but it should be the same one that's recommended for CM10, which ever one that is :p

For an update -- I'm on the last part of the compile process for the Bravo's PA 2.10. I ended up canceling the earlier compile, adding in Quarx's latest pushes to github today, and started over. It should finish in an hour or two.
[Defy Android Development] deffyplus:
Thanks for quick answer, :good:

i have one more question...i have seen on xda and i have the same problem when i start recording,after apx 10 sec the sound stops on recorded material...during recording there is no indications that something is wrong..is that also the bug in this ROM? :confused:
[Defy Android Development] skeevydude:
Haven't used the camcorder with CM10 for more than 5 seconds -- just long enough to see if it'll work... I'm using Nadlabak's camera app (same as in Quarx's CM10 builds now) so hopefully that'll fix the bug. I'm on the very, very last stage of the compile -- optimizing the apk's right before it make the rom. I'll be able to flash the rom in about 15 minutes and I'll test it then....although I'll be testing on a Bravo which has different camera libraries than the Defy (ours is a 3m soc green lens with no flash).

Oddly enough I'm currently running the latest CM7 Defy Nightly from CyanogenMod.com -- a Bravo user was using it and said it had very good speed but he couldn't get the camera running. I flashed it a few hours ago and had camera in about 15 minutes -- it helps having all the different revisions of the camera drivers when porting. :silly: What's funny is I used camera libraries from around January, the newest ones didn't work....I really need to update my CM7 repos and release a new Kang.

I'd also like to get back to MS2. Its never fully worked on the Bravo -- it doesn't jive with our camera libraries. Stock Froyo drivers cause it to freeze on boot and the CM7\9\10 drivers just don't work. I suspect I need to decompile framework.jar and replace its camera code from the Bravo's stock framework.jar. I'd also like to remove MS2's phone home command for tethering -- that'll benefit Defy and Bravo users in America (especially AT&T customers like me)

WoopWoop compile finished while I was typing this....later.
[Defy Android Development] skeevydude:
Finally installed and working great so far. Haven't tested battery life since its been on the charger since flashed. Camcorder recorded and had sound for 18 seconds. The first boot was choppy and laggy during the Google Sync and app install. Smooth on the second boot. SmartassV2 replaced smartass; sio fixed in the bootmenu and tweaked like in the DX pack; the updated PAPreferences has some nice new options -- set default dpi for all apps depending on work space to name one. All the battery issues are resolved now so it won't be an issue for the next release.

Gonna start on the Defy and Defy Plus builds. They'll be done in the morning, but I won't be able to upload until I get off work tomorrow (Bravo users aren't getting until then either so don't feel left out).
[Defy Android Development] nziria:
when it's ready we retrieve it on goo.im?

just install over old PA? wiping only cache and dalvik?
[Defy Android Development] x-Moi-x:
Every time I restart the phone it enters me to the bootloader first.

Can I change it?
[Defy Android Development] nziria:
i think you have to goo in 2ninit Boot and chanche something here
[Defy Android Development] skeevydude:
Yes to goo.im, you shoud be notified that a new version is ready.

You don't even have to wipe the cache\dalvik, just reboot and flash :) -- I added that in to the installer to save on volume\power button presses.

That only happens to me when I change PAPreferences -- I figured it was to remind you to wipe cache\dalik afterwards.

Well, Defy is done, just started Plus. I had a mile long command in terminal to wipe, compile, copy defy, wipe, compile plus; but I left out an "i" in the Plus compile command -- it was on the edge of the screen and spilled over to the next line so it looked like i had put in ./rom-build.sh.

I gotta go to work, I'll upload them when I get home if no one is playing games here (with the capped upload speed I can't upload when PSN is active)
[Defy Android Development] nziria:
nice! i can't wait!:good:
[Defy Android Development] skeevydude:
Bravo, Defy, Plus Builds online.

For a change log, go to github and view the commit history. Its a pita to keep up with everything Quarx, PA, and I may add to the rom from release to release. Download link is in the first post as usual.

For bugs look at the bottom of the second post. I've found a few, but they're nothing even remotely serious.

That said, PAPreferences has been updated and has a few new features like setting layouts and dpi for all apps at once :), some translations, replaced Smartass with V2 (use the smartass settings in the bootmenu to tweak V2), fixed sio so it loads by default -- noop will load if set to 0 (it was cfs before), the new touchscreen driver; I'm tired and I don't feel like trying to remember more :p. It was a long day today & I'm tired.

Battery life is somewhere between Stock Froyo and CM7 depending. Wifi connects fast, but I use a static IP and that's probably a factor (haven't tested connection speed with DHCP yet). The Bravo doesn't have that 10 sec camcorder audio bug (not sure if it did before) so hopefully the Defy\Plus doesn't have it now either. It runs a lot smoother than the last release.

I asked the PA team about the reboot to bootmenu issue; haven't had a reply to the forum post yet. I'll let you guys know when I hear something.
[Defy Android Development] hunyadia:
my phone always forgetting gapps minimal pack (ie no play store, no sync) when I change from cm10 to pa or back to cm10. I have to install gapps again to work properly. Is it normal guys?

I am using gapps-jb0726-min pack.

Thx

defy green powered by jb
[Defy Android Development] niksy+:
It is if you're wiping data :silly:

Skeevy, thanks for the update! Downloaded and hoping I'll find some time to test it today!
[Defy Android Development] nziria:
can'w wait! + Strange bug on 2.00

i'm downloading the rom,can't wait.

i have a strange bug appears yesterday:

i have a game (go go goat) that stopped working.i uninstalled it and downloaded it again,at the installation it says that i hane not space,but it's worse. if i install another app, even if if are bigger than go go goat,it install normally >-<

i try this new rom to see if the problem is solved.
[Defy Android Development] abhi9029:
It takes above 400MB+ RAM. It really slows down mobile. Is there any solution for this?
[Defy Android Development] skeevydude:
If all you did was wipe dalvik and cache, then there shouldn't be a problem -- however, I noticed a problem with certain gapps not remaining on the system after a dirty upgrade. After looking over the gapps backup\restore script included with all roms I noticed talk was missing from it (that's what made me notice the gapps upgrade issue in the first place) so I went through the gapps script and added all files from the full jb gapps to be backed up and restored. Install this w\o flashing gapps and let me know if that issue was fixed for you, if not, I'll go through the minimal gapps and add in all of its files.

I've had that bug appear on almost every rom (meaning all roms I've used) so far at random. You have to go to /data/app and make sure it was really removed and /data/data and delete its folder from there; that usually fixes the issue (wiping cache and dalvik afterwards helps too) It first happened to me with PowerAmp on CM7 (and 7 is the king of stability and crap not going wrong, so if it'll happen there it'll happen on any rom)

Use HWA Selector to switch apps from HWUI to software

Use Zepplinrox's V6 Supercharger and KickAss Kernelizer

Remove all the live wallpapers from /system (all specialty wallpaper apks eat ram just to be an option in the menu; CM Wallpapers, PA Wallpapers, all the random Live Wallpapers like Galaxy4, PhaseBeam, NoiseField, etc)

Don't use a wallpaper.

Limit the Widgets you use.

If you're on Froyo kernel its set to run at 300@20\700@42\1000@54 -- if its not at those values then go to the overclock setting in the bootmenu and select "Use Default Values" and I'll set all the values to custom levels I set for all the governors and Vsels. Defy Plus has the custom governor settings and is clocked at 300@20\600@40\800@48\1000@54

In settings menu:

Performance>16 Bit Transparency

Performance>Memory Management>Allow Purging of Assets

Developer Options>Background Process Limit -- use no background proccess (not recommended) to at most 2 or 3 (may make things start up longer)

I've removed all the Live Wallpapers except for Live Wallpaper support, enabled 16-bit transparency, and Purging of Assets and I'm running just fine.

I also use Holo Launcher HD Plus instead of Trebuchet. Seems to run better on PA, at least for me. Try Holo Lanucher HD free from the market and see if it makes it better.
[Defy Android Development] nziria:
can you post Here the 2 scripts? kickasskenelizer and the latest v6 supercharger?

i tried v6 on msginger and it always gave me an error on the read only memory,i don't remember....
[Defy Android Development] skeevydude:
http://xdaforums.com/showthread.php?t=991276

KaK is in the recent files link. You also gotta read post 2 since this is a JB\ICS rom.

I'll also add that 3gTurboCharger's Unknown 1 setting works wonders for me; but those vary depending on your service provider so you gotta try them all and find the one that works best. The WifiAfterburner setting works well too.
[Defy Android Development] guffoe:
still using Quax build 02-09-2012 ke?
[Defy Android Development] aLeda:
skeevy what's Performance>16 Bit Transparency please ? :)
[Defy Android Development] skeevydude:
An option in Setings>Performance Settings>

Just lower quality transparency setting. By default it uses 32-bit transparency. 16 bit uses less color and alpha channels to do image rendering and will speed up drawing\rendering of graphics and images, but it may cause drawing issues (I haven't really noticed any and I always run PA\CM9\CM10 with 16 bit).

Google 16 bit transparency for more technical info about the subject.

@Guffore -- No, its based on Quarx's CM10 sources and PA's sources from the Date in the Name of the Rom. If you'd have read the first post you'd see where I listed the date and time of my last pull\sync before I started the compile process for all 3 roms. I'm not trying to be an ass, but read the first two posts. They cover that question.
[Defy Android Development] Kayant:
Read the first post --- it's built from source like CM10 there is no zip porting here..... ;)
[Defy Android Development] ldiomedi:
For some reason, after V6 script I lost status bar in every mod (phone, phabet,tablet). Will unsupercharg to see if it solve the problem
[Defy Android Development] pasha4ur:
Looked the picture. Very user-friendly interface.
[Defy Android Development] sebx_g1:
On my green lens Defy with newest version there is no backlight for capacitive menu button possibly this is a bug? Still many things to test...

---------- Post added at 08:34 PM ---------- Previous post was at 08:28 PM ----------

Try to enable and disable extended desktop from power menu. Lost of status bar occurs sometimes for me to without using any supercharge scripts.
[Defy Android Development] hunyadia:
I was also lost the status bar and phone gsm signal when I try to flash the circle battery mod. It wasn't surprise for me cos after the wipe cache and dalvik the reboot process said something like this: initializing .. %1$d/%2$d and the pa started without status bar and I got a process stop notice - can't remember what.

defy green powered by jb

---------- Post added at 07:33 PM ---------- Previous post was at 07:32 PM ----------

I do it w/o data wipe :p

defy green powered by jb

---------- Post added at 07:38 PM ---------- Previous post was at 07:33 PM ----------

Thx for the look around, I will try next time. :thumbup:

defy green powered by jb
[Defy Android Development] zyxwvut:
This rom is very snappy PA 2.10 defy+ build on regular red lens defy. Unfortunately battery problems are not sorted out! Upon fresh clean install the battery works perfectly, including charging and battery percentage display! Reboot the phone and it shows battery at 1% indefinitely. I charged for over 1 hour but still 1%. I do a data/cache/dalvik wipe and once again battery works perfectly. Reboot the phone and back to 1%. This can be reproduced every time.

Coming from Quarx CMX 0904 defy+ build on red lens defy. Clean install, data/cache/dalvik wipe (even though skeevy420 says cache/dalvik isn't necessary and built into zip)

And please don't tell me to flash a red lens battery fix. This is obviously not the problem!

Any thoughts?

EDIT: after unplugging the charger, at least shortly thereafter, it suddenly started working perfect again. It must just be a small glitch.

Aside from that this ROM kicks ass for sure! Thanks skeevy!!

EDIT 2: after a reboot the battery is once again back to displaying 1%. I left it alone for almost 2 hours thinking it would correct itself as it did before, instead the OS just shut down. Excuse my ignorance, for I don't follow Quarx github, but I remember reading that he was working on a new battery daemon. Since this PA is compiled from source, is this new daemon present in this rom? Could this be the cause of this strange behavior?
[Defy Android Development] venkatp:
IHi,

Happy to see another PA build. Thanks skeevy.

Few things i found odd in this build:

-As mentioned in previous posts talk was missing. Had to flash gapps again.

-Play store is force closing. Tried flashing gapps(26/7 & 17/7) but didn't work. It's a difficult thing to manage without play store :)

- Power amp is also force closing.

- I'm on multiboot 0.8 with PA on 2nd system. From boot menu, nothing is happening when i select 2nd system. I'm able to boot into PA only if I'm seeing PA as default boot. Don't know if it is an issue with multiboot. But didn't come across such problem in the last PA build.

Apart from that I'm happy to see camera in this build is same as seen in the screenshots in first post. But the icons are appearing very big. Many settings are overflowing out of the screen. Using camera is very difficult. How to change the dpi settings of camera? Didn't find camera in the app list of PA settings.

Happy with the speed of the rom. No lag seen yet. :) Will post if i find anything else peculiar. Thankful to skeevy (again :p )
[Defy Android Development] aLeda:
Heeeey, its curently based on 04.09 by quarx ? :)

// Sent from my Phone
[Defy Android Development] brajesh.sharma87:
Amazing man :eek:

You didn't even had to search, the answer is on the same page given by skeevy and also Kayant. Just amazing question. I am wondering how did u even root your phone. :eek:
[Defy Android Development] aLeda:
I am a pro.

Lol no sorry i didn't read enought the op lol

// Sent from my Phone
[Defy Android Development] bharaththeunique:
And now d audacity....:banghead:
[Defy Android Development] zyxwvut:
I'm sorry for OT, but this was the funniest thing I read all night!
[Defy Android Development] sebx_g1:
My last observations after 24h of use (on MB525 green lens , previous rom PA 1.992 - no data wipe .)

1) slow after flashing , after 3-4 reboots speed is no problem (strange a bit ?)

2) New PA settings works good , really nice utility . But sometimes I lost status bar then

two reboots are needed and extended desktop option disadble/enable to bring it back

- nasty thing need fix .

3) Battery life very good better than in latest CM10 builds (look @ pics really nice balance of deepsleep and battery drain ).

4) Menu hardware button have no backlight - its a bug I think .

more to come later ...
[Defy Android Development] brajesh.sharma87:
EDIT: ooops, I didn't read carefully before giving solution. :D