Wireless Moot

[hAHAha Halo]

I remember what I had, I had a Motorola W755! But no, it was black, not the purple one.. Anyways, that was a neat phone.

Off topic, so now that TI dropped us, who do you guys think the next chips are going to come from?

 

[Dave12308]

it lasted 2 years and 2 months, then the touchscreen gave in, which probably had something to do with me having it overclocked to 800hz when it was mainly a 400-600hz phone.

That wouldn't kill it, 800MHz was a "mild" overclock for the OMAP3430. As a matter of fact, with Android 2.2 (Froyo) it actually WOULD run at 800MHz with the stock kernel, at least while running Flash Player (minimum specs for Flash Player were 800MHz CPU, Moto simply tweaked the kernel to allow for that). Mine ran 24/7 at 1.2GHz from the time p3droid and I created our overclocking kernel until I 'retired' it on the day the iPhone 4 came to VZW. With absolutely no issues.

What killed the touchscreens was dirt and grime getting into the small "crack" between the screen glass and the bezel. I found this out AFTER I threw mine away due to a "broken" touchscreen. If I had taken it apart and cleaned it thoroughly, i'd still be messing with it to this day.

 

[Dave12308]

It's called the "cheesecake factory". I learned how to do it after I was already on ICS. Someone on 905 can look for any update for any phone for any version....if they know how.

So THAT'S what that app is that shows which servers have been updated when, 'eh?

 

[SamuriHL]

-Edit-
I can't imagine you needing help with a bricked phone, with everything you've achieved and done for us!

How do you think I *LEARNED* what I know? No one wakes up knowing everything. I was part of the original crew that discovered how to flash boot img's...we did it the hard way back then. But it worked. Now, we're way more advanced and have multiple methods and all that. But all this stuff was born out of the sweat, blood, and tears of those of us that worked on it back then. The community came together to get people back on the OTA path. This is why I feel so strongly about wanting to give back to the community. The HoB is my contribution to the community and payment to those who taught me what I know.

 

[SamuriHL]

And your willingness to support EVERYONE is what makes you such an amazing person. If your answers are not popular, it means the person asking probably should not be messing with stuff to begin with. At least YOUR support doesn't start with "Well, first you need to do a factory reset........" - that's the type of support I get EVERYTIME I call Verizon about something. One time I had a Blackberry Storm with a F'ed up "surepress" screen, and they tried to tell me a data wipe would fix it. I got into a lengthy argument about how a data wipe was NOT going to fix an issue that had to do with Torx screws and a messed up screen.

I do my best but I'm only one person. So far, I've been able to help everyone whether they like it or not. The HoB mostly speaks for itself. The trick to support is to find the pain points and fix them so that the majority don't need support. That's the design philosophy behind the HoB.

 

[altspeed]

I need better battery life!

Sent from my DROID BIONIC using Droid Forums

On 244/246 with a couple of smart actions (one that kills WIFI from 7a-7p mon thru fri and one that kills data totally from 11p-5a sun thru thurs) I get about 20-22 hrs

 

[Dave12308]

Random thought - I'm actually looking forward to seeing how the Qualcomm-based Moto devices perform, to be completely honest...... Qualcomm has alot of experience with mobile radios as well, and I think they might very well give Moto's in-house modems a run for their money. Only time will tell, but i'd really have no qualms if my next device was Qualcomm-based. The S4 seems to be a nice chipset. A Qualcomm radio mixed with Moto's antenna design might just end up working well. Could be a decent chipset to hold us over until Intel comes out with something decent, anyways.

 

[hAHAha Halo]

That wouldn't kill it, 800MHz was a "mild" overclock for the OMAP3430. As a matter of fact, with Android 2.2 (Froyo) it actually WOULD run at 800MHz with the stock kernel, at least while running Flash Player (minimum specs for Flash Player were 800MHz CPU, Moto simply tweaked the kernel to allow for that). Mine ran 24/7 at 1.2GHz from the time p3droid and I created our overclocking kernel until I 'retired' it on the day the iPhone 4 came to VZW. With absolutely no issues.

What killed the touchscreens was dirt and grime getting into the small "crack" between the screen glass and the bezel. I found this out AFTER I threw mine away due to a "broken" touchscreen. If I had taken it apart and cleaned it thoroughly, i'd still be messing with it to this day.

Umm.. I know that whatever I was clocking it at wasn't good for it. Maybe it was 1Ghz, it ran the processor hard. Secondly, taking it apart is much easier said than done. The D1 is like many devices where you have to take everything apart and work your way from the back of the phone to get to the screen. Special tools, steady hands, carefully following instructions.. Too risky for me. I still have my D1 though.. Huh.. Maybe a project for another day.

 

[Dave12308]

How do you think I *LEARNED* what I know? No one wakes up knowing everything. I was part of the original crew that discovered how to flash boot img's...we did it the hard way back then. But it worked. Now, we're way more advanced and have multiple methods and all that. But all this stuff was born out of the sweat, blood, and tears of those of us that worked on it back then. The community came together to get people back on the OTA path. This is why I feel so strongly about wanting to give back to the community. The HoB is my contribution to the community and payment to those who taught me what I know.

*LOL* I remember that night in Shoutbox where HoB was basically "born" after John L. Galt bricked his phone for us. Never in my life have I seen an FXZ file "appear" so quickly *LMAO*

 

[SamuriHL]

Not gonna lie...I was intimidated by the HOB which was a big reason I stayed on .232 for a while. I never have used a piece of software made by a member of a community to do something as extensive as what the HOB provides....especially to something I NEED to be able to depend on daily... It seemed too easy...make sense? I am sure that I overcomplicated and over thought how the scripts were written...until a discussion you were having with me in the .244 thread , (at least I think it was me) where you kinda explained how you were able to make a mini-fxz by using part of the .905 img (I think that was what you said) and with all of the successful updates others had.. at that point I realized you had basically created a very useful and well made program. I have used plenty of community made Mod tools for Simcity4 , that's about all that is available (another story for another day) and if it crashed my computer It would piss me off,but I could at least fix my computer rather easily.. my phone...not so easy.

The HoB was developed on top of other people's work that came before me. I did some clever tricks to make it work without losing your data. Sarge gave me the method for not rebooting the phone after an RSD flash and that's really opened up some serious power. I've also done a lot of my own development work to make it more powerful and easier to use. The boot img creation is based on the complex manual method that Matt developed. I automated it which was no easy challenge. The mini-fxz was also my idea. John Galt helped me with that one by telling me how to pull certain partitions from the phone such as recovery. It's been an iterative development process to get it where it is today. And through all of the months, it has been COMPLETELY battle tested. Dave and I have bricked numerous times on 235+ and have always been able to recover using the REINSTALL (mini-fxz) option. The dynamic menuing code is something I developed that took a *LOT* of work. It's not nearly as simple as it seems. Even what script to call is done dynamically based upon what option you pick and what files you have available to you. Root is dynamic in that if a new root method comes along, you can throw it in the root dir and as long as it has a run.bat to kick it off, you're golden. The FXZ...that's dynamically discovered. When we get a new one, you'll get a new FXZ installer that'll install it into the HoB. Then you'll delete the 905_FXZ dir and you're fully covered. This project has taken months, but, the results are a tool that is fully dynamic and battle tested.

 

[SamuriHL]

So THAT'S what that app is that shows which servers have been updated when, 'eh?

No. Motowatcher is something else entirely. Cheesecake factory is a term Matt created for what he does. It uses the standard cheesecake app in a very unusual manner. It's a pain to do but if you know how, you can force a bionic to find updates for any version of any moto phone.

 

[SamuriHL]

*LOL* I remember that night in Shoutbox where HoB was basically "born" after John L. Galt bricked his phone for us. Never in my life have I seen an FXZ file "appear" so quickly *LMAO*

The HoB existed before that. Weeks before that, in fact. The FXZ was required because of the 235 security. We owe daywalker04 a huge debt of gratitude for giving us the FXZ that fast. It's enabled Matt's method of moving between leaks without being able to fully FXZ back.

 

[Dave12308]

Umm.. I know that whatever I was clocking it at wasn't good for it. Maybe it was 1Ghz, it ran the processor hard. Secondly, taking it apart is much easier said than done. The D1 is like many devices where you have to take everything apart and work your way from the back of the phone to get to the screen. Special tools, steady hands, carefully following instructions.. Too risky for me. I still have my D1 though.. Huh.. Maybe a project for another day.

Like I said, even 1.0GHz was NOTHING for the OMAP3430. Crap between the screen and bezel is what kills D1 touchscreens. I never did say that it was EASY to fix. I just would have attempted it had I known. But take it from a guy that CREATED custom kernels for the damn thing - 1.0GHz was totally safe. Most of my 1.0GHz kernels actually ran stock 600MHz voltages to hit that speed, and my 1.2GHz kernels were very SLIGHTLY raised. I've never heard of any cases where 1.0GHz would kill an OMAP3430.

 

[altspeed]

my phones since the late 80s have been:

*Dynatac brick 89-94 cellular one
*some nokia bag phone 94 alltel
*startac 94 swbell mobile
*microtac 98-04for a loooooooong time swbell mobile
*kyocera rage 05 alltel
*V220 late 05 cingular
*V400 05 cingular
*V440 05 cingular
*V451 06 cingular
*a treo 650 06 cingular that got linux hacked on top of the palm OS with a fitzall kernel (called shadowmite linux if anybody remembers the *rather involved hack) first smartphone that would run a terminal emulator
*some rather unkillable little sony ericsson flip 06-07 cingular with a weird "roll bar" looking antenna
*a samsung blackjack 07 cingular
*a sony ericcson w851 07 walkman phone ATT
*a blackberry curve 08 ATT
*some HTC POS windows 6.5 phone 09 (ozone maybe?) Tmobile
*D1 09 VZW
*Bionic 8GB 11 VZW
*Bionic 16GB 11 VZW

most of those changes were full retail unsubsidized, the ones I didn't like went to ebay since my esns were pretty much clear from day 1

still got my D1, may JB it this weekend

 

[Dave12308]

The HoB existed before that. Weeks before that, in fact. The FXZ was required because of the 235 security. We owe daywalker04 a huge debt of gratitude for giving us the FXZ that fast. It's enabled Matt's method of moving between leaks without being able to fully FXZ back.

That's right - it was in the "how to downgrade to .902" thread, IIRC. But I don't believe you had coined the name "House of Bionic" at that point. That's what had me confused. I thought it became "HoB" once you had it to the point where it was a "swiss army knife", so to speak, of Bionic repair.