Related
For starters, HOLY HELL does this forum have the mother of all 'search ya n00b' features built in! Dang impressive!!
Second, being a long time stalker, and due to those previously mentioned features, I do not have the rights to post in the thread for this ROM. Thus I am posting my question here. I just recently installed the Incredibly Re-Engineered ROM v2.20 on my Inc. Out of all of the hacking that I have done to this poor phone, this ROM has given it the biggest improvement. However, I can't figure out how to access voicemails on it. The dev said that he fixed something with voicemails in this release but my not-so-smart-phone doesn't seem to know that.
I know that the Inc uses a native app instead of VZ's visual app and I am guessing that it's the one named Visual VM 1.13 that Titanium is telling me I am missing (but doesn't give me an option to restore). Anyone know the secret to getting this to work?
I'm not quite sure what you mean... Are you looking for a Visual Voicemail app, or are you unable to get to your voicemail at all? Have you tried dialing *86
Yeah, I could just call to get my messages but that would be too easy.
The issue is that the native app that downloads voicemails and plays them appears to be awol. When I get a voicemail VZ sends me a text stating "You have 1 unheard Visual Voice Mail messages. Please select the Visual VM icon to reinstall." However, you can't just download VZ's app because it will tell you that your phone already has an app built in for handling voicemails... except for my phone which now appears to be missing it.
Oh and before anyone asks, yes I did wipe the phone before installing the new ROM with ROM Manager.
Have you tried changing the voicemail settings to what you want to use to handle your voicemails? Menu > Settings > Call Settings
If you already have then maybe try pushing the apk through adb?
There is a flashover to 2.2 that is supposed to fix the VM indicator.
Absent that, there is also a flashable zip posted in the ROM and IncReEng. mods thread.
hth
g00s3y said:
Have you tried changing the voicemail settings to what you want to use to handle your voicemails? Menu > Settings > Call Settings
Click to expand...
Click to collapse
I did not even know about that setting. I have now set it to 'My Carrier' since I am not using Google Voice but unfortunately that didn't fix it.
smtom said:
There is a flashover to 2.2 that is supposed to fix the VM indicator.
Absent that, there is also a flashable zip posted in the ROM and IncReEng. mods thread.
hth
Click to expand...
Click to collapse
I did perform that flashover. Maybe I will wait until the updated ROM is posted tonight and see if that fixes it... otherwise I might have to go hunting for the zips you are referencing.
2wheel'r said:
I did not even know about that setting. I have now set it to 'My Carrier' since I am not using Google Voice but unfortunately that didn't fix it.
I did perform that flashover. Maybe I will wait until the updated ROM is posted tonight and see if that fixes it... otherwise I might have to go hunting for the zips you are referencing.
Click to expand...
Click to collapse
You can click on the little paperclip next to the rom thread title and see all the .zip attachments that have been posted in the thread. This way you don't have to go searching through the whole thread to find the files you are looking for.
I just wanted to update this in case anyone else is searching for an answer to this problem.
So I did an update to v2.3 of the Re-Engineered ROM and that didn't get my voicemail back. And I actually lost some more functionality. I'm not in any way diss'n this ROM though. The issue is just that it is a seriously customized piece of art and maybe a bit overkill for a phone that needs to occasionally be a phone!
Since I tried Skyraider in the past and had some syncing issues, I decided to load up Redemptive rEVOlution this time. So far everything is running smooth and it appears that my voicemail and everything else is working as it should.
BTW, I should mention that I work in the Quality field because I have a natural gift for breaking things. So my issues may not be typical for all users.
I believe the problem you are having with VVM is because re-ingeneered is 100% evo framework. Sprint does not use VVM and therefore not coded for it.
That being said, google voice offers the same features without the added fees from Verizon.
Disclaimer--- this is simply a thread to discuss and rant about issues with wifi calling related to MMS sending and retrieval as well as blurry mms. This is also to keep it in one place rather than on other posts where it becomes unrelated to the original topic. I have tested sending MMS through stock, hand cent, and go SMS and am unable to send pictures. This said I am using kl1 deodexed rom by whitehawx. This is just the beginning of my research and observation. Another user (docmjldds) mentioned that it was working on zombie rom but only using hand cent. Please post what roms you have tested and whether or not sending over wifi calling works for you. Also post what SMS app you are using and what file size it was also. Screenshots help but keep them G rated. Also post whether the pics where blurry. If it helps post what types of mms mods you have flashed. I will clean this up more when I get to a computer and update the list... please feel free to rant and rave. Just don't take it personal.
You can help research by posting the following:
1.) Rom you are using and version
2.) Kernel you are using
3.) Any mods, scripts, etc.
4.) Using wificalling only, NOT 4g, attempt to send MMS to yourself or other person using either
1.) Stock Rom
2.) Other sms app (please state which one works)
3.) State whether or not it DID or DID NOT compress the image when sending and if it failed, or when receiving if it ends up blurry.
My rom:
Deodexed KL1 by Whitehawx. Using Fauxkernel 07b5 default with no scripts or mods added.
[stock mms app] = unable to send large pictures but can send decent size. Takes more than 10 minutes for me to send. Compresses the images right away.
[Go Sms and Handcent] able to send regular sized pictures but not large ones >1mb. Still took 10 minutes to send. Compression occurred.
Did not notice any blurriness from the pictures that I did receive.
Updated List for ROMS able to send MMS/Large sized MMS, etc
--ZombieRom 3.0 Thank you Docmjldds for the heads up on this info.
Updated List for tweaks, mods, tricks to get MMS to send.
--Will update as people post.
Thanks for your contribution. I will post better screenshots of pictures sent and received.
I can send through Go SMS ...
I am running a mishmash of ROM's I threw together myself, I know not much help
It is 2.3.6 with KL1 ...
Using the alternate APN but transferred all the MMS settings to the new APN ...
I can send while on Wi-Fi with wifi calling enabled, BUT, it does seem to take a very long time ...
yes it helps. I noticed I sent one large pic about 200 KB and the other was less. After ten mins I got a link to download the smaller of the two. The bigger failed. No blurriness though. I got notifications from all the SMS apps with the smaller pic.
tcboo said:
I can send through Go SMS ...
I am running a mishmash of ROM's I threw together myself, I know not much help
It is 2.3.6 with KL1 ...
Using the alternate APN but transferred all the MMS settings to the new APN ...
I can send while on Wi-Fi with wifi calling enabled, BUT, it does seem to take a very long time ...
Click to expand...
Click to collapse
Sent from my SGH-T989 using XDA App
chib1panda said:
yes it helps. I noticed I sent one large pic about 200 KB and the other was less. After ten mins I got a link to download the smaller of the two. The bigger failed. No blurriness though. I got notifications from all the SMS apps with the smaller pic.
Sent from my SGH-T989 using XDA App
Click to expand...
Click to collapse
Not going to repeat the same old same old. I will simply watch and learn what others state. Until I see otherwise, I only ask users to try every ROM 2.3.6 based and tell me if they can specifically send and receive with the following parameters
1. Use WiFi calling enabled. I am NOT interested in 4G. That's NOT the issue here.
2. Be able to enable 1.0Mb file sizes to send with MMS and NOT have files shrink to 16-26Kb file sizes.
3. Not have to R+R any mms.apk files from one source to get around blurry mms issues.
Now, based on these parameters, I am simply going to make the following statement regarding what works for me and specifics. For those that have already heard me say this, hold your ears please since many users here may not have had the misery of reading my prior posts.
I have found that consistently only one ROM here for our model works. I have no idea on why. I am only stating to try the following.
The Zombie based ROM, currently 3.0 version here. Install per OP directions. Then install Handcent SMS third party app. It's the only app that works consistently for me where I can send large sized MMS files (350-950Kb sized) using WiFi calling enabled. It should only take a few seconds to send. And yes, these are the sizes received. I am using 2-3Mb pictures I take with our phone, using the 1.0Mb MMS settings for sending in the Handcent preference setup for MMS. You can use the stock message app to read the same file, AFTER it is first received with Handcent, BTW. Oh, like GoSMS Pro, you don't have that arrow showing in the mms file as if it's a video file you are seeing, BTW. I have seen this asked by others. But Handcent does not give that message "Unable to send. Wait till Network is available message". GoSMS Pro does give that message for me.
I have posted enough screen shots on various development threads so I won't clutter up the post here. If users ask, I will post to prove that with the ROM mentioned and Handcent, it works, but I cannot get this to work with any other ROM. Again, NOT 4G and not 16-26KB file sizes that I am interested specifically in.
1) didn't use 4g
2.) File over 1mb did not com press with hand cent nor go SMS but did with stock. I couldn't test what file size it was received as because large file never was sent.
3.) Did zombierom dev state what specific tweaks mods or scripts he used that other 2.3.6 roms. Don't have in them?
4.) I will have more time tomorrow so I can flash zombie and see if I can duplicate the same as you.
Thanks
chib1panda said:
1) didn't use 4g
2.) File over 1mb did not com press with hand cent nor go SMS but did with stock. I couldn't test what file size it was received as because large file never was sent.
3.) Did zombierom dev state what specific tweaks mods or scripts he used that other 2.3.6 roms. Don't have in them?
4.) I will have more time tomorrow so I can flash zombie and see if I can duplicate the same as you.
Thanks
Click to expand...
Click to collapse
Before 3.0 just posted it basically has been a plain Jane ROM much the same as the Original MrX first 2.3.6 or Whitehawk 2.3.6 ROM. No themeing to speak of. In fact, it doesn't even have the 13-14 toggle above the notification area. I would have to look at the original change-logs to see specifically what exact tweaks etc may have been incorporated. AFAIK, nothing at all different from the others. I can only add that I routinely change to the Faux kernels since I want BLN support, and the kernel he uses for stock doesn't offer it. But Kernels never played any role in what made this work or not work. Just an fyi.
Do you think kernel has anything to do with it? I would be very surprised to find out. Plus, I want to know why my wife's Mytouch 4g is able to send any type of picture, text quickly with good results?? whats different about HTC's wifi calling than ours? I know hers is activated by an actual app like other legacy wifi calling phones still do. I wonder if the way it is now implemented messes with sending MMS.
Docmjldds said:
Before 3.0 just posted it basically has been a plain Jane ROM much the same as the Original MrX first 2.3.6 or Whitehawk 2.3.6 ROM. No themeing to speak of. In fact, it doesn't even have the 13-14 toggle above the notification area. I would have to look at the original change-logs to see specifically what exact tweaks etc may have been incorporated. AFAIK, nothing at all different from the others. I can only add that I routinely change to the Faux kernels since I want BLN support, and the kernel he uses for stock doesn't offer it. But Kernels never played any role in what made this work or not work. Just an fyi.
Click to expand...
Click to collapse
chib1panda said:
Do you think kernel has anything to do with it? I would be very surprised to find out. Plus, I want to know why my wife's Mytouch 4g is able to send any type of picture, text quickly with good results?? whats different about HTC's wifi calling than ours? I know hers is activated by an actual app like other legacy wifi calling phones still do. I wonder if the way it is now implemented messes with sending MMS.
Click to expand...
Click to collapse
My wife also has a MyTouch4G and I believe it really has something to do with the newer implementation used by our style WiFi calling. I know that TMobile has already acknowledged to me it's an issue they are looking at. I really have a feeling they know they are intentionally overcompressing on the newer models like our SGS2. The Sensation I used to use also was on the older standard and worked just fine, as long as the model and brand name was correct in the build.prop files. Kernel is NOT an issue. I have basically tested every Kernel there is with all the ROMs. Zombie consistently works with any of them. Anecdotal here, the Revolution ROM that I believe is retired because of some XDA issues with the Developer, also did work, like the Zombie ROM too, but I am going on another close friend here that remembers it worked for him.
When I get the time, I have several programs that can do a file by file comparison. Takes a lot of time, but that's the only way I know of to see what is different from the base that Zombie is using vs the others. My feeling is it's a source files used issue. Just a guess.
EDIT:
PS... I have all the older files for the legacy method here along with the necessary build.prop edits that are required to make that older HTC method work. Not sure it will even be worth it, but I am going to try adding that stuff, lib files and APK and edits to see if it's even possible to use the older wifi calling.
It may also mean also going back to Android 2.3.5 base. I'm pretty ADD about this subject. I just need to find the time
Sounds like that too. I hope they fix it. It looks like you have more time than I do for testing. Ill be getting my new white one tomorrow so that means rerooting and installing everything again.
Edit-.saw your edit. That would be great if you could get that working.
Docmjldds said:
My wife also has a MyTouch4G and I believe it really has something to do with the newer implementation used by our style WiFi calling. I know that TMobile has already acknowledged to me it's an issue they are looking at. I really have a feeling they know they are intentionally overcompressing on the newer models like our SGS2. The Sensation I used to use also was on the older standard and worked just fine, as long as the model and brand name was correct in the build.prop files. Kernel is NOT an issue. I have basically tested every Kernel there is with all the ROMs. Zombie consistently works with any of them. Anecdotal here, the Revolution ROM that I believe is retired because of some XDA issues with the Developer, also did work, like the Zombie ROM too, but I am going on another close friend here that remembers it worked for him.
When I get the time, I have several programs that can do a file by file comparison. Takes a lot of time, but that's the only way I know of to see what is different from the base that Zombie is using vs the others. My feeling is it's a source files used issue. Just a guess.
Click to expand...
Click to collapse
Sent from my SGH-T989 using XDA App
chib1panda said:
Sounds like that too. I hope they fix it. It looks like you have more time than I do for testing. Ill be getting my new white one tomorrow so that means rerooting and installing everything again.
Edit-.saw your edit. That would be great if you could get that working.
Sent from my SGH-T989 using XDA App
Click to expand...
Click to collapse
Just to show how lame TMobile support is, out on their tech Forums they are basically telling users NOT to even have wifi calling enabled. Below is a stock answer I see this mod. posting to everyone with issues complaining about this subject.
Being a retired bum, I do have some time on my hands. I can think of better ways to spend it, but this is one nut I really would like to crack. But at least there's a method on a particular ROM that does work. So deoending on importance of this feature will dictate what any user wants in a given ROM. BTW, don't know why the Zombie developer is placing his beta stuff outside of XDA, but there are references to links. Latest 3.1.1 includes update for the multiple toggles above notification area. Just an FYI...NOT...again NOT trying to be a Troll, but I can see how I can be accused, by now
IF...other ROMs would work, I would have no reason to state what to use...really...
http://www.androidzombie.com/az/Andr...x0.9KERNv2.zip
***********************************************************************************
TMobile Reply
8. Jan 11, 2012 8:42 AM (in response to sjmrshll)
Correct AnswerRe: MMS will not download while WiFi is enabled...
Hi!
Let me first thank you for being part of our community! We are happy to have you here and love to see you as an active participant. Unfortunately we cannot guarantee any of your services will work over the wi-fi network. Not being able to both send and receive MMS over wi-fi is an issue that can be slightly common.
If you have any further questions, please feel free to reply to this message or contact any member of the staff. Thank you and have a great day!
- Alicia B.
Community Moderator
1.) Juggernaut 4.1
2.) Faux .007
3.) ICS Mod
4.) No matter what the file size no MMS will come through while I am connnected to wifi calling. If I disconnect and switch to 4G it will go through provided it has synced with Google.
1.) Stock SMS App doesn't work. Neither does GOSMS which is my go to texting app.
2.) See above.
3.) Fails completetly on download or upload.
Hope this helps!
Haven't tried zombie but the only rom I have tried that lets me send and receive mms while using wifi is when I'm on complete stock with root of course but its not really too much of a hassle to just switch wifi off if needed while using jugs 4.1 if it ever does get too annoying I always keep a backup of my stock just in case... So I know it has to be something that's been removed from the custom roms that keeps the phone from auto switching to data from wifi when using mms
Sent from my SGH-T989 using Tapatalk
rickm8384 said:
1.) Juggernaut 4.1
2.) Faux .007
3.) ICS Mod
4.) No matter what the file size no MMS will come through while I am connnected to wifi calling. If I disconnect and switch to 4G it will go through provided it has synced with Google.
1.) Stock SMS App doesn't work. Neither does GOSMS which is my go to texting app.
2.) See above.
3.) Fails completetly on download or upload.
Hope this helps!
Click to expand...
Click to collapse
IT basically verifies what my claims have been. Something about the Zombie Rom is different to allow MMS to work correctly as long as Handcent is being used. I used Tmoble_SGH-T989UVKL1_Stock_Rooted.zip as a base 2.3.6 to compare with the latest Zombie ROM although versions of this ROM have always worked. Using a program that actually does a great job of side by side taking files withing a given folder to compare with another source of given files. All of the folders basically used the same exact files. The few times lets say that one ROM used a slightly different version lets say of wificalling.apk as an example could not break either the working Zombie functionality, nor could using the Zombie based file in the stock ROM would NOT make that ROM work either. IOW I tried to switch files between these two ROMs, to either create a working stock ROM, or break the function of the ZOMBIE Rom. Could not succeed in making or breaking opposing ROMs.
If it as you say it's probably the system framework differs somewhere. Causing mms not to send.
Sent from my SGH-T989 using xda premium
Coming from my nexus one, we needed specidifc kernels built to support wifi calling. Maybe this new wifi calling is implemented different
Sent from my SGH-T989 using Tapatalk
Killbynature said:
If it as you say it's probably the system framework differs somewhere. Causing mms not to send.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
I am pretty much confident that you are correct it's a framework issue. I have used file comparison programs and rulled out every other source file, such as all of the lib files etc. And it has nothing to do with kernels. I have tested every kernel on all these ROMs and the same results occur, irregardless of kernel.
---------- Post added at 06:04 AM ---------- Previous post was at 05:58 AM ----------
drzplaya1121 said:
Coming from my nexus one, we needed specidifc kernels built to support wifi calling. Maybe this new wifi calling is implemented different
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
Nexus one was my first Android too. Bought it the first day of availability to the public, direct from Google back in Jan. 2010. The current Wifi calling is totally a different animal WRT our SGS2 phones. It's more or less based on the Network, itself, the proper Sim Card etc. Unlike the older WiFi calling that uses the Gans lib files and Build.prop edits, this doesn't rely on any of that stuff. And it's also a required Android 2.3.6 min. source. So yes...a totally different implementation.
I know this is an 'older' post but it helped me so here you go:
BeastMOD 5.0 (build Test13)
Sinergy kernel
no mods
The only way I can send mms over wifi is running Handcent. GO and stock wouldn't work. What ever zombie was doing made it's way into Melvins Rom
This issue is fixed in the ics leaks. Rom reconnects.to 4g momentarily to send or receive mms
Sent from my SGH-T989 using XDA
xUnreachablex said:
I know this is an 'older' post but it helped me so here you go:
BeastMOD 5.0 (build Test13)
Sinergy kernel
no mods
The only way I can send mms over wifi is running Handcent. GO and stock wouldn't work. What ever zombie was doing made it's way into Melvins Rom
Click to expand...
Click to collapse
I have the beastMOD 5.1 testbuild13 ROM also, but i could receive MMS and send MMS thru wifi in stock sms app. The only difference is that i have the darkside kernel.
Sent from my SGH-T989 using XDA
I'm using darkside rom with the included kernel, no mods or tweaks. WIFI calling and mms works fine, never experienced blurry mms.
Sent from my SGH-T989 using XDA
this is somewhat of a self serving post. I had a customer running a jb rom show me that some of my themes for Go sms pro weren't showing up properly. Could anyone help me with some testing? will compensate with some free themes. B-)
the ones that aren't looking right are any of my legacy themes and the enterprise themes.
looking for people on stock and custom jb roms.
thanks!
Sent from my HTC EVO 4G LTE
same problem
I've run into the same problem several times. Did you ever find out anyway to troubleshoot the issue or what may be causing it? RAM issue maybe? Some people say their screen goes blank, others says it turns a random color. Any ideas would be great. Thx.
skanndelus said:
this is somewhat of a self serving post. I had a customer running a jb rom show me that some of my themes for Go sms pro weren't showing up properly. Could anyone help me with some testing? will compensate with some free themes.
the ones that aren't looking right are any of my legacy themes and the enterprise themes.
looking for people on stock and custom jb roms.
thanks!
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
its something to do with the market and jelly bean. both of them together cause problems. ive been emailing the apks to my customers
Sent from my HTC EVO 4G LTE
thanks, that was it. I sent out an apk last night and it fixed the problem. here's a little more info about the jb download issue. hopefully it gets resolved soon, sending out individual apks isn't exactly productive iwiz-vicky.blogspot.it/2012/08/how-to-fix-paid-apps-from-play-store-on.html?m=1 ...sry if it doesn't link, still under 10 posts.
skanndelus said:
its something to do with the market and jelly bean. both of them together cause problems. ive been emailing the apks to my customers
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
GO SMS Pro Themes Jelly Bean
Hello!
I'me having a lot of issues too with my go sms pro themes. They can't be properly read from go sms pro now that they are installed into the folder mnt/asec by the play store in jelly bean .
This is the thread on google code for info:
http://code.google.com/p/android/issues/detail?id=34880
Google is not going to fix this (they said in the google code thread) although it causes a lot of problem. I don't really understand their logic.
They change that folder without saying a thing and cause this mess. Then they say that the developers need to fix this path. But the really annoying thing is that because of this only who pay the app is damaged, because who pirates it has a perfect working app.
I've written to the go sms dev team and they seemed totally unaware of the problem. I've said them they need to add that path in go sms pro in order to have themes working again in jelly bean. But I don't know if they can or will fix this.
Google is really doing a big mess with jelly bean in some aspects. This is a really bad thing and needed to be disclosed with developers before making the change.
I'm thinking they will never fix this. Google say that the application need to be fixed (in this case go sms pro) and the go sms dev team doesn't seem to mind about this problem. All their themes now are Getjar "FREE" or in-app buy. So they really don't care about all the customers of their older themes or about all the other dev that can't add their theme as an in-app purchase.
So I searched for the answer, but everyone seems to say that GW is working on CM10...I did get it installed with the workaround, but what I'm finding is that in my Settings app in CM10, that there is no NFC option. Am I just blind and missing it in a different menu, or why does it not show up? I'm using the newest 7/29 stable build.
dubbactrumpetmsu said:
So I searched for the answer, but everyone seems to say that GW is working on CM10...I did get it installed with the workaround, but what I'm finding is that in my Settings app in CM10, that there is no NFC option. Am I just blind and missing it in a different menu, or why does it not show up? I'm using the newest 7/29 stable build.
Click to expand...
Click to collapse
Don't hold this answer against me, but I am pretty sure that the NFC drivers are absent, Since CM10 is still in preview phase.
codyrichards said:
Don't hold this answer against me, but I am pretty sure that the NFC drivers are absent, Since CM10 is still in preview phase.
Click to expand...
Click to collapse
Not true. Tons of people using Google Wallet (NFC), and I'm using NFC Task Launcher just fine.
zmore said:
Not true. Tons of people using Google Wallet (NFC), and I'm using NFC Task Launcher just fine.
Click to expand...
Click to collapse
So I'm curious...on CM10, where should the settings be? Am I missing something, or should I reflash? Also...my soft buttons are gone?! Just the lights...they still work...
WOW!
I thought I was loosing my mind. I'm glad I'm not the only one having this issue. I scoured these forums so much today my phone ran out of juice around noon. I wonder why some S3 747 users are having issues and others aren't. I have the AT&T variant and am using the 07/29 preview release just like the other posts. I have already done all the wallet fixes, but can't seem to find how to turn the nfc on either. Can you tell us the work around you used to get yours to work?
I'm having the same problem, NFC options do not appear in settings and Google Wallet states that NFC is disabled. This is on an ATT SIII, running CM10.
Exactly...no idea on my end. I'm also finding that Android File Transfer doesn't work, so I can't use my new SD card...I also cant back up, since my current one is full...feeling like Im stuck for now.
zmore said:
Not true. Tons of people using Google Wallet (NFC), and I'm using NFC Task Launcher just fine.
Click to expand...
Click to collapse
You're running the preview build, right? Did you have to do anything to get NFC running or was it enabled by default?
So... By any chance, did you miss a step in the wallet workaround install? I had the exact same problem. Ended up having to wipe and reinstall my rom. Then follow the wallet workaround instructions exactly. Also, if you ever installed wallet from the market, go in and make sure auto update is unchecked. If you look at the original wallet thread in the development forum you'll see this happened to a couple of folks. Not sure of the cause, but I know that I had to reflash and also disable that auto update. I'd recommend a nandroid right after you reflash a clean rom and verify that nfc settings are there (under wireless - more).
HTH
Good luck!
Sent from my Galaxy Nexus using xda app-developers app
Settings------> more settings.
Sent from my rooted SGH-I747M
thecoach1999 said:
Settings------> more settings.
Sent from my rooted SGH-I747M
Click to expand...
Click to collapse
Thanks for that, but that was the first place I checked...since that's where it always is. The whole problem from the beginning was that it wasn't where it should be.
Anyway....
Good news. I found a workaround if it's missing. If you install CM9, make sure its there, then do a no-wipe install of CM10...there it is. Not sure why that works, or why it's missing in at least a few people's downloads of CM10, but that's my workaround. Going to try the newest version wallet workaround now and make sure it works.
I'm running into a really strange problem... while running a clean install of CM10, NFC is available in the menu. However, after installing Google Wallet via this method:
blog.tekkidd.com/2012/07/howto-install-google-wallet-on-att-samsung-galaxy-s3-sgh-i747
the settings option for NFC disappears.
I can run NFC by going through root access and installing nfc.apk from the app folder, however, this makes the phone EXTREMELY unstable, and it will begin to freeze up every few minutes. For the time being, it looks like the best option would be to wait for Wallet compatibility to be improved in the coming updates.
That is really weird. What I did was flash CM9, then CM10. (now I'm on paranoid android...but anyway). NFC was there, then I used the method listed in the Q&A section to load the newest version. Of course, when I went to McDonald's to use it...it failed...as it always has ( I had the Verizon Galaxy Nexus at one point). I've never seen NFC actually work for real. I don't know what it is, but maybe the people that run the businesses don't have it turned on correctly. I was really wanting to see it work too.
Hi XDA,
I'm currently running latest Flinny CM10 test build (125), and an issue I've had for a while is that even when the phone is locked, but screen is on, I can pull down the notification bar and do actions. Is this normal? Is there a setting somewhere that needs to be switched off? I am using Apex launcher.
Cheers.
As far as I know this is a standard behavior since android 4.0 (ICS). There is no settings to disable it.
Someone correct me if I’m wrong
EDIT: If you have enabled screen security (pattern, PIN, password) you should not be able to pull down the notification bar. You should be able to pull it down only with slide lock.
I enabled a simple gesture unlock and yes now I can't pull down the notification bar.
It still seems strange that this is normal behaviour.
Thanks heaps!
yup... That's normal...
I also face some issue which is the ROM could not connect to external gps device... I think that's issue exist in CM10 since have same issue with galaxy smtd...
Yeah I don't have working orientation, light or gyro sensors still. It seems like some people have this problem and others don't depending on hardware revision.
Sorry for writing sth different here but i didnt want to create a new topic, so...
I had this andromadus version on my DZ but i didnt find any pre installed camera app, anyone else who had this or do i have to reload the rom (maybe sth went wrong during downloading)
Sent from my GT-N8010
Vauvenal7 said:
Sorry for writing sth different here but i didnt want to create a new topic, so...
I had this andromadus version on my DZ but i didnt find any pre installed camera app, anyone else who had this or do i have to reload the rom (maybe sth went wrong during downloading)
Sent from my GT-N8010
Click to expand...
Click to collapse
Just wondering... Do u install gapps? If not, you should do that when u install it for the first time (after you install the rom).
Vauvenal7 said:
Sorry for writing sth different here but i didnt want to create a new topic, so...
I had this andromadus version on my DZ but i didnt find any pre installed camera app, anyone else who had this or do i have to reload the rom (maybe sth went wrong during downloading)
Sent from my GT-N8010
Click to expand...
Click to collapse
As with every CM build after 4.1.11.1 on the G1, ALWAYS FLASH GAPPS AFTER FLASHING THE ROM.
cm made a 4.2 donut where the base was flashed first still, so starting with eclair gapps where flashed after
Sent from my HTC Vision using xda premium
blackknightavalon said:
As with every CM build after 4.1.11.1 on the G1, ALWAYS FLASH GAPPS AFTER FLASHING THE ROM.
Click to expand...
Click to collapse
I did, yet ther was no camera app pre installed
Even the icon on the unlock streen existed, but when i unlocked it with the cam symbol nothing happened, it just went back to the lockscreen
I had mimicry before and therefore i got used to flash gapps, so did i with this jb rom too
Sent from my GT-N8010
I love this ROM, everything I generally use on a regular basis works fine. My only real problem is this ROM is a serious power drain, within an hour of being unplugged in the morning I have already lost 10% of the battery, by mid afternoon I am forced to plug the phone back in, this is something of an issue as I work at hospitals and plugging appliances into the mains is a violation of health and safety regulations, but I need my phone so I do what ya gotta do. Is there any way to reduce the drain from this ROM as I am fairly sure it is not any applications I have installed causing it, as none are running in the background when I check running apps.
plug it in to a computer with a logcat running, see what is going on that way. or if you aren't able to sit in front of a computer for a while watchdog is a nice app for this (keep in mind it should be for testing basis and be removed later as it to will always be running in the background)
Sent from my HTC Vision using xda premium
evernote makes phone slow
I am using this rom (build 124) and I have and after restoring all my apps it became really slow. After some try/error I found that uninstalling some apps solved the problem. After that I started installing my apps again one by one and I found installing evernote make the phone near unusable.
Anybody is experiencing this? it also happen if I install "camera 360".
I am running build 127 of this ROM which definitely seems faster than build 126 which was the first one I tried and seems to be quick enough to actually use it most of the time.
When things do go slow it seems to be when switching to a new app and seems more likely to happen is the new or old app is big.
Regarding more apps slowing things down I wonder if it is actually more widgets and background services. If this is, as I suspect, do to with how many apps can be cached in RAM for fast switching then the more apps have something running in the background, for example to sync with a cloud service or to keep a widget updated, the less RAM there will be for the apps you are trying to use and there will therefore be a greater chance the app you are trying to start has to be started from scratch.
These threads really need to stop, Flinny's test build is just that A TEST BUILD problems/issues are expected.
I think it's normal...anyway it don't obstruct me
tarroyo said:
These threads really need to stop, Flinny's test build is just that A TEST BUILD problems/issues are expected.
Click to expand...
Click to collapse
In my case I am certainly NOT contributing in order to criticise. Of course I know a test build may have issues but, like many others I suspect, I am happy to try the latest thing. When things don't work quite right it is worth discussing it. If we can understand what is happening we can help each other mitigate the issue and maybe even have something useful to feed back to developers.
I was running build 127 and things had become very slow. I have now updated to build 128 and the phone is fast again. At this stage I am not sure if this has anything to do with the new build or whether it is down to apps. I have all 45 apps installed but for many of those that sync to cloud services I have not yet got round to setting up the username/password for that to happen so this may be limiting the amount of background activity to a level where it doesn't get in the way. I'll try setting some of them up and see what happens.