Guest naghtan Posted August 9, 2012 Report Posted August 9, 2012 Edit: I think I fixed the logging mess that Huawei insist on causing. I can't test right now as USB is completely dead obviously. :P Now, if you'll excuse me, It's 3:46am and I need to "hibernate". :ph34r: Are you overclocked too? jejeje that looks you are a genius or these its so easy! but you run so fast! Please keep going! Great Works!
Guest Dazzozo Posted August 9, 2012 Report Posted August 9, 2012 The way they word that - it's as if they believe it has an accelerated UI already. Yeah this upgrade is seriously taking the urine. I would've expected reasonably to have seen a Jelly Bean upgrade within a month or two.
Guest wrtease Posted August 9, 2012 Report Posted August 9, 2012 that could be so. or a new model with it on it.
Guest Dazzozo Posted August 9, 2012 Report Posted August 9, 2012 I think I just sped everything up significantly. :P Edit: must... stop and fix USB...
Guest unaszplodrmann Posted August 9, 2012 Report Posted August 9, 2012 :lol: Damned priorities! At least your foray into overclocking could be of use more generally, outside of a CM port...
Guest Dazzozo Posted August 9, 2012 Report Posted August 9, 2012 I'm in the process of redoing and decluttering all the init scripts. I feel that by continuing to use the ones from Gingerbread that are just left over in the repo it's causing us some issues, and from what I'm looking at right now it might fix USB. Edit: Don't make me do that again, please. :( My neck is killing me.
Guest unaszplodrmann Posted August 9, 2012 Report Posted August 9, 2012 Why was the Netfilter MSS module borked? That just seems really odd.
Guest Dazzozo Posted August 9, 2012 Report Posted August 9, 2012 I think it crossed a case-insensitive file system at some point during the open sourcing which dropped xt_TCPMSS down to xt_tcpmss, which are different files. Strange how it only had an effect on those two, though. Ultimately two files that are only different in capitalisation became equal. It's happened before, it's happened to me. I've had to keep an Overlay.h and an overlay.h in the same directory and it crossed over Windows one day and boom, I was there figuring it out for hours. Edit: no biggie either, it seems netfilter is the only part of the kernel that Huawei didn't feel the need to fiddle with and add ifdeffing everywhere for CONFIG_HUAWEI_KERNEL. I just grabbed it from the Android kernel repos.
Guest ramitos Posted August 9, 2012 Report Posted August 9, 2012 (edited) I still couldn't boot with this cm10 build. Here is my steps:wipe data/factory resetwipe cache partitionReboot Recoveryinstall zip from sdcardwait more than 10m on the huawei boot logorestartwait againformat /cacheformat /dataformat /systemformat /datadataformat /custReboot Recoveryinstall zip from sdcardwait more than 10m on the huawei boot logorestartwait again Is there any log I can get to figure out the problem? Edited August 9, 2012 by ramitos
Guest Dazzozo Posted August 9, 2012 Report Posted August 9, 2012 Well that's exactly your point. If you can't get it to even boot there are no logs. Again, in CWM:Wipe data/factory resetReboot RecoveryInstall zip from sdcardReboot system now These are the exact steps I follow religiously every time I flash every build I've made in the past 24 hours and it's worked every time. (Besides for when I got curious and disabled CONFIG_HUAWEI_KERNEL).
Guest Valicek1 Posted August 9, 2012 Report Posted August 9, 2012 I had same problem with CM9 and CWM on my G300.. I tried TWRP and it works fine :) Link1 - http://www.modaco.com/topic/353879-team-win-recovery-for-huawei-u8815ascend-g-300/ Download v.2.2: http://goo.gl/6m3GO - > just burn it via fastboot.
Guest Dazzozo Posted August 9, 2012 Report Posted August 9, 2012 #STOPSHIP: Remove logwrapper and -d option before production service bluetoothd /system/bin/logwrapper /system/bin/bluetoothd -d -n [/CODE] Well that didn't happen did it
Guest kirilmanika Posted August 9, 2012 Report Posted August 9, 2012 I installed version from 01/07/2012 but I don't have network coverage. Help me. I'm in normal mode, not in airplane.
Guest Dazzozo Posted August 9, 2012 Report Posted August 9, 2012 You flashed it over B926/7. We don't have a reversed RIL implementation for the 2030 baseband yet. This only works on the 109808 baseband.
Guest unaszplodrmann Posted August 9, 2012 Report Posted August 9, 2012 #STOPSHIP: Remove logwrapper and -d option before production service bluetoothd /system/bin/logwrapper /system/bin/bluetoothd -d -n Well that didn't happen did it :rolleyes:
Guest carstenheuer Posted August 9, 2012 Report Posted August 9, 2012 This Rom only works on the 109808 baseband!!! put this in the first post ;)
Guest kirilmanika Posted August 9, 2012 Report Posted August 9, 2012 No, before I had "infusion rom",but I wipe data before install this rom. What I should to do for normal work? thanks
Guest Dazzozo Posted August 9, 2012 Report Posted August 9, 2012 No, before I had "infusion rom",but I wipe data before install this rom. What I should to do for normal work? thanks Which is B926/7. You're going to have to downgrade to a B8xx base ROM until we have someone able to reverse the new RIL or I read up enough on it.
Guest ramitos Posted August 9, 2012 Report Posted August 9, 2012 (edited) Just to make sure I'm not crazy, I tested your previous build (cm-10-20120721-UNOFFICIAL-u8818) and it booted just fine. And also tried TWRP (thanks Valicek1 for the tip) Edit: I'm using cm9-20120701 with 109808 baseband Edited August 10, 2012 by ramitos
Guest Dazzozo Posted August 10, 2012 Report Posted August 10, 2012 I just got ADB working which will lead on to mass storage, MTP etc quite easily. That was the most frustrating thing I've done in my entire life for something so simple. Huawei over-complicating things again... Edit: Working on Wi-Fi now, almost done Edit 2: compiling...
Guest unaszplodrmann Posted August 10, 2012 Report Posted August 10, 2012 I can only imagine that adding an unnecessary condition everywhere was almost as frustrating as removal... At least you're cooking on gas now! I'll pitch in with testing when hardware support is initially completed. I rely on my mobile during the week and only have a G300 atm, so I'm reluctant to jump onboard in the early stages ;)
Recommended Posts