Related
My buttons won't work when i press them not exactly sure whats wrong but this began happening within the past few days. I've been running WTSB 3.5 latest update of 2.4 and Olympus Prime both of which use's a chad kernel which i'm not sure may or may not be the source of the problem. Can anyone offer any suggestions?
Selebrity said:
My buttons won't work when i press them not exactly sure whats wrong but this began happening within the past few days. I've been running WTSB 3.5 latest update of 2.4 and Olympus Prime both of which use's a chad kernel which i'm not sure may or may not be the source of the problem. Can anyone offer any suggestions?
Click to expand...
Click to collapse
By LED buttons I'm going to assume you're referring to the 4 capacitive buttons across the bottom, Home, Menu, Back and Search.
Never really heard of any software disabling these buttons, either intentionally or accidently but doesn't mean it couldn't happen!
Quick shorter term and temporary approach: boot into the custom recovery and see if their lights flash or they work at all in the custom recovery. I remember at one point during TWRP development we had the lights flashing on them. Not sure what kinda support ended up but you should be able to get some type of response to at least indicate the hardware is working.
Long but thorough approach:
Since you are running a custom ROM and kernel, I would suggest first reverting back to Stock and wipe /data and /cache.
If everything works on a Stock ROM and kernel, then you know it has something to do with either the custom ROM, custom kernel or a custom setting configuration. From a known working stock configuration, you can customize one piece at a time checking after each customization step to make sure the buttons work.
Ideally, the buttons will break after a specific customization step and you'll be able to narrow it down to that step and approach the appropriate developer with your results who will then be able to dig into their code and look at the issue.
Hope that helps!
I'm having a few problems since rooting my i777. It randomly shuts down while I'm not using it, I think it's the messaging app causing this. I also can no longer get the phone to rotate into landscape mode for anything :/
Anyone know what might be going on?
Did you install any ROMs or just a simple root? Also, there's a setting that can disable rotation so check and see if that's enabled. I have no idea where it is on stock, considering I used it for a good day before I installed a custom ROM. Anyway, if you're still having persistent issues, I suggest just going to SHOstock ROM as it's very very close to stock but it's unbloated and performs better with better battery life.
I did install a custom ROM but I can't for the life of me remember which one it was, I went through some trouble because I was accidentally trying to install i727 stuff, so I just installed an i777 ROM someone linked me.
All settings are set to allow it to rotate. I'll try out SHOstock. Is it a ROM file I install from Clockwork Recovery Mode?
Hi all,
I installed CM7 on my TP a ways back but never really used it and stuck with WebOS. I decided to upgrade to CM9 Alpha2 yesterday and did without any issues. I then got curious about CherryKang and decided what the heck. I was able to install CherryKang but now I am having a few issues:
1. When booting CM is still listed in MoBoot and CherryKang is not. If I select CM, then I get the CM boot screen for a sec and then CherryKang boot screen comes up. Not that big of a deal, just hoping to get it setup right.
2. The Gallery force closes every single time.
3. Occasionally unresponsive when trying to wake it up. I always put it to sleep when I am done by pressing the power button, but I have to reset it to wake it up about 30-40% of the time.
Those are my only issues so far. Other than that I'm diggin' ICS.
1. CherryKang is based on CM9, if you don't like it change the name to cherrykang. Or something that suits you.
2. Reflash?? I had CherryKang before and I had no issues, try gallery++cm from market or play store whatever
3. Reflash?? + maybe wipe everything??
svenerator said:
1. CherryKang is based on CM9, if you don't like it change the name to cherrykang. Or something that suits you.
2. Reflash?? I had CherryKang before and I had no issues, try gallery++cm from market or play store whatever
3. Reflash?? + maybe wipe everything??
Click to expand...
Click to collapse
I tried wiping the cache, dalvik cache from CWM but no luck. Then re-downloaded and reflashed but still no luck. Ended up going back to CM9 Alpha2 and so far has been stable. I've been able to wake it up without issue far....
You may want to try and restall CM9 with the Acmeinstaller2 method. I read that although you can use CWM to go from CM7 to CM9, you can get leftover files/directories that could may or may not cause issues in CM9.
after using Acmeinstaller2 to get to CM9, you can safely use CWM to flash other CM9 roms. Also, before you flash, use classicnerd's moboot uimage and tga cleaner to wipe out previous boot images left by other roms.
Many people just wipe the cache and dalvik caches before flashing, and don't do the factory reset. I always do, because the roms seem to have less issues if I do the factory reset.
I've had a couple of instances in more than one rom where the lock screen doesn't respond (touch screen doesn't work) and I have to reboot, so I just disable the lock screen all together.
Gallery is currently working on my install of cherrykang, but I prefer Quickpic from the market, and usually install it right away.
I believe the boot option issue is because it uses the standard CM kernel, so that's what it boots up. If you flash the Bricked kernel, and entry will appear for that, even though you're using the CherryKang.
I too was getting the problem where it became unresponsive. What seemed to mostly work was setting the minimum clock up to 384mhz. You can use SetCPU from the market, or CPU Master (free in the market -- that's what i used). I had some problems again last night, but overall it seemed to help. His latest version did set the min clock speed to 200-something.
Thanks for all the tips guys. Still running strong with no lockups after going back to the original Alpha2.
I actually tried setting the min CPU higher prior to going back to [email protected] but that didn't work either. I still have my kids TP to install CM9 on so I might try CherryKang on that.
This is a MIUI GB 2.3.xx rom ported from stock ZCPK9(China version) rom with miui patchrom.
---FLASH AT YOUR OWN RISK---
I'm now busy preparing for college entrance exam so I won't (perhaps) continue develop before I get into college
Not working:
GPS(Don't know why)
Not perfect:
Theme
DownloadProviderUI
SideKick
ClockPackage
Default language is Chinese.
App2SD(Cause reboot every time when you switch an App between SD and internal memory but actually it has operated successfully)
Ugly statusbar transparent.
Not proted now(All using stock one):
MIUI Settings
MIUI Camera
MIUI SoundRecorder
MIUI SuperUser
MIUI FileManager
MIUI Browser
MIUI Gallery3D
(And some other MIUI apps)
Features:
All MIUI features except that mentioned above (plus that I forgot and not find).
GUI installer by Aroma.
Optional Ad-hoc patch, Gapps, no keyboard light patch, USA keyboard patch.
Something wonderful:
Press home at lock screen to turn on torch.
Press home + back at same time to take screenshot.
Press menu + volum up to turn background light max(temporary).
Thanks to:
Myself , MIUI team and friends at XDA and Sdapk.
How to install:
1. Make sure you have rj's or Entropy512's installed. This rom does not contain kernel.
2. Download rom and place in your sdcard.
3. Reboot into recovery.
4. Wipe /data as well as anything else if you are first install this rom.IMPORTANT!
5. Choose install zip and this will start Aroma Installer.
6. Choose any patch you like in Aroma Installer and finish install it.
7. You will reboot automatically.
8. Be patient while first boot up.
9. Congratulations!
Screenshots:
Change log:
Code:
MIUI.2.3.xx.Noisyfox.01b
Fixed FC when headset plug in
Add USA keyboard patch
MIUI.2.3.xx.Noisyfox.01a
Fixed Settings Fail After Wipe /data
MIUI.2.3.xx.Noisyfox.01
Initial Release
Download:
https://github.com/Noisyfox/patchrom_GalaxyPlayer5.0/downloads
Develop:
If you are interested in this project, you can get fully source code from here:
https://github.com/Noisyfox/patchrom_GalaxyPlayer5.0
Hey how do we change it back to English in this ROM? And what do you mean by "Theme" is not working perfect? It is working partly or are there any bugs!
Thanks
Rom is perfect for me , but slow .
I have INTL device , which kernel is better for me Rumirand's or your patched kernel?
anil_kilic said:
Rom is perfect for me , but slow .
I have INTL device , which kernel is better for me Rumirand's or your patched kernel?
Click to expand...
Click to collapse
rj's is better.
pmdisawesome said:
Hey how do we change it back to English in this ROM? And what do you mean by "Theme" is not working perfect? It is working partly or are there any bugs!
Thanks
Click to expand...
Click to collapse
It works partly.
This is sweet, good job!!
I followed instructions to the letter. Seemed to flash fine but it is now sitting at the black Samsung screen screen for about 20 minutes. How long has it taken for 1st boot? Tried re-flashing, clearing cache, etc.
change your kernel to rj's kernel and flash again.
rj's kernel says it is for International SGP not US. My SGP is US so I am not sure if this kernel will work.
tsg2513 said:
rj's kernel says it is for International SGP not US. My SGP is US so I am not sure if this kernel will work.
Click to expand...
Click to collapse
Dont install . rj's kernel is for only INTL devices . Sorry i think your device is INTL and replied.
could you make a port for the 4 inch sgp?
I have the same problem as tsg2513, it sits at the Samsung logo and does nothing. I have a USA SGP5.0 and I flashed entropy's kernel right before I flashed the MIUI.
mrjaredbeta said:
I have the same problem as tsg2513, it sits at the Samsung logo and does nothing. I have a USA SGP5.0 and I flashed entropy's kernel right before I flashed the MIUI.
Click to expand...
Click to collapse
figured it out. i have a USA device as well and had the same issue. It was also strange as to why the flashing process only took like 5 seconds....
i flashed rj's kernel (so my buttons stopped working) then i restarted recovery just so the changes get applied. then i proceeded to flash miui. just make sure in the install options you selection USA keyboard patch and the install process should take much longer (that means its working) and bam.
EDIT: ok so the buttons light up but they still don't work. after booting to miui and sat at the homescreen for a minute or two, reboot and flash entropy's kernel.
raishiro said:
figured it out. i have a USA device as well and had the same issue. It was also strange as to why the flashing process only took like 5 seconds....
i flashed rj's kernel (so my buttons stopped working) then i restarted recovery just so the changes get applied. then i proceeded to flash miui. just make sure in the install options you selection USA keyboard patch and the install process should take much longer (that means its working) and bam.
EDIT: ok so the buttons light up but they still don't work. after booting to miui and sat at the homescreen for a minute or two, reboot and flash entropy's kernel.
Click to expand...
Click to collapse
Are you saying that after you re-flashed entropy's kernel the buttons work? Also, have you checked to see if the GPS works?
i flashed entropy's kernel after miui successfully boot up in order to get my buttons to work again, so yes
raishiro said:
i flashed entropy's kernel after miui successfully boot up in order to get my buttons to work again, so yes
Click to expand...
Click to collapse
Great! Can you please check if GPS works?
Google Maps works, just cant get a lock on Navigation. also, just discovered that the launcher restarts whenever you try to turn on usb storage with your cable plugged in...preventing you from accessing your files on your computer
raishiro said:
Google Maps works, just cant get a lock on Navigation. also, just discovered that the launcher restarts whenever you try to turn on usb storage with your cable plugged in...preventing you from accessing your files on your computer
Click to expand...
Click to collapse
Yeah, I just flashed it a little while ago. Everything looks really good expect for a few small problems (as you mention) which I can live with but I really need the GPS to work to consider this my dailer driver. Here's to hoping someone can get it fixed.
tsg2513 said:
Yeah, I just flashed it a little while ago. Everything looks really good expect for a few small problems (as you mention) which I can live with but I really need the GPS to work to consider this my dailer driver. Here's to hoping someone can get it fixed.
Click to expand...
Click to collapse
Anyone know how to get the GPS working?
So after a couple of hours searching the web, it may be that the GPS problem is inherent in MIUI 2.3.
For those who want to get in on CM12 pronto, here is a straight-from-CM-source build. The usual disclaimers: I'm not responsible for anything going wrong, including but not limited to bricking your tablet, requiring reflashes, or the NSA spying on you.
I will update this post with new builds as I create them every day or two, depending on what changes are merged: http://review.cyanogenmod.org/#/q/status:merged+branch:cm-12.0,n,z
If something doesn't work, I doubt I can help you, I'm not developer. I just ran the build and installed it on my Nexus 7 to see if it works (it does!). No cherry picks, just merged CM ROM/Kernel. However, if something doesn't work, post it.
What works: Everything stock plus a few CM features.
What's broken: Some people report data connection problems
What's here (1/03+):
Battery % indicator in notification bar, choosable icon
A bunch of behind the scenes stuff
Trebuchet
Status bar brightness control
Single-down swipe for settings panel for swipes on the right side of status bar
Privacy Guard (including Privacy section in settings)
CM File Manager
Advanced Reboot
CM Superuser controls
Double-tap status bar or lockscreen slider to sleep
Notification light controls (including custom lights for individual apps)
Codec enhancements
Option not to have the screen wake on plug
ADB over network
Voice wakeup
Lots of CM app Material design changes
Requirements:
Latest bootloader installed via fastboot
The ROM from here: 1/06 - https://www.androidfilehost.com/?fid=95887005526787409
Old versions:
1/05 - https://www.androidfilehost.com/?fid=95887005526786861
1/04 - https://www.androidfilehost.com/?fid=95887005526786862
1/03 - https://www.androidfilehost.com/?fid=95864024717074739
12/31 - https://www.androidfilehost.com/?fid=95864024717072947
12/29 - https://www.androidfilehost.com/?fid=95864024717071892
12/24 - https://www.androidfilehost.com/?fid=95864024717069216
12/22 - https://www.androidfilehost.com/?fid=95864024717068185
12/21 - https://www.androidfilehost.com/?fid=95864024717067734
12/19 - https://www.androidfilehost.com/?fid=95864024717066366
12/17 - https://www.androidfilehost.com/?fid=95857557620393232
12/18 - https://www.androidfilehost.com/?fid=95857557620393643
GAPPS: http://d-h.st/l6z
Latest TWRP
Instructions:
The usual: Backup, Wipe, Flash Zips.
If you have problems downloading files after you flash this, follow the steps listed here: http://forum.xda-developers.com/showpost.php?p=57295498&postcount=89
I DID NOT DO ANY OF THIS WORK. ALL THE CREDIT GOES TO:
The CM Team
Chainfire
TheMuppets
The testers: nazafalas, skynet11
Cheers
I tried the 12/17 build but got bootloop city even though I had already been running a Lollipop ROM. I was grilling some buffalo wings (woohoo!) at the time so I had waited well over 20 minutes. I'm trying again so I can try to grab a logcat if it doesn't boot this time.
Edit: Oh snap! This time it booted! Thanks for your hard work to everyone involved ��
The LTE radio seems a bit wonky, being disabled until I toggle airplane mode on and off again (after which it seems to work fine). Also, it gives some 5-digit number for my carrier as opposed to saying "Verizon Wireless." I tried to grab a logcat but it didn't contain anything useful. Sorry ?
bootloop
lolo696 said:
bootloop
Click to expand...
Click to collapse
Flash again. Someone else had the same problem. Let me know if it persists.
skynet11 said:
The LTE radio seems a bit wonky, being disabled until I toggle airplane mode on and off again (after which it seems to work fine). Also, it gives some 5-digit number for my carrier as opposed to saying "Verizon Wireless." I tried to grab a logcat but it didn't contain anything useful. Sorry ?
Click to expand...
Click to collapse
Carriers have unique ID codes. Apparently matching up those codes to their respective carriers hasn't been done yet.
Thanks for the heads up on the radio.
Wipe cache and dalvik is needed for first install, then no problem with boot.
Works good, thanks
Working fine. Thanks for supporting DEB
Working VERY fine. No radio issues for me, German APNs seem to be in order, as well.
deb build
Full wipe works best from km 4.04. Great so far with everything working to plan. Not used cm since my Xoom days.
First of all, THANK YOU for supporting deb! :fingers-crossed:
I tried to dirty flash over an existing AOSP install first (I know, bad Ambious) and obviously it didn't boot very well (it actually started deodexing, then stuck at 'Starting apps').
So then I went back to recovery, full-wiped, flashed clean.... and nothing. Endless boot (people throw the term 'bootloop' around where it's actually just a boot hang).
Tried clearing cache, dalvik, fix permission even - to no avail.
I also can't logcat because the CM default requires manual authorization... :/
(I have everything backed up so it's no biggy, I just really wanted to try it).
Any tips?
Ambious said:
First of all, THANK YOU for supporting deb! :fingers-crossed:
I tried to dirty flash over an existing AOSP install first (I know, bad Ambious) and obviously it didn't boot very well (it actually started deodexing, then stuck at 'Starting apps').
So then I went back to recovery, full-wiped, flashed clean.... and nothing. Endless boot (people throw the term 'bootloop' around where it's actually just a boot hang).
Tried clearing cache, dalvik, fix permission even - to no avail.
I also can't logcat because the CM default requires manual authorization... :/
(I have everything backed up so it's no biggy, I just really wanted to try it).
Any tips?
Click to expand...
Click to collapse
flash your previous ROM again, flash CM12 over it, and if it gets stuck on "starting apps" again just do a normal reboot. It's really weird how a simple reboot after one of these lockups works better than starting over from scratch. I've only rarely ever seen this be the case, and I've been flashing custom ROMs since the Eclair days.
Bum, now stuck in boot whatever, I'll try a reflash later.
skynet11 said:
flash your previous ROM again, flash CM12 over it, and if it gets stuck on "starting apps" again just do a normal reboot. It's really weird how a simple reboot after one of these lockups works better than starting over from scratch. I've only rarely ever seen this be the case, and I've been flashing custom ROMs since the Eclair days.
Click to expand...
Click to collapse
Amazing how the simplest of solutions sometimes pass by us.
It actually worked
Thanks!
Can some people test GPS for me? Thanks!
Worked fine for me last night even indoors.Not got round to a reflash today though so on kk at the moment, not sure why it wouldn't boot up this morning even with a soft reboot.
Clean flashed 19 build and gapps, all working as it should,no issues with 3g,GPS or videos so far.????
GPS works great for me ?
Mmmm battery stats saying 4hours left o 82%, better watch that.
As soon as you turn it off and back on it goes into bootloop or sticks on upgrading app.