[ROM] FusionX Huawei Y300 v1.0 [B199] [Full HWA]

[Guest jackosterman]

I may be wrong, but there appears to be a memory leak with app ID 6948 and 992 as the heap is full. 6948 even causes an error at the end of the log.

Hm, I can't seem to locate 6948. 992, however, appears as such:

 root      159   1     992    424   ffffffff 00000000 S /system/bin/installd

Edit: In the event that these occurrences are unique to my device, I should note that I've (permanently) disabled both the Gtalk and Google Analytics services, via the app Disable Service. I don't imagine a correlation, but I may as well throw it out there.

Edited August 27, 2013 by jackosterman

[Guest H3ROS]

installd is the native package management daemon. Wouldn't worry about that one too much, although it's a little odd that it's logging it as an error rather than debug.

If you reboot the phone you may get the MMS errors again as well as the file not found exception (/data/skin/description.xml).

I've got to go for now but I'll check back later.

Edited August 27, 2013 by H3ROS

[Guest jackosterman]

After a reboot, this is the closest I could find:

 08-27 06:45:42.009 I/GservicesProvider(1003): Gservices pushing to system: true; secure: true

08-27 06:45:48.950 I/PushServiceReceiver(1224): start PushSerevice for ACTION_BOOT_COMPLETED or CONNECTIVITY_ACTION

08-27 06:45:50.720 I/PushServiceReceiver(1224): start PushSerevice for ACTION_BOOT_COMPLETED or CONNECTIVITY_ACTION 

Not sure if it's relevant. Thanks, at any rate.

[Guest Laximus]

I'm in the UK, but I don't have plans to buy this phone. I've been looking into this ROM and helping out where I can as a friend of mine in Canada has the 0151 version.

well, i just thought, maybe we would collect you the amount for an y300 to contiue/restart the developing of its rom =)

[Guest jackosterman]

Anyone care to run a logcat and see if a "wifi_send_command" error comes up repeatedly? While I admittedly have no idea what that really means, I've oft been getting a lower wifi signal since flashing and wondering if the error is related/unique to my device. Thanks.

[Guest taio.doio]

i don't know if it's a bug or not..

but after a while using google search, Maps,.. the "Data connection" stop working.

If i close the app (in background) the connection restart to work..

(All the APN are ok..i've just uncheck "always on data" for save my battery..and i use "greenPower" for manage the connection during stand-by..)

[Guest H3ROS]

well, i just thought, maybe we would collect you the amount for an y300 to contiue/restart the developing of its rom =)

If I had the device I'd dev for it, but people could probably donate to Tillaz so that he gets another, if he'd want to continue that is.

@ jackosterman

What you pasted there are just info strings. Error would start "E/".

The MMS errors may take a while to show up. Maybe if you open the MMS app in an attempt to download one and then load up logcat it'd show?

As for the wifi_send_command, that's using SIGNAL_POLL which actually is a good thing. Well it should be, but like I previously said this has logged it as an error rather than debug info. It's probably really debug info though.

-----

Can anyone confirm if MMS is working for them? Maybe if you try to send a picture to yourselves?

Edited August 27, 2013 by H3ROS

[Guest aapee]

Can anybody help me with a strange problem i have? I cant seem to be able to connect to any networks. The icon on top right just shows that its in roaming mode.... If it helps i have a finnish ascend y300

[Guest H3ROS]

You might be missing APN info. Try to find it online for your carrier or try an app.

https://play.google.com/store/apps/details?id=com.SIMAPNCheck

[Guest jackosterman]

--

I've sent myself three MMS-- the first, a 50KB image, didn't seem to go through (it hung at "Sending"). Wary of my signal strength, I opted to try a couple pictures around 10KB each. Those were successfully sent and received. Three caveats: the first of this batch didn't acknowledge my reception in the delivery report (stuck at "Pending"). The next two successfully displayed as "Received" in the delivery reports, however the status icons (the tiny grey chat bubble next to the time) of each message failed to convert to a green checkmark 'received' icon. Lastly, while these messages were successfully sent and received, after downloading the images failed to actually show (the received message only showing text).

Here's the logcat, apologies if it's a little cluttered with unrelated material.

EDIT: I sent myself a fourth message, this time with Messaging set to auto-retrieve. It's been minutes and its yet to arrive. So it goes!

EDIT 2: Whoops, I accidentally sent that last MMS to the missus, who is still using an old Nokia candy bar phone. I resent myself the MMS with auto-retrieve on-- it went fine, except again no image displayed after downloading. Perhaps results may differ when sending to a third-party? I'm off now, but might bother someone with a test message later.

2013-08-27-17-58-41.txt

Edited August 27, 2013 by jackosterman

[Guest tillaz]

Can anybody help me with a strange problem i have? I cant seem to be able to connect to any networks. The icon on top right just shows that its in roaming mode.... If it helps i have a finnish ascend y300

what rom where you using before this? and did it work ok on that?

[Guest H3ROS]

@ jackosterman

Theres lots of errors and I'm still processing through them. That skin/description.xml one showed up again and theres also a mention of hwframework.jar.

08-27 17:59:19.280 W/System.err(27057): java.io.FileNotFoundException: /data/skin/description.xml: open failed: ENOENT (No such file or directory)

...

08-27 17:59:23.100 E/Trace (27963): error opening trace file: No such file or directory (2)

08-27 17:59:23.150 W/dalvikvm(27963): Refusing to reopen boot DEX '/system/framework/hwframework.jar'

...

08-27 17:59:23.800 W/ResourceType(27963): No package identifier when getting value for resource number 0x00000000

...

08-27 17:59:37.880 E/libEGL ( 927): eglSetBlobCacheFuncsANDROID resulted in an error: 0x300c

...

08-27 17:59:43.940 W/IInputConnectionWrapper(27963): getTextBeforeCursor on inactive InputConnection


08-27 17:59:43.950 W/IInputConnectionWrapper(27963): getSelectedText on inactive InputConnection

...

08-27 18:00:10.010 E/ThumbnailManager(27057): Can't open uri: content://mms/part/12

08-27 18:00:10.010 E/ThumbnailManager(27057): java.io.FileNotFoundException: No entry for content://mms/part/12

08-27 18:00:10.010 E/ThumbnailManager(27057): at android.database.DatabaseUtils.readExceptionWithFileNotFoundExceptionFromParcel(DatabaseUtils.java:149)

08-27 18:00:10.010 E/ThumbnailManager(27057): at android.content.ContentProviderProxy.openTypedAssetFile(ContentProviderNative.java:617)

08-27 18:00:10.010 E/ThumbnailManager(27057): at android.content.ContentResolver.openTypedAssetFileDescriptor(ContentResolver.java:715)

08-27 18:00:10.010 E/ThumbnailManager(27057): at android.content.ContentResolver.openAssetFileDescriptor(ContentResolver.java:612)

08-27 18:00:10.010 E/ThumbnailManager(27057): at android.content.ContentResolver.openInputStream(ContentResolver.java:447)

08-27 18:00:10.010 E/ThumbnailManager(27057): at com.android.mms.util.ThumbnailManager$ThumbnailTask.requestDecode(ThumbnailManager.java:445)

08-27 18:00:10.010 E/ThumbnailManager(27057): at com.android.mms.util.ThumbnailManager$ThumbnailTask.onDecodeOriginal(ThumbnailManager.java:416)

08-27 18:00:10.010 E/ThumbnailManager(27057): at com.android.mms.util.ThumbnailManager$ThumbnailTask.getBitmap(ThumbnailManager.java:319)

08-27 18:00:10.010 E/ThumbnailManager(27057): at com.android.mms.util.ThumbnailManager$ThumbnailTask.run(ThumbnailManager.java:231)

08-27 18:00:10.010 E/ThumbnailManager(27057): at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1076)

08-27 18:00:10.010 E/ThumbnailManager(27057): at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:569)

08-27 18:00:10.010 E/ThumbnailManager(27057): at java.lang.Thread.run(Thread.java:856)

08-27 18:00:10.010 W/ThumbnailManager(27057): decode orig failed /data/data/com.android.providers.telephony/app_parts/PART_1377619208826_sketch1369721313433.png

...

08-27 18:02:16.100 E/	 ( 227): coming in huawei_oem_rapi_streaming_function! event=102.

...

08-27 18:03:25.570 W/System.err(28506): java.lang.IllegalStateException: You must call EasyTracker.getInstance().setContext(context) or startActivity(activity) before calling getTracker()

^ That's a bug in app "Community Reader by Tapatalk 2"

...

08-27 18:04:34.490 E/Mms/image(28754): initFromContentUri couldn't load image uri: content://mms/part/3

08-27 18:04:34.490 E/Mms/image(28754): java.lang.IllegalArgumentException: Query on content://mms/part/3 returns 0 or multiple rows.

08-27 18:04:34.490 E/Mms/image(28754): at com.android.mms.ui.UriImage.initFromContentUri(UriImage.java:126)

08-27 18:04:34.490 E/Mms/image(28754): at com.android.mms.ui.UriImage.<init>(UriImage.java:65)

08-27 18:04:34.490 E/Mms/image(28754): at com.android.mms.util.ThumbnailManager$ThumbnailTask.getBitmap(ThumbnailManager.java:288)

08-27 18:04:34.490 E/Mms/image(28754): at com.android.mms.util.ThumbnailManager$ThumbnailTask.run(ThumbnailManager.java:231)

08-27 18:04:34.490 E/Mms/image(28754): at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1076)

08-27 18:04:34.490 E/Mms/image(28754): at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:569)

08-27 18:04:34.490 E/Mms/image(28754): at java.lang.Thread.run(Thread.java:856)

08-27 18:04:34.540 E/Mms/image(28754): IOException caught while opening stream

08-27 18:04:34.540 E/Mms/image(28754): java.io.FileNotFoundException: No entry for content://mms/part/3

08-27 18:04:34.540 E/Mms/image(28754): at android.database.DatabaseUtils.readExceptionWithFileNotFoundExceptionFromParcel(DatabaseUtils.java:149)

08-27 18:04:34.540 E/Mms/image(28754): at android.content.ContentProviderProxy.openTypedAssetFile(ContentProviderNative.java:617)

08-27 18:04:34.540 E/Mms/image(28754): at android.content.ContentResolver.openTypedAssetFileDescriptor(ContentResolver.java:715)

08-27 18:04:34.540 E/Mms/image(28754): at android.content.ContentResolver.openAssetFileDescriptor(ContentResolver.java:612)

08-27 18:04:34.540 E/Mms/image(28754): at android.content.ContentResolver.openInputStream(ContentResolver.java:447)

08-27 18:04:34.540 E/Mms/image(28754): at com.android.mms.ui.UriImage.decodeBoundsInfo(UriImage.java:177)

08-27 18:04:34.540 E/Mms/image(28754): at com.android.mms.ui.UriImage.<init>(UriImage.java:73)

08-27 18:04:34.540 E/Mms/image(28754): at com.android.mms.util.ThumbnailManager$ThumbnailTask.getBitmap(ThumbnailManager.java:288)

08-27 18:04:34.540 E/Mms/image(28754): at com.android.mms.util.ThumbnailManager$ThumbnailTask.run(ThumbnailManager.java:231)

08-27 18:04:34.540 E/Mms/image(28754): at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1076)

08-27 18:04:34.540 E/Mms/image(28754): at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:569)

08-27 18:04:34.540 E/Mms/image(28754): at java.lang.Thread.run(Thread.java:856)

...

08-27 18:04:58.810 E/RetrieveTransaction(28754): java.io.IOException: Cannot establish route to proxy 1259222794

08-27 18:04:58.810 E/RetrieveTransaction(28754): at com.android.mms.transaction.Transaction.ensureRouteToHost(Transaction.java:224)

08-27 18:04:58.810 E/RetrieveTransaction(28754): at com.android.mms.transaction.Transaction.sendPdu(Transaction.java:175)

08-27 18:04:58.810 E/RetrieveTransaction(28754): at com.android.mms.transaction.Transaction.sendPdu(Transaction.java:123)

08-27 18:04:58.810 E/RetrieveTransaction(28754): at com.android.mms.transaction.RetrieveTransaction.sendAcknowledgeInd(RetrieveTransaction.java:285)

08-27 18:04:58.810 E/RetrieveTransaction(28754): at com.android.mms.transaction.RetrieveTransaction.run(RetrieveTransaction.java:185)

08-27 18:04:58.810 E/RetrieveTransaction(28754): at java.lang.Thread.run(Thread.java:856)

08-27 18:04:58.880 E/Mms:PduLoaderManager(28754): MmsException loading uri: content://mms/4

08-27 18:04:58.880 E/Mms:PduLoaderManager(28754): com.google.android.mms.MmsException: Bad uri: content://mms/4

08-27 18:04:58.880 E/Mms:PduLoaderManager(28754): at com.google.android.mms.pdu.PduPersister.load(PduPersister.java:555)

08-27 18:04:58.880 E/Mms:PduLoaderManager(28754): at com.android.mms.util.PduLoaderManager$PduTask.run(PduLoaderManager.java:173)

08-27 18:04:58.880 E/Mms:PduLoaderManager(28754): at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1076)

08-27 18:04:58.880 E/Mms:PduLoaderManager(28754): at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:569)

08-27 18:04:58.880 E/Mms:PduLoaderManager(28754): at java.lang.Thread.run(Thread.java:856)

08-27 18:04:58.890 E/MediaPlayer(28754): Uri is content://media/internal/audio/media/211

...

08-27 18:04:59.090 E/Mms/slideshow(28754): No part found for the model.

08-27 18:04:59.090 E/Mms/slideshow(28754): java.lang.IllegalArgumentException: No part found for the model.

08-27 18:04:59.090 E/Mms/slideshow(28754): at com.android.mms.model.MediaModelFactory.findPart(MediaModelFactory.java:81)

08-27 18:04:59.090 E/Mms/slideshow(28754): at com.android.mms.model.MediaModelFactory.getMediaModel(MediaModelFactory.java:48)

08-27 18:04:59.090 E/Mms/slideshow(28754): at com.android.mms.model.SlideshowModel.createFromPduBody(SlideshowModel.java:160)

08-27 18:04:59.090 E/Mms/slideshow(28754): at com.android.mms.util.PduLoaderManager$PduTask.run(PduLoaderManager.java:175)

08-27 18:04:59.090 E/Mms/slideshow(28754): at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1076)

08-27 18:04:59.090 E/Mms/slideshow(28754): at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:569)

08-27 18:04:59.090 E/Mms/slideshow(28754): at java.lang.Thread.run(Thread.java:856)

Edited August 27, 2013 by H3ROS

[Guest aapee]

what rom where you using before this? and did it work ok on that?

I was using OptimusPureGoogle by Corsoba and everything worked fine on that :D

[Guest tillaz]

just waiting for the B194 backup from zola, then i will update the ROM, i have actually managed to get a lend of a Y300 a few days while i unlock the bootloader and stuff for them.

so other than the problem with mms (picture messages) what do people want to see improved? or what other bugs / problem are there ?

[Guest tillaz]

I was using OptimusPureGoogle by Corsoba and everything worked fine on that

do you know what version its based on? just wondering if the ril included in this rom is not good for your baseband

similar to like what we had on the G300 and LG o2x

or it could be that the rom mentioned above uses the stock apn.config, where as this uses the cyanogenmod apn.config

which i believe to be the most complete version around.

try flashing this (stock apn)

stock_apn_config.zip

[Guest H3ROS]

so other than the problem with mms (picture messages) what do people want to see improved? or what other bugs / problem are there ?

If you get the backup check that the Google patches Huawei mentioned are actually the security ones, otherwise you can include the patch I done for B190.

http://www.modaco.co...20#entry2151628

Also why not replace the Alarm? http://d-h.st/agl

I've been looking into the MMS bug and I'm curious to know where you got the framework smali patches from and if the messaging app was from the same ROM? I checked and it appears as though you didn't do any patching to TelephonyProvider, so I don't know if the issues there. It's like as though the info gets lost between the app, the framework and TelephonyProvider.

In the stock framework for some MMS playback it'll look for ro.config.helix_enable. One other config entry is ro.config.hw_gcf_mms, but I don't know what setting it to false does.

Edited August 27, 2013 by H3ROS

[Guest tillaz]

If you get the backup check that the Google patches Huawei mentioned are actually the security ones, otherwise you can include the patch I done for B190.

http://www.modaco.co...20#entry2151628

Also why not replace the Alarm? http://d-h.st/agl

I've been looking into the MMS bug and I'm curious to know where you got the framework smali patches from and if the messaging app was from the same ROM? I checked and it appears as the you didn't do any patching to TelephonyProvider, so I don't know if the issues there. It's like as though the info gets lost between the app, the framework and TelephonyProvider.

framework files are from AOSP 4.1.1 same as the MMs.apk, but patching TelephonyProvider broke the sending function of any messages,

you press send and the message just disappears and nothing happens... also the smali files looked fine, no mismatched ids,

leaving TelephonyProvider stock seemed to work fine, so i guess that is where the problem with mms is, but how to fix it i'm not to sure,

its something i will leave to last to be honest as i don't have that much time to update the rom.

[Guest H3ROS]

AOSP 4.1.1 for which device?

I'll take a look into TelephonyProvider later as although the ID's may match I'd be curious to know if the functions are exactly the same, plus what happens when you don't use stock const's and use what's found in AOSP.

[Guest aapee]

do you know what version its based on? just wondering if the ril included in this rom is not good for your baseband

similar to like what we had on the G300 and LG o2x

or it could be that the rom mentioned above uses the stock apn.config, where as this uses the cyanogenmod apn.config

which i believe to be the most complete version around.

try flashing this (stock apn)

stock_apn_config.zip

so weird im still having the problem, guess i just have to forget this rom ;_;

[Guest tillaz]

AOSP 4.1.1 for which device?

I'll take a look into TelephonyProvider later as although the ID's may match I'd be curious to know if the functions are exactly the same, plus what happens when you don't use stock const's and use what's found in AOSP.

official AOSP 4.1.1 for the nexus s,

AOSP framework / apps are the same on every device its built for as its all built from the same google source code so that wouldn't matter.

[Guest H3ROS]

Yeah, it's just that some people will tweak AOSP and don't mention it. As it's for a Nexus S though then it should be fine. That's also the one I'll look through to try to trace any error based off of the logcat :)

[Guest internectual]

so other than the problem with mms (picture messages) what do people want to see improved? or what other bugs / problem are there ?

If you don't mind posting a flashable .zip of the files you removed pertaining to the virtual CD drive. I miss having the phone offer the handset drivers when plugged into a new PC. Adding the two .ISO files back manually didn't do it for me, as the virtual drive showed no volume mounted.

EDIT:

Fixed by copying the two files and changing the following in build.prop:

persist.service.cdrom.enable=1

FusionX has changed it to 0 so init.qcom.usb.sh never performs the required setup to mount cdrom_install.iso

Edited August 28, 2013 by internectual

[Guest internectual]

I was able to resolve my issue with USB Mass Storage and the 3G "fix" from Modaco. Instead of applying the "fix" I used the OEMINFO hack to backup my IMEI, flash a downloaded UPDATE.APP for Entel, and restore my IMEI. Once I was done with those steps I did a complete wipe and installed beta 3 and now everything (including 3G) works as it should.

[Guest aapee]

so weird im still having the problem, guess i just have to forget this rom ;_;

yeah so im getting the error on cm10 rom too? whats so different about these than stock?

[Guest H3ROS]

For them wanting to test MMS.

1. AOSP Messaging + stock framework (with HWA) - http://d-h.st/9Lz

2. AOSP Messaging + modded framework (with HWA) - http://d-h.st/rOW

3. AOSP Messaging + modded framework (with HWA) + modded TelephonyProvider - http://d-h.st/Fju

4. AOSP Messaging + stock framework (with HWA) + modded TelephonyProvider - http://d-h.st/2eR

If you flash them in order of 1-4 then you won't have to restore to a backup until testings complete.

Everythings sourced from AOSP and I've resigned Mms.apk with test signatures (I don't know if this will work on this device). It may require you to delete /data/ in recovery as I don't know if the existing Mms.apk app has the same signature.

@ Tillaz

The AOSP messaging app is different to what you've included with this ROM. I'm not sure if that was accidental, but it may be why MMS doesn't work.

Edited August 27, 2013 by H3ROS