Anybody else think that yakju has more bugs than yakjuux???
They are technically the same. Besides, even if there are bugs you would most likely get fixes faster on yakju as updates come directly from Google whereas yakju** all receive updates from Samsung which come weeks later.
Any way to switch from one to another?
Many thanks.
franzfume said:
Any way to switch from one to another?
Many thanks.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1391881
I noticed as soon as i have changed to yanju the 4.0.2 update came that i find more force stops, more features not working and suddenly getting fixed.Anyway i hope Google dont mess up and continue developing the awesome ICS.
I have not seen anything on CMAS alerts (US only) on the Galaxy Nexus. I know I do not currently receive them on 4.0.4 VZW (though on my mom's phone she got it on Gingerbread with an app).
Does Jelly Bean add CMAS alert support or not?
RaymieHumbert said:
I have not seen anything on CMAS alerts (US only) on the Galaxy Nexus. I know I do not currently receive them on 4.0.4 VZW (though on my mom's phone she got it on Gingerbread with an app).
Does Jelly Bean add CMAS alert support or not?
Click to expand...
Click to collapse
I have Jelly Bean build JRO03O on my VZW Galaxy Nexus and it supports CMAS.
Just curious, what is the CMAS that you are talking about?
Beamed from my Maguro
Hello, Im new on this forum as I just bought a Smasung Galaxy Nexus to use as a testing device for the Linux on Android Project. It is running stock jelleybean 4.1 and is Verizon 4G LTE version. However every now and then on the lockscreen it just completely locks up and i have to push on the backing or wait it out fo it to work again (I am not sure which one actually ade it work again). It does this 1 to 2 times a day and is relitivley annoying. Is this a bug with Jellybean or should I send it to Samsung for repair? Any help would be greatly appreciated. Thanks!
Ok sorry guys if this has already been answered I checked only the Galaxy Nexus forums because it's the only device I have and I haven't heard of anyone else having my problem yet. I've searched Google as well but I've couldn't find an answer to my question so I came here. Maybe I'm not wording the question correctly. Let me give a little background.
I'm using a Stock 32Gig Verizon Galaxy Nexus 4.1 Device. I'm not rooted. So I noticed that one of the features of 4.1 Jelly Bean was the nice expandable notifications in the notification bar with the ability to respond to the text,emails, & Facebook posts directly from the notification bar.
However I can't respond to anything. The only thing it allows me to do is to collapse or un-collapse the text,email, etc. Anyone know if I've done something wrong or was this feature removed from 4.1 Jelly Bean or from the Verizon version of the Nexus? The latter definitely would not surprise me. Thanks
I have a Fido Samsung Galaxy S III that is running CM10 stable.
The caller ID I receive on the phone are all scrambled letters, like they're corrupted. For example, someone's caller ID will be AJ#*%*#$JF
How do I fix this problem? I've flashed the latest modem available for the Canadian region but this did not fix the problem
Rogers S3 Caller ID Garbled
I'm having the same problem but with the following phone:
Rogers Samsung S3
Baseband: I747MUMLL1
CM 10.1 Nightly
K747 Kernel 3.0.62 (Feb 8/13)
Android Version 4.2
I've been having the issue ever since I started using custom ROM's. If the contact is in my contacts it shows fine, but if it's not in my contacts then it shows garbled information for the NAME, the number shows fine.
Does anyone have a solution or even any thoughts on how to fix this?
Rogers S3 Caller ID Garbled
I am also having the same issue. My phone details are below:
Model: Samsung SGH-I747 (Rogers)
Android Version: 4.2.2
Kernel: 3.4.45-cyanogenmod-g23e3784 [email protected] #1 Fri May 31 14:53:30 PDT 2013
Cyanogenmod Version: 10.1.0-RC4-d2att
Has anyone determined a resolution for this?
Thanks,
This is a known issue with CM10.1 as well as any roms based on CM10.1. CM 10.0 included.
I've tried all of the 'M' modems to see which ones work for call display and this is what I found.
Working Call Display
VLLH1
LALH1
LJ1
LE8
Call Display Garbled
LK3
LK4
LL1
There is an open JIRA report on the issue. https://jira.cyanogenmod.org/browse/CYAN-1202 Not sure when or if this will be fixed. For now, just try one of the ICS modems that I listed above as working.
This does not apply to any ROMs that do not support CNAP. Call display on anything CM or CM based however should work by going back to an older modem as this ROM does support Name Call Display at least when using ICS modems.
On a side note, if you want to help generate some interest on this bug and hopefully get it resolved. Sign up on JIRA and click "Vote" to vote for the issue. No need to comment or say you are seeing the same thing. A simple vote works great.
Cm10.1 RC5 has fixed the garbled Call Display Name when using the LK3, LK4 and LL1 modems for us Rogers/Fido users. No need to use an ICS based modem just to get this to work.
flexfulton said:
Cm10.1 RC5 has fixed the garbled Call Display Name when using the LK3, LK4 and LL1 modems for us Rogers/Fido users. No need to use an ICS based modem just to get this to work.
Click to expand...
Click to collapse
Hey folks,
this issue has resurfaced for me in the 10.1 nightlies. Can anyone else confirm?
Also, wonder if anyone knows what fixed it, as I would like to suggest the fix be re-implemented...
treadlightly said:
Hey folks,
this issue has resurfaced for me in the 10.1 nightlies. Can anyonyou lse confirm?
Also, wonder if anyone knows what fixed it, as I would like to suggest the fix be re-implemented...
Click to expand...
Click to collapse
Everything is still okay for me. Currently on today's release of CMs nightly. Running MF1 modem.
I have the same issue with caller ID bad scrambled on Samsung S2 i727 with Fideo/Rogers network using CM10.1 to CM11
Roger's / Fido Name Display CallerID CNAP / CNAM issue
Issue exists at nearly the end of 2015. From what I remember it worked on and off randomly and suddenly then just does not work no matter which CM or AOSP base ROM I flash now. Only on their crappy stock ROM it works. This means Roger's / Fido are screwing up something and refusing to accept it. Whatever they are doing is probably not a standard technology. Someone told me it works for them on Telus. So I will need more people to confirm this before I go at Roger's full speed and let them know what the deal is. Personally, I think Roger's are breaking rules to get people to use their Phones and their Software rather than buying cheaper used unbranded / unlocked devices. They don't like that. Also, I wasted hours of my life to find details from them, and they know about as much as a Cat knows about the solar system. So I say call and just keep complaining and tell them what they are doing is not standard. (Because I remember it used to work).
Thanks!
TeckieD said:
I have the same issue with caller ID bad scrambled on Samsung S2 i727 with Fideo/Rogers network using CM10.1 to CM11
Click to expand...
Click to collapse
Rogers / Fido call ID altogether absent on CM13 / skyrocket
I'm good and tired of the lack of caller ID on Fido, and the wife really likes her SGH-i727r. My current feeling is that the chance of getting any intelligible information from Fido / Rogers on this topic is of the same order of the cat versus the universe that you alluded to..,. Unless by fortune, some technical person on the inside (Rogers/Fido) belongs to xda-dev?
With the above in mind, putting on my reverse engineer's hat, do you have any good hints of how to go about getting into the nuts and bolts of 1. obtaining raw caller ID data from the phone, and 2. examining the code in CM that is relevant to processing same? Or pointers to individuals who might be able to dispense the necessary hints and entry points?
Regards,
Tim
Thanks for your response. I thought it was just me and a couple other people but after my numerous posts around the web, I'm beginning to see that I'm not alone.
I got it working half assed like I mentioned in a couple of my posts but the issue is due to our Custom ROMS, ie, Cyanogenmod, AOSP, AOKP, etc etc. They all have this problem.
Also, they don't make use of Sim toolkit, there are no CSC in custom Roms, and they also don't contain some of the Framework required to make this feature work with the RIL in our phones. Those frameworks are proprietary and cannot be ported to Cyanogenmod or Custom ROMS which are based on Android.
Android by itself is just a shell on top of the kernel. To get specific features working with the hardware properly, the Manufacturer provides the Code needed to get Carrier ROMS working with their respective services. So unless Google puts this Standard functionality in their Source, we will never get a fix and Cyanogenmod is certainly not going to fix it. But because it is open source, many developers are able to realize that lots of features do not work, sometimes they can fix them, sometimes they cannot.
Your best bet is to do what I ended up doing if you intend to use your device as a Phone and not a mini entertainment computer. I went back to Stock ROM, Amped up its security to the best of my knowledge to protect from Stagefright type stuff,while I keep other devices around for GPS, Music, etc, running on CM 13.1.
Also, with newer phones coming out, they are becoming decent enough that CM and AOSP based ROMS are hardly needed anymore anyway.
If you want more control over your device, make sure that it comes with an Unlocked Bootloader to begin with. Do research before you buy. This way you will never have to deal with these issues. Good luck Tim.
tim.ishimuni said:
I'm good and tired of the lack of caller ID on Fido, and the wife really likes her SGH-i727r. My current feeling is that the chance of getting any intelligible information from Fido / Rogers on this topic is of the same order of the cat versus the universe that you alluded to..,. Unless by fortune, some technical person on the inside (Rogers/Fido) belongs to xda-dev?
With the above in mind, putting on my reverse engineer's hat, do you have any good hints of how to go about getting into the nuts and bolts of 1. obtaining raw caller ID data from the phone, and 2. examining the code in CM that is relevant to processing same? Or pointers to individuals who might be able to dispense the necessary hints and entry points?
Regards,
Tim
Click to expand...
Click to collapse