Found the solution!
It was by matlacki, basically just reflash stock ruu 1.32, re-root and restore your nanadroid and it's all good.
matlacki said:
I had the same problem yesterday and I found the solution (it works for me). Flashed stock RUU 1.32, rooted again, eng/radio-s off, again, flashed CW7 bulid 30 and my proxymity sensor is back to normal.
Click to expand...
Click to collapse
I have done the same and now my proximity sensor is working again when restored from my CM7 nanadroid.
This doesnt make any sense?!
==================================================
Btw i am using build 30
For those who having this proximity sensor issue like myself , I done a test.
Go to setting > CyanogenMod setting >display > automatic backlight > > tick use custom > edit other levels.
For me I can see my sensor functioning will. 7 for total darkness and 59 for din light and 190+ for lamp.
Now try to make a call and watch the screen go off. You can't on it back but there's still ringing tone.
I used my nexus one flash to shine on the sensor and my screen turned back on.
Now go back to the edit other lvl notice that the light sensor doesn't response to the different brightness.
A reboot will fix the problem but if there's s phone call,this bug starts again. Try it!!!
And share your results. If there's ppl with the same as mine, it might be a cm7 bug and not s proximity sensor failure
Its not a CM7 bug. I have never had the proximity sensor problem on any ROM, be it stock or otherwise.
I'm also using build 30 and no proximity sensor problem to report.
i want to believe its not a CM7 bug.
For the past 2 weeks when I was using various CM7 builds, I do not have any proximity issues as described by other users till yesterday, it just popped up.
Nandroid to my old backup (which has no such the problem), and problem still persist.
flashed back to RUU 1.32 rom and the sensor is working in sense rom.
So now i cant even send back for a replacement.
matlacki said:
I had the same problem yesterday and I found the solution (it works for me). Flashed stock RUU 1.32, rooted again, eng/radio-s off, again, flashed CW7 bulid 30 and my proxymity sensor is back to normal.
Click to expand...
Click to collapse
I have done the same and now my proximity sensor is working again when restored from my CM7 nanadroid.
This doesnt make any sense?!
This problem started yesterday evening for me. 5days of CM7 without issues and now this dealbreaker. Need to pull battery after end of a call.
Sent from my Desire HD using XDA App
try flashing 1.32 RUU and redo the whole rooting again > and back to CM7.
seems unreal but it really did solve my problem..
Okay...
I'm having the same problem, i just checked it with the program "Sensorlist" which gives me info about the proximity sensor....
With CM7 it doesn't work, but with stock rooted ROM it works fine...
So it must be a problem with the CM7 software....
Has anyone solved the problem, so it doesn't come back?
Solved my Problem, too.
And I guess I've found the reason for the Problem.
Within the last Days, I've played around a little with the ambient light sensor settings. Both, system side and also with the additional cyanogen settings.
Why do I come to that conclusion?
Well, I made a Backup of all my Apps and Settings via TitaniumBackup.
Then I:
- Wiped my phone via CW + Full-Wipe.zip
- Flashed this 1.72 via CW http://forum.xda-developers.com/showthread.php?t=884327. Tested it = everything fine.
- Wiped again + clean installed PNK_AB CM7. Testet it = everything fine.
- Restored my Apps + Settings. Failure retuned after restart.
Now I was sure, it is Software related.
- So I wiped the data partition via CW and restarted. Everything fine again. Even after Reboot.
- Time to restore Apps + Settings, but this time without the settings from the Cyanogen Apps/Settings, Debug App and SpareParts. Everything fine in first, but the problem retourned after reboot.
- So again: wiping data = everything fine. Rebooted about five times, te be sure. Everything fine.
- Restored Apps + Settings: without: Cyanogen Apps/Settings, Debug App, SpareParts AND SystemSettings.
Voila: The Problem was away and didn't even come back after several reboots.
So my conclusion:
CM7 ambient light settings and system ambient light settings mess each other up. Dunno, which is causing the problem, but it is solved for me, yet.
What's your Opinion guys?
My findings (with input from Apache14):
- The proximity issue only affects those with a non-Sharp LCD.
- The kernel source code released by HTC does not contain the correct code to handle this device. I am still looking for solutions.
- On the 1.32 kernel, when proximity is required, some polling mechanism is activated. I assume this is needed as there is no Interrupt hooked up on a hardware level on this LCD/chip (same sensor uC however).
- There is no source code for this. Not in HTC released kernel source or CM or AOSP.
Currently I am looking at either:
- Getting the latest source code for the DHD kernel which HTC has failed to release. The source code corresponds to some RUU older than 1.32.
or
- Hacking the kernel to do the same polling as present in the 1.32 kernel binaries.
McKebapp said:
Solved my Problem, too.
And I guess I've found the reason for the Problem.
Within the last Days, I've played around a little with the ambient light sensor settings. Both, system side and also with the additional cyanogen settings.
Why do I come to that conclusion?
Well, I made a Backup of all my Apps and Settings via TitaniumBackup.
Then I:
- Wiped my phone via CW + Full-Wipe.zip
- Flashed this 1.72 via CW http://forum.xda-developers.com/showthread.php?t=884327. Tested it = everything fine.
- Wiped again + clean installed PNK_AB CM7. Testet it = everything fine.
- Restored my Apps + Settings. Failure retuned after restart.
Now I was sure, it is Software related.
- So I wiped the data partition via CW and restarted. Everything fine again. Even after Reboot.
- Time to restore Apps + Settings, but this time without the settings from the Cyanogen Apps/Settings, Debug App and SpareParts. Everything fine in first, but the problem retourned after reboot.
- So again: wiping data = everything fine. Rebooted about five times, te be sure. Everything fine.
- Restored Apps + Settings: without: Cyanogen Apps/Settings, Debug App, SpareParts AND SystemSettings.
Voila: The Problem was away and didn't even come back after several reboots.
So my conclusion:
CM7 ambient light settings and system ambient light settings mess each other up. Dunno, which is causing the problem, but it is solved for me, yet.
What's your Opinion guys?
Click to expand...
Click to collapse
how can you remove these parts from the Rom? "the Cyanogen Apps/Settings, Debug App and SpareParts. "?
Sent from my Desire HD using XDA App
Numsefis said:
how can you remove these parts from the Rom? "the Cyanogen Apps/Settings, Debug App and SpareParts. "?
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
Didn't remove them from the ROM.
I simply unticked them while/before restoring my FullBackup with TitaniumBackup.
For those that cant get proximity sensor to work on custom kernel/ROMS, try the following (no root required):
Code:
echo '0x50530b0c 0x140b0b0c' > /sys/devices/virtual/optical_sensors/proximity/ps_kadc
This will adjust the calibration values. The 0b part is the 'low tide' aka FAR start and 0c is the 'high tide' aka NEAR start.
IOW, values below FAR start is FAR, and values above NEAR start is NEAR.
Tested this on latest Buzz (Apache14) kernel.
Need to somehow make this persistent, and make sure it does not get reset during normal operation.
Stay tuned
Update: Still thinking of how to apply this at boot, maybe 'init.d' ? Also havent been reset during normal operation.
Thanks for the info
ok but how do you appli that ?
Text editor ? etc.
Flashing default (stock ruu) kernel
did it for me. Prox sensor working as intended.
Sent from my Revolutionized Desire HD using XDA App
I wrote an app to fix this.
See http://forum.xda-developers.com/showthread.php?p=11312762#post11312762.
Great work Leppie!
I had this problem, wile on CM6, started after I installed ADW EX. Used to use launcher pro, but realy liked the transisions in ex, so started using that, and got this problem. Updated to CM7, stil had the problem, no matter rom version. Went back to launcher pro, and now it works like normal. Thinking ther might be something with the launcher, and mabye a hardwere thing in some phones.
I am now on nihtly CM7 34, I think, and no problem.
So for those having this prob, try to switch to another launcher, and reboot a couple of times.
Hope this helps
how did you downgrade?
with Recovery?! or with Gold card?!
i have done both ways but didn't solve my problem :-(
please give me a link of Stock rom ruu!
Related
I am writing on this thread as i still cannot add to the development thread yet
I am using Elelinux-7.0.0-Hero-v2.0. Thanks Ele for a great rom.
So far the only problem i have had is once the unlock screen went invisible on me.
I had to use the patch which worked fine. no black screen. everything else works great so far.
Just trying to contribute to the developers what i can to help.
Any one else has any issue yet.
Elelinux-7.0.0-Hero-v2.0
RADIO VERSION:63.18.55.06SU_6.35.17.03
Kernel: Herokernel-12a
I've had the same issue with the lockscreen but like yourself it was a once off.
Generally the ROM is great (however, this is the first ROM that I've flashed to my hero)
The only other issue im getting is with linking facebook with my contacts; for some reason FB keeps crashing. But keep in mind that I'm a retard in comparison to what you lads know about custom roms etc..... but slowly learning!
Sent from my Hero using XDA App
same problems
I have had the same problems as you. lock screen went invisible a couple of times. and my facebook does not work quite right.
Apart from that has been very stable. no problems or reboots. works great.
Running gingerbread with honeycomb theme on my hero. running at 691mhz is well good.
I have got widgets running on every screen to.
Elelinux RC4 version 7.0 V2.0
kernel 12a
691mhz
clockworkmod.
Thanks Ele for a great rom
After installed 2.0 patch, I still get blank screen (wall paper ok, no any widgets).
The only way to solve is restart
Any thing wrong with my installation? (same spec as above post)
The Bug seems to affect some phones and not others. Might be due to different hardware but not sure.
I am a network engineer. Not a developer.
There is a patch that fixes the black screen bug which might help. You might have to delete dalvik cache first though. But as said not a developer.
I just wanted to try some different roms and loaded cronos rom yesterday and is very good. So running that at the moment.
It is really fast and stable. The fastest i have used so far. But i have not tested everything yet like GPS. But admit i am becoming a cronos fan.
Cheers.
P.s i always backup my phone first and do a complete wipe before trying a new rom. Otherwise could get problems.
I use clockwork mod.
Unfortunately the bug your getting with black screens, invisible menus etc.. is an aosp bug that affects some devices which Google are unable to fix, if you had read through the thread you would have seen this. Ele is working hard on a fix for this but as CM no longer support the hero, its unlikely many cm7 roms will see many updates.
Sent from my HTC Hero using XDA App
Everyone is hoping that Google will fix the memleak and invisible manus problem. To fix it, one needs to undersatand the big picture on how these things are managed. I think it can be done only by experienced coder.
It's a real shame. i love gingerbread and did not want to go back to 2.1 or 2.2.
But might have to if they do not fix it.
I know Ele is working hard on a fix. using his rom at the moment. Was using cronos. But suddenly started getting random reboots and battery started only lasting a few hours and could not find out why.
Thanks to all devs and help.
Elelinux 7.0 v2.1 GPS reboot issue
Hi all,
I found Elelinux 7.0 v2.1 to be almost perfect.
The only major issue so far for me is that when running applications such as sportstracker that use GPS and are running in the background, that as soon as the GPS connection is lost (for whatever reason) the phone always seems to crash.
I wonder whether anyone else has seen this issue and whether there's a way to investigate it.
E.g. is it possible ot redirect logcat to the sdcard and then analyze the log file?
Regards,
MJ
Her0 V2.1 - USB problem
This is a weird one...
I flashed to Elelinux 's fab 2.1 the usual way....
I booted into the ClockworkMod Recovery V2.5.0.7
-- wipe cache partition
-- Advanced - Wipe Dalvik Cache
-- reboot
Then again within Clockwork Recovery I choose 'Install zip from sdcard'
I select the Hero rom and it flashes perfectly...
Now the problem ----> I cant get the usb port working to enable transfer of files?
When the phone boots up it shows 'preparing sd card'
Then when i connect usb lead to pc it shows 'usb connected'
When i then pull the screen down, i see 'usb connected - select to copy files to/from your computer'
When i select that tab, it just crashes back to the home page?
I see the icon at the top of the screen but when i pull down the screen and select as above, it crashes back to home screen again?
In settings, i have both USB debugging and USB debugging notify - all enabled.
Can anyone provide a solution to this issue for me..
thank you
The only way around this problem i think is to mount usb storage from recovery.
Sent from my HTC Hero using XDA App
Hello.
This is where you can look at the tutorial and get the files to install if you feel like jumping into it ...
ICS Step by step and files
Note: if you do flash this and it hangs at the boot screen, pull the battery and flash it again and it should work. Some have had to do it 3 times.
I take no credit for this ROM and full props go to the developers of the above post and all those working to make this happen.
First the look and feel of ICS is nothing short of superb. The speed as of now is similar to all the other ROMS I have tried with a little chop here and there but nothing major.
Yes lots of little issues and items that do not work like the camera and GPS but not a huge deal for me so I am willing to stick to it.
Battery so far is decent. 13 hours and 43 min. on the first charge to calibrate and sitting at 24% still. This included allot of playing with the phone and reboots to test jigs
As for the issues that are somewhat bothersome, they include the following.
1. No home or search button. I know same as usual when installing an i9000 ROM but the key mappings from the GB ROMS does not work.
2. BLN (issue all around) will remain lit until you wake the phone to get the notification.
3. They had to do some funky stuff to get 3G to work so it lags to start. Not a huge deal cause it does start and remain working.
I will be continuing to use this ROM and hopefully everything will be working soon (these guys are flying. Also I have been told that the folks over at Glitch are already working on the kernels for the ICS port so that is promising as well.
If there are any other out there running this on our phone chime in with your thoughts or fixes if you have any.
Thanx
Bucky
Thanks for starting this thread. Can't wait to hear about your progress.
Alpha 7
Hey here is the update ...
Installed the Alpha 7 update today and I have to say this rom is fantastic.
1. Camera is fixed and works like a charm.
2. GPS locked in seconds and accurate indoors!! Big improvment over all other roms I have used.
3. HW Acceleration is fixed and working from what I can tell
4. You Tube is fixed and can watch video
Still on the not working list
1. Can not plug the phone in while off as it just restarts. this is a work in progress and known issue
2. Can not record video
3. Will not read a SIM card for contacts and so on (thank god for Google sync)
4. Still no home or search buttons (I think I may need to work on that on myself unless a kernel is released)
SO my review so far ...
No real issues with the general use of the phone. Text, phone, email and web are solid, I have installed apps from the market with no issues and not one FC yet. Battery life is good and nothing is taking over. I have been able to use the phone all day and still have lots left over before going to bed and plugging in. I have not been through a full battery as of yet but that is what I am working on now.
Memory - Last I looked I had 174MB of memory remaining which is the highest I have seen.
ICS is really smooth and fast while moving around. I am going to continue to play with it and report back here for everyone.
I don't use a whole lot of apps so there won't be much regarding those.
Thanx for stopping by and I will post pics when I can.
Bucky
Nevermind
Sent from my SCH-I500 using XDA App
Thanks for the update. From your review, it sounds like an awesome rom. Can't wait to try it but need them to fix the video recording first. Although I might just cave and try it out just to see what the fuss is all about
Can always restore my current setup... lol.
Update ...
been getting the SOD today and not sure why, I mentioned above that the HW acceleration was working, I misunderstood and it is not fully working yet.
I found that the system partition is very small. There was an update which required copying libs and there was not enough space left to do this (2MB). Not too sure if this is due to coming from MIUI or just a ROM issue.
Alpha 8 was released but had quite a few issues so not flashing that one.
Daily use has been great so far (except for the SOD) with no reception or data issues.
I am still working on the home and search buttons but I think that will get fixed with a kernel update. I tried the keymap file but these buttons do not even register in recovery so I get nothing in the ROM either.
More to come ...
Haven't tried this (likely won't as I need the phone for work) but buck have you tried the manual key fix - some directions in our thread on putting on Darkys 10.3.
Sent from T959D running Miui
Yup been there done that no go
Sent from my GT-I9000 using XDA App
Hey buck , was doing some searching in teamhacksung's thread about their ICS port, and someone suggested to change the following and then the key mapping for our phones will work properly. Not sure if the file system is the same for both, but definitely a bit of info if it isn't!
All you have to do is change this part on**arch/arm/mach-s5pv210/mach-aries.c*
*Original**(line 1216~1221)
static const int touch_keypad_code[] = {
#if defined (CONFIG_SAMSUNG_GALAXYS) || defined (CONFIG_SAMSUNG_GALAXYSB)
KEY_MENU,
KEY_BACK,
*0,*
*0*
----------------------------------------------------------------------------*
*Edited*
static const int touch_keypad_code[] = {
#if defined (CONFIG_SAMSUNG_GALAXYS) || defined (CONFIG_SAMSUNG_GALAXYSB)
KEY_MENU,
KEY_BACK,
*KEY_HOME,*
*KEY_SEARCH*
Sent from my GT-I9000 (T959 mod) using XDA App
Thank for the input. After flashing bata 1 all the buttons are working. More to come: )
Sent from my GT-I9000 using XDA App
Hey, have a telus fascinate too. Know how to flash and all that fun stuff. Just don't fully follow where you make the changes for key mapping...if you could just guide me in the right direction, I can figure the rest out...
changes in the kernel zip? the beta zip? after flashing? something completely different?
thanks a lot!
There are no changes to be made with this ROM, they are built in. Just flash and all good.
I will post update tonight after work.
Sent from my GT-I9000 using XDA App
yeah sorry realized that immediately after posting / flashing to the new rom.
have you tried out BT audio? I can connect to different devices but audio won't stream
havoksupertwit said:
yeah sorry realized that immediately after posting / flashing to the new rom.
have you tried out BT audio? I can connect to different devices but audio won't stream
Click to expand...
Click to collapse
There are allot of BT related posts in the QA. I personally do not use any BT but I do have a headset that I will try when I get home.
Seems to be a battery drain issue too as my phone is now dead but I have not calibrated so we will see after I do that.
bucknetbucky said:
Seems to be a battery drain issue too as my phone is now dead but I have not calibrated so we will see after I do that.
Click to expand...
Click to collapse
Calibrated my phone this morning. Heavy use today configuring everything but about 52% now (sooo 5 hours or use?)
Why god! Whhyyy!!
bucknetbucky said:
There are allot of BT related posts in the QA. I personally do not use any BT but I do have a headset that I will try when I get home.
Seems to be a battery drain issue too as my phone is now dead but I have not calibrated so we will see after I do that.
Click to expand...
Click to collapse
AT LEAST YOU GUYS HAVE IT RUNNING!!
I am having a hell of a time trying to get it to work. I have tried so many different ways to get it up and running but no luck.
I've tried installing it from MIUI 3 times but all I get when trying to boot into ICS for the first time is a Black Screen after the FuguMod boot screen.
The funny thing is that the 4 soft buttons at the bottom light up still.
So I then decided to try the JVT way:
-Flashed JVT DARKYROM (ODIN)
-Lagfix OFF
-FULL WIPEs (factory reset, cache, dalvik)
-FLASHED CM7.1 STABLE
-FULL WIPEs (factory reset, cache, dalvik)
-Flash ICS BETA1
-Flash kernel
-FOR THE SECOND TIME:
-Flash ICS BETA1 AGAIN
-Flash kernel AGAIN
Same issue, black screen after the FuguMod boot screen, buttons still light up.
So i tried a couple more times in a few different ways based off what I have already tried, but this time, before booting into ICS for the first time, I installed the 'Superuser-3.0.6-efgh-signed.zip' package.
Same issue. I'm not having any luck here.
iwebsource said:
AT LEAST YOU GUYS HAVE IT RUNNING!!
I am having a hell of a time trying to get it to work. I have tried so many different ways to get it up and running but no luck.
I've tried installing it from MIUI 3 times but all I get when trying to boot into ICS for the first time is a Black Screen after the FuguMod boot screen.
The funny thing is that the 4 soft buttons at the bottom light up still.
So I then decided to try the JVT way:
-Flashed JVT DARKYROM (ODIN)
-Lagfix OFF
-FULL WIPEs (factory reset, cache, dalvik)
-FLASHED CM7.1 STABLE
-FULL WIPEs (factory reset, cache, dalvik)
-Flash ICS BETA1
-Flash kernel
-FOR THE SECOND TIME:
-Flash ICS BETA1 AGAIN
-Flash kernel AGAIN
Same issue, black screen after the FuguMod boot screen, buttons still light up.
So i tried a couple more times in a few different ways based off what I have already tried, but this time, before booting into ICS for the first time, I installed the 'Superuser-3.0.6-efgh-signed.zip' package.
Same issue. I'm not having any luck here.
Click to expand...
Click to collapse
OK so here is what I did ...
Started from MIUI 1.11.18
1. Do a nandroid backup
2. download all the files to the SD card. This includes the ROM, Kernel and super user fix
Links:
Kernel:http://ice-cream-sandwich-sgs.googlecode.com/files/FuguModICS_GT-I9000_update.zip
ROM:http://ice-cream-sandwich-sgs.googlecode.com/files/ICS_4.0.1_r1-Beta1-i9000.zip
Super User:http://ice-cream-sandwich-sgs.googlecode.com/files/Superuser-3.0.6-efgh-signed.zip
3. Boot to recovery and do factory reset, wipe cache and davlik cache
4. Install the Kernel first and reboot now
5. Boot into recovery factory reset and wipe cache and Davlik and Install the ROM then reboot now
6 Boot back to recovery and install the Kernel again with out the wipe
7. If after reboot you do not have root then boot to recovery and flash super user fix
8. reboot and it should be working at least it was for me
It seems to me that you are missing the first flash of the kernel before the ROM. It sets up the file system from what I gather
Note: If needed flash the kernel and rom then kernel again with all the wipes as mentioned above.
I know there are allot of folks having issues getting it to run. Not too sure if it was the way I installed MIUI that might have made the difference.
My battery is charging now so I can calibrate it and see how it goes after that (it drained pretty quick today) lol.
I hope you can get it going cause it truly is awesome
Still not working:
Can not charge with the phone off
Google TTS stops working
Phone will not vibrate for SMS or email when in silent mode
BLN stays on for notifications until the phone is taken out of sleep (can be turned off)
Compass is why off (have not attempted to calibrate yet though)
11 MB left in the system partition (not much but I do not think there will be many changes there)
Video play back is choppy and some will not play
Bucky
regarding the black screen:
- had that too... I let it sit on the black screen for 2-3 minutes and then it went to the boot screen animation (a multi-coloured )...that for a few minutes...then finally booted.
How i got it working:
a) Started on MIUI...booted into clockwork
b) Backup
c) Wipe data / factory reset and cache and dalvik cache
d) Install rom and then kernel
e) Restart
f) Install rom and then kernel
g) Restart and wait very patiently for a little while
h) Once it all works, can reboot into clockwork and install superuser
Good luck! I really think the rom is nearly stable enough for daily use...
-------
Also have the no vibrate on silent... haven't tried the other stuff yet.
Oh and TTS hasn't crashed on this version yet for me...
Astrid glitches a little to a lot.
Changing from google tts to picco tts solves the problem there. As for the other stuff it is all reported as known.
I am using as a daily on my phone and no issues with general use. Still testing battery and that seems to be a bit of an issue with regard to Android OS as usual
Sent from my GT-I9000 using XDA App
So to install this ROM I would just have to install it as per totallydubbed's instructions? I don't want to flash miui if I don't have to to try this out.
Sent from my GT-I9000 (T959 mod) using XDA App
The Official OTA 4.0.3 ICS update broke auto rotation. The rest of the thing is running smooth as butter, but no auto rotation and the switch isn't doing anything.
Anyone know of a fix to this? I had this prob with the leak but after rooting and reinstall leak from scratch it cured itself. This one isn't doing that.
Is there an app to set the orientation of the screen manually that i can use in the interim??
------------------------------------------
400+ Views later, i think quite a few people have this issue and are trying to find a solution to this.
So far, thank you networkdawg for your app suggestion for manually rotating the screen, however that is a paid for app with a few too many options for my need. I'm currently using Mantano Reader Free to rotate my screen.
https://play.google.com/store/apps/details?id=nl.fameit.rotate
------------------------------------------
Before i accidentally upgraded to the ICS leak, i had my old HC bootloader and was running Lightspeed flawlessly.
Does anyone know of a way to downgrade the bootloader back to HC so i can run a custom bootloader?
OR
a custom bootloader for ICS?
------------------------------------------
Ok so in the end i used jazzyjames' tutorial and blasted HC + HC Bootloader back onto my tab (accelerometer now working once more), rooted, ran Acer Recovery Installer and loaded Light Speed ICS once more.
Everything is working swimmingly. No issues and i got ICS running like a champ.
When the hardworking devs in the dev section have streamlined the ICS bootloader unlocker and installing of a custom recovery a little further, i may try the ICS bootloader once more. But for now, to just have a functional tab, im sticking with the old stuff a little longer.
Thanks Civato, Blackthund3r and jazzyjames for their excellent tools and tutorials. I could not have done it without their help.
------------------------------------------
Update May 08 2012
Did something new, reverted back to stock 3.2.1 (the Gen 2 that was used in Jazzy's revert tutorial), did an OTA upgrade to ICS Official. On first run everything worked.
The minute i rebooted, the accelerometer stopped working.
Followed Civato's tutorial down to the letter, got the custom ICS bootloader working with recovery. Ran like a charm.
Installed a custom ROM (Lightspeed), accelerometer was still not working.
MY TAKEAWAY ---- The accelerometer issues is not a problem with ICS itself, but related to the new chipset firmware and bootloader included with the ICS update. I could be wrong here.
Anyone have any other insights into this?
Back to HC bootloader once more (accelerometer working again) no dice with ICS bootloader :S
I'm not aware of any apps that will switch orientations, only lock it.
Have you tried switching the lock to off then rebooting to see if that resets it?
I have noticed the orientation check isn't as sensitive as it used to be so sometimes I have to wait a few extra seconds or orient the tablet a little more [than usual] to get it to switch over. But it does work.
I have the rotation problem also. As a workaround, I installed this and it works great, although manually.
https://play.google.com/store/apps/details?id=nl.fameit.rotate
veer01_42 I'd be interested in your review of that app if you use it and/or pay for it.
I have the same issue. I have a couple apps that are orientation locked and I can use them to rotate but it's very annoying. Hope this gets fixed soon
anyone try a factory reset to see if that fixed it
A factory reset fixed it for me
Sent from my PC36100 using XDA
Been factory resetting this thing all night, no beans at all.
With the 4.0.3 leak, after one reset it worked for me, but i never got it to repeat again. So don't go factory resetting your tab in a hurry if you know whats good for you, especially if your rotation is working.
Good app, lots of options, but for what i want, this app is too much and it puts an icon next to the clock for quick access, but you cant preset the orientations there. There are only three, locked, auto and whatever you have it in now.
To get to the other options, tap the notification and it brings up a menu with all the other orientations (over 10 of them) its too much for me. But its an extremely powerful app.
Not worth the money as a workaround to a stupid accelerometer.
Encountered the same issue. I was in Portrait mode, playing Draw Something, and suddenly it just rebooted and went into Landscape mode. After a factory reset, it is not fixed. Not sure where to go, but this is highly disappointing for a tablet I paid close to $500 for...
Try wipe cache, it works for me. All said methods in the forum doesn't work for my tablet though.
qpmzal said:
Try wipe cache, it works for me. All said methods in the forum doesn't work for my tablet though.
Click to expand...
Click to collapse
What cache?
Do you mean Pwr Button + Volume Up while toggling screen lock switch?
Or is it something else?
On some a500 that were rooted and accepted the ics ota, a few things got broken during the upgrade. Flash a stock rooted ice rom, but before you do go into recovery and and select backup an restore,click on toggle backup of internal storage. Then you should see enabled on the screen. Then do full reset in mounts and storage plus your normal wipe. This will fully format everything on your tab but sd . When you reflash the new ics rom everything should work fine.
You miss 100% of the shots you don't take....... ..Wayne Gretzky.......
Flash a stock rooted ice rom
Click to expand...
Click to collapse
You mean the 4.0.3 Leak, install that and then use the one click root tool available in the forum?
but before you do go into recovery and and select backup an restore,click on toggle backup of internal storage.
Click to expand...
Click to collapse
Are you talking about Installing the V3 ICS recovery or the original honeycomb?
Then you should see enabled on the screen. Then do full reset in mounts and storage plus your normal wipe. This will fully format everything on your tab but sd . When you reflash the new ics rom everything should work fine.
Click to expand...
Click to collapse
This is in the ICS V3 custom bootloader/recovery right?
variations on problem for different versions
More pieces to the puzzle.
I just downloaded and installed Acer_AV041_A500_1.041.00_WW_CUS1 (very close to stock OTA, but rooted) from XDA and applied it over the stock OTA I had received from Acer directly, Acer_AV041_A500_RV05RC01_PA_CUS1.
Under Acer_AV041_A500_1.041.00_WW_CUS1 screen rotation (and the error 26's) would not clear. I could not get the rotation to work at all, even with multiple reboots, and hard (pinhole) resets.
I restored to Acer_AV041_A500_RV05RC01_PA_CUS1 and rotation is back to it's unstable self, but at least a pinhole reset will clear it.
Installation
https://github.com/LegacyHuawei/local_manifests/wiki/Installation
Bugs
https://github.com/LegacyHuawei/local_manifests/wiki/Status
Downloads
https://basketbuild.com/devs/LegacyHuawei
Changelog
https://github.com/LegacyHuawei/local_manifests/wiki/CM11.0-changelog
If you have any bugs to report, open new issue at https://github.com/LegacyHuawei/local_manifests/issues
Readme
Use the standard Torch app wherever possible, it only enables flashlight. Other apps from Play Store are designed to use the camera interface, which means camera will use additional power.
For more RAM: Settings->Performance->Memory management.
Do not enable KSM, as video encoder/decoder stops working.
HuaweiSettings
Charge current - allows you to set custom charging current. While this actually limits the current input, it effectively decreases or increases the available current transferred to the battery. This is useful in multiple ways:
Slower, but more effective charging. Your battery will last longer.
Faster charging when connected to USB. For example, USB charging is limited to 500mA, but newer PCs allow drawing up to 800mA or even more. This can be configured via the setting.
Manual override of non-standard charger allowing to draw more than 500mA.
Magnetic sensor calibration - lets you delete previous calibration information. This is useful to recalibrate the compass (when it's inaccurate). Just tap the item & then open any compass up to recalibrate your sensor.
If the phone reboots unexpectedly, crash log is found at /data/dontpanic .
To report bugs, use this app: https://play.google.com/store/apps/details?id=com.tortel.syslog
Thank you, i'll try
wow, downloaded...
Many thanks, good job!
after installing cm11 and gapps, the phone always reboot to recovery
ggunzio said:
after installing cm11 and gapps, the phone always reboot to recovery
Click to expand...
Click to collapse
Did you do a factory reset before?
And does it show the cm logo or just boot to recovery?
Sent from my IDEOS X5 using Tapatalk
Blefish said:
Did you do a factory reset before?
And does it show the cm logo or just boot to recovery?
Sent from my IDEOS X5 using Tapatalk
Click to expand...
Click to collapse
before installing the rom, i've wiped everything, data, cache, system and dalvkit cache, reboot recovery. After installed the rom, and right after, installed the gapps. Then, in recovery, reboot system and after it show the huawei logo, it enters recovery without showing the CM logo.
EDIT: i will install ble_part stock, and them install again the B518, repartition again and try to install CM again.
Booted and installed just fine after doing Blepart and using your recovery. It's slow as molasses, probably in great part due to the fact that the display glitches are still there, but it certainly works, and it's as much KitKat as my Moto G. Something worth mentioning, your recovery has some sort (the same?) of display glitch as well in which the screen only seems to update after a couple of presses of the volume button, not immediately.
ROM and GAPPS, everything works fine.
No glitches for me.
Great job, thanks!
faekplastik3s said:
Booted and installed just fine after doing Blepart and using your recovery. It's slow as molasses, probably in great part due to the fact that the display glitches are still there, but it certainly works, and it's as much KitKat as my Moto G. Something worth mentioning, your recovery has some sort (the same?) of display glitch as well in which the screen only seems to update after a couple of presses of the volume button, not immediately.
Click to expand...
Click to collapse
Thanks.
I don't have any devices to compare it with so it feels "fast" to me. Its great to know the recovery suffers same display bugs, it confirms that its in fact kernel side problem. Though, kernel side does not have BLT enabled, which I thought would be the problem. I'll debug the registers, and see if I can find something odd. It could also be a clock hz issue, it was changed in 3.4.
Sent from my IDEOS X5 using Tapatalk
Blefish said:
Thanks.
I don't have any devices to compare it with so it feels "fast" to me. Its great to know the recovery suffers same display bugs, it confirms that its in fact kernel side problem. Though, kernel side does not have BLT enabled, which I thought would be the problem. I'll debug the registers, and see if I can find something odd. It could also be a clock hz issue, it was changed in 3.4.
Sent from my IDEOS X5 using Tapatalk
Click to expand...
Click to collapse
Well, it stutters a lot, and it's not nearly as smooth as something like Aurora or even stock Huawei ROMs, but I'm sure it's related to the display issues or another issue like that because even scrolling through the Settings app or the little animation in the notification drawer that flips into the shortcuts stutters like hell and drags around, which shouldn't be an issue for this device and wasn't a problem with other ROMs, and overclocking and other user-level optimizations do nothing to alleviate it.
I did also notice black screens when waking the device from lockscreen (digitizer still works) almost every time, requiring multiple attempts until the display finally wakes. I know you squashed this one multiple times, but here it is again.
It's a miracle for this to happen to begin with, so I can't help to be amazed seeing KitKat on this device. Thank YOU so much, Blefish.
do i need to have my phone rooted?
faekplastik3s said:
It's a miracle for this to happen to begin with, so I can't help to be amazed seeing KitKat on this device. Thank YOU so much, Blefish.
Click to expand...
Click to collapse
This. If some months ago anyone told me I'd be installing 4.4 on this device I'd tell them they were crazy.
Thanks for your amazing work, Blefish
Here its works as it should be, you are awesome blefish
Sent from my SM-T210 with rocketTab 2.1 + MK1 kernel using tapatalk v4
Finally i could get it to boot.
probably i broke something, i've installed the oficial rom and then, with 5.5.0.4 recovery wiped everything. Next installed the blepart, new recovery and its working
Good job sir
Thank you!
faekplastik3s said:
I did also notice black screens when waking the device from lockscreen (digitizer still works) almost every time, requiring multiple attempts until the display finally wakes. I know you squashed this one multiple times, but here it is again.
Click to expand...
Click to collapse
Yes, I have waking problems too.
Install everything (partition, 6 recovery, cm11 rom and gapps) and works pretty well so far.
Fantastico. :good::highfive:
lemene said:
Install everything (partition, 6 recovery, cm11 rom and gapps) and works pretty well so far.
Fantastico. :good::highfive:
Click to expand...
Click to collapse
is anyone having problems to connect to wifi networks? i cant connect
EDIT: i guess that is a problem with the wireless definition of the rom, im thinking this, because i can connect to open networks, but when i change the segurity of the wlan to wpa or wpa2, i can't connect to it.
Could you look at this @Blefish?
Im not sure if its a bug or not, maybe something is broken in wpa.supplicant
[]
I have flashed BlePart recovery, i have rebooted the recovery and i have flashed blepart 2.2 then i have flashed CVM Version 6.0.4.6. The phone rebooted and now i cant open the phone or recovery. I tried to install offical 2.3 from sd card but i coudn't. How can i recover my phone?
Hey guys,
I have a Galaxy S4 (i9500). I installed Omega ROM v22 on it and everything went smoothly, Wifi & BT working perfectly.
After a few hours of using the device (nothing special at all, texts and stuff like that) - I noticed my wifi isn't working and by not working I mean that I click the wi-fi button and it changes from gray to the mid-state between gray to green for around 20 seconds before it goes back to green ago.
If I open the menu to see my networks it just says "Enabling" without any networks there.
I had to drive somewhere so I went to my car and tried to enable Bluetooth, and same thing happens there - Bluetooth will not turn on and will stay stuck on mid-state between gray and green for a while and go back to green.
I flashed omega rom v22 again and the problem was gone, or so I thought. I went back to the car for another drive and realized the bluetooth issue is back - and when I got home I realized the wifi issue is back as well.
I figured I need to reset everything so I tried the following:
Full wipe (including dalvik and even including "internal SD card") and then flashing stock rom (from the official website, stock rom of my country).
The issue was back after a few hours. I do not have BT or Wifi access. Yesterday Wifi suddenly started working for a few hours but then it stopped working again.
I really need help! I have no idea what to do with this issue!
Well rule number one when you have problems after flashing without wipe.
1. perform a full wipe and see if the problem persists.
Lennyz1988 said:
Well rule number one when you have problems after flashing without wipe.
1. perform a full wipe and see if the problem persists.
Click to expand...
Click to collapse
Tried that, no luck.
What else would you try?
In some places when people had problems with Wi-Fi they said to flash a different kernel but I don't see why I would have this specific issue with Omega Rom and why the default kernel with it wont work well?
Maybe this could be a root issue? My root works fine but I have this weird gut feeling like this is some permissions thing that's going on.
I'm trying to think why it would work right after the wipe but then stop working shortly after.
Another symptom: It randomly started working for a few minutes and then stopped again (around three hours ago).
Any idea what's going on?
Well, if you fully wiped and didn't restore any apps and settings then it can be two other things.
Or it's a bug in the rom or a hardware failure in your phone.
I would suggest trying a different rom first. Do not restore anything, not even your google account.
wi-fi fix?
Do you actually have an i9505? or is it a canadian or att version? if its the latter sometimes the devs offer some wifi-fixes, also try a different kernel. otherwise it could be that your radio/modem are not compatible with the version of the ROM you are flashing.
Tried arrow ROM and this issue doesn't seem to happen in this rom. Hope it stays like that...
morhsn said:
Tried arrow ROM and this issue doesn't seem to happen in this rom. Hope it stays like that...
Click to expand...
Click to collapse
Sadly, it did happen with this rom, after just a few hours.
I'm now using stock rom and still suffering from the issue.
Does anyone have ANY idea what I can do to fix this?
Thanks in advance!