Nice rom only when you try to rotate the screen it goes blacks/blue blank and pressing N button comes back awhile then try again to rotate the screen ..same thing happens...I done full wipe of Davik and factory reset..run the rom again same results happen...I think a update is needed for this build. any thoughts on this Guys?? Is there going to be a update??
Related
I guess I don't have enough posts yet to post in the Starburst thread in Development, but I was wondering had anyone ever experienced their motion sensor dying, or at least the loss of the auto-rotation feature after flashing this rom?
I have re-flashed several times, but I have NOT done a full factory wipe and then flashed yet. Perhaps this is the next step.
When I go into settings > screen > horizontal calibration, the thing appears to be a dead stick (little ball doesn't move) and when you hit calibrate it sits there for a few minutes then screen goes black and it goes to my lock screen.
I am going to try a full factory wipe and then flash it back to stock, but has anyone ever encountered this before?
Thanks in advance.
P.S. - I've searched everywhere and can't find mention of anyone having this problem before.
Okay after restoring backup from ROM manager the rotation is working again, indicating it was an issue with my flashing most likely? I will try a full wipe and try again with Starburst.
So even with a complete wipe, even formatting data, system, etc. I cannot get rotation working in Starburst rom. Any clues? This is completely baffling.
Just now i decided to update froyo to gingerbread and dx is a very nice looking and fast rom. But the weird thing is that the screen will fades and eventually turn off by itself, the only way to get the screen to work again is to press lock button to lock then unlock. This issue doesnt get away after few reboots. Also chinese language in dx is not fully supported.
Does anyone have the same problem?
Should i try any other gingerbread rom?
This is how i install rom:
Wipe dalvik cache, wipe partition cache, fatory reset, flash rom, flash modules_fix, flash cmparts_fix, factory reset.
Is this correct?
Hi,
You can't use Autobrightness , go to :
-Settings
- Display settings
-Brightnesss
then UNCHECK Automatic brightness
now issue with fading screen should no to take place
I flashed CM 10.1 nightly 031313 with no problems. I've been using it for several days now and after using Google Maps navigation, I put my X912 in my pocket. I take it out and it's shut off. Try to turn it back on, safestrap, continue, then black screen but backlight is on. A sudden vibration and then the backlight turns off, then on and just sits there.
I wasn't doing anything special with the ROM like updating or anything. It just "broke" in my pocket. Tried a cache and dalvik wipe. Reinstall. Nothing.
Short of wiping that ROM Slot and starting over, any ideas?
cschuck320 said:
I flashed CM 10.1 nightly 031313 with no problems. I've been using it for several days now and after using Google Maps navigation, I put my X912 in my pocket. I take it out and it's shut off. Try to turn it back on, safestrap, continue, then black screen but backlight is on. A sudden vibration and then the backlight turns off, then on and just sits there.
I wasn't doing anything special with the ROM like updating or anything. It just "broke" in my pocket. Tried a cache and dalvik wipe. Reinstall. Nothing.
Short of wiping that ROM Slot and starting over, any ideas?
Click to expand...
Click to collapse
kernel problem
flash a new kernel and the latest one of your choice
maybe this will solve ur problem(try to find the kernel in the dev section)if still it causes problem then ask
Hi guys, I was using my phone messaging my friends. I put the phone down for about half an hour. When I pick it up again it is hot and will boot to the glowing slimbean logo (boot animation). I assume the phone ran out of battery, but even when I plug it in it will not boot past the logo. Do you guys have any idea as to what is going on, and how I can get my phone working again?
Try booting to recovery and wiping dalvik (hold both volume keys, plus power at the same time - release all after the Samsung logo appears). Phones don't usually freak out like this unless there's something the user either did or installed, especially those running stable slim roms.
On another note, the version you're running is very outdated; have you considered installing the last i777 slim rom, based on 4.2.2 (8.1)?
SteveMurphy said:
Try booting to recovery and wiping dalvik (hold both volume keys, plus power at the same time - release all after the Samsung logo appears). Phones don't usually freak out like this unless there's something the user either did or installed, especially those running stable slim roms.
On another note, the version you're running is very outdated; have you considered installing the last i777 slim rom, based on 4.2.2 (8.1)?
Click to expand...
Click to collapse
Thanks for your reply Steve!!
The reason why I'm still using 7.1 is because I was having battery problems on 8.0. I wasn't sure if the bug I had was fixed so I decided to stay behind. This was probably not the best choice but convenience and stability were something I wanted. I will try 8.1 after I backup my current setup if it works.
I believe its Google Now that has been causing me problems. Ever since I started using it my battery drains much faster, and the phone is hotter than usual. If wiping the cache works then I will delete it , otherwise I will probably have to wipe to factory which I really don't want to do.
OK so wiping the dalvik cache has allowed my phone to get past the bootloop. I get this message "Android is Upgrading.. starting apps" and its been stuck on it for a while. Any ideas?
This is weird, don't really know why - out of nowhere - your rom just all of a sudden won't boot.
And yes Google Now will kill ANY battery!
One other method would be to dirty flash 7.1 without doing any more wiping, if you want to keep it. If that doesn't work, full wipe/format system and start over.
Hope you get it working again!
I'm really hoping someone can help me. My back and menu buttons stopped working today, and I'm pretty sure it has to do with a failed Swype install.
I'm running AOKP 4.4.2 (1/25 build) on my VZW Galaxy S4 (jfltevzw). The phone has been running great, but I can't stand the new kitkat keyboard. I decided to try Swype again, after dumping it a few years back.
I installed the free Swype (which obnoxiously comes with Dragon also), but I couldn't get past step two (select default keyboard). The wizard just wouldn't progress further. I went into the menu to try switch manually, but I trying to type would just bring up the installer again. I tried switching back to the stock keyboard via Settings>Language, but nothing would happen when I tried to type. The only thing I could do was reboot.
When I booted back up, the menu and back buttons would no longer work. I tried clearing dalvik and cache, resetting permissions, reinstalling AOKP and Gapps, and so on and so forth. I'm backing everything up to do a hard wipe, but I'm not holding my breath.
Has anyone seen this problem before? Is it failing during the Swype install just coincidence? I can't see how it could be....
After a hard-reset / factory wipe, everything is working again.
I will not be installing Swype on AOKP/KitKat again, hehe.