NEW DEV TEAM - TeamXE

Search This thread

doperthancoke

Senior Member
Jul 22, 2013
436
138
It doesn't have Google Now either. D:

I'm randomly syncing either CM10 or CM9 - I've got both repos there, just downloading what I want to at the moment.

Who needs Google Now? At this point, staying up to date isn't important anymore. I think we should just try and get ONE fully working CM rom.
 

xperiathunder

Member
Oct 2, 2014
30
17
either we sholu choose cm10 or cm9

Sent from my C1605 using XDA Premium 4 mobile app

---------- Post added at 12:29 PM ---------- Previous post was at 12:27 PM ----------

sorry its "should";)

Sent from my C1605 using XDA Premium 4 mobile app
 

NSDCars5

Senior Member
Feb 17, 2013
1,188
461
Over there
nsood.in
Who needs Google Now? At this point, staying up to date isn't important anymore. I think we should just try and get ONE fully working CM rom.

I need Google Now! I use it a lot!

It isn't about staying up to date. Right now, ICS has a separate Google version. Soon, apps will start being incompatible. I prefer Jelly Bean to that, even if lag builds up. (It doesn't in stock JB, though...)
 

NeoTrix

Senior Member
May 12, 2013
581
127
Bangalore
I need Google Now! I use it a lot!

It isn't about staying up to date. Right now, ICS has a separate Google version. Soon, apps will start being incompatible. I prefer Jelly Bean to that, even if lag builds up. (It doesn't in stock JB, though...)

I do remember having a flashable zip for google now.
It's in pico section.
Works (Y)
Tested.
 

Louai13

Member
May 31, 2014
11
3
Just A Suggestion !

What About Resting Now and wait for Android L to be released { maybe 16/10 } and make an unofficial build of CM12 {when released} ....
For Now , I think that You Should make the team that will work on this ROM and develop it .
You are true that CM9 And ICS is kinda outdated now and many apps and features will not work on it .. So it is not a good idea
CM10 is approximtly Stable So it doesn't need development { except for the camera which will take long time if you try to fix it }
So i think that working on Android L and trying to make it the first { and last } ROM that has no bug would be the best Case
I know that it is hard but i think that will be the best Thing that could be Done :)
 

doperthancoke

Senior Member
Jul 22, 2013
436
138
What About Resting Now and wait for Android L to be released { maybe 16/10 } and make an unofficial build of CM12 {when released} ....
For Now , I think that You Should make the team that will work on this ROM and develop it .
You are true that CM9 And ICS is kinda outdated now and many apps and features will not work on it .. So it is not a good idea
CM10 is approximtly Stable So it doesn't need development { except for the camera which will take long time if you try to fix it }
So i think that working on Android L and trying to make it the first { and last } ROM that has no bug would be the best Case
I know that it is hard but i think that will be the best Thing that could be Done :)

CM10 is not stable. If you use it long enough, your gsm stop working.

Sent from my C1505 using XDA Free mobile app
 
  • Like
Reactions: NeoTrix

Louai13

Member
May 31, 2014
11
3
CM10 is not stable. If you use it long enough, your gsm stop working.

Sent from my C1505 using XDA Free mobile app

Oh , i have just remembered
This happened to me 1 or 2 times only in last few months
AnyWay , What do you think that is better ?!
{ Trying to fix CM10 , Making CM9 , Or Try to make CM12 when Cyanogen release it }
 

doperthancoke

Senior Member
Jul 22, 2013
436
138
Oh , i have just remembered
This happened to me 1 or 2 times only in last few months
AnyWay , What do you think that is better ?!
{ Trying to fix CM10 , Making CM9 , Or Try to make CM12 when Cyanogen release it }

I think the best option right now is to try and make CM9. CM10 is slower and hard to fix, so trying out CM9 is a good idea: It might not have bugs/ less bugs overall. My theory: The older the android version,the easier and less complicated it is to compile/port.
 

NSDCars5

Senior Member
Feb 17, 2013
1,188
461
Over there
nsood.in
I think the best option right now is to try and make CM9. CM10 is slower and hard to fix, so trying out CM9 is a good idea: It might not have bugs/ less bugs overall. My theory: The older the android version,the easier and less complicated it is to compile/port.

Not necessarily. For example, porting Gingerbread to, say, the Xperia Z3 would be really hard.

CM9 doesn't have support of any kind for the E. CM10 at least has an FXP device tree to start with. It'll actually be easier to port CM10.

Plus, unless you're gaming, the difference between stock JB and stock ICS is barely noticeable (both on 1 Ghz). CM10 vs CM9 should be the same - only gamers would have any use for it. And I'm pretty sure nobody buys the Xperia E for its gaming prowess. :p
 
  • Like
Reactions: doperthancoke

doperthancoke

Senior Member
Jul 22, 2013
436
138
Not necessarily. For example, porting Gingerbread to, say, the Xperia Z3 would be really hard.

CM9 doesn't have support of any kind for the E. CM10 at least has an FXP device tree to start with. It'll actually be easier to port CM10.

Plus, unless you're gaming, the difference between stock JB and stock ICS is barely noticeable (both on 1 Ghz). CM10 vs CM9 should be the same - only gamers would have any use for it. And I'm pretty sure nobody buys the Xperia E for its gaming prowess. :p

Its up to you and the devs then. I'm not a dev, so I guess I should just appreciate whatever you guys do. I mean, we are still lucky enough to have *some* devs left (unlike some devices ) and I think I should be thankful for that.

Sent from my C1505 using XDA Free mobile app
 

NSDCars5

Senior Member
Feb 17, 2013
1,188
461
Over there
nsood.in
Its up to you and the devs then. I'm not a dev, so I guess I should just appreciate whatever you guys do. I mean, we are still lucky enough to have *some* devs left (unlike some devices ) and I think I should be thankful for that.

Sent from my C1505 using XDA Free mobile app

Fun fact: "Dev" in Hindi (different pronunciation) means "god". :p Not relevant, but I just remembered that.

Yep, let's see what me and the gods do. :p Don't keep hopes high from me, though - just trying my best.
 
  • Like
Reactions: doperthancoke

UltraGamerHD

Senior Member
Aug 15, 2013
1,259
1,406
Xiaomi Redmi Note 7
Xiaomi Poco X3 NFC
But I'm already syncing CM10 sour- fine. :p But I'm 99% sure it'll never be finished. :p

Hi!

CM10: I have got CM10 fully working with jjm34 source code, its just picking out correct repo's from his manifest apart from that the rom compiles without issues and works great. He has used a lot of source code from the code aurora forum which has discontinued support for msm7x27a.
 

doperthancoke

Senior Member
Jul 22, 2013
436
138
Hi!

CM10: I have got CM10 fully working with jjm34 source code, its just picking out correct repo's from his manifest apart from that the rom compiles without issues and works great. He has used a lot of source code from the code aurora forum which has discontinued support for msm7x27a.

Wow! Thumbs up for you! No more gsm bug?

Sent from my C1605 using XDA Free mobile app
 

NeoTrix

Senior Member
May 12, 2013
581
127
Bangalore
Video recording?[I guess no] *Asks though he knows the answer*
Btw,I suggest you stay on cm10 for a while. Reboot the phone sometimes just to check if gsm bug is still present.
But if things are good like you said,It's awesome.
Maybe we could receive some cm10 based ports like PA.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 4
    But I'm already syncing CM10 sour- fine. :p But I'm 99% sure it'll never be finished. :p

    Hi!

    CM10: I have got CM10 fully working with jjm34 source code, its just picking out correct repo's from his manifest apart from that the rom compiles without issues and works great. He has used a lot of source code from the code aurora forum which has discontinued support for msm7x27a.
    3
    If you want to build a properly working CM10 there is a lot of work to do.

    jjm34's device repos are messed up and incomplete. No offence to him, or any of his skills but it's even a wonder the ROM boots.

    It would be best to start from scratch, but that's a pain.

    I do not own the device anymore, but for my current phone(the almighty bacon :D)there already is a ton of development so I think you guys would appreciate my help more than they do.

    Anyway, I'll have another look at the source again this Saturday to see what I can do.

    -Peace

    ---------- Post added at 10:20 PM ---------- Previous post was at 10:18 PM ----------

    Actually, cut the triple recovery, at least on stock. CM11, maybe, but stock won't work - vold managed partitions in KitKat recoveries don't show up with stock.

    If you really want to, I might know a way to do it, but Xperia devices have always been annoying things to build kernels for.

    Anyway, it would require a lot of "hacking" and chopping up code to work, but it might be possible.

    Again, why would you want it?

    ---------- Post added at 10:28 PM ---------- Previous post was at 10:20 PM ----------

    Oh, and your CM11 source is also messy. You merge commits like it's nothing and don't organise them. Make a list of errors and eliminate them one by one.

    Don't do all sorts of stuff at the same time, it causes confusion for others who want to check your source.

    I shouldn't be such a know-it-all, but I always am, sorry. :p

    Please don't take this the wrong way.
    2
    Video recording?[I guess no] *Asks though he knows the answer*
    Btw,I suggest you stay on cm10 for a while. Reboot the phone sometimes just to check if gsm bug is still present.
    But if things are good like you said,It's awesome.
    Maybe we could receive some cm10 based ports like PA.

    I can never get CM10 ports to work because I don't know what RIL is used and I think its incorporated into framework.jar also its not defined in build.prop
    1
    What About Resting Now and wait for Android L to be released { maybe 16/10 } and make an unofficial build of CM12 {when released} ....
    For Now , I think that You Should make the team that will work on this ROM and develop it .
    You are true that CM9 And ICS is kinda outdated now and many apps and features will not work on it .. So it is not a good idea
    CM10 is approximtly Stable So it doesn't need development { except for the camera which will take long time if you try to fix it }
    So i think that working on Android L and trying to make it the first { and last } ROM that has no bug would be the best Case
    I know that it is hard but i think that will be the best Thing that could be Done :)

    CM10 is not stable. If you use it long enough, your gsm stop working.

    Sent from my C1505 using XDA Free mobile app
    1
    I think the best option right now is to try and make CM9. CM10 is slower and hard to fix, so trying out CM9 is a good idea: It might not have bugs/ less bugs overall. My theory: The older the android version,the easier and less complicated it is to compile/port.

    Not necessarily. For example, porting Gingerbread to, say, the Xperia Z3 would be really hard.

    CM9 doesn't have support of any kind for the E. CM10 at least has an FXP device tree to start with. It'll actually be easier to port CM10.

    Plus, unless you're gaming, the difference between stock JB and stock ICS is barely noticeable (both on 1 Ghz). CM10 vs CM9 should be the same - only gamers would have any use for it. And I'm pretty sure nobody buys the Xperia E for its gaming prowess. :p
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone