[ROM][6.0.1_r74][CM+AOSP][FINAL BUILD 08/12/2016] Unofficial TEMASEK [UberTC/Linaro]

[timbuctoo]

Just a quick update: Flashed the newest version and it works perfectly. I also went through the trouble of installing the latest beta of the Google app, xposed for Marshmallow (for the N'ify module that allows you to run Nougat only apps), and the Google Assistant lifted from the leaked Pixel system dump. It works perfectly, the full Assistant is a lot more than the teaser that is part of Allo.

Thanks for the confirmation on Google Assistant.
@FSadino, would be great if we could have Assistant as part of the ROM itself

 

[FSadino]

Just a quick update: Flashed the newest version and it works perfectly. I also went through the trouble of installing the latest beta of the Google app, xposed for Marshmallow (for the N'ify module that allows you to run Nougat only apps), and the Google Assistant lifted from the leaked Pixel system dump. It works perfectly, the full Assistant is a lot more than the teaser that is part of Allo.

Thanks for the confirmation on Google Assistant.

@FSadino, would be great if we could have Assistant as part of the ROM itself

Please share the guide you used to make it work because I tryed with xposed + N-ify but can't make it work. Please share all your steps and links.

I will see what I can do but for now I'm spending my time working on Android N so temasek cm13 updates will be paused for some days.

 

[kaibosh99]

Please share the guide you used to make it work because I tryed with xposed + N-ify but can't make it work. Please share all your steps and links.

Everything I did is listed here: http://www.droidape.com/get-google-assistant-marshmallow-devices/

Keep in mind this involves using xposed. The module to allow this is called 'N'ify', but there is another module that is being developed specifically just for this. Either way, there is still one single bug that so far hasn't been squashed - every time you activate the Assistant by voice, it brings up the trainer screen. You can just hit 'not now' to get around it, but some people would call this a killer bug. It still works perfectly via a long press of the home 'button'.

For now, this is still technically a 'hack'. Google themselves may choose to fight Assistant integration into other nougat builds as time goes by, so for now I would choose to play with this at your peril. The cutting edge google.apk installation by itself seems to work perfectly, and brings a very slick new pulldown menu and such that I haven't had any issues with.

 

[keen36]

Everything I did is listed here: http://www.droidape.com/get-google-assistant-marshmallow-devices/

Keep in mind this involves using xposed. The module to allow this is called 'N'ify', but there is another module that is being developed specifically just for this. Either way, there is still one single bug that so far hasn't been squashed - every time you activate the Assistant by voice, it brings up the trainer screen. You can just hit 'not now' to get around it, but some people would call this a killer bug. It still works perfectly via a long press of the home 'button'.

For now, this is still technically a 'hack'. Google themselves may choose to fight Assistant integration into other nougat builds as time goes by, so for now I would choose to play with this at your peril. The cutting edge google.apk installation by itself seems to work perfectly, and brings a very slick new pulldown menu and such that I haven't had any issues with.

can confirm that except for the one known retrain bug, everything seems to be well. the notification menu is slick, that is true. for the assistant to be really cool, that bug has to be fixed though. it's difficult to have a conversation when one has to press a button before every sentence :silly:

all in all everything is running surprisingly well

 

[mohit310]

@FSadino are we having any new releases with Android 7

 

[FSadino]

@FSadino are we having any new releases with Android 7

I didn't decided yet if I will continue temasek or make my own build. BTW, I don't have time now

 

[gogunners]

I didn't decided yet if I will continue temasek or make my own build. BTW, I don't have time now

Could this be the end of temasek for oneplus one...?

 

[GuestX00561]

I didn't decided yet if I will continue temasek or make my own build. BTW, I don't have time now

Too bad... After a few weeks with nougat (which is great ofc) I'm back to this ROM. It's so fast, smooth and polished, best battery ever. [emoji8]

Sent from my A0001 using Tapatalk

 

[FSadino]

Could this be the end of temasek for oneplus one...?

Too bad... After a few weeks with nougat (which is great ofc) I'm back to this ROM. It's so fast, smooth and polished, best battery ever. [emoji8]

Sent from my A0001 using Tapatalk

I didn't said it's over...

 

[lobai]

I didn't said it's over...

Thanks bro [emoji1]
Love ur work..

 

[cybot_x1024]

So I've been investigating why my battery life is so short and battery stats figures don't add up so I enabled the most verbose battery stats I could get out of this ROM.
Since the last full charge this 'miscellaneous' was at 53%, screen was 13% battery use and the rest of the apps and processes 8% and below.
Why would there be such a big difference between observed power use and computed power use? My battery has only lasted 12 hours or so since 100% to taking that screenshot

Sent from my A0001 using XDA Free mobile app

 

[Kzeran]

So I've been investigating why my battery life is so short and battery stats figures don't add up so I enabled the most verbose battery stats I could get out of this ROM.
Since the last full charge this 'miscellaneous' was at 53%, screen was 13% battery use and the rest of the apps and processes 8% and below.
Why would there be such a big difference between observed power use and computed power use? My battery has only lasted 12 hours or so since 100% to taking that screenshot

Sent from my A0001 using XDA Free mobile app

I have the same "problem" here

 

[FSadino]

So I've been investigating why my battery life is so short and battery stats figures don't add up so I enabled the most verbose battery stats I could get out of this ROM.
Since the last full charge this 'miscellaneous' was at 53%, screen was 13% battery use and the rest of the apps and processes 8% and below.
Why would there be such a big difference between observed power use and computed power use? My battery has only lasted 12 hours or so since 100% to taking that screenshot

Sent from my A0001 using XDA Free mobile app

I have the same "problem" here

Try clean flash and update your gapps

 

[prince747]

Hi,

Been here on this ROM for almost a year. Now contemplating move to the official CM 13. Normally I would have clean flashed the official version over this directly.

But I was wondering if there is any thing (maybe some partition related stuff) I'd have to do like flash a particular build before flashing the latest nightly etc.

Sorry this is off topic but I'd appreciate any help. Thanks!

 

[kaibosh99]

Hi,

Been here on this ROM for almost a year. Now contemplating move to the official CM 13. Normally I would have clean flashed the official version over this directly.

But I was wondering if there is any thing (maybe some partition related stuff) I'd have to do like flash a particular build before flashing the latest nightly etc.

Sorry this is off topic but I'd appreciate any help. Thanks!

Don't take this as gospel, but all you should need to do is make sure you have the latest *proven* version of recovery, namely TWRP. Other than that, the baseline CM build is what is needed to flash first in order to flash most *other* CM variants, usually because of drivers and such. At least, this is always how it has worked in the past. Needless to say, go through the trouble of making a full recovery backup and pulling it off onto your pc before proceeding, and if you are like me make a full Titanium Backup and pull that as well. The software to pull individual apps/data out of a recovery backup is clunky but it does work if you absolutely need it to.

I would do a full factory/data wipe though, not a dirty flash - if for no other reason than to ensure full cleanup of GAPPS stuff. Junk left behind by older GAPPS is the cause of a lot of misery in this hobby.


And, while off topic, please let us know how it went. I am very happy with this current build and it doesn't upset me in the slightest that we aren't getting any releases lately because it is so rock solid and complete, but... We will all be moving to a stable 7.x build someday.

 

[prince747]

Don't take this as gospel, but all you should need to do is make sure you have the latest *proven* version of recovery, namely TWRP. Other than that, the baseline CM build is what is needed to flash first in order to flash most *other* CM variants, usually because of drivers and such. At least, this is always how it has worked in the past. Needless to say, go through the trouble of making a full recovery backup and pulling it off onto your pc before proceeding, and if you are like me make a full Titanium Backup and pull that as well. The software to pull individual apps/data out of a recovery backup is clunky but it does work if you absolutely need it to.

I would do a full factory/data wipe though, not a dirty flash - if for no other reason than to ensure full cleanup of GAPPS stuff. Junk left behind by older GAPPS is the cause of a lot of misery in this hobby.


And, while off topic, please let us know how it went. I am very happy with this current build and it doesn't upset me in the slightest that we aren't getting any releases lately because it is so rock solid and complete, but... We will all be moving to a stable 7.x build someday.

I took a TiBa backup of my apps+data and tried to clean flash the latest CM nightly using TWRP (which was always there). The installation failed saying "corrupt zip file".

I said screw it and clean flashed the last @FSadino's build and restored my apps+data. Can wait until 7.x like you said

Thanks for the reply though!

 

[kaibosh99]

I took a TiBa backup of my apps+data and tried to clean flash the latest CM nightly using TWRP (which was always there). The installation failed saying "corrupt zip file". I said screw it and clean flashed the last @FSadino's build and restored my apps+data. Can wait until 7.x like you said

I ran into this a little while back and looking into it my TWRP just wasn't compatible with the .zip. I would have had to switch to a completely different recovery altogether, I cringed and did a full restore.

 

[FSadino]

Hello guys and girls,

I have talked to some devs and I have some lights to upgrade this amazing rom to nougat trees but I'm having a huge problem to compile my build. It seems I can't continue building with my old laptop with only 4gb of ram and I decided to sell my ram and buy 4gb x 4gb, it should be enough... Maybe next week I have the money to do this and continue to compile and test my builds.

 

[sino1641]

Hello guys and girls,

I have talked to some devs and I have some lights to upgrade this amazing rom to nougat trees but I'm having a huge problem to compile my build. It seems I can't continue building with my old laptop with only 4gb of ram and I decided to sell my ram and buy 4gb x 4gb, it should be enough... Maybe next week I have the money to do this and continue to compile and test my builds.

I think dev should keep building marshallow because nougat is not stable for now.

 

[saberzaid]

how this rom compare to the others