yashsingh1/xdaforums huggingface dataset:
[Bravo Android Development] skeevydude:
Nothing new to report on other than Panorama Pictures work (I never tested it until last night). The Defy SoC Camera Driver works for everything but taking pictures. Last night I removed all the flash code from the jordan camera source and I'm recompiling -- even if it doesn't fix the camera its one step closer. Forgot to change /system/bin/battd from the 526 to 525\520 and now I hope my phone charges up enough to push the proper battd -- its been on the charger all night so hopefully it has a charge now.
[Bravo Android Development] skeevydude:
First attachment is a panorama from my porch (JB CM10 Custom Kernel) -- quality sucks, but it works

The 2nd and 3rd are my dogs -- The dark one is Leecie and the other is Bonnie (they're 8 years old now, had Bonnie since she was a puppy and Leecie since she was a year old. (Pictures from CM7 I think)

Had a video to upload, but its .02 mb too big to upload....
[Bravo Android Development] josuearisty:
Excellent... man you did it, I think you hacv become our moto bravo guru!

You have grown very much in development for android. Congrats for you!

You have gone very far.

I think you should create a new thread for JB 4.1.2 and 4.2 (when it comes) so you can update the main post with new features and updates.
[Bravo Android Development] skeevydude:
Still haven't done it yet. Got another test to try today -- now that flash is removed from from the jordan libs, did some of the changes Quarx did for the hal and compiled that last night; gotta do some crap around the house before I go full on Android today. I still have a few changes I'd like to do on the Bravo builds before I start a thread on it. Our current JB thread is good enough for discussing JB crap for now -- I don't want to have a gillion different threads for the same thing like the Defy forums have.

All the changes I'm gonna do today are common repo related -- I'm gonna integrate the Defy, Plus, and Bravo scripts a little better. Bravo has some Defy branding in build.prop, our Overlay hasn't been touched in a long time, gonna add some if-then's to the build scripts and separate things like the oem camera libs (Bravo has bayer, soc, and oem libs). I'm gonna try and do it in a way that hopefully Quarx will take the pull request.

I hope the changes I did to the hal work, but I'm doubtful since nothing else I've tried has worked. At least nothing I've done has broke anything so it makes my a (tiny) bit hopeful that maybe I'm doing something right. I'll chime in later with the results.
[Bravo Android Development] mataflakitas:
good news skeevy420 thanks may friend
[Bravo Android Development] marcelarr:
W-O-W

Amazing! And beautiful dogs.
[Bravo Android Development] skeevydude:
Thanks. I still haven't gotten anywhere yet. Found the capacitive code, changed it to what I thought would work for us, but it loads the specs in the devtree and ignores the hard-codec values. Replacing the Jordan cpkey code with Kobe's (in devtree) causes the boot to hang. With no way of viewing uart output I have no idea where our devtree hangs -- never bootloops, only hangs (maybe freezes???). I'm gonna look over the code again and see if I can't remove the lines to check the devtree for cpkey info.

Modified camera code didn't work.

I don't think Motorola released the actual Kobe sources, just the unmodified sources that they were using at the time. There's a ton of Sholes references (Droid1\Milestone1) in the code, but that's it. Nothing in the way of Kobe or Jordan. Some Moto sources contain a log of what patches they used, but not ours (I downloaded the sources for all Moto phones with 3 cpkeys looking for solutions). I've looked in both the (Kobe) Eclair and Froyo sources and both are very similar, but have nothing that helps since the files in question are identical to whats in Quarx's repo (except for the fixes he's done) -- the lines I'm referring to are identical (cpkey code). Its frustrating.

FYI, the cpkey code is in Jordan-Kernel/arch/arm/mach-omap2/board-mapphone.c (search for vkey)

I'd hate to have to fork the kernel for a few lines in one file...I'm gonna ask Quarx to see if he can't get it to boot with the Kobe devtree since that'll help us more than anything. With no uart output, all I can do is guess.

//Quarx did a ton of kernel updates over the past few days. That dude's a machine. :cool:

///Epsy's been working on an ICS custom kernel rom :)
[Bravo Android Development] fatfox2002cn:
sounds good.
[Bravo Android Development] Shawn:
Broke my S2, got this Bravo off my brother for a temporary phone. Was going to buy another s2 tomorrow because stock on this phone is horrible and laggy. The phone even started typing by itself and opening things. Now that I flashed CM10, I'm keeping the Bravo as my main phone until my upgrade! Sorry for the little rant, just excited!
[Bravo Android Development] Dr. Orange:
We're glad you like it. :) This phone would nothing with the Defy and Bravo devs. They put in so much time to perfect these phones and they have done an outstanding job.
[Bravo Android Development] Shawn:
What's really funny is that my brother tried to trade me his captivate glide he likes the Bravo so much. I love the devs for the time and work they've put into both phones!
[Bravo Android Development] kevins547:
the battery life has been improved ?
[Bravo Android Development] skeevydude:
Somewhere between CM9 and CM7 depending on usage. That's with gps always on, wifi or 3g depending on availability, Yahoo Weather always running, 2-4 hours of music (headphones or thru jack), and moderate usage. Only tweaking done to save battery life is undervolting.

It would be close to better than 7 if I turned off gps/sync, no weather, and only made calls.
[Bravo Android Development] mataflakitas:
ghost town..for bravo..
[Bravo Android Development] kevins547:
when i charge, the led is turn white, but i dont want it, how can i turn off that light?

i just want the led is on when i missed message or call only.

and the keyboard vibrate after i touch it, it uncomfortale, and waste battery.
[Bravo Android Development] skeevydude:
led

settings>advanced>charge led mode

or edit the build.prop

vibrate

settings>sound>vibrate on touch
[Bravo Android Development] mikiemc73:
I wouldn't expect much right now, with Christmas and all. So call it on vacation.
[Bravo Android Development] kevins547:
the connect to 3G is pretty slow compare to CM7

and how can i export contact list to sim card, its just have export to SD card.
[Bravo Android Development] Quarx:
Don't worry, be happy:)

I'm fixed camera for bravo.. soon i'll upload new build:)

skeevy420, do you have correct coordinates for touch buttons?
[Bravo Android Development] skeevydude:
What a lovely Christmas Present ;)

static struct vkey mapphone_touch_vkeys[] = {
{
.code	= KEY_BACK,
.center_x	= 376,
.center_y	= 906,
.width	= 36,
.height	= 57,
},
{
.code	= KEY_MENU,
.center_x	= 104,
.center_y	= 906,
.width	= 36,
.height	= 57,
},
{
.code	= KEY_HOME,
.center_x	= 240,
.center_y	= 906,
.width	= 36,
.height	= 57,
},
};

I think that's correct. .center_x may be off by 1-4 pixels for menu and back, but that shouldn't be too big of a deal. The values above work out mathematically for a 480 screen and correspond with what's shown when using the show touch coordinate feature.

Thanks Quarx. We're all very glad you're helping us.

Merry Christmas
[Bravo Android Development] hotshot545:
Hey guys

hey guys my bravo has had a long run and i just upgraded to a pantech burst....i was wondering if anyone would be able to make a jelly bean rom for us...we do not have as many talented devs like you do....can any of you help us. thx
[Bravo Android Development] Quarx:
New build: http://d-h.st/users/Quarx/?fld_id=5154#files
[Bravo Android Development] mataflakitas:
Thanks Quarx...

Enviado desde mi SGH-T989 usando Tapatalk 2
[Bravo Android Development] skeevydude:
Snowstorm knocked out my cable internet, I'll download and give you some feedback when the net is back up.

I don't like downloading roms over my limited 3g. Overage charges suck.
[Bravo Android Development] skeevydude:
Got partial internet. Some sites work, some don't. Xda and Play Store don't. Downloaded CM10 for Bravo and it works great. Camera, capacitive buttons work perfectly - but no 848x480 video recording :(. Only used stock camera app.

Quarx, is the camcorder's recording resolution limited by Moto in the proprietary libs? We're able to record video in 848 with libsoccamera but only preview in 848x480 with libkobecamera (only records video in 4:3 640X480 and under; soc allows 16:9 @ 848 and under). Seems like the hardware can but the software can't. I hope that made sense - typing on a Defy over 3g to access Xda.
[Bravo Android Development] kevins547:
sorry, i have to say i should bach to CM7, because it's smoother than this rom cook. :(
[Bravo Android Development] kevins547:
i back to CM7

oh no, my phone is stuck at logo M :(

i had gone to stock recovery wip date/cart..., reboot, but its still :(
[Bravo Android Development] skeevydude:
You didn't try using ext4 did you? If so, you'll have to reinstall CM10, reboot, switch back to ext3, reboot, install cm7. If that doesn't work, just flash the sbf :rolleyes: (its what I did)

To make CM10 less laggy, go to Settings>Performance>Memory Management and enable Kernel samepage merging and Zram -- I have decent results with the default setting. I'm using SIO and Interactive (default settings I believe). I also haven't messed wtih 16bit graphics, purging of assets, or surface improvement yet -- If someone has, share your results with us.

Some other tweaks to do are in Settings>Developer options. Go down to Drawing and change the both animation scales and duration scale to .5x or none. Haven't messed with disable hw overlays or force gpu rendering -- share results if you have.

I use Holo Launcher HD and it works pretty well for the most part -- disabling the App Drawer Open\Close animation helped a lot with its snappiness and open time. Using less home screens and widgets helps a lot. I use 3 screens myself -- One with weather (the left), Center screen has music widget and a folder with some common apps I use frequently (my home screen), my left screen has nothing on it :p.

If ya'll haven't noticed a trend yet -- the less animations the better the performance of CM10 (or using a less intensive animation). There's also messing with the HWA settings, I haven't since ICS so I won't comment too much, but disabling HWA for some apps helps -- search the Defy forums for more info on this.

You could also bump Vsel4 up to 1100@55~57 as well. Changing all values to something like 300@20,600@40,900@48,1100@56 should increase performance and not have too much of an impact on battery life.

Properly tuned and tweaked CM10 will run very well, even with live wallpapers. The default settings aren't necessarily the best, but once you spent some time getting it setup it'll work great.
[Bravo Android Development] kevins547:
thank you, it work.

but everytime i reboot, all my setup is gone, i have to set it up again everything.
[Bravo Android Development] sdrawkcab3:
Thanks for the new build, quarx and thanks for the tweak suggestions skeevy420.

I didn't realize we had access to all 4 vsels. Seems I can't get vsel3 working, nor does CPU Spy record any vsel other than deep sleep. Any suggestions?
[Bravo Android Development] syllogyking:
Those have been traditional issues (nothing major imo) in the 2nd boot builds. I think it has something to do with the power hal which only works on the interactive governor, but I might be wrong.
[Bravo Android Development] skeevydude:
That's what I picked up over in Defyland, mainly Blechd0se's custom kernel thread. I've never noticed vsel3 not working, but CPUSpy was as far as I checked. BTW, I plan on forking Blechd0se's kernel and applying Quarx's Bravo patches to it. Probably tomorrow or Saturday the latest ;). There's also been some talk about removing the hal so that other governors work better -- gonna keep an eye on that.

Speaking of kernels, does anyone think that the back button seems just a bit off? Like you need to press just a hair to the left of where you think you need to? Seems that way to me...Anyhoo, would anyone be interested in media keys in the dead space next to menu and back? Like track skip forward\back, volume up\down, etc. I'd like track skipping there myself, but that's me. Gets annoying having to exit the app I'm using, press next on the widget, reopen app or turn off screen, long press volume, turn screen back on. Now that I think of it, we could hide something between Menu\Home & Home\Back as well... Anyone have thoughts on what to do with all that unused space? It might even be possible to hide some buttons up top around Motorola. Every part of the screen is supposed to be touch sensitive so it doesn't hurt to look into it.

As for the settings not sticking, not too sure on that one. I've had it happen before and usually a factory reset from CWM and a rom install fixes it. When that doesn't fix it, the next option is to reboot into stock recovery and perform a factory reset from there -- Hold Power + Volume Down on Boot until you get to the screen with an ! in a triangle next to an android, then press Volume Up + Volume Down at the same time, select factory reset, and reboot when its done. If that doesn't work, flash the sbf. When in doubt, flash the sbf. :silly:

EDIT: Checked Blechd0se's github and he's already added the necessary Bravo patches. Guess all I need to do is change kernels on android.xml, sync and compile CM10 :).
[Bravo Android Development] kevins547:
i can not install apps from play store :(

it's just showing "downloading"
[Bravo Android Development] Dr. Orange:
I have no issues with this latest build except: standard lagginess (easily fixable with some tweaks), and the capacitive buttons are slightly off. The menu button is the worst of the 3 for me, I have to push it 2 or 3 times before I find the sweet spot. But that could be just how I press the buttons normally. That, and the vibration is pretty low for the capacitive buttons, it's hard to know when I've pushed it. But that's with all the builds so it's not a big deal. :p

All that being said, I'm really impressed with this build and will probably keep using it until school starts back up. Thnx Quarx! :)

@skeevy: I'd prefer to have buttons at the top just because my fat thumbs would always accidentally push the ones in between the standard 3 at the bottom. I'm interested in more buttons, play/pause, and skip back/forward buttons would be pretty cool if we could use them while in other apps. :D

Edit: I've also noticed an issue with the notification sounds not loading right. Example: I'll get a message, and the phone will freeze while it waits for the sound to play, I've had to reboot at least once because of it. Is anyone else having this problem?
[Bravo Android Development] skeevydude:
I didn't notice the menu button being off until you mentioned it. Looks like their centers need to be shifted to the right by 2, maybe even a slightly bigger touch area -- but bigger area potentially means less "hidden" buttons. I'm gonna look into the Moto area idea tomorrow. Pretty much any key can that's available on an android hw keyboard\bt headset can be done and be recognized by apps, though I don't think we need an ALT key over the notification light :p

I hear ya on the fat thumbs -- I can't tell ya how many time I've hit the search button while playing FF3. In the middle of a battle and search pops up...:mad: Track and volume should be fine down below -- track skipping would only matter if music is playing and volume won't make an app exit out, making them ok if they're accidentally pushed; that's my logic anyways.

**Kinda technical crap, skip to the sentence below for a simple summary**

Well, did a bit of testing before submitting and have some interesting finds -- all the black borders around the screen respond to touch except the Motorola area, only tested with Pointer location under Developer Settings. I'm hoping that the tool just doesn't recognize that area. From what I've noticed, the tool recognizes the screen as approximately 916*x490*. 845- 916 is the capacitive buttons while -5 to 0 is left of screen and 481-490 is right side of screen. Note the *'s -- I was getting values like 916.5, 490.2....and there is a negative X axis from left edge of screen to the edge of capacitive screen -- I'm hoping that there's a negative y axis so we can use the Motorola area. I'm a bit confused on one side of the screen having 9 available pixels and the other only 5...fat thumbs???

What all that means is placing buttons in the Moto area might not be doable, but we can use the black borders on the sides of the screen.

Edit: I've also had some sound issues, but for me its my ring tone -- it'll play the first half second of it then nothing at all. I've missed a few calls because of it. I'm speculating that its from undervolting -- Bravo with "stock" settings has no notification tone issues at all, undervolted Defy does...Quarx's latest on both. I know the Bravo's working correctly since every time I get an email the sonar goes off. Kzurb sonar ftw :)

//really need to update the rom I'm using in my signature (only used that one for 3 days)
[Bravo Android Development] kevins547:
i use Rock player lite for playing video, in the last buil it very smooth, but now it really bad
[Bravo Android Development] skeevydude:
Only have a couple of ideas for that. Try disabling hwa for it (use the app HWA Settings). Enable ksm if not enabled, same for zram -- if they're enabled, then disable. After that bump up the vsels like I described a few posts back. After all that and you still have bad performance, go to Developer options and enable forced gpu rendering. You can also try messing with Don't Keep Activities and Background Process Limit (both at bottom of Developer options).

If you still have bad performance you're gonna have to look into V6 Supercharger and similar tweaks.

Also, try MXPlayer and MXPlayer Codec ARMv7 and see if they help -- It played my DVD rip of Chronicles of Riddick with 2 audio tracks, vobsubs, high quality x264 encode (done myself) with no problems. Albeit that was on Gingerbread a year ago...I don't have any videos on my phone to test anything right now (all my dvd rips are 1.5gb+, I'd rather have good quality rip versus a blocky rip that fits on a blank cd...sdcard only has about 800mb of space left). I use Handbrake to do most of my dvd ripping if anyone is curious (sometimes I have to use mplayer from the command line -- some dvd's are a pita to rip).

//Looking forward to the new Riddick movie being released next year (September 6, 2013 according to wikipedia)
[Bravo Android Development] BravoMotorola:
Quarx server must be down, any one want to upload the new build??
[Bravo Android Development] Dr. Orange:
I'm uploading it now. Will post link when it's finished.

For Quarx's custom kernel CM10 20121226

Here you go: https://www.box.com/shared/kgwdqv4yvwq4kw2rgblv

Current ROM: CM7.2 Euroskank Cherry Picks | Bravo port
[Bravo Android Development] magicCrazyThing:
I Finally got myself a new BRAVO, and I am using this ROM since it's not my daily use phone. I agree with you that the back button is a little off. I have pretty small thumbs so if I press the back button directly I get nothing. I have to press a little bit to the left. The touch point only covers about half the back button. other than that the ROM runs very well after I tweaked it for no lag. :D

I'm also having a problem flashing the universal version of AC!D audio engine. the .Zip is fine, and I am not getting any errors while flashing. when I boot up the phone though none of the changes have been made. The AC!D notifier app isn't there, and the Build.prop changes haven't been made. Is it possible that the new kernel is causing this. :confused:

This .zip does flash the new kernel right?
[Bravo Android Development] kevins547:
first of all, i'd like to thank you.

in HWA setting dont have ksm & zram

yesterday i used MXplayer, better than Rock player in this new buil,pretty good, but not good as good Rock player in the last buil, i dont know why? MXplayer can play but it not smooth in some videos, haizz.

V6 Supercharger has a lot of version, so i can use version?

reflash, should i wipe data/cache, like flash a new rom? Or i just install zip form SD, no need to wipe.... ?
[Bravo Android Development] skeevydude:
ksm and zram are under Settings>Performance>Memory Management

use the latest V6 version and the patcher as well. the patcher is the most important part of v6 supercharger.

if its the same rom, you can just wipe cache, dalvik and reflash. no factory reset is required. -- What I like to do is use the bootmenu's mount /data partition over usb feature and delete everything other than /data/app (apps) /data/data (app data) and paid apps (forgot the directory; its late :p). When doing that while upgrading you may experience issues if a system app updates with a new feature -- If that happens, then mount /data over usb and delete everything except /data/app and you're paid apps -- you still gotta configure everything, but it beats reinstalling every app you regularly use.

//Started compile of CM10 with Blechd0se's custom kernel that'll be followed by an AOSP build with Quarx's kernel. Provided I don't get any build errors, CM10 to be tested before work, AOSP after. Never built from AOSP before so not sure if its gonna error or not. Let ya'll know how it goes in the morning.

Good Night
[Bravo Android Development] kevins547:
should we use MT task killer, auto kill ?

after using apps, i quite, but cheking ram, it still there. Has other way to saving battery life
[Bravo Android Development] skeevydude:
You can use a task killer of some sort, but its not recommenced at all. That's why I suggest V6 -- it tweaks the levels of android's built in task killer to make it more or less aggressive (depends on how you set it up). Also, apps in ram won't kill your battery, they'll just open up faster. If you really must go the task killer route, I recommend using Advanced Task Killer Pro; once you get it configured to not kill system processes, the kill all widget it has is great. Don't use it as a task killer, just the widget and kill manually after you're done doing memory intensive crap.

On Android 2.2\2.3 a task killer is needed (sometimes). Not so much on 4.0+. The built in killer is pretty good, but the settings it comes with aren't necessarily the best ones to use and that's where V6 comes in.

@All

Flashed CM10 with Blechd0se's kernel and it seems to be working just fine -- camera took a picture, some apps opened and closed without crashing. Unlike normal, I dirty installed this directly over Quarx's latest CM10 cause I know ya'll will. Dirty install = installing rom without a factroy reset --- Very dirty install = not even bothering to wipe cache or dalvik. Only sim is in my Defy, so 3g\phone calling untested. Uploading. Link when up.

---------- Post added at 10:02 AM ---------- Previous post was at 09:10 AM ----------

CM10 with Blechd0se's kernel

http://www.mediafire.com/download.php?4uqbetzrg5s139c

Install like normal.....

Leaving for work, later.
[Bravo Android Development] Dr. Orange:
Has anyone tried this build with Blechd0se's kernel yet?

Current ROM: CM7.2 Euroskank Cherry Picks | Bravo port
[Bravo Android Development] skeevydude:
It ended up being a hybrid of Quarx's and Blechd0se's kernel -- used Blechd0se's sources and Quarx's defconfig. Didn't realize Bravo had its own config file now...so I updated it with Blechd0s's settings and started again...forgot to commit that (received a call and got in a hurry) synced before the compile, built, flashed, tested and realized I screwed up somewhere :silly:. Fixed it and compiling again. Off tomorrow so gonna try and get something done.
[Bravo Android Development] mikiemc73:
I flashed it last night, and cant seem to install a few things from google, like ADW, or the one of the themes I've been using(EpicBlue), or XDA & RootzWiki. Everything keeps coming up with unknown error code 24.