Related
Latest and stable Wifi Driver for Android 2.1, Build SHOLS_U2_02.36.0
Build for the kernel "2.6.29-omap1"
** Stable and without any Wifi drop problem, which is compiled from the latest source from Google Android Repository. **
I recently found out that the Wifi driver of the latest Froyo 2.2.1 of Milestone that released by G.O.T. team is a new build and very stable. Therefore, I tried to pull the latest TIWLAN Wifi driver source code from the Google Android Source Repository (http://android.git.kernel.org/?p=platform/hardware/ti/wlan.git;a=summary), and compile it for the ROM build "SHOLS_U2_02.36.0", kernel "2.6.29-omap1".
I succeeded to compile as "tiwlan_drv.ko", and use it with the latest firmware "fw_wlan1271.bin" from the Froyo 2.2.1 build, and finally uses on the "SHOLS_U2_02.36.0", and the result is very stable wifi connection with the proprietary power saving feature .
I am using the ROM South Asia SHOLS_U2_02.36.0, I am not sure if it can be used with any other ROM, but normally should work on any kernel which have the version "2.6.29-omap1".
I did it because that the latest Froyo 2.2.1 beta ROM is not stable enough and the battery drain fast, but it have the stable wifi connection, so I compiled it for 2.1.
Enhancement:
Much more stable WIFI connection, no more connection drop within good signal environment.
No more WIFI freeze occur, will auto re-connect to AP if back to the signaled environment.
Much much much more battery saving (IT IS THE MOST IMPORTANT), can also feel that impressively in using "android-wireless-tether".
!!! Use it at YOUR OWN RISK !!!
Make a backup of "/system/lib/modules/tiwlan_drv.ko" and "/system/etc/wifi/fw_wl1271.bin".
Copy the file "tiwlan_drv.ko" to "/system/lib/modules/", and copy the file "fw_wl1271.bin" to "/system/etc/wifi/".
** WARNING **
Normally should work on any ROM which have the kernel version "2.6.29-omap1", BUT I didn't test it for any ROM other than SHOLS_U2.02.36.0, so USE IT AT YOUR OWN RISK!!!
It may result in bootloop in case if you did something wrong or not compatible with your ROM (need to revert back to the old driver with OpenRecovery + adb).
Therefore, it is only for advanced users, and ALWAYS MAKE FULL BACKUP of your milestone.
Download link:
http://www.sendspace.com/file/ln3xm7
Ooooo nice! The leaked rom did have superb wifi performance...
I'll give this a try on Telus' U2_03.11.0
[EDIT]What does fw_tiwlan_ap.bin do?
And the instruction for fw_wlan1271.bin is just a bit wrong... it's adb push fw_wlan1271.bin /system/etc/wifi/
[EDIT2]Woo! Works!
Lollipop_Lawlipop said:
Ooooo nice! The leaked rom did have superb wifi performance...
I'll give this a try on Telus' U2_03.11.0
[Edit]What does fw_tiwlan_ap.bin do?
And the instruction for fw_wlan1271.bin is just a bit wrong... it's adb push fw_wlan1271.bin /system/etc/wifi/
Click to expand...
Click to collapse
"fw_tiwlan_ap.bin" is the firmware required for the Froyo 2.2.1 to use Wifi Hotspot, it did nothing on Android 2.1, so just simply ignore it.
and Thanks for pointing out the location of placing the "fw_wlan1271.bin" file, I will modify it.
Lollipop_Lawlipop said:
Ooooo nice! The leaked rom did have superb
[EDIT2]Woo! Works!
Click to expand...
Click to collapse
Congratulation !!
You can use "dmesg" to see the new TIWLAN driver version
How can I copy and paste to the system?
Thanks!
royshum said:
Congratulation !!
You can use "dmesg" to see the new TIWLAN driver version
Click to expand...
Click to collapse
Thanks for your work!
I'll be putting it to the test on Monday when I get to my school campus. Stock 2.1 drivers never worked there and only 2.2.1 drivers work. Fingers crossed! Thanks for the info about the hotspot. Guess it's not very useful for 2.1 users...
How can I copy and paste to the system?
Thanks!
Click to expand...
Click to collapse
As long as you have adb setup, it's an easy task.
First, restart to recovery and do a backup:
Code:
adb pull /system/lib/modules/tiwlan_drv.ko tiwlan_drv.ko.bak
adb pull /system/etc/wifi/fw_wlan1271.bin fw_wlan1271.bin.bak
Then, unzip the files into your AndroidSDK/tools/ folder and push:
Code:
adb push fw_wlan1271.bin /system/etc/wifi/fw_wlan1271.bin
adb push tiwlan_drv.ko /system/lib/modules/tiwlan_drv.ko
adb shell reboot
Lollipop_Lawlipop said:
Thanks for your work!
I'll be putting it to the test on Monday when I get to my school campus. Stock 2.1 drivers never worked there and only 2.2.1 drivers work. Fingers crossed! Thanks for the info about the hotspot. Guess it's not very useful for 2.1 users...
As long as you have adb setup, it's an easy task.
First, restart to recovery and do a backup:
Code:
adb pull /system/lib/modules/tiwlan_drv.ko tiwlan_drv.ko.bak
adb pull /system/etc/wifi/fw_wlan1271.bin fw_wlan1271.bin.bak
Then, unzip the files into your AndroidSDK/tools/ folder and push:
Code:
adb push fw_wlan1271.bin /system/etc/wifi/fw_wlan1271.bin
adb push tiwlan_drv.ko /system/lib/modules/tiwlan_drv.ko
adb shell reboot
Click to expand...
Click to collapse
failed to copy - read only!
chungtau said:
failed to copy - read only!
Click to expand...
Click to collapse
You must have a rooted milestone in order to process.
Before you using adb push, try to remount your /system partition first.
Or you can try the following commands.
Ensure your wifi is turned off first.
*** Remember to make FULL BACKUP for your milestone before proceeding the following commands. ***
Code:
C:\android-sdk-windows\tools>adb push tiwlan_drv.ko /sdcard/tiwlan_drv.ko
C:\android-sdk-windows\tools>adb push fw_wl1271.bin /sdcard/fw_wl1271.bin
C:\android-sdk-windows\tools>adb shell
$ su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock6 /system
# cd /system/lib/modules
# mv tiwlan_drv.ko tiwlan_drv.ko.bak
# cp /sdcard/tiwlan_drv.ko ./tiwlan_drv.ko
# chmod 644 tiwlan_drv.ko
# cd /system/etc/wifi
# mv fw_wl1271.bin fw_wl1271.bin.bak
# cp /sdcard/fw_wl1271.bin ./fw_wl1271.bin
# chmod 644 fw_wl1271.bin
# mount -o ro,remount -t yaffs2 /dev/block/mtdblock6 /system
And now, you can try turning on your wifi.
In case if there is any problem occurred, you may reboot into OpenRecovery, revert the drivers from "tiwlan_drv.ko.bak" and "fw_wl1271.bin.bak".
I want to make a quick update and say that this indeed solves my campus wifi issues I have had with 2.1-based drivers.
I'm not 100% sure about the stability of the drivers though - I'm having a little trouble with maintaining a steady connection with SwiFTP.
[EDIT]I must stress, however, that in no way does this mean the new drivers are of any blame. Until I have the time to investigate deeply into this issue, it is an isolated incident that is only occurring within my network and is of no indication of the fault of the new drivers.
I have 2.2.1 milestone but it didnt work with me proper, I installed everything properly but i got error when i try to open wifi. then i restore my back up files but it still gives me eeror
Lollipop_Lawlipop said:
I want to make a quick update and say that this indeed solves my campus wifi issues I have had with 2.1-based drivers.
I'm not 100% sure about the stability of the drivers though - I'm having a little trouble with maintaining a steady connection with SwiFTP.
[EDIT]I must stress, however, that in no way does this mean the new drivers are of any blame. Until I have the time to investigate deeply into this issue, it is an isolated incident that is only occurring within my network and is of no indication of the fault of the new drivers.
Click to expand...
Click to collapse
It is glad to hear that the new driver solved your wifi issues .
Besides, are you still having the problem even after setting the "Wifi Sleep Policy" to "Never"?
In my experience, although the new driver is much more stable, but due to the highly power saving, it may still become instable (just in weak signal, not freeze nor wifi hang) if the AP have far distance to your mobile. In this case, you may try "WifiPowerSavingOff" from market to turn off the power saving feature.
But if you turned off the power saving feature for this connection session, it may drain your battery much much faster, so just use it in some trouble network .
hagizma said:
I have 2.2.1 milestone but it didnt work with me proper, I installed everything properly but i got error when i try to open wifi. then i restore my back up files but it still gives me eeror
Click to expand...
Click to collapse
You haven't read the instructions carefully. It is the latest wifi driver for "2.1", not "2.2.1", as it is supposed to compile the driver from "2.2.1" down to "2.1".
So for 2.2.1, by default, you are already have the latest wifi driver (at least a stable wifi driver), it is no clue for using it.
royshum said:
It is glad to hear that the new driver solved your wifi issues .
Besides, are you still having the problem even after setting the "Wifi Sleep Policy" to "Never"?
In my experience, although the new driver is much more stable, but due to the highly power saving, it may still become instable (just in weak signal, not freeze nor wifi hang) if the AP have far distance to your mobile. In this case, you may try "WifiPowerSavingOff" from market to turn off the power saving feature.
But if you turned off the power saving feature for this connection session, it may drain your battery much much faster, so just use it in some trouble network :
Click to expand...
Click to collapse
Yeah, it's always set to never ever ever turn off wifi unless I explicitly shut it off. For me, it seems like wifi is transferring in bursts or in intervals. After a while (roughly 5 minutes of heavy wifi activity like FTPing stuff), the phone will freeze up and it won't even automatically reboot. Of course, a quick battery pull and the problem is solved, but nonetheless the issue is still here. It *may* be my sdcard, since I've made a swap from a class 6 4GB to a class 2 16GB, but I'm not going to jump to conclusions just yet until I do some testing here and there.
Btw, CM6 uses the file name fw_wlan1271.bin. I'm guessing stock Android from Moto looks for fw_wl1271.bin (just guessing... can't exactly prove it since I'm not running stock Android), which was why I was trying to correct you (although it seems to me both of us are right).
hagizma said:
I have 2.2.1 milestone but it didnt work with me proper, I installed everything properly but i got error when i try to open wifi. then i restore my back up files but it still gives me eeror
Click to expand...
Click to collapse
If you're running 2.2.1-CM6 you can extract the files from the update zip and adb push them into the phone. That is, if you're on CM6. If not, well... you can either upgrade to CM6 or go into fastboot and restore the sbf again.
Lollipop_Lawlipop said:
Yeah, it's always set to never ever ever turn off wifi unless I explicitly shut it off. For me, it seems like wifi is transferring in bursts or in intervals. After a while (roughly 5 minutes of heavy wifi activity like FTPing stuff), the phone will freeze up and it won't even automatically reboot. Of course, a quick battery pull and the problem is solved, but nonetheless the issue is still here. It *may* be my sdcard, since I've made a swap from a class 6 4GB to a class 2 16GB, but I'm not going to jump to conclusions just yet until I do some testing here and there.
Click to expand...
Click to collapse
Very interesting what you are saying. I had the same suspicion due the fact that the sdcard is often not accessible, this again causes multiple attempts to write and fills the buffer.
Concerning the battery pull, you can reboot and wipe the protected storage area with a script, so that you don't need to pull out the battery (which at the end does nothing else but losing voltage, resulting in loss of temp data
MenoDev said:
Very interesting what you are saying. I had the same suspicion due the fact that the sdcard is often not accessible, this again causes multiple attempts to write and fills the buffer.
Click to expand...
Click to collapse
Yes, I have the same suspicion as well.
MenoDev said:
Concerning the battery pull, you can reboot and wipe the protected storage area with a script, so that you don't need to pull out the battery (which at the end does nothing else but losing voltage, resulting in loss of temp data
Click to expand...
Click to collapse
Can you go into a bit of detail on that? I'm interested
I've also had problems with the cell signal for 2.2-CM6. Again, I'm not sure the cause of it, but it's a very very serious issue that strikes at the wrong time. It seems like the cell radio freezes up even after a reboot with zero prior warning. So when I try to make a call, it doesn't go through. It's super frustrating, especially when there's really no good alternative to 2.2-CM6 right now. The only way to resolve this issue is to push the Telus baseband files again, but after a while it'll freeze up again. Ugh.
At least the Wifi works.
[EDIT]It seems like the cell problem is at least reported in the thread and acknowledge by other users. It seems to be fixed on 2.2.1-CM6, but since that's a little meh right now I'll have to dig around and see just what's causing the freeze.
[EDIT2]In fact, it seems like the problem is pretty widespread. Anything 2.2-CM6 based (that includes MotoFrenzy, Cronos...) has this problem.
works flawless, extreme improvement, thank you very much!
Lollipop_Lawlipop said:
Yes, I have the same suspicion as well.
Can you go into a bit of detail on that? I'm interested
Well, I use to code similar stuff but I am complete new to android so i have to read the dev guide, if I had no guide I'd probably create a dump, see according the file descriptor where the tables and storage are are located, then set a "write" flag on the file system and flush it to avoid a manual battery pull. but i'm sure there's more elegant ways.
I've also had problems with the cell signal for 2.2-CM6. Again, I'm not sure the cause of it, but it's a very very serious issue that strikes at the wrong time. It seems like the cell radio freezes up even after a reboot with zero prior warning. So when I try to make a call, it doesn't go through. It's super frustrating, especially when there's really no good alternative to 2.2-CM6 right now. The only way to resolve this issue is to push the Telus baseband files again, but after a while it'll freeze up again. Ugh.
At least the Wifi works.
[EDIT]It seems like the cell problem is at least reported in the thread and acknowledge by other users. It seems to be fixed on 2.2.1-CM6, but since that's a little meh right now I'll have to dig around and see just what's causing the freeze.
[EDIT2]In fact, it seems like the problem is pretty widespread. Anything 2.2-CM6 based (that includes MotoFrenzy, Cronos...) has this problem.
Click to expand...
Click to collapse
I made a little research and found a working solution, tested it myself.
Apparently it can happen that the resolved DNS can not be stored under certain circumstances, (in order to trace those, i try to avoid the "out of the box" mods, even though the guys make a tremendous job, but i feel more secure and have a higher learning curve by doing stuff myself).
In order to avoid random disconnects from network or wifi, or worst case both, add the following lines of code to /system/default.prop
net.dns1=8.8.8.8
net.dns2=8.8.4.4
net.rmnet0.dns1=8.8.8.8
net.rmnet0.dns2=8.8.4.4
These are the google dns, most probably the best choice. You can find this out if you fire up the "getprop" command.
I've seen that most Recovery tools such as the G.O.T one, have implemented the DNS fix, but personally I prefer to just fire up a terminal from the phone and add these lines manually with some comment, so i know what and why I'm doing stuff.
Hope this helps, let me know.
Please help! I succesfully copied both files using root explorer, but now I can't turn on wifi. Then I have restored the original files but it didn'tsolve the issue. I could do a nandroid restore but I really don't want to (last backup is quite old). I have a german milestone running 2.1 build SHOLS_U2_02.36.0
b787 said:
Please help! I succesfully copied both files using root explorer, but now I can't turn on wifi. Then I have restored the original files but it solve the issue. I could do a nandroid restore but I really don't want to (last backup is quite old). I have a german milestone running 2.1 build SHOLS_U2_02.36.0
Click to expand...
Click to collapse
If you followed the instruction you should have to *.bak files that you previously pulled, so no need to do a "panic rollback".
Did you turn of wifi before copying the kernel objects and made a reboot before turning on wifi as described in the howto ?
MenoDev said:
If you followed the instruction you should have to *.bak files that you previously pulled, so no need to do a "panic rollback".
Did you turn of wifi before copying the kernel objects and made a reboot before turning on wifi as described in the howto ?
Click to expand...
Click to collapse
I did turn off wifi before copying any files. However, I didn't rebooted before I tried to start wifi, only after I noticed it doesn't work.
Fix for 2.2.1 Possible?
I have the same issue with my home WIFI network on 2.1 and 2.2.1: namely the connection drops during large transfers (such as a Market app download) and I have to turn WIFI off and on again to have connectivity again.
I wonder if 2.2.1 really has the latest firmware baked in...how would I compile the TI firmware for 2.2.1?
Ok so I just installed Deca's battery tweak after coming from the normal collin_ph battery tweak.
I run this:
$ su
# batt-cfg
Click to expand...
Click to collapse
And then I get this... (Yes I'm rooted)
whoami: unknown uid 0
batt-cfg must be ran as root.
Press enter to atempt to run as root
Or press 1 then enter to continue without
attempting to gain root access
*I press enter not 1*
[: bad number
whoami: unknown uid 0
batt-cfg must be ran as root.
Press enter to atempt to run as root
Or press 1 then enter to continue without
attempting to gain root access
Click to expand...
Click to collapse
Do I have to re-root my phone? Or is something just messed up because I came from normal collin_ph battery tweak and then went to Deca's battery tweak...
But If I press [1] then it goes into the battery tweak config, but I'm not sure if it's working...
I'm thinking about switching to SetCPU but I really need some help with that. I have no idea how to use it, so my phone just freezes...
I even tried removing batt.sh but it says "cant find batt.sh" ...
Can I go to SetCPU?
Please help
Pwn3d said:
Ok so I just installed Deca's battery tweak after coming from the normal collin_ph battery tweak.
I run this:
And then I get this... (Yes I'm rooted)
Do I have to re-root my phone? Or is something just messed up because I came from normal collin_ph battery tweak and then went to Deca's battery tweak...
But If I press [1] then it goes into the battery tweak config, but I'm not sure if it's working...
I'm thinking about switching to SetCPU but I really need some help with that. I have no idea how to use it, so my phone just freezes...
I even tried removing batt.sh but it says "cant find batt.sh" ...
Can I go to SetCPU?
Please help
Click to expand...
Click to collapse
I believe it is batt-rm.sh to remove the battery tweak.
poashll said:
I believe it is batt-rm.sh to remove the battery tweak.
Click to expand...
Click to collapse
Ohhh thanks
Could anyone give me some tips on setCPU? I'd like to try it since people say its better.
EDIT: Just tried it out and setC freezed my phone...
Can you guys give me a link to Decas batt mod? ive looked EVVVERYWHERE
davidevan said:
Can you guys give me a link to Decas batt mod? ive looked EVVVERYWHERE
Click to expand...
Click to collapse
look at the bottom of the 2nd post of decad3nce's thread
http://forum.xda-developers.com/showthread.php?t=756774
You have a UID mismatch. In amon ra recovery there is an option to fix uid mismatch, so you could fix it that way. There is probably also a command you could run, if you find it, use adb and not the emulator, because thats your problem.
sent from my hero, which no longer sucks ass
I have sucessfully rooted my nook and I can load apks from dropbox, installers or via adb so I am a happy camper, all is good....
But I got greedy. The ComicViewer doesn't work well without menu keys so I decided to install softkeys.apk and that is where the trouble started, something is amiss.
I am not an expert here, just a novice, so forgive my patchwork explanation.
Here's what I know and what I did, maybe someone can spot my error?
I can fully access adb.
I remember installing SuperUser and SU using the commands:
# adb shell
# cd /system/bin
# mount -o remount,rw /dev/block/mmcblk0p5 /system
# cat /data/local/su > su
# chmod 6755 su
# ls -l su
And all was fine, SuperUser shows up in the drawer. Then I tried installing SoftKeys and it never showed up or worked.
So I figured I fubared the SuperUser install somehow or have an old version of SU or SuperUser. So I downloaded the most recent versions and went to uninstall the original with uninstall utilities and it's not listed in any of them, so I tried using adb (adb shell ls /data/app) and it's still not in the list.
I even reset the Nook to factory and rooted again with nooter and when I tried to install SuperUser again (downloaded the latest version here on the forum) it said "Install Failed already exists!"
So I cannot uninstall the SuperUser or overwrite it with a newer version, and a factory reset doesn't fix it??
I cannot use any root utilities like SuperUser or z4root, SuperUser has all blank screens and I cannot update it and 4zroot just doesn't seem to do anything but reboot the nook.
Titanium Backup says I don't have root access and other utilities say the same thing,
I can mount system partition as read-write
> adb shell
# mount -o remount rw /system
# exit
That works...
So I tried the commands again to install SuperUser and SU and when I try to install SU
# cd /system/bin
# mount -o remount,rw /dev/block/mmcblk0p5 /system
are OK but when I do:
# cat /data/local/su > su
I get:
Cannot create su: remote access failed
I have also tried a few other things that seem to be available to root users and all come back with write or access errors.
What could I be doing wrong?
Note: I also tried to do a full wipe by using that Power and Volume Down and nothing happens...
Power the nook on and off immediately 8 times until it does a full factory reset. When I've done the Power+VolUp+Nook button reset it doesn't always seem to do a FULL reset. When the nook fails to boot 8 times it does a different reset that takes a good deal longer and (at least in my experience) seems to be the real deal.
z4root will work and install superuser for you.
mhoepfin said:
z4root will work and install superuser for you.
Click to expand...
Click to collapse
I have already mentioned that that did not work, but thanks for the suggestion anyway.
Ok, something VERY weird is going on.
I have reset it to factory twice
Each time I did it by powering on and off 8 times in a row
The first time after it indicated it was updating th software, it went into a stuck at NookColor Logo boot loop again.
The second time I left in the nooter microSD card and it booted properly.
But it booted to a "clean" system with all my programs.
All my settings and data was gone, but all my apks were still installed.
So what exactly did it reset? Just data?
I tried to get it to flash both ways, the quick (power/home/volume) and now twice with the 8 power cycles. Neither reset the Nook entirely.
Am I screwed?
I want to go back to factory to fix this thing
EDIT:
Looks like I am locked out of the system entirely, none of my apps work, some of them come back and say no write access.
I cannot do an app listing like:
adb shell ls /data/app
I get:
opendir failed, Permission denied
I can't do a simple mount
mount -o remount rw /system
I get:
mount: operation not permitted
This should help you with what type of reset you want to do. I think you should do another 8 power on/off reset followed by a power-up-home reset to get it fully reset.
axe2 said:
This should help you with what type of reset you want to do. I think you should do another 8 power on/off reset followed by a power-up-home reset to get it fully reset.
Click to expand...
Click to collapse
I tried that...
Now it's completely dead.
Won't power up at all.
It had plenty of battery life left and plugging it in will not boot it either...
gormly said:
I tried that...
Now it's completely dead.
Won't power up at all.
It had plenty of battery life left and plugging it in will not boot it either...
Click to expand...
Click to collapse
Well that's a bummer! Maybe something went wrong in one of the resets. Did they seem to complete? If it's not a hardware problem you should still be able to revive it via nooter. I would suggest PMing pokey9000 and see if he can walk you through a recovery. You might be the first near brick that requires running some of the recovery commands by hand. I think Pokey9000 knows the most about that.
axe2 said:
Well that's a bummer! Maybe something went wrong in one of the resets. Did they seem to complete? If it's not a hardware problem you should still be able to revive it via nooter. .
Click to expand...
Click to collapse
Yea, but it won't respond to anything, it won't boot meaning no power at all.
It's just completely black screen.
Nothing I do does anything.
gormly said:
Yea, but it won't respond to anything, it won't boot meaning no power at all.
It's just completely black screen.
Nothing I do does anything.
Click to expand...
Click to collapse
Whatever you do make sure the battery is getting charged somehow.. Try to leave it plugged into the wall or in a usb. Does the computer see the device when plugged in? HAve you tried to remove the SD card from the NC while powering up?
norkoastal said:
Whatever you do make sure the battery is getting charged somehow.. Try to leave it plugged into the wall or in a usb. Does the computer see the device when plugged in? HAve you tried to remove the SD card from the NC while powering up?
Click to expand...
Click to collapse
Yep tried all those things...very frustrating afternoon so far
However...I did get it to boot.. here is how:
Press and hold the power button while inserting the USB charger connected to a computer, continue to hold (I think it was 10 seconds or so).
I remember doing this to reset a device a long time ago, not sure what.
But it worked, not only that but I was able to do a pwer/up/home rest and this time it completely wiped the nook. It looks like I am back to factory!
YES!!
Thanks for alll the help and suggestions guys. Hopefully this struggle will help someone else in the future.
gormly said:
But it worked, not only that but I was able to do a pwer/up/home rest and this time it completely wiped the nook. It looks like I am back to factory!
YES!!
Thanks for alll the help and suggestions guys. Hopefully this struggle will help someone else in the future.
Click to expand...
Click to collapse
OK. This time around, do this:
(1) nooter
(2) use ADB to enable Non-Market Apps
(3) use ADB to enable multitouch
(4) Use ADB to push z4root over to the NC
(5) Run z4root and do a full-root (whatever is NOT the "temp" option)
(6) Use ADB to install Astro
(7) Use ADB or Astro to install a market
(8) Install the rest of your apps however you choose.
johnopsec said:
OK. This time around, do this:
(1) nooter
(2) use ADB to enable Non-Market Apps
(3) use ADB to enable multitouch
(4) Use ADB to push z4root over to the NC
(5) Run z4root and do a full-root (whatever is NOT the "temp" option)
(6) Use ADB to install Astro
(7) Use ADB or Astro to install a market
(8) Install the rest of your apps however you choose.
Click to expand...
Click to collapse
I did 1,2,3,6,7,8 and in place of 4/5 I used the most recent version of SU and SuperUser and all is good on my Nook! Not sure what happened before but it must have been a bad version of su or superuser. In any case, all seems fine, only Titanium doesn't work, all the rest of the root requesting apps work fine.
Thanks!
http://www.addictivetips.com/mobile...-issue-on-a-rooted-android-device/#more-50317
check this out .. but the problem is when i load into recovery those same options dnt come .. if ne1 can do this procedure please explain me ..
rrohanjs said:
http://www.addictivetips.com/mobile...-issue-on-a-rooted-android-device/#more-50317
check this out .. but the problem is when i load into recovery those same options dnt come .. if ne1 can do this procedure please explain me ..
Click to expand...
Click to collapse
Check this out:
# Wipe Battery Stats. The following screenshots demonstrate how to wipe battery stats in ClockworkMod Recovery v2.5.0.7. Select advanced > Wipe Battery Stats > Yes – Wipe Battery Stats.
Click to expand...
Click to collapse
AFAIK, ClockworkMod Recovery is not available for Milestone.
Alternatively delete it manually.
Search for batterystat in milestone forum there's a lot to read.....
Good luck,
scholbert
Hi,
If you are root on your device you can use the terminal emulator to remove the batterystats.bin file yourself...
su [enter]
rm data/system/batterystats.bin [enter]
Beware, for the first few charge cycles your battery life may actually be worse, but it will improve. Ensure that you reboot straight after too.
Thanks for the tip.
Sent from my Milestone using XDA App
Sometimes 100% charged is not really 100% but actually it is only 60% charged. This mismatch happens when flashing new rom. Have you done the battery calibration either using zeppelinrox's method
http://forum.xda-developers.com/showpost.php?p=11803458&postcount=10
or my method below:
Step 1:
Boot up your phone normally and charge your phone as how you would normally do until it says "charged".
Step 2:
Once your phone charging status says "charged", unplug the wall socket cable from the phone. Shut the phone off.
Step 3:
While the phone is still off, plug back in the wall charger cable. Switch on the power of the wall charger.
Step 4:
You should then see the M logo for a while and then it shows the 100% green battery icon in the middle of the screen.
Step 5:
Open the battery cover and pull out the battery and wait for awhile until you see the "?" icon in the middle of the LCD screen.
Step 6:
Put the battery back in.
Step 7:
If your battery is OK (properly calibrated) then it would show 100%. If it is not properly calibrated, then it would show 60% and it will continue to charge your battery until 100%.
Step 8:
Once your battery has reached 100% (while phone is still off), leave it there to charge for another 15 minutes or until the battery is no longer hot. When the battery is cool to the touch, it means the charger has stopped charging the battery.
Step 9:
Unplug the charging cable and do the "3 finger boot" (x button + camera button + power button) to boot into recovery and flash the new ROM.
Doing so will calibrate the new ROM to the current state of the battery as 100% charged.
Somebody actually posted a video of it... I think it was androidve.com
I should find it again and update my post hehe
Ah... http://androidve.com/2011/03/androidcast-episodio-ocho-calibrando-la-bateria/
ther aint ne folder called system in the data folder .. i cnt find the batterystats.bin file to delete
you can use clockworkmod on milestone
just copy update.zip to /sdcard/OpenRecovery/update and run it
Dear Friends
i have galaxy tab 8.9 inch 32Gb
i need to downgrade from 4.0.4 to 3.2 because of battery problem
i did to 3.2 but still the same
now i need to flash 3.1
but
my device is 32gb should i use the same PIT.file labled P7300_P7310_p5_0614.pit or what
if i used former one it will not decreast the internal SD from 32 to 16 g
where i can get 32g pit file
thanks
For battery problem, switching roms won't help. Its a waste of time. The soln to this its here in the general section.
http://forum.xda-developers.com/showthread.php?t=1861229
Sent from my GT-P7300 using XDA Premium HD app
lrcquest said:
For battery problem, switching roms won't help. Its a waste of time. The soln to this its here in the general section.
http://forum.xda-developers.com/showthread.php?t=1861229
Sent from my GT-P7300 using XDA Premium HD app
Click to expand...
Click to collapse
Nothing usefull from that
Can u elaborate abt the battery pblm?
Sent from my GT-N7000 using xda premium
lrcquest said:
Can u elaborate abt the battery pblm?
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
i did but the battery voltage show 0.004V
i think there is a problem my be fixed with full rom
Inside android or in recovery? How did it get this low? Have u charged with phone off? Have u tried to take volt measurement in adb after charging?
Sent from my GT-N7000 using xda premium
lrcquest said:
Inside android or in recovery? How did it get this low? Have u charged with phone off? Have u tried to take volt measurement in adb after charging?
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
i did inside android
many program show this results as shown
Have u charged with phone off?
yes i did many times after i discovered this matter
Have u tried to take volt measurement in adb after charging?
yes correct measurement of voltage appear in 50% appear 3881
The adb measurement seems to be ok as the range is 3400 to 4100. U can get to recovery & wait / reboot till the voltage drops to near 3400. I have done this Eden faced with problems of battery on the stock ics twice.
Sent from my GT-N7000 using xda premium
lrcquest said:
The adb measurement seems to be ok as the range is 3400 to 4100. U can get to recovery & wait / reboot till the voltage drops to near 3400. I have done this Eden faced with problems of battery on the stock ics twice.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
i don't knew how to measure voltage in recovery mode using adb ?
i think there is problem
the command in my tab results in 3680 in 3% battery percentage ( only 4 digit)
but when i tried on my galaxy s2 results 3853750 in 42% ( 7 digit )
somaare said:
i don't knew how to measure voltage in recovery mode using adb ?
i think there is problem
the command in my tab results in 3680 in 3% battery percentage ( only 4 digit)
but when i tried on my galaxy s2 results 3853750 in 42% ( 7 digit )
Click to expand...
Click to collapse
first u need android sdk in your pc. download & install the same. it will be in "C:\Program Files (x86)\Android\android-sdk" in an 64 bit pc. in the command prompt go to this location. "C:\Program Files (x86)\Android\android-sdk\platform-tools"
from this point u can use the adb commands.
first check with the command "adb help"
u will get some responses.
u have to mount the system (in the cwm recovery) in the mount & storage section. then only will the device communicate with the pc in adb.
now connect the equipment (which is now in recovery mode) to the pc & use the command "adb devices"
u will get some sort of numbers instead of the 7300 or galaxy tab etc.
use the following command to know the voltage. "adb shell cat /sys/class/power_supply/battery/voltage_now"
pls note that there is a space in between "cat & /sys"
now follow the steps.
1. in CWM/recovery let it sit till battery in terminal will show less then 3700. The less you can get it the better. 3400 is probably absolute minimum.
2. shut down tab and let it sit for 1 hour. (this is needed for the first measurement)
3. plug it to charger and charge it for 5 hours.
4. disconnected charger and let it sit for 1 hour. (this is needed for the second measurement)
5. boot up your tab and test it, it your battery still not calibrated you can flash back your backup and repeat calibration procedure.
this is definitely a laborious process, but there is no option but to follow this.
hope this helps.
lrcquest said:
first u need android sdk in your pc. download & install the same. it will be in "C:\Program Files (x86)\Android\android-sdk" in an 64 bit pc. in the command prompt go to this location. "C:\Program Files (x86)\Android\android-sdk\platform-tools"
from this point u can use the adb commands.
first check with the command "adb help"
u will get some responses.
u have to mount the system (in the cwm recovery) in the mount & storage section. then only will the device communicate with the pc in adb.
now connect the equipment (which is now in recovery mode) to the pc & use the command "adb devices"
u will get some sort of numbers instead of the 7300 or galaxy tab etc.
use the following command to know the voltage. "adb shell cat /sys/class/power_supply/battery/voltage_now"
pls note that there is a space in between "cat & /sys"
now follow the steps.
1. in CWM/recovery let it sit till battery in terminal will show less then 3700. The less you can get it the better. 3400 is probably absolute minimum.
2. shut down tab and let it sit for 1 hour. (this is needed for the first measurement)
3. plug it to charger and charge it for 5 hours.
4. disconnected charger and let it sit for 1 hour. (this is needed for the second measurement)
5. boot up your tab and test it, it your battery still not calibrated you can flash back your backup and repeat calibration procedure.
this is definitely a laborious process, but there is no option but to follow this.
hope this helps.
Click to expand...
Click to collapse
thanks i will try again today
lrcquest said:
first u need android sdk in your pc. download & install the same. it will be in "C:\Program Files (x86)\Android\android-sdk" in an 64 bit pc. in the command prompt go to this location. "C:\Program Files (x86)\Android\android-sdk\platform-tools"
from this point u can use the adb commands.
first check with the command "adb help"
u will get some responses.
u have to mount the system (in the cwm recovery) in the mount & storage section. then only will the device communicate with the pc in adb.
now connect the equipment (which is now in recovery mode) to the pc & use the command "adb devices"
u will get some sort of numbers instead of the 7300 or galaxy tab etc.
use the following command to know the voltage. "adb shell cat /sys/class/power_supply/battery/voltage_now"
pls note that there is a space in between "cat & /sys"
now follow the steps.
1. in CWM/recovery let it sit till battery in terminal will show less then 3700. The less you can get it the better. 3400 is probably absolute minimum.
2. shut down tab and let it sit for 1 hour. (this is needed for the first measurement)
3. plug it to charger and charge it for 5 hours.
4. disconnected charger and let it sit for 1 hour. (this is needed for the second measurement)
5. boot up your tab and test it, it your battery still not calibrated you can flash back your backup and repeat calibration procedure.
this is definitely a laborious process, but there is no option but to follow this.
hope this helps.
Click to expand...
Click to collapse
thanks alot
i did that using my current installation just need to mount system to work on recovery mod
i downgrade to 3.1 using 5 files and update to 3.2
and i did the previous instruction and the battery now is very good and no fake percentage
But still fake voltage even using adb
see the attachment
i think my be some fail in files measure voltage
today morining to disconnect battery for 10 minute but the same problem
any program for the battery show voltage in MVor 0.00? V
U can use battery monitor widget. Always good measurements & worth timeline also.
The second voltage from the s2 might be divided by 1000 to get the right value.
Sent from my GT-N7000 using xda premium