Active Topics

 


Reply
Thread Tools
Posts: 223 | Thanked: 38 times | Joined on Jul 2007 @ home
#1
There is a newer version of the Android SDK; however, the older version is being used on the tablets. Why?

I looked it up a while back when I attempted to do all the work myself (didn't work very well lol). From what I can remember it had something to do with the framebuffer/kernel interface to it changed? I also read that it was possible of using the userspace of the newer SDK, but for some reason people generally don't.

• What can be done to port the newer SDK?
• What can be done to increase the speed of Android on the N800?
(it runs smoother on cells with lower specs, the 400MHz proc should be more than adequate for running Android)

--Jon
 
Bundyo's Avatar
Posts: 4,708 | Thanked: 4,649 times | Joined on Oct 2007 @ Bulgaria
#2
http://groups.google.com/group/andro...6624085c3080bd

Someone already got m5-rc15 running on n800 but not very stable. However, we can benefit from his stop all unneeded processes script

The problem is called RAM - already filled up with maemo.

EDIT: Just trying unloading the whole bunch of processes there - Android is much faster and responsive this way. If you want it before penguinbait adds it to the deb - just add this in
Code:
/usr/bin/android.sh
just after
Code:
echo "Starting Android..."
Code:
/etc/init.d/zzinitdone stop
/etc/init.d/alarmd stop
/etc/init.d/mediaplayer-daemon stop
/etc/init.d/bme-dbus-proxy stop
/etc/init.d/af-base-apps stop
/etc/init.d/btcond stop
/etc/init.d/dbus stop
/etc/init.d/gpsdriver stop
/etc/init.d/hildon-desktop stop
/etc/init.d/hulda stop
/etc/init.d/libgpsbt stop
/etc/init.d/obexsrv stop
/etc/init.d/af-startup stop
/etc/init.d/af-services stop
/etc/init.d/x-server stop
/etc/init.d/maemo-launcher stop
/etc/init.d/osso-systemui stop
/etc/init.d/bluez-utils stop
/etc/init.d/multimediad stop
/etc/init.d/mce stop
/etc/init.d/product-code stop
/etc/init.d/hildon-update-notifier stop
/etc/init.d/metalayer-crawler0 stop
/etc/init.d/esd stop
And by much faster i mean at least 5 times

According to the post - you should have lifeguard reset switched off.
__________________
Technically, there are three determinate states the cat could be in: Alive, Dead, and Bloody Furious.

Last edited by Bundyo; 2008-07-02 at 21:39.
 

The Following 7 Users Say Thank You to Bundyo For This Useful Post:
penguinbait's Avatar
Posts: 3,096 | Thanked: 1,525 times | Joined on Jan 2006 @ Michigan, USA
#3
Originally Posted by Bundyo View Post
http://groups.google.com/group/andro...6624085c3080bd

Someone already got m5-rc15 running on n800 but not very stable. However, we can benefit from his stop all unneeded processes script

The problem is called RAM - already filled up with maemo.

EDIT: Just trying unloading the whole bunch of processes there - Android is much faster and responsive this way. If you want it before penguinbait adds it to the deb - just add this in
Code:
/usr/bin/android.sh
just after
Code:
echo "Starting Android..."
Code:
/etc/init.d/zzinitdone stop
/etc/init.d/alarmd stop
/etc/init.d/mediaplayer-daemon stop
/etc/init.d/bme-dbus-proxy stop
/etc/init.d/af-base-apps stop
/etc/init.d/btcond stop
/etc/init.d/dbus stop
/etc/init.d/gpsdriver stop
/etc/init.d/hildon-desktop stop
/etc/init.d/hulda stop
/etc/init.d/libgpsbt stop
/etc/init.d/obexsrv stop
/etc/init.d/af-startup stop
/etc/init.d/af-services stop
/etc/init.d/x-server stop
/etc/init.d/maemo-launcher stop
/etc/init.d/osso-systemui stop
/etc/init.d/bluez-utils stop
/etc/init.d/multimediad stop
/etc/init.d/mce stop
/etc/init.d/product-code stop
/etc/init.d/hildon-update-notifier stop
/etc/init.d/metalayer-crawler0 stop
/etc/init.d/esd stop
And by much faster i mean at least 5 times

According to the post - you should have lifeguard reset switched off.


Did you actually test this? It kep rebooting, then I did the lifeguard reset, and now it starts but the red line is not really moving. Its like its CPU is pegged or something? I need to get ssh on this partition.

more to follow

UPDATE, I just need to remember what kernel I am running??

hehe too much going on sometimes...
__________________
To all my Maemo friends. I will no longer be monitoring any of my threads here on a regular basis. I am no longer supporting anything I did under maemo at maemo.org. If you need some help with something you can reach me at tablethacker.com or www.facebook.com/penguinbait. I have disabled my PM's here, and removed myself from Council email and Community mailing list. There has been some fun times, see you around.

Last edited by penguinbait; 2008-07-02 at 23:08.
 
Bundyo's Avatar
Posts: 4,708 | Thanked: 4,649 times | Joined on Oct 2007 @ Bulgaria
#4
Yes, i tested it both from ssh and from the menu.

Looks like your lifeguard reset is still active. Scratch that - something is hogging your CPU...
__________________
Technically, there are three determinate states the cat could be in: Alive, Dead, and Bloody Furious.

Last edited by Bundyo; 2008-07-02 at 23:15.
 
penguinbait's Avatar
Posts: 3,096 | Thanked: 1,525 times | Joined on Jan 2006 @ Michigan, USA
#5
Not exactly sure if it 5 times faster, but its definetly faster. The only problem is that the only way to set no lifeguard reset flag,is on the linux flasher. I do stop some services for KDE, and I assume that many of the pieces can be shutdown but I think it would be better to come up with a list of as many as we can shutdown without lifeguard reset. So we can get it in as many hands as possible. We can also keep this around, to use for people with the reset flag.

Now I am off to see how this effects KDE?

hehe, I like it
__________________
To all my Maemo friends. I will no longer be monitoring any of my threads here on a regular basis. I am no longer supporting anything I did under maemo at maemo.org. If you need some help with something you can reach me at tablethacker.com or www.facebook.com/penguinbait. I have disabled my PM's here, and removed myself from Council email and Community mailing list. There has been some fun times, see you around.
 

The Following User Says Thank You to penguinbait For This Useful Post:
Posts: 214 | Thanked: 30 times | Joined on Jan 2008
#6
OK, i'll start from the top and see how many I can kill before it resets.

All good up until:

af-services
x-server killed it too. This seems like a pretty big one, but don't you need the x server for android anyway?

maemo-launcher also killed it, this list is starting to get long


And thats it. The rest worked just fine.

So here's the final list

Code:
/etc/init.d/zzinitdone stop
/etc/init.d/alarmd stop
/etc/init.d/mediaplayer-daemon stop
/etc/init.d/bme-dbus-proxy stop
/etc/init.d/af-base-apps stop
/etc/init.d/btcond stop
/etc/init.d/dbus stop
/etc/init.d/gpsdriver stop
/etc/init.d/hildon-desktop stop
/etc/init.d/hulda stop
/etc/init.d/libgpsbt stop
/etc/init.d/obexsrv stop
/etc/init.d/af-startup stop
/etc/init.d/bluez-utils stop
/etc/init.d/multimediad stop
/etc/init.d/mce stop
/etc/init.d/product-code stop
/etc/init.d/hildon-update-notifier stop
/etc/init.d/metalayer-crawler0 stop
/etc/init.d/esd stop
 

The Following 5 Users Say Thank You to drizek For This Useful Post:
Posts: 214 | Thanked: 30 times | Joined on Jan 2008
#7
OK, so according to qwerty, the x-server is not needed by android since it uses the framebuffer instead.

I also found that killing browserd frees up about 2mb of memory. Its hard to tell though since the numbers seem to jump all over the place.

Another way to improve performance is to go into dev-tools and disable window animations.

Last edited by drizek; 2008-07-03 at 07:17.
 
Posts: 393 | Thanked: 112 times | Joined on Jul 2007
#8
Originally Posted by penguinbait View Post
The only problem is that the only way to set no lifeguard reset flag,is on the linux flasher.
Does:

touch /etc/no_lg_reboots

not work in Diablo?
 
Posts: 23 | Thanked: 18 times | Joined on May 2007 @ Fremont, CA
#9
I have not set lifegurd, but drizek's script works fine.
 

The Following User Says Thank You to kimitake For This Useful Post:
Posts: 12 | Thanked: 23 times | Joined on Jul 2008
#10
This works for me without any special changes for lifeguard

Code:
echo "Starting Android..."

/etc/init.d/zzinitdone stop
/etc/init.d/alarmd stop
/etc/init.d/mediaplayer-daemon stop
/etc/init.d/bme-dbus-proxy stop
/etc/init.d/af-base-apps stop
/etc/init.d/btcond stop
/etc/init.d/dbus stop
/etc/init.d/gpsdriver stop
/etc/init.d/hildon-desktop stop
/etc/init.d/hulda stop
/etc/init.d/libgpsbt stop
/etc/init.d/obexsrv stop
/etc/init.d/af-startup stop
/etc/init.d/bluez-utils stop
/etc/init.d/multimediad stop
/etc/init.d/mce stop
/etc/init.d/product-code stop
/etc/init.d/hildon-update-notifier stop
/etc/init.d/metalayer-crawler0 stop
/etc/init.d/esd stop

## These may cause lifeguard to reboot the system
touch /etc/no_lg_reboots
/etc/init.d/af-services stop
/etc/init.d/x-server stop
/etc/init.d/maemo-launcher stop
/etc/init.d/osso-systemui stop

rm -rf /android/tmp/*
This does make Android run much faster! Thanks for the tip
 
Reply

Tags
android


 
Forum Jump


All times are GMT. The time now is 18:50.