Hey,
I just flashed the latest Quark's KitKat nightly (20141007), was on CM7.2 previously, is it supposed to be so much slower/more sluggish or did I do something wrong?
Any action takes at least a second (opening the menu, going into any submenu in the settings, ...), the keyboard takes 5s to popup when I tap an input field, call screen takes a few seconds too, if I tap the Google Now search bar I can only start typing 10s later, ...
The display and touch seem responsive, scrolling between my home screens is fluid and doesn't lag behind, but opening anything is slow.
Any idea?
It's a red lens MB525 Defy.
I went straight from CM7.2 to CM11, installed using the guide at quarx2k.ru, didn't install the 2.2.2 sbf (or any sbf).
Edit: Actually, just realised I installed new_boostrap.zip from recovery (as seen in another guide here) instead of doing the terminal part. Is that a problem?
Flash 08/10 nightly with the steps in the first post of kitkat thread, I don't know what you mean with "the terminal part"
DiegoxG said:
Flash 08/10 nightly with the steps in the first post of kitkat thread, I don't know what you mean with "the terminal part"
Click to expand...
Click to collapse
(The tutorial on quarx website makes you install the bootstrap manually via shell or terminal instead of recovery but I guess that's the same)
This KitKat thread right ? http://forum.xda-developers.com/showthread.php?t=2515036
That's how I did it actually. Install TWRP, install new_bootstrap, reboot, install resize, reboot, install CM11. Then I also installed the minimal gapps, and did a Factory Reset in android settings (to get the google first boot set-up).
Edit : Lock screen is super slow and if I check cpu usage after unlocking, Lock Screen is using over 50%...
DinoD2 said:
(The tutorial on quarx website makes you install the bootstrap manually via shell or terminal instead of recovery but I guess that's the same)
This KitKat thread right ? http://forum.xda-developers.com/showthread.php?t=2515036
That's how I did it actually. Install TWRP, install new_bootstrap, reboot, install resize, reboot, install CM11. Then I also installed the minimal gapps, and did a Factory Reset in android settings (to get the google first boot set-up).
Edit : Lock screen is super slow and if I check cpu usage after unlocking, Lock Screen is using over 50%...
Click to expand...
Click to collapse
You don't need to do a factory reset in order to get the wizard setup.
That's strange, those issues shouldn't occur. Try with 09/23 build
DiegoxG said:
You don't need to do a factory reset in order to get the wizard setup.
Click to expand...
Click to collapse
Yeah I knew there was probably a better way but I hadn't installed anything yet anyway.
DiegoxG said:
That's strange, those issues shouldn't occur. Try with 09/23 build
Click to expand...
Click to collapse
Hmm, where can I find older builds? There's only the latest 7 on quarx2k.ru and quarx.cm-for.us
Edit: I installed the 10/12 nightly, still laggy (maybe a tiny bit better, not sure). Also, the phone seems to reboot by itself from time to time.
DiegoxG said:
Try with 09/23 build
Click to expand...
Click to collapse
Hm. I got cm-11-20140923-NIGHTLY-mb526.zip, tried installing it from recovery, got the following error : "E:Error executing updater binary in zip '/sdcard/cm-11-20140923-NIGHTLY-mb526.zip".
Then I had no boot anymore (TWRP was saying I had no OS installed).
I got a newer (october) nightly and install worked for this one.
Am I not compatible with the older releases becuase I installed the new bootstrap and the partition resizing?
Is there a way to undo it or do I have to install an SBF?
Edit: Yep, installed an SBF, rooted, installed september CM11 and it worked. It seems faster too, no more big lags, but still slower than CM7.2 imo, I think I'm gonna downgrade.
DinoD2 said:
Hey,
I just flashed the latest Quark's KitKat nightly (20141007), was on CM7.2 previously, is it supposed to be so much slower/more sluggish or did I do something wrong?
Any action takes at least a second (opening the menu, going into any submenu in the settings, ...), the keyboard takes 5s to popup when I tap an input field, call screen takes a few seconds too, if I tap the Google Now search bar I can only start typing 10s later, ...
The display and touch seem responsive, scrolling between my home screens is fluid and doesn't lag behind, but opening anything is slow.
Click to expand...
Click to collapse
For keyboard remove if u don't use it swipe and suggestions
Related
Check progress in DEV section http://forum.xda-developers.com/showthread.php?t=1562595
( I have posted less than 10 posts, so I can't write in the dev section. )
Stupid question : is it using Holo?
And, if it is based on CM9, it is rooted, isn't it?
If WiFi works, I'm SURELY going to try this!
I installed it yesterday. Wifi works, it uses Holo, hat root and performs better than I expected.
Thx.
I' ve put it on. It's really laggy, but it works!
It's a good start, but if this is the best performance the legend can give, I think I won't ever change definitevly to ICS. Maybe it can be optimizated for the Legend hardware to become smoother.
Thanks for testing, but it has not got hardware acceleration yet. For testing purpose, you could overclock it up to 787 MHZ safely, and the overall performance get better notably.
/=\lex said:
Thx.
I' ve put it on. It's really laggy, but it works!
It's a good start, but if this is the best performance the legend can give, I think I won't ever change definitevly to ICS. Maybe it can be optimizated for the Legend hardware to become smoother.
Click to expand...
Click to collapse
Yea is pretty smooth overall eventhough hardware aceleration is not working, this port looks really promising,
Tried it yesterday and in My view its the smoothest ics ROM ever tested.i had some fcs but will try Tor correct rights via rommanager.if GPS is working i will use this one.its a must Have for me.
Sent from my Legend using XDA
Thanks for testing, but it has not got hardware acceleration yet. For testing purpose, you could overclock it up to 787 MHZ safely, and the overall performance get better notably.
Click to expand...
Click to collapse
I'll try keeping it on for more time. By my first impression, it doesn't look so buggy, I think it is also quite stable. I'll tell you if I find anything.
Anyway, this is a great ROM, thanks for your work!
EDIT : Stupid question : to install GApps I have to flash the zip, right?
EDIT 2x : Yea, it was a very stupid question. Flashed from clockwork recovery. Works perfectly.
Its getting better and better. but still GPS not working. Hope you get it fixed soon.
Realy great job!!!!!
really good job. Just need GPS and Camera.
Hoping for 2.5 soon...also hoping based on Android 4.0.4.
How is work going?
Sent from my Legend using XDA
I have a problem with the latest 3.0 version.
After i flash gapps i keep getting boot loops.
If i dont flash it and just flash the rom it boots fine.
Dont know what the problem is. Can someone help me?
I have the exact same problem as DareFace, but I think zeubea is aware of the problem.
zeubea-cm-9.0.0-ALPHA3.0.1 and Google Apps
I tried install this ROM multiple times today, everything works until i install gapps (full or tiny). After that phone enters infinite boot-loop (HTC logo on white background).
Radio 7.13.35.05
Bootloader HBOOT-1.01 (S-ON)
ClockworkMod Recovery 5.0.2.0
Edited @ 08:31PM GMT+2
After installing gapps over gapps works as a charm. That's weird...
I had the same bootloop problem until I installed another kernel that Zeubea provided. It's till get some fc's, mainly for clock and email, but the email still works, clock is inaccessible atm.
It's even better than cm 7.2RC1, running oc'ed at 787mhz ! It's so smooth and beautiful. Let's hope that the gps and camera will get fixed soon. If I had capabilities to donate, I so would do it.
Thanks Zeubea! The Legend community loves you, keep up the wonderful work of making our ICS dreams come true when htc can't and won't deliver.
The reason for bootlooping is the clock issue.
The default clock in 3.0.0 is 806MHz - something every Legend doesn't handle, so it bootloops.
The 3.0.1 version has this "problem" fixed.
I faced another issue releted to sounds. I change both ring and notification sounds and after some time i realise that they are reverted to default!
I have this weird thing where the danish keyboard force-closes.
It's everytime i type the word "lige". It doesn't do it with the english keyboard
I've tried to turn off the spelling correction, since it's in english, and there isn't a danish one, but it doesn't help.
Other than that it's great
bootlooping after flashing cm9 gapps, possible fix
boots up normally after flashing the zip in CWM, but after flashing gapps it bootloops, and after awhile of countless flashing i discovered it bootloops even before flashing gapps, so i tried different step to flash it and finally it boots up normally, here's what i did :
1) full wipe, dalvik cache and cache partition, factory reset
2) flash the main cm9 zip
3) full wipe, dalvik cache and cache partition, factory reset (again)
4) flash gapps (not tiny version)
5) reboot, if it boots up normally thats great, if not its ok, continue to step 6
6) boot into CWM
7) dont wipe or anything*
8) flash the main cm9 zip
9) instead of rebooting device, continue by just flashing gapps (not tiny version)
this were the steps i did to fix the bootloops after flashing gapps, apparently the gapps tiny version is not compatible with cm9 on the htc legend thats why i stick to the normal gapps file, i hope this helps anyone of u experiencing the bootloops after flashing gapps
I have some kind of problem with wifi connection. If "Keep Wi-Fi on during sleep" is set to "Only when plugged in". After I wake up phone wifi is turned on it cannot find any networks.
EDIT: Logcat trimmed to "network|wifi|power|conectivity" http://pastebin.com/pdUAbfDy
And terminal emulator displays an error "Unfortunately, Terminal Emulator has stopped" when I try to open it.
EDIT: Logcat http://pastebin.com/ChRUu3jS
Im new to Android world, so please help me.
Now, my Nexus 7 Wifi is now unlocked and rooted by your tutorial, and
flashed Xenon HD Custom Rom.
I was in Jelly Bean 4.2.2 before. And i found some site that says
XenonHD is updated to 4.2.2 version, so i try to get it, and installed it to
my device. But after evrything done, i checked my device's version and it
says 4.2.1, but im sure i downloaded the right one, dated April 2013, as
far as i know. So, my device was downgraded to 4.2.1
Question:
a) Is it just that easy for downgrading an Android device? Because on
iOS, there are lots of concerns first before you can actually do
downgrading..
b) After installing apps, i made a backup with Nexus Root Toolkit, and
after the backup process, it reboots, and i notice that something is
wrong, the X animation logo goes somewhere at the lower right, and
when it goes to lockscreen, since im locked on landscape orientation,
half right side shows first then the half left side, youll really say that, it is
not okay. I tried rebooting by XenonHD settings, i tried to turn off and turn
it on again, same thing happens, what should i do?
c) About XenonHD, is it just one theme available? or i can download more
themes elsewhere? can somebody point me to where can i do that?
d) should i be re-flashing for XenonHD 4.2.2? How would i do that?
e) And what more can i do to my device to achieve it AWESOMENESS
Thanks in advance..
a) Yes, on many android devices it's that easy to downgrade. You don't need to jump through all the hoops like iOS requires you to.
b) Sounds like something may have gone wrong during the install process. Perhaps you could post a picture of what it looks like.
c) not sure, never used it.
d) Guess that's up to you. If it's an upgrade then it could fix the screen issue you're having. You'd flash it the same way you flashed the 4.2.1 version.
I'm sorry for spoonfeeding.
zeneleven said:
a) Is it just that easy for downgrading an Android device? Because on
iOS, there are lots of concerns first before you can actually do
downgrading..
Click to expand...
Click to collapse
Yes. XenonHD says it's 4.2.2 though, so I'm pretty sure you flashed an old build or the dev forgot to edit some text to make it say 4.2.2.
zeneleven said:
b) After installing apps, i made a backup with Nexus Root Toolkit, and
after the backup process, it reboots, and i notice that something is
wrong, the X animation logo goes somewhere at the lower right, and
when it goes to lockscreen, since im locked on landscape orientation,
half right side shows first then the half left side, youll really say that, it is
not okay. I tried rebooting by XenonHD settings, i tried to turn off and turn
it on again, same thing happens, what should i do?
Click to expand...
Click to collapse
Flash a different ROM or reflash your current one. Backups shouldn't have any effect on the ROM; if the backup app you're using negatively impacts your experience, switch it (I use titanium backup). TWRP recovery also supports nandroid backups.
zeneleven said:
c) About XenonHD, is it just one theme available? or i can download more
themes elsewhere? can somebody point me to where can i do that?
Click to expand...
Click to collapse
From the ROM thread, it says it supports CM10.1 themes (theme chooser). Search "CM10 themes" on Google Play to find them, then go to your settings to apply.
zeneleven said:
d) should i be re-flashing for XenonHD 4.2.2? How would i do that?
Click to expand...
Click to collapse
First, download the ROM to your device (if you haven't already), and google apps.
Make a backup of your data (nandroid or Titanium backup or some other backup app).
Then hold the power button, and select either "reboot"/"restart" or "recovery".
If you select "reboot" and no option for "recovery" comes up, hold down the volume down key while the device is restarting, then navigate using the volume buttons once the bootloader pops up, to the "recovery" tab.
Verify that the recovery installed is indeed TWRP (TeamWin recovery). If it isn't stop, and get TWRP before continuing.
Once your recovery pops up, select "factory reset", and swipe.
Then, select "install" from the menu that pops up, navigate to the folder labeled "downloads" and select the ROM file, and then select "add more zips", then select the gapps (google apps) file.
After that, swipe the little bar to start flashing, then after it's finished, select "reboot system".
Once the thing has properly booted into the setup screen, set it up, and restore your data.
zeneleven said:
e) And what more can i do to my device to achieve it AWESOMENESS
Click to expand...
Click to collapse
Install M-Kernel and Trickster Mod (app).
Install Nova launcher.
Install fdroid (for freedoms).
Install MX Player.
Ive already re-flashed with XenonHD's latest update i think, and yeah its on 4.2.2. and still, got the lockscreen problem which i solved by changing the lockscreen orientation, locking it to portrait.. and got more error like "Apollo" and its launcher "has stopped" something.. and the voice dictation, exits when being used, wherever im in..
Now, im planning to switch to Cyanogenmod for 4.2.2, since it has few themes available.
About Kernel? Can someone help me how to do that? a great guide will be greatly appreciated, done searching and cant find it, i swear.
Thank you so much in advance
Hello, my problems started when switching from CM10.2 to try out a CM7.2 based ROM that was a stripped down version of MokeeOS. I disliked it so I then flashed the original CM7.2 and everything seemed fine, however I missed the app support of Android 4.2.2+ and decided to go back to CM10.1.
For some reason my phone switched off during the flashing of CM10.1 (Quarx's 9th of July build) and was screwed. I pulled up RSD Lite and went to flash an SBF and start again. I used this SBF [DEFYPLUS_U3_4.5.1-134_DFP-231_AU_SIGN_UCADEFYEMARAB1B80AA004.0R_PDS03C_USAJRDNGIBRANZ_P021_A030_Service1FF.sbf] Everything was fine and everything worked. I then went on to root the device so I could install CM10.1 and noticed I had trouble rooting with SuperOneClick. It always hung step #7 which said something along the lines of "cannot mount, are you root?". I hesitantly tried an APK based root called Farmaroot which surprisingly worked which then allowed me to install 2nd init recovery. Here's where it gets weird. I flashed CM10.1 and the corresponding version of GApps and rebooted and everything seemed fine. However the first thing I noticed is that it only asked me for my Google Account, not the device language or which Network I should connect to, I thought nothing of it for some reason and continued thinking everything ok. However I then noticed that the notification slider and the quick settings menu were both inoperative, no notifications or tiles could be seen. Pressing the home button did not work, nor did long pressing it to show currently open apps.
I reflashed CM10.1 using TWR and had the same problem. I then flashed CM10.2 and another version of GApps and had the same problem.
Is this a problem originating from the fact I could not root the device to begin with? I am pretty sure I also tried this SBF
[DEFYPLUS_U3_4.5.1-134_DFP-1321_AU_SIGN_SIGNED_UCADEFYEMARAB1B80AA004.0R_PDS03C_USAJRDNGIBRANZ_P020_A026_HWp3_Service1FF.sbf]
Where should I go from here? I'm currently in exam period so I am unable to extensively search for answers or mess around. The device is currently wiped.
I'm using a Defy+ by the way.
Thanks.
Defy+ can't be rooted by SuperOneClick. And I had those issues earlier. I tried a different gapps and it worked. Search and use TJKV's minimal gapps (in the General section).
hotdog125 said:
Defy+ can't be rooted by SuperOneClick.
Click to expand...
Click to collapse
Really? It's what I used to root it every time until now.
hotdog125 said:
I tried a different gapps and it worked. Search and use TJKV's minimal gapps (in the General section).
Click to expand...
Click to collapse
Oh wow this actually worked. Thanks!
woofdog said:
Really? It's what I used to root it every time until now.
Click to expand...
Click to collapse
That's not possible:laugh:
Framaroot method doesn't affect anything. Looks like some leftover data files to me
Sent from my MB526 using Tapatalk 2
Hello,
I have been trying to upgrade my nexus 4 to 4.4.4 or 4.4.3. I currently run the rom below and keep getting system update notifications. its downloading the update over and over and failing and killed my data plan lastnight.
When I flash a rom for 443 right now it looks to install fine. With some roms i get halfway through the config, Just after giving your name if im right. You can scroll down on the page, the arrow at the bottom of the screen that you are to click to go to the next screen turns from a down arrow to a right arrow but it never lets you click it to continue. im stuck. ive tried unclicking everything. My only safety is having the backup from 4.4.2 and i restore it back.
Some roms let me go all the way through the config but when its at the home screen and is giving you the quick tutorial, you click on the screen to continue and you can hear it click so it knows you touched the screen but it never goes further. again cant get to my homescreen to do anything. have to restore.
Ive been in this loop for a while now and just looking for any suggestions to why i cant put 4.4.3 or 4.4.4 on? Wouldnt call myself a noob with all of this but im kinda feelin like it now.
Nexus 4, Android Version 4.4.2
Kernel Version 3.4.76-NexusExperience-CAF
Nexus 5 Experience Release 3.1 CAF Kernel
Build Jan 23 2014
Build No KOT49H
Any suggestions would be appreciated. Thx
blacktuxnc said:
Hello,
I have been trying to upgrade my nexus 4 to 4.4.4 or 4.4.3. I currently run the rom below and keep getting system update notifications. its downloading the update over and over and failing and killed my data plan lastnight.
When I flash a rom for 443 right now it looks to install fine. With some roms i get halfway through the config, Just after giving your name if im right. You can scroll down on the page, the arrow at the bottom of the screen that you are to click to go to the next screen turns from a down arrow to a right arrow but it never lets you click it to continue. im stuck. ive tried unclicking everything. My only safety is having the backup from 4.4.2 and i restore it back.
Some roms let me go all the way through the config but when its at the home screen and is giving you the quick tutorial, you click on the screen to continue and you can hear it click so it knows you touched the screen but it never goes further. again cant get to my homescreen to do anything. have to restore.
Ive been in this loop for a while now and just looking for any suggestions to why i cant put 4.4.3 or 4.4.4 on? Wouldnt call myself a noob with all of this but im kinda feelin like it now.
Nexus 4, Android Version 4.4.2
Kernel Version 3.4.76-NexusExperience-CAF
Nexus 5 Experience Release 3.1 CAF Kernel
Build Jan 23 2014
Build No KOT49H
Any suggestions would be appreciated. Thx
Click to expand...
Click to collapse
im assuming that you you wiped data? you are flashing over a CAF based rom and kernel(cm), and general android is not CAF based. how and what are you flashing as well, stock 443/444?
simms22 said:
im assuming that you you wiped data? you are flashing over a CAF based rom and kernel(cm), and general android is not CAF based. how and what are you flashing as well, stock 443/444?
Click to expand...
Click to collapse
Wipe data/cache, dalvik wipe
I installed - [ROM+KERNEL][CM11][KTU84M][CAF&AOSP] Nexus 5 Experience - CM11 Based [R8.2 - 12Jun
im sure im missing a step here. its user error. in the past i flashed a rom and that was all i needed to do. Im trying to do this upgrade without connecting to a pc, its been in the closet for a while. thought of using the raspberry pi if i needed to.
blacktuxnc said:
Wipe data/cache, dalvik wipe
I installed - [ROM+KERNEL][CM11][KTU84M][CAF&AOSP] Nexus 5 Experience - CM11 Based [R8.2 - 12Jun
im sure im missing a step here. its user error. in the past i flashed a rom and that was all i needed to do. Im trying to do this upgrade without connecting to a pc, its been in the closet for a while. thought of using the raspberry pi if i needed to.
Click to expand...
Click to collapse
ok..
did you make a backup in recovery? if you did, try this, as a wipe isnt required to upgrade. restore your backup, boot up, then go back and dirty flash that rom over what you have. dirty flash means dont wipe a single thing. btw, when you flash a rom, it automatically wipes dalvik and cache, so you never actually have to do that when rom flashing(and never have to wipe anything for kernel flashing).
when i did that i can see icons on the homescreen which is different but i still get stuck at the same spot. the screen is faded with a blue circle in the center that says welcome make your self at home. it has a create more screens for apps and folders wording at the bottom with an arrow, and a OK button.
I click OK and hear it click but nothing happens. i try to scroll for the arrow and hear actions but nothing happens. I can pull down the menu at the top and goto my email. but when i go back to home, that screen is still there. ive rebooted the device. tried clicking back to get past it. run task killer. it always comes back to this intro screen on the home screen
blacktuxnc said:
when i did that i can see icons on the homescreen which is different but i still get stuck at the same spot. the screen is faded with a blue circle in the center that says welcome make your self at home. it has a create more screens for apps and folders wording at the bottom with an arrow, and a OK button.
I click OK and hear it click but nothing happens. i try to scroll for the arrow and hear actions but nothing happens. I can pull down the menu at the top and goto my email. but when i go back to home, that screen is still there. ive rebooted the device. tried clicking back to get past it. run task killer. it always comes back to this intro screen on the home screen
Click to expand...
Click to collapse
weird. it happens after dirty flashing? the reason i said dirty flash is because those menus wont appear. it might be wise to flash the stock image, then reroot.
simms22 said:
weird. it happens after dirty flashing? the reason i said dirty flash is because those menus wont appear. it might be wise to flash the stock image, then reroot.
Click to expand...
Click to collapse
Can you point me in the right direction of the right stock image? i was downloading from googles developer site "Factory Images "occam" for Nexus 4" but i think that might be the wrong thing? wouldnt extract properly. several download attempts and methods
it was the right thing you were downloading probably, as it is a google site.
nexus factory images https://developers.google.com/android/nexus/images
how to flash the factory image http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
Ive got adb working on my raspberry pi now and im able to send commands but im getting an error towards the end
error failed to load 'image-occam--ktu84p.zip' : Cannot allocate memory
what folder is it trying to copy it to? /system?
i couldnt delete aps from system/app
i removed some stuff from /android/data but that didnt help. same error.
EDIT: Flashable zips from AndroidPolice (just flash from recovery) ----> http://www.androidpolice.com/2015/1...gs-android-6-0-marshmallow-nexus-ota-roundup/
Steps:
1) Backup apps and data
2) Make an Nandroid backup
3) Factory Reset (optional but recommended)
4) Download and install Android 6.0 factory image through adb https://developers.google.com/android/nexus/images?hl=en
5) Flash latest TWRP 2.8.7.0 recovery
6) Flash ElementalX kernel 5.0 for Marshmallow or stock rootable kernel from @zaclimon through TWRP http://elementalx.org/devices/nexus-7-2013/ or http://forum.xda-developers.com/showpost.php?p=63158038&postcount=210
7) Flash latest supersu 2.46 zip https://download.chainfire.eu/696/SuperSU
8) Reboot
Hope that someone creates a zip to flash...
My USB port is not reliable, and i'm kind of lazy.
Booting now... I'll report when it boots
Edit: First boot takes even longer than lollipop :/ (~10 minutes)
Just finished flashing the factory image. Waiting for it to boot also.
noahvt said:
Booting now... I'll report when it boots
Edit: First boot takes even longer than lollipop :/ (~10 minutes)
Click to expand...
Click to collapse
I waited about 8 mins. but nothing happend! No "optimising apps/system" message, so I wiped again....
Is that normal?
It booted !!! took what it felt like about 10-15 minutes (wasn't watching the clock, only my Flo's screen). Runing the Setup Wizzard now.
Feels snappy. I will be entertained for the next couple of hours
idCyber said:
It booted !!! took what it felt like about 10-15 minutes (wasn't watching the clock, only my Flo's screen). Runing the Setup Wizzard now.
Feels snappy. I will be entertained for the next couple of hours
Click to expand...
Click to collapse
I hope someone is already working on a custom kernel to support root lol
takes a long time to bootup first then its ok...all animationa re optimised and more of material animations are visible.. just enables system tuner (by pressing and holding settings icon until it spins on the notification tray and removed the aeroplane ,mobile data and torch mode).. i didnt find the restore from old nexus option.. but i did get sync data via bluetooth from existing android device...nice
Can someone test if there is kind of the multiwindow feature that we saw in the M Previews?
I have installed it using the app flashfire beta by chainfire. Still booting up but since it shows the android m boot animation, looks like a success
Installed fine for me, booted in what felt like a normal amount of time.
Problems may have begun trying to root though.
Use NRT... first problem: it didn't actually copy the root files over so when it rebooted into TWRP they weren't there. I just rebooted and manually copied them over, then back into TWRP and I was able to install them. But, now I'm sitting here at the startup animation for about 10 minutes now, far longer than after initial install, so I'm starting to think boot loop.
I'll give it a few more minutes and then re-flash the system partition, should get it working again. NRT naturally doesn't know about this version yet, using the *.*.* option, but I'm starting to get the feeling root isn't straight-up on M. I'll repost if it happens to start up, but anyone else try rooting yet? If so, how'd it go for you?
EDIT: Another thread seems to support the conclusion that root isn't working yet, someone else had a boot loop too (something to do with stock recovery replacing TWRP and TWRP trying to save itself, or some such).
moliverac8 said:
Can someone test if there is kind of the multiwindow feature that we saw in the M Previews?
Click to expand...
Click to collapse
Yes, not enabled by default:
pull build.prop from recovery and change release from user to userdebug
push build.prop
chmod 644 build.prop
reboot device and find it in dev options under drawing
my 32gb nexus7 is showing only 16gb of space...
i see this in other users when lollipop is out...
Flashed insecure boot.img, flashed root = bootloop So I REPEAT ROOT DOES NOT WORK
http://www.androidpolice.com/2015/1...es-are-live-for-the-nexus-5-6-7-9-and-player/
In the comments there are people saying that they're doing this:
"Unlocked bootloader + Change flash script to remove -w = Never wait for OTA again"
What is the remove -w? Apparently it makes it so it doesn't wipe userdata. that would be helpful but how would one accomplish that?
skyrocketeer said:
What is the remove -w? Apparently it makes it so it doesn't wipe userdata. that would be helpful but how would one accomplish that?
Click to expand...
Click to collapse
You just edit the batch file (.bat) or shell script (.sh) that comes with the factory image download with a text editor and remove the '-w' part from the fastboot line.
Waiting to try it using Multiboot (zip image and root)
Looks like we are not getting root until google decides to release the source code, what a bummer...
NO Gallery app as it was in Lollipop, now we need to use Photos ad main app for photos... :/, got old app drawer with black background scrolling is left-right not up-down. Shame they didn't add percentage battery too
Luk45z said:
NO Gallery app as it was in Lollipop, now we need to use Photos ad main app for photos... :/, got old app drawer with black background scrolling is left-right not up-down. Shame they didn't add percentage battery too
Click to expand...
Click to collapse
Hold settings icon in quick settings until it starts spinning and then release, system ui tuner will open, then enable show embedded battery percentage