Related
So I have this problem where when I am running Cyanogen Mod (currently 128 of ICS) on an R800x and the data will randomly just stop working, and the only way to fix it is to reboot the phone. Everything else appears to be working perfectly. I am running the latest firmware from that stickied thread in the developer's section. Any ideas why this is happening and how i can fix it? Btw as far as I can tell it's only the data that stops working, not sending/receiving calls/texts or wifi.
xrishox said:
So I have this problem where when I am running Cyanogen Mod (currently 128 of ICS) on an R800x and the data will randomly just stop working, and the only way to fix it is to reboot the phone. Everything else appears to be working perfectly. I am running the latest firmware from that stickied thread in the developer's section. Any ideas why this is happening and how i can fix it? Btw as far as I can tell it's only the data that stops working, not sending/receiving calls/texts or wifi.
Click to expand...
Click to collapse
Yeah, It's like that with all us cdma users. I've brought it up and fxp doesn't even acknowledge it. All you need to do is turn the mobile data off then on again. It's annoying, but until a decent dev looks into it it's the only workaround
ive tried putting it into airplane mode, and taking it back out, but that doesn't fix the problem. how do you do it?
and is there a way we can politely point this out to them, without acting completely entitled? like if its effecting all cdma users that's a pretty large group.
xrishox said:
ive tried putting it into airplane mode, and taking it back out, but that doesn't fix the problem. how do you do it?
and is there a way we can politely point this out to them, without acting completely entitled? like if its effecting all cdma users that's a pretty large group.
Click to expand...
Click to collapse
Well nobody on the fxp team has an r800x, I think two of them have gsm versions. So they can't test it out, and with my history with fxp himself he doesn't seem to really care about cdma at all (doesn't least show he does). People have mentioned it before and nothing comes from it. So it's a lack of caring about our type of issues, they don't have time, or it's beyond their comprehension. Your best bet is to mention it to Pax, since he does a lot of things for cdma. Here's a link to his profile
http://forum.xda-developers.com/member.php?u=4234200
Here is Keiran's profile also (he's on the fxp team)
http://forum.xda-developers.com/member.php?u=4344506
Oh, and the way I do it is: setttings>more..>mobile networks> Check data enabled off (wait 5sec) then check it back on. If that doesn't help then you can try a fresh install to see if it does anything
agraceful said:
Well nobody on the fxp team has an r800x, I think two of them have gsm versions. So they can't test it out, and with my history with fxp himself he doesn't seem to really care about cdma at all (doesn't least show he does). People have mentioned it before and nothing comes from it. So it's a lack of caring about our type of issues, they don't have time, or it's beyond their comprehension. Your best bet is to mention it to Pax, since he does a lot of things for cdma. Here's a link to his profile
http://forum.xda-developers.com/member.php?u=4234200
Here is Keiran's profile also (he's on the fxp team)
http://forum.xda-developers.com/member.php?u=4344506
Oh, and the way I do it is: setttings>more..>mobile networks> Check data enabled off (wait 5sec) then check it back on. If that doesn't help then you can try a fresh install to see if it does anything
Click to expand...
Click to collapse
thanks for the quick fix. worst case scenario that isn't too inconvenient of a fix. i tried sending both of them a polite message, and we'll see if anything comes of it, though probably not.
Hey,
Although I'm not on FXP team anymore (working with AOKP now <3 unicorns haha) I looked into this issue once.
Any AOSP based ROM (CM, AOKP) for zeus and zeusc use prebuilt radio interface layer libraries, which is a problem, because the ones we are using in CM9 are gingerbread, not made for ICS.
I tried reverse engineering it once but I seriously need to work more on that kinda stuff
I'll tell jerpelea (FXP) of this issue and what he wants to do about it, its not really in my power now. Although if I do find a fix then I will be sure to push it to gerrit, regardless of FXP's opinion on the issue.
J is the only one I know with an R800x (he has whole 2011 line + S + P + x10)
Hope I could be of any help,
Keiran
KeiranFTW said:
Hey,
Although I'm not on FXP team anymore (working with AOKP now <3 unicorns haha) I looked into this issue once.
Any AOSP based ROM (CM, AOKP) for zeus and zeusc use prebuilt radio interface layer libraries, which is a problem, because the ones we are using in CM9 are gingerbread, not made for ICS.
I tried reverse engineering it once but I seriously need to work more on that kinda stuff
I'll tell jerpelea (FXP) of this issue and what he wants to do about it, its not really in my power now. Although if I do find a fix then I will be sure to push it to gerrit, regardless of FXP's opinion on the issue.
J is the only one I know with an R800x (he has whole 2011 line + S + P + x10)
Hope I could be of any help,
Keiran
Click to expand...
Click to collapse
Ah ok I can see the issue now, I honestly never even considered that. I deved on gb for many years and I'm still not use to ics yet lol. I seriously thank you for responding. From what I can tell gsm users don't have this issue (maybe they do but the ones I've talked to don't) and even though it's not major to me it'd be nice to be on the same level you know? Since you're on aokp I may jump onto that soon, but thanks again Keiran, I hope you stick with developing you got a knack for it that most people don't.
I have been looking for a couple of weeks, but I can't find anything that is just this. I don't know much about development, so I wouldn't know how to take what someone else has done and modify it to how I want.
Basically, I am wanting a Paranoid Android soft key area. I want to get rid of the nav bar up top and move my clock, battery, signal, wifi, etc. to the bottom with the soft keys. That is the only change I really want to make.
I know that this is one of the premier features of Paranoid Android, but it is my understanding that PA for JB is based on CM10 and still has a lot of bugs to flesh out, especially on the CDMA/Toro version. Also, I do not know enough to figure out the tablet mode, hybrid mode, and regular mode stuff, especially since some of it is done in ADB (again, my understanding of it, I could be wrong).
Is it possible to do only what I described without flashing to PA for JB? I feel like some of the modifications I have seen posted in this forum come close to this, but the ones I remember off the top of my head move only the clock to the bottom.
Thanks to anyone who can help.
May I ask, why you dont want to flash PA? what bugs are keeping you from flashing?
I am currently running it and there are no real bugs, that irritate me (I dont use bluetooth^^)
And since a new build will be coming very soon even the toro devices should be fine aswell.
Nordpolcamper said:
May I ask, why you dont want to flash PA? what bugs are keeping you from flashing?
I am currently running it and there are no real bugs, that irritate me (I dont use bluetooth^^)
And since a new build will be coming very soon even the toro devices should be fine aswell.
Click to expand...
Click to collapse
I will definitely flash PA in the future, I would just prefer to wait until all the bugs are kicked.
First, I need to be able to be reached on my phone all day and by email (which I check 95% of on my phone) at all times. Apparently there is a problem with gmail on PA right now, as well as other smaller bugs. While I can't name any specifically that I remember, I do know the developer himself is calling it very alpha. While I love the developer-made ROMs, I also need stability, at least until the summer is over and I'm back in school.
Second, it is my understanding (I love that saying, obviously) that you have to do a full wipe each time you flash a new version of any CM-based ROM. Because I hate having to re-download and re-log into all of my apps (especially ones that need credit card numbers), I usually stay on stable ROMs that allow me to dirty flash when newer versions are released. I know there are ways around this, but I don't know enough to get around it at the moment nor do I have time to learn how to do it until school starts back up.
TexPP said:
I will definitely flash PA in the future, I would just prefer to wait until all the bugs are kicked.
First, I need to be able to be reached on my phone all day and by email (which I check 95% of on my phone) at all times. Apparently there is a problem with gmail on PA right now, as well as other smaller bugs. While I can't name any specifically that I remember, I do know the developer himself is calling it very alpha. While I love the developer-made ROMs, I also need stability, at least until the summer is over and I'm back in school.
Second, it is my understanding (I love that saying, obviously) that you have to do a full wipe each time you flash a new version of any CM-based ROM. Because I hate having to re-download and re-log into all of my apps (especially ones that need credit card numbers), I usually stay on stable ROMs that allow me to dirty flash when newer versions are released. I know there are ways around this, but I don't know enough to get around it at the moment nor do I have time to learn how to do it until school starts back up.
Click to expand...
Click to collapse
well that gmail issue is a myth^^ you can simply change the dpi to phone and everything works flawless
Furthermore moles said, that form 1.7 onwards you wont need a factory reset anymore^^
Nordpolcamper said:
well that gmail issue is a myth^^ you can simply change the dpi to phone and everything works flawless
Furthermore moles said, that form 1.7 onwards you wont need a factory reset anymore^^
Click to expand...
Click to collapse
Thanks for the info. I just sent you a PM regarding some of what I said, but I sent it before seeing this reply. I may try to jump on PA tonight if it is working better.
Hello everyone one,
I had an international HTC One X locked to the ThreeUK network (1.28). They were rubbish releasing updates namely 1.29.701.11
I get the screen flicker issue, and last night I rooted and installed Revolution HD 9.1.0 (sense 4.1) rom onto my phone.
The phone is soooo much snappier and faster, plus scores 700-800 more on antutu.
My question is, will this custom firmwire update I have done also fix the screen flicker issue and lost memory card data I was experiencing with 1.28 4.0.3??
Thanks.
New here and looking to stay
ben-fisher-bro said:
Hello everyone one,
I had an international HTC One X locked to the ThreeUK network (1.28). They were rubbish releasing updates namely 1.29.701.11
I get the screen flicker issue, and last night I rooted and installed Revolution HD 9.1.0 (sense 4.1) rom onto my phone.
The phone is soooo much snappier and faster, plus scores 700-800 more on antutu.
My question is, will this custom firmwire update I have done also fix the screen flicker issue and lost memory card data I was experiencing with 1.28 4.0.3??
Thanks.
New here and looking to stay
Click to expand...
Click to collapse
It should do, wait a couple of weeks for the screen flicker fix to fully implement.
ste1164 said:
It should do, wait a couple of weeks for the screen flicker fix to fully implement.
Click to expand...
Click to collapse
Thanks for the reply.
I'm getting conflicting reports that the screen flicker won't be fixed as I need that specific update and a custom rom will not fix it as it's more to do with the binary and not with the rom side?
Any other ideas ?
Cheers
ben-fisher-bro said:
Thanks for the reply.
I'm getting conflicting reports that the screen flicker won't be fixed as I need that specific update and a custom rom will not fix it as it's more to do with the binary and not with the rom side?
Any other ideas ?
Cheers
Click to expand...
Click to collapse
Can you reference these conflicting reports?
I firmly believe that the cusotm ROM you have will include the fix (ask the author) but it is fair to say that a few people found the fix didn't work but the majority of handsets were fixed by 1.29.xxx.11.
I cannot reference no. If I find the thread again i'll link it here.
So what's the best route of it being fixed? Maximum brightness?
farnsbarns said:
Can you reference these conflicting reports?
I firmly believe that the cusotm ROM you have will include the fix (ask the author) but it is fair to say that a few people found the fix didn't work but the majority of handsets were fixed by 1.29.xxx.11.
Click to expand...
Click to collapse
farnsbarns
Hmm, this is what I always wanted to know. Maybe you can shed light on this for me (getting ignored in custom kernel, or CM threads)
The custom kernels are made from the source right? I mean compiled?
Whats the latest one there is? Last time I was on custom kernel there was the official source only from the 0.7 version without the flicker fix.
Or is there already a new source? Or no source needed, they can just hack into the kernel without it?
Also the modded roms, they have their own kernels right? Also a new source with the flicker fix?
Also I didn't have flicker with .11 (got the phone shipped with it) and when I tested custom kernels = flickers, back to stock = no flicker.
On this OTA, it flickers, hoping it will settle, but I can already tell it was faster "fixed" for me on the .11
Maybe there was the data, which will it have to gather from new on as I am now after RUU etc.
I'm having the exact same issue on CM10. I know it's still an alpha build, so I'm willing to wait. But I've asked one of the developers directly, but he/she won't respond.
It is a big problem for some of us, yet it's being ignored. That alone doesn't sit right with me. Does that mean that it's not easy to fix or that it's not in the pipeline (yet)?
jvlmp said:
I'm having the exact same issue on CM10. I know it's still an alpha build, so I'm willing to wait. But I've asked one of the developers directly, but he/she won't respond.
It is a big problem for some of us, yet it's being ignored. That alone doesn't sit right with me. Does that mean that it's not easy to fix or that it's not in the pipeline (yet)?
Click to expand...
Click to collapse
You know, I wouldn't mind the flickering as much I am now, if someone of them would at least say something to it. Like "not possible" or "working on it" but ignoring the questions just made me abandon CM for now and I am back to stock.
PAGOT said:
You know, I wouldn't mind the flickering as much I am now, if someone of them would at least say something to it. Like "not possible" or "working on it" but ignoring the questions just made me abandon CM for now and I am back to stock.
Click to expand...
Click to collapse
I totally agree! I'm playing with the same idea of going back to the stock ROM, but I truly don't like Sense. But I ike it more than the flickering though.
jvlmp said:
I totally agree! I'm playing with the same idea of going back to the stock ROM, but I truly don't like Sense. But I ike it more than the flickering though.
Click to expand...
Click to collapse
I hate sense too . Thats why I have most of it deactivated and use Nova launcher. There is even a sense cleaner here in the forum. But I just frozen the aps I don't like. Should help a bit with deactivating most of the sense stuffs.
I would go for CM, but there were few issues, I had with it besides the flickering.
It's been a while, but did anyone have any luck in fixing the screen flickering in CM10?
I love CyanogenMod, I really do. It is constantly improving and the devs working on it obviously work very hard to keep things running smoothly. However, with a codebase this large, constant improvements inevitably leads to a fairly consistent stream of new bugs amidst the improvements. I understand that nightlies are not intended to be used as daily drivers, although usually they are stable enough for most here at XDA.
Acknowledging all of this: I can't help but wish on some days that I could take the excellent skills/care/devotion of the CyanogenMod team and have them devote a fraction of their work to create a pure, optimized AOSP ROM. No mods, no community apps, and (hopefully) no bugs. This would be an incredible stop-gap between the initial build of a new CM nightlie (say, CM11) and the inevitable stable release.
This is NOT a statement against the added mods/apps to CyanogenMod (File Manager, Apollo, DSP Manager, etc.), I am very much of the opinion that these additions are beneficial, even necessary to the growth of CyanogenMod.
I do not expect this to happen, and I especially do not expect them to go back through CM10 and line-by-line strip all of their adjustments/additions. I understand that they are all very busy at work to keep us happy, and I appreciate that. Think of this as wishful thinking from a big fan.
Am I alone in this opinion?
it is called an AOSP rom. in this case vanilla. get a nexus device for that
Obviously, but I think you're missing my point...or you didn't read my post.
ohfoxxxycole said:
create a pure, optimized AOSP ROM. No mods, no community apps, and (hopefully) no bugs.
Click to expand...
Click to collapse
A vanilla android rom with a custom kernel
Sent from my SPH-L710 using xda app-developers app
XxSilent.NightmarexX said:
A vanilla android rom with a custom kernel
Click to expand...
Click to collapse
Yes, but done by devs that know what they're doing.
Every single dev here knows what they are doing. Plus aosp is easy to compile for any device
Sent from my SPH-L710 using xda app-developers app
I don't see any after a quick search. I've used pure vanilla ROMs on my evo/evo3d and they were pretty terrible. I just assumed, by prior experience and lack of vanilla roms here, that they were tricky.
no, thats just because AOSP roms lack features that people crave from CM or AOKP
Alright, so we're back to my initial post now.
In other words an aosp pure android rom is not people look forward to. Cm10 stable rom is there and probably with like one minor bug or two.
Sent from my SPH-L710 using xda app-developers app
I know how you feel; I wish they would release a stable ROM for those that prefer stability over speed/features
EXACTLY. i love how hard the devs work to improve android and add features but until its possible to get a stable rom with these features I'd prefer simple, pure vanilla with all work going towards stability. Maybe I'll start on that one day
Sent from my SPH-L710 using xda app-developers app
ohfoxxxycole said:
EXACTLY. i love how hard the devs work to improve android and add features but until its possible to get a stable rom with these features I'd prefer simple, pure vanilla with all work going towards stability. Maybe I'll start on that one day
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
You can't ask for optimization with stability. The nightlies are there because that's what they're trying to achieve, if it's not stable enough for you - don't use it. Go back to TW. That's the closest to pure stable for this device you're going to get. There are -always- bugs, even in the most fine tuned software, because it's all about what the user puts on their devices and how it interacts with the system.
Plus, not too long ago CM released the CM10 Milestone 2. It's stable enough for daily use. Give that a shot. If it's not to your liking, pull CM's device tree into a freshly synced repo of AOSP and compile it. See how easy it is to get it working.
There are -always- bugs, even in the most fine tuned software, because it's all about what the user puts on their devices and how it interacts with the system.
Click to expand...
Click to collapse
this is true, but i'd be using this with mostly stock software + social network feeds and games only
the milestones are a great idea, and probably the closest thing im going to get to this, but they are still snapshots of mostly stable aosp with many many tweaks to keep modifications that i may or may not use stable. not exactly ideal, but thanks for the suggestion. i'll probably stick with the newest m build when it is ready.
im not asking for cms device tree compiled as it is, or anything at all. im just hoping that before or adjacent to cm11 getting going with mods and tweaks that they will release builds tailored to vanilla and nothing else, concentrating only on bugs before adding things and testing them and adding things and breaking things and testing them and so on and so forth. i feel im not communicating this efficiently and im sorry
$MyName said:
You can't ask for optimization with stability. The nightlies are there because that's what they're trying to achieve, if it's not stable enough for you - don't use it. Go back to TW. That's the closest to pure stable for this device you're going to get. There are -always- bugs, even in the most fine tuned software, because it's all about what the user puts on their devices and how it interacts with the system.
Plus, not too long ago CM released the CM10 Milestone 2. It's stable enough for daily use. Give that a shot. If it's not to your liking, pull CM's device tree into a freshly synced repo of AOSP and compile it. See how easy it is to get it working.
Click to expand...
Click to collapse
Does the bottom mic work on M2? What about the data drops that constantly happen? Does it transition well from LTE to 3G, vice versa?
And these are serious questions, I'm not trying to be a [email protected] at all.
I have a 20 month old baby girl so I do a lot of video recording, so the bottom mic is important to me since the top one doesn't pick anything up unless you're basically speaking directly into it. I do a lot of business through my phone, so a reliable data connection is obviously very important too. I've had BB6 on my phone for about a week now, and I absolutely love it...with these two exceptions. It seems they're both problems with all AOSP ROMs. If they get fixed sooner rather than later, there will be zero reason to have TW ROM for me.
EDIT: And GPS seems to take quite a bit longer to lock on compared to TW.
hayzooos said:
Does the bottom mic work on M2? What about the data drops that constantly happen? Does it transition well from LTE to 3G, vice versa?
And these are serious questions, I'm not trying to be a [email protected] at all.
I have a 20 month old baby girl so I do a lot of video recording, so the bottom mic is important to me since the top one doesn't pick anything up unless you're basically speaking directly into it. I do a lot of business through my phone, so a reliable data connection is obviously very important too. I've had BB6 on my phone for about a week now, and I absolutely love it...with these two exceptions. It seems they're both problems with all AOSP ROMs. If they get fixed sooner rather than later, there will be zero reason to have TW ROM for me.
EDIT: And GPS seems to take quite a bit longer to lock on compared to TW.
Click to expand...
Click to collapse
I was using m2 for quite a while before I switched over to bb6. In my time playing with m2 I found that video recording was fine and data connectivity took about 10 seconds longer on a reboot. Other than that I've experienced no data drops.
To add to this, YMMV. I'm not sure if my phone is different somehow but I've never had any of these problems that people describe with data drops at random.
Edit:
Also, as far as lte/3g hand off goes, I'm unable to test as I'm not in an lte area. As for GPS, it takes about 7 seconds to lock on in a room with no windows. Tested on slimbean, so again YMMV
Sent from my SPH-L710 using Tapatalk 2
Just try looking into building aosp from source its really not that hard it will just take some time. You could even use the device tree for d2spr from cm so you really will just be using pure stock
Sent from my SPH-L710 using xda app-developers app
ohfoxxxycole said:
I don't see any after a quick search. I've used pure vanilla ROMs on my evo/evo3d and they were pretty terrible. I just assumed, by prior experience and lack of vanilla roms here, that they were tricky.
Click to expand...
Click to collapse
You're clearly smoking some good crack. AOSP ROMs for the E3D are awesome right now.
Months ago
Sent from my SPH-L710 using xda app-developers app
Ok, here's my situation. I have a Verizon M8, S-OFF, unlocked, rooted, custom firmware... but running the stock VZW Lollipop+Stagefright OTA. Everything patched up to date.
I'm ready to take the plunge and try something more custom (which I've done repeatedly on other phones, so I'm not ignorant here).
The catch? I kind of like Sense. More specifically I kind of like tap-to-wake and motion gestures.
Additionally - and I know I'll catch some flak for this - I really like the Verizon Messages+ for SMS. I know I can install that on any ROM but it uses integrated services that I'm not sure what the requirements are.
So ... which ROM to try? I've been limiting my search to Sense based ROMs, but what do I lose without Sense? I don't much care about blinkfeed, TBH.
Skydragon looks really good, and seems to support VZW. S.Rom seemed nice but apparently VZW support is dead.
Who else should I consider? No matter what my priorities are battery life, audio quality (with an EQ, dear god please...) and not having to endlessly troubleshoot force closes or hangs.
Thanks in advance!
Watch out for SkyDragon. The VZW support can be flaky. I found that no matter what firmware i was on, Data would start out working, then disconnect at some point, and i could never get it working again (reboot didn't fix it)
I'm on LeeDroid with Quantum Kernel and its pretty good. Battery and speed are both fantastic.
If you're willing to try leaving Sense, try a CM rom like Resurrection.
Tap to wake is present in pretty much every ROM. The only thing you really loose for that is camera open in landscape with vol+ pressed and that is even in some aosp ROMs.
Sent from my m8wl
Thanks, guys. I'll check out LeeDroid. I am a little ... disappointed, I guess ... that the VZW support for a lot of these roms is pretty sketchy. *sigh*