yashsingh1/xdaforums huggingface dataset:
[HD2 General] Cyclonezephyrxz7:
Hmm...I had read that I should turn off the backlight auto-control and install "AutoBacklightSteps" (or "AutoBacklight") ... That is what I have now at least ...

Right now I have brightness set to 20% [on battery], and higher on external power. Auto- is turned off. I use the app to change the backlight setting when I need to, although I often don't.

Now I don't personally use phones very very often. Seeing as I am in school, and one of the few kids who actually takes notes and doesn't text in class, I will use it for maybe 30 minutes at most [cumulatively] from 7AM to 3PM. Today, I used my phone as I think I normally would ....actually probably much less. In any case, it is now 10:33 here and I have 55% battery life. This is how I ran the phone for the day:

6AM : Took the phone off the charger [100%]

6AM -> 7:30AM : Phone left relatively un-touched. [98%]

7:30 AM -> 2:45 PM : the "Phone" [in comm manager] is off, in 'Airplane Mode' ... relatively low use [@ 2:45 -> 89%]

2:45 - 3:30 : I had 'Phone' on, received text messages I had gotten throughout the day, then turned it off [87% / 88% ... my memory is a bit fuzzy]

3:30 - Now : I generally had the 'phone' off, and I was in airplane mode. I intermittently turned it on.. I played some games, watched some moves [with Window Media Player] (I literally watched like 5 minutes of Transformers to show off to my friend haha, then I was done with that) Not much else...

All day the screen's brightness was at 20%. I used the LEDs for some flash photos, and the flashlight very rarely. I did take a couple of photos randomly thoughout the day ... but that was it. Right now, [after having the phone ON for about 30 min], my battery is at 55%.

I have to say that isn't too bad. Maybe the reader just wasn't that accurate yesterday, or I was doing a lot more than i though I was hehe [Could be file transfers and such]... In any case ... is this normal? I do expect to use the device more and more later on, I will text more and such [use Web sparingly as I know it eats battery] ... if I can manage to get though a day without losing power entirely I'll be happy haha.

Oh, and just some 'stats' : Today I placed 5 Phone Calls, received/sent 10 SMS, used internet for maybe 15 Minutes. That is basically it [since I know that probably affects seeing if battery consumption is normal].

PS: If you noticed I have the phone in Airplane mode a lot, it is because the signal for T-Mobile doesn't get into my school ... something about the dropped ceilings or just the architecture prevents the signal from entering, so I just generally leave it in airplane mode.

In any case, I would like to thank you guys a lot for already responding to my prior post :) :)
[Captivate Q&A, Help & Troubleshooting] sinichi21:
Is the Android ID and Device ID the same? and if i flash the 2.2 froyo leak using 1 click odin which of the 2 will be the problem?
[Captivate Q&A, Help & Troubleshooting] dayv:
First go to the market and get "android id changer" and "device id"app, both of these are for your device id - which is the bug in the leaked froyo and the roms built on the leaked froyo.

Before you flash anything use the device id app to get your id and write it down. Then after you flash you can use android id changer to change your id back to what its supposed to be.
[Captivate Q&A, Help & Troubleshooting] sinichi21:
So just to clarify the device ID and android ID are the same right? cause i download an app called ID it give you a lot of info and i see the device ID and android ID are different the device Id is my IMEI. so if I flash the leak 2.2 my IMEI will remain the same right? just the android ID will be bug
[Captivate Q&A, Help & Troubleshooting] dayv:
Ya I got wrong in my previous post - both of those apps are for your android id - which is the bug in froyo leak

Your IEMI - device Id should be fine
[Captivate Q&A, Help & Troubleshooting] Rhiannon224:
You need Android Device Id app, that gets your unique code.
[Captivate Q&A, Help & Troubleshooting] dayv:
Open all three apps and compare three number that populates - this is android id

It may be a good idea to write down all four numbers from the id app to keep if you are going to flash just in case: but I am pretty sure the android id is the only one that does not regenerate correctly when flashing the froyo leak and the android id changer app will allow you to manually fix this
[Captivate Q&A, Help & Troubleshooting] sinichi21:
This the odin flash right? not the ROM Flash. btw do i keep my unlock code on odin flash?
[Captivate Q&A, Help & Troubleshooting] dayv:
If you flash any of the roms built on the froyo 2.2 leak you will have this issue with android id, some of the cog 2.2 betas are odin flash, some are rom manager clockwork flash and I think with cog 2.2b8 you have the option for either, and no matter which one they all have the android id bug.

I'm not sure about your unlock code - I believe I have seen on here that you will have to reapply that, but I really don't know myself about this for sure - you will need some info from someone who has unlocked their phone. Check the cog thread for unlock code someone has probably posted info about unlock code in there.
[Captivate Q&A, Help & Troubleshooting] spartan062984:
Newb Q: Besides the fact that it is a known bug in the Froyo leaks, what purpose does the Android Id serve again? I thought i read somewhere that it only relates to the Market....?
[Captivate Q&A, Help & Troubleshooting] JOe K.:
I'm a little confused as well. I upgraded to Cog2.2B6 at the beginning of the month. I didn't see anything in the install wiki (at the time) to log an Android and Device ID.

Is there anyway I can recover my ID? What is the ID for? With my version of Cog was the deviceID over written?

Thanks,

JOe K.
[Captivate Q&A, Help & Troubleshooting] Chargerdude70:
+1........
[Captivate Q&A, Help & Troubleshooting] Krad:
woudl like to know as well.
[Captivate Q&A, Help & Troubleshooting] klloyd:
I've read some people have been able to regenerate the id by going back to stock, then doing a factory reset. Get the id and write it down. Then u can run cognition and change your id to what it really is. I can try it tonight or tomorrow, as I don't have anything special installed.

DONT FORGET!!!! If you are running cog with voodoo, disable voodoo first!!!!
[Captivate Q&A, Help & Troubleshooting] Sulphur4724:
This is what i did. worked like a charm. The only thing I'm personally sure it effects is interaction with the market and any app that uses it to identify you before you can use it. Mostly heard about a few games. For sure it will bork Fast Web Install for use with Appbrain.

This! I'd look long and hard for an answer to your unlock code. I distinctly remember someone in cog thread havin' a hissy fit over it.

I'm pretty sure the IMEI (??) code is on your sim card. Which you should pull before you start muckin' with stuff. :)
[Captivate Q&A, Help & Troubleshooting] ianwood:
IMEI is the unique ID of the device hardware. It is part of the GSM standard.

IMSI is the unique ID associated with your SIM and is used to identify the subscriber. Also part of the GSM standard.

The Android ID is specific to Android and is used to uniquely identify the device and user.
[Captivate Q&A, Help & Troubleshooting] Sulphur4724:
Excellent. Thanks for clearin' that up!
[Captivate Q&A, Help & Troubleshooting] klloyd:
Seeing thag in cog. 9 there is no voice to tell me voodoo is being disabled, how would I know its truly disabled? I went throught the steps so I can go back to stock, but I have no sure way of knowing I'm afraid... that's all I need, then ill do the stock-reset thing and see if it works.
[Captivate Q&A, Help & Troubleshooting] Sulphur4724:
From a terminal or adb shell type this. mount | grep data

/data should be ext4
[Captivate Q&A, Help & Troubleshooting] klloyd:
yes, sulfer is correct. I have went from cog 9 back to stock, and it gave me a new ID. So it can be undone...
[Captivate Q&A, Help & Troubleshooting] Neo-ST:
Hi, I have SGS i9000 that I flashed with this ROM. I never wrote down my ID while I was on stock ROM, just installed this one over it.

I have a problem with Kik messenger, which doesn't work properly (doesn't always receive messages). When I told them about it, this was their reply:

In the end of the reply is the link to this thread.

I don't really know anything about these ID's, could you please assist. What do I have to do to set these ID's properly? I just need to get this messenger running normally....

Thank you!
[Captivate Q&A, Help & Troubleshooting] alphadog00:
As mentioned above, if you lost your id, you need to revert to stock and do a reset. The captivate is easy - there is one click ROM. For the SGS i9000 you should check on those forums as to how to revert to stock, or if they have another idea on how to fix your ID.

If you have your ID, then you use the ID changer mentioned on the first page.
[Captivate Q&A, Help & Troubleshooting] Neo-ST:
I don't have the stock rom.... :/
[Captivate Q&A, Help & Troubleshooting] chtamina:
does this apply to htc desire as well ?

I'm having similar problems with kik messenger and MIUI
[HD2 General] Alize:
Been a user of HD2 since release and follower of xda since then!

Been using Android on HD2 as much as possible last few months...now....I own a Desire HD!

Thanks to the developers here, I've happily converted to Android full time!

Thanks again developers, hello Android!

For anybody else getting rid of their HD2 in the UK, if you go on mobilevaluer.com, you can trade it in for £170 cash! I'll be doing that :)
[HD2 General] Wdave:
Why does this seem like a plug for that service?
[HD2 General] m4sta2k:
Does it look like we care?
[HD2 General] hagba:
Same here,my son installed Android on his HD2,since than never used WM part of the phone,he liked it so much that will get the Desire HD.
[HD2 General] Alize:
MobileValuer.com doesn't take any money, it is just like comparethemarket.com and confused.com. It compares offers from all of the sites that recycle phones like Envirofone etc, so I don't see any value (no pun intended) in advertising the website!

I'm sure ill see many regular posters from HD2 in the DHD forums ;) I'm loving Android now!
[HD2 General] Archer:
Serious question though, is Android on the Desire HD any better than running a Desire HD ROM on the HD2?
[HD2 General] MykeChester:
a very good question...
[HD2 General] hagba:
Just the camera I guess.Everything else working perfect.
[HD2 General] Alize:
Yes, far better.

HD video recording - camera is by far better.

Battery lasts longer when using Android.

Android is a lot smoother (possibly because of the 800mb of RAM). Also read the DHD has a much better GPU and newer CPU.

Official support as well (although sometimes support by the devs at xda is better :P )

I also had reliability problems with all builds I've tried on HD2, I've tried 4 different radio versions as well as about 6 different builds, my favorite and most stable one was shubCraft's however, after about a week of use, I would have to reformat and start again as black screen of death would occur more and more frequently the longer I used a build.

To be honest, I got a little bit sick of supporting and tweaking my phone, normally I would love to spend hours tweaking, but now I'm at Uni full time and trying to work full time as well as run a house - so I never find the time to do the tweaks I want to do!

Looks wise, I definitely think I've downgraded, the Desire HD is hideous compared to the beauty of the HD2, but I prefer functionality over beauty (although not when it comes to operating systems!)

HD2 is a brilliant phone though - as long as you have the time to spend on it and tweak it, fix it and support it.
[HD2 General] Archer:
Thanks for getting back to us - it's good to get a good idea from someone that has used both the HD2 version and the real version.

It's pretty much what I expected, but I'm still sticking with the HD2. I think I'll probably have Gingerbread before you ;)

Cheers, and have fun with your new phone :)
[HD2 General] evolutionqy7:
agree lol

why do people actually bother making these posts?
[HD2 General] raziel123:
HD2

You must be of your rocker,

I just checked that website, it valued my Fully working HD2 for £114!!! :eek:

the phone cost over £400 quid and I'm gonna sell it to them for £114 ...

lol,

In anycase, I'm not selling it, as long as XDA developers supports the phone ... :cool:

The only thing the Desire HD has over the HD2 is HD recording, and the Adreno 205 graphics Chip ...

don't be suprised if XDA get HD recording working ... :D

graphics performance is pretty descent anyway ...

regards

Raz
[HD2 General] OrionCarl:
after my mate had a play with my HD2 on android, he decided to buy a htc!sadly the HD desire, but its a pukka phone, system runs beautifully. Can make a man change his mind...but im sticking with the HD2,
[HD2 General] troed:
Why not have the best of two worlds ?

Having Android on the HD2 and wait until Samsung issues the Galaxy S2, keep the HD2 and have both to play :D:D:D:D
[HD2 General] Archer:
What are you talking about? I think it's you who is

off

their rocker ;)
[HD2 General] SreePillai:
i think it's nice to have the views of someone who has used both the phones on android...and i think it's just made me that much surer that i'm sticking with my HD2 for now..with xda chefs the possibilities are endless.
[HD2 General] OrionCarl:
I think the hd runs android tonnes better then the hd2, but im sure it will be on par soon enough
[HD2 General] lude219:
Of course android running natively on the DHD is a lot better than the gimped android we run on HD2. With the obvious aside, I dont think you're missing much other than the camera.
[Nexus One Android Development] houzuoguo:
Few months ago, there was a post on XDA:

http://xdaforums.com/showthread.php?t=718952

and a link to:

http://nexusonehacks.net/nexus-one-hacks/how-to-install-ubuntu-on-your-nexus-oneandroid/

They explain how to install and run Ubuntu on Nexus One.

But a lot of people got problems when running script bootubuntu and ubuntu.sh, and I was one of them.

After Cyanogen Mod 6.0 was released, I could successfully run Ubuntu according to given instructions, but later I discovered the two scripts (ubuntu.sh and bootubuntu) don't always work, and I found them very complex and unnecessary statements can be removed.

Since few months ago I've been refining the two scripts to make them able to boot Ubuntu with less likelihood to get error. I thought I would like to share my findings to everyone interested.

Here are some reasons why it's useful to have Ubuntu on Nexus One

1. Fully functional web browser Firefox

2. Fully functional office suite OpenOffice

3. Fully functional Linux terminal with lots of ultilities

4. Fully functional image manipulation tool Gimp

5. Ability to run lots of useful native Linux programs

6. Python, gcc, g++..

I'll talk about my findings in next few posts.

Post #2: simplify ubuntu.sh, remove unnecessary script files

Post #3: simplify bootubuntu, forcibly umount

Post #4: how to shutdown Ubuntu properly if terminal application was closed by Android

Post #5: a little script which should be run before exiting from Ubuntu

Post #6: how to start GNOME desktop (instead of LXDE) and get correct keyboard mapping

Post #7: a possible solution to loop device's "resource or device busy" error

About my Nexus One:

bought on 2nd March

Cyanogen Mod 6.0

IntersectRaven HAVS CM CFS 1020 kernel

Busybox 1.17

Radio 5.0.8

Gapps hdpi 20101020.1

Please don't hesitate to tell me if I made any mistake, I'm a Linux beginner because I taught myself Linux, my University will teach Unix next semester.

Attachment: ubuntu_scripts.zip

contains all modified scripts.
[Nexus One Android Development] houzuoguo:
Finding #1:

In original Zip package, there are five scripts, but only two of them are actually used to install and boot up Ubuntu.

fsrw, mountonly, unionfs are not necessary to install and boot ubuntu, thus their reference can be removed from ubuntu.sh

Here is my simplified version of ubuntu.sh

#-------------------------------

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

rm -f /system/bin/bootubuntu

rm -r -f /data/local/ubuntu

cp -f bootubuntu /system/bin

cd /

echo "Type 'bootubuntu' to boot Ubuntu"

#-------------------------------

Simplified ubuntu.sh removed unnecessary statements to reduce risk of error.

Also I discovered:

Files in /sdcard/ubuntu can not be chmod, and it's unnecessary to chmod 4777 to them.

chmod 4777 /system/bin/* will cause some Android softwares to malfunction (e.g. Orbot), also it *possibly* cause some roms to fail to boot up next time (CM6.0)
[Nexus One Android Development] houzuoguo:
Finding #2:

Here's my simplified bootubuntu script, there are minor changes to script flow and removed all unnecessary statements:

#-------------------------------

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

echo "SETTING VARIABLES"

export bin=/system/bin

export mnt=/data/local/ubuntu

export PATH=$bin:/usr/bin:/usr/sbin:/bin:$PATH

export TERM=linux

export HOME=/root

if [ ! -d /data/local/ubuntu ]

then

mkdir /data/local/ubuntu

fi

echo "SETTING UP LOOP DEVICE"

losetup /dev/block/loop1 /sdcard/ubuntu/ubuntu.img

echo "MOUNTING"

mount -t ext2 /dev/block/loop1 /data/local/ubuntu

mount -t devpts devpts $mnt/dev/pts

mount -t proc proc $mnt/proc

mount -t sysfs sysfs $mnt/sys

echo "SETTING UP NETWORK"

sysctl -w net.ipv4.ip_forward=1

echo "nameserver 208.67.222.222" > $mnt/etc/resolv.conf

echo "nameserver 208.67.220.220" >> $mnt/etc/resolv.conf

echo "127.0.0.1 localhost" > $mnt/etc/hosts

echo "Brought to you by NexusOneHacks.net and the open source community! "

chroot $mnt /bin/bash

echo "UMOUNTING"

umount -lfr $mnt/dev/pts

umount -lfr $mnt/proc

umount -lfr $mnt/sys

umount -lfr $mnt

losetup -d /dev/block/loop1

#-------------------------------

and it forcibly,lazily,read-only-if-failed umount $mnt, thus losetup -d will less likely to fail and eliminate the problem when booting ubuntu second time.
[Nexus One Android Development] houzuoguo:
Finding #3:

If terminal application is terminated automatically by Android system, in this situation, the Ubuntu is not properly umounted.

Thus we change ubuntu.sh into:

#------------------------------

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

rm -f /system/bin/bootubuntu

rm -f /system/bin/exitu

rm -r -f /data/local/ubuntu

cp -f bootubuntu /system/bin

cp -f exitu /system/bin

cd /

echo "Type 'bootubuntu' to boot Ubuntu"

#------------------------------

and we create a new script named "exitu" in sdcard/ubuntu directory:

#------------------------------

export mnt=/data/local/ubuntu

echo "UMOUNTING"

umount -lfr $mnt/dev/pts

umount -lfr $mnt/proc

umount -lfr $mnt/sys

umount -lfr $mnt

losetup -d /dev/block/loop1

#------------------------------

remember to run "sh ./ubuntu.sh" to copy new exitu script into /system/bin.

Then whenever you went back to terminal, found Ubuntu terminal is gone, simply type exitu (remember to be su first) to exit ubuntu, then bootubuntu again to enter ubuntu terminal. It's harmless to execute exitu multiple times to ensure $mnt is umounted successfully.

Sometimes exitu still can not successfully remove loop1 assignment with /sdcard/ubuntu/ubuntu.img, but seems like it doesn't really matter, ubuntu still can boot up successful even loop1 was not unassigned successfully
[Nexus One Android Development] houzuoguo:
Finding #4:

To reduce likelihood of getting "device or resource busy" error when removing loop device assignment, it's good to have this script in your Ubuntu, and run the script before exiting from Ubuntu:

#-------------------

export USER=root

vncserver -kill :1

vncserver -kill :2

sudo reboot

sudo halt

#-------------------

(remember, the script should be in your Ubuntu's file system, not your android's file system!)

run the script before you exiting from Ubuntu, this will greatly reduce likelihood of getting device or resource busy error when exiting.
[Nexus One Android Development] houzuoguo:
Finding #5:

For those of you who prefer to enter GNOME desktop manually (no automatically start-up), this script may help, also this script should be able to fix androidVNC keyboard mapping problem:

(this script should be in Ubuntu)

#--------------------

cd /

rm -r -f tmp

mkdir tmp

cd /

export USER=root

export XKL_XMODMAP_DISABLE=1

vncserver -geometry 800x600

#--------------------

regarding the guide:

http://nexusonehacks.net/nexus-one-hacks/how-to-install-ubuntu-on-your-nexus-oneandroid/

if you would like to enter gnome and not to autostart desktop environment, please don't follow its instruction on making change to /root/.vnc/xstartup and /root/.bashrc

instead, create a script as I mentioned above, and run the script to bring up VNC server, and you will get GNOME desktop in VNC with correct keyboard mapping
[Nexus One Android Development] houzuoguo:
Finding #6

If you're constantly getting "device or resource busy" error when mounting loop1 to /data/local/ubuntu, the reason might be caused by Android App2SD (Froyo version), if you have any software installed on SD card, it may cause all loop devices to be busy all the time (even newly created loop device!) And busy loop device can not be mounted, thus generates "device or resource busy" error message.

Most people had the same problem few months ago, when they execute bootubuntu, they get an error saying loop device is busy, and even changing loop device wouldn't help.

Now I think the reason is determined. After uninstalled all applications which are on SD card (or move all of them from SD card to internal storage), the Ubuntu can boot successfully without getting "device or resource busy" error when mounting loop device.

Edit 2010-11-04:

If bootubuntu gets executed before Android loads all app2sd applications, it is possible solves the loop device busy error even with App2SD applications installed. It requires a very perfect timing, today after few experiments on my phone, I worked out a process which can always boot up Ubuntu on my phone:

1. Reboot phone

2. as soon as you enter lock screen, unlock screen

3. quickly go to terminal emulator

4. become su by typing su and enter

5. type bootubuntu and wait (type it fast... practice ;))

-------------

1-5 must be done before SD "Checking for errors" notification disappears, if you fail to do so.. reboot and try again ;)

------------

6. as soon as SD "Checking for errors" notification disappears, hit enter IMMEDIATELY

Now you should be able to enter Ubuntu terminal.

Do NOT exit from your Android terminal (don't press back or home button), wait 1-2 minutes for Android to load applications on SD card.

Once you reboot your phone, you'll need to repeat the above procedure again to enter Ubuntu successfully.
[Nexus One Android Development] mathrock:
Also chmod 4777 is horrible from a security point of view. It makes all the system bin files writable by anyone and run with root privileges (setuid root).
[Nexus One Android Development] mathrock:
This is because with Froyo apps to SD android creates an encrypted loopback device for each app on the SD card, so depending on the number of apps on your SD card loop0-7 may be in use. I solve this by using a high loop number with losetup - loop99.
[Nexus One Android Development] fralacos:
Use a higher loop device, the best option

It worked for me on loop7, but to be on the safe side, decided to use a higher loop number as suggested, but it requires to create the loop device as it doesn't exists, use mknod:

echo "SETTING UP LOOP DEVICE"
mknod /dev/block/loop99 b 7 99
losetup /dev/block/loop99 /sdcard/ubuntu/ubuntu.img

Now is working on loop99 too!. The clean up section for both bootubuntu and exitu scripts:

echo "UMOUNTING"
umount -f $mnt/dev/pts
umount -f $mnt/proc
umount -f $mnt/sys
umount -f $mnt
losetup -d /dev/block/loop99
rm /dev/block/loop99

I'm not sure about how I am cleaning up the new node, rm erases it... but is this the best method? rebooting the phone will erase the node anyway so maybe an if clause to test for the node loop99 before creating it will be better.