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

The BIG 2.1 Thread

Fadelight said:
No problem... glad I could help!



OFFICIAL NEWS - The problem with the keyboard lights has been fixed.

(If anyone else has an easier way, let me know. This is just how I did it.)


As always - Proceed at your own risk.

libhw.zip


Most people suggest taking steps to back up your phone, but lets face it... at this point in the game, anyone who would be doing this has probably got everything backed up with Nandroid anyway, so I am just going to skip it.

First, plug your phone into your PC and mount the SD card. Extract contents of the zip folder to the root of your SD card. (Not inside the folder... each file individually.) Unmount the card. (Make sure your phone is plugged in and in debug mode)

Open a command window, switch to adb shell


Here are the commands to type out as follows:

su

mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system

busybox cp -R /sdcard/gralloc.default.so /system/lib/hw

busybox cp -R /sdcard/gralloc.omap3.so /system/lib/hw

busybox cp -R /sdcard/lights.sholes.so /system/lib/hw

busybox cp -R /sdcard/overlay.omap3.so /system/lib/hw

busybox cp -R /sdcard/sensors.sholes.so /system/lib/hw

cd /system/lib/hw

chmod 644 gralloc.default.so

chmod 644 gralloc.omap3.so

chmod 644 lights.sholes.so

chmod 644 overlay.omap3.so

chmod 644 sensors.sholes.so

sync

reboot


The ZIP was provided by Greek35T at Alldroid. All thanks go to him.
Click to expand...
OK... I'm trying to patch the keyboard lights (thanks for the files, BTW), but I think I missed a step somewhere. When I attempt to go to adb shell, I'm getting...

sh: /sdcard/bash_profile: Permission denied
sh-3.2$

This is my first attempt at doing anything to the phone since installing 2.1V1.
 
dja1980 said:
OK... I'm trying to patch the keyboard lights (thanks for the files, BTW), but I think I missed a step somewhere. When I attempt to go to adb shell, I'm getting...

sh: /sdcard/bash_profile: Permission denied
sh-3.2$

This is my first attempt at doing anything to the phone since installing 2.1V1.
Click to expand...



Think you've missed "SU".


Don't follow those directions anyway. It wasn't a permanent fix, only a temporary solution. They are still working on a permanent fix, but a better solution has come up for the time being anyway.




Here are the goals of the temp fix and status of it.

1. Control backlight on and off - DONE
2. Turn on when system on, off when asleep - DONE
3. Turn off backlight when keyboard is not out -Not Implemented
4. Enhanced power management with keystroke event integration - Not Planned for implementation
Click to expand...


I'd do a writeup, but things are getting way too chaotic in this thread at the moment, so I am going to hold off for now.
 
Fadelight said:
Think you've missed "SU".
Click to expand...
I'm not sure what "SU" is... I don't remeber using that when installing 2.1... again I've VERY new to all this tinkering :o

Anyway, I get the message I posted above after I go to the command prompt and cd to c:\android\tools. I get to that directory fine, but the error comes after I put in "adb shell" and press enter.

7. Boot phone into recovery, leave it plugged into your comp
8. Open command prompt on your comp
9. Type cd C:\android\tools and press enter

You know what... I just realized after pasting that, that I wasn't in Recovery. I'll hold off on using the previous instructions, but am I on track for when I install the future patch?
 
dja1980 said:
I'm not sure what "SU" is... I don't remeber using that when installing 2.1... again I've VERY new to all this tinkering :o

Anyway, I get the message I posted above after I go to the command prompt and cd to c:\android\tools. I get to that directory fine, but the error comes after I put in "adb shell" and press enter.

7. Boot phone into recovery, leave it plugged into your comp
8. Open command prompt on your comp
9. Type cd C:\android\tools and press enter

You know what... I just realized after pasting that, that I wasn't in Recovery. I'll hold off on using the previous instructions, but am I on track for when I install the future patch?
Click to expand...


su means "superuser". when you enter your adb shell, it has to be the very first thing you type. The second needs to be remounting your phone with read/write permission rather than read only. Either of these two steps would cause the error you are talking about.


In the second post which I quoted, you have quoted my directions for something completely different. You do not need to boot into recovery to do this. Simply plugging your phone in will do quite nicely.

Make sure you are not missing these steps. Remember, they should be the VERY FIRST thing you are typing after you enter adb shell.

su

mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
 
Ah, ok.

Installing 2.1 to my phone was the first thing I have ever done. So, when I saw in your instructions to "Open a command window, switch to adb shell", I went back to the instructions I used to install 2.1 to get to adb shell (steps 7,8, & 9).

I'm learning as I go... and having fun doing it... I think I'm just missing the basics.
 
Hmmm... I think I give up for now. Is there a 101 thread for this type of stuff anyone can direct me to?

Here are the line-by-line steps I'm attempting... and failing...

1. Settings ->SD card & phone storage -> Unmount SD card.
2. Plug phone into PC via USB (USB debugging connected).
3. Open command prompt on PC.
4. type "cd C:\android\tools" and press Enter.

It changes to the correct directory, but this is the point where I get locked up. Here are the different things I have tried as the next step...

5. type "adb shell" and press Enter
Permission Denied

5. type "adb shell su" and press Enter
su: access granted courtesy of magicandroidapps.com
sh-3.2# (It won't let me type anything after this even though curser continues to blink)

5. type "adb shell su mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system" and press Enter
su: access granted courtesy of magicandroidapps.com
su: exec failed for -o Error:Permission denied
C:\android\tools>

Also, when I open Terminal Emulator from my Apps, I get the same "Permission denied" error immediately.

I'm sure it's something stupid I missed... maybe I'll play some more later.
 
So I flashed humancyborg's new 2.1 ROM, gotta say it is noticeably faster and the keyboard backlight is much more stable now. I'm loving it so far.
 
I've been reading about it. I think I might do that tonight after work to see what is what. I'd do it now, but I need my phone for work.
 
Fadelight said:
I've been reading about it. I think I might do that tonight after work to see what is what. I'd do it now, but I need my phone for work.
Click to expand...

If you get 3G or WiFi at work then you can do it up, all you gotta do is download it (get the one with SU already in it) then put the BCDMRS-20091231-0912 in the nandroid folder (not consoletty if you have the newer recovery like 0.15.0) and do a advanced restore and choose it. It is really good, better then Greek's IMO.
 
CRPercodani said:
If you get 3G or WiFi at work then you can do it up...
Click to expand...


I'm not sure that would be a good idea... I am a courier. I think the roads will be unsafe enough tonight with all of the drunk drivers and the snow storm... I don't think anyone needs me driving around dodging drunk people in 4" of snow while trying to load a new ROM on my phone. :D
 
The programming menu doesn't work so no EVRC-B or 13K for now, not that the call quality was shoddy to begin with, I just like changing it :D

There's a fix floating around Alldroid that worked for Greek's ROM, it will probably work for this one too, but I have to run so I can't try it now.
 
Fadelight said:
I'm not sure that would be a good idea... I am a courier. I think the roads will be unsafe enough tonight with all of the drunk drivers and the snow storm... I don't think anyone needs me driving around dodging drunk people in 4" of snow while trying to load a new ROM on my phone. :D
Click to expand...

What do you courier at this time of night in Maine? Dead moose?
 
Quick question I just installed busy box on 2.1 recently I used metamorph to put a hero theme on my droid but I forgot to back upbefore I applied the theme :( anyways I wanted to revert back to 2.0.1 to test out a theme but on nandroid don't you have to wipe your system before applying a back up? if I wipe will I lose the busybox install? I want to know because I was trying to install busybox for days and I just recently got it and I don't wanna lose it plus I don't really remember how I did it luck I guess ..anyways thanks in advance :)
 
Does anyone know if the 2.1 gallery will work on the mytouch 3g (android 1.6) have a few friends with it and they like the new gallery
 
CRPercodani said:
What do you courier at this time of night in Maine? Dead moose?
Click to expand...

lol close. Meds to nursing homes.

Just getting home... we had an early call time tonight. Usually I get home about 2-3am.


I just flashed to the new ROM, and it is currently syncing. After it is done, I'll have to go through and double-check to make sure all of my apps were automatically restored. (They haven't all been restoring lately.)

When that is over, I will go after the framework-res.apk, since this default one is ugly as crap and has the VZ eri. UGH. lol.
 
DroidJnkie said:
what's the problem with handcent in 2.1? I'm running it on 2.1 and it seems the exact same as on 2.0.1
Click to expand...

you'll notice after a few days. iIthought it was just handcent until I saw others mention it was 2.1, and I veridied after reverting. Forgiv e the bad typing, the droid seems to hate posting here.

And for the guys waiting for my seal of approval, I hope that wasn't sarcastic because I take my seals seriously. (And the hc dump had only been out for a few min so I thought id post impressions to save people posting asking for them)
 
This thread had turned into Frankenstein...

Anyway, I installed 2.1 last night and I am loving it so far. Picasa synching with the Gallery is awesome. I like the new Contact shortcut method as well. It now pops up the opinions only instead of going to the contact page.
 
Deja Vu.



The newer 2.1 dump is a lot better. I just barely finished setting it all up the way I want it. I can't really say it is faster... it seems about the same as the Geek35 rom. The backlight seems to work perfectly, though. no FCs so far. It seems quite nice.
 
Fadelight said:
Deja Vu.



The newer 2.1 dump is a lot better. I just barely finished setting it all up the way I want it. I can't really say it is faster... it seems about the same as the Geek35 rom. The backlight seems to work perfectly, though. no FCs so far. It seems quite nice.
Click to expand...
This is a different file from the greek35t rev 4? Where is everyone finding these different 2.1 version and such? im not up on my droid 2.1ness yet. lol
 
gotwillk said:
i remember reading that 2.1 is an update for ALL phones currently using android, so it's not just for us droid users. not sure if there are any significant or specific updates for droid itself but this is pretty much by and large, an upgrade for all android users. especially for the ppl using 1.6. they don't even get 2.0. just gonna skip straight to 2.1.
Click to expand...

Google's releases of Android are not tied to specific products (well, they can include enhancements for certain form factors as a result of a partnership with certain manufacturers, but the model is to just continue to improve Android agnostic to any devices out there). When the new version of Android is released, it's available to any manufacturer that released products on the previous releases, and up to them to figure out whether it makes sense to do the work to upgrade the current units to that new version. So it's not correct to say that 2.1 is for 1.6 users - 2.1 is for all Android phones, and 1.6 users are not more or less likely to get 2.1 than any other users. The thing that makes the difference is whether the phone you have is a "Google Experience" phone (G1, DROID) or has been significantly enhanced by the manufacturer (CLIQ, Sense UI phones). When these non Google Experience phones get upgraded is a function of whether a) the new version of Android still would fit within the phone's physical constraints (like memory availability) and b) the cost to upgrade all the custom code to the new API changes made in the new underlying Google release is less than the benefit to the manufacturer to do the upgrade. Remember that you are not actually PAYING anything to the manufacturer for these upgrades, so it's basically just a goodwill thing if Motorola or HTC do the upgrade at all. Goodwill can be worth a lot, as users have an expectation that they'll be updated, but if it costs $100M to do the upgrade (I'm exaggerating to make a point) then they won't bother.
 
Berry2Droid said:
This is a different file from the greek35t rev 4? Where is everyone finding these different 2.1 version and such? im not up on my droid 2.1ness yet. lol
Click to expand...

Yep... vastly different from Greeks roms.

I can't tell you where to find it, but if you know where to look for Greeks release, then you are in the right place. ;)
 
You must log in or register to reply here.
Back
Top Bottom