Post Reply

[ROM][4.2.2][NIGHTLIES] CyanogenMod 10.1 for HTC One XL

OP h8rift

11th January 2013, 03:58 PM   |  #471  
Senior Member
Thanks Meter: 21
 
273 posts
Join Date:Joined: Oct 2007
More
Quote:
Originally Posted by davis7198

For the past two days I have had a weird bug happening. I set up the hardware keys for long press home to open Google Now and the app switch for opening options. For most of the day it works as planned but for the past two days it seems at random that the buttons change and just tapping home opens google now and tapping the app switcher opens up the app switcher. Has anyone else ran into this problem?

I've had this exact problem happen a few times. I ended up just turning off the 'hardware keys' customization entirely.
11th January 2013, 04:58 PM   |  #472  
alejobog's Avatar
Senior Member
Thanks Meter: 67
 
579 posts
Join Date:Joined: Nov 2008
More
Update android 4.2.2 Jelly Beam !


http://pocketnow.com/2013/01/11/android-4_2_2-nexus-4


Cyanogenmod started working with the new version?
11th January 2013, 05:47 PM   |  #473  
subarudroid's Avatar
Senior Member
Flag SL,UT
Thanks Meter: 661
 
1,429 posts
Join Date:Joined: Jun 2011
Donate to Me
More
Quote:
Originally Posted by davis7198

For the past two days I have had a weird bug happening. I set up the hardware keys for long press home to open Google Now and the app switch for opening options. For most of the day it works as planned but for the past two days it seems at random that the buttons change and just tapping home opens google now and tapping the app switcher opens up the app switcher. Has anyone else ran into this problem?

+1 the short press is functioning as long press. Reboot fixes. We should create a new issue in the issues list. However we might want to wait till the next build with kernel changes? See how the next one settles.

Sent from my HOX w/CM10.1
11th January 2013, 05:50 PM   |  #474  
lauterm's Avatar
Senior Member
Thanks Meter: 237
 
652 posts
Join Date:Joined: Apr 2011
More
Quote:
Originally Posted by alejobog

Update android 4.2.2 Jelly Beam !


http://pocketnow.com/2013/01/11/android-4_2_2-nexus-4


Cyanogenmod started working with the new version?

Source has to be released through the Android Open Source Project for CyanogenMod to be able to do anything with it.
11th January 2013, 06:26 PM   |  #475  
Junior Member
Thanks Meter: 2
 
10 posts
Join Date:Joined: Jan 2007
I seem to recall that for CM10, to retain LTE access in Rogers and AT&T, you needed to start with a 4.0.x HTC ROM. Is that still the case with CM10.1?

I am wondering (complete conjecture) whether the GPS dropouts are due to some sort of mismatch conflict between the RIL's?
The Following User Says Thank You to lschen For This Useful Post: [ View ]
11th January 2013, 06:56 PM   |  #476  
Senior Member
Flag Azusa
Thanks Meter: 14
 
205 posts
Join Date:Joined: May 2007
More
Quote:
Originally Posted by h8rift

Sorry to post this later than expected. Looks like we got it working shortly after my last post about it last night. Gotta do some other testing and such for some kernel updates (not related) and chase these other gerrit changes to approval (still....).

Should be putting a build together for everyone soon.

Will bluetooth still be using this update https://github.com/cyanogenmod/andro...d705688412746c I have not been able to use any ROM since the last experimental CM10 that update really screwed my bluetooth quality with distortion. At this point if it doesn't get reverted I am gonna have to either buy a new car stereo, start a bounty for someone to modify that specific setting on newer builds, or sell the phone which I really don't want to do. Please can I get a yay or nay on whether you care to fix this or not so I can move on?
Last edited by P_Dub_S; 11th January 2013 at 06:59 PM.
11th January 2013, 09:35 PM   |  #477  
xfinrodx's Avatar
Senior Member
Flag Spokane
Thanks Meter: 76
 
360 posts
Join Date:Joined: Jul 2010
More
Quote:
Originally Posted by P_Dub_S

Will bluetooth still be using this update https://github.com/cyanogenmod/andro...d705688412746c I have not been able to use any ROM since the last experimental CM10 that update really screwed my bluetooth quality with distortion. At this point if it doesn't get reverted I am gonna have to either buy a new car stereo, start a bounty for someone to modify that specific setting on newer builds, or sell the phone which I really don't want to do. Please can I get a yay or nay on whether you care to fix this or not so I can move on?

Why don't you just go back to a different ROM? No shame in that. Find something that works and stick with it or deal with the rough ride of progress (or learn and help the progress)! Either of those options are good, but nobody really cares about whether you buy a new car stereo. Fix it yourself, comment on/file a relevant bug, deal with it, or try another ROM. I see no other productive alternative... Surely the CyanogenMod team "care(s) to fix" all issues in their distribution - the challenges of time, manpower and distributed knowledge make this a utopian goal, however. Contribute or leech, just don't complain about it
The Following 5 Users Say Thank You to xfinrodx For This Useful Post: [ View ]
11th January 2013, 10:19 PM   |  #478  
Senior Member
Flag Azusa
Thanks Meter: 14
 
205 posts
Join Date:Joined: May 2007
More
Quote:
Originally Posted by xfinrodx

Why don't you just go back to a different ROM? No shame in that. Find something that works and stick with it or deal with the rough ride of progress (or learn and help the progress)! Either of those options are good, but nobody really cares about whether you buy a new car stereo. Fix it yourself, comment on/file a relevant bug, deal with it, or try another ROM. I see no other productive alternative... Surely the CyanogenMod team "care(s) to fix" all issues in their distribution - the challenges of time, manpower and distributed knowledge make this a utopian goal, however. Contribute or leech, just don't complain about it

I can't go to a different ROM on sense i had the same problem it was CyanogenMod that fixed it up until that last update. I have been using CM since the Tmobile G1 days it worked then. Then upgraded to a EVO 4G CyanogenMod fixed it back then too then upgraded to the ONE X and guess what CM fixed the same problem that has plagued HTC's Sense based ROMS since all the way back to the HTC Hero days. Now the latest update that I linked causes distortion and btw I did comment on that fix and if you see nobody has replied that hey well look into it nothing. All i can do is ask nothing wrong with that and its a simple answer of either yes ill see what i can do or hey I really don't care about that problem and you can go fly a kite. Not trying to complain but trying to get a FIX or even a acknowledgement.

As for contributing I have contributed plenty over the years since my G1 from logcats to donations hell I helped fix the microphone using the top input problem by bringing it up so don't just assume I haven't done anything in relation to CM.
Last edited by P_Dub_S; 11th January 2013 at 10:24 PM.
11th January 2013, 10:31 PM   |  #479  
xfinrodx's Avatar
Senior Member
Flag Spokane
Thanks Meter: 76
 
360 posts
Join Date:Joined: Jul 2010
More
Quote:
Originally Posted by P_Dub_S

I can't go to a different ROM on sense i had the same problem it was CyanogenMod that fixed it up until that last update. I have been using CM since the Tmobile G1 days it worked then. Then upgraded to a EVO 4G CyanogenMod fixed it back then too then upgraded to the ONE X and guess what CM fixed the same problem that has plagued HTC's Sense based ROMS since all the way back to the HTC Hero days. Now the latest update that I linked causes distortion and btw I did comment on that fix and if you see nobody has replied that hey well look into it nothing. All i can do is ask nothing wrong with that and its a simple answer of either yes ill see what i can do or hey I really don't care about that problem and you can go fly a kite. Not trying to complain but trying to get a FIX or even a acknowledgement.

As for contributing I have contributed plenty over the years since my G1 from logcats to donations hell I helped fix the microphone using the top input problem by bringing it up so don't just assume I haven't done anything in relation to CM.

Better ways to go about this abound. If you'd like to discuss it further feel free to PM me, I think I've made the only public point I needed to in my previous post. I'm a little more Kantean than some in regards to this topic and I believe your history is not as important as your present choices.
11th January 2013, 10:46 PM   |  #480  
h8rift's Avatar
OP Recognized Developer
Thanks Meter: 9,824
 
1,854 posts
Join Date:Joined: Jun 2010
Donate to Me
More
Quote:
Originally Posted by P_Dub_S

Will bluetooth still be using this update https://github.com/cyanogenmod/andro...d705688412746c I have not been able to use any ROM since the last experimental CM10 that update really screwed my bluetooth quality with distortion. At this point if it doesn't get reverted I am gonna have to either buy a new car stereo, start a bounty for someone to modify that specific setting on newer builds, or sell the phone which I really don't want to do. Please can I get a yay or nay on whether you care to fix this or not so I can move on?

We are aware and of course we are working on the problem. There are hundreds of other issue besides audio quality at this time.

Quote:
Originally Posted by xfinrodx

Why don't you just go back to a different ROM? No shame in that. Find something that works and stick with it or deal with the rough ride of progress (or learn and help the progress)! Either of those options are good, but nobody really cares about whether you buy a new car stereo. Fix it yourself, comment on/file a relevant bug, deal with it, or try another ROM. I see no other productive alternative... Surely the CyanogenMod team "care(s) to fix" all issues in their distribution - the challenges of time, manpower and distributed knowledge make this a utopian goal, however. Contribute or leech, just don't complain about it

I see what you responded the way you did, but you should be more aware that this will only cause more back-and-forth, which does nothing for this project excepts stops me to calm everyone down. again.

Quote:
Originally Posted by P_Dub_S

I can't go to a different ROM on sense i had the same problem it was CyanogenMod that fixed it up until that last update. I have been using CM since the Tmobile G1 days it worked then. Then upgraded to a EVO 4G CyanogenMod fixed it back then too then upgraded to the ONE X and guess what CM fixed the same problem that has plagued HTC's Sense based ROMS since all the way back to the HTC Hero days. Now the latest update that I linked causes distortion and btw I did comment on that fix and if you see nobody has replied that hey well look into it nothing. All i can do is ask nothing wrong with that and its a simple answer of either yes ill see what i can do or hey I really don't care about that problem and you can go fly a kite. Not trying to complain but trying to get a FIX or even a acknowledgement.

As for contributing I have contributed plenty over the years since my G1 from logcats to donations hell I helped fix the microphone using the top input problem by bringing it up so don't just assume I haven't done anything in relation to CM.

Of course this is being worked on, there is no need to flaunt your credentials and past deeds. I get it bro .

Quote:
Originally Posted by xfinrodx

Better ways to go about this abound. If you'd like to discuss it further feel free to PM me, I think I've made the only public point I needed to in my previous post. I'm a little more Kantean than some in regards to this topic and I believe your history is not as important as your present choices.

I'm glad you are trying to pull this into a PM (where it belongs, mind you!)


<begin rant>
To all who think that every single reply on every single issue on every single forums post, issue tracker, and Q&A topic is going to receive a personalized message from me saying "Don't worry br0, I got it.", throw that thought in the trash can.

I see *every single issue* on the Issue Tracker.

Every.
Single.
Day.

I look at them and try to think which one can I tackle today while still continuing to fix the problems we already have porting this forward, and trying to help users that need support (emailing me, PM'ing me, GTalking me, Google+ messaging me, and pinging me on IRC).

Now please don't start replying with anger, and dont reply with "dont make him mad, he will leave us!" either. I do this because I have fun doing it. The more and more I play with Android, the more enjoyment I get. I've spent the last 10 years in IT doing, you guessed it, squashing bugs! Its fun for me!

Just don't take the fun out of it by saying "is it done yet?" or "what's the problem, it seems so easy" or "well I'm just gonna leave for XYZ rom". To be completely, level-headedly honest. I'm fine if you feel the need to flash another ROM. I didn't make this for you. I made this for fun. I'm just sharing it with you.

Basically. I love that you guys enjoy using this as much as I enjoy working on it. And the support from all of you is amazing. Let's just keep it that simple, k?

</rant>

Thanks all!
-h8

The Following 51 Users Say Thank You to h8rift For This Useful Post: [ View ]
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Top Threads in One X Original Android Development by ThreadRank