Jump to content

[Development][ROM] Stock FROYO + 2.6.32 kernel

Guest pier11

By Guest pier11
in T-Mobile Pulse

 Share

Recommended Posts

Guest Smikeyy

Guest Smikeyy

Posted
Posted

I have flashed this on my pulse I firstly flashed CHT8000 2.1 rom before flashing this room.

This issue is that when booting up it gets stuck on the boot loader and continues to load

Any solutions ?

Link to comment
Share on other sites
  • Replies 651
  • Created
  • Last Reply

Popular Days

Popular Days

Popular Posts

Guest pier11
Guest pier11

Dear all, let me present work in progress to make standard FROYO reference rom based on appropriate kernel - 2.6.32 Rom is an adopted stock froyo of Huawei UM840 device (msm7225 based). Same for r

Guest lloco73
Guest lloco73

replaced libril.so from cm7.2 and now i can search network manually.

Guest pier11
Guest pier11

um840-20120218.zip (download is on the first page) - Updated apps to latest versions. This fixed that some apps did not show up. - Added Pulse's sound profile. - Added SetMacAddress to correct de

Posted Images

Guest Smikeyy

Guest Smikeyy

Posted
Posted

I have flashed this on my pulse I firstly flashed CHT8000 2.1 rom before flashing this room.

This issue is that when booting up it gets stuck on the boot loader and continues to load

Any solutions ?

Link to comment
Share on other sites
Guest Smikeyy

Guest Smikeyy

Posted
Posted

I have flashed this on my pulse I firstly flashed CHT8000 2.1 rom before flashing this room.

This issue is that when booting up it gets stuck on the boot loader and continues to load

Any solutions ?

Link to comment
Share on other sites
Guest lloco73

Guest lloco73

Posted
Posted

aafter runiing a logcat on boot.

for button lights i suspect that this 2 erros are somehow the cause of us not having it/ or somewhere there is a call for this 2

Couldn't find APS-12D Light Sensor driver (/dev/light)

Couldn't find APS-12D Proximity Sensor driver (/dev/proximity)

Also there are some xml files missing on data/cust/xml

Link to comment
Share on other sites
Guest pier11

Guest pier11

Posted
Posted (edited)

- cm6+.32kernel does not have this issue (try someone to exchange parts between cm6-u8220-20120206-v2.zip and u8150 (froyo 2.2.1) - might help. For example entire /system/lib/ folder or so). cm6 is froyo 2.2.1 too. um840 is froyo 2.2.2, so u8150 is closer to cm6.

Experiment #1 on the above.

- cm6 rom

- boot.img from um840

= Result: alarm works

(which proves ramdisk is rather fine)

Reconfirm, u8150 reboots on alarm.

Experiment #2.

if replace the following in u8150 /system with cm6':

/app

/framework

/lib

/bin

alarm works.

But substitution is very broad, basically turning u8150 into cm6...

Edited by pier11
Link to comment
Share on other sites
Guest radodendron

Guest radodendron

Posted
Posted (edited)

I tried to replace in part. When replacing the / app and /bin when the phone starts blinking during image se

If you replace / fraemwork not included at all, hangs on the boot image

Edited by radodendron
Link to comment
Share on other sites
Guest radodendron

Guest radodendron

Posted
Posted (edited)

if you carefully read the topic, just this error trying to solve the pier

error when the alarm goes off in the android sdk

E/AlarmClock(2161): HWDrmException :nativeCreateDrmContent() returned JNI_DRM_FAILURE; ErrorCode:65538

Errors with incoming sms

02-24 11:43:24.563: E/M4vH263Decoder(1307): failed to decode video frame.

02-24 11:43:24.573: E/MetadataRetrieverClient(1307): failed to capture a video frame

02-24 11:43:24.573: E/MediaMetadataRetrieverJNI(1981): captureFrame: videoFrame is a NULL pointer

02-24 11:43:25.343: E/M4vH263Decoder(1307): failed to decode video frame.

02-24 11:43:25.343: E/MetadataRetrieverClient(1307): failed to capture a video frame

02-24 11:43:25.343: E/MediaMetadataRetrieverJNI(1981): captureFrame: videoFrame is a NULL pointer

02-24 11:43:26.003: E/M4vH263Decoder(1307): failed to decode video frame.

02-24 11:43:26.003: E/MetadataRetrieverClient(1307): failed to capture a video frame

02-24 11:43:26.003: E/MediaMetadataRetrieverJNI(1981): captureFrame: videoFrame is a NULL pointer

02-24 11:43:26.823: E/Cursor(1514): Finalizing a Cursor that has not been deactivated or closed. database = /data/data/com.android.providers.telephony/databases/mmssms.db, table = canonical_addresses, query = SELECT _id, address FROM canonical_addresses WHERE address=?

02-24 11:43:26.823: E/Cursor(1514): android.database.sqlite.DatabaseObjectNotClosedException: Application did not close the cursor or database object that was opened here

02-24 11:43:26.823: E/Cursor(1514): at android.database.sqlite.SQLiteCursor.<init>(SQLiteCursor.java:210)

02-24 11:43:26.823: E/Cursor(1514): at android.database.sqlite.SQLiteDirectCursorDriver.query(SQLiteDirectCursorDriver.java:53)

02-24 11:43:26.823: E/Cursor(1514): at android.database.sqlite.SQLiteDatabase.rawQueryWithFactory(SQLiteDatabase.java:1345)

02-24 11:43:26.823: E/Cursor(1514): at android.database.sqlite.SQLiteDatabase.queryWithFactory(SQLiteDatabase.java:1229)

02-24 11:43:26.823: E/Cursor(1514): at android.database.sqlite.SQLiteDatabase.query(SQLiteDatabase.java:1184)

02-24 11:43:26.823: E/Cursor(1514): at android.database.sqlite.SQLiteDatabase.query(SQLiteDatabase.java:1264)

02-24 11:43:26.823: E/Cursor(1514): at com.android.providers.telephony.MmsSmsProvider.getSingleAddressId(MmsSmsProvider.java:482)

02-24 11:43:26.823: E/Cursor(1514): at com.android.providers.telephony.MmsSmsProvider.getAddressIds(MmsSmsProvider.java:541)

02-24 11:43:26.823: E/Cursor(1514): at com.android.providers.telephony.MmsSmsProvider.getThreadId(MmsSmsProvider.java:619)

02-24 11:43:26.823: E/Cursor(1514): at com.android.providers.telephony.MmsSmsProvider.query(MmsSmsProvider.java:311)

02-24 11:43:26.823: E/Cursor(1514): at android.content.ContentProvider$Transport.query(ContentProvider.java:163)

02-24 11:43:26.823: E/Cursor(1514): at android.content.ContentResolver.query(ContentResolver.java:245)

02-24 11:43:26.823: E/Cursor(1514): at android.database.sqlite.SqliteWrapper.query(SqliteWrapper.java:59)

02-24 11:43:26.823: E/Cursor(1514): at android.provider.Telephony$Threads.getOrCreateThreadId(Telephony.java:1211)

02-24 11:43:26.823: E/Cursor(1514): at android.provider.Telephony$Threads.getOrCreateThreadId(Telephony.java:1182)

02-24 11:43:26.823: E/Cursor(1514): at com.android.mms.transaction.SmsReceiverService.storeMessage(SmsReceiverService.java:532)

02-24 11:43:26.823: E/Cursor(1514): at com.android.mms.transaction.SmsReceiverService.insertMessage(SmsReceiverService.java:442)

02-24 11:43:26.823: E/Cursor(1514): at com.android.mms.transaction.SmsReceiverService.handleSmsReceived(SmsReceiverService.java:343)

02-24 11:43:26.823: E/Cursor(1514): at com.android.mms.transaction.SmsReceiverService.access$100(SmsReceiverService.java:70)

02-24 11:43:26.823: E/Cursor(1514): at com.android.mms.transaction.SmsReceiverService$ServiceHandler.handleMessage(SmsReceiverService.java:191)

02-24 11:43:26.823: E/Cursor(1514): at android.os.Handler.dispatchMessage(Handler.java:99)

02-24 11:43:26.823: E/Cursor(1514): at android.os.Looper.loop(Looper.java:123)

02-24 11:43:26.823: E/Cursor(1514): at android.os.HandlerThread.run(HandlerThread.java:60)

02-24 11:43:27.233: E/AudioPolicyManagerBase(1307): computeVolume:stream = 5

02-24 11:43:27.233: E/AudioPolicyManagerBase(1307): computeVolume:index = 3, mIndexMin = 0, mIndexMax = 7

02-24 11:43:27.973: E/M4vH263Decoder(1307): failed to decode video frame.

02-24 11:43:27.973: E/MetadataRetrieverClient(1307): failed to capture a video frame

02-24 11:43:27.983: E/MediaMetadataRetrieverJNI(1981): captureFrame: videoFrame is a NULL pointer

02-24 11:43:28.523: E/M4vH263Decoder(1307): failed to decode video frame.

02-24 11:43:28.523: E/MetadataRetrieverClient(1307): failed to capture a video frame

02-24 11:43:28.523: E/MediaMetadataRetrieverJNI(1981): captureFrame: videoFrame is a NULL pointer

02-24 11:43:29.843: E/ThumbnailUtils(1981): exception in get decode path:nativeCreateDrmContent() returned JNI_DRM_FAILURE

02-24 11:43:30.103: E/ThumbnailUtils(1981): exception in get decode path:nativeCreateDrmContent() returned JNI_DRM_FAILURE

Edited by radodendron
Link to comment
Share on other sites
Guest lloco73

Guest lloco73

Posted
Posted (edited)

i asked on a venezuela forum if someone can arrange us a nandroid of UM840, for testing purposes that perhaps can helpus. i'm waiting a response.

Update:

please tes this DeskClock.apk. I've tested it and worked without reboot.(no usb power connected) but screen was on

This is from a U8150 rom

DeskClock.zip

Edited by lloco73
Link to comment
Share on other sites
Guest pier11

Guest pier11

Posted
Posted

please tes this DeskClock.apk. I've tested it and worked without reboot.(no usb power connected) but screen was on

This is from a U8150 rom

Reboots...

Screen should be off..

Link to comment
Share on other sites
Guest dr.flo

Guest dr.flo

Posted
Posted (edited)

progress:

alarm works if remove lights.msm7k.so

Good news. Lights weren't working anyways.... ;) Or - even on ascend rom, where leds were on, alarm caused reboots.

Maybe we should give up trying to get native .32 leds and switch to compat leds that work in cm6/cm7. We could use lights.u8220.so from cm6 then, I would think.

Would be interesting what both leds and alarm do on ascend rom with regard to removal of lights.msm7k.so

or maybe the cm6 version of generic lights.msm7k.so (not u8220) could work, then without led compat in kernel...

Edited by dr.flo
Link to comment
Share on other sites
Guest lloco73

Guest lloco73

Posted
Posted

today i decided to try the kernel 2.6.32 on android 2.1 stock rom to see it it is compatible.

Phone boot ok but after the configuration process it appears me a error about home application.

Also observed that lights are not working.

Test ended due to that error.

Link to comment
Share on other sites
Guest dr.flo

Guest dr.flo

Posted
Posted

when you add this file from cm6 it works

"this file" would need some more desciption....

lights.msm7k.so

lights.u8220.so

lights.u8220.so renamed to lights.msm7k.so

just a few possibilities...

Link to comment
Share on other sites
Guest pier11

Guest pier11

Posted
Posted (edited)

Maybe we should give up trying to get native .32 leds and switch to compat leds that work in cm6/cm7. We could use lights.u8220.so from cm6 then, I would think.

give up not that easy :)

I used lights.msm7k.so from htc Magic's froyo: both alarm and lights(if set ascend's opta/optb) work.

EDIT:

same lib from LG gw620 - alarm works, lights - never.

EDIT2:

same lib from Pulse's stock Eclair - alarm works, lights - never.

EDIT3:

same lib from ideos X3 - reboot. (Though lights if set ascend's opta/optb work)

Edited by pier11
Link to comment
Share on other sites
Guest dr.flo

Guest dr.flo

Posted
Posted (edited)

I used lights.msm7k.so from htc Magic's froyo: both alarm and lights(if set ascend's opta/optb) work.

Ok then let's pick this one for now. Brings us back to where we were but reboot issue solved ;)

x3 rom labels its browser metroweb and disables wifi tether if setting ascend opta/optb. Well known, confirmed on yet another rom. It didn't turn on lights for me, but after your test I'm sure it would do so if I had used the latest keypad lights ready kernel. What I can say is that cm7 lights.u8220 renamed does not turn on lights with compat kernel + ascend settings on that rom. Most likely, using compat lights on um840 + led compat kernel would give the same outcome.

Edited by dr.flo
Link to comment
Share on other sites
Guest pier11

Guest pier11

Posted
Posted (edited)

I'm sure it would do so if I had used the latest keypad lights ready kernel.

I thinks so too. That is the compat kernel where lights hack was removed... Previous rom-um840 kernels were just compat-kernels, with hacks both for cameras and lights.

EDIT:

If strings|grep the lights lib with "/sys" pattern, it can be seeing many control entries. Notably, cm6 version missed "button-backlight" entry. (ref to hack). So it destined not to work with official roms where looks control happens via it.

Actually something changes that control, as if NOT set opta/b to ascend, rom starts using

/sys/class/leds/red/brightness instead and fails to find one. If switched to ascend - no such error.

Edited by pier11
Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
 Share
Go to topic listing
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.

  I accept