I'm close to throwing myself behind a driving bus...
No matter what CM10 I try, the phone randomly locks its SIM card again and again.
Sometimes it just takes minutes, sometimes 2 hours.
No rebooting or so, it just "loses" its PIN.
Reenter and all fine...'til next time that is...
I was coming from rooted 4.0.3 stock, but now, whatever CM10 I install, same behaviour.
Be it CM10 AOSP, AOKP, vSync exp., doesn't matter.
The last one I remember to have been stable was nightly CM AOSP 21092012.
So I tried to do search, XDA...Google...answers sounded to me as if it could have been this ominous RIL thingy.
So I got myself getRIL which installed me an other RIL to my original BUKP baseband.
No help.
I read of people recommending LQ6 modem.
Installed it, added LPQ RIL.
Same ****.
Changed RIL to LQB.
But still...
Now, is there anything I have overseen?
Misunderstood?
Or is this a known issue I was not aware of?
I mean, yes, it's not an officially released FW and I wouldn't bother to deal with one bug or two, but if I can't rely on at least being available and reachable by phone, this unfortunately is a no go for me.
If at least it would wave the white flag so you knew when it happened...
So, any other help possible, folks, or do I have to revert to stock ICS?
Damn, I really love CM10, especially the latest vSync of today is running like...yeah...butter, I guess...
Lindexslp said:
I'm close to throwing myself behind a driving bus...
No matter what CM10 I try, the phone randomly locks its SIM card again and again.
Sometimes it just takes minutes, sometimes 2 hours.
No rebooting or so, it just "loses" its PIN.
Reenter and all fine...'til next time that is...
I was coming from rooted 4.0.3 stock, but now, whatever CM10 I install, same behaviour.
Be it CM10 AOSP, AOKP, vSync exp., doesn't matter.
The last one I remember to have been stable was nightly CM AOSP 21092012.
So I tried to do search, XDA...Google...answers sounded to me as if it could have been this ominous RIL thingy.
So I got myself getRIL which installed me an other RIL to my original BUKP baseband.
No help.
I read of people recommending LQ6 modem.
Installed it, added LPQ RIL.
Same ****.
Changed RIL to LQB.
But still...
Now, is there anything I have overseen?
Misunderstood?
Or is this a known issue I was not aware of?
I mean, yes, it's not an officially released FW and I wouldn't bother to deal with one bug or two, but if I can't rely on at least being available and reachable by phone, this unfortunately is a no go for me.
If at least it would wave the white flag so you knew when it happened...
So, any other help possible, folks, or do I have to revert to stock ICS?
Damn, I really love CM10, especially the latest vSync of today is running like...yeah...butter, I guess...
Click to expand...
Click to collapse
Flash another kernel!
Jokesy said:
Flash another kernel!
Click to expand...
Click to collapse
Thanx!
Ok...true, this would explain why my 21092012 nightly didn't have that problem - I had used the Siyah kernel with it back then.
This would mean to reintroduce the mem leak for now as far as I understand which is at least better because you know when the necessary reboot happens.
I'll give it a try, especially as the mem leak should be fixed in one of the next builds, I guess.
Thanx again for your help!
Lindex
Related
The dreaded face unlock bug. I have been experiencing this for several days now, on and off with no particular rhyme or reason. I'll explain the bug. I press the power key to enable the phone, after 2 or 3 seconds the camera comes on, this is where is gets sticky. Sometimes it does not recognize me (like if I have my glasses on, or a hat) and gives me the keyboard to enter the pin. Other times it just dies, picture still on the screen, no combination of buttons unfreezes the phone, I have to yank the battery and start all over again.
I am rooted running Phone Bricker 2.1, stock kernel, and everything else, although I was going to try a different modem, apparently in my area a different modem works better.
I've seen numerous posts on the international version of our phone but nothing for the I-777, do I have a phone problem, or is this just an expected errata from running 'leaked' software?
Also are there any fixes anyone is aware of? I love the face unlock feature and I guess I could disable it.
One clue that might shed some light on the subject, as soon as I unlock my phone, if I use the pull down menu and mess with Wifi at all, the phone all but dies. It does recover but it takes awhile.
Thanks for any insight or a link I missed.
And happy Easter!
Wink
Phone-Bricker is not based on the leak, its from i9100 LP3 (o2 carrier) base.
Not sure what the face unlock bug is but I tried it before without any problems.
Try using Entropy's latest kernel named Zombie Ass!
I am running Phone Bricker and also use the Face Unlock feature, with no problems whatsoever. But then, I've only had my phone since Friday.
Sent from my SGH-I777 using xda premium
LiLChris06 said:
Phone-Bricker is not based on the leak, its from i9100 LP3 (o2 carrier) base.
Not sure what the face unlock bug is but I tried it before without any problems.
Try using Entropy's latest kernel named Zombie Ass!
Click to expand...
Click to collapse
I was able to find the Kernel, thanks again.
Thank you my friend.
Wink
Were you over/under clocking?
I don't think the ICS kernels support that. I would get the same problem with the slide unlock screen, and all I did was change the governor, using the stock frequencies.
Sent from my Galaxy S II (i777)
Well I had SetCPU installled, but the Kernel does not support overclocking so I saw no need for the application and removed it.
I started from scratch, I did a factory wipe/ cleared Dalvik cache and reinstalled the ROM, both versions 2.0.1 and 2.1, also the mail fix. I installed the modem that shows the best performance where I live now, and also installed Entropy's new Kernel (again at least from a cursory look it maxxes out at 1.2 GHz)
I'll know more after today, I'll post here tonight after work and we'll see how things are going now.
Wink
Well face unlock seemed to work perfectly, i'll chock it up to some strange code bug.
Odd thing my mic out would not work all day, however connected to headphones here at home it's working fine. I guess it could be the radio at work or a co-worker who is sick of my music who borked it so I can't use my phone as an MP3 player.
Overall I gotta say I am extremely happy.
Thanks all for your help!
Wink
Great thread title.
Thread title added.
I noticed I omitted it and tried to add it after the fact....
No such luck, sorry.
Hi LiLChris06 - Is the face unlock an app? If so do you think it would work on your gingerbread 2.3.6 rom?
Thanks
superdog404
superdog404 said:
Hi LiLChris06 - Is the face unlock an app? If so do you think it would work on your gingerbread 2.3.6 rom?
Thanks
superdog404
Click to expand...
Click to collapse
Doubt it would work, its meant for ICS.
I have no audio on calls on Jelly bean. Ive tried switching roms to different Jelly bean roms and no difference. This is so annyoing cause I can not call or receive calls! Any solutions??
I had this happen to me. I called at&t and they disconnected and reconnected my phone to the local tower and it started working fine again.
I get the same problems using a couple roms on here...I get reboots..then when comes back on I have no data..or someone will call and I can hear thrm but they cannot hear me....I found just rebooting fixes this...but I'm starting to hate JB right now...lol
If this solved the problem please respond and add [SOLVED] to the thread title so others with the same problem can benefit
I have the exact same problem with CM10, and it started with an old nightly, then I upgraded to the latest nightly and its still occuring. Anyone know whats going on, I don't want to go back to CM9
Rebooting is not fixing it.
Yarbo said:
I have the exact same problem with CM10, and it started with an old nightly, then I upgraded to the latest nightly and its still occuring. Anyone know whats going on, I don't want to go back to CM9
Rebooting is not fixing it.
Click to expand...
Click to collapse
Try a re flash. That was the only way I corrected this issue when I was running JB. I'm on ICS now and all issues have gone away. Soon, JB will be that way too. Until then though....
Sent from one bad ass, highly modified, Samsung Galaxy Note running Novena A3 using the BEST in mobile apps, XDA-Developers!
Until official jb source drops for our phone this will be a problem on ALL job roms . It seems to affect some more than others. For me, this happened less often than for most. However, it always happened at the worst times.. I am currently using the ICS based 7005 ROM with Google now and 4.2 camera flashed after the fact and find it to be an excellent compromise. 100% stability with 95% of the feature set and buttery smoothness.
I can't wait to see what PTMR3 does with padawan on this base....or better yet what manelscout4life brings us with official jellybean code..
On every Jellybean rom, I have calling issues. On some roms, call audio wont work. On the rom I just flashed, it would not make or receive calls all together. Also, this happens only after a certain period of time. And it goes from sporadic occurances to permanent. It takes about a day or two for these issues to start appearing. This is so god damn frustrating because in the beginning the rom works perfectly, I spend all my time setting it up, and then a day or so later, I get these issues that make the phone completely unusable. Its absolutely ridiculous, and If anyone has any ideas, please please let me know. I love the JB roms but they all seem to make my phone unusable after a short time.
Please help....
JB roms are still a work in progress. And your problems could be caused/made worse by your setup (apps, widgets, tweaks, etc...). If you are using different kernels/radio, it can also contribute to problems. There are just too many variables.
My answer : use an ICS rom. ICS roms are alot more stable on our phone right now.
H0rn3t920 said:
On every Jellybean rom, I have calling issues. On some roms, call audio wont work. On the rom I just flashed, it would not make or receive calls all together. Also, this happens only after a certain period of time. And it goes from sporadic occurances to permanent. It takes about a day or two for these issues to start appearing. This is so god damn frustrating because in the beginning the rom works perfectly, I spend all my time setting it up, and then a day or so later, I get these issues that make the phone completely unusable. Its absolutely ridiculous, and If anyone has any ideas, please please let me know. I love the JB roms but they all seem to make my phone unusable after a short time.
Please help....
Click to expand...
Click to collapse
I am observing similar issues. I didn't used to happen before. I mean it did happen but it was a rare thing. But now it is more often. Almost everyday I have to reflash because of loosing phone audio.
I was rocking AOCP 3.1 , Worked really sweet and then decided to update to go for AOCP 4.1 and since then no rom that I tried have saved me. In fact I had to revert back to stock. What rom are you using?
People, it's a known issue on all JB Roms.
Don't open a thread about it.
xaragen said:
I am observing similar issues. I didn't used to happen before. I mean it did happen but it was a rare thing. But now it is more often. Almost everyday I have to reflash because of loosing phone audio.
I was rocking AOCP 3.1 , Worked really sweet and then decided to update to go for AOCP 4.1 and since then no rom that I tried have saved me. In fact I had to revert back to stock. What rom are you using?
Click to expand...
Click to collapse
I have the exact same issue now, It doesnt look like any rom is saving me right now.. my phone wont make calls or receive texts at all. I was running cookies and cream 4.1.2 and everytime i flash a JB rom it just seems to get worse and worse...
EDIT: I got it back on ICS. I guess I will just have to wait to use any JB roms... its unfortunate cause I love the JB roms hahaha
I have had issues with JB as well. I, just like the OP, would experience a perfectly working phone for a day or two then **** would hit the fan for no apparent reason. The phone would start locking up, randomly rebooting, apps would fail or not load, etc etc etc.
On most ROM's I didn't even have anything installed outside of the stock apps that CAME with the ROM.
Since then I have moved to a deoxed stock ICS ROM and honestly am not looking back. ICS is fast, stable, feature packed, and JUST WORKS.
My thing with JB was it's speed...but I was also comparing a barebones JB to the stock Gingerbread that came with the phone. I wasn't aware of how fast ICS was or I would have just gone with it long before hand!
But yeah, either way it goes, for me, no matter the ROM, JB always seemed to mess up at one point or another. Got annoying. Been going with ICS for over a week now with ZERO issues what so ever. No reboots, no crashes, no freezing, no nothing.
NEVERMIND..... ICS worked for one call, and now no calls work... great....
ICS roms are very stable.
You may have flashed your rom/kernel/radio incorrectly, or made some tweaks, or installed incompatible apps... There are too many variables.
Revert back to completely stock setup and see if the problems persist.
H0rn3t920 said:
NEVERMIND..... ICS worked for one call, and now no calls work... great....
Click to expand...
Click to collapse
I'll take a stab, what gapps? Do you use a call blocker of any kind?
Sent from my Samsung-SGH-I717 using xda premium
Same. I think it's the same for a lot of people, and I think the ones who say things run great either ignore the problems or are just extremely lucky.
Switch to Padawan. It's rock solid and you get all the fanciness of jelly bean. Since switching to it I've completely lost the itch to try out random JB ROMs. I have cool animations, Google Now, and ICS Browser+. And until I rebooted earlier to mess with stuff, I was at 142 hours uptime without any problems.
I'm not calling anyone a liar, though. I just think some people ignore more or are, as stated, lucky. I've done wiped everything, went back and wiped stuff post ROM, ran 3rd party (3rd ROM party) kernels and the ones that come with it. I've set cron to fix permissions on boot. And other than gapps -- which I always flash what the dev says to -- I run about ten 3rd party apps, and that's mostly made up of solid apps -- dropbox, exdialer, ics browser+.. etc..
Padawan, or even Nebula.
These ROMs are by the same dev, and the only difference is that Nebula is based off of Canadian version, which has even less bloat. It is better than stock.
I have been on Nebula for about a week, and no random reboots, no lockup, no phone problems. Everything just works.
ddochi11 said:
Padawan, or even Nebula.
These ROMs are by the same dev, and the only difference is that Nebula is based off of Canadian version, which has even less bloat. It is better than stock.
I have been on Nebula for about a week, and no random reboots, no lockup, no phone problems. Everything just works.
Click to expand...
Click to collapse
I like padawan, and Im on it now. But i still am getting this random issue where calls do not go through. Its so aggravating that Im about to smash my phone against the wall. Its happening all the time now and when I need to make a call, I cant. god damnit
have you flashed the most recent modem?
Yes, that was my next question.
Have you at any point flashed a different kernel/radio/modem? If you have, or if you do not know, search for stock kernel/radio/modem and flash them to see if it helps.
yes, uclf6 modem but eventually it just gives out.. idk what the issue is here everything works fine for a few days and out of the blue when I need my phone i cant receive or make calls anymore its INFURIATING
yes, uclf6 modem but eventually it just gives out.. idk what the issue is here everything works fine for a few days and out of the blue when I need my phone i cant receive or make calls anymore its INFURIATING
Revert back to complete stock and see if the issue still exists.
Mobile Network Type
Ltilt2 said:
People, it's a known issue on all JB Roms.
Don't open a thread about it.
Click to expand...
Click to collapse
I have had a similar issue with the JB rom's...so far I've tried only two and seem to find the aokp_quicyatt_jb_milestone-1 rom. I have noticed issues with my phone and LTE network coverage...meaning, I can see the signal go from 4G LTE to 3G to H, then gone...I looked at the phone status settings and noticed the mobile network type with this rom is LTE:13 and with the stock ICS rom (prior to rooting and flashing) it was LTE:14...is there a way that I can change it via terminal? Thank you in advance for any help on this. The one big difference I can see so far is the battery life...much better. Any help is greatly appreciated.
Issues are known....Thread Closed & Thank You.
Hi guys... I'm trying to solve a problem with my Vibrant, CM10 works except it doesn't give me data connection. But first I have to tell you a bit of a backstory
So, a couple of months ago I was a Vibrant CM9 user, never been able to solve the data problem with CM10 so I stick w/ 9. Then I decided to sell my phone and I put up an annuncment saying the phone has this and that and that and it comes with ICS.
Then CM9 for Vibrant disappeared from CM site (never understood why) and I couldn't sell my device with a ROM that was not supported anymore. I found a buyer and told him that actually I wasn't able to give him the phone w/ ICS and he was fine with it, so I sold the phone.
Now he just called me and said that the CM7 was draining is battery in 4h (never happened to me) and so he had someone installing another ICS custom ROM (he doesn't know which one) but it is buggy and bla bla bla and he asked for my help.
I don't want to ignore him, I was the one who kinda dropped the ball in the first place not giving him what I promised, and the easiest, quickest and better way to help him would be to having him install CM10 and solve the data connection thing. Another easy way would be to get a CM9 zip, but there must have been a reason for them to remove it... right?
Why all the story? To tell you that now I have to fix a problem on a device that I don't have with me
Now I explained everything to him and instructed him to install CM10, and I'm waiting to hear back from him.
I live in Italy and I have a minor carrier, he has one of the big ones... I was hoping that that alone could solve the problem, but most likely it doesn't matter at all.
Any suggestions?
Thank you a lot in advance.
Flashing any Jelly Bean ROM on one of the Vibrants I have with no SIM card installed will yield no cell data when the card is put back in.
Flash the same ROM with the SIM card in and cell data comes up perfect.
If you're flashing with the SIM card out it might be worth trying with it back in...
The other Vibrant I have doesn't care at all if the card is in or out.
Thank you for your help, I don't believe this applies to the Vibrant that I had, but I'll remember it and I'll try to put the sim in and out or something. The guy didn't reply to me yet... we'll see.
In the mean time any other thoughts are welcome
CM7 should NOT be used. Ideally you should run CM10 or CM10.1 to make sure you have the best E911 experience.
Has he tried flashing CM10 maybe it'll work with his SIM card or however he does it.
FaultException said:
CM7 should NOT be used.
Click to expand...
Click to collapse
Did you mean CM9? Because of the EU Bug? Or what is wrong with CM7?
Anyway E911 is not important because in Europe the universal emergency number is that uses the E911 system is 112, but here in Italy we are retarded and we didn't implemented it yet. Seems like it's a work-in-progress thing, but it's complicated because in Italy 112 has always been another emergency number (carabinieri answer to it)... and also because we are retarded.
Marlon90 said:
Did you mean CM9? Because of the EU Bug? Or what is wrong with CM7?
Anyway E911 is not important because in Europe the universal emergency number is that uses the E911 system is 112, but here in Italy we are retarded and we didn't implemented it yet. Seems like it's a work-in-progress thing, but it's complicated because in Italy 112 has always been another emergency number (carabinieri answer to it)... and also because we are retarded.
Click to expand...
Click to collapse
CM7 and probably part of CM9 had intermittent issues so latest CM10 is best.
same here
FaultException said:
CM7 and probably part of CM9 had intermittent issues so latest CM10 is best.
Click to expand...
Click to collapse
I used for a while the CM9 on sensation xe and had no issues with data connection. After moving to the CM10 (CM version= 10-20130119-EXPERIMENTAL-pyramid) I'm now having that problem. The WIFI works great but no data connection on the mobile network. I tried rebooting, wiping cach/dalvik cach, reset network to default settings...nothing worked for me.
any help!
Hi all,
I have an AT&T Galaxy SII (I777) which as everyone knows has the unsupported un-open Exynos4 chipset. I am currently on CM 9.1, which I like and is pretty stable for me.
I've been watching the nightlies in the CM10, CM10.1 and now CM10.2 threads hoping to see some sort of M or RC release. I think at some point, we were close to having an RC, but I guess the decision was changed.
As you might expect, I am looking for a daily driver build that is stable because I don't have as much time now as before to flash on a daily, weekly or even monthly basis, but I would like to get close to the cutting edge of software.
I noticed that AOKP has released jb-mr1 Milestone 1 back in April 2013 for the Samsung Galaxy S2 (i9100 INTL Exynos) (I777 ported by Task650). Then Milestone 2 in July 2013 (with I777 ports). So I am very interested in this.
My question/confusion: How is it possible that somewhat stable (i.e. milestone build) AOKP is available for i9100 when we haven't had anything but nightlies by CM. I thought AOKP is partly based on CM. Have they been able to fix certain things that the CM team couldn't? Or have they decided to have milestone builds despite some known bugs/issues? Can these AOKP builds (and their counterpart I777 ports) be considered daily drivers?
Thanks in advance!
I find most of the roms I have run are suitable for a daily driver. I am a flashaholic. I tend to change my daily driver monthly if not bimonthly. Task's rom is a good one. Of late I have been running Carbon, and it runs pretty well with the included kernel. I have ran Pacrom in the past as a daily, and performed pretty well too. I find with most of the 4.2.2 roms I like the STI kernel for better battery life. I really like the 4.2.2 interface. There is no reason not to try it out. I don't have any issues with any of the features I use on a daily basis ie Bluetooth, wifi, gps, and mobile data all seem to work nicely on the roms I have used. If something starts acting wonky a simple reboot fixes any problems.
Butchr said:
I find most of the roms I have run are suitable for a daily driver. I am a flashaholic. I tend to change my daily driver monthly if not bimonthly. Task's rom is a good one. Of late I have been running Carbon, and it runs pretty well with the included kernel. I have ran Pacrom in the past as a daily, and performed pretty well too. I find with most of the 4.2.2 roms I like the STI kernel for better battery life. I really like the 4.2.2 interface. There is no reason not to try it out. I don't have any issues with any of the features I use on a daily basis ie Bluetooth, wifi, gps, and mobile data all seem to work nicely on the roms I have used. If something starts acting wonky a simple reboot fixes any problems.
Click to expand...
Click to collapse
I agree. I went from task ics to sho stock jb and i can tell that is by far, imo, the most stable rom. But it is 4.1.2, now mr cook has the official att version moded and seems to be good. I've been on pac man for about 4 months now with sti kernel and it's been great. Don't update always to the latest build because nothing is broken for me. I agree with butcher, try it out and you will see.
Sent from the second to last Galaxy
PACman Rom 23.0
STI kernel 2.38
Hi guys,
Thanks a lot for the recommendations.
This past weekend I started by flashing Task650's AOKP ROM. It seemed awesome at first, but then I ran into the following annoying issues which were non-issues with my previous CM 9.1 ROM:
I am unable to turn ring or notification vibrate off even though I uncheck all the boxes I am aware of.
Battery life *feels* worse than CM 9.1. Also, I sometimes get the sudden drop in battery percentage on phone reboot, even though I re-calibrated the battery by discharging and charging it fully.
Voice dialer using Bluetooth doesn't work/ gets stuck at Start up. It also freezes with Google Search. Seems to be a known JB issue so I am very surprised. This functionality is critical as I commute 2 hours and it's safer for me to use the Voice Dialer for calls.
Audio defaults to Bluetooth when I have both my headphone jack and Bluetooth connected. I have to unplug my headphones and plug them again to get the sound re-routed to the headphones. With CM 9.1, it always defaulted to the headphones.
I think I will try PACman next because at least I see it at RC1, which gives an indication of some sort of stability. I hope the above issues are fixed.
As a last resort, I would probably go to Shostock3.
The battery going from somewhere under fifty percent down to the teens on reboot is a known issue for any jellybean rom. I found the battery on Tasks rom not so great as well. Flashing Sti kernel helped mine drastically. Never had all the Bluetooth problems everyone else complains about. I mean sometimes it was a little wonky, but a simple phone reboot always took care of any issue with my Bluetooth. Granted I only use it once a week or so with my LG headset when I mow the grass. I am waiting on Pac to release 4.3 for our phone before I flash back to Pac.
Thanks for your reply, Butchr.
A couple of nights ago was an interesting night for me. I was already on Task's AOKP and I decided to give PAC a shot. After copying the ROM's ZIP to my internal SD card and formatting system, the flash failed because it couldn't identify my phone as an I777. So I had to comment out the first lines of the updater scripts in order to bypass the check. However, I didn't have a way to push the updated ZIP file over to the internal SD card. I tried adb but it didn't work in recovery. Also, USB mounting in recovery doesn't work, at least not with Windows.
After a couple of hours, I wound up having to flash creepyncrawly's rooted 4.0.4 build using Odin. From there, I put PAC. It seemed awesome at first. Unfortunately, it had the exact same problem with Bluetooth that is affecting 4.2.2--bluetooth audio works fine, but bluetooth dialing causes the Voice Dialer or the Google Search to hang up at startup and fail initialization. It would be awesome if this is fixed in the last build, even though it seems like a Jelly Bean issue.
Immediately afterwards, I jumped on SHOstock's 4.1.2 ROM. Here are my thoughts:
- Not a big fan of touchwiz, but it's a little better than the Gingerbread days.
- I also don't like the notification panel because it's just packed with things, not leaving enough space for the actual notification. Could be a little more compact. Even after removing the brightness adjustment section. Cannot get rid of all the quick settings buttons.
- Another thing was when I downloaded Google maps, it always force-closed when attempting to start navigation. I had to uninstall it and download the APK for the latest version of Google Maps (with the interface changes). That worked fine.
- GPS locks very quickly.
- Battery life is awesome.
- No Bluetooth dialing issue. Had to use Google Search because Voice Dialer is not packaged in it.
- There is a known issue with notification sounds sometimes getting cut off. My first alarm this morning got cut off very quickly that I didn't wake up, but the first snooze alarm was fine, and that's when I woke up (10 minutes late).
I am interested in PAC if the bluetooth problem is fixed.