yashsingh1/xdaforums huggingface dataset:
[Bravo Android Development] raul1113:
So far:

No problem with bandbase, automatically detected

Camera ok, video camera ok, panorama ok

wifi ok

battery life : not that bad, better than stock not as good as CM7

GUI speed : very good, sometimes suffer little slowdowns but in general very fluid

Games : I tried a couple without problems, no lag or slowdown

That's what I've tried. The only thing that failed to me was the custom actions in the unlock screen, I configured two actions but didn't appear.

In general I'm very satisfied, Quark is a genius and I'm very happy because I can have JB in my Bravo.
[Bravo Android Development] mikiemc73:
So far, so good. I haven't had any problem with the lock screen actions, battery life is good. I do have one problem, a Metamorph for the theme I'm using is now boot-looping my phone. :( Anybody have any ideas?
[Bravo Android Development] syllogyking:
I'm not positive, but I don't think metamorph supports jb (api level 16) yet.
[Bravo Android Development] mikiemc73:
It was working on previous builds, just not the last 2 or 3. I think it was 0828 that it last worked on.
[Bravo Android Development] mikiemc73:
the other option is to theme the ROM before I flash it. If anyone has any pointers on that, I would greatly appreciate it .
[Bravo Android Development] skeevydude:
Care to post a link to your theme? It'll help.
[Bravo Android Development] mikiemc73:
Its in the drop box mirror I put up in the "Other Stuff" folder.
[Bravo Android Development] skeevydude:
If its not working by patch, then you can do it manually. Just open up framework-res.apk for the rom you want to use with 7zip and the zip with the icons in it. Then drag and drop each icon into framework-res into its corresponding folder. I'd do a quick look over and not add icons that aren't present in framework-res.apk -- that may be the problem.

You can also use Rom Toolbox by JRummy-- it has the Epic Blue Framework theme as one of its mod options.
[Bravo Android Development] mikiemc73:
Thanks, I'll try it.
[Bravo Android Development] skeevydude:
I forgot to add, you don't even need to use apktool to decompile the framework-res.apk. This is literally a drag & drop procedure with 7zip (or a few presses with Rom Toolbox). I'd do it manually -- the issue is, I think, you added an image(s) that wasn't present in the framework-res of the rom you're using it on. Plus you'll learn to do it w\o a tool.
[Bravo Android Development] marcelarr:
I like it!

I installed Quark's latest build an like it very much so far.

Coming from Kangs CM7 I can say the following:

- A little slower than the CM7 hangs up a bit, but not as much as the last one I tried (20120812) which I hat to uninstall immediate because it was not usable. I can compare this build to how slow my stock rom was working. (Not that bad but not as good as CM7)

- Battery is not as bad as expected... I am turning off wifi to make it last longer, I did not have to do that with CM7. I get a full day out if it. Yesterday I used it all day, including wifi and music and still had 39% by 10 pm.

- Charging is for some reason much slower than CM7 (faster when the device is turned off)

- I have not have any problems with radio at all... signal is working perfectly and when sometimes CM7 didn't manage to sent a text or make a call on the first time (I had to redial or re send).

- Camera is working fine for me including auto focus

- Poweramp, my preferred music player works wonderfully compared to the previous build I tried

- Gaming was fin... no lagging

- Wifi connects fine, does not take long at all

- I had problems authenticating to Google Account with CM7 and my router, I hat to go to another router to get the market even working! And could not purchase apps when connected to my home router... this rom does not give me that problem at all!

- Youtube works fine!

So so far so good! Thanks to the devs for the awesome work! Im keeping it as my daily rom!
[Bravo Android Development] hotshot545:
Reboot problems

Hey guy's i'm having a major problem because my phone is being reset everytime i turn it on and off, I rebooted it to change baseband and that's when I saw that my phone keeps reseting itself to the screen that say's welcome, like the one which comes after you flash a rom onto the phone.
[Bravo Android Development] mikiemc73:
So, here is where I stand on the theme issue. I tried using ROMToolbox, no luck, it wouldn't download. Other mods downloaded fine, just not EpicBlue. I tried to push it to the ROM, and no luck there either. It seems like anything I do to the framework-res causes it to bootloop. I have no idea what to try next.
[Bravo Android Development] mikiemc73:
Well, apparently IZarc doesn't work as well as I thought it did. I downloaded 7zip, and poof, I have my lock screen back.:D
[Bravo Android Development] syllogyking:
has anyone tested quarx' test kernel to see if it works on our bravo? apparently, gb kernel can now be used on the SoC green lens. one user was reporting more than 250 mb of free RAM (although this could be because of disabling hwa for apps). looks like button backlights, promity/light sensor, and utlization of 4 clks/vsels will not work unless a defy+ JB build is flashed, according to users.

edit: just checked quarx's upload site and noticed a jpeg of our bravo with a custom kernel! :) so don't fret boys and men about the lack of an update. he's definitely working on our device.

http://quarx2k.ru/uart.jpg

ot: interesting how it shows his total memory is 475 mb, while mine shows 477 mb. wonder where my extra 2 mb are coming from..

alright, since I doubt anyone will post, let alone look at this till much later, I'll be home in a few hours and test it out. I'll post my results here.
[Bravo Android Development] josuearisty:
Yes it is working, he tested it alredy it works using the kernel for defy, as always you know our phones share almost everything speaking about hardware

I wish they get it working as well as possible very soon.
[Bravo Android Development] syllogyking:
I know that they are very similar hardware wise...but there's obviously going to be kinks that need to be worked out when using defy-optimized things, like hm maybe camera?

Anyways, I tested it. It booted up fine. Didn't have cell radio and was greeted with an android system fc. I did have ksm and zram (not implemented yet) options in cm performance settings. I didn't have any changes in my free RAM. Didn't really feel any smoother either. When I opened up camera/video camera, the preview was like a green screen and full of static. Obviously, not optimized for kobe camera. Also when I turned on wifi, it went into a bootloop. And yes, I had replaced with quarx's 2ndboot.ko and walter's ramdisk file before flashing the kernel.

Currently restoring my nand.

edit day 2: new 6/10 kernel came out from quarx, wifi bootloop issue is fixed. 1st bootup after reboot is very laggy. camera preview is still fuzzy, and taking picture caused phone to freeze. progress is progress
[Bravo Android Development] BravoMotorola:
I find it awesome all this work is being done for the Bravo. Saves everyone money lol. Who needs to move on to another phone really when the Bravo can run JB and get all of these extra goodies? Satisfies me. It has better support and stability with CM10 and everything then my Atrix, I've pretty much ditched the Atrix for the good old Bravo.
[Bravo Android Development] Parcae:
Has there been any progress on fixing the memory leak?
[Bravo Android Development] syllogyking:
what do you mean by that?

/device reboots occasionally with custom kernel, but nothing too obtrusive.
[Bravo Android Development] Parcae:
CM10 based roms have a memory leak, right? Or has that been resolved?
[Bravo Android Development] syllogyking:
I don't know what 'memory leak' is referring to. If you're meaning less free RAM after flashing, then probably yes compared to cm7. However, you could always get more free RAM by disabling HWA for apps. The only thing I have it enabled for is system UI and android system, and I usually sit anywhere between 150-170 mb free RAM.

///

Since, our device has been stuck on the 9/12 build for some time now, I went ahead and made a zip (http://www.sendspace.com/file/i9f8l7) based on today's 10/10 JB 4.1.2 build for defy(+) that Quarx uploaded. The kernel that comes in the zip wasn't getting me past the Moto splash logo, so I went into recovery and flashed the 10/6 custom kernel on his site. I could finally boot, and it was obviously laggy for a while. But after disabling wifi, and putting it in sleep for a few minutes, things were speedy :D crt-animation still isn't working for me though and the green static in the camera is still there :(

So, I installed 3rd party camera apps (LG camera, camera MX). Preview works great there, but pictures taken can't be saved...I wonder what could get this to work? My hunch is that there's something in /system/bootmenu/2ndboot that's knocking off compatibility with the kobe camera...

I recommend enabling KSM and 18%(default) zRAM in performance settings. Don't worry if it's hanging a bit here and there. It does get smoother and more responsive over time.
[Bravo Android Development] BravoMotorola:
Static could just be the kernels fault. The camera libs not changed and the kernel doesn't work great with them maybe. Maybe eventually he'll put up a better/more specific kernel that works better with the Bravo's camera. Other then that any problems we have Defys probably also have.
[Bravo Android Development] syllogyking:
alright, so unless Quarx gets the camera to work there won't be a functioning Bravo camera with custom kernels at least.

But for those of you who don't mind, any updated defy(+) custom kernel builds can be used on our bravo by following these instructions by nidhish91:

STEPS TO FOLLOW WHEN YOU HAVE BOOTLOOPS OR BLACK SCREEN WITH RED LED ON:

-1st of all set default boot to 2nd-boot

-Go to recovery and flash the 24.9 defy+ build

-Then flash the kernel 6.10

-After that flash the latest build

-Wait and you will have your phone working proper.

I'll post a screen of proof soon.
[Bravo Android Development] josuearisty:
This steps are only for defy red lens, not for us, Im using lastest build with custom kernel now I was using cm7 before and all I had to do was:

-flash lastest rom with custom kernel

-then flash gapps

-then update_for_11.10 (which is like a fix because it didnt work for me before this file)
[Bravo Android Development] syllogyking:
thanks jos, but that didn't work for me. I was coming from 10/10 jb with 10/6 kernel. I think it was ok for you because you came straight from cm7.
[Bravo Android Development] josuearisty:
Ok, I understand, I swicthed betwen those jb roms but I made a full wipe, including system with a flashable zip.

I hope quarx can ends all of this soon and we have a completly working jb rom
[Bravo Android Development] AwesomeChris:
Any luck with the latest defy build? Anyone having any luck with camera?
[Bravo Android Development] josuearisty:
No way, I dont know if merging libs and camera files with these builds would make the camera works, but maybe there is something attached in kernel which need to wait for quarx. I would like quarx fix omap 720p codec or whatever is needed to watch flash videos in browser and netflix isnt working either.
[Bravo Android Development] syllogyking:
i've already tried merging camera libs/files from cm10 bravo builds...no dice on camera working. Same green static background shows for camera preview and pictures/video can't be taken. definitely, a kernel compatibility issue. I pm'ed quarx, but he hasn't gotten back to me.

on another note, battery seems to be working relatively well:
[Bravo Android Development] Dr. Orange:
How exactly do you merge cam libs/files from one build to another? And which files do you need to merge? I'm trying to fix skeevy420's cm7 kang from 0902. Everything about the build is perfect except the camera.
[Bravo Android Development] syllogyking:
skeevy (btw: he's been MIA for a while :confused:), mentioned some libs to use for porting cm9 form defy. I'm not sure if that would be the same for cm7. he posted in the dev thread twice with the files/libs that needed to be moved. I'll see if I can find them, or you can do it yourself :p

EDIT:

link 1: http://xdaforums.com/showpost.php?p=27283851&postcount=171

link 2: http://xdaforums.com/showpost.php?p=24602726&postcount=1
[Bravo Android Development] Dr. Orange:
Thanks! I'll check it out. :) I hope skeevy is alright. :(
[Bravo Android Development] josuearisty:
There is a problem also with buttons, they work as if there were four buttons, I had to enable on screen buttons.

I hope skeevy is fine too! It seems to be he is working hard these days, when he was helping us he was not with a job.
[Bravo Android Development] skeevydude:
Just been busy working. Been doing 5-6 days a week between 7-12 hrs a day. Can't save any money cause my Dad can't work since he's had surgery (part of colon and appendix removed; diverticulitis) so I'm paying for some of his expenses now (cigs, smoke, medicine). He's starting to get better, but still in a lot of pain and has very limited mobility -- although he's much better with a shotgun in COD now :cowboy:.

Since I have a three day weekend and some time off (finally) I'm gonna work on a new CM72 port based on the latest Defy CM.com Nightly and update PA. Still need to install Linux on my garbage can PC (found a working quad core with 3 gigs of ram in the trash at work) but that'll only take a few hours including installing all the required apps and syncing with github.

I'm also going to study up on the custom kernel and see if I can't make PA run one :).

If I'm not bothered too much today I should be able to have a 7 port tonight or tomorrow (they're not hard to do at all, takes longer to push it to the sdcard than it does to actually port the rom; seriously). No eta on PA or anything custom kernel since I've been out of the loop for a while now.

//just realized this was aleeyt's cm10 thread, only posting here since I was mentioned a few times.
[Bravo Android Development] syllogyking:
good to have you back for a little while. I hope your dad's health improves.
[Bravo Android Development] josuearisty:
Good to see around, hope to see you working with us again soon.

Thanks for supporting.
[Bravo Android Development] Dr. Orange:
Yeah it's good to see you again! We all wish a speedy recovery for your father! :)
[Bravo Android Development] syllogyking:
latest commit by quarx: 13 minutes ago

Quarx2k pushed to jellybean at CyanogenKobe/android_device_moto_mb520 cdf78cf

add support 2ndboot

there's hope for camera+kernel compatibility after all

:)
[Bravo Android Development] josuearisty:
Good to know about that, we were left in the dark for some time, but after all if flash player isnt working I wont use it as my daily rom.
[Bravo Android Development] skeevydude:
My Dad's getting better, but its taking time. He had part of his colon and his appendix removed. I feel bad for him -- if he takes pain pills it relieves the pain, but he gets constipated from the pills and that makes him hurt worse, or he doesn't take the pills and just hurts.

I should have had something done by now, but I went out this weekend and enjoyed myself for a change :p. Finally have Linux on my "new" pc (and all the required files to compile cm), but all my android files are scattered throughout 5 hard drives totaling 3.5TB, so its a bit hard finding everything needed to port roms for the moment. The 2 drives with everything I need on them are in my old pc that's not fully working at the moment -- I stole its upgraded power supply and video card for the new one. Once I turn the old pc into a file server I should be back in business :).
[Bravo Android Development] mikiemc73:
I feel for ya. My mother in law is recovering from a heart attack, and both of my file drives crashed. Plus I just smashed the screen on my Bravo. I got a new one on its way, and with being switched to nights at work , I might have the money to replace the drives, after I take care of a few other bills. I'll keep your father in my prayers.
[Bravo Android Development] marcelarr:
Hope your dad feels better soon!
[Bravo Android Development] skeevydude:
Thanks. Sucks you m-i-l had a heart attack. My mother has had 3 now and another one will be the last one.

Normally, I don't have a problem fitting in all my drives into a pc, but this hp quad core I found has a ton of built in proprietary HP storage bays and they take up way too much room for something I'll never use. I'll end up taking a Dremmel and a Mig Welder and fabricating in some new storage mounts and more ventilation.

So does he. He has the worst case of cabin fever ever now. He used to go out one or two days a week and drink with his friends, but he's only been home and the hospital for the past 2-3 months now. Call of Duty isn't cutting it for him anymore -- I'm trying to get him to play Assassin's Creed (1 & 2) but he's hooked on Hardcore Domination like a crackhead to rocks :p.
[Bravo Android Development] Dr. Orange:
He's a good man, hardcore is the only way to play. ;)
[Bravo Android Development] itzdustin:
i tried to apply the ROM while on stock 2.1 and now im stuck on the M screen. i used bravo bootstrapper for recovery and now i can only access stock recovery. how can i get the phone unbricked at this point?
[Bravo Android Development] josuearisty:
If you are stock on motorola logo, you have to flash the SBF file again and start from zero.

http://xdaforums.com/showthread.php?t=1559109

Then instead of using bootstrap go to this thread and follow the steps to root and install recovery with one click

http://xdaforums.com/showthread.php?t=1817842
[Bravo Android Development] syllogyking:
@skeevy - I saw your issue post on quarx's github. does camera compatibility with custom kernel look promising to you?
[Bravo Android Development] skeevydude:
I compiled a JB rom eariler today from Quarx's sources just for the Bravo (custom kernel). I'm about to test it. I haven't looked over the kernel sources enough to know if I'll be able to do anything about it. I'll post back in about a half an hour and let you know how it goes (and maybe start an upload if it works alright).

So far all I've done is cleaned up the common repos (device and vendor) and updated the kobe overlay to mirror the jordan overlay for the most part (torch and led flash options don't really matter for us :p). I also made sure to keep PA compatibility when doing this as well -- the only reason I built this rom was to see if my build environment was working. Now all I have to do is pull in a ton of PA updates and that'll be going again :).

I also have a good CM7 port almost done (based on cm.com 11\04). I've been running it for two days now and the only bug I've noticed is that I need to reboot to change the pulldown power widget color:confused:. I still need to reflash it, not enter my account info, do some tweaking, nandroid, and upload it.

UPDATE

Camera didn't work, button bug still present -- I finally realized that its acting like we have the 4 Defy buttons, but we only have the 3 icons so its annoying -- all 4 work...perhaps buying a Defy screen is a better solution :p. It also doesn't boot when the usb is plugged in. Other than that it seemed smooth enough :).

Another Update

Been looking over make menuconfig and I noticed that the soc driver wasn't used. I enabled it and did a few other tweaks. Recompiling.
[Bravo Android Development] skeevydude:
Still no success -- tried kernel with SoC enabled and used Bravo devtree. Compiling the rom with the Bravo kernel located at sourceforge and with the Bravo devtree since Qurax recommended trying it. I'll be able to test it in about an hour and a half to two. I'll update this post once its flashed and hopefully boots.

UPDATE

Defy kernel boots and works with Defy devtree -- acts like it has 4 capacitive buttons; camera\camcorder doesn't work; capacitive backlight always at 100%

Defy kernel hangs on 2nd-boot with Bravo devtree

Bravo kernel bootloops on 2nd-boot with Bravo devtree

Bravo kernel hangs on 2nd-boot with Defy devtree

Other than the camera and capacitive buttons' issues, it runs really, really good.

I've been reviewing Quarx's Jordan kernel commit history and I'm gonna apply some of them to the Bravo kernel sources and go from there -- no uart output isn't helping any either. If you can deal with no camera and the capacitive quirks, the download the Defy Plus custom kernel rom since there aren't any major problems or issues. Remember to check the OC settings before booting and make sure you're using interactive (only one that works properly right now) and configure the 4 vsels to your liking. I'm using 300@22, 600@38, 800@48, 1000@54.
[Bravo Android Development] syllogyking:
here's to hoping moto didn't screw up
[Bravo Android Development] skeevydude:
Making a bit of progress -- I've been hexediting the Defy devtree and I've replaced a few strings that differed between ours. Now uses the camise driver, umts-kobe-keypad, and is branded as MB520....hasn't helped anything, but hasn't hurt either. So far the only testing I've done is using libsoccamera.so and a replacing libsoccamers.so with libkobecamera.so. I'm going to try using the Kobe libs that I compiled yesterday when I get some free time (got some things to do in a little bit).

Looked over both Kobe and Jordan ramdisks and the each load the exact same keypad file....The capacitive keymap is a mystery to me...

I'll post some files later today when I have the time -- leaving now.
[Bravo Android Development] josuearisty:
Great, hope you get it man, our Bravo needs some of this new modified kernels.

I'm happy you got wide screen recording for us too.
[Bravo Android Development] skeevydude:
I didn't really give us wide screen, just got lucky using the old porting tricks :p. Checked github, looks like Quarx may have fixed the Bravo camera, I'm gonna start on a compile after I finish my coffee.

Still haven't figured out where the capacitive buttons settings are set or stored. Its not that bad once you remember that search is just to the right of back; back is between back and home; home is between home and menu; menu is to the left of menu. I still think a better fix is to buy a Defy capacitive screen with all for icons on it....I'm both joking and being serious there.

The capacitive issue is in the devtree -- all other files related between the Defy and Bravo are identical. Its just gonna take either some time with a hexeditor or Quarx patching 2nd-boot.ko to work with the Bravo devtree (currently the 2nd-kernel uses the Defy+ devtree, while its similar to the Bravo's its just different enough to mess with us).

//I've tested about 30 different devtree edits....
[Bravo Android Development] josuearisty:
It's seems to be very hard editing the Devtree to find how match with the capacitive buttons for bravo, I hope our kernel don't change so we can port some defy rom in the future.

Do you think that wide screen video recording can be port to gingerbread? It would be great to have it.

Thanks for all man.
[Bravo Android Development] skeevydude:
Editing the devtree isn't that hard, just open it up with a hex editor and have at it. So far I've managed to change the camera driver it loads by default, changed the key layout from umts-jordan to umts-kobe, changed a mb526 to mb520; but any changes to the button settings causes it to hang on boot.

Widescreen video on GB will come when we can boot a custom kernel on GB roms.

Quarx's change to the camera hal allowed camera.apk to load, but nothing previewed or worked (it crashed on init before) using libkobecamera.so as the camera driver. Using libsoccamera.so (had to rename to libkobecamera.so) with Quarx's change doesn't work either. Tested with both the default devtree and my edited devtree.

Gotta do some things around the house, I'll post some logcats later tonight and the CM10 I'm using now (If you don't care about camera and the capacitive buttons don't bother you CM10 runs great now)