Related
I'm new to rooting, installed MIUI and loving it so far. My hw is 003. Everything is working so far but i have a few questions -
1. Do you use the default kernel or replaced it? I've seen screen tearing a few times and battery life could be better so I'm thinking of trying a different one. Read a number of threads in the root section.
2. Did you replace the lockscreen? I'm asking because I love its look, but if you enable security there's no slide to unlock and its not so useful.
3. How often do you update the MIUI build - I read it comes out every Fri, do they have major changes?
#3, the official build is done on friday, porting to individual phones is on/around sunday
1. I'm on the 1.1.28 build and using the kernel that came with it. Savage 1.6. It is by far the best kernel I have ever had the pleasure of flashing and I have no reason to use anything else. When I update to a newer build, I will most likely flash this kernel over it.
2. Still using stock lockscreen. I agree that the pattern lock could have been implemented better.
3. What elegantai said.
2 more issues I noticed -
1. Back button is now killing apps. The only way to fix it is turn off 'long press kills app', reboot, and turn it back on.
2. When in a call the notification bar cannot be dragged down.
Both are minor issues, just wondering if they are common.
1. That's not an issue at all, it's supposed to do that, and I think that's an awesome feature. If you just tap back it won't kill the app, and you can set how long the long press needs to be.
2. Never really noticed that before. Can you pull it down with a Sense ROM? It's been so long I can't remember. You can always hit the home key while in a call and pull the bar down from there.
ECrispy said:
2 more issues I noticed -
1. Back button is now killing apps. The only way to fix it is turn off 'long press kills app', reboot, and turn it back on.
2. When in a call the notification bar cannot be dragged down.
Both are minor issues, just wondering if they are common.
Click to expand...
Click to collapse
I actually have the same problem with the app killing. Great feature yes but it always kills the app regardless of how long or short I press it lol. Changing the duration didnt seem to help.
Sent from my PC36100 using XDA App
_MetalHead_ said:
1. That's not an issue at all, it's supposed to do that, and I think that's an awesome feature. If you just tap back it won't kill the app, and you can set how long the long press needs to be.
.
Click to expand...
Click to collapse
It kills the app even when I just tap back, that's the bug. When its working yes, it only kills after a 2s tap.
ECrispy said:
It kills the app even when I just tap back, that's the bug. When its working yes, it only kills after a 2s tap.
Click to expand...
Click to collapse
That's odd, it works perfectly for me. What MIUI build are you on?
_MetalHead_ said:
That's odd, it works perfectly for me. What MIUI build are you on?
Click to expand...
Click to collapse
Latest - 1.2.11
I dunno, maybe it's a bug with that build.
from my observations the back tap close program happens only when a program is lagging. if you dont have too many things going on at once it shouldnt be a problem
yeahh it is a problem occasionally for me. I normally skip and flash every other week. This week im gonna flash again though, because it seems slow.
I installed cm9 after using cm7 and cant get the four buttons on the phone to light up. They are accessible but not illuminated. has anyone else encountered this problem.
Also I was wondering if the Cm7 uses more battery than cm9
You have to use auto brightness.
cm9 illumination
If you mean display auto brightness ok but when I'm outside I can't see the screen...guess ibhave to toggle back and forth. I had switched back to cm7. In your opinion is 9 worth changing to. It seems like in 7 everything is working pretty well.
Thank you for the reply
pmpic said:
I installed cm9 after using cm7 and cant get the four buttons on the phone to light up. They are accessible but not illuminated. has anyone else encountered this problem.
Also I was wondering if the Cm7 uses more battery than cm9
Click to expand...
Click to collapse
Toggling auto brightness on and off solves it. Just tinker with it..
Sent from my Incredible 2 using xda premium
cm9 illumination
Thank you....I appreciate it
Menu keys...
Ive been using the dinc2 since last July and I got used to the buttons to the point that I noticed they didn't light up, but until I saw this post, I never considered it a "problem". Since I knew where they were and didn't need to see them to use them. If they ever do "fix" this issue I hope they allow for a settings option to keep them turned off. I actually enjoy them off, in my mind its just one more security feature. I know when my wife tries to use my phone she needs to see them, and since recently rooting to CM9 I don't want her bricking my phone. Because of the unlit buttons she has stopped using my phone (she uses some cheap AT&T phone, refuses to switch to Verizon). Just throwing my opinion in the mix. Thanks for the post as well I wasn't sure it was intentional or not.
atomwes said:
Ive been using the dinc2 since last July and I got used to the buttons to the point that I noticed they didn't light up, but until I saw this post, I never considered it a "problem". Since I knew where they were and didn't need to see them to use them. If they ever do "fix" this issue I hope they allow for a settings option to keep them turned off. I actually enjoy them off, in my mind its just one more security feature. I know when my wife tries to use my phone she needs to see them, and since recently rooting to CM9 I don't want her bricking my phone. Because of the unlit buttons she has stopped using my phone (she uses some cheap AT&T phone, refuses to switch to Verizon). Just throwing my opinion in the mix. Thanks for the post as well I wasn't sure it was intentional or not.
Click to expand...
Click to collapse
I believe in the advanced brightness settings under CMSettings you can do just that. Whenever I run a CM rom, I always go to the brightness settings under edit Other Levels and set all the softkey values on the far right column to 255 so they're always the same brightness and look nice. I like the sheen they have, but I can only see it when they're close to full brightness.
If you did the opposite, set all the values to 0 and then click Save and Apply Values at the top of that screen, they should, theoretically, never turn on.
Thank you ....as I am new to a rooted phone and this forum I didn't know those adjustments were available...learn something new everyday ......
Does cm9 drain the battery alot quicker or is it unnoticeable
pmpic said:
Thank you ....as I am new to a rooted phone and this forum I didn't know those adjustments were available...learn something new everyday ......
Does cm9 drain the battery alot quicker or is it unnoticeable
Click to expand...
Click to collapse
Unfortunately, I can't answer that question for you, as my phone doesn't like our ICS builds. Until we get a leaked official kernel and some source, I'm SOL.
RegnierD said:
I believe in the advanced brightness settings under CMSettings you can do just that. Whenever I run a CM rom, I always go to the brightness settings under edit Other Levels and set all the softkey values on the far right column to 255 so they're always the same brightness and look nice. I like the sheen they have, but I can only see it when they're close to full brightness.
If you did the opposite, set all the values to 0 and then click Save and Apply Values at the top of that screen, they should, theoretically, never turn on.
Click to expand...
Click to collapse
Where exactly are these settings? Running CM7 with the same problem as the OP and can't find it anywhere. Edit: found the settings and putting them all at 255 didn't do anything. Any other ideas?
Hey everyone, I've been having a little bug that I noticed after I received the 4.0.4 update. I don't know what I exactly do to cause this but my nexus takes random screenshots whenever I press my power button to unlock my phone. I have the pattern lock that I use and when I hit power it randomly vibrates and when I go check my gallery it shows that I just took a screenshot. At times, when my battery is low it seems to randomly vibrate again and take a screen shot and gives me the prompt screen for which app I'd like to use to complete the action... No, I don't press the volume down key when this happens and no I don't have any screenshot apps. I'm stock, non rooted... Anyone else have this issue?
Stuck volume key?
adrynalyne said:
Stuck volume key?
Click to expand...
Click to collapse
I'm having doubts that it would be that...sometimes it does it even when I don't touch the power off key..
I have this same problem. I decided to find out what was going on when it asks what app to use, so I selected google drive. It uploaded the screenshot and a bug report to google drive. The bug report is a 3mb text file. I can't upload it here.
Same here with 4.0.4 IMM76I rooted,bootloader unlocked
Sent from my Galaxy Nexus using XDA
Do any of you guys run a rom that gives the ability to use the volume rocker to take screenshots? Have you tried reflashing your roms since you updated?
Sent from my Galaxy Nexus using Tapatalk 2
xterrain15 said:
I have this same problem. I decided to find out what was going on when it asks what app to use, so I selected google drive. It uploaded the screenshot and a bug report to google drive. The bug report is a 3mb text file. I can't upload it here.
Click to expand...
Click to collapse
Upload it somewhere and update your post with the link.
sent from my i9250
Posting the bug report
docs.google.com/open?id=0BxAJdhmCAyirSDU2UEU5dTRyQzg
There it is.
I am about to try flashing the 4.0.4 update again, as I just downloaded the zip of it.
Screenshots are Volume Down + Power. Bug Reports with screenshots are Both Volume Keys + Power. Do you have a case on? I've seen many people having these issues that were due to a tight fitting case.
Case
I do have a case on, but I know that's not the issue, as the power button is not covered, and this often occurs without me being anywhere near the power button. It can happen in the middle of typing out a text message. A prompt appears asking what application I'd like to complete this action with, and if I check the gallery later, there will be a new screenshot of my messaging app.
Slightly tangential - but is there any ROM or setting that will allow you to use a softkey to take screenshots? Or do I need to just search out an app that'll do so?
I find it really awkward (at least with my case on) to take screenshots and wouldn't mind the ability to do it with a softkey instead.
ceribaen said:
Slightly tangential - but is there any ROM or setting that will allow you to use a softkey to take screenshots? Or do I need to just search out an app that'll do so?
I find it really awkward (at least with my case on) to take screenshots and wouldn't mind the ability to do it with a softkey instead.
Click to expand...
Click to collapse
AOKP allows you to set up any functions/icons to softkeys
Sent from my Galaxy Nexus using xda premium
nirco68 said:
Same here with 4.0.4 IMM76I rooted,bootloader unlocked
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
I have the exact same problem! No clue what's causing this. I'm on AOKP M5 on rooted Galaxy Nexus. I can't find any setting to disable bug report creation, nor can I find anything about bug reports in the settings at all. I really hope someone can figure out what's causing these spontaneous bug reports (plus screenshots) to be generated.
Same issue
I just received my 4.0.4 update on Galaxy Nexus, and I am having the same issue. It randomly takes a snapshot of the lock screen and generates a bug report. Have they added some new hardkey combination that is too easy to trigger? I do have a case on, but I have always had it on, way before the update.
This is a manual bug report triggered by pressing both volume keys and the power button at the same time. It will vibrate once when you do it and then it takes a good minute or two for it to compile the report. The phone will then vibrate 3 times quickly when the report is ready, but only if the phone is awake and unlocked. So, for example, if you hit the power button to check the time and happen to press all three buttons or your TPU case (just an example) is holding down your volume buttons, then it will trigger then. You won't actually see the results until the next time you unlock the device. They are addressed to your default email address unless your ROM developer adds an email to them. Obviously being stock this would not be the case.
If you want to get rid of this feature, go to /system/bin and rename bugmailer.sh to bugmailer.sh.bak or delete it. Then reboot and no more bugmailer.
Source: http://rootzwiki.com/index.php?/topic/18671-Disable-bug-report-error-messaging?#entry488123
chandradithya said:
This is a manual bug report triggered by pressing both volume keys and the power button at the same time. It will vibrate once when you do it and then it takes a good minute or two for it to compile the report. The phone will then vibrate 3 times quickly when the report is ready, but only if the phone is awake and unlocked. So, for example, if you hit the power button to check the time and happen to press all three buttons or your TPU case (just an example) is holding down your volume buttons, then it will trigger then. You won't actually see the results until the next time you unlock the device. They are addressed to your default email address unless your ROM developer adds an email to them. Obviously being stock this would not be the case.
If you want to get rid of this feature, go to /system/bin and rename bugmailer.sh to bugmailer.sh.bak or delete it. Then reboot and no more bugmailer.
Click to expand...
Click to collapse
While I appreciate the fact that you are helping out, please do not take my responses from another forum and paste them here verbatim as your own.
Source: http://rootzwiki.com/index.php?/topic/18671-Disable-bug-report-error-messaging?#entry488123
Also of note for those having the issue on the 4.0.4 update, disabling USB debugging should now also disable the bugmailer.
Sent from my brain using human to phone transport technology.
ABQNM said:
While I appreciate the fact that you are helping out, please do not take my responses from another forum and paste them here verbatim as your own.
Source: http://rootzwiki.com/index.php?/topic/18671-Disable-bug-report-error-messaging?#entry488123
Also of note for those having the issue on the 4.0.4 update, disabling USB debugging should now also disable the bugmailer.
Sent from my brain using human to phone transport technology.
Click to expand...
Click to collapse
No offence to you. Seriously.
was annoyed with this issue, google searched it , opened a lot of tabs, found many posts never had answers,
I agree it was copy paste, sorry for not mentioning the source.
I edited them and linked it to your post on rootzwiki,
I was in a hurry then and rushed up and pasted on the threads where there was no proper answers.
I have the same problem
Hello guys.
I have the same problem. I have the Android 4.2 original from Google. I have the issue from Android 4.1 and I don't know what is the problem.
Drakonworld said:
Hello guys.
I have the same problem. I have the Android 4.2 original from Google. I have the issue from Android 4.1 and I don't know what is the problem.
Click to expand...
Click to collapse
See my full explanation here http://rootzwiki.com/index.php?/topic/18671-Disable-bug-report-error-messaging?#entry488123 (last post on the page). Simple answer, something is pressing all three buttons at once, be it a case or whatever. Either disable usb debugging to turn it off or see my link for instructions to disable just the bugmailer.
Sent from my brain using human to phone transport technology.
This is not Officially supported by CyanogenMod but I have brought this to you for your flashing pleasure.
THIS IS AN ALPHA BUILD AND WILL HAVE SOME ISSUES AS WITH THE OTHER AOSP ROMS!
THIS IS UNOFFICIAL CM9 FOR THE I927
KERNEL BUILT FROM OFFICIAL ICS KERNEL SOURCE
ROM BUILT WITH MY GLIDE DEVICE TREE
THIS IS COMPILED FROM SOURCE FOR THE GLIDE ON MY LINUX MACHINE, THIS IS NOT A PORT!
CM SOURCE HERE-CM-Github
Kernel source here-Kernel github
TeamGlide Github Here-TeamGlide Github
known issues:
wifi may be janky
keyboard may or may not work properly
autorotation broke when using physical keyboard.
APN may not be present on first boot. Enter new APN if so..
Any other issues please report here.
INSTALLATION:
WIPE DATA
WIPE CACHE
WIPE DALVIK CACHE
FORMAT SYSTEM
FORMAT DATA
FORMAT CACHE
FLASH ROM
FLASH GAPPS
ENJOY!
Download- CM-9 UNOFFICIAL-Glide
CM-9-Glide-Alpha-2
ICS Google Gapps
CM9-Glide-Alpha-3
great! this makes the glide the best keyboard phone for europe
many thanks for your effort!
Mine!
Well done !
My wife took her Glide to work!!! NOOOOO!!! oh well. Guess we'll have to wait till tonight
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Anyone who flashes, do some tests with wifi please. My Glide is a wifi only device so I definitely need that working good before I can flash. This is great dman, thanks so much for showing our little device and community some love!
Very nice! If I didn't have to depend on my phone I'd have this sucker flashed in a heartbeat to put it through its rigors. Been looking forward to a CM port for a while.
Here's some money, go see a star war.
downloading now, will be back with a logcat if anything unexpected happens.
Tyfighter said:
Here's some money, go see a star war.
downloading now, will be back with a logcat if anything unexpected happens.
Click to expand...
Click to collapse
Thanks bro.. that's why I love the glide community.. you guys are so appreciative.. and I appreciate you guys..
Sent from my SGH-I897 using xda premium
Working on grabbing a logcat, don't have my adb pc on hand, so I have to use an app for now and that's proving problematic.
But for now:
-everything boots up fine, but on both my two installs it says that my sd card is damaged (which a restore to my previous rom says its not).
-The power button is only functional when you hold it down to power off; no locking, no power menu.
-I tried adding an APN, but it didn't save (only tried once, as said before the hardware keyboard isn't functional and pressing a key on the soft keyboard caused it to "perma-vibrate". worried about potential damage from the extended vibration, I didn't risk punching in the APN again.
And I know this isn't useful without a logcat but upon opening the camera I got a 'could not connect to camera' error
edit: just flipped through the other thread and saw the suggestion to try a different kernel. going to try that now and see if that resolves anything
Further edit: using the Lite Kernel, I was able to get wifi working. Logcats are incoming. Now, from what I've been able to tell, its not just the keyboard giving the perma-vibrate, but certain other events are doing it too; moving stuff in the drawer or homescreen and unlocking the phone. Further weirdness is that it only happens about 75% of the time when moving icons.
Its amazing that i knew dman would make this phone amazing still has bugs but ofcourse it will good job
Sent from my SGH-I927 using xda premium
I'm making a new build.. think I fixed the keyboard issue... and power menu
Sent from my SGH-I897 using xda premium
Here is what I have after playing around with the ROM for about an hour and doing several power on/off
- No problems with the flashing or first boot
- Vibration does not seem to stop. Like another posted noted this is not limited to the keyboard but appears to occur for the unlock screen, long press, etc. I ended up having to pull the battery each time this occurred and went into the system settings and disabled everything I could find that uses vibration.
- No cellular signal. I tried to add an APN but it did not get saved onto the list. WiFi and bluetooth don't seem to turn on.
- The capactive keys don't light up.
- The physical keyboard does not light up or work.
- I thought that the power button turned the screen on/off at first... But it doesn't seem to anymore now that I have disabled the lock screen (to remove the vibration which occurs when unlocking). Now I'm not certain if the power button worked in the first place or not. Currently with the lock screen disabled the power button doesn't seem to do anything. If the screen turns off the only way for me to turn it back on is to open the slider.
- Screen rotation did not work during the initial Google account setup. I opened the slider and it went into landscape mode. Then I closed the slider and the screen remained in landscape mode. This was all occurring while the phone was continually vibrating so I'm not sure if this is related. Right now the screen rotation works fine after having turned off all the features that use vibration.
- Attempting to use the camera get a message of "Can't connect to the camera".
- Surprisingly the Torch app works and turns on the LED. However, shortly afterwards the phone froze requiring me to pull the battery.
- There are no sounds played when I go into system settings and try to change the notifications or ringtones.
Sorry if the list is a bit long. I'm not sure what is important and what's not but I wanted to post my experience hoping to help.
Thanks for doing this for our community. I've sent you a small donation which I know is nowhere near the value of your efforts... But please enjoy a few beers on me.
Ok, so here's a logcat of the second boot after installing. Perma-vibrate starts when unlocking and lasts a few seconds. I then tried to restore my APNs to trigger an attempt to access the storage.
On the first boot from this install, I did some poking around in Antek and found that not only is the external SD not showing up, but neither are any non-root directories on the internal.
google docs link because XDA was being finicky about the file/character size
https://docs.google.com/open?id=0B7ZF6qbivGeNeE1nb3ZiZERTTjA
edit: forgot to mention before that the capacitive keys light up on a different kernel, and also (I didn't even think to test sound) but some error info on that looks like its available in the logcat. Also, it should be noted that the perma-vibrate can be stopped short of a battery pull by clicking on the app drawer icon. Possibly there's another way, but that's the one I found first so that's how I've been doing it.
The log at won't load up.. says its not available
Sent from my SGH-I897 using xda premium
Strange, try this. Don't know why I didn't think to zip it before.
Here is a new test build.. Please report if any issues are fixed
CM9-Glide Alpha-2
The keyboard is working a little better now. The soft keyboard doesn't pop up when the slide is out and most of the buttons work. Alt, backspace, question mark, sym, .com, microphone, search, home and the middle dpad button are nonfunctional.
Power button and power menu are working. In fact, I was just able to use it to successfully boot to recovery.
Tyfighter said:
The keyboard is working a little better now. The soft keyboard doesn't pop up when the slide is out and most of the buttons work. Alt, backspace, question mark, sym, .com, microphone, search, home and the middle dpad button are nonfunctional.
Power button and power menu are working. In fact, I was just able to use it to successfully boot to recovery.
Click to expand...
Click to collapse
Nice.. we have progress.. made some more changes to see if we can get some more issues fixed
Sent from my SGH-I897 using xda premium
Alpha-2 build in OP for testing
Hi all,
After my Wildfire running CM7 being so unresponsive I've almost had the urge to throw it against a wall at times, last night I snapped and installed AOKP Lite v5. Wow. ICS yet amazingly fast.
All was fine and dandy until this morning when for some reason long pressing the power button (for anything more than half a second) results in an instant reboot - but not a full reboot - I don't get the HTC logo. What should be happening is that the power menu displays, but for some reason it's no longer doing this.
Some actions that may have contributed to the problem that I have reversed:
- I enabled trackballwake via the terminal (I've now reverted it, no effect)
- SuperSU updated - this apparently caused problems due to some "pro" features not available. I reverted to factory version, then, installed the CWM Superuser and disabled SuperSU. Playing with different Superuser apps hasn't helped get the power button menu back.
- Enabled USB Fast Charge (then disabled again).
- Enabled then disabled the Power Saver.
- Changed Scaling governor to smartassv2 from performance, for the sake of testing, reverted back to performance.
- Added Screenshot to power menu, later removed.
My guess is that what's actually happening is that the power menu is trying to display and is then catastrophically failing resulting in an instant reload of the ROM. Why this is the case I can't work out.
I'm not finding any reference to such a problem but I thought I'd put it out there in case someone has an idea. It's early enough on that I could just reload everything but I'd rather not have to go through that if I can avoid it seeing as (everything else) is set up how I'd like it. Also, what's to say it might not happen again in the future!
Thanks
@rguk,
I've also experianced this before, as I know it is caused by enabling the power saver options. Its best to let that be.
had to reflash the ROM again to solve it.
Cheers
just disabling power saver solves this issue.
Wasimk32 said:
just disabling power saver solves this issue.
Click to expand...
Click to collapse
not sure, didn't work for me...
Thanks for the quick reply guys. Oh well, re-flash it is then... Turning off the power saver options didn't fix it for me.
Hmmm. Received a call and the screen remained black. Did a quick search and I'm seeing some related stuff, let's hope a re-flash fixes that, too.
@Wasimk32
mate, I just found a guide about soft rebooting, I don't know whether this'll be helpful or not as I'm not a dev.
Thought this could, if it can, help you to solve the soft rebooting issue.
http://forum.xda-developers.com/showthread.php?t=2360936
Cheers
lakshan_456 said:
@Wasimk32
mate, I just found a guide about soft rebooting, I don't know whether this'll be helpful or not as I'm not a dev.
Thought this could, if it can, help you to solve the soft rebooting issue.
http://forum.xda-developers.com/showthread.php?t=2360936
Cheers
Click to expand...
Click to collapse
thanks mate,thats something we call hot reboot.This might not solve this issue but definitely could help me looking in a right place.