• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root white widow 4.0?!?!!?

i removed JIT, its unstable and slow, thats why the linpack scores are low. linpack ca be manipulated to show whatever you want. its not a true speed benchmark.

the md5sums i havent had a chance to post up there yet, i literally put it together in less than an hour.

if your touchscreen goes out frisco, check the patches section. i have a patch for that. it fixes your ts and no longer breaks wifi or softkey lights.

sorry if i missed anyones comments, post agian and ill get back o you


im also working on getting a contact form on the website so you can contact me straight from there
 
This is quite interesting. I'm trying a fresh download of WW 4.1 and sitting here looking at that Nexus One boot animation for 11 minutes now.. coming up on the 12 minutes I quit on earlier today.

I'd sure like to know the specifics of what causes some ROMs to be unable to install on some phones.. I've had great luck with EE and Senseable and the original and Lightning.

12 minutes now.. when should I abort? :rolleyes: :D


[edit] Well, that's that. I had to do a battery pull, no responses from buttons or volume toggles.
 
alprazolam said:
Andrizoid...I have one issue that is becoming sort of a big deal for me. When talking on bluetooth, the screen goes to sleep. No big deal there. Well, if I try to wake it up to, say turn the in-call volume up or down or to try to look something up, I hang up on the person. Is there any way to set the ROM so that one press wakes the phone and a second press hangs it up? Also, what happened to the "number block" on the dialer? That was a very handy feature that I used in 3.1.
Click to expand...

Andrizoid...I called Charter today and needed to use the dial pad. No can do because the phone lcd was off with no way to turn it on without cutting off the call.
 
alprazolam said:
Andrizoid...I called Charter today and needed to use the dial pad. No can do because the phone lcd was off with no way to turn it on without cutting off the call.
Click to expand...


sounds like the proximity sensor isnt working, let me look into few things. im on vacation with my family so i havent been able to do a whole lot :/
 
Frisco said:
This is quite interesting. I'm trying a fresh download of WW 4.1 and sitting here looking at that Nexus One boot animation for 11 minutes now.. coming up on the 12 minutes I quit on earlier today.

I'd sure like to know the specifics of what causes some ROMs to be unable to install on some phones.. I've had great luck with EE and Senseable and the original and Lightning.

12 minutes now.. when should I abort? :rolleyes: :D


[edit] Well, that's that. I had to do a battery pull, no responses from buttons or volume toggles.
Click to expand...

do you know how to do a logcat frisco?
plug your phone in
cd to sdk tools
adb logcat
then turn on the phone. copy and paste the report onto a pastebin for me and ill help you out
 
andrizoid said:
do you know how to do a logcat frisco?
plug your phone in
cd to sdk tools
adb logcat
then turn on the phone. copy and paste the report onto a pastebin for me and ill help you out
Click to expand...

Thank you, andrizoid. I'll do that today.

[edit] You must mean to do that with WW booting up. I got rid of WW, but I'll do a dry run to see if I can generate the logcat in case this happens again with another ROM (I tried 4 unsuccessful flashes of WW 4.1).

I'll try it with my (for now) default Senseable 3.1
 
Frisco said:
This is quite interesting. I'm trying a fresh download of WW 4.1 and sitting here looking at that Nexus One boot animation for 11 minutes now.. coming up on the 12 minutes I quit on earlier today.

I'd sure like to know the specifics of what causes some ROMs to be unable to install on some phones.. I've had great luck with EE and Senseable and the original and Lightning.

12 minutes now.. when should I abort? :rolleyes: :D


[edit] Well, that's that. I had to do a battery pull, no responses from buttons or volume toggles.
Click to expand...

That's really strange Frisco. I've flashed every ROM available and some testing builds, and have never had a problem besides when I downloaded a ROM file it ended early but I thought it was done so I had problems there, re-downloaded the file checking to make sure the Mb is correct. and never had problem since. every one is difference obv. and so are phones, Best of luck, I'd try re-downloading the file but I'm sure a man of yourself has already tried that.
 
Yeah, I sure did re-download the WW 4.1 file: three different times.

What I have not done, though, is an md5 checksum match.

I had it happen a few times when downloading linux distro iso files to my laptop, via wireless router, it came up with problems and then turned out the hash was off.

Later today I'll get the file using a PC in the house. I'm now nearly certain that has been the problem.
 
Downloaded and flashed a fresh 4.1.

It booted quickly this time, went to the SU permissions screen for a "killer" app, now is stuck on "Welcome to Eris - Touch the android to begin."

The touch screen does not function.
 
Frisco said:
Downloaded and flashed a fresh 4.1.

It booted quickly this time, went to the SU permissions screen for a "killer" app, now is stuck on "Welcome to Eris - Touch the android to begin."

The touch screen does not function.
Click to expand...

Go to andrizoids web site above and get the touchscreen patch. You'll have to copy it using recovery and then flash the zip. That will get you going !!

Andrizoids Space - **** the Haters
 
You must log in or register to reply here.
Back
Top Bottom