5,593,401 Members 36,281 Now Online
XDA Developers Android and Mobile Development Forum

[Discussion][ROM][S4][WIP] CM10.1 on HTC One S

Tip us?
 
klutch
Old
(Last edited by klutch; 13th December 2012 at 05:34 AM.)
#21  
klutch's Avatar
Senior Member
Thanks Meter 34
Posts: 576
Join Date: Jul 2007
Location: Bronx,Ny
well it seemz that 10.1 experimental had a issue and did eveything wipe ect... i just rather wait for the next update , i thought i bricked it n checked everything n i was doing it right but its the build that he may not working properly, so like i said its much better to wait for the next one and go back to the one u had backed up
Device:Nexus 5
Recovery: TWRP v2.7.0.0
ROM:PA Beta 3/Franco Kernel

Device:Nexus 4
Recovery:TWRP v2.7.0.0
ROM:Cataclysm/Franco Kernel

Device:HTC One S
Recovery:TWRP v2.7.0.0
ROM:CM11

Device:Note 3
Recovery:TWRP v2.7.0.0
ROM:SlimKat
--------------------
Retired Phones
Tmobile-G1 =>Sold
My Touch 4G CM7 =>SOLD
HTC Sensation 4G CM10=>SOLD
Nexus S GSM =>Repair
Nexus One GSM=>Repair
TF201 =>Repair
The Following User Says Thank You to klutch For This Useful Post: [ Click to Expand ]
 
rugmankc
Old
#22  
rugmankc's Avatar
Senior Member
Thanks Meter 1469
Posts: 6,800
Join Date: Jun 2010
Location: Dayton, Ohio
Quote:
Originally Posted by klutch View Post
well it seemz that 10.1 experimental had a issue and did eveything wipe ect... i just rather wait for the next update , i thought i bricked it n checked everything n i was doing it right but its the build that he mad not working properly, so like i said its much better to wait for the next one and go back to the one u had backed up
gotcha--there is always a rom or two that doesn't want to play nice on some phones no matter what we do
ATT Samsung Galaxy S4/Rooted/TWRP 2.5.0.2/KT, Faux, or Audism Kernels/3 Minit, Wanam Xposed, or Gravity Box/Long Time MultiRom Flasher




 
WHou
Old
#23  
Junior Member
Thanks Meter 2
Posts: 23
Join Date: Sep 2009
Why is it so difficult to get a working version of cyanogenmod? Just curious as to why every new release is utterly broken.
 
Zonium
Old
#24  
Senior Member
Thanks Meter 13
Posts: 103
Join Date: Apr 2012
My CM10 has been working great since I starded flashing CM Roms. Like 2 months ago.

Sent from my HTC One S
 
rugmankc
Old
#25  
rugmankc's Avatar
Senior Member
Thanks Meter 1469
Posts: 6,800
Join Date: Jun 2010
Location: Dayton, Ohio
That's why they call it development and it is free to you--

I question your comment "every" release is broken

If you are about talking cyanogen in general, the nightlies work fine for me and most folks

If talking about this one, READ xkonni's comments in his CM10 thread. He said he probably uploaded this too early. But, WE are appreciative he did so we can get a taste of JB4.2 as it gets DEVELOPED--

Except for camera and bluetooth it works very well, not a daily for most, but not intended as one--

The technicals are beyond me to answer that part of your question, but enjoy these builds and respect the hard work the devs put in to these roms, working 100% or not.
ATT Samsung Galaxy S4/Rooted/TWRP 2.5.0.2/KT, Faux, or Audism Kernels/3 Minit, Wanam Xposed, or Gravity Box/Long Time MultiRom Flasher




The Following 3 Users Say Thank You to rugmankc For This Useful Post: [ Click to Expand ]
 
el_smurfo
Old
#26  
el_smurfo's Avatar
Senior Member
Thanks Meter 1040
Posts: 3,001
Join Date: Oct 2009
Quote:
Originally Posted by WHou View Post
Why is it so difficult to get a working version of cyanogenmod? Just curious as to why every new release is utterly broken.
1. AOSP is not device specific, so every single handset needs to have it's specific drivers and associated tweaks imported by hand, one by one, by one or two dedicated developers, entirely in their spare time.

2. Utterly broken is just stupid. This build is 95% working only a few weeks after release to AOSP. The camera and bluetooth functions are always hard to get because the code is usually closed source for the hardware layers. If I didn't have a toddler I wanted to photograph, this would be my daily driver right now.

3. Most would find it very hard to get motivated to spend their free time delivering up awesome ROMs only to be told they are "utterly broken". I'd suggest you rewrite your comment as follows: "Why is it so difficult to get appreciation for devoting ones free time to developing awesome ROMs. Just curious why so many users are utterly rude".
The Following 6 Users Say Thank You to el_smurfo For This Useful Post: [ Click to Expand ]
 
Darknites
Old
#27  
Darknites's Avatar
Senior Member
Thanks Meter 2064
Posts: 5,190
Join Date: Jul 2011
Quote:
Originally Posted by el_smurfo View Post
1. AOSP is not device specific, so every single handset needs to have it's specific drivers and associated tweaks imported by hand, one by one, by one or two dedicated developers, entirely in their spare time.

2. Utterly broken is just stupid. This build is 95% working only a few weeks after release to AOSP. The camera and bluetooth functions are always hard to get because the code is usually closed source for the hardware layers. If I didn't have a toddler I wanted to photograph, this would be my daily driver right now.

3. Most would find it very hard to get motivated to spend their free time delivering up awesome ROMs only to be told they are "utterly broken". I'd suggest you rewrite your comment as follows: "Why is it so difficult to get appreciation for devoting ones free time to developing awesome ROMs. Just curious why so many users are utterly rude".
Agreed, I have no real issues with AOSP roms.
BAKED BlackBean 9
Best rom going and its blacked out too (sorry other devs)

Common Issues, Tips & Useful Links
Are you bootlooping or can't access the SD card, then don't look no further and click above to see how to fix it.

HoloCrazy
Are you bored of the white icons but really like Holo colour like me, then this mod is for you
 
djsubtronic
Old
#28  
Senior Member
Thanks Meter 449
Posts: 1,973
Join Date: Jun 2010
I think the issue is about curiosity as to WHY they are broken, i.e. the camera was fixed in 4.1.2 so why is it broken in 4.2? To be honest I'm quite curious about that as well. Or eg the headset detection - this existed in 4.1 but was fixed, so I would have thought it should continue working on 4.2...
 
el_smurfo
Old
#29  
el_smurfo's Avatar
Senior Member
Thanks Meter 1040
Posts: 3,001
Join Date: Oct 2009
Quote:
Originally Posted by djsubtronic View Post
I think the issue is about curiosity as to WHY they are broken, i.e. the camera was fixed in 4.1.2 so why is it broken in 4.2? To be honest I'm quite curious about that as well. Or eg the headset detection - this existed in 4.1 but was fixed, so I would have thought it should continue working on 4.2...
I suspect because the device specific parts of the One S have not been merged into the 4.2 branch. I don't think AOSP contains any proprietary code, while any handset hardware requires these binaries and hardware interface layers.
 
tnpapadakos
Old
#30  
tnpapadakos's Avatar
Senior Member
Thanks Meter 1020
Posts: 2,857
Join Date: Dec 2009
Location: Tampa

 
DONATE TO ME
Quote:
Originally Posted by djsubtronic View Post
I think the issue is about curiosity as to WHY they are broken, i.e. the camera was fixed in 4.1.2 so why is it broken in 4.2? To be honest I'm quite curious about that as well. Or eg the headset detection - this existed in 4.1 but was fixed, so I would have thought it should continue working on 4.2...
this used to irk me too
now i think of aosp as the OS
then there's the hardware specific files like libs and such...i think of these as the drivers

not even Windows has all the drivers you'll ever need included

Tags
10.1, cm10.1, cyanogenmod, discussion
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes