Android 2.2 Development

[Guest guyh1]

well, I know people are down on posters like me (people who wouldn't know where to start cooking a rom never mind messing about with kernels etc) but just thought i'd say a big thank you to everyone developing in this community on behalf of us lot. so thank you everyone - especially this Tom G character who seems like a big deal (and the other Rom creators, fibblesan etc). Keep up the good work chaps, and keep those donation links up :P

Edited September 7, 2010 by guyh1

[Guest totiadrenalin]

I'm surprised a few people are reporting that rotation freezes the phone. I've had absolutely no issues. It could be a kernel issue (I'm running a newer kernel on Froyo)

If you want to try the UK kernel then download this and flash it through recovery. It'll replace the wifi binaries to newer versions which work with the UK kernel.

The boot.img has a couple of changes from the one Tom used. It will boot Android with loglevel 3 instead of 8, and will give you the graphical Android logo instead of the text based one. It's mostly the same but the layout has been tidied up a bit.

Tom, feel free to use this in any updates.

Flibble. Sorry man that I have to tell you this, but after flashing your kernel, the phone is becoming a bit unstable from time to time.

From time to time I'm loosing the 3G. After reboot the 3G is back.

I didn't change anything on the phone, just flash your zip with the boot.im and /system/wifi/ over pulse_froyo_040.zip and changin the permissions for /system/netcfg

Apps that I have are: root explorer, gps tether, wireless tether, system panel,terminal emulator,auto startup, and rom manager. And of course super user.

And once again I get frozen screen on rotation.

The Wifi tethering is working good. The link rate bug is here.

But sometimes I get reboots.

I'll tell it once again.

I'm sorry for telling this but I just had to. You know?!

EDIT:

I forgot that I replace HW to.

Edited September 8, 2010 by totiadrenalin

[Guest Simon O]

Flibble. Sorry man that I have to tell you this, but after flashing your kernel, the phone is becoming a bit unstable from time to time.

From time to time I'm loosing the 3G. After reboot the 3G is back.

I didn't change anything on the phone, just flash your zip with the boot.im and /system/wifi/ over pulse_froyo_040.zip and changin the permissions for /system/netcfg

Apps that I have are: root explorer, gps tether, wireless tether, system panel,terminal emulator,auto startup, and rom manager. And of course super user.

And once again I get frozen screen on rotation.

The Wifi tethering is working good. The link rate bug is here.

But sometimes I get reboots.

I'll tell it once again.

I'm sorry for telling this but I just had to. You know?!

EDIT:

I forgot that I replace HW to.

I don't know.. maybe with all the work you've been doing to your phone you've made the froyo installation unstable. I've had no stability issues since I installed froyo 0.40 on my phone from a recovery zip.

I don't know what I can suggest to you. I should point out that when I do release a custom rom based on Froyo it will be using the 2.6.29 kernel from the UK T-Mobile 2.1 update. Purely because, like the Tre kernel, it's stable.

[Guest totiadrenalin]

I don't know.. maybe with all the work you've been doing to your phone you've made the froyo installation unstable. I've had no stability issues since I installed froyo 0.40 on my phone from a recovery zip.

I don't know what I can suggest to you. I should point out that when I do release a custom rom based on Froyo it will be using the 2.6.29 kernel from the UK T-Mobile 2.1 update. Purely because, like the Tre kernel, it's stable.

I'll give it a test one more time.

First I'll upgrade the UK dload.

Then fastboot the pulse froyo

and then your kernel.

I'll report tomorrow.

Since the Uk is out I'm using that rom.

I know that's very stable rom.

And since flb mod 1.3.1 u are using Uk eclair rom.

I can freely say that I'm in love with your mod, and what you have done with the eclair about stability and speed. it's somethings like a near perpetuum mobile! :P

HEHE!

Edited September 8, 2010 by totiadrenalin

[Guest totiadrenalin]

About ten days I use my pulse just to perform tests on it, and from time to time to make some conversation.

HEHE! :P

[Guest totiadrenalin]

And Now I get it.

About the Marked bug.

This is important only for Macedonians owners of pulse.

The Marked never actually worked in Macedonia.

I remember since I bought this phone. First I was using the ProjectMenuACT to trick my phone that I'm in USA and under T-mobile US operator.

But after I put eclair in my phone i find that it would be easier to use marked enabler.

So this practice continues in froyo.

I'm just wondering why the ProjectMenuAct.apk doesn't work in froyo?

I push back and the MMITest_II.apk, but it doesn't work to.

Is there any way to be fixed?

EDIT:

Sorry T-mobile UK, not us

Edited September 8, 2010 by totiadrenalin

[Guest TelluricMax]

Just been playing around with the 8150 rom and got to the point where it boots, displays the ideos loading logo and then displays a system error in chinese (attached if any chinese speakers would care to translate?), if this is likely to be of use I can email it to someone to look at.

This was produced using the xda kitchen, deodexing the rom, adding the uk 2.1 boot.img and removing a few apps/ringtones etc.

it means" sorry! the system app has no response

FC or wait"

[Guest totiadrenalin]

Nope!

I did all that Y said, and here what I get in the logcat.

E/SyncSettingReceiver( 1513): onReceive is called for android.intent.action.SERV

ICE_STATE

E/CommonUtilMethods( 1513): Account is null

fixed....

E/QC-DSS-LIB( 1071): Ignoring physlink state change received in state 2

E/QC-DSS-LIB( 1071): dsc_kif_cfg_fail called in state 2

E/QC-DSS-LIB( 1071): dsc_kif_cfg_cnf called in state 5, ignoring!

D/MobileDataStateTracker( 1133): replacing old mInterfaceName (rmnet0) with rmne

t0 for hipri

D/MobileDataStateTracker( 1133): replacing old mInterfaceName (rmnet0) with rmne

t0 for supl

D/MobileDataStateTracker( 1133): default Received state= CONNECTED, old= CONNECT

ING, reason= apnChanged, apnTypeList= default,supl

D/NetworkStateTracker( 1133): setDetailed state, old =CONNECTING and new state=C

ONNECTED

D/ConnectivityService( 1133): ConnectivityChange for mobile: CONNECTED/CONNECTED


D/ConnectivityService( 1133): adding dns 62.162.155.229 for mobile

I/ApnPreference( 1623): ID: 294 :true

D/ConnectivityService( 1133): adding dns 62.162.155.230 for mobile

D/Tethering( 1133): Tethering got CONNECTIVITY_ACTION

I just made changes to build.prob

build.prop.zip

Edited September 8, 2010 by totiadrenalin

[Guest Tom G]

Now Tom G !

About the Video Preview and camera!

Check this link.

I thing it could help you.

E/copybit ( 1014): copyBits failed (Invalid argument)

D/copybit ( 1014): 0: src={w=320, h=480, f=0, rect={0,25,320,10}}

D/copybit ( 1014):	 dst={w=320, h=480, f=0, rect={0,25,320,10}}

D/copybit ( 1014):	 flags=00020000

D/copybit ( 1014): 1: src={w=320, h=480, f=0, rect={0,35,24,184}}

D/copybit ( 1014):	 dst={w=320, h=480, f=0, rect={0,35,24,184}}

D/copybit ( 1014):	 flags=00020000

D/copybit ( 1014): 2: src={w=320, h=480, f=0, rect={312,35,8,184}}

D/copybit ( 1014):	 dst={w=320, h=480, f=0, rect={312,35,8,184}}

D/copybit ( 1014):	 flags=00020000

D/copybit ( 1014): 3: src={w=320, h=480, f=0, rect={0,219,320,261}}

D/copybit ( 1014):	 dst={w=320, h=480, f=0, rect={0,219,320,261}}

D/copybit ( 1014):	 flags=00020000

E/libagl  ( 1014): copybit failed (Unknown error: -22)

E/copybit ( 1014): copyBits failed (Operation not permitted)

D/copybit ( 1014): 0: src={w=320, h=480, f=0, rect={242,0,72,25}}

D/copybit ( 1014):	 dst={w=320, h=480, f=0, rect={242,0,72,25}}

D/copybit ( 1014):	 flags=00020000

D/copybit ( 1014): 1: src={w=320, h=480, f=0, rect={6,25,308,160}}

D/copybit ( 1014):	 dst={w=320, h=480, f=0, rect={6,25,308,160}}

D/copybit ( 1014):	 flags=00020000

E/libagl  ( 1014): copybit failed (Unknown error: -1)

Really close log as I get in log cat when I try to play video and open the camera app.

The bug they have there is in eclair, but I really thing that this could be very helpful to you..

Thanks for finding that, but we probably won't be able to fix it without the kernel source (the google code page indicates a kernel header needs to be modified). We could try replacing the header used by bionic with the equivalent header out of the aosp 2.6.29 kernel and hope for the best. It needs more debugging to be sure it is the same problem as described on that google code page, but thats a good start.

It looks as if the interface is the same in aosp and codeaurora but codeaurora hasn't picked up the include file name change. It would be good to see the errors you are getting. Is the github you are intending to upload the code to the one at http://github.com/TomGiordano/device-pulse ? If so it appears to not even contain the aosp code yet, have you forgotten to do the push?

I decide to setup another github account just for android. That way if I move on to other things later I can pass the account on to someone else (plus I don't have a heap of android repos in my other account). http://github.com/pulse-android-dev.

Its all just aosp code at the moment. Some of the repos I need to modify aren't mirrored on github, so I will need to get them from kernel.org and put them on github. I'm still trying to get my head around git, it must be the least user-friendly software I have every used.

I haven't had time the last few days to do anything with android and I probably won't until the weekend. Sorry.

[Guest Spikey001]

Hey guys, been following post since it started!

Absolutely brilliant work, can't believe how well just a few of you working on this have done!

Gonna get the pom poms out n cheer you on!! :P

[Guest Josh04]

Bad news; just dropped an SMS : /

[Guest flip360]

And Now I get it.

About the Marked bug.

This is important only for Macedonians owners of pulse.

The Marked never actually worked in Macedonia.

I remember since I bought this phone. First I was using the ProjectMenuACT to trick my phone that I'm in USA and under T-mobile US operator.

But after I put eclair in my phone i find that it would be easier to use marked enabler.

So this practice continues in froyo.

I'm just wondering why the ProjectMenuAct.apk doesn't work in froyo?

I push back and the MMITest_II.apk, but it doesn't work to.

Is there any way to be fixed?

EDIT:

Sorry T-mobile UK, not us

So we just need to use market enabler with t-mob uk?

[Guest igor_anta]

So we just need to use market enabler with t-mob uk?

T-Mob US is probably the best, but as far as I remember MarketEnabler was not working for people trying this build, like flibble for example. Or maybe I'm wrong.

[Guest flip360]

i cannot seem to find settings for T-Mobile UK in market enabler, could you know the settings by any chace?

cheers

[Guest whackster]

i cannot seem to find settings for T-Mobile UK in market enabler, could you know the settings by any chace?

cheers

Give this a try :P

[Guest igor_anta]

Give this a try :)

Just be carefull with this one, it switched my APN permanently once, it though I'm on T-Mob US and I had to go through the trouble to set up my APN's all over again :P It's good though, just backup the default value first and DON'T set it to emulate on boot.

[Guest flip360]

Thanks!

[Guest Sh4d0w940]

Well didn't take long for the Chinese friends to find the zip posted earlier. http://hiapk.com/bbs/thread-477774-1-1.html

That's fast indeed, but they didn't mirror it so I changed the zip to a 403 and 404 error :P

Also, they didn't confirm it worked and google translate says that they had download problems.

Sh4d0w940

[Guest flip360]

Give this a try :P

hmmm, doesnt show t-mob uk also, do you have it working?

[Guest D-D-]

hmmm, doesnt show t-mob uk also, do you have it working?

Just tried it and it worked for me.

[Guest rikkiej]

hmmm, doesnt show t-mob uk also, do you have it working?

doesn't work @ all for me :P

[Guest totiadrenalin]

i cannot seem to find settings for T-Mobile UK in market enabler, could you know the settings by any chace?

cheers

I was using T-Mobile UK in the ProjectMenuAct

And T-mobile US in Market enabler.

[Guest Josh04]

I nicked the JIT-enabled dalvikvm from Cyanogen-mod and got a cool 3.197 on Linpack :P

Check it out:

http://www.greenecomputing.com/apps/linpac...pack-by-device/

(Ignore that it says U8150 in the fingerprint - I've been trying to get some apps to show up in the market)

[Guest flip360]

nice :P can you share the files?

cheers

[Guest totiadrenalin]

I Find something interesting about the market.

Just edit the build prop, and replase the fingerprint with the passion fingerprint.

# Do not try to parse ro.build.description or .fingerprint

ro.build.description=passion-user 2.2 FRF85B 42745 release-keys

ro.build.fingerprint=google/passion/passion/mahimahi:2.2/FRF85B/42745:user/release-keys

# end build properties

With the root explorer or via adb delete the /data/data/vending data, and /data/dalvik-cache/the vending class.dex

then reboot into recovery and re-flash the google apps zip.

After that you can use the market enabler and trick your phone that you are under t-mobile us operator.

And that's all.

The market app will have full functionality.

The market enabler is only for non eu, country's, like Macedonia for example.

The fingerprint trick is the same as filbb did in his eclair flb mod.

Edited September 8, 2010 by totiadrenalin