It's funny cos I have never set up fastboot, I don't even know what it does. What does it do?
Anyway, I just flashed 1.4RC and hotfix2 and I don't see any change at all compared to 27/4/12 build, the compache isn't even disabled as said in the release notes.
I'll wipe battery stats and do a full battery test tommorrow.
EDIT: Actually yeah, the compass is still stuffed up
Quote:
Originally Posted by yo9gnc
hi,
i flashed the 29072012 (without reading the touch screen problems). finally i flashed the hotfixes and the phone is responsive and usable. still camera won`t work (and obvious camera related apps).
i have an u8180 (orange stockholm).
another thing: the cm7 roms from goo manager should be flashed between them with or without wiping (i didn`t wipe anything)?
Let me explain: Huawei's kernel source has support for TWENTY Huawei models, and some models have hardware sub-versions. The U8160 and U8180 are actually the same hardware (code HD1U813M), but there are two sub-revisions: A and C (the U8160 can be either and the U8180 is only revision C). However, it seems that even within these revisions there can be variance in the hardware installed.
For some reason, Huawei builds support for all twenty devices in its kernel configuration (which is seen in the configuration file included in the source, but also in production kernels found in stock roms). This is not very efficient, since I know for sure that my port only needs to support two devices.
I've removed a lot of drivers from the build configuration that aren't needed on my particular phone, but it seems that other U8160 and U8180 models are still missing some drivers (camera and compass, maybe more?). I'll try to identify the missing drivers for you guys and put it in the next hotfix; ideally, I don't want to go back to using the monolithic kernel config.
I do need more information to be sure, though:
Repartee: install "Sensor List", and tell me the name of the compass hardware/hardware that's not functioning. Also, does the compass never work, or does it work sometimes?
yo9gnc: does the camera never work at all, or does it stop working after some time? Try to reboot and see if it returns.
Let me explain: Huawei's kernel source has support for TWENTY Huawei models, and some models have hardware sub-versions. The U8160 and U8180 are actually the same hardware (code HD1U813M), but there are two sub-revisions: A and C (the U8160 can be either and the U8180 is only revision C). However, it seems that even within these revisions there can be variance in the hardware installed.
For some reason, Huawei builds support for all twenty devices in its kernel configuration (which is seen in the configuration file included in the source, but also in production kernels found in stock roms). This is not very efficient, since I know for sure that my port only needs to support two devices.
I've removed a lot of drivers from the build configuration that aren't needed on my particular phone, but it seems that other U8160 and U8180 models are still missing some drivers (camera and compass, maybe more?). I'll try to identify the missing drivers for you guys and put it in the next hotfix; ideally, I don't want to go back to using the monolithic kernel config.
I do need more information to be sure, though:
Repartee: install "Sensor List", and tell me the name of the compass hardware/hardware that's not functioning. Also, does the compass never work, or does it work sometimes?
yo9gnc: does the camera never work at all, or does it stop working after some time? Try to reboot and see if it returns.
psyke i would like to thank you for all the effort and dedication that you put in this rom
first thanks psyke great job i'm totally agree with you all the ifdefs very hard to look through, potentially bugs and 'unavailabe' storage
and second push:
Quote:
Originally Posted by Elibl
could someone please check if he gets a haptic feedback (vibration) from the onscreen touch keys in cwm recovery?
i need some clarity i compiled cwm recovery with support and mapping of virtual on screen keys (home, menu...) fully working but i want to know if they were already working right before...
first thanks psyke great job i'm totally agree with you all the ifdefs very hard to look through, potentially bugs and 'unavailabe' storage
and second push:
i need some clarity i compiled cwm recovery with support and mapping of virtual on screen keys (home, menu...) fully working but i want to know if they were already working right before...
I don't think so, but I'm using a v6 recovery on my phone at the moment. I haven't tried any of the touch modifications (but I see that koush is still keeping part of his code proprietary).
@psyke83
Hello!
I have 1.4 hotfix 2 release.
I am also experiencing some troubles with camera, like yo9gnc. I also have U8180, however it is not Orange Stockholm.
Problem is that it doesn't working at all. Reboot doesn't fix that.
While opening Camera I got that error:
"Camera Error
Cannot connect to camera."
psyke, I am experiencing strange behaviour with my wireless on the u8160 phone after the RC1.4+hotfix1+hotfix2. At home on the WPA wireless everything seems to be working, but at the university at the WPA2-PSK network like eduroam with PEAP although it does connect, only the white bars are present, no green ones. I tried to reset the network, reboot, it says i am connected, but a browser and nothing else can actually download anything. It worked before, and the wireless does work with my computer.
Logcat attached.
What can be the problem? Some modules missing maybe?
I don't think so, but I'm using a v6 recovery on my phone at the moment. I haven't tried any of the touch modifications (but I see that koush is still keeping part of his code proprietary).
thanks ok i saw in recovery code (minui/events.c) that virtual hardcoded keys (/sys/board_properties/virtualkeys.*) like we have are already supported form recovery 5.x.x.x they just didn't worked for me but after compiling cwm from gb-release-7.2 branch they suddenly just worked and i only needed to map them from recovery_ui.c
link (zip not cwm flashable!!! tested with my u8160)
i'll have a look if i can implement hardcoded on screen key support to ics recovery... (as i was able to see there is nothing in there like that)
btw: little tweak: if you create .one_confirm no matter what content in /sdcard/clockworkmod/ you wont have in some confirmations the multiple no's...
btw: how do you switch between cyanogenmod branches (eg gingerbread and ics)? i'm very new to all this via repo init?
but sorry for ot -> btt i'll check out your release the next days when i've got time thanks a lot for all your work
@psyke83
Hello!
I have 1.4 hotfix 2 release.
I am also experiencing some troubles with camera, like yo9gnc. I also have U8180, however it is not Orange Stockholm.
Problem is that it doesn't working at all. Reboot doesn't fix that.
While opening Camera I got that error:
"Camera Error
Cannot connect to camera."
After almost a month with the frustrating 20120702 build (sorry psyke83 ) and about 10 reboots a day, I also installed the latest 20120729 build + hotfix1&2(
(btw I could not restore from the 20120702 build to my previous backup as I always got an error..)
So far the phone seems smoother, as it did in previous versions, default governor is now "ondemand" which seems much better
The "random waking up from sleep" glitch seems to be gone,
The other glitches remain, stock camera app doesnt work and now even 3rd party camera apps stopped working.
The phone keeps resetting randomly, and whenever it resets it seems to do it like 3 or 4 times in a row.
The music-player-skip-track glitch still happens,
Did not try the compass yet as I rarely use it.
I know it's apples and oranges,but here are the sensors that're on the fritz for me in CM9 on the 8160 as per the app you mentioned earlier to repartee:
Working:
G-sensor(model name not given)
APS-12D Combo Proximity sensor/Light Sensor
Not Working(all stuck at 'waiting for update'):
AK8973's Magnetic field sensor,Compass and Thermometer sensors.
Rotation Vector Sensor ( 2/11 -> no device name given)
Hope ^ help out for the CM7,but also that you somehow find a way to get them ticking under ICS without having to do open-device surgery (or wait a couple of aeons for a new ROM revision ...)
We are the Børg.Get assimilated. Resistance Sucks.
=======================================
Most of us take the simple act of waking up our devices and having a quick glance at the … more
XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality. Are you a developer?