Where can I find a stock Gingerbread ROM at? When I purchased my phone it already had ICS on it, and honestly I do not like it at all. I jumped to my favorite phone mod site (XDA) and did some searching but came up empty handed. Can anyone assist me with my request? Thanks!
qtipextra said:
Where can I find a stock Gingerbread ROM at? When I purchased my phone it already had ICS on it, and honestly I do not like it at all. I jumped to my favorite phone mod site (XDA) and did some searching but came up empty handed. Can anyone assist me with my request? Thanks!
Click to expand...
Click to collapse
Sorry. There are not any GB ROMs for the D4 that will work on ICS. The GB D4 ROMs there are are not compatible with the ICS kernel. Maybe if you can describe the issues you are having with ICS we can help you with those.
Sent from my XT894 using Tapatalk 2
Mainly just nitpicking things, but the one thing I've had an issue with ICS is the fact that I cannot link notification and ringer volumes together.
Another issue I'm having is when typing using the hardware keyboard, I'll be typing something and the cursor will
jump and start typing at the beginning. Happened just as I was typing this reply, too.
qtipextra said:
Mainly just nitpicking things, but the one thing I've had an issue with ICS is the fact that I cannot link notification and ringer volumes together.
Another issue I'm having is when typing using the hardware keyboard, I'll be typing something and the cursor will
jump and start typing at the beginning. Happened just as I was typing this reply, too.
Click to expand...
Click to collapse
That is odd stock ICS does not have the functionality to link notification and ringer volume. You should be able to find an app on the market that will give you this functionality. Found this on another forum with a quick google search: "Get cvolume from the market. Under settings you need to check notification volume not(Use incoming call volume for notifications). Works great" aarong03 - DroidForums
There are other volume control apps out there as well that may have similar functions. Try some out and let us know!
Not sure about the cursor jumping on you. It seems like I had this problem once too and it ended up being something I was doing that was causing it but I cannot think for the life of me what it was. Some button I was hitting or something.
kwyrt said:
That is odd stock ICS does not have the functionality to link notification and ringer volume. You should be able to find an app on the market that will give you this functionality. Found this on another forum with a quick google search: "Get cvolume from the market. Under settings you need to check notification volume not(Use incoming call volume for notifications). Works great" aarong03 - DroidForums
There are other volume control apps out there as well that may have similar functions. Try some out and let us know!
Not sure about the cursor jumping on you. It seems like I had this problem once too and it ended up being something I was doing that was causing it but I cannot think for the life of me what it was. Some button I was hitting or something.
Click to expand...
Click to collapse
Thanks for the information. I have tried many volume apps that claim to link the volumes together, but do not work. I basically just want to use my hardware volume buttons as a master volume control, so when I set it with the hardware buttons, nothing is higher. or lower than that volume. I had a Samsung captivate glide on att that was running GB and the app that I used on that phone did not work on my D4 for linking volume. I tried this cvolume app and it doesn't seem to be working either, even though the option to link them is set.
qtipextra said:
Thanks for the information. I have tried many volume apps that claim to link the volumes together, but do not work. I basically just want to use my hardware volume buttons as a master volume control, so when I set it with the hardware buttons, nothing is higher. or lower than that volume. I had a Samsung captivate glide on att that was running GB and the app that I used on that phone did not work on my D4 for linking volume. I tried this cvolume app and it doesn't seem to be working either, even though the option to link them is set.
Click to expand...
Click to collapse
I use audio manager pro. It costs about $3 but is well worth it - Play Store
-
There is also a free version that just doesn't allow saving of profiles.
azrael293 said:
I use audio manager pro. It costs about $3 but is well worth it - Play Store
-
There is also a free version that just doesn't allow saving of profiles.
Click to expand...
Click to collapse
I've been using AudioGuru for profile selection, but I would much rather be able to dynamically change the volume of notifications and ringer together from the hardware buttons instead of set profiles with defined volume levels at each.
I have not found an app yet that works on this phone/ICS that works to lock both volumes together.
Perhaps I will just have to wait until JB is officially released for our phones. But I really liked GB on my previous phone, its too bad I can't get a ROM to work from ICS to GB, considering that the phone was originally released with GB.
Another thing I don't like about ICS is the stock messaging only let's you save a maximum of 1000 messages per contact. I would prefer messages never get automatically deleted, and in ICS it cannot be disabled, you can only change the max number of kept messages.
If you attempt to downgrade the phone to official GB there is a very high risk of bricking the phone.
I'd recommend you stop trying to do this and instead try to either get used to ICS or to replace the bits you don't like with some 3rd party apps.
I'm always having that cursor problem with the keyboard. Happens whenever I open up the keyboard and immediately start typing. Wait a second or two before typing, and it's usually ok. Seems the input editor is too slow to initialize itself, so it's still trying to set the cursor to column zero by the time you start typing...
Sent from my DROID4 using Tapatalk
If you need to back to gingerbread dowlnoad official moto ginger software
http://sbf.droid-developers.org/cdma_maserati/list.php
niko99 said:
If you need to back to gingerbread dowlnoad official moto ginger software
http://sbf.droid-developers.org/cdma_maserati/list.php
Click to expand...
Click to collapse
did you try yourself before suggesting?
There is no risk in downgrading to GB via SBF. No risk, because you will most certainly B R I C K your phone. So learn to live with it.
I too have some issues with ICS. The cursor jump happens to me too, and I hate it. I also have issues with BT volume control. Music is no problem, but controlling Youtube volume does not work for me. And when docked (lapdock or plain HDMI cable) volume also doesn't work. On or off, nothing in between.
But still, I think ICS runs much smoother than GB.
with locked bootloader is unable to brick droid ( always is way to get back phone to life) but ppl must know what ar they doing
niko99 said:
with locked bootloader is unable to brick droid ( always is way to get back phone to life) but ppl must know what ar they doing
Click to expand...
Click to collapse
Yes you can (maybe) bring your phone back to life, but one thing that will definitely not happen is that Gingerbread ROM actually booting. The locked bootloader does not allow you to downgrade.
Do not even bother trying to downgrade it will waste your time and you may end up with a brick.
highlandsun said:
I'm always having that cursor problem with the keyboard. Happens whenever I open up the keyboard and immediately start typing. Wait a second or two before typing, and it's usually ok. Seems the input editor is too slow to initialize itself, so it's still trying to set the cursor to column zero by the time you start typing...
Sent from my DROID4 using Tapatalk
Click to expand...
Click to collapse
Die Bruine said:
There is no risk in downgrading to GB via SBF. No risk, because you will most certainly B R I C K your phone. So learn to live with it.
I too have some issues with ICS. The cursor jump happens to me too, and I hate it. I also have issues with BT volume control. Music is no problem, but controlling Youtube volume does not work for me. And when docked (lapdock or plain HDMI cable) volume also doesn't work. On or off, nothing in between.
But still, I think ICS runs much smoother than GB.
Click to expand...
Click to collapse
At least I know I am not the only one with the cursor jump issue. And yes, I notice it only happens to me when I open the keyboard and immediately start typing. I will have to start being patient and give it a few seconds before typing.
I've tried many different Volume apps, and even when locking volume settings are enabled, the volumes are not locked when I adjust it with the hardware volume rocker.
I did read that JB will be getting an official push to the D4, but they have not said when. ICS just doesn't set too well with me for some reason. Yes, it runs pretty smooth, but I don't like it's all black theme, some functionality that was left out, and the new widget being part of the app list doesn't always show new widgets immediately. I guess my biggest upset about it is that it seems rather... buggy or undeveloped. To me, GB seemed to be more developed and work the way you would come to expect an android OS to run now days, and ICS just isnt there yet. Hopefully JB will be better...
niko99 said:
with locked bootloader is unable to brick droid ( always is way to get back phone to life) but ppl must know what ar they doing
Click to expand...
Click to collapse
I bricked my first droid 4 without problems with locked bootloader. do you want a link I sell it for parts?
olegfusion said:
I bricked my first droid 4 without problems with locked bootloader. do you want a link I sell it for parts?
Click to expand...
Click to collapse
unless you borked your bootloader or had a hardware failure niko is right there is no way to hard brick your phone just by flashing roms/sbf's
as long as your bootloader is intact you are able to recover your device
All that said, there's no reason someone couldn't get a vanilla AOSP GB build working with the ICS kernel for use with safestrap. On the XDAndroid project we had a single Linux 3.5 kernel working for Froyo, GB, and ICS. It's not a slamdunk, but the amount of patching required isn't that bad.
Sent from my DROID4 using Tapatalk
Related
my touch screen was crazy when I get my phone out of my pants. I did not touch the screen but it still automatically run the app and drag the taskbar up and down .........
nobody is like me???
care to share more details and/or what ROm you're running? 2.2?
it happened randomly to me too, with any rom 2.1 2.2, but I still didn't figure the reason out yet..
Same for me.I have cronos 1.6.1 on phone with adw launcher.But happens only ones or twice.
Sent from my Milestone using Tapatalk
You guys probably overclocked it too much damaging the touchscreen.
Crypto_ahash said:
You guys probably overclocked it too much damaging the touchscreen.
Click to expand...
Click to collapse
this makes no sense mate. The overclock affects the cpu and not the touch screen. Anyway I didn't use any extreme overclock, beside using for a while the Telus Lite with 1.1ghz oc stock. And well I barely played any game, just a lot of emails and surfing on the web, very few calls. I noticed it happens when i move too much, like dancing or when i leave it on the shelf for the night and by the morning it acts crazy
lapy said:
this makes no sense mate. The overclock affects the cpu and not the touch screen. Anyway I didn't use any extreme overclock, beside using for a while the Telus Lite with 1.1ghz oc stock. And well I barely played any game, just a lot of emails and surfing on the web, very few calls. I noticed it happens when i move too much, like dancing or when i leave it on the shelf for the night and by the morning it acts crazy
Click to expand...
Click to collapse
I used to have that issue with stock 2.1 roms.
CM6, Sense mod, fastest Eclare and now MIUI does not bring that night mare back to me.
Also, if you charge using a 2-pin socket [the one without the earthed pin, popular in Asia], it'll show up.
OP needs to be a little more clear, but let me say my results.
Ever since flashing 2.2.1 SBF and then applying a few Froyo Mods and even goign back to ECLAIR,
I noticed that multitouch screws up. Sometimes it things I have a finger on the screen already, so by putting a finger on, it does a pinch zoom on me even though I only have 1 finger on it. Then sometimes it doesn't let me press an icon on my screen insisting my finger is elsewhere. Other times the notification bar starts getting pulled down randomly.
Perhaps Kadalban can explain his Multitouch fix, but for me it seemed to solve a lot of issues. Granted it was only pushed out in CM6 12/4/2010, which gives me 1 day to test so far, but some of those freak-incidents have been disappearing. You'd have to give me 3-5 days to conclude anything, but for now it seems to have done the trick.
i have issue with eclair 3b and CM6....it crazy when i I get my phone out of my pants....
is it FW error or HW error? in my country, in my country there are many like me.and we do not have a solution for this problem rather than the touch screen
google translate
duytrum444 said:
i have issue with eclair 3b and CM6....it crazy when i I get my phone out of my pants....
is it FW error or HW error? in my country, in my country there are many like me.and we do not have a solution for this problem rather than the touch screen
google translate
Click to expand...
Click to collapse
Update to the new CM6. 12.04.2010 solves it for me.
i'm using it....and now,i don't have issue again. i testing it.
Sent from my Milestone using XDA App
how did you fix your screen.my homebutton does not respond
I just changed to some mod roms and the problem disappeared for me.
Some of my friends got really big issue with the touch panel and when they came to Motorola service point, the technicians said there is a known issue with the panel they used but not all customers are affected (hence some people are OK after trying different roms).
So if one experiences it then just needs to go to Moto and they'll change to a healthy-guaranteed panel obviously, if you're still under warranty, it's free!
I've never rooted my phone but am about to receive my third nexus one because of power button failure and I don't want to do it again. I watched some Nexus One development video where they were using a machine to depress the trackball thousands of times, to simulate lifetime use and test for failure. I guess they didn't test the power button.
Any suggestions on a ROM similar to stock but that has wake on trackball press? I was looking at cyanogenmod.
It seems like there should be an app for this, but I noticed an enhancement request on Google code, I guess that ability was removed in 2.3.3.
I am currently using anyunlock to wake my phone with the volume button but am not really a fan. I don't want to adjust the volume and it replaces the lock screen.
Thanks a lot.
CM7. Like Stock but...better!
DirkGently1 said:
CM7. Like Stock but...better!
Click to expand...
Click to collapse
+1
CyanogenMod is one of the best alternative ROMs out there. All the features of stock with a ton more added (along with bugfixes).
archinloaf said:
I've never rooted my phone but am about to receive my third nexus one because of power button failure and I don't want to do it again. I watched some Nexus One development video where they were using a machine to depress the trackball thousands of times, to simulate lifetime use and test for failure. I guess they didn't test the power button.
Any suggestions on a ROM similar to stock but that has wake on trackball press? I was looking at cyanogenmod.
It seems like there should be an app for this, but I noticed an enhancement request on Google code, I guess that ability was removed in 2.3.3.
I am currently using anyunlock to wake my phone with the volume button but am not really a fan. I don't want to adjust the volume and it replaces the lock screen.
Thanks a lot.
Click to expand...
Click to collapse
agreed with cm7 (if you prefer the normal stock look) I personally don't like all that sense / miui stuff. now that the big bugs are fixed, i don't see why you shouldn't give it a try.
cyanogen 7 really is easily the best option. and with the newest battery increases and optimizations, its a no brainer to use cm7 over stock.
Running Kang-o-rama-1.2 . . . . It's just CM7, kind of.
Loaded it last night and seems to be the best so far. The least amount of lost MMS compared to regular CM7.
samson_420 said:
Running Kang-o-rama-1.2 . . . . It's just CM7, kind of.
Loaded it last night and seems to be the best so far. The least amount of lost MMS compared to regular CM7.
Click to expand...
Click to collapse
There were issues with MMS messages in the nightlies due to a merging conflict when they merged to the 2.3.4. This has been resolved for the last couple of weeks.
I'm not sure if that is what you were talking about.
How much free memory do you have on your phone?
All,
We don't have an ICS Bugs thread going on. I wanted to check with some of the people here on XDA to see if they are experiencing what I am. Currently on .213, but most of these bugs I've seen since the begining. Oh, I'm also in Canada running on 3G HSPA+. I'm stock, but rooted with safestrap installed.
1) When placing a phone call, the phone hangs up immediately (you here the disconnected beep), then retries the phone call a few seconds later (it always succeeds). I have tried this on a freshly wiped phone and found the same experience. I have also tried disabling the Assisted Dialing, but have found ikt's the same thing
2) When using Google Chrome, if there is a input box, most of the time my keyboard won't appear (I'm using Swype as my default keyboard)
3) Phone runs hot sometimes, and when it's running hot it slows down to a halt. Usually happens after a day or two without a restart
4) My photo doesn't appear in the text messaging app (worked in AOKP/CM9 on my D3, as well as it works on my gf's Nexus S)
The only bug I noticed was that it initially booted up in global mode, and wouldn't connect to 4G/CDMA. Switching it to CDM+LTE fixed the issue and I haven't seen a bug since (213).:good:
podspi said:
The only bug I noticed was that it initially booted up in global mode, and wouldn't connect to 4G/CDMA. Switching it to CDM+LTE fixed the issue and I haven't seen a bug since (213).:good:
Click to expand...
Click to collapse
Is your chrome working properly? Specifically the bug I mentioned in the OP...?
I didn't comment on that because I use Opera
Just tried the Chrome Beta now just to see, and I can confirm I am seeing the same behavior. I use Swiftkey, so it isn't a Swype-specific bug either.
What exactly is the difference between Chrome and the built-in browser? Aren't they both Webkit-based? Why is Google bothering to work on both?
podspi said:
I didn't comment on that because I use Opera
Just tried the Chrome Beta now just to see, and I can confirm I am seeing the same behavior. I use Swiftkey, so it isn't a Swype-specific bug either.
What exactly is the difference between Chrome and the built-in browser? Aren't they both Webkit-based? Why is Google bothering to work on both?
Click to expand...
Click to collapse
Chrome is way faster at many things since it users hardware acceleration for video. Does text input work properly on opera?
Sent from my XT894 running ICS
I'm in the US also running .213
I haven't noticed any bugs, its working fine for me. I do not use chrome beta so I can't comment on that. The stock is not too bad, I don't use it much anyways.
Sent from my DROID4 using xda app-developers app
danifunker said:
Chrome is way faster at many things since it users hardware acceleration for video. Does text input work properly on opera?
Sent from my XT894 running ICS
Click to expand...
Click to collapse
Text entry works fine in both the stock browser and Opera. BTW, Opera also has hardware acceleration, which is why it never worked in any of the Frankbuilds of ICS based off the GB kernel ... So you can have your teh snappy and type with it too :laugh:
I'm on the 212 build and i can't screencap using power + volume down.
Is this fixed in 213 or am i just doing it wrong?
Also on 212 i can't control the default google music app or winamp from my bluetooth headset when the screen is off. I could do this before with the same version of the winamp app when i was back on gingerbread. I tried upgrading winamp, but that did nothing. Is there any change in 213?
Thanks ahead of time
Edit: just tried it and the volume down + power combo worked. Lol
One question, possible thought to ponder.
Are the bugs being described here really bugs of Android 4 or are they bugs in the individual app itself not being fully compatible with Android 4 yet?
Do similar bugs happen on a non-motorola device with android 4?
I'm considering flashing one of the leaks, so I'm trying to understand how you are sure these are ics bugs before I make the leap and run into issues.
Thanks.
Apologies if this constitutes hijacking the thread, if it does let me know and I"ll edit it to delete the question.
I was able to figure out bug #4, I had to login with my Google+ account again, since the update yesterday everything seems to be working fine.
Bugs 1 through 3 still exist, although I've switched off Global mode for now and put it to GSM only, it seems like the phone runs a lot cooler in this mode.
Even after updating Chrome to the final version, I'm still experiencing that text input bug. Maybe it's a Motorola issue... Can't wait for the next version of the leak!
I have tasker reboot my phone every morning at 6am. The phone doesn't need to be rebooted every day, but it ensures that it is fresh and ready to go every morning :laugh:
Nothing more annoying than trying to do something with your phone and having to reboot it because it is slow for whatever reason.
podspi said:
I have tasker reboot my phone every morning at 6am. The phone doesn't need to be rebooted every day, but it ensures that it is fresh and ready to go every morning :laugh:
Nothing more annoying than trying to do something with your phone and having to reboot it because it is slow for whatever reason.
Click to expand...
Click to collapse
for this reason I think there will be other leaks, ICS is supposed to handle killing processes much better than GB, however the settings seem to not be aggressive enough in 213.
Probably there will be, though I likely won't update again for a while. Don't feel like losing all that data...
podspi said:
Probably there will be, though I likely won't update again for a while. Don't feel like losing all that data...
Click to expand...
Click to collapse
You could just do what I do: once you have root install safestrap and then take a backup of your phone before flashing the upgrade.
Once you're all done upgrading, re-root and re-install safestrap, then do an advanced restore and only restore the data. Voilla, all your apps are back.
podspi said:
Probably there will be, though I likely won't update again for a while. Don't feel like losing all that data...
Click to expand...
Click to collapse
I don't know, just had a random reboot after watching a youtube video in firefox, most likely memory related, not sure who's fault though, Motorola or Firefox. gotta root and use system tuner to change memory mgmt states.
danifunker said:
You could just do what I do: once you have root install safestrap and then take a backup of your phone before flashing the upgrade.
Once you're all done upgrading, re-root and re-install safestrap, then do an advanced restore and only restore the data. Voilla, all your apps are back.
Click to expand...
Click to collapse
That is a great idea. Though there hasn't been another leak since 213, so
Notification Bar Sticking/Wont Pull Down
I am on 212 currently, and I have noticed in 208 and 212 something that has happened only twice so far. Today, I just tried to check my notifications, and the bar will not pull down.
After a reboot it works fine, and it has only happened 2 times in the past couple weeks since the leaks first appeared.
Obviously it is a minor glitch, but just thought I'd throw it out there in case anyone else has seen it and overlooked it. :cyclops:
danifunker said:
You could just do what I do: once you have root install safestrap and then take a backup of your phone before flashing the upgrade.
Once you're all done upgrading, re-root and re-install safestrap, then do an advanced restore and only restore the data. Voilla, all your apps are back.
Click to expand...
Click to collapse
I have heard of a few others using this method successfully. If you are not using safestrap or just don't want to go this route take a look at the post link in my signature. It's a modified version of the original Droid 4 Utility and includes a script to jump from one ICS leak to another without losing data. It also flashes the GB files and the Kernel (boot.img) in one script, thus making it easier to go from one leak to another.
Regarding bugs, my wife got a razr yesterday. It wouldn't pull down the ICS update, so I just sideloaded it. We both run some of the same apps. So this gave me a chance to do side by side comparisons.The issue with some of the icons being small in the left top of the status seems to be a app issue. The chrome issue isn't present on the razr, of course there isn't a physical keyboard. Otherwise my 213 ICS seems to run great.
I found a new bug, it looks like GSM call forwarding doesn't work properly... at least it doesn't with my SIM card, I'm on Rogers in Canada.
Does Verizon support call forwarding? Does it work on there?
I have noticed in Chrome that pressing shift and then one of the symbol keys (like @) will only work if you hold the shift key.
More importantly I don't get notifications of app updates from google play. Check to see if you have any apps that need updating. Superuser had a update on July 1, dropbox yesterday and voodoo rootkeeper on June 28, I think. Anyone else?
Hi folks,
Apologies if this question has been asked on the Bionic forums elsewhere; I did a search and didn't find anyone with an answer.
I've been experimenting with custom ICS ROMs on my Droid Bionic, and of the four I tried, three of them leave me in a situation where my Home button doesn't work. This applies to both the capacitive key on the Bionic bezel as well as the soft key which is native to ICS in phones that don't have capacitive or hard buttons (but can be enabled for the Bionic in custom ROMs).
Let me break down what I mean by "work". When I press or long-press Home, I get the appropriate visual and and haptic feedback as expected. But nothing happens in the OS. I expect it to take me to my home screen from any app; it does not. I expect the capacitive button long-press to bring up the Recents for multi-tasking, and it doesn't. I've assigned different behaviors to the soft key in the launcher, both press and long-press, and none work. All other capacitive and soft keys work just fine, and CM10 on my Iconia A100 doesn't exhibit any home button issue.
Here are the ROMs I tried which exhibited this issue for me:
CyanogenMod 9 (CM9 20120725 build, unofficial)
AOKP (Targa 20120725 Milestone 6 build)
LiquidSmooth MR 2.6 (Jester's JMOD modification of LiquidSmooth v1.5)
Currently I'm running on LiquidSmooth v1.5 MR 1, and it works perfectly. One thing I noticed is that CM9 runs the Trebuchet launcher, and AOKP and the JMOD of LiquidSmooth both run Nova Launcher. Meanwhile, the Liquidsmooth build I'm on is running what looks like LiquidSmooth's own modified Launcher (forgive me as I betray my n00b roots). I can only assume that the launcher is the issue and that perhaps if I just ripped LiquidSmooth's launcher APK I could run/use it in any other ROM, but this is just an assumption. I'm just wondering if anyone else experienced what I did, because from the looks of it I haven't found anyone who has.
Thanks for any insight anyone can provide!
This issue with the Home Button is not Bionic specific. I have had this issue with both Bionic and OG Droid. It has more to do with the OS I believe. I know I've read about this somewhere but I don't remember where. Usually it happens when you upgrade your phone with a custom rom and for some reason it disables the home button. In my case I just reinstall said rom until it works. It's happened a few times with my OG Droid considering I would switch roms always weekly due to the unlocked bootloader. Not so much on the Bionic since it's locked. Waiting for Motorola to release the bootloader unlock for our Bionic...hurry up Motorola or Google...I know I didn't really answer your question but that's my experience.
amageus said:
This issue with the Home Button is not Bionic specific. I have had this issue with both Bionic and OG Droid. It has more to do with the OS I believe. I know I've read about this somewhere but I don't remember where. Usually it happens when you upgrade your phone with a custom rom and for some reason it disables the home button. In my case I just reinstall said rom until it works. It's happened a few times with my OG Droid considering I would switch roms always weekly due to the unlocked bootloader. Not so much on the Bionic since it's locked. Waiting for Motorola to release the bootloader unlock for our Bionic...hurry up Motorola or Google...I know I didn't really answer your question but that's my experience.
Click to expand...
Click to collapse
Even though it wasn't a direct answer I definitely appreciate the insight! It's good to know what's happening out there and I now have some more context around the situation... It's weird because Liquid is really the only one that works for me. I just now tried a CM9 update just for kicks and again the Home button doesn't work. (Using Trebuchet natch.)
MrCHUPON said:
Even though it wasn't a direct answer I definitely appreciate the insight! It's good to know what's happening out there and I now have some more context around the situation... It's weird because Liquid is really the only one that works for me. I just now tried a CM9 update just for kicks and again the Home button doesn't work. (Using Trebuchet natch.)
Click to expand...
Click to collapse
I know that the Bionic and the OG Droid are not the only ones who experience this dreaded dead home button issue. It exist in a lot of android phones. You could google it and get a lot of hits on different phones. I know I have the first time I experienced this issue with the OG Droid. Could have something to do with the coding in the roms you are installing and it seems to be a hit and miss. Apparently your phone is picky about which rom it wants you to install lol. Maybe a developer could chime in and explain a bit more? Or someone with a lot more knowledge?
t
amageus said:
I know that the Bionic and the OG Droid are not the only ones who experience this dreaded dead home button issue. It exist in a lot of android phones. You could google it and get a lot of hits on different phones. I know I have the first time I experienced this issue with the OG Droid. Could have something to do with the coding in the roms you are installing and it seems to be a hit and miss. Apparently your phone is picky about which rom it wants you to install lol. Maybe a developer could chime in and explain a bit more? Or someone with a lot more knowledge?
Click to expand...
Click to collapse
Ino developer but I had this problem as well but once I flashed the latest gapps all was well.
Hope this helps
Hey,
So my dad isnt exactly satisfied with the custom ROM I flashed on his device, he needs to wait about 4 - 5 seconds (!) when theres an incoming call for the screen to turn on. The ringtone will keep on going off during that few seconds, but the screen will be black.
So I tested it on my Nexus 4, and no such issue has been spotted by me. Although, on his device, no matter how many times I tried, the issue was never gone and I had to wait a couple of seconds for the screen to turn on so I could see who's calling.
I'm not sure whether it is a kitkat issue or not, I tried 2 different roms, first BeanStalk, and now CyanFox, both had the same issue.
I also tried to flash CM10.1, but the keyboard kept on crashing after a fresh flash, wipes didnt help (maybe someone could give me a hand here?).
Another question is, where can I find some good call recording app? the ones from the play store aren't good, they only record one side of the call, never both
tl;dr:
is there some setting that I should change for the screen to turn on quicker when theres an incoming call on kitkat?
what to do if I want to downgrade from kitkat to jellybean?
is there some GOOD call recorder app around?
thank you
Pawelss said:
Hey,
So my dad isnt exactly satisfied with the custom ROM I flashed on his device, he needs to wait about 4 - 5 seconds (!) when theres an incoming call for the screen to turn on. The ringtone will keep on going off during that few seconds, but the screen will be black.
So I tested it on my Nexus 4, and no such issue has been spotted by me. Although, on his device, no matter how many times I tried, the issue was never gone and I had to wait a couple of seconds for the screen to turn on so I could see who's calling.
I'm not sure whether it is a kitkat issue or not, I tried 2 different roms, first BeanStalk, and now CyanFox, both had the same issue.
I also tried to flash CM10.1, but the keyboard kept on crashing after a fresh flash, wipes didnt help (maybe someone could give me a hand here?).
Another question is, where can I find some good call recording app? the ones from the play store aren't good, they only record one side of the call, never both
tl;dr:
is there some setting that I should change for the screen to turn on quicker when theres an incoming call on kitkat?
what to do if I want to downgrade from kitkat to jellybean?
is there some GOOD call recorder app around?
thank you
Click to expand...
Click to collapse
If you still on cm10.1 then download keyboard from market and you are good to go Also stock 4.1.2 has this lag issue when incoming call its pretty annoying really
tuncay_93 said:
If you still on cm10.1 then download keyboard from market and you are good to go Also stock 4.1.2 has this lag issue when incoming call its pretty annoying really
Click to expand...
Click to collapse
hey, thanks for your reply
actually no, STOCK 4.1.2 didnt have this issue, it started to show when I flashed 4.4.2 on it, is there some sort of fix for this or do I have to downgrade to JB? I'd rather stick to KK as I prefer it more.
on the other hand my dad hated google hangouts and he wants the stock messaging app back, I guess I can only go with CM
also I cant install a keyboard from the market, because I cant even log in to my google account, I cant get through the setup without a few things crashing over and over again, every second or so. the keyboard doesnt even show up
delete the latinIme.apk from the zip file you are trying to flash and substitute it with one from the other roms you tried flashing.
I know how to control the delay with which the ringer starts but not screen :s
These commands I think only help when call ends but it doesn't hurt to try, add them (or check the values if already present)
to build.prop in zipfile before you flash it
Code:
ro.lge.proximity.delay=5
mot.proximity.delay=5
I am on kitkat right now and have no lag issue...have you tried changing kernel?
Rudjgaard said:
delete the latinIme.apk from the zip file you are trying to flash and substitute it with one from the other roms you tried flashing.
I know how to control the delay with which the ringer starts but not screen :s
These commands I think only help when call ends but it doesn't hurt to try, add them (or check the values if already present)
to build.prop in zipfile before you flash it
Code:
ro.lge.proximity.delay=5
mot.proximity.delay=5
I am on kitkat right now and have no lag issue...have you tried changing kernel?
Click to expand...
Click to collapse
hey, thanks for your reply
I flashed Nameless ROM and surprisingly the lag issue is gone, and due to stripped gapps I flashed, I got the old messaging app back, which is quite the perfect combo, now the only thing I am missing is a good call recording app, is there a chance you can suggest one to me?
thanks again!
Pawelss said:
hey, thanks for your reply
I flashed Nameless ROM and surprisingly the lag issue is gone, and due to stripped gapps I flashed, I got the old messaging app back, which is quite the perfect combo, now the only thing I am missing is a good call recording app, is there a chance you can suggest one to me?
thanks again!
Click to expand...
Click to collapse
Still havent tried nameless but i did red the thread about it. Seems everyone likes it. It should be good
tuncay_93 said:
Still havent tried nameless but i did red the thread about it. Seems everyone likes it. It should be good
Click to expand...
Click to collapse
well I tried it out, the rom is nice and all, but my phone is extremely slow, the lag issue with phone calls is back, sometimes turning the screen off is impossible, or takes up to 2 minutes (!). turning it back on isnt much better either, I dont know what the problem is, the same thing happened on the BeanStalk ROM so I assume it isnt a software issue, but a hardware one, do you have any ideas what could be the problem and how can I solve it?
I want to tell you my experience about custom roms.
I don't know if you tried this combo: CM11 + kicos kernel (modified iodak's kernel) + minimal PA gapps
I works for me very well.
LGaljo said:
I want to tell you my experience about custom roms.
I don't know if you tried this combo: CM11 + kicos kernel (modified iodak's kernel) + minimal PA gapps
I works for me very well.
Click to expand...
Click to collapse
yeah, but shouldnt all the 4.4.2 ROMs be quite snappy? doesn't kitkat reduce the hardware requirements? why would JB work fine (or so I think, I'll go back to stock in a few mins and see) and KK be laggy as hell?
I've got a theory, I'm not a hardware guy and I dont know if I'm right or not, but:
could be that one of the cores is damaged and the system tries to switch some tasks to the damaged core (if android handles different cores the way I think) and that core doesnt really work the way it should, causing the entire system to work like a granny?
Pawelss said:
well I tried it out, the rom is nice and all, but my phone is extremely slow, the lag issue with phone calls is back, sometimes turning the screen off is impossible, or takes up to 2 minutes (!). turning it back on isnt much better either, I dont know what the problem is, the same thing happened on the BeanStalk ROM so I assume it isnt a software issue, but a hardware one, do you have any ideas what could be the problem and how can I solve it?
Click to expand...
Click to collapse
This is probably some wake/lock problem with software. Also on my o2x i've noticed strange lag when i press the power key it has lag until the screen comes on buttons below the screen light and after a couple of seconds the screen. It has 4.3 CM rom there if your father is using this phone i would suggest you some stock based rom with custom kernel. They should not have problems like these.
tuncay_93 said:
This is probably some wake/lock problem with software. Also on my o2x i've noticed strange lag when i press the power key it has lag until the screen comes on buttons below the screen light and after a couple of seconds the screen. It has 4.3 CM rom there if your father is using this phone i would suggest you some stock based rom with custom kernel. They should not have problems like these.
Click to expand...
Click to collapse
That still the best sollution for him - optimized kernel with stable ROM. He probably isn't techno freak?
tuncay_93 said:
This is probably some wake/lock problem with software. Also on my o2x i've noticed strange lag when i press the power key it has lag until the screen comes on buttons below the screen light and after a couple of seconds the screen. It has 4.3 CM rom there if your father is using this phone i would suggest you some stock based rom with custom kernel. They should not have problems like these.
Click to expand...
Click to collapse
could be, however, it isnt only for the power button, when the screen is off and a call is coming, it needs a few seconds for the screen to turn on, after the call is done, the system is all choppy and laggy. Turning the screen off after that is also nearly impossible, due to power button malfunction. I went back to stock for now and I'll see if the lag is gone, if it isnt, then its probably a hardware issue.
edit:
yeah, I'm on stock 4.1.2 and the issue isnt gone.
crap.
sounds like a problem in the timing the processor uses for scaling frequencies...
hav no idea what could be causing it unless you have some kernel tweak app and set wrong values
Have you tried clean flashing the Roms you installed? Have you Factory-Reset, Cleared cache, cleared Dalvik cache, and maybe did a system partition format before flashing?
Inviato dal mio GT-P3110 utilizzando Tapatalk