Guest StewieTech Posted September 28, 2014 Report Posted September 28, 2014 So H3ROS, when can we expect a new update with some statusbar portuguese love? Thanks.
Guest H3ROS Posted September 28, 2014 Report Posted September 28, 2014 I'm working on it. I've been investigating the issue that fonz93 reported a little while back and have found that even the stock Y300/G510 ROM's do it if you simply disable the Huawei lockscreen app.
Guest fonz93 Posted September 28, 2014 Report Posted September 28, 2014 (edited) You're right, i didn't notice it until now (i don't use stock Huawei ROM), but i am pretty sure that on my old ROM (SlimStock) this didn't happen, i'll try it and report back Edited September 28, 2014 by fonz93
Guest luca020400 Posted September 28, 2014 Report Posted September 28, 2014 Yes in slimstock work fine ;)
Guest fonz93 Posted September 28, 2014 Report Posted September 28, 2014 (edited) Yes, i tried it just now and it's something unusual, because SystemUI included in SlimStock is the one made by H3ROS, but the "no network" bug is not fixed. @ H3ROS, which Huawei stock ROM did you try? Maybe there are some changes between B199 (SlimStock is B199) and B209 related to RIL (i can confirm that the bug is present on B209)? I am downloading the update.app of a pure B199 to see if the bug is there too Edited September 28, 2014 by fonz93
Guest luca020400 Posted September 28, 2014 Report Posted September 28, 2014 Yes the SystemUI doesn't contain the no network patch If there are some chamges in ril , can we see the differnces ??
Guest fonz93 Posted September 28, 2014 Report Posted September 28, 2014 (edited) Yes the SystemUI doesn't contain the no network patch If there are some chamges in ril , can we see the differnces ?? Yes, but neither the stock Huawei B209 have this fix and is affected by that bug, too. Edited September 28, 2014 by fonz93
Guest H3ROS Posted September 28, 2014 Report Posted September 28, 2014 Yes, i tried it just now and it's something unusual, because SystemUI included in SlimStock is the one made by H3ROS, but the "no network" bug is not fixed. @ H3ROS, which Huawei stock ROM did you try? Maybe there are some changes between B199 (SlimStock is B199) and B209 related to RIL (i can confirm that the bug is present on B209)? I am downloading the update.app of a pure B199 to see if the bug is there too I tried stock B209. I think B199 (FusionX) also has the issue, so maybe it's something you removed from SlimStock? One of the build.prop entries or something.
Guest fonz93 Posted September 28, 2014 Report Posted September 28, 2014 (edited) This is the SlimStock build.prop: # begin build properties # autogenerated by buildinfo.sh ro.build.id=HuaweiY300-0100 ro.build.display.id=[slimStock][b199] ro.build.version.incremental=C00B199 ro.build.version.sdk=16 ro.build.version.codename=REL ro.build.version.release=4.1.1 ro.build.date=Sat Oct 12 14:57:57 CST 2013 ro.build.date.utc=1381561077 ro.build.type=user ro.build.user=huawei ro.build.host=huawei-desktop ro.build.tags=release-keys ro.product.model=Ascend Y300 ro.product.brand=Huawei ro.product.name=Y300-0100 ro.product.device=hwY300-0100 ro.product.board=U8833-1 ro.product.cpu.abi=armeabi-v7a ro.product.cpu.abi2=armeabi ro.product.manufacturer=HUAWEI ro.product.locale.language=en ro.product.locale.region=US ro.wifi.channels= ro.board.platform=msm7627a # ro.build.product is obsolete; use ro.product.device ro.build.product=msm7627a # Do not try to parse ro.build.description or .fingerprint ro.build.description=Y300-0100-user 4.1.1 GRJ90 C00B199 release-keys ro.build.fingerprint=Huawei/Y300-0100/hwY300-0100:4.1.1/HuaweiY300-0100/C00B199:user/ota-rel-keys,release-keys ro.build.characteristics=default # end build properties # The value may be external_sd or internal_sd persist.sys.main_storage=external_sd # Code Aurora/Huawei DEVICE_PROVISIONED=1 rild.libpath=/system/lib/libril-qc-1.so rild.libargs=-d /dev/smd0 persist.rild.nitz_plmn= persist.rild.nitz_long_ons_0= persist.rild.nitz_long_ons_1= persist.rild.nitz_long_ons_2= persist.rild.nitz_long_ons_3= persist.rild.nitz_short_ons_0= persist.rild.nitz_short_ons_1= persist.rild.nitz_short_ons_2= persist.rild.nitz_short_ons_3= ril.subscription.types=NV,RUIM keyguard.no_require_sim=true persist.cne.bat.range.low.med=30 persist.cne.bat.range.med.high=60 persist.cne.loc.policy.op=/system/etc/OperatorPolicy.xml persist.cne.loc.policy.user=/system/etc/UserPolicy.xml persist.cne.bwbased.rat.sel=false persist.cne.snsr.based.rat.mgt=false persist.cne.bat.based.rat.mgt=false persist.cne.rat.acq.time.out=30000 persist.cne.rat.acq.retry.tout=0 persist.cne.fmc.init.time.out=30 persist.cne.fmc.comm.time.out=130 persist.cne.fmc.retry=false persist.cne.feature=0 media.stagefright.enable-player=true media.stagefright.enable-meta=false media.stagefright.enable-scan=true media.stagefright.enable-http=true media.stagefright.enable-fma2dp=true media.stagefright.enable-aac=true media.stagefright.enable-qcp=true headset.hook.delay=500 audio.legacy.postproc=true ro.opengles.version=131072 wifi.interface=eth0 ro.use_data_netmgrd=true persist.data.ds_fmc_app.mode=0 persist.ims.regmanager.mode=0 ro.bluetooth.request.master=true ro.qualcomm.bluetooth.ftp=true ro.qualcomm.bluetooth.sap=true ro.bluetooth.remote.autoconnect=true debug.bt.discoverable_time=0 persist.sys.strictmode.visual=false persist.omh.enabled=1 ro.config.ehrpd=true ro.qualcomm.cabl=1 ro.ril.transmitpower=true ro.fm.analogpath.supported=true ro.fm.transmitter=false ro.fm.mulinst.recording.support=false ro.emmc.sdcard.partition=19 ro.staticwallpaper.pixelformat=RGB_565 debug.camcorder.disablemeta=0 persist.fuse_sdcard=false ro.config.hw_allowformat=true ro.config.hw_allow_ums_and_mtp=true ro.config.switchPrimaryVolume=true debug.camera.landscape=true ro.max.fling_velocity=4000 ro.config.hw_addsettingsdbex=1 httplive.enable.discontinuity=true dev.pm.dyn_samplingrate=1 dev.pm.dyn_sample_period=700000 persist.thermal.monitor=true debug.hwui.render_dirty_regions=false debug.enabletr=false debug.hwc.dynThreshold=1.9 debug.composition.7x27A.type=mdp debug.composition.7x25A.type=mdp debug.composition.8x25.type=dyn debug.sf.hw=1 ro.qc.sdk.camera.facialproc=false ro.qc.sdk.gestures.camera=false debug.sf.swaprect=1 persist.gralloc.cp.level3=1 # Display ro.lcd.backlight=75 ro.button.backlight=20 ro.sf.lcd_density=240 # Dalvik dalvik.vm.heapsize=128m dalvik.vm.heapgrowthlimit=48m dalvik.vm.heapstartsize=5m dalvik.vm.heaputilization=0.25 dalvik.vm.heapidealfree=8388608 dalvik.vm.heapconcurrentstart=2097152 dalvik.vm.stack-trace-file=/data/anr/traces.txt dalvik.vm.dexopt-flags=m=y # # ADDITIONAL_BUILD_PROPERTIES # ro.config.ringtone=CyanTone.ogg ro.config.notification_sound=Tejat.ogg ro.config.alarm_alert=Oxygen.ogg ro.com.android.dataroaming=false ro.com.android.dateformat=dd-MM-yyyy ro.vendor.extension_library=/system/lib/libqc-opt.so net.bt.name=Android ro.com.google.clientidbase=android-huawei ro.telephony.default_network=0 ro.ril.hsxpa=1 ro.ril.gprsclass=10 # Huawei Added wlan.driver.status=ok hw.cabl.level=2 hw.cabl.version=1.0.20120512 persist.sys.strictmode.disable=1 persist.radio.force_nw_search=1 persist.timed.enable=true del.autofill.for.qcom=true net.dns.cache_size=512 net.dns.cache_ttl=600 net.tcp.fin.aggregation=1 net.webkit.cache.mindeadsize=4194304 net.webkit.cache.maxdeadsize=4194304 net.webkit.cache.size=12582912 net.webkit.setpri=1 hw_internal_sd=true drm.service.enabled=true ro.use_data_netmgrd=true ro.config.usesEncodingDetector=1 ro.config.fm_type=libqcomfm_if ro.config.hw_GSensorOptimize=true ro.config.hw_proximity=true ro.config.xtra_support=true ro.config.camera.afctl.enable=true ro.config.hw_handset_mic=primary ro.config.hw_virtualsdcard=true ro.config.hw_power_saving=true ro.config.move_up_display=true ro.config.hw_eapsim=true ro.config.internal_sdcard=yes ro.config.umts_no_feat_ccat=true ro.config.incall_notify_mms=true ro.config.hw_gcf_mms=true ro.config.hw.usedtime.statis=1 ro.config.g2w_resel_dis_opt=true ro.config.hwft_PinPukUnlockscr=true ro.config.umts_no_feat_ccat=true ro.config.DOMAIN_ASCII_ONLY=true ro.config.showEmergencyNumber=true ro.config.hw_sd_swith=true ro.config.hwft_simrefresh=true ro.config.keypasstouser=true ro.config.remove_air_plane=true ro.config.hwecc_feature=true ro.config.hw_sd_swith=true # Huawei Disabled sys.media.vdec.sw=0 persist.cne.UseCne=none persist.cne.fmc.mode=false ro.camera.sound.forced=0 ro.dual.sim.phone=false ro.config.dualmic=false ro.config.hw_dsda=false ro.config.hwtheme=0 ro.config.show_battery_id=false ro.config.hw_tether_dun_enable=0 ro.config.hw_remindBT=false ro.config.hw.security_enabled=false ro.config.hw_smartcardservice=false ro.config.hw_accesscontrol=false ro.config.hw_support_ipcall=false ro.config.hw_voicerecord=false ro.config.hw_lockscreen=false ro.config.hw_menu_unlockscreen=false ro.config.hw.security_enabled=false # ViPER4Android Disabled lpa.decode=false # Huawei ro.confg.hw_appsbootversion=Y300-0100V100R001C00B199_APPSBOOT ro.confg.hw_appversion=Y300-0100V100R001C00B199_KERNEL ro.confg.hw_appfsversion=Y300-0100V100R001C00B199_SYSIMG # Tweaks persist.adb.notify=0 I tried a pure unmodified stock Huawei B199 and the bug is not present here I think we need to track again the changes Huawei made on B209 Edited September 28, 2014 by fonz93
Guest H3ROS Posted September 28, 2014 Report Posted September 28, 2014 (edited) So stock B199 doesn't have the problem but B199 FusionX does. And stock B209 has the problem with every ROM. I think the easier thing for me to do here would be to try your build.prop and then to compare FusionX to SlimStock. That SIM not present message isn't 100% accurate. You can tell that Huawei screwed up RIL because when in airplane mode I believe it's supposed to display no message for Android 4.1.1. That's if what my virtual device is showing me is correct. The stock B199 that you're trying, does that have the cust partition correctly setup? Edited September 28, 2014 by H3ROS
Guest fonz93 Posted September 28, 2014 Report Posted September 28, 2014 The stock B199 that you're trying, does that have the cust partition correctly setup? Yes, it is working, on B199 (and B209 too) Huawei uses the countries folders ("weu" etc, i am in "weu", so it loads the "weu" folder)
Guest Nomm Posted September 29, 2014 Report Posted September 29, 2014 The default storage location is your SD card because when you download files you're not going to run out of space that way. It can be changed by changing the following line in build.prop: persist.sys.main_storage=external_sd Into this: persist.sys.main_storage=internal_sd As for the install behaviour that's set to auto. That means that most apps are installed onto the system memory unless they're very large (a game that downloads extra content) and for everything else you'll get the option to move the app to your SD card only if the app supports it. Having it setup like this means that there's going to be no stability issues or apps crashing unexpectedly. You can adjust the install behaviour by using Link2SD. In it's settings there's an option to change it between auto, internal and external. @Nomm I've seen it, but I can't do that yet. It's actually a large change that requires multiple files to be edited. I'll try to get it done, but it probably won't be for this next update. @MarioKralj Check that the ringtones are setup correctly. I don't use the facebook app myself, but I'm pretty sure it installs them to the SD card. okay whenever you feel like doing this large change bro ;) i am eagerly waiting for you to be healthy as a horse again and release amazing updates
Guest H3ROS Posted September 29, 2014 Report Posted September 29, 2014 Yes, it is working, on B199 (and B209 too) Huawei uses the countries folders ("weu" etc, i am in "weu", so it loads the "weu" folder) I tried SlimStock today and found that it has the exact same issue as B209 on my phone. It'll only display the correct message if I put it in airplane mode and then reboot.
Guest fonz93 Posted September 29, 2014 Report Posted September 29, 2014 (edited) I tried SlimStock today and found that it has the exact same issue as B209 on my phone. It'll only display the correct message if I put it in airplane mode and then reboot. I don't know why it does it on you, but on me didn't, did you try stock B199? Edited September 29, 2014 by fonz93
Guest H3ROS Posted September 29, 2014 Report Posted September 29, 2014 I don't know why it does it on you, but on me didn't, did you try stock B199? I don't have a stock B199 to hand. I deleted a lot of files that I had laying around after switching to B209. If you've got one I'll try it though. It might have something to do with how your carrier requires the cust partition in order to display the correct network name. It likely triggers the bug differently for you.
Guest fonz93 Posted September 29, 2014 Report Posted September 29, 2014 I don't have a stock B199 to hand. I deleted a lot of files that I had laying around after switching to B209. If you've got one I'll try it though. It might have something to do with how your carrier requires the cust partition in order to display the correct network name. It likely triggers the bug differently for you. I used this B199 to test: https://docs.google.com/file/d/0B1th-jpHK5tXZnZwYjNKYzhpZjg/edit?pli=1, there is no official link for it on Huawei site
Guest Tonal4Nagual Posted September 29, 2014 Report Posted September 29, 2014 The default storage location is your SD card because when you download files you're not going to run out of space that way. It can be changed by changing the following line in build.prop: persist.sys.main_storage=external_sd Into this: persist.sys.main_storage=internal_sd As for the install behaviour that's set to auto. That means that most apps are installed onto the system memory unless they're very large (a game that downloads extra content) and for everything else you'll get the option to move the app to your SD card only if the app supports it. Having it setup like this means that there's going to be no stability issues or apps crashing unexpectedly. You can adjust the install behaviour by using Link2SD. In it's settings there's an option to change it between auto, internal and external. Tnx H3ROS
Guest krux3r Posted September 29, 2014 Report Posted September 29, 2014 Guys, does someone knows why Shuttle player uses so much ram, in my case 54mb? I use Omich player, and it uses just 24mb. It is not some major problem, I am just curious.
Guest H3ROS Posted September 29, 2014 Report Posted September 29, 2014 More options, more things displayed on screen, custom resources, more animations and it supports Gingerbread and up. So all of that is why it uses a little more memory.
Guest StewieTech Posted September 29, 2014 Report Posted September 29, 2014 H3ROS, could you consider injecting the app "Toggle 2G"(xda) by default on next update? I find it such an amazing app for what it does and quite a few roms have this app by default. Thanks.
Guest krux3r Posted September 29, 2014 Report Posted September 29, 2014 (edited) More options, more things displayed on screen, custom resources, more animations and it supports Gingerbread and up. So all of that is why it uses a little more memory.I checked the ram usage of it, it doesnt run just itself it runs google play services and youtube when playing music, why is that? Edited September 29, 2014 by krux3r
Guest lomax84 Posted September 30, 2014 Report Posted September 30, 2014 (edited) hi all, are there new updates coming for this rom? are gapps included? thanks Edited September 30, 2014 by lomax84
Guest krux3r Posted September 30, 2014 Report Posted September 30, 2014 hi all, are there new updates coming for this rom? are gapps included? thanks I think H3ROS is working on it, the apps will be updated I guess.
Guest H3ROS Posted September 30, 2014 Report Posted September 30, 2014 (edited) I checked the ram usage of it, it doesnt run just itself it runs google play services and youtube when playing music, why is that? Google Play Services is normally running. As for YouTube, maybe it's a process that's remained in memory? It doesn't load up anything when I use Shuttle. @lomax94 It includes gapps. You can see some of the Google apps in the screenshots :) I think I've now got all of the bugs fixed, including the one fonz93 mentioned. @fonz93 I couldn't get it to work correctly even with the stock ROM's. I think it's due to how Huawei shares code between devices as the Y300/G510 stock ROM's contain a lot of code for a second SIM card. That would explain why the network name moves to the right. Huawei has changed some of the code from what I'll show you here, but this will allow you to understand the problem. private void updateCarrierStateWithSimStatus(State simState) { if (DEBUG) Log.d(TAG, "updateCarrierTextWithSimStatus(), simState = " + simState); CharSequence carrierText = null; int carrierHelpTextId = 0; mEmergencyButtonEnabledBecauseSimLocked = false; mStatus = getStatusForIccState(simState); mSimState = simState; switch (mStatus) { case Normal: carrierText = makeCarierString(mPlmn, mSpn); break; case NetworkLocked: carrierText = makeCarrierStringOnEmergencyCapable( getContext().getText(R.string.lockscreen_network_locked_message), mPlmn); carrierHelpTextId = R.string.lockscreen_instructions_when_pattern_disabled; break; case SimMissing: // Shows "No SIM card | Emergency calls only" on devices that are voice-capable. // This depends on mPlmn containing the text "Emergency calls only" when the radio // has some connectivity. Otherwise, it should be null or empty and just show // "No SIM card" carrierText = makeCarrierStringOnEmergencyCapable( getContext().getText(R.string.lockscreen_missing_sim_message_short), mPlmn); carrierHelpTextId = R.string.lockscreen_missing_sim_instructions_long; break; So the SIM state would return as "SimMissing" when in airplane mode. The second parameter for makeCarrierStringOnEmergencyCapable contains the PLMN aka the provider name. So I patched the method to this... case SimMissing: // Shows "No SIM card | Emergency calls only" on devices that are voice-capable. // This depends on mPlmn containing the text "Emergency calls only" when the radio // has some connectivity. Otherwise, it should be null or empty and just show // "No SIM card" // // Huawei screwed this up. The PLMN never gets cleared and it's probably due to the // changes Huawei made for dual SIM support. The quick fix? Send null anyway. carrierText = makeCarrierStringOnEmergencyCapable( getContext().getText(R.string.lockscreen_missing_sim_message_short), null); carrierHelpTextId = R.string.lockscreen_missing_sim_instructions_long; break; Edited September 30, 2014 by H3ROS
Guest fonz93 Posted September 30, 2014 Report Posted September 30, 2014 So if the emergency message is your provider name then it'll write null instead, meaning you'll only get the no SIM card message that you'd expect to get :) Very good work, as always ^_^
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now