My sys fs paths are good. But the values of it are from 0 to 4338000
in stead of 0 - 100 like it normally is?
On Jun 9, 3:01 am, Yi Sun beyo...@gmail.com wrote:
I have never see it. But is you sys fs patch is worng, you could end up
with a red square with cross in it.
On Mon, 2009-06-08 at
ACPI standard said :
(charge_now/charge_full) * scale
I thought I have posted the fix for this part in my earlier patches,
need to check it.
BTW-- if I remember it correct, the vold crash may cause you lost your
battery icon (I seems to remember it happens that way. It has been a
while already)
I'm not using vold, but mountd.
On Jun 10, 9:53 am, Yi Sun beyo...@gmail.com wrote:
ACPI standard said :
(charge_now/charge_full) * scale
I thought I have posted the fix for this part in my earlier patches,
need to check it.
BTW-- if I remember it correct, the vold crash may cause you lost
Then, I don't have any idea for you :-( sorry.
On Wed, 2009-06-10 at 01:15 -0700, Androidphan wrote:
I'm not using vold, but mountd.
On Jun 10, 9:53 am, Yi Sun beyo...@gmail.com wrote:
ACPI standard said :
(charge_now/charge_full) * scale
I thought I have posted the fix for this part in
Now that I'm using vold again, it doesn't show a battery icon. It does
show a too big percentage level when I plug back in the power supply.
On Jun 10, 10:28 am, Yi Sun beyo...@gmail.com wrote:
Then, I don't have any idea for you :-( sorry.
On Wed, 2009-06-10 at 01:15 -0700, Androidphan
Ok, here is the thing you may need to dig into; you may need to debug
into statusbarservice code to see why your icon does not show up. Look
at the code in frameworks/base/service/java/com/android/server/status
On Wed, 2009-06-10 at 01:39 -0700, Androidphan wrote:
Now that I'm using vold again,
I found the problem. The BATTERY_CAPACITY_PATH is transfered to
mBatterLevel, in my code it was the total 'amount' of battery and the
BATTERY_VOLTAGE_PATH was the amount of battery left. This amount left
is now scaled to fit between 0 and 100. It has to be between these
numbers because the code
look at the update function in BatteryService.java. It is triggered by
uevent. And the icon will only be updated when cap dropped to certain
level.
On Wed, 2009-06-10 at 04:42 -0700, Androidphan wrote:
I found the problem. The BATTERY_CAPACITY_PATH is transfered to
mBatterLevel, in my code it
I need to check the patches. I thought I have put this in.
On Wed, 2009-06-10 at 04:42 -0700, Androidphan wrote:
I found the problem. The BATTERY_CAPACITY_PATH is transfered to
mBatterLevel, in my code it was the total 'amount' of battery and the
BATTERY_VOLTAGE_PATH was the amount of battery
BTW-- Sometime, I don't see the uevent for battery capacity change hence
the battery icon is not updated. To solve it, I added a timer to call
the update function. But it may not be good for your battery life.
On Wed, 2009-06-10 at 05:07 -0700, Yi Sun wrote:
look at the update function in
HI YiSun:
app_process disbaled,still black screen,It should be Ok,maybe my
developping envirmont have unknown issues.I'm now tring to use another
PC(FC8) for doing so,hope it works. Do you think is it worth to try on
another machine? Thanks!
On 6月8日, 下午1时40分, Yi Sun beyo...@gmail.com wrote:
No, it should be a different issue. If you try alt-f1, do you see the
console prompt?
On Mon, 2009-06-08 at 01:06 -0700, GrainWang wrote:
HI YiSun:
app_process disbaled,still black screen,It should be Ok,maybe my
developping envirmont have unknown issues.I'm now tring to use another
Do more people have the problem that they don't see any battery icon
on the status bar? Does it supposed to be there with the battery patch?
--~--~-~--~~~---~--~~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website:
I have never see it. But is you sys fs patch is worng, you could end up
with a red square with cross in it.
On Mon, 2009-06-08 at 06:02 -0700, Androidphan wrote:
Do more people have the problem that they don't see any battery icon
on the status bar? Does it supposed to be there with the battery
NO console prompt. If there is console prompt, it's much easier.
Thanks!
On 6月8日, 下午5时13分, Yi Sun beyo...@gmail.com wrote:
No, it should be a different issue. If you try alt-f1, do you see the
console prompt?
On Mon, 2009-06-08 at 01:06 -0700, GrainWang wrote:
HI YiSun:
Ok, do you see the kernel boot messages?
On Mon, 2009-06-08 at 18:17 -0700, GrainWang wrote:
NO console prompt. If there is console prompt, it's much easier.
Thanks!
On 6月8日, 下午5时13分, Yi Sun beyo...@gmail.com wrote:
No, it should be a different issue. If you try alt-f1, do you see the
No, just when boot from std_boot, the console flahsed some message
bzImage, and it's too fast(I can only remember this),after it. black
screen. Thanks!
On 6月9日, 上午11时02分, Yi Sun beyo...@gmail.com wrote:
Ok, do you see the kernel boot messages?
On Mon, 2009-06-08 at 18:17 -0700, GrainWang
HI YiSun:
I got black srceen after pushing F12 buttom and choosing the boot
from std_boot as the guide. Thanks!
On 6月5日, 下午1时43分, Yi Sun beyo...@gmail.com wrote:
push f12 and select the boot partition
On Thu, 2009-06-04 at 22:27 -0700, GrainWang wrote:
HI YiSun:
Sorry to
Are you ok now? Or you are still having problems?
On Sun, 2009-06-07 at 17:59 -0700, GrainWang wrote:
HI YiSun:
I got black srceen after pushing F12 buttom and choosing the boot
from std_boot as the guide. Thanks!
On 6月5日, 下午1时43分, Yi Sun beyo...@gmail.com wrote:
push f12 and select
HI YiSun:
Yes, I still have the problem. Thanks!
On 6月8日, 上午10时12分, Yi Sun beyo...@gmail.com wrote:
Are you ok now? Or you are still having problems?
On Sun, 2009-06-07 at 17:59 -0700, GrainWang wrote:
HI YiSun:
I got black srceen after pushing F12 buttom and choosing the boot
I assume that your linux kernel boots up ok, And you box only turns to
block screen after launch up the Android. If I'm right, the black screen
could be caused by the wrong FB driver. Please rebuild your kernel to
use VESA fb and see if it works. Otherwise disable app_process and get
into the
HI YiSun:
I applied four patches only,did not use the intelfb method you
supplied, so it should be VESA. Am I right? Also, How to disable the
app_process to get into shell? I dit not find the correspondinng
options for virtualbox. Thanks!
On 6月8日, 下午12时52分, Yi Sun beyo...@gmail.com wrote:
On Sun, 2009-06-07 at 22:33 -0700, GrainWang wrote:
HI YiSun:
I applied four patches only,did not use the intelfb method you
supplied, so it should be VESA. Am I right?
No, if you did not rebuild the kernel, then you are using i915.
Also, How to disable the
app_process to get into
HI YiSun:
Sorry to bother you again. I tried the VirtualBox method, when
choose std_boot, I just got black screen and I can't see any
messages or progesses for booting. Thanks!
On 6月2日, 上午6时43分, Yi Sun beyo...@gmail.com wrote:
I also combine all the mouse cursor fixes as well. Now the
push f12 and select the boot partition
On Thu, 2009-06-04 at 22:27 -0700, GrainWang wrote:
HI YiSun:
Sorry to bother you again. I tried the VirtualBox method, when
choose std_boot, I just got black screen and I can't see any
messages or progesses for booting. Thanks!
On 6月2日, 上午6时43分,
The most important thing for ALSA to work, is to get a working
asound.conf file.
Use alsa_ctl for this.
On May 31, 2:11 pm, Luca Belluccini lucabellucc...@gmail.com wrote:
When I'll get ALSA work, I'll publish a doc explaining the key edits
to be done over original sources.
Any help for ALSA
I'm checking out the cupcake and rebuild the tree with all these patches
to see if I have the same issue. Otherwise, you may need to check your
build environment.
On Mon, 2009-06-01 at 02:26 -0700, GrainWang wrote:
HI YiSun:
I have applied the 4 patches(and only the 4 patches),
I also combine all the mouse cursor fixes as well. Now the 0002* is
removed.
On Mon, 2009-06-01 at 12:13 -0700, Yi Sun wrote:
Ok, I have just checked out one new cupcake and built it with the
patches I posted. I did not see any problem. I attached my screen.
Also, I apply the patch 0002*. It
HI YiSun:
Thanks for your help. The compling process was over this morning.
I'll check later why it's so time consuming. Now I can boot android on
x86 netbook now. Just when boot from usb disk, it erases the WinXp I
installed, and only have the standard linux .so files and none of
Android
When I'll get ALSA work, I'll publish a doc explaining the key edits
to be done over original sources.
Any help for ALSA on x86 will be appreciated.
On 31 Mag, 07:44, GrainWang wlc...@yahoo.com.cn wrote:
HI YiSun:
Thanks for your suggestions! I'm now tring to get the code from
git again
HI YiSun:
The new patches confilt too. 0001*.patch and 0002*.patch try to
patch the same KeyInputQue.java and WindowManagerService.java, See the
log below
r...@ubuntu:/home/cupcake_new/frameworks/base# git apply 0001-1.-fixed-
crash-caused-by-wrong-preload-class.patch
0002 should be applied on top of the 0001. I don't have conflict on my
tree. But anyway, I will combine them later.
For now, don't apply 0002 patch. Without it you should be fine for
now.
On Sun, 2009-05-31 at 18:33 -0700, GrainWang wrote:
HI YiSun:
The new patches confilt too.
The frameworks patch is there. Somehow, the vendor patch is not there.
I'm loading it now
On Sun, 2009-05-31 at 19:18 -0700, GrainWang wrote:
HI YiSun:
Also the frameworks patch was not included in http://
code.google.com/p/patch-hosting-for-android-x86-support/downloads/
list I have to
Could you send me the reject file? I tested it again. It works for me.
On Sun, 2009-05-31 at 19:35 -0700, Yi Sun wrote:
0002 should be applied on top of the 0001. I don't have conflict on my
tree. But anyway, I will combine them later.
For now, don't apply 0002 patch. Without it you should be
HI YiSun:
It seemed that it's caused by another confict. Both your 0001-
fixed***.path and touch_screen.path try to modify KeyInputQueue.java.
So could you kindly tell mehow to deal with all the conflicts? such
as which patch should be applied first or something? Thanks!
On 6月1日, 上午10时35分,
Don't apply the touch screen patch. YOu don't need it either.
To build a normal 701 image, you only need:
0001-1*
alarm.patch
e2fsprogs.patch.
If you want to build kernel, then you need the kernel.config for your
kernel .config
I will need to update the wiki for this. We need to discuss about
HI YiSun:
Thanks for your suggestions! I'm now tring to get the code from
git again and do all the steps from the start again.
On 5月31日, 下午12时00分, Yi Sun beyo...@gmail.com wrote:
Ok,I think you broke something when you apply the patches.
Could u create a new tree and apply the new patches
37 matches
Mail list logo
