[JB:CM10:HYBRID] ParanoidAndroid 2.5.3 for Bravo & Defy 2nd Kernel

skeevydude · Sep 4, 2012

Kayant said:
@skeevy420

Did you still have the rules in vendor and common device trees?? Maybe that's what is causing the battery problems...

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 --

Code:

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)

Code:

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.

Kayant · Sep 4, 2012

skeevy420 said:
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 --

Code:

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)

Code:

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

Not too sure about this one you need to ask quarx about that

skeevy420 said:

Code:

# 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

skeevy420 said:
EDIT: Also posted this in the group.

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

Snikeer · Sep 5, 2012

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).

sebx_g1 · Sep 5, 2012

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?

J_M_V_S · Sep 6, 2012

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?

skeevydude · Sep 6, 2012

J_M_V_S said:
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?

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.

Snikeer · Sep 6, 2012

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.

AnkurBedi · Sep 6, 2012

skeevy420 said:

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 --

Code:

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)

Code:

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.

1)

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

OR

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

2) YES

:good:

maguz01 · Sep 6, 2012

thanks, im triying this rom i had the 2.00 of brajesh and the battery was great, almost the double duration than cmx

skeevydude · Sep 7, 2012

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:

deffyplus · Sep 7, 2012

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

skeevydude · Sep 7, 2012

deffyplus said:
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

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

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.

deffyplus · Sep 7, 2012

skeevy420 said:
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

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.

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?

skeevydude · Sep 8, 2012

deffyplus said:
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?

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.

skeevydude · Sep 8, 2012

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).

nziria · Sep 8, 2012

skeevy420 said:
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).

when it's ready we retrieve it on goo.im?

just install over old PA? wiping only cache and dalvik?

x-Moi-x · Sep 8, 2012

Every time I restart the phone it enters me to the bootloader first.
Can I change it?

nziria · Sep 8, 2012

x-Moi-x said:
Every time I restart the phone it enters me to the bootloader first.
Can I change it?

i think you have to goo in 2ninit Boot and chanche something here

skeevydude · Sep 8, 2012

nziria said:
when it's ready we retrieve it on goo.im?

just install over old PA? wiping only cache and dalvik?

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.

x-Moi-x said:
Every time I restart the phone it enters me to the bootloader first.
Can I change it?

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)

nziria · Sep 8, 2012

nice! i can't wait!:good:

[JB:CM10:HYBRID] ParanoidAndroid 2.5.3 for Bravo & Defy 2nd Kernel

Inactive Recognized Contributor

Senior Member

Member

Senior Member

Senior Member

Inactive Recognized Contributor

Member

Senior Member

Member

Inactive Recognized Contributor

Senior Member

Inactive Recognized Contributor

Senior Member

Inactive Recognized Contributor

Inactive Recognized Contributor

Senior Member

Senior Member

Senior Member

Inactive Recognized Contributor

Senior Member

Similar threads

Top Liked Posts