Database Develop

TELUS – SHOLS_U2_03.11.0 and app2sd works too!!

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

CM6 bugs

Lately I've been using the latest CM6 test 8 Rom and have encountered a few problems. The kernel Koush is using is a pretty fast one with minimal power usage but I believe this has also contributed to overheating. While on other stock or stable roms this rarely occurs de my phone, but now when my phone is even idle, the overall heat radiating from it is not usual. Is anyone else having these issues? I must give Koush props for the camera fix, it is nice work for a test rom and I look forward to an upcoming camera fix. I have also noticed that on this Rom that I can not install certain apps. I have cleared my market cache and have done all I can think of to install the apps successfully. I have also noticed using the track pad to wake the phone is spotty. To me this is expected, for some reason even using this feature on other roms or lock screens is spotty too. I find that holding the track pad down for 5 seconds seems to wake the phone when the feature is enabled. I was also wondering about the notifications. Is it possible to get this feature available? Although this is a pre release, I admire the coding and work Koush did to get this Rom up when the people wanted it.
Sent from my Incredible using XDA App

http://forum.xda-developers.com/showthread.php?t=722478

There is a thread dedicated to CM6 bugs here: http://forum.xda-developers.com/showthread.php?t=722478
You'll probably get more help there b/c that's where the CM6 users are hanging out.

[Q] Where is RC1-7.0.0-11.02.18 CM7 for Milestone?

I see in the Dev forum that the first RC1 of Cyanogenmod 7 for Milestone is available, but when I go to download it here, it doesn't seem to be available. I guess it would be called update-cm-7.0.0-RC1-0.07-11.02.18-Milestone-signed.zip but that last one available was the 11.02.15 release. Does anyone know whether the RC1-7.0.0-11.02.18 has been withdrawn for some reason?
I've been testing each and every build with good success, so I'm really keen to try the new one. I would ask in the dev forum, but I'm relatively new at the XDA forum and am therefore not eligible to post in it.
SF

Well, I eventually found the correct download link at https://github.com/downloads/nadlabak/android/update-cm-7.0.0-RC1-0.07-11.02.18-Milestone-signed.zip
Thanks,
SF

How is it working out so far? I've recently just started using cm6 but I don't want to install too much / get invested in it if CM7 is solid enough to use day 2 day.

FANdroid said:
How is it working out so far? I've recently just started using cm6 but I don't want to install too much / get invested in it if CM7 is solid enough to use day 2 day.
Click to expand...
Click to collapse
I would stick with cm6 for now. CM7 could use many improvements and as of now is very memory hungry (I was on the feb.10 release). CM7, however, has many bug fixes that are not implemented in cm6, for example, the wifi fix (wasn't working with some n routers before I think [depending on the security type or something] ) and it seems as though there is also the random freeze + random reboot fix (using another, older kernel) I would not switch to CM7, until many bugs are fixed. Also some games don't work.

FANdroid said:
How is it working out so far? I've recently just started using cm6 but I don't want to install too much / get invested in it if CM7 is solid enough to use day 2 day.
Click to expand...
Click to collapse
It's great. But video playing not working for me.

So I installed CM7 to try it out, and on RC1 my videos play fine (widescreen) using the included "Video" app. Well most of them do, one of them is displayed 4:3 for some reason?

I'm finding that it works quite well. Battery life is good, but there are a few bugs that need working out. CM6 is probably better if you need your phone to be 100% reliable, but I like to push the boundaries and play around.
Bugs or missing features so far:
- Button lights and keyboard backlight not working properly for me (and at least one other user here)
- Auto backlight brightness not working for me at all
- Volume button swapping/remapping not yet implemented, so that in lanscape mode left means louder (which is the wrong way round for me)
- Memory usage is a problem, so that Launcher pro keeps having to re-initialise
- Camera is VERY unreliable
- Getting random reboots and lockups, especially in Google Maps
Still, things are getting better with every release and I can always go back to CM6 if I want, since I made a Nandroid backup in OpenRecovery before I installed the CM7 update. I've just installed the RC2 update, so lets see how that goes...
SF

Droid4 Stock ICS Bugs

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?

CyanogenMod 12 for HTC One Mini 2 (Memul)

Hi guys,
Thought I would start a thread for users of CyanogenMod 12 for HTC One Mini 2 (memul).
I have installed a nightly dated 24th February 2015. It seems to be working great, my only issues have been:
After phone restart, the first time you call someone you cant hear them. Call them again, the problem is fixed and doesnt seeem to come back for that contact. (will happen again for other contacts the first time you call them though).
Camera is very laggy and doesnt respond well at all...the viewfinder is super stuttery and laggy and when you hit the take a picture button it can take a second or two to respond. I dont use the camera much so it doesnt bother me.
Have had some problems with the music player not outputting music to the headphones after a while, but taking the headphones out, pressing play so it plays out the speaker, then putting the headphones back in fixes this. Again,
not a big issue.
Official TWRP stops working after going through setup, but factory reset from within CM12 fixes it if you do have to re-flash or something.
So I recommend CM12 latest nightly for our phone, its better than CM11 and actually had less problems than the Release channel rom for our device (CM11). Although that ROM says it has no known issues, there are known issues that have not been noted on the wiki.

Hey thanks for doing this, I am considering CM12 on my phone too. i use the loud speaker and the camera a lot, does this impact the sound quality? i really enjoy the boom sound on this phone.

ECEng said:
Hey thanks for doing this, I am considering CM12 on my phone too. i use the loud speaker and the camera a lot, does this impact the sound quality? i really enjoy the boom sound on this phone.
Click to expand...
Click to collapse
Loud speaker works fine, and one of the great things about cyanogenmod is the built in system level equalizer, so boom sound equivalent is built in. Camera, on the basis of the build i am using from mid Feb, is not so good...actually the pictures are not so bad but the actual viewfinder is very laggy and pressing the take shot button is slow to respond. It could be fixed in newer nightlies, I have been away from home for over a month but when i get back ill flash a new nightly.

snorglamp said:
Loud speaker works fine, and one of the great things about cyanogenmod is the built in system level equalizer, so boom sound equivalent is built in. Camera, on the basis of the build i am using from mid Feb, is not so good...actually the pictures are not so bad but the actual viewfinder is very laggy and pressing the take shot button is slow to respond. It could be fixed in newer nightlies, I have been away from home for over a month but when i get back ill flash a new nightly.
Click to expand...
Click to collapse
Thanks for the advice, I installed march 25th build last night.
From your first post, only problem i experienced was the camera, its still very laggy, and the picture quality dose not compare well to the original. I have tired third party camera app but no joy, similar issues. Other than that, happy to say every thing else is working fine, i will update regularly to see if camera improves.

Hi all,
I'm using CM12 since 2 weeks. In some case, the phone is very laggy. For example, with Chrome or also when opening new apps, of when i switch from app to other.
Maybe i'm not using the correct boot or recovery or radio.
Can you tell me which one is recommended with the CM12 ROM ?
Thanks.

mlhamdi said:
Hi all,
I'm using CM12 since 2 weeks. In some case, the phone is very laggy. For example, with Chrome or also when opening new apps, of when i switch from app to other.
Maybe i'm not using the correct boot or recovery or radio.
Can you tell me which one is recommended with the CM12 ROM ?
Thanks.
Click to expand...
Click to collapse
Hi there,
I have been flashing the latest nightly. I think we need to log a JIRA issue for the camera, but I havent checked if someone already did. It doesnt seem to be getting better does it?
Dont use chrome...if you dont like the cyanogen browser, try firefox XD
The best recovery is TWRP, see the other posts in our part of the forum about this. Make sure your get the U-RA version of TWRP as the official TWRP page doesnt list our device for latest versions.

Also I should note that the calendar doesnt work in this ROM in offline mode, which is true for all Cyanogen ROMs i believe. But the solution is to install from DroidForge the offline calendar account, and then you can enter items in the calendar without google calendar, or sync USB with outlook etc (latter requires purchase of sync program separately to go on your PC).

Bad news for CM12 on memul: the only developer u-ra has stopped working with our device. So there are no new nightlies anymore since 04/11 and we don't know when it will be going on.
Look here: http://forum.xda-developers.com/showthread.php?p=60126091

corbeau56 said:
Bad news for CM12 on memul: the only developer u-ra has stopped working with our device. So there are no new nightlies anymore since 04/11 and we don't know when it will be going on.
Look here: http://forum.xda-developers.com/showthread.php?p=60126091
Click to expand...
Click to collapse
That is bad news alright, Is there any way for me to get back to stock rom and wait for official lollipop release? I am quiet new to this.