Database Develop

All ROMs are unusable in my Milestone

Hi guys, I really need some help. Every ROM I install gets this weird display problem. It changes the screen to like 4-bit color, and sometimes just blue, and sometimes red. I tried almost all ROMs i can get my hands on, and they all do the same.
I'm really new at this and here are the steps I have taken to root my phone and install the ROMs:
I followed this guide to install GOT in my milestone. I purchased my Milestone online, so I wasn't sure it's origin. It says EMEA in my About Phone page, so I went with the G.O.T RETAIL EUROPE (RTEU) version. I was stuck in one of the steps in the recovery mode where I have to apply the update.zip to get into OpenRecovery. It greeted me with the an error message. I did some googling and found out it might have something to do with the vulnerable recovery. So i downloaded it and flashed my phone. Somehow, that worked. I have used the G.O.T thing for about a day and decided to install the ROMs. First, I deleted the G.O.T Openrecovery file from the sd card and copy the ANDROIDIANI files into sd card. I also did the wipe dvlivk/data/cache before applying the ROM. And the clock speed is in default.
What did I do wrong?? Any help will be greatly appreciated.
Here's how screen looks like:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I hope you'll be answered shortly..
may I suggest you to flash stock rom.. from the following link
http://and-developers.com/sbf:milestone
choose your area & try..
hope this will help

Thanks for the respond. I forgot teo mention that the 2.2.1 G.O.T SBF that I flashed with does not have this problem. But it presents in all the different ROMs that i have tried. This is so weird. Anyone have any idea of what might cause this problem?

I'm sorry to bring up this post, but I can barely use my phone because of this problem. I desperately need help with this. My english is not very good. Can someone please provide the correct words to describe my problem. So i can do some proper google search and hopefully, it will come up with something.

if by spf you are not having this problem, true?
then, can you give us an example of one rom you used that creat this problem?

I tried the Froyo Mod, Cyanogen Mod, Cronos Mod, MIUI mod and HoboMod. They all have the same problem. =(

I still can't a solution to my problem yet. Any help will be greatly appreciated.

So just to be sure... it runs fine on a stock rom right?
Most roms when they install they are overclocked.
Did you try setting the clock back to 550mhz after installing one of these roms?
Also, maybe one of the new leaks will work for you.

that's weird, sorry but I can't help

Really weird. You can try to do all again. Put the original SBF file and the using ANDROIANI openrecovery put a Ho!no nandroid or other system with a nandroid archives.

njmata said:
Really weird. You can try to do all again. Put the original SBF file and the using ANDROIANI openrecovery put a Ho!no nandroid or other system with a nandroid archives.
Click to expand...
Click to collapse
Thanks for the reply. I'm going to try that now.
I'm trying to get the original sbf from this page. http://and-developers.com/sbf:milestone
The thing is that I live in the US and I got mine from Newegg.com. Which one should i download??
EDIT: What is the difference between service and non service?

Never have that problem. Maybe should flash back to stock to see if hardware problem.

It works fine with the stock ROM and the GOT SBF. And with anything else, I will get that stupid screen. =( This is so weird. I have flashed back to stock ROM. And now, how do I install HO!NO!? I can't seem to get into the Open Recovery with the Stock ROM. Any help please??
EDIT: When every time I install a new ROM, I don't get that problem until like after 10 minutes when I installed a bunch of apps. Could it be the apps that I installed that caused that problem??? But it's the same apps that i run in the GOT SBF.

which apps are you applying?
try adding by group, or left out any game (can be a problem).
Are the apps ready for your phone? perhaps some app is for other phone and works bad in MM.
Yo mention that applying the ROM works UNTIL applying apps, so it is very possible that some app is not for your hardware or need some special feature from display.

zeppelinrox said:
So just to be sure... it runs fine on a stock rom right?
Most roms when they install they are overclocked.
Did you try setting the clock back to 550mhz after installing one of these roms?
Also, maybe one of the new leaks will work for you.
Click to expand...
Click to collapse
Did the OP try this...it seems like the most likely explanation.
Your phone could be very bad at overclocking. My first milestone was, but it didnt experience these exact symptoms.
Try flashing a rom and downclocking it to around stock (550 or 600).
Your phone could be fine until it heats up due to the 3g/wifi being used. Combine this with the added heat of upped vsels €nd you have general weirdness.
Sent from my Milestone using Tapatalk

I have this exact same problem - when I used the stock rom on my hong kong milestone and overclocked modestly (800 52vsel) I was fine. As soon as I installed my first rom (in my case Shadowmod 2.5 via update.zip from AOR 3.3) I had this problem. It happens most often when the keyboard is open.
In additon to the screen yellow/red colour problem it will also just go blank, while the touch buttons stay lit. For either problem, simply turning the screen off and on again using the power button clears it, so it is more annoying than a show stopper.
Now I am using the APAC jan 25 leak and still have the issue. I only used an sbf to install the vulnerable recovery, and have used nandroid/updates to install everything else (never used the GOT thing). SBFs are annoying for me as I have a mac.
Anyway, I plan to recover my stock 2.1 nandroid and see if the problem is still there. Too bad, I love the battery life of the 2.2 roms, and the apps2sd native as well.
Sent from my Milestone using XDA App

Lleviathan said:
I have this exact same problem - when I used the stock rom on my hong kong milestone and overclocked modestly (800 52vsel) I was fine. As soon as I installed my first rom (in my case Shadowmod 2.5 via update.zip from AOR 3.3) I had this problem. It happens most often when the keyboard is open.
In additon to the screen yellow/red colour problem it will also just go blank, while the touch buttons stay lit. For either problem, simply turning the screen off and on again using the power button clears it, so it is more annoying than a show stopper.
Now I am using the APAC jan 25 leak and still have the issue. I only used an sbf to install the vulnerable recovery, and have used nandroid/updates to install everything else (never used the GOT thing). SBFs are annoying for me as I have a mac.
Anyway, I plan to recover my stock 2.1 nandroid and see if the problem is still there. Too bad, I love the battery life of the 2.2 roms, and the apps2sd native as well.
Sent from my Milestone using XDA App
Click to expand...
Click to collapse
Wow I thought I was the only one with this problem. I have been testing with different kernels and ROMs. Well, basically every ROM posted on this forum, and the new and old kernels. I have also tried the leaked 2.2.1 sbf as well as the offical 2.2.1 release SBF(UK and EU version). Played with different clock speeds. They all have the same issue. The only thing that doesn't have that issue are the original 2.1-update1 and the GOT sbf. I'm using GOT sbf so I could use app2sd, but the battery life is absolutely horrible.

[ROM] [2.3.6] Blur Daily Driver Rom + Webtop [45.21.78] [Dec10]

This is based on the official 4.5.2A-51_OLL-17.8 firmware (its the 2.3.6 Bell rom) and will work with both INTL & AT&T users. Most of the Blur apps have been updated in this version with new looks and features. The Camera on this version is really good. Takes much better images then any of the other BlurCamera's I have tried. Also the gallery is a huge improvement over the older ones, looks much better and a lot faster. Plus as this is the Bell firmware it hasn't got all the AT&T menus in the settings.
The only changes I have made is removed the bundled Bell apps plus added a few tweaks that I see as a must as it fixes or addresses issues that people have with the default Atrix software.
If anyone wants to fork this and add extra features please feel free to do so. You do not need to ask me before hand. I am even willing to host the ROM if you have no where to store it. So if you feel you can improve upon the ROM please do.
Changes Made:
The ROM is SuperCharged.
Its Rooted and has Busybox installed.
Fully DeOdexed and zipaligned
No changes made to the theme so no more disappearing status bar.
1080p video recording and 5 finger multi touch.
Raindrop Fix
Beats Audio + XLound
Bravia HD Mobile
Jug6 Battery FIX + tweaks I have made. Gives the best battery performance of any Blur ROM when set to 1.0 GHz.
Improved AGPS
Adblocker
faux123 026 1.45 GHz kernel with a CPU app to under-clock it for even better battery life.
Using the CM7 APN list. AT&T users that are having data problems try this.
Due to this only having a few locales I have added MoreLocale 2 so you can select your language. I'm from the UK and its not one of the locales that is listed in the blur setup. It can be set to English UK, its just a bit of a pain setting up as you need to skip setup, select MoreLocale 2 and put in en GB and then run blur setup. But you only need to do this once. So its not a huge deal. This also goes for anyone else that haven't got their locale listed. Just skip the blur setup and select MoreLocale 2 and select your locale.
Root Uninstall is also added so you can easily remove system apps you don't want. Its also a pretty nice app to manage your normal installed apps.
You install this like you would with any other ROM. Make sure you have a fairly well charged phone before attempting flashing this. Because this also comes with the webtop it does take awhile to install.
*NEW* [Dec 10] Vanilla Download: 423 MB
http://tinyurl.com/vanilla-stock-blur-webtop
MD5: 6e08268f5798123664f9ec4b15d7bfd1
Wish/To-do list:
LS HDMI
WebTop over HDMI
HDMI Mirroring
Toggles in notification bar - Can now be added with this zip.
Multilingual in blur setup.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
IF YOU GET A BOOTLOOP PULL THE BATTERY AND REBOOT.

will this work for att guys too?

looks good
any way to make the luncher with 4 rows instead of 5?

miko85 said:
will this work for att guys too?
Click to expand...
Click to collapse
Unsure if it will work as is, but if you install the ATT kernel from here after flashing the ROM it will work then.

wow makes sense im back to nottach right now been on miui and cm9 for so long i forgot how to work factory **** i will reply back after flashing thanks for your work

I had stock 2.3.6 on my bell atrix when I first rooted my phone back in February???

ATRIXXIRTA said:
I had stock 2.3.6 on my bell atrix when I first rooted my phone back in February???
Click to expand...
Click to collapse
I am from the UK. We haven't seen a 2.3.6 update. We could get 2.3.6 working with a custom kernel but I had problems with random reboots and calls getting cut off. It also had really bad battery life and over heated often. But this version is using the new bell kernel that was only released a few weeks ago here and I haven't had any of them issues since I have been using it.
The bell kernel is the first official kernel that will work for international users on 2.3.6

When I was on 2.3.6 my battery life was ****!! lol
Hopefully the kernel in this build is better then the one that came with the bell 2.3.6 update back in feb

I've got a UK Atrix and tried to install this 3 times earlier, just stays on the unlocked screen, i waited 20 mins before i did a battery pull. Come from CM7, and did all of the neccessary wipes first :-(
Sent from my MB860 using xda premium

EDITED

Does it contain polish language?

pinguy1982 said:
Unsure if it will work as is, but if you install the ATT kernel from here after flashing the ROM it will work then.
Click to expand...
Click to collapse
Works great !!!!!
Thanks, i have had many reboots with nottach4g and none now
Sent from my SGH-T989 using xda premium

i flashe this ROM like Nottach ROM ?!

OP..........Might want to change the thread title to reflect this has the 2.3.6 webtop and not the "new webtop", as some people may think it has Webtop 3.0 from the upcoming ICS update.

decker39 said:
I've got a UK Atrix and tried to install this 3 times earlier, just stays on the unlocked screen, i waited 20 mins before i did a battery pull. Come from CM7, and did all of the neccessary wipes first :-(
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
nevermind

wobo said:
Does it contain polish language?
Click to expand...
Click to collapse
Yes.
CaelanT said:
OP..........Might want to change the thread title to reflect this has the 2.3.6 webtop and not the "new webtop", as some people may think it has Webtop 3.0 from the upcoming ICS update.
Click to expand...
Click to collapse
Who in there right mind would think this comes with Webtop 3.0? Webtop 3.0 is just ICS in tablet mode. This is GB so would never be able to run Webtop 3.0. Also I give the version number of the Webtop in the OP. This is the latest webtop for GB.
Saying this is Webtop 2.3.6 means nothing. The latest Bell firmware that is 2.3.6 is running an older version of webtop. That version comes with Firefox 7.
decker39 said:
I've got a UK Atrix and tried to install this 3 times earlier, just stays on the unlocked screen, i waited 20 mins before i did a battery pull. Come from CM7, and did all of the neccessary wipes first
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Try wiping dalvik cache or re-downloading. Could be a bad download.

capercb said:
nevermind
Click to expand...
Click to collapse
What's that supposed to mean ??
Sent from my MB860 using xda premium

decker39 said:
What's that supposed to mean ??
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
i was having the same problem as you . try everything and still nothing ...i tried twice and nothin ..thats all

I think its likely that this is in fact NOT stock 2.3.6 but just a striped down version of the 2.3.6 Nottachtrix rom. i'm pretty sure that stock 236 doesn't have the toggle in the notification area. and in the first post for this rom it says based heavily on Notatchtrix.
I have tried EVERY rom, available for attrix in every flavor flashing multiple time to try to achieve stability and maximium hacability and performance. i think i'm sad to say i'm at the end of my tether as this place were all searching for just doesn't exist.
I regularly return to the only real rom to supply true stability and regular performance. 2.3.4 international ram fix.
On top of this not being a true stock rom. it's not perfect and i wish i could have some of the features of notachtrix but without the reboots and un-reliable behaviour.
I think the sun is most likely setting on our beloved Atrix. this may well not be the case for some US users. I wouldn't even mind being able to get hold of the TRUE stock SBF for my handset which i know just isnt available i have tried two orange sbfs that are in circulation and neither are quite right. 2.1.1 and 1.3 something.
We all need to appreciate that Nottachtrix is pretty much as good as it gets for us and if your after stability then use 234! simple.
i invite the opinion of others who consider me wrong!

Hi installed this rom got unlock screen hang so flashed 2.3.6 kernel works now but me fingerprint reader is not work can anyone help?

Warning cm9/cwm bricks (Spam/solutions/support thread)

hello everyone,
please post the problems here i try everything to get you guys out of trouble!
do not spam the cm9 thread spam here
i read sometimes here since today that some users had brick there tablet by installing the new cwm 6.0.1.2 or the CM9
the problems are:
# cwm version broken
# the 3.1 kernel is broken
after you have flashed one of these things your tab will stay black!
we still sourcing for a solution
kallt_kaffe's tab is also bricked lucky my tab is still alive!
very sadly for alk the peoples that have bricked there tablet and kallt_kaffe good luck i hope you can get your tab up and running again!
#YOU HAVE BEEN WARNED#

support
SUPPORT:
we have not found any working solutions yet as we have found one you will hear from me
maybe this will work: http://forum.xda-developers.com/showpost.php?p=31166314&postcount=3
or this maybe: http://forum.xda-developers.com/showthread.php?t=1478361
ALWAYS FEEL FREE TO PM ME!
or message me:
[email protected]
[email protected]

you might want to change the title.
bricks brick support? lol
would be great it getting bricked would get bricked and bricking your tab would no longer be "supported"

pseudoheld said:
you might want to change the title.
bricks brick support? lol
would be great it getting bricked would get bricked and bricking your tab would no longer be "supported"
Click to expand...
Click to collapse
haha yes im using swype on my tablet so there went something wrong i think
CHANGED!

i flashed the latest error prone cwm and luckily didn't have any issues. now im contemplating flashing back the old one 6.0.0.8 i think but i don't want to risk getting a brick whilst flashing back the old cwm.
does the brick only occur when formating something? is there any further info on that.
i think i will just keep my tab running as it is for the time being until there really is the need to flash sth (ie ics 7300 coming out) then i will try and go back to the old cwm

pseudoheld said:
i flashed the latest error prone cwm and luckily didn't have any issues. now im contemplating flashing back the old one 6.0.0.8 i think but i don't want to risk getting a brick whilst flashing back the old cwm.
does the brick only occur when formating something? is there any further info on that.
i think i will just keep my tab running as it is for the time being until there really is the need to flash sth (ie ics 7300 coming out) then i will try and go back to the old cwm
Click to expand...
Click to collapse
you can just flash back from 6.0.1.2 i have also done that now running on 6.0.0.8!
now i need some sleep see ya tommorow guys!

i have problem after using cm10 preview and the cmw from kallt_kaffe thread , it's probably cmw that caused the problem because JB was running smooth without any issues but when i tried to restore the stock HC the cmw stuck for some time but i was able to return back to HC .
after this the device was lagging a lot and couldn't enter cmw again the screen was black but the device still wasn't dead , i managed to turn it off and reboot it again and used it for two days before it's completely dead and connects only as APX device, i will try you the first method you posted and post back here .
there also this method form tab 10.1 sections for the unlocked devices: http://forum.xda-developers.com/showthread.php?t=1130574]
my device is locked and can't Bass (rcm version 0x4) error . so if there is anyone can help figuring out or providing the secure boot key for the locked devices that will be great .

Im not really sure what makes this bugs happen..
But this issues is not new for me in galaxyNOTE gt n7000 and Sgs2 I9100 we call this as EMMC superbrick..
It happen in ICS kernel stock if you operates some EMMC_CAP_ERASE in kernel such as wiping your data or system.. Format.. Or deleting large file in recovery operation or factory reset in EMMC with firmware revision 0x19(firmware of this chip)..
It cannot recover with regular utility like JTAG coz This superbrick makes EMMC faulty in /data partition or /system partition blocks..
If you go to Samsung Service Centre.. Your device should be on mainboard replacement..
Sorry for my english.. You could use this app for testing your emmc has a bug or not..
If you had the emmc bug.. Dont use any recovery from ICS sources until someone with expert knowledge confirm that everything is fine..
Please read this thread for complete issues and discuss..from recognized developer entropy512
http://forum.xda-developers.com/showthread.php?t=1633938
Edit:
After testing i got my EMMC had a bugs warning from chainfire got brick bug app...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I've tested my tab apparently it got the bug too. So, have anyone know what the problem exactly? Is it the ICS kernel or CWM which causing the brick?
---------- Post added at 02:26 AM ---------- Previous post was at 02:21 AM ----------
Is it safe to flash KK's CM10 ROM cause it still using GB kernel? And what CWM version to use for flashing? I know CWM versions 5. cannot use to flash CM10. Thanks

nexus_g said:
I've tested my tab apparently it got the bug too. So, have anyone know what the problem exactly? Is it the ICS kernel or CWM which causing the brick?
---------- Post added at 02:26 AM ---------- Previous post was at 02:21 AM ----------
Is it safe to flash KK's CM10 ROM cause it still using GB kernel? And what CWM version to use for flashing? I know CWM versions 5. cannot use to flash CM10. Thanks
Click to expand...
Click to collapse
Use CWM 6.0.0.8 NOT CWM 6.0.1.2!
You still have the 2.6.36.4.... Kernel Yes I know You can just upgrade to cm10 no problem!

nexus_g said:
I know CWM versions 5. cannot use to flash CM10. Thanks
Click to expand...
Click to collapse
I can't recall reading that before... What happens if you would do so?
Kallt_kaffe is currently recommending 6.0.0.8, post 2 of cm9 thread.
I heard of changes in the nandroid backup file structure in 6.x that I don't like, personally, but that's IMHO I'm still on 5.1 because the menu structure of 5.5.0.4 is incomplete (e.g. no shutdown)

fred_be9300 said:
I can't recall reading that before... What happens if you would do so?
Kallt_kaffe is currently recommending 6.0.0.8, post 2 of cm9 thread.
I heard of changes in the nandroid backup file structure in 6.x that I don't like, personally, but that's IMHO I'm still on 5.1 because the menu structure of 5.5.0.4 is incomplete (e.g. no shutdown)
Click to expand...
Click to collapse
From what I remember from the cm10 or AOSP JB thread, somebody tried to use cwm 5. to flash cm10 and he was getting error massage and cwm won't let it flash. That is why persoot and KK recommend cwm 6.

Could someone confirm using the good old CWM 6.0.0.8 or below and has flash ICS kernel and do wipe recover and survive the brickbug? Thanks.

safariking said:
you can just flash back from 6.0.1.2 i have also done that now running on 6.0.0.8!
now i need some sleep see ya tommorow guys!
Click to expand...
Click to collapse
Could you tell us what is the best way to flash back to CWM 6.0.0.8? Do you use cwm 6.0.1.2 or Odin? Thanks

nexus_g said:
Could you tell us what is the best way to flash back to CWM 6.0.0.8? Do you use cwm 6.0.1.2 or Odin? Thanks
Click to expand...
Click to collapse
I have flashed CWM 6.0.0.8 from 6.0.1.2!

[Q&A] [ROM] [NIGHTLY] [Lollipop] [5.0] CyanogenMod 12.0 nightlies [3.0 kernel]

Q&A for [ROM] [NIGHTLY] [Lollipop] [5.0] CyanogenMod 12.0 nightlies [3.0 kernel]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM] [NIGHTLY] [Lollipop] [5.0] CyanogenMod 12.0 nightlies [3.0 kernel]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

[ISSUE]*Bluetooth audio + notification
Hi,
First of all, thanks Milaq for maintaining, with others, Android on this famous tablet.
I drop a short message to point out an issue. When connected to an external audio device via Bluetooth, the sound may become heavily saturated. This occurs while listing to music and receiving a notification. Typically while using Google Play Music, TuneIn or any music app and getting notified of a new Tweet, a new mail or any kind of other notifications.
In this case, the amplification factor applied to the general audio level seems not to be restored the right way after the notification is played: a factor over 100% is applied and a too loud signal is sent out, producing an heavily saturated sound. Fixing this manually is very easy: simply press Volume Down or Up (even if already at the maximum level) to instantly restore the audio signal to its normal level.
This issue seems to be related to CM12 as, with CM11, it worked fine for months with the same devices and same apps.
Do not hesitate to get in touch if I can provide info or logs.

Wow, i will have to say this ROM was much more stable that i expected. Dirty flashed from jcsullins' 1125 CM11 build on Philz. I did make the mistake of not flashing the latest gapps, so Google Play Store did not work, but that was fixed by reflashing with Philz, using the right gapps zip this time.
I have had two reboots and an SOD thus far, the reboots likely being memory issues, and the SOD from having a passcode, which i have fixed by changing lock screen security. Weirdly enough, i actually got a performance boost with this ROM on the same processor settings, running Geebench 3. Will post images once i have the chance.
EDIT: Hmmm, just loaded the 0121 build, and it doesn't seem to be able to read the webOS partition?
EDIT 2: Rolled back to the 0118 build, and still the File Manager can't read the webOS sdcard. Is this intentional, or a bug that's being worked on?

Thanks for the Lollipop nightly release
I have two 16GB touchpads running Milaq's nightlies since KitKat days. Firstly thanks for the nightly builds.
Lollipop (build from 1/22) seems to be running great on the touchpads. I have both overclocked to 1782 MHz . Very snappy. Previously on KitKat the Antutu scores came to about 14100 on both my touchpads. Now the scores are in the 16100 range. Good improvement in performance.
Also on KitKat, videos would stutter when using Firefox. With Lollipop, no issues. Overall big jump in usability.
There are some random reboots just like everybody else. Not a big deal.
Solid release. Thank you, Milaq.

Kernel 3.0 vs 3.4
What are the advantages of going to kernel 3.4 over 3.0?
Milaq's nightlies use 3.0 kernel where as there are other ROM packagers using kernel 3.4. I am not complaining. Just asking why some ROMs use 3.0 and some use 3.4. What are the differences?

does anyone know how to fix the wifi issues within tenderloin? it seems with every rom i flash my tablet still has issues streaming content from my computer (using Plex or similar software) because the wifi cuts out. sometimes it crashes the tablet, other times i have to restart or turn off and on the wifi/

vishnumrao said:
I have two 16GB touchpads running Milaq's nightlies since KitKat days. Firstly thanks for the nightly builds.
Lollipop (build from 1/22) seems to be running great on the touchpads. I have both overclocked to 1782 MHz . Very snappy. Previously on KitKat the Antutu scores came to about 14100 on both my touchpads. Now the scores are in the 16100 range. Good improvement in performance.
Also on KitKat, videos would stutter when using Firefox. With Lollipop, no issues. Overall big jump in usability.
There are some random reboots just like everybody else. Not a big deal.
Solid release. Thank you, Milaq.
Click to expand...
Click to collapse
Same here, I was getting Geekbench 3 scores in the 700s with KitKat on 1782 MHz with performance governor. With the same processor settings I have scores over 800, which is really nice.

Great ROM but getting random reboots,hoping this will get better soon,running 25/01/15

Updated to 27/01/15 and up to now no random reboots,well done to milaq and all the other devs involved in keeping the touchpad alive and up to date, what a fantastic ROM.

garydclarke said:
Updated to 27/01/15 and up to now no random reboots,well done to milaq and all the other devs involved in keeping the touchpad alive and up to date, what a fantastic ROM.
Click to expand...
Click to collapse
Sounds great. Can anybody else confirm this, the 0124 build is running well enough for me, haven't had a lot of reboots and I've downloaded quite a few builds this month. Also, does that build read both SD cards, the 0124 build does not seem to be able to do so for me.

Hey guys! Coming from jb to lollipop. Had a bit of an accident, assumed I could simply update the tcwm recovery, then install the nightly build - but saw someone's upgrade went slightly different and they formatted /system in between that step - this ended up costing me. I can't install from the zip, I get what looks like a corrupted file system. I can't use the tp toolbox to fix the android partition (fsck) and my former android won't boot. I can't look at the fs to resize through that utility either. I was wondering is there a simple few step process to go about upgrading to this ROM? Or do I need to try and start from scratch (reformat as webos only and work through installing android on the tp from tutorials)? I am able to see/mount my "sdcard" and I do have cwm recovery manager access.
Sent from my D6603 using Tapatalk
edit/update: I have erased android and attempted to use TPToolbox to install the Gapps, Recovery and Rom from the OP - but I keep getting an incompatible Rom error when I go to install android. Anyone know what I need to do? Can I not go directly to 5.0, and I need to install 4.4 first? I resized the partitions as well - everything looks good from that part. I tried renaming the CM-12-20150129-UNOFFICIAL-tenderloin.zip to CM-12-20150129-tenderloin.zip but that hasn't worked, neither has downloading other nightlies for this purpose. Any suggestions? in order to use TPToolBox do I need to change the name to CM-11-20150129-tenderloin.zip in order to install this rom through that? Or do I just install 4.4.2 and use CWM to update after resizing some partitions?
edit/update2: After installing kit kat through tptoolbox the proven way - I updated cwm with the one from the original post, and the rom and gapps installed perfectly. Beautiful rom, beautiful work. I love and am thankful for this scene.

futurepr0n said:
Hey guys! Coming from jb to lollipop. Had a bit of an accident, assumed I could simply update the tcwm recovery, then install the nightly build - but saw someone's upgrade went slightly different and they formatted /system in between that step - this ended up costing me. I can't install from the zip, I get what looks like a corrupted file system. I can't use the tp toolbox to fix the android partition (fsck) and my former android won't boot. I can't look at the fs to resize through that utility either. I was wondering is there a simple few step process to go about upgrading to this ROM? Or do I need to try and start from scratch (reformat as webos only and work through installing android on the tp from tutorials)? I am able to see/mount my "sdcard" and I do have cwm recovery manager access.
Sent from my D6603 using Tapatalk
edit/update: I have erased android and attempted to use TPToolbox to install the Gapps, Recovery and Rom from the OP - but I keep getting an incompatible Rom error when I go to install android. Anyone know what I need to do? Can I not go directly to 5.0, and I need to install 4.4 first? I resized the partitions as well - everything looks good from that part. I tried renaming the CM-12-20150129-UNOFFICIAL-tenderloin.zip to CM-12-20150129-tenderloin.zip but that hasn't worked, neither has downloading other nightlies for this purpose. Any suggestions? in order to use TPToolBox do I need to change the name to CM-11-20150129-tenderloin.zip in order to install this rom through that? Or do I just install 4.4.2 and use CWM to update after resizing some partitions?
Click to expand...
Click to collapse
For the first part, you sound like you were trying to dirty flash a data-media build over a non data-media build, which I don't think can be done. I have a hunch, referring to your update, that you might be using an older version of TP Toolbox. Either that, or you're mixing recovery, gapps and ROM packages. Just my two cents.

Hello Milaq. Thank you for firmware. But I have a problem. How to fix it?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Ive got today's build going, and for some reason Kodi is goofing up and crashing when I try to add a SMB share. Is this happening to anyone else?

On the nightlies since sometime after 02/01, I have a problem of wifi turning OFF and ON randomly. This is happening on two touchpads. Anyone else have this problem?

vishnumrao said:
On the nightlies since sometime after 02/01, I have a problem of wifi turning OFF and ON randomly. This is happening on two touchpads. Anyone else have this problem?
Click to expand...
Click to collapse
Yes WiFi is very random on builds from this month. On mine its quite frequent. I completely wiped my touchpad but the issue still remains.

wifi
WiFi seems to be staying on in the 2/21 build. Well spoke to soon now comes on for about 10 minutes goes off and stays off

basrawi said:
Yes WiFi is very random on builds from this month. On mine its quite frequent. I completely wiped my touchpad but the issue still remains.
Click to expand...
Click to collapse
I think this problem is not with the builds. Seems to be a problem with the router. I have two routers. The TM-AC1900 is the primary and an E3000 running tomatousb as a backup. With the TM-AC1900, I had constant wifi turn ON/OFF problem. I connected the backup. No issues! Wifi work like a charm.
Check the Android 5.0 threads started by flintman or invisiblek. I can't find the posts now. But I remember reading that people using the other ROMs have the same problem and they traced it to something to do with config on some routers.

vishnumrao said:
I think this problem is not with the builds. Seems to be a problem with the router. I have two routers. The TM-AC1900 is the primary and an E3000 running tomatousb as a backup. With the TM-AC1900, I had constant wifi turn ON/OFF problem. I connected the backup. No issues! Wifi work like a charm.
Check the Android 5.0 threads started by flintman or invisiblek. I can't find the posts now. But I remember reading that people using the other ROMs have the same problem and they traced it to something to do with config on some routers.
Click to expand...
Click to collapse
I have a another router. I will give it a go. Thanks for the tip

How can I have auto update when new version comes out for this ROM? Evervolv ROM has it built-in settings and ROM manager didn't work for this.
Edit: found it in the Apps
Sent from my TouchPad using Tapatalk

[Q&A] [ROM][Shamu][5.1]Temasek's UNOFFICIAL CM12.1 Build V9.5 April 8

Q&A for [ROM][Shamu][5.1]Temasek's UNOFFICIAL CM12.1 Build V9.5 April 8
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][Shamu][5.1]Temasek's UNOFFICIAL CM12.1 Build V9.5 April 8. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Can't install 5.2 after 5.0.2
Temasek's Unofficial from apascual89 is the only ROM I've installed on my Nexus6 from stock, excellent work guys!!!! But... actually I have the same problems as some of you: I flash the ROM, GAPPS and Kernel (non encrypted) and enter on bootloop... I made a full wipe (I have a backup from 5.0.2) and updated recovery. No idea what radio, bootloader, kernel, gapps or what kind of order of installation is failing.
Well, patience... I'll stay on 5.02, excluding "OK google" everything works great! :fingers-crossed:
My question is if I will ever see sometime in the future a Temasek 5.2 ROM with a cool unecrypted, radied, kerneled, rooted, and OkGoogleled precious piece of software inside one unic treasured ZIP. :silly:
Thanks all, amigos

nianoniano said:
Temasek's Unofficial from apascual89 is the only ROM I've installed on my Nexus6 from stock, excellent work guys!!!! But... actually I have the same problems as some of you: I flash the ROM, GAPPS and Kernel (non encrypted) and enter on bootloop... I made a full wipe (I have a backup from 5.0.2) and updated recovery. No idea what radio, bootloader, kernel, gapps or what kind of order of installation is failing.
Well, patience... I'll stay on 5.02, excluding "OK google" everything works great! :fingers-crossed:
My question is if I will ever see sometime in the future a Temasek 5.2 ROM with a cool unecrypted, radied, kerneled, rooted, and OkGoogleled precious piece of software inside one unic treasured ZIP. :silly:
Thanks all, amigos
Click to expand...
Click to collapse
Hey man! Saludos! I'm going to try and get to the bottom of this.

Andres, thanks a lot for your replies!
As you can see I finally decided to write my question into the Q&A thread for noobs, I feel alone, but there's no need to use private messages
As I said, I can wait until somebody describes a reasonable method to check what versions I'm running and which new ones I should install, I don't want to be the first to have a definitively bricked Nexus 6. But since I made a recovery from backup I'm gettinfg FC's and my system becomes more laggy, but everything "is working great"... During the last month I have read in the forum many conflicting reports about moving from one version to another or use different kernels as Hydra, Vindicator, etc...
I don't want to go stock, I love the way this ROM works... What do you recommend me to do?

Ok, after reading successful stories I finally have been able to install 5.2 from 5.0.2.
Well, may be it's going to be useful for some of you:
After full wipe I flashed from OTG/usb the ROM, GAPPS and chainfire's root, as last time, but I introduced the Hydra Kernel and It booted flawlessly. With 5.2 working I noticed 2 differences with 5.02:
-GPS stops sometimes (I'm an Ingress player) on one place and jumps to other...
- battery is draining much more than leankernel
So...I tried to flash leankernel from recovery and it stays in the CM logo... Flashing again Hydra kernel and works again.
Should I update with OTA on next @Apascual release? Will change my actual kernel? Any advice about?...
Thanks all for your patience.
Sent from my Nexus 6 using XDA Free mobile app

Is there any way to fix this? I am connected to my network and everything works OK, but it messes with my OCD lol. If it can't be fixed can I hide it possibly? It seems to only happen with cm based ROMs for me.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(the no service in the top left)

Anyone got data while calling working on latest build ?
Sent from my Nexus 6 using Tapatalk

kenbrownstone said:
Anyone got data while calling working on latest build ?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I'm on T-Mobile and it works after having toggled "Enhanced 4G LTE Mode" off and then on again. You will have to do this after every reboot. It seems to be an issue with the CM base judging by the fact that every 12.1 CM-based ROM I've tried exhibits the same brokenness in this regard. Hopefully they fix it soon because it's really annoying and inconvenient since it kicks data when a call comes in until it's toggled off and on again. AOSP-based ROMs fixed this issue within a week or so IIRC.

With Temasek 9.5 + HydraKernel V2.0 my 4G connection is working while making phone calls. I'm in Spain and my operator is Orange.
Still having minor issues with this kernel, like a small "robotic crisp" in the speakers when playing games or the intermittent GPS stops... I'm also waiting for a stand alone Temasek installation with his own stock kernel...
Sent from my Nexus 6 using XDA Free mobile app

Hi all, congrats again to apascual & temasek for the ROM, it gets better day by day!
Just some sound problems... I heard some cracking and electronic buzz in the speakers (not in headphones) while playing some games, is like an interference with CPU or something like that. This is happening since the first 5.0.1 version. I didn't test on stock or other ROMS (my shamu only wants this unofficial cooked software). BUT... Today I changed Selinux to permissive and installed Viper4android, flashing the 4 .zip proposed in viper's thread and updated the sound driver to high quality. Finally all sounds are now much better, at least I cannot listen any sound glitch!
Just a question.. Is possible to include ViperAudio on the next ROM updates instead of soundFX??? It is working perfectly!
Let me know your thoughts
Sent from my Nexus 6 using XDA Free mobile app

When I hide clock in status bar it pops back up! Never stays hidden..is there a fix for that? Thx in advance
---------- Post added 26-04-2015 at 12:12 AM ---------- Previous post was 25-04-2015 at 11:39 PM ----------
Why do we have Q&A and we don't get answers?

..
---------- Post added at 11:02 AM ---------- Previous post was at 10:51 AM ----------
Does this ROM still utilize SuperSU for privilege escalation, instead of the built-in mechanisms in CM 12.x?

Supersu is built-in in the ROM. Not necessary to install nothing, it works!
EDITED: oh..sorry.. After a clean install I realized that we need to flash root. But it persists after dirty flashings. I'ts ok for me.
Sent from my Nexus 6 using XDA Free mobile app

At the moment the build in root mechanism doesn't work. ?

I've been dirtyflashing for a long time, but last build made swype gesture disappear from the keyboard. I tried to do a fresh install but it is still missing. I've read other users with same problem. Any working suggestion? Can anything to do with installed new "handwriting app from Google"???
Thanks all
Sent from my Nexus 6 using XDA Free mobile app

Anyone else experiencing random reboots especially when you try to wake up the phone from sleep?
running 05/12 build with elementalX 1.06, pa gapps and latest viper4android. No other tweaks like xposed etc.

Yes, I'm also having random reboots under all conditions... While sleeping, gaming, switching from 4g to WiFi... It happens 5 or 6 times a day and it's annoying.... I have last ROM update and no tweaked kernel or sound or whatever... I have no explanation...
Sent from my Nexus 6 using XDA Free mobile app

Call recording disabled in newest Temasek's Nexus 6 rom?
Hi!
I would like to confirm if call recording ia disabled in Temasek's Nexus 6 rom. Anyone know for sure? I found earlier mention that it should be enabled, but not sure about the newest version.
When I tried recording with Total Recall, I got completely silent recording file. All internal recording strategies A, B, C and Rooted act the same way. Device is rooted. If someone has solved the silent recording problem, please advise

kunnis said:
Hi!
I would like to confirm if call recording ia disabled in Temasek's Nexus 6 rom. Anyone know for sure?
Click to expand...
Click to collapse
call recording is 100% functional. after a call has connected open the three-dot menu and select record call. you can access to the recording from the call history screen.

I'm on sprint with my N6. I'm seeing references to a sprint.zip. Why would this be needed? I did search on 'sprint.zip' but I'm not finding a post that answered that question.
Been using this ROM since its early releases. I've never had trouble with data or calls. Actually I've never had any trouble that wasn't self induced.