New alternate method below!
Wildchild and Romrix both suggested to create a new google sync account to solve the in call volume issue but that did not work for me. At least, not at first. Not only did I have no contacts, no calendars, etc., I still had low in call volume. I then added my old google sync account so I could back up my contacts but they did not import as a secondary account so I deleted the account from the phone and it told me my settings would also be deleted from google sync. I then reflashed 4.1 beta tweaks build and synced back to my original google sync account to get contacts. While syncing, my phone rang. I answered to discover that my in call volume had fixed itself. After spending a day trying to recreate the low in call volume I was left scratching my head. That's when wmunn said:
wmunn said:
Here is a direct quote from the google android support pages regarding data backups using the automatic backup feature.
"If you uncheck this option, your data stops getting backed up, and any existing backups are deleted from Google servers."
Going from this statement, it would appear if you flash your device, uncheck backup during the initial set up, then later reflash the phone and check the box that should have completely wiped any backup data on that account and be starting fresh.
At least thats what they are stating.....
Click to expand...
Click to collapse
Thank you wmunn for pointing that out.
That's when I put it all together and came up with this guide.
These are the steps that worked for me...
Delete your google sync account from your phone (3.6 or 4.1 doesn't matter) so it will delete any stored settings from google sync account (settings are still on phone though) (extremely important).
Create a new gmail account and do nothing with it after authorization.
Back up anything you want to keep from internal sdcard.
Boot into recovery by removing battery and NOT through the power menu shortcut. (optional but recommended)
Normal wipes with two additions... Wipe internal sdcard and wipe system (extremely important)
Flash your phone with 4.1 ROM from either Homeslice or WildChild (both are experiencing the same problems with in call volume).
Sync to new "virgin" gmail account during setup so it will "virginize" your settings in the phone and get rid of any stored google sync settings (extremely important)
Once your phone is completely booted and synced with google, pull your battery and enter recovery (optional but HIGHLY recommended at this stage. The idea is to get as "fresh" of an install as possible).
Reflash your phone with 4.1 ROM and sync with old google sync account.
Set up as normal from here.
Good Luck! Let me know your results
UPDATE: I now know that romrix stumbled across this "fix" back in February. He fixed it by backing up his contacts with SnapPea, creating a new google sync account, syncing to it leaving his old account behind, and restoring his contacts with SnapPea. I did not know this when I created this thread. Sorry Romrix.
****************************************************************************************************************************************************
****************************************************************************************************************************************************
Alternate method:
The above worked for me until I flashed a new WCX Beta ROM and my volume was gone again. This time, no matter how many times I tried the above steps, my volume just would not come back. So, I decided to try something new. This is what worked this time:
I deleted my google sync account from my phone.
I relocked my bootloader using fastboot and my unlock.bin token.
I ran the RUU from my computer and let it flash my phone back to stock 3.6.
I skipped through the setup steps (do not log in to google sync at this time).
I unlocked my bootloader using fastboot and my unlock.bin token.
I rebooted into bootloader and flashed recovery and kernel using fastboot making sure to use the latest WCX Beta ROM kernel.
I booted into recovery (WCX preferred) and wiped everything except for boot and sdcard (do wipe internal sdcard).
I then flashed the latest WCX Beta ROM.
I completed setup but did not log in to google sync yet.
I tested in call volume. It was good.
I logged in to google sync and made another test call. No change to in call volume.
Good luck again!
Thanks for this again. Everyone Keep in mind this is not affecting all users the same. I'm a firm believer in the 'if it ain't broke dont fix it' policy. But anyone who does this please report back with what you find
Sent from my HTC PH39100 using Tapatalk 2
Updated OP. Steps left out. Sorry :redface:
I'm gonna test this and report back
Sent from my HTC PH39100 using xda app-developers app
zippox180 said:
I'm gonna test this and report back
Sent from my HTC PH39100 using xda app-developers app
Click to expand...
Click to collapse
Thank you. It can't really be labelled as a [FIX] until more people than just me post positive results
Do you think this method will work with CM10?
Conjukt said:
Do you think this method will work with CM10?
Click to expand...
Click to collapse
I imagine it will work when switching to ANY other ROM. All we are doing is flushing google sync settings from google sync and our phones.
Conjukt said:
Do you think this method will work with CM10?
Click to expand...
Click to collapse
I believe that the low call volume on cm10 has to do with the noise cancelling mic not liking the AOSP drivers...
And that really means nothing cuz I'm not a Dev...
Sent from my Vivid 4G using Tapatalk 2
phrotac said:
These are the steps that worked for me...
Delete your google sync account from your phone (3.6 or 4.1 doesn't matter) so it will delete any stored settings from google sync account (settings are still on phone though) (extremely important).
Create a new gmail account and do nothing with it after authorization.
Back up anything you want to keep from internal sdcard.
Boot into recovery by removing battery and NOT through the power menu shortcut. (optional but recommended)
Normal wipes with two additions... Wipe internal sdcard and wipe system (extremely important)
Flash your phone with 4.1 ROM from either Homeslice or WildChild (both are experiencing the same problems with in call volume).
Sync to new "virgin" gmail account during setup so it will "virginize" your settings in the phone and get rid of any stored google sync settings (extremely important)
Once your phone is completely booted and synced with google, pull your battery and enter recovery (optional but HIGHLY recommended at this stage. The idea is to get as "fresh" of an install as possible).
Reflash your phone with 4.1 ROM and sync with old google sync account.
Set up as normal from here.
Good Luck! Let me know your results
Click to expand...
Click to collapse
Almost there... but do I do full wipe again before performing step number 9??
Yes. Just like you normally would.
OK so I finally got myself situated with cm10 and I followed everything to the t. Now...I made some test calls and it seems louder...now this is in no way conclusive and could very well be placebo. But first test worked well with a baby screaming in the background. But I wont know until I take it to a more crowded place. But it seems better... I will continue testing
Sent from my Vivid 4G using xda app-developers app
rignfool said:
I believe that the low call volume on cm10 has to do with the noise cancelling mic not liking the AOSP drivers...
And that really means nothing cuz I'm not a Dev...
Sent from my Vivid 4G using Tapatalk 2
Click to expand...
Click to collapse
That's possible. I don't know anything about cm10. I flashed it once after I s-off'd just to see that the boot flashed too but then I went back to WCX right after. Funny, wildchild's kernels still have to be flashed manually even with s-off.
zippox180 said:
OK so I finally got myself situated with cm10 and I followed everything to the t. Now...I made some test calls and it seems louder...now this is in no way conclusive and could very well be placebo. But first test worked well with a baby screaming in the background. But I wont know until I take it to a more crowded place. But it seems better... I will continue testing
Sent from my Vivid 4G using xda app-developers app
Click to expand...
Click to collapse
If it worked then it would be a noticeable difference, or at least it was for me on wcx 4.1 beta. I even had to turn my volume down once because I have a friend who practically screams into his phone
phrotac said:
These are the steps that worked for me...
Delete your google sync account from your phone (3.6 or 4.1 doesn't matter) so it will delete any stored settings from google sync account (settings are still on phone though) (extremely important).
Create a new gmail account and do nothing with it after authorization.
Back up anything you want to keep from internal sdcard.
Boot into recovery by removing battery and NOT through the power menu shortcut. (optional but recommended)
Normal wipes with two additions... Wipe internal sdcard and wipe system (extremely important)
Flash your phone with 4.1 ROM from either Homeslice or WildChild (both are experiencing the same problems with in call volume).
Sync to new "virgin" gmail account during setup so it will "virginize" your settings in the phone and get rid of any stored google sync settings (extremely important)
Once your phone is completely booted and synced with google, pull your battery and enter recovery (optional but HIGHLY recommended at this stage. The idea is to get as "fresh" of an install as possible).
Reflash your phone with 4.1 ROM and sync with old google sync account.
Set up as normal from here.
Good Luck! Let me know your results
Click to expand...
Click to collapse
phrotac said:
Yes. Just like you normally would.
Click to expand...
Click to collapse
nope... no luck. I have followed the instructions to the letter.:crying:
I have tried in the in-call volume as well as the loud speaker. both are still the same volume.
Wow......just did it....and it's loud. Tested in 3 places all crowded with plenty background noise, with fresh cm10.
CM10 powered, Jelly Bean made.
stormleader said:
nope... no luck. I have followed the instructions to the letter.:crying:
I have tried in the in-call volume as well as the loud speaker. both are still the same volume.
Click to expand...
Click to collapse
What ROM? Borked?
Also, I don't remember seeing anyone reporting low speakerphone volume too. Did it work correctly on other ROMs?
[email protected] said:
Wow......just did it....and it's loud. Tested in 3 places all crowded with plenty background noise, with fresh cm10.
CM10 powered, Jelly Bean made.
Click to expand...
Click to collapse
That's awesome! I'm glad to hear it. It even works for cm10!
The one thing I noticed was that it seemed louder and the slider moved made no difference but I don't remember the slider actually moving before. I just called and had a fan blowing in the background and I could hear again I have to test more but my house is fairly quiet besides the baby
Sent from my Vivid 4G using xda app-developers app
I had to cover my unused ear while pressing the phone to my head really hard and say "What?" a lot before. Now I can hear them without even touching the phone to my head. I am using WCX 4.04-4.1 beta tweaks build. I haven't tried with Borked so I was hoping to hear reports from users of Borked, good or bad. Hearing it worked for one user of cm10 was a bonus so I'm hoping you will be the second cm10 user to have success.
The way I see it, if 5 WCX users have success, 5 Borked users have success, and 5 cm10 users have success, this can be relabelled as [FIX] instead of [POSSIBLE FIX]
phrotac said:
What ROM? Borked?
Also, I don't remember seeing anyone reporting low speakerphone volume too. Did it work correctly on other ROMs?
Click to expand...
Click to collapse
yes Borked ROM, I had to go back on stock to s-off just right before following the instructions and the difference in volume was huge.
and Yes,,, when I go on loud speaker, from distance, it almost sounds like the normal in-call volume, have to put it close to my ears to hear it (happens on CM10, touchwiz or borked, but stock and Holics were fine).
hmm... this worked for other people, I might try it again just in case I made a mistake...
Remember, you have to remove your google sync account on the phone so it will delete google's settings from google before you reflash and sync to the new gmail account. Doing this will delete settings from both google and your phone.
I really hate to say this but I have not had any positive reports with this working with Borked but instead I have received two reports of it NOT working with Borked. I have, however, received positive reports with both cm10 and WCX 4.1 Beta, no negative reports on either ROM, and one "maybe, not sure" report on cm10.
Related
For some odd reason, my wife's phone will randomly lose sound output and input.
For instance, cannot make calls because no sound is heard through speaker and it seems the mic becomes non-functioning, therefore the person on the other line hears nothing.
I've noticed at the same time that no other sounds (system, media, key presses, etc.) can be heard as well.
If the phone is rebooted the problem is fixed. This problem occurs usually once or twice a day. Its running a nearly stock 2.1 w/ root (although no root apps used or installed), I have also tried a different custom rom and have the same issue.
Any ideas? (I have searched and read up on some things, but did not see a definitive answer)
** Working on a fix now **
DrewX2, I'm having the same exact problem. Thought I was crazy! So I have the Damageless 2.08.1 (Android 2.1) ROM installed, and I thought I was being punished for not using Sprint's official ROM image . But you say that your wife's phone exhibited this behavior in more than one setup? What do you mean by "nearly stock"? Maybe someone out there knows of a way to look or download the internal error logs on the Android platform so we can at least get some stack trace info? Thanks!
Here guys, try this thread.
http://forum.xda-developers.com/showthread.php?t=657244&highlight=Audio+fix
-------------------------------------
Sent via the XDA Tapatalk App
danaff37 said:
Here guys, try this thread.
http://forum.xda-developers.com/showthread.php?t=657244&highlight=Audio+fix
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
This is the exact fix I installed. So far no problems, will report back in a day or two.
Also, for the earlier question, when I said nearly stock, I should have said I am using nfinitefx45's Stock Sprint Deoxed ROM.
CyanogenMod 5.0.8 for HTC Droid Incredible
Koush just updated this to Test Version 3 today.
Get it here - http://inc.sodpit.com/roms/koush/
*FYI* I did not make, nor am I trying to take credit for this ROM. Just making a thread where it can be discussed.
Post up any bugs you notice here and I can add them to the 1st post in a list.
quite a few bugs in test 3 right now
1. High pitched whining sound when making phone calls
2. No speakerphone
3. No bluetooth
4. Camera is 3mp
5. No multi-touch in stock browser or maps
6. Trackball wake and unlock has dissappeared
7. Facebook sync not working
8. Internal storage not recognized
Calendar is force closing on me
Sent from my Incredible using Tapatalk
i can't get MMS to download
EDIT: disregard, seems to be working after a reboot
Oh wow. I guess I will hold off on installing this one then.
What has been fixed so far ? Graphic flickering issue still there ?
Maps is fc for me
Sent from my Incredible using XDA App
Graphical issues are fixed. You guys might wanna hold off on this one if you actually make phone calls. It's a pretty big issue, but I'm sure koush is working it out.
This release is also scoring much lower in linpack as well.... I'm getting 3.5s as opposed to 7s compared to the last test rom.
jonnybueno said:
quite a few bugs in test 3 right now
1. High pitched whining sound when making phone calls
2. No speakerphone
3. No bluetooth
4. Camera is 3mp
5. No multi-touch in stock browser or maps
6. Trackball wake and unlock has dissappeared
7. Facebook sync not working
8. Internal storage not recognized
Click to expand...
Click to collapse
These plus couple others.
Calendar is force closing
Can't get my contacts to sync right. 11 get pushed through but nothing else.
Also it seems a bit less responsive. Linpack was running 3.5 - 3.8 instead of my normal 8.1 - 8.3.
Can anyone get GPS to work? cell location works fine, but no GPS.
I will come back to this or any other roms when GPS is working.
You had me thinking this was a final version with the "[ROM] Cyanogen 5.0.8" thread
I too noticed no GPS.
I believe that this rom is a definate step in the right direction. Once the devs can get all of the hardware working in their roms, the sky is the limit. Thanks to Koush for all of his work!
I don't have Twitter, but does anyone else here?
Someone should tweet him to look at this thread because all the bugs are listed here (I'm sure he knows most of them but maybe not all). So this would help him a lot with progress I'm sure.
Droid Incredible Rooted!
Twitter is working for me and so is maps. Button unlock works too just have to hold it down for a few seconds.
Sent from my Incredible using Tapatalk
It says "upgraded to test version 3" in the first post.
Sent from my ADR6300 using XDA App
I didn't have any high pitched noise making calls and speakerphone worked fine for me. no FC's in Maps either.
andrew53517 said:
I don't have Twitter, but does anyone else here?
Someone should tweet him to look at this thread because all the bugs are listed here (I'm sure he knows most of them but maybe not all). So this would help him a lot with progress I'm sure.
Droid Incredible Rooted!
Click to expand...
Click to collapse
I'm sure he knows. That is why it is still called a test version. He is working on it still.
Sent from my ADR6300 using XDA App
I have maps working on mine. On the first boot I installed the maps update which broke it. Then I redownloaded the app pack from rom manager and installed it. It removed maps from my phone for some reason. I then installed maps from market again and it worked.
Sent from my Incredible using XDA App
-Calendar also FC for me. Couldn't fix it.
-Maps FC at first but after I reinstalled it from the market it worked.
-Reboot seems to turn off the phone rather than rebooting.
Been using this ROM since it popped up as update 3.
Noticed most of the above bugs, and got maps to install just like the others, however Google Earth is -refusing- to install properly. Also, I have the high pitched whining issue, but the ROM also isn't seeming to recognize my microphone so no one can hear me when I call.
All the progress is excellent so far, I'm very impressed with Koush's work. Can't wait till this thing is ready
Cameron_S said:
Twitter is working for me and so is maps. Button unlock works too just have to hold it down for a few seconds.
Click to expand...
Click to collapse
Do you see the option to enable anywhere in the settings? I can't get this working. you're on test 3 right?
seanhassars said:
I didn't have any high pitched noise making calls and speakerphone worked fine for me. no FC's in Maps either.
Click to expand...
Click to collapse
I reinstalled and the high pitch squeal went away. I think wireless n or hydra kernel may be the source of that issue.
On another note, Twitter works fine for me
ok i have updated to the new firmware and used app2sd from my previous post(other ones dont work on my milestone)
first i did 2 nano backups one just data and the other a full backup in case i screw up.i then flashed the new telus sbf after i did a wipe and then factory reset ,then i rooted(using open recovery)installed app2sd then did a nano restore of my data and voila its running with all my apps.
i must say the update is awesome gps locks in real quick it runs smoother overall everything launcher games,menu, home screen etc without overclock apk.no lag at all ..call are clearer but lets see on that still early.here is the link to the file http://groupoften.wordpress.com/ and my previous post on how to app2sd http://forum.xda-developers.com/showthread.php?t=692367
I am using this one since the day of release. All annoying bugs are ironed - location based service in 3G on non-Telus network works, no more music starting and stopping on its own, the newer and better youtube app and many other improvements.
Overall - HUGE improvements over current Telus stock one.
Edit: I forgot to mention the most important improvement: people stopped complaining I am breaking up on them when talking to me!!
do i just flash this using RBD?
Simply follow the how-to: http://groupoften.wordpress.com/category/how-to/
leobg said:
I am using this one since the day of release. All annoying bugs are ironed - location based service in 3G on non-Telus network works, no more music starting and stopping on its own, the newer and better youtube app and many other improvements.
Overall - HUGE improvements over current Telus stock one.
Edit: I forgot to mention the most important improvement: people stopped complaining I am breaking up on them when talking to me!!
Click to expand...
Click to collapse
yes i love that i dont break up on call's anymore also i notice battery life is better.the phone no longer reboots on its on
im new here, just a question, so this is the SBF file, what part of the phone does it change? I have the nandroid backup from other posters here after i flashed this SBF my RAM has gone down a lot, does anyone know? thanks
Check the other goodie G.O.T. offers - their open recovery. There are few hacks that it can apply which will cure your memory problems (as well as others like paid apps on market/etc).
the got hacks do not work you just get stuck in a boot loop
Just installed this firmware everything works. Ran GOT openrecovery too. 1.04a worked flawlessly. Running apps2sd from openrecovery was so cool. Partitioned my sd card, installed busybox, installed apps2sd, as well all my apps got moved over automatically. All done from openrecovery.
imma have to try this out soon
Shamelessly bumping this thread
Thanks a lot for the link to the ROM and the GOTS OpenRecovery, I never even knew about this. Hopefully the music auto-start issue goes away now!
dsixda said:
Shamelessly bumping this thread
Thanks a lot for the link to the ROM and the GOTS OpenRecovery, I never even knew about this. Hopefully the music auto-start issue goes away now!
Click to expand...
Click to collapse
Music auto-start is fixed. Along with geolocation issues in 3G and noise cancelation issues. Battery seem to last a tad longer too. Overall - I am extremely happy with the GOT Telus release!
leobg said:
Music auto-start is fixed. Along with geolocation issues in 3G and noise cancelation issues. Battery seem to last a tad longer too. Overall - I am extremely happy with the GOT Telus release!
Click to expand...
Click to collapse
I had issues earlier with G.O.T.'s JIT but realized it was my fault and it had to do with the dalvik-cache. After clearing it and installing JIT, those problems went away. However I was still unable to get JIT working 100%. Everything seemed to work fine until I started up Google Navigation, and then as soon as it locked onto a satellite the Milestone rebooted by itself. (EDIT: It's probably an overclocking issue, I had VSEL=56 with 1GHz; turning it up to 62 seems to have fixed it)
Audio bug doesn't seem to happen anymore. I did notice, however, at one point the audio played for a fraction of a second while doing some file browsing.... It was probably the bug trying to show up + the fix trying to suppress it. No big deal, as long as it's not too loud when it happens in public ;-)
yeah it happens.
I think it was a quick and dirty fix for it. Unfortunately only applicable to the stock Music app. Any other media app will auto play still
Hi guys,
I just came from CM7 to this CM6 by Milaq. Love it, everything is much faster, always enough RAM.
I did 3 wipes, flashed ROM through OpenRecovery, reboot, flash gapps for HDPI, reboot, and then restored some apps with titanium backup.
I'm having some issues, I'll list them in order of how much they're bothering me:
1) A bunch of system apps aren't showing up in the market and therefore aren't getting updated. Ex. Facebook, youtube, twitter, etc. What do I do and why did this happen?
2) Titanium backup seems to fail at restoring data for a lot of apps (ex. Shazam, LauncherPro, ColorNote, etc). At the very least I want my Shazam tags back. It doesn't say it fails, it says it's successful but once you open the app, the data isn't there. Interestingly enough, the data IS there in /data/data, at this point basically just taking up space. Now I'm wondering how many apps it restored data to which the data just sits there, useless.
3) The custom LED blink frequency in HandcentSMS just broke. It was working fine until I turned the CM setting "succession" on, and then off. Basically now the LED either blinks as it wants to (no matter what setting), or will stay on if I choose the "Default" setting OR a custom setting with 0 for the "off time."
HELP please?!?
I have had similar problems with market some time ago once switched from CM7 to CM6. I did several cleanups of the marked data and even full wipe plus SD card cleanup (there are some system folders) and suddenly it helped. Can't confirm what are the correct steps to recover from the problem ...
Additionaly had an impression the Google backup is causing some troubles so disabled it.
Edit:
The led blinking is controled by some hardware device so either you can't change the frequency OR apps controls the led by itself using main CPU, which costs extra battery ...
I stay with apps settings only and not change anything by CM settings and works fine. Every time have beeing playing with CM led settings ends up with some mess I could not recover from.
Sent from my Milestone using Tapatalk
janosik47 said:
I have had similar problems with market some time ago once switched from CM7 to CM6. I did several cleanups of the marked data and even full wipe plus SD card cleanup (there are some system folders) and suddenly it helped. Can't confirm what are the correct steps to recover from the problem ...
Additionaly had an impression the Google backup is causing some troubles so disabled it.
Edit:
The led blinking is controled by some hardware device so either you can't change the frequency OR apps controls the led by itself using main CPU, which costs extra battery ...
I stay with apps settings only and not change anything by CM settings and works fine. Every time have beeing playing with CM led settings ends up with some mess I could not recover from.
Sent from my Milestone using Tapatalk
Click to expand...
Click to collapse
1) is solved: I fixed the market by rolling back to the old market that is included with gapps. I forgot to write that I had updated to the new one (provided by Milaq though so I thought it'd be fine). All apps are seen now.
3) As for the LED, I know what you mean, as soon as you touch CM settings it gets messed up!!! How can I reset the CM settings? Tried data wipe through titanium backup on CM settings but it didn't do a thing... This is gonna bother me to no end.
EDIT: I somehow managed to find this thread: http://forum.cyanogenmod.com/topic/18051-solid-led-notifications/
Going to CM settings, selecting Succession and then clicking cancel at the dialog box seems to have brought the blinking frequency function back to handcent. Although...it's kind of buggy, doesn't alway blink properly. But at least some change is visible now. Does your led listen perfectly to on and off times?
Flyview said:
...
Going to CM settings, selecting Succession and then clicking cancel at the dialog box seems to have brought the blinking frequency function back to handcent. Although...it's kind of buggy, doesn't alway blink properly. But at least some change is visible now. Does your led listen perfectly to on and off times?
Click to expand...
Click to collapse
I do not use Handcent just the stock app and do not chage the CM led settings and everything works as expected.
In case seriuos problems Titanium Backup + full wipe is OK for me
Sent from my Milestone using Tapatalk
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?